hi, sorry if i post a question in a very old tread but i couldn't find an
appropriate one for my problem that is the one described here but i have
ubuntu 12.04 precise-64 bit
i tried to open xorg.0.log.old but i need a software to open backup
files... what i should use? (sorry i'm neubbie)
if
Hello Niccolo,
Launchpad is not a forum, but a platform to track and solve bugs. To
solve your problem, please use one of the numerous Ubuntu forums you can
find :)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
@Niccolo
Welcome.
I don't think this old bug report is a way to get this problem solved as
it is already closed. Since you have already looked for a current bug
report and can't find one I'd suggest you file a new one yourself.
Please don't be shy. I'd suggest you use the approach at
Hi Mathieu, thanks for your answer and sorry if i misunderstood the
format...
Anyway, i report the bug is still present in the newest LTS version of
Ubuntu (precise 12.04) and i cannot find a solution to fix it neither in
this platform or in any ubuntu forum (i came here by suggestion from
@John S.Gruber: i read your post just now.. thank you for your
suggestions, i will write a new post describing my problem and
eventually take a look on askubuntu.com. I'll try to be not shine :)))
PS Sorry again if my approach is forum-style
--
You received this bug notification because you are
I have this problem with a Toshiba Portegé Z930 and Ubuntu 12.04. But I
get instead a black screen with a mouse cursor and a console cursor
blinking. After pressing 2 or ENTER, lightdm starts again.
I leave a tail -f /var/log/Xorg.0.log on the tty1 before pressing 2 or
ENTER, and then I press it,
Additional attachment
** Attachment added: X log after pressing ENTER - Toshiba Portegé Z930
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/532047/+attachment/3453843/+files/2012-12-05%2018.39.26.jpg
--
You received this bug notification because you are a member of Ubuntu-X,
which
I had this problem with ubuntu 11.10 when I pressing 2 or Enter at
login screen or in my account the first time I enter. A temporary
solution that work for me is:
Edit the file /etc/init/plymount-splash.conf and remove the line or
stopped udev-fallback-graphics.
So it should be:
start on
I have the same problem in 11.10.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/532047
Title:
Plymouth text-mode splash causes X to crash on first run due to shared
tty7
To manage
This bug is definitly not fixed in 11.10.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/532047
Title:
Plymouth text-mode splash causes X to crash on first run due to shared
tty7
To
I've opened bug 887445 and found out that it is related to this bug. The same
problem remains in 11.10.
It crashes if I press 2 or ENTER.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Hi,
I'm on Natty 64 bit and I'm experiencing the same symptoms (and also the
same backtrace) of this bug:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/529230
which is marked as duplicate of the one on which I'm commenting on.
I can confirm the bug happening on pressing enter or 2,
On Tue, May 24, 2011 at 08:59:31PM -, Steven wrote:
I'm on Natty 64 bit and I'm experiencing the same symptoms (and also the
same backtrace) of this bug:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/529230
which is marked as duplicate of the one on which I'm commenting on.
after I upgraded the system to maverick, when I start any gui java application
from eclipse X crashes
Backtrace:
[ 10634.359] 0: /usr/bin/X (xorg_backtrace+0x28) [0x4a0fa8]
[ 10634.359] 1: /usr/bin/X (0x40+0x60fcd) [0x460fcd]
[ 10634.359] 2: /lib/libpthread.so.0 (0x7fa4bb939000+0xfb40)
Thanks for your comment, jedioetzi. I wonder if you would find it
worthwhile to look further for another report, or to open a new one,
perhaps with the command:
ubuntu-bug xorg
The 532047 bug has been marked fixed (and it was), and therefore may not
show up on many triagers' bug searches. (In
Mmm... sarcasmperhaps I should just reopen the bug so we can get a
response/sarcasm
You know, in my opinion this is a critical bug. There are _many_ people
right on this very bug and others who have been reporting crashes after
the supposed fix was released. I'm guessing that the fix just didn't
@Seth: Are you also watching bug #625239? This is where I've posted all
of my feedback, and there is active work going on there. It's difficult
for me to be certain of whether we're experiencing the very same bug or
not. I'm also on Lucid, nvidia-current, current updates and on a fast
machine, and
@Krug: so that sums up all the symptoms. Do you ever see the scrolllock light
come on / flash just before the crash is imminent?
It seems like no risk of crash exists for a while since boot, and then at a
certain point (perhaps due to some very slow upstart/init job completing or
giving up),
@Krug: PS. do you have a founded opinion on my workaround/fix in comment
#91 ? My systems seems a bit slower to the desktop while booting, but I
haven't had the problem manifest itself. I might start explicitely
logging the virtual terminals for any X sessions somehow so I can be
sure that I'm
@Seth: Oddly, I don't think my laptop has a scroll lock light, so I
can't confirm or deny that correlation. I honestly don't quite
understand your workaround in #91, sorry. And sorry if my comments got
verbose--I'll try to keep them succinct ;-) I'm a bit over my head, but
I'm doing my best to
@Seth: Please join us over at bug #625239. I'd love to see one of your
failing Xorg.0.logs and a plymouth-debug.log if you could manage it in
order to compare them to those contributed by Jamie and Dino. In Dino's
case we can see that gdm is trying to follow plymouth to plymouth's tty
(which
@Steve Langasek:
To me, your response seems a bit harsh, as it appears (to me) to imply that my
judgement must be bad, and I must be jumping to conclusions. I venture, you
might be the one jumping to conclusions - or at least using a definition of the
word 'fixed' that is incompatible with mine
FWIW: I've started running with my own naive modification of
/etc/init/gdm.conf, to see whether it changes symptoms. Here the diff (I
use etckeeper with git, so this is git diff output):
diff --git a/init/gdm.conf b/init/gdm.conf
index 5600d4c..d36acdc 100644
--- a/init/gdm.conf
+++
Still crashing my X server on lucid, nvidia-current and using all the latest
patches.
Any news?
** Changed in: plymouth (Ubuntu)
Status: Fix Released = In Progress
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You
Please do not reopen this bug. If you are seeing X crashes in lucid you
should open a new bug, not assume that your issue is the same as one
that has already been fixed.
** Changed in: plymouth (Ubuntu)
Status: In Progress = Fix Released
--
Plymouth text-mode splash causes X to crash on
Sorry if this is not the right bug to comment on, but I spent hours yesterday
just trying to figure out where I should be commenting. I just commented on bug
#529230 (comments 21 and 22) because that seems the best fit, but it's listed
as a duplicate of this bug. This bug's description does not
FYI: I've posted a comment on bug #625239, as suggested by John on bug
#529230.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Looks like the regression in Maverick has been filed as bug #625239
and has been marked as confirmed.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
As Scott said, we need to file a new bug about this issue. I tried the
workaround given in this bug description and it worked, which meansthat
the problem is affecting Plymouth once again.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
This is broken for me as well.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
Same problem, filed bug #625239 about problem in maverick, however I
think this one is the correct bug.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
Is this change the problem causer?
+ 121_only_switch_vt_when_active.diff:
Add a check to prevent the X server from changing the VT when killing
GDM from the console.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
Subscribed RAOF as it appears this is a regression from the last upload.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
This bug has been fixed for a long time. However, the latest update
breaks maverick once again. Please note that I have removed quiet
splash from the boot params as I personally hate the splash, so
Plymouth doesn't seem to be causing it. This has started happening only
today after update, with X
Still borked here, as of latest Lucid, long after final release.
WTF is going on
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is
Horrible bug, affects me too
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
I have installed Lucid Lynx final release (system if fully updated right
now) and this bug persists :-( Whenever I boot and press Enter or 2
X crashed and restart, It's annoying !
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
When I put my notebook in docking-station, with secondary monitor attached, I
still get the same behavior as before (have to press Alt-SysRq-K to get X
restart). The bug is fixed for me when booting WITHOUT secondary monitor
attached. So it seems that Plymouth doesn't work correctly with
I read here: plymouth (Ubuntu) Fix released. Milestone Ubuntu 10.04-beta1
There has no fix arrived here.
My X still sometimes appears on my 1st and sometimes on my 8th virtual console.
'~$ uname -a; Linux T42 2.6.32-17-generic #26-Ubuntu SMP Fri Mar 19 23:58:53
UTC 2010 i686 GNU/Linux'
--
I am seeing this after installing from today's alternate ISO build...
I looked at bug 538213 and tried the updated plymouth package but that
did not fix the issue at all...
I still get the X terminiation if I hit enter on the first login attempt
after boot.
--
Plymouth text-mode splash causes
** Tags added: iso-testing
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
On Wed, 2010-03-17 at 18:39 +, Jeff Lane wrote:
I am seeing this after installing from today's alternate ISO build...
Do you have cryptsetup installed?
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
Hy!
I'm having this issue with the NVIDIA 173 (not nvidia-current because of Bug
#534754) driver and an up2date lucid...
And yes I have cryptsetup installed (with pammount for my luks encrypted
home)...
How can I help?
--
Plymouth text-mode splash causes X to crash on first run due to shared
On Monday, March 15, 2010 at 13:02:30 (-), Scott James Remnant wrote:
On Mon, 2010-03-15 at 01:59 +, Marc A. Donges wrote:
This problem still exists for me with current versions of lucid:
Could you describe the problem you're seeing?
Yes, of course. But I have not yet encountered
Reproduced in daily (today) liveCD in virtualbox, bootup shows text-splash
(+errror messages, broken pipe, etc.).
Enter restarts gdm reproducibly after first login.
Bug should be reopened?
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
@arand
Please see bug 538213
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
On Tue, 2010-03-16 at 20:22 +, Marc A. Donges wrote:
On Monday, March 15, 2010 at 13:02:30 (-), Scott James Remnant wrote:
On Mon, 2010-03-15 at 01:59 +, Marc A. Donges wrote:
This problem still exists for me with current versions of lucid:
Could you describe the
Confirmation: I did a lucid update this morning (Mar 15th), and this
behaviour has been fixed for me.
Sean
On 15 March 2010 06:01, Steve Langasek steve.langa...@canonical.com
wrote:
The majority of users have confirmed that this bug is fixed, so marking
this again as fixed and unmarking bug
On Sun, 2010-03-14 at 16:22 +, Claudio Moretti wrote:
Still experiencing it:
Could you provide cat /proc/fb output for me, and confirm whether you
see an Ubuntu logo during boot, or the words Ubuntu 10.04 in text
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
Plymouth text-mode
On Mon, 2010-03-15 at 01:59 +, Marc A. Donges wrote:
This problem still exists for me with current versions of lucid:
Could you describe the problem you're seeing?
Does plymouth show a graphical logo or do you see Ubuntu 10.04 written
in text?
Scott
--
Scott James Remnant
Still experiencing it, too. I have the text boot splash, not the graphical logo
one.
My description from
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/529230/comments/9 still
stands.
I use quiet splash nomodeset in the grub linux line, because KMS doesn't work
with my graphics
On Mon, 2010-03-15 at 14:03 +, Henning Schröder wrote:
Still experiencing it, too. I have the text boot splash, not the graphical
logo one.
Thanks. This is bug #538213 - which is specifically about the text boot
splash
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
Plymouth
Fixed for me too
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
Still experiencing it:
r...@jarvis:~# apt-cache policy plymouth
plymouth:
Installato: 0.8.0~-14
Candidato: 0.8.0~-14
Tabella versione:
*** 0.8.0~-14 0
500 http://archive.ubuntu.com lucid/main Packages
100 /var/lib/dpkg/status
r...@jarvis:~# apt-cache policy plymouth-x11
@Claudio: does X crash as described in this bug, or does plymouth simply
drop you to VT1 (with the desktop accessible by pressing Ctrl-Alt-F7)
without any crashing on pressing 2 or Enter? I get this on my
laptop, although not on my desktop. This is a different problem, though,
the present bug
What I just described is covered by bug #538214, by the way.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
Bug behaviour: pressing 2 or Enter causes gdm restart.
On Sun, Mar 14, 2010 at 18:29, pablomme pablo...@googlemail.com wrote:
What I just described is covered by bug #538214, by the way.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
I agree with those above that the X/GDM crash bug is fixed, but like
pablomme, I now get bug #538214 instead. i.e. I wind up on VT1 instead
of VT7.
Also I get a report of plymouthd crashing after I log in and I no longer
have plymouth on shutdown.
--
Plymouth text-mode splash causes X to crash
It is fixed for me now.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
This problem still exists for me with current versions of lucid:
ii mountall 2.8
filesystem mounting tool
ii plymouth 0.8.0~-14
graphical boot animation and logger -
Attaching Xorg.log of X catching SIGQUIT (in gdm when pressing enter
right after entering the username).
** Attachment added: Xorg.log of X catching SIGQUIT
http://launchpadlibrarian.net/40939230/Xorg.0.log.old
** Changed in: plymouth (Ubuntu)
Status: Fix Released = New
--
Plymouth
The majority of users have confirmed that this bug is fixed, so marking
this again as fixed and unmarking bug #529230 as a duplicate.
** Changed in: plymouth (Ubuntu)
Status: New = Fix Released
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
Confirmed: latest update fixes the problem.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
Yes, for me this update fixed it too.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
Yes, for me this update fixed it too.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
** Changed in: plymouth (Ubuntu)
Milestone: None = ubuntu-10.04-beta-1
** Changed in: plymouth (Ubuntu)
Assignee: (unassigned) = Scott James Remnant (scott)
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You
Is there a work around for this yet ? I tried the one suggested but I
still get logged out on hitting the 2 key. I can handle some beta/alpha
problems but getting logged out in the middle of doing something in
Firefox is a little hard to take. Can't I just install another login
manager and do away
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:
-
Be careful when updating. I just did, rebooted and mountall couldn't
find some libplybootclient.so.2 library, so my laptop doesn't boot. I've
reported this as bug #538298. Wait for a matching mountall update before
updating (if I'm right to think that's the problem).
--
Plymouth text-mode splash
The update to mountall indeed fixes the problem. It's already in the
repositories for i386, but not for amd64 just yet. If you happen to run
into the problem as I did, the steps to get a booting system are in bug
#538298. Then just wait for mountall before updating plymouth.
--
Plymouth
Would this explain why the login screen appears on my right hand ( of dual
screen setup) and when I hit enter it appears on the left hand screen and I
have to login again?
The second login works.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
I have similar problem, but I can get past GDM with Enter with ease, but
when working, writing something in console or text editor, after some
random enter it crashes. I think reason is the same - Plytmouth.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
@Tony: the right hand/left hand login screen bug is covered in bug
#395314 (there's a workaround in comment 11,
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/395314/comments/11).
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
@Pēteris, yes, those are Bug 535318 and Bug 535316, which are really
duplicates, since the latter is the cause of the former.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a
@Pablomme So far I must've rebooted a dozen or so times. I have not seen
this issue recurring, yet it was affecting me before. Unless it is a bug
with very similar problems. For me, it seems to have been solved.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
This bug seems to be inconsistent. I will go for several days without
having any issues, but then I'll have it again for a few reboots. I have
not been able to correlate the behavior with any updates, but I'm not
convinced that the behavior disappearing for several reboots necessarily
means that
I still have it all the time. Last Lucid update was Tuesday.
Sean
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
I'm still having this issue. No updates have fixed anything for me yet.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I had exactly one reboot where the bug didn't occur (when I reinstalled
plymouth after reading it was fixed), and then it was back.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you
I'm also having this each time I boot up, and my machine has been updated
many times since I first posted.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of
The problem is understood and fix should be available shortly. As
frustrating as it is, there have been no plymouth updates to justify
comments about it still being an issue so please help keep this bug
manageable by clicking the Does this bug also affect you? button at
the top if it does.
--
The workaround didn't worked for me. It fixes the problem only a few
seconds after the system startup, when i can press 2 or enter as often
as i want. But a few (minutes) later, hitting enter crashes the system
again (for only one time).
--
Plymouth text-mode splash causes X to crash on first
I tried the above instructions and while the bug is fixed for the login
screen, when I press Enter the first time during the session X crashes.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification
I believe it may be related to the most recent kernel (2.6.32-16), as
before I updated to this kernel, I never experienced this issue, but
afterwards, I will login from GDM only to have it reset and I have to
enter my password again. Sometimes it doesn't even go to the GDM screen,
but it shows a
** Changed in: xorg-server
Status: New = Invalid
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
Madde, Matteo: I've had both the login problem, and the later Enter or
2 problem. The difficulty is the keyboard scancodes, so different
keyboards can have different triggers if the keyboards have different
scancode assignments.
Whenever it happens later, it seems that my crashed X session had
Interesting.
- My Xorg.0.log.old file says that X session --which crashed-- was running on
VT7.
- The current Xorg.0.log file says the present, stable X session is running on
VT8.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
There is a bug for the random characters on the tty: Bug 535316
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
I have the same issue. According to the Xorg.0.log and Xorg.0.log.old
files, my first X session was running on VT1 and my second one on VT7.
When I switch to VT1 after the second login, I can see what seems to be
a unsuccesful attempt to log in :
init: unreadahead-other main process (717)
The VT7 and VT8 I reported earlier were for my desktop (fresh 64-bit
install, binary nvidia driver, text-mode plymouth). My laptop (fresh
32-bit install, Intel 945GM, graphical-mode plymouth) also has VT7 for
the crashy session and VT8 for the working one according to the log
files.
Does anyone
Seems to be fixed for me now since I updated initscripts, sysv-rc and
sysvinit-utils in an update today.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
@ManhattanOS: not in my case. The patch sysvinit-utils received was
related to unkillable processes at shutdown, which seems unrelated. This
bug is somewhat intermittent -- how many times did you successfully
reboot cleanly into the desktop/login screen?
--
Plymouth text-mode splash causes X to
@Noel: yes it is.
Are the two bugs related somehow ?
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
I also suffer this problem.
Xorg.0.log: VT 7
Xorg.0.log.old: VT 8
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
I followed the Steve Langasek's instructions:
1) purge and install the plymouth package
2) checked the /etc/init/ folder and found a few new plymouth related files
that had not been there before
3) restarted PC and faced the same double loging problem
4) then executed: sudo mv
The temporary workaround intended to disable plymouth-splash:
sudo mv /etc/init/plymouth-splash.conf /etc/init/plymouth-splash.conf.disabled
does not work for me, because there is no /etc/init/plymouth-
splash.conf file on my installation.
Running: OS Ubuntu 10.04 alpha 3 64-bit fully updated
The temporary workaround intended to disable plymouth-splash:
sudo mv /etc/init/plymouth-splash.conf /etc/init/plymouth-splash.conf.disabled
does not work for me, because there is no /etc/init/plymouth-
splash.conf file on my installation.
Running: OS Ubuntu 10.04 alpha 3 64-bit fully updated
On Mon, Mar 08, 2010 at 08:01:55PM -, VladimirCZ wrote:
The temporary workaround intended to disable plymouth-splash [...]
does not work for me, because there is no /etc/init/plymouth-splash.conf
file on my installation.
Why isn't there? It's part of the plymouth package; if you have
I still have this bug.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
I've had this bug for a long time, but since yesterday, it doesn't crash
anymore!
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
1 - 100 of 105 matches
Mail list logo
