Bug#763963: Systemd says Failed to create root cgroup hierarchy: Invalid argument
Package: systemd Version: 208-8 When I boot my system, I see the following message: Loading, please wait ... When I remove the quiet keyword from the GRUB - Debian GNU/Linux menu entry and boot the system with the following entry: linux /boot/vmlinuz-2.6.32-5-686 root=UUID=3de041fe-155b-4329-939e-f1da57fea70f ro then I see the following error on console: [ 2.696080] 30 systemd[1]: systemd 208 running in system mode (+PAM +LIBWRAP +AUDIT +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ) Welcome to Debian GNU/Linux jessie/sid! [ 3.012374] 30 systemd[1]: Inserted module 'autofs4' [ 3.038538] 30 systemd[1]: Set hostname to debian [ 3.062844] 27 systemd[1]: Failed to create root cgroup hierarchy: Invalid argument [ 3.063076] 27 systemd[1]: failed to allocate manager object: Invalid argument What caused this problem: I upgraded systemd and libpam-systemd then the above errors started coming. apt-get update aptitude upgrade systemd libpam-systemd I thought that I have not taken the complete upgrade so i did the dist-upgrade using apt-get. apt-get update apt-get dist-upgrade. but these errors do not go away and hence I am filing this bug report. I am using Debian jessie: output of uname -a: Linux (none) 2.6.32-5-686 #1 SMP Sun Sep 23 09:49:36 UTC 2012 i686 GNU/Linux Currently I am using my system by dropping to shell using the below grub menu entry: linux /boot/vmlinuz-2.6.32-5-686 root=UUID=3de041fe-155b-4329-939e-f1da57fea70f ro init=/bin/bash
Bug#556276: bug resolved
Hi, The problem was due to my faulty hard drive. Please, close this bug. Thank you for all the help :-) Regards Manish Mohania -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556276: Gnome Nautilus and Panel error when attempting to register with bonobo on gnome startup
Hi, As per your suggestions: I have run memtest86+ on my system, and I did not find any errors through it. I also tested it through a new RAM, but I am having the same error: Decompressing Linux .. crc error System halted Let me know what do you suggest ? Can it be a hardisk problem ? I have run e2fsck on my hard disk - /dev/sda1 and I did not find any errors. Right now I am running my system using gNewSense Live CD. It is running fine. I am mailing you using gmail through this Live CD. Thanks Regards Manish Mohania On Mon, Nov 16, 2009 at 3:53 PM, Manish Mohania manish.moha...@gmail.com wrote: Thanks again, for a quick reply and suggestion .. Ok ... Let me check it with memtest86. I will also try to check it with a new/different RAM, if I can arrange one. Will get back to you soon ... :-) Regards Manish Mohania 2009/11/16 Josselin Mouette j...@debian.org: Le lundi 16 novembre 2009 à 20:31 +0530, Manish Mohania a écrit : 1) sometimes when I boot my system, I get the following error: RAMDISK: incomplete write (-28 != 32768) 8388608 crc error Kernel Panic - not syncing: VFS : Unable to mount root fs on unknown-block (0) 2) sometimes I get this error: Probing EDD (edd=off to disable) Decompressing Linux ok crc error Do you think I should file a seperate bug report for this error. ?? This is a hardware issue. You should test your RAM with the memtest86 program. It is very likely that the issues you are experiencing are caused by that. Cheers, -- .''`. Josselin Mouette : :' : `. `' “I recommend you to learn English in hope that you in `- future understand things” -- Jörg Schilling -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556276: Gnome Nautilus and Panel error when attempting to register with bonobo on gnome startup
Thanks again, for a quick reply and suggestion .. Ok ... Let me check it with memtest86. I will also try to check it with a new/different RAM, if I can arrange one. Will get back to you soon ... :-) Regards Manish Mohania 2009/11/16 Josselin Mouette j...@debian.org: Le lundi 16 novembre 2009 à 20:31 +0530, Manish Mohania a écrit : 1) sometimes when I boot my system, I get the following error: RAMDISK: incomplete write (-28 != 32768) 8388608 crc error Kernel Panic - not syncing: VFS : Unable to mount root fs on unknown-block (0) 2) sometimes I get this error: Probing EDD (edd=off to disable) Decompressing Linux ok crc error Do you think I should file a seperate bug report for this error. ?? This is a hardware issue. You should test your RAM with the memtest86 program. It is very likely that the issues you are experiencing are caused by that. Cheers, -- .''`. Josselin Mouette : :' : `. `' “I recommend you to learn English in hope that you in `- future understand things” -- Jörg Schilling -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556276: Gnome Nautilus and Panel error when attempting to register with bonobo on gnome startup
Thank you, for addressing my problem. Here is what I did as per your suggestion. When I run the following command from terminal (CTRL + ALT + F1) : ps aux | grep bonobo I do not see any process with name bonobo-ativation-server. Also, when I do : killall bonobo-activation-server It gives the following output : bonobo-activation-server: no process killed I do not understand what bonobo-activation-server is, but I have read the man page. I think it is some important application :( There as no errors in ~/.xsession-errors but two warnings. I am providing the contents of ~/.xsession-errors: --- File: ~/.xsession-errors - /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/debian:/tmp/.ICE-unix/2902 ** (gnome-settings-daemon:2960): WARNING **: Failed to open file '/etc/gnome/config/General.ad': No such file or directory Window manager warning: Failed to read saved session file /home/manish/.metacity/sessions/default0.ms: Failed to open file '/home/manish/.metacity/sessions/default0.ms': No such file or directory - End File: ~/.xsession-errors - As far as I believe my gnome is running since, I can see the background and I am able to run application from terminal (CTRL + ALT + F1) as : iceweasel --display=:0.0 gedit --display=:0.0 This problem is very unpredictable, today I was able to login two times in my gnome with these steps. 1. First I rebooted in single user mode. 2. After login as root, I run the init 5 command. 3. Then, I login as normal user manish from graphical display. But when I rebooted in single user mode again, I was not able to login using above mentioned steps :( Also, 1) sometimes when I boot my system, I get the following error: RAMDISK: incomplete write (-28 != 32768) 8388608 crc error Kernel Panic - not syncing: VFS : Unable to mount root fs on unknown-block (0) 2) sometimes I get this error: Probing EDD (edd=off to disable) Decompressing Linux ok crc error Do you think I should file a seperate bug report for this error. ?? Thank you for your patience and time to read this bug report. Regards Manish Mohania 2009/11/16 Josselin Mouette j...@debian.org: What if you kill any bonobo-activation-server that might be left on your system? Also, are there any relevant errors in ~/.xsession-errors ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556276: Gnome Nautilus and Panel error when attempting to register with bonobo on gnome startup
Package: gnome Version: 1:2.22.2~5 When I login to GNOME, I get this error : 1) Nautilus Package: nautilus Version: 2.20.0-7 Error: Nautilus can't be used now, due to an unexpected error. Details: Nautilus can't be used now, due to an unexpected error from Bonobo when attempting to register the file manager view server 2) Panel Package: gnome-panel Version: 2.20.3-5 Error: The panel has encountered a fatal error. The panel could not register with the bonobo-activation server (error code: 3) and will exit. It may be automatically restarted. My system was working fine till I shutdown/restarted my system and tried to login to GNOME. The only thing that I did before logging out/shutdown was to connect to ftp site using : Places - Connect to Server menu option in nautilus. After I connect to server, an icon with connection name as label appeared on my desktop. I didnot unmount the connection before logging out. I am a complete novice and I do not know if this is the real issue. I am not able to use GNOME due to these 2 errors. please, help me get my good system back to working state :-) . Also, please let me know if you need to know anything else. Thanks and Regards Manish Mohania System Information - Output of uname -a Linux debian 2.6.26-2-686 #1 SMP Wed Nov 4 20:45:37 UTC 2009 i686 GNU/Linux Debian Lenny/stable - 5.0.3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org