[lucid] crashes after first CTRL+C pressing

Bug #519460 reported by Pavol Klačanský
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

When I boot to lucid and then I press CTRL+C to copy some string, Xorg crashes and I must login again, after that annoying "feature", everything works properly

Revision history for this message
Gabe Gorelick (gabegorelick) wrote :

Interesting bug, what's probably happening is that the Ctrl-C is getting passed to some program that it shouldn't be, signaling a kill.

tags: added: needs-reassignment
Revision history for this message
Pavol Klačanský (pavolzetor-deactivatedaccount) wrote :

yes, it kills Xorg or GDM, I have to login again, it 's terrible
how can I fix it?

Revision history for this message
Gabe Gorelick (gabegorelick) wrote :

Not sure what package this belongs in, but gdm is a better guess than no package.

affects: ubuntu → gdm (Ubuntu)
Revision history for this message
Pavol Klačanský (pavolzetor-deactivatedaccount) wrote :

I removed plymouth and problem has gone

affects: gdm (Ubuntu) → plymouth (Ubuntu)
Revision history for this message
Steve Langasek (vorlon) wrote :

Please run 'apport-collect -p plymouth 519460'.

Changed in plymouth (Ubuntu):
status: New → Incomplete
Revision history for this message
Pavol Klačanský (pavolzetor-deactivatedaccount) wrote :

I have run it, but I think it failed

tags: added: apport-collected
tags: removed: needs-reassignment
Revision history for this message
Steve Langasek (vorlon) wrote :

It looks like we may be running into bug #519460 in apport.

Revision history for this message
Gabe Gorelick (gabegorelick) wrote :

I don't think you mean bug #519460 in apport, since that is actually this bug. ;)

Revision history for this message
Steve Langasek (vorlon) wrote :

<cough> indeed, I meant bug #516381

Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (4.1 KiB)

This bug was fixed in the package plymouth - 0.8.0~-13

---------------
plymouth (0.8.0~-13) lucid; urgency=low

  [ Steve Langasek ]
  * Don't attach /proc/cmdline to apport reports, this is already in the
    standard info that gets collected...

  [ Alberto Milone ]
  * ubuntu_logo theme:
    - New logo from Otto Greenslade.
    - Switch off dots starting from the ones on the left instead of
      switching them off all at once.

  [ Scott James Remnant ]
  * Move the Ubuntu logo up as discussed with Otto, this makes the mouse
    cursor appear between the logo and dots and solves the optical illusion
    of the logo being too low. LP: #535014.
  * Don't include message about disk checks, which can come from mountall.
  * Drop the rc script splash functions, we don't want the SysV-rc compat
    stuff messing around with the splash screen - this can be entirely
    managed by Upstart now. LP: #528787, #537262.

  * Plymouth Fix Mega Patch:
    - This hasn't yet been broken up into enough bits to send upstream, and
      doesn't *quite* address all the issues yet, but it's a major step.

    - Rewrite the VT handling, rather than abusing /dev/tty0 keep all VT
      operations on the actual VT (tty7), this avoids issues where we set
      the graphics mode of the wrong VT or put the wrong VT into VT_PROCESS
      mode. LP: #520460, #522598, #526321, #533135
    - Don't attempt VT switch when using non-VT consoles.
    - Make VT mandatory for renderer plugins, so we fallback gracefully to
      text when the console is not a VT. LP: #516825, #527083.
    - Restore VT when finished displaying the splash unless plymouth quit
      is called with --retain-splash. LP: #506297.
    - Activate VT from text and details plugins, rather than haphardly in
      the main code, this means the textual boot is also on VT7.
      LP: #518352, #520122.
    - Add a --has-active-vt command that can let gdm inquire whether it
      should reuse Plymouth's VT; fixes the issue where Plymouth has no
      visible splash screen and X ends up on VT1. LP: #519641, #533572.

    - Don't open terminal device in X11, fixes the issue where X will crash
      when debugging plugins using the X11 renderer.
    - Add --tty option to plymouthd for debugging when X is running and
      thus using an alternate VT.

    - Improve deactivate command so that the terminal is no longer watched
      for keyboard input, session is closed, etc. LP: #528787, #531650.
    - Ignore mode changes while deactivated, otherwise we can end up
      resetting the VT back into text mode while X is starting up.
      LP: #523788, #502509.

    - Fix races with simultaneous quit and deactivate commands, or multiples
      of those commands.
    - Ignore --show-splash, --hide-splash, etc. commands while deactivated.
    - Add reactivate command for testing purposes.

    - Don't scan out drm buffer contents to fbcon when not called with
      quit --retain-splash. LP: #527180.

    - Avoid resetting the terminal to unbuffered mode on every write, this
      results in setting X's VT into raw mode and results in the X server
      crashing on key presses. LP: #532047, #534861, #519460, #520...

Read more...

Changed in plymouth (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.