Results 1 to 5 of 5

Thread: "Could not acquire name on session bus"?

  1. #1

    Question "Could not acquire name on session bus"?

    After upgrading from 11.1 to 11.2 my gnome box starts with a message box stating "Could not acquire name on session bus" directly after the (successful) login.

    I'm not really sure which applications creates the message box since there is no title on the window.

    As far as I can see, the everything else on the desktop is fully operational.

    When investigating the problem I found some kind of recursive calls in the process table (ps -axf):

    \_ /usr/bin/gnome-session
    | \_ /usr/bin/gnome-session
    | | \_ /usr/bin/gnome-session
    | | | \_ /usr/bin/gnome-session
    | | | | \_ /usr/bin/gnome-session
    | | | | | \_ /usr/bin/gnome-session
    | | | | | | \_ /usr/bin/gnome-session
    | | | | | | | \_ /usr/bin/gnome-session
    | | | | | | | | \_ /usr/bin/gnome-session
    | | | | | | | | | \_ /usr/bin/gnome-session
    | | | | | | | | | | \_ /usr/bin/gnome-session
    | | | | | | | | | | | \_ /usr/bin/gnome-session
    | | | | | | | | | | | | \_ /usr/bin/gnome-session
    | | | | | | | | | | | | | \_ /usr/bin/gnome-session
    | | | | | | | | | | | | | \_ nautilus
    | | | | | | | | | | | | | \_ python /usr/share/system-config-printer/applet.py
    | | | | | | | | | | | | | \_ gpk-update-icon
    | | | | | | | | | | | | \_ nautilus
    | | | | | | | | | | | | \_ python /usr/share/system-config-printer/applet.py
    | | | | | | | | | | | | \_ /bin/sh /usr/bin/start-pulseaudio-x11
    | | | | | | | | | | | | \_ /usr/bin/pulseaudio --start
    | | | | | | | | | | | \_ nautilus
    | | | | | | | | | | | \_ python /usr/share/system-config-printer/applet.py
    | | | | | | | | | | | \_ /bin/sh /usr/bin/start-pulseaudio-x11
    | | | | | | | | | | | \_ /usr/bin/pulseaudio --start
    | | | | | | | | | | | \_ /usr/bin/pulseaudio --start
    | | | | | | | | | | \_ nautilus
    | | | | | | | | | | \_ python /usr/share/system-config-printer/applet.py
    | | | | | | | | | \_ nautilus
    | | | | | | | | | \_ python /usr/share/system-config-printer/applet.py
    | | | | | | | | \_ nautilus
    | | | | | | | | \_ python /usr/share/system-config-printer/applet.py
    | | | | | | | \_ nautilus
    | | | | | | | \_ python /usr/share/system-config-printer/applet.py
    | | | | | | \_ nautilus
    | | | | | | \_ python /usr/share/system-config-printer/applet.py
    | | | | | \_ nautilus
    | | | | | \_ python /usr/share/system-config-printer/applet.py
    | | | | \_ nautilus
    | | | | \_ python /usr/share/system-config-printer/applet.py
    | | | \_ nautilus
    | | | \_ python /usr/share/system-config-printer/applet.py
    | | \_ python /usr/share/system-config-printer/applet.py
    | | \_ nautilus
    | \_ python /usr/share/system-config-printer/applet.py
    | \_ nautilus
    \_ gnome-panel


    I already crawled the dbus sources as well as the python tools above with no result.

    I also noticed nautilus to continuously write the message "(nautilus:2613): GLib-WARNING **: poll(2) failed due to: Das Argument ist ungltig" to ~/.xsession-errors.

    My system is running openSUSE 11.2 with the std kernel 2.6.31.8-0.1-default #1 SMP 2009-12-15 23:55:40 +0100 x86_64 GNU/Linux.

    Can anyone suggest a direction for further investigation at least?

  2. #2
    palladium NNTP User

    Default Re: "Could not acquire name on session bus"?

    Elizar wrote:
    > After upgrading from 11.1 to 11.2 . . .
    > Can anyone suggest a direction for further investigation at least?


    if it were my problem i'd confirm the iso's md5sum again, and
    reconfirm the install disk didn't get a fingerprint/scratch/whatever
    after its initial http://tinyurl.com/yajm2aq, and then after being
    absolutely SURE the install media is 100% correct, i'd pick "Repair
    Installed System" from that same DVD install screen..

    oh, you DID upgrade using the accepted/tested/proven method outlined
    here http://en.opensuse.org/Upgrade right? or, you used a 100% pure
    DVD and selected the upgrade option, right? otherwise you are kinda
    out there in experiment land and there is really little we might . . .

    on the other hand, if your media and install are good, i guess you
    might have a bug to report....at least you might drag a net through
    that area and see if any bugs there apply...(that is to say: you got a
    new one, to me!)

    see: http://en.opensuse.org/Submitting_Bu...ching_for_Bugs

    --
    palladium

  3. #3

    Default Re: "Could not acquire name on session bus"?

    I did the md5sum check after downloading the iso. No problems detected there.

    Yes, I proceeded as suggested. (I did some upgrades with previous SuSE releases before and made a colorful bunch of experiences - including some really bizarre moments ).

    > absolutely SURE the install media is 100% correct, i'd pick "Repair
    > Installed System" from that same DVD install screen..

    The problem appeared directly after upgrading. How can 'repair' change anything about that?

    I would really like to narrow the problem further before crying "bug!".

  4. #4
    palladium NNTP User

    Default Re: "Could not acquire name on session bus"?

    Elizar wrote:
    > The problem appeared directly after upgrading. How can 'repair' change
    > anything about that?


    i was just going on the assumption that you had one of these:

    1. faulty install media
    2. damaged install
    3. known bug
    4. something else (perhaps hardware, software, setup, persistent bit
    from previous install...who knows, the range of possibilities is
    incredible....is a lot easier to take'em step by step)

    you solved the first question in your second post..

    however, even with good media it is still possible to have an error
    introduced at some point in the install process or during the initial
    online update before the install is completed (via RAM blip, bad hard
    drive bit flip, etc)

    while the DVD 'repair' script _might_ detect and fix the second i've
    not known it to make matters worse, so it is usually a fix (win) or no
    damage (win); and to my mind a win-win is usually a good thing...but
    if you are not willing to take that step until i explain myself (as i
    am now) or you wanna continue questioning, you are extremely welcome
    to wait for another opinion on how to proceed..


    > I would really like to narrow the problem further before crying "bug!".


    which is precisely *why* i wrote "if your media and install are good"
    and "see if any bugs there apply" and did not write "cry 'bug!' and
    file a report, see: http://en.opensuse.org/Submitting_Bug_Reports"

    i'd say if you wanna ask for help here you should be willing to *read*
    the answers..

    on the other hand perhaps you are not a native english user, in which
    case i can probably understand your apparent confusion with my attempt
    at helping..

    i know i should not assume...but, i just took a step i assumed you had
    taken before your first post, and found:

    http://www.google.com/search?&q="Could+not+acquire+name+on+session+bus"

    --
    palladium

  5. #5

    Default Re: "Could not acquire name on session bus"?

    Hello, check your ~/.xinitrc file, it may contains "gnome-session". remove this file or just delete the line can fix it. I guess you tried switching your desk to KDE

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
  •