@Henning
I must concur as well. I faced the same problem even with the nouveau
drivers. So I don't feel its related to the nvidia drivers as well.
I did install ubuntu on a SSD under ext3 as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Guys, I must admit I jumped the gun a bit with my solution on #54. That
is not the real fix.
To tell if your problem is the race condition I mentioned run the
following 2 commands:
killall -9 gnome-settings-daemon
gnome-settings-daemon
At this point, your theme should be applied properly.
Small update: it seems the bug affects me if I select a theme other than the
default Ambiance.
If I log on into my session with the ambiance theme I can switch to a different
theme and it loads with no problems. Once I reset or log out however, next
time I log back in the but reappears :(
--
Gentlemen, I bring great news!
It seems the problem we are facing has to do with the fact that your desktop
starts before gnome-settings-daemon does (the timing is off).
By following the tips on this thread
http://ubuntuforums.org/showthread.php?t=1594010highlight=GTK+theme I
managed to fix my
I can confirm the same bug on a clean 10.10 install:
- Core i7 (950)
- nVidia Geforce GTX470
- Intel X58
--
Meerkat (10.10) does not apply theme properly
https://bugs.launchpad.net/bugs/649809
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Steve, does this mean there is no need to use the softpedia solution
(http://news.softpedia.com/news/How-to-Fix-the-Big-and-Ugly-Plymouth-
Logo-in-Ubuntu-10-04-140810.shtml) anymore? NVIDIA cards now work dandy
with plymouth?
--
ubuntu-logo on VGA fb (as with nvidia or fglrx binary drivers)
I tried the http://news.softpedia.com/news/How-to-Fix-the-Big-and-Ugly-
Plymouth-Logo-in-Ubuntu-10-04-140810.shtml solution and it worked for me
=D
But I must say, the default ubuntu driver was able to display plymouth
at a higher resolution (it seemed like 1920x1200) than the measly
1280x1020
I have the same problem.
In my case i tried upgrading grub to grub2. When testing grub2 via
chainloading, the ubuntu entries worked fine however the windows one
doesnt. It gives me this error.
Booting into windows under legacy grub is ok.
Any ideas or suggestions?
--
grub2 fails to boot
Just want to add my 2 cents on the matter.
I have only 1 gig of memory. Ubuntu Intrepid upon boot was always
between 300 - 400 mb. Whereas kubuntu jaunty (fresh install) starts
up at around 750 megs. Thats almost double the space of my prior ubuntu
install.
--
Kubuntu Jaunty KDE 4.2 very
I can confirm as well. The fix here solves the problem. Thanks!
--
no sound with kernel 2.6.27-11 and audigy2 zs
https://bugs.launchpad.net/bugs/310179
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I can confirm the bug in intrepid 8.10
I followed Bálint Magyar's advice above and fixed the issue. Under Preferences
Misc i set my DVD device to /dev/cdrom1 and it worked like a charm.
Since I have a CD drive and I DVD drive (both internal) I executed a 'ls
/dev/cdrom*' command. It returned
Sergio, where do I get this backport fix for Gutsy you mentioned?
I have been dying to get my dictionary applet back! : )
--
The Gnome dictionary applet won't let any text be typed in on its window on the
panel on Ubuntu Gutsy.
https://bugs.launchpad.net/bugs/175151
You received this bug
Awesome, thanks guys! Now I have my dictionary applet back =D
--
The Gnome dictionary applet won't let any text be typed in on its window on the
panel on Ubuntu Gutsy.
https://bugs.launchpad.net/bugs/175151
You received this bug notification because you are a member of Ubuntu
Bugs, which is
13 matches
Mail list logo
