This does not happen every time I try to post a message from Knode on KDE4.1
but more often than not. As soon as I try to post the message, Kontact
vanishes. I’ve re-installed the thing many times, trying different ways of
getting my folders from KDE3 to KDE4. The last time, I thought I’d forget
the KDE3 stuff and delete .kde4/share/apps/knode and config/knoderc. I set
up one newsgroup, composed a test message, hit “send” and that was the last
I saw of Kontact.
I did see one error message instead of a crash when it said it couldn’t
write to the file “support-forums.novell.com”.
Anyone got this working, and if so, how?
–
Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy
Now open new post editor:
gpd@linux-ycg1:~> Object::connect: No such signal
KNComposerEditor::sigDragEnterEvent(QDragEnterEvent*)
Object::connect: (receiver name: ‘composerWindow’)
Object::connect: No such signal KNComposerEditor::sigDropEvent(QDropEvent*)
Object::connect: (receiver name: ‘composerWindow’)
Now try to post:
Enchant dict for “en_GB” 0x8717d60
knode(4411): KNFolder::saveArticles() : cannot open mbox-file!
Message said it didn’t have correct permission.
==============================
I looked in share/apps/knode/folders/ to see what the permissions were for
the mbox files and found there weren’t any. There were just the info files
for drafts_1, outbox_2, root_0, and sent_3. There were also no idx files.
I’m not sure where this gets me because, in earlier tests, these files would
have existed because I copied the KDE3 versions. Odd.
–
Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy
When I upgraded from 10.2 to 10.3 I had a problem where the SSL
stuff was screwy. Had to purge some stuff from the .kde/share/apps/knode
folder before it would work properly. It exhibited the same behavior though
as yours. As soon as you clicked on anything crash to desktop. Since you
mention it cannot write to support-forums.novell.com it sounds like a
permissions issue. You can take a peek at them since you have already
located where it all resides. You can also launch the app with increased
permissions and see if it goes away. At least you can narrow down the
possibilities, I’d not recommend running it with extended privileges for
long, just for troubleshooting. Then maybe nose around and see if you can
locate the problem.
> When I upgraded from 10.2 to 10.3 I had a problem where the SSL
> stuff was screwy. Had to purge some stuff from the .kde/share/apps/knode
> folder before it would work properly. It exhibited the same behavior
> though
> as yours. As soon as you clicked on anything crash to desktop. Since you
> mention it cannot write to support-forums.novell.com it sounds like a
> permissions issue. You can take a peek at them since you have already
> located where it all resides. You can also launch the app with increased
> permissions and see if it goes away. At least you can narrow down the
> possibilities, I’d not recommend running it with extended privileges for
> long, just for troubleshooting. Then maybe nose around and see if you can
> locate the problem.
I’ve since set up a new user and set up knode from scratch so there should
have been no conflicts over permissions. It still fell over in a heap. I
forgot to run from command so didn’t see the errors. The file it was having
trouble writing to did not exist so that suggests it could not create it.
As it has been said that KDE forums have more on this, I’d better have a
look there.
–
Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy
Now open new post editor:
gpd@linux-ycg1:~> Object::connect: No such signal
KNComposerEditor::sigDragEnterEvent(QDragEnterEvent*)
Object::connect: (receiver name: ‘composerWindow’)
Object::connect: No such signal KNComposerEditor::sigDropEvent(QDropEvent*)
Object::connect: (receiver name: ‘composerWindow’)
Now try to post:
Enchant dict for “en_GB” 0x8717d60
knode(4411): KNFolder::saveArticles() : cannot open mbox-file!
Message said it didn’t have correct permission.
==============================
I looked in share/apps/knode/folders/ to see what the permissions were for
the mbox files and found there weren’t any. There were just the info files
for drafts_1, outbox_2, root_0, and sent_3. There were also no idx files.
I’m not sure where this gets me because, in earlier tests, these files would
have existed because I copied the KDE3 versions. Odd.
–
Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy
When I upgraded from 10.2 to 10.3 I had a problem where the SSL
stuff was screwy. Had to purge some stuff from the .kde/share/apps/knode
folder before it would work properly. It exhibited the same behavior though
as yours. As soon as you clicked on anything crash to desktop. Since you
mention it cannot write to support-forums.novell.com it sounds like a
permissions issue. You can take a peek at them since you have already
located where it all resides. You can also launch the app with increased
permissions and see if it goes away. At least you can narrow down the
possibilities, I’d not recommend running it with extended privileges for
long, just for troubleshooting. Then maybe nose around and see if you can
locate the problem.
> When I upgraded from 10.2 to 10.3 I had a problem where the SSL
> stuff was screwy. Had to purge some stuff from the .kde/share/apps/knode
> folder before it would work properly. It exhibited the same behavior
> though
> as yours. As soon as you clicked on anything crash to desktop. Since you
> mention it cannot write to support-forums.novell.com it sounds like a
> permissions issue. You can take a peek at them since you have already
> located where it all resides. You can also launch the app with increased
> permissions and see if it goes away. At least you can narrow down the
> possibilities, I’d not recommend running it with extended privileges for
> long, just for troubleshooting. Then maybe nose around and see if you can
> locate the problem.
I’ve since set up a new user and set up knode from scratch so there should
have been no conflicts over permissions. It still fell over in a heap. I
forgot to run from command so didn’t see the errors. The file it was having
trouble writing to did not exist so that suggests it could not create it.
As it has been said that KDE forums have more on this, I’d better have a
look there.
–
Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy
:setAddress: Invalid