Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#325 Post Installation Issues :: Unable to copy the user's .Xauthorization file :: Empty /etc/resolv.conf :: /tmp Directory Permissions Break X

PeerGuardian_Linux
closed
hasufell
None
7
15 hours ago
2013-04-19
Eric
No

On a fresh install of Ubuntu 12.04, compiling the latest version from SourceForge breaks your system.

After successfully compiling and installing, you get this error message any time you try to run a sudo command:

"Unable to copy the user's .Xauthorization file"

To fix this error message, you need to run the following commands:

cd ~
touch .Xauthority
sudo chown youruser:youruser ~/.Xauthority
chmod 600 ~/.Xauthority

When you restart, X will not work. This is due to the permissions on the /tmp folder being changed during make and make install. To fix this issue, you need to run the following command:

sudo chmod 1777 /tmp

I've also tried compiling the Peerguardian Linux code on my Mint 13 fresh install. I ran into the same problems listed above on it. I also had an empty /etc/resolv.conf file which broke my connection until I re-added my nameserver.

I'm following this guide for installation:

http://blog.eamster.tk/?p=5

I didn't run into these problems a year ago with the older repository code and Ubuntu 10.04

Discussion

1 2 > >> (Page 1 of 2)
  • Eric
    Eric
    2013-04-19

    This is for PeerGuardian Linux. Not PeerGuardian 2.

     
  • jre-phoenix
    jre-phoenix
    2013-04-26

    • status: open --> pending
    • assigned_to: jre-phoenix
    • Group: PeerGuardian_2 --> PeerGuardian_Linux
     
  • jre-phoenix
    jre-phoenix
    2013-04-26

    First off, for Debian based systems I'd recommend to use my official precompiled packages at moblock-deb.sourceforge.net (see https://sourceforge.net/p/peerguardian/wiki/pgl-Install-DebianUbuntu/).

    Of course you can still build your own packages, instead of using my precompiled ones. See https://sourceforge.net/p/peerguardian/wiki/pgl-Install-DebianUbuntu-Custom/
    Even if you don't want to add my repository for easier updating and build-dependeny installing, you can always compile&build the Debian (Ubuntu/Mint) way:
    debuild -uc -us -tc
    I guess, that way you also don't have the .Xauthority and /tmp problems (still, I will look into this).

    About the nameserver problem: indeed if its IP is saved in /etc/resolv.conf, then pglcmd will take care of allowing it automatically. Is there any other place on your system, where I can get the nameserver IP of your system?

     
  • Eric
    Eric
    2013-04-27

    Thanks for the information. Had I known about this, I would have attempted to install it following your guide.

    When I compiled and installed peerguardian linux on my Mint 13 system, after the install was complete, I couldn't access web pages anymore. The reason was that my /etc/resolv.conf file was blank. Somehow, the installation script for PGL deleted all contents of the /etc/resolv.conf file. I had to re-add my name server to the /etc/resolv.conf file before web pages started to load again.

    I hope that clears it up a bit more.

     
  • jre-phoenix
    jre-phoenix
    2013-04-28

    This definitely mustn't happen.

    I just tried it with

    ./configure \
        --prefix=/usr \
        --mandir=/usr/share/man \
        --datadir=/usr/share \
        --sysconfdir=/etc \
        --localstatedir=/var \
        --with-lsb=/lib/lsb/init-functions \
        --enable-cron \
        --enable-dbus \
        --enable-logrotate \
        --enable-networkmanager \
        --enable-zlib \
        --with-qt4 \
        --disable-lowmem
    make
    sudo make install
    

    but neither can I reproduce your problems, nore spot anything related in the build logs.

    So, for my own sake, I hope it is something wrong on your end (Although you said it happens on two different installations). Is the mentioned blog your own, or is this another guy?

    Can you still reproduce these problems? If yes, can you post hte exact commands and log files from configure, make && make install. Do they occur if you run "autoreconf" first?

     
  • jre-phoenix
    jre-phoenix
    2013-04-28

    To be more precise:

    Ownership and rights of /tmp aren't changed here. It is drwxr-xr-x root root

    /etc/resolv.conf is not changed (but created before the build by NetworkManager)

    ~/.Xauthourity doesn't exist on my system (Debian Wheezy)

     
  • jre-phoenix
    jre-phoenix
    2013-04-28

    • status: pending --> accepted
     
  • jre-phoenix
    jre-phoenix
    2013-04-28

    Correction, at least it really mangles with /tmp here. I couldn't log in after installation and other things didn't work before that neither.
    Thus I also did the

    sudo chmod 1777 /tmp
    

    thus changing /tmp to drwxrwxrwt root root

    About resolv.conf I can't tell, because it was generated by NetworkManager automatically. Does NetworkManager run on your system?

    ~/.Xauthority still is not necessary or present on my system.

     
  • Eric
    Eric
    2013-04-28

    Yes, I run NetworkManager on my system.

    The blog posted above is my own. That's basically the process I followed on my Ubuntu and Mint machines when compiling and installing PeerGuardian Linux.

    I'm not sure if my ~/.Xauthority file existed before install either. I just know that post install, I couldn't run any sudo commands because I'd get this error:

    "Unable to copy the user's .Xauthorization file"

    I had to create the file and change permissions on it before I was able to run sudo commands again.

    My resolv.conf file was empty post install on my Mint machine. I'm not sure about Ubuntu, because I gave up on trying to fix it. I didn't know what was wrong with it. I ended up installing Mint on it, and I ran into the same problem post compiling and installing PeerGuardian. Except, the difference here was that Mint actually pointed out what could possibly be wrong, which is when I figured out the fixes posted in the first post.

     
1 2 > >> (Page 1 of 2)