*** This bug is a duplicate of bug 173890 ***
https://bugs.launchpad.net/bugs/173890
Same issue here
--
flashplugin-nonfree md5sum mismatch error on Ubuntu Gutsy AMD64
https://bugs.launchpad.net/bugs/175420
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Well, there were no official answer to this problem and it's been a few
weeks.
I'm going back to slack, which is way faster/more responsive on my
system. It is a pain to see uge performance decrease after an upgrade...
--
[Gutsy] GNOME takes too much time to load during system boot
https://bugs.
Public bug reported:
I tried i386 and AMD64 versions of Gutsy. I noticed that gimmie was
working in i386 but now that I run amd64 image, it won't even start. I
get the following when I try to run it from terminal:
[EMAIL PROTECTED]:~$ gimmie
!!! org.gnome.PowerManager D-BUS service not available
Reistlehr -> there was indeed an update today. If you compare 64 and
i386, please report the results, I would be glade to go back on 64 bits.
For now, i386 is blazing fast.
--
[Gutsy] GNOME takes too much time to load during system boot
https://bugs.launchpad.net/bugs/151544
You received this bug
I installed from i386 image instead of amd64, gnome loads much faster
now. I get a usable desktop after 20 seconds and there is far less HD
activity on login as well.
This problem was always reported on amd systems in the forum, so I guess
that the problem is related to the 64 bits system.
--
[G
Same problem, hp dv2412ca with AMD-64.
Long time to login, no splash screen, I can see the panel appear in
plain gtk (grey, not themed) and then I see the theme being applied.
Overall, gnome feels slow, dialogs takes time to appear, apps freeze for
a few seconds from time to time. I also noticed h
Problem solved. In fact, there was never a problem (in Ubuntu). I
realized that the sound state depended on how I would reboot my
computer. If I run Vista and I want o log into Uduntu, I have to unplug
the power cord from the laptop before rebooting. Then, I have sound.
There is no way to have soun
Mario, if alsa-driver are in the kernel, I suspect that the affected
package would be default Gutsy kernel.
--
No sound in Gutsy
https://bugs.launchpad.net/bugs/156771
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Public bug reported:
I bought a new laptop, hp dv2000 (model dv2412ca).
lspci says:
Audio device: "nVidia Corporation MCP51 High Definition Audio (rev a2)
Ubuntu loads the snd-hda-intel modules. The soundcard looks like it is
configured, but I have no sound. I had the same issue with feisty.
Ple
I have tried the Gutsy RC, still have no sound with this card on my hp
dv2412ca laptop.
--
Not work Audio device: "nVidia Corporation MCP51 High Definition Audio (rev a2)"
https://bugs.launchpad.net/bugs/117246
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
I tried the patch and the steps mentioned on the fedora forum... very
bad results on Gutsy. First, removing alsa stuff remove gdm and a few
other things. Then, after installing everything and rebooting, the
soundcard is not even detected. alsaconf detect the card but can't
configure it. Please! do
Can someone from the Ubuntu audio team confirm that this patch fix the
problem for this chipset please? I think I found how to fix my wireless
and if audio works as well, I might consider Ubuntu again for this
laptop...
--
Not work Audio device: "nVidia Corporation MCP51 High Definition Audio (re
same problem here, latop is HP dv2412ca, sound card is detected and seem
to be configured but I hear no sound. This morning, when I booted my
laptop, I had sound (I haven't done anything special beside booting) but
now that I have restart the computer, sound went away again.
I tested with Gutsy li
Hi!,
here is the info:
1. Linux abi 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux
Since then, I think that I made a kernel upgrade through update-manager, still
have the same problem.
2. file is attached
3. file is attached
Thanks!
carl
** Attachment added: "logs.zip"
h
Hi Brian,
I talking about suspend to RAM, I never use suspend to disk.
Thank you,
carl
On 5/16/07, Brian Murray <[EMAIL PROTECTED]> wrote:
>
> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. When you mention suspend are you referring to suspend to RAM or
> su
Public bug reported:
Under Edgy, my laptop was working perfectly. Under Feisty, I have
several problems, the most anoying being suspend to ram. Whenever I
suspend and wake up, gnome tells me that suspend didn't worked. Then,
gnome-network-manager is unable to get back on the network. Sometimes,
it
16 matches
Mail list logo
