Since today Ubuntu 20.04.1 LTS stopped waking up after being suspended by the closing of my laptop's lid, just showing a blank screen. I've tried lots of differents solutions, from modifying some GRUB arguments values to changing lid behavior on systemd's logind.conf file, but none of them seemed to work. Then I remembered that I updated Linux kernel version 5.4.0.56 earlier today, so I checked to see if the same problem ocurred with version 5.4.0.54. And well, it didn't, with version 5.4.0.54 suspension seeming to work properly still, given that the notebook woken up correctly and that I was able to have access to my laptop again after logging in. For that I ask how could I report a Linux Kernel issue to its developers, because I'm quite convinced that this a kernel related issue, given that changing the kernel version used solved this issue.
4237
I found a problem with an application on Ubuntu.   Questions :   How do I best report the issue?  What sort of information should I provide?
88384
Did a fresh install of Ubuntu 17.10 a few days ago on my Lenovo Thinkpad Edge (using an existing home directory on a different partition).  When I close the lid and put it to sleep, on waking it I can no longer login. Sometimes it spends ages checking the password, then says the password is wrong. Sometimes I can't even enter anything into the password box. To fix this I have to shut down and restart. Login always works fine on a restart.  Any help?
97926
I have a , with Ubuntu 16.04 installed.  I have recently (today) updated it(not upgraded), and afterwards it asked for a reboot, so I did that. However, after reboot it showed the login screen and mentioned connection established (for internet through Ethernet), and login password cursor was blinking during that time but after that even the cursor stopped blinking and accepting no response from keyboard or mouse. Only one option is to force shutdown. I have no idea what part of the update resulted in this.   Everything was working fine before the update. Once the Ethernet icon announcing connection has been established goes away, it takes away the blinking of the cursor, then keyboard and mouse simply won't work. I even tried connecting keyboard on other slots, but no success. Can I uninstall the last update?  NOTE:  I heard a sound from the processor when login screen comes and in between the cursor also blinks, but once this sound is over then the blinking freezes and you have to forcibly shutdown, as this is an institute computer (I took the admin privilege, headache). Now I am  really worried about it. How to fix it?  IMPROVEMENT  I did not have to go for a live USB, and I was able to go to grub I was able to go to the GRUB menu by pressing the Esc key). This what I got.      I have no idea how to go about it after that. It is saying Secure boot forbids loading module, while loading Ubuntu I did secure boot by entering a password for that.
58702
I accidentally clicked on the option "When power is critically low" under System Settings>Power. The original entry was blank, but the only two options after I clicked were Hibernate and Shutdown. I want to set it back to Suspend.
7513
A few days ago my MacBook Pro slipped out of my hands and fell onto the tile floor. The outside got banged up quite a bit and the Touch Bar no longer lights up but still responds to touches sometimes but not all the time.   Anyway, since then it will randomly restart every once in a while with a kernel panic. I have the log posted below and wanted to know if anyone could tell me what is causing the panic?
44518
I am experienced the following issue: after hibernation (using command sudo systemctl hibernatein a terminal or the menu on the right top of Ubuntu desktop) I get a black screen (Even though all devices seem to work. The fan works!) and I am forced to reboot the OS because resume failed and I can't back to a "saved state". The content in etc/polkit-1/localauthority/50-local.d/com.ubuntu.enable-hibernate.pkla is:      [Re-enable hibernate by default in upower] Identity=unix-user:* Action=org.freedesktop.upower.hibernate ResultActive=yes  [Re-enable hibernate by default in logind] Identity=unix-user:* Action=org.freedesktop.login1.hibernate;org.freedesktop.login1.handle-hibernate-key;org.freedesktop.login1;org.freedesktop.login1.hibernate-multiple-sessions;org.freedesktop.login1.hibernate-ignore-inhibit ResultActive=yes   Additional info: Ubuntu version: 16.04LTS  Kernel version:   uname -r 4.13.0-26-generic   Graphic info:   udo lspci | grep -E 'VGA|Display' [sudo] password di michele:  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6730M/6770M/7690M XT] (rev ff) michele@michele-ubuntu:~$ sudo lshw -c display | grep driver        configuration: driver=i915 latency=0   CPU info:  sudo lscpu [sudo] password di michele: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 42 Model name: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz Stepping: 7 CPU MHz: 1995.561 CPU max MHz: 2900,0000 CPU min MHz: 800,0000 BogoMIPS: 3991.12 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 6144K NUMA node0 CPU(s): 0-7 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm epb pti tpr_shadow vnmi flexpriority ept vpid xsaveopt dtherm ida arat pln pts   Why does the resuming fail?  Thanks in advance for your help.
57961
The problem When I boot Ubuntu 11.10, the boot process hangs, before even getting to the login screen of the display manager, with the message   Could not write bytes: broken pipes   at the top of the screen, followed by some lines of text (where one yellow star left of "PulseAudio" is - don't know if this is important...), the last being       * Stopping System V runlevel compatability                                          [Ok]    After that I can only press Ctrl+Alt+Del to reboot.  The cause The problem occured after I did an update on feb., the 18th. In the process of the update a window popped up in which I had to choose the default display manager. Being in a hurry, I just clicked "ok" (gdm was the default selection in that window). Afterwards I found out that Ubuntu 11.10 us es lightdm so I figured, that maybe this was the cause of my problem. Before this update everything worked fine.  {What I tried so far to do to fix it [skip this, if its too long] I logged in as root in recovery mode and tried to reinstall lightdm. Using the apt-get command I get error that spans over 3 lines of text, the first of which is  Not using locking for read only lock file /var/lib/dpkg/lock;   but I don't know of any process that is using apt-get, that is preventing it from being run.  After that I used  dpkg-reconfigure lightdm  and selected lightdm as the default display manager. This exited with the line   mv: cannot move 'etc/X11/default-display-manager' to '/etc/X11/default-display-manager.pdkg-tmp': Read-only file system".   When I then booted in normal mode it still hung, but the message Could not write bytes: broken pipes was gone, there were just two lines of text, the first said something about the battery state and the last was identical to the one above ("* Stopping System V[...]"). I played around a little bit by also trying dpkg-reconfigure gdm and choosing gdm instead of lightdm, but none of that helped. The system still hangs, just with different lines of text showing up, but "* Stopping System V[...]" is always the last one. }  Other info This may be or not be relevant: I use multiple operating systems (the other ones work) and the kernel I use is 3.0.0-15-generic-pae.  Please help, I invested so much time in setting my Ubuntu system up, I don't want to do it all over again.
1975
All operating systems freeze sometimes, and Ubuntu is no exception. What should I do to regain control when...   just one program stops responding? nothing at all responds to mouse clicks or key presses? the mouse stops moving entirely? I have an    In what order should I try various solutions before deciding to pull the power plug?  What should I do when starting up Ubuntu fails?  Is there a diagnostic procedure I can follow?
86056
I tried to post to this thread  for if I understand their question I am having the same problem, but the answer option won't work for.  After suspend, the wireless is disconnected and the only way to get it to reinitialize/be recognized is to do a full restart.  At first I thought it was my gnome-shell (for lock screen disappeared there with 13.10), but when I switched to the default Ubuntu it's still doing it and it's kinda driving me nuts for I have to reopen all my files and browsers/tabs/windows every time. I don't know how to show the terminal stuff the above asker shows, but it sounds like the same issue and it only started with 13.10 upgrade a few days ago.   Any help would be much appreciated!!! -- Thanks so much, ser.
102908
Since one or two months ago, my laptop with ubuntu 12.10x64 hangs during shutdown. There's just a black screen, no harddisk activity, it justs sits there. I feel it happens near the end of a normal shutdown cycle, judging from time elapsed.  Only resolution is hard power-off (holding power key for several seconds) - neither Ctrl-Alt-Backspace (which normally works, I have it switched on in Settings) nor Ctrl-Alt-Del help, nor can I get into a text console with Ctrl-Alt-F1.   How do I diagnose that? It does not happen on every shutdown, but often enough to be annoying (as it forces a diskcheck on reboot, of course).   Which log files can tell me what's going wrong? More or less blindly searching in the sys log viewer reminds me of needles in a haystack.  I imagine I could pinpoint the time it happens via log timestamps, but how do I read timestamps like e.g. in kern.log: [36169.146130]? How do I get this human-readable?  Lastly, a bit of a btw, I've never managed to execute an Alt-Sysrq-REISUB to force a cleaner shutdown, but that's probably because I'm on a laptop, PrintScr is only accessible via an Fn key, and I'm not sure of the exact key sequence I need. Is there a "harmless" but user-visible magic command I could practice this with (during normal operation), so I can find out how to do a REISUB next time?  Thanks all! Comment if you need additional data...
63990
Dell LAtitude E6430 with CPU Intel® Core™ i5-3210M, 64 bits, no longer boots after updating 14.04 LTS system to kernel 3.13.0-66. It hangs off after completion of the password. Back to the 3.13.0-64 kernel works, but still with a system error, pending since about the beginning of the year (beginning approximately for the kernel 3.13.0-40) and never corrected by subsequent upgrades. It seems that the system 14.04 LTS is going worse and worse on this computer. Is there a solution ?
36853
I have a PC that has a Windows 8 partition and an Ubuntu 13.04 partition.  I am trying to get wake-on-lan to work.  Everything works fine on the Windows 8 partition: I can wake-on-lan from both the sleep state and the shutdown state. However, when I shutdown Ubuntu using:  sudo shutdown -h now   I cannot wake the PC through my LAN. Is this because the network interface is getting turned off? What command can I use or how can I reconfigure Ubuntu so that wake-on-lan still works?  Also, if I do not use the -h option in the shutdown command, the PC does not actually shutdown; it just freezes up on me.  Using ethtool, I found that it says:  Supports Wake-on: pumbg Wake-on: g ... Link detected: yes   My etc/network/interfaces says this:  auto eth0 iface eth0 inet dhcp       up ethtool -s eth0 wol g   EDIT: I have found that if I shut down the PC by simply holding the power button, then wol works. If I shutdown using the command line or through the Ubunutu GUI, then it does not work. So I think the issue is not that it is not being setup properly, but that something is overriding it or shutting it off when I shut down properly. Are there are any scripts that get run at shutdown?  I have added  NETDOWN=no   to both etc/default/halt and etc/init.d/halt
39430
When my computer blanks the screen after the timeout (10 minutes) or after I turn off the monitors and turn them back on some time later, I only see a black screen with the mouse pointer. I can move the mouse pointer, but nothing else happens.  I am able to switch to the console with Ctrl + Alt + F3 and then switching back to the display with Ctrl + Alt + F1 gives me the login screen. But after logging in, I get the same problem.  Restarting gdm3 from the console does not seem to help. It gets stuck initializing and then I have to hard shutdown. The only thing that works is to restart the machine from the console, but that is annoying.  Has anyone else experienced this problem or have any ideas on how to fix this?  My machine is Ubuntu 18.04 with the 4.15.0-32-generic kernel.
87149
I'm quite positive that this used to work flawlessly in 19.04 (and past releases) but no longer does after a release-upgrade to 19.10 (kernel 5.3.0-24, ThinkPad X1 Carbon gen 5 in case this matters).  I have the corresponding switch set in GNOME-Tweaks and have also attempted to manually edit /etc/systemd/logind.conf as suggested , namely uncomment and adjust the following lines, followed by a reboot:  $ grep -v '^#' /etc/systemd/logind.conf [Login] HandleLidSwitch=suspend HandleLidSwitchExternalPower=suspend HandleLidSwitchDocked=suspend LidSwitchIgnoreInhibited=yes   (strictly speaking, only the first one ought to be required but, just in case, I also added lines 2 &amp; 3, as well as #4 for good measure...  Looking at the output of systemctl status systemd-logind, I see the following:  Dec 17 17:56:50 x1c5 systemd-logind[8959]: Lid closed. Dec 17 17:57:03 x1c5 systemd-logind[8959]: Lid opened.   So the lid events are correctly detected.  To rule out any issue with the suspend process itself, I have also set my power button to suspend in Settings->Power->Suspend &amp; Power Button, for testing purposes.  Pressing the power button now results in this in the output of systemctl status systemd-logind (after a successful suspend-resume cycle):  Dec 17 18:13:58 x1c5 systemd-logind[8959]: Power key pressed. Dec 17 18:14:28 x1c5 systemd-logind[8959]: Delay lock is active (UID 121/gdm, PID 9215/gsd-power) but inhibitor timeout is reached. Dec 17 18:14:39 x1c5 systemd-logind[8959]: Operation 'sleep' finished.   Bottom line: lid events are detected correctly and suspend works flawlessly - but not on lid close...  Any idea how I can get the suspend on lid-close feature back to life?  I can of course use the workaround with the power button but it's a little too easy to forget and result in laptop overheating in bag etc...  --- edited to add ---  Got a little further courtesy of , although the issue isn't the exactly as described.  Here's a smoking gun:  $ systemd-inhibit --list --mode=block WHO       UID  USER      PID  COMM           WHAT                                                     WHY                                                         MODE  gdm       121  gdm       2231 gsd-power      handle-lid-switch                                        External monitor attached or configuration changed recently block gdm       121  gdm       2252 gsd-media-keys handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling keypresses                                   block user      1000 user      3017 gsd-media-keys handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling keypresses                                   block   This suggests that the lid close action is being blocked because "External monitor attached or configuration changed recently".  I do connect my laptop to a monitor using a USB-C cable but as I write this, it's been undocked and running on batteries for nearly 3 hours (GNOME settings only shows my laptop display as available).  However it looks like systemd or whichever component is responsible for this still incorrectly believes the external display is attached and - per the ticket - suspend isn't supported by GNOME in such scenarios...  Interestingly the gsd-power process (PID 2231) is owned by gdm rather than my UID.  Killing it restores the suspend-on-lid-close functionality.  Need to figure out why this process exists... When actually connected to external display, systemd-inhibit --list --mode=block reports a 2nd gsd-power process owned by the interactive user; which appears correct and sufficient.
100282
I am asking for a help or a fix for this black screen in Ubuntu 15.04.  The black screen contains the message starting version 219 and I am stuck in there for like a day already. Been trying to find a fix in Google but failed. So far I tried fixing it by going into the terminal using commands like:  sudo systemctl enable sddm.service -f   This command dint go through, because I don't have sddm in my system, so it failed. Next thing is, I found out, that my sddm was a lightdm, so I tried using  sudo systemctl enable lightdm.service -f    …and same result, but this time, it got a message, that it is not meant to be activated through systemctl. Lastly I tried this one:  systemctl start lightdm   This goes in. After putting my password, it went through, but it went back to the black screen. Tried hitting the shift key, when I rebooted it, but it didn't work.
107982
When I close the lid of my laptop, the computer shuts down immediately and won't power on again. I need to take a screwdriver and disconnect-reconnect the battery in order to make it power on.  I really want Linux to ignore the lid switch.  I already tried a lot of answers on stack overflow but none works. What I tried:   Put HandleLidSwitch=ignore in /etc/systemd/logind.conf systemd-inhibit --what=handle-lid-switch sleep 1d cat /etc/systemd/logind.conf | grep -i lid does throw nothing Put IgnoreLid=true in /etc/UPower/UPower.conf systemctl unmask sleep.target suspend.target /etc/acpi/lid.sh does not exist In gconf-editor, in apps &gt; gnome-power-manager &gt; buttons, set lid_ac and lid_battery to nothing   I reboot my computer after changing those config files to be sure all services are restarted.  How is this possible? What could I try next in order to make the lid switch be ignored?  I'm using Ubuntu with Cinnamon.
42249
I installed Ubuntu on my Windows 7 Sager laptop using Wubi. Hibernate (i.e. suspend to disc) is not an option from the power icon, only suspend, shutdown, etc. Hibernate is also not an option from my battery/lid close options. I understand that hibernation is disabled by default in Ubuntu 12.04. I tried running pm-hibernate but I get the following message:  Looking for splash system... none  s2disk: Snapshotting system   and then the computer just hangs with a black screen. According to the documentation  if this fails then I can't enable hibernate but it offers no help in making pm-hibernate succeed.  Could swap be my problem? It looks like I have very small swap:  user@ubuntu:~$ cat /proc/swaps Filename                Type        Size    Used    Priority /host/ubuntu/disks/swap.disk            file        262140  0   -1   The advice on  is only for the author's set up (e.g. I don't have an Ubuntu install disk since I used Wubi) and he says that 'INFO: This will not work for 12.04, resume from hibernate work differently in 12.04.'  Any advice? I really need to get hibernate working to use my laptop as a, er, laptop.  Thanks