This is far from a clean or truly simple workaround, but FWIW, here's
what I've done... I thought logrotate, with the copytruncate option,
might be a reasonable hack to address that rapidly growing ~/.xsession-
errors file. (BTW, I'm running Xubuntu 11.10). Unfortunately, the out-
of-the-box
I had the same experience as @gridcube (comment 15) on Xubuntu
11.10/Oneiric; very slow first open of Thunar, with multiple instances
popping open. Last test, I tried to open my ~/Downloads folder in Thunar
(via Kupfer); while nothing was happening, I tried opening my home
folder in thunar from
For a year or more I've used the fspc program
(http://sourceforge.net/projects/fsp-lnxdrv/) to run a startup script
that would reset my Sentelic FSP (to disable the tap-to-click and hot
spots for horizontal/vertical scrolling, because they just drove me
nuts, as there's no disable-while-typing
@dualityim: FWIW, your workaround in comment #28 works well for me as
well (Maverick 64-bit). Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/625670
Title:
Not all desktop items are themed
I can confirm this as well: top panel always looks awful after a reboot;
generally takes numerous logout/login cycles to get clean theme; fast
system w/nVidia, i7 and SSD:
Maverick/10.10 64-bit
System76 Serval Pro (SER-P6) laptop
Core i7-840QM Processor ( 45nm, 8MB L3 Cache, 1.86GHz )
8 GB - DDR3
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
resume from suspend does not initialize the display on 2.6.35 kernel
https://bugs.launchpad.net/bugs/656631
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Unfortunately, the SUSPEND_MODULES workaround did not work for me after
all. I went almost a week without suspend/resume problems, but the
problems have appeared again. A few days ago I had a new one, where
trying to suspend did not fully suspend--yet I was able to get the login
screen, so no
It looks like I may have a fix/workaround that works for me, from this forum
thread:
http://ubuntuforums.org/showpost.php?p=10100625postcount=75
Basically, I add my wireless module ID to SUSPEND_MODULES in
/etc/pm/config.d/unload_module. Not only does this seemed to have made
my suspend/resume
mikeos, my laptop specs:
System76 Serval Professional
- Graphics Nvidia GeForce GTX 285M Graphics with 1GB GDDR3 Video Memory
- Processor Core i7-840QM Processor ( 45nm, 8MB L3 Cache, 1.86GHz )
- Memory 8 GB - DDR3 1333 MHz - 2 DIMMs
- Hard Drive 160 GB Intel X25-M Solid State Drive
--
resume
I'm pretty sure this problem only manifests itself if I suspend or
resume while my SerP6 laptop is running on battery power. I'm fairly
certain that I've never had a problem on suspend or resume if I'm always
connected to AC power, but that's obviously hardly ideal with a laptop.
That said, I
I have a System76 Serval Pro (SerP6) laptop running the latest Ubuntu
10.10 Maverick 64-bit.
Suspend/resume works fine most of the time, but occasionally I see the
blank screen upon resume, while all other expected lights are on--it's
as if it has resumed, but I can see nothing and no key strokes
Martin, Seth: Thanks for the confirmation. FWIW, I've narrowed my
newfound nasty crashes down to the Chrome browser, with nVidia drivers
installed, but only when on battery power! If I disable nVidia drivers,
or simply keep AC power connected to my laptop, everything is fine; but
with battery
Martin,
Based on my previous comment (#79), I'm curious whether you think this
bug is still relevant or whether I should be opening a new bug (I'm
guessing the latter). I've further confirmed the battery power
relationship by working for a few hours with AC power plugged in and now
crash, then
Martin,
As you suggested, I've changed to this in my gdm.conf:
start on (filesystem
and started dbus
and stopped udevtrigger)
I will run with this for normal use and report back in a few days, or
whenever a crash might occur (hopefully none!). I can also do 20 reboots
in a
Martin:
Crashes which happen during the running GNOME/KDE session are
unrelated to this.
Interesting. After sharing extensive results in bug #625239, it seemed
quite clear that my issue related to the correct bug and that #625239
was a duplicate of this one (and has been marked as such). Am I
Martin:
by looking at glxinfo or just the X server look it should
be possible to detect this situation right after boot.
Sorry, I'm not entirely sure what to look for, but I've attached the
output from a glxinfo command just after boot/login.
** Attachment added: glxinfo.out
Seth:
Include
ps -ef | grep X
gdmtty=$(ps --no-heading -o tty -p $(pgrep X))
stty -F /dev/$gdmtty
ps -f -t $gdmtty
I rebooted, switched to tty1 and I'm attaching the output from the
above. Thanks.
** Attachment added: out_20100922-1156.tgz
@John
Do you remember if you are typing anything when they happen? Anything
else you can remember about the circumstances? You mentioned above a
resume, is that always or usually involved?
I'm fairly certain I was *not* typing anything, but usually had just
clicked something (e.g., a link). I
I have some new clues on my crashes! First, Martin's changes to my
gdm.conf as mentioned in comment #67 did not fix all for me, as I just
had a few more crashes. What I noticed (and had a hunch this morning
too), is that I believe I've primarily (if not always) had crashes occur
while on battery
The patch from comment #64 does not entirely fix this issue for me on
Lucid, although it has certainly improved things. I looked at the patch
and changed my /etc/init/gdm.conf file accordingly (hopefully that's all
I was supposed to do?). My gdm.conf is included with the archive
attached to this
As I mentioned in my previous comment, I had another GDM crash right
after a reboot. The logs for this one are attached here. Please let me
know if there's anything else I can provide. Thanks.
** Attachment added: logs_20100921-2053.tar.gz
Forgive me if I'm missing something, but based on comments from Martin
and Steve, and Seth's thorough testing reported in comment #159, my
understanding is that I should simply wait for the bug #615549 fix to be
back-ported to Lucid. Is this correct? Should I be updating bug #615549
for Lucid in
Steve Langasek wrote in #150:
Thanks. Could you now provide the same files when *not* booting with this
workaround?
Yes, the attached archive contains two sets of logs, both without
vga=799 or any other workaround in place. One has quiet splash
appended to the boot line, which landed X on tty2
Steve,
Please show the contents of a plymouth:debug log, and /proc/fb, when
booting with vga=799 (and without grub_gfxmode set).
Attaching /var/log/udev, /var/log/plymouth-debug.log and /proc/fb after boot
with no GRUB_GFXMODE set and:
GRUB_CMDLINE_LINUX_DEFAULT=vga=799 plymouth:debug
Steve,
Seth, Jamie, can one of you also show the output of 'grep fb
/var/log/kern.log' on a system showing this problem?
Attached, after boot with standard configuration (no workarounds or
related custom config at all).
** Attachment added: kern.log-grep-fb.out
Steve,
I meant to confirm that the boot that produced the output file attached to
comment #127 did indeed land me with X on vt2, and I did crash, as expected,
after a few minutes, when pressing enter in Terminal.
--
X starts on wrong tty because gdm starts before nvidia driver is ready
Steve,
You might also be able to confirm this is the problem by commenting out
the graphics-device-added fb0 part of the start condition.
Okay, testing with standard disto version of /etc/default/grub and the
following in my /etc/init/gdm.conf:
start on (filesystem
and started dbus
Seth,
So let me get this straight, you just removed the graphics-device-added
fb0 PRIMARY_DEVICE_FOR_DISPLAY=1 disjunction?
Yes, that is exactly what I did, and nothing else.
--
X starts on wrong tty because gdm starts before nvidia driver is ready
https://bugs.launchpad.net/bugs/625239
You
Steve, Seth,
The graphics-device-added fb0 PRIMARY_DEVICE_FOR_DISPLAY=1 removal
tweak is not a guaranteed workaround after all. I just booted up again
and crashed within a minute of use. I was just waiting for a Chrome tab
to open--no keyboard activity this time.
--
X starts on wrong tty
I seem to have discovered a slightly new style of crashes, which I believe have
only occurred when I have a modified /etc/init/gdm.conf file. Yesterday and
today I've witnessed this new crash behavior with both:
* Seth's /etc/init/gdm.conf workaround from
Seth,
May I suggest _not_ tweaking your gdm.conf in that particular way
then?
Yes :) I did so only as a workaround, but obviously that was not stable.
I also just discovered that the same crashes can now occur even with a
untouched gdm.conf. Possibly a different bug, sure, but I hope not!?!
Seth, thanks for the additional workaround. I've applied your patch from
ppa:bugs-sehe/gdm625239 and all has been well for about an hour. My boot
time seemed a little slow again, after re-enabling my nVidia drivers,
but I can live with that if I have a stable X session! I will report
back if I see
Seth,
I just installed bootchart, rebooted and had 2 quick crashes (with your
patch installed). I only see black screen when switching tty, so unable
to check out logs so far. I'll report back soon.
--
X starts on wrong tty because gdm starts before nvidia driver is ready
Seth,
With just a couple bootcharts, it appears I take 4 seconds longer to
boot with nVidia drivers enabled. Also, despite having an extremely fast
machine, your boots were about 400% faster than mine! I've attached the
two, in case they're of any interest.
Is there any reason installing
Okay, I've tested Seth's patch to /etc/init/gdm.conf from
https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/532047/comments/91
I first changed my /etc/default/grub back to basics and ran update-grub
(so, a state that would normally cause this bug to occur after boot). I
did not notice a
New crash for me, possibly a fluke. I reverted my /etc/default/grub to
simply use the plymouth:debug on the boot line as a workaround, and also
reverted my /etc/init/gdm.conf (after trying Seth's workaround). My next
reboot looked normal, and X was on tty7, but I crashed very quickly, and
not when
Okay, the crash from tty7 happened twice in a row, after reboots, for
me. I now see that I'd changed two different variables when I thought
the simple plymouth:debug was acting as a workaround. I'd also changed
these lines in /etc/default/grub, to allow me to catch grub and test
boot parameters
@dino99: These crashes definitely seem to correlate with the fastest
systems. Myself and a few others with the bug have SSD, 8 GB and fast
processors.
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notification
@John: Yes, I'm running apache. I don't see a way for me to test Dino's
bug 626723 on my Lucid machine. That bug appears to have a proposed fix
for Maverick. Also, the suggested workaround doesn't make sense on Lucid
--there is no stty sane line in my /etc/init.d/apache2.
--
X starts on wrong
John, I've attached ps aux output while X is on tty2 (this is usually
what happens, but occasionally tty1--eventual crash in both cases).
Thanks.
** Attachment added: ps.out
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/625239/+attachment/1560408/+files/ps.out
--
X
@dino99: I installed updates this morning, which included the mountall
update for Lucid. I rebooted, but still ended up with X on tty2, and
crashed to the login screen after about 30 minutes of bouncing around in
Chrome browser tabs.
--
X starts on wrong tty: pressing enter after 5 minutes
@John,
Thanks again for keeping us moving. To the best of my
ability/understanding, your theories are sound to me, FWIW! Here's some
more info, as requested:
(a) My /var/run/gdm/firstserver.stamp does have a time matching my most
recent boot.
(b) I searched all of my /var/log/Xorg.* files for
@John, my /var/log/udev file...
** Attachment added: udev
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/625239/+attachment/1563869/+files/udev
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this
@John, my /var/log/dmesg file...
** Attachment added: dmesg
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/625239/+attachment/1563870/+files/dmesg
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received
I tried editing the boot line from the grub menu and added
plymouth:debug to the end, but then the boot just froze at the splash
screen. I was unable to switch to another VT or find any way to get rid
of the splash screen, so had to do a hard power off. It did, however,
produce a debug log file,
I reproduced the bug and will now attach these three files, which all had the
time stamp of the crash/reset to GDM login screen (and as usual, was on VT1
after boot, then VT8 after crash and second login):
/var/log/Xorg.2.log.old
/var/log/gdm/:2.log.1
/var/log/gdm/:2-slave.log.1
** Attachment
** Attachment added: :2.log.1
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/625239/+attachment/1557211/+files/%3A2.log.1
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notification
** Attachment added: :2-slave.log.1
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/625239/+attachment/1557212/+files/%3A2-slave.log.1
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug
John:
Unfortunately, I don't seem to have an Xorg log for yesterday's crashes. I'll
try to be more diligent about grabbing those, but I had some quick unexpected X
crashes when experimenting with grub settings yesterday. I do have a bunch of
logs dated for yesterday under /var/log/gdm/, but I
@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
More test results, log, and another workaround:
- booting with plymouth:debug added to boot line, but quiet splash removed,
results in booting to VT7 every time, and no crashes (sample plymouth debug log
attached).
- booting with quiet plymouth:debug (but no splash), same results--boots to
VT7
@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
@Carl,
Those grub resolution settings wreak havoc on me. I booted to vt2, so logged
out, logged in, on vt8. Then, for the first time ever, I had the X reset after
a logout/login cycle (some logs attached for this). Shortly thereafter, I had
yet another crash, and these did not seem to be
@John,
Yes, the first plymouth-debug.log was generated the first time I added
plymouth:debug to the boot line, but I had a freeze on the splash screen and
powered off. When I booted again without plymouth:debug I found that log file
there, so it obviously generated that prior to the freeze and
@John: Thanks very much for helping this along.
I watched very closely when I booted this morning, and I'm certain that I'm
seeing a flash of a text screen just after the Ubuntu splash, but before the
GDM login screen, and I'm certain that it is showing this message near the top:
GLib-WARNING
John, here's the version info you requested:
gdm 2.30.2.is.2.30.0-0ubuntu3
upstart 0.6.5-7
plymouth 0.8.2-2ubuntu2
nvidia-current 256.52-0ubuntu0sarvatt3~lucid
Next I'll reboot with plymouth debugging and post some logs...
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
Okay, this is really strange--I suddenly have no /etc/grub/ directory.
I've edited /etc/grub/default before, and I'm certain I had a couple
backup files in there too. Any thoughts???
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You
Breaking news! John, I think you're definitely on to something with your
idea of this being a race condition. When I just rebooted, the periodic
disk check ran (at the splash screen, essentially), so I paid close
attention, remembering the race condition hunch. I noted that there was
no flicker
Steve: I've always modified /etc/grub/default in the past, as suggested here:
https://wiki.ubuntu.com/Grub2#grub (/etc/default/grub)
...and in `cat /etc/grub.d/README`:
All executable files in this directory are processed in shell expansion order.
00_*: Reserved for 00_header.
10_*: Native
FYI: In an attempt to keep my environment as clean as possible, I've removed
the ppa:ubuntu-x-swat/x-updates repo, which I'd added earlier in an attempt to
fix this issue (http://ubuntuforums.org/showthread.php?t=1545846). Since this
did not work, I've removed it and reinstalled my
Doh! Sorry for the confusion, I was just looking for /etc/grub/default
instead of /etc/default/grub. I'll have another cup of coffee and try
this again ;-)
On another note, in an effort to get that file back (the one that I'd a
mistaken path for, which was there all along), I installed
Okay, I've done some experimenting with my linux command options. If I
have vga=799 on there, I boot to tty7 every time. With or without the
quite and/or splash options, I see the same results. However, when I
tried vga=771, I end up on tty1 or tty2 again.
So, for whatever reason, this line in my
@Carl: I'm sorry to say that your suggested changes to /etc/default/grub
did not work for me. I noticed that 1920x1080 was not listed when I
tried the vbeinfo command from a GRUB command prompt, as suggested in
GRUB2 docs/help. I also tried a resolution that *is* listed as supported
for me,
@John:
I do see a splash screen. Everything is relatively quick, as I have an SSD in
my new System76 laptop :D I see a blank screen with a blinking cursor, followed
by a quick flicker to the splash screen, followed by another
blank-screen/flicker, and then the login screen. I think there's a
*** This bug is a duplicate of bug 532047 ***
https://bugs.launchpad.net/bugs/532047
I know this is suggested as a duplicate of bug #532047, but this one seems more
closely aligned with the behavior I'm experiencing. I'm running Ubuntu 10.04
64-bit on a new System76 Serval Pro (serp6)
*** This bug is a duplicate of bug 532047 ***
https://bugs.launchpad.net/bugs/532047
@John: Interesting... I meant to also comment on your question about
stuff like this showing up in /var/log/auth.log:
$ cat /var/log/auth.log | grep FAILED
Sep 1 21:38:16 jkrug-serval login[6215]: FAILED
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
*** This bug is a duplicate of bug 532047 ***
https://bugs.launchpad.net/bugs/532047
@John:
Thanks for the response. I'm pretty sure I was on tty1 on 9/2 when X
crashed, but it was either tty1 or tty2--that I'm certain of. It's
always either tty1 or tty2 (I believe it's VT2 most often) upon
After spending hours pouring over Google results and bug reports like
bug #529230 and bug #532047, I believe this is the bug I'm seeing on my
Lucid (Ubuntu 10.04 64-bit on a new System76 Serval Pro--serp6) laptop.
I have a decent amount of information to share, which corroborates this
bug, and
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
Bugs, which is subscribed to
@John:
Synaptic shows plymouth 0.8.2-2ubuntu2.
--
Pressing Enter crashes both X and plymouth in graphical mode
https://bugs.launchpad.net/bugs/625239
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Steve,
I have X running on VT1 or VT2 after every reboot, and I always
eventually have X crash on me when pressing Enter (but never the first
pressing of Enter).
--
Pressing Enter crashes both X and plymouth in graphical mode
https://bugs.launchpad.net/bugs/625239
You received this bug
I too am affected by this bug, on my Dell Vostro 1510 laptop. I see the
same error message during boot: mmc0: Unknown controller version (2).
You may experience problems. I can also confirm that the error message
is in /var/log/kern.log and /var/log/dmesg. I just installed Ubuntu
10.04 64-bit to
I'm running Ubuntu 9.10 64-bit (final) on a Dell Vostro 1510 laptop.
Using recordMyDesktop with default out-of-the-box configuration
produced very choppy and out-of-sync audio. Simply changing the
AdvancedSoundDevice setting from DEFAULT to plughw:0,0 fixed
everything! That was really annoying,
74 matches
Mail list logo
