Bug#720329: xserver-xorg-video-radeon: Screen keeping black at start but for the cursor

[Michel Dänzer]

On Mit, 2014-02-26 at 23:10 +0100, Samuel Hym wrote:
> 
> When starting the kernel with radeon.modeset=1 video=radeonfb:off, I
> got a normal screen for login. But the interface stopped responding
> after a few seconds.
> The first time I didn't succeed in logging in, it crashed while I was
> typing my password.
> The second one, after a violent shutdown and booting again, I logged
> in but it crashed before launching an application.

Does adding radeon.agpmode=1 or radeon.agpmode=-1 to the kernel command
line avoid the crashes?


-- 
Earthling Michel Dänzer|  http://www.amd.com
Libre software enthusiast  |Mesa and X developer


-- 
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/1393483627.6729.37.camel@thor.local

Bug#231041: marked as done (xterm: want scrollbar enabled by default)

[Debian Bug Tracking System]

Your message dated Wed, 26 Feb 2014 17:36:02 -0500
with message-id <20140226223602.gb3...@aerie.jexium-island.net>
and subject line re: 231041
has caused the Debian Bug report #231041,
regarding xterm: want scrollbar enabled by default
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.)


-- 
231041: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=231041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xterm
Version: 4.2.1-5jds2
Severity: wishlist

The default settings for xterm in /usr/lib/menu/xterm have no options
specified by default.  The -sb option places a 50 line scroll bar on the
left side of the terminal thus making it far more useful.

-- System Information:
Debian Release: 3.0
Architecture: i386
Kernel: Linux averroes 2.4.22-ac4 #5 Thu Dec 25 21:30:05 CST 2003 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages xterm depends on:
ii  debconf 1.2.34.99.jones1 Debian configuration
management sy
ii  libc6   2.3.2.ds1-10 GNU C Library: Shared
libraries an
ii  libfreetype62.1.7-1  FreeType 2 font engine,
shared lib
ii  libncurses5 5.3.20030719-4   Shared libraries for terminal
hand
ii  libxaw7 4.2.1-5jds2  X Athena widget set library
ii  xlibs   4.2.1-5jds2  X Window System client
libraries

-- no debconf information

--- End Message ---
--- Begin Message ---
no further comments were made; as noted this was not a bug but rather a
request to change the default appearance of xterm.

(scrollbars can be customized per-user as well as turned on/off via menu)

-- 
Thomas E. Dickey 
http://invisible-island.net
ftp://invisible-island.net


signature.asc
Description: Digital signature
--- End Message ---

Bug#739691: Upgrade to Xserver 1.15 broke kwin and others: primus also affected

[Ralf Jung]

primus is also affected by this problem:


Kind regards
Ralf


-- 
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/530e6a3a.5000...@ralfj.de

Processed: re: 737692

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 737692 fixed-upstream
Bug #737692 [xterm] xterm: incorrect pathname in 
/usr/share/doc/xterm/xterm.faq.gz
Added tag(s) fixed-upstream.
> --
Stopping processing here.

Please contact me if you need assistance.
-- 
737692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737692
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.c.139345398212748.transcr...@bugs.debian.org

Bug#740128: nouveau: libgl looks for nouveau_dri.so on incorrect path with multiarch

[Sven Joachim]

On 2014-02-26 19:34 +0100, Alejandro Carrazzoni wrote:

> Sorry, my bad, I got the package name mixed up. The output of 'dpkg -S
> libGL.so.1' is:
>
> libgl1-mesa-glx:i386: /usr/lib/i386-linux-gnu/libGL.so.1
> libgl1-mesa-glx:i386: /usr/lib/i386-linux-gnu/libGL.so.1.2.0
> libgl1-mesa-glx:amd64: /usr/lib/x86_64-linux-gnu/libGL.so.1
> libgl1-mesa-glx:amd64: /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0

This is how it's supposed to be.

> And the output of 'ldd /usr/bin/glxinfo' is:
> [...]
> libGL.so.1 => /usr/lib/libGL.so.1 (0x7f0f2fb89000)

This is the problem, you need to get rid of that file which does not
belong to any Debian package.

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/87ios1ya8i@turtle.gmx.de

Bug#740128: nouveau: libgl looks for nouveau_dri.so on incorrect path with multiarch

[Alejandro Carrazzoni]

Sorry, my bad, I got the package name mixed up. The output of 'dpkg -S
libGL.so.1' is:

libgl1-mesa-glx:i386: /usr/lib/i386-linux-gnu/libGL.so.1
libgl1-mesa-glx:i386: /usr/lib/i386-linux-gnu/libGL.so.1.2.0
libgl1-mesa-glx:amd64: /usr/lib/x86_64-linux-gnu/libGL.so.1
libgl1-mesa-glx:amd64: /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0

