On Sun, 11 Nov 2012 21:46:58 +0100, Julien Cristau wrote:
> > Why would it work with the 32bit "foreign" libraries but not with the
> > "native" 64bit ones?
> Because this is not a '32bit' vs '64bit' test, it's a 'direct' vs
> 'indirect' test. No surprise that they're different. (Your 64bit libG
On Sat, 21 Jul 2007 11:06:36 +0200, Brice Goglin wrote:
> Does it help if you:
> * get a ModeLine for your desired resolution/refresh rate with something
> like
> gtf 1024 768 78
> and add it to your xorg.conf Monitor section
> * add a PreferredMode line to your Monitor section
> Option
On Wed, 10 Jun 2009 22:58:47 +0200, Julien Cristau wrote:
> > > > on $server:
> > > > DISPLAY=$desktop:0 ssh -X $client sensible-browser "$URL"
> > > Wow, that's quite a running in circles. Why don't you just use
> > > ssh client DISPLAY=:0 sensible-browser "$URL"
> > /me coughs in embarrassment
>
On Sun, 22 Mar 2009 20:20:39 +0100, Jan De Luyck wrote:
> I can confirm that the patch supplied by Thomas Dickey makes xterm beep
> again. Yay ;)
I just tried the new 243 upstream release from
ftp://invisible-island.net/xterm/xterm-243.tgz
and I can confirm that the audible bell is back.
Cheers
Package: xauth
Version: 1:1.0.3-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Since quite some time I've used the following setup (with two machines
in my LAN for getting $URL from irssi on $server to $desktop):
on $desktop:
/usr/bin/xauth extract - $desktop:0.0 | ssh $server
On Fri, 17 Apr 2009 11:20:06 +0200, Bernhard R. Link wrote:
> > on $server:
> > DISPLAY=$desktop:0 ssh -X $client sensible-browser "$URL"
> Wow, that's quite a running in circles. Why don't you just use
> ssh client DISPLAY=:0 sensible-browser "$URL"
/me coughs in embarrassment
Right, that's ind
On Sun, 11 Jul 2010 10:21:42 +0100, Julien Cristau wrote:
> > (EE) Error compiling keymap (server-0)
> > (EE) XKB: Couldn't compile keymap
> > XKB: Failed to compile keymap
> > Keyboard initialization failed. This could be a missing or incorrect setup
> > of xkeyboard-config.
> Please attach your
On Sat, 09 Jan 2010 17:50:09 -0500, Thomas Dickey wrote:
> >Right, configure doesn't use XkbBell in the debian build because the
> >package doesn't build-depend on libxkbfile-dev (which provides
> >). I'll try to remember to fix that.
> thanks (barring bug-fixes, I don't have any plans to change
Control: tag -1 + moreinfo
Control: severity -1 important
On Mon, 04 Jun 2018 09:54:40 +0200, Emilio Pozuelo Monfort wrote:
> > 2018-05-30 07:53:07 status installed xserver-xorg-input-all:amd64 1:7.7+19
> > 2018-05-30 07:53:08 remove xserver-xorg-input-all:amd64 1:7.7+19
> > 2018-05-30 07:53:08
Control: severity -1 important
Control: tag -1 + moreinfo
I looked through this bug during the Bern Bug Squashing Party, and
although I'm not in the xorg team, my impression is that the bug is
not actionable in the current state.
The individual messages hint at problems that might be related to th
On Mon, 01 Aug 2022 14:57:59 +0200, Hermann Meyer wrote:
> With libx11-6 1.8.1 I get:
>
> |glxinfo name of display: :0 glxinfo: ../nptl/pthread_mutex_lock.c:424:
> __pthread_mutex_lock_full: Assertion `e != ESRCH || !robust' failed.
> Abgebrochen|
Same here.
With xscreensaver I also see SIGABR
On Wed, 03 Aug 2022 20:06:28 +0200, Richard B. Kreckel wrote:
> So, should Debian build with --disable-thread-safety-constructor, at
> least for a while?
I can confirm that the following trivial change avoids the issues I'm
seeing in glxinfo and xscreensaver-gl-visual:
#v+
--- libx11-1.8.1/debia
12 matches
Mail list logo
