Hello, Nx-ers!

I am experiencing a small, but very bothersome problem with my desktop.
I have 2 desktops on the same screen, most of the times when i start my computer. Sometime i got only 1 desktop, so it works normally. How can i ban forever the double desktop on the same screen?
At the end of the booting process it always comes up normally, single desktop, with nx logo in the middle, but as -a last step- it creates another desktop half over the previous one...
Has anyone experienced something like this before?

Adrian

I was taking a wild stab that you're recursively listing your Desktop in your Desktop.

But I couldn't replicate the problem which means I'm not breaking it properly or that is not the answer.

Cut and paste the output of It will look like

Hello, Moe!

This is what i got:

total 1432
261255 4 drwxr-xrwx 2 nx nx 4096 Mar 24 17:07 .
261123 4 drwxr-xr-x 64 nx nx 4096 Mar 24 17:07 ..
302982 616 -rw-rw-r-- 1 nx nx 629619 Mar 14 16:58 2014-03-14_175851_1360x768.png
303007 612 -rw-rw-r-- 1 nx nx 625265 Mar 15 18:03 2014-03-15_190323_1360x768.png
303328 92 -rw-rw-r-- 1 nx nx 93414 Mar 24 17:07 2014-03-24_170713_1360x768.png
303541 100 -rw-rw-r-- 1 nx nx 98748 Mar 24 17:07 2014-03-24_170719_1360x768.png
261256 4 -rw-r--rw- 1 nx nx 181 Mar 4 06:46 home.desktop

Bugger! No simple solution for us.

I've been looking Adrian and coming up with nothing.

Now, you said this is happening on every boot since the 4th of March, or is it intermittent and some time after the 4th?

I also thought you had done a hard drive installation.

You might be time ahead to re-make your persistence file though the boot menu and see if that is causing it....or will fix it as might be the case.

Hello, Moe!

It is funny that you ask about 4th of march. Thats the day of my first complete nx meltdown. We were on passage, 3rd day out, and the thing just would not boot up more. Froze with a blinking propmt...
I made a new HDD installation from my emergency stick, which also contains the mirror of my HDD`s Home, Music,Pictures,Documents folders, backed up very often.
So after installation i sudo copied my entire backup Home folder into the virgin HDD installation`s Home folder.
And everything works fine, but the redhift, the desktop-problem, and another one with wvdial...
Well, everything else works as before:I have all my files: slypheed gets my mail via satellite, can receive gribs offshore, wikipedia is working fine, got all my music, charts, opencpn tracks...etc.
But some little things like the redshift did not fall in place right.
Any opinions?
Adrian

There was a low budget sci-fi movie in the 1950-60s where the "Mad Scientist" injects himself with the memory of a deceased person....oh, it starts with vague impressions; leading to nightmares and eventual, ultimately, insanity.

Let me ponder this one a bit....I might even recall the name of the movie.

In the meantime try:it will look something like this...just 'cause we're curious people.

Hello, Moe!

It is very similar to your return:
total 20
261121 4 drwxr-xr-x 5 root root 4096 Mar 4 06:46 .
2 4 drwxr-xr-x 23 root root 4096 Mar 4 06:48 ..
261340 4 drwxrwxrwx 7 nx nx 4096 Mar 4 07:01 Charts
261345 4 drwxrwxrwx 3 nx nx 4096 Mar 4 06:46 Music
261123 4 drwxr-xr-x 64 nx nx 4096 Mar 25 06:22 nx

adrian

Ok...now when you did this fresh install on that dark day in the beginning of March...did you create a user other than nx?

looks likeWhat do you have?

wow, i got lots of stuff :

nx@navigatrix:~$ cat /etc/passwd
root:x:0:0:root:/root:/bin/bash
daemon:x:1:1:daemon:/usr/sbin:/bin/sh
bin:x:2:2:bin:/bin:/bin/sh
sys:x:3:3:sys:/dev:/bin/sh
sync:x:4:65534:sync:/bin:/bin/sync
games:x:5:60:games:/usr/games:/bin/sh
man:x:6:12:man:/var/cache/man:/bin/sh
lp:x:7:7:lp:/var/spool/lpd:/bin/sh
mail:x:8:8:mail:/var/mail:/bin/sh
news:x:9:9:news:/var/spool/news:/bin/sh
uucp:x:10:10:uucp:/var/spool/uucp:/bin/sh
proxy:x:13:13:proxy:/bin:/bin/sh
www-data:x:33:33:www-data:/var/www:/bin/sh
backup:x:34:34:backup:/var/backups:/bin/sh
list:x:38:38:Mailing List Manager:/var/list:/bin/sh
irc:x:39:39:ircd:/var/run/ircd:/bin/sh
gnats:x:41:41:Gnats Bug-Reporting System (admin):/var/lib/gnats:/bin/sh
libuuid:x:100:101::/var/lib/libuuid:/bin/sh
syslog:x:101:103::/home/syslog:/bin/false
messagebus:x:102:105::/var/run/dbus:/bin/false
usbmux:x:103:46:usbmux daemon,,,:/home/usbmux:/bin/false
dnsmasq:x:104:65534:dnsmasq,,,:/var/lib/misc:/bin/false
ntp:x:105:109::/home/ntp:/bin/false
whoopsie:x:106:110::/nonexistent:/bin/false
lightdm:x:107:115:Light Display Manager:/var/lib/lightdm:/bin/false
debian-tor:x:108:119::/var/lib/tor:/bin/false
rtkit:x:109:120:RealtimeKit,,,:/proc:/bin/false
avahi:x:110:121:Avahi mDNS daemon,,,:/var/run/avahi-daemon:/bin/false
pulse:x:111:123:PulseAudio daemon,,,:/var/run/pulse:/bin/false
mpd:x:112:29::/var/lib/mpd:/bin/false
nobody:x:65534:65534:nobody:/nonexistent:/bin/sh
nx:x:1000:1000:nx,,,:/home/nx:/bin/bash

Is this good for me?

To butcher the idea, that is a list of all the 'users' on the system.

nx:x:1000:1000:nx,,,:/home/nx:/bin/bash

nx, user name
x, there is an encrypted password for the account
1000, user ID number
1000, group ID number
nx, "Real" name
<missing>, additional information about user, typically blank, but could be phone #...whaterver.
/home/nx, the user's stomping ground
/bin/bash, the user's path to a command or shell, that the user does things with

The whole thing is a secure way of listing...who you are (and all potential background operators); where you (they) belong; what is your (their) range of activity.

Unfortunately I don't see a 'smoking gun'.

That is I thought...maybe the 'user' of the install might be buried by the whole scale replacement of /home/nx, and there was a vestigial 'nx' user on the system that got a chance to live....similar to that old sci-fi movie.

Something did not fully transfer when you copied over part of the filesystem...but what?

It might be the the least aggravating path to re-install the system and then transfer the data file you have backed up <some place else>, and then move your personal data back to the new installation rather than figure out what went wrong on the 4th of March.