[SOLVED] Stuffed up GNOME I think...

1234rewq · 10-16-2010, 10:23 PM

* Ubuntu 10.04 LTS *

So I got board and wanted to compile Audacious.
On ./configure I was advised I needed to obtain the library 'GLib 2.26', then when I tried to compile that I was advised I needed to get 'zlib'... so, I ./configure, make, make install zlib (awesome my first ever compile and install)... then I do the same with GLib 2.26... that installs... so, I continue on to ./configure Audacious... oow, now it wants another library... so just out of curiosity I launch synaptic package manager so see if they are listed there... synaptic fails to launch... WTF? Oh well, I'll restart that usually fixes issues.

So... I restart, the default Ubuntu background loads so I am guessing this is X server, but then the system hangs (could not even control+alt+F1 to Linux command line). OK, so its hung... so I restart... Cool, the default Ubuntu background loads again, this time the mouse appears and the computer is running (I can move the mouse and the screen fades to black after idle and I can reach Linux command line if I want via control+alt+F1) but nothing loads - the GNOME login fails to display. I am guessing one of those libraries I installed has broken something.

Is there a log that I look at to see what was last installed and what files were modified? If I could find this, I guess I can replace those files with the original files off the Ubuntu CD? Then once I can normally login I'll just use update manager to get the latest version again.. would this do?

I suspect it is Glib 2.26 that has stuffed it up since it looks like a GNOME related library:

http://ftp.gnome.org/pub/gnome/sourc...-2.26.0.tar.gz

My further research makes me suspect I have broken GTK+.

http://www.gtk.org/download-linux.html

Does anyone have a suggestion?

1234rewq · 10-16-2010, 11:06 PM

I just followed the same steps now from the live session of Ubuntu 10.04 LTS (the live session I am using now) and the exact same issue has occured. Could someone reproduce it also maybe in a virtual machine or something and trying and find out what the hells going on. I have little clue, though I do suspect a library that something is depending on (I suspect the GTK+ version that shipped with Ubuntu 10.04 LTS uses) brakes when using this version of Glib.

http://zlib.net/zlib-1.2.5.tar.bz2

Extract the above and from the directory, run the following (as root):

./configure
make
make install

http://ftp.gnome.org/pub/gnome/sourc...-2.26.0.tar.gz

Extract the above and from the directory, run the following (as root):

./configure
make
make install

Now it should have stuffed GNOME. Try launching Synaptic Package Manager and you will see what I mean. Now reboot and watch GNOME not display. FFS. What is going on?! As much as I hate Windows, some times I do miss it!

sag47 · 10-16-2010, 11:21 PM

Hmmm... The best way I can think for you to do is to first take a snapshot of the files installed on your system and then do a comparison before/after install. Though this only covers whole files that have been added/removed.

I wrote a wiki article on doing this.

Additionally it would be prudent to md5sum your whole filesystem before and after install to see what files have been changed.

Code:

 cd /
find . -type f -print0 | xargs -0 md5sum | tee md5sum.txt

Best to run that command as root before the install. Then after you install GLib do a md5check on the system.

Code:

cd /
md5sum -c md5sum.txt 2>/dev/null | grep -i 'FAIL' > failed.txt

Assuming md5sum exists you can view which files failed their check by opening the document failed.txt with a pager (less) or editor (vim).

Code:

cd /
less ./failed.txt

The reason why I have you running both of those commands is because the 1st one (using the wiki article) will only show you what files have been added or removed from the system. The 2nd one only shows you which files have been changed or removed from the system.

So if you put both commands together you can figure out which files have been added, removed, or changed in your file system.

Please let us know how you fix this problem because others may experience it and need a solution. Please ask if you get stuck and I'll try to help you more along the way. It may also be helpful to search your logs for any keywords you can think of.

1234rewq · 10-17-2010, 03:52 AM

Hi sag47,

Thanks for your assistance with this issue. I see what your doing here.. I think your on a winner mate smart!

When running:

Quote:

find . -type f -print0 | xargs -0 md5sum | tee md5sum.txt

It works and starts checksumming the file system and then after about five minutes of doing so this occurs:

md5sum: ./proc/sysrq-trigger: Input/output error

Is there a switch to make errors ignored and continue with the checksuming?

1234rewq · 10-17-2010, 06:10 AM

OK, so I did was

