[Desktop-packages] [Bug 2063150] [NEW] No sound after upgrade to 24.04
Public bug reported: After upgrading from Ubuntu 23.10 to 24.04, it does not work on the computer. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: pipewire 1.0.5-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 15:52:58 2024 InstallationDate: Installed on 2024-03-25 (28 days ago) InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: pipewire UpgradeStatus: Upgraded to noble on 2024-04-21 (1 days ago) ** Affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/2063150 Title: No sound after upgrade to 24.04 Status in pipewire package in Ubuntu: New Bug description: After upgrading from Ubuntu 23.10 to 24.04, it does not work on the computer. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: pipewire 1.0.5-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 15:52:58 2024 InstallationDate: Installed on 2024-03-25 (28 days ago) InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: pipewire UpgradeStatus: Upgraded to noble on 2024-04-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2063150/+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 1897754] Re: The icon does not appear in the GNOME bar
** Description changed: + https://github.com/flameshot-org/flameshot/issues/1009 + + --- + When upgrading from gnome-shell-extension-appindicator_33-3_all.deb to gnome-shell-extension-appindicator_34-1_all.deb the icon does not appear in the GNOME toolbar. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: flameshot 0.8.1-1 Uname: Linux 5.8.12-050812-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 29 11:55:57 2020 InstallationDate: Installed on 2020-06-19 (102 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609) SourcePackage: flameshot UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1897754 Title: The icon does not appear in the GNOME bar Status in flameshot package in Ubuntu: New Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: https://github.com/flameshot-org/flameshot/issues/1009 --- When upgrading from gnome-shell-extension-appindicator_33-3_all.deb to gnome-shell-extension-appindicator_34-1_all.deb the icon does not appear in the GNOME toolbar. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: flameshot 0.8.1-1 Uname: Linux 5.8.12-050812-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 29 11:55:57 2020 InstallationDate: Installed on 2020-06-19 (102 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609) SourcePackage: flameshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1897754/+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 1897754] [NEW] The icon does not appear in the GNOME bar
Public bug reported: When upgrading from gnome-shell-extension-appindicator_33-3_all.deb to gnome-shell-extension-appindicator_34-1_all.deb the icon does not appear in the GNOME toolbar. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: flameshot 0.8.1-1 Uname: Linux 5.8.12-050812-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 29 11:55:57 2020 InstallationDate: Installed on 2020-06-19 (102 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609) SourcePackage: flameshot UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: flameshot (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Also affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1897754 Title: The icon does not appear in the GNOME bar Status in flameshot package in Ubuntu: New Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: When upgrading from gnome-shell-extension-appindicator_33-3_all.deb to gnome-shell-extension-appindicator_34-1_all.deb the icon does not appear in the GNOME toolbar. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: flameshot 0.8.1-1 Uname: Linux 5.8.12-050812-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 29 11:55:57 2020 InstallationDate: Installed on 2020-06-19 (102 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609) SourcePackage: flameshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1897754/+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 1702151] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets()
** Tags added: groovy -- 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/1702151 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets() Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: In Progress Bug description: https://errors.ubuntu.com/problem/ada10af9bce533d2cce9447f055123b325fd6c1d https://errors.ubuntu.com/problem/7db21198c9a21745b60cc46aabafb2b7e636bf95 --- Todays update had a kernal and my gnome shell update. Happened when I rebooted. I now have a black screen and no panel. Icons are all that shows up on desktop. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu7 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 3 12:46:31 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: gnome-shell --sm-client-id 102c52716a25d9b2dd1495780366603150001329 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f9bec254d5c : movzbl 0x14(%rax),%edx PC (0x7f9bec254d5c) ok source "0x14(%rax)" (0x20706f746b736558) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_theme_get_custom_stylesheets () from /usr/lib/gnome-shell/libgnome-shell.so ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: gnome-shell 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 sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1702151/+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 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no screens found") from dix_main()
** Tags added: groovy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1543192
Title:
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("no screens found") from dix_main()
Status in xorg-server package in Ubuntu:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530
https://errors.ubuntu.com/problem/4c203db78dea0a68c29cbd981d4abbd4aef31851
---
No idea what happened.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core 2:1.17.3-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CrashCounter: 1
Date: Mon Feb 8 17:07:23 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics
Controller [17aa:21da]
InstallationDate: Installed on 2015-04-30 (283 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 429149G
ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic
root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0
panic=-1
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
OsAbort ()
?? ()
FatalError ()
?? ()
__libc_start_main (main=0x557f8180ff00, argc=11, argv=0x7fffc9e34fd8,
init=, fini=, rtld_fini=,
stack_end=0x7fffc9e34fc8) at libc-start.c:289
SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit
code 2:
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/18/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET46WW (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 429149G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 429149G
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.66-2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20160127-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
xserver.bootTime: Mon Feb 8 17:08:14 2016
xserver.configfile: default
xserver.errors: systemd-logind: failed to get session: PID 9847 does not
belong to any known session
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 728
vendor LGD
xserver.version: 2:1.17.3-2ubuntu2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192/+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 1880742] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance()
https://gitlab.gnome.org/GNOME/mutter/-/issues/1274 ** Description changed: - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2840 + https://gitlab.gnome.org/GNOME/mutter/-/issues/1274 --- I was working with nautilus, I hit a 'recent' click. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.2-1ubuntu1 Uname: Linux 5.7.0-050700rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 13:55:31 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (541 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 () () at /lib/x86_64-linux-gnu/libc.so.6 g_type_check_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_connect_data () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom chrome-remote-desktop dip lpadmin plugdev sambashare sudo separator: ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1274 https://gitlab.gnome.org/GNOME/mutter/-/issues/1274 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1274 Importance: Unknown Status: Unknown -- 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/1880742 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance() Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/mutter/-/issues/1274 --- I was working with nautilus, I hit a 'recent' click. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.2-1ubuntu1 Uname: Linux 5.7.0-050700rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 13:55:31 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (541 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 () () at /lib/x86_64-linux-gnu/libc.so.6 g_type_check_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_connect_data () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom chrome-remote-desktop dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1880742/+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 1880742] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance()
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1880742 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance() Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2840 --- I was working with nautilus, I hit a 'recent' click. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.2-1ubuntu1 Uname: Linux 5.7.0-050700rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 13:55:31 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (541 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 () () at /lib/x86_64-linux-gnu/libc.so.6 g_type_check_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_connect_data () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom chrome-remote-desktop dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880742/+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 1880742] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance()
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2840 ** Description changed: + https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2840 + + --- + I was working with nautilus, I hit a 'recent' click. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.2-1ubuntu1 Uname: Linux 5.7.0-050700rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 13:55:31 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (541 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: - LANG=es_CL.UTF-8 - LANGUAGE=es_CL:es - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=es_CL.UTF-8 + LANGUAGE=es_CL:es + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: - __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 - () - () at /lib/x86_64-linux-gnu/libc.so.6 - g_type_check_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_signal_connect_data () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 + () + () at /lib/x86_64-linux-gnu/libc.so.6 + g_type_check_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_signal_connect_data () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom chrome-remote-desktop dip lpadmin plugdev sambashare sudo separator: ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2840 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2840 -- 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/1880742 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance() Status in gnome-shell package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2840 --- I was working with nautilus, I hit a 'recent' click. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.2-1ubuntu1 Uname: Linux 5.7.0-050700rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 13:55:31 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (541 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 () () at /lib/x86_64-linux-gnu/libc.so.6 g_type_check_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_connect_data () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom chrome-remote-desktop dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880742/+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 1880742] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1880742 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance() Status in gnome-shell package in Ubuntu: New Bug description: I was working with nautilus, I hit a 'recent' click. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.2-1ubuntu1 Uname: Linux 5.7.0-050700rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 13:55:31 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (541 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 () () at /lib/x86_64-linux-gnu/libc.so.6 g_type_check_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_connect_data () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom chrome-remote-desktop dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880742/+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 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()
** Tags added: groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1865300 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback() Status in GNOME Shell: Unknown Status in glib2.0 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9 --- Happened during normal use of the desktop. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 29 19:51:58 2020 DisplayManager: gdm3 ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer InstallationDate: Installed on 2020-01-25 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax PC (0x7f5f54fa6444) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1865300/+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 1746656] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_display@1: error 1: invalid arguments for
** Tags added: groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1746656 Title: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_display@1: error 1: invalid arguments for zwp_relative_pointer_manager_v1@15.get_relative_pointer\n"] Status in xorg-server package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.19.5-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/919f7b6d37f2b2e23bf18d4cc9fad6a6116edf82 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1746656/+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 1867480] Re: scp-dbus-service.py crashed with SIGSEGV in _PyObject_GC_UNTRACK_impl()
** Tags added: groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1867480 Title: scp-dbus-service.py crashed with SIGSEGV in _PyObject_GC_UNTRACK_impl() Status in System Config Printer: New Status in system-config-printer package in Ubuntu: Confirmed Bug description: not sure what it is I just saw there was n bug - I am new to Linux ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: system-config-printer-common 1.5.12-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Mar 15 02:22:17 2020 ExecutablePath: /usr/share/system-config-printer/scp-dbus-service.py InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200312) InterpreterPath: /usr/bin/python3.8 Lpstat: device for L365: dnssd://EPSON%20L365%20Series._pdl-datastream._tcp.local/ MachineType: Universal Exports Group Limited ITL 1403-I3 128 PackageArchitecture: all Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/L365.ppd'] failed with exit code 2: grep: /etc/cups/ppd/L365.ppd: Permission denied ProcCmdline: /usr/bin/python3 /usr/share/system-config-printer/scp-dbus-service.py ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=464449a8-03b3-4536-9504-744640ef4b27 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonDetails: N/A SegvAnalysis: Segfault happened at: 0x506f57: mov%rcx,(%rdx) PC (0x00506f57) ok source "%rcx" ok destination "(%rdx)" (0x0004) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: system-config-printer StacktraceTop: ?? () ?? () from /usr/lib/python3/dist-packages/cups.cpython-38-x86_64-linux-gnu.so __nptl_deallocate_tsd () at pthread_create.c:301 __nptl_deallocate_tsd () at pthread_create.c:256 start_thread (arg=) at pthread_create.c:488 Title: scp-dbus-service.py crashed with SIGSEGV in __nptl_deallocate_tsd() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 04/29/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 0429 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Default dmi.board.vendor: Default dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr0429:bd04/29/2019:svnUniversalExportsGroupLimited:pnITL1403-I3128:pvrTBDbyOEM:rvnDefault:rnDefault:rvrType2-BoardVersion:cvnChassisManufacture:ct10:cvrChassisVersion: dmi.product.family: Notepad dmi.product.name: ITL 1403-I3 128 dmi.product.sku: ITL 1403-I3 128 dmi.product.version: TBD by OEM dmi.sys.vendor: Universal Exports Group Limited separator: To manage notifications about this bug go to: https://bugs.launchpad.net/system-config-printer/+bug/1867480/+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 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
** Tags added: groovy -- 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/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path Status in Nautilus: New Status in gtk+3.0 package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/gtk/issues/2457 --- https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1726129/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820859] Re: /usr/bin/nautilus:11:g_application_impl_get_dbus_object_path:g_application_get_dbus_object_path:update_dbus_opened_locations:bus_acquired_cb:connection_get_cb
** Tags added: groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1820859 Title: /usr/bin/nautilus:11:g_application_impl_get_dbus_object_path:g_application_get_dbus_object_path:update_dbus_opened_locations:bus_acquired_cb:connection_get_cb Status in nautilus package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.31.90-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/8a8c9fc62039a8bb83a7ee530ac4140a9b8c29d9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874262] Re: User session does not start: Problem with chrome-remote-desktop
** Summary changed: - User session does not start: xkbcomp "Internal error: Could not resolve keysym Invalid" + User session does not start: Problem with chrome-remote-desktop -- 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/1874262 Title: User session does not start: Problem with chrome-remote-desktop Status in gdm3 package in Ubuntu: Invalid Status in xorg package in Ubuntu: New Bug description: https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues/14 https://gitlab.gnome.org/GNOME/gdm/-/issues/593 --- Today I tried to log into my ubuntu session with my personal account through Xorg and Xwayland. And I couldn't, I had to install lightdm and to be able to enter. In my experience, I found this message ($journalctl): Apr 22 09:06:44 romanescu gnome-shell [3651]: The XKEYBOARD keymap compiler (xkbcomp) reports: Apr 22 09:06:44 romanescu gnome-shell [3651]:> Warning: Unsupported maximum keycode 569, clipping. Apr 22 09:06:44 romanescu gnome-shell [3651]:> X11 cannot support keycodes above 255. Apr 22 09:06:44 romanescu gnome-shell [3651]:> Internal error: Could not resolve keysym Invalid Apr 22 09:06:44 romanescu gnome-shell [3651]: Errors from xkbcomp are not fatal to the X server Attached log of the attempt to log in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 Uname: Linux 5.6.6-050606-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 09:54:26 2020 InstallationDate: Installed on 2018-12-02 (506 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1874262/+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 1874262] Re: User session does not start: xkbcomp "Internal error: Could not resolve keysym Invalid"
https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues/14 ** Also affects: xorg (Ubuntu) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu) Status: New => Invalid ** Description changed: + https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues/14 https://gitlab.gnome.org/GNOME/gdm/-/issues/593 --- Today I tried to log into my ubuntu session with my personal account through Xorg and Xwayland. And I couldn't, I had to install lightdm and to be able to enter. In my experience, I found this message ($journalctl): Apr 22 09:06:44 romanescu gnome-shell [3651]: The XKEYBOARD keymap compiler (xkbcomp) reports: Apr 22 09:06:44 romanescu gnome-shell [3651]:> Warning: Unsupported maximum keycode 569, clipping. Apr 22 09:06:44 romanescu gnome-shell [3651]:> X11 cannot support keycodes above 255. Apr 22 09:06:44 romanescu gnome-shell [3651]:> Internal error: Could not resolve keysym Invalid Apr 22 09:06:44 romanescu gnome-shell [3651]: Errors from xkbcomp are not fatal to the X server Attached log of the attempt to log in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 Uname: Linux 5.6.6-050606-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 09:54:26 2020 InstallationDate: Installed on 2018-12-02 (506 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Bug watch added: gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues #14 https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues/14 -- 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/1874262 Title: User session does not start: xkbcomp "Internal error: Could not resolve keysym Invalid" Status in gdm3 package in Ubuntu: Invalid Status in xorg package in Ubuntu: New Bug description: https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues/14 https://gitlab.gnome.org/GNOME/gdm/-/issues/593 --- Today I tried to log into my ubuntu session with my personal account through Xorg and Xwayland. And I couldn't, I had to install lightdm and to be able to enter. In my experience, I found this message ($journalctl): Apr 22 09:06:44 romanescu gnome-shell [3651]: The XKEYBOARD keymap compiler (xkbcomp) reports: Apr 22 09:06:44 romanescu gnome-shell [3651]:> Warning: Unsupported maximum keycode 569, clipping. Apr 22 09:06:44 romanescu gnome-shell [3651]:> X11 cannot support keycodes above 255. Apr 22 09:06:44 romanescu gnome-shell [3651]:> Internal error: Could not resolve keysym Invalid Apr 22 09:06:44 romanescu gnome-shell [3651]: Errors from xkbcomp are not fatal to the X server Attached log of the attempt to log in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 Uname: Linux 5.6.6-050606-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 09:54:26 2020 InstallationDate: Installed on 2018-12-02 (506 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1874262/+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 1874262] [NEW] User session does not start: xkbcomp "Internal error: Could not resolve keysym Invalid"
Public bug reported: https://gitlab.gnome.org/GNOME/gdm/-/issues/593 --- Today I tried to log into my ubuntu session with my personal account through Xorg and Xwayland. And I couldn't, I had to install lightdm and to be able to enter. In my experience, I found this message ($journalctl): Apr 22 09:06:44 romanescu gnome-shell [3651]: The XKEYBOARD keymap compiler (xkbcomp) reports: Apr 22 09:06:44 romanescu gnome-shell [3651]:> Warning: Unsupported maximum keycode 569, clipping. Apr 22 09:06:44 romanescu gnome-shell [3651]:> X11 cannot support keycodes above 255. Apr 22 09:06:44 romanescu gnome-shell [3651]:> Internal error: Could not resolve keysym Invalid Apr 22 09:06:44 romanescu gnome-shell [3651]: Errors from xkbcomp are not fatal to the X server Attached log of the attempt to log in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 Uname: Linux 5.6.6-050606-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 09:54:26 2020 InstallationDate: Installed on 2018-12-02 (506 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "gdm.log" https://bugs.launchpad.net/bugs/1874262/+attachment/5357963/+files/gdm.log ** Summary changed: - User session does not start "Internal error: Could not resolve keysym Invalid" + User session does not start: xkbcomp "Internal error: Could not resolve keysym Invalid" -- 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/1874262 Title: User session does not start: xkbcomp "Internal error: Could not resolve keysym Invalid" Status in gdm3 package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/gdm/-/issues/593 --- Today I tried to log into my ubuntu session with my personal account through Xorg and Xwayland. And I couldn't, I had to install lightdm and to be able to enter. In my experience, I found this message ($journalctl): Apr 22 09:06:44 romanescu gnome-shell [3651]: The XKEYBOARD keymap compiler (xkbcomp) reports: Apr 22 09:06:44 romanescu gnome-shell [3651]:> Warning: Unsupported maximum keycode 569, clipping. Apr 22 09:06:44 romanescu gnome-shell [3651]:> X11 cannot support keycodes above 255. Apr 22 09:06:44 romanescu gnome-shell [3651]:> Internal error: Could not resolve keysym Invalid Apr 22 09:06:44 romanescu gnome-shell [3651]: Errors from xkbcomp are not fatal to the X server Attached log of the attempt to log in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 Uname: Linux 5.6.6-050606-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 09:54:26 2020 InstallationDate: Installed on 2018-12-02 (506 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1874262/+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 1873003] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2643 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2643 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2643 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2643 Importance: Unknown Status: Unknown ** Description changed: + https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2643 + + --- + I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 Uname: Linux 5.6.4-050604-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 10:11:16 2020 DisplayManager: gdm3 ExecutablePath: /usr/libexec/gnome-shell-hotplug-sniffer InstallationDate: Installed on 2018-12-02 (499 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/libexec/gnome-shell-hotplug-sniffer ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANGUAGE=es_CL:es - LANG=es_CL.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANGUAGE=es_CL:es + LANG=es_CL.UTF-8 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SegvAnalysis: - Segfault happened at: 0x7f89b635e494 : movsbl (%rdi),%eax - PC (0x7f89b635e494) ok - source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! - destination "%eax" ok + Segfault happened at: 0x7f89b635e494 : movsbl (%rdi),%eax + PC (0x7f89b635e494) ok + source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! + destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: - g_str_hash () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_hash_table_lookup () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - () - () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 - () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 + g_str_hash () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_hash_table_lookup () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + () + () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 + () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() UpgradeStatus: Upgraded to focal on 2018-12-02 (499 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- 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/1873003 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2643 --- I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 Uname: Linux 5.6.4-050604-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 10:11:16 2020 DisplayManager: gdm3 ExecutablePath: /usr/libexec/gnome-shell-hotplug-sniffer InstallationDate: Installed on 2018-12-02 (499 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/libexec/gnome-shell-hotplug-sniffer ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SegvAnalysis: Segfault happened at: 0x7f89b635e494 : movsbl (%rdi),%eax PC (0x7f89b635e494) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() UpgradeStatus: Upgraded to focal on 2018-12-02 (499 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1873003/+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 1873003] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1873003 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() Status in gnome-shell package in Ubuntu: New Bug description: I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 Uname: Linux 5.6.4-050604-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 10:11:16 2020 DisplayManager: gdm3 ExecutablePath: /usr/libexec/gnome-shell-hotplug-sniffer InstallationDate: Installed on 2018-12-02 (499 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/libexec/gnome-shell-hotplug-sniffer ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SegvAnalysis: Segfault happened at: 0x7f89b635e494 : movsbl (%rdi),%eax PC (0x7f89b635e494) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() UpgradeStatus: Upgraded to focal on 2018-12-02 (499 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873003/+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 1871489] Re: xdg-desktop-portal-gtk crashed with SIGSEGV
https://github.com/flatpak/xdg-desktop-portal-gtk/issues/298 ** Description changed: + https://github.com/flatpak/xdg-desktop-portal-gtk/issues/298 + + --- + I think it happened like this: 1. I opened bijiben 2. I clicked on a note that was already created 3. In the note there was a web link 4. I clicked with the right mouse button on 'Open link' in the web link 5. The web link was opened in the web browser (chrome) 6. After all this, it seems that it hung: 'xdg-desktop-portal-gtk' ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xdg-desktop-portal-gtk 1.6.0-1build1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 7 15:32:08 2020 ExecutablePath: /usr/libexec/xdg-desktop-portal-gtk ExecutableTimestamp: 1582584543 InstallationDate: Installed on 2018-12-02 (492 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/libexec/xdg-desktop-portal-gtk ProcCwd: /home/caravena ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: xdg-desktop-portal-gtk StacktraceTop: () g_cclosure_marshal_VOID__BOOLEANv () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 UpgradeStatus: Upgraded to focal on 2018-12-02 (491 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Bug watch added: github.com/flatpak/xdg-desktop-portal-gtk/issues #298 https://github.com/flatpak/xdg-desktop-portal-gtk/issues/298 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1871489 Title: xdg-desktop-portal-gtk crashed with SIGSEGV Status in xdg-desktop-portal-gtk package in Ubuntu: New Bug description: https://github.com/flatpak/xdg-desktop-portal-gtk/issues/298 --- I think it happened like this: 1. I opened bijiben 2. I clicked on a note that was already created 3. In the note there was a web link 4. I clicked with the right mouse button on 'Open link' in the web link 5. The web link was opened in the web browser (chrome) 6. After all this, it seems that it hung: 'xdg-desktop-portal-gtk' ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xdg-desktop-portal-gtk 1.6.0-1build1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 7 15:32:08 2020 ExecutablePath: /usr/libexec/xdg-desktop-portal-gtk ExecutableTimestamp: 1582584543 InstallationDate: Installed on 2018-12-02 (492 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/libexec/xdg-desktop-portal-gtk ProcCwd: /home/caravena ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: xdg-desktop-portal-gtk StacktraceTop: () g_cclosure_marshal_VOID__BOOLEANv () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 UpgradeStatus: Upgraded to focal on 2018-12-02 (491 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1871489/+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 1871489] Re: xdg-desktop-portal-gtk crashed with SIGSEGV
Is there a relationship? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1871489 Title: xdg-desktop-portal-gtk crashed with SIGSEGV Status in xdg-desktop-portal-gtk package in Ubuntu: Incomplete Bug description: I think it happened like this: 1. I opened bijiben 2. I clicked on a note that was already created 3. In the note there was a web link 4. I clicked with the right mouse button on 'Open link' in the web link 5. The web link was opened in the web browser (chrome) 6. After all this, it seems that it hung: 'xdg-desktop-portal-gtk' ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xdg-desktop-portal-gtk 1.6.0-1build1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 7 15:32:08 2020 ExecutablePath: /usr/libexec/xdg-desktop-portal-gtk ExecutableTimestamp: 1582584543 InstallationDate: Installed on 2018-12-02 (492 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/libexec/xdg-desktop-portal-gtk ProcCwd: /home/caravena ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: xdg-desktop-portal-gtk StacktraceTop: () g_cclosure_marshal_VOID__BOOLEANv () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 UpgradeStatus: Upgraded to focal on 2018-12-02 (491 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1871489/+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 1871489] Re: xdg-desktop-portal-gtk crashed with SIGSEGV
Sebastien, I updated the description of the report ... Could it be because of this? ** Description changed: - I don't know what happened. + I think it happened like this: + 1. I opened bijiben + 2. I clicked on a note that was already created + 3. In the note there was a web link + 4. I clicked with the right mouse button on 'Open link' in the web link + 5. The web link was opened in the web browser (chrome) + 6. After all this, it seems that it hung: 'xdg-desktop-portal-gtk' ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xdg-desktop-portal-gtk 1.6.0-1build1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 7 15:32:08 2020 ExecutablePath: /usr/libexec/xdg-desktop-portal-gtk ExecutableTimestamp: 1582584543 InstallationDate: Installed on 2018-12-02 (492 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/libexec/xdg-desktop-portal-gtk ProcCwd: /home/caravena ProcEnviron: - LANG=es_CL.UTF-8 - LANGUAGE=es_CL:es - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=es_CL.UTF-8 + LANGUAGE=es_CL:es + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: xdg-desktop-portal-gtk StacktraceTop: - () - g_cclosure_marshal_VOID__BOOLEANv () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + () + g_cclosure_marshal_VOID__BOOLEANv () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 UpgradeStatus: Upgraded to focal on 2018-12-02 (491 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1871489 Title: xdg-desktop-portal-gtk crashed with SIGSEGV Status in xdg-desktop-portal-gtk package in Ubuntu: Incomplete Bug description: I think it happened like this: 1. I opened bijiben 2. I clicked on a note that was already created 3. In the note there was a web link 4. I clicked with the right mouse button on 'Open link' in the web link 5. The web link was opened in the web browser (chrome) 6. After all this, it seems that it hung: 'xdg-desktop-portal-gtk' ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xdg-desktop-portal-gtk 1.6.0-1build1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 7 15:32:08 2020 ExecutablePath: /usr/libexec/xdg-desktop-portal-gtk ExecutableTimestamp: 1582584543 InstallationDate: Installed on 2018-12-02 (492 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/libexec/xdg-desktop-portal-gtk ProcCwd: /home/caravena ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: xdg-desktop-portal-gtk StacktraceTop: () g_cclosure_marshal_VOID__BOOLEANv () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 UpgradeStatus: Upgraded to focal on 2018-12-02 (491 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1871489/+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 1869876] Re: totem crashed with SIGSEGV in g_mount_spec_get()
*** This bug is a duplicate of bug 1860235 *** https://bugs.launchpad.net/bugs/1860235 ** This bug has been marked a duplicate of bug 1860235 totem crashed with SIGSEGV in g_mount_spec_get() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1869876 Title: totem crashed with SIGSEGV in g_mount_spec_get() Status in Totem: Unknown Status in totem package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/totem/-/issues/411 --- I don't know how it happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu2 Uname: Linux 5.6.0-050600-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 19:29:08 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (484 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7f981803dd09 : mov (%rbx),%rdi PC (0x7f981803dd09) ok source "(%rbx)" (0x7000700070006) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: totem StacktraceTop: g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 totem_pl_parser_parse_with_base () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 Title: totem crashed with SIGSEGV in g_mount_spec_get() UpgradeStatus: Upgraded to focal on 2018-12-02 (484 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1869876/+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 1869876] Re: totem crashed with SIGSEGV in g_mount_spec_get()
https://gitlab.gnome.org/GNOME/totem/-/issues/411 ** Information type changed from Private to Public ** Bug watch added: gitlab.gnome.org/GNOME/totem/-/issues #411 https://gitlab.gnome.org/GNOME/totem/-/issues/411 ** Also affects: totem via https://gitlab.gnome.org/GNOME/totem/-/issues/411 Importance: Unknown Status: Unknown ** Description changed: + https://gitlab.gnome.org/GNOME/totem/-/issues/411 + + --- + I don't know how it happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu2 Uname: Linux 5.6.0-050600-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 19:29:08 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (484 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANGUAGE=es_CL:es - LANG=es_CL.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANGUAGE=es_CL:es + LANG=es_CL.UTF-8 SegvAnalysis: - Segfault happened at: 0x7f981803dd09 : mov (%rbx),%rdi - PC (0x7f981803dd09) ok - source "(%rbx)" (0x7000700070006) not located in a known VMA region (needed readable region)! - destination "%rdi" ok - Stack memory exhausted (SP below stack segment) + Segfault happened at: 0x7f981803dd09 : mov (%rbx),%rdi + PC (0x7f981803dd09) ok + source "(%rbx)" (0x7000700070006) not located in a known VMA region (needed readable region)! + destination "%rdi" ok + Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: totem StacktraceTop: - g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so - () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so - () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so - () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 - totem_pl_parser_parse_with_base () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 + g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so + () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so + () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so + () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 + totem_pl_parser_parse_with_base () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 Title: totem crashed with SIGSEGV in g_mount_spec_get() UpgradeStatus: Upgraded to focal on 2018-12-02 (484 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1869876 Title: totem crashed with SIGSEGV in g_mount_spec_get() Status in Totem: Unknown Status in totem package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/totem/-/issues/411 --- I don't know how it happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu2 Uname: Linux 5.6.0-050600-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 19:29:08 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (484 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7f981803dd09 : mov (%rbx),%rdi PC (0x7f981803dd09) ok source "(%rbx)" (0x7000700070006) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: totem StacktraceTop: g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 totem_pl_parser_parse_with_base () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 Title: totem crashed with SIGSEGV in g_mount_spec_get() UpgradeStatus: Upgraded to focal on 2018-12-02 (484 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1869876/+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 1869404] Re: nautilus crashed with SIGABRT
** Description changed: https://gitlab.gnome.org/GNOME/nautilus/-/issues/1426 --- - I was working with: NAS(samba) + nautilus + nautilus search bar in - folder of NAS. + I was working with: NAS(samba) + nautilus search bar in folder of NAS. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.0-1ubuntu1 Uname: Linux 5.6.0-050600rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 27 14:35:37 2020 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-12-02 (480 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () nautilus_window_slot_open_location_full () () at /usr/lib/x86_64-linux-gnu/libffi.so.7 Title: nautilus crashed with SIGABRT UpgradeStatus: Upgraded to focal on 2018-12-02 (480 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: -- 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/1869404 Title: nautilus crashed with SIGABRT Status in Nautilus: Unknown Status in nautilus package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/nautilus/-/issues/1426 --- I was working with: NAS(samba) + nautilus search bar in folder of NAS. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.0-1ubuntu1 Uname: Linux 5.6.0-050600rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 27 14:35:37 2020 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-12-02 (480 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () nautilus_window_slot_open_location_full () () at /usr/lib/x86_64-linux-gnu/libffi.so.7 Title: nautilus crashed with SIGABRT UpgradeStatus: Upgraded to focal on 2018-12-02 (480 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1869404/+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 1869404] Re: nautilus crashed with SIGABRT
https://gitlab.gnome.org/GNOME/nautilus/-/issues/1426 ** Information type changed from Private to Public ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1426 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1426 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/1426 Importance: Unknown Status: Unknown ** Description changed: + https://gitlab.gnome.org/GNOME/nautilus/-/issues/1426 + + --- + I was working with: NAS(samba) + nautilus + nautilus search bar in folder of NAS. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.0-1ubuntu1 Uname: Linux 5.6.0-050600rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 27 14:35:37 2020 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-12-02 (480 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () nautilus_window_slot_open_location_full () () at /usr/lib/x86_64-linux-gnu/libffi.so.7 Title: nautilus crashed with SIGABRT UpgradeStatus: Upgraded to focal on 2018-12-02 (480 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: -- 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/1869404 Title: nautilus crashed with SIGABRT Status in Nautilus: Unknown Status in nautilus package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/nautilus/-/issues/1426 --- I was working with: NAS(samba) + nautilus search bar in folder of NAS. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.0-1ubuntu1 Uname: Linux 5.6.0-050600rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 27 14:35:37 2020 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-12-02 (480 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () nautilus_window_slot_open_location_full () () at /usr/lib/x86_64-linux-gnu/libffi.so.7 Title: nautilus crashed with SIGABRT UpgradeStatus: Upgraded to focal on 2018-12-02 (480 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1869404/+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 1868999] Re: Characters in the web browser do not work
@Olivier, This morning it happened again. I had to restart three times. -- 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/1868999 Title: Characters in the web browser do not work Status in firefox package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Bug description: I updated my ubuntu 20.04 (03-25-2020) and I can't write in Firefox or Chrome. In all other GNOME applications it works fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 74.0+build3-0ubuntu1 Uname: Linux 5.4.27-050427-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1725 F pulseaudio BuildID: 20200309095159 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 10:03:04 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-12-02 (478 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.0.1 dev enx000ec6c82c3f proto dhcp metric 100 169.254.0.0/16 dev enx000ec6c82c3f scope link metric 1000 192.168.0.0/24 dev enx000ec6c82c3f proto kernel scope link src 192.168.0.101 metric 100 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:729 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=74.0/20200309095159 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2018-12-02 (478 days ago) dmi.bios.date: 11/18/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.35:bd11/18/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1868999/+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 1868999] Re: Characters in the web browser do not work
** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- 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/1868999 Title: Characters in the web browser do not work Status in firefox package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Bug description: I updated my ubuntu 20.04 (03-25-2020) and I can't write in Firefox or Chrome. In all other GNOME applications it works fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 74.0+build3-0ubuntu1 Uname: Linux 5.4.27-050427-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1725 F pulseaudio BuildID: 20200309095159 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 10:03:04 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-12-02 (478 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.0.1 dev enx000ec6c82c3f proto dhcp metric 100 169.254.0.0/16 dev enx000ec6c82c3f scope link metric 1000 192.168.0.0/24 dev enx000ec6c82c3f proto kernel scope link src 192.168.0.101 metric 100 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:729 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=74.0/20200309095159 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2018-12-02 (478 days ago) dmi.bios.date: 11/18/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.35:bd11/18/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1868999/+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 1868999] Re: Characters in the web browser do not work
How strange, I just rebooted and selected my 5.6.0-050600rc7-generic and tried Xorg and Xwayland and everything works fine 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/1868999 Title: Characters in the web browser do not work Status in firefox package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Bug description: I updated my ubuntu 20.04 (03-25-2020) and I can't write in Firefox or Chrome. In all other GNOME applications it works fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 74.0+build3-0ubuntu1 Uname: Linux 5.4.27-050427-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1725 F pulseaudio BuildID: 20200309095159 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 10:03:04 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-12-02 (478 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.0.1 dev enx000ec6c82c3f proto dhcp metric 100 169.254.0.0/16 dev enx000ec6c82c3f scope link metric 1000 192.168.0.0/24 dev enx000ec6c82c3f proto kernel scope link src 192.168.0.101 metric 100 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:729 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=74.0/20200309095159 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2018-12-02 (478 days ago) dmi.bios.date: 11/18/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.35:bd11/18/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1868999/+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 1868999] Re: Characters in the web browser do not work
Good morning, I just rebooted with the kernel: 5.4.0-18-generic And everything works perfectly. -- 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/1868999 Title: Characters in the web browser do not work Status in firefox package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: New Bug description: I updated my ubuntu 20.04 (03-25-2020) and I can't write in Firefox or Chrome. In all other GNOME applications it works fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 74.0+build3-0ubuntu1 Uname: Linux 5.4.27-050427-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1725 F pulseaudio BuildID: 20200309095159 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 10:03:04 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-12-02 (478 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.0.1 dev enx000ec6c82c3f proto dhcp metric 100 169.254.0.0/16 dev enx000ec6c82c3f scope link metric 1000 192.168.0.0/24 dev enx000ec6c82c3f proto kernel scope link src 192.168.0.101 metric 100 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:729 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=74.0/20200309095159 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2018-12-02 (478 days ago) dmi.bios.date: 11/18/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.35:bd11/18/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1868999/+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 1868999] Re: Characters in the web browser do not work
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1868999 Title: Characters in the web browser do not work Status in firefox package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: I updated my ubuntu 20.04 (03-25-2020) and I can't write in Firefox or Chrome. In all other GNOME applications it works fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 74.0+build3-0ubuntu1 Uname: Linux 5.4.27-050427-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1725 F pulseaudio BuildID: 20200309095159 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 10:03:04 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-12-02 (478 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.0.1 dev enx000ec6c82c3f proto dhcp metric 100 169.254.0.0/16 dev enx000ec6c82c3f scope link metric 1000 192.168.0.0/24 dev enx000ec6c82c3f proto kernel scope link src 192.168.0.101 metric 100 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:729 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=74.0/20200309095159 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2018-12-02 (478 days ago) dmi.bios.date: 11/18/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.35:bd11/18/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1868999/+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 1868999] [NEW] Characters in the web browser do not work
Public bug reported: I updated my ubuntu 20.04 (03-25-2020) and I can't write in Firefox or Chrome. In all other GNOME applications it works fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 74.0+build3-0ubuntu1 Uname: Linux 5.4.27-050427-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1725 F pulseaudio BuildID: 20200309095159 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 10:03:04 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-12-02 (478 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.0.1 dev enx000ec6c82c3f proto dhcp metric 100 169.254.0.0/16 dev enx000ec6c82c3f scope link metric 1000 192.168.0.0/24 dev enx000ec6c82c3f proto kernel scope link src 192.168.0.101 metric 100 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:729 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=74.0/20200309095159 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2018-12-02 (478 days ago) dmi.bios.date: 11/18/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.35:bd11/18/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Summary changed: - Characters in Spanish in the web browser do not work + Characters in the web browser do not work -- 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/1868999 Title: Characters in the web browser do not work Status in firefox package in Ubuntu: New Bug description: I updated my ubuntu 20.04 (03-25-2020) and I can't write in Firefox or Chrome. In all other GNOME applications it works fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 74.0+build3-0ubuntu1 Uname: Linux 5.4.27-050427-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1725 F pulseaudio BuildID: 20200309095159 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 10:03:04 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-12-02 (478 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.0.1 dev enx000ec6c82c3f proto dhcp metric 100 169.254.0.0/16 dev enx000ec6c82c3f scope link metric 1000 192.168.0.0/24 dev enx000ec6c82c3f proto kernel scope link src 192.168.0.101 metric 100 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:729 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=74.0/20200309095159 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2018-12-02 (478 days ago) dmi.bios.date: 11/18/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.35:bd11/18/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family:
[Desktop-packages] [Bug 1867905] Re: Sound output volume controls not showing in menu
*** This bug is a duplicate of bug 1865169 *** https://bugs.launchpad.net/bugs/1865169 ** This bug has been marked a duplicate of bug 1865169 volume and light not working in Gnome Shell 3.35 -- 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/1867905 Title: Sound output volume controls not showing in menu Status in gnome-shell package in Ubuntu: New Bug description: The volume icon and sound output slider doesn't show up in the top- right menu in Focal Gnome. Also, changing the volume with mouse wheel while on the menu doesn't work anymore. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Mar 18 11:14:46 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-19 (150 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-13 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867905/+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 1866222] Re: GNOME Shell crashed with signal 11
Hello Stéphane Witzmann (swzn), Please: https://wiki.ubuntu.com/DebuggingProgramCrash Thanks! -- 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/1866222 Title: GNOME Shell crashed with signal 11 Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome-shell has crashed twice on me today. Unfortunately there's nothing in /var/crash. There's nothing in the journalctl log prior to the crash that explains it. I've attached a log of everything between when the crash happened and when I logged back in (though I suspect most of it is not relevant). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 13:04:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (201 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-31 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+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 1865144] Re: Characters in Spanish in the web browser do not work correctly
I just updated the package x11-xkb-utils (7.7+4) to 7.7+5, and I have restarted Ubuntu 20.04(development). After this, the character encoding works correctly in Firefox and Chrome. ** Also affects: x11-xkb-utils (Ubuntu) Importance: Undecided Status: New ** Changed in: x11-xkb-utils (Ubuntu) Status: New => Fix Released ** Changed in: firefox (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-xkb-utils in Ubuntu. https://bugs.launchpad.net/bugs/1865144 Title: Characters in Spanish in the web browser do not work correctly Status in firefox package in Ubuntu: Invalid Status in x11-xkb-utils package in Ubuntu: Fix Released Bug description: I just updated my ubuntu 20.04 (development) (02-28-2020) and I have problems with the Spanish-Latin American features in Firefox and Chrome. On the other hand: gedit, libreoffice works the Spanish characters correctly. I don't think it's a Firefox problem, but that's where the subject occurs. Please derive the error in the corresponding package.. Thank you! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 73.0.1+build1-0ubuntu1 Uname: Linux 5.5.6-050506-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1700 F pulseaudio /dev/snd/pcmC0D0p: caravena 1700 F...m pulseaudio BuildID: 20200217142647 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 09:23:55 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-12-02 (452 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 10.20.125.1 dev wlx98ded0105daf proto dhcp metric 600 10.20.125.0/24 dev wlx98ded0105daf proto kernel scope link src 10.20.125.168 metric 600 169.254.0.0/16 dev wlx98ded0105daf scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:737 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=73.0.1/20200217142647 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2018-12-02 (452 days ago) dmi.bios.date: 04/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1865144/+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 1865144] Re: Characters in Spanish in the web browser do not work correctly
** Description changed: I just updated my ubuntu 20.04 (development) (02-28-2020) and I have problems with the Spanish-Latin American features in Firefox and Chrome. - On the other hand; gedit, libreoffice works the Spanish characters + On the other hand: gedit, libreoffice works the Spanish characters correctly. I don't think it's a Firefox problem, but that's where the subject occurs. Please derive the error in the corresponding package.. Thank you! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 73.0.1+build1-0ubuntu1 Uname: Linux 5.5.6-050506-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1700 F pulseaudio /dev/snd/pcmC0D0p: caravena 1700 F...m pulseaudio BuildID: 20200217142647 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 09:23:55 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-12-02 (452 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 10.20.125.1 dev wlx98ded0105daf proto dhcp metric 600 10.20.125.0/24 dev wlx98ded0105daf proto kernel scope link src 10.20.125.168 metric 600 169.254.0.0/16 dev wlx98ded0105daf scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:737 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=73.0.1/20200217142647 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2018-12-02 (452 days ago) dmi.bios.date: 04/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP -- 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/1865144 Title: Characters in Spanish in the web browser do not work correctly Status in firefox package in Ubuntu: New Bug description: I just updated my ubuntu 20.04 (development) (02-28-2020) and I have problems with the Spanish-Latin American features in Firefox and Chrome. On the other hand: gedit, libreoffice works the Spanish characters correctly. I don't think it's a Firefox problem, but that's where the subject occurs. Please derive the error in the corresponding package.. Thank you! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 73.0.1+build1-0ubuntu1 Uname: Linux 5.5.6-050506-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1700 F pulseaudio /dev/snd/pcmC0D0p: caravena 1700 F...m pulseaudio BuildID: 20200217142647 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 09:23:55 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-12-02 (452 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 10.20.125.1 dev wlx98ded0105daf proto dhcp metric 600 10.20.125.0/24 dev wlx98ded0105daf proto kernel scope link src 10.20.125.168 metric 600 169.254.0.0/16 dev wlx98ded0105daf scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:737 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=73.0.1/20200217142647 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus:
[Desktop-packages] [Bug 1865144] [NEW] Characters in Spanish in the web browser do not work correctly
Public bug reported: I just updated my ubuntu 20.04 (development) (02-28-2020) and I have problems with the Spanish-Latin American features in Firefox and Chrome. On the other hand; gedit, libreoffice works the Spanish characters correctly. I don't think it's a Firefox problem, but that's where the subject occurs. Please derive the error in the corresponding package.. Thank you! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 73.0.1+build1-0ubuntu1 Uname: Linux 5.5.6-050506-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1700 F pulseaudio /dev/snd/pcmC0D0p: caravena 1700 F...m pulseaudio BuildID: 20200217142647 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 09:23:55 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-12-02 (452 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 10.20.125.1 dev wlx98ded0105daf proto dhcp metric 600 10.20.125.0/24 dev wlx98ded0105daf proto kernel scope link src 10.20.125.168 metric 600 169.254.0.0/16 dev wlx98ded0105daf scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:737 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=73.0.1/20200217142647 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2018-12-02 (452 days ago) dmi.bios.date: 04/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Description changed: I just updated my ubuntu 20.04 (development) (02-28-2020) and I have problems with the Spanish-Latin American features in Firefox and Chrome. On the other hand; gedit, libreoffice works the Spanish characters correctly. I don't think it's a Firefox problem, but that's where the subject - occurs. Please refer the error to the corresponding package. + occurs. Please derive the error in the corresponding package.. Thank you! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 73.0.1+build1-0ubuntu1 Uname: Linux 5.5.6-050506-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: caravena 1700 F pulseaudio - /dev/snd/pcmC0D0p: caravena 1700 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: caravena 1700 F pulseaudio + /dev/snd/pcmC0D0p: caravena 1700 F...m pulseaudio BuildID: 20200217142647 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 09:23:55 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-12-02 (452 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: - default via 10.20.125.1 dev wlx98ded0105daf proto dhcp metric 600 - 10.20.125.0/24 dev wlx98ded0105daf proto kernel scope link src 10.20.125.168 metric 600 - 169.254.0.0/16 dev wlx98ded0105daf scope link metric 1000 + default via 10.20.125.1 dev wlx98ded0105daf proto dhcp metric 600 + 10.20.125.0/24 dev wlx98ded0105daf proto kernel scope link src 10.20.125.168 metric 600 + 169.254.0.0/16 dev wlx98ded0105daf scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:737 PrefSources: prefs.js
[Desktop-packages] [Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
** No longer affects: nautilus ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/gtk/issues/2457 Importance: Unknown Status: Unknown -- 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/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path Status in Nautilus: Unknown Status in gtk+3.0 package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/gtk/issues/2457 --- https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1726129/+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 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
Moved to: https://gitlab.gnome.org/GNOME/gtk/issues/2457 ** Description changed: - https://gitlab.gnome.org/GNOME/nautilus/issues/1190 + https://gitlab.gnome.org/GNOME/gtk/issues/2457 --- https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #2457 https://gitlab.gnome.org/GNOME/gtk/issues/2457 -- 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/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path Status in Nautilus: Fix Released Status in gtk+3.0 package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/gtk/issues/2457 --- https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1726129/+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 1828581] Re: /usr/bin/gnome-calendar:11:gtk_image_reset:gtk_image_clear:update_weather:update_no_events_page:gcal_year_view_component_removed
** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1828581 Title: /usr/bin/gnome- calendar:11:gtk_image_reset:gtk_image_clear:update_weather:update_no_events_page:gcal_year_view_component_removed Status in GNOME Calendar: New Status in gnome-calendar package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-calendar. This problem was most recently seen with package version 3.32.0-1, the problem page at https://errors.ubuntu.com/problem/c13a94eea4826eb85fc9ea3d284eaa906e646c07 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1828581/+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 1826159] Re: gsd-print-notifications assert failure: free(): invalid pointer
** Tags added: focal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1826159
Title:
gsd-print-notifications assert failure: free(): invalid pointer
Status in gnome-settings-daemon package in Ubuntu:
Confirmed
Bug description:
This problem occurs since upgrade to disco dingo. Have not seen this
in earlier releases. It seems to be related to printers in the gnome
settings.
janw-LIFEBOOK-AH532-G21{janw}(79)% lsb_release -rd
Description: Ubuntu 19.04
Release: 19.04
apt-cache policy gnome-settings-daemon
gnome-settings-daemon:
Installerad: 3.32.0-1ubuntu1
Kandidat:3.32.0-1ubuntu1
Versionstabell:
*** 3.32.0-1ubuntu1 500
500 http://se.archive.ubuntu.com/ubuntu disco/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: gnome-settings-daemon 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AssertionMessage: free(): invalid pointer
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 23 22:16:13 2019
ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-print-notifications
InstallationDate: Installed on 2018-02-20 (427 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-print-notifications
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=sv_SE.UTF-8
SHELL=/bin/tcsh
Signal: 6
SourcePackage: gnome-settings-daemon
StacktraceTop:
__libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f247b810952
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
malloc_printerr (str=str@entry=0x7f247b80ea9b "free(): invalid pointer") at
malloc.c:5352
_int_free (av=, p=, have_lock=)
at malloc.c:4181
()
g_list_foreach () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gsd-print-notifications assert failure: free(): invalid pointer
UpgradeStatus: Upgraded to disco on 2019-04-19 (4 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
mtime.conffile..etc.apport.crashdb.conf: 2019-04-24T11:16:47.806271
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1826159/+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 1713581] Re: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
** Tags added: focal -- 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/1713581 Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Bionic: Fix Released Bug description: [ Impact ] Nautilus crashes when trying to open a folder selecting a file, when another has already been selected before and the current folder didn't finish loading. [ Test case ] It's not easy to verify this without hacking the code to change the scenario, but an example could be launching quickly: nautilus /usr/bin/true & nautilus /usr/bin/false At the second command nautilus could crash. [ Regression potential ] Calling nautilus with a file argument might not select that file -- Upstream bug: https://gitlab.gnome.org/GNOME/nautilus/issues/295 Upstream MR: https://gitlab.gnome.org/GNOME/nautilus/merge_requests/277 --- https://errors.ubuntu.com/problem/ef1ce30f6325c683b207fd96a3be93eda5384054 Fixed in https://gitlab.gnome.org/GNOME/nautilus/commit/b6691821b86460bf9d4caa6391666ae506a743c5 no idea,sorry ProblemType: CrashDistroRelease: Ubuntu 17.10 Package: nautilus 1:3.25.90-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 29 00:07:44 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-08-09 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170807) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=de_DE.UTF-8 SegvAnalysis: Segfault happened at: 0x7f8b19a60d27 : mov(%rdi),%rdx PC (0x7f8b19a60d27) ok source "(%rdi)" (0x0002) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading NULL VMASignal: 11SourcePackage: nautilus StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_list_copy_deep () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1713581/+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 1860235] Re: totem crashed with SIGSEGV in g_mount_spec_get()
** Description changed: https://errors.ubuntu.com/problem/4ef67c07533ef05b6c12894767e604456aca3ace https://gitlab.gnome.org/GNOME/gvfs/issues/446 --- - I don't know what happened. + This happened to me when I opened nautilus and accessed my NAS through + smb. And press double click on file. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 Uname: Linux 5.4.12-050412-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 19:08:13 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (412 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7ff6dc45dd09 : mov (%rbx),%rdi PC (0x7ff6dc45dd09) ok source "(%rbx)" (0x7000600070007) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: totem StacktraceTop: g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 Title: totem crashed with SIGSEGV in g_mount_spec_get() UpgradeStatus: Upgraded to focal on 2018-12-02 (412 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Description changed: https://errors.ubuntu.com/problem/4ef67c07533ef05b6c12894767e604456aca3ace https://gitlab.gnome.org/GNOME/gvfs/issues/446 --- This happened to me when I opened nautilus and accessed my NAS through - smb. And press double click on file. + smb. And press double click on file and totem crash. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 Uname: Linux 5.4.12-050412-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 19:08:13 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (412 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7ff6dc45dd09 : mov (%rbx),%rdi PC (0x7ff6dc45dd09) ok source "(%rbx)" (0x7000600070007) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: totem StacktraceTop: g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 Title: totem crashed with SIGSEGV in g_mount_spec_get() UpgradeStatus: Upgraded to focal on 2018-12-02 (412 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1860235 Title: totem crashed with SIGSEGV in g_mount_spec_get() Status in gvfs: New Status in gvfs package in Ubuntu: Triaged Status in totem package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/4ef67c07533ef05b6c12894767e604456aca3ace https://gitlab.gnome.org/GNOME/gvfs/issues/446 --- This happened to me when I opened nautilus and accessed my NAS through smb. And press double click on file and totem crash. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 Uname: Linux 5.4.12-050412-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 19:08:13 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (412 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7ff6dc45dd09 : mov (%rbx),%rdi PC (0x7ff6dc45dd09) ok source "(%rbx)" (0x7000600070007) not located in a known VMA region (needed
[Desktop-packages] [Bug 1860235] Re: totem crashed with SIGSEGV in g_mount_spec_get()
Yes, I work with smb on a NAS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1860235 Title: totem crashed with SIGSEGV in g_mount_spec_get() Status in gvfs: New Status in gvfs package in Ubuntu: Triaged Status in totem package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/4ef67c07533ef05b6c12894767e604456aca3ace https://gitlab.gnome.org/GNOME/gvfs/issues/446 --- I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 Uname: Linux 5.4.12-050412-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 19:08:13 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (412 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7ff6dc45dd09 : mov (%rbx),%rdi PC (0x7ff6dc45dd09) ok source "(%rbx)" (0x7000600070007) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: totem StacktraceTop: g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 Title: totem crashed with SIGSEGV in g_mount_spec_get() UpgradeStatus: Upgraded to focal on 2018-12-02 (412 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1860235/+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 1860235] Re: totem crashed with SIGSEGV in g_mount_spec_get()
https://gitlab.gnome.org/GNOME/gvfs/issues/446 ** Also affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Description changed: https://errors.ubuntu.com/problem/4ef67c07533ef05b6c12894767e604456aca3ace - https://gitlab.gnome.org/GNOME/totem/issues/390 + https://gitlab.gnome.org/GNOME/gvfs/issues/446 --- I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 Uname: Linux 5.4.12-050412-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 19:08:13 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (412 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7ff6dc45dd09 : mov (%rbx),%rdi PC (0x7ff6dc45dd09) ok source "(%rbx)" (0x7000600070007) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: totem StacktraceTop: g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 Title: totem crashed with SIGSEGV in g_mount_spec_get() UpgradeStatus: Upgraded to focal on 2018-12-02 (412 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Bug watch added: gitlab.gnome.org/GNOME/gvfs/issues #446 https://gitlab.gnome.org/GNOME/gvfs/issues/446 ** No longer affects: totem ** Also affects: gvfs via https://gitlab.gnome.org/GNOME/gvfs/issues/446 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1860235 Title: totem crashed with SIGSEGV in g_mount_spec_get() Status in gvfs: Unknown Status in gvfs package in Ubuntu: New Status in totem package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/4ef67c07533ef05b6c12894767e604456aca3ace https://gitlab.gnome.org/GNOME/gvfs/issues/446 --- I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 Uname: Linux 5.4.12-050412-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 19:08:13 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (412 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7ff6dc45dd09 : mov (%rbx),%rdi PC (0x7ff6dc45dd09) ok source "(%rbx)" (0x7000600070007) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: totem StacktraceTop: g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 Title: totem crashed with SIGSEGV in g_mount_spec_get() UpgradeStatus: Upgraded to focal on 2018-12-02 (412 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1860235/+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 1860235] Re: totem crashed with SIGSEGV in g_mount_spec_get()
https://gitlab.gnome.org/GNOME/totem/issues/390 ** Information type changed from Private to Public ** Bug watch added: gitlab.gnome.org/GNOME/totem/issues #390 https://gitlab.gnome.org/GNOME/totem/issues/390 ** Also affects: totem via https://gitlab.gnome.org/GNOME/totem/issues/390 Importance: Unknown Status: Unknown ** Description changed: + https://gitlab.gnome.org/GNOME/totem/issues/390 + + --- + I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 Uname: Linux 5.4.12-050412-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 19:08:13 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (412 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANGUAGE=es_CL:es - LANG=es_CL.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANGUAGE=es_CL:es + LANG=es_CL.UTF-8 SegvAnalysis: - Segfault happened at: 0x7ff6dc45dd09 : mov (%rbx),%rdi - PC (0x7ff6dc45dd09) ok - source "(%rbx)" (0x7000600070007) not located in a known VMA region (needed readable region)! - destination "%rdi" ok - Stack memory exhausted (SP below stack segment) + Segfault happened at: 0x7ff6dc45dd09 : mov (%rbx),%rdi + PC (0x7ff6dc45dd09) ok + source "(%rbx)" (0x7000600070007) not located in a known VMA region (needed readable region)! + destination "%rdi" ok + Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: totem StacktraceTop: - g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so - () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so - () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so - () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 - () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 + g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so + () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so + () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so + () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 + () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 Title: totem crashed with SIGSEGV in g_mount_spec_get() UpgradeStatus: Upgraded to focal on 2018-12-02 (412 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1860235 Title: totem crashed with SIGSEGV in g_mount_spec_get() Status in Totem: New Status in totem package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/totem/issues/390 --- I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 Uname: Linux 5.4.12-050412-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 19:08:13 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (412 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7ff6dc45dd09 : mov (%rbx),%rdi PC (0x7ff6dc45dd09) ok source "(%rbx)" (0x7000600070007) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: totem StacktraceTop: g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 Title: totem crashed with SIGSEGV in g_mount_spec_get() UpgradeStatus: Upgraded to focal on 2018-12-02 (412 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1860235/+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 1859485] Re: remmina crashed with SIGSEGV
** Also affects: remmina-ppa via https://gitlab.com/Remmina/Remmina/issues/2059 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1859485 Title: remmina crashed with SIGSEGV Status in remmina-ppa: Unknown Status in remmina package in Ubuntu: New Bug description: Close session of Win10(remote). --- https://gitlab.com/Remmina/Remmina/issues/2059 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: remmina 1.3.10+dfsg-1ubuntu1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 13 12:08:00 2020 ExecutablePath: /usr/bin/remmina InstallationDate: Installed on 2018-12-02 (406 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: remmina ProcEnviron: SHELL=/bin/bash LANGUAGE=es_CL:es LANG=es_CL.UTF-8 XDG_RUNTIME_DIR= PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f9442a77ac0:movdqu 0x10(%rax),%xmm2 PC (0x7f9442a77ac0) ok source "0x10(%rax)" (0x7f941f872a60) not located in a known VMA region (needed readable region)! destination "%xmm2" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: remmina StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 pixman_blt () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 () at /usr/lib/x86_64-linux-gnu/libcairo.so.2 () at /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: remmina crashed with SIGSEGV UpgradeStatus: Upgraded to focal on 2018-12-02 (406 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/remmina-ppa/+bug/1859485/+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 1859485] Re: remmina crashed with SIGSEGV
https://gitlab.com/Remmina/Remmina/issues/2059 ** Information type changed from Private to Public ** Description changed: Close session of Win10(remote). + + --- + + https://gitlab.com/Remmina/Remmina/issues/2059 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: remmina 1.3.10+dfsg-1ubuntu1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 13 12:08:00 2020 ExecutablePath: /usr/bin/remmina InstallationDate: Installed on 2018-12-02 (406 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: remmina ProcEnviron: - SHELL=/bin/bash - LANGUAGE=es_CL:es - LANG=es_CL.UTF-8 - XDG_RUNTIME_DIR= - PATH=(custom, no user) + SHELL=/bin/bash + LANGUAGE=es_CL:es + LANG=es_CL.UTF-8 + XDG_RUNTIME_DIR= + PATH=(custom, no user) SegvAnalysis: - Segfault happened at: 0x7f9442a77ac0:movdqu 0x10(%rax),%xmm2 - PC (0x7f9442a77ac0) ok - source "0x10(%rax)" (0x7f941f872a60) not located in a known VMA region (needed readable region)! - destination "%xmm2" ok + Segfault happened at: 0x7f9442a77ac0:movdqu 0x10(%rax),%xmm2 + PC (0x7f9442a77ac0) ok + source "0x10(%rax)" (0x7f941f872a60) not located in a known VMA region (needed readable region)! + destination "%xmm2" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: remmina StacktraceTop: - () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 - () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 - pixman_blt () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 - () at /usr/lib/x86_64-linux-gnu/libcairo.so.2 - () at /usr/lib/x86_64-linux-gnu/libcairo.so.2 + () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 + () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 + pixman_blt () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 + () at /usr/lib/x86_64-linux-gnu/libcairo.so.2 + () at /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: remmina crashed with SIGSEGV UpgradeStatus: Upgraded to focal on 2018-12-02 (406 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Bug watch added: gitlab.com/Remmina/Remmina/issues #2059 https://gitlab.com/Remmina/Remmina/issues/2059 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1859485 Title: remmina crashed with SIGSEGV Status in remmina package in Ubuntu: New Bug description: Close session of Win10(remote). --- https://gitlab.com/Remmina/Remmina/issues/2059 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: remmina 1.3.10+dfsg-1ubuntu1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 13 12:08:00 2020 ExecutablePath: /usr/bin/remmina InstallationDate: Installed on 2018-12-02 (406 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: remmina ProcEnviron: SHELL=/bin/bash LANGUAGE=es_CL:es LANG=es_CL.UTF-8 XDG_RUNTIME_DIR= PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f9442a77ac0:movdqu 0x10(%rax),%xmm2 PC (0x7f9442a77ac0) ok source "0x10(%rax)" (0x7f941f872a60) not located in a known VMA region (needed readable region)! destination "%xmm2" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: remmina StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 pixman_blt () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 () at /usr/lib/x86_64-linux-gnu/libcairo.so.2 () at /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: remmina crashed with SIGSEGV UpgradeStatus: Upgraded to focal on 2018-12-02 (406 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1859485/+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 1859437] Re: gnome-software crashed with SIGSEGV in as_app_add_provide()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1859437 Title: gnome-software crashed with SIGSEGV in as_app_add_provide() Status in gnome-software package in Ubuntu: New Bug description: I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-software 3.30.6-2ubuntu11 Uname: Linux 5.4.10-050410-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 10 07:52:49 2020 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-12-02 (406 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: gnome-software-plugin-flatpak 3.30.6-2ubuntu11 gnome-software-plugin-snap3.30.6-2ubuntu11 ProcCmdline: /usr/bin/gnome-software --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7f0fdeeb2c84 :mov (%rdx,%rax,8),%r14 PC (0x7f0fdeeb2c84) ok source "(%rdx,%rax,8)" (0x2e70) not located in a known VMA region (needed readable region)! destination "%r14" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-software StacktraceTop: as_app_add_provide () at /usr/lib/x86_64-linux-gnu/libappstream-glib.so.8 () at /usr/lib/x86_64-linux-gnu/libappstream-glib.so.8 as_store_add_apps () at /usr/lib/x86_64-linux-gnu/libappstream-glib.so.8 () at /usr/lib/x86_64-linux-gnu/gs-plugins-12/libgs_plugin_flatpak.so () at /usr/lib/x86_64-linux-gnu/gs-plugins-12/libgs_plugin_flatpak.so Title: gnome-software crashed with SIGSEGV in as_app_add_provide() UpgradeStatus: Upgraded to focal on 2018-12-02 (406 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1859437/+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 1859347] Re: cups-browsed crashed with SIGSEGV in unlink_chunk()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1859347 Title: cups-browsed crashed with SIGSEGV in unlink_chunk() Status in cups-filters package in Ubuntu: New Bug description: I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: cups-browsed 1.26.1-1 Uname: Linux 5.4.10-050410-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CupsErrorLog: Date: Sun Jan 12 14:39:42 2020 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2018-12-02 (405 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lpstat: device for Samsung-CLX-8640-8650: lpd://10.39.106.2/lp MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx Papersize: letter PpdFiles: Samsung-CLX-8640-8650: Samsung CLX-8640 8650 Series PS ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.10-050410-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f5c60543ad1 : cmp 0x18(%rax),%rdi PC (0x7f5c60543ad1) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: cups-filters StacktraceTop: unlink_chunk (p=p@entry=0x561be25b4fc0, av=0x7f5c60695b80 ) at malloc.c:1459 _int_malloc (av=av@entry=0x7f5c60695b80 , bytes=bytes@entry=184) at malloc.c:4041 __libc_calloc (n=, elem_size=) at malloc.c:3428 () at /lib/x86_64-linux-gnu/libdbus-1.so.3 _dbus_message_loader_queue_messages () at /lib/x86_64-linux-gnu/libdbus-1.so.3 Title: cups-browsed crashed with SIGSEGV in unlink_chunk() UpgradeStatus: Upgraded to focal on 2018-12-02 (405 days ago) UserGroups: dmi.bios.date: 04/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1859347/+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 1736664] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv() from g_log() from gjs_callback_closure() f
** Tags added: focal -- 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/1736664 Title: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv() from g_log() from gjs_callback_closure() from ffi_closure_unix64_inner() [any error message logged from JavaScript will look like this] Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.26.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736664/+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 1858414] Re: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject()
** Description changed: - This happened after entering the user's password. It did not boot after - GDM gnome-shell. + This happened after selecting and entering the password of the GDM user. + + GDM gives the pass to gnome-shell, and it does not part. I reboot the + notebook, and it successfully enters gnome-shell. --- https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 Uname: Linux 5.4.8-050408-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 07:42:52 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (399 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 ObjectInstance::remove_wrapped_gobjects_if(std::function const&, std::function const&) () at /usr/lib/libgjs.so.0 ObjectInstance::update_heap_wrapper_weak_pointers(JSContext*, JSCompartment*, void*) () at /usr/lib/libgjs.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() UpgradeStatus: Upgraded to focal on 2018-12-02 (399 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Description changed: This happened after selecting and entering the password of the GDM user. - GDM gives the pass to gnome-shell, and it does not part. I reboot the - notebook, and it successfully enters gnome-shell. + GDM gives the pass to gnome-shell, and it does not start. I reboot the + notebook, and it successfully enters gnome-shell --- https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 Uname: Linux 5.4.8-050408-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 07:42:52 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (399 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 ObjectInstance::remove_wrapped_gobjects_if(std::function const&, std::function const&) () at /usr/lib/libgjs.so.0 ObjectInstance::update_heap_wrapper_weak_pointers(JSContext*, JSCompartment*, void*) () at /usr/lib/libgjs.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() UpgradeStatus: Upgraded to focal on 2018-12-02 (399 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- 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/1858414 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: This happened after selecting and entering the password of the GDM user. GDM gives the pass to gnome-shell, and it does not start. I reboot the notebook, and it successfully enters gnome-shell --- https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 Uname: Linux 5.4.8-050408-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 07:42:52 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (399 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ObjectInstance::disassociate_js_gobject() () at
[Desktop-packages] [Bug 1858414] Re: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject()
** Description changed: - I don't know what happened. + This happened after entering the user's password. It did not boot after + GDM gnome-shell. --- https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 Uname: Linux 5.4.8-050408-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 07:42:52 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (399 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 ObjectInstance::remove_wrapped_gobjects_if(std::function const&, std::function const&) () at /usr/lib/libgjs.so.0 ObjectInstance::update_heap_wrapper_weak_pointers(JSContext*, JSCompartment*, void*) () at /usr/lib/libgjs.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() UpgradeStatus: Upgraded to focal on 2018-12-02 (399 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- 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/1858414 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: This happened after entering the user's password. It did not boot after GDM gnome-shell. --- https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 Uname: Linux 5.4.8-050408-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 07:42:52 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (399 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 ObjectInstance::remove_wrapped_gobjects_if(std::function const&, std::function const&) () at /usr/lib/libgjs.so.0 ObjectInstance::update_heap_wrapper_weak_pointers(JSContext*, JSCompartment*, void*) () at /usr/lib/libgjs.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() UpgradeStatus: Upgraded to focal on 2018-12-02 (399 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1858414/+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 1841794] Re: gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed ob
See LP: #1858414 -- 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/1841794 Title: gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed object of type: Clutter.PropertyTransition"] Status in GNOME Shell: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Eoan: Fix Released Bug description: https://errors.ubuntu.com/problem/10051642bda6e2a9a27fe0b0d5f84f8b1f29438f ubuntu-bug crash report for bug reported in LP: #1841680 On Eoan, gnome-shell (3.33.91-1ubuntu1) crashes and restarts when opening up applications from the dock. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 27 10:42:41 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-02-19 (554 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: Upgraded to eoan on 2019-08-27 (0 days ago) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1841794/+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 1858414] Re: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject()
https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2084 https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 Importance: Unknown Status: Unknown ** Description changed: I don't know what happened. + + --- + + https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 Uname: Linux 5.4.8-050408-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 07:42:52 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (399 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: - LANG=es_CL.UTF-8 - LANGUAGE=es_CL:es - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=es_CL.UTF-8 + LANGUAGE=es_CL:es + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: - ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 - ObjectInstance::remove_wrapped_gobjects_if(std::function const&, std::function const&) () at /usr/lib/libgjs.so.0 - ObjectInstance::update_heap_wrapper_weak_pointers(JSContext*, JSCompartment*, void*) () at /usr/lib/libgjs.so.0 - () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 - () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 + ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 + ObjectInstance::remove_wrapped_gobjects_if(std::function const&, std::function const&) () at /usr/lib/libgjs.so.0 + ObjectInstance::update_heap_wrapper_weak_pointers(JSContext*, JSCompartment*, void*) () at /usr/lib/libgjs.so.0 + () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 + () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() UpgradeStatus: Upgraded to focal on 2018-12-02 (399 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- 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/1858414 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: I don't know what happened. --- https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 Uname: Linux 5.4.8-050408-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 07:42:52 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (399 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 ObjectInstance::remove_wrapped_gobjects_if(std::function const&, std::function const&) () at /usr/lib/libgjs.so.0 ObjectInstance::update_heap_wrapper_weak_pointers(JSContext*, JSCompartment*, void*) () at /usr/lib/libgjs.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() UpgradeStatus: Upgraded to focal on 2018-12-02 (399 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1858414/+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 1858414] Re: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1858414 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() Status in gnome-shell package in Ubuntu: New Bug description: I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 Uname: Linux 5.4.8-050408-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 07:42:52 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (399 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 ObjectInstance::remove_wrapped_gobjects_if(std::function const&, std::function const&) () at /usr/lib/libgjs.so.0 ObjectInstance::update_heap_wrapper_weak_pointers(JSContext*, JSCompartment*, void*) () at /usr/lib/libgjs.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() UpgradeStatus: Upgraded to focal on 2018-12-02 (399 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1858414/+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 1857736] Re: nautilus crashed with SIGABRT
https://gitlab.gnome.org/GNOME/nautilus/issues/1324 ** Description changed: I do not know, what happened. + + --- + + https://gitlab.gnome.org/GNOME/nautilus/issues/1324 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.34.1-1ubuntu1 Uname: Linux 5.4.6-050406-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 27 21:22:37 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-12-02 (390 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANGUAGE=es_CL:es - LANG=es_CL.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANGUAGE=es_CL:es + LANG=es_CL.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: - () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - () - () - () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + () + () + () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGABRT UpgradeStatus: Upgraded to focal on 2018-12-02 (390 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: - + usr_lib_nautilus: ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1324 https://gitlab.gnome.org/GNOME/nautilus/issues/1324 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/1324 Importance: Unknown Status: Unknown -- 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/1857736 Title: nautilus crashed with SIGABRT Status in Nautilus: Unknown Status in nautilus package in Ubuntu: New Bug description: I do not know, what happened. --- https://gitlab.gnome.org/GNOME/nautilus/issues/1324 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.34.1-1ubuntu1 Uname: Linux 5.4.6-050406-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 27 21:22:37 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-12-02 (390 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () () () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGABRT UpgradeStatus: Upgraded to focal on 2018-12-02 (390 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1857736/+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 1857736] Re: nautilus crashed with SIGABRT
** Information type changed from Private to Public -- 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/1857736 Title: nautilus crashed with SIGABRT Status in nautilus package in Ubuntu: New Bug description: I do not know, what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.34.1-1ubuntu1 Uname: Linux 5.4.6-050406-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 27 21:22:37 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-12-02 (390 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () () () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGABRT UpgradeStatus: Upgraded to focal on 2018-12-02 (390 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857736/+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 1797820] Re: Xorg/Xwayland crashed with SIGSEGV in glamor_bind_texture → glamor_set_composite_texture → glamor_composite_set_shader_blend → glamor_composite_with_shader → glamo
** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1797820 Title: Xorg/Xwayland crashed with SIGSEGV in glamor_bind_texture → glamor_set_composite_texture → glamor_composite_set_shader_blend → glamor_composite_with_shader → glamor_composite_clipped_region Status in xorg-server package in Ubuntu: Confirmed Bug description: Xwayland: https://errors.ubuntu.com/problem/f8ea9bb558676edbe2acec52b0f386ab1321fdaf Xorg: https://errors.ubuntu.com/problem/90ab0b3de538bdc1058e1af52156d870e04dd56e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1797820/+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 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no screens found") from dix_main()
** Tags added: focal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1543192
Title:
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("no screens found") from dix_main()
Status in xorg-server package in Ubuntu:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530
---
No idea what happened.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core 2:1.17.3-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CrashCounter: 1
Date: Mon Feb 8 17:07:23 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics
Controller [17aa:21da]
InstallationDate: Installed on 2015-04-30 (283 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 429149G
ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic
root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0
panic=-1
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
OsAbort ()
?? ()
FatalError ()
?? ()
__libc_start_main (main=0x557f8180ff00, argc=11, argv=0x7fffc9e34fd8,
init=, fini=, rtld_fini=,
stack_end=0x7fffc9e34fc8) at libc-start.c:289
SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit
code 2:
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/18/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET46WW (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 429149G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 429149G
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.66-2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20160127-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
xserver.bootTime: Mon Feb 8 17:08:14 2016
xserver.configfile: default
xserver.errors: systemd-logind: failed to get session: PID 9847 does not
belong to any known session
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 728
vendor LGD
xserver.version: 2:1.17.3-2ubuntu2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192/+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 1825727] Re: gnome-shell-extension-prefs crashed with SIGSEGV in gtk_css_gadget_set_state() from gtk_switch_state_flags_changed()
** Tags added: focal -- 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/1825727 Title: gnome-shell-extension-prefs crashed with SIGSEGV in gtk_css_gadget_set_state() from gtk_switch_state_flags_changed() Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/b9099237efc0ed3a713ac34e260c33a215c4599d Crashes when updating extensions using gnome-tweaks on Gnome 3.32+ ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Apr 21 19:32:17 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell-extension-prefs InstallationDate: Installed on 2019-01-01 (110 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcCmdline: gnome-shell-extension-prefs dash-to-pa...@jderose9.github.com ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f32337f2a77:mov(%rdi,%rax,1),%rdi PC (0x7f32337f2a77) ok source "(%rdi,%rax,1)" (0xffd0) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_cclosure_marshal_VOID__UINTv () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell-extension-prefs crashed with SIGSEGV UpgradeStatus: Upgraded to disco on 2019-04-19 (2 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-01-15T04:51:59.517661 separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820859] Re: /usr/bin/nautilus:11:g_application_impl_get_dbus_object_path:g_application_get_dbus_object_path:update_dbus_opened_locations:bus_acquired_cb:connection_get_cb
** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1820859 Title: /usr/bin/nautilus:11:g_application_impl_get_dbus_object_path:g_application_get_dbus_object_path:update_dbus_opened_locations:bus_acquired_cb:connection_get_cb Status in nautilus package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.31.90-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/8a8c9fc62039a8bb83a7ee530ac4140a9b8c29d9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
** Tags added: focal -- 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/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path Status in Nautilus: New Status in gtk+3.0 package in Ubuntu: New Status in nautilus package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/nautilus/issues/1190 --- https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1726129/+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 1845000] Re: evince assert failure: double free or corruption (!prev)
https://gitlab.gnome.org/GNOME/evince/issues/1246 ** No longer affects: evince ** Bug watch added: gitlab.gnome.org/GNOME/evince/issues #1246 https://gitlab.gnome.org/GNOME/evince/issues/1246 ** Also affects: evince via https://gitlab.gnome.org/GNOME/evince/issues/1246 Importance: Unknown Status: Unknown ** Description changed: - https://gitlab.gnome.org/GNOME/evince/issues/1259 + https://gitlab.gnome.org/GNOME/evince/issues/1246 --- I'm working with .pdf ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: evince 3.32.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AssertionMessage: double free or corruption (!prev) CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 09:20:00 2019 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2018-12-02 (294 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-12-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: evince StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f16dd7e73a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f16dd7e90c0 "double free or corruption (!prev)") at malloc.c:5332 _int_free (av=0x7f16dd818b80 , p=0x560e3a72c2c0, have_lock=) at malloc.c:4317 g_datalist_clear () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: evince assert failure: double free or corruption (!prev) UpgradeStatus: Upgraded to eoan on 2018-12-02 (294 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1845000 Title: evince assert failure: double free or corruption (!prev) Status in Evince: Unknown Status in evince package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/evince/issues/1246 --- I'm working with .pdf ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: evince 3.32.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AssertionMessage: double free or corruption (!prev) CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 09:20:00 2019 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2018-12-02 (294 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-12-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: evince StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f16dd7e73a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f16dd7e90c0 "double free or corruption (!prev)") at malloc.c:5332 _int_free (av=0x7f16dd818b80 , p=0x560e3a72c2c0, have_lock=) at malloc.c:4317 g_datalist_clear () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: evince assert failure: double free or corruption (!prev) UpgradeStatus: Upgraded to eoan on 2018-12-02 (294 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1845000/+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 1845000] Re: evince assert failure: double free or corruption (!prev)
https://gitlab.gnome.org/GNOME/evince/issues/1259 ** Bug watch added: gitlab.gnome.org/GNOME/evince/issues #1259 https://gitlab.gnome.org/GNOME/evince/issues/1259 ** Also affects: evince via https://gitlab.gnome.org/GNOME/evince/issues/1259 Importance: Unknown Status: Unknown ** Description changed: + https://gitlab.gnome.org/GNOME/evince/issues/1259 + + --- + I'm working with .pdf ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: evince 3.32.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AssertionMessage: double free or corruption (!prev) CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 09:20:00 2019 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2018-12-02 (294 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-12-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANGUAGE=es_CL:es - LANG=es_CL.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANGUAGE=es_CL:es + LANG=es_CL.UTF-8 Signal: 6 SourcePackage: evince StacktraceTop: - __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f16dd7e73a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 - malloc_printerr (str=str@entry=0x7f16dd7e90c0 "double free or corruption (!prev)") at malloc.c:5332 - _int_free (av=0x7f16dd818b80 , p=0x560e3a72c2c0, have_lock=) at malloc.c:4317 - g_datalist_clear () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 + __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f16dd7e73a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 + malloc_printerr (str=str@entry=0x7f16dd7e90c0 "double free or corruption (!prev)") at malloc.c:5332 + _int_free (av=0x7f16dd818b80 , p=0x560e3a72c2c0, have_lock=) at malloc.c:4317 + g_datalist_clear () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: evince assert failure: double free or corruption (!prev) UpgradeStatus: Upgraded to eoan on 2018-12-02 (294 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1845000 Title: evince assert failure: double free or corruption (!prev) Status in Evince: Unknown Status in evince package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/evince/issues/1259 --- I'm working with .pdf ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: evince 3.32.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AssertionMessage: double free or corruption (!prev) CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 09:20:00 2019 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2018-12-02 (294 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-12-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: evince StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f16dd7e73a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f16dd7e90c0 "double free or corruption (!prev)") at malloc.c:5332 _int_free (av=0x7f16dd818b80 , p=0x560e3a72c2c0, have_lock=) at malloc.c:4317 g_datalist_clear () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: evince assert failure: double free or corruption (!prev) UpgradeStatus: Upgraded to eoan on 2018-12-02 (294 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1845000/+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 1845000] Re: evince assert failure: double free or corruption (!prev)
** Information type changed from Private to Public ** Attachment added: "valgrind.log" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1845000/+attachment/5290711/+files/valgrind.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1845000 Title: evince assert failure: double free or corruption (!prev) Status in evince package in Ubuntu: New Bug description: I'm working with .pdf ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: evince 3.32.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AssertionMessage: double free or corruption (!prev) CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 09:20:00 2019 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2018-12-02 (294 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-12-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: evince StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f16dd7e73a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f16dd7e90c0 "double free or corruption (!prev)") at malloc.c:5332 _int_free (av=0x7f16dd818b80 , p=0x560e3a72c2c0, have_lock=) at malloc.c:4317 g_datalist_clear () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: evince assert failure: double free or corruption (!prev) UpgradeStatus: Upgraded to eoan on 2018-12-02 (294 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1845000/+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 1843703] Re: gnome-shell crashed with SIGSEGV in async_get_property_finish()
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1599 ** Description changed: + https://gitlab.gnome.org/GNOME/gnome-shell/issues/1599 + + --- + I have proposed to the list of package updates. Selecting some packages to update from there. After restarting, he does not log in and he votes me for the session. Then I try again and I can enter. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 08:56:37 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (283 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: - LANG=es_CL.UTF-8 - LANGUAGE=es_CL:es - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=es_CL.UTF-8 + LANGUAGE=es_CL:es + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: - __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 - () - () at /lib/x86_64-linux-gnu/libc.so.6 - () at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0 - () at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0 + __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 + () + () at /lib/x86_64-linux-gnu/libc.so.6 + () at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0 + () at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: Upgraded to eoan on 2018-12-02 (283 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1599 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1599 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1599 Importance: Unknown Status: Unknown ** Description changed: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1599 --- I have proposed to the list of package updates. Selecting some packages to update from there. After restarting, he does not log in and he votes me for the session. Then I try again and I can enter. + + Also crashed _usr_lib_gnome-session_gnome-session-binary.1000 ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 08:56:37 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (283 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 () () at /lib/x86_64-linux-gnu/libc.so.6 () at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: Upgraded to eoan on 2018-12-02 (283 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** No longer affects: gnome-shell ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #780 https://gitlab.gnome.org/GNOME/mutter/issues/780 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/mutter/issues/780 Importance: Unknown Status: Unknown ** Description changed: - https://gitlab.gnome.org/GNOME/gnome-shell/issues/1599 + https://gitlab.gnome.org/GNOME/mutter/issues/780 --- I have proposed to the list of package updates. Selecting some packages to update from there. After restarting, he does not log in and he votes me for the session. Then I try again and I can enter. Also crashed _usr_lib_gnome-session_gnome-session-binary.1000 ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 08:56:37 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (283 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline:
[Desktop-packages] [Bug 1843698] Re: gnome-software crashed with SIGSEGV in __memmove_avx_unaligned_erms()
https://gitlab.gnome.org/GNOME/gnome-software/issues/792 ** Information type changed from Private to Public ** Description changed: + https://gitlab.gnome.org/GNOME/gnome-software/issues/792 + + --- + I do not know what happened. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 07:57:24 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-12-02 (283 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: - gnome-software-plugin-flatpak 3.30.6-2ubuntu10 - gnome-software-plugin-snap3.30.6-2ubuntu10 + gnome-software-plugin-flatpak 3.30.6-2ubuntu10 + gnome-software-plugin-snap3.30.6-2ubuntu10 ProcCmdline: /usr/bin/gnome-software --gapplication-service ProcEnviron: - LANG=es_CL.UTF-8 - LANGUAGE=es_CL:es - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=es_CL.UTF-8 + LANGUAGE=es_CL:es + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= SegvAnalysis: - Segfault happened at: 0x7f565aa3fcc4 <__memmove_avx_unaligned_erms+372>: vmovdqu -0x20(%rsi,%rdx,1),%ymm5 - PC (0x7f565aa3fcc4) ok - source "-0x20(%rsi,%rdx,1)" (0x7f5e4c1bab30) not located in a known VMA region (needed readable region)! - destination "%ymm5" ok - Stack memory exhausted (SP below stack segment) + Segfault happened at: 0x7f565aa3fcc4 <__memmove_avx_unaligned_erms+372>: vmovdqu -0x20(%rsi,%rdx,1),%ymm5 + PC (0x7f565aa3fcc4) ok + source "-0x20(%rsi,%rdx,1)" (0x7f5e4c1bab30) not located in a known VMA region (needed readable region)! + destination "%ymm5" ok + Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-software StacktraceTop: - __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:384 - g_ptr_array_remove_range () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_ptr_array_set_size () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - as_store_remove_all () at /usr/lib/x86_64-linux-gnu/libappstream-glib.so.8 - () at /usr/lib/x86_64-linux-gnu/gs-plugins-12/libgs_plugin_flatpak.so + __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:384 + g_ptr_array_remove_range () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_ptr_array_set_size () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + as_store_remove_all () at /usr/lib/x86_64-linux-gnu/libappstream-glib.so.8 + () at /usr/lib/x86_64-linux-gnu/gs-plugins-12/libgs_plugin_flatpak.so Title: gnome-software crashed with SIGSEGV in __memmove_avx_unaligned_erms() UpgradeStatus: Upgraded to eoan on 2018-12-02 (283 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/issues #792 https://gitlab.gnome.org/GNOME/gnome-software/issues/792 ** Also affects: gnome-software via https://gitlab.gnome.org/GNOME/gnome-software/issues/792 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1843698 Title: gnome-software crashed with SIGSEGV in __memmove_avx_unaligned_erms() Status in GNOME Software: Unknown Status in gnome-software package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/gnome-software/issues/792 --- I do not know what happened. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 07:57:24 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-12-02 (283 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: gnome-software-plugin-flatpak 3.30.6-2ubuntu10 gnome-software-plugin-snap3.30.6-2ubuntu10 ProcCmdline: /usr/bin/gnome-software --gapplication-service ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f565aa3fcc4 <__memmove_avx_unaligned_erms+372>: vmovdqu -0x20(%rsi,%rdx,1),%ymm5 PC (0x7f565aa3fcc4) ok source "-0x20(%rsi,%rdx,1)" (0x7f5e4c1bab30) not located in a known VMA region (needed readable region)! destination "%ymm5" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-software
[Desktop-packages] [Bug 1843627] Re: evolution-calendar-factory crashed with SIGSEGV in tcache_get()
https://gitlab.gnome.org/GNOME/evolution/issues/616 ** Information type changed from Private to Public ** Description changed: + https://gitlab.gnome.org/GNOME/evolution/issues/616 + + --- + I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: evolution-data-server 3.33.91-3 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 13:41:26 2019 ExecutablePath: /usr/libexec/evolution-calendar-factory InstallationDate: Installed on 2018-12-02 (282 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/libexec/evolution-calendar-factory ProcEnviron: - LANG=es_CL.UTF-8 - LANGUAGE=es_CL:es - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=es_CL.UTF-8 + LANGUAGE=es_CL:es + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= SegvAnalysis: - Segfault happened at: 0x7f36355653ae <__GI___libc_malloc+286>: mov (%r8),%rsi - PC (0x7f36355653ae) ok - source "(%r8)" (0x7f36) not located in a known VMA region (needed readable region)! - destination "%rsi" ok - Stack memory exhausted (SP below stack segment) + Segfault happened at: 0x7f36355653ae <__GI___libc_malloc+286>: mov (%r8),%rsi + PC (0x7f36355653ae) ok + source "(%r8)" (0x7f36) not located in a known VMA region (needed readable region)! + destination "%rsi" ok + Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: - tcache_get (tc_idx=) at malloc.c:2937 - __GI___libc_malloc (bytes=32) at malloc.c:3051 - g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_datalist_id_set_data_full () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + tcache_get (tc_idx=) at malloc.c:2937 + __GI___libc_malloc (bytes=32) at malloc.c:3051 + g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_datalist_id_set_data_full () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get() UpgradeStatus: Upgraded to eoan on 2018-12-02 (282 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Bug watch added: gitlab.gnome.org/GNOME/evolution/issues #616 https://gitlab.gnome.org/GNOME/evolution/issues/616 ** Also affects: evolution-data-server via https://gitlab.gnome.org/GNOME/evolution/issues/616 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1843627 Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get() Status in evolution-data-server: Unknown Status in evolution-data-server package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/evolution/issues/616 --- I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: evolution-data-server 3.33.91-3 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 13:41:26 2019 ExecutablePath: /usr/libexec/evolution-calendar-factory InstallationDate: Installed on 2018-12-02 (282 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/libexec/evolution-calendar-factory ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f36355653ae <__GI___libc_malloc+286>: mov (%r8),%rsi PC (0x7f36355653ae) ok source "(%r8)" (0x7f36) not located in a known VMA region (needed readable region)! destination "%rsi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: tcache_get (tc_idx=) at malloc.c:2937 __GI___libc_malloc (bytes=32) at malloc.c:3051 g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_datalist_id_set_data_full () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get() UpgradeStatus: Upgraded to eoan on 2018-12-02 (282 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1843627/+subscriptions -- Mailing
[Desktop-packages] [Bug 1843467] Re: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE()
https://gitlab.gnome.org/GNOME/nautilus/issues/1216 ** Information type changed from Private to Public ** Description changed: + https://gitlab.gnome.org/GNOME/nautilus/issues/1216 + + --- + I opened nautilus to see my files from my account u...@gmail.com. And before it loaded, I pressed the magnifying glass. After all this, nautilus crash. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.33.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 10 14:44:44 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-12-02 (282 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANGUAGE=es_CL:es - LANG=es_CL.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANGUAGE=es_CL:es + LANG=es_CL.UTF-8 SegvAnalysis: - Segfault happened at: 0x55ae33b30b2d : mov0x0(%rbp),%rdi - PC (0x55ae33b30b2d) ok - source "0x0(%rbp)" (0x) not located in a known VMA region (needed readable region)! - destination "%rdi" ok + Segfault happened at: 0x55ae33b30b2d : mov0x0(%rbp),%rdi + PC (0x55ae33b30b2d) ok + source "0x0(%rbp)" (0x) not located in a known VMA region (needed readable region)! + destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: - nautilus_view_is_searching () - () - g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + nautilus_view_is_searching () + () + g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in nautilus_view_is_searching() UpgradeStatus: Upgraded to eoan on 2018-12-02 (281 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: - + usr_lib_nautilus: ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1216 https://gitlab.gnome.org/GNOME/nautilus/issues/1216 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/1216 Importance: Unknown Status: Unknown -- 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/1843467 Title: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE() Status in Nautilus: Unknown Status in nautilus package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/nautilus/issues/1216 --- I opened nautilus to see my files from my account u...@gmail.com. And before it loaded, I pressed the magnifying glass. After all this, nautilus crash. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.33.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 10 14:44:44 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-12-02 (282 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x55ae33b30b2d : mov0x0(%rbp),%rdi PC (0x55ae33b30b2d) ok source "0x0(%rbp)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: nautilus_view_is_searching () () g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in nautilus_view_is_searching() UpgradeStatus: Upgraded to eoan on 2018-12-02 (281 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1843467/+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 1839211] Re: Please upgrade to 2.2.1-1(Debian)
Please, close report. New version in eoan: https://launchpad.net/ubuntu/+source/tracker/2.2.99.0-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1839211 Title: Please upgrade to 2.2.1-1(Debian) Status in tracker package in Ubuntu: Triaged Bug description: I am testing gnome-music [0]night, and request tracker version 2.2.0 or higher. [0] https://wiki.gnome.org/Apps/Music/Resources ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.1.8-2 Uname: Linux 5.2.6-050206-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 16:10:43 2019 InstallationDate: Installed on 2018-12-02 (247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1839211/+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 1839211] Re: Please upgrade to 2.2.1-1(Debian)
See LP: #1842118 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1839211 Title: Please upgrade to 2.2.1-1(Debian) Status in tracker package in Ubuntu: Triaged Bug description: I am testing gnome-music [0]night, and request tracker version 2.2.0 or higher. [0] https://wiki.gnome.org/Apps/Music/Resources ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.1.8-2 Uname: Linux 5.2.6-050206-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 16:10:43 2019 InstallationDate: Installed on 2018-12-02 (247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1839211/+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 1839211] Re: Please upgrade to 2.2.1-1(Debian)
See LP 1842118 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1839211 Title: Please upgrade to 2.2.1-1(Debian) Status in tracker package in Ubuntu: Triaged Bug description: I am testing gnome-music [0]night, and request tracker version 2.2.0 or higher. [0] https://wiki.gnome.org/Apps/Music/Resources ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.1.8-2 Uname: Linux 5.2.6-050206-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 16:10:43 2019 InstallationDate: Installed on 2018-12-02 (247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1839211/+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 1839211] Re: Please upgrade to 2.2.1-1(Debian)
See LP #1842118 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1839211 Title: Please upgrade to 2.2.1-1(Debian) Status in tracker package in Ubuntu: Triaged Bug description: I am testing gnome-music [0]night, and request tracker version 2.2.0 or higher. [0] https://wiki.gnome.org/Apps/Music/Resources ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.1.8-2 Uname: Linux 5.2.6-050206-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 16:10:43 2019 InstallationDate: Installed on 2018-12-02 (247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1839211/+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 1839211] Re: Please upgrade to 2.2.1-1(Debian)
Please close report. New version in eoan: https://launchpad.net/ubuntu/+source/tracker/2.2.99.0-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1839211 Title: Please upgrade to 2.2.1-1(Debian) Status in tracker package in Ubuntu: Triaged Bug description: I am testing gnome-music [0]night, and request tracker version 2.2.0 or higher. [0] https://wiki.gnome.org/Apps/Music/Resources ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.1.8-2 Uname: Linux 5.2.6-050206-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 16:10:43 2019 InstallationDate: Installed on 2018-12-02 (247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1839211/+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 1840996] Re: Working with Samba
** Summary changed: - Working with smb + Working with Samba ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/1201 Importance: Unknown Status: Unknown -- 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/1840996 Title: Working with Samba Status in Nautilus: Unknown Status in nautilus package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/nautilus/issues/1201 --- I opened nautilus, accessed a shared resource with samba. Then I tried to write in that mounted folder. And he threw me that he had no writing privileges. I went to the samba server configuration and increased the privileges. And I tried to write *without* closing nautilus. It was something similar to what I mention. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.33.90-1ubuntu1 Uname: Linux 5.2.9-050209-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 21 19:25:59 2019 ExecutablePath: /usr/bin/nautilus ExecutableTimestamp: 1565361020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2018-12-02 (262 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcCwd: /home/caravena ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: nautilus UpgradeStatus: Upgraded to eoan on 2018-12-02 (262 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1840996/+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 1840996] Re: Working with smb
Add: https://gitlab.gnome.org/GNOME/nautilus/issues/1201 ** Information type changed from Private to Public ** Description changed: + https://gitlab.gnome.org/GNOME/nautilus/issues/1201 + + --- + I opened nautilus, accessed a shared resource with samba. Then I tried to write in that mounted folder. And he threw me that he had no writing privileges. I went to the samba server configuration and increased the privileges. And I tried to write *without* closing nautilus. It was something similar to what I mention. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.33.90-1ubuntu1 Uname: Linux 5.2.9-050209-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 21 19:25:59 2019 ExecutablePath: /usr/bin/nautilus ExecutableTimestamp: 1565361020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2018-12-02 (262 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcCwd: /home/caravena ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: nautilus UpgradeStatus: Upgraded to eoan on 2018-12-02 (262 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1201 https://gitlab.gnome.org/GNOME/nautilus/issues/1201 -- 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/1840996 Title: Working with smb Status in nautilus package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/nautilus/issues/1201 --- I opened nautilus, accessed a shared resource with samba. Then I tried to write in that mounted folder. And he threw me that he had no writing privileges. I went to the samba server configuration and increased the privileges. And I tried to write *without* closing nautilus. It was something similar to what I mention. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.33.90-1ubuntu1 Uname: Linux 5.2.9-050209-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 21 19:25:59 2019 ExecutablePath: /usr/bin/nautilus ExecutableTimestamp: 1565361020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2018-12-02 (262 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcCwd: /home/caravena ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: nautilus UpgradeStatus: Upgraded to eoan on 2018-12-02 (262 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1840996/+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 1840915] Re: tracker-store crashed with SIGSEGV in tracker_events_add_delete()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1840915 Title: tracker-store crashed with SIGSEGV in tracker_events_add_delete() Status in tracker package in Ubuntu: Invalid Bug description: I don't know how it happened. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: tracker 2.1.8-2 Uname: Linux 5.2.9-050209-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 21 08:28:15 2019 ExecutablePath: /usr/lib/tracker/tracker-store InstallationDate: Installed on 2018-12-02 (261 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/lib/tracker/tracker-store ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x56172bf3c22d : mov0x10(%rax),%rdi PC (0x56172bf3c22d) ok source "0x10(%rax)" (0x0010) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: tracker StacktraceTop: tracker_events_add_delete () () () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so.0 () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so.0 () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so.0 Title: tracker-store crashed with SIGSEGV in tracker_events_add_delete() UpgradeStatus: Upgraded to eoan on 2018-12-02 (261 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1840915/+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 1501049] Re: totem crashed with assertion failure [Totem:ERROR:totem-grilo.c:729:browse_cb: code should not be reached]
** Description changed: https://errors.ubuntu.com/problem/49f61eb5b4c7c242dac2179ff053a937285c37ce --- the gnome video application crashed twice while attempting to browse a upnp media server. at first I tried to play a video which failed to play, then twice afterwards the application crashed before it would even load the file list --- $ LANGUAGE=C totem Click 'Channels' - Click 'ServerDLNA' + Click 'DLNAServer' Click 'Photos' Click 'All Photos' In console: ** Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Bail out! Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Abortado (`core' generado) ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: totem 3.16.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 29 16:31:47 2015 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2015-09-28 (0 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo ** Description changed: https://errors.ubuntu.com/problem/49f61eb5b4c7c242dac2179ff053a937285c37ce --- the gnome video application crashed twice while attempting to browse a upnp media server. at first I tried to play a video which failed to play, then twice afterwards the application crashed before it would even load the file list --- $ LANGUAGE=C totem Click 'Channels' - Click 'DLNAServer' + Click 'DLNA-Server' Click 'Photos' Click 'All Photos' In console: ** Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Bail out! Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Abortado (`core' generado) ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: totem 3.16.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 29 16:31:47 2015 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2015-09-28 (0 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1501049 Title: totem crashed with assertion failure [Totem:ERROR:totem- grilo.c:729:browse_cb: code should not be reached] Status in totem package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/49f61eb5b4c7c242dac2179ff053a937285c37ce --- the gnome video application crashed twice while attempting to browse a upnp media server. at first I tried to play a video which failed to play, then twice afterwards the application crashed before it would even load the file list --- $ LANGUAGE=C totem Click 'Channels' Click 'DLNA-Server' Click 'Photos' Click 'All Photos' In console: ** Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Bail out! Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Abortado (`core' generado) ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: totem 3.16.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 29 16:31:47 2015 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2015-09-28 (0 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1501049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1501049] Re: totem crashed with assertion failure [Totem:ERROR:totem-grilo.c:729:browse_cb: code should not be reached]
** Description changed: https://errors.ubuntu.com/problem/49f61eb5b4c7c242dac2179ff053a937285c37ce --- the gnome video application crashed twice while attempting to browse a upnp media server. at first I tried to play a video which failed to play, then twice afterwards the application crashed before it would even load the file list + + --- + + $ LANGUAGE=C totem + Click 'Channels' + Click 'ServerDLNA' + Click 'Photos' + Click 'All Photos' + + In console: + ** + Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached + Bail out! Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached + Abortado (`core' generado) ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: totem 3.16.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 29 16:31:47 2015 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2015-09-28 (0 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1501049 Title: totem crashed with assertion failure [Totem:ERROR:totem- grilo.c:729:browse_cb: code should not be reached] Status in totem package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/49f61eb5b4c7c242dac2179ff053a937285c37ce --- the gnome video application crashed twice while attempting to browse a upnp media server. at first I tried to play a video which failed to play, then twice afterwards the application crashed before it would even load the file list --- $ LANGUAGE=C totem Click 'Channels' Click 'ServerDLNA' Click 'Photos' Click 'All Photos' In console: ** Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Bail out! Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Abortado (`core' generado) ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: totem 3.16.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 29 16:31:47 2015 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2015-09-28 (0 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1501049/+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 1839782] Re: totem crashed with SIGABRT
*** This bug is a duplicate of bug 1501049 *** https://bugs.launchpad.net/bugs/1501049 ** Description changed: $ LANGUAGE=C totem Click 'Channels' - Click 'MyCloudEX2Ultra' + Click 'ServerDLNA' Click 'Photos' Click 'All Photos' In console: ** Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Bail out! Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Abortado (`core' generado) ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: totem 3.33.90-2ubuntu1 Uname: Linux 5.2.8-050208-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 16:06:29 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (252 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: totem Signal: 6 SourcePackage: totem StacktraceTop: - () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - () at /usr/lib/x86_64-linux-gnu/libtotem.so.0 - () at /usr/lib/x86_64-linux-gnu/libgrilo-0.3.so.0 - g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + () at /usr/lib/x86_64-linux-gnu/libtotem.so.0 + () at /usr/lib/x86_64-linux-gnu/libgrilo-0.3.so.0 + g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: totem crashed with SIGABRT UpgradeStatus: Upgraded to eoan on 2018-12-02 (252 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1839782 Title: totem crashed with SIGABRT Status in totem package in Ubuntu: New Bug description: $ LANGUAGE=C totem Click 'Channels' Click 'ServerDLNA' Click 'Photos' Click 'All Photos' In console: ** Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Bail out! Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Abortado (`core' generado) ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: totem 3.33.90-2ubuntu1 Uname: Linux 5.2.8-050208-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 16:06:29 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (252 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: totem Signal: 6 SourcePackage: totem StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libtotem.so.0 () at /usr/lib/x86_64-linux-gnu/libgrilo-0.3.so.0 g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: totem crashed with SIGABRT UpgradeStatus: Upgraded to eoan on 2018-12-02 (252 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1839782/+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 1839545] [NEW] Graphic environment slows down and then returns to normal
Private bug reported: After updating the mesa, the management of my graphic environment is no longer as fluid. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libegl-mesa0 19.1.4-1ubuntu1 Uname: Linux 5.2.7-050207-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 8 16:46:39 2019 DistUpgraded: 2018-12-02 16:59:40,473 DEBUG inhibit gnome-session idle DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.10, 5.2.7-050207-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:8486] InstallationDate: Installed on 2018-12-02 (249 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.7-050207-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to eoan on 2018-12-02 (249 days ago) dmi.bios.date: 04/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.1.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan regression single-occurrence ubuntu wayland-session ** Information type changed from Public to Private -- 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/1839545 Title: Graphic environment slows down and then returns to normal Status in mesa package in Ubuntu: New Bug description: After updating the mesa, the management of my graphic environment is no longer as fluid. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libegl-mesa0 19.1.4-1ubuntu1 Uname: Linux 5.2.7-050207-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 8 16:46:39 2019 DistUpgraded: 2018-12-02 16:59:40,473 DEBUG inhibit gnome-session idle DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.10, 5.2.7-050207-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:8486] InstallationDate: Installed on 2018-12-02 (249 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.7-050207-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to eoan on 2018-12-02 (249 days ago) dmi.bios.date: 04/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri:
[Desktop-packages] [Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path Status in Nautilus: Unknown Status in gtk+3.0 package in Ubuntu: New Status in nautilus package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/nautilus/issues/1190 --- https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1726129/+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 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1190 https://gitlab.gnome.org/GNOME/nautilus/issues/1190 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/1190 Importance: Unknown Status: Unknown -- 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/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/nautilus/issues/1190 --- https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1726129/+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 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
** Description changed: + https://gitlab.gnome.org/GNOME/nautilus/issues/1190 + + --- + https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- 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/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path Status in nautilus package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/nautilus/issues/1190 --- https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726129/+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 1839211] Re: Upgrade to 2.2.1-1
** Attachment added: "Captura de pantalla de 2019-08-06 16-20-51.png" https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1839211/+attachment/5281307/+files/Captura%20de%20pantalla%20de%202019-08-06%2016-20-51.png ** Summary changed: - Upgrade to 2.2.1-1 + Upgrade to 2.2.1-1(Debian) ** Summary changed: - Upgrade to 2.2.1-1(Debian) + Please upgrade to 2.2.1-1(Debian) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1839211 Title: Please upgrade to 2.2.1-1(Debian) Status in tracker package in Ubuntu: New Bug description: I am testing gnome-music [0]night, and request tracker version 2.2.0 or higher. [0] https://wiki.gnome.org/Apps/Music/Resources ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.1.8-2 Uname: Linux 5.2.6-050206-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 16:10:43 2019 InstallationDate: Installed on 2018-12-02 (247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1839211/+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 1839211] [NEW] Upgrade to 2.2.1-1(Debian)
Public bug reported: I am testing gnome-music [0]night, and request tracker version 2.2.0 or higher. [0] https://wiki.gnome.org/Apps/Music/Resources ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.1.8-2 Uname: Linux 5.2.6-050206-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 16:10:43 2019 InstallationDate: Installed on 2018-12-02 (247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago) ** Affects: tracker (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan upgrade-software-version wayland-session ** Description changed: - I am testing gnome-music night, and request tracker version 2.2.0 or - higher. + I am testing gnome-music [0]night, and request tracker version 2.2.0 or higher. + [0] https://wiki.gnome.org/Apps/Music/Resources ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.1.8-2 Uname: Linux 5.2.6-050206-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 16:10:43 2019 InstallationDate: Installed on 2018-12-02 (247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1839211 Title: Upgrade to 2.2.1-1(Debian) Status in tracker package in Ubuntu: New Bug description: I am testing gnome-music [0]night, and request tracker version 2.2.0 or higher. [0] https://wiki.gnome.org/Apps/Music/Resources ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.1.8-2 Uname: Linux 5.2.6-050206-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 16:10:43 2019 InstallationDate: Installed on 2018-12-02 (247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1839211/+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 1832869] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call()
** Tags added: eoan -- 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/1832869 Title: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call() Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell-extension-dashtodock package in Ubuntu: Invalid Status in mutter package in Ubuntu: Won't Fix Status in mutter source package in Bionic: In Progress Status in mutter source package in Disco: Won't Fix Bug description: [ Description ] GNOME shell crashes on restart when some window actors are opened [ Test case ] - Run gnome-shell in Xorg, start some windows - Hit Alt+F2 - Write 'r' and press Enter - The shell should restart without crashing in meta_workspace_list_windows [ Regression potential ] Javascript errors might be emitted when trying to access to invalidated data, but nothing really harmful. [ Note ] This crash doesn't affect versions after 3.28 for various reasons: - The JS code triggering it isn't there anymore - MetaScreen doesn't exist anymore. Similar crashes might happen in newer versions, but as per different code paths, and so to be reported as different bugs. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/d3f9725b7fae2763643521acfc58c734f829dd64 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. https://errors.ubuntu.com/problem/ac8df0b1e2d67e423c634fde1a3acecd3c381d58 https://errors.ubuntu.com/problem/d3f9725b7fae2763643521acfc58c734f829dd64 https://errors.ubuntu.com/problem/1e69eadeb69f4e2b8aa933205d2be3a8db4af36c https://errors.ubuntu.com/problem/6f7810166a3ae02cc8025514d6ffbbde10063e76 https://errors.ubuntu.com/problem/1bfbc00c70cfe6f4f2b66b4efc86f5c089c28680 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832869/+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 1837546] Re: totem assert failure: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1837546 Title: totem assert failure: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. Status in totem package in Ubuntu: New Bug description: Moving forward and backward a 4k movie. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: totem 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AssertionMessage: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Tue Jul 23 08:28:51 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (232 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7f6a9e64fd5f , assertion=0x7f6a46a39ba4 "0", file=0x7f6a4672ecd0 "gen9_mfd.c", line=649, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f6a46a39ba4 "0", file=0x7f6a4672ecd0 "gen9_mfd.c", line=649, function=0x7f6a4672f3e0 "gen9_hcpd_get_reference_picture_frame_id") at assert.c:101 () at /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so () at /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so () at /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so Title: totem assert failure: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. UpgradeStatus: Upgraded to eoan on 2018-12-02 (232 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1837546/+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 1603324] Re: file-roller crashed with SIGSEGV in confirmation_dialog_response()
** Tags added: eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1603324 Title: file-roller crashed with SIGSEGV in confirmation_dialog_response() Status in file-roller package in Ubuntu: Confirmed Bug description: Error after unzip a file. It seems to have unzipped it correctly though ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: file-roller 3.20.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13 Uname: Linux 4.4.0-30-generic x86_64 ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 15 14:53:45 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/file-roller InstallationDate: Installed on 2012-11-25 (1328 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627) ProcCmdline: file-roller --extract-here --notify file:///home/username/aaa/bbb/ccc/ddd.zip file:///home/username/aaa/bbb/ccc/eee.zip ProcEnviron: LANGUAGE=en_SG:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_SG.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: file-roller StacktraceTop: ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: file-roller crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to yakkety on 2015-03-14 (488 days ago) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1603324/+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 1825981] Re: /usr/lib/tracker/tracker-extract:6:mem_error:slab_allocator_free_chunk:magazine_cache_trim:magazine_cache_push_magazine:thread_memory_magazine2_unload
** Tags added: eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1825981 Title: /usr/lib/tracker/tracker- extract:6:mem_error:slab_allocator_free_chunk:magazine_cache_trim:magazine_cache_push_magazine:thread_memory_magazine2_unload Status in tracker package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding tracker. This problem was most recently seen with package version 2.1.6-1, the problem page at https://errors.ubuntu.com/problem/b99e01aacdc0c848c2170270ddbb577546a03a73 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825981/+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 1836070] Re: seahorse crashed with signal 5
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1836070 Title: seahorse crashed with signal 5 Status in seahorse package in Ubuntu: Invalid Bug description: I just opened the application and it froze. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: seahorse 3.32-1 Uname: Linux 5.2.0-050200rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 10 10:17:19 2019 ExecutablePath: /usr/bin/seahorse InstallationDate: Installed on 2018-12-02 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/seahorse --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 5 SourcePackage: seahorse StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XGetRequest () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XShmCreatePixmap () at /usr/lib/x86_64-linux-gnu/libXext.so.6 Title: seahorse crashed with signal 5 UpgradeStatus: Upgraded to eoan on 2018-12-02 (219 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1836070/+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 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
This still happens in eoan. ** Changed in: nautilus (Ubuntu) Status: Expired => 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/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path Status in nautilus package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726129/+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 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no screens found") from dix_main()
** Tags added: eoan
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1543192
Title:
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("no screens found") from dix_main()
Status in xorg-server package in Ubuntu:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530
---
No idea what happened.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core 2:1.17.3-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CrashCounter: 1
Date: Mon Feb 8 17:07:23 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics
Controller [17aa:21da]
InstallationDate: Installed on 2015-04-30 (283 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 429149G
ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic
root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0
panic=-1
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
OsAbort ()
?? ()
FatalError ()
?? ()
__libc_start_main (main=0x557f8180ff00, argc=11, argv=0x7fffc9e34fd8,
init=, fini=, rtld_fini=,
stack_end=0x7fffc9e34fc8) at libc-start.c:289
SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit
code 2:
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/18/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET46WW (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 429149G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 429149G
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.66-2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20160127-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
xserver.bootTime: Mon Feb 8 17:08:14 2016
xserver.configfile: default
xserver.errors: systemd-logind: failed to get session: PID 9847 does not
belong to any known session
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 728
vendor LGD
xserver.version: 2:1.17.3-2ubuntu2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192/+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 1614143] Re: gedit (11) update_actions_sensitivity → readonly_changed → g_closure_invoke → signal_emit_unlocked_R → g_signal_emit_valist
** Tags added: eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1614143 Title: gedit (11) update_actions_sensitivity → readonly_changed → g_closure_invoke → signal_emit_unlocked_R → g_signal_emit_valist Status in gedit: Confirmed Status in gedit package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gedit. This problem was most recently seen with version 3.18.3-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/e5cc28cceb18cc41c0015180e3af7c0bc3186364 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1614143/+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 1748563] Re: /usr/bin/eog:11:gtk_tree_model_get_valist:gtk_tree_model_get:is_file_in_list_store:is_file_in_list_store_file:file_monitor_changed_cb
** Tags added: eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1748563 Title: /usr/bin/eog:11:gtk_tree_model_get_valist:gtk_tree_model_get:is_file_in_list_store:is_file_in_list_store_file:file_monitor_changed_cb Status in Eye of GNOME: New Status in eog package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding eog. This problem was most recently seen with package version 3.26.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/2e739466ac6b0cecc40e58fd7ec888752657ccdf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1748563/+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 1834367] Re: nautilus crashed with SIGSEGV in gtk_places_sidebar_set_drop_targets_visible()
** Description changed: - https://gitlab.gnome.org/GNOME/nautilus/issues/1082 - - --- - - I was moving movies from one directory to another directory. + I was moving movies from one directory to another directory with mouse. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.32.1-1ubuntu1 Uname: Linux 5.1.15-050115-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 26 15:49:12 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-12-02 (206 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7f1f91d44914 :mov0xe8(%rdi),%eax PC (0x7f1f91d44914) ok source "0xe8(%rdi)" (0x00e8) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: gtk_places_sidebar_set_drop_targets_visible () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in gtk_places_sidebar_set_drop_targets_visible() UpgradeStatus: Upgraded to eoan on 2018-12-02 (205 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: -- 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/1834367 Title: nautilus crashed with SIGSEGV in gtk_places_sidebar_set_drop_targets_visible() Status in Nautilus: Unknown Status in nautilus package in Ubuntu: New Bug description: I was moving movies from one directory to another directory with mouse. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.32.1-1ubuntu1 Uname: Linux 5.1.15-050115-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 26 15:49:12 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-12-02 (206 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7f1f91d44914 :mov0xe8(%rdi),%eax PC (0x7f1f91d44914) ok source "0xe8(%rdi)" (0x00e8) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: gtk_places_sidebar_set_drop_targets_visible () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in gtk_places_sidebar_set_drop_targets_visible() UpgradeStatus: Upgraded to eoan on 2018-12-02 (205 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1834367/+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 1834367] Re: nautilus crashed with SIGSEGV in gtk_places_sidebar_set_drop_targets_visible()
** Information type changed from Private to Public ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1082 https://gitlab.gnome.org/GNOME/nautilus/issues/1082 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/1082 Importance: Unknown Status: Unknown ** Description changed: + https://gitlab.gnome.org/GNOME/nautilus/issues/1082 + + --- + I was moving movies from one directory to another directory. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.32.1-1ubuntu1 Uname: Linux 5.1.15-050115-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 26 15:49:12 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-12-02 (206 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANGUAGE=es_CL:es - LANG=es_CL.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANGUAGE=es_CL:es + LANG=es_CL.UTF-8 SegvAnalysis: - Segfault happened at: 0x7f1f91d44914 :mov0xe8(%rdi),%eax - PC (0x7f1f91d44914) ok - source "0xe8(%rdi)" (0x00e8) not located in a known VMA region (needed readable region)! - destination "%eax" ok + Segfault happened at: 0x7f1f91d44914 :mov0xe8(%rdi),%eax + PC (0x7f1f91d44914) ok + source "0xe8(%rdi)" (0x00e8) not located in a known VMA region (needed readable region)! + destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: - gtk_places_sidebar_set_drop_targets_visible () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 - () - g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + gtk_places_sidebar_set_drop_targets_visible () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 + () + g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in gtk_places_sidebar_set_drop_targets_visible() UpgradeStatus: Upgraded to eoan on 2018-12-02 (205 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: - + usr_lib_nautilus: -- 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/1834367 Title: nautilus crashed with SIGSEGV in gtk_places_sidebar_set_drop_targets_visible() Status in Nautilus: Unknown Status in nautilus package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/nautilus/issues/1082 --- I was moving movies from one directory to another directory. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.32.1-1ubuntu1 Uname: Linux 5.1.15-050115-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 26 15:49:12 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-12-02 (206 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7f1f91d44914 :mov0xe8(%rdi),%eax PC (0x7f1f91d44914) ok source "0xe8(%rdi)" (0x00e8) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: gtk_places_sidebar_set_drop_targets_visible () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in gtk_places_sidebar_set_drop_targets_visible() UpgradeStatus: Upgraded to eoan on 2018-12-02 (205 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1834367/+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 1826918] Re: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay() from detach_pixmap() from meta_surface_actor_x11_dispose() from g_object_unref() from g_object_
** Tags added: bionic -- 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/1826918 Title: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay() from detach_pixmap() from meta_surface_actor_x11_dispose() from g_object_unref() from g_object_unref() Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.32.0+git20190410-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/1a5d1f99fd9215f7a79b718d2e915c675ebcd69f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1826918/+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 1774587] Re: nautilus crashes in recent_thread_func -> is_file_valid_recursive -> g_local_file_query_info -> free(): invalid pointer
Thanks for your work! -- 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/1774587 Title: nautilus crashes in recent_thread_func -> is_file_valid_recursive -> g_local_file_query_info -> free(): invalid pointer Status in nautilus package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.3-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Similar crash in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1638389 Trace at: https://bugzilla.redhat.com/attachment.cgi?id=1492907 https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9 https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 https://errors.ubuntu.com/problem/43301aeee406cdbd57ba7d571ff838f0340d72a2 https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 https://errors.ubuntu.com/problem/7e550b34e134ed57f0684a8c554e3219191cd7f9 Similar but related to this thread (so likely the same issue): https://errors.ubuntu.com/problem/b0ad24ee4008e11e2adf5d14b6b0463e14aa8637 https://errors.ubuntu.com/problem/cec510782baf291622cd2bdd5a3761d27d587523 https://errors.ubuntu.com/problem/a829a6947498ae1bc279781b820f2409238af3a0 https://errors.ubuntu.com/problem/5ac15513eba57b72b1b09bafc448ffa1a7f3aa7f https://errors.ubuntu.com/problem/c3b2e8a30a1ccdd23e1155f0c0067a89dea5eb6a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774587/+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
