** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1574341/+attachment/5538304/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xinput in Ubuntu.
https://bugs.launchpad.net/bugs/1574341
Although most other issues are solved there is still no multitouch for
this device with kernel v5.15 and xserver-xorg 1.20.13-1ubuntu1 using
Kubuntu 21.10.
# xinput
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4
Had my techie test the SRU for 20.04 on the affected E495 and can
confirm this works.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
https://bugs.launchpad.net/bugs/1873895
Title:
Regression: block staircase display with
I've worked with upstream AMD and we've fixed the problem in in xf86
-video-amdgpu. As soon as that is available in the upstream repository
I'll prepare a cherry-pick update to 20.04.
I suspect we also need to consider an SRU patch to 18.04 ?
--
You received this bug notification because you
** Also affects: linux via
https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/10
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
Urgh, should have written "With the help and suggestions of 'brainwash'
and 'bluesabre' on #xubuntu-devel..."
** Summary changed:
- Regression: block staircase display with side-by-side monitors
+ Regression: block staircase display with side-by-side monitors of different
pixel widths
**
With the help and suggestions of Bluesabre on #xubuntu-devel we've
tracked it down to a recent change in xfwm4 where it switched from using
glx to xpresent:
https://git.xfce.org/xfce/xfwm4/commit/?id=23900123ad8418149897a094d1096d6ecb984d3c
which seems to be a bug in the driver as mentioned
** Also affects: xfwm4 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
https://bugs.launchpad.net/bugs/1873895
Title:
Regression: block staircase display with side-by-side
Reproducing this:
$ xrandr -d :0.0 --output HDMI-A-0 --left-of eDP
$ xrandr -d :0.0 --output HDMI-A-0 --right-of eDP
No problem with:
$ xrandr -d :0.0 --output HDMI-A-0 --above eDP
$ xrandr -d :0.0 --output HDMI-A-0 --below eDP
The affected and unaffected laptops each have identical kernel log
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357362/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357353/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
https://bugs.launchpad.net/bugs/1873895
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357363/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
https://bugs.launchpad.net/bugs/1873895
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357354/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
https://bugs.launchpad.net/bugs/1873895
Timo: yes, sorry, I think I got a bit confused about packages due to
lack of sleep. I've reported this against xserver-xorg-video-amdgpu for
now although looking at the apt history it wasn't updated.
I'm not too familiar with the Xorg internals so any pointers on
potential culprits would be
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357364/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
https://bugs.launchpad.net/bugs/1873895
Tim
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
https://bugs.launchpad.net/bugs/1873895
Title:
Regression: block staircase display with side-by-side monitors
To manage notifications about this bug go to:
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357361/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
https://bugs.launchpad.net/bugs/1873895
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357359/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357358/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357355/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357356/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357360/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
https://bugs.launchpad.net/bugs/1873895
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357357/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357351/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
https://bugs.launchpad.net/bugs/1873895
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357352/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
https://bugs.launchpad.net/bugs/1873895
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357350/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
https://bugs.launchpad.net/bugs/1873895
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357347/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
https://bugs.launchpad.net/bugs/1873895
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357349/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357346/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357348/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
apport information
** Also affects: xserver-xorg-video-amdgpu (Ubuntu)
Importance: Undecided
Status: New
** Tags added: apport-collected focal ubuntu
** Description changed:
Two identical Lenovo E495 laptops with 20.04 installed. The problem
occurred initially on the laptop that
These are the packages I've tested via a downgrade:
$ apt list --upgradeable
Listing... Done
libxcomposite1/focal 1:0.4.5-1 amd64 [upgradable from: 1:0.4.5-0ubuntu1]
libxcomposite1/focal 1:0.4.5-1 i386 [upgradable from: 1:0.4.5-0ubuntu1]
libxdamage1/focal 1:1.1.5-2 amd64 [upgradable from:
I'm attaching the complete list of packages upgraded on the second
laptop that triggered this bug.
The total list is over 300 packages. I've prefixed the unlikely package
with #. That leaves 77 possibles all related to X server or display
drivers.
** Attachment added: "List of upgraded packages
The packages upgraded on the second laptop that are libx related are:
$ grep 'Upgrade: hunspell' /var/log/apt/history.log | grep -o 'libx[^ ]*'
libxml2-utils:amd64
libxml2:amd64
libxatracker2:amd64
libxcomposite1:amd64
libxcomposite1:i386
libxml2-dev:amd64
libxfixes3:amd64
libxfixes3:i386
Public bug reported:
Two identical Lenovo E495 laptops with 20.04 installed. The problem
occurred initially on the laptop that is having package upgrades applied
regularly.
With dual monitors and the external monitor placed left or right the
display has a blocked staircase effect shown in the
Had a user in IRC #ubuntu today re-rporting this for 18.04 when trying
to use Onboard. The user was asked to create a new bug report for their
issue but may not do so.
Adding this link which may be useful for other users caught by this:
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1655752
Title:
Xorg crashed with SIGABRT in
@Robie: "It looks like your backport also pulled in upstream commit
116cddba69b37246db564c1ddf772c0144c589f0. Was this intentional?"
No, from what I can see the backported commit
72bac84df9ce72f2baf730655ecc23f1692d1e64 removes and re-applies that
specific change too.
@Timo: My local package
** Changed in: xserver-xorg-input-libinput (Ubuntu)
Assignee: TJ (tj) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1655752
Title:
Xorg cras
)
Status: New => In Progress
** Changed in: xserver-xorg-input-libinput (Ubuntu)
Assignee: (unassigned) => TJ (tj)
** Patch added: "Debdiff containing backported upstream fix"
https://bugs.launchpad.net/xorg-server/+bug/1655752/+attachment/4805807/+files/xs
** No longer affects: xorg-server
** Bug watch added: freedesktop.org Bugzilla #97117
https://bugs.freedesktop.org/show_bug.cgi?id=97117
** Also affects: xorg-server via
https://bugs.freedesktop.org/show_bug.cgi?id=97117
Importance: Unknown
Status: Unknown
--
You received this
** Bug watch added: freedesktop.org Bugzilla #99390
https://bugs.freedesktop.org/show_bug.cgi?id=99390
** Also affects: xorg-server via
https://bugs.freedesktop.org/show_bug.cgi?id=99390
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
The log file shows the input device(s) being removed upon system idle
and the attempt to re-attach it failing.
** Attachment added: "Xorg log"
https://bugs.launchpad.net/debian/+source/xorg-server/+bug/1655752/+attachment/4803510/+files/Xorg.0.log.old
--
You received this bug notification
The NULL device bubbles up from
xserver-xorg-input-
libinput-0.18.0/src/xf86libinput.c::xf86libinput_pre_init()
where it does
is_subdevice = xf86libinput_is_subdevice(pInfo);
if (!is_subdevice) {
...
} else {
InputInfoPtr parent;
struct xf86libinput
Public bug reported:
Using Xubuntu 16.04, including light-locker, whenever the screen has
been locked the X server will SIGABRT crash as soon as the user has
entered their credentials. This happens 100% of the time.
The only related information I can find is a Debian bug report:
** Bug watch added: freedesktop.org Bugzilla #98770
https://bugs.freedesktop.org/show_bug.cgi?id=98770
** Also affects: xinput-calibrator via
https://bugs.freedesktop.org/show_bug.cgi?id=98770
Importance: Unknown
Status: Unknown
** Project changed: xinput-calibrator => libinput
** Bug watch added: Linux Kernel Bug Tracker #117601
http://bugzilla.kernel.org/show_bug.cgi?id=117601
** Also affects: xinput-calibrator via
http://bugzilla.kernel.org/show_bug.cgi?id=117601
Importance: Unknown
Status: Unknown
** No longer affects: xinput-calibrator
** Also
** Summary changed:
- Asus T300 CHI bluetooth Touchpad is recognized incorrectly
+ [ELAN 3320KD-3100] Asus T300 CHI bluetooth Touchpad is recognized incorrectly
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xinput in Ubuntu.
I opened up the keyboard dock today to identify the touchpad chip. It is
an ELAN 3320KD-3100 in a 64 pin QFN package. It links over Bluetooth
using the Broadcom BCM20730 A1KFBG.
The device presents over Bluetooth with an ASUS ID: 0B05:8502.
ELAN call the touchpad the "Smart Pad":
** Bug watch added: Linux Kernel Bug Tracker #117451
http://bugzilla.kernel.org/show_bug.cgi?id=117451
** Also affects: xinput-calibrator via
http://bugzilla.kernel.org/show_bug.cgi?id=117451
Importance: Unknown
Status: Unknown
** Project changed: xinput-calibrator => linux
**
** Description changed:
This is a related but separate issue to bug #1480673 "Asus T300 CHI
bluetooth Touchpad is recognized incorrectly".
- Affecting this digitizer is also bug #1574028 "Asus T300 CHI: Synaptics
- Touch Digitizer - missing at boot".
+ Affecting this digitizer is also bug
** Changed in: xinput (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xinput in Ubuntu.
https://bugs.launchpad.net/bugs/1480673
Title:
Asus T300 CHI bluetooth Touchpad is recognized incorrectly
To
** Summary changed:
- 16,04: Asus T300 CHI: touchscreen digitiser missing at boot
+ Asus T300 CHI: Synaptics Touch Digitizer - missing at boot
** Changed in: xinput (Ubuntu)
Status: New => Triaged
** Changed in: xinput (Ubuntu)
Importance: Undecided => Medium
--
You received this
** Description changed:
This is a related but separate issue to bug #1480673 "Asus T300 CHI
bluetooth Touchpad is recognized incorrectly".
- Affecting this digitizer is also bug #1574028 "Asus T300 CHI:
- touchscreen digitiser missing at boot".
+ Affecting this digitizer is also bug
** Description changed:
This is a related but separate issue to bug #1480673 "Asus T300 CHI
bluetooth Touchpad is recognized incorrectly".
+
+ Affecting this digitizer is also bug #1574028 "Asus T300 CHI:
+ touchscreen digitiser missing at boot".
Using 16.04 amd64 Ubuntu (unity).
** Description changed:
+ Moved the touchscreen issues to bug #1574341 "[Asus T300 CHI] Synaptics
+ Touch Digitizer V04 - no multitouch".
+
The Asus T300 CHI has a touchscreen and a (bluetooth) keyboard/touchpad combo.
Both (touchscreen, touchpad) only work like a mouse (moving pointer, left
Public bug reported:
This is a related but separate issue to bug #1480673 "Asus T300 CHI
bluetooth Touchpad is recognized incorrectly".
Affecting this digitizer is also bug #1574028 "Asus T300 CHI:
touchscreen digitiser missing at boot".
Using 16.04 amd64 Ubuntu (unity).
In this case the
** Summary changed:
- 16,04: Asus T300 CHI: touchscreen missing at boot
+ 16,04: Asus T300 CHI: touchscreen digitiser missing at boot
** Attachment added: "lsusb after cold boot"
** Attachment added: "ACPI DSDT decompiled"
https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1574028/+attachment/4644326/+files/dsdt.dsl
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xinput in Ubuntu.
Public bug reported:
Using 16.04 amd64 on an Asus T300 CHI 2-in-1 transformer-book (tablet +
docking Bluetooth keyboard/trackpad).
At boot-time the USB-connected Synaptics touchscreen digitiser is not
recognised but after an S3 sleep/resume it is. Smells like an ACPI issue
but so far testing
** Attachment added: "lsusb after S3 resume showing device"
https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1574028/+attachment/4644316/+files/lsusb.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xinput in Ubuntu.
1 root root 4096 Apr 23 12:59 unbind
tj@T300CHI:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 06cb:11ef Synaptics, Inc.
Bus 001 Device 005: ID 04f2:b3d5 Chicony Electronics Co., Ltd
Bus 001 Device 003: ID 8087:0a2a Intel Corp.
Bus 001 Devi
My loss of the touchscreen seems to be due to my doing a lot of
experimenting with evtest and udev's hwdb. After an S3 resume this
morning the touchscreen Synaptic devices re-appeared. Thinking about it,
it may also be due to some ACPI DSDT experimentation I was doing to try
to get the Fn+F5-F7
Confirmed here too... although with 16.04 / Unity there was touchscreen
input during live session but after booting the installed system I just
realised there is no touchscreen input device.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xinput
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Assignee: Jakob Povsic (jakob-povsic) => (unassigned)
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: Fix Released => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Public bug reported:
fglrx-installer-updates (2:15.201-0ubuntu2~15.10.2) wily-proposed does
not fix crash on startup on the 4.3 stable kernel. Installed from ubuntu
mainline ppa.
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: fglrx-updates-core 2:15.201-0ubuntu2~15.10.2
Uname: Linux
The report in /var/log/Xorg.0.log:
"_XSERVTransMakeAllCOTSServerListeners: server already running"
suggests the system (user: gdm, uid: 116) display manager X server on
VT7 owns/uses the socket in "/tmp/.X11-unix/" which prevents the user
(uid:1000) display manager on VT2 from using the same
** Tags added: apport-request-retrace
--
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/1237904
Title:
Xorg crashed with SIGABRT in OsAbort()
To manage notifications about this bug go to:
** Changed in: xorg-server (Ubuntu)
Status: Expired => Triaged
** Changed in: xorg-server (Ubuntu)
Importance: Low => Medium
** Also affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
** Description changed:
- The mouse cursor is gone when Oneiric starts. The mouse itself is
+ The mouse cursor is gone when the GUI starts. The mouse itself is
responding, but the pointer is invisible. Very annoying. I do have a
workaround. One must simply restart the lightdm interface with
** Information type changed from Private to Public
** Changed in: xorg-server (Ubuntu)
Status: Invalid = Incomplete
--
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/1479009
Title:
Public bug reported:
The explicit copyright text in each source file is Proprietary all
rights reserved, not open source.
The package copyright file /usr/share/doc/nvidia-340/copyright is less
than ideal and only purports to repeat extracts from an email exchange,
it is not a copyright license.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New = Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Changed in: linux (Ubuntu)
Milestone: None = ubuntu-14.04.3
--
You received this bug
Public bug reported:
Happened while I was updating via software updater.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: fglrx 2:14.501-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9
Uname: Linux 3.16.0-37-generic x86_64
NonfreeKernelModules: fglrx
Unfortunately this driver has suffered bit-rot upstream since the chip-
set is ancient and not widely used, and support for it in the 12.04 and
14.04 releases is poor to non-existant.
Marking as Won't Fix since we haven't found the expertise to fix it in
7 years.
** Changed in: xorg (Ubuntu)
-xfree86-nonfree, xfs
** Affects: flashplugin-nonfree (Ubuntu)
Importance: Undecided
Assignee: TJ (tj)
Status: Triaged
** Affects: wdm (Ubuntu)
Importance: Undecided
Assignee: TJ (tj)
Status: Triaged
** Affects: xfonts-terminus (Ubuntu)
Importance: Undecided
** Also affects: nvidia-graphics-drivers-340 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1247736
Title:
** Changed in: nvclock (Ubuntu)
Assignee: TJ (tj) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1039916
Title:
Nvidia driver causing SIGSEGV
Christopher, please leave the bug status as it is now. I was the
original reporter *and* member of the Ubuntu Kernel team and I created
this bug specifically to track the issue against the mainline kernel.
There is no work to be done nor data collection required against Ubuntu,
as I have
No point. All work - if any - will be upstream not in Ubuntu and the
information required is already available in the initial comment I
created for this bug report.
** Tags removed: needs-kernel-logs
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
I did some work upstream but it became too complicated. Others have also
tried but nothing has changed. In the meantime the hardware out there
that has a 32-bit limit imposed by its southbridge on 64-bit CPUs is all
now old legacy gear so I don't foresee the kernel fixing this, ever.
It still
A ray of hope for the alternative. After fixing a bug in the nvidiabl
kernel module[1] I can use the standard OS brightness controls to
control the backlight. More work needs to be done on that, and it needs
to be brought into Ubuntu, but it is the proper solution and it does
work for many
The blacklisted entry was introduced by the latest security patch to the
nvidia drivers.
nvidia-graphics-drivers-updates (295.49-0ubuntu0.2) precise-security;
urgency=low
* SECURITY UPDATE: privilege escalation via kernel memory access
-
:292
alignOff = 0
#2 0x00401f43 in unmap_mem () at backend.c:150
No locals.
#3 0x004022dd in unset_card () at backend.c:252
No locals.
#4 0x0040dd83 in create_config (file=0x61f030
/home/tj/.nvclock/config) at config.c:611
section = hw0
bios
Discussion with Adam Conrad on IRC #ubuntu-devel:
TJ- A recent change to the nvidia DKMS drivers package has broken another
package such that it won't conceivably ever work again. What's the procedure in
such cases?
infinity TJ-: That might need to be slightly less vague.
TJ- infinity: bug
The SIGSEGV is being tracked in bug #1039916 Nvidia driver causing
SIGSEGV in nvclock and smartdimmer.
That bug affects the Fix released status of this bug since this work-
around no longer functions. I've nominated this bug for Precise and
Quantal, but any fix of the SIGSEGV issue will be done
I've got two Samsung P2450 monitors and am seeing something similar.
Monitor A was deployed as as the external monitor connected to the
Ubuntu laptop docking station using DVI-D. Laptop has Nvidia GeForce Go
7600.
Monitor B was the secondary monitor on a Windows XP Gaming PC with
Nvidia 9800GT
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed = New
--
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
The original report was on a desktop with an ATI Radeon video adapter
running Lucid. I gave up on that system.
Now, on a Precise amd64 installation on my primary laptop that has an
Nvidia GEForce Go 7600 and the nvidia drivers I've hit the same issue
several times today (23 April 2012) after
** Attachment added: Xorg log containing stack backtraces
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/567696/+attachment/3100849/+files/Xorg.0.log.old
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a
** Changed in: xorg-server (Ubuntu)
Assignee: TJ (intuitivenipple) = (unassigned)
** Changed in: linux (Ubuntu)
Assignee: TJ (intuitivenipple) = (unassigned)
** Changed in: xorg-server (Ubuntu)
Status: In Progress = Confirmed
** Changed in: linux (Ubuntu)
Status
** Changed in: nvidia-graphics-drivers-173 (Ubuntu)
Assignee: TJ (intuitivenipple) = (unassigned)
** Changed in: nvidia-graphics-drivers-96 (Ubuntu)
Assignee: TJ (intuitivenipple) = (unassigned)
** Changed in: nvidia-graphics-drivers (Ubuntu)
Assignee: TJ (intuitivenipple
** Changed in: nvidia-graphics-drivers-173 (Ubuntu)
Assignee: (unassigned) = TJ (intuitivenipple)
** Changed in: nvidia-graphics-drivers-96 (Ubuntu)
Assignee: (unassigned) = TJ (intuitivenipple)
** Changed in: nvidia-graphics-drivers (Ubuntu)
Assignee: (unassigned) = TJ
This is caused by a failure to detect the kernel version by the
'conftest.sh' script, which attempts to compile an incomplete kernel
module.
There are a variety of issues causing the failure. I've current
addressed the one that affects builds for 2.6.39 and later (compiler
should use
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New = Confirmed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = TJ (intuitivenipple)
--
You received this bug notification because you are a member of Ubuntu-X
After considering that many different video graphics drivers exhibit
this fault, I decided to focus on the kernel's DRM (Direct Rendering
Manager) code since it is common to all reports.
There has been a lot of change in the DRM code since the Lucid kernel
was released with Linux v2.6.32. As a
** Changed in: linux (Ubuntu)
Status: Confirmed = In Progress
--
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/567696
Title:
[mi] EQ overflowing. The server is probably stuck in an
I've managed to trigger the fault using kernel v2.6.38 from Natty whilst
running the Software Sources update after enabling additional
repositories.
I noticed in previous debugging sessions that the DRM_DEBUG messages
emitted when enabled in the kernel with
echo 1 | sudo tee
** Summary changed:
- [Radeon] [Lucid] [mi] EQ overflowing. The server is probably stuck in an
infinite loop
+ [mi] EQ overflowing. The server is probably stuck in an infinite loop
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
** Description changed:
- Whilst running an update-manager session for Lucid 10.04 i386 the
- update-manager appeared to 'freeze' midway. The rest of the Gnome
- interface was similarly unresponsive and the mouse cursor displays the
- animated 'busy' circle (but it wasn't being animated).
+
1 - 100 of 164 matches
Mail list logo
