PDA

View Full Version : [ubuntu] Jaunty boots to a black screen with cursor


RobertWaelder
April 24th, 2009, 03:33 AM
This was already posted at this link (http://ubuntuforums.org/showthread.php?t=1129192&highlight=jaunty+black+screen+after+login). Since the Jaunty testing forum is closed now, I'd like to resurrect this post. So basically, after I input my name and password at the login screen, the screen goes black and I am left with a lonely little arrow (the cursor). It pretty much just stays there indefinitely. I can access a terminal via Ctrl + Alt + Fn, and everything in the console works fine. First I tried removing "nvidia-common" using apt-get as recommended in the previous thread, but when I rebooted, same deal. Then I booted using Failsafe mode in Gnome. This was a little more successful, as I actually got to see the wallpaper, but not soon after that I received two error messages. The first: "There is a problem with the configuration server. (/usr/lib/libgconf2-4/gconf-sanity-check-2 exited with status 256)" and the next: "Nautilus could not create the following required folders: /home/robzilla/Desktop, /home/robzilla/.nautilus. Before running Nautilus, please create these folders, or set permissions such that Nautilus can create them." Soooo.... if anyone could help me figure this issue out, I would be extremely grateful. I really wanna try out Jaunty!:popcorn:

Oh btw, misc information: I'm running 64-bit Ubuntu on an HP Pavilion dv9000, and I'm dual booting alongside Windows.
danlea
April 24th, 2009, 07:37 PM
It could be the same issue I was having (and took me literally all day to figure out). Is your ~/.pulse directory owned by root? If so, delete it.
RobertWaelder
April 24th, 2009, 07:41 PM
Hmm, I think I'll try just changing the permissions before I delete it, but I'll try that! Thanks.
RobertWaelder
April 24th, 2009, 08:02 PM
Hmm, I did ls -a on /home/robzilla, but all I saw was .pulse-cookie (which was a blank text file). Wierd. I think I'll try uninstalling pulse audio altogether.
danlea
April 24th, 2009, 08:26 PM
Well the bug is detailed at the link below, so if it's not applicable to you, there's no need to uninstall pulse audio. I found it through the ~/.xsessions-errors line:
E: core-util.c: Failed to create secure directory: Permission denied

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/330766
RobertWaelder
April 24th, 2009, 08:35 PM
I looked in /root and found a .pulse directory. When I moved it to my home directory, I was able to get a little bit further, and I actually heard the startup sound. It was a little jilted and wonky sounding though. Anyway, I got the same error messages as if I had logged in through the failsafe mode. I decided to check the log file that the first error message mentioned for any clues, and it was a bunch of garbled text with the occasional bit of readable text. I was told it "may be a binary file". I read the readable bits, and it mentioned something about problems with separately mounted /home directories (which I suspected anyway). I'll try to get that file copied to a USB drive so I can post it. Maybe someone will be able to make sense of it.
RobertWaelder
April 24th, 2009, 09:09 PM
Here is the full log file created by the error message. It's rather confusing, so I'll post the full one, plus an abridged version with the important stuff in it.


ELF > @ @ `2 @ 8 @ @ @ @ @ @ 8 8@ 8@ @ @ |' |' - -` -` - -` -` T T@ T@ Ptd h& h&@ h&@ 4 4 Qtd Rtd - -` -` H H /lib64/ld-linux-x86-64.so.2 GNU % : ' 6 4 # & / 7 + , ( 9 3 1 * ) $ % 8 - 5 2
. " ! 0
- € !
ˆ @- 0 8 j Cֺ’|CE:—2bKfUažqXjš|ž % 2 H W 5 › † , o k ‚ “ ` Ÿ i & S = + 8 B { U ~ P1` Z €1` G `1` € P1` „
@ o @ & `1` ‹
@@ ‰ N `1` B
@ + P@ _
0@ i @ libgtk-x11-2.0.so.0 g_free g_unlink g_slist_free g_option_context_free __gmon_start__ _Jv_RegisterClasses g_option_context_parse g_strdup_vprintf g_set_error g_option_context_add_group g_getenv g_file_open_tmp g_file_error_from_errno g_build_filename g_strerror g_option_context_new g_get_home_dir g_error_free g_mkstemp g_file_error_quark g_dgettext gtk_init_check gtk_dialog_add_buttons gtk_get_option_group gtk_message_dialog_new gtk_dialog_run gtk_dialog_get_type gtk_widget_destroy g_print g_printerr g_type_check_instance_cast libgconf-2.so.4 gconf_load_source_path gconf_resolve_address gconf_blow_away_locks gconf_ping_daemon gconf_source_free gconf_use_local_locks g_thread_init libgthread-2.0.so.0 libgobject-2.0.so.0 libglib-2.0.so.0 libpthread.so.0 close open __errno_location fcntl libc.so.6 stdin _IO_getc __libc_start_main _edata __bss_start _end __libc_csu_fini _IO_stdin_used __data_start __libc_csu_init GLIBC_2.2.5 ui › ui › /` `1` 3 0` 0` 0` 0` 0` (0` 00` 80`
@0` H0` P0`
X0` `0` h0` p0` x0` €0` ˆ0` 0` ˜0` *0` 0` 0` 0` 0` 0` 0` 0` 0` 0` 0` ! 0` " 1` # 1` $ 1` % 1` & 1` ' (1` ( 01` ) 81` * @1` + H1` , Hƒ ‚ m Hƒ5‚ %„ @ %‚ h %z h %r h %j h %b h *%Z h %R h €%J h p%B h `%: h P%2 h
@%* h 0%" h % h
% h %
h % h % h % h % h % h *% h % h €% h p% h `% h P% h @% h 0% h %š h %’ h %Š h %‚ h %z h! %r h" %j h# %b h$ *%Z h% %R h& €%J h' p%B h( `%: h) P 1I‰^H‰HƒPTI0@ H@@ H @ HƒH‹‰ H…tHƒÐUH‰SHƒ€= uK-` H‹ H--` HHXH9s%€ HBH‰ -` H‹ H9r› Hƒ[fff.„ UHƒ= H‰t H…t-` I‰A@ ÐUSH H‰T$0H‰t$(H• r@ H‰L$8L‰D$@L‰L$HH‰H)H„$ )x)p)h)`)X)P)H‘)@H„$ $ D$0 H‰D$HD$ H‰D$‹ H‰…„‚ ‹ …tXI‰A@ 111RH‰H‰2H‰H‰GH‰OH‰ H []D H‰@ 1H []€ 11o9 ‰/ `fH‰\$L‰t$E1L‰|$H‰l$A‰L‰d$L‰l$HƒHK … t2L‰‰H‹l$ H‹\$L‹d$(L‹l$0L‹t$8L‹|$@HƒHD Ll$1Ҿ@ $@ 1˜L‰H‰I‰HD$ H…I‰H‰„ f.„ H‹+L‰HD$ H‰H‹|$H…u/H‰H‹;WH‹[H…uL‰t=€ E…D t+H‹_* @ J@ {L‰H‰H‰H‰1H‹|$1€ E…tJH‹D$@ H‰H…t1@ J@ H‹h&H‰þ@ J@ H‰H‰H‰L‰1)H‹|$1H…u’Ž„ H‰\$L‰d$L‰l$L‰t$Hƒx‰|$1H‰4$aQ@ J@ H‰J1H‰H‰H‰eHL$HHt$H‰H‰H D$H H‰_H‹T$HH…t]H‹$L‹b8!@ J@ H‹KL‰H‰1H‰KH‹|$H ‰H‹\$XL‹d$`L‹l$hL‹t$pHƒxf„ HD$@ Š…„ k@ HD$8 H…„> k@ 1H‰Ǿ*!@ 1;H‰H‰D$@~ƒA‰„* L‹d$8M…„ L‹l$@‹!@ M‹d$J@ tL‰H‰‰L‰1E1‡H‹|$8D‰
H‹|$@…ˆc H‹|$@E…… fD 1H‰Ǿx@ 1‚H‰H‰D$@H‹|$@1 A …A‰ˆ HT$1 D‰fD$ HD$ fD$ HD$ A …‰=‹‰L‹l$@I‰ľ #@ J@ mL‰H‰‰L‰1E1€ 11…D …$@ J@ +‹5 H‰…„' ‹
…„ I‰1A@ 1111@ J@ I‰@ J@ I‰I‰L‰H‰H‰E1AL‰H‰L ‰1 H‰L‰H‰L‰‰|ƒ…K1Ҿ@ $@ 11H‰H‰CH‰I‰M…L‰„n @ H‹;0H‹;H‹[H…uL‰ u1…”f„ 3‹‰zL‹l$@I‰ľ!@ a‹8\L‹d$@H‰þ‘@ J@ H‰H‰L‰1e„ HT$8Ht$@*!@ A‰@ ‹‰L‹l$@‰I‰‰4H|$8‰M‰M‰ !@ ‰1’@ J@ %H‰H‰1H‹=‰ lƒY„ƒy…f€11€ m ‰c 8&@ 1žfffff.„ H‰l$L‰|$H-c L=\ L‰d$L‰l$L‰t$H‰\$Hƒ8L)A‰I‰HI‰H…t1 @ L‰L‰D‰AHƒH9rH‹\$H‹l$L‹d$L‹l$ L‹t$(L‹|$0Hƒ8ÐUH‰SHƒH‹ Hƒt-` D HƒH‹HƒuHƒ[ÐHƒ_Hƒ %s path /etc/gconf/2 Error reading the file: GConf2 - Sanity checks for GConf GCONF_TMPDIR .gconf-test-locking-file Can't remove file %s: %s
_Continue _Log Out %s Continue (y/n)? Please contact your system administrator to resolve the following problem:
No configuration sources in the configuration file "%s"; this means that preferences and other settings can't be saved. %s%s Please contact your system administrator to resolve the following problem:
Could not resolve the address "%s" in the configuration file "%s": %s Error while parsing options: %s.
Run '%s --help' to see a full list of available command line options.
gconf-test-locking-file-XXXXXX Failed to create file '%s': %s Please contact your system administrator to resolve the following problem:
Could not open or create the file "%s"; this indicates that there may be a problem with your configuration, as many programs will need to create files in your home directory. The error was "%s" (errno = %d). Please contact your system administrator to resolve the following problem:
Could not lock the file "%s"; this indicates that there may be a problem with your operating system configuration. If you have an NFS-mounted home directory, either the client or the server may be set up incorrectly. See the rpc.statd and rpc.lockd documentation. A common cause of this error is that the "nfslock" service has been disabled.The error was "%s" (errno = %d). The files that contain your preference settings are currently in use.

You might be logged in to a session from another computer, and the other login session is using your preference settings files.

You can continue to use the current session, but this might cause temporary problems with the preference settings in the other session.

Do you want to continue? Failed to load addresses to delete locks
;4 P p ˜˜ zR x @ > AAGƒ† $ < P@ JŽƒM†QPŒ d @ + X€ŽŒƒ zR x $ 4 ‰ J†f@ƒŽŒ P@
@ x@ o @ @ `@
/` `@ 0@ 0 o
@ o o x
@ -` ~@ Ž@ ž@ @ @ @ @ @ @ @ @ .@ >@ N@ ^@ n@ ~@ Ž@ ž@ @ @ @ @ @ @ @ @ .@ >@ N@ ^@ n@ ~@ Ž@ ž@ @ @ @ @ @ @ @ gconf-sanity-check-2 ͏y .shstrtab .interp .note.ABI-tag .gnu.hash .dynsym .dynstr .gnu.version .gnu.version_r .rela.dyn .rela.plt .init .text .fini .rodata .eh_frame_hdr .eh_frame .ctors .dtors .jcr .dynamic .got .got.plt .data .bss .gnu_debuglink 8@ 8 T@ T % x@ x „ ! o @ ` + `@ ` p 3 @ ; o x
@ x
t H o
@
@ W 0@ 0 0 a `@ ` k P@ P f h@ h q @ w @ } @ P … h&@ h& 4 “ *&@ *& -` - -` - -` - -` - /` / /` / h P1` P1 `1` `1 `1 |1


%s path /etc/gconf/2 Error reading the file: GConf2 - Sanity checks for GConf GCONF_TMPDIR .gconf-test-locking-file Can't remove file %s: %s
_Continue _Log Out %s Continue (y/n)? Please contact your system administrator to resolve the following problem:
No configuration sources in the configuration file "%s"; this means that preferences and other settings can't be saved. %s%s Please contact your system administrator to resolve the following problem:
Could not resolve the address "%s" in the configuration file "%s": %s Error while parsing options: %s.
Run '%s --help' to see a full list of available command line options.
gconf-test-locking-file-XXXXXX Failed to create file '%s': %s Please contact your system administrator to resolve the following problem:
Could not open or create the file "%s"; this indicates that there may be a problem with your configuration, as many programs will need to create files in your home directory. The error was "%s" (errno = %d). Please contact your system administrator to resolve the following problem:
Could not lock the file "%s"; this indicates that there may be a problem with your operating system configuration. If you have an NFS-mounted home directory, either the client or the server may be set up incorrectly. See the rpc.statd and rpc.lockd documentation. A common cause of this error is that the "nfslock" service has been disabled.The error was "%s" (errno = %d). The files that contain your preference settings are currently in use.

You might be logged in to a session from another computer, and the other login session is using your preference settings files.

You can continue to use the current session, but this might cause temporary problems with the preference settings in the other session.

Do you want to continue? Failed to load addresses to delete locks

I'm going to try completely uninstalling pulseaudio via apt-get. Couldn't hurt, right?

EDIT: Completely removing pulse-audio had no effect.
p310don
April 26th, 2009, 12:15 AM
I had the issue when upgrading from 8.10 to 9.04 where I left the computer to do its thing for an hour or so, and when I came back, I had a black screen with a cursor, nothing else. I reset the machine, got a login which looked normal, so did the usual, however it came back to the black screen with mouse cursor and nothing at all. After much searching and mucking around, I discovered a solution. Apparently the upgrade didn't finish. To do so, open terminal, ie ctrl alt f2 and type

sudo dpkg --configure -a

Let it continue the upgrade, which took about ten to fifteen mins, then when all is done, type

sudo reboot

And then login. This got me to the gnome desktop, where the notification icon told me a I had a bunch of updates. After installing all updates, I'm now enjoying 9.04.

Hope this helps other users who are also losing hair from frustration. :)
RobertWaelder
April 26th, 2009, 12:50 AM
So simple it just might work!
RobertWaelder
April 26th, 2009, 01:28 AM
That didn't work either :-( I am sad now.
pavel__
April 26th, 2009, 12:26 PM
http://ubuntuforums.org/showthread.php?t=1135402

same thing, but already by using livecd, without installing at all.
RobertWaelder
April 29th, 2009, 10:22 PM
So I figured it out. I am now the proud user of a shiny new Jaunty installation, w00t. :) Basically, I failed to realize when I imported all my Windows settings that I had filled up the /home partition to capacity and nautilus and some configuration programs couldn't create the files they needed to start up. When I did 'df' at the terminal I saw my drive was full and had an aha moment haha. I simply deleted some of the data from the hard drive and voila! Working installation. Thanks everyone for your help and advice!
Snif
June 16th, 2009, 02:38 PM
Had the same error after upgrading from 8.10, alongwith "users $HOME/.dmcr file is being ignored....user's $HOME directory must be owned by user and not writeable to other users" ( http://ubuntuforums.org/showthread.php?t=1062651 ) problem.
Black screen with cursor fixed with

sudo chown -R user:user /home/user
sudo chmod -R 744 /home/user/
sudo chmod 777 /home/user/.dmcr

BTW, I had no .dmcr file in my home directory, so I created it as user.

It may be something wrong with those commands, but they fix the problem.
Please correct me if there's something wrong!

Regards, Michael.
mhgsys
June 16th, 2009, 03:00 PM
H
It may be something wrong with those commands, but they fix the problem.
Please correct me if there's something wrong!

Regards, Michael.

I've seen that error get fixed with these commands;



sudo chmod 644 /home/username/.dmrc



sudo chown username /home/username/.dmrc



sudo chmod 755 /home/username