cphite wrote:Completely unrelated but seems to fit the thread... has anyone else noticed Chrome becoming much less responsive since the last update? I am still running Kubuntu 14.04 64-bit (not sure how much difference that makes) and ever since Chrome updated to version 51.x I'm seeing a lot of delays in various functionality. For example, if I click on the "other bookmarks" button it's often taking several seconds to open, or when navigating the tools menu it's occasionally lagging when trying to open various sub-menus.
And if so, any ideas on how to resolve?
It's always been pretty snappy in the past.
cheesyking wrote:I haven't noticed anything like that with chrome but it has been causing other problems for me... quite often it refuses to exit gracefully when I shut the computer down which is extremely annoying as means a shutdown now takes about 90 seconds (IIRC that's how long systemd on ubuntu give a process to exit before killing it.) Doesn't do it every time and so long as I remember to close all my chrome windows first I don't have to worry.
PenGun wrote:Ah the joys of just killing X to go somewhere. I could not live without AltCtrlBackspace myself. Boom it's gone,
PenGun wrote:and my command line understands R means reboot and H means stop. Yeah I'm crazy, been root for decades. The user in /home is just to make Chrome run.
cphite wrote:Still mostly a n00b with this Linux stuff, so I have another question that'll probably make most of you roll your eyes, but whatever..
So... I have an oldish Dell desktop that I decided to use in my workout room... Basically just something to watch DVDs, YouTube, or listen to music, etc.
I installed Mint 18 and everything seemed to be fine, machine has been running for a few weeks now. Last night I got a bunch of updates including the kernel so I did those, and everything still seemed fine - and then I rebooted, er rather tried to reboot.
I get past the disk encryption password, it starts booting up and then right before it gets to the login screen, it crashes and I get a page of text that ends with "Kernel Panic" and something about the kernel being out of sync. My best guess is that something about the new kernel just isn't playing nice with my 10 year old hardware.
So how do I go about rolling back? I've rolled back on systems where I can at least boot up, but in this case I can't even get logged into it...
just brew it! wrote:Issues like that really suck. Try switching to the first virtual console (Ctrl-Alt-F1) as soon as you initiate the shutdown. There may be some clues in the messages it spews there.
Aside from that, my recommendation would be to wait and see if the next kernel update fixes it, or revert to the previous kernel... unless you're interested in going down a potentially bottomless rabbit hole.
Chuckaluphagus wrote:The 4.15.0-30 kernel showed up in system updates yesterday, and it's not showing any problems, so whatever that was appears to have been fixed.
cphite wrote:I get past the disk encryption password, it starts booting up and then right before it gets to the login screen, it crashes and I get a page of text that ends with "Kernel Panic" and something about the kernel being out of sync. My best guess is that something about the new kernel just isn't playing nice with my 10 year old hardware.
Glorious wrote:Chuckaluphagus wrote:The 4.15.0-30 kernel showed up in system updates yesterday, and it's not showing any problems, so whatever that was appears to have been fixed.
That's weird though, because that was just a CVE fix for a TCP DoS.
just brew it! wrote:Sounds like it.
If you hadn't wiped, it might've been easy to try going back to the previous kernel (since there's a good chance it was still present on the OS disk, just not being selected at boot).
At this point, I'd say your options are:
A) Live with it (initiate the shutdown, and when it gets stuck, hold down the power button to turn off the power). Wait and see if a future update fixes it.
B) Install a previous version that doesn't have the issue.
C) Go down the rabbit hole and start Googling for anyone else who is reporting similar issues on similar hardware, and see what turns up. The solution could be as simple as tweaking a hidden setting somewhere, or it might be complicated. Depending on your tolerance level for tinkering, you may not reach the bottom of the rabbit hole until you're compiling device drivers and/or OS kernels from source...