Hi,
pdfchain decided to quit working. It just segfaults when started.
oppa@oppa-hex-ssd:~$ pdfchain
PDF Chain 0.4.4.2 - A graphical user interface for the PDF Toolkit
Segmentation fault
This is sad because this was very easy to use and did the job. Do you know of any alternatives ?
Please let me know.
Have fun,
Stephan
Edit:
Does this help ? It seems to choke on glib.
(gdb) run
Starting program: /usr/bin/pdfchain
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffea4fe700 (LWP 16794)]
[New Thread 0x7fffe9cfd700 (LWP 16795)]
PDF Chain 0.4.4.2 - A graphical user interface for the PDF Toolkit
[New Thread 0x7fffe3fff700 (LWP 16797)]
[New Thread 0x7fffe36eb700 (LWP 16798)]
[New Thread 0x7fffe2c97700 (LWP 16800)]
Thread 1 "pdfchain" received signal SIGSEGV, Segmentation fault.
0x00007ffff4af9360 in g_slist_find () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
An alternative might be: file a bug
Hi Stephan,
no problems here with pdfchain 1:0.4.4.2-1 on my kde based system.
I think pdfsam could do the same job
Mal ganz ehrlich - wir fahren sid - und da ändern sich auch mal Bibliotheken un ABIs und so was - normalerweise wird das während Transitions erledigt. Wenn das mal nicht klappt, dann sollte man nen bug malen. Terminal auf, "reportbug pdfchain" ist doch nur wirklich nicht zu viel, oder? So über den Daumen gepeilt ist ein Segfault einer der Fehler, die in Debian nicht auftreten sollten - und wenn doch, dann wissen die jeweiligen Maintainer auch gerne darüber Bescheid um das zu fixen.
QuoteAn alternative might be: file a bug
Well, not for me. I'm either too numb for this or I'm not allowed to file bugs. I've used reportbug two times but never saw these bug reports or heard something about it.
QuoteI think pdfsam could do the same job
Thanks, I'll have a look. For now I used pdftk:
pdftk file1 file2 fileN cat output outputfilename Edit: this was all messed up by itself...
Also here no problem with version 1:0.4.4.2-1 and Xfce.
neither do I see issues with cinnamon.
Perhaps you can see what config file causes the crash with
~$ strace -eopen pdfchain
For me pdfchain does not crash/segfault, but there is an existing bugreport already from 2013, still not fixed since then, with same symptoms (libglib): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725859
Hi,
this produces about a billion lines of output.
strace -eopen pdfchain | grep WHAT
I did this as root by accident and pdfchain is showing up. It is bright white, I have the dark theme running in Gnome but this maybe because root started it.
Edit: I've started it as root again. There is some problem, the screen shows some flickering in the upper right. This stops when I close pdfchain.
Don't start it as root.
The strace will stop as soon as the segfault happens, so hopefully the culprit will be opened near the end.
At least this is the theory ...
With some more luck, the cause is one of your user config files, so you can avoid it easily.
greetz
musca
Quote from: musca on 2017/12/14, 22:52:05
The strace will stop as soon as the segfault happens, so hopefully the culprit will be opened near the end.
It might be that strace is the wrong tool for that - i would suggest gdb - and some debug symbols installed. But before i would clean up the system, install the latest packages, remove not needed packages and packages that are no longer in the repository. Segfaults are not common behaviour of debian packages - and they mostly occour if wrong or broken dependencies are installed.
Moin,
after a reboot and a d-u and another reboot.
Output of strace -eopen pdfchain: http://paste.siduction.org/20171215113748
To me this looks like I'm missing everything. A ton of ENOENT lines.
Have a nice weekend,
Stephan
In case of optional files you don't need to worry about ENOENT.
It seems reading "/home/oppa/.config/dconf/user" lets your app segfault.
you can try to avoid that.
Erm - how do I avoid this ? I've tried to rename but then I get another ENOENT and a segfault.