Bug 4201

Summary:	eog doesn't start after yesterday's update - no window displayed, no error in terminal
Product:	Mageia	Reporter:	JaromÃr CápÃk <tavvva>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	jani.valimaa
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	eog-3.3.4-1.mga2.src.rpm	CVE:
Status comment:

Description JaromÃr CápÃk 2012-01-20 09:26:17 CET

Description of problem:
Hello. After yesterday's updates I can't start Eye of Gnome. I get just 1 second long delay (when started from terminal) and nothing. Application is terminated without displaying the main window and without any text output in the terminal.


Version-Release number of selected component (if applicable):
3.3.4-1.mga2

How reproducible:
always

Steps to Reproduce:
1. Install the latest updates
2. Start EOG

Comment 1 Manuel Hiebel 2012-01-20 12:24:28 CET

Hi, we need the backtrace

1) enable the "core release debug"
2) install the following packages: gdb eog-debug
3) run the following command from a terminal:
   gdb -q eog
4) then type "run"
5) when it segfaults, type "bt" and copy back the stack trace in a file you'll
attach (not paste) to this bug report
Thanks

Keywords: (none) => NEEDINFO

Comment 2 JaromÃr CápÃk 2012-01-20 17:40:10 CET

Hello Manuel.

The funny thing is that I get no segfaults ... 

$ gdb -q eog
Reading symbols from /usr/bin/eog...Reading symbols from /usr/lib/debug/usr/bin/eog.debug...done.
done.
(gdb) run
Starting program: /usr/bin/eog 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffebacf700 (LWP 19351)]
[New Thread 0x7fffeb0c6700 (LWP 19352)]
[New Thread 0x7fffea8c5700 (LWP 19353)]
[New Thread 0x7fffe9125700 (LWP 19354)]
[Thread 0x7fffea8c5700 (LWP 19353) exited]
[Thread 0x7fffeb0c6700 (LWP 19352) exited]
[Thread 0x7fffebacf700 (LWP 19351) exited]
[Thread 0x7fffe9125700 (LWP 19354) exited]
[Inferior 1 (process 19348) exited normally]

Since correctly terminated apps have no stacktrace, I have nothing to attach.

J.

Comment 3 JaromÃr CápÃk 2012-01-22 16:28:20 CET

The problem disappeared after the latest updates ... The issue can be closed.

Comment 4 Jani Välimaa 2012-01-22 18:25:07 CET

Closing as OLD.

Status: NEW => RESOLVED
CC: (none) => jani.valimaa
Resolution: (none) => OLD