GSB several problems

slayeriq · 01-26-2009, 08:59 AM

Hello,

Im sorry for the vague title i used but i cant describe it better than that. I have a couple of problems on my GSB that i use in my slackware 12.2 installation.

I dont know much about gnome so i was hoping that you give me clear explanations.

These are the problems:

1. I cant mount my external hdd i can see it in system but if i open it i see the following error: "Error org.freedesktop.DBus.Error.AccessDenied.". I get this under my own account aswell under root.

2. I get "You are not allowed to access the system configuration." if i try to open something under system->Administration i get that error if im logged in as normal user also and under root.

3. I cant open the root terminal any account also root.

I think those problems are linked but i dont know how to solve it. I want to say that i searched the internet before i did this post and i couldn't find usefull info or i found things i dont know how to do.

I hope u guys can help me.

Thanks in advance,

SlayeriQ

indienick · 01-26-2009, 09:35 AM

For the first error, I am 99% certain the problem can be fixed by adding yourself to the "plugdev" group.

Unfortunately, I do not know what to suggest as for the second and third errors.

slayeriq · 01-26-2009, 09:43 AM

Quote:

Originally Posted by indienick

For the first error, I am 99% certain the problem can be fixed by adding yourself to the "plugdev" group.

Unfortunately, I do not know what to suggest as for the second and third errors.

Thank you for the response but how do i add my self to plugdev and doensnt that have any security problems with it ?

indienick · 01-26-2009, 09:47 AM

No - no security issues that I know of...

"plugdev", as far as I know, is a group that allow users access to devices managed by HAL (and thus other programs connected to HAL through Dbus).

To add your user to the "plugdev" group (or any other group for that matter), you can either crack open a text editor (as root, of course) and edit "/etc/group", or issue the following command (as root):

Code:

# usermod -aG plugdev your_user_name

slayeriq · 01-26-2009, 09:57 AM

Quote:

Originally Posted by indienick

No - no security issues that I know of...

"plugdev", as far as I know, is a group that allow users access to devices managed by HAL (and thus other programs connected to HAL through Dbus).

To add your user to the "plugdev" group (or any other group for that matter), you can either crack open a text editor (as root, of course) and edit "/etc/group", or issue the following command (as root):

Code:

# usermod -aG plugdev your_user_name

i did that logged out then logged in still same problem i only changed usermod -aG plugdev to
usermod -G plugdev

if i run id now i see this

uid=1000(slayeriq) gid=100(users) groups=11(floppy),17(audio),18(video),19(cdrom),100(users)

plugdev is not added

wadsworth · 01-26-2009, 10:10 AM

The command to see the groups you belong to is

Code:

groups

To add a user to a group, I've always used

Code:

gpasswd -a user_name group

indienick · 01-26-2009, 10:18 AM

Okay, then try the adding yourself to the /etc/group file with a text editor:

Code:

$ sudo gedit /etc/group
-OR-
$ gksu gedit /etc/group

slayeriq · 01-26-2009, 10:24 AM

Quote:

Originally Posted by wadsworth

The command to see the groups you belong to is

Code:

groups

To add a user to a group, I've always used

Code:

gpasswd -a user_name group

I think there is something wrong with the groups becouse this happend:

im now added to plugdev still i get the error i added a screenshot so u can see the error also i forgot to mention that the hdd is ntfs i dont know if thats the problem:

Click image for larger version

Name: Screenshot.png
Views: 29
Size: 17.5 KB
ID: 29

indienick · 01-26-2009, 10:30 AM

...it shouldn't be a problem, but make sure you have ntfs-3g installed, and that your /etc/fstab entry for /dev/hdd[n] is set to mount with the ntfs-3g driver (as opposed to the read-only ntfs driver).

Code:

---Checking that you have ntfs-3g installed...---
$ find /var/log/packages -iname ntfs-3g
...
...

Could you please post the contents of your /etc/fstab file, and wrap it in [code] tags?

wadsworth · 01-26-2009, 10:31 AM

