Verified the 1.20.0-1ubuntu0.3 via proposed channel, the new touchpad
works after installation.
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/2023623
Public bug reported:
But after I turned on the Dock's auto-hide, the size of the app icons in
the overview became significantly smaller.
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux
.-/+oooo+/-. xiaozhangup@xiaozhangup
`:+ss+:` ---
-+ssyy+- OS: Ubuntu Jammy Jellyfish (developm
.ossdMMMNyo. Kernel: 5.15.0-23-generic
libglvnd-dev only provide libGL.so, but not libapi.so!
--
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/1768755
Title:
Missing links to libGL.so and libglapi.so
To manage notifications about
Public bug reported:
The computer is not able to resume after suspend.
The screen brightness is not able to be adjusted
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
Uname: Linux 5.0.0-05-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
Whiskey Lake (WHL)
Package/pin compatible Quad core WHL (U42) or Dual core CNL (U22) design in
common board with stuffing option Two versions of CPU Si will be compatible
with this platform:
• WHL U4+2 derived based on Coffelake-U with CNL-LP PCH
Use CFL-S/H code already in
I have this problem with Nvidia GeForce 1080 Ti. Driver version 381.22.
Ubuntu 16.04, kernel version 4.10.0-33-generic.
--
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/1705884
Title:
Black
I hit the same problem, LIBGL_DRI3_DISABLE=1 workaround doesn't work for
me , but kernel 4.0.0-999-generic ( http://kernel.ubuntu.com/~kernel-
ppa/mainline/daily/current/ ) can fix my problem as makis said.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Public bug reported:
I have tried the catalyst 12.03 from AMD site but got exactly the same
error.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: fglrx 2:8.930-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux 3.2.0-23-generic-pae i686
** Description changed:
- /var/lib/dkms/fglrx/8.930/build/make.log
-
-
- DKMS make.log for fglrx-8.930 for kernel 3.2.0-23-generic-pae (i686)
- Thu Apr 19 11:03:48 CST 2012
- AMD kernel module generator version 2.1
- make.sh: line 390: [: too many arguments
- make.sh: line 396: [: too many
+1
Ubuntu 11.04
Dell Latitude E5410
2011/6/29 Elephantman 550...@bugs.launchpad.net
+1
--
You received this bug notification because you are subscribed to a
duplicate bug report (603439).
https://bugs.launchpad.net/bugs/550625
Title:
Alps touchpad is recognized but synaptics clients
This issue still exists in lucid. Jason has found one fix for it. Will
attach soon.
** Changed in: xf86-input-evtouch (Ubuntu)
Status: Expired = In Progress
** Changed in: xf86-input-evtouch (Ubuntu)
Assignee: (unassigned) = Zhang Lily (r58066)
--
You received this bug notification
Hi, previous patch is about to fix eDP issue, seems not specifically for this
X201 bug.
so we will leave it alone and plan to fix this issue with the following patch
instead: https://patchwork.kernel.org/patch/109959/
Updated Lucid kernel for test on X86 and AMD64 are uploaded to
mabawsa, there are couple updates like i915: fix ironlake edp panel setup (v2)
on https://patchwork.kernel.org/patch/108282/
Dave Airlie seems working on push his fix to upstream, which looks similar to
this bug,
so we are holding for a while and waiting for comments and feedback from
upstream.
test with X.Org X Server 1.7.6 in current Lucid
AMD64 test package uploaded to
http://people.canonical.com/~hzhang/554569/linux-
image-2.6.32-23-generic_2.6.32-23.38_amd64.deb
--
[lucid] Blank screen with KMS on Thinkpad X201 with Arrandale (i915)
https://bugs.launchpad.net/bugs/554569
You
test kernel uploaded to http://people.canonical.com/~hzhang/554569
/linux-image-2.6.32-23-generic_2.6.32-23.38_i386.deb
patched Lucid kernel with workaround from
http://bugs.freedesktop.org/attachment.cgi?id=36483
--
[lucid] Blank screen with KMS on Thinkpad X201 with Arrandale (i915)
After upgrade BIOS to 1.15 (6QET45WW), Embedded Controller Verison 1.09
my i7-M620 X201 still won't affect with this bug, but I already reproduce this
bug on another i3 X201.
Looks through http://en.wikipedia.org/wiki/Arrandale_(microprocessor) page,
i3/i5/i7 are all in Arrandale Family, so it's
Hi, I can't reproduce this bug on my X201,
Product ID: 3626AM9, Intel i7 + i915, BIOS 1.05
it's working just fine with both Lucid i386 and amd64.
I will try to trigger this bug after upgrade BIOS to latest.
and still need further investigation on more i5/i7 X201.
BTW: some people also report if
On 05/03/2010 05:32 AM, Thomas Schwinge wrote:
This bug's status is Fix Committed -- are updated packages available already?
Or shall I compile something and test it?
Updated packages are currently available in Bryce's Personal Package
Archive. You can add it to your sources.list by
Neither apport nor gdb can catch a meaningful backtrace; and apport can
detect the crash only when gdb is attached to the X process. I don't
know why. I've carefully read and followed the instructions provided in
the following X debugging howtos:
apport detected the crash when I was trying to get a full backtrace
using gdb. See bug #561433 for the crash report.
** Attachment removed: _usr_bin_Xorg.0.crash
http://launchpadlibrarian.net/43427946/_usr_bin_Xorg.0.crash
--
Lucid 2.6.32-16 crashed to login screen - miCopyRegion
According to https://wiki.ubuntu.com/CrashReporting, we should wait for
the triaging team to verify that it does not contain any sensitive
information. But I don't think it contains much sensitive information
that I care about. I am setting it public.
--
Lucid 2.6.32-16 crashed to login screen -
*** This bug is a duplicate of bug 539772 ***
https://bugs.launchpad.net/bugs/539772
** Visibility changed to: Public
--
X server crash - ATI M6 LY
https://bugs.launchpad.net/bugs/561433
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I was not able to get X to core dump, but I found one X crash report in
/var/crash. I don't even know if it was caused by the same bug.
I have installed the dbg packages as referred to in
https://wiki.ubuntu.com/X/Backtracing. What am I missing?
r...@micky:~/report# gdb /usr/bin/X CoreDump
GNU
apport cannot detect the crash, core is not dumped even though ulimit
-c unlimited is set, and gdb fails to collect a meaningful backtrace. I
failed to collect a full backtrace. Please shed some light on it.
When trying to collect a full backtrace, I found that typing in the
search bar of firefox
On 03/30/2010 05:05 PM, Bryce Harrington wrote:
Are you able to reproduce this issue easily?
Yes, every time.
If so, please collect a
full backtrace - see http://wiki.ubuntu.com/X/Backtracing for
The backtrace collected by gdb contains much less information
than what X collected.
Sorry, I mean the search bar. It seems that typing in the address bar
cannot reproduce the crash.
** Description changed:
Binary package hint: xserver-xorg
After upgrading my ThinkPad X32 to Ubuntu 10.04 beta, I often experience
- X server crash when typing in the address/search bar of
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = New
--
[lucid] X server crash
https://bugs.launchpad.net/bugs/545045
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
** Attachment added: Xorg.0.log.old after reproducing the issue
http://launchpadlibrarian.net/41830702/Xorg.0.log.old
--
[lucid] X server crash
https://bugs.launchpad.net/bugs/545045
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server
** Attachment added: Xorg.0.log after reproducing the issue
http://launchpadlibrarian.net/41830816/Xorg.0.log
--
[lucid] X server crash
https://bugs.launchpad.net/bugs/545045
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
** Attachment added: output of `lspci -vvnn`
http://launchpadlibrarian.net/41830863/lspci-vvnn.out
--
[lucid] X server crash
https://bugs.launchpad.net/bugs/545045
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
** Tags removed: needs-xorglog
--
[lucid] X server crash
https://bugs.launchpad.net/bugs/545045
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
___
Mailing list:
It seems that XAA can no longer be enabled in Lucid, and the problem is
still reproducible: Open Gnome-Terminal, run top, and then keep moving
the Gnome-Terminal window, the cpu usage of Xorg instantly climbs to 80%
or more. So the problem has not been fixed yet.
** Changed in:
Although the cpu usage of Xorg is still high, I feel that the
performance is better than in Jaunty.
--
[RV100] very poor Xorg performance on various older graphics HW - XAA no longer
works
https://bugs.launchpad.net/bugs/363238
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: xserver-xorg
After upgrading my ThinkPad X32 to Ubuntu 10.04 beta, I often experience
X server crash when typing in the address/search bar of Firefox.
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x3b) [0x80e880b]
1: /usr/bin/X (0x8048000+0x61aed)
Attaching xorg.conf. (X server crashes too when using XAA.)
** Attachment added: xorg.conf
http://launchpadlibrarian.net/41714182/xorg.conf
--
[lucid] X server crash
https://bugs.launchpad.net/bugs/545045
You received this bug notification because you are a member of Ubuntu-X,
which is
** Attachment added: :0.log.1
http://launchpadlibrarian.net/41713732/%3A0.log.1
--
[lucid] X server crash
https://bugs.launchpad.net/bugs/545045
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
Can someone reopen this please?
--
Race condition in libXext
https://bugs.launchpad.net/bugs/519576
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxext in ubuntu.
___
Mailing list:
Ping. Please reopen. I realize Lucid is almost out, but Hardy will be
supported for a while longer. Please at least backport this to Hardy.
--
Race condition in libXext
https://bugs.launchpad.net/bugs/519576
You received this bug notification because you are a member of Ubuntu-X,
which is
Umm, I know it's fixed in Lucid, which is why this bug report is asking
for the fix to be backported to Hardy - Karmic.
--
Race condition in libXext
https://bugs.launchpad.net/bugs/519576
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxext in
FYI, this patch may fix all the crashes for xcb_io.c:378: _XAllocID:
Assertion. There's many instances of this bug in the Ubuntu bug
database, i.e. bug 458989.
--
Race condition in libXext
https://bugs.launchpad.net/bugs/519576
You received this bug notification because you are a member of
Hi, the requested logs are irrelevant because I cannot reproduce the
race condition on my machine. I only know about it because the
aggregated reports from Google Chrome's crash logger show this crash
happening.
This affects any application that calls XShmAttach(). The fix is pretty
clear. Please
Public bug reported:
There's a race condition in libXext that causes apps that use the X
shared memory extensions to occasionally crash. [1][2] This has been
fixed upstream with a small patch. [3] Can we cherrypick this for all
affected releases? (Hardy to Karmic)
[1]
Public bug reported:
HW configuration: MX51 EVK board
SW configuration:
1. Install xserver-xorg-input-evtouch page (version: 0.8.8-0ubuntu6.1)
2. Add fdi file by vi /usr/share/hal/fdi/policy/20thirdparty/50-mxc-ts.fdi:
?xml version=1.0 encoding=ISO-8859-1?
deviceinfo version=0.2
device
Yes, the sarvatt version cannot work, but gomyhr (patched) version
can detect my TV and can set resolution to 1360x768 @ 60Hz.
xrandr report:
Screen 0: minimum 320 x 200, current 1360 x 768, maximum 1360 x 1360
VGA disconnected (normal left inverted right x axis y axis)
HDMI-1 connected
Thanks Geir Ove Myhr.
I will try your package later.
--
[G41] Jaunty: HDMI connected but no valid modes
https://bugs.launchpad.net/bugs/384660
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xf86-video-intel.
** Attachment removed: xorg.conf with debug enabled
http://launchpadlibrarian.net/27644732/Xorg.0.log
** Attachment added: xorg.conf with debug enabled
http://launchpadlibrarian.net/27716654/xorg.conf
--
[G41] Jaunty: HDMI connected but no valid modes
Report bugs to upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=22189
** Bug watch added: freedesktop.org Bugzilla #22189
https://bugs.freedesktop.org/show_bug.cgi?id=22189
--
[G41] Jaunty: HDMI connected but no valid modes
https://bugs.launchpad.net/bugs/384660
You received this bug
I have tried: xserver-xorg-video-intel_2.7.1-0ubuntu1~xup~1_i386.deb from
https://launchpad.net/~ubuntu-x-swat/+archive/x-updates/.
But it is still failed to find my monitor.
** Attachment added: xorg.conf with debug enabled
http://launchpadlibrarian.net/27644732/Xorg.0.log
--
[G41]
** Attachment added: X log with 2.7.1-0ubuntu1~xup~1_i386.deb
http://launchpadlibrarian.net/27644750/Xorg.0.log
--
[G41] Jaunty: HDMI connected but no valid modes
https://bugs.launchpad.net/bugs/384660
You received this bug notification because you are a member of Ubuntu-X,
which is
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/27632096/Xorg.0.log
--
Ubuntu 9.04: G41 with HDMI connected but no valid modes
https://bugs.launchpad.net/bugs/384660
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: lspci.txt
http://launchpadlibrarian.net/27632102/lspci.txt
--
Ubuntu 9.04: G41 with HDMI connected but no valid modes
https://bugs.launchpad.net/bugs/384660
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: lsmod.txt
http://launchpadlibrarian.net/27632105/lsmod.txt
--
Ubuntu 9.04: G41 with HDMI connected but no valid modes
https://bugs.launchpad.net/bugs/384660
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: lshw.txt
http://launchpadlibrarian.net/27632111/lshw.txt
--
Ubuntu 9.04: G41 with HDMI connected but no valid modes
https://bugs.launchpad.net/bugs/384660
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: lshal.txt
http://launchpadlibrarian.net/27632120/lshal.txt
--
Ubuntu 9.04: G41 with HDMI connected but no valid modes
https://bugs.launchpad.net/bugs/384660
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Rolf Leggewie, I just tried your suggestion by adding the following to
xorg.conf:
Section Module
Load glx
Load dri
EndSection
Section DRI
Mode 0666
EndSection
It doesn't help. Xorg log (see attachment) shows that glx and dri are
enabled by default:
(II) glx will
56 matches
Mail list logo
