@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
https://wik
Helge,
Since the original problem was resolved (it was rather specific), and
since this bug is therefore marked as closed, this bug doesn't show up
on searches for bug triagers to work on. While I noticed your comments
because I'm still subscribed, those triaging problems such as yours
probably wo
That's a perfectly reasonable question, Daniel.
Thanks to Chase, it is going to the main natty repositories, no need for a PPA.
It has already been published at
http://us.archive.ubuntu.com/ubuntu/pool/main/x/xserver-xorg-input-synaptics/
and should
be headed to all of them shortly (maybe it ha
Work-around:
If, like me, you have difficulty not touching the touchad while you type, you
can use xinput to disable it:
xinput --list
and find the id of the touchpad. Say it is 12:
xinput set-prop 12 "Device Enabled" 0
--
You received this bug notification because you are a member of Ubuntu
natty has moved the mesa package version past that in my ppa.
As an update, there are plans to upgrade mesa in natty to 7.10, perhaps
shortly if xorg-edgers testing goes well. It appears to me that the
upstream patch referred to above is currently included in 7.10. (5b15b5f
in git://cgit.freedeskt
** Branch linked: lp:~jsjgruber/ubuntu/natty/mesa/mesa.fix681915
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in ubuntu.
https://bugs.launchpad.net/bugs/681915
Title:
garbled graphics and text after launching unity
___
** Changed in: mesa (Ubuntu)
Assignee: (unassigned) => John S. Gruber (jsjgruber)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in ubuntu.
https://bugs.launchpad.net/bugs/681915
Title:
garbled graphics and text after launch
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in ubuntu.
https://bugs.launchpad.net/bugs/681915
Title:
garbled graphics and text after launching unity
___
@manny:
Any luck getting it to work?
Anyone else?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in ubuntu.
https://bugs.launchpad.net/bugs/681915
Title:
garbled graphics and text after launching unity
The patch from upstream:
Author: Dave Airlie
Date: Fri Dec 10 15:40:48 2010 +1000
r300g: fixup rs690 tiling stride alignment calculations.
The RS690 memory controller prefers things to be on a different
boundary than the discrete GPUs, we had an attempt to fix this,
but it still failed, this
I was able to trace this problem on my machine to libgl1-mesa-dri.
Using git bisect I was able to identify and successfully test mesa
commit 32218e4cc88f7dedebadffe4a80247decf4498f1 as addressing the
problem.
I've rebuilt the mesa package with this patch cherry-picked in
ppa:jsjgruber/ppatwo, and
** Changed in: mesa (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in ubuntu.
https://bugs.launchpad.net/bugs/694430
Title:
mesa bug affects new kernels
_
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launchpad.net/bugs/681915
Title:
garbled graphics and text after lau
apport information
** Attachment added: "peripherals.txt"
https://bugs.launchpad.net/bugs/681915/+attachment/1784400/+files/peripherals.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launch
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/681915/+attachment/1784398/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "glxinfo.txt"
https://bugs.launchpad.net/bugs/681915/+attachment/1784399/+files/glxinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "XorgLog_.txt"
https://bugs.launchpad.net/bugs/681915/+attachment/1784397/+files/XorgLog_.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launchpad.ne
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/681915/+attachment/1784401/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launchpad.ne
apport information
** Attachment added: "XorgLogOld_.txt"
https://bugs.launchpad.net/bugs/681915/+attachment/1784396/+files/XorgLogOld_.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launch
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/681915/+attachment/1784395/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/681915/+attachment/1784394/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "UdevLog_.txt"
https://bugs.launchpad.net/bugs/681915/+attachment/1784393/+files/UdevLog_.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launchpad.ne
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/681915/+attachment/1784392/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/681915/+attachment/1784391/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "ProcModules_.txt"
https://bugs.launchpad.net/bugs/681915/+attachment/1784390/+files/ProcModules_.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.laun
apport information
** Attachment added: "ProcInterrupts_.txt"
https://bugs.launchpad.net/bugs/681915/+attachment/1784388/+files/ProcInterrupts_.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bug
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/681915/+attachment/1784389/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launch
apport information
** Attachment added: "ProcCpuinfo_.txt"
https://bugs.launchpad.net/bugs/681915/+attachment/1784386/+files/ProcCpuinfo_.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.laun
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/681915/+attachment/1784385/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launch
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/681915/+attachment/1784384/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/681915/+attachment/1784383/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "GconfCompiz.txt"
https://bugs.launchpad.net/bugs/681915/+attachment/1784382/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launch
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/681915/+attachment/1784381/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.laun
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/681915/+attachment/1784380/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.laun
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/681915/+attachment/1784379/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/681915/+attachment/1784387/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.
Architecture: i386
CompizPlugins: No value set for
`/apps/compiz-1/general/allscreens/options/active_plugins'
CompositorRunning: compiz
DRM.card0.LVDS.1:
status: connected
enabled: enabled
dpms: On
modes: 1440x900 1280x854 1280x800 1280x720 1152x768 1024x768 800x600 848x480
720x480 640x480
e
If I run qtdemo as follows the corruption disappears:
LIBGL_ALWAYS_INDIRECT= qtdemo
This also works with firefox flash videos if I start firefox's initial
browser instance with this environment variable.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscr
Jaime:
I've applied the patch to mesa from the above bugzilla bug report and
built it in my ppa. You may want to try it. It didn't fix the bug I'm
having but I guess it should fix yours.
The ppa is: ppa:jsjgruber/ppa
--
You received this bug notification because you are a member of Ubuntu-X,
wh
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 add
*** This bug is a duplicate of bug 615549 ***
https://bugs.launchpad.net/bugs/615549
@Jamie:
Looks like Martin is taking care of it in #615549. If I recall correctly, it
will be (has been?) uploaded to the proposed queue and, after testing, it will
be released to Lucid.
--
X starts on wron
*** This bug is a duplicate of bug 615549 ***
https://bugs.launchpad.net/bugs/615549
Are you running the latest version of gdm? gdm (2.30.5-0ubuntu4) or
later? See bug #615549.
I know this may sound odd, but are you running apache, and if so, are you
running the latest version? apache2 (2.2.
** Description changed:
- Binary package hint: xorg
- After the system boots and the plymouth screen disappears and X starts
- up, if I press the enter key (occurs only with the enter key) X shuts
- down and starts again in around 2 seconds. In the session of X that
- comes up after this, the p
In syslog you might find messages like:
gdm_binary[2542]WARNING: GdmDisplay: display lasted 0.945450 seconds
Those are the ones Jamie has coming out quickly. I only get one when I start.
It may be easier to look for those than to look at the log files.
--
X starts on wrong tty: pressing enter af
You may want to check out bug #626723
--
X server crash on my first login after I insert my password to unlock my key
ring
https://bugs.launchpad.net/bugs/631003
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in ubuntu.
_
@Seth:
I just saw that I missed several of your messages above. In particular 98 and
99. I'm sorry. Before I say it you coded it and had it building on launchpad.
Great.
I see no problem with your code. I built your change here and am running
it successfully. Since I didn't see the bug I can't s
@Jamie: Rats.
We don't need the plymouth:debug anymore. Would deleting it help? Can
you simply go back to where you were last night when you were getting
logs (albeit with the tty1 bug). If you can, maybe you can try Seth's
new gdm fix.
modeset and nomodeset are other possible things to try (I ca
@Bilal:
Congratulations.
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
___
@Jamie: One of the earlier X logs you posted had an error that ended
like that--without giving any backtrace.
I see you are running apache. Does Dino's have your fix?
Sounds like our fraternal twin bug may have been fixed since Bilal
confirmed it is gone. Great catch, Dino. It also sounds like vt
@Jamie:
Great! That's confirmation that gdm is starting too early relative to the
tty's. and helps confirm similarity of your situation with Seth's.
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notification becaus
@Seth:
I don't believe initctl passes a VT parameter. gdm is either starting X with a
VT parameter, or not. It determines whether plymouth is running and if it is,
and if it has its screen before the user, gdm tries to determine what VT that
is and specifies that to X in a VT parameter. If that
@Brian
This bug was split at about comment 30. We have been working on the case where
the X crash happens some time after login because it has been started on tty1.
Bilal's case start on tty7 is now being discussed in bug #626723. I feel a
little bad that we aren't discussing his situation but t
I don't see any errors in the dmesg log and it looks like the nvidia
kernel module is ready rather late in that log. Looking at the udev log
I would guess that the module isn't loaded any sooner than about .31
seconds before the last entry in the udev log (if I'm reading it
correctly).
@Seth:
*IF*
@Jamie,
It's my pleasure to work with you all.
Would you mind posting your /var/log/udev file and /var/log/dmesg file?
It probably doesn't matter when they are collected relative to when the
bug occurs.
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.ne
So here is a theory for Seth and Jamie's case:
gdm starts its race with the tty's before the nvidia software is really
ready for X.
Plymouth is running and gdm starts up, hand shakes with plymouth. Starts
X.
Gdm in the handshake tells plymouth to quit and it does.
X crashes because it is too ea
Seth:
That is simply wonderful.
One of Jamie's logs from comment 62 says:
(**) Sep 07 22:16:47 NVIDIA(0): Enabling RENDER acceleration
(II) Sep 07 22:16:47 NVIDIA(0): Support for GLX with the Damage and Composite X
extensions is
(II) Sep 07 22:16:47 NVIDIA(0): enabled.
NVIDIA: could not open
Hi Dino
Thanks for the information. That's good about firstserver.stamp.
>From the ps.out I assume that the bug is still gone on your system since
X started on tty7. If it ever fails again (starting on tty1-tty6) that
time stamp, the output of ps before X crashes, and, if possible, the
output in /
It would be great if anyone else having the problem could post the
output from the ps command on their system while they are running X on
tty1 through tty6.
@Dino:
That's great news!
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You rec
@Dino
Could you attach the output from ps as Jamie did? If it starts happening again
perhaps you can do the same again during a session you expect to crash?
@Jamie and Dino
Could you look again at that file creation time?
sudo ls -l /var/run/gdm/firstserver.stamp
It should exist and be empty, i
It's a shame about the crash getting in our way, but oh well. I don't
see anything in the log either, sad to say. the acpid messages at
10:00:17 are from an unrelated daemon that tells interested processes on
your computer about closing the lid, etc., if I'm not mistaken.
Could you recreate the si
@Jamie,
Do you remember how you got the first log?
Could the log you posted be from some time it hung? If it's complete it
does look like plymouth crashed. For the crash situation does anything
get recorded in the plymouth-debugging log?
Maybe we should look in your /var/log/syslog from the time
@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 should
@Carl,
Dino99 has the problem with Maverick.
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
___
Thanks for sticking with this even though you guys have found
circumventions. If someone can fix this without adding boot parameters,
etc. -- if it just works-- it will be better for many Ubuntu users.
@Jamie:
It looks like :2.log.1 is what I would expect for the bug we have been
hunting. It was
Jamie and Dino:
If I understand, you each reported a problem with an X crash when X had
already crashed. As Dino pointed out, that's very different. Would you
please post the failing Xorg log? You can probably figure out which one
by the time on the file.
--
X starts on wrong tty: pressing enter
Cool, Jamie. I'm glad you found a work-around, and I appreciate your
kind offer to post the logs later. I'd like to see how they match up
with dino's, both with regard to the messages dino saw in his plymouth
log post, and with regard to the little dance gdm and plymouth do to
keep on the same VT7
Our comments crossed. Sorry.
Please take your time and only do things you are ok with.
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver
I don't have /etc/grub/default either. I do have /etc/default/grub. The
file names are confusing.
I see no reference to the former in update-grub or grub-mkconfig, but
grub-mkconfig includes the contents of /etc/default/grub. Are you
missing /etc/default/grub?
I sometimes get nervous about grub,
On Tue, Sep 7, 2010 at 10:53 AM, dino99 <625...@bugs.launchpad.net> wrote:
> hi Jamie,
> have done it by editing the boot line (E) into grub menu ( added at end of
> quiet splash ) then boot (ctrl+x)
Yep. That's what I do, too. As soon as the grub menu appears I move the
arrow to the item I want
merci, Dino
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
___
@Jamie:
Since I'm only another member of the community it's completely possible
that I won't be able to see this through to a fix. A glance from a
plymouth or gdm developer may mean more progress than I could make in
days. If it's ok with you, though, maybe we can move this towards a
successful tr
@Jamie:
What are you seeing right before gdm brings up the login screen? In particular,
are you watching the splash screen?
>From the command "sudo ls -l /var/run/gdm" when was the
firstserver.stamp file created?
--
Pressing Enter crashes both X and plymouth in graphical mode
https://bugs.launc
I'm an Ubuntu amateur, so believe what Steve says over what I say. He's
no amateur.
I don't think the message "requirement "user ingroup nopasswdlogin" not
met by user "bilal" " is a problem. I see from the forum post
http://ubuntuforums.org/showthread.php?t=819198 that this is a
requirement that
@Jamie:
If you don't mind my asking, what version of Plymouth are you running?
--
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-X,
which is subscribed to xserver-xorg-video-
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,
whic
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 b
** Attachment added: "Xorg.0.log.old"
http://launchpadlibrarian.net/40308463/Xorg.0.log.old
--
X server crashes when enter key is pressed
https://bugs.launchpad.net/bugs/529230
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubunt
I can reproduce at times right after booting current Lucid kernel.
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
** Tags added: lucid
--
X server crashes when enter key is pressed
https://bugs.launchpad.net/bugs/529230
You received this bug notification because you are a m
This happens to me intermittently. I noticed it some weeks ago, I didn't
see it for a while, and it returned in the last several days. It may
happen more often if I boot with the radeon.modeset=0 option and I also
see it with a rather new 2.6.33 release candidate stock kernel I
sometimes boot. It m
I turned Compiz and the Snapping Windows plugin on with Karmic but I
didn't see the problem.
--
windows seem to want to be at the top-left
https://bugs.launchpad.net/bugs/321128
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-syna
80 matches
Mail list logo
