[DONE] Beta 2 dbus SYSTEM SETTINGS troubles

[zxr250cc]

ERROR 1

I am trying to set the LOGIN SCREEN settings so that I show no users when you come to the log in page. I am not trying to have auto log in, I just want the log in page to show no users at all. When I try to save that setting I get this read out from the program after it fails to save my setting:

Unable to authenticate/execute the action: DBus Backend error: could not contact the helper. Connection error: Failed to execute program /usr/libexec/dbus-1/dbus-daemon-launch-helper: Success. Message error: Failed to execute program /usr/libexec/dbus-1/dbus-daemon-launch-helper: Success (code 7)


ERROR 2

I have also set the screen so that the log in screen should NOT pop up to lock the screen and ask me to unlock the screen if the power saving function dims the screen. I have set that feature OFF twice and it still comes on when the screen dims. Can I delete this from software if I cannot get it to function correctly?

cheers

[doktor5000]

Which DM are you using and what configuration changes did you actually do?

[zxr250cc]

LOGIN SCREEN - SYSTEM SETTINGS

I am using the current beta 2 download with KDE. As I described, I tried to have the log in screen show without users listed. I got the error code mentioned. I also tried to have the auto log in feature (turned on for some reason) turned off and it also complained in the same way as the first error.

ERROR 2 result:
Unable to authenticate/execute the action: DBus Backend error: could not contact the helper. Connection error: Could not get owner of name 'org.kde.kcontrol.kcmkdm': no such name. Message error: Failed to execute program /usr/libexec/dbus-1/dbus-daemon-launch-helper: Success (code 7)

I am wondering if dbus is not installed properly somehow. I have never had an error like this with the LOGIN SCREEN settings before. I manually downloaded a lot of dbus related program after this problem started but it has not helped.

???

EDIT

I have tried this as a user and as root with the same error results.

??

cheers

[doktor5000]

Please post the complete command that you used. The dbus errors tell me that it wasn't launched from a complete environement,
e.g. doing an su and then trying to run it, this will not work for most graphical programs.

What should definitely work, is to run as your normal user via kdesu:

Code: Select all

/usr/lib64/kde4/libexec/kdesu systemsettings

kdesu can be used also for all other graphical applications, it's the analogon to sudo/su.
If you use it more often, you may want to symlink it to /usr/bin so you can use it via Alt+F2 from within krunner.

[zxr250cc]

Hi,

I copied the error script out of the pop up buttons. I was not using a command line, I was using KDE and had that reaction when pressing the save button to save my choices for not showing user names on the log in screen and for not having auto log in.

cheers

[doktor5000]

Okay, what about the proposals i gave you, did they work?

[zxr250cc]

I did not try the kdesu command, sorry. I got so frustrated that the program was doing weird things that I wiped the drive. It began to spontaneously have the desktop panel disappear and not come back. It was so screwy it was beyond being useful even for testing. I will try it again tomorrow with another install.

I have never tried doing any kdesu commands. Where can I find documentation on those?

thanks for the attempt to help me...

cheers

[zxr250cc]

Hi all,

I just tried to make the screen settings with the disk running LIVE and have the same messages I had when it was installed. I think I need to download another copy of the LIVE disk as this may have some bugs in it.

cheers

[pete910]

Well, same problem as above on mine as well. That's with systemsettings and now it is preventing Steam from starting.

It is odd as a dbus call for say Amarok to start playing or what ever works fine!

Have done a journelctl -u dbus and its showing the following.

Code: Select all

