I agree this is a issue with Unity that needs to be addressed. I like to
use the second monitor to display fullscreen apps (prime example is xbmc
on second monitor) and having the top panel unhidable ruins the
experience, which is one of the reasons I'm using gnome shell instead of
Unity right
apport information
** Tags added: apport-collected kubuntu natty patch
** Description changed:
After installing the proprietary nvidia driver in Ubuntu Natty (32bit
and 64bit tested) and rebooting, the system freezes before reaching the
login screen. The system can boot fine using the
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/770559/+attachment/2121773/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/770559
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/770559/+attachment/2121774/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/770559
Title:
Ubuntu
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/770559/+attachment/2121775/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/770559
Title:
Ubuntu
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/770559/+attachment/2121777/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/770559/+attachment/2121776/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/770559
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/770559/+attachment/2121778/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/770559
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/770559/+attachment/2121779/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/770559
Title:
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/770559/+attachment/2121780/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/770559
Title:
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/770559/+attachment/2121781/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/770559
Title:
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/770559/+attachment/2121782/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/770559
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/770559/+attachment/2121783/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/770559
Title:
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/770559/+attachment/2121784/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/770559
Title:
apport information
** Attachment added: xinput.txt
https://bugs.launchpad.net/bugs/770559/+attachment/2121785/+files/xinput.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/770559
Title:
To clarify, the information just added to the report shows nvidia-
graphics-driver as not installed because I am unable to boot with the
driver installed, so I had to uninstall it to run the apport-collect
program.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm having a problem doing that. On my 11.04 install, if I remove the
blacklist for the driver and I boot it panics and I can't change to a
tty to retrieve the logs because it's completely frozen. So I blacklist
it again from a live i386 session and boot to see if I can retrieve the
logs, but
I have been trying to get a log but I can't find anything relating to
the crash. What I've done for now is take a picture of the crash on the
screen until I get more advice on how to get the logs.
** Attachment added: Call trace of kernel panic
This pic has the text which is cut off from the last picture
** Attachment added: text which is cut off from last picture
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/768524/+attachment/2117023/+files/P1100927.JPG
--
You received this bug notification because you are a member of
Success! I have managed to use netconsole to get the error log on my
netbook after booting the machine with ethernet connected. I am
attaching it here.
** Attachment added: netconsole.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/768524/+attachment/2117396/+files/netconsole.log
--
I was unable to get any kernel logs directly from the machine, but I was
advised by someone to use netconsole to get the Kernel Oops and I am
attaching it here. In line 26 you can see the Oops occur after the
nvidia driver is loaded. I hope this helps uncover the problem.
Cheers,
Matt
**
*** This bug is a duplicate of bug 770559 ***
https://bugs.launchpad.net/bugs/770559
I can confirm this bug affects me with the same nvidia 9300 igp from
zotac on both 32 and 64 bit versions of natty. I also filed a bug report
(https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
This problem still persists after yesterdays release so I can't upgrade
to Natty at this time without losing support for my nVidia card. What
extra information do I need to give?
I've done some more messing about to see if I can fix the problem. I
added the x-swat ppa to my Maverick system to see
I can confirm the problem is with the amd64 vt6656 driver. I downloaded
yesterdays release and the live cd would not boot, with a kernel panic
being shown after the splash screen. I unsquashfs'ed the
filesystem.squashfs file, added vt6656_stage to the blacklist file and
re-added the file to the
Public bug reported:
After installing the proprietary nvidia driver in Ubuntu Natty (32bit
and 64bit tested) and rebooting, the system freezes before reaching the
login screen. The system can boot fine using the nouveau package, but as
soon as nvidia-current is installed the system crashes.
I seem to be affected with a similar bug to this, I have reported it at
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers/+bug/770559 . None of the workarounds here work so I don't think
it's plymouth related.
--
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: linux-image
Booting the 64bit Natty beta2 live cd fails with a kernel panic on my
system where the 32bit image works fine. Installing using the alternate
cd works, but then booting the installed system fails with a kernel
panic too. After looking at the
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/768524
Title:
Kernel Panic on boot because of vt6656_stage driver
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Further - as a small test the other day I built vlc 1.0.6 on lucid
statically linked to faad2 -2.6.1 (source used in karmic)
It plays aac LC files fine, exhibited the same (mis)behavior with aac
Main
another indication that the libfaad2 package fails to playback aac main
thanks for your
This is quite a severe problem for me as I have encoded hundreds of
files in previous versions of Ubuntu using gstreamer and all these files
are now useless to me in Lucid.
--
Severe sound problem playing some aac files
https://bugs.launchpad.net/bugs/575798
You received this bug notification
please attach such files to this bug so that we can verify that
claim.
Here's a sample file which doesn't play correctly.
Matt
** Attachment added: new.m4a
http://launchpadlibrarian.net/47927428/new.m4a
--
Severe sound problem playing some aac files
https://bugs.launchpad.net/bugs/575798
I don't know what to put it against, it happens in most audio players
including Rhythmbox, Totem and VLC, It doesn't happen with XBMC or
Aqualung. Here's a sample file which is affected http://drop.io/lwx4fgt
, this file plays fine in previous versions of Ubuntu, and in other
OS's, but won't play
** Description changed:
Binary package hint: alsa-base
When playing some aac files (.m4a extension) in Lucid Lynx the sound is
corrupted so that every split second there is a high pitched screeching
noise and skipping. These files play perfectly in Karmic, Arch with all
packages
I started a thread in the forum about the bug
http://ubuntuforums.org/showthread.php?t=1473550
** Package changed: alsa-driver (Ubuntu) = ffmpeg (Ubuntu)
--
Severe sound problem playing some aac files
https://bugs.launchpad.net/bugs/575798
You received this bug notification because you are a
Public bug reported:
Binary package hint: alsa-base
When playing some aac files (.m4a extension) in Lucid Lynx the sound is
corrupted so that every split second there is a high pitched screeching
noise and skipping. These files play perfectly in Karmic, Arch with all
packages updated, and
I can confirm this problem after upgrading from Jaunty to Karmic. The
problem exists even when booting in recovery mode from the Jaunty kernel
after upgrading to Karmic.
--
Karmic - Corrupted Recovery Menu
https://bugs.launchpad.net/bugs/458352
You received this bug notification because you are
This is quite a serious issue as the recovery mode is completely
unusable in its current state ...
--
Karmic - Corrupted Recovery Menu
https://bugs.launchpad.net/bugs/458352
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I've tried compiling this driver with kernel 2.6.31 and it's not
possible at the moment. And googling it seems that other people are also
experiencing this problem. I suppose this means this driver won't be
available in Karmic, unless someone patches it.
--
VT6656 wireless chipset is unsupported
38 matches
Mail list logo
