Rebooting from GUI takes a long time/icons and menus go white

[Bednar]

Rebooting from GUI takes a long time/icons and menus go white. Sudo reboot works fine. The same is true for shutting the machine down.

If you require anything let me know what to run and I will copy paste the results.

Thanks,

B

[gravy45 (gravy45)]

I have seen this before, where the icons you were using change into a really old-style? I've always thought it had to do with a stuck process or possibly the X session crashed. If you can press ctrl-alt-backspace when it is doing it, log right back in after the session resets, then try to shutdown right away, then you might be able to rule out it is happening all the time.

If you could install 'inxi' and run:
$ inxi -Fx

Then at least you will have posted all the system details.

[Bednar (bednarczyk-pawel)]

Hi,

>I have seen this before, where the icons you were using change into a really old-style?

Yup, that right.

>If you can press ctrl-alt-backspace when it is doing it, log right back in after the session resets, then try to shutdown right away, >then you might be able to rule out it is happening all the time.

I'll do that and post back.

In the meantime, here's the output from inxi -Fx

bednar@bednar-PC:~$ inxi -Fx
System: Host: bednar-PC Kernel: 4.1.2-040102-generic x86_64 (64 bit gcc: 4.8.4)
           Desktop: N/A Distro: Ubuntu 15.04 vivid
Machine: System: Gigabyte product: N/A
           Mobo: Gigabyte model: Z77-D3H v: x.x
           Bios: American Megatrends v: F23b date: 01/06/2014
CPU: Quad core Intel Core i5-3570K (-MCP-) cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 27225
           clock speeds: max: 3800 MHz 1: 1626 MHz 2: 1682 MHz 3: 1659 MHz
           4: 1634 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] Pitcairn XT [Radeon HD 7870 GHz Edition]
           bus-ID: 01:00.0
           Display Server: X.Org 1.17.1 drivers: ati,radeon (unloaded: fbdev,vesa)
           Resolution: 1920x1200@60.0hz
           GLX Renderer: Gallium 0.4 on AMD PITCAIRN
           GLX Version: 3.0 Mesa 10.7.0-devel (git-ad2c390 2015-07-11 vivid-oibaf-ppa) Direct Rendering: Yes
Audio: Card-1 Intel 7 Series/C210 Series Family High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 Advanced Micro Devices [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series]
           driver: snd_hda_intel bus-ID: 01:00.1
           Card-3 C-Media CM108 Audio Controller
           driver: USB Audio usb-ID: 006-004
           Sound: Advanced Linux Sound Architecture v: k4.1.2-040102-generic
Network: Card: Qualcomm Atheros AR8161 Gigabit Ethernet
           driver: alx port: d000 bus-ID: 05:00.0
           IF: eth0 state: up speed: 100 Mbps duplex: full
           mac: 90:2b:34:5c:be:65
Drives: HDD Total Size: 5622.6GB (28.3% used)
           ID-1: USB /dev/sda model: Expansion_Desk size: 4000.8GB
           ID-2: /dev/sdb model: Samsung_SSD_840 size: 120.0GB
           ID-3: /dev/sdc model: SAMSUNG_HD103UJ size: 1000.2GB
           ID-4: /dev/sdd model: ST3500320AS size: 500.1GB
           ID-5: USB /dev/sdf model: Internal_Storage size: 1.4GB
Partition: ID-1: / size: 12G used: 9.1G (81%) fs: ext4 dev: /dev/sdb3
           ID-2: /home size: 36G used: 3.7G (11%) fs: ext4 dev: /dev/sdb4
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 29.8C mobo: 27.8C gpu: 31.0
           Fan Speeds (in rpm): cpu: N/A
Info: Processes: 210 Uptime: 2:06 Memory: 1107.4/7940.5MB
           Init: systemd runlevel: 5 Gcc sys: 4.9.2
           Client: Shell (bash 4.3.301) inxi: 2.2.16

Thanks,

B

[gravy45 (gravy45)]

Have you always had the issue, since a fresh install, or did it occur after you went to the 4.1 kernel and that development version of Mesa 10.7? Both are unsupported under Ubuntu MATE, not that they couldn't work but that's the official word. Have you looked in /var/log/syslog to compare what messages are recorded at the time of that long shutdown? It may give you an idea of what was going on at the time.

[Bednar (bednarczyk-pawel)]

I have always had this issue - even on the kernel and config that ships default with Ubuntu Mate. I found the culprit. It's mate-panel. I removed it from required components in session in dconf editor and installed cairo dock. Everything appears to work fine now.

I didn't see anything meaningful in syslog but I am newb so I could have missed it.

Now the file is overwhelming and I am not sure how to extract the relevant parts.

[gravy45 (gravy45)]

I meant just look at the timeframe between the initiation of shutdown to when it actually shutdown.

[Anton (an-lar)]

I can reproduce that problem consistently when I'm trying to shutdown/reboot with launched quiterss.

But now that you've mentioned mate-panel I've tried do disable tray icon in quiterss and was able to reboot without delay.

[Bednar (bednarczyk-pawel)]

Well, I now have moved on to a different distribution but unless quietrss was installed by default, I didn't have it on my system.

[Bednar (bednarczyk-pawel)]

alright, I am back to Ubuntu Mate and this behavior is back. To reproduce 100% of the time, I leave steam open and then reboot from the GUI.

I will try to see what syslog logs and post back.

[gravy45 (gravy45)]

Obviously if you close Steam and don't ever get it, then it has to do with Steam exiting or a process that is part of it. Systemd gives processes time to exit gracefully. I don't know much about Steam but it could be updating (a game server?) during that time.

You may or may not see enough detail in syslog. Might even be able to get away with just hitting escape as you wait to reboot, and if you consistently see a process named like steam (at shutdowns) then you know that is it.

Or, you can modify /etc/systemd/system.conf to contain these two lines uncommented.
LogLevel=debug
LogTarget=syslog-or-kmsg

Then review syslog but it will be more verbose.

[Launchpad Janitor (janitor)]

[Expired for ubuntu-mate because there has been no activity for 60 days.]