I'm pretty new to Linux. I'm using Debian 12 on a laptop (and a dock) with the SwayWM wayland compositor. I have 2 external monitors connected to the dock, one landscape (DVI) monitor and another portrait (VGA) monitor. How could I: - Change the arrangement and rotation of the monitors - Set the background of any monitor to an image - Have persistence of everything when I undock and dock again Using Xubuntu, I can easily do everything using Xfce4 Display Settings and xfdesktop. But how do I do the aforementioned in Sway? (I don't need a GUI though since I'm rarely gonna change anything) Any advice would be appreciated. Thanks in advance.

I have this hardware: - Lenovo thinkpad x390 yoga - Lenovo thinkpad thunderbolt 3 dock gen 2/Workstation dock gen 2 and this software: Wayland + sway I would like to be able to connect laptop to the dock and it will charge it and connects external display using HDMI or display port. None of these think is happening. What should I do to be able to use the dock ? Thankyou for help ## Diagnostics cat /proc/version outputs

Linux version 6.9.7-arch1-1 (linux@archlinux) (gcc (GCC) 14.1.1 20240522, GNU ld (GNU Binutils) 2.42.0) #1 SMP PREEMPT_DYNAMIC Fri, 28 Jun 2024 04:32:50 +0000

lspci | grep -i thunder outputs

07:00.0 PCI bridge: Intel Corporation JHL6240 Thunderbolt 3 Bridge (Low Power) [Alpine Ridge LP 2016] (rev 01)
08:00.0 PCI bridge: Intel Corporation JHL6240 Thunderbolt 3 Bridge (Low Power) [Alpine Ridge LP 2016] (rev 01)
08:01.0 PCI bridge: Intel Corporation JHL6240 Thunderbolt 3 Bridge (Low Power) [Alpine Ridge LP 2016] (rev 01)
08:02.0 PCI bridge: Intel Corporation JHL6240 Thunderbolt 3 Bridge (Low Power) [Alpine Ridge LP 2016] (rev 01)
09:00.0 System peripheral: Intel Corporation JHL6240 Thunderbolt 3 NHI (Low Power) [Alpine Ridge LP 2016] (rev 01)
2f:00.0 USB controller: Intel Corporation JHL6240 Thunderbolt 3 USB 3.1 Controller (Low Power) [Alpine Ridge LP 2016] (rev 01)

In journalctl -p 3 -xb is this:

Jul 06 17:08:43 archlinux kernel: ucsi_acpi USBC000:00: con1: failed to register alt modes
Jul 06 17:08:43 archlinux kernel: ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed
Jul 06 17:09:14 archlinux acpid: cannot open input layer
Jul 06 17:09:14 archlinux acpid: can't open socket /var/run/acpid.socket: Address already in use
Jul 06 17:09:15 archlinux sudo: pam_unix(sudo:auth): conversation failed
Jul 06 17:09:15 archlinux sudo: pam_unix(sudo:auth): auth could not identify password for [john]
Jul 06 17:09:17 archlinux sudo: pam_unix(sudo:auth): conversation failed
Jul 06 17:09:17 archlinux sudo: pam_unix(sudo:auth): auth could not identify password for [john]

I have these packages installed: - local/bolt 0.9.8-1 - Thunderbolt 3 device manager - local/plasma-thunderbolt 6.1.2-1 (plasma) - Plasma integration for controlling Thunderbolt devices - local/tbtools 0.4.1-1 - Collection of tools for Linux Thunderbolt/USB4 development, debugging and validation systemctl status bolt.service outputs

● bolt.service - Thunderbolt system service
     Loaded: loaded (/usr/lib/systemd/system/bolt.service; static)
     Active: active (running) since Sat 2024-07-06 17:08:40 CEST; 24min ago
 Invocation: 391ae69c33e947c9aa0b9dde79bdc8b6
       Docs: man:boltd(8)
   Main PID: 1015 (boltd)
     Status: "authmode: enabled, force-power: unset"
      Tasks: 4 (limit: 18738)
     Memory: 1.6M (peak: 2.3M)
        CPU: 153ms
     CGroup: /system.slice/bolt.service
             └─1015 /usr/lib/boltd

