[Bug 369822] Re: Sound muted, volume 0% after reboot/shutdown

2010-10-18 Thread jp.seixas
I had the same problem here after upgrade from Kubuntu Lucid Lynx to
Kubuntu Maverick Meerkat. I found out that the problem was in the
~/.kde/share/config/kmixctrlrc file. I simply deleted this file and
everything was back to normality...

-- 
Sound muted, volume 0% after reboot/shutdown
https://bugs.launchpad.net/bugs/369822
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 563878] Re: Ubuntu splashscreen big and ugly after installing ATI/nVidia proprietary graphics driver

2010-10-17 Thread jp.seixas
A workaround for the ugly text bootsplash (in Maverik Meerkat) is to
uninstall plymouth-theme-kubuntu-text and plymouth-theme-ubuntu-text.

You will get the text messages of boot proccess, instead of the ugly
text logo.

-- 
Ubuntu splashscreen big and ugly after installing ATI/nVidia proprietary 
graphics driver
https://bugs.launchpad.net/bugs/563878
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 647539] Re: No sound after Maverick Meerkat upgrade

2010-10-14 Thread jp.seixas
With the latest updates I don't have the problem anymore.

-- 
No sound after Maverick Meerkat upgrade
https://bugs.launchpad.net/bugs/647539
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 553854] Re: plymouth: after installing proprietary nvidia driver, splash screen displays in low color/low resolution mode

2010-10-07 Thread jp.seixas
*** This bug is a duplicate of bug 563878 ***
https://bugs.launchpad.net/bugs/563878

The workaround works fine with Kubuntu Maverick Meerkat (10.10). I just
can't understand why there's no fix if a workaround is already out, so,
the problem AND solution is already known.

When I try to show Kubuntu (or Ubuntu) to a Windows user, the first
thing they notice is the UGLY boot... :(

-- 
plymouth: after installing proprietary nvidia driver, splash screen displays in 
low color/low resolution mode
https://bugs.launchpad.net/bugs/553854
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 551013] Re: ubuntu-logo on VGA fb (as with nvidia or fglrx binary drivers) does not display crisply

2010-10-07 Thread jp.seixas
The workaround works fine with Kubuntu Maverick Meerkat (10.10). I just
can't understand why there's no fix if a workaround is already out, so,
the problem AND solution is already known.

When I try to show Kubuntu (or Ubuntu) to a Windows user, the first
thing they notice is the UGLY boot... :(

-- 
ubuntu-logo on VGA fb (as with nvidia or fglrx binary drivers) does not display 
crisply
https://bugs.launchpad.net/bugs/551013
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 647539] Re: No sound after Maverick Meerkat upgrade

2010-10-05 Thread jp.seixas
Eduardo Sanz,

If you completly uninstalled pulseaudio and still got no sound, your
problem is with another package, you should investigate and open another
thread.


ntomka,

I know it's not a solution, but is better than no sound at all. There's
only 4 people complaining about this bug, and there's no one assigned to
fix it. I think this will remain unfixed for a lng time.

** Description changed:

-- 
No sound after Maverick Meerkat upgrade
https://bugs.launchpad.net/bugs/647539
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 647539] Re: No sound after Maverick Meerkat upgrade

2010-10-05 Thread jp.seixas
ntomka,

I agree it's ugly, and no prior version had it. I hope that with the
official launch of final version more people complain about it. But,
unfortunately, I've seen ugly bugs that have never been fixed...

-- 
No sound after Maverick Meerkat upgrade
https://bugs.launchpad.net/bugs/647539
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 647539] Re: No sound after Maverick Meerkat upgrade

2010-10-05 Thread jp.seixas
** Description changed:

  Binary package hint: pulseaudio
  
  After upgrading from Lucid, the system was unable to reproduce sound.
  Even yes  /dev/dsp had no effect.
  
  For some strange reason, alsamixer showed all channels to be muted while
  KDE's mixer didn't – But that turned out not to be the problem.
  Correcting that had no effect.
  
  However, the problem was solved by doing the following:
  
  rm -rf ~/.pulse*
  killall -HUP pulseaudio
  
  Another workaround is using alsa output in players.
  
  Whatever it is that's confusing Pulseaudio should be deleted or renamed
  upon every upgrade.
+ 
+ 
+ * killing the pulseaudio daemon may also work:
+ 
+ pulseaudio --kill

-- 
No sound after Maverick Meerkat upgrade
https://bugs.launchpad.net/bugs/647539
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 647539] Re: No sound after Maverick Meerkat upgrade

2010-10-02 Thread jp.seixas
After killing pulseaudio, you have to restart the application you are trying do 
hear. You have to kill it each reboot.
Here simply killing pulseaudio deamon works perfect: pulseaudio --kill.

-- 
No sound after Maverick Meerkat upgrade
https://bugs.launchpad.net/bugs/647539
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 647539] Re: No sound after Maverick Meerkat upgrade

2010-10-02 Thread jp.seixas
PS: uninstalling pulseaudio solves the problem at all.

-- 
No sound after Maverick Meerkat upgrade
https://bugs.launchpad.net/bugs/647539
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 647539] Re: No sound after Maverick Meerkat upgrade

2010-09-28 Thread jp.seixas
No sound here too. Killing pulseaudio also works here.

-- 
No sound after Maverick Meerkat upgrade
https://bugs.launchpad.net/bugs/647539
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 591024] Re: Can't edit Auto eth0 connection makes impossible to use static Ip / custom connections in Kubuntu/Kde

2010-08-19 Thread jp.seixas
It's very annoying... You can overcome this problem by setting up the
connection directly at /etc/network/interfaces, or setting it up
during a installation using the alternate install disk. Both ways, you
won't use the KDE Connection Manager, what is kind of annoying too...

-- 
Can't edit Auto eth0 connection makes impossible to use static Ip / custom 
connections in Kubuntu/Kde
https://bugs.launchpad.net/bugs/591024
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 554514] Re: cant find resource agents

2010-06-01 Thread jp.seixas
After a fresh install on 2 different machines, I've got Akonadi is not
operational error message when I try to use Kontact. It says that no
resource agents have been found.

Kubuntu 10.04 is simply not usable for professional purposes. :-(

-- 
cant find resource agents
https://bugs.launchpad.net/bugs/554514
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to akonadi in ubuntu.

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs