[Dx-packages] [Bug 1161423] Re: Removing a webapp package doesn't remove its shortcut from the dash
Corresponding entries in indicator menus also remain after webapps are uninstalled. For example, after uninstalling unity-webapps- facebookmessenger, a "Facebook Messenger" entry (with a broken icon) remains in the messaging menu. -- 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/1161423 Title: Removing a webapp package doesn't remove its shortcut from the dash Status in One Hundred Papercuts: Triaged Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: ** STEPS TO REPRODUCE ** 1. Write into the Terminal "sudo apt-get install unity-webapps-gmail -y" 2. Write into the Terminal "sudo apt-get remove unity-webapps-gmail -y" 3. Press the "Super" key and type "gmail" * BEHAVIOUR * - EXPECTED: The webapp not to be available. - REAL: The webapp is still available. *** WORK-AROUND *** - Manually remove the app from "~/.local/share/applications" and "~/.icons". RELEVANT DETAILS - It affect any webapp. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.03.25.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4 Uname: Linux 3.8.0-15-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Mar 28 15:18:01 2013 InstallationDate: Installed on 2013-03-23 (4 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130323) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1161423/+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 1350536] Re: url-dispatcher report_recoverable_problem() handler triggers reports filed against upstart
** Also affects: url-dispatcher Importance: Undecided Status: New ** Changed in: url-dispatcher Importance: Undecided => High ** Changed in: url-dispatcher Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of DX Packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1350536 Title: url-dispatcher report_recoverable_problem() handler triggers reports filed against upstart Status in URL Dispatcher: New Status in “url-dispatcher” package in Ubuntu: New Bug description: Currently, the top crasher reported on arm for the phones is in url- dispatcher: https://errors.ubuntu.com/problem/e17057d970fd4d64e71eb28c6f18b8a6468df471 This is a recoverable error, reported by url-dispatcher's explicit "recoverable problem" handling. The problem is, a large number of these are being reported against *upstart* as the package. They're being correctly included in the right bucket, but since the package is listed as upstart instead of url-dispatcher, the version information is a bit junk. url-dispatcher's handler only sometimes calls /usr/share/apport/recoverable_problem with a pid. Sometimes it calls it without one. In that case, /usr/share/apport/recoverable_problem looks at the parent pid. However, if url-dispatcher *exits* before recoverable_problem processes the request, recoverable_problem will be reparented to upstart. There may be an underlying issue causing url-dispatcher to exit abnormally here, which we are subsequently not capturing. But I think url-dispatcher should be unconditionally passing a PID, to avoid this misbucketing. The other option would be to spawn recoverable_problem synchronously, to make sure the parent process doesn't exit before it's had a chance to look at it. That obviously has other tradeoffs, though. To manage notifications about this bug go to: https://bugs.launchpad.net/url-dispatcher/+bug/1350536/+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 974480] Re: Notification area whitelist is obsolete
Liferea, Geary, Qutim, Venom and other necessary and good programs do not working as they should on Ubuntu 14.04. Why do you deprive users habits and why you trim features? Why? Everything worked fine before, why should all break??? I'm upset and disappointed! -- 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/974480 Title: Notification area whitelist is obsolete Status in Ayatana Design: Fix Released Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Mark has asked us to consider retiring the notification area whitelist for 12.10. The application indicator system has been in place for two years now, which should be long enough for applications to adopt it. If the whitelist was retired, Java and Wine would be hard-coded as the only software still able to use the menu bar as if it was a notification area, because their developers don't necessarily know that Ubuntu even exists. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/974480/+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 1351452] [NEW] unity header corrupted with buzzing defects (see screenshot)
Public bug reported: Doesnt depends of your graphical card, drivers. Such squares and lines appears and dissapears quickly for a few seconds eveytime cursor is on the header. 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.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Aug 1 23:42:07 2014 InstallationDate: Installed on 2014-01-14 (199 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-18 (105 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Attachment added: "bug scrsht" https://bugs.launchpad.net/bugs/1351452/+attachment/4167629/+files/bug.png -- 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/1351452 Title: unity header corrupted with buzzing defects (see screenshot) Status in “unity” package in Ubuntu: New Bug description: Doesnt depends of your graphical card, drivers. Such squares and lines appears and dissapears quickly for a few seconds eveytime cursor is on the header. 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.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Aug 1 23:42:07 2014 InstallationDate: Installed on 2014-01-14 (199 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-18 (105 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1351452/+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 1351113] Re: password input box after suspend/resume was not focused but looked like it was; keyboard input was being intercepted by another window
@2 not sure. I'll restart now. By the way I've observed the issue again in the meantime at the very next suspend/resume. -- 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/1351113 Title: password input box after suspend/resume was not focused but looked like it was; keyboard input was being intercepted by another window Status in “unity” package in Ubuntu: New Bug description: This is a HUGE SECURITY ISSUE. I suspended, then I resumed. Upon resume, I was presented the usual screen where you have to insert the password to unlock the screen. The password input box had a blinking cursor, as expected. I tried to type the password but it appeared to be not responding to keystrokes (from an external usb keyboard), meaning the usual dots would not appear at every keystroke. I thought the external usb keyboard was not working (due to another known bug) so I plugged it to another port, with no luck. So I tried to use the builtin keyboard of the laptop, but it wouldn't (apparently) respond to keystrokes either. So I clicked with the mouse on the language selection indicator in the upper right corner of the screen, and selected the (unique and already selected) language: spanish. A posteriori I think this was irrelevant. What I guess was relevant is that I gave focus to anything other than the password input box and then clicked on the password input box again. So now it worked and I could type my password and unlock the screen. AND HERE'S THE TERRIFYING THING: after inserting the password and unlocking the screen, Google Chrome was the active window (because it had been prior to suspending), and in the active tab there was facebook open. In the status-update textarea there were all the keys that I had been hitting when trying to input the password. Do you realize the enormous security hazard here? If I had typed the whole password quickly without looking at the screen and hit Enter before realizing the keystrokes were not being intercepted by the password input box, I could have posted my password on facebook without seeing it. Perhaps even twice. Fortunately, I saw the keystrokes were not being registered from the very beginning, and reacted by repeating the first few characters several times, and then hitting random keys, so I only typed a nonsense sequence of characters that doesn't even remotely resemble my password and I never got to hit the Enter key anyway. So, to sum up the issue: - after resume, the password input box wasn't focused and it should have been - worse: it completely looked like it was focused, with a blinking cursor inside, so everything looked like keyboard was not working at all - worst of all: keystrokes were actually being intercepted by an active application (which was not visible because the screen was locked). NOTHING that is "behind" the locked screen should be able to intercept keystrokes or mouse interaction, under any circumstance. If you are not seing something, that something must be non-existent to keyboard and mouse interaction. This is far from systematically reproducible. This is the first time I have observed this, ever, and have no idea what triggered this. I suspend and resume very often on a daily basis so this must be something pretty rare. Yet it is hugely dangerous. My very real-life case could have led to posting my password on facebook. Imagine if the active window was a terminal and if you happen to have a funny password such as "sudo rm -f /*" 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: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Aug 1 02:40:29 2014 InstallationDate: Installed on 2013-10-11 (293 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1351113/+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 1310690] Re: Lock screen password field does not "capture" key press - password is disclosed in background application
You need to install your security updates to get unity 7.2.2+14.04.20140714-0ubuntu1.1 See: http://www.ubuntu.com/usn/usn-2303-1/ -- 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/1310690 Title: Lock screen password field does not "capture" key press - password is disclosed in background application Status in Unity: Expired Status in “unity” package in Ubuntu: Expired Bug description: The new lockscreen in Ubuntu 14.04 is really nice, however I noticed (by 2 times already) that the password field doesn't "capture" the key presses sometimes. Key presses are not registered by the field and it looks like it is frozen (except by the cursor blinking). What I had to do when this happened was to wait until the tentative expires (screen goes blank) and then try again - then it worked. However the application running in the foregroung (or background, if you consider the lockscreen is on top) received the key presses, i.e, my whole password - you can imagine the implications if it was a chat window. I'm using 14.04, upgraded by 04/17 from 12.04 - all packages updated. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1310690/+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 1310690] Re: Lock screen password field does not "capture" key press - password is disclosed in background application
I made a reinstall of ubuntu 14.1 64bit just a couple of days ago, this has happened to me several times since then. Still figuring out when it happens. Just recently when I started from suspended. No virtualbox running, just google chrome and a couple of terminals. -- 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/1310690 Title: Lock screen password field does not "capture" key press - password is disclosed in background application Status in Unity: Expired Status in “unity” package in Ubuntu: Expired Bug description: The new lockscreen in Ubuntu 14.04 is really nice, however I noticed (by 2 times already) that the password field doesn't "capture" the key presses sometimes. Key presses are not registered by the field and it looks like it is frozen (except by the cursor blinking). What I had to do when this happened was to wait until the tentative expires (screen goes blank) and then try again - then it worked. However the application running in the foregroung (or background, if you consider the lockscreen is on top) received the key presses, i.e, my whole password - you can imagine the implications if it was a chat window. I'm using 14.04, upgraded by 04/17 from 12.04 - all packages updated. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1310690/+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 1310690] Re: Lock screen password field does not "capture" key press - password is disclosed in background application
eslin@chef:~$ apt-cache policy unity unity: Installed: 7.2.2+14.04.20140714-0ubuntu1 Candidate: 7.2.2+14.04.20140714-0ubuntu1 Version table: *** 7.2.2+14.04.20140714-0ubuntu1 0 500 http://se.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 7.2.0+14.04.20140416-0ubuntu1 0 500 http://se.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages eslin@chef:~$ eslin@chef:~$ apt-cache policy gnome-screensaver gnome-screensaver: Installed: 3.6.1-0ubuntu13 Candidate: 3.6.1-0ubuntu13 Version table: *** 3.6.1-0ubuntu13 0 500 http://se.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status -- 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/1310690 Title: Lock screen password field does not "capture" key press - password is disclosed in background application Status in Unity: Expired Status in “unity” package in Ubuntu: Expired Bug description: The new lockscreen in Ubuntu 14.04 is really nice, however I noticed (by 2 times already) that the password field doesn't "capture" the key presses sometimes. Key presses are not registered by the field and it looks like it is frozen (except by the cursor blinking). What I had to do when this happened was to wait until the tentative expires (screen goes blank) and then try again - then it worked. However the application running in the foregroung (or background, if you consider the lockscreen is on top) received the key presses, i.e, my whole password - you can imagine the implications if it was a chat window. I'm using 14.04, upgraded by 04/17 from 12.04 - all packages updated. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1310690/+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 1337917] Re: Alarm does not ring when phone is muted
Raising priority to critical since this is a must for RTM and missing alarms due to the phone being silent doesn't look too good. ** Changed in: ubuntu-clock-app Importance: High => Critical ** Changed in: ubuntu-clock-app Status: Confirmed => Triaged -- 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/1337917 Title: Alarm does not ring when phone is muted Status in Clock application for Ubuntu devices: Triaged Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: I expect the alarm to go off even if the phone is muted. I am not sure if this is a simple fix or all the things mentioned at https://wiki.ubuntu.com/SilentMode need to be implemented first. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1337917/+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 1349128] Re: Ubuntu 14.04 lock screen doesn't accept keyboard input and sends it back to the underlying window (until using indicators)
It looks like this was fixed in Trusty, but I don't see any messages indicating it was fixed in Utopic. Can someone verify and ensure this is also fixed in the development release? Thanks ** Also affects: unity (Ubuntu Trusty) Importance: Undecided Status: New -- 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/1349128 Title: Ubuntu 14.04 lock screen doesn't accept keyboard input and sends it back to the underlying window (until using indicators) Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: New Bug description: After upgrading to Unity version 7.2.2+14.04.20140714-0ubuntu1 on Trusty, the lockscreen sometimes fails to take the keyboard focus away from Chrome. This might happen if there's a text selection in Chrome, and also when resuming after suspend. It doesn't always happen, as this is a race condition, but it's easy to reproduce by selecting the location bar in Chrome and then locking the screen. Workaround: click on any indicator in the upper right corner, and close the menu. After that, keyboard input is sent to the lockscreen again. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1349128/+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 1351389] [NEW] power off / restart and cancel buttoms too close together
Public bug reported: The 3 buttons are currently stacked vertically but: 1) The spacing between them looks cramped. 2) The height of each button is too low to be comfortable. If you compare this menu with the Android equivalent, on Android the buttons actually touch _but_ they are atleast as tall as a finger is wide. This seems like a good policy wrt height. We don't appear to be space-constrained here so I'd suggest making the buttoms more spaced out and taller. ** Affects: indicator-power (Ubuntu) Importance: Undecided Status: New ** Tags: avengers -- 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/1351389 Title: power off / restart and cancel buttoms too close together Status in “indicator-power” package in Ubuntu: New Bug description: The 3 buttons are currently stacked vertically but: 1) The spacing between them looks cramped. 2) The height of each button is too low to be comfortable. If you compare this menu with the Android equivalent, on Android the buttons actually touch _but_ they are atleast as tall as a finger is wide. This seems like a good policy wrt height. We don't appear to be space-constrained here so I'd suggest making the buttoms more spaced out and taller. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1351389/+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 1320999] Re: Drums sound when screen locks
Not sure it's a unity bug. For the moment it's better to subscribe other projects too. ** Also affects: gnome-power Importance: Undecided Status: New -- 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/1320999 Title: Drums sound when screen locks Status in Gnome Powermanager: New Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Since Trusty, the drums now sound when the screen locks. To reproduce, just leave your computer untouched for 10 minutes. I believe this is an unintentional side-effect of the use of unity-greeter instead of gnome-screensaver. I can't see any usability benefit, and it can even be mildly annoying. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Tags: trusty Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-03-05 (82 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/1320999/+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 1332509] Re: Lockscreen misses arrow activator.
** Tags added: lockscreen -- 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/1332509 Title: Lockscreen misses arrow activator. Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Unity lock screen password entry should have an activator arrow like unity-greeter. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1332509/+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 1333935] Re: Unity now prompts 2 unlock screen upon resuming from suspend
** Tags added: lockscreen -- 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/1333935 Title: Unity now prompts 2 unlock screen upon resuming from suspend Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: For some unknown reasons, when I resume my Ubuntu from suspend, I am prompted with the old unlock screen (one that we had before Trusty) and subsequently the new Unity built-in unlock screen after I unlocked the old lock screen http://i.imgur.com/CBah4Hk.jpg http://i.imgur.com/ANCLKdk.jpg ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.1+14.04.20140513-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 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: Tue Jun 24 20:06:04 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.12, 3.13.0-27-generic, i686: installed vboxhost, 4.3.12, 3.13.0-29-generic, i686: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:a001] Subsystem: Intel Corporation Device [8086:a001] InstallationDate: Installed on 2014-04-01 (84 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily i386 (20140331) MachineType: Intel Corporation Pine Trail - M CRB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=cb7acec2-e0c5-4138-beb9-da46e06eaa8e ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.asset.tag: PTL Nanjing dmi.board.name: Pine Trail - M CRB dmi.board.vendor: Intel Corporation dmi.board.version: Revision A dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2010:svnIntelCorporation:pnPineTrail-MCRB:pvrRevisionA:rvnIntelCorporation:rnPineTrail-MCRB:rvrRevisionA:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: Pine Trail - M CRB dmi.product.version: Revision A dmi.sys.vendor: Intel Corporation version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Jun 23 11:26:59 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17 vendor INL xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1333935/+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 1340125] Re: Notification Center icon looks like an alarm is set
** Summary changed: - Alarm indicator visible when no alarms set + Notification Center icon looks like an alarm is set ** Description changed: - Not sure if it's a unity8 bug, actually. + The Notification Center indicator icon is a bell. - Do we really need the alarm indicator, when there's no alarms? + This makes it look as if a clock alarm is set when it is not. ** Changed in: indicator-datetime Status: Incomplete => Confirmed ** Also affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-themes Importance: Undecided Status: New ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- 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/1340125 Title: Notification Center icon looks like an alarm is set Status in The Date and Time Indicator: Confirmed Status in Themes for Ubuntu: New Status in “indicator-datetime” package in Ubuntu: New Status in “ubuntu-themes” package in Ubuntu: New Bug description: The Notification Center indicator icon is a bell. This makes it look as if a clock alarm is set when it is not. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1340125/+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 1351033] Re: Lock screen asks for password, should be passcode #163
** Branch linked: lp:~mterry/unity8/wrong-password-handling -- 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/1351033 Title: Lock screen asks for password, should be passcode #163 Status in “unity” package in Ubuntu: New Bug description: In System Settings -> Security, set a 4 digit "passcode". Lock screen, get asked to "Please enter password". It should be consistent, lock screen should ask for a passcode if one is set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1351033/+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 1350952] Re: replace the text "Empty!" with something more useful
** Changed in: ubuntu-ux Assignee: (unassigned) => Daniela Ferrai (dferrai) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1350952 Title: replace the text "Empty!" with something more useful Status in Ubuntu UX bugs: New Status in “indicator-messages” package in Ubuntu: New Bug description: when clearing the menu on this indicator (and others), the text "Empty!" is displayed. Can we please remove that and put something more useful there. It looks bad. Need advise from design.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1350952/+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 848011] Re: Restart required notification not shown in the shutdown menu after installing updates that require reboot
** No longer affects: hundredpapercuts -- 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/848011 Title: Restart required notification not shown in the shutdown menu after installing updates that require reboot Status in The Session Menu: Fix Released Status in Unity Foundations: Fix Released Status in “indicator-session” package in Ubuntu: Invalid Bug description: When the updates that require system reboot are installed there used to be a notification in the shutdown menu that a restart is required and the shutdown icon will be red. This is now missing. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/848011/+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 848011] Re: Restart required notification not shown in the shutdown menu after installing updates that require reboot
This is no longer part of the design. ** Changed in: indicator-session (Ubuntu) Status: In Progress => Invalid -- 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/848011 Title: Restart required notification not shown in the shutdown menu after installing updates that require reboot Status in One Hundred Papercuts: New Status in The Session Menu: Fix Released Status in Unity Foundations: Fix Released Status in “indicator-session” package in Ubuntu: Invalid Bug description: When the updates that require system reboot are installed there used to be a notification in the shutdown menu that a restart is required and the shutdown icon will be red. This is now missing. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/848011/+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 1310490] Re: Doesn't register to use the messaging menu (indicator-messages) on 14.04 LTS
indicator-messages now includes an example of how this should be done. Could you please fix gm-notify, please? Thanks. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicate in Ubuntu. https://bugs.launchpad.net/bugs/1310490 Title: Doesn't register to use the messaging menu (indicator-messages) on 14.04 LTS Status in Highly Ubuntu integrated GMail Notifier: Confirmed Status in Libindicate: Confirmed Status in “gm-notify” package in Ubuntu: Confirmed Status in “libindicate” package in Ubuntu: Confirmed Bug description: I've recently upgraded from Ubuntu 12.04.4 LTS to 14.04 LTS. I've noticed, that the mail icon (indicator-messages) is hidden (I don't use Thunderbird, so it is not installed.) I know, that it is hidden, because I'm using GMail Notifier, which displays itself if new mail has arrived, and it works. Package info: gm-notify: Installed: 0.10.3-0ubuntu3 Candidate: 0.10.3-0ubuntu3 Version table: *** 0.10.3-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status indicator-messages: Installed: 13.10.1+14.04.20140410-0ubuntu1 Candidate: 13.10.1+14.04.20140410-0ubuntu1 Version table: *** 13.10.1+14.04.20140410-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status python-indicate: Installed: 12.10.1-0ubuntu3 Candidate: 12.10.1-0ubuntu3 Version table: *** 12.10.1-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status $ gsettings get com.canonical.indicator.messages applications @as [] Please fix this issue! To manage notifications about this bug go to: https://bugs.launchpad.net/gm-notify/+bug/1310490/+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 1311403] Re: Can't type password after resume.
*** This bug is a duplicate of bug 1349128 *** https://bugs.launchpad.net/bugs/1349128 I experienced the same behaviour as Jeremy, but it is not reliable. E.g., after lightdm restart everything seems to work properly. Not sure if the same as #1349128, because in my case the password input box inside the login box is not displayed at all. If it can be helpful, in my case Synergy is running and Chrome is not. -- 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/1311403 Title: Can't type password after resume. Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I couldn't type password after resume - no characters displayed this time. I had to Ctrl+alt+f2 and service lightdm restart. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Tue Apr 22 17:37:49 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-23 (150 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-04-19 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311403/+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 1346355] Re: 14.04 power-cog does not turn red when restart is needed
Sorry, but this change was deliberate. A red icon may have worked for you, but that does not mean it worked for most or even many people. The red icon dates from the era when the rightmost menu was a "device menu", trying to cover everything from attached printers to external displays to software updates to screen locking, which was absurd. Nowadays everything to do with software updates is integrated into Software Updater, including the restart notification. It will sometimes be true that the alert appears when it's not a good time to restart; but you can leave it open (even minimized) until you're ready. ** Changed in: indicator-session Status: New => Invalid -- 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/1346355 Title: 14.04 power-cog does not turn red when restart is needed Status in The Session Menu: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: In ubuntu 12.04 the power-cog turned red when a reboot/restart was needed. This was a helpful feature because it informed users that they needed to restart the computer. But this helpful indicator is gone in 14.04 and it has resulted in me never remembering to restart my computer because there is no helpful feedback from ubuntu that a restart is needed. In 14.04, I will perform an update and a popup tells me a Restart is needed but I usually select to restart-later because I am in the middle of working. By the the time I am done working I have forgotten that a restart is needed. Later when I am working again a popup occurs informing me that a restart is needed (but again I am in the middle of working so I don't restart). Bottom line: when the power-cog turned red, it reminded me that I needed to restart the computer. When I finished my work I look up and see the red power-cog and "Oh yeah, I need to restart. Now is a good time." In 14.04 this doesn't happen. Instead I'm perpetually bugged by a popup (which is useless because it's never a good time to restart when it pops up). The red power-cog was a much BETTER design choice. The removal of the power-cog turning red has negatively affected the management of ubuntu updates and it should be fixed so that it behaves like 12.04. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1346355/+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 1262022] Re: incorrect multi-arch related meta information.
This package is handled by the automatic CI train machinery, so I can't just sponsor it. -- You received this bug notification because you are a member of DX Packages, which is subscribed to overlay-scrollbar in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1262022 Title: incorrect multi-arch related meta information. Status in “overlay-scrollbar” package in Ubuntu: Triaged Bug description: I'm on a 64-bit system trying to install "overlay-scrollbar-gtk2:i386" which depends on the "overlay-scrollbar:i386" package. "overlay- scrollbar:i386" doesn't have an install candidate because it's a "multi-arch" package. This should (or so I've been told) be reflected in the meta information of the "overlay-scrollbar" package but isn't, which is why the former package fails to install. As a more competent person than I put it: "The overlay-scrollbar package does not come in i386 or amd64 flavors; it comes as an "all" flavor, which installs on all archs. It appears to be missing the Multi-Arch: allowed header so it won't satisfy an i386 package depending on it. You should file a bug report asking that the missing header be added." ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: overlay-scrollbar 0.2.16+r359+13.10.20130826-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Dec 18 02:14:35 2013 InstallationDate: Installed on 2013-12-14 (3 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: overlay-scrollbar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1262022/+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 980519] Re: Random log off in Ubuntu 12.04 LTS
Wow got similar behavior as described in this bug just yesterday after an update. So when I log in and the Unity desktop should become visible the Welcome screen comes back asking again for a password. If I try XFCE I do get the desktop but when I try to start any programs there is a crash and the Welcome screen comes up asking for the password. I use Nvidia Quadro card and Ubuntu 13.10. So the bug might not be fixed. Before the update I didn't not have this issue. Kind regards. -- 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/980519 Title: Random log off in Ubuntu 12.04 LTS Status in Unity: Fix Released Status in “nvidia-graphics-drivers” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “xorg” package in Ubuntu: Fix Released Status in Fedora: New Bug description: I get logged off from Ubuntu sometimes. There is no error message or any indication that it is going to log off. The screen goes black, and after 2-4 seconds, i get presented with the Ubuntu Log On Screen. There is no clear pattern (or at least if have not noticed any). One time i am working with Netbeans, another time i am using firefox. This also means that at present i can not clearly say what package might be causing this behaviour. I am fairly sure the problem lies in 12.04 (or more precise - the combination of 12.04 and the hardware i am using). I do not have the same problem running 11.04 or 11.10. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/980519/+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
