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
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
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
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
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
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
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
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
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
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)
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
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/779639
Title:
gnome
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
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
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
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
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
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.
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
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
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/241206
Title:
Gnome
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
** 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
Desktop Bugs, which is subscribed to gnome
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
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
--
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
Desktop Bugs, which is subscribed to empathy in ubuntu.
--
desktop-bugs mailing list
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
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
--
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
Desktop Bugs, which is subscribed to empathy in ubuntu.
--
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
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
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,
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
** 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
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
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.
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
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
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.
--
** 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
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: 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
** 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
Desktop Bugs, which is a bug assignee.
--
*** 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
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
** 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
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
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:
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
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.
--
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
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
Desktop
2.26.1-0ubuntu1
It's a pretty important issue if the CD you are burning is intended for
use by a non-technical Windows user. In that case, they complain at you
that you burned a disc full of garbage.
--
make brasero retain extension when truncating file names for windows
Public bug reported:
Binary package hint: brasero
When I checked the Increase compatibility with Windows option before
burning my disk, Brasero warned me that it would have to truncate file
names longer than 64 characters in order to be Windows compatible. I
allowed it and burned the disk.
The
I can also confirm this on 9.04 (i686) with gnome-panel 2.26.0.
Roydhouse's method (comment #12) is effective in reproducing it. This
bug seems to happen primarily when you change screen resolution. It
severely affects laptop users, rendering the use of external monitors to
be unnecessarily
The bug occurred in Gutsy definitely. I used Hardy only very briefly,
so I don't know if it occurred there. Right now I have no dedicated
Linux box, due to massive (hardware?) instability on what was once my
primary workstation. I will not have time to correct this situation for
several weeks.
As of my upgrade to hardy, this bug is fixed for me. Does it still
affect anyone who is using hardy, or has this finally been fixed for
good?
--
Trash always empty.
https://bugs.launchpad.net/bugs/34247
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I'll throw my experience with this bug into the hat. I just upgraded
from Gutsy, in which this feature worked correctly, to Hardy, in which
the bug appeared. Hardy is currently up to date.
First, I reverted my Gnome keyboard preferences to the default. I tried
Jay Finger's suggestion of
I just created a brand new account, and verified that my observations in
comment 42 are still happening in a new account. That is, using the
xorg.conf workaround, with all defaults for Gnome keyboard preferences
and *no* ~/.xmodmaprc file, the default behavior of Gnome overrides the
xorg.conf
To reiterate, my problem is that trash does not work for my home
directory. The problem is with both the Trash Applet and Nautilus. If I
mount a floppy or a USB stick or whatever, trash works correctly for
those mounts. However, trash will not work for my home directory.
I have NOT tried
I have just done a fresh install. The only difference between this
install and my previous installation is that I have mounted /home on its
own partition, as opposed to having only a / partition. Both the Trash
applet and Nautilus trash now are able to see and empty trash stored in
my ~/.Trash
I have found some more information, although I don't really have time
now to do more.
In the file gnome-vfs-unix-mounts.c there are several different
possibilities based on what type of unix you have and how it stores
mount information. In particular for Ubuntu the HAVE_MNTENT_H ifdef is
used, so
I have instrumented gnome_vfs_volume_handles_trash(...) in libgnomevfs
/gnome-vfs-volume.c. I have observed that gnome-vfs identifies the type
of the root filesystem as rootfs. There is no entry for such a
filesystem in gnome-vfs-filesystem-type.c, so it thinks that the root
filesytem, on which my
60 matches
Mail list logo
