[Ubuntu-x-swat] [Bug 2013071] Re: Session crash after initial login
Looks like Sean was right - removing libva-wayland2 and then rebooting resolved the issue. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2013071 Title: Session crash after initial login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2013071/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2013071] Re: Session crash after initial login
I can't reproduce this on Ubuntu MATE (though I can make other things crash sadly). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2013071 Title: Session crash after initial login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2013071/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2013071] Re: Session crash after initial login
Interestingly, I'm not getting any XFCE-related crashes when I use
gnome-boxes rather than QEMU. The process that is crashing is actually
X.
I got a backtrace from it:
(gdb) bt -full
#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=)
at ./nptl/pthread_kill.c:44
tid =
ret = 0
pd =
old_mask = {__val = {0}}
ret =
pd =
old_mask =
ret =
tid =
ret =
resultvar =
resultvar =
__arg3 =
__arg2 =
__arg1 =
_a3 =
_a2 =
_a1 =
__futex =
resultvar =
__arg3 =
__arg2 =
__arg1 =
_a3 =
_a2 =
_a1 =
__futex =
__private =
__oldval =
#1 __pthread_kill_internal (signo=6, threadid=)
at ./nptl/pthread_kill.c:78
No locals.
#2 __GI___pthread_kill (threadid=, signo=signo@entry=6)
at ./nptl/pthread_kill.c:89
No locals.
#3 0x7f39b123c406 in __GI_raise (sig=sig@entry=6)
at ../sysdeps/posix/raise.c:26
ret =
#4 0x7f39b122287c in __GI_abort () at ./stdlib/abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0x20, sa_sigaction = 0x20},
sa_mask = {__val = {0 }}, sa_flags = 67108868,
sa_restorer = 0x7f39b123c4b0 <__restore_rt>}
#5 0x558075c86b60 in OsAbort () at ../../../../os/utils.c:1352
No locals.
#6 0x558075c8c319 in AbortServer () at ../../../../os/log.c:879
No locals.
#7 0x558075c8d359 in FatalError (
f=f@entry=0x558075cbee90 "Caught signal %d (%s). Server aborting\n")
at ../../../../os/log.c:1017
args = {{gp_offset = 24, fp_offset = 48,
overflow_arg_area = 0x7ffd9edeb5a0,
reg_save_area = 0x7ffd9edeb4d0}}
args2 = {{gp_offset = 8, fp_offset = 48,
overflow_arg_area = 0x7ffd9edeb5a0,
reg_save_area = 0x7ffd9edeb4d0}}
beenhere = 1
#8 0x558075c83ddc in OsSigHandler (unused=,
sip=, signo=6) at ../../../../os/osinit.c:156
No locals.
#9 OsSigHandler (signo=6, sip=, unused=)
at ../../../../os/osinit.c:110
No locals.
#10
No locals.
#11 __pthread_kill_implementation (no_tid=0, signo=6, threadid=)
at ./nptl/pthread_kill.c:44
tid =
ret = 0
pd =
old_mask = {__val = {139885759425152}}
ret =
pd =
old_mask =
ret =
tid =
ret =
resultvar =
resultvar =
__arg3 =
__arg2 =
__arg1 =
_a3 =
_a2 =
_a1 =
__futex =
resultvar =
__arg3 =
__arg2 =
__arg1 =
_a3 =
_a2 =
_a1 =
__futex =
__private =
__oldval =
#12 __pthread_kill_internal (signo=6, threadid=)
at ./nptl/pthread_kill.c:78
No locals.
#13 __GI___pthread_kill (threadid=, signo=signo@entry=6)
at ./nptl/pthread_kill.c:89
No locals.
#14 0x7f39b123c406 in __GI_raise (sig=sig@entry=6)
at ../sysdeps/posix/raise.c:26
ret =
#15 0x7f39b122287c in __GI_abort () at ./stdlib/abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0x20, sa_sigaction = 0x20},
sa_mask = {__val = {94010244971792, 110, 0, 139885763323770, 0,
49245412224, 0, 140727268852584, 15975794021409362944, 5,
18446744073709550696, 11, 94010220322512, 122, 94010220302986,
94010220853328}}, sa_flags = -1322649741,
sa_restorer = 0x7f39b13b677a <_nl_C_name>}
#16 0x7f39b122279b in __assert_fail_base (
fmt=0x7f39b13b9f68 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
assertion=assertion@entry=0x558075c9528a "key->initialized",
file=file@entry=0x558075c99ed0 "../../../../../../include/privates.h",
line=line@entry=122,
function=function@entry=0x558075cb9580 <__PRETTY_FUNCTION__.7>
"dixGetPrivateAddr") at ./assert/assert.c:92
str = 0x55807741bd10 "\273\2238/\205U"
total = 4096
#17 0x7f39b1233b86 in __assert_fail (
assertion=assertion@entry=0x558075c9528a "key->initialized",
file=file@entry=0x558075c99ed0 "../../../../../../include/privates.h",
line=line@entry=122,
function=function@entry=0x558075cb9580 <__PRETTY_FUNCTION__.7>
"dixGetPrivateAddr") at ./assert/assert.c:101
No locals.
#18 0x558075c3ba25 in dixGetPrivateAddr (
key=0x558075d57020 , privates=0x71)
at ../../../../../../include/privates.h:122
__PRETTY_FUNCTION__ = "dixGetPrivateAddr"
#19 0x558075c3dd25 in dixGetPrivateAddr (key=,
privates=) at ../../../../../../include/privates.h:167
__PRETTY_FUNCTION__ = "dixGetPrivateAddr"
#20 dixLookupPrivate (key=, privates=)
at ../../../../../../include/privates.h:165
No locals.
#21 DRI2Authenticate (client=client@entry=0x558077415b80,
pScreen=, magic=1)
at ../../../../../../hw/xfree86/dri2/dri2.c:1365
[Ubuntu-x-swat] [Bug 2013071] Re: Session crash after initial login
And there's more random crashes. (xiccd being the next one to go kaput) All of this in a pure QEMU VM. My guess is xfce4-power-manager crashes thanks to GLib and that takes down other stuff at random. Not sure how that would be triggered by the third-party software option, but that's what I'm seeing here. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2013071 Title: Session crash after initial login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2013071/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2013071] Re: Session crash after initial login
Hmm, and now xfce4-power-manager. Looking at the stacktrace when xfce4-power-manager goes awry, it's GLib's fault. Which means we probably have another slice allocator removal causing problems. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2013071 Title: Session crash after initial login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2013071/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2013071] Re: Session crash after initial login
I notice a blueman-applet crash when I reproduce this. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2013071 Title: Session crash after initial login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2013071/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2006408] Re: nvidia-uvm module does not exist, making CUDA unusable with the 390 driver
** Description changed: Notice: I have not reproduced this bug myself, nor do I have the needed setup to reproduce this bug. This is a bug report based on info provided to me over IRC. - In order for CUDA compute to work, a kernel module "nvidia-uvm" is - necessary. This module *should* exist in the headless NVIDIA 390 driver. - However, it apparently does not exist - it does not show up in the - output of "lsmod", attempting to modprobe it fails, doing a recursive - grep on /lib/modules/$(uname -r) does not reveal it, and it appears that - the Installable Client Driver is not loading correctly. + In order for CUDA or OpenCL compute to work, a kernel module "nvidia- + uvm" is necessary. This module *should* exist in the headless NVIDIA 390 + driver. However, it apparently does not exist - it does not show up in + the output of "lsmod", attempting to modprobe it fails, doing a + recursive grep on /lib/modules/$(uname -r) does not reveal it, and it + appears that the Installable Client Driver is not loading correctly. From my own personal experience, I know that nvidia-uvm *does* exist in recommended driver for an NVIDIA 1050 Ti card, however the 390 driver used with the GTX 570 card does not appear to have the driver, even though the card supports CUDA. ** Summary changed: - nvidia-uvm module does not exist, making CUDA unusable with the 390 driver + nvidia-uvm module does not exist, making CUDA and OpenCL unusable with the 390 driver -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2006408 Title: nvidia-uvm module does not exist, making CUDA and OpenCL unusable with the 390 driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2006408/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2006408] Re: nvidia-uvm module does not exist, making CUDA unusable with the 390 driver
strace of "clinfo -l" from the machine of the affected user. ** Attachment added: "clinfo_strace.log" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2006408/+attachment/5645158/+files/clinfo_strace.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2006408 Title: nvidia-uvm module does not exist, making CUDA unusable with the 390 driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2006408/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2006408] [NEW] nvidia-uvm module does not exist, making CUDA unusable with the 390 driver
Public bug reported: Notice: I have not reproduced this bug myself, nor do I have the needed setup to reproduce this bug. This is a bug report based on info provided to me over IRC. In order for CUDA compute to work, a kernel module "nvidia-uvm" is necessary. This module *should* exist in the headless NVIDIA 390 driver. However, it apparently does not exist - it does not show up in the output of "lsmod", attempting to modprobe it fails, doing a recursive grep on /lib/modules/$(uname -r) does not reveal it, and it appears that the Installable Client Driver is not loading correctly. >From my own personal experience, I know that nvidia-uvm *does* exist in recommended driver for an NVIDIA 1050 Ti card, however the 390 driver used with the GTX 570 card does not appear to have the driver, even though the card supports CUDA. ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2006408 Title: nvidia-uvm module does not exist, making CUDA unusable with the 390 driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2006408/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1855220] Re: xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry)
(all those "no longer affects" is me figuring out what I'm doing with Launchpad bug management and changing my mind about pressing a button, please disregard) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1855220 Title: xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-default-settings/+bug/1855220/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1855220] Re: xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry)
** Tags added: lunar ** Also affects: xserver-xorg-video-nouveau (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: lubuntu-default-settings (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: xserver-xorg-video-nouveau (Ubuntu Lunar) Importance: Undecided Status: Confirmed ** Also affects: lubuntu-default-settings (Ubuntu Lunar) Importance: Low Assignee: Aaron Rainbolt (arraybolt3) Status: In Progress ** No longer affects: lubuntu-default-settings (Ubuntu Kinetic) ** No longer affects: xserver-xorg-video-nouveau (Ubuntu Kinetic) ** No longer affects: xserver-xorg-video-nouveau (Ubuntu Lunar) ** No longer affects: lubuntu-default-settings (Ubuntu Lunar) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1855220 Title: xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-default-settings/+bug/1855220/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1855220] Re: xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry)
** Also affects: lubuntu-default-settings (Ubuntu) Importance: Undecided Status: New ** Changed in: lubuntu-default-settings (Ubuntu) Assignee: (unassigned) => Aaron Rainbolt (arraybolt3) ** Changed in: lubuntu-default-settings (Ubuntu) Importance: Undecided => Low ** Changed in: lubuntu-default-settings (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1855220 Title: xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-default-settings/+bug/1855220/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1855220] Re: xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry)
Interesting. For me, the problem is easily reproducible on an Acer Chromebook C720 with a 2nd gen Intel Celeron with an Intel iGPU. And I *think* (though can't remember for sure) that this happens on a Compaq laptop around here with an AMD iGPU. All of these with single screens. So I don't think it can be NVIDIA-specific. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1855220 Title: xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1855220/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1855220] Re: xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry)
I've noticed this problem also on slower systems of mine (an Acer Chromebook C720 for instance). This leads me to believe that system speed (or perhaps graphics subsystem speed?) is the culprit here, as other systems work with flurry just fine. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1855220 Title: xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1855220/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1983000] Re: IDK
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1983000 Title: IDK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1983000/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1983001] Re: IDK
*** This bug is a duplicate of bug 1983000 *** https://bugs.launchpad.net/bugs/1983000 Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** This bug has been marked a duplicate of bug 1983000 IDK -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1983001 Title: IDK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1983001/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1983002] Re: IDK
*** This bug is a duplicate of bug 1983000 *** https://bugs.launchpad.net/bugs/1983000 Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** This bug has been marked a duplicate of bug 1983000 IDK -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1983002 Title: IDK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1983002/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
