[Dx-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1
** Bug watch removed: GNOME Bug Tracker #685676 https://bugzilla.gnome.org/show_bug.cgi?id=685676 ** Bug watch removed: GNOME Bug Tracker #162726 https://bugzilla.gnome.org/show_bug.cgi?id=162726 -- 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 Status in Aptana Studio Installer: New Status in Default settings for the Baltix GNU/Linux OS and desktop: New Status in LibreOffice Productivity Suite: Confirmed 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 The OpenOffice.org Suite: 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
** Bug watch removed: GNOME Bug Tracker #712669 https://bugzilla.gnome.org/show_bug.cgi?id=712669 -- 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 Status in Aptana Studio Installer: New Status in Default settings for the Baltix GNU/Linux OS and desktop: New Status in LibreOffice Productivity Suite: Confirmed 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 The OpenOffice.org Suite: 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 1350017] Re: [clock-app] There is no vibration when an alarm goes off
This bug was fixed in the package indicator-datetime - 13.10.0+14.10.20140808-0ubuntu1 --- indicator-datetime (13.10.0+14.10.20140808-0ubuntu1) utopic; urgency=low [ Charles Kerr ] * Add haptic feedback support for alarms. (LP: #1350017) * Have the shared Translations.cmake file look for .c, .cc, .cpp, .cxx, and .vala files. (LP: #1354058) -- Ubuntu daily releaseFri, 08 Aug 2014 20:52:54 + ** Changed in: indicator-datetime (Ubuntu) Status: In Progress => Fix Released -- 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/1350017 Title: [clock-app] There is no vibration when an alarm goes off Status in Clock application for Ubuntu devices: In Progress Status in Ubuntu UX bugs: Fix Committed Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: It'd be probably nice to also have vibration beside the sound alert when an alarm triggers. - Design Solution -- Giorgio Venturi updated the design spec for the clock app at [1]. The vibration will be enabled by default for all alarms. The user however will be provided a global setting to disable that if required. [1] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1350017/+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 1354058] Re: Translations.cmake doesn't pick up cc/cxx/cpp files
This bug was fixed in the package indicator-datetime - 13.10.0+14.10.20140808-0ubuntu1 --- indicator-datetime (13.10.0+14.10.20140808-0ubuntu1) utopic; urgency=low [ Charles Kerr ] * Add haptic feedback support for alarms. (LP: #1350017) * Have the shared Translations.cmake file look for .c, .cc, .cpp, .cxx, and .vala files. (LP: #1354058) -- Ubuntu daily releaseFri, 08 Aug 2014 20:52:54 + ** Changed in: indicator-datetime (Ubuntu) Status: New => Fix Released -- 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/1354058 Title: Translations.cmake doesn't pick up cc/cxx/cpp files Status in The Date and Time Indicator: In Progress Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: potfile-building rules in cmake/Translations.cmake checks for .vala and .c files, but not C++ files, so they don't get passed to xgettext. Frankly I don't understand how this didn't get spotted earlier, surely this is throwing off our translations for indicator-datetime? To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1354058/+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
** Bug watch removed: freedesktop.org Bugzilla #55585 https://bugs.freedesktop.org/show_bug.cgi?id=55585 -- 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 Status in Aptana Studio Installer: New Status in Default settings for the Baltix GNU/Linux OS and desktop: New Status in LibreOffice Productivity Suite: Confirmed 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 The OpenOffice.org Suite: 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 618587] Re: eclipse does not work with appmenu
** Project changed: audacity => unity-gtk-module -- You received this bug notification because you are a member of DX Packages, which is subscribed to libdbusmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/618587 Title: eclipse does not work with appmenu Status in Application menu module for GTK+: Invalid Status in Eclipse: Unknown Status in The Application Menu: Invalid Status in DBus Menu: Fix Released Status in Unity Foundations: Fix Released Status in Unity GTK+ module: Invalid Status in “libdbusmenu” package in Ubuntu: Fix Released Status in “libdbusmenu” source package in Natty: Won't Fix Bug description: Binary package hint: indicator-appmenu eclipse do not work ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: indicator-appmenu 0.0.9-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1 Uname: Linux 2.6.35-15-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Aug 16 13:06:20 2010 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100803.1) ProcEnviron: PATH=(custom, user) LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: indicator-appmenu To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-gtk/+bug/618587/+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 1268848] Re: Unity in 13.10 unstable with Radeon 7950
** Changed in: unity (Ubuntu) Status: Incomplete => New ** Package changed: unity (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: unity Status: Incomplete => 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/1268848 Title: Unity in 13.10 unstable with Radeon 7950 Status in Unity: Invalid Status in “linux” package in Ubuntu: Fix Released Bug description: About a month ago I installed a fresh Ubuntu 13.10 64bit on a i5 machine, 8GB RAM, with Radeon 7950 graphic card. Before this, I was running 12.04 64bit without any graphic driver related problems. I tried both Catalyst versions from official repository, latest 13.12 drivers from AMD site and open source drivers (radeon), and I can't tell which one was more unstable. After a few hours of use, I could not play any videos with any of the drivers (tried mplayer and VLC, both crashed with various errors), OpenGL isn't working anymore (even glxgears was crashing) and I had various artifacts on screen (like parts of window rendered on the wrong place on screen). Putting machine to sleep and waking it up later produced even more errors. I also tried to turn off various things in CCSM, without any positive results. Steam client had terrible flickering almost all the time, it was practically unusable; also about 8 of 10 times it was crashing on startup. After about two weeks of trying to make it usable, I gave up and installed MATE desktop. Not a single graphic error since then. Steam works flawlessly, 3D games also, Wine games, playing videos, everything. I kind of like how Unity works, I was using it for the last two years as my main desktop (on the same machine), but this behaviour is unexpected and utterly undesireable. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Jan 14 07:26:14 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: fglrx, 13.251, 3.11.0-14-generic, x86_64: installed fglrx, 13.251, 3.11.0-15-generic, x86_64: installed vboxhost, 4.3.6, 3.11.0-14-generic, x86_64: installed vboxhost, 4.3.6, 3.11.0-15-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950] [1002:679a] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:0424] InstallationDate: Installed on 2013-12-06 (38 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) JockeyStatus: kmod:fglrx - ATI Fire GL (Proprietary, Enabled, In use) kmod:fglrx_updates - Video driver for the AMD graphics accelerators (Proprietary, Disabled, Not in use) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic root=UUID=eab5c9d7-0979-4fae-9ed5-a26a530694de ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.00 dmi.board.name: Z68 Extreme4 Gen3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd07/08/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ68Extreme4Gen3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubu
[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
After restarting (several times) I've never observed the issue again, so I guess it was fixed by the update mentioned above. -- 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: Incomplete Status in “unity” package in Ubuntu: Incomplete 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/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 49579] Re: screen doesn't lock when some menu is open
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu Precise) 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/49579 Title: screen doesn't lock when some menu is open Status in GNOME Screensaver: Confirmed Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in X.Org X server: Confirmed Status in “gnome-screensaver” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Confirmed Status in “gnome-screensaver” source package in Precise: Confirmed Status in “unity” source package in Precise: Confirmed Status in “xorg-server” package in Debian: Confirmed Bug description: Binary package hint: gnome-screensaver I'm running a fresh install of Dapper with screensaver set to 'blank screen', and 'lock screen when screensaver is active' enabled. If a panel menu (e.g. Applications) is open and the machine is left idle, the screen fails to lock. It fades out after the time period as expected, but the desktop reappears after a few seconds. Ben (comments / criticism welcome, this is my first bug report) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+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 1086058] Re: my unity laucher and environment disappeared when i changed certain permission in dpkg file while installing hadoop.
Thanks for your comments. This does not appear to be a bug report and we are closing it. We appreciate the difficulties you are facing, but it would make more sense to raise your question in the support tracker. Please visit https://answers.launchpad.net/ubuntu/+addquestion ** Information type changed from Private Security to Public ** Changed in: unity Status: New => Invalid ** Changed in: unity (Ubuntu) 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/1086058 Title: my unity laucher and environment disappeared when i changed certain permission in dpkg file while installing hadoop. Status in Unity: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: my settings for flashdrive is not working. users and groups are disabled. error: configuration cannot be loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1086058/+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
** Changed in: unity (Ubuntu) Status: New => Incomplete ** Changed in: unity Status: New => Incomplete -- 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: Incomplete Status in “unity” package in Ubuntu: Incomplete 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/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 955193] Re: Menu bar - add option for the global menu to make it always visible
** This bug is no longer a duplicate of bug 682788 Improve Unity Global Menu ** Changed in: unity Importance: Undecided => Medium ** No longer affects: unity-2d ** Changed in: unity Milestone: backlog => 7.3.2 -- 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/955193 Title: Menu bar - add option for the global menu to make it always visible Status in Ayatana Design: Triaged Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: 1) In System Settings/Appearance/Behavior ( see section 2.2 of http://tinyurl.com/7c7nofq ), the "Application Menu" options should be "Integrated in menu bar and hidden" (default) and "Integrated in menu bar and visible" 2) If "Integrated in menu bar and visible" is selected, the menus should always be shown, in exactly the same manner they are currently displayed when the pointer is moved over the menu bar. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/955193/+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 1298903] Re: Lockscreen: ibus input method selection doesn't work in lock screen
** Changed in: unity Assignee: Brandon Schaefer (brandontschaefer) => Andrea Azzarone (andyrock) ** Changed in: unity/7.2 Assignee: (unassigned) => Andrea Azzarone (andyrock) ** Changed in: unity (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (andyrock) ** Also affects: indicator-keyboard Importance: Undecided Status: New ** Changed in: indicator-keyboard Assignee: (unassigned) => Andrea Azzarone (andyrock) ** Changed in: indicator-keyboard Status: New => In Progress ** Changed in: unity Status: Triaged => Invalid ** Changed in: unity (Ubuntu) Status: Triaged => Invalid ** Changed in: indicator-keyboard Importance: Undecided => Medium ** Changed in: unity/7.2 Status: Triaged => 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/1298903 Title: Lockscreen: ibus input method selection doesn't work in lock screen Status in Indicator keyboard: In Progress Status in Unity: Invalid Status in Unity 7.2 series: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: Earlier, I switched my ibus daemon to the Japanese/anthy input mode and locked my screen. I couldn't key in my password (consisting solely of ascii characters), as it appeared to be inputting everything in Japanese (the typical underlines were there, but everything was starred as it was a password input field). There didn't appear to be a way to switch it back to a standard qwerty input mode, so I was kind of stuck. Workaround: I managed to get back in by activating the switch user menu item and logging back in from there. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,copytex,compiztoolbox,decor,vpswitch,extrawm,text,resize,ring,screenshot,place,commands,put,mousepoll,move,gnomecompat,annotate,blur,clone,widget,regex,imgpng,animation,obs,workarounds,neg,bicubic,resizeinfo,grid,expo,session,wall,showmouse,ezoom,unitymtgrabhandles,fade,scale,scalefilter,showdesktop,scaleaddon,unityshell] CurrentDesktop: Unity Date: Fri Mar 28 17:56:06 2014 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-03 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-keyboard/+bug/1298903/+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 1354498] [NEW] Switcher Icons emblem (count) it's too small
Public bug reported: It should have a count emblem with a size proprtional on the icon size itself. ** Affects: unity Importance: Low Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: unity/7.2 Importance: Low Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: unity (Ubuntu) Importance: Low Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Tags: switcher ** Changed in: unity/7.2 Importance: Undecided => Low ** Changed in: unity/7.2 Status: New => In Progress ** Changed in: unity/7.2 Milestone: None => 7.2.3 ** Changed in: unity/7.2 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity (Ubuntu) Status: New => In Progress ** Changed in: unity (Ubuntu) Importance: Undecided => Low ** Changed in: unity (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Branch linked: lp:~3v1n0/unity/icons-emblem-scaling -- 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/1354498 Title: Switcher Icons emblem (count) it's too small Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: It should have a count emblem with a size proprtional on the icon size itself. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1354498/+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 1318997] Re: [clock] Provide a way to change alarm sound
** Changed in: ubuntu-clock-app Status: New => Won't Fix -- 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/1318997 Title: [clock] Provide a way to change alarm sound Status in The Date and Time Indicator: Fix Released Status in Clock application for Ubuntu devices: Won't Fix Status in Ubuntu Clock App reboot series: In Progress Status in Ubuntu UX bugs: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: The alarms API provides to way to set different alarm sounds for every alarm. Let's provide that feature to the users so that they can change the alarm sound while creating an alarm. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1318997/+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 682788] Re: Improve Unity Global Menu
Marco: that would be this bug: https://bugs.launchpad.net/ayatana- design/+bug/955193 - right? It is a duplicate of this one but has some design to it. -- 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/682788 Title: Improve Unity Global Menu Status in Ayatana Design: Fix Committed Status in Compiz: Invalid Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity-control-center” package in Ubuntu: Triaged Status in Baltix GNU/Linux: Confirmed Bug description: ===+++ _ ! ALL USERS ! _ +++=== ===+++ READ THIS BEFORE MAKING A COMMENT OR MODIFICATION +++=== IMPORTANT 1: Please don't post any "me too message"; use the "Does this bug affect you?" feature you can find a bit above this bug description on Launchpad. IMPORTANT 2: Do not post anything if you haven't read all comments to verify that your point hasn't been made. If you feel tempted to stop reading because there are too many messages, that is a strong indicator that you shouldn't add even more comments. Developers have a tough time to find anything if you post redundant stuff. So please abstain from doing that. = Global menu in general (not only in Unity) is very unergonomic on large screens (see the attached screenshot) because if you have a small window somewhere near the low right corner you have to move the cursor all the way up to to panel to reach the menu. I understand why the global menu was used for the netbook edition (it saves space and most windows are maximized), but since Unity is intended to be for the desktop edition there should be an option to switch to the traditional position of the app menu. It would be welcomed by many desktop users. Please try to find a solution for it that works. A commonly suggested solution is: [ ] Global Menu on [ ] Global Menu off [ ] Global Menu only for maximized windows The default is usually suggested as either the first (on) or last (on only for maximized windows). - Desired change: Implement the 'Enhanced Menu' project for 12.10. This project will address the issue described in this bug and also issues described in the duplicates of this bus. Note this is the 'official' bug that tracks the implementation of this project. The following options will be added to 'System Settings/Appearance': --- Menus Location:Global/Local Visibility: Hidden/Always displayed --- To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/682788/+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 682788] Re: Improve Unity Global Menu
@Aleve: This bug was actually fixed by the Locally Integrated Menus release, but as for the option to make the menus always visible is something that we're going to fix ASAP. By the way, since I think that it's a different bug, then I prefer to close this and moving to another clean bug for the visibility thing (and feel free to open it, if there isn't another). -- 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/682788 Title: Improve Unity Global Menu Status in Ayatana Design: Fix Committed Status in Compiz: Invalid Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity-control-center” package in Ubuntu: Triaged Status in Baltix GNU/Linux: Confirmed Bug description: ===+++ _ ! ALL USERS ! _ +++=== ===+++ READ THIS BEFORE MAKING A COMMENT OR MODIFICATION +++=== IMPORTANT 1: Please don't post any "me too message"; use the "Does this bug affect you?" feature you can find a bit above this bug description on Launchpad. IMPORTANT 2: Do not post anything if you haven't read all comments to verify that your point hasn't been made. If you feel tempted to stop reading because there are too many messages, that is a strong indicator that you shouldn't add even more comments. Developers have a tough time to find anything if you post redundant stuff. So please abstain from doing that. = Global menu in general (not only in Unity) is very unergonomic on large screens (see the attached screenshot) because if you have a small window somewhere near the low right corner you have to move the cursor all the way up to to panel to reach the menu. I understand why the global menu was used for the netbook edition (it saves space and most windows are maximized), but since Unity is intended to be for the desktop edition there should be an option to switch to the traditional position of the app menu. It would be welcomed by many desktop users. Please try to find a solution for it that works. A commonly suggested solution is: [ ] Global Menu on [ ] Global Menu off [ ] Global Menu only for maximized windows The default is usually suggested as either the first (on) or last (on only for maximized windows). - Desired change: Implement the 'Enhanced Menu' project for 12.10. This project will address the issue described in this bug and also issues described in the duplicates of this bus. Note this is the 'official' bug that tracks the implementation of this project. The following options will be added to 'System Settings/Appearance': --- Menus Location:Global/Local Visibility: Hidden/Always displayed --- To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/682788/+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 682788] Re: Improve Unity Global Menu
May I ask what fix was released, Marco, and what's exactly the nature of the fix? Has it been fixed for the current Ubuntu version (14.04.1) or is it fixed for an upcoming one? If it's the latter, which one: 14.10 or/and 14.04.2? -- 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/682788 Title: Improve Unity Global Menu Status in Ayatana Design: Fix Committed Status in Compiz: Invalid Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity-control-center” package in Ubuntu: Triaged Status in Baltix GNU/Linux: Confirmed Bug description: ===+++ _ ! ALL USERS ! _ +++=== ===+++ READ THIS BEFORE MAKING A COMMENT OR MODIFICATION +++=== IMPORTANT 1: Please don't post any "me too message"; use the "Does this bug affect you?" feature you can find a bit above this bug description on Launchpad. IMPORTANT 2: Do not post anything if you haven't read all comments to verify that your point hasn't been made. If you feel tempted to stop reading because there are too many messages, that is a strong indicator that you shouldn't add even more comments. Developers have a tough time to find anything if you post redundant stuff. So please abstain from doing that. = Global menu in general (not only in Unity) is very unergonomic on large screens (see the attached screenshot) because if you have a small window somewhere near the low right corner you have to move the cursor all the way up to to panel to reach the menu. I understand why the global menu was used for the netbook edition (it saves space and most windows are maximized), but since Unity is intended to be for the desktop edition there should be an option to switch to the traditional position of the app menu. It would be welcomed by many desktop users. Please try to find a solution for it that works. A commonly suggested solution is: [ ] Global Menu on [ ] Global Menu off [ ] Global Menu only for maximized windows The default is usually suggested as either the first (on) or last (on only for maximized windows). - Desired change: Implement the 'Enhanced Menu' project for 12.10. This project will address the issue described in this bug and also issues described in the duplicates of this bus. Note this is the 'official' bug that tracks the implementation of this project. The following options will be added to 'System Settings/Appearance': --- Menus Location:Global/Local Visibility: Hidden/Always displayed --- To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/682788/+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 1354023] Re: Screen contents are not being redrawn unless moving window off screen.
After some tests I can say it's compiz or nvidia blob. I have forced full scene repaints in CCSM for now. ** Also affects: compiz (Ubuntu) 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/1354023 Title: Screen contents are not being redrawn unless moving window off screen. Status in “compiz” package in Ubuntu: New Status in “unity” package in Ubuntu: New Bug description: Nvidia 340.24 Ubuntu 14.04.1 GTX 550Ti Let's say that I'm scrolling through web page in firefox. It's not redrawing so I have to drag window for it to redraw. Another example: I'm in Ubuntu Tweak, just toggled some stuff but it's not showing button change. I have to drag window off screen to properly redraw. Another example: Nautilus, I'm scrolling but it's not showing that it's scrolling. Again need to move window off screen and back to see changes. Another one: I'm writing right now and when I press Enter nothing happens, I have to press it again but cursor goes two rows down. Oh and now word "rows" is still in previous line with cursor so I have one ghost cursor and one in front. I think it's understandable now. I have this bug since 14.04 alpha, I though it's some dev crap and just made switch to Arch. Since 14.04.1 you have nice Vsync so I'm back. My guess: Someone at Cannonical tried to implement "reuse screen contents" from Kwin but failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1354023/+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 1343962] Re: Sound slider moves itself randomly when scrolling or moving sound pointer
I am having a similar issue, though I did not install ubuntu-sdk. I unfortunately don't know when this bug started happening as my install of Ubuntu 14.04.1 (from Live-CD) is only a few-days old. I attached my own sources.log. ** Attachment added: "sources.log" https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1343962/+attachment/4172834/+files/sources.log -- 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/1343962 Title: Sound slider moves itself randomly when scrolling or moving sound pointer Status in “indicator-sound” package in Ubuntu: Incomplete Bug description: I've described this bug in details at askubuntu.com :: http://askubuntu.com/questions/499268/strange-bug-with-sound-slider In brief: 1) Problem caused by installation of Ubuntu-SDK 2) Removing Ubuntu-SDK didn't fix the problem 3) This problem occurs only with desktop sound slider (notification slider). In Ubuntu sound settings, everything is fine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ActionStates: ({'next.vlc.desktop': (true, signature '', @av []), 'mute': (true, '', []), 'phone-settings': (true, '', []), 'mic-volume': (true, '', [<0.1183929443359375>]), 'scroll': (true, 'i', []), 'play-playlist.spotify.desktop': (true, 's', []), 'vlc.desktop': (true, '', [<{'running': , 'state': <'Paused'>}>]), 'desktop-settings': (true, '', []), 'previous.vlc.desktop': (true, '', []), 'play-playlist.vlc.desktop': (true, 's', []), 'spotify.desktop': (true, '', [<{'running': , 'state': <'Paused'>}>]), 'volume': (true, 'i', [<0.51992553710937495>]), 'play.spotify.desktop': (true, '', [<'Paused'>]), 'previous.spotify.desktop': (true, '', []), 'root': (true, '', [<{'title': <'Dźwięk'>, 'accessible-desc': <'Głośność (51%)'>, 'icon': <('themed', <['audio-volume-medium-panel', 'audio-volume-medium', 'audio-volume', 'audio']>)>, 'visible': }>]), 'next.spotify.desktop': (true, '', []), 'play.vlc.desktop': (true, '', [<'Paused'>])},) ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 18 12:28:16 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service InstallationDate: Installed on 2014-04-17 (91 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: PATH=(custom, no user) LANGUAGE=pl XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1343962/+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 1308572] Re: Ubuntu 14.04: security problem in the lock screen
Just another sidenote: I'm unaffected by this bug, because I always use xscreensaver instead of those newer unsecure rewrites. People concerned about security might want to read the http://www.jwz.org/blog/2014/04/the-awful-thing-about-getting-it-right-the-first-time-is-that-nobody-realizes-how-hard-it-was/ blog post of Jamie Zawinski who has written xscreensaver. -- 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/1308572 Title: Ubuntu 14.04: security problem in the lock screen Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: affects ubuntu Hello, I am running Ubuntu 14.04 with all the packages updated. When the screen is locked with password, if I hold ENTER after some seconds the screen freezes and the lock screen crashes. After that I have the computer fully unlocked. -- Marco Agnese This bug is about the lockscreen being bypassed when unity crashes/restarts, which is a critcal security issue. The crash will be handled from bug 1308750 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308572/+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 1354406] Re: 2nd of 2 alarms at same time is unclickable
Although this is a rare thing for me I understand that people do have overlapping meeting and personal alarms so this could happen more often than not. Having to reboot a phone to get into it because alarm crash the login screen is not great. ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided => High -- 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/1354406 Title: 2nd of 2 alarms at same time is unclickable Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: Steps to reproduce 1. Run recent image (I'm on #178 on mako) 2. Setup pin lock in system settings 3. Enter two events for the same time, soon, in your google calendar 4. Have your phone sync your google calendar using system settings -> accounts 5. Lock screen 6. Wait for the events What happens * Multiple alarms go off, notification on screen. You can hear two rings at once (separate bug) * Tap notification to make it go away * Sound continues, but there's no notification on screen. At this point you cannot unlock the phone. You can swipe away the welcome screen, but the display dims a bit once you do, and nothing is clickable - can't click numbers in pin unlock, can't swipe down indicators.. You have to reboot the phone to get past this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1354406/+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 1354406] Re: 2nd of 2 alarms at same time is unclickable
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-datetime (Ubuntu) Status: New => Confirmed -- 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/1354406 Title: 2nd of 2 alarms at same time is unclickable Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: Steps to reproduce 1. Run recent image (I'm on #178 on mako) 2. Setup pin lock in system settings 3. Enter two events for the same time, soon, in your google calendar 4. Have your phone sync your google calendar using system settings -> accounts 5. Lock screen 6. Wait for the events What happens * Multiple alarms go off, notification on screen. You can hear two rings at once (separate bug) * Tap notification to make it go away * Sound continues, but there's no notification on screen. At this point you cannot unlock the phone. You can swipe away the welcome screen, but the display dims a bit once you do, and nothing is clickable - can't click numbers in pin unlock, can't swipe down indicators.. You have to reboot the phone to get past this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1354406/+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 1354406] [NEW] 2nd of 2 alarms at same time is unclickable
Public bug reported: Steps to reproduce 1. Run recent image (I'm on #178 on mako) 2. Setup pin lock in system settings 3. Enter two events for the same time, soon, in your google calendar 4. Have your phone sync your google calendar using system settings -> accounts 5. Lock screen 6. Wait for the events What happens * Multiple alarms go off, notification on screen. You can hear two rings at once (separate bug) * Tap notification to make it go away * Sound continues, but there's no notification on screen. At this point you cannot unlock the phone. You can swipe away the welcome screen, but the display dims a bit once you do, and nothing is clickable - can't click numbers in pin unlock, can't swipe down indicators.. You have to reboot the phone to get past this. ** Affects: indicator-datetime (Ubuntu) Importance: High Status: Confirmed ** Description changed: Steps to reproduce 1. Run recent image (I'm on #178 on mako) 2. Setup pin lock in system settings 3. Enter two events for the same time, soon, in your google calendar 4. Have your phone sync your google calendar using system settings -> accounts 5. Lock screen 6. Wait for the events What happens * Multiple alarms go off, notification on screen. You can hear two rings at once (separate bug) * Tap notification to make it go away * Sound continues, but there's no notification on screen. At this point you cannot unlock the phone. You can swipe away the welcome screen, but the display dims a bit once you do, and nothing is clickable - can't click numbers in pin unlock, can't swipe down indicators.. + + You have to reboot the phone to get past this. -- 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/1354406 Title: 2nd of 2 alarms at same time is unclickable Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: Steps to reproduce 1. Run recent image (I'm on #178 on mako) 2. Setup pin lock in system settings 3. Enter two events for the same time, soon, in your google calendar 4. Have your phone sync your google calendar using system settings -> accounts 5. Lock screen 6. Wait for the events What happens * Multiple alarms go off, notification on screen. You can hear two rings at once (separate bug) * Tap notification to make it go away * Sound continues, but there's no notification on screen. At this point you cannot unlock the phone. You can swipe away the welcome screen, but the display dims a bit once you do, and nothing is clickable - can't click numbers in pin unlock, can't swipe down indicators.. You have to reboot the phone to get past this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1354406/+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 1354400] Re: Implement Alarm Snooze functionality
** Description changed: - Background Info - Currently the snap notification shown when an alarm is triggered shows the buttons "Ok" and "Show" which both does the same thing which is to dismiss the alarm. Since Snap notifications require a minimum of 2 buttons, the only choice is to implement the "Snooze" functionality and replace the "Show" button with "Snooze". However "Snooze" was decided to be implemented as part of the SDK Alarms API which is worked on by zsombor. As per the blueprint at [1], the snooze functionality was to be implemented in revision 0.2 (post-RTM). However we require a solution to the above issue before RTM. - Proposed Solution - It was decided after discussing with Mirco Mueller, Giorgio Venturi and Daniela Ferrai to implement the Snooze functionality as a workaround in the Indicator-datetime by dismissing the notification and showing it again after the snooze duration. The full design spec is described below. 1. Provide a settings option in dbus to set the snooze duration that the clock app can expose in the settings page to allow the user to choose the snooze duration. This is shown in [2]. The snooze duration options will be 2, 4, 5 and 10 minutes. 2. On pressing the "Ok" button in the snap notification, the alarm will be dismissed permanently for the day. 3. If the user pressed "Snooze", then indicator-datetime should dismiss the snap notification and show it again after the snooze duration. This process will be repeated until the alarm timeout defined by the user in the clock app settings. By default that timeout is 30 minutes. + This will require a Go/No-Go decision from Charles Kerr regarding the + implementation in indicator-datetime since as mentioned above this will + be a workaround and workaround are not permanent solutions. [1] https://blueprints.launchpad.net/ubuntu/+spec/sdk-system-alarm-api [2] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024 -- 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/1354400 Title: Implement Alarm Snooze functionality Status in Clock application for Ubuntu devices: Triaged Status in “indicator-datetime” package in Ubuntu: New Bug description: - Background Info - Currently the snap notification shown when an alarm is triggered shows the buttons "Ok" and "Show" which both does the same thing which is to dismiss the alarm. Since Snap notifications require a minimum of 2 buttons, the only choice is to implement the "Snooze" functionality and replace the "Show" button with "Snooze". However "Snooze" was decided to be implemented as part of the SDK Alarms API which is worked on by zsombor. As per the blueprint at [1], the snooze functionality was to be implemented in revision 0.2 (post- RTM). However we require a solution to the above issue before RTM. - Proposed Solution - It was decided after discussing with Mirco Mueller, Giorgio Venturi and Daniela Ferrai to implement the Snooze functionality as a workaround in the Indicator-datetime by dismissing the notification and showing it again after the snooze duration. The full design spec is described below. 1. Provide a settings option in dbus to set the snooze duration that the clock app can expose in the settings page to allow the user to choose the snooze duration. This is shown in [2]. The snooze duration options will be 2, 4, 5 and 10 minutes. 2. On pressing the "Ok" button in the snap notification, the alarm will be dismissed permanently for the day. 3. If the user pressed "Snooze", then indicator-datetime should dismiss the snap notification and show it again after the snooze duration. This process will be repeated until the alarm timeout defined by the user in the clock app settings. By default that timeout is 30 minutes. This will require a Go/No-Go decision from Charles Kerr regarding the implementation in indicator-datetime since as mentioned above this will be a workaround and workaround are not permanent solutions. [1] https://blueprints.launchpad.net/ubuntu/+spec/sdk-system-alarm-api [2] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1354400/+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 1354400] [NEW] Implement Alarm Snooze functionality
Public bug reported: - Background Info - Currently the snap notification shown when an alarm is triggered shows the buttons "Ok" and "Show" which both does the same thing which is to dismiss the alarm. Since Snap notifications require a minimum of 2 buttons, the only choice is to implement the "Snooze" functionality and replace the "Show" button with "Snooze". However "Snooze" was decided to be implemented as part of the SDK Alarms API which is worked on by zsombor. As per the blueprint at [1], the snooze functionality was to be implemented in revision 0.2 (post-RTM). However we require a solution to the above issue before RTM. - Proposed Solution - It was decided after discussing with Mirco Mueller, Giorgio Venturi and Daniela Ferrai to implement the Snooze functionality as a workaround in the Indicator-datetime by dismissing the notification and showing it again after the snooze duration. The full design spec is described below. 1. Provide a settings option in dbus to set the snooze duration that the clock app can expose in the settings page to allow the user to choose the snooze duration. This is shown in [2]. The snooze duration options will be 2, 4, 5 and 10 minutes. 2. On pressing the "Ok" button in the snap notification, the alarm will be dismissed permanently for the day. 3. If the user pressed "Snooze", then indicator-datetime should dismiss the snap notification and show it again after the snooze duration. This process will be repeated until the alarm timeout defined by the user in the clock app settings. By default that timeout is 30 minutes. This will require a Go/No-Go decision from Charles Kerr regarding the implementation in indicator-datetime since as mentioned above this will be a workaround and workaround are not permanent solutions. [1] https://blueprints.launchpad.net/ubuntu/+spec/sdk-system-alarm-api [2] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024 ** Affects: ubuntu-clock-app Importance: Critical Status: Triaged ** Affects: indicator-datetime (Ubuntu) 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/1354400 Title: Implement Alarm Snooze functionality Status in Clock application for Ubuntu devices: Triaged Status in “indicator-datetime” package in Ubuntu: New Bug description: - Background Info - Currently the snap notification shown when an alarm is triggered shows the buttons "Ok" and "Show" which both does the same thing which is to dismiss the alarm. Since Snap notifications require a minimum of 2 buttons, the only choice is to implement the "Snooze" functionality and replace the "Show" button with "Snooze". However "Snooze" was decided to be implemented as part of the SDK Alarms API which is worked on by zsombor. As per the blueprint at [1], the snooze functionality was to be implemented in revision 0.2 (post- RTM). However we require a solution to the above issue before RTM. - Proposed Solution - It was decided after discussing with Mirco Mueller, Giorgio Venturi and Daniela Ferrai to implement the Snooze functionality as a workaround in the Indicator-datetime by dismissing the notification and showing it again after the snooze duration. The full design spec is described below. 1. Provide a settings option in dbus to set the snooze duration that the clock app can expose in the settings page to allow the user to choose the snooze duration. This is shown in [2]. The snooze duration options will be 2, 4, 5 and 10 minutes. 2. On pressing the "Ok" button in the snap notification, the alarm will be dismissed permanently for the day. 3. If the user pressed "Snooze", then indicator-datetime should dismiss the snap notification and show it again after the snooze duration. This process will be repeated until the alarm timeout defined by the user in the clock app settings. By default that timeout is 30 minutes. This will require a Go/No-Go decision from Charles Kerr regarding the implementation in indicator-datetime since as mentioned above this will be a workaround and workaround are not permanent solutions. [1] https://blueprints.launchpad.net/ubuntu/+spec/sdk-system-alarm-api [2] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1354400/+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/List