April 2009 - openSUSE Users - openSUSE Mailing Lists

Re: [opensuse] Cups network printers stuck with URI /dev/null (SOLVED)
by Andre Truter 29 Apr '09

29 Apr '09

Solved! 2009/4/29 Andre Truter <andre.truter(a)gmail.com>: > Hi John, > > 2009/4/29 John Andersen <jsamyth(a)gmail.com>: >> >> You can manually edit /etc/cups/printers.conf and remove them. > > They are not in that file. Only local printers are in there. > I found the file that contained the offending entries. /etc/cups/yes/remote.cache I just stopped the cups server, then renamed that file and started the cups server again. Now it only shows local and real remote printers. -- Andre Truter | Software Consultant | Registered Linux user #185282 Jabber: andre.truter(a)gmail.com | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] openSUSE Weekly News, Issue #69 is out
by Sascha 'saigkill' Manns 29 Apr '09

29 Apr '09

We are pleased to announce: Issue 69 of openSUSE Weekly News is out! [0] In this week's issue: * openSUSE 11.2 Milestone 1 Released * People of openSUSE: Jan Engelhardt * Michal Vyskocil : How to track changes in packages: osc vc * Joe Brockmeier: The argument for free fonts * openSUSE Forums: Newbie KDE Questions For a list of available translations see this page: http://en.opensuse.org/OpenSUSE_Weekly_News/69/Translations [0] http://en.opensuse.org/OpenSUSE_Weekly_News/69 Have a lot of fun! -- Sincereley yours Sascha Manns openSUSE Marketing Team openSUSE Build Service openSUSE Features Screening Team Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Covert content change in /root/.wapi/shared_data*
by Thomas Schmitt 29 Apr '09

29 Apr '09

Hi, on my SuSE 10.2 i see a strange behavior of file /root/.wapi/shared_data-ts5-Linux-x86_64-320-10-0 It changes its content without changing inode number, ctime or mtime. Only atime is up to date (due to my reading ?). The affected filesystem is ext3. Is this supposed to be normal ? Does this still happen with the current SuSE version ? How can it happen at all ? Does Mono circumvent the POSIX filesystem interface e.g. by writing directly to blocks of /dev/sda ? ----------------------------------------------- Why i ask: I understand POSIX filesystem semantics the following way: - If the inode was new, then it should have a younger ctime than in the old backup. - If the inode was moved to that place and existed when the backuped inode still existed, then it should have a different inode number. - If the content was overwritten, then mtime should have changed. If mtime was set back to the old timestamp later, then ctime should have been set to the time when this happened. ctime is supposed not to be adjustable freely. All other files in my backup seem to follow those rules. (POSIX promises persistence of "file serial numbers" actually only for a single session. But that filesytem was not unmounted since the old backup was made, and ext3 keeps inode numbers persistent, anyway.) It is not urgent to me to back up a file with Mono stuff which i understand is used for zmd. But i am alarmed by the covert content change which puts in question the faster one of my two incremental backup strategies. The content change was detected by comparing a backup of february with the file's content as it is now. Not much doubt possible. The backup is on BD-RE with its expensive error checking and correction features. Any content alteration on that media should cause an i/o error. The slower backup strategy compares file contents of backup and disk. It detects the covert content change but it has severe drawbacks with BD media and 100+ sessions on them. So the fast backup strategy which only compares inode numbers and timestamps is very valuable to me. Now i would like to learn how it got fooled. Have a nice day :) Thomas -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] X display number
by James Knott 29 Apr '09

29 Apr '09

In X, one can connect to a remote desktop by using a command such as "X -query host :1", which will open the remote desktop as display 1. Is there any method to use the next available number, rather than explicitly specifying the display number? -- Use OpenOffice.org <http://www.openoffice.org> -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 2

[opensuse] corrupt root partition question
by Adam Jimerson 29 Apr '09

29 Apr '09

Ok I have a question regarding the root partition corrupting under openSUSE 11.1 on three different machines. Over night these machines would go from their root partition being less than 50% full to being completely full, but nothing was installed, nothing was changed, and I know the tmp directories are not filling it up because I have cron set up to clear /tmp once a day and /var/tmp every three days at midnight. To be sure I checked to see if cron was still running and didn't have an error, that was fine, so I went in and cleared the tmp directories by hand and did df -h to see if that made a difference and it was still saying 100% full. The first two times this happened I did a clean install after fsk could change anything. Now that this has happened a third time it is looking less like a coincidence and more like a serious problem. Right now it is looking like I may just do a clean install on the third computer because right now it is completely unusable and if I logged out of the active session which can't do anything but sit there then I will be limited to terminal only. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] yum, python 2.6 and Suse 11.1 - A sad tale
by peby＠sagonet.com 29 Apr '09

29 Apr '09

