[Desktop-packages] [Bug 1671339] [NEW] After resumed from suspend, desktop wallpaper does not get drawn correctly on Nvidia graphics
Public bug reported: This is a known issue on Nvidia driver for a long time. Originally it only happens on Unity Launcher, now it also affects desktop background. To solve/workaround this, the background needs to be redrawn upon resume. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: nautilus 1:3.20.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Mar 8 23:34:27 2017 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+65+24'" InstallationDate: Installed on 2017-03-08 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170307) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu6 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty ** Attachment added: "Screenshot from 2017-03-08 23-26-49.png" https://bugs.launchpad.net/bugs/1671339/+attachment/4834308/+files/Screenshot%20from%202017-03-08%2023-26-49.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1671339 Title: After resumed from suspend, desktop wallpaper does not get drawn correctly on Nvidia graphics Status in nautilus package in Ubuntu: New Bug description: This is a known issue on Nvidia driver for a long time. Originally it only happens on Unity Launcher, now it also affects desktop background. To solve/workaround this, the background needs to be redrawn upon resume. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: nautilus 1:3.20.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Mar 8 23:34:27 2017 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+65+24'" InstallationDate: Installed on 2017-03-08 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170307) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1671339/+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 1653324] Re: No wireless networks visible on resume from suspend. Erroneous Wired connection icon in nm-applet
Is NM asleep in all those failed cases? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1653324 Title: No wireless networks visible on resume from suspend. Erroneous Wired connection icon in nm-applet Status in network-manager package in Ubuntu: Confirmed Bug description: As others have reported this I just woke my Thinkpad 450 to find no network. I resolved this by manually reconnecting with "nmcli c up id " where was taken from the output of "nmcli c" on the same machine. Steps to reproduce:- This is an intermittent issue which for me happens once in a while, but not super often to be annoying. For others it appears to happen often. I suspend my laptop multiple times daily and don't see this more than once per couple of weeks, or sometimes once a month. * Use laptop in one location on wifi * Suspend (shut lid) laptop * Resume (open lid) in same location (so same wifi networks nearby) Expected behaviour:- * Network come back up Actual behaviour:- * No network connectivity * nm-applet icon shows the two arrows as if a wired connection is made * No or few wireless erroneous wireless networks shown nearby * Workaround 1 (reconnect from command line) nmcli c (lists wireless networks, look for yours in the "NAME" column, use it in command below) nmcli c up id NAME * Workaround 2 (restart entire network stack) This AskUbuntu question has one solution http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend- after-16-04-upgrade#761220 Further information:- Output of nmcli m while suspending and resuming:- alan@gort:~$ nmcli m Connectivity is now 'none' Networkmanager is now in the 'asleep' state enp0s25: unmanaged wlp3s0: unmanaged Connectivity is now 'full' Networkmanager is now in the 'connected (local only)' state enp0s25: unavailable wlp3s0: unavailable wlp3s0: disconnected Output of nmcli after using workaround 1 above:- popey_2.4g_bed: connection profile changed Connectivity is now 'none' Networkmanager is now in the 'connecting' state wlp3s0: connecting (configuring) wlp3s0: using connection 'popey_2.4g_bed' wlp3s0: connecting (getting IP configuration) Connectivity is now 'full' 'popey_2.4g_bed' is now the primary connection Networkmanager is now in the 'connected' state wlp3s0: connected popey_2.4g_bed: connection profile changed Hardware info:- Thinkpad T450 alan@gort:~$ lspci | grep -i net 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (3) I218-LM (rev 03) 03:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59) alan@gort:~$ uptime 05:31:54 up 2 days, 18:03, 7 users, load average: 0.34, 0.94, 1.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 31 05:38:47 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-27 (247 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 10.235.160.0/24 dev lxdbr0 proto kernel scope link src 10.235.160.1 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.95 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1653324/+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 1653324] Re: No wireless networks visible on resume from suspend. Erroneous Wired connection icon in nm-applet
I also had this problem before. "Networkmanager is now in the 'asleep' state" because somehow logind failed to work, which is caused by a dbus bug. Would you like to give new dbus a try? At least I no longer have this issue after installed dbus in xenial-proposed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1653324 Title: No wireless networks visible on resume from suspend. Erroneous Wired connection icon in nm-applet Status in network-manager package in Ubuntu: Confirmed Bug description: As others have reported this I just woke my Thinkpad 450 to find no network. I resolved this by manually reconnecting with "nmcli c up id " where was taken from the output of "nmcli c" on the same machine. Steps to reproduce:- This is an intermittent issue which for me happens once in a while, but not super often to be annoying. For others it appears to happen often. I suspend my laptop multiple times daily and don't see this more than once per couple of weeks, or sometimes once a month. * Use laptop in one location on wifi * Suspend (shut lid) laptop * Resume (open lid) in same location (so same wifi networks nearby) Expected behaviour:- * Network come back up Actual behaviour:- * No network connectivity * nm-applet icon shows the two arrows as if a wired connection is made * No or few wireless erroneous wireless networks shown nearby * Workaround 1 (reconnect from command line) nmcli c (lists wireless networks, look for yours in the "NAME" column, use it in command below) nmcli c up id NAME * Workaround 2 (restart entire network stack) This AskUbuntu question has one solution http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend- after-16-04-upgrade#761220 Further information:- Output of nmcli m while suspending and resuming:- alan@gort:~$ nmcli m Connectivity is now 'none' Networkmanager is now in the 'asleep' state enp0s25: unmanaged wlp3s0: unmanaged Connectivity is now 'full' Networkmanager is now in the 'connected (local only)' state enp0s25: unavailable wlp3s0: unavailable wlp3s0: disconnected Output of nmcli after using workaround 1 above:- popey_2.4g_bed: connection profile changed Connectivity is now 'none' Networkmanager is now in the 'connecting' state wlp3s0: connecting (configuring) wlp3s0: using connection 'popey_2.4g_bed' wlp3s0: connecting (getting IP configuration) Connectivity is now 'full' 'popey_2.4g_bed' is now the primary connection Networkmanager is now in the 'connected' state wlp3s0: connected popey_2.4g_bed: connection profile changed Hardware info:- Thinkpad T450 alan@gort:~$ lspci | grep -i net 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (3) I218-LM (rev 03) 03:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59) alan@gort:~$ uptime 05:31:54 up 2 days, 18:03, 7 users, load average: 0.34, 0.94, 1.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 31 05:38:47 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-27 (247 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 10.235.160.0/24 dev lxdbr0 proto kernel scope link src 10.235.160.1 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.95 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1653324/+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 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name
The commits in this merge can fix this bug: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=0d7bf7dee31175d3eeab2bd5a9eef8e7b6618016 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1647283 Title: WiFi being detected as ethernet when race condition on renaming for persistent name Status in HWE Next: New Status in NetworkManager: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: New Bug description: Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613 Version: NetworkManager 1.4.2 This bug happens after power-on with probability about 1/50. That means we need to reboot about 50 times to get into the buggy situation. "nmcli d" shows the device type is ethernet: DEVICE TYPE STATECONNECTION wlp1s0 ethernet unavailable -- lo loopback unmanaged-- The bug starts from a race condition. But it is not the root cause. I've also attach 2 logs. One is in good situation. Another is in bad situation. This log is generated by applying a "log patch" to network-manager 1.4.2 so we can see more stuff. In the bad situation. The bug starts with race condition. But the race condition is not the root cause. The race condition is: * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared. * Inside the NM, it is still using "wlan0" in "_linktype_get_type()". * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching failed in _linktype_get_type(). * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 disappeared. * And finally, devtype and kind are both NULL, so it returns NM_LINK_TYPE_ETHERNET for wlan0. Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit the type so it is still type ethernet. But from the log, I saw _linktype_get_type() is called several times later and return the correct type (wifi). But just, "nmcli d" still shows type ethernet. I'm wondering if we are missing to update the type in the Object created after renaming and re-detecting the type. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1647283/+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 1636397] Re: Fix modesetting slave output names
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1636397 Title: Fix modesetting slave output names Status in HWE Next: New Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Xenial: Fix Committed Status in xorg-server source package in Yakkety: Fix Committed Bug description: [Impact] Currently, NVIDIA and modesetting drivers are using same output names, that creates confusion for xrandr clients like gnome-setting-daemon or xrandr utility. When modesetting outputs act as slave for other x-screen (like NVIDIA X-screen here), modesetting driver uses different scheme of output names to avoid kind of confusion we are seeing here. There is a bug in modesetting X-driver gets shipped with X-server, which disables slave output's name scheme. From a reviewed upstream patch: "Commit c7e8d4a6ee9542f56cd241cf7a960fb8223a6b22 had already unifdef MODESETTING_OUTPUT_SLAVE_SUPPORT but commit 9257b1252da9092ddc676fec9aabe2b33dfad272 didn't notice that." so we need to backport that to zesty/yakkety/xenial. [Test Case] Enable dGPU, test that output to DP works. [Regression Potential] There should be none, as this leftover was a simple mistake that shouldn't be there. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1636397/+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 1575867] Re: unity-settings-daemon crashes on start with SIGABRT if xrandr provides two displays with the same name
Hi Rafał Cieślak, I made a merge proposal on your patch (with credit). Thanks for it! ** Branch linked: lp:~kaihengfeng/unity-settings-daemon/lp1575867 -- 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/1575867 Title: unity-settings-daemon crashes on start with SIGABRT if xrandr provides two displays with the same name Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: -- Symptoms -- I am experiencing this bug after a recent upgrade to Ubuntu 16.04, with unity-settings-daemon 15.04.1+16.04.20160209. unity-settings-daemon always fails to start (leaving me with a quasi- functional desktop); when run from a command-line, it simply outputs: ** ERROR:gsd-rr-config.c:661:gsd_rr_config_load_current: assertion failed: (gsd_rr_config_match (config, config)) Aborted and crashes with SIGABRT. This is 100% reproducible on my system. I have investigated the cause of this crash, and I can provide a patch that solves this bug. I do not know whether I shall help fixing this bug here, or if should I work with the upstream directly, a word of advice in this matter would be very appreciated. -- Bug analysis and proposed solution -- The mentioned assertion fails even though it compares the same configuration with itself. What gsd_rr_config_match does internally is that it takes each output from a configuration one by one, and searches - by name - for a matching output in the other config. If the search fails, or the found output does not match the one from first config, the gsd_rr_config_match check fails. Because of that, this check should never fail when comparing a configuration to itself, with the exception of one (presumably rare) care. It happens that, for my multi-monitor setup, libxrandr reports that there are two different outputs that share the same name "DP-1". In this case, the gsd_rr_config_match fails, because when searching for a matching output named "DP-1", it will return the same output both times, and therefore one pair will be not matching (the find_output function returns the first output that matches requested name). Therefore it appears that comparing configurations by checking whether outputs with matching names are equivalent may be wrong, because the output names are not guaranteed to be unique. I propose to modify both configuration comparing procedures (gsd_rr_config_match and gsd_rr_config_equal) so that they compare outputs matching them by their ids, which will always be unique due to their nature. Since the find_output function (which takes an output name as an argument) is only used by these two comparing functions, it makes sense to modify it so that it takes an output id as an argument instead. This is a valid solution, because in this case even if output names happen to repeat, the output ids will be used to distinguish between them, and gsd_rr_config_match will no longer incorrectly fail. Also, the proposed change will never cause a configuration comparing function to return true where it would otherwise not, because each two outputs with a different name will always have a different id as well. I attach to this bug report a patch that implements the proposed changes. Applying this patch entirely fixed the described symptoms on my machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1575867/+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 1560162] Re: Xenial: scaling is horribly out on xps13 install session
** Branch linked: lp:~kaihengfeng/ubiquity/fix-usd-scaling -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1560162 Title: Xenial: scaling is horribly out on xps13 install session Status in metacity package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Confirmed Bug description: STEPS: Requirements laptop desktop with a hidpi screen (Here xps 13) 1. Grab the latest daily image and trigger an install 2. On the first page notice the of centre and over scaled window EXPECTED: I expect to see something resembling a normal scaled desktop install ACTUAL: Things are not quite correct see attached screenshots ubiquity/xenial 2.21.49 amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1560162/+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 1571640] Re: lightdm changing resolution
** Branch linked: lp:~kaihengfeng/unity-greeter/16.04-sru-fix-1571640 -update-deps -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1571640 Title: lightdm changing resolution Status in unity-greeter package in Ubuntu: Fix Committed Status in unity-greeter source package in Xenial: New Status in unity-greeter source package in Yakkety: Fix Committed Bug description: [Impact] * Unity Greeter does not have the right scale at the beginning, after a short delay, it changes to the right scale. [Test Case] * It can be easily observed on HiDPI display, when Unity Greeter is starting. [Regression Potential] * If u-s-d failed to launch, Unity Greeter stuck at waiting u-s-d's signal and failed to proceed. But it's not likely to happen. Just after the upgrade to ubuntu 16.04, when lightdm starts the resolution is 2560x1600. Then, after about half a second it is automatically changed to 1280x800. This happens systematically at each boot. No external monitor is connected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 Uname: Linux 4.5.0-040500-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 18 14:39:03 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (525 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: lightdm UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1571640/+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 1571640] Re: lightdm changing resolution
** Description changed: + [Impact] + + * Unity Greeter does not have the right scale at the beginning, after a + short delay, it changes to the right scale. + + [Test Case] + + * It can be easily observed on HiDPI display, when Unity Greeter is + starting. + + [Regression Potential] + + * If u-s-d failed to launch, Unity Greeter stuck at waiting u-s-d's + signal and failed to proceed. But it's not likely to happen. + + + Just after the upgrade to ubuntu 16.04, when lightdm starts the resolution is 2560x1600. Then, after about half a second it is automatically changed to 1280x800. This happens systematically at each boot. No external monitor is connected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 Uname: Linux 4.5.0-040500-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 18 14:39:03 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (525 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: lightdm UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1571640 Title: lightdm changing resolution Status in unity-greeter package in Ubuntu: Fix Committed Status in unity-greeter source package in Xenial: New Status in unity-greeter source package in Yakkety: Fix Committed Bug description: [Impact] * Unity Greeter does not have the right scale at the beginning, after a short delay, it changes to the right scale. [Test Case] * It can be easily observed on HiDPI display, when Unity Greeter is starting. [Regression Potential] * If u-s-d failed to launch, Unity Greeter stuck at waiting u-s-d's signal and failed to proceed. But it's not likely to happen. Just after the upgrade to ubuntu 16.04, when lightdm starts the resolution is 2560x1600. Then, after about half a second it is automatically changed to 1280x800. This happens systematically at each boot. No external monitor is connected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 Uname: Linux 4.5.0-040500-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 18 14:39:03 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (525 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: lightdm UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1571640/+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 1571640] Re: lightdm changing resolution
** Branch linked: lp:~kaihengfeng/unity-greeter/16.04-sru-fix-1571640 ** Branch linked: lp:~kaihengfeng/unity-settings-daemon/16.04-sru- fix-1571640 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1571640 Title: lightdm changing resolution Status in unity-greeter package in Ubuntu: Fix Committed Status in unity-greeter source package in Xenial: New Status in unity-greeter source package in Yakkety: Fix Committed Bug description: Just after the upgrade to ubuntu 16.04, when lightdm starts the resolution is 2560x1600. Then, after about half a second it is automatically changed to 1280x800. This happens systematically at each boot. No external monitor is connected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 Uname: Linux 4.5.0-040500-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 18 14:39:03 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (525 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: lightdm UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1571640/+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 1492443] Re: bluetooth-wizard cannot pair with a 1byone bluetooth keyboard (or possibly, any keyboard that requires a PIN code?)
I can confirm that unity-control-center 15.04.0+16.04.20160413-0ubuntu3 in xenial-proposed fixes the issue. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1492443 Title: bluetooth-wizard cannot pair with a 1byone bluetooth keyboard (or possibly, any keyboard that requires a PIN code?) Status in unity-control-center package in Ubuntu: Fix Released Status in unity-control-center source package in Xenial: Fix Committed Bug description: * Impact some bluetooth keyboards can't be paired * Test case If you own a keyboard requiring a pincode for pairing try to pair it, it should work * Regression potential limited, it's only adding new code to a callback function which was unimplemented I'm on wily. I just got this keyboard, so I don't know if this is a regression or not with Bluez5. I'm guessing it is though. I can pair via the console just fine (though connecting is another story -- bug 1492441): $ bluetoothctl [NEW] Device 08:73:00:13:CC:45 1byone Keyboard [bluetooth]# agent on Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# pair 08:73:00:13:CC:45 Attempting to pair with 08:73:00:13:CC:45 [CHG] Device 08:73:00:13:CC:45 Connected: yes [agent] PIN code: 420005 [CHG] Device 08:73:00:13:CC:45 Modalias: usb:v04E8p7021d011B [CHG] Device 08:73:00:13:CC:45 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 08:73:00:13:CC:45 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 08:73:00:13:CC:45 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 08:73:00:13:CC:45 Paired: yes Pairing successful [CHG] Device 08:73:00:13:CC:45 Connected: no But when using bluetooth-wizard, none of the "PIN options" options work for me. I expected to be prompted to enter a random PIN code like I do when connecting it to my iPad or when connecting via the console above. But it just spins for a while and says that pairing failed. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity-control-center 15.04.0+15.10.20150818-0ubuntu1 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 4 15:55:47 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-09 (967 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 SourcePackage: unity-control-center SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: Upgraded to wily on 2013-01-31 (945 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1492443/+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 1571640] Re: lightdm changing resolution
Hi, Can you guys try my merge proposals? They should fix the issue. Both unity-greeter and unity-settings-daemon are needed. Thanks! ** Branch linked: lp:~kaihengfeng/unity-greeter/fix-resolution-changing ** Branch linked: lp:~kaihengfeng/unity-settings-daemon/add-signal-queue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1571640 Title: lightdm changing resolution Status in unity-greeter package in Ubuntu: Confirmed Bug description: Just after the upgrade to ubuntu 16.04, when lightdm starts the resolution is 2560x1600. Then, after about half a second it is automatically changed to 1280x800. This happens systematically at each boot. No external monitor is connected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 Uname: Linux 4.5.0-040500-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 18 14:39:03 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (525 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: lightdm UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1571640/+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 1557893] Re: The transition wallpaper does not have right scale on HiDPI monitor.
** Patch added: "cario-device-scale-api.patch" https://bugs.launchpad.net/ubuntu/+source/vala-0.20/+bug/1557893/+attachment/4614418/+files/cario-device-scale-api.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1557893 Title: The transition wallpaper does not have right scale on HiDPI monitor. Status in unity-greeter package in Ubuntu: Fix Released Status in vala-0.20 package in Ubuntu: Fix Released Status in unity-greeter source package in Trusty: Triaged Status in vala-0.20 source package in Trusty: New Bug description: Ubuntu Release: 16.04 Package Version: 16.04.0-0ubuntu1 What you expected to happen: The wallpaper scales to whole HiDPI monitor. What happened instead: The wallpaper only shows on upper left corner. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1557893/+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 1557893] Re: The transition wallpaper does not have right scale on HiDPI monitor.
** Also affects: vala-0.20 (Ubuntu) Importance: Undecided Status: New ** Changed in: vala-0.20 (Ubuntu) Status: New => Fix Committed ** Changed in: vala-0.20 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1557893 Title: The transition wallpaper does not have right scale on HiDPI monitor. Status in unity-greeter package in Ubuntu: Fix Released Status in vala-0.20 package in Ubuntu: Fix Released Status in unity-greeter source package in Trusty: Triaged Status in vala-0.20 source package in Trusty: New Bug description: Ubuntu Release: 16.04 Package Version: 16.04.0-0ubuntu1 What you expected to happen: The wallpaper scales to whole HiDPI monitor. What happened instead: The wallpaper only shows on upper left corner. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1557893/+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 1557893] Re: The transition wallpaper does not have right scale on HiDPI monitor.
In order to make the change build-able on Trusty, we need to add new
interface into cairo.vapi:
--- vala-0.22-0.22.1.orig/vapi/cairo.vapi
+++ vala-0.22-0.22.1/vapi/cairo.vapi
@@ -645,6 +645,8 @@ namespace Cairo {
public void mark_dirty_rectangle (int x, int y, int width, int
height);
public void set_device_offset (double x_offset, double
y_offset);
public void get_device_offset (out double x_offset, out double
y_offset);
+ public void set_device_scale (double x_scale, double y_scale);
+ public void get_device_scale (out double x_scale, out double
y_scale);
public void set_fallback_resolution (double x_pixels_per_inch,
double y_pixels_per_inch);
public void show_page ();
public Status status ();
Those two functions are indeed in Trusty's cairo, so I think it's safe
to expose these interface for Vala.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1557893
Title:
The transition wallpaper does not have right scale on HiDPI monitor.
Status in unity-greeter package in Ubuntu:
Fix Released
Status in unity-greeter source package in Trusty:
Triaged
Bug description:
Ubuntu Release: 16.04
Package Version: 16.04.0-0ubuntu1
What you expected to happen:
The wallpaper scales to whole HiDPI monitor.
What happened instead:
The wallpaper only shows on upper left corner.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1557893/+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 1557893] Re: The transition wallpaper does not have right scale on HiDPI monitor.
Hi Sebastien, When we enabled OEM products with HiDPI display, the "let's wait before xsettings settle down" hack was applied [1], so the unity-greeter is actually scaled to the right resolution, hence this issue. So it would be great if this fix can be put into Trusty. [1] https://bazaar.launchpad.net/~fourdollars/unity-greeter/add-hidpi- support/revision/1497 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1557893 Title: The transition wallpaper does not have right scale on HiDPI monitor. Status in unity-greeter package in Ubuntu: In Progress Status in unity-greeter source package in Trusty: Triaged Bug description: Ubuntu Release: 16.04 Package Version: 16.04.0-0ubuntu1 What you expected to happen: The wallpaper scales to whole HiDPI monitor. What happened instead: The wallpaper only shows on upper left corner. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1557893/+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 1557893] Re: The transition wallpaper does not have right scale on HiDPI monitor.
** Branch linked: lp:~kaihengfeng/unity-greeter/fix-hidpi-trasition- wallpaper -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1557893 Title: The transition wallpaper does not have right scale on HiDPI monitor. Status in unity-greeter package in Ubuntu: New Bug description: Ubuntu Release: 16.04 Package Version: 16.04.0-0ubuntu1 What you expected to happen: The wallpaper scales to whole HiDPI monitor. What happened instead: The wallpaper only shows on upper left corner. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1557893/+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 1557893] [NEW] The transition wallpaper does not have right scale on HiDPI monitor.
Public bug reported: Ubuntu Release: 16.04 Package Version: 16.04.0-0ubuntu1 What you expected to happen: The wallpaper scales to whole HiDPI monitor. What happened instead: The wallpaper only shows on upper left corner. ** Affects: unity-greeter (Ubuntu) Importance: Undecided Status: New ** Attachment added: "download.png" https://bugs.launchpad.net/bugs/1557893/+attachment/4600797/+files/download.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1557893 Title: The transition wallpaper does not have right scale on HiDPI monitor. Status in unity-greeter package in Ubuntu: New Bug description: Ubuntu Release: 16.04 Package Version: 16.04.0-0ubuntu1 What you expected to happen: The wallpaper scales to whole HiDPI monitor. What happened instead: The wallpaper only shows on upper left corner. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1557893/+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 1511301] Re: Failed to upgrade fglrx from 14.502 to 15.200 on Trusty.
Hi serenity, So it's a different issue. I think you should file a new bug for the HDMI issue, though I think no one but AMD has the capability to solve the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1511301 Title: Failed to upgrade fglrx from 14.502 to 15.200 on Trusty. Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in fglrx-installer source package in Trusty: Fix Committed Status in fglrx-installer-updates source package in Trusty: Fix Committed Bug description: SRU Request: [Impact] Upgrading from the upstream fglrx driver packages to the packages in the Ubuntu repository fails because the /etc/ati directory is a real directory instead of being a link (which was common in the Ubuntu packages). [Test Case] 1. Install the fglrx driver (14.502) in Ubuntu 14.04 generating deb packages from the AMD installer 2. Upgrade the package to the current ubuntu release. 3. Check the apt-get output Expected results: the fglrx module should be updated correctly. Actual results: The update fails as described below. [Regression Potential] Low. The change only affects a migration from a specific release. __ Note that the fglrx 14.502 package name is fglrx_14.502-0ubuntu1_amd64_UB_14.01.deb, which is from AMD's site, not from Ubuntu repository. Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for gconf2 (3.2.6-0ubuntu2) ... Processing triggers for hicolor-icon-theme (0.13-1) ... (gtk-update-icon-cache-3.0:22930): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Processing triggers for install-info (5.2.0.dfsg.1-2) ... Processing triggers for shared-mime-info (1.2-0ubuntu3) ... Processing triggers for sgml-base (1.26+nmu4ubuntu1) ... Processing triggers for gnome-icon-theme (3.10.0-0ubuntu2) ... (gtk-update-icon-cache-3.0:23024): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Processing triggers for doc-base (0.10.5) ... Processing 1 changed doc-base file... Errors were encountered while processing: /var/cache/apt/archives/fglrx_2%3a15.200-0ubuntu0.5_amd64.deb Log ended: 2015-10-22 05:31:11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1511301/+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 1511301] Re: Failed to upgrade fglrx from 14.502 to 15.200 on Trusty.
Hi serenity, Seems like you are using HDMI, so that's an HDMI audio output issue. Did you have HDMI audio when using open source driver? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1511301 Title: Failed to upgrade fglrx from 14.502 to 15.200 on Trusty. Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in fglrx-installer source package in Trusty: Fix Committed Status in fglrx-installer-updates source package in Trusty: Fix Committed Bug description: SRU Request: [Impact] Upgrading from the upstream fglrx driver packages to the packages in the Ubuntu repository fails because the /etc/ati directory is a real directory instead of being a link (which was common in the Ubuntu packages). [Test Case] 1. Install the fglrx driver (14.502) in Ubuntu 14.04 generating deb packages from the AMD installer 2. Upgrade the package to the current ubuntu release. 3. Check the apt-get output Expected results: the fglrx module should be updated correctly. Actual results: The update fails as described below. [Regression Potential] Low. The change only affects a migration from a specific release. __ Note that the fglrx 14.502 package name is fglrx_14.502-0ubuntu1_amd64_UB_14.01.deb, which is from AMD's site, not from Ubuntu repository. Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for gconf2 (3.2.6-0ubuntu2) ... Processing triggers for hicolor-icon-theme (0.13-1) ... (gtk-update-icon-cache-3.0:22930): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Processing triggers for install-info (5.2.0.dfsg.1-2) ... Processing triggers for shared-mime-info (1.2-0ubuntu3) ... Processing triggers for sgml-base (1.26+nmu4ubuntu1) ... Processing triggers for gnome-icon-theme (3.10.0-0ubuntu2) ... (gtk-update-icon-cache-3.0:23024): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Processing triggers for doc-base (0.10.5) ... Processing 1 changed doc-base file... Errors were encountered while processing: /var/cache/apt/archives/fglrx_2%3a15.200-0ubuntu0.5_amd64.deb Log ended: 2015-10-22 05:31:11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1511301/+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 1511301] Re: Failed to upgrade fglrx from 14.502 to 15.200 on Trusty.
Hi Serenity, First, be sure the APT is updated: $ sudo apt-get update Then you can remove old fglrx by `apt-get purge`: $ sudo apt-get purge fglrx fglrx-core fglrx-amdcccle Finally, reinstall them: $ sudo apt-get install fglrx fglrx-core fglrx-amdcccle And supposedly, this should fix your upgrading problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1511301 Title: Failed to upgrade fglrx from 14.502 to 15.200 on Trusty. Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in fglrx-installer source package in Trusty: Fix Committed Status in fglrx-installer-updates source package in Trusty: Fix Committed Bug description: SRU Request: [Impact] Upgrading from the upstream fglrx driver packages to the packages in the Ubuntu repository fails because the /etc/ati directory is a real directory instead of being a link (which was common in the Ubuntu packages). [Test Case] 1. Install the fglrx driver (14.502) in Ubuntu 14.04 generating deb packages from the AMD installer 2. Upgrade the package to the current ubuntu release. 3. Check the apt-get output Expected results: the fglrx module should be updated correctly. Actual results: The update fails as described below. [Regression Potential] Low. The change only affects a migration from a specific release. __ Note that the fglrx 14.502 package name is fglrx_14.502-0ubuntu1_amd64_UB_14.01.deb, which is from AMD's site, not from Ubuntu repository. Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for gconf2 (3.2.6-0ubuntu2) ... Processing triggers for hicolor-icon-theme (0.13-1) ... (gtk-update-icon-cache-3.0:22930): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Processing triggers for install-info (5.2.0.dfsg.1-2) ... Processing triggers for shared-mime-info (1.2-0ubuntu3) ... Processing triggers for sgml-base (1.26+nmu4ubuntu1) ... Processing triggers for gnome-icon-theme (3.10.0-0ubuntu2) ... (gtk-update-icon-cache-3.0:23024): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Processing triggers for doc-base (0.10.5) ... Processing 1 changed doc-base file... Errors were encountered while processing: /var/cache/apt/archives/fglrx_2%3a15.200-0ubuntu0.5_amd64.deb Log ended: 2015-10-22 05:31:11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1511301/+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 1511301] Re: Failed to upgrade fglrx from 14.502 to 15.200 on Trusty.
Hi serenity, >From your bug link, looks like you were upgrading fglrx from 13.350.1-0ubuntu2 to 15.200-0ubuntu0.6, but not exactly "Failed to upgrade fglrx from 14.502 to 15.200" as the bug title described. Although the symptom looks the same, I think there are some differences between those two situation. Anyway, can you try to manually remove the old fglrx via `apt-get purge` then installing the new one? I think this method might solve your problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1511301 Title: Failed to upgrade fglrx from 14.502 to 15.200 on Trusty. Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in fglrx-installer source package in Trusty: Fix Committed Status in fglrx-installer-updates source package in Trusty: Fix Committed Bug description: SRU Request: [Impact] Upgrading from the upstream fglrx driver packages to the packages in the Ubuntu repository fails because the /etc/ati directory is a real directory instead of being a link (which was common in the Ubuntu packages). [Test Case] 1. Install the fglrx driver (14.502) in Ubuntu 14.04 generating deb packages from the AMD installer 2. Upgrade the package to the current ubuntu release. 3. Check the apt-get output Expected results: the fglrx module should be updated correctly. Actual results: The update fails as described below. [Regression Potential] Low. The change only affects a migration from a specific release. __ Note that the fglrx 14.502 package name is fglrx_14.502-0ubuntu1_amd64_UB_14.01.deb, which is from AMD's site, not from Ubuntu repository. Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for gconf2 (3.2.6-0ubuntu2) ... Processing triggers for hicolor-icon-theme (0.13-1) ... (gtk-update-icon-cache-3.0:22930): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Processing triggers for install-info (5.2.0.dfsg.1-2) ... Processing triggers for shared-mime-info (1.2-0ubuntu3) ... Processing triggers for sgml-base (1.26+nmu4ubuntu1) ... Processing triggers for gnome-icon-theme (3.10.0-0ubuntu2) ... (gtk-update-icon-cache-3.0:23024): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Processing triggers for doc-base (0.10.5) ... Processing 1 changed doc-base file... Errors were encountered while processing: /var/cache/apt/archives/fglrx_2%3a15.200-0ubuntu0.5_amd64.deb Log ended: 2015-10-22 05:31:11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1511301/+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 1381625] Re: Adjust brightness to lowest value caused screen whole black
There are some scenarios make turning off brightness not desirable, e.g. an AIO user changes brightness to the lowest level in unity-control- center, he can't change it back if his keyboard does not have brightness hotkey. Since we can't ensure that all graphics driver have the same mechanism and each one of them does not change, I think it's a better choice to let userspace program controls a consistent policy. -- 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/1381625 Title: Adjust brightness to lowest value caused screen whole black Status in HWE Next: Confirmed Status in Unity Settings Daemon: Fix Released Status in linux package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Won't Fix Bug description: [Impact] When adjusting screen brightness to lowest value, it turns screen backlight off. [Test Case] 1. Install Image 2. Press System's brightness hotkey to adjust the brightness level to the lowest or 3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level to the lowest 4. Check if the screen display still has backlight Expected results: There is still screen backlight Actual results: Sceen backlight is turned off To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1381625/+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 1381625] Re: Adjust brightness to lowest value caused screen whole black
Yes, we can use that approach on unity-settings-daemon, with some minor modification to make xbacklight works. My intention to make it configurable is because there was a Braswell laptop with a cheap panel, which needs at least 5% max brightness to make it barely visible. For OEM projects, to solve problems like that, a minimum brightness setting can be a generic and convenient way to make preloaded Ubuntu more polished. That being said, most panel works just fine with brightness value 1 in my experience. -- 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/1381625 Title: Adjust brightness to lowest value caused screen whole black Status in HWE Next: Confirmed Status in Unity Settings Daemon: Fix Released Status in linux package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Won't Fix Bug description: [Impact] When adjusting screen brightness to lowest value, it turns screen backlight off. [Test Case] 1. Install Image 2. Press System's brightness hotkey to adjust the brightness level to the lowest or 3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level to the lowest 4. Check if the screen display still has backlight Expected results: There is still screen backlight Actual results: Sceen backlight is turned off To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1381625/+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 1511301] [NEW] Failed to upgrade fglrx from 14.502 to 15.200 on Trusty.
Public bug reported: Note that the fglrx 14.502 package name is fglrx_14.502-0ubuntu1_amd64_UB_14.01.deb, which is from AMD's site, not from Ubuntu repository. Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for gconf2 (3.2.6-0ubuntu2) ... Processing triggers for hicolor-icon-theme (0.13-1) ... (gtk-update-icon-cache-3.0:22930): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Processing triggers for install-info (5.2.0.dfsg.1-2) ... Processing triggers for shared-mime-info (1.2-0ubuntu3) ... Processing triggers for sgml-base (1.26+nmu4ubuntu1) ... Processing triggers for gnome-icon-theme (3.10.0-0ubuntu2) ... (gtk-update-icon-cache-3.0:23024): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Processing triggers for doc-base (0.10.5) ... Processing 1 changed doc-base file... Errors were encountered while processing: /var/cache/apt/archives/fglrx_2%3a15.200-0ubuntu0.5_amd64.deb Log ended: 2015-10-22 05:31:11 ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Failed to upgrade fglrx from 14.502 to 15.200. + Failed to upgrade fglrx from 14.502 to 15.200 on Trusty. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1511301 Title: Failed to upgrade fglrx from 14.502 to 15.200 on Trusty. Status in fglrx-installer package in Ubuntu: New Bug description: Note that the fglrx 14.502 package name is fglrx_14.502-0ubuntu1_amd64_UB_14.01.deb, which is from AMD's site, not from Ubuntu repository. Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for gconf2 (3.2.6-0ubuntu2) ... Processing triggers for hicolor-icon-theme (0.13-1) ... (gtk-update-icon-cache-3.0:22930): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Processing triggers for install-info (5.2.0.dfsg.1-2) ... Processing triggers for shared-mime-info (1.2-0ubuntu3) ... Processing triggers for sgml-base (1.26+nmu4ubuntu1) ... Processing triggers for gnome-icon-theme (3.10.0-0ubuntu2) ... (gtk-update-icon-cache-3.0:23024): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Processing triggers for doc-base (0.10.5) ... Processing 1 changed doc-base file... Errors were encountered while processing: /var/cache/apt/archives/fglrx_2%3a15.200-0ubuntu0.5_amd64.deb Log ended: 2015-10-22 05:31:11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1511301/+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 1376764] Re: on-screen keyboard requires expert knowledge to launch in 14.10 Final Beta
Hi, I found this problem also occurs on Trusty. No effects when enabling On Screen Keyboard in Universal Access panel which is in unity-control-center. Although comment #6 mentioned that it works in Trusty, but I found that the org.gnome.Shell actually exits in dbus.. I tried applying the patch (revno:1818 in trunk), and it can fix the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1376764 Title: on-screen keyboard requires expert knowledge to launch in 14.10 Final Beta Status in Onboard on-screen keyboard: Fix Released Status in onboard package in Ubuntu: Fix Released Bug description: Activating the on-screen keyboard in the settings menu has no effect. Trying to manually execute /usr/bin/onboard via pointing-and-clicking opens up gedit (i.e., it's not recognised as an executable). No other keyboard input is available for the device in question, so further tests via command line (such as confirming that `python /usr/bin/onboard' starts onboard normally) are not feasible. Thus, 14.10 final beta is bootable but completely unusable on some tablet devices (Surface Pro 3 here). (Filing against `onboard' because this might be an `onboard' installation issue.) To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1376764/+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 1326257] Re: [nvidia-prime] Cannot adjust brightness in guest session and results in black screen while changing the resolution
This package also fixes Bug #1330425, caused by xrandr reporting excessive list of resolution/refresh-rate, which makes wrong res/rate value being picked under mirror mode. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1326257 Title: [nvidia-prime] Cannot adjust brightness in guest session and results in black screen while changing the resolution Status in Nvidia Feature Request and Bug Reporting: New Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: New Status in “nvidia-prime” package in Ubuntu: In Progress Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “nvidia-prime” source package in Precise: In Progress Status in “ubuntu-drivers-common” source package in Precise: Invalid Status in “xorg-server-lts-saucy” source package in Precise: New Status in “nvidia-prime” source package in Trusty: Invalid Status in “ubuntu-drivers-common” source package in Trusty: Fix Committed Status in “xorg-server-lts-saucy” source package in Trusty: New Bug description: SRU Request Systems with Optimus (Intel+NVIDIA GPUs) can have problems with the backlight (private bug #1290694) and when detecting and switching to different resolutions (private bug #1285062). Using the intel driver (with SNA) works better than the current solution (the modesetting driver). [Impact] * Backlight control and resolution changes fail on some Optimus systems. [Test Case] * Select performance mode from the nvidia-settings panel and try to adjust the backlight or to cycle through the available resolutions - Expected: the backlight can be adjusted, and changing the resolution works. - Bad behavior: the backlight can't be adjusted and changing the resolution can some times result in a black screen. [Regression Potential] * Low, as the intel driver is more feature complete than modesetting. [Other Info] * N/A -- Running the proprietary nvidia drivers in an Optimus config works (Intel+NVIDIA) can discover two issues: 1. Cannot adjust brightness in the guest session (private bug #1290694) [Test Case] * Switch to guest session and adjust brightness from settings or hotkey or command line - Expected: Can adjust the brightness - Bad behavior: Cannot adjust brightness 2. Black screen while changing the resolution (private bug #1285062) but switching to the guest session results in a black screen. [Test Case] * Go to display setting, set rotation to counterclockwise/clockwise/180 degrees and click apply - Expected results: Can switch display rotation successfully - Actual results: Black screen when switching display rotation To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1326257/+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
