Bug 1096861 - lifeograph does not start
Summary: lifeograph does not start
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lifeograph
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ankur Sinha (FranciscoD)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-12 14:29 UTC by nomnex
Modified: 2014-08-28 15:29 UTC (History)
5 users (show)

Fixed In Version: lifeograph-1.1.0-1.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-28 15:29:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description nomnex 2014-05-12 14:29:09 UTC
Description of problem:

Lifeograph from the stable repository does not start on Fedora LXDE 20

Version-Release number of selected component (if applicable):

Lifeograph 0.11.1

How reproducible:

Always

Steps to Reproduce:
1. # yum install lifeograph
2. $ lifeograph


Actual results:

[mt@localhost ~]$ lifeograph
INFO: No configuration file, maiden voyage!
Segmentation fault


Expected results:



Additional info:

Package maintainer, could you please update the stable F20 repo with version 1.0.1. Thanks

Comment 1 Ankur Sinha (FranciscoD) 2014-05-13 09:03:45 UTC
Hi,

Thank you for your bug report. Can you please install the required debuginfo packages and provide us with a stack trace? Lifeograph 1.0.1 itself is broken. I've informed upstream and he fixed the issue in r1642. However, I'm unsure if lifeograph 1.0.1+ is supposed to use gnome3.10 libraries, or gnome3.12. It works with gnome3.12, and I maintain a COPR repository here:

http://copr.fedoraproject.org/coprs/ankursinha/lifeograph/

Once you provide the stack trace, I'll be in a better position to understand if it's a bug that a package update will fix, or if it's something else. 

Thanks,
Ankur

Comment 2 nomnex 2014-05-14 02:08:12 UTC
Hi,

Thank you for maintaining this package.

I don't use Gnome, I use the Fedora LXDE spin if it is relevant with the bug report?

I begun to read the Wiki http://fedoraproject.org/wiki/StackTraces#Installing_debuginfo_RPMs_using_yum but I won't have time to give it a try before the end of the month. Sorry.

Comment 3 Ankur Sinha (FranciscoD) 2014-05-14 05:32:09 UTC
Hi,

This should be enough:

$ sudo debuginfo-install lifeograph

$ gdb lifeograph

# in gdb:
> run

# when it crashes
> bt

# to get out of gdb:
> q

You can then copy paste the back trace and provide it here. 

I just need to figure out where it's segfaults. 

Thanks,
Warm regards,
Ankur

Comment 4 Nathan Robertson 2014-08-15 02:08:25 UTC
Ok, I've got this one too. Machine is a Fedora 20 x64 VM running on VMware Fusion, on Mac OS X 10.9. Here's the gdb backtrace:

[nathanr@localhost ~]$ gdb lifeograph
GNU gdb (GDB) Fedora 7.7.1-17.fc20
Copyright (C) 2014 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 "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from lifeograph...Reading symbols from /usr/lib/debug/usr/bin/lifeograph.debug...done.
done.
(gdb) run
Starting program: /usr/bin/lifeograph 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Missing separate debuginfo for /lib64/libgraphite2.so.3
Try: yum --enablerepo='*debug*' install /usr/lib/debug/.build-id/90/82e46860379c3dff9004eb8c9834e50afbb528.debug
Detaching after fork from child process 36559.
Detaching after fork from child process 36560.
[New Thread 0x7fffef86a700 (LWP 36561)]
INFO: No configuration file, maiden voyage!
[New Thread 0x7fffef041700 (LWP 36562)]
[New Thread 0x7fffee840700 (LWP 36563)]
[New Thread 0x7fffee03f700 (LWP 36564)]
[New Thread 0x7fffed83e700 (LWP 36565)]
[New Thread 0x7fffecdb1700 (LWP 36566)]
[Thread 0x7fffee840700 (LWP 36563) exited]
[Thread 0x7fffee03f700 (LWP 36564) exited]

