LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 11-07-2007, 11:31 AM   #16
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,559

Rep: Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351

I just tested the jasper build script - it's not the culprit.
Check the perms on each of your other packages created by checkinstall.
 
Old 11-07-2007, 11:50 AM   #17
mattydee
Member
 
Registered: Dec 2006
Location: Vancouver, BC
Distribution: Debian,Ubuntu,Slackware
Posts: 479

Original Poster
Rep: Reputation: 48
Quote:
Originally Posted by rworkman View Post
I just tested the jasper build script - it's not the culprit.
Check the perms on each of your other packages created by checkinstall.
Did that, and they are all good. I've never had a problem using checkinstall before. This is probably something on my end. Some kind of obscure configuration must be causing this.

As mentioned before my umask is 0002 for both my user and root.

I'll think about it...

Thanks for your help.
 
Old 11-07-2007, 11:52 AM   #18
mattydee
Member
 
Registered: Dec 2006
Location: Vancouver, BC
Distribution: Debian,Ubuntu,Slackware
Posts: 479

Original Poster
Rep: Reputation: 48
Quote:
Originally Posted by Alien Bob View Post
All of these packages - needed for digiKam - are available at http://www.slackware.com/~alien/slackbuilds/ (SlackBuilds too).

Eric
Thanks Eric.
That's good to know... would have saved me some compiling/time, but oh well.
 
Old 11-07-2007, 12:01 PM   #19
mattydee
Member
 
Registered: Dec 2006
Location: Vancouver, BC
Distribution: Debian,Ubuntu,Slackware
Posts: 479

Original Poster
Rep: Reputation: 48
UPdate

ok, so I noticed that my /tmp folder had SBo folder 700.

I rm -R the SBo folder, and built Jasper again using the slackbuild. All the perms were just fine, and the SBo folder was recreated with 755 perms.

Could the /tmp/SBo folder being 700 have been responsible? I wonder how it could have gotten those perms.
 
Old 11-07-2007, 02:08 PM   #20
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,559

Rep: Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351
Quote:
Originally Posted by mattydee View Post
ok, so I noticed that my /tmp folder had SBo folder 700.

I rm -R the SBo folder, and built Jasper again using the slackbuild. All the perms were just fine, and the SBo folder was recreated with 755 perms.

Could the /tmp/SBo folder being 700 have been responsible? I wonder how it could have gotten those perms.
No, that directory's permissions would not have influenced the permissions of any newly created directories inside it. However, I am curious as to how that directory came to have those permissions, as it would have been created originally with 0755 perms (unless your umask for root is set differently, but you've stated that such is not the case). I know of at least one way this could have happened, but it doesn't seem relevant to what you're experiencing...

If you have some spare time, do a fresh installation inside a virtual environment (qemu, vmware, virtualbox, whatever) and repeat all the customization you've done on this system. Check the perms on the relevant directories after *each* change you make, and perhaps you can find the culprit.
 
Old 11-07-2007, 05:07 PM   #21
mattydee
Member
 
Registered: Dec 2006
Location: Vancouver, BC
Distribution: Debian,Ubuntu,Slackware
Posts: 479

Original Poster
Rep: Reputation: 48
I've got it!

When I upon a terminal using F4 from Konqueror, and then su to execute the slackbuild, that's when the permissions get messed up.

If I open up a terminal "manually" (just running konsole), then this doesn't happen.

If I use F4:
Code:
bash-3.1#
As opposed to:
Code:
matty@slackmatt:~$
I've always wondered why this difference occurred, but it never seemed to matter anyways until now...
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Can't install pygtk datbenik Linux - Software 1 01-09-2006 09:46 AM
pygtk question bendeco13 Programming 1 04-13-2005 03:26 AM
PyGTK sailu_mvn Programming 1 02-28-2005 10:58 PM
Pygtk sailu_mvn Programming 0 02-28-2005 07:34 AM
pyGTK v. wxPython...? servnov Linux - General 1 01-09-2005 11:47 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:30 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration