[Desktop-packages] [Bug 2011350] Re: ERROR:../src/nautilus-gtk4-helpers.c:116:gtk_widget_get_first_child: assertion failed: (GTK_IS_CONTAINER (widget))
Tracking in https://errors.ubuntu.com/problem/d6e8be4f90a24d66fd0bf410ccb31d3c6fd0eb9b ** Summary changed: - Nautilus crash on close (Ubuntu 22.04) + ERROR:../src/nautilus-gtk4-helpers.c:116:gtk_widget_get_first_child: assertion failed: (GTK_IS_CONTAINER (widget)) ** Description changed: + https://errors.ubuntu.com/problem/d6e8be4f90a24d66fd0bf410ccb31d3c6fd0eb9b + + --- Title: nautilus crashed with SIGABRT in g_assertion_message_expr() - - Sometimes Nautilus crashes when closing a window instead of exiting cleanly. It wouldn't be so bad if it didn't bring other windows down too. + Sometimes Nautilus crashes when closing a window instead of exiting + cleanly. It wouldn't be so bad if it didn't bring other windows down + too. It usually happens when the window has multiple tabs and/or they contain lots of pictures. It may be related to the thumbnails or the image viewer. I tried to attach the crash log but it looks like apport only attached generic system info. I may have used the wrong apport command so I attached the .crash file manually. I'm not sure if it has all the necessary symbols tho. Description: Ubuntu 22.04.2 LTS Release: 22.04 Nautilus 1:42.2-0ubuntu2.1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- 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/2011350 Title: ERROR:../src/nautilus-gtk4-helpers.c:116:gtk_widget_get_first_child: assertion failed: (GTK_IS_CONTAINER (widget)) Status in nautilus package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/d6e8be4f90a24d66fd0bf410ccb31d3c6fd0eb9b --- Title: nautilus crashed with SIGABRT in g_assertion_message_expr() Sometimes Nautilus crashes when closing a window instead of exiting cleanly. It wouldn't be so bad if it didn't bring other windows down too. It usually happens when the window has multiple tabs and/or they contain lots of pictures. It may be related to the thumbnails or the image viewer. I tried to attach the crash log but it looks like apport only attached generic system info. I may have used the wrong apport command so I attached the .crash file manually. I'm not sure if it has all the necessary symbols tho. Description: Ubuntu 22.04.2 LTS Release: 22.04 Nautilus 1:42.2-0ubuntu2.1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
[Desktop-packages] [Bug 2011335] Re: Graphics Driver Problem
Your CD-ROM is experiencing read errors that might be blocking the kernel and delaying booting. So please try removing any disc you have inserted. Also the attached logs are from recovery mode so don't show the original problem. Please reproduce the issue by booting WITHOUT recovery mode, then reboot again and run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/2011335 Title: Graphics Driver Problem Status in Ubuntu: Incomplete Bug description: I am having an issue with Ubuntu Graphics Driver whenever I try to open my pc after booting ubuntu my monitor gets a blank screen, I don't know why this is happening. For Booting my Ubuntu successfully I have to go to the advanced option from the boot menu and then run ubuntu from there. I think it is a graphics driver problem as after booting ubuntu from advanced settings I get a message saying that the graphics driver will not boot for booting them restart the pc and run ubuntu normally. My PC Specs Monitor with VGA directly form the mother board Integrated graphics of Intel Core i3 10100 Mother board MSI M410 M-HV3 Ask Ubuntu question link https://askubuntu.com/questions/1458896/ubuntu-graphics-driver-problem-intel/1458901#1458901 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 12 17:42:17 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: anbox-ashmem/1, 5.19.0-32-generic, x86_64: installed anbox-ashmem/1, 5.19.0-35-generic, x86_64: installed anbox-binder/1: added GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc8] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd CometLake-S GT2 [UHD Graphics 630] [1458:d000] InstallationDate: Installed on 2022-11-14 (117 days ago) InstallationMedia: MachineType: Gigabyte Technology Co., Ltd. H410M H V3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=18c74b79-bde0-49d3-9a2f-9238bdfe8fee ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F6 dmi.board.asset.tag: Default string dmi.board.name: H410M H V3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF6:bd03/25/2022:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnH410MHV3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH410MHV3:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H510 MB dmi.product.name: H410M H V3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2011335/+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 2011321] Re: random windows launching with wrong title bar settings
This is likely related to the new X11 window frame code in mutter 44. I can't find any upstream bugs that match this one but there are other bugs in 44 relating to the new functionality... https://gitlab.gnome.org/GNOME/mutter/-/issues/2673 https://gitlab.gnome.org/GNOME/mutter/-/issues/2682 https://gitlab.gnome.org/GNOME/mutter/-/issues/2660 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2673 https://gitlab.gnome.org/GNOME/mutter/-/issues/2673 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2682 https://gitlab.gnome.org/GNOME/mutter/-/issues/2682 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2660 https://gitlab.gnome.org/GNOME/mutter/-/issues/2660 ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) -- 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/2011321 Title: random windows launching with wrong title bar settings Status in mutter package in Ubuntu: New Bug description: With recent gnome-shell in Lunar, some of my windows, seemingly at random, are launching with weird title bars that don't reflect the title bar settings I have configured. E.g., the font in the title bar is not the same as for other windows, and the buttons on the right when I have them configured via the Tweaks apps to be on the left. Logging out and logging back in seems to clear up the issue temporarily. Again, this isn't happening with all windows even within the same session. Truly bizarre. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 21:10:00 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-17 (175 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 44~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2022-11-17 (114 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2011321/+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 2002432] Re: X11 not started during boot (intel: waited 2020 ms for i915.ko driver to load)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/2002432 Title: X11 not started during boot (intel: waited 2020 ms for i915.ko driver to load) Status in linux package in Ubuntu: Expired Status in xserver-xorg-video-intel package in Ubuntu: Won't Fix Bug description: After update from Ubuntu 20.04->22.10 X11 was not correctly updated. I can only boot into recovery mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Jan 10 18:45:16 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: acpi-call/1.2.2, 5.15.0-56-generic, x86_64: installed acpi-call/1.2.2, 5.15.0-57-generic, x86_64: installed tp_smapi/0.43, 5.15.0-56-generic, x86_64: installed tp_smapi/0.43, 5.15.0-57-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:501e] InstallationDate: Installed on 2015-11-17 (2611 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20AV002WXS ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=23ec64aa-726f-4a3c-b489-2dbbc0a36528 ro recovery nomodeset dis_ucode_ldr i915.enable_hangcheck=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2018 dmi.bios.release: 1.93 dmi.bios.vendor: LENOVO dmi.bios.version: J4ET93WW(1.93) dmi.board.asset.tag: Not Available dmi.board.name: 20AV002WXS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ4ET93WW(1.93):bd05/30/2018:br1.93:svnLENOVO:pn20AV002WXS:pvrThinkPadL540:rvnLENOVO:rn20AV002WXS:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AV_BU_Think_FM_ThinkPadL540: dmi.product.family: ThinkPad L540 dmi.product.name: 20AV002WXS dmi.product.sku: LENOVO_MT_20AV_BU_Think_FM_ThinkPad L540 dmi.product.version: ThinkPad L540 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1 version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 xserver.bootTime: Tue Jan 10 18:24:35 2023 xserver.configfile: /root/xorg.conf.new xserver.devices: xserver.errors: Server terminated with error (2). Closing log file. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:21.1.3-2ubuntu2.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002432/+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 2011317] Re: gnome-shell spontaneously logging me out when screen locked, laptop lid closed
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/2011317 Title: gnome-shell spontaneously logging me out when screen locked, laptop lid closed Status in gnome-shell package in Ubuntu: Incomplete Bug description: In the short time since I've installed the recent GNOME updates in Lunar, I've been logged out spontaneously at least three times while my laptop lid was closed and screen locked and I wasn't doing anything with my computer. Perhaps the attached logs will help you figure out why/how? ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 16:57:51 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-17 (175 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 44~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2022-11-17 (114 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011317/+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 2011317] Re: gnome-shell spontaneously logging me out when screen locked, laptop lid closed
The screen flickering is bug 2007668 which suggests that machine is still on kernel 5.19? -- 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/2011317 Title: gnome-shell spontaneously logging me out when screen locked, laptop lid closed Status in gnome-shell package in Ubuntu: Incomplete Bug description: In the short time since I've installed the recent GNOME updates in Lunar, I've been logged out spontaneously at least three times while my laptop lid was closed and screen locked and I wasn't doing anything with my computer. Perhaps the attached logs will help you figure out why/how? ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 16:57:51 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-17 (175 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 44~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2022-11-17 (114 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011317/+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 2011271] Re: gdm3: "Oh no! Something has gone wrong."
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.
Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
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/2011271
Title:
gdm3: "Oh no! Something has gone wrong."
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
I have installed ubuntu-desktop on Ubuntu Lunar using a RISCV system
with Nvidia GT 710 as well as on a system with a Radeon 8450. In both
cases gdm3 does not show a dialog but a message "Oh no! Something has
gone wrong." Kinetic and Jammy work fine.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gdm3 43.0-3ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-1013.14-generic 5.19.17
Uname: Linux 5.19.0-1013-generic riscv64
ApportVersion: 2.26.0-0ubuntu2
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Fri Mar 10 21:53:33 2023
InstallationDate: Installed on 2023-02-22 (16 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release
riscv64 (20230221)
ProcCpuinfoMinimal:
processor: 3
hart : 3
isa : rv64imafdc
mmu : sv39
uarch: sifive,u74-mc
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=vt220
SourcePackage: gdm3
UpgradeStatus: Upgraded to lunar on 2023-03-10 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011271/+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 2011279] Re: xorg
Please run the following command: journalctl -b0 > journal.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => gnome-shell-extension-desktop-icons-ng (Ubuntu) ** Summary changed: - xorg + The desktop icon is not displayed, and the right-click menu is incompletely loaded ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: New => Incomplete -- 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/2011279 Title: The desktop icon is not displayed, and the right-click menu is incompletely loaded Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Incomplete Bug description: 桌面标不显示，右键菜单加载不完整 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 07:57:08 2023 DistUpgraded: 2022-11-12 11:37:26,280 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: nvidia/525.85.05, 6.1.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22ca] Subsystem: Lenovo TU117M [GeForce MX450] [17aa:22ca] InstallationDate: Installed on 2022-01-02 (432 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211105) MachineType: LENOVO 20W0005VCD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=b4c00f4f-589b-42e2-b402-7ea8b75191a7 ro quiet splash systemd.unified_cgroup_hierarchy=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2022-11-12 (118 days ago) dmi.bios.date: 11/21/2022 dmi.bios.release: 1.54 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET54W (1.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0005VCD dmi.board.vendor: LENOVO dmi.board.version: SDK0L77769 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET54W(1.54):bd11/21/2022:br1.54:efr1.42:svnLENOVO:pn20W0005VCD:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0005VCD:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0005VCD dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2011279/+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 2011257] Re: Latest gnome-shell hanging regularly
Please also find the system log entries (journalctl -b0) from the time of the hang. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/2011257 Title: Latest gnome-shell hanging regularly Status in gnome-shell package in Ubuntu: Incomplete Bug description: In the short time I've had the newest GNOME updates for Lunar, my gnome-shell has hung twice. The first time I had just logged into a Google account in Chrome, and it popped up the window asking me if I wanted to switch to a new Chrome profile rather than logging into that account in the same profile, and I clicked the yes button to do that, and then my screen simply hang and refused to do anything for about 30-45 seconds, after which it unhung. The mouse pointer moved during the hang but nothing else. The second time I attempted to open an external drive that was mounted by clicking on its icon in the dock, and the open animation appeared but the folder didn't open. I clicked again and the open animation appeared again but again the folder did not open. At this point everything hung--once again, mouse cursor moved but nothing else would happen no matter what I typed or clicked. Waiting this one out didn't work; I had to SSH into the machine from another bo and kill -9 the gnome-shell process to escape. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 10 16:20:01 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (1302 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 44~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2022-11-24 (106 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011257/+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 2011257] Re: Latest gnome-shell hanging regularly
Thanks for the bug report. Please try disabling each of your shell extensions and tell us if that resolves the issue. It might be the locally installed ones or I suspect it might be Ubuntu Dock to blame. If that does not resolve the issue then please try deleting the locally installed extensions: cd ~/.local/share/gnome-shell/ rm -rf extensions and then log in again. -- 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/2011257 Title: Latest gnome-shell hanging regularly Status in gnome-shell package in Ubuntu: Incomplete Bug description: In the short time I've had the newest GNOME updates for Lunar, my gnome-shell has hung twice. The first time I had just logged into a Google account in Chrome, and it popped up the window asking me if I wanted to switch to a new Chrome profile rather than logging into that account in the same profile, and I clicked the yes button to do that, and then my screen simply hang and refused to do anything for about 30-45 seconds, after which it unhung. The mouse pointer moved during the hang but nothing else. The second time I attempted to open an external drive that was mounted by clicking on its icon in the dock, and the open animation appeared but the folder didn't open. I clicked again and the open animation appeared again but again the folder did not open. At this point everything hung--once again, mouse cursor moved but nothing else would happen no matter what I typed or clicked. Waiting this one out didn't work; I had to SSH into the machine from another bo and kill -9 the gnome-shell process to escape. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 10 16:20:01 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (1302 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 44~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2022-11-24 (106 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011257/+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 2011270] Re: Printing intermittenly fails -- autodetected network printer
** Package changed: xorg (Ubuntu) => 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/2011270 Title: Printing intermittenly fails -- autodetected network printer Status in Ubuntu: New Bug description: It appears that print jobs passed to the auto-detected printer "adding" wizard do not always succeed. See in these error messages how hpcups is passed a null object to print. It's unclear what the interactions is between the auto-discovery gnome(?) applet, the hpcups system, and dbus. The net effect is that a print job is sent to the printer defined here, and it just gets stuck in "stopped". With no error message or way for the user to resolve the issue. I'm not sure where to begin debugging ... Error messages in question : Mar 10 16:44:17 semiauto dbus-daemon[680]: [system] Activating service name='org.opensuse.CupsPkHelper.Mechanism' requested by ':1.1929' (uid=1000 pid=485631 comm="gnome-control-center printers" label="unconfined") (using servicehelper) Mar 10 16:44:17 semiauto dbus-daemon[680]: [system] Successfully activated service 'org.opensuse.CupsPkHelper.Mechanism' Mar 10 16:44:25 semiauto google-chrome.desktop[496973]: Warning: disabling flag --expose_wasm due to conflicting flags Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 79: unable to open /var/lib/hp/hplip.state: No such file or directory Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 129: validate_plugin_version() Failed to get Plugin version from [/var/lib/hp/hplip.state] Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 173: Plugin version is not matching Mar 10 16:44:34 semiauto hpcups[515382]: prnt/hpcups/HPCupsFilter.cpp 505: m_Job initialization failed with error = 48 Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 244: Invalid Library handler pLibHandler = NULL. Mar 10 16:45:01 semiauto CRON[515541]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Mar 10 16:45:09 semiauto gnome-shell[333439]: Window manager warning: Ping serial 447743079 was reused for window W713, previous use was for window 0xc00014. Mar 10 16:45:20 semiauto systemd[4596]: vte-spawn-4d0c2df5-8c91-461c-ac5d-b95a2bc252a9.scope: Consumed 33.860s CPU time. Mar 10 16:45:20 semiauto gnome-shell[333439]: JS ERROR: TypeError: this.actor is null#012_syncEnabled@resource:///org/gnome/shell/ui/windowManager.js:138:25#012onStopped@resource:///org/gnome/shell/ui/windowManager.js:150:35#012_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:150:22#012_easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:316:60#012_destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1596:21#012onStopped@resource:///org/gnome/shell/ui/windowManager.js:1564:39#012_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:150:22#012_easeActor/<@resource:///org/gnome/shell/ui/environment.js:239:64 Mar 10 16:45:23 semiauto dbus-daemon[680]: [system] Activating service name='org.opensuse.CupsPkHelper.Mechanism' requested by ':1.1929' (uid=1000 pid=485631 comm="gnome-control-center printers" label="unconfined") (using servicehelper) Mar 10 16:45:23 semiauto systemd[4596]: app-gnome-virtualbox-495654.scope: Consumed 11min 33.878s CPU time. Mar 10 16:45:23 semiauto dbus-daemon[680]: [system] Successfully activated service 'org.opensuse.CupsPkHelper.Mechanism' Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Settings.SearchProvider' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Calculator.SearchProvider' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Characters' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Notes.SearchProvider' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Successfully activated service 'org.gnome.Settings.SearchProvider' Make and model auto-reported is: "HP LaserJet Professional m1217nfw MFP, hpcups 3.22.6, requires proprietary plugin" yes, it has commas. URI is reported as: dnssd://HP%20LaserJet%20Professional%20M1217nfw%20MFP._pdl-datastream._tcp.local/ and "location" is aparrently blank. I can troubleshoot further. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2
[Desktop-packages] [Bug 2011251] Re: gnome-shell gets into state where clicking on window title bars doesn't raise them
Tracking in https://gitlab.gnome.org/GNOME/mutter/-/issues/2660 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2660 https://gitlab.gnome.org/GNOME/mutter/-/issues/2660 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/mutter/-/issues/2660 Importance: Unknown Status: Unknown ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => 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/2011251 Title: gnome-shell gets into state where clicking on window title bars doesn't raise them Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: After the most recent Lunar updates (i.e., with the newest GNOME) my gnome-shell got into a state where clicking on the title bar of a window wouldn't raise the window (or do anything else), while clicking inside the window raised it as expected. The problem went away after I rebooted. I think this may have occurred after some other aberrant behavior, specifically the shell hanging for about 30 seconds (I will file a separate bug about that), so it's possible that things were in some sort of broken state because of that and this bug isn't actually specifically about the title bar, but I thought I should file a bug report about it just in case it's something other people start seeing so we can see how frequently it's happening. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 10 16:16:22 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (1302 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 44~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2022-11-24 (106 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2011251/+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 2010924] Re: MT7921K --> BLE funktion don't working
Thanks for the bug report. This is a kernel bug, but your kernel "6.2.0-76060200-generic" is not an officially supported one. Can you check to see if the same bug exists in a supported Ubuntu kernel? ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2010924 Title: MT7921K --> BLE funktion don't working Status in linux package in Ubuntu: Incomplete Bug description: Hi, i have MT7921K BT chip that BLE function is not working with linux, but normal BT is working. I try several distros and some live-iso and get same effect. BLE just not working with this device. I have other BT adapters and BLE is working for them. This is a probe for my PC: https://linux-hardware.org/?probe=969ab4279f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2010924/+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 2011362] [NEW] automatic time zone does not detect time zone change from the network
Public bug reported: Observed: Went on a trip to the US from Croatia. Laptop connected to local LAN. External IP correctly identified to be in the US. Noticed that my local time zone is still Croatian. Checked time & date settings and saw that "automatic time zone" is enabled. Expected: the time zone would change to the local US timezone as soon as the laptop detected the change in the local network Reproducability: 1/1 Workaround: manual setting of time zone? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 ProcVersionSignature: Ubuntu 5.4.0-144.161~18.04.1-generic 5.4.229 Uname: Linux 5.4.0-144-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 02:45:45 2023 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-05-10 (1767 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2020-03-04 (1103 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2011362 Title: automatic time zone does not detect time zone change from the network Status in gnome-control-center package in Ubuntu: New Bug description: Observed: Went on a trip to the US from Croatia. Laptop connected to local LAN. External IP correctly identified to be in the US. Noticed that my local time zone is still Croatian. Checked time & date settings and saw that "automatic time zone" is enabled. Expected: the time zone would change to the local US timezone as soon as the laptop detected the change in the local network Reproducability: 1/1 Workaround: manual setting of time zone? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 ProcVersionSignature: Ubuntu 5.4.0-144.161~18.04.1-generic 5.4.229 Uname: Linux 5.4.0-144-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 02:45:45 2023 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-05-10 (1767 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2020-03-04 (1103 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011362/+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 2009902] Re: Windows do not open on screen or with long delay.
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- ubuntu-dock (Ubuntu) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2009902 Title: Windows do not open on screen or with long delay. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: On login, clicking on 2nd hard drive icon and/or Files (nautilus) there is a long delay in anything opening. Sometimes I can open a Terminal, sometimes I can't. When application windows do open promptly, they are often "off-screen" visible from the Activities overview, but not on the workspace itself when "zoomed in" after clicking on one of the windows. This is happening on Lunar Lobster. Upgraded from a fresh install of Kinetic Kudu with a fresh ISO downloaded today 9 March, 2023. I ran: sudo apt install --reinstall gnome-shell ubuntu-desktop gdm3 Reinstall completed successfully but problems persisted after a cold boot. Interface has started behaving again for now, but this has happened through multiple cold boots (reboot menu not reliably responsive either). **Expected Behavior:** Click on application shortcut on the panel, application window opens in active workspace. **What Happened Instead:** Clicked on app icon, spinning wheel or no response at all. Window sometimes opens but is only visible through Activities overview. Clicking on window in this view "zooms back in" and hides the window again. **Release and Package Info** No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 gnome-shell: Installed: 43.2-1ubuntu1 Candidate: 43.2-1ubuntu1 Version table: *** 43.2-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 43.2-1ubuntu1 Uname: Linux 6.1.0-16-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 9 17:54:32 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1673971989 ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/nathaniel ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-03-09 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 43.2-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 RelatedPackageVersions: mutter-common 43.2-6ubuntu1 Tags: third-party-packages lunar Uname: Linux 6.1.0-16-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-03-09 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2009902/+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 1974029] Re: [nvidia] vram memory leak under Wayland
willian, the image in comment #4 shows Xwayland is using the most VRAM. That might be an Xwayland bug or it might just be a resource-hungry app. To identify potential apps you can run 'xwininfo' and the cursor will change to a cross whenever it is over an Xwayland app. You can also run 'xrestop' to get a list of the most resource hungry Xwayland apps. -- 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/1974029 Title: [nvidia] vram memory leak under Wayland Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: I use 3 monitors. When I turn two of then off and on, the "memory usage" shown by nvidia-smi grows by approximately 400 MB each cycle. When used video memory reaches maximum my card has (it ix GTX 970 with 4GB) the graphical system sort of crashes (desktop is not shown, one of the monitor does not show image at all). This occurs only under Wayland. Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0c.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 18 14:50:11 2022 DistUpgraded: 2022-03-19 09:03:59,252 INFO cache.commit() DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed nvidia/510.60.02, 5.15.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GM204 [GeForce GTX 970] [1458:367a] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=UUID=ca73c670-cd82-4bb7-9d49-1e036cf94a1a ro usbcore.autosuspend=-1 libata.force=1.00:noncq acpi_enforce_resources=lax libata.noacpi=1 amd_iommu=on iommu=pt SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-03-19 (60 days ago) dmi.bios.date: 08/10/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5861 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO 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.:bvr5861:bd08/10/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: 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 mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1974029/+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 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
** Changed in: mutter (Ubuntu) Status: Incomplete => Confirmed -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 2011313] Re: gnome-control-center crashes after launch
Yeah.. That "Couldn't get locale for language: (null)" warning comes from a patch which I wrote initially, and first I feared that the segfault is related to that. But it's not. I committed a fix which will get rid of the warning in this situation: https://salsa.debian.org/gnome-team/gnome-control- center/-/commit/53e9a9a2 But it still segfaults. For some reason it fails to fetch the user data properly. My thought is that since the problem seems to be gone in g-c-c 1:44~rc, it's not worth it to figure out why exactly the alpha version crashes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2011313 Title: gnome-control-center crashes after launch Status in gnome-control-center package in Ubuntu: In Progress Bug description: I had successfully opened settings and used it to change some of the desktop options (size of the docker icons, etc.). Then I clicked on "Users" and ubuntu-settings crashed. Since then, I am unable to open ubuntu-settings - it will open and flash up on the screen before crashing. This has continued even after restarting the machine a few times. ubuntu-settings version: 23.04.2 500 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-settings 23.04.2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 18:33:16 2023 InstallationDate: Installed on 2023-03-11 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+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 1974029] Re: [nvidia] vram memory leak under Wayland
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1974029 Title: [nvidia] vram memory leak under Wayland Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: I use 3 monitors. When I turn two of then off and on, the "memory usage" shown by nvidia-smi grows by approximately 400 MB each cycle. When used video memory reaches maximum my card has (it ix GTX 970 with 4GB) the graphical system sort of crashes (desktop is not shown, one of the monitor does not show image at all). This occurs only under Wayland. Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0c.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 18 14:50:11 2022 DistUpgraded: 2022-03-19 09:03:59,252 INFO cache.commit() DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed nvidia/510.60.02, 5.15.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GM204 [GeForce GTX 970] [1458:367a] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=UUID=ca73c670-cd82-4bb7-9d49-1e036cf94a1a ro usbcore.autosuspend=-1 libata.force=1.00:noncq acpi_enforce_resources=lax libata.noacpi=1 amd_iommu=on iommu=pt SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-03-19 (60 days ago) dmi.bios.date: 08/10/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5861 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO 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.:bvr5861:bd08/10/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: 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 mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1974029/+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 1973084] Re: transmission-daemon high RAM usage
It's possible to sideload the debian package and its dependencies. I did it before reporting this bug and it has been working flawlessly. Not the perfect solution but the solution that is avaliable. Don't forget to lock the package and dependencies using apt-mark, otherwise, it will get upgraded and the bug will return. On Sun, Mar 12, 2023, 15:15 lan <1973...@bugs.launchpad.net> wrote: > Same problem, is possible to have an update to fix this problem? > Thx > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1973084 > > Title: > transmission-daemon high RAM usage > > Status in transmission package in Ubuntu: > Confirmed > > Bug description: > Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign > on a Raspberry Pi 4. > > It "eats" RAM and the RAM usage grows each hour until it crashes the > system. > > I sideloaded transmission-daemon and its dependancies from debian 11 > (arm64) locked the packages so apt won't update them and, ever since, > this issue hasn't happened. > > > Description:Ubuntu 22.04 LTS > Release:22.04 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+subscriptions > > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Confirmed Bug description: Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+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 2011350] Re: Nautilus crash on close (Ubuntu 22.04)
** Description changed: - Sometimes Nautilus crashes when closing a window instead of exiting - cleanly. + + Title: nautilus crashed with SIGABRT in g_assertion_message_expr() + + + Sometimes Nautilus crashes when closing a window instead of exiting cleanly. It wouldn't be so bad if it didn't bring other windows down too. It usually happens when the window has multiple tabs and/or they contain lots of pictures. It may be related to the thumbnails or the image viewer. - - I tried to attach the crash log but it looks like apport only attached generic system info. I may have used the wrong apport command. + I tried to attach the crash log but it looks like apport only attached + generic system info. I may have used the wrong apport command so I + attached the .crash file manually. I'm not sure if it has all the + necessary symbols tho. Description: Ubuntu 22.04.2 LTS Release: 22.04 Nautilus 1:42.2-0ubuntu2.1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 -- 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/2011350 Title: Nautilus crash on close (Ubuntu 22.04) Status in nautilus package in Ubuntu: New Bug description: Title: nautilus crashed with SIGABRT in g_assertion_message_expr() Sometimes Nautilus crashes when closing a window instead of exiting cleanly. It wouldn't be so bad if it didn't bring other windows down too. It usually happens when the window has multiple tabs and/or they contain lots of pictures. It may be related to the thumbnails or the image viewer. I tried to attach the crash log but it looks like apport only attached generic system info. I may have used the wrong apport command so I attached the .crash file manually. I'm not sure if it has all the necessary symbols tho. Description: Ubuntu 22.04.2 LTS Release: 22.04 Nautilus 1:42.2-0ubuntu2.1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS
[Desktop-packages] [Bug 2011350] Re: Nautilus crash on close (Ubuntu 22.04)
I'm trying to attach the crash file manually. I hope it is useful. ** Description changed: Sometimes Nautilus crashes when closing a window instead of exiting cleanly. It usually happens when the window has multiple tabs and/or they contain - lots of pictures. + lots of pictures. It may be related to the thumbnails or the image + viewer. + + + I tried to attach the crash log but it looks like apport only attached generic system info. I may have used the wrong apport command. Description: Ubuntu 22.04.2 LTS Release: 22.04 Nautilus 1:42.2-0ubuntu2.1 - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: - evince42.3-0ubuntu3 - file-roller 3.42.0-1 - nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 - nautilus-share0.7.3-2ubuntu6 - --- + evince42.3-0ubuntu3 + file-roller 3.42.0-1 + nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 + nautilus-share0.7.3-2ubuntu6 + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: - evince42.3-0ubuntu3 - file-roller 3.42.0-1 - nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 - nautilus-share0.7.3-2ubuntu6 + evince42.3-0ubuntu3 + file-roller 3.42.0-1 + nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 + nautilus-share0.7.3-2ubuntu6 ** Attachment added: "Nautilus .crash file" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011350/+attachment/5654026/+files/_usr_bin_nautilus.1000.crash -- 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/2011350 Title: Nautilus crash on close (Ubuntu 22.04) Status in nautilus package in Ubuntu: New Bug description: Sometimes Nautilus crashes when closing a window instead of exiting cleanly. It usually happens when the window has multiple tabs and/or they contain lots of pictures. It may be related to the thumbnails or the image viewer. I tried to attach the crash log but it looks like apport only attached generic system info. I may have used the wrong apport command. Description: Ubuntu 22.04.2 LTS Release: 22.04 Nautilus 1:42.2-0ubuntu2.1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" -
[Desktop-packages] [Bug 2011350] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2011350/+attachment/5654025/+files/ProcEnviron.txt -- 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/2011350 Title: Nautilus crash on close (Ubuntu 22.04) Status in nautilus package in Ubuntu: New Bug description: Sometimes Nautilus crashes when closing a window instead of exiting cleanly. It usually happens when the window has multiple tabs and/or they contain lots of pictures. It may be related to the thumbnails or the image viewer. I tried to attach the crash log but it looks like apport only attached generic system info. I may have used the wrong apport command. Description: Ubuntu 22.04.2 LTS Release: 22.04 Nautilus 1:42.2-0ubuntu2.1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011350/+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 2011350] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2011350/+attachment/5654024/+files/ProcCpuinfoMinimal.txt -- 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/2011350 Title: Nautilus crash on close (Ubuntu 22.04) Status in nautilus package in Ubuntu: New Bug description: Sometimes Nautilus crashes when closing a window instead of exiting cleanly. It usually happens when the window has multiple tabs and/or they contain lots of pictures. It may be related to the thumbnails or the image viewer. I tried to attach the crash log but it looks like apport only attached generic system info. I may have used the wrong apport command. Description: Ubuntu 22.04.2 LTS Release: 22.04 Nautilus 1:42.2-0ubuntu2.1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011350/+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 2011350] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/2011350/+attachment/5654023/+files/GsettingsChanges.txt -- 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/2011350 Title: Nautilus crash on close (Ubuntu 22.04) Status in nautilus package in Ubuntu: New Bug description: Sometimes Nautilus crashes when closing a window instead of exiting cleanly. It usually happens when the window has multiple tabs and/or they contain lots of pictures. It may be related to the thumbnails or the image viewer. I tried to attach the crash log but it looks like apport only attached generic system info. I may have used the wrong apport command. Description: Ubuntu 22.04.2 LTS Release: 22.04 Nautilus 1:42.2-0ubuntu2.1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011350/+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 2011350] Re: Nautilus crash on close (Ubuntu 22.04)
apport information ** Description changed: Sometimes Nautilus crashes when closing a window instead of exiting cleanly. It usually happens when the window has multiple tabs and/or they contain lots of pictures. Description: Ubuntu 22.04.2 LTS Release: 22.04 Nautilus 1:42.2-0ubuntu2.1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.3 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2020-06-05 (1010 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + NonfreeKernelModules: nvidia_modeset nvidia + Package: nautilus 1:42.2-0ubuntu2.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 + Tags: jammy + Uname: Linux 5.19.0-35-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) + UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + usr_lib_nautilus: + evince42.3-0ubuntu3 + file-roller 3.42.0-1 + nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 + nautilus-share0.7.3-2ubuntu6 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2011350/+attachment/5654022/+files/Dependencies.txt -- 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/2011350 Title: Nautilus crash on close (Ubuntu 22.04) Status in nautilus package in Ubuntu: New Bug description: Sometimes Nautilus crashes when closing a window instead of exiting cleanly. It usually happens when the window has multiple tabs and/or they contain lots of pictures. It may be related to the thumbnails or the image viewer. I tried to attach the crash log but it looks like apport only attached generic system info. I may have used the wrong apport command. Description: Ubuntu 22.04.2 LTS Release: 22.04 Nautilus 1:42.2-0ubuntu2.1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to:
[Desktop-packages] [Bug 2011350] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/2011350/+attachment/5654019/+files/GsettingsChanges.txt -- 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/2011350 Title: Nautilus crash on close (Ubuntu 22.04) Status in nautilus package in Ubuntu: New Bug description: Sometimes Nautilus crashes when closing a window instead of exiting cleanly. It usually happens when the window has multiple tabs and/or they contain lots of pictures. Description: Ubuntu 22.04.2 LTS Release: 22.04 Nautilus 1:42.2-0ubuntu2.1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011350/+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 2011350] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2011350/+attachment/5654020/+files/ProcCpuinfoMinimal.txt -- 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/2011350 Title: Nautilus crash on close (Ubuntu 22.04) Status in nautilus package in Ubuntu: New Bug description: Sometimes Nautilus crashes when closing a window instead of exiting cleanly. It usually happens when the window has multiple tabs and/or they contain lots of pictures. Description: Ubuntu 22.04.2 LTS Release: 22.04 Nautilus 1:42.2-0ubuntu2.1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011350/+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 2011350] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2011350/+attachment/5654021/+files/ProcEnviron.txt -- 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/2011350 Title: Nautilus crash on close (Ubuntu 22.04) Status in nautilus package in Ubuntu: New Bug description: Sometimes Nautilus crashes when closing a window instead of exiting cleanly. It usually happens when the window has multiple tabs and/or they contain lots of pictures. Description: Ubuntu 22.04.2 LTS Release: 22.04 Nautilus 1:42.2-0ubuntu2.1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011350/+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 2011350] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2011350/+attachment/5654018/+files/Dependencies.txt -- 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/2011350 Title: Nautilus crash on close (Ubuntu 22.04) Status in nautilus package in Ubuntu: New Bug description: Sometimes Nautilus crashes when closing a window instead of exiting cleanly. It usually happens when the window has multiple tabs and/or they contain lots of pictures. Description: Ubuntu 22.04.2 LTS Release: 22.04 Nautilus 1:42.2-0ubuntu2.1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011350/+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 2011350] [NEW] Nautilus crash on close (Ubuntu 22.04)
Public bug reported: Sometimes Nautilus crashes when closing a window instead of exiting cleanly. It usually happens when the window has multiple tabs and/or they contain lots of pictures. Description:Ubuntu 22.04.2 LTS Release:22.04 Nautilus 1:42.2-0ubuntu2.1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected jammy ** Package changed: yaru-theme (Ubuntu) => nautilus (Ubuntu) ** Tags added: apport-collected jammy ** Description changed: Sometimes Nautilus crashes when closing a window instead of exiting cleanly. It usually happens when the window has multiple tabs and/or they contain lots of pictures. Description: Ubuntu 22.04.2 LTS Release: 22.04 Nautilus 1:42.2-0ubuntu2.1 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.3 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2020-06-05 (1010 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + NonfreeKernelModules: nvidia_modeset nvidia + Package: nautilus 1:42.2-0ubuntu2.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 + Tags: jammy + Uname: Linux 5.19.0-35-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) + UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + usr_lib_nautilus: + evince42.3-0ubuntu3 + file-roller 3.42.0-1 + nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 + nautilus-share0.7.3-2ubuntu6 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2011350 Title: Nautilus crash on close (Ubuntu 22.04) Status in nautilus package in Ubuntu: New Bug description: Sometimes Nautilus crashes when closing a window instead of exiting cleanly. It usually happens when the window has multiple tabs and/or they contain lots of pictures. Description: Ubuntu 22.04.2 LTS Release: 22.04 Nautilus 1:42.2-0ubuntu2.1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011350/+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 1973084] Re: transmission-daemon high RAM usage
Same problem, is possible to have an update to fix this problem? Thx -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Confirmed Bug description: Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+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 1961508] Re: Dock displaying over window after resuming from blank screen
The workaround for this is to allow the Dock extension to keep running when the screen is locked. To do this, you need to insert the following text into /usr/share/gnome-shell/extensions/ubuntu- d...@ubuntu.com/metadata.json just before "uuid" (backup it before editing): "session-modes": [ "user", "unlock-dialog" ], So it should look like this: "session-modes": [ "user", "unlock-dialog" ], "uuid": "ubuntu-d...@ubuntu.com", Keep in mind that this is just a workaround, and after the next update, this file may be overwritten, so you will have to edit it again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen Status in Dash to dock: Unknown Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gnome-desktop package in Fedora: Confirmed Bug description: I have Blank Screen set to happen after 2 minutes of inactivity. When resuming from a Blank Screen (by moving the mouse or touching the keyboard), the Dock is displayed over the top of the current program. To get it back to normal I need to click "Restore Down" on the current programs window and then "Maximize" so that the Dock no longer overlaps it. (Note: I have Auto-hide dock turned off.) This only happens sometimes. I can't reproduce the bug it every time. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - Ubuntu 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - Not sure (I guess the Dock is part of the Gnome interface?) 3) What you expected to happen - Dock should not overlap the current program on resume from screen blank. 4) What happened instead - The Dock overlaps the current program on resume from screen blank. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2022-02-18 (24 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 Tags: wayland-session impish Uname: Linux 5.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-02-18 (328 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 43.0-1ubuntu4 Tags: wayland-session third-party-packages kinetic Uname: Linux 5.19.0-28-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+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 2011313] Re: gnome-control-center crashes after launch
I can browse the control-center with resetting the last-panel. When opening "Users" it tells `WARNING: Couldn't get locale for language: (null) Speicherzugriffsfehler (Speicherabzug geschrieben)`. The first thing I realized was that the "Users" section was totally empty. Afterwards gnome-control-center crashed. When adding a new User via command line I could browse the open "Users" tab and the new and the old user were present. After a reboot it was empty again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2011313 Title: gnome-control-center crashes after launch Status in gnome-control-center package in Ubuntu: In Progress Bug description: I had successfully opened settings and used it to change some of the desktop options (size of the docker icons, etc.). Then I clicked on "Users" and ubuntu-settings crashed. Since then, I am unable to open ubuntu-settings - it will open and flash up on the screen before crashing. This has continued even after restarting the machine a few times. ubuntu-settings version: 23.04.2 500 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-settings 23.04.2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 18:33:16 2023 InstallationDate: Installed on 2023-03-11 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+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 1974029] Re: [nvidia] vram memory leak under Wayland
Same problem. Ubuntu 22.04. I constantly change the desktop from my main monitor, to a tv to mirroring. Picture shows large memory usage, but not from where it comes. If asked, I can provide additional info. RTX 3070 GPU. ** Attachment added: "Screenshot from 2023-03-12 12-31-43.png" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1974029/+attachment/5653955/+files/Screenshot%20from%202023-03-12%2012-31-43.png -- 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/1974029 Title: [nvidia] vram memory leak under Wayland Status in Mutter: New Status in mutter package in Ubuntu: New Bug description: I use 3 monitors. When I turn two of then off and on, the "memory usage" shown by nvidia-smi grows by approximately 400 MB each cycle. When used video memory reaches maximum my card has (it ix GTX 970 with 4GB) the graphical system sort of crashes (desktop is not shown, one of the monitor does not show image at all). This occurs only under Wayland. Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0c.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 18 14:50:11 2022 DistUpgraded: 2022-03-19 09:03:59,252 INFO cache.commit() DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed nvidia/510.60.02, 5.15.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GM204 [GeForce GTX 970] [1458:367a] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=UUID=ca73c670-cd82-4bb7-9d49-1e036cf94a1a ro usbcore.autosuspend=-1 libata.force=1.00:noncq acpi_enforce_resources=lax libata.noacpi=1 amd_iommu=on iommu=pt SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-03-19 (60 days ago) dmi.bios.date: 08/10/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5861 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO 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.:bvr5861:bd08/10/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: 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 mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1974029/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 2009824] Re: Crash in raspberrypi_ipa_proxy when compiled with LTO
This bug was fixed in the package libcamera - 0.0.4-2ubuntu2 --- libcamera (0.0.4-2ubuntu2) lunar; urgency=medium * Fix static order init problems when building under LTO (LP: #2009824) -- Dave Jones Fri, 03 Mar 2023 15:42:32 + ** Changed in: libcamera (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcamera in Ubuntu. https://bugs.launchpad.net/bugs/2009824 Title: Crash in raspberrypi_ipa_proxy when compiled with LTO Status in libcamera package in Ubuntu: Fix Released Bug description: The libcamera 0.0.4 implementation currently in lunar has a couple of global objects which are unsafely allocated, leading to a crash in the subordinate raspberrypi_ipa_proxy process when used at runtime. The attached patch resolves the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2009824/+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 2009918] Re: package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to install/upgrade: impossible de créer un lien symbolique de secours de « ./usr/lib/x86_64-linux-gnu/dri/
if you are creating your own iso, then you can also disable automatic
updates on it
** Changed in: mesa (Ubuntu)
Status: New => Invalid
--
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/2009918
Title:
package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to
install/upgrade: impossible de créer un lien symbolique de secours de
« ./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une
nouvelle version: Aucun espace disponible sur le périphérique
Status in mesa package in Ubuntu:
Invalid
Bug description:
Running inside a VM (KVM) from a remastered ISO
The screen also show some artifacts horizontal dotted lines which disappear
after a second or two.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5json: {
CasperVersion: 1.445.1
CompositorRunning: None
Date: Fri Mar 10 08:21:08 2023
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ErrorMessage: impossible de créer un lien symbolique de secours de «
./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une nouvelle
version: Aucun espace disponible sur le périphérique
ExtraDebuggingInterest: No
GraphicsCard:
Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00
[VGA controller])
Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
InstallationDate: Installed on 2022-02-22 (380 days ago)
InstallationMedia:
LiveMediaBuild: Systemback Live (MobiOffice) - Release amd64
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
480M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz boot=casper
initrd=/casper/initrd.gz quiet splash
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal,
3.8.2-0ubuntu2
PythonDetails: N/A
SourcePackage: mesa
Title: package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to
install/upgrade: impossible de créer un lien symbolique de secours de «
./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une nouvelle
version: Aucun espace disponible sur le périphérique
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.13.0-1ubuntu1.1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-focal
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-focal
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
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
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/mesa/+bug/2009918/+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 2011305] Re: package libgl1-mesa-dri 22.3.6-1ubuntu2 failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/dri/i915_dri.so« zu überschreiben, welches auch in Paket lib
*** This bug is a duplicate of bug 2006744 *** https://bugs.launchpad.net/bugs/2006744 ** This bug has been marked a duplicate of bug 2006744 libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict -- 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/2011305 Title: package libgl1-mesa-dri 22.3.6-1ubuntu2 failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/dri/i915_dri.so« zu überschreiben, welches auch in Paket libgl1-amber-dri:amd64 21.3.7-0ubuntu1 ist Status in mesa package in Ubuntu: New Bug description: Error during update ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgl1-mesa-dri 22.3.6-1ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Wed Mar 8 20:40:12 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: virtualbox/7.0.6, 5.19.0-21-generic, x86_64: installed virtualbox/7.0.6, 6.1.0-16-generic, x86_64: installed DpkgTerminalLog: Vorbereitung zum Entpacken von .../00-libgl1-mesa-dri_22.3.6-1ubuntu1_amd64.deb ... Entpacken von libgl1-mesa-dri:amd64 (22.3.6-1ubuntu1) über (22.2.5-0ubuntu1) ... [1mdpkg:[0m Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-pp6Hzh/00-libgl1-mesa-dri_22.3.6-1ubuntu1_amd64.deb (--unpack): Versuch, »/usr/lib/x86_64-linux-gnu/dri/i915_dri.so« zu überschreiben, welches auch in Paket libgl1-amber-dri:amd64 21.3.7-0ubuntu1 ist ErrorMessage: Versuch, »/usr/lib/x86_64-linux-gnu/dri/i915_dri.so« zu überschreiben, welches auch in Paket libgl1-amber-dri:amd64 21.3.7-0ubuntu1 ist ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2022-12-13 (88 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=eccd5abd-1337-4d37-bd5f-2fdb537f804a ro quiet splash Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: mesa Title: package libgl1-mesa-dri 22.3.6-1ubuntu2 failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/dri/i915_dri.so« zu überschreiben, welches auch in Paket libgl1-amber-dri:amd64 21.3.7-0ubuntu1 ist UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2011305/+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 2008919] Re: [FFe] Implement support for "buttercup_eval"
This bug was fixed in the package dh-elpa - 2.0.16ubuntu2 --- dh-elpa (2.0.16ubuntu2) lunar; urgency=medium * dh_elpa_test: Implement new buttercup_eval directive. (LP: #2008919) -- Sergio Durigan Junior Wed, 01 Mar 2023 13:08:44 -0500 ** Changed in: dh-elpa (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dh-elpa in Ubuntu. https://bugs.launchpad.net/bugs/2008919 Title: [FFe] Implement support for "buttercup_eval" Status in dh-elpa package in Ubuntu: Fix Released Status in dh-elpa package in Debian: Unknown Bug description: dh-elpa supports the "ert_eval" directive inside d/elpa-test, which allows the package to provide custom Elisp code to be executed before ERT is invoked. Unfortunately, a similar feature is missing for buttercup tests. This means that, whenever a package uses buttercup to run its tests, the maintainer needs to override dh_elpa_test and invoke buttercup by hand. This, however, only works during build time; dh-elpa is also used to run autopkgtest, and in that specific scenario it's not possible to execute custom Elisp code using buttercup at all. Why is this important, you might ask. Well, I've been investigating a bug in Emacs 28.2's native compilation mechanism which affects a bunch of packages (see bug #2006963 for more details). One of those affected packages is flycheck, which uses buttercup. I uploaded a fix for a flycheck FTBFS which addresses the problem, but the package still fails its autopkgtest because of the problem mentioned above. Long story short, I've implemented the support for a new dh-elpa directive called "buttercup_eval" and would like it to Lunar. I also proposed the feature to Debian here: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1032202 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-elpa/+bug/2008919/+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 1997168] Re: [snap] Passwords are saved but not loaded with gnome keyring
I'm trying to understand why the user is enforced to do action described in
file:///snap/chromium/2381/firstrun/password-en.html
manually instead of the package manager which introduced the change ?
And if the user is required to take manual action, the message which is
slightly modified version of post #9 above needs to be more precise. Especially
if with or without this manual action any password migration/reencryption
happened or will happen and how it's exactly done. Also besides 'Login Data' in
my case there are few more:
'Login Data-journal' - empty - probably SQlite which could be ignored
'Login Data 2-journal' - also empty but here I'm not sure
'Login Data For Account' - not empty, almost the size of 'Login Data'
'Login Data For Account-journal' - empty
--
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/1997168
Title:
[snap] Passwords are saved but not loaded with gnome keyring
Status in chromium-browser package in Ubuntu:
Fix Released
Bug description:
Steps to reproduce:
* System: Fresh (minimal, desktop) installation of Ubuntu 22.04 LTS in
VirtualBox to rule out any side-effects from preexisting configurations
* Install latest updates: `sudo apt update && sudo apt upgrade -y && sudo apt
dist-upgrade -y && sudo snap refresh`
* Install chromium from snap (`sudo snap install chromium`)
* Connect chromium to password manager service (`sudo snap connect
chromium:password-manager-service`) -> now chromium should be able to use gnome
keyring to store its master password
* Launch chromium, navigate to "chrome://settings/passwords"
* Add a new password ("Saved Passwords" -> "Add")
* Password shows up under "Saved Passwords" as expected.
* Close chromium and open it again, navigate to "chrome://settings/passwords"
* Expected: Password should show up. Instead: The list is empty.
* Add another password: List stays empty.
What I found out so far:
* Despite of the list showing up as empty in chromium, both passwords have
been stored in "~/snap/chromium/common/chromium/Default/Login Data" (to
confirm, grep for the username of the saved login, as the password itself will
be encrypted)
* It seems that the snap version of chromium does not create the entries
"Chrome Safe Storage" and "Chrome Safe Storage Control" in the gnome keyring,
which seems to be necessary at the moment (see http://crbug.com/660005). If a
non-snap version of chromium (e.g. from
https://launchpad.net/~savoury1/+archive/ubuntu/chromium) is installed first,
which is used to bootstrap the user's chromium config folder and which creates
the aforementioned entries in the gnome keyring, things are working fine, even
after transitioning to the snap version.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997168/+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 2011335] [NEW] Graphics Driver Problem
Public bug reported: I am having an issue with Ubuntu Graphics Driver whenever I try to open my pc after booting ubuntu my monitor gets a blank screen, I don't know why this is happening. For Booting my Ubuntu successfully I have to go to the advanced option from the boot menu and then run ubuntu from there. I think it is a graphics driver problem as after booting ubuntu from advanced settings I get a message saying that the graphics driver will not boot for booting them restart the pc and run ubuntu normally. My PC Specs Monitor with VGA directly form the mother board Integrated graphics of Intel Core i3 10100 Mother board MSI M410 M-HV3 Ask Ubuntu question link https://askubuntu.com/questions/1458896/ubuntu-graphics-driver-problem-intel/1458901#1458901 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 12 17:42:17 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: anbox-ashmem/1, 5.19.0-32-generic, x86_64: installed anbox-ashmem/1, 5.19.0-35-generic, x86_64: installed anbox-binder/1: added GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc8] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd CometLake-S GT2 [UHD Graphics 630] [1458:d000] InstallationDate: Installed on 2022-11-14 (117 days ago) InstallationMedia: MachineType: Gigabyte Technology Co., Ltd. H410M H V3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=18c74b79-bde0-49d3-9a2f-9238bdfe8fee ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F6 dmi.board.asset.tag: Default string dmi.board.name: H410M H V3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF6:bd03/25/2022:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnH410MHV3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH410MHV3:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H510 MB dmi.product.name: H410M H V3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy 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/2011335 Title: Graphics Driver Problem Status in xorg package in Ubuntu: New Bug description: I am having an issue with Ubuntu Graphics Driver whenever I try to open my pc after booting ubuntu my monitor gets a blank screen, I don't know why this is happening. For Booting my Ubuntu successfully I have to go to the advanced option from the boot menu and then run ubuntu from there. I think it is a graphics driver problem as after booting ubuntu from advanced settings I get a message saying that the graphics driver will not boot for booting them restart the pc and run ubuntu normally. My PC Specs Monitor with VGA directly form the mother board Integrated graphics of Intel Core i3 10100 Mother board MSI M410 M-HV3 Ask Ubuntu question link https://askubuntu.com/questions/1458896/ubuntu-graphics-driver-problem-intel/1458901#1458901 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 12 17:42:17 2023 DistUpgraded: Fresh install DistroCodename: jammy
[Desktop-packages] [Bug 2011313] Re: gnome-control-center crashes after launch
Sorry, I was on Ubuntu 22.04 when testing that command, but they seem to have changed the schema name. On 23.04 this would have worked: gsettings reset org.gnome.Settings last-panel -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2011313 Title: gnome-control-center crashes after launch Status in gnome-control-center package in Ubuntu: In Progress Bug description: I had successfully opened settings and used it to change some of the desktop options (size of the docker icons, etc.). Then I clicked on "Users" and ubuntu-settings crashed. Since then, I am unable to open ubuntu-settings - it will open and flash up on the screen before crashing. This has continued even after restarting the machine a few times. ubuntu-settings version: 23.04.2 500 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-settings 23.04.2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 18:33:16 2023 InstallationDate: Installed on 2023-03-11 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+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 1720250] Re: im-config configuration ignored with gdm3
Ok, the reason I left a comment here was very logical: disabling the code in /etc/profile.d/input-method-config.sh script made the problem "go away". And in the header of this script there is a reference to this particular bug number, so that was my first place to go to. However, I completely agree with you, that the real cause of the problem may be elsewhere and it should be reported against the corresponding subsystem. I will do as you suggest as soon as I have more information (I am not working on this actively, as my "workaround" seems to be ok, but of course I am curious and so "in the back of my mind" I am still considering this issue :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1720250 Title: im-config configuration ignored with gdm3 Status in gdm3 package in Ubuntu: Invalid Status in im-config package in Ubuntu: Fix Released Bug description: After having logged in via gdm3, the IM related environment variables are always set like this: $ env | grep -E '_IM|XMOD' QT_IM_MODULE=ibus XMODIFIERS=@im=ibus Changing ~/.xinputrc to e.g. xim makes no difference, so gdm3 prevents all other IM frameworks but IBus from working. This problem seems to be similar to bug #1594681 (which was fixed). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+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 1720250] Re: im-config configuration ignored with gdm3
Well, I don't claim that im-config is bug free forever after the fix of this bug. New issues show up. My point is that trying to revive an old and closed bug report is simply not the right way to call the developers' attention to new issues. My advice still stands: Use Ask Ubuntu to get help to sort things out. If you conclude that there is a bug, you are welcome to submit a new bug report about your problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1720250 Title: im-config configuration ignored with gdm3 Status in gdm3 package in Ubuntu: Invalid Status in im-config package in Ubuntu: Fix Released Bug description: After having logged in via gdm3, the IM related environment variables are always set like this: $ env | grep -E '_IM|XMOD' QT_IM_MODULE=ibus XMODIFIERS=@im=ibus Changing ~/.xinputrc to e.g. xim makes no difference, so gdm3 prevents all other IM frameworks but IBus from working. This problem seems to be similar to bug #1594681 (which was fixed). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+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 2011313] Re: gnome-control-center crashes after launch
That command: gsettings reset org.gnome.ControlCenter last-panel Doesn't work for me - I get: No such schema “org.gnome.ControlCenter” -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2011313 Title: gnome-control-center crashes after launch Status in gnome-control-center package in Ubuntu: In Progress Bug description: I had successfully opened settings and used it to change some of the desktop options (size of the docker icons, etc.). Then I clicked on "Users" and ubuntu-settings crashed. Since then, I am unable to open ubuntu-settings - it will open and flash up on the screen before crashing. This has continued even after restarting the machine a few times. ubuntu-settings version: 23.04.2 500 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-settings 23.04.2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 18:33:16 2023 InstallationDate: Installed on 2023-03-11 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+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 1720250] Re: im-config configuration ignored with gdm3
@Gunnar You are assuming that the bug was fixed completely by the code in /etc/profile.d/input-method-config.sh. Well, in complex entities, such as the operating systems (even in user-space level) there is no such thing as "complete, universal bugfix". There will always be some subtle cases, which the developer did not think of and these may or may not come up later, which may be 7 years later as in this case. I assume that my 20+ years of Linux kernel development experience allow me to make such a statement. The real problem is that I have 7 other machines (identical clones) running exactly the same Ubuntu 18 system and on none of them this problem manifests itself. There are a few differences between this machine and the rest, namely: 1. I configured LVM2 on it. 2. I use bind-mounts in /etc/fstab heavily (for /usr/local and other parts). 3. I use QEMU on this machine extensively, so VFIO/PCI passthrough etc etc are configured. 4. Maybe a few other bits and pieces. Oh well, don't worry, I won't bother you further with this. I will try to figure out the cause and will let you know if I find it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1720250 Title: im-config configuration ignored with gdm3 Status in gdm3 package in Ubuntu: Invalid Status in im-config package in Ubuntu: Fix Released Bug description: After having logged in via gdm3, the IM related environment variables are always set like this: $ env | grep -E '_IM|XMOD' QT_IM_MODULE=ibus XMODIFIERS=@im=ibus Changing ~/.xinputrc to e.g. xim makes no difference, so gdm3 prevents all other IM frameworks but IBus from working. This problem seems to be similar to bug #1594681 (which was fixed). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+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 2009224] Re: pulseaudio does not recognize PCI SoundBlaster card
I confirm this. It happens with kernel 5.19 but works with 5.15 and earlier (tried with grub options /advanced ubuntu options/boot with previous kernel version). -- 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/2009224 Title: pulseaudio does not recognize PCI SoundBlaster card Status in alsa-driver package in Ubuntu: New Bug description: I didn't have sound after an update to Ubuntu (and a reboot the next day). Pulseaudio does not recognize my soundcard. Since all my work involves audio, I have switched to Windows 10 (I have a dual boot computer). LSPCI finds my sound card but alsa and pacmd don't. Until this is fixed, I am no longer using UBuntu but am switching to Windows 10. Let me know when this issue is resolved. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: george 4472 F pipewire-media- /dev/snd/pcmC1D0c: george 4473 F...m pulseaudio /dev/snd/seq:george 4471 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 3 13:14:07 2023 InstallationDate: Installed on 2021-07-19 (592 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to jammy on 2022-08-14 (201 days ago) dmi.bios.date: 03/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A3 dmi.board.name: H11H4-AD2 dmi.board.vendor: Acer dmi.board.version: V:1.1 dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A3:bd03/18/2016:br5.11:svnAcer:pnSoniaHC:pvr:rvnAcer:rnH11H4-AD2:rvrV1.1:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: SoniaHC dmi.product.sku: dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2009224/+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 2011313] Re: gnome-control-center crashes after launch
And thanks for the tip ref running it without going to "Users" :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2011313 Title: gnome-control-center crashes after launch Status in gnome-control-center package in Ubuntu: In Progress Bug description: I had successfully opened settings and used it to change some of the desktop options (size of the docker icons, etc.). Then I clicked on "Users" and ubuntu-settings crashed. Since then, I am unable to open ubuntu-settings - it will open and flash up on the screen before crashing. This has continued even after restarting the machine a few times. ubuntu-settings version: 23.04.2 500 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-settings 23.04.2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 18:33:16 2023 InstallationDate: Installed on 2023-03-11 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+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 2011313] Re: gnome-control-center crashes after launch
As a data point, when I run gnome-control-center from the terminal I get a "Segmentation Error" and core dump. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2011313 Title: gnome-control-center crashes after launch Status in gnome-control-center package in Ubuntu: In Progress Bug description: I had successfully opened settings and used it to change some of the desktop options (size of the docker icons, etc.). Then I clicked on "Users" and ubuntu-settings crashed. Since then, I am unable to open ubuntu-settings - it will open and flash up on the screen before crashing. This has continued even after restarting the machine a few times. ubuntu-settings version: 23.04.2 500 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-settings 23.04.2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 18:33:16 2023 InstallationDate: Installed on 2023-03-11 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+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
