Bug#802890: backintime-qt4: can't launch with gksu/gksudo, blank grey window appears

2015-10-24 Thread Lev Livnev
Package: backintime-qt4
Version: 1.1.6-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Trying to start the QT interface for backintime-qt4 using:

$ gksu backintime-qt4

results in a blank grey window appearing, along with the output:

Back In Time
Version: 1.1.6

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime-qt4 --license' for details.

X Error: BadAccess (attempt to access private resource denied) 10
  Extension:130 (MIT-SHM)
  Minor opcode: 1 (X_ShmAttach)
  Resource id:  0x18b
X Error: BadShmSeg (invalid shared segment parameter) 128
  Extension:130 (MIT-SHM)
  Minor opcode: 5 (X_ShmCreatePixmap)
  Resource id:  0xf4
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x3800013
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x3800013
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x3800013
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x3800013
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x3800013
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x3800013

(using gksudo leads to the same behaviour but without the above Error messages
in the output.) This appears to be a common problem for some qt4 programs, and
is fixed by running instead:

$ gksu QT_X11_NO_MITSHM=1 backintime-qt4

in which case the program runs as normal. This problem has only recently
started to affect my system, no idea why. Googling QT_X11_NO_MITSHM=1 shows
that this affects a lot of QT apps that need gksu/gksudo.



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

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages backintime-qt4 depends on:
ii  backintime-common 1.1.6-1
ii  libnotify-bin 0.7.6-2
ii  policykit-1   0.105-12
ii  python3-dbus.mainloop.qt  4.11.4+dfsg-1+b2
ii  python3-pyqt4 4.11.4+dfsg-1+b2
pn  python3:any   
ii  x11-utils 7.7+3

Versions of packages backintime-qt4 recommends:
ii  python3-secretstorage  2.1.2-3

Versions of packages backintime-qt4 suggests:
pn  meld | kompare  

-- no debconf information



Bug#802890: backintime-qt4: can't launch with gksu/gksudo, blank grey window appears

2015-10-24 Thread Germar Reitze
This is fixed upstream in 1.1.8

Please use 'pkexec backintime-qt4' instead of 'gksu'


signature.asc
Description: This is a digitally signed message part


Bug#802890: backintime-qt4: can't launch with gksu/gksudo, blank grey window appears

2015-10-24 Thread Germar Reitze
It's a duplicate of https://bugs.launchpad.net/backintime/+bug/1493020


signature.asc
Description: This is a digitally signed message part


Bug#802890: backintime-qt4: can't launch with gksu/gksudo, blank grey window appears

2015-10-24 Thread Germar Reitze
tags 802890 + fixed-upstream upstream
severity 802890 important
thanks


signature.asc
Description: This is a digitally signed message part