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
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
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
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
** 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
** 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
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
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
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
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
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)
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
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
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
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
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:
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
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
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
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
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
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
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
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
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
** 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.
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,
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
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
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
** 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.
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
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
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
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 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
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.
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.
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:
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/241206
Title:
Gnome Screensaver does not activate
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
Bugs, which is subscribed to Ubuntu.
https
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
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,
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
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
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
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,
** 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
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,
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
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.
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
** 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
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
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
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)
** 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
Bugs, which is subscribed to Ubuntu.
--
*** 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:
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.
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
** 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
** 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
** 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
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
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
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
Bugs,
*** 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
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
1 - 100 of 138 matches
Mail list logo