Load Ubuntu live;
Configure network settings
Install 'zlib' (a glib dependency)
Install 'gettext' (a glib dependency)
ran (as root)

Code:

cd /
find . -type f -print0 | xargs -0 md5sum | tee md5sum.txt'
cd /
md5sum -c md5sum.txt 2>/dev/null | grep -i 'FAIL' > failed.txt'
gedit failed.txt'

Here is the content of failed.txt

Code:

./media/New Volume/glib-2.26.0/glib/tests/bookmarks/fail-08.xbel: OK
./media/New Volume/glib-2.26.0/glib/tests/bookmarks/fail-09.xbel: OK
./media/New Volume/glib-2.26.0/glib/tests/bookmarks/fail-04.xbel: OK
./media/New Volume/glib-2.26.0/glib/tests/bookmarks/fail-17.xbel: OK
./media/New Volume/glib-2.26.0/glib/tests/bookmarks/fail-01.xbel: OK
./media/New Volume/glib-2.26.0/glib/tests/bookmarks/fail-14.xbel: OK
./media/New Volume/glib-2.26.0/glib/tests/bookmarks/fail-05.xbel: OK
./media/New Volume/glib-2.26.0/glib/tests/bookmarks/fail-03.xbel: OK
./media/New Volume/glib-2.26.0/glib/tests/bookmarks/fail-16.xbel: OK
./media/New Volume/glib-2.26.0/glib/tests/bookmarks/fail-11.xbel: OK
./media/New Volume/glib-2.26.0/glib/tests/bookmarks/fail-13.xbel: OK
./media/New Volume/glib-2.26.0/glib/tests/bookmarks/fail-06.xbel: OK
./media/New Volume/glib-2.26.0/glib/tests/bookmarks/fail-10.xbel: OK
./media/New Volume/glib-2.26.0/glib/tests/bookmarks/fail-02.xbel: OK
./media/New Volume/glib-2.26.0/glib/tests/bookmarks/fail-15.xbel: OK
./media/New Volume/glib-2.26.0/glib/tests/bookmarks/fail-07.xbel: OK
./media/New Volume/glib-2.26.0/glib/tests/bookmarks/fail-12.xbel: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-1.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-30.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-7.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-10.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-30.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-8.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-12.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-36.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-9.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-13.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-17.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-33.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-23.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-35.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-28.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-2.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-27.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-22.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-24.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-31.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-37.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-34.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-2.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-29.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-16.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-4.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-20.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-25.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-26.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-39.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-27.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-6.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-34.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-35.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-18.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-24.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-25.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-17.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-13.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-19.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-14.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-23.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-32.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-37.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-32.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-39.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-21.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-14.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-5.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-8.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-31.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-40.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-3.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-22.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-38.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-10.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-40.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-38.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-26.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-9.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-16.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-5.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-33.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-20.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-11.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-1.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-15.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-11.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-19.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-15.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-6.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-21.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-7.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-18.expected: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-28.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-4.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-29.gmarkup: OK
./media/New Volume/glib-2.26.0/glib/tests/markups/fail-12.expected: OK
./media/New Volume/glib-2.26.0/docs/reference/gio/html/failable_initialization.html: OK
./usr/bin/faillog: OK
./usr/lib/apt/apt-report-mirror-failure: OK
./usr/lib/pymodules/python2.6/simplejson/tests/test_fail.pyc: OK
./usr/lib/python2.6/dist-packages/twisted/python/failure.pyc: OK
./usr/lib/python2.6/dist-packages/twisted/test/generator_failure_tests.pyc: OK
./usr/lib/python2.6/dist-packages/twisted/test/test_failure.pyc: OK
./usr/lib/python2.6/dist-packages/twisted/test/test_pbfailure.pyc: OK
./usr/share/man/man8/faillog.8.gz: OK
./usr/share/man/man8/pam_faildelay.8.gz: OK
./usr/share/man/man5/faillog.5.gz: OK
./usr/share/man/cs/man5/faillog.5.gz: OK
./usr/share/man/cs/man8/faillog.8.gz: OK
./usr/share/man/fr/man5/faillog.5.gz: OK
./usr/share/man/fr/man8/faillog.8.gz: OK
./usr/share/man/it/man5/faillog.5.gz: OK
./usr/share/man/it/man8/faillog.8.gz: OK
./usr/share/man/ja/man5/faillog.5.gz: OK
./usr/share/man/ja/man8/faillog.8.gz: OK
./usr/share/man/pl/man5/faillog.5.gz: OK
./usr/share/man/pl/man8/faillog.8.gz: OK
./usr/share/man/ru/man5/faillog.5.gz: OK
./usr/share/man/ru/man8/faillog.8.gz: OK
./usr/share/man/sv/man5/faillog.5.gz: OK
./usr/share/man/sv/man8/faillog.8.gz: OK
./usr/share/doc/python-couchdb/api/couchdb.client.PreconditionFailed-class.html: OK
./usr/share/apt/apt-auth-failure.note: OK
./usr/share/couchdb/www/image/test_failure.gif: OK
./usr/share/gnome/help/update-manager/C/figures/failed-repos.png: OK
./usr/share/icons/hicolor/16x16/apps/gdu-smart-failing.png: OK
./usr/share/icons/hicolor/22x22/apps/gdu-smart-failing.png: OK
./usr/share/icons/hicolor/48x48/apps/gdu-smart-failing.png: OK
./usr/share/icons/hicolor/scalable/apps/gdu-smart-failing.svg: OK
./usr/share/locale-langpack/de/LC_MESSAGES/failsafexinit.mo: OK
./usr/share/locale-langpack/en_AU/LC_MESSAGES/failsafexinit.mo: OK
./usr/share/locale-langpack/en_CA/LC_MESSAGES/failsafexinit.mo: OK
./usr/share/locale-langpack/en_GB/LC_MESSAGES/failsafexinit.mo: OK
./usr/share/locale-langpack/es/LC_MESSAGES/failsafexinit.mo: OK
./usr/share/locale-langpack/fr/LC_MESSAGES/failsafexinit.mo: OK
./usr/share/locale-langpack/pt/LC_MESSAGES/failsafexinit.mo: OK
./usr/share/locale-langpack/pt_BR/LC_MESSAGES/failsafexinit.mo: OK
./usr/share/pyshared/simplejson/tests/test_fail.py: OK
./usr/share/pyshared/twisted/python/failure.py: OK
./usr/share/pyshared/twisted/test/generator_failure_tests.py: OK
./usr/share/pyshared/twisted/test/test_failure.py: OK
./usr/share/pyshared/twisted/test/test_pbfailure.py: OK
./usr/share/recovery-mode/options/failsafeX: OK
./usr/share/synaptic/glade/dialog_update_failed.glade: OK
./usr/share/xsessions/gnome-failsafe.desktop: OK
./usr/src/linux-headers-2.6.32-21-generic/include/config/arch/supports/memory/failure.h: OK
./usr/src/linux-headers-2.6.32-21-generic/include/config/memory/failure.h: OK
./usr/src/linux-headers-2.6.32-21-generic/include/config/x86/supports/memory/failure.h: OK
./home/ubuntu/.xsession-errors: FAILED
./home/ubuntu/.gconfd/saved_state: FAILED
./home/ubuntu/.bash_history: FAILED
./home/ubuntu/.local/share/gvfs-metadata/home: FAILED
./home/ubuntu/.local/share/gvfs-metadata/home-d3838d7c.log: FAILED open or read
./home/ubuntu/.cache/indicator-applet.log: FAILED
./home/ubuntu/.cache/indicator-applet-session.log: FAILED
./home/ubuntu/.gconf/apps/gnome-terminal/profiles/Default/%gconf.xml: FAILED
./home/ubuntu/.gconf/apps/nautilus/preferences/%gconf.xml: FAILED
./var/log/Xorg.0.log: FAILED
./var/log/gdm/:0.log: FAILED
./var/log/wtmp: FAILED
./var/log/auth.log: FAILED
./var/log/faillog: OK
./var/run/utmp: FAILED
./etc/init/failsafe-x.conf: OK
./etc/gdm/failsafeBlacklist: OK
./etc/gdm/failsafeXServer: OK
./etc/gdm/failsafeXinit: OK
./rofs/etc/gdm/failsafeBlacklist: OK
./rofs/etc/gdm/failsafeXServer: OK
./rofs/etc/gdm/failsafeXinit: OK
./rofs/etc/init/failsafe-x.conf: OK
./rofs/lib/partman/display.d/90failsafe: OK
./rofs/lib/security/pam_faildelay.so: OK
./rofs/usr/bin/faillog: OK
./rofs/usr/lib/apt/apt-report-mirror-failure: OK
./rofs/usr/lib/pymodules/python2.6/simplejson/tests/test_fail.pyc: OK
./rofs/usr/lib/python2.6/dist-packages/twisted/python/failure.pyc: OK
./rofs/usr/lib/python2.6/dist-packages/twisted/test/generator_failure_tests.pyc: OK
./rofs/usr/lib/python2.6/dist-packages/twisted/test/test_failure.pyc: OK
./rofs/usr/lib/python2.6/dist-packages/twisted/test/test_pbfailure.pyc: OK
./rofs/usr/share/apt/apt-auth-failure.note: OK
./rofs/usr/share/couchdb/www/image/test_failure.gif: OK
./rofs/usr/share/doc/python-couchdb/api/couchdb.client.PreconditionFailed-class.html: OK
./rofs/usr/share/gnome/help/update-manager/C/figures/failed-repos.png: OK
./rofs/usr/share/icons/hicolor/16x16/apps/gdu-smart-failing.png: OK
./rofs/usr/share/icons/hicolor/22x22/apps/gdu-smart-failing.png: OK
./rofs/usr/share/icons/hicolor/48x48/apps/gdu-smart-failing.png: OK
./rofs/usr/share/icons/hicolor/scalable/apps/gdu-smart-failing.svg: OK
./rofs/usr/share/locale-langpack/de/LC_MESSAGES/failsafexinit.mo: OK
./rofs/usr/share/locale-langpack/en_AU/LC_MESSAGES/failsafexinit.mo: OK
./rofs/usr/share/locale-langpack/en_CA/LC_MESSAGES/failsafexinit.mo: OK
./rofs/usr/share/locale-langpack/en_GB/LC_MESSAGES/failsafexinit.mo: OK
./rofs/usr/share/locale-langpack/es/LC_MESSAGES/failsafexinit.mo: OK
./rofs/usr/share/locale-langpack/fr/LC_MESSAGES/failsafexinit.mo: OK
./rofs/usr/share/locale-langpack/pt/LC_MESSAGES/failsafexinit.mo: OK
./rofs/usr/share/locale-langpack/pt_BR/LC_MESSAGES/failsafexinit.mo: OK
./rofs/usr/share/man/cs/man5/faillog.5.gz: OK
./rofs/usr/share/man/cs/man8/faillog.8.gz: OK
./rofs/usr/share/man/fr/man5/faillog.5.gz: OK
./rofs/usr/share/man/fr/man8/faillog.8.gz: OK
./rofs/usr/share/man/it/man5/faillog.5.gz: OK
./rofs/usr/share/man/it/man8/faillog.8.gz: OK
./rofs/usr/share/man/ja/man5/faillog.5.gz: OK
./rofs/usr/share/man/ja/man8/faillog.8.gz: OK
./rofs/usr/share/man/man5/faillog.5.gz: OK
./rofs/usr/share/man/man8/faillog.8.gz: OK
./rofs/usr/share/man/man8/pam_faildelay.8.gz: OK
./rofs/usr/share/man/pl/man5/faillog.5.gz: OK
./rofs/usr/share/man/pl/man8/faillog.8.gz: OK
./rofs/usr/share/man/ru/man5/faillog.5.gz: OK
./rofs/usr/share/man/ru/man8/faillog.8.gz: OK
./rofs/usr/share/man/sv/man5/faillog.5.gz: OK
./rofs/usr/share/man/sv/man8/faillog.8.gz: OK
./rofs/usr/share/pyshared/simplejson/tests/test_fail.py: OK
./rofs/usr/share/pyshared/twisted/python/failure.py: OK
./rofs/usr/share/pyshared/twisted/test/generator_failure_tests.py: OK
./rofs/usr/share/pyshared/twisted/test/test_failure.py: OK
./rofs/usr/share/pyshared/twisted/test/test_pbfailure.py: OK
./rofs/usr/share/recovery-mode/options/failsafeX: OK
./rofs/usr/share/synaptic/glade/dialog_update_failed.glade: OK
./rofs/usr/share/xsessions/gnome-failsafe.desktop: OK
./rofs/usr/src/linux-headers-2.6.32-21-generic/include/config/arch/supports/memory/failure.h: OK
./rofs/usr/src/linux-headers-2.6.32-21-generic/include/config/memory/failure.h: OK
./rofs/usr/src/linux-headers-2.6.32-21-generic/include/config/x86/supports/memory/failure.h: OK
./rofs/var/log/faillog: OK
./dev/shm/pulse-shm-1976512829: FAILED
./lib/partman/display.d/90failsafe: OK
./lib/security/pam_faildelay.so: OK
./proc/dri/0/gem_objects: FAILED
./proc/dri/0/clients: FAILED

