[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#579185: x11-xserver-utils: weird xkeystone executable



Package: x11-xserver-utils
Version: 7.6+3
Followup-For: Bug #579185

Dear Maintainer,

I managed to get xkeystone to work by commenting out a couple lines.

--- xkeystone~  2011-07-02 11:25:46.000000000 -0700
+++ xkeystone   2012-04-03 07:52:18.000000000 -0700
@@ -496,8 +496,8 @@
           text = (string[3]) { "no solution", "" ... };
           m_available = false;
       }
-       for (int i = 0; i < 3; i++)
-           Label::relabel (label[i], text[i]);
+/*     for (int i = 0; i < 3; i++)
+           Label::relabel (label[i], text[i]);*/
    }
    &quad_t    quad = Quad::new (&nichrome, callback);

With this patch, there are a few labels on the screen that read "Matrix"
instead of whatever information they are supposed to show. By default,
xkeystone shows only a white screen and outputs these error messages for me:

~$ xkeystone
Unhandled exception deadlock (&{sem = semaphore 1 (0), owner = owner = %86},
%86)
/usr/share/nickle/mutex.5c:49:     raise deadlock (m, Thread::current ());
   acquire (<composite>)
/usr/share/nickle/nichrome.5c:189:     twixt (Mutex::acquire
(widget.nichrome.drawing); Mutex::release (widget.nichrome.drawing))
   resize (<composite>)
/usr/bin/xkeystone:500:     Label::relabel (label[i], text[i]);
   callback (<composite>)
/usr/share/nickle/nichrome-box.5c:303:     item.configure (&item.contained,
child_layout, child_geometry);
   configure (<composite>, <composite>, <composite>)
/usr/share/nickle/nichrome.5c:414:     nichrome.configure (&nichrome);
   draw (<composite>)
/usr/share/nickle/nichrome.5c:542:     draw (&nichrome);
   main_loop (<composite>)
/usr/bin/xkeystone:556:     main ();
^CUnhandled exception signal (2)
/usr/share/nickle/nichrome.5c:530:     Semaphore::wait (read_event);
   event_reader ()
/usr/share/nickle/nichrome.5c:534:     event_reader ();
   main_loop (<composite>)
/usr/bin/xkeystone:556:     main ();
~$

With my patch, those problems go away, but of course it is not an
optimal solution. Best would be to catch the mutex exception and
handle it properly.


-- System Information:
Debian Release: wheezy/sid
 APT prefers testing
 APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages x11-xserver-utils depends on:
ii  cpp          4:4.6.2-4
ii  libc6        2.13-26
ii  libice6      2:1.0.7-2
ii  libx11-6     2:1.4.4-4
ii  libxau6      1:1.0.6-4
ii  libxaw7      2:1.0.9-3
ii  libxcursor1  1:1.1.12-1
ii  libxext6     2:1.3.0-3
ii  libxi6       2:1.4.5-1
ii  libxmu6      2:1.1.0-3
ii  libxmuu1     2:1.1.0-3
ii  libxrandr2   2:1.3.2-2
ii  libxrender1  1:0.9.6-2
ii  libxt6       1:1.1.1-2
ii  libxxf86vm1  1:1.1.1-2

x11-xserver-utils recommends no packages.

Versions of packages x11-xserver-utils suggests:
ii  cairo-5c        1.4
ii  nickle          2.74-1
ii  xorg-docs-core  1:1.6-1

-- no debconf information



Reply to: