Invalid is a misnomer, because it is valid, but has been ignored long
enough that at some point it got fixed in due process, but only in later
releases.
(Marking invalid, anyway, because there is no way for me to mark it
will not fix (or will ignore and hope it magically gets fixed ;-).
**
Suspend seems more than 99% reliable in 11.10 (Oneiric), which is 2-3
orders of magnitude better, and good enough. I'm content closing this
bug (Won't fix?).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I'm running gnome-session-fallback, if that matters.
I'm trying to rip a DVD. Launching brasero from a terminal with gdb...
Click on Disc copy. Copy CD/DVD window appears, with Select disc to
copy pulldown blank gray, and Select a disc to write to pulldown says
New disc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/931230
Title:
Brasero display problems and crashes
To manage notifications about this bug go to:
Public bug reported:
Bug #664161 could be the same bug, by my reading, but I'm on a different
hardware platform, so here goes...
Upgraded to Maverick Meerkat, and suspend usually fails, about 9 times
out of 10. Screen will go black, the moon indicator LED will usually
flash, sometimes forever,
** Attachment added: output of ubuntu-bug --save=ubuntu-bug.out linux
https://bugs.launchpad.net/bugs/670685/+attachment/1722258/+files/ubuntu-bug.out
--
suspend usually fails
https://bugs.launchpad.net/bugs/670685
You received this bug notification because you are a member of Ubuntu
Bugs,
I installed the mainline kernel 2.6.35-02063508-generic (from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35.8-maverick/), and
I was just able to successfully suspend and resume twice in a row.
--
suspend usually fails
https://bugs.launchpad.net/bugs/670685
You received this bug
...hmm...Then it failed one, worked once, then failed again...
I'm seeing messages like this appear on the console:
Nov 3 18:40:50 pc kernel: [ 1015.272615] [drm:atom_op_jump] *ERROR* atombios
stuck in loop for more than 1sec aborting
Nov 3 18:40:50 pc kernel: [ 1015.272620]
egad, and apologies. I had a version of kino installed in /usr/local
which was taking preference over the Ubuntu version. I removed it and
kino successfully starts up for me now. blush
I'd suggest closing this bug report as was previously done on 2008-09-05
(since I'm not the original bug
Yes, it failed identically after I updated everything, rebooted, and ran
kino yesterday.
--
kino stalls when opening
https://bugs.launchpad.net/bugs/135456
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
A few details...
# uname -r
2.6.27-7-generic
Probably unrelated message which appears early:
/usr/share/themes/Human/gtk-2.0/gtkrc:273: Unable to locate image file in
pixmap_path: panel_bg.png
And this message appears quite a number of times:
(kino:6755): Gtk-WARNING **: GtkSpinButton: setting
Public bug reported:
Binary package hint: libpam0g
running upgrade-manager -d on an 8.04 system to upgrade to 8.10 alpha6, I see:
---
Preparing to replace libpam0g 0.99.7.1-5ubuntu6.1 (using
.../libpam0g_1.0.1-4ubuntu4_amd64.deb) ...
Unpacking replacement libpam0g ...
Setting up libpam0g
** Attachment added: /var/log/dist-upgrade/apt.log
http://launchpadlibrarian.net/18105944/apt.log
--
libpam0g error while upgrading from 8.04 to 8.10 alpha6
https://bugs.launchpad.net/bugs/276777
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: /var/log/dist-upgrade/apt-term.log
http://launchpadlibrarian.net/18105958/apt-term.log
--
libpam0g error while upgrading from 8.04 to 8.10 alpha6
https://bugs.launchpad.net/bugs/276777
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: /var/log/dist-upgrade/main.log
http://launchpadlibrarian.net/18105969/main.log
--
libpam0g error while upgrading from 8.04 to 8.10 alpha6
https://bugs.launchpad.net/bugs/276777
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: /var/log/dist-upgrade/main_pre_req.log
http://launchpadlibrarian.net/18105990/main_pre_req.log
--
libpam0g error while upgrading from 8.04 to 8.10 alpha6
https://bugs.launchpad.net/bugs/276777
You received this bug notification because you are a member of Ubuntu
Bugs,
I just upgraded a copy of my Hardy install to 8.10 alpha 6, and kino
still hangs immediately upon launch.
--
kino stalls when opening
https://bugs.launchpad.net/bugs/135456
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
just rebooted, and the upgrade appears to have gone successfully
--
libpam0g error while upgrading from 8.04 to 8.10 alpha6
https://bugs.launchpad.net/bugs/276777
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Changed in: kino (Ubuntu)
Status: Invalid = New
--
kino stalls when opening
https://bugs.launchpad.net/bugs/135456
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
I just upgraded to Hardy, and I see this exact problem. I'll be happy
to provide any information. Can I reopen this bug, or must I open a new
one?
--
kino stalls when opening
https://bugs.launchpad.net/bugs/135456
You received this bug notification because you are a member of Ubuntu
Bugs,
I have the same motherboard, and just installed Feisty Fawn. I can
confirm that it picked nv driver for X, but the X server display was
mangled (or black), and Ctrl-F1 got me to an unreadable/mangled
console. It looked a lot like UPC codes. I was able to chroot into the
partition and install
I downloaded 6.06.1 yesterday, and I think observed the same problem, on
an IBM Netfinity. Boot of the CD hangs/becomes unreadable at Mounting
root filesystem, which I think is right after drivers are loaded.
--
Dapper install boots but cdrom fails on Dell CPt S600GT
22 matches
Mail list logo
