[Dx-packages] [Bug 381416] Re: notify-osd should have a close button
This is really obnoxious. I thought I'd get used to it once gnome3 and unity came out, but it's only made me more frustrated as time goes on. I miss the old gconf way of doing things, where a user could change anything they disagreed with. This seems more like locking the end users into the lowest common denominator of UI/UX in an attempt to fit in with The Big Two. The whole idea seems counter to the linux philosophy. I don't want to beat a dead horse, but I do want to restart a discussion. I think this needs a control panel with user customizable items like time to display, opacity, size, sound, position, and possibly the ability to dismiss simply by moving the cursor over it. However, I'd settle for just an X to dismiss. -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/381416 Title: notify-osd should have a close button Status in notify-osd package in Ubuntu: Won't Fix Bug description: Binary package hint: notify-osd As simple as that. The new notification system works fine, but it really bugs me that I'm forced to wait for those little messages to fade away by themselves. Should I suggest this somewhere else? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/381416/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 998955] Re: Printer Window is corrupt.
** Package changed: indicator-printers (Ubuntu) => system-config-printer (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-printers in Ubuntu. https://bugs.launchpad.net/bugs/998955 Title: Printer Window is corrupt. Status in system-config-printer package in Ubuntu: New Bug description: See file attached. My printer has plenty of ink. No problem in all previous versions of Ubuntu. I have six ink cartridges but see attachment how they are displayed. I use Unity 2D due to well known NVidia problem but same display appears in Unity 3D. I upgraded to 12.04 from 11.10. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: indicator-printers 0.1.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Mon May 14 12:34:45 2012 ExecutablePath: /usr/lib/indicator-printers/indicator-printers-service InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_AU.UTF-8 SourcePackage: indicator-printers UpgradeStatus: Upgraded to precise on 2012-05-03 (10 days ago) XsessionErrors: (gnome-settings-daemon:30727): color-plugin-WARNING **: failed to get edid: unable to get EDID for output (gnome-settings-daemon:30727): color-plugin-WARNING **: unable to get EDID for xrandr-default: unable to get EDID for output (gnome-settings-daemon:30727): color-plugin-WARNING **: failed to reset xrandr-default gamma tables: gamma size is zero (gnome-settings-daemon:30727): color-plugin-WARNING **: unable to get EDID for xrandr-default: unable to get EDID for output (gnome-settings-daemon:30727): color-plugin-WARNING **: failed to reset xrandr-default gamma tables: gamma size is zero To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/998955/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1483427] Re: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5
In the example above, I dimmed backlight to complete black (nothing visible) 2x, just before posting the log... -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1483427 Title: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5 Status in indicator-power package in Ubuntu: Invalid Status in repowerd package in Ubuntu: New Bug description: Possible to manually set display brightness to 0 on Ubuntu Touch It is possible to move the brightness slider to the very left position, which will set the display brightness of affected device to zero, or, to total darkness. This is a bug, since this leads to user's inability to set the brightness back or, generally, to operate the device. There is a slight chance, though, to return the brightness back to non-zero value (blindly, trying by user's memory). Also, this gets even more problematic, if we think about a scenario, where such Ubuntu device is locked by a PIN. User has to try to unlock the device on the dark screen, open the top panel with settings, scroll to the far right (to access the brightness settings), and then trying to hit the correct slider - all on a dark screen. This happened on Aquaris E5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1483427/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1483427] Re: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5
And here is the second one... ** Attachment added: "repowerd.log" https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1483427/+attachment/4790905/+files/repowerd.log -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1483427 Title: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5 Status in indicator-power package in Ubuntu: Invalid Status in repowerd package in Ubuntu: New Bug description: Possible to manually set display brightness to 0 on Ubuntu Touch It is possible to move the brightness slider to the very left position, which will set the display brightness of affected device to zero, or, to total darkness. This is a bug, since this leads to user's inability to set the brightness back or, generally, to operate the device. There is a slight chance, though, to return the brightness back to non-zero value (blindly, trying by user's memory). Also, this gets even more problematic, if we think about a scenario, where such Ubuntu device is locked by a PIN. User has to try to unlock the device on the dark screen, open the top panel with settings, scroll to the far right (to access the brightness settings), and then trying to hit the correct slider - all on a dark screen. This happened on Aquaris E5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1483427/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1483427] Re: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5
My config attached. ** Attachment added: "config-default.xml" https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1483427/+attachment/4790904/+files/config-default.xml -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1483427 Title: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5 Status in indicator-power package in Ubuntu: Invalid Status in repowerd package in Ubuntu: New Bug description: Possible to manually set display brightness to 0 on Ubuntu Touch It is possible to move the brightness slider to the very left position, which will set the display brightness of affected device to zero, or, to total darkness. This is a bug, since this leads to user's inability to set the brightness back or, generally, to operate the device. There is a slight chance, though, to return the brightness back to non-zero value (blindly, trying by user's memory). Also, this gets even more problematic, if we think about a scenario, where such Ubuntu device is locked by a PIN. User has to try to unlock the device on the dark screen, open the top panel with settings, scroll to the far right (to access the brightness settings), and then trying to hit the correct slider - all on a dark screen. This happened on Aquaris E5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1483427/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1557717] Re: indicator-session should emit Shutdown not Reboot for unity8
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1557717 Title: indicator-session should emit Shutdown not Reboot for unity8 Status in indicator-session package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: In indicator-session, the following code exists: case PROMPT_WITH_UNITY: /* NB: TYPE_REBOOT instead of TYPE_SHUTDOWN because the latter adds lock & logout options in Unity... */ show_unity_end_session_dialog (self, END_SESSION_TYPE_REBOOT); Can we get that fixed? unity8 doesn't currently have such issues, but is forced to hack a shutdown dialog when asked to show a reboot dialog because of this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1557717/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1557717] Re: indicator-session should emit Shutdown not Reboot for unity8
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-session (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1557717 Title: indicator-session should emit Shutdown not Reboot for unity8 Status in indicator-session package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: In indicator-session, the following code exists: case PROMPT_WITH_UNITY: /* NB: TYPE_REBOOT instead of TYPE_SHUTDOWN because the latter adds lock & logout options in Unity... */ show_unity_end_session_dialog (self, END_SESSION_TYPE_REBOOT); Can we get that fixed? unity8 doesn't currently have such issues, but is forced to hack a shutdown dialog when asked to show a reboot dialog because of this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1557717/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1307657] Re: [SRU] UBUNTU_MENUPROXY should not be set in Xfce
We have not a chance to make the global menu really configurable per sessions? If we don't have UBUNTU_MENUPROXY in our environment also could be problematic. For example, if i'm outside of unity and i want to use the unity-gtk-module in a third-party global menu implementation. I will need to set UBUNTU_MENUPROXY=0 for all root sessions, not matter if was launched with pkexec or gksudo or sudo, because root application have not access to the com.canonical.AppMenu.Registrar. Then the only solution will be to set UBUNTU_MENUPROXY=0 in etc/environment and then probably in /etc/profile i will need to set it to 1 again, but of course this will have some side effect in other sessions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1307657 Title: [SRU] UBUNTU_MENUPROXY should not be set in Xfce Status in unity-gtk-module package in Ubuntu: Fix Released Status in xfce4-indicator-plugin package in Ubuntu: Invalid Status in unity-gtk-module source package in Trusty: Fix Released Status in xfce4-indicator-plugin source package in Trusty: Invalid Status in unity-gtk-module source package in Utopic: Fix Released Status in xfce4-indicator-plugin source package in Utopic: Invalid Bug description: [Impact] The upstart script for unity-gtk-module causes it to run under all desktop environments indiscriminately when it should only be running under Unity. It does this by adding unity-gtk-module to the environment variable GTK_MODULES. In Xfce, this causes the panel to crash when trying to add Unity indicators, as well as other related side effects (see: LP: #1314782, LP: #1347272). The fix to ensure we only modify GTK_MODULES under Unity is already in 14.10. [Test Case] Log into a Xubuntu session on a machine that has both ubuntu-desktop and xubuntu-desktop. Add the Indicator Plugin to the panel and open a terminal window. A crash dialog should appear notifying the user that the Indicator Plugin unexpectedly left the panel. [Regression Potential] The potential for regression is low since the only change is to preserve the original value of the GTK_MODULES environment variable, as well as to never set UBUNTU_MENUPROXY. The fix restores the desktop environment to its intended state of not running unity-gtk-module. Also, I've tested the change under Unity, and application menus still work properly under the global menu without regression. [Other Info] N/A === original bug report === To reproduce: either start with a fresh Ubuntu install and then install xubuntu-desktop, or start with Xubuntu and then install ubuntu-desktop - ie have both Xfce and Unity installed on the same machine. Xfce now has support for gtk3 indicators launched by upstart, but indicator-appmenu is totally broken - it will constantly crash the panel and applications. Xfce has a mechanism to hide indicators, and then the frontend UI will not be loaded in the panel, but it seems that UBUNTU_MENUPROXY is still being set in Xfce, which causes menus to disappear from applications, even though nothing is available to receive them. I discussed this with tedg and he suggested that the problem may be to do with the upstart service which sets UBUNTU_MENUPROXY, ie /usr/share/upstart/sessions/unity-gtk-module.conf We may in future get the appmenus working in Xfce, and then we would need some way to turn the menuproxy on and off depending on the user configuration. But for now, since they are broken anyway, it would be easiest to simply blacklist xubuntu desktop completely. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-gtk-module-common 0.0.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 14 19:40:36 2014 InstallationDate: Installed on 2014-02-11 (61 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140210) PackageArchitecture: all SourcePackage: unity-gtk-module UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1307657/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1483427] Re: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5
Repowerd reads the min/max values from the device config xml file shipped with the device. Does this file contain sane values? Could someone with an E5 device paste the contents of: 1. /usr/share/powerd/device_configs/config-default.xml 2. /var/log/repowerd.log Thanks. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1483427 Title: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5 Status in indicator-power package in Ubuntu: Invalid Status in repowerd package in Ubuntu: New Bug description: Possible to manually set display brightness to 0 on Ubuntu Touch It is possible to move the brightness slider to the very left position, which will set the display brightness of affected device to zero, or, to total darkness. This is a bug, since this leads to user's inability to set the brightness back or, generally, to operate the device. There is a slight chance, though, to return the brightness back to non-zero value (blindly, trying by user's memory). Also, this gets even more problematic, if we think about a scenario, where such Ubuntu device is locked by a PIN. User has to try to unlock the device on the dark screen, open the top panel with settings, scroll to the far right (to access the brightness settings), and then trying to hit the correct slider - all on a dark screen. This happened on Aquaris E5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1483427/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1483427] Re: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: repowerd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1483427 Title: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5 Status in indicator-power package in Ubuntu: Invalid Status in repowerd package in Ubuntu: New Bug description: Possible to manually set display brightness to 0 on Ubuntu Touch It is possible to move the brightness slider to the very left position, which will set the display brightness of affected device to zero, or, to total darkness. This is a bug, since this leads to user's inability to set the brightness back or, generally, to operate the device. There is a slight chance, though, to return the brightness back to non-zero value (blindly, trying by user's memory). Also, this gets even more problematic, if we think about a scenario, where such Ubuntu device is locked by a PIN. User has to try to unlock the device on the dark screen, open the top panel with settings, scroll to the far right (to access the brightness settings), and then trying to hit the correct slider - all on a dark screen. This happened on Aquaris E5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1483427/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1483427] Re: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5
** Package changed: powerd (Ubuntu) => repowerd (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1483427 Title: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5 Status in indicator-power package in Ubuntu: Invalid Status in repowerd package in Ubuntu: New Bug description: Possible to manually set display brightness to 0 on Ubuntu Touch It is possible to move the brightness slider to the very left position, which will set the display brightness of affected device to zero, or, to total darkness. This is a bug, since this leads to user's inability to set the brightness back or, generally, to operate the device. There is a slight chance, though, to return the brightness back to non-zero value (blindly, trying by user's memory). Also, this gets even more problematic, if we think about a scenario, where such Ubuntu device is locked by a PIN. User has to try to unlock the device on the dark screen, open the top panel with settings, scroll to the far right (to access the brightness settings), and then trying to hit the correct slider - all on a dark screen. This happened on Aquaris E5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1483427/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
