Bug#1027142: Correction: Not a permissions but a settings problem
In searching for the cause, I found that the failure of 2D acceleration must be due to a user configuration problem rather than a permissions problem. The system partition and thus the roots folder were newly created, the /home/ partition was taken over from the previous installation. This was created years ago with Debian 9 (at that time with a radeon driver). The 2D acceleration does not work for any of the old users. But it does for a completely new user or the new root-account created during the installation. So there must be a problem with the old user settings that prevents access to the hardware acceleration memory or puts it on a wrong address. No idea which one this should be and where to find it. My solution now is to recreate the user directories and move the data from the old directories there. Users will then have to redo their settings, which is less tragic than not having 2D acceleration. OpenPGP_signature Description: OpenPGP digital signature
Bug#999631: "works for me" - Problem obviously solved
My box is running now for a whole night without problems, including multiple hours of active working with libreoffice writer. Obviously this solution works: create folder and file /etc/X11/xorg.conf.d/20-nouveau.conf and put in: Section "Device" Identifier "NvidiaCard" Driver "nouveau" BusID "PCI:01:00:0" # PCI bus address of the Nvidia GPU here EndSection I'd recommend debian install / upgrade procedure to care for a similiar solution, maybe adopted to the proper debianic way.
Bug#968192: the problem is actually related to XCompose
after learning a bit more about bépo layout, it turns out the problematics keys are all supposed to be dead keys. not being detected as such due to XCompose not implementing them is the reason why it does not work properly So I’ll report this to libx11-data you can close this.
Re: Depends problem. Libc6 is 2.28 but I need 2.29
On 2020-02-15 16:35, Grisha Grybyniuk wrote: > Here it is > > пт, 14 лют. 2020 о 13:31 Grisha Grybyniuk пише: It appears that you have a few entries for ubuntu/disco. This distribution is based on libc6 2.29, which might cause the issue you see there. In general it is not a good idea to mix debian and ubuntu repositories. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#952731: xkb-data: Same for fr layout, reverting to 2.26-2 fixes the problem
Package: xkb-data Followup-For: Bug #952731 Hi, fr [fr (variant) under gnome] stops also to work after upgrading xkb-data. Reverting to 2.26-2 fixes the problem. Regards Jean-Luc -- System Information: Debian Release: bullseye/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-rc3-i7-0.1 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) -- no debconf information
Re: Depends problem. Libc6 is 2.28 but I need 2.29
On Sat, Feb 15, 2020 at 04:35:20PM +0200, Grisha Grybyniuk wrote: > Here it is Anything in /etc/apt/sources.list.d/ ? Also if you install and run apt-show-versions, you can filter out the 'uptodate' lines and see what packages it things are either from unknown sources or too new. -- Len Sorensen
Re: Depends problem. Libc6 is 2.28 but I need 2.29
Ok, I will check. On Thu, Feb 13, 2020, 20:39 Aurelien Jarno wrote: > On 2020-02-13 19:15, Grisha Grybyniuk wrote: > > Hello, I have a depending problem. For clearly understanding I will write > > whole story. So I added a *buster-backports* repository with *main*, > > *contrib*, *non-free*. I run "sudo aptitude update", then "sudo aptitude > > upgrade (dist-upgrade also)" I get a many upgrades and for my drivers and > > firmwares, but there is a one problem I cant upgrade my libvulkan1, > > libvulkan1:i386, > > nvidia-settings, libxnvctrl0 packages becouse of unmet depends, so here > is > > more info: > > Can you please share your /etc/apt/sources.list? > > > sudo aptitude dist-upgrade > > > > The following packages will be upgraded: > > *libvulkan1{b} libvulkan1:i386{b} libxnvctrl0 nvidia-settings{b}* > > 4 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > Need to get 1,165 kB of archives. After unpacking 7,168 B will be used. > > The following packages have unmet dependencies: > > *libvulkan1* : Depends: *libc6* (>= 2.29) but 2.28-10 is installed > > *libvulkan1:i386* : Depends: *libc6:i386* (>= 2.29) but 2.28-10 is > > installed > > There is no buster-backports version of libvulkan1, and the version in > buster doesn't depends on libc6 (>= 2.29). I guess you have more sources > in /etc/apt/sources.list. > > -- > Aurelien Jarno GPG: 4096R/1DDD8C9B > aurel...@aurel32.net http://www.aurel32.net >
Re: Depends problem. Libc6 is 2.28 but I need 2.29
On 2020-02-13 19:15, Grisha Grybyniuk wrote: > Hello, I have a depending problem. For clearly understanding I will write > whole story. So I added a *buster-backports* repository with *main*, > *contrib*, *non-free*. I run "sudo aptitude update", then "sudo aptitude > upgrade (dist-upgrade also)" I get a many upgrades and for my drivers and > firmwares, but there is a one problem I cant upgrade my libvulkan1, > libvulkan1:i386, > nvidia-settings, libxnvctrl0 packages becouse of unmet depends, so here is > more info: Can you please share your /etc/apt/sources.list? > sudo aptitude dist-upgrade > > The following packages will be upgraded: > *libvulkan1{b} libvulkan1:i386{b} libxnvctrl0 nvidia-settings{b}* > 4 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > Need to get 1,165 kB of archives. After unpacking 7,168 B will be used. > The following packages have unmet dependencies: > *libvulkan1* : Depends: *libc6* (>= 2.29) but 2.28-10 is installed > *libvulkan1:i386* : Depends: *libc6:i386* (>= 2.29) but 2.28-10 is > installed There is no buster-backports version of libvulkan1, and the version in buster doesn't depends on libc6 (>= 2.29). I guess you have more sources in /etc/apt/sources.list. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Depends problem. Libc6 is 2.28 but I need 2.29
Hello, I have a depending problem. For clearly understanding I will write whole story. So I added a *buster-backports* repository with *main*, *contrib*, *non-free*. I run "sudo aptitude update", then "sudo aptitude upgrade (dist-upgrade also)" I get a many upgrades and for my drivers and firmwares, but there is a one problem I cant upgrade my libvulkan1, libvulkan1:i386, nvidia-settings, libxnvctrl0 packages becouse of unmet depends, so here is more info: sudo aptitude dist-upgrade The following packages will be upgraded: *libvulkan1{b} libvulkan1:i386{b} libxnvctrl0 nvidia-settings{b}* 4 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 1,165 kB of archives. After unpacking 7,168 B will be used. The following packages have unmet dependencies: *libvulkan1* : Depends: *libc6* (>= 2.29) but 2.28-10 is installed *libvulkan1:i386* : Depends: *libc6:i386* (>= 2.29) but 2.28-10 is installed *nvidia-settings* : Depends: *screen-resolution-extra* (>= 0.18~) which is a virtual package and is not provided by any available package Depends: libc6 (>= 2.29) but 2.28-10 is installed open: 34; closed: 628; defer: 8; conflict: 8 So how you can see that there is a problem with libc6, libc6:i386, and sreen-resolution-extra.
depends problem
Hello, I have a depending problem. For clearly understanding I will write whole story. So I added a *buster-backports* repository with *main*, *contrib*, *non-free*. I run "sudo aptitude update", then "sudo aptitude upgrade (dist-upgrade also)" I get a many upgrades and for my drivers and firmwares, but there is a one problem I cant upgrade my libvulkan1, libvulkan1:i386, nvidia-settings, libxnvctrl0 packages becouse of unmet depends, so here is more info: sudo aptitude dist-upgrade The following packages will be upgraded: *libvulkan1{b} libvulkan1:i386{b} libxnvctrl0 nvidia-settings{b} * 4 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 1,165 kB of archives. After unpacking 7,168 B will be used. The following packages have unmet dependencies: *libvulkan1* : Depends: *libc6* (>= 2.29) but 2.28-10 is installed *libvulkan1:i386* : Depends: *libc6:i386* (>= 2.29) but 2.28-10 is installed *nvidia-settings* : Depends: *screen-resolution-extra* (>= 0.18~) which is a virtual package and is not provided by any available package Depends: libc6 (>= 2.29) but 2.28-10 is installed open: 34; closed: 628; defer: 8; conflict: 8 So how you can see that there is a problem with libc6, libc6:i386, and sreen-resolution-extra. How I know in many distributions libc6 is already 2.29 version. So now is a question - it will be fixed in buster or its need to wait a bullseye Debian 11? And one more thing, I cant understand what I need to do with screen-resolution-extra for fixing my problem, maybe you know? Thanks for your attention, will wait for your answer.
Processed: Re: Bug#947108: Xorg problem preventing bootup
Processing control commands: > reassign -1 xserver-xorg Bug #947108 [x.org] Xorg problem preventing bootup Warning: Unknown package 'x.org' Bug reassigned from package 'x.org' to 'xserver-xorg'. No longer marked as found in versions 1.20.6. Ignoring request to alter fixed versions of bug #947108 to the same values previously set -- 947108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Bug#947108: Xorg problem preventing bootup
Control: reassign -1 xserver-xorg On Vi, 20 dec 19, 23:47:46, Casey Cullen wrote: > Package: X.org > Version: 1.20.6 > Architecture: PPC64 > > When trying to boot into Debian PPC64 on a "cyrus plus" board (Freescale > P5020 e5500 core based PPC64 system), an error is displayed. Below is the > log. This only occurs on PPC64 (does not occur on PowerPC). > Thank you for your assistance. > > [ 922.574] > X.Org X Server 1.20.6 > X Protocol Version 11, Revision 0 > [ 922.592] Build Operating System: Linux 4.19.0-5-powerpc64 ppc64 Debian > [ 922.598] Current Operating System: Linux Fienix > 5.5-a2_A-EON_X5000-05280-g89d577d3-dirty #1 SMP PREEMPT Wed Nov 27 > 12:53:57 CET 2019 ppc64 > [ 922.598] Kernel command line: root=/dev/sdb2 rootdelay=5 > [ 922.612] Build Date: 25 November 2019 09:49:09AM > [ 922.618] xorg-server 2:1.20.6-1 (https://www.debian.org/support) > [ 922.625] Current version of pixman: 0.36.0 > [ 922.638] Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > [ 922.638] Markers: (--) probed, (**) from config file, (==) default > setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > [ 922.666] (==) Log file: "/home/fienix/.local/share/xorg/Xorg.0.log", > Time: Sat Dec 21 00:37:38 2019 > [ 922.673] (==) Using system config directory "/usr/share/X11/xorg.conf.d" > [ 922.674] (==) No Layout section. Using the first Screen section. > [ 922.674] (==) No screen section available. Using defaults. > [ 922.674] (**) |-->Screen "Default Screen Section" (0) > [ 922.674] (**) | |-->Monitor "" > [ 922.675] (==) No monitor specified for screen "Default Screen Section". > Using a default monitor configuration. > [ 922.675] (==) Automatically adding devices > [ 922.675] (==) Automatically enabling devices > [ 922.675] (==) Automatically adding GPU devices > [ 922.675] (==) Max clients allowed: 256, resource mask: 0x1f > [ 922.675] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not > exist. > [ 922.675] Entry deleted from font path. > [ 922.675] (==) 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 > [ 922.675] (==) ModulePath set to "/usr/lib/xorg/modules" > [ 922.675] (II) The server relies on udev to provide the list of input > devices. > If no devices become available, reconfigure udev or disable > AutoAddDevices. > [ 922.675] (II) Loader magic: 0x1279f6ad0 > [ 922.675] (II) Module ABI versions: > [ 922.675] X.Org ANSI C Emulation: 0.4 > [ 922.675] X.Org Video Driver: 24.0 > [ 922.675] X.Org XInput driver : 24.1 > [ 922.675] X.Org Server Extension : 10.0 > [ 922.677] (++) using VT number 1 > > [ 922.680] (II) systemd-logind: took control of session > /org/freedesktop/login1/session/c1 > [ 922.683] (II) xfree86: Adding drm device (/dev/dri/card0) > [ 922.684] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 > paused 0 > [ 922.690] (--) PCI:*(1@0:0:0) 1002:6738:174b:e177 rev 0, Mem @ > 0xc/268435456, 0xc1000/131072, I/O @ 0x1000/256, BIOS @ > 0x/131072 > [ 922.690] (II) LoadModule: "glx" > [ 922.691] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so > [ 922.695] (II) Module glx: vendor="X.Org Foundation" > [ 922.695] compiled for 1.20.6, module version = 1.0.0 > [ 922.695] ABI class: X.Org Server Extension, version 10.0 > [ 922.695] (II) Applying OutputClass "Radeon" to /dev/dri/card0 > [ 922.695] loading driver: radeon > [ 922.695] (==) Matched radeon as autoconfigured driver 0 > [ 922.696] (==) Matched ati as autoconfigured driver 1 > [ 922.696] (==) Matched modesetting as autoconfigured driver 2 > [ 922.696] (==) Matched fbdev as autoconfigured driver 3 > [ 922.696] (==) Assigned the driver to the xf86ConfigLayout > [ 922.696] (II) LoadModule: "radeon" > [ 922.696] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so > [ 922.697] (II) Module radeon: vendor="X.Org Foundation" > [ 922.697] compiled for 1.20.4, module version = 19.1.0 > [ 922.697] Module class: X.Org Video Driver > [ 922.697] ABI class: X.Org Video Driver, version 24.0 > [ 922.697] (II) LoadModule: "ati" > [ 922.698] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so > [ 922.698] (II) Module ati: vendor="X.Org Foundation" > [ 922.698] compiled for 1.20.4, module version = 19.1.0 > [ 922.698] Module class: X.Org Video Driver > [ 922.698] ABI class: X.Org Video Driver, version 24.0 > [ 922.698] (II) LoadModule: "modesetting" > [ 922.698] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so > [ 922.699] (II) Module modesetting:
Bug#944758: Problem solved
Reason was either some amdgpu-pro package or updating libegl to git version.
Bug#943475: xwayland: "resolution" or "dot" or .. problem with rotated second screen
Package: xwayland Version: 2:1.20.4-1 Severity: normal Hello, i use a dual monitor setup, when using the second monitor in landscape mode, all is fine, when using the second monitor in a rotated (right in in this case) mode, the readibility of the screen significantly declines, for example black number become barely readible green number (workrave app as example) i don't if this is related to #914382 , #216161 or #522431 this occured after upgrading to buster, in buster there was no problem hth, Wim -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores) Locale: LANG=nl_BE.utf8, LC_CTYPE=nl_BE.utf8 (charmap=UTF-8) (ignored: LC_ALL set to nl_BE.UTF-8), LANGUAGE=nl_BE:nl (charmap=UTF-8) (ignored: LC_ALL set to nl_BE.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xwayland depends on: ii libaudit1 1:2.8.4-3 ii libbsd0 0.9.1-2 ii libc6 2.28-10 ii libdrm2 2.4.97-1 ii libegl1 1.1.0-1 ii libepoxy0 1.5.3-0.1 ii libgbm1 18.3.6-2 ii libgcrypt20 1.8.4-5 ii libgl1 1.1.0-1 ii libpixman-1-0 0.36.0-1 ii libselinux1 2.8-1+b1 ii libsystemd0 241-7~deb10u1 ii libunwind8 1.2.1-9 ii libwayland-client0 1.16.0-1 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 xserver-common 2:1.20.4-1 xwayland recommends no packages. xwayland suggests no packages. -- no debconf information
Bug#879624: Still a serious problem
Hello all, I upgraded a jessie to buster 6 weeks ago and after reboot was left with the black screen and blinking cursor. After considerable machinations (the details of which I can't remember) I got it working. I have just attempt the same upgrade today on another machine and got the same result - blank screen with flashing cursor. Of course, everything is ok in recovery mode but IMHO the persistence and recurrence of this problem in many hands for going on an entire year suggests that there is something fundamentally wrong with the upgrade process. I am not experienced enough to have a clue as to what might be wrong or where to start fixing it but one would thing, that the numerous and lengthy forum discussions would have led to a clear solution by now. If there is a solution that has yet to be revealed, now it the time. Thank you, Dan Essin
Re: Problem with AMD HD 5670 GPU
On 2019-07-05 5:28 p.m., Philippe Lefèvre wrote: > Sorry, error into the subject > please read Problem with AMD HD 5670 GPU > > Hi all, > > I am stuck with my graphic card since I upgraded my Linux box from > Jessie to Stretch. > Before debian upgade, I had the fglrx proprietary driver which was > removed when upgrade. > > Now the issue is I can't get some structure rendering > For example, in a online game (Champions Of Regnum) my characters are > now nude and other players are not diplayed. > > Is there anyone who knows better than me the arcannes of graphics cards > parameters and who could help me to solve my problem? > (if possible using open source softwares) > > Regards, > Philippe > > > Here are some details of my installation: > > # lsb_release -a | grep Desc > Debian GNU/Linux 9.9 (stretch) > > My card is an AMD HD 5670, my distro is Debian Stretch up to date > # lspci -nn | grep VGA > 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. > [AMD/ATI] Redwood XT [Radeon HD 5670/5690/5730] [1002:68d8] > > As there is no more proprietary drivers available for Debian, I tried to > compile AMD Catalyst(TM) Proprietary Driver-15.201.1151 > The compilation checks fails due to the X server version which is too > high on my box. > # error: Detected X Server version 'XServer 1.19.2_64a' is not supported. > Supported versions are X.Org 6.9 or later, up to XServer 1.10 > (default:v2:x86_64:lib:XServer 1.19.2_64a:none:4.9.0-9-amd64:) > Installation will not proceed. > > The non-free package firmware-amd-graphics (20161130-5) doesn't contain > any driver for HD5670 > > I then installed the recommended open source packages. > > I removed /etc/X11/xorg.conf > > # glxinfo | grep OpenGL > OpenGL vendor string: X.Org > OpenGL renderer string: Gallium 0.4 on AMD REDWOOD (DRM 2.49.0 / > 4.9.0-9-amd64, LLVM 3.9.1) > OpenGL core profile version string: 3.3 (Core Profile) Mesa 13.0.6 > 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 13.0.6 > OpenGL shading language version string: 1.30 > OpenGL context flags: (none) > OpenGL extensions: > OpenGL ES profile version string: OpenGL ES 3.0 Mesa 13.0.6 > OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 > OpenGL ES profile extensions: > > What is installed : > [...] I'd try upgrading these and (at least) libgl1-mesa-dri to stretch-backports, and see if it works better then. -- Earthling Michel Dänzer | https://www.amd.com Libre software enthusiast | Mesa and X developer
Problem with AMD HD 5670 GPU
Sorry, error into the subject please read Problem with AMD HD 5670 GPU Hi all, I am stuck with my graphic card since I upgraded my Linux box from Jessie to Stretch. Before debian upgade, I had the fglrx proprietary driver which was removed when upgrade. Now the issue is I can't get some structure rendering For example, in a online game (Champions Of Regnum) my characters are now nude and other players are not diplayed. Is there anyone who knows better than me the arcannes of graphics cards parameters and who could help me to solve my problem? (if possible using open source softwares) Regards, Philippe Here are some details of my installation: # lsb_release -a | grep Desc Debian GNU/Linux 9.9 (stretch) My card is an AMD HD 5670, my distro is Debian Stretch up to date # lspci -nn | grep VGA 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Redwood XT [Radeon HD 5670/5690/5730] [1002:68d8] As there is no more proprietary drivers available for Debian, I tried to compile AMD Catalyst(TM) Proprietary Driver-15.201.1151 The compilation checks fails due to the X server version which is too high on my box. # error: Detected X Server version 'XServer 1.19.2_64a' is not supported. Supported versions are X.Org 6.9 or later, up to XServer 1.10 (default:v2:x86_64:lib:XServer 1.19.2_64a:none:4.9.0-9-amd64:) Installation will not proceed. The non-free package firmware-amd-graphics (20161130-5) doesn't contain any driver for HD5670 I then installed the recommended open source packages. I removed /etc/X11/xorg.conf # glxinfo | grep OpenGL OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD REDWOOD (DRM 2.49.0 / 4.9.0-9-amd64, LLVM 3.9.1) OpenGL core profile version string: 3.3 (Core Profile) Mesa 13.0.6 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 13.0.6 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 13.0.6 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: What is installed : ii firmware-amd-graphics 20161130-5 all Binary firmware for AMD/ATI graphics chips ii firmware-linux 20161130-5 all Binary firmware for various drivers in the Linux kernel (meta-package) ii firmware-linux-free 3.4 all Binary firmware for various drivers in the Linux kernel ii firmware-linux-nonfree 20161130-5 all Binary firmware for various drivers in the Linux kernel (meta-package) ii firmware-misc-nonfree 20161130-5 all Binary firmware for various drivers in the Linux kernel ii libdrm-amdgpu1:amd64 2.4.74-1 amd64 Userspace interface to amdgpu-specific kernel DRM services -- runtime ii libdrm-amdgpu1:i386 2.4.74-1 i386 Userspace interface to amdgpu-specific kernel DRM services -- runtime ii libdrm-dev:amd64 2.4.74-1 amd64 Userspace interface to kernel DRM services -- development files ii libdrm-intel1:amd64 2.4.74-1 amd64 Userspace interface to intel-specific kernel DRM services -- runtime ii libdrm-intel1:i386 2.4.74-1 i386 Userspace interface to intel-specific kernel DRM services -- runtime ii libdrm-nouveau2:amd64 2.4.74-1 amd64 Userspace interface to nouveau-specific kernel DRM services -- runtime ii libdrm-nouveau2:i386 2.4.74-1 i386 Userspace interface to nouveau-specific kernel DRM services -- runtime ii libdrm-radeon1:amd64 2.4.74-1 amd64 Userspace interface to radeon-specific kernel DRM services -- runtime ii libdrm-radeon1:i386 2.4.74-1 i386 Userspace interface to radeon-specific kernel DRM services -- runtime ii libdrm2:amd64 2.4.74-1 amd64 Userspace interface to kernel DRM services -- runtime ii libdrm2:i386 2.4.74-1 i386 Userspace interface to kernel DRM services -- runtime ii xorg 1:7.7+19 amd64 X.Org X Window System ii xorgxrdp 0.9.1-9+deb9u3 amd64 Remote Desktop Protocol (RDP) modules for X.org ii xserver-xorg 1:7.7+19 amd64
Problem with Firepro WD2100 (AMD)
Hi all, I am stuck with my graphic card since I upgraded my Linux box from Jessie to Stretch. Before debian upgade, I had the fglrx proprietary driver which was removed when upgrade. Now the issue is I can't get some structure rendering For example, in a online game (Champions Of Regnum) my characters are now nude and other players are not diplayed. Is there anyone who knows better than me the arcannes of graphics cards parameters and who could help me to solve my problem? (if possible using open source softwares) Regards, Philippe Here are some details of my installation: # lsb_release -a | grep Desc Debian GNU/Linux 9.9 (stretch) My card is an AMD HD 5670, my distro is Debian Stretch up to date # lspci -nn | grep VGA 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Redwood XT [Radeon HD 5670/5690/5730] [1002:68d8] As there is no more proprietary drivers available for Debian, I tried to compile AMD Catalyst(TM) Proprietary Driver-15.201.1151 The compilation checks fails due to the X server version which is too high on my box. # error: Detected X Server version 'XServer 1.19.2_64a' is not supported. Supported versions are X.Org 6.9 or later, up to XServer 1.10 (default:v2:x86_64:lib:XServer 1.19.2_64a:none:4.9.0-9-amd64:) Installation will not proceed. The non-free package firmware-amd-graphics (20161130-5) doesn't contain any driver for HD5670 I then installed the recommended open source packages. I removed /etc/X11/xorg.conf # glxinfo | grep OpenGL OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD REDWOOD (DRM 2.49.0 / 4.9.0-9-amd64, LLVM 3.9.1) OpenGL core profile version string: 3.3 (Core Profile) Mesa 13.0.6 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 13.0.6 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 13.0.6 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: What is installed : ii firmware-amd-graphics 20161130-5 all Binary firmware for AMD/ATI graphics chips ii firmware-linux 20161130-5 all Binary firmware for various drivers in the Linux kernel (meta-package) ii firmware-linux-free 3.4 all Binary firmware for various drivers in the Linux kernel ii firmware-linux-nonfree 20161130-5 all Binary firmware for various drivers in the Linux kernel (meta-package) ii firmware-misc-nonfree 20161130-5 all Binary firmware for various drivers in the Linux kernel ii libdrm-amdgpu1:amd64 2.4.74-1 amd64 Userspace interface to amdgpu-specific kernel DRM services -- runtime ii libdrm-amdgpu1:i386 2.4.74-1 i386 Userspace interface to amdgpu-specific kernel DRM services -- runtime ii libdrm-dev:amd64 2.4.74-1 amd64 Userspace interface to kernel DRM services -- development files ii libdrm-intel1:amd64 2.4.74-1 amd64 Userspace interface to intel-specific kernel DRM services -- runtime ii libdrm-intel1:i386 2.4.74-1 i386 Userspace interface to intel-specific kernel DRM services -- runtime ii libdrm-nouveau2:amd64 2.4.74-1 amd64 Userspace interface to nouveau-specific kernel DRM services -- runtime ii libdrm-nouveau2:i386 2.4.74-1 i386 Userspace interface to nouveau-specific kernel DRM services -- runtime ii libdrm-radeon1:amd64 2.4.74-1 amd64 Userspace interface to radeon-specific kernel DRM services -- runtime ii libdrm-radeon1:i386 2.4.74-1 i386 Userspace interface to radeon-specific kernel DRM services -- runtime ii libdrm2:amd64 2.4.74-1 amd64 Userspace interface to kernel DRM services -- runtime ii libdrm2:i386 2.4.74-1 i386 Userspace interface to kernel DRM services -- runtime ii xorg 1:7.7+19 amd64 X.Org X Window System ii xorgxrdp 0.9.1-9+deb9u3 amd64 Remote Desktop Protocol (RDP) modules for X.org ii xserver-xorg 1:7.7+19 amd64 X.Org X server ii xserver-xorg-core 2
Bug#878170: Problem elsewhere, you can close it
On 2019-04-03 2:26 p.m., Anton Ivanov wrote: > I found the underlying root cause and the fix by chance when trawling > the web for something else. > > The issue is compositing in the window manager. > > If compositing is enabled the video WILL tear. If compositing is > disabled the videos display correctly. > > Definitely the case for xfce4. It's an xfwm4 (configuration) issue then. -- Earthling Michel Dänzer | https://www.amd.com Libre software enthusiast | Mesa and X developer
Bug#878170: Problem elsewhere, you can close it
I found the underlying root cause and the fix by chance when trawling the web for something else. The issue is compositing in the window manager. If compositing is enabled the video WILL tear. If compositing is disabled the videos display correctly. Definitely the case for xfce4. -- Anton R. Ivanov https://www.kot-begemot.co.uk/
Bug#923334: I suspect it's not an xorg problem
I went into IceWm after reporting this this morning and xorg is acting normally under that windown manager. I now suspect it's a Mate problem. Sorry for the noise.
Bug#873290: Similar problem on Mint Mate 18.2 with Freeciv
I'm having a similar problem with Mint 18.2. It's triggered by launching freeciv-client-gtk. When I boot it's fine. Open a terminal window, fine. Open Chrome, fine. Open Freeciv, the initial screens are OK, but once the full screen game starts, XORG pegs to 100% of a single core, even when nothing is happening. Closing Freeciv returns XORG to normal. Screen shots of atop output during all of these test cases are here: https://drive.google.com/open?id=1e15ZaYrxgWcFNRaquUHcTMxZ99_pZDf0 apt-cache policy freeciv-client-gtk freeciv-client-gtk: Installed: 2.5.10-1 Candidate: 2.5.10-1 Version table: *** 2.5.10-1 500 500 http://mirror.genesisadaptive.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/statusapt-cache policy xorg apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://mirror.genesisadaptive.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://mirror.genesisadaptive.com/ubuntu bionic/main amd64 Packages Please let me know if you need more info. Thanks - Pete
Re: problem with radeon since mesa > 18.0.5-1
2018-07-17 11:21 GMT+02:00 Michel Dänzer : > On 2018-07-16 08:31 PM, Jérémy Lal wrote: > > After login on a x11 gnome gdm3 sesssion, > > display hangs, crash, becomes black, and occasionally freeze the > computer. > > Which is an imac 27" 2011. > > But > > - i'm not sure it's a mesa bug, maybe a linux kernel bug triggered by the > > mesa update > > - i think it's appearing only on large displays like 2560x1440. > > - i don't know how to get logs from previous boots with journalctl > > > > I remember something about "cs ring radeon", etc.. > > Sounds like https://bugs.freedesktop.org/105381 , fixed in > xf86-video-ati upstream Git master. > right ! Using master@499d2f9d (july 17th) and it works again. Thanks.
Re: problem with radeon since mesa > 18.0.5-1
On 2018-07-16 08:31 PM, Jérémy Lal wrote: > After login on a x11 gnome gdm3 sesssion, > display hangs, crash, becomes black, and occasionally freeze the computer. > Which is an imac 27" 2011. > But > - i'm not sure it's a mesa bug, maybe a linux kernel bug triggered by the > mesa update > - i think it's appearing only on large displays like 2560x1440. > - i don't know how to get logs from previous boots with journalctl > > I remember something about "cs ring radeon", etc.. Sounds like https://bugs.freedesktop.org/105381 , fixed in xf86-video-ati upstream Git master. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer
problem with radeon since mesa > 18.0.5-1
After login on a x11 gnome gdm3 sesssion, display hangs, crash, becomes black, and occasionally freeze the computer. Which is an imac 27" 2011. But - i'm not sure it's a mesa bug, maybe a linux kernel bug triggered by the mesa update - i think it's appearing only on large displays like 2560x1440. - i don't know how to get logs from previous boots with journalctl I remember something about "cs ring radeon", etc.. Please help because it's a real bug ! Jérémy
Bug#891915: Patch for Debian 10 (buster), it fixes the problem
Tags: patch I attached patch from ArchLinux AUR ( https://aur.archlinux.org/packages/xorg-server-bug865/, https://aur.archlinux.org/cgit/aur.git/tree/freedesktop-bug-865.patch?h=xorg-server-bug865 ). This patch is stable and reliable. ArchLinux users are happy with it. It fixes current bug on Debian 10 (buster). I have tested it withon MATE desktop. Please kindly review it and consider applying it before official final release of Debian 10. As the result Debian and Ubuntu users will be as happy as ArchLinux's users. --- xorg-server-1.19.1/xkb/xkbActions.c.orig 2017-01-12 18:34:23.435568903 +0300 +++ xorg-server-1.19.1/xkb/xkbActions.c 2017-02-23 12:58:00.719948700 +0300 @@ -351,26 +351,83 @@ return 1; } +static int xkbSwitchGroupOnRelease(void) +{ +/* TODO: user configuring */ +return TRUE; +} + +static void xkbUpdateLockedGroup(XkbSrvInfoPtr xkbi, XkbAction* pAction) +{ +XkbGroupAction ga = pAction->group; +if (ga.flags_GroupAbsolute) + xkbi->state.locked_group= XkbSAGroup(); +else + xkbi->state.locked_group+= XkbSAGroup(); +} + +static XkbFilterPtr _XkbNextFreeFilter(XkbSrvInfoPtr xkbi); + static int -_XkbFilterLockState(XkbSrvInfoPtr xkbi, +_XkbFilterLockGroup(XkbSrvInfoPtr xkbi, XkbFilterPtr filter, unsigned keycode, XkbAction *pAction) { +int sendEvent = 1; + if (filter->keycode == 0) /* initial press */ AccessXCancelRepeatKey(xkbi, keycode); - -if (pAction && (pAction->type == XkbSA_LockGroup)) { -if (pAction->group.flags & XkbSA_GroupAbsolute) -xkbi->state.locked_group = XkbSAGroup(>group); -else -xkbi->state.locked_group += XkbSAGroup(>group); -return 1; +if (!xkbSwitchGroupOnRelease()) { + xkbUpdateLockedGroup(xkbi, pAction); + return sendEvent; +} + +/* Delay switch till button release */ +if (filter->keycode==0) { /* initial press */ + filter->keycode = keycode; + filter->active = 1; + filter->filterOthers = 0; /* for what? */ + filter->filter = _XkbFilterLockGroup; + + /* filter->priv = 0; */ + filter->upAction = *pAction; + + /* Ok, now we need to simulate the action which would go if this action didn't block it. + XkbSA_SetMods is the one: it is to set modifier' flag up. */ + { + XkbStateRec fake_state = xkbi->state; + XkbAction act; + + fake_state.mods = 0; + act = XkbGetKeyAction(xkbi, _state, keycode); + + /* KLUDGE: XkbSA_SetMods only? */ + if (act.type == XkbSA_SetMods) { + XkbFilterPtr filter = _XkbNextFreeFilter(xkbi); + sendEvent = _XkbFilterSetState(xkbi,filter,keycode,); + } + } +} +else { + /* do nothing if some button else is pressed */ + if (!pAction) + xkbUpdateLockedGroup(xkbi, >upAction); + filter->active = 0; } +return sendEvent; +} + +static int +_XkbFilterLockMods(XkbSrvInfoPtr xkbi, + XkbFilterPtrfilter, + unsignedkeycode, + XkbAction * pAction) +{ if (filter->keycode == 0) { /* initial press */ filter->keycode = keycode; filter->active = 1; filter->filterOthers = 0; filter->priv = xkbi->state.locked_mods & pAction->mods.mask; -filter->filter = _XkbFilterLockState; +filter->filter = _XkbFilterLockMods; filter->upAction = *pAction; if (!(filter->upAction.mods.flags & XkbSA_LockNoLock)) xkbi->state.locked_mods |= pAction->mods.mask; @@ -1244,9 +1301,12 @@ *sendEvent = _XkbFilterLatchState(xkbi, filter, key, act); break; case XkbSA_LockMods: +filter = _XkbNextFreeFilter(xkbi); +*sendEvent = _XkbFilterLockMods(xkbi, filter, key, act); +break; case XkbSA_LockGroup: filter = _XkbNextFreeFilter(xkbi); -*sendEvent = _XkbFilterLockState(xkbi, filter, key, act); +*sendEvent = _XkbFilterLockGroup(xkbi, filter, key, act); break; case XkbSA_ISOLock: filter = _XkbNextFreeFilter(xkbi);
Bug#891674: Patch to fix the problem
> "Michel" == Michel Dänzerwrites: Michel> On 2018-02-28 02:41 AM, peter.ch...@data61.csiro.au wrote: Michel> Doing it like this breaks ABI. This is fixed in libpciaccess Michel> 0.14 by Michel> https://cgit.freedesktop.org/xorg/lib/libpciaccess/commit/?id=a167bd6474522a709ff3cbb00476c0e4309cb66f Michel> , though Xorg needs to be rebuilt against that for it to take Michel> effect. Any idea when this'll hit Debian's archives? Because this bug will prevent X11 working on any machine that has VMD storage. Peter C -- Dr Peter Chubb Tel: +61 2 9490 5852 http://ts.data61.csiro.au/ Trustworthy Systems Group Data61 (formerly NICTA)
Bug#891674: Patch to fix the problem
On 2018-02-28 02:41 AM, peter.ch...@data61.csiro.au wrote: > The linux kernel treats PCI domains as 32 bit ints. > > diff -ru libpciaccess-0.13.4/include/pciaccess.h > libpciaccess-0.13.4-fixed/include/pciaccess.h > --- libpciaccess-0.13.4/include/pciaccess.h 2015-05-01 14:44:47.0 > +1000 > +++ libpciaccess-0.13.4-fixed/include/pciaccess.h 2018-02-28 > 12:21:12.280963252 +1100 > @@ -321,7 +321,7 @@ > * the domain will always be zero. > */ > /*@{*/ > -uint16_tdomain; > +uint32_tdomain; > uint8_t bus; > uint8_t dev; > uint8_t func; > diff -ru libpciaccess-0.13.4/src/linux_sysfs.c > libpciaccess-0.13.4-fixed/src/linux_sysfs.c > --- libpciaccess-0.13.4/src/linux_sysfs.c 2015-05-01 14:44:47.0 > +1000 > +++ libpciaccess-0.13.4-fixed/src/linux_sysfs.c 2018-02-28 > 12:21:32.676941130 +1100 > @@ -157,7 +157,7 @@ > (struct pci_device_private *) >devices[i]; > > > - sscanf(devices[i]->d_name, "%04x:%02x:%02x.%1u", > + sscanf(devices[i]->d_name, "%x:%02x:%02x.%1u", > & dom, & bus, & dev, & func); > > device->base.domain = dom; > Doing it like this breaks ABI. This is fixed in libpciaccess 0.14 by https://cgit.freedesktop.org/xorg/lib/libpciaccess/commit/?id=a167bd6474522a709ff3cbb00476c0e4309cb66f , though Xorg needs to be rebuilt against that for it to take effect. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer
Bug#891674: Patch to fix the problem
The linux kernel treats PCI domains as 32 bit ints. diff -ru libpciaccess-0.13.4/include/pciaccess.h libpciaccess-0.13.4-fixed/include/pciaccess.h --- libpciaccess-0.13.4/include/pciaccess.h 2015-05-01 14:44:47.0 +1000 +++ libpciaccess-0.13.4-fixed/include/pciaccess.h 2018-02-28 12:21:12.280963252 +1100 @@ -321,7 +321,7 @@ * the domain will always be zero. */ /*@{*/ -uint16_tdomain; +uint32_tdomain; uint8_t bus; uint8_t dev; uint8_t func; diff -ru libpciaccess-0.13.4/src/linux_sysfs.c libpciaccess-0.13.4-fixed/src/linux_sysfs.c --- libpciaccess-0.13.4/src/linux_sysfs.c 2015-05-01 14:44:47.0 +1000 +++ libpciaccess-0.13.4-fixed/src/linux_sysfs.c 2018-02-28 12:21:32.676941130 +1100 @@ -157,7 +157,7 @@ (struct pci_device_private *) >devices[i]; - sscanf(devices[i]->d_name, "%04x:%02x:%02x.%1u", + sscanf(devices[i]->d_name, "%x:%02x:%02x.%1u", & dom, & bus, & dev, & func); device->base.domain = dom; -- Dr Peter Chubb Tel: +61 2 9490 5852 http://ts.data61.csiro.au/ Trustworthy Systems Group Data61 (formerly NICTA)
Bug#888633: libgl1-mesa-dri: Problem with Firefox and other XWayland applications on AMD GPU
Package: libgl1-mesa-dri Version: 17.3.3-1.1 Severity: important Tags: patch Hi, it's seems that last version of Mesa 17.3 (17.3.3-1) present in unstable cause problem with firefox and other XWayland applications when computer run on AMD GPU, there is a bug report upstream at https://bugs.freedesktop.org/show_bug.cgi?id=104306 and a patch available here https://patchwork.freedesktop.org/patch/200999/. I managed to apply the patch on my system and that solved the problem. -- Package-specific info: glxinfo: name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_video_sync Extended renderer info (GLX_MESA_query_renderer): Vendor: X.Org (0x1002) Device: AMD CAPE VERDE (DRM 2.50.0 / 4.14.15-towo.1-siduction-amd64, LLVM 5.0.1) (0x6820) Version: 17.3.3 Accelerated: yes Video memory: 2048MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 4.5 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.1 OpenGL vendor string: X.Org OpenGL renderer string: AMD CAPE VERDE (DRM 2.50.0 / 4.14.15-towo.1-siduction-amd64, LLVM 5.0.1) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: GL_AMD_conservative_depth, GL_AMD_draw_buffers_blend, GL_AMD_performance_monitor, GL_AMD_pinned_memory, GL_AMD_seamless_cubemap_per_texture, GL_AMD_shader_stencil_export, GL_AMD_shader_trinary_minmax, GL_AMD_vertex_shader_layer, GL_AMD_vertex_shader_viewport_index, GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, GL_ARB_ES2_compatibility, GL_ARB_ES3_1_compatibility, GL_ARB_ES3_2_compatibility, GL_ARB_ES3_compatibility, GL_ARB_arrays_of_arrays, GL_ARB_base_instance, GL_ARB_bindless_texture, GL_ARB_blend_func_extended, GL_ARB_buffer_storage, GL_ARB_clear_buffer_object, GL_ARB_clear_texture, GL_ARB_clip_control, GL_ARB_color_buffer_float, GL_ARB_compressed_texture_pixel_storage, GL_ARB_compute_shader, GL_ARB_compute_variable_group_size, GL_ARB_conditional_render_inverted, GL_ARB_conservative_depth, GL_ARB_copy_buffer, GL_ARB_copy_image, GL_ARB_cull_distance, GL_ARB_debug_output, GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_derivative_control, GL_ARB_direct_state_access, GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, GL_ARB_draw_elements_base_vertex, GL_ARB_draw_indirect, GL_ARB_draw_instanced
Processed: Not a problem in stretch
Processing commands for cont...@bugs.debian.org: > tags 887076 buster sid Bug #887076 [src:xserver-xorg-video-ast] xserver-xorg-video-ast: unused build-dependency on libxatracker-dev Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 887076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887076 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#851416: Similar (identical ?) problem avter upgrading from stretch to buster
I am in the process to rework an old machine, used as a (slow) server. To make things simple, I installed Debian from an USB key of Debian Live (Stretch), which worked okay, including Gnome. Then I upgraded this system to buster (s/stretch/buster in /etc/apt/source.list.d/*, then apt-get update ; apt-get dist-updrade), which went smoothly. The problem started at the next reboot : GDM comes up fine, but any attempt to start a gnome session locked the screen ; no action on any key (including F6/alt-F6) ; an open ssh session from another machine displayed messages similar to : -- Aug 15 19:42:08 alpha kernel: [ 1008.200709] NMI watchdog: BUG: soft lockup - C\ PU#0 stuck for 22s! [Xwayland:3204] -- This was reproductible. I created a (gzipped) extract of /var/log/syslog covering (what I believe to be) an entire such session, which is enclosed. HTH, SampleLog.txt.gz Description: application/gzip
Bug#860539: marked as done (xserver-xorg-video-nouveau: Nouveau GPU lockup problem (GeForce GT 240))
Your message dated Mon, 10 Jul 2017 17:42:18 +0200 with message-id <CA+7wUsz-E00M=31wvwdue+cohcupsn6odhnavg1vk6ktmsq...@mail.gmail.com> and subject line xserver-xorg-video-nouveau: Nouveau GPU lockup problem (GeForce GT 240) has caused the Debian Bug report #860539, regarding xserver-xorg-video-nouveau: Nouveau GPU lockup problem (GeForce GT 240) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 860539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xserver-xorg-video-nouveau Version: 1:1.0.11-1 Severity: normal Looks like my GeForce GT 240 is not well supported by nouveau. Here is what I can see before pulling the plug: Apr 18 12:16:06 vostrodell kernel: [15473.519712] nouveau E[ PGRAPH][:01:00.0] vm flush timeout Apr 18 12:16:08 vostrodell kernel: [15475.519540] nouveau E[ PGRAPH][:01:00.0] vm flush timeout Apr 18 12:16:10 vostrodell kernel: [15477.519169] nouveau E[ VM][:01:00.0] vm flush timeout: engine 13 Apr 18 12:16:12 vostrodell kernel: [15479.518772] nouveau E[ PGRAPH][:01:00.0] vm flush timeout Apr 18 12:16:14 vostrodell kernel: [15481.518476] nouveau E[ PGRAPH][:01:00.0] vm flush timeout Apr 18 12:16:23 vostrodell kernel: [15490.810128] nouveau W[ BARCTL][:01:00.0] flush timeout Apr 18 12:16:23 vostrodell kernel: [15490.810161] nouveau W[ PFIFO][:01:00.0] unknown intr 0x0080, ch 3 Apr 18 12:16:23 vostrodell kernel: [15490.810389] [sched_delayed] sched: RT throttling activated Apr 18 12:16:23 vostrodell rtkit-daemon[1233]: The canary thread is apparently starving. Taking action. Apr 18 12:16:23 vostrodell rtkit-daemon[1233]: Demoting known real-time threads. Apr 18 12:16:23 vostrodell rtkit-daemon[1233]: Successfully demoted thread 1297 of process 1212 (/usr/bin/pulseaudio). Apr 18 12:16:23 vostrodell rtkit-daemon[1233]: Successfully demoted thread 1296 of process 1212 (/usr/bin/pulseaudio). Apr 18 12:16:23 vostrodell rtkit-daemon[1233]: Successfully demoted thread 1295 of process 1212 (/usr/bin/pulseaudio). Apr 18 12:16:23 vostrodell rtkit-daemon[1233]: Successfully demoted thread 1212 of process 1212 (/usr/bin/pulseaudio). Apr 18 12:16:23 vostrodell rtkit-daemon[1233]: Demoted 4 threads. Apr 18 12:16:24 vostrodell kernel: [15492.137476] nouveau W[ PFIFO][:01:00.0] unknown intr 0x0400, ch 3 Apr 18 12:16:25 vostrodell kernel: [15492.81] nouveau E[ PGRAPH][:01:00.0] vm flush timeout Apr 18 12:16:44 vostrodell kernel: [15494.809641] nouveau E[ VM][:01:00.0] vm flush timeout: engine 13 Apr 18 12:16:44 vostrodell kernel: [15512.402357] nouveau W[ BARCTL][:01:00.0] flush timeout Apr 18 12:16:44 vostrodell kernel: [15512.402364] nouveau W[ PFIFO][:01:00.0] unknown intr 0x04c0, ch 3 Would be nice to at least be able to switch to virtual term instead of hard reboot. Thanks for packaging nouveau -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Sep 5 2015 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 2401376 Feb 11 2015 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT215 [GeForce GT 240] [10de:0ca3] (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.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) Xorg X server log files on system: -- -rw-r--r-- 1 root root 12312 Nov 14 13:24 /var/log/Xorg.2.log -rw-r--r-- 1 root root 35304 Apr 18 12:22 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [53.385] X.Org X Server 1.16.4 Release Date: 2014-12-20 [53.385] X Protocol Version 11, Revision 0 [53.385] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [53.385] Current Operating System: Linux vostrodell 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 [53.385] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=dc3d1d5a-c1bf-4867-b16a-5c0542b5b258 ro drm_kms_helper.edid_firmware=edid/HPv220.edid.bin quiet [53.385] Build Date: 11 February 2015 12:32:02AM [53.385] xorg-server 2:1.16.
Processed: xserver-xorg-video-nouveau: Nouveau GPU lockup problem (GeForce GT 240)
Processing control commands: > fixed -1 1:1.0.13-3 Bug #860539 [xserver-xorg-video-nouveau] xserver-xorg-video-nouveau: Nouveau GPU lockup problem (GeForce GT 240) Marked as fixed in versions xserver-xorg-video-nouveau/1:1.0.13-3. -- 860539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#860539: xserver-xorg-video-nouveau: Nouveau GPU lockup problem (GeForce GT 240)
Control: fixed -1 1:1.0.13-3 I have been using stretch for a couple of weeks and nothing bad appears. So I am now an happy nouveau user. cheers
Bug#860539: xserver-xorg-video-nouveau: Nouveau GPU lockup problem (GeForce GT 240)
On 2017-04-18 12:40 +0200, Mathieu Malaterre wrote: > Package: xserver-xorg-video-nouveau > Version: 1:1.0.11-1 > Severity: normal > > Looks like my GeForce GT 240 is not well supported by nouveau. Try a kernel and libgl1-mesa-dri from jessie-backports. If that does not help, use the NVidia blob or buy a Radeon card. > Here is what I can see before pulling the plug: > > Apr 18 12:16:06 vostrodell kernel: [15473.519712] nouveau E[ > PGRAPH][:01:00.0] vm flush timeout > Apr 18 12:16:08 vostrodell kernel: [15475.519540] nouveau E[ > PGRAPH][:01:00.0] vm flush timeout > Apr 18 12:16:10 vostrodell kernel: [15477.519169] nouveau E[ > VM][:01:00.0] vm flush timeout: engine 13 > Apr 18 12:16:12 vostrodell kernel: [15479.518772] nouveau E[ > PGRAPH][:01:00.0] vm flush timeout > Apr 18 12:16:14 vostrodell kernel: [15481.518476] nouveau E[ > PGRAPH][:01:00.0] vm flush timeout > Apr 18 12:16:23 vostrodell kernel: [15490.810128] nouveau W[ > BARCTL][:01:00.0] flush timeout > Apr 18 12:16:23 vostrodell kernel: [15490.810161] nouveau W[ > PFIFO][:01:00.0] unknown intr 0x0080, ch 3 > Apr 18 12:16:23 vostrodell kernel: [15490.810389] [sched_delayed] sched: RT > throttling activated > Apr 18 12:16:23 vostrodell rtkit-daemon[1233]: The canary thread is > apparently starving. Taking action. > Apr 18 12:16:23 vostrodell rtkit-daemon[1233]: Demoting known real-time > threads. > Apr 18 12:16:23 vostrodell rtkit-daemon[1233]: Successfully demoted thread > 1297 of process 1212 (/usr/bin/pulseaudio). > Apr 18 12:16:23 vostrodell rtkit-daemon[1233]: Successfully demoted thread > 1296 of process 1212 (/usr/bin/pulseaudio). > Apr 18 12:16:23 vostrodell rtkit-daemon[1233]: Successfully demoted thread > 1295 of process 1212 (/usr/bin/pulseaudio). > Apr 18 12:16:23 vostrodell rtkit-daemon[1233]: Successfully demoted thread > 1212 of process 1212 (/usr/bin/pulseaudio). > Apr 18 12:16:23 vostrodell rtkit-daemon[1233]: Demoted 4 threads. > Apr 18 12:16:24 vostrodell kernel: [15492.137476] nouveau W[ > PFIFO][:01:00.0] unknown intr 0x0400, ch 3 > Apr 18 12:16:25 vostrodell kernel: [15492.81] nouveau E[ > PGRAPH][:01:00.0] vm flush timeout > Apr 18 12:16:44 vostrodell kernel: [15494.809641] nouveau E[ > VM][:01:00.0] vm flush timeout: engine 13 > Apr 18 12:16:44 vostrodell kernel: [15512.402357] nouveau W[ > BARCTL][:01:00.0] flush timeout > Apr 18 12:16:44 vostrodell kernel: [15512.402364] nouveau W[ > PFIFO][:01:00.0] unknown intr 0x04c0, ch 3 > > > Would be nice to at least be able to switch to virtual term instead of hard > reboot. I guess you'll have to use ssh or even netconsole to capture more kernel messages. Possibly related upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=69465. Cheers, Sven
Bug#860539: xserver-xorg-video-nouveau: Nouveau GPU lockup problem (GeForce GT 240)
Package: xserver-xorg-video-nouveau Version: 1:1.0.11-1 Severity: normal Looks like my GeForce GT 240 is not well supported by nouveau. Here is what I can see before pulling the plug: Apr 18 12:16:06 vostrodell kernel: [15473.519712] nouveau E[ PGRAPH][:01:00.0] vm flush timeout Apr 18 12:16:08 vostrodell kernel: [15475.519540] nouveau E[ PGRAPH][:01:00.0] vm flush timeout Apr 18 12:16:10 vostrodell kernel: [15477.519169] nouveau E[ VM][:01:00.0] vm flush timeout: engine 13 Apr 18 12:16:12 vostrodell kernel: [15479.518772] nouveau E[ PGRAPH][:01:00.0] vm flush timeout Apr 18 12:16:14 vostrodell kernel: [15481.518476] nouveau E[ PGRAPH][:01:00.0] vm flush timeout Apr 18 12:16:23 vostrodell kernel: [15490.810128] nouveau W[ BARCTL][:01:00.0] flush timeout Apr 18 12:16:23 vostrodell kernel: [15490.810161] nouveau W[ PFIFO][:01:00.0] unknown intr 0x0080, ch 3 Apr 18 12:16:23 vostrodell kernel: [15490.810389] [sched_delayed] sched: RT throttling activated Apr 18 12:16:23 vostrodell rtkit-daemon[1233]: The canary thread is apparently starving. Taking action. Apr 18 12:16:23 vostrodell rtkit-daemon[1233]: Demoting known real-time threads. Apr 18 12:16:23 vostrodell rtkit-daemon[1233]: Successfully demoted thread 1297 of process 1212 (/usr/bin/pulseaudio). Apr 18 12:16:23 vostrodell rtkit-daemon[1233]: Successfully demoted thread 1296 of process 1212 (/usr/bin/pulseaudio). Apr 18 12:16:23 vostrodell rtkit-daemon[1233]: Successfully demoted thread 1295 of process 1212 (/usr/bin/pulseaudio). Apr 18 12:16:23 vostrodell rtkit-daemon[1233]: Successfully demoted thread 1212 of process 1212 (/usr/bin/pulseaudio). Apr 18 12:16:23 vostrodell rtkit-daemon[1233]: Demoted 4 threads. Apr 18 12:16:24 vostrodell kernel: [15492.137476] nouveau W[ PFIFO][:01:00.0] unknown intr 0x0400, ch 3 Apr 18 12:16:25 vostrodell kernel: [15492.81] nouveau E[ PGRAPH][:01:00.0] vm flush timeout Apr 18 12:16:44 vostrodell kernel: [15494.809641] nouveau E[ VM][:01:00.0] vm flush timeout: engine 13 Apr 18 12:16:44 vostrodell kernel: [15512.402357] nouveau W[ BARCTL][:01:00.0] flush timeout Apr 18 12:16:44 vostrodell kernel: [15512.402364] nouveau W[ PFIFO][:01:00.0] unknown intr 0x04c0, ch 3 Would be nice to at least be able to switch to virtual term instead of hard reboot. Thanks for packaging nouveau -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Sep 5 2015 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 2401376 Feb 11 2015 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT215 [GeForce GT 240] [10de:0ca3] (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.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) Xorg X server log files on system: -- -rw-r--r-- 1 root root 12312 Nov 14 13:24 /var/log/Xorg.2.log -rw-r--r-- 1 root root 35304 Apr 18 12:22 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [53.385] X.Org X Server 1.16.4 Release Date: 2014-12-20 [53.385] X Protocol Version 11, Revision 0 [53.385] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [53.385] Current Operating System: Linux vostrodell 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 [53.385] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=dc3d1d5a-c1bf-4867-b16a-5c0542b5b258 ro drm_kms_helper.edid_firmware=edid/HPv220.edid.bin quiet [53.385] Build Date: 11 February 2015 12:32:02AM [53.385] xorg-server 2:1.16.4-1 (http://www.debian.org/support) [53.385] Current version of pixman: 0.32.6 [53.385]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [53.385] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [53.385] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Apr 18 12:21:53 2017 [53.457] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [53.919] (==) No Layout section. Using the first Screen section. [53.919] (==) No screen section available. Using defaults. [53.919] (**) |-->Screen "Default Screen Section" (0) [53.919] (**) | |-->Monitor "" [53.946] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [53.946] (==)
Bug#714531: marked as done (xserver-xorg-core: Xorg freezes with i915 intel_crtc_wait_for_pending_flips problem)
Your message dated Sat, 23 Jul 2016 00:01:57 +0200 with message-id <20160723000157.2efc4869f7617fd16247d...@paranoici.org> and subject line Re: xserver-xorg-core: Xorg freezes with i915 intel_crtc_wait_for_pending_flips problem has caused the Debian Bug report #714531, regarding xserver-xorg-core: Xorg freezes with i915 intel_crtc_wait_for_pending_flips problem to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 714531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714531 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xserver-xorg-core Version: 2:1.12.4-6 Severity: normal Hi. I just encountered a freeze on a Dell latitude E5400, where X is frozen, but the machine is accessible through SSH. Here's the message I found in the syslog : Jun 29 15:19:28 jonsnow kernel: [ 1320.668051] INFO: task kworker/0:2:224 blocked for more than 120 seconds. Jun 29 15:19:28 jonsnow kernel: [ 1320.668057] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 29 15:19:28 jonsnow kernel: [ 1320.668060] kworker/0:2 D 88007d013ec0 0 224 2 0x Jun 29 15:19:28 jonsnow kernel: [ 1320.668066] 880077620830 0046 81613400 00013ec0 Jun 29 15:19:28 jonsnow kernel: [ 1320.668071] 880036a2bfd8 880036a2bfd8 880077620830 880036bcd390 Jun 29 15:19:28 jonsnow kernel: [ 1320.668076] 880077620830 880036bcd394 0002 Jun 29 15:19:28 jonsnow kernel: [ 1320.668080] Call Trace: Jun 29 15:19:28 jonsnow kernel: [ 1320.668096] [] ? schedule_preempt_disabled+0x5/0x6 Jun 29 15:19:28 jonsnow kernel: [ 1320.668099] [] ? __mutex_lock_common.isra.6+0x145/0x161 Jun 29 15:19:28 jonsnow kernel: [ 1320.668102] [] ? mutex_lock+0x17/0x27 Jun 29 15:19:28 jonsnow kernel: [ 1320.668114] [] ? output_poll_execute+0x3f/0x153 [drm_kms_helper] Jun 29 15:19:28 jonsnow kernel: [ 1320.668118] [] ? finish_task_switch+0x81/0xae Jun 29 15:19:28 jonsnow kernel: [ 1320.668121] [] ? process_one_work+0x19b/0x2b1 Jun 29 15:19:28 jonsnow kernel: [ 1320.668124] [] ? worker_thread+0x123/0x1ca Jun 29 15:19:28 jonsnow kernel: [ 1320.668126] [] ? manage_workers+0x217/0x217 Jun 29 15:19:28 jonsnow kernel: [ 1320.668130] [] ? kthread+0x7d/0x85 Jun 29 15:19:28 jonsnow kernel: [ 1320.668133] [] ? __kthread_parkme+0x59/0x59 Jun 29 15:19:28 jonsnow kernel: [ 1320.668136] [] ? ret_from_fork+0x7c/0xb0 Jun 29 15:19:28 jonsnow kernel: [ 1320.668139] [] ? __kthread_parkme+0x59/0x59 Jun 29 15:19:28 jonsnow kernel: [ 1320.668156] INFO: task Xorg:3125 blocked for more than 120 seconds. Jun 29 15:19:28 jonsnow kernel: [ 1320.668158] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 29 15:19:28 jonsnow kernel: [ 1320.668159] XorgD 88007d013ec0 0 3125 2920 0x0044 Jun 29 15:19:28 jonsnow kernel: [ 1320.668162] 880036c95870 0082 81613400 00013ec0 Jun 29 15:19:28 jonsnow kernel: [ 1320.668166] 8800778ddfd8 8800778ddfd8 880036c95870 88007878c000 Jun 29 15:19:28 jonsnow kernel: [ 1320.668169] 880079a62308 880036bcd000 Jun 29 15:19:28 jonsnow kernel: [ 1320.668171] Call Trace: Jun 29 15:19:28 jonsnow kernel: [ 1320.668186] [] ? intel_crtc_wait_for_pending_flips+0xaa/0xe0 [i915] Jun 29 15:19:28 jonsnow kernel: [ 1320.668190] [] ? abort_exclusive_wait+0x79/0x79 Jun 29 15:19:28 jonsnow kernel: [ 1320.668201] [] ? i9xx_crtc_disable+0x79/0x185 [i915] Jun 29 15:19:28 jonsnow kernel: [ 1320.668213] [] ? intel_crtc_update_dpms+0x56/0x64 [i915] Jun 29 15:19:28 jonsnow kernel: [ 1320.668225] [] ? intel_connector_dpms+0x2f/0x53 [i915] Jun 29 15:19:28 jonsnow kernel: [ 1320.668235] [] ? drm_mode_obj_set_property_ioctl+0x162/0x1ec [drm] Jun 29 15:19:28 jonsnow kernel: [ 1320.668242] [] ? drm_mode_connector_property_set_ioctl+0x29/0x2e [drm] Jun 29 15:19:28 jonsnow kernel: [ 1320.668249] [] ? drm_ioctl+0x28f/0x36d [drm] Jun 29 15:19:28 jonsnow kernel: [ 1320.668257] [] ? drm_mode_obj_set_property_ioctl+0x1ec/0x1ec [drm] Jun 29 15:19:28 jonsnow kernel: [ 1320.668261] [] ? _raw_spin_unlock_irqrestore+0xc/0xd Jun 29 15:19:28 jonsnow kernel: [ 1320.668264] [] ? sysfs_notify+0x5d/0x6d Jun 29 15:19:28 jonsnow kernel: [ 1320.668268] [] ? __cache_free.isra.46+0x18c/0x19b Jun 29 15:19:28 jonsnow kernel: [ 1320.668273] [] ? get_pageblock_flags_group+0x3e/0x6f Jun 29 15:19:28 jonsnow kernel: [ 1320.668275] [] ? sysfs_release+0
Processed: Re: xserver-xorg-core: Xorg freezes with i915 intel_crtc_wait_for_pending_flips problem
Processing control commands: > reassign -1 xserver-xorg-video-intel 2:2.19.0-4 Bug #714531 [xserver-xorg-core] xserver-xorg-core: Xorg freezes with i915 intel_crtc_wait_for_pending_flips problem Bug reassigned from package 'xserver-xorg-core' to 'xserver-xorg-video-intel'. No longer marked as found in versions xorg-server/2:1.12.4-6. Ignoring request to alter fixed versions of bug #714531 to the same values previously set Bug #714531 [xserver-xorg-video-intel] xserver-xorg-core: Xorg freezes with i915 intel_crtc_wait_for_pending_flips problem Marked as found in versions xserver-xorg-video-intel/2:2.19.0-4. -- 714531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714531 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#714531: xserver-xorg-core: Xorg freezes with i915 intel_crtc_wait_for_pending_flips problem
Control: reassign -1 xserver-xorg-video-intel 2:2.19.0-4 On Wed, 22 Jun 2016 22:54:20 +0200 Francesco Poli wrote: [...] > If nobody objects in the next 30 days, I will reassign bug #714531 > to package xserver-xorg-video-intel and close both bug > reports (#714531 and #682816) as fixed in > xserver-xorg-video-intel/2:2.99.917+git20160325-1 I am reassigning bug #714531 ... -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgp23LkQS5ahQ.pgp Description: PGP signature
Bug#682816: xserver-xorg-core: Xorg freezes with i915 intel_crtc_wait_for_pending_flips problem
Sorry, I haven't been using debian for some time, so cannot comment anymore. Regards, Joseph On 22 June 2016 at 21:54, Francesco Poliwrote: > On Mon, 14 Jul 2014 22:28:05 +0200 Francesco Poli wrote: > > > I had found out that the issue vanishes when using SNA acceleration. > [...] > > and I am keeping DPMS disabled. > [...] > > Is there any progress on this issue? > > These two issues (#714531 [1] and #682816 [2]) seem to have disappeared > (at least) since > xserver-xorg-video-intel/2:2.99.917+git20160325-1 > linux-image-4.5.0-2-amd64/4.5.3-2 > > [1] https://bugs.debian.org/714531 > [2] https://bugs.debian.org/682816 > > I haven't experienced them for quite some time, after re-enabling DPMS > and while using the default acceleration (which is now SNA, as far as I > can tell). > > Olivier, Joseph, Wolodja, do you still experience any of the two bugs? > Please let me know, thanks for your time. > > If nobody objects in the next 30 days, I will reassign bug #714531 > to package xserver-xorg-video-intel and close both bug > reports (#714531 and #682816) as fixed in > xserver-xorg-video-intel/2:2.99.917+git20160325-1 > > Bye. > > -- > http://www.inventati.org/frx/ > There's not a second to spare! To the laboratory! > . Francesco Poli . > GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE >
Bug#828191: xserver-xorg-video-nouveau: attachment of script.log for shruken screen problem (nvidia 6800 Ultra)
Control: reassign -1 xserver-xorg-video-fbdev Control: merge 828183 -1 On 2016-06-25 15:49 -0700, macthetux wrote: > Package: xserver-xorg-video-nouveau > Version: 1:1.0.11-1 > Severity: normal > > Dear Maintainer, > > This is just the attachment on the system with GeForce 6800Ultra(powerpc G5 > mac tower, Dual 2.0 GHz. Please use "reportbug -N " for followups, this avoids useless duplicates. Thanks, Sven
Processed: Re: Bug#828191: xserver-xorg-video-nouveau: attachment of script.log for shruken screen problem (nvidia 6800 Ultra)
Processing control commands: > reassign -1 xserver-xorg-video-fbdev Bug #828191 [xserver-xorg-video-nouveau] xserver-xorg-video-nouveau: attachment of script.log for shruken screen problem (nvidia 6800 Ultra) Bug reassigned from package 'xserver-xorg-video-nouveau' to 'xserver-xorg-video-fbdev'. No longer marked as found in versions xserver-xorg-video-nouveau/1:1.0.11-1. Ignoring request to alter fixed versions of bug #828191 to the same values previously set > merge 828183 -1 Bug #828183 [xserver-xorg-video-fbdev] xserver-xorg-video-nouveau: 8bit colours with severly shrunken screen, no hw accel (GeForce 6800 Ultra on Jessie) Bug #828191 [xserver-xorg-video-fbdev] xserver-xorg-video-nouveau: attachment of script.log for shruken screen problem (nvidia 6800 Ultra) Merged 828183 828191 -- 828183: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828183 828191: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#828191: xserver-xorg-video-nouveau: attachment of script.log for shruken screen problem (nvidia 6800 Ultra)
Package: xserver-xorg-video-nouveau Version: 1:1.0.11-1 Severity: normal Dear Maintainer, This is just the attachment on the system with GeForce 6800Ultra(powerpc G5 mac tower, Dual 2.0 GHz. 8 bit shrunken screen. I switched graphics cards with my 5200 FX Ultra which was running my desktop with 16bit graphics but full screen real estate. When I switched to the 6800 Ultra the usable screen area became much smaller, and 8but.) -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Jun 25 04:57 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 2498728 Feb 10 2015 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- :f0:10.0 VGA compatible controller [0300]: NVIDIA Corporation NV40 [GeForce 6800 Ultra] [10de:0040] (rev a1) Xorg X server configuration file status: -rwxr-xr-x 1 root root 3174 Jun 25 05:42 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: --- Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 Screen 1 "Screen1" RightOf "Screen0" InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" EndSection Section "Files" ModulePath "/usr/lib/xorg/modules" FontPath "/usr/share/fonts/X11/misc" FontPath "/usr/share/fonts/X11/cyrillic" FontPath "/usr/share/fonts/X11/100dpi/:unscaled" FontPath "/usr/share/fonts/X11/75dpi/:unscaled" FontPath "/usr/share/fonts/X11/Type1" FontPath "/usr/share/fonts/X11/100dpi" FontPath "/usr/share/fonts/X11/75dpi" FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" FontPath "built-ins" EndSection Section "Module" Load "dbe" Load "record" Load "extmod" Load "dri" Load "glx" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5 6 7" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName"Monitor Model" EndSection Section "Monitor" Identifier "Monitor1" VendorName "Monitor Vendor" ModelName"Monitor Model" EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz", ### : "%" ### [arg]: arg optional #Option "SWcursor" # [] Option "HWcursor" "on" #Option "NoAccel" # [] #Option "ShadowFB" # [] #Option "VideoKey" # #Option "WrappedFB" # [] #Option "GLXVBlank" # [] #Option "ZaphodHeads" # #Option "PageFlip" # [] #Option "SwapLimit" # #Option "AsyncUTSDFS" # [] Option "Randr12" "on" Option "AccelMethod" "EXA" Option "RenderAccel" "on" Identifier "Card0" Driver "nouveaufb" BusID "PCI:240:16:0" EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz", ### : "%" ### [arg]: arg optional #Option "ShadowFB" # [] #Option "Rotate"# #Option "fbdev" # #Option "debug" # [] Identifier "Card1" Driver "fbdev" BusID "PCI:240:16:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor"Monitor0" DefaultDepth 16 SubSection "Display" Viewport 0 0 Depth 16 EndSubSection EndSection Section "Screen" Identifier "Screen1" Device "Card1" Monitor"Monitor1" DefaultDepth 16 SubSection "Display" Viewport 0 0 Depth 16 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-powerpc64 (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) Xorg X server log files on system: -- -rw-r--r-- 1 root root 18772 Jun 25 05:31
Bug#682816: xserver-xorg-core: Xorg freezes with i915 intel_crtc_wait_for_pending_flips problem
On Mon, 14 Jul 2014 22:28:05 +0200 Francesco Poli wrote: > I had found out that the issue vanishes when using SNA acceleration. [...] > and I am keeping DPMS disabled. [...] > Is there any progress on this issue? These two issues (#714531 [1] and #682816 [2]) seem to have disappeared (at least) since xserver-xorg-video-intel/2:2.99.917+git20160325-1 linux-image-4.5.0-2-amd64/4.5.3-2 [1] https://bugs.debian.org/714531 [2] https://bugs.debian.org/682816 I haven't experienced them for quite some time, after re-enabling DPMS and while using the default acceleration (which is now SNA, as far as I can tell). Olivier, Joseph, Wolodja, do you still experience any of the two bugs? Please let me know, thanks for your time. If nobody objects in the next 30 days, I will reassign bug #714531 to package xserver-xorg-video-intel and close both bug reports (#714531 and #682816) as fixed in xserver-xorg-video-intel/2:2.99.917+git20160325-1 Bye. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpYDzeM7r460.pgp Description: PGP signature
Bug#819461: found the problem
plese close the ticket
Bug#675363: I had the same problem but it went away
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I was having the same issues on my HD Graphics 5500, last seen on jessie with original kernel + backports xserver-xorg-video-intel. However since getting the backports kernel, too, this problem disapeared. It also did not reappear in stretch (testing at the time of writing) so far. Your report is quite old, can you verify it still exists? Best Regards Christian Hawkins -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJW784XAAoJEN3zqGdyMf8B9SAH/0r5H461SvsHTr8T1emANRUz 1/5TJP5zvRVvQw/ybPSI+Abhu2nRG96dW29p5ZiYu4RCI8jkGJvI+a9/KSVJZAUG EvjkoepkdDNfDROCmzDgG3b6/tReGMLgLnoANhT4XBkNLJmiG2IxsrXaVuEssgof audiD66E5+npbZnX+OX7IsskcCzCBZ3d88D8YsgGe8/dB/Qrot0G/6gDGOBqOAxG 4P94Z5CCxhztOiBPkIrtRxJebVDAVaySRZWmViXfrqNOQgArs/IlexrJ3pEtIp72 hlA2iCwGRFfnu18SpZCXC+PyL6THWfthhQ6HCcEYU2z02iz9NZx8Vmkl1yfUejw= =8YFN -END PGP SIGNATURE-
Bug#801605: Same problem, different error.
On Sat, 24 Oct 2015 08:06:56 -0700 VDR User <user@gmail.com> wrote: > I have the same problem here but my error is different. > > xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory) > > From what I've read it's caused by Debian not providing correct > systemd files and thus breaking Xorg's "unprivileged mode". > > Before "upgrading", I could startx/xinit as a user no problem. After > "upgrading", no. It only works when using sudo or as root. I have seen this error on two machines as well, and, as mentioned above, making /usr/lib/xorg/Xorg suid "resolves" it. In both cases the "radeon" kernel module was involved. I straced it and I saw that some system call got an access denied. On two other machines I had X but no mouse and no keyboard after this "upgrade". To resolve this I had to make the user member of the group "input". After that, the mouse and keyboard worked properly again. Normally X is started by gdm or whatever, so for most people X will work properly. But this issue is a problem for those who start X as a normal user, so there will be few people who encounter this rather annoying problem. BTW: systems mentioned above are systemd-free. R. -- Richard Lucassen <netwerkbeh...@opbouw.net>
Bug#801605: Same problem, different error.
I have the same problem here but my error is different. xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory) >From what I've read it's caused by Debian not providing correct systemd files and thus breaking Xorg's "unprivileged mode". Before "upgrading", I could startx/xinit as a user no problem. After "upgrading", no. It only works when using sudo or as root.
Bug#795651: same problem in sid
I upgrade my system to sid, and get the same problem.
Bug#783705: xserver-xorg-video-radeon: Weird X wakeup problem since Jessie upgrade
On Tue, May 05, 2015 at 09:06:40AM -0400, Alex Deucher wrote: On Wed, Apr 29, 2015 at 7:45 AM, Steve McIntyre st...@einval.com wrote: Package: xserver-xorg-video-radeon Version: 1:7.5.0-1 Severity: normal Hi folks, I upgrade my main office desktop to Jessie on Monday, and just about evrrything worked really well - just half a dozen oro so config files needed merging with new upstream etc. Painless! However, I'm now seeing a really odd problem with X on my machine. I've got an AMD graphics card, which Xorg.0.log tells me is a RADEON(0): Chipset: PITCAIRN (ChipID = 0x6810) and a DP+ connection to a lovely 27 NEC monitor. It works just fine when I'm using it, *but* when I leave it overnight and come in the next morning it doesn't want to wake up properly. I'm locking the screen with Xscreensaver and then turning off the monitor as I leave. In the morning, I turn on the screen and I don't get a display at all. I've wiggled the mouse, hit numlock on the keybard (the numlock led illuminates fine), etc., but no display. I've seen this kind of thing happen in the past on some machines, so I switch to VT1 and back to see if that helps. Still no display at all, either on console or under X. I log in remotely and I can see that the Xorg.0.log file has been updated with mode lines for the monitor, suggesting things have just woken up fine. But still no display. Here's the really weird thing: at this point, the monitor has basically locked up. It won't respond to the power/input/menu butttons at all, and is still showing the blue LED that says I have signal rather than switching to the amber no signal warning. Therefore, I can only assume there's a problem here with some weird invalid DP signal being produced. Yesterday, I gave up and rebooted after a few minutes - I had work to do. Today, I started searching for any other reports like this using my laptop. About ten minutes later while I was doing this (approximately, wasn't paying massive attention at this point), my desktop screen suddenly came to life and now it's working OK. I have no idea of where to even start debugging this. Help! If this is a regression, what previous version was working correctly? I was using an up-to-date wheezy installation previously, so that would be 1:6.14.4-8. Does the problem only happen when you physically power off the monitor? Ah, yes! In fact, it's the act of physically powering off the monitor that's the problem here. I can reproduce immediately by doing that. Last night, I locked the screen and left the monitor on and things were still working fine this morning when I came in. Does it come back ok when you let dpms kick in? Pass - I disabled dpms ages ago for unrelated reasons... How about when you physically disconnect the monitor from the computer? I tried that - if I unplugged the cable from the monitor, the monitor started responding to button presses ok but as soon as I reconnected it locked up again and still no display. Also, what screensavers are you using? There may be a problematic GL screensaver that's causing a GPU lockup. Can you try forcing a single known stable screensaver? I just use bumps under xscreensaver, and I've had that configured for years. -- Steve McIntyre, Cambridge, UK.st...@einval.com Can't keep my eyes from the circling sky, Tongue-tied twisted, Just an earth-bound misfit, I... -- 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/20150506131222.gd7...@einval.com
Bug#783705: xserver-xorg-video-radeon: Weird X wakeup problem since Jessie upgrade
On Tue, May 05, 2015 at 01:55:16PM +0200, Julien Cristau wrote: On Tue, May 5, 2015 at 12:40:54 +0100, Steve McIntyre wrote: On Wed, Apr 29, 2015 at 12:45:29PM +0100, Steve McIntyre wrote: In the morning, I turn on the screen and I don't get a display at all. I've wiggled the mouse, hit numlock on the keybard (the numlock led illuminates fine), etc., but no display. I've seen this kind of thing happen in the past on some machines, so I switch to VT1 and back to see if that helps. Still no display at all, either on console or under X. I log in remotely and I can see that the Xorg.0.log file has been updated with mode lines for the monitor, suggesting things have just woken up fine. But still no display. Similar problem this morning. I've found that using xrandr to disable and re-enable the DisplayPort output I'm using helps - the display comes back. Until xrandr segfaults, anyway - see separate bug. Something weird in the card state, I guess? Sounds likely. If this still happens with linux 4.0, can you report this upstream at https://bugs.freedesktop.org/enter_bug.cgi?product=DRIcomponent=DRM%2fRadeon and let us know the bug number? OK. New kernel didn't help at all. Bug filed: https://bugs.freedesktop.org/show_bug.cgi?id=90340 -- Steve McIntyre, Cambridge, UK.st...@einval.com Aardvark I dislike C++ to start with. C++11 just seems to be handing rope-creating factories for users to hang multiple instances of themselves. -- 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/20150506132640.ge7...@einval.com
Bug#783705: xserver-xorg-video-radeon: Weird X wakeup problem since Jessie upgrade
On Wed, Apr 29, 2015 at 12:45:29PM +0100, Steve McIntyre wrote: In the morning, I turn on the screen and I don't get a display at all. I've wiggled the mouse, hit numlock on the keybard (the numlock led illuminates fine), etc., but no display. I've seen this kind of thing happen in the past on some machines, so I switch to VT1 and back to see if that helps. Still no display at all, either on console or under X. I log in remotely and I can see that the Xorg.0.log file has been updated with mode lines for the monitor, suggesting things have just woken up fine. But still no display. Similar problem this morning. I've found that using xrandr to disable and re-enable the DisplayPort output I'm using helps - the display comes back. Until xrandr segfaults, anyway - see separate bug. Something weird in the card state, I guess? -- Steve McIntyre, Cambridge, UK.st...@einval.com This dress doesn't reverse. -- Alden Spiess -- 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/20150505114054.ga21...@einval.com
Bug#783705: xserver-xorg-video-radeon: Weird X wakeup problem since Jessie upgrade
On Tue, May 5, 2015 at 12:40:54 +0100, Steve McIntyre wrote: On Wed, Apr 29, 2015 at 12:45:29PM +0100, Steve McIntyre wrote: In the morning, I turn on the screen and I don't get a display at all. I've wiggled the mouse, hit numlock on the keybard (the numlock led illuminates fine), etc., but no display. I've seen this kind of thing happen in the past on some machines, so I switch to VT1 and back to see if that helps. Still no display at all, either on console or under X. I log in remotely and I can see that the Xorg.0.log file has been updated with mode lines for the monitor, suggesting things have just woken up fine. But still no display. Similar problem this morning. I've found that using xrandr to disable and re-enable the DisplayPort output I'm using helps - the display comes back. Until xrandr segfaults, anyway - see separate bug. Something weird in the card state, I guess? Sounds likely. If this still happens with linux 4.0, can you report this upstream at https://bugs.freedesktop.org/enter_bug.cgi?product=DRIcomponent=DRM%2fRadeon and let us know the bug number? Thanks, Julien signature.asc Description: Digital signature
Bug#783705: xserver-xorg-video-radeon: Weird X wakeup problem since Jessie upgrade
On Wed, Apr 29, 2015 at 7:45 AM, Steve McIntyre st...@einval.com wrote: Package: xserver-xorg-video-radeon Version: 1:7.5.0-1 Severity: normal Hi folks, I upgrade my main office desktop to Jessie on Monday, and just about evrrything worked really well - just half a dozen oro so config files needed merging with new upstream etc. Painless! However, I'm now seeing a really odd problem with X on my machine. I've got an AMD graphics card, which Xorg.0.log tells me is a RADEON(0): Chipset: PITCAIRN (ChipID = 0x6810) and a DP+ connection to a lovely 27 NEC monitor. It works just fine when I'm using it, *but* when I leave it overnight and come in the next morning it doesn't want to wake up properly. I'm locking the screen with Xscreensaver and then turning off the monitor as I leave. In the morning, I turn on the screen and I don't get a display at all. I've wiggled the mouse, hit numlock on the keybard (the numlock led illuminates fine), etc., but no display. I've seen this kind of thing happen in the past on some machines, so I switch to VT1 and back to see if that helps. Still no display at all, either on console or under X. I log in remotely and I can see that the Xorg.0.log file has been updated with mode lines for the monitor, suggesting things have just woken up fine. But still no display. Here's the really weird thing: at this point, the monitor has basically locked up. It won't respond to the power/input/menu butttons at all, and is still showing the blue LED that says I have signal rather than switching to the amber no signal warning. Therefore, I can only assume there's a problem here with some weird invalid DP signal being produced. Yesterday, I gave up and rebooted after a few minutes - I had work to do. Today, I started searching for any other reports like this using my laptop. About ten minutes later while I was doing this (approximately, wasn't paying massive attention at this point), my desktop screen suddenly came to life and now it's working OK. I have no idea of where to even start debugging this. Help! If this is a regression, what previous version was working correctly? Does the problem only happen when you physically power off the monitor? Does it come back ok when you let dpms kick in? How about when you physically disconnect the monitor from the computer? Also, what screensavers are you using? There may be a problematic GL screensaver that's causing a GPU lockup. Can you try forcing a single known stable screensaver? Alex -- 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/cadnq5_oqrha6u84gd8vcmelsunfupxc-1zsu8_fufcseegd...@mail.gmail.com
Bug#783705: xserver-xorg-video-radeon: Weird X wakeup problem since Jessie upgrade
Package: xserver-xorg-video-radeon Version: 1:7.5.0-1 Severity: normal Hi folks, I upgrade my main office desktop to Jessie on Monday, and just about evrrything worked really well - just half a dozen oro so config files needed merging with new upstream etc. Painless! However, I'm now seeing a really odd problem with X on my machine. I've got an AMD graphics card, which Xorg.0.log tells me is a RADEON(0): Chipset: PITCAIRN (ChipID = 0x6810) and a DP+ connection to a lovely 27 NEC monitor. It works just fine when I'm using it, *but* when I leave it overnight and come in the next morning it doesn't want to wake up properly. I'm locking the screen with Xscreensaver and then turning off the monitor as I leave. In the morning, I turn on the screen and I don't get a display at all. I've wiggled the mouse, hit numlock on the keybard (the numlock led illuminates fine), etc., but no display. I've seen this kind of thing happen in the past on some machines, so I switch to VT1 and back to see if that helps. Still no display at all, either on console or under X. I log in remotely and I can see that the Xorg.0.log file has been updated with mode lines for the monitor, suggesting things have just woken up fine. But still no display. Here's the really weird thing: at this point, the monitor has basically locked up. It won't respond to the power/input/menu butttons at all, and is still showing the blue LED that says I have signal rather than switching to the amber no signal warning. Therefore, I can only assume there's a problem here with some weird invalid DP signal being produced. Yesterday, I gave up and rebooted after a few minutes - I had work to do. Today, I started searching for any other reports like this using my laptop. About ten minutes later while I was doing this (approximately, wasn't paying massive attention at this point), my desktop screen suddenly came to life and now it's working OK. I have no idea of where to even start debugging this. Help! -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Jul 22 2014 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2401376 Feb 11 00:35 /usr/bin/Xorg Diversions concerning libGL are in place 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/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions diversion of /usr/lib/libGLESv2.so.2 to /usr/lib/mesa-diverted/libGLESv2.so.2 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/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGLESv2.so.2 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2 by glx-diversions 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/libGLESv1_CM.so.1.1.0 to /usr/lib/mesa-diverted/libGLESv1_CM.so.1.1.0 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 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/libGLESv2.so to /usr/lib/mesa-diverted/libGLESv2.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/i386-linux-gnu/libGLESv1_CM.so.1.1.0 to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1.1.0 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/libGLESv2.so to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so by glx-diversions diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2 by glx-diversions diversion of /usr
Bug#749006: marked as done (xkb-data: fujitsu_vndr layouts syntax problem in ckbcomp)
Your message dated Sun, 26 Apr 2015 17:00:01 + with message-id e1ymput-gx...@franck.debian.org and subject line Bug#749006: fixed in xkeyboard-config 2.14-1 has caused the Debian Bug report #749006, regarding xkb-data: fujitsu_vndr layouts syntax problem in ckbcomp to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 749006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749006 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xkb-data Version: 2.11-1 Severity: minor I made a script that uses ckbcomp to parse layout files in /usr/share/X11/xkb/symbols It works fine, but when it enters the fujitsu_vndr folder, ckbcomp errors out with the following error: /usr/bin/ckbcomp: instead of {overridefujitsu_vndr/usaugment keyAE01{[],[ka in fujitsu_vndr/jp expected string. ERROR: no valid keyboard layout found. Check the input. so i took a look at the layout files us and jp (the only ones in that folder) and i noticed they have this style: xkb_symbols { so they haven't got a name string before { character but they have a single xkb_symbols {} block These are the only layout files that are giving the error, because all other layouts have, for example xkb_symbols basic { Adding basic to the xkb_symbols block solves the problem for both layouts -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14.4-1-zen (SMP w/4 CPU cores; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information ---End Message--- ---BeginMessage--- Source: xkeyboard-config Source-Version: 2.14-1 We believe that the bug you reported is fixed in the latest version of xkeyboard-config, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 749...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Cristau jcris...@debian.org (supplier of updated xkeyboard-config package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 26 Apr 2015 16:30:30 +0200 Source: xkeyboard-config Binary: xkb-data xkb-data-udeb Architecture: source all Version: 2.14-1 Distribution: sid Urgency: medium Maintainer: Debian X Strike Force debian-x@lists.debian.org Changed-By: Julien Cristau jcris...@debian.org Description: xkb-data - X Keyboard Extension (XKB) configuration data xkb-data-udeb - X Keyboard Extension (XKB) configuration data (udeb) Closes: 749006 752680 776817 Changes: xkeyboard-config (2.14-1) unstable; urgency=medium . * New upstream release (closes: #776817). - fujitsu_vndr: add a name to xkb_symbols sections (closes: #749006) - Add option to swap right alt right control (closes: #752680) * Remove Cyril from Uploaders. * Drop fr-oss-rctrl.diff, upstream did a mostly equivalent change. Checksums-Sha1: b3646767a05b2dfa3384516f18901d1e64fe5651 2077 xkeyboard-config_2.14-1.dsc db566a0c87b2ba2cc158acadca1ee8aeeb18da67 1485921 xkeyboard-config_2.14.orig.tar.gz ce76f88e47e7822cf361fc17b5981f97a31aae6f 40558 xkeyboard-config_2.14-1.diff.gz 4dc06b53aded02de8dc99c35e6032a531ab71b84 614436 xkb-data_2.14-1_all.deb 8bf349abd7689ec914b7bca616e1f7b810096bcc 152508 xkb-data-udeb_2.14-1_all.udeb Checksums-Sha256: c67316a834fdad7018de4d412ae6c1a799112ab1c3887e739da155083d6f5e45 2077 xkeyboard-config_2.14-1.dsc 030df627c023f63eeb2995b1d0da83a3c7c079f979c79c0d588ee14f1f7c2ac1 1485921 xkeyboard-config_2.14.orig.tar.gz 8cbae88286316a97f002fab061501ce9f924dbeaca4fd1eba333d8a40ef63e54 40558 xkeyboard-config_2.14-1.diff.gz 39566e621e5049524809945dac203d29ba6aecf1c90b8fd8dab7055b4d8bc5c7 614436 xkb-data_2.14-1_all.deb e837b67376626dd9af2b0a23a8aa9b35548590e06f77d5161cb9907bfa06f961 152508 xkb-data-udeb_2.14-1_all.udeb Files: d0d289fc84b5094957429f30843f9a59 2077 x11 extra xkeyboard-config_2.14-1.dsc a820a86d93707c725fa20cf28ebf96cb 1485921 x11 extra xkeyboard-config_2.14.orig.tar.gz 70a5f80c781b675e5fea3b41313ecd66 40558 x11 extra xkeyboard-config_2.14-1.diff.gz e9cd785406ca08894b660dbbbebd75b5 614436 x11 extra xkb-data_2.14-1_all.deb
Bug#746409: Problem solved.
I have not used the computer for several months. Then I discovered that the motherboard was broken. After replacing a new motherboard and updating Debian GNOME works correct. dmesg|grep radeon output: [5.511786] [drm] radeon kernel modesetting enabled. [5.523032] radeon :01:05.0: enabling device ( - 0003) [5.52] radeon :01:05.0: BAR 6: can't assign [??? 0x flags 0x0] (bogus alignment) [5.523355] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM [5.523398] radeon :01:05.0: Fatal error during GPU init [5.523440] [drm] radeon: finishing device. [5.524639] radeon: probe of :01:05.0 failed with error -22 [5.526061] radeon :02:00.0: VRAM: 512M 0x - 0x1FFF (512M used) [5.526064] radeon :02:00.0: GTT: 512M 0x2000 - 0x3FFF [5.526167] [drm] radeon: 512M of VRAM memory ready [5.526169] [drm] radeon: 512M of GTT memory ready. [5.579009] radeon :02:00.0: firmware: direct-loading firmware radeon/RV730_pfp.bin [5.586026] radeon :02:00.0: firmware: direct-loading firmware radeon/RV730_me.bin [5.588686] radeon :02:00.0: firmware: direct-loading firmware radeon/R700_rlc.bin [5.589641] radeon :02:00.0: firmware: direct-loading firmware radeon/RV740_smc.bin [5.605496] radeon :02:00.0: firmware: direct-loading firmware radeon/RV710_uvd.bin [5.608451] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [5.622259] radeon :02:00.0: WB enabled [5.622268] radeon :02:00.0: fence driver on ring 0 use gpu addr 0x2c00 and cpu addr 0xffb75c00 [5.622275] radeon :02:00.0: fence driver on ring 3 use gpu addr 0x2c0c and cpu addr 0xffb75c0c [5.625160] radeon :02:00.0: fence driver on ring 5 use gpu addr 0x0005c598 and cpu addr 0xf8d1c598 [5.625216] radeon :02:00.0: irq 44 for MSI/MSI-X [5.625252] radeon :02:00.0: radeon: using MSI. [5.625303] [drm] radeon: irq initialized. [6.043974] [drm] radeon: dpm initialized [6.106284] fbcon: radeondrmfb (fb0) is primary device [6.140265] radeon :02:00.0: fb0: radeondrmfb frame buffer device [6.140267] radeon :02:00.0: registered panic notifier [6.140273] [drm] Initialized radeon 2.36.0 20080528 for :02:00.0 on minor 0 -- 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/6983921426974...@web3h.yandex.ru
Bug#778991: picture of the problem
signature.asc Description: This is a digitally signed message part
Bug#776411: nouveau: Another Nouveau gup lockup problem
On 2015-01-27 20:12 +0100, Tobias Schlemmer wrote: Package: xserver-xorg-video-nouveau Version: 1:1.0.11-1 Severity: normal File: nouveau Hi, I'm experiencing occasionally GPU lockups. So far I can tell, that in most cases iceweasel is involved. After opening a new tab, the image freezes, while the mouse can still be moved. After some time (or when I press Ctrl+Alt+F2) I can read the message “failed to idle channel“ (see attached logs). As some developers wish to have a different report for each GPU lookup issue (which can't be distinguished by the end user well) I open a new report for this issue. Please try a 3.18 kernel from experimental, and if you still experience GPU lockups, report them upstream. See http://nouveau.freedesktop.org/wiki/Bugs/ for instructions. Cheers, Sven -- 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/87fvao44fm@turtle.gmx.de
Bug#774283: Problem identified and solved
Hello together, i did not install the backup and found the problem now. The ATI driver from March 2014 did not fit together with the updated X-Server package. I downloaded and installed the newest Catalyst driver from here and X is running now again: http://support.amd.com/de-de/download/desktop?os=Linux+x86 Version Omega (14.12) from 09.12.2014. So this bug can be closed now. But you should think about an solution for the problem, because after the upgrade you did not have the chance to see anything, because the graphic card was dead. When you have not another PC, network and a running SSH-Server on the system, you can't do anything to get it working again. This is really fatal! From my experience in the last year it is getting more and more difficult to get an working desktop system with running X and sound with Debian. There are problems with ATI and NVidia, such as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767678 Is there really no chance to get this problems covered? A failsafe system that has the possibilty to have X with a standard VGA resolution would be a milestone for Debian. I wish you a happy new year! Karsten -- 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/54a3e4b0.6000...@home.decotrain.de
Bug#758274: Same problem here with i915_dri.so on 10.3.2-1
On Sun, Dec 14, 2014 at 20:20:16 +0100, Piotr Rudzki wrote: [26.637] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so failed (/usr/lib/x86_64-linux-gnu/dri/i965_dri.so: undefined symbol: _glapi_tls_Dispatch) [26.637] (EE) AIGLX: reverting to software rendering [27.269] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so failed (/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: undefined symbol: _glapi_tls_Dispatch) [27.269] (EE) GLX: could not load software renderer The same problem exists in mesa-10.3.2-1. This is not our bug, it's most likely due to a hand-installed version of mesa. Cheers, Julien signature.asc Description: Digital signature
Bug#771416: No problem with Wheezy kernel
Dear maintainers, I just wanted to add that this problem does not appear with Wheezy. Thanks for your time and work, YvanM -- 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/1418664574.1878.2.ca...@openmailbox.org
Bug#758274: Same problem here with i915_dri.so on 10.3.2-1
[26.637] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so failed (/usr/lib/x86_64-linux-gnu/dri/i965_dri.so: undefined symbol: _glapi_tls_Dispatch) [26.637] (EE) AIGLX: reverting to software rendering [27.269] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so failed (/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: undefined symbol: _glapi_tls_Dispatch) [27.269] (EE) GLX: could not load software renderer The same problem exists in mesa-10.3.2-1. -- 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/548de2f0.4040...@gmail.com
Bug#749006: xkb-data: fujitsu_vndr layouts syntax problem in ckbcomp
Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=85489 On Thu, May 22, 2014 at 23:31:45 +, smxs...@gmail.com wrote: Package: xkb-data Version: 2.11-1 Severity: minor I made a script that uses ckbcomp to parse layout files in /usr/share/X11/xkb/symbols It works fine, but when it enters the fujitsu_vndr folder, ckbcomp errors out with the following error: /usr/bin/ckbcomp: instead of {overridefujitsu_vndr/usaugment keyAE01{[],[ka in fujitsu_vndr/jp expected string. ERROR: no valid keyboard layout found. Check the input. so i took a look at the layout files us and jp (the only ones in that folder) and i noticed they have this style: xkb_symbols { so they haven't got a name string before { character but they have a single xkb_symbols {} block These are the only layout files that are giving the error, because all other layouts have, for example xkb_symbols basic { Adding basic to the xkb_symbols block solves the problem for both layouts Forwarded upstream at the url above. Thanks for the report. Cheers, Julien signature.asc Description: Digital signature
Processed: Re: Bug#749006: xkb-data: fujitsu_vndr layouts syntax problem in ckbcomp
Processing control commands: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=85489 Bug #749006 [xkb-data] xkb-data: fujitsu_vndr layouts syntax problem in ckbcomp Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=85489'. -- 749006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749006 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b749006.141434890519725.transcr...@bugs.debian.org
Bug#765490: xserver-xorg-video-vmware problem details
I have also been experiencing the window resize problems. My problems are there whether or not VMware tools as provided with VMware workstation 10 are installed. I have been running Debian Jessie recently installed from debian-testing-amd64-netinst.iso in VMware workstation 10 running under Windows 8.1. Window resize was occurring when the 800x600 login screen was replaced by the 1440x900 desktop (i.e. not full screen) that I have been using. I could prevent this resize by creating /etc/X11/xorg.conf and setting: 'Option PreferredMode 1440x900' in 'Section Monitor' Once the display resolution was made fixed then the problems disappeared unless I deliberately used the desktop System-Display configuration tool to change the resolution to 800x600 for example and then back again. The most obvious and consistent problems following resize were: * On shutdown the Xorg process went CPU bound for about 90 seconds until systemd gave up waiting and killed it and then shutdown proceeding normally. Control via the VMware desktop was lost as I could not try switching to a different virtual terminal etc. * Attempting to switch to a different virtual terminal (CTRL ALT F1) instead of shutting down had the same effect. Although this time Xorg remained CPU bound indefinitely and control via the VMware desktop was again lost. * The behaviour on logout from the desktop was similar to switching to a different virtual terminal. I then discovered that it was possible to still connect to the system via ssh. This is how I discovered that Xorg was becoming CPU bound. If I killed the Xorg process then after a while a new one would be created but the displayed login screen was somewhat garbled. However killing Xorg, then running 'systemctl stop gdm', then 'systemctl start gdm' usually (but not always) provided a clean login screen and everything behaved normally. I tried to download xserver-xorg-video-vmware-dbg but it does not exist so I downloaded xserver-xorg-video-vmware-13.0.2 source and modified debian/rules and debian/control to enable the production of debug symbols and then built it. I was then able to use gdb to connect to Xorg whilst it was stuck CPU bound and got traces like the following: ^C Program received signal SIGINT, Interrupt. vmwgfx_pixmap_present_readback (vsaa=0x7f6e388e5f40, pixmap=0x7f6e3892d4b0, region=0x7f6e3892d528) at ../../vmwgfx/vmwgfx_saa.c:236 236 struct saa_pixmap *spix = saa_get_saa_pixmap(pixmap); (gdb) where #0 vmwgfx_pixmap_present_readback (vsaa=0x7f6e388e5f40, pixmap=0x7f6e3892d4b0, region=0x7f6e3892d528) at ../../vmwgfx/vmwgfx_saa.c:236 #1 0x7f6e3132118e in vmwgfx_download_from_hw (driver=0x7f6e388e5f40, pixmap=0x7f6e3892d4b0, readback=0x7f6e3892d528) at ../../vmwgfx/vmwgfx_saa.c:353 #2 0x7f6e3132260d in vmwgfx_saa_drop_master (pScreen=optimized out) at ../../vmwgfx/vmwgfx_saa.c:1608 #3 0x7f6e3131b623 in drv_leave_vt (arg=0x7f6e388714e0) at ../../vmwgfx/vmwgfx_driver.c:1185 #4 0x7f6e36f377d4 in xf86XVLeaveVT (pScrn=0x7f6e388714e0) at ../../../../hw/xfree86/common/xf86xv.c:1349 #5 0x7f6e333a6f8d in glxDRILeaveVT (scrn=0x7f6e388714e0) at ../../glx/glxdri2.c:837 #6 0x7f6e36f1ea97 in xf86VTLeave () at ../../../../hw/xfree86/common/xf86Events.c:492 #7 0x7f6e36ee4bab in WakeupHandler (result=result@entry=2, pReadmask=pReadmask@entry=0x7f6e372e1f40 LastSelectMask) at ../../dix/dixutils.c:423 #8 0x7f6e3703bee7 in WaitForSomething (pClientsReady=pClientsReady@entry=0x7f6e38cf4520) at ../../os/WaitFor.c:229 #9 0x7f6e36edfce1 in Dispatch () at ../../dix/dispatch.c:361 #10 0x7f6e36ee4066 in dix_main (argc=17, argv=0x776893e8, envp=optimized out) at ../../dix/main.c:296 #11 0x7f6e34b9fb45 in __libc_start_main (main=0x7f6e36ece4e0 main, argc=17, argv=0x776893e8, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x776893d8) at libc-start.c:287 #12 0x7f6e36ece50e in _start () I interrupted several times and vmwgfx_saa_drop_master() was always in the stack trace Looking at the source for vmwgfx_saa_drop_master() there is a loop that steps through vsaa-pixmaps. WSBMLISTFOREACH(list, vsaa-pixmaps) { SNIP } I added the following diagnostics to the loop if (limit 50){ LogMessage(X_ERROR, XXX (%d) list = 0x%lx\n, limit, list); limit++; } to print out up to 50 list values before going silent. Normally there were 7 different values (i.e. if no screen resize done). Oct 22 19:49:46 debian gdm-Xorg-:0[588]: (EE) XXX hrg vmwgfx_saa_drop_master entry. pixmaps = 0x7fc97184a0a8 Oct 22 19:49:46 debian gdm-Xorg-:0[588]: (EE) XXX (1) list = 0x7fc971891620 Oct 22 19:49:46 debian gdm-Xorg-:0[588]: (EE) XXX (2) list = 0x7fc971893f00 Oct 22
Bug#754822: same problem with a ALPS device
hi, during an apt-get upgrade today, my xserver-xorg-input-synaptics was upgraded to 1.8.0-1 and the same problem arise. I'm not using an Elantech mouse, but an ALPS: $ egrep -i 'synap|alps|etps' /proc/bus/input/devices N: Name=ALPS PS/2 Device N: Name=AlpsPS/2 ALPS GlidePoint I noticed the problem in GDM login screen, xfce and fluxbox. If I plug an external usb mouse, the pointer moves normally with the mouse and slowly with the touchpad. more info: $ dpkg -l xserver-xorg-input-synaptics 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) ||/ Nome Versão Arquitectura Descrição +++-==-==-==-== ii xserver-xorg-input 1.8.0-1i386 Synaptics TouchPad driver for X.Org server $ more /etc/X11/xorg.conf.d/50-synaptics.conf Section InputClass Identifier touchpad catchall Driver synaptics MatchIsTouchpad on # This option is recommend on all Linux systems using evdev, but cannot be # enabled by default. See the following link for details: # http://who-t.blogspot.com/2010/11/how-to-ignore-configuration-errors.html # MatchDevicePath /dev/input/event* EndSection Section InputClass Identifier touchpad ignore duplicates MatchIsTouchpad on MatchOS Linux MatchDevicePath /dev/input/mouse* Option Ignore on EndSection # This option enables the bottom right corner to be a right button on # non-synaptics clickpads. # This option is only interpreted by clickpads. Section InputClass Identifier Default clickpad buttons MatchDriver synaptics Option SoftButtonAreas 50% 0 82% 0 0 0 0 0 # To disable the bottom edge area so the buttons only work as buttons, # not for movement, set the AreaBottomEdge # Option AreaBottomEdge 82% EndSection # This option disables software buttons on Apple touchpads. # This option is only interpreted by clickpads. Section InputClass Identifier Disable clickpad buttons on Apple touchpads MatchProduct Apple|bcm5974 MatchDriver synaptics Option SoftButtonAreas 0 0 0 0 0 0 0 0 EndSection -- 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/CAPr829=lnagd93krorx-0qd57kycxoo_56sajtsbmj0pzv2...@mail.gmail.com
Bug#754822: same problem with a ALPS device
On Wed, Jul 16, 2014 at 12:32:29PM -0300, Fred Maranhão wrote: hi, during an apt-get upgrade today, my xserver-xorg-input-synaptics was upgraded to 1.8.0-1 and the same problem arise. I'm not using an Elantech mouse, but an ALPS: $ egrep -i 'synap|alps|etps' /proc/bus/input/devices N: Name=ALPS PS/2 Device N: Name=AlpsPS/2 ALPS GlidePoint I noticed the problem in GDM login screen, xfce and fluxbox. Ditto, with pretty much similar setup. I only have one screen (my laptop screen). I rebuilt xsserver-xorg with the patch pointed to (http://cgit.freedesktop.org/xorg/xserver/commit/?id=9a19bf06b5b409fa0d5b5932e29cd4c5545052c5) and installed it; my mouse now works absolutely fine again. Julian -- 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/20140717001520.ga7...@d-and-j.net
Bug#714531: xserver-xorg-core: Xorg freezes with i915 intel_crtc_wait_for_pending_flips problem
On Thu, 11 Jul 2013 22:48:05 +0200 Francesco Poli wrote: On Wed, 10 Jul 2013 22:31:25 +0200 Francesco Poli wrote: [...] I am currently trying to see what happens if I disable dpms in xscreensaver... After disabling dpms, I again experienced the slowness issue similar to #682816. After leaving the box with a locked display, I type my password, unlock the X session and find that almost everything (especially the text displayed inside XTerm windows) is repainted extremely slowly. If I close all the graphical applications and try to exit from the X session (which was started with startx), I never get back to the console. Hence I cannot login again and the only way out is to press the power button to shut the system down (luckily the power button press event is handled and triggers a clean shutdown...). I had found out that the issue vanishes when using SNA acceleration. Hence, I set: $ cat /etc/X11/xorg.conf Section Device Identifier Intel Graphics Driver intel Option AccelMethod sna EndSection and I am keeping DPMS disabled. I have just given another try without forcing the SNA acceleration (that is to say, after moving /etc/X11/xorg.conf out of the way): I was again able to reproduce the slowness-and-never-get-back-to-console issue. Is there any progress on this issue? Has the bug been investigated? Has the report been forwarded upstream? I am looking forward to hearing back from the X Strike Force: thanks for your time and for any help you may provide. Olivier, did you manage to find out a (better) workaround? Do you still experience the freeze issue? Do you also experience the slowness issue? Please let me know: thanks for your time. -- http://www.inventati.org/frx/ fsck is a four letter word... . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgp_hisY2PxoN.pgp Description: PGP signature
Bug#749963: Should be software problem
I think this issue is software problem (not hardware), because, when I use chromium with flash (download from google-chrome), watching youtue movie (flash version), the movie is very smooth, and the sound is also good. Anyone have idea? Thanks. -- 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/53898d8b.2070...@gmail.com
Bug#749006: xkb-data: fujitsu_vndr layouts syntax problem in ckbcomp
Package: xkb-data Version: 2.11-1 Severity: minor I made a script that uses ckbcomp to parse layout files in /usr/share/X11/xkb/symbols It works fine, but when it enters the fujitsu_vndr folder, ckbcomp errors out with the following error: /usr/bin/ckbcomp: instead of {overridefujitsu_vndr/usaugment keyAE01{[],[ka in fujitsu_vndr/jp expected string. ERROR: no valid keyboard layout found. Check the input. so i took a look at the layout files us and jp (the only ones in that folder) and i noticed they have this style: xkb_symbols { so they haven't got a name string before { character but they have a single xkb_symbols {} block These are the only layout files that are giving the error, because all other layouts have, for example xkb_symbols basic { Adding basic to the xkb_symbols block solves the problem for both layouts -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14.4-1-zen (SMP w/4 CPU cores; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (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: https://lists.debian.org/20140522233144.10900.24672.reportbug@Arch
Bug#640699: marked as done (keyboard problem with xserver xfbdev: why does it not work?)
Your message dated Sun, 13 Apr 2014 18:09:39 +0200 with message-id 20140413160939.ga1...@betterave.cristau.org and subject line Re: Bug#640699: keyboard problem with xserver xfbdev: why does it not work? has caused the Debian Bug report #640699, regarding keyboard problem with xserver xfbdev: why does it not work? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 640699: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640699 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: xserver-xfbdev version: 2:1.7.7-13 I have installed on my small laptop xfbdev xserver, because the xorg xserver does not work on my system. I have changed the link /usr/bin/X to /usr/bin/Xfbdev (the same /etc/X11/X to /usr/bin/Xfbdev) then i have edit the /etc/X11/xinit/xserverrc script just including the following: exec /usr/bin/X -screen 800x600x16 -mouse ps2 -keybd keyboard -nolisten tcp $@ When server start, all works good but no keyboard, just i see on screen the following message: DRIVER LINUX CONSOLE KEYBOARD WANTED What does mean it? Does it want a package to work properly? Wich package? I have tried also to start it with my keyboard driver (i think): exec /usr/bin/X -screen 800x600x16 -mouse ps2 -keybd pc102 -nolisten tcp $@ but i was not able to resolve the question. I use Debian Squeeze with generic 2.6-i686 kernel on a small laptop panasonic CF-M34 with 4mb video ram and svga screen. ---End Message--- ---BeginMessage--- Source: xorg-server Source-Version: 2:1.14.99.3-1 On Tue, Sep 6, 2011 at 19:07:21 +0200, pasquale_fr...@libero.it wrote: package: xserver-xfbdev version: 2:1.7.7-13 I have installed on my small laptop xfbdev xserver, because the xorg xserver does not work on my system. I have changed the link /usr/bin/X to /usr/bin/Xfbdev (the same /etc/X11/X to /usr/bin/Xfbdev) then i have edit the /etc/X11/xinit/xserverrc script just including the following: exec /usr/bin/X -screen 800x600x16 -mouse ps2 -keybd keyboard -nolisten tcp $@ When server start, all works good but no keyboard, just i see on screen the following message: DRIVER LINUX CONSOLE KEYBOARD WANTED Unfortunately this didn't get fixed before we stopped shipping Xfbdev. Sorry about that. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Bug#418818: marked as done (xterm: strange creeping background problem on redraw when using mutt and screen)
Your message dated Tue, 21 Jan 2014 23:19:44 + with message-id 52df0090.1060...@solveig.org and subject line Re: xterm: strange creeping background problem on redraw when using mutt and screen - closing has caused the Debian Bug report #418818, regarding xterm: strange creeping background problem on redraw when using mutt and screen to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 418818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xterm Version: 225-1 Severity: normal Tags: upstream I'm not sure exactly where the bug lies here -- it could be in screen, mutt, ncurses, or xterm. I'm going with xterm for now because rxvt, while it also exhibits a bug, doesn't exhibit exactly the same bug. It appears that xterm sometimes forgets what color to paint certain character cells. How to reproduce: 1) Be running screen. 2) Have mutt running with a folder (index) view in 2 different screen windows. 3) Go to the one of the mutt windows in screen. (You may already notice that the top-line menu bar's background color is not drawn all the way across the xterm window.) 4) Switch to the other mutt window in screen. (You should notice that the top-line menu bar's background color is not present all the way across the window. For me, it stops with the last character that has a foreground glyph.) 5) Press enter to tell mutt to view a message in the folder. (Again, the background color of the top line stops with the last real character drawn.) 6) Press 'i' to tell mutt to return to the folder view. (Notice how some correct background color has crept in from the right side, leaving a gap in the middle of the top line with the default terminal background color.) 7) Repeat steps 5) and 6), pressing no other keys, and watch how each time you return to the folder view, the gap with the wrong background color gets progressively smaller. 8) Eventually, the folder index is rendered correctly. The gap persists in message view as well, but doesn't get larger. Some of the gap is clobbered from the left because mutt writes more text to the menu bar in that view than in folder view, though. 9) CTRL-L at any time (with the affected screen window active) cleans all of this up. rxvt-unicode-ml seems to be broken slightly differently. Instead, as you repeat steps 5) and 6), it forgets the correct background color for more and more character cells, not fewer. I took a ton of screenshots to document this. Please find a compressed tar archive at the following URL: http://necrotic.deadbeast.net/tmp/creeping_mutt.tar.gz It contains the following files: xterm01.png xterm02.png xterm03.png xterm04.png xterm05.png xterm06.png xterm07.png xterm08.png xterm09.png xterm10.png xterm11.png xterm12.png xterm13.png xterm14.png xterm15.png xterm16.png xterm17.png xterm18.png xterm19.png rxvt01.png rxvt02.png rxvt03.png -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: powerpc (ppc) Kernel: Linux 2.6.15-1-powerpc-smp (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xterm depends on: ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libfontconfig1 2.4.2-1.2generic font configuration library ii libice6 1:1.0.1-2X11 Inter-Client Exchange library ii libncurses5 5.5-5Shared libraries for terminal hand ii libsm6 1:1.0.1-3X11 Session Management library ii libx11-62:1.0.3-7X11 client-side library ii libxaw7 1:1.0.2-4X11 Athena Widget library ii libxext61:1.0.1-2X11 miscellaneous extension librar ii libxft2 2.1.8.2-8FreeType-based font drawing librar ii libxmu6 1:1.0.2-2X11 miscellaneous utility library ii libxt6 1:1.0.2-2X11 toolkit intrinsics library ii xbitmaps1.0.1-2 Base X bitmaps Versions of packages xterm recommends: ii xutils 1:7.1.ds.3-1 X Window System utility programs -- no debconf information ---End Message--- ---BeginMessage--- Hi! I'm closing this bug, since it was tagged unreproductible for years without answer. If you still encounter this problem, please feel free to re-open it or ask me to do it. Solveig---End
Bug#588802: marked as done (After log out, xorg crashes, problem with internal graphic card)
Your message dated Wed, 18 Dec 2013 12:32:41 + with message-id e1vtgir-0007wi...@franck.debian.org and subject line Bug#732478: Removed package(s) from unstable has caused the Debian Bug report #588802, regarding After log out, xorg crashes, problem with internal graphic card to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 588802: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xorg Version: 1:7.5+6 Severity: normal Xorg has some problem with my internal graphic card which is: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Dipslpay Adapter Every time I log off the xorg crashes and I return to terminal login. The same happens in Lenny, while there the computer hangs and I have to reboot the computer to get the login screen. I have around 70 pc with this graphic card running Lenny (skolelinux) and it happens with all of them! -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core) Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xorg depends on: ii konsole [x-terminal-emulator] 4:4.4.4-1 X terminal emulator for KDE 4 ii libgl1-mesa-dri 7.7.1-3A free implementation of the OpenG ii libgl1-mesa-glx [libgl1] 7.7.1-3A free implementation of the OpenG ii libglu1-mesa 7.7.1-3The OpenGL utility library (GLU) ii x11-apps 7.5+5 X applications ii x11-session-utils 7.5+1 X session utilities ii x11-utils 7.5+4 X11 utilities ii x11-xfs-utils 7.4+1 X font server utilities ii x11-xkb-utils 7.5+2 X11 XKB utilities ii x11-xserver-utils 7.5+1+b1 X server utilities ii xauth 1:1.0.4-1 X authentication utility ii xfonts-100dpi 1:1.0.1100 dpi fonts for X ii xfonts-75dpi 1:1.0.175 dpi fonts for X ii xfonts-base 1:1.0.1standard fonts for X ii xfonts-scalable 1:1.0.1-1 scalable fonts for X ii xfonts-utils 1:7.5+2X Window System font utility progr ii xinit 1.2.0-2X server initialisation tool ii xkb-data 1.8-1 X Keyboard Extension (XKB) configu ii xorg-docs-core1:1.5-1Core documentation for the X.org X ii xserver-xorg 1:7.5+6the X.Org X server ii xterm [x-terminal-emulator] 261-1 X terminal emulator xorg recommends no packages. Versions of packages xorg suggests: pn xorg-docs none (no description available) -- no debconf information ---End Message--- ---BeginMessage--- Version: 1:0.10.4-1+rm Dear submitter, as the package xserver-xorg-video-sis has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/732478 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain)---End Message---
Bug#729157: Problem gone
Hello, the problem which I reported a few days back disappeared again and I cannot reproduce anymoe. I suggest to close the bug report since I did not upgrade xserver-xorg-video- intel and the bug went away. Thanks Rainer -- Rainer Dorsch http://bokomoko.de/ -- 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/6780465.MuSoKMAzvg@blackbox
Bug#730351: xorg: Fresh Jessie, same problem
Package: xorg Followup-For: Bug #730351 Because my system is really unstable since I encountered this bug, I tried wiping everything and installed Jessie from scratch. Turns out I get the same behaviour, just worse. Now gnome-shell as well as xorg go crazy with CPU usage. I don't have the xorg package installed though, so this is probably the wrong thread to have this bug posted. It probably has to go to xserver-xorg? I would really appreciate some help. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xserver-xorg depends on: ii libc6 2.17-93 ii x11-xkb-utils 7.7~1 ii xkb-data 2.5.1-3 ii xserver-xorg-core 2:1.14.3-4 ii xserver-xorg-input-all1:7.7+4 ii xserver-xorg-input-evdev [xorg-driver-input] 1:2.8.2-1 ii xserver-xorg-input-mouse [xorg-driver-input] 1:1.9.0-1+b1 ii xserver-xorg-input-synaptics [xorg-driver-input] 1.7.1-2+b1 ii xserver-xorg-input-vmmouse [xorg-driver-input]1:13.0.0-1+b1 ii xserver-xorg-input-wacom [xorg-driver-input] 0.23.0+20131011-1 ii xserver-xorg-video-all1:7.7+4 ii xserver-xorg-video-ati [xorg-driver-video]1:7.2.0-1+b2 ii xserver-xorg-video-cirrus [xorg-driver-video] 1:1.5.2-1+b1 ii xserver-xorg-video-fbdev [xorg-driver-video] 1:0.4.4-1 ii xserver-xorg-video-intel [xorg-driver-video] 2:2.21.15-1+b2 ii xserver-xorg-video-mach64 [xorg-driver-video] 6.9.4-1+b1 ii xserver-xorg-video-mga [xorg-driver-video]1:1.6.2-1+b1 ii xserver-xorg-video-modesetting [xorg-driver-video]0.8.0-1+b2 ii xserver-xorg-video-neomagic [xorg-driver-video] 1:1.2.8-1 ii xserver-xorg-video-nouveau [xorg-driver-video]1:1.0.10-1 ii xserver-xorg-video-openchrome [xorg-driver-video] 1:0.3.3-1 ii xserver-xorg-video-qxl [xorg-driver-video]0.1.0-2.1 ii xserver-xorg-video-r128 [xorg-driver-video] 6.9.1-1 ii xserver-xorg-video-radeon [xorg-driver-video] 1:7.2.0-1+b2 ii xserver-xorg-video-savage [xorg-driver-video] 1:2.3.7-2 ii xserver-xorg-video-siliconmotion [xorg-driver-video] 1:1.7.7-2 ii xserver-xorg-video-sisusb [xorg-driver-video] 1:0.9.6-2 ii xserver-xorg-video-tdfx [xorg-driver-video] 1:1.4.5-1 ii xserver-xorg-video-trident [xorg-driver-video]1:1.3.6-2 ii xserver-xorg-video-vesa [xorg-driver-video] 1:2.3.3-1+b1 ii xserver-xorg-video-vmware [xorg-driver-video] 1:13.0.1-2 Versions of packages xserver-xorg recommends: ii libgl1-mesa-dri 9.2.2-1 -- 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/20131130130445.8264.58300.report...@jessienut.fritz.box
Bug#729758: xorg: startx fails with a screen indicating an unknown problem and a logout button
Package: xorg Version: 1:7.7+3~deb7u1 Severity: important Dear Maintainer, I have completed a new install of Debian 7 and updated it as of 16-Nov-2013 (version 7.2). When I try to start X (i.e., enter the startx command) the screen goes blank for a long time (i.e., the better part of a minute) then displays an graphic error screen indicating something has gone wrong and for me to try again. The display includes a button marked Log out. The cursor is working and when I click the button the server shutsdown with no indication of a problem. The log file shows only a few warnings that seem to be unimportant. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Sep 15 10:22 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2027892 Oct 21 11:42 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV11 [GeForce2 MX/MX 400] [10de:0110] (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 3.2.0-4-686-pae (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.51-1 Xorg X server log files on system: -- -rw-r--r-- 1 root root 39040 Nov 16 12:42 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 2128.377] X.Org X Server 1.12.4 Release Date: 2012-08-27 [ 2128.383] X Protocol Version 11, Revision 0 [ 2128.385] Build Operating System: Linux 3.2.0-4-amd64 i686 Debian [ 2128.387] Current Operating System: Linux intel1 3.2.0-4-686-pae #1 SMP Debian 3.2.51-1 i686 [ 2128.387] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-686-pae root=UUID=84ecc6b5-a4c1-44dd-b140-824a10e4c67c ro single [ 2128.391] Build Date: 21 October 2013 05:31:52PM [ 2128.393] xorg-server 2:1.12.4-6+deb7u1 (Moritz Muehlenhoff j...@debian.org) [ 2128.395] Current version of pixman: 0.26.0 [ 2128.399]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 2128.399] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 2128.407] (==) Log file: /var/log/Xorg.0.log, Time: Sat Nov 16 12:40:55 2013 [ 2128.409] (==) Using system config directory /usr/share/X11/xorg.conf.d [ 2128.411] (==) ServerLayout Configured Layout [ 2128.411] (**) |--Screen NVIDIA/Samsung Screen (0) [ 2128.411] (**) | |--Monitor Samsung Monitor [ 2128.411] (**) | |--Device NVIDIA Video Device [ 2128.411] (==) Automatically adding devices [ 2128.412] (==) Automatically enabling devices [ 2128.412] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [ 2128.412]Entry deleted from font path. [ 2128.412] (WW) The directory /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType does not exist. [ 2128.412]Entry deleted from font path. [ 2128.412] (==) 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 [ 2128.412] (==) ModulePath set to /usr/lib/xorg/modules [ 2128.412] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 2128.412] (II) Loader magic: 0xb771d5a0 [ 2128.412] (II) Module ABI versions: [ 2128.412]X.Org ANSI C Emulation: 0.4 [ 2128.412]X.Org Video Driver: 12.1 [ 2128.412]X.Org XInput driver : 16.0 [ 2128.412]X.Org Server Extension : 6.0 [ 2128.414] (--) PCI:*(0:1:0:0) 10de:0110:10de:004a rev 161, Mem @ 0xfd00/16777216, 0xe800/134217728, BIOS @ 0x/65536 [ 2128.414] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) [ 2128.414] (II) LoadModule: extmod [ 2128.415] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so [ 2128.416] (II) Module extmod: vendor=X.Org Foundation [ 2128.417]compiled for 1.12.4, module version = 1.0.0 [ 2128.417]Module class: X.Org Server Extension [ 2128.417]ABI class: X.Org Server Extension, version 6.0 [ 2128.417] (II) Loading extension SELinux [ 2128.417] (II) Loading extension MIT-SCREEN-SAVER [ 2128.417] (II) Loading extension XFree86-VidModeExtension [ 2128.417] (II) Loading extension XFree86-DGA [ 2128.417] (II) Loading extension DPMS [ 2128.417] (II) Loading extension XVideo [ 2128.417] (II) Loading extension XVideo-MotionCompensation
Bug#645468: marked as done (xserver-common: Left Mouse Button does not work - Dell Mouse - Replugin it fixes the problem)
Your message dated Tue, 08 Oct 2013 01:22:28 + with message-id 52535e54.2080...@solveig.org and subject line Re: xserver-common: Left Mouse Button does not work - Dell Mouse - Replugin it fixes the problem - closing has caused the Debian Bug report #645468, regarding xserver-common: Left Mouse Button does not work - Dell Mouse - Replugin it fixes the problem to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 645468: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xserver-common Version: 2:1.11.1-1 Severity: normal Tags: upstream Replugin the mouse fixes the problem for me but it is disturbing. *-usb:0 description: USB Controller product: SB7x0/SB8x0/SB9x0 USB OHCI0 Controller vendor: ATI Technologies Inc physical id: 12 bus info: pci@:00:12.0 version: 00 width: 32 bits clock: 66MHz capabilities: ohci bus_master configuration: driver=ohci_hcd latency=64 resources: irq:18 memory:d440a000-d440afff -- System Information: Debian Release: wheezy/sid APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xserver-common depends on: ii x11-common 1:7.6+9 ii x11-xkb-utils 7.6+4 ii xkb-data 2.1-2 Versions of packages xserver-common recommends: ii xauth1:1.0.6-1 ii xfonts-base 1:1.0.3 xserver-common suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Hi! I'm closing this bug, since it was tagged moreinfo for years without answer. If you still encounter this problem, please feel free to re-open it.---End Message---
Bug#695496: marked as done (mesa: Torchlight crashes because of mesa texture problem)
Your message dated Sat, 28 Sep 2013 18:16:56 +0200 (CEST) with message-id 1162443426.1028741380385016433.JavaMail.defaultUser@defaultHost and subject line fixed in 9.1 has caused the Debian Bug report #695496, regarding mesa: Torchlight crashes because of mesa texture problem to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 695496: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695496 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mesa Version: 8.0.5-3 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** The game Torchlight for Linux crashes when entering certain location. It seems the problem is in mesa package and its checks for mipmap dimensions (see http://forums.runicgames.com/viewtopic.php?f=24t=34893sid=c4c3efa2a55860e0ced3359f27753d0bstart=20). The fix for mesa should be in theese links: http://lists.freedesktop.org/archives/mesa-dev/2012-October/028210.html http://lists.freedesktop.org/archives/mesa-dev/2012-October/028211.html or in the bug filled on freedestop.org: https://bugs.freedesktop.org/show_bug.cgi?id=55445 but they are apparently for diferent version of mesa then contain in current Debian unstable. *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- Version: 9.1.3-1---End Message---
Bug#445023: marked as done (compiz: Problem with struts on top and left panels)
Your message dated Fri, 16 Aug 2013 13:46:15 + with message-id e1vakm3-0002x4...@franck.debian.org and subject line Bug#719870: Removed package(s) from unstable has caused the Debian Bug report #445023, regarding compiz: Problem with struts on top and left panels to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 445023: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=445023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: compiz Version: 0.5.2-2 Severity: normal I use ROX-Filer which has panels you can use a bit like GNOME panels. However, only panels on the bottom or right screen edge work correctly. Top and left panels are placed away from the edge by the same distance as the struts they set to make other windows avoid them. The panels do have GDK_WINDOW_TYPE_HINT_DOCK set which is sufficient to avoid this problem with metacity. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22.9 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages compiz depends on: ii compiz-core 0.5.2-2+b1 OpenGL window and compositing mana ii compiz-gnome 0.5.2-2+b1 OpenGL window and compositing mana ii compiz-gtk0.5.2-2+b1 OpenGL window and compositing mana ii compiz-plugins0.5.2-2+b1 OpenGL window and compositing mana compiz recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- Version: 0.8.4-5.2+rm Dear submitter, as the package compiz has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/719870 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Ansgar Burchardt (the ftpmaster behind the curtain)---End Message---
Bug#714531: xserver-xorg-core: Xorg freezes with i915 intel_crtc_wait_for_pending_flips problem
On Wed, 10 Jul 2013 22:31:25 +0200 Francesco Poli wrote: [...] I am currently trying to see what happens if I disable dpms in xscreensaver... After disabling dpms, I again experienced the slowness issue similar to #682816. After leaving the box with a locked display, I type my password, unlock the X session and find that almost everything (especially the text displayed inside XTerm windows) is repainted extremely slowly. If I close all the graphical applications and try to exit from the X session (which was started with startx), I never get back to the console. Hence I cannot login again and the only way out is to press the power button to shut the system down (luckily the power button press event is handled and triggers a clean shutdown...). After doing this, I found the attached snippet inside /var/log/kern.log: it's really similar to what I obtained with dpms on, although not identical. Maybe #714531 and #682816 are two sides of the same coin? -- http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt New GnuPG key, see the transition document! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE snippet_nodpms_kern.log Description: Binary data pgpxP2rk0rvbS.pgp Description: PGP signature
Bug#714531: xserver-xorg-core: Xorg freezes with i915 intel_crtc_wait_for_pending_flips problem
On Sun, 30 Jun 2013 15:58:58 +0200 Olivier Berger wrote: Hi. I just encountered a freeze on a Dell latitude E5400, where X is frozen, but the machine is accessible through SSH. Here's the message I found in the syslog [...] Hello, I seem to experience basically the same bug on a jessie/sid desktop box with integrated Intel graphics. The attached /var/log/kern.log snippet looks very similar to what Olivier quoted. The same information may be found in /var/log/messages. I see nothing special in /var/log/Xorg.0.log The issue started after upgrading to Linux kernel version 3.9 with Intel video driver version 2:2.20.14-1 (from experimental, I had upgraded in the hope to solve a bug similar to #682816). I experience the bug once every 3 or 4 days, after leaving the box with a locked display (with xscreensaver) for more than 1 hour: when it happens, I find the screen in energy saving mode (I configured xscreensaver with dpmsStandby: 1:00:00 and dpmsSuspend: 1:00:00), but there's no way to wake the screen up again, since all keyboard/mouse events are completely ignored. The only way out seems to be to power cycle the box. :-( I am currently trying to see what happens if I disable dpms in xscreensaver... I have: $ lspci -v | grep -A 9 VGA 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device 8276 Flags: bus master, fast devsel, latency 0, IRQ 44 Memory at fe40 (64-bit, non-prefetchable) [size=4M] Memory at d000 (64-bit, prefetchable) [size=256M] I/O ports at cc00 [size=8] Expansion ROM at unassigned [disabled] Capabilities: access denied Kernel driver in use: i915 $ dpkg -l | grep xserver-xorg-video-intel | cut -c 1-70 ii xserver-xorg-video-intel 2:2.20.14-1 $ cat /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 $ dpkg -l | grep linux-image-3.9 | cut -c 1-70 ii linux-image-3.9-1-amd64 3.9.8-1 Should this bug be reassigned to xserver-xorg-video-intel 2:2.20.14-1 ? I hope it may be fixed soon, since it's really annoying... Thanks to anyone who may provide any kind of help. -- http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt New GnuPG key, see the transition document! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE snippet_kern.log Description: Binary data pgpFM41AW7Ovy.pgp Description: PGP signature
Bug#696176: No problem here
Filipus Klutiero chea...@gmail.com writes: I also use a Radeon HD 7660D (on A10-5700) and do not experience this issue on my wheezy install (using Linux 3.8). Can you reproduce with current versions? Yes, I can still reproduce this using xserver-xorg-video-radeon 1:6.14.4-8 and linux-image-3.8-trunk-amd64 3.8.5-1~experimental.1. Sascha pgpL3C83BWY2A.pgp Description: PGP signature
Bug#646989: xserver-xorg: Exactly the same Problem here
Package: xserver-xorg Version: 1:7.7+2 Followup-For: Bug #646989 Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? I wanted to upgrade from Squeeze to Wheezy, but I failed because of the described bug. I did a fresh-install of Wheezy (because I thought it is somehow my fault) ... but bug appeared again. The Graphic-Card worked on Squeeze with both, the nouveau-driver and the nvidia-driver .. now it seems not to work with any of them. I tried different re-configurations of the X-Server in /usr/share/X11/xorg.conf.d Somehow I got the error-message failed to load module nv disappear .. however it did not help on the bug itself. The bug: When starting Gnome, before the login-shell comes up, the screen stays black. Only the mouse-pointer is visible (it can be moved around) If I press STRG+ALT+F1, sometimes I can observe the text-output of a endless-loop, in which Xorg seems to stuck. But I dont know how I can get my hand on this text-output. Below as well my Xorg.0.log Think I as well will go for a dual-boot now. Thanks Cheers, Derek *** End of the template - remove these lines *** -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 May 9 23:49 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2044664 Apr 17 12:40 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 06:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT200 [GeForce GTX 260] [10de:05e2] (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 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-15) ) #1 SMP Debian 3.2.41-2 Xorg X server log files on system: -- -rw-r--r-- 1 root root 33936 May 10 00:08 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 210.149] X.Org X Server 1.12.4 Release Date: 2012-08-27 [ 210.152] X Protocol Version 11, Revision 0 [ 210.153] Build Operating System: Linux 3.2.0-4-amd64 x86_64 Debian [ 210.153] Current Operating System: Linux schwinn-desktop 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 [ 210.153] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=ec5ab5b9-29c4-4092-87b9-9eb2c12f1af4 ro single [ 210.155] Build Date: 17 April 2013 10:22:47AM [ 210.156] xorg-server 2:1.12.4-6 (Julien Cristau jcris...@debian.org) [ 210.157] Current version of pixman: 0.26.0 [ 210.159]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 210.159] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 210.163] (==) Log file: /var/log/Xorg.0.log, Time: Fri May 10 00:07:52 2013 [ 210.201] (==) Using system config directory /usr/share/X11/xorg.conf.d [ 210.202] (==) No Layout section. Using the first Screen section. [ 210.202] (==) No screen section available. Using defaults. [ 210.202] (**) |--Screen Default Screen Section (0) [ 210.202] (**) | |--Monitor default monitor [ 210.202] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [ 210.202] (==) Automatically adding devices [ 210.202] (==) Automatically enabling devices [ 210.202] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [ 210.203]Entry deleted from font path. [ 210.203] (WW) The directory /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType does not exist. [ 210.203]Entry deleted from font path. [ 210.203] (==) 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 [ 210.203] (==) ModulePath set to /usr/lib/xorg/modules [ 210.203] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 210.203] (II) Loader magic: 0x7fe515476ae0 [ 210.203] (II) Module ABI versions: [ 210.203]X.Org ANSI C Emulation: 0.4 [ 210.203]X.Org Video Driver: 12.1 [ 210.203]X.Org XInput driver : 16.0 [ 210.203]X.Org Server Extension : 6.0 [ 210.204] (--) PCI:*(0:6:0:0) 10de:05e2:19da:2120 rev 161, Mem @ 0xfa00/16777216, 0xd000/268435456, 0xf800/33554432, I/O @ 0x9f00/128, BIOS @ 0x/524288 [ 210.205] (WW) Open ACPI
Bug#687058: xserver-xorg-video-radeon: Gnome 3 fonts rendering problem (also appeared at fonts in Blender Software)
Just re-installed Debian Testing, and the problem still exists. The problem appears only on fonts that are rendered for Gnome Menu, as shown in the pic attached on first message. The lines on the fonts change as i change the font size and hinting via Advanced Settings program. -- 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/7a0a86808e9cd8b75fcb421a36edf...@ceid.upatras.gr
Processed: Re: Bug#703291: [xserver-xorg-video-nouveau] Dual display problem: Using xrandr to setup dual displays causes X to hang
Processing control commands: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=63048 Bug #703291 [xserver-xorg-video-nouveau] [xserver-xorg-video-nouveau] Dual display problem: Using xrandr to setup dual displays causes X to hang Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=63048'. reassign -1 src:linux Bug #703291 [xserver-xorg-video-nouveau] [xserver-xorg-video-nouveau] Dual display problem: Using xrandr to setup dual displays causes X to hang Bug reassigned from package 'xserver-xorg-video-nouveau' to 'src:linux'. No longer marked as found in versions xserver-xorg-video-nouveau/1:1.0.1-5. Ignoring request to alter fixed versions of bug #703291 to the same values previously set found -1 3.2.39-1 Bug #703291 [src:linux] [xserver-xorg-video-nouveau] Dual display problem: Using xrandr to setup dual displays causes X to hang Marked as found in versions linux/3.2.39-1. affects -1 xserver-xorg-video-nouveau Bug #703291 [src:linux] [xserver-xorg-video-nouveau] Dual display problem: Using xrandr to setup dual displays causes X to hang Added indication that 703291 affects xserver-xorg-video-nouveau -- 703291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703291 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b703291.136500621719639.transcr...@bugs.debian.org
Bug#703291: [xserver-xorg-video-nouveau] Dual display problem: Using xrandr to setup dual displays causes X to hang
Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=63048 Control: reassign -1 src:linux Control: found -1 3.2.39-1 Control: affects -1 xserver-xorg-video-nouveau On 2013-04-03 01:06 +0200, Guy Heatley wrote: I have raised this issue as a bug on freedesktop.org The bug number is 63048 https://bugs.freedesktop.org/show_bug.cgi?id=63048 Thanks, marking as forwarded accordingly (and reassigning to the kernel). Cheers, Sven -- 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/871uarziq2@turtle.gmx.de
Bug#703291: [xserver-xorg-video-nouveau] Dual display problem: Using xrandr to setup dual displays causes X to hang
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The 3.8 kernel doesn't fix this. I can't get any output on DVI-I-1 using xrandr: % xrandr Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192 VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 380mm x 300mm 1280x1024 60.0*+ 75.0 1152x864 75.0 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 640x48072.8 75.0 60.0 720x40070.1 DVI-I-1 disconnected (normal left inverted right x axis y axis) 1280x1024_60.00 59.9 But, there are no system hangs caused by the use of xrandr - it just fails to work: % xrandr --output DVI-I-1 --mode 1280x1024_60.00 --left-of VGA-1 --dpi 96 xrandr: Configure crtc 1 failed I shall file a bug report at freedesktop.org Cheers! - -- Guy On 19/03/13 19:39, Sven Joachim wrote: On 2013-03-18 22:44 +0100, Guy Heatley wrote: Sven - I can confirm that your downgrading suggestion fixes this problem. On 18/03/13 17:03, Sven Joachim wrote: Kernel folks, this appears to be a regression resulting from the DRM 3.4 backport. Can you confirm that downgrading linux-image-3.2.0-4-amd64 to 3.2.35-2 (available on snapshots.debian.org[1]) fixes the problem? Yes, this fixes it. Could you please try a 3.8 kernel from experimental (requires initramfs-tools from experimental as well)? If the problem persists, file a bug on https://bugs.freedesktop.org/. Choose product xorg, component Driver/nouveau, and let us know the bug number. Cheers, Sven -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlFbXnMACgkQcVtC8LX0UebCuQCg2Vrq+3oiML+fY01jE77xnAzB lCwAnAlAXKmEnn41RwpNgp0gK7AzrRP1 =p8HU -END PGP SIGNATURE- -- 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/515b5e89@member.fsf.org
Bug#703291: [xserver-xorg-video-nouveau] Dual display problem: Using xrandr to setup dual displays causes X to hang
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have raised this issue as a bug on freedesktop.org The bug number is 63048 https://bugs.freedesktop.org/show_bug.cgi?id=63048 Cheers! - -- Guy On 19/03/13 19:39, Sven Joachim wrote: On 2013-03-18 22:44 +0100, Guy Heatley wrote: Sven - I can confirm that your downgrading suggestion fixes this problem. On 18/03/13 17:03, Sven Joachim wrote: Kernel folks, this appears to be a regression resulting from the DRM 3.4 backport. Can you confirm that downgrading linux-image-3.2.0-4-amd64 to 3.2.35-2 (available on snapshots.debian.org[1]) fixes the problem? Yes, this fixes it. Could you please try a 3.8 kernel from experimental (requires initramfs-tools from experimental as well)? If the problem persists, file a bug on https://bugs.freedesktop.org/. Choose product xorg, component Driver/nouveau, and let us know the bug number. Cheers, Sven -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlFbZJEACgkQcVtC8LX0UeYa9gCg0wd6u9Iwydj04MP9mZgSNYUt BUYAoLIL/VUM9YU6/0UmN95jifsdIxuj =0x5Y -END PGP SIGNATURE- -- 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/515b6491.1050...@member.fsf.org
Bug#653327: same problem with cairo-dock
Dear Maintainers, I ran into a similar problem on a fresh Wheezy install when trying to use Cairo-Dock. The error message I got from Xsession is: Xsession: X session started for dani at 2013. márc. 23., szombat, 13.43.47 CET Xsession: unable to launch gnome-session --session=cairo-dock X session --- gnome-session --session=cairo-dock not found; falling back to default session. My installed version is: x11-common: Installed: 1:7.7+2 Candidate: 1:7.7+2 The patch available at http://anonscm.debian.org/gitweb/?p=pkg-xorg/debian/xorg.git;a=blobdiff;f=debian/local/Xsession.d/20x11-common_process-args;h=33696ad9988cf7a5d5683bb027ae40a85cf53a15;hp=53e7a7b294f8c2a3b63dd0320b6d79e6225c683b;hb=75c2a9cfacafbd46c433b44dd672985433032f99;hpb=50706e3079f37799a3e6a3a06d711c764703960c fixes the problem for me. Best Regards, Dániel Kondor -- 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/cadozelropgqefgerh0h0njpi53uxykjeybshmzkvci3ryee...@mail.gmail.com
Bug#703291: [xserver-xorg-video-nouveau] Dual display problem: Using xrandr to setup dual displays causes X to hang
On 2013-03-18 22:44 +0100, Guy Heatley wrote: Sven - I can confirm that your downgrading suggestion fixes this problem. On 18/03/13 17:03, Sven Joachim wrote: Kernel folks, this appears to be a regression resulting from the DRM 3.4 backport. Can you confirm that downgrading linux-image-3.2.0-4-amd64 to 3.2.35-2 (available on snapshots.debian.org[1]) fixes the problem? Yes, this fixes it. Could you please try a 3.8 kernel from experimental (requires initramfs-tools from experimental as well)? If the problem persists, file a bug on https://bugs.freedesktop.org/. Choose product xorg, component Driver/nouveau, and let us know the bug number. Cheers, Sven -- 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/874ng7ji0y@turtle.gmx.de
Bug#703291: [xserver-xorg-video-nouveau] Dual display problem: Using xrandr to setup dual displays causes X to hang
Kernel folks, this appears to be a regression resulting from the DRM 3.4 backport. On 2013-03-18 02:05 +0100, Guy Heatley wrote: Package: xserver-xorg-video-nouveau Version: 1:1.0.1-5 Severity: important --- Please enter the report below this line. --- Since upgrading my (Wheezy) desktop machine a couple of days ago with APT, my dual-display setup has stopped working. I assume that the last upgrade was less than half a year ago? If so, it's almost certainly a problem with the latest kernel. I run an xrandr script as I login to set up my twin displays: # 1280x1024 59.89 Hz (CVT 1.31M4) hsync: 63.67 kHz; pclk: 109.00 MHz xrandr --newmode 1280x1024_60.00 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync xrandr --addmode DVI-I-1 1280x1024_60.00 xrandr --output VGA-1 --primary --gamma 1.2:1.2:1.05 --brightness 0.95 --dpi 96 xrandr --output DVI-I-1 --mode 1280x1024_60.00 --right-of VGA-1 --gamma 0.75:0.9:0.9 --brightness 0.9 --dpi 96 Running this script in Gnome or XFCE now causes X to immediately hang, and requires I log in to the machine via SSH and reboot it. In fluxbox or KDE the script simply doesn't work (but no hang ... well fluxbox hangs X when I log out) Concerning my secondary display (the one called DVI-I-1 in the script): the graphics card has never been able to poll any monitor attached for any EDID information (I suspect the DVI-A to SVGA adapter I use is not fully wired?). Anyway, I boot with the drm_kms_helper.poll=0 in my grub.cfg to prevent constant futile polling. I don't know if this has any bearing? Remove that parameter to find out. Thanks for any advice. Can you confirm that downgrading linux-image-3.2.0-4-amd64 to 3.2.35-2 (available on snapshots.debian.org[1]) fixes the problem? Cheers, Sven 1. http://snapshot.debian.org/package/linux/3.2.35-2/#linux-image-3.2.0-4-amd64_3.2.35-2 -- 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/8738vsej3t@turtle.gmx.de
Bug#703291: [xserver-xorg-video-nouveau] Dual display problem: Using xrandr to setup dual displays causes X to hang
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sven - I can confirm that your downgrading suggestion fixes this problem. On 18/03/13 17:03, Sven Joachim wrote: Kernel folks, this appears to be a regression resulting from the DRM 3.4 backport. On 2013-03-18 02:05 +0100, Guy Heatley wrote: Package: xserver-xorg-video-nouveau Version: 1:1.0.1-5 Severity: important --- Please enter the report below this line. --- Since upgrading my (Wheezy) desktop machine a couple of days ago with APT, my dual-display setup has stopped working. I assume that the last upgrade was less than half a year ago? If so, it's almost certainly a problem with the latest kernel. Yes. Anyway, I boot with the drm_kms_helper.poll=0 in my grub.cfg to prevent constant futile polling. I don't know if this has any bearing? Remove that parameter to find out. Yep its a red herring: it just makes the 2nd screen flicker every couple of seconds, if I remove it. Can you confirm that downgrading linux-image-3.2.0-4-amd64 to 3.2.35-2 (available on snapshots.debian.org[1]) fixes the problem? Yes, this fixes it. - -- Guy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlFHipQACgkQcVtC8LX0UebhmQCg4ZjNG89yq+9BpXM2f1bETnjI xJIAnj0O7co8fmhr0EpsdQG37isBXLf/ =VN6S -END PGP SIGNATURE- -- 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/51478aa4.2040...@member.fsf.org
Bug#673923: KVM-Switch-Problem
Same Problem here. (Being despaired since I need my notebook for many presentations.) lspci output: 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device 17df Flags: bus master, fast devsel, latency 0, IRQ 48 Memory at d400 (64-bit, non-prefetchable) [size=4M] Memory at c000 (64-bit, prefetchable) [size=256M] I/O ports at 4000 [size=64] Expansion ROM at unassigned [disabled] Capabilities: access denied Kernel driver in use: i915 Regards, Bernhard signature.asc Description: This is a digitally signed message part.
Bug#698324: gpu hang problem exists only since 2.20
found 698324 2:2.19.0-6 notfound 698324 2:2.19.0-6 thx i downgraded to xserver-xorg-video-intel:amd64 2:2.19.0-6, and i haven't run into that condition for almost four days. with 2.20, the issues occurred roughly every 24-48 hours for four times in succession, so i'm confident enough to state this here as a working assumption. signature.asc Description: Digital signature
Processed (with 5 errors): gpu hang problem exists only since 2.20
Processing commands for cont...@bugs.debian.org: found 698324 2:2.19.0-6 Bug #698324 [xserver-xorg-video-intel] recent gpu hangups on 965GM Marked as found in versions xserver-xorg-video-intel/2:2.19.0-6. notfound 698324 2:2.19.0-6 Bug #698324 [xserver-xorg-video-intel] recent gpu hangups on 965GM No longer marked as found in versions xserver-xorg-video-intel/2:2.19.0-6. thx Unknown command or malformed arguments to command. i downgraded to xserver-xorg-video-intel:amd64 2:2.19.0-6, and i haven't Unknown command or malformed arguments to command. run into that condition for almost four days. with 2.20, the issues Unknown command or malformed arguments to command. occurred roughly every 24-48 hours for four times in succession, so i'm Unknown command or malformed arguments to command. confident enough to state this here as a working assumption. Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. -- 698324: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698324 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.135915922212835.transcr...@bugs.debian.org
Bug#698324: gpu hang problem exists only since 2.20
found 698324 2:2.19.0-6 found 698324 2:2.19.0-6 thank you On Sat, Jan 26, 2013 at 01:04:43AM +0100, chrysn wrote: found 698324 2:2.19.0-6 notfound 698324 2:2.19.0-6 thx i downgraded to xserver-xorg-video-intel:amd64 2:2.19.0-6, and i haven't run into that condition for almost four days. with 2.20, the issues occurred roughly every 24-48 hours for four times in succession, so i'm confident enough to state this here as a working assumption. as things happen, the problem bit again, while running 2.19. whether it happens less frequently or i was just lucky the last days remains to be seen. -- 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/20130126014328.ga...@hephaistos.amsuess.com
Processed: Re: gpu hang problem exists only since 2.20
Processing commands for cont...@bugs.debian.org: found 698324 2:2.19.0-6 Bug #698324 [xserver-xorg-video-intel] recent gpu hangups on 965GM Marked as found in versions xserver-xorg-video-intel/2:2.19.0-6. found 698324 2:2.19.0-6 Bug #698324 [xserver-xorg-video-intel] recent gpu hangups on 965GM Ignoring request to alter found versions of bug #698324 to the same values previously set thank you Stopping processing here. Please contact me if you need assistance. -- 698324: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698324 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.135916461318506.transcr...@bugs.debian.org
Bug#695496: mesa: Torchlight crashes because of mesa texture problem
Package: mesa Version: 8.0.5-3 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** The game Torchlight for Linux crashes when entering certain location. It seems the problem is in mesa package and its checks for mipmap dimensions (see http://forums.runicgames.com/viewtopic.php?f=24t=34893sid=c4c3efa2a55860e0ced3359f27753d0bstart=20). The fix for mesa should be in theese links: http://lists.freedesktop.org/archives/mesa-dev/2012-October/028210.html http://lists.freedesktop.org/archives/mesa-dev/2012-October/028211.html or in the bug filled on freedestop.org: https://bugs.freedesktop.org/show_bug.cgi?id=55445 but they are apparently for diferent version of mesa then contain in current Debian unstable. *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20121208205737.12970.34906.report...@shiva.kaspar.in