[Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation
I have three screens: 1) nVidia GTX 970M HDMI port of laptop. 1920x1080 2) USB-C, Thunderbolt III HDMI dongle. 3840x2160 3) Laptop eDP1 (i7 6700HQ, HD 530 iGPU). 1920x1080 Upon resume the 3840x2160 screen's wallpaper is **OK**. The two 1920x1080 screens wallpaper is all white. Ubuntu 16.04.6 LTS upgrade direct to 19.04 w/kernel 5.0.0-23 yesterday. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1809407/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753884] Re: session logout after suspend
This happens to me periodically with Ubuntu 16.04.6 LTS, Kernel 4.14.114. External HDMI 1080p TV nVidia GTX 970M driven External HDMI 4K TV i915 Thunderbolt3 USB-C driven Internal Dell 1080p LCD i915 driven Method: 1) close laptop lid with power & systemd set to "do nothing" 2) external monitors will disconnect (no signal) and have to move mouse to reconnect. 3) select GUI suspend from external monitor 4) power off external screens after system suspends 5) power on external screens 6) open laptop lid to resume 7) about 20% of time login screen appears and all work is lost If fixed in 17.10 would be nice to see backported to 16.04 as current plans for upgrade aren't until 20.04. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1753884 Title: session logout after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753884/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1587154] Re: --working-directory does not work anymore
This bug has been fixed for Ubuntu 16.04.3 LTS running under Kernel 4.14.34-generic: $ gnome-terminal --working-directory=/tmp Opens a new terminal window with `/tmp` the current directory as expect. -- 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/1587154 Title: --working-directory does not work anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1587154/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759462] Re: Keyboard shortcuts not operational on 18.04
Reply to #8, problem seems to have gone away on it's own today. Had tried multiple DE's that didn't work and went into Unity. A message that "Updates are available" appeared. Clicking on it installed nothing but probably ran `sudo apt update`, `sudo apt upgrade` in the background. Rebooted into 16.04. Later rebooted into 18.04 test environment and `Ctrl`+`Alt`+`T` and media keys are working. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1759462 Title: Keyboard shortcuts not operational on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1759462/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759462] Re: Keyboard shortcuts not operational on 18.04
Like #3 I also have the Logitech K800 wireless keyboard. - Ctrl+Alt+T doesn't open terminal must use Dash and select gnome-terminal - Alt+PrintScreen doesn't open screen-shot must use Dash and select Screenshot - Media keys don't work Resorting to laptop's keyboard (Alienware 17 R3) Ctrl+Alt+T doesn't work either. Ubuntu 16.04 upgraded to Ubuntu 18.04 (luckily in test environment). Answered Y to half a dozen prompts to convert login.d, sane, network and others to new configuration format. Only declined not to update /etc/default/grub to new configuration format. Signed in with Unity under Xorg. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1759462 Title: Keyboard shortcuts not operational on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1759462/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1575484] Re: "Set document metadata failed"
You get this error when elevating privileges to root using sudo, gksu or pkexec. Further you can't set default tab stops, tabs to spaces, font, it doesn't return to last save position and the entire top line menu dissappears. I'm curious whether creating an account called "root" will setup configuration files for gedit to save to??? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1575484 Title: "Set document metadata failed" To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1575484/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1582496] Re: GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup
Just received a similar message Ubuntu 16.04 using YAD (Yet Another Dialog): (yad:8401): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ^^^ Appears about 20 times. I was in the process of adding new columns of icons to existing dialog box matching mime file types. Not sure exactly which code revisions caused the error though. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1582496 Title: GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1582496/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1506704] Re: Thin font, nautilus doesn't integrate with Unity.
That's good to know. I now have Startup Applications loading (which also causes a delay) and thin fonts haven't appeared in a long time. I thought they had fixed the bug. Thank you for the update! On Mon, Oct 3, 2016 at 10:17 AM, Alfred Cavigelli < 1506...@bugs.launchpad.net> wrote: > I had a freshly installed Ubuntu 16.01.1 with same issues (thin fonts). > The issue appeared with auto login only. Now I defined a auto-login-delay > of 1 second and it works fine. > To define the delay open the file "/etc/lightdm/lightdm.conf" and edit the > line "autologin-user-timeout=1". > > $ sudo nano /etc/lightdm/lightdm.conf > > autologin-user-timeout=1 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1506704 > > Title: > Thin font, nautilus doesn't integrate with Unity. > > Status in gnome-settings-daemon package in Ubuntu: > Confirmed > > Bug description: > It happens frequently (around 1/2 of the time) that when I boot the > computer, font lines are only one pixel thick. This concerns watch in > the sys-tray, all item in the menu of all applications, as well as all > fonts in Nautilus. When this happens. Nautilus doesn't display menu in > the Unity menu bar, but displays an additional button showing three > horizontal lines for bringing up the menu. > > This problem has been with me for years, although sometimes disappears > for months at a time when I run sudo apt-get update. This time it re- > emerged after upgrading to 15.10 beta (Wily). It happens usually on > power-up, and disappears after system restart. (To appear again on the > next power-up). > > ProblemType: Bug > DistroRelease: Ubuntu 15.10 > Package: nautilus 1:3.14.2-0ubuntu12 > ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 > Uname: Linux 4.2.0-16-generic x86_64 > ApportVersion: 2.19.1-0ubuntu2 > Architecture: amd64 > CurrentDesktop: Unity > Date: Fri Oct 16 04:53:31 2015 > GsettingsChanges: > > InstallationDate: Installed on 2015-10-08 (7 days ago) > InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) > SourcePackage: nautilus > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-settings- > daemon/+bug/1506704/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1506704 Title: Thin font, nautilus doesn't integrate with Unity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1506704/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1506704] Re: Thin font, nautilus doesn't integrate with Unity.
NB This is more than a Nautilus issue because like others the Unity bar is now clearer (before it was hard to read). Conky is now clearer. Google chrome is noticeably clearer and scrolling is smooth when it used to be choppy. The pixel breaks / line cracks when scrolling in Chrome have disappeared. Should this be reclassified as a critical bug with Linux Kernel / systemd as a whole and not just Nautilus? I had just upgraded to Ubuntu 16.04 Kernel 4.4 then 4.6.3 when the Nautilus font became an issue and led me to this thread. But even under Ubuntu 14.04 / Kernel 3.13 there were problems which I'll try to recreate / eliminate with the USB plugged in / not plugged in during boot. As far as "3) Bluetooth Earbuds" in post #23 we must eliminate that off the list because it's on a Y-Cable with the smartphone and only the smartphone gets data comm + power, whereas the Earbuds are power only. Watson the game is afoot. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1506704 Title: Thin font, nautilus doesn't integrate with Unity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1506704/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1506704] Re: Thin font, nautilus doesn't integrate with Unity.
Can confirm now that simply unplugging the USB powered hub and rebooting fixes the Nautilus 1 pixel font problem. Another problem where the built-in display was black and only the TV got wallpaper was also fixed. Plugging the USB hub in after boot did not break Nautilus fonts. On the hub are: 1) UPS battery status monitor 2) Smartphone 3) Blue tooth ear buds 4) Laser Printer 5) Couple of spare cables -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1506704 Title: Thin font, nautilus doesn't integrate with Unity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1506704/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1506704] Re: Thin font, nautilus doesn't integrate with Unity.
Unfortunately the solution in #21 is not permanent and you have to repeat it after reboot. More investigation is needed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1506704 Title: Thin font, nautilus doesn't integrate with Unity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1506704/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1506704] Re: Thin font, nautilus doesn't integrate with Unity.
I had same problems with Nautilus. Something to do with MS ttf fonts. The solution for me was to open terminal and type: fc-cache -rv Then log out and log back in. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1506704 Title: Thin font, nautilus doesn't integrate with Unity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1506704/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
