[Dx-packages] [Bug 1409530] Re: password dialog missing after suspend
** Package changed: lightdm (Ubuntu) = unity (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1409530 Title: password dialog missing after suspend Status in unity package in Ubuntu: New Bug description: Intermittently after returning from suspend, the password text box will be missing, making it impossible to unlock the screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 11 13:59:03 2015 InstallationDate: Installed on 2014-11-30 (42 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1409530/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1, 14.10
** Tags removed: charset hotkeys keyboard-layout-switching-related layout trusty-desktop ** Tags added: keyboard-layout-switching-hotkeys metabug -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1, 14.10 Status in Aptana Studio Installer: New Status in Default settings for the Baltix GNU/Linux OS and desktop: New Status in LibreOffice Productivity Suite: Fix Released Status in IBus: New Status in Indicator keyboard: Fix Released Status in Inkscape: A Vector Drawing Tool: New Status in MonoDevelop: New Status in Mutter: Fix Released Status in KDE document viewer: New Status in The OpenOffice.org Suite: New Status in Sigram: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in indicator-keyboard package in Ubuntu: Triaged Status in openjdk-7 package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-settings-daemon package in Fedora: Unknown Status in gnome-shell package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters-keyboard-hotkeys-windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1, 14.10
** Tags removed: ubuntu-desktop-trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1, 14.10 Status in Aptana Studio Installer: New Status in Default settings for the Baltix GNU/Linux OS and desktop: New Status in LibreOffice Productivity Suite: Fix Released Status in IBus: New Status in Indicator keyboard: Fix Released Status in Inkscape: A Vector Drawing Tool: New Status in MonoDevelop: New Status in Mutter: Fix Released Status in KDE document viewer: New Status in The OpenOffice.org Suite: New Status in Sigram: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in indicator-keyboard package in Ubuntu: Triaged Status in openjdk-7 package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-settings-daemon package in Fedora: Unknown Status in gnome-shell package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters-keyboard-hotkeys-windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+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 1280759] Re: Unity shortcuts (Super+A/F/M/C/V) do not work on non-latin layout in Trusty - shortcuts are defined via keyboard layout, not the keys
*** This bug is a duplicate of bug 1226962 *** https://bugs.launchpad.net/bugs/1226962 ** This bug has been marked a duplicate of bug 1226962 Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1, 14.10 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1280759 Title: Unity shortcuts (Super+A/F/M/C/V) do not work on non-latin layout in Trusty - shortcuts are defined via keyboard layout, not the keys Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: There are shortcuts to open lenses in Unity, for example Super + A for App Lens, or Super + F for Files Lens, etc. There are also shortcuts in the Launcher Super + 1 to 9 to launch apps from the Launcher. These shortcuts don't work if the keyboard layout is set to a non-Latin layout, in my case Persian, where almost all the keys are mapped to new characters. HOW TO REPRODUCE: Add a new Persian keyboard layout to the system, in addition to English, via keyboard layout indicator -- Text Entry Settings. Switch to the Persian layout (by clicking on the keyboard layout indicator). Press Super + F. WHAT HAPPENS: Dash is not open. Nothing happens. WHAT SHOULD HEPPEN: The Files Lens in the dash should open. The shortcuts should be associated with the keys on the keyboard, not to the characters they are associated with (which depends on the active keyboard layout). When I am typing something in Persian, and I want to search for a file, it is not reasonable that I should first switch back to the English layout before I can use a particular shortcut. This problem does not happen in some other apps like gedit or Firefox. COMPARE TO GEDIT: Open gedit text editor. Write something. Switch to the Persian layout. Press Ctrl + S (the shortcut to save the document). WHAT HAPPENS, AND WHAT SHOULD HAPPEN: The save dialoge box appears. I think this problem happens for all keyboard layouts that don't use Latin characters. Layout-wise, when I press Ctrl + S while Persian layout is active, I am typing Ctrl + س. But keyboard-wise, I am always pressing the same keyboard binding. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libunity9 7.1.4+14.04.20140210-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 16 12:04:10 2014 InstallationDate: Installed on 2014-02-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) SourcePackage: libunity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1280759/+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 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program
** Tags removed: trusty-desktop ** Tags added: amd64 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program Status in GNOME Shell: Won't Fix Status in Unity: Confirmed Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Status in gnome-settings-daemon package in ALT Linux: Unknown Status in gnome-settings-daemon package in Debian: New Status in gnome-settings-daemon package in Fedora: Unknown Status in gnome-settings-daemon package in openSUSE: Confirmed Bug description: Tried only with ctrl+shift, maybe behaves the same for other modifier key combinations when used as shortcut for switching layouts. - Set ctrl+shift as shortcut for switching keyboard layouts - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work (actually Terminal window loses focus when ctrl+shift is pressed, and layout is switched) -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:40:02 2013 InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1245473/+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 1156566] Re: Restart is missing from the system menu
** Tags removed: ubuntu-desktop-trusty ** Tags added: trusty ** Tags added: running-unity -- 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/1156566 Title: Restart is missing from the system menu Status in The Session Menu: Triaged Status in indicator-session package in Ubuntu: Triaged Bug description: Problem occurs in: indicator-session 12.10.5daily13.03.08-0ubuntu1, Ubuntu R Does not occur in: Ubuntu 12.10 1. Open the system menu. What you see: Log Out..., Suspend, and Shut Down... items. What you should see: A Restart... item between Suspend and Shut Down https://wiki.ubuntu.com/SystemMenu This is a regression of bug 815077. In 2011 we thought it might be a good idea to demote Restart to an extra button in the Shut Down dialog, but we were wrong. So we moved it back to a top-level item in the system menu. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1156566/+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 1391501] Re: Calendar reminders should mute if phone is muted
I would use a separate role. Calendar reminders are lower in priority than Ringer and Alarms and users should be able to silence them. ** Description changed: Calendar reminders seem to use the alarm role, which means muting your phone does not impact them. It should either use the same role as the ringer, or maybe a completely separate one. This is related to bug #1291458. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-datetime 13.10.0+15.04.20141103-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 11 13:06:24 2014 SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) + + UX Solution: + I would use a separate role. + + Calendar reminders are lower in priority than Ringer and Alarms and + users should be able to silence them. ** Changed in: ubuntu-ux Status: New = Fix Committed ** Changed in: ubuntu-ux Assignee: Paty Davila (dizzypaty) = Giorgio Venturi (giorgio-venturi) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1391501 Title: Calendar reminders should mute if phone is muted Status in the base for Ubuntu mobile products: New Status in Ubuntu UX bugs: Fix Committed Status in indicator-datetime package in Ubuntu: New Bug description: Calendar reminders seem to use the alarm role, which means muting your phone does not impact them. It should either use the same role as the ringer, or maybe a completely separate one. This is related to bug #1291458. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-datetime 13.10.0+15.04.20141103-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 11 13:06:24 2014 SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) UX Solution: I would use a separate role. Calendar reminders are lower in priority than Ringer and Alarms and users should be able to silence them. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1391501/+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 1409530] [NEW] password dialog missing after suspend
You have been subscribed to a public bug: Intermittently after returning from suspend, the password text box will be missing, making it impossible to unlock the screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 11 13:59:03 2015 InstallationDate: Installed on 2014-11-30 (42 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- password dialog missing after suspend https://bugs.launchpad.net/bugs/1409530 You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. -- 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 1388235] Re: [indicators] Battery icon turns red at 30%
** Summary changed: - Battery icon turns red at 30% + [indicators] Battery icon turns red at 30% -- 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/1388235 Title: [indicators] Battery icon turns red at 30% Status in Ubuntu UX bugs: Confirmed Status in indicator-power package in Ubuntu: In Progress Status in ubuntu-themes package in Ubuntu: In Progress Bug description: This seems a bit pessimistic since the phone still has a great deal of capacity and time left, perhaps 15 or 20% is a better threshold To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1388235/+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 1347638] Re: Launch1 button doesn't work on shortcuts
Is there any workarround for this? Looks like simple regression -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1347638 Title: Launch1 button doesn't work on shortcuts Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: Hardware: Thinkpad X230, but seemingly all Thinkpads. (Apologies if this is mis-characterized as a Unity bug - not sure where to put it) The special Thinkpad button, often called ThinkVantage button, used to work fine for keyboard shortcuts in 12.04, as configured in the keyboard settings panel. In 14.04 it is possible to assign it to a shortcut in the keyboard settings dialog, where it shows up as Launch1, but it doesn't work - they shortcut is not activated by hitting that key. The key appears to get through to the desktop and apps, because if I hit it while Emacs has focus it complains that nothing is assigned to XF86Launch1 (in 12.04 the key didn't get through to Emacs and there was no problem) Discussion of this, including some other's outputs, is here: http://ubuntuforums.org/showthread.php?t=890 - xev gives this on keypress/release: MappingNotify event, serial 37, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 KeyPress event, serial 37, synthetic NO, window 0x401, root 0xa2, subw 0x0, time 2883009, (-1684,706), root:(610,758), state 0x0, keycode 156 (keysym 0x1008ff41, XF86Launch1), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x401, root 0xa2, subw 0x0, time 2883009, (-1684,706), root:(610,758), state 0x0, keycode 156 (keysym 0x1008ff41, XF86Launch1), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False - acpi_listen gives: button/prog1 PROG1 0080 K - ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,place,grid,vpswitch,gnomecompat,mousepoll,session,move,obs,imgpng,snap,regex,animation,expo,ezoom,staticswitcher,workarounds,wall,fade,scale] CurrentDesktop: Unity Date: Wed Jul 23 08:11:18 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-11 (11 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1347638/+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 743823] Re: Battery indicator goes Critical Red with 1:10 battery left
argh, why did the auto-linking of the bug id not work? here, have a link instead: https://bugs.launchpad.net/ubuntu/+source/indicator- power/+bug/1410495 -- 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/743823 Title: Battery indicator goes Critical Red with 1:10 battery left Status in Ayatana Design: Fix Released Status in The Power Indicator: Fix Released Status in indicator-power package in Ubuntu: Fix Released Bug description: Binary package hint: ubuntu-mono Since the Ubuntu-Monochrome 0.0.26 upload, the battery status icon now goes critical red with over an hour to spare. We need to confirm this in Ayatana-Design, but my hunch is the following would be more useful: external power: normal text colour (ivory/chocolate for Ambiance/Radiance) =1:00 remaining: normal text colour 1:00 remaining: orange non-critical warning =0:10 remaining: red critical warning =0:02 remaining: red critical warning if suspend/hibernate action selected and proven working =0:02 remaining: red critical (flashing) warning if simply going to power-off Additionally, the Ubuntu Mono 0.0.26 change uses a battery icon with no fill for empty. This is not as clear to the user as an icon that instead uses a very small fill at end of the battery, even for zero. This is more intuitive as it makes it clear that the icon is used as a percentage indicator; with an empty fill the user must already know this for empty to be useful as a relative indicator. At the moment, the Red with some left state seen at 1:10 remaining is far more visible to the user than the (more serious) completely empty icon. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/743823/+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 1410495] Re: Battery indicator goes Critical Red with more than 1 hour battery left
The times left shown in the UPowerDump file will not be representative, as the bug report happened quite some time after I originally made the screenshot. -- 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/1410495 Title: Battery indicator goes Critical Red with more than 1 hour battery left Status in indicator-power package in Ubuntu: New Bug description: On my current laptop, the battery indicator shows a red-with-a-little- left icon when there is more than an hour left in the battery, which is not really appropriate for a critical battery warning. This bug is probably a regression of #743823, and I was asked to create a new bug by @mpt: Christoph, yes, please report a new bug including a screenshot. On phones we may have to color by percentage, but on PCs we can and should color by time remaining to avoid false alarms. A screenshot is attached. Unfortunately I didn't realize at the time that the screenshotter does not record open menus, so you'll have to take my word that the time remaining in the indicator menu was at 1 hour. I can redo the screenshot, if necessary. fwiw, the transition levels (based on minutes left) proposed in the bug description of #743823 sound good to me. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-power 12.10.6+14.10.20141015-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 13 21:08:43 2015 InstallationDate: Installed on 2014-12-22 (22 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: indicator-power UpgradeStatus: Upgraded to utopic on 2014-12-22 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1410495/+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 1410495] [NEW] Battery indicator goes Critical Red with more than 1 hour battery left
Public bug reported: On my current laptop, the battery indicator shows a red-with-a-little- left icon when there is more than an hour left in the battery, which is not really appropriate for a critical battery warning. This bug is probably a regression of #743823, and I was asked to create a new bug by @mpt: Christoph, yes, please report a new bug including a screenshot. On phones we may have to color by percentage, but on PCs we can and should color by time remaining to avoid false alarms. A screenshot is attached. Unfortunately I didn't realize at the time that the screenshotter does not record open menus, so you'll have to take my word that the time remaining in the indicator menu was at 1 hour. I can redo the screenshot, if necessary. fwiw, the transition levels (based on minutes left) proposed in the bug description of #743823 sound good to me. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-power 12.10.6+14.10.20141015-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 13 21:08:43 2015 InstallationDate: Installed on 2014-12-22 (22 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: indicator-power UpgradeStatus: Upgraded to utopic on 2014-12-22 (21 days ago) ** Affects: indicator-power (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages utopic ** Attachment added: indicator-bug.png https://bugs.launchpad.net/bugs/1410495/+attachment/4297830/+files/indicator-bug.png -- 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/1410495 Title: Battery indicator goes Critical Red with more than 1 hour battery left Status in indicator-power package in Ubuntu: New Bug description: On my current laptop, the battery indicator shows a red-with-a-little- left icon when there is more than an hour left in the battery, which is not really appropriate for a critical battery warning. This bug is probably a regression of #743823, and I was asked to create a new bug by @mpt: Christoph, yes, please report a new bug including a screenshot. On phones we may have to color by percentage, but on PCs we can and should color by time remaining to avoid false alarms. A screenshot is attached. Unfortunately I didn't realize at the time that the screenshotter does not record open menus, so you'll have to take my word that the time remaining in the indicator menu was at 1 hour. I can redo the screenshot, if necessary. fwiw, the transition levels (based on minutes left) proposed in the bug description of #743823 sound good to me. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-power 12.10.6+14.10.20141015-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 13 21:08:43 2015 InstallationDate: Installed on 2014-12-22 (22 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: indicator-power UpgradeStatus: Upgraded to utopic on 2014-12-22 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1410495/+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 1354180] Re: Regression: Ctrl+Alt+T doesn't open a terminal
** Changed in: unity (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1354180 Title: Regression: Ctrl+Alt+T doesn't open a terminal Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Not sure Unity is the package. Ctrl+Alt+T used to be the keyboard shortcut for opening a new terminal window (whether or not one was already open). It doesn't work any more. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu Aug 7 23:12:06 2014 InstallationDate: Installed on 2013-10-11 (300 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (75 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1354180/+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 743823] Re: Battery indicator goes Critical Red with 1:10 battery left
Matthew, thanks, I just did: #1410495 -- 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/743823 Title: Battery indicator goes Critical Red with 1:10 battery left Status in Ayatana Design: Fix Released Status in The Power Indicator: Fix Released Status in indicator-power package in Ubuntu: Fix Released Bug description: Binary package hint: ubuntu-mono Since the Ubuntu-Monochrome 0.0.26 upload, the battery status icon now goes critical red with over an hour to spare. We need to confirm this in Ayatana-Design, but my hunch is the following would be more useful: external power: normal text colour (ivory/chocolate for Ambiance/Radiance) =1:00 remaining: normal text colour 1:00 remaining: orange non-critical warning =0:10 remaining: red critical warning =0:02 remaining: red critical warning if suspend/hibernate action selected and proven working =0:02 remaining: red critical (flashing) warning if simply going to power-off Additionally, the Ubuntu Mono 0.0.26 change uses a battery icon with no fill for empty. This is not as clear to the user as an icon that instead uses a very small fill at end of the battery, even for zero. This is more intuitive as it makes it clear that the icon is used as a percentage indicator; with an empty fill the user must already know this for empty to be useful as a relative indicator. At the moment, the Red with some left state seen at 1:10 remaining is far more visible to the user than the (more serious) completely empty icon. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/743823/+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 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
ubuntu-touch-session sync ** Changed in: canonical-devices-system-image Importance: Undecided = High ** Changed in: canonical-devices-system-image Status: New = Confirmed ** Changed in: canonical-devices-system-image Milestone: None = ww05-2015 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1389008 Title: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control) Status in the base for Ubuntu mobile products: Confirmed Status in indicator-sound package in Ubuntu: Invalid Status in ubuntu-touch-session package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid Status in indicator-sound package in Ubuntu RTM: Invalid Status in ubuntu-touch-session package in Ubuntu RTM: Confirmed Status in unity8 package in Ubuntu RTM: Invalid Bug description: Often after boot indicator-sound fails to connect to Pulseaudio and to unity-notifications using libnotify. Therefore, volume notifications aren't shown and changes to the volume role go unnoticed, which then results in improper volume control. As already mentioned in the original bug description, running restart indicator-sound resolves the issue. Original description: Happens often after phone boot where changing volume by touch or by phone buttons. Volume correctly changes, but the org.freedesktop.Notifications popup isn't displayed. The problem seems fixes itself if you run restart indicator-sound, so maybe there's an issue with i-sound and unity-notifications starting at the same time, with the former querying the latter's capabilities before it's ready for business? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1389008/+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 1403349] Re: Right click items in Launcher, pop up a menu, the menu will disappear after move the mouse
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1403349 ** Tags added: iso-testing -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1403349 Title: Right click items in Launcher, pop up a menu, the menu will disappear after move the mouse Status in Ubuntu Kylin: New Status in unity package in Ubuntu: New Bug description: Right click items in Launcher, pop up a menu, the menu will disappear after move the mouse. This problem only exists in vivid x32 system. 右键点击启动栏的项目，弹出一个小菜单。移动鼠标后，小菜单消失。该问题只在vivid32位系统上发现 Steps: 1. Install the latest OS(Vivid x32 Daily Build 20141214) 2. Log in the system, right click the items in Launcher 3. After a menu pop up, move the mouse --Failed. The menu disappear Configuration: OS: Vivid x32 Daily Build 20141214 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1403349/+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 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu) Status: Confirmed = Invalid ** Changed in: unity8 (Ubuntu RTM) Status: New = Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1389008 Title: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control) Status in the base for Ubuntu mobile products: New Status in indicator-sound package in Ubuntu: Invalid Status in ubuntu-touch-session package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid Status in indicator-sound package in Ubuntu RTM: Invalid Status in ubuntu-touch-session package in Ubuntu RTM: Confirmed Status in unity8 package in Ubuntu RTM: Invalid Bug description: Often after boot indicator-sound fails to connect to Pulseaudio and to unity-notifications using libnotify. Therefore, volume notifications aren't shown and changes to the volume role go unnoticed, which then results in improper volume control. As already mentioned in the original bug description, running restart indicator-sound resolves the issue. Original description: Happens often after phone boot where changing volume by touch or by phone buttons. Volume correctly changes, but the org.freedesktop.Notifications popup isn't displayed. The problem seems fixes itself if you run restart indicator-sound, so maybe there's an issue with i-sound and unity-notifications starting at the same time, with the former querying the latter's capabilities before it's ready for business? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1389008/+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 892370] Re: The time zone for China should default to Beijing not Shanghai (when offline)
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/892370 ** Tags added: iso-testing -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/892370 Title: The time zone for China should default to Beijing not Shanghai (when offline) Status in The Date and Time Indicator: New Status in OEM Priority Project: Won't Fix Status in OEM Priority Project oneiric series: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in OEM Priority Project quantal series: Won't Fix Status in OEM Priority Project raring series: Won't Fix Status in Ubuntu Kylin: New Status in indicator-datetime package in Ubuntu: In Progress Status in libtimezonemap package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Confirmed Status in indicator-datetime source package in Quantal: Won't Fix Status in libtimezonemap source package in Quantal: Won't Fix Status in ubiquity source package in Quantal: Won't Fix Status in indicator-datetime source package in Raring: Won't Fix Status in libtimezonemap source package in Raring: Fix Released Status in ubiquity source package in Raring: Won't Fix Status in indicator-datetime source package in Saucy: Won't Fix Status in libtimezonemap source package in Saucy: Fix Released Status in ubiquity source package in Saucy: Won't Fix Bug description: When installing Ubuntu and selecting Simplified Chinese as the default language, the default timezone should point to Beijing instead of Shanghai. Everything in China is referenced to Beijing time. In mainland China this standard time is called Beijing Time (北京时间) domestically but it is commonly referred to as China Standard Time (CST) internationally. This seems to have come up a lot in past bugs: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/228554 https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/517621 Steps to recreate: 1) Install Ubuntu and select Simplified Chinese for the language. Actual Results: At the timezone page, the default city is Shanghai. Expected Results: Most Chinese users prefer it be set to Beijing. It looks as if the upstream tz database needs to be updated for Beijing for starters, as Beijing is not listed in there. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: tzdata 2011n-0ubuntu0.11.10 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Nov 18 15:26:03 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: tzdata UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/892370/+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 1181536] Re: LG Display LGD-MultiTouch: loosing clic on Unity after few touchs
@isi, does it happen after few clicks or all the time? Did you change the scaling settings in Control Center - Display panel? -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1181536 Title: LG Display LGD-MultiTouch: loosing clic on Unity after few touchs Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: If logging in Unity, i loose clic after 3-4 touchs on DELL st2220t (1fd2:0064). It doesn't occur when logging in Gnome ! Please help, i do like using Unity !!! ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8 Uname: Linux 3.8.0-21-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,obs,widget,grid,wobbly,resize,resizeinfo,mousepoll,place,move,imgpng,regex,vpswitch,gnomecompat,commands,winrules,session,animation,fade,cube,workarounds,animationaddon,scale,rotate,cubeaddon,td,expo,scaleaddon,ezoom,unitymtgrabhandles,unityshell] Date: Sat May 18 16:16:03 2013 InstallationDate: Installed on 2012-05-30 (352 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20120425-15:28 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to raring on 2013-05-05 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1181536/+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 1407523] Re: Unity in lockscreen mode does not allow password entry
*** This bug is a duplicate of bug 1311316 *** https://bugs.launchpad.net/bugs/1311316 ** Tags added: lockscreen ** This bug has been marked a duplicate of bug 1311316 After locking screen there is no input field to type password for unlock -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1407523 Title: Unity in lockscreen mode does not allow password entry Status in Unity: New Status in unity package in Ubuntu: New Bug description: Sometimes, when I come back to my computer after locking it, the password field is not displayed. This means I cannot enter the password, and I have to do an ungraceful shutdown of my X session. It only happens when the workstation has been running for a while (usually a few weeks) which leads me to suspect a memory leak, or similar. The unlock dialog box appears, but the password field is not rendered. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1407523/+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 1406085] Re: Overview mode - add option for the name windows to make it always visible
** Changed in: unity Status: New = Opinion ** Changed in: unity Importance: Undecided = Wishlist ** Changed in: unity Status: Opinion = Triaged ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1406085 Title: Overview mode - add option for the name windows to make it always visible Status in Unity: Triaged Status in unity package in Ubuntu: Confirmed Bug description: Can I make a overview mode, the name of each window, for example in Nautilus, would always show, not only for the transition to the desired window. The rest is left as it is - when you go to the window title is slightly increased, and it is highlighted, perhaps it is necessary to consider the allocation of the selected window, for example, to increase its illumination. So it would be easier to navigate not only the image, which can be nearly identical in several windows, but also in parallel by location/name of application windows. I think the idea increases the convenience and comfort of using the system ... the details of the implementation can certainly think. P.S. Ubuntu 14.04 -15.04 Example attached. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1406085/+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 1405398] Re: add custom sources to screenshot, for local applications
** Changed in: unity
Status: New = Opinion
** Changed in: unity
Importance: Undecided = Wishlist
** Also affects: unity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity (Ubuntu)
Status: New = Opinion
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1405398
Title:
add custom sources to screenshot, for local applications
Status in Unity:
Opinion
Status in unity package in Ubuntu:
Opinion
Bug description:
I have some local 'apps', that I use to make myself more productive.
While searching for the it via the DASH. I right clicked it to preview
it. And I found out there is no screen-shot(naturally), of my app.
Apparently to add a screen-shot to the unity dash, is by uploading it
here: http://screenshots.debian.net/upload, and that can only be done,
if there is an existing application, to upload a screen-shot for.
My apps are purely for my benefit and solely made for my current
setup. I don't think it would benefit anyone else.
My feature request - the short version - is: make it so that one
could add there own screen-shot sources/direct link:
1.
screenshot_sources {
'http://screenshots.debian.net/screenshots/',
'custom_path_to_screenshot'
}
2.
screenshot_MyApp {
'http://screenshots.debian.net/screenshots/existingappname.png',
'custom_path_to_screenshot/MyApp.png'
}
Or via the `.desktop` file.
Screenshot=/home/blah/MyApp/MyApp-screenshot.png
LONG VERSION:
I may not be with a company that uses Ubuntu as there default work
horse, but companies could definitely use such a feature. Most
companies have there own set of apps, some even developed in house.
It would be beneficial that those app could also be further integrated
in to the unity desktop without having to post there existence online.
I'm not just talking about screen-shot, although my knowledge is
somewhat limited on how far one could integrate there app in to unity,
locally. For that I leave you to your imagination.
This is just a feature that would make me more happier than I am right
now with Ubuntu. And I think it could make others happy to.
If you implement it, or not, I still wanna thank the team for taking
the time to look at this, and for all the hard work you guys put into
Ubuntu.
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1405398/+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 1407192] Re: firefox icon frequently replaced by placeholder
** Changed in: unity Status: New = Confirmed ** Also affects: bamf (Ubuntu) Importance: Undecided Status: New ** Changed in: bamf (Ubuntu) Status: New = Confirmed ** Also affects: bamf Importance: Undecided Status: New ** Changed in: bamf Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1407192 Title: firefox icon frequently replaced by placeholder Status in BAMF Application Matching Framework: Confirmed Status in Unity: Confirmed Status in bamf package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Several times over the last week I have noticed that the when I start firefox, the default icon is replaced by a grey square with a question mark in the center as shown in the attached image. The only fix I've found is to unlock firefox from the launcher, quit the program, search for firefox in the dash, manually drag the icon onto the launcher, and then open it(i.e. if I start firefox directly from the dash, the grey icon appears on the launcher again). I haven't noticed this occurring with any other program. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20141216-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 2 21:38:32 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fb43] InstallationDate: Installed on 2014-12-11 (23 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141210) MachineType: TOSHIBA Satellite L875D ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-28-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: PLCSC8 dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:svnTOSHIBA:pnSatelliteL875D:pvrPSKFQU-003034:rvnAMD:rnPLCSC8:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L875D dmi.product.version: PSKFQU-003034 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.916+git20141119-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Jan 1 20:07:44 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.2.901-1ubuntu3 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1407192/+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
