Pressing <Enter> causes X to freeze

[Zaphod]

Binary package hint: plymouth

I am running ubuntu 10.04 Alpha2 and after last nights updates pressing the enter key causes the whole system to freeze and I have to hard reboot.

Only removing Plymouth would allow me to work normally.

The system still respond to ssh.

WORKAROUND (thanks to Simon Baconnais): kill X by pressing Ctrl+Alt+Print+K fixes the problem until the next reboot.

[Harry (harry33)]

This is true.
I have Nvidia graphic card (285 GTX) and 64-bit Lucid-alpha2.
This makes using terminal impossible.
As a workaround one has to downgrade the packages "plymouth" and "libplymouth2" back to the version 0.8.0~-7

So just download the packages (64-bit lucid) from:
https://edge.launchpad.net/ubuntu/lucid/amd64?text=plymouth
and then reboot to recovery mode, drop to terminal, go to the directory where you downloaded packages, then run:
dpkg -i plymouth_0.8.0~-7_amd64.deb libplymouth2_0.8.0~-7_amd64.deb
and reboot.

[Alfredas Beinartas (fuxialis)]

Same here. Nvidia 7900 GS ant 64-bit Lucid-alpha2. System seems completely frozen but reboots with Alt+SysRq+b. So maybe it is only graphics problem. Temporareliy solved this problem by removing Plymouth.

[Harry (harry33)]

This bug does not seem to affect 32-bit installations. At least those with ATI cards.
I tested this with 32-bit Lucid-alpha2 in a laptop with ATI Mobility Radeon 9700.

[Mike (bild85)]

Happens for me using 32-bit w/nvidia on a Latitude D630. It's as if the Enter key was remapped to a "system freeze" function. I can log in and do many tasks using the mouse to click through confirmation dialogs, but as soon as I hit the Enter key, be it at the terminal or to press a highlighted button, the system freezes and cannot be recovered. Only holding down the power button will power it off (I did not try the alt-sysRq+b sequence.)
Removed the "plymouth" package through aptitude in the recovery console and now it's fine.

$ lspci | grep -i vga
01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 135M (rev a1)

$ uname -a
Linux hostname 2.6.32-12-generic #16-Ubuntu SMP Wed Jan 27 18:34:19 UTC 2010 i686 GNU/Linux

[Zaphod (vilppu777)]

I also have an nvidia card. I think it is effecting nvidia users only.

[ROB3RT (rob3rt)]

I concur that it is only NVIDIA cards. I have an NVIDIA 9600M GT, and it happens to me too. Hopefully this can be resolved ASAP.

[Anton Kraus (done)]

Uninstalling plymouth made the bug disappear.

Two related bugs disappeared as well:
1) I'm no longer experiencing graphical corruption (flickering pixels) along the top edge of the screen.
2) Previously, when GDM came up on my Nvidia Twinview setup (two monitors), only the primary screen would work, whereas the secondary monitor just gave me an "out of range" message. The workaround was a quick switch to a TTY and back again. With Plymouth gone, both screens now work immediately.

Should I file separate bugs?

My graphics card is an Nvidia GeForce 6600LE.

[Hernando Torque (htorque)]

Nvidia 6600 GT/BLOB/32-bit: for me the enter key just kills X, after logging in again everything works fine. I remember reading somewhere that starting Plymouth in text mode while having X running will crash X - maybe that's connected?

[Hernando Torque (htorque)]

Happens also with a Go 7600/Nouveau/32-bit with KMS enabled.

[Alfredas Beinartas (fuxialis)]

Just updated to latest NVIDIA beta drver 195.36.03. Thought maybe it is a driver problem. Same hang. Tried nv driver. The same. Bug is definitely connected to NVIDIA hardware in spite of architecture or driver.

[Aron Xu (happyaron)]

I have this problem with my Nvidia 8500GT card with x86_64 Lucid installed, plymouth version 0.8.0-~8.

[YunQiang Su (wzssyqa)]

it effect me.too.
i am using lucid amd64,and geforce 8600m gs,with nvidia's 195.30 driver.

but,i seem not only press enter key,and using mouse.

[Simon Baconnais (smon-deactivatedaccount)]

Same thing here with lucid amd64 and Intel Corporation Mobile 945GM/GMS

[ROB3RT (rob3rt)]

Yes, the flickering pixels have also come up for me too, and are extremely annoying. I believe that this bug should be marked High importance.

[christian (chmathieu)]

I have the same bug with ATI 9550.

[Simon Baconnais (smon-deactivatedaccount)]

Upgrades this morning have solved the problem :)

[Hernando Torque (htorque)]

I still can reproduce it.

[Elfy (elfy)]

Still an issue here for me

[Simon Baconnais (smon-deactivatedaccount)]

Okay, i think i have a solution !

Actually, this morning xserver-xorg-video-intel have been upgraded and it have solved the problem.

But a few minutes ago i had a new plymouth upgrade that brought back the problem.

So I tried to reinstall xserver-xorg-video-intel, and it solved the problem.

I think that plymouth upgrades just break the xorg conf (or something like that), but an aptitude reinstall xserver-xorg-video-intel (or ati, or nv, etc.) can fix it :)

[phillamg (me-phillg)]

I'm running an AMD64 system with a NVidia card and I managed to get things working again (without a reboot) by re-installing xserver-common, xserver-xorg-core, xserver-xorg-video-intel and nvidia-current through GDebi (used nautilus to go to /var/cache/apt/archives). Hope that helps someone else, sorry I didn't have time to narrow it down to just one package!

[Elfy (elfy)]

Updated and reinstall of plymouth and all is well here now. No re-installing of any other packages were necessary for me

[jnns (jnns)]

This issue is also discussed here: http://wiki.archlinux.org/index.php/GNOME#Gnome.2FXorg_crashes_randomly_when_the_enter_key_is_pressed
http://bugs.archlinux.org/task/17472

[Harry (harry33)]

Jannis, actually the Arch-linux Gnome problem is a different issue, nothing to do with plymouth.

Those having a Nvidia graphics card really should use Nvidia proprietary drivers (nvidia-current).
And in fact what plymouth is for the time being, it is pretty useless with Nvidia.
I think it is better to remove the package plymouth from lucid, the problems will disappear.
Then you can upgrade the package libplymouth2.
I also have found out that plymouth slows down the boot process and shutdown process in lucid.

[Hernando Torque (htorque)]

I can confirm that reinstalling the video driver works, whereas reinstalling Plymouth didn't change a thing.

[Fred (ian-bews)]

AMD64 with 7900GT GX2

Tried reinstalling xserver-xorg-video-nv -still freezes on enter.

