Choose style:

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Ulysses_

Pages: [1] 2 3 4
1
Code: [Select]
DISTRIB_ID=Peppermint
DISTRIB_RELEASE=9
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Peppermint 9 Nine"

Code: [Select]
Linux peppermint 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

2
64-bit. Don't remember what version it started as, don't the upgrades with synaptic make it the same as the current one?

3
The point is maybe drawing the icons on top of each other at the bottom right is what triggers the leak if there are enough icons, or there is a calculation overflow as often happens in extreme cases. Another thing in my setup is that an NTFS drive is mounted at the Desktop directory at boot time. Shouldn't matter but it had to be mentioned. Next time I see it happen, what info should I print-screen?

4
Have you tried having more files on the desktop than will fit in it?

5
By the way, for regular file management Pcmanfm is just as beautiful and feature-packed as Nemo but snappier. I'd recommend it to the devs.

6
Already have a panel with Files. It is the desktop management that is changed with the above instructions/notes.

"why would you want pcmanfm over nemo ?"

Because nemo's desktop management has a memory leak that eventually slows everything down.

7
Pcmanfm solves it.

apt-get install pcmanfm

xed .config/pcmanfm/default/desktop-items-0.conf
Change the font line to this bigger font:
desktop_font=Sans 14
Change this line if another color is wanted for the desktop:
desktop_bg=#000000

Add an autostart item for "pcmanfm --desktop" under Peppermint Settings Panel - System - Startup & Default Applications - Autostart:
Add pcmanfm --desktop
Disable Nemo

Log out and log in.

Pcmanfm is a little snappier too, compared to Nemo. Wondering why it is not preferred.

8
So the question is then how do I keep Nemo as a file manager because it is nice and has a search function too but dump nemo-desktop and have a black desktop with an alternative file manager (which?) or with plain X11 settings?

9
The nemo-desktop binary has a bug that causes it to use more and more memory, probably indefinitely, if there are too many files on the desktop. Maybe it happens with fewer files too. So I kill nemo-desktop when this happens and lose the feature of files on the desktop, while regular Nemo still works. Would rather nemo-desktop did not autostart, to avoid the trouble of everything slowing down when the swap space is eventually used.

10
Nemo autostart can be disabled under Peppermint Settings Panel - System - Startup & Default Applications. This leaves a gray desktop. How can the desktop be made black?

11
Those 20 seconds of wait till the desktop appears are not ok. The whole point of this exercise is productivity, while staying secure with separate VM's for different sites. Just discovered that the problem does not occur at all with the live CD. Maybe I ought to try and install peppermint on a brand new VM and see if it happens there. Any other ideas to try before doing that?

12
Nice command that. Here's the output:

f: /home/user/.cache/dconf/user
 drwxr-xr-x root root /
 drwxr-xr-x root root home
 drwxrwxr-x user user user
 drwxrwxr-x user user .cache
 drwx------ root root dconf
 -rw------- root root user

This is a hack really but these two commands:

chmod 777 /home/user/.cache/dconf
chmod 777 /home/user/.cache/dconf/user

remove the error and you get another load of errors:

# cat nohup.out

(nemo-desktop:3569): GLib-GIO-CRITICAL **: 00:00:31.650: g_dbus_proxy_new_sync: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(nemo-desktop:3569): libunity-CRITICAL **: 00:00:37.701: unity-launcher.vala:157: Unable to connect to session bus: Could not connect: Connection refused

(nemo-desktop:3569): libunity-CRITICAL **: 00:00:40.737: unity-launcher.vala:157: Unable to connect to session bus: Could not connect: Connection refused

(nemo-desktop:3569): GLib-CRITICAL **: 00:00:40.746: g_strstr_len: assertion 'haystack != NULL' failed
** Message: 00:00:40.746: nemo-desktop: session is not cinnamon (checked XDG_SESSION_DESKTOP,DESKTOP_SESSION environment variables.) Applying default behavior

(nemo-desktop:3569): GLib-CRITICAL **: 00:00:40.747: g_variant_new_string: assertion 'g_utf8_validate (string, -1, NULL)' failed

(nemo-desktop:3569): GLib-CRITICAL **: 00:00:43.767: g_variant_new_string: assertion 'g_utf8_validate (string, -1, NULL)' failed

(nemo-desktop:3569): GLib-CRITICAL **: 00:00:43.768: g_variant_new_string: assertion 'g_utf8_validate (string, -1, NULL)' failed

(nemo-desktop:3569): GLib-CRITICAL **: 00:00:43.768: g_variant_new_string: assertion 'g_utf8_validate (string, -1, NULL)' failed

(nemo-desktop:3569): LIBDBUSMENU-GLIB-WARNING **: 00:00:43.769: Unable to get session bus: Could not connect: Connection refused

(nemo-desktop:3569): LIBDBUSMENU-GLIB-WARNING **: 00:00:43.769: Unable to get session bus: Could not connect: Connection refused

(nemo-desktop:3569): Gtk-WARNING **: 00:00:43.893: Invalid input string

(nemo-desktop:3569): Gtk-WARNING **: 00:00:43.894: Invalid input string

(nemo-desktop:3569): GLib-CRITICAL **: 00:00:43.905: g_variant_new_string: assertion 'g_utf8_validate (string, -1, NULL)' failed

(nemo-desktop:3569): GLib-CRITICAL **: 00:00:43.905: g_variant_new_string: assertion 'g_utf8_validate (string, -1, NULL)' failed

(nemo-desktop:3569): GLib-CRITICAL **: 00:00:43.905: g_variant_new_string: assertion 'g_utf8_validate (string, -1, NULL)' failed

(nemo-desktop:3569): GLib-CRITICAL **: 00:00:43.906: g_variant_new_string: assertion 'g_utf8_validate (string, -1, NULL)' failed

(nemo-desktop:3569): Gtk-WARNING **: 00:00:43.906: Invalid input string

(nemo-desktop:3569): Gtk-WARNING **: 00:00:43.906: Invalid input string

(nemo-desktop:3569): Gtk-WARNING **: 00:00:43.906: Invalid input string

But 20 seconds later, the files appear on the desktop as if nemo-desktop is happy.

13
Same thing happens except the errors go to nohup.out.

Tried gksudo -u user nemo-desktop and it still happens. Is nemo-desktop launched from a script at boot time that we can copy from?

14
One would think that root can run anything as if he were any user, using sudo -u like this:

pkill nemo-desktop
sudo -u user nemo-desktop &

It does not work. It produces this error:

(nemo-desktop:4378): dconf-CRITICAL **: 16:50:26.008: unable to create file '/home/user/.cache/dconf/user': Permission denied. dconf will not work properly.

But it works if you're an ordinary user. What's the proper way to restart nemo-desktop if you're root? This is needed when resuming VM's where vmware allows you to run your own script as root.

15
I don't know, sorry.

Pages: [1] 2 3 4