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

Bug#690521: marked as done (xxxterm: X Window System errror, dies with 'BadAlloc (insufficient resources for operation)')

Your message dated Thu, 03 Aug 2017 17:37:05 +0000
with message-id <[🔎] E1ddK3V-0009k0-Qp@fasolo.debian.org>
and subject line Bug#868984: Removed package(s) from unstable
has caused the Debian Bug report #690521,
regarding xxxterm: X Window System errror, dies with 'BadAlloc (insufficient resources for operation)'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
690521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690521
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: xxxterm
Version: 1:1.11.3-1
Severity: important

Steps to reproduce:

1) start xxxterm
2) do anything, e.g. click right on the empty main tab and select 'Inspect
   Element'
3) xxxterm dies with code 1, leaving the message:
   xxxterm: config_parse: cannot open /home/<myuser>/.xxxterm.conf: No such file or directory
   The program 'xxxterm' received an X Window System error.
   This probably reflects a bug in the program.
   The error was 'BadAlloc (insufficient resources for operation)'.
     (Details: serial 1328 error_code 11 request_code 53 minor_code 0)
     (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.)

(note I'm replacing my login name with <myuser>)

Running with --sync prevents from crashing there.

I'm a little confused, xxxterm runs on another Wheezy box, amd64, without
abnormality. I'm not sure what additional Information I could provide.

Using the source package gives the same behavior, running in gdb without
anything, with break on gdk_x_error() and finally with --sync gives:

$ gdb linux/xxxterm
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /home/<myuser>/tmp/xxxterm-1.11.3/linux/xxxterm...done.
(gdb) r
Starting program: /home/<myuser>/tmp/xxxterm-1.11.3/linux/xxxterm 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
xxxterm: config_parse: cannot open /home/<myuser>/.xxxterm.conf: No such file or directory
[New Thread 0xb341ab70 (LWP 11833)]
[New Thread 0xb2af2b70 (LWP 11834)]
[New Thread 0xb22ddb70 (LWP 11835)]
[New Thread 0xb1addb70 (LWP 11836)]
[New Thread 0xad309b70 (LWP 11837)]
[New Thread 0xac60db70 (LWP 11839)]
[New Thread 0xabe05b70 (LWP 11840)]
[New Thread 0xab605b70 (LWP 11841)]
[New Thread 0xaae05b70 (LWP 11842)]
[New Thread 0xaa605b70 (LWP 11843)]
[New Thread 0xa9e05b70 (LWP 11844)]
[New Thread 0xa94e4b70 (LWP 11845)]
[New Thread 0xa8ce4b70 (LWP 11846)]
[New Thread 0xa84e4b70 (LWP 11847)]
[New Thread 0xa7ce4b70 (LWP 11848)]
[New Thread 0xa6f6eb70 (LWP 11849)]
[Thread 0xac60db70 (LWP 11839) exited]
[New Thread 0xac60db70 (LWP 11850)]
[Thread 0xaa605b70 (LWP 11843) exited]
[Thread 0xab605b70 (LWP 11841) exited]
[Thread 0xabe05b70 (LWP 11840) exited]
[Thread 0xac60db70 (LWP 11850) exited]
[Thread 0xaae05b70 (LWP 11842) exited]
[Thread 0xa8ce4b70 (LWP 11846) exited]
[Thread 0xa7ce4b70 (LWP 11848) exited]
[Thread 0xa84e4b70 (LWP 11847) exited]
[Thread 0xa94e4b70 (LWP 11845) exited]
[New Thread 0xa94e4b70 (LWP 11851)]
[New Thread 0xa84e4b70 (LWP 11852)]
[New Thread 0xa7ce4b70 (LWP 11853)]
The program 'xxxterm' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 1432 error_code 11 request_code 53 minor_code 0)
  (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.)
