I'm getting this bug at every boot after making a new boot disk and
installing Karmic NBR. System hang is roughly 6-10seconds with this bug
after install.
--
Pci problem while booting in karmic
https://bugs.launchpad.net/bugs/432164
You received this bug notification because you are a member of
** Attachment added: Here's a screen shot of the warning to help get the bug
to the right team.
http://launchpadlibrarian.net/33110536/Effects%20Alert.png
** Attachment added: .var.log.jockey.log.txt
http://launchpadlibrarian.net/33110537/.var.log.jockey.log.txt
** Attachment added:
Public bug reported:
When trying to enable Nvidia proprietary driver 185 in Karmic Beta from
live disk, jockey ask for a password I never set and denies access for
using the driver. It does this when enabling desktop effects and when
trying to install software. May be related to authorizations
Public bug reported:
Binary package hint: pulseaudio
Every time I open a new application in Karmic Beta pulse pops with a
slight crackle. With volume on full it has blown out one of my speakers.
It does this for all applications including non-audio applications like
terminal, and system monitor.
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/33110148/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/33110149/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/33110152/ArecordDevices.txt
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/33112906/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/33112907/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/33112908/ArecordDevices.txt
Public bug reported:
In hardware testing on the Karmic Netbook Remix Beta I can get playback
from my usb sound blaster MP3+ but it will not record. Hardware works
with my other computer so i know it and the microphone are functioning.
Sound playback is fine and actually good quality.
Public bug reported:
I cannot drop to other run levels while running the live disk of Karmic
NBR on an acer aspire one 1295. Running gksudo-nautilus causes the
computer to freeze with warning about permissions and crtl-alt F1-F6
cause similar freeze and warnings.
ProblemType: Bug
Architecture:
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/33113107/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/33113109/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/33113111/ArecordDevices.txt
Acer Aspire One Karmic NBR Beta crashed while closing F-spot.
--
maximus crashed with SIGSEGV in IA__g_closure_invoke()
https://bugs.launchpad.net/bugs/321957
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Same bug occurred on Acer Aspire One 1295 Netbook running Karmic NBR
Beta. Happened while reporting another bug.
--
run assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
Same issue on Acer Aspire One 1295 with Karmic NBR Beta. Grub starts to
load, system freezes with blank screen and does not resond to any key
presses. Pressing esc does nothing during load. Cannot get command
prompt, cannot enter any info. Cannot edit grub preferences from live
disk because it
Causing hang on boot using USB thumb drive as live disk. Hang duration
for Karmic NBR Beta is 35-60 seconds. Causes delay in loading for Grub
2.
--
Pci problem while booting in karmic
https://bugs.launchpad.net/bugs/432164
You received this bug notification because you are a member of Ubuntu
The latest round of Jaunty updates have fixed this issue so far. I've
been running stable for a few days without issue. I would consider this
bug closed on my end unless anyone else wants to confirm it.
--
Jaunty Crashes Randomly
https://bugs.launchpad.net/bugs/368410
You received this bug
I filed a bug using the ubuntu bug xorg command right after rebooting my
machine. the reason for filing this report was to clearly state what all
I've tried as the bug report filed that way didn't allow me to include
information about Randomly means exactly that. As stated before, when
the
Public bug reported:
Binary package hint: xorg
Every time my machine is idle for times ranging from 3-40 minutes X
crashes hard and I must hit reset to reboot. It never did this in
Intrepid only with Jaunty. At first I thought it was because of Ext4
drive formating, so I re-installed with ext3.
Richard: Whit Screen of Death
What's happening is your graphics driver was not updated with -19
kernel. If you can try and go into graphics safe mode/recovery mode from
the grub menu and see if you can enable your graphics card from there.
Your going to want to go into the restricted drivers
Hey pfeels, you want to download and burn a copy of the ubuntu alternate
cd from here: http://www.ubuntu.com/getubuntu/download
Make sure the check the box under the green start download button to get the
alternate disc.
(For futre reference, keep this disc handy as it's the only version of
I have this, but i'm wondering if its a separate issue as I have intel
3100 not nvidia. Is this only an nvidia bug?
This is not esculisive to nvidia chipsets. I have an ATI radeon card and
intel 3100 graphics on board and I'm havint the same problem with both
GPU's. Just did -18 upgrade via
Tried -19 version 2.0. Still had the suspend error but did not have to
jump cmos this time to reboot. behaves like -17. Thanks for trying Tim,
let me know if i should send you any info to help.
--
Kernel 2.6.24-17 - broken resume from suspend to RAM
https://bugs.launchpad.net/bugs/226279
You
Attempted 2.6.24-19 upgrade and rebooted to a white screen as there were
no drivers for my ATI card. Went into graphics safe mode and attempted
suspend. Computer suspended and I then pressed power to resume. It did
exactly the same thing as with -17 except when I did hard reboot via the
power
I can confirm this bug on a gigabyte g33m dsr2 motherboard with core 2
duo processor and ATI graphics card. I can also confirm that Tims fix
caused the computer to reduce to just spinning the drive and and
required a hard reboot to restore the system.
--
Kernel 2.6.24-17 - broken resume from
101 - 122 of 122 matches
Mail list logo
