The keyboard is also not recognized when booted to runlevel 3.
This would seem to confirm that this is indeed a kernel bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1090956
Title:
Wireless
Just posting here to say that this is still a bug in 13.04 beta. Seeing
as we are this close to release date, I think it is safe to assume that
this bug will still be present after 13.04 goes live.
** Summary changed:
- Wireless keyboard not properly configured
+ Wireless keyboard not properly
** Bug watch added: freedesktop.org Bugzilla #63530
https://bugs.freedesktop.org/show_bug.cgi?id=63530
** Also affects: evdev via
https://bugs.freedesktop.org/show_bug.cgi?id=63530
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
I'm not following the reasoning here, Fabio?
Does that mean that since the bug is not ubuntu-specific, it should not be
listed as affecting that distro?
It was my understanding that since it affected BOTH distros, I'd mark it as
affecting _both of them_...
I'm confused as to why this is
** Attachment added: proc.bus.input.devices
https://bugs.launchpad.net/linux/+bug/1090956/+attachment/3461481/+files/proc.bus.input.devices
** Also affects: fedora
Importance: Undecided
Status: New
** Also affects: ubuntu
Importance: Undecided
Status: New
** Tags added:
Is there a reason why usb-creator is limited to only create Ubuntu images as
opposed to images from ANY random iso file?
There are not really a bunch of alternatives to this on Ubuntu, and forcing
someone to choose only between Debian/Ubuntu specifications for the possible
isos the program will
For what it's worth, the error outputed to the Terminal if an unrecognized
iso is selected is now:
isoinfo: Unable to find Joliet SVD
There's quite a few comments about this on Google.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: usb-creator (Ubuntu)
Status: Confirmed = Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/948257
Title:
Doesn't tell what's wrong when fails to add an ISO image
To
A quick me too here to say this is still happening in 12.04 :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/962279
Title:
I am not able to view the calendar or create google calendar items.
To
a fix for this seems to be issuing the command:
$export UBUNTU_MENUPROXY=0
before loading the app, in a terminal.
source: http://www.omgubuntu.co.uk/2010/12/missing-menus-in-ubuntu-apps-try-this
Seems to still affect Guayadeque in Ubuntu Precise.
DISCLAIMER: If it matters, I am currently on
Actually, I think I am wrong here.
This is obviously due to Unity's Global Menu behaviour, I suspect...
So the question is, is there a reason why Unity's settings are messing with
Gnome-shell?
And why does it only affect some -read a few- applications, and not (most)
others?
--
You received
as well, to help further the discussion.
As a reminder to all, my graphics card is:
tiede@laptop:~$ lspci -vvnn |grep Graphics
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series
Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA
controller])
00
Public bug reported:
When moving a shaded window, a trail is left behind the operation completes.
Furthermore, even when the window is shaded, a thin rectangular box remains
delimiting where the window was before. It does not seem to affect operational
behavior, however, so this is a very low
** Attachment added: moving a shaded window leaves trails
https://bugs.launchpad.net/bugs/886120/+attachment/2585204/+files/Screenshot%20at%202011-11-04%2009%3A36%3A21.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: box left behind after shading a window
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/886120/+attachment/2585205/+files/Screenshot%20at%202011-11-04%2009%3A40%3A45.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: unity
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886120
Title:
unity leaves trails when moving window if shaded
To manage
After comment #31, I believe this should be reinstated as a bug. Not just an
opinion.
Why? Not only does it break with users' expectations, it can actually be
counter-productive, and impractical.
I should not have to fear minimizing an application while on a touch-screen
device!
There is no
This bug is marked as incomplete, but no further request for information
has been asked. Reassigning this bug as Confirmed until such demands are
clearly expressed, so we may satisfy them.
** Changed in: unity
Status: Incomplete = Confirmed
** Changed in: unity (Ubuntu)
Status:
Confused as to why Didier Roche marked this as incomplete...
No further information is requested (!?!)...
Clarify?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832004
Title:
Alt Tab behavior is
Public bug reported:
When using alt-tab to switch between windows, it may lead to a situation where
the user doesn't know which tab is currently selected, because there are many
different highlights depending on WHICH application is opened, not their states.
This can lead to a condition where
** Attachment added: This attachment should clarify the issue being presented
in the bug report
https://bugs.launchpad.net/bugs/881463/+attachment/2571805/+files/example.png
** Also affects: unity
Importance: Undecided
Status: New
** Description changed:
- When using alt-tab to
Is there a reason why this is marked incomplete?
It's my understanding that if something is marked incomplete there should be a
request for more info, so we can make it complete. Simply marking an entry as
incomplete without specifying what's missing defeats the purpose of that status.
Other
Just commenting that this happens not just with firefox and chrome, but with
all applications that have a fullscreen option with F11.
However, I also observed that while the dash itself is not summoned, the
current window loses focus, and it would appear that keystrokes are sent
elsewhere as
I'm not sure how else to explain it.
So I made a video.
I hope it helps:
http://www.youtube.com/watch?v=0cpm-c1bes8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/801351
Title:
Cannot summon dash
Public bug reported:
If one switches firefox to full screen mode, mouse dwelling on the leftmost
corner of the screen, Alt+F2 and Super all fail to show the unity dash
board/bar. Switching firefox back to windowed mode fixes the issue.
Expected behavior: The dash should be able to be summoned
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/801351
Title:
Cannot summon dash when Firefox is in fullscreen
To manage notifications about this bug go to:
Public bug reported:
Binary package hint: gnome-control-center
Within gnome-control-center, clicking on the Hardware lister does nothing.
Launching gnome-control-center from the terminal, we see that the problem is
because it couldn't find su-to-root which is available in the package menu.
** Attachment added: gcc.lshw-gtk.err
https://bugs.launchpad.net/bugs/797790/+attachment/2170086/+files/gcc.lshw-gtk.err
** Description changed:
Binary package hint: gnome-control-center
Within gnome-control-center, clicking on the Hardware lister does nothing.
Launching
Public bug reported:
Binary package hint: nspluginwrapper
During upgrade from maverick to natty.
Was not using flash or even web browsing at the time. So no steps to reproduce
are currently available.
Unless this is an upgrade-related bug?
ProblemType: Package
DistroRelease: Ubuntu 11.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774721
Title:
package nspluginwrapper 1.2.2-0ubuntu9 failed to install/upgrade:
ErrorMessage: le sous-processus script post-installation installé a
Apparently, it's segfaulting somewhere:
tiede@upgrading :~$ sudo dpkg --configure -a
Paramétrage de nspluginwrapper (1.2.2-0ubuntu9) ...
plugin dirs: :/var/lib/flashplugin-installer/
Auto-update plugins from /usr/lib/mozilla/plugins
Looking for plugins in /usr/lib/mozilla/plugins
Segmentation
*** This bug is a duplicate of bug 773020 ***
https://bugs.launchpad.net/bugs/773020
** This bug has been marked a duplicate of bug 773020
segfault in post-install script
* You can subscribe to bug 773020 by following this link:
*** This bug is a duplicate of bug 773020 ***
https://bugs.launchpad.net/bugs/773020
** This bug has been marked a duplicate of bug 773020
segfault in post-install script
* You can subscribe to bug 773020 by following this link:
*** This bug is a duplicate of bug 773020 ***
https://bugs.launchpad.net/bugs/773020
** This bug has been marked a duplicate of bug 773020
segfault in post-install script
* You can subscribe to bug 773020 by following this link:
*** This bug is a duplicate of bug 773020 ***
https://bugs.launchpad.net/bugs/773020
** This bug has been marked a duplicate of bug 773020
segfault in post-install script
* You can subscribe to bug 773020 by following this link:
*** This bug is a duplicate of bug 773020 ***
https://bugs.launchpad.net/bugs/773020
** This bug has been marked a duplicate of bug 773020
segfault in post-install script
* You can subscribe to bug 773020 by following this link:
*** This bug is a duplicate of bug 773020 ***
https://bugs.launchpad.net/bugs/773020
** This bug has been marked a duplicate of bug 773020
segfault in post-install script
* You can subscribe to bug 773020 by following this link:
*** This bug is a duplicate of bug 773020 ***
https://bugs.launchpad.net/bugs/773020
** This bug has been marked a duplicate of bug 773020
nspluginwrapper segfaults in post-install script
* You can subscribe to bug 773020 by following this link:
just to point it's not just upgrades.
Purging and reinstalling it results in the same behavior:
(sorry example is in french)
tiede@ubuntu:~$ sudo apt-get purge nspluginwrapper
[sudo] password for tiede:
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture
*** This bug is a duplicate of bug 773020 ***
https://bugs.launchpad.net/bugs/773020
** This bug has been marked a duplicate of bug 773020
nspluginwrapper segfaults in post-install script
* You can subscribe to bug 773020 by following this link:
Workaround for those affected by this issue:
There seems to be a conflict with the Google Talk Plugin, causing this behavior.
To resolve the issue, this should work
sudo apt-get purge google-talkplugin
at the end, nspluginwrapper will be automatically configured.
**workaround taken from
** Visibility changed to: Public
--
npviewer.bin crashed with SIGSEGV
https://bugs.launchpad.net/bugs/676153
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 am not sure if the fix is there...
I noticed this bug today, by clicking on the notification area applet while
using a chat window. Apparently, the indicator applet was warning me about a
new IM message, which in itself was strange, since I had the IM window focused,
and it is my
I will add that information here at once!
The same thing happened to me while using a wireless network requiring
authentication after connecting...
NOTE:
===personal email adresses where removed===
these where replaced with the nugget ***private***
** Attachment added: debug_info.txt
with information now added, I am changing the status to New again, as
per Launchpad rules...
--
telepathy-butterfly crashed with ValueError in __parse_command()
https://bugs.launchpad.net/bugs/562057
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hmmm... Seeing as this affecting me now, I don't think this should be
invalid...
Problem is, all information I have on the crash is through apport, and I don't
even know how to reproduce it;
It happened while I was doing something else, totally unrelated to telepathy...
It does happen from time
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/52052374/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/52052375/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/52052376/Disassembly.txt
** Attachment
looking at the debugging info, I can tell this is not related to the
icon theme change, so please disregard that bit...
--
pidgin_control.py crashed with SIGSEGV in PyObject_SetAttrString()
https://bugs.launchpad.net/bugs/606510
You received this bug notification because you are a member of
This is not a bug per se. (at least the fact that it is there isn't...)
What needs to be done is make it easier to remove it, or state how to do it
more clearly.
But for anyone that needs to remove this icon, all you need to do is go to:
System-Preferences-Keyboard, go to the Accessibility tab
Found a workaround that makes it apparent that this bug is related to
gnome-appearance-properties...
** Package changed: xserver-xorg-video-intel (Ubuntu) = gnome-control-
center (Ubuntu)
** Also affects: xserver-xorg-video-intel
Importance: Undecided
Status: New
** Changed in:
sorry i messed up all the tagging and whatnots, I just learned (right
now) how to add another package to a bug report... Did not mean to
change it thusly...
Anyways, as I said a moment ago, I have found a workaround that lets me
think that the bug is at least partly related with gnome-appearance-
** Tags added: regression-potential
--
emerald hangs after lucid upgrade
https://bugs.launchpad.net/bugs/579046
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
Public bug reported:
Binary package hint: xserver-xorg-video-intel
This bug is also manifested in other ways, but this is by far the most
noticeable.
It probably is not a DRI issue, since update5 fixed the disabled DRI from
update3.
I am not quite sure what exactly is wrong, but ever since I
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/48300804/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/48300805/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/48300806/Dependencies.txt
**
*** This bug is a duplicate of bug 546392 ***
https://bugs.launchpad.net/bugs/546392
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/47847577/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/47847578/ProcMaps.txt
** Attachment
I thought this was a fixed issue... I am afraid it is back again.
wifi-radar crashed while i was in user mode and forgot to sudo to it:
u...@ubuntu:~$ wifi-radar
Traceback (most recent call last):
File /usr/sbin/wifi-radar, line 3392, in module
fileLogHandler =
I am reopening this bug as it seems more people are willing to supply the
missing information.
I am not sure if Pedro V. is asking this because of known updates within the
version of telepathy on the ppa, but just to be on the safe side, someone
please try the same with the telepathy version
Over 4 months, and nothing? Sheesh! This is a mere technical bug,
nothing too serious... why is nothing said about it? Is is even going to
be fixed in lucid?
--
After Update from 9.04 to 9.10 journaux système non trouvés
https://bugs.launchpad.net/bugs/482705
You received this bug notification
I am not an Average user, I suppose, but this bug IS happening on a pretty
much vanilla installation, with changes unrelated to gnome-screensaver. Even
the mention of compiz is to help identify the problem, and does not introduce
it...
I do believe a single developer stumbling upon this might
Public bug reported:
Binary package hint: gnome-screensaver
Gnome screensaver does not always fade out when coming back to the desktop.
By this I mean, if gnome-screensaver is running, and i enter my password, it is
accepted, but I don't get to see the desktop.
setting general transparency to
It is now about two months since this bug report came out... anyone has an idea
what to do to fix it?
I want to point out that it is my understanding that all of us affected users
are using the French version of Ubuntu. Could the change in local be causing
this. I am asking because I know of at
I forgot to mention, is there a reason why this is marked incomplete?
what exactly is missing in this bug report?
--
After Update from 9.04 to 9.10 journaux système non trouvés
https://bugs.launchpad.net/bugs/482705
You received this bug notification because you are a member of Ubuntu
Bugs,
I want to mark this as anything else than New undecided, but I have no
input from anyone else.
If you use OpenGL and you have your computer setup in two different language
modes, would you mind testing it out and report if it happens to you as well,
whosoever reads this. I don't want to make
Public bug reported:
When PyOpenGL is run in Ubuntu with the language set to French(France), it
crashes when loading GL
The same exact code works perfectly fine if the language is changed to
English(USA)
See attached.
** Affects: pyopengl (Ubuntu)
Importance: Undecided
Status:
** Attachment added: The oputput says it all.
http://launchpadlibrarian.net/36265016/open.gl
--
PyOpenGL fails to load correctly when locale is not English
https://bugs.launchpad.net/bugs/490463
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Oops, I didn't think the uploader would change the file type according
to extension... Uploading again!
Again, the only thing I am doing is:
from OpenGL import GL
** Attachment added: The output is Copy/Paste straight from PyCrust
http://launchpadlibrarian.net/36265069/pyopengl.debug
--
I am noticing the same problem on Karmic too, after a regular upgrade.
What does it mean?
Paramétrage de kerneloops-daemon (0.12+git20090217-1ubuntu4.1) ...
Installation de la nouvelle version du fichier de configuration
/etc/init.d/kerneloops ...
update-rc.d: warning: kerneloops stop runlevel
Forgot to add that this is on the 64-bit of ubuntu, so this pretty much
means this is arch independent...
** Changed in: kerneloops (Ubuntu)
Status: New = Confirmed
--
kerneloops stop runlevel arguments (0 1 6) do not match LSB Default-Stop values
(1)
The same exact bug is noticed here too.
I've looked everywhere for a workaround, and am currently following a lead on
disabling ehci_hcd (or ohci_hcd or even uhci_hcd, depending on the case) and
loading it manually. will update here if it turns out to be good and reliable.
Either case, i think
This bug should be filed against usb-storage, since it's the crashing
module (as noted in the other report...) maybe on should be the
duplicate of the other?
output of dmesg after unloading/reloading the culprit driver (sudo rmmod
usb_storage sudo modprobe usb-storage):
m...@tuxed:~$ dmesg
** Bug watch added: Linux Kernel Bug Tracker #13496
http://bugzilla.kernel.org/show_bug.cgi?id=13496
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=13496
Importance: Unknown
Status: Unknown
--
usb storage(LG KU380) didn't mount automatically
*** This bug is a duplicate of bug 367484 ***
https://bugs.launchpad.net/bugs/367484
** This bug has been marked a duplicate of bug 367484
usb storage(LG KU380) didn't mount automatically
--
Huawei E620 USB Modem's micro usb drive doesn't work in jaunty, but works in
hardy
Well, the silence here has been deafening. Undeniably...
But I have good news! (no, I did not just save 15% off my car insurance ...)
But after the last few batches of updates, everything is well again...
Incidently, something disabled my don't zap workaround! Kinda fishy... but
the computer
This issue has resolved itself after the latest updates...
** Changed in: ubuntu
Status: New = Fix Released
--
Computer unresponsive after Alt+SysRq+K command
https://bugs.launchpad.net/bugs/381013
You received this bug notification because you are a member of Ubuntu
Bugs, which is
hmm... The silence on this is deafening...
I am not sure what to interpret this silence as... Is it a need for more info?
I'll provide anything... really...
(I just discovered that Ctrl+Alt+Backspace does NOT work on gdm, and that ain't
cool...)
Isn't X technically started by the time gdm is
** Attachment added: lshw
http://launchpadlibrarian.net/27683680/lshw
--
Computer unresponsive after Alt+SysRq+K command
https://bugs.launchpad.net/bugs/381013
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: lshw
http://launchpadlibrarian.net/27683564/lshw
** Attachment removed: lshw
http://launchpadlibrarian.net/27683564/lshw
--
Computer unresponsive after Alt+SysRq+K command
https://bugs.launchpad.net/bugs/381013
You received this bug notification because you are a
I'm sorry Corry Maccarrone, but have you modified anything in Nautilus to get
that to work?
I have upgraded to Jaunty recently, and my system is fairly standard. However,
the issue is still present.
Are you sure the background you're using is not the default one? If it is, the
problem does not
Public bug reported:
This bug is found in this version...
ti...@tuxed:~$ apt-cache policy gnome-panel
gnome-panel:
Installé : 1:2.26.0-0ubuntu7
Candidat : 1:2.26.0-0ubuntu7
Table de version :
*** 1:2.26.0-0ubuntu7 0
500 http://us.archive.ubuntu.com jaunty/main Packages
100
** Attachment added: output of lscpi -vvnn
http://launchpadlibrarian.net/27209130/lspci
--
Computer unresponsive after Alt+SysRq+K command
https://bugs.launchpad.net/bugs/381013
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
I am not sure which package this should be filed against...
I just upgraded to Jaunty a couple of days ago and stumbled upon the
Ctrl+Alt+Backspace removal feature...
So now, I am trying to use AltGr+SysRq+K to restart X, just testing, mind you,
to feel confident that I'll
here is the output with a fresh Jaunty upgrade.
It's just about the same...
** Attachment added: hddtemp_debug
http://launchpadlibrarian.net/26967080/hddtemp_debug
--
package hddtemp 0.3-beta15-44 failed to install/upgrade: subprocess
post-installation script returned error exit status 1
*** This bug is a duplicate of bug 307748 ***
https://bugs.launchpad.net/bugs/307748
This bug is a duplicate of bug 307748. All comments should be directed
to that bug report.
** This bug has been marked a duplicate of bug 307748
package hddtemp 0.3-beta15-44 failed to install/upgrade:
*** This bug is a duplicate of bug 307748 ***
https://bugs.launchpad.net/bugs/307748
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug is a duplicate of bug #307748. Please
report all future comments to that bug report.
** This bug has
*** This bug is a duplicate of bug 307748 ***
https://bugs.launchpad.net/bugs/307748
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug is a duplicate of bug #307748. All
future comments should be directed to that report.
** This bug has
*** This bug is a duplicate of bug 307748 ***
https://bugs.launchpad.net/bugs/307748
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular situation has already been reported in
bug #307748. Therefore, all future comments should be directed there.
Required info provided. Found five duplicates. Tentatively marking this
bug as confirmed.
** Changed in: hddtemp (Ubuntu)
Status: Incomplete = Confirmed
--
package hddtemp 0.3-beta15-44 failed to install/upgrade: subprocess
post-installation script returned error exit status 1
I have recently checked the website mentioned using firefox 3.0.10 and it seems
that everything is just fine now...
Marking this as invalid. If someone else is experiencing this, feel free to
reopen this, and attach a screenshot, mentioning which firefox version is being
used, and whether any
hmm... Ditto here. Crashed on install.
I see the report is confirmed. Is there a fix coming soon?
I am about to try to uninstall and reinstall acroread and see what happens...
it worked. sort of. I'd like to warn qrwe that this method will effectively
remove acroread-debian-files
Hmmm. I am a little perturbed by your saying Dennis...
Are you sure it was working when you did that? and how long is a
while?
in my laptop, it doesn't work. Now it looks like it does for the first
few minutes or so sometimes, but whenever the laptop gets hot, the lines
start appearing. And the
It's February 2009, and this bug is finally triaged...
Am I to expect a release candidate soon?
Or am we waiting for Jaunty+1?
Needless to say, the error is still very much present...
--
automatic filters for thumbs.db and desktop.ini files
https://bugs.launchpad.net/bugs/116802
You received
i don't know if that's related, but i had a BUNCH of problems following my
upgrade to intrepid from hardy:
Snowy/fuzzy X; soundcard not detected; wireless not working, Ctrl+Alt+* (*
replaced at will F[1-9], Backspace...) not working.
Alt+F[1-9] replacing Ctrl+Alt+F[1-9], being the ones i
Public bug reported:
Binary package hint: avant-window-navigator
Currently, if you click on an item in a stack, the stack stays open, until
focus is changed (if ever) to the new window.
This makes the user doubt whether he properly selected the item he wanted and
delays feedback.
Also, if
I am posting to say that the same has just started to happen on my system.
I just noticed it today, although my last major update was about a week ago,
when I also installed the new banshee-1 player.
The problem appears as stated above, on either banshee-1 (which I was using
when I noticed it)
I am reopening this bug as requested by Sebatien, since I provided the
missing info...
** Changed in: metacity (Ubuntu)
Status: Invalid = New
--
video playback artifacts when composite manager is enabled
https://bugs.launchpad.net/bugs/218322
You received this bug notification because
hmmm... June 2008, and this issue is still present.
Will it ever be resolved upstream?
Anyway, I think this has some importance. Especially since I am left currently
with no viable option.
In my case, I am using stalonetray. It works quite well and I don't want to
part with it.
After receiving
I don't know what happened, but the trash icon issue seemed to be fixed about a
month or so ago.
Now, I am sad to say that the problem is showing its ugly head again.
I wish I knew what specific update brought back the issue, but I am afraid I
cannot recall...
Thanks for trying anyways...
Sorry for double posting, but I just noticed that the status of this bug report
is Fix Released.
That particular fix no longer works. Somebody, please re-open this bug as the
issue is STILL current under up-to-date hardy.
--
Nautilus does not update trashcan icon
Re-opening this bug since the fix no longer works
** Changed in: nautilus (Ubuntu)
Status: Fix Released = Confirmed
--
Nautilus does not update trashcan icon
https://bugs.launchpad.net/bugs/195266
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: gnome-panel
Old (obsolete) gnome panel entries in gconf-editor never get deleted.
If a user has more than the original two panels at one time, then decides to
delete a few of them (say they had 5 customized panels, and bringing it down to
1), the
1 - 100 of 135 matches
Mail list logo
