[Desktop-packages] [Bug 1984147] Re: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland
** Changed in: gnome-shell (Ubuntu Kinetic) Status: Fix Committed => Fix Released -- 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/1984147 Title: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: In Progress Status in gnome-shell source package in Kinetic: Fix Released Bug description: [Impact] Users using desktop PC is not able to switch monitor mode between mirrored and joined mode using Super-P or keyboard shortcut. This SRU fixes the issue. [Test Plan] 1. Use a desktop PC and start GNOME 3 2. Connect the PC with 2 monitors 3. Use Super-P to switch to joined display (note that using Displays from Settings does not trigger the issue) 4. Use Super-P to switch display mode again Expected: Display Switcher popup should appear Actual: Display Switcher does not popup [Where problems could occur] Although this change is minimal, the impact should be only on switching display mode using the shortcut. [Version] gnome-shell42.2-0ubuntu0.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-10 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984147/+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 1959937] Re: gnome-shell crashed with SIGSEGV in meta_context_terminate(context=0x0) from process_ice_messages()
** Changed in: mutter (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1959937
Title:
gnome-shell crashed with SIGSEGV in
meta_context_terminate(context=0x0) from process_ice_messages()
Status in GNOME Shell:
New
Status in Mutter:
Unknown
Status in mutter package in Ubuntu:
Fix Released
Status in gnome-shell package in Fedora:
Confirmed
Bug description:
The error occurred when I ran apt update/upgrade in a terminal window
after logging in.
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 41.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 3 09:03:52 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'41.3'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'hu')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.notifications' b'application-children'
b"['gnome-initial-setup']"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-02-03 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 41.3-1ubuntu1
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
meta_context_terminate () from /lib/x86_64-linux-gnu/libmutter-9.so.0
?? () from /lib/x86_64-linux-gnu/libmutter-9.so.0
g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in meta_context_terminate()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1959937/+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 1986889] Re: Icons are blurry in nautilus 43 at display scale >= 200%
** Changed in: nautilus (Ubuntu) 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/1986889 Title: Icons are blurry in nautilus 43 at display scale >= 200% Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Fix Released Bug description: Icons are blurry in nautilus 43 at display scale >= 200%. Screenshot attached (compare the icons to their text). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~beta.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Aug 18 10:58:35 2022 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2022-07-20 (28 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.1-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1986889/+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 1973638] Re: gnome-shell 42 leaks tens of megabytes with every screenshot
** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- 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/1973638 Title: gnome-shell 42 leaks tens of megabytes with every screenshot Status in GNOME Shell: Unknown Status in gjs package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Released Status in gnome-shell source package in Jammy: Fix Committed Bug description: [Impact] gnome-shell's memory usage grows by tens of megabytes with every screenshot. A few screenshots make it 100MB larger and a few dozen screenshots make it 1GB larger. [Test Plan for GNOME Shell Fix] TODO [Test Plan for GJS Fix] 1. Log into gnome-shell. 2. Measure its real memory usage: grep RSS /proc/`pidof gnome-shell`/status 3. Take 20 full screen screenshots by pressing PrtScn each time. No need to save them anywhere. 4. Measure the memory usage again. Expected: Memory usage grows a little but growth does not exceed a few hundred megabytes. It should level off after a while and sometimes even shrink due to garbage collection. Observed: Memory usage grows without bounds, easily exceeding 1GB after about 20 screenshots (depending on screen resolution). It never shrinks significantly. [Where problems could occur] Since the fix affects GJS, problems could occur in any part of gnome- shell. [Other Info] This leak requires multiple fixes to minimize the memory usage. For the moment we are only aiming to fix the main GJS portion of the bug that allows memory usage to exceed 1GB. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1973638/+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 1988256] Re: gnome-shell crashed with SIGSEGV in meta_get_first_subsurface_node() from pointer_can_grab_surface() from meta_wayland_pointer_can_grab_surface() from meta_wayland
** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1988256 Title: gnome-shell crashed with SIGSEGV in meta_get_first_subsurface_node() from pointer_can_grab_surface() from meta_wayland_pointer_can_grab_surface() from meta_wayland_seat_get_grab_info() from token_can_activate() Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 43~beta-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/6582f375d7b1e6bec0fdee2e9d2ec574844a8457 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1988256/+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 1988906] Re: Night light and colour management has stopped working in 22.10
** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1988906 Title: Night light and colour management has stopped working in 22.10 Status in mutter package in Ubuntu: Fix Released Bug description: Night light and colour management has stopped working in 22.10, because it's transitioning from the gnome-settings-daemon project into mutter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1988906/+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 1989615] Re: gnome-shell crashed with SIGABRT in assertion [libmutter:ERROR:../src/backends/meta-monitor-manager.c:1690:get_connector_type_name: code should not be reached]
** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1989615 Title: gnome-shell crashed with SIGABRT in assertion [libmutter:ERROR:../src/backends/meta-monitor- manager.c:1690:get_connector_type_name: code should not be reached] Status in mutter package in Ubuntu: Fix Released Bug description: Started Ubuntu Kinetic (22.10) Desktop for Raspberry Pi on a Pi 4 with 4GB of RAM. One notable thing about this particular setup is that the display is the Pimoroni Hyperpixel which has an unusual resolution of 480x800 (portrait by default) or 800x480 landscape, which seems to be too low for the vast majority of GNOME applications unfortunately. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-1001.3-raspi 5.19.0-rc8 Uname: Linux 5.19.0-1001-raspi aarch64 ApportVersion: 2.23.0-0ubuntu1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME-Greeter:GNOME Date: Wed Sep 14 20:40:05 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: ImageMediaBuild: 20220829 ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/false RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 Signal: 6 SourcePackage: gnome-shell StacktraceTop: g_assertion_message () from /lib/aarch64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/aarch64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/aarch64-linux-gnu/libmutter-11.so.0 ?? () from /lib/aarch64-linux-gnu/libffi.so.8 ?? () from /lib/aarch64-linux-gnu/libffi.so.8 Title: gnome-shell crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1989615/+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 1990040] [NEW] Bass speakers not enabled on Lenovo Yoga 7 Gen 7 (14ARB7)
Public bug reported: The Lenovo Yoga 7 Gen 7 (14ARB7) has 4 speakers - 2 trebles and 2 basses. The treble speakers work, but the bass ones don't. I think this is very similar to https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165, but that patch does not solve the problem, I suppose because the chipset is not the same (ALC245 on this machine vs ALC295 on that. This report has been sent from a system with Pipewire (and kernel 6.0), but this can be ignored, as the problem reproduces the same way on a system without Pipewire (kernel 6.0 is needed because of keyboard issues). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 Uname: Linux 6.0.0-06rc3-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio2016 F wireplumber /dev/snd/controlC0: saverio2016 F wireplumber /dev/snd/seq:saverio2014 F pipewire CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Sep 18 00:08:29 2022 InstallationDate: Installed on 2022-09-15 (2 days ago) InstallationMedia: Ubuntu-MATE 22.04.1-6.0rc3 "Custom Jammy Jellyfish" (20220910) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2022 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: K5CN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 14ARB7 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrK5CN27WW:bd05/08/2022:br1.27:efr1.27:svnLENOVO:pn82QF:pvrYoga714ARB7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga714ARB7:skuLENOVO_MT_82QF_BU_idea_FM_Yoga714ARB7: dmi.product.family: Yoga 7 14ARB7 dmi.product.name: 82QF dmi.product.sku: LENOVO_MT_82QF_BU_idea_FM_Yoga 7 14ARB7 dmi.product.version: Yoga 7 14ARB7 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.default.apport: 2022-09-15T11:39:08.571662 mtime.conffile..etc.pulse.default.pa: 2022-09-15T11:39:08.207685 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/1990040 Title: Bass speakers not enabled on Lenovo Yoga 7 Gen 7 (14ARB7) Status in pulseaudio package in Ubuntu: New Bug description: The Lenovo Yoga 7 Gen 7 (14ARB7) has 4 speakers - 2 trebles and 2 basses. The treble speakers work, but the bass ones don't. I think this is very similar to https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165, but that patch does not solve the problem, I suppose because the chipset is not the same (ALC245 on this machine vs ALC295 on that. This report has been sent from a system with Pipewire (and kernel 6.0), but this can be ignored, as the problem reproduces the same way on a system without Pipewire (kernel 6.0 is needed because of keyboard issues). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 Uname: Linux 6.0.0-06rc3-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio2016 F wireplumber /dev/snd/controlC0: saverio2016 F wireplumber /dev/snd/seq:saverio2014 F pipewire CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Sep 18 00:08:29 2022 InstallationDate: Installed on 2022-09-15 (2 days ago) InstallationMedia: Ubuntu-MATE 22.04.1-6.0rc3 "Custom Jammy Jellyfish" (20220910) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2022 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: K5CN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 14ARB7 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrK5CN27WW:bd05/08/2022:br1.27:efr1.27:svnLENOVO:pn82QF:pvrYoga714ARB7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga714ARB7:skuLENOVO_MT_82QF_BU_idea_FM_Yoga714ARB7: dmi.product.family:
[Desktop-packages] [Bug 1988234] Re: Shell crash after leting file to be opened with gnome-text-editor
The bug is gone after last upgrade of these packages: 2022-09-17 23:32:43 upgrade python3-problem-report:all 2.23.0-0ubuntu1 2.23.0-0ubuntu2 2022-09-17 23:32:43 upgrade python3-apport:all 2.23.0-0ubuntu1 2.23.0-0ubuntu2 2022-09-17 23:32:43 upgrade apport:all 2.23.0-0ubuntu1 2.23.0-0ubuntu2 2022-09-17 23:32:43 upgrade libexpat1-dev:amd64 2.4.8-1 2.4.8-2 2022-09-17 23:32:43 upgrade libexpat1:amd64 2.4.8-1 2.4.8-2 2022-09-17 23:32:43 upgrade libexpat1:i386 2.4.8-1 2.4.8-2 2022-09-17 23:32:43 upgrade ubuntu-minimal:amd64 1.493 1.494 2022-09-17 23:32:43 upgrade ubuntu-standard:amd64 1.493 1.494 2022-09-17 23:32:43 upgrade apport-gtk:all 2.23.0-0ubuntu1 2.23.0-0ubuntu2 2022-09-17 23:32:43 upgrade libatspi2.0-dev:amd64 2.44.1-1 2.45.91-1ubuntu3 2022-09-17 23:32:44 upgrade gir1.2-atspi-2.0:amd64 2.44.1-1 2.45.91-1ubuntu3 2022-09-17 23:32:44 upgrade libatspi2.0-0:amd64 2.44.1-1 2.45.91-1ubuntu3 2022-09-17 23:32:44 upgrade at-spi2-core:amd64 2.44.1-1 2.45.91-1ubuntu3 2022-09-17 23:32:44 upgrade libatk1.0-dev:amd64 2.38.0-1 2.45.91-1ubuntu3 2022-09-17 23:32:44 upgrade libatk1.0-0:amd64 2.38.0-1 2.45.91-1ubuntu3 2022-09-17 23:32:44 upgrade gir1.2-atk-1.0:amd64 2.38.0-1 2.45.91-1ubuntu3 2022-09-17 23:32:44 upgrade libatk-bridge2.0-dev:amd64 2.38.0-4 2.45.91-1ubuntu3 2022-09-17 23:32:44 upgrade libatk-bridge2.0-0:amd64 2.38.0-4 2.45.91-1ubuntu3 2022-09-17 23:32:44 upgrade code:amd64 1.71.1-1662667267 1.71.2-1663191218 2022-09-17 23:32:51 upgrade fonts-noto-color-emoji:all 2.034-1 2.038-1 2022-09-17 23:32:51 upgrade libadwaita-1-0:amd64 1.2~rc-1ubuntu1 1.2.0-1ubuntu2 2022-09-17 23:32:51 upgrade gir1.2-adw-1:amd64 1.2~rc-1ubuntu1 1.2.0-1ubuntu2 2022-09-17 23:32:51 upgrade libgoa-1.0-common:all 3.45.2-2 3.45.2-3 2022-09-17 23:32:51 upgrade gir1.2-soup-3.0:amd64 3.1.4-1 3.2.0-1 2022-09-17 23:32:52 upgrade glib-networking-common:all 2.74~rc-1 2.74.0-1 2022-09-17 23:32:52 upgrade glib-networking:i386 2.74~rc-1 2.74.0-1 2022-09-17 23:32:52 upgrade glib-networking:amd64 2.74~rc-1 2.74.0-1 2022-09-17 23:32:52 upgrade glib-networking-services:amd64 2.74~rc-1 2.74.0-1 2022-09-17 23:32:52 upgrade libsoup-3.0-common:all 3.1.4-1 3.2.0-1 2022-09-17 23:32:52 upgrade libsoup-3.0-0:amd64 3.1.4-1 3.2.0-1 2022-09-17 23:32:52 upgrade gnome-online-accounts:amd64 3.45.2-2 3.45.2-3 2022-09-17 23:32:52 upgrade libgoa-backend-1.0-1:amd64 3.45.2-2 3.45.2-3 2022-09-17 23:32:52 upgrade libgoa-1.0-0b:amd64 3.45.2-2 3.45.2-3 2022-09-17 23:32:52 upgrade gir1.2-goa-1.0:amd64 3.45.2-2 3.45.2-3 2022-09-17 23:32:52 upgrade libhandy-1-0:amd64 1.7.90-1 1.8.0-1 2022-09-17 23:32:52 upgrade gir1.2-handy-1:amd64 1.7.90-1 1.8.0-1 2022-09-17 23:32:52 upgrade mutter-common:all 43~beta-3ubuntu2 43~rc-2ubuntu2 2022-09-17 23:32:52 upgrade gir1.2-mutter-11:amd64 43~beta-3ubuntu2 43~rc-2ubuntu2 2022-09-17 23:32:52 upgrade libmutter-11-0:amd64 43~beta-3ubuntu2 43~rc-2ubuntu2 2022-09-17 23:32:52 upgrade gnome-calendar:amd64 43~rc-1ubuntu1 43.0-2 2022-09-17 23:32:52 upgrade gnome-control-center-data:all 1:43~rc-1ubuntu2 1:43.0-1ubuntu1 2022-09-17 23:32:53 upgrade gnome-control-center:amd64 1:43~rc-1ubuntu2 1:43.0-1ubuntu1 2022-09-17 23:32:53 upgrade gnome-control-center-faces:all 1:43~rc-1ubuntu2 1:43.0-1ubuntu1 2022-09-17 23:32:53 upgrade gnome-initial-setup:amd64 43~beta-0ubuntu1 43~rc.1-1ubuntu1 2022-09-17 23:32:53 upgrade gnome-power-manager:amd64 3.32.0-2build2 43.0-1 2022-09-17 23:32:53 upgrade gnome-shell-extension-prefs:amd64 43~beta-1ubuntu2 43~rc-1ubuntu2 2022-09-17 23:32:53 upgrade yaru-theme-gnome-shell:all 22.10.1 22.10.2 2022-09-17 23:32:53 upgrade gnome-shell:amd64 43~beta-1ubuntu2 43~rc-1ubuntu2 2022-09-17 23:32:54 upgrade gnome-shell-common:all 43~beta-1ubuntu2 43~rc-1ubuntu2 2022-09-17 23:32:54 upgrade libatk-adaptor:amd64 2.38.0-4 2.45.91-1ubuntu3 2022-09-17 23:32:54 upgrade libblockdev-utils2:amd64 2.27-1 2.28-1 2022-09-17 23:32:54 upgrade libblockdev-crypto2:amd64 2.27-1 2.28-1 2022-09-17 23:32:54 upgrade libblockdev-part-err2:amd64 2.27-1 2.28-1 2022-09-17 23:32:54 upgrade libblockdev-fs2:amd64 2.27-1 2.28-1 2022-09-17 23:32:54 upgrade libblockdev-loop2:amd64 2.27-1 2.28-1 2022-09-17 23:32:54 upgrade libblockdev-part2:amd64 2.27-1 2.28-1 2022-09-17 23:32:54 upgrade libblockdev-swap2:amd64 2.27-1 2.28-1 2022-09-17 23:32:54 upgrade libblockdev2:amd64 2.27-1 2.28-1 2022-09-17 23:32:54 upgrade libftdi1-2:amd64 1.5-5build3 1.5-6 2022-09-17 23:32:54 upgrade libgtksourceview-5-common:all 5.5.1-2~fakesync1 5.5.1-3~fakesync1 2022-09-17 23:32:54 upgrade libgtksourceview-5-0:amd64 5.5.1-2~fakesync1 5.5.1-3~fakesync1 2022-09-17 23:32:54 upgrade wireplumber:amd64 0.4.10-2ubuntu1 0.4.11-4 2022-09-17 23:32:55 upgrade libwireplumber-0.4-0:amd64 0.4.10-2ubuntu1 0.4.11-4 2022-09-17 23:33:04 upgrade linux-xanmod:amd64 5.19.8-xanmod1-0 5.19.9-xanmod1-0 2022-09-17 23:33:04 upgrade php8.1-xml:amd64 8.1.7-1ubuntu2 8.1.7-1ubuntu3 2022-09-17 23:33:04 upgrade php8.1-readline:amd64 8.1.7-1ubuntu2 8.1.7-1ubuntu3 2022-09-17 23:33:04 upgrade php8.1-opcache:amd64
[Desktop-packages] [Bug 1990039] gsd-xsettings crashed with SIGSEGV in g_closure_invoke()
StacktraceTop: ?? () g_closure_invoke (closure=0x56413bdea160, return_value=0x0, n_param_values=2, param_values=0x7ffdcb6d15d0, invocation_hint=0x7ffdcb6d1550) at ../../../gobject/gclosure.c:832 signal_emit_unlocked_R.isra.0 (node=node@entry=0x56413bc5d280, detail=detail@entry=349, instance=instance@entry=0x56413bcbbee0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffdcb6d15d0) at ../../../gobject/gsignal.c:3796 g_signal_emit_valist (instance=, signal_id=, detail=, var_args=var_args@entry=0x7ffdcb6d1790) at ../../../gobject/gsignal.c:3549 g_signal_emit (instance=, signal_id=, detail=) at ../../../gobject/gsignal.c:3606 ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1990039 Title: gsd-xsettings crashed with SIGSEGV in g_closure_invoke() Status in gnome-settings-daemon package in Ubuntu: New Bug description: sudden crashed ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-settings-daemon 43~rc-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7 Uname: Linux 5.19.0-16-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 17 21:28:17 2022 Disassembly: => 0x7f321c9854f0: Cannot access memory at address 0x7f321c9854f0 ExecutablePath: /usr/libexec/gsd-xsettings InstallationDate: Installed on 2020-06-25 (813 days ago) InstallationMedia: JournalErrors: Error: command ['journalctl', '--priority=warning', '--since=@1663421287', '--until=@1663421307'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcCmdline: /usr/libexec/gsd-xsettings SegvAnalysis: Segfault happened at: 0x7f321c9854f0:Cannot access memory at address 0x7f321c9854f0 PC (0x7f321c9854f0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gsd-xsettings crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (144 days ago) UserGroups: nordvpn sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1990039/+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 1990039] [NEW] gsd-xsettings crashed with SIGSEGV in g_closure_invoke()
Public bug reported: sudden crashed ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-settings-daemon 43~rc-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7 Uname: Linux 5.19.0-16-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 17 21:28:17 2022 Disassembly: => 0x7f321c9854f0: Cannot access memory at address 0x7f321c9854f0 ExecutablePath: /usr/libexec/gsd-xsettings InstallationDate: Installed on 2020-06-25 (813 days ago) InstallationMedia: JournalErrors: Error: command ['journalctl', '--priority=warning', '--since=@1663421287', '--until=@1663421307'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcCmdline: /usr/libexec/gsd-xsettings SegvAnalysis: Segfault happened at: 0x7f321c9854f0: Cannot access memory at address 0x7f321c9854f0 PC (0x7f321c9854f0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gsd-xsettings crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (144 days ago) UserGroups: nordvpn sudo separator: ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash kinetic wayland-session ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1990039 Title: gsd-xsettings crashed with SIGSEGV in g_closure_invoke() Status in gnome-settings-daemon package in Ubuntu: New Bug description: sudden crashed ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-settings-daemon 43~rc-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7 Uname: Linux 5.19.0-16-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 17 21:28:17 2022 Disassembly: => 0x7f321c9854f0: Cannot access memory at address 0x7f321c9854f0 ExecutablePath: /usr/libexec/gsd-xsettings InstallationDate: Installed on 2020-06-25 (813 days ago) InstallationMedia: JournalErrors: Error: command ['journalctl', '--priority=warning', '--since=@1663421287', '--until=@1663421307'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcCmdline: /usr/libexec/gsd-xsettings SegvAnalysis: Segfault happened at: 0x7f321c9854f0:Cannot access memory at address 0x7f321c9854f0 PC (0x7f321c9854f0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gsd-xsettings crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (144 days ago) UserGroups: nordvpn sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1990039/+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 1987976]
I mean: for 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/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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 1987976]
The severity field is not set for this bug. :gerard-majax, could you have a look please? For more information, please visit [auto_nag documentation](https://wiki.mozilla.org/Release_Management/autonag#workflow.2Fno_severity.py). -- 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/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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 1987976]
Does Ubuntu Software still offer an update for 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/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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 1987976]
Created attachment 9294284 Capture2022-09-12.png No update offered anymore. -- 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/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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 1988686] Re: Read failure Photo SD Memory Card in USB
** Changed in: nautilus Status: New => 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/1988686 Title: Read failure Photo SD Memory Card in USB Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: In Progress Bug description: Tried to read my SD memory card in the USB slot. Nautilus responded with message box "Force Close" or "Wait". Nautilus is outputting the following messages to Syslog when trying to display the device. Sep 4 14:41:42 Desktopps nautilus[31175]: specified class size for type 'NautilusXContentBar' is smaller than the parent type's 'GtkInfoBar' class size Sep 4 14:41:42 Desktopps nautilus[31175]: g_once_init_leave: assertion 'result != 0' failed Sep 4 14:41:42 Desktopps nautilus[31175]: g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed Sep 4 14:41:42 Desktopps nautilus[31175]: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed Sep 4 14:41:42 Desktopps nautilus[31175]: gtk_box_append: assertion 'GTK_IS_WIDGET (child)' failed Able to read this memory card in a Ubuntu 22.04 system. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~beta.1-2ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Sep 4 15:08:36 2022 InstallationDate: Installed on 2022-09-03 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43~alpha-1 nautilus-extension-gnome-terminal 3.45.90-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1988686/+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 1981148] Re: Focusing the filename in GTK's portal file dialog triggers search
This bug affects me as well: Ubuntu Release 22.04 LTS (Jammy Jellyfish) 64-bit Kernel Linux 5.15.0-47-generic x86_64 Hardware Memory: 15.5 GiB Processor: Intel Core i5-3330S CPU @ 2.70 GHz x4 Graphics: Mesa Intel HD Graphics 2500 (IVB GT1) Am wondering if this is being looked into as its confirmed as a bug. My workaround is to save with original filename the use file manager to rename file after the fact. -- 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/1981148 Title: Focusing the filename in GTK's portal file dialog triggers search Status in firefox package in Ubuntu: Confirmed Status in lubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-mate-meta package in Ubuntu: Confirmed Bug description: I'm still wondering why my Ubuntu forces the snap version of Firefox onto me, despite apt-pinning, but OK, I guess being frustrated about that would be a lost cause. In any case: The snap version of Firefox that my Ubuntu has decided to install despite my apt-pinning has a bug in the saving dialog. I've recorded a video and left it online, here: https://anonfiles.com/X4ec15w7y3/simplescreenrecorder-2022-07-10_15.57.54_mkv Following protocol: 1) $ lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 2) $ apt-cache policy firefox firefox: Installed: 1:1snap1-0ubuntu2 Candidate: 1:1snap1-0ubuntu2 Version table: *** 1:1snap1-0ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 102.0.1+build1-0ubuntu0.18.04.1 999 500 http://ppa.launchpad.net/ubuntu-mozilla-security/ppa/ubuntu bionic/main amd64 Packages 500 https://ppa.launchpadcontent.net/ubuntu-mozilla-security/ppa/ubuntu bionic/main amd64 Packages (note how Ubuntu doesn't give a damn about the pin priority, but whatever) 3) I'm trying to save a downloaded document. 3.1) Firefox opens the save dialogue. 3.2) I would like to enter a filename into the filename bar 4) following 3.1: 4.2) When I try to change the filename, the focus immediately jumps to the search bar and the dialogue for some reason tries to search for the entered letters on the drive. I can click back to focus on the filename bar, sometimes I can manage to type one or two letters, before the focus jumps, again. This does not happen with the version I installed using apt, but which repeatedly gets removed by the Ubuntu updating process, to install the snap version, which sadly never seems to work without problems. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Jul 10 16:00:53 2022 InstallationDate: Installed on 2022-03-07 (125 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1981148/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Still broken, 17th September 2022 in Ubuntu 22.04. Evince prints the following message "env: ‘/snap/bin/firefox’: Permission denied" Workaround: https://github.com/popey/unsnap -- 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/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in apparmor source package in Jammy: Confirmed Status in evince source package in Jammy: Confirmed Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1750199]
Caolán McNamara committed a patch related to this issue. It has been pushed to "libreoffice-7-4": https://git.libreoffice.org/core/commit/c062358d7b58ce3a9b27681040d854ec7ea1868b Resolves: tdf#144583 reuse lok hidpi icon scheme for gtk It will be available in 7.4.2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- 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/1750199 Title: Blurry Icons on HighDPI Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: In Progress Bug description: On bionic with libreoffice 6.0 from proposed new and subjectively better icons are shipped which is great. However, they still are rather blurry on a HighDPI screen. Can we patch the package to provide a higher resolution iconset? To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1750199/+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 1989418] Re: [BPO] libreoffice 7.3.6 for focal
** Changed in: libreoffice (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1989418 Title: [BPO] libreoffice 7.3.6 for focal Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: Fix Released Bug description: [Impact] * LibreOffice 7.3.6 is in its sixth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.6_release * This source packages matches the proposed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1988744 and its backport is currently provided by the LibreOffice Fresh PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages * Previous backport of 7.3.5 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1987045 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * LibreOffice 7.3.5 is currently released in focal-backports. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.6-0ubuntu0.22.04.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/1900/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/amd64/libr/libreoffice/20220904_103401_f46f5@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/arm64/libr/libreoffice/20220904_144020_84b5b@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/armhf/libr/libreoffice/20220904_113245_95845@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/ppc64el/libr/libreoffice/20220904_100953_3af7d@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/s390x/libr/libreoffice/20220904_095636_d0c69@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 50 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1989418/+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 1965219] Re: gnome lock screen does not permit reentering password
Seeing exactly the same symptoms on a machine upgraded to 22.04, with wayland. Definitely seems suspend-related, but I haven't figured out what the problem is, yet. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Confirmed ** Changed in: systemd (Ubuntu) Status: Incomplete => Confirmed -- 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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
[Desktop-packages] [Bug 1989434] Re: poppler 0.62.0-2ubuntu2.13 breaks GDAL compilation
*** This bug is a duplicate of bug 1989515 *** https://bugs.launchpad.net/bugs/1989515 Thanks for reporting. Based on the comments, I belive this issue to be resolved by bug 1989515. ** This bug has been marked a duplicate of bug 1989515 "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic ** Tags added: bionic patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1989434 Title: poppler 0.62.0-2ubuntu2.13 breaks GDAL compilation Status in poppler package in Ubuntu: New Bug description: The security update poppler 0.62.0-2ubuntu2.13 that fixes CVE-2022-38784 adds a new header file goo/GooCheckedOps.h that is included by goo/gmem.h goo/gmem.h is a file installed in the libpoppler-private-dev package, which is used by GDAL, but the patches added in the 0.62.0-2ubuntu2.13 update omit installing goo/GooCheckedOps.h, consequently any external code including goo/gmem.h breaks at compilation The following extra patch should fix this: ``` $ diff -u CMakeLists.txt.ori CMakeLists.txt --- CMakeLists.txt.ori2022-09-13 10:58:42.282712260 +0200 +++ CMakeLists.txt2022-09-13 10:58:44.198709344 +0200 @@ -578,6 +578,7 @@ goo/GooString.h goo/gtypes.h goo/gmem.h +goo/GooCheckedOps.h goo/gfile.h goo/FixedPoint.h goo/ImgWriter.h ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1989434/+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 1989515] Re: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic
** Tags added: bionic regression-update -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1989515 Title: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic Status in poppler package in Ubuntu: Fix Released Bug description: Somehow "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic but "goo/gmem.h" still has the statement `#include "GooCheckedOps.h"`. As a result, a compile error will happen when compiling code that uses poppler: /usr/include/poppler/goo/gmem.h:31:11: fatal error: GooCheckedOps.h: No such file or directory I'm using Ubuntu 18.04 and currently having 0.62.0-2ubuntu2.12 (the previous version) installed. I confirmed that "goo/gmem.h" doesn't have the `#include "GooCheckedOps.h"` statement. I found this issue when I was compiling gdal on my Docker container. The Docker container was installed the problematic version 0.62.0-2ubuntu2.13 and I ran into the "No such file or directory" error. I compiled on both Amd64 and AArch64 and I ran into the same error on both platforms. By reading the diff between 2.12 and 2.13 (https://launchpadlibrarian.net/622079418/poppler_0.62.0-2ubuntu2.12_0.62.0-2ubuntu2.13.diff.gz), the patch looks quite right. But when I examined the contents of the built `.deb` packages, I didn't find the file "goo/GooCheckedOps.h". Kind of weird, because the problem seems to be caused by applying "CVE-2022-38784-pre.patch" in half: the first part that creates "goo/GooCheckedOps.h" was not applied during the build process and the second part that modifies "goo/gmem.h" was applied. Any thoughts? Ideas? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1989515/+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 70872] Re: MASTER Firefox makes X run out windows
** Changed in: firefox
Status: Confirmed => Invalid
--
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/70872
Title:
MASTER Firefox makes X run out windows
Status in Mozilla Firefox:
Invalid
Status in firefox package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: firefox
After letting firefox run for some days I started getting this error
every time I tried to start an X application:
Xlib: connection to ":0.0" refused by server
Xlib: Maximum number of clients reached
cannot open display:
I then closed some applications so that I could use xwininfo and
xlsclients.
andre@huge:~/downloads$ xlsclients
huge x-session-manager
huge gnome-settings-daemon
huge metacity
huge gnome-panel
huge gnome-volume-manager
huge nautilus
huge update-notifier
huge gnome-power-manager
huge gnome-cups-icon
huge evolution-alarm-notify
huge evolution-exchange
huge multiload
huge gweather
huge mixer_applet2
huge stickynotes_applet
huge gnome-screensaver
huge gnome-terminal
huge /usr/lib/tomboy/Tomboy.exe
huge /usr/lib/tomboy/Tomboy.exe
huge firefox-bin
huge notification-daemon
huge gnome-btdownload
huge gaim
andre@huge:~/downloads$
andre@huge:~/downloads$ xwininfo -root -children
xwininfo: Window id: 0x4d (the root window) (has no name)
Root window id: 0x4d (the root window) (has no name)
Parent window id: 0x0 (none)
361 children:
0x28a4236 "Firefox": ("Gecko" "Firefox-bin") 200x200+0+0 +0+0
0x28a4230 "Firefox": ("Gecko" "Firefox-bin") 200x200+0+0 +0+0
0x2e0dab2 "Terminal": ("gnome-terminal" "Gnome-terminal") 200x21+980+73
+980+73
0x28a3b66 "Firefox": ("Gecko" "Firefox-bin") 200x200+0+0 +0+0
0x28a3b60 "Firefox": ("Gecko" "Firefox-bin") 200x200+0+0 +0+0
0x1ba07851 "gaim": () 10x10+-100+-100 +-100+-100
0x28cd713 "Firefox": ("Gecko" "Firefox-bin") 419x124+856+129 +856+129
0x28001a6 "Firefox": ("Gecko" "Firefox-bin") 212x17+707+146 +707+146
0x3200b55 (has no name): () 336x280+0+0 +0+0
0x3200b3d (has no name): () 728x90+0+0 +0+0
0xc01d86 "gnome-panel": ("gnome-panel" "Gnome-panel") 169x21+748+27
+748+27
0x3200b25 (has no name): () 234x60+0+0 +0+0
0x3200b0d (has no name): () 234x60+0+0 +0+0
0x3200af5 (has no name): () 728x90+0+0 +0+0
0x3200add (has no name): () 234x60+0+0 +0+0
0x3200ac5 (has no name): () 234x60+0+0 +0+0
0x280018c "Firefox": ("Gecko" "Firefox-bin") 95x17+661+640 +661+640
0x2800192 "Firefox": ("Gecko" "Firefox-bin") 782x112+461+100 +461+100
0x1ba00055 "Buddy List": ("gaim" "Gaim") 255x766+39+82 +39+82
0x3200aad (has no name): () 428x351+0+0 +0+0
0x3200a93 (has no name): () 728x90+0+0 +0+0
0x288ec2a "Firefox": ("Gecko" "Firefox-bin") 200x200+0+0 +0+0
0x288ec24 "Firefox": ("Gecko" "Firefox-bin") 200x200+0+0 +0+0
0x3200a90 (has no name): () 1x1+0+0 +0+0
0x3200a45 (has no name): () 549x340+0+0 +0+0
0x3200a8d (has no name): () 1x1+0+0 +0+0
0x3200a8a (has no name): () 1x1+0+0 +0+0
0x3200a87 (has no name): () 1x1+0+0 +0+0
0x3200a84 (has no name): () 1x1+0+0 +0+0
0x3200a81 (has no name): () 1x1+0+0 +0+0
0x3200a7e (has no name): () 1x1+0+0 +0+0
0x3200a7b (has no name): () 1x1+0+0 +0+0
0x3200a78 (has no name): () 1x1+0+0 +0+0
0x3200a75 (has no name): () 1x1+0+0 +0+0
0x3200a72 (has no name): () 1x1+0+0 +0+0
0x3200a6f (has no name): () 1x1+0+0 +0+0
0x3200a6c (has no name): () 1x1+0+0 +0+0
0x3200a69 (has no name): () 1x1+0+0 +0+0
0x3200a66 (has no name): () 1x1+0+0 +0+0
0x3200a63 (has no name): () 1x1+0+0 +0+0
0x3200a60 (has no name): () 1x1+0+0 +0+0
0x3200a5d (has no name): () 1x1+0+0 +0+0
0x1ba1 "gaim": ("gaim" "Gaim") 10x10+10+10 +10+10
0x1c00034 "gnome-btdownload": () 10x10+-100+-100 +-100+-100
0x1c00031 "gnome-btdownload": () 10x10+-100+-100 +-100+-100
0x1c1 "gnome-btdownload": ("gnome-btdownload" "Gnome-btdownload")
10x10+10+10 +10+10
0xc00217 "gnome-panel": ("gnome-panel" "Gnome-panel") 270x21+178+27
+178+27
0x2834037 "Firefox": ("Gecko" "Firefox-bin") 200x200+0+0 +0+0
0xc020dd "gnome-panel": ("gnome-panel" "Gnome-panel") 247x21+458+27
+458+27
0x2855711 "Firefox": ("Gecko" "Firefox-bin") 139x128+779+211 +779+211
0x2828954 "Firefox": ("Gecko" "Firefox-bin") 236x177+545+72 +545+72
0x3200a2d (has no name): () 760x91+0+0 +0+0
0x3200a0d (has no name): () 760x91+0+0 +0+0
0x3200a28 (has no name): () 150x150+0+0 +0+0
0x3200a25 (has no name): () 300x250+0+0 +0+0
0x32009f2 (has no
[Desktop-packages] [Bug 70872]
Wow, I haven’t seen this problem in a while. Just close the bug and hope
nobody ever has to report a similar one.
--
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/70872
Title:
MASTER Firefox makes X run out windows
Status in Mozilla Firefox:
Invalid
Status in firefox package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: firefox
After letting firefox run for some days I started getting this error
every time I tried to start an X application:
Xlib: connection to ":0.0" refused by server
Xlib: Maximum number of clients reached
cannot open display:
I then closed some applications so that I could use xwininfo and
xlsclients.
andre@huge:~/downloads$ xlsclients
huge x-session-manager
huge gnome-settings-daemon
huge metacity
huge gnome-panel
huge gnome-volume-manager
huge nautilus
huge update-notifier
huge gnome-power-manager
huge gnome-cups-icon
huge evolution-alarm-notify
huge evolution-exchange
huge multiload
huge gweather
huge mixer_applet2
huge stickynotes_applet
huge gnome-screensaver
huge gnome-terminal
huge /usr/lib/tomboy/Tomboy.exe
huge /usr/lib/tomboy/Tomboy.exe
huge firefox-bin
huge notification-daemon
huge gnome-btdownload
huge gaim
andre@huge:~/downloads$
andre@huge:~/downloads$ xwininfo -root -children
xwininfo: Window id: 0x4d (the root window) (has no name)
Root window id: 0x4d (the root window) (has no name)
Parent window id: 0x0 (none)
361 children:
0x28a4236 "Firefox": ("Gecko" "Firefox-bin") 200x200+0+0 +0+0
0x28a4230 "Firefox": ("Gecko" "Firefox-bin") 200x200+0+0 +0+0
0x2e0dab2 "Terminal": ("gnome-terminal" "Gnome-terminal") 200x21+980+73
+980+73
0x28a3b66 "Firefox": ("Gecko" "Firefox-bin") 200x200+0+0 +0+0
0x28a3b60 "Firefox": ("Gecko" "Firefox-bin") 200x200+0+0 +0+0
0x1ba07851 "gaim": () 10x10+-100+-100 +-100+-100
0x28cd713 "Firefox": ("Gecko" "Firefox-bin") 419x124+856+129 +856+129
0x28001a6 "Firefox": ("Gecko" "Firefox-bin") 212x17+707+146 +707+146
0x3200b55 (has no name): () 336x280+0+0 +0+0
0x3200b3d (has no name): () 728x90+0+0 +0+0
0xc01d86 "gnome-panel": ("gnome-panel" "Gnome-panel") 169x21+748+27
+748+27
0x3200b25 (has no name): () 234x60+0+0 +0+0
0x3200b0d (has no name): () 234x60+0+0 +0+0
0x3200af5 (has no name): () 728x90+0+0 +0+0
0x3200add (has no name): () 234x60+0+0 +0+0
0x3200ac5 (has no name): () 234x60+0+0 +0+0
0x280018c "Firefox": ("Gecko" "Firefox-bin") 95x17+661+640 +661+640
0x2800192 "Firefox": ("Gecko" "Firefox-bin") 782x112+461+100 +461+100
0x1ba00055 "Buddy List": ("gaim" "Gaim") 255x766+39+82 +39+82
0x3200aad (has no name): () 428x351+0+0 +0+0
0x3200a93 (has no name): () 728x90+0+0 +0+0
0x288ec2a "Firefox": ("Gecko" "Firefox-bin") 200x200+0+0 +0+0
0x288ec24 "Firefox": ("Gecko" "Firefox-bin") 200x200+0+0 +0+0
0x3200a90 (has no name): () 1x1+0+0 +0+0
0x3200a45 (has no name): () 549x340+0+0 +0+0
0x3200a8d (has no name): () 1x1+0+0 +0+0
0x3200a8a (has no name): () 1x1+0+0 +0+0
0x3200a87 (has no name): () 1x1+0+0 +0+0
0x3200a84 (has no name): () 1x1+0+0 +0+0
0x3200a81 (has no name): () 1x1+0+0 +0+0
0x3200a7e (has no name): () 1x1+0+0 +0+0
0x3200a7b (has no name): () 1x1+0+0 +0+0
0x3200a78 (has no name): () 1x1+0+0 +0+0
0x3200a75 (has no name): () 1x1+0+0 +0+0
0x3200a72 (has no name): () 1x1+0+0 +0+0
0x3200a6f (has no name): () 1x1+0+0 +0+0
0x3200a6c (has no name): () 1x1+0+0 +0+0
0x3200a69 (has no name): () 1x1+0+0 +0+0
0x3200a66 (has no name): () 1x1+0+0 +0+0
0x3200a63 (has no name): () 1x1+0+0 +0+0
0x3200a60 (has no name): () 1x1+0+0 +0+0
0x3200a5d (has no name): () 1x1+0+0 +0+0
0x1ba1 "gaim": ("gaim" "Gaim") 10x10+10+10 +10+10
0x1c00034 "gnome-btdownload": () 10x10+-100+-100 +-100+-100
0x1c00031 "gnome-btdownload": () 10x10+-100+-100 +-100+-100
0x1c1 "gnome-btdownload": ("gnome-btdownload" "Gnome-btdownload")
10x10+10+10 +10+10
0xc00217 "gnome-panel": ("gnome-panel" "Gnome-panel") 270x21+178+27
+178+27
0x2834037 "Firefox": ("Gecko" "Firefox-bin") 200x200+0+0 +0+0
0xc020dd "gnome-panel": ("gnome-panel" "Gnome-panel") 247x21+458+27
+458+27
0x2855711 "Firefox": ("Gecko" "Firefox-bin") 139x128+779+211 +779+211
0x2828954 "Firefox": ("Gecko" "Firefox-bin") 236x177+545+72 +545+72
0x3200a2d (has no name): () 760x91+0+0 +0+0
0x3200a0d (has no name): () 760x91+0+0 +0+0
0x3200a28 (has no name): () 150x150+0+0 +0+0
0x3200a25 (has no
[Desktop-packages] [Bug 70872]
Is this bug still relevant since flash and gnash are no longer
supported. Or can this bug be closed by now?
--
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/70872
Title:
MASTER Firefox makes X run out windows
Status in Mozilla Firefox:
Invalid
Status in firefox package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: firefox
After letting firefox run for some days I started getting this error
every time I tried to start an X application:
Xlib: connection to ":0.0" refused by server
Xlib: Maximum number of clients reached
cannot open display:
I then closed some applications so that I could use xwininfo and
xlsclients.
andre@huge:~/downloads$ xlsclients
huge x-session-manager
huge gnome-settings-daemon
huge metacity
huge gnome-panel
huge gnome-volume-manager
huge nautilus
huge update-notifier
huge gnome-power-manager
huge gnome-cups-icon
huge evolution-alarm-notify
huge evolution-exchange
huge multiload
huge gweather
huge mixer_applet2
huge stickynotes_applet
huge gnome-screensaver
huge gnome-terminal
huge /usr/lib/tomboy/Tomboy.exe
huge /usr/lib/tomboy/Tomboy.exe
huge firefox-bin
huge notification-daemon
huge gnome-btdownload
huge gaim
andre@huge:~/downloads$
andre@huge:~/downloads$ xwininfo -root -children
xwininfo: Window id: 0x4d (the root window) (has no name)
Root window id: 0x4d (the root window) (has no name)
Parent window id: 0x0 (none)
361 children:
0x28a4236 "Firefox": ("Gecko" "Firefox-bin") 200x200+0+0 +0+0
0x28a4230 "Firefox": ("Gecko" "Firefox-bin") 200x200+0+0 +0+0
0x2e0dab2 "Terminal": ("gnome-terminal" "Gnome-terminal") 200x21+980+73
+980+73
0x28a3b66 "Firefox": ("Gecko" "Firefox-bin") 200x200+0+0 +0+0
0x28a3b60 "Firefox": ("Gecko" "Firefox-bin") 200x200+0+0 +0+0
0x1ba07851 "gaim": () 10x10+-100+-100 +-100+-100
0x28cd713 "Firefox": ("Gecko" "Firefox-bin") 419x124+856+129 +856+129
0x28001a6 "Firefox": ("Gecko" "Firefox-bin") 212x17+707+146 +707+146
0x3200b55 (has no name): () 336x280+0+0 +0+0
0x3200b3d (has no name): () 728x90+0+0 +0+0
0xc01d86 "gnome-panel": ("gnome-panel" "Gnome-panel") 169x21+748+27
+748+27
0x3200b25 (has no name): () 234x60+0+0 +0+0
0x3200b0d (has no name): () 234x60+0+0 +0+0
0x3200af5 (has no name): () 728x90+0+0 +0+0
0x3200add (has no name): () 234x60+0+0 +0+0
0x3200ac5 (has no name): () 234x60+0+0 +0+0
0x280018c "Firefox": ("Gecko" "Firefox-bin") 95x17+661+640 +661+640
0x2800192 "Firefox": ("Gecko" "Firefox-bin") 782x112+461+100 +461+100
0x1ba00055 "Buddy List": ("gaim" "Gaim") 255x766+39+82 +39+82
0x3200aad (has no name): () 428x351+0+0 +0+0
0x3200a93 (has no name): () 728x90+0+0 +0+0
0x288ec2a "Firefox": ("Gecko" "Firefox-bin") 200x200+0+0 +0+0
0x288ec24 "Firefox": ("Gecko" "Firefox-bin") 200x200+0+0 +0+0
0x3200a90 (has no name): () 1x1+0+0 +0+0
0x3200a45 (has no name): () 549x340+0+0 +0+0
0x3200a8d (has no name): () 1x1+0+0 +0+0
0x3200a8a (has no name): () 1x1+0+0 +0+0
0x3200a87 (has no name): () 1x1+0+0 +0+0
0x3200a84 (has no name): () 1x1+0+0 +0+0
0x3200a81 (has no name): () 1x1+0+0 +0+0
0x3200a7e (has no name): () 1x1+0+0 +0+0
0x3200a7b (has no name): () 1x1+0+0 +0+0
0x3200a78 (has no name): () 1x1+0+0 +0+0
0x3200a75 (has no name): () 1x1+0+0 +0+0
0x3200a72 (has no name): () 1x1+0+0 +0+0
0x3200a6f (has no name): () 1x1+0+0 +0+0
0x3200a6c (has no name): () 1x1+0+0 +0+0
0x3200a69 (has no name): () 1x1+0+0 +0+0
0x3200a66 (has no name): () 1x1+0+0 +0+0
0x3200a63 (has no name): () 1x1+0+0 +0+0
0x3200a60 (has no name): () 1x1+0+0 +0+0
0x3200a5d (has no name): () 1x1+0+0 +0+0
0x1ba1 "gaim": ("gaim" "Gaim") 10x10+10+10 +10+10
0x1c00034 "gnome-btdownload": () 10x10+-100+-100 +-100+-100
0x1c00031 "gnome-btdownload": () 10x10+-100+-100 +-100+-100
0x1c1 "gnome-btdownload": ("gnome-btdownload" "Gnome-btdownload")
10x10+10+10 +10+10
0xc00217 "gnome-panel": ("gnome-panel" "Gnome-panel") 270x21+178+27
+178+27
0x2834037 "Firefox": ("Gecko" "Firefox-bin") 200x200+0+0 +0+0
0xc020dd "gnome-panel": ("gnome-panel" "Gnome-panel") 247x21+458+27
+458+27
0x2855711 "Firefox": ("Gecko" "Firefox-bin") 139x128+779+211 +779+211
0x2828954 "Firefox": ("Gecko" "Firefox-bin") 236x177+545+72 +545+72
0x3200a2d (has no name): () 760x91+0+0 +0+0
0x3200a0d (has no name): () 760x91+0+0 +0+0
0x3200a28 (has no name): () 150x150+0+0 +0+0
0x3200a25 (has no name): ()
[Desktop-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?
Another attempt: $ cat /etc/modprobe.d/blacklist_i2c-nvidia-gpu.conf # https://askubuntu.com/a/1289997 blacklist i2c_nvidia_gpu Didn't make any difference. My judgment is that this is NOT a hardware issue, a plain software one indicated by: As the flow of dmesg items ends; if I start tapping ESC ant Enter keys repeatedly I will see the X / Wayland GUI Login screen within 10 seconds. If i do NOT do that key-tapping, then the boot stop just prior to the login screen; screen is black, cursor flashing in upper left corner (at least to begin with), it stays like that indefinitely, after some time cooling fans start blowing - so there appears to be some CPU-intensive thing going on. The only way out of this is holding the power button until power drops off. Looking into the dmesg log, there is nothing after the 10 second mark. What appears after 10 seconds on a tap-a-long-boot doesn't seem to be related, the list isn't long and does not seem to contain any leads into the issue. -- 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/1988658 Title: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize? Status in pulseaudio package in Ubuntu: New Bug description: $ cat /etc/os-release NAME="Ubuntu" VERSION="20.04.5 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.5 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal 3 to 5 of 10 boot occasions stops prematurely. dmesg (included here, I assume) indicates a pulseaudio failure stopping the booting. I have NOT investigated further (knowledge limit). This very latest bootup seemed to indicate that there is something waiting on the keyboard, as I got all the way "up" after beating repeatedly - alternating - on ESC and ENTER --- dmesg tail on this boot --- 4 sec pause from previous line (at 9 secs) [ 13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 13.444031] usb usb3: root hub lost power or was reset [ 13.444032] usb usb4: root hub lost power or was reset [ 13.557170] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61) [ 17.001076] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 17.105681] rfkill: input handler disabled [ 28.694324] Bluetooth: RFCOMM TTY layer initialized [ 28.694328] Bluetooth: RFCOMM socket layer initialized [ 28.694331] Bluetooth: RFCOMM ver 1.11 [ 28.922797] rfkill: input handler enabled [ 29.043050] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 31.669031] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 31.907300] rfkill: input handler disabled [ 41.959736] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 78.940840] usb usb3: root hub lost power or was reset [ 78.940841] usb usb4: root hub lost power or was reset [ 929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 929.174669] usb usb3: root hub lost power or was reset [ 929.174671] usb usb4: root hub lost power or was reset -- end --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sun Sep 4 08:19:01 2022 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G731GU.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G731GU
[Desktop-packages] [Bug 1990005] Re: Visible columns option missing function
** Changed in: nautilus (Ubuntu) Status: New => Confirmed ** Changed in: nautilus (Ubuntu) Assignee: (unassigned) => Eugenio (thsgiannotti) -- 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/1990005 Title: Visible columns option missing function Status in nautilus package in Ubuntu: Confirmed Bug description: In Ubuntu 20.04 nautilus setting Preferences > List Columns was affecting display on ALL the folders and was possible to remove the column 'Star' while in Ubuntu 22.10 nautilus 1:43~rc-1ubuntu1 setting 'Visible Columns' affect only the current folder and can't remove the 'Star' column. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~rc-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 16 20:00:16 2022 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1064, 734)' InstallationDate: Installed on 2022-09-08 (8 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43~alpha-1 nautilus-extension-gnome-terminal 3.45.90-1ubuntu1 python3-nautilus 4.0~alpha-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1990005/+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 1990005] Re: Visible columns option missing function
Reported in https://gitlab.gnome.org/GNOME/nautilus/-/issues/2496 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2496 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2496 -- 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/1990005 Title: Visible columns option missing function Status in nautilus package in Ubuntu: New Bug description: In Ubuntu 20.04 nautilus setting Preferences > List Columns was affecting display on ALL the folders and was possible to remove the column 'Star' while in Ubuntu 22.10 nautilus 1:43~rc-1ubuntu1 setting 'Visible Columns' affect only the current folder and can't remove the 'Star' column. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~rc-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 16 20:00:16 2022 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1064, 734)' InstallationDate: Installed on 2022-09-08 (8 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43~alpha-1 nautilus-extension-gnome-terminal 3.45.90-1ubuntu1 python3-nautilus 4.0~alpha-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1990005/+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