Jul 06 17:08:40 archlinux boltd: udev: enumerating devices
Jul 06 17:08:40 archlinux boltd: probing: adding /sys/devices/pci0000:00/0000:00:1c.4/0000:07:00.0 to roots
Jul 06 17:08:40 archlinux boltd: [d7030000-00a2-domain0                    ] bootacl: synchronizing journal
Jul 06 17:08:40 archlinux boltd: security level set to 'user'
Jul 06 17:08:40 archlinux boltd: [d7030000-00a2-domain0                    ] connected: as domain0 [user] (/sys/devices/pci0000:00/0000:00:1c.4/0000:07:00.0/0000:08:00.0/0000:09:00.0/domain0)
Jul 06 17:08:40 archlinux boltd: [d7030000-00a2-X390-YOGA                  ] parent is (null)...
Jul 06 17:08:40 archlinux boltd: [d7030000-00a2-X390-YOGA                  ] connected: authorized (/sys/devices/pci0000:00/0000:00:1c.4/0000:07:00.0/0000:08:00.0/0000:09:00.0/domain0/0-0)
Jul 06 17:08:40 archlinux boltd: [d7030000-00a2-domain0                    ] dbus: exported domain at /org/freedesktop/bolt/domains/d7030000_00a2_a088_a074_8e242873d324
Jul 06 17:08:40 archlinux boltd: [d7030000-00a2-X390-YOGA                  ] dbus: exported device at /org/freedesktop/bolt/devices/d7030000_00a2...
Jul 06 17:08:40 archlinux systemd: Started Thunderbolt system service.

boltctl list does not output anything boltctl list --all outputs

● Lenovo X390-YOGA
   ├─ type:          host
   ├─ name:          X390-YOGA
   ├─ vendor:        Lenovo
   ├─ uuid:          d7030000-00a2-a088-a074-8e242873d324
   ├─ generation:    Thunderbolt 3
   ├─ status:        authorized
   │  ├─ domain:     d7030000-00a2-a088-a074-8e242873d324
   │  └─ authflags:  none
   ├─ authorized:    Sat Jul  6 15:08:38 2024
   ├─ connected:     Sat Jul  6 15:08:38 2024
   └─ stored:        Sun May 26 12:38:48 2024
      ├─ policy:     manual
      └─ key:        no

lsmod | grep thunderbolt outputs

intel_wmi_thunderbolt    16384  0
thunderbolt           565248  0
wmi                    36864  4 video,intel_wmi_thunderbolt,wmi_bmof,think_lmi

## What I tried - Rebooting - Updating kernel - Updating firmware

If my ThinkPad P1 gen4 is connected to Lenovo Thunderbolt4-dock (0B40 series). I'm not able to start. My root- and home-partitions are encrypted with luks. At boot I'm asked for passphrase, for decrypting root-partition. This works if it is not attached to dock. If it is connected, after I wrote passphrase, but I get

`
no key available with this passphrase

` Why the dock is blocking decrypting partition?