Feb 06 17:09:01 localhost dbus-daemon[997]: dbus[997]: [system] Activated service 'org.kde.powerdevil.backlighthelper' failed: Failed to execute program /usr/libexec/dbus-1/dbus-daemon-launch-helper: Success
Feb 06 17:09:01 localhost dbus[997]: [system] Activated service 'org.kde.powerdevil.backlighthelper' failed: Failed to execute program /usr/libexec/dbus-1/dbus-daemon-launch-helper: Success
Feb 06 17:09:01 localhost dbus[997]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Feb 06 17:09:01 localhost dbus-daemon[997]: dbus[997]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Feb 06 17:09:01 localhost dbus-daemon[997]: dbus[997]: [system] Activated service 'org.kde.powerdevil.backlighthelper' failed: Failed to execute program /usr/libexec/dbus-1/dbus-daemon-launch-helper: Success
Feb 06 17:09:01 localhost dbus[997]: [system] Activated service 'org.kde.powerdevil.backlighthelper' failed: Failed to execute program /usr/libexec/dbus-1/dbus-daemon-launch-helper: Success
Feb 06 17:09:10 localhost dbus-daemon[997]: dbus[997]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Feb 06 17:09:10 localhost dbus[997]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Feb 06 17:09:10 localhost dbus-daemon[997]: dbus[997]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Feb 06 17:09:10 localhost dbus[997]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Feb 06 17:13:44 localhost dbus-daemon[997]: dbus[997]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Feb 06 17:13:44 localhost dbus[997]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Feb 06 17:13:44 localhost dbus-daemon[997]: dbus[997]: [system] Activated service 'org.kde.powerdevil.backlighthelper' failed: Failed to execute program /usr/libexec/dbus-1/dbus-daemon-launch-helper: Success
Feb 06 17:13:44 localhost dbus-daemon[997]: dbus[997]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Feb 06 17:13:44 localhost dbus[997]: [system] Activated service 'org.kde.powerdevil.backlighthelper' failed: Failed to execute program /usr/libexec/dbus-1/dbus-daemon-launch-helper: Success
Feb 06 17:13:44 localhost dbus[997]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Feb 06 17:13:44 localhost dbus[997]: [system] Activated service 'org.kde.powerdevil.backlighthelper' failed: Failed to execute program /usr/libexec/dbus-1/dbus-daemon-launch-helper: Success
Feb 06 17:13:44 localhost dbus-daemon[997]: dbus[997]: [system] Activated service 'org.kde.powerdevil.backlighthelper' failed: Failed to execute program /usr/libexec/dbus-1/dbus-daemon-launch-helper: Success
Feb 06 17:13:44 localhost dbus-daemon[997]: dbus[997]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Feb 06 17:13:44 localhost dbus[997]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Feb 06 17:13:44 localhost dbus-daemon[997]: dbus[997]: [system] Activated service 'org.kde.powerdevil.backlighthelper' failed: Failed to execute program /usr/libexec/dbus-1/dbus-daemon-launch-helper: Success

its full of above error.

When trying Steam it has the following,

Code: Select all

[pete@com1 ~]$ steam
Traceback (most recent call last):
  File "/usr/bin/steamdeps", line 309, in <module>
    status = main( *sys.argv[1:] )
  File "/usr/bin/steamdeps", line 268, in main
    process = subprocess.Popen( ['dpkg', '-l'] + list( packages.keys() ), stdout=subprocess.PIPE, stderr=subprocess.PIPE )
  File "/usr/lib64/python2.7/subprocess.py", line 679, in __init__
    errread, errwrite)
  File "/usr/lib64/python2.7/subprocess.py", line 1249, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory
Running Steam on mageia 3 64-bit
STEAM_RUNTIME is enabled automatically
Installing breakpad exception handler for appid(steam)/version(1360379549_client)
Looks like steam didn't shutdown cleanly, scheduling immediate update check
Installing breakpad exception handler for appid(steam)/version(1360379549_client)
Installing breakpad exception handler for appid(steam)/version(1360379549_client)
unlinked 0 orphaned pipes
removing stale semaphore last operated on by process 10396 with name 0eBlobRegistryMutex_D5C3E185A7F1E57F8A2A3D2FF4843E79
removing stale semaphore last operated on by process 10396 with name 0eBlobRegistrySignal_D5C3E185A7F1E57F8A2A3D2FF4843E79
removing stale semaphore last operated on by process 10396 with name 0emSteamEngineInstance
removing stale semaphore last operated on by process 10396 with name 0eSteamEngineLock

