[Desktop-packages] [Bug 1925742] [NEW] IMAP broken in Evolution
Public bug reported: There is a recently introduced bug in evolution-data-server which broke access to email in iCloud. The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: IMAP broken in Evolution Status in evolution-data-server package in Ubuntu: New Bug description: There is a recently introduced bug in evolution-data-server which broke access to email in iCloud. The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1922839] Re: Opening new tab in gnome-terminal launched from nautilus loses most environment variables
** Changed in: gnome-terminal (Ubuntu Hirsute) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1922839 Title: Opening new tab in gnome-terminal launched from nautilus loses most environment variables Status in gnome-terminal package in Ubuntu: New Status in gnome-terminal source package in Hirsute: New Bug description: [Impact] If you launch gnome-terminal by right clicking a directory in Nautilus, selecting "Open in Terminal", you get a fully functional terminal window. If you then press the new tab button, or ctrl-shift-t to open a new terminal tab, you will find that most environment variables have become unset, and you see the text: To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. Comparing printenv between: Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/ Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/ Most commands won't run in the new terminal tab, due to $HOME and $USER not being set. Note, if you launch gnome-terminal from gnome-shell or the dock, and create a new tab, everything works perfectly. Is something wrong with the Nautilus option for "Open in Terminal"? [Testcase] 1. Launch Nautilus to home directory 2. Right click > "Open in Terminal" 3. Run "printenv" to see full list of env variables 4. Click new tab button, or ctrl-shift-t 5. Run "printenv" see the lack of env variables I have a test package available in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1922839-test The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac reverted. If you install this package, environment variables will be set correctly. [Where problems could occur] I think there is some risk with re-instating a commit which has been reverted, and users could run into similar issues as found in the upstream bug. We do have some supporting evidence that the commit isn't too harmful, since it is applied to Groovy currently, things work as intended there, and users haven't complained about the issues in the upstream bug applying to Groovy. If a regression were to occur, then launching a new gnome-terminal or opening a new tab could land the user with a terminal with little to no environment variables set. A workaround will be to launch gnome- terminal from gnome-shell overview. [Other info] Focal and Groovy have the following commit applied: commit fd5ac772154426e2da5afd633b336414bca33be9 Author: Christian Persch Date: Mon Mar 23 09:57:56 2020 +0100 Subject: screen: Use clean env when creating new tab Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/fd5ac772154426e2da5afd633b336414bca33be9 This was then reverted in 3.38.1 due to the upstream bug: https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253 The reverted commit is: commit 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac Author: Christian Persch Date: Thu Sep 17 17:10:47 2020 +0200 Subject: Revert "screen: Use clean env when creating new tab" Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac This revert seems to have broken Hirsute. If we revert the revert, that is, apply the commit again, things work as intended. To fix this, we need to re-apply fd5ac772154426e2da5afd633b336414bca33be9. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1922839/+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 1918855] Re: Xorg xserver got signal 6 to abort
Test pass with newer mesa version from oibaf ppa. libegl-mesa0:amd64 21.2~git2104200600.4a384f~oibaf~h libgbm1:amd64 21.2~git2104200600.4a384f~oibaf~h libgl1-mesa-dri:amd64 21.2~git2104200600.4a384f~oibaf~h libglapi-mesa:amd64 21.2~git2104200600.4a384f~oibaf~h libglx-mesa0:amd64 21.2~git2104200600.4a384f~oibaf~h libxatracker2:amd64 21.2~git2104200600.4a384f~oibaf~h mesa-vulkan-drivers:amd64 21.2~git2104200600.4a384f~oibaf~h -- 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/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+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 1925739] [NEW] I get sound for no resone
Public bug reported: when everything is off even sound is muted I am getting sound like connecting 3.5mm jack. It's not sure why this sound is coming to my headphone. It's coming unevenly few seconds later. It's not case with ubuntu 20.10 usb stick. It begin when I upgrade pkgs. ubuntu 20.10 all updated. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Description changed: - when everything is off even sound is muted I am getting sound like connecting 3.5mm jack. It's not sure why this sound is coming to my headphone. It's coming unevenly few seconds later. + when everything is off even sound is muted I am getting sound like connecting 3.5mm jack. It's not sure why this sound is coming to my headphone. It's coming unevenly few seconds later. It's not case with ubuntu 20.10 usb stick. It begin when I upgrade pkgs. ubuntu 20.10 all updated. -- 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/1925739 Title: I get sound for no resone Status in pulseaudio package in Ubuntu: New Bug description: when everything is off even sound is muted I am getting sound like connecting 3.5mm jack. It's not sure why this sound is coming to my headphone. It's coming unevenly few seconds later. It's not case with ubuntu 20.10 usb stick. It begin when I upgrade pkgs. ubuntu 20.10 all updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1925739/+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 1925379] Re: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4
** Summary changed: - Auto-Correct does not work since upgrade to Hirsute + Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4 ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- 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/1925379 Title: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4 Status in gtk+3.0 package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, same LibreOffice profile, same LibreOffice document, and no changes on my part to my LibreOffice settings since I installed Ubuntu 21.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1925379/+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 1925733] [NEW] Syslog file exeeds 19GB and registers millions of entries per hour
Public bug reported: Syslog repeatedly saves this and flooding the system space Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx org.gnome.Shell.desktop[1932]: #4 0x7ffd6a29ba00 I self-hosted:914 (0x7f3d41ef12b8 @ 346) Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx gnome-shell[1932]: clutter_actor_get_n_children: assertion 'CLUTTER_IS_ACTOR (self)' failed Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx gnome-shell[1932]: Object Clutter.Actor (0x55ff0cfbf750), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx gnome-shell[1932]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx gnome-shell[1932]: Object Clutter.Actor (0x55ff1272e470), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx gnome-shell[1932]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx gnome-shell[1932]: Object Clutter.Actor (0x55ff1272e470), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx gnome-shell[1932]: clutter_actor_get_n_children: assertion 'CLUTTER_IS_ACTOR (self)' failed Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx gnome-shell[1932]: Object Clutter.Actor (0x55ff1272e470), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx gnome-shell[1932]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx gnome-shell[1932]: Object Clutter.Actor (0x55ff1272f850), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx gnome-shell[1932]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx gnome-shell[1932]: Object Clutter.Actor (0x55ff1272f850), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx gnome-shell[1932]: clutter_actor_get_n_children: assertion 'CLUTTER_IS_ACTOR (self)' failed Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx gnome-shell[1932]: Object Clutter.Actor (0x55ff1272f850), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx gnome-shell[1932]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx gnome-shell[1932]: Object Clutter.Actor (0x55ff0cfbf750), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx org.gnome.Shell.desktop[1932]: == Stack trace for context 0x55ff04a9f340 == Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx org.gnome.Shell.desktop[1932]: #0 0x7ffd6a29b920 I resource:///org/gnome/shell/ui/animation.js:53 (0x7f3d41913bc0 @ 41) Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx org.gnome.Shell.desktop[1932]: #1 0x7ffd6a29b980 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f3d41eb5de0 @ 71) Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx org.gnome.Shell.desktop[1932]: #2 0x7ffd6a29b980 I resource:///org/gnome/shell/ui/animation.js:65 (0x7f3d41913c48 @ 28) Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx org.gnome.Shell.desktop[1932]: #3 0x7ffd6a29ba00 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f3d41eb5de0 @ 71) Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx org.gnome.Shell.desktop[1932]: #4 0x7ffd6a29ba00 I self-hosted:914 (0x7f3d41ef12b8 @ 346) Apr 22 15:53:10 shadowfox-OMEN-by-HP-Laptop-15-dc0xxx org.gnome.Shell.desktop[1932]: == Stack trace for context 0x55ff04a9f340 == Apr 22 1
[Desktop-packages] [Bug 1925726] Re: Fx was not updated a whole week
*** This bug is a duplicate of bug 1925188 *** https://bugs.launchpad.net/bugs/1925188 ** This bug has been marked a duplicate of bug 1925188 Mozilla Firefox Multiple Vulnerabilities -- 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/1925726 Title: Fx was not updated a whole week Status in firefox package in Ubuntu: New Bug description: FX release 88 was on Monday, 19-Apr-2021 06:18 Now, Friday 23-Apr-2021 there is still no update available. As hardcore Fx user this is a real problem cause of the two problematic "High"-Lücken CVE-2021-23994 and CVE-2021-23995. ---> so Fx cannot used for security critical work from monday till now (5 days +) . ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: firefox 87.0+build3-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: frank 1736 F pulseaudio /dev/snd/controlC0: frank 1736 F pulseaudio BuildID: 20210318103112 CasperMD5CheckResult: skip Channel: Unavailable Date: Fri Apr 23 06:58:31 2021 ForcedLayersAccel: False InstallationDate: Installed on 2020-12-28 (115 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.0.1 dev enp6s0 proto static metric 100 169.254.0.0/16 dev enp6s0 scope link metric 1000 192.168.0.0/24 dev enp6s0 proto kernel scope link src 192.168.0.6 metric 100 NoProfiles: True ProcEnviron: LANGUAGE=de_DE TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to groovy on 2020-12-30 (113 days ago) dmi.bios.date: 03/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X570-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd03/19/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX570-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1925726/+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 1925732] [NEW] new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal
Public bug reported: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. ** Affects: ubuntu Importance: Undecided Status: New ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal Status in Ubuntu: New Status in gnome-terminal package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1925732/+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 1925730] [NEW] Dell XPS 17 (Ubuntu 21.04) - No sound AT ALL upon fresh installation
Public bug reported: New laptop - Dell XPS 17, bought in 2020. Upon installation of Ubuntu 21.04 sound does not work at all. System settings only show one audio output - "Dummy output". Audio input does not have even that, just an empty drop-down list. Issue can be fixed if we load a custom sound driver as described here: https://blog.fts.scot/2020/07/04/dell-xps-2020-how-to-get-audio-working- on-linux/ That poses a security risk however and according to the author of the article is not necessary since mainline Kernel release 5.11 now has required device headers included. ... lspci output: user@MYPC:~$ lspci -v | grep -i -A 10 audio 00:1f.3 Multimedia audio controller: Intel Corporation Comet Lake PCH cAVS Subsystem: Dell Comet Lake PCH cAVS Flags: bus master, fast devsel, latency 64, IRQ 229, IOMMU group 16 Memory at 609b218000 (64-bit, non-prefetchable) [size=16K] Memory at 609b10 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: sof-audio-pci Kernel modules: snd_hda_intel, snd_sof_pci -- 01:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio Controller (rev a1) Subsystem: Dell TU106 High Definition Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 17, IOMMU group 1 Memory at 7300 (32-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel Looked around for soundwire drivers, found this: user@MYPC:~$ lsmod | grep soundwire soundwire_intel40960 2 snd_sof_intel_hda_common,snd_intel_dspcfg soundwire_generic_allocation16384 1 soundwire_intel soundwire_cadence 32768 1 soundwire_intel soundwire_bus 77824 7 regmap_sdw,soundwire_intel,snd_soc_rt715,soundwire_generic_allocation,soundwire_cadence,snd_soc_rt711,snd_soc_rt1308_sdw snd_soc_core 294912 8 soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_rt715,snd_soc_hdac_hda,snd_soc_rt711,snd_soc_dmic,snd_soc_rt1308_sdw snd_pcm 118784 14 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_sof_intel_ipc,snd_soc_rt715,snd_compress,snd_soc_core,snd_soc_rt711,snd_soc_rt1308_sdw,snd_hda_core,snd_pcm_dmaengine Maybe using the soundwire_intel driver would fix the problem? Need to keep digging. Will post an update if I have any progress. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iamarkadyt 1593 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 00:18:15 2021 InstallationDate: Installed on 2021-04-23 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: TU106 High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iamarkadyt 1593 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA NVidia, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2020 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0YK6XT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd09/03/2020:br1.4:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0YK6XT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- 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/1925730 Title: Dell XPS 17 (Ubuntu 21.04) - No sound AT ALL upon fresh installation Status in alsa-driver package in Ubuntu: New Bug description: New laptop - Dell XPS 17, bought in 2020. Upon installation of Ubuntu 21.04 sound does not work at all. System settings only show one audio output - "Dummy output". Audio input does not have even that, just an empty drop-down list. Issue can be fixed if we load a custom sound driver as described here: https://blog.fts.scot/2020/07/04/dell-xps-2020-how-to-get-audio- working-on-linux/ That poses a security risk however and according to the autho
[Desktop-packages] [Bug 1925726] [NEW] Fx was not updated a whole week
Public bug reported: FX release 88 was on Monday, 19-Apr-2021 06:18 Now, Friday 23-Apr-2021 there is still no update available. As hardcore Fx user this is a real problem cause of the two problematic "High"-Lücken CVE-2021-23994 and CVE-2021-23995. ---> so Fx cannot used for security critical work from monday till now (5 days +) . ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: firefox 87.0+build3-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: frank 1736 F pulseaudio /dev/snd/controlC0: frank 1736 F pulseaudio BuildID: 20210318103112 CasperMD5CheckResult: skip Channel: Unavailable Date: Fri Apr 23 06:58:31 2021 ForcedLayersAccel: False InstallationDate: Installed on 2020-12-28 (115 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.0.1 dev enp6s0 proto static metric 100 169.254.0.0/16 dev enp6s0 scope link metric 1000 192.168.0.0/24 dev enp6s0 proto kernel scope link src 192.168.0.6 metric 100 NoProfiles: True ProcEnviron: LANGUAGE=de_DE TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to groovy on 2020-12-30 (113 days ago) dmi.bios.date: 03/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X570-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd03/19/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX570-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1925726 Title: Fx was not updated a whole week Status in firefox package in Ubuntu: New Bug description: FX release 88 was on Monday, 19-Apr-2021 06:18 Now, Friday 23-Apr-2021 there is still no update available. As hardcore Fx user this is a real problem cause of the two problematic "High"-Lücken CVE-2021-23994 and CVE-2021-23995. ---> so Fx cannot used for security critical work from monday till now (5 days +) . ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: firefox 87.0+build3-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: frank 1736 F pulseaudio /dev/snd/controlC0: frank 1736 F pulseaudio BuildID: 20210318103112 CasperMD5CheckResult: skip Channel: Unavailable Date: Fri Apr 23 06:58:31 2021 ForcedLayersAccel: False InstallationDate: Installed on 2020-12-28 (115 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.0.1 dev enp6s0 proto static metric 100 169.254.0.0/16 dev enp6s0 scope link metric 1000 192.168.0.0/24 dev enp6s0 proto kernel scope link src 192.168.0.6 metric 100 NoProfiles: True ProcEnviron: LANGUAGE=de_DE TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to groovy on 2020-12-30 (113 days ago) dmi.bios.date: 03/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X570-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string
[Desktop-packages] [Bug 1849478] Re: [snap] (experimental) pipewire support not available
[continuing] This is bad, since Ubuntu 21.04 switches from Xorg to Wayland by default which effectively disables screen sharing on Chromium. User needs to go back to Xorg to enable screen sharing on Chromium, which is a bit of a pity since pipewire is already in place and ready to be used. -- 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/1849478 Title: [snap] (experimental) pipewire support not available Status in chromium-browser package in Ubuntu: Confirmed Bug description: I'm using the chromium snap (currently 77.0.3865.120, rev 899), it's not possible to enable experimental support for pipewire, as the toggle doesn't show up in chrome://flags. It would be nice to have chromium compiled with pipewire support, to enable screensharing in Hangouts and similar apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849478/+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 1849478] Re: [snap] (experimental) pipewire support not available
Starting from Ubuntu 21.04 the pipewire libs are bundled in Ubuntu itself, to allow screen sharing over webrtc. This allows Firefox to cast screen properly, which is great :) However, since the Chromium snap is missing the pipewire support (currently 90.0.4430.85), it's not possible to set the flag chrome://flags/#enable-webrtc-pipewire-capturer to true, which effectively disables screen sharing on Chromium. -- 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/1849478 Title: [snap] (experimental) pipewire support not available Status in chromium-browser package in Ubuntu: Confirmed Bug description: I'm using the chromium snap (currently 77.0.3865.120, rev 899), it's not possible to enable experimental support for pipewire, as the toggle doesn't show up in chrome://flags. It would be nice to have chromium compiled with pipewire support, to enable screensharing in Hangouts and similar apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849478/+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 1913570] Re: Firefox not opening file chooser dialog for importing certificates
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1913570 Title: Firefox not opening file chooser dialog for importing certificates Status in firefox package in Ubuntu: Expired Bug description: When installed as a snap, firefox won't open the file chooser dialog for importing a certificate authority. However, it is working when installed using apt. How to reproduce: 1. Install firefox as snap 2. Navigate to Preferences | Privacy & Security | Certificates | View Certificates 3. Select Authorities 4. Click Import ... -> A file selector dialog should open to import a certificate, but nothing happens. Environment: ProblemType: Bug ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Thu Jan 28 11:43:55 2021 DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-01-15 (12 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 (20210115) ProcCpuinfoMinimal: processor: 3 vendor_id: GenuineIntel cpu family : 6 model: 42 model name : Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz stepping : 7 microcode: 0x2f cpu MHz : 3701.000 cache size : 8192 KB physical id : 6 siblings : 1 core id : 0 cpu cores: 1 apicid : 6 initial apicid : 6 fpu : yes fpu_exception: yes cpuid level : 13 wp : yes flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc arch_perfmon nopl xtopology tsc_reliable nonstop_tsc cpuid pni pclmulqdq ssse3 cx16 pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx hypervisor lahf_lm pti ssbd ibrs ibpb stibp tsc_adjust arat md_clear flush_l1d arch_capabilities bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit bogomips : 7402.00 clflush size : 64 cache_alignment : 64 address sizes: 43 bits physical, 48 bits virtual power management: ProcEnviron: SHELL=/bin/bash LANGUAGE=en_US LC_ADDRESS=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_PAPER=de_DE.UTF-8 LANG=en_US.UTF-8 TERM=xterm-256color LC_IDENTIFICATION=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 XDG_RUNTIME_DIR= LC_TIME=de_DE.UTF-8 PATH=(custom, no user) LC_NUMERIC=de_DE.UTF-8 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Snap: firefox 84.0.2-1 (stable) Tags: hirsute Uname: Linux 5.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1913570/+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
Re: [Desktop-packages] [Bug 1820859] Re: nautilus --version segfaults in g_application_impl_get_dbus_object_path
Don't get the crash any longer. Den tors 22 apr. 2021 kl 16:41 skrev Launchpad Bug Tracker < 1820...@bugs.launchpad.net>: > This bug was fixed in the package nautilus - 1:3.38.2-1ubuntu2 > > --- > nautilus (1:3.38.2-1ubuntu2) hirsute; urgency=medium > > * d/p/19_unity_open_location_xid: > - Do not update opened locations on bus connection. > Nautilus may connect to the bus when the application is already about > shut down, however at that point its implementation is destroyed but > Gio doesn't handle this gracefully as per GNOME/GLib!2056. > To prevent this, we can safely reduce the delta of the distro-patch > by > avoiding updating the opened locations on bus acquired, as we > already do > it in all the cases a window actually changes its state. (LP: > #1820859) > > -- Marco Trevisan (Treviño) Wed, 21 Apr 2021 > 07:03:29 +0200 > > ** Changed in: nautilus (Ubuntu Hirsute) >Status: Fix Committed => Fix Released > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1820859 > > Title: > nautilus --version segfaults in > g_application_impl_get_dbus_object_path > > Status in nautilus package in Ubuntu: > Fix Released > Status in nautilus source package in Hirsute: > Fix Released > > Bug description: > * Impact > > nautilus hits a segfault when called with the version argument, which > was annoying but became problematic in hirsute since the desktop icons > ng calls that command to check if nautilus is available > > * Test case > > $ nautilus --version > shouldn't segfault > > * Regression potential > > The change is in a patch which was added to expose open locations to > Unity for the benefit of the launcher and which is also used by the > dashtodock one now. Check that the launcher correctly indicates which > windows are active, especially when dealing with external devices. > > -- > > > The Ubuntu Error Tracker has been receiving reports about a problem > regarding nautilus. This problem was most recently seen with package > version 1:3.31.90-1ubuntu2, the problem page at > https://errors.ubuntu.com/problem/8a8c9fc62039a8bb83a7ee530ac4140a9b8c29d9 > 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/ubuntu/+source/nautilus/+bug/1820859/+subscriptions > -- Skickat från min Sony Xperia eller Ubuntu -- 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/1820859 Title: nautilus --version segfaults in g_application_impl_get_dbus_object_path Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Hirsute: Fix Released Bug description: * Impact nautilus hits a segfault when called with the version argument, which was annoying but became problematic in hirsute since the desktop icons ng calls that command to check if nautilus is available * Test case $ nautilus --version shouldn't segfault * Regression potential The change is in a patch which was added to expose open locations to Unity for the benefit of the launcher and which is also used by the dashtodock one now. Check that the launcher correctly indicates which windows are active, especially when dealing with external devices. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.31.90-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/8a8c9fc62039a8bb83a7ee530ac4140a9b8c29d9 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/ubuntu/+source/nautilus/+bug/1820859/+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 1875592] Re: Xorg: High CPU usage when USB mic is plugged in after hibernation
@klobalaccel5: I've never heard of this, so I'd say "no" here. @.Xmodmap: Not consciously. Maybe my (XUbuntu) system uses it in the background. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1875592 Title: Xorg: High CPU usage when USB mic is plugged in after hibernation Status in xorg-server package in Ubuntu: New Bug description: Problem: = When I plug in a USB microphone after one, two or three hibernations with work in between* the Xorg process is "going crazy" at around 100% - 130% CPU usage. (please see the attached chart) Steps (to hopefulle reproduce): === - start pc - do some usual work for a couple of hours - hibernate - wake up - do some usual work for a couple of hours - hibernate - wake up ( you might need more repetitions here) - do some usual work for a couple of hours - plug in USB microphone Actual: - Xorg has high CPU usage Expected: - Xorg has usual CPU usage Remarks = I could not safely reproduce this behaviour on purpose simply by starting and hibernating. But I experience it on a week to week basis. I'm not suspending or some kind of suspend+hibernate. It's pure hibernation I experience this problem, I think, in 16 (started here), (never tried 17), 18, 19.10 I used perftop with flamegraph the other day. It revealed - DeletePassiveGrabFromList with 3 ~ 5% - ResourceClientBits: around 5% - GrabMatchesSecond: 3 ~ 5% - trace_raw_output_kvm_inj_virq: around 7 ~ 8% System === lsb_release -rd --- Description: Ubuntu 19.10 Release: 19.10 apt-cache policy xorg -- xorg: Installed: 1:7.7+19ubuntu12 Candidate: 1:7.7+19ubuntu12 Version table: *** 1:7.7+19ubuntu12 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Misc - 12GB RAM - Core i5 4 cores Debugging -- I can help collecting data, but I need assistance ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Apr 28 17:29:02 2020 DistUpgraded: 2019-12-01 10:19:03,497 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-40-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. UHD Graphics 620 [10cf:1959] MachineType: FUJITSU FMVWB3U27 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=fe637d00-125b-4a54-adce-3711830d450b ro pci=nomsi acpi_osi=Linuxs resume=UUID=8fa6d40f-c23d-497e-9846-f6f26536690d SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-12-01 (149 days ago) dmi.bios.date: 01/23/2018 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.07 dmi.board.name: FJNB2BB dmi.board.vendor: FUJITSU dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWB3U27 dmi.sys.vendor: FUJITSU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1875592/+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 1925467] Re: stack-buffer-overflow of text.c in function _import_ansi
** Description changed:
Hello ubuntu security team
+
+ issues: https://github.com/cacalabs/libcaca/issues/55
+
System info：
Ubuntu 20.04 : clang 10.0.0 , gcc 9.3.0
Fedora 33: clang 11.0.0 , gcc 10.2.1
libcaca version e4968ba
Verification steps：
1.Get the source code of libcaca
2.Compile the libcaca.so library
$ cd libcaca
$ ./bootstrap
$ ./configure
$ make
or
$ cd libcaca
$ ./bootstrap
$ ../configure CC="clang -O2 -fno-omit-frame-pointer -g
-fsanitize=address,fuzzer-no-link -fsanitize-coverage=bb" CXX="clang++ -O2
-fno-omit-frame-pointer -g -fsanitize=address,fuzzer-no-link
-fsanitize-coverage=bb"
$ make
3.Create the poc_ansi.cc && build
#include "config.h"
#include "caca.h"
//#include "common-image.h"
#include
#include
#include
#include
#include
#include
using namespace std;
void crash(const uint8_t *Data, size_t Size) {
- if(Size<8) return ;
- size_t len=0;
- caca_canvas_t *cv;
- cv = caca_create_canvas(0,0);
- caca_create_frame(cv,0);
- caca_set_frame(cv,0);
- caca_import_canvas_from_memory(cv,Data,Size,"ansi");
- caca_free_canvas(cv);
- cv=NULL;
+ if(Size<8) return ;
+ size_t len=0;
+ caca_canvas_t *cv;
+ cv = caca_create_canvas(0,0);
+ caca_create_frame(cv,0);
+ caca_set_frame(cv,0);
+ caca_import_canvas_from_memory(cv,Data,Size,"ansi");
+ caca_free_canvas(cv);
+ cv=NULL;
}
-
int main(int args,char* argv[]){
- size_t len = 0;
- unsigned char buffer[] =
{0x20,0x4a,0x0c,0x0a,0x20,0x0a,0x20,0x0c,0xc,0xc};
- len = sizeof(buffer)/sizeof(unsigned char);
- printf("%d\n",sizeof(buffer)/sizeof(unsigned char));
- crash((const uint8_t*)buffer,len);
+ size_t len = 0;
+ unsigned char buffer[] =
{0x20,0x4a,0x0c,0x0a,0x20,0x0a,0x20,0x0c,0xc,0xc};
+ len = sizeof(buffer)/sizeof(unsigned char);
+ printf("%d\n",sizeof(buffer)/sizeof(unsigned char));
+ crash((const uint8_t*)buffer,len);
- return 0;
+ return 0;
}
4.compile poc_ansi.cc
clang++ -g poc_ansi.cc -O2 -fno-omit-frame-pointer -fsanitize=address
-I./caca/ -lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/ -o poc_ansi
5.Run poc_ansi
asan info:
=
==3763372==ERROR: AddressSanitizer: stack-buffer-overflow on address
0x7ffda0164bea at pc 0x7f098d82c310 bp 0x7ffda01647b0 sp 0x7ffda01647a8
READ of size 1 at 0x7ffda0164bea thread T0
- #0 0x7f098d82c30f in _import_ansi
/home/hh/Downloads/libcaca/caca/codec/text.c:391:38
- #1 0x4c6c72 in crash(unsigned char const*, unsigned long)
/home/hh/Downloads/libcaca/poc_bin.cc:21:3
- #2 0x4c6c72 in main /home/hh/Downloads/libcaca/poc_bin.cc:34:9
- #3 0x7f098d2780b2 in __libc_start_main
/build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16
- #4 0x41c38d in _start (/home/hh/Downloads/libcaca/poc_mbay+0x41c38d)
+ #0 0x7f098d82c30f in _import_ansi
/home/hh/Downloads/libcaca/caca/codec/text.c:391:38
+ #1 0x4c6c72 in crash(unsigned char const*, unsigned long)
/home/hh/Downloads/libcaca/poc_bin.cc:21:3
+ #2 0x4c6c72 in main /home/hh/Downloads/libcaca/poc_bin.cc:34:9
+ #3 0x7f098d2780b2 in __libc_start_main
/build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16
+ #4 0x41c38d in _start (/home/hh/Downloads/libcaca/poc_mbay+0x41c38d)
Address 0x7ffda0164bea is located in stack of thread T0 at offset 42 in frame
- #0 0x4c6b9f in main /home/hh/Downloads/libcaca/poc_bin.cc:28
+ #0 0x4c6b9f in main /home/hh/Downloads/libcaca/poc_bin.cc:28
- This frame has 1 object(s):
- [32, 42) 'buffer' (line 31) <== Memory access at offset 42 overflows this
variable
+ This frame has 1 object(s):
+ [32, 42) 'buffer' (line 31) <== Memory access at offset 42 overflows this
variable
HINT: this may be a false positive if your program uses some custom stack
unwind mechanism, swapcontext or vfork
- (longjmp and C++ exceptions *are* supported)
+ (longjmp and C++ exceptions *are* supported)
SUMMARY: AddressSanitizer: stack-buffer-overflow
/home/hh/Downloads/libcaca/caca/codec/text.c:391:38 in _import_ansi
Shadow bytes around the buggy address:
- 0x100034024920: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
- 0x100034024930: f8 f8 f8 f8 f8 f8 f8 f8 f8 f2 f2 f2 f2 f2 f2 f2
- 0x100034024940: f2 f2 f8 f2 f2 f2 f8 f3 f3 f3 f3 f3 00 00 00 00
- 0x100034024950: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
- 0x100034024960: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
+ 0x100034024920: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
+ 0x100034024930: f8 f8 f8 f8 f8 f8 f8 f8 f8 f2 f2 f2 f2 f2 f2 f2
+ 0x100034024940: f2 f2 f8 f2 f2 f2 f8 f3 f3 f3 f3 f3 00 00 00 00
+ 0x100034024950: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
+ 0x100034024960: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x100034024970: 0
[Desktop-packages] [Bug 1925468] Re: stack-buffer-overflow of import.c in function _import_bin
** Description changed:
Hello ubuntu security team
+
+ issues：https://github.com/cacalabs/libcaca/issues/56
+
System info：
Ubuntu 20.04 : clang 10.0.0 , gcc 9.3.0
Fedora 33: clang 11.0.0 , gcc 10.2.1
+
libcaca version e4968ba
Verification steps：
1.Get the source code of libcaca
2.Compile the libcaca.so library
$ cd libcaca
$ ./bootstrap
$ ./configure
$ make
or
$ cd libcaca
$ ./bootstrap
$ ../configure CC="clang -O2 -fno-omit-frame-pointer -g
-fsanitize=address,fuzzer-no-link -fsanitize-coverage=bb" CXX="clang++ -O2
-fno-omit-frame-pointer -g -fsanitize=address,fuzzer-no-link
-fsanitize-coverage=bb"
$ make
3.Create the poc_bin.cc && build
#include "config.h"
#include "caca.h"
//#include "common-image.h"
#include
#include
#include
#include
#include
#include
using namespace std;
void crash(const uint8_t *Data, size_t Size) {
- if(Size<8) return ;
- size_t len=0;
- caca_canvas_t *cv;
- cv = caca_create_canvas(0,0);
- caca_create_frame(cv,0);
- caca_set_frame(cv,0);
- caca_import_canvas_from_memory(cv,Data,Size,"bin");
- caca_free_canvas(cv);
- cv=NULL;
+ if(Size<8) return ;
+ size_t len=0;
+ caca_canvas_t *cv;
+ cv = caca_create_canvas(0,0);
+ caca_create_frame(cv,0);
+ caca_set_frame(cv,0);
+ caca_import_canvas_from_memory(cv,Data,Size,"bin");
+ caca_free_canvas(cv);
+ cv=NULL;
}
int main(int args,char* argv[]){
- size_t len = 0;
- unsigned char buffer[] =
{0x0a,0x20,0x0a,0x0a,0x20,0x20,0x20,0x20,0x20,0x20,0x47,0x47,0x47};
- len = sizeof(buffer)/sizeof(unsigned char);
- printf("%d\n",sizeof(buffer)/sizeof(unsigned char));
- crash((const uint8_t*)buffer,len);
- return 0;
+ size_t len = 0;
+ unsigned char buffer[] =
{0x0a,0x20,0x0a,0x0a,0x20,0x20,0x20,0x20,0x20,0x20,0x47,0x47,0x47};
+ len = sizeof(buffer)/sizeof(unsigned char);
+ printf("%d\n",sizeof(buffer)/sizeof(unsigned char));
+ crash((const uint8_t*)buffer,len);
+ return 0;
}
4.compile poc_bin.cc
clang++ -g poc_bin.cc -O2 -fno-omit-frame-pointer -fsanitize=address
-I./caca/ -lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/ -o poc_bin
5.Run poc_bin
asan info:
=
==3817476==ERROR: AddressSanitizer: stack-buffer-overflow on address
0x7ffe7cd3774d at pc 0x7f8c6314acfd bp 0x7ffe7cd376c0 sp 0x7ffe7cd376b8
READ of size 1 at 0x7ffe7cd3774d thread T0
- #0 0x7f8c6314acfc in _import_bin
/home/hh/Downloads/libcaca/caca/codec/import.c:425:33
- #1 0x4c6c72 in crash(unsigned char const*, unsigned long)
/home/hh/Downloads/libcaca/poc_bin.cc:21:3
- #2 0x4c6c72 in main /home/hh/Downloads/libcaca/poc_bin.cc:34:9
- #3 0x7f8c62ba00b2 in __libc_start_main
/build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16
- #4 0x41c38d in _start (/home/hh/Downloads/libcaca/poc_bin+0x41c38d)
+ #0 0x7f8c6314acfc in _import_bin
/home/hh/Downloads/libcaca/caca/codec/import.c:425:33
+ #1 0x4c6c72 in crash(unsigned char const*, unsigned long)
/home/hh/Downloads/libcaca/poc_bin.cc:21:3
+ #2 0x4c6c72 in main /home/hh/Downloads/libcaca/poc_bin.cc:34:9
+ #3 0x7f8c62ba00b2 in __libc_start_main
/build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16
+ #4 0x41c38d in _start (/home/hh/Downloads/libcaca/poc_bin+0x41c38d)
Address 0x7ffe7cd3774d is located in stack of thread T0 at offset 45 in frame
- #0 0x4c6b9f in main /home/hh/Downloads/libcaca/poc_bin.cc:28
+ #0 0x4c6b9f in main /home/hh/Downloads/libcaca/poc_bin.cc:28
- This frame has 1 object(s):
- [32, 45) 'buffer' (line 31) <== Memory access at offset 45 overflows this
variable
+ This frame has 1 object(s):
+ [32, 45) 'buffer' (line 31) <== Memory access at offset 45 overflows this
variable
HINT: this may be a false positive if your program uses some custom stack
unwind mechanism, swapcontext or vfork
- (longjmp and C++ exceptions *are* supported)
+ (longjmp and C++ exceptions *are* supported)
SUMMARY: AddressSanitizer: stack-buffer-overflow
/home/hh/Downloads/libcaca/caca/codec/import.c:425:33 in _import_bin
Shadow bytes around the buggy address:
- 0x10004f99ee90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
- 0x10004f99eea0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
- 0x10004f99eeb0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
- 0x10004f99eec0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
- 0x10004f99eed0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
+ 0x10004f99ee90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
+ 0x10004f99eea0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
+ 0x10004f99eeb0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
+ 0x10004f99eec0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
+ 0x10004f99eed0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[Desktop-packages] [Bug 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Forget about the messages that I show in the previous post: it seems
that this problem is also happening in Ubuntu 20.10 groovy and are
unrelated to the original bug. I didn't realize these messages before
because in groovy these messages are way less informative than in
hirsute. In groovy it only show:
abr 23 02:45:40 fpglinux gnome-shell[1730]: value "nan" of type 'gfloat' is
invalid or out of range for property 'x' of type 'gfloat'
abr 23 02:45:40 fpglinux gnome-shell[1730]: value "nan" of type 'gfloat' is
invalid or out of range for property 'y' of type 'gfloat'
abr 23 02:45:40 fpglinux gnome-shell[1730]: value "-inf" of type 'gfloat' is
invalid or out of range for property 'width' of type 'gfloat'
abr 23 02:45:40 fpglinux gnome-shell[1730]: value "-inf" of type 'gfloat' is
invalid or out of range for property 'height' of type 'gfloat'
So it's probably happening since ages...
Thank you very much for the quick fix and happy releasing.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1923267
Title:
Gjs promises on Gio.File operations don't work anymore after upgrading
libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Status in gjs package in Ubuntu:
Fix Committed
Status in gnome-shell-extension-appindicator package in Ubuntu:
Won't Fix
Status in gjs source package in Hirsute:
Fix Committed
Bug description:
[ Impact ]
As per glib commit
https://gitlab.gnome.org/GNOME/glib/-/commit/d52728f99
Gio.File.new_for_path("") returns a GDummyFile implementation, while
Gio._promisify relies on it being a LocalFile, so we don't promisify
the right methods.
[ Test case ]
gjs -c "imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype,
'delete_async', 'delete_finish');
print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" &&
echo GJS works
Should write on terminal:
[object Promise]
GJS works
In the bugged version would instead just:
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: JS ERROR: TypeError: method
Gio.File.delete_async: At least 3 arguments required, but only 2 passed
@:2:48
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: Script
threw an exception
[ Regression potential ]
Gjs apps are slower in starting up, or not act properly when / is not
a local location.
---
Problem tested in two different environments:
- Ubuntu 21.04 Beta amd64
- Ubuntu 21.04 Beta arm64 (Raspberry Pi 4B 8GB)
After upgrading these packages:
libglib2.0-02.67.5-2 to 2.68.0-1
libglib2.0-bin 2.67.5-2 to 2.68.0-1
libglib2.0-data 2.67.5-2 to 2.68.0-1
The app indicator-multiload (0.4-0ubuntu5) doesn't work showing only
three dots (...) instead of the graphic expected. It's throwing error
messages to the system journal every second or so (depends of the
refresh interval selected in the app settings):
abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]:
multiload, Impossible to read image from path '/run/user/1026
/multiload-icons-Wc8kck/icons/indicator-multiload-graphs-0.png':
TypeError: method Gio.File.read_async: At least 3 arguments required,
but only 2 passed
Don't know if this is a documented change of that method and the bug
should be open for the indicator-multiload app. Please, if that's the
case just let me know to do it.
Thanks and best reagrds
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+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 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
BTW: as I said the problem is solved with the proposed builds.
So, the indicator-multiload app is working as expected. But I just
realized that is throwing another messages at its start, messages that
it's not throwing in Ubuntu 20.10 groovy. These are the messages:
amd64:
--
abr 23 02:54:52 fprietog-VirtualBox gnome-shell[1339]: value "nan" of type
'gfloat' is invalid or out of range for property 'x' of type 'gfloat'
abr 23 02:54:52 fprietog-VirtualBox gnome-shell[1339]: value "nan" of type
'gfloat' is invalid or out of range for property 'y' of type 'gfloat'
abr 23 02:54:52 fprietog-VirtualBox gnome-shell[1339]: JS ERROR: Exception in
callback for signal: shown: Error: Wrong type number; float expected. But it's
out of range: -Infinity
_init/GObject.Object.prototype.set@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:553:16
_easeActor@resource:///org/gnome/shell/ui/environment.js:155:15
init/Clutter.Actor.prototype.ease@resource:///org/gnome/shell/ui/environment.js:294:19
_syncWorkspacesActualGeometry@resource:///org/gnome/shell/ui/workspacesView.js:728:21
_init/this._overviewShownId<@resource:///org/gnome/shell/ui/workspacesView.js:396:18
_emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47
_showDone@resource:///org/gnome/shell/ui/overview.js:604:14
onComplete@resource:///org/gnome/shell/ui/overview.js:589:36
_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:85:13
_easeActor/<@resource:///org/gnome/shell/ui/environment.js:168:64
arm64:
--
abr 23 00:18:31 fpgrpi gnome-shell[1494]: value "nan" of type 'gfloat' is
invalid or out of range for property 'x' of type 'gfloat'
abr 23 00:18:31 fpgrpi gnome-shell[1494]: value "nan" of type 'gfloat' is
invalid or out of range for property 'y' of type 'gfloat'
abr 23 00:18:31 fpgrpi gnome-shell[1494]: JS ERROR: Exception in callback for
signal: shown: Error: Wrong type number; float expected. But it's out of range:
-Infinity
_init/GObject.Object.prototype.set@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:553:16
_easeActor@resource:///org/gnome/shell/ui/environment.js:155:15
init/Clutter.Actor.prototype.ease@resource:///org/gnome/shell/ui/environment.js:294:19
_syncWorkspacesActualGeometry@resource:///org/gnome/shell/ui/workspacesView.js:728:21
_init/this._overviewShownId<@resource:///org/gnome/shell/ui/workspacesView.js:396:18
_emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47
_showDone@resource:///org/gnome/shell/ui/overview.js:604:14
onComplete@resource:///org/gnome/shell/ui/overview.js:589:36
_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:85:13
_easeActor/<@resource:///org/gnome/shell/ui/environment.js:168:64
abr 23 00:18:31 fpgrpi gnome-shell[1494]: value "nan" of type 'gfloat' is
invalid or out of range for property 'x' of type 'gfloat'
abr 23 00:18:31 fpgrpi gnome-shell[1494]: value "nan" of type 'gfloat' is
invalid or out of range for property 'y' of type 'gfloat'
abr 23 00:18:31 fpgrpi gnome-shell[1494]: JS ERROR: Error: Wrong type number;
float expected. But it's out of range: -Infinity
_init/GObject.Object.prototype.set@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:553:16
_easeActor@resource:///org/gnome/shell/ui/environment.js:155:15
init/Clutter.Actor.prototype.ease@resource:///org/gnome/shell/ui/environment.js:294:19
_syncWorkspacesActualGeometry@resource:///org/gnome/shell/ui/workspacesView.js:728:21
_updateWorkspacesActualGeometry/this._syncActualGeometryLater<@resource:///org/gnome/shell/ui/workspacesView.js:716:22
But, as I said, I think these messages are not having impact in the
execution of indicator-multiload app. At least I didn't notice any
problem.
Just wanted to comment it, just in case.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1923267
Title:
Gjs promises on Gio.File operations don't work anymore after upgrading
libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Status in gjs package in Ubuntu:
Fix Committed
Status in gnome-shell-extension-appindicator package in Ubuntu:
Won't Fix
Status in gjs source package in Hirsute:
Fix Committed
Bug description:
[ Impact ]
As per glib commit
https://gitlab.gnome.org/GNOME/glib/-/commit/d52728f99
Gio.File.new_for_path("") returns a GDummyFile implementation, while
Gio._promisify relies on it being a LocalFile, so we don't promisify
the right methods.
[ Test case ]
gjs -c "imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype,
'delete_async', 'delete_finish');
print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" &&
echo GJS works
Should write on terminal:
[object Promise]
GJS works
In the bugged version would instead just:
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: JS ERROR: TypeError: method
Gio.File.delete_async: At least 3 arguments required, but only 2 passed
@:2:48
[Desktop-packages] [Bug 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Just tested amd64 packages with the same results than arm64: problem is
solved.
Thanks and best regards.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1923267
Title:
Gjs promises on Gio.File operations don't work anymore after upgrading
libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Status in gjs package in Ubuntu:
Fix Committed
Status in gnome-shell-extension-appindicator package in Ubuntu:
Won't Fix
Status in gjs source package in Hirsute:
Fix Committed
Bug description:
[ Impact ]
As per glib commit
https://gitlab.gnome.org/GNOME/glib/-/commit/d52728f99
Gio.File.new_for_path("") returns a GDummyFile implementation, while
Gio._promisify relies on it being a LocalFile, so we don't promisify
the right methods.
[ Test case ]
gjs -c "imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype,
'delete_async', 'delete_finish');
print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" &&
echo GJS works
Should write on terminal:
[object Promise]
GJS works
In the bugged version would instead just:
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: JS ERROR: TypeError: method
Gio.File.delete_async: At least 3 arguments required, but only 2 passed
@:2:48
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: Script
threw an exception
[ Regression potential ]
Gjs apps are slower in starting up, or not act properly when / is not
a local location.
---
Problem tested in two different environments:
- Ubuntu 21.04 Beta amd64
- Ubuntu 21.04 Beta arm64 (Raspberry Pi 4B 8GB)
After upgrading these packages:
libglib2.0-02.67.5-2 to 2.68.0-1
libglib2.0-bin 2.67.5-2 to 2.68.0-1
libglib2.0-data 2.67.5-2 to 2.68.0-1
The app indicator-multiload (0.4-0ubuntu5) doesn't work showing only
three dots (...) instead of the graphic expected. It's throwing error
messages to the system journal every second or so (depends of the
refresh interval selected in the app settings):
abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]:
multiload, Impossible to read image from path '/run/user/1026
/multiload-icons-Wc8kck/icons/indicator-multiload-graphs-0.png':
TypeError: method Gio.File.read_async: At least 3 arguments required,
but only 2 passed
Don't know if this is a documented change of that method and the bug
should be open for the indicator-multiload app. Please, if that's the
case just let me know to do it.
Thanks and best reagrds
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+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 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Hello Brian,
Just tested arm64 build; updated these packages:
- gjs_1.67.2-2ubuntu2_arm64.deb
fprietog@fpgrpi:~$ apt-cache policy gjs
gjs:
Instalados: 1.67.2-2ubuntu2
Candidato: 1.67.2-2ubuntu2
Tabla de versión:
*** 1.67.2-2ubuntu2 100
100 /var/lib/dpkg/status
1.67.2-2ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports hirsute/main arm64 Packages
- libgjs0g_1.67.2-2ubuntu2_arm64.deb
fprietog@fpgrpi:~$ apt-cache policy libgjs0g
libgjs0g:
Instalados: 1.67.2-2ubuntu2
Candidato: 1.67.2-2ubuntu2
Tabla de versión:
*** 1.67.2-2ubuntu2 100
100 /var/lib/dpkg/status
1.67.2-2ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports hirsute/main arm64 Packages
And, after reboot, the problem reported is solved:
1./ Test case:
fprietog@fpgrpi:~$ gjs -c
"imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype, 'delete_async',
'delete_finish');
print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" && echo
GJS works
[object Promise]
GJS works
2./ The error shown in every boot as also gone.
3./ The indicator-multiload app now is working as expected
I'll test amd64 build when available.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1923267
Title:
Gjs promises on Gio.File operations don't work anymore after upgrading
libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Status in gjs package in Ubuntu:
Fix Committed
Status in gnome-shell-extension-appindicator package in Ubuntu:
Won't Fix
Status in gjs source package in Hirsute:
Fix Committed
Bug description:
[ Impact ]
As per glib commit
https://gitlab.gnome.org/GNOME/glib/-/commit/d52728f99
Gio.File.new_for_path("") returns a GDummyFile implementation, while
Gio._promisify relies on it being a LocalFile, so we don't promisify
the right methods.
[ Test case ]
gjs -c "imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype,
'delete_async', 'delete_finish');
print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" &&
echo GJS works
Should write on terminal:
[object Promise]
GJS works
In the bugged version would instead just:
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: JS ERROR: TypeError: method
Gio.File.delete_async: At least 3 arguments required, but only 2 passed
@:2:48
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: Script
threw an exception
[ Regression potential ]
Gjs apps are slower in starting up, or not act properly when / is not
a local location.
---
Problem tested in two different environments:
- Ubuntu 21.04 Beta amd64
- Ubuntu 21.04 Beta arm64 (Raspberry Pi 4B 8GB)
After upgrading these packages:
libglib2.0-02.67.5-2 to 2.68.0-1
libglib2.0-bin 2.67.5-2 to 2.68.0-1
libglib2.0-data 2.67.5-2 to 2.68.0-1
The app indicator-multiload (0.4-0ubuntu5) doesn't work showing only
three dots (...) instead of the graphic expected. It's throwing error
messages to the system journal every second or so (depends of the
refresh interval selected in the app settings):
abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]:
multiload, Impossible to read image from path '/run/user/1026
/multiload-icons-Wc8kck/icons/indicator-multiload-graphs-0.png':
TypeError: method Gio.File.read_async: At least 3 arguments required,
but only 2 passed
Don't know if this is a documented change of that method and the bug
should be open for the indicator-multiload app. Please, if that's the
case just let me know to do it.
Thanks and best reagrds
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+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 1022858] Re: Guest session asks for a password after switching users
You do not need to switch from guest session to do those nowadays: https://help.ubuntu.com/community/CustomizeGuestSession -- 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/1022858 Title: Guest session asks for a password after switching users Status in lightdm package in Ubuntu: Confirmed Bug description: When I switch back to an already open guest session from my user account, I find that the guest session is locked and it asks for the Guest password (which obviously there isn't because it's a guest session!). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-session-bin 3.2.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Tue Jul 10 09:54:55 2012 ExecutablePath: /usr/bin/gnome-session InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (compiz:1719): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed --- ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MarkForUpload: True Package: lightdm 1.2.1-0ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35 Tags: precise running-unity Uname: Linux 3.2.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1022858/+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 1022858] Re: Guest session asks for a password after switching users
Jarno Suni wrote: > Does one need to switch from guest session? Maybe it should be disabled. One needed to switch from the guest session to the primary (sudoer) user session to make permanent customization to the guest session. See https://ubuntuforums.org/showthread.php?t=2152804&p=12687863#post12687863 for instructions. This allowed one to do some house cleaning such as disabling the **backup reminder popup** (which one can't setup in a guest session anyways, as all changes are lost on logout), and add Chrome on the Guest's top panel for example. -- 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/1022858 Title: Guest session asks for a password after switching users Status in lightdm package in Ubuntu: Confirmed Bug description: When I switch back to an already open guest session from my user account, I find that the guest session is locked and it asks for the Guest password (which obviously there isn't because it's a guest session!). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-session-bin 3.2.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Tue Jul 10 09:54:55 2012 ExecutablePath: /usr/bin/gnome-session InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (compiz:1719): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed --- ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MarkForUpload: True Package: lightdm 1.2.1-0ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35 Tags: precise running-unity Uname: Linux 3.2.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1022858/+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 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Hello fprietog, or anyone else affected,
Accepted gjs into hirsute-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/gjs/1.67.2-2ubuntu2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
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.
** Changed in: gjs (Ubuntu Hirsute)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-hirsute
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1923267
Title:
Gjs promises on Gio.File operations don't work anymore after upgrading
libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Status in gjs package in Ubuntu:
Fix Committed
Status in gnome-shell-extension-appindicator package in Ubuntu:
Won't Fix
Status in gjs source package in Hirsute:
Fix Committed
Bug description:
[ Impact ]
As per glib commit
https://gitlab.gnome.org/GNOME/glib/-/commit/d52728f99
Gio.File.new_for_path("") returns a GDummyFile implementation, while
Gio._promisify relies on it being a LocalFile, so we don't promisify
the right methods.
[ Test case ]
gjs -c "imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype,
'delete_async', 'delete_finish');
print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" &&
echo GJS works
Should write on terminal:
[object Promise]
GJS works
In the bugged version would instead just:
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: JS ERROR: TypeError: method
Gio.File.delete_async: At least 3 arguments required, but only 2 passed
@:2:48
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: Script
threw an exception
[ Regression potential ]
Gjs apps are slower in starting up, or not act properly when / is not
a local location.
---
Problem tested in two different environments:
- Ubuntu 21.04 Beta amd64
- Ubuntu 21.04 Beta arm64 (Raspberry Pi 4B 8GB)
After upgrading these packages:
libglib2.0-02.67.5-2 to 2.68.0-1
libglib2.0-bin 2.67.5-2 to 2.68.0-1
libglib2.0-data 2.67.5-2 to 2.68.0-1
The app indicator-multiload (0.4-0ubuntu5) doesn't work showing only
three dots (...) instead of the graphic expected. It's throwing error
messages to the system journal every second or so (depends of the
refresh interval selected in the app settings):
abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]:
multiload, Impossible to read image from path '/run/user/1026
/multiload-icons-Wc8kck/icons/indicator-multiload-graphs-0.png':
TypeError: method Gio.File.read_async: At least 3 arguments required,
but only 2 passed
Don't know if this is a documented change of that method and the bug
should be open for the indicator-multiload app. Please, if that's the
case just let me know to do it.
Thanks and best reagrds
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+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 1923267] Please test proposed package
Hello fprietog, or anyone else affected,
Accepted gjs into hirsute-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/gjs/1.67.2-2ubuntu2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
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.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1923267
Title:
Gjs promises on Gio.File operations don't work anymore after upgrading
libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Status in gjs package in Ubuntu:
Fix Committed
Status in gnome-shell-extension-appindicator package in Ubuntu:
Won't Fix
Status in gjs source package in Hirsute:
Fix Committed
Bug description:
[ Impact ]
As per glib commit
https://gitlab.gnome.org/GNOME/glib/-/commit/d52728f99
Gio.File.new_for_path("") returns a GDummyFile implementation, while
Gio._promisify relies on it being a LocalFile, so we don't promisify
the right methods.
[ Test case ]
gjs -c "imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype,
'delete_async', 'delete_finish');
print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" &&
echo GJS works
Should write on terminal:
[object Promise]
GJS works
In the bugged version would instead just:
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: JS ERROR: TypeError: method
Gio.File.delete_async: At least 3 arguments required, but only 2 passed
@:2:48
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: Script
threw an exception
[ Regression potential ]
Gjs apps are slower in starting up, or not act properly when / is not
a local location.
---
Problem tested in two different environments:
- Ubuntu 21.04 Beta amd64
- Ubuntu 21.04 Beta arm64 (Raspberry Pi 4B 8GB)
After upgrading these packages:
libglib2.0-02.67.5-2 to 2.68.0-1
libglib2.0-bin 2.67.5-2 to 2.68.0-1
libglib2.0-data 2.67.5-2 to 2.68.0-1
The app indicator-multiload (0.4-0ubuntu5) doesn't work showing only
three dots (...) instead of the graphic expected. It's throwing error
messages to the system journal every second or so (depends of the
refresh interval selected in the app settings):
abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]:
multiload, Impossible to read image from path '/run/user/1026
/multiload-icons-Wc8kck/icons/indicator-multiload-graphs-0.png':
TypeError: method Gio.File.read_async: At least 3 arguments required,
but only 2 passed
Don't know if this is a documented change of that method and the bug
should be open for the indicator-multiload app. Please, if that's the
case just let me know to do it.
Thanks and best reagrds
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+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 1925379] Re: Auto-Correct does not work since upgrade to Hirsute
I can confirm this issue and it is caused by the current gtk+-3.0 package. Running with gtk+-3.0 3.24.28+git fixes the issue locally for me. ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- 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/1925379 Title: Auto-Correct does not work since upgrade to Hirsute Status in gtk+3.0 package in Ubuntu: New Status in libreoffice package in Ubuntu: Confirmed Bug description: I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, same LibreOffice profile, same LibreOffice document, and no changes on my part to my LibreOffice settings since I installed Ubuntu 21.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1925379/+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 1775088] Re: Ubuntu Mate guest session locked out when switching from another account
*** This bug is a duplicate of bug 1022858 *** https://bugs.launchpad.net/bugs/1022858 ** This bug has been marked a duplicate of bug 1022858 Guest session asks for a password after switching users -- 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/1775088 Title: Ubuntu Mate guest session locked out when switching from another account Status in Ubuntu MATE: New Status in lightdm package in Ubuntu: Confirmed Bug description: ATTN: Ubuntu Mate Developers Description: Ubuntu 18.04 LTS Release: 18.04 lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status In Ubuntu Mate 18.04 LTS LightDM, I created a file in /etc/lightdm/lightdm.conf, with the line: allow-guest=true This allows me to log into a guest session. The issue is when I try to switch between the guest session and a normal session and back. Switching from guest session to the normal user session is fine. LightDM asks for the normal user password. However, when I try to switch from the normal user to back to the guest session I am asked for password as well. This is the problem as the guest session has no known password. The unlock window has a 'Switch User" button along with Cancel, etc. Clicking the "Switch User" button takes me to the standard LightDM screen. There I can select from the normal user and the guest. However, selecting guest here opens a new guest session, and does not take me back to the guest session already open. This looks like an old bug https://bugs.launchpad.net/bugs/1481804 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: MATE Date: Mon Jun 4 17:46:33 2018 InstallationDate: Installed on 2018-05-31 (4 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1775088/+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 1925683] Re: Cursor Tracking with Gnome Shell Magnifier on Wayland
Upstream bug: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4112
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1925683
Title:
Cursor Tracking with Gnome Shell Magnifier on Wayland
Status in gnome-shell package in Ubuntu:
New
Bug description:
Affected version
GNOME 3.36 - 3.40.
Ubuntu 20.04, 20.10, 21.04 and Fedora 34 Beta.
Wayland only.
Bug summary
When running GNOME shell with Wayland, the cursor and focus tracking
functionality of the magnifier (a11y feature) do not correctly compute the
cursor/focus location. The position is calculated from the top left of the
window but the windows position is not included. This causes the magnifier to
track the wrong location when the window is not maximiser or is on a second
monitor.
I suspect this is related to the way in which wayland is designed. But
my experience in this area is minimal. When using X11 this feature
works correctly.
The wiki page states that under wayland the cursor and focus tracking
work but this information is either out dated or was not tested
correctly.
Steps to reproduce
From the Gnome desktop, open a terminal by pressing ctrl + alt + t or by
opening the activities overlay and searching for "terminal".
Press super + left arrow key to maximize the terminal window on the left side
of the screen.
Activity the magnifier by pressing super + alt + 8.
Type text into the terminal window. The magnified view will move with the
text cursor.
Press super + right arrow key to maximize the terminal windows on the right
side of the screen.
Type text into the terminal. The magnified view will move but it will not
show the text cursor. It will move when text is entered but will focus on the
left side of the screen.
What happened
The magnified view does not follow the text/focus cursor correctly.
What did you expect to happen
The magnified view should follow the cursor and show the cursor as it does
when the widnows is maximized. The correct behaviour can also be seen in Gnome
shell running with X11.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.4-1ubuntu2
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 22 20:55:25 2021
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2021-04-22 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1925683/+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 1925683] [NEW] Cursor Tracking with Gnome Shell Magnifier on Wayland
Public bug reported:
Affected version
GNOME 3.36 - 3.40.
Ubuntu 20.04, 20.10, 21.04 and Fedora 34 Beta.
Wayland only.
Bug summary
When running GNOME shell with Wayland, the cursor and focus tracking
functionality of the magnifier (a11y feature) do not correctly compute the
cursor/focus location. The position is calculated from the top left of the
window but the windows position is not included. This causes the magnifier to
track the wrong location when the window is not maximiser or is on a second
monitor.
I suspect this is related to the way in which wayland is designed. But
my experience in this area is minimal. When using X11 this feature works
correctly.
The wiki page states that under wayland the cursor and focus tracking
work but this information is either out dated or was not tested
correctly.
Steps to reproduce
>From the Gnome desktop, open a terminal by pressing ctrl + alt + t or by
>opening the activities overlay and searching for "terminal".
Press super + left arrow key to maximize the terminal window on the left side
of the screen.
Activity the magnifier by pressing super + alt + 8.
Type text into the terminal window. The magnified view will move with the text
cursor.
Press super + right arrow key to maximize the terminal windows on the right
side of the screen.
Type text into the terminal. The magnified view will move but it will not show
the text cursor. It will move when text is entered but will focus on the left
side of the screen.
What happened
The magnified view does not follow the text/focus cursor correctly.
What did you expect to happen
The magnified view should follow the cursor and show the cursor as it does when
the widnows is maximized. The correct behaviour can also be seen in Gnome shell
running with X11.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.4-1ubuntu2
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 22 20:55:25 2021
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2021-04-22 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug hirsute wayland-session
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4112
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4112
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1925683
Title:
Cursor Tracking with Gnome Shell Magnifier on Wayland
Status in gnome-shell package in Ubuntu:
New
Bug description:
Affected version
GNOME 3.36 - 3.40.
Ubuntu 20.04, 20.10, 21.04 and Fedora 34 Beta.
Wayland only.
Bug summary
When running GNOME shell with Wayland, the cursor and focus tracking
functionality of the magnifier (a11y feature) do not correctly compute the
cursor/focus location. The position is calculated from the top left of the
window but the windows position is not included. This causes the magnifier to
track the wrong location when the window is not maximiser or is on a second
monitor.
I suspect this is related to the way in which wayland is designed. But
my experience in this area is minimal. When using X11 this feature
works correctly.
The wiki page states that under wayland the cursor and focus tracking
work but this information is either out dated or was not tested
correctly.
Steps to reproduce
From the Gnome desktop, open a terminal by pressing ctrl + alt + t or by
opening the activities overlay and searching for "terminal".
Press super + left arrow key to maximize the terminal window on the left side
of the screen.
Activity the magnifier by pressing super + alt + 8.
Type text into the terminal window. The magnified view will move with the
text cursor.
Press super + right arrow key to maximize the terminal windows on the right
side of the screen.
Type text into the terminal. The magnified view will move but it will not
show the text cursor. It will move when text is entered but will focus on the
left side of the screen.
What happened
The magnified view does not follow the text/focus cursor correctly.
What did you expect to happen
The magnified view should follow the cursor and show the cursor as it does
when the widnows is maximized. The correct behaviour can
[Desktop-packages] [Bug 1022858] Re: Guest session asks for a password after switching users
On 2020-01-16 13:03, Jarno Suni wrote: > What is so difficult in not asking password when guest session > is concerned? Maybe low priority since guest session is disabled by default. https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1775088/comments/2 > Does one need to switch from guest session? Maybe it should be > disabled. Also such a change would need work. -- 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/1022858 Title: Guest session asks for a password after switching users Status in lightdm package in Ubuntu: Confirmed Bug description: When I switch back to an already open guest session from my user account, I find that the guest session is locked and it asks for the Guest password (which obviously there isn't because it's a guest session!). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-session-bin 3.2.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Tue Jul 10 09:54:55 2012 ExecutablePath: /usr/bin/gnome-session InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (compiz:1719): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed --- ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MarkForUpload: True Package: lightdm 1.2.1-0ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35 Tags: precise running-unity Uname: Linux 3.2.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1022858/+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 1925676] Re: Xorg freeze
** Package changed: ubuntu => xorg (Ubuntu) -- 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/1925676 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Since a week or two, videos started to freeze on Youtube. The video jam, the audio repeating the last quarter of a second of material, just like an audio CD that stays hooked. At this point, the mouse and the keyboard don't respond in any way and I have to depress the ON/OFF key and hold it a few seconds to do a forced stop. The computer restart normally, and Firefox open with a screen that says:"sorry we cannot restore your previous tabs". This bug happens again and again, each time 15 or 20 minutes after starting a video. I thought maybe it is a problem related to Youtube, but I tried watching a video on another site, DailyMotion, and the same thing happened, again after 15 minutes. I didn't upgrade or add any software recently, nor change any setting. This thing really appeared out of a blue sky. Thanks for your attention, RB ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262 Uname: Linux 4.4.0-210-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.30 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 22 14:53:35 2021 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA controller]) Subsystem: IBM ThinkPad X41 [1014:0582] Subsystem: IBM ThinkPad X41 [1014:0582] InstallationDate: Installed on 2018-08-14 (982 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: IBM 1875M2U PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=fr_CA:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-210-generic root=UUID=596f4e0f-deb0-4de7-973b-8259f928fbe9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2007 dmi.bios.vendor: IBM dmi.bios.version: 70ET69WW (1.29 ) dmi.board.name: 1875M2U dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr70ET69WW(1.29):bd05/29/2007:svnIBM:pn1875M2U:pvrThinkPadT43:rvnIBM:rn1875M2U:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 1875M2U dmi.product.version: ThinkPad T43 dmi.sys.vendor: IBM version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.12 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Apr 22 10:09:47 2021 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1925676/+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 1925676] [NEW] Xorg freeze
You have been subscribed to a public bug: Since a week or two, videos started to freeze on Youtube. The video jam, the audio repeating the last quarter of a second of material, just like an audio CD that stays hooked. At this point, the mouse and the keyboard don't respond in any way and I have to depress the ON/OFF key and hold it a few seconds to do a forced stop. The computer restart normally, and Firefox open with a screen that says:"sorry we cannot restore your previous tabs". This bug happens again and again, each time 15 or 20 minutes after starting a video. I thought maybe it is a problem related to Youtube, but I tried watching a video on another site, DailyMotion, and the same thing happened, again after 15 minutes. I didn't upgrade or add any software recently, nor change any setting. This thing really appeared out of a blue sky. Thanks for your attention, RB ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262 Uname: Linux 4.4.0-210-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.30 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 22 14:53:35 2021 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA controller]) Subsystem: IBM ThinkPad X41 [1014:0582] Subsystem: IBM ThinkPad X41 [1014:0582] InstallationDate: Installed on 2018-08-14 (982 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: IBM 1875M2U PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=fr_CA:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-210-generic root=UUID=596f4e0f-deb0-4de7-973b-8259f928fbe9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2007 dmi.bios.vendor: IBM dmi.bios.version: 70ET69WW (1.29 ) dmi.board.name: 1875M2U dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr70ET69WW(1.29):bd05/29/2007:svnIBM:pn1875M2U:pvrThinkPadT43:rvnIBM:rn1875M2U:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 1875M2U dmi.product.version: ThinkPad T43 dmi.sys.vendor: IBM version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.12 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Apr 22 10:09:47 2021 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.12 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 freeze i386 ubuntu xenial -- Xorg freeze https://bugs.launchpad.net/bugs/1925676 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- 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 1925680] [NEW] Accessing the filesystem hangs unless µI kill gvfsd-trash
Public bug reported: Description:Ubuntu 20.04.2 LTS Release:20.04 gvfs: Installed: 1.44.1-1ubuntu1 Randomly my filesystem hangs during 30s when I'm trying to open a file from an application, lauching a file manager or doing something which requires some access to my filesystem. I've a Synology Drive mounted with a classic `mount -t cifs`. When the filesystem start hanging I need to either reboot my computer or kill the gvfsd-trash process. I've no clue on how to fix that. ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1925680 Title: Accessing the filesystem hangs unless µI kill gvfsd-trash Status in gvfs package in Ubuntu: New Bug description: Description: Ubuntu 20.04.2 LTS Release: 20.04 gvfs: Installed: 1.44.1-1ubuntu1 Randomly my filesystem hangs during 30s when I'm trying to open a file from an application, lauching a file manager or doing something which requires some access to my filesystem. I've a Synology Drive mounted with a classic `mount -t cifs`. When the filesystem start hanging I need to either reboot my computer or kill the gvfsd-trash process. I've no clue on how to fix that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1925680/+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 1875592] Re: Xorg: High CPU usage when USB mic is plugged in after hibernation
Is klobalaccel5 also consuming high amounts of CPU? Are you using .Xmodmap? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1875592 Title: Xorg: High CPU usage when USB mic is plugged in after hibernation Status in xorg-server package in Ubuntu: New Bug description: Problem: = When I plug in a USB microphone after one, two or three hibernations with work in between* the Xorg process is "going crazy" at around 100% - 130% CPU usage. (please see the attached chart) Steps (to hopefulle reproduce): === - start pc - do some usual work for a couple of hours - hibernate - wake up - do some usual work for a couple of hours - hibernate - wake up ( you might need more repetitions here) - do some usual work for a couple of hours - plug in USB microphone Actual: - Xorg has high CPU usage Expected: - Xorg has usual CPU usage Remarks = I could not safely reproduce this behaviour on purpose simply by starting and hibernating. But I experience it on a week to week basis. I'm not suspending or some kind of suspend+hibernate. It's pure hibernation I experience this problem, I think, in 16 (started here), (never tried 17), 18, 19.10 I used perftop with flamegraph the other day. It revealed - DeletePassiveGrabFromList with 3 ~ 5% - ResourceClientBits: around 5% - GrabMatchesSecond: 3 ~ 5% - trace_raw_output_kvm_inj_virq: around 7 ~ 8% System === lsb_release -rd --- Description: Ubuntu 19.10 Release: 19.10 apt-cache policy xorg -- xorg: Installed: 1:7.7+19ubuntu12 Candidate: 1:7.7+19ubuntu12 Version table: *** 1:7.7+19ubuntu12 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Misc - 12GB RAM - Core i5 4 cores Debugging -- I can help collecting data, but I need assistance ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Apr 28 17:29:02 2020 DistUpgraded: 2019-12-01 10:19:03,497 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-40-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. UHD Graphics 620 [10cf:1959] MachineType: FUJITSU FMVWB3U27 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=fe637d00-125b-4a54-adce-3711830d450b ro pci=nomsi acpi_osi=Linuxs resume=UUID=8fa6d40f-c23d-497e-9846-f6f26536690d SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-12-01 (149 days ago) dmi.bios.date: 01/23/2018 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.07 dmi.board.name: FJNB2BB dmi.board.vendor: FUJITSU dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWB3U27 dmi.sys.vendor: FUJITSU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1875592/+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 1925379] Re: Auto-Correct does not work since upgrade to Hirsute
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- 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/1925379 Title: Auto-Correct does not work since upgrade to Hirsute Status in libreoffice package in Ubuntu: Confirmed Bug description: I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, same LibreOffice profile, same LibreOffice document, and no changes on my part to my LibreOffice settings since I installed Ubuntu 21.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1925379/+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 1925677] [NEW] Thunderbird: Recurring tasks on CalDAV account can no longer be set to completed
Public bug reported: Steps to reproduce: Set up calendar and tasks with a CalDav server and an old Thunderbird version (up to ca. December 2020). Set up a recurring task. Whenever an instance of the recurring task becomes due, mark it as completed. Repeat this for a few instances. Upgrade to Thunderbird 78.7.1. Examine the list of tasks. Actual results: Previous instances of the recurring tasks (which had already been marked as completed before the update) now reappear and show as incomplete. If I manually set them to Completed, the status will be reset upon sync. Expected results: Completion status (as previously set) is honored and the tasks no longer show as open. Additional information: The server is running DAViCal. I just ran a few extra tests: * Recurring tasks in local storage (create a weekly task, starting a few weeks in the past and ending a few weeks into the future, then mark some of the past instances as complete) * Same on the CalDAV calendar, sync after marking a few past instances complete * Repeat the CalDAV tests with variations: complete the second instance but leave the first one uncompleted; complete the third instance, sync, then complete the second one * Non-recurring task on CalDAV Results: * Non-recurring tasks are not affected; I can mark the task completed and it will keep its status. * Recurring tasks in local storage are also not affected; completed instances will keep their status. * Instances of recurring tasks on CalDAV can be marked completed but will lose their status upon synchronization. Exception: one instance maintains its completion status. * The instance to maintain its completion status is the first one that got marked complete (i.e. based on the time the completion flag got set, not based on start date). This bug began showing with an update deployed sometime between January–March 2021, though I failed to record the exact version numbers. I also have an Android app accessing the same DAViCal instance, where the completed instance have not been reset. In conclusion, the issue seems to occur when reading tasks from a CalDAV server (tasks on the server are not altered). The first instance which got set to Completed retains its completion status, whereas the flag is ignored for all later ones. I have filed this bug upstream at https://bugzilla.mozilla.org/show_bug.cgi?id=1707032 and was told that this issue should be fixed as of Thunderbird 78.8.0 (current being 78.10.0). So the main issue is that the Ubuntu repos have an outdated Thunderbird version with a known issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: thunderbird 1:78.7.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BuildID: 20210203182138 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Thu Apr 22 22:31:01 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-09 (2325 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) SourcePackage: thunderbird UpgradeStatus: Upgraded to focal on 2020-11-17 (156 days ago) ** Affects: thunderbird (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 thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1925677 Title: Thunderbird: Recurring tasks on CalDAV account can no longer be set to completed Status in thunderbird package in Ubuntu: New Bug description: Steps to reproduce: Set up calendar and tasks with a CalDav server and an old Thunderbird version (up to ca. December 2020). Set up a recurring task. Whenever an instance of the recurring task becomes due, mark it as completed. Repeat this for a few instances. Upgrade to Thunderbird 78.7.1. Examine the list of tasks. Actual results: Previous instances of the recurring tasks (which had already been marked as completed before the update) now reappear and show as incomplete. If I manually set them to Completed, the status will be reset upon sync. Expected results: Completion status (as previously set) is honored and the tasks no longer show as open. Additional information: The server is running DAViCal. I just ran a few extra tests: * Recurring tasks in local storage (create a weekly task, starting a few weeks in the past and ending a few weeks into the future, then mark some of the past instances as complete) * Same on the CalDAV calendar, sync after marking a few past instances complete * Repeat the CalDAV tests with variations: complete the second instance but leave the first one uncompleted; complete the third instance, sync, then complete the second one * Non-recurring task on CalDAV Results: * Non-recurring tasks are not affected; I can mark
[Desktop-packages] [Bug 1925379] Re: Auto-Correct does not work since upgrade to Hirsute
Same here with Xubuntu 21.04 which I am running as a VM in KVM/QEMU and have the same problem - almost. If I type 1/2 it does not autocorrect to ½ unless I highlight it in the text then go to Tools -> Autocorrect -> Apply when the change occurs. However, if I try to repeat that with a second typing of 1/2, highlight it, and again go through the Tools -> Autocorrect -> Apply, nothing happens. Once and only once it happens, not automatically as it does in Xubuntu 20.04 with the same LO version 7.1.2.2. -- 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/1925379 Title: Auto-Correct does not work since upgrade to Hirsute Status in libreoffice package in Ubuntu: Confirmed Bug description: I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, same LibreOffice profile, same LibreOffice document, and no changes on my part to my LibreOffice settings since I installed Ubuntu 21.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1925379/+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 1922548] Re: The admin backend is broken
The issue is fixed in upstream git https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/122/ ** Changed in: gvfs (Ubuntu) Importance: Undecided => High ** Changed in: gvfs (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1922548 Title: The admin backend is broken Status in PolicyKit: Unknown Status in gvfs package in Ubuntu: Fix Committed Status in nautilus package in Ubuntu: Invalid Bug description: On my PC I have some different users. If from one user I try to access the Home directory of a different user I enter the password and then I have a crash. Seen attached screenshot. Problem happens with both x11 and Wayland sessions. More: opening this bug I have the messages: corrado@corrado-n2-hh-0402:~$ ubuntu-bug -w ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 227, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 945, in attach_casper_md5check with open(location) as json_file: PermissionError: [Errno 13] Permission denied: '/var/log/installer/casper-md5check.json' corrado@corrado-n2-hh-0402:~$ [GFX1-]: glxtest: Could not connect to wayland socket ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 5 12:05:27 2021 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1137, 611)' InstallationDate: Installed on 2021-04-02 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210402) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.39.2-1 file-roller 3.38.0-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/policykit/+bug/1922548/+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 1922548] Re: The admin backend is broken
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1922548 Title: The admin backend is broken Status in PolicyKit: Unknown Status in gvfs package in Ubuntu: Fix Committed Status in nautilus package in Ubuntu: Invalid Bug description: On my PC I have some different users. If from one user I try to access the Home directory of a different user I enter the password and then I have a crash. Seen attached screenshot. Problem happens with both x11 and Wayland sessions. More: opening this bug I have the messages: corrado@corrado-n2-hh-0402:~$ ubuntu-bug -w ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 227, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 945, in attach_casper_md5check with open(location) as json_file: PermissionError: [Errno 13] Permission denied: '/var/log/installer/casper-md5check.json' corrado@corrado-n2-hh-0402:~$ [GFX1-]: glxtest: Could not connect to wayland socket ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 5 12:05:27 2021 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1137, 611)' InstallationDate: Installed on 2021-04-02 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210402) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.39.2-1 file-roller 3.38.0-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/policykit/+bug/1922548/+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 1922548] Re: Error accessing Home of another user [Oops! Something went wrong. Unhandled error message: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Unix process subjec
** Changed in: nautilus (Ubuntu) Status: New => Invalid ** Package changed: policykit-1 (Ubuntu) => gvfs (Ubuntu) ** Summary changed: - Error accessing Home of another user [Oops! Something went wrong. Unhandled error message: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Unix process subject does not have uid set] + The admin backend is broken -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1922548 Title: The admin backend is broken Status in PolicyKit: Unknown Status in gvfs package in Ubuntu: Fix Committed Status in nautilus package in Ubuntu: Invalid Bug description: On my PC I have some different users. If from one user I try to access the Home directory of a different user I enter the password and then I have a crash. Seen attached screenshot. Problem happens with both x11 and Wayland sessions. More: opening this bug I have the messages: corrado@corrado-n2-hh-0402:~$ ubuntu-bug -w ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 227, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 945, in attach_casper_md5check with open(location) as json_file: PermissionError: [Errno 13] Permission denied: '/var/log/installer/casper-md5check.json' corrado@corrado-n2-hh-0402:~$ [GFX1-]: glxtest: Could not connect to wayland socket ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 5 12:05:27 2021 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1137, 611)' InstallationDate: Installed on 2021-04-02 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210402) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.39.2-1 file-roller 3.38.0-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/policykit/+bug/1922548/+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 1925464] Re: Cannot open /boot/efi
*** This bug is a duplicate of bug 1922548 *** https://bugs.launchpad.net/bugs/1922548 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1922548, so it 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. Feel free to continue to report any other bugs you may find. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** This bug has been marked a duplicate of bug 1922548 The admin backend is broken -- 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/1925464 Title: Cannot open /boot/efi Status in nautilus package in Ubuntu: New Bug description: Get this error message when trying to open /boot/efi "gdbus error freedesktop policykit1 error failed unix process subject does not have uuid set" ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 22 12:24:31 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'355' b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" 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-22 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) 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/1925464/+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 1022858] Re: Guest session asks for a password after switching users
Does one need to switch from guest session? Maybe it should be disabled. -- 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/1022858 Title: Guest session asks for a password after switching users Status in lightdm package in Ubuntu: Confirmed Bug description: When I switch back to an already open guest session from my user account, I find that the guest session is locked and it asks for the Guest password (which obviously there isn't because it's a guest session!). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-session-bin 3.2.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Tue Jul 10 09:54:55 2012 ExecutablePath: /usr/bin/gnome-session InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (compiz:1719): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed --- ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MarkForUpload: True Package: lightdm 1.2.1-0ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35 Tags: precise running-unity Uname: Linux 3.2.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1022858/+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 1923845] Re: Please compress packages with zstd by default
** Changed in: apt (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
New
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
In Progress
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
New
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
cowdancer - not affected, just documentation
eccodes - skip, just orig-data.tar.xz
eckit - skip, just ...orig-data.tar.xz
firefox - skip, profdata.tar.xz
firefox-esr - skip, profdata.tar.xz
galculator - skip, just changelog
grads - skip, ...orig-data.tar.xz
gvmd- skip, just creates xz compressed .deb
insighttoolkit4 - skip, ...orig-data.tar.xz
jdeb- skip, just creates compressed .deb packages
jmol- skip, just local data archive
jq
[Desktop-packages] [Bug 1925379] Re: Auto-Correct does not work since upgrade to Hirsute
Same thing here. This issue does not occur in Kubuntu 21.04, so perhaps it's something in the GTK stack? It doesn't seem to be a problem with LO per se. I even installed older versions, and they exhibited the same problem. This exact same issue occurred in Fedora Workstation (Gnome) a month or so ago, and after a couple of weeks was fixed - not sure what package since it was an updated of nearly 100 packages. -- 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/1925379 Title: Auto-Correct does not work since upgrade to Hirsute Status in libreoffice package in Ubuntu: New Bug description: I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, same LibreOffice profile, same LibreOffice document, and no changes on my part to my LibreOffice settings since I installed Ubuntu 21.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1925379/+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 1901391] Re: Ctrl+Alt+Shift+R screen recording not working anymore in 20.10 (Pipewire is now a requirement)
I'm on Ubuntu 21.04, upgraded to Gnome 40. My system should be fully up to date, but this problem is still there for me. Is this normal, or should the fix have reached my machine by now? I had the problem in 20.10 as well, though it worked on 20.04. Always in Wayland. When trying to run pipewire in the terminal I get the following error, which may or may not be related: ``` [E][02893.342993][module-protocol-native.c:578 lock_socket()] server 0x56383cd9dfe0: unable to lock lockfile '/run/user/1000/pipewire-0.lock': Resource temporarily unavailable (maybe another daemon is running) [E][02893.343190][conf.c:309 load_module()] config 0x56383cd834e0: could not load mandatory module "libpipewire-module-protocol-native": Resource temporarily unavailable [E][02893.343234][conf.c:383 create_object()] can't find factory spa-node-factory ``` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1901391 Title: Ctrl+Alt+Shift+R screen recording not working anymore in 20.10 (Pipewire is now a requirement) Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: I'm using gnome-shell with wayland (don't know if that matters), and, when I press CTRL-ALT-SHIFT-R, nothing happens. I checked my keyboard shortcuts, and this shortcut is supposed to trigger screencasting. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sun Oct 25 10:39:48 2020 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-07 (260 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-10-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1901391/+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 1925238] Re: [nvidia-prime] switches between xorg and wayland session
** Tags added: rls-hh-incoming -- 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/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. Performance mode is selected in nvidia-settings, which is supposed to mean nvidia & therefore xorg but it's not working. Selecting it explicitly doesn't help either. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+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 1925530] Re: Backport Metro Exodus Mesa fix into Hirsute
The fix will also (most likely) be included in Mesa 21.0.4 after it is released in a week or two. -- 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/1925530 Title: Backport Metro Exodus Mesa fix into Hirsute Status in One Hundred Papercuts: New Status in mesa package in Ubuntu: New Bug description: Please, consider backporting an important fix for "memory leak on descriptor pool reset with layout_size=0" into Ubuntu 21.04 Mesa. Without this fix, Metro Exodus and possibly other games cause system to hang or crash after playing for some time. Here is a MR with the fix: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10317 It is already staged to be backported into current stable Mesa releases and so it should be fine to apply it as a downstream patch for Mesa 21.0.1 in Ubuntu Hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1925530/+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 1925530] [NEW] Backport Metro Exodus Mesa fix into Hirsute
Public bug reported: Please, consider backporting an important fix for "memory leak on descriptor pool reset with layout_size=0" into Ubuntu 21.04 Mesa. Without this fix, Metro Exodus and possibly other games cause system to hang or crash after playing for some time. Here is a MR with the fix: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10317 It is already staged to be backported into current stable Mesa releases and so it should be fine to apply it as a downstream patch for Mesa 21.0.1 in Ubuntu Hirsute. ** Affects: hundredpapercuts Importance: Undecided Status: New ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute ** Also affects: hundredpapercuts Importance: Undecided Status: New ** Tags added: hirsute ** Description changed: Please, consider backporting an important fix for "memory leak on descriptor pool reset with layout_size=0" into Ubuntu 21.04 Mesa. Without this fix, Metro Exodus and possibly other games cause system to - hang on crash after playing for some time. + hang or crash after playing for some time. Here is a MR with the fix: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10317 It is already staged to be backported into current stable Mesa releases and so it should be fine to apply it as a downstream patch for Mesa 21.0.1 in Ubuntu Hirsute. -- 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/1925530 Title: Backport Metro Exodus Mesa fix into Hirsute Status in One Hundred Papercuts: New Status in mesa package in Ubuntu: New Bug description: Please, consider backporting an important fix for "memory leak on descriptor pool reset with layout_size=0" into Ubuntu 21.04 Mesa. Without this fix, Metro Exodus and possibly other games cause system to hang or crash after playing for some time. Here is a MR with the fix: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10317 It is already staged to be backported into current stable Mesa releases and so it should be fine to apply it as a downstream patch for Mesa 21.0.1 in Ubuntu Hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1925530/+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 1925651] [NEW] chromium snap snaps with SIGTERM
Public bug reported: LSB Version:core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS chromium 90.0.4430.721558 latest/stable canonical✓ - core18 202103091997 latest/stable canonical✓ base gnome-3-28-18043.28.0-19-g98f9e67.98f9e67 145latest/stable canonical✓ - gtk-common-themes 0.1-52-gb92ac40 1515 latest/stable canonical✓ - snapd 2.49.2 11588 latest/stable canonical✓ snapd random pages, chromium snaps no reload on any tab, only exit/quit I am using ubuntu with chromium since 2006 never been so bad I want chromium but want to kill snap for ever and not give a second chance If I cant have it, Iĺl just loose snap and chromium all together ! snap needs another 15 years of development for beta version. I consider it currently as alpha ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- 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/1925651 Title: chromium snap snaps with SIGTERM Status in chromium-browser package in Ubuntu: New Bug description: LSB Version: core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS chromium 90.0.4430.721558 latest/stable canonical✓ - core18 202103091997 latest/stable canonical✓ base gnome-3-28-18043.28.0-19-g98f9e67.98f9e67 145latest/stable canonical✓ - gtk-common-themes 0.1-52-gb92ac40 1515 latest/stable canonical✓ - snapd 2.49.2 11588 latest/stable canonical✓ snapd random pages, chromium snaps no reload on any tab, only exit/quit I am using ubuntu with chromium since 2006 never been so bad I want chromium but want to kill snap for ever and not give a second chance If I cant have it, Iĺl just loose snap and chromium all together ! snap needs another 15 years of development for beta version. I consider it currently as alpha To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1925651/+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 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
** Description changed:
+ [ Impact ]
+
+ As per glib commit
+ https://gitlab.gnome.org/GNOME/glib/-/commit/d52728f99
+ Gio.File.new_for_path("") returns a GDummyFile implementation, while
+ Gio._promisify relies on it being a LocalFile, so we don't promisify the
+ right methods.
+
+ [ Test case ]
+
+ gjs -c "imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype,
'delete_async', 'delete_finish');
+print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" &&
echo GJS works
+
+ Should write on terminal:
+
+ [object Promise]
+ GJS works
+
+ In the bugged version would instead just:
+
+ (gjs:226393): Gjs-CRITICAL **: 16:45:51.396: JS ERROR: TypeError: method
Gio.File.delete_async: At least 3 arguments required, but only 2 passed
+ @:2:48
+
+ (gjs:226393): Gjs-CRITICAL **: 16:45:51.396: Script threw
+ an exception
+
+
+ [ Regression potential ]
+
+ Gjs apps are slower in starting up, or not act properly when / is not a
+ local location.
+
+ ---
+
+
Problem tested in two different environments:
- - Ubuntu 21.04 Beta amd64
+ - Ubuntu 21.04 Beta amd64
- Ubuntu 21.04 Beta arm64 (Raspberry Pi 4B 8GB)
After upgrading these packages:
libglib2.0-02.67.5-2 to 2.68.0-1
libglib2.0-bin 2.67.5-2 to 2.68.0-1
libglib2.0-data 2.67.5-2 to 2.68.0-1
The app indicator-multiload (0.4-0ubuntu5) doesn't work showing only
three dots (...) instead of the graphic expected. It's throwing error
messages to the system journal every second or so (depends of the
refresh interval selected in the app settings):
abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]: multiload,
Impossible to read image from path '/run/user/1026/multiload-icons-
Wc8kck/icons/indicator-multiload-graphs-0.png': TypeError: method
Gio.File.read_async: At least 3 arguments required, but only 2 passed
Don't know if this is a documented change of that method and the bug
should be open for the indicator-multiload app. Please, if that's the
case just let me know to do it.
Thanks and best reagrds
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1923267
Title:
Gjs promises on Gio.File operations don't work anymore after upgrading
libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Status in gjs package in Ubuntu:
In Progress
Status in gnome-shell-extension-appindicator package in Ubuntu:
Won't Fix
Bug description:
[ Impact ]
As per glib commit
https://gitlab.gnome.org/GNOME/glib/-/commit/d52728f99
Gio.File.new_for_path("") returns a GDummyFile implementation, while
Gio._promisify relies on it being a LocalFile, so we don't promisify
the right methods.
[ Test case ]
gjs -c "imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype,
'delete_async', 'delete_finish');
print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" &&
echo GJS works
Should write on terminal:
[object Promise]
GJS works
In the bugged version would instead just:
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: JS ERROR: TypeError: method
Gio.File.delete_async: At least 3 arguments required, but only 2 passed
@:2:48
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: Script
threw an exception
[ Regression potential ]
Gjs apps are slower in starting up, or not act properly when / is not
a local location.
---
Problem tested in two different environments:
- Ubuntu 21.04 Beta amd64
- Ubuntu 21.04 Beta arm64 (Raspberry Pi 4B 8GB)
After upgrading these packages:
libglib2.0-02.67.5-2 to 2.68.0-1
libglib2.0-bin 2.67.5-2 to 2.68.0-1
libglib2.0-data 2.67.5-2 to 2.68.0-1
The app indicator-multiload (0.4-0ubuntu5) doesn't work showing only
three dots (...) instead of the graphic expected. It's throwing error
messages to the system journal every second or so (depends of the
refresh interval selected in the app settings):
abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]:
multiload, Impossible to read image from path '/run/user/1026
/multiload-icons-Wc8kck/icons/indicator-multiload-graphs-0.png':
TypeError: method Gio.File.read_async: At least 3 arguments required,
but only 2 passed
Don't know if this is a documented change of that method and the bug
should be open for the indicator-multiload app. Please, if that's the
case just let me know to do it.
Thanks and best reagrds
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+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 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
** Summary changed:
- indicator-multiload app broken after upgrading libglib2.0-0 2.67.5-2 to
2.68.0-1
+ Gjs promises on Gio.File operations don't work anymore after upgrading
libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1923267
Title:
Gjs promises on Gio.File operations don't work anymore after upgrading
libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Status in gjs package in Ubuntu:
In Progress
Status in gnome-shell-extension-appindicator package in Ubuntu:
Won't Fix
Bug description:
[ Impact ]
As per glib commit
https://gitlab.gnome.org/GNOME/glib/-/commit/d52728f99
Gio.File.new_for_path("") returns a GDummyFile implementation, while
Gio._promisify relies on it being a LocalFile, so we don't promisify
the right methods.
[ Test case ]
gjs -c "imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype,
'delete_async', 'delete_finish');
print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" &&
echo GJS works
Should write on terminal:
[object Promise]
GJS works
In the bugged version would instead just:
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: JS ERROR: TypeError: method
Gio.File.delete_async: At least 3 arguments required, but only 2 passed
@:2:48
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: Script
threw an exception
[ Regression potential ]
Gjs apps are slower in starting up, or not act properly when / is not
a local location.
---
Problem tested in two different environments:
- Ubuntu 21.04 Beta amd64
- Ubuntu 21.04 Beta arm64 (Raspberry Pi 4B 8GB)
After upgrading these packages:
libglib2.0-02.67.5-2 to 2.68.0-1
libglib2.0-bin 2.67.5-2 to 2.68.0-1
libglib2.0-data 2.67.5-2 to 2.68.0-1
The app indicator-multiload (0.4-0ubuntu5) doesn't work showing only
three dots (...) instead of the graphic expected. It's throwing error
messages to the system journal every second or so (depends of the
refresh interval selected in the app settings):
abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]:
multiload, Impossible to read image from path '/run/user/1026
/multiload-icons-Wc8kck/icons/indicator-multiload-graphs-0.png':
TypeError: method Gio.File.read_async: At least 3 arguments required,
but only 2 passed
Don't know if this is a documented change of that method and the bug
should be open for the indicator-multiload app. Please, if that's the
case just let me know to do it.
Thanks and best reagrds
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+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 1925518] [NEW] Evince is using 100% cpu
Public bug reported: Evince is using 100% cpu most likely related to https://bugs.launchpad.net/ubuntu/+source/evince/+bug/384062 removing pdf files from currently active "Files" window resolves issue ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1.2 ProcVersionSignature: Ubuntu 5.4.0-70.78~18.04.1-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 22 16:31:25 2021 InstallationDate: Installed on 2021-03-16 (36 days ago) InstallationMedia: Ubuntu 18.04.5 2020.11.30 LTS am "Custom Bionic Beaver" (20201130) KernLog: [685319.390960] SGI XFS with ACLs, security attributes, realtime, no debug enabled SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: Evince is using 100% cpu most likely related to https://bugs.launchpad.net/ubuntu/+source/evince/+bug/384062 + + removing pdf files from currently active "Files" window resolves issue + ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1.2 ProcVersionSignature: Ubuntu 5.4.0-70.78~18.04.1-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 22 16:31:25 2021 InstallationDate: Installed on 2021-03-16 (36 days ago) InstallationMedia: Ubuntu 18.04.5 2020.11.30 LTS am "Custom Bionic Beaver" (20201130) KernLog: [685319.390960] SGI XFS with ACLs, security attributes, realtime, no debug enabled SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1925518 Title: Evince is using 100% cpu Status in evince package in Ubuntu: New Bug description: Evince is using 100% cpu most likely related to https://bugs.launchpad.net/ubuntu/+source/evince/+bug/384062 removing pdf files from currently active "Files" window resolves issue ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1.2 ProcVersionSignature: Ubuntu 5.4.0-70.78~18.04.1-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 22 16:31:25 2021 InstallationDate: Installed on 2021-03-16 (36 days ago) InstallationMedia: Ubuntu 18.04.5 2020.11.30 LTS am "Custom Bionic Beaver" (20201130) KernLog: [685319.390960] SGI XFS with ACLs, security attributes, realtime, no debug enabled SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1925518/+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 1820859] Re: nautilus --version segfaults in g_application_impl_get_dbus_object_path
This bug was fixed in the package nautilus - 1:3.38.2-1ubuntu2 --- nautilus (1:3.38.2-1ubuntu2) hirsute; urgency=medium * d/p/19_unity_open_location_xid: - Do not update opened locations on bus connection. Nautilus may connect to the bus when the application is already about shut down, however at that point its implementation is destroyed but Gio doesn't handle this gracefully as per GNOME/GLib!2056. To prevent this, we can safely reduce the delta of the distro-patch by avoiding updating the opened locations on bus acquired, as we already do it in all the cases a window actually changes its state. (LP: #1820859) -- Marco Trevisan (Treviño) Wed, 21 Apr 2021 07:03:29 +0200 ** Changed in: nautilus (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- 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/1820859 Title: nautilus --version segfaults in g_application_impl_get_dbus_object_path Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Hirsute: Fix Released Bug description: * Impact nautilus hits a segfault when called with the version argument, which was annoying but became problematic in hirsute since the desktop icons ng calls that command to check if nautilus is available * Test case $ nautilus --version shouldn't segfault * Regression potential The change is in a patch which was added to expose open locations to Unity for the benefit of the launcher and which is also used by the dashtodock one now. Check that the launcher correctly indicates which windows are active, especially when dealing with external devices. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.31.90-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/8a8c9fc62039a8bb83a7ee530ac4140a9b8c29d9 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/ubuntu/+source/nautilus/+bug/1820859/+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 1918985] Re: Xorg crashed with SIGABRT (caught SIGSEGV) in libinput_device_config_send_events_get_modes(device=NULL) from LibinputApplyConfig() from LibinputSetProperty() from
This bug was fixed in the package xserver-xorg-input-libinput - 0.30.0-1ubuntu1 --- xserver-xorg-input-libinput (0.30.0-1ubuntu1) hirsute; urgency=medium * make-sure-device-is-valid.diff: Make sure the device is valid when setting the tap button map. (LP: #1918985) -- Timo Aaltonen Mon, 19 Apr 2021 11:52:07 +0300 ** Changed in: xserver-xorg-input-libinput (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1918985 Title: Xorg crashed with SIGABRT (caught SIGSEGV) in libinput_device_config_send_events_get_modes(device=NULL) from LibinputApplyConfig() from LibinputSetProperty() from XIChangeDeviceProperty() Status in xserver-xorg-input-libinput: Unknown Status in xserver-xorg-input-libinput package in Ubuntu: Fix Released Status in xserver-xorg-input-libinput source package in Hirsute: Fix Released Bug description: https://errors.ubuntu.com/problem/ca9c5dd3e5b0995fd1e275261512a4a7bd61f7e9 --- W: Fehlschlag beim Holen von http://de.archive.ubuntu.com/ubuntu/dists/hirsute/InRelease Verbindung fehlgeschlagen [IP: 141.30.62.24 80] W: Einige Indexdateien konnten nicht heruntergeladen werden. Sie wurden ignoriert oder alte an ihrer Stelle benutzt. ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: xserver-xorg-core 2:1.20.10-3ubuntu3 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 BootLog: Fr Mär 12 12:21:23 CET 2021 Fr Mär 12 22:40:02 CET 2021 CasperMD5CheckResult: unknown CompositorRunning: None Date: Fri Mar 12 23:05:07 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.39, 5.10.0-14-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) [103c:850d] InstallationDate: Installed on 2020-12-17 (85 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:5300 Quanta Computer, Inc. HP Wide Vision HD Camera Bus 001 Device 002: ID 1d57:fa60 Xenta 2.4G Wireless Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY x360 Convertible 15-cn1xxx ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/126/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3 ProcEnviron: Error: [Errno 13] Permission denied: 'environ' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=826c1aaa-9eb3-447b-aede-b8f0b5ef3ee2 ro recovery nomodeset dis_ucode_ldr ProcMaps: Error: [Errno 13] Permission denied: 'maps' Signal: 6 SourcePackage: xorg-server StacktraceTop: System () () () () () at /lib/x86_64-linux-gnu/libpthread.so.0 Title: Xorg crashed with SIGABRT in System() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A dmi.bios.date: 11/16/2020 dmi.bios.release: 15.24 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 850D dmi.board.vendor: HP dmi.board.version: 70.76 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 70.76 dmi.modalias: dmi:bvnInsyde:bvrF.24:bd11/16/2020:br15.24:efr70.76:svnHP:pnHPENVYx360Convertible15-cn1xxx:pvrType1ProductConfigId:rvnHP:rn850D:rvr70.76:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 15-cn1xxx dmi.product.sku: 5WA69EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.4-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.3.4-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-input-libinput/+bug/1918985/+subscriptions -- Mailing list: https://lau
[Desktop-packages] [Bug 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected
As a side note: headset mic was brought to life (tested for "headset- mode" model) on the 0x19 pin (as detected/configured by default) with specifically selecting "Not Present" for jack detection (in Advanced override tab). -- 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/1807138 Title: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Running the command alsamixer allows me to manually increase the sound levels for the headset, and sound plays properly through them. This requires me to disable the auto-mute feature. I haven't rebooted my system yet to see if this is permanent. But the UI doesn't show the heaphones at all and only sends sound through the main speakers of the laptop. ➜ ~ lspci -nnk | grep -i -A7 audio 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 ➜ ~ cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC256 Codec: Intel Kabylake HDMI Using for example pavucontrol allows me to select the headphone, which are marked as unplugged, and I can play audio through them as long as I keep the application open. If I reboot or close pavucontrol, everything is back to the original state and only the speakers work. Additional Information: ➜ ~ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 What I expect to happen: When I plug in my headphones, Ubuntu and the UI should see them and automatically redirect all sound through them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: olivar 8320 F...m pulseaudio /dev/snd/controlC0: olivar 8320 F pulseaudio CurrentDesktop: X-Cinnamon Date: Thu Dec 6 13:02:14 2018 InstallationDate: Installed on 2018-11-21 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: Razer dmi.bios.version: 01.01 dmi.board.name: DANA_MB dmi.board.vendor: Razer dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr: dmi.product.family: 1A582001 Razer Blade dmi.product.name: Blade dmi.product.version: 1.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1807138/+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 1925505] [NEW] package libgdk-pixbuf2.0-0:i386 2.40.0+dfsg-5ubuntu0.2 failed to install/upgrade: зацикливание триггеров, отмена работы
Public bug reported: just do something to solve it ProblemType: Package DistroRelease: Ubuntu 20.10 Package: libgdk-pixbuf2.0-0:i386 2.40.0+dfsg-5ubuntu0.2 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 22 22:55:45 2021 ErrorMessage: зацикливание триггеров, отмена работы InstallationDate: Installed on 2021-02-18 (63 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: i386 Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.3 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf2.0-0:i386 2.40.0+dfsg-5ubuntu0.2 failed to install/upgrade: зацикливание триггеров, отмена работы UpgradeStatus: Upgraded to groovy on 2021-04-22 (0 days ago) ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package groovy i386 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1925505 Title: package libgdk-pixbuf2.0-0:i386 2.40.0+dfsg-5ubuntu0.2 failed to install/upgrade: зацикливание триггеров, отмена работы Status in gdk-pixbuf package in Ubuntu: New Bug description: just do something to solve it ProblemType: Package DistroRelease: Ubuntu 20.10 Package: libgdk-pixbuf2.0-0:i386 2.40.0+dfsg-5ubuntu0.2 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 22 22:55:45 2021 ErrorMessage: зацикливание триггеров, отмена работы InstallationDate: Installed on 2021-02-18 (63 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: i386 Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.3 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf2.0-0:i386 2.40.0+dfsg-5ubuntu0.2 failed to install/upgrade: зацикливание триггеров, отмена работы UpgradeStatus: Upgraded to groovy on 2021-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1925505/+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 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected
I found a work-around that allows detection of headphones to work correctly. by changing model name of the codec to "headset-mode" from "headset-mic" in /etc/modprobe.d/alsa-base.conf However this did not solve the problem with headset mic, which is not working (tried all pins available from hdajackretask) for any of two of above specified model names. Alsa-info output: http://alsa- project.org/db/?f=5066c1fc285a210c75e5ef61712c35c2cce9efca -- 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/1807138 Title: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Running the command alsamixer allows me to manually increase the sound levels for the headset, and sound plays properly through them. This requires me to disable the auto-mute feature. I haven't rebooted my system yet to see if this is permanent. But the UI doesn't show the heaphones at all and only sends sound through the main speakers of the laptop. ➜ ~ lspci -nnk | grep -i -A7 audio 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 ➜ ~ cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC256 Codec: Intel Kabylake HDMI Using for example pavucontrol allows me to select the headphone, which are marked as unplugged, and I can play audio through them as long as I keep the application open. If I reboot or close pavucontrol, everything is back to the original state and only the speakers work. Additional Information: ➜ ~ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 What I expect to happen: When I plug in my headphones, Ubuntu and the UI should see them and automatically redirect all sound through them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: olivar 8320 F...m pulseaudio /dev/snd/controlC0: olivar 8320 F pulseaudio CurrentDesktop: X-Cinnamon Date: Thu Dec 6 13:02:14 2018 InstallationDate: Installed on 2018-11-21 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: Razer dmi.bios.version: 01.01 dmi.board.name: DANA_MB dmi.board.vendor: Razer dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr: dmi.product.family: 1A582001 Razer Blade dmi.product.name: Blade dmi.product.version: 1.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1807138/+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 1918985] Re: Xorg crashed with SIGABRT (caught SIGSEGV) in libinput_device_config_send_events_get_modes(device=NULL) from LibinputApplyConfig() from LibinputSetProperty() from
Hello Mahmoud, or anyone else affected, Accepted xserver-xorg-input-libinput into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /xserver-xorg-input-libinput/0.30.0-1ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! 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. ** Changed in: xserver-xorg-input-libinput (Ubuntu Hirsute) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1918985 Title: Xorg crashed with SIGABRT (caught SIGSEGV) in libinput_device_config_send_events_get_modes(device=NULL) from LibinputApplyConfig() from LibinputSetProperty() from XIChangeDeviceProperty() Status in xserver-xorg-input-libinput: Unknown Status in xserver-xorg-input-libinput package in Ubuntu: Fix Committed Status in xserver-xorg-input-libinput source package in Hirsute: Fix Committed Bug description: https://errors.ubuntu.com/problem/ca9c5dd3e5b0995fd1e275261512a4a7bd61f7e9 --- W: Fehlschlag beim Holen von http://de.archive.ubuntu.com/ubuntu/dists/hirsute/InRelease Verbindung fehlgeschlagen [IP: 141.30.62.24 80] W: Einige Indexdateien konnten nicht heruntergeladen werden. Sie wurden ignoriert oder alte an ihrer Stelle benutzt. ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: xserver-xorg-core 2:1.20.10-3ubuntu3 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 BootLog: Fr Mär 12 12:21:23 CET 2021 Fr Mär 12 22:40:02 CET 2021 CasperMD5CheckResult: unknown CompositorRunning: None Date: Fri Mar 12 23:05:07 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.39, 5.10.0-14-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) [103c:850d] InstallationDate: Installed on 2020-12-17 (85 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:5300 Quanta Computer, Inc. HP Wide Vision HD Camera Bus 001 Device 002: ID 1d57:fa60 Xenta 2.4G Wireless Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY x360 Convertible 15-cn1xxx ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/126/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3 ProcEnviron: Error: [Errno 13] Permission denied: 'environ' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=826c1aaa-9eb3-447b-aede-b8f0b5ef3ee2 ro recovery nomodeset dis_ucode_ldr ProcMaps: Error: [Errno 13] Permission denied: 'maps' Signal: 6 SourcePackage: xorg-server StacktraceTop: System () () () () () at /lib/x86_64-linux-gnu/libpthread.so.0 Title: Xorg crashed with SIGABRT in System() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A dmi.bios.date: 11/16/2020 dmi.bios.release: 15.24 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 850D dmi.board.vendor: HP dmi.board.version: 70.76 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 70.76 dmi.modalias: dmi:bvnInsyde:bvrF.24:bd11/16/2020:br15.24:
[Desktop-packages] [Bug 1820859] Re: nautilus --version segfaults in g_application_impl_get_dbus_object_path
Hello errors.ubuntu.com, or anyone else affected, Accepted nautilus into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nautilus/1:3.38.2-1ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! 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. ** Tags added: verification-needed verification-needed-hirsute -- 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/1820859 Title: nautilus --version segfaults in g_application_impl_get_dbus_object_path Status in nautilus package in Ubuntu: Fix Committed Status in nautilus source package in Hirsute: Fix Committed Bug description: * Impact nautilus hits a segfault when called with the version argument, which was annoying but became problematic in hirsute since the desktop icons ng calls that command to check if nautilus is available * Test case $ nautilus --version shouldn't segfault * Regression potential The change is in a patch which was added to expose open locations to Unity for the benefit of the launcher and which is also used by the dashtodock one now. Check that the launcher correctly indicates which windows are active, especially when dealing with external devices. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.31.90-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/8a8c9fc62039a8bb83a7ee530ac4140a9b8c29d9 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/ubuntu/+source/nautilus/+bug/1820859/+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 1925480] Re: [Patch] hp-systray doesn't support --qt5, but help message says it does
The attachment "Proposed patch" seems to be a patch. If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]
** Tags added: patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1925480
Title:
[Patch] hp-systray doesn't support --qt5, but help message says it
does
Status in HPLIP:
New
Status in hplip package in Ubuntu:
New
Status in hplip package in Fedora:
Unknown
Bug description:
Hi,
we have an issue in Fedora
(https://bugzilla.redhat.com/show_bug.cgi?id=1951922) regarding hp-
systray. Its help page ('hp-systray -h') says:
```
[OPTIONS]
Use Qt5:--qt5 (Default)
```
but once you run 'hp-systray --qt5', you get:
```
error: option --qt5 not recognized
```
It is because 'setUsage()' automatically creates the option in help
message if hplip is compiled with GUI, 'parseStdOpt()' doesn't add it
to the list of approved options.
The attached patch fixes the issue.
Ubuntu 20.04 is affected too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1925480/+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 1918855] Re: Xorg xserver got signal 6 to abort
Re-attach full dmesg log with this issue reproduced on RKL SDP (202102-28687) running 5.12-rc8. ** Attachment added: "journalctl.RKL-SDP.5.12.0-8-generic.gz" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1918855/+attachment/5490979/+files/journalctl.RKL-SDP.5.12.0-8-generic.gz ** Attachment removed: "dmesg.RKL-SDP.5.12.0-8-generic" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1918855/+attachment/5490918/+files/dmesg.RKL-SDP.5.12.0-8-generic -- 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/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+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 1924757] Re: Ubuntu debug mirror is out of sync
** Package changed: ubuntu => mesa (Ubuntu) -- 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/1924757 Title: Ubuntu debug mirror is out of sync Status in mesa package in Ubuntu: Confirmed Bug description: lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 When using the Ubuntu debug mirror (ddebs.ubuntu.com) and the official mirror (archive.ubuntu.com), it is not possible to install some debug symbols. For example: apt install mesa-vulkan-drivers-dbgsym Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mesa-vulkan-drivers-dbgsym : Depends: mesa-vulkan-drivers (= 20.0.4-2ubuntu1) but 20.2.6-0ubuntu0.20.04.1 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1924757/+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 1918855] Re: Xorg xserver got signal 6 to abort
Reproduce with kernel cod/tip/drm-tip/2021-04-22 Mainline on hirsute. ** Attachment added: "sosreport-u-Inspiron-3891-2021-04-22-rurdrvj.tar.xz" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1918855/+attachment/5490976/+files/sosreport-u-Inspiron-3891-2021-04-22-rurdrvj.tar.xz -- 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/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+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 1918855] Re: Xorg xserver got signal 6 to abort
Attach also dmesg from drm-tip today, version 5.12.0-051200rc8drmtip20210422-generic on RKL SDP installed Focal. Also using linux-firmware from upstream master HEAD. ** Attachment added: "journalctl.5.12.0-051200rc8drmtip20210422-generic.gz" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1918855/+attachment/5490974/+files/journalctl.5.12.0-051200rc8drmtip20210422-generic.gz -- 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/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+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 1925480] [NEW] [Patch] hp-systray doesn't support --qt5, but help message says it does
Public bug reported:
Hi,
we have an issue in Fedora
(https://bugzilla.redhat.com/show_bug.cgi?id=1951922) regarding hp-
systray. Its help page ('hp-systray -h') says:
```
[OPTIONS]
Use Qt5:--qt5 (Default)
```
but once you run 'hp-systray --qt5', you get:
```
error: option --qt5 not recognized
```
It is because 'setUsage()' automatically creates the option in help
message if hplip is compiled with GUI, 'parseStdOpt()' doesn't add it to
the list of approved options.
The attached patch fixes the issue.
Ubuntu 20.04 is affected too.
** Affects: hplip
Importance: Undecided
Status: New
** Affects: hplip (Ubuntu)
Importance: Undecided
Status: New
** Affects: hplip (Fedora)
Importance: Unknown
Status: Unknown
** Patch added: "Proposed patch"
https://bugs.launchpad.net/bugs/1925480/+attachment/5490977/+files/hplip-systray-qt5.patch
** Also affects: hplip (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: Red Hat Bugzilla #1951922
https://bugzilla.redhat.com/show_bug.cgi?id=1951922
** Also affects: hplip (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1951922
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1925480
Title:
[Patch] hp-systray doesn't support --qt5, but help message says it
does
Status in HPLIP:
New
Status in hplip package in Ubuntu:
New
Status in hplip package in Fedora:
Unknown
Bug description:
Hi,
we have an issue in Fedora
(https://bugzilla.redhat.com/show_bug.cgi?id=1951922) regarding hp-
systray. Its help page ('hp-systray -h') says:
```
[OPTIONS]
Use Qt5:--qt5 (Default)
```
but once you run 'hp-systray --qt5', you get:
```
error: option --qt5 not recognized
```
It is because 'setUsage()' automatically creates the option in help
message if hplip is compiled with GUI, 'parseStdOpt()' doesn't add it
to the list of approved options.
The attached patch fixes the issue.
Ubuntu 20.04 is affected too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1925480/+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 1924757] [NEW] Ubuntu debug mirror is out of sync
You have been subscribed to a public bug: lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 When using the Ubuntu debug mirror (ddebs.ubuntu.com) and the official mirror (archive.ubuntu.com), it is not possible to install some debug symbols. For example: apt install mesa-vulkan-drivers-dbgsym Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mesa-vulkan-drivers-dbgsym : Depends: mesa-vulkan-drivers (= 20.0.4-2ubuntu1) but 20.2.6-0ubuntu0.20.04.1 is to be installed E: Unable to correct problems, you have held broken packages. ** Affects: mesa (Ubuntu) Importance: Undecided Status: Confirmed -- Ubuntu debug mirror is out of sync https://bugs.launchpad.net/bugs/1924757 You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. -- 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 1925467] [NEW] stack-buffer-overflow of text.c in function _import_ansi
*** This bug is a security vulnerability ***
Public security bug reported:
Hello ubuntu security team
System info：
Ubuntu 20.04 : clang 10.0.0 , gcc 9.3.0
Fedora 33: clang 11.0.0 , gcc 10.2.1
libcaca version e4968ba
Verification steps：
1.Get the source code of libcaca
2.Compile the libcaca.so library
$ cd libcaca
$ ./bootstrap
$ ./configure
$ make
or
$ cd libcaca
$ ./bootstrap
$ ../configure CC="clang -O2 -fno-omit-frame-pointer -g
-fsanitize=address,fuzzer-no-link -fsanitize-coverage=bb" CXX="clang++ -O2
-fno-omit-frame-pointer -g -fsanitize=address,fuzzer-no-link
-fsanitize-coverage=bb"
$ make
3.Create the poc_ansi.cc && build
#include "config.h"
#include "caca.h"
//#include "common-image.h"
#include
#include
#include
#include
#include
#include
using namespace std;
void crash(const uint8_t *Data, size_t Size) {
if(Size<8) return ;
size_t len=0;
caca_canvas_t *cv;
cv = caca_create_canvas(0,0);
caca_create_frame(cv,0);
caca_set_frame(cv,0);
caca_import_canvas_from_memory(cv,Data,Size,"ansi");
caca_free_canvas(cv);
cv=NULL;
}
int main(int args,char* argv[]){
size_t len = 0;
unsigned char buffer[] =
{0x20,0x4a,0x0c,0x0a,0x20,0x0a,0x20,0x0c,0xc,0xc};
len = sizeof(buffer)/sizeof(unsigned char);
printf("%d\n",sizeof(buffer)/sizeof(unsigned char));
crash((const uint8_t*)buffer,len);
return 0;
}
4.compile poc_ansi.cc
clang++ -g poc_ansi.cc -O2 -fno-omit-frame-pointer -fsanitize=address
-I./caca/ -lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/ -o poc_ansi
5.Run poc_ansi
asan info:
=
==3763372==ERROR: AddressSanitizer: stack-buffer-overflow on address
0x7ffda0164bea at pc 0x7f098d82c310 bp 0x7ffda01647b0 sp 0x7ffda01647a8
READ of size 1 at 0x7ffda0164bea thread T0
#0 0x7f098d82c30f in _import_ansi
/home/hh/Downloads/libcaca/caca/codec/text.c:391:38
#1 0x4c6c72 in crash(unsigned char const*, unsigned long)
/home/hh/Downloads/libcaca/poc_bin.cc:21:3
#2 0x4c6c72 in main /home/hh/Downloads/libcaca/poc_bin.cc:34:9
#3 0x7f098d2780b2 in __libc_start_main
/build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16
#4 0x41c38d in _start (/home/hh/Downloads/libcaca/poc_mbay+0x41c38d)
Address 0x7ffda0164bea is located in stack of thread T0 at offset 42 in frame
#0 0x4c6b9f in main /home/hh/Downloads/libcaca/poc_bin.cc:28
This frame has 1 object(s):
[32, 42) 'buffer' (line 31) <== Memory access at offset 42 overflows this
variable
HINT: this may be a false positive if your program uses some custom stack
unwind mechanism, swapcontext or vfork
(longjmp and C++ exceptions *are* supported)
SUMMARY: AddressSanitizer: stack-buffer-overflow
/home/hh/Downloads/libcaca/caca/codec/text.c:391:38 in _import_ansi
Shadow bytes around the buggy address:
0x100034024920: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
0x100034024930: f8 f8 f8 f8 f8 f8 f8 f8 f8 f2 f2 f2 f2 f2 f2 f2
0x100034024940: f2 f2 f8 f2 f2 f2 f8 f3 f3 f3 f3 f3 00 00 00 00
0x100034024950: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x100034024960: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x100034024970: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00[02]f3 f3
0x100034024980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x100034024990: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1000340249a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1000340249b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1000340249c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user:f7
Container overflow: fc
Array cookie:ac
Intra object redzone:bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone:cb
Shadow gap: cc
==3763372==ABORTING
Thanks
** Affects: libcaca (Ubuntu)
Importance: Undecided
Status: New
** Information type changed from Public to Public Security
--
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/1925467
Title:
stack-buffer-overflow of text.c in function _import_ansi
Status in libcaca package in Ubuntu:
New
Bug description:
Hello ubuntu security team
System info：
Ubuntu 20.04 : clang 10.0.0 , gcc 9.3.0
Fedora 33: clang 11.0.0 , gcc 10.2.1
libcaca version e4968ba
Verification steps：
1.Get the source code of libcaca
2.Compile the libcaca.so library
$ cd libcaca
$ ./bootstrap
$
[Desktop-packages] [Bug 1925464] [NEW] Cannot open /boot/efi
Public bug reported: Get this error message when trying to open /boot/efi "gdbus error freedesktop policykit1 error failed unix process subject does not have uuid set" ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 22 12:24:31 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'355' b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" 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-22 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) 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 wayland-session ** Attachment added: "error message" https://bugs.launchpad.net/bugs/1925464/+attachment/5490958/+files/Screenshot%20from%202021-04-22%2012-29-55.png -- 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/1925464 Title: Cannot open /boot/efi Status in nautilus package in Ubuntu: New Bug description: Get this error message when trying to open /boot/efi "gdbus error freedesktop policykit1 error failed unix process subject does not have uuid set" ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 22 12:24:31 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'355' b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" 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-22 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) 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/1925464/+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 1925468] [NEW] stack-buffer-overflow of import.c in function _import_bin
*** This bug is a security vulnerability ***
Public security bug reported:
Hello ubuntu security team
System info：
Ubuntu 20.04 : clang 10.0.0 , gcc 9.3.0
Fedora 33: clang 11.0.0 , gcc 10.2.1
libcaca version e4968ba
Verification steps：
1.Get the source code of libcaca
2.Compile the libcaca.so library
$ cd libcaca
$ ./bootstrap
$ ./configure
$ make
or
$ cd libcaca
$ ./bootstrap
$ ../configure CC="clang -O2 -fno-omit-frame-pointer -g
-fsanitize=address,fuzzer-no-link -fsanitize-coverage=bb" CXX="clang++ -O2
-fno-omit-frame-pointer -g -fsanitize=address,fuzzer-no-link
-fsanitize-coverage=bb"
$ make
3.Create the poc_bin.cc && build
#include "config.h"
#include "caca.h"
//#include "common-image.h"
#include
#include
#include
#include
#include
#include
using namespace std;
void crash(const uint8_t *Data, size_t Size) {
if(Size<8) return ;
size_t len=0;
caca_canvas_t *cv;
cv = caca_create_canvas(0,0);
caca_create_frame(cv,0);
caca_set_frame(cv,0);
caca_import_canvas_from_memory(cv,Data,Size,"bin");
caca_free_canvas(cv);
cv=NULL;
}
int main(int args,char* argv[]){
size_t len = 0;
unsigned char buffer[] =
{0x0a,0x20,0x0a,0x0a,0x20,0x20,0x20,0x20,0x20,0x20,0x47,0x47,0x47};
len = sizeof(buffer)/sizeof(unsigned char);
printf("%d\n",sizeof(buffer)/sizeof(unsigned char));
crash((const uint8_t*)buffer,len);
return 0;
}
4.compile poc_bin.cc
clang++ -g poc_bin.cc -O2 -fno-omit-frame-pointer -fsanitize=address -I./caca/
-lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/ -o poc_bin
5.Run poc_bin
asan info:
=
==3817476==ERROR: AddressSanitizer: stack-buffer-overflow on address
0x7ffe7cd3774d at pc 0x7f8c6314acfd bp 0x7ffe7cd376c0 sp 0x7ffe7cd376b8
READ of size 1 at 0x7ffe7cd3774d thread T0
#0 0x7f8c6314acfc in _import_bin
/home/hh/Downloads/libcaca/caca/codec/import.c:425:33
#1 0x4c6c72 in crash(unsigned char const*, unsigned long)
/home/hh/Downloads/libcaca/poc_bin.cc:21:3
#2 0x4c6c72 in main /home/hh/Downloads/libcaca/poc_bin.cc:34:9
#3 0x7f8c62ba00b2 in __libc_start_main
/build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16
#4 0x41c38d in _start (/home/hh/Downloads/libcaca/poc_bin+0x41c38d)
Address 0x7ffe7cd3774d is located in stack of thread T0 at offset 45 in frame
#0 0x4c6b9f in main /home/hh/Downloads/libcaca/poc_bin.cc:28
This frame has 1 object(s):
[32, 45) 'buffer' (line 31) <== Memory access at offset 45 overflows this
variable
HINT: this may be a false positive if your program uses some custom stack
unwind mechanism, swapcontext or vfork
(longjmp and C++ exceptions *are* supported)
SUMMARY: AddressSanitizer: stack-buffer-overflow
/home/hh/Downloads/libcaca/caca/codec/import.c:425:33 in _import_bin
Shadow bytes around the buggy address:
0x10004f99ee90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99eea0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99eeb0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99eec0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99eed0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x10004f99eee0: 00 00 00 00 f1 f1 f1 f1 00[05]f3 f3 00 00 00 00
0x10004f99eef0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99ef00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99ef10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99ef20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99ef30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user:f7
Container overflow: fc
Array cookie:ac
Intra object redzone:bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone:cb
Shadow gap: cc
==3817476==ABORTING
Thanks
** Affects: libcaca (Ubuntu)
Importance: Undecided
Status: New
** Information type changed from Public to Public Security
--
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/1925468
Title:
stack-buffer-overflow of import.c in function _import_bin
Status in libcaca package in Ubuntu:
New
Bug description:
Hello ubuntu security team
System info：
Ubuntu 20.04 : clang 10.0.0 , gcc 9.3.0
Fedora 33: clang 11.0.0 , gcc 10.2.1
libcaca version e4968ba
Verification steps：
1.Get the source code of libcaca
2.Compile the libcaca.so library
$ cd libcaca
$ ./bo
[Desktop-packages] [Bug 1861408] Re: firefox apparmor messages
Updated again for Python 3.9:
https://bazaar.launchpad.net/~mozillateam/firefox/firefox.hirsute/revision/1489
--
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/1861408
Title:
firefox apparmor messages
Status in apparmor package in Ubuntu:
New
Status in firefox package in Ubuntu:
Fix Released
Bug description:
firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
19.3.
i see there is newer ubuntu version in
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
, 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
apparmor.
i have not found a page for firefox bugs in linux mint sites, so i
belive i should report here. but i have also asked about that in linux
mint's irc and then github.
i have enabled apparmor for firefox and see these types of messages in
syslog:
Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")
Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5525.077960] audit: type=1400 audit(1580226276.440:27):
apparmor="DENIED" operation="capable"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
comm="firefox" capability=21 capname="sys_admin"
Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/RealtimeKit1"
interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
name="org.freedesktop.RealtimeKit1" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/Private/RemoteVolumeMonitor"
interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
mask="send" name=":1.35" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="ListMounts2" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="LookupMount" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000
pid=15948 comm="/usr/lib/firefox/firefox "
label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)")
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/hostname1"
interface="org.freedesktop.DBus.Properties" member="GetAll"
mask="send" name=":1.120" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=16177
peer_label="unconfined"
Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer"
member="Change" mask="send" name="ca.desrt.dconf" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1370
peer_label="unconfined"
Jan 28 21:51:30 dinar-HP-Pavilion-g7-Notebook-PC kernel:
[10131.880788] audit: type=1400 audit(1580237490.777:123):
apparmor="DENIED" operation="open"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/dinar/.cache/mesa_shader_cache/index" pid=19720
comm="firefox" requested_mask="wrc" denied_mask="wrc" fsuid=1000
ouid=1000
these appeared while saving a file:
Jan 30
[Desktop-packages] [Bug 1861408] Re: firefox apparmor messages
** Branch linked: lp:firefox
--
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/1861408
Title:
firefox apparmor messages
Status in apparmor package in Ubuntu:
New
Status in firefox package in Ubuntu:
Fix Released
Bug description:
firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
19.3.
i see there is newer ubuntu version in
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
, 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
apparmor.
i have not found a page for firefox bugs in linux mint sites, so i
belive i should report here. but i have also asked about that in linux
mint's irc and then github.
i have enabled apparmor for firefox and see these types of messages in
syslog:
Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")
Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5525.077960] audit: type=1400 audit(1580226276.440:27):
apparmor="DENIED" operation="capable"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
comm="firefox" capability=21 capname="sys_admin"
Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/RealtimeKit1"
interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
name="org.freedesktop.RealtimeKit1" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/Private/RemoteVolumeMonitor"
interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
mask="send" name=":1.35" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="ListMounts2" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="LookupMount" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000
pid=15948 comm="/usr/lib/firefox/firefox "
label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)")
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/hostname1"
interface="org.freedesktop.DBus.Properties" member="GetAll"
mask="send" name=":1.120" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=16177
peer_label="unconfined"
Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer"
member="Change" mask="send" name="ca.desrt.dconf" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1370
peer_label="unconfined"
Jan 28 21:51:30 dinar-HP-Pavilion-g7-Notebook-PC kernel:
[10131.880788] audit: type=1400 audit(1580237490.777:123):
apparmor="DENIED" operation="open"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/dinar/.cache/mesa_shader_cache/index" pid=19720
comm="firefox" requested_mask="wrc" denied_mask="wrc" fsuid=1000
ouid=1000
these appeared while saving a file:
Jan 30 11:08:28 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1151]:
apparmor="DENIED"
[Desktop-packages] [Bug 1925392] Re: firefox remote on wayland/dbus does not work
Fixed with
https://bazaar.launchpad.net/~mozillateam/firefox/firefox.hirsute/revision/1488.
** Changed in: firefox (Ubuntu)
Status: Confirmed => Fix Committed
--
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/1925392
Title:
firefox remote on wayland/dbus does not work
Status in firefox package in Ubuntu:
Fix Committed
Bug description:
[agnew(~)] lsb_release -rc
Release:21.04
Codename: hirsute
[agnew(~)] dpkg-query -W firefox
firefox 87.0+build3-0ubuntu4
[agnew(~)]
Attempting to open links with `firefox $URL` times out and gives me
the old familiar profile-locked error dialog.
As far as I can tell, all of the ducks are lined up correctly (thanks
to the fix for LP:1921931)
[agnew(~)] tr \\0 \\n < /proc/$(pgrep -x firefox)/environ | egrep -i
'dbus|wayland'
XDG_SESSION_TYPE=wayland
MOZ_ENABLE_WAYLAND=1
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
MOZ_DBUS_REMOTE=1
WAYLAND_DISPLAY=wayland-0
XAUTHORITY=/run/user/1000/.mutter-Xwaylandauth.QKTZ10
[agnew(~)] sh -x $(which firefox) https://ubuntu.com/
+ set -e
+ MOZ_LIBDIR=/usr/lib/firefox
+ which /usr/bin/firefox
+ MOZ_APP_LAUNCHER=/usr/bin/firefox
+ MOZ_APP_NAME=firefox
+ export MOZ_APP_LAUNCHER
+ [ wayland = wayland ]
+ export MOZ_ENABLE_WAYLAND=1
+ export MOZ_DBUS_REMOTE=1
+ [ ! -x /usr/lib/firefox/firefox ]
+ moz_debug=0
+ moz_debugger_args=
+ moz_debugger=gdb
+ [ 1 -gt 0 ]
+ break
+ [ 0 -eq 1 ]
+ exec /usr/lib/firefox/firefox https://ubuntu.com/
[GFX1-]: No GPUs detected via PCI
[GFX1-]: glxtest: process failed (received signal 11)
(firefox:60063): Gtk-WARNING **: 10:09:52.171: Loading IM context type
'xim' failed
(firefox:60063): Gtk-WARNING **: 10:09:52.174: Loading IM context type
'xim' failed
(firefox:60063): Gtk-WARNING **: 10:09:52.179: Loading IM context type
'xim' failed
(firefox:60063): Gtk-WARNING **: 10:09:52.179: Loading IM context type
'xim' failed
(firefox:60063): Gtk-WARNING **: 10:09:52.197: Loading IM context type
'xim' failed
(firefox:60063): Gtk-WARNING **: 10:09:52.199: Loading IM context type
'xim' failed
###!!! [Parent][RunMessage] Error: Channel closing: too late to
send/recv, messages will be lost
[agnew(~)]
However, on dbus-monitor, I see:
method call time=1619043038.755430 sender=:1.392 ->
destination=org.mozilla.firefox.ZGVmYXVsdA__ serial=2
path=/org/mozilla/firefox/Remote; interface=org.mozilla.firefox; member=OpenURL
array of bytes [
02 00 00 00 17 00 00 00 30 00 00 00 2f 68 6f 6d 65 2f 70 61 75 6c 00 2f
75 73 72 2f 6c 69 62 2f 66 69 72 65 66 6f 78 2f 66 69 72 65 66 6f 78 00
68 74 74 70 73 3a 2f 2f 75 62 75 6e 74 75 2e 63 6f 6d 2f 00
]
error time=1619043038.755479 sender=org.freedesktop.DBus ->
destination=:1.392 error_name=org.freedesktop.DBus.Error.ServiceUnknown
reply_serial=2
string "The name org.mozilla.firefox.ZGVmYXVsdA__ was not provided by any
.service files"
And, indeed, firefox is not listening on that name (which is correct
for my profile, "default") or indeed any other such name:
[agnew(~)] busctl --user | grep -i firefox
:1.162 54607
firefox paul :1.162user@1000.service - -
:1.163 54607
firefox paul :1.163user@1000.service - -
[agnew(~)] _
---
ProblemType: Bug
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: paul 3311 F pulseaudio
/dev/snd/controlC1: paul 3311 F pulseaudio
BuildID: 20210318103112
CasperMD5CheckResult: unknown
Channel: Unavailable
CurrentDesktop: GNOME
DefaultProfileIncompatibleExtensions: Default -
{972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:352
DefaultProfilePrefSources:
/usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js
prefs.js
DistroRelease: Ubuntu 21.04
ForcedLayersAccel: False
InstallationDate: Installed on 2011-11-06 (3454 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: firefox 87.0+build3-0ubuntu4
PackageArchitecture: amd64
ProcCmdline: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic
root=UUID=617752e9-3054-4928-881c-0e0651a839b0 ro splash quiet vt.handoff=7
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile1Locales: exten
[Desktop-packages] [Bug 1925392] Re: firefox remote on wayland/dbus does not work
** Branch linked: lp:firefox
--
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/1925392
Title:
firefox remote on wayland/dbus does not work
Status in firefox package in Ubuntu:
Fix Committed
Bug description:
[agnew(~)] lsb_release -rc
Release:21.04
Codename: hirsute
[agnew(~)] dpkg-query -W firefox
firefox 87.0+build3-0ubuntu4
[agnew(~)]
Attempting to open links with `firefox $URL` times out and gives me
the old familiar profile-locked error dialog.
As far as I can tell, all of the ducks are lined up correctly (thanks
to the fix for LP:1921931)
[agnew(~)] tr \\0 \\n < /proc/$(pgrep -x firefox)/environ | egrep -i
'dbus|wayland'
XDG_SESSION_TYPE=wayland
MOZ_ENABLE_WAYLAND=1
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
MOZ_DBUS_REMOTE=1
WAYLAND_DISPLAY=wayland-0
XAUTHORITY=/run/user/1000/.mutter-Xwaylandauth.QKTZ10
[agnew(~)] sh -x $(which firefox) https://ubuntu.com/
+ set -e
+ MOZ_LIBDIR=/usr/lib/firefox
+ which /usr/bin/firefox
+ MOZ_APP_LAUNCHER=/usr/bin/firefox
+ MOZ_APP_NAME=firefox
+ export MOZ_APP_LAUNCHER
+ [ wayland = wayland ]
+ export MOZ_ENABLE_WAYLAND=1
+ export MOZ_DBUS_REMOTE=1
+ [ ! -x /usr/lib/firefox/firefox ]
+ moz_debug=0
+ moz_debugger_args=
+ moz_debugger=gdb
+ [ 1 -gt 0 ]
+ break
+ [ 0 -eq 1 ]
+ exec /usr/lib/firefox/firefox https://ubuntu.com/
[GFX1-]: No GPUs detected via PCI
[GFX1-]: glxtest: process failed (received signal 11)
(firefox:60063): Gtk-WARNING **: 10:09:52.171: Loading IM context type
'xim' failed
(firefox:60063): Gtk-WARNING **: 10:09:52.174: Loading IM context type
'xim' failed
(firefox:60063): Gtk-WARNING **: 10:09:52.179: Loading IM context type
'xim' failed
(firefox:60063): Gtk-WARNING **: 10:09:52.179: Loading IM context type
'xim' failed
(firefox:60063): Gtk-WARNING **: 10:09:52.197: Loading IM context type
'xim' failed
(firefox:60063): Gtk-WARNING **: 10:09:52.199: Loading IM context type
'xim' failed
###!!! [Parent][RunMessage] Error: Channel closing: too late to
send/recv, messages will be lost
[agnew(~)]
However, on dbus-monitor, I see:
method call time=1619043038.755430 sender=:1.392 ->
destination=org.mozilla.firefox.ZGVmYXVsdA__ serial=2
path=/org/mozilla/firefox/Remote; interface=org.mozilla.firefox; member=OpenURL
array of bytes [
02 00 00 00 17 00 00 00 30 00 00 00 2f 68 6f 6d 65 2f 70 61 75 6c 00 2f
75 73 72 2f 6c 69 62 2f 66 69 72 65 66 6f 78 2f 66 69 72 65 66 6f 78 00
68 74 74 70 73 3a 2f 2f 75 62 75 6e 74 75 2e 63 6f 6d 2f 00
]
error time=1619043038.755479 sender=org.freedesktop.DBus ->
destination=:1.392 error_name=org.freedesktop.DBus.Error.ServiceUnknown
reply_serial=2
string "The name org.mozilla.firefox.ZGVmYXVsdA__ was not provided by any
.service files"
And, indeed, firefox is not listening on that name (which is correct
for my profile, "default") or indeed any other such name:
[agnew(~)] busctl --user | grep -i firefox
:1.162 54607
firefox paul :1.162user@1000.service - -
:1.163 54607
firefox paul :1.163user@1000.service - -
[agnew(~)] _
---
ProblemType: Bug
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: paul 3311 F pulseaudio
/dev/snd/controlC1: paul 3311 F pulseaudio
BuildID: 20210318103112
CasperMD5CheckResult: unknown
Channel: Unavailable
CurrentDesktop: GNOME
DefaultProfileIncompatibleExtensions: Default -
{972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:352
DefaultProfilePrefSources:
/usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js
prefs.js
DistroRelease: Ubuntu 21.04
ForcedLayersAccel: False
InstallationDate: Installed on 2011-11-06 (3454 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: firefox 87.0+build3-0ubuntu4
PackageArchitecture: amd64
ProcCmdline: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic
root=UUID=617752e9-3054-4928-881c-0e0651a839b0 ro splash quiet vt.handoff=7
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:grepre
[Desktop-packages] [Bug 1925392] Re: firefox remote on wayland/dbus does not work
Very good catch, thank you Paul!
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
** Changed in: firefox (Ubuntu)
Importance: Undecided => High
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
--
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/1925392
Title:
firefox remote on wayland/dbus does not work
Status in firefox package in Ubuntu:
Confirmed
Bug description:
[agnew(~)] lsb_release -rc
Release:21.04
Codename: hirsute
[agnew(~)] dpkg-query -W firefox
firefox 87.0+build3-0ubuntu4
[agnew(~)]
Attempting to open links with `firefox $URL` times out and gives me
the old familiar profile-locked error dialog.
As far as I can tell, all of the ducks are lined up correctly (thanks
to the fix for LP:1921931)
[agnew(~)] tr \\0 \\n < /proc/$(pgrep -x firefox)/environ | egrep -i
'dbus|wayland'
XDG_SESSION_TYPE=wayland
MOZ_ENABLE_WAYLAND=1
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
MOZ_DBUS_REMOTE=1
WAYLAND_DISPLAY=wayland-0
XAUTHORITY=/run/user/1000/.mutter-Xwaylandauth.QKTZ10
[agnew(~)] sh -x $(which firefox) https://ubuntu.com/
+ set -e
+ MOZ_LIBDIR=/usr/lib/firefox
+ which /usr/bin/firefox
+ MOZ_APP_LAUNCHER=/usr/bin/firefox
+ MOZ_APP_NAME=firefox
+ export MOZ_APP_LAUNCHER
+ [ wayland = wayland ]
+ export MOZ_ENABLE_WAYLAND=1
+ export MOZ_DBUS_REMOTE=1
+ [ ! -x /usr/lib/firefox/firefox ]
+ moz_debug=0
+ moz_debugger_args=
+ moz_debugger=gdb
+ [ 1 -gt 0 ]
+ break
+ [ 0 -eq 1 ]
+ exec /usr/lib/firefox/firefox https://ubuntu.com/
[GFX1-]: No GPUs detected via PCI
[GFX1-]: glxtest: process failed (received signal 11)
(firefox:60063): Gtk-WARNING **: 10:09:52.171: Loading IM context type
'xim' failed
(firefox:60063): Gtk-WARNING **: 10:09:52.174: Loading IM context type
'xim' failed
(firefox:60063): Gtk-WARNING **: 10:09:52.179: Loading IM context type
'xim' failed
(firefox:60063): Gtk-WARNING **: 10:09:52.179: Loading IM context type
'xim' failed
(firefox:60063): Gtk-WARNING **: 10:09:52.197: Loading IM context type
'xim' failed
(firefox:60063): Gtk-WARNING **: 10:09:52.199: Loading IM context type
'xim' failed
###!!! [Parent][RunMessage] Error: Channel closing: too late to
send/recv, messages will be lost
[agnew(~)]
However, on dbus-monitor, I see:
method call time=1619043038.755430 sender=:1.392 ->
destination=org.mozilla.firefox.ZGVmYXVsdA__ serial=2
path=/org/mozilla/firefox/Remote; interface=org.mozilla.firefox; member=OpenURL
array of bytes [
02 00 00 00 17 00 00 00 30 00 00 00 2f 68 6f 6d 65 2f 70 61 75 6c 00 2f
75 73 72 2f 6c 69 62 2f 66 69 72 65 66 6f 78 2f 66 69 72 65 66 6f 78 00
68 74 74 70 73 3a 2f 2f 75 62 75 6e 74 75 2e 63 6f 6d 2f 00
]
error time=1619043038.755479 sender=org.freedesktop.DBus ->
destination=:1.392 error_name=org.freedesktop.DBus.Error.ServiceUnknown
reply_serial=2
string "The name org.mozilla.firefox.ZGVmYXVsdA__ was not provided by any
.service files"
And, indeed, firefox is not listening on that name (which is correct
for my profile, "default") or indeed any other such name:
[agnew(~)] busctl --user | grep -i firefox
:1.162 54607
firefox paul :1.162user@1000.service - -
:1.163 54607
firefox paul :1.163user@1000.service - -
[agnew(~)] _
---
ProblemType: Bug
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: paul 3311 F pulseaudio
/dev/snd/controlC1: paul 3311 F pulseaudio
BuildID: 20210318103112
CasperMD5CheckResult: unknown
Channel: Unavailable
CurrentDesktop: GNOME
DefaultProfileIncompatibleExtensions: Default -
{972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:352
DefaultProfilePrefSources:
/usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js
prefs.js
DistroRelease: Ubuntu 21.04
ForcedLayersAccel: False
InstallationDate: Installed on 2011-11-06 (3454 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: firefox 87.0+build3-0ubuntu4
PackageArchitecture: amd64
ProcCmdline: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic
root=UUID=617752e9-3054-4928-881c-0e0651a839b0 ro splash quiet vt.handoff=7
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt
[Desktop-packages] [Bug 1925409] Re: the screen just blink. somewhat look crash
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1925409 Title: the screen just blink. somewhat look crash Status in evince package in Ubuntu: New Bug description: As I continuing doing my works. The apps I just use is lag and somewhat crashing. When I turn on the another app. Same things happen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 22 10:44:11 2021 InstallationDate: Installed on 2021-04-21 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1925409/+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 1925320] Re: Backport packages for 20.04.3 HWE stack
** Changed in: libdrm (Ubuntu Focal) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: mesa (Ubuntu Focal) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: xorg-server (Ubuntu Focal) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- 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/1925320 Title: Backport packages for 20.04.3 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-12 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in directx-headers source package in Focal: New Status in libdrm source package in Focal: New Status in llvm-toolchain-12 source package in Focal: New Status in mesa source package in Focal: New Status in xorg-server source package in Focal: New Bug description: [Impact] These are needed for 20.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] directx-headers: a new package, nothing can go wrong libdrm: adds some new api, no changes to old stuff llvm-12: a new package, no regression potential on it's own libclc: just a rebuild against the new llvm mesa: a new major release, but we'll pull the final stable release of 21.0.x series, so there shouldn't be any regressions left at that point xserver: a new point-release, 1.20.x series is in deep maintenance mode, so there should be little chance of breakage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+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
Re: [Desktop-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
Also reproduced on RKL SDP (202102-28687) running 5.12-rc8. Checking drm-tip. ** Attachment added: "dmesg.RKL-SDP.5.12.0-8-generic" https://bugs.launchpad.net/bugs/1918855/+attachment/5490918/+files/dmesg.RKL-SDP.5.12.0-8-generic -- 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/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+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 1925434] [NEW] New bugfix release 21.0.x
Public bug reported: [Impact] This is the last point-release of the 21.0.x-series, we should put it in hirsute so latest bugfixes would get there, and in focal for 20.04.3 image. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. ** Affects: mesa (Ubuntu) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: In Progress ** Affects: mesa (Ubuntu Focal) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: In Progress ** Affects: mesa (Ubuntu Hirsute) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: In Progress ** Also affects: mesa (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu Focal) Status: New => In Progress ** Changed in: mesa (Ubuntu Focal) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: mesa (Ubuntu Hirsute) Status: New => In Progress ** Changed in: mesa (Ubuntu Hirsute) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- 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/1925434 Title: New bugfix release 21.0.x Status in mesa package in Ubuntu: In Progress Status in mesa source package in Focal: In Progress Status in mesa source package in Hirsute: In Progress Bug description: [Impact] This is the last point-release of the 21.0.x-series, we should put it in hirsute so latest bugfixes would get there, and in focal for 20.04.3 image. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1925434/+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 1925320] Re: Backport packages for 20.04.3 HWE stack
** Description changed: - PLACEHOLDER + [Impact] - migrate to building libclc from llvm? + These are needed for 20.04.3 images. + + [Test case] + + Boot a daily image, see that it still has the necessary stack installed + and working. + + [What could go wrong] + + directx-headers: a new package, nothing can go wrong + + libdrm: adds some new api, no changes to old stuff + + llvm-12: a new package, no regression potential on it's own + + libclc: just a rebuild against the new llvm + + mesa: a new major release, but we'll pull the final stable release of + 21.0.x series, so there shouldn't be any regressions left at that point + + xserver: a new point-release, 1.20.x series is in deep maintenance mode, + so there should be little chance of breakage -- 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/1925320 Title: Backport packages for 20.04.3 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-12 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in directx-headers source package in Focal: New Status in libdrm source package in Focal: New Status in llvm-toolchain-12 source package in Focal: New Status in mesa source package in Focal: New Status in xorg-server source package in Focal: New Bug description: [Impact] These are needed for 20.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] directx-headers: a new package, nothing can go wrong libdrm: adds some new api, no changes to old stuff llvm-12: a new package, no regression potential on it's own libclc: just a rebuild against the new llvm mesa: a new major release, but we'll pull the final stable release of 21.0.x series, so there shouldn't be any regressions left at that point xserver: a new point-release, 1.20.x series is in deep maintenance mode, so there should be little chance of breakage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+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
