Could I get a bump? I installed the recent Betsy updates, and now have
Code: Select all
$ date ; cinnamon --version
Thu Apr 28 18:09:21 MST 2016
Cinnamon 3.0.1
But I still have the same problem with `cinnamon --replace` that I had with cinnamon-2.8.6, and which I did
not have with cinnamon-2.6.13 or before:
TomRoche wrote:In the new version, when I run `cinnamon --replace`, it does not return. Worse yet, if I either
* hit C-c in the terminal in which `cinnamon --replace` is running
* close the terminal in which `cinnamon --replace` is running
Cinnamon dies violently:
* desktop background goes black (though all previous desktop windows, icons, and panel continue to display)
* desktop windows lose their frames
* mouse moves, but won't interact with anything
* keyboard fails: no keychords have any effect other than C-A-F1 etc.
At which point my only option appears to be to goto tty1, shutdown those applications which can be shutdown cleanly from a terminal (e.g., Emacs), and reboot.
Note that I currently get the following spew when I run `cinnamon --replace` in a terminal:
Code: Select all
$ date ; cinnamon --replace
> Thu Apr 28 18:11:19 MST 2016
> Cjs-Message: JS LOG: About to start Cinnamon
> St-Message: cogl npot texture sizes SUPPORTED
> Cjs-Message: JS LOG: Cinnamon started at Thu Apr 28 2016 18:11:20 GMT-0700 (MST)
> Cjs-Message: JS WARNING: [/home/me/.local/share/cinnamon/applets/multicore-sys-monitor@ccadeptic23/DataProviders.js 390]: assignment to undeclared variable mountedDirList
> Cjs-Message: JS LOG: network applet: Cannot find connection for active (or connection cannot be read)
> Cjs-Message: JS LOG: network applet: Cannot find connection for active (or connection cannot be read)
> Window manager warning: Log level 16: Symbolic icon /usr/share/cinnamon/applets/windows-quick-list@cinnamon.org/icons/windows-quick-list-symbolic.svg is not in an icon theme directory
> openGL version 3.3 detected (GL Cogl Driver)
> Window manager warning: Log level 16: STACK_OP_REMOVE: window 0x288 not in stack
> Cjs-Message: JS LOG: Invalid network device type, is 13
> Cjs-Message: JS LOG: Invalid network device type, is 14
> Cjs-Message: JS LOG: network applet: Found connection for active
> Cjs-Message: JS LOG: network applet: Found connection for active
> Window manager warning: Log level 16: Symbolic icon /usr/share/cinnamon/applets/windows-quick-list@cinnamon.org/icons/windows-quick-list-symbolic.svg is not in an icon theme directory
after which nothing (no further messages, no return to prompt).
Note my motivation for wanting a working `cinnamon --replace` remains the same, though I have not yet used cinnamon-3.0.1 long enough to know its memory-usage behavior: Cinnamon (or some component--perhaps an applet?) seems to increase its memory consumption over time, as if it has a memory leak. Specifically:
1. When I reboot and start my Cinnamon-running laptop "fresh" I get (and have for many months) approximately the following memory usage per applet=`multicore-sys-monitor@ccadeptic23`: 11% usedup, 11% cached, 1% buffer, 77% free, 0% swap. Note that "fresh" means no running applications other than Cinnamon (i.e., the desktop), Update Manager, the HPLIP print manager (aka `HP Device Manager`), and a few applets: the above plus `
user@cinnamon.org`, `
network@cinnamon.org`, `
sound@cinnamon.org`, `
power@cinnamon.org`, `
calendar@cinnamon.org`, `
windows-quick-list@cinnamon.org`.
2. I periodically run my
recover_memory scripts to ... recover memory. The
driver formerly ran `cinnamon --replace` but can no longer due to the problem documented in this thread.
3. In the past (through cinnamon-2.6.13), I could approximate the "fresh" situation by
3.1. shutdown all other applications
3.2. run my recover_memory driver (which called `cinnamon --replace`)
after which, usedup memory would never get all-the-way down to 11%, but it would reliably (and more importantly, repeatably) get down to ~15%.
4. For at least cinnamon-2.8.6 (I just started using cinnamon-3.0.1, so dunno yet if it will reproduce the previous behavior), when I
4.1. shutdown all other applications
4.2. run my recover_memory driver (which cannot call `cinnamon --replace`)
usedup memory increases monotonically by ~5-10% per week. (I usually reboot after it hits ~40% post-recover_memory.) The only exception is ...
5. If I am "fortunate" enough to get a Cinnamon crash (which is, to the credit of the Cinnamon team, very infrequent) (and which I have yet to experience with cinnamon-3.0.1), I can subsequently
5.1. shutdown all other applications
5.2. run my recover_memory driver (which cannot call `cinnamon --replace`)
after which, "fresh" usedup memory will again get down to ~15%! So there does still seem to be (at least with cinnamon-2.8.6) some memory-usage advantage to restarting Cinnamon ... but I don't know how to script that anymore.
Hence I'd
still like to know
TomRoche wrote:
1. is [the failure of `cinnamon --replace`] a bug? If so, where should I file it?
2. is there a new way to restart Cinnamon programmatically and recover its usedup memory?