The small hack I found seems to work in a stable manner, so I'm posting
a small tip to automate it since the Palette lines keep on coming back
at every session login.
Just create a shell script wherever you want (mine is ~/fix_qt4_colors)
and paste the following 2 lines into it:
#!/bin/sh
cat
Public bug reported:
WARNING: this bug affects all the distros shipping with KDE 4.1.2
(Kubuntu 8.10, Mandriva 2009.0 and openSUSE 11.1) so this is definitely
an upstream bug (any Qt/KDE team member 'round here?)
Launching a Qt4 (non KDE4) application (Picard, Avidemux2 Qt version and
so on)
** Attachment added: Systemsettings' colors panel (upper left) showing Oxygen
color scheme (right) and Avidemux2 (Qt version, bottom right) showing a deep
blue selection color (wrong)
http://launchpadlibrarian.net/18922075/Schermata.jpg
** Also affects: mandriva
Importance: Undecided
** Description changed:
WARNING: this bug affects all the distros shipping with KDE 4.1.2
(Kubuntu 8.10, Mandriva 2009.0 and openSUSE 11.1) so this is definitely
an upstream bug (any Qt/KDE team member 'round here?)
Launching a Qt4 (non KDE4) application (Picard, Avidemux2 Qt version
Public bug reported:
Binary package hint: grub
I don't know if there was an update to GRUB lately (Dec 2007 / Jan 2008)
but in the last 2 weeks my Box (details following) hangs at Grub
loading, please wait... if I try to do a cold boot (i.e. the PC was
off for at least 30 minutes), at this point
** Description changed:
Binary package hint: grub
I don't know if there was an update to GRUB lately (Dec 2007 / Jan 2008)
but in the last 2 weeks my Box (details following) hangs at Grub
loading, please wait... if I try to do a cold boot (i.e. the PC was
off for at least 30
** Description changed:
Binary package hint: grub
After I've installed Ubuntu Gutsy 2 weeks ago my Box (details following)
hangs at Grub loading, please wait... if I try to do a cold boot
(i.e. the PC was off for at least 30 minutes), at this point nothing can
be done, but if I press
Can we have packages for 64bit systems please?
--
MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in
XRRGetScreenInfo()
https://bugs.launchpad.net/bugs/91545
You received this bug notification because you are a member of Kubuntu
Team, which is a bug assignee.
--
kubuntu-bugs
Well, it's a really weird thing for Kubuntu to not offer the user a
panel to manage available sound devices (or at least to set the default
one).
I confirm the problem reported by tmp, I have 2 soundcards on my
system, an Audigy PCI card and a on-board Nvidia CK804, everytime I boot
the system I
Actually the code I've posted previously gives some problems, I've
finally fixed my system by doing this (in a console):
sudo nano /etc/modprobe.d/sound
contents of the file
#sound card loading order
#Audigy (default)
alias snd-card-0 snd-emu10k1
options snd-emu10k1 index=0
#Nvidia CK804
alias
I had the same problem installing Kubuntu Feisty Fawn 7.04 over an
existing Kubuntu Edgy Eft 6.10 without changing existing partitions.
--
GRUB Error 15 after edgy-feisty upgrade of Kubuntu
https://bugs.launchpad.net/bugs/102070
You received this bug notification because you are a member of
By saying the same problem I was referring to the weird GRUB error
15 thing of course.
--
GRUB Error 15 after edgy-feisty upgrade of Kubuntu
https://bugs.launchpad.net/bugs/102070
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
12 matches
Mail list logo