After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 697922 - bijiben Segfaults on X86 Platform
bijiben Segfaults on X86 Platform
Status: RESOLVED DUPLICATE of bug 697921
Product: bijiben
Classification: Applications
Component: general
3.8.x
Other Linux
: Normal critical
: ---
Assigned To: Bijiben maintainer(s)
Bijiben maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-04-12 22:05 UTC by Balázs L. Batári
Modified: 2013-04-12 22:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gdb backtrace (3.83 KB, application/octet-stream)
2013-04-12 22:05 UTC, Balázs L. Batári
Details

Description Balázs L. Batári 2013-04-12 22:05:49 UTC
Created attachment 241410 [details]
gdb backtrace

Running bijiben and clicking the "New" button crashes bijiben with a "Segmentation Fault"
While Running it on my X64 (Arch too) laptop everything works.

Steps to reproduce:

1. Run bijiben
2. Click the "New" button
3. segmentation fault (core dumped)  bijiben

Sytem info:
Distribution: Arch Linux
Architecture: X86
CPU: AMD Phenom(tm) II X4 955 Processor
RAM: 8Gb RAM
Kernel: 3.8.6-1-pae 
Gnome version: 3.8.0
bijiben version: 3.8.0
gcc version 4.8.0 20130411

gdb backtrace attached
Comment 1 Antoine Saroufim 2013-04-12 22:18:07 UTC
Same issue as https://bugzilla.gnome.org/process_bug.cgi
Comment 2 Antoine Saroufim 2013-04-12 22:19:15 UTC
A few seconds ago someone filed the same bug report
Comment 3 Antoine Saroufim 2013-04-12 22:20:12 UTC
Correct link: https://bugzilla.gnome.org/show_bug.cgi?id=697922
Comment 4 Balázs L. Batári 2013-04-12 22:21:01 UTC
thats the link to this bug :)
Comment 5 Balázs L. Batári 2013-04-12 22:22:20 UTC
i see now: https://bugzilla.gnome.org/show_bug.cgi?id=697921

how can i close this then ?
Comment 6 Pierre-Yves Luyten 2013-04-12 22:23:23 UTC
yep, duplicate with a few seconds interval:)

*** This bug has been marked as a duplicate of bug 697921 ***
Comment 7 Balázs L. Batári 2013-04-12 22:23:52 UTC
found it