[Gutsy] Kino freezes when starting

Bug #122437 reported by Duncan Lithgow
32
Affects Status Importance Assigned to Milestone
Kino
Unknown
Unknown
kino (Ubuntu)
Fix Released
Medium
Unassigned
Gutsy
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: kino

[Gutsy] Kino doesn't start with full GUI, actually when I just tried it a second time all I got was a window with nothing inside at all.

Revision history for this message
Justin Payne (neolithium82) wrote :

Thanks for taking the time to report this bug, however we are unable to fix it with the current information provided. Would you be able to provide the output of trying to run Kino from Terminal, and any backtrace if possible (https://wiki.ubuntu.com/Backtrace) I experienced a similar problem, however with the current description I'm not sure if they are identical. I experience Kino freezing partly through the launch of the program, causing it to have to be killed.

I will provide my logs below.

Regards,
Justin

Changed in kino:
assignee: nobody → jbeerwart
status: New → Incomplete
Revision history for this message
Justin Payne (neolithium82) wrote :
Revision history for this message
Justin Payne (neolithium82) wrote :
Revision history for this message
Justin Payne (neolithium82) wrote :
Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote :

output from GDB with Kino

Changed in kino:
assignee: jbeerwart → nobody
status: Incomplete → Confirmed
Changed in kino:
importance: Undecided → Medium
Changed in kino:
status: Confirmed → Triaged
Revision history for this message
riny (rinyfeller) wrote :

Here the same problem. I only got a small peace of the logo in the window of kino. I started Kino again, but now in the terminal. Same results.

Copy pasted the contents of the terminal in a textfile.

Revision history for this message
Jason Fergus (leech-sisna) wrote :

I've got the same thing, even while trying the 1.0.0 package from getdeb.net and from Debian's Experimental. The only thing I could guess is the problem is that it does not like the new GTK. It worked fine in Debian Sid.

Revision history for this message
Jonathan Anderson (jonathan-anderson) wrote :

Ditto for me... here's a screenshot.

Revision history for this message
Hans Halvorson (hans.halvorson) wrote :

Confirmed -- exactly the same problem here (Gutsy on i386)

Revision history for this message
Hans Halvorson (hans.halvorson) wrote :

I just tried Kino 1.0 from Debian Experimental. The problem persists, but the following additional information is given when trying to start in the terminal:

***MEMORY-WARNING***: [7458]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon...

Revision history for this message
Jonathan Anderson (jonathan-anderson) wrote :

I've noticed this in a few programs lately: Eclipse, gnome-terminal, Kino... only Kino seems to have major problems, though.

Revision history for this message
Jonathan Anderson (jonathan-anderson) wrote :

When I say "this", I mean the error message about glib functions being called before g_thread_init().

Revision history for this message
Tdey (tdey) wrote :

Ok, my problem is the same.

Revision history for this message
Bauldrick (gouldyis) wrote :

I get this same problem

Revision history for this message
Hans Halvorson (hans.halvorson) wrote :
Revision history for this message
Hans Halvorson (hans.halvorson) wrote :
Revision history for this message
Jonathan Anderson (jonathan-anderson) wrote :

Added a link to the SF.net bug tracker.

Revision history for this message
Andreas John (derjohn) wrote :

hm,
as stated in the thread mention by Snah Nosrovlah, the upstream version has fixed the bug. I droped-in their cvs and rebuilded the package. kino starts now (but at least one file overlaps with kinoplus).

Please consider using cvs from upstream.

rgds,
Andreas

Revision history for this message
Jonathan Anderson (jonathan-anderson) wrote :

I can confirm that CVS versions of Kino start up just fine.

Since Kino is in 'main', would 'ubuntu-dev' be the right team to assign to?

Changed in kino:
assignee: nobody → ubuntu-dev
Revision history for this message
Sebastien Bacher (seb128) wrote :

No, ubuntu-dev is not the right team, you are sending mails to the member of the team when you do, you should rather try to find somebody with an interest in kino to assign the bug or let it and wait for somebody to triage it

Changed in kino:
assignee: ubuntu-dev → nobody
Revision history for this message
Jonathan Anderson (jonathan-anderson) wrote :

> to find somebody with an interest in kino to assign the bug

I thought that packages in 'main' were Canonical-supported...

> wait for somebody to triage it

'Tis triaged. We have a fix (I could build a .deb package for you), but we need somebody with upload rights to actually put the fix in place.

Revision history for this message
Kees Cook (kees) wrote :

Hi Jon,

Can you attach the debdiff from the resulting .deb build?

Thanks!

Revision history for this message
Jonathan Anderson (jonathan-anderson) wrote :

Here's my debdiff file.

One issue is that kinoplus is (now?) in the Kino source tree, so kino now provides, replaces and conflicts with kinoplus.

Revision history for this message
Steve Kowalik (stevenk) wrote :

I've uploaded kino 1.1.0-3ubuntu1 to Gutsy, would you mind trying it and seeing if it still freezes when starting?

Revision history for this message
Jonathan Anderson (jonathan-anderson) wrote :

The fix works for me.

Changed in kino:
status: Triaged → Fix Released
Revision history for this message
riny (rinyfeller) wrote :

Here the fix works also... Thanks

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.