** Attachment added: "VGA connected on boot: external works properly (ONLY) in
this case"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/979748/+attachment/3537525/+files/xrandr-bootVGAconnected.txt
--
You received this bug notification because you are a member of Ub
** Attachment added: "VGA connected after booted (no signal, but Displays
detects)"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/979748/+attachment/3537524/+files/xrandr-VGAconnectedAFTERboot.txt
--
You received this bug notification because you are a member of Ubu
I will attach 3 files with the output of xrandr --verbose. However,
this is with Precise w/o edgers ppa. I'll first update to edgers ppa,
do it again, then later try Raring.
First file is xrandr --verbose when booting w/o VGA external connected
(and still disconnected). So this is "baseline".
** Attachment added: "VGA disconnected on boot: baseline xrandr --verbose"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/979748/+attachment/3537523/+files/xrandr-bootVGAdisconnected.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which
Thank you for the reply. I think I understand the situation and can
appreciate that many others would be negatively affected by my
experience being improved!
I do need more advice on how to "manually trigger a probe". In my
experience, connecting the monitor (after booted), then opening display
I am experiencing some crashes again after resuming from suspend. The
xserver-xorg-input-synaptics is indeed at the prior version, and for at
least a few weeks this seemed to solve the issues (to reveiw, for me at
least on my Thinkpad T520 the problem occurred in me being kicked out to
the login s
Timo or Jonatan,
Can either of you comment on "how" the crash happens? My issue (and I
think several others) was that I was kicked out to lightdm. If you are
getting actual freezes then this does seem separate.
If that is the case, maybe it is best to "separate the bug reports" and
mark the oth
I agree that it does appear that this bug report was possibly "hijacked"
as the OP issues arose before. A majority of the comments are after
July 18, with nothing between March and July.
But as the OP hasn't been involved since March, it is hard to know what
the status of the "original bug" is.
*** This bug is a duplicate of bug 956071 ***
https://bugs.launchpad.net/bugs/956071
Just confirming that there have been no crashes for me after reverting
the xserver-xorg-input-synaptics version and locking it in synaptic
package manager as well (advice from other bug #32 linked to above).
*** This bug is a duplicate of bug 956071 ***
https://bugs.launchpad.net/bugs/956071
** This bug is no longer a duplicate of bug 1026777
Xorg segfault: kicks out to login screen
** This bug has been marked a duplicate of bug 956071
Xorg crashed with SIGSEGV in XIGetDeviceProperty()
--
*** This bug is a duplicate of bug 956071 ***
https://bugs.launchpad.net/bugs/956071
** This bug has been marked a duplicate of bug 956071
Xorg crashed with SIGSEGV in XIGetDeviceProperty()
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
*** This bug is a duplicate of bug 956071 ***
https://bugs.launchpad.net/bugs/956071
Just confirming that there have been no crashes for me after reverting
the xserver-xorg-input-synaptics version and locking it in synaptic
package manager (advice from other bug #32 linked to above). The othe
Thomas in #34 makes a good point. The fix from #31 impairs the
functionality of the touchpad. I have changed using the advice from
#32, namely installing the previous version of xserver-xorg-input-
synaptics in synaptic package manager and then locking the version
there. It does seem that this i
Proposed workaround offered in posts #31 and #32 from here:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/956071
I have followed the suggestion from #31 and have not had any crashes
since.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscrib
Proposed workaround offered in posts #31 and #32 from here:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/956071
I have followed the suggestion from #31 and have not had any crashes
since.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscrib
Fix from #31 above seems to be working for me. Great day and thanks for
the help!!!
Am posting a reference to the other 2 bugs that seem closely related
(sorry, but above in #30 I linked back to this bug, not the other one!):
Here are the other 2 possibly related bugs I will refer back here for
I should cross reference that it seems there are a few additional
related bugs which seem to be very simliar, if not identical:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/956071
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1030535
--
You received this
I neglected to note that I have also been contributing to another bug
that specifically is about begin "kicked out to the login screen".
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1026777
>From this one (1026777), there is instructions about setting up your
machine to get a more d
Also similar reporting going on at this bug report:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/956071
I am guessing the OP here is experiencing the crash by being kicked out
to the login screen (lightdm)?
--
You received this bug notification because you are a member of Ubuntu-X
This seems to be simliar to the bug I have been following here:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/956071
Largely newer Thinkpads with Intel graphics. I have tested with the
xorg "edgers" PPA and still had the issue. I can reproduce the crash by
doing successive suspend
Finally got the /etc/X11/core created on recent crash yesterday.
Trying the gdb command, I was first presented with an error, after which
I ran the bt full command (inside gdb). Maybe I have a problem and gdb
is not running well? I'll post the reply when starting gdb, and then
the results of the
Lasse,
I followed the above steps, but am not getting a /etc/X11/core created
after a crash. I did install the dbg versions of core and video-intel.
One minor adjustment to the above instructions is that lightdm.conf is
in /etc/lightdm/lightdm.conf (just forgot the lightdm folder)
--
You recei
I should note that the machine I am having issues with is running 32
bit, so is not just 64bit related.
I just tried from a live CD on a stick (12.04 32 bit), and couldn't
reproduce the problem (not 100% sure it wouldn't crop up, but it
successfully woke from suspend 10 times in a row without kic
Andy Holyer, are you indicating this bug happens when hibernating as
well? If you are "suspending" and that is fully shutting down your
computer, starting again and logging in back to the place you were
before it seems like you are referring to "hibernating".
Regardless, it does seem like the sam
I have confirmed that the "kick out to login" still is a problem even
with wifi disabled (via hardware switch).
Stephen, I have the machine set to not suspend (due to inactivity) when
plugged in. So, we are shutting it down overnight, but keeping it
active during the day. Windows just isn't an o
I should note that I have seen the issue in 2 ways:
1. The manual 3 times suspend / wake leads me to the type of hang that
smwilsonau reports: nameile the "half-moon light keeps blinking" when
the lid is closed and it is attempting to suspend. Then, when opening
the lid, I am already back to the
bfrancom,
Any chance you have the time to try 3-4 successive "lid close, wait for
full suspend, lid open, wait until all settled" sequences? I can
consistently re-create the problem doing this and wonder if anyone can
confirm.
--
You received this bug notification because you are a member of Ub
Bug 1027619 does seem identical. I will mark the other as a duplicate
as we have a bit more testing in the comments listed here, but good
summary of problem in the other listing as well.
Again, I am happy to install the debug versions for xserver-xorg but
would appreciate any help on how to best
*** This bug is a duplicate of bug 1026777 ***
https://bugs.launchpad.net/bugs/1026777
** This bug has been marked a duplicate of bug 1026777
Xorg segfault: kicks out to login screen
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in
*** This bug is a duplicate of bug 1026777 ***
https://bugs.launchpad.net/bugs/1026777
indeed I believe this bug seems identical to what I am experiencing and
have reported on in bug 1026777 (as linked to above in comment #6).
--
You received this bug notification because you are a member of
** Summary changed:
- Xorg segfault
+ Xorg segfault: kicks out to login screen
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1026777
Title:
Xorg segfault: kicks out to login screen
To manage
OK, I have done a bit more testing.
In either Ubuntu (3D) or Ubuntu 2D, if I close the lid, wait for it to
fully suspend, then re-open it, wait for it to fully connect and stop
disk activity, then repeat, the 3rd time I do this the suspend light
that blinks until it suspends (normally blinks about
Lasse,
Interesting that you are on a T520 Intel graphics machine as well. So
we clearly are having the same issue. I have a 32 bit install to be
consistent with some other older desktop machines I support that cannot
handle 64 bit.
I got this machine new a few months ago so have only seen the p
Did your screen freeze or did it kick you back to the login prompt? I
have had a random issue of waking from suspend and then after a minute
or 2 getting kicked out to the login prompt. I have a similar backtrace
in my /var/logXorg.0.log.old file.
Fom me this happening with a Thinkpad T520 with
This may not be just a nouveau driver issue. I've got standard Intel
graphics and have been getting the same error on my "clean install" of
Ubuntu 12.04 B2 (all updates applied and still get the error daily).
--
You received this bug notification because you are a member of Ubuntu-X,
which is su
Here is what I have add to my .xprofile:
===
xrandr --newmode "1280x1024_60.00" 109.00 1280 1368 1496 1712 1024
1027 1034 1063 -hsync +vsync
xrandr --addmode VGA1 1280x1024_60.00
===
Note that the reason for these 2 lines is that Ubuntu doesn't prop
** Tags added: external monitor vga
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/979748
Title:
Laptop with Intel Graphics: external VGA monitor only gets signal on
boot (no “hot plugging”)
Public bug reported:
I am able to get an external VGA monitor (or projector) to work if I
start my laptop with it connected. However, if I start the laptop with
it disconnected there is no signal on the external. The Displays screen
shows the external, and thinks that it is active, but there is no
38 matches
Mail list logo