Tried reinstalling plymouth -still freezes on enter.

What's with plymouth on nvidia anyway? I haven't seen a lucid splash screen on this machine ever :-(

[phenest (steve-clark)]

nVidia 7950GTX here. Removing plymouth fixed it.

[Eddie Ringle (eddie.ringle)]

I started experiencing the problem a few minutes ago when I upgraded Plymouth to 0.8.0~-9.
I removed it, rebooted, and it fixed the problem.

Good riddance, my boot-up is faster without it.

[Fred (ian-bews)]

Removed Plymouth (was using 0.8.0~-9) and I can now press enter again.

[Yann Dìnendal (yannbreliere)]

Hi, I have the same problem. I also have an NVidia card (and plymouth has never shown me any graphical boot).

But I have noticed something else : if I type the key « (or maybe any other unicod character, I haven't tried), it would crash my gnome session and return to GDM. I believed it was not the same problem at all… But once I do that and my session crashes, I can then type ENTER or the "«" key without any problem !

I would gladly give more details or try some tests if it could help.

[Yann Dìnendal (yannbreliere)]

Oh, There might be a confirmation of what I was saying on duplicate bug #516807 :

> The computer automatically randomly logged me out, and it no longer crashes when hitting enter. IT only crashes when hitting enter after startup. Very weird...

yankeeboy254, did you noticed if you were logged out after typing some particular character?

[ROB3RT (rob3rt)]

As a matter of fact, any time I press SHIFT + 2, for the @ symbol when signing into my email, it does log me out. Then, when I log back in, it doesn't happen any more... It is very, very strange, but it only happens sometimes when I press SHIFT + 2, AKA @. This is the strangest bug I've ever seen...

I'd also like to suggest that this be moved up to critical, as it affects many people (30). I'm not sure how many people the bug needs to be affected by for it to be critical, but this is one heckuva important bug.

Anyone know what exactly Plymouth is doing to cause this? It has something to do, with Plymouth, and the NVIDIA drivers... I'm not sure how they relate, but all I know is that I can't successfully reboot, or shut down until this is fixed... Hard boots are bad for your HDD, so I hope this gets resolved ASAP!

[Steve Langasek (vorlon)]

My current understanding is that this is likely to be a side effect of broken VT switching code in plymouth, an issue that we're expecting to receive an upstream fix for later this month.

[ROB3RT (rob3rt)]

Wow... This is the strangest bug I've ever seen. I've never seen anything as simple as this, cause such a big issue. I also hope to see improved NVIDIA drivers which are... Not decent... I also really want to see improved Flash support, because in Karmic we took a step forward, and now we've taken 2 steps back... Something I assume will be improved in the final releases.

And, for the record. THIS is why I love open source. If this happened in Windows, we wouldn't see a fix for this until the Fall.

[Simon Baconnais (smon-deactivatedaccount)]

Ok, my bad ...

Reinstalling xserver-xorg-video-* doesn't fix this bug :P

But, in my case, killing X by Ctrl+Alt+Print+K fix the problem until the next reboot.

Hop it will help you ...

[Michal Matyska (michal-matyska)]

+1 ... removing plymouth has helped.

But not just to waste digital space I have to add, that I saw graphical boot with Nvidia graphic card. It was working for about 2 days on lucid (daily updated) and what I can recall is that it was between nuoveau and lbm?-nuoveau (real module name, not alias) was put on blacklist. But cannot find that text in plymouth changelist - was it another package?

[ROB3RT (rob3rt)]

Hey, I think I have a solution. Temporarily at least, as the other one doesn't work for me. Anytime I type in a number (1-9), into anything, such as a search bar, I am auto-logged out. Then, I log back in, and it is fine! It doesn't work all the time, but I'm going to do some more testing with it to see if I can get exact specs.

[ROB3RT (rob3rt)]

I HAVE DONE IT!!! I have found a permanent temporary solution! Okay, as soon as you boot up, go into firefox or anything with a search bar. I use my dictionary search bar that I have on my top panel. Then, just click on the search bar, and press 2. You will be logged out. Just log back in, and the problem is solved! I don't know if it will work for anyone else, but it works great for me! I suggest doing it as soon as you boot up. Can somebody else try this and see if it works. As soon as you press 2 into the search bar, you should be auto-logged out, so do this as soon as you boot up, so you don't lose any work.

[Harry (harry33)]

Yankeeboy254,
I would not call that a solution.
A solution is to remove the package plymouth until it is fixed.
See post #32 of Steve Langasek.

[Harry (harry33)]

It seems this is quite a big and widely affecting nasty bug.
With NVidia you get the <enter> freeze, not much more,
but with Intel and ATI you get freeze during boot etc. and that one is reported here:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/510524

[Steve Langasek (vorlon)]

The vast majority of Intel users are not seeing such freezes. And bug #510524 discusses Intel only, not ATI; anyone seeing problems on ATI video should open a separate bug report.

[ROB3RT (rob3rt)]

@Harry,
I agree, that it is not a solution, but a temporary problem... Fixer... This is until a permanent fix is implemented, which will probably come with the Alpha 3. I sincerely don't want to install Plymouth, because I really don't want to mess around with system files... Bad experiences with 9.10 alpha releases... Bad experiences....

[shankao (shankao)]

The current workaround described in the bug description is lots simpler and works from the very beginning of the login screen.
If you find a simpler one or something that fixes the problem in a permanent way *and* is consistent with the Ubuntu upgrade policies, feel free to describe it in the bug description.

[[e-mail] (fz420)]

Removed Plymouth (was using 0.8.0~-9) and I can now press enter again.
me too

[Theo Nolte (theo-nolte)]

same problem here with 64-bit and nvidia. Pressing Ctrl-Alt-Print-K works for me. Blinking pixels on the top of the screen disappear and I can press ENTER again to login.

[Yann Dìnendal (yannbreliere)]

I did'nt have the problem for this boot! I had a fsck during the boot, it might be linked…

[Niels Egberts (nielsegberts)]

On Mon, Feb 8, 2010 at 9:24 PM, Yann Dìnendal <email address hidden> wrote:
> I did'nt have the problem for this boot! I had a fsck during the boot,
> it might be linked…

Probably not.

[Casey J Peter (caseyjp1)]

64bit ubuntu + nvidia proprietary drivers here using nvidia gtx260oc

alt+printscrn+k restarts gdm. This restart works and no further issues until the next boot. Until plymouth is fixed later, this will bypass the lockup. The gdm restart only takes a couple seconds, so leaving plymouth installed as part of the "alpha" seems the way to go here.
No issues with gfx or other after log in is complete.

[Harry (harry33)]

Please note, that there are other issues regarding the package plymouth, with NVidia card and nvidia-current drivers.
For example you should measure the time your system takes to shut-down (or restart if you will).
With plymouth installed it takes 2-3 secs more time.
Also, there is clearly a noticeable difference concerning boot-up time too.

[Claudio Moretti (flyingstar16)]

Regarding the workaround mentioined in comment 1, after downgrading the package you may want to prevent automatic upgrades pf plymouth and libplymouth2
To do this, open a root terminal and give the following commands:
# dpkg --set-selections
plymouth hold
libplymouth2 hold

and exit with Ctrl+D (NOT Ctrl+C)

To revert back when this will be fixed:

# dpkg --set-selections
plymouth install
libplymouth2 install

and exit again with Ctrl+D

To check the package status
# dpkg --get-selections plymouth
# dpkg --get-selections libplymouth2

[emarkay (mrk)]

FWIW it happens with both ATI (HD2600) and NVIDIA (FX1500M) graphics here.

[ROB3RT (rob3rt)]

I'd just like to add that I get an fsck every time I boot. So, it may very well be related. Just saying.

[Steve Langasek (vorlon)]

Could those experiencing this issue please try installing the attached file in /etc/init/plymouth-splash.conf on your systems (with the plymouth package installed, of course), and report whether it makes a difference?

[yasaswi (yasaswi-lakkaraju)]

Steve: I tried you conf file, it made no difference. The system freezes once I hit enter.

Workaround that worked for me:

at grub select recovery mode. select drop to root option and just enter "start gdm". once gdm comes up I am able to use enter key without any issue. I read this/similar work around on another bug report.

[Niels Egberts (nielsegberts)]

On Wed, Feb 10, 2010 at 10:15 AM, yasaswi <email address hidden> wrote:
> at grub select recovery mode. select drop to root option and just enter
> "start gdm". once gdm comes up I am able to use enter key without any
> issue. I read this/similar work around on another bug report.

I think thats essentially the same workaround as 'sudo aptitude remove
plymouth' as you skip the graphical startup.

[Hernando Torque (htorque)]

That plymouth-splash.conf works for me (no PPAs, Nvidia BLOB).

[Tom Louwrier (tom-louwrier)]

Had the same problems on my wife's laptop, a Dell XPS 1530 (Intel CPU, Lucid 64bit, NVidia GForce 8600M GT card).
Uninstalling Plymouth seems to have solved it for now (although I think that is not what the devs of Plymouth aimed for...).
Thanx for the information guys.

cheers
Tom

[Steve Langasek (vorlon)]

Rather than just uninstalling plymouth, please test the partial solution from <https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/516412/comments/52>.

Also, when reporting results, please mention if you see the Ubuntu logo splash screen before gdm starts.

[Christian Victor (post-kerm-it-deactivatedaccount)]

Tested the mentioned plymouth-splash.conf

<Enter> can be pressed now without freezing but I could not see the
Ubuntu logo

Am Mittwoch, den 10.02.2010, 19:40 +0000 schrieb Steve Langasek:
> Rather than just uninstalling plymouth, please test the partial solution
> from
> <https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/516412/comments/52>.
>
> Also, when reporting results, please mention if you see the Ubuntu logo
> splash screen before gdm starts.
>

[Elfy (elfy)]

Using the plymouth.conf in comment 52 - I have control of my enter key again.

No splash logo seen at all.

[Hernando Torque (htorque)]

Tested the plymouth-splash.conf on a second system with xorg-edgers/nouveau PPA enabled (0.8.0~-10~nouveau): pressing enter doesn't lock up the system and I'm seeing the Ubuntu logo.

[Steve Langasek (vorlon)]

Sorry, it seems I need to collect a bit more information from testers to really see whether we're making progress here. If you're testing the fix from comment 52, please do the following:

 - make sure you have the plymouth package installed (sudo apt-get install plymouth)
 - copy the plymouth-splash.conf to /etc/init (sudo cp plymouth-splash.conf /etc/init/plymouth-splash.conf)
 - reboot, to test.

Then in your report, please provide all the following information:

 - did you see an Ubuntu logo at boot?
 - if so did it disappear before the spinning X cursor appeared?
 - if you don't see an Ubuntu logo, do you see a blue and white bar at the bottom of your screen?
 - show the output of 'cat /proc/fb'
 - show the output of 'ps aw | grep X.*vt'
 - if you have nvidia video hardware, please mention if you're using nouveau or the binary driver.
 - does the problem with X freezing persist for you?
 - if you *don't* see the Ubuntu logo at boot, or if it disappeared before the X cursor appeared, and X does not freeze for you, is this reproducible across multiple reboots or do you still sometimes hit the freeze?

Since the fixed plymouth-splash.conf does seem to improve things for some (but not all) users, and I have a theory why this should be, I'm going to go ahead with uploading that change. I will still need to collect the above information in order to figure out the remaining problems.

[Matt Joiner (anacrolix)]

Note to others! The conf file goes in /etc/**init** not init.d, which I'm used to typing.

The provided conf file did not work, I did reinstalls of all plymouth, xorg and nvidia packages, and rebooted several times.

No ubuntu logo. I saw a blue and white bar, which after using the new conf didn't jumble as it has earlier, it was a single line. (Previously it would spread out over other lines with error messages about ureadahead). Also a fsck warning right after pressing the grub menu option has gone.

$ cat /proc/fb
0 VGA16 VGA

$ ps aw | grep X.*vt
 1731 tty7 Rs+ 0:06 /usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-4fxC0r/database -nolisten tcp vt7
 2282 pts/0 S+ 0:00 grep --color=auto X.*vt

I am using BINARY driver (nvidia-current, no idea what's going on with the packages, so I installed this one, and configured with nvidia-settings).

I always get the freeze, the provided .conf slightly improves the boot process, but it's no worse than it was.

[Launchpad Janitor (janitor)]

This bug was fixed in the package plymouth - 0.8.0~-9ubuntu1

---------------
plymouth (0.8.0~-9ubuntu1) lucid; urgency=low

  * Make plymouth-splash a service instead of a task, to make sure we only
    run it once per instance of plymouthd; and add an 'or starting gdm' to the
    start condition so that we're assured of having this command run before
    gdm starts - otherwise, this plays havoc with gdm's assumptions regarding
    initial VT selection. LP: #516412.
 -- Steve Langasek <email address hidden> Wed, 10 Feb 2010 16:08:56 -0800

[Matt Joiner (anacrolix)]

Steve does this change do more than adjust the plymouth-splash.conf?

For others, I found that pressing Alt+SysRq+K as soon as GDM first loads fixes the problem temporarily.
Running 'sudo apt-get remove plymouth' has fixed it permanently.

[ROB3RT (rob3rt)]

Hey, Good to know a fix has been released. Problem is, I still get the bug. I have Plymouth 0.8.0~9, according to synaptic, but I still get an fsck at boot, and pressing ENTER still causes the screen to freeze. Any suggestions?

[Matt Joiner (anacrolix)]

Boot in recovery mode. Run 'sudo apt-get remove plymouth'. Reboot.

[ROB3RT (rob3rt)]

Will that affect the system stability at all, will I need to do anything after that?

[Matt Joiner (anacrolix)]

No that's all. You'll get a few warnings during boot but it's fine.

[ROB3RT (rob3rt)]

Okay, I'll try it... Will I be able to replace it if needed?

[ROB3RT (rob3rt)]

Okay, I have it working. I uninstalled Plymouth, rebooted and everything went fine. So, I then reinstalled Plymouth, rebooted and I didn't get the problem. I rebooted again, and I still don't have the problem. Only thing is, the splash screen doesn't show up, but thats alright, I'm too cool for a splash screen :P

[Steve Langasek (vorlon)]

yankeeboy254,

0.8.0~9 is the previous, known-broken version of plymouth. The fixed upstart job is in version 0.8.0~9ubuntu1 only.

Since you mention that you're using the nvidia binary drivers, the lack of splash screen is expected. Unfortunately, the nvidia drivers don't export a framebuffer interface that the current plymouth can use. This may be fixed in a future update to plymouth.

[Steve Langasek (vorlon)]

Matt Joiner,

No, this update only changes the plymouth-splash.conf. So if that didn't fix it for you, unfortunately neither will the package upgrade.

In the output of the 'ps' command, is this the X server that was originally started at boot time, or is this a respawned X server *after* you experienced the freeze and used Alt+SysRq+K to restart it?

[Claus Pedersen (pedersen-claus)]

Hi,

I stilt have the the problem on every boot. System fully updated. plymouth - 0.8.0~-9ubuntu1
Using the binary nvidia driver.
No logo during boot, but white and blue line.
Output after using Alt+SysRq+K to restart:

cat /proc/fb
0 VGA16 VGA

ps aw | grep X.*vt
 1969 tty7 Ss+ 0:09 /usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-hgv9qn/database -nolisten tcp vt7
 2368 pts/0 S+ 0:00 grep --color=auto X.*vt

[Michal Matyska (michal-matyska)]

I'm using vesafb (having 80x25 VT on 24" screen is quite ugly) and nvidia binary drivers.
If I don't get blue/white lines during startup, then Enter is working fine.
If I see blue/white lines (but they are flickering, looks like something else is trying to clear the screen), then there is Enter key problem. Tested few times, hopefully this is the correct pattern. In this situation I see:

before SysRq+K: /usr/bin/X :0 -nr -verbose -auth /var/run/gdm/auth-for-gdm/uXADGb/database -noliste tcp vt7
after SysRq+K: /usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm/uXADGb/database -noliste tcp vt7

/proc/fb: 0 EFI VGA

I tried to replace vesafb with vga16fb (which I assume is the default one used) and removed gfxpayload from grub boot entry. I saw nice white/blue line growing at the bottom edge of screen, but it took approx. one minute to fill the whole line with white color and nothing happened. After pressing SysRq+K I got rescue shell, so I put vesafb back.

[Steve Langasek (vorlon)]

I need to see the ps aw output before restarting with Alt+SysRq+K. Please use Ctrl+Alt+F2 to switch to a console after boot and run the command there.

[Steve Langasek (vorlon)]

Michal,

> /proc/fb: 0 EFI VGA

Does this value change when you boot without gfxpayload?

What value were you using for gfxpayload?

(You actually are *not* using the vesa framebuffer; according to this, you're using the EFI framebuffer, which could cause problems of its own.)

[Claus Pedersen (pedersen-claus)]

I can't go to console. I just get a blank screen with two small grey cursor-like boxes.
Only after pressing enter and then alt+sys+k can I switch to console.

[Steve Langasek (vorlon)]

Claus,

Please open a separate bug report regarding the broken console at boot.

[Michal Matyska (michal-matyska)]

Using SSH to get to the system affected by Enter freeze:

michal@opus:~$ cat /proc/fb
0 EFI VGA

Oh yes, its not vesa ;-)... from dmesg:
[ 0.871514] Linux agpgart interface v0.103
[ 0.871550] efifb: probing for efifb
[ 0.871632] efifb: framebuffer at 0xf9000000, mapped to 0xffffc90011100000, using 2252k, total 2250k
[ 0.871634] efifb: mode is 1920x1200x8, linelength=1920, pages=1
[ 0.871636] efifb: scrolling: redraw
[ 0.871637] efifb: Truecolor: size=0:8:8:8, shift=0:0:0:0
[ 0.871661] fb0: EFI VGA frame buffer device

michal@opus:~$ status plymouth
plymouth stop/waiting
michal@opus:~$ status plymouth-splash
plymouth-splash stop/waiting
michal@opus:~$ ps aw
  PID TTY STAT TIME COMMAND
 1282 tty7 Ss+ 0:01 /usr/bin/X :0 -nr -verbose -auth /var/run/gdm/auth-for-gdm-KuxdtT/database -nolisten tcp vt7
 1343 tty4 Ss+ 0:00 /sbin/getty -8 38400 tty4
 1346 tty5 Ss+ 0:00 /sbin/getty -8 38400 tty5
 1353 tty2 Ss+ 0:00 /sbin/getty -8 38400 tty2
 1356 tty3 Ss+ 0:00 /sbin/getty -8 38400 tty3
 1360 tty6 Ss+ 0:00 /sbin/getty -8 38400 tty6
 1592 tty1 Ss+ 0:00 /sbin/getty -8 38400 tty1
 2098 pts/0 Ss 0:00 -bash
 2129 pts/0 R+ 0:00 ps aw

When I press Enter then it looks like something is written to console as there are some pixels in top left corner changed and every key press modifies more pixels.

I have tried to boot w/o gfxpayload, but in such case I don't see the white/blue line during boot and Enter works immediately (tested 3 times).

[Michal Matyska (michal-matyska)]

BTW the X process is consuming 100%CPU...

[Elfy (elfy)]

I get

fsck util line then

white/blue panel at bottom

then nothing else until the desktop, assume that as I am using nvidia driver I will not see splash screen.

cat /proc/fb
0 VGA16 VGA

ps aw | grep X.*vt
 1187 tty7 Ss+ 0:11 /usr/bin/X :0 -nr -verbose -auth /var/run/gdm/auth-for-gdm-OrbGsH/database -nolisten tcp vt7
 2008 pts/0 S+ 0:00 grep X.*vt

Have rebooted a few times and still have enter key working ok.

[Matt Joiner (anacrolix)]

@Steve, the command was executed _after_ killing the server. I can't switch to another VT as described in #77.

[Noel J. Bergman (noeljb)]

@Steve:

  $ dpkg -l | grep plymouth
  ii libplymouth2 0.8.0~-9ubuntu1
  ii plymouth 0.8.0~-9ubuntu1

> please provide all the following information:
> - did you see an Ubuntu logo at boot?
  No. I see a C in the middle of the screen, and the blue/white moving bars across the bottom.

> - if you don't see an Ubuntu logo, do you see a blue and white bar at the bottom of your screen?
  yes

> - show the output of 'cat /proc/fb'
  $ cat /proc/fb
  0 VGA16 VGA

> - show the output of 'ps aw | grep X.*vt'
  $ ps aw | grep X.*vt
   1364 tty7 Ss+ 0:12 /usr/bin/X :1 -br -verbose -auth /var/run/gdm/auth-for-gdm-d8TatG/database -nolisten tcp vt7

> - if you have nvidia video hardware, please mention if you're using nouveau or the binary driver.
  The real driver (nvidia-current, currently 190.53-0ubuntu14)

> - does the problem with X freezing persist for you?
  NOT ANYMORE, THANK YOU! :-)

> - if you *don't* see the Ubuntu logo at boot, or if it disappeared before the X cursor appeared,
> and X does not freeze for you, is this reproducible across multiple reboots or do you still
> sometimes hit the freeze?
  I'll let you know! The freeze had been consistent earlier, which is why I'd restored an older version of Plymouth, and blocked it from updating.

[Michal Matyska (michal-matyska)]

Interesting progress... I did another update of the system (there wasn't plymouth in the list) but now I can see the non-flickering white/blue line at the bottom (well, it is actually black/blue because of different colour mapping?) and can press Enter without freeze.

Among others, there was new kernel 2.6.32-13.18 installed and gdm updated from 2.29.6-0ubuntu2 to 2.29.6-0ubuntu3

[Noel J. Bergman (noeljb)]

@Steve,

> - if you *don't* see the Ubuntu logo at boot, or if it disappeared before the X cursor appeared,
> and X does not freeze for you, is this reproducible across multiple reboots or do you still
> sometimes hit the freeze?

Oh, well. I still get the crash. Not always, but more often than not. AND it appears that this is also the state in which hitting @ will force a logout, and after gdm comes back, <cr> is permitted again.

I'll keep an eye out for another fix attempt. Meanwhile, I'm reverting to the older Plymouth.

[Anthony Hook (anthonyhook)]

$ dpkg -l | grep plymouth
ii libplymouth2 0.8.0~-9ubuntu1 graphical boot animation and logger - shared
ii plymouth 0.8.0~-9ubuntu1 graphical boot animation and logger - main p

I did not see the boot logo, rather the blue and white bars.

$ uname -a
Linux hookbox 2.6.32-13-generic #18-Ubuntu SMP Wed Feb 10 21:32:38 UTC 2010 x86_64 GNU/Linux

$ cat /proc/fb
0 VGA16 VGA

$ ps aw | grep X.*vt
 3378 tty7 Ss+ 1:19 /usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-Nu0jaJ/database -nolisten tcp vt7
24698 pts/2 S+ 0:00 grep X.*vt

nvidia-current, currently 190.53-0ubuntu14

Yes, I'm having the problem persist, I haven't replaced the .conf as mentioned previously as people said it hadn't worked for them.

Yes, the freeze is reproducible after multiple boots.

[rossjenkins (rossawjenkins-gmail)]

@Steve,

Running Lucid Alpha 2 x86-64 with all the updates (as of Feb 12, 2010 00:30 EST) I get the splash screen OK but also get the freeze if I hit the Enter key after entering my password. I'm not sure if anyone else here has this config, but I am running Lucid as a Guest OS under Virtual Box on a Karmic 9.10 host OS. Thus, all my video hardware is "virtual" for Lucid, no "bare metal" at all and I get the same freeze up symptoms. The same cure as for a bare metal system works - sudo apt-get remove plymouth - and reboot the virtual machine and all is well except for a few brief error messages at boot start complaining about not being able to connect to plymouth. Also, the boot time is amazing fast with plymouth removed (about 11-12 seconds from when I start the VBox Lucid guest OS to the log in screen).

I don't know how the Virtual Box video driver compares to the Nvidia or ATI proprietary ones, but since virtual video hardware chokes just like real hardware then this plymouth bug seems pretty fundamental in character.

Any commands I can run to get more info for you? Its easy with a virtual machine to play with :-)

[rockwallaby (paul-alting)]

I have been following this thread since having the problem describe.
System is new Dell D420 with Lucid A2, with updates checked and installed for many times each day.
System is set for auto login.

As Steve Langasek wrote at post #61, where he describes the various ways in which the problem may be seen,
I have noticed my system pretty well doing those things, that is;

Approximately 60% of the time boot up will be such that I see the ubuntu logo only for a short period and then the X cursor, with no spinning wheel. When the boot up goes this way I know I have the freeze state just waiting for me to hit the enter key at any opportunity. Also I notice that gdm gets a frame buffer error and blacks the screen, needing me to go to ctrl F1 and then back to ctrl F7 to have it up again. The system is still working underneath ok.

When the system boots such that I see the ubuntu logo stay, I then get to see the spinning wheel in the middle of the logo and then the cursor, and I know all is well.

I have rebooted many many times to see how consistent this would be, and well like I say, about 40% clean boots against 60% bad boots.

Yes, plymouth, when installed slows down the boot process considerably. Without, it does what others have noticed, in that it generates errors because it is not installed to be run.
But without plymouth at this stage the system seems to boot and be stable.

In any case I don't get to see any blue and white bars at any time

the plymouth-splash.conf was already part of the newer updates I installed and no improvement.
It looks to be some sort of race situation for it to be so unpredictable I think.

So, all this with the latest updates as of 12-02-2009 20:00 Australian time (10:00 GMT I think)
Video is Intel Mobile 945GM/ Express rev 03.
kernel 2.6.32-13
GNOME 2.29.90

$ cat /proc/fb
0 inteldrmfb
1 VGA16 VGA

$ ps aw | grep X.*vt
1155 tty7 Ss+ 1:11 /usr/bin/X :0 -br - verbose - auth /var/run/gdm/auth-for-gdm-noogdp/database -nolisten tcp vt7
1885 pts/0 S+ 0:00 grep --color=auto X.*vt

Steve, I know not much of Linux but I appreciated your effort and I think you explain well the problem and are heading on the right track. Also grateful to others on this bug for their input.

rockwallaby ~ sipping red wine in hope of inspiration later on ;~)

[Michal Matyska (michal-matyska)]

Oops... my last comment is not true anymore... another boot this morning and it is again flickering and freezes on Enter. The boot process took much more time than yesterday...

[Claus Pedersen (pedersen-claus)]

With the new 0.8.0~-10 it worked fine on the first boot.
On the next five boots, still the freeze.

[rockwallaby (paul-alting)]

Yes, I notice that on re-installing plymouth it seems to boot good on the first boot only, then becomes unpredictable thereafter.

[Noel J. Bergman (noeljb)]

That matches what I saw ... fine on first boot, issues after.

[emarkay (mrk)]

The last 4 posts are after "Fix Released", are still affected with the same issue.
Thus is it safe to conclude that the released fix does not completely solve this problem?
FWIW, I have Plymouth removed for now.

[Steve Langasek (vorlon)]

If you are still experiencing problems after the update, please open a new bug report. If you already filed a separate bug report that was marked as a duplicate of this one, please un-mark it as a duplicate.

The upload did fix *one* of the problems with plymouth, but there are still other problems that need to be debugged. Since the original submitter of this bug report hasn't chimed in yet, I'm assuming that that particular bug is fixed, so we should use a different bug report as the master bug for the remaining problems.

[Eric Appleman (erappleman)]

This is not fixed. X will crash randomly upon Enter keypresses as long as Plymouth is installed.

[Zaphod (vilppu777)]

I am the original bug submitter an the only way I was able to fix the issue was to remove Plymouth all together. However due to other issues I am currently running 9.10 now so the others with the same issue can help troubleshoot as they have been.

It's not too hard to tell if it is the same bug. If you press <enter> and the system pretty much freezes except for ssh then it is the same issue.

I'm not real sure why we really need Plymouth anyway seams that every one has less problems and faster boot ups without it.

[Nicolás Lichtmaier (niqueco)]

The problem is not fixed until it stops happening. It's so obvious I'm amazed somebody could disagree. I installed the new version and my pc crashed exactly as before. If this is "fixed" (ha!) then please somebody should post here the new bugnumber for this bug.

[Steve Langasek (vorlon)]

On Fri, Feb 12, 2010 at 04:23:30PM -0000, Zaphod wrote:
> It's not too hard to tell if it is the same bug. If you press <enter>
> and the system pretty much freezes except for ssh then it is the same
> issue.

No, that's not the standard for saying this is the same bug. That's the
same *symptom*, which can be caused by a number of different underlying
bugs.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>

[Simon Baconnais (smon-deactivatedaccount)]

Are you kidding ? This is **EXACTLY** the same bug !!!

[Niels Egberts (nielsegberts)]

On Fri, Feb 12, 2010 at 5:45 PM, Steve Langasek
<email address hidden> wrote:
> No, that's not the standard for saying this is the same bug.  That's the
> same *symptom*, which can be caused by a number of different underlying
> bugs.

The chance that 1 person is being affected by both bugs at the same
time with exact the same symptom seems not very high to me. And if we
create a new bugreport, the information it holds is going to be the
same, so I don't see a reason either to close this bug.

[vmc (vmclark)]

I think Plymouth is causing a myriad problems.
(1) is this key freeze issue
(2) Computer freezes right after fsck flashes across screen

I have (2), which I believe its still this bug :
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/510524

All relating to Plymouth. Or at least some configuration file is being updated relating to Plymouth.
Plymouth works for 3 re-boots and then the deep freeze?!

[shankao (shankao)]

Well, I think that in this case we should maintain the same bug in launchpad as the perceived problem is well defined, still happens and *we would want to maintain all the info we've about it in the same place*.

@Steve: I think the two bugs can exist but both must be fixed in order for this to be marked as fix released. Otherwise, bug #1 should have being marked as fixed long ago, just after solving one part of the "symptom" described there.

[Sense Egbert Hofstede (sense)]

I can confirm that the new upload of Plymouth fixed this bug.

Guys, please listen to Steve Langasek. He fixes these bugs, he knows what he's doing. He is correct with saying that an equal symptom doesn't mean the cause is equal. It could be that some people suffer from both different causes, that is perfectly possible.

[shankao (shankao)]

Ok, then it could be a problem of bug management in these cases.

Should we then open a new bug with the same subject and contents? As we can't distinguish between the two bugs, the two entries in launchpad would have the same information.
Maybe we must work in the correct identification of "the other bug" but the start of the bug report will be the same "Pressing <Enter> causes X to freeze"

[Sense Egbert Hofstede (sense)]

shankao: Yes, that does sound like the best option, especially considering the enormous mess this bug report has become.

[Sense Egbert Hofstede (sense)]

Please don't change the status without providing a reason and please don't subscribe yourself if you're not the one working on the bug.

[00raq00 (00raq00)]

Problem is still in plymouth, remove only works....

[Matt Joiner (anacrolix)]

Currently running libplymouth and plymouth 0.8.0~-10 and still crashes at X.

[Simon Baconnais (smon-deactivatedaccount)]

Problem remains

[Simon Baconnais (smon-deactivatedaccount)]

By the way, the original bug submitter say that the bug isn't fixed. So Steve Langasek surely fixed a bug, but not the good one ...

[Calçada, Luís Pedro (luispedrocalcada)]

First of all, sorry for my bad english.

I discovered various things.

1 - Press Enter key don't cause more crashes after our session log out automatically or we manualy logout the first login since boot and re-log in same account.

2 - There it a random time to session logout without do anything. After that no problem with pressing Enter key.

[Theo Nolte (theo-nolte)]

For me the behavior has changed now since Steves fix. Previously pressing ENTER caused X to freeze, now gdm is frozen from the start, I can't even move the mouse or enter a password. As previous, Alt-Print-K restarts X and fixes it.

1. I use lucid 64 bit with Nvidia GeForce 9300M G with binary drivers (nvidia-current)

2. I see no logo

3. I see blue and white bars at bottom of screen

4. The bars disappear when the spinning cursor appears

5. $ cat /proc/fb
    0 VGA16 VGA

6. $ ps aw | grep X.*vt
 1732 tty7 Rs+ 0:16 /usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-4h7UJ8/database -nolisten tcp vt7

7.
dpkg -l plymouth libplymouth2
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii libplymouth2 0.8.0~-10 graphical boot animation and logger - shared
ii plymouth 0.8.0~-10 graphical boot animation and logger - main p

Hope that helps.

[ROB3RT (rob3rt)]

Hey, what worked for me was:
Reboot into safe mode.
Sudo apt-get remove Plymouth
Reboot
Reinstall Plymouth

What it did:
No more Fscks at boot.
No more crashes when pressing ENTER. It seems like this bug still affects some people, which means that there should probably be a seperate bug report, to see why this is still going on.

[00raq00 (00raq00)]

git clone git://anongit.freedesktop.org/plymouth

Next configure and compile it:

> cd plymouth
> ./autogen.sh --prefix=/usr/ --with-system-root-install
> make
> make install

it resolve problem :) but i'm waiting for .get from repository

[Ari Torhamo (ari-torhamo)]

I was affected by this bug. Pressing Enter at any time forward from the login screen froze the system. No Ubuntu logo was visible during the boot, but there was a blue and white progress bar at the bottom of the screen.

Removing plymouth fixed the bug (removed it in Synaptic, not in safe mode)
- reinstalling plymouth brought the problem back
- removed plymouth again, and the bug is now gone
(removing plymouth made the system freeze at shut down - had to reset)

System:
Ubuntu Lucid daily live of 13.2.2009
AMD 64 bit
Nvidia Geforce 8800 GT with binary driver

[Simon Baconnais (smon-deactivatedaccount)]

I still affected by this bug.

[Anthony Hook (anthonyhook)]

As a normal user, not a bug-patcher, etc, this is what I see:

When I press 'Enter,' X Freezes. It still happens with the latest Plymouth. As far as I know, this bug isn't fixed.

Occasionally when I try to switch to a TTY to log in before I log into GDM (which then allows me to use 'Enter' properly), I get the attached screenshot which leaves me having to hard-power down my laptop.

[Harry (harry33)]

I can confirm the bug is not fixed yet.
Still affected by this in a fully updated lucid_amd64, NVidia GLX285, driver: nvidia-current.

[UGN (eugene-korneev)]

i have same issue on my asus eee pc 701 and last lucid,
after boot and autologon my system ican wait some time and X crush, and\or press "2" (not "enter") X restarts and i can logon into systen (not auto) and continue wotrk...

[Sense Egbert Hofstede (sense)]

Guys, please read the comments on this bug. This has become such a mess that it is undoable to continue to use this bug report to track this symptom. What's more, the developer indicated several times that the cause for this particular bug has already been found and eliminated.

Please do not change the status of this bug again.

[shankao (shankao)]

I have just added the bug report #522692 for those still affected by similar symptoms. Let's try to solve it there.

[Benny Källström (benny-k)]

I agree, this bug is a mess.

[Casey J Peter (caseyjp1)]

As of this morning's updates, I will add that on my amd64 x2 rig with 190.xx nvidia drivers, this is still an issue.
alt+printscrn+k restarts gdm and no further issues until the next reboot. I've added "affects me" to the 522692 bug report as well. this isn't resolved, at least for the prop. nvidia folks.

[tsm124 (tsm1248)]

Release the update in the update manager...

[[e-mail] (jan-san)]

Installed all the updates, still affected

[Nicolò Chieffo (yelo3)]

This issue seems really similar to one that appeared las year, and was
caused by starting Xorg and a VT on the same console.
Can a developer check?

[Claudio Moretti (flyingstar16)]

Comment #125

[Andrew Gee (andrewgee)]

Nicolò,

I think that's the problem I'm having, as I get a blank terminal with a flashing cursor, over the login window, until I switch to another tty and back.

[Paolo Sammicheli (xdatap1)]

Hello,

During Xorg Team Alpha testing, 22 Feb Image changed behaviour. Now pressing enter, X did Crash and it fall back to GDM login. It's a step ahead indeed :)

http://xorg.qa.ubuntu.com/qatracker/result/3603/419

[Marco Simonelli (sumydi)]

Il 22/02/2010 21:41, Paolo Sammicheli ha scritto:
> Hello,
>
> During Xorg Team Alpha testing, 22 Feb Image changed behaviour. Now
> pressing enter, X did Crash and it fall back to GDM login. It's a step
> ahead indeed :)
>
> http://xorg.qa.ubuntu.com/qatracker/result/3603/419
>
>
I had the same behaviour with plymouth 0.8.0~-10ubuntu1, now I removed
it. I use nvidia-current blob but no splash, only text.

--
Marco Simonelli

[Claudio Moretti (flyingstar16)]

Please open a new bug.
This was fixed and no (quite) one looks here :)

On Tue, Feb 23, 2010 at 07:54, Marco Simonelli <email address hidden> wrote:

> Il 22/02/2010 21:41, Paolo Sammicheli ha scritto:
> > Hello,
> >
> > During Xorg Team Alpha testing, 22 Feb Image changed behaviour. Now
> > pressing enter, X did Crash and it fall back to GDM login. It's a step
> > ahead indeed :)
> >
> > http://xorg.qa.ubuntu.com/qatracker/result/3603/419
> >
> >
> I had the same behaviour with plymouth 0.8.0~-10ubuntu1, now I removed
> it. I use nvidia-current blob but no splash, only text.
>
> --
> Marco Simonelli
>
> --
> Pressing <Enter> causes X to freeze
> https://bugs.launchpad.net/bugs/516412
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “plymouth” package in Ubuntu: Fix Released
>
> Bug description:
> Binary package hint: plymouth
>
> I am running ubuntu 10.04 Alpha2 and after last nights updates pressing the
> enter key causes the whole system to freeze and I have to hard reboot.
>
> Only removing Plymouth would allow me to work normally.
>
> The system still respond to ssh.
>
> WORKAROUND (thanks to Simon Baconnais): kill X by pressing Ctrl+Alt+Print+K
> fixes the problem until the next reboot.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/516412/+subscribe
>

[shankao (shankao)]

It's open as bug #522692 (see comment #121)

[MJ (mjjaa)]

Hey,

i have a similar problem, when I press enter, Gnome crashes and goes back to the login screen, when I login now and press enter again this error does not occur. I have auto login switched on and I am using Alpha 3

[Sense Egbert Hofstede (sense)]

MJ: I think you're having bug #522692.

[burivoy (burivoy)]

Bull sheet no fix release has been released yet.

I have installed Lucid on HP Pavilion zv5000 with ATI Mobility Radeon(TM) 9000 IGP. Ufter update of this bloody plymouth I never started X. After pressing Enter I hear the login sound and cursor appers but that is all. Nothing helped - neither uninstalling plymouth nor reinstalling xorg. Developers should test such a things on different graphic cards prior to send it to repo.

[Sense Egbert Hofstede (sense)]

burivoy: Please read the previous comments. As the developer indicated that this specific bug was fixed. There might be other bugs with the same symptoms, but they are different bugs. Maybe you're using different hardware than the original reporter. Furthermore, the fact that removing Plymouth doesn't solve the issue for you is another indication that you're suffering from a different bug, most likely in GDM.

About the testing: if you could provide the developers with the hardware and the time for testing new packages that extensively, then we'd be happy to do more extensive testing. Otherwise, please consider reinforcing the testing team, which can use some help as well.

Please also mind your language.

[Claudio Moretti (flyingstar16)]

>
> Developers should test such a things on different
> graphic cards prior to send it to repo
>
Also, what did you expect from a _development_ release?

On Tue, Mar 2, 2010 at 17:29, Sense Hofstede <email address hidden> wrote:

> burivoy: Please read the previous comments. As the developer indicated
> that this specific bug was fixed. There might be other bugs with the
> same symptoms, but they are different bugs. Maybe you're using different
> hardware than the original reporter. Furthermore, the fact that removing
> Plymouth doesn't solve the issue for you is another indication that
> you're suffering from a different bug, most likely in GDM.
>
> About the testing: if you could provide the developers with the hardware
> and the time for testing new packages that extensively, then we'd be
> happy to do more extensive testing. Otherwise, please consider
> reinforcing the testing team, which can use some help as well.
>
> Please also mind your language.
>
> --
> Pressing <Enter> causes X to freeze
> https://bugs.launchpad.net/bugs/516412
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “plymouth” package in Ubuntu: Fix Released
>
> Bug description:
> Binary package hint: plymouth
>
> I am running ubuntu 10.04 Alpha2 and after last nights updates pressing the
> enter key causes the whole system to freeze and I have to hard reboot.
>
> Only removing Plymouth would allow me to work normally.
>
> The system still respond to ssh.
>
> WORKAROUND (thanks to Simon Baconnais): kill X by pressing Ctrl+Alt+Print+K
> fixes the problem until the next reboot.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/516412/+subscribe
>

[burivoy (burivoy)]

Does not fucking work on HP Pavioin zv5000 and ATI Mobility Radeon 9000 IGP.

[Anthony Hook (anthonyhook)]

That language is unacceptable in the Ubuntu Community, as you were already previously informed. Please review the Code of Conduct http://launchpad.net/codeofconduct/1.1 and http://www.ubuntu.com/community/conduct before you decide to post again.

Most of us are volunteers and this type of behavior is unacceptable.

[Matthieu Baerts (matttbe)]

I agree with Anthony Hook !

 > "Most of us are volunteers and this type of behavior is unacceptable."

If you don't like Plymouth, simply uninstall it... Or if you didn't like Ubuntu and its Code of Conduct, there are other solutions !

[Claudio Moretti (flyingstar16)]

Even if I agree with you on the language matter, I must point out a thing:

root@Jarvis:~# apt-get remove plymouth
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze
Lettura informazioni sullo stato... Fatto
I seguenti pacchetti sono stati installati automaticamente e non sono più
richiesti:
  linux-backports-modules-nouveau-2.6.32-14-generic db4.6-util libbttracker0
  libbtutil0 libmcrypt4 libapache2-mod-bt libdb4.6
Usare "apt-get autoremove" per rimuoverli.
I seguenti pacchetti saranno RIMOSSI:
  cryptsetup plymouth plymouth-x11
0 aggiornati, 0 installati, 3 da rimuovere e 0 non aggiornati.
Dopo quest'operazione, verranno liberati 2269kB di spazio su disco.
Continuare [S/n]? n
Interrotto.

I need cryptsetup and I cannot remove it without being unable to use my
system

On Wed, Mar 3, 2010 at 00:51, Matthieu Baerts <email address hidden> wrote:

> I agree with Anthony Hook !
>
> > "Most of us are volunteers and this type of behavior is
> unacceptable."
>
> If you don't like Plymouth, simply uninstall it... Or if you didn't like
> Ubuntu and its Code of Conduct, there are other solutions !
>
> --
> Pressing <Enter> causes X to freeze
> https://bugs.launchpad.net/bugs/516412
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “plymouth” package in Ubuntu: Fix Released
>
> Bug description:
> Binary package hint: plymouth
>
> I am running ubuntu 10.04 Alpha2 and after last nights updates pressing the
> enter key causes the whole system to freeze and I have to hard reboot.
>
> Only removing Plymouth would allow me to work normally.
>
> The system still respond to ssh.
>
> WORKAROUND (thanks to Simon Baconnais): kill X by pressing Ctrl+Alt+Print+K
> fixes the problem until the next reboot.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/516412/+subscribe
>

[burivoy (burivoy)]

I thought I would never see my Desktop again.

[RichardNeill (ubuntu-richardneill)]

I'm seeing this on Oneiric (64-bit) with Xubuntu. I have a very repeatable test case:

1. Reboot.
2. Wait for autologin to occur.
3. Press enter on desktop.
4. X will crash, and I get dumped back to password prompt to login.
5. Then it works ok till I reboot again.

I tried the recommended suggestion of removing plymouth, but it isn't possible to do that in oneiric without removing the entire base-system.

Incidentally, I'm using a Lenovo S205 laptop, which has a radeon GPU but where I have NOT installed the binary driver, and the bootloader is grub-legacy (grub-2 won't work with EFI).

[Steve Langasek (vorlon)]

On Sat, Dec 17, 2011 at 05:28:03AM -0000, RichardNeill wrote:
> 1. Reboot.
> 2. Wait for autologin to occur.
> 3. Press enter on desktop.
> 4. X will crash, and I get dumped back to password prompt to login.
> 5. Then it works ok till I reboot again.

Do you have any custom init scripts or upstart jobs installed on this
system? If so, chances are that one of these is breaking the console
underneath X.

> I tried the recommended suggestion of removing plymouth, but it isn't
> possible to do that in oneiric without removing the entire base-system.

This is NOT recommended. This has only been recommended by people who have
no involvement with Ubuntu development. You are correct, plymouth is part
of the base system. This is not a bug and not an accident.

> Incidentally, I'm using a Lenovo S205 laptop, which has a radeon GPU but
> where I have NOT installed the binary driver, and the bootloader is
> grub-legacy (grub-2 won't work with EFI).

I expect this is entirely unrelated, but note that there is a grub-efi
package for grub2 EFI support.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>