I've recently installed Arch and chose KDE5 for my desktop environment. Being a fan of docks, I've opted to install Latte. The problem is that icons do not appear in my dock at all, thus rendering it pretty much unusable.  I remember reading somewhere in a bug report (which I can't find at the moment, and was really difficult to find in the first place) that Latte uses libtaskmanager to display the icons. However, the task manager has no issues displaying icons whatsoever. How can I fix this?

On Debian-based Linux, dnsmasq works by replacing the nameservers in /etc/resolv.conf with 127.0.0.1 (referring to "Linux for Wireless Engineers: How to Do DNS Caching with dnsmasq "). But I find that on Alpine (and Alpine based docker) it does not work that way. When dnsmasq starts, /etc/resolv.conf remains the same. So if I just start dnsmasq it makes no difference in term of dns resolving. I write a script to start dnsmasq and it feels awkward. cp /etc/resolv.conf /etc/resolv.dnsmasq sed -i 's/^nameserver.*/nameserver 127.0.0.1/' /etc/resolv.conf dnsmasq -r /etc/resolv.dnsmasq So is there a better ("proper") way make dnsmasq work on Alpine ?

If I use a dock on Xubuntu, I get a screen corruption: vs. Tried with plank and docky. Any clue?

I am running Debian 12 on my Dell Precision 3581. I typically go between two physical locations, both of which have docking stations. One docking station, a Dell something or other, always works flawlessly. The other, a Lenovo ThinkPad Thunderbolt 3 Dock Gen 2, works great when I boot my laptop with the docking station connected, but I have USB issues when I undock and re-dock. Here's is lsusb | sort after a boot while docked

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 1bcf:28d2 Sunplus Innovation Technology Inc. Integrated_Webcam_FHD
Bus 001 Device 004: ID 8087:0033 Intel Corp. AX211 Bluetooth
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 17ef:3080 Lenovo USB2.0 Hub             
Bus 003 Device 003: ID 2109:2820 VIA Labs, Inc. VL820 Hub
Bus 003 Device 004: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 003 Device 005: ID 2109:8818 VIA Labs, Inc. USB Billboard Device   
Bus 003 Device 006: ID 17ef:3081 Lenovo USB2.0 HUB
Bus 003 Device 007: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 003 Device 009: ID 17ef:3083 Lenovo ThinkPad Thunderbolt 3 Dock USB Audio
Bus 003 Device 010: ID 413c:2113 Dell Computer Corp. KB216 Wired Keyboard
Bus 003 Device 011: ID 17ef:608d Lenovo Optical Mouse
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 002: ID 17ef:307f Lenovo USB3.1 Hub             
Bus 004 Device 003: ID 2109:0820 VIA Labs, Inc. VL820 Hub
Bus 004 Device 004: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 004 Device 005: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 004 Device 006: ID 17ef:3082 Lenovo ThinkPad TBT 3 Dock
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

and this is what I have after undocking and re-docking

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 1bcf:28d2 Sunplus Innovation Technology Inc. Integrated_Webcam_FHD
Bus 001 Device 004: ID 8087:0033 Intel Corp. AX211 Bluetooth
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

As you can see, buses 3 and 4 are missing. The only log I can find that something is going wrong is in dmesg which shows

[  688.046933] xhci_hcd 0000:05:00.0: Host halt failed, -19                                                                                                                                                          
[  688.046942] xhci_hcd 0000:05:00.0: Host not accessible, reset failed.                     
[  688.047612] xhci_hcd 0000:05:00.0: USB bus 3 deregistered

I did a few more sanity checks (lsmod, tree /sys/bus/usb/drivers/, ls -al /sys/bus/pci/drivers/xhci_hcd which I can post here if desired) which again confirm that the USB buses and and corresponding PCI devices are missing, I can't find the reason why. Does anyone have any ideas?

I'm using Pop!_OS 22.04. I just downloaded and installed a new app (PyCharm), but it didn't come with an icon for my dock. I created a new icon using this ~/.local/share/applications/pycharm.desktop file:

[Desktop Entry]
Encoding=UTF-8
Version=1.0
Type=Application
Terminal=false
Exec=/opt/pycharm-2022.1.1/bin/pycharm.sh
Name=PyCharm
Icon=/home/USERNAME/Pictures/icons/pycharm.png

This seems to work great. I can see the icon I chose when I look for the app, and it opens in my dock. The only problem is that I can't seem to pin it to my dock's favorites. The "Add to Favorites" button that every other dock icon has when I right click on them doesn't appear in my new icon at all. Am I doing something wrong? Am I missing something? Is this a bug? Update: I've seen this on other apps too, but for PyCharm, turns out there's an option in the GUI to create the desktop launcher. It appears to do exactly the same thing I did (place a .desktop file in the same folder), but it also adds a few extra keys. The biggest one seems to be StartupWMClass. If that key is included, the "Add to Favorites" option appears when you right-click the icon in the dock. If the StartupWMClass key is not present, the "Add to Favorites" option is not there. Why is that? What does that option do?

I just installed Parsehub on a System 76 Lemur Pro running Pop!_OS 22.04. Question applies to other apps though When I run Parsehub via the command line, the app's icon appears on the dock. How can I save it so it stays there even when the app is closed? When I right click on the icon, there is no option to save it to favorites. Thank you!

# Symptoms 2 out of 4 monitors don't light up after suspend. This is a similar problem as this post but not quite the same. # Hardware - Dell XPS 9320 plus (i7-1280P) - UD22 Dock - 4 monitors # OS - LinuxMint 21.2 with kernel 5.19.0-50 (all is well except, 10-15% chance, 1 of the monitors doesn't revive after suspend and I just need to reboot) - LinuxMint 21.2 with kernel 6.2.0-26 (where the problem occurs) # Software - DisplayLink driver 5.6.1, 5.7.0, 5.8.0 Standalone Installer # Other info Unlike this post , the service is always "loaded" and "active (running)" even when 2 monitors don't revive.

$ sudo systemctl status displaylink-driver.service 

        ● displaylink-driver.service - DisplayLink Driver Service
     Loaded: loaded (/lib/systemd/system/displaylink-driver.service; static)
     Active: active (running) since Mon 2023-08-14 09:06:37 EDT; 1h 48min ago
    Process: 1240 ExecStartPre=/bin/sh -c modprobe evdi || (dkms install $(ls -t /usr/src | grep evdi | head -n1  | sed -e "s:-:/:") && modprobe evdi) (code=exited, status=0/SUCCESS)

   Main PID: 1243 (DisplayLinkMana)
      Tasks: 53 (limit: 37856)
     Memory: 103.3M
        CPU: 24min 30.305s
     CGroup: /system.slice/displaylink-driver.service
             └─1243 /opt/displaylink/DisplayLinkManager

Aug 14 09:06:37 xps-9320 systemd[1] : Starting DisplayLink Driver Service...
Aug 14 09:06:37 xps-9320 systemd[1] : Started DisplayLink Driver Service.

# What I tried: 1. Upgrade the DisplayLink driver to 5.7.0 then 5.8.0 2. Upgrade evdi to 1.13.1 then 1.14.1 3. Restart the service Nothing worked. So far the most effective way is to logout/login, which is much faster than reboot. Somehow the DisplayLink driver causes a long hanging (120 secs) during startup/reboot. # Updates 1. Oct 31, 2023 - problem solved after upgrading to kernel 6.2.0-36 2. Jan 17, 2024 - upgrading from Linux Mint 21.2 to 21.3 somehow stopped the service. I had to start the service manually.

$ sudo systemctl start displaylink-driver.service

Struggling with some devices often not functioning upon suspend , I came across the SE U&L question of [reloading drivers](https://unix.stackexchange.com/questions/113828/how-to-find-and-reload-specific-driver-from-kernel). In my case, a few devices are not detected, and I can see the driver (displaylink-driver.service) is loaded but inactive/dead.  So, is it possible to start drivers up again? $ lsusb # missing usb devices (detected by $ lsusb before the issue) Bus 004 Device 005: ID 17ef:a357 Lenovo USB3.1 Hub Bus 004 Device 004: ID 17ef:a359 Lenovo ThinkPad Lan Bus 004 Device 003: ID 17e9:6015 DisplayLink ThinkPad Hybrid USB-C with USB-A Dock Bus 004 Device 002: ID 17ef:a356 Lenovo USB3.1 Hub $ sudo systemctl status displaylink-driver.service ● displaylink-driver.service - DisplayLink Driver Service Loaded: loaded (/lib/systemd/system/displaylink-driver.service; static) Active: inactive (dead) May 26 14:50:56 debija systemd[1] : Starting DisplayLink Driver Service... May 26 14:50:56 debija systemd[1] : Started DisplayLink Driver Service. May 26 18:03:21 debija systemd[1] : Stopping DisplayLink Driver Service... May 26 18:03:22 debija systemd[1] : displaylink-driver.service: Succeeded. May 26 18:03:22 debija systemd[1] : Stopped DisplayLink Driver Service. May 26 18:03:22 debija systemd[1] : displaylink-driver.service: Consumed 41min 25.761s CPU time.

Two monitors sometimes wake up from suspend, and other times they do not e.g. . _Specifically_, entering suspend and hitting the keyboard seems to wake up the monitors the first time. But clicking suspend the second time the monitors remain black. As a result USB devices connecting the monitors to the laptop with Displaylink cannot be found, and the Displaylink driver is deactivated. Only reboot works. Other usb connected devices to the dock work, such as keyboard and mouse. The issue seems independent of the lid position and does not occur 'intermittently' . How to troubleshoot? Is the issue due to DisplayLink, suspend, or something else? The following did _not_ work: - turn off USB autosuspend and blacklist in tlp or TLP UI. - thunderbolt-tools , tbtadm approve-all and checking with lspci devices. - Unplugging hdmi or usb-c of the dock. I would not know what I would be doing: - remove /etc/pm/sleep.d/displaylink.sh. - udev rules - blacklist - powertop Some possible involved files

/etc/tlp.conf 
/sys/bus/usb/devices/usb3/power/wakeup

/usr/lib/systemd/system-sleep/displaylink.sh
/usr/lib/systemd/system/displaylink-driver.service
/etc/udev/rules.d/99-displaylink.rules
/etc/pm/sleep.d/10_displaylink
/opt/displaylink/suspend.sh
/etc/pm/sleep.d/10_displaylink

___log__: suspend causes evdi to be disconnected/closed?_

$ sudo dmesg -w | grep Display

[    3.306247] usb 4-1.2: Manufacturer: DisplayLink
[    7.395781] evdi: [I] (card1) Opened by Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[    7.397744] evdi: [I] (card1) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[    7.399740] evdi: [I] (card2) Opened by Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[    7.401344] evdi: [I] (card2) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[    9.889337] evdi: [I] (card1) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[    9.912344] evdi: [I] (card2) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[ 1849.616093] evdi: [I] (card1) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[ 1849.616521] evdi: [I] (card2) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[ 7301.667983] evdi: [I] (card1) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[ 7301.668399] evdi: [I] (card2) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11442.370372] evdi: [I] (card1) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11442.370503] evdi: [I] (card2) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11552.506775] evdi: [I] (card1) Disconnected from Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11552.534477] evdi: [I] (card1) Closed by Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11552.536880] evdi: [I] (card2) Disconnected from Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11552.542512] evdi: [I] (card2) Closed by Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)

