NikhilWanpal's questions

I have 22.10 running on a Dell laptop, received a popup to upgrade to 23.04. During the installation I got an error message stating that the installation of linux-headers-6.2.0-20-generic has failed due to an error. At the end it said that the system will be left in an unstable state. I have not restarted the laptop, but I believe it wont restart if I tried! :/

Here is the output of sudo dpkg --configure -a:

Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ...
Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ...
/etc/kernel/header_postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.2.0-20-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module:
Cleaning build area...
make -j4 KERNELRELEASE=6.2.0-20-generic all INCLUDEDIR=/lib/modules/6.2.0-20-generic/build/include KVERSION=6.2.0-20-generic DKMS_BUILD=1...(bad exit status: 2)
ERROR (dkms apport): binary package for evdi: 1.12.0 not found
Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
Consult /var/lib/dkms/evdi/1.12.0/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
   ...fail!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
dpkg: error processing package linux-headers-6.2.0-20-generic (--configure):
 installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-headers-generic:
 linux-headers-generic depends on linux-headers-6.2.0-20-generic; however:
  Package linux-headers-6.2.0-20-generic is not configured yet.

dpkg: error processing package linux-headers-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic:
 linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however:
  Package linux-headers-generic is not configured yet.

dpkg: error processing package linux-generic (--configure):
 dependency problems - leaving unconfigured
Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.2.0-20-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module:
Cleaning build area...
make -j4 KERNELRELEASE=6.2.0-20-generic all INCLUDEDIR=/lib/modules/6.2.0-20-generic/build/include KVERSION=6.2.0-20-generic DKMS_BUILD=1...(bad exit status: 2)
ERROR (dkms apport): binary package for evdi: 1.12.0 not found
Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
Consult /var/lib/dkms/evdi/1.12.0/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
   ...fail!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: error processing package linux-image-6.2.0-20-generic (--configure):
 installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 linux-headers-6.2.0-20-generic
 linux-headers-generic
 linux-generic
 linux-image-6.2.0-20-generic

What should I do to fix this?

I am using fully patched / updated Ubuntu 21.04 + KDE 5.21.4 on Lenovo Thinkpad X1 extreme Gen 3. Kernel in use is 5.11.0-37-generic, with latest firmware for the System (0.1.17) and Intel (225.53.1649).

I am trying to use OnePlus buds Z with the laptop and they keep randomly disconnecting every once in a while. I have not seen this issue when I use them with my phone; so I believe the buds are fine.

Here are the logs:

