Hi,
is there a bug I can subscribe to?
... resolved, thanks
If you have hit this and you still have the system live, you
should be able to find the X crash in abrt and report it.
now that's the interesting part - I got abrt reports just for lxqt
components, but not X itself
in dmesg, the events around the crash look like:
[263728.985192] thinkpad_acpi: EC reports that Thermal Table has changed
[263729.086435] nouveau 0000:01:00.0: DRM: resuming kernel object tree...
[263729.773945] nouveau 0000:01:00.0: devinit: 0x64da[0]: script needs
connector type
[263729.855794] nouveau 0000:01:00.0: DRM: resuming client object trees...
[263729.855883] nouveau 0000:01:00.0: DRM: resuming display...
[263729.855906] nouveau 0000:01:00.0: DRM: resuming console...
[263730.500358] show_signal_msg: 177 callbacks suppressed
[263730.500360] trojita[3202]: segfault at 7fbbac0ce980 ip 00007fbbc1d1b583
sp 00007ffdb015fe60 error 4 in libQt5Gui.so.5.7.0[7fbbc1bb1000+489000]
[263730.565213] traps: lxqt-globalkeys[1359] general protection
ip:7f74c978a375 sp:7ffdf9b9c500 error:0 in
libc-2.24.so[7f74c9750000+1bd000]
[263730.570483] lxqt-runner[1368]: segfault at 20 ip 00007fd77f401ab4 sp
00007ffe06acb760 error 6 in libQt5Core.so.5.7.0[7fd77f363000+477000]
[263730.574903] lxqt-panel[1364]: segfault at 7f8ceb64fab0 ip
00007f8cf447eff3 sp 00007ffd409942d0 error 4 in
libQt5Core.so.5.7.0[7f8cf4206000+477000]
[263730.740922] lxqt-session[1169]: segfault at 7faea01d8ab0 ip
00007faea8ac5ff3 sp 00007ffe49685980 error 4 in
libQt5Core.so.5.7.0[7faea884d000+477000]
[263730.740963] Pid 1169(lxqt-session) over core_pipe_limit
[263730.740963] Skipping core dump
[263730.925284] wlp3s0: deauthenticating from d0:72:dc:01:14:ae by local
choice (Reason: 3=DEAUTH_LEAVING)
[263730.969754] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[263736.678436] nouveau 0000:01:00.0: DRM: suspending console...
[263736.678439] nouveau 0000:01:00.0: DRM: suspending display...
[263736.678456] nouveau 0000:01:00.0: DRM: evicting buffers...
[263736.680332] nouveau 0000:01:00.0: DRM: waiting for kernel channels to
go idle...
[263736.680357] nouveau 0000:01:00.0: DRM: suspending client object
trees...
[263736.685955] nouveau 0000:01:00.0: DRM: suspending kernel object tree...
[263737.915140] thinkpad_acpi: EC reports that Thermal Table has changed
first trace in journal is:
říj 03 09:44:19 kvolny qterminal-qt5[3840]: The X11 connection broke: I/O
error (code 1)
- it looks like X simply exited, not crashed
but that should rather go to Bugzilla ...
/me goes to play with the reproducer
Otherwise, at least run 'dnf update' in a VT -
hit ctrl-alt-f3 to get a VT console login prompt, log in, and do it
there. Don't do it inside your desktop.
or better (IMHO) - run it using `screen` ;-)
I think whether that's better or not depends on exactly how the
screen/tmux server process was run...
not sure what do you mean?
I don't use tmux, but as for screen, a little experiment ... running it I
get something like:
17795 ? Rl 8:23 /usr/bin/qterminal-qt5
17798 pts/0 Ss 0:00 \_ /bin/bash
17845 pts/0 S 0:00 | \_ su -
17853 pts/0 S 0:00 | \_ -bash
13178 pts/0 S+ 0:00 | \_ screen
13179 ? Ss 0:00 | \_ SCREEN
13180 pts/10 Ss 0:00 | \_ /bin/bash
17837 pts/10 R+ 0:00 | \_ ps xfa
let's do something nasty - just cut the screen's branch using `xkill` on
the qterminal; then the above is reduced to:
13179 ? Ss 0:00 SCREEN
13180 pts/10 Ss+ 0:00 \_ /bin/bash
- the big SCREEN (and the shell running under it) still surviving, I can
reattach and see the previous action:
[root@kvolny ~]# xkill
Select the window whose client you wish to kill with button 1....
xkill: killing creator of resource 0x2200005
K.
--
Karel Volný
BaseOS QE - Daemons
Red Hat Czech, Brno
tel. +420 532294274
(RH: +420 532294111 ext. 8262074)
:: "Never attribute to malice what can
:: easily be explained by stupidity."
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
