8.04 bug - Ubuntu

This is a discussion on 8.04 bug - Ubuntu ; Here is a strange bug. If I gksudo nautilus with a blank CD/DVD in a drive, the command fails with a Segmentation fault. Nice. Is this by design ?...

+ Reply to Thread
Results 1 to 16 of 16

Thread: 8.04 bug

  1. 8.04 bug

    Here is a strange bug.

    If I gksudo nautilus with a blank CD/DVD in a drive, the command fails
    with a Segmentation fault.

    Nice.

    Is this by design ?

  2. Re: 8.04 bug

    On Sat, 19 Jul 2008 22:30:59 -0400, Hobbes wrote:

    > Here is a strange bug.
    >
    > If I gksudo nautilus with a blank CD/DVD in a drive, the command fails
    > with a Segmentation fault.
    >
    > Nice.
    >
    > Is this by design ?


    Strange, I tried it and got the same result, popping a blank DVD in
    afterwards kills it too.

    Do you need root access to a blank DVD?

    --
    A Freudian slip is when you say one thing but mean your mother.



  3. Re: 8.04 bug

    Moog wrote:
    > Hobbes illuminated alt.os.linux.ubuntu by typing:
    >> Here is a strange bug.
    >>
    >> If I gksudo nautilus with a blank CD/DVD in a drive, the command fails
    >> with a Segmentation fault.
    >>
    >> Nice.
    >>
    >> Is this by design ?

    >
    > Well. The same is happening here too. And no, I doubt it is by design.
    >
    > Digging a little deeper, i.e. having a root nautilaus open while
    > inserted a blank DVD.
    >
    > Root nautilus closes and echo's the following error into the terminal
    > window....
    >
    > (nautilus:7526): WARNING **: Unable to add monitor: Operation not
    > supported
    > Nautilus-Share-Message: Called "net usershare info" but it failed:
    > 'net usershare' returned error 255: net usershare: cannot open
    > usershare directory /var/lib/samba/usershares. Error No such file or
    > directory
    > Please ask your system administrator to enable user sharing.
    >
    > So. It's actually an issue with Samba. There is already a launchpad
    > bug open
    > https://bugs.launchpad.net/ubuntu/+s...re/+bug/211966
    >
    > Workaround
    > "The directory didn't exist. I have solved it by doing this
    >
    > mkdir /var/lib/samba/usershares
    > chmod 777 /var/lib/samba/usershares
    > "
    >
    > HTH
    >


    Using dual boot 8.04/WinXP and trying to keep Ubuntu as isolated as
    possible, and got this
    me@AMD64:~$ mkdir /var/lib/samba/usershares
    mkdir: cannot create directory `/var/lib/samba/usershares': No such
    file or directory
    me@AMD64:~$

    me@AMD64:~$ sudo mkdir /var/lib/samba/usershares
    sudo: unable to resolve host AMD64
    [sudo] password for me:
    mkdir: cannot create directory `/var/lib/samba/usershares': No such
    file or directory
    me@AMD64:~$

    I do know there's a probably self inflicted config error somewhere
    that would explain the "unable to resolve host" but as I'm unaware of
    any resultant adverse affects I've been content not to meddle any
    more than using sudo in that instance.

    HTH




    --
    Bob
    Calling alcoholism 'a disease' is
    the politically correct substitute for 'a self induced insanity.'

  4. Re: 8.04 bug

    Bob wrote:
    >
    > Using dual boot 8.04/WinXP and trying to keep Ubuntu as isolated as
    > possible, and got this
    > me@AMD64:~$ mkdir /var/lib/samba/usershares
    > mkdir: cannot create directory `/var/lib/samba/usershares': No such
    > file or directory
    > me@AMD64:~$


    > me@AMD64:~$ sudo mkdir /var/lib/samba/usershares
    > sudo: unable to resolve host AMD64
    > [sudo] password for me:
    > mkdir: cannot create directory `/var/lib/samba/usershares': No such
    > file or directory
    > me@AMD64:~$


    Does /var/lib/samba exist?

    > I do know there's a probably self inflicted config error somewhere
    > that would explain the "unable to resolve host" but as I'm unaware of
    > any resultant adverse affects I've been content not to meddle any
    > more than using sudo in that instance.


    Correct ip-hostname lines in /etc/hosts ?

    --
    Niklaus

  5. Re: 8.04 bug

    Niklaus Kuehnis wrote:
    > Bob wrote:
    >> Using dual boot 8.04/WinXP and trying to keep Ubuntu as isolated as
    >> possible, and got this
    >> me@AMD64:~$ mkdir /var/lib/samba/usershares
    >> mkdir: cannot create directory `/var/lib/samba/usershares': No such
    >> file or directory
    >> me@AMD64:~$

    >
    >> me@AMD64:~$ sudo mkdir /var/lib/samba/usershares
    >> sudo: unable to resolve host AMD64
    >> [sudo] password for me:
    >> mkdir: cannot create directory `/var/lib/samba/usershares': No such
    >> file or directory
    >> me@AMD64:~$

    >
    > Does /var/lib/samba exist?
    >
    >> I do know there's a probably self inflicted config error somewhere
    >> that would explain the "unable to resolve host" but as I'm unaware of
    >> any resultant adverse affects I've been content not to meddle any
    >> more than using sudo in that instance.

    >
    > Correct ip-hostname lines in /etc/hosts ?
    >


    Thanks, it seems not.

    > 127.0.0.1 localhost
    > 127.0.1.1 AMD64.Belkin.127.0.0.1
    >

    # The following lines are desirable for IPv6 capable hosts
    # ::1 ip6-localhost ip6-loopback
    # fe00::0 ip6-localnet
    # ff00::0 ip6-mcastprefix
    # ff02::1 ip6-allnodes
    # ff02::2 ip6-allrouters
    # ff02::3 ip6-allhosts



    --
    Bob
    Calling alcoholism 'a disease' is
    the politically correct substitute for 'a self induced insanity.'

  6. Re: 8.04 bug

    Moog wrote:
    > Hobbes illuminated alt.os.linux.ubuntu by typing:
    >> Here is a strange bug.
    >>
    >> If I gksudo nautilus with a blank CD/DVD in a drive, the command fails
    >> with a Segmentation fault.
    >>
    >> Nice.
    >>
    >> Is this by design ?

    >
    > Well. The same is happening here too. And no, I doubt it is by design.
    >
    > Digging a little deeper, i.e. having a root nautilaus open while
    > inserted a blank DVD.
    >
    > Root nautilus closes and echo's the following error into the terminal
    > window....
    >
    > (nautilus:7526): WARNING **: Unable to add monitor: Operation not
    > supported
    > Nautilus-Share-Message: Called "net usershare info" but it failed:
    > 'net usershare' returned error 255: net usershare: cannot open
    > usershare directory /var/lib/samba/usershares. Error No such file or
    > directory
    > Please ask your system administrator to enable user sharing.
    >
    > So. It's actually an issue with Samba. There is already a launchpad
    > bug open
    > https://bugs.launchpad.net/ubuntu/+s...re/+bug/211966
    >
    > Workaround
    > "The directory didn't exist. I have solved it by doing this
    >
    > mkdir /var/lib/samba/usershares
    > chmod 777 /var/lib/samba/usershares
    > "
    >
    > HTH
    >


    Worked here.
    I had to prefix sudo to the commands

  7. Re: 8.04 bug

    Trevor Best wrote:
    > On Sat, 19 Jul 2008 22:30:59 -0400, Hobbes wrote:
    >
    >> Here is a strange bug.
    >>
    >> If I gksudo nautilus with a blank CD/DVD in a drive, the command fails
    >> with a Segmentation fault.
    >>
    >> Nice.
    >>
    >> Is this by design ?

    >
    > Strange, I tried it and got the same result, popping a blank DVD in
    > afterwards kills it too.
    >
    > Do you need root access to a blank DVD?
    >


    No.
    But Moogs reply below worked for me.

    I just happened to have a blank CD in the drive whilst doing something else.

  8. Re: 8.04 bug

    On 2008-07-20, Moog wrote:
    > Hobbes illuminated alt.os.linux.ubuntu by typing:
    >> Here is a strange bug.
    >>
    >> If I gksudo nautilus with a blank CD/DVD in a drive, the command fails
    >> with a Segmentation fault.
    >>
    >> Nice.
    >>
    >> Is this by design ?

    >
    > Well. The same is happening here too. And no, I doubt it is by design.
    >
    > Digging a little deeper, i.e. having a root nautilaus open while
    > inserted a blank DVD.
    >
    > Root nautilus closes and echo's the following error into the terminal
    > window....
    >
    > (nautilus:7526): WARNING **: Unable to add monitor: Operation not
    > supported
    > Nautilus-Share-Message: Called "net usershare info" but it failed:
    > 'net usershare' returned error 255: net usershare: cannot open
    > usershare directory /var/lib/samba/usershares. Error No such file or
    > directory
    > Please ask your system administrator to enable user sharing.
    >
    > So. It's actually an issue with Samba. There is already a launchpad
    > bug open


    shouldn't Nautilus, as Gnome file manager, be a little more robust in
    handling share errors?

    > https://bugs.launchpad.net/ubuntu/+s...re/+bug/211966
    >
    > Workaround
    > "The directory didn't exist. I have solved it by doing this
    >
    > mkdir /var/lib/samba/usershares
    > chmod 777 /var/lib/samba/usershares
    > "



  9. Re: 8.04 bug

    jane doa illuminated alt.os.linux.ubuntu by typing:
    > On 2008-07-20, Moog wrote:
    >> Hobbes illuminated alt.os.linux.ubuntu by typing:
    >>> Here is a strange bug.
    >>>
    >>> If I gksudo nautilus with a blank CD/DVD in a drive, the command fails
    >>> with a Segmentation fault.
    >>>
    >>> Nice.
    >>>
    >>> Is this by design ?

    >>
    >> Well. The same is happening here too. And no, I doubt it is by design.
    >>
    >> Digging a little deeper, i.e. having a root nautilaus open while
    >> inserted a blank DVD.
    >>
    >> Root nautilus closes and echo's the following error into the terminal
    >> window....
    >>
    >> (nautilus:7526): WARNING **: Unable to add monitor: Operation not
    >> supported
    >> Nautilus-Share-Message: Called "net usershare info" but it failed:
    >> 'net usershare' returned error 255: net usershare: cannot open
    >> usershare directory /var/lib/samba/usershares. Error No such file or
    >> directory
    >> Please ask your system administrator to enable user sharing.
    >>
    >> So. It's actually an issue with Samba. There is already a launchpad
    >> bug open

    >
    > shouldn't Nautilus, as Gnome file manager, be a little more robust in
    > handling share errors?


    It should be, but it passes it's networking shares via samba, so
    therefore it's either a samba issue, or Nautilus is not correctly
    implementing itself.

    As the priority is set to "low" on the bug on launchpad, I would
    suggest that the dev team aren't overly worried about it.

    --
    "How many people here have telekenetic powers? Raise my hand." ~ Emo
    Philips

  10. Re: 8.04 bug

    Hobbes illuminated alt.os.linux.ubuntu by typing:

    >
    > Worked here.
    > I had to prefix sudo to the commands


    I'm glad. Thanks for reporting back.

    --
    "How many people here have telekenetic powers? Raise my hand." ~ Emo
    Philips

  11. Re: 8.04 bug

    Bob illuminated alt.os.linux.ubuntu by typing:

    >
    > Using dual boot 8.04/WinXP and trying to keep Ubuntu as isolated as
    > possible, and got this
    > me@AMD64:~$ mkdir /var/lib/samba/usershares
    > mkdir: cannot create directory `/var/lib/samba/usershares': No such
    > file or directory
    > me@AMD64:~$
    >
    > me@AMD64:~$ sudo mkdir /var/lib/samba/usershares
    > sudo: unable to resolve host AMD64
    > [sudo] password for me:
    > mkdir: cannot create directory `/var/lib/samba/usershares': No such
    > file or directory
    > me@AMD64:~$
    >
    > I do know there's a probably self inflicted config error somewhere
    > that would explain the "unable to resolve host" but as I'm unaware of
    > any resultant adverse affects I've been content not to meddle any
    > more than using sudo in that instance.


    It's unlikely to be "self inflicted".

    My first thought is...

    Do you actually have the full samba package installed?

    --
    "I was sleeping the other night, alone, thanks to the exterminator." ~
    Emo Philips

  12. Re: 8.04 bug

    Moog wrote:
    > Bob illuminated alt.os.linux.ubuntu by typing:
    >
    >> Using dual boot 8.04/WinXP and trying to keep Ubuntu as
    >> isolated as possible, and got this me@AMD64:~$ mkdir
    >> /var/lib/samba/usershares mkdir: cannot create directory
    >> `/var/lib/samba/usershares': No such file or directory
    >> me@AMD64:~$
    >>
    >> me@AMD64:~$ sudo mkdir /var/lib/samba/usershares sudo: unable to
    >> resolve host AMD64 [sudo] password for me: mkdir: cannot create
    >> directory `/var/lib/samba/usershares': No such file or directory
    >> me@AMD64:~$
    >>
    >> I do know there's a probably self inflicted config error
    >> somewhere that would explain the "unable to resolve host" but as
    >> I'm unaware of any resultant adverse affects I've been content
    >> not to meddle any more than using sudo in that instance.

    >
    > It's unlikely to be "self inflicted".
    >
    > My first thought is...
    >
    > Do you actually have the full samba package installed?
    >


    Thanks for a welcome escape card, Moog.

    No, and I don't recall installi8ng any Samba at all on this
    installation. However Synaptic [samba] search reveals these are in
    fact installed.
    smbclient
    samba-common
    nautilus-share
    libsmbclient

    I haven't always checked what dependencies I'm installing and guess
    that explains a lot if not all the reason for those.

    Note, since joining this thread I have backed up and edited /etc/hosts

    from
    127.0.0.1 localhost
    127.0.1.1 AMD64.Belkin.127.0.0.1

    To

    127.0.0.1 localhost
    127.0.1.1 AMD64

    Which seemed to result in an unusually fast launch after gksudo
    nautilus but the following chatter is still in terminal after closing
    nautilus.

    me@AMD64:~$ gksudo nautilus
    Initializing nautilus-share extension

    ** (nautilus:27782): WARNING **: Unable to add monitor: Operation not
    supported
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS SSSSSSSSSSSSSSSSSSSSSSSSNautilus-Share-Message:
    Called "net usershare info" but it failed: 'net usershare' returned
    error 255: net usershare: cannot open usershare directory
    /var/lib/samba/usershares. Error No such file or directory
    Please ask your system administrator to enable user sharing.

    seahorse nautilus module shutdown
    me@AMD64:~$


    HTH

    --
    Bob
    Calling alcoholism 'a disease' is
    the politically correct substitute for 'a self induced insanity.'

  13. Re: 8.04 bug

    Bob wrote:
    > Moog wrote:
    > > Bob illuminated alt.os.linux.ubuntu by typing:
    > >
    > >> Using dual boot 8.04/WinXP and trying to keep Ubuntu as
    > >> isolated as possible, and got this me@AMD64:~$ mkdir
    > >> /var/lib/samba/usershares mkdir: cannot create directory
    > >> `/var/lib/samba/usershares': No such file or directory
    > >> me@AMD64:~$
    > >>
    > >> me@AMD64:~$ sudo mkdir /var/lib/samba/usershares sudo: unable to
    > >> resolve host AMD64 [sudo] password for me: mkdir: cannot create
    > >> directory `/var/lib/samba/usershares': No such file or directory
    > >> me@AMD64:~$
    > >>
    > >> I do know there's a probably self inflicted config error
    > >> somewhere that would explain the "unable to resolve host" but as
    > >> I'm unaware of any resultant adverse affects I've been content
    > >> not to meddle any more than using sudo in that instance.

    > >
    > > It's unlikely to be "self inflicted".
    > >
    > > My first thought is...
    > >
    > > Do you actually have the full samba package installed?
    > >


    > Thanks for a welcome escape card, Moog.


    > No, and I don't recall installi8ng any Samba at all on this
    > installation. However Synaptic [samba] search reveals these are in
    > fact installed.
    > smbclient
    > samba-common
    > nautilus-share
    > libsmbclient


    > I haven't always checked what dependencies I'm installing and guess
    > that explains a lot if not all the reason for those.


    > Note, since joining this thread I have backed up and edited /etc/hosts


    > from
    > 127.0.0.1 localhost
    > 127.0.1.1 AMD64.Belkin.127.0.0.1


    > To


    > 127.0.0.1 localhost
    > 127.0.1.1 AMD64


    > Which seemed to result in an unusually fast launch after gksudo
    > nautilus but the following chatter is still in terminal after closing
    > nautilus.


    > me@AMD64:~$ gksudo nautilus
    > Initializing nautilus-share extension


    > ** (nautilus:27782): WARNING **: Unable to add monitor: Operation not
    > supported
    > SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS SSSSSSSSSSSSSSSSSSSSSSSSNautilus-Share-Message:
    > Called "net usershare info" but it failed: 'net usershare' returned
    > error 255: net usershare: cannot open usershare directory
    > /var/lib/samba/usershares. Error No such file or directory
    > Please ask your system administrator to enable user sharing.


    > seahorse nautilus module shutdown
    > me@AMD64:~$


    Hmmm.

    If you'd do this from a terminal anyway, try sudo.

    I think you can't uninstall nautilus-share without uninstalling
    nautilus, right?

    --
    Niklaus

  14. Re: 8.04 bug

    Niklaus Kuehnis wrote:
    > Bob wrote:
    >> Moog wrote:
    >>> Bob illuminated alt.os.linux.ubuntu by typing:
    >>>
    >>>> Using dual boot 8.04/WinXP and trying to keep Ubuntu as
    >>>> isolated as possible, and got this me@AMD64:~$ mkdir
    >>>> /var/lib/samba/usershares mkdir: cannot create directory
    >>>> `/var/lib/samba/usershares': No such file or directory
    >>>> me@AMD64:~$
    >>>>
    >>>> me@AMD64:~$ sudo mkdir /var/lib/samba/usershares sudo: unable to
    >>>> resolve host AMD64 [sudo] password for me: mkdir: cannot create
    >>>> directory `/var/lib/samba/usershares': No such file or directory
    >>>> me@AMD64:~$
    >>>>
    >>>> I do know there's a probably self inflicted config error
    >>>> somewhere that would explain the "unable to resolve host" but as
    >>>> I'm unaware of any resultant adverse affects I've been content
    >>>> not to meddle any more than using sudo in that instance.
    >>> It's unlikely to be "self inflicted".
    >>>
    >>> My first thought is...
    >>>
    >>> Do you actually have the full samba package installed?
    >>>

    >
    >> Thanks for a welcome escape card, Moog.

    >
    >> No, and I don't recall installi8ng any Samba at all on this
    >> installation. However Synaptic [samba] search reveals these are in
    >> fact installed.
    >> smbclient
    >> samba-common
    >> nautilus-share
    >> libsmbclient

    >
    >> I haven't always checked what dependencies I'm installing and guess
    >> that explains a lot if not all the reason for those.

    >
    >> Note, since joining this thread I have backed up and edited /etc/hosts

    >
    >> from
    >> 127.0.0.1 localhost
    >> 127.0.1.1 AMD64.Belkin.127.0.0.1

    >
    >> To

    >
    >> 127.0.0.1 localhost
    >> 127.0.1.1 AMD64

    >
    >> Which seemed to result in an unusually fast launch after gksudo
    >> nautilus but the following chatter is still in terminal after closing
    >> nautilus.

    >
    >> me@AMD64:~$ gksudo nautilus
    >> Initializing nautilus-share extension

    >
    >> ** (nautilus:27782): WARNING **: Unable to add monitor: Operation not
    >> supported
    >> SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS SSSSSSSSSSSSSSSSSSSSSSSSNautilus-Share-Message:
    >> Called "net usershare info" but it failed: 'net usershare' returned
    >> error 255: net usershare: cannot open usershare directory
    >> /var/lib/samba/usershares. Error No such file or directory
    >> Please ask your system administrator to enable user sharing.

    >
    >> seahorse nautilus module shutdown
    >> me@AMD64:~$

    >
    > Hmmm.
    >
    > If you'd do this from a terminal anyway, try sudo.
    >
    > I think you can't uninstall nautilus-share without uninstalling
    > nautilus, right?
    >


    nautilus-share didn't show anything else going out with it during a
    complete removal using Synaptic

    After that I got this


    me@AMD64:~$ sudo nautilus
    seahorse nautilus module initialized

    ** (nautilus:1292): WARNING **: Unable to add monitor: Operation not
    supported
    seahorse nautilus module shutdown
    me@AMD64:~$

    Then, this launched nautilus, I closed nautilus, all so cleanly its scary
    me@AMD64:~$ gksudo nautilus
    me@AMD64:~$

    I suspect it was a consequence of System/Help and Support
    sudo pppoeconf

    while attempting to optimise a working modem/router setup that
    resulted in needless dependencies being installed

    HTH

    --
    Bob
    Calling alcoholism 'a disease' is
    the politically correct substitute for 'a self induced insanity.'

  15. Re: 8.04 bug

    Bob illuminated alt.os.linux.ubuntu by typing:
    > I suspect it was a consequence of System/Help and Support
    > sudo pppoeconf
    >
    > while attempting to optimise a working modem/router setup that
    > resulted in needless dependencies being installed


    That's possible, Bob.

    Glad we seem to have got somewhere though.

    --
    On another night, they'd have won 2-2. ~ Ron Atkinson

  16. Re: 8.04 bug

    Moog wrote:
    > Bob illuminated alt.os.linux.ubuntu by typing:
    >> I suspect it was a consequence of System/Help and Support
    >> sudo pppoeconf
    >>
    >> while attempting to optimise a working modem/router setup that
    >> resulted in needless dependencies being installed

    >
    > That's possible, Bob.
    >
    > Glad we seem to have got somewhere though.
    >


    Moog, that would be true if I didn't subsequently leave /home as it
    is and do a fresh install before digging deeper into the logs to save
    nanoseconds on boot up.

    I'll get around to starting a new thread on booting up stanzas
    sometime if I can't find my answer through Google. My TV card is
    correctly recognized despite a stanza error (of mine), and I've lost
    HDD temps and fan speeds, only core temp (whatever that is, used to
    have cpu temp) remains, in my panel applet.

    Thanks again,

    --
    Bob
    Calling alcoholism 'a disease' is
    the politically correct substitute for 'a self induced insanity.'

+ Reply to Thread