[Dx-packages] [Bug 1300624] Re: indicator-bluetooth-service crashed with SIGSEGV in g_closure_invoke()
*** This bug is a duplicate of bug 1272686 *** https://bugs.launchpad.net/bugs/1272686 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1272686, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1300624/+attachment/4057347/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1300624/+attachment/4057349/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1300624/+attachment/4057351/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1300624/+attachment/4057352/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1300624/+attachment/4057353/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1300624/+attachment/4057354/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1300624/+attachment/4057355/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1272686 indicator-bluetooth-service crashed with SIGSEGV in org_bluez_adapter_set_property() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1300624 Title: indicator-bluetooth-service crashed with SIGSEGV in g_closure_invoke() Status in “indicator-bluetooth” package in Ubuntu: New Bug description: I switched on visibility from the applet when it just disappeared and seem to have crashed ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 1 09:24:12 2014 EcryptfsInUse: Yes ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service InstallationDate: Installed on 2014-03-30 (1 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service SegvAnalysis: Segfault happened at: 0x40d880: mov(%rbx),%rdi PC (0x0040d880) ok source (%rbx) (0x) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-bluetooth StacktraceTop: ?? () ?? () ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: indicator-bluetooth-service crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to trusty on 2014-03-30 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo upstart.indicator-bluetooth.log: ** (process:25679): CRITICAL **: bluez.vala:104: GDBus.Error:org.bluez.Error.NoSuchAdapter: No such adapter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1300624/+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 1300627] Re: compiz crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 962581 *** https://bugs.launchpad.net/bugs/962581 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #962581, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1300627/+attachment/4057356/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1300627/+attachment/4057358/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1300627/+attachment/4057360/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1300627/+attachment/4057361/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1300627/+attachment/4057362/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1300627/+attachment/4057363/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1300627/+attachment/4057364/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 962581 compiz crashed with SIGSEGV in empty() from check_selection() [unity-rvgrid-accessible.cpp:171] ** Information type changed from Private to Public ** Tags removed: need-i386-retrace -- 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/1300627 Title: compiz crashed with SIGSEGV in g_main_context_dispatch() Status in “unity” package in Ubuntu: New Bug description: This happend while I was using Launchpad ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-60.91-generic-pae 3.2.55 Uname: Linux 3.2.0-60-generic-pae i686 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 Date: Tue Apr 1 12:58:00 2014 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0xb474372f:mov0x4(%ecx),%edx PC (0xb474372f) ok source 0x4(%ecx) (0x0024) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/compiz/libunityshell.so ?? () from /usr/lib/compiz/libunityshell.so ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: compiz crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: (compiz:3566): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed gnome-session[3494]: WARNING: Application 'compiz.desktop' killed by signal gnome-session[3494]: WARNING: App 'compiz.desktop' respawning too quickly gnome-session[3494]: CRITICAL: We failed, but the fail whale is dead. Sorry (compiz:4137): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1300627/+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 1300638] Re: compiz crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
*** This bug is a duplicate of bug 1300219 *** https://bugs.launchpad.net/bugs/1300219 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1300219, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1300638/+attachment/4057445/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1300638/+attachment/4057447/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1300638/+attachment/4057449/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1300638/+attachment/4057450/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1300638/+attachment/4057451/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1300638/+attachment/4057452/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1300638/+attachment/4057453/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1300219 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1300638 Title: compiz crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() Status in “unity” package in Ubuntu: New Bug description: compiz crashed as soon as I switched from another user session to this session that I'm reporting the bug from. ProblemType: Crash 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 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 1 09:35:38 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-03-08 (23 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140304) ProcCmdline: compiz Signal: 6 SourcePackage: unity StacktraceTop: __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::__throw_bad_function_call() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: compiz crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: nopasswdlogin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1300638/+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 1292451] Re: screensaver re-locks itself after unlocking if the configured screen-off timer goes off while screen is locked
Still broken here too. -- 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/1292451 Title: screensaver re-locks itself after unlocking if the configured screen- off timer goes off while screen is locked Status in Unity: New Status in “gnome-screensaver” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Set screen-off timeout to 1 minute 2. Configure screen to lock immediately when screen goes off. 3. Lock screen manually (Ctrl+Alt+L) 4. Wait for 1 minute 5. Notice that screen doesn't turn off 6. Unlock screen 7. Wait a couple of seconds (~10 or so) 8. Notice that screen re-locks itself. 9. Repeat steps 6-7 and notice that the screen doesn't re-lock itself this time. There are two bugs described here: 1. Screen does not shut off if the screen is locked manually before the idle timer (see step 5). 2. Screen re-locks itself after unlocking if the idle timer goes off while the screen is locked (see step 7). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 14 18:19:26 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-03-03 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292451/+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] [NEW] XBMC steals input from the lockscreen
Public bug reported: 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) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lockscreen 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/1300646 Title: XBMC steals input from the lockscreen Status in “unity” package in Ubuntu: New 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/ubuntu/+source/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 1298088] Re: battery indicator is hidden when no battery is present
Ah, this is a bug in the design. Where there is a battery slot with no battery in it, its menu item should say Battery (not present). But with the current design, that item will never appear, unless there happen to be any other chargeable components connected to ensure that the menu is present at all! So the default When a battery is present setting needs to change to something meaning When a battery, battery slot, or anything chargeable is present. But that's much too long for a menu item, so we need a shorter way of saying it. -- 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/1298088 Title: battery indicator is hidden when no battery is present Status in “indicator-power” package in Ubuntu: New Bug description: Though there's no battery attached on my laptop but then it should have a indicator in panel that power is plug in. lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 Beta2 upower -d Device: /org/freedesktop/UPower/devices/line_power_AC native-path: AC power supply: yes updated: Thursday, 27 March, 2014 05:32:48 AM PHT (2129 seconds ago) has history: no has statistics: no line-power online: yes Daemon: daemon-version: 0.9.23 can-suspend: yes can-hibernate: no on-battery: no on-low-battery: no lid-is-closed: no lid-is-present: yes is-docked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1298088/+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 1300649] Re: Schemas should not come with the library package
Added task for unity8, since we'd need to switch unless bug #1300650 is solved first. -- 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/1300649 Title: Schemas should not come with the library package Status in “unity” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Bug description: ⟫ dpkg -L libunity-core-6.0-9 | grep schemas /usr/share/glib-2.0/schemas /usr/share/glib-2.0/schemas/com.canonical.Unity.gschema.xml /usr/share/glib-2.0/schemas/org.compiz.unityshell.gschema.xml /usr/share/glib-2.0/schemas/org.compiz.unitymtgrabhandles.gschema.xml /usr/share/glib-2.0/schemas/org.compiz.unitydialog.gschema.xml /usr/share/glib-2.0/schemas/org.compiz.networkarearegion.gschema.xml 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:30:16 2014 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/1300649/+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 1290171] Re: appointments don't change when you click on a calendar date
With latest update, it lists all events for all past selected dates properly except today's date. When I click any past date on calendar it shows: 1. all all-day events. 2. all events with time 3. future all day events 4. future events with time But when I click on today's date it only shows: 1. future all day events #now it seems it doesn't show calendar color from evolution anymore(?) 2. future events with time I still have to click on previous day's date to find out all all-day events for today. The behavior should be same for any date including today's date. -- 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/1290171 Title: appointments don't change when you click on a calendar date Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: In the desktop's Coming Events section, we should update the event/alarm entries based on the date clicked on in the Monthly Calendar section. In indicator-datetime-13.10.0+14.04.20140227.1-0ubuntu1, the events are tied to the current clock time and do not change when you click on another date in the calendar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1290171/+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 1155561] Re: Unity Launcher sometimes fails to reveal on mouse move (autohide)
The bug still exists in 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/1155561 Title: Unity Launcher sometimes fails to reveal on mouse move (autohide) Status in “unity” package in Ubuntu: Confirmed Bug description: In Raring, the launcher fails to reveal with mouse mouvement. Settings are set to 32 pixels wide launcher, and sensitivity slightly above default. This does not happen always, but quite often. I could not define the exact scenario that triggers the problem... Hitting the Super button makes the launcher appear. Once it has appeared, it will show again on mouse move to the left, until... this happens again. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.03.13.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2 Uname: Linux 3.8.0-12-generic x86_64 ApportVersion: 2.9.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Mar 15 11:50:25 2013 InstallationDate: Installed on 2013-02-16 (26 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130216) MarkForUpload: True 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/1155561/+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 1073114] Re: Online Smart Scopes Do Not Respect User Privacy
@bkerensa: well, right now we just have the OMG Ubuntu article and some explanations from Michael Hall on Google+. I would wait to see what explanations/details the devs from Unity team can provide here. AFAIC, to be considered fixed, all the correctives proposed by EFF should be implemented and the opt-in should applied not only to Amazon scopes, but also to all online scopes/search. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1073114 Title: Online Smart Scopes Do Not Respect User Privacy Status in “libunity” package in Ubuntu: In Progress Status in “unity-lens-shopping” package in Ubuntu: In Progress Status in “libunity” source package in Quantal: Won't Fix Status in “unity-lens-shopping” source package in Quantal: Won't Fix Status in “libunity” source package in Raring: Won't Fix Status in “unity-lens-shopping” source package in Raring: Won't Fix Bug description: See this from the Electronic Frontier Foundation (EFF), a well respected international non-profit digital rights advocacy and legal organization (as described on Wikipedia): https://www.eff.org/deeplinks/2012/10/privacy-ubuntu-1210-amazon-ads- and-data-leaks Obviously, despite some improvements that have came late in the 12.10 development cycle, there are still serious privacy concerns with the unity shopping lens. To be more precise, here are the main problems to be fixed according to EFF: - Disable Include online search results by default. - Explain in detail what Canonical does with search queries and IP addresses, how long it stores them, and in what circumstances it gives them to third parties. - Make the Search Results tab of the Privacy settings let users toggle on and off specific online search results, as some users might want Amazon products in their search results, but never anything from Facebook. Here is another related bug: #1055952 Direct data leaking to Amazon: https://bugs.launchpad.net/ubuntu/+source/unity-lens- shopping/+bug/1055952 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity-lens-shopping 6.8.0-0ubuntu1 Uname: Linux 3.5.6-030506-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Tue Oct 30 06:35:38 2012 InstallationDate: Installed on 2012-02-12 (260 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True SourcePackage: unity-lens-shopping UpgradeStatus: Upgraded to quantal on 2012-09-28 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1073114/+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 1300722] [NEW] hud-service is eating up 100% of one of my CPUs in a pool loop
Public bug reported: hud-service is polling like crazy: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 2295 hud-service 46084.6342.94 46127.58 (very high) 2325 hud-service 0.09 0.00 0.09 (very low) 2329 hud-service 0.07 0.00 0.07 (very low) 2340 hud-service 0.05 0.00 0.05 (very low) Total 46084.8442.94 46127.78 File I/O operations: No file I/O operations detected. System calls traced: PID Process Syscall CountRate/Sec 2295 hud-service poll 83 23124.8503 2295 hud-service write10 0.2313 2295 hud-service sendmsg 4 0.0925 2325 hud-service restart_syscall 1 0.0231 2329 hud-service restart_syscall 1 0.0231 2340 hud-service restart_syscall 1 0.0231 Total 100 23125.2435 (gdb) where #0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from /usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2 #9 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() () #17 0x00441e43 in hud::service::WindowImpl::activate() () #18 0x00439f6a in hud::service::QueryImpl::updateToken(QSharedPointerhud::service::Window) () #19 0x0043a672 in hud::service::QueryImpl::refresh() () #20 0x0044b115 in ?? () #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x0045662a in hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const, unsigned int) () #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00467361 in ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, QString const, unsigned int) () #25 0x004678bd in ?? () #26 0x00467c63 in ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, void**) () #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #28 0x7fda8435e22e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7fda84335c2d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7fda84337e07 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7fda84382cd3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7fda833dbe04 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x7fda833dc048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: hud 13.10.1+14.04.20140326-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 1 12:23:11 2014 EcryptfsInUse: Yes InstallationDate: Installed on
[Dx-packages] [Bug 607796] Re: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application
** Description changed: If the user drags and hold a file over a running application in the Launcher, all the windows of that application should be shown with the spread. The user should then be able to drag and drop the file in a windows in the spread to load the file into that specific window. Bug #727903 needs to be fixed at the same time. --- History: This bug had been previously fixed as buggybutclosed for Unity on 2011-04-18, leaving this function with other bugs: https://bugs.launchpad.net/ayatana-design/+bug/727903 https://bugs.launchpad.net/ayatana-design/+bug/727904 https://bugs.launchpad.net/ayatana-design/+bug/727902 https://bugs.launchpad.net/ayatana-design/+bug/764424 + https://bugs.launchpad.net/ayatana-design/+bug/832988 On 2011-10-18, it was reopened for regression in Oneiric. -- 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/607796 Title: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application Status in Ayatana Design: Fix Committed Status in One Hundred Papercuts: Fix Released Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: If the user drags and hold a file over a running application in the Launcher, all the windows of that application should be shown with the spread. The user should then be able to drag and drop the file in a windows in the spread to load the file into that specific window. Bug #727903 needs to be fixed at the same time. --- History: This bug had been previously fixed as buggybutclosed for Unity on 2011-04-18, leaving this function with other bugs: https://bugs.launchpad.net/ayatana-design/+bug/727903 https://bugs.launchpad.net/ayatana-design/+bug/727904 https://bugs.launchpad.net/ayatana-design/+bug/727902 https://bugs.launchpad.net/ayatana-design/+bug/764424 https://bugs.launchpad.net/ayatana-design/+bug/832988 On 2011-10-18, it was reopened for regression in Oneiric. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/607796/+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 1300722] Re: hud-service is eating up 100% of one of my CPUs in a pool loop
Indeed, there's a number of these instances. If I could find out which application it is that causes this, it'd help a lot with debugging. -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1300722 Title: hud-service is eating up 100% of one of my CPUs in a pool loop Status in “hud” package in Ubuntu: New Bug description: hud-service is polling like crazy: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 2295 hud-service 46084.6342.94 46127.58 (very high) 2325 hud-service 0.09 0.00 0.09 (very low) 2329 hud-service 0.07 0.00 0.07 (very low) 2340 hud-service 0.05 0.00 0.05 (very low) Total 46084.8442.94 46127.78 File I/O operations: No file I/O operations detected. System calls traced: PID Process Syscall CountRate/Sec 2295 hud-service poll 83 23124.8503 2295 hud-service write10 0.2313 2295 hud-service sendmsg 4 0.0925 2325 hud-service restart_syscall 1 0.0231 2329 hud-service restart_syscall 1 0.0231 2340 hud-service restart_syscall 1 0.0231 Total 100 23125.2435 (gdb) where #0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from /usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2 #9 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() () #17 0x00441e43 in hud::service::WindowImpl::activate() () #18 0x00439f6a in hud::service::QueryImpl::updateToken(QSharedPointerhud::service::Window) () #19 0x0043a672 in hud::service::QueryImpl::refresh() () #20 0x0044b115 in ?? () #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x0045662a in hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const, unsigned int) () #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00467361 in ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, QString const, unsigned int) () #25 0x004678bd in ?? () #26 0x00467c63 in ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, void**) () #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #28 0x7fda8435e22e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7fda84335c2d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7fda84337e07 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7fda84382cd3 in ?? () from
[Dx-packages] [Bug 1300750] Re: indicator-bluetooth-service crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM()
*** This bug is a duplicate of bug 1278680 *** https://bugs.launchpad.net/bugs/1278680 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1278680, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1300750/+attachment/4058080/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1300750/+attachment/4058082/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1300750/+attachment/4058084/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1300750/+attachment/4058085/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1300750/+attachment/4058086/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1300750/+attachment/4058087/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1300750/+attachment/4058088/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1278680 ** Information type changed from Private to Public ** Tags removed: need-i386-retrace -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1300750 Title: indicator-bluetooth-service crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM() Status in “indicator-bluetooth” package in Ubuntu: New Bug description: Bluetooth not turn on after a wake system from suspend. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic i686 ApportVersion: 2.14-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Tue Apr 1 13:58:33 2014 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-bluetooth/indicator-bluetooth-service InstallationDate: Installed on 2014-02-26 (33 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140224) ProcCmdline: /usr/lib/i386-linux-gnu/indicator-bluetooth/indicator-bluetooth-service SegvAnalysis: Segfault happened at: 0x8054fd8: mov(%ebx),%eax PC (0x08054fd8) ok source (%ebx) (0x) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-bluetooth StacktraceTop: ?? () ?? () ?? () g_cclosure_marshal_VOID__PARAM () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: indicator-bluetooth-service crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1300750/+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 723167] Re: Fuzzy fonts caused by Cairo antialiasing artifacts with Radiance theme.
** Changed in: unity (Ubuntu) Status: Triaged = In Progress ** Changed in: unity (Ubuntu) Assignee: Stephen M. Webb (bregma) = 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/723167 Title: Fuzzy fonts caused by Cairo antialiasing artifacts with Radiance theme. Status in Ayatana Design: Invalid Status in Cairo Graphics Library: New Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Since the switch to a theme-aware panel, the Unity panel uses very fuzzy fonts. The actual submenus in the global menu bar, as well as the indicators look fine, but the top-level menu entries, time, name in me-menu, and the window title look fuzzy. Presumably this is because it doesn't use the configured Pango font anti-aliasing as the rest of GTK, as these are rendered by nux? This is Unity 3.4.4 on current Natty. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/723167/+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 1300722] Re: hud-service is eating up 100% of one of my CPUs in a pool loop
Hi Pete, how do I look that up? -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1300722 Title: hud-service is eating up 100% of one of my CPUs in a pool loop Status in “hud” package in Ubuntu: New Bug description: hud-service is polling like crazy: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 2295 hud-service 46084.6342.94 46127.58 (very high) 2325 hud-service 0.09 0.00 0.09 (very low) 2329 hud-service 0.07 0.00 0.07 (very low) 2340 hud-service 0.05 0.00 0.05 (very low) Total 46084.8442.94 46127.78 File I/O operations: No file I/O operations detected. System calls traced: PID Process Syscall CountRate/Sec 2295 hud-service poll 83 23124.8503 2295 hud-service write10 0.2313 2295 hud-service sendmsg 4 0.0925 2325 hud-service restart_syscall 1 0.0231 2329 hud-service restart_syscall 1 0.0231 2340 hud-service restart_syscall 1 0.0231 Total 100 23125.2435 (gdb) where #0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from /usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2 #9 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() () #17 0x00441e43 in hud::service::WindowImpl::activate() () #18 0x00439f6a in hud::service::QueryImpl::updateToken(QSharedPointerhud::service::Window) () #19 0x0043a672 in hud::service::QueryImpl::refresh() () #20 0x0044b115 in ?? () #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x0045662a in hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const, unsigned int) () #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00467361 in ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, QString const, unsigned int) () #25 0x004678bd in ?? () #26 0x00467c63 in ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, void**) () #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #28 0x7fda8435e22e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7fda84335c2d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7fda84337e07 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7fda84382cd3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7fda833dbe04 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
[Dx-packages] [Bug 1300722] Re: hud-service is eating up 100% of one of my CPUs in a pool loop
What I am seeing is the following poll:
poll([{fd=13, events=POLLIN}], 1, 18813) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 18813) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 18813) = 1 ([{fd=13, revents=POLLIN}])
write(3, \1\0\0\0\0\0\0\0, 8) = 8
write(3, \1\0\0\0\0\0\0\0, 8) = 8
write(2, \33[31mvoid DBusMenuImporter::slot..., 335) = 335
write(2, \33[31mbool DBusMenuImporterPrivat..., 300) = 300
write(2, \33[31mvoid DBusMenuImporter::slot..., 115) = 115
sendmsg(13, {msg_name(0)=NULL, msg_iov(2)=[{l\1\0\1
\0\0\0\354\243\2\0r\0\0\0\1\1o\0\33\0\0\0/com/can..., 136},
{n\3\0\0\6\0\0\0opened\0\1s\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0, 32}],
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 168
sendmsg(13, {msg_name(0)=NULL,
msg_iov(2)=[{l\1\0\1\4\0\0\0\355\243\2\0w\0\0\0\1\1o\0\33\0\0\0/com/can...,
136}, {\f\2\0\0, 4}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 140
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 24999) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 24999) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 24999) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 24999) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 24999) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 24999) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 24999) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 24999) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 24999) = 1 ([{fd=13, revents=POLLIN}])
.. and this repeats and the timeout drops from 25000 milliseconds down
to 1, which is a tad excessive. Polling a gazillion times with sub
millisecond timeout is a little bit antisocial ;-)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to hud in Ubuntu.
https://bugs.launchpad.net/bugs/1300722
Title:
hud-service is eating up 100% of one of my CPUs in a pool loop
Status in “hud” package in Ubuntu:
New
Bug description:
hud-service is polling like crazy:
Context Switches:
PID ProcessVoluntary Involuntary Total
Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec
2295 hud-service 46084.6342.94 46127.58 (very high)
2325 hud-service 0.09 0.00 0.09 (very low)
2329 hud-service 0.07 0.00 0.07 (very low)
2340 hud-service 0.05 0.00 0.05 (very low)
Total 46084.8442.94 46127.78
File I/O operations:
No file I/O operations detected.
System calls traced:
PID Process Syscall CountRate/Sec
2295 hud-service poll 83 23124.8503
2295 hud-service write10 0.2313
2295 hud-service sendmsg 4 0.0925
2325 hud-service restart_syscall 1 0.0231
2329 hud-service restart_syscall 1 0.0231
2340 hud-service restart_syscall 1 0.0231
Total 100 23125.2435
(gdb) where
#0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81
#1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from
/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#8 0x7fda83eb940b in
[Dx-packages] [Bug 561540] Re: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0
Problem is gone with Trusty i386 too. -- 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/561540 Title: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 Status in The synaptic package manager: New Status in “gdm” package in Ubuntu: Confirmed Status in “unity-2d” package in Ubuntu: Confirmed Bug description: Binary package hint: gdm Specification Gnome 2.26.1 Distributor ID: Ubuntu Description: Ubuntu 9.04 Release: 9.04 Codename: jaunty gdm: Installed: 2.20.10-0ubuntu2 Candidate: 2.20.10-0ubuntu2 Version table: *** 2.20.10-0ubuntu2 0 500 http://no.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status This bug leads to random GDM freezes. The freeze occurs when I start a new application through Gnome's application launcher. It is possible that this bug affects 9.10 as well. I assume but do not really know that it is caused by the gdm package. The .xsession-errors file looks like this, I guess only the last few lines are relevant. /etc/gdm/Xsession: Beginning session setup... Setting IM through im-switch for locale=en_US. Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default. /usr/bin/xmodmap: unable to open file '/usr/share/apps/kxkb/ubuntu.xmodmap' for reading /usr/bin/xmodmap: 1 error encountered, aborting. I: caps.c: Limited capabilities successfully to CAP_SYS_NICE. I: caps.c: Dropping root privileges. I: caps.c: Limited capabilities successfully to CAP_SYS_NICE. N: main.c: Called SUID root and real-time and/or high-priority scheduling was requested in the configuration. However, we lack the necessary privileges: N: main.c: We are not in group 'pulse-rt', PolicyKit refuse to grant us the requested privileges and we have no increase RLIMIT_NICE/RLIMIT_RTPRIO resource limits. N: main.c: For enabling real-time/high-priority scheduling please acquire the appropriate PolicyKit privileges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user. x-session-manager[24868]: EggSMClient-WARNING: Desktop file '/home/halbach/.config/gnome-session/saved-session/108f0182279bf1285c12683177068619280043600043.desktop' has malformed Icon key 'skype.png'(should not include extension) (gnome-settings-daemon:24971): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (gnome-settings-daemon:24971): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed GNOME_KEYRING_SOCKET=/tmp/keyring-D8NWqg/socket SSH_AUTH_SOCK=/tmp/keyring-D8NWqg/socket.ssh x-session-manager[24868]: atk-bridge-WARNING: AT_SPI_REGISTRY was not started at session startup. x-session-manager[24868]: atk-bridge-WARNING: IOR not set. x-session-manager[24868]: atk-bridge-WARNING: Could not locate registry (at-spi-registryd-wrapper:24967): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup. (at-spi-registryd-wrapper:24967): atk-bridge-WARNING **: IOR not set. (at-spi-registryd-wrapper:24967): atk-bridge-WARNING **: Could not locate registry (gnome-settings-daemon:24971): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup. (gnome-settings-daemon:24971): atk-bridge-WARNING **: IOR not set. (gnome-settings-daemon:24971): atk-bridge-WARNING **: Could not locate registry Window manager warning: found in configuration database is not a valid value for keybinding switch_panels Window manager warning: found in configuration database is not a valid value for keybinding cycle_group Window manager warning: found in configuration database is not a valid value for keybinding cycle_windows Window manager warning: found in configuration database is not a valid value for keybinding cycle_panels Window manager warning: found in configuration database is not a valid value for keybinding show_desktop Window manager warning: found in configuration database is not a valid value for keybinding move_to_workspace_left Window manager warning: found in configuration database is not a valid value for keybinding move_to_workspace_right Window manager warning: found in configuration database is not a valid value for keybinding move_to_workspace_up Window manager warning: found in configuration database is not a valid value for keybinding move_to_workspace_down ** (gnome-panel:24988): DEBUG: Adding applet 0. ** (gnome-panel:24988): DEBUG: Initialized Panel Applet Signaler. Failure: Module initalization failed ** (gnome-panel:24988): DEBUG: Adding applet 1. ** (gnome-panel:24988): DEBUG: Adding applet 2. ** (gnome-panel:24988): DEBUG: Adding applet 3. Unable to open desktop file file:///usr/share/applications/mozilla-thunderbird.desktop for panel launcher: No such file or
[Dx-packages] [Bug 1292451] Re: screensaver re-locks itself after unlocking if the configured screen-off timer goes off while screen is locked
Nevermind, only if you issue the lock-screen but if it is automatic... same problem. -- 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/1292451 Title: screensaver re-locks itself after unlocking if the configured screen- off timer goes off while screen is locked Status in Unity: New Status in “gnome-screensaver” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Set screen-off timeout to 1 minute 2. Configure screen to lock immediately when screen goes off. 3. Lock screen manually (Ctrl+Alt+L) 4. Wait for 1 minute 5. Notice that screen doesn't turn off 6. Unlock screen 7. Wait a couple of seconds (~10 or so) 8. Notice that screen re-locks itself. 9. Repeat steps 6-7 and notice that the screen doesn't re-lock itself this time. There are two bugs described here: 1. Screen does not shut off if the screen is locked manually before the idle timer (see step 5). 2. Screen re-locks itself after unlocking if the idle timer goes off while the screen is locked (see step 7). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 14 18:19:26 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-03-03 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292451/+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 1281297] Re: Scale/Spread Search does not use applications name
** Branch linked: lp:~3v1n0/unity/spread-filter-improvements -- 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/1281297 Title: Scale/Spread Search does not use applications name Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: To reproduce: 1) Open 2 gnome-terminal 2) Super+W (to go into scale mode) 3) type terminal Expected: The 2 gnome-terminals to be left as valid matches. Result: Empty search results on the gnome-terminals. Also, based on a duplicate: I propose that not only are the windows in spread filtered by title, but also by - application name, e.g. gnome terminal - generic name, e.g. web browser - application category, e.g. multimedia To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1281297/+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 1281297] Re: Scale/Spread Search does not use applications name
** Changed in: unity (Ubuntu) Status: Triaged = In Progress ** Changed in: unity 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/1281297 Title: Scale/Spread Search does not use applications name Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: To reproduce: 1) Open 2 gnome-terminal 2) Super+W (to go into scale mode) 3) type terminal Expected: The 2 gnome-terminals to be left as valid matches. Result: Empty search results on the gnome-terminals. Also, based on a duplicate: I propose that not only are the windows in spread filtered by title, but also by - application name, e.g. gnome terminal - generic name, e.g. web browser - application category, e.g. multimedia To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1281297/+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 1165420] Re: Unable to access indicators from HUD
This is surprising to me too, I'll ask around for the rationale. Mark -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1165420 Title: Unable to access indicators from HUD Status in Ayatana Design: Confirmed Status in Unity HUD: Confirmed Status in “hud” package in Ubuntu: Confirmed Bug description: In Ubuntu 12.10 I was able to use HUD to access Messaging menu and Gwibber's Update Status option there, making status updates to Twitter easy and fast. I could also use HUD to change my status in Empathy from Available to Busy and vice-versa. In Ubuntu 13.04 Beta HUD no longer finds the Update Status option when typing Update Status or Update Also writing Available Away or Busy no longer gives any results. Other indicators however are accessible and I can use HUD to Suspend my computer or to view Skype status or Ubuntu one indicator options. Repeating: 1. Press alt key to start HUD 2. Write Update status or Available What was expected: HUD should have shown options ether from Gwibber to Update Status or Empathy to change status to Available both available from the messaging indicator. What happened: HUD didn't find any results. Notes: I have Ubuntu 13.04 Beta 64bit upgraded from Ubuntu 12.10 64bits and I'm using proprietary fglrx drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1165420/+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 1299080] Re: [UIFe] New style force-quit window dialog
** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: New = In Progress ** Changed in: unity Status: Confirmed = 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/1299080 Title: [UIFe] New style force-quit window dialog Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: In order to fix the regression lp:1299061 we want to introduce a new styled dialog (as designed lp:698031) inside unity (it used to be in compiz gtk-window-decorator before). Unfortunately this introduces two new strings: - This window is not responding - Do you want to force the application to exit, or wait for it to respond? Result: http://people.ubuntu.com/~3v1n0/shots/force-quit-dialog- new.png Translators ML: https://lists.ubuntu.com/archives/ubuntu-translators/2014-March/006439.html Docs ML: in moderation queue... To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1299080/+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 1300864] Re: Duplicate webapps launcher confuses bamf
** Also affects: unity-webapps-qml Importance: Undecided Status: New ** Changed in: unity-webapps-qml Assignee: (unassigned) = Alexandre Abreu (abreu-alexandre) ** Branch linked: lp:~abreu-alexandre/unity-webapps-qml/broken-desktop- file-gen ** Changed in: unity-webapps-qml Importance: Undecided = High -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1300864 Title: Duplicate webapps launcher confuses bamf Status in BAMF Application Matching Framework: New Status in WebApps: libunity: Fix Committed Status in Unity WebApps QML component: New Status in “libunity-webapps” package in Ubuntu: In Progress Bug description: Even with the recent fixes to bamf, I can still be in cases where my webapp launcher does not associate correctly on the launcher. It happens for no particular webapp. However it stops occuring as soon as I suppress the duplicate desktop file we generate in ~/.local/share/applications. To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1300864/+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 1300864] [NEW] Duplicate webapps launcher confuses bamf
Public bug reported: Even with the recent fixes to bamf, I can still be in cases where my webapp launcher does not associate correctly on the launcher. It happens for no particular webapp. However it stops occuring as soon as I suppress the duplicate desktop file we generate in ~/.local/share/applications. ** Affects: bamf Importance: Undecided Status: New ** Affects: libunity-webapps Importance: High Assignee: Alexandre Abreu (abreu-alexandre) Status: Fix Committed ** Affects: unity-webapps-qml Importance: High Assignee: Alexandre Abreu (abreu-alexandre) Status: New ** Affects: libunity-webapps (Ubuntu) Importance: High Assignee: Alexandre Abreu (abreu-alexandre) Status: In Progress ** Summary changed: - Duplicate webapps launcher confuse bamf + Duplicate webapps launcher confuses bamf ** Changed in: libunity-webapps Status: New = Fix Committed ** Changed in: libunity-webapps Importance: Undecided = High ** Changed in: libunity-webapps Assignee: (unassigned) = Alexandre Abreu (abreu-alexandre) ** Also affects: bamf Importance: Undecided Status: New ** Also affects: libunity-webapps (Ubuntu) Importance: Undecided Status: New ** Changed in: libunity-webapps (Ubuntu) Status: New = In Progress ** Changed in: libunity-webapps (Ubuntu) Importance: Undecided = High ** Changed in: libunity-webapps (Ubuntu) Assignee: (unassigned) = Alexandre Abreu (abreu-alexandre) ** Changed in: libunity-webapps (Ubuntu) Milestone: None = ubuntu-14.04 -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1300864 Title: Duplicate webapps launcher confuses bamf Status in BAMF Application Matching Framework: New Status in WebApps: libunity: Fix Committed Status in Unity WebApps QML component: New Status in “libunity-webapps” package in Ubuntu: In Progress Bug description: Even with the recent fixes to bamf, I can still be in cases where my webapp launcher does not associate correctly on the launcher. It happens for no particular webapp. However it stops occuring as soon as I suppress the duplicate desktop file we generate in ~/.local/share/applications. To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1300864/+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 1300915] [NEW] bluetooth pairing does not require a pin
Public bug reported: click on bluetooth desktop applet, turn on visible on nexus 4 go to settings bluetooth click on ubuntu-0 under available devices pairing succeeds without asking for a pin or authentication from Ubuntu! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 1 18:41:07 2014 InstallationDate: Installed on 2014-03-27 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: indicator-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-bluetooth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1300915 Title: bluetooth pairing does not require a pin Status in “indicator-bluetooth” package in Ubuntu: New Bug description: click on bluetooth desktop applet, turn on visible on nexus 4 go to settings bluetooth click on ubuntu-0 under available devices pairing succeeds without asking for a pin or authentication from Ubuntu! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 1 18:41:07 2014 InstallationDate: Installed on 2014-03-27 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: indicator-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1300915/+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 1300926] [NEW] does not respond to pairing request / incompatible with Bluetooth file transfer Android app
Public bug reported: https://play.google.com/store/apps/details?id=it.medieval.blueftp get bluetooth file transfer from Google Play run it click on Bluetooth icon click on ubuntu-0 pairing - phone loops asking user to enter pin number but unity never shows a request for pairing ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 1 18:56:01 2014 InstallationDate: Installed on 2014-03-27 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: indicator-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-bluetooth (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 indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1300926 Title: does not respond to pairing request / incompatible with Bluetooth file transfer Android app Status in “indicator-bluetooth” package in Ubuntu: New Bug description: https://play.google.com/store/apps/details?id=it.medieval.blueftp get bluetooth file transfer from Google Play run it click on Bluetooth icon click on ubuntu-0 pairing - phone loops asking user to enter pin number but unity never shows a request for pairing ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 1 18:56:01 2014 InstallationDate: Installed on 2014-03-27 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: indicator-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1300926/+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 1148033] Re: GDBus.Error:org.openobex:Error.Failed: Unable to request session
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1148033 ** Tags added: iso-testing -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1148033 Title: GDBus.Error:org.openobex:Error.Failed: Unable to request session Status in Bluetooth Menu: New Status in “gnome-bluetooth” package in Ubuntu: In Progress Status in “indicator-bluetooth” package in Ubuntu: Triaged Bug description: I'm using 13.04 and i can't send file from my netbook to my phone via bluetooth. Worked on 12.10 (I use Lenovo 3000 N200) after installing Blueman Bluetooth Manager problem solved. Also affects 13.10! To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1148033/+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 1300931] [NEW] desktop HUD Help entries do nothing unless files window is already open
Public bug reported: close all open application windows. tap alt, type help and select any HUD result eg find a lost file (Help) Nothing happens Click on files in the launcher tap alt, type help and select any result eg find a lost file (Help) Now it works. 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 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 19:15:21 2014 InstallationDate: Installed on 2014-03-27 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) 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/1300931 Title: desktop HUD Help entries do nothing unless files window is already open Status in “unity” package in Ubuntu: New Bug description: close all open application windows. tap alt, type help and select any HUD result eg find a lost file (Help) Nothing happens Click on files in the launcher tap alt, type help and select any result eg find a lost file (Help) Now it works. 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 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 19:15:21 2014 InstallationDate: Installed on 2014-03-27 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (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/1300931/+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 1300931] Re: desktop HUD Help entries do nothing unless files window is already open
Also see bug #1300936 -- 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/1300931 Title: desktop HUD Help entries do nothing unless files window is already open Status in “unity” package in Ubuntu: New Bug description: close all open application windows. tap alt, type help and select any HUD result eg find a lost file (Help) Nothing happens Click on files in the launcher tap alt, type help and select any result eg find a lost file (Help) Now it works. 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 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 19:15:21 2014 InstallationDate: Installed on 2014-03-27 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (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/1300931/+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 1300926] Re: does not respond to pairing request / incompatible with Bluetooth file transfer Android app
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1300926 ** Tags added: iso-testing -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1300926 Title: does not respond to pairing request / incompatible with Bluetooth file transfer Android app Status in “indicator-bluetooth” package in Ubuntu: New Bug description: https://play.google.com/store/apps/details?id=it.medieval.blueftp get bluetooth file transfer from Google Play run it click on Bluetooth icon click on ubuntu-0 pairing - phone loops asking user to enter pin number but unity never shows a request for pairing ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 1 18:56:01 2014 InstallationDate: Installed on 2014-03-27 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: indicator-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1300926/+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 1300936] [NEW] weird results from HUD
Public bug reported: close all open application windows. tap alt. type enter =there are no results. There should be results. Why does enter have no results but ente or enter do have results? hit spacebar select Enter Location... (Go) Nothing happens - it should have opened theLocation window ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: hud 13.10.1+14.04.20140326-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 1 19:22:55 2014 InstallationDate: Installed on 2014-03-27 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: hud UpgradeStatus: No upgrade log present (probably fresh install) upstart.hud.log: hud-service: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. hud-service: Fatal IO error 0 (Success) on X server :0. upstart.window-stack-bridge.log: QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was ':1.5' QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was ':1.10' ** Affects: hud (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 hud in Ubuntu. https://bugs.launchpad.net/bugs/1300936 Title: weird results from HUD Status in “hud” package in Ubuntu: New Bug description: close all open application windows. tap alt. type enter =there are no results. There should be results. Why does enter have no results but ente or enter do have results? hit spacebar select Enter Location... (Go) Nothing happens - it should have opened theLocation window ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: hud 13.10.1+14.04.20140326-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 1 19:22:55 2014 InstallationDate: Installed on 2014-03-27 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: hud UpgradeStatus: No upgrade log present (probably fresh install) upstart.hud.log: hud-service: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. hud-service: Fatal IO error 0 (Success) on X server :0. upstart.window-stack-bridge.log: QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was ':1.5' QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was ':1.10' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1300936/+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 1300931] Re: desktop HUD Help entries do nothing unless files window is already open
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1300931 ** Tags added: iso-testing -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1300931 Title: desktop HUD Help entries do nothing unless files window is already open Status in “unity” package in Ubuntu: New Bug description: close all open application windows. tap alt, type help and select any HUD result eg find a lost file (Help) Nothing happens Click on files in the launcher tap alt, type help and select any result eg find a lost file (Help) Now it works. 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 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 19:15:21 2014 InstallationDate: Installed on 2014-03-27 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (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/1300931/+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 1300915] Re: bluetooth pairing does not require a pin
Nexus 4 is running official unmodified Android 4.4.2. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1300915 Title: bluetooth pairing does not require a pin Status in “indicator-bluetooth” package in Ubuntu: New Bug description: click on bluetooth desktop applet, turn on visible on nexus 4 go to settings bluetooth click on ubuntu-0 under available devices pairing succeeds without asking for a pin or authentication from Ubuntu! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 1 18:41:07 2014 InstallationDate: Installed on 2014-03-27 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: indicator-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1300915/+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 1300936] Re: weird results from HUD
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1300936 ** Tags added: iso-testing -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1300936 Title: weird results from HUD Status in “hud” package in Ubuntu: New Bug description: close all open application windows. tap alt. type enter =there are no results. There should be results. Why does enter have no results but ente or enter do have results? hit spacebar select Enter Location... (Go) Nothing happens - it should have opened theLocation window ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: hud 13.10.1+14.04.20140326-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 1 19:22:55 2014 InstallationDate: Installed on 2014-03-27 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: hud UpgradeStatus: No upgrade log present (probably fresh install) upstart.hud.log: hud-service: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. hud-service: Fatal IO error 0 (Success) on X server :0. upstart.window-stack-bridge.log: QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was ':1.5' QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was ':1.10' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1300936/+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 1300936] Re: weird results from HUD
Also see bug #1300931 -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1300936 Title: weird results from HUD Status in “hud” package in Ubuntu: New Bug description: close all open application windows. tap alt. type enter =there are no results. There should be results. Why does enter have no results but ente or enter do have results? hit spacebar select Enter Location... (Go) Nothing happens - it should have opened theLocation window ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: hud 13.10.1+14.04.20140326-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 1 19:22:55 2014 InstallationDate: Installed on 2014-03-27 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: hud UpgradeStatus: No upgrade log present (probably fresh install) upstart.hud.log: hud-service: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. hud-service: Fatal IO error 0 (Success) on X server :0. upstart.window-stack-bridge.log: QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was ':1.5' QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was ':1.10' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1300936/+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 1290171] Re: appointments don't change when you click on a calendar date
uh oh, looks like I'm experiencing the same issues. Can't confirm the absence of today's events (have no events scheduled today) but it is missing colors for me. -- 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/1290171 Title: appointments don't change when you click on a calendar date Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: In the desktop's Coming Events section, we should update the event/alarm entries based on the date clicked on in the Monthly Calendar section. In indicator-datetime-13.10.0+14.04.20140227.1-0ubuntu1, the events are tied to the current clock time and do not change when you click on another date in the calendar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1290171/+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 1300946] [NEW] unity power settings ignored
Public bug reported: start the trusty installer desktop go to settings power note that Suspend when inactive for is set to Don't suspend (default) Wait 5m15s Laptop suspends 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 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 19:45:16 2014 InstallationDate: Installed on 2014-03-27 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) 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/1300946 Title: unity power settings ignored Status in “unity” package in Ubuntu: New Bug description: start the trusty installer desktop go to settings power note that Suspend when inactive for is set to Don't suspend (default) Wait 5m15s Laptop suspends 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 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 19:45:16 2014 InstallationDate: Installed on 2014-03-27 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (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/1300946/+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 1300946] Re: unity power settings ignored
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1300946 ** Tags added: iso-testing -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1300946 Title: unity power settings ignored Status in “unity” package in Ubuntu: New Bug description: start the trusty installer desktop go to settings power note that Suspend when inactive for is set to Don't suspend (default) Wait 5m15s Laptop suspends 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 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 19:45:16 2014 InstallationDate: Installed on 2014-03-27 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (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/1300946/+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 1165420] Re: Unable to access indicators from HUD
@Rüdiger: I am actually using the HUD quite often as a fast and easy means to access menus, especially in apps where I do a lot of typing, like LibreOfffice, Firefox, Gedit etc... But I used to use it a lot also as a fast and easy means to access the indicators, and I do miss that feat. :-/ -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1165420 Title: Unable to access indicators from HUD Status in Ayatana Design: Confirmed Status in Unity HUD: Confirmed Status in “hud” package in Ubuntu: Confirmed Bug description: In Ubuntu 12.10 I was able to use HUD to access Messaging menu and Gwibber's Update Status option there, making status updates to Twitter easy and fast. I could also use HUD to change my status in Empathy from Available to Busy and vice-versa. In Ubuntu 13.04 Beta HUD no longer finds the Update Status option when typing Update Status or Update Also writing Available Away or Busy no longer gives any results. Other indicators however are accessible and I can use HUD to Suspend my computer or to view Skype status or Ubuntu one indicator options. Repeating: 1. Press alt key to start HUD 2. Write Update status or Available What was expected: HUD should have shown options ether from Gwibber to Update Status or Empathy to change status to Available both available from the messaging indicator. What happened: HUD didn't find any results. Notes: I have Ubuntu 13.04 Beta 64bit upgraded from Ubuntu 12.10 64bits and I'm using proprietary fglrx drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1165420/+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 1291737] Re: New lockscreen doesn't indicate when capslock is on
** Branch linked: lp:~brandontschaefer/unity/lockscreen-caps-lock- detector -- 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/1291737 Title: New lockscreen doesn't indicate when capslock is on Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: The Unity greeter shows a warning sign in the password field when capslock is on. The old lockscreen does the same. The new lockscreen should also indicate when capslock is on. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140311-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu Mar 13 03:24:59 2014 InstallationDate: Installed on 2014-02-24 (16 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140223) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291737/+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 1292041] Re: Lockscreen doesn't turn off the screen
** Project changed: unity-greeter = unity-greeter (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/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in Unity: Invalid Status in “gnome-screensaver” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Invalid Status in “unity-greeter” package in Ubuntu: New Bug description: The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't trun off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+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 1292041] Re: Lockscreen doesn't turn off the screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity-greeter (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/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in Unity: Invalid Status in “gnome-screensaver” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Invalid Status in “unity-greeter” package in Ubuntu: New Bug description: The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't trun off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+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 1291362] Re: Apps locked to launcher only launch once per session.
OK, I think I found out what this is about. Can reliably repeat it now. It's about having multiple monitors. I have three. This problem occurs if I set the launcher placement to be anything other than All Displays or the leftmost display. (Confirmed by swapping displays around in the display prefs; whichever one is spacially positioned leftmost is fine; if the launcher is on (and only on) any other display, this issue occurs.) But I want my launcher in the middle! :-) Situation here is that the middle display is a 27 2560x1440, and the two on either side are 24 1920x1080. Having just one launcher on that big middle screen, and pushing new windows from there to the outer displays at need, works well for me, and of course ought to be a supported choice, as the UI lets me do it. ;-) Of course what I really really really want is the launcher on auto-hide along the bottom of every display, but that's not going to happen. :-( Hey, is anyone actually seeing this? I haven't even had a bot come by and ask for more information... -- 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/1291362 Title: Apps locked to launcher only launch once per session. Status in “unity” package in Ubuntu: New Bug description: In Trusty: An application that has been locked to launcher, (including those there by default) can only be clicked on once per session to actually launch the application. After that it's unresponsive to clicks, although right-click actions work. Seems to affect all apps, including Files. To repeat, for any application not already on the launcher bar: Launch the application using the dash. Right-click on its launcher icon and select Lock to Launcher Quit the application. Click on its launcher icon. It should launch again. Quit it again. Click on its launcher icon again. It won't work this time. It looks like dragging would work, but its operation as a launcher will not. NB: I haven't installed any hacks eg: click-to-minimise. Seen this on two systems upgraded from saucy to trusty. (One with AMD graphics, one with Intel, so I doubt that's relevant either.) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140311-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Mar 12 13:10:56 2014 InstallationDate: Installed on 2014-03-08 (3 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-10 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1291362/+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 1300989] Re: compiz crashed with SIGSEGV in FT_Load_Glyph()
*** This bug is a duplicate of bug 1199571 *** https://bugs.launchpad.net/bugs/1199571 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1199571, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1300989/+attachment/4059134/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1300989/+attachment/4059136/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1300989/+attachment/4059137/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1300989/+attachment/4059138/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1300989/+attachment/4059139/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1300989/+attachment/4059140/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1300989/+attachment/4059141/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1199571 compiz crashed with SIGSEGV in af_latin_hints_compute_edges() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1300989 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() Status in “unity” package in Ubuntu: New Bug description: On one of the first reboots following upgrade to 14.04 beta. ProblemType: Crash 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 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 1 15:19:24 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2012-05-18 (682 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f9879a0593c:testb $0x1,(%rax) PC (0x7f9879a0593c) ok source $0x1 ok destination (%rax) (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() UpgradeStatus: Upgraded to trusty on 2014-04-01 (0 days ago) UserGroups: adm cdrom dip fuse kvm libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1300989/+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 1295413] Re: new unity lock screen doesn't appear after resume
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/1295413 Title: new unity lock screen doesn't appear after resume Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: New lock screen is awesome. Unfortunately, for me, whenever I resume, I get a blank screen. I can switch VTs but switching to a text VT and back to X doesn't help. If I unplug and/or re-plug my external display, I'll sometimes get a black screen with a mouse, sometimes a lock screen that doesn't appear to be accepting keyboard input. This has happened twice now, running current trusty and I've ended up rebooting each time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140318-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 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] CurrentDesktop: Unity Date: Thu Mar 20 23:26:52 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-20 (882 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-19 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1295413/+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 1292695] Re: Lock screen isn't cat-friendly (no input timemout)
Wait. Is unity 7.2 targetted for trusty, or did this milestone target basically just say leaving screens on all night is an acceptable behaviour for an LTS? -- 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/1292695 Title: Lock screen isn't cat-friendly (no input timemout) Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: gnome-screensaver's lock screen has an input timeout, so that if you, say, lock your screen and have a cat walk across your keyboard in the middle of the night, after N seconds (don't recall how long it is) of no input, it gives up and blanks the screen again. The new unity lock screen appears to be missing this feature, as I woke up this morning to a password box filled with dots and a screen that had been on all night. It looks like maybe there had been a failed attempt to address this use-case, as once one clears the password field and logs in, a second or two later, the screen re-locks and you need to log in again. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292695/+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 1295413] Re: new unity lock screen doesn't appear after resume
I have more or less the same problem, and create a new bug few days ago.. But in my case, I use a AMD GPU https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1298650 -- 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/1295413 Title: new unity lock screen doesn't appear after resume Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: New lock screen is awesome. Unfortunately, for me, whenever I resume, I get a blank screen. I can switch VTs but switching to a text VT and back to X doesn't help. If I unplug and/or re-plug my external display, I'll sometimes get a black screen with a mouse, sometimes a lock screen that doesn't appear to be accepting keyboard input. This has happened twice now, running current trusty and I've ended up rebooting each time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140318-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 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] CurrentDesktop: Unity Date: Thu Mar 20 23:26:52 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-20 (882 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-19 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1295413/+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 1073114] Online Smart Scopes Do Not Respect User Privacy
I do not agree, this bug has not been solved and should remain open.. as titled the “bug” is “online smart scopes do not respect user privacy” and from what i can tell; the new setup still does not respect user privacy.. keystrokes typed in search are still sent to canonical services (correct me if i’m wrong). and the scopes scope is still opt-out.. and does not appear to address the EFF’s concerns at all.. Mike Davis IOA On Mar 31, 2014, at 9:34 PM, Benjamin Kerensa 1073...@bugs.launchpad.net wrote: @mlaverdiere: I agree this announcement addresses any privacy concerns users should have do we have a likely milestone to attach it to and is it worth marking Fix Committed? ** Changed in: libunity (Ubuntu Quantal) Status: Confirmed = Won't Fix ** Changed in: libunity (Ubuntu Raring) Status: Confirmed = Won't Fix ** Changed in: unity-lens-shopping (Ubuntu Quantal) Status: Confirmed = Won't Fix ** Changed in: unity-lens-shopping (Ubuntu Raring) Status: Confirmed = Won't Fix ** Changed in: unity-lens-shopping (Ubuntu) Milestone: None = later ** Changed in: libunity (Ubuntu) Milestone: None = later ** Changed in: unity-lens-shopping (Ubuntu) Status: Confirmed = In Progress ** Changed in: libunity (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are subscribed to a duplicate bug report (1074780). https://bugs.launchpad.net/bugs/1073114 Title: Online Smart Scopes Do Not Respect User Privacy Status in “libunity” package in Ubuntu: In Progress Status in “unity-lens-shopping” package in Ubuntu: In Progress Status in “libunity” source package in Quantal: Won't Fix Status in “unity-lens-shopping” source package in Quantal: Won't Fix Status in “libunity” source package in Raring: Won't Fix Status in “unity-lens-shopping” source package in Raring: Won't Fix Bug description: See this from the Electronic Frontier Foundation (EFF), a well respected international non-profit digital rights advocacy and legal organization (as described on Wikipedia): https://www.eff.org/deeplinks/2012/10/privacy-ubuntu-1210-amazon-ads- and-data-leaks Obviously, despite some improvements that have came late in the 12.10 development cycle, there are still serious privacy concerns with the unity shopping lens. To be more precise, here are the main problems to be fixed according to EFF: - Disable Include online search results by default. - Explain in detail what Canonical does with search queries and IP addresses, how long it stores them, and in what circumstances it gives them to third parties. - Make the Search Results tab of the Privacy settings let users toggle on and off specific online search results, as some users might want Amazon products in their search results, but never anything from Facebook. Here is another related bug: #1055952 Direct data leaking to Amazon: https://bugs.launchpad.net/ubuntu/+source/unity-lens- shopping/+bug/1055952 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity-lens-shopping 6.8.0-0ubuntu1 Uname: Linux 3.5.6-030506-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Tue Oct 30 06:35:38 2012 InstallationDate: Installed on 2012-02-12 (260 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True SourcePackage: unity-lens-shopping UpgradeStatus: Upgraded to quantal on 2012-09-28 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1073114/+subscriptions -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1073114 Title: Online Smart Scopes Do Not Respect User Privacy Status in “libunity” package in Ubuntu: In Progress Status in “unity-lens-shopping” package in Ubuntu: In Progress Status in “libunity” source package in Quantal: Won't Fix Status in “unity-lens-shopping” source package in Quantal: Won't Fix Status in “libunity” source package in Raring: Won't Fix Status in “unity-lens-shopping” source package in Raring: Won't Fix Bug description: See this from the Electronic Frontier Foundation (EFF), a well respected international non-profit digital rights advocacy and legal organization (as described on Wikipedia): https://www.eff.org/deeplinks/2012/10/privacy-ubuntu-1210-amazon-ads- and-data-leaks Obviously, despite some improvements that have came late in the 12.10 development cycle, there are still serious privacy concerns with the unity shopping lens. To be more precise, here are the main problems to be fixed according to EFF: - Disable Include online search results by default. - Explain in detail what Canonical does with
[Dx-packages] [Bug 774714] Re: glxew.h does not compile
Ubuntu 14.04 LTS has 1.10.0 ** Changed in: glew (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to glew in Ubuntu. https://bugs.launchpad.net/bugs/774714 Title: glxew.h does not compile Status in “glew” package in Ubuntu: Fix Released Bug description: /usr/include/GL/glxew.h:1182:49: error: expected ‘)’ before ‘*’ token. 'uint' should be 'GLuint' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glew/+bug/774714/+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 1301028] Re: indicator-bluetooth-service crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM()
*** This bug is a duplicate of bug 1278680 *** https://bugs.launchpad.net/bugs/1278680 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1278680, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1301028/+attachment/4059373/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1301028/+attachment/4059375/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1301028/+attachment/4059376/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1301028/+attachment/4059377/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1301028/+attachment/4059378/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1301028/+attachment/4059379/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1301028/+attachment/4059380/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1278680 ** Information type changed from Private to Public ** Tags removed: need-i386-retrace -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1301028 Title: indicator-bluetooth-service crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM() Status in “indicator-bluetooth” package in Ubuntu: New Bug description: Bluetooth out when manual start. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic i686 ApportVersion: 2.14-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Tue Apr 1 23:28:22 2014 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-bluetooth/indicator-bluetooth-service InstallationDate: Installed on 2014-03-10 (22 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140223) ProcCmdline: /usr/lib/i386-linux-gnu/indicator-bluetooth/indicator-bluetooth-service ProcEnviron: PATH=(custom, no user) LANGUAGE=ca XDG_RUNTIME_DIR=set LANG=ca_ES.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x8054fd8: mov(%ebx),%eax PC (0x08054fd8) ok source (%ebx) (0x) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-bluetooth StacktraceTop: ?? () ?? () ?? () g_cclosure_marshal_VOID__PARAM () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: indicator-bluetooth-service crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo upstart.indicator-bluetooth.log: ** (process:12706): CRITICAL **: bluez.vala:104: GDBus.Error:org.bluez.Error.NoSuchAdapter: No such adapter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1301028/+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 1260884] Re: Please update glew to 1.10.0
glew 1.10.0 is in trusty ** Changed in: glew (Ubuntu) Status: Fix Committed = Fix Released -- 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/1260884 Title: Please update glew to 1.10.0 Status in “glew” package in Ubuntu: Fix Released Status in “nux” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: The current version of glew in ubuntu is outdated and blocking other updates. Can someone please update to 1.10, which might break other packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glew/+bug/1260884/+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 1301033] [NEW] glew fails to build from source on armhf
Public bug reported: trying to build openimageio on armhf, ignoring the b-d on opencolorio, you get a build failure: In file included from /usr/include/qt4/QtOpenGL/QGLWidget:1:0, from /home/doko/tmp/openimageio-1.3.12~dfsg0/src/iv/ivgl.h:52, from /home/doko/tmp/openimageio-1.3.12~dfsg0/src/iv/imageviewer.cpp:32: /usr/include/qt4/QtOpenGL/qgl.h:85:17: error: conflicting declaration 'typedef GLfloat GLdouble' typedef GLfloat GLdouble; ^ In file included from /home/doko/tmp/openimageio-1.3.12~dfsg0/src/iv/imageviewer.h:50:0, from /home/doko/tmp/openimageio-1.3.12~dfsg0/src/iv/imageviewer.cpp:31: /usr/include/GL/glew.h:283:16: error: 'GLdouble' has a previous declaration as 'typedef double GLdouble' typedef double GLdouble; ^ make[4]: *** [src/iv/CMakeFiles/iv.dir/imageviewer.cpp.o] Error 1 make[4]: Leaving directory `/home/doko/tmp/openimageio-1.3.12~dfsg0/build' how ready is openimageio for OpenGLES? ** Affects: glew (Ubuntu) Importance: High Status: Confirmed ** Affects: glew (Ubuntu Trusty) Importance: High Status: Confirmed ** Tags: ftbfs ** Also affects: glew (Ubuntu Trusty) Importance: High Status: Confirmed ** Changed in: glew (Ubuntu Trusty) Milestone: None = ubuntu-14.04-beta-2 -- You received this bug notification because you are a member of DX Packages, which is subscribed to glew in Ubuntu. https://bugs.launchpad.net/bugs/1301033 Title: glew fails to build from source on armhf Status in “glew” package in Ubuntu: Confirmed Status in “glew” source package in Trusty: Confirmed Bug description: trying to build openimageio on armhf, ignoring the b-d on opencolorio, you get a build failure: In file included from /usr/include/qt4/QtOpenGL/QGLWidget:1:0, from /home/doko/tmp/openimageio-1.3.12~dfsg0/src/iv/ivgl.h:52, from /home/doko/tmp/openimageio-1.3.12~dfsg0/src/iv/imageviewer.cpp:32: /usr/include/qt4/QtOpenGL/qgl.h:85:17: error: conflicting declaration 'typedef GLfloat GLdouble' typedef GLfloat GLdouble; ^ In file included from /home/doko/tmp/openimageio-1.3.12~dfsg0/src/iv/imageviewer.h:50:0, from /home/doko/tmp/openimageio-1.3.12~dfsg0/src/iv/imageviewer.cpp:31: /usr/include/GL/glew.h:283:16: error: 'GLdouble' has a previous declaration as 'typedef double GLdouble' typedef double GLdouble; ^ make[4]: *** [src/iv/CMakeFiles/iv.dir/imageviewer.cpp.o] Error 1 make[4]: Leaving directory `/home/doko/tmp/openimageio-1.3.12~dfsg0/build' how ready is openimageio for OpenGLES? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glew/+bug/1301033/+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 811789] Re: glew compiled without -fPIC flag
according to the build logs this is at least fixed in 14.04 LTS ** Changed in: glew (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to glew in Ubuntu. https://bugs.launchpad.net/bugs/811789 Title: glew compiled without -fPIC flag Status in “glew” package in Ubuntu: Fix Released Bug description: I'm developing a shared library that uses GLEW. When I'm trying to link it I get the following error: /usr/bin/ld: /usr/lib64/libGLEW.a(glew.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC /usr/lib64/libGLEW.a: could not read symbols: Bad value collect2: ld returned 1 exit status It seems that GLEW in ubuntu is compiled without -fPIC flag. When I compile my library as static I get no errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glew/+bug/811789/+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 1301032] Re: compiz crashed with SIGSEGV in FT_Load_Glyph()
*** This bug is a duplicate of bug 1276378 *** https://bugs.launchpad.net/bugs/1276378 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1276378, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1301032/+attachment/4059390/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1301032/+attachment/4059392/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1301032/+attachment/4059393/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1301032/+attachment/4059394/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1301032/+attachment/4059395/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1301032/+attachment/4059396/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1301032/+attachment/4059397/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1276378 compiz crashed with SIGSEGV in memcpy() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1301032 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() Status in “unity” package in Ubuntu: New Bug description: I'm a non-dev user, just trying 14.04 beta (installed, not the live one) and had screen freezing, and compiz taking 99.7% CPU. So, after a little wait with no signs of recovering, I pkilled compiz from the console. I wasn't doing anything special but typing a search. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 1 23:19:00 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-03-23 (9 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140321) ProcCmdline: compiz ProcEnviron: LANGUAGE=es_ES PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=es_ES.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f87ea0a1e30 __memcpy_sse2_unaligned+32: movdqu (%rsi),%xmm8 PC (0x7f87ea0a1e30) ok source (%rsi) (0x) not located in a known VMA region (needed readable region)! destination %xmm8 ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom fuse lpadmin netdev plugdev sambashare scanner video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1301032/+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
Hi! Will the Visibility: Hidden/Always displayed option be added to the System Settings/Appearance, in Ubuntu 14.04? Or is it too late? Would something like the screenshot in the attachment be possible for unmaximized windows? Thanks. ** Attachment added: Ubuntu.png https://bugs.launchpad.net/unity/+bug/682788/+attachment/4059518/+files/Ubuntu.png -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/682788 Title: Improve Unity Global Menu Status in Ayatana Design: Fix Committed Status in Compiz: Invalid Status in Unity: Fix Committed 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 1208019] Re: Eclipse menus doesn't show up in Saucy
I created the Java Ayatana Project http://code.google.com/p/java-swing- ayatana/, And I have a similar problem, when you change the menu items direct of menu bar, the menu items aren't refresh, and the Eclipse Kepler create and remove menu items direct of menu bar for a open file or selected project or resource. -- 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: Confirmed 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 1301067] Re: compiz crashed with SIGSEGV in _int_malloc()
*** This bug is a duplicate of bug 1235010 *** https://bugs.launchpad.net/bugs/1235010 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1235010, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1301067/+attachment/4059572/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1301067/+attachment/4059574/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1301067/+attachment/4059576/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1301067/+attachment/4059577/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1301067/+attachment/4059578/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1301067/+attachment/4059579/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1301067/+attachment/4059580/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1235010 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1301067 Title: compiz crashed with SIGSEGV in _int_malloc() Status in “unity” package in Ubuntu: New Bug description: I was trying to access aplication lens ProblemType: Crash 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 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Tue Apr 1 20:45:30 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-03-21 (11 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140319) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7f7b593f2b27 _int_malloc+103: mov 0x10(%rcx),%rdi PC (0x7f7b593f2b27) ok source 0x10(%rcx) (0x14300010) not located in a known VMA region (needed readable region)! destination %rdi ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: _int_malloc (av=av@entry=0x7f7b0020, bytes=bytes@entry=8) at malloc.c:3351 __libc_calloc (n=optimized out, elem_size=optimized out) at malloc.c:3219 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: compiz crashed with SIGSEGV in _int_malloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1301067/+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 proposed exactly that to Marcon Trevisan and he asked me to look for John Lea on IRC. I confess I haven't had the time (I've never used IRC before and haven't even learned how to). Here's my proposal: http://blog.3v1n0.net/informatica/linux/ubuntu- introducing-locally-integrated-menus-to- unity-7/?utm_source=twitterfeedutm_medium=twitter#comment-1270843203 (there's a pretty interesting talk in the comments at that Marco's post) While it probably is too late to put the title on the screen top bar and the menu permanently visible on the window title bar, Marco said he would put some gconf/dconf setting to make the menu permanently visible. -- 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 Committed 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 1208019] Re: Eclipse menus doesn't show up in Saucy
@zap-4 Hi Wiktor, my apologies, I'm not an Eclipse user. Is there a set of simple steps I could do to reproduce the missing menus problem? -- 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: Confirmed 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 1301125] [NEW] Lock screen after idle time freezes unity
Public bug reported: Hello, I recently upgrade to 14.04. My system uses fglrx provided by 14.04. When I lock manually the screen, I get no problem. I can even sleep the system without problem. However, when the screen is locked by idle time, I cannot unlock it. At this point, I can see the screen but with some kind of translucent panel over it. Mouse also works. I tried to type blink the password but I had no luck. I only get a working system by going text mode (ctrl+alt+f1) and restarting lightdm. No dmesg or Xorg logs seems to indicate any error. The only strange log was in .xsession-errors.old: init: processos unity-settings-daemon main (2495) terminados com status 1 init: processos gnome-session (Unity) main (2539) terminados com status 1 init: processos unity-panel-service main (2572) terminados com status 1 init: processos hud main (2536) terminados com status 1 init: processo indicator-powermain (2740) morto pelo sinal TERM init: processo indicator-datetimemain (2741) morto pelo sinal TERM init: processo indicator-soundmain (2747) morto pelo sinal TERM init: processo indicator-printersmain (2748) morto pelo sinal TERM init: processo indicator-sessionmain (2768) morto pelo sinal TERM init: processo indicator-syncmain (2795) morto pelo sinal TERM init: processo update-notifier-crash (/var/crash/_usr_bin_istanbul.1000.crash)main (4987) morto pelo sinal TERM init: processos unity-panel-service-lockscreen main (7447) terminados com status 1 init: Disconnected from notified D-Bus bus init: processos at-spi2-registryd main (2538) terminados com status 1 But as it has no time info, I cannot tell when they happened. At least another user faces the same problem: http://ubuntuforums.org/showthread.php?t=2214421 And this seems to be different from bug 1283938 as pm sleep/wake works as expected. 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: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 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] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 2 00:01:05 2014 DistUpgraded: 2014-03-31 21:24:46,145 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.11.0-18-generic, x86_64: installed fglrx-updates, 13.350.1, 3.13.0-20-generic, x86_64: installed vboxhost, 4.3.10, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-20-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0012] InstallationDate: Installed on 2012-10-19 (529 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) JockeyStatus: kmod:wl - Broadcom STA wireless driver (Proprietário, Desativado, Não está em uso) [auto-install] kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietário, Desativado, Não está em uso) kmod:fglrx_updates - ATI Fire GL (Proprietário, Habilitado, Não está em uso) MachineType: Dell Inc. XPS 8300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=6633d579-d782-47ec-ad5a-22abac1412a0 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-01 (1 days ago) dmi.bios.date: 10/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0Y2MRG dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/17/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8300 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 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: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 1 23:48:17 2014 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open
[Dx-packages] [Bug 1292041] Re: Lockscreen doesn't turn off the screen
** No longer affects: unity-greeter (Ubuntu) ** No longer affects: unity (Ubuntu) ** No longer affects: unity -- 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/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't trun off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+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 1299454] Re: Display needs to be unlocked twice
*** This bug is a duplicate of bug 1292451 *** https://bugs.launchpad.net/bugs/1292451 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/1299454 Title: Display needs to be unlocked twice Status in “unity” package in Ubuntu: Confirmed Bug description: I've had this issue since the new lock screen: 1) Wait for the display to get locked 2) Unlock the display by entering you password What should happen: - The display should unlock and stay unlocked What happens instead: - The display gets unlocked, but after ~15 secs the display gets locked again by itself - Unlocking the display once more makes it now stay unlocked This happens something like 7/10. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Mar 29 15:11:06 2014 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/1299454/+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