Program received signal SIGSEGV, Segmentation fault.
Gtk::Widget::drag_dest_set (this=0x0, targets=..., flags=Gtk::DEST_DEFAULT_ALL, actions=Gdk::ACTION_COPY) at widget.cc:505
505           targets.size(), (GdkDragAction)actions);
Missing separate debuginfos, use: debuginfo-install GConf2-3.2.6-7.fc20.x86_64 at-spi2-atk-2.10.2-1.fc20.x86_64 at-spi2-core-2.10.2-1.fc20.x86_64 dbus-glib-0.100.2-2.fc20.x86_64 dbus-libs-1.6.12-9.fc20.x86_64 dconf-0.18.0-2.fc20.x86_64 expat-2.1.0-7.fc20.x86_64 fontconfig-2.11.0-2.fc20.x86_64 freetype-2.5.0-5.fc20.x86_64 harfbuzz-0.9.27-1.fc20.x86_64 hunspell-1.3.2-14.fc20.x86_64 libX11-1.6.1-1.fc20.x86_64 libXau-1.0.8-2.fc20.x86_64 libXcomposite-0.4.4-4.fc20.x86_64 libXcursor-1.1.14-2.fc20.x86_64 libXdamage-1.1.4-4.fc20.x86_64 libXext-1.3.2-2.fc20.x86_64 libXfixes-5.0.1-2.fc20.x86_64 libXi-1.7.4-1.fc20.x86_64 libXinerama-1.1.3-2.fc20.x86_64 libXrandr-1.4.1-2.fc20.x86_64 libXrender-0.9.8-2.fc20.x86_64 libXxf86vm-1.1.3-2.fc20.x86_64 libdrm-2.4.54-1.fc20.x86_64 libffi-3.0.13-5.fc20.x86_64 libgpg-error-1.12-1.fc20.x86_64 libpng-1.6.6-3.fc20.x86_64 libselinux-2.2.1-6.fc20.x86_64 libwayland-client-1.2.0-3.fc20.x86_64 libwayland-cursor-1.2.0-3.fc20.x86_64 libwayland-server-1.2.0-3.fc20.x86_64 libxcb-1.9.1-3.fc20.x86_64 libxkbcommon-0.3.1-1.fc20.x86_64 mesa-libEGL-10.1.5-1.20140607.fc20.x86_64 mesa-libGL-10.1.5-1.20140607.fc20.x86_64 mesa-libgbm-10.1.5-1.20140607.fc20.x86_64 mesa-libglapi-10.1.5-1.20140607.fc20.x86_64 oxygen-gtk3-1.3.5-1.fc20.x86_64 pcre-8.33-6.fc20.x86_64 pixman-0.30.0-4.fc20.x86_64 systemd-libs-208-21.fc20.x86_64 xz-libs-5.1.2-12alpha.fc20.x86_64 zlib-1.2.8-3.fc20.x86_64
(gdb) bt
#0  Gtk::Widget::drag_dest_set (this=0x0, targets=..., flags=Gtk::DEST_DEFAULT_ALL, actions=Gdk::ACTION_COPY) at widget.cc:505
#1  0x000000000046afe4 in LIFEO::EntryView::EntryView (this=0xba2fe0) at ../src/view_entry.cpp:88
#2  0x0000000000451f03 in LIFEO::Lifeograph::login (this=0x7a6800) at ../src/lifeograph.cpp:505
#3  0x0000000000470e39 in LIFEO::ViewLogin::open_selected_diary (this=0x726cc0, read_only=<optimized out>) at ../src/view_login.cpp:374
#4  0x00007ffff6c67a48 in operator() (this=0xb10668) at /usr/include/sigc++-2.0/sigc++/functors/slot.h:440
#5  Glib::SignalProxyNormal::slot0_void_callback (self=<optimized out>, data=0xb10660) at signalproxy.cc:95
#6  0x0000003c07610298 in g_closure_invoke (closure=0xb10710, return_value=return_value@entry=0x0, n_param_values=1, param_values=param_values@entry=0x7fffffffcff0, invocation_hint=invocation_hint@entry=0x7fffffffcf90) at gclosure.c:777
#7  0x0000003c07622601 in signal_emit_unlocked_R (node=node@entry=0x870340, detail=detail@entry=0, instance=instance@entry=0xa0ec50, emission_return=emission_return@entry=0x0, 
    instance_and_params=instance_and_params@entry=0x7fffffffcff0) at gsignal.c:3656
#8  0x0000003c0762a0f2 in g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7fffffffd170) at gsignal.c:3330
#9  0x0000003c0762a3af in g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at gsignal.c:3386
#10 0x000000312c2dab00 in gtk_real_button_released (button=0xa0ec50) at gtkbutton.c:2106
#11 0x00007ffff7bbe080 in Gtk::Button_Class::released_callback (self=0xa0ec50) at button.cc:283
#12 0x0000003c076104c7 in _g_closure_invoke_va (closure=closure@entry=0x870200, return_value=return_value@entry=0x0, instance=instance@entry=0xa0ec50, args=args@entry=0x7fffffffd490, n_params=0, param_types=0x0) at gclosure.c:840
#13 0x0000003c07629749 in g_signal_emit_valist (instance=0xa0ec50, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7fffffffd490) at gsignal.c:3238
#14 0x0000003c0762a3af in g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=detail@entry=0) at gsignal.c:3386
#15 0x000000312c2d98b1 in gtk_button_button_release (widget=<optimized out>, event=<optimized out>) at gtkbutton.c:1938
#16 0x00007ffff7c5b4d4 in Gtk::Widget::on_button_release_event (this=0xaf8e30, event=0xb25260) at widget.cc:8145
#17 0x00007ffff7c5d6d4 in Gtk::Widget_Class::button_release_event_callback (self=0xa0ec50, p0=0xb25260) at widget.cc:4582
#18 0x000000312c3ab52c in _gtk_marshal_BOOLEAN__BOXED (closure=0x705230, return_value=0x7fffffffd6e0, n_param_values=<optimized out>, param_values=0x7fffffffd790, invocation_hint=<optimized out>, marshal_data=<optimized out>)
    at gtkmarshalers.c:85
