Hey,
Op 24-06-12 07:03, Piyush Roy schreef:
> Hi Marteen,
>
> Even in virtual console it freezes.
>
> Steps I performed.
>
> 1) Login to my desktop session
> 2) Run command "pgrep Xorg" to get the pid. Lets say 1122
> 3) Then I pressed "control-alt-f2" to go to virtual console.
> 4) Run command "p
Hey,
Op 23-06-12 02:59, Piyush Roy schreef:
> Yes, I am doing it locally. Not ssh. I have no way to ssh. Is it not
> good to do it locally ? If so then I am afraid I cant give output
> regarding this bug.
>
If you are doing it from inside the X server itself, the first thing
attaching a debugger d
Hey,
Op 22-06-12 19:16, Piyush Roy schreef:
> I think even gdb hangs.
>
> At least from this bug I conclude that Bug #342588.
>
> =
>
> Hi Maarten,
> I tried to follow ur steps but it does not accepts any input at all. Here,
> are the steps
Hey,
Op 22-06-12 16:01, Piyush Roy schreef:
> I already said in my previous comment that when I run gdb to debug xorg,
> the system freezes indefinitely. I have run this command
>
> sudo gdb /usr/bin/Xorg 2>&1 | tee gdb-Xorg.txt
>
> ** Attachment added: "gdb-Xorg.txt"
>
> https://bugs.launchpa
Erm that's not from that repository, only the xorg-server package there
is useful. 2.19.0-0ubuntu1~xup1 is not in it.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/966744
Titl
For those on precise (not quantal), could you test the xorg-server
package in ppa:ubuntu-x-swat/ppa ? X dying on resume seems to look
similar and at least 1 person had a dmesg captured of a Xorg segfault
here.
--
You received this bug notification because you are a member of Ubuntu-X,
which is su
** Changed in: xserver-xorg-input-synaptics (Ubuntu Precise)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/941953
Title:
Xorg cras
** Description changed:
- This crash occurred on resume from suspend (to RAM) on a precise box up-
- to-date as of Feb 24.
+ [Impact]
+ Crash bug and silent memory corruption due to out of bounds access that may
not be noticed until much much later, in which case it's fatal.
+
+ [Test Case]
+ Th
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Assignee: Chase Douglas (chasedouglas) => Maarten Lankhorst (mlankhorst)
** Changed in: xserver-xorg-input-synaptics (Ubuntu Precise)
Assignee: Chase Douglas (chasedouglas) => Maarten Lankhorst (mlankhorst)
--
You received th
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => Fix Committed
--
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/1009629
Title:
Xorg crashed with SIGSEGV in DeliverRawEvent()
** Description changed:
[Impact]
Crashes the X.org server for some people several times a day.
[Test Case]
1. Start Xephyr
2. killall Xephyr
Broken Behavior: Aborts with SIGSEGV and a backtrace
Fixed Behavior: Exits cleanly
[Regression Potential]
- Will regress LP #968845 so
** Description changed:
+ [Impact]
+ Crashes the X.org server for some people several times a day.
+
+ [Test Case]
+ 1. Start Xephyr
+ 2. killall Xephyr
+ Broken Behavior: Aborts with SIGSEGV and a backtrace
+ Fixed Behavior: Exits cleanly
+
+ [Regression Potential]
+ Will regress LP #968845 so
12:35 < jcristau> possibly
https://lists.debian.org/debian-x/2012/05/msg00240.html?
12:36 < jcristau> sadly no bt in that bug though
12:36 < tjaalton> in the lp one? right
12:36 < tjaalton> but does look similar
12:37 < jcristau> yeah looks the same
12:37 < jcristau> there's a revert in 1.12-branc
I had that patch as a workaround locally, but since I didn't understand
the problem well enough, I didn't want to accept it as real solution.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.lau
Not sure yet how to fix it, but can be worked around by adding
nouveau.noaccel=1 to command line.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/925048
Title:
[GTX 580] X s
What does cat /proc/interrupts return?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/952113
Title:
[ 5589.174937] [drm] nouveau :01:00.0: GPU lockup - switching to
It kind of looks like the display is detected as disconnected briefly
for whatever reason, does unplugging then replugging the monitor
restore the old settings or does it revert to mirrored setup too?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1011732
Title:
External display blinks off periodically
*** This bug is a duplicate of bug 1010794 ***
https://bugs.launchpad.net/bugs/1010794
** This bug has been marked a duplicate of bug 1010794
Graphics/text corruptions in some applications with nouveau drivers
--
You received this bug notification because you are a member of Ubuntu-X,
whi
** Package changed: xorg (Ubuntu) => fglrx-installer (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1011327
Title:
Systems Settings Brightness and Lock won't select
To manag
More information is needed, what exactly happened after upgrade?
--
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/1010075
Title:
happened after upgrade
To manage notifications about this bug go t
Public bug reported:
Please sync libdrm 2.4.33-1 (main) from Debian unstable (main)
Explanation of the Ubuntu delta and why it can be dropped:
[ Robert Hooker ]
* Merge from Debian unstable, remaining changes:
- debian/rules
- debian/control:
+ Build libdrm-intel1 everywhere rat
Hey,
There's no need to change kernel for testing, the bug was specifically
abourt X.org crashing in a specific way. I was simply asking if the
attached deb fixed that crash or not. It's a X.org driver not a kernel
driver.
Cheers,
~Maarten
--
You received this bug notification because you are a
Please test. :)
--
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/943880
Title:
Xorg crashed with SIGABRT in __libc_message() from malloc_printerr()
via XIDestroyDeviceProperty
To manage
I'll try to get all the patches in through the upstream stable kernel.
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Assignee: (unassigned) => Maarten Lankhorst (mlankhorst)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xser
Well if reverting that patch breaks things again I would assume you
could build the 3.4 kernel with it and have it working. :)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/8
The problem is there are a million possible reasons why a freeze could
occur, usually nouveau dies after an invalid instruction or memory
access occurs. There is some work being done so the system won't
completely freeze in the future, but it's not complete yet. If the
screen freezes, can you log i
This looks suspicious:
[4.607278] fb: conflicting fb hw usage nouveaufb vs EFI VGA - removing
generic driver
[4.607298] Console: switching to colour dummy device 80x25
It
The dummy device is not connected to anything, it should say say 'frame buffer
device' or something.
Can you post a
19:52 < tkamppeter> mlankhorst, I had an old xorg.conf which defined only my
old 1680x150 Samsung monitor which dies a year
ago. Natty and Oneiric happily worked with my new Eizo with
1920x1080 and this file, Precise not. After
removing the file and movin
Well there was a corruption occuring in synaptics that could trigger
every time the touchpad was disabled, for example with syndaemon. It was
fixed in a newer version, and might be what you're experiencing here.
Could you try the appropriate i386/amd64 deb from
http://people.canonical.com/~mlankho
Ok looks like it should be fixed upstream now.
Since this bug was attached to freedesktop.org I tried rebuilding
synaptics locally with the fixes and it seems to fix the corruption I
personally was seeing upstream.
Does
http://people.canonical.com/~mlankhorst/synaptics-rebuild/xserver-xorg-input-
Might be related to a upstream bug, and is probably going to be fixed in
3.4-rc5 or final by reverting nouveau's custom handling of i2c. After a
change in i2c it would no longer be needed, if nouveau's going to be
backported the i2c change probably needs to be backported too. I haven't
looked yet w
Probably fixed upstream:
http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?id=a3a285f17867f0018de798b5ee85731ec1268305
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/7138
If it's back in v3.4-rc3-precise, did it work with v3.4-rc2-precise?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/898784
Title:
Distorted screen on MacBook Air 3,2 (GT216
Would it be possible to attach a dmesg of a more recent kernel version?
It looks like not all output connectors are recognised correctly, which
explains the black screen.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau
Can you get a dmesg blindly after a freeze? From what I can tell in the
Xorg log the card froze, which likely means there's more information in
the kernel log.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
*** This bug is a duplicate of bug 925048 ***
https://bugs.launchpad.net/bugs/925048
The lockup is just confirmation it died. However it doesn't say why. Can
you post the result of running the command 'dmesg' after the lockup?
** This bug has been marked a duplicate of bug 925048
[GTX 580]
Easy workaround would be to change /lib/udev/rules.d/50-udev-
default.rules :
KERNEL=="nvidia*|nvidiactl*", GROUP="video", MODE="0660"
However that requires current user to be in the video group, and that
will probably cause a lot of issues on its own, since by default users
are not part of the
Does the problem go away if you boot with the kernel from older ubuntu?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/925048
Title:
[GTX 580] X seems to hang a login promp
This might be a real bug on its own, but why are you using the software
rasterizer?
--
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/934069
Title:
compiz crashed with SIGSEGV in _wordcopy_fwd_alig
What all these bugs have in common is that synaptics driver is used, but
the only thing I see that looks suspicious is that BOOL is redefined as
char for X, the common definition is int. However that seems to be done
consistently so not likely to be a problem, sizeof(BOOL) = 1 inside
synaptics, whi
901 - 941 of 941 matches
Mail list logo