[Thread 0xa7ce4b70 (LWP 11853) exited]
[Thread 0xa84e4b70 (LWP 11852) exited]
[Thread 0xa94e4b70 (LWP 11851) exited]
[Thread 0xa6f6eb70 (LWP 11849) exited]
[Thread 0xa9e05b70 (LWP 11844) exited]
[Thread 0xad309b70 (LWP 11837) exited]
[Thread 0xb1addb70 (LWP 11836) exited]
[Thread 0xb22ddb70 (LWP 11835) exited]
[Thread 0xb2af2b70 (LWP 11834) exited]
[Thread 0xb341ab70 (LWP 11833) exited]
[Inferior 1 (process 11830) exited with code 01]
(gdb) b gdk_x_error
Function "gdk_x_error" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (gdk_x_error) pending.
(gdb) r
Starting program: /home/<myuser>/tmp/xxxterm-1.11.3/linux/xxxterm 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
xxxterm: config_parse: cannot open /home/<myuser>/.xxxterm.conf: No such file or directory
[New Thread 0xb341ab70 (LWP 11860)]
[New Thread 0xb2af2b70 (LWP 11861)]
[New Thread 0xb22ddb70 (LWP 11862)]
[New Thread 0xb1addb70 (LWP 11863)]
[New Thread 0xad309b70 (LWP 11865)]
[New Thread 0xac60db70 (LWP 11866)]
[New Thread 0xabe05b70 (LWP 11867)]
[New Thread 0xab605b70 (LWP 11868)]
[New Thread 0xaae05b70 (LWP 11869)]
[New Thread 0xaa605b70 (LWP 11870)]
[New Thread 0xa9e04b70 (LWP 11871)]
[New Thread 0xa94e4b70 (LWP 11872)]
[New Thread 0xa8ce4b70 (LWP 11873)]
[New Thread 0xa84e4b70 (LWP 11874)]
[New Thread 0xa7ce4b70 (LWP 11875)]
[New Thread 0xa70fcb70 (LWP 11876)]
[Thread 0xabe05b70 (LWP 11867) exited]
[Thread 0xab605b70 (LWP 11868) exited]
[Thread 0xa84e4b70 (LWP 11874) exited]
[Thread 0xac60db70 (LWP 11866) exited]
[Thread 0xaa605b70 (LWP 11870) exited]
[Thread 0xa94e4b70 (LWP 11872) exited]
[Thread 0xa9e04b70 (LWP 11871) exited]
[Thread 0xa7ce4b70 (LWP 11875) exited]
[Thread 0xaae05b70 (LWP 11869) exited]
[New Thread 0xaae05b70 (LWP 11878)]
[New Thread 0xa7ce4b70 (LWP 11879)]
[New Thread 0xa9e04b70 (LWP 11880)]
The program 'xxxterm' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 1436 error_code 11 request_code 53 minor_code 0)
  (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.)
