I have this same issue on Feisty. The Intel graphics processor is the
cause of this issue, as i have an i810.
The specs of this machine are:
1.2Ghz Intel PIII
512Mb RAM
Intel i810 Chipset
Ubuntu 7.0.4 Feisty Fawn (Mythbuntu 7.0.4)
--
Progress bar is invisible
https://bugs.launchpad.net/bugs/67
Additionally...the hardware for the chipset is:
Driver "i810"
Device "Intel Corporation 82810E DC-133 CGC [Chipset Graphics
Controller]"
Which would make it appear to be a standing issue with the Intel 810
--
Progress bar is invisible
https://bugs.launchpad.net/bugs/67443
You r
Confirming, all but MPlayer. All mp3 files.
--
Crackling sound during MP3 podcast playback in Amarok 1.4.5
https://bugs.launchpad.net/bugs/84774
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for amarok in ubuntu.
--
kubuntu-bugs mailing list
You received this bug notification because you are a direct subscriber
> of the bug.
>
Realllly? Thats brilliant :D
--
Kris Douglas
Softdel Limited Hosting Services
Web: www.softdel.net
Mail: [EMAIL PROTECTED]
--
Progress bar is invisible
https://bugs.launchpad.net/bugs
*** This bug is a duplicate of bug 1107850 ***
https://bugs.launchpad.net/bugs/1107850
** This bug has been marked a duplicate of bug 1107850
Square area in top left of desktop slow to load when launching Firefox
--
You received this bug notification because you are a member of Ubuntu
Bug
Hello, I am also experiencing this bug with Google Talk. Empathy reckons
it's an un-approved self signed cert from Google. When ticking the box
to never ask again, it persists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
I have to agree with the importance raise, we were on the brink of
moving over to exchange and had to bail it all because of this lack of
support for exchange. I swear it used to work fine but I am receiving:
"The server is running Exchange 5.5. Exchange Connector
supports Microsoft Exchange 2000
I am also able to confirm that on 10.04 desktop and netbook this problem
is present. It's very noticeable on older 4600 and 5400rpm drives where
you can wait up to and even over 35 seconds for it to appear.
A non-programmer solution to this problem would be to have the menu
stored in a cache along