# a little more dmseg output
[11293.477299] evdi: [I] (card2) Notifying display power state: off
[11293.477327] evdi: [I] (card1) Notifying display power state: off
[11293.479051] evdi: [I] (card2) Notifying display power state: off
[11293.479737] evdi: [I] (card1) Notifying display power state: off
[11302.597210] PM: suspend entry (s2idle)
[11302.613795] Filesystems sync: 0.016 seconds
[11302.614152] (NULL device *): firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin
[11302.614496] (NULL device *): firmware: direct-loading firmware regulatory.db
[11302.614516] (NULL device *): firmware: direct-loading firmware regulatory.db.p7s
[11302.615831] (NULL device *): firmware: direct-loading firmware iwlwifi-8265-36.ucode
[11302.615962] Freezing user space processes ... (elapsed 0.003 seconds) done.
[11302.619720] OOM killer disabled.
[11302.619723] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[11302.621413] printk: Suspending console(s) (use no_console_suspend to debug)
[11302.892991] e1000e: EEE TX LPI TIMER: 00000011
[11302.930826] ACPI: EC: interrupt blocked
[11438.215551] ACPI: EC: interrupt unblocked
[11438.233739] pcieport 0000:00:1c.2: Intel SPT PCH root port ACS workaround enabled
[11438.233740] pcieport 0000:00:1c.0: Intel SPT PCH root port ACS workaround enabled
[11439.737330] pcieport 0000:00:1d.0: Intel SPT PCH root port ACS workaround enabled
[11441.218576] pcieport 0000:00:1c.4: Intel SPT PCH root port ACS workaround enabled
[11441.537943] usb 1-10: reset full-speed USB device number 7 using xhci_hcd
[11441.699720] OOM killer enabled.
[11441.699723] Restarting tasks ... 
[11441.699875] pci_bus 0000:08: Allocating resources
[11441.699914] pci_bus 0000:3c: Allocating resources
[11441.713490] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
[11441.714617] done.
[11441.778266] PM: suspend exit
[11441.943765] evdi: [I] (card1) Notifying display power state: on
[11441.943785] evdi: [I] (card1) Notifying mode changed: 2560x1440@60; bpp 32; pixel format XR24 little-endian (0x34325258)
[11441.943786] evdi: [I] (card1) Notifying display power state: on
[11441.953580] evdi: [I] (card2) Notifying display power state: on
[11441.953595] evdi: [I] (card2) Notifying mode changed: 1920x1080@60; bpp 32; pixel format XR24 little-endian (0x34325258)
[11441.953596] evdi: [I] (card2) Notifying display power state: on
[11441.957136] psmouse serio1: synaptics: queried max coordinates: x [..5678], y [..4720]
[11441.987991] psmouse serio1: synaptics: queried min coordinates: x [1264..], y [1132..]
[11442.370370] evdi: [W] evdi_painter_connect:883 (card1) Double connect - replacing 00000000249f7991 with 00000000249f7991
[11442.370372] evdi: [I] (card1) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11442.370374] evdi: [I] (card1) Connector state: connected
[11442.370502] evdi: [W] evdi_painter_connect:883 (card2) Double connect - replacing 00000000d81e37fa with 00000000d81e37fa
[11442.370503] evdi: [I] (card2) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11442.370504] evdi: [I] (card2) Connector state: connected
[11445.432016] evdi: [I] (card1) Notifying mode changed: 2560x1440@60; bpp 32; pixel format XR24 little-endian (0x34325258)
[11445.432022] evdi: [I] (card1) Notifying display power state: on
[11445.444692] evdi: [I] (card2) Notifying mode changed: 1920x1080@60; bpp 32; pixel format XR24 little-endian (0x34325258)
[11445.444698] evdi: [I] (card2) Notifying display power state: on
[11495.853579] e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down
[11495.863841] evdi: [I] (card2) Notifying display power state: off
[11495.863875] evdi: [I] (card1) Notifying display power state: off
[11495.865487] evdi: [I] (card2) Notifying display power state: off
[11495.868225] evdi: [I] (card1) Notifying display power state: off
[11498.374912] PM: suspend entry (s2idle)
[11498.387093] Filesystems sync: 0.012 seconds
[11498.387319] (NULL device *): firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin
[11498.387679] (NULL device *): firmware: direct-loading firmware regulatory.db.p7s
[11498.387682] (NULL device *): firmware: direct-loading firmware regulatory.db
[11498.388599] (NULL device *): firmware: direct-loading firmware iwlwifi-8265-36.ucode
[11498.388662] Freezing user space processes ... (elapsed 0.004 seconds) done.
[11498.392991] OOM killer disabled.
[11498.392994] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[11498.394918] printk: Suspending console(s) (use no_console_suspend to debug)
[11498.466114] hub 4-1:1.0: hub_ext_port_status failed (err = -71)
[11498.473177] usb 4-1.4: Port disable: can't disable remote wake
[11498.481987] usb 4-1-port4: cannot disable (err = -71)
[11498.596552] usb 4-1-port4: device 4-1.4 not suspended yet
[11498.641355] e1000e: EEE TX LPI TIMER: 00000011
[11503.725305] xhci_hcd 0000:3c:00.0: xHCI host not responding to stop endpoint command.
[11503.725312] xhci_hcd 0000:3c:00.0: USBSTS: 0x00000000
[11503.725321] xhci_hcd 0000:3c:00.0: xHCI host controller not responding, assume dead
[11503.725344] xhci_hcd 0000:3c:00.0: HC died; cleaning up
[11503.749658] ACPI: EC: interrupt blocked
[11549.036097] ACPI: EC: interrupt unblocked
[11549.054131] pcieport 0000:00:1c.0: Intel SPT PCH root port ACS workaround enabled
[11549.054135] pcieport 0000:00:1c.2: Intel SPT PCH root port ACS workaround enabled
[11550.541723] pcieport 0000:00:1d.0: Intel SPT PCH root port ACS workaround enabled
[11552.003809] pcieport 0000:00:1c.4: Intel SPT PCH root port ACS workaround enabled
[11552.314323] usb 1-10: reset full-speed USB device number 7 using xhci_hcd
[11552.487970] OOM killer enabled.
[11552.487973] Restarting tasks ... 
[11552.488140] pci_bus 0000:08: Allocating resources
[11552.488177] pci_bus 0000:3c: Allocating resources
[11552.488237] usb 4-1.2: USB disconnect, device number 3
[11552.491498] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
[11552.495234] evdi: [I] Detached from parent device
[11552.495237] evdi: [I] Detached from parent device
[11552.495386] usb 4-1.3: USB disconnect, device number 4
[11552.495433] cdc_ether 4-1.3:2.0 enx806d973a4123: unregister 'cdc_ether' usb-0000:3c:00.0-1.3, CDC Ethernet Device
[11552.496390] usb 4-1: USB disconnect, device number 2
[11552.501152] done.
[11552.506775] evdi: [I] (card1) Disconnected from Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11552.506780] evdi: [I] (card1) Removing i2c adapter bus number 8
[11552.534477] evdi: [I] (card1) Closed by Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11552.536880] evdi: [I] (card2) Disconnected from Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11552.536882] evdi: [I] (card2) Removing i2c adapter bus number 9
[11552.538087] usb 4-1.4: USB disconnect, device number 5
[11552.542512] evdi: [I] (card2) Closed by Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11552.567133] PM: suspend exit
[11552.738946] psmouse serio1: synaptics: queried max coordinates: x [..5678], y [..4720]
[11552.769228] psmouse serio1: synaptics: queried min coordinates: x [1264..], y [1132..]
[11665.969996] usb 1-9: USB disconnect, device number 6
[11666.277389] usb 1-9: new full-speed USB device number 13 using xhci_hcd
[11666.427964] usb 1-9: New USB device found, idVendor=06cb, idProduct=009a, bcdDevice= 1.64
[11666.427973] usb 1-9: New USB device strings: Mfr=0, Product=0, SerialNumber=1
[11666.427978] usb 1-9: SerialNumber: a9fd9886e55f
[11668.237192] usb 1-9: USB disconnect, device number 13
[11669.029351] usb 1-9: new full-speed USB device number 14 using xhci_hcd
[11669.179964] usb 1-9: New USB device found, idVendor=06cb, idProduct=009a, bcdDevice= 1.64
[11669.179973] usb 1-9: New USB device strings: Mfr=0, Product=0, SerialNumber=1
[11669.179978] usb 1-9: SerialNumber: a9fd9886e55f