> journalctl -r -n 12000 | grep bluetooth                                                                                                                          
Sep 29 14:18:24 Matrix bluetoothd[792]: /org/bluez/hci0/dev_E4_41_22_45_85_0D/sep1/fd4: fd(40) ready
Sep 29 14:18:18 Matrix bluetoothd[792]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to E4:41:22:45:85:0D: Connection timed out (110)
Sep 29 14:17:55 Matrix dbus-daemon[794]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.72" (uid=1000 pid=1493 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.5" (uid=0 pid=792 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined")
Sep 29 13:39:15 Matrix bluetoothd[792]: /org/bluez/hci0/dev_E4_41_22_45_85_0D/sep1/fd3: fd(40) ready
Sep 29 13:39:07 Matrix bluetoothd[792]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to E4:41:22:45:85:0D: Connection timed out (110)
Sep 29 13:38:42 Matrix dbus-daemon[794]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.72" (uid=1000 pid=1493 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.5" (uid=0 pid=792 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined")
Sep 29 13:38:42 Matrix bluetoothd[792]: profiles/audio/avdtp.c:handle_unanswered_req() No reply to Suspend request
Sep 29 13:38:42 Matrix bluetoothd[792]: profiles/audio/avdtp.c:cancel_request() Suspend: Connection timed out (110)
Sep 29 13:30:06 Matrix bluetoothd[792]: /org/bluez/hci0/dev_E4_41_22_45_85_0D/sep1/fd2: fd(40) ready
Sep 29 13:29:58 Matrix bluetoothd[792]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to E4:41:22:45:85:0D: Host is down (112)
Sep 29 13:29:39 Matrix bluetoothd[792]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to E4:41:22:45:85:0D: Connection timed out (110)
Sep 29 13:29:17 Matrix dbus-daemon[794]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.72" (uid=1000 pid=1493 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.5" (uid=0 pid=792 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined")
Sep 29 12:46:23 Matrix bluetoothd[792]: /org/bluez/hci0/dev_E4_41_22_45_85_0D/sep1/fd1: fd(40) ready
Sep 29 12:46:20 Matrix bluetoothd[792]: profiles/audio/avctp.c:avctp_control_confirm() Control: Refusing unexpected connect
Sep 29 12:45:59 Matrix bluetoothd[792]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to E4:41:22:45:85:0D: Host is down (112)
Sep 29 11:38:43 Matrix dbus-daemon[794]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.72" (uid=1000 pid=1493 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.5" (uid=0 pid=792 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined")

I am using a Lenovo ThinkPad X1 Extreme Gen 3, with fully updated Kubuntu 20.10, with KDE plasma 5.19.5 and trying to connect two external Samsung monitors using ThinkPad Thunderbolt 3 dock (gen 1). Both monitors have HDMI cables, I am using a displayport-HDMI adapter for both.

I could a couple of times get both the screens to work on this dock, but once I disconnect the dock and reconnect it, my system seems to forget whatever those settings were. Either one or both screens show up black, they exist are detected, show up in settings and I can drag windows there; but nothing really shows up for the human eye to see, not even the mouse pointer.

The second time it worked was when I switched off the NVidia card rebooted, switched to nvidia card and rebooted again, but same thing happened after disconnecting the dock.

When it works, I have to add a new panel, and widgets again. It shows blank, but I can at least see my mouse pointer; in this case, basically that screen has no widgets/wallpaper. I can add these; but when it doesn't even the mouse pointer does not show up.

I can see the two screens in the settings, re-arrange them; if the middle screen is not working I can drag a window all the way over to left screen through the void. Whether the monitors work or not other peripherals like keyboard, mouse etc seem to work through the dock.

I do not seem to have .config/monitors file; I tried removing .local/share/kscreens but it did not help; it just stopped detecting the monitors even in settings so I added it back.

The monitors work, machine is fine, can display 2 screens and all, cause it sometimes works and cause I have another dock, a DisplayLink enabled dock with which I can use both monitors.

How do I make it work on the thunderbolt dock?

Note: This worked all right in Kubuntu 18.04 LTS.

I am using a fresh install of Kubuntu 18.10, with the default plasma version that comes with it: 5.13.5.

The option in System Settings keeps getting reverted every few minutes. On visiting again, it shows a message meaning that the "Options visible are different from those in effect" and on refreshing, option gets unchecked. Screenshot:

xinput method, xinput --set-button-map 13 1 2 3 5 4 6 7,found in some answers is causing unreliable effect, i.e. some of the apps start working reverse while some work inverted of inverted (i.e. original default).

Xorg method of setting Option "NaturalScrolling" "on" is having no effect.

Is there a reliable, permanent method of setting "natural scrolling" in Kubuntu 18.10?

Update 1: I have seen that some of the options like X config work on boot, but at some point stop working randomly. I have not been able to pinpoint what causes it though (yet).

Update 2: Confirming that my natural scrolling option keeps getting reverted!

I would like to remove all KDE PIM related modules: kmail, calendar, akonadi and the db etc as I am not using them actively. There is no clear documentation on how to uninstall those modules apart from some old discussion board comments which are caught between KDE/plasma 4 and 5.

So how do I safely uninstall PIM modules on ubuntu 18.04 which is plasma 5.12? I was using them and I can see these processes running, if there is a way to completely disable them, that can work too.

I am trying to play screen in a VLC window. (To share-screen on chrome) When I try to capture screen with "Desktop" option it says:

Your input can't be opened: VLC is unable to open the MRL 'screen://'. Check the log for details.

In the popup window. I have tried enabling verbose logs, but nothing gets generated in the logs either. I am using KDE. If it helps, the same used to work when I was running mint+cinnamon on this same machine.

I recently bought a new laptop, a Dell Inspiron 15 7560 i7, and have dual booted Ubuntu Gnome 17.04.

I am facing an issue with the sound card, it just randomly stops working, no sound produced whatsoever. Normally when this happens I am on a headphone or just connected a headphone (like, removed and reconnected etc). The headphone is a standard JBL mic+speaker headphone with a 3.5 audio jack. I have already tried installing alsa, using alsamixer to change volumes, restarting pulseaudio (pulseaudio -k && sudo alsa force-reload) etc. Output of aplay -l:

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

When this happens Ubuntu starts showing some additional HDMI (DisplayPort) devices in Sound settings (screenshot), and headphone option even after removing headphones, these devices are not listed normally. If I restart, it boots and shows a 'Dummy Output' under sound settings. This is how it looks when broken:

The only thing I have seen to work so far is a shutdown, wait, and a startup (not a restart command), that too not guaranteed, but sound does come back again a few restarts later.

Interestingly, if I restart into Windows 10 when it is broken, even Windows does not produce sound, shows a 'red cross' on the speaker icon in system tray. Dell support has already upgraded my BIOS, motherboard drivers and Sound drivers in Windows because of this, but I do not see how that matters, except for BIOS upgrade.

Is this a hardware issue?

Updates:

• I figured out while trying different things that if I use an external sound card, i.e. the digital adaptor for headphones to provide USB connectivity or a USB headphone itself this issue does not occur.
• If before disconnecting the headphones I switch the output device to 'Speakers built-in audio' in settings and then disconnect headphones the issue does not occur. But I have to do this every time; or a shutdown is required. This does not look like a hardware issue based on the two points above. It seems like a software issue. Hoping some update to OS fixes it.

Updates 2:

• When I am trying to do a shutdown to reset audio devices, I am seeing better success when the power is disconnected while this shutdown-restart-cycle.
• I need to switch the output device to built-in and disconnect headphones before closing the lid or the issue occurs on wake.

I bought a new Dell Inspiron 7650, i7 few days ago and dual booted it with Ubuntu 17.04, alongside Windows 10 that came with it.

I am noticing that whenever I wake up the laptop, for a fraction of a second I see some hardware errors on the ui and just before the unlock screen shows up. The error message goes something like this:

mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ee2000000040110a
mce: [Hardware Error]: TSC 0 ADDR fef20000 MISC 43880000086
mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1493996371 SOCKET 0 APIC 0 microcode 42
mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 7: ee2000000040110a
mce: [Hardware Error]: TSC 0 ADDR fef20040 MISC 43880000086
mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1493996371 SOCKET 0 APIC 0 microcode 42

I saw that in "additional drivers" there was some Intel microcode driver listed, I also tried installing it but the error message still shows up every time. What could it be? Is that a hardware issue or kernel?

Here is a photo of the screen:

Update:

I ran all the hardware tests on machine: Dell Support Center tests from windows and the pre-boot tests from BIOS, both pass. Windows event viewer does not show any error logs related to this, when I sleep/wake it. Raised a dell support request, the support person told me that this error is due to some issue with 'drivers' in Ubuntu and happens only when we dual-boot Windows 10 and Ubuntu. I could choose to remove Windows completely and install only Ubuntu, then it should go away and they could schedule a support call for it, but post that the support will be very limited (since Linux!). Also, that they have raised this with Ubuntu developers / Intel and they are working on this issue and I should watch for an update to OS that fixes this (could not get a link to the issue report.)

Essentially, there seems like no solution to this for now. If it is a false positive, is there a way I can at least hide this from showing up on each wake?

When I am running a fullscreen application, for example the game SPAZ from the HumbleBundle 6, if some popup comes or if I press the super key to come back to desktop and minimize the game, I am unable to play the game again. The game just wont lock my mouse again, I am sometimes able to get it to become fullscreen again (no idea exactly how!), but the mouse just wont get locked.. Any idea how to continue the game without exit and restart?