Hello,
Thank you very much, indeed it was the solution, I modified the file kdmrc
and now I have a complete stop of the computer. It will allow me to close
the Bug 761647 of 15/09/2014 which I had created to indicate the
problem. A supplementary question, know you why Kde dish one mattering
Hey,
A supplementary question, know you why Kde dish one mattering time before
throwing the hand to systemd?
You mean, why kde taks so long till systemd actully shuting down the pc?
Well KDE is asking everything to shutdown nicely and waits for reply. If there
is anything that awnsers, I need
Hello,
First on my computer it's an Debian Sid up to date and kde 4.14.2.
First of all I would want to congratulate the Kde team on its really fantastic
work.
However I collide with Kde with a problem which bores me a lot.
When I click to Switch off the computer in Kde, the current duration of
Hi,
Not the same behaviour here : computer and akonadi close fast.
However I remember some closing problems in akonadi in the past. What kde
version are you running ?
Which startup system (sysvinit, upstart, systemd) ?
How it works if you try to stop your computer from a fresh test account ?
Le jeudi 11 décembre 2014, 14:57:46 Xavier Brochard a écrit :
Hi,
Not the same behaviour here : computer and akonadi close fast.
However I remember some closing problems in akonadi in the past. What
kde
version are you running ?
Which startup system (sysvinit, upstart, systemd) ?
How it
I believe the problem is memory. Sign out, it releases a whole bunch of memory
(KDE is not exactly economical). Get this behavior going from account to
account if I have two sessions going and log out from one.
Once the log out is done, the poweroff is very quick (systemd).
Hi,
Not the same
Le jeudi 11 décembre 2014, 18:14:02 David Baron a écrit :
I believe the problem is memory. Sign out, it releases a whole
bunch of
memory (KDE is not exactly economical). Get this behavior
going from
account to account if I have two sessions going and log out
from one.
Once the log out is
On Thursday 11 December 2014 17:56:52 MERLIN Philippe wrote:
Le jeudi 11 décembre 2014, 18:14:02 David Baron a écrit :
I believe the problem is memory. Sign out, it releases a whole
bunch of
memory (KDE is not exactly economical). Get this behavior
going from
account to account if
Le jeudi 11 décembre 2014, 19:44:59 David Baron a écrit :
On Thursday 11 December 2014 17:56:52 MERLIN Philippe wrote:
Le jeudi 11 décembre 2014, 18:14:02 David Baron a écrit :
I believe the problem is memory. Sign out, it releases a whole
bunch of
memory (KDE is not exactly
Le jeudi 11 décembre 2014, 17:06:04 MERLIN Philippe a écrit :
Le jeudi 11 décembre 2014, 14:57:46 Xavier Brochard a écrit :
How it works if you try to stop your computer from a fresh test account ?
try this, just to check if the problem comes from your kde config
First on my computer
Hey,
I think this is configurable
I would take a look at your configs from your login manager. At least kdm
handles the shutdown commad: /etc/kde4/kdm/kdmrc
regards,
sandro
--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
In data giovedì 11 dicembre 2014 19:20:23, MERLIN Philippe ha scritto:
for
information before we migrate to Systemd this problem did not exist.
Hi Philippe,
use
systemd-analyze blame
to see timing details about the boot process.
Show the results to us, too :-)
Regards
Ps my boot process took
Le jeudi 11 décembre 2014, 21:05:39 Sandro Knauß a écrit :
Hey,
I think this is configurable
I would take a look at your configs from your login manager. At least kdm
handles the shutdown commad: /etc/kde4/kdm/kdmrc
regards,
sandro
Thank you for your help,I join my
Hey,
I would suggest, that you delete your halt/reboot command to the defaults or
modify it to somthing that works for your computer.
# The command (subject to word splitting) to run to halt the system.
# Default is /sbin/shutdown -h -P now
#HaltCmd=
# The command (subject to word splitting) to
14 matches
Mail list logo
