kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #142279
[Bug 1509839] Re: segfault on start of live session in kactivitymanager / libqt5sql
Looks like the nouveau driver is involved in this somehow. Having a
screenshot likely means at some point (when the cpu lockup is detected)
there is an automatic switch to vt#1. Is it at that point possible to
use alt+f2 (for example) to get to another text login screen and still
login there (life iso user ubuntu and just enter for password). The
other thing to try might be to interrupt the isolinux boot when the
icons on the lower part of the screen appear with esc and then use
nomodeset from the f6 menu. That only gives very low resolution but
maybe gets to the live session.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1509839
Title:
segfault on start of live session in kactivitymanager / libqt5sql
Status in linux package in Ubuntu:
Incomplete
Bug description:
I've installed 15.10 Wily Werewolf to my USB stick via usb-creator and restart the laptop
on boot, I'm asked for the language and if I want to install or try a live session
I select try life session, the dialog disappears and the machine is frozen
Next try:
boot to selection dialog
switch to console crtl+alt+F1 (takes a moment)
issue alt+syreq+1 and alt+sysreq+t ... both answer "operation is disabled"
switch back to X ctrl+alt+F7 & click try live session
immediately switch back to console ctrl+alt+F1
watchdog detects hard lockup a few seconds later
see attached screenshot
reproduced also in beta1 of wily werewolf ... a month ago I imagine
the beta was still starting, as for bug #1492840. But I've reformated
the stick meanwhile and cannot really guarantee, that I didn't confuse
the multiple ISO's I tried in short time.
version information:
kernel 4.2.0-16-generic #19-Ubuntu (4.1.0-3-generic #3-Ubuntu)
libqt5sql.so 5.4.2 (both)
currently running Kubuntu 15.04 on the same hardware
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509839/+subscriptions
References