[Bug 1096951] [NEW] libpurple does not implement AIM groupchat exit
Public bug reported: The AIM protocol sends clients a contact list, which may include groups of which the user is a member. Once an AIM user enters a groupchat, the user must leave the groupchat before the groupchat will be permanently removed from the user's contact list. Leaving a groupchat is not implied by closing a groupchat window, deleting a groupchat from the contacts list, or signing out of the client. I was able to delete a groupchat or delete and block a groupchat, and the groupchat disappeared from my contacts list. However, once I signed out and signed back in, the groupchat returned. I was able to permanently expunge the groupchat only by signing into the AIM Express web client (http://www.aim.com/products/express/) and leaving the groupchat from that app. My experience with this bug was using Empathy via telepathy-haze as the front-end, but the following appears to be the upstream bug report regarding the Pidgin front-end: https://developer.pidgin.im/ticket/12734 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libpurple0 1:2.10.6-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Mon Jan 7 11:45:21 2013 InstallationDate: Installed on 2011-08-29 (497 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MarkForUpload: True SourcePackage: pidgin UpgradeStatus: Upgraded to quantal on 2012-10-22 (76 days ago) ** Affects: pidgin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096951 Title: libpurple does not implement AIM groupchat exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1096951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1075975] [NEW] ufw needs hooks to execute commands pre/post firewall startup/shutdown
Public bug reported: Some commands related to iptables must be executed in conjunction with starting/stopping a firewall in order for the correct operation of the firewall. UFW currently does not provide the ability to run those commands without hacking its source code. My specific use case: I must deploy machines to my customer, on which I must block certain countries' IP ranges. The most efficient method of doing this is to use the ipset utilities. I can insert ipset-matching firewall rules via iptables commands in the /etc/ufw/before.rules script. However, this will fail if I do not first execute ipset commands to define the respective ipsets. My current workaround choices are: 1) Write a separate init script to define ipsets and configure it to execute before ufw. I don't like this option because user error could cause this script to not execute first, and then ufw would not start properly. 2) Hack ufw init scripts (/lib/ufw/ufw-init-functions) to make the necessary calls before actually starting the firewall. This is the option I went with. However, I don't like it, because now I must maintain a forked version of ufw and make sure that it is preferred over the official version. My proposal: Implement 4 hook shell script files that are called by UFW's init scripts pre-start, post-start, pre-stop, and post-stop. These should be stored in /etc/ufw/ and marked as config files so that they are not overwritten on ufw upgrade. They should default to being empty scripts, and sysadmins could then choose to populate them with whatever commands are necessary for their individual deployments. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: ufw 0.33-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Wed Nov 7 09:13:03 2012 InstallationDate: Installed on 2011-08-29 (435 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MarkForUpload: True PackageArchitecture: all SourcePackage: ufw UpgradeStatus: Upgraded to quantal on 2012-10-22 (15 days ago) ** Affects: ufw (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075975 Title: ufw needs hooks to execute commands pre/post firewall startup/shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1075975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 492658] Re: Rhythmbox MusicBrainz cover art search engine fails to load available cover art
This bug appears to have been fixed in 12.10. I was able to use MusicBrainz to get album info and cover art for my CDs. The fix appears not to have been the application of my patch, but a general refactoring of the module. Unless someone else can confirm that this bug still exists in 12.10 (which I seriously doubt) then this bug should be closed. ** Changed in: rhythmbox (Ubuntu) Status: In Progress = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/492658 Title: Rhythmbox MusicBrainz cover art search engine fails to load available cover art To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/492658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1071345] Re: empathy contacts list compact mode is missing in 3.6
I did not confirm my own bug report. If you look at the history, Launchpad Janitor confirmed the report (comment 2) because multiple people said that it affected them. Then, in comment 3, qwazi referenced another bug, and in comment 4, Bilal Shahid responded with a workaround for the unrelated bug, and marked this bug as incomplete, questioning if the workaround mitigated this bug. Of course it did not, because it is not related to this bug. I corrected this and reset the status to Confirmed, which is what it was before comment 4 was (IMHO erroneously) posted. Please reset the bug report to Confirmed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1071345 Title: empathy contacts list compact mode is missing in 3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1071345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1071345] Re: empathy contacts list compact mode is missing in 3.6
I am the original reporter of this bug. Please do not hijack this bug report. This bug report deals with the disappearance of the compact mode for the contacts list. The ability to sort by status is also missing, but it is *not* the subject of this bug report. Please file a separate report for that. The ability to show/hide offline contacts does nothing to ameliorate the lack of the compact mode contacts list. ** Changed in: empathy (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1071345 Title: empathy contacts list compact mode is missing in 3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1071345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1071345] [NEW] empathy contacts list compact mode is missing in 3.6
Public bug reported: Prior to upgrading to quantal, Empathy had a compact mode for the contacts list. This would show each contact on a single line that was just tall enough to display the contact's username. This way, I would be able to use my high resolution monitor to view all of my online contacts simultaneously. Under Empathy 3.6 on quantal, the option for a compact mode disappeared and each contact in the list takes about 3 times the vertical space needed to display the contact's username. Now even with my high resolution montor, I can only view about 1/3 of my online contacts at a time. Please bring back the compact mode. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: empathy 3.6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Thu Oct 25 10:43:27 2012 InstallationDate: Installed on 2011-08-29 (422 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MarkForUpload: True SourcePackage: empathy UpgradeStatus: Upgraded to quantal on 2012-10-22 (2 days ago) ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1071345 Title: empathy contacts list compact mode is missing in 3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1071345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070879] [NEW] Calling service networking restart kills unity
Public bug reported: Note: I am not sure if this is an issue with unity, with compiz, or with some other component such as dbus, or if it is multiple bugs. At work I use a bridged network interface (br0) over eth0 on my laptop to seamlessly connect my laptop and its virtual machines to the corporate network. As Network Manager cannot handle bridged connections, I am forced to use the old /etc/network/interfaces file to configure the bridge. (Note that I removed all network manager entries that reference eth0 before creating the bridge.) This setup worked fine in 12.04 and earlier versions. I was able to reconfigure the bridge (when necessary) and restart it using the command line without issue using those releases. When my computer is booted with the bridged configuration, 12.10 uses the bridge to connect to the network without issue. The problem occurs only when I restart networking. In 12.10, issuing the command sudo service networking restart or sudo /etc/init.d/networking restart causes Unity to instantly and completely die. The compiz window manager decorations disappear and do not restart, keyboard shortcuts do not work, services such as bluetooth become unresponsive. Existing windows remained (without window manager decoration) on the screen, but appeared hung. With a USB mouse I was able to move the mouse and right click to open menus, but they were unresponsive to clicks. I was unable to do anything in Unity to correct the situation. I was able to switch to a virtual terminal (Ctrl+Alt+F1) and log in to the command line. From there I was able to restart the computer. I have been able to replicate this consistently. I am attaching my .xsession-errors file. Note that the entries up to and including line 110 were made before issuing the network restart command. Entries after 110 resulted from issuing the command. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.8.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,copytex,compiztoolbox,decor,move,gnomecompat,vpswitch,dbus,place,regex,imgsvg,mousepoll,snap,imgpng,resize,wall,animation,unitymtgrabhandles,session,resizeinfo,fade,expo,workarounds,ezoom,scale,unityshell] Date: Wed Oct 24 10:31:16 2012 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to quantal on 2012-10-22 (1 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity ** Attachment added: My .xsession-errors file. Lines after 110 were the result of restarting networking. https://bugs.launchpad.net/bugs/1070879/+attachment/3411800/+files/SAVEDxsession-errors -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070879 Title: Calling service networking restart kills unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1070879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070879] Re: Calling service networking restart kills unity
** Attachment added: This is my /etc/network/interfaces file declaring the bridge. https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1070879/+attachment/3411804/+files/__etc__network__interfaces -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070879 Title: Calling service networking restart kills unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1070879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070879] Re: Calling service networking restart kills unity
** Description changed: + Note: I am not sure if this is an issue with unity, with compiz, or with + some other component such as dbus, or if it is multiple bugs. + At work I use a bridged network interface (br0) over eth0 on my laptop to seamlessly connect my laptop and its virtual machines to the corporate network. As Network Manager cannot handle bridged connections, I am forced to use the old /etc/network/interfaces file to configure the bridge. (Note that I removed all network manager entries that reference eth0 before creating the bridge.) This setup worked fine in 12.04 and earlier versions. I was able to reconfigure the bridge (when necessary) and restart it using the command - line without issue. + line without issue using those releases. When my computer is booted + with the bridged configuration, 12.10 uses the bridge to connect to the + network without issue. The problem occurs only when I restart + networking. In 12.10, issuing the command sudo service networking restart or sudo /etc/init.d/networking restart causes Unity to instantly and completely die. The compiz window manager decorations disappear and do not - restart, the keyboard becomes unresponsive, services such as bluetooth + restart, keyboard shortcuts do not work, services such as bluetooth become unresponsive. Existing windows remained (without window manager decoration) on the screen, but appeared hung. With a USB mouse I was able to move the mouse and right click to open menus, but they were unresponsive to clicks. I was unable to do anything in Unity to correct the situation. I was able to switch to a virtual terminal (Ctrl+Alt+F1) and log in to the command line. From there I was able to restart the computer. I have been able to replicate this consistently. I am attaching my .xsession-errors file. Note that the entries up to and including line 110 were made before issuing the network restart command. Entries after 110 resulted from issuing the command. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.8.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,copytex,compiztoolbox,decor,move,gnomecompat,vpswitch,dbus,place,regex,imgsvg,mousepoll,snap,imgpng,resize,wall,animation,unitymtgrabhandles,session,resizeinfo,fade,expo,workarounds,ezoom,scale,unityshell] Date: Wed Oct 24 10:31:16 2012 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to quantal on 2012-10-22 (1 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070879 Title: Calling service networking restart kills unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1070879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070879] Re: Calling service networking restart kills unity
I did a test on another machine that has a more vanilla configuration with eth0 configured through Network Manager. The only thing in /etc/network/interfaces was the loopback stuff that is installed there by default. I issued sudo service networking restart and the same thing happened: Unity essentially died and I had to switch to a virtual terminal to restart the computer. This result demonstrates that it is the networking script (or some hook program called by it) that is the problem, and not any particular network configuration. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070879 Title: Calling service networking restart kills unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1070879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070879] Re: Calling service networking restart kills unity
While logged into Unit, I ran the commands: ifdown lo ifup lo The system continues to work correctly. Therefore, it's not merely restarting the loopback device that causes Unity to crash, it's some other part of the networking restart script. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070879 Title: Calling service networking restart kills unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1070879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 841409] Re: GEdit is the only choice as Calendar application in Default Applications dialog
For those who do not wish to wait for a patch to fix this, you can add the following line to the [Default Applications] section of the file $HOME/.local/share/applications/mimeapps.list: text/calendar=thunderbird.desktop I also added the same line to the [Added Associations] section, but I am not sure if that is necessary. Once you do this, Thunderbird becomes a recommended application for that file type, and shows up in the list. If the Google Calendar app, or any other calendar app has a .desktop file, you can do the same for that app. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/841409 Title: GEdit is the only choice as Calendar application in Default Applications dialog To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/841409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 779639] Re: gnome screensaver activation is hindered by unobscure routine
I have marked this bug invalid because the bug exists (might still exist) in a package that is no longer used by default in current Ubuntu releases. ** Changed in: gnome-screensaver (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779639 Title: gnome screensaver activation is hindered by unobscure routine To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/779639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 241206] Re: Gnome Screensaver does not activate reliably
I have marked this bug invalid because the bug exists (might still exist) in a package that is no longer used by default in current Ubuntu releases. ** Changed in: gnome-screensaver (Ubuntu) Status: In Progress = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/241206 Title: Gnome Screensaver does not activate reliably To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/241206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 850309] Re: libvirt fails to autostart VM attached to a bridged port
Can we get an official word that this is a Won't fix for Natty and below? I would like to retire this bug from my active bugs tracker, but I cannot make the change to Won't fix and I would rather not set it to Invalid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/850309 Title: libvirt fails to autostart VM attached to a bridged port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/850309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 779639] Re: gnome screensaver activation is hindered by unobscure routine
Let me rephrase: the mechanism by which this bug exists is no longer in current releases of Ubuntu by default (Unity does its own thing to activate screen blanking/lockout), and it is crystal clear that in older releases of Ubuntu, this is a Won't fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779639 Title: gnome screensaver activation is hindered by unobscure routine To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/779639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666108] Re: empathy does not display AOL OSCAR too-frequent-login ban message to users
This bug still exists in 12.10 (Quetzalcoatl, or whatever the crazy code name is this time) and I presume 12.04 as well. Now it says authentication failure after logging in and out too many times. Still no indication to the user that they should wait a while before trying to log in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/666108 Title: empathy does not display AOL OSCAR too-frequent-login ban message to users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/666108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184508] Re: Gnome Window Selector loses windows
The bug did occur on 10.04 with the desktop visual effects turned on. However, unless Ubuntu devs plan to go back and fix an obscure bug on a non-default desktop widget that is no longer even available the current UI environment, I would ask that they mark this as Won't fix so that I (and others) can retire this bug from my active bug tracker. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/184508 Title: Gnome Window Selector loses windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/184508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 444420] Re: USB logitech bluetooth doesn't work
Can we set the Lucid target to Invalid or Won't fix since it seems like there will be no more action on this bug? That way this bug can be closed and retired from people's active bug trackers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/20 Title: USB logitech bluetooth doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/20/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 850309] Re: libvirt fails to autostart VM attached to a bridged port
After upgrading to 11.10, I no longer see this bug. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/850309 Title: libvirt fails to autostart VM attached to a bridged port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/850309/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 779639] Re: gnome screensaver activation is hindered by unobscure routine
Since Ubuntu 11.10 effectively eliminated gnome-screensaver, I no longer see this bug in that release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779639 Title: gnome screensaver activation is hindered by unobscure routine To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/779639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 850309] Re: libvirt fails to autostart VM attached to a bridged port
After upgrading to 11.10, I no longer see this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/850309 Title: libvirt fails to autostart VM attached to a bridged port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/850309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146296] Re: Cannot bind buttons to Button8 etc.
This bug appears to be fixed as of 11.10 (probably much earlier, but that is the version I am using now), perhaps it should be closed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/146296 Title: Cannot bind buttons to Button8 etc. To manage notifications about this bug go to: https://bugs.launchpad.net/compizconfig-settings-manager/+bug/146296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 869301] Re: Banshee track slider shows total play time instead of position in current track
I have looked into it more and the problem does not appear when playing OGG Vorbis files, but does when playing FLAC files. GStreamer appears to have plugins to parse files to get things like padding. It has such a plugin for Vorbis, which I think, is why Banshee shows the correct track position for Vorbis files, even when in gapless mode. GStreamer has no plugin for parsing FLAC files (or at least, I did not see one) so I think that is why it has no way of knowing, in gapless mode, when one FLAC ends and another begins. I have included a link to the upstream GStreamer bug report. ** Summary changed: - Banshee track slider displaying incorrectly, incorrect time + Banshee track slider shows total play time instead of position in current track ** Bug watch added: GNOME Bug Tracker #664433 https://bugzilla.gnome.org/show_bug.cgi?id=664433 ** Also affects: gst-plugins via https://bugzilla.gnome.org/show_bug.cgi?id=664433 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/869301 Title: Banshee track slider shows total play time instead of position in current track To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/869301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 869301] Re: Banshee track slider displaying incorrectly, incorrect time
I instrumented ConnectedSeekSlider.cs with debugging statements and found that the PlayerEngine is not resetting its Position attribute (the number of milliseconds into the track it is) when it rolls over to a new track. If the new track is shorter than the current position (the sum of previous positions) then the slider will show only the position, not the time on the current track. If you move the slider, this forces the PlayerEngine to reset its Position and thus the slider behaves properly again, for a time. I am currently looking into why the PlayerEngine is not resetting its position on track change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/869301 Title: Banshee track slider displaying incorrectly, incorrect time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/869301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 869301] Re: Banshee track slider displaying incorrectly, incorrect time
I have confirmed that gapless playback is responsible for this bug. Disabling gapless playback in the preferences will make the slider work correctly again. This will cause a brief (1 sec) pause between tracks, so depending on your albums, this may be no big deal (modern music) or it may be very jarring (e.g., orchestral albums, Pink Floyd, etc.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/869301 Title: Banshee track slider displaying incorrectly, incorrect time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/869301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 779639] Re: gnome screensaver activation is hindered by unobscure routine
Truth be told, I never understood what Shih-Yuan Lee's patch did or how it addressed this bug. My patch is much simpler, but it only addresses a symptom of the bug (the unobscure routine deactivating the screensaver) rather than the underlying bug (why is the obscure/unobscure routine called at every invocation of the screensaver?). Of course, a patch of a particularly annoying symptom is still better than no patch for the underlying cause... To apply the patch, you must use the Debian package building system to rebuild the gnome-screensaver package. It's very easy to apply if you are familiar with that system, but it's beyond the scope of this bug tracker to provide directions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779639 Title: gnome screensaver activation is hindered by unobscure routine To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/779639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 850309] Re: libvirt fails to autostart VM attached to a bridged port
The temporary workaround from comment 10 did not work for me. No matter how big I made the sleep, it did not wait. Also, it broke `stop libvirt-bin`. Attached is a modified init file that seems to work. ** Attachment added: /etc/init/libvirt-bin.conf https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+attachment/2414363/+files/libvirt-bin.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/850309 Title: libvirt fails to autostart VM attached to a bridged port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/850309/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 850309] Re: libvirt fails to autostart VM attached to a bridged port
The temporary workaround from comment 10 did not work for me. No matter how big I made the sleep, it did not wait. Also, it broke `stop libvirt-bin`. Attached is a modified init file that seems to work. ** Attachment added: /etc/init/libvirt-bin.conf https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+attachment/2414363/+files/libvirt-bin.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/850309 Title: libvirt fails to autostart VM attached to a bridged port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/850309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 850309] Re: libvirt fails to autostart VM attached to a bridged port
Attached /etc/init/libvirt-bin.conf as requested. ** Attachment added: /etc/init/libvirt-bin.conf https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+attachment/2408314/+files/libvirt-bin.conf ** Changed in: libvirt (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/850309 Title: libvirt fails to autostart VM attached to a bridged port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 850309] Re: libvirt fails to autostart VM attached to a bridged port
Attached /etc/init/libvirt-bin.conf as requested. ** Attachment added: /etc/init/libvirt-bin.conf https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+attachment/2408314/+files/libvirt-bin.conf ** Changed in: libvirt (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/850309 Title: libvirt fails to autostart VM attached to a bridged port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 850309] [NEW] libvirt fails to autostart VM attached to a bridged port
Public bug reported: I have assigned my eth0 as the sole bridge port on bridge device br0. I have my VMs set to connect to br0. When I manually start them, everything works well. I have set one VM to autostart on bootup, but it fails. I found bug #495394, particularly comment 49 to be what I see happening. In that bug, the person who wrote comment 49 was told to file a new bug report, but it seems he did not do that. I am now filing the report. Attached is a syslog snippet that shows autostart failing. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libvirt-bin 0.8.8-1ubuntu6.5 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 Architecture: amd64 Date: Wed Sep 14 15:24:19 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty running-unity -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/850309 Title: libvirt fails to autostart VM attached to a bridged port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 850309] Re: libvirt fails to autostart VM attached to a bridged port
** Attachment added: Syslog snippet showing where autostarting fails https://bugs.launchpad.net/bugs/850309/+attachment/2404270/+files/libvirt-syslog.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/850309 Title: libvirt fails to autostart VM attached to a bridged port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 850309] Re: libvirt fails to autostart VM attached to a bridged port
I used a simple non-lvm setup. Vanilla partitioning, no mucking about. ** Attachment added: My vanilla fstab https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+attachment/2404273/+files/fstab -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/850309 Title: libvirt fails to autostart VM attached to a bridged port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 850309] Re: libvirt fails to autostart VM attached to a bridged port
I created a bridge interface br0 and assigned eth0 as the only real bridge port. The VMs are configured to connect to this port as well. ** Attachment added: /etc/network/interfaces https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+attachment/2404309/+files/interfaces -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/850309 Title: libvirt fails to autostart VM attached to a bridged port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 850309] Re: libvirt fails to autostart VM attached to a bridged port
This is the virtual machine config. It works fine when I start it manually. I believe that the problem is that libvirt starts it before br0 has come up, but I thought that bug was supposed to have been fixed. ** Attachment added: My VM config https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+attachment/2404332/+files/vsubuntu1-clone1.xml -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/850309 Title: libvirt fails to autostart VM attached to a bridged port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 850309] [NEW] libvirt fails to autostart VM attached to a bridged port
Public bug reported: I have assigned my eth0 as the sole bridge port on bridge device br0. I have my VMs set to connect to br0. When I manually start them, everything works well. I have set one VM to autostart on bootup, but it fails. I found bug #495394, particularly comment 49 to be what I see happening. In that bug, the person who wrote comment 49 was told to file a new bug report, but it seems he did not do that. I am now filing the report. Attached is a syslog snippet that shows autostart failing. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libvirt-bin 0.8.8-1ubuntu6.5 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 Architecture: amd64 Date: Wed Sep 14 15:24:19 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/850309 Title: libvirt fails to autostart VM attached to a bridged port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 850309] Re: libvirt fails to autostart VM attached to a bridged port
** Attachment added: Syslog snippet showing where autostarting fails https://bugs.launchpad.net/bugs/850309/+attachment/2404270/+files/libvirt-syslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/850309 Title: libvirt fails to autostart VM attached to a bridged port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 850309] Re: libvirt fails to autostart VM attached to a bridged port
I used a simple non-lvm setup. Vanilla partitioning, no mucking about. ** Attachment added: My vanilla fstab https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+attachment/2404273/+files/fstab -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/850309 Title: libvirt fails to autostart VM attached to a bridged port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 850309] Re: libvirt fails to autostart VM attached to a bridged port
I created a bridge interface br0 and assigned eth0 as the only real bridge port. The VMs are configured to connect to this port as well. ** Attachment added: /etc/network/interfaces https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+attachment/2404309/+files/interfaces -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/850309 Title: libvirt fails to autostart VM attached to a bridged port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 850309] Re: libvirt fails to autostart VM attached to a bridged port
This is the virtual machine config. It works fine when I start it manually. I believe that the problem is that libvirt starts it before br0 has come up, but I thought that bug was supposed to have been fixed. ** Attachment added: My VM config https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+attachment/2404332/+files/vsubuntu1-clone1.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/850309 Title: libvirt fails to autostart VM attached to a bridged port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 779639] Re: gnome screensaver activation is hindered by unobscure routine
Jason: Do you have a screensaver password that activates immediately when the screensaver activates? If you do, then instead of deactivating the screensaver, it will simply pop up the password dialog box. In either case, did you apply my patch listed in the Gnome Bugzilla linked to this bug, and rebuild the screensaver? http://bugzilla-attachments.gnome.org/attachment.cgi?id=187479 That patch *does* fix this bug. I cannot understand why the patch was not accepted, or at least, why no Gnome or Ubuntu developers even commented on it. It is a relatively simple explanation and solution that any developer should be able to confirm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779639 Title: gnome screensaver activation is hindered by unobscure routine To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/779639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 779639] Re: gnome screensaver activation is hindered by unobscure routine
This is the same patch as the one I submitted to the Gnome Bugzilla. Since no one ever commented on it there or here, I am explicitly submitting it here for consideration. ** Patch added: gnome-screensaver-fix-fade-to-black-back-to-desktop-bug.patch https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/779639/+attachment/2350750/+files/gnome-screensaver-fix-fade-to-black-back-to-desktop-bug.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779639 Title: gnome screensaver activation is hindered by unobscure routine To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/779639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666108] Re: empathy does not display AOL OSCAR too-frequent-login ban message to users
This bug still very much exists using the latest Natty as of today. I just got myself banned for 10 minutes testing it. I must assume that no one who looks that this bug report has an AOL IM account, because anyone with such an account can easily trigger this bug by logging out in about 15 or so times in rapid succession. After doing so, the contacts list shows that the account is offline due to network error and offers the little button to retry the connection. If you look into the telepathy-haze logs, as I pointed out when I submitted the bug, you get the snippet of XML sent by the OSCAR server saying that you have logged on too many times in rapid succession. ** Changed in: empathy (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/666108 Title: empathy does not display AOL OSCAR too-frequent-login ban message to users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/666108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666117] Re: empathy (AOL IM protocol) does not handle messages to the logged in user from the same user (from another host) correctly
This bug appears to be partially mooted, because apparently now Empathy will not show the logged-in user in the buddy list. To be clear, my user name is still listed in my AIM buddy list, it's just that Empathy filters it out of the displayed contacts. Pidgin and Adium still show your logged-in user in your buddy list (assuming you have added yourself to your own buddy list), and if you send an IM from one of those clients, while you are also logged on (with non-away status) to an Empathy client, your Empathy client will not show the message. ** Changed in: empathy (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/666117 Title: empathy (AOL IM protocol) does not handle messages to the logged in user from the same user (from another host) correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/666117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 722690] Re: error: /usr/lib/mozilla/plugins/libvlcplugin.so: undefined symbol: NPP_Initialize
I adapted Rafał's patch from Gentoo to Ubuntu. Note, it does a full copy of the old npunix.c to a new npunix.cpp with the changes included: this was the only way I could make the patch so that dpkg-buildpackage would apply it without failing. To apply, put it into vlc-1.1.9/debian/patches/ and add a line containing the patch name to vlc-1.1.9/debian/patches/series. Then you should be able to use dpkg-buildpackage like usual. ** Patch added: patch to fix vlc mozplugin crash https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/722690/+attachment/2136816/+files/900_fix_vlc_mozplugin_crash.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/722690 Title: error: /usr/lib/mozilla/plugins/libvlcplugin.so: undefined symbol: NPP_Initialize -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574634] Re: Can't edit dhcp range
I have run into the same thing. Apparently, you cannot edit a DHCP configuration. However, you can delete it and create a new one. First you have to click Stop Network (for me, a red circle with an X inside), then Delete Network (a red crossed circle), then the green plus sign to add a network. The wizard steps you through creating a new DHCP setup, and this new network's default settings are more sensible, with the dynamic range from 128-254. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/574634 Title: Can't edit dhcp range -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184508] Re: Gnome Window Selector loses windows
I can't mark it won't fix, but that's basically what this bug is. With the transition to either Gnome Shell or Unity, this bug is mooted. I don't think anyone is still doing any hard hacking on the old Gnome 2 stuff like this, so for anyone stuck on Gnome 2, I guess they will have to live with it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/184508 Title: Gnome Window Selector loses windows -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 597057] Re: on panel restart, indicator-applet-session does not show the status (AKA: me) menu
This bug appears mooted with the transition to Unity (or Gnome Shell). ** Changed in: indicator-me (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/597057 Title: on panel restart, indicator-applet-session does not show the status (AKA: me) menu -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 385461] Re: firefox source does not compile on first try
This bug is very old, and it's no longer the case, so closing. ** Changed in: firefox-3.0 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/385461 Title: firefox source does not compile on first try -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 779639] [NEW] gnome screensaver activation is hindered by unobscure routine
Public bug reported: Binary package hint: gnome-screensaver The problem occurs in Natty, using the Unity desktop. I have not tried the old-style desktop to see if it also affects that. https://bugzilla.gnome.org/show_bug.cgi?id=649755 I have reported upstream a bug in Gnome Screensaver that is preventing my screensaver from activating during session timeout. The symptom is that the session times out, the screen fades to black, and then immediately returns to the desktop. The symptoms are similar to Bug #241206 and Bug #363635, but the cause is different than those bugs. Summary of upstream bug report: The problem is caused in gs-manager.c by the function window_obscured_cb. This function is called when the screensaver window is obscured (i.e., when fast user switching swaps to another VT) or unobscured (i.e., switching back to the VT). In addition to attempting to disable or re-enable the screensaver animation, when the screensaver is unobscured the callback automatically makes a request to unlock the screen. This saves the user from having to press a key or wave their mouse around to bring up the unlock dialog. My problem is that, for reasons I do not understand, my screensaver thinks, every time it activates due to session timeout, that its window is obscured briefly. window_obscured_cb is called twice in rapid succession, once for obscure, then again for unobscure. Because I do not use the screensaver lock feature, this means that, on the unobscure call, the screensaver is deactivated. Thus, my screensaver will never activate due to a session timeout. I have verified that the obscured window event is the reason for the screensaver deactivation using the debugging output. I have attached a patch in the upstram bug report that fixes the problem by removing the line that calls the screensaver unlock automatically as a result of an unobscure event. ** Affects: gnome-screensaver Importance: Unknown Status: Unknown ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: gnome-screensaver + + The problem occurs in Natty, using the Unity desktop. I have not tried + the old-style desktop to see if it also affects that. https://bugzilla.gnome.org/show_bug.cgi?id=649755 I have reported upstream a bug in Gnome Screensaver that is preventing my screensaver from activating during session timeout. The symptom is that the session times out, the screen fades to black, and then immediately returns to the desktop. The symptoms are similar to Bug #241206 and Bug #363635, but the cause is different than those bugs. Summary of upstream bug report: The problem is caused in gs-manager.c by the function window_obscured_cb. This function is called when the screensaver window is obscured (i.e., when fast user switching swaps to another VT) or unobscured (i.e., switching back to the VT). In addition to attempting to disable or re-enable the screensaver animation, when the screensaver is unobscured the callback automatically makes a request to unlock the screen. This saves the user from having to press a key or wave their mouse around to bring up the unlock dialog. My problem is that, for reasons I do not understand, my screensaver thinks, every time it activates due to session timeout, that its window is obscured briefly. window_obscured_cb is called twice in rapid succession, once for obscure, then again for unobscure. Because I do not use the screensaver lock feature, this means that, on the unobscure call, the screensaver is deactivated. Thus, my screensaver will never activate due to a session timeout. I have verified that the obscured window event is the reason for the screensaver deactivation using the debugging output. I have attached a patch in the upstram bug report that fixes the problem by removing the line that calls the screensaver unlock automatically as a result of an unobscure event. ** Bug watch added: GNOME Bug Tracker #649755 https://bugzilla.gnome.org/show_bug.cgi?id=649755 ** Also affects: gnome-screensaver via https://bugzilla.gnome.org/show_bug.cgi?id=649755 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779639 Title: gnome screensaver activation is hindered by unobscure routine -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 241206] Re: Gnome Screensaver does not activate reliably
The regression I reported in comment #25 is actually a new bug. See Bug #779639 for details. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/241206 Title: Gnome Screensaver does not activate reliably -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 241206] Re: Gnome Screensaver does not activate reliably
Under Maverick, I experienced no problems with the stock screensaver. Unfortunately, with Natty I have experienced a regression to the fade to black and then back to desktop issue whenever I use caffeine to disable the screensaver, and then sometime later use it to re-enable the screensaver. I am reapplying my patch from comment 21, and will report whether that fixes the situation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/241206 Title: Gnome Screensaver does not activate reliably -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 241206] Re: Gnome Screensaver does not activate reliably
** Changed in: gnome-session Assignee: Robert Lange (rcl24) = (unassigned) ** Changed in: gnome-screensaver (Ubuntu) Assignee: Robert Lange (rcl24) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/241206 Title: Gnome Screensaver does not activate reliably -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 241206] Re: Gnome Screensaver does not activate reliably
Stuart, the gnome-screensaver code watches the idle_delay gconf variable, and any change to it triggers reset_idle_watch. Your changing that variable is a work-around for those who are not comfortable with patching code and recompiling, but it's not a solution. The precise cause of this bug has been diagnosed in my comments 16, 17, and 21, and patches have been provided to fix it. Unfortunately, it appears that my patches were never accepted by Ubuntu or upstream. What graphics subsystem you have is irrelevant to this bug. That said, I am now using the stock gnome-session and gnome-screensaver packages in Maverick, and I have yet to experience the issue. If you are still getting the fade to black and then back to desktop issue on Maverick, I recommend applying the patch in comment 21. It's only a few lines long (so it still should be valid on Maverick) and will take care of most of the problem. My patches from comments 16 and 17 are much larger (and therefore, much more likely to have broken between Lucid and Maverick) and only are needed if you regularly disable the screensaver, wait for a while, and then re-enable it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/241206 Title: Gnome Screensaver does not activate reliably -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666108] [NEW] empathy does not display AOL OSCAR too-frequent-login ban message to users
Public bug reported: Binary package hint: empathy The AOL Instant Messenger protocol bars users from logging in if they log in and out of their accounts too many times in rapid succession. When this happens in other clients, such as Adium (for OSX) and Slick (for Symbian), a message is popped up to the user informing them that they are barred from logging in, and letting them know not to try again for 10 minutes, or the length of the ban will be increased. From empathy, I logged in and out of my account a bunch of times, forgetting about this rule. Eventually, empathy just stopped signing me in, and only gave a cryptic 'Network error' message. I kept hitting the button to try again, without success or further explanation. Then, I remembered the too-frequent-logins rule, and I tried signing in from another client. I discovered that I had triggered the ban. Empathy had provided no information about this ban to me. UBUNTU RELEASE: 10.10 with latest updates as of 2010-10-24 empathy VERSION: 2.32.0-0ubuntu2 telepathy-haze VERSION: 0.4.0-1 REPRODUCIBLE: Always STEPS TO REPRODUCE: Sign in and out of an AIM account a bunch of times in rapid succession. WHAT HAPPENS: Eventually, empathy stops signing you in, but provides no error message except 'Network error'. If you enable EMPATHY_DEBUG and check the empathy logs, you only see an error message about a network error and another error message for not being able to get an 'owner' for the account name. If you enable HAZE_DEBUG and look in the haze logs, you see the text of the ban message from AOL's OSCAR servers. WHAT SHOULD HAPPEN: Telepathy-haze needs to communicate the relevant reason for the login failure to Empathy, and Empathy needs to display that to the user. I am not sure where the message is getting lost (that is, is telepathy-haze not sending it properly, or is empathy not displaying it). This problem needs to get fixed, otherwise our users may accidentally trigger lengthy bans by trying to reconnect after the ban message has been sent from AOL's servers. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: empathy 2.32.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sun Oct 24 22:31:23 2010 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) ProcEnviron: LC_COLLATE=C PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: empathy ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- empathy does not display AOL OSCAR too-frequent-login ban message to users https://bugs.launchpad.net/bugs/666108 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666108] Re: empathy does not display AOL OSCAR too-frequent-login ban message to users
-- empathy does not display AOL OSCAR too-frequent-login ban message to users https://bugs.launchpad.net/bugs/666108 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666108] Re: empathy does not display AOL OSCAR too-frequent-login ban message to users
I have attached a relevant snippet from my telepathy-haze.log. My username has been changed to 'myacct1' for privacy. ** Attachment added: telepathy-haze log snippet showing ban text https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/666108/+attachment/1710022/+files/telepathy-haze-ban.log -- empathy does not display AOL OSCAR too-frequent-login ban message to users https://bugs.launchpad.net/bugs/666108 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666117] [NEW] empathy (AOL IM protocol) does not handle messages to the logged in user from the same user (from another host) correctly
Public bug reported: Binary package hint: empathy Okay, bear with me, this one is complicated ;-) Let your username be 'fubar' and let your two computers be called 'host1' and 'host2'. Login to AOL IM as fubar on host1. Add fubar to your buddy list. Notice that you can open a chat window to fubar and type in messages, which once sent, show up in both the sending and receiving portions of the chat window (because, of course, you are sending a message to yourself). Now also login to AIM as fubar on host2. This perfectly allowable, and the AOL IM protocol says that, if a user is logged in more than once, then messages sent to that user are sent to every non-away client, or to all clients, if all are away. STEPS TO REPRODUCE: Log in to fubar on both host1 and host2. Make sure that both hosts are not away and will not go auto-away. On host1, make sure that there are no chat windows open for fubar. On host2, send a message to fubar. WHAT SHOULD HAPPEN: On host1, a message should appear to fubar from fubar. (Note: this works correctly, if a chat window for fubar was already open on host1 when the message came in. For this bug to be triggered, host1 cannot have a chat window open for fubar.) On host2, the message should appear in both the send and receive portions of the chat window. Everything else on host1 and host2 should work normally. WHAT ACTUALLY HAPPENS: 1. On host1, nothing visible happens. There is no indication of any kind that a message has been received; no chat window pops up, and the indicator and notification area icons do nothing. However, if you check the chat transcript for fubar, you will see that the message has been silently received. 2. Also on host1, from the moment the message was silently received, until you either logout and log back in, or until you restart empathy, you will not be able to summon a chat window for fubar. Looking in the empathy debug messages, it seems that empathy never gets a reply from telepathy-haze when it tries to open a chat window channel. (Nothing bad happens on host2.) CURRENT STATUS: Right now, I am trying to collect minimal empathy and telepathy-haze logs that show the series of events involved in receiving messages, receiving messages that are also from the logged-in user, and opening chat windows before and after triggering this bug. I suspect that the actual problem is in telepathy-haze, but until I know more, I am filing this under empathy, as that is the more user-visible project. (Speculation: Now that I am thinking about it, I wonder if telepathy- haze assumes that a message from the logged-in user must correspond to an existing window channel, and gets into a funky state if this is not the case.) JUSTIFICATION FOR SETUP: Some people may wonder why I would add myself to my own buddy list. The answer is that I log in to the same account from work, home, and abroad, so that I don't bother my friends with multiple accounts at which to contact me. I also send messages to myself from one location, so I know that I will see them on my desktop when I get to the other location. I have used this as a quick and easy way to leave myself to-dos for many years now. Also, it's a quick way of checking whether your connection is hung, because sending a message from yourself to yourself on the same client still has to pass through the AOL servers, and will not do so, if your connection is hung. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: empathy 2.32.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sun Oct 24 23:03:38 2010 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) ProcEnviron: LC_COLLATE=C PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: empathy ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- empathy (AOL IM protocol) does not handle messages to the logged in user from the same user (from another host) correctly https://bugs.launchpad.net/bugs/666117 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666117] Re: empathy (AOL IM protocol) does not handle messages to the logged in user from the same user (from another host) correctly
-- empathy (AOL IM protocol) does not handle messages to the logged in user from the same user (from another host) correctly https://bugs.launchpad.net/bugs/666117 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 492658] Re: Rhythmbox MusicBrainz cover art search engine fails to load available cover art
It looks like the patch was not properly applied, or else, your initial copy of /usr/lib/rhythmbox/plugins/artdisplay/MusicBrainzCoverArtSearch.py was different than mine. Can you attach your copy, as well as the initial copy, if it still exists? -- Rhythmbox MusicBrainz cover art search engine fails to load available cover art https://bugs.launchpad.net/bugs/492658 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 492658] Re: Rhythmbox MusicBrainz cover art search engine fails to load available cover art
All, The above solution patch is formatted to be dropped into the Ubuntu source package and recompiled into the binary package. However, since it's just a Python file, you can just apply it directly to the /usr/lib/rhythmbox/plugins/artdisplay/MusicBrainzCoverArtSearch.py file without building a new binary package, using the following commands: cd /usr/lib/rhythmbox/plugins/artdisplay/ sudo patch -p4 /full/path/to/solution_file - Medor: Whatever editor you used to copy-paste the diff contents into your file, it messed up the indentation by replacing all tabs with the wrong number of spaces. Python is a whitespace-sensitive language, and for better or worse, the authors of this file have used tabs to indent, so we need to fix your indentation. To fix it, you need to make sure there is exactly 1 tab before the first line of the fix, and exactly 2 tabs before the second line. These need to be actual tabs, not spaces, so you will have to make sure your editor is not set to replace tabs with spaces. (If you use Emacs (with a default .emacs configuration file; I can't vouch for all customizations...), the first line of the MusicBrainzCoverArtSearch.py file will auto-configure Emac's tab-mode for this file for you. I don't know what other editors respect that line.) -- Rhythmbox MusicBrainz cover art search engine fails to load available cover art https://bugs.launchpad.net/bugs/492658 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 492658] Re: Rhythmbox MusicBrainz cover art search engine fails to load available cover art
Medor, we need more information to determine if this error is really related to the patch. Please quit Rhythmbox (making sure it's not still running in the background) and from the command line, run: rhythmbox --debug rhythmbox-debug.txt 21 Start playing one album/song that causes the error, wait for the error to appear, and then quit rhythmbox and wait for the command line instance to return to the prompt. Then, please attach the file for us to look at. -- Rhythmbox MusicBrainz cover art search engine fails to load available cover art https://bugs.launchpad.net/bugs/492658 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 658471] Re: udev fails to call hid2hci for Logitech USB Bluetooth adapter
Ugh, an update to udev (without this patch) just overwrote my fix from comment #6. Note to people using my fix: until my patch, or something equivalent, gets released, first copy /lib/udev/rules.d/70-hid2hci.rules to /etc/udev/rules.d/ and then apply the patch to that copy. Files in /etc/udev/rules.d/ are protected from updates. -- udev fails to call hid2hci for Logitech USB Bluetooth adapter https://bugs.launchpad.net/bugs/658471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 492658] Re: Rhythmbox MusicBrainz cover art search engine fails to load available cover art
Yeah, lannatwin, Last.FM is another search option that is automatically tried, if you are logged in to it. However, my patch fixes things even for those who do not have a Last.FM account. -- Rhythmbox MusicBrainz cover art search engine fails to load available cover art https://bugs.launchpad.net/bugs/492658 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 492658] Re: Rhythmbox not load cover arts
** Changed in: rhythmbox (Ubuntu) Status: Incomplete = Opinion ** Changed in: rhythmbox (Ubuntu) Status: Opinion = In Progress -- Rhythmbox MusicBrainz cover art search engine fails to load available cover art https://bugs.launchpad.net/bugs/492658 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 492658] Re: Rhythmbox not load cover arts
This bug is a simple omission in a search handler. In MusicBrainzCoverArtSearch.py, someone forgot to implement the method get_result_meta. It's just a stub that does nothing important, but the overall search algorithm expects it to be there, and when it's not, it returns a runtime error rather than trying the found URL. Basically, this would be a compile error if it were a C program, but since it's Python, it becomes a cryptic runtime error. Attached is a patch which fixes this bug. It implements a stub for get_result_meta, which causes the MusicBrainz search handler to happily download the album art. ** Patch added: add a missing sub method that allows the MusicBrainz search handler to return results https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/492658/+attachment/1701026/+files/95_rhythmbox-0.13.1__plugins__artdisplay__artdisplay__MusicBrainzCoverArtSearch.py.patch ** Summary changed: - Rhythmbox not load cover arts + Rhythmbox MusicBrainz cover art search engine fails to load available cover art -- Rhythmbox MusicBrainz cover art search engine fails to load available cover art https://bugs.launchpad.net/bugs/492658 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 658471] Re: udev fails to call hid2hci for Logitech USB Bluetooth adapter
My problem with the KERNEL==hidraw* line was that it would not match for my adapter (even though my adapter appeared as a hidraw device). Was the problem encountered in bug #550288 that it would not match for KERNEL==hiddev*|hidraw* but it would match for KERNEL==hidraw*? I ask this, because I tried adding a separate copy of the line for hiddev*|hidraw* before the original hidraw* line. This patch still fixes my problem. Is it possible to ask someone who had the problem with the | operator in bug #550288 to try out this new patch? If I am right, then it should work for them as well. ** Patch added: new patch for 70-hid2hci.rules, supercedes last patch https://bugs.launchpad.net/ubuntu/+source/udev/+bug/658471/+attachment/1692788/+files/__lib__udev__rules.d__70-hid2hci.rules.diff -- udev fails to call hid2hci for Logitech USB Bluetooth adapter https://bugs.launchpad.net/bugs/658471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 658471] [NEW] udev fails to call hid2hci for Logitech USB Bluetooth adapter
Public bug reported:
Binary package hint: udev
This bug is related to Bug #20, but I was told to file it as a new
bug here.
Here are the rules I have for Logitech USB Bluetooth dongles in
/lib/udev/rules.d/70-hid2hci.rules:
# Logitech devices
KERNEL==hiddev*, ATTRS{idVendor}==046d, ATTRS{idProduct}==c70[35e], \
RUN+=hid2hci --method=logitech-hid --devpath=%p
KERNEL==hidraw*, ATTRS{idVendor}==046d,
ATTRS{idProduct}==c70[4abc]|c71[34bc], \
RUN+=hid2hci --method=logitech-hid --devpath=%p
This is an upgrade from Lucid (on which hid2hci was called) to Maverick
(at which point, hid2hci was no longer called).
As seen in lsusb output, my adapter should have matched the second line:
Bus 001 Device 006: ID 046d:c70c Logitech, Inc. BT Mini-Receiver (HID proxy
mode)
Bus 001 Device 005: ID 046d:c70b Logitech, Inc. BT Mini-Receiver (HID proxy
mode)
Bus 001 Device 003: ID 046d:0b02 Logitech, Inc. BT Mini-Receiver (HID proxy
mode)
I removed the KERNEL condition from the rules file:
# Logitech devices
ATTRS{idVendor}==046d, ATTRS{idProduct}==c70[35e], \
RUN+=hid2hci --method=logitech-hid --devpath=%p
ATTRS{idVendor}==046d, ATTRS{idProduct}==c70[4abc]|c71[34bc], \
RUN+=hid2hci --method=logitech-hid --devpath=%p
I restarted udev and re-inserted the adapter. While everything seems to
work correctly now, I am told that this is wrong because it could
somehow overmatch something.
Attached is the output of `udevadm monitor` when udev is running with
the original Maverick 70-hid2hci.rules file and the adapter is inserted.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: udev 162-2
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon Oct 11 11:16:01 2010
InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429)
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic
root=UUID=b8e395c0-dc79-4ec7-8100-3d7b33afb2e4 ro quiet splash
ProcEnviron:
LC_COLLATE=C
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: udev
dmi.bios.date: 02/24/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0703
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P6X58D PREMIUM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0703:bd02/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58DPREMIUM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
** Affects: udev (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug maverick
--
udev fails to call hid2hci for Logitech USB Bluetooth adapter
https://bugs.launchpad.net/bugs/658471
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 658471] Re: udev fails to call hid2hci for Logitech USB Bluetooth adapter
** Attachment added: `udevadm monitor` output with original udev rules https://bugs.launchpad.net/bugs/658471/+attachment/1685145/+files/udevadm_monitor.log ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/658471/+attachment/1685146/+files/BootDmesg.txt ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/658471/+attachment/1685147/+files/CurrentDmesg.txt ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/658471/+attachment/1685148/+files/Dependencies.txt ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/658471/+attachment/1685149/+files/Lspci.txt ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/658471/+attachment/1685150/+files/Lsusb.txt ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/658471/+attachment/1685151/+files/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/658471/+attachment/1685152/+files/ProcInterrupts.txt ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/658471/+attachment/1685153/+files/ProcModules.txt ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/658471/+attachment/1685154/+files/UdevDb.txt ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/658471/+attachment/1685155/+files/UdevLog.txt -- udev fails to call hid2hci for Logitech USB Bluetooth adapter https://bugs.launchpad.net/bugs/658471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 658471] Re: udev fails to call hid2hci for Logitech USB Bluetooth adapter
I made the following change in /lib/udev/rules.d/70-hid2hci.rules and
now it works.
KERNEL==hidraw*, ATTRS{idVendor}==046d,
ATTRS{idProduct}==c70[4abc]|c71[34bc], \
changed to:
KERNEL==hiddev*|hidraw*, ATTRS{idVendor}==046d,
ATTRS{idProduct}==c70[4abc]|c71[34bc], \
I don't understand this, because it seems from the `udevadm monitor`
output that my adapter (c70[bc]) really was a hidraw device. However,
the results speak for themselves and this change has fixed the problem
for me, while maintaining a fairly tight KERNEL condition. I suspect
that if other people's Logitech USB Bluetooth dongles are still not
working with this patch, then they may want to make a similar change to
the previous line in 70-hid2hci.rules, but I am not touching that for
now, because it does not affect me.
I remember a while ago, there was only one Logitech rule, and it used
the | (or) operator for the KERNEL condition, just like my fix does.
Does anyone know why they were separated into different rules? Because,
obviously, they were under-matching by doing so.
I have attached a proper diff patch for those who are interested.
** Patch added: fix to udev hid2hci rules for Logitech USB Bluetooth dongles
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/658471/+attachment/1685188/+files/__lib__udev__rules.d__70-hid2hci.rules.diff
** Changed in: udev (Ubuntu)
Status: New = In Progress
--
udev fails to call hid2hci for Logitech USB Bluetooth adapter
https://bugs.launchpad.net/bugs/658471
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 444420] Re: USB logitech bluetooth doesn't work
Okay, point taken. For people who have Maverick and stumble across this bug looking for help, I have opened a new Bug #658471 that basically continues this bug and documents the fix that I have found works. -- USB logitech bluetooth doesn't work https://bugs.launchpad.net/bugs/20 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544242] Re: [PATCH] Empathy should allow users to toggle auto-away mode on/off
An update: Apparently Empathy has switched from using GConf as its settings storage to GSettings and its corresponding dconf. On the first start of Empathy after doing the dist-upgrade, the Empathy settings are imported once from GConf into dconf, and then GConf is no longer used for empathy. Likewise, I imagine that for new 10.10 installs, there never will be a GConf empathy entry. As such, you cannot use gconf-editor to change the autoaway setting. Instead, you must install the package dconf-tools and use dconf-editor, which works very much like gconf-editor. -- [PATCH] Empathy should allow users to toggle auto-away mode on/off https://bugs.launchpad.net/bugs/544242 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 444420] Re: USB logitech bluetooth doesn't work
I have the Logitech Bluetooth dongle and I just upgraded from a working Lucid install to Maverick. Bluetooth broke. I followed slipdipper's advice from comment #114, resulting in the following patch. Now, Bluetooth works for me. Just why exactly is it necessary to specify the kernel device type? Doesn't that vendor ID + hardware ID pretty much guarantee what device it is? ** Patch added: udev hid2hci rules https://bugs.launchpad.net/ubuntu/+source/udev/+bug/20/+attachment/1683665/+files/__lib__udev__rules.d__70-hid2hci.rules.diff -- USB logitech bluetooth doesn't work https://bugs.launchpad.net/bugs/20 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 444420] Re: USB logitech bluetooth doesn't work
** Changed in: udev (Ubuntu Maverick) Status: Fix Released = Incomplete -- USB logitech bluetooth doesn't work https://bugs.launchpad.net/bugs/20 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 241206] Re: Gnome Screensaver does not activate reliably
Upon further testing, while my previous patch does fix a code path which results in the idle watch timer not being reset, it has not fully fixed this bug. There still appears to be a race condition in which the idle watch timer is sometimes not being reset. Try as I have, I have not been able to isolate the exact reason for it. However, I have a work-around that seems to fix the problem fully. It is the fairly ugly solution of calling reset_idle_watch from within the on_idle_timeout callback. While it might not be elegant, it does guarantee that the idle timeout is always reset. I have tested this patch on two machines for nearly the last 3 months, and not once has my session failed to go idle, and activate the screensaver, when it was supposed to. Furthermore, I have watched for any undesirable behavior from the screensaver or session (such as, screensaver deactivating without activity, session going idle when active, high processor usage, etc.) and have seen no undesirable activity. The following patch does *not* supercede my previous patch. For the full fix, both patches are required. The following patch is made against Ubuntu gnome-session 2.30.0-0ubuntu1. ** Patch added: Guarantee reset_idle_watch is called whenever idle watch timer expires https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/241206/+attachment/1676278/+files/111_gnome-session-2.30.0__gnome-session__gsm-presence.c.patch -- Gnome Screensaver does not activate reliably https://bugs.launchpad.net/bugs/241206 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 241206] Re: Gnome Screensaver does not activate reliably
Also, I have already submitted the above patch to upstream #625019. -- Gnome Screensaver does not activate reliably https://bugs.launchpad.net/bugs/241206 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 597057] Re: on panel restart, indicator-applet-session does not show the status (AKA: me) menu
Attached before screenshot. ** Attachment added: before screenshot http://launchpadlibrarian.net/53076879/Screenshot.png -- on panel restart, indicator-applet-session does not show the status (AKA: me) menu https://bugs.launchpad.net/bugs/597057 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 597057] Re: on panel restart, indicator-applet-session does not show the status (AKA: me) menu
Attached after screenshot. As you can see, both the me menu and the network manager applet fail to restart, although this bug is limited to the me menu. ** Attachment added: after screenshot http://launchpadlibrarian.net/53076953/Screenshot-1.png ** Changed in: indicator-me (Ubuntu) Status: Incomplete = New -- on panel restart, indicator-applet-session does not show the status (AKA: me) menu https://bugs.launchpad.net/bugs/597057 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 241206] Re: Gnome Screensaver does not activate reliably
** Changed in: gnome-screensaver (Ubuntu) Assignee: (unassigned) = Robert Lange (rcl24) ** Changed in: gnome-session Assignee: (unassigned) = Robert Lange (rcl24) -- Gnome Screensaver does not activate reliably https://bugs.launchpad.net/bugs/241206 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 491926] Re: screensaver doesn't start immediately after being enabled
See Bug #241206 comments 16 and 17 for my explanation of this bug, and patches. ** Also affects: gnome-session Importance: Undecided Status: New ** Changed in: gnome-session Assignee: (unassigned) = Robert Lange (rcl24) ** Changed in: gnome-session Status: New = In Progress -- screensaver doesn't start immediately after being enabled https://bugs.launchpad.net/bugs/491926 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 363635] Re: Screensaver does not work in 9.04
See Bug #241206 comments 16 and 17 for my explanation of this bug, and patches. ** Also affects: gnome-screensaver Importance: Undecided Status: New ** Project changed: gnome-screensaver = gnome-session ** Changed in: gnome-session Status: New = In Progress ** Changed in: gnome-screensaver (Ubuntu) Status: New = In Progress ** Summary changed: - Screensaver does not work in 9.04 + Gnome Screensaver does not activate when time limit is reached ** Changed in: gnome-session Assignee: (unassigned) = Robert Lange (rcl24) -- Gnome Screensaver does not activate when time limit is reached https://bugs.launchpad.net/bugs/363635 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 491926] Re: screensaver doesn't start immediately after being enabled
** Changed in: gnome-screensaver (Ubuntu) Status: Triaged = In Progress -- screensaver doesn't start immediately after being enabled https://bugs.launchpad.net/bugs/491926 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 363635] Re: Gnome Screensaver does not activate when time limit is reached
*** This bug is a duplicate of bug 241206 *** https://bugs.launchpad.net/bugs/241206 ** This bug has been marked a duplicate of bug 241206 Gnome Screensaver does not activate reliably -- Gnome Screensaver does not activate when time limit is reached https://bugs.launchpad.net/bugs/363635 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 205574] Re: Screensaver does not activate while mouse pointer on tooltip
Changed to invalid. I have tried on a fresh install of 10.04 pointing to all of the tooltips I know of, and I simply cannot trigger this bug. ** Changed in: gnome-screensaver (Ubuntu) Status: Confirmed = Invalid -- Screensaver does not activate while mouse pointer on tooltip https://bugs.launchpad.net/bugs/205574 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 241206] Re: On Hardy screen saver never displays
** Also affects: gnome-session Importance: Undecided Status: New ** Project changed: gnome-session = stracciatella-session ** Project changed: stracciatella-session = gnome-session ** Summary changed: - On Hardy screen saver never displays + Gnome Screensaver does not activate reliably -- Gnome Screensaver does not activate reliably https://bugs.launchpad.net/bugs/241206 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 241206] Re: Gnome Screensaver does not activate reliably
After getting really frustrated with this bug, I spent most of 4th of
July weekend wading knee-deep in gnome-session and gnome-screensaver
code, but I finally rooted out the bugs behind this. There are two
bugs:
=== Bug 1 -- gnome-session -- gsm-manager.c ===
Gnome Screensaver activates when the Gnome Session Manager's Presence
module (gsm-presence.c) sends a StatusChanged signal over DBus. This
signal is sent when an idle watch timer expires. When the timer expires
and sends the signal, it needs to be reset. One code path to reset it
is triggered when the screensaver activates or deactivates.
(Notification of this is via DBus message.) Otherwise, resets are
triggered by calls from gsm-manager.c that happen when a) the GConf key
corresponding to screensaver timeout is changed (e.g., when the user
changes the timeout in the preferences dialog), or b) an inhibitor is
added or removed (e.g., when you watch a movie in vlc).
So, if the screensaver is disabled when the idle timer expires, nothing
will be able to reset the idle timer. Furthermore, when the user re-
enables the screensaver, the timer is still inactive, so the screensaver
won't be called. Only by taking some special action, such as logging
outin, changing the screensaver timeout, or manually activating a
screensaver, will the timer be re-activated.
I have fixed this by adding a callback in gsm-manager.c that watches for
changes to the GConf key corresponding to the screensaver being enabled
(/apps/gnome-screensaver/idle_activation_enabled). When this GConf key
is changed, the idle watch timer is reset.
=== Bug 2 -- gnome-screensaver -- gs-listener-dbus.c ===
The above explains why screensavers are not triggered at all after re-
enabling the screensaver. However, even with that fix, the screensaver
fades out, but then snaps back to life as soon as the fade is done.
Gnome Screensaver activation is a 2-stage process: first, the gnome-
session presence module sends a DBus StatusChanged signal, {gs-
watcher-x11.c gs-monitor.c} checks whether the screensaver is
inhibited, and if not, begins a fade-out for 10 seconds. When the 10
seconds have expired, assuming the user has not interrupted the fade-out
by doing something, {gs-watcher-x11.c gs-monitor.c} triggers the
screensaver activation. Activation is actually initiated from gs-
listener-dbus.c.
Unfortunately, due to some convoluted and muddled logic in
listener_check_activation and gs_listener_set_session_idle, if the
screensaver is disabled when an idle session signal is received, the gs-
listener-dbus.c believes that the session is idle (i.e., the screensaver
is on), even though the screensaver is disabled. Then, once the
screensaver is re-enabled and begins receiving more idle session
notifications, gs-listener-dbus.c ignores those notifications, because
it thinks the screensaver is already on! However, the fade-outs operate
on a different, uncorrupted state variable, so they are unaffected.
Thus, the fade-out happens correctly, but at the moment that the
screensaver should activate, nothing happens and the session returns to
the desktop.
My fixes to gs-listener-dbus.c maintain the correct state for the
session_idle variable, and clean up the logic of the two mentioned
functions, while adding comments and debugging messages.
=== Conclusion ===
When both packages are patched and recompiled, the screensaver will
resume working correctly after it has been disabled and re-enabled.
The gnome-session patch is against gnome-session_2.30.0-0ubuntu1. To
apply, drop it in gnome-session-2.30.0/debian/patches, append a line
containing the filename to gnome-session-2.30.0/debian/patches/series,
and rebuild.
The gnome-screensaver patch is against gnome-
screensaver_2.30.0-0ubuntu2. To apply, drop it in gnome-
screensaver-2.30.0/debian/patches and rebuild.
I will work to get these patches in a state where they can be accepted
into Ubuntu and upstream. If anyone knows more about the process and
could help, that would be appreciated.
** Attachment added: 110_gnome-session-2.30.0__gnome-session__gsm-manager.c
http://launchpadlibrarian.net/51443690/110_gnome-session-2.30.0__gnome-session__gsm-manager.c
--
Gnome Screensaver does not activate reliably
https://bugs.launchpad.net/bugs/241206
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 241206] Re: Gnome Screensaver does not activate reliably
Agghh! Ignore Launchpad's links to B U G 1 and B U G 2 in the above post. Also, the above patch should end with the extension .patch. Here is the second patch file, which covers the gnome-screensaver patch. Read the above comment #16 for the explanation and how to apply it. ** Patch added: 21_gnome-screensaver-2.30.0__src__gs-listener-dbus.c.patch http://launchpadlibrarian.net/51443767/21_gnome-screensaver-2.30.0__src__gs-listener-dbus.c.patch ** Changed in: gnome-session Status: New = In Progress ** Changed in: gnome-screensaver (Ubuntu) Status: Triaged = In Progress -- Gnome Screensaver does not activate reliably https://bugs.launchpad.net/bugs/241206 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 597057] [NEW] on panel restart, indicator-applet-session does not show the status menu
Public bug reported: Binary package hint: indicator-applet When I restart the panel without logging out/logging in (i.e., by sighup'ing it), or if the panel crashes and auto-restarts itself, the status menu portion of indicator-applet-session is not visible, although the power menu portion is. To get the status menu back (without logging out/logging in), I must sighup indicator-applet-session, which pops up a dialog box (so this cannot be automated by a script). When the panel restarts, all of my other applets re-display themselves properly without additional manual effort. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: indicator-applet-session 0.3.6-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic x86_64 Architecture: amd64 Date: Mon Jun 21 18:06:21 2010 LiveMediaBuild: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: indicator-applet ** Affects: indicator-me (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- on panel restart, indicator-applet-session does not show the status menu https://bugs.launchpad.net/bugs/597057 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 597057] Re: on panel restart, indicator-applet-session does not show the status menu
Ugh. I don't know if this bug affects indicator-applet, indicator- session, or indicator-me. Frankly, I can't figure out the difference between the three. I thought I was adding indicator-session and indicator-me to the list of affected packages, but apparently I was just switching the affected package. Would someone who knows please set this to the appropriate package. -- on panel restart, indicator-applet-session does not show the status menu https://bugs.launchpad.net/bugs/597057 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 597057] Re: on panel restart, indicator-applet-session does not show the status menu
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/50708117/Dependencies.txt ** Package changed: indicator-applet (Ubuntu) = indicator-session (Ubuntu) ** Package changed: indicator-session (Ubuntu) = indicator-me (Ubuntu) -- on panel restart, indicator-applet-session does not show the status menu https://bugs.launchpad.net/bugs/597057 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 597057] Re: on panel restart, indicator-applet-session does not show the status (AKA: me) menu
** Summary changed: - on panel restart, indicator-applet-session does not show the status menu + on panel restart, indicator-applet-session does not show the status (AKA: me) menu -- on panel restart, indicator-applet-session does not show the status (AKA: me) menu https://bugs.launchpad.net/bugs/597057 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 597057] Re: on panel restart, indicator-applet-session does not show the status (AKA: me) menu
** Description changed: Binary package hint: indicator-applet When I restart the panel without logging out/logging in (i.e., by sighup'ing it), or if the panel crashes and auto-restarts itself, the status menu portion of indicator-applet-session is not visible, although the power menu portion is. To get the status menu back (without logging out/logging in), I must sighup indicator-applet-session, which pops up a dialog box (so this cannot be automated by a script). When the panel restarts, all of my other applets re-display themselves properly without additional manual effort. + EDIT (2010-06-22): The status (AKA: me) menu still functions after + restarting the panel. It is a thin empty area immediately to the left + of the power (AKA: session) menu. Neither the user name nor the status + icon is shown, but clicking the thin empty area opens the status menu. + So it seems that this bug is simply a failure to re-initialize the icon + and username for the menu. + + ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: indicator-applet-session 0.3.6-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic x86_64 Architecture: amd64 Date: Mon Jun 21 18:06:21 2010 LiveMediaBuild: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) ProcEnviron: - LANG=en_US.utf8 - SHELL=/bin/bash + LANG=en_US.utf8 + SHELL=/bin/bash SourcePackage: indicator-applet -- on panel restart, indicator-applet-session does not show the status (AKA: me) menu https://bugs.launchpad.net/bugs/597057 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 363635] Re: Screensaver does not work in 9.04
Sebastian: I know this is not the kind of bug you like, since it is difficult to describe and hard to reproduce reliably, but it is a real bug. Perhaps the wording of the title could be better, and we need more people to flesh out what is happening. As it stands now, I have absolutely no faith that gnome-screensaver will reliably lock my computer or protect my screen, so I always manually lock my workstation and always shut off my monitor when I am not at it. It's a shame I have to do this. johnsdagg: Your description in comment #7 was what drew me to this bug report. In my case, I disable gnome-screensaver via the preferences dialog, so I can watch hulu.com uninterrupted. When I am done watching, I re-enable it via the preferences dialog. However, all that happens once the timeout hits is the screen fades as though the screensaver were activating, then it blinks back to the desktop. The screensaver will not properly activate until I right-click on the Lock Screen applet (that I added to my panel) and choose activate screensaver. (A weird thing that happens then is the screensaver activates, but once I move my mouse, it deactivates, but instantly reactivates, no matter how long I waited after it first came on. It does this exactly once per manual activation.) Once I have manually re-activated it, the screensaver seems to behave normally, until the next time I deactivate it. Also, a reboot or logout solves the problem, but that is of course not an acceptable solution. For me, the problem is pretty repeatable: once I deactivate the screensaver through the preferences dialog, then re-activate it through the preferences dialog, I must manually use the Lock Screen button (either click to lock, or right-click and choose the Activate screensaver option to activate the screensaver, but not lock). It does not seem to matter whether I use the blank screensaver or any particular screensaver. I first noticed this bug after upgrading from 8.10 to 9.04 on an x86 machine. I thought it was an upgrade-related bug, so I ignored it. Now I have just done a clean stock install of 10.04 on an amd64 machine, and I have observed the same problem. Is there anyway to log screensaver events, such as activations and deactivations. Clearly the screensaver is activating, b/c the screen fades to black, but something is immediately signaling it to halt the screensaver instantly as it activates. I would like to find out what event is doing this, so we can fix this bug. ** Changed in: gnome-screensaver (Ubuntu) Status: Invalid = New -- Screensaver does not work in 9.04 https://bugs.launchpad.net/bugs/363635 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386211] Re: presence icons are in fast user switch applet even when presence is disabled
In 10.04, the presence applet seems to be separate from the user-switch applet, so I am closing this as a moot point now. ** Changed in: fast-user-switch-applet (Ubuntu) Status: Triaged = Invalid -- presence icons are in fast user switch applet even when presence is disabled https://bugs.launchpad.net/bugs/386211 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 205574] Re: Screensaver does not activate while mouse pointer on tooltip
I have spent the evening running down Gnome Screensaver bugs. [un]Fortunately, I cannot reproduce this particular bug on a fresh install of 10.04. I can point to things that show a tooltip, such as the panel menu, and after the timeout, the tooltip disappears and the screen is blanked/locked. -- Screensaver does not activate while mouse pointer on tooltip https://bugs.launchpad.net/bugs/205574 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 241206] Re: On Hardy screen saver never displays
I had noticed this bug on an upgraded 8.10 - 9.04 - 9.10 but had assumed it was an upgrade bug, and ignored it. Now I have the same bug a clean install of 10.04. This absolutely should be a serious issue, as it could cause screen damage (imagine I go away for the week forgetting to turn off my monitor) and is a security issue (imagine forgetting to manually lock the screen). I definitely have found that the most reliable way to initiate this bug is to deactivate the screensaver via the preferences dialog for some length of time (e.g., to watch a show on hulu.com), and then reactivate it. I have found a work-around that's better than logging out or restarting. I have a Lock Screen applet on my panel, and right-clicking it and choosing Activate Screensaver, after reactivating the screensaver via the preferences, will cause the screensaver to work correctly. Note, this bug may also be related to bug #363635. Given that this bug involves the screen fading to black, as though the screensaver were activated, before popping right back to the desktop, it seems that something is canceling the screensaver at the last moment. Does anyone know how to log the events that deactivate a screensaver? -- On Hardy screen saver never displays https://bugs.launchpad.net/bugs/241206 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 491926] Re: screensaver doesn't start immediately after being enabled
Other related bugs are bug #241206 and bug #363635. These may all be different peoples' renditions of the same bug. -- screensaver doesn't start immediately after being enabled https://bugs.launchpad.net/bugs/491926 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 538541] Re: murrine_style_draw_box: assertion `height = -1' failed
*** This bug is a duplicate of bug 538499 *** https://bugs.launchpad.net/bugs/538499 Just a quick update to say there is a fix reported in the following comment of bug #538499, so people can find it more rapidly. https://bugs.launchpad.net/ubuntu/+source/light- themes/+bug/538499/comments/24 -- murrine_style_draw_box: assertion `height = -1' failed https://bugs.launchpad.net/bugs/538541 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359407] Re: Jaunty icedtea6-plugin doesn ’t work in Firefox 3.5
I am using Jaunty 32-bit with Firefox 3.5 (3.5.7+nobinonly- 0ubuntu0.9.04.1) from the Ubuntu Universe repository and OpenJDK/IcedTea (6b16-1.6.1-0jaunty1) from the OpenJDK PPA (https://launchpad.net/~openjdk/+archive/ppa). I have never had Sun JDK or GCJ installed on this system. None of the Java applets I have tried work (for example, http://www.java.com/en/download/help/testvm.xml). Prior to installing OpenJDK 1.6.x from the OpenJDK PPA (when I was using OpenJDK 1.4.x that came with the official Jaunty repositories) when I loaded a Java applet, Firefox would hang at 100% CPU and nothing but a grey box would appear in place of the applet. I would have to manually kill the Firefox process. Now that I am using OpenJDK 1.6.x, Firefox does not hang upon attempting to load the applet, but still only shows the grey box. I can still do all other Firefox operations normally. I still get error messages on the terminal identical to those shown in this bug report. When I close Firefox, the Firefox process hangs, and I have to manually kill it before starting a new Firefox instance. So from what I can see, the OpenJDK/IcedTea 1.6.x packages in the OpenJDK PPA do nothing for this bug except delay the hang until you attempt to close the Firefox instance. Can someone confirm whether simply adding the OpenJDK PPA and dist-upgrading to OpenJDK 1.6.x is enough to fix this? Do I have to do any extra voodoo like first remove and purge all of Firefox/OpenJDK/world? Do I have to manually delete any directories or symlinks? I have not done any manual mucking around with the Firefox or OpenJDK stuff, and was hoping that simply letting apt do the upgrade would be sufficient, but apparently it's not. -- Jaunty icedtea6-plugin doesn’t work in Firefox 3.5 https://bugs.launchpad.net/bugs/359407 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