_displaylink-driver.service becomes inactive and usb device is not registered - after suspend_

$ sudo systemctl status displaylink-driver.service 
● displaylink-driver.service - DisplayLink Driver Service
     Loaded: loaded (/lib/systemd/system/displaylink-driver.service; static)
     Active: inactive (dead)

May 26 14:50:56 debija systemd[1] : Starting DisplayLink Driver Service...
May 26 14:50:56 debija systemd[1] : Started DisplayLink Driver Service.
May 26 18:03:21 debija systemd[1] : Stopping DisplayLink Driver Service...
May 26 18:03:22 debija systemd[1] : displaylink-driver.service: Succeeded.
May 26 18:03:22 debija systemd[1] : Stopped DisplayLink Driver Service.
May 26 18:03:22 debija systemd[1] : displaylink-driver.service: Consumed 41min 25.761s CPU time.

$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 0bda:0328 Realtek Semiconductor Corp. USB3.0-CRW
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 014: ID 06cb:009a Synaptics, Inc. Metallica MIS Touch Fingerprint Reader
Bus 001 Device 004: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated Camera
Bus 001 Device 009: ID 1395:0025 Sennheiser Communications Headset [PC 8]
Bus 001 Device 012: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse
Bus 001 Device 011: ID 145f:020c Trust Trust Ergo Mouse
Bus 001 Device 010: ID 04b4:5218 Cypress Semiconductor Corp. USB-Serial Bridge
Bus 001 Device 008: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 005: ID 17ef:1029 Lenovo USB2.0 Hub             
Bus 001 Device 002: ID 17ef:1028 Lenovo USB2.0 Hub             
Bus 001 Device 007: ID 056a:5144 Wacom Co., Ltd Pen and multitouch sensor
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