[Thread 0xa9e04b70 (LWP 11880) exited]
[Thread 0xa7ce4b70 (LWP 11879) exited]
[Thread 0xaae05b70 (LWP 11878) exited]
[Thread 0xa70fcb70 (LWP 11876) exited]
[Thread 0xa8ce4b70 (LWP 11873) exited]
[Thread 0xad309b70 (LWP 11865) exited]
[Thread 0xb1addb70 (LWP 11863) exited]
[Thread 0xb22ddb70 (LWP 11862) exited]
[Thread 0xb2af2b70 (LWP 11861) exited]
[Thread 0xb341ab70 (LWP 11860) exited]
[Inferior 1 (process 11859) exited with code 01]
(gdb) r --sync
Starting program: /home/<myuser>/tmp/xxxterm-1.11.3/linux/xxxterm --sync
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
xxxterm: config_parse: cannot open /home/<myuser>/.xxxterm.conf: No such file or directory
[New Thread 0xb341ab70 (LWP 11884)]
[New Thread 0xb2af2b70 (LWP 11885)]
[New Thread 0xb20ffb70 (LWP 11886)]
[New Thread 0xb18ffb70 (LWP 11887)]
[New Thread 0xad208b70 (LWP 11888)]
[New Thread 0xac50cb70 (LWP 11890)]
[New Thread 0xabd04b70 (LWP 11891)]
[New Thread 0xab504b70 (LWP 11892)]
[New Thread 0xaad04b70 (LWP 11893)]
[New Thread 0xaa504b70 (LWP 11894)]
[New Thread 0xa9d03b70 (LWP 11895)]
[New Thread 0xa93e3b70 (LWP 11896)]
[New Thread 0xa8be3b70 (LWP 11897)]
[New Thread 0xa83e3b70 (LWP 11898)]
[New Thread 0xa7be3b70 (LWP 11899)]
[New Thread 0xa6ffbb70 (LWP 11900)]
[Thread 0xaad04b70 (LWP 11893) exited]
[New Thread 0xaad04b70 (LWP 11901)]
[Thread 0xa9d03b70 (LWP 11895) exited]
[Thread 0xa83e3b70 (LWP 11898) exited]
[Thread 0xa8be3b70 (LWP 11897) exited]
[Thread 0xac50cb70 (LWP 11890) exited]
[Thread 0xa93e3b70 (LWP 11896) exited]
[Thread 0xabd04b70 (LWP 11891) exited]
[Thread 0xaad04b70 (LWP 11901) exited]
[Thread 0xab504b70 (LWP 11892) exited]
[Thread 0xaa504b70 (LWP 11894) exited]
[New Thread 0xaa504b70 (LWP 11902)]
[New Thread 0xab504b70 (LWP 11903)]
[New Thread 0xaad04b70 (LWP 11904)]
[New Thread 0xabd04b70 (LWP 11906)]
[New Thread 0xa93e3b70 (LWP 11907)]
[New Thread 0xa9d03b70 (LWP 11908)]
[New Thread 0xa8be3b70 (LWP 11909)]
[New Thread 0xa83e3b70 (LWP 11910)]
[New Thread 0xa5cf8b70 (LWP 11911)]
[Thread 0xa93e3b70 (LWP 11907) exited]
[Thread 0xa9d03b70 (LWP 11908) exited]
[Thread 0xaad04b70 (LWP 11904) exited]
[Thread 0xaa504b70 (LWP 11902) exited]
[Thread 0xa83e3b70 (LWP 11910) exited]
[Thread 0xa8be3b70 (LWP 11909) exited]
[Thread 0xa5cf8b70 (LWP 11911) exited]
[Thread 0xab504b70 (LWP 11903) exited]
[Thread 0xabd04b70 (LWP 11906) exited]
[Thread 0xa6ffbb70 (LWP 11900) exited]
[Thread 0xa7be3b70 (LWP 11899) exited]
[Thread 0xad208b70 (LWP 11888) exited]
[Thread 0xb18ffb70 (LWP 11887) exited]
[Thread 0xb20ffb70 (LWP 11886) exited]
[Thread 0xb2af2b70 (LWP 11885) exited]
[Thread 0xb341ab70 (LWP 11884) exited]
[Inferior 1 (process 11883) exited normally]
(gdb) q
$

What's to do now? --sync would help debugging, but disables the bug.


Cheers,

	Julius


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

Kernel: Linux 3.2.0-3-486
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 xxxterm depends on:
ii  libatk1.0-0                 2.4.0-2
ii  libbsd0                     0.4.2-1
ii  libc6                       2.13-35
ii  libcairo2                   1.12.2-2
ii  libfontconfig1              2.9.0-7
ii  libfreetype6                2.4.9-1
ii  libgcrypt11                 1.5.0-3
ii  libgdk-pixbuf2.0-0          2.26.1-1
ii  libglib2.0-0                2.32.3-1
ii  libgnutls26                 2.12.20-1
ii  libgtk2.0-0                 2.24.10-2
ii  libjavascriptcoregtk-1.0-0  1.8.1-3.3
ii  libpango1.0-0               1.30.0-1
ii  libsoup2.4-1                2.38.1-2
ii  libwebkitgtk-1.0-0          1.8.1-3.3

xxxterm recommends no packages.

xxxterm suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 2:1.6.4-3+rm

Dear submitter,

as the package xombrero has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/868984

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)

--- End Message ---
Reply to: