Sunday February 28th 2021 - Update issue with packman inode mirror
There are issues with the inode mirror, please configure an alternative mirror. See http://packman.links2linux.org/mirrors
-
File Manager crashes under SU
I'm running Suse 11.0 v3.1.34 (kernel 2.6.25.5-1.1-default).
I was literally just using file manager as SU this morning. Now it is crashing every time. I get to the point where I enter my password, then it crashes with the following message:
The application konqueror crashed and caused the signal 11 (SIGSEGV):
[KCrash handler]
#5 0xb7f83ced in ?? () from /usr/lib/libkdeinit4_konqueror.so
#6 0xb7fa4e98 in ?? () from /usr/lib/libkdeinit4_konqueror.so
#7 0xb75b53fa in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#8 0xb75b5972 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#9 0xb3eda527 in ?? () from /usr/lib/kde4/dolphinpart.so
#10 0xb3edc493 in ?? () from /usr/lib/kde4/dolphinpart.so
#11 0xb75b53fa in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb75b5972 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#13 0xb3e925e7 in DolphinView::modeChanged ()
from /usr/lib/libdolphinprivate.so.4
#14 0xb3e939e6 in DolphinView::applyViewProperties ()
from /usr/lib/libdolphinprivate.so.4
#15 0xb3e95492 in DolphinView::updateView ()
from /usr/lib/libdolphinprivate.so.4
#16 0xb3e95558 in DolphinView::setUrl () from /usr/lib/libdolphinprivate.so.4
#17 0xb3edb351 in ?? () from /usr/lib/kde4/dolphinpart.so
#18 0xb7f530be in ?? () from /usr/lib/libkdeinit4_konqueror.so
#19 0xb7f928e3 in ?? () from /usr/lib/libkdeinit4_konqueror.so
#20 0xb7f5a433 in ?? () from /usr/lib/libkdeinit4_konqueror.so
#21 0xb7f591f7 in ?? () from /usr/lib/libkdeinit4_konqueror.so
#22 0xb7f58e4a in ?? () from /usr/lib/libkdeinit4_konqueror.so
#23 0xb7f5a62c in ?? () from /usr/lib/libkdeinit4_konqueror.so
#24 0xb7f5b651 in ?? () from /usr/lib/libkdeinit4_konqueror.so
#25 0xb7f5bc14 in ?? () from /usr/lib/libkdeinit4_konqueror.so
#26 0xb7f5eb28 in ?? () from /usr/lib/libkdeinit4_konqueror.so
#27 0xb7fc529b in kdemain () from /usr/lib/libkdeinit4_konqueror.so
#28 0x080487c2 in _start ()
#0 0xffffe430 in __kernel_vsyscall ()
Thanks
-
Re: File Manager crashes under SU
d-pabs wrote:
> I was literally just using file manager as SU this morning.
what were you using it for: moving, deleting, looking inside files?
what? where?
i notice this is your first post here....*welcome*...but, i wonder how
much experience you have with openSUSE and/or Linux...
and, i wonder what you moved, deleted or changed...
mostly, i wonder if you put it all back like it was before you started
doing whatever you did in the file manager as root if it wouldn't be
alright again..
--
palladium
-
Re: File Manager crashes under SU
I'm a Windows vet trying to learn Linux. I'm becoming familiar with more of the linux commands, but am still very slow at it so I tend to use the file manager. New to Suse and <6 months with Linux in general.
We have installed some custom software which should have zero impact on any system (root) files. The most recent item that I installed (in order to get my software to run properly) was qwt-4.2.0. To the best of my knowledge, i haven't deleted or moved any important OS files.
Does that help?
-
Re: File Manager crashes under SU
d-pabs wrote:
> I'm a Windows vet trying to learn Linux. I'm becoming familiar with
> more of the linux commands, but am still very slow at it so I tend to
> use the file manager. New to Suse and <6 months with Linux in general.
>
>
> We have installed some custom software which should have zero impact on
> any system (root) files. The most recent item that I installed (in
> order to get my software to run properly) was qwt-4.2.0. To the best of
> my knowledge, i haven't deleted or moved any important OS files.
>
> Does that help?
maybe..
i wonder, when you say you haven't moved or deleted any important OS
files, does that mean you know which ones are important/unimportant?
[i would recommend you consider every file outside of /home as
important and don't change them in anyway (including moving) until you
have a safe backup of the original AND a foolproof recovery (move
back) plan...btw, i've used linux most of 10 years and i STILL do it
that way]
and, i wonder how you installed qwt-4.2.0, because that doesn't
require the use of a file manager...(so, i still wonder what you were
doing with a file manager with root powers??)
have you yet discovered YaST or Zypper? they are the preferred (and
safest) way to install programs...as far as i know the qwt you mention
is available as an rpm and once you have it local just right click it,
select Actions > Install with YaST, give the root pass and sit on your
hands--no file manager required..
[if you downloaded a tar and compiled that qwt then you are working
under the broadly believed idea that installing linux software is
'difficult'...which is FUD]
if you have not yet you should read http://en.opensuse.org/Concepts
especially the part about software handling..
since we don't know what was munged i believe i'd begin by trying to
repair konqueror and dolphin...do that in YaST:
YaST > Software > Software Management > search for konqueror and in
place on the right side where you see a blue check mark next to
something related to konqueror, right click it change the symbol to
"Update" which should put all the right stuff back in the right place..
and, do the same (search, right click, etc) for dolphin..
hopefully that will solve those problems..
i guess there is an outside chance that something about the qwt you
installed messes with the Qt the system uses...but, i have no idea..
come back.
--
palladium
-
Re: File Manager crashes under SU
I've just noticed that other programs are not working either (either under root or user). I tried configuring my network card under "Network Settings". When I try to open the settings window, the computer thinks for a bit I can see it trying to open the network settings panel and then nothing happens. Same goes for "Install Updates". Not sure if this is a separate problem?
This is a brand new install on two brand new 1TB HDs, 1GB RAM, dual 2.8 GHz processor, on-board video card. I'm also noticing that it runs very slow: windows freezing up/laggy. I tried to edit xorg.conf as suggested by another post.
Code:
Option "AllowGLXWithComposite" "True"
Option "DisableGLXRootClipping" "True"
Option "RenderAccel" "True"
Option "AddARGBGLXVisuals" "True"
I don't notice much difference.
-
Re: File Manager crashes under SU
 Originally Posted by palladium
i wonder, when you say you haven't moved or deleted any important OS files, does that mean you know which ones are important/unimportant? [i would recommend you consider every file outside of /home as important and don't change them in anyway (including moving) until you have a safe backup of the original AND a foolproof recovery (move back) plan...btw, i've used linux most of 10 years and i STILL do it that way]
Right, I have not touched anything outside of user directory unless asked to. Most of our software packages require root access to set variables and the like, so I just logged in as root - which is why I was in the file manager as root. I am not used to making backups of files I edit, and will learn to do so quickly! What is a good way to recognize which should be backed up without going overboard? Anything outside of user directories?
 Originally Posted by palladium
and, i wonder how you installed qwt-4.2.0, because that doesn't
require the use of a file manager...(so, i still wonder what you were
doing with a file manager with root powers??)
I installed qwt under my user account with rpmbuild:
Code:
rpmbuild -ta qwt-4.2.0.tar.bz2
It then asked me to do the following:
Code:
cd /usr/src/packages/RPMS/i586
su
rpm -ivh qwt-4.2.0-1.i586
rpm -ivh qwt-devel-4.2.0-1.i586
I didn't get any sort of errors.
-
Re: File Manager crashes under SU
d-pabs wrote:
> I've just noticed that other programs are not working either (either
> under root or user).
well...i guess that means you have been logging into KDE as root, huh?
in my most humble opinion that is something which should never be
done, ever....my experience is that that always leads to a wide (very
wide) range of little problems that are so very difficult to track
down that it often requires one to start over, fresh format and install...
you can solicit other opinions (some say it is ok as long as you are
careful---but i don't know how to be that careful)...now i know the
model that MS used for years leads folks to come to Linux and wanna
wander around as root...my best advice is don't do that....also, many
MS vets don't like the idea that they can't do with _their_ machine
what they want, and then are frustrated when they do as they wish and
it all turns brown..
here is some stuff you probably ought to take the time to read:
http://docs.kde.org/stable/en/kdebas...uide/root.html
http://en.opensuse.org/SDB:Login_as_root
http://tinyurl.com/6ry6yd
http://tinyurl.com/8b9s6
you do as you wish...but, if you want stable (ROCK SOLID) then never
ever log into KDE, Gnome or any other *nix desktop environment as
root...and, never even open a file as root until you have a BACKUP
copy of it untouched (just opening a file in a file manager as root
can/will change file permissions..
oh, and you will find plenty of advice to get around permission
problems by using chown (or other) and "magic" codes like 777...do NOT
do it, until you have a valid backup and recovery plan..
> I tried configuring my network card under "Network
> Settings". When I try to open the settings window, the computer thinks
> for a bit I can see it trying to open the network settings panel and
> then nothing happens. Same goes for "Install Updates". Not sure if
> this is a separate problem?
did the network ever work?
during initial install were you connected to the local network or
thereby the internet? usually if you have an ethernet cable plugged in
and select DCHP it "just works" (*nix was networking before Windows
for Work Groups was 'innovated')
i suggest you repair all the damage you have done as su/root and then
revisit the network problem...
> This is a brand new install on two brand new 1TB HDs, 1GB RAM, dual 2.8
> GHz processor, on-board video card. I'm also noticing that it runs very
> slow: windows freezing up/laggy. I tried to edit xorg.conf as suggested
> by another post.
another post here? or?
i GUESS you installed KDE4? if so i highly recommend something else...
kde4 is one huge pile of bugs until you get to kde4.3, at least
and, all that "laggy" is more likely a slow graphics card, what kind
of graphic chip are you using?
--
palladium
-
Re: File Manager crashes under SU
d-pabs wrote:
> palladium;2048646 Wrote:
>> i wonder, when you say you haven't moved or deleted any important OS
>> files, does that mean you know which ones are important/unimportant? [i
>> would recommend you consider every file outside of /home as important
>> and don't change them in anyway (including moving) until you have a safe
>> backup of the original AND a foolproof recovery (move back) plan...btw,
>> i've used linux most of 10 years and i STILL do it that way]
>>
> Right, I have not touched anything outside of user directory unless
> asked to. Most of our software packages require root access to set
> variables and the like, so I just logged in as root - which is why I
> was in the file manager as root.
as mentioned, don't do that...instead log in as yourself and 'become
root' the correct way..
> I am not used to making backups of
> files I edit, and will learn to do so quickly! What is a good way to
> recognize which should be backed up without going overboard? Anything
> outside of user directories?
well, any file you change outside of your home directory can kill the
system, or some part of it..
and, for that matter, any file you change in the hidden directories of
the /home can kill or radically change the operation, looks etc of
that user....well, remember this: Linux is born a MULTI-user
environment....you can have hundreds of users and each user can use
Firefox, and mess with the settings s/he wants to see and all of those
will be saved in /home/[a user]/.mozilla, and that user can go into
that directory and throughly screw it up and never be able to use
Firefox again (until repaired) BUT all the other users on the system
can still use Firefox....BECAUSE the program itself is outside the
reach of ALL users, except root.
>
> palladium;2048646 Wrote:
>> and, i wonder how you installed qwt-4.2.0, because that doesn't
>> require the use of a file manager...(so, i still wonder what you were
>> doing with a file manager with root powers??)
>>
>
> I installed qwt under my user account with rpmbuild:
two things, always install system programs into the system!
well, i don't even know how you could have installed it into /home..
>
>
> Code:
> --------------------
>
> rpmbuild -ta qwt-4.2.0.tar.bz2
>
> --------------------
i've never used rpmbuild, ever....if i down load a source tarball i
unpack it and read the README which gives step by step instructions on
how to compile and install....no need to go through the process of
building an rpm..
but FIRST: i always search with YaST to see if there isn't a package
already in the openSUSE repos ready made for openSUSE..and just click
install done!
second, i'd look via http://software.opensuse.org/search, but i do NOT
recommend the "one click" install...rather opt to download and right
click Action > Install with YaST, as previously mentioned.
>
>
> It then asked me to do the following:
>
> Code:
> --------------------
>
> cd /usr/src/packages/RPMS/i586
> su
> rpm -ivh qwt-4.2.0-1.i586
> rpm -ivh qwt-devel-4.2.0-1.i586
>
> --------------------
>
>
> I didn't get any sort of errors.
then maybe you installed it ok....i wonder though why you use 4.2 when
5.2 is available..
--
palladium
-
Re: File Manager crashes under SU
Those system specs are for the computer I'm doing this install on. The graphics card is the generic, on-board card. i.e. no dedicated graphics card.
WRT running the most current updates/software, I would love to be doing that. However, I am told by my higher ups (i.e. well-seasoned Linux users) that the software they've developed on old OS versions of linux will not properly compile on newer versions OR it is possible for our software to not work due to differences between, say, Suse 9 and Suse 11 or qt3 vs qt4, etc.
As per the network problem, I think I have it sorted out. I managed to get yast2 working (again - did a "zypper rm" and "zypper in") and set everything up using the GUI. I have 2 cards, one for internet (DCHP) and one for local hardware (static). I was having troubles with the static one.
Thanks for your comments and assistance.
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|