Version 1:0.34.5-1ubuntu1 breaks GDM
Bug #1184132 reported by
Michael Kuhn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Gnome Virtual Terminal Emulator |
Fix Released
|
High
|
|||
vte3 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
After backporting version 1:0.34.5-1ubuntu1 to raring, I could no longer log in, because GDM did not start anymore. This is apparently due to the new vte.sh script that returns an error code != 0 if it bails out early.
The attached patch fixes it on my systems. I can also forward it upstream if you want.
Changed in vte: | |
importance: | Unknown → High |
status: | Unknown → New |
Changed in vte: | |
status: | New → Fix Released |
To post a comment you must log in.
On Sat, May 25, 2013 at 12:01:14PM -0000, Michael Kuhn wrote:
> Public bug reported:
>
> After backporting version 1:0.34.5-1ubuntu1 to raring, I could no longer
> log in, because GDM did not start anymore. This is apparently due to the
> new vte.sh script that returns an error code != 0 if it bails out early.
>
> The attached patch fixes it on my systems. I can also forward it
> upstream if you want.
Seems sensible - yes, please forward upstream. Link the bug here so that
we can track it and I'll cherry pick into Ubuntu if necessary.
--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]