[Desktop-packages] [Bug 2052996] [NEW] nautilus crashes when drag&drop the image file
Public bug reported: Repro Steps - `repro.webm` attached: 1. Run nautilus 2. Navigate to https://plugins.hex-rays.com/. 3. Drag and drop the Hex-Rays logo onto the Desktop. 4. SEGV at 0x000b Crash Report: ProblemType: Crash Signal: 11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 13 14:52:00 2024 DistroRelease: Ubuntu 22.04 JournalErrors: 2월 13 14:51:57 dch3ck-Z790-UD nautilus[104092]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed 2월 13 14:51:59 dch3ck-Z790-UD nautilus[104092]: g_file_get_child: assertion '!g_path_is_absolute (name)' failed 2월 13 14:51:59 dch3ck-Z790-UD nautilus[104092]: g_file_equal: assertion 'G_IS_FILE (file2)' failed 2월 13 14:51:59 dch3ck-Z790-UD nautilus[104092]: g_file_copy: assertion 'G_IS_FILE (destination)' failed ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= LC_ADDRESS=ko_KR.UTF-8 SHELL=/bin/bash LC_NAME=ko_KR.UTF-8 LC_MEASUREMENT=ko_KR.UTF-8 LC_TIME=ko_KR.UTF-8 LC_MONETARY=ko_KR.UTF-8 LANGUAGE=ko:en_AU:en_CA:en_GB:en_US:en LC_TELEPHONE=ko_KR.UTF-8 LC_PAPER=ko_KR.UTF-8 LC_NUMERIC=ko_KR.UTF-8 PATH=(custom, no user) LANG=ko_KR.UTF-8 LC_IDENTIFICATION=ko_KR.UTF-8 * thread #7, name = 'pool-org.gnome.', stop reason = signal SIGSEGV: invalid address (fault address: 0x0) frame #0: 0x55b7dc24e624 nautilus`___lldb_unnamed_symbol4282 + 1140 nautilus`___lldb_unnamed_symbol4282: -> 0x55b7dc24e624 <+1140>: movl (%rax), %ebx 0x55b7dc24e626 <+1142>: testl %r12d, %r12d 0x55b7dc24e629 <+1145>: je 0x55b7dc24ea60; <+2224> 0x55b7dc24e62f <+1151>: movl 0x118(%rsp), %edx (lldb) bt * thread #7, name = 'pool-org.gnome.', stop reason = signal SIGSEGV: invalid address (fault address: 0x0) * frame #0: 0x55b7dc24e624 nautilus`___lldb_unnamed_symbol4282 + 1140 frame #1: 0x55b7dc24fdde nautilus`___lldb_unnamed_symbol4283 + 542 frame #2: 0x7fb6019b1194 libgio-2.0.so.0`___lldb_unnamed_symbol5250 + 116 frame #3: 0x7fb6026876b4 libglib-2.0.so.0`___lldb_unnamed_symbol2565 + 116 frame #4: 0x7fb602684a51 libglib-2.0.so.0`___lldb_unnamed_symbol2558 + 81 frame #5: 0x7fb601294ac3 libc.so.6`start_thread(arg=) at pthread_create.c:442:8 frame #6: 0x7fb601326850 libc.so.6`__clone3 at clone3.S:81 (lldb) c Process 128770 resuming Process 128770 exited with status = 11 (0x000b) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Attachment added: "repro.webm" https://bugs.launchpad.net/bugs/2052996/+attachment/5746017/+files/repro.webm -- 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/2052996 Title: nautilus crashes when drag&drop the image file Status in nautilus package in Ubuntu: New Bug description: Repro Steps - `repro.webm` attached: 1. Run nautilus 2. Navigate to https://plugins.hex-rays.com/. 3. Drag and drop the Hex-Rays logo onto the Desktop. 4. SEGV at 0x000b Crash Report: ProblemType: Crash Signal: 11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 13 14:52:00 2024 DistroRelease: Ubuntu 22.04 JournalErrors: 2월 13 14:51:57 dch3ck-Z790-UD nautilus[104092]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed 2월 13 14:51:59 dch3ck-Z790-UD nautilus[104092]: g_file_get_child: assertion '!g_path_is_absolute (name)' failed 2월 13 14:51:59 dch3ck-Z790-UD nautilus[104092]: g_file_equal: assertion 'G_IS_FILE (file2)' failed 2월 13 14:51:59 dch3ck-Z790-UD nautilus[104092]: g_file_copy: assertion 'G_IS_FILE (destination)' failed ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= LC_ADDRESS=ko_KR.UTF-8 SHELL=/bin/bash LC_NAME=ko_KR.UTF-8 LC_MEASUREMENT=ko_KR.UTF-8 LC_TIME=ko_KR.UTF-8 LC_MONETARY=ko_KR.UTF-8 LANGUAGE=ko:en_AU:en_CA:en_GB:en_US:en LC_TELEPHONE=ko_KR.UTF-8 LC_PAPER=ko_KR.UTF-8 LC_NUMERIC=ko_KR.UTF-8 PATH=(custom, no user) LANG=ko_KR.UTF-8 LC_IDENTIFICATION=ko_KR.UTF-8 * thread #7, name = 'pool-org.gnome.', stop reason = signal SIGSEGV: invalid address (fault address: 0x0) frame #0: 0x55b7dc24e624 nautilus`___lldb_unnamed_symbol4282 + 1140 nautilus`___lldb_unnamed_symbol4282: -> 0x55b7dc24e624 <+1140>: movl (%rax), %ebx 0x55b7dc24e626 <+1142>: testl %r12d, %r12d 0x55b7dc24e629 <+1145>: je 0x55b7dc24ea60; <+2224> 0x55b7dc24e62f <+1151>: movl 0x118(%rsp), %edx (lldb) bt * thread #7, name = 'pool-org.gnome.', stop reason = signal SIGSEGV: invalid address (fault address: 0x0) * frame #0: 0x55b7dc24e624 nautilus`___lldb_unnamed_symbol4282 + 1140 frame #1: 0x55b7dc24fdde nautilus`___lldb_unnamed_symbol4283 + 542 frame #2: 0x7fb6019b1194 libgio-2.0.so.0`___lldb_unnamed_symbol5250 + 116 frame #3: 0x7fb6026876b4 libglib-2.0.so.0
[Desktop-packages] [Bug 1959507] Re: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f)
** Tags removed: kinetic -- 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/1959507 Title: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f) Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi, I'm starting a VM Ubuntu 22.04 on QEMU/KVM and this alert appears. It seems to myself there is an issue between Wayland and spice-vdagent. Regards, Michel ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 29 09:52:12 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-01-28 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 41.3-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: __pthread_kill_implementation (no_tid=0, signo=6, threadid=140083783699840) at pthread_kill.c:44 __pthread_kill_internal (signo=6, threadid=140083783699840) at pthread_kill.c:80 __GI___pthread_kill (threadid=140083783699840, signo=signo@entry=6) at pthread_kill.c:91 __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 __GI_abort () at abort.c:79 Title: gnome-shell crashed with SIGABRT in __pthread_kill_implementation() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959507/+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 2052859] Re: Windows go to behind others when clicking with mouse
Please run:
sudo apt remove gnome-shell-extensions
and then log in again. Does the bug still occur? If so then please again
run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
--
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/2052859
Title:
Windows go to behind others when clicking with mouse
Status in mutter package in Ubuntu:
Incomplete
Bug description:
After installing ubuntu graphics-drivers ppa nvidia-550 driver, the
bug appears.
When there are several windows on top of each other, clicking within
the topmost window, the window seems to disappear. Actually, the
window is still there, but just goes behind another window, that comes
in front of the clicked window. The program in the window that is
clicked will not notice the click.
This does not happen with all programs. Mines is a good example
program. If the window fills full screen, this happens, but if it is
smaller, only partially covering the screen, it does not happen.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.fabric-imex-mgmt:
DeviceFileMinor: 4323
DeviceFileMode: 256
DeviceFileModify: 1
.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..2d.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 550.40.07 Thu Jan 18
07:30:58 UTC 2024
GCC version: gcc version 13.2.0 (Ubuntu 13.2.0-4ubuntu3)
.tmp.unity_support_test.0:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CompizPlugins:
[core,bailer,detection,composite,opengl,compiztoolbox,decor,snap,gnomecompat,resize,regex,imgpng,grid,mousepoll,move,unitymtgrabhandles,animation,vpswitch,place,session,workarounds,expo,wall,fade,ezoom,scale,unityshell]
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 10 17:56:32 2024
DistUpgraded: 2023-11-03 20:23:14,648 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation AD103 [GeForce RTX 4070 Ti SUPER] [10de:2705] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:e130]
InstallationDate: Installed on 2012-12-22 (4067 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic
root=UUID=a21f1300-e2a3-44c9-a667-86fc6184627b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-11-03 (99 days ago)
dmi.bios.date: 02/28/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: A.J0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MPG X570 GAMING PLUS (MS-7C37)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.J0:bd02/28/2023:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C37:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570GAMINGPLUS(MS-7C37):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C37
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu4
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
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-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
xserver.bootTime: Fri Feb 9 20:05:59
[Desktop-packages] [Bug 2052832] Re: Desktop lock-screen is bypassed after switching to virtual tty on console
Thanks for the bug report. I'm not sure if your using lightdm is a factor here (jammy should be using gdm3 instead). But the first thing we should check is to see if gnome-shell crashed and restarted. Please follow the steps in: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment Separately please also: * Try: gnome-extensions disable 'clock- overr...@gnomeshell.kryogenix.org' * Log another bug about the repeating log message: "Failed to create offscreen effect framebuffer: Failed to create an OpenGL framebuffer object". ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags added: nvidia -- 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/2052832 Title: Desktop lock-screen is bypassed after switching to virtual tty on console Status in gnome-shell package in Ubuntu: Incomplete Bug description: Expected to have to provide session user password to return to GUI desktop after locking that session via the task-bar power-button dropdown -> Lock button. Actually was able to resume GUI session without providing a password. Steps to reproduce: In desktop session, mouse-click the task bar power icon to show its dropdown, and select Lock Desktop session locks and displays a password prompt box. Press CTL-ALT-F1 to show virtual console tty1 Press CTL-ALT-F6 to return to GUI. GUI is restored without prompting for a password. Repeatable with other virtual consoles (F2 F3 etc.) Repeatable whether or not I logged in on the virtual console or just switched to it then back to the GUI. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-92.102-generic 5.15.131 Uname: Linux 5.15.0-92-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 9 14:06:32 2024 DisplayManager: lightdm ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-08-12 (545 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2052832/+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 2052832] Re: Desktop lock-screen is bypassed after switching to virtual tty on console
** Information type changed from Private Security to Public Security -- 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/2052832 Title: Desktop lock-screen is bypassed after switching to virtual tty on console Status in gnome-shell package in Ubuntu: New Bug description: Expected to have to provide session user password to return to GUI desktop after locking that session via the task-bar power-button dropdown -> Lock button. Actually was able to resume GUI session without providing a password. Steps to reproduce: In desktop session, mouse-click the task bar power icon to show its dropdown, and select Lock Desktop session locks and displays a password prompt box. Press CTL-ALT-F1 to show virtual console tty1 Press CTL-ALT-F6 to return to GUI. GUI is restored without prompting for a password. Repeatable with other virtual consoles (F2 F3 etc.) Repeatable whether or not I logged in on the virtual console or just switched to it then back to the GUI. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-92.102-generic 5.15.131 Uname: Linux 5.15.0-92-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 9 14:06:32 2024 DisplayManager: lightdm ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-08-12 (545 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2052832/+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 2046020] Re: Plymouth is eating up close to 40 seconds in my ubuntu
[Expired for plymouth (Ubuntu) because there has been no activity for 60 days.] ** Changed in: plymouth (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/2046020 Title: Plymouth is eating up close to 40 seconds in my ubuntu Status in plymouth package in Ubuntu: Expired Bug description: pachake name - plymouth-quit-wait.service When i reboot the system - There has been significant delay - despite using a 16gb ram with Cor I5 processor the boot time to start using the laptop is close to 110 seconds when i check the blame it shows close to 40 seconds is being eaten up by plymouth pachage itself ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: plymouth 0.9.5+git20211018-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131 Uname: Linux 5.15.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Dec 9 11:56:47 2023 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2023-03-02 (281 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:a031 Quanta Computer, Inc. VGA WebCam Bus 001 Device 004: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros QCA9377 Bluetooth Bus 001 Device 002: ID 3151:3020 YICHIP Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A315-55G ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-91-generic root=UUID=9eb358a8-44a6-448b-b086-39276decf015 ro 0 quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-91-generic root=UUID=9eb358a8-44a6-448b-b086-39276decf015 ro 0 quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: Upgraded to jammy on 2023-12-08 (0 days ago) dmi.bios.date: 06/14/2019 dmi.bios.release: 1.5 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Happy_WC dmi.board.vendor: WHL dmi.board.version: V1.05 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd06/14/2019:br1.5:efr1.4:svnAcer:pnAspireA315-55G:pvrV1.05:rvnWHL:rnHappy_WC:rvrV1.05:cvnChassisManufacturer:ct10:cvrChassisVersion:sku: dmi.product.family: Aspire 3 dmi.product.name: Aspire A315-55G dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2046020/+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 1959507] Re: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f)
That was a bot error. The duplicate bug is not related to this one. ** Tags removed: noble -- 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/1959507 Title: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f) Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi, I'm starting a VM Ubuntu 22.04 on QEMU/KVM and this alert appears. It seems to myself there is an issue between Wayland and spice-vdagent. Regards, Michel ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 29 09:52:12 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-01-28 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 41.3-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: __pthread_kill_implementation (no_tid=0, signo=6, threadid=140083783699840) at pthread_kill.c:44 __pthread_kill_internal (signo=6, threadid=140083783699840) at pthread_kill.c:80 __GI___pthread_kill (threadid=140083783699840, signo=signo@entry=6) at pthread_kill.c:91 __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 __GI_abort () at abort.c:79 Title: gnome-shell crashed with SIGABRT in __pthread_kill_implementation() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959507/+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 2052922] Re: gnome-shell crashed with SIGABRT in ???()
Comment #2 is incorrect. The bot is treating all assertions as the same bug. ** This bug is no longer a duplicate of bug 1959507 gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f) ** Summary changed: - gnome-shell crashed with SIGABRT in ???() + gnome-shell crashed with SIGABRT at ERROR:../src/st/st-icon-theme.c:3584:st_icon_info_load_icon_finish: assertion failed: (icon_info_get_pixbuf_ready (icon_info)) -- 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/2052922 Title: gnome-shell crashed with SIGABRT at ERROR:../src/st/st-icon- theme.c:3584:st_icon_info_load_icon_finish: assertion failed: (icon_info_get_pixbuf_ready (icon_info)) Status in gnome-shell package in Ubuntu: New Bug description: This happened under some I/O load, with the laptop in power saver mode. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: gnome-shell 45.3-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 12 10:52:57 2024 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2024-02-07 (5 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) JournalErrors: lut 12 10:52:55 username-laptop systemd[1]: /lib/systemd/system/rsyslog.service:24: Failed to parse protect home value, ignoring: readonly lut 12 10:52:56 username-laptop gnome-shell[6437]: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. lut 12 10:52:57 username-laptop systemd[1]: /lib/systemd/system/rsyslog.service:24: Failed to parse protect home value, ignoring: readonly lut 12 10:52:58 username-laptop systemd[1]: /lib/systemd/system/rsyslog.service:24: Failed to parse protect home value, ignoring: readonly ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=pl_PL.UTF-8 PATH=(custom, user) SHELL=/usr/bin/zsh XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 45.3-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 st_icon_info_load_icon_finish () at /usr/lib/gnome-shell/libst-13.so ??? () at /usr/lib/gnome-shell/libst-13.so ??? () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell crashed with SIGABRT in ???() UpgradeStatus: Upgraded to noble on 2024-02-07 (5 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2052922/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
kgeotag is also affected by #2052491 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bubblewrap in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Confirmed Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Confirmed Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kgeotag package in Ubuntu: Confirmed Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: In Progress Status in kontact package in Ubuntu: In Progress Status in marble package in Ubuntu: In Progress Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Confirmed Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Confirmed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: In Progress Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2046844/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Also affects: kgeotag (Ubuntu) Importance: Undecided Status: New ** Changed in: kgeotag (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bubblewrap in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Confirmed Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Confirmed Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kgeotag package in Ubuntu: Confirmed Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: In Progress Status in kontact package in Ubuntu: In Progress Status in marble package in Ubuntu: In Progress Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Confirmed Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Confirmed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: In Progress Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2046844/+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 1416766] Re: gnome-system-monitor doesn't remember window size after being resize and system start
** Changed in: gnome-system-monitor (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1416766 Title: gnome-system-monitor doesn't remember window size after being resize and system start Status in gnome-system-monitor package in Ubuntu: Fix Released Bug description: gnome-system-monitor doesn't remember window size after being resize and system start ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gnome-system-monitor 3.8.2.1-2ubuntu4 Uname: Linux 3.18.5-031805-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 1 01:40:26 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-01-26 (5 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1416766/+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 2052859] Re: Windows go to behind others when clicking with mouse
thank you for looking at this.
Did not help. Journal attavhed.
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2052859/+attachment/5745969/+files/journal.txt
--
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/2052859
Title:
Windows go to behind others when clicking with mouse
Status in mutter package in Ubuntu:
Incomplete
Bug description:
After installing ubuntu graphics-drivers ppa nvidia-550 driver, the
bug appears.
When there are several windows on top of each other, clicking within
the topmost window, the window seems to disappear. Actually, the
window is still there, but just goes behind another window, that comes
in front of the clicked window. The program in the window that is
clicked will not notice the click.
This does not happen with all programs. Mines is a good example
program. If the window fills full screen, this happens, but if it is
smaller, only partially covering the screen, it does not happen.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.fabric-imex-mgmt:
DeviceFileMinor: 4323
DeviceFileMode: 256
DeviceFileModify: 1
.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..2d.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 550.40.07 Thu Jan 18
07:30:58 UTC 2024
GCC version: gcc version 13.2.0 (Ubuntu 13.2.0-4ubuntu3)
.tmp.unity_support_test.0:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CompizPlugins:
[core,bailer,detection,composite,opengl,compiztoolbox,decor,snap,gnomecompat,resize,regex,imgpng,grid,mousepoll,move,unitymtgrabhandles,animation,vpswitch,place,session,workarounds,expo,wall,fade,ezoom,scale,unityshell]
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 10 17:56:32 2024
DistUpgraded: 2023-11-03 20:23:14,648 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation AD103 [GeForce RTX 4070 Ti SUPER] [10de:2705] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:e130]
InstallationDate: Installed on 2012-12-22 (4067 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic
root=UUID=a21f1300-e2a3-44c9-a667-86fc6184627b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-11-03 (99 days ago)
dmi.bios.date: 02/28/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: A.J0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MPG X570 GAMING PLUS (MS-7C37)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.J0:bd02/28/2023:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C37:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570GAMINGPLUS(MS-7C37):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C37
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu4
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
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-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
xserver.bootTime: Fri Feb 9 20:05:59 2
[Desktop-packages] [Bug 2052963] [NEW] Upgrade from jammy to mantic failed install for gnome-control-center
Public bug reported: lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 apt-cache policy gnome-control-center gnome-control-center: Installed: (none) Candidate: 1:45.0-1ubuntu3.1 Version table: 1:45.0-1ubuntu3.1 500 500 http://us.archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu mantic-security/main amd64 Packages 1:45.0-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu mantic/main amd64 Packages Expected: A correct installation, with proper suggestions if a package is missing. What happened: I did an upgrade from jammy to mantic, gnome-control-center was missing. When tried to install manually, I got this error: The following packages have unmet dependencies: gnome-control-center : Depends: libsnapd-glib-2-1 (>= 1.63) but it is not installable Couldn't find any way to satisfy the dependency. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/2052963 Title: Upgrade from jammy to mantic failed install for gnome-control-center Status in gnome-control-center package in Ubuntu: New Bug description: lsb_release -rd No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 apt-cache policy gnome-control-center gnome-control-center: Installed: (none) Candidate: 1:45.0-1ubuntu3.1 Version table: 1:45.0-1ubuntu3.1 500 500 http://us.archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu mantic-security/main amd64 Packages 1:45.0-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu mantic/main amd64 Packages Expected: A correct installation, with proper suggestions if a package is missing. What happened: I did an upgrade from jammy to mantic, gnome-control-center was missing. When tried to install manually, I got this error: The following packages have unmet dependencies: gnome-control-center : Depends: libsnapd-glib-2-1 (>= 1.63) but it is not installable Couldn't find any way to satisfy the dependency. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2052963/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
John, The version in the PPA is now older than the version in the repository so no further testing can be done unless the changes in the PPA have now been uploaded (?). That said, regarding electron apps, it does appear as though the .deb versions of Visual Studio Code and Element Desktop are affected. Granted, those are installed from outside the repository, but I'd contend those are applications a gigantic part of the user base depends on. In fact, for Element, that's something the Ubuntu Community will be relying on in short order. The only workarounds for these are to install the snap versions or launch with `--no-sandbox`. In Element's case, it's maintained by a third party, so that's the only factor I can see as being problematic. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bubblewrap in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Confirmed Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Confirmed Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: In Progress Status in kontact package in Ubuntu: In Progress Status in marble package in Ubuntu: In Progress Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Confirmed Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Confirmed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: In Progress Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2046844/+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 2052959] [NEW] FTBFS when rebuilding 1.44
Public bug reported: FTBFS due to test failure after an unrelated autopkgtest change was uploaded (https://launchpad.net/ubuntu/+source/network- manager/1.44.2-7ubuntu2). ok 7 /config/warnings PASS: src/core/tests/config/test-config 7 /config/warnings # (src/core/tests/config/test-config.c:1107) invalid value in config-data .intern.with-whitespace.key2 = (null) (instead of " b c\, d ") exec "./src/core/tests/config/test-config" failed with exit code 133 ERROR: src/core/tests/config/test-config - too few tests run (expected 14, got 7) ERROR: src/core/tests/config/test-config - exited with status 5 See upstream bug report: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1465 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2052959 Title: FTBFS when rebuilding 1.44 Status in network-manager package in Ubuntu: New Bug description: FTBFS due to test failure after an unrelated autopkgtest change was uploaded (https://launchpad.net/ubuntu/+source/network- manager/1.44.2-7ubuntu2). ok 7 /config/warnings PASS: src/core/tests/config/test-config 7 /config/warnings # (src/core/tests/config/test-config.c:1107) invalid value in config-data .intern.with-whitespace.key2 = (null) (instead of " b c\, d ") exec "./src/core/tests/config/test-config" failed with exit code 133 ERROR: src/core/tests/config/test-config - too few tests run (expected 14, got 7) ERROR: src/core/tests/config/test-config - exited with status 5 See upstream bug report: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1465 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2052959/+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 2008355] Re: Unable to set fractional scaling on three monitor setup
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/2008355 Title: Unable to set fractional scaling on three monitor setup Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I have three monitors: one 4K (3840x2160) display and two 2560x1440. I've tried setting fractional scaling to 150% on the 4K display in gnome control center (ubuntu 22.10), but it does not work. It works fine when I disconnect some displays, leaving only the 4K or 4k and one 2560. However, when all three are connected the apply button is disabled and the following message appears: "Changes Cannot be Applied. This could be due to hardware limitations." When gnome-control-center is started from terminal it shows the following warning: ``` (gnome-control-center:12235): display-cc-panel-WARNING **: 18:42:27.389: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors not adjacent ``` thought it doesn't seem to be the case. After some digging I've found a workaround, executing the following commands seems to do what the control panel does: ``` xrdb -m
[Desktop-packages] [Bug 2052824] Re: ubuntu-drivers list warning messages
*** This bug is a duplicate of bug 2037004 *** https://bugs.launchpad.net/bugs/2037004 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2037004, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 2037004 warnings in terminal with software-properties-gtk ** Tags added: mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2052824 Title: ubuntu-drivers list warning messages Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Running "ubuntu-drivers list" as root from commandline give the following output, under Ubuntu 23.10: udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. nvidia-driver-535-server, (kernel modules provided by linux-modules-nvidia-535-server-generic-hwe-22.04) nvidia-driver-535-open, (kernel modules provided by linux-modules-nvidia-535-open-generic-hwe-22.04) nvidia-driver-545, (kernel modules provided by linux-modules-nvidia-545-generic-hwe-22.04) nvidia-driver-535, (kernel modules provided by linux-modules-nvidia-535-generic-hwe-22.04) nvidia-driver-525-open, (kernel modules provided by linux-modules-nvidia-525-open-generic-hwe-22.04) nvidia-driver-545-open, (kernel modules provided by linux-modules-nvidia-545-open-generic-hwe-22.04) nvidia-driver-525, (kernel modules provided by linux-modules-nvidia-525-generic-hwe-22.04) nvidia-driver-525-server, (kernel modules provided by linux-modules-nvidia-525-server-generic-hwe-22.04) nvidia-driver-535-server-open, (kernel modules provided by linux-modules-nvidia-535-server-open-generic-hwe-22.04) Additional Info: e# lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 Background: After updating my drivers the /dev/dri directory was not present, so was looking around and tried: apt update ubuntu-drivers install ubuntu-drivers install --gpgpu ubuntu-drivers list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2052824/+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 2052946] [NEW] Two-finger scroll stops working
Public bug reported: On a thinkpad p15v gen 3. two-finger scroll works initially, after fresh boot, but after some time it stop working at all. A simple way to redproduce: bootup, scroll something in browser, then open new terminal, try to scroll there ( won't scroll as there is not enough content in terminal), after that the twofinger scroll will stop working everywhere until next boot touchpad model: [2.878688] psmouse serio1: synaptics: Touchpad model: 1, fw: 10.32, id: 0x1e2a1, caps: 0xf01ea3/0x940300/0x12e800/0x50, board id: 3471, fw id: 3942087 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-input-libinput 1.2.1-1 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 12 16:38:16 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu InstallationDate: Installed on 2022-07-14 (578 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21D9A0CKCD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic root=/dev/mapper/vgubuntu-root ro selinux=0 quiet splash mitigations=off vt.handoff=7 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2023 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: N3EET35W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 21D9A0CKCD dmi.board.vendor: LENOVO dmi.board.version: SDK0T76479 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrN3EET35W(1.21):bd11/08/2023:br1.21:efr1.15:svnLENOVO:pn21D9A0CKCD:pvrThinkPadP15vGen3:rvnLENOVO:rn21D9A0CKCD:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21D9_BU_Think_FM_ThinkPadP15vGen3: dmi.product.family: ThinkPad P15v Gen 3 dmi.product.name: 21D9A0CKCD dmi.product.sku: LENOVO_MT_21D9_BU_Think_FM_ThinkPad P15v Gen 3 dmi.product.version: ThinkPad P15v Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.0.20230414.1+2061~u22.04 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 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: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy possible-manual-nvidia-install third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/2052946 Title: Two-finger scroll stops working Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: On a thinkpad p15v gen 3. two-finger scroll works initially, after fresh boot, but after some time it stop working at all. A simple way to redproduce: bootup, scroll something in browser, then open new terminal, try to scroll there ( won't scroll as there is not enough content in terminal), after that the twofinger scroll will stop working everywhere until next boot touchpad model: [2.878688] psmouse serio1: synaptics: Touchpad model: 1, fw: 10.32, id: 0x1e2a1, caps: 0xf01ea3/0x940300/0x12e800/0x50, board id: 3471, fw id: 3942087 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-input-libinput 1.2.1-1 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 12 16:38:16 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu InstallationDate: Installed on 2022-07-14 (578 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21D9A0CKCD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic root=/dev/mapper/vgubuntu-root ro
[Desktop-packages] [Bug 1956110] Re: upower requires libimobiledevice6 as a dependency
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: libimobiledevice (Ubuntu) Status: New => Incomplete ** Changed in: upower (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1956110 Title: upower requires libimobiledevice6 as a dependency Status in libimobiledevice package in Ubuntu: Incomplete Status in upower package in Ubuntu: Incomplete Bug description: An iPhone library is required to have power management required by Gnome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1956110/+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 2039757] Re: Fix race condition in gdm with simpledrm and real drm drivers
This bug was fixed in the package gdm3 - 42.0-1ubuntu7.22.04.4 --- gdm3 (42.0-1ubuntu7.22.04.4) jammy; urgency=medium * Add local-display-factory-skip-simpledrm-when-checking-.patch to fix a race condition that occurs with simpledrm (LP: #2039757) -- Mario Limonciello Tue, 30 Jan 2024 11:28:18 -0600 ** Changed in: gdm3 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2039757 Title: Fix race condition in gdm with simpledrm and real drm drivers Status in gdm: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: Fix Released Bug description: [ Impact ] When the kernel has been compiled with FB_EFI=n, FB_VESA=n, SIMPLEDRM=y a series of events can occur that cause simpledrm to race with GDM. When GDM loses the race then a user is left with a black screen. This series of events doesn't currently happen in Jammy kernels, but can happen from a mainline kernel or HWE kernel that enables it. To protect users from this circumstance it is better to fix the race condition. This issue has been readily reproduced in Ubuntu and reported to upstream mutter. It's also already fixed in GNOME 45, included in Mantic and later. https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * GDM can take longer to start up while settling [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 * the changes needed to enable this in the kernel are tracked in bug 1965303 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/2039757/+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 1959507] Re: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f)
** Tags added: noble -- 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/1959507 Title: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f) Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi, I'm starting a VM Ubuntu 22.04 on QEMU/KVM and this alert appears. It seems to myself there is an issue between Wayland and spice-vdagent. Regards, Michel ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 29 09:52:12 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-01-28 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 41.3-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: __pthread_kill_implementation (no_tid=0, signo=6, threadid=140083783699840) at pthread_kill.c:44 __pthread_kill_internal (signo=6, threadid=140083783699840) at pthread_kill.c:80 __GI___pthread_kill (threadid=140083783699840, signo=signo@entry=6) at pthread_kill.c:91 __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 __GI_abort () at abort.c:79 Title: gnome-shell crashed with SIGABRT in __pthread_kill_implementation() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959507/+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 2043820] Re: Unable to contact snap store on Xubuntu from Jammy to Noble
Here is the whole Jenkins archive. The file you asked is in `archive/ubuntu-jammy-noble-xubuntu- amd64_qemu/20240105.141607/artifacts/upgrade_run/system_details/dist- upgrade/main.log`, along with many other files that may also be interesting. ** Attachment added: "archive.zip" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2043820/+attachment/5745887/+files/archive.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2043820 Title: Unable to contact snap store on Xubuntu from Jammy to Noble Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in firefox source package in Noble: Confirmed Status in snapd source package in Noble: Confirmed Bug description: When running `do-release-upgrade -d` on Jammy Xubuntu, the upgrade fails consistently at the `Installing the firefox snap` step. This was first detected on Jenkins [1], then reproduced locally with `auto-upgrade-testing`, then finally by manually running a `do- release-upgrade -d` in a VM. [1]: https://platform-qa-jenkins.ps5.ubuntu.com/view/upgrade- list/job/upgrade_ubuntu-jammy-noble-xubuntu-amd64_qemu/7/consoleFull (Jenkins full log attached) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.17 ProcVersionSignature: User Name 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: XFCE Date: Fri Nov 17 18:24:22 2023 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2043820/+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 2052922] Re: gnome-shell crashed with SIGABRT in ???()
*** This bug is a duplicate of bug 1959507 *** https://bugs.launchpad.net/bugs/1959507 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1959507, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2052922/+attachment/5745874/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/2052922/+attachment/5745876/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2052922/+attachment/5745879/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2052922/+attachment/5745880/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/2052922/+attachment/5745881/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2052922/+attachment/5745883/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2052922/+attachment/5745884/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1959507 gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f) ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2052922 Title: gnome-shell crashed with SIGABRT in ???() Status in gnome-shell package in Ubuntu: New Bug description: This happened under some I/O load, with the laptop in power saver mode. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: gnome-shell 45.3-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 12 10:52:57 2024 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2024-02-07 (5 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) JournalErrors: lut 12 10:52:55 username-laptop systemd[1]: /lib/systemd/system/rsyslog.service:24: Failed to parse protect home value, ignoring: readonly lut 12 10:52:56 username-laptop gnome-shell[6437]: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. lut 12 10:52:57 username-laptop systemd[1]: /lib/systemd/system/rsyslog.service:24: Failed to parse protect home value, ignoring: readonly lut 12 10:52:58 username-laptop systemd[1]: /lib/systemd/system/rsyslog.service:24: Failed to parse protect home value, ignoring: readonly ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=pl_PL.UTF-8 PATH=(custom, user) SHELL=/usr/bin/zsh XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 45.3-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 st_icon_info_load_icon_finish () at /usr/lib/gnome-shell/libst-13.so ??? () at /usr/lib/gnome-shell/libst-13.so ??? () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell crashed with SIGABRT in ???() UpgradeStatus: Upgraded to noble on 2024-02-07 (5 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2052922/+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 2052925] Re: lpoptions -d as root
Thanks, I'm closing for the current serie since it's fixed in Noble but we added it to the team backlog to SRU to Jammy ** Tags added: udeng-2281 ** Changed in: cups (Ubuntu) Status: New => Fix Released ** Changed in: cups (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2052925 Title: lpoptions -d as root Status in cups package in Ubuntu: Fix Released Bug description: Copied from https://github.com/OpenPrinting/cups/issues/454 Yair Yarom submitted Debian bug 1008053 and observed that running lpoptions as root does not update /etc/cups/lpoptions but /root/.cups/lpoptions. Running lpoptions as root (e.g. "lpoptions -d HP-OfficeJet") should update /etc/cups/lpoptions to be the defaults for all users. But instead it tries to update /root/.cups/lpoptions. This has been fixed upstream in cups, in debian sid, and mantic. Proposing to add this change in jammy and older (still supported) series as well. The fix is a one line change in https://github.com/OpenPrinting/cups/pull/456 Thanks. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu ubuntu@jammy-vm:~$ lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ubuntu@jammy-vm:~$ apt-cache policy cups cups: Installed: 2.4.1op1-1ubuntu4.7 Candidate: 2.4.1op1-1ubuntu4.7 Version table: *** 2.4.1op1-1ubuntu4.7 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 2.4.1op1-1ubuntu4 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What you expected to happen: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# 4) What happened instead: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2052925/+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 2052925] Re: lpoptions -d as root
Upstream fix in debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008053 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2052925 Title: lpoptions -d as root Status in cups package in Ubuntu: Fix Released Bug description: Copied from https://github.com/OpenPrinting/cups/issues/454 Yair Yarom submitted Debian bug 1008053 and observed that running lpoptions as root does not update /etc/cups/lpoptions but /root/.cups/lpoptions. Running lpoptions as root (e.g. "lpoptions -d HP-OfficeJet") should update /etc/cups/lpoptions to be the defaults for all users. But instead it tries to update /root/.cups/lpoptions. This has been fixed upstream in cups, in debian sid, and mantic. Proposing to add this change in jammy and older (still supported) series as well. The fix is a one line change in https://github.com/OpenPrinting/cups/pull/456 Thanks. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu ubuntu@jammy-vm:~$ lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ubuntu@jammy-vm:~$ apt-cache policy cups cups: Installed: 2.4.1op1-1ubuntu4.7 Candidate: 2.4.1op1-1ubuntu4.7 Version table: *** 2.4.1op1-1ubuntu4.7 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 2.4.1op1-1ubuntu4 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What you expected to happen: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# 4) What happened instead: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2052925/+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 2052925] [NEW] lpoptions -d as root
Public bug reported: Copied from https://github.com/OpenPrinting/cups/issues/454 Yair Yarom submitted Debian bug 1008053 and observed that running lpoptions as root does not update /etc/cups/lpoptions but /root/.cups/lpoptions. Running lpoptions as root (e.g. "lpoptions -d HP-OfficeJet") should update /etc/cups/lpoptions to be the defaults for all users. But instead it tries to update /root/.cups/lpoptions. This has been fixed upstream in cups, in debian sid, and mantic. Proposing to add this change in jammy and older (still supported) series as well. The fix is a one line change in https://github.com/OpenPrinting/cups/pull/456 Thanks. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu ubuntu@jammy-vm:~$ lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ubuntu@jammy-vm:~$ apt-cache policy cups cups: Installed: 2.4.1op1-1ubuntu4.7 Candidate: 2.4.1op1-1ubuntu4.7 Version table: *** 2.4.1op1-1ubuntu4.7 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 2.4.1op1-1ubuntu4 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What you expected to happen: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# 4) What happened instead: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# ** Affects: cups (Ubuntu) Importance: Low Status: Fix Released ** Tags: udeng-2281 ** Attachment added: "strace of `lpoptions -d` as root" https://bugs.launchpad.net/bugs/2052925/+attachment/5745886/+files/strace.txt ** Description changed: Copied from https://github.com/OpenPrinting/cups/issues/454 - Yair Yarom submitted Debian bug #1008053 and observed that running + Yair Yarom submitted Debian bug 1008053 and observed that running lpoptions as root does not update /etc/cups/lpoptions but /root/.cups/lpoptions. - - Running lpoptions as root (e.g. "lpoptions -d HP-OfficeJet") should update /etc/cups/lpoptions to be the defaults for all users. But instead it tries to update /root/.cups/lpoptions. + Running lpoptions as root (e.g. "lpoptions -d HP-OfficeJet") should + update /etc/cups/lpoptions to be the defaults for all users. But instead + it tries to update /root/.cups/lpoptions. This has been fixed upstream in cups, in debian sid, and mantic. Proposing to add this change in jammy and older (still supported) series as well. The fix is a one line change in https://github.com/OpenPrinting/cups/pull/456 - Thanks. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu ubuntu@jammy-vm:~$ lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ubuntu@jammy-vm:~$ apt-cache policy cu
[Desktop-packages] [Bug 1853784] Re: Format button has no effect when I right click a USB and select Format
Still happening on 22.04 - right click USB drive -> Format... does nothing. Please fix old bugs which are around for years, before introducing cool new cloud features. Especially when the features are very basic, like formatting a USB drive -- 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/1853784 Title: Format button has no effect when I right click a USB and select Format Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Triaged Bug description: Whenever I boot up ubuntu and attempt to format a plugged-in or mounted USB, the Format button has no effect when clicked on; not even an error message. If there is an error, Ubuntu should let me know or not allow me to format by disabling to format option. Steps to Reproduce: 1. Boot up Ubuntu on the hard disk with a live-usb of ubuntu plugged in (this will be the USB to attempt to format) 2. Log in and open Files 3. Right-click the USB and select "Format" Expected Results: Either the Format menu appears, an error message appears if I am unable to format the disk, or the Format button is disabled. Actual Results: Files allows the format button to be clicked, but nothing happens when it is clicked on. Description: Ubuntu 19.10 Release: 19.10 nautilus: Installed: 1:3.34.1-1ubuntu1 Candidate: 1:3.34.1-1ubuntu1 Version table: *** 1:3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 24 17:22:27 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'260' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2019-11-20 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-24T17:17:29.098099 usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1853784/+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 2035310] Re: gnome-session-binary crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
Gnome-session crashed after boot up. Every time I start session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2035310 Title: gnome-session-binary crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() Status in gnome-session package in Ubuntu: Invalid Bug description: Just started, no apps active ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-session-bin 44.0-4ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 13 08:02:26 2023 ExecutablePath: /usr/libexec/gnome-session-binary InstallationDate: Installed on 2023-09-08 (5 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230904.2) ProcCmdline: /usr/libexec/gnome-session-binary --systemd-service --session=ubuntu ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7fe746724c41 : mov(%rax),%rax PC (0x7fe746724c41) ok source "(%rax)" (0x7fe0d273ef17) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-session StacktraceTop: g_type_check_instance_is_fundamentally_a () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-session-binary crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2035310/+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
