Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#35100 - [gnome-shell] desktop freezes partially (segfault)
Attached to Project:
Arch Linux
Opened by Michael Pusterhofer (feanor12) - Sunday, 05 May 2013, 11:21 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Wednesday, 12 March 2014, 15:28 GMT
Opened by Michael Pusterhofer (feanor12) - Sunday, 05 May 2013, 11:21 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Wednesday, 12 March 2014, 15:28 GMT
|
DetailsAll except the mouse cursor freezes. using gnome3(shell)
Did a restart via ssh and it worked. dmesg: [ 1969.557939] gnome-shell[833]: segfault at 1 ip 00007f585d34d7d0 sp 00007fffa7005a28 error 4 in libglib-2.0.so.0.3600.1[7f585d315000+fc000] [ 1971.737838] systemd-journald[126]: Failed to write entry, ignoring: Argument list too long [ 7053.517776] Uhhuh. NMI received for unknown reason 3d on CPU 0. [ 7053.517781] Do you have a strange power saving mode enabled? [ 7053.517782] Dazed and confused, but trying to continue journalctl: Mai 05 12:39:21 michael-arch kernel: Uhhuh. NMI received for unknown reason 3d on CPU 0. Mai 05 12:39:21 michael-arch kernel: Do you have a strange power saving mode enabled? Mai 05 12:39:21 michael-arch kernel: Dazed and confused, but trying to continue CPU from dmesg: CPU0: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz (fam: 06, model: 17, stepping: 0a) [ 0.109913] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter. |
This task depends upon
Closed by Gerardo Exequiel Pozzi (djgera)
Wednesday, 12 March 2014, 15:28 GMT
Reason for closing: No response
Wednesday, 12 March 2014, 15:28 GMT
Reason for closing: No response
Comment by Gerardo Exequiel Pozzi (djgera) -
Wednesday, 12 February 2014, 03:10 GMT
- Field changed: Status (Assigned → Waiting on Response)
- Field changed: Category (Packages: Extra → Upstream Bugs)
status? upstream report?