And the output of 'ldd /usr/bin/glxinfo' is:

linux-vdso.so.1 (0x7fff9a3fe000)
libGLEW.so.1.10 => /usr/lib/x86_64-linux-gnu/libGLEW.so.1.10
(0x7f0f30079000)
libGLU.so.1 => /usr/lib/x86_64-linux-gnu/libGLU.so.1
(0x7f0f2fe0b000)
libGL.so.1 => /usr/lib/libGL.so.1 (0x7f0f2fb89000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f0f2f886000)
libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6
(0x7f0f2f54b000)
libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6
(0x7f0f2f338000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f0f2ef8f000)
libXmu.so.6 => /usr/lib/x86_64-linux-gnu/libXmu.so.6
(0x7f0f2ed75000)
libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x7f0f2eb64000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x7f0f2e86)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x7f0f2e64a000)
libXxf86vm.so.1 => /usr/lib/x86_64-linux-gnu/libXxf86vm.so.1
(0x7f0f2e443000)
libXdamage.so.1 => /usr/lib/x86_64-linux-gnu/libXdamage.so.1
(0x7f0f2e24)
libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3
(0x7f0f2e03a000)
libdrm.so.2 => /usr/lib/x86_64-linux-gnu/libdrm.so.2
(0x7f0f2de2d000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f0f2dc1)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f0f2da0c000)
libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1
(0x7f0f2d7ec000)
/lib64/ld-linux-x86-64.so.2 (0x7f0f30332000)
libXt.so.6 => /usr/lib/x86_64-linux-gnu/libXt.so.6 (0x7f0f2d586000)
libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6
(0x7f0f2d381000)
libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6
(0x7f0f2d17c000)
libSM.so.6 => /usr/lib/x86_64-linux-gnu/libSM.so.6 (0x7f0f2cf75000)
libICE.so.6 => /usr/lib/x86_64-linux-gnu/libICE.so.6
(0x7f0f2cd59000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f0f2cb54000)



2014-02-26 6:14 GMT-03:00 Julien Cristau :

> On Tue, Feb 25, 2014 at 22:58:28 -0300, Alejandro Carrazzoni wrote:
>
> > Package: libgl1-mesa-dri
>
> This is not the package containing libGL.
>
> > Version: 9.2.2-1
> > Severity: important
> > File: nouveau
> >
> > When using nouveau I didn't have 3d acceleration, running glxinfo gave
> the
> > following error:
> >
> > name of display: :0.0
> > libGL: OpenDriver: trying /usr/lib/dri/tls/nouveau_dri.so
> > libGL: OpenDriver: trying /usr/lib/dri/nouveau_dri.so
> > libGL error: dlopen /usr/lib/dri/nouveau_dri.so failed
> > (/usr/lib/dri/nouveau_dri.so: cannot open shared object file: No such
> file or
> > directory)
> > libGL error: unable to load driver: nouveau_dri.so
> > libGL error: driver pointer missing
> > libGL: OpenDriver: trying /usr/lib/dri/tls/swrast_dri.so
> > libGL: OpenDriver: trying /usr/lib/dri/swrast_dri.so
> > libGL error: dlopen /usr/lib/dri/swrast_dri.so failed
> > (/usr/lib/dri/swrast_dri.so: cannot open shared object file: No such
> file or
> > directory)
> > libGL error: unable to load driver: swrast_dri.so
> > libGL error: reverting to indirect rendering
> > display: :0  screen: 0
> > direct rendering: No (If you want to find out why, try setting
> > LIBGL_DEBUG=verbose)
> >
> > Because of multiarch nouveau_dri.so is currently in
> /usr/lib/i386-linux-gnu/dri
> > and /usr/lib/x86_64-linux-gnu/dri but libgl isn't looking for them. I
> had to
> > change the LIBGL_DRIVERS_PATH variable to get 3d accel to work.
> >
> Where's your libGL, and which package does it come from?  (provide the
> output of 'ldd /usr/bin/glxinfo', and 'dpkg -S libGL.so.1')
>
> Cheers,
> Julien
>

Bug#740168: marked as done (xbacklight uses wrong control)

[Debian Bug Tracking System]

Your message dated Wed, 26 Feb 2014 16:45:45 +0100
with message-id <20140226154545.gs17...@betterave.cristau.org>
and subject line Re: Bug#740168: xbacklight uses wrong control
has caused the Debian Bug report #740168,
regarding xbacklight uses wrong control
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.)


-- 
740168: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xbacklight
Version: 1.1.2-1
Severity: normal

Dear Maintainer,

on my Lenovo T410 with an Intel graphics card, xbacklight  modifies the values
in /sys/class/backlight/acpi_video0 instead of
/sys/class/backlight/intel_backlight . The latter works just fine, whereas
changing values in the former has no visible effect.

