<solved> nemo and thunar suddenly started hanging

[sadhu]

See my signature for versions. This is happening on the desktop.

Suddenly I'm getting the message 'not responding' and nemo freezes.

I tried reinstalling all the nemo stuff using synaptic, but no luck. Rebooting doesn't help.

I just did an update (tiff), if that's of any help. At any rate nemo was working an hour ago and all afternoon, but not now.

This is a terminal response

Code: Select all

$nemo-desktop
** Message: nemo-desktop: session is cinnamon, establishing proxy

(nemo:27384): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint64: assertion 'G_IS_FILE_INFO (info)' failed

(nemo:27384): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint64: assertion 'G_IS_FILE_INFO (info)' failed

(nemo:27384): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint64: assertion 'G_IS_FILE_INFO (info)' failed
Could not register nemo as a remote: Timeout was reached
Could not register nemo as a remote: Timeout was reached
Could not register nemo as a remote: Timeout was reached

(nemo:27384): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint64: assertion 'G_IS_FILE_INFO (info)' failed

(nemo:27384): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint64: assertion 'G_IS_FILE_INFO (info)' failed

(nemo:27384): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint64: assertion 'G_IS_FILE_INFO (info)' failed

Starting nemo itself from a terminal window gives no response.
-sadhu

[AZgl1800]

you need to provide us the output of inxi -Fzxd

post the results in between the CODE tags above the editor < / >

[Acewiza]

you need to provide us the output of inxi...

S'cuse me, just curious, but what nemo/thunar-specific inxi output might you be looking for?

[Acewiza]

Let me guess - it just magically started working again?

[sadhu]

you need to provide us the output of inxi -Fzxd

post the results in between the CODE tags above the editor < / >

Code: Select all

sadhu@desk ~ $ sudo inxi -Fzxd
[sudo] password for sadhu: 
System:    Host: desk Kernel: 4.4.0-109-generic x86_64 (64 bit gcc: 5.4.0)
           Desktop: Cinnamon 3.6.7 (Gtk 3.18.9-1ubuntu3.3)
           Distro: Linux Mint 18.3 Sylvia
Machine:   Mobo: ASUSTeK model: STRIX B250G GAMING v: Rev X.0x
           Bios: American Megatrends v: 0810 date: 09/13/2017
CPU:       Dual core Intel Pentium G4560 (-HT-MCP-) cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 14017
           clock speeds: max: 3500 MHz 1: 799 MHz 2: 799 MHz 3: 799 MHz
           4: 799 MHz
Graphics:  Card: Intel HD Graphics 610 bus-ID: 00:02.0
           Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa)
           tty size: 80x24 Advanced Data: N/A for root
Audio:     Card-1 Intel 200 Series PCH HD Audio
           driver: snd_hda_intel bus-ID: 00:1f.3
           Card-2 C-Media CM108 Audio Controller
           driver: USB Audio usb-ID: 001-007
           Sound: Advanced Linux Sound Architecture v: k4.4.0-109-generic
Network:   Card: Intel Ethernet Connection (2) I219-V
           driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6
           IF: enp0s31f6 state: down mac: <filter>
Drives:    HDD Total Size: 3120.6GB (61.5% used)
           ID-1: /dev/sda model: KINGSTON_SV300S3 size: 120.0GB temp: 32C
           ID-2: /dev/sdb model: WDC_WD10EZEX size: 1000.2GB temp: 31C
           ID-3: /dev/sdc model: WDC_WD10EZEX size: 1000.2GB temp: 31C
           ID-4: USB /dev/sdd model: External_USB_3.0 size: 1000.2GB temp: 0C
           Optical: No optical drives detected.
Partition: ID-1: / size: 24G used: 18G (79%) fs: ext4 dev: /dev/sda7
           ID-2: swap-1 size: 3.89GB used: 0.00GB (0%) fs: swap dev: /dev/sda8
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C
           Fan Speeds (in rpm): cpu: 0
Info:      Processes: 252 Uptime: 4 min Memory: 1367.4/3819.7MB
           Init: systemd runlevel: 5 Gcc sys: 5.4.0
           Client: Shell (sudo) inxi: 2.2.35 

[sadhu]

Let me guess - it just magically started working again?

You wish. Me too.

BTW thunar will run up to about 5 mins before it hangs. ps aux shows thunar & nemo both running.