(steam:11646): Gtk-WARNING **: Unable to locate theme engine in module_path: "oxygen-gtk",

(steam:11646): Gtk-WARNING **: Unable to locate theme engine in module_path: "oxygen-gtk",
Installing breakpad exception handler for appid(steam)/version(1360379549_client)
[0209/175302:ERROR:object_proxy.cc(239)] Failed to call method: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files
[0209/175302:WARNING:proxy_service.cc(646)] PAC support disabled because there is no system implementation
Installing breakpad exception handler for appid(steam)/version(1360379549_client)
Installing breakpad exception handler for appid(steam)/version(1360379549_client)
Installing breakpad exception handler for appid(steam)/version(1360379549_client)
Uploading dump (in-process) [proxy '']
/tmp/dumps/crash_20130209175302_1.dmp
success = yes
response:  CrashID=bp-343977ee-1a1b-4e2a-b22b-d50c62130209
/home/pete/Steam/steam.sh: line 561: 11646 Segmentation fault      $STEAM_DEBUGGER "$STEAMROOT/$PLATFORM/$STEAMEXE" "$@"

Seems to be a dbus/(permissions?) problem.

Pete

[pete910]

Found a part solution on my system, seems it was a permissions problem for steam

I changed dbus-daemon-launch-helper perms. to 752.

Code: Select all

chmod 752 /usr/libexec/dbus-1/dbus-daemon-launch-helper

No difference to the main problem(systemsettings) though

Pete.

[pete910]

Solved all the problems now

Must be a bad package install or something, reinstalled all the dbus rpms. after reboot all works fine.

Code: Select all

urpmi --replacepkgs qt4-qtdbus-4.8.4-5.mga3 lib64dbus-devel-1.6.8-3.mga3 dbus-1.6.8-3.mga3 lib64dbus1_3-1.6.8-3.mga3 libdbus1_3-1.6.8-3.mga3 dbus-x11-1.6.8-3.mga3 lib64qtdbus4-4.8.4-5.mga3 lib64dbusmenu-qt2-0.9.2-2.mga3 python-qt4-dbus-4.9.6-4.mga3 python-slip-dbus-0.2.20-3.mga3 lib64dbus-glib1_2-0.100-2.mga3 python-dbus-1.1.1-2.mga3

Pete.

[zxr250cc]

I am still having the same trouble where I go into SYSTEM SETTINGS, LOGIN SCREEN and try to set the log in screen to show no users or other settings in the last three tabs and I get the same readout pop up complaining about dbus that I had in the last install of this release on this X-31. Is there a command for 32 bit version to update all of this like the poster above with the 64 bit system?

cheers

oh, another anomaly: I am using grub 2 and it is calling for 1280x1024 on a 1024x768 laptop screen. how can I work on that?

[doktor5000]

Well, that is probably due to systemsettings wanting to ask your credentials, as that dialog needs root permissions for changes.
Can you try to manually launch it via kdesu? either Alt+F2 -> kdesu systemsettings or from a terminal as user via

Code: Select all

/usr/lib64/kde4/libexec/kdesu systemsettings

[pete910]

I am still having the same trouble where I go into SYSTEM SETTINGS, LOGIN SCREEN and try to set the log in screen to show no users or other settings in the last three tabs and I get the same readout pop up complaining about dbus that I had in the last install of this release on this X-31. Is there a command for 32 bit version to update all of this like the poster above with the 64 bit system?

cheers

oh, another anomaly: I am using grub 2 and it is calling for 1280x1024 on a 1024x768 laptop screen. how can I work on that?

Regards dbus reinstall for 32bit.