Since my KDE session seems to use xbacklight upon login to restore the old
backlight, this results in a totally black screen, because the intel value
seems to be initialized to 0. Pressing the brightness up and down keys has no
effect either, so the only way to recover from this is to change the values in
/sys/class/backlight/intel_backlight by hand.



-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (600, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xbacklight depends on:
ii  libc6   2.18-3
ii  libx11-62:1.6.2-1
ii  libxrandr2  2:1.4.2-1

xbacklight recommends no packages.

xbacklight suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, Feb 26, 2014 at 15:31:31 +0100, Philipp Hagemeister wrote:

> Package: xbacklight
> Version: 1.1.2-1
> Severity: normal
> 
> Dear Maintainer,
> 
> on my Lenovo T410 with an Intel graphics card, xbacklight  modifies the values
> in /sys/class/backlight/acpi_video0 instead of
> /sys/class/backlight/intel_backlight . The latter works just fine, whereas
> changing values in the former has no visible effect.
> 
> Since my KDE session seems to use xbacklight upon login to restore the old
> backlight, this results in a totally black screen, because the intel value
> seems to be initialized to 0. Pressing the brightness up and down keys has no
> effect either, so the only way to recover from this is to change the values in
> /sys/class/backlight/intel_backlight by hand.
> 
That's not a bug in xbacklight, it's either a bug in your kernel or X
driver.

Cheers,
Julien


signature.asc
Description: Digital signature
--- End Message ---

Bug#740168: xbacklight uses wrong control

[Philipp Hagemeister]

Package: xbacklight
Version: 1.1.2-1
Severity: normal

Dear Maintainer,

on my Lenovo T410 with an Intel graphics card, xbacklight  modifies the values
in /sys/class/backlight/acpi_video0 instead of
/sys/class/backlight/intel_backlight . The latter works just fine, whereas
changing values in the former has no visible effect.

Since my KDE session seems to use xbacklight upon login to restore the old
backlight, this results in a totally black screen, because the intel value
seems to be initialized to 0. Pressing the brightness up and down keys has no
effect either, so the only way to recover from this is to change the values in
/sys/class/backlight/intel_backlight by hand.



-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (600, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xbacklight depends on:
ii  libc6   2.18-3
ii  libx11-62:1.6.2-1
ii  libxrandr2  2:1.4.2-1

xbacklight recommends no packages.

xbacklight suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20140226143131.26008.57569.report...@t4.home.phihag.de

Processed: tagging 740128

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 740128 + moreinfo
Bug #740128 [libgl1-mesa-dri] nouveau: libgl looks for nouveau_dri.so on 
incorrect path with multiarch
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
740128: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740128
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.c.139341085915262.transcr...@bugs.debian.org

Bug#740128: nouveau: libgl looks for nouveau_dri.so on incorrect path with multiarch

[Julien Cristau]

On Tue, Feb 25, 2014 at 22:58:28 -0300, Alejandro Carrazzoni wrote:

> Package: libgl1-mesa-dri

This is not the package containing libGL.

> Version: 9.2.2-1
> Severity: important
> File: nouveau
> 
> When using nouveau I didn't have 3d acceleration, running glxinfo gave the
> following error:
> 
> name of display: :0.0
> libGL: OpenDriver: trying /usr/lib/dri/tls/nouveau_dri.so
> libGL: OpenDriver: trying /usr/lib/dri/nouveau_dri.so
> libGL error: dlopen /usr/lib/dri/nouveau_dri.so failed
> (/usr/lib/dri/nouveau_dri.so: cannot open shared object file: No such file or
> directory)
> libGL error: unable to load driver: nouveau_dri.so
> libGL error: driver pointer missing
> libGL: OpenDriver: trying /usr/lib/dri/tls/swrast_dri.so
> libGL: OpenDriver: trying /usr/lib/dri/swrast_dri.so
> libGL error: dlopen /usr/lib/dri/swrast_dri.so failed
> (/usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or
> directory)
> libGL error: unable to load driver: swrast_dri.so
> libGL error: reverting to indirect rendering
> display: :0  screen: 0
> direct rendering: No (If you want to find out why, try setting
> LIBGL_DEBUG=verbose)
> 
> Because of multiarch nouveau_dri.so is currently in 
> /usr/lib/i386-linux-gnu/dri
> and /usr/lib/x86_64-linux-gnu/dri but libgl isn't looking for them. I had to
> change the LIBGL_DRIVERS_PATH variable to get 3d accel to work.
> 
Where's your libGL, and which package does it come from?  (provide the
output of 'ldd /usr/bin/glxinfo', and 'dpkg -S libGL.so.1')

Cheers,
Julien


signature.asc
Description: Digital signature