SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Upgraded and everything appeared to be running okay.
And then out of the blue while browsing in Firefox I got a kernel oops.
I'm just not quite sure how to report or if more is needed than the following.
Also, something I had not noticed before as I rarely use Calligra.
I created a simple test file in both Calligrawords and Calligrasheets.
Saved the file and attempted to open them and got the following message:
The manifest file seems to be corrupted. The document could not be opened.
Quote:
Could not open /home/alpha/Documetns/test3calligrawords.odt
Reason: Not a valid Calligra file: /home/alpha/Documetns/test3calligrawords.odt
Is anybody else seeing this problem with KTimeTracker? On start there is an error box with "Could not create the KTimeTracker part."
According to post #19 and #21 here https://bugs.launchpad.net/ubuntu/+s...im/+bug/864975, a rebuild of /usr/lib/kde4/ktimetrackerpart.so with altered compile options may be a fix.
Thanks for your hard work guys! Just got done upgrading kde to 4.8 and i ran into a little snag... after I re-booted and typed in startx to go to kde I was thrown out of it.. Seems like kde won't start for me. Have to use xfce for now. Any ideas as to what I might have done to kde?
try to rename .kde to another name and give another shot of startx
by the way, have you make sure that you have upgraded/installed all the new dependencies of KDE 4.8 and fully upgraded to -Current?
As far as I know I am fully upgraded to current, I did a fresh install yesterday. Will upgrading via slackware current pull in all of the dependencies, or will I still need to add those separately? I'm getting a message "cannot contact kdeinit4". I did rename .kde, but that did not seem to help.
in my opinion the Exec entry for konsole in konsole.dektop
should not be
Exec=konsole -e $SHELL -l
but only
Exec=konsole
I think Exec=konsole -e $SHELL -l m
makes the login shell (bash) ignore .profile and similars in ~/
and the first tab in konsole will not contain your configured environment
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.