#19 0x0000003c07610298 in g_closure_invoke (closure=closure@entry=0x705230, return_value=return_value@entry=0x7fffffffd6e0, n_param_values=2, param_values=param_values@entry=0x7fffffffd790, 
    invocation_hint=invocation_hint@entry=0x7fffffffd730) at gclosure.c:777
#20 0x0000003c0762211b in signal_emit_unlocked_R (node=node@entry=0x705280, detail=detail@entry=0, instance=instance@entry=0xa0ec50, emission_return=emission_return@entry=0x7fffffffd840, 
    instance_and_params=instance_and_params@entry=0x7fffffffd790) at gsignal.c:3624
#21 0x0000003c07629ddd in g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7fffffffd920) at gsignal.c:3340
#22 0x0000003c0762a3af in g_signal_emit (instance=instance@entry=0xa0ec50, signal_id=<optimized out>, detail=detail@entry=0) at gsignal.c:3386
#23 0x000000312c4dd37c in gtk_widget_event_internal (widget=widget@entry=0xa0ec50, event=event@entry=0xb25260) at gtkwidget.c:7168
#24 0x000000312c4dd659 in gtk_widget_event (widget=widget@entry=0xa0ec50, event=event@entry=0xb25260) at gtkwidget.c:6830
#25 0x000000312c3a990c in propagate_event_up (topmost=<optimized out>, event=<optimized out>, widget=0xa0ec50) at gtkmain.c:2391
#26 propagate_event (widget=<optimized out>, event=0xb25260, captured=<optimized out>, topmost=0x0) at gtkmain.c:2499
#27 0x000000312c3ab1ea in gtk_main_do_event (event=0xb25260) at gtkmain.c:1714
#28 0x000000312be4ef62 in gdk_event_source_dispatch (source=source@entry=0x712180, callback=<optimized out>, user_data=<optimized out>) at gdkeventsource.c:364
#29 0x0000003c05a492a6 in g_main_dispatch (context=0x722ad0) at gmain.c:3066
#30 g_main_context_dispatch (context=context@entry=0x722ad0) at gmain.c:3642
#31 0x0000003c05a49628 in g_main_context_iterate (context=0x722ad0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3713
#32 0x0000003c05a49a3a in g_main_loop_run (loop=0xad8420) at gmain.c:3907
#33 0x000000312c3aa6f5 in gtk_main () at gtkmain.c:1158
#34 0x00007ffff7c002cd in Gtk::Main::run (window=...) at main.cc:399
#35 0x00000000004230e9 in main (argc=1, argv=0x7fffffffdde8) at ../src/main.cpp:60
(gdb)

Comment 5 Nathan Robertson 2014-08-15 02:56:08 UTC
I recompiled lifeograph-1.0.1-3.r1642.fc21.src.rpm from Rawhide on Fedora 20 and that works fine.

I suggest that that package gets pushed out on the FC20 channel as an update - that should fix this issue.

Comment 6 Ankur Sinha (FranciscoD) 2014-08-15 07:05:28 UTC
I see that 1.1.0 has been released. I'll update rawhide and F20 over the weekend.

https://launchpad.net/lifeograph/trunk/1.1.0

Comment 7 Fedora Update System 2014-08-17 03:42:50 UTC
lifeograph-1.1.0-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/lifeograph-1.1.0-1.fc20

Comment 8 lnie 2014-08-18 08:13:19 UTC
lifeograph-1.1.0-1.fc20 works

Comment 9 Nathan Robertson 2014-08-19 03:08:08 UTC
The updated package (lifeograph-1.1.0-1.fc20) works for me.

Comment 10 Ankur Sinha (FranciscoD) 2014-08-19 04:11:58 UTC
If you have the time, please consider providing karma to the update, otherwise it'll remain in the testing repository for at least 2 weeks.

Comment 11 Fedora Update System 2014-08-19 07:03:22 UTC
Package lifeograph-1.1.0-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing lifeograph-1.1.0-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-9518/lifeograph-1.1.0-1.fc20
then log in and leave karma (feedback).

Comment 12 Fedora Update System 2014-08-28 15:29:23 UTC
lifeograph-1.1.0-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.