Thank you for taking the time, 3rods, to report this bug and helping to make Ubuntu better.
Please open a new bug, indicating the bug number of this one in it. The hard part is to get the crash info. KernelTeamBugPolicie suggest: "If the bug report involves a crash, it is hoped that a kernel backtrace (aka OOPS, kernel panic) is available. If the machine does not completely lockup from the crash, the backtrace should be available in the dmesg output. If the crash completely locks the system, try rebooting to a known working kernel and see if any backtrace was logged to /var/log/kern.log.0 . Please attach this file if anything was captured. If all else fails, supply a digital photo of the screen to capture the crash." In your case, you could also try VPN not from gnome-terminal, but from console (Ctrl-Alt-F1). console shows kernel info, and hopefully crash info. Include the following additional information (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team: 1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture. 2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report. 3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report. For your reference, the full description of procedures for kernel- related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance! -- CAPS LOCK LED STARTS BLINKING AND THE NOTEBOOK CRASH (KDE?) (PCI: Bus #04 (-#07) is hidden behind transparent bridge #03 ) https://bugs.launchpad.net/bugs/129500 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
