[Desktop-packages] [Bug 1435020] Re: Custom Shortcut keybindings does not work
*** This bug is a duplicate of bug 1755106 *** https://bugs.launchpad.net/bugs/1755106 I am also experiencing this on Ubuntu 18.04 when I use Unity with the Nvidia drivers. It seems to work fine when I use gnome. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1435020 Title: Custom Shortcut keybindings does not work Status in Ubuntu GNOME Flashback: New Status in unity-settings-daemon package in Ubuntu: Triaged Bug description: System Settings -> Keyboard -> Shortcuts -> Custom Shortcuts Click the add button (the one with the plus symbol). Write a name such as "gsm". Write a command such as "gnome-system-monitor". Press the Apply button. Set the hotkey (accelerator) to something. Press the hotkey. Nothing happens. The hotkey does not trigger. No application gets launched. This works fine when in Unity and GNOME Shell, but not in GNOME Flashback. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-session-flashback 1:3.14.0-3ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Sun Mar 22 15:56:07 2015 InstallationDate: Installed on 2013-12-26 (450 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: gnome-flashback UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome-flashback/+bug/1435020/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1742443] Re: Ubuntu 18.04: PrtSc doesn't trigger gnome-screenshot window
It seems to only affect me when I use the Nvidia drivers. I am using Ubuntu 18.04 with Unity and Nvidia Drivers. It works fine when I use gnome or unity with nouveau. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1742443 Title: Ubuntu 18.04: PrtSc doesn't trigger gnome-screenshot window Status in gnome-screenshot package in Ubuntu: Opinion Bug description: Ubuntu 18.04 gnome-screenshot v 3.25.0-0ubuntu2 (amd64) Using the PrtSc button, alone or in combination with shift, alt or ctrl, doesn't trigger the gnome-screenshot window that asks to save the image. The screen blinks (so the button is intercepted) but no window is triggered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1742443/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
Hello. My situation was very complicated, and none of the fixes I found would work. I am running a Nvidia GTX970 with an Intel CPU and using a dual monitor setup. Ubuntu 17.04 was working very well. Later upgrading to Ubuntu 17.10, the Nvidia graphics became an issue because of Wayland, but I followed this guide and was able to set it working for 17.10, https://charlienewey.github.io/getting-nvidia-drivers-working-on- ubuntu-17-10/ . For 18.04, nothing I found online was working. I was able to setup Openbox and use that to investigate the matter. I suspected it was some sort of opengl problem since all applications requiring it would fail to run and cheking with the terminal, it would say that the libGLU1.1.so was not found, or one of those opengl libraries. Upon further investigating, it turned out that the xorg that comes stock with 18.04 does not have the latest Mesa patch that supports nvidia graphics cards. So I ended up getting the padoka ppa in order to get the latest xorg and mesa. Upon doing so, everything is working fine. I thought this fix was a little unorthodox being that I believed that Padoka was for Nouvou and AMD cards but, apparently it fixed the issue with the proprietary 396 drivers. I had the same issue with the 384, and 390. So I am not sure if this fix only pertains to the Nvidia 396 drivers, but I believe the problem stems from an Xorg that does not have the latest Mesa. https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/mesa -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
