@Dmitry, "continue crashing" - do you have Xorg from oneiric-proposed
installed? Post your /var/log/Xorg.0.log.old from after a crash.
--
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/930936
Hello,
Can someone clarify where we stand in regard with this issue and Ubuntu Quantal
12.10?
I've been following Qt doc to the letter and got QPinchGesture working in a
QWidget... but as soon as the "grabGesture" is issued on that widget all other
widgets (tabs, pushbuttons, lineedits, etc.) st
The only infra red device on this laptop is the receiver for the remote
control. I don't think that should be affecting this.
Next time it happens (probably later tonight), I'll attach a wired
mouse, but I think the issues will remain.
After that, I'll try blacklisting the wacom driver and seeing
Still having trouble yet...
Indeed I have two Graphics Cards, but they were fine with Oneiric and
Precise, that's why this bug is so strange for me... X never did it with
me, I already have used Arch Linux, Debian, Ubuntu and this was my first
problem with X.
I've tried to reinstall xorg, radeon/
** Attachment added: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1051075/+attachment/3315421/+files/ThreadStacktrace.txt
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/bugs/1051075/+attachment/3315389/+files/CoreDump.gz
** Changed in: xorg-server (Ubuntu)
Im
** Attachment added: "StacktraceSource.txt"
https://bugs.launchpad.net/bugs/1051075/+attachment/3315420/+files/StacktraceSource.txt
--
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/1051075
** Attachment added: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1051075/+attachment/3315419/+files/Stacktrace.txt
--
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/1051075
Title:
X
StacktraceTop:
_XSERVTransClose (ciptr=0xb9026b00) at /usr/include/X11/Xtrans/Xtrans.c:902
CloseWellKnownConnections () at ../../os/connection.c:515
AbortServer () at ../../os/log.c:649
FatalError (f=f@entry=0xb76dc678 "%s: VT_ACTIVATE failed: %s\n") at
../../os/log.c:793
switch_to (vt=7, fro
** Visibility changed to: Public
--
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/1051075
Title:
Xorg crashed with SIGABRT in _XSERVTransClose()
To manage notifications about this bug go t
** Package changed: xorg (Ubuntu) => xf86-video-omap (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-video-omap in Ubuntu.
https://bugs.launchpad.net/bugs/1037306
Title:
after todays update there is no desktop on omap4+armhf on p
Not enough information has been provided to make this a useful bug
report. See http://wiki.ubuntu.com/X/Reporting for instructions on
reporting X issues.
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which
All the logs attached to this bug are useless, they just show VESA
loaded because you disabled modesetting on intel. You need to look at
the log files from the broken system.
Roosje, no your problem is something completely different.
** Changed in: xorg (Ubuntu)
Status: Confirmed => Inval
Also, when you reproduce this bug can you check that it corresponds with
the segfault? E.g. `tail -f /var/log/Xorg.0.log` in a window, then
reproduce and see if the stacktrace prints at exactly that moment. I'm
assuming it does, but if not you may be looking at two separate bugs
(lucky you).
**
Please collect a full backtrace on this crash - see
http://wiki.ubuntu.com/X/Backtracing for guidance.
** Package changed: xorg (Ubuntu) => xserver-xorg-video-ati (Ubuntu)
** Changed in: xserver-xorg-video-ati (Ubuntu)
Importance: Undecided => High
** Changed in: xserver-xorg-video-ati (Ubunt
** Package changed: xorg (Ubuntu) => qt4-x11 (Ubuntu)
--
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/1047664
Title:
xorg swaps some gigabytes and so system is not very responsive
To manage noti
** Package changed: xorg (Ubuntu) => virtualbox-ose (Ubuntu)
--
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/1044746
Title:
Response very slow, windows dim out when cliked on close.
To manage no
That's actually prior to when X actually gets started up.
** Package changed: xorg (Ubuntu) => plymouth (Ubuntu)
--
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/1046957
Title:
"error during file
According to the Xorg.0.log, the touchpad has the synaptics driver
loaded, whereas the touchscreen and pen are using the wacom driver.
There is also a "MCE IR Keyboard/Mouse" which loads the evdev driver; I
assume that's for your keyboard, no IR mouse?
If I understand your report, you're seeing th
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1049088
Title:
Unity crashes at login with nouveau driver
To m
Still having trouble? Your bug description is rather terse so hard to
understand. I see you have two video cards, and X is not able to
associate a video driver with either of them. It might help if you
could explain your situation in more detail, what's worked in the past
and what all you've tes
Not enough information has been provided to make this a useful bug
report. See http://wiki.ubuntu.com/X/Reporting for instructions on
reporting X issues.
In particular for issues such as described in the title, no useful
information is printed to logs, so you need to provide a detailed case
for h
Bug in the nouveau drm I'm guessing. Might try booting
newer/older/mainline kernels.
** Package changed: xorg (Ubuntu) => xserver-xorg-video-nouveau (Ubuntu)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a memb
Stefan, are you still seeing this issue? If so I'd recommend working
through some of the troubleshooting steps at
https://wiki.ubuntu.com/Hotkeys to help narrow down where the fault is.
** Changed in: xorg (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification be
Suspend/resume is handled by the kernel, so am bumping this over to them for
troubleshooting.
However this looks to me like perhaps something screwy with the nouveau drm
module not reinitializing the GPU.
The kernel team can guide you through testing some alternate kernels and bisect
down to the
Unlikely to be X doing this, but feel free to reopen if evidence comes to light
indicating X is doing something wrong.
I'd suggest also trying multiple times and see if the fault is reproducible or
not.
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug notific
This is well before X comes into play. X only kicks in after plymouth
is done.
Might be a plymouth bug but maybe more likely to be something with the
kernel framebuffer initialization. Probably best to start analysis from
the kernel and work your way up to find the cause.
** Package changed: xo
Same problem with the following card and twinview. Nothing rotated.
01:00.0 VGA compatible controller: NVIDIA Corporation G84 [Quadro FX
570] (rev a1)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bug
--
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/1051035
Title:
MacBookAir3,1 has screen corruption on boot between Grub and Login (no
Pylmouth Ubuntu logo)
To manage notifications about this bu
Public bug reported:
During a reboot or fresh cold boot my MacBookAir3,1 doesn't give a
Plymouth Ubuntu logo screen. It's just garbled corruption from unflushed
video memory. Sometimes the last image on screen before reboot is
visible after reboot (albeit backwards, blocked, and pixelated).
* ht
** Also affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
--
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/1051027
Title:
MacBookAir3,1 loses desktop background im
Public bug reported:
After a suspend/resume my desktop background image changes from my
custom image back to black. When I go back into gnome-control-center
(Gear -> System Settings... -> Appearance -> Look) the background image
is still set there and I have to toggle something (change from Fill t
--
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/1051020
Title:
MacBookAir3,1 has pulsing pixelated vertical line down right side of
screen after suspend/resume
To manage notifications about thi
Public bug reported:
After suspend/resume my MacBookAir3,1 has pulsing pixelated vertical
line down right side of screen:
* http://www.youtube.com/watch?v=_ymoZ9uIQ4E
Logs and additional info should be attached below with ubuntu-bug.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg 1
*** This bug is a duplicate of bug 1037518 ***
https://bugs.launchpad.net/bugs/1037518
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1037518, so is being marked as such.
** Description changed:
1) lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04
lsb_release -rd
Description: Ubuntu oneiric (development branch)
Release: 11.10
2)
uname -a
Linux monikerpc 3.4.0-030400rc1-generic #201203312035 SMP Sun Apr
** Summary changed:
- [Quantal] [Intel Atom] Mesa 2012/09/07 updates broke it all
+ [Mesa revert because of it, not impacting quantal right now] [Quantal] [Intel
Atom] Mesa 2012/09/07 updates broke it all
** Summary changed:
- [Mesa revert because of it, not impacting quantal right now] [Quanta
*** This bug is a duplicate of bug 1037518 ***
https://bugs.launchpad.net/bugs/1037518
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1037518, so is being marked as such.
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-v3.6-rc5-quantal
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/869047
Title:
PgUp does not work Acer As
** Also affects: nvidia-settings (Ubuntu Quantal)
Importance: Medium
Assignee: Alberto Milone (albertomilone)
Status: Fix Released
** Also affects: nvidia-graphics-drivers (Ubuntu Quantal)
Importance: Medium
Assignee: Alberto Milone (albertomilone)
Status: Fix Release
This is the bug for ubiquity
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1040544
--
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/1046951
Title:
No desktop environmen
In addition, run sudo update-grub
--
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/750437
Title:
fglrx hard lockup on shutdown
To manage notifications about this bug go to:
https:
"Disabling kernel mode setting is important, as the driver doesn't
appear to take advantage of KMS yet. If you do not deactivate KMS, your
system might freeze when trying to switch to a tty or even when shutting
down via your DE. "
Source: Arch Wiki
For Grub2, edit /etc/default/grub and add nomod
And still - nothing. Hey guys, there are _lots_ of users out there with
good old CRT monitors that are left in rain!
Please - We do not ask to mess up the user interface with lots of
entries. But is too much to ask for an "experts" button, behind which
you could just simply _set_ resolution, refre
Launchpad has imported 1 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=54914.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
--
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/1050850
Title:
fail gpu driver
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1050850/+subscript
Public bug reported:
po up message of internal sistem fail. fail gpu driver
Hardware: Intel Sandy Bridge 2500k
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3
Uname: Linux 3.5.0-13-generic i686
ApportVersion: 2.0.1
I'm not sure why ubiquity can't cope with 8 bit colours.possibly
something that might be worth looking into?
--
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/1046951
Title:
N
The radeon driver no longer supports UMS. Because of the current
PowerPC kernel config (radeonfb is built in) KMS drm cannot be
activated. You are falling back to the fbdev driver in 8 bit mode (hence
the poor colors).
One way to activate KMS is using the video=ofonly parameter (this
disables rad
** Changed in: mesa
Status: Confirmed => Fix Released
--
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/496653
Title:
[KMS][RV530] compiz very slow on Radeon AGP video card
Launchpad has imported 1 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=54840.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
Yep, this is an issue with the kernel modeset code in the drm/i915.ko
driver. But this bug is in the right bugzilla, we also handle the kernel
issues for the intel driver here.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-in
Daniel, does having these messages from drm indicate this is likely a
kernel issue rather than an Xorg issue, at this point?
--
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/10219
(In reply to comment #15)
> (In reply to comment #14)
>
> > The further commits to drt may have regressed this again - I can't be sure
> > as I
> > can't run todays head, but while bisecting for -
> >
> > https://bugs.freedesktop.org/show_bug.cgi?id=27536
> >
> > I noticed on the "goods" close
Unfortunately, this patch changed nothing here.
I'm still enable to start unity/gnome-shell and I have some graphic corruptions
when using a fallback such as Unity 2D.
This is on a Acer Emachine e625 laptop. I tested the patch on both 32
and 32-pae kernels from Ubuntu 12.04 (3.2.0-31.50).
--
Yo
I got one more laptop with ivy bridge and same issue: Zunebook ux31a. CPU
i5-3317U.
intel_stepping
Vendor: 0x8086, Device: 0x0166, Revision: 0x09 (??)
render clock: unknown sampler clock: unknown
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
This appears in dmesg:
[ 21.891791] i915 :00:02.0: setting latency timer to 64
[ 21.892354] i915 :00:02.0: irq 50 for MSI/MSI-X
[ 21.892364] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 21.892365] [drm] Driver supports precise vblank timestamp query.
[ 21.892690]
Sorry I haven't had more time to try and debug this. Just posted on G+
asking for anyone with the same CPU/Motherboard and multiple displays to
help out if possible.
That said, I tried switching crtc on the outputs just now, and I can get
the main screen to switch between the two, but the secondar
** Bug watch added: freedesktop.org Bugzilla #54914
https://bugs.freedesktop.org/show_bug.cgi?id=54914
** Also affects: mesa via
https://bugs.freedesktop.org/show_bug.cgi?id=54914
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member o
When you're patching away this bug, will button touches then get ignored
completely?
This wouldn't be helpful because under Windows you have got two
different options concerning the left pad : To touch the button and
execute a touch action or to press the button without executing the
touch event.
** Also affects: fglrx-installer (Ubuntu)
Importance: Undecided
Status: New
--
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/933846
Title:
java crashed with SIGABRT in XQueryE
Can you check if the following testcase can trigger the bug:
wget
https://jogamp.org/git/?p=jogl.git\;a=blob_plain\;f=src/test-native/displayMultiple02.c
-O displayMultiple02.c
gcc -o displayMultiple02 displayMultiple02.c -lX11 -lGL
./displayMultiple02
I belive this bug is similar to:
https://b
I just came across this report, and while I'm not having problems with
black screens or failed shut-downs so much, I have a similar set-up to
the original reporter: Nvidia 8400M GT, Core 2 Duo, and I've been having
problems with the GPU failing to activate (see Bug #1009312). It seems
to be happeni
I also have this bug on my gigabyte t1005 cando touchscreen. A
workaround for me is replacing unity with avant-window-navigator.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/9
Fix committed into lp:compiz at revision 3370
--
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/1037411
Title:
[regression][DRI] SubBuffer rendering is much slower in compiz 0.9.8.0
than it was i
64 matches
Mail list logo
