Package: libx11-6 Followup-For: Bug #630169 Hello, i took a stab at reproducing the issue and think it is not really a bug in libx11.
Getting a backtrace of the problem with debug symbols confirms that the XSetWMProperties function is called with bogus arguments. Specifically bogus value for argc which lets XSetCommand (called from XSetWMProperties) trying to access the argv array out of its bound -> segv. The bogus value is being passed in from some qt code. Searching a bit shows that this seems to be a known problem for some years [1] [2]. Note: [1] seems to be post from the bug-reporter here. [3] Seems to indicate wrong usage of qt api by the programs using it. So not completely clear to where the bug should be reassigned to (qt4? ocaml used by the sample-code?, but looks like its definitely not the fault of libx11 when bogus input data is sent in. Also i see no way at the moment to enhance the XSetWMProperties with some arguments checking for this specific case. Regards, Stefan [1] http://qt-project.org/forums/viewthread/7838 [2] http://lists.qt.nokia.com/public/qt-interest/2009-March/003675.html [3] http://www.qtcentre.org/archive/index.php/t-28785.html -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-2-amd64 (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20130817125320.16574.93532.reportbug@shupnapc
