Description of problem:In Subtitles coposer I cant open new project. Nothing happed by pressing this button "New". Also I cant open video, but I think it's because I cant open new project. Dialog for existing project working, but I havn't any.
I think, it was my mistake. After some tryings its working now
Status: NEW => RESOLVEDResolution: (none) => INVALID
But still together with video seems, it isn't working
Status: RESOLVED => REOPENEDResolution: INVALID => (none)
hi, if you open the soft in the console, do you see some errors ?
Keywords: (none) => NEEDINFO
Simple message on UI: There was an error opening file /home/jaanus/out.ogv In console nothing more: [jaanus@localhost ~]$ subtitlecomposer Enchant dict for "en_US" 0x2bd20a0 Enchant dict for "en_US" 0x2c9b9c0 Enchant dict for "en_US" 0x2cab800
can you do: 1) enable the "core release debug" 2) install the following packages: subtitlecomposer-debug enchant-debug 3) run the following command from a terminal: gdb -q subtitlecomposer 2>&1 | tee debug.txt 4) then type "run" (if it ask for missing packages, install them) 5) when it segfaults, type "bt" 6) attach the file debug.txt to this bug thanks
CC: (none) => remco
Reporter, could you please reply to the previous question? If you won't reply within two weeks from now, I will have to close this bug as OLD. Thank you.
CC: (none) => marja11
Created attachment 1927 [details] from terminal
Created attachment 1928 [details] Error message in GUI
you didn't type "bt" ?
It doesn't seem to be a crash here. It just isn't able to support the ogv. There are two types off ogg video, one of which is proprietary and can't be supported. Does the program work if you use something like an xvid or mpg video instead?
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Reporter, Can you confirm this bug is still valid on Cauldron ? Roelof
CC: (none) => r.wobben
Since we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Status: REOPENED => RESOLVEDResolution: (none) => OLD