Hi Guys, I would like to use yum on 11.1 - specifically yum-utils and the ability to use yum localinstall, which I find extremely handy and which zypper does not support. (Yes, I know "You should just use zypper!" and "smart is better" and "why would you ever want to use yum on Suse?" and all those wonder things, but the bottom line is that there is still no way for zypper to install a local rpm and handle the dependencies from the repos. Plus, I like yum.) yum is not in 11.1 repo, and seems to have been removed due to python being updated to 2.6 which does not play well with yum. You can still get yum from the 11.0 repo, but there are the below issues trying to get it to work with python 11.0 repo: http://download.opensuse.org/distribution/11.0/repo/oss/suse/i586/yum-3.2.1… Errors when installing as it needs Python < 2.4 and 2.6 is installed with Suse 11.1 I tried a later version of Yum (3.2.22), for RHEL 5.0 from Pbone, but it still required Python < 2.4 and had other dependency isssue as well. No problem, let's just have both Python 2.4 and 2.6 installed right? I downloaded Python and built Python 2.4 from http://www.python.org/download/releases/2.4.6/ ./configure ./make I normally try to run checkinstall to make an rpm rather than 'make install' - but this had a bug too, it just need a directory to be manually created. (What the heck is up with checkinstall having these issues lately?) mkdir -p /usr/local/lib/python2.4/config checkinstall You now have a Python 2.4 RPM - yeah! And it looks good: Callandor:~ # rpm -qpl Python-2.4.6-1.i386.rpm | less Callandor:~ # rpm -Uvh yum-3.2.14-15.1.i586.rpm error: Failed dependencies: python-gpgme is needed by yum-3.2.14-15.1.i586 python < 2.6 is needed by yum-3.2.14-15.1.i586 I installed python-gpgme which resolved that dependency and then just forced the install as Python 2.4 exists: rpm -ivh --nodeps yum-3.2.14-15.1.i586.rpm Callandor:~ #ln -s /usr/local/bin/python2.4 /usr/bin/python2.4 Callandor:~ # python -V Python 2.4.6 Callandor:~ # python2.6 -V Python 2.6 I edited /usr/bin/yum to specify using 2.4.6, which it is. However, yum is still not working with python: Callandor:~ # yum There was a problem importing one of the Python modules required to run yum. The error leading to this problem was: No module named yum Please install a package which provides this module, or verify that the module is installed correctly. It's possible that the above module doesn't match the current version of Python, which is: 2.4.6 (#1, Apr 25 2009, 08:25:54) [GCC 4.3.2 [gcc-4_3-branch revision 141291]] If you cannot solve this problem yourself, please go to the yum faq at: http://wiki.linux.duke.edu/YumFaq I found this there, but honestly it is not too helpful http://wiki.linux.duke.edu/YumFaq#Q7 I tried importing yum in python, no errors but the same issue exists. Any suggestions on how to finish this off and get yum working on 11.1? Thanks! Pete Eby -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

10 22

[opensuse] flock?
by Per Jessen 29 Apr '09

29 Apr '09

I am looking into flock as I have a need to single-thread a particular step in an otherwise highly parallel make. The man page has a suggestion of: (flock -s 200; <single-threaded commands>) 200>/var/lock/file I don't see any obvious race-conditions here, but I was just wondering if anyone's already used this construct? /Per -- Per Jessen, Zürich (7.3°C) -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Edit a file with gedit as root causes error messages
by buzlite 29 Apr '09

29 Apr '09

When I su to root to edit a text file, I received the following message in the console. Could someone give some insight? Thanks $ su Password: # gedit /etc/wvdial.conf (gedit:4437): EggSMClient-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) # -- View this message in context: http://www.nabble.com/Edit-a-file-with-gedit-as-root-causes-error-messages-… Sent from the openSUSE community mailing list archive at Nabble.com. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 3

[opensuse] Re: gnome gui startup error message
by Joachim Schrod 29 Apr '09

29 Apr '09

buzlite wrote: > When I reboot my opensuse 11.1, using the Gnome gui. A dialog box would > appear saying: > > Could not update ICEauthority file /home/someuser/.ICEauthority Does the file exist and is owned by a different user than someuser? If yes, delete it. I had this error the last time when I called k3b from a remote system with sudo. The ownership of ~/.ICEauthority got changed to root and the next application could not open it, access rights being 600. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod(a)acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] gnome gui startup error message
by buzlite 28 Apr '09

28 Apr '09

When I reboot my opensuse 11.1, using the Gnome gui. A dialog box would appear saying: Could not update ICEauthority file /home/someuser/.ICEauthority Could some one help out? Thanks -- View this message in context: http://www.nabble.com/gnome-gui-startup-error-message-tp23283983p23283983.h… Sent from the openSUSE community mailing list archive at Nabble.com. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 1