[Dx-packages] [Bug 1787867] Re: Ubuntu 18.04 LTS bluetooth left discoverable
Just checked in 20.04, with a connected Bluetooth device, and my system is no more automatically discoverable. It's discoverable only when the Bluetooth Settings panel is opened. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1787867 Title: Ubuntu 18.04 LTS bluetooth left discoverable Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: Ubuntu 18.04 LTS, when Bluetooth is on, the computer stays discoverable which opens up unnecessary vulnerability surface. There should be a separate UI switch for discoverability with auto timeout. Leaving bluetooth on (using a Bluetooth mouse) should not leave the computer always discoverable. Current behavior does not match documentation https://help.ubuntu.com/stable/ubuntu-help/bluetooth- visibility.html.en, even without Bluetooth panel open, the computer is still discoverable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1787867/+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 1652789] Re: indicator-datetime-service using high volumes of ram/memory
*** This bug is a duplicate of bug 1642634 *** https://bugs.launchpad.net/bugs/1642634 Happened to me on 18.04 (with Unity). To the point that my system got frozen with indicator-datetime-service consuming 11.5 GB of 16GB RAM. -- 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/1652789 Title: indicator-datetime-service using high volumes of ram/memory Status in indicator-datetime package in Ubuntu: Confirmed Bug description: I have noticed every time my computer boots into Ubuntu, it freezes up with the mouse lagging and then unfreezes. I notice the SSD making huge amounts of read/writes (which I imagine is into virtual memory/swap space). I have to leave the computer for 15 mins or so before coming back to it. I noticed `indicator-datetime-service` was using a lot of RAM in `System Monitor`. So I killed it, and it comes back again each time I kill the process. So I clicked 'Stop' with has seemed to have temporary fixed the problem. Obviously now the correct time is not displayed on the task bar. indicator-datetime: Installed: 15.10+16.10.20160820.1-0ubuntu1 Candidate: 15.10+16.10.20160820.1-0ubuntu1 Version table: *** 15.10+16.10.20160820.1-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status Description:Ubuntu 16.10 Release:16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1652789/+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 1787867] Re: Ubuntu 18.04 LTS bluetooth left discoverable
This is a serious security issue and it's fixed in Gnome upstream. Probably should be backported. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1787867 Title: Ubuntu 18.04 LTS bluetooth left discoverable Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: Ubuntu 18.04 LTS, when Bluetooth is on, the computer stays discoverable which opens up unnecessary vulnerability surface. There should be a separate UI switch for discoverability with auto timeout. Leaving bluetooth on (using a Bluetooth mouse) should not leave the computer always discoverable. Current behavior does not match documentation https://help.ubuntu.com/stable/ubuntu-help/bluetooth- visibility.html.en, even without Bluetooth panel open, the computer is still discoverable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1787867/+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 381416] Re: notify-osd should have a close button
You guys can use the patched NotifyOSD: it's close to the default one, but with very usefull features, like click to close, time/font/color/position configurations. This article: http://www.webupd8.org/2012/11/patched-notifyosd-with-close-on- click.html Cites only until 13.10, but it works fine on 14.04, I use it. -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/381416 Title: notify-osd should have a close button Status in “notify-osd” package in Ubuntu: Won't Fix Bug description: Binary package hint: notify-osd As simple as that. The new notification system works fine, but it really bugs me that I'm forced to wait for those little messages to fade away by themselves. Should I suggest this somewhere else? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/381416/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 627195] Re: Window management - Apps raised from indicators sometimes dont have the focus
Ok, I realized that for some reason, any applications were gaining focus. I fixed following this answer into askubuntu: http://askubuntu.com/questions/128738/when-i-launch-an-app-the-focus- doesnt-move-to-the-opened-app Run in a terminal: gconftool-2 --type=Integer --set /apps/compiz-1/general/screen0/options/focus_prevention_level 0 -- You received this bug notification because you are a member of DX Packages, which is subscribed to libdbusmenu in Ubuntu. Matching subscriptions: dx-packages, dx-packages, dx-packages, dx-packages https://bugs.launchpad.net/bugs/627195 Title: Window management - Apps raised from indicators sometimes dont have the focus Status in Ayatana Design: Fix Committed Status in Compiz: Invalid Status in The Messaging Menu: Fix Released Status in Messaging Menu 13.04 series: Fix Released Status in Sound Menu: Fix Released Status in The Sound Menu 13.04 series: Fix Released Status in DBus Menu: Triaged Status in MPRIS D-Bus Interface Specification: Confirmed Status in Ubuntu One Client: Fix Committed Status in Unity: Invalid Status in “compiz” package in Ubuntu: Invalid Status in “empathy” package in Ubuntu: Fix Released Status in “indicator-messages” package in Ubuntu: Fix Released Status in “indicator-sound” package in Ubuntu: Fix Released Status in “libdbusmenu” package in Ubuntu: New Status in “tomboy” package in Ubuntu: Confirmed Status in “ubuntuone-client” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Status in “indicator-messages” source package in Raring: New Status in “indicator-sound” source package in Raring: New Bug description: Ubuntu 11.10 beta compiz 1:0.9.5.94+bzr2803-0ubuntu5 unity 4.16.0-0ubuntu1 1. open banshee, start a song in it and minimize 2. open another application lets say gnome-terminal 3. click on the sound menu and select banshee What happens banshee icon in the launcher wiggles and banshee main window is not shown What should happen banshee main window should come to focus This is a long standing bug which Ted Gould thinks should be fixed at window manager's level. Some other observations= The problem wont happen 1. if every other app is minimized or 2. Banshee is the only opened app or 3. after opening gnome-terminal, banshee window is closed so that it hides to the SoundMenu and opened again =Comment from Ted Gould= om26er tedg, Hi! any thoughts on the long standing bug 627195 ? Its been there before unity so I guess we can conclude unity not to be responsible tedg om26er, My thought is that window managers should $%#$ get fixed... though I haven't convinced smspillaz of it yet. =The good rule= 3v1n0: Indicators should present the application windows by passing to them the timestamp of the menu item activation event. Unfortunately for indicator-sound, this is not trival as it sounds, since it needs a change to the MPRIS dbus specification. See comment https://bugs.launchpad.net/ayatana-design/+bug/627195/comments/26 for more informations. For what concerns libappindicator based indicators (such as the one used by tomboy), since it's not currently possible in libdbusmenu to pass the event during activation (so that clients will be able to get the proper timestamp using gtk_get_current_event_time), there are two hackish ways: 1. Use the server time to present a window: https://bugzilla.gnome.org/show_bug.cgi?id=688830 2. Get the event timestamp from the dbus-menu linked to the gtk-menus: http://paste.ubuntu.com/5701235/ 3. Qt applications workaround: http://is.gd/WnW9eN Window managers will obey to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/627195/+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 627195] Re: Window management - Apps raised from indicators sometimes dont have the focus
I'm on 14.04, and this still happens, for Rhythmbox, Empathy, etc. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libdbusmenu in Ubuntu. Matching subscriptions: dx-packages, dx-packages, dx-packages, dx-packages https://bugs.launchpad.net/bugs/627195 Title: Window management - Apps raised from indicators sometimes dont have the focus Status in Ayatana Design: Fix Committed Status in Compiz: Invalid Status in The Messaging Menu: Fix Released Status in Messaging Menu 13.04 series: Fix Released Status in Sound Menu: Fix Released Status in The Sound Menu 13.04 series: Fix Released Status in DBus Menu: Triaged Status in MPRIS D-Bus Interface Specification: Confirmed Status in Ubuntu One Client: Fix Committed Status in Unity: Invalid Status in “compiz” package in Ubuntu: Invalid Status in “empathy” package in Ubuntu: Fix Released Status in “indicator-messages” package in Ubuntu: Fix Released Status in “indicator-sound” package in Ubuntu: Fix Released Status in “libdbusmenu” package in Ubuntu: New Status in “tomboy” package in Ubuntu: Confirmed Status in “ubuntuone-client” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Status in “indicator-messages” source package in Raring: New Status in “indicator-sound” source package in Raring: New Bug description: Ubuntu 11.10 beta compiz 1:0.9.5.94+bzr2803-0ubuntu5 unity 4.16.0-0ubuntu1 1. open banshee, start a song in it and minimize 2. open another application lets say gnome-terminal 3. click on the sound menu and select banshee What happens banshee icon in the launcher wiggles and banshee main window is not shown What should happen banshee main window should come to focus This is a long standing bug which Ted Gould thinks should be fixed at window manager's level. Some other observations= The problem wont happen 1. if every other app is minimized or 2. Banshee is the only opened app or 3. after opening gnome-terminal, banshee window is closed so that it hides to the SoundMenu and opened again =Comment from Ted Gould= om26er tedg, Hi! any thoughts on the long standing bug 627195 ? Its been there before unity so I guess we can conclude unity not to be responsible tedg om26er, My thought is that window managers should $%#$ get fixed... though I haven't convinced smspillaz of it yet. =The good rule= 3v1n0: Indicators should present the application windows by passing to them the timestamp of the menu item activation event. Unfortunately for indicator-sound, this is not trival as it sounds, since it needs a change to the MPRIS dbus specification. See comment https://bugs.launchpad.net/ayatana-design/+bug/627195/comments/26 for more informations. For what concerns libappindicator based indicators (such as the one used by tomboy), since it's not currently possible in libdbusmenu to pass the event during activation (so that clients will be able to get the proper timestamp using gtk_get_current_event_time), there are two hackish ways: 1. Use the server time to present a window: https://bugzilla.gnome.org/show_bug.cgi?id=688830 2. Get the event timestamp from the dbus-menu linked to the gtk-menus: http://paste.ubuntu.com/5701235/ 3. Qt applications workaround: http://is.gd/WnW9eN Window managers will obey to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/627195/+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 1305267] Re: notify-osd crashed with signal 5 in _XReply()
*** This bug is a duplicate of bug 1304889 *** https://bugs.launchpad.net/bugs/1304889 I cannot access the other bug report, bug #1304889. -- 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/1305267 Title: notify-osd crashed with signal 5 in _XReply() Status in “notify-osd” package in Ubuntu: New Bug description: It appeared after I started a full screen game on Steam. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: notify-osd 0.9.35+14.04.20140213-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Wed Apr 9 16:19:01 2014 DesktopSession: 'ubuntu' ExecutablePath: /usr/lib/x86_64-linux-gnu/notify-osd GtkTheme: 'Radiance' IconTheme: 'ubuntu-mono-light' InstallationDate: Installed on 2014-03-28 (11 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140323) MachineType: Dell Inc. Dell System XPS L502X ProcCmdline: /usr/lib/x86_64-linux-gnu/notify-osd ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=39eb0c52-5364-4d22-9911-2fcc581e8aa0 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libgl1-mesa-glx 10.1.0-4ubuntu2 libdrm2 2.4.52-1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1 xserver-xorg-video-ati 1:7.3.0-1ubuntu3 Signal: 5 SourcePackage: notify-osd StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: notify-osd crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0MY6GN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0MY6GN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1305267/+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 1302249] Re: Rhythmbox play button not working in indicator-sound applet
Hi Lars, thank you for your fast response!
I can be started normally, even clicking in the rhythmbox entry in the
indicator-sound menu.
MPRIS plugin was not installed. The package rhythmbox-plugins was not
installed.
I installed, and now, all working fine!
So, sorry if I'm wrong, but appears that rhythmbox-plugins package is
missing in default 14.04 install.
--
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/1302249
Title:
Rhythmbox play button not working in indicator-sound applet
Status in “indicator-sound” package in Ubuntu:
Incomplete
Bug description:
In the Rhythmbox music controls at the indicator-sound, after click in
the play button, button displays the loading image, but then
nothing happens.
In its own window, Rhythmbox buttons are working properly.
Steps to reproduce:
1 - Click on indicator sound to expand it;
2 - In indicator sound menu, click in the Play button for Rhythmbox.
Expected result(s):
Last selected music/radio will start to play.
Current result(s):
Button displays the loading image, but nothing happens (see attached image).
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
ActionStates: ({'mute': (true, signature '', [false]), 'phone-settings':
(true, '', []), 'mic-volume': (true, '', [0.2818603515625]), 'scroll': (true,
'i', []), 'desktop-settings': (true, '', []), 'rhythmbox.desktop': (true, '',
[{'running': false, 'state': 'Launching'}]),
'previous.rhythmbox.desktop': (true, '', []), 'volume': (true, 'i',
[0.46783116740198283]), 'root': (true, '', [{'title': 'Sound',
'accessible-desc': 'Volume (71%)', 'icon': ('themed',
['audio-volume-high-panel', 'audio-volume-high', 'audio-volume', 'audio']),
'visible': true}]), 'play.rhythmbox.desktop': (true, '', ['Launching']),
'play-playlist.rhythmbox.desktop': (true, 's', []), 'next.rhythmbox.desktop':
(true, '', [])},)
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 3 20:28:22 2014
InstallationDate: Installed on 2014-03-28 (6 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140323)
SourcePackage: indicator-sound
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1302249/+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 1302249] [NEW] Rhythmbox play button not working in indicator-sound applet
Public bug reported:
In the Rhythmbox music controls at the indicator-sound, after click in
the play button, button displays the loading image, but then nothing
happens.
In its own window, Rhythmbox buttons are working properly.
Steps to reproduce:
1 - Click on indicator sound to expand it;
2 - In indicator sound menu, click in the Play button for Rhythmbox.
Expected result(s):
Last selected music/radio will start to play.
Current result(s):
Button displays the loading image, but nothing happens (see attached image).
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
ActionStates: ({'mute': (true, signature '', [false]), 'phone-settings':
(true, '', []), 'mic-volume': (true, '', [0.2818603515625]), 'scroll': (true,
'i', []), 'desktop-settings': (true, '', []), 'rhythmbox.desktop': (true, '',
[{'running': false, 'state': 'Launching'}]),
'previous.rhythmbox.desktop': (true, '', []), 'volume': (true, 'i',
[0.46783116740198283]), 'root': (true, '', [{'title': 'Sound',
'accessible-desc': 'Volume (71%)', 'icon': ('themed',
['audio-volume-high-panel', 'audio-volume-high', 'audio-volume', 'audio']),
'visible': true}]), 'play.rhythmbox.desktop': (true, '', ['Launching']),
'play-playlist.rhythmbox.desktop': (true, 's', []), 'next.rhythmbox.desktop':
(true, '', [])},)
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 3 20:28:22 2014
InstallationDate: Installed on 2014-03-28 (6 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140323)
SourcePackage: indicator-sound
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: indicator-sound (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug trusty
** Attachment added: Play button in indicator-sound after click
https://bugs.launchpad.net/bugs/1302249/+attachment/4064205/+files/Rhythmbox_play_not_working_at_indicator-sound.png
--
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/1302249
Title:
Rhythmbox play button not working in indicator-sound applet
Status in “indicator-sound” package in Ubuntu:
New
Bug description:
In the Rhythmbox music controls at the indicator-sound, after click in
the play button, button displays the loading image, but then
nothing happens.
In its own window, Rhythmbox buttons are working properly.
Steps to reproduce:
1 - Click on indicator sound to expand it;
2 - In indicator sound menu, click in the Play button for Rhythmbox.
Expected result(s):
Last selected music/radio will start to play.
Current result(s):
Button displays the loading image, but nothing happens (see attached image).
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
ActionStates: ({'mute': (true, signature '', [false]), 'phone-settings':
(true, '', []), 'mic-volume': (true, '', [0.2818603515625]), 'scroll': (true,
'i', []), 'desktop-settings': (true, '', []), 'rhythmbox.desktop': (true, '',
[{'running': false, 'state': 'Launching'}]),
'previous.rhythmbox.desktop': (true, '', []), 'volume': (true, 'i',
[0.46783116740198283]), 'root': (true, '', [{'title': 'Sound',
'accessible-desc': 'Volume (71%)', 'icon': ('themed',
['audio-volume-high-panel', 'audio-volume-high', 'audio-volume', 'audio']),
'visible': true}]), 'play.rhythmbox.desktop': (true, '', ['Launching']),
'play-playlist.rhythmbox.desktop': (true, 's', []), 'next.rhythmbox.desktop':
(true, '', [])},)
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 3 20:28:22 2014
InstallationDate: Installed on 2014-03-28 (6 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140323)
SourcePackage: indicator-sound
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1302249/+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 1302249] Re: Rhythmbox play button not working in indicator-sound applet
Hm, I just realized now that all 3 buttons are not working (previous,
play, next).
--
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/1302249
Title:
Rhythmbox play button not working in indicator-sound applet
Status in “indicator-sound” package in Ubuntu:
New
Bug description:
In the Rhythmbox music controls at the indicator-sound, after click in
the play button, button displays the loading image, but then
nothing happens.
In its own window, Rhythmbox buttons are working properly.
Steps to reproduce:
1 - Click on indicator sound to expand it;
2 - In indicator sound menu, click in the Play button for Rhythmbox.
Expected result(s):
Last selected music/radio will start to play.
Current result(s):
Button displays the loading image, but nothing happens (see attached image).
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
ActionStates: ({'mute': (true, signature '', [false]), 'phone-settings':
(true, '', []), 'mic-volume': (true, '', [0.2818603515625]), 'scroll': (true,
'i', []), 'desktop-settings': (true, '', []), 'rhythmbox.desktop': (true, '',
[{'running': false, 'state': 'Launching'}]),
'previous.rhythmbox.desktop': (true, '', []), 'volume': (true, 'i',
[0.46783116740198283]), 'root': (true, '', [{'title': 'Sound',
'accessible-desc': 'Volume (71%)', 'icon': ('themed',
['audio-volume-high-panel', 'audio-volume-high', 'audio-volume', 'audio']),
'visible': true}]), 'play.rhythmbox.desktop': (true, '', ['Launching']),
'play-playlist.rhythmbox.desktop': (true, 's', []), 'next.rhythmbox.desktop':
(true, '', [])},)
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 3 20:28:22 2014
InstallationDate: Installed on 2014-03-28 (6 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140323)
SourcePackage: indicator-sound
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1302249/+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 1243069] Re: Launcher does not reveal when autohide is on
Appears to be the same as https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1268167 -- 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/1243069 Title: Launcher does not reveal when autohide is on Status in “unity” package in Ubuntu: Confirmed Bug description: I use a dual screen setup and autohide with the launcher on the left. After the 13.10 upgrade the autohide feature is broken : - The launcher does not reveal anymore with the mouse (it reveals with the keyboard shortcut). - I can't move the mouse to the second monitor : the cursor is stuck on the right border of the left monitor. If I move the mouse top right and move fast I can pass to the second monitor) I tried different settings in ccsm in vain. I could not find any similar issues report except this one : http://askubuntu.com/questions/363205/13-10-auto-hidelauncher-breaks- multiple-monitor-setup ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,compiztoolbox,regex,place,move,gnomecompat,imgpng,grid,resize,mousepoll,session,vpswitch,snap,animation,workarounds,expo,wall,ezoom,staticswitcher,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Oct 22 09:19:09 2013 DistUpgraded: 2013-10-18 12:53:39,653 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: virtualbox, 4.2.16, 3.11.0-12-generic, x86_64: installed virtualbox, 4.2.16, 3.8.0-31-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 6350 [1028:2126] InstallationDate: Installed on 2011-06-08 (866 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MachineType: Dell Inc. OptiPlex 990 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=c4c9bb00-bea9-47e8-9175-82937fe761ef ro radeon.agpmode=-1 quiet splash i915.semaphores=1 vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-10-18 (3 days ago) dmi.bios.date: 11/24/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/24/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 3:1.12.4+git20121105-makson1~ppa2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 2:2.7.3+git20120928~quantal2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 2:6.14.6+git20120928~quantal1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 3:2.20.8+git20120928~quantal2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 2:1.0.2+git20120928~quantal1 xserver.bootTime: Mon Oct 21 15:19:46 2013 xserver.configfile: /etc/X11/xorg.conf xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputUSB Optical MouseMOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 3:1.12.4+git20121105-makson1~ppa2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1243069/+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 1268167] Re: No Autohide Launcher Bar Mouse Reveal on Secondary Monitor
Same here. After the last update, launch is not revealing on second monitor (placed at right). 12.04 LTS, X64, Intel Graphics. -- 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/1268167 Title: No Autohide Launcher Bar Mouse Reveal on Secondary Monitor Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: Since several updates performed on 1/8/2014, I am no longer able to reveal the launcher bar on my secondary (right) display with the mouse auto-reveal function. Under display settings, both monitors are set to display a launcher bar. Auto reveal works fine with the mouse on the primary (left) monitor. The sticky edge works fine with the secondary (right) monitor, but no auto reveal for the launcher bar. I can bring up the secondary (right) monitor launcher bar with the super key and alt+f1. So far I've reverted to Nvidia 3.04 drivers from 3.19 by purging from terminal and re-installing to no avail, and now back to 3.19 and it's still not working. Ubuntu 12.04.4 LTS 32-bit AMD Athlon 64x2 Dual Core Processor 6000+ Nvidia GT630 PCIe 2GB RAM Any outputs you'd like from me, please let me know. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1268167/+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 331369] Re: regression vs. notification-daemon: positioning when multiple screens are available
I decided to give a try to Unity, in 2013, on LTS (12.04). And, while fighting to change font size, themes, I found this bug while working with second monitor attached to desktop. I.e., my configured as primary is the HDMI monitor at left. And the notifications are displayed in the secondary (at right) monitor. Any patch for Precise? I know there is a dconf workaround. But this is really the Unity way? For anything I want to customize/fix, install a third party program? -- 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/331369 Title: regression vs. notification-daemon: positioning when multiple screens are available Status in Ayatana Design: Fix Released Status in Notify OSD: Fix Released Status in Notify OSD trunk series: Fix Released Status in “notify-osd” package in Ubuntu: Fix Released Status in “notify-osd” source package in Natty: Fix Released Status in “notify-osd” source package in Oneiric: Fix Released Status in “notify-osd” source package in Jaunty: Won't Fix Bug description: Binary package hint: notify-osd I use nvidia TwinView (one X desktop across two monitors). notification-daemon was apparently sensitive to this (presumably through Xinerama info?) and would popup on my primary screen. notify-osd seems to be unaware of this, and appears in the top right of the overall viewport, which is on my secondary screen, and less visible, so less useful as a notifier. --- https://wiki.ubuntu.com/NotifyOSD#position: If any windows are open, a bubble should appear on whichever display contains the largest fraction of the area of the focused window at the moment the bubble starts appearing. If no windows are open, a bubble should appear on whichever display the first pointer is on at the moment the bubble starts appearing. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/331369/+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