I should mention again, the error 'md5sum: ./proc/sysrq-trigger: Input/output error' occured again when checksumming the directory './proc/dri/0/. As can be seen above (at the bottem of the output from failed.txt) all files in that directory FAILED.

Whilst it may just be nothing.. out of curiosity I opened the first failed file (.xsession-errors) and searched for the term 'glib' and these were found:

Code:

(polkit-gnome-authentication-agent-1:4174): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
** (nm-applet:4166): DEBUG: old state indicates that this was not a disconnect 0

(gnome-power-manager:4182): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.24.0/gobject/gsignal.c:2273: signal `proxy-status' is invalid for instance `0x8950130'

Now this retarded log file is not time stamped, but from the looks of it these errors occured during the boot up of this live session, so these errors occured with the stock files, but the reason I am mentioning this is because as you can see above, it refers to glib as 'glib2.0-2.24.0'. The version I installed is 2.26! so perhaps it has broken something.

What do you make of this?

sag47 · 10-17-2010, 06:51 PM

Quote:

Originally Posted by 1234rewq

It works and starts checksumming the file system and then after about five minutes of doing so this occurs:

md5sum: ./proc/sysrq-trigger: Input/output error

Ah that's because you can't run an md5 checksum on processes in RAM (/proc directory). I forgot about that. Sorry. Here is a command to properly exclude the /proc directory and run an md5sum on the rest of your system....