in console all as root do:

Code: Select all

rpm -qa | grep dbus

all the packages you see listed wants to be in the line afer the following:

Code: Select all

urpmi --replacepkgs " inserted listed packages from above, space separated without the quotes"

It should look pretty much like the command for mine minus the 64 in there names.

Pete.

[pete910]

Well, that is probably due to systemsettings wanting to ask your credentials, as that dialog needs root permissions for changes.
Can you try to manually launch it via kdesu? either Alt+F2 -> kdesu systemsettings or from a terminal as user via

Code: Select all

/usr/lib64/kde4/libexec/kdesu systemsettings

That's been the problem with the dbus install, it fails when trying to be called for root access or whatever. But the reinstall of them solves it.

I noticed that some of the files from the dbus packages had a zero byte size on mine, so did above.

Pete

[doktor5000]

That's been the problem with the dbus install, it fails when trying to be called for root access or whatever. But the reinstall of them solves it.

Well, usually the problem is that people switch to root via su, and then try to call graphical applications, which will never work if they need a dbus session
or something other that gets initiated with a full environment. That's why you need to use su - or kdesu/gksu fro graphical applications.

For the reinstall of dbus you mentioned, that will really only help if the installed dbus packages are broken, not in above mentioned case.

[zxr250cc]

Well. I edited the kdmrc file as usual and logged in as root.

I tried to use SYSTEM SETTINGS (both as a user and as root) and it still does not work for changing SHUTDOWN settings, USERS settings or CONVENIENCE settings. It works just fine for power, or all other settings I have tried as a user or as root. Only the three settings above have been a problem. I have the same error message pop up as I originally posted in this thread...

Could someone give me some cut and paste 32 bit commands to get this fixed with a console? I don't seem to be able to get this fixed myself. Is this a BUG?

I am also not able to change to GRUB as a boot loader instead of grub2 for this install in MCC.

bugs, I guess...

cheers

[pete910]

post output of from the terminal of

Code: Select all

rpm -qa | grep dbus

[zxr250cc]

I worked my way through replacing all of the dbus related packages from the grep command and then the SYSTEM SETTINGS section worked correctly! When I tried to make a change the small permission box for the root password popped up and then the change was saved. Small victory noise here!!!!!!!!!!!!!!!!!

I am still unable to fix the messed up grub install which chose grub2 and tries to set up a 1280x1024 x-11 screen and fails because the screen is 1024x768. It functions after saying press any button and then shows a black and white script style boot loader menu. I have tried to reinstall grub2 and have also tried to install grub instead. Short of doing another install (which I DO NOT want to do!) what are my options?

X-31 1.4 ghz, ati video chipset, 2 gb RAM

I have it set with XP in dual boot configuration.

cheers

[alf]

screen resolution for grub2 can be changed either via kde systemsettings if kcm-grub2 is installed or in file /etc/default/grub directly.

Code: Select all

GRUB_GFXMODE="1024x768x24"

[zxr250cc]

Thanks for the suggestion. I looked in there and discovered that the themes.txt was at issue. I edited it to show the absolute path for the png file it wanted to call up and it still did not work correctly.

My REAL COMPAINT is this: I want to use grub, not grub2 and the system will not switch from grub2 to grub using either MCC or SYSTEM SETTINGS.

Any way that anyone knows, WITH GUI, to force the system to rewrite a boot sector when it is refusing to do so with SYSTEM SETTINGS or MCC?

cheers

[alf]

Well, i just tried changing from grub2 to grub via mcc, no success. That's worth a bug report if none already exists. Will you do that?

[zxr250cc]

Yes, I will try do that. I thought it was just me...

Cheers,

[alf]

Well i've to correct myself. didn't notice that grub was installed to partition instead of MBR, so all works fine with MCC, no need for a bug reprot; Sorry for the noise

[zxr250cc]

I filed a bug report for mine anyway. It should work and it doesn't.