[Bug 1397553] Re: 1002:9802 The Linux kernel is no longer able to page the graphics processor, making the system to boot with a blank screen

Please, do. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397553 Title: 1002:9802 The Linux kernel is no longer able to page the graphics processor, making the system to boot with a blank screen

[Bug 1397553] Re: 1002:9802 The Linux kernel is no longer able to page the graphics processor, making the system to boot with a blank screen

As of the latest kernel update (3.16.0-28.38) I am still getting this error happening. My graphics hardware is an AMD Radeon HD 6670 using the open source drivers. Sabertooth 990FX R2.0 motherboard. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1380974] [NEW] [To be filled by O.E.M. To be filled by O.E.M.] suspend/resume failure

Public bug reported: Crashed on attempting to resume from suspend. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-22-generic 3.16.0-22.29 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 Annotation: This occured

[Bug 1379402] Re: gnome-panel crashed with signal 5 in _XReply()

*** This bug is a duplicate of bug 1293252 *** https://bugs.launchpad.net/bugs/1293252 Attempting to run Wasteland 2 again results in this appearing on the command line (GNOME panel crashing): (gnome-panel:12259): Gdk-ERROR **: The program 'gnome-panel' received an X Window System error.

[Bug 1379402] [NEW] gnome-panel crashed with signal 5 in _XReply()

*** This bug is a duplicate of bug 1293252 *** https://bugs.launchpad.net/bugs/1293252 Public bug reported: GNOME-Panel aborts with SIGTRAP (Signal 5) when executing some Unity- based games (notably, Wasteland 2). It does not auto-restart and must be restarted via other means (e.g. command

[Bug 1379402] Re: gnome-panel crashed with signal 5 in _XReply()

*** This bug is a duplicate of bug 1293252 *** https://bugs.launchpad.net/bugs/1293252 Also, this is probably not a GNOME Panel issue, or a Wasteland 2 issue, per se - it appears to be driver-related. It does not do this using the open source AMD drivers, only fglrx. -- You received this

[Bug 1375450] Re: vlc assert failure: *** Error in `/usr/bin/vlc': free(): invalid next size (fast): 0x00007fa2c4cca3b0 ***

** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1375450 Title: vlc assert failure: *** Error in `/usr/bin/vlc': free(): invalid next size (fast):

[Bug 1299428] [NEW] kernel BUG at /build/buildd/linux-3.13.0/mm/slub.c:3365!

Public bug reported: Error always occurs on start-up. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-19-generic 3.13.0-19.40 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic i686 NonfreeKernelModules: fglrx Annotation: Your

[Bug 1166947] [NEW] st2.py crashed with AttributeError in rowno(): 'NoneType' object has no attribute 'get_path'

Public bug reported: Attempting to edit bookmarks the program crashed. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: streamtuner2 2.0.8-5 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Uname: Linux 3.8.0-17-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu5

[Bug 979071] Re: nepomukservicestub crashed with SIGSEGV in QObject::~QObject()

** Visibility changed to: Public -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-runtime in Ubuntu. https://bugs.launchpad.net/bugs/979071 Title: nepomukservicestub crashed with SIGSEGV in QObject::~QObject() To manage notifications

[Bug 973323] Re: pidgin crashed with SIGABRT in raise()

** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/973323 Title: pidgin crashed with SIGABRT in raise() To manage notifications about this bug go to:

[Bug 969268] Re: plymouthd crashed with SIGABRT in raise()

** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969268 Title: plymouthd crashed with SIGABRT in raise() To manage notifications about this bug go to:

[Bug 969410] Re: Xorg crashed with SIGABRT

** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969410 Title: Xorg crashed with SIGABRT To manage notifications about this bug go to:

[Bug 946349] Re: soffice.bin crashed with SIGSEGV in QCoreApplication::notifyInternal()

** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/946349 Title: soffice.bin crashed with SIGSEGV in QCoreApplication::notifyInternal() To manage notifications about

[Bug 858111] Re: apport-kde crashed with RuntimeError in __main__: the PyQt4.QtCore module is version 1 but the PyKDE4.kdecore module requires version -1

** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/858111 Title: apport-kde crashed with RuntimeError in __main__: the PyQt4.QtCore module is version 1 but the

[Bug 760665] Re: soffice.bin crashed with SIGSEGV in Window::GetAccessible()

** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/760665 Title: soffice.bin crashed with SIGSEGV in Window::GetAccessible() -- ubuntu-bugs mailing list

[Bug 88504] Re: Screen corruption.

I am also using the DRI drivers for my Radeon 9200. Is this a driver- related issue, somehow? -- Screen corruption. https://bugs.launchpad.net/bugs/88504 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list

[Bug 88504] Re: Screen corruption.

The problem always occurs with GNOME Terminal. Not using any accessibility features, no Compiz/Beryl/XGL/AIGLX. Opensource ATI drivers. -- Screen corruption. https://launchpad.net/bugs/88504 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 88504] Re: Screen corruption.

** Attachment added: Example of 'cursor'-over-text corruption. http://librarian.launchpad.net/6583575/CursorCorruption.png -- Screen corruption. https://launchpad.net/bugs/88504 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 85575] Re: gnome-terminal reacting very sluggishly

Not quite fixed, as the screenshot shows (incomplete status bar, what looks like a cursor block over my typing). ** Attachment added: Screen corruption, GNOME Terminal 2.17.92/VTE 0.15.4. http://librarian.launchpad.net/6561186/Corrupt2.png -- gnome-terminal reacting very sluggishly

[Bug 85575] Re: gnome-terminal reacting very sluggishly

Reported. https://launchpad.net/ubuntu/+source/gnome-terminal/+bug/88504 -- gnome-terminal reacting very sluggishly https://launchpad.net/bugs/85575 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 88504] Screen corruption.

Public bug reported: Binary package hint: gnome-terminal There appears to be some random screen corruption in GNOME Terminal, as of 2.17.92 (VTE 0.15.4). The latest versions of each seem to have made little difference to the issue (missing characters, cursor block appearing over typed input).

[Bug 88504] Re: Screen corruption.

Attached screenshot demonstrates corruption. ** Attachment added: Screenshot showing terminal corruption. http://librarian.launchpad.net/6561810/Corruption3.png -- Screen corruption. https://launchpad.net/bugs/88504 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 85575] Re: gnome-terminal reacting very sluggishly

Not just slower, but there is also screen corruption (missing/partially drawn characters). ** Attachment added: Visual of screen corruption using GNOME Terminal 2.17.91. http://librarian.launchpad.net/6493272/Corruption.png -- gnome-terminal reacting very sluggishly

[Bug 85575] Re: gnome-terminal reacting very sluggishly

Has anyone been able to confirm if this is a VTE issue, or an issue with another of the GTK+ libraries? -- gnome-terminal reacting very sluggishly https://launchpad.net/bugs/85575 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 85575] Re: gnome-terminal reacting very sluggishly

Indeed this is not just an issue with GNOME Terminal. I have seen similar problems with XFCE's terminal. As Konsole does not show these issues, it is likely related to the GTK+ family of libraries (which both GNOME and XFCE use). -- gnome-terminal reacting very sluggishly

[Bug 85575] Re: gnome-terminal reacting very sluggishly

Yes, both GNOME Terminal and XFCE4 Terminal use VTE. Konsole does not. -- gnome-terminal reacting very sluggishly https://launchpad.net/bugs/85575 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 65710] Re: kernel panic on edgy RC

Is this linked to https://launchpad.net/distros/ubuntu/+source/linux- source-2.6.17/+bug/61848 at all? -- kernel panic on edgy RC https://launchpad.net/bugs/65710 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 61848] Re: [edgy] kernel panic after last update

acpi=force never worked under the older kernel (2.6.15) for me, and doesn't with the newer one, either. noapic doesn't do much on my hardware, either and nor does pnpbios=off. Still no joy as of 22nd October. -- [edgy] kernel panic after last update https://launchpad.net/bugs/61848 --

[Bug 61848] Re: [edgy] kernel panic after last update

2.6.17-10-386 appears to work (was using the generic kernel before) without need for any extra boot parameters. -- [edgy] kernel panic after last update https://launchpad.net/bugs/61848 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 61848] Re: [edgy] kernel panic after last update

Tried acpi=off and force, with pnpbios=off, nolapic and noapic options... nothing works, 2.6.17-31 does not boot under any circumstances on this machine. VT8378 (KM400/A) motherboard. Athlon XP 2000+. -- [edgy] kernel panic after last update https://launchpad.net/bugs/61848 -- ubuntu-bugs