Code:

cd /
find . -type f -wholename './proc' -prune -print0 | xargs -0 md5sum | tee md5sum.txt

That comes directly from the find man page (search for "-wholename pattern" in that page).

You can run the md5sum -c command just like in my last post to check for failed md5 checksums. Hopefully this clarifies things for you.

Quote:

Originally Posted by 1234rewq

Is there a switch to make errors ignored and continue with the checksuming?

Refer to the md5sum man page (type "man md5sum" in your terminal). You may also want to google "redirect error output bash" which you saw me use in the md5sum -c command.

Quote:

Originally Posted by 1234rewq

Whilst it may just be nothing.. out of curiosity I opened the first failed file (.xsession-errors) and searched for the term 'glib' and these were found:

Now this retarded log file is not time stamped, but from the looks of it these errors occured during the boot up of this live session, so these errors occured with the stock files, but the reason I am mentioning this is because as you can see above, it refers to glib as 'glib2.0-2.24.0'. The version I installed is 2.26! so perhaps it has broken something.

What do you make of this?

The only sure way is to clear your .xsession-errors file and restart. Now any errors you have in the .xsession-errors file will have come from that fresh reboot. You may want to make a backup copy of .xsession-errors but here's how you can clear it (note: my command is in relation to the current working directory).

Code:

cat /dev/null > ./.xsession-errors

Now you just reboot and view .xsession-errors as it will be populated with errors from just that boot sequence.

---------------------------------------------------------
edit: please note:
if you typed the following correctly...

Code:

md5sum -c md5sum.txt 2> /dev/null | grep -i 'FAIL' > failed.txt

Then when you view failed.txt you should only see entries which say failed. If there's any part of the commands I provided which you don't understand then it is best to view the man page for that command. If you don't know how to use the man pages then use the command "man man" in the terminal to read the man page about man.

SAM

1234rewq · 10-18-2010, 06:55 AM

Thanks for your help. It was greatly appreciate it and whilst it did not solve the problem (because glib wasn't the problem), I learn't about md5sum which will one day come handy in life.

The problem was being caused by zlib, not glib.. All I did was remove the zlib files that were installed to fix it.

Its pretty pathetic that GNOME fails due to some files simply being placed in a few directories.

The problem can be reproduced on Ubuntu 10.04 LTS with the following file and commands:

http://zlib.net/zlib125.zip

./configure
make

'make install' will show the files that were installed (and that need to be removed for fixing the issue).

I've only been using Linux (Ubuntu) primarily for my operating system for a couple of months now, so I am not sure exactly why this causes a problem, but perhaps the files are being installed into a sort of boot autorun directory and GNOME is shitting itself when trying to run them, which is why the login screen does not appear.