Now that I've run Nautilus (I needed SOMETHING to handle file activities) nemo-desktop doesn't have any effect, and I'm stuck with some other desktop handler, which I don't like.

Also, after killing all nemo processes (the icons on the desktop disappear), then running in the command line
nemo-desktop & --(I get a response that another handler is running)
nemo & --(nothing happens)
ps aux -- reveals both are running.
sudo find / -type f -name org.nemo.desktop --finds nothing. Where to find this setting?


-sadhu

[sadhu]

Further notes:
After rebooting and fiddling around a bit, I restarted cinnamon, killed all nemo processes, then entered

Code: Select all

 $ nemo-desktop

(nemo-desktop:4074): Gtk-WARNING **: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
** Message: nemo-desktop: session is cinnamon, establishing proxy
Loading Desktop module

^Z
[1]+  Stopped                 nemo-desktop
sadhu@desk ~ $ bg
[1]+ nemo-desktop &

So nemo-desktop is now running and the desktop is back. I clicked the 'Files' icon on the panel, then clicked a directory icon on the desktop. I then ran ps aux | grep nemo, and got this

Code: Select all

sadhu     4074  2.0  1.5 1237108 61204 pts/0   Sl   13:39   0:02 nemo-desktop
sadhu     4164  0.6  1.4 902468 55860 ?        Sl   13:40   0:00 nemo
sadhu     4262  0.4  0.5 389468 22340 pts/0    Sl   13:41   0:00 nemo /ddr/shared_config/desktops/desk/wods-in-winter
sadhu@desk ~ $ Could not register nemo as a remote: Timeout was reached

A moment later a non-functioning nemo window appeared, probably due to clicking the icon on the panel. Which is what the "could not register nemo" message is about, I suspect.

[Acewiza]

I'm pretty sure a good clue was in the first code snippet you posted. Still wondering what anyone expects inxi to find, under the circumstances.

What have you been doing with/to the network?

[sadhu]

Network? Nothing that I know of. Maybe I ran into a flaky site when I was browsing using Tor without stopping Javascript.

At any rate, I"ve solved the problem: I re-installed LM18.3-64.

Thanks to all
-Sadhu

[catweazel]

you need to provide us the output of inxi...

S'cuse me, just curious, but what nemo/thunar-specific inxi output might you be looking for?

Who imagined that the output ought to be specific to nemo or thunar?

At the very least, the output of inxi will assist people to decide if they can or should get involved. For example, I avoid offering assistance if the inxi output indicates certain configurations are present. There was absolutely nothing wrong with John's request for it. Nothing.

[sadhu]

For example, I avoid offering assistance if the inxi output indicates certain configurations are present. There was absolutely nothing wrong with John's request for it. Nothing.

Just wondering--- was there anything in my configuration that would cause you to avoid offering assistance?

-Sadhu

[catweazel]

For example, I avoid offering assistance if the inxi output indicates certain configurations are present. There was absolutely nothing wrong with John's request for it. Nothing.

Just wondering--- was there anything in my configuration that would cause you to avoid offering assistance?

No

[sadhu]

[catweazel]

The reason I do it is to ensure I don't end up causing you more woes than you already have. I don't like guessing

[sadhu]

Well, Mr. Cat, sometimes I've posted queries that received no responses, so after a while I usually take the posts down, but all the while I wonder if I have bad breath or something. Now it turns out that you don't respond if there's a bad config. It would be nice, therefore, if you could respond to a bad configuration --- maybe with some boilerplate text saying saying that there's something wrong with the config.

I suppose this could open up an even bigger can of worms...


But thanks for your answers and help over the years!

-Sadhu

[Acewiza]

Who imagined that the output ought to be specific to nemo or thunar?

My guess would be the person who asked for it, but since you asked, what's your point? You seem to be the one making imaginative interruptions here.

At the very least, the output of inxi will assist people to decide if they can or should get involved...

I'd expect a scripted response from the M$ or Amazon help desk. I get a little nauseous when the community starts doing it. Evaluate your involvement potential, huh? Interesting....

[MrEen]

How 'bout partition full, memory maxed out, graphics mixmatch, system overheating, known problematic kernel? All could cause strange issues. The inxi output would be helpful then.

It also gives the Mint version. That comes in handy if system files need to be edited.

[catweazel]

Who imagined that the output ought to be specific to nemo or thunar?

My guess would be the person who asked for it...

Wrong guess.

[sadhu]

c'mon folks, whaddya say we just let this whole thread die?