[Bug 50014] Re: KDM makes KDE startup troubleshooting difficult
Bug Watch Updater
50014 at bugs.launchpad.net
Sat Jul 13 10:30:59 UTC 2013
Launchpad has imported 31 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=81653.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
------------------------------------------------------------------------
On 2004-05-15T21:14:46+00:00 Thorsten Staerk wrote:
Version: (using KDE KDE 3.2.0)
Installed from: SuSE RPMs
Two different ordinary users cannot log in one after the other when on
the harddisk (containing / and ~) is no space left.
There should be an error msg.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
workspace/+bug/50014/comments/0
------------------------------------------------------------------------
On 2004-05-22T15:53:01+00:00 Oswald Buddenhagen wrote:
see bug #81597 for a related comment.
note that space requirements are pretty individual, so it is hard to define some generally useful limits.
anyway, i agree that kde could check for "disk low" situations at startup, possibly by doing a ratio calculation on the df output or whatever. this is not kdm's task, though.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-workspace/+bug/50014/comments/1
------------------------------------------------------------------------
On 2004-05-22T18:46:31+00:00 Thorsten Staerk wrote:
most important to me (!) is that the users do not get the feeling "it just logs me out again when I log in".
Then, there should come up a message "Logging you out again because no space left". That would make error tracking more easy.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
workspace/+bug/50014/comments/2
------------------------------------------------------------------------
On 2004-07-29T14:30:28+00:00 N-bastian wrote:
ksmserver checks for disk full and some other common problems and
informs the user.
Seems like that check doesn't work too well then.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
workspace/+bug/50014/comments/3
------------------------------------------------------------------------
On 2004-07-31T17:56:10+00:00 N-bastian wrote:
I notice that if /tmp is unwritable (e.g. due to a full disk) the X
server will not fully come up and startkde is never executed, so
ksmserver will not have a chance to tell anything to the user.
So I suggest that kdm adopts some of the sanity checks from
ksmserver/main.cpp
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-workspace/+bug/50014/comments/4
------------------------------------------------------------------------
On 2005-03-13T23:08:30+00:00 Oswald Buddenhagen wrote:
*** Bug 101446 has been marked as a duplicate of this bug. ***
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
workspace/+bug/50014/comments/5
------------------------------------------------------------------------
On 2007-02-10T17:17:48+00:00 Oswald Buddenhagen wrote:
*** Bug 138232 has been marked as a duplicate of this bug. ***
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
workspace/+bug/50014/comments/7
------------------------------------------------------------------------
On 2007-03-10T10:47:35+00:00 Oswald Buddenhagen wrote:
*** Bug 142775 has been marked as a duplicate of this bug. ***
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
workspace/+bug/50014/comments/8
------------------------------------------------------------------------
On 2008-03-12T16:40:44+00:00 FiNeX wrote:
*** Bug 159180 has been marked as a duplicate of this bug. ***
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
workspace/+bug/50014/comments/9
------------------------------------------------------------------------
On 2008-05-21T02:21:07+00:00 Daniel Nicoletti wrote:
Hi,
If someone give me the directions to what is the first app called in startkde i can write a simple pach that:
Check for quotas and full disk space at startUp and simply do a
KMessageBox::Warning("You runned out of space, free some files or buy a new HD :P")
then start dolphin after that check again to see if there's is at least "5 mb" free and start kde otherwise warn again...
i can also do a system service that could check periodicaly for space and quotas, if someone know if there is some working in progress or where should i do that i'll appreciate, someone told me that solid should have something like this.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-workspace/+bug/50014/comments/10
------------------------------------------------------------------------
On 2008-06-24T20:59:59+00:00 Oswald Buddenhagen wrote:
*** Bug 164853 has been marked as a duplicate of this bug. ***
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
workspace/+bug/50014/comments/11
------------------------------------------------------------------------
On 2008-06-24T21:10:08+00:00 Laurent Claessens wrote:
One should think about a warning in the logout instead of the login.
If you try to logout while there is only 0M free, you should be warned
that you will no more be able to login again.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-workspace/+bug/50014/comments/12
------------------------------------------------------------------------
On 2008-06-24T21:45:20+00:00 Matthias Heinz wrote:
Doesnt make much sense. Think of a multi user system. Why should a user
care about the next user?
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
workspace/+bug/50014/comments/13
------------------------------------------------------------------------
On 2008-11-29T14:49:33+00:00 Thorsten Staerk wrote:
I think I have an idea how to fix this, assigning from kdm-bugs-
null at kde.org to me
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
workspace/+bug/50014/comments/14
------------------------------------------------------------------------
On 2008-11-30T17:07:20+00:00 Thorsten Staerk wrote:
still exists for KDE from today
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
workspace/+bug/50014/comments/15
------------------------------------------------------------------------
On 2008-11-30T18:43:44+00:00 Thorsten Staerk wrote:
As far as I can see, kdm does not call startkde. So, yes, sanity checks
in kdm are needed.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-workspace/+bug/50014/comments/16
------------------------------------------------------------------------
On 2008-11-30T19:30:25+00:00 Thorsten Staerk wrote:
kdm's possible session types (KDE, GNOME etc) are defined in .desktop
files in $KDEDIR/share/apps/kdm/sessions. There is also stated where the
startkde resides that will be started by kdm. This brought me on the
wrong track - kdm does call startkde.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
workspace/+bug/50014/comments/17
------------------------------------------------------------------------
On 2008-11-30T19:40:35+00:00 Thorsten Staerk wrote:
(In reply to comment #4)
> I notice that if /tmp is unwritable (e.g. due to a full disk) the X server will
> not fully come up and startkde is never executed, so ksmserver will not have a
> chance to tell anything to the user.
>
> So I suggest that kdm adopts some of the sanity checks from ksmserver/main.cpp
>
wrong. startkde IS executed, I just tested this scenario.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-workspace/+bug/50014/comments/18
------------------------------------------------------------------------
On 2008-11-30T20:28:08+00:00 Oswald Buddenhagen wrote:
some bugs were fixed since waldo made that comment. ;)
it is still possible that it wouldn't even get to run ksmserver - e.g., if /home is shared with /tmp and the user has a strict quota or the disk is simply *completely* full.
if you want to do it Right™,you need to create pam_diskfull (google first - maybe somebody already did :).
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-workspace/+bug/50014/comments/19
------------------------------------------------------------------------
On 2008-11-30T20:37:04+00:00 Thorsten Staerk wrote:
Thanks Oswald, but I tested in a completely-full-situation.
startkde is started, but it cannot access X (no xclock, no xmessage,
...). So my proposal is the startkde should return a special value (say
5) to indicate it found there is no more space on /tmp. kdm would need
to react on this value - does this find your placet, Ossi?
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
workspace/+bug/50014/comments/20
------------------------------------------------------------------------
On 2008-12-01T00:25:00+00:00 Oswald Buddenhagen wrote:
bah, so the error while writing the Xauth temp file still goes
undetected and the x server later refuses to allow clients to connect.
this needs to be fixed.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-workspace/+bug/50014/comments/21
------------------------------------------------------------------------
On 2009-06-02T15:32:09+00:00 L-lunak-5 wrote:
*** Bug 191452 has been marked as a duplicate of this bug. ***
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
workspace/+bug/50014/comments/22
------------------------------------------------------------------------
On 2009-06-02T15:52:07+00:00 Richih-kde wrote:
Why is this severity wishlist? In the case I encountered in
https://bugs.kde.org/show_bug.cgi?id=191452 , the laptop was completely
and utterly broken for my girlfriend. Thankfully, I was near so I could
fix it for her.
Otherwise the laptop would have been, literally, useless to her.
If this happens while someone is abroad etc, this is a major issue!
PS: Warning at logout may help, but a warning within kdm, and a way to
fix it, are needed.
Unless someone objects Real Soon, I will raise the severity to critical or major as per https://bugs.kde.org/page.cgi?id=fields.html#bug_severity
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
workspace/+bug/50014/comments/23
------------------------------------------------------------------------
On 2009-06-03T12:43:25+00:00 Richih-kde wrote:
As per discussion in #kde-devel, I am setting this to grave. It will
probably not help fixing anything, but at least it's tagged correctly.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
workspace/+bug/50014/comments/24
------------------------------------------------------------------------
On 2009-06-03T12:48:34+00:00 Richih-kde wrote:
http://www.kernel.org/pub/linux/libs/pam/modules.html does not list
anything which could help.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
workspace/+bug/50014/comments/25
------------------------------------------------------------------------
On 2009-06-03T17:26:08+00:00 Richih-kde wrote:
I sent email to upstream.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
workspace/+bug/50014/comments/26
------------------------------------------------------------------------
On 2009-11-07T10:41:21+00:00 FiNeX wrote:
A related bug is this: bug #205630 .
If the disk is full the splash screen is drawn over the messagebox which
indicate that the disk is full, so if the user wait for the login
without a mouse click, he will never know that the disk is full because
the message is hidden.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
workspace/+bug/50014/comments/28
------------------------------------------------------------------------
On 2011-03-25T14:19:54+00:00 Nick Shaforostoff wrote:
is 194806 a duplicate of this bug?
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
workspace/+bug/50014/comments/29
------------------------------------------------------------------------
On 2011-03-25T15:25:27+00:00 Oswald Buddenhagen wrote:
no, this report is currently about missing/incorrect error handling (see
comment #20). the other one is about a workaround (quite a hack, in
fact).
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
workspace/+bug/50014/comments/30
------------------------------------------------------------------------
On 2011-05-13T14:20:18+00:00 Nick Shaforostoff wrote:
i'm thinking about extending disk monitor plasma applet to give a
notification to user when the disk space is full
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
workspace/+bug/50014/comments/31
------------------------------------------------------------------------
On 2011-05-13T15:17:14+00:00 Richih-kde wrote:
While that is helpful in general, this does not help if something else
filled the disk or the user does not comprehend the warning.
Background processes, daemons or other users might have filled the disk.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
workspace/+bug/50014/comments/32
** Bug watch added: KDE Bug Tracking System #191452
https://bugs.kde.org/show_bug.cgi?id=191452
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in Ubuntu.
https://bugs.launchpad.net/bugs/50014
Title:
KDM makes KDE startup troubleshooting difficult
To manage notifications about this bug go to:
https://bugs.launchpad.net/kde-baseapps/+bug/50014/+subscriptions
More information about the kubuntu-bugs
mailing list