Bug 19967 - regression in switching to virtual terminal
Summary: regression in switching to virtual terminal
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: 7.4 (2008.09)
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-05 08:04 UTC by Hervé Cauwelier
Modified: 2009-02-11 08:28 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
log of the crashing X (25.75 KB, application/x-trash)
2009-02-05 08:04 UTC, Hervé Cauwelier 		no flags Details
log of the respawned X (25.18 KB, text/x-log)
2009-02-05 08:05 UTC, Hervé Cauwelier 		no flags Details
xorg.conf (2.00 KB, application/octet-stream)
2009-02-05 08:05 UTC, Hervé Cauwelier 		no flags Details
View All

Description Hervé Cauwelier 2009-02-05 08:04:53 UTC 
Created attachment 22611 [details]
log of the crashing X

regression in switching to virtual terminal

I'm quite happy with the efforts to improve the performance of switching desktops and resizing windows.

But since then, switching to the VT and switching back to X makes X crash with signal 11.

Attaching the logs.

I'm using nouveau/master and drm/master.
Comment 1 Hervé Cauwelier 2009-02-05 08:05:41 UTC 
Created attachment 22612 [details]
log of the respawned X
Comment 2 Hervé Cauwelier 2009-02-05 08:05:56 UTC 
Created attachment 22613 [details]
xorg.conf
Comment 3 Hervé Cauwelier 2009-02-05 08:07:32 UTC 
Sorry, it's a GeForce 8400M GS.

01:00.0 VGA compatible controller: nVidia Corporation GeForce 8400M GS (rev a1) (prog-if 00 [VGA controller])
Comment 4 Maarten Maathuis 2009-02-05 08:12:43 UTC 
I have encountered the same, for some reason the framebuffer is failing to allocate and we're not gracefully handling that, so that's (at least) two bugs.
Comment 5 Hervé Cauwelier 2009-02-11 08:28:09 UTC 
It's all fixed to me. Thanks!

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.