I was away for a few days and i did not noticed the issue until now. I`m using kde 4.7.1 and this morning when starting kwrite i get the following message:
*“A kde text editor component could not be found. Please check you kde installation”. *
The weird part is that i have kwrite installed creatura@creation:~> whereis kwrite
kwrite: /usr/bin/kwrite /usr/bin/X11/kwrite
After this the crash handler from KDE shows and here is the output i get from backtrace:
Application: KWrite (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#6 0x00007fd48ee935e0 in KTextEditor::Editor::setSimpleMode(bool) () from /usr/lib64/libktexteditor.so.4
#7 0x00007fd48f1039e0 in KWriteApp::KWriteApp(KCmdLineArgs*) () from /usr/lib64/libkdeinit4_kwrite.so
#8 0x00007fd48f1003c9 in kdemain () from /usr/lib64/libkdeinit4_kwrite.so
#9 0x0000000000407279 in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) ()
#10 0x0000000000407dfd in handle_launcher_request(int, char const*) ()
#11 0x000000000040859a in handle_requests(int) ()
#12 0x00000000004091f0 in main ()
Try to downgrade to version 4.6.5 still the issue is present. What can i do to solve it ?
Yes, I agree. Personally, I stick to the actual release. I can wait for the next release for a new version. That results in a more stable system.
However, I do participate in testing. I currently have 12.1 M5 installed on a test system. That’s bleeding edge too, but it is only a test install where I expect stuff to break.
So I booted up 12.1 M5, and checked kwrite. It seems to work just fine. It is KDE 4.7.1. So should be good to go when 12.1 is officially released.
I’ll add that there is other broken stuff in 12.1 M5.
Well i did take some steps back to kde 4.6.5 and kwrite is working again…
Maybe you are right nrickert; well no harm done to my OS by using KDE from a non-Tumbleweed repo. I belive i will follow your model nrickert and use vbox for testing new versions of apps. Do you think that 11.2 M5 is a good point to start or should i just wait for the Beta ?
> On 09/25/2011 04:26 PM, creatura85 wrote:
>>
>> Well i did take some steps back to kde 4.6.5 and kwrite is working
>> again…
>
> please log the bug you found: http://tinyurl.com/nzhq7j
>
> it is, after all, testing software…
>
i’m not sure it’s a bug really. he (OP) is the only one who’s encountered
this behavior, and there’s up- and downgrading between repos involved.
moreover, in one of his latest posts the word “tumbleweed” was mentioned.
no point filing a bug if if different / incompatible repos are involved.
> i’m not sure it’s a bug really. he (OP) is the only one who’s
> encountered this behavior, and there’s up- and downgrading between repos
> involved. moreover, in one of his latest posts the word “tumbleweed” was
> mentioned. no point filing a bug if if different / incompatible repos
> are involved.
good point…
–
DD
openSUSE®, the “German Automobiles” of operating systems
Just for the record, I have 11.4_x64 and KDE4.7.1 installed and kwrite runs, just fine, both from the CLI and from within Dolphin (right-clicking to open a text file).
I HAVE noticed on several occasions after doing a Yast Software Management update (I use Repositories-@System-Package-All in this list update if newer) that some KDE apps fail in strange ways. Logging out and logging back in (presumably to restart X) almost always clears up the issues.
This was particularly noticeable as 4.7.1 “dribbled” out with numerous daily updates, but has quieted down recently.
Well i did a netinstall last evening and the factory state is still M5. Now i have to read, i guess, how can i get involved in bug squashing.
phanisvara: you are half-right; Tumbleweed started with 11.4 as a base, so you cant say that they are that different. For e.g. there are no repos for Tumbleweed regarding filesystem, perl, php, webcam drivers, wine, mono and so on, and that makes me to use 11.4 repo`s to get the packages i need. In other words Tumbleweed is not yet mature.