[Bug 1542519] Re: Double menu bar
Running 16.04 in 2 different machines, one of which is affected by the bug and the other not. I prefer to stay with Xenial since I admin a few family systems and the workload reduces over time with Xenial now in caretaker mode. Each was installed at different times, the unaffected one having been installed almost from the first stable release and having been regularly updated, the affected one having been installed a few weeks ago from an iso saved about 2 years ago and updated at install and regularly since. The unaffected machine is a 14 inch Clevo laptop with i3 onboard graphics "Broadwell GT1", no special driver noted. The affected machine is an ASRock mini hybrid desktop affair with i5 onboard graphics "HD Graphics 530 (Skylake GT2)", no special driver noted. Both are running the same official package 2.2.2-5ubuntu0.16.04.4 Thanks to rtimai's work on this bug, I've given the user a simple shortcut to restart the Unity session - per comment 14 https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1542519/comments/14 This is a small burden for such a great version as Xenial with unity has been. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1542519 Title: Double menu bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1542519/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779476] Re: Boot process hangs indefinitely. Never finishes.
Further to the above on wireless start, booting into *.23 kernel, Bionic loses all the retarding symptoms for Gnome start and for wireless network start. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1779476 Title: Boot process hangs indefinitely. Never finishes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779476] Re: Boot process hangs indefinitely. Never finishes.
Installing plymouth 0.9.3-3 over the distro 0.9.3-1 had no effect on this system - amd64 - either. Steps taken with dpkg for a hash-checked .deb were: Preparing to unpack .../plymouth_0.9.3-3_amd64.deb ... Unpacking plymouth (0.9.3-3) over (0.9.3-1ubuntu7) ... Setting up plymouth (0.9.3-3) ... update-initramfs: deferring update (trigger activated) update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Processing triggers for systemd (237-3ubuntu10) ... Processing triggers for ureadahead (0.100.0-20) ... ureadahead will be reprofiled on next reboot Processing triggers for man-db (2.8.3-2) ... Processing triggers for initramfs-tools (0.130ubuntu3.1) ... update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic Apt complained about some redundancies, which I deleted. After uninstalling haveged, the system hung indefinitely once more at various advices of processes waiting, depending on the 3 restarts I tried. GDM featured variously, as did utmp. Not knowing much at that level, I can only report that plymouth 0.9.3-3 doesn't fix the hang I reported upthread. Nor does it change the lack of either keyboard or usb mouse/touchpad access for at least 90s of that hang. Another symptom, just noticed because of all the restarts, is that wireless networking gets a significant delay before kicking in after the handover to Gnome - about 30s. With the 16.04 I dual boot this machine to, wireless networking is ready to go almost as soon as the UI is up. Reinstalling haveged returns the good handover to Gnome - about 20s, but wireless networking stays slow to begin its work. Note that uninstalling plymouth 0.9.3-3 returns the listing of 0.9.3-1 to the system, but a couple of the Ubuntu display dependencies needed also to be reinstalled to get back a coherent recognisable splash screen progress. Probably time for me to get familiar with using the shell at startup. That UI looks like a real curate's egg and this is a significant bug (or set of bugs maybe). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1779476 Title: Boot process hangs indefinitely. Never finishes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779476] Re: Ubuntu 18.04: gdm3 does not switch to graphics after update
I can report a very similar experience after the update to kernel *-24. The difference with my machine - a barebook Clevo packaged by Pioneer Computers Australia - is that no keyboarding, usb mouse, or touchpad use reproducably reduces the hang time by plymouth to less than an average 90seconds. The appearance of the cursor is fairly unpredictable within those times and at a rare few boots, CTRL+ALT F2 sent the system into a wobbly dance between the shell and plymouth. Holding SHIFT during boot however does produce an acceptable and reproducable boot into Xorg time of about 15s. Installing and enabling haveged in sysctrl has the same effect as holding the SHIFT key. Booting into the *-23 kernel removes the hang and any of the wobbly moves between shell and plymouth. As requested, after uninstalling haveged and booting to *-24 kernel, both using the SHIFT workaround and the longer playing with keyboard and pointers, issuing the command: lsof | grep /dev/random listed nothing. Interesting that with sudo prefixed, the command complains: 'lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete.' While it doesn't complain when the user themself issues the command. Is this a bug too, or is it logical that the virtual gnome file system is indeed run per user and not by root? Neither forms of the command list anything. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1779476 Title: Ubuntu 18.04: gdm3 does not switch to graphics after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
