Bug#708958: x11-common: X11 crashes after quitting Stellarium

[Guenther]

Package: x11-common
Version: 1:7.7+3~deb7u1
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
  Using Stellarium.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 Clicking on the exit button.

   * What was the outcome of this action?
   Stellarium is finished and some seconds later X11 crashes and will be
restarted.

   * What outcome did you expect instead?
   No X11 restart.



-- System Information:
Debian Release: 7.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (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 x11-common depends on:
ii  debconf [debconf-2.0]  1.5.49
ii  lsb-base   4.1+Debian8

x11-common recommends no packages.

x11-common suggests no packages.

-- debconf information:

Add. Information
VGA compatible controller: NVIDIA Corporation G86 [GeForce 8400M G] (rev A1)
NVIDIA Driver 304.88-1+debu7u
/etc/gdm3/Xsession: Beginning session setup...
localuser:inet being added to access control list
openConnection: connect: Datei oder Verzeichnis nicht gefunden
cannot connect to brltty at :0
User id(1000) name = inet
euid = root
dir '/var/spool/turboprint/inet' already existing
gnome-session[6954]: EggSMClient-WARNING: Desktop file 
'/home/inet/.config/autostart/turboprint-monitor.desktop' has malformed Icon 
key 'turboprint-applet.png'(should not include extension)
GNOME_KEYRING_CONTROL=/home/inet/.cache/keyring-AL8Lra
GPG_AGENT_INFO=/home/inet/.cache/keyring-AL8Lra/gpg:0:1
GNOME_KEYRING_CONTROL=/home/inet/.cache/keyring-AL8Lra
GNOME_KEYRING_CONTROL=/home/inet/.cache/keyring-AL8Lra
GPG_AGENT_INFO=/home/inet/.cache/keyring-AL8Lra/gpg:0:1
GNOME_KEYRING_CONTROL=/home/inet/.cache/keyring-AL8Lra
GPG_AGENT_INFO=/home/inet/.cache/keyring-AL8Lra/gpg:0:1
SSH_AUTH_SOCK=/home/inet/.cache/keyring-AL8Lra/ssh

(gnome-panel:7042): Gtk-CRITICAL **: gtk_accelerator_parse_with_keycode: 
assertion `accelerator != NULL' failed

** (gnome-panel:7042): WARNING **: Unable to parse mouse modifier '(null)'

Initializing tracker-miner-fs...
Initializing tracker-store...
Tracker-Message: Setting up monitor for changes to config 
file:'/home/inet/.config/tracker/tracker-miner-fs.cfg'
Starting log:
  File:'/home/inet/.local/share/tracker/tracker-miner-fs.log'
Tracker-Message: Setting up monitor for changes to config 
file:'/home/inet/.config/tracker/tracker-store.cfg'
Tracker-Message: Setting up monitor for changes to config 
file:'/home/inet/.config/tracker/tracker-store.cfg'
Starting log:
  File:'/home/inet/.local/share/tracker/tracker-store.log'

** (gnome-screensaver:7061): WARNING **: Config key not handled: 
disable-application-handlers

** (gnome-screensaver:7061): WARNING **: Config key not handled: 
disable-command-line

** (gnome-screensaver:7061): WARNING **: Config key not handled: disable-log-out

** (gnome-screensaver:7061): WARNING **: Config key not handled: 
disable-print-setup

** (gnome-screensaver:7061): WARNING **: Config key not handled: 
disable-printing

** (gnome-screensaver:7061): WARNING **: Config key not handled: 
disable-save-to-disk
** Message: applet now removed from the notification area

(gnome-panel:7042): Gtk-CRITICAL **: 
_gtk_style_properties_set_property_by_property: assertion `_gtk_css_value_holds 
(value, _gtk_css_style_property_get_computed_type (style_prop))' failed
** Message: already started, ignoring error

(gnome-panel:7042): Gtk-CRITICAL **: 
_gtk_style_properties_set_property_by_property: assertion `_gtk_css_value_holds 
(value, _gtk_css_style_property_get_computed_type (style_prop))' failed

(gnome-panel:7042): Gtk-CRITICAL **: gtk_accelerator_parse_with_keycode: 
assertion `accelerator != NULL' failed

** (gnome-panel:7042): WARNING **: Unable to parse mouse modifier '(null)'


(gnome-panel:7042): Gtk-CRITICAL **: 
_gtk_style_properties_set_property_by_property: assertion `_gtk_css_value_holds 
(value, _gtk_css_style_property_get_computed_type (style_prop))' failed

(gnome-panel:7042): GLib-GObject-WARNING **: 
/tmp/buildd/glib2.0-2.33.12+really2.32.4/./gobject/gsignal.c:2459: signal 
`size_request' is invalid for instance `0x10d27e0'

(gnome-panel:7042): Gtk-CRITICAL **: 
_gtk_style_properties_set_property_by_property: assertion `_gtk_css_value_holds 
(value, _gtk_css_style_property_get_computed_type (style_prop))' failed

(gnome-panel:7042): Gtk-CRITICAL **: 
_gtk_style_properties_set_property_by_property: assertion `_gtk_css_value_holds 
(value, _gtk_css_style_property_get_computed_type (style_prop))' failed

(gnome-panel:7042): Gtk-CRITICAL **: 
_gtk_style_properties_set_property_by_property: assertion `_gtk_css_value_holds 
(value, _gtk_css_style_property_get_computed_type (style_prop))' fa

Bug#691699: libxkbcommon: upgrade to 0.2.0

[Michael Stapelberg]

Hi Timo,

Timo Aaltonen  writes:
>> Could you make the build log verbose (i.e. don't hide compiler
>> command-lines)? Passing --disable-silent-rules to configure, or V=1
>> to make should do the trick.
>
> why?
See http://wiki.debian.org/UpstreamGuide#Verbose_builds

>> It might be a good idea to add build-dependency on "dpkg-dev (>=
>> 1.16.0)", which is needed for multi-arch support. debhelper in the
>> main archive has this dependency itself, but the one in squeeze
>> backports doesn't.
>
> Why would you want libxkbcommon in squeeze backports?
libxkbcommon will be a requirement for future versions of i3lock, which
I would like to upload to backports eventually (due to much improved
keyboard handling).

AFAICT, there were updates to
http://anonscm.debian.org/gitweb/?p=pkg-xorg/lib/libxkbcommon.git but no
new upload yet. What is blocking a new upload? Can I help in any way?

Thanks.

-- 
Best regards,
Michael


-- 
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/x6a9nq940q@midna.zekjur.net

Bug#708980: xserver-xephyr does not open a window

[Jan Christoph Uhde]

Package: xserver-xephyr
Version: 2:1.12.4-6
Severity: important

Dear Maintainer,

Xephyr stopped working for me some days ago. At first I thought it is some
problem of the enlightenment 17 build I use. Today I have tried to run bbox,
gnome-session and other WMs but none of them worked.

I use the following script to start my sessions:
» cat desktop-xephyr 
#!/bin/bash
if [[ -z "$@" ]]; then
echo "you need to supply something to be started in Xephyr"
exit 1
fi

xdisplay()
{
local disp=0;
while [ -e "/tmp/.X${disp}-lock" ]; do
disp=$(( disp + 1 ));
done;
echo $disp
}

#select display
display=$(xdisplay)

#start xserver
Xephyr -ac -screen 1600x900 -br 2> /dev/null :$display &

#set display
export DISPLAY=:$display

#wait for Xephyr to become ready
sleep 1

#start window manager
bash -c "$@"

#remove x lock
rm -fr /tmp/.X${display}-lock

And it creates the following output:

» bash -x desktop-xephyr /usr/bin/blackbox 
+ [[ -z /usr/bin/blackbox ]]
++ xdisplay
++ local disp=0
++ '[' -e /tmp/.X0-lock ']'
++ disp=1
++ '[' -e /tmp/.X1-lock ']'
++ echo 1
+ display=1
+ export DISPLAY=:1
+ Xephyr -ac -screen 1600x900 -br :1
+ DISPLAY=:1
+ sleep 1
+ bash -c /usr/bin/blackbox
bt::Display: failed to open display ''
+ rm -fr /tmp/.X1-lock


I think running "+ Xephyr ..." line used to open a window. But this is not
happening anymore.

Please give me some hints how to provide more useful information.

Regards,
Jan C. Uhde


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

Kernel: Linux 3.8-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages xserver-xephyr depends on:
ii  libaudit0 1:1.7.18-1.1
ii  libc6 2.17-3
ii  libdrm2   2.4.40-1~deb7u2
ii  libgcrypt11   1.5.0-5
ii  libgl1-mesa-glx [libgl1]  8.0.5-5
ii  libpixman-1-0 0.26.0-4
ii  libselinux1   2.1.13-1
ii  libx11-6  2:1.5.0-1
ii  libxau6   1:1.0.7-1
ii  libxdmcp6 1:1.1.1-1
ii  libxext6  2:1.3.1-2
ii  libxfont1 1:1.4.5-2
ii  libxv12:1.0.7-1
ii  xserver-common2:1.12.4-6

Versions of packages xserver-xephyr recommends:
ii  libgl1-mesa-dri  8.0.5-5

xserver-xephyr suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130519225522.11253.26936.reportbug@edward

Bug#688828: Solution or workaround?

[Geoff Crompton]

On 18/05/13 10:10, Geoff Crompton wrote:

On 18/05/13 09:49, Thaddeus H. Black wrote:
I'm sorry, I don't have a work around. I never tried the drm-3.7 branch
that Alex suggested. Due to bug 703468 I've been booting some later
kernels as well, and I think I still have the same problem. On Monday
(when I'm back at that computer) I'll confirm which kernel I'm running,
and whether that kernel has fixed this bug.

Cheers,
Geoff


The computer at work is running a 3.6.9-1~experimental.1 kernel, 
downloaded from snapshot.debian.org (as part of working on bug 703468). 
This kernel does still have the bug on this computer.


Cheers,
Geoff


--
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/5199622b.7050...@trinity.unimelb.edu.au