[Dx-packages] [Bug 784270] Re: List of upcoming events from calendar shows only days names instead of dates
The Date & Time spec covers this in https://wiki.ubuntu.com/TimeAndDate#Presenting_times ** Changed in: ayatana-design Status: New => Fix Committed ** Changed in: ayatana-design Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/784270 Title: List of upcoming events from calendar shows only days names instead of dates Status in Ayatana Design: Fix Released Status in The Date and Time Indicator: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: Binary package hint: indicator-datetime I use Ubuntu 11.04. I have some events in Evolution calendar. Those events are shown in the indicator. Unfortunately next to the event name it's only name of the day that event will happen. So if I have 3 events on Mondays, I don't know if it's one Monday, and which Monday. Displaying full date would be much more useful in this case. See screenshot with the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/784270/+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 1291370] Re: in virtual-manager, the global-menu or local integrated menus stopped working in the vm-display
Marc, thanks for pinpointing exactly where the regression occurred. virt-manager disables gtk-enable-mnemonics when a running VM window is focused and re-enables it when the focus is lost. So clicking the global menu steals the focus away, changing the gtk-enable-mnemonics setting, which updates the menus (adding back their mnemonics). Since menu updates are done by removing and re-adding the same menu, the old menu is opened but immediately replaced by a new unopened menu... I think we need to patch virt-manager to fix this. -- 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/1291370 Title: in virtual-manager, the global-menu or local integrated menus stopped working in the vm-display Status in “unity-gtk-module” package in Ubuntu: Confirmed Status in “virt-manager” package in Ubuntu: Invalid Bug description: 1) open virtual manager 2) create / open a virtual machine 3) start it 4) try to open menu "Send keys" -> Ctrl Alt F2 the menu titles "File, Virtual Machine, ..." are visible but it's not possible to expand them, see any options under them, or click on them. I believe virtual manager is using python-gtk2. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-gtk2-module 0.0.0+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 CurrentDesktop: Unity Date: Wed Mar 12 13:24:29 2014 InstallationDate: Installed on 2012-01-12 (789 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318) SourcePackage: unity-gtk-module UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1291370/+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 1292935] Re: New Lockscreen inhibits putting the screens to sleep.
** Changed in: unity (Ubuntu) Importance: Undecided => High ** Changed in: unity (Ubuntu) Status: New => Triaged ** Changed in: unity (Ubuntu) Assignee: Stephen M. Webb (bregma) => Andrea Azzarone (andyrock) -- 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/1292935 Title: New Lockscreen inhibits putting the screens to sleep. Status in “unity” package in Ubuntu: Triaged Bug description: Ok, so since the new lockscreen landed in Trusty, I've been observing inconsistent behavior with the power settings on my screens. I managed to do a little bit of troubleshooting and this is what I discovered: My power settings are set such that the screens turn off prior to the screen locking (5 minutes and 10 minutes respectively but I don't think the times are relevant). If I walk away from my computer and leave it unlocked, the screens will successfully power down, and the next time I come back then the lock screen will appear when I wake up the screens. This part is good. If I type Ctrl-Alt-L, the screen locks, but it keeps the screens on, even for extended periods of time (eg, overnight. On several occaisions I've locked my screen, gone to bed, and then woken up to discover both my screens powered on at maximum brightness just displaying that sexy lockscreen). Oddly, when I unlock the screens in this state, what will happen is that just a few seconds after unlocking, some kind of timer will trigger and say "oh yeah, time to power down the screens!" so even though I *just unlocked my desktop*, both screens power down for about 5 seconds and then turn back on, and *then* they "fade to black" and snap back to maximum brightness. It's very discordant. So, the workaround for me is "don't lock the screen", and that's probably fine at home, but obviously that's not a viable solution in any kind of security context, eg in an office. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-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: Sat Mar 15 10:56:14 2014 InstallationDate: Installed on 2013-12-06 (99 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-12-06 (99 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1292935/+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)
** Changed in: unity (Ubuntu) Status: New => Triaged ** Changed in: unity (Ubuntu) Importance: Undecided => High ** Changed in: unity (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (andyrock) -- 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” 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/ubuntu/+source/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 1244010] Re: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service:11:_IO_vfprintf_internal:buffered_vfprintf:_IO_vfprintf_internal:___fprintf_chk:pa_log_levelv_meta
** Changed in: indicator-sound Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1244010 Title: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound- service:11:_IO_vfprintf_internal:buffered_vfprintf:_IO_vfprintf_internal:___fprintf_chk:pa_log_levelv_meta Status in Sound Menu: Fix Released Status in “indicator-sound” package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-sound. This problem was most recently seen with version 12.10.2+13.10.20131011-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/d73e81071c5c71876c0087cb4715f18d3c038725 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1244010/+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 1270812] Re: pyruntest fails to build from source in trusty
This bug was fixed in the package pyruntest - 0.1+13.10.20130702-0ubuntu3 --- pyruntest (0.1+13.10.20130702-0ubuntu3) trusty; urgency=medium * Fix FTBFS (LP: #1270812): + Pass "cover_pylib=True" to coverage, as it now defaults to not cover modules installed in standard library. + Add jquery build-dependencies for coverage to be able to produce html coverage reports. -- Dimitri John LedkovSat, 15 Mar 2014 23:12:17 + ** Changed in: pyruntest (Ubuntu Trusty) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to pyruntest in Ubuntu. https://bugs.launchpad.net/bugs/1270812 Title: pyruntest fails to build from source in trusty Status in “pyruntest” package in Ubuntu: Fix Released Status in “pyruntest” source package in Trusty: Fix Released Bug description: see https://launchpadlibrarian.net/162444081/buildlog_ubuntu- trusty-i386.pyruntest_0.1%2B13.10.20130702-0ubuntu1_FAILEDTOBUILD.txt.gz running build running build_scripts creating build creating build/scripts-2.7 copying and adjusting pyruntest -> build/scripts-2.7 changing mode of build/scripts-2.7/pyruntest from 664 to 775 debian/rules override_dh_auto_test make[1]: Entering directory `/build/buildd/pyruntest-0.1+13.10.20130702' nosetests F.. == FAIL: tests.FunctionalRunTests.test_can_generate_html_coverage -- _StringException: Traceback (most recent call last): File "/build/buildd/pyruntest-0.1+13.10.20130702/tests.py", line 197, in test_can_generate_html_coverage self.assertThat(code, Equals(0)) File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 412, in assertThat raise MismatchError(matchee, matcher, mismatch, verbose) MismatchError: 0 != 1 -- Ran 19 tests in 4.411s FAILED (failures=1) make[1]: *** [override_dh_auto_test] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyruntest/+bug/1270812/+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 1270812] Re: pyruntest fails to build from source in trusty
** Branch linked: lp:ubuntu/trusty-proposed/pyruntest -- You received this bug notification because you are a member of DX Packages, which is subscribed to pyruntest in Ubuntu. https://bugs.launchpad.net/bugs/1270812 Title: pyruntest fails to build from source in trusty Status in “pyruntest” package in Ubuntu: Confirmed Status in “pyruntest” source package in Trusty: Confirmed Bug description: see https://launchpadlibrarian.net/162444081/buildlog_ubuntu- trusty-i386.pyruntest_0.1%2B13.10.20130702-0ubuntu1_FAILEDTOBUILD.txt.gz running build running build_scripts creating build creating build/scripts-2.7 copying and adjusting pyruntest -> build/scripts-2.7 changing mode of build/scripts-2.7/pyruntest from 664 to 775 debian/rules override_dh_auto_test make[1]: Entering directory `/build/buildd/pyruntest-0.1+13.10.20130702' nosetests F.. == FAIL: tests.FunctionalRunTests.test_can_generate_html_coverage -- _StringException: Traceback (most recent call last): File "/build/buildd/pyruntest-0.1+13.10.20130702/tests.py", line 197, in test_can_generate_html_coverage self.assertThat(code, Equals(0)) File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 412, in assertThat raise MismatchError(matchee, matcher, mismatch, verbose) MismatchError: 0 != 1 -- Ran 19 tests in 4.411s FAILED (failures=1) make[1]: *** [override_dh_auto_test] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyruntest/+bug/1270812/+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 1270812] Re: pyruntest fails to build from source in trusty
** Changed in: pyruntest (Ubuntu Trusty) Assignee: Thomi Richards (thomir) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of DX Packages, which is subscribed to pyruntest in Ubuntu. https://bugs.launchpad.net/bugs/1270812 Title: pyruntest fails to build from source in trusty Status in “pyruntest” package in Ubuntu: Confirmed Status in “pyruntest” source package in Trusty: Confirmed Bug description: see https://launchpadlibrarian.net/162444081/buildlog_ubuntu- trusty-i386.pyruntest_0.1%2B13.10.20130702-0ubuntu1_FAILEDTOBUILD.txt.gz running build running build_scripts creating build creating build/scripts-2.7 copying and adjusting pyruntest -> build/scripts-2.7 changing mode of build/scripts-2.7/pyruntest from 664 to 775 debian/rules override_dh_auto_test make[1]: Entering directory `/build/buildd/pyruntest-0.1+13.10.20130702' nosetests F.. == FAIL: tests.FunctionalRunTests.test_can_generate_html_coverage -- _StringException: Traceback (most recent call last): File "/build/buildd/pyruntest-0.1+13.10.20130702/tests.py", line 197, in test_can_generate_html_coverage self.assertThat(code, Equals(0)) File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 412, in assertThat raise MismatchError(matchee, matcher, mismatch, verbose) MismatchError: 0 != 1 -- Ran 19 tests in 4.411s FAILED (failures=1) make[1]: *** [override_dh_auto_test] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyruntest/+bug/1270812/+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 1244702] Re: /usr/lib/i386-linux-gnu/hud/hud-service:6:__libc_message:malloc_printerr:_int_free:nih_free:hud_application_source_new_for_id
*** This bug is a duplicate of bug 1278439 *** https://bugs.launchpad.net/bugs/1278439 ** This bug has been marked a duplicate of bug 1278439 /usr/lib/i386-linux-gnu/hud/hud-service:6:__libc_message:malloc_printerr:_int_free:nih_free:hud::common::DBusTypes::applicationPath -- 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/1244702 Title: /usr/lib/i386-linux-gnu/hud/hud- service:6:__libc_message:malloc_printerr:_int_free:nih_free:hud_application_source_new_for_id Status in Unity HUD: New Status in “hud” package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding hud. This problem was most recently seen with version 13.10.1+13.10.20131014-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/0b45859ec30260279d3748fd04d43a74f61d604b contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1244702/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 968533] Re: Alt-tab to Firefox sends Firefox to 100% CPU; unity-panel-service to 80% CPU and hud-service to 20-80% CPU
The #18 solution solve the problem for me. (ui.use_unity_menubar = false) Thank you. I hope this will be fixed in the 14.04 release. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/968533 Title: Alt-tab to Firefox sends Firefox to 100% CPU; unity-panel-service to 80% CPU and hud-service to 20-80% CPU Status in Unity: Confirmed Status in “indicator-appmenu” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I've been seeing UI hangs after switching tabs in Firefox, and switching from other applications to Firefox. It can take 3-8 seconds to change *tab*. During this time the CPU is maxed out; typical output from 'top' during this period shows 'hud- service' and 'unity-panel-service' combined using about the same CPU as Firefox itself: 100 10.4 26:07.73 firefox 53 0.6 6:14.86 hud-service 38 1.5 6:42.14 unity-panel-service I suspect that the change is causing a (an inefficient) re-index related to updated menu structures. (Eg. something like the history menu, although I can't see what it is as don't currently have a menu bar). To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/968533/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 942798] Re: unity hud doesn't list menu items from indicator-ng indicators
*** This bug is a duplicate of bug 1165420 *** https://bugs.launchpad.net/bugs/1165420 ** This bug has been marked a duplicate of bug 1165420 Unable to access indicators from HUD -- 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/942798 Title: unity hud doesn't list menu items from indicator-ng indicators Status in Unity HUD: Triaged Status in “hud” package in Ubuntu: Triaged Bug description: Menu items "Power settings" and "Show time in menu bar" from indicator-power are not displayed in Unity's HUD ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 1.93-0ubuntu2 Architecture: amd64 CasperVersion: 1.304 CheckboxSubmission: c029f392d7891201d16e32d195c2666d CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Tue Feb 28 21:18:40 2012 LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120228.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/942798/+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 1218219] Re: hud-service crashed with signal 5 in g_type_create_instance()
*** This bug is a duplicate of bug 1228864 *** https://bugs.launchpad.net/bugs/1228864 ** This bug is no longer a duplicate of private bug 1216323 ** This bug has been marked a duplicate of bug 1228864 hud-service crashed with signal 5 in g_type_create_instance() -- 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/1218219 Title: hud-service crashed with signal 5 in g_type_create_instance() Status in “hud” package in Ubuntu: New Bug description: No idea what happened. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20130822.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 CheckboxSubmission: 2f383a1679e8525d7196eb2518a1921f CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f Date: Thu Aug 29 09:38:51 2013 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/hud-service InstallationDate: Installed on 2011-08-19 (740 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110817) MarkForUpload: True ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/hud-service Signal: 5 SourcePackage: hud StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libbamf3.so.2 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: hud-service crashed with signal 5 in g_type_create_instance() UpgradeStatus: Upgraded to saucy on 2013-06-07 (82 days ago) UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare utah To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1218219/+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 1218313] Re: hud-service crashed with signal 5 in g_type_create_instance()
*** This bug is a duplicate of bug 1228864 *** https://bugs.launchpad.net/bugs/1228864 ** This bug is no longer a duplicate of private bug 1216323 ** This bug has been marked a duplicate of bug 1228864 hud-service crashed with signal 5 in g_type_create_instance() -- 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/1218313 Title: hud-service crashed with signal 5 in g_type_create_instance() Status in “hud” package in Ubuntu: New Bug description: After I closed CompizConfig settings manager, this crash came up. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20130822.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Thu Aug 29 13:11:44 2013 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/hud-service InstallationDate: Installed on 2013-02-27 (183 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130226) MarkForUpload: True ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/hud-service Signal: 5 SourcePackage: hud StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libbamf3.so.2 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: hud-service crashed with signal 5 in g_type_create_instance() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo modified.conffile..etc.apport.crashdb.conf.d.hud.crashdb.conf: [deleted] upstart.hud.log: ** (process:11226): ERROR **: Unable to get org.ayatana.bamf matcher: Fehler beim Aufruf von StartServiceByName für org.ayatana.bamf: Zeitüberschreitung wurde erreicht To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1218313/+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 1219254] Re: hud-service crashed with signal 5 in g_type_create_instance()
*** This bug is a duplicate of bug 1228864 *** https://bugs.launchpad.net/bugs/1228864 ** This bug is no longer a duplicate of private bug 1216323 ** This bug has been marked a duplicate of bug 1228864 hud-service crashed with signal 5 in g_type_create_instance() -- 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/1219254 Title: hud-service crashed with signal 5 in g_type_create_instance() Status in “hud” package in Ubuntu: New Bug description: Not sure what caused this. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20130822.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Wed Aug 28 15:53:14 2013 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/hud-service ExecutableTimestamp: 1377195584 InstallationDate: Installed on 2013-04-28 (123 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/hud-service ProcCwd: /home/dylan ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: hud StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libbamf3.so.2 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: hud-service crashed with signal 5 in g_type_create_instance() UpgradeStatus: Upgraded to saucy on 2013-08-23 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo upstart.hud.log: ** (process:9902): ERROR **: Unable to get org.ayatana.bamf matcher: Error spawning command line 'dbus-launch --autolaunch=5f54fc6986dac9fd6ff8101b517c72b3 --binary-syntax --close-stderr': Child process exited with code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1219254/+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 1218622] Re: hud-service crashed with signal 5 in g_type_create_instance()
*** This bug is a duplicate of bug 1228864 *** https://bugs.launchpad.net/bugs/1228864 ** This bug is no longer a duplicate of private bug 1216323 ** This bug has been marked a duplicate of bug 1228864 hud-service crashed with signal 5 in g_type_create_instance() -- 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/1218622 Title: hud-service crashed with signal 5 in g_type_create_instance() Status in “hud” package in Ubuntu: New Bug description: tried to launch unity8 on my touch capable notebook. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20130822.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Thu Aug 29 22:21:54 2013 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/hud-service InstallationDate: Installed on 2013-08-29 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130829) MarkForUpload: True ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/hud-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_GB:en XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: hud StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libbamf3.so.2 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: hud-service crashed with signal 5 in g_type_create_instance() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1218622/+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 575335] Re: indicator-applet uses extremely large amounts of memory
** Changed in: indicator-applet (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-applet in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/575335 Title: indicator-applet uses extremely large amounts of memory Status in “indicator-applet” package in Ubuntu: Incomplete Bug description: Binary package hint: indicator-applet Probably a duplicate of #369539, but creating a new bug at Sebastien Bacher's direction. Indicator-applet appears to have a memory leak. I upgraded to Lucid the day it was released, before that running a clean if somewhat old install of Karmic. In Karmic I did not experience the issue. Under normal usage, the indicator-applet process uses more and more memory until eventually things start dying from the OOM killer. To combat this, I have been watching the system monitor applet's memory usage graph until it reaches a high level, checking with top to find indicator-applet at the top of the memory usage stack (currently using 882m virt, 617m res 11m shr) and then kill the pid from the command line. I have to do this twice a day. Expected behavior: indicator-applet sits next to my clock and doesn't cause problems. Actual behavior: indicator-applet uses more and more memory over time until the system becomes unstable. lsb_release -a: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 10.04 LTS Release: 10.04 Codename: lucid apt-cache policy indicator-applet: Installed: 0.3.6-0ubuntu2 Candidate: 0.3.6-0ubuntu2 Version table: *** 0.3.6-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status uname -a: Linux motoko 2.6.32-21-generic #32-Ubuntu SMP Fri Apr 16 08:09:38 UTC 2010 x86_64 GNU/Linux Further information available upon request. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: indicator-applet 0.3.6-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue May 4 09:28:56 2010 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: indicator-applet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/575335/+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 781088] Re: Time is not syncronized with NTP-server
Hi Charles. I'm a core dev and I run Trusty on my laptop. Still affected as of 2 months ago when I last traveled with that laptop. I will test again with the latest software and post the results soon. Excerpts from Charles Kerr's message of 2014-03-15 19:29:50 UTC: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. The issue that you reported is one that should be > reproducible with the live environment of the Desktop ISO of the > development release - Trusty Tahr. It would help us greatly if you could > test with it so we can work on getting it fixed in the next release of > Ubuntu. You can find out more about the development release at > http://www.ubuntu.com/testing/ . Thanks again and we appreciate your > help. > > ** Changed in: indicator-datetime (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/781088 > > Title: > Time is not syncronized with NTP-server > > Status in “indicator-datetime” package in Ubuntu: > Incomplete > Status in “ntp” package in Ubuntu: > Incomplete > > Bug description: > 11.4 > after installation there doesn't seems to be configured any communication > with the nets NTP-servers, as the time isn't set correctly. > using ntpdate, its possible to get the time set correctly, but this only > last until next boot. > 1) Default ought to be, that there is communication with NTP-server > (when setting location to Denmark the NTP-server(s) ought be set to > dk.pool.ntp.org) > 2) When explicitly using ntpdate, it ought to result in a lasting > configuration of the NTP-client. > > ProblemType: Bug > DistroRelease: Ubuntu 11.04 > Package: gnome-system-monitor 2.28.2-0ubuntu1 > ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 > Uname: Linux 2.6.38-8-generic i686 > Architecture: i386 > Date: Wed May 11 12:53:34 2011 > ExecutablePath: /usr/bin/gnome-system-monitor > ProcEnviron: >LANGUAGE=en_US:en >LANG=en_DK.UTF-8 >LC_MESSAGES=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: gnome-system-monitor > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/781088/+subscriptions -- 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/781088 Title: Time is not syncronized with NTP-server Status in “indicator-datetime” package in Ubuntu: Incomplete Status in “ntp” package in Ubuntu: Incomplete Bug description: 11.4 after installation there doesn't seems to be configured any communication with the nets NTP-servers, as the time isn't set correctly. using ntpdate, its possible to get the time set correctly, but this only last until next boot. 1) Default ought to be, that there is communication with NTP-server (when setting location to Denmark the NTP-server(s) ought be set to dk.pool.ntp.org) 2) When explicitly using ntpdate, it ought to result in a lasting configuration of the NTP-client. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-system-monitor 2.28.2-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Date: Wed May 11 12:53:34 2011 ExecutablePath: /usr/bin/gnome-system-monitor ProcEnviron: LANGUAGE=en_US:en LANG=en_DK.UTF-8 LC_MESSAGES=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/781088/+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 740821] Re: Month and year navigation items aren't keyboard-selectable
** Also affects: ido Importance: Undecided Status: New ** Changed in: indicator-datetime (Ubuntu) Assignee: Karl Lattimer (karl-qdh) => (unassigned) ** Changed in: ido Status: New => Confirmed ** Changed in: ido Importance: Undecided => Low -- 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/740821 Title: Month and year navigation items aren't keyboard-selectable Status in Indicator Display Objects: Confirmed Status in The Date and Time Indicator: Confirmed Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: Binary package hint: indicator-datetime indicator-datetime 0.1.98-0ubuntu1, Ubuntu Natty 1. Open the clock menu. 2. Press Down twice. 3. Press Right once. 4. Press Right once again. What happens: 2. The Monday of the second week in the calendar is focused. 3. The Tuesday of the second week in the calendar is focused. 4. The Wednesday of the second week in the calendar is focused. What should happen: 2. The previous-month navigation item is highlighted. 3. The next-month navigation item is highlighted. 4. The previous-year navigation item is highlighted. To manage notifications about this bug go to: https://bugs.launchpad.net/ido/+bug/740821/+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 741011] Re: Calendar in clock menu has inconsistent background color
** Also affects: ido Importance: Undecided Status: New ** Changed in: ido Status: New => Confirmed ** Changed in: ido Importance: Undecided => Low -- 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/741011 Title: Calendar in clock menu has inconsistent background color Status in Indicator Display Objects: Confirmed Status in The Date and Time Indicator: Confirmed Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: indicator-datetime 0.1.98-0ubuntu1, Ubuntu Natty indicator-datetime 0.2.93-0ubuntu1, Ubuntu Ocelot 1. In "Time & Date Settings…" > "Clock", check "Monthly calendar" if it is not checked already. 2. Open the clock menu. What you see: The calendar has a different background color from the rest of the menu. What you should see: The calendar has exactly the same background color as the rest of the menu. (This report previously also mentioned a border around the calendar, which has since been fixed.) To manage notifications about this bug go to: https://bugs.launchpad.net/ido/+bug/741011/+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 1024756] Re: where the clock should be I have the word "Time"
When I saw this bug, I'm pretty sure I was running 12.10. I haven't seen appear since though. I imagine it had to do with an upgrade bug, since I've never seen it on a fresh install of any version. -- 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/1024756 Title: where the clock should be I have the word "Time" Status in “indicator-datetime” package in Ubuntu: Incomplete Bug description: From original question: "where the clock should be I have the word time, re-installed indicator-datetime (suggested on a help website), changed location in time & date settings from localtime to London (noticed no buttons there ie OK) still no clock. " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1024756/+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 940919] Re: clock is not automatically set in live session
Since the datetime panel has moved from indicator-datetime to unity- control-center, I'm reassigning this Affects there based on Sebastien's logic in comment #8, though I agree with him that this is more an issue with the liveCD's environment than it is control-center or indicator- datetime... ** Project changed: indicator-datetime => unity-control-center ** Package changed: indicator-datetime (Ubuntu) => unity-control-center (Ubuntu) -- 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/940919 Title: clock is not automatically set in live session Status in Unity Control Center: Confirmed Status in “ubiquity” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: Confirmed Bug description: Hello Launch a live session, choose a a language outside of the UTC (italian is UTC+1), when the live session will be launched the clock will be set to UTC instead of localized even if the net is working. expected A fully localized environenment at startup probably related to bug 940908 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.3.90-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 ApportVersion: 1.93-0ubuntu2 Architecture: amd64 CasperVersion: 1.304 Date: Sat Feb 25 12:42:07 2012 LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120225) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.2-0ubuntu2 deja-dup21.90-0ubuntu1 gnome-bluetooth 3.2.2-0ubuntu2 indicator-datetime 0.3.90-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-control-center/+bug/940919/+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 996623] Re: "Time in other locations" always show Chongqing for GMT+8
*** This bug is a duplicate of bug 966658 *** https://bugs.launchpad.net/bugs/966658 ** This bug is no longer a duplicate of bug 996845 Ubuntu 12.04. "Time in other locations" shows the time for unspecified locations . ** This bug has been marked a duplicate of bug 966658 Indicator Date Time shows clocks that have been deleted from the list. -- 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/996623 Title: "Time in other locations" always show Chongqing for GMT+8 Status in The Date and Time Indicator: Confirmed Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. sudo dpkg-reconfigure tzdata Set the timezone to be Asia/Hong_Kong 2. date Verify that it shows "HKT" 3. check "Time in other locations" to enable this feature. The corresponding menu would show "UTC", "Chongqing", "Hong Kong". "Chongqing" is not expected. 4. By clicking "Chongqing", "Hong Kong" would disappear. Probable reasons (I haven't checked code): 1. "Chongqing" is somehow hard coded for GMT+8 2. Asia/Chongqing is the auto detection result of my PC. I'm in Shenzhen though. The auto detection is implicitly called. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/996623/+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 784270] Re: List of upcoming events from calendar shows only days names instead of dates
** Changed in: indicator-datetime (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/784270 Title: List of upcoming events from calendar shows only days names instead of dates Status in Ayatana Design: New Status in The Date and Time Indicator: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: Binary package hint: indicator-datetime I use Ubuntu 11.04. I have some events in Evolution calendar. Those events are shown in the indicator. Unfortunately next to the event name it's only name of the day that event will happen. So if I have 3 events on Mondays, I don't know if it's one Monday, and which Monday. Displaying full date would be much more useful in this case. See screenshot with the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/784270/+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 996845] Re: Ubuntu 12.04. "Time in other locations" shows the time for unspecified locations .
*** This bug is a duplicate of bug 966658 *** https://bugs.launchpad.net/bugs/966658 ** This bug has been marked a duplicate of bug 966658 Indicator Date Time shows clocks that have been deleted from the list. -- 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/996845 Title: Ubuntu 12.04. "Time in other locations" shows the time for unspecified locations . Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: Ubuntu 12.04 64 bits. Unfortunately, I don't know the name of the package which shows Time and Date on the top menu. After I enabled option "Time in other locations" in All Settings -> Time & Date, it had "UTC". I specified a city and closed the window. After I click on Date and Clock (top menu) and notices that there are another locations which I did not specify. After that I opened All Settings -> Time & Date windows again and deleted all locations (Screenshot 1). When I clicked on Date and Clock (top menu) I saw two location "None" and the city of my current time zone (Screenshot 2). I think it's a bug. I understand that "None" is UTC time, but I did not specify to show it so it should not be displayed. I also did not specify "Melbourne" time as I already have it on the panel, so it should not be displayed as well. Please fix. Both screenshots are attached as archive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/996845/+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 1024756] Re: where the clock should be I have the word "Time"
Thank you for taking the time to report this bug and helping to make Ubuntu better. What version of Ubuntu were you running when you encountered this? Please test and see if you can reproduce the issue with the live environment of the Desktop ISO of the development release - Trusty Tahr. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help. ** Changed in: indicator-datetime (Ubuntu) Status: Confirmed => Incomplete -- 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/1024756 Title: where the clock should be I have the word "Time" Status in “indicator-datetime” package in Ubuntu: Incomplete Bug description: From original question: "where the clock should be I have the word time, re-installed indicator-datetime (suggested on a help website), changed location in time & date settings from localtime to London (noticed no buttons there ie OK) still no clock. " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1024756/+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 1084862] Re: Unable to add locations of time/date to show in clock applet on computer behind a proxy
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop ISO of the development release - Trusty Tahr. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help. ** Package changed: indicator-datetime (Ubuntu) => unity-control-center (Ubuntu) ** Changed in: unity-control-center (Ubuntu) Status: Confirmed => Incomplete ** Project changed: indicator-datetime => unity-control-center ** Changed in: unity-control-center Status: New => Incomplete -- 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/1084862 Title: Unable to add locations of time/date to show in clock applet on computer behind a proxy Status in Unity Control Center: Incomplete Status in “unity-control-center” package in Ubuntu: Incomplete Bug description: Ubuntu version info: Description: Ubuntu 12.10 Release: 12.10 Gnome Control Centre version info: Installed: 1:3.4.2-0ubuntu19 Candidate: 1:3.4.2-0ubuntu19 Version table: *** 1:3.4.2-0ubuntu19 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status When trying to add extra locations to show the time for in the Clock applet (via Time & Date Settings -> Clock -> Choose Locations) the list of possible matches for my typed entry is never shown. I'm using a computer with a proxy configured via the network applet (and "Use system-wide" pressed) and suspect that's the root of the trouble however I'm not sure how to go about debugging this, any pointers would be appreciated. Steps taken: * Click clock -> "Time & Date Settings" * Select "Clock" tab * Check "Time in other locations" * Click "Choose Locations" * Click "+" * Type "New Yo" * nothing happens Expected results: * On other machines (without the proxied connection) a list of potential locations from which I can select "New York, New York" is shown. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-control-center/+bug/1084862/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
** Branch linked: lp:~noskcaj/unity-control-center/gnome-desktop-3.10b ** Branch linked: lp:~noskcaj/unity-settings-daemon/gnome-desktop-3.10b ** Branch unlinked: lp:~noskcaj/unity-control-center/gnome-desktop-3.10 ** Branch unlinked: lp:~noskcaj/unity-settings-daemon/gnome-desktop-3.10 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Invalid Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: In Progress Bug description: Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- control-center 3.10. This however requires a transition to gnome- desktop 3-10. I have been working on this for quite some time however this work was essentially blocked waiting on the unity- forks for settings daemon and control center. These were only finalised the day before feature freeze. Right now there are quite a few features that are not available for configuration in g-c-c given it is so old. We are also hitting some odd bugs with mutter using its own display config separate to what gnome-settings-daemon is doing with xrandr. For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such have forked the display config code from mutter and ported *-settings-daemon and *-control-center to the new api. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. We have tested this via a ppa, however it was hard to get extensive testing, due to the amount of archive churn in the affected packages. I am pretty confident there are no much regressions and I will commit to fixing any issues to do appear. Essentially this transition will involve: new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session) my upstream branch is at https://github.com/darkxst/displayconfig (I had trouble working out how to import a git branch into bzr, but I imagine it should live in bzr once approved) gnome/unity-settings-daemon, have backported patches to adapt to the new API. Likewise for gnome/unity-control-center. All other rdepends just require a no-change rebuild to adapt to the new soname. Assuming this gets a approved, subsequent FFe's for gnome-settings- daemon and gnome-control-center 3.10 will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1043860] Re: Manual setting of time and date has no effect on the clock present on the desktop
This is ameliorated in 14.04, but still present. indicator-datetime updates its display at least once per minute, so the click Akhila mentioned in comment #5 isn't necessary anymore. However, it still doesn't update immediately when the user changes the time manually. org.freedesktop.timedate1 provides a mechanism for setting the time, but doesn't appear to have a signal notifying when it's been set. I'm not what the Right Way is to listen for manual time changes here...? ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided => Low ** Changed in: indicator-datetime (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1043860 Title: Manual setting of time and date has no effect on the clock present on the desktop Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: Clock was already showing proper local time and date. When I tried to changethe time and date manually in the 'Time and Date' settings menu, it takes the changes but those changes are not reflected on the desktop clock. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1 Uname: Linux 3.5.0-10-generic i686 ApportVersion: 2.4-0ubuntu6 Architecture: i386 Date: Thu Aug 30 19:34:33 2012 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120814.1) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1043860/+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 1001595] Re: Clock does not respect regional settings
** Changed in: indicator-datetime Importance: Wishlist => Low ** Changed in: indicator-datetime (Ubuntu) Importance: Wishlist => Low -- 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/1001595 Title: Clock does not respect regional settings Status in The Date and Time Indicator: Confirmed Status in Unity: Invalid Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: The clock unity applet (or indicator) have an option to show a date. Regional settings are set to show the date as "19 may", but the clock shows "may 19" instead. After clicking on a clock, in a calendar, it shows properly — 19 may 2012. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1001595/+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 784270] Re: List of upcoming events from calendar shows only days names instead of dates
This is not the case in newer versions of indicator-datetime. Any date that lies outside of today or the next 6 days is given a date. ** Changed in: indicator-datetime (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: indicator-datetime Status: Confirmed => Fix Released ** Changed in: indicator-datetime Importance: Undecided => Low -- 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/784270 Title: List of upcoming events from calendar shows only days names instead of dates Status in Ayatana Design: New Status in The Date and Time Indicator: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Committed Bug description: Binary package hint: indicator-datetime I use Ubuntu 11.04. I have some events in Evolution calendar. Those events are shown in the indicator. Unfortunately next to the event name it's only name of the day that event will happen. So if I have 3 events on Mondays, I don't know if it's one Monday, and which Monday. Displaying full date would be much more useful in this case. See screenshot with the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/784270/+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 1044353] Re: indicator-datetime-session has 100% cpu use with geoclue-geonames
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop ISO of the development release - Trusty Tahr. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help. ** Changed in: indicator-datetime (Ubuntu) Status: New => Incomplete -- 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/1044353 Title: indicator-datetime-session has 100% cpu use with geoclue-geonames Status in “indicator-datetime” package in Ubuntu: Incomplete Bug description: I had geoclue-geonames installed and not geoclue-ubuntu-geoip. I don't know why, probably happend at a random point during the quantal dist- upgrades. This caused indicator datetime to spinn 100% cpu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1044353/+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 781088] Re: Time is not syncronized with NTP-server
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop ISO of the development release - Trusty Tahr. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help. ** Changed in: indicator-datetime (Ubuntu) Status: Confirmed => Incomplete -- 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/781088 Title: Time is not syncronized with NTP-server Status in “indicator-datetime” package in Ubuntu: Incomplete Status in “ntp” package in Ubuntu: Incomplete Bug description: 11.4 after installation there doesn't seems to be configured any communication with the nets NTP-servers, as the time isn't set correctly. using ntpdate, its possible to get the time set correctly, but this only last until next boot. 1) Default ought to be, that there is communication with NTP-server (when setting location to Denmark the NTP-server(s) ought be set to dk.pool.ntp.org) 2) When explicitly using ntpdate, it ought to result in a lasting configuration of the NTP-client. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-system-monitor 2.28.2-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Date: Wed May 11 12:53:34 2011 ExecutablePath: /usr/bin/gnome-system-monitor ProcEnviron: LANGUAGE=en_US:en LANG=en_DK.UTF-8 LC_MESSAGES=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/781088/+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 966658] Re: Indicator Date Time shows clocks that have been deleted from the list.
** Changed in: indicator-datetime (Ubuntu) Status: Confirmed => Incomplete -- 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/966658 Title: Indicator Date Time shows clocks that have been deleted from the list. Status in The Date and Time Indicator: Incomplete Status in “indicator-datetime” package in Ubuntu: Incomplete Bug description: In Time and Date setting I deleted the default UTC clock and added 3 more. Vancouver, Honolulu and Hong Kong. I then deleted Vancouver. When I select the time in the indicator to view the clocks it shows the deleted UTC time as being "None" with the time and also still shows Vancouver even though it has been deleted. Pics to be attached. I have updated and rebooted several times. Once it did only show the two remaining correctly but then it reverted back to showing them all again. In my clock "Locations" settings it only shows Honolulu and Hong Kong. If I cycle "Time in other locations" setting on and off all four locations still show. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: indicator-datetime 0.3.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Tue Mar 27 14:53:40 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/966658/+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 1188849] Re: unity-panel-service crashed with SIGSEGV in ido_calendar_menu_item_get_calendar()
This was caused by a 'visible' callback being triggered before the IdoCalendarWidget had been created. Fixed in 13.10 by decoupling IDO from indicator-datetime. ** Changed in: indicator-datetime Status: New => Fix Released ** Changed in: indicator-datetime (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1188849 Title: unity-panel-service crashed with SIGSEGV in ido_calendar_menu_item_get_calendar() Status in The Date and Time Indicator: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: $ lsb_release -rd Description:Ubuntu Saucy Salamander (development branch) Release:13.10 $ apt-cache policy indicator-datetime indicator-datetime: Installed: 12.10.3daily13.06.07-0ubuntu1 Candidate: 12.10.3daily13.06.07-0ubuntu1 Version table: *** 12.10.3daily13.06.07-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: indicator-datetime 12.10.3daily13.06.07-0ubuntu1 ProcVersionSignature: Ubuntu 3.9.0-4.9-generic 3.9.4 Uname: Linux 3.9.0-4-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat Jun 8 05:47:56 2013 ExecutablePath: /usr/lib/unity/unity-panel-service InstallationDate: Installed on 2012-09-30 (250 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.1) MarkForUpload: True ProcCmdline: /usr/lib/unity/unity-panel-service SegvAnalysis: Segfault happened at: 0x7fa953be99e6 : cmp%rax,(%rdx) PC (0x7fa953be99e6) ok source "%rax" ok destination "(%rdx)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: indicator-datetime StacktraceTop: ido_calendar_menu_item_get_calendar () from /usr/lib/x86_64-linux-gnu/libido3-0.1.so.0 ?? () from /usr/lib/indicators3/7/libdatetime.so 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 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in ido_calendar_menu_item_get_calendar() UpgradeStatus: Upgraded to saucy on 2013-05-06 (32 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1188849/+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 1228093] Re: Dash content flickers when the touchpad is used to scroll it.
** Changed in: nux Milestone: 4.0.6 => 4.0.7 -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1228093 Title: Dash content flickers when the touchpad is used to scroll it. Status in Nux: In Progress Status in “nux” package in Ubuntu: In Progress Bug description: When the touchpad is used to scroll the dash sometimes scroll down is dected as scroll up and vice versa. Two fingers scroll must be ON! This is because horizontal scrolling is now enabled by default and can't be disabled using g-c-c. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1228093/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1050959] Re: Dash - Fix Dash scrollbar so that it does not displace Dash background texture
** Changed in: nux Milestone: 4.0.6 => 4.0.7 -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1050959 Title: Dash - Fix Dash scrollbar so that it does not displace Dash background texture Status in Ayatana Design: Fix Committed Status in Nux: In Progress Status in Unity: Won't Fix Status in Unity 6.0 series: Won't Fix Status in “nux” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Bug description: Prior to building the full version of the overlay scrollbars, the most urgent fix is to stop the current scrollbar displacing the Dash background texture. Once this issue is fixed the next step is to move on to bug #608124 To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1050959/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1282884] Re: compiz crashed with SIGSEGV in __dynamic_cast()
** Changed in: nux 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/1282884 Title: compiz crashed with SIGSEGV in __dynamic_cast() Status in Nux: Fix Released Status in “nux” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Bug description: $ apt-cache policy compiz compiz: Installed: 1:0.9.11+14.04.20140218-0ubuntu1 Candidate: 1:0.9.11+14.04.20140218-0ubuntu1 Version table: *** 1:0.9.11+14.04.20140218-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy unity unity: Installed: 7.1.2+14.04.20140220-0ubuntu1 Candidate: 7.1.2+14.04.20140220-0ubuntu1 Version table: *** 7.1.2+14.04.20140220-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status $ dmesg [ 3920.925590] compiz[2391]: segfault at 8038 ip 7f863004e31c sp 7fff232998d0 error 4 in libstdc++.so.6.0.19[7f862fff1000+e6000] ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 21 13:20:30 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2012-09-30 (508 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.1) ProcCmdline: compiz Signal: 11 SourcePackage: unity StacktraceTop: __dynamic_cast () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 nux_base_window_accessible_check_active () from /usr/lib/compiz/libunityshell.so ?? () from /usr/lib/compiz/libunityshell.so ?? () from /usr/lib/compiz/libunityshell.so ?? () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in __dynamic_cast() UpgradeStatus: Upgraded to trusty on 2013-11-10 (102 days ago) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1282884/+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 1091589] Re: Nux draws every single BaseWindow to the backbuffer regardless of what the host WM draw region is
** Changed in: nux (Ubuntu) Status: In Progress => Fix Released ** Changed in: nux 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 https://bugs.launchpad.net/bugs/1091589 Title: Nux draws every single BaseWindow to the backbuffer regardless of what the host WM draw region is Status in Nux: Fix Released Status in “nux” package in Ubuntu: Fix Released Bug description: At the moment, this bug is essentially the reason why bug 1091583 exists in unity. When we switched to using backbuffer persistence in compiz, it means that it was no longer permissible for plugins to draw outside damage boundaries, as that would result in bleeding from the regions beneath not being redrawn. At the moment, calling nux::WindowThread::RenderInterfaceFromForeignCmd causes the entire interface to be drawn on-screen, regardless of the damage region inside of compiz. This means bleeding everywhere. Nux should support the concept of being able to selectively present its render targets to the screen, so that there's no overdraw when we only need to re-present, eg, the launcher or the panel. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1091589/+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 1265565] Re: Add Preedit support for XIM
** Changed in: nux Status: Fix Committed => Fix Released ** Changed in: nux (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 https://bugs.launchpad.net/bugs/1265565 Title: Add Preedit support for XIM Status in Nux: Fix Released Status in “nux” package in Ubuntu: Fix Released Bug description: Right now in Nux XIM support is very limited. It basically just commit text, with the default style. It really needs to support preedit highlighting, as well as at lease position the preedit window along the X window boundary. So currently if you are using XIM (such as using fcitx in nux) preedit does not show up in the TextEntry. It only appears once you have committed the text. The preedit text needs to be rendered in the TextEntry while the user types in XIM. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1265565/+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 1291276] Re: None of Geany's keyboard combos appear in the Ubuntu menu bar
** Changed in: unity-gtk-module (Ubuntu) Assignee: (unassigned) => William Hua (attente) -- 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/1291276 Title: None of Geany's keyboard combos appear in the Ubuntu menu bar Status in “unity-gtk-module” package in Ubuntu: New Bug description: Problem occurs in: * geany 1.23.1+dfsg-1, unity-gtk-module 0.0.0+13.10.20130716.1-0ubuntu1, Ubuntu 13.10 * geany 1.23.1+dfsg-1, unity-gtk-module 0.0.0+14.04.20140311-0ubuntu1, Ubuntu Trusty 1. Launch Geany and browse its menus. 2. Launch Geany with its own menu bar (UBUNTU_MENUPROXY= geany) and browse its menus. What you see: 1. No keyboard equivalents for any menu items. 2. Lots of keyboard equivalents for menu items. What you should see: 1. The same keyboard equivalents for menu items. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1291276/+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 705049] Re: blacklist vmplayer
Marking as "incomplete"; we can't proceed on this until someone provides the information requested in comment #3 ** Changed in: unity-gtk-module Assignee: Charles Kerr (charlesk) => (unassigned) ** Changed in: unity-gtk-module (Ubuntu) Status: Triaged => Incomplete ** Changed in: unity-gtk-module Status: Triaged => Incomplete -- 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/705049 Title: blacklist vmplayer Status in Unity GTK+ module: Incomplete Status in “unity-gtk-module” package in Ubuntu: Incomplete Bug description: Binary package hint: appmenu-gtk vmware player does not works correct with appmenu, please blacklist it ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: appmenu-gtk 0.1.9-0ubuntu4.1 ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8 Uname: Linux 2.6.35-24-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Wed Jan 19 20:38:36 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: LANG=ru_UA.utf8 SHELL=/bin/bash SourcePackage: appmenu-gtk To manage notifications about this bug go to: https://bugs.launchpad.net/unity-gtk-module/+bug/705049/+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 1292935] [NEW] New Lockscreen inhibits putting the screens to sleep.
Public bug reported: Ok, so since the new lockscreen landed in Trusty, I've been observing inconsistent behavior with the power settings on my screens. I managed to do a little bit of troubleshooting and this is what I discovered: My power settings are set such that the screens turn off prior to the screen locking (5 minutes and 10 minutes respectively but I don't think the times are relevant). If I walk away from my computer and leave it unlocked, the screens will successfully power down, and the next time I come back then the lock screen will appear when I wake up the screens. This part is good. If I type Ctrl-Alt-L, the screen locks, but it keeps the screens on, even for extended periods of time (eg, overnight. On several occaisions I've locked my screen, gone to bed, and then woken up to discover both my screens powered on at maximum brightness just displaying that sexy lockscreen). Oddly, when I unlock the screens in this state, what will happen is that just a few seconds after unlocking, some kind of timer will trigger and say "oh yeah, time to power down the screens!" so even though I *just unlocked my desktop*, both screens power down for about 5 seconds and then turn back on, and *then* they "fade to black" and snap back to maximum brightness. It's very discordant. So, the workaround for me is "don't lock the screen", and that's probably fine at home, but obviously that's not a viable solution in any kind of security context, eg in an office. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-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: Sat Mar 15 10:56:14 2014 InstallationDate: Installed on 2013-12-06 (99 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-12-06 (99 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Assignee: Stephen M. Webb (bregma) Status: New ** Tags: amd64 apport-bug third-party-packages 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/1292935 Title: New Lockscreen inhibits putting the screens to sleep. Status in “unity” package in Ubuntu: New Bug description: Ok, so since the new lockscreen landed in Trusty, I've been observing inconsistent behavior with the power settings on my screens. I managed to do a little bit of troubleshooting and this is what I discovered: My power settings are set such that the screens turn off prior to the screen locking (5 minutes and 10 minutes respectively but I don't think the times are relevant). If I walk away from my computer and leave it unlocked, the screens will successfully power down, and the next time I come back then the lock screen will appear when I wake up the screens. This part is good. If I type Ctrl-Alt-L, the screen locks, but it keeps the screens on, even for extended periods of time (eg, overnight. On several occaisions I've locked my screen, gone to bed, and then woken up to discover both my screens powered on at maximum brightness just displaying that sexy lockscreen). Oddly, when I unlock the screens in this state, what will happen is that just a few seconds after unlocking, some kind of timer will trigger and say "oh yeah, time to power down the screens!" so even though I *just unlocked my desktop*, both screens power down for about 5 seconds and then turn back on, and *then* they "fade to black" and snap back to maximum brightness. It's very discordant. So, the workaround for me is "don't lock the screen", and that's probably fine at home, but obviously that's not a viable solution in any kind of security context, eg in an office. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-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: Sat Mar 15 10:56:14 2014 InstallationDate: Installed on 2013-12-06 (99 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-12-06 (99 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1292935/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https:/
[Dx-packages] [Bug 1292925] [NEW] compiz crashed with SIGSEGV in std::_Rb_tree_rebalance_for_erase()
Public bug reported: Ubuntu 14.04 LTS with latest updates, Intel GM45 graphics. Sorry, but I didn't notice a crash of compiz so I can't give any further information. I got the apport message after unlocking the display. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-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 CurrentDesktop: Unity Date: Sat Mar 15 18:06:26 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-01-16 (58 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140109) ProcCmdline: compiz ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f95ed407fb9 <_ZSt28_Rb_tree_rebalance_for_erasePSt18_Rb_tree_node_baseRS_+201>: cmpl $0x1,(%rdx) PC (0x7f95ed407fb9) ok source "$0x1" ok destination "(%rdx)" (0x002f) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: std::_Rb_tree_rebalance_for_erase(std::_Rb_tree_node_base*, std::_Rb_tree_node_base&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::_Rb_tree >, std::_Select1st > >, std::less, std::allocator > > >::erase(std::string const&) () from /usr/lib/compiz/libunityshell.so unity::IconLoader::Impl::CoalesceTasksCb() () from /usr/lib/compiz/libunityshell.so unity::glib::Source::SourceCallback(void*) () from /usr/lib/libunity-core-6.0.so.9 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: compiz crashed with SIGSEGV in std::_Rb_tree_rebalance_for_erase() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace trusty ** Information type changed from Private to Public -- 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/1292925 Title: compiz crashed with SIGSEGV in std::_Rb_tree_rebalance_for_erase() Status in “unity” package in Ubuntu: New Bug description: Ubuntu 14.04 LTS with latest updates, Intel GM45 graphics. Sorry, but I didn't notice a crash of compiz so I can't give any further information. I got the apport message after unlocking the display. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-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 CurrentDesktop: Unity Date: Sat Mar 15 18:06:26 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-01-16 (58 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140109) ProcCmdline: compiz ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f95ed407fb9 <_ZSt28_Rb_tree_rebalance_for_erasePSt18_Rb_tree_node_baseRS_+201>: cmpl $0x1,(%rdx) PC (0x7f95ed407fb9) ok source "$0x1" ok destination "(%rdx)" (0x002f) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: std::_Rb_tree_rebalance_for_erase(std::_Rb_tree_node_base*, std::_Rb_tree_node_base&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::_Rb_tree >, std::_Select1st > >, std::less, std::allocator > > >::erase(std::string const&) () from /usr/lib/compiz/libunityshell.so unity::IconLoader::Impl::CoalesceTasksCb() () from /usr/lib/compiz/libunityshell.so unity::glib::Source::SourceCallback(void*) () from /usr/lib/libunity-core-6.0.so.9 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: compiz crashed with SIGSEGV in std::_Rb_tree_rebalance_for_erase() 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/1292925/+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 963633] Invitation to connect on LinkedIn
LinkedIn Bug, I'd like to add you to my professional network on LinkedIn. - Brian Brian Rohan Advisor at AdvoCare International Portland, Oregon Area Confirm that you know Brian Rohan: https://www.linkedin.com/e/-wbhiw0-hst489h2-4s/isd/5850640165495652354/QWmbJYag/?hs=false&tok=2hNOLpNkzzLm81 -- You are receiving Invitation to Connect emails. Click to unsubscribe: http://www.linkedin.com/e/-wbhiw0-hst489h2-4s/A-2OrJZQlSGQWdVrGzo8I2AQH5msYl7d5obBFUF/goo/963633%40bugs%2Elaunchpad%2Enet/20061/I6690167803_1/?hs=false&tok=3Vxxx89o7zLm81 (c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA. -- 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/963633 Title: Unity 5.8: Login to blank screen (all black or just wallpaper) Status in Compiz: Won't Fix Status in Compiz Core: Fix Released Status in Unity Distro Priority: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Status in “compiz” source package in Precise: Fix Released Status in “unity” source package in Precise: Invalid Bug description: WORKAROUND/FIX: unity --reset TEST CASE: Edit ~/.gconf/apps/compiz-1/general/screen0/options/%gconf.xml and add an entry AFTER composite and BEFORE opengl for a dummy plugin name that does not exist. Log out and in again. ORIGINAL DESCRIPTION: After the update earlier today to Unity 5.8, I've found that when I try logging into Unity 3D, all I get is a solid black screen and my mouse cursor. I know it loaded some sort of desktop though, since I could still hit Ctrl+Alt+T and blindly type `sudo reboot` followed by my password to make my computer do a normal reboot. I do not get the same problem with GNOME Shell or Unity 2D (the latter of which I'm using now to report this bug), although for both the screen does temporarily turn black but only for a moment. Unity 5.6 3D used to work perfectly fine for me. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,imgpng,move,vpswitch,mousepoll,resize,snap,wall,grid,place,gnomecompat,regex,session,animation,expo,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: None Date: Fri Mar 23 22:47:44 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (2029.1) MachineType: Gigabyte Technology Co., Ltd. M61PME-S2P ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic root=UUID=2d55fd3e-d932-47b9-abd6-a1fde1ec0453 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6 dmi.board.name: M61PME-S2P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd11/03/2009:svnGigabyteTechnologyCo.,Ltd.:pnM61PME-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM61PME-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: M61PME-S2P dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.7.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/963633/+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 1291302] Re: password never match since IM is on in unity lockscreen
Hi guys, I maintained ibus-mozc in upstream and actually handled very similar issue for GNOME shell. My guts feeling is that this issue is a Unity version of https://code.google.com/p/mozc/issues/detail?id=199 and https://bugzilla.redhat.com/show_bug.cgi?id=1027028 If my assumption is true, all you need to do is just setting GTK_INPUT_PURPOSE_PASSWORD into the password field on the lock screen. Both IBus 1.5.5 and Mozc 1.13.1651.102 have already been aware of GTK_INPUT_PURPOSE_PASSWORD attribute. Here is the list of relevant bugs and commits and announce. Hope this helps. https://bugzilla.redhat.com/show_bug.cgi?id=891835 https://bugzilla.gnome.org/show_bug.cgi?id=691392 https://github.com/ibus/ibus/commit/927e9f58da9b4a9898403c8e339109e2ad2fa966 https://github.com/ibus/ibus/commit/3b3a7ceccbf75f36dee0df45589d79f7e96131f4 https://groups.google.com/d/msg/ibus-devel/mvCHDO1BJUw/hSOCNHSDwPQJ https://bugzilla.redhat.com/show_bug.cgi?id=1013948 https://code.google.com/p/mozc/issues/detail?id=199 ** Bug watch added: code.google.com/p/mozc/issues #199 http://code.google.com/p/mozc/issues/detail?id=199 ** Bug watch added: Red Hat Bugzilla #1027028 https://bugzilla.redhat.com/show_bug.cgi?id=1027028 ** Bug watch added: Red Hat Bugzilla #891835 https://bugzilla.redhat.com/show_bug.cgi?id=891835 ** Bug watch added: GNOME Bug Tracker #691392 https://bugzilla.gnome.org/show_bug.cgi?id=691392 ** Bug watch added: Red Hat Bugzilla #1013948 https://bugzilla.redhat.com/show_bug.cgi?id=1013948 -- 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/1291302 Title: password never match since IM is on in unity lockscreen Status in “unity” package in Ubuntu: New Bug description: With a combination of ibus-mozc and unity, password never match until making IM off manually. How to reproduce: 1. set ibus-mozc as a default IM 2. lock screen with unity (Ctrl+Alt+L) 3. input your password to unlock screen Expected result: screen unlocked. Actual result: password never match until making IM off manually. ibus-mozc: Installed: 1.13.1651.102-2 Candidate: 1.13.1651.102-2 Version table: *** 1.13.1651.102-2 0 500 http://jp.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status unity: Installed: 7.1.2+14.04.20140311-0ubuntu1 Candidate: 7.1.2+14.04.20140311-0ubuntu1 Version table: *** 7.1.2+14.04.20140311-0ubuntu1 0 500 http://jp.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 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 05:58:23 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-15 (148 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131014) 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/1291302/+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 1260728] Re: Indicators should send timestamps, not pre-formatted strings
Hm. Actually the menuitems are timestamps, but indicator-datetime's header is a preformatted string -- we could prevent some bus traffic by changing that to a timestamp as well. We'd need to add a new entry (say, "time-title") to the header dictionary that the indicators pass over, and Unity 8 would need to check for that and if found use it instead of the dict's standard "title" entry. Saviq, does that sound alright to you? ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided => Medium ** Changed in: indicator-datetime (Ubuntu) Status: Invalid => Triaged ** Changed in: indicator-datetime (Ubuntu) Assignee: (unassigned) => Charles Kerr (charlesk) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1260728 Title: Indicators should send timestamps, not pre-formatted strings Status in The Unity 8 shell: Triaged Status in “indicator-datetime” package in Ubuntu: Triaged Status in “indicator-messages” package in Ubuntu: New Bug description: Some indicators send pre-formatted strings, when they should be sending unix timestamps, to be formatted by the UI according to locale / timezone / user preferences. See https://wiki.ubuntu.com/TimeAndDate for the design spec. To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1260728/+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 1182040] Re: Grey printer indicator
** Changed in: indicator-printers (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-printers in Ubuntu. https://bugs.launchpad.net/bugs/1182040 Title: Grey printer indicator Status in “indicator-printers” package in Ubuntu: Confirmed Bug description: Using Cairo-Dock, grey printer indicator seems like drowned in grey background. Attached file is a screenshot that shows printer indicator on top of active LibreOffice worksheet. Perhaps that indicator could be made more colorful? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/1182040/+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 1278290] Re: package python-appindicator 12.10.0-0ubuntu1 failed to install/upgrade: ErrorMessage: le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'éta
*** This bug is a duplicate of bug 1234147 *** https://bugs.launchpad.net/bugs/1234147 ** This bug has been marked a duplicate of bug 1234147 package python-appindicator 12.10.1daily13.04.15-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess new pre-removal script returned error exit status 1 -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1278290 Title: package python-appindicator 12.10.0-0ubuntu1 failed to install/upgrade: ErrorMessage: le sous-processus nouveau script pre- removal a retourné une erreur de sortie d'état 1 Status in “libappindicator” package in Ubuntu: Confirmed Bug description: upgrade 12.10 to 13.10 ProblemType: Package DistroRelease: Ubuntu 13.10 Package: python-appindicator 12.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-45.68-generic 3.5.7.26 Uname: Linux 3.5.0-45-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 10 07:30:04 2014 DuplicateSignature: package:python-appindicator:12.10.0-0ubuntu1:ErrorMessage: le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'état 1 ErrorMessage: ErrorMessage: le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'état 1 MarkForUpload: True SourcePackage: libappindicator Title: package python-appindicator 12.10.0-0ubuntu1 failed to install/upgrade: ErrorMessage: le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'état 1 UpgradeStatus: Upgraded to saucy on 2014-02-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1278290/+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 1065730] Re: Should have a dependency on GTK+3
** Changed in: libappindicator (Ubuntu) Importance: Undecided => Low ** Changed in: libappindicator (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1065730 Title: Should have a dependency on GTK+3 Status in “libappindicator” package in Ubuntu: Triaged Bug description: The -dev package requires the pkgconfig file from GTK so it should also require GTK's dev package to be installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1065730/+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 1286853] Re: package python-appindicator 12.10.1+13.10.20130920-0ubuntu2 failed to install/upgrade: ErrorMessage: le sous-processus nouveau script pre-removal a retourné une erreur
*** This bug is a duplicate of bug 1234147 *** https://bugs.launchpad.net/bugs/1234147 ** This bug has been marked a duplicate of bug 1234147 package python-appindicator 12.10.1daily13.04.15-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess new pre-removal script returned error exit status 1 -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1286853 Title: package python-appindicator 12.10.1+13.10.20130920-0ubuntu2 failed to install/upgrade: ErrorMessage: le sous-processus nouveau script pre- removal a retourné une erreur de sortie d'état 1 Status in “libappindicator” package in Ubuntu: New Bug description: The error is probably the consequence of an upgrade 13.04 13.10 which was on hols and thta I stopped by rebooting. The system is now 13.10 with some glitches. I'll try to reinstall the Python package. Regards ProblemType: Package DistroRelease: Ubuntu 13.10 Package: python-appindicator 12.10.1+13.10.20130920-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sun Mar 2 15:13:04 2014 DuplicateSignature: package:python-appindicator:12.10.1+13.10.20130920-0ubuntu2:ErrorMessage: le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'état 1 ErrorMessage: ErrorMessage: le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2010-05-06 (1396 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MarkForUpload: True SourcePackage: libappindicator Title: package python-appindicator 12.10.1+13.10.20130920-0ubuntu2 failed to install/upgrade: ErrorMessage: le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'état 1 UpgradeStatus: Upgraded to saucy on 2014-03-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1286853/+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 1274669] Re: scope-runner-dbus.py crashed with signal 5 in g_variant_new_va()
I clicked on the Dash launcher button and started to type "Chro" for Chromium, and this error came up. I know I've seen it before, but I need to test further, but I think the error appears the first time you use the Dash after logging in. Once it's appeared the first time, it seems to go away until you reboot again. -- 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/1274669 Title: scope-runner-dbus.py crashed with signal 5 in g_variant_new_va() Status in Unity Manpages Scope: New Status in “libunity” package in Ubuntu: Confirmed Bug description: Typed "disks" in the dash and the crash occured shortly after opening disks. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity-scopes-runner 7.1.3+14.04.20131106-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 30 21:20:26 2014 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InstallationDate: Installed on 2013-08-30 (153 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterpreterPath: /usr/bin/python3.3 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s code/manpages.scope Signal: 5 SourcePackage: libunity StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_new_va () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_builder_add () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: scope-runner-dbus.py crashed with signal 5 in g_variant_new_va() UpgradeStatus: Upgraded to trusty on 2014-01-30 (0 days ago) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers www-data To manage notifications about this bug go to: https://bugs.launchpad.net/unity-scope-manpages/+bug/1274669/+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 1292697] Re: Lock screen paints over indicators, rendering them useless
*** This bug is a duplicate of bug 1292442 *** https://bugs.launchpad.net/bugs/1292442 ** This bug has been marked a duplicate of bug 1292442 lockscreen: menus interactable but render behind the lockscreen -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1292697 Title: Lock screen paints over indicators, rendering them useless Status in “unity” package in Ubuntu: New Bug description: I noticed that the new lock screen appeared to lack a "switch user" function. Thinking this might be cleverly hidden in the cog menu, I clicked on the cog indicator and discovered that it paints the menu *behind* the lock screen background. It still accepts input, it seems, as I accidentally clicked blindly on shutdown, but the menus are entirely invisible. Not sure if there's a switch user option hidden in the cog menu, as clicking blindly to try to find it isn't my cup of tea, but if there isn't, that would be a second bug exposed by fixing this one. :P To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1292697/+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 1292833] [NEW] Alt+F4 doesn't work after restarting unity
Public bug reported: After I restart unity (unity --replace) due to some visual glitches I reported in another bug, Alt+F4 does not work any more. When in a terminal, pressing Alt+F4 results in "OS" typed into the terminal. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia wl 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 15 12:29:06 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages 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/1292833 Title: Alt+F4 doesn't work after restarting unity Status in “unity” package in Ubuntu: New Bug description: After I restart unity (unity --replace) due to some visual glitches I reported in another bug, Alt+F4 does not work any more. When in a terminal, pressing Alt+F4 results in "OS" typed into the terminal. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia wl 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 15 12:29: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/1292833/+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 1292446] Re: lockscreen: on autolock on suspend the fade does not complete before suspend leaving desktop partially visible for a short period on resume
Also if you have open the right click context menu of any application (for example terminal) the screen will not blank off and it will not lock. In this case it doesn't lock even if the mouse cursor is outside of the menu and application. -- 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/1292446 Title: lockscreen: on autolock on suspend the fade does not complete before suspend leaving desktop partially visible for a short period on resume Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: When auto-locking as part of a suspend operation the lock screen still fades to opaque, this takes seconds and mid fade the suspend occurs. This means that on waking the machine the fade is still occurring and the desktop is partially visible potentially exposing information protected by the lock. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-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: Fri Mar 14 10:02:52 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-20 (266 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-11-10 (123 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292446/+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 1292446] Re: lockscreen: on autolock on suspend the fade does not complete before suspend leaving desktop partially visible for a short period on resume
The new Unity lock screen doesn't have problem with application grabbing the mouse (indicators, menus, etc.) but only if the mouse cursor is outside of that menu. When you open menu of application (global or LIM) or indicator then move the cursor outside of that menu and application the screen will blank off and lock. When you have open indicator or menu of application (global or LIM) and mouse is focused on that menu the screen will not blank off and of course it will also not lock. This is still a bug in gnome-screensaver and X server just like the one that you linked because the new Unity lock screen still uses gnome- screensaver. -- 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/1292446 Title: lockscreen: on autolock on suspend the fade does not complete before suspend leaving desktop partially visible for a short period on resume Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: When auto-locking as part of a suspend operation the lock screen still fades to opaque, this takes seconds and mid fade the suspend occurs. This means that on waking the machine the fade is still occurring and the desktop is partially visible potentially exposing information protected by the lock. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-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: Fri Mar 14 10:02:52 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-20 (266 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-11-10 (123 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292446/+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 390508] Re: notifyOSD ignores the expire timeout parameter
The documentation patch is wrong. Notification is a client/server
infrastructure, and it is up to the server to respect or ignore certain
client requests (such as timeout settings, amonst others). The man page
of the client cannot possibly know which server the user is using. Thus,
"currently ignored" is wrong. All you can say is that some servers may
ignore certain settings.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in “notify-osd” package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ "expire-time", 't', 0,G_OPTION_ARG_INT, &expire_timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+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 1244084] Re: Ubuntu 13.10 "Indicator Applet Complete" icon
Marking Ubuntu GNOME task invalid, Edubuntu team maintains gnome- flashback session ** Changed in: ubuntu-gnome Status: New => Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-applet in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1244084 Title: Ubuntu 13.10 "Indicator Applet Complete" icon Status in Ubuntu GNOME: Invalid Status in “indicator-applet” package in Ubuntu: Incomplete Bug description: I just upgraded to *Ubuntu 13.10* using *Gnome (classic) Desktop*. The system "Indicator Applet Complete" icon on the far-right is wrong Note that if I boot to the *Ubuntu Unity desktop* the same applet has the correct icon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1244084/+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
