permission to push Geode to XSF Git on Salsa?
Greetings, Over these past few days, I'm been converting my Debian packages from static to Salsa Git. Next is xf86-video-geode. What I'd like to do is push it to the following Git repo: https://salsa.debian.org/xorg-team/driver/xserver-xorg-video-geode I'd like to so something similar to what I did for src:cups-pdf, which is to set the team as the Maintainer and myself as the Uploader. This has worked well for CUPS-PDF, since I still take care of maintenance, but the Debian Printing Team is also able to contribute patches or advise me whenever an issue is due to e.g. API changes in CUPS itself. Both CUPS-PDF and xf86-video-geode also happen to be really low-maintenance packages. Would this be possible? Thanks! Martin-Éric
Bug#1025389:
Removing the Intel config in /etc/X11/xorg.conf.d/*.conf made my laptop boot again.
Bug#1025389: Info received ()
On Wed, 7 Dec 2022 at 13:33, Debian Bug Tracking System wrote: > > Thank you for the additional information you have supplied regarding > this Bug report. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Debian X Strike Force > > If you wish to submit further information on this problem, please > send it to 1025...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 1025389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025389 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems
Bug#1025389:
I am also affected by this bug on a 2020 Lenovo laptop, same as OP reported. After an upgrade on my unstable debian system it booted only to a blinking cursor. Going into a terminal and checking logs I also saw the segmentation fault. It made my laptop unusable as of now. :( Hope that the driver can be brought back or the hardware supported otherwise. This was also reported in #1025659 I'm happy to support you with information as much as I can. Xorg.0.log https://paste.debian.net/1263176/ Hardware info https://paste.debian.net/1263178/
Bug#1025659:
I am also affected by this bug on a 2020 Lenovo laptop, same as OP reported. After an upgrade on my unstable debian system it booted only to a blinking cursor. Going into a terminal and checking logs I also saw the segmentation fault. It made my laptop unusable as of now. :( Hope that the driver can be brought back or the hardware supported otherwise. This was also reported in #1025389 I'm happy to support you with information as much as I can. Xorg.0.log https://paste.debian.net/1263176/ Hardware info https://paste.debian.net/1263178/
Bug#1024342: /etc/X11/Xsession.d/90x11-common_ssh-agent: ssh-agent missing on second log-in
Package: x11-common Version: 1:7.7+23 Severity: normal File: /etc/X11/Xsession.d/90x11-common_ssh-agent Dear Maintainer, When logging out of Cinnamon and back in, I don't have ssh-agent running any more. Several current desktop environments persist environment variables across logins, so that on a logout followed by a login these variables are available. I have found code for doing so in Gnome [1] and Cinnamon [2]. The X11 ssh-agent session startup script checks [ -z "$SSH_AUTH_SOCK" ] as a precondition for launching ssh-agent [3]. So when taken together, the first login will launch ssh-agent, then save environment variables to dbus. The next session will be initialized with these environment variables (presumably something systemd does, haven't checked) and will therefore skip launching ssh-agent, despite the fact that the previous agent got terminated at shutdown of the first session. One possible solution to this would be to replace [ -z "$SSH_AUTH_SOCK" ] with [ ! -S "$SSH_AUTH_SOCK" ], i.e. to check that the environment variable is not only set but actually refers to a socket. That way, when ssh-agent for the first session terminates, the socket will get closed and the next session will launch its own agent despite the fact that the environment variable got persisted. An alternative might be to also inspect SSH_AGENT_PID, and when it's set and doesn't refer to a running process then that could also be taken as in indication that a new agent is needed. I can't think of a reasonable scenario that would warrant such a complex approach; I'd think that the solution in the previous paragraph should be enough, but if I'm missing some legitimate use case where the environment variable would be set before the agent gets launched, then the PID might offer a viable and even safer alternative. Personally I'm not a fan of environment variables getting persisted in this fashion, but given that it is default behavior in multiple desktop environments, and probably there for a reason, I think it makes sense to cater for it in the script. The benefits should outweigh potential drawbacks in weird corner cases. My current workaround, based on [4], is having this in my ~/.xsessionrc: if [ -n "$SSH_AUTH_SOCK" ] && [ ! -S "$SSH_AUTH_SOCK" ]; then unset SSH_AUTH_SOCK unset SSH_AGENT_PID fi [1] https://salsa.debian.org/gnome-team/gnome-session/-/blob/81c88fa3485949f8c7ea12e68d07e8060d368e79/gnome-session/gsm-util.c#L544-707 [2] https://salsa.debian.org/cinnamon-team/cinnamon-session/-/blob/255fd6600dfafe131ca3247d641fdd64098f7f47/cinnamon-session/csm-util.c#L569-715 [3] https://salsa.debian.org/xorg-team/xorg/-/blob/d6af3f0a48de41f74069a8befc4fe9ca0fcd0118/debian/local/Xsession.d/90x11-common_ssh-agent#L10 [4] https://utcc.utoronto.ca/~cks/space/blog/linux/Fedora26CinnamonSSHAgent -- System Information: Debian Release: rodete Architecture: amd64 (x86_64) Foreign Architectures: i386 Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages x11-common depends on: ii lsb-base 11.2 x11-common recommends no packages. x11-common suggests no packages. -- no debconf information
Bug#884829: Still present in Debian 11
A small update: I managed to rebuild the xserver-xorg-core package with the patch applied, but the leak persists. So while it manifests the same way and can be triggered by the same application, my problem seems to have a different cause. On a second thought, it makes sense: if I understand it correctly, XAA, EXA, UXA etc. were replaced by Glamor in recent years. And from the Xorg log it seems that that's what my laptop uses (Intel HD 5500), so I should not experience any issues coming from the EXA code, right? I'm not very experienced with Valgrind, but I'll send an update if I manage to set it up and find anything of interest. Martin P.S. I had no clue about this transition to Glamor; Debian now generally works well out of the box, so I'm not learning about new stuff by constantly fixing stuff. :))
Bug#884829: Still present in Debian 11
Hi, I can confirm this bug still exists in xserver-xorg-core 2:1.20.11-1+deb11u1; I have been suffering from it ever since I upgraded from Debian 10 to Debian 11 a few months ago. The memory usage of Xorg process keeps growing until eventually the laptop becomes unresponsive and OOM killer starts reaping random processes and everything comes crashing down. In my case, I tracked the problem mainly to xfdesktop4 and xfce4-panel (leaking about 5 MB per hour when the machine is idle). Only when I kill both of them the increase in memory consumption stops, although the already consumed memory is not released. Using the machine makes the rate of leaking worse, so clearly there are many other sources that can trigger the leak. I can also confirm that if I install audacious and play it with the visualization on, the leak increases to about 57 MB per hour, so the problem I experience is very likely the same one as reported here. I'm really happy to finally learn I'm not crazy and someone else noticed the issue as well (although I did not expect it to go all the way back to 2017). Is there anything I can do to help move this along? Should I try testing the patch? Or open a bug report upstream? Thanks, Martin
Bug#1011227: xserver-xorg-video-vesa: open /dev/dri/card0: No such file or directory
On Tue, May 24, 2022 at 11:44 AM Julien Cristau wrote: > > On Wed, May 18, 2022 at 05:37:32PM +0300, Martin-Éric Racine wrote: > > On Wed, May 18, 2022 at 5:03 PM Julien Cristau wrote: > > > On Wed, May 18, 2022 at 04:52:01PM +0300, Martin-Éric Racine wrote: > > > > xf86-video-vesa fails to lauch on a VESA-capable host. Logs attached. > > > > > > > Please include kernel logs, and contents of /proc/fb. > > > > $ cat /proc/fb > > 0 VESA VGA > > > > Output of dmesg attached. > > > So you're using vesafb in the kernel, that's not compatible with the > vesa Xorg driver, you have to pick one. Is that documented anywhere? > Another question is why the fbdev Xorg driver fails to init, so you can > try debugging that. Which is highly suspicious to begin with. Martin-Éric
Bug#1011227: xserver-xorg-video-vesa: open /dev/dri/card0: No such file or directory
On Wed, May 18, 2022 at 5:03 PM Julien Cristau wrote: > On Wed, May 18, 2022 at 04:52:01PM +0300, Martin-Éric Racine wrote: > > xf86-video-vesa fails to lauch on a VESA-capable host. Logs attached. > > > Please include kernel logs, and contents of /proc/fb. $ cat /proc/fb 0 VESA VGA Output of dmesg attached. Thanks! Martin-Éric [0.00] Linux version 5.17.0-1-686 (debian-ker...@lists.debian.org) (gcc-11 (Debian 11.2.0-20) 11.2.0, GNU ld (GNU Binutils for Debian) 2.38) #1 SMP PREEMPT Debian 5.17.3-1 (2022-04-18) [0.00] x86/fpu: x87 FPU will use FSAVE [0.00] signal: max sigframe size: 928 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009e7ff] usable [0.00] BIOS-e820: [mem 0x0009e800-0x0009] reserved [0.00] BIOS-e820: [mem 0x000f-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x37fa] usable [0.00] BIOS-e820: [mem 0x37fb-0x37fb2fff] ACPI NVS [0.00] BIOS-e820: [mem 0x37fb3000-0x37fb] ACPI data [0.00] BIOS-e820: [mem 0x-0x] reserved [0.00] Notice: NX (Execute Disable) protection missing in CPU! [0.00] SMBIOS 2.2 present. [0.00] DMI: First International Computer, Inc. ION603/ION603, BIOS 6.00 PG 11/08/2007 [0.00] tsc: Fast TSC calibration using PIT [0.00] tsc: Detected 498.060 MHz processor [0.019830] e820: update [mem 0x-0x0fff] usable ==> reserved [0.019876] e820: remove [mem 0x000a-0x000f] usable [0.019932] last_pfn = 0x37fb0 max_arch_pfn = 0x10 [0.019951] Disabled [0.019961] x86/PAT: MTRRs disabled, skipping PAT initialization too. [0.019978] x86/PAT: Configuration [0-7]: WB WT UC- UC WB WT UC- UC [0.046994] initial memory mapped: [mem 0x-0x1fff] [0.047313] RAMDISK: [mem 0x316ad000-0x34b4dfff] [0.047409] ACPI: Early table checksum verification disabled [0.047436] ACPI: RSDP 0x000F5910 14 (v00 AMDGX3) [0.047478] ACPI: RSDT 0x37FB3000 28 (v01 AMDGX3 AWRDACPI 42302E31 AWRD ) [0.047537] ACPI: FACP 0x37FB3080 74 (v01 AMDGX3 AWRDACPI 42302E31 AWRD ) [0.047593] ACPI BIOS Warning (bug): Invalid length for FADT/Pm2ControlBlock: 16, using default 8 (20211217/tbfadt-669) [0.047642] ACPI: DSDT 0x37FB3100 001581 (v01 AMDGX3 AWRDACPI 1017 MSFT 0300) [0.047693] ACPI: FACS 0x37FB 40 [0.047729] ACPI: Reserving FACP table memory at [mem 0x37fb3080-0x37fb30f3] [0.047749] ACPI: Reserving DSDT table memory at [mem 0x37fb3100-0x37fb4680] [0.047769] ACPI: Reserving FACS table memory at [mem 0x37fb-0x37fb003f] [0.047866] 19MB HIGHMEM available. [0.047879] 875MB LOWMEM available. [0.047890] mapped low ram: 0 - 36bfe000 [0.047903] low ram: 0 - 36bfe000 [0.047946] Zone ranges: [0.047955] DMA [mem 0x1000-0x00ff] [0.047982] Normal [mem 0x0100-0x36bfdfff] [0.048008] HighMem [mem 0x36bfe000-0x37fa] [0.048034] Movable zone start for each node [0.048044] Early memory node ranges [0.048053] node 0: [mem 0x1000-0x0009dfff] [0.048073] node 0: [mem 0x0010-0x37fa] [0.048096] Initmem setup node 0 [mem 0x1000-0x37fa] [0.048168] On node 0, zone DMA: 1 pages in unavailable ranges [0.048739] On node 0, zone DMA: 98 pages in unavailable ranges [0.082807] Using APIC driver default [0.083193] ACPI: PM-Timer IO Port: 0x9c10 [0.083214] No local APIC present or hardware disabled [0.083224] APIC: disable apic facility [0.083234] APIC: switched to apic NOOP [0.083246] smpboot: Allowing 1 CPUs, 0 hotplug CPUs [0.083322] PM: hibernation: Registered nosave memory: [mem 0x-0x0fff] [0.083345] PM: hibernation: Registered nosave memory: [mem 0x0009e000-0x0009efff] [0.083363] PM: hibernation: Registered nosave memory: [mem 0x0009f000-0x0009] [0.083381] PM: hibernation: Registered nosave memory: [mem 0x000a-0x000e] [0.083399] PM: hibernation: Registered nosave memory: [mem 0x000f-0x000f] [0.083424] [mem 0x37fc-0xfffe] available for PCI devices [0.083442] Booting paravirtualized kernel on bare hardware [0.083461] clocksource: refined-jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 7645519600211568 ns [0.083511] setup_percpu: NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:1 nr_node_ids:1 [0.084563] percpu: Embedded 32 pages/cpu s98892 r0 d32180 u131072 [0.084618] pcpu-alloc: s98892 r0 d32180 u131072 alloc=32*4096 [0.084650] pcpu-alloc: [0] 0 [0.084782] Built 1 zonelists, mobility grou
Bug#1011227: xserver-xorg-video-vesa: open /dev/dri/card0: No such file or directory
Package: xserver-xorg-video-vesa Version: 1:2.5.0-1+b1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 xf86-video-vesa fails to lauch on a VESA-capable host. Logs attached. - -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: - -- 00:01.1 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD] Geode LX Video [1022:2081] /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - - total 0 /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): - --- Linux version 5.17.0-1-686 (debian-ker...@lists.debian.org) (gcc-11 (Debian 11.2.0-20) 11.2.0, GNU ld (GNU Binutils for Debian) 2.38) #1 SMP PREEMPT Debian 5.17.3-1 (2022-04-18) Xorg X server log files on system: - -- - -rw-r--r-- 1 root root 6986 May 18 16:46 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - - [ 214.155] (--) Log file renamed from "/var/log/Xorg.pid-851.log" to "/var/log/Xorg.0.log" [ 214.162] X.Org X Server 1.21.1.3 X Protocol Version 11, Revision 0 [ 214.167] Current Operating System: Linux geode 5.17.0-1-686 #1 SMP PREEMPT Debian 5.17.3-1 (2022-04-18) i586 [ 214.168] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1-686 root=UUID=97b2628b-28a5-49f2-85f7-495728b3bef8 ro panic=15 noquiet loglevel=4 nosplash cs5535audio.ac97_quirk=1 iomem=relaxed [ 214.168] xorg-server 2:21.1.3-2+b1 (https://www.debian.org/support) [ 214.168] Current version of pixman: 0.40.0 [ 214.168]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 214.168] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 214.175] (==) Log file: "/var/log/Xorg.0.log", Time: Wed May 18 16:46:34 2022 [ 214.176] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 214.188] (==) No Layout section. Using the first Screen section. [ 214.191] (==) No screen section available. Using defaults. [ 214.191] (**) |-->Screen "Default Screen Section" (0) [ 214.191] (**) | |-->Monitor "" [ 214.199] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 214.205] (==) Automatically adding devices [ 214.205] (==) Automatically enabling devices [ 214.205] (==) Automatically adding GPU devices [ 214.205] (==) Automatically binding GPU devices [ 214.205] (==) Max clients allowed: 256, resource mask: 0x1f [ 214.206] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 214.206]Entry deleted from font path. [ 214.206] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [ 214.206]Entry deleted from font path. [ 214.206] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [ 214.206]Entry deleted from font path. [ 214.207] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist. [ 214.207]Entry deleted from font path. [ 214.207] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [ 214.207]Entry deleted from font path. [ 214.207] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [ 214.207]Entry deleted from font path. [ 214.207] (==) FontPath set to: /usr/share/fonts/X11/misc, built-ins [ 214.207] (==) ModulePath set to "/usr/lib/xorg/modules" [ 214.208] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 214.208] (II) Loader magic: 0x6fd7c0 [ 214.208] (II) Module ABI versions: [ 214.208]X.Org ANSI C Emulation: 0.4 [ 214.208]X.Org Video Driver: 25.2 [ 214.208]X.Org XInput driver : 24.4 [ 214.208]X.Org Server Extension : 10.0 [ 214.229] (++) using VT number 1 [ 214.312] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c6 [ 214.357] (--) PCI:*(0@0:1:1) 1022:2081:1509:801b rev 0, Mem @ 0xd000/268435456, 0xefff/16384, 0xeffec000/16384, 0xeffe8000/16384, 0xefff8000/16384, BIOS @ 0x/131072 [ 214.362] (II) LoadModule: "glx" [ 214.369] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 214.385] (II) Module glx: vendor="X.Org Foundation" [ 214.386]compiled for 1.21.1.3, module version = 1.0.0 [ 214.390]ABI class: X.Org Server Extension, version 10.0 [ 214.391] (==) Matched geode as autoconfigured driver 0 [ 214.391] (==) Matched modesetting as autoconfigured driver 1 [ 214.391] (==) Matched fbdev as autoconfigured driver
Bug#1004946: Cannot hold down backspace to delete password
Regarding the following, written by "Jamie Zawinski" on 2022-02-12 at 09:55 Uhr -0800: Also this is far from the only problem with XInput2's keyboard event handling. See the comments in xscreensaver/driver/xinput.c for a laundry list of its bugs. Why did you switch to it? Or am I misunderstanding that you did? -- .''`. martin f. krafft @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems "i feel sorry for people who don't drink. when they wake up in the morning, that's as good as they're going to feel all day." -- frank sinatra
Bug#1005170: xserver-xorg-video-nouveau: corrupted display on GT218 [GeForce 210] since Firefox 91 ESR
On Tue, Feb 8, 2022 at 9:36 PM Timo Aaltonen wrote: > > Martin-Éric Racine kirjoitti 8.2.2022 klo 18.59: > > On Tue, Feb 8, 2022 at 4:02 PM Martin-Éric Racine > > wrote: > >> > >> On Tue, Feb 8, 2022 at 3:54 PM Timo Aaltonen wrote: > >>> > >>> Martin-Éric Racine kirjoitti 8.2.2022 klo 14.09: > >>> > Package: xserver-xorg-video-nouveau > >>> > Version: 1:1.0.17-1 > >>> > Severity: important > >>> > > >>>> Since ESR 91 replaced ESR 78 in Stable, Firefox randomly triggers nasty > >>>> bugs in nouveau. The content in Firefox gets randomly garbled for > >>>> several minutes then suddenly gets cleaned up. This is highly > >>>> problematic, since I use the browser to access government sites and > >>>> having to close Firefox and logon again seldom is an option. > >>>> > >>>> dmesg shows the following: > >>>> > >>>> [133514.948849] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > >>>> Xorg[1785]] subc 3 class 8597 mthd 1510 data > >>>> [133613.222007] nouveau :01:00.0: Xorg[1785]: nv50cal_space: -16 > >>>> [133624.336810] nouveau :01:00.0: Xorg[1785]: nv50cal_space: -16 > >>>> [133635.477428] nouveau :01:00.0: Xorg[1785]: nv50cal_space: -16 > >>>> [133700.776172] nouveau :01:00.0: Xorg[1785]: nv50cal_space: -16 > >>>> [133716.072659] nouveau :01:00.0: Xorg[1785]: nv50cal_space: -16 > >>>> [133716.355210] nouveau :01:00.0: gr: DATA_ERROR 000d > >>>> [BEGIN_END_ACTIVE] > >>>> [133716.355219] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > >>>> Xorg[1785]] subc 3 class 8597 mthd 12e4 data > >>>> [133716.355232] nouveau :01:00.0: gr: DATA_ERROR 000d > >>>> [BEGIN_END_ACTIVE] > >>>> [133716.355236] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > >>>> Xorg[1785]] subc 3 class 8597 mthd 1360 data > >>>> [133716.355247] nouveau :01:00.0: gr: DATA_ERROR 000d > >>>> [BEGIN_END_ACTIVE] > >>>> [133716.355250] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > >>>> Xorg[1785]] subc 3 class 8597 mthd 19c4 data > >>>> [133716.355264] nouveau :01:00.0: gr: DATA_ERROR 000d > >>>> [BEGIN_END_ACTIVE] > >>>> [133716.355267] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > >>>> Xorg[1785]] subc 3 class 8597 mthd 1a00 data > >>>> [133716.355279] nouveau :01:00.0: gr: DATA_ERROR 000d > >>>> [BEGIN_END_ACTIVE] > >>>> [133716.355283] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > >>>> Xorg[1785]] subc 3 class 8597 mthd 12e8 data > >>>> [133716.355296] nouveau :01:00.0: gr: DATA_ERROR 000d > >>>> [BEGIN_END_ACTIVE] > >>>> [133716.355299] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > >>>> Xorg[1785]] subc 3 class 8597 mthd 12cc data > >>>> [133716.355312] nouveau :01:00.0: gr: DATA_ERROR 000d > >>>> [BEGIN_END_ACTIVE] > >>>> [133716.355315] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > >>>> Xorg[1785]] subc 3 class 8597 mthd 19bc data > >>>> [133716.355328] nouveau :01:00.0: gr: DATA_ERROR 000d > >>>> [BEGIN_END_ACTIVE] > >>>> [133716.355332] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > >>>> Xorg[1785]] subc 3 class 8597 mthd 1380 data > >>>> [133716.355360] nouveau :01:00.0: gr: DATA_ERROR 000d > >>>> [BEGIN_END_ACTIVE] > >>>> [133716.355363] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > >>>> Xorg[1785]] subc 3 class 8597 mthd 1594 data > >>>> [133716.355380] nouveau :01:00.0: gr: DATA_ERROR 000d > >>>> [BEGIN_END_ACTIVE] > >>>> [133716.355384] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > >>>> Xorg[1785]] subc 3 class 8597 mthd 12ec data > >>>> [133716.355400] nouveau :01:00.0: gr: DATA_ERROR 000d > >>>> [BEGIN_END_ACTIVE] > >>>> [133716.355403] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > >>>> Xorg[1785]] subc 3 class 8597 mthd 12d4 data 1d01 > >>>> [133716.355
Bug#1005170: xserver-xorg-video-nouveau: corrupted display on GT218 [GeForce 210] since Firefox 91 ESR
On Tue, Feb 8, 2022 at 4:02 PM Martin-Éric Racine wrote: > > On Tue, Feb 8, 2022 at 3:54 PM Timo Aaltonen wrote: > > > > Martin-Éric Racine kirjoitti 8.2.2022 klo 14.09: > > > Package: xserver-xorg-video-nouveau > > > Version: 1:1.0.17-1 > > > Severity: important > > > > > > Since ESR 91 replaced ESR 78 in Stable, Firefox randomly triggers nasty > > > bugs in nouveau. The content in Firefox gets randomly garbled for several > > > minutes then suddenly gets cleaned up. This is highly problematic, since > > > I use the browser to access government sites and having to close Firefox > > > and logon again seldom is an option. > > > > > > dmesg shows the following: > > > > > > [133514.948849] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > > Xorg[1785]] subc 3 class 8597 mthd 1510 data > > > [133613.222007] nouveau :01:00.0: Xorg[1785]: nv50cal_space: -16 > > > [133624.336810] nouveau :01:00.0: Xorg[1785]: nv50cal_space: -16 > > > [133635.477428] nouveau :01:00.0: Xorg[1785]: nv50cal_space: -16 > > > [133700.776172] nouveau :01:00.0: Xorg[1785]: nv50cal_space: -16 > > > [133716.072659] nouveau :01:00.0: Xorg[1785]: nv50cal_space: -16 > > > [133716.355210] nouveau :01:00.0: gr: DATA_ERROR 000d > > > [BEGIN_END_ACTIVE] > > > [133716.355219] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > > Xorg[1785]] subc 3 class 8597 mthd 12e4 data > > > [133716.355232] nouveau :01:00.0: gr: DATA_ERROR 000d > > > [BEGIN_END_ACTIVE] > > > [133716.355236] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > > Xorg[1785]] subc 3 class 8597 mthd 1360 data > > > [133716.355247] nouveau :01:00.0: gr: DATA_ERROR 000d > > > [BEGIN_END_ACTIVE] > > > [133716.355250] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > > Xorg[1785]] subc 3 class 8597 mthd 19c4 data > > > [133716.355264] nouveau :01:00.0: gr: DATA_ERROR 000d > > > [BEGIN_END_ACTIVE] > > > [133716.355267] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > > Xorg[1785]] subc 3 class 8597 mthd 1a00 data > > > [133716.355279] nouveau :01:00.0: gr: DATA_ERROR 000d > > > [BEGIN_END_ACTIVE] > > > [133716.355283] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > > Xorg[1785]] subc 3 class 8597 mthd 12e8 data > > > [133716.355296] nouveau :01:00.0: gr: DATA_ERROR 000d > > > [BEGIN_END_ACTIVE] > > > [133716.355299] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > > Xorg[1785]] subc 3 class 8597 mthd 12cc data > > > [133716.355312] nouveau :01:00.0: gr: DATA_ERROR 000d > > > [BEGIN_END_ACTIVE] > > > [133716.355315] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > > Xorg[1785]] subc 3 class 8597 mthd 19bc data > > > [133716.355328] nouveau :01:00.0: gr: DATA_ERROR 000d > > > [BEGIN_END_ACTIVE] > > > [133716.355332] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > > Xorg[1785]] subc 3 class 8597 mthd 1380 data > > > [133716.355360] nouveau :01:00.0: gr: DATA_ERROR 000d > > > [BEGIN_END_ACTIVE] > > > [133716.355363] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > > Xorg[1785]] subc 3 class 8597 mthd 1594 data > > > [133716.355380] nouveau :01:00.0: gr: DATA_ERROR 000d > > > [BEGIN_END_ACTIVE] > > > [133716.355384] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > > Xorg[1785]] subc 3 class 8597 mthd 12ec data > > > [133716.355400] nouveau :01:00.0: gr: DATA_ERROR 000d > > > [BEGIN_END_ACTIVE] > > > [133716.355403] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > > Xorg[1785]] subc 3 class 8597 mthd 12d4 data 1d01 > > > [133716.355419] nouveau :01:00.0: gr: DATA_ERROR 000d > > > [BEGIN_END_ACTIVE] > > > [133716.355422] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > > Xorg[1785]] subc 3 class 8597 mthd 1688 data > > > [133716.355438] nouveau :01:00.0: gr: DATA_ERROR 000d > > > [BEGIN_END_ACTIVE] > > > [133716.355442] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > > Xorg[1785]] subc 3 class 8597 mthd 1534 data > > > [133716.355458] nouveau :01:00.0: gr: DATA_ERROR 000d > > > [BEGIN_END_AC
Bug#1005170: xserver-xorg-video-nouveau: corrupted display on GT218 [GeForce 210] since Firefox 91 ESR
On Tue, Feb 8, 2022 at 3:54 PM Timo Aaltonen wrote: > > Martin-Éric Racine kirjoitti 8.2.2022 klo 14.09: > > Package: xserver-xorg-video-nouveau > > Version: 1:1.0.17-1 > > Severity: important > > > > Since ESR 91 replaced ESR 78 in Stable, Firefox randomly triggers nasty > > bugs in nouveau. The content in Firefox gets randomly garbled for several > > minutes then suddenly gets cleaned up. This is highly problematic, since I > > use the browser to access government sites and having to close Firefox and > > logon again seldom is an option. > > > > dmesg shows the following: > > > > [133514.948849] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > Xorg[1785]] subc 3 class 8597 mthd 1510 data > > [133613.222007] nouveau :01:00.0: Xorg[1785]: nv50cal_space: -16 > > [133624.336810] nouveau :01:00.0: Xorg[1785]: nv50cal_space: -16 > > [133635.477428] nouveau :01:00.0: Xorg[1785]: nv50cal_space: -16 > > [133700.776172] nouveau :01:00.0: Xorg[1785]: nv50cal_space: -16 > > [133716.072659] nouveau :01:00.0: Xorg[1785]: nv50cal_space: -16 > > [133716.355210] nouveau :01:00.0: gr: DATA_ERROR 000d > > [BEGIN_END_ACTIVE] > > [133716.355219] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > Xorg[1785]] subc 3 class 8597 mthd 12e4 data > > [133716.355232] nouveau :01:00.0: gr: DATA_ERROR 000d > > [BEGIN_END_ACTIVE] > > [133716.355236] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > Xorg[1785]] subc 3 class 8597 mthd 1360 data > > [133716.355247] nouveau :01:00.0: gr: DATA_ERROR 000d > > [BEGIN_END_ACTIVE] > > [133716.355250] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > Xorg[1785]] subc 3 class 8597 mthd 19c4 data > > [133716.355264] nouveau :01:00.0: gr: DATA_ERROR 000d > > [BEGIN_END_ACTIVE] > > [133716.355267] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > Xorg[1785]] subc 3 class 8597 mthd 1a00 data > > [133716.355279] nouveau :01:00.0: gr: DATA_ERROR 000d > > [BEGIN_END_ACTIVE] > > [133716.355283] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > Xorg[1785]] subc 3 class 8597 mthd 12e8 data > > [133716.355296] nouveau :01:00.0: gr: DATA_ERROR 000d > > [BEGIN_END_ACTIVE] > > [133716.355299] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > Xorg[1785]] subc 3 class 8597 mthd 12cc data > > [133716.355312] nouveau :01:00.0: gr: DATA_ERROR 000d > > [BEGIN_END_ACTIVE] > > [133716.355315] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > Xorg[1785]] subc 3 class 8597 mthd 19bc data > > [133716.355328] nouveau :01:00.0: gr: DATA_ERROR 000d > > [BEGIN_END_ACTIVE] > > [133716.355332] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > Xorg[1785]] subc 3 class 8597 mthd 1380 data > > [133716.355360] nouveau :01:00.0: gr: DATA_ERROR 000d > > [BEGIN_END_ACTIVE] > > [133716.355363] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > Xorg[1785]] subc 3 class 8597 mthd 1594 data > > [133716.355380] nouveau :01:00.0: gr: DATA_ERROR 000d > > [BEGIN_END_ACTIVE] > > [133716.355384] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > Xorg[1785]] subc 3 class 8597 mthd 12ec data > > [133716.355400] nouveau :01:00.0: gr: DATA_ERROR 000d > > [BEGIN_END_ACTIVE] > > [133716.355403] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > Xorg[1785]] subc 3 class 8597 mthd 12d4 data 1d01 > > [133716.355419] nouveau :01:00.0: gr: DATA_ERROR 000d > > [BEGIN_END_ACTIVE] > > [133716.355422] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > Xorg[1785]] subc 3 class 8597 mthd 1688 data > > [133716.355438] nouveau :01:00.0: gr: DATA_ERROR 000d > > [BEGIN_END_ACTIVE] > > [133716.355442] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > Xorg[1785]] subc 3 class 8597 mthd 1534 data > > [133716.355458] nouveau :01:00.0: gr: DATA_ERROR 000d > > [BEGIN_END_ACTIVE] > > [133716.355461] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > Xorg[1785]] subc 3 class 8597 mthd 13b0 data > > [133716.355477] nouveau :01:00.0: gr: DATA_ERROR 000d > > [BEGIN_END_ACTIVE] > > [133716.355481] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 > > Xorg[1785]] subc 3 class 8597 mthd 1570 data > > [133716.355498] nouveau :01:00.0: gr: DATA
Bug#1005170: xserver-xorg-video-nouveau: corrupted display on GT218 [GeForce 210] since Firefox 91 ESR
Package: xserver-xorg-video-nouveau Version: 1:1.0.17-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Since ESR 91 replaced ESR 78 in Stable, Firefox randomly triggers nasty bugs in nouveau. The content in Firefox gets randomly garbled for several minutes then suddenly gets cleaned up. This is highly problematic, since I use the browser to access government sites and having to close Firefox and logon again seldom is an option. dmesg shows the following: [133514.948849] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 Xorg[1785]] subc 3 class 8597 mthd 1510 data [133613.222007] nouveau :01:00.0: Xorg[1785]: nv50cal_space: -16 [133624.336810] nouveau :01:00.0: Xorg[1785]: nv50cal_space: -16 [133635.477428] nouveau :01:00.0: Xorg[1785]: nv50cal_space: -16 [133700.776172] nouveau :01:00.0: Xorg[1785]: nv50cal_space: -16 [133716.072659] nouveau :01:00.0: Xorg[1785]: nv50cal_space: -16 [133716.355210] nouveau :01:00.0: gr: DATA_ERROR 000d [BEGIN_END_ACTIVE] [133716.355219] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 Xorg[1785]] subc 3 class 8597 mthd 12e4 data [133716.355232] nouveau :01:00.0: gr: DATA_ERROR 000d [BEGIN_END_ACTIVE] [133716.355236] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 Xorg[1785]] subc 3 class 8597 mthd 1360 data [133716.355247] nouveau :01:00.0: gr: DATA_ERROR 000d [BEGIN_END_ACTIVE] [133716.355250] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 Xorg[1785]] subc 3 class 8597 mthd 19c4 data [133716.355264] nouveau :01:00.0: gr: DATA_ERROR 000d [BEGIN_END_ACTIVE] [133716.355267] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 Xorg[1785]] subc 3 class 8597 mthd 1a00 data [133716.355279] nouveau :01:00.0: gr: DATA_ERROR 000d [BEGIN_END_ACTIVE] [133716.355283] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 Xorg[1785]] subc 3 class 8597 mthd 12e8 data [133716.355296] nouveau :01:00.0: gr: DATA_ERROR 000d [BEGIN_END_ACTIVE] [133716.355299] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 Xorg[1785]] subc 3 class 8597 mthd 12cc data [133716.355312] nouveau :01:00.0: gr: DATA_ERROR 000d [BEGIN_END_ACTIVE] [133716.355315] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 Xorg[1785]] subc 3 class 8597 mthd 19bc data [133716.355328] nouveau :01:00.0: gr: DATA_ERROR 000d [BEGIN_END_ACTIVE] [133716.355332] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 Xorg[1785]] subc 3 class 8597 mthd 1380 data [133716.355360] nouveau :01:00.0: gr: DATA_ERROR 000d [BEGIN_END_ACTIVE] [133716.355363] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 Xorg[1785]] subc 3 class 8597 mthd 1594 data [133716.355380] nouveau :01:00.0: gr: DATA_ERROR 000d [BEGIN_END_ACTIVE] [133716.355384] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 Xorg[1785]] subc 3 class 8597 mthd 12ec data [133716.355400] nouveau :01:00.0: gr: DATA_ERROR 000d [BEGIN_END_ACTIVE] [133716.355403] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 Xorg[1785]] subc 3 class 8597 mthd 12d4 data 1d01 [133716.355419] nouveau :01:00.0: gr: DATA_ERROR 000d [BEGIN_END_ACTIVE] [133716.355422] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 Xorg[1785]] subc 3 class 8597 mthd 1688 data [133716.355438] nouveau :01:00.0: gr: DATA_ERROR 000d [BEGIN_END_ACTIVE] [133716.355442] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 Xorg[1785]] subc 3 class 8597 mthd 1534 data [133716.355458] nouveau :01:00.0: gr: DATA_ERROR 000d [BEGIN_END_ACTIVE] [133716.355461] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 Xorg[1785]] subc 3 class 8597 mthd 13b0 data [133716.355477] nouveau :01:00.0: gr: DATA_ERROR 000d [BEGIN_END_ACTIVE] [133716.355481] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 Xorg[1785]] subc 3 class 8597 mthd 1570 data [133716.355498] nouveau :01:00.0: gr: DATA_ERROR 000d [BEGIN_END_ACTIVE] [133716.355502] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 Xorg[1785]] subc 3 class 8597 mthd 166c data [133716.355518] nouveau :01:00.0: gr: DATA_ERROR 000d [BEGIN_END_ACTIVE] [133716.355521] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 Xorg[1785]] subc 3 class 8597 mthd 1518 data [133716.355537] nouveau :01:00.0: gr: DATA_ERROR 000d [BEGIN_END_ACTIVE] [133716.355540] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 Xorg[1785]] subc 3 class 8597 mthd 1520 data [133716.37] nouveau :01:00.0: gr: DATA_ERROR 000d [BEGIN_END_ACTIVE] [133716.355560] nouveau :01:00.0: gr: 0010 [] ch 3 [003fa24000 Xorg[1785]] subc 3 class 8597 mthd 1658 data [133716.355576] nouveau :01:00.0: gr: DATA_ERROR 000d [BEGIN_END_ACTIVE] [133716.355580] nouveau
Bug#999657: xserver-xorg-core: SIGABRT on Geode LX
Package: xserver-xorg-core Version: 2:1.20.11-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 $ sudo LC_ALL=C coredumpctl debug 796 PID: 796 (Xorg) UID: 101 (Debian-gdm) GID: 122 (Debian-gdm) Signal: 6 (ABRT) Timestamp: Sun 2021-11-14 11:56:46 EET (35min ago) Command Line: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/101/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3 Executable: /usr/lib/xorg/Xorg Control Group: /user.slice/user-101.slice/session-c2.scope Unit: session-c2.scope Slice: user-101.slice Session: c2 Owner UID: 101 (Debian-gdm) Boot ID: f3a26744832345239aef0aefea90c72c Machine ID: 1063a9d1fb9df6e371ea9f94491345ed Hostname: geode Storage: /var/lib/systemd/coredump/core.Xorg.101.f3a26744832345239aef0aefea90c72c.796.163688380600.zst (present) Disk Size: 1.5M Message: Process 796 (Xorg) of user 101 dumped core. Found module linux-gate.so.1 with build-id: 26cfc7f594b1cd597c1dd0029da5ca8cc8a38fcd Found module libicudata.so.67 with build-id: 83e8d014d7a5f6d5a428b3ee29dfa7bda5a19196 Found module libicuuc.so.67 with build-id: f4808c52328e01d59304fe921eea551503cb6845 Found module libxml2.so.2 with build-id: a228f93c55a0471c6af6f854ef01fd44263c2b6c Found module libtinfo.so.6 with build-id: c96350c275bfaa792c87a215e0419d0a13bcfaca Found module libz3.so.4 with build-id: 2cc826025173edf6736eae4d1e3cb7204a6bbd7f Found module libedit.so.2 with build-id: ebb868e816530e2391a4c11101a8a343e1a70d2e Found module libffi.so.8 with build-id: 73cdf5d5ebbd8539c40cde02d82f5841f0d839a8 Found module libatomic.so.1 with build-id: 9f2e8078c39a22274be214e78fab5b3f46dffd3b Found module libgcc_s.so.1 with build-id: e645d7848b6fde91618294cbcc7ee43fa13e53c0 Found module libstdc++.so.6 with build-id: 66615284d14b0f61cc9fbe643037d0873a66e471 Found module libvulkan.so.1 with build-id: b37c08ebda037507a652b6566c4181b38c7f3cca Found module libdrm_nouveau.so.2 with build-id: de6d2837c511a549f3974046aacdebde3719bcb2 Found module libdrm_amdgpu.so.1 with build-id: 9c2ec3c9f40a516af0886087ba01da24e6f45145 Found module libelf.so.1 with build-id: 6c10ac18e4c9de96b7cabf0c0115bdbaaa8009d3 Found module libdrm_radeon.so.1 with build-id: f56eb9fa0a13d792723fc64f182dbaf9121e8b43 Found module libsensors.so.5 with build-id: 686675d0b0908055ba7081b1f873155d28a8753d Found module libexpat.so.1 with build-id: 93a838c801828692e5922d763ccaefdba2733ebe Found module libLLVM-12.so.1 with build-id: 42f0f6873784c93609b3de4f251969932c58638d Found module libglapi.so.0 with build-id: c39e117948f1ff056758e91f09164b0fec081fa7 Found module swrast_dri.so with build-id: f97cd40fd941328398c07fc3bffd840a703ffc73 Found module libexa.so with build-id: 7d820816d6768df89205424d2072bba1a94d95a8 Found module libfb.so with build-id: 39663b5f810f6861868f3e4a1f94428b99ac13e6 Found module libint10.so with build-id: fc3f53c365dba85b60e9137106d62ac75ddaec62 Found module libvgahw.so with build-id: c9e255566c4cb25933b352cf799eda69a1261c92 Found module geode_drv.so with build-id: 75869e0950418b46e56072e542d90f09892da7b7 Found module libxcb.so.1 with build-id: 03195227c69b0195390b4b8b5ee188bb12cb1cd3 Found module libX11.so.6 with build-id: 35a90bcb02a9b194371505741049efe58b4c8769 Found module libGLX.so.0 with build-id: c75c08d5765c67238038b85348a34845774bd92e Found module libGLdispatch.so.0 with build-id: bc9e99fc57dd02a74d7e7a3ed8a792688e054354 Found module libGL.so.1 with build-id: fbfc96e21f8bb5dbb7fc1a821803eba49bfad018 Found module libglx.so with build-id: 7a6f6a7ee6b4c97d85a65d556de35d2ed55db275 Found module libbrotlicommon.so.1 with build-id: f63efc2a7a62dd49dddfc67aec6b4fb6d7041c9c Found module libbrotlidec.so.1 with build-id: f54312be9fd635f41c88a2fba6f48194b5a514e5 Found module libpng16.so.16 with build-id: d63474e9123664b790ae0dea7c0d3f14d756ea98 Found module libmd.so.0 with build-id: f9f1c69ce240aea241d9978cf6146a61d9061bd0 Found module libcap-ng.so.0 with build-id: aa6038a53112df6f372332a19d44df3f0226cf3e Found module libcap.so.2 with build-id: dd3588996222b97eb95fbcf60452215fe44ae0c5 Found module liblz4.so.1 with build-id: 7ccef3390a7a41278e860f86aae9ef9bfa68d5a9 Found module libzstd.so.1 with
Bug#981368: xserver-xorg-video-intel: Xserver becomes unresponsive with some worloads. maybe related to video rendering
Control: reassign -1 linux Control: found -1 5.10.0-2 Control: affects -1 xserver-xorg-video-intel Control: fixed -1 5.10.19-1 Control: close -1 5.10.19-1 On Tue, 23 Feb 2021 22:36:02 +0100 joerg.mechnich wrote: > Looks like this was actually a bug in the i915 module: > > https://gitlab.freedesktop.org/drm/intel/-/issues/2905 > > There is a linked issue #2923 > "deadlock in intel_atomic_cleanup_work (kernel 5.10.5)" > that seems to fit the descriptions in this thread here. > > After upgrading to a custom 5.10.17 kernel, I don't seem to experience > the same issue anymore while still using the intel Xorg driver. > > I agree that this report could be closed now. Hi, Since this seems to be a kernel bug, I am resssigning this bug report to linux kernel and marking it as affecting xserver-xorg-video-intel. Since linux 5.10.19 is already in sid I am marking this bug report as fixed with that upload. Trying to do everything with this message, not sure if it will work well. > Cheers and thanks for keeping the intel driver alive, still performs > significantly better on my particular system than the modesetting driver! +1 Regards, -- Agustin
Wayland backport for buster?
Would one of the wayland maintainers consider doing an upload to buster-backports? I just built it fine on buster without any modifications, but I don't want to maintain a backport. -- Martin Michlmayr https://www.cyrius.com/
Bug#947813: SIGSEGV resulting from mesa dri2_add_config dealing poorly with invalid attrib
My issue appears to be largely due to a version mismatch, and I have been able to resolve this. I had tried to get a specific version from unstable to test a fix for a different bug, but apparently I misunderstood how pinning works and got updates to mesa packages from the unstable release even after the version for which I intended this. Once I downgraded mesa packages to testing version, I was able to start X again. I'll leave it to you whether you believe this kind of issue is worth addressing at the distro level (perhaps via more strict version dependencies?) or forwarding to the upstream maintainers (so that unexpected behavior from a module library gets detected in a nicer fashion than by crashing the X server). If you decide to just close this bug, that's fine with me, too. In that case sorry for the noise. $ cat /etc/apt/preferences.d/mesa.pref Explanation: test fix for #933906 Package: *mesa* Pin: release a=unstable Version: 19.1.4-1 Pin-Priority: 600 $ dpkg -l '*mesa*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===---=> ii libegl-mesa0:amd64 19.2.6-1 amd64free implementation of the EGL API -- Mesa vendor library ii libegl-mesa0-dbgsym:amd64 19.2.6-1 amd64debug symbols for libegl-mesa0 ii libegl1-mesa:amd64 19.3.1-3 amd64 transitional dummy package ii libgl1-mesa-dri:amd64 19.3.1-3 amd64free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-dri-dbgsym:amd6419.3.1-3 amd64debug symbols for libgl1-mesa-dri un libgl1-mesa-glx (no description available) un libgl1-mesa-swx11 (no description available) ii libglapi-mesa:amd64 19.3.1-3 amd64free implementation of the GL API -- shared library ii libglapi-mesa-dbgsym:amd64 19.3.1-3 amd64debug symbols for libglapi-mesa un libgles2-mesa (no description available) ii libglu1-mesa:amd64 9.0.1-1 amd64Mesa OpenGL utility library (GLU) ii libglx-mesa0:amd64 19.3.1-3 amd64free implementation of the OpenGL API -- GLX vendor libra> un libwayland-egl1-mesa (no description available) un mesa-opencl-icd (no description available) un mesa-utils(no description available) ii mesa-va-drivers:amd64 19.3.1-3 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd6419.3.1-3 amd64Mesa VDPAU video acceleration drivers ii mesa-vdpau-drivers-dbgsym:amd64 19.3.1-3 amd64debug symbols for mesa-vdpau-drivers ii mesa-vulkan-drivers:amd64 19.3.1-3 amd64Mesa Vulkan graphics drivers un mesag3(no description available) un xlibmesa3 (no description available)
Bug#947813: SIGSEGV resulting from mesa dri2_add_config dealing poorly with invalid attrib
Package: libegl-mesa0 Version: 19.2.6-1 It seems dri2_add_config is encountering some invalid values causing memory corruption and subsequent SIGSEGV at X server startup. The stack trace written to the Xorg log isn't too useful, so I ran X under gdb with debug symbols installed, and copied relevant portions below. The way I read the results from that, for i==24 I get attrib==__DRI_ATTRIB_MAX(=50). So dri2_add_config will enter the default case in egl_dri2.c:319, call the inlined _eglSetConfigKey for some invalid key for which _eglOffsetOfConfig returns its default of -1 (as seen in %rdx). The assertion of a positive offset apparently is disabled in my build. This clobbers some bytes of the display pointer in the base data structure, which will lead to invalid access later on, e.g. during _eglValidateConfig. I haven't been able to work out where the invalid attrib is coming from. I don't know where dri2_dpy->core->indexConfigAttrib is implemented. (gdb) break dri2_add_config Breakpoint 1 at 0x7fffecce8a40: file ../src/egl/drivers/dri2/egl_dri2.c, line 221. ⋮ Thread 1 "Xorg" hit Breakpoint 1, dri2_add_config (disp=disp@entry=0x55891220, dri_config=0x5585ab90, id=id@entry=1, surface_type=surface_type@entry=4, attr_list=attr_list@entry=0x7fffe2e4, rgba_masks=rgba_masks@entry=0x0) at ../src/egl/drivers/dri2/egl_dri2.c:221 221 ../src/egl/drivers/dri2/egl_dri2.c: No such file or directory. ⋮ [step past _eglInitConfig call] (gdb) watch base.Display Hardware watchpoint 2: base.Display (gdb) c Continuing. Thread 1 "Xorg" hit Hardware watchpoint 2: base.Display Old value = (_EGLDisplay *) 0x55891220 New value = (_EGLDisplay *) 0x5500 dri2_add_config (disp=disp@entry=0x55891220, dri_config=0x5585ab90, id=id@entry=1, surface_type=surface_type@entry=4, attr_list=attr_list@entry=0x7fffe2e4, rgba_masks=rgba_masks@entry=0x0) at ../src/egl/drivers/dri2/egl_dri2.c:239 239 in ../src/egl/drivers/dri2/egl_dri2.c (gdb) bt surface_type=surface_type@entry=4, attr_list=attr_list@entry=0x7fffe2e4, rgba_masks=rgba_masks@entry=0x0) at ../src/egl/drivers/dri2/egl_dri2.c:239 #1 0x7fffeccef239 in drm_add_configs_for_visuals (drv=0x7fffe370, disp=0x55891220) at ../src/egl/drivers/dri2/platform_drm.c:640 #2 dri2_initialize_drm (drv=drv@entry=0x55891d00, disp=disp@entry=0x55891220) at ../src/egl/drivers/dri2/platform_drm.c:761 #3 0x7fffecce894b in dri2_initialize (disp=0x55891220, drv=0x55891d00) at ../src/egl/drivers/dri2/egl_dri2.c:911 #4 dri2_initialize (drv=0x55891d00, disp=0x55891220) at ../src/egl/drivers/dri2/egl_dri2.c:876 #5 0x7fffecce4b9d in _eglMatchAndInitialize (disp=disp@entry=0x55891220) at ../src/egl/main/egldriver.c:75 #6 0x7fffecce4be6 in _eglMatchDriver (disp=disp@entry=0x55891220) at ../src/egl/main/egldriver.c:96 #7 0x7fffeccdf188 in eglInitialize (dpy=0x55891220, major=0x0, minor=0x0) at ../src/egl/main/eglapi.c:617 #8 0x7621d292 in glamor_egl_init (scrn=scrn@entry=0x557ff150, fd=) at ../../../../../../glamor/glamor_egl.c:927 #9 0x77fbd183 in try_enable_glamor (pScrn=0x557ff150) at ../../../../../../../hw/xfree86/drivers/modesetting/driver.c:769 #10 PreInit (pScrn=0x557ff150, flags=) at ../../../../../../../hw/xfree86/drivers/modesetting/driver.c:996 #11 0x555ef814 in InitOutput (pScreenInfo=pScreenInfo@entry=0x557c37c0 , argc=argc@entry=1, argv=argv@entry=0x7fffe6a8) at ../../../../../../hw/xfree86/common/xf86Init.c:522 #12 0x555b2714 in dix_main (argc=1, argv=0x7fffe6a8, envp=) at ../../../../dix/main.c:193 #13 0x76ed3bbb in __libc_start_main (main=0x5559c710 , argc=1, argv=0x7fffe6a8, init=, fini=, rtld_fini=, stack_end=0x7fffe698) at ../csu/libc-start.c:308 #14 0x5559c74a in _start () (gdb) disas Dump of assembler code for function dri2_add_config: 0x7fffecce8a40 <+0>: push %r15 0x7fffecce8a42 <+2>: push %r14 0x7fffecce8a44 <+4>: push %r13 0x7fffecce8a46 <+6>: push %r12 0x7fffecce8a48 <+8>: mov%rsi,%r12 0x7fffecce8a4b <+11>: mov%rdi,%rsi 0x7fffecce8a4e <+14>: push %rbp 0x7fffecce8a4f <+15>: xor%ebp,%ebp 0x7fffecce8a51 <+17>: push %rbx 0x7fffecce8a52 <+18>: lea0x15b7f(%rip),%rbx# 0x7fffeccfe5d8 0x7fffecce8a59 <+25>: sub$0x118,%rsp 0x7fffecce8a60 <+32>: mov0x70(%rdi),%r15 0x7fffecce8a64 <+36>: mov%rdi,(%rsp) 0x7fffecce8a68 <+40>: lea0x44(%rsp),%r14 0x7fffecce8a6d <+45>: lea0x40(%rsp),%r13 0x7fffecce8a72 <+50>: mov%edx,0x3c(%rsp) 0x7fffecce8a76 <+54>: mov%ecx,0x14(%rsp) 0x7fffecce8a7a <+58>: mov%r8,0x20(%rsp) 0x7fffecce8a7f <+63>: mov%r9,0x28(%rsp) 0x7fffecce8a84 <+68>: mov%fs:0x28,%rax 0x7fffecce8a8d <+77>: mov%rax,0x108(%rsp)
Bug#943893: glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage
On Thu, Oct 31, 2019 at 05:24:52PM +0100, Michel Dänzer wrote: > On 2019-10-31 3:11 p.m., Agustin Martin Domingo wrote: > > Package: xserver-xorg-core > > Version: 2:1.20.4-1 > > Severity: important > > > > Dear Maintainer, > > > > X session crashes randomly, losing unsaved information. > > > > Xorg.0.log (attached below) shows that a segfault is aborting the server. > > > > Error starts with > > > > glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage > > > > Browsing for that error I found > > > > [Bug 110500 - X-Server crashes - GL error: GL_OUT_OF_MEMORY in > > glTexSubImage ] > > https://bugs.freedesktop.org/show_bug.cgi?id=110500 > > > > with a similar backtrace. > > > > Very similar backtraces (but for /usr/bin/Xwayland instead of > > /usr/lib/xorg/modules/libglamoregl.so) are reported in > > > > [Sometimes my Ubuntu Log me out and close all applications] > > https://gitlab.freedesktop.org/xorg/xserver/issues/833. > > > > and > > > > [https://gitlab.freedesktop.org/xorg/xserver/issues/647] > > https://gitlab.freedesktop.org/xorg/xserver/issues/647 > > > > This last one seems already fixed upstream, and there is a suggestion that > > Xwayland 1.20.5 contains the fix. Since I see libglamoregl.so in my > > backtrace I am setting xserver-xorg-core as affected package. Please > > reassign if aprppriate. > > The root cause seems to be a memory leak in the nouveau drivers. While > glamor can be made more robust against not being able to allocate/update > OpenGL textures, at some point it won't be able to continue if no memory > can be allocated, so it's better to address the leak. Thanks for the info. Seems that this has already been reported against the nouveau driver, [Xorg crashes randomly because of memory leak] https://bugs.freedesktop.org/show_bug.cgi?id=110714 Bad news in that bug report are that 1.20.5 is reported not helping. Regards, -- Agustin
Bug#943893: glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage
Package: xserver-xorg-core Version: 2:1.20.4-1 Severity: important Dear Maintainer, X session crashes randomly, losing unsaved information. Xorg.0.log (attached below) shows that a segfault is aborting the server. Error starts with glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage Browsing for that error I found [Bug 110500 - X-Server crashes - GL error: GL_OUT_OF_MEMORY in glTexSubImage ] https://bugs.freedesktop.org/show_bug.cgi?id=110500 with a similar backtrace. Very similar backtraces (but for /usr/bin/Xwayland instead of /usr/lib/xorg/modules/libglamoregl.so) are reported in [Sometimes my Ubuntu Log me out and close all applications] https://gitlab.freedesktop.org/xorg/xserver/issues/833. and [https://gitlab.freedesktop.org/xorg/xserver/issues/647] https://gitlab.freedesktop.org/xorg/xserver/issues/647 This last one seems already fixed upstream, and there is a suggestion that Xwayland 1.20.5 contains the fix. Since I see libglamoregl.so in my backtrace I am setting xserver-xorg-core as affected package. Please reassign if aprppriate. Thanks for your work in xorg. Regards, -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Jan 11 2010 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 Mar 5 2019 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 0 KMS configuration files: /etc/modprobe.d/i915-kms.conf: options i915 modeset=1 /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 5.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 9.2.1 20191008 (Debian 9.2.1-9)) #1 SMP Debian 5.3.7-1 (2019-10-19) -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (200, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8), LANGUAGE=es_ES.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xserver-xorg-core depends on: ii keyboard-configuration 1.193 ii libaudit1 1:2.8.5-2 ii libbsd0 0.10.0-1 ii libc6 2.29-2 ii libdbus-1-3 1.12.16-2 ii libdrm2 2.4.99-1 ii libegl1 1.1.0-1+b1 ii libegl1-mesa19.2.1-1 ii libepoxy0 1.5.3-0.1 ii libgbm1 19.2.1-1 ii libgcrypt20 1.8.5-3 ii libgl1 1.1.0-1+b1 ii libpciaccess0 0.14-1 ii libpixman-1-0 0.36.0-1 ii libselinux1 2.9-2+b2 ii libsystemd0 242-7 ii libudev1242-7 ii libunwind8 1.2.1-9 ii libxau6 1:1.0.8-1+b2 ii libxdmcp6 1:1.1.2-3 ii libxfont2 1:2.0.3-1 ii libxshmfence1 1.3-1 ii udev242-7 ii xserver-common 2:1.20.4-1 Versions of packages xserver-xorg-core recommends: ii libgl1-mesa-dri 19.2.1-1 ii libpam-systemd 242-7 Versions of packages xserver-xorg-core suggests: ii xfonts-100dpi1:1.0.4+nmu1 ii xfonts-75dpi 1:1.0.4+nmu1 ii xfonts-scalable 1:1.0.3-1.1 -- no debconf information Xorg.0.log.old Description: application/trash
Bug#939373: xorg-server: Copy/paste broken with wayland
Source: xorg-server Version: 2:1.20.4-1 Severity: normal Dear Maintainer, I'm not really sure if this is the right package to report this bug to, bus as xwayland is built from it, I guess I'm right ... Since a recent update to my system it defaults to wayland instead of xorg. From that moment on, copy/paste behaviour went berserk! It is not really consistent how it goes wromg, but there are some common annoyances that I observe: 1. copy/paste via primary selection works within some applications 2. copy/paste via primary selection almost allways fails from one application to another 3. when copying text and trying to paste it, it gets replaced by text that got accidentially selected by some default mechanism (e.g. when pressing Ctrl-L in nautilus to paste a path) 4. sometimes the primary selection will replace the text selected by Ctrl-C and vice versa ... this is really annoying, as I am used to take primary selection and copy/paste buffer to be completely seperated and used it that way for more than twenty years ... there might be more, but at the moment I can't remember all annoyances that struck me in this case. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (999, 'unstable'), (501, 'experimental'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Re: Bug#900108: xserver-xorg-video-geode: FTBFS with xserver 1.20
It ought to be noted that: 1) This bug was fixed ages ago. 2) It only concerns building against Xserver 1.20, which has been stuck in unstable for ages. 3) Basically, the version in testing works as expected with the Xserver that is in testing. Despite this, xf86-video-geode has been slated for removal. I'd really like to know why. Martin-Éric 2018-05-26 12:28 GMT+03:00 Emilio Pozuelo Monfort : > Source: xserver-xorg-video-geode > Version: 2.11.19-3 > Severity: serious > Tags: patch > > geode fails to build with xserver 1.20. There is a patch available > upstream but no release at this time: > > https://cgit.freedesktop.org/xorg/driver/xf86-video-geode/commit/?id=8382e6bb0c76a8029493eae3f2d7a3dbfd0cfc12 > > Emilio
Bug#900550: xserver-xorg-core: X server segfaults for xfce4+nouveau after 2:1.19.6-1 -> 2:1.20.0-2 upgrade
Control: tags -1 +patch Control: affects -1 xfce4-session On Fri, Jun 01, 2018 at 12:00:37PM +0200, Michel Dänzer wrote: > On 2018-06-01 10:10 AM, Agustin Martin Domingo wrote: > > Package: xserver-xorg-core > > Version: 2:1.20.0-2 > > Severity: important > > > > Dear Maintainer, > > > > After 2:1.19.6-1 -> 2:1.20.0-2 xfce4-session+nouveau segfaults on startup > > and cannot start sesion. Trying to start it manually with startxfce4 > > fails giving > > they suggests that it may be the real cause, with a a fatal interaction > > between the "compositor" option of xfwm4 and xorg-server-1.20.0. It is also > > noted that this may be a problem not only with the nouveau driver, but also > > with radeon driver, both with xfce4. > > It would happen with anything using EXA. > > https://patchwork.freedesktop.org/patch/226573/ fixes it. Patch tested, problem gone with xfce4 composer enabled. Thanks. -- Agustin
Bug#900550: xserver-xorg-core: X server segfaults for xfce4+nouveau after 2:1.19.6-1 -> 2:1.20.0-2 upgrade
Package: xserver-xorg-core Version: 2:1.20.0-2 Severity: important Dear Maintainer, After 2:1.19.6-1 -> 2:1.20.0-2 xfce4-session+nouveau segfaults on startup and cannot start sesion. Trying to start it manually with startxfce4 fails giving (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x555e574106fd] (EE) 1: /usr/lib/xorg/Xorg (0x555e5725d000+0x1b73b9) [0x555e574143b9] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fc78ff7+0x11f50) [0x7fc78ff81f50] (EE) 3: /usr/lib/xorg/Xorg (miRenderColorToPixel+0xe) [0x555e57384a9e] (EE) 4: /usr/lib/xorg/modules/libexa.so (0x7fc78c9e+0xf12b) [0x7fc78c9ef12b] (EE) 5: /usr/lib/xorg/Xorg (0x555e5725d000+0x13a786) [0x555e57397786] (EE) 6: /usr/lib/xorg/Xorg (0x555e5725d000+0x12eaec) [0x555e5738baec] (EE) 7: /usr/lib/xorg/Xorg (0x555e5725d000+0x5b008) [0x555e572b8008] (EE) 8: /usr/lib/xorg/Xorg (0x555e5725d000+0x5f008) [0x555e572bc008] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7) [0x7fc78fbd1a87] (EE) 10: /usr/lib/xorg/Xorg (_start+0x2a) [0x555e572a5d0a] (EE) (EE) Segmentation fault at address 0x8 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation fault). Server aborting (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.2.log" for additional information. (EE) (II) AIGLX: Suspending AIGLX clients for VT switch (EE) Server terminated with error (1). Closing log file. No problem with icewm and probably other windows managers. I have googled a bit about this problem and found a recent message in debian-user about this very same problem, [upgrade to X 1.20.0 broken] https://lists.debian.org/debian-user/2018/05/msg01008.html Problem has been confirmed by some people in that thread and it is suggested to be triggered by the Xfce compositor https://lists.debian.org/debian-user/2018/05/msg01035.html As a matter of fact, if I disable the compositor, problem goes away. I am filing this bug report against xserver-xorg-core because in other reference about this problem in slackware, https://www.linuxquestions.org/questions/slackware-14/slackware-current-xorg-server-1-20-0-with-xf86-video-nouveau-segfaults-4175629581/ they suggests that it may be the real cause, with a a fatal interaction between the "compositor" option of xfwm4 and xorg-server-1.20.0. It is also noted that this may be a problem not only with the nouveau driver, but also with radeon driver, both with xfce4. In slackware they rebuild xfce4 with --disable-compositor as a workaround, but in that thread they point to an old xorg-server 2009 commit as dealing with this, not sure if that still applies. Note: This bug report is sent from icewm, not xfce4. Regards, -- Agustin -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Jan 11 2010 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 May 24 18:23 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/i915-kms.conf: options i915 modeset=1 /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 4.16.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-19)) #1 SMP Debian 4.16.12-1 (2018-05-27) udev information: - P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 E: EV=3 E: ID_FOR_SEAT=input-acpi-LNXPWRBN_00 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXPWRBN:00 E: ID_PATH_TAG=acpi-LNXPWRBN_00 E: KEY=10 0 E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw E: NAME="Power Button" E: PHYS="LNXPWRBN/button/input0" E: PRODUCT=19/0/1/0 E: PROP=0 E: SUBSYSTEM=input E: TAGS=:seat: E: USEC_INITIALIZED=26651401 P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event3 N: input/event3 E: BACKSPACE=guess E: DEVNAME=/dev/input/event3 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event3 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXPWRBN:00 E: ID_PATH_TAG=acpi-LNXPWRBN_00 E: LIBINPUT_DEVICE_GROUP=19/0/1:LNXPWRBN/button E: MAJOR=13 E: MINOR=67 E: SUBSYSTEM=input E: TAGS=:power-switch: E: USEC_INITIALIZED=28869196 E: XKBLAYOUT=es E: XKBMODEL=pc105 E: XKBOPTIONS=lv3:ralt_switch,terminate:ctrl_alt_bksp P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3 E: EV=3 E: ID_FOR_SEAT=input-acpi-PNP0C0C_00 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-PNP0C0C:00 E: ID_PATH_TAG=acpi-PNP0C0C_00 E: KEY=10 0 E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw E: NAME="Power
Bug#900352: new xorg-server version causes a random freezes in plasmashell
Hi. Maximiliano Curia - 29.05.18, 14:18: > Package: src:xorg-server > Version: 2:1.20.0-2 > Severity: critical > Tags: upstream […] > The severity is set as it breaks "unrelated programs" although I'm not > sure a desktop environment can be called "unrelated" to x, but in any > case, it would be better if this version of xorg does not migrate to > testing till this is fixed. Probably related: xserver-xorg-core: flickering, black screen and modeset driver error: flip queue failed: Cannot allocate memory https://bugs.debian.org/900333 But depends on whether you use modesettings driver and have your Xorg log spammed with: [ 1201.939] (WW) modeset(0): flip queue failed: Cannot allocate memory [ 1201.939] (WW) modeset(0): Page flip failed: Cannot allocate memory [ 1201.939] (EE) modeset(0): present flip failed Thanks, -- Martin
Bug#900333: xserver-xorg-core: flickering, black screen and modeset driver error… downgrading fixes the issue
Hi! Downgrading to xserver-xorg-core 2:1.19.6-1 fixes the issue completely. Removing xserver-xorg-video-intel had no effect. Thanks, -- Martin
Bug#877811: xorg: FN key causes stuck keypress
Package: xorg Version: 1:7.7+19 Severity: important Dear Maintainer, This is a bug on my Lenovo Yoga 710 laptop. As far as I know, it happens in all X11 applications (but not outside of xorg). To replicate, e.g., I can hold down the right arrow key, then hold the FN key, then release the arrow key, then release the FN key. In xev, this produces keypress/keyrelease events separated by ~30ms, with the next keypress immediately after the previous keyrelease event, until I change windows. I think this is because the FN + right key combination recognizes the "End" key being unpressed, and assumes the right arrow key is still pressed. This has caused a stuck backspace in emacs when I code multiple times, and while brevity is important to me, sometimes those lines are even more important. -Martin -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:5916] (rev 02) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 4.9.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19) Xorg X server log files on system: -- -rw-r--r-- 1 martin martin 35069 Jun 9 12:27 /home/martin/.local/share/xorg/Xorg.0.log Contents of most recent Xorg X server log file (/home/martin/.local/share/xorg/Xorg.0.log): --- [ 11955.221] (--) Log file renamed from "/home/martin/.local/share/xorg/Xorg.pid-13984.log" to "/home/martin/.local/share/xorg/Xorg.0.log" [ 11955.221] X.Org X Server 1.19.2 Release Date: 2017-03-02 [ 11955.221] X Protocol Version 11, Revision 0 [ 11955.221] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [ 11955.221] Current Operating System: Linux iof-yoga 4.9.0-2-amd64 #1 SMP Debian 4.9.18-1 (2017-03-30) x86_64 [ 11955.221] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-2-amd64 root=UUID=f7481dda-9f66-41a2-a09b-b9f8327e2f88 ro quiet [ 11955.221] Build Date: 03 March 2017 03:14:41PM [ 11955.221] xorg-server 2:1.19.2-1 (https://www.debian.org/support) [ 11955.221] Current version of pixman: 0.34.0 [ 11955.221]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 11955.221] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 11955.222] (==) Log file: "/home/martin/.local/share/xorg/Xorg.0.log", Time: Fri Jun 9 12:27:19 2017 [ 11955.222] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 11955.222] (==) No Layout section. Using the first Screen section. [ 11955.222] (==) No screen section available. Using defaults. [ 11955.222] (**) |-->Screen "Default Screen Section" (0) [ 11955.222] (**) | |-->Monitor "" [ 11955.222] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 11955.222] (==) Automatically adding devices [ 11955.222] (==) Automatically enabling devices [ 11955.222] (==) Automatically adding GPU devices [ 11955.222] (==) Max clients allowed: 256, resource mask: 0x1f [ 11955.222] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 11955.222]Entry deleted from font path. [ 11955.222] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 11955.222] (==) ModulePath set to "/usr/lib/xorg/modules" [ 11955.222] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 11955.222] (II) Loader magic: 0x55cedebaee00 [ 11955.222] (II) Module ABI versions: [ 11955.222]X.Org ANSI C Emulation: 0.4 [ 11955.222]X.Org Video Driver: 23.0 [ 11955.222]X.Org XInput driver : 24.1 [ 11955.222]X.Org Server Extension : 10.0 [ 11955.224] (++) using VT number 2 [ 11955.226] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_310 [ 11955.227] (II) xfree86: Adding drm device (/dev/dri/card0) [ 11955.227] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 12 paused 0 [ 11955.229] (--) PCI:*(0:0:2:0) 8086:5916:17aa:39f3 rev 2, Mem @ 0xb000/16777216, 0xa000/268435456, I/O @ 0
Bug#651399: Xdmx segfault on start
Hello, I just a confirm the bug. On google groups i found a thread about the problem [1]. After i apply the patch [2] the problem is solved on my Host. [1] https://groups.google.com/forum/embed/#!topic/linux.debian.maint.x/ee7i6iVqT3c [2] https://cgit.freedesktop.org/xorg/xserver/commit/?id=21eda7464d0e13ac6558edaf6531c3d3251e05df Regards Martin
Bug#865113: xserver-xorg-core: X freezes on startup with segmentation fault after upgrade from jessie to stretch
Package: xserver-xorg-core Version: 2:1.19.2-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I upgraded from jessie to stretch. After the upgrade I cannot use X anymore. Normally I work on the framebuffer-console. When I need X I start it with startx. My wm is IceWM. In jessie this worked fine. In stretch the screen of IceWM and the mouse pointer appear and then the whole computer seems to freeze. It doesn't react on the keyboard or mouse-button. It is a IBM Thinkpad X40. * What exactly did you do (or not do) that was effective (or ineffective)? On the machine with the problem I can't do anything but pressing the power-button to shut down and start again. >From another machine I can ssh on the machine with the problem, kill xinit and then I can return to the machine and work on it like before. After I installed XOrg from jessie (by downgrade), X worked perfectly. When I install XOrg from stretch again, I get the same problems. I checked the RAM with memtest86+ and got no errors. * What was the outcome of this action? The bug persists and is reproducible. I found a similar bug in: <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844523> but I am not sure if it is the same. My hardware is different and in my case I cannot work on X at all. * What outcome did you expect instead? I would be great if you can fix it. Thank you! If you need any more information, please let me know. Thank you very much Martin -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 02) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 3.16.0-4-586 (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 Debian 3.16.43-2 (2017-04-30) Xorg X server log files on system: -- -rw-r--r-- 1 martinkl martinkl 12107 Jun 18 22:43 /home/martinkl/.local/share/xorg/Xorg.0.log -rw-r--r-- 1 root root 6223 Jun 19 10:34 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 9132.711] X.Org X Server 1.19.2 Release Date: 2017-03-02 [ 9132.727] X Protocol Version 11, Revision 0 [ 9132.731] Build Operating System: Linux 3.16.0-4-amd64 i686 Debian [ 9132.734] Current Operating System: Linux maurice 3.16.0-4-586 #1 Debian 3.16.43-2 (2017-04-30) i686 [ 9132.734] Kernel command line: BOOT_IMAGE=Linux ro root=801 [ 9132.741] Build Date: 03 March 2017 03:15:35PM [ 9132.745] xorg-server 2:1.19.2-1 (https://www.debian.org/support) [ 9132.749] Current version of pixman: 0.34.0 [ 9132.756]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 9132.756] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 9132.770] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jun 19 10:34:02 2017 [ 9132.770] (II) Loader magic: 0x802b6720 [ 9132.771] (II) Module ABI versions: [ 9132.771]X.Org ANSI C Emulation: 0.4 [ 9132.771]X.Org Video Driver: 23.0 [ 9132.771]X.Org XInput driver : 24.1 [ 9132.771]X.Org Server Extension : 10.0 [ 9132.772] (--) using VT number 7 [ 9132.772] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 9132.773] (II) xfree86: Adding drm device (/dev/dri/card0) [ 9132.775] (--) PCI:*(0:0:2:0) 8086:3582:1014:0557 rev 2, Mem @ 0xe000/134217728, 0xd000/524288, I/O @ 0x1800/8 [ 9132.775] (--) PCI: (0:0:2:1) 8086:3582:1014:0557 rev 2, Mem @ 0xe800/134217728, 0xd008/524288 [ 9132.779] List of video drivers: [ 9132.783]modesetting [ 9132.786]intel [ 9132.786] (II) LoadModule: "modesetting" [ 9132.787] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 9132.787] (II) Module modesetting: vendor="X.Org Foundation" [ 9132.787]compiled for 1.19.2, module version = 1.19.2 [ 9132.787]Module class: X.Org Video Driver [ 9132.787]ABI class: X.Org Video Driver, version 23.0 [ 9132.787] (II) LoadModule: "intel" [ 9132.787] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so [ 9132.841] (II) Module intel: vendor="X.Org Foundation" [ 9132.841]compiled for 1.19.0, module version = 2.99.917 [ 9132.841]Module class
Bug#858322: Please integrate a document
Package: x11-xkb-utils Version: 7.7+3+b1 Severity: wishlist I kinda want to get rid of http://madduck.net/docs/extending-xkb/ (along with my entire webserver). It gets a lot of access (from Debian machines, according to access.log), and I think it'd be best included in the package, or pushed upstream if they care. I'd put it under whatever licence suits, and please let me know what format you prefer. It's Markdown right now. Thanks for your consideration! -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages x11-xkb-utils depends on: ii libc62.24-9 ii libx11-6 2:1.6.4-3 ii libxaw7 2:1.0.13-1 ii libxkbfile1 1:1.0.9-2 ii libxt6 1:1.1.5-1 x11-xkb-utils recommends no packages. x11-xkb-utils suggests no packages. -- no debconf information -- .''`. martin f. krafft <madduck@d.o> @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#856662: xorg: starting X within X without specifying -vt destroys current X session
Hello Adrian, not sure what happened, but something changed the last few days, maybe due to an update. (Latest update was small: libpgm-5.2-0 libwxbase3.0-0v5 libwxgtk3.0-0v5 libzmq5 orage. I'm not sure if I had more updates in the meantime) I've had the described bug, but now I get the same error messages as you without crashing X on display :0. Before sending this bug report, I did further tests in virtualbox. The bug still persists in VirtualBox with guest additions installed. It is gone in virtualbox _without_ guest additions, and it does not happen on my host machine anymore. > You are basically trying to shoot yourself into the foot and you are > surprised that you get hit. :) Nice said. Those command has been possible in debian jessie, stretch behaves different. For example, in jessie I can use vt8...vt12, but not in stretch. But that is another story ... Not sure if this is related: Now, if running several X servers on tty1...tty6 with xinit xterm -- :1 vt1 ... xinit xterm -- :6 vt6 my desktop session (xfce) on display :0 returns to lightdm login after some switching between ttys. Thanks, Martin
Bug#812791: xserver-xorg-core: Kills DM controlled session when opening X from another tty
On Tue, Oct 04, 2016 at 11:43:07AM +0200, Agustin Martin wrote: > On Wed, Sep 07, 2016 at 12:08:15PM +0200, Agustin Martin wrote: > > On Wed, Jan 27, 2016 at 03:51:22PM +0100, Agustin Martin wrote: > > > On Wed, Jan 27, 2016 at 08:29:21AM +0100, Julien Cristau wrote: > > > > On Tue, Jan 26, 2016 at 16:51:27 +0100, Agustin Martin wrote: > > > > > > > > > Package: xserver-xorg-core > > > > > Version: 2:1.17.3-2 > > > > > Severity: normal > > > > > > > > > > Dear Maintainers, > > > > > > > > > > I am having a strange problem apparently starting with 2:1.17.2-3. > > > > > > > > > > I often have a display-manager controlled X session for one user and > > > > > open > > > > > another X session in a free tty for a different user with startx. > > > > > > > > > > This has been working for a long time. However, after a recent testing > > > > > upgrade including xserver-xorg-core 2:1.17.2-3 this started to fail > > > > > (failure happened before in a sid box, but there were more upgrades to > > > > > look when trying to locate which change might be responsible). > > > > > > > > > > When I have a display-mamager controlled X session and, without > > > > > leaving the > > > > > session, switch to a free tty, login as another user and start an X > > > > > session > > > > > with startx original X session gets killed and I am sent to DM > > > > > greeter. > > > > > > > > > Please provide the log from both X processes. > > > > > > Hi, thanks for quick reply. > > > > > > Please find them attached. > > > > Hi, > > > > Just to add some additional info. This problem is happening not only with > > the xserver-xorg-video-nouveau driver, but also if I remove it leaving the > > fbdev > > or vesa drivers. Hi, some funny info about this problem, I am using a sysvinit box and it is currently suffering from https://bugs.debian.org/844785 [systemd-shim not fully compatible with systemd 232] and similar bugs against lightdm #770885 lightdm: Restart, Suspend, Hibernate, Shut Down all greyed out and nonfunctional #804165 lightdm: Options reboot,suspend,hibernate are all greyed out The funny thing is that as soon as this systemd-shim bug reappeared my original problem reported in this bug #812791 report become no longer present when using "sysvinit"+"buggy systemd-shim". I have booted with systemd to see what happens and my original problem reappeared, cannot switch. So, this may be related to interaction with policykit or friends, but apart from that guess I am clueless. Regards, -- Agustin
Bug#812791: xserver-xorg-core: Kills DM controlled session when opening X from another tty
On Tue, Oct 04, 2016 at 11:43:07AM +0200, Agustin Martin wrote: > Package: xserver-xorg-core > Version: 2:1.17.3-2 > Severity: normal > > Dear Maintainers, > > I am having a strange problem apparently starting with 2:1.17.2-3. > > I often have a display-manager controlled X session for one user and open > another X session in a free tty for a different user with startx. > > This has been working for a long time. However, after a recent testing > upgrade including xserver-xorg-core 2:1.17.2-3 this started to fail > (failure happened before in a sid box, but there were more upgrades to > look when trying to locate which change might be responsible). > > When I have a display-mamager controlled X session and, without leaving the > session, switch to a free tty, login as another user and start an X session > with startx original X session gets killed and I am sent to DM greeter. Hi, I could also reproduce this problem in a i5 laptop with integrated intel card, so this seems not related to a particular issue with Nvidia cards. xserver-xorg-legacy is installed and Xwrapper.config contains allowed_users=console needs_root_rights=yes Xorg.log files showing the failure are attached, both with none of fbdev+vesa+intel xorg drivers installed and with all of them (intel seems not used). Regards, Additional information follows: Versions of used packages: -- xserver-xorg: 1:7.7+16 xserver-xorg-core: 2:1.18.4-2 xserver-xorg-legacy: 2:1.18.4-2 xserver-xorg-video-fbdev: 1:0.4.4-1+b4 xserver-xorg-video-intel: 2:2.99.917+git20160706-1 xserver-xorg-video-vesa: 1:2.3.4-1+b1 (see some auto-retrieved versions at the end of the message) X server symlink status: lrwxrwxrwx 1 root root 13 Sep 25 2013 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 Sep 6 15:09 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 4.7.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.1 20160904 (Debian 5.4.1-2) ) #1 SMP Debian 4.7.8-1 (2016-10-19) DRM Information from dmesg: --- [2.053999] Linux agpgart interface v0.103 [ 42.962476] [drm] Initialized drm 1.1.0 20060810 [ 43.582387] [drm] Memory usable by graphics device = 2048M [ 43.582391] [drm] Replacing VGA console driver [ 43.588324] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 43.588327] [drm] Driver supports precise vblank timestamp query. [ 43.880196] fbcon: inteldrmfb (fb0) is primary device [ 44.919349] [drm] Initialized i915 1.6.0 20160425 for :00:02.0 on minor 0 [ 44.924531] i915 :00:02.0: fb0: inteldrmfb frame buffer device -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages xserver-xorg-core depends on: ii keyboard-configuration1.152 ii libaudit1 1:2.6.7-1 ii libc6 2.24-3 ii libdbus-1-3 1.10.12-1 ii libdrm2 2.4.71-1 ii libegl1-mesa 12.0.3-1 ii libepoxy0 1.3.1-1 ii libgbm1 12.0.3-1 ii libgcrypt20 1.7.3-2 ii libgl1-mesa-glx [libgl1] 12.0.3-1 ii libpciaccess0 0.13.4-1 ii libpixman-1-0 0.34.0-1 ii libselinux1 2.5-3 ii libsystemd0 231-9 ii libudev1 231-9 ii libxau6 1:1.0.8-1 ii libxdmcp6 1:1.1.2-1.1 ii libxfont1 1:1.5.2-1 ii libxshmfence1 1.2-1 ii udev 231-9 ii xserver-common2:1.18.4-2 Versions of packages xserver-xorg-core recommends: ii libgl1-mesa-dri 12.0.3-1 ii libpam-systemd 231-9 Versions of packages xserver-xorg-core suggests: ii xfonts-100dpi1:1.0.4+nmu1 ii xfonts-75dpi 1:1.0.4+nmu1 ii xfonts-scalable 1:1.0.3-1.1 -- Agustin [67.291] X.Org X Server 1.18.4 Release Date: 2016-07-19 [67.291] X Protocol Version 11, Revision 0 [67.291] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [67.291] Current Operating System: Linux lenovo-testing 4.7.0-1-amd64 #1 SMP Debian 4.7.8-1 (2016-10-19) x86_64 [67.291] Kernel command line: BOOT_IMAGE=/vmlinuz-4.7.0-1-amd64 root=/dev/mapper/debian-testing ro quiet [67.291] Build Date: 06 September
Bug#644838: xserver-xorg-video-nouveau: X lockup, DRM reports "fail ttm_validate" and DMA_W_PROTECTION fault
Package: xserver-xorg-video-nouveau Version: 1:1.0.13-1 Followup-For: Bug #644838 This issues still exists in Testing. It regularly makes gnome-session take up to 50% of available memory, at which point the desktop session completely freezes for a few minutes. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Aug 17 2014 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 Sep 6 16:09 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:05.0 VGA compatible controller [0300]: NVIDIA Corporation C51 [GeForce 6150 LE] [10de:0241] (rev a2) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 4.7.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.1 20160904 (Debian 5.4.1-2) ) #1 SMP Debian 4.7.6-1 (2016-10-07) Xorg X server log files on system: -- -rw-r--r-- 1 root root 40128 Oct 11 17:42 /var/log/Xorg.0.log -rw-r--r-- 1 perkelix perkelix 70416 Oct 21 12:15 /home/perkelix/.local/share/xorg/Xorg.0.log Contents of most recent Xorg X server log file (/home/perkelix/.local/share/xorg/Xorg.0.log): - [ 160.238] (--) Log file renamed from "/home/perkelix/.local/share/xorg/Xorg.pid-1135.log" to "/home/perkelix/.local/share/xorg/Xorg.0.log" [ 160.239] X.Org X Server 1.18.4 Release Date: 2016-07-19 [ 160.242] X Protocol Version 11, Revision 0 [ 160.242] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [ 160.242] Current Operating System: Linux media 4.7.0-1-amd64 #1 SMP Debian 4.7.6-1 (2016-10-07) x86_64 [ 160.242] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.7.0-1-amd64 root=UUID=e430a8a8-229e-4696-a3a6-6929d945a22c ro panic=15 iommu=noagp nouveau.config=NvMSI=0 video=TV-1:d quiet splash [ 160.243] Build Date: 06 September 2016 01:32:44PM [ 160.243] xorg-server 2:1.18.4-2 (https://www.debian.org/support) [ 160.243] Current version of pixman: 0.34.0 [ 160.243]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 160.243] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 160.243] (==) Log file: "/home/perkelix/.local/share/xorg/Xorg.0.log", Time: Fri Oct 21 11:36:02 2016 [ 160.269] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 160.303] (==) No Layout section. Using the first Screen section. [ 160.303] (==) No screen section available. Using defaults. [ 160.303] (**) |-->Screen "Default Screen Section" (0) [ 160.304] (**) | |-->Monitor "" [ 160.331] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 160.331] (==) Automatically adding devices [ 160.331] (==) Automatically enabling devices [ 160.331] (==) Automatically adding GPU devices [ 160.331] (==) Max clients allowed: 256, resource mask: 0x1f [ 160.331] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 160.331]Entry deleted from font path. [ 160.331] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [ 160.331]Entry deleted from font path. [ 160.331] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [ 160.332]Entry deleted from font path. [ 160.332] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist. [ 160.332]Entry deleted from font path. [ 160.332] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [ 160.332]Entry deleted from font path. [ 160.332] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [ 160.332]Entry deleted from font path. [ 160.332] (==) FontPath set to: /usr/share/fonts/X11/misc, built-ins [ 160.332] (==) ModulePath set to "/usr/lib/xorg/modules" [ 160.332] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 160.332] (II) Loader magic: 0x563cf1284dc0 [ 160.332] (II) Module ABI versions: [ 160.333]X.Org ANSI C Emulation: 0.4 [ 160.333]X.Org Video Driver: 20.0 [ 160.333]X.Org XInput driver : 22.1 [ 160.333]X.Org Server Extension : 9.0 [ 160.337] (++) using VT number 3 [ 160.364] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_32 [ 160.365] (II) xfree86: Adding drm device (/dev/dri/card0) [ 160.387] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 9 paused 0 [ 160.390] (--) PCI:*(0:0:5:0) 10de:0241:103c:2a34 rev 162, Mem @ 0xfc00/16777216, 0xe000/268435456,
Bug#812791: xserver-xorg-core: Kills DM controlled session when opening X from another tty
On Wed, Sep 07, 2016 at 12:08:15PM +0200, Agustin Martin wrote: > On Wed, Jan 27, 2016 at 03:51:22PM +0100, Agustin Martin wrote: > > On Wed, Jan 27, 2016 at 08:29:21AM +0100, Julien Cristau wrote: > > > On Tue, Jan 26, 2016 at 16:51:27 +0100, Agustin Martin wrote: > > > > > > > Package: xserver-xorg-core > > > > Version: 2:1.17.3-2 > > > > Severity: normal > > > > > > > > Dear Maintainers, > > > > > > > > I am having a strange problem apparently starting with 2:1.17.2-3. > > > > > > > > I often have a display-manager controlled X session for one user and > > > > open > > > > another X session in a free tty for a different user with startx. > > > > > > > > This has been working for a long time. However, after a recent testing > > > > upgrade including xserver-xorg-core 2:1.17.2-3 this started to fail > > > > (failure happened before in a sid box, but there were more upgrades to > > > > look when trying to locate which change might be responsible). > > > > > > > > When I have a display-mamager controlled X session and, without leaving > > > > the > > > > session, switch to a free tty, login as another user and start an X > > > > session > > > > with startx original X session gets killed and I am sent to DM greeter. > > > > > > > Please provide the log from both X processes. > > > > Hi, thanks for quick reply. > > > > Please find them attached. > > Hi, > > Just to add some additional info. This problem is happening not only with > the xserver-xorg-video-nouveau driver, but also if I remove it leaving the > fbdev > or vesa drivers. Forgot to mention that this also happens without any of those (nouveau, vesa, fbdev) drivers installed, log attached Regards, -- Agustin [86.097] X.Org X Server 1.18.4 Release Date: 2016-07-19 [86.097] X Protocol Version 11, Revision 0 [86.097] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [86.097] Current Operating System: Linux mala-sid 4.7.0-1-amd64 #1 SMP Debian 4.7.2-1 (2016-08-28) x86_64 [86.097] Kernel command line: BOOT_IMAGE=/vmlinuz-4.7.0-1-amd64 root=/dev/mapper/debian-sid ro quiet [86.097] Build Date: 06 September 2016 01:32:44PM [86.097] xorg-server 2:1.18.4-2 (https://www.debian.org/support) [86.097] Current version of pixman: 0.33.6 [86.097]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [86.097] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [86.097] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Sep 9 10:36:00 2016 [86.113] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [86.236] (==) No Layout section. Using the first Screen section. [86.236] (==) No screen section available. Using defaults. [86.236] (**) |-->Screen "Default Screen Section" (0) [86.236] (**) | |-->Monitor "" [86.258] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [86.258] (==) Automatically adding devices [86.258] (==) Automatically enabling devices [86.258] (==) Automatically adding GPU devices [86.258] (==) Max clients allowed: 256, resource mask: 0x1f [86.403] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [86.403]Entry deleted from font path. [86.465] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [86.466] (==) ModulePath set to "/usr/lib/xorg/modules" [86.466] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [86.488] (II) Loader magic: 0x558d0b61fdc0 [86.488] (II) Module ABI versions: [86.488]X.Org ANSI C Emulation: 0.4 [86.488]X.Org Video Driver: 20.0 [86.488]X.Org XInput driver : 22.1 [86.488]X.Org Server Extension : 9.0 [86.489] (++) using VT number 7 [86.489] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [86.490] (II) xfree86: Adding drm device (/dev/dri/card0) [86.492] (--) PCI:*(0:1:0:0) 10de:104a:1043:8460 rev 161, Mem @ 0xfd00
Bug#812791: xserver-xorg-core: Kills DM controlled session when opening X from another tty
On Wed, Jan 27, 2016 at 03:51:22PM +0100, Agustin Martin wrote: > On Wed, Jan 27, 2016 at 08:29:21AM +0100, Julien Cristau wrote: > > On Tue, Jan 26, 2016 at 16:51:27 +0100, Agustin Martin wrote: > > > > > Package: xserver-xorg-core > > > Version: 2:1.17.3-2 > > > Severity: normal > > > > > > Dear Maintainers, > > > > > > I am having a strange problem apparently starting with 2:1.17.2-3. > > > > > > I often have a display-manager controlled X session for one user and open > > > another X session in a free tty for a different user with startx. > > > > > > This has been working for a long time. However, after a recent testing > > > upgrade including xserver-xorg-core 2:1.17.2-3 this started to fail > > > (failure happened before in a sid box, but there were more upgrades to > > > look when trying to locate which change might be responsible). > > > > > > When I have a display-mamager controlled X session and, without leaving > > > the > > > session, switch to a free tty, login as another user and start an X > > > session > > > with startx original X session gets killed and I am sent to DM greeter. > > > > > Please provide the log from both X processes. > > Hi, thanks for quick reply. > > Please find them attached. Hi, Just to add some additional info. This problem is happening not only with the xserver-xorg-video-nouveau driver, but also if I remove it leaving the fbdev or vesa drivers. This does not always happen in first switch, sometimes more switches are needed, seems some sort of race condition. Attached logs for both failures. /etc/X11/Xwrapper.config contains "needs_root_rights=yes" and xserver-xorg-legacy is installed. Versions: xserver-xorg-video-fbdev: 1:0.4.4-1+b4 xserver-xorg-video-vesa: 1:2.3.4-1+b1 Regards, -- Agustin [86.058] X.Org X Server 1.18.4 Release Date: 2016-07-19 [86.058] X Protocol Version 11, Revision 0 [86.058] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [86.058] Current Operating System: Linux mala-sid 4.7.0-1-amd64 #1 SMP Debian 4.7.2-1 (2016-08-28) x86_64 [86.058] Kernel command line: BOOT_IMAGE=/vmlinuz-4.7.0-1-amd64 root=/dev/mapper/debian-sid ro quiet [86.058] Build Date: 20 July 2016 05:14:41AM [86.058] xorg-server 2:1.18.4-1 (http://www.debian.org/support) [86.058] Current version of pixman: 0.33.6 [86.058]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [86.058] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [86.058] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Sep 5 18:04:52 2016 [86.102] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [86.184] (==) No Layout section. Using the first Screen section. [86.184] (==) No screen section available. Using defaults. [86.184] (**) |-->Screen "Default Screen Section" (0) [86.184] (**) | |-->Monitor "" [86.199] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [86.199] (==) Automatically adding devices [86.199] (==) Automatically enabling devices [86.199] (==) Automatically adding GPU devices [86.199] (==) Max clients allowed: 256, resource mask: 0x1f [86.340] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [86.340]Entry deleted from font path. [86.469] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [86.469] (==) ModulePath set to "/usr/lib/xorg/modules" [86.469] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [86.493] (II) Loader magic: 0x56340226cdc0 [86.493] (II) Module ABI versions: [86.493]X.Org ANSI C Emulation: 0.4 [86.493]X.Org Video Driver: 20.0 [86.493]X.Org XInput driver : 22.1 [86.493]X.Org Server Extension : 9.0 [86.494] (++) using VT number 7 [86.494] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [86.494] (II) xfree86: Adding drm device (/dev/dri/card0) [86.497] (--) PCI:*(0:1:0:0) 10de:104a:1043:8460 rev 161, Mem @ 0xfd00/16777216, 0xf000/134217728, 0xf800/33554432, I
Bug#832560: xserver-xorg-core: performance is very bad since using built-in modesetting 4th gen GMA on ivy bridge
Am 02.08.2016 um 20:53 schrieb Julien Cristau: > Please show the output of dpkg -l '*mesa*', you seem to have some bits > from experimental, but possibly not all that's needed. And please > attach your X log (after removing xorg.conf again), which should be in > ~/.local/share/xorg. Ok, it seems like libgbm1 was not yet installed from experimental which i did now. Now it looks like this: > dpkg -l '*mesa*' > Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten > | Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/ > Halb installiert/Trigger erWartet/Trigger anhängig > |/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht) > ||/ NameVersion Architektur Beschreibung > +++-===---=== > ii libegl1-mesa:amd64 12.0.1-3 amd64free > implementation of the EGL API -- runtime > un libegl1-mesa-drivers(keine > Beschreibung vorhanden) > ii libgl1-mesa-dri:amd64 12.0.1-3 amd64free > implementation of the OpenGL API -- DRI module > ii libgl1-mesa-dri:i38612.0.1-3 i386 free > implementation of the OpenGL API -- DRI module > un libgl1-mesa-dri-experim (keine > Beschreibung vorhanden) > ii libgl1-mesa-glx:amd64 12.0.1-3 amd64free > implementation of the OpenGL API -- GLX runtim > ii libgl1-mesa-glx:i38612.0.1-3 i386 free > implementation of the OpenGL API -- GLX runtim > ii libglapi-mesa:amd64 12.0.1-3 amd64free > implementation of the GL API -- shared library > ii libglapi-mesa:i386 12.0.1-3 i386 free > implementation of the GL API -- shared library > ii libgles1-mesa:amd64 12.0.1-3 amd64free > implementation of the OpenGL|ES 1.x API -- run > ii libgles2-mesa:amd64 12.0.1-3 amd64free > implementation of the OpenGL|ES 2.x API -- run > ii libglu1-mesa:amd64 9.0.0-2.1amd64Mesa OpenGL > utility library (GLU) > ii libwayland-egl1-mesa:am 12.0.1-3 amd64implementation > of the Wayland EGL platform -- runti > ii mesa-utils 8.3.0-1 amd64Miscellaneous > Mesa GL utilities > ii mesa-utils-extra8.3.0-1 amd64Miscellaneous > Mesa utilies (opengles, egl) > ii mesa-va-drivers:amd64 12.0.1-3 amd64Mesa VA-API > video acceleration drivers > ii mesa-vdpau-drivers:amd6 12.0.1-3 amd64Mesa VDPAU > video acceleration drivers > ii mesa-vulkan-drivers 12.0.1-3 amd64Mesa Vulkan > graphics drivers > un mesag3 (keine > Beschreibung vorhanden) > un xlibmesa3 (keine > Beschreibung vorhanden) Right now I can't afford restarting X but I'll do later and have a look if it will work now. Best regards, Martin signature.asc Description: OpenPGP digital signature
Bug#832560: xserver-xorg-core: performance is very bad since using built-in modesetting 4th gen GMA on ivy bridge
Hello, after I saw reportbug wasn't able to read the xorg.conf I changed the permissions to 640 and it works again. It was not mentioned in the maintainers email that the file requires reading permission for everyone. So by just copying the file my UMASk set the permission to 640. But for Ivy Bridge you shouldn't switch away from intel driver as this was really slowing down my system. Best regards, Martin signature.asc Description: OpenPGP digital signature
Bug#832560: xserver-xorg-core: performance is very bad since using built-in modesetting 4th gen GMA on ivy bridge
Package: xserver-xorg-core Version: 2:1.18.4-1 Severity: important Dear Maintainer, since the last update my systems performance is very low. Even gnome shell animations like are "stuttering". Playing games is no more possible of cause. With the update I got this mail: > xorg-server (2:1.18.3-2) unstable; urgency=medium > > X now defaults to using built-in modesetting video driver on Intel > hardware which is "4th gen GMA" and newer, so roughly speaking on hardware > from 2007 and up. If this triggers new bugs on your hw, please file them > against the xserver. > > Continuing to use the -intel driver is possible by dropping the template > xorg.conf to /etc/X11: > > # cp /usr/share/doc/xserver-xorg-video-intel/xorg.conf /etc/X11 > > -- Timo Aaltonen <tjaal...@debian.org> Tue, 19 Jul 2016 04:28:05 +0300 But this xorg.conf shows no effect after restarting X and even after complete reboot. There is also some weird output of VMWare in glxinfo: > glxinfo | grep OpenGL > OpenGL vendor string: VMware, Inc. > OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) > OpenGL core profile version string: 3.3 (Core Profile) Mesa 12.0.1 > OpenGL core profile shading language version string: 3.30 > OpenGL core profile context flags: (none) > OpenGL core profile profile mask: core profile > OpenGL core profile extensions: > OpenGL version string: 3.0 Mesa 12.0.1 > OpenGL shading language version string: 1.30 > OpenGL context flags: (none) > OpenGL extensions: > OpenGL ES profile version string: OpenGL ES 3.0 Mesa 12.0.1 > OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 > OpenGL ES profile extensions: Compared to the old output before: 1,2c1,2 < OpenGL vendor string: Intel Open Source Technology Center < OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile --- > OpenGL vendor string: VMware, Inc. > OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) Feel free to ask for mor information needed to investigate in this issue. Best regards, Martin -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) Xorg X server configuration file status: -rw-r- 1 root root 92 Jul 26 22:57 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: --- /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 4.6.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.0 20160609 (Debian 5.4.0-6) ) #1 SMP Debian 4.6.4-1 (2016-07-18) No Xorg X server log files found. udev information: - P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input14 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input14 E: EV=3 E: ID_FOR_SEAT=input-acpi-LNXPWRBN_00 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXPWRBN:00 E: ID_PATH_TAG=acpi-LNXPWRBN_00 E: KEY=10 0 E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw E: NAME="Power Button" E: PHYS="LNXPWRBN/button/input0" E: PRODUCT=19/0/1/0 E: PROP=0 E: SUBSYSTEM=input E: TAGS=:seat: E: USEC_INITIALIZED=10945123 P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input14/event6 N: input/event6 E: BACKSPACE=guess E: DEVNAME=/dev/input/event6 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input14/event6 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXPWRBN:00 E: ID_PATH_TAG=acpi-LNXPWRBN_00 E: LIBINPUT_DEVICE_GROUP=19/0/1/0:LNXPWRBN/button E: MAJOR=13 E: MINOR=70 E: SUBSYSTEM=input E: TAGS=:power-switch: E: USEC_INITIALIZED=11045678 E: XKBLAYOUT=de E: XKBMODEL=pc105 P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input16 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input16 E: EV=3 E: ID_FOR_SEAT=input-acpi-LNXVIDEO_00 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXVIDEO:00 E: ID_PATH_TAG=acpi-LNXVIDEO_00 E: KEY=3e000b 0 0 0 E: MODALIAS=input:b0019vp0006e-e0,1,kE0,E1,E3,F1,F2,F3,F4,F5,ramlsfw E: NAME="Video Bus" E: PHYS="LNXVIDEO/video/input0" E: PRODUCT=19/0/6/0 E: PROP=0 E: SUBSYSTEM=input E: TAGS=:seat: E: USEC_INITIALIZED=10981552 P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input16/event8 N: input/event8 E: BACKSPACE=guess E: DEVNAME=/dev/input/event8 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input16/event8 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXVIDEO:00 E: ID_PATH_TAG=acpi-LNXVIDEO_00 E: LIBINPUT_DEVICE_GROUP=19/0/6/0:LNXVID
Bug#831901: xserver-xorg-core: no hardware assisted 3D acceleration using modesetting driver on Sandybridge
Am Mittwoch, 20. Juli 2016, 22:12:48 CEST schrieb Andreas Boll: > On Wed, Jul 20, 2016 at 06:51:21PM +0200, Martin Steigerwald wrote: > > Package: xserver-xorg-core > > Version: 2:1.18.4-1 > > Severity: important > > > > Dear Timo, dear Maintainers, > > > > as apt-listchanges informed me that with newest X server modesetting > > driver > > is now default, I tried it. > > > > It basically works, but subjectively feels a bit more sluggish (expected, > > but read on why). > > > > > > But kwin_x11 doesn´t enable OpenGL compositor anymore but falls back to > > XRender: > > > > OpenGL vendor string: VMware, Inc. > > OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.8, > > 256 bits) OpenGL version string: 3.0 Mesa 12.0.1 > > OpenGL shading language version string: 1.30 > > Driver: LLVMpipe > > GPU class: Unknown > > OpenGL version: 3.0 > > GLSL version: 1.30 > > Mesa version: 12.0.1 > > X server version: 1.18.4 > > Linux kernel version: 4.7 > > Requires strict binding:yes > > GLSL shaders: yes > > Texture NPOT support: yes > > Virtual Machine:no > > kwin_core: OpenGL driver recommends XRender based compositing. Falling > > back to XRender. kwin_core: To overwrite the detection use the > > environment variable KWIN_COMPOSE kwin_core: For more information see > > http://community.kde.org/KWin/Environment_Variables#KWIN_COMPOSE > > kwin_core: Failed to initialize compositing, compositing disabled > > > > > > glxinfo agrees that LLVMpipe OpenGL renderer is active instead of the > > Intel mesa> > > driver: > > Vendor: VMware, Inc. (0x) > > Device: llvmpipe (LLVM 3.8, 256 bits) (0x) > > Version: 12.0.1 > > Accelerated: no > > Video memory: 15829MB > > Unified memory: no > > Preferred profile: core (0x1) > > Max core profile version: 3.3 > > Max compat profile version: 3.0 > > Max GLES1 profile version: 1.1 > > Max GLES[23] profile version: 3.0 > > > > > >From the Xorg log it looks like initialization of OpenGL based Glamor > > > > 2D acceleration also fails: > > > > [ 47090.425] (II) Loading sub module "glamoregl" > > [ 47090.425] (II) LoadModule: "glamoregl" > > [ 47090.425] (II) Loading /usr/lib/xorg/modules/libglamoregl.so > > [ 47090.432] (II) Module glamoregl: vendor="X.Org Foundation" > > [ 47090.432] »··compiled for 1.18.4, module version = 1.0.0 > > [ 47090.432] »··ABI class: X.Org ANSI C Emulation, version 0.4 > > [ 47090.432] (II) glamor: OpenGL accelerated X.org driver based. > > [ 47090.452] (EE) modeset(0): eglInitialize() failed > > [ 47090.452] (EE) modeset(0): glamor initialization failed > > Yep EGL failed to initialize. > > > snip > > > Versions of packages xserver-xorg-core depends on: > > ii keyboard-configuration1.147 > > ii libaudit1 1:2.6.5-1 > > ii libc6 2.23-2 > > ii libdbus-1-3 1.10.8-1 > > ii libdrm2 2.4.68-1 > > ii libegl1-mesa 12.0.1-3 > > ii libepoxy0 1.3.1-1 > > ii libgbm1 11.2.2-1 > > If you use mesa from experimental you need to upgrade all binary > packages of mesa. > Upgrading libgbm1 to version 12.0.1-3 should fix glamor and 3d acceleration. Thank you Andreas. Indeed. I wasn´t aware of libgbm1. Upgrading it to experimental fixes the issue for me. So feel free to close the bug report. > > ii libgcrypt20 1.7.2-2 > > ii libgl1-mesa-glx [libgl1] 12.0.1-3 > > ii libpciaccess0 0.13.4-1 > > ii libpixman-1-0 0.33.6-1 > > ii libselinux1 2.5-3 > > ii libsystemd0 230-7 > > ii libudev1 230-7 > > ii libxau6 1:1.0.8-1 > > ii libxdmcp6 1:1.1.2-1.1 > > ii libxfont1 1:1.5.1-1 > > ii libxshmfence1 1.2-1 > > ii udev 230-7 > > ii xserver-common2:1.18.4-1 > > > > Versions of packages xserver-xorg-core recommends: > > ii libgl1-mesa-dri 12.0.1-3 > > ii libpam-systemd 230-7 > > > > Versions of packages xserver-xorg-core suggests: > > ii xfonts-100dpi1:1.0.4+nmu1 > > ii xfonts-75dpi 1:1.0.4+nmu1 > > ii xfonts-scalable 1:1.0.3-1.1 > > > > -- no debconf information -- Martin
Bug#831901: xserver-xorg-core: no hardware assisted 3D acceleration using modesetting driver on Sandybridge
Package: xserver-xorg-core Version: 2:1.18.4-1 Severity: important Dear Timo, dear Maintainers, as apt-listchanges informed me that with newest X server modesetting driver is now default, I tried it. It basically works, but subjectively feels a bit more sluggish (expected, but read on why). But kwin_x11 doesn´t enable OpenGL compositor anymore but falls back to XRender: OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) OpenGL version string: 3.0 Mesa 12.0.1 OpenGL shading language version string: 1.30 Driver: LLVMpipe GPU class: Unknown OpenGL version: 3.0 GLSL version: 1.30 Mesa version: 12.0.1 X server version: 1.18.4 Linux kernel version: 4.7 Requires strict binding:yes GLSL shaders: yes Texture NPOT support: yes Virtual Machine:no kwin_core: OpenGL driver recommends XRender based compositing. Falling back to XRender. kwin_core: To overwrite the detection use the environment variable KWIN_COMPOSE kwin_core: For more information see http://community.kde.org/KWin/Environment_Variables#KWIN_COMPOSE kwin_core: Failed to initialize compositing, compositing disabled glxinfo agrees that LLVMpipe OpenGL renderer is active instead of the Intel mesa driver: Vendor: VMware, Inc. (0x) Device: llvmpipe (LLVM 3.8, 256 bits) (0x) Version: 12.0.1 Accelerated: no Video memory: 15829MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 3.3 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.0 >From the Xorg log it looks like initialization of OpenGL based Glamor 2D acceleration also fails: [ 47090.425] (II) Loading sub module "glamoregl" [ 47090.425] (II) LoadModule: "glamoregl" [ 47090.425] (II) Loading /usr/lib/xorg/modules/libglamoregl.so [ 47090.432] (II) Module glamoregl: vendor="X.Org Foundation" [ 47090.432] »··compiled for 1.18.4, module version = 1.0.0 [ 47090.432] »··ABI class: X.Org ANSI C Emulation, version 0.4 [ 47090.432] (II) glamor: OpenGL accelerated X.org driver based. [ 47090.452] (EE) modeset(0): eglInitialize() failed [ 47090.452] (EE) modeset(0): glamor initialization failed Expected results: Hardware assisted 3D acceleration works as usual if modesetting driver is new default. Switching back to my AccelMethod "uxa" based Intel driver xorg configuration snippet for now. Device is ThinkPad T520 with external 24 inch display from Fujitsu: # phoronix-test-suite system-info Phoronix Test Suite v5.2.1 System Information Hardware: Processor: Intel Core i5-2520M @ 3.20GHz (4 Cores), Motherboard: LENOVO 42433WG, Chipset: Intel 2nd Generation Core Family DRAM, Memory: 16384MB, Disk: 300GB INTEL SSDSA2CW30 + 480GB Crucial_CT480M50, Graphics: LLVMpipe, Audio: Conexant CX20590, Monitor: P24T-7 LED, Network: Intel 82579LM Gigabit Connection + Intel Centrino Advanced-N 6205 Software: OS: Debian unstable, Kernel: 4.7.0-rc5-tp520-btrfstrim+ (x86_64), Desktop: KDE Frameworks 5, Display Server: X Server 1.18.4, Display Driver: modesetting 1.18.4, OpenGL: 3.3 Mesa 12.0.1 Gallium 0.4, Compiler: GCC 6.1.1 20160705, File-System: btrfs, Screen Resolution: 3840x1080 Debian unstable as of basically now: # apt-show-versions | egrep "libgl1-mesa-dri:amd64|libdrm-intel1:amd64|xserver-xorg:amd64|xserver-xorg-core:amd64|kwin-x11:amd64" kwin-x11:amd64/sid 4:5.7.0-1 uptodate libdrm-intel1:amd64/sid 2.4.68-1 uptodate libgl1-mesa-dri:amd64/experimental 12.0.1-3 uptodate xserver-xorg:amd64/sid 1:7.7+16 uptodate xserver-xorg-core:amd64/sid 2:1.18.4-1 uptodate Thanks, Martin -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 May 19 2011 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 Jul 20 05:00 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 0 /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): ------- Linux version 4.7.0-rc5-tp520-btrfstrim+ (martin@merkaba) (gcc version 6.1.1 20160620 (Debian 6.1.1-7) ) #60 SMP PREEMPT Mon Jun 27 14:42:12 CEST 2016 Xorg X server log files on system: -- -rw-r--r-- 1 root root 34434 Feb 17 2014 /var/log/Xorg.3.log -rw-r--r-- 1 root root 76789 Feb 19 15:32 /var/log/Xorg.2.log -
Bug#828023: libdrm-tegra for arm64
Package: libdrm
Version: 2.4.68-1
Severity: wishlist
Tags: patch
Can you please build libdrm-tegra0 for arm64. NVIDIA has 64-bit ARM
Tegra CPUs (e.g. Tegra X1).
The attached patch works for me.
--
Martin Michlmayr
http://www.cyrius.com/
diff --git a/debian/control b/debian/control
index e81dff2..82f78e3 100644
--- a/debian/control
+++ b/debian/control
@@ -34,7 +34,7 @@ Depends:
libdrm-omap1 (= ${binary:Version}) [any-arm],
libdrm-freedreno1 (= ${binary:Version}) [any-arm arm64],
libdrm-exynos1 (= ${binary:Version}) [any-arm],
- libdrm-tegra0 (= ${binary:Version}) [any-arm],
+ libdrm-tegra0 (= ${binary:Version}) [any-arm arm64],
${misc:Depends},
Multi-Arch: same
Description: Userspace interface to kernel DRM services -- development files
@@ -274,7 +274,7 @@ Description: Userspace interface to exynos-specific kernel DRM services -- debug
This package provides the debugging symbols for the libdrm-exynos1 package.
Package: libdrm-tegra0
-Architecture: any-arm
+Architecture: any-arm arm64
Depends:
${shlibs:Depends},
${misc:Depends},
@@ -290,7 +290,7 @@ Description: Userspace interface to tegra-specific kernel DRM services -- runtim
Package: libdrm-tegra0-dbg
Section: debug
Priority: extra
-Architecture: any-arm
+Architecture: any-arm arm64
Depends:
libdrm-tegra0 (= ${binary:Version}),
${misc:Depends},
diff --git a/debian/rules b/debian/rules
index 2dd69bc..169f648 100755
--- a/debian/rules
+++ b/debian/rules
@@ -49,10 +49,18 @@ endif
ifeq ($(ARM), yes)
confflags += --enable-exynos-experimental-api
confflags += --enable-omap-experimental-api
- confflags += --enable-tegra-experimental-api
else
confflags += --disable-exynos-experimental-api
confflags += --disable-omap-experimental-api
+endif
+
+# Tegra is on arm and arm64
+ifneq (,$(filter arm arm64,$(DEB_HOST_ARCH_CPU)))
+ TEGRA = yes
+endif
+ifeq ($(TEGRA), yes)
+ confflags += --enable-tegra-experimental-api
+else
confflags += --disable-tegra-experimental-api
endif
@@ -96,6 +104,8 @@ endif
ifeq ($(ARM), yes)
dh_strip -plibdrm-omap1 --dbg-package=libdrm-omap1-dbg
dh_strip -plibdrm-exynos1 --dbg-package=libdrm-exynos1-dbg
+endif
+ifeq ($(TEGRA), yes)
dh_strip -plibdrm-tegra0 --dbg-package=libdrm-tegra0-dbg
endif
ifeq ($(FREEDRENO), yes)
@@ -116,6 +126,8 @@ endif
ifeq ($(ARM), yes)
dh_makeshlibs -plibdrm-omap1 -V'libdrm-omap1 (>= 2.4.38)' -- -c4
dh_makeshlibs -plibdrm-exynos1 -V'libdrm-exynos1 (>= 2.4.66)' -- -c4
+endif
+ifeq ($(TEGRA), yes)
dh_makeshlibs -plibdrm-tegra0 -V'libdrm-tegra0' -- -c4
endif
ifeq ($(FREEDRENO), yes)
Bug#823843: cinnamon-common: Touchpad setting "tap to click" stopped working
Package: xserver-xorg-input-synaptics Followup-For: Bug #823843 Dear Maintainer, i could solve this malfunction by uninstalling xserver-xorg-input-synaptics. After uninstalling tap-to-click works again and the touchpad settings reappear in gnome-settings. Best regards, Martin -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#823843: cinnamon-common: Touchpad setting "tap to click" stopped working
Package: xserver-xorg-input-synaptics Version: 1.8.3-2 Followup-For: Bug #823843 Dear Maintainer, tap-to-click also refuses working in my installation. Also scrolling by using the touchpad goes the other direction. I'm using Gnome3, so it seems it's not depending on Cinnamon. The scrolling direction I could change, but I didn't find a setting to reactivate tap-to-click and this makes my laptop nearly unusable as I first click several times until I realize I have to use the buttons now. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Apr 17 2015 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 Apr 5 09:05 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 4.5.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 20160528 (Debian 5.3.1-21) ) #1 SMP Debian 4.5.5-1 (2016-05-29) Xorg X server log files on system: -- -rw-r--r-- 1 root root 22824 Sep 1 2015 /var/log/Xorg.2.log -rw-r--r-- 1 root root 22565 Sep 1 2015 /var/log/Xorg.1.log -rw-r--r-- 1 root root 23569 Oct 28 2015 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [47.357] X.Org X Server 1.17.2 Release Date: 2015-06-16 [47.357] X Protocol Version 11, Revision 0 [47.357] Build Operating System: Linux 4.1.0 x86_64 Debian [47.357] Current Operating System: Linux schlepptop 4.2.0-1-amd64 #1 SMP Debian 4.2.1-2 (2015-09-27) x86_64 [47.357] Kernel command line: BOOT_IMAGE=/vmlinuz-4.2.0-1-amd64 root=/dev/mapper/schlepptop--vg-root ro quiet [47.357] Build Date: 11 August 2015 10:51:15AM [47.357] xorg-server 2:1.17.2-1.1 (http://www.debian.org/support) [47.357] Current version of pixman: 0.33.2 [47.357]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [47.357] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [47.358] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 28 11:15:57 2015 [48.137] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [48.140] (==) No Layout section. Using the first Screen section. [48.140] (==) No screen section available. Using defaults. [48.140] (**) |-->Screen "Default Screen Section" (0) [48.140] (**) | |-->Monitor "" [48.141] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [48.141] (==) Automatically adding devices [48.141] (==) Automatically enabling devices [48.141] (==) Automatically adding GPU devices [48.323] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [48.323]Entry deleted from font path. [48.397] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [48.397] (==) ModulePath set to "/usr/lib/xorg/modules" [48.397] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [48.615] (II) Loader magic: 0x562aa9ef4d40 [48.615] (II) Module ABI versions: [48.615]X.Org ANSI C Emulation: 0.4 [48.615]X.Org Video Driver: 19.0 [48.615]X.Org XInput driver : 21.0 [48.615]X.Org Server Extension : 9.0 [48.616] (II) xfree86: Adding drm device (/dev/dri/card0) [48.618] (--) PCI:*(0:0:2:0) 8086:0166:1558:1310 rev 9, Mem @ 0xf6c0/4194304, 0xe000/268435456, I/O @ 0xf000/64 [48.672] (II) LoadModule: "glx" [48.897] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [49.000] (II) Module glx: vendor="X.Org Foundation" [49.000]compiled for 1.17.2, module version = 1.0.0 [49.000]ABI class: X.Org Server Extension, version 9.0 [49.000] (==) AIGLX enabled [49.000] (==) Matched intel as autoconfigured driver 0 [49.000] (==) Matched intel as autoconfigured driver 1 [49.000] (==) Matched modesetting as autoconfigured driver 2 [49.000] (==) Matched fbdev as autoconfigured driver 3 [49.000] (==) Matched vesa as autoconfigured driver 4 [49.000] (==) Assigned the driver to the xf86ConfigLayout [49.000] (II) LoadModule:
Bug#808871: xserver-xorg-core: under Linux kernel >= 4.2: (EE) XKB: Could not invoke xkbcomp
Package: xserver-xorg-core Version: 2:1.18.0-3 Followup-For: Bug #808871 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 This isssue still exists under Xserver 1.18 running on top of kernel 4.3. - -- Package-specific info: X server symlink status: - lrwxrwxrwx 1 root root 13 Feb 3 2010 /etc/X11/X -> /usr/bin/Xorg - -rwxr-xr-x 1 root root 274 Jan 27 19:37 /usr/bin/Xorg VGA-compatible devices on PCI bus: - -- 00:01.1 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD] Geode LX Video [1022:2081] /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): - --- Linux version 4.3.0-1-686 (debian-ker...@lists.debian.org) (gcc version 5.3.1 20160114 (Debian 5.3.1-6) ) #1 SMP Debian 4.3.3-7 (2016-01-19) Xorg X server log files on system: - -- - -rw-r--r-- 1 root root 20705 Feb 3 19:20 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - - [ 311.653] X.Org X Server 1.18.0 Release Date: 2015-11-09 [ 311.658] X Protocol Version 11, Revision 0 [ 311.659] Build Operating System: Linux 3.16.0-4-amd64 i686 Debian [ 311.659] Current Operating System: Linux geode 4.3.0-1-686 #1 SMP Debian 4.3.3-7 (2016-01-19) i586 [ 311.659] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.3.0-1-686 root=UUID=97b2628b-28a5-49f2-85f7-495728b3bef8 ro panic=15 pnpbios=off boot_delay=1 quiet splash cs5535audio.ac97_quirk=1 [ 311.659] Build Date: 27 January 2016 05:35:14PM [ 311.659] xorg-server 2:1.18.0-3 (http://www.debian.org/support) [ 311.659] Current version of pixman: 0.33.6 [ 311.659]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 311.659] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 311.663] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Feb 3 19:20:22 2016 [ 311.714] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 311.782] (==) No Layout section. Using the first Screen section. [ 311.784] (==) No screen section available. Using defaults. [ 311.784] (**) |-->Screen "Default Screen Section" (0) [ 311.784] (**) | |-->Monitor "" [ 311.803] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 311.804] (==) Automatically adding devices [ 311.804] (==) Automatically enabling devices [ 311.804] (==) Automatically adding GPU devices [ 311.804] (==) Max clients allowed: 256, resource mask: 0x1f [ 311.862] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 311.862]Entry deleted from font path. [ 311.862] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [ 311.862]Entry deleted from font path. [ 311.862] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [ 311.863]Entry deleted from font path. [ 311.863] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist. [ 311.863]Entry deleted from font path. [ 311.863] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [ 311.863]Entry deleted from font path. [ 311.863] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [ 311.863]Entry deleted from font path. [ 311.863] (==) FontPath set to: /usr/share/fonts/X11/misc, built-ins [ 311.863] (==) ModulePath set to "/usr/lib/xorg/modules" [ 311.863] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 311.863] (II) Loader magic: 0x8031c700 [ 311.863] (II) Module ABI versions: [ 311.863]X.Org ANSI C Emulation: 0.4 [ 311.864]X.Org Video Driver: 20.0 [ 311.864]X.Org XInput driver : 22.1 [ 311.864]X.Org Server Extension : 9.0 [ 311.876] (++) using VT number 7 [ 311.930] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c52 [ 311.950] (--) PCI:*(0:0:1:1) 1022:2081:1509:801b rev 0, Mem @ 0xd000/268435456, 0xefff/16384, 0xeffec000/16384, 0xeffe8000/16384, 0xefff8000/16384 [ 311.964] (II) LoadModule: "glx" [ 312.020] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 312.183] (II) Module glx: vendor="X.Org Foundation" [ 312.184]compiled for 1.18.0, module version = 1.0.0 [ 312.186]ABI class: X.Org Server Extension, version 9.0 [ 312.187] (==) AIGLX enabled [ 312.187] (==) Matched geode as autoconfigured driver 0 [ 312.187] (==) Matched modesetting as autoconfigured driver 1 [ 312.187] (==) Matched fbdev as
Bug#812791: xserver-xorg-core: Kills DM controlled session when opening X from another tty
On Wed, Jan 27, 2016 at 08:29:21AM +0100, Julien Cristau wrote: > On Tue, Jan 26, 2016 at 16:51:27 +0100, Agustin Martin wrote: > > > Package: xserver-xorg-core > > Version: 2:1.17.3-2 > > Severity: normal > > > > Dear Maintainers, > > > > I am having a strange problem apparently starting with 2:1.17.2-3. > > > > I often have a display-manager controlled X session for one user and open > > another X session in a free tty for a different user with startx. > > > > This has been working for a long time. However, after a recent testing > > upgrade including xserver-xorg-core 2:1.17.2-3 this started to fail > > (failure happened before in a sid box, but there were more upgrades to > > look when trying to locate which change might be responsible). > > > > When I have a display-mamager controlled X session and, without leaving the > > session, switch to a free tty, login as another user and start an X session > > with startx original X session gets killed and I am sent to DM greeter. > > > Please provide the log from both X processes. Hi, thanks for quick reply. Please find them attached. DM (wdm in this case) is started at display 0, startx from tty is started at display 1 Xorg.1.log: Log for display 1, session started with startx -- :1 Xorg.0.log: Log for display 0 when user session has already been wrongly killed and DM greeter shown again. Xorg.0.log.old: Hopefully log for killed session at display 0. Did not notice before, but there is some possibly interesting info in it. - Unable to get master: Invalid argument - NOUVEAU(0): failed to set mode: Permission denied - Fatal server error: EnterVT failed for screen 0 - Error dropping master: -22(Invalid argument) ... xserver-xorg-legacy is installed for this test. Hope this helps, -- Agustin [ 1410.663] X.Org X Server 1.17.3 Release Date: 2015-10-26 [ 1410.663] X Protocol Version 11, Revision 0 [ 1410.663] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [ 1410.663] Current Operating System: Linux uguindo 4.3.0-1-amd64 #1 SMP Debian 4.3.3-7 (2016-01-19) x86_64 [ 1410.663] Kernel command line: BOOT_IMAGE=/vmlinuz-4.3.0-1-amd64 root=/dev/mapper/debian-testing ro quiet [ 1410.663] Build Date: 27 October 2015 11:41:02PM [ 1410.663] xorg-server 2:1.17.3-2 (http://www.debian.org/support) [ 1410.663] Current version of pixman: 0.33.6 [ 1410.663]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 1410.663] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 1410.663] (==) Log file: "/var/log/Xorg.1.log", Time: Wed Jan 27 15:28:33 2016 [ 1410.663] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 1410.664] (==) No Layout section. Using the first Screen section. [ 1410.664] (==) No screen section available. Using defaults. [ 1410.664] (**) |-->Screen "Default Screen Section" (0) [ 1410.664] (**) | |-->Monitor "" [ 1410.664] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 1410.664] (==) Automatically adding devices [ 1410.664] (==) Automatically enabling devices [ 1410.664] (==) Automatically adding GPU devices [ 1410.664] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 1410.664]Entry deleted from font path. [ 1410.664] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 1410.664] (==) ModulePath set to "/usr/lib/xorg/modules" [ 1410.664] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 1410.664] (II) Loader magic: 0x55c456ea7de0 [ 1410.664] (II) Module ABI versions: [ 1410.664]X.Org ANSI C Emulation: 0.4 [ 1410.664]X.Org Video Driver: 19.0 [ 1410.664]X.Org XInput driver : 21.0 [ 1410.664]X.Org Server Extension : 9.0 [ 1410.667] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_34 [ 1410.667] (II) xfree86: Adding drm device (/dev/dri/card0) [ 1410.668] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0 [ 1410.669] (--) PCI:*(0:1:0:0) 10de:104a:1043:8460 rev 161, Mem @ 0xfd00/16777216, 0xf000/134217728, 0xf800/33554432, I/O @ 0xe000/128, BIOS @ 0x/524288 [ 1410.669] (II) LoadModul
Bug#812791: xserver-xorg-core: Kills DM controlled session when opening X from another tty
Package: xserver-xorg-core Version: 2:1.17.3-2 Severity: normal Dear Maintainers, I am having a strange problem apparently starting with 2:1.17.2-3. I often have a display-manager controlled X session for one user and open another X session in a free tty for a different user with startx. This has been working for a long time. However, after a recent testing upgrade including xserver-xorg-core 2:1.17.2-3 this started to fail (failure happened before in a sid box, but there were more upgrades to look when trying to locate which change might be responsible). When I have a display-mamager controlled X session and, without leaving the session, switch to a free tty, login as another user and start an X session with startx original X session gets killed and I am sent to DM greeter. With 2:1.17.2-3 I was not even allowed to re-open a DM controlled session even if I close first the startx created X session. Seems that this is no longer happening and I can now re-enter but after some session switch original new DM controlled session gets killed. Tried with xdm, wdm and lightdm as DM and xfce4, icewm and openbox as sessions opened from the DM. With xfce4 session killing is faster, but it is killed anyway with the other. Tried with xserver-xorg-legacy and /etc/X11/Xwrapper.config containing needs_root_rights=yes allowed_users=console No luck, problem persists. No problem if I create different X sessions with startx from different ttys. If I downgrade xserver-xorg stuff to versions in wheezy/stable, problem seems to disappear. Also, note that I am using sysvinit in this box. No apparent errors in usual log files. auth.log just shows it as a normal logout. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Jun 4 2009 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 Oct 28 00:43 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 4.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 20160114 (Debian 5.3.1-6) ) #1 SMP Debian 4.3.3-7 (2016-01-19) DRM Information from dmesg: --- [0.00] AGP: No AGP bridge found [0.00] AGP: Checking aperture... [0.00] AGP: No AGP bridge found [0.00] AGP: Node 0: aperture [bus addr 0x-0x01ff] (32MB) [0.00] AGP: Your BIOS doesn't leave an aperture memory hole [0.00] AGP: Please enable the IOMMU option in the BIOS setup [0.00] AGP: This costs you 64MB of RAM [0.00] AGP: Mapping aperture over RAM [mem 0xd000-0xd3ff] (65536KB) [1.155897] PCI-DMA: Disabling AGP. [1.155979] PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture [1.182742] Linux agpgart interface v0.103 [ 23.916063] [drm] Initialized drm 1.1.0 20060810 [ 24.620545] nouveau :01:00.0: DRM: VRAM: 2048 MiB [ 24.620549] nouveau :01:00.0: DRM: GART: 1048576 MiB [ 24.620555] nouveau :01:00.0: DRM: TMDS table version 2.0 [ 24.620559] nouveau :01:00.0: DRM: DCB version 4.0 [ 24.620564] nouveau :01:00.0: DRM: DCB outp 00: 02000300 [ 24.620570] nouveau :01:00.0: DRM: DCB outp 01: 01000302 00020030 [ 24.620574] nouveau :01:00.0: DRM: DCB outp 02: 02011362 00020010 [ 24.620578] nouveau :01:00.0: DRM: DCB outp 03: 04022310 [ 24.620582] nouveau :01:00.0: DRM: DCB conn 00: 1030 [ 24.620585] nouveau :01:00.0: DRM: DCB conn 01: 2161 [ 24.620589] nouveau :01:00.0: DRM: DCB conn 02: 0200 [ 24.622677] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 24.622680] [drm] Driver supports precise vblank timestamp query. [ 24.677537] nouveau :01:00.0: DRM: MM: using COPY0 for buffer copies [ 24.899601] nouveau :01:00.0: DRM: allocated 1920x1080 fb: 0x6, bo 8800da058400 [ 24.992886] [drm] Initialized nouveau 1.3.0 20120801 for :01:00.0 on minor 0 -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (200, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages xserver-xorg-core depends on: ii keyboard-configuration1.134 ii libaudit1 1:2.4.5-1 ii libc6 2.21-6 ii libdbus-1-3 1.10.6-1 ii libdrm2 2.4.66-2 ii libegl1-mesa 11.1.1-2 ii libepoxy0
Bug#812384: xserver-xorg-video-freedreno: new upstream release
Package: xserver-xorg-video-freedreno Severity: wishlist Version 1.4.0 is available from ftp://mirror.csclub.uwaterloo.ca/x.org/individual/driver/ -- Martin Michlmayr Linux for HPE Helion, Hewlett Packard Enterprise
Bug#812385: Please enable arm64
Package: xserver-xorg-video-freedreno Version: 1.3.0-1 Severity: wishlist Please enable this package on arm64. The Snapdragon 400 is a CPU that can do 64 bit and it includes an Adreno 306 GPU. -- Martin Michlmayr Linux for HPE Helion, Hewlett Packard Enterprise
Bug#812385: Please enable arm64
FWIW, I successfully compiled the package after adding arm64 to debian/control (twice). -- Martin Michlmayr Linux for HPE Helion, Hewlett Packard Enterprise
Bug#808871: xserver-xorg-core: under Linux kernel >= 4.2: (EE) XKB: Could not invoke xkbcomp
Package: xserver-xorg-core Version: 2:1.17.3-2 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Whenever booting this host under Linux kernel newer than 4.1, xkbcomp systematically fails to load and Xserver exits with an error. The same result happens whether xf86-video-geode or xf86-video-vesa is used. Under kernel 4.1 or 3.16, this issue does not happen and Xserver launches as expected. - -- Package-specific info: X server symlink status: - lrwxrwxrwx 1 root root 13 Feb 3 2010 /etc/X11/X -> /usr/bin/Xorg - -rwxr-xr-x 1 root root 274 Oct 28 01:32 /usr/bin/Xorg VGA-compatible devices on PCI bus: - -- 00:01.1 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD] Geode LX Video [1022:2081] /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): - --- Linux version 4.3.0-1-686 (debian-ker...@lists.debian.org) (gcc version 5.3.1 20151207 (Debian 5.3.1-3) ) #1 SMP Debian 4.3.3-2 (2015-12-17) Xorg X server log files on system: - -- - -rw-r--r-- 1 root root 8894 Dec 24 00:58 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - - [ 663.918] X.Org X Server 1.17.3 Release Date: 2015-10-26 [ 663.924] X Protocol Version 11, Revision 0 [ 663.924] Build Operating System: Linux 3.16.0-4-amd64 i686 Debian [ 663.924] Current Operating System: Linux geode 4.3.0-1-686 #1 SMP Debian 4.3.3-2 (2015-12-17) i586 [ 663.924] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.3.0-1-686 root=UUID=97b2628b-28a5-49f2-85f7-495728b3bef8 ro panic=15 pnpbios=off boot_delay=1 quiet splash cs5535audio.ac97_quirk=1 [ 663.924] Build Date: 27 October 2015 11:29:29PM [ 663.924] xorg-server 2:1.17.3-2 (http://www.debian.org/support) [ 663.925] Current version of pixman: 0.33.4 [ 663.925]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 663.925] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 663.925] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Dec 24 00:58:54 2015 [ 663.926] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 663.933] (==) No Layout section. Using the first Screen section. [ 663.935] (==) No screen section available. Using defaults. [ 663.935] (**) |-->Screen "Default Screen Section" (0) [ 663.935] (**) | |-->Monitor "" [ 663.939] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 663.942] (==) Automatically adding devices [ 663.942] (==) Automatically enabling devices [ 663.943] (==) Automatically adding GPU devices [ 663.943] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 663.943]Entry deleted from font path. [ 663.943] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [ 663.943]Entry deleted from font path. [ 663.943] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [ 663.943]Entry deleted from font path. [ 663.943] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist. [ 663.943]Entry deleted from font path. [ 663.943] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [ 663.943]Entry deleted from font path. [ 663.944] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [ 663.944]Entry deleted from font path. [ 663.944] (==) FontPath set to: /usr/share/fonts/X11/misc, built-ins [ 663.944] (==) ModulePath set to "/usr/lib/xorg/modules" [ 663.944] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 663.944] (II) Loader magic: 0x802b4700 [ 663.944] (II) Module ABI versions: [ 663.944]X.Org ANSI C Emulation: 0.4 [ 663.944]X.Org Video Driver: 19.0 [ 663.947]X.Org XInput driver : 21.0 [ 663.947]X.Org Server Extension : 9.0 [ 664.003] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c162 [ 664.026] (--) PCI:*(0:0:1:1) 1022:2081:1509:801b rev 0, Mem @ 0xd000/268435456, 0xefff/16384, 0xeffec000/16384, 0xeffe8000/16384, 0xefff8000/16384 [ 664.027] (II) LoadModule: "glx" [ 664.031] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 664.059] (II) Module glx: vendor="X.Org Foundation" [ 664.063]compiled for 1.17.3, module version = 1.0.0 [ 664.063]ABI class: X.Org Server Extension, version 9.0 [ 664.063] (==) AIGLX enabled [ 664.065] (==) Matched geode as autoconfigured
Bug#802327: xserver-xorg-core: (EE) Server terminated with error (1). Closing log file.
Btw, is there any other X driver that is known to fail to launch as a non-root user? We might as well clone this bug for each of them and propose "Recommends: xserver-xorg-legacy" as the solution in each case. Cheers! Martin-Éric 2015-10-21 22:50 GMT+03:00 Martin-Éric Racine <martin-eric.rac...@iki.fi>: > Thanks for the additional info. > > In that case, the fbdev driver ought to Recommends xserver-xorg-legacy > (Depends seems too strong of a dependency, since it's mostly GDM3 that > wants to launch X as non-root; lightdm doesn't). > > Martin-Éric > > 2015-10-20 9:32 GMT+03:00 Julien Cristau <jcris...@debian.org>: >> On Mon, Oct 19, 2015 at 20:24:36 +0300, Martin-Éric Racine wrote: >> >>> That's what I assumed too, except that X also fails to launch via gdm3 >>> without the legacy wrapper if I remove the Geode driver and let the >>> Xserver use its own choice of fbdev or its built-in modeline driver. >>> >> The modesetting driver requires a kernel driver, which there isn't for >> geode; the fbdev driver requires root. >> >> Cheers, >> Julien
Bug#802327: xserver-xorg-core: (EE) Server terminated with error (1). Closing log file.
Thanks for the additional info. In that case, the fbdev driver ought to Recommends xserver-xorg-legacy (Depends seems too strong of a dependency, since it's mostly GDM3 that wants to launch X as non-root; lightdm doesn't). Martin-Éric 2015-10-20 9:32 GMT+03:00 Julien Cristau <jcris...@debian.org>: > On Mon, Oct 19, 2015 at 20:24:36 +0300, Martin-Éric Racine wrote: > >> That's what I assumed too, except that X also fails to launch via gdm3 >> without the legacy wrapper if I remove the Geode driver and let the >> Xserver use its own choice of fbdev or its built-in modeline driver. >> > The modesetting driver requires a kernel driver, which there isn't for > geode; the fbdev driver requires root. > > Cheers, > Julien
Bug#802327: xserver-xorg-core: (EE) Server terminated with error (1). Closing log file.
Package: xserver-xorg-core Version: 2:1.17.2-3 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Since a new Xorg transitioned into Testing today, X flat out fails to launch. $ ls -al /dev/fb0 crw-rw 1 root video 29, 0 loka 19 2015 /dev/fb0 $ ls -al /dev/cpu/0/msr crw--- 1 root root 202, 0 loka 19 2015 /dev/cpu/0/msr - -- Package-specific info: X server symlink status: - lrwxrwxrwx 1 root root 13 Feb 3 2010 /etc/X11/X -> /usr/bin/Xorg - -rwxr-xr-x 1 root root 274 Oct 8 13:07 /usr/bin/Xorg VGA-compatible devices on PCI bus: - -- 00:01.1 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD] Geode LX Video [1022:2081] Xorg X server configuration file status: - - -rw-r--r-- 1 root root 212 Feb 18 2012 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: - --- Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Depth 24 Modes "1280x1024" "1024x768" "800x600" "640x480" EndSubSection EndSection /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): - --- Linux version 3.16.0-4-586 (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 Debian 3.16.7-ckt11-1+deb8u5 (2015-10-09) Oct 19 16:57:45 geode systemd[1]: Starting GNOME Display Manager... Oct 19 16:57:45 geode systemd[1]: Starting GNOME Display Manager... Oct 19 16:57:45 geode systemd[1]: Started GNOME Display Manager. Oct 19 16:57:45 geode systemd[1]: Started GNOME Display Manager. Oct 19 16:57:46 geode systemd[1]: Started Session c288 of user Debian-gdm. Oct 19 16:57:46 geode systemd[1]: Started Session c288 of user Debian-gdm. Oct 19 16:57:46 geode console-kit-daemon[922]: (process:12550): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed Oct 19 16:57:46 geode console-kit-daemon[922]: (process:12550): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed Oct 19 16:57:47 geode gnome-session[12554]: gnome-session[12554]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary Oct 19 16:57:47 geode gnome-session[12554]: gnome-session[12554]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary Oct 19 16:57:47 geode gnome-session[12554]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary Oct 19 16:57:47 geode gnome-session[12554]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary Oct 19 16:57:47 geode gnome-session[12554]: (gnome-shell:12560): mutter-WARNING **: Could not stat /dev/dri/card0: Tiedostoa tai hakemistoa ei ole Oct 19 16:57:47 geode gnome-session[12554]: (gnome-shell:12560): mutter-WARNING **: Could not stat /dev/dri/card0: Tiedostoa tai hakemistoa ei ole Oct 19 16:57:47 geode gnome-session[12554]: (gnome-shell:12560): Clutter-CRITICAL **: Unable to initialize Clutter: Unable to initialize the Clutter backend Oct 19 16:57:47 geode gnome-session[12554]: (gnome-shell:12560): Clutter-CRITICAL **: Unable to initialize Clutter: Unable to initialize the Clutter backend Oct 19 16:57:47 geode gnome-session[12554]: (gnome-shell:12560): mutter-ERROR **: Unable to initialize Clutter. Oct 19 16:57:47 geode gnome-session[12554]: (gnome-shell:12560): mutter-ERROR **: Unable to initialize Clutter. Oct 19 16:57:47 geode gnome-session[12554]: WARNING: Application 'gnome-shell-wayland.desktop' killed by signal 5 Oct 19 16:57:47 geode gnome-session[12554]: gnome-session[12554]: WARNING: Application 'gnome-shell-wayland.desktop' killed by signal 5 Oct 19 16:57:47 geode gnome-session[12554]: WARNING: Application 'gnome-shell-wayland.desktop' killed by signal 5 Oct 19 16:57:47 geode gnome-session[12554]: gnome-session[12554]: WARNING: Application 'gnome-shell-wayland.desktop' killed by signal 5 Oct 19 16:57:47 geode /usr/lib/gdm3/gdm-wayland-session[12551]: Activating service name='ca.desrt.dconf' Oct 19 16:57:47 geode /usr/lib/gdm3/gdm-wayland-session[12551]: Activating service name='ca.desrt.dconf' Oct 19 16:57:47 geode gnome-session[12554]: Unrecoverable failure in required component gnome-shell-wayland.desktop Oct 19 16:57:47 geode gnome-session[12554]: Unrecoverable failure in required component gnome-shell-wayland.desktop Oct 19 16:57:47 geode gdm3: GdmDisplay: display lasted 1,787149 seconds Oct 19 16:57:47 geode gdm3: GdmDisplay: display lasted 1,787149 seconds Oct 19 16:57:47 geode console-kit-daemon[922]: (process:12568): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed Oct 19 16:57:47 geode console-kit-daemon[922]: (process:12568): GLib-CRITICAL **: g_slice_set_config: assertion
Bug#802327: xserver-xorg-core: (EE) Server terminated with error (1). Closing log file.
That's what I assumed too, except that X also fails to launch via gdm3 without the legacy wrapper if I remove the Geode driver and let the Xserver use its own choice of fbdev or its built-in modeline driver. Martin-Éric 2015-10-19 20:00 GMT+03:00 Julien Cristau <jul...@cristau.org>: > Gdm now starts X as the user, I guess lightdm starts it as root. > > Cheers, > Julien > > On October 19, 2015 6:45:15 PM CEST, "Martin-Éric Racine" > <martin-eric.rac...@iki.fi> wrote: >> >> 2015-10-19 18:31 GMT+03:00 Julien Cristau <jcris...@debian.org>: >>> >>> On Mon, Oct 19, 2015 at 17:27:35 +0300, Martin-Éric Racine wrote: >>> >>>> Package: xserver-xorg-core >>>> Version: 2:1.17.2-3 >>>> Severity: important >>>> >>>> Since a new Xorg transitioned into Testing today, X flat out fails to >>>> launch. >>>> >>>> $ ls -al /dev/fb0 >>>> crw-rw 1 root video 29, 0 loka 19 2015 /dev/fb0 >>>> >>>> $ ls -al /dev/cpu/0/msr >>>> crw--- 1 root root 202, 0 loka 19 2015 /dev/cpu/0/msr >>> >>> >>> If the geode driver requires running X as root, it should depend on the >>> new xserver-xorg-legacy package. >> >> >> lightdm launches fine as-is with the Geode driver. Only gdm3 ! >> seems >> to >> require that special wrapper to launch on Geode. >> >> -- Martin-Éric >> > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#802327: xserver-xorg-core: (EE) Server terminated with error (1). Closing log file.
2015-10-19 18:31 GMT+03:00 Julien Cristau <jcris...@debian.org>: > On Mon, Oct 19, 2015 at 17:27:35 +0300, Martin-Éric Racine wrote: > >> Package: xserver-xorg-core >> Version: 2:1.17.2-3 >> Severity: important >> >> Since a new Xorg transitioned into Testing today, X flat out fails to launch. >> >> $ ls -al /dev/fb0 >> crw-rw 1 root video 29, 0 loka 19 2015 /dev/fb0 >> >> $ ls -al /dev/cpu/0/msr >> crw--- 1 root root 202, 0 loka 19 2015 /dev/cpu/0/msr >> > If the geode driver requires running X as root, it should depend on the > new xserver-xorg-legacy package. lightdm launches fine as-is with the Geode driver. Only gdm3 seems to require that special wrapper to launch on Geode. -- Martin-Éric
Bug#758460: xserver-xorg-video-nouveau: Crash and freeze with GeForce 6150SE.
2015-05-10 12:48 GMT+02:00 Agustin Martin agmar...@debian.org: 2015-05-05 19:43 GMT+02:00 Martin-Éric Racine martin-eric.rac...@iki.fi: 2015-05-05 19:38 GMT+03:00 Agustin Martin agmar...@debian.org: On Mon, May 04, 2015 at 12:49:52PM +0200, Agustin Martin wrote: Hi, Just to confirm a similar problem in a GeForce 6150SE graphics engine, 00:0d.0 VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) Similar messages in syslog, [ 711.849697] nouveau E[PBUS][:00:0d.0] MMIO write of 0x00870001 FAULT at 0x00b010 and random freeze. Last seen thing is some sort of zig-zag random pattern apparently with colors used at that time. Nothing but hard reboot helps once the system is frozen, not even Magic SysRq. No relevant info seems to appear in syslog. An important info is that this does not happen if I reboot with old 3.2.04-amd64 (3.2.65-1+deb7u2) wheezy kernel. So this seems to be a problem with the nouveau kernel module. [...] http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=b7387454bda64a16350fabee4d81bec3b8de8fa2 applied, but I then noticed that it is already in jessie's kernel. Martin-Éric, has jessie's kernel fixed the problem in your box? Agustin, There's two NVDIA boxes involved (IIRC, I filed separate bugs reports). Neither box works with the Nouveau X.org driver in Jessie. In both cases, I've had to remove xserver-xorg-video-nouveau and let Xserver use the generic modeline driver. Hi, Just to add that this freeze no longer appears with jessie's kernel if I pass nouveau.noaccel=1 as a kernel boot parameter (as suggested in #776838) or if I put options nouveau noaccel=1 in my /etc/modprobe.d/local-video.conf. No intense graphics use is done in this box, so I did not notice a performance loss. Hi all, I have been searching the web to try finding more info about this problem. Seems that there are some reports about similar problems in different forums (added some info below for those curious) and that it appeared somewhere between kernel 3.6 and 3.7. I have tried unsuccessfully a couple of the proposed patches, no luck. The good news are that I have also tried sid kernel removing the nouveau noaccel=1 from boot cmdline, and I am no longer having this problem for a couple of days with that sid kernel (cross fingers), I have even re-enabled use hardware acceleration if possible in firefox and things are still working well. Summarizing, in this jessie box: linux-image-3.2.0-4-amd64 (3.2.65-1+deb7u2): No problem found linux-image-3.16.0-4-amd64 (3.16.7-ckt11-1): Problem is present linux-image-4.0.0-2-amd64 (4.0.7-1): No problem found, did not try with testing 4.0.5-1 So, at least in my box, problem seems not to be a problem with xserver-xorg-video-nouveau but with the nouveau module in kernel. For those curious, other possibly related references I found in my web searches * https://bugzilla.redhat.com/show_bug.cgi?id=901816 Bug 901816 - artifacts/freezeups in graphical mode with nouveau and GeForce 6150SE * https://bugs.freedesktop.org/show_bug.cgi?id=61321 Bug 61321 - [regression][NV4c] System hang while loading gdm on 3.7 kernel (works on 3.6) * https://bugs.freedesktop.org/show_bug.cgi?id=87361 Bug 87361 - [NV4C] GPU lock-up after booting to desktop in Fedora 20 21 (Nvidia Geforce 6100 IGP) * https://bugzilla.redhat.com/show_bug.cgi?id=679619 Bug 679619 - Nouveau freeze when try to start X. nvidia Geforce Go 6150 * https://forums.gentoo.org/viewtopic-t-952224-start-0.html Kernel 3.7.9 crashes (nouveau?) * https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1181902 Nouveau driver glitch on Ubuntu 13.04 will cause system to freeze under certain conditions, Bug #1181902 * http://www.linuxquestions.org/questions/slackware-14/firefox-nouveau-on-fresh-current-install-freezes-system-4175455844/ Firefox + nouveau on fresh -current install freezes system * https://bugzilla.kernel.org/show_bug.cgi?id=50091 Bug 50091 - [BISECTED]GeForce 6150SE: system hangs on X-server start with garbled screen * http://ubuntuforums.org/showthread.php?t=2181430 Nouveau crash and freeze on install of 13.10 * https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1217585 #1217585, System hangs after some time with nouveau and GT240 * https://bugs.freedesktop.org/show_bug.cgi?id=87361 Bug 87361 - [NV4C] GPU lock-up after booting to desktop in Fedora 20 21 (Nvidia Geforce 6100 IGP) * https://bbs.archlinux.org/viewtopic.php?id=156690 Upgrade to linux-3.7.3: freeze on some actions in X (nouveau driver) * https://bugs.freedesktop.org/show_bug.cgi?id=89842 Bug 89842 - Nvidia nouveau drivers hangs all gnome when opening the new legacy tray (and many other situations) * https://bugs.freedesktop.org/show_bug.cgi?id=90276 Bug 90276 - [NVE4] read fault error, bisected * https://bugs.freedesktop.org/show_bug.cgi?id=90453 Bug 90453 - [NVE4] Desktop freezes
Bug#758460: xserver-xorg-video-nouveau: Crash and freeze with GeForce 6150SE.
2015-05-05 19:43 GMT+02:00 Martin-Éric Racine martin-eric.rac...@iki.fi: 2015-05-05 19:38 GMT+03:00 Agustin Martin agmar...@debian.org: On Mon, May 04, 2015 at 12:49:52PM +0200, Agustin Martin wrote: Hi, Just to confirm a similar problem in a GeForce 6150SE graphics engine, 00:0d.0 VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) Similar messages in syslog, [ 711.849697] nouveau E[PBUS][:00:0d.0] MMIO write of 0x00870001 FAULT at 0x00b010 and random freeze. Last seen thing is some sort of zig-zag random pattern apparently with colors used at that time. Nothing but hard reboot helps once the system is frozen, not even Magic SysRq. No relevant info seems to appear in syslog. An important info is that this does not happen if I reboot with old 3.2.04-amd64 (3.2.65-1+deb7u2) wheezy kernel. So this seems to be a problem with the nouveau kernel module. [...] http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=b7387454bda64a16350fabee4d81bec3b8de8fa2 applied, but I then noticed that it is already in jessie's kernel. drm/nv4c/mc: disable msi commit 4761703bd04bbdf56396d264903cc5a1fdcb3c01 upstream. Martin-Éric, has jessie's kernel fixed the problem in your box? Agustin, There's two NVDIA boxes involved (IIRC, I filed separate bugs reports). Neither box works with the Nouveau X.org driver in Jessie. In both cases, I've had to remove xserver-xorg-video-nouveau and let Xserver use the generic modeline driver. Hi, Just to add that this freeze no longer appears with jessie's kernel if I pass nouveau.noaccel=1 as a kernel boot parameter (as suggested in #776838) or if I put options nouveau noaccel=1 in my /etc/modprobe.d/local-video.conf. No intense graphics use is done in this box, so I did not notice a performance loss. -- Agustin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cahmxk7jnno0us76jxoymvo7mgbgg5boaruwwsyy8+w4_lv+...@mail.gmail.com
Re: Xserver 1.17 in unstable
2015-05-06 10:51 GMT+03:00 Julien Cristau jcris...@debian.org: xorg-server 2:1.17.1-2 was intended to go to experimental but ended up in sid by mistake. Your package needs to be updated for the new server, please let debian-x know of your plans and upstream status. Also for free drivers, please let us know if you'd like us to NMU. Sorry for the unintended breakage. No problem. I was actually wondering when 1.17 would enter unstable. :) Btw, I notice that XSF is still using Debhelper compatibility 8. Is there any particular reason for foregoing compatibility 9? Cheers! Martin-Éric -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/capzxpqeuh2jluq8xlv3g3dhzg4kqzjmog3mf6t3bsug_4my...@mail.gmail.com
Re: Xserver 1.17 in unstable
2015-05-06 16:13 GMT+03:00 Julien Cristau jcris...@debian.org:
On Wed, May 6, 2015 at 16:07:36 +0300, Martin-Éric Racine wrote:
2015-05-06 15:22 GMT+03:00 Julien Cristau jcris...@debian.org:
On Wed, May 6, 2015 at 12:40:51 +0300, Martin-Éric Racine wrote:
Btw, I notice that XSF is still using Debhelper compatibility 8. Is
there any particular reason for foregoing compatibility 9?
Depends on the package. I've been updating a few to debhelper compat 9
recently. For drivers however, at least when using dh_auto_configure,
that requires overriding its multiarch libdir setting to keep things
under /usr/lib/xorg/modules. But there's no specific reason to avoid
bumping to 9 AFAIK.
The consequences of compatibility level 9 (automatically enforced
multiarch libdir) on drivers is precisely what I'm worried about. If
there is a standardized debian/rules stanza for overriding this for X
drivers, I would love to hear about it.
I've been using this:
override_dh_auto_configure:
dh_auto_configure -- \
--disable-silent-rules \
--libdir=\$${exec_prefix}/lib
See e.g.
http://anonscm.debian.org/cgit/pkg-xorg/driver/xserver-xorg-video-trident.git/commit/?id=713c309b94fa2084dee04def78924fbc7563d011
Thanks for the link to that code sample! Implemented and ready to sponsor:
http://mentors.debian.net/debian/pool/main/x/xserver-xorg-video-geode/xserver-xorg-video-geode_2.11.16-9.dsc
Cheers!
Martin-Éric
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/capzxpqemvqm0hifhohaktf8y3apauqmxouarvff-usogqow...@mail.gmail.com
Re: Xserver 1.17 in unstable
2015-05-06 15:22 GMT+03:00 Julien Cristau jcris...@debian.org: On Wed, May 6, 2015 at 12:40:51 +0300, Martin-Éric Racine wrote: Btw, I notice that XSF is still using Debhelper compatibility 8. Is there any particular reason for foregoing compatibility 9? Depends on the package. I've been updating a few to debhelper compat 9 recently. For drivers however, at least when using dh_auto_configure, that requires overriding its multiarch libdir setting to keep things under /usr/lib/xorg/modules. But there's no specific reason to avoid bumping to 9 AFAIK. The consequences of compatibility level 9 (automatically enforced multiarch libdir) on drivers is precisely what I'm worried about. If there is a standardized debian/rules stanza for overriding this for X drivers, I would love to hear about it. Cheers! Martin-Éric -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/capzxpqdgthjyyc6mmezuxdc8qmxj5je8wwem3hkurr6lh_o...@mail.gmail.com
Bug#758460: xserver-xorg-video-nouveau: Crash and freeze with GeForce 6150SE.
2015-05-05 19:38 GMT+03:00 Agustin Martin agmar...@debian.org: On Mon, May 04, 2015 at 12:49:52PM +0200, Agustin Martin wrote: Hi, Just to confirm a similar problem in a GeForce 6150SE graphics engine, 00:0d.0 VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) Similar messages in syslog, [ 711.849697] nouveau E[PBUS][:00:0d.0] MMIO write of 0x00870001 FAULT at 0x00b010 and random freeze. Last seen thing is some sort of zig-zag random pattern apparently with colors used at that time. Nothing but hard reboot helps once the system is frozen, not even Magic SysRq. No relevant info seems to appear in syslog. An important info is that this does not happen if I reboot with old 3.2.04-amd64 (3.2.65-1+deb7u2) wheezy kernel. So this seems to be a problem with the nouveau kernel module. Noticed that something similar has been reported in http://bugs.debian.org/758460 for a GeForce 6150LE. Not merging both bug reports in case they are different issues for different chip variants, but cc'ing. Following advice there I tried with kernel boot parameter nouveau.config=NvMSI=0 in the command line and with options nouveau NvMSI=0 in a /etc/modprobe.d/local-video.conf file (also built a new initramfs in case this is needed), problem is still here, no luck. Hi, I was thinking about building a kernel with patch mentioned in http://bugs.debian.org/758460 http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=b7387454bda64a16350fabee4d81bec3b8de8fa2 applied, but I then noticed that it is already in jessie's kernel. Searching kernel changelogs, I found this in https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.18.4 commit 715f7c8214c7822833af757109022006c3f01d6a Author: Ilia Mirkin imir...@alum.mit.edu Date: Tue Dec 16 13:55:38 2014 -0500 drm/nv4c/mc: disable msi commit 4761703bd04bbdf56396d264903cc5a1fdcb3c01 upstream. Several users have, over time, reported issues with MSI on these IGPs. They're old, rarely available, and MSI doesn't provide such huge advantages on them. Just disable. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=87361 Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=74492 Fixes: fa8c9ac72fe (drm/nv4c/mc: nv4x igp's have a different msi rearm register) Signed-off-by: Ilia Mirkin imir...@alum.mit.edu Signed-off-by: Ben Skeggs bske...@redhat.com Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org also in https://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.14.30 (LTS?) Now it is clear why setting NvMSI=0 did not make any difference in the box with the GeForce 6150SE where I hit the bug (Did not try with noaccel). Martin-Éric, has jessie's kernel fixed the problem in your box? Agustin, There's two NVDIA boxes involved (IIRC, I filed separate bugs reports). Neither box works with the Nouveau X.org driver in Jessie. In both cases, I've had to remove xserver-xorg-video-nouveau and let Xserver use the generic modeline driver. Martin-Éric -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAPZXPQfNtkR9e+pWCJPbYgY6H0Qwa8eK7nhhmidj=egdpzz...@mail.gmail.com
Bug#758460: xserver-xorg-video-nouveau: Crash and freeze with GeForce 6150SE.
On Mon, May 04, 2015 at 12:49:52PM +0200, Agustin Martin wrote: Hi, Just to confirm a similar problem in a GeForce 6150SE graphics engine, 00:0d.0 VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) Similar messages in syslog, [ 711.849697] nouveau E[PBUS][:00:0d.0] MMIO write of 0x00870001 FAULT at 0x00b010 and random freeze. Last seen thing is some sort of zig-zag random pattern apparently with colors used at that time. Nothing but hard reboot helps once the system is frozen, not even Magic SysRq. No relevant info seems to appear in syslog. An important info is that this does not happen if I reboot with old 3.2.04-amd64 (3.2.65-1+deb7u2) wheezy kernel. So this seems to be a problem with the nouveau kernel module. Noticed that something similar has been reported in http://bugs.debian.org/758460 for a GeForce 6150LE. Not merging both bug reports in case they are different issues for different chip variants, but cc'ing. Following advice there I tried with kernel boot parameter nouveau.config=NvMSI=0 in the command line and with options nouveau NvMSI=0 in a /etc/modprobe.d/local-video.conf file (also built a new initramfs in case this is needed), problem is still here, no luck. Hi, I was thinking about building a kernel with patch mentioned in http://bugs.debian.org/758460 http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=b7387454bda64a16350fabee4d81bec3b8de8fa2 applied, but I then noticed that it is already in jessie's kernel. Searching kernel changelogs, I found this in https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.18.4 commit 715f7c8214c7822833af757109022006c3f01d6a Author: Ilia Mirkin imir...@alum.mit.edu Date: Tue Dec 16 13:55:38 2014 -0500 drm/nv4c/mc: disable msi commit 4761703bd04bbdf56396d264903cc5a1fdcb3c01 upstream. Several users have, over time, reported issues with MSI on these IGPs. They're old, rarely available, and MSI doesn't provide such huge advantages on them. Just disable. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=87361 Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=74492 Fixes: fa8c9ac72fe (drm/nv4c/mc: nv4x igp's have a different msi rearm register) Signed-off-by: Ilia Mirkin imir...@alum.mit.edu Signed-off-by: Ben Skeggs bske...@redhat.com Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org also in https://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.14.30 (LTS?) Now it is clear why setting NvMSI=0 did not make any difference in the box with the GeForce 6150SE where I hit the bug (Did not try with noaccel). Martin-Éric, has jessie's kernel fixed the problem in your box? -- Agustin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150505163815.ga5...@agmartin.aq.upm.es
Bug#758460: xserver-xorg-video-nouveau: Crash and freeze with GeForce 6150SE.
Package: xserver-xorg-video-nouveau Version: 1:1.0.11-1 Followup-For: Bug #783805 Dear Maintainer, 1) I've just switched to Jessie and now my system is very unstable (barely usable). That was not the case at all with Wheezy. I guess it's related to the nouveau driver, but maybe some cryptic kernel issue are involved too ? Just for the record, I gave a try to Jessie in the beginning of 2013 (so testing at that time), but went back to Wheezy, for the same reason : way too frequent crashes. 2) ctrl+alt+F1 doesn't work to take control again. 3) It's difficult to accurately trigger (at user level) which typical action entails a crash, it's somewhat fuzzy. 4) I skimmed through the bug lists but I can't figure out whether or not the same *exact* bug has always been reported. Forgive me, if so. And it's my first bug report. 5) I used the reportbug tool, but why some critical section doesn't figure and reportbug removes it, like this one (extract of dmesg) : dmesg:[ 68.627296] nouveau E[PBUS][:00:0d.0] MMIO write of x00820001 FAULT at 0x00b000 Hi, Just to confirm a similar problem in a GeForce 6150SE graphics engine, 00:0d.0 VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) Similar messages in syslog, [ 711.849697] nouveau E[PBUS][:00:0d.0] MMIO write of 0x00870001 FAULT at 0x00b010 and random freeze. Last seen thing is some sort of zig-zag random pattern apparently with colors used at that time. Nothing but hard reboot helps once the system is frozen, not even Magic SysRq. No relevant info seems to appear in syslog. An important info is that this does not happen if I reboot with old 3.2.04-amd64 (3.2.65-1+deb7u2) wheezy kernel. So this seems to be a problem with the nouveau kernel module. Noticed that something similar has been reported in http://bugs.debian.org/758460 for a GeForce 6150LE. Not merging both bug reports in case they are different issues for different chip variants, but cc'ing. Following advice there I tried with kernel boot parameter nouveau.config=NvMSI=0 in the command line and with options nouveau NvMSI=0 in a /etc/modprobe.d/local-video.conf file (also built a new initramfs in case this is needed), problem is still here, no luck. I am still blindly trying to find a reproducibility pattern, Seems that when mozilla is used and closed, if I try to open it again inmediately failure often happens. Just have to do one of this quick iceweasel start and stop cycles to hit the problem with a very high probability (funny, this seems not to happen with chromium). I do not have daily access to the affected box (and it is not one of my boxes), but let me know if I can try to provide more info. By the way, gdm3 is not used there, just lightdm, and init is sysvinit. Regards, X server symlink status: lrwxrwxrwx 1 root root 13 Mar 11 2014 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2401376 Feb 11 01:35 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:0d.0 VGA compatible controller [0300]: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24) -- Agustin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150504104952.ga27...@agmartin.aq.upm.es
Bug#758460: xserver-xorg-video-nouveau: [GeForce 6150 LE] complete system freeze as soon as GDM launches on kernel (= 3.14)
2014-12-17 20:37 GMT+02:00 Sven Joachim svenj...@gmx.de: On 2014-08-17 20:33 +0200, Martin-Éric Racine wrote: Package: xserver-xorg-video-nouveau Version: 1:1.0.10-1+b2 Severity: important This Athlon 64 system complete freezes (requires a hard poweroff via the power switch) as soon as X 1.16 launches via GDM when booting from kernel 3.14 or 3.16-trunk. Does it help to boot with the nouveau.config=NvMSI=0 kernel parameter? See https://bugs.freedesktop.org/show_bug.cgi?id=87361 for more information on that topic. Yes, it does. Thank you. Could this exception be incorporated into the driver? Martin-Éric -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/debian-x
Bug#758460: xserver-xorg-video-nouveau: [GeForce 6150 LE] complete system freeze as soon as GDM launches on kernel (= 3.14)
2014-12-17 21:13 GMT+02:00 Sven Joachim svenj...@gmx.de: On 2014-12-17 19:55 +0100, Martin-Éric Racine wrote: 2014-12-17 20:37 GMT+02:00 Sven Joachim svenj...@gmx.de: On 2014-08-17 20:33 +0200, Martin-Éric Racine wrote: Package: xserver-xorg-video-nouveau Version: 1:1.0.10-1+b2 Severity: important This Athlon 64 system complete freezes (requires a hard poweroff via the power switch) as soon as X 1.16 launches via GDM when booting from kernel 3.14 or 3.16-trunk. Does it help to boot with the nouveau.config=NvMSI=0 kernel parameter? See https://bugs.freedesktop.org/show_bug.cgi?id=87361 for more information on that topic. Yes, it does. Thank you. Could this exception be incorporated into the driver? There's a patch in Ben Skegg's nouveau master branch[1]. It should go into the stable kernels eventually, but that will take some time. Could this fix be cherry-picked for Jessie's kernels? -- Martin-Éric -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/debian-x
Bug#758460: xserver-xorg-video-nouveau: [GeForce 6150 LE] complete system freeze as soon as GDM launches on kernel (= 3.14)
2014-12-17 21:50 GMT+02:00 Sven Joachim svenj...@gmx.de: On 2014-12-17 20:19 +0100, Martin-Éric Racine wrote: 2014-12-17 21:13 GMT+02:00 Sven Joachim svenj...@gmx.de: On 2014-12-17 19:55 +0100, Martin-Éric Racine wrote: 2014-12-17 20:37 GMT+02:00 Sven Joachim svenj...@gmx.de: On 2014-08-17 20:33 +0200, Martin-Éric Racine wrote: Package: xserver-xorg-video-nouveau Version: 1:1.0.10-1+b2 Severity: important This Athlon 64 system complete freezes (requires a hard poweroff via the power switch) as soon as X 1.16 launches via GDM when booting from kernel 3.14 or 3.16-trunk. Does it help to boot with the nouveau.config=NvMSI=0 kernel parameter? See https://bugs.freedesktop.org/show_bug.cgi?id=87361 for more information on that topic. Yes, it does. Thank you. Could this exception be incorporated into the driver? There's a patch in Ben Skegg's nouveau master branch[1]. It should go into the stable kernels eventually, but that will take some time. Could this fix be cherry-picked for Jessie's kernels? It should land there via Canonical's 3.16.y releases. Come again? Has the Ubuntu team taken over maintenance of Debian's kernels? -- Martin-Éric -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/debian-x
Bug#680514: xserver-xorg-video-intel: freezes also occuring in Jessie
Package: xserver-xorg-video-intel Version: 2:2.21.15-2+b2 Followup-For: Bug #680514 Hi there, I'm experiencing this issue over one month now and I'm running an up to date jessie system (kernel 3.16.0-4-amd64, xserver-xorg-video-intel 2:2.21.15-2+b2, xserver-xorg-core 2:1.16.1.901-1). I'm not able to find any trigger for the lock-up, the bug just randomly appears out of the blue. Once I also found my laptop frozen this way in the morning; the system was idle for at least several hours when the lock-up occured. As reported earlier, it is still possible to SSH into the machine; what I think was not reported is that it is _sometimes_ possible to revive the system by executing pm-suspend via SSH - the screen goes off for a while, turns immediately back on and everything works perfectly again. Sometimes, however, the pm-suspend succeeds and xserver remains frozen even after waking up, no matter how many times I try executing pm-suspend. In the latter case I also noticed that it takes more time than usual to finish suspending. Any idea what should I look for when it happens again? I'm running into this bug few times a week so I could try to learn more, but the logs do not seem to reveal anything useful.. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Oct 4 2013 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2397280 Nov 3 22:52 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) Xorg X server configuration file status: -rw-r--r-- 1 root root 152 May 22 2014 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: --- Section Device Identifier Intel Graphics Driver intel Option AccelMethod sna Option TearFree true EndSection /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-13) ) #1 SMP Debian 3.16.7-2 (2014-11-06) Xorg X server log files on system: -- -rw-r--r-- 1 root root 20725 Dec 11 18:23 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 3.985] X.Org X Server 1.16.1.901 (1.16.2 RC 1) Release Date: 2014-11-02 [ 3.985] X Protocol Version 11, Revision 0 [ 3.985] Build Operating System: Linux 3.2.0-4-amd64 x86_64 Debian [ 3.985] Current Operating System: Linux hx31 3.16.0-4-amd64 #1 SMP Debian 3.16.7-2 (2014-11-06) x86_64 [ 3.985] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=0d377c28-a14d-4365-ab55-3d9f001fb7b5 ro quiet pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nmi_watchdog=0 acpi_osi= [ 3.985] Build Date: 03 November 2014 09:44:08PM [ 3.985] xorg-server 2:1.16.1.901-1 (http://www.debian.org/support) [ 3.985] Current version of pixman: 0.32.6 [ 3.985]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 3.985] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 3.985] (==) Log file: /var/log/Xorg.0.log, Time: Thu Dec 11 18:21:02 2014 [ 3.987] (==) Using config file: /etc/X11/xorg.conf [ 3.987] (==) Using system config directory /usr/share/X11/xorg.conf.d [ 3.994] (==) No Layout section. Using the first Screen section. [ 3.994] (==) No screen section available. Using defaults. [ 3.994] (**) |--Screen Default Screen Section (0) [ 3.994] (**) | |--Monitor default monitor [ 3.994] (==) No device specified for screen Default Screen Section. Using the first device section listed. [ 3.994] (**) | |--Device Intel Graphics [ 3.994] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [ 3.994] (==) Automatically adding devices [ 3.994] (==) Automatically enabling devices [ 3.994] (==) Automatically adding GPU devices [ 3.997] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [ 3.997]Entry deleted from font path. [ 4.025] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 4.025] (==) ModulePath set to /usr/lib/xorg/modules [ 4.025] (II) The
Bug#771108: xserver-xorg-video-nouveau: gnome-session fails to launch on [Riva TNT2 / TNT2 Pro] [10de:0028] (rev 15)
Package: xserver-xorg-video-nouveau Version: 1:1.0.11-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 When selecting GNOME-session from GDM on this host, I get the dreaded Oh no! Something has gone wrong. dialog with a [Log Out] button during the session launch. - -- Package-specific info: X server symlink status: - lrwxrwxrwx 1 root root 13 Nov 7 2007 /etc/X11/X - /usr/bin/Xorg - -rwxr-xr-x 1 root root 2556784 Nov 3 23:52 /usr/bin/Xorg VGA-compatible devices on PCI bus: - -- 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV5 [Riva TNT2 / TNT2 Pro] [10de:0028] (rev 15) Xorg X server configuration file status: - - -rw-r--r-- 1 root root 1178 Feb 23 2008 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: - --- # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type man xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section InputDevice Identifier Generic Keyboard Driver kbd Option XkbRules xorg Option XkbModel pc105 Option XkbLayout fi Option XkbVariantclassic EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option Emulate3Buttons true EndSection Section Device Identifier Configured Video Device EndSection Section Monitor Identifier Configured Monitor EndSection Section Screen Identifier Default Screen Monitor Configured Monitor Device Configured Video Device EndSection /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): - --- Linux version 3.16.0-4-686-pae (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-13) ) #1 SMP Debian 3.16.7-2 (2014-11-06) Xorg X server log files on system: - -- - -rw-r--r-- 1 root root 35100 Nov 26 22:15 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - - [64.498] X.Org X Server 1.16.1.901 (1.16.2 RC 1) Release Date: 2014-11-02 [64.501] X Protocol Version 11, Revision 0 [64.501] Build Operating System: Linux 3.2.0-4-amd64 i686 Debian [64.501] Current Operating System: Linux voito 3.16.0-4-686-pae #1 SMP Debian 3.16.7-2 (2014-11-06) i686 [64.501] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-686-pae root=UUID=cc540c15-0f8a-4933-88de-5516da7b3414 ro panic=15 quiet splash [64.501] Build Date: 03 November 2014 09:48:56PM [64.501] xorg-server 2:1.16.1.901-1 (http://www.debian.org/support) [64.501] Current version of pixman: 0.32.6 [64.501]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [64.501] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [64.502] (==) Log file: /var/log/Xorg.0.log, Time: Wed Nov 26 22:12:37 2014 [64.533] (==) Using config file: /etc/X11/xorg.conf [64.533] (==) Using system config directory /usr/share/X11/xorg.conf.d [64.584] (==) No Layout section. Using the first Screen section. [64.584] (**) |--Screen Default Screen (0) [64.584] (**) | |--Monitor Configured Monitor [64.601] (**) | |--Device Configured Video Device [64.601] (==) Automatically adding devices [64.601] (==) Automatically enabling devices [64.601] (==) Automatically adding GPU devices [64.661] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [64.661]Entry deleted from font path. [64.661] (WW) The directory /usr/share/fonts/X11/100dpi/ does not exist. [64.661]Entry deleted from font path. [64.661] (WW) The directory /usr/share/fonts/X11/75dpi/ does not exist. [64.661]Entry deleted from font path. [64.661] (WW) The directory /usr/share/fonts/X11/Type1 does not exist. [64.661]Entry deleted from font path. [64.661] (WW) The directory /usr/share/fonts/X11/100dpi does not exist. [64.661]Entry deleted from font path. [64.661] (WW)
Bug#759005: xdm: Missing xdm.service, can't use with systemd
On Sat, Aug 23, 2014 at 09:30:24PM +0200, Sven Joachim wrote: On 2014-08-23 19:52 +0200, Kan-Ru Chen (陳侃如) wrote: Package: xdm Version: 1:1.1.11-1 Severity: important The xdm upstream ships a xdm.service file however it is not include in the xdm debian package. It would probably make sense to ship it, but care must be taken not to enable the service unless xdm is the default display manager. Hi, Please have a look at the info I provided for wdm in #761642. Main reference is https://titanpad.com/s-gsprintchangelog section = default display manager selection = Since xdm is not as complex as gdm, I think that lightdm may also be used as a reference. For implementation details, see https://bugs.debian.org/733220 where, among other things, it is proposed to use something like ExecStartPre=/bin/sh -c '[ ! -f /etc/X11/default-display-manager -o $(cat /etc/X11/default-display-manager 2/dev/null) = /usr/sbin/lightdm ]' Note that other things mentioned there are needed. While we are with errors just warn you about slim's bug https://bugs.debian.org/748668 which I'd expect to also affect xdm. slim.service enables the service unconditionally regardless of being default display manager or not. If xdm is the default slim will hijack that status. Regards, -- Agustin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140917102915.ga6...@agmartin.aq.upm.es
Bug#758460: xserver-xorg-video-nouveau: [GeForce 6150 LE] complete system freeze as soon as GDM launches on kernel (= 3.14)
Package: xserver-xorg-video-nouveau Version: 1:1.0.10-1+b2 Severity: important This Athlon 64 system complete freezes (requires a hard poweroff via the power switch) as soon as X 1.16 launches via GDM when booting from kernel 3.14 or 3.16-trunk. Reverting to the kernel 3.2 leftover from Stable won't crash. However, operation under that kernel both gets systemd complaining about missing features and produces seriously buggy video output in my gnome-shell session. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Aug 17 15:24 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2356320 Jul 18 01:25 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:05.0 VGA compatible controller [0300]: NVIDIA Corporation C51 [GeForce 6150 LE] [10de:0241] (rev a2) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 3.14-2-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-7) ) #1 SMP Debian 3.14.15-2 (2014-08-09) No Xorg X server log files found. udev information: - P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 E: EV=3 E: ID_FOR_SEAT=input-acpi-LNXPWRBN_00 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXPWRBN:00 E: ID_PATH_TAG=acpi-LNXPWRBN_00 E: KEY=10 0 E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw E: NAME=Power Button E: PHYS=LNXPWRBN/button/input0 E: PRODUCT=19/0/1/0 E: PROP=0 E: SUBSYSTEM=input E: TAGS=:seat: E: USEC_INITIALIZED=66474 P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event1 N: input/event1 E: BACKSPACE=guess E: DEVNAME=/dev/input/event1 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event1 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXPWRBN:00 E: ID_PATH_TAG=acpi-LNXPWRBN_00 E: MAJOR=13 E: MINOR=65 E: SUBSYSTEM=input E: TAGS=:power-switch: E: USEC_INITIALIZED=357797 E: XKBLAYOUT=fi E: XKBMODEL=pc105 P: /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2 E: DEVPATH=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2 E: EV=3 E: ID_FOR_SEAT=input-acpi-PNP0C0C_00 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-PNP0C0C:00 E: ID_PATH_TAG=acpi-PNP0C0C_00 E: KEY=10 0 E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw E: NAME=Power Button E: PHYS=PNP0C0C/button/input0 E: PRODUCT=19/0/1/0 E: PROP=0 E: SUBSYSTEM=input E: TAGS=:seat: E: USEC_INITIALIZED=66418 P: /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2/event0 N: input/event0 E: BACKSPACE=guess E: DEVNAME=/dev/input/event0 E: DEVPATH=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2/event0 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-PNP0C0C:00 E: ID_PATH_TAG=acpi-PNP0C0C_00 E: MAJOR=13 E: MINOR=64 E: SUBSYSTEM=input E: TAGS=:power-switch: E: USEC_INITIALIZED=356634 E: XKBLAYOUT=fi E: XKBMODEL=pc105 P: /devices/pci:00/:00:0b.1/usb1/1-6/1-6.3/1-6.3:1.0/0003:03F9:0100.0001/input/input4 E: DEVPATH=/devices/pci:00/:00:0b.1/usb1/1-6/1-6.3/1-6.3:1.0/0003:03F9:0100.0001/input/input4 E: EV=120013 E: ID_BUS=usb E: ID_FOR_SEAT=input-pci-_00_0b_1-usb-0_6_3_1_0 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_INPUT_KEYBOARD=1 E: ID_MODEL=Keytronic_USB_Keyboard E: ID_MODEL_ENC=Keytronic\x20USB\x20Keyboard E: ID_MODEL_ID=0100 E: ID_PATH=pci-:00:0b.1-usb-0:6.3:1.0 E: ID_PATH_TAG=pci-_00_0b_1-usb-0_6_3_1_0 E: ID_REVISION=0102 E: ID_SERIAL=Key_Tronic_Keytronic_USB_Keyboard E: ID_TYPE=hid E: ID_USB_DRIVER=usbhid E: ID_USB_INTERFACES=:030101: E: ID_USB_INTERFACE_NUM=00 E: ID_VENDOR=Key_Tronic E: ID_VENDOR_ENC=Key\x20Tronic E: ID_VENDOR_ID=03f9 E: KEY=10007 ff9f207ac14057ff febeffdfffef fffe E: LED=7 E: MODALIAS=input:b0003v03F9p0100e0110-e0,1,4,11,14,k71,72,73,74,75,77,79,7A,7B,7C,7D,7E,7F,80,81,82,83,84,85,86,87,88,89,8A,8C,8E,96,98,9E,9F,A1,A3,A4,A5,A6,AD,B0,B1,B2,B3,B4,B7,B8,B9,BA,BB,BC,BD,BE,BF,C0,C1,C2,F0,ram4,l0,1,2,sfw E: MSC=10 E: NAME=Key Tronic Keytronic USB Keyboard E: PHYS=usb-:00:0b.1-6.3/input0 E: PRODUCT=3/3f9/100/110 E: PROP=0 E: SUBSYSTEM=input E: TAGS=:seat: E: UNIQ= E: USEC_INITIALIZED=3632 P: /devices/pci:00/:00:0b.1/usb1/1-6/1-6.3/1-6.3:1.0/0003:03F9:0100.0001/input/input4/event2 N: input/event2 S: input/by-id/usb-Key_Tronic_Keytronic_USB_Keyboard-event-kbd S: input/by-path/pci-:00:0b.1-usb-0:6.3:1.0-event-kbd E: BACKSPACE=guess E: DEVLINKS=/dev/input/by-id/usb-Key_Tronic_Keytronic_USB_Keyboard-event-kbd /dev/input/by-path/pci-:00:0b.1-usb-0:6.3:1.0-event-kbd E: DEVNAME=/dev/input/event2 E: DEVPATH=/devices/pci:00/:00:0b.1/usb1/1-6/1-6.3/1-6.3:1.0/0003:03F9:0100.0001/input/input4/event2 E: ID_BUS=usb E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_INPUT_KEYBOARD=1 E: ID_MODEL=Keytronic_USB_Keyboard E: ID_MODEL_ENC=Keytronic\x20USB\x20Keyboard E: ID_MODEL_ID=0100 E:
Bug#726154: xserver-xorg-video-radeon: conffiles not removed
Package: xserver-xorg-video-radeon Followup-For: Bug #726154 Please note Debian Policy version 3.9.5.0 at section: 10.7.3 Packages should remove all obsolete configuration files without local changes during upgrades. The `dpkg-maintscript-helper' tool, available from the `dpkg' package since _Wheezy_, can help with this. Cheers! Martin-Éric -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/debian-x
Bug#756475: xserver-xorg-video-radeon: obsolete-conffile /etc/modprobe.d/radeon-kms.conf
Package: xserver-xorg-video-radeon Version: 1:7.4.0-2 Severity: normal $ adequate xserver-xorg-video-radeon xserver-xorg-video-radeon: obsolete-conffile /etc/modprobe.d/radeon-kms.conf For information on how to fix this, please read: man dh_installdeb man dpkg-maintscript-helper Thanks! -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Oct 25 2008 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2528112 Jul 18 02:04 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 3.14-1-686-pae (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-4) ) #1 SMP Debian 3.14.12-1 (2014-07-11) Xorg X server log files on system: -- -rw-r--r-- 1 root root 10965 Jan 5 2013 /var/log/Xorg.7.log -rw-r--r-- 1 root root 7647 Jan 5 2013 /var/log/Xorg.9.log -rw-r--r-- 1 root root 7647 Jan 5 2013 /var/log/Xorg.8.log -rw-r--r-- 1 root root 7647 Jan 5 2013 /var/log/Xorg.6.log -rw-r--r-- 1 root root 7080 Jul 20 23:43 /var/log/Xorg.3.log -rw-r--r-- 1 root root 7080 Jul 20 23:43 /var/log/Xorg.2.log -rw-r--r-- 1 root root 7080 Jul 20 23:43 /var/log/Xorg.5.log -rw-r--r-- 1 root root 7080 Jul 20 23:43 /var/log/Xorg.4.log -rw-r--r-- 1 root root 46420 Jul 21 15:09 /var/log/Xorg.1.log -rw-r--r-- 1 root root 49411 Jul 22 20:37 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 25237.869] X.Org X Server 1.15.99.904 (1.16.0 RC 4) Release Date: 2014-07-07 [ 25237.870] X Protocol Version 11, Revision 0 [ 25237.870] Build Operating System: Linux 3.2.0-4-amd64 i686 Debian [ 25237.870] Current Operating System: Linux suomi 3.14-1-686-pae #1 SMP Debian 3.14.12-1 (2014-07-11) i686 [ 25237.870] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.14-1-686-pae root=UUID=cd9a1998-9fb2-4208-aba6-bc2ba8f5e36a ro panic=15 video=TV-1:d quiet splash [ 25237.870] Build Date: 08 July 2014 03:58:16PM [ 25237.870] xorg-server 2:1.15.99.904-1 (http://www.debian.org/support) [ 25237.870] Current version of pixman: 0.32.6 [ 25237.870]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 25237.870] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 25237.870] (==) Log file: /var/log/Xorg.0.log, Time: Tue Jul 22 08:04:46 2014 [ 25237.965] (==) Using system config directory /usr/share/X11/xorg.conf.d [ 25238.394] (==) No Layout section. Using the first Screen section. [ 25238.394] (==) No screen section available. Using defaults. [ 25238.394] (**) |--Screen Default Screen Section (0) [ 25238.394] (**) | |--Monitor default monitor [ 25238.395] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [ 25238.395] (==) Automatically adding devices [ 25238.395] (==) Automatically enabling devices [ 25238.395] (==) Automatically adding GPU devices [ 25238.581] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [ 25238.581]Entry deleted from font path. [ 25238.581] (WW) The directory /usr/share/fonts/X11/100dpi/ does not exist. [ 25238.581]Entry deleted from font path. [ 25238.581] (WW) The directory /usr/share/fonts/X11/75dpi/ does not exist. [ 25238.581]Entry deleted from font path. [ 25238.639] (WW) The directory /usr/share/fonts/X11/100dpi does not exist. [ 25238.639]Entry deleted from font path. [ 25238.639] (WW) The directory /usr/share/fonts/X11/75dpi does not exist. [ 25238.639]Entry deleted from font path. [ 25238.639] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/Type1, built-ins [ 25238.639] (==) ModulePath set to /usr/lib/xorg/modules [ 25238.639] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 25238.639] (II) Loader magic: 0xb7761700 [ 25238.639] (II) Module ABI versions: [ 25238.639]X.Org ANSI C Emulation: 0.4 [ 25238.639]X.Org Video Driver: 18.0 [ 25238.639]X.Org XInput driver : 21.0 [ 25238.639]X.Org Server Extension : 8.0 [ 25238.640] (II) xfree86: Adding drm device (/dev/dri/card0) [ 25238.644] (--) PCI:*(0:0:2:0) 8086:27a2:1028:0201 rev 3, Mem @ 0xeff0/524288, 0xd000/268435456, 0xefec/262144, I/O @ 0xeff8/8 [
Bug#755701: False positive
Hi! I think the blank screen is due to a BTRFS hang bug in kernel 3.15 and 3.16. BTRFS hangs then, processes go into D State, screen blanker wants to access harddisk unblanking and hangs then to. Feel free to close. Ciao, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/8473675.NHUN7Nigv1@merkaba
Bug#750129: libxkbcommon0: Please package latest upstream release (0.4.2)
Package: libxkbcommon0 Version: 0.4.0-1 Severity: wishlist Dear Maintainer, please update the package to the latest upstream release. This is needed to build Qt 5.3 which requires 0.4.1, the currently provided 0.4.0 is not sufficient to build Qt 5.3. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libxkbcommon0 depends on: ii libc6 2.18-7 ii multiarch-support 2.18-7 ii xkb-data 2.11-1 libxkbcommon0 recommends no packages. libxkbcommon0 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140601200703.725.68137.report...@martin-thinkpad.fritz.box
Bug#749646: x11-xserver-utils depends on cpp
Package: x11-xserver-utils Version: 7.7~3 The packages x11-xserver-utils and x11-apps both depend on cpp. Since these are miscellaneous assortment of X applications and not development tools, I think they should not depend on cpp. There are people like myself, who like to keep their installations clean and minimal, without packages that they don't need. Or am I mistaken and cpp is needed for x11-xserver-utils to work? I am using Debian Wheezy -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/538645b4.7000...@aol.com
Bug#598819: Confirmed on Fujitsu Esprimo workstation
- Ursprüngliche Mail - Am 13.09.2013 um 12:13 schrieb Martin Steigerwald: […] I attach kdm.log and lspci.txt Its a workstation in a training center, I do not have always access to. Upgrading driver to newest unstable stuff aka: [...] didn´t help either. (hmmm, I see some libdrm modules still being around, but I think it would use libdrm-nouveau2). The most important piece to upgrade would be the kernel. I don't think it will help, but if you want to report your problem upstream, please try a newer kernel first. Kernel running was: Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.46-1+deb7u1 There's 3.10 in wheezy-backports, jessie and sid, and 3.11 in experimental. Will try when creating the new Wheezy training image or holding next training. If it doesn't work I just use the proprietary driver. (Again I know why I personally don't buy NVidia cards.) I suspect this being an upstream bug. Duh! _All_ bugs in this package are upstream bugs, in this case https://bugs.freedesktop.org/show_bug.cgi?id=47288 seems to be related to your problem. Thanks, I will follup there. Ciao, -- Martin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2003878482.2577529.1379317260451.javamail.zim...@teamix.de
Bug#598819: Confirmed on Fujitsu Esprimo workstation
Hi! I can confirm this on a Fujitsu Esprimo E BS015 workstation with Debian Wheezy: 00:05.0 VGA compatible controller [0300]: NVIDIA Corporation C51 [GeForce 6150 LE] [10de:0241] (rev a2) I attach kdm.log and lspci.txt Its a workstation in a training center, I do not have always access to. Upgrading driver to newest unstable stuff aka: root@es5601:~# apt-show-versions | egrep (mesa|nouveau|libdrm) glx-alternative-mesa/sid uptodate 0.4.0 libdrm-intel1/wheezy uptodate 2.4.40-1~deb7u2 libdrm-nouveau1a/wheezy uptodate 2.4.40-1~deb7u2 libdrm-nouveau2/sid uptodate 2.4.46-2 libdrm-radeon1/wheezy uptodate 2.4.40-1~deb7u2 libdrm2/sid uptodate 2.4.46-2 libgl1-mesa-dri/sid uptodate 9.1.6-2+b1 libgl1-mesa-glx/sid uptodate 9.1.6-2+b1 libglapi-mesa/sid uptodate 9.1.6-2+b1 libglu1-mesa/sid uptodate 9.0.0-1 mesa-utils/sid uptodate 8.1.0-2 xserver-xorg-video-nouveau/sid uptodate 1:1.0.9-2+b1 didn´t help either. (hmmm, I see some libdrm modules still being around, but I think it would use libdrm-nouveau2). I have a full output of dmidecode available in case you need any part of it. Kernel running was: Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.46-1+deb7u1 I also tested with empty X.org configuration to make sure its not one configuration option. Proprietary NVidia driver packages were completely removed. I now installed them again to get back gfx output. I suspect this being an upstream bug. I would like to switch to OSS driver with when I create a Wheezy image for it, but I can keep it at the proprietary driver as well. The Wheezy I tested this on I upgraded to from Squeeze. Ciao, -- Martin Steigerwald - teamix GmbH - http://www.teamix.de gpg: 19E3 8D42 896F D004 08AC A0CA 1E10 C593 0399 AE90 Server terminated successfully (0). Closing log file. X.Org X Server 1.12.4 Release Date: 2012-08-27 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.2.0-4-amd64 x86_64 Debian Current Operating System: Linux es5601 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1+deb7u1 x86_64 Kernel command line: root=UUID=bf9d5a55-d0ad-4d85-9282-4673412a8a33 vga=791 ro Build Date: 17 April 2013 10:22:47AM xorg-server 2:1.12.4-6 (Julien Cristau jcris...@debian.org) Current version of pixman: 0.26.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Fri Sep 13 11:14:58 2013 (==) Using config directory: /etc/X11/xorg.conf.d (==) Using system config directory /usr/share/X11/xorg.conf.d Fatal server error: no screens found Please consult the The X.Org Foundation support at http://wiki.x.org for help. Please also check the log file at /var/log/Xorg.0.log for additional information. Server terminated with error (1). Closing log file. X.Org X Server 1.12.4 Release Date: 2012-08-27 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.2.0-4-amd64 x86_64 Debian Current Operating System: Linux es5601 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1+deb7u1 x86_64 Kernel command line: root=UUID=bf9d5a55-d0ad-4d85-9282-4673412a8a33 vga=791 ro Build Date: 17 April 2013 10:22:47AM xorg-server 2:1.12.4-6 (Julien Cristau jcris...@debian.org) Current version of pixman: 0.26.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Fri Sep 13 11:16:10 2013 (==) Using config directory: /etc/X11/xorg.conf.d (==) Using system config directory /usr/share/X11/xorg.conf.d Fatal server error: no screens found Please consult the The X.Org Foundation support at http://wiki.x.org for help. Please also check the log file at /var/log/Xorg.0.log for additional information. Server terminated with error (1). Closing log file. X.Org X Server 1.12.4 Release Date: 2012-08-27 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.2.0-4-amd64 x86_64 Debian Current Operating System: Linux es5601 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1+deb7u1 x86_64 Kernel command line: root=UUID=bf9d5a55-d0ad-4d85-9282-4673412a8a33 vga=791 ro Build Date: 17 April 2013 10:22:47AM xorg-server 2:1.12.4-6 (Julien Cristau jcris...@debian.org) Current version of pixman: 0.26.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Fri Sep 13 11:17:41 2013
Bug#719518: /usr/bin/X: symbol lookup error: intel_drv.so: pixman_glyph_cache_create
Package: xserver-xorg-video-intel Version: 2:2.21.14-3 Severity: grave Justification: renders package unusable Dear Maintainer, Latest version of xserver-xorg-video-intel causes X to crash with the error in the description -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Mar 6 12:43 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2044664 Apr 17 07:40 /usr/bin/Xorg Diversions concerning libGL are in place diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by glx-diversions diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2 to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by glx-diversions diversion of /usr/lib/libGL.so.1.2.0 to /usr/lib/mesa-diverted/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so by glx-diversions VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev ff) Xorg X server configuration file status: -rw-r--r-- 1 root root 181 Aug 12 13:54 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: --- Section Device Identifier intel Driver intel Option AccelMethod sna # Option XAANoOffscreenPixmaps true # Option Tear free true EndSection /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 3.9-1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.7.3 (Debian 4.7.3-5) ) #1 SMP Debian 3.9.8-1 Xorg X server log files on system: -- -rw-r--r-- 1 root root 16144 Jun 14 16:18 /var/log/Xorg.1.log -rw-r--r-- 1 root bumblebee 18392 Aug 12 12:11 /var/log/Xorg.8.log -rw-r--r-- 1 root root 10426 Aug 12 14:13 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [32.396] X.Org X Server 1.12.4 Release Date: 2012-08-27 [32.396] X Protocol Version 11, Revision 0 [32.396] Build Operating System: Linux 3.2.0-4-amd64 x86_64 Debian [32.396] Current Operating System: Linux ncc-74656-a 3.9-1-amd64 #1 SMP Debian 3.9.8-1 x86_64 [32.396] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.9-1-amd64 root=UUID=5d9ef714-6851-41f2-8255-d5492f4ae6c1 ro quiet pcie_aspm=force i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1 add_efi_memmap acpi_osi=!Windows 2012 [32.396] Build Date: 17 April 2013 10:22:47AM [32.396] xorg-server 2:1.12.4-6 (Julien Cristau jcris...@debian.org) [32.396] Current version of pixman: 0.26.0 [32.396]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [32.396] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [32.396] (==) Log file: /var/log/Xorg.0.log, Time: Mon Aug 12 14:13:16 2013 [32.396] (==) Using config file:
Bug#657215: [PATCH videoproto] Xvproto: fix xvEncodingInfo to match actual wire protocol
On 10 June 2013 11:55, Julien Cristau jcris...@debian.org wrote: On Mon, Jun 10, 2013 at 11:41:00 +0200, Daniel Martin wrote: On 9 June 2013 19:00, Julien Cristau jcris...@debian.org wrote: The padding is *before* the rate field, so the rate is placed on a 32bit boundary. This change adds explicit padding between height and rate, and removes extraneous padding after the rate field, which the server never sent and xlib never read. This changes sizeof(xvEncodingInfo). Hopefully that's not a big deal as clients only see the Xlib structure XvEncodingInfo. (Hopefully, I'm right with that): I think that's an ABI change and a bit more difficult. Think about an X server, which is compiled against a xvproto version without that change and the lib compiled against xvproto with that change. In that case the lib would start to read the encoding info, where the X server just sended those extraneous pad bytes. No. As said in the commit message, the server never sent the extraneous pad bytes, so this patch doesn't change either the server or libXv behaviour. Both it and libXv use sz_xvEncodingInfo, which is ok. Sorry, after putting it side by side on a paper I clearly saw it. With that it's: Reviewed-by me. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cadscph26zgvjfccyxhryay1gc2wjd2rr-2w91ft6fkeeivy...@mail.gmail.com
Bug#657215: [PATCH videoproto] Xvproto: fix xvEncodingInfo to match actual wire protocol
On 9 June 2013 19:00, Julien Cristau jcris...@debian.org wrote: The padding is *before* the rate field, so the rate is placed on a 32bit boundary. This change adds explicit padding between height and rate, and removes extraneous padding after the rate field, which the server never sent and xlib never read. This changes sizeof(xvEncodingInfo). Hopefully that's not a big deal as clients only see the Xlib structure XvEncodingInfo. (Hopefully, I'm right with that): I think that's an ABI change and a bit more difficult. Think about an X server, which is compiled against a xvproto version without that change and the lib compiled against xvproto with that change. In that case the lib would start to read the encoding info, where the X server just sended those extraneous pad bytes. I just saw that the reply structure itself (xvQueryEncodingsReply) has such extraneous padding too: ... CARD32 length B32; CARD16 num_encodings B16; CARD32 padl3 B32; ... And even without this padding sz_xvQueryEncodingsReply=32 is wrong, as the fields sum up to 34 and with that padding we're at 36. Cheers, Daniel Martin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CADscph3sgfHoCUB3YTtrihCGe5SBSJ0m22n8Wc9oVz=8nmw...@mail.gmail.com
Bug#637958: Please close
The battery on the machine in question was faulty and replacing it seems to have resolved this bug. I still don't understand how it was causing the behaviour I saw, nor why it seemed to be (semi-)repeatable. Thank you all for your help and patience. Cheers, - Martin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1362581483.28048.27.camel@raphael
Bug#698229: [Intel 965G] GPU Hangs (possibly bug #608782 duplicate)
Package: xserver-xorg-video-intel Version: 2:2.20.14-1 In X (I'm using Openbox with no DM), the mouse pointer suddenly freezes. The mouse seems to actually be moving (buttons highlight when rolled over), but the pointer is frozen in one spot. The system is still usable via keyboard, however, if I try to switch to any TTY, it freezes completely. The same happens if I try to kill X via CTRL+ALT+BACKSPACE or kill the X-process. The X.org-log says that the GPU hangs I'm not able to tell what triggers this hang, it appears to happen randomly from normal use of the GUI. I'm using LinuxBBQ (Debian Unstable), with xserver-xorg-video-intel package from Experimental. I had the same problem with the package in Unstable. The problem may have been more frequent in the Unstable version. I'll paste the Xorg-log. If there's anything else I should attach, let me know. [58.039] X.Org X Server 1.12.4 Release Date: 2012-08-27 [58.039] X Protocol Version 11, Revision 0 [58.039] Build Operating System: Linux 3.2.0-4.drm-amd64 x86_64 Debian [58.039] Current Operating System: Linux lynet 3.7-2.towo-siduction-amd64 #1 SMP PREEMPT Sat Jan 12 13:52:15 UTC 2013 x86_64 [58.040] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.7-2.towo-siduction-amd64 root=UUID=fca240e0-3568-42c6-8a59-0c1e4c01bec1 ro quiet init=/bin/systemd [58.040] Build Date: 29 November 2012 07:18:16PM [58.040] xorg-server 2:1.12.4-4 (Julien Cristau jcris...@debian.org) [58.040] Current version of pixman: 0.26.0 [58.040]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [58.040] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [58.040] (==) Log file: /var/log/Xorg.0.log, Time: Tue Jan 15 15:22:37 2013 [58.078] (==) Using system config directory /usr/share/X11/xorg.conf.d [58.085] (==) No Layout section. Using the first Screen section. [58.085] (==) No screen section available. Using defaults. [58.086] (**) |--Screen Default Screen Section (0) [58.086] (**) | |--Monitor default monitor [58.086] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [58.086] (==) Automatically adding devices [58.086] (==) Automatically enabling devices [58.151] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [58.151]Entry deleted from font path. [58.164] (WW) The directory /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType does not exist. [58.164]Entry deleted from font path. [58.164] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [58.164] (==) ModulePath set to /usr/lib/xorg/modules [58.164] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [58.164] (II) Loader magic: 0x7f5b633e4ae0 [58.164] (II) Module ABI versions: [58.164]X.Org ANSI C Emulation: 0.4 [58.164]X.Org Video Driver: 12.1 [58.164]X.Org XInput driver : 16.0 [58.164]X.Org Server Extension : 6.0 [58.165] (--) PCI:*(0:0:2:0) 8086:29a2:a0a0:062a rev 2, Mem @ 0xfd80/1048576, 0xd000/268435456, I/O @ 0xff00/8 [58.165] (II) Open ACPI successful (/var/run/acpid.socket) [58.165] (II) LoadModule: extmod [58.211] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so [58.226] (II) Module extmod: vendor=X.Org Foundation [58.226]compiled for 1.12.4, module version = 1.0.0 [58.226]Module class: X.Org Server Extension [58.226]ABI class: X.Org Server Extension, version 6.0 [58.226] (II) Loading extension SELinux [58.226] (II) Loading extension MIT-SCREEN-SAVER [58.226] (II) Loading extension XFree86-VidModeExtension [58.226] (II) Loading extension XFree86-DGA [58.226] (II) Loading extension DPMS [58.226] (II) Loading extension XVideo [58.226] (II) Loading extension XVideo-MotionCompensation [58.226] (II) Loading extension X-Resource [58.226] (II) LoadModule: dbe [58.226] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so [58.227] (II) Module dbe: vendor=X.Org Foundation [58.227]compiled for 1.12.4, module version = 1.0.0 [58.227]Module class: X.Org Server Extension [58.227]ABI class: X.Org Server Extension, version 6.0 [58.227] (II) Loading extension DOUBLE-BUFFER [58.227] (II) LoadModule: glx [58.227] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [58.234] (II) Module glx: vendor=X.Org Foundation [58.234]compiled
Geode 2.11.14 released
Upstream went ahead and released as Geode 2.11.14 what had been pushed over the past few months into Debian/unstable as a patched 2.11.13 source. I've already prepared a 2.11.14-1 package for Debian/unstable. Sponsors are welcome to perform the upload. Regards, Martin-Éric -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAPZXPQf+zpOO=NkWbrodNszZv-sCs9-acDdtdetn=y1ctky...@mail.gmail.com
Bug#690296: xserver-xorg-video-intel: /etc/modprobe.d/i915-kms.conf reported as obsolete config
Package: xserver-xorg-video-intel Version: 2:2.19.0-6 Severity: normal /etc/modprobe.d/i915-kms.conf is reported as obsolete by dpkg-status. It probably needs dpkg-maintscript-helper actions in postinst. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1001, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xserver-xorg-video-intel depends on: ii libc6 2.13-35 ii libdrm-intel1 2.4.33-3 ii libdrm22.4.33-3 ii libpciaccess0 0.13.1-2 ii libudev0 175-7 ii libx11-6 2:1.5.0-1 ii libx11-xcb12:1.5.0-1 ii libxcb-dri2-0 1.8.1-1 ii libxcb-util0 0.3.8-2 ii libxcb11.8.1-1 ii libxext6 2:1.3.1-2 ii libxfixes3 1:5.0-4 ii libxv1 2:1.0.7-1 ii libxvmc1 2:1.0.7-1 ii xserver-xorg-core [xorg-video-abi-12] 2:1.12.3.902-1 xserver-xorg-video-intel recommends no packages. xserver-xorg-video-intel suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121012083845.10026.58189.report...@tupla.lan
Bug#684931: /usr/share/x11/xkb/symbols/fi: AltGr problem
2012/8/30 Josselin Mouette j...@debian.org: Le lundi 20 août 2012 à 17:08 +0300, Martin-Éric Racine a écrit : I'm begining to wonder if GTK3 or GNOME3 maintain their own (presumably outdated) copies of the xkb-data keymaps? Yes. http://git.gnome.org/browse/gtk+/tree/gtk/gtkimcontextsimpleseqs.h Thanks for the info, Joss. At least, we now know what tool is used to generate this, so we might be in a position to produce a patch. However, I'm not sure of which Debian source package this corresponds to. Something tells me that you might know, however, so could you please reassign it to the correct one? Thanks! Martin-Éric -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAPZXPQcujQJaMrCM7yTYLuWkRRk-r7=9tvy+p7es_nf2whf...@mail.gmail.com
Bug#684931: /usr/share/x11/xkb/symbols/fi: AltGr problem
2012/8/21 Troy Korjuslommi t...@tksoft.com: I would focus on the input method handling in gnome. If you set xim as IM in gnome, things work. Therefore, the logical starting point for debugging is the default IM gnome uses. I didn't make it clear, but the bugs I filed a couple of years back were gnome bugs. I am not in front of the right machine right now, but as I recall the effort didn't produce any results. It might even be that I never got replies other than this is not the right place to file a bug. Please file at XXX, and at XXX I was told to file at YYY. I might be mistaken, since it's a while back, but I do remember feeling frustrated at the process. I just verified and the compose sequence indeed works as expected in an xterm within a gnome-shell session. However, it fails to work in Firefox, gedit, gnome-terminal, LibreOffice and Pidgin — all of which are based on some GTK variant. Martin-Éric -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/capzxpqep_odvk+p01dlpjkm+0rlheazgynhsyiqv61ck+tg...@mail.gmail.com
Bug#684931: /usr/share/x11/xkb/symbols/fi: AltGr problem
2012/8/20 Troy Korjuslommi t...@tksoft.com: I actually filed the same bug a couple of years ago, as I recall. The behavior is the same, so no change seems to have taken place. Some debugging notes first. Always try X11 apps first, to see if the problem is with X11. If X11 works, then the problem is with something on top of X11, usually GTK or KDE. The problem with X11 can be with a number of things such as the key symbols .h file, the Compose file, or the actual file for the specific keyboard. In this case, I tried entering U+0111 (Altgr-§-d) with xkb-data version 1.8-2 on debian stable, and xkb-data version 2.5-1ubuntu1.3 on the latest desktop ubuntu. I got the same results on both. If you try X11 (xterm, xev) everything works. Same for KDE (kaffeine et al). If you open gnome-terminal or some other gnome app, you will first get only a plain d. To rule out font problems, paste § to the gnome app. It should show up just fine. The solution is to change to the XIM input method. You can do this from the right mouse button for some apps, but for others you have to fiddle with the input settings globally. Once XIM is set as the input method, you get your Islandic đ. The behavior is obviously still wrong. GTK apps should work without the users having to fiddle with their input method settings. All input methods (at least the default one) should understand all correct input. However, I hope the above demonstrated conclusively that the problem is not with X11 or its configurations. The problem lies with input methods other than XIM when using GTK. I'm begining to wonder if GTK3 or GNOME3 maintain their own (presumably outdated) copies of the xkb-data keymaps? At least, what is shown whenever selecting Show keyboard map from the keyboard applet in gnome-shell doesn't quite match what I'm supposed to be using (fi-Kotoistus keymap), which might explain other problems such as this unability to generate D-slash or L-slash using only compose sequences from the Kotoistus keymap within GNOME applications. Martin-Éric -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/capzxpqemx1q0npdxxkcn7ry0hs4vzs7rvoo89xcquo51qvl...@mail.gmail.com
Bug#576565: kotoistus-variant of fi-keyboard is too old
2012/8/14 Martin-Éric Racine martin-eric.rac...@iki.fi: ma, 2010-04-05 kello 20:01 +0300, Juhapekka Tolvanen kirjoitti: Package: xkb-data Version: 1.8-1 Severity: normal Please compare this file: /usr/share/X11/xkb/symbols/fi With this: http://kotoistus.tksoft.com/linux/symbols_fi.txt It is upstream version of kotoistus-variant of fi-keyboard. Please note that Troy's version could never be considered as upstream. Basically, the Finnish keymap at FreeDesktop.org is canonical to the X11 universe so, for any changes to this to be merged upstream, they have to be submitted to the FreeDesktop.org Bugzilla as a patch. Alternately, some of us might be persuaded to merge such a patch as an an attachment to this bug report, provided that it comes accompanied with proper documentation to justify the changes and that it applies cleanly on whatever currently sits in the X.org Git repository. Terveisin, Martin-Éric Actually, comparing with the version of xkb-data currently in Wheezy (2.5.1-1), I notice that the symbols defined for the Kotoistus keymap are the exact same as in Troy's version. Only the comments are arranged differently. Thus, I'd really like to know if this bug remains an issue and, if yes, exactly how? Otherwise, let's close it. Martin-Éric -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAPZXPQdauHEQ=e+W0v5F�hwdsdauzcyjvi5mu5dvq+wub...@mail.gmail.com
Bug#684931: /usr/share/X11/xkb/symbols/fi: AltGr § doesn't produce a deadkey slash as expected
Package: xkb-data Version: 2.5.1-1 Severity: normal On a standard Finnish keyboard layout, the § key combined with AltGr is supposed to produce a deadkey slash. This would be used to produce either slash-L for Polish names or slash-D for Vietnamese names. Yet, the keypress is not a deadkey in practice. Pressing §+AltGr, followed by either D or L only produces a normal D or L, instead of an accented one. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1001, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.5-trunk-686-pae (SMP w/2 CPU cores) Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120814201327.6208.51486.report...@henna.lan
Bug#576565: kotoistus-variant of fi-keyboard is too old
ma, 2010-04-05 kello 20:01 +0300, Juhapekka Tolvanen kirjoitti: Package: xkb-data Version: 1.8-1 Severity: normal Please compare this file: /usr/share/X11/xkb/symbols/fi With this: http://kotoistus.tksoft.com/linux/symbols_fi.txt It is upstream version of kotoistus-variant of fi-keyboard. Please note that Troy's version could never be considered as upstream. Basically, the Finnish keymap at FreeDesktop.org is canonical to the X11 universe so, for any changes to this to be merged upstream, they have to be submitted to the FreeDesktop.org Bugzilla as a patch. Alternately, some of us might be persuaded to merge such a patch as an an attachment to this bug report, provided that it comes accompanied with proper documentation to justify the changes and that it applies cleanly on whatever currently sits in the X.org Git repository. Terveisin, Martin-Éric -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1344977248.6688.11.ca...@henna.lan
Bug#681981: Minor package description issues
Package: compizconfig-backend-gconf Version: 0.8.4-1 Severity: wishlist X-Debbugs-CC: debian-l10n-engl...@lists.debian.org Dear Maintainer, there are some minor (mainly orthographic) issues with the package description (1): Description: Compiz Fusion configuration system - gconf backend Compiz Fusion is the result of the re-unification of the Beryl-project and the community around the Compiz Window Manager. It seeks to provide an easy and fun-to-use windowing environment, allowing use of the graphics hardware to provide impressive effects, amazing speed and unrivalled usefulness . This package provides the gconf-based configuration backend for the compiz-fusion plugin system. GNOME uses another spelling for GConf (2). Perhaps you meant reunion instead of re-unification as well. And s/seeks/aims/ would sound better for me. For your convenience I copied a new version into this mail. Description: Compiz Fusion configuration system - GConf backend Compiz Fusion is the result of the reunion of the Beryl project and the community around the Compiz Window Manager. It seeks to provide an easy and fun-to-use windowing environment, allowing use of the graphics hardware to provide impressive effects, amazing speed and unrivalled usefulness. . This package provides the GConf configuration backend for the Compiz Fusion plugin system. Kind regards, Martin 1: http://ddtp.debian.net/ddt.cgi?desc_id=40600 2: http://projects.gnome.org/gconf/ -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5006a909.3020...@gmx.de
Bug#677617: dri: nouveau_vieux segfaults when called from gnome-control-center
2012/6/16 Julien Cristau jcris...@debian.org: On Fri, Jun 15, 2012 at 14:12:53 +0300, Martin-?ric Racine wrote: 0xb0527b94 in ?? () from /usr/lib/i386-linux-gnu/dri/nouveau_vieux_dri.so You need debug symbols. Cheers, Julien I installed the following: libgl1-mesa-dri-dbg libcogl9-dbg libcogl-pango0-dbg Here's an updated trace (note: neither Clutter or gnome-control-center seem to offer any -dbg package): Reading symbols from /usr/bin/gnome-control-center...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/gnome-control-center [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/i686/cmov/libthread_db.so.1. (process:3609): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. (gnome-control-center:3609): Clutter-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. Program received signal SIGSEGV, Segmentation fault. nv04_context_engine (ctx=0x8203cd0) at nv04_context.c:70 70 nv04_context.c: No such file or directory. (gdb) bt #0 nv04_context_engine (ctx=0x8203cd0) at nv04_context.c:70 #1 0xb06e9568 in nv04_emit_tex_obj (ctx=0x8203cd0, emit=65) at nv04_state_tex.c:64 #2 0xb06e75cd in nv04_channel_flush_notify (chan=0x83ce198) at nv04_context.c:99 #3 0xb06c73b1 in nouveau_pushbuf_flush () from /usr/lib/i386-linux-gnu/libdrm_nouveau.so.1 #4 0xb06c7748 in nouveau_grobj_free () from /usr/lib/i386-linux-gnu/libdrm_nouveau.so.1 #5 0xb06e7538 in nv04_context_destroy (ctx=0x8203cd0) at nv04_context.c:161 #6 0xb06e2788 in nouveau_context_destroy (dri_ctx=0x81f25d8) at nouveau_context.c:187 #7 0xb06df00a in driDestroyContext (pcp=0x81f25d8) at ../common/dri_util.c:277 #8 0xb0be282a in ?? () from /usr/lib/i386-linux-gnu/libGL.so.1 #9 0xb0bb96c2 in glXDestroyContext () from /usr/lib/i386-linux-gnu/libGL.so.1 #10 0xb0e9e63c in _cogl_winsys_display_destroy (display=0x8182d68) at ./winsys/cogl-winsys-glx.c:704 #11 0xb0e56d8c in _cogl_display_free (display=0x8182d68) at ./cogl-display.c:59 #12 _cogl_object_display_indirect_free (obj=0x8182d68) at ./cogl-display.c:43 #13 0xb0e58392 in _cogl_object_default_unref (object=0x8182d68) at ./cogl-object.c:96 #14 0xb0e582ef in cogl_object_unref (obj=0x8182d68) at ./cogl-object.c:104 #15 0xb0e5675a in cogl_renderer_check_onscreen_template (renderer=0x81edcb8, onscreen_template=0x8182d30, error=0xbfffec1c) at ./cogl-renderer.c:231 #16 0xb0f14b94 in ?? () from /usr/lib/i386-linux-gnu/libclutter-1.0.so.0 #17 0xb0f4a8bc in ?? () from /usr/lib/i386-linux-gnu/libclutter-1.0.so.0 #18 0xb0f4af07 in ?? () from /usr/lib/i386-linux-gnu/libclutter-1.0.so.0 #19 0xb0f644f1 in ?? () from /usr/lib/i386-linux-gnu/libclutter-1.0.so.0 #20 0xb0f70f5d in ?? () from /usr/lib/i386-linux-gnu/libclutter-1.0.so.0 #21 0xb0f711ad in ?? () from /usr/lib/i386-linux-gnu/libclutter-1.0.so.0 #22 0xb769127a in g_option_context_parse () from /lib/i386-linux-gnu/libglib-2.0.so.0 #23 0xb0f7152e in clutter_init () from /usr/lib/i386-linux-gnu/libclutter-1.0.so.0 #24 0xb0d94e92 in gtk_clutter_init () from /usr/lib/i386-linux-gnu/libclutter-gtk-1.0.so.0 #25 0xb103aef3 in cheese_gtk_init () from /usr/lib/i386-linux-gnu/libcheese-gtk.so.21 #26 0xb1160dd4 in g_io_module_load () from /usr/lib/control-center-1/panels/libuser-accounts.so #27 0xb77e165e in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 #28 0xb776d656 in g_type_module_use () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #29 0xb77e1af9 in g_io_modules_load_all_in_directory_with_scope () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 #30 0xb77e1bb3 in g_io_modules_load_all_in_directory () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 #31 0x08050d42 in ?? () #32 0xb776a507 in g_type_create_instance () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #33 0xb774ccf1 in ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #34 0xb774ea19 in g_object_newv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #35 0xb774efb8 in g_object_new () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #36 0x080515f8 in gnome_control_center_new () #37 0x0804ed49 in main () (gdb) -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/capzxpqfj76-1aemw64lb6-uy73c115j4zdmj8puxsiqar82...@mail.gmail.com
Bug#672601: pointer jumps/bounces after some time of usage (Lenovo ThinkPad x220i)
Quoting Cyril Brulebois k...@debian.org: and let us know the bug number for tracking. #49898 -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120514124646.10381jlcucp5a...@webmail.in-berlin.de
Bug#672601: pointer jumps/bounces after some time of usage (Lenovo ThinkPad x220i)
Package: xserver-xorg-input-synaptics Version: 1.5.99.904-1 Severity: normal After some time of usage, the mouse pointer starts to move (mainly small, fast left-right movements) even when I'm not touching the computer. When I disable the touchpad using gpointing-device-settings and enable it again, it works for some minutes and then I get the same problem again. So my workaround is keeping gpointing-device-settings open and do the disable/enable dance every ten or twenty minutes. The problem occurs also on Squeeze, not only on Wheezy. Searching for the problem, I found forum messages of people running Windows Vista or Windows 7 on other Lenovo machines having the same problem. Maybe this is not a driver problem, but a hardware problem of Lenovo? -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Apr 2 20:09 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2044072 Mar 5 04:21 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/i915-kms.conf: options i915 modeset=1 /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 3.2.0-2-686-pae (Debian 3.2.16-1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-4) ) #1 SMP Mon Apr 30 05:59:35 UTC 2012 Xorg X server log files on system: -- -rw-r--r-- 1 root root 34907 May 12 08:32 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 124.075] X.Org X Server 1.11.4 Release Date: 2012-01-27 [ 124.075] X Protocol Version 11, Revision 0 [ 124.075] Build Operating System: Linux 2.6.32-5-amd64 i686 Debian [ 124.075] Current Operating System: Linux what 3.2.0-2-686-pae #1 SMP Mon Apr 30 05:59:35 UTC 2012 i686 [ 124.075] Kernel command line: BOOT_IMAGE=/vmlinuz-3.2.0-2-686-pae root=/dev/mapper/what-root ro quiet [ 124.075] Build Date: 05 March 2012 04:16:09AM [ 124.075] xorg-server 2:1.11.4-1 (Cyril Brulebois k...@debian.org) [ 124.075] Current version of pixman: 0.24.4 [ 124.075]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 124.075] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 124.075] (==) Log file: /var/log/Xorg.0.log, Time: Sat May 12 08:32:02 2012 [ 124.108] (==) Using system config directory /usr/share/X11/xorg.conf.d [ 124.157] (==) No Layout section. Using the first Screen section. [ 124.157] (==) No screen section available. Using defaults. [ 124.157] (**) |--Screen Default Screen Section (0) [ 124.157] (**) | |--Monitor default monitor [ 124.175] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [ 124.175] (==) Automatically adding devices [ 124.175] (==) Automatically enabling devices [ 124.251] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [ 124.251]Entry deleted from font path. [ 124.334] (WW) The directory /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType does not exist. [ 124.334]Entry deleted from font path. [ 124.334] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 124.334] (==) ModulePath set to /usr/lib/xorg/modules [ 124.334] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 124.360] (II) Loader magic: 0xb7770580 [ 124.360] (II) Module ABI versions: [ 124.360]X.Org ANSI C Emulation: 0.4 [ 124.360]X.Org Video Driver: 11.0 [ 124.360]X.Org XInput driver : 13.0 [ 124.360]X.Org Server Extension : 6.0 [ 124.361] (--) PCI:*(0:0:2:0) 8086:0116:17aa:21da rev 9, Mem @ 0xf000/4194304, 0xe000/268435456, I/O @ 0x5000/64 [ 124.361] (II) Open ACPI successful (/var/run/acpid.socket) [ 124.361] (II) LoadModule: extmod [ 124.384] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so [ 124.414] (II) Module extmod: vendor=X.Org Foundation [ 124.414]compiled for 1.11.4, module version = 1.0.0 [ 124.414]Module class: X.Org Server Extension [ 124.414]ABI class: X.Org Server Extension, version 6.0
Bug#667721: xserver-xorg-video-radeon: abysmal performance
rassign 667721 libcairo2 retitle 667721 X abysmal performance after libcairo upgrade notfound 667721 1:6.14.4-1 found 667721 1.12.0-2 thanks also sprach Michel Dänzer daen...@debian.org [2012.04.06.1302 +0200]: If downgrading libcairo2 to 1.10.2 works around the problem, that's probably the best workaround for now until we get a better handle on the above. Otherwise, Option NoAccel might be feasible if you don't need OpenGL or XVideo acceleration. Indeed, libcairo2 downgrading seems to fix this issue. Thanks to you and Cyril (IRC). Reassigning this bug… -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems no cat has eight tails. a cat has one tail more than no cat. therefore, a cat has nine tails. digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#667721: X bug report
https://bugs.freedesktop.org/show_bug.cgi?id=47266 -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
