[Dx-packages] [Bug 1463667] [NEW] No shortcut number is assigned to the most recently opened window
Public bug reported: When an application that is not locked to the launcher is opened, its window doesn't get a shortcut number assigned. However, when I open another application, the previous one gets a number assigned, but the new one does not. Moving the application's icon around in the launcher also assigns it a shortcut. Note: I have less than 10 application icons in my launcher. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Jun 10 10:48:55 2015 InstallationDate: Installed on 2015-04-24 (46 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Attachment added: "Screenshot demonstrating the bug" https://bugs.launchpad.net/bugs/1463667/+attachment/4412362/+files/no_shortcut.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/1463667 Title: No shortcut number is assigned to the most recently opened window Status in unity package in Ubuntu: New Bug description: When an application that is not locked to the launcher is opened, its window doesn't get a shortcut number assigned. However, when I open another application, the previous one gets a number assigned, but the new one does not. Moving the application's icon around in the launcher also assigns it a shortcut. Note: I have less than 10 application icons in my launcher. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Jun 10 10:48:55 2015 InstallationDate: Installed on 2015-04-24 (46 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1463667/+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 888039] Re: Gradual degradation in desktop performance.
** Changed in: unity (Ubuntu) Assignee: Jason Smith (jassmith) => Ron Karoles (rkaroles) -- 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/888039 Title: Gradual degradation in desktop performance. Status in Unity: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity source package in Oneiric: Won't Fix Bug description: SRU test case: 1. start Ubuntu and use it for a few hours 2. After the constant usage of a few hours there general performance degrade noted 3. now install NUX from oneiric-proposed 4. The situation is much imporved =Original Report edit - This bug has been scoped down to a particular std:vector growing out of control inside of nux. Any report about degrading performance not related to this should be filed as new bugs. :) Thanks guys. Over the span of 1-3 days I see my desktop consistently become more sluggish. The functions most affected are window movement, file icon movement, and sometimes window resizing. Other animations (such as minimizing fades, switching desktops, expo mode) are not affected when this degradation occurs. They remain smooth; however, I have let the problem go on as long as to find out that eventually all desktop animations/effects will degrade, it just takes a lot lot longer. I find that my actual 3D gaming goes unaffected (though I have no data to back that up, perhaps it does). I have recorded the output of 'ps auxw' and have slowly watched the VSZ and RSS memory columns creep upwards. A fresh compiz session will see 675164 and 169860, respectively. After a day or two it will result in as high as 878552 and 255664. I have attached a log output from an hourly cron job (though I had suspended for a few days because of travel). After the degradation has occurred compiz will consistently use higher CPU. Dragging a terminal window while watching top: before: ~10%, after: ~30 percent. This has been an issue since 11.04 for me on both my Intel i915 and Nvidia (proprietary) machines (had an 8600 GT and upgraded to 560 GTX, both having the same issue). However, the nvidia machine is where it really hurts, _always_ happening within a day or two, while the i915 machine is pretty reliable overall with certain instances of degradation (used to be affected just as badly in 11.04). I will attach two videos demonstrating behavior before and after. --- ApportVersion: 1.23-0ubuntu4 Architecture: amd64 CheckboxSubmission: 33c9cec13de798ee31ce4ea2f2cbd4df CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 CompizPlugins: [core,detection,composite,opengl,decor,regex,winrules,compiztoolbox,animation,grid,vpswitch,snap,place,gnomecompat,resize,move,mousepoll,imgpng,workarounds,session,expo,wall,fade,scale,unityshell] DistroCodename: oneiric DistroRelease: Ubuntu 11.10 DistroVariant: ubuntu InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) NonfreeKernelModules: nvidia Package: compiz 1:0.9.6+bzr20110929-0ubuntu5vv1 PackageArchitecture: all ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Tags: oneiric running-unity oneiric running-unity ubuntu Uname: Linux 3.0.0-12-generic x86_64 UnreportableReason: This is not a genuine Ubuntu package UpgradeStatus: Upgraded to oneiric on 2011-10-13 (26 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/888039/+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 1238346] Re: on bootup wrong keyboard layout is recognized
I'm affected too on Ubuntu 14.04, in fact the keyboard is correctly configured on "Azerty" (fr) on lightdm, but it switch to "Qwerty" (en) when the desktop (Unity) starts. I have only the "Fr" as possible input mapping in the config panel. I must select the "Fr" icon in the top bar and click on "French" again to have the correct mapping for the keyboard. -- 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/1238346 Title: on bootup wrong keyboard layout is recognized Status in One Hundred Papercuts: Confirmed Status in Unity: New Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: This is a regression. I have two keyboard layouts activated, the Dvorak and the English US. The Dvorak should be the default keyboard. That is the way I have it set up, and it shows up in the task bar on top as En1, which is the Dvorak. However, when I start to type, it starts in QUERTY. ?? To correct this, I go to the task bar (where it shows EN1, or Dvorak), re-select the Dvorak, and then everything is fine. ?? I have another minor problem which should probably go on another bug, but happened at the same time. CTL-ALT-T doesn't bring up the terminal any more. No matter what keyboard I'm using. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.1+13.10.20131004-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Oct 10 21:20:39 2013 InstallationDate: Installed on 2013-08-12 (60 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130811) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1238346/+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 1170647] Re: After minimizing a Nautilus window of another partition or external media or Trash folder, clicking on the "Files" icon on the Launcher again doesn't restore the minimi
I'm affected too, I have 4 HDD in addition with my primary drive (SSD), and I have frequently the bug ! -- 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/1170647 Title: After minimizing a Nautilus window of another partition or external media or Trash folder, clicking on the "Files" icon on the Launcher again doesn't restore the minimized window, but opens a new one Status in One Hundred Papercuts: Triaged Status in Unity: Triaged Status in Vivid OPM Workspace: New Status in unity package in Ubuntu: Triaged Status in unity source package in Trusty: Confirmed Bug description: *** ISSUE *** HOW TO REPRODUCE 1. Connect a removable media to the computer. 2. On the launcher, click on the "Files" icon. 3. On the left sidebar, click on the removable media icon or the trash. 4. Minimize the window. 5. Click on the "Files" icon. EXPECTED BEHAVIOUR - The Files window to be maximized. REAL BEHAVIOUR - A new window is opened. RELEVANT DETAILS - One way to navigate between windows at this moment is to use the "control + tabulation" key combination, or to click again on the "Files" icon so windows are exposed. Otherwise the minimized window Can be restored by clicking on the Volume's launcher icon or scrolling on the Files icon ** SOLUTION ** WORK-AROUND - On the launcher, left click on the "Files" icon and select the "unlock from Launcher" option. FIX - The launcher icon for "Files" to be treated the same way as if it was unlocked. REGRESSION POTENTIAL - Clicking on the "Files" icon won't send the user to its home folder, but to the latest opened Files window. TECHNICAL INFO ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Fri Apr 19 11:33:13 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'814x493+136+38'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'182' InstallationDate: Installed on 2011-07-23 (635 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1170647/+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 1046190] Re: Migration to gsettings doesn't migrate compiz/unity configurable keys to g-c-c and those keys doesn't work
** Changed in: unity (Ubuntu) Assignee: Łukasz Zemczak (sil2100) => (unassigned) ** Changed in: unity Assignee: Łukasz Zemczak (sil2100) => (unassigned) -- 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/1046190 Title: Migration to gsettings doesn't migrate compiz/unity configurable keys to g-c-c and those keys doesn't work Status in Compiz: Fix Released Status in Unity: Triaged Status in Unity Distro Priority: Fix Committed Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Triaged Bug description: From the test case "TESTING THE MIGRATION" from bug #1035261 1. open gnome-control-center, go to the keyboard shorcut panel 2. open, "systems" -> notice that the keys are "disabled" by default, (same in "launchers", "navigation" and other compiz/unity contents) --> on a migrated session, the keys should be migrated and appearing here --> on a guest session, the default keybindings should be shown. Note that this only impact the g-c-c org.compiz.integrated keys. Those are not migrated nor have a default value (even if I disagree and that's an hackish workaround). What needs to be done: 1. migrate the current compiz gconf profile keys to .integrated scheme as well 2. set default values for those so that a guest session shows default values for them. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1046190/+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 1463238] Re: luks / encrypted volume can not be closed
** Summary changed: - lukes / encrypted volume can not be closed + luks / encrypted volume can not be closed -- 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/1463238 Title: luks / encrypted volume can not be closed Status in udisks2 package in Ubuntu: New Status in unity package in Ubuntu: New Bug description: If you install ubuntu with the default full disk encryption option, it creates a partition as a luks container holding an lvm physical volume, which holds two logical volumes: one for root and one for swap. If you boot the livecd, it shows an encrypted disk icon on the unity launcher. Clicking this icon prompts for the luks password and then opens it, and the lvm inside is automatically mounted. The encrypted physical volume vanishes from the unity launcher and the contained root partition is auto mounted. Unmounting this partition still leaves the luks volume unlocked so you can remount it without having to supply the encryption password. Using the gnome disks utility to unlock the luks volume causes it to show up as if it is a sub-partition of the luks partition, and trying to click the lock icon to close the luks volume results in a giant error dialog because it is in use by the lvm volumes. It should be smart enough to deactivate the vg contained in the luks volume so it can then deactivate the luks volume. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1463238/+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 1445106] Re: [Notifications] turn the screen on
i assume IOS also locks down all kinds of input while the device is locked ... we dont really do that currently, so you can still slide the indicator bar or the launcher causing unexpected results ... -- 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/1445106 Title: [Notifications] turn the screen on Status in Ubuntu UX bugs: Triaged Status in indicator-messages package in Ubuntu: Confirmed Bug description: Built: r20 When getting a notification, such as a text message, the screen will turn on. This becomes a problem when the device is kept in a pocket, where it may falsely register screen activity and thus stay on for hours. -UX comment- Please refer for the correct behaviour here: https://docs.google.com/a/canonical.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit?pli=1# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1445106/+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 1463353] Re: Notifications not translated on first boot
Probably the locale is not correctly propagated to all the programs, so it's not a problem of indicator-messages, but of the installation wizard. ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- 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/1463353 Title: Notifications not translated on first boot Status in indicator-messages package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Needs a krillin with SD card and working SIM card. Test case. - Flash a new image. - Complete the installation wizard. - Make a call to the device (missed one). - Open the notification indicator. Expected result. - SD Card and missed call notifications are not translated on first boot. After rebooting the phone, the notifications appear translated. current build number: 28 device name: krillin channel: rc-proposed/bq-aquaris.en To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1463353/+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 1463353] [NEW] Notifications not translated on first boot
Public bug reported: Needs a krillin with SD card and working SIM card. Test case. - Flash a new image. - Complete the installation wizard. - Make a call to the device (missed one). - Open the notification indicator. Expected result. - SD Card and missed call notifications are not translated on first boot. After rebooting the phone, the notifications appear translated. current build number: 28 device name: krillin channel: rc-proposed/bq-aquaris.en ** Affects: indicator-messages (Ubuntu) Importance: Undecided Status: New ** Tags: qa-silo ** Attachment added: "screenshot20150609_101611687.png" https://bugs.launchpad.net/bugs/1463353/+attachment/4411997/+files/screenshot20150609_101611687.png -- 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/1463353 Title: Notifications not translated on first boot Status in indicator-messages package in Ubuntu: New Bug description: Needs a krillin with SD card and working SIM card. Test case. - Flash a new image. - Complete the installation wizard. - Make a call to the device (missed one). - Open the notification indicator. Expected result. - SD Card and missed call notifications are not translated on first boot. After rebooting the phone, the notifications appear translated. current build number: 28 device name: krillin channel: rc-proposed/bq-aquaris.en To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1463353/+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 1419001] Re: Reminders trigger at the time of the event and not before by default
when inserting a new date into LOCAL calendar, having german timezone, entering no data, but saving this date, afterwards it is moved two hours before the entered time. -- 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/1419001 Title: Reminders trigger at the time of the event and not before by default Status in the base for Ubuntu mobile products: Confirmed Status in Calendar application for Ubuntu devices: Fix Released Status in indicator-datetime package in Ubuntu: Fix Released Status in qtorganizer5-eds package in Ubuntu: Invalid Bug description: Sync of google calendar. The Google calendar setting is set by default to notify 10 min prior to all meetings. Is it possible to get this default notification time from google with the sync? or can we add a setting for a default notification time in the calendar app? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419001/+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 1463332] [NEW] zeitgeist-datahub.vala:229: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!
Public bug reported: get that error logged into journalctl: org.gnome.zeitgeist.Engine[1675]: ** (zeitgeist-datahub:2083): WARNING **: zeitgeist-datahub.vala:229: Unable to get name "org.gnome.zeitgeist.datahub" on the bus! ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: zeitgeist-datahub 0.9.14-2.2ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17.3-0ubuntu4 Architecture: i386 CurrentDesktop: GNOME Date: Tue Jun 9 11:32:35 2015 SourcePackage: zeitgeist UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zeitgeist (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 wily -- You received this bug notification because you are a member of DX Packages, which is subscribed to zeitgeist in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1463332 Title: zeitgeist-datahub.vala:229: Unable to get name "org.gnome.zeitgeist.datahub" on the bus! Status in zeitgeist package in Ubuntu: New Bug description: get that error logged into journalctl: org.gnome.zeitgeist.Engine[1675]: ** (zeitgeist-datahub:2083): WARNING **: zeitgeist-datahub.vala:229: Unable to get name "org.gnome.zeitgeist.datahub" on the bus! ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: zeitgeist-datahub 0.9.14-2.2ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17.3-0ubuntu4 Architecture: i386 CurrentDesktop: GNOME Date: Tue Jun 9 11:32:35 2015 SourcePackage: zeitgeist UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1463332/+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 1463327] [NEW] Cannot "Lock to Launcher" Android Studio icon
Public bug reported: It does not matter if you select "Lock to Launcher" or not. Upon exiting Android Studio editor, the icon would disappear. Creating the .desktop file manually, also solves the problem only partially: upon clicking on the Android Studio icon, yet another Android Studio icon would appear in the bottom of the Unity bar -- see screenshot attached (look at the icon with a green calipers). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.5+14.04.20150521.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,grid,mousepoll,regex,vpswitch,snap,gnomecompat,place,wall,move,resize,imgpng,animation,expo,session,workarounds,ezoom,staticswitcher,fade,scale,unityshell] CurrentDesktop: Unity Date: Tue Jun 9 12:20:06 2015 InstallationDate: Installed on 2011-10-23 (1324 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-25 (380 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Attachment added: "screenshot.png" https://bugs.launchpad.net/bugs/1463327/+attachment/4411955/+files/screenshot.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/1463327 Title: Cannot "Lock to Launcher" Android Studio icon Status in unity package in Ubuntu: New Bug description: It does not matter if you select "Lock to Launcher" or not. Upon exiting Android Studio editor, the icon would disappear. Creating the .desktop file manually, also solves the problem only partially: upon clicking on the Android Studio icon, yet another Android Studio icon would appear in the bottom of the Unity bar -- see screenshot attached (look at the icon with a green calipers). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.5+14.04.20150521.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,grid,mousepoll,regex,vpswitch,snap,gnomecompat,place,wall,move,resize,imgpng,animation,expo,session,workarounds,ezoom,staticswitcher,fade,scale,unityshell] CurrentDesktop: Unity Date: Tue Jun 9 12:20:06 2015 InstallationDate: Installed on 2011-10-23 (1324 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-25 (380 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1463327/+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 1445106] Re: [Notifications] turn the screen on
To answer Oliver's question, iOS prevents pocket presses on notifications by requiring you to slide notifications on the lock screen, not just tap them. There are probably many other sane solutions. -- 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/1445106 Title: [Notifications] turn the screen on Status in Ubuntu UX bugs: Triaged Status in indicator-messages package in Ubuntu: Confirmed Bug description: Built: r20 When getting a notification, such as a text message, the screen will turn on. This becomes a problem when the device is kept in a pocket, where it may falsely register screen activity and thus stay on for hours. -UX comment- Please refer for the correct behaviour here: https://docs.google.com/a/canonical.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit?pli=1# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1445106/+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 1386111] Re: Keyboard shortcuts not working on Ubuntu 14.10 and 15.04
The short-cuts seem to work in tty7 but the gnome-shell is running in tty2. -- 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/1386111 Title: Keyboard shortcuts not working on Ubuntu 14.10 and 15.04 Status in Unity: New Status in eclipse package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: New Status in qtbase package in Ubuntu: Confirmed Status in texmaker package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Keyboard shortcuts do not work. E.g. F1 for quick compile, Strg+F for searching ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: texmaker 4.3-1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 27 11:01:56 2014 InstallationDate: Installed on 2014-04-18 (191 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: texmaker UpgradeStatus: Upgraded to utopic on 2014-10-25 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1386111/+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 1386111] Re: Keyboard shortcuts not working on Ubuntu 14.10 and 15.04
** Also affects: gnome-shell (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/1386111 Title: Keyboard shortcuts not working on Ubuntu 14.10 and 15.04 Status in Unity: New Status in eclipse package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: New Status in qtbase package in Ubuntu: Confirmed Status in texmaker package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Keyboard shortcuts do not work. E.g. F1 for quick compile, Strg+F for searching ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: texmaker 4.3-1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 27 11:01:56 2014 InstallationDate: Installed on 2014-04-18 (191 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: texmaker UpgradeStatus: Upgraded to utopic on 2014-10-25 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1386111/+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 1407220] Re: clock is sometimes missing in notification area
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/1407220 Title: clock is sometimes missing in notification area Status in indicator-datetime package in Ubuntu: Confirmed Bug description: After startup the clock in the notification area is sometimes missing. It looks quite random when the clock is missing and when not. The bug is similar to bug#1239710, but as comment #67 says. This bug is for the phone and I am running the desktop version of ubuntu 14.04 (x64). That is why a new bug report should be created. A workaround for the bug is to kill the indicator-datetime. It will be restarted and the clock will be visible after that. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140415.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 NonfreeKernelModules: tbs6982fe tbs6680fe tbs6923fe tbs6985se tbs6928se tbs6982se tbs6991fe tbs6618fe tbs6983fe tbs6922fe tbs6928fe tbs6991se tbs6290fe wl ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 3 10:23:40 2015 InstallationDate: Installed on 2014-03-30 (278 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140329) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1407220/+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