# missing usb devices (detected by $ lsusb before the issue)
Bus 004 Device 005: ID 17ef:a357 Lenovo USB3.1 Hub             
Bus 004 Device 004: ID 17ef:a359 Lenovo ThinkPad Lan
Bus 004 Device 003: ID 17e9:6015 DisplayLink ThinkPad Hybrid USB-C with USB-A Dock
Bus 004 Device 002: ID 17ef:a356 Lenovo USB3.1 Hub

With Debian stable and proprietary drivers on a Lenovo x1 3rd gen--but not with MS windows 10 on an older Lenovo laptop (using the usb-c to usb-a) and a HP laptop (using usb-c)--I have a problem with the *ThinkPad Hybrid USB-C with USB-A Dock*: The USB-devices mouse, keyboard, and headset works fine; but the two monitors do not (akin to Pauxlo's experience ). What to do? 1. forget about using this docking station (costly) 2. install Ubuntu (well, Debian is otherwise nice and installed) 3. try to make DisplayLink for Ubuntu [2] [3] work on Debian (may be quite involved) 4. ask the question elsewhere e.g. on the displaylink forum, on the linux-hardware.org forum, et cetera. 5. other alternatives I have found related issues, some which are solved, others which are still unsolved: - detected on Debian 11 and Debian Testing with "snd_usb_audio" driver according to linux-hardware.org - Debian Buster with a link to solution for arch linux - solutions and non-solutions [7] [8] for Ubuntu distributions - issue on Fedora, solution on RHEL8 and so on - in case of high resolution, apt-get install evdi-dkms libevdi0 has been suggested for Debian [10]

$ lsusb
Bus 004 Device 011: ID 17e9:6015 DisplayLink ThinkPad Hybrid USB-C with USB-A Dock

I have a Lenovo X220 with a dock and external screen. Right now I have to launch a xrandr shortcut by hand to use the screen I want, depending on the situation. For example : - Docked : xrandr with external screen output - Not docked : xrandr with laptop screen output I was wondering how to do this automatically, maybe with help of lsusb's output? When the laptop is docked it lists Lenovo ThinkPad Mini Dock Plus Series 3, is there a way to detect that and then run the corresponding xrandr command? Or maybe there's another simpler solution?

I have a Dell laptop which is connected to a Dell WD19TB dock. It is set up to be able to dual boot into Windows 10 as well as Kubuntu 22.04 (the problem also existed with 20.04). When I turn off the laptop from within Windows, then I can send a WOL packet to the MAC address of the NIC of the dock. This does not work when I turn off the laptop from within Kubuntu. When I connect the network cable directly into the laptop instead of the dock, then I can wake up the laptop after having it shut down from within Kubuntu, when I send the WOL packet to the NIC of the laptop. What could the issue here? ethtool signals that the NIC is set up correctly, that WOL is active.

ethtool enx
Settings for enx:
	Supported ports: [ TP	 MII ]
	Supported link modes:   10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	                        1000baseT/Half 1000baseT/Full
	Supported pause frame use: No
	Supports auto-negotiation: Yes
	Supported FEC modes: Not reported
	Advertised link modes:  10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	                        1000baseT/Full
	Advertised pause frame use: No
	Advertised auto-negotiation: Yes
	Advertised FEC modes: Not reported
	Link partner advertised link modes:  10baseT/Half 10baseT/Full
	                                     100baseT/Half 100baseT/Full
	                                     1000baseT/Full
	Link partner advertised pause frame use: No
	Link partner advertised auto-negotiation: Yes
	Link partner advertised FEC modes: Not reported
	Speed: 1000Mb/s
	Duplex: Full
	Auto-negotiation: on
	Port: MII
	PHYAD: 32
	Transceiver: internal
	Supports Wake-on: pumbg
	Wake-on: g
        Current message level: 0x00007fff (32767)
                               drv probe link timer ifdown ifup
                               rx_err tx_err tx_queued intr
                               tx_done rx_status pktdata hw wol
	Link detected: yes

lshw -class network prints

description: Ethernet interface
physical id: 14
bus info: usb@4:2.4
logical name: enx
serial: 
size: 1Gbit/s
capacity: 1Gbit/s
capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8152 driverversion=v1.12.13 duplex=full firmware=rtl8153b-2 v1 10/23/19 link=yes multicast=yes port=MII speed=1Gbit/s

The dock is connected via Thunderbolt. Maybe Windows is putting the dock into some sort of standby mode while Kubuntu is powering it off? Same issue when putting the Laptop to sleep, it won't wake up with a WOL.

I've got a WD15 dock and a Dell laptop running Arch Linux. I inserted two monitors' HDMI plugs into the dock and plugged the dock's USB-C cable into my laptop. The laptop display outputs correctly to the monitors. I inserted the plug of a USB keyboard and mouse into the dock, but the laptop didn't detect them. I plugged an Ethernet cable into the dock, but the laptop did not detect that either. What must I do to make the laptop detect the keyboard, mouse and Ethernet cable that are plugged into the WD15?

I am trying to make a **Lenovo Thinkpad P52** work with an **Lenovo USB-C Hybrid Dock** (**40AF**, see [docks to avoid](https://www.reddit.com/r/thinkpad/wiki/newdocks#wiki_overview) ...) on Linux Mint 20.3 Una a.k.a. **Ubuntu 20.04**. What a ... journey ... The laptop has its /home folder sitting on a ZFS file system (zpool). The operating system itself runs on btrfs. Graphics are switched to dedicated (i.e. Nvidia) in the BIOS and driven by Nvidia's proprietary driver. The laptop's BIOS [has been updated](https://wiki.archlinux.org/title/Lenovo_ThinkPad_P52) to the latest version beforehand to avoid bricking the mainboard in this kind of setup (really impressive BIOS bugs). Thunderbold security has been switched off in the BIOS as well. Interestingly, the dock does not show up when running boltctl list - although I had to disable Thunderbold security. I guess this is where the "hybrid" comes in. DisplayLink drivers have been installed from [here](https://www.displaylink.com/downloads/ubuntu) . I *should* be ready to go. When I **boot the laptop with the dock disconnected**, everything works **fine**. I can then plug the dock in once the computer is up and network plus USB on the dock are working as expected. (I am not yet far enough down the rabbit hole to trouble-shoot the display connection.) When I **boot with the dock plugged into the laptop**, the boot hangs for about two minutes just before the login screen should appear. It usually shows a single line of console output, usually some error, but different ones every time (e.g. ucsi_acpi USBC000:00 con1 failed to register alternate modes or bluetooth hci0 setting interface failed (71)). I figure that those errors also happen without the dock - it's due to the hang that I can see them, I guess. When I wait for some timeout to pass, I am presented with the usual graphical login screen, though login attempts fail. This is when I discovered that my zpool was gone (every time when I booted with the dock connected), hence there was no user folder to log a user into. I switched to the command line (Ctrl+F1) and checked zpool status - nothing. A manual zpool import data, the contents of /home showed up again, back the the login screen (Ctrl+F7) and everything worked fine. The timeout and the fact that my zpool is gone suggest some sort of error during kernel module loading or initialization, perhaps the order in which things happen - though I am not sure how to debug this or what is going on. Without the dock, everything works as expected. --- *I am troubleshooting this system for a visually impaired person. The whole point of the docking station is that there are fewer cables to connect/disconnect from the laptop. It's the general difficulty of plugging the cables in and out that has created my scenario. Therefore, it's a tough sell for me to say "just unplug the cable every time before you boot the machine even if you do not carry it with you" even if it's only this one cable.*

I have installed plank and noticed the transparent field with a distinct border (which is not only visible, windows even stick to it when dragged near) around it. Below a picture where I have highlighted a part of it. How to get rid of this effect? I have seen many screen shots of plank without this but switching themes in the settings doesn't seem to help. Nor could I find the option to disable it.

I used to use dash-to-dock as my daily driver now, I tried switching to plank but whenever I open the activities menu I see another dock at the left of my screen(even after I disable the dash-to-dock gnome extension). I tried installing the vanilla-gnome-desktop but that too has that dock at the side. Is there any way of getting rid of that dock?

Suppose I have a program myapp. It has two sub tasks, A and B. Launcjhing myapp --task A launches A and similar for B. Launching myapp only opens another intro window. I have three .desktop files in /usr/local/share/applications: myapp.desktop, myappA.desktop and myappB.desktop; all with different icons. When I launch myappA from applications menu in my desktop environment, it opens task A but the icon shown in plasma task manager (or dock in gnome) is of myapp.desktop. Also if I run myappA and myappB together, they are grouped together (I can prevent grouping but that will not group two task A windows also). The behavior is consistent in KDE, GNOME and other DE's. So is there any way to have three different icons for task A, task B and intro windows in task manager?