Bug#712852: [Debian-med-packaging] Bug#712852: gwyddion: Gwyddion does not start
Hello Tim, the gwyddion upstream maintainer said: = This most likely is not Gwyddion-specific bug. But the only thing I can suggest to try is running gwyddion with --disable-gl. = This could help with driver issues. But debugging stuff like that is well beyond my capabilities, I'm afraid. But try first... Best regards, Jan Und es begab sich am 21.06.2013 17:45, dass bugrep...@quantentunnel.de schrieb: Hello Jan, well, I only use Debian stable. But I just installed Gwyddion on a second machine. There it works. The Bug appears on a computer with an ATI Radeon card. The other one has an Intel chip. Could the driver may be a reason? I also tried apt-get install --reinstall but it didn't help. Have a nice weekend Tim -- Jan Beyer happy Debian Maintainer ;-) mailj...@beathovn.deGPG key ID 0x0CA6B4AA jabber beath...@jabber.org web http://www.beathovn.de/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712852: gwyddion: Gwyddion does not start
Package: gwyddion Version: 2.28-2 Severity: important Dear Maintainer, Gwyddion does nor start. Instead, this message appears in the terminal: The program 'gwyddion' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 120 error_code 1 request_code 135 minor_code 19) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) The -sync option has no affect, by the way. -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gwyddion depends on: ii gwyddion-common 2.28-2 ii libatk1.0-0 2.4.0-2 ii libc6 2.13-38 ii libcairo2 1.12.2-3 ii libfftw3-33.3.2-3.1 ii libfontconfig12.9.0-7.1 ii libfreetype6 2.4.9-1.1 ii libgcc1 1:4.7.2-5 ii libgdk-pixbuf2.0-02.26.1-1 ii libgl1-mesa-glx [libgl1] 8.0.5-4+deb7u2 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libglu1-mesa [libglu1]8.0.5-4+deb7u2 ii libgtk2.0-0 2.24.10-2 ii libgtkglext1 1.2.0-2 ii libgtksourceview2.0-0 2.10.4-1 ii libgwyddion2-02.28-2 ii libice6 2:1.0.8-2 ii libpango1.0-0 1.30.0-1 ii libpng12-01.2.49-1 ii libpython2.7 2.7.3-6 ii libsm62:1.2.1-2 ii libstdc++64.7.2-5 ii libx11-6 2:1.5.0-1+deb7u1 ii libxml2 2.8.0+dfsg1-7+nmu1 ii libxmu6 2:1.1.1-1 ii libxt61:1.1.3-1+deb7u1 ii zlib1g1:1.2.7.dfsg-13 gwyddion recommends no packages. Versions of packages gwyddion suggests: ii gwyddion-plugins 2.28-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712852: gwyddion: Gwyddion does not start
Hi, just to provide some additional information: The problem does not seem to exist under recent testing (also amd64) - at least I was not able to reproduce it here. Kind regards Andreas. On Thu, Jun 20, 2013 at 08:43:19AM +0200, Tim wrote: Package: gwyddion Version: 2.28-2 Severity: important Dear Maintainer, Gwyddion does nor start. Instead, this message appears in the terminal: The program 'gwyddion' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 120 error_code 1 request_code 135 minor_code 19) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) The -sync option has no affect, by the way. -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gwyddion depends on: ii gwyddion-common 2.28-2 ii libatk1.0-0 2.4.0-2 ii libc6 2.13-38 ii libcairo2 1.12.2-3 ii libfftw3-33.3.2-3.1 ii libfontconfig12.9.0-7.1 ii libfreetype6 2.4.9-1.1 ii libgcc1 1:4.7.2-5 ii libgdk-pixbuf2.0-02.26.1-1 ii libgl1-mesa-glx [libgl1] 8.0.5-4+deb7u2 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libglu1-mesa [libglu1]8.0.5-4+deb7u2 ii libgtk2.0-0 2.24.10-2 ii libgtkglext1 1.2.0-2 ii libgtksourceview2.0-0 2.10.4-1 ii libgwyddion2-02.28-2 ii libice6 2:1.0.8-2 ii libpango1.0-0 1.30.0-1 ii libpng12-01.2.49-1 ii libpython2.7 2.7.3-6 ii libsm62:1.2.1-2 ii libstdc++64.7.2-5 ii libx11-6 2:1.5.0-1+deb7u1 ii libxml2 2.8.0+dfsg1-7+nmu1 ii libxmu6 2:1.1.1-1 ii libxt61:1.1.3-1+deb7u1 ii zlib1g1:1.2.7.dfsg-13 gwyddion recommends no packages. Versions of packages gwyddion suggests: ii gwyddion-plugins 2.28-2 -- no debconf information ___ Debian-med-packaging mailing list debian-med-packag...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712852: [Debian-med-packaging] Bug#712852: gwyddion: Gwyddion does not start
Dear Tim, thanks for the bug report. Unfortunately, I cannot reproduce the bug here on a kind-of-recent Debian unstable. Even worse, I currently do not have a working Debian stable installation around. But I will contact the upstream author of gwyddion, maybe he has seen something similar before and can help. And I will see what I can do to get a working Debian stable installation again. In the meantime I would like to ask you to check whether a reinstallation of gwyddion might help? In case there could be some strange configuration trouble somewhere? If you have aptitude installed, then sudo aptitude reinstall gwyddion could do the trick. Otherwise simply uninstall and reinstall gwyddion. Best regards, Jan -- Jan Beyer happy Debian Maintainer ;-) mailj...@beathovn.deGPG key ID 0x0CA6B4AA jabber beath...@jabber.org web http://www.beathovn.de/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
