[Dx-packages] [Bug 1251915] Re: Dash + zeitgeist does not log use of KDE applications for 'Recently used'
Still being hit with this bug on Trusty. Some digging into zeitgeist's source shows that it gets the application info from the *.desktop file using glib's GDesktopAppInfo https://developer.gnome.org/gio/2.33/gio-Desktop-file-based-GAppInfo.html#g-desktop-app-info-new Reading the info from the above URL and using konsole.desktop again as the example, zeitgeist will only find konsole.desktop if it is renamed kde4-konsole.desktop. Another solution is to create a symlink named /usr/share/kde4 that points to /usr/share/applications/kde4 and add /usr/share/kde4 to XDG_DATA_DIR desktop env. variable at login. ** Description changed: - Using Saucy 13.10, when using KDE applications launched from the Dash, - they do not show up as 'Recently used' neither in the Home or - Applications lenses. + Using Saucy 13.10 and Trusty 14.04, when using KDE applications launched + from the Dash, they do not show up as 'Recently used' neither in the + Home or Applications lenses. Seems zeitgeist or the information presented to it cannot get the path to the KDE application's *.desktop file. Using 'konsole' as a KDE application example: ~ $ /usr/libexec/zeitgeist-fts --log-level=DEBUG ** (zeitgeist-fts:28799): DEBUG: zeitgeist-fts.vala:106: got insertion notification ** (zeitgeist-fts:28799): DEBUG: Indexing event with ID: 6382 ** (zeitgeist-fts:28799): WARNING **: Unable to get info on application://konsole.desktop This happens because 'konsole.desktop' resides in /usr/share/applications/kde4/konsole.desktop If I symlink or copy 'konsole.desktop' to /usr/share/applications/konsole.desktop, then everything works as it should, zeitgeist index's the event correctly and Konsole shows under 'Recently used' for Home and Applications lenses. -- You received this bug notification because you are a member of DX Packages, which is subscribed to zeitgeist in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1251915 Title: Dash + zeitgeist does not log use of KDE applications for 'Recently used' Status in “unity” package in Ubuntu: Confirmed Status in “zeitgeist” package in Ubuntu: New Bug description: Using Saucy 13.10 and Trusty 14.04, when using KDE applications launched from the Dash, they do not show up as 'Recently used' neither in the Home or Applications lenses. Seems zeitgeist or the information presented to it cannot get the path to the KDE application's *.desktop file. Using 'konsole' as a KDE application example: ~ $ /usr/libexec/zeitgeist-fts --log-level=DEBUG ** (zeitgeist-fts:28799): DEBUG: zeitgeist-fts.vala:106: got insertion notification ** (zeitgeist-fts:28799): DEBUG: Indexing event with ID: 6382 ** (zeitgeist-fts:28799): WARNING **: Unable to get info on application://konsole.desktop This happens because 'konsole.desktop' resides in /usr/share/applications/kde4/konsole.desktop If I symlink or copy 'konsole.desktop' to /usr/share/applications/konsole.desktop, then everything works as it should, zeitgeist index's the event correctly and Konsole shows under 'Recently used' for Home and Applications lenses. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1251915/+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 532095] Re: Changing left/right balance in sound-preferences changes the output volume slider when indicator-applet is running
Please create a new bugreport for this issue. -- 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/532095 Title: Changing left/right balance in sound-preferences changes the output volume slider when indicator-applet is running Status in GNOME Media Utilities: Unknown Status in Sound Menu: Fix Released Status in “indicator-sound” package in Ubuntu: Fix Released Status in “indicator-sound” source package in Lucid: Fix Released Bug description: Description of the problem: Moving the balance to the left in sound preferences is also causing the overall volume to become muted. Steps to reproduce: 1. Ensure indicator-applet is running and that the speaker icon is visible within it. 2. Start gnome-terminal . Run speaker-test . 3. Run gnome-volume-control . 4. Select the Output tab. 5. Set the "Output volume" slider to 100%. 6. Drag the Balance slider all the way to the left. Expected result: Sound to only come out of the left speaker. Only the Balance slider should move. Actual result: Balance slider marker jumps back and forth while being dragged to the left. "Output volume" slider also moves to the left (seemingly all the way to 0). No sound is heard from speakers. How reproducible is this: It is reproducible every time. Version information: Ubuntu 10.04 alpha 3 gnome-media 2.29.91-0ubuntu1 pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu10 00:1b.0 Audio device [0403]: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller [8086:27d8] (rev 02) Additional Information: Pressing the right mouse button over the volume indicator applet and going to "Remove from Panel" (so step 1. no longer holds) resolves the issue. This problem does not occur in Fedora 12. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-media/+bug/532095/+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 1074968] Re: Pulseaudio leading to rtkit making hard kernel lock-up
I'm sorry I missed the lspci output. ** Attachment added: "lspci -vv" https://bugs.launchpad.net/ubuntu/+source/unity-lens-music/+bug/1074968/+attachment/4133066/+files/lspci.txt -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-music in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1074968 Title: Pulseaudio leading to rtkit making hard kernel lock-up Status in “unity-lens-music” package in Ubuntu: Confirmed Bug description: After upgrading to 12.10 it takes about five minutes to boot my system while the system load goes crazy and unity occasionally crashes once or twice in the process. Looking at my syslog the only syspicious lines is Nov 4 20:30:58 zelito rtkit-daemon[2524]: The canary thread is apparently starving. Taking action. Nov 4 20:30:58 zelito rtkit-daemon[2524]: Demoting known real-time threads. Nov 4 20:30:58 zelito rtkit-daemon[2524]: Successfully demoted thread 10780 of process 10774 (n/a). Nov 4 20:30:58 zelito rtkit-daemon[2524]: Successfully demoted thread 10779 of process 10774 (n/a). Nov 4 20:30:58 zelito rtkit-daemon[2524]: Successfully demoted thread 10774 of process 10774 (n/a). Nov 4 20:30:58 zelito rtkit-daemon[2524]: Demoted 3 threads. These lines repeat about 20 times and end up with a kernel lock-up Nov 4 20:31:48 zelito rtkit-daemon[2524]: Demoted 3 threads. Nov 4 20:31:49 zelito kernel: [ 373.910966] [ cut here ] Nov 4 20:31:49 zelito kernel: [ 373.910974] WARNING: at /build/buildd/linux-3.5.0/kernel/watchdog.c:242 watchdog_overflow_callback+0x9a/0xc0() Nov 4 20:31:49 zelito kernel: [ 373.910975] Hardware name: NBLBX Nov 4 20:31:49 zelito kernel: [ 373.910976] Watchdog detected hard LOCKUP on cpu 0 Nov 4 20:31:49 zelito kernel: [ 373.910977] Modules linked in: snd_hrtimer pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) dm_crypt coretemp arc4 tpm_infineon psmouse kvm snd_hda_codec_hdmi hp_wmi sparse_keymap snd_hda_codec_realtek uvcvideo videobuf2_core videodev videobuf2_vmalloc videobuf2_memops snd_hda_intel snd_hda_codec snd_hwdep snd_pcm microcode snd_seq_midi snd_rawmidi serio_raw ath9k snd_seq_midi_event i7core_edac snd_seq edac_core mac80211 snd_timer ath9k_common snd_seq_device ath9k_hw ath fglrx(PO) intel_ips lpc_ich cfg80211 mei snd soundcore snd_page_alloc tpm_tis rfcomm bnep parport_pc bluetooth ppdev mac_hid lp parport binfmt_misc vesafb hid_generic usbhid hid r8169 wmi video Nov 4 20:31:49 zelito kernel: [ 373.911020] Pid: 16187, comm: unity-music-dae Tainted: P O 3.5.0-18-generic #29-Ubuntu Nov 4 20:31:49 zelito kernel: [ 373.911021] Call Trace: Nov 4 20:31:49 zelito kernel: [ 373.911023][] warn_slowpath_common+0x7f/0xc0 Nov 4 20:31:49 zelito kernel: [ 373.911031] [] warn_slowpath_fmt+0x46/0x50 Nov 4 20:31:49 zelito kernel: [ 373.911035] [] ? touch_nmi_watchdog+0x80/0x80 Nov 4 20:31:49 zelito kernel: [ 373.911038] [] watchdog_overflow_callback+0x9a/0xc0 Nov 4 20:31:49 zelito kernel: [ 373.911043] [] __perf_event_overflow+0x9d/0x230 Nov 4 20:31:49 zelito kernel: [ 373.911048] [] ? x86_perf_event_set_period+0xd7/0x160 Nov 4 20:31:49 zelito kernel: [ 373.911051] [] perf_event_overflow+0x14/0x20 Nov 4 20:31:49 zelito kernel: [ 373.911054] [] intel_pmu_handle_irq+0x193/0x310 Nov 4 20:31:49 zelito kernel: [ 373.911059] [] perf_event_nmi_handler+0x1d/0x20 Nov 4 20:31:49 zelito kernel: [ 373.911062] [] nmi_handle.isra.0+0x51/0x80 Nov 4 20:31:49 zelito kernel: [ 373.911065] [] do_nmi+0xe0/0x360 Nov 4 20:31:49 zelito kernel: [ 373.911067] [] end_repeat_nmi+0x1a/0x1e Nov 4 20:31:49 zelito kernel: [ 373.911069] <> Nov 4 20:31:49 zelito kernel: [ 373.911071] ---[ end trace 70e4a0a58141ab52 ]--- I'm reporting it against pulseaudio since process 10774 which is the last demoted every time is pulseaudio. It seems not to be the first time this has happened, but the bug does not get a lot of attention: http://ubuntuforums.org/archive/index.php/t-1874171.html https://bugs.freedesktop.org/show_bug.cgi?id=45241 There is even an old (abandoned?) branch which seems to have tried to address this issue: https://code.launchpad.net/~awe/pulseaudio/rtkit-conflicts ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zilvador 10774 F pulseaudio /dev/snd/controlC0: zilvador 10774 F pulseaudio Date: Sun Nov 4 21:01:43 2012 InstallationDate: Installed on 2010-11-13 (721 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) M
[Dx-packages] [Bug 1074968] Re: Pulseaudio leading to rtkit making hard kernel lock-up
Hello there. I am having a but that seems to be related. My computer freezes completely and i have to reboot it. Kernel: Linux fuga 3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:00:20 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attaching relevant syslog messages and lspci output. Thanks. ** Attachment added: "Syslog with relevant output." https://bugs.launchpad.net/ubuntu/+source/unity-lens-music/+bug/1074968/+attachment/4133065/+files/syslog.txt -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-music in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1074968 Title: Pulseaudio leading to rtkit making hard kernel lock-up Status in “unity-lens-music” package in Ubuntu: Confirmed Bug description: After upgrading to 12.10 it takes about five minutes to boot my system while the system load goes crazy and unity occasionally crashes once or twice in the process. Looking at my syslog the only syspicious lines is Nov 4 20:30:58 zelito rtkit-daemon[2524]: The canary thread is apparently starving. Taking action. Nov 4 20:30:58 zelito rtkit-daemon[2524]: Demoting known real-time threads. Nov 4 20:30:58 zelito rtkit-daemon[2524]: Successfully demoted thread 10780 of process 10774 (n/a). Nov 4 20:30:58 zelito rtkit-daemon[2524]: Successfully demoted thread 10779 of process 10774 (n/a). Nov 4 20:30:58 zelito rtkit-daemon[2524]: Successfully demoted thread 10774 of process 10774 (n/a). Nov 4 20:30:58 zelito rtkit-daemon[2524]: Demoted 3 threads. These lines repeat about 20 times and end up with a kernel lock-up Nov 4 20:31:48 zelito rtkit-daemon[2524]: Demoted 3 threads. Nov 4 20:31:49 zelito kernel: [ 373.910966] [ cut here ] Nov 4 20:31:49 zelito kernel: [ 373.910974] WARNING: at /build/buildd/linux-3.5.0/kernel/watchdog.c:242 watchdog_overflow_callback+0x9a/0xc0() Nov 4 20:31:49 zelito kernel: [ 373.910975] Hardware name: NBLBX Nov 4 20:31:49 zelito kernel: [ 373.910976] Watchdog detected hard LOCKUP on cpu 0 Nov 4 20:31:49 zelito kernel: [ 373.910977] Modules linked in: snd_hrtimer pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) dm_crypt coretemp arc4 tpm_infineon psmouse kvm snd_hda_codec_hdmi hp_wmi sparse_keymap snd_hda_codec_realtek uvcvideo videobuf2_core videodev videobuf2_vmalloc videobuf2_memops snd_hda_intel snd_hda_codec snd_hwdep snd_pcm microcode snd_seq_midi snd_rawmidi serio_raw ath9k snd_seq_midi_event i7core_edac snd_seq edac_core mac80211 snd_timer ath9k_common snd_seq_device ath9k_hw ath fglrx(PO) intel_ips lpc_ich cfg80211 mei snd soundcore snd_page_alloc tpm_tis rfcomm bnep parport_pc bluetooth ppdev mac_hid lp parport binfmt_misc vesafb hid_generic usbhid hid r8169 wmi video Nov 4 20:31:49 zelito kernel: [ 373.911020] Pid: 16187, comm: unity-music-dae Tainted: P O 3.5.0-18-generic #29-Ubuntu Nov 4 20:31:49 zelito kernel: [ 373.911021] Call Trace: Nov 4 20:31:49 zelito kernel: [ 373.911023][] warn_slowpath_common+0x7f/0xc0 Nov 4 20:31:49 zelito kernel: [ 373.911031] [] warn_slowpath_fmt+0x46/0x50 Nov 4 20:31:49 zelito kernel: [ 373.911035] [] ? touch_nmi_watchdog+0x80/0x80 Nov 4 20:31:49 zelito kernel: [ 373.911038] [] watchdog_overflow_callback+0x9a/0xc0 Nov 4 20:31:49 zelito kernel: [ 373.911043] [] __perf_event_overflow+0x9d/0x230 Nov 4 20:31:49 zelito kernel: [ 373.911048] [] ? x86_perf_event_set_period+0xd7/0x160 Nov 4 20:31:49 zelito kernel: [ 373.911051] [] perf_event_overflow+0x14/0x20 Nov 4 20:31:49 zelito kernel: [ 373.911054] [] intel_pmu_handle_irq+0x193/0x310 Nov 4 20:31:49 zelito kernel: [ 373.911059] [] perf_event_nmi_handler+0x1d/0x20 Nov 4 20:31:49 zelito kernel: [ 373.911062] [] nmi_handle.isra.0+0x51/0x80 Nov 4 20:31:49 zelito kernel: [ 373.911065] [] do_nmi+0xe0/0x360 Nov 4 20:31:49 zelito kernel: [ 373.911067] [] end_repeat_nmi+0x1a/0x1e Nov 4 20:31:49 zelito kernel: [ 373.911069] <> Nov 4 20:31:49 zelito kernel: [ 373.911071] ---[ end trace 70e4a0a58141ab52 ]--- I'm reporting it against pulseaudio since process 10774 which is the last demoted every time is pulseaudio. It seems not to be the first time this has happened, but the bug does not get a lot of attention: http://ubuntuforums.org/archive/index.php/t-1874171.html https://bugs.freedesktop.org/show_bug.cgi?id=45241 There is even an old (abandoned?) branch which seems to have tried to address this issue: https://code.launchpad.net/~awe/pulseaudio/rtkit-conflicts ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/cont
[Dx-packages] [Bug 1330678] [NEW] indicator-datetime or -session missing ~10% of the time
Public bug reported: Same symptoms as Bug #1239710 which was marked fixed. It happens quite frequently lately in my Ubuntu 14.04 install (fresh install). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140415.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jun 16 23:03:32 2014 InstallationDate: Installed on 2014-04-19 (58 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1330678 Title: indicator-datetime or -session missing ~10% of the time Status in “indicator-datetime” package in Ubuntu: New Bug description: Same symptoms as Bug #1239710 which was marked fixed. It happens quite frequently lately in my Ubuntu 14.04 install (fresh install). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140415.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jun 16 23:03:32 2014 InstallationDate: Installed on 2014-04-19 (58 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1330678/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1239710] Re: indicator-datetime or -session missing ~10% of the time
Symptoms I have are those described here, which is of course why I reported here. Anyway, new report opened according to your indications (#1330678) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1239710 Title: indicator-datetime or -session missing ~10% of the time Status in The Date and Time Indicator: Fix Released Status in The Session Menu: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-session” package in Ubuntu: Fix Released Status in “indicator-datetime” source package in Saucy: Fix Released Status in “indicator-session” source package in Saucy: Fix Released Bug description: Impact: sometime indicator-session or datetime go missing in unity Test Case: start sessions until that happens (or not) Regression potential: the change is a one liner workaround for a glib lock, shouldn't create issue, just check that those indicators keep working as they should --- Indicator-datetime is not showing in the indicator bar today on image 96. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20131011-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.5-0ubuntu2 Architecture: armhf Date: Mon Oct 14 16:00:26 2013 InstallationDate: Installed on 2013-10-14 (0 days ago) InstallationMedia: Ubuntu 13.10 - armhf (20131014) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1239710/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
Re: [Dx-packages] [Cairo-dock-team] [Bug 1242112] Re: Shutdown/restart dialogue is not working if Cairo-Dock and its logout applet are running
ok, thanks for the feedback
I think that's because Unity doesn't try to grab the bus if someone has it.
if they just used something like dbus.service.BusName
('com.canonical.Unity', dbus.SessionBus(), replace_existing=True) it would
work
2014-06-16 14:27 GMT+02:00 Abhishek <1242...@bugs.launchpad.net>:
> The actual location was /usr/lib/x86_64-linux-gnu/cairo-dock/cairo-dock-
> launcher-API-daemon.
>
> But it didn't work on my PC.
> I tried both with and without the login applet and it made no difference.
>
> Although it is working good with the "fix" suggested by Ali Rostami
> @rostami2 in #32.
>
> --
> You received this bug notification because you are a member of Cairo-
> Dock Devs, which is subscribed to Cairo-Dock Core.
> https://bugs.launchpad.net/bugs/1242112
>
> Title:
> Shutdown/restart dialogue is not working if Cairo-Dock and its logout
> applet are running
>
> Status in Cairo-Dock : Core:
> Invalid
> Status in “cairo-dock” package in Ubuntu:
> Invalid
> Status in “unity” package in Ubuntu:
> Confirmed
> Status in “cairo-dock” source package in Trusty:
> Confirmed
> Status in “unity” source package in Trusty:
> Confirmed
> Status in “cairo-dock” source package in Utopic:
> Invalid
> Status in “unity” source package in Utopic:
> Confirmed
>
> Bug description:
> Using latest stable release (3.3.1). Just upgraded to Saucy Salamander
> in Ubuntu. When cairo dock is set to automatically run at boot up the
> options to shutdown/restart do not work from the top menu panel next
> to the clock. When run manually after boot the shutdown/restart works
> fine. The shutdown/restart options do work fine from cairo
> dock/terminal but just mess up the shutdown/restart from the top menu
> panel
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cairo-dock-core/+bug/1242112/+subscriptions
>
> ___
> Mailing list: https://launchpad.net/~cairo-dock-team
> Post to : cairo-dock-t...@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~cairo-dock-team
> More help : https://help.launchpad.net/ListHelp
>
--
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/1242112
Title:
Shutdown/restart dialogue is not working if Cairo-Dock and its logout
applet are running
Status in Cairo-Dock : Core:
Invalid
Status in “cairo-dock” package in Ubuntu:
Invalid
Status in “unity” package in Ubuntu:
Confirmed
Status in “cairo-dock” source package in Trusty:
Confirmed
Status in “unity” source package in Trusty:
Confirmed
Status in “cairo-dock” source package in Utopic:
Invalid
Status in “unity” source package in Utopic:
Confirmed
Bug description:
Using latest stable release (3.3.1). Just upgraded to Saucy Salamander
in Ubuntu. When cairo dock is set to automatically run at boot up the
options to shutdown/restart do not work from the top menu panel next
to the clock. When run manually after boot the shutdown/restart works
fine. The shutdown/restart options do work fine from cairo
dock/terminal but just mess up the shutdown/restart from the top menu
panel
To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo-dock-core/+bug/1242112/+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 1330032] Re: 14.04 Lockscreen 'pops under' when YouTube is full screen
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1330032 Title: 14.04 Lockscreen 'pops under' when YouTube is full screen Status in “unity” package in Ubuntu: New Bug description: I have marked this bug against Unity but may be incorrect. When a Youtube video is fullscreen and left until the lockscreen activates (set at: screen off after 10 minutes, lock after 30, require pwd), on returning to the PC, possibly hours later, the now-ended video image is displayed but no mouse operations are possible. In fact, the lock screen has activated but failed to become uppermost, ie, it has popped under; the screen is locked but that cannot be seen. At this point, to recover operation: hit enter (to clear the password 'buffer' if any keys have been pressed); type the password and hit enter; the mouse is now operational on the Youtube screen, so click the YouTube lower right minimise button (or press escape). This is a security vulnerabilty, as the last full-screen image displayed before lock activation remains visible. Until proven otherwise, the impact may not be restricted to YouTube. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.1+14.04.20140513-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Jun 14 07:44:34 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0112] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device [1849:0112] InstallationDate: Installed on 2014-04-26 (48 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=b496ff7c-0680-4117-9bcc-1bf2bb35be8f ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: Z68 Pro3-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd10/25/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ68Pro3-M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Jun 14 07:30:09 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Laser Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 494 vendor SAM xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ub
[Dx-packages] [Bug 1330037] Re: upower 0.99 transition
ubuntu-system-settings uses at least the device-added/device-removed signals on the D-Bus API. It should be simple to modify it to watch the notify signals instead, and we have autopilot tests to cover this so ensure they keep working. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1330037 Title: upower 0.99 transition Status in “cairo-dock-plug-ins” package in Ubuntu: Fix Committed Status in “gnome-control-center” package in Ubuntu: New Status in “gnome-packagekit” package in Ubuntu: New Status in “gnome-power-manager” package in Ubuntu: New Status in “gnome-session” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: New Status in “gnome-shell” package in Ubuntu: New Status in “indicator-power” package in Ubuntu: Triaged Status in “mate-applets” package in Ubuntu: New Status in “mate-power-manager” package in Ubuntu: New Status in “mate-session-manager” package in Ubuntu: New Status in “mutter” package in Ubuntu: New Status in “powerd” package in Ubuntu: New Status in “python-dbusmock” package in Ubuntu: New Status in “razorqt” package in Ubuntu: New Status in “sugar-0.96” package in Ubuntu: New Status in “sugar-0.98” package in Ubuntu: New Status in “telepathy-mission-control-5” package in Ubuntu: New Status in “tracker” package in Ubuntu: New Status in “ubuntu-system-settings” package in Ubuntu: New Status in “unity-control-center” package in Ubuntu: New Status in “unity-settings-daemon” package in Ubuntu: New Status in “upower” package in Ubuntu: New Status in “xfce4-power-manager” package in Ubuntu: New Status in “xfce4-session” package in Ubuntu: New Status in “xfce4-settings” package in Ubuntu: New Status in “xfce4-systemload-plugin” package in Ubuntu: Fix Committed Status in “wmbattery” package in Debian: New Bug description: upower 0.99 needs uploading for gnome 3.12. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed Some packages are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages wmbattery will probably need removing. If a package only needs a rebuild, mark it fix commited, if something else is needed, in progress. cairo-dock-plug-ins: needs rebuilding #gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Fixed in newest upstream release, needs packaging gnome-power-manager: Fixed in newest upstream release. Merge from debian experimental gnome-session: Done in ppa, needs patches from git or new upstream release gnome-settings-daemon: 3.12 is ready out of the box, however that also requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is mostly working, however had to cherry-pick quite a few patches and may just be better to backport 3.12 power plugin. (considering g-s-d patches will be temporary, but u-s-d not so) kde: no idea (awaiting reply) mate: all mate packages need rebuilding python-dbusmock: lp:1324791 sugar: no idea. telepathy-mission-control-5: Debian has dropped upower support, needs merging wmbattery: needs removal. orphaned upstream/debian and doesn't work with new kernals xfce4-power-manager: Fixed in new upstream release. Needs merging from debian experimental xfce4-session: patch is upstream, needs work to apply with our current patchset xfce4-settings: Patch from upstream in ppa xfce4-systemload-plugin: needs rebuild To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1330037/+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 1329089] Re: g++-4.9 binary incompatibilties with libraries built with g++-4.8
** Changed in: debian Status: Unknown => New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1329089 Title: g++-4.9 binary incompatibilties with libraries built with g++-4.8 Status in “dbus-cpp” package in Ubuntu: In Progress Status in “firefox” package in Ubuntu: New Status in “gcc-4.9” package in Ubuntu: Confirmed Status in “gcc-defaults” package in Ubuntu: Fix Released Status in “location-service” package in Ubuntu: Invalid Status in “mir” package in Ubuntu: New Status in “process-cpp” package in Ubuntu: Invalid Status in “qtbase-opensource-src” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “unity-scope-click” package in Ubuntu: New Status in “unity-scopes-api” package in Ubuntu: New Status in “unity-scopes-shell” package in Ubuntu: New Status in Debian GNU/Linux: New Bug description: The location-service 0.0.3+14.10.20140512-0ubuntu1 package in utopic, when rebuilt against libdbus-cpp3 3.0.0+14.10.20140604-0ubuntu1 (built with gcc-4.8) and with current gcc-defaults (which makes g++-4.9 the default), fails the package build in its test suite. 2/14 Test #2: acceptance_tests ..***Failed 30.54 sec DBus daemon: unix:abstract=/tmp/dbus-HdW1T5UHNB,guid=188551aa5d797b663dade1425398d71b task-0: Started with PID: 13031 task-0: [==] Running 2 tests from 1 test case. task-0: [--] Global test environment set-up. task-0: [--] 2 tests from LocationServiceStandalone task-0: [ RUN ] LocationServiceStandalone.SessionsReceiveUpdatesViaDBus ** (dbus-test-runner:13025): WARNING **: Timing out at maximum wait of 30 seconds. (dbus-test-runner:13025): libdbustest-CRITICAL **: dbus_test_service_run: assertion 'all_tasks(service, all_tasks_finished_helper)' failed task-0: Shutting down DBus daemon: Shutdown This test suite does *not* fail if either dbus-cpp is rebuilt with g++-4.9, or if location-service is built with g++-4.8. This implies a binary compatibility problem for C++ libraries in g++ 4.9, which is critical to resolve. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1329089/+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 1329089] Re: g++-4.9 binary incompatibilties with libraries built with g++-4.8
** Bug watch added: Debian Bug tracker #751780 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751780 ** Also affects: debian via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751780 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1329089 Title: g++-4.9 binary incompatibilties with libraries built with g++-4.8 Status in “dbus-cpp” package in Ubuntu: In Progress Status in “firefox” package in Ubuntu: New Status in “gcc-4.9” package in Ubuntu: Confirmed Status in “gcc-defaults” package in Ubuntu: Fix Released Status in “location-service” package in Ubuntu: Invalid Status in “mir” package in Ubuntu: New Status in “process-cpp” package in Ubuntu: Invalid Status in “qtbase-opensource-src” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “unity-scope-click” package in Ubuntu: New Status in “unity-scopes-api” package in Ubuntu: New Status in “unity-scopes-shell” package in Ubuntu: New Status in Debian GNU/Linux: Unknown Bug description: The location-service 0.0.3+14.10.20140512-0ubuntu1 package in utopic, when rebuilt against libdbus-cpp3 3.0.0+14.10.20140604-0ubuntu1 (built with gcc-4.8) and with current gcc-defaults (which makes g++-4.9 the default), fails the package build in its test suite. 2/14 Test #2: acceptance_tests ..***Failed 30.54 sec DBus daemon: unix:abstract=/tmp/dbus-HdW1T5UHNB,guid=188551aa5d797b663dade1425398d71b task-0: Started with PID: 13031 task-0: [==] Running 2 tests from 1 test case. task-0: [--] Global test environment set-up. task-0: [--] 2 tests from LocationServiceStandalone task-0: [ RUN ] LocationServiceStandalone.SessionsReceiveUpdatesViaDBus ** (dbus-test-runner:13025): WARNING **: Timing out at maximum wait of 30 seconds. (dbus-test-runner:13025): libdbustest-CRITICAL **: dbus_test_service_run: assertion 'all_tasks(service, all_tasks_finished_helper)' failed task-0: Shutting down DBus daemon: Shutdown This test suite does *not* fail if either dbus-cpp is rebuilt with g++-4.9, or if location-service is built with g++-4.8. This implies a binary compatibility problem for C++ libraries in g++ 4.9, which is critical to resolve. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1329089/+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 532095] Re: Changing left/right balance in sound-preferences changes the output volume slider when indicator-applet is running
When I drag the balance so that only the R speaker is outputting sound, the indicator-sound menu volume drops to zero, even though the sound is correctly being played (only on the R speaker). Playing with the sound level in the indicator becomes very glitchy (it always displays a 0 level even though the volume is not 0). This is with 14.04. -- 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/532095 Title: Changing left/right balance in sound-preferences changes the output volume slider when indicator-applet is running Status in GNOME Media Utilities: Unknown Status in Sound Menu: Fix Released Status in “indicator-sound” package in Ubuntu: Fix Released Status in “indicator-sound” source package in Lucid: Fix Released Bug description: Description of the problem: Moving the balance to the left in sound preferences is also causing the overall volume to become muted. Steps to reproduce: 1. Ensure indicator-applet is running and that the speaker icon is visible within it. 2. Start gnome-terminal . Run speaker-test . 3. Run gnome-volume-control . 4. Select the Output tab. 5. Set the "Output volume" slider to 100%. 6. Drag the Balance slider all the way to the left. Expected result: Sound to only come out of the left speaker. Only the Balance slider should move. Actual result: Balance slider marker jumps back and forth while being dragged to the left. "Output volume" slider also moves to the left (seemingly all the way to 0). No sound is heard from speakers. How reproducible is this: It is reproducible every time. Version information: Ubuntu 10.04 alpha 3 gnome-media 2.29.91-0ubuntu1 pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu10 00:1b.0 Audio device [0403]: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller [8086:27d8] (rev 02) Additional Information: Pressing the right mouse button over the volume indicator applet and going to "Remove from Panel" (so step 1. no longer holds) resolves the issue. This problem does not occur in Fedora 12. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-media/+bug/532095/+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 1329089] Re: g++-4.9 binary incompatibilties with libraries built with g++-4.8
** Also affects: unity-scope-click (Ubuntu) Importance: Undecided Status: New ** Also affects: unity-scopes-shell (Ubuntu) Importance: Undecided Status: New ** Also affects: unity-scopes-api (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1329089 Title: g++-4.9 binary incompatibilties with libraries built with g++-4.8 Status in “dbus-cpp” package in Ubuntu: In Progress Status in “firefox” package in Ubuntu: New Status in “gcc-4.9” package in Ubuntu: Confirmed Status in “gcc-defaults” package in Ubuntu: Fix Released Status in “location-service” package in Ubuntu: Invalid Status in “mir” package in Ubuntu: New Status in “process-cpp” package in Ubuntu: Invalid Status in “qtbase-opensource-src” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “unity-scope-click” package in Ubuntu: New Status in “unity-scopes-api” package in Ubuntu: New Status in “unity-scopes-shell” package in Ubuntu: New Bug description: The location-service 0.0.3+14.10.20140512-0ubuntu1 package in utopic, when rebuilt against libdbus-cpp3 3.0.0+14.10.20140604-0ubuntu1 (built with gcc-4.8) and with current gcc-defaults (which makes g++-4.9 the default), fails the package build in its test suite. 2/14 Test #2: acceptance_tests ..***Failed 30.54 sec DBus daemon: unix:abstract=/tmp/dbus-HdW1T5UHNB,guid=188551aa5d797b663dade1425398d71b task-0: Started with PID: 13031 task-0: [==] Running 2 tests from 1 test case. task-0: [--] Global test environment set-up. task-0: [--] 2 tests from LocationServiceStandalone task-0: [ RUN ] LocationServiceStandalone.SessionsReceiveUpdatesViaDBus ** (dbus-test-runner:13025): WARNING **: Timing out at maximum wait of 30 seconds. (dbus-test-runner:13025): libdbustest-CRITICAL **: dbus_test_service_run: assertion 'all_tasks(service, all_tasks_finished_helper)' failed task-0: Shutting down DBus daemon: Shutdown This test suite does *not* fail if either dbus-cpp is rebuilt with g++-4.9, or if location-service is built with g++-4.8. This implies a binary compatibility problem for C++ libraries in g++ 4.9, which is critical to resolve. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1329089/+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 805087] Re: Dash and launcher appear underneath windows
Is happening to me also now for the first time, in Ubuntu 14.04, clean install on release date of Ubuntu 14.04, fully updated. The command "setsid unity" relads Unity and temporarily fixes the issue, but the problem comes back during the session. -- 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/805087 Title: Dash and launcher appear underneath windows Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Oneiric: Fix Released Bug description: main problem: unity launcher and dash always hidden (behind displayed application-windows) more details and symptoms: docky behaves like unity-launcher/dash. press "super" button and type "terminal+enter" (nothing displayed) ... a terminal-window starts/pop-up conclusion: the "input-stack/focus" is o.k. the "windows-display-stack/focus" is wrong more symptoms: After docky-stop and docky-start (restart) the docky-bar shows as "top-level-window" => o.k. This is reproducable with firefox windows by moving/maximise/move to desktop XY. Sometimes other windows (like terminal-window/google-chrome-window) are hiding the launcher/dash/docky too. This problem is reproducable on a T60p with ATI-FireGL video-card. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: unity 3.8.16-0ubuntu1~natty1 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: compiz Date: Sun Jul 3 13:58:33 2011 DistUpgraded: Fresh install DistroCodename: natty DistroVariant: ubuntu DkmsStatus: tp-smapi, 0.40, 2.6.38-10-generic, x86_64: installed tp-smapi, 0.40, 2.6.38-8-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21d1] InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) InstallationMedia_: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) InstallationMedia__: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MachineType: LENOVO 428449G ProcEnviron: LANGUAGE=de_DE:en LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-10-generic root=UUID=be0937c9-8117-4833-a50b-1b5c391c9b69 ro quiet splash i915.semaphores=1 vt.handoff=7 ProcVersionSignature_: Ubuntu 2.6.38-10.46-generic 2.6.38.7 ProcVersionSignature__: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Renderer: Unknown SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Default Device" Option "NoLogo""True" EndSection dmi.bios.date: 04/19/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET42WW (1.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 428449G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8BET42WW(1.22):bd04/19/2011:svnLENOVO:pn428449G:pvrThinkPadW520:rvnLENOVO:rn428449G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 428449G dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2 version.ia32-libs: ia32-libs 20090808ubuntu13 version.libdrm2: libdrm2 2.4.23-1ubuntu6 version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2 version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/805087/+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 1242112] Re: Shutdown/restart dialogue is not working if Cairo-Dock and its logout applet are running
The actual location was /usr/lib/x86_64-linux-gnu/cairo-dock/cairo-dock- launcher-API-daemon. But it didn't work on my PC. I tried both with and without the login applet and it made no difference. Although it is working good with the "fix" suggested by Ali Rostami @rostami2 in #32. -- 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/1242112 Title: Shutdown/restart dialogue is not working if Cairo-Dock and its logout applet are running Status in Cairo-Dock : Core: Invalid Status in “cairo-dock” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Confirmed Status in “cairo-dock” source package in Trusty: Confirmed Status in “unity” source package in Trusty: Confirmed Status in “cairo-dock” source package in Utopic: Invalid Status in “unity” source package in Utopic: Confirmed Bug description: Using latest stable release (3.3.1). Just upgraded to Saucy Salamander in Ubuntu. When cairo dock is set to automatically run at boot up the options to shutdown/restart do not work from the top menu panel next to the clock. When run manually after boot the shutdown/restart works fine. The shutdown/restart options do work fine from cairo dock/terminal but just mess up the shutdown/restart from the top menu panel To manage notifications about this bug go to: https://bugs.launchpad.net/cairo-dock-core/+bug/1242112/+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 1329089] Re: g++-4.9 binary incompatibilties with libraries built with g++-4.8
unorderd_map is not exposed in the API/ABI of the library ** Branch linked: lp:~thomas-voss/dbus-cpp/bump-so-name-and-major- version ** Changed in: dbus-cpp (Ubuntu) Assignee: (unassigned) => Thomas Voß (thomas-voss) ** Changed in: process-cpp (Ubuntu) Status: New => Invalid ** Changed in: dbus-cpp (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1329089 Title: g++-4.9 binary incompatibilties with libraries built with g++-4.8 Status in “dbus-cpp” package in Ubuntu: In Progress Status in “firefox” package in Ubuntu: New Status in “gcc-4.9” package in Ubuntu: Confirmed Status in “gcc-defaults” package in Ubuntu: Fix Released Status in “location-service” package in Ubuntu: Invalid Status in “mir” package in Ubuntu: New Status in “process-cpp” package in Ubuntu: Invalid Status in “qtbase-opensource-src” package in Ubuntu: New Status in “unity” package in Ubuntu: New Bug description: The location-service 0.0.3+14.10.20140512-0ubuntu1 package in utopic, when rebuilt against libdbus-cpp3 3.0.0+14.10.20140604-0ubuntu1 (built with gcc-4.8) and with current gcc-defaults (which makes g++-4.9 the default), fails the package build in its test suite. 2/14 Test #2: acceptance_tests ..***Failed 30.54 sec DBus daemon: unix:abstract=/tmp/dbus-HdW1T5UHNB,guid=188551aa5d797b663dade1425398d71b task-0: Started with PID: 13031 task-0: [==] Running 2 tests from 1 test case. task-0: [--] Global test environment set-up. task-0: [--] 2 tests from LocationServiceStandalone task-0: [ RUN ] LocationServiceStandalone.SessionsReceiveUpdatesViaDBus ** (dbus-test-runner:13025): WARNING **: Timing out at maximum wait of 30 seconds. (dbus-test-runner:13025): libdbustest-CRITICAL **: dbus_test_service_run: assertion 'all_tasks(service, all_tasks_finished_helper)' failed task-0: Shutting down DBus daemon: Shutdown This test suite does *not* fail if either dbus-cpp is rebuilt with g++-4.9, or if location-service is built with g++-4.8. This implies a binary compatibility problem for C++ libraries in g++ 4.9, which is critical to resolve. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1329089/+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 1330037] Re: upower 0.99 transition
** Description changed: upower 0.99 needs uploading for gnome 3.12. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed Some packages are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages wmbattery will probably need removing. If a package only needs a rebuild, mark it fix commited, if something else is needed, in progress. cairo-dock-plug-ins: needs rebuilding #gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Fixed in newest upstream release, needs packaging gnome-power-manager: Fixed in newest upstream release. Merge from debian experimental gnome-session: Done in ppa, needs patches from git or new upstream release - gnome-settings-daemon + gnome-settings-daemon: 3.12 is ready out of the box, however that also requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is mostly working, however had to cherry-pick quite a few patches and may just be better to backport 3.12 power plugin. (considering g-s-d patches will be temporary, but u-s-d not so) kde: no idea (awaiting reply) mate: all mate packages need rebuilding python-dbusmock: lp:1324791 sugar: no idea. telepathy-mission-control-5: Debian has dropped upower support, needs merging wmbattery: needs removal. orphaned upstream/debian and doesn't work with new kernals xfce4-power-manager: Fixed in new upstream release. Needs merging from debian experimental xfce4-session: patch is upstream, needs work to apply with our current patchset xfce4-settings: Patch from upstream in ppa xfce4-systemload-plugin: needs rebuild -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1330037 Title: upower 0.99 transition Status in “cairo-dock-plug-ins” package in Ubuntu: Fix Committed Status in “gnome-control-center” package in Ubuntu: New Status in “gnome-packagekit” package in Ubuntu: New Status in “gnome-power-manager” package in Ubuntu: New Status in “gnome-session” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: New Status in “gnome-shell” package in Ubuntu: New Status in “indicator-power” package in Ubuntu: Triaged Status in “mate-applets” package in Ubuntu: New Status in “mate-power-manager” package in Ubuntu: New Status in “mate-session-manager” package in Ubuntu: New Status in “mutter” package in Ubuntu: New Status in “powerd” package in Ubuntu: New Status in “python-dbusmock” package in Ubuntu: New Status in “razorqt” package in Ubuntu: New Status in “sugar-0.96” package in Ubuntu: New Status in “sugar-0.98” package in Ubuntu: New Status in “telepathy-mission-control-5” package in Ubuntu: New Status in “tracker” package in Ubuntu: New Status in “ubuntu-system-settings” package in Ubuntu: New Status in “unity-control-center” package in Ubuntu: New Status in “unity-settings-daemon” package in Ubuntu: New Status in “upower” package in Ubuntu: New Status in “xfce4-power-manager” package in Ubuntu: New Status in “xfce4-session” package in Ubuntu: New Status in “xfce4-settings” package in Ubuntu: New Status in “xfce4-systemload-plugin” package in Ubuntu: Fix Committed Status in “wmbattery” package in Debian: New Bug description: upower 0.99 needs uploading for gnome 3.12. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed Some packages are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages wmbattery will probably need removing. If a package only needs a rebuild, mark it fix commited, if something else is needed, in progress. cairo-dock-plug-ins: needs rebuilding #gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Fixed in newest upstream release, needs packaging gnome-power-manager: Fixed in newest upstream release. Merge from debian experimental gnome-session: Done in ppa, needs patches from git or new upstream release gnome-settings-daemon: 3.12 is ready out of the box, however that also requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is mostly working, however had to cherry-pick quite a few patches and may just be better to backport 3.12 power plugin. (considering g-s-d patches will be temporary, but u-s-d not so) kde: no idea (awaiting reply) mate: all mate packages need rebuilding python-dbusmock: lp:1324791 sugar: no idea. telepathy-mission-control-5: Debian has dropped upower support, needs merging wmbattery: needs removal. orphaned upstream/debian and doesn't work with new kernals xfce4-power-manager: Fixed in new upstream release. Needs merging from debian experimental xfce4-session: patch is upstream, needs work to apply with our current
[Dx-packages] [Bug 1330037] Re: upower 0.99 transition
** Description changed: upower 0.99 needs uploading for gnome 3.12. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed Some packages are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages wmbattery will probably need removing. If a package only needs a rebuild, mark it fix commited, if something else is needed, in progress. cairo-dock-plug-ins: needs rebuilding #gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Fixed in newest upstream release, needs packaging gnome-power-manager: Fixed in newest upstream release. Merge from debian experimental gnome-session: Done in ppa, needs patches from git or new upstream release gnome-settings-daemon kde: no idea (awaiting reply) mate: all mate packages need rebuilding python-dbusmock: lp:1324791 sugar: no idea. telepathy-mission-control-5: Debian has dropped upower support, needs merging wmbattery: needs removal. orphaned upstream/debian and doesn't work with new kernals xfce4-power-manager: Fixed in new upstream release. Needs merging from debian experimental - xfce4-session: patch is upstream, needs testing + xfce4-session: patch is upstream, needs work to apply with our current patchset xfce4-settings: Patch from upstream in ppa xfce4-systemload-plugin: needs rebuild -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1330037 Title: upower 0.99 transition Status in “cairo-dock-plug-ins” package in Ubuntu: Fix Committed Status in “gnome-control-center” package in Ubuntu: New Status in “gnome-packagekit” package in Ubuntu: New Status in “gnome-power-manager” package in Ubuntu: New Status in “gnome-session” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: New Status in “gnome-shell” package in Ubuntu: New Status in “indicator-power” package in Ubuntu: Triaged Status in “mate-applets” package in Ubuntu: New Status in “mate-power-manager” package in Ubuntu: New Status in “mate-session-manager” package in Ubuntu: New Status in “mutter” package in Ubuntu: New Status in “powerd” package in Ubuntu: New Status in “python-dbusmock” package in Ubuntu: New Status in “razorqt” package in Ubuntu: New Status in “sugar-0.96” package in Ubuntu: New Status in “sugar-0.98” package in Ubuntu: New Status in “telepathy-mission-control-5” package in Ubuntu: New Status in “tracker” package in Ubuntu: New Status in “ubuntu-system-settings” package in Ubuntu: New Status in “unity-control-center” package in Ubuntu: New Status in “unity-settings-daemon” package in Ubuntu: New Status in “upower” package in Ubuntu: New Status in “xfce4-power-manager” package in Ubuntu: New Status in “xfce4-session” package in Ubuntu: New Status in “xfce4-settings” package in Ubuntu: New Status in “xfce4-systemload-plugin” package in Ubuntu: Fix Committed Status in “wmbattery” package in Debian: New Bug description: upower 0.99 needs uploading for gnome 3.12. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed Some packages are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages wmbattery will probably need removing. If a package only needs a rebuild, mark it fix commited, if something else is needed, in progress. cairo-dock-plug-ins: needs rebuilding #gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Fixed in newest upstream release, needs packaging gnome-power-manager: Fixed in newest upstream release. Merge from debian experimental gnome-session: Done in ppa, needs patches from git or new upstream release gnome-settings-daemon kde: no idea (awaiting reply) mate: all mate packages need rebuilding python-dbusmock: lp:1324791 sugar: no idea. telepathy-mission-control-5: Debian has dropped upower support, needs merging wmbattery: needs removal. orphaned upstream/debian and doesn't work with new kernals xfce4-power-manager: Fixed in new upstream release. Needs merging from debian experimental xfce4-session: patch is upstream, needs work to apply with our current patchset xfce4-settings: Patch from upstream in ppa xfce4-systemload-plugin: needs rebuild To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1330037/+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 1330390] Re: Some messages sent from the indicator never appear in the message-app
This is probably a bug in the messaging app. The message is sent, so the messaging menu definitely communicated it back to the app. ** Package changed: indicator-messages (Ubuntu) => telephony-service (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1330390 Title: Some messages sent from the indicator never appear in the message-app Status in “telephony-service” package in Ubuntu: New Bug description: Sometimes, when I answer a message directly from the indicator panel, the message *is* sent, but is never visible in the message-app, even after restarting. I'm sadly at the moment unable to reproduce this bug for sure, but it occurs to me very often so I prefer to file an issue yet, in case others can help or in case in ring a bell to someone. I'm on #79, on a Nexus 4 (I've two phones, and I've seen this on both). I will post again if I have a clearer STR. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1330390/+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 1330390] [NEW] Some messages sent from the indicator never appear in the message-app
Public bug reported: Sometimes, when I answer a message directly from the indicator panel, the message *is* sent, but is never visible in the message-app, even after restarting. I'm sadly at the moment unable to reproduce this bug for sure, but it occurs to me very often so I prefer to file an issue yet, in case others can help or in case in ring a bell to someone. I'm on #79, on a Nexus 4 (I've two phones, and I've seen this on both). I will post again if I have a clearer STR. ** Affects: indicator-messages (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1330390 Title: Some messages sent from the indicator never appear in the message-app Status in “indicator-messages” package in Ubuntu: New Bug description: Sometimes, when I answer a message directly from the indicator panel, the message *is* sent, but is never visible in the message-app, even after restarting. I'm sadly at the moment unable to reproduce this bug for sure, but it occurs to me very often so I prefer to file an issue yet, in case others can help or in case in ring a bell to someone. I'm on #79, on a Nexus 4 (I've two phones, and I've seen this on both). I will post again if I have a clearer STR. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1330390/+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 1327648] Re: Hibernate option disappeared from GUI
Now what? any ideas everyone? -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1327648 Title: Hibernate option disappeared from GUI Status in “indicator-session” package in Ubuntu: New Bug description: I previously enabled hibernation following this SwapFAQ wiki: https://help.ubuntu.com/community/SwapFaq#How_do_I_add_more_swap.3F It was working alright until the hibernate option suddenly decided to disappear. It's no longer in the menu in the top right corner or the options that show up when pressing the power button. sudo pm-hibernate also does not work now! This maybe a cause of some Ubuntu updates, but I am not sure. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: karim 2385 F pulseaudio /dev/snd/controlC0: karim 2385 F pulseaudio CurrentDesktop: Unity Date: Sun Jun 8 02:48:32 2014 HibernationDevice: RESUME=UUID=ef9f1ffe-354c-4678-87b6-23d905b28b19 InstallationDate: Installed on 2014-04-18 (50 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ASUSTeK COMPUTER INC. S551LB ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed root=UUID=5e90a77e-a145-4fab-a643-017dd30261e6 ro resume=UUID=ef9f1ffe-354c-4678-87b6-23d905b28b19 quiet splash acpi=force RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S551LB.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: S551LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS551LB.212:bd04/25/2014:svnASUSTeKCOMPUTERINC.:pnS551LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS551LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: S551LB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:130d] Subsystem: ASUSTeK Computer Inc. Device [1043:130d] InstallationDate: Installed on 2014-04-18 (51 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ASUSTeK COMPUTER INC. S551LB Package: unity 7.2.1+14.04.20140513-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-031500-generic root=UUID=5e90a77e-a145-4fab-a643-017dd30261e6 ro resume=UUID=ef9f1ffe-354c-4678-87b6-23d905b28b19 quiet splash acpi=force vt.handoff=7 Tags: third-party-packages trusty third-party-packages trusty third-party-packages trusty ubuntu compiz-0.9 Uname: Linux 3.15.0-031500-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S551LB.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: S551LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS551LB.212:bd04/25/2014:svnASUSTeKCOMPUTERINC.:pnS551LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS551LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: S551LB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
[Dx-packages] [Bug 1329275] Re: missed call from x-ofono-unknown
Confirmed from screenshot ** Changed in: indicator-messages (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1329275 Title: missed call from x-ofono-unknown Status in “dialer-app” package in Ubuntu: Incomplete Status in “indicator-messages” package in Ubuntu: Confirmed Status in “ofono” package in Ubuntu: Invalid Bug description: I have a missed call which has no name or number. It shows up as from "x-ofono-unknown" in the indicator and dialer-app. The call came from my local taxi company who ring 3 times when the cab is nearly at your house. So there's no number, no contact, it's just an unknown number. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ofono 1.12.bzr6868+14.10.20140513.1-0ubuntu2 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu1 Architecture: armhf Date: Thu Jun 12 11:22:51 2014 InstallationDate: Installed on 2014-06-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140612) SourcePackage: ofono UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1329275/+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
That's unlikely to be related. If you have a reproducible example of a
notification bubble that never disappears, please report it as a
separate bug. Thanks!
--
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 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
I'm not working on Compiz/Unity anymore, but I agree with the bug description and the comments to where compiz/unity headed to today. We had a lot of stability problem at the time, hence this helper to reset unity (which is never used in the session itself to start unity). Stephen's team will handle it. I'm accepting the SRU nomination for trusty as well. ** Also affects: unity (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1324114 Title: Unity kills running compiz, even if it belongs to a different Unity session Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity” source package in Trusty: New Bug description: Hi! I'm trying to get a setup with two different Unity desktop sessions running at the same time. One for the local desktop, one for a remote desktop. This almost works, except that when starting the second Unity session, the compiz process that belongs to the first one is killed because of this code in /usr/bin/unity: # kill a previous compiz if was there (this is a hack as compiz can # sometimes get stuck and not exit on --replace) subprocess.call (["pkill", "-9", "compiz"]) Commenting this line makes both desktop sessions work fine. This kill is far too harsh. If you want to kill compiz, you should make sure that you are killing it in the same DISPLAY as the session that you are about to start, and not just every possible compiz process that is running. Please consider either removing the kill or making it apply only to processes in the same DISPLAY. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1324114/+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