Try logging out/back in (may need to do this for the group changes to take)

Don't have much experience with ntfs volumes, but I know ntfs-3g needs fuse.
Is /etc/rc.d/rc.fuse set executable and running?

slayeriq · 01-26-2009, 10:33 AM

Code:

/dev/sda4        swap             swap        defaults         0   0
/dev/sda3        /                ext3        defaults         1   1
/dev/sda1        /ntfs-c          ntfs-3g     umask=077        1   0
/dev/sda5        /ntfs-d          ntfs-3g     umask=077        1   0
#/dev/cdrom      /mnt/cdrom       auto        noauto,owner,ro  0   0
/dev/fd0         /mnt/floppy      auto        noauto,owner     0   0
devpts           /dev/pts         devpts      gid=5,mode=620   0   0
proc             /proc            proc        defaults         0   0
tmpfs            /dev/shm         tmpfs       defaults         0   0
shm            /dev/shm     tmpfs  defaults        0     0

also i logged out an and then logged back in and it didnt work.

i can acces ntfs-c and ntfs-d as root but i configured it that way at the install.

and fuse is running.

indienick · 01-26-2009, 10:40 AM

Try the following to the lines for sda{1,5}:

Code:

...
/dev/sda1   /ntfs-c   ntfs-3g   umask=077,users,rw   0   0
/dev/sda5   /ntfs-d   ntfs-3g   umask=077,users,rw   0   0
...

...then unmount, and re-mount them.

slayeriq · 01-26-2009, 10:43 AM

Quote:

Originally Posted by indienick

Try the following to the lines for sda{1,5}:

Code:

...
/dev/sda1   /ntfs-c   ntfs-3g   umask=077,users,rw   0   0
/dev/sda5   /ntfs-d   ntfs-3g   umask=077,users,rw   0   0
...

...then unmount, and re-mount them.

sorry for the question but they are already working why should i do that?

edit:

I found out how to solve it by accident if i change in

etc/dbus-1/system.d/system-tools-backends.conf

Code:

<!-- configuration modules can't be accessed directly... -->
<deny send_interface="org.freedesktop.SystemToolsBackends"/>
<deny send_interface="org.freedesktop.SystemToolsBackends.Platform"/>

i changed deny with allow for both and it worked but im concerned about security issues now.

gegechris99 · 01-26-2009, 10:57 AM

Hello,

GSB: Do you mean GNOME SlackBuild?

If so, which version of GSB did you install?

On GSB homepage, there is an annoucement about a new testing version and I'm not sure whether it's compatible with Slackware 12.2.

The following thread on their mailing list seems to indicate that Slackware 12.2 is not yet supported:

http://groups.google.com/group/gsb-u...7804b7f76b3e8d

I think it's preferable for you to stick with Slackware 12.1 and the latest stable GSB (if you really want to use GSB) and wait for the next stable GSB version compatible with 12.2.

Of course, you can help debug GSB -current but I think it would then be most appropriate to report your problems on GSB mailing lists.

slayeriq · 01-26-2009, 11:04 AM

Quote:

Originally Posted by gegechris99

Hello,

GSB: Do you mean GNOME SlackBuild?

If so, which version of GSB did you install?

On GSB homepage, there is an annoucement about a new testing version and I'm not sure whether it's compatible with Slackware 12.2.

The following thread on their mailing list seems to indicate that Slackware 12.2 is not yet supported:

http://groups.google.com/group/gsb-u...7804b7f76b3e8d

I think it's preferable for you to stick with Slackware 12.1 and the latest stable GSB (if you really want to use GSB) and wait for the next stable GSB version compatible with 12.2.

Of course, you can help debug GSB -current but I think it would then be most appropriate to report your problems on GSB mailing lists.

Thank you then i guess i have to uninstall gsb and return to kde until 12.2 is supported.

but its working fine for me now i only need to know if changing


<deny send_interface="org.freedesktop.SystemToolsBackends"/>
<deny send_interface="org.freedesktop.SystemToolsBackends.Platform"/>

to allow has security problems.