1 |
dhk wrote: |
2 |
> Saphirus Sage wrote: |
3 |
>> dhk wrote: |
4 |
>>> I originally posted this question to the kino group. The chain of |
5 |
>>> emails is below. |
6 |
>>> |
7 |
>>> The problem is that kino crashes when opening a file, clicking on a |
8 |
>>> folder that has a video file in it, or when passing it in on the |
9 |
>>> command line. I removed and reinstalled kino, but the same thing |
10 |
>>> happens. I compiled the source manually and the problem wasn't |
11 |
>>> there. Now I think it has something to do with the Gentoo environment |
12 |
>>> or the ebuild. |
13 |
>>> |
14 |
>>> One thing I noticed on my system is that in |
15 |
>>> /usr/portage/media-video/kino there are two ebuilds a 1.3.1 and a |
16 |
>>> 1.3.3 I have 1.3.1 installed. The diffs to these files are as follows. |
17 |
>>> |
18 |
>>> $ diff kino-1.3.1.ebuild kino-1.3.3.ebuild |
19 |
>>> 1c1 |
20 |
>>> < # Copyright 1999-2008 Gentoo Foundation |
21 |
>>> --- |
22 |
>>>> # Copyright 1999-2009 Gentoo Foundation |
23 |
>>> 3c3 |
24 |
>>> < # $Header: |
25 |
>>> /var/cvsroot/gentoo-x86/media-video/kino/kino-1.3.1.ebuild,v 1.7 |
26 |
>>> 2008/12/21 14:44:31 nixnut Exp $ |
27 |
>>> --- |
28 |
>>>> # $Header: |
29 |
>>> /var/cvsroot/gentoo-x86/media-video/kino/kino-1.3.3.ebuild,v 1.1 |
30 |
>>> 2009/03/29 13:39:42 patrick Exp $ |
31 |
>>> 11c11 |
32 |
>>> < KEYWORDS="amd64 ppc ppc64 sparc x86" |
33 |
>>> --- |
34 |
>>>> KEYWORDS="~amd64 ~ppc ~ppc64 ~sparc ~x86" |
35 |
>>> 29a30 |
36 |
>>>> dev-util/intltool |
37 |
>>> I'm not sure if the 1.3.3 file is causing a problem somehow. |
38 |
>>> |
39 |
>>> Any ideas? |
40 |
>>> |
41 |
>>> Thanks, |
42 |
>>> dhk |
43 |
>>> |
44 |
>>> Dan Dennedy wrote: |
45 |
>>>> On Wed, May 13, 2009 at 4:54 AM, dhk <dhkuhl@×××××××××.net> wrote: |
46 |
>>>>> Dan Dennedy wrote: |
47 |
>>>>>> On Tue, May 12, 2009 at 3:08 AM, dhk <dhkuhl@×××××××××.net> wrote: |
48 |
>>>>>>> dhk wrote: |
49 |
>>>>>>>> Carl Karsten wrote: |
50 |
>>>>>>>>> On Sat, May 9, 2009 at 5:27 AM, dhk <dhkuhl@×××××××××.net> wrote: |
51 |
>>>>>>>>>> I don't edit video very often so I don't know exactly when this |
52 |
>>>>>>>>>> problem |
53 |
>>>>>>>>>> started. |
54 |
>>>>>>>>>> |
55 |
>>>>>>>>>> Whenever I try to open a file kino crashes. It starts fine, |
56 |
>>>>>>>>>> but as |
57 |
>>>>>>>>>> soon |
58 |
>>>>>>>>>> as I try to open a .kino, .dv and other type files it crashes. |
59 |
>>>>>>>>>> When |
60 |
>>>>>>>>>> I'm |
61 |
>>>>>>>>>> in the kino gui the crash occurs when I click on the folder |
62 |
>>>>>>>>>> that has |
63 |
>>>>>>>>>> the |
64 |
>>>>>>>>>> .kino file. On the command line it crashes when I pass the |
65 |
>>>>>>>>>> file in as |
66 |
>>>>>>>>>> a |
67 |
>>>>>>>>>> parameter. |
68 |
>>>>>> More than likely the libdv or libavcodec libraries changed somehow |
69 |
>>>>>> and |
70 |
>>>>>> Kino needs to be rebuilt. If you are going to rebuild it, see if |
71 |
>>>>>> there |
72 |
>>>>>> is a v1.3.3, the latest release, available - it will clear up many of |
73 |
>>>>>> those GTK+ warnings. |
74 |
>>>>>> |
75 |
>>>>>>>>> post the command line and resulting output. |
76 |
>>>>>>>>> |
77 |
>>>>>> [...] |
78 |
>>>>>>>> /Video/Capture/MomAndDad50thAnniversary $ kino take1.kino |
79 |
>>>>>> [...] |
80 |
>>>>>>>> Kino experienced a segmentation fault. |
81 |
>>>>>> $ gdb kino |
82 |
>>>>>> (gdb) run take1.kino |
83 |
>>>>>> ...segfault |
84 |
>>>>>> (gdb) where |
85 |
>>>>>> |
86 |
>>>>>> send the output. |
87 |
>>>>>> |
88 |
>>>>> I think the problem is in the environment or setup somewhere. I |
89 |
>>>>> don't have |
90 |
>>>>> the answer, but I think I'm getting closer. So please bear with me |
91 |
>>>>> as I |
92 |
>>>>> explain. |
93 |
>>>>> |
94 |
>>>>> First) This is kino version 1.3.1 I'm working with. There isn't any |
95 |
>>>>> libavcodec package in the portage tree as far as I've seen, but |
96 |
>>>>> there is a |
97 |
>>>>> libavc1394 version 0.5.3. The highest version of lbdv is 1.0.0-r2. |
98 |
>>>> I do not know the gentoo package names; libavcodec is a part of FFmeg. |
99 |
>>>> |
100 |
>>>> $ ldd $(which kino) |
101 |
>>>> and see if it is linked to a libavcodec |
102 |
>>>> |
103 |
>>>>> Second) I tried compiling the source so I could run the program |
104 |
>>>>> through the |
105 |
>>>>> gdb debugger. When I ran the program without gdb it runs fine, but |
106 |
>>>>> the same |
107 |
>>>>> problem exists with the crashing. However, when running the program |
108 |
>>>>> through |
109 |
>>>>> gdb it SIGSEGV because it can't find the magick.glade and kino.glade |
110 |
>>>>> file. |
111 |
>>>>> The program was looking for them in /usr/local/share/kino/ and that |
112 |
>>>>> path |
113 |
>>>>> and the file don't exist. |
114 |
>>>> You have to install it to put resources in the expected location. |
115 |
>>>> |
116 |
>>>>> Third) Then I did a make clean and ran configure with my own |
117 |
>>>>> --prefix and |
118 |
>>>>> copied the two .glade file to that location. I redid the steps above |
119 |
>>>>> running kino with and without gdb and to my surprise everything |
120 |
>>>>> worked. |
121 |
>>>>> Except for some missing icons , which is understandable since I |
122 |
>>>>> change the |
123 |
>>>>> --prefix, everything I tested was functional. I could open files |
124 |
>>>>> and play |
125 |
>>>>> them. |
126 |
>>>> Like I said, Kino needed to be rebuilt for some reason or another. Or, |
127 |
>>>> something special about the gentoo build is triggering a bug. |
128 |
>>>> |
129 |
>>>>> So now is the problem with the way kino is getting installed on |
130 |
>>>>> Gentoo amd64 |
131 |
>>>>> or am I picking up older files from previous versions that don't |
132 |
>>>>> work? Any |
133 |
>>>>> ideas? I think we're getting closer? |
134 |
>>>> Remove it entirely, re-emerge it. If the problem remains, file a bug |
135 |
>>>> with gentoo. If there is a patch that belongs upstream, someone should |
136 |
>>>> attach it to the Kino SourceForge tracker. Kino is no longer actively |
137 |
>>>> maintained, so someone needs to step up if they need it to work for |
138 |
>>>> them because no one else is going out of there way to resolve issues |
139 |
>>>> for various environments. |
140 |
>>>> |
141 |
>>> |
142 |
>> I've only been using Kino for a short time, but 1.3.3 has been perfectly |
143 |
>> find on my amd64 system. Consider unmasking it and installing that |
144 |
>> version, see if that gets around whatever the problem is. |
145 |
>> |
146 |
>> |
147 |
> |
148 |
> I don't see a version 1.3.3 on my amd64, but I seem to have an ebuild |
149 |
> for it. I don't think I have it masked either. All I see is |
150 |
> media-video/kino gstreamer dvdr sox in the package.use file. |
151 |
> |
152 |
> # emerge --search kino |
153 |
> !!! CONFIG_PROTECT is emptySearching... |
154 |
> [ Results for search key : kino ] |
155 |
> [ Applications found : 1 ] |
156 |
> |
157 |
> * media-video/kino |
158 |
> Latest version available: 1.3.1 |
159 |
> Latest version installed: 1.3.1 |
160 |
> Size of files: 10,804 kB |
161 |
> Homepage: http://www.kinodv.org/ |
162 |
> Description: Kino is a non-linear DV editor for GNU/Linux |
163 |
> License: GPL-2 |
164 |
> |
165 |
> |
166 |
> |
167 |
Never mind I found it. Version 1.3.3 was masked. I had to add |
168 |
media-video/kino ~amd64 to the package.keywords file. Now the problem |
169 |
is gone. Thanks all. |