[Dx-packages] [Bug 1315384] Re: python-indicate not showing up in message indictor
I was able to reproduce the bug both using the mentioned demo (im- client.py) and by using the Gajim libnotify plugin - neither works. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicate in Ubuntu. https://bugs.launchpad.net/bugs/1315384 Title: python-indicate not showing up in message indictor Status in “libindicate” package in Ubuntu: Confirmed Bug description: Install python-indicate and libindicate-doc. Run: python /usr/share/doc/libindicate/examples/im-client.py An entry should appear in message indicator, but does not. That worked in 12.04 but is broken in 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python-indicate 12.10.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 2 15:22:27 2014 InstallationDate: Installed on 2014-05-01 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libindicate UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libindicate/+bug/1315384/+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 1315384] Re: python-indicate not showing up in message indictor
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libindicate (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicate in Ubuntu. https://bugs.launchpad.net/bugs/1315384 Title: python-indicate not showing up in message indictor Status in “libindicate” package in Ubuntu: Confirmed Bug description: Install python-indicate and libindicate-doc. Run: python /usr/share/doc/libindicate/examples/im-client.py An entry should appear in message indicator, but does not. That worked in 12.04 but is broken in 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python-indicate 12.10.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 2 15:22:27 2014 InstallationDate: Installed on 2014-05-01 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libindicate UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libindicate/+bug/1315384/+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 1239710] Re: indicator-datetime or -session missing ~10% of the time
vanadium, it's possible for more than one bug to cause the same symptom. And commenting in the report of a fixed bug generally isn't a good way to get other bugs fixed. Instead, at a terminal please enter "ubuntu-bug indicator-datetime" (without quotes) to report the bug you're seeing. Thanks. -- 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, dx-packages https://bugs.launchpad.net/bugs/1239710 Title: indicator-datetime or -session missing ~10% of the time Status in The Date and Time Indicator: Fix Released Status in The Session Menu: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-session” package in Ubuntu: Fix Released Status in “indicator-datetime” source package in Saucy: Fix Released Status in “indicator-session” source package in Saucy: Fix Released Bug description: Impact: sometime indicator-session or datetime go missing in unity Test Case: start sessions until that happens (or not) Regression potential: the change is a one liner workaround for a glib lock, shouldn't create issue, just check that those indicators keep working as they should --- Indicator-datetime is not showing in the indicator bar today on image 96. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20131011-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.5-0ubuntu2 Architecture: armhf Date: Mon Oct 14 16:00:26 2013 InstallationDate: Installed on 2013-10-14 (0 days ago) InstallationMedia: Ubuntu 13.10 - armhf (20131014) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1239710/+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 1289477] Re: Display brightness can lag far behind moving the slider
On a Galaxy Nexus it was terrible. On a Nexus 4 it is much better, but both the slider and the emitted brightness still lag about half a second behind where I drag. Because the slider itself is lagging, I can't tell whether this is a toolkit problem, a System Settings problem, or a brightness subsystem problem. ** Also affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1289477 Title: Display brightness can lag far behind moving the slider Status in “indicator-power” package in Ubuntu: Fix Released Status in “ubuntu-system-settings” package in Ubuntu: New Bug description: Ubuntu Trusty r188 1. Access any of the brightness sliders: in System Settings > "Brightness", or System Settings > "Battery", or the Battery menu (bug 1289470). 2. Rapidly slide the slider from minimum to maximum and back again, about ten times, then let go. 3. Wait. What happens: The phone repeatedly dims and brightens over several seconds after you stop touching the slider. What should happen: The current brightness level is always either on, or less than ~500 ms from reaching, the brightness shown by the slider *right now*. Any values that the slider was on previously should be ignored. Compare bug 1306499, the equivalent problem with the volume slider. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1289477/+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 1316956] [NEW] Maximized windows move to the first monitor after wakeup
Public bug reported:
After wakeup, maximized windows always move to the first monitor ("LVDS
connected" here).
Unity panel is on second monitor ("VGA-0 connected primary").
$ xrandr
Screen 0: minimum 320 x 200, current 3286 x 1080, maximum 8192 x 8192
VGA-0 connected primary 1920x1080+1366+0 (normal left inverted right x axis y
axis) 531mm x 298mm
1920x1080 60.0*+
1680x1050 60.0
1600x900 60.0
1280x1024 75.0 60.0
1280x800 59.8
1152x864 75.0
1280x720 60.0
1024x768 75.1 60.0
832x62474.6
800x60075.0 60.3
640x48075.0 60.0
720x40070.1
LVDS connected 1366x768+0+312 (normal left inverted right x axis y axis) 309mm
x 174mm
1366x768 60.0*+ 50.0
1280x720 59.9
1152x768 59.8
1024x768 59.9
800x60059.9
848x48059.7
720x48059.7
640x48059.4
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 disconnected (normal left inverted right x axis y axis)
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Wed May 7 11:16:31 2014
InstallationDate: Installed on 2013-10-23 (195 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-04-18 (18 days ago)
** Affects: unity (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug trusty
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1316956
Title:
Maximized windows move to the first monitor after wakeup
Status in “unity” package in Ubuntu:
New
Bug description:
After wakeup, maximized windows always move to the first monitor ("LVDS
connected" here).
Unity panel is on second monitor ("VGA-0 connected primary").
$ xrandr
Screen 0: minimum 320 x 200, current 3286 x 1080, maximum 8192 x 8192
VGA-0 connected primary 1920x1080+1366+0 (normal left inverted right x axis y
axis) 531mm x 298mm
1920x1080 60.0*+
1680x1050 60.0
1600x900 60.0
1280x1024 75.0 60.0
1280x800 59.8
1152x864 75.0
1280x720 60.0
1024x768 75.1 60.0
832x62474.6
800x60075.0 60.3
640x48075.0 60.0
720x40070.1
LVDS connected 1366x768+0+312 (normal left inverted right x axis y axis)
309mm x 174mm
1366x768 60.0*+ 50.0
1280x720 59.9
1152x768 59.8
1024x768 59.9
800x60059.9
848x48059.7
720x48059.7
640x48059.4
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 disconnected (normal left inverted right x axis y axis)
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Wed May 7 11:16:31 2014
InstallationDate: Installed on 2013-10-23 (195 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
(20131016.1)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-04-18 (18 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1316956/+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 1315384] Re: python-indicate not showing up in message indictor
Because of this bug, gm-notify indicator is not shown. ** Also affects: libindicate Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicate in Ubuntu. https://bugs.launchpad.net/bugs/1315384 Title: python-indicate not showing up in message indictor Status in Libindicate: New Status in “libindicate” package in Ubuntu: Confirmed Bug description: Install python-indicate and libindicate-doc. Run: python /usr/share/doc/libindicate/examples/im-client.py An entry should appear in message indicator, but does not. That worked in 12.04 but is broken in 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python-indicate 12.10.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 2 15:22:27 2014 InstallationDate: Installed on 2014-05-01 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libindicate UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libindicate/+bug/1315384/+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 1315384] Re: python-indicate not showing up in message indictor
** Changed in: libindicate Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicate in Ubuntu. https://bugs.launchpad.net/bugs/1315384 Title: python-indicate not showing up in message indictor Status in Libindicate: Confirmed Status in “libindicate” package in Ubuntu: Confirmed Bug description: Install python-indicate and libindicate-doc. Run: python /usr/share/doc/libindicate/examples/im-client.py An entry should appear in message indicator, but does not. That worked in 12.04 but is broken in 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python-indicate 12.10.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 2 15:22:27 2014 InstallationDate: Installed on 2014-05-01 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libindicate UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libindicate/+bug/1315384/+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 1315434] Re: Mouse with no time remaining estimate showing in preference to battery being charged
Making it configurable obviously wouldn't "satisfy all user needs", because only a small fraction of users who might benefit from it would even know the option exists. Fewer still would comprehend *why* it exists, and even fewer than that would be bothered changing it. Making things worse, the added UI complexity would dissuade people from using the more-useful options around it. And the code would be less reliable, because engineers and testers would be allocating the same total amount of time to more code paths. And, after all that, we'd still have to decide what the default setting should be! So, no, we're not going to make this configurable. Instead let's concentrate on actually fixing the bug. I don't know how I missed seeing before that the mouse in question "has no time remaining estimate". That should automatically exclude it from being considered as the device that will discharge most quickly. ** Changed in: indicator-power (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1315434 Title: Mouse with no time remaining estimate showing in preference to battery being charged Status in “indicator-power” package in Ubuntu: In Progress Bug description: When my laptop battery is in a charging state, but is not fully charged, I expect it to be displayed in preference to my mouse, which has no time remaining estimate. The spec here: https://wiki.ubuntu.com/Power says: "If anything is discharging, the menu title should represent the component (not battery, but component) that is estimated to lose power first. For example, if your notebook battery is estimated to discharge in 1 hour 47 minutes, and your wireless mouse battery is estimated to discharge in 27 minutes, the menu title should represent the mouse. " but there doesn't seem to be any guideline to what happens when a battery is being charged. I suggest the time remaining to charge a battery should be displayed in preference to the power level in a wireless mouse. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 2 11:50:36 2014 InstallationDate: Installed on 2013-11-26 (156 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: indicator-power UpgradeStatus: Upgraded to trusty on 2014-01-17 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1315434/+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 1315384] Re: python-indicate not showing up in message indictor
libindicate has been deprecated in favor of libmessaging-menu in Quantal (12.10), becasue we couldn't use libindicate on the phone. Porting to libmessaging-menu is fairly simple. Let me know if you need any pointers. Note that this might change again when we switch to Unity8, which will most likely have a Qt/QML API as part of the SDK. Sorry about that. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicate in Ubuntu. https://bugs.launchpad.net/bugs/1315384 Title: python-indicate not showing up in message indictor Status in Libindicate: Confirmed Status in “libindicate” package in Ubuntu: Confirmed Bug description: Install python-indicate and libindicate-doc. Run: python /usr/share/doc/libindicate/examples/im-client.py An entry should appear in message indicator, but does not. That worked in 12.04 but is broken in 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python-indicate 12.10.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 2 15:22:27 2014 InstallationDate: Installed on 2014-05-01 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libindicate UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libindicate/+bug/1315384/+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 1300646] Re: XBMC steals input from the lockscreen
what is this fixed in? I still get it with Unity 7.2.0 and xbmc 13.0. The only solution is to switch terminals, kill xbmc, then switch back to the lock screen, click on the indicator (which regains focus) and then click on the password text input. If this is fixed by another bug then the bugs should be linked so that we can track the release. -- 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/1300646 Title: XBMC steals input from the lockscreen Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Steps to reproduce: * launch xbmc * suspend * resume Expected results: * screen is locked with the unity lockscreen * you can unlock the screen * no input goes to xbmc Current results: * screen is locked * you can't unlock, 'cause all the input goes to XBMC behind the lockscreen ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 1 09:05:06 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1300646/+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 1315384] Re: python-indicate not showing up in message indictor
Lars, do you have some pointer how libmessaging-menu is used in python? I will try to port the Gajim plugin "Ubuntu Ayatana Integration" to libmessaging-menu. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicate in Ubuntu. https://bugs.launchpad.net/bugs/1315384 Title: python-indicate not showing up in message indictor Status in Libindicate: Confirmed Status in “libindicate” package in Ubuntu: Confirmed Bug description: Install python-indicate and libindicate-doc. Run: python /usr/share/doc/libindicate/examples/im-client.py An entry should appear in message indicator, but does not. That worked in 12.04 but is broken in 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python-indicate 12.10.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 2 15:22:27 2014 InstallationDate: Installed on 2014-05-01 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libindicate UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libindicate/+bug/1315384/+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]
is this bug still valid in 4.2.x branch? if yes, please move it from mab4.1 to mab 4.2 list since 4.1.x is EOL -- 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 and 14.04 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 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 “kingsoft-office” package in Ubuntu: Confirmed Status in “openjdk-7” package in Ubuntu: Confirmed 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/df-libreoffice/+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 1315384] Re: python-indicate not showing up in message indictor
Please teach me. I will port gm-notify to libmessaging-menu. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicate in Ubuntu. https://bugs.launchpad.net/bugs/1315384 Title: python-indicate not showing up in message indictor Status in Libindicate: Confirmed Status in “libindicate” package in Ubuntu: Confirmed Bug description: Install python-indicate and libindicate-doc. Run: python /usr/share/doc/libindicate/examples/im-client.py An entry should appear in message indicator, but does not. That worked in 12.04 but is broken in 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python-indicate 12.10.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 2 15:22:27 2014 InstallationDate: Installed on 2014-05-01 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libindicate UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libindicate/+bug/1315384/+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 1316830] [NEW] /usr/lib/accountsservice/accounts-daemon :: memory and CPU time leak
You have been subscribed to a public bug: netikras@netikras-netbook ~/received/accountsservice-0.6.20 $ cat /etc/lsb-release DISTRIB_ID=LinuxMint DISTRIB_RELEASE=16 DISTRIB_CODENAME=petra DISTRIB_DESCRIPTION="Linux Mint 16 Petra" uname -a Linux netikras-netbook 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:12:00 UTC 2013 i686 i686 i686 GNU/Linux Nothing. Using my netbook as usual. Did not really notice when this started since earlier today did not feel any significant slowdowns. That's what happened: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 13155 root 20 0 61424 25m 2948 R 99,6 1,3 1:06.01 accounts-daemon netikras@netikras-netbook /tmp $ while :; do ps aux | grep accounts|grep -v grep;echo; sleep 2; done root 13155 93.6 26.1 555660 519912 pts/0 Sl 01:11 3:15 /usr/lib/accountsservice/accounts-daemon root 13155 92.7 26.1 555660 519912 pts/0 Sl 01:11 3:15 /usr/lib/accountsservice/accounts-daemon root 13155 91.9 26.1 555660 519912 pts/0 Sl 01:11 3:15 /usr/lib/accountsservice/accounts-daemon accounts-daemon is using lots o CPU cycles and memory. Stats above are after restarting daemon for several times. Before this memory usage was >60%; CPU - 100%. In file attached you should be able to see there's a loop checking for something repeatedly. Not sure this is the cause though, but feels like it.. It's the first time I've noticed this problem, but I often leave my computer running unattended so I cannot tell if it's really the first time it happened. ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Tags: accounts-daemon cpu leak ram -- /usr/lib/accountsservice/accounts-daemon :: memory and CPU time leak https://bugs.launchpad.net/bugs/1316830 You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1310490] Re: Doesn't register to use the messaging menu (indicator-messages) on 14.04 LTS
*** This bug is a duplicate of bug 1315384 *** https://bugs.launchpad.net/bugs/1315384 ** Also affects: libindicate Importance: Undecided Status: New ** Changed in: libindicate Status: New => Confirmed ** Also affects: libindicate (Ubuntu) Importance: Undecided Status: New ** Changed in: libindicate (Ubuntu) Status: New => Confirmed ** This bug has been marked a duplicate of bug 1315384 python-indicate not showing up in message indictor ** Description changed: I've recently upgraded from Ubuntu 12.04.4 LTS to 14.04 LTS. I've noticed, that the mail icon (indicator-messages) is hidden (I don't use Thunderbird, so it is not installed.) I know, that it is hidden, because I'm using GMail Notifier, which displays itself if new mail has arrived, and it works. Package info: gm-notify: Installed: 0.10.3-0ubuntu3 Candidate: 0.10.3-0ubuntu3 Version table: *** 0.10.3-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status indicator-messages: Installed: 13.10.1+14.04.20140410-0ubuntu1 Candidate: 13.10.1+14.04.20140410-0ubuntu1 Version table: *** 13.10.1+14.04.20140410-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status + python-indicate: + Installed: 12.10.1-0ubuntu3 + Candidate: 12.10.1-0ubuntu3 + Version table: + *** 12.10.1-0ubuntu3 0 + 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages + 100 /var/lib/dpkg/status + + $ gsettings get com.canonical.indicator.messages applications @as [] Please fix this issue! -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicate in Ubuntu. https://bugs.launchpad.net/bugs/1310490 Title: Doesn't register to use the messaging menu (indicator-messages) on 14.04 LTS Status in Highly Ubuntu integrated GMail Notifier: Confirmed Status in Libindicate: Confirmed Status in “gm-notify” package in Ubuntu: Confirmed Status in “libindicate” package in Ubuntu: Confirmed Bug description: I've recently upgraded from Ubuntu 12.04.4 LTS to 14.04 LTS. I've noticed, that the mail icon (indicator-messages) is hidden (I don't use Thunderbird, so it is not installed.) I know, that it is hidden, because I'm using GMail Notifier, which displays itself if new mail has arrived, and it works. Package info: gm-notify: Installed: 0.10.3-0ubuntu3 Candidate: 0.10.3-0ubuntu3 Version table: *** 0.10.3-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status indicator-messages: Installed: 13.10.1+14.04.20140410-0ubuntu1 Candidate: 13.10.1+14.04.20140410-0ubuntu1 Version table: *** 13.10.1+14.04.20140410-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status python-indicate: Installed: 12.10.1-0ubuntu3 Candidate: 12.10.1-0ubuntu3 Version table: *** 12.10.1-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status $ gsettings get com.canonical.indicator.messages applications @as [] Please fix this issue! To manage notifications about this bug go to: https://bugs.launchpad.net/gm-notify/+bug/1310490/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1316830] Re: /usr/lib/accountsservice/accounts-daemon :: memory and CPU time leak
** Project changed: linuxmint => accountsservice ** Project changed: accountsservice => accountsservice (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1316830 Title: /usr/lib/accountsservice/accounts-daemon :: memory and CPU time leak Status in “accountsservice” package in Ubuntu: New Bug description: netikras@netikras-netbook ~/received/accountsservice-0.6.20 $ cat /etc/lsb-release DISTRIB_ID=LinuxMint DISTRIB_RELEASE=16 DISTRIB_CODENAME=petra DISTRIB_DESCRIPTION="Linux Mint 16 Petra" uname -a Linux netikras-netbook 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:12:00 UTC 2013 i686 i686 i686 GNU/Linux Nothing. Using my netbook as usual. Did not really notice when this started since earlier today did not feel any significant slowdowns. That's what happened: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 13155 root 20 0 61424 25m 2948 R 99,6 1,3 1:06.01 accounts-daemon netikras@netikras-netbook /tmp $ while :; do ps aux | grep accounts|grep -v grep;echo; sleep 2; done root 13155 93.6 26.1 555660 519912 pts/0 Sl 01:11 3:15 /usr/lib/accountsservice/accounts-daemon root 13155 92.7 26.1 555660 519912 pts/0 Sl 01:11 3:15 /usr/lib/accountsservice/accounts-daemon root 13155 91.9 26.1 555660 519912 pts/0 Sl 01:11 3:15 /usr/lib/accountsservice/accounts-daemon accounts-daemon is using lots o CPU cycles and memory. Stats above are after restarting daemon for several times. Before this memory usage was >60%; CPU - 100%. In file attached you should be able to see there's a loop checking for something repeatedly. Not sure this is the cause though, but feels like it.. It's the first time I've noticed this problem, but I often leave my computer running unattended so I cannot tell if it's really the first time it happened. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1316830/+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 1231796] Re: Loading animation fails/looks bad when starting a player
Isn't this bug fixed in latest shimmer-themes 1.7.3 package, which is in Ubuntu 14.04 and later (see LP bug #1298741)? -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1231796 Title: Loading animation fails/looks bad when starting a player Status in Sound Menu: Fix Released Status in Themes for Ubuntu: Fix Released Status in “ido” package in Ubuntu: Fix Released Status in “shimmer-themes” package in Ubuntu: Fix Committed Status in “ubuntu-themes” package in Ubuntu: Fix Released Bug description: To reproduce this I just need a media player registered in the sound menu. I make sure the player is not running, then I click the play button in the indicator to start the player. The result is an ugly "loading" icon enclosed in an orange square. Please take a look at the screenshots I provided. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 indicator-sound: Installed: 12.10.2+13.10.20130924-0ubuntu1 Candidate: 12.10.2+13.10.20130924-0ubuntu1 Version table: *** 12.10.2+13.10.20130924-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-sound 12.10.2+13.10.20130924-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic i686 ApportVersion: 2.12.4-0ubuntu1 Architecture: i386 Date: Fri Sep 27 00:23:03 2013 InstallationDate: Installed on 2013-08-31 (26 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130830) MarkForUpload: True SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1231796/+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 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
@Daniel: thanks for taking the time to file an upstream bug report. I have tested Maarten's latest work on the Qt library, and I can confirm that it solves the issue on both tablets and non-tablets. Maarten's work is available here (you only need to update the qt packages): https://launchpad.net/~canonical-x/+archive/x-staging -- 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/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Triaged Status in “qtbase-opensource-src” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Triaged Status in “qtbase-opensource-src” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
** Package changed: xorg-server (Ubuntu) => qtbase-opensource-src (Ubuntu) ** Changed in: qtbase-opensource-src (Ubuntu) Importance: Undecided => High ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => In Progress ** Changed in: qtbase-opensource-src (Ubuntu) Assignee: (unassigned) => Maarten Lankhorst (mlankhorst) -- 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/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Triaged Status in “qtbase-opensource-src” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1231796] Re: Loading animation fails/looks bad when starting a player
Yup it is, guess I forgot to flip the switch. ** Changed in: shimmer-themes (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1231796 Title: Loading animation fails/looks bad when starting a player Status in Sound Menu: Fix Released Status in Themes for Ubuntu: Fix Released Status in “ido” package in Ubuntu: Fix Released Status in “shimmer-themes” package in Ubuntu: Fix Released Status in “ubuntu-themes” package in Ubuntu: Fix Released Bug description: To reproduce this I just need a media player registered in the sound menu. I make sure the player is not running, then I click the play button in the indicator to start the player. The result is an ugly "loading" icon enclosed in an orange square. Please take a look at the screenshots I provided. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 indicator-sound: Installed: 12.10.2+13.10.20130924-0ubuntu1 Candidate: 12.10.2+13.10.20130924-0ubuntu1 Version table: *** 12.10.2+13.10.20130924-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-sound 12.10.2+13.10.20130924-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic i686 ApportVersion: 2.12.4-0ubuntu1 Architecture: i386 Date: Fri Sep 27 00:23:03 2013 InstallationDate: Installed on 2013-08-31 (26 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130830) MarkForUpload: True SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1231796/+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 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
After upgrading to 14.04 I am more affected by this bug than before: network-manager does not wake up properly after hibernation. With 13.10 this might only happen when I was using overriding the METHOD to METHOD=suspend_hybrid for METHOD=suspend. The workaround: `sudo nmcli nm sleep false`. -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in NetworkManager: New Status in wicd: New Status in “systemd-shim” package in Ubuntu: Confirmed Status in “systemd-shim” source package in Saucy: Confirmed Status in “systemd-shim” source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1252121/+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 968533] Re: Alt-tab to Firefox sends Firefox to 100% CPU; unity-panel-service to 80% CPU and hud-service to 20-80% CPU
hud-service is still eating up my CPU with 14.04. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/968533 Title: Alt-tab to Firefox sends Firefox to 100% CPU; unity-panel-service to 80% CPU and hud-service to 20-80% CPU Status in Unity: Confirmed Status in “indicator-appmenu” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I've been seeing UI hangs after switching tabs in Firefox, and switching from other applications to Firefox. It can take 3-8 seconds to change *tab*. During this time the CPU is maxed out; typical output from 'top' during this period shows 'hud- service' and 'unity-panel-service' combined using about the same CPU as Firefox itself: 100 10.4 26:07.73 firefox 53 0.6 6:14.86 hud-service 38 1.5 6:42.14 unity-panel-service I suspect that the change is causing a (an inefficient) re-index related to updated menu structures. (Eg. something like the history menu, although I can't see what it is as don't currently have a menu bar). To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/968533/+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 1302760] Re: unity: "always on visible workspace" not working
*** This bug is a duplicate of bug 1305327 *** https://bugs.launchpad.net/bugs/1305327 ** This bug has been marked a duplicate of bug 1305327 Always in visible workspace does not work -- 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/1302760 Title: unity: "always on visible workspace" not working Status in “unity” package in Ubuntu: New Bug description: This is on a machine with an external display connected but happens equally when that display is unplugged: steps to reproduce: - open any new window - right click titlebar, select "always on visible workspace" - switch to a different workspace - window does not stay visible but stays on old workspace expected behaviour: - keep selected window visible on any workspace I switch to Trusty apt-cache policy unity unity: Installed: 7.1.2+14.04.20140328.1-0ubuntu1 Candidate: 7.2.0+14.04.20140403-0ubuntu1 Version table: 7.2.0+14.04.20140403-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages *** 7.1.2+14.04.20140328.1-0ubuntu1 0 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302760/+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 1316828] Re: Sync sparsehash 2.0.2-1 (main) from Debian unstable (main)
This bug was fixed in the package sparsehash - 2.0.2-1 Sponsored for Artur Rona (ari-tczew) --- sparsehash (2.0.2-1) unstable; urgency=low * New upstream release (Closes: #705974) * Update watch file * Stop build depending on outdated automake, thanks to Eric Dorland for the patch (Closes: #724437) * Update to Standards-Version 3.9.5 + debian/rules: add build-arch and build-indep targets * Run tests during build, thanks to Michael Terry for the patch (Closes: #700339) * Drop obsolete binary transition package (sparsehash) -- Roberto C. Sanchez Tue, 11 Mar 2014 19:15:30 -0400 ** Changed in: sparsehash (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to sparsehash in Ubuntu. https://bugs.launchpad.net/bugs/1316828 Title: Sync sparsehash 2.0.2-1 (main) from Debian unstable (main) Status in “sparsehash” package in Ubuntu: Fix Released Bug description: Please sync sparsehash 2.0.2-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * debian/rules: - Run tests as part of the build * debian/rules: - Run tests as part of the build * debian/rules: - Run tests as part of the build * debian/rules: - Run tests as part of the build * debian/rules: - Run tests as part of the build * No-change rebuild against current pkgbinarymangler to fix broken md5sums. (see LP #875466) * No-change rebuild against current pkgbinarymangler to fix broken md5sums. (see LP #875466) * No-change rebuild against current pkgbinarymangler to fix broken md5sums. (see LP #875466) Debian has merged Ubuntu changes. Changelog entries since current utopic version 1.10-1ubuntu1: sparsehash (2.0.2-1) unstable; urgency=low * New upstream release (Closes: #705974) * Update watch file * Stop build depending on outdated automake, thanks to Eric Dorland for the patch (Closes: #724437) * Update to Standards-Version 3.9.5 + debian/rules: add build-arch and build-indep targets * Run tests during build, thanks to Michael Terry for the patch (Closes: #700339) * Drop obsolete binary transition package (sparsehash) -- Roberto C. Sanchez Tue, 11 Mar 2014 19:15:30 -0400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sparsehash/+bug/1316828/+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 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Also affects: xorg-server via https://bugs.freedesktop.org/show_bug.cgi?id=78345 Importance: Unknown Status: Unknown -- 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/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Triaged Status in X.Org X server: Unknown Status in “qtbase-opensource-src” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Status in “xorg-server” package in Ubuntu: New Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
Qt still XISelectEvents my "N-Trig Pen stylus" and "N-Trig Pen eraser" slave devices though. But thankfully no events come from them and thus peace is maintained :) ** Changed in: unity (Ubuntu) Status: In Progress => 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/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Triaged Status in X.Org X server: Unknown Status in “qtbase-opensource-src” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “xorg-server” package in Ubuntu: New Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
I confirm that the Qt from https://launchpad.net/~canonical-x/+archive/x-staging does XISelectEvents on the master pointer (instead of the touchscreen slave device, as previously) and that the resulting behavior of the xserver is good. Ie., touch ownership mechanics work properly and mouse pointer emluation from touch events keeps working as well. -- 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/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Triaged Status in X.Org X server: Unknown Status in “qtbase-opensource-src” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “xorg-server” package in Ubuntu: New Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1316265] Re: Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+E (window spread)
simliar bug report: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1314851 -- 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/1316265 Title: Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+E (window spread) Status in “unity” package in Ubuntu: New Bug description: A maximized application's title bar does not merge into the menu bar once a user has performed Super + E (window slide). Note that if one does not do Super+E, then the bars to merge together. However, once Super+E has been performed, this bug persists for the lifetime of the windowed application. If the application is restarted after doing Super+E, then the bug is gone. Thus, it seems like Super+E introduces this bug for the lifetime of the windowed application. Expected behavior: Maximized window's title bar is merged into menu bar. Observed: Does not occur after Super+E is performed. Try this out using Terminal. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon May 5 14:48:01 2014 InstallationDate: Installed on 2013-09-08 (239 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1316265/+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 1316320] Re: Screen Lock does not prompt for password
I think the issue here is that since users on the Terminal server are authenticated with sssd/ldap the client images need to be able to authenticate as well. As a temporary work around I have installed xscreensaver and sssd. With the same sssd.conf from the server, the xscreensaver lock works just as well. -- 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/1316320 Title: Screen Lock does not prompt for password Status in “unity” package in Ubuntu: New Bug description: I am using LTSP fat clients, created with: $ sudo ltsp-build-image --arch amd64 --fat-client-desktop ubuntu- desktop LTSP server has sssd authentication utilizing pam and ldap. Users can log in without issue and the home folder is available. Everything works as expected except for screen locking. When locking the screen, the displays first go blank and the monitor goes to sleep. Then if i move the mouse or press a keystroke, They go black but the mouse is visible. Once I move the mouse or strike a key the second time, everything comes back up without password prompt. However, password prompt is enabled in "Brightness & Lock" The client hardware is an Intel NUC D34010WYK Also maybe related, there seems to be no system tray. No clock or username/logout buttons. I am using Ctrl + Alt + L to lock the screen. (See attached screenshot) This is a security vulnerability and I can not make the new 14.04 image available as fat clients, since they users cannot lock their workstation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1316320/+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 1316265] Re: Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+E (window spread)
I can confirm this behaviour on a fresh install of 14.04 - although "Window Spread" doesn't seem to trigger it in my setup. It seems to just happen at certain points, and closing the window and reopening solves the issue temporarily. -- 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/1316265 Title: Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+E (window spread) Status in “unity” package in Ubuntu: New Bug description: A maximized application's title bar does not merge into the menu bar once a user has performed Super + E (window slide). Note that if one does not do Super+E, then the bars to merge together. However, once Super+E has been performed, this bug persists for the lifetime of the windowed application. If the application is restarted after doing Super+E, then the bug is gone. Thus, it seems like Super+E introduces this bug for the lifetime of the windowed application. Expected behavior: Maximized window's title bar is merged into menu bar. Observed: Does not occur after Super+E is performed. Try this out using Terminal. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon May 5 14:48:01 2014 InstallationDate: Installed on 2013-09-08 (239 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1316265/+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 1303462] Re: [Regression] Window titlebars placed behind panel
** Package changed: unity (Ubuntu) => compiz (Ubuntu) ** Changed in: compiz Importance: Medium => High ** Changed in: compiz Milestone: None => 0.9.11.0 ** Changed in: compiz Assignee: (unassigned) => Christopher Townsend (townsend) ** Changed in: compiz (Ubuntu) Assignee: (unassigned) => Christopher Townsend (townsend) ** Changed in: compiz Status: Triaged => In Progress ** Changed in: compiz (Ubuntu) Status: Triaged => In Progress -- 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/1303462 Title: [Regression] Window titlebars placed behind panel Status in Compiz: In Progress Status in Unity: Invalid Status in “compiz” package in Ubuntu: In Progress Bug description: Windows with a height of (Display Height - Panel Height) get placed at y=0 (behind the top panel) which means window titlebars are not reachable without alt-moving the window. I assume this happens with windows that want to resize themselves if their height exceeds the display resolution. Reproducable on my 1366x768 screen with LibreOffice and a Qt 5 desktop application I'm working on. TEMPORARY WORKAROUND: Use the Cntrl+SuperKey+Right or Left Arrow Key This will resize your currently focused window to occupy the Right (Left) half of the screen. The Title Bar should now be visible, so you need to drag it and resize it at your prefered position. This will save the new position in place of the previously hidden state. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Apr 6 21:45:41 2014 InstallationDate: Installed on 2014-04-04 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140404) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1303462/+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 1306112] Re: calendar sync causing 100% cpu and does not complete
syncevolution was already uploaded: https://launchpad.net/ubuntu/+source/syncevolution/1.4-1ubuntu4 Closing MP. ** Also affects: syncevolution (Ubuntu) Importance: Undecided Status: New ** Changed in: syncevolution (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/1306112 Title: calendar sync causing 100% cpu and does not complete Status in Sync monitor for Ubuntu Touch: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “qtorganizer5-eds” package in Ubuntu: Fix Released Status in “sync-monitor” package in Ubuntu: Fix Released Status in “syncevolution” package in Ubuntu: Fix Released Bug description: test using canonical google account this is the problem i'm seeing with the canonical account the calendar sync starts to run first, and it gets about progress of 70 and then evolution-calendar-factory starts consuming all the CPU - 100% (run "top -d1") and at the same time the sync-monitor.log shows an infinite number of messages about static void ViewWatcher::onObjectsAdded(ECalClientView*, GSList*, ViewWatcher*) 0x15468a8 virtual QList QOrganizerEDSEngine::collections(QtOrganizer::QOrganizerManager::Error*) virtual bool QOrganizerEDSEngine::startRequest(QtOrganizer::QOrganizerAbstractRequest*) virtual bool QOrganizerEDSEngine::waitForRequestFinished(QtOrganizer::QOrganizerAbstractRequest*, int) syn requested for account: "bill.fil...@canonical.com" "calendar" Account aready in the queue The sync never finishes, seems that evolution process is stuck. I have to kill it. http://pastebin.ubuntu.com/7231364/ Seems we might be in a loop when calendar events are getting added because of the sync we see tons of messages in the sync-monitor log maybe we're not ignoring the events correctly? or maybe it's a problem is the calendar has a recurring event? seems to cause infinite loop. This one is critical. To manage notifications about this bug go to: https://bugs.launchpad.net/sync-monitor/+bug/1306112/+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 1316005] Re: Panel shadow appears over full screen applications
Hi Christopher, Thanks for the update. I don't think there is another bug opened about this. We (the developers) were just discussing this issue the other day, but didn't enter a bug report about it:) ** Changed in: unity (Ubuntu) Status: Incomplete => Triaged ** Changed in: unity (Ubuntu) Importance: Undecided => Medium ** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Status: New => Triaged ** Changed in: unity Importance: Undecided => Medium ** Changed in: unity Milestone: None => 7.2.1 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1316005 Title: Panel shadow appears over full screen applications Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: The shadow of the top Unity panel draws over full screen applications that have controls visible when the mouse is moved. Steps to reproduce: 1) Open an image in Image Viewer 2) Double click the image to full-screen it 3) Move the mouse to the top of the screen to access the controls Expected behavior: Only the image and the Image Viewer controls should be visible Acutal behavior: The Unity panel shadow is drawn on top of the controls at the top of the screen Notes: This also appears in the Videos application, but does not in VLC or gimp. I believe it is GTK applications with UI elements that only appear on mouse movement (gimp's UI is static, and I believe VLC is Qt based). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun May 4 22:37:44 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:2117] InstallationDate: Installed on 2014-04-19 (15 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ASUSTeK COMPUTER INC. G55VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=927ff2bd-c81d-4a5d-9acb-3bd3dd820e35 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/05/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G55VW.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G55VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG55VW.206:bd04/05/2012:svnASUSTeKCOMPUTERINC.:pnG55VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG55VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G55VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserv
[Dx-packages] [Bug 381416] Re: notify-osd should have a close button
I think there should be a close button on each notification card. also it will be better if there exists some notification settings through which user can enable or disable notification card and customize the display time. unread notifications should be stored in notification center. ** Attachment added: "notification center" https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/381416/+attachment/4107388/+files/Pear-desktop-17.jpg -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/381416 Title: notify-osd should have a close button Status in “notify-osd” package in Ubuntu: Won't Fix Bug description: Binary package hint: notify-osd As simple as that. The new notification system works fine, but it really bugs me that I'm forced to wait for those little messages to fade away by themselves. Should I suggest this somewhere else? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/381416/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1315384] Re: python-indicate not showing up in message indictor
There is no python binding yet for libmessaging-menu. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicate in Ubuntu. https://bugs.launchpad.net/bugs/1315384 Title: python-indicate not showing up in message indictor Status in Libindicate: Confirmed Status in “libindicate” package in Ubuntu: Confirmed Bug description: Install python-indicate and libindicate-doc. Run: python /usr/share/doc/libindicate/examples/im-client.py An entry should appear in message indicator, but does not. That worked in 12.04 but is broken in 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python-indicate 12.10.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 2 15:22:27 2014 InstallationDate: Installed on 2014-05-01 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libindicate UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libindicate/+bug/1315384/+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 1315384] Re: python-indicate not showing up in message indictor
The link above does not show the attachment. See here at comment #17 https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1040259 -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicate in Ubuntu. https://bugs.launchpad.net/bugs/1315384 Title: python-indicate not showing up in message indictor Status in Libindicate: Confirmed Status in “libindicate” package in Ubuntu: Confirmed Bug description: Install python-indicate and libindicate-doc. Run: python /usr/share/doc/libindicate/examples/im-client.py An entry should appear in message indicator, but does not. That worked in 12.04 but is broken in 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python-indicate 12.10.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 2 15:22:27 2014 InstallationDate: Installed on 2014-05-01 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libindicate UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libindicate/+bug/1315384/+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 1315384] Re: python-indicate not showing up in message indictor
Noseong, here is a demo in python: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1040259/comments/17 But I need more documentation about that. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicate in Ubuntu. https://bugs.launchpad.net/bugs/1315384 Title: python-indicate not showing up in message indictor Status in Libindicate: Confirmed Status in “libindicate” package in Ubuntu: Confirmed Bug description: Install python-indicate and libindicate-doc. Run: python /usr/share/doc/libindicate/examples/im-client.py An entry should appear in message indicator, but does not. That worked in 12.04 but is broken in 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python-indicate 12.10.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 2 15:22:27 2014 InstallationDate: Installed on 2014-05-01 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libindicate UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libindicate/+bug/1315384/+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 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
** Changed in: xorg-server (Ubuntu) Assignee: (unassigned) => Maarten Lankhorst (mlankhorst) ** Changed in: xorg-server (Ubuntu) Importance: Undecided => High ** Changed in: xorg-server (Ubuntu) Status: New => In Progress -- 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/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Triaged Status in X.Org X server: Unknown Status in “qtbase-opensource-src” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “xorg-server” package in Ubuntu: In Progress Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1313280] Re: Fullscreen window set to "Always on Top" in single-monitor will hide the lockscreen
** Description changed: - Im running on Ubuntu 14.04 and noticed this while watching a video last - time. + [Impact] + A fullscreen window set to "always on top" hides the lockscreem. - There is a really easy way to replicate this bug: - * Open a video in Totem - * Set Totem to "Always on Top" - * Make Totem full screen - * Manually Lock the screen using Super+L - * Notice that the lockscreen is hidden by totem. + [Test Case] + (1) Open a video in Totem + (2) Right-click on the titlebar and set Totem to "Always on Top" + (3) Make Totem full screen (eg. with the F11 key or clicking on the control) + (4) Manually Lock the screen using Super+L + (5) Notice that the lockscreen is hidden by totem. If you don't lock it manually and just pause the video and let it lock automatically this will show the same behavior. The same behavior occurs with any application that can enter full screen mode. + + [Regression Potential] + Two cases may potentially source regressions. + (1) windows that need to appear above the lockscreen, such as on-screen keyboards, + (2) applications presenting fullscreen windows using unusual or non-standard toolkits. + It is unlikely that regressions in either of these cases would be introduced by this bug fix, but rather would be pre-existing problems not fixed here. -- 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/1313280 Title: Fullscreen window set to "Always on Top" in single-monitor will hide the lockscreen Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: [Impact] A fullscreen window set to "always on top" hides the lockscreem. [Test Case] (1) Open a video in Totem (2) Right-click on the titlebar and set Totem to "Always on Top" (3) Make Totem full screen (eg. with the F11 key or clicking on the control) (4) Manually Lock the screen using Super+L (5) Notice that the lockscreen is hidden by totem. If you don't lock it manually and just pause the video and let it lock automatically this will show the same behavior. The same behavior occurs with any application that can enter full screen mode. [Regression Potential] Two cases may potentially source regressions. (1) windows that need to appear above the lockscreen, such as on-screen keyboards, (2) applications presenting fullscreen windows using unusual or non-standard toolkits. It is unlikely that regressions in either of these cases would be introduced by this bug fix, but rather would be pre-existing problems not fixed here. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313280/+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 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Branch linked: lp:~macslow/unity-notifications/fix-1295762 -- 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/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Ubuntu UX bugs: Fix Committed Status in Unity: Triaged Status in Server and client library for desktop notifications in Unity: In Progress Status in “unity” package in Ubuntu: Confirmed Status in “unity-notifications” package in Ubuntu: Confirmed Bug description: Problem: If user receives an SMS/call, snap decision for incoming SMS/call stays on screen for always only 60sec. and then disappears from screen (by default). There was no interaction from user. Possible solution: The snap decision should stay on screen for the amount of time the app asks it to, being always app dependant. A 60sec. time-out is too short due to use cases where an action from user is mandatory. Use case example: A class 1/2 SMS arrives after user triggered a USSD command from dialer. These type of SMS always requires a response from user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is too short because it can be missed and these type of SMS is NOT saved into the usual messages thread. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1295762/+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 1221673] Re: compiz crashed with SIGSEGV in CompAction::initiate()
** Description changed: + [Impact] at boot - ProblemType: Crash - DistroRelease: Ubuntu 13.10 + ProblemType: CrashDistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130903.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Fri Sep 6 10:38:05 2013 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-09-04 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130904) MarkForUpload: True ProcCmdline: compiz ProcEnviron: - LANGUAGE=pt:pt_BR:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=pt_PT.UTF-8 - SHELL=/bin/bash + LANGUAGE=pt:pt_BR:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=pt_PT.UTF-8 + SHELL=/bin/bash SegvAnalysis: - Segfault happened at: 0x7fe02b8d169d <_ZN10CompAction8initiateEv+13>: mov0x8(%rdi),%rdx - PC (0x7fe02b8d169d) ok - source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! - destination "%rdx" ok + Segfault happened at: 0x7fe02b8d169d <_ZN10CompAction8initiateEv+13>: mov0x8(%rdi),%rdx + PC (0x7fe02b8d169d) ok + source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! + destination "%rdx" ok SegvReason: reading NULL VMA - Signal: 11 - SourcePackage: unity + Signal: 11SourcePackage: unity StacktraceTop: - CompAction::initiate() () from /usr/lib/libcompiz_core.so.ABI-20130415 - unity::MultiActionList::Initiate(std::string const&, std::vector > const&, int) const () from /usr/lib/compiz/libunityshell.so - unity::MultiActionList::InitiateAll(std::vector > const&, int) const () from /usr/lib/compiz/libunityshell.so - unity::PluginAdapter::InitiateExpo() () from /usr/lib/compiz/libunityshell.so - unity::launcher::LauncherIcon::Activate(unity::launcher::ActionArg) () from /usr/lib/compiz/libunityshell.so + CompAction::initiate() () from /usr/lib/libcompiz_core.so.ABI-20130415 + unity::MultiActionList::Initiate(std::string const&, std::vector > const&, int) const () from /usr/lib/compiz/libunityshell.so + unity::MultiActionList::InitiateAll(std::vector > const&, int) const () from /usr/lib/compiz/libunityshell.so + unity::PluginAdapter::InitiateExpo() () from /usr/lib/compiz/libunityshell.so + unity::launcher::LauncherIcon::Activate(unity::launcher::ActionArg) () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in CompAction::initiate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + + [Test Case] + Unclear: this is an intermittent crash problem. + + [Regression Potential] + The worst case is that session would continue to crash on startup. -- 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/1221673 Title: compiz crashed with SIGSEGV in CompAction::initiate() Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: [Impact] at boot ProblemType: CrashDistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130903.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Fri Sep 6 10:38:05 2013 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-09-04 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130904) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe02b8d169d <_ZN10CompAction8initiateEv+13>: mov0x8(%rdi),%rdx PC (0x7fe02b8d169d) ok source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading NULL VMA Signal: 11SourcePackage: unity StacktraceTop: CompAction::initiate() () from /usr/lib/libcompiz_core.so.ABI-20130415 unity::MultiActionList::Initiate(std::string const&, std::vector > const&, int) const () from /usr/lib/compiz/libunityshell.so unity::MultiActionList::InitiateAll(std::vector > const&, int) const () from /usr/lib/compiz/libunityshell.so unity::PluginAdapter::InitiateExpo() () from /usr/lib/compiz/libunityshell.so unity::launcher::LauncherIcon::Activate(unity::launcher::ActionArg) () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in CompAction::initiate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo [Test Case] Unclear: this is an intermittent crash problem.
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Changed in: unity-notifications Status: Triaged => In Progress -- 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/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Ubuntu UX bugs: Fix Committed Status in Unity: Triaged Status in Server and client library for desktop notifications in Unity: In Progress Status in “unity” package in Ubuntu: Confirmed Status in “unity-notifications” package in Ubuntu: Confirmed Bug description: Problem: If user receives an SMS/call, snap decision for incoming SMS/call stays on screen for always only 60sec. and then disappears from screen (by default). There was no interaction from user. Possible solution: The snap decision should stay on screen for the amount of time the app asks it to, being always app dependant. A 60sec. time-out is too short due to use cases where an action from user is mandatory. Use case example: A class 1/2 SMS arrives after user triggered a USSD command from dialer. These type of SMS always requires a response from user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is too short because it can be missed and these type of SMS is NOT saved into the usual messages thread. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1295762/+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 1291461] Re: Lockscreen: keyboard layout switching shortcuts not working
** Description changed: + [Impact] New Unity Lockscreen has the same problem as the old one from Gnome: the chosen keyboard shortcut is not switching keyboard layouts on it, the only way is to use mouse. - Steps to reproduce: + + [Test Case] 1. To make things uncomfortable, switch layout to Russian or any other with your favourite shortcut(i am using alt-shift) 2. Lock the screen with ctrl-alt-l 3. Try to change layout back to English to enter password Expected: Layput should change and you should be able to login without touching anything but keyboard. What's happening: Nothing, doesn't react on the keyboard shortcut, you have to change layout using indicator on top panel. + + [Regression Potential] + 1. There may potentially be missing keyboard shorts. + 2. Key grabs may persist after the lockscreen has been released. + 3. new code contains dynamic memory allocation, which always introduces potential leaks, crashes, or exhaustion -- 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/1291461 Title: Lockscreen: keyboard layout switching shortcuts not working Status in Unity: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] New Unity Lockscreen has the same problem as the old one from Gnome: the chosen keyboard shortcut is not switching keyboard layouts on it, the only way is to use mouse. [Test Case] 1. To make things uncomfortable, switch layout to Russian or any other with your favourite shortcut(i am using alt-shift) 2. Lock the screen with ctrl-alt-l 3. Try to change layout back to English to enter password Expected: Layput should change and you should be able to login without touching anything but keyboard. What's happening: Nothing, doesn't react on the keyboard shortcut, you have to change layout using indicator on top panel. [Regression Potential] 1. There may potentially be missing keyboard shorts. 2. Key grabs may persist after the lockscreen has been released. 3. new code contains dynamic memory allocation, which always introduces potential leaks, crashes, or exhaustion To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291461/+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 1313280] Re: Fullscreen window set to "Always on Top" in single-monitor will hide the lockscreen
** Description changed: [Impact] A fullscreen window set to "always on top" hides the lockscreem. [Test Case] (1) Open a video in Totem (2) Right-click on the titlebar and set Totem to "Always on Top" (3) Make Totem full screen (eg. with the F11 key or clicking on the control) (4) Manually Lock the screen using Super+L (5) Notice that the lockscreen is hidden by totem. If you don't lock it manually and just pause the video and let it lock automatically this will show the same behavior. The same behavior occurs with any application that can enter full screen mode. - [Regression Potential] - Two cases may potentially source regressions. + [Regression Potential]Two cases may potentially source regressions. (1) windows that need to appear above the lockscreen, such as on-screen keyboards, - (2) applications presenting fullscreen windows using unusual or non-standard toolkits. - It is unlikely that regressions in either of these cases would be introduced by this bug fix, but rather would be pre-existing problems not fixed here. + (2) applications presenting fullscreen windows using unusual or non-standard toolkits.It is unlikely that regressions in either of these cases would be introduced by this bug fix, but rather would be pre-existing problems not fixed here. + (3) Indicator menus might be not being drawn -- 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/1313280 Title: Fullscreen window set to "Always on Top" in single-monitor will hide the lockscreen Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: [Impact] A fullscreen window set to "always on top" hides the lockscreem. [Test Case] (1) Open a video in Totem (2) Right-click on the titlebar and set Totem to "Always on Top" (3) Make Totem full screen (eg. with the F11 key or clicking on the control) (4) Manually Lock the screen using Super+L (5) Notice that the lockscreen is hidden by totem. If you don't lock it manually and just pause the video and let it lock automatically this will show the same behavior. The same behavior occurs with any application that can enter full screen mode. [Regression Potential]Two cases may potentially source regressions. (1) windows that need to appear above the lockscreen, such as on-screen keyboards, (2) applications presenting fullscreen windows using unusual or non-standard toolkits.It is unlikely that regressions in either of these cases would be introduced by this bug fix, but rather would be pre-existing problems not fixed here. (3) Indicator menus might be not being drawn To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313280/+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 1033936] Re: Window management - Add "ghost" new window in spread for applications that support multiple windows
** Description changed: The new unity window switching specification says the following about the spread: "For applications which provide a New Window option or equivalent (currently accessed by middle clicking the Launcher icon or choosing the option from the right mouse button menu), a New Window item is displayed in the spread. When this window is highlighted, it will be outlined by the orange glow border and show the caption New Window, but does not show a title-bar or close button. The user can click on this item to create a new window, bring it to front and focus it and exit the spread." - This feature should be implemented according to the spec published here: - http://design.canonical.com/the-toolkit/unity-task-switching/ + This feature should be implemented according to the design published here: + http://design.canonical.com/2012/03/task-switching-in-ubuntu-and-a-introduction-to-the-spread/ -- 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/1033936 Title: Window management - Add "ghost" new window in spread for applications that support multiple windows Status in Ayatana Design: Fix Committed Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: The new unity window switching specification says the following about the spread: "For applications which provide a New Window option or equivalent (currently accessed by middle clicking the Launcher icon or choosing the option from the right mouse button menu), a New Window item is displayed in the spread. When this window is highlighted, it will be outlined by the orange glow border and show the caption New Window, but does not show a title-bar or close button. The user can click on this item to create a new window, bring it to front and focus it and exit the spread." This feature should be implemented according to the design published here: http://design.canonical.com/2012/03/task-switching-in-ubuntu-and-a-introduction-to-the-spread/ To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1033936/+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 1316191] Re: Mouse pointer is blocked on dual monitor setup
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1316191 Title: Mouse pointer is blocked on dual monitor setup Status in “unity” package in Ubuntu: Confirmed Bug description: On a dual monitor setup, by default, the mouse pointer is "blocked" when trying to go to the other screen. This is a very annoying bug since the user shouldn't be restricted to switch screens with his mouse pointer. The fix for that is downloading compizconfig-settings-manager and setting the "Edge Stop Velocity" to 1. This is way beyond a newbie would actually know, so I request that this option come by default. Thanks, ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon May 5 12:06:53 2014 InstallationDate: Installed on 2014-02-21 (72 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-23 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1316191/+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 1317138] [NEW] Password input field too long at a wrong input
You have been subscribed to a public bug: If I lock my machine with Strg+Alt+L an insert box is shown. After entering a wrong password a dialog asking me to retry. This dialog and the password insert is too long. It goes until the transparent box ends and then it is cut off. ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Password input field too long at a wrong input https://bugs.launchpad.net/bugs/1317138 You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1317138] Re: Password input field too long at a wrong input
** Package changed: ubuntu => unity (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1317138 Title: Password input field too long at a wrong input Status in “unity” package in Ubuntu: New Bug description: If I lock my machine with Strg+Alt+L an insert box is shown. After entering a wrong password a dialog asking me to retry. This dialog and the password insert is too long. It goes until the transparent box ends and then it is cut off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1317138/+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 1317187] [NEW] unity launcher 'auto-hide' gets pointer stuck between screens
Public bug reported: Similar to #1095854 and #970038 (and quite possibly the same bug?), when 'auto-hide' is enabled, if I try to move my pointer to the left hand of my first screen(ie where the launcher is), it only comes up sometimes, and very haphazardly, whereas(and here's the bug:) if I move towards the right(ie towards the other monitor) it usually gets 'stuck' at the edges of the two monitors. Sometimes the pointer is allowed to go through, and I can 'force' it back to the correct screen by alt-tabbing to a window on the correct monitor, and then alt-space -> move. Turning off the launcher auto-hide option makes this symptom disappear immediately. Ubuntu 14.04 themusicgod1@snowden:~$ !! apt-cache policy unity unity: Installed: 7.2.0+14.04.20140423-0ubuntu1.2 Candidate: 7.2.0+14.04.20140423-0ubuntu1.2 Version table: *** 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packag es 500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 Package s 100 /var/lib/dpkg/status 7.2.0+14.04.20140416-0ubuntu1 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed May 7 12:23:20 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-28 (40 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta i386 (20140326) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1317187 Title: unity launcher 'auto-hide' gets pointer stuck between screens Status in “unity” package in Ubuntu: New Bug description: Similar to #1095854 and #970038 (and quite possibly the same bug?), when 'auto-hide' is enabled, if I try to move my pointer to the left hand of my first screen(ie where the launcher is), it only comes up sometimes, and very haphazardly, whereas(and here's the bug:) if I move towards the right(ie towards the other monitor) it usually gets 'stuck' at the edges of the two monitors. Sometimes the pointer is allowed to go through, and I can 'force' it back to the correct screen by alt-tabbing to a window on the correct monitor, and then alt-space -> move. Turning off the launcher auto-hide option makes this symptom disappear immediately. Ubuntu 14.04 themusicgod1@snowden:~$ !! apt-cache policy unity unity: Installed: 7.2.0+14.04.20140423-0ubuntu1.2 Candidate: 7.2.0+14.04.20140423-0ubuntu1.2 Version table: *** 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packag es 500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 Package s 100 /var/lib/dpkg/status 7.2.0+14.04.20140416-0ubuntu1 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed May 7 12:23:20 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-28 (40 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta i386 (20140326) 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/1317187/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1310490] Re: Doesn't register to use the messaging menu (indicator-messages) on 14.04 LTS
*** This bug is a duplicate of bug 1315384 *** https://bugs.launchpad.net/bugs/1315384 One more thing. After "swig -python -module messaging messaging.c", messaging_wrap.c is created. Add #include to the file such that gcc doesn't complain. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicate in Ubuntu. https://bugs.launchpad.net/bugs/1310490 Title: Doesn't register to use the messaging menu (indicator-messages) on 14.04 LTS Status in Highly Ubuntu integrated GMail Notifier: Confirmed Status in Libindicate: Confirmed Status in “gm-notify” package in Ubuntu: Confirmed Status in “libindicate” package in Ubuntu: Confirmed Bug description: I've recently upgraded from Ubuntu 12.04.4 LTS to 14.04 LTS. I've noticed, that the mail icon (indicator-messages) is hidden (I don't use Thunderbird, so it is not installed.) I know, that it is hidden, because I'm using GMail Notifier, which displays itself if new mail has arrived, and it works. Package info: gm-notify: Installed: 0.10.3-0ubuntu3 Candidate: 0.10.3-0ubuntu3 Version table: *** 0.10.3-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status indicator-messages: Installed: 13.10.1+14.04.20140410-0ubuntu1 Candidate: 13.10.1+14.04.20140410-0ubuntu1 Version table: *** 13.10.1+14.04.20140410-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status python-indicate: Installed: 12.10.1-0ubuntu3 Candidate: 12.10.1-0ubuntu3 Version table: *** 12.10.1-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status $ gsettings get com.canonical.indicator.messages applications @as [] Please fix this issue! To manage notifications about this bug go to: https://bugs.launchpad.net/gm-notify/+bug/1310490/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1310490] Re: Doesn't register to use the messaging menu (indicator-messages) on 14.04 LTS
*** This bug is a duplicate of bug 1315384 *** https://bugs.launchpad.net/bugs/1315384 I could make it working, but not perfect yet. It shows the gm-notify icon and unread e-mail numbers. I ported to libmessaging-menu. Please somebody continue to take a look a it. I may not be available for the next several days. 1. Download python wrapper for libmessagng-menu swig -python -module messaging messaging.c gcc -I/usr/include/python2.7 -I/usr/include/glib-2.0 -I/usr/lib/x86_64 -linux-gnu/glib-2.0/include -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk- pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/freetype2 -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/harfbuzz -I/usr/include/libindicate-0.7 -I/usr/include /libindicate-gtk-0.7/ -lindicate -ldbusmenu-glib -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfontconfig -lgobject-2.0 -lglib-2.0 -lfreetype -lindicate-gtk -I/usr/include/messaging-menu -lmessaging-menu -fPIC -c messaging.c messaging_wrap.c ld -shared -o _messaging.so messaging.o messaging_wrap.o -lmessaging- menu Now you can see _messaging.so is created. This is a python wrapper. 2. Download the modified gm-notify and run it. At line 44, you should specify your wrapper library location. ** Attachment added: "ported to libmessaging-menu" https://bugs.launchpad.net/ubuntu/+source/gm-notify/+bug/1310490/+attachment/4107454/+files/gm-notify-modified.tgz -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicate in Ubuntu. https://bugs.launchpad.net/bugs/1310490 Title: Doesn't register to use the messaging menu (indicator-messages) on 14.04 LTS Status in Highly Ubuntu integrated GMail Notifier: Confirmed Status in Libindicate: Confirmed Status in “gm-notify” package in Ubuntu: Confirmed Status in “libindicate” package in Ubuntu: Confirmed Bug description: I've recently upgraded from Ubuntu 12.04.4 LTS to 14.04 LTS. I've noticed, that the mail icon (indicator-messages) is hidden (I don't use Thunderbird, so it is not installed.) I know, that it is hidden, because I'm using GMail Notifier, which displays itself if new mail has arrived, and it works. Package info: gm-notify: Installed: 0.10.3-0ubuntu3 Candidate: 0.10.3-0ubuntu3 Version table: *** 0.10.3-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status indicator-messages: Installed: 13.10.1+14.04.20140410-0ubuntu1 Candidate: 13.10.1+14.04.20140410-0ubuntu1 Version table: *** 13.10.1+14.04.20140410-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status python-indicate: Installed: 12.10.1-0ubuntu3 Candidate: 12.10.1-0ubuntu3 Version table: *** 12.10.1-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status $ gsettings get com.canonical.indicator.messages applications @as [] Please fix this issue! To manage notifications about this bug go to: https://bugs.launchpad.net/gm-notify/+bug/1310490/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1310490] Re: Doesn't register to use the messaging menu (indicator-messages) on 14.04 LTS
*** This bug is a duplicate of bug 1315384 *** https://bugs.launchpad.net/bugs/1315384 I forgot to say copy /usr/share/gm-notify/gm-notify.desktop to /usr/share/applications/ -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicate in Ubuntu. https://bugs.launchpad.net/bugs/1310490 Title: Doesn't register to use the messaging menu (indicator-messages) on 14.04 LTS Status in Highly Ubuntu integrated GMail Notifier: Confirmed Status in Libindicate: Confirmed Status in “gm-notify” package in Ubuntu: Confirmed Status in “libindicate” package in Ubuntu: Confirmed Bug description: I've recently upgraded from Ubuntu 12.04.4 LTS to 14.04 LTS. I've noticed, that the mail icon (indicator-messages) is hidden (I don't use Thunderbird, so it is not installed.) I know, that it is hidden, because I'm using GMail Notifier, which displays itself if new mail has arrived, and it works. Package info: gm-notify: Installed: 0.10.3-0ubuntu3 Candidate: 0.10.3-0ubuntu3 Version table: *** 0.10.3-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status indicator-messages: Installed: 13.10.1+14.04.20140410-0ubuntu1 Candidate: 13.10.1+14.04.20140410-0ubuntu1 Version table: *** 13.10.1+14.04.20140410-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status python-indicate: Installed: 12.10.1-0ubuntu3 Candidate: 12.10.1-0ubuntu3 Version table: *** 12.10.1-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status $ gsettings get com.canonical.indicator.messages applications @as [] Please fix this issue! To manage notifications about this bug go to: https://bugs.launchpad.net/gm-notify/+bug/1310490/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 815996] Re: Desktop occasionally freezes/locks up when switching workspaces
If you need a testbed just install gnome-session-flashback in a 14.04 virtualbox vm. I tried using it and had the exact same issues as on my desktop. I used the latest virtualbox from the 14.04 repos/no usb/ no guest tools It shipped broken. I read in another place that there was a new compiz in staging with large feature changes. Could this relate? -- You received this bug notification because you are a member of DX Packages, which is subscribed to compiz-plugins-main in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/815996 Title: Desktop occasionally freezes/locks up when switching workspaces Status in Compiz: Confirmed Status in Compiz Main Plugins: Confirmed Status in Compiz Desktop Wall Plugin: Confirmed Status in “compiz-plugins-main” package in Ubuntu: Confirmed Bug description: I'm assuming the issue is related to Compiz, but I'm not 100% sure. When I'm switching workspaces, it occasionally locks up (becoming more frequent). Most of the time, I'm going from the current one down (Ctrl+Alt+Down Arrow), and it freezes mid slide. Typically, I'm able to correct things by backing out to a terminal then returning (Ctrl+Alt+F1, pause, Alt+F7), but sometimes when I return the dual screen setup acts as one large screen (windows are stretched to the full width of both screens) and many of the windows collect on the first workspace. Ubuntu 11.04 (Classic) All packages up-to-date. If there are any logs/etc that would be helpful, let me know. --- Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,grid,imgpng,snap,compiztoolbox,resize,place,regex,move,gnomecompat,animation,vpswitch,mousepoll,workarounds,session,expo,wall,ezoom,fade,switcher,scale] DistroCodename: natty DistroRelease: Ubuntu 11.04 DistroVariant: ubuntu InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) InstallationMedia_: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) NonfreeKernelModules: nvidia Package: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 ProcVersionSignature_: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Tags: natty natty ubuntu Uname: Linux 2.6.38-10-generic x86_64 UnreportableReason: Please work this issue through technical support channels first. UpgradeStatus: Upgraded to natty on 2011-05-02 (84 days ago) UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/815996/+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 1316614] Re: Keyboard shortcuts setting value is reset after reboot.
Same problem here. My custom keyboard shortcuts are reset at reboot. It does not happen all the time, but it happens regularly enough to become annoying. -- 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/1316614 Title: Keyboard shortcuts setting value is reset after reboot. Status in “unity” package in Ubuntu: New Bug description: Ubuntu 14.04 LTS unity: Installed: 7.2.0+14.04.20140423-0ubuntu1.2 Candidate: 7.2.0+14.04.20140423-0ubuntu1.2 Version table: *** 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://kr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://kr.archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140416-0ubuntu1 0 500 http://kr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages How to reproduce: 1. Setting - Keyboard - Shortcuts - Navigation 2. Disable the "Switch to workspace left" shortcut using backspace 3. Close Setting application 3. Go to sleep mode or reboot the computer What should happen: The setting value should be "Disable" What happens instead: The setting value is default value "Ctrl+Alt+Left" ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue May 6 22:43:15 2014 InstallationDate: Installed on 2014-04-20 (16 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1316614/+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: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations
Nice bug guys, think this would ship with Windows 7 gold? -- 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: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations Status in “bamf” package in Ubuntu: Triaged Status in “nautilus” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Sometimes left clicking the nautilus launcher icon doesn't bring up a minimized nautilus window. Instead of restoring the window a new instance of nautilus is showing up. Steps to reproduce: 1. Open a nautilus window by clicking on the launcher icon. 2. Navigate to a symlinked directory whose target is located on a different harddrive (for example: a symlink to a folder on a sd-card). 3. Minimize the nautilus window. 4. Try to bring up that window again by clicking the launcher icon. What happens: 1. A new instance (window) of nautilus is opened. 2. There's no obvious way to access the first window again. The only way is ALT+TAB. What schould happen: If a nautilus window is already open and minimized clicking the launcher icon should bring up that window. This was the behavior of nautilus windows in Ubuntu 12.10 (quantal). Ubuntu 13.04 Raring Ringtail (development branch) nautilus 3.6.3-0ubuntu16 unity 7.0.0daily13.04.18~13.04-0ubuntu1 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/ubuntu/+source/bamf/+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 1315734] Re: There are no sound notifications, twitter and facebook
friends-app work but the pop-up notifications or ubuntu social networks are not seen! I do not know if they are related to friends-app -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1315734 Title: There are no sound notifications, twitter and facebook Status in “notify-osd” package in Ubuntu: New Bug description: Just after I upgraded to Ubuntu 12.04 with unity ubuntu 14:04 by cd I had no more sound notifications, notifications from social networks like twitter and facebook if there are those that can be found in friends and I would get back if possible! If you need to know were notifications thunderbird, and those of the free chat and probably almost all the other missing but as I said those sound and social networking friends who are in image https://encrypted-tbn2.google.com/images?q=tbn:ANd9GcTBuicYUPqlyVgdHC648uIdbgjnayadGQbZzHIxcA1uxlzbOGDt ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: notify-osd 0.9.35+14.04.20140213-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Sat May 3 20:26:57 2014 DesktopSession: 'ubuntu' GtkTheme: 'Radiance' IconTheme: 'unity-icon-theme' InstallationDate: Installed on 2014-04-20 (12 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=1fbfdeb5-8eba-4184-85b1-0d8013756cfd ro quiet splash RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libgl1-mesa-glx 10.1.0-4ubuntu5 libdrm2 2.4.52-1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1 xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 SourcePackage: notify-osd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0402 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5KPL-AM EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0402:bd05/22/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AMEPU:rvrx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1315734/+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 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
Launchpad has imported 8 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=78345. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2014-05-06T15:52:38+00:00 Daniel d'Andrada wrote: It happens on Ubuntu running on laptop with a touchscreen. Scenario: - There's a small window whose client called XISelectEvents on it for the touchscreen slave device with mask=XI_TouchBegin|XI_TouchUpdate|XI_TouchEnd (client[5290, /usr/lib/x86_64-linux-gnu/qt5/bin/qmlscene qml-demo-minimal-client.qml] in the logs). - compiz and nautilus (which handles the desktop background) have selections and/or grabs on the master device Actions: 1- user taps the qmlscene window. Touch events are reported to both qmlscene (from the slave device) and to compiz (from the master device). compiz rejects the touch sequence and it's not delivered to anyone else 2- user now presses on the desktop background. TouchBegin, TouchOwnership and further TouchUpdates are sent to compiz. 3- compiz rejects the touch sequence. TouchPuntToNextOwner fails to emulate a pointer and pass it to nautilus as it still thinks that touch 1 is active. And as per pointer emulation rules, only the oldest active touch is used for touch emulation. From the logs, the lines are: """ [ 9223.917] (II) TouchPuntToNextOwner: touch 2 [ 9223.917] (II) - Not all older pointer emulated touches have been seen yet. Oldest touch(client_id=1, active=1, pending_finish=0, emulate_pointer=1). """ 4- user lifts his finger So that scenario on touch 1 clearly left xserver in an inconsistent, buggy, state. Reply at: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307701/comments/28 On 2014-05-06T15:53:47+00:00 Daniel d'Andrada wrote: Created attachment 98564 Xorg.log with detailed input event handling info Reply at: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307701/comments/29 On 2014-05-06T15:54:25+00:00 Daniel d'Andrada wrote: Created attachment 98565 A filtered Xorg.log with only the interesting parts Reply at: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307701/comments/30 On 2014-05-06T15:54:42+00:00 Daniel d'Andrada wrote: Created attachment 98566 output of xinput Reply at: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307701/comments/31 On 2014-05-06T15:55:08+00:00 Daniel d'Andrada wrote: Created attachment 98567 output of xwininfo showing the whole window tree Reply at: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307701/comments/32 On 2014-05-06T15:57:35+00:00 Daniel d'Andrada wrote: For reference, those were the steps I took when recording the log - started lightdm (and threfore X) - logged in - launched the Qt app (qmlscene) - tapped on the qmlscene window - tapped on the desktop background (nautilus) - closed the Qt app (qmlscene) - stopped lightdm (and threfore X) Reply at: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307701/comments/33 On 2014-05-07T15:09:20+00:00 Bugs-i wrote: Created attachment 98629 xorg-integration-tests testcase I think this reproduces the bug quite well, does this match your logs? Reply at: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307701/comments/39 On 2014-05-07T15:56:41+00:00 Bugs-i wrote: Comment on attachment 98629 xorg-integration-tests testcase Woops, test is broken, the way it was written probably doesn't reproduce this bug. Although I believe it probably matches the description of the bug. Maybe missing something? Reply at: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307701/comments/40 ** Changed in: xorg-server Status: Unknown => Confirmed ** Changed in: xorg-server Importance: Unknown => Medium -- 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/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Triaged Status in X.Org X server: Confirmed Status in “qtbase-opensource-src” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “xorg-serve
[Dx-packages] [Bug 1208019] Re: Eclipse menus doesn't show up in Saucy
Currently the "Source" menu does not work at all in Eclipse. (100% reproducible). Both "Search" and "Refactor" appear to be working just fine. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1208019 Title: Eclipse menus doesn't show up in Saucy Status in Eclipse: Unknown Status in Unity GTK+ module: In Progress Status in “oracle-jdk7-installer” package in Ubuntu: Triaged Status in “unity-gtk-module” package in Ubuntu: Fix Released Bug description: HOW TO REPRODUCE 1. Run Eclipse, Gimp or Inkscape. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) ** EXPECTED BEHAVIOUR ** - The content of the submenus show up. ** REAL BEHAVIOUR ** - Only the top-level headers are available. - Nothing happens when clicking on them - They don't show up in the HUD either. *** WORK-AROUND *** To modify "/usr/share/applications/eclipse.desktop" to look like this: [Desktop Entry] Type=Application Name=Eclipse Comment=Eclipse Integrated Development Environment Icon=eclipse Exec=env UBUNTU_MENUPROXY= eclipse Terminal=false Categories=Development;IDE;Java; RELEVANT DETAILS - Doesn't affect Ubuntu releases prior to 13.10. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1208019/+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 872051] Re: Drag & Drop from dash to Desktop broken: produces a unusable shortcut
dinamic: Unity-2d has been removed since Ubuntu 12.10: http://www.omgubuntu.co.uk/2012/08/unity-2d-removed-from-ubuntu-12-10 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-2d in Ubuntu. https://bugs.launchpad.net/bugs/872051 Title: Drag & Drop from dash to Desktop broken: produces a unusable shortcut Status in “unity-2d” package in Ubuntu: Confirmed Bug description: When dragging from the dash to Desktop a root owned shortcut is created ls -la shows me as the owner, but properties does not lrwxrwxrwx 1 doug doug 48 2011-10-10 18:37 chromium- browser.desktop -> /usr/share/applications/chromium-browser.desktop ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity-2d 4.12.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Mon Oct 10 18:47:01 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20111007.1) PackageArchitecture: all SourcePackage: unity-2d UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/872051/+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 1208019] Re: Eclipse menus doesn't show up in Saucy
Wiktor, how are you reproducing the bug? Are you using the PPA? -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1208019 Title: Eclipse menus doesn't show up in Saucy Status in Eclipse: Unknown Status in Unity GTK+ module: In Progress Status in “oracle-jdk7-installer” package in Ubuntu: Triaged Status in “unity-gtk-module” package in Ubuntu: Fix Released Bug description: HOW TO REPRODUCE 1. Run Eclipse, Gimp or Inkscape. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) ** EXPECTED BEHAVIOUR ** - The content of the submenus show up. ** REAL BEHAVIOUR ** - Only the top-level headers are available. - Nothing happens when clicking on them - They don't show up in the HUD either. *** WORK-AROUND *** To modify "/usr/share/applications/eclipse.desktop" to look like this: [Desktop Entry] Type=Application Name=Eclipse Comment=Eclipse Integrated Development Environment Icon=eclipse Exec=env UBUNTU_MENUPROXY= eclipse Terminal=false Categories=Development;IDE;Java; RELEVANT DETAILS - Doesn't affect Ubuntu releases prior to 13.10. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1208019/+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 1315384] Re: python-indicate not showing up in message indictor
I could make the gm-notify work well after creating a python wrapper library of libmessaging-menu. Please see https://bugs.launchpad.net/ubuntu/+source/gm-notify/+bug/1310490 -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicate in Ubuntu. https://bugs.launchpad.net/bugs/1315384 Title: python-indicate not showing up in message indictor Status in Libindicate: Confirmed Status in “libindicate” package in Ubuntu: Confirmed Bug description: Install python-indicate and libindicate-doc. Run: python /usr/share/doc/libindicate/examples/im-client.py An entry should appear in message indicator, but does not. That worked in 12.04 but is broken in 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python-indicate 12.10.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 2 15:22:27 2014 InstallationDate: Installed on 2014-05-01 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libindicate UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libindicate/+bug/1315384/+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 1317253] [NEW] UI scaling and font scaling sometime get confused/change at random.
Public bug reported: I have a Lenovo Yoga 2 Pro, with a 13.3" screen running at 3200x1800 pixels... I bought this partly to test out the UI scaling in Unity!... and I have to say it's very awesome (both the screen and the UI scaling)... however I have encountered a strange problem. Seemingly at random, I have so far 3 times in 10 days had the font size (not UI size) suddenly jump to something much too large. UI scaling for the display is set at 1.38x and this is quite perfect for me, it sure means no one will be able to read my screen over my shoulder, but I that's fine! I had to install a Firefox plugin to apply scaling there, but I realise why that is. Anyway... I installed ubuntu-tweak and discovered that the large fonts were due to the "Text Scaling Factor" having jumped up to a number above 2.5... I also discovered that I could not move the slider because every time I moved it the fonts re-scaled the slider moved and lost mouse focus... and the slider reset to where it was to begin with... I clicked the button on the right to return to 1.0, and it returned to 1.4, which I assume is representative of the 1.38 I set in the screen scaling... but I have no explanation for why it suddenly jumped (when I logged out and back in) from 1.4 to something like 2.5.).. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed May 7 20:55:53 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-28 (8 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1317253 Title: UI scaling and font scaling sometime get confused/change at random. Status in “unity” package in Ubuntu: New Bug description: I have a Lenovo Yoga 2 Pro, with a 13.3" screen running at 3200x1800 pixels... I bought this partly to test out the UI scaling in Unity!... and I have to say it's very awesome (both the screen and the UI scaling)... however I have encountered a strange problem. Seemingly at random, I have so far 3 times in 10 days had the font size (not UI size) suddenly jump to something much too large. UI scaling for the display is set at 1.38x and this is quite perfect for me, it sure means no one will be able to read my screen over my shoulder, but I that's fine! I had to install a Firefox plugin to apply scaling there, but I realise why that is. Anyway... I installed ubuntu-tweak and discovered that the large fonts were due to the "Text Scaling Factor" having jumped up to a number above 2.5... I also discovered that I could not move the slider because every time I moved it the fonts re-scaled the slider moved and lost mouse focus... and the slider reset to where it was to begin with... I clicked the button on the right to return to 1.0, and it returned to 1.4, which I assume is representative of the 1.38 I set in the screen scaling... but I have no explanation for why it suddenly jumped (when I logged out and back in) from 1.4 to something like 2.5.).. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed May 7 20:55:53 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-28 (8 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1317253/+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
Re: [Dx-packages] [Bug 1208019] Re: Eclipse menus doesn't show up in Saucy
I can easily trigger this one by opening a new Window. My wild guess would be a race of sorts in MenuItem.createHandle C [libglib-2.0.so.0+0x38fe0] g_str_hash+0x0 Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) j org.eclipse.swt.internal.gtk.OS._gtk_widget_show(J)V+0 j org.eclipse.swt.internal.gtk.OS.gtk_widget_show(J)V+8 j org.eclipse.swt.widgets.MenuItem.createHandle(I)V+249 j org.eclipse.swt.widgets.Widget.createWidget(I)V+2 j org.eclipse.swt.widgets.MenuItem.(Lorg/eclipse/swt/widgets/Menu;II)V+38 j org.eclipse.ui.internal.SwitchToWindowMenu.fill(Lorg/eclipse/swt/widgets/Menu;I)V+97 2014-05-07 20:39 GMT+01:00 William Hua <1208...@bugs.launchpad.net>: > Wiktor, how are you reproducing the bug? Are you using the PPA? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1208019 > > Title: > Eclipse menus doesn't show up in Saucy > > Status in Eclipse: > Unknown > Status in Unity GTK+ module: > In Progress > Status in “oracle-jdk7-installer” package in Ubuntu: > Triaged > Status in “unity-gtk-module” package in Ubuntu: > Fix Released > > Bug description: > > HOW TO REPRODUCE > > > 1. Run Eclipse, Gimp or Inkscape. > 2. Move the cursor to the top of the screen. > 3. Click on any of the menu items (File, Edit, Navigate, ...) > > ** > EXPECTED BEHAVIOUR > ** > > - The content of the submenus show up. > > ** > REAL BEHAVIOUR > ** > > - Only the top-level headers are available. > - Nothing happens when clicking on them > - They don't show up in the HUD either. > > *** > WORK-AROUND > *** > > To modify "/usr/share/applications/eclipse.desktop" to look like this: > > [Desktop Entry] > Type=Application > Name=Eclipse > Comment=Eclipse Integrated Development Environment > Icon=eclipse > Exec=env UBUNTU_MENUPROXY= eclipse > Terminal=false > Categories=Development;IDE;Java; > > > RELEVANT DETAILS > > > - Doesn't affect Ubuntu releases prior to 13.10. > > ** > TECHNICAL INFO > ** > > ProblemType: Bug > DistroRelease: Ubuntu 13.10 > Package: eclipse 3.8.1-1ubuntu1 > ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 > Uname: Linux 3.10.0-6-generic i686 > ApportVersion: 2.11-0ubuntu1 > Architecture: i386 > Date: Sat Aug 3 17:03:55 2013 > InstallationDate: Installed on 2013-07-08 (25 days ago) > InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 > (20130708) > MarkForUpload: True > PackageArchitecture: all > SourcePackage: eclipse > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/eclipse/+bug/1208019/+subscriptions > ** Attachment added: "hs_err_pid15787.log" https://bugs.launchpad.net/bugs/1208019/+attachment/4107573/+files/hs_err_pid15787.log -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1208019 Title: Eclipse menus doesn't show up in Saucy Status in Eclipse: Unknown Status in Unity GTK+ module: In Progress Status in “oracle-jdk7-installer” package in Ubuntu: Triaged Status in “unity-gtk-module” package in Ubuntu: Fix Released Bug description: HOW TO REPRODUCE 1. Run Eclipse, Gimp or Inkscape. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) ** EXPECTED BEHAVIOUR ** - The content of the submenus show up. ** REAL BEHAVIOUR ** - Only the top-level headers are available. - Nothing happens when clicking on them - They don't show up in the HUD either. *** WORK-AROUND *** To modify "/usr/share/applications/eclipse.desktop" to look like this: [Desktop Entry] Type=Application Name=Eclipse Comment=Eclipse Integrated Development Environment Icon=eclipse Exec=env UBUNTU_MENUPROXY= eclipse Terminal=false Categories=Development;IDE;Java; RELEVANT DETAILS - Doesn't affect Ubuntu releases prior to 13.10. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present
[Dx-packages] [Bug 868346] Re: Language selector broken in Ubuntu
** Changed in: accountsservice (Ubuntu Oneiric) Assignee: (unassigned) => emmanuel ngailo (ngailoemanuel) ** Changed in: accountsservice (Ubuntu) Assignee: Gunnar Hjalmarsson (gunnarhj) => emmanuel ngailo (ngailoemanuel) ** Changed in: lightdm (Ubuntu Oneiric) Assignee: (unassigned) => emmanuel ngailo (ngailoemanuel) ** Changed in: lightdm (Ubuntu) Assignee: Gunnar Hjalmarsson (gunnarhj) => emmanuel ngailo (ngailoemanuel) -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/868346 Title: Language selector broken in Ubuntu Status in “accountsservice” package in Ubuntu: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “accountsservice” source package in Oneiric: Fix Released Status in “lightdm” source package in Oneiric: Fix Released Bug description: If you enable the language selector in lightdm-gtk-greeter, the initial value is incorrectly based on the LANG environment variable instead of the current language, and whatever option you select, the session language is still the previously saved user language. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/868346/+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 1126806] Re: unity_support_test crashed with SIGSEGV in in ??()
*** This bug is a duplicate of bug 1125568 *** https://bugs.launchpad.net/bugs/1125568 ** This bug has been marked a duplicate of bug 1125568 unity_support_test crashed with SIGSEGV in in ??() -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1126806 Title: unity_support_test crashed with SIGSEGV in in ??() Status in “nux” package in Ubuntu: Confirmed Bug description: . ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: nux-tools 4.0.0daily13.02.04-0ubuntu1 Uname: Linux 3.1.10-9-nexus7 armv7l .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu4 Architecture: armhf CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashCounter: 1 Date: Sat Feb 16 02:10:48 2013 Disassembly: => 0x0: Cannot access memory at address 0x0 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExecutablePath: /usr/lib/nux/unity_support_test GraphicsCard: Lspci: Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MarkForUpload: True ProcCmdline: /usr/lib/nux/unity_support_test ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: tegra_wdt.heartbeat=30 tegra_wdt.heartbeat=30 tegraid=30.1.3.0.0 mem=1022M@2048M android.commchip=0 vmalloc=512M androidboot.serialno=015d21098247ec0a video=tegrafb no_console_suspend=1 console=none debug_uartport=hsport usbcore.old_scheme_first=1 lp0_vec=8192@0xbddf9000 tegra_fbmem=8195200@0xabe01000 core_edp_mv=0 audio_codec=rt5640 board_info=f41:a00:1:44:2 tegraboot=sdmmc gpt gpt_sector=30535679 androidboot.bootloader=4.18 androidboot.baseband=unknown root=/dev/mmcblk0p9 rootfstype=ext4 rw console=tty0 access=m2 quiet splash rootflags=defaults,noatime,nodiratime rootsubdir=/media/0/multirom/roms/raring/root ProcModules: zram 8348 4 - Live 0x (C) Signal: 11 SourcePackage: nux StacktraceTop: ?? () NvRmMemHandleFromId () from /usr/lib/nvidia-tegra/libnvrm.so ?? () from /usr/lib/nvidia-tegra/libnvwsi.so ?? () from /usr/lib/nvidia-tegra/libnvwsi.so Title: unity_support_test crashed with SIGSEGV in NvRmMemHandleFromId() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1 version.libdrm2: libdrm2 2.4.42-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu2 xserver.bootTime: Sat Feb 16 02:11:35 2013 xserver.configfile: None xserver.devices: inputgpio-keysKEYBOARD, id 6 inputelan-touchscreen TOUCHSCREEN, id 7 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output HDMI-1 LVDS-1 xserver.version: 2:1.13.2-0ubuntu2 xserver.video_driver: tegra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1126806/+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 1125569] Re: unity_support_test crashed with SIGSEGV in in ??()
*** This bug is a duplicate of bug 1125568 *** https://bugs.launchpad.net/bugs/1125568 ** This bug has been marked a duplicate of bug 1125568 unity_support_test crashed with SIGSEGV in in ??() -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1125569 Title: unity_support_test crashed with SIGSEGV in in ??() Status in “nux” package in Ubuntu: Confirmed Bug description: . ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: nux-tools 4.0.0daily13.02.04-0ubuntu1 Uname: Linux 3.1.10-9-nexus7 armv7l ApportVersion: 2.8-0ubuntu4 Architecture: armhf CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 14 22:17:14 2013 Disassembly: => 0x0: Cannot access memory at address 0x0 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExecutablePath: /usr/lib/nux/unity_support_test GraphicsCard: Lspci: Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MarkForUpload: True ProcCmdline: /usr/lib/nux/unity_support_test ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: tegra_wdt.heartbeat=30 tegra_wdt.heartbeat=30 tegraid=30.1.3.0.0 mem=1022M@2048M android.commchip=0 vmalloc=128M androidboot.serialno=015d21098247ec0a video=tegrafb no_console_suspend=1 console=none debug_uartport=hsport usbcore.old_scheme_first=1 lp0_vec=8192@0xbddf9000 tegra_fbmem=8195200@0xabe01000 core_edp_mv=0 displayboard=0x8034:0xbf00:0x3e:0x80:0x00 audio_codec=rt5640 board_info=245:803e:3:0:0 tegraboot=sdmmc gpt gpt_sector=30535679 androidboot.bootloader=4.13 root=/dev/mmcblk0p9 rootfstype=ext4 rw console=tty0 access=m2 quiet splash rootflags=defaults,noatime,nodiratime rootsubdir=/media/0/multirom/roms/raring/root ProcModules: zram 8348 4 - Live 0x (C) Signal: 11 SourcePackage: nux StacktraceTop: ?? () NvRmMemHandleFromId () from /usr/lib/nvidia-tegra/libnvrm.so ?? () from /usr/lib/nvidia-tegra/libnvwsi.so ?? () from /usr/lib/nvidia-tegra/libnvwsi.so Title: unity_support_test crashed with SIGSEGV in NvRmMemHandleFromId() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1 version.libdrm2: libdrm2 2.4.42-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu2 xserver.bootTime: Thu Feb 14 22:16:41 2013 xserver.configfile: None xserver.devices: inputgpio-keysKEYBOARD, id 6 inputelan-touchscreen TOUCHSCREEN, id 7 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output HDMI-1 LVDS-1 xserver.version: 2:1.13.2-0ubuntu2 xserver.video_driver: tegra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1125569/+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 1311913] Re: Dash sometimes incorrectly returns no search results
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity-lens-applications (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. https://bugs.launchpad.net/bugs/1311913 Title: Dash sometimes incorrectly returns no search results Status in “unity-lens-applications” package in Ubuntu: Confirmed Bug description: I intermittently get no results when searching the dash (Ubuntu 14.04 64bit). It seems to depend on typing speed/have a random element, however here is a way which consistently reproduces the error for me (with Firefox installed): - Copy the word 'firefox' to clipboard - Open the dash (super key) and paste (ctrl+v) - Firefox result appears after a short pause - Press ctrl+backspace to clear search, then immediately ctrl+v again - Message appears 'sorry, nothing matches your search' after a short pause This seems to only happen on the 'home' lens and not the 'applications' lens specifically. It works with other applications too e.g. 'calculator'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-applications/+bug/1311913/+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 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04
** Changed in: unity Milestone: 7.0.1 => None -- 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/987060 Title: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04 Status in The Application Menu: Confirmed Status in Unity: Won't Fix Status in “unity” package in Ubuntu: Confirmed Bug description: unity-panel-service and hud-service quickly racks up memory and CPU usage until I kill it when invoking the HUD on Firefox. It's taking anywhere from a few minutes to half an hour, but it sometimes makes the system completely unusable. 1. run Firefox 12.0 in the foreground 2. hit Alt to bring up HUD 3. type any text 4. select one proposal from HUD 5. wait for unity-panel-service and hud-service to fill up the remaining RAM and swap space. This is due to a high number of bookmarks in a user profile (hundreds). To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/987060/+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 1050959] Re: Dash - Fix Dash scrollbar so that it does not displace Dash background texture
** Changed in: unity Milestone: 7.0.1 => None ** Changed in: unity/6.0 Milestone: 6.14.0 => None -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1050959 Title: Dash - Fix Dash scrollbar so that it does not displace Dash background texture Status in Ayatana Design: Fix Committed Status in Nux: In Progress Status in Unity: Won't Fix Status in Unity 6.0 series: Won't Fix Status in “nux” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Bug description: Prior to building the full version of the overlay scrollbars, the most urgent fix is to stop the current scrollbar displacing the Dash background texture. Once this issue is fixed the next step is to move on to bug #608124 To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1050959/+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 1291461] Re: Lockscreen: keyboard layout switching shortcuts not working
** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Milestone: None => 7.2.1 ** Changed in: unity Milestone: 7.2.1 => 7.3.0 ** Changed in: unity/7.2 Status: New => In Progress ** Changed in: unity/7.2 Importance: Undecided => Low ** Changed in: unity (Ubuntu) Status: Fix Released => In Progress -- 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/1291461 Title: Lockscreen: keyboard layout switching shortcuts not working Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: [Impact] New Unity Lockscreen has the same problem as the old one from Gnome: the chosen keyboard shortcut is not switching keyboard layouts on it, the only way is to use mouse. [Test Case] 1. To make things uncomfortable, switch layout to Russian or any other with your favourite shortcut(i am using alt-shift) 2. Lock the screen with ctrl-alt-l 3. Try to change layout back to English to enter password Expected: Layput should change and you should be able to login without touching anything but keyboard. What's happening: Nothing, doesn't react on the keyboard shortcut, you have to change layout using indicator on top panel. [Regression Potential] 1. There may potentially be missing keyboard shorts. 2. Key grabs may persist after the lockscreen has been released. 3. new code contains dynamic memory allocation, which always introduces potential leaks, crashes, or exhaustion To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291461/+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 1251193] Re: Language issue from the unity lense screen
** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Status: New => In Progress ** Changed in: unity/7.2 Importance: Undecided => Medium ** Changed in: unity/7.2 Milestone: None => 7.2.1 ** Changed in: unity Milestone: 7.2.1 => 7.3.0 -- 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/1251193 Title: Language issue from the unity lense screen Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: [Impact] Every characters over U+AA60 will shown as '?' in dash. It's critical to Korean user because every hangul character(Korean alphabet) is over U+AA60. [Test Case] 1. Install Ubuntu with Korean language. 2. Open dash. 3. See if dash show application's name as set of '?'. [Regression Potential] This fix modifies code added to prevent crashes in the Pango renderer when composing certain Unicode characters in the Burmese code plane. It is likely that the original problem is limited to that code plane, however it is possible that a similar desktop crash could occur with other Unicode code planes in which composite characters are rendered, including Hangul. Form the Unity lens , There are several characters of "" There should be displayed name of certain package , files, etc ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.6-0ubuntu1 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] Date: Thu Nov 14 19:38:05 2013 InstallationDate: Installed on 2013-11-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131113) MarkForUpload: TrueSourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1251193/+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 1313280] Re: Fullscreen window set to "Always on Top" in single-monitor will hide the lockscreen
** Changed in: unity Milestone: 7.2.1 => 7.3.0 ** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Status: New => In Progress ** Changed in: unity/7.2 Importance: Undecided => High ** Changed in: unity/7.2 Milestone: None => 7.2.1 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1313280 Title: Fullscreen window set to "Always on Top" in single-monitor will hide the lockscreen Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: [Impact] A fullscreen window set to "always on top" hides the lockscreem. [Test Case] (1) Open a video in Totem (2) Right-click on the titlebar and set Totem to "Always on Top" (3) Make Totem full screen (eg. with the F11 key or clicking on the control) (4) Manually Lock the screen using Super+L (5) Notice that the lockscreen is hidden by totem. If you don't lock it manually and just pause the video and let it lock automatically this will show the same behavior. The same behavior occurs with any application that can enter full screen mode. [Regression Potential]Two cases may potentially source regressions. (1) windows that need to appear above the lockscreen, such as on-screen keyboards, (2) applications presenting fullscreen windows using unusual or non-standard toolkits.It is unlikely that regressions in either of these cases would be introduced by this bug fix, but rather would be pre-existing problems not fixed here. (3) Indicator menus might be not being drawn To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313280/+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 1221673] Re: compiz crashed with SIGSEGV in CompAction::initiate()
** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Importance: Undecided => High ** Changed in: unity/7.2 Status: New => In Progress ** Changed in: unity/7.2 Milestone: None => 7.2.1 ** Changed in: unity Milestone: 7.2.1 => 7.3.0 -- 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/1221673 Title: compiz crashed with SIGSEGV in CompAction::initiate() Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: [Impact] at boot ProblemType: CrashDistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130903.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Fri Sep 6 10:38:05 2013 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-09-04 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130904) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe02b8d169d <_ZN10CompAction8initiateEv+13>: mov0x8(%rdi),%rdx PC (0x7fe02b8d169d) ok source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading NULL VMA Signal: 11SourcePackage: unity StacktraceTop: CompAction::initiate() () from /usr/lib/libcompiz_core.so.ABI-20130415 unity::MultiActionList::Initiate(std::string const&, std::vector > const&, int) const () from /usr/lib/compiz/libunityshell.so unity::MultiActionList::InitiateAll(std::vector > const&, int) const () from /usr/lib/compiz/libunityshell.so unity::PluginAdapter::InitiateExpo() () from /usr/lib/compiz/libunityshell.so unity::launcher::LauncherIcon::Activate(unity::launcher::ActionArg) () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in CompAction::initiate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo [Test Case] Unclear: this is an intermittent crash problem. [Regression Potential] The worst case is that session would continue to crash on startup. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1221673/+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 868346] Re: Language selector broken in Ubuntu
Vandalism reverted. ** Changed in: accountsservice (Ubuntu) Assignee: emmanuel ngailo (ngailoemanuel) => Gunnar Hjalmarsson (gunnarhj) ** Changed in: accountsservice (Ubuntu Oneiric) Assignee: emmanuel ngailo (ngailoemanuel) => (unassigned) ** Changed in: lightdm (Ubuntu) Assignee: emmanuel ngailo (ngailoemanuel) => Gunnar Hjalmarsson (gunnarhj) ** Changed in: lightdm (Ubuntu Oneiric) Assignee: emmanuel ngailo (ngailoemanuel) => (unassigned) -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/868346 Title: Language selector broken in Ubuntu Status in “accountsservice” package in Ubuntu: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “accountsservice” source package in Oneiric: Fix Released Status in “lightdm” source package in Oneiric: Fix Released Bug description: If you enable the language selector in lightdm-gtk-greeter, the initial value is incorrectly based on the LANG environment variable instead of the current language, and whatever option you select, the session language is still the previously saved user language. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/868346/+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 741869] Re: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs.
** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Importance: Undecided => Medium ** Changed in: unity/7.2 Status: New => In Progress ** Changed in: unity/7.2 Milestone: None => 7.2.1 ** Changed in: unity Milestone: 7.2.1 => 7.3.0 ** Changed in: unity/7.2 Importance: Medium => High -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/741869 Title: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs. Status in Ayatana Design: Fix Committed Status in Compiz: Triaged Status in Compiz Core: Triaged Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “compiz” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: New Bug description: [Impact] After upgrading from Maverick to Natty, I can no longer use the Super (windows) key in Virtual Machine Manager. Previously, as long as I had the Virtual Machine Manager console window in the foreground, I could press the Super key and the start menu would pop up. Since upgrading to Natty, this no longer works, and the search box appears in the upper left. Also see bug #934921 [Test Case] (1) Install virt-manager and qemu-system, create and boot a virtual machine (2) while in the virtual machine, press the Super key Expected Result: the super key acts inside the VM Actual Result: the super key acts in the host and the Unity Dash is displayed [regression Potential] This patch plays with ket grabs and ungrabs: the most likely potential for regression is (a) the existing grabs continue and no fix obtains or (2) the grab is not resumed when returning control from the VM and the Super key does nto invoke the Unity Dash. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/741869/+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 1312749] Re: German translation: password wrong text is too long and destroys layout
** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Importance: Undecided => High ** Changed in: unity/7.2 Status: New => In Progress ** Changed in: unity/7.2 Milestone: None => 7.2.1 ** Changed in: unity Milestone: 7.2.1 => 7.3.0 -- 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/1312749 Title: German translation: password wrong text is too long and destroys layout Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: When I try to log in with a wrong password, the string which informs me about the wrong password is too long (I will attach a "screenshot") it makes the password box enlarge, which makes the right end of it (with the circle, that is spinning while logging in) disappear. [Test Case] (1) Log in to Unity (2) Set the local to German (Use the Language Support panel in System Settings) (3) Bring up the lockscren (eg. using control-alt-L) (4) Attempt to unlock but enter an incorrect password [Regression Potential] Rendering error message text in the password dialog has been modified. It is possible the text may break incorrectly or the box may be incorrectly sized. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1312749/+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 1317277] [NEW] Don't always receive a notification of incoming SMS
You have been subscribed to a public bug: This is impossibly vague, I'm sorry. I was dogfooding u2 and I got several texts over the course of a day from the same contact that did not trigger a notification at all in indicator-messages. If I opened the Messaging app, I would see the texts. I just had to check and see because indicator-messages didn't tell me. Other contacts seemed to work fine. I don't know what was wrong with this one. ** Affects: indicator-messages (Ubuntu) Importance: Undecided Status: New -- Don't always receive a notification of incoming SMS https://bugs.launchpad.net/bugs/1317277 You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1317277] [NEW] Don't always receive a notification of incoming SMS
Public bug reported: This is impossibly vague, I'm sorry. I was dogfooding u2 and I got several texts over the course of a day from the same contact that did not trigger a notification at all in indicator-messages. If I opened the Messaging app, I would see the texts. I just had to check and see because indicator-messages didn't tell me. Other contacts seemed to work fine. I don't know what was wrong with this one. ** Affects: indicator-messages (Ubuntu) Importance: Undecided Status: New ** Package changed: telephony-service (Ubuntu) => indicator-messages (Ubuntu) -- 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/1317277 Title: Don't always receive a notification of incoming SMS Status in “indicator-messages” package in Ubuntu: New Bug description: This is impossibly vague, I'm sorry. I was dogfooding u2 and I got several texts over the course of a day from the same contact that did not trigger a notification at all in indicator-messages. If I opened the Messaging app, I would see the texts. I just had to check and see because indicator-messages didn't tell me. Other contacts seemed to work fine. I don't know what was wrong with this one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1317277/+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 1112061] Re: unity forgets focus-follows-mouse setting across update and reboot
I can confirm this happens regularly on 14.04 machines. (Focus Mode = Mouse changes to default.) I am available for testing if that's helpful. -- 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/1112061 Title: unity forgets focus-follows-mouse setting across update and reboot Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I had gone roughly two weeks without rebooting my 12.10 installation. After applying updates that included a new kernel today, I rebooted to finish the updates. Unity forgot my focus-follows-mouse setting across the updates and reboot. Thanks ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.12.0-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Thu Jan 31 18:57:02 2013 InstallationDate: Installed on 2012-10-18 (105 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to quantal on 2013-01-20 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1112061/+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 1317288] [NEW] Date and time do not show up on indicator panel
Public bug reported: Date-time indicator as well as a few other indicators (e.g. cpufreq, weather) do not show up on my indicator panel even though they are installed in my system. This happened for the first time after upgrading from Ubuntu 12.04 to 14.04. It used to show up normaly before. Other indicators (e.g. keyboard, sound, multiload) show up normaly. I have tried different things like uninstalling and re-installing the missing indicators but no luck. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140415.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Wed May 7 17:16:23 2014 InstallationDate: Installed on 2011-01-13 (1210 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1) SourcePackage: indicator-datetime UpgradeStatus: Upgraded to trusty on 2014-04-30 (6 days ago) ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty ** Attachment added: "Screenshot of my desktop verifying that the date-time is missing" https://bugs.launchpad.net/bugs/1317288/+attachment/4107616/+files/screenshot.png -- 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/1317288 Title: Date and time do not show up on indicator panel Status in “indicator-datetime” package in Ubuntu: New Bug description: Date-time indicator as well as a few other indicators (e.g. cpufreq, weather) do not show up on my indicator panel even though they are installed in my system. This happened for the first time after upgrading from Ubuntu 12.04 to 14.04. It used to show up normaly before. Other indicators (e.g. keyboard, sound, multiload) show up normaly. I have tried different things like uninstalling and re-installing the missing indicators but no luck. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140415.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Wed May 7 17:16:23 2014 InstallationDate: Installed on 2011-01-13 (1210 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1) SourcePackage: indicator-datetime UpgradeStatus: Upgraded to trusty on 2014-04-30 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1317288/+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 1313280] Re: Fullscreen window set to "Always on Top" in single-monitor will hide the lockscreen
** Changed in: unity/7.2 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1313280 Title: Fullscreen window set to "Always on Top" in single-monitor will hide the lockscreen Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: [Impact] A fullscreen window set to "always on top" hides the lockscreem. [Test Case] (1) Open a video in Totem (2) Right-click on the titlebar and set Totem to "Always on Top" (3) Make Totem full screen (eg. with the F11 key or clicking on the control) (4) Manually Lock the screen using Super+L (5) Notice that the lockscreen is hidden by totem. If you don't lock it manually and just pause the video and let it lock automatically this will show the same behavior. The same behavior occurs with any application that can enter full screen mode. [Regression Potential]Two cases may potentially source regressions. (1) windows that need to appear above the lockscreen, such as on-screen keyboards, (2) applications presenting fullscreen windows using unusual or non-standard toolkits.It is unlikely that regressions in either of these cases would be introduced by this bug fix, but rather would be pre-existing problems not fixed here. (3) Indicator menus might be not being drawn To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313280/+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 1313280] Re: Fullscreen window set to "Always on Top" in single-monitor will hide the lockscreen
** Changed in: unity (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1313280 Title: Fullscreen window set to "Always on Top" in single-monitor will hide the lockscreen Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: [Impact] A fullscreen window set to "always on top" hides the lockscreem. [Test Case] (1) Open a video in Totem (2) Right-click on the titlebar and set Totem to "Always on Top" (3) Make Totem full screen (eg. with the F11 key or clicking on the control) (4) Manually Lock the screen using Super+L (5) Notice that the lockscreen is hidden by totem. If you don't lock it manually and just pause the video and let it lock automatically this will show the same behavior. The same behavior occurs with any application that can enter full screen mode. [Regression Potential]Two cases may potentially source regressions. (1) windows that need to appear above the lockscreen, such as on-screen keyboards, (2) applications presenting fullscreen windows using unusual or non-standard toolkits.It is unlikely that regressions in either of these cases would be introduced by this bug fix, but rather would be pre-existing problems not fixed here. (3) Indicator menus might be not being drawn To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313280/+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 1317150] [NEW] When I create .desktop files, they don't get found by Trusty's Dash
You have been subscribed to a public bug: Magnifier not found by Trusty's Dash though Manage Launcher (both variants) are. I've tried creating Magnifier.desktop both with 'Manage Launcher', 'Manage Launcher (Administrator)' & Arronax. root@JohnDesktop:/home/john# ls -l /usr/share/applications/Ma* -rw-r-- r-- 1 root root 142 May 7 15:35 /usr/share/applications/Magnifier.desktop -rw-r--r-- 1 root root 322 Oct 1 2013 /usr/share/applications/Manage Launcher (Administrator).desktop -rw-r--r-- 1 root root 281 Oct 1 2013 /usr/share/applications/Manage Launcher.desktop ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: dash 0.5.7-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 7 16:43:02 2014 InstallationDate: Installed on 2014-04-25 (12 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: dash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity-lens-applications (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- When I create .desktop files, they don't get found by Trusty's Dash https://bugs.launchpad.net/bugs/1317150 You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1317150] Re: When I create .desktop files, they don't get found by Trusty's Dash
** Package changed: dash (Ubuntu) => unity-lens-applications (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. https://bugs.launchpad.net/bugs/1317150 Title: When I create .desktop files, they don't get found by Trusty's Dash Status in “unity-lens-applications” package in Ubuntu: New Bug description: Magnifier not found by Trusty's Dash though Manage Launcher (both variants) are. I've tried creating Magnifier.desktop both with 'Manage Launcher', 'Manage Launcher (Administrator)' & Arronax. root@JohnDesktop:/home/john# ls -l /usr/share/applications/Ma* -rw-r-- r-- 1 root root 142 May 7 15:35 /usr/share/applications/Magnifier.desktop -rw-r--r-- 1 root root 322 Oct 1 2013 /usr/share/applications/Manage Launcher (Administrator).desktop -rw-r--r-- 1 root root 281 Oct 1 2013 /usr/share/applications/Manage Launcher.desktop ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: dash 0.5.7-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 7 16:43:02 2014 InstallationDate: Installed on 2014-04-25 (12 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: dash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-applications/+bug/1317150/+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 1309052] Re: To be able to show also the date and time, not only the hour.
** Changed in: indicator-datetime (Ubuntu) Status: Incomplete => Invalid -- 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/1309052 Title: To be able to show also the date and time, not only the hour. Status in “indicator-datetime” package in Ubuntu: Invalid Bug description: It whould be very usefull to show the date in the menu, not only time, so often I have to click to see the day, it would be usefull to be able to setup if I wish to see also the month and day. Bests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1309052/+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 754580] Re: Cannot move tabs between multiple Firefox or Chromium windows while using Unity unless windows are both unmaximized, unminimized, and visible.
** Changed in: unity Milestone: None => 7.2.1 ** Changed in: unity Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity Status: Triaged => In Progress ** Also affects: unity/7.3 Importance: Undecided Status: New ** Changed in: unity/7.3 Status: New => In Progress ** Changed in: unity Importance: High => Medium ** Changed in: unity/7.3 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity/7.3 Importance: Undecided => Medium ** Changed in: unity/7.3 Milestone: None => 7.3.0 ** Branch linked: lp:~3v1n0/unity/dnd-launcher-icon-fixes -- 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/754580 Title: Cannot move tabs between multiple Firefox or Chromium windows while using Unity unless windows are both unmaximized, unminimized, and visible. Status in Ayatana Design: Fix Committed Status in Chromium Browser: New Status in Unity: In Progress Status in Unity 7.3 series: In Progress Status in “chromium-browser” package in Ubuntu: Triaged Status in “firefox” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Triaged Bug description: Binary package hint: unity With Metacity, one would need only to drag the tab to the bottom bar, mouse-over the destination window, and then release the tab in the newly focused window. There is no equivalent behavior with Unity. Dragging tabs to its bar does nothing. - Desired resolution: Users should be able to move tabs between browser windows irrespective of window state (minimised, restored or maximised) by dragging and dropping the via the Launcher app spread. Use case 1. User opens two Chromium or Firefox windows, with two tabs open in each. 2. User starts dragging a browser tab 3. Unity slides out the Launcher with valid drop receptacles highlighted 4. User drags the tab over a browser icon in the Launcher 5. Unity displays a spread of the two browser windows 6. User continues the drag, and drags and drops the tab into the other browser window 7. Unity shifts the tab to the other browser window. If this window is minimised it is restored and brought into focus. If this window is maximised or restored it is brought into focus. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/754580/+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 784435] Re: Launcher - Dragging and dropping a file directly on to the Thunderbird or Evolution Launcher icons should open a new email with the file attached
** Changed in: unity Status: Confirmed => Won't Fix -- 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/784435 Title: Launcher - Dragging and dropping a file directly on to the Thunderbird or Evolution Launcher icons should open a new email with the file attached Status in Ayatana Design: Fix Committed Status in Unity: Won't Fix Status in “evolution” package in Ubuntu: Triaged Status in “thunderbird” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Desired functionality: Dragging and dropping a file directly on to the Thunderbird or Evolution Launcher icons should open a new email with the file attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/784435/+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
I also can't find any dconf (gsettings) setting to make the menu permanently visible in Ubuntu 14.04. How to do that? -- 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: Triaged 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 865344] Re: Unity keeps shortcuts to desktop files instead of copies
** Changed in: unity (Ubuntu) Status: Triaged => Invalid ** Changed in: unity Status: Triaged => Won't Fix -- 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/865344 Title: Unity keeps shortcuts to desktop files instead of copies Status in Unity: Won't Fix Status in “unity” package in Ubuntu: Invalid Bug description: I have installed a game via Wine (which created a nice shortcut on my desktop). After moving the shortcut to Unity panel, it showed up correctly, but after removing the shortcut from my desktop shortcut in Unity disappeared. This behaviour is desired, because the icons of not installed apps will disappear automatically, but will prevent using it for 3rd party applications or WINE applications. Steps to reproduce : 1. In terminal: cp /usr/share/applications/gedit.desktop ~/; chmod +x ~/gedit.desktop 2. Drag the gedit icon from your home directory to the panel 3. Watch the icon show up on the panel 4. Delete the icon from your home directory 5. Watch the icon disappear Fix: Unity should create copies of desktop files that are not located in "/usr/share/applications" and "/usr/local/share/applications". So the current behaviour will remain, but will allow users to add their own custom launchers. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/865344/+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 1067349] Re: Unity is sluggish and uses a lot of CPU (even with hardware support) on low-end systems
This issue is no longer present in 14.04. -- 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/1067349 Title: Unity is sluggish and uses a lot of CPU (even with hardware support) on low-end systems Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I asked this question already on Askubuntu, but was directed to file a bug: I have a nice Lenovo Thinkpad Edge 11 AMD Neo II with a ATI Radeon 4225 integrated graphics device. In my perception this is already a not-so-lowspeced device, but still a netbook. Up to Ubuntu 12.04 precise pangolin I preferred Unity2D over Unity mainly because it did perform much better than Unity and moreover I was able to achieve 5-6h with one battery charge. The typical load of an idling desktop settled around 0.00 to 0.02. Yesterday I tried the new Beta 2 of Ubuntu Quantal Quetzal: This does no longer offer a Unity2D version. The performance itself has definitely improved over Unity in precise, but nevertheless I do experience now a minimum load of 0.24 to 0.36 while completely idling. According to top this is mainly due to compiz eating about 3-6% CPU all the time. In comparison to my Unity2D experience, quantal is more sluggish, eats much faster my battery and produces significant more fan noise. I already tried a few tweaks like static blurring, fast texture renderer or choosing alternate window manager on precise, but without a significant change. Are there ways which enable me to continue to use Ubuntu/Unity on my device without major loss of functionality, performance and battery life? --- ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom] DistroRelease: Ubuntu 12.10 MarkForUpload: True Package: unity 6.8.0-0ubuntu2 PackageArchitecture: i386 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Tags: quantal running-unity Uname: Linux 3.5.0-18-generic i686 UpgradeStatus: Upgraded to quantal on 2012-11-06 (0 days ago) UserGroups: adm admin audio cdrom floppy fuse kvm lpadmin netdev plugdev tape video To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1067349/+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 1312882] Re: Main menu of Qt apps locally integrated in the window title bar disappears after activation of any menu item
Also have to mixx. ** Description changed: [The bug] When the integration of the app menus into the window title bars is turned on, call of any dialogue from the menu leads to disappearance of the menu. After that, the window title bar displays only the application title string. The main menu cannot be seen and cannot be accessed until you switch to another application and then return. The bug is observed only for unmaximized windows. The main menu of maximized windows works fine. - This bug is observed only for Qt applications. I have “succeeded” to reproduce it for VLC, Gwenview, digiKam, Krita, Calliga, VirtualBox, GoldenDict. + This bug is observed only for Qt applications. I have “succeeded” to reproduce it for VLC, Gwenview, digiKam, Krita, Calliga, VirtualBox, GoldenDict, Mixx. [How to reproduce] 1. Make sure that “Show the menus for a window” parameter (System Settings -> Appearance -> Behavior) is set to “In the window's title bar”. 2. Start any Qt application, say, one of mentioned above. Let it be, for example, Gwenview. 3. Unmaximize the app window. 4. Activate any dialogue from the main menu. For instance, File -> Open... or Settings -> Configure Gwenview... 5. Press Cancel to close the dialogue. 6. Hover the mouse pointer over the window title bar. [What is expected] The app menu should appear and be accessible. [What happens] The app menu is not shown. Only the application title is displayed in the title bar. The following screencast shows the bug “in action”: http://www.youtube.com/watch?v=WAfJXmwDJpg&feature=youtu.be ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,imgjpeg,decor,snap,move,gnomecompat,imgpng,vpswitch,place,grid,resize,text,imgsvg,unitymtgrabhandles,regex,mousepoll,session,wall,animation,fade,expo,workarounds,scale,ezoom,unityshell] CurrentDesktop: Unity Date: Fri Apr 25 22:38:19 2014 InstallationDate: Installed on 2012-05-02 (723 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-21 (3 days ago) -- 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/1312882 Title: Main menu of Qt apps locally integrated in the window title bar disappears after activation of any menu item Status in “unity” package in Ubuntu: Confirmed Bug description: [The bug] When the integration of the app menus into the window title bars is turned on, call of any dialogue from the menu leads to disappearance of the menu. After that, the window title bar displays only the application title string. The main menu cannot be seen and cannot be accessed until you switch to another application and then return. The bug is observed only for unmaximized windows. The main menu of maximized windows works fine. This bug is observed only for Qt applications. I have “succeeded” to reproduce it for VLC, Gwenview, digiKam, Krita, Calliga, VirtualBox, GoldenDict, Mixx. [How to reproduce] 1. Make sure that “Show the menus for a window” parameter (System Settings -> Appearance -> Behavior) is set to “In the window's title bar”. 2. Start any Qt application, say, one of mentioned above. Let it be, for example, Gwenview. 3. Unmaximize the app window. 4. Activate any dialogue from the main menu. For instance, File -> Open... or Settings -> Configure Gwenview... 5. Press Cancel to close the dialogue. 6. Hover the mouse pointer over the window title bar. [What is expected] The app menu should appear and be accessible. [What happens] The app menu is not shown. Only the application title is displayed in the title bar. The following screencast shows the bug “in action”: http://www.youtube.com/watch?v=WAfJXmwDJpg&feature=youtu.be ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,imgjpeg,decor,snap,move,gnomecompat,imgpng,vpswitch,place,grid,resize,text,imgsvg,unitymtgrabhandles,regex,mousepoll,session,wall,animation,fade,expo,workarounds,scale,ezoom,unityshell] CurrentDesktop: Unity Date: Fri Apr 25 22:38:19 2014 InstallationDate: Installed on 2012-05-02 (723 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-21 (3 days ago) To manage notifications ab
[Dx-packages] [Bug 1317348] [NEW] Switcher (Alt-Tab) does not respect monitor-defined scaling factor
Public bug reported: Unity switcher doesn't get properly scaled on HiDPI monitors. ** Affects: unity Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: unity/7.2 Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: unity (Ubuntu) Importance: Undecided Status: In Progress ** Tags: hidpi ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: New => In Progress ** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Status: New => In Progress ** Changed in: unity/7.2 Importance: Undecided => High ** Changed in: unity/7.2 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity/7.2 Milestone: None => 7.2.1 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1317348 Title: Switcher (Alt-Tab) does not respect monitor-defined scaling factor Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Unity switcher doesn't get properly scaled on HiDPI monitors. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317348/+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 1317348] Re: Switcher (Alt-Tab) does not respect monitor-defined scaling factor
** Branch linked: lp:~3v1n0/unity/switcher-hidpi -- 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/1317348 Title: Switcher (Alt-Tab) does not respect monitor-defined scaling factor Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Unity switcher doesn't get properly scaled on HiDPI monitors. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317348/+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 890271] Re: Timezone bug in event list for ICAL events
[Expired for Indicator Date and Time because there has been no activity for 60 days.] ** Changed in: indicator-datetime Status: Incomplete => Expired -- 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/890271 Title: Timezone bug in event list for ICAL events Status in The Date and Time Indicator: Expired Status in “indicator-datetime” package in Ubuntu: Expired Bug description: For events from a web-served ICAL file, the dates show up correctly in Evolution and in the indicator event list. Alarms also go off at the correct time. But the indicator event list only shows events that are at least 5 hours in the future. I am in EST timezone (-5h), so perhaps the code to filter out events in the past does not taking the timezone into account? This only happens for events from my ICAL file. normal Evolution events show up as expected. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: indicator-datetime 0.3.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Mon Nov 14 09:50:32 2011 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/tcsh SourcePackage: indicator-datetime UpgradeStatus: Upgraded to oneiric on 2011-10-17 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/890271/+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 890271] Re: Timezone bug in event list for ICAL events
[Expired for indicator-datetime (Ubuntu) because there has been no activity for 60 days.] ** Changed in: indicator-datetime (Ubuntu) Status: Incomplete => Expired -- 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/890271 Title: Timezone bug in event list for ICAL events Status in The Date and Time Indicator: Expired Status in “indicator-datetime” package in Ubuntu: Expired Bug description: For events from a web-served ICAL file, the dates show up correctly in Evolution and in the indicator event list. Alarms also go off at the correct time. But the indicator event list only shows events that are at least 5 hours in the future. I am in EST timezone (-5h), so perhaps the code to filter out events in the past does not taking the timezone into account? This only happens for events from my ICAL file. normal Evolution events show up as expected. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: indicator-datetime 0.3.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Mon Nov 14 09:50:32 2011 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/tcsh SourcePackage: indicator-datetime UpgradeStatus: Upgraded to oneiric on 2011-10-17 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/890271/+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 1317356] [NEW] Shortcut hint does not respect monitor scaling factor
Public bug reported: The shortcut hint is not properly scaled in HiDPI monitors ** Affects: unity Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: unity/7.2 Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: unity (Ubuntu) Importance: Undecided Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Tags: hidpi ** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Status: New => In Progress ** Changed in: unity/7.2 Importance: Undecided => Medium ** Changed in: unity/7.2 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity/7.2 Milestone: None => 7.2.1 ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: New => In Progress ** Changed in: unity (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1317356 Title: Shortcut hint does not respect monitor scaling factor Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: The shortcut hint is not properly scaled in HiDPI monitors To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317356/+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 1317356] Re: Shortcut hint does not respect monitor scaling factor
** Branch linked: lp:~3v1n0/unity/shortcuts-hidpi -- 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/1317356 Title: Shortcut hint does not respect monitor scaling factor Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: The shortcut hint is not properly scaled in HiDPI monitors To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317356/+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 1315384] Re: python-indicate not showing up in message indictor
libmessaging-menu already comes with python bindings through gobject-
introspection. Unfortunately the online documentation seems to have been
taken down. The libmessaging-menu-dev package contains the C
documentation (viewable with devhelp), which maps 1:1 to the python API.
Here's a simple example:
from gi.repository import GLib, Gio, MessagingMenu
mmapp = MessagingMenu.App(desktop_id='my-app.desktop')
# make the application appear in the messaging menu. The name and icon are
taken from the desktop file above
mmapp.register()
def source_activated(mmapp, source_id):
print('source {} activated'.format(source_id))
# do something when the user clicks on a source. The source will be removed
automatically
mmapp.connect('activate-source', source_activated)
# add a 'source' (a menu item below the application's name) with the name
'Inbox' and a count of 7
icon = Gio.ThemedIcon.new_with_default_fallbacks('my-source-icon')
mmapp.append_source_with_count('inbox', icon, 'Inbox', 7)
# this is not necessary for gtk applications, which start a mainloop in
gtk_main()
GLib.MainLoop().run()
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to libindicate in Ubuntu.
https://bugs.launchpad.net/bugs/1315384
Title:
python-indicate not showing up in message indictor
Status in Libindicate:
Confirmed
Status in “libindicate” package in Ubuntu:
Confirmed
Bug description:
Install python-indicate and libindicate-doc. Run:
python /usr/share/doc/libindicate/examples/im-client.py
An entry should appear in message indicator, but does not. That worked
in 12.04 but is broken in 14.04.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: python-indicate 12.10.1-0ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Fri May 2 15:22:27 2014
InstallationDate: Installed on 2014-05-01 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: libindicate
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/libindicate/+bug/1315384/+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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
** Also affects: unity-settings-daemon (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/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Invalid Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: Confirmed Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: In Progress Status in “unity-settings-daemon” package in Ubuntu: New Bug description: Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- control-center 3.10. This however requires a transition to gnome- desktop 3-10. I have been working on this for quite some time however this work was essentially blocked waiting on the unity- forks for settings daemon and control center. These were only finalised the day before feature freeze. Right now there are quite a few features that are not available for configuration in g-c-c given it is so old. We are also hitting some odd bugs with mutter using its own display config separate to what gnome-settings-daemon is doing with xrandr. For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such have forked the display config code from mutter and ported *-settings-daemon and *-control-center to the new api. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. We have tested this via a ppa, however it was hard to get extensive testing, due to the amount of archive churn in the affected packages. I am pretty confident there are no much regressions and I will commit to fixing any issues to do appear. Essentially this transition will involve: new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session) my upstream branch is at https://github.com/darkxst/displayconfig (I had trouble working out how to import a git branch into bzr, but I imagine it should live in bzr once approved) gnome/unity-settings-daemon, have backported patches to adapt to the new API. Likewise for gnome/unity-control-center. All other rdepends just require a no-change rebuild to adapt to the new soname. Assuming this gets a approved, subsequent FFe's for gnome-settings- daemon and gnome-control-center 3.10 will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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
