| Summary: | lokalize crashes | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Oliver Burger <oliver.bgr> |
| Component: | RPM Packages | Assignee: | John Balcaen <balcaen.john> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | anssi.hannula, lmenut |
| Version: | Cauldron | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | kdesdk4 | CVE: | |
| Status comment: | |||
| Attachments: |
lokalize backtrace
Real backtrace now |
||
|
Manuel Hiebel
2012-03-08 12:25:50 CET
Attachment 1695 mime type:
application/octet-stream =>
text/plain I can't reproduce in my VM (download .po, open, edit, save.) Any ideas guys ? CC:
(none) =>
lmenut I can try in a vm later. @assignment: according to https://wiki.mageia.org/en/Absent mikala is absent for some time. Perhaps reassign to another KDE packager? (In reply to comment #2) > @assignment: according to https://wiki.mageia.org/en/Absent mikala is absent > for some time. Perhaps reassign to another KDE packager? That's why lmenut is in CC (I don't know other people working in kde*4) but yes we can do the apposite. There are no backtraces in the attachment #1695 [details]. Backtrace is performed via "bt" or "bt full" commands in GDB, or "thread apply all bt" or "thread apply all bt full" in case of multithreaded applications. Or just copypaste the trace from the KDE Crash dialog.CC:
(none) =>
anssi.hannula Sorry for taking the wrong word... That happens, when not being a native speaker... Oliver (In reply to comment #0) > Created attachment 1695 [details] > lokalize backtrace > > When trying to edit anything in lokalize, it crashes. I attach the backtrace. You opened this bug report the March 7, 2012. At this date we were in the middle of update to kde 4.8.1; lokalize 4.8.1 was built the March 9th. Can you reproduce this crash with a fully updated system to kde 4.8.1? (I can't reproduce the crash on my system) Created attachment 1714 [details]
Real backtrace now
Still the same.
lokalize dies as soon as I try to edit a po file.
(I took de.po from drakconf, that is in our svn). According to "msgfmt -c" there are no syntax errors in the po file.
Attachment 1695 is obsolete:
0 =>
1 Which 'Default language' do you have in Systemsettings/Locale/Spell Checker? "German" only or "German (Germany)"? If you have "German" only, can you try to select "German (Germany)", and re-try lokalize. That did the trick... Still, it's a bug that should be solved, I think. (In reply to comment #9) > That did the trick... good, you can use lokalise. > > Still, it's a bug that should be solved, I think. Yes, in fact there are 2 bugs: - lokalize crashes when the default dictionary in systemsettings is not available, - systemsettings shouldn't set by default a dictionary not available on the system. Can you report upstream at least the first bug, with its condition and the backtrace. With hunspell dictionaries there isn't de.[dic,aff] (= German), there are only de_DE.[dic,aff] (= German (Germany)), de_BE.[dic,aff], ..., so "German" doesn't fit to a hunspell dictionary, only "German (...)" fit with an existing hunspell dictionary. recently, there were some changes regarding spell checking in sonnet and in lokalize, cf.: https://bugs.kde.org/show_bug.cgi?id=256896 http://git.reviewboard.kde.org/r/103729/ 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 Keywords:
(none) =>
NEEDINFO Seems to be fixed. Status:
NEW =>
RESOLVED |
Created attachment 1695 [details] lokalize backtrace When trying to edit anything in lokalize, it crashes. I attach the backtrace.