Welcome, Guest. Please login or register.
April 19, 2014, 12:34:24 PM
Home Help Search Calendar Login Register
Show unread posts since last visit.
News: Let Pardus-Anka become #1: Pardus-Anka Bug ReportPardus-Anka World Google+ | The Pardus wiki  | Visit Pardus-Anka official website  | Register as forum member?  Email the moderator!

+  Pardus Worldforum
|-+  Assistance
| |-+  Pardus for beginners
| | |-+  My login manager is lying to me.
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: 1 [2] Go Down Print
Author Topic: My login manager is lying to me.  (Read 2542 times)
JoanRC
Pardus fellow craft
**
Posts: 39



View Profile
« Reply #15 on: August 08, 2010, 21:28:15 PM »

Yes, there is. Here is the screenshot:



* snapshot25.png (28.71 KB, 537x460 - viewed 89 times.)
Logged

Remember: only you can prevent forum fires!
atolboo
Pardus Guru
****
Posts: 2317



View Profile
« Reply #16 on: August 08, 2010, 21:39:18 PM »

Try "Start with an empty session" + Apply.
And maybe luck is coming your way Wink
Logged
JoanRC
Pardus fellow craft
**
Posts: 39



View Profile
« Reply #17 on: August 08, 2010, 23:27:47 PM »

No luck.  My new user is the only account that can log in at the graphical login screen and shutdown or reboot from the desktop.
My root and original user can only log out from the desktop. There is a small difference between the two: root can interact with the logout notification screen, i.e. cancel logout if I choose. But original user cannot. I doubt that has any significance here.

There is an errormessage when I am logged out to konsole after choosing reboot at the desktop in root account. It says kde4 is crashing:

failed to conncet  /tmp/dbus-8wuKqv6UPt  connection refused
KUniqueApplication:Pipeclosed unexpectedly
Socket Notifier:Invalid socket 15 and type 'Read' disabling
Konqi: cannot connect to Xserver :0.0

I'm guessing that's because I set Pardus to clean out my /tmp directory on closing, as per your previous advice to tame my runaway /tmp directory.
Logged

Remember: only you can prevent forum fires!
atolboo
Pardus Guru
****
Posts: 2317



View Profile
« Reply #18 on: August 09, 2010, 00:23:26 AM »

I'm guessing that's because I set Pardus to clean out my /tmp directory on closing, as per your previous advice to tame my runaway /tmp directory.
I do not think so as the new user doesn't have the problem.
And the /tmp directory is common to all users.
On my test computer I can not reproduce the problem whatever I do.
As far as I am concerned it's a once in a lifetime occurrence.
And the final solution can also be a re-installation.
Logged
JoanRC
Pardus fellow craft
**
Posts: 39



View Profile
« Reply #19 on: August 09, 2010, 00:31:49 AM »

Thank you for your heroic attempts to resolve this issue. I really did not expect anyone would go to such lengths to resolve a relatively unimportant issue.

However, I have learned a lot during this process. So, it has been usefull for me.
Logged

Remember: only you can prevent forum fires!
atolboo
Pardus Guru
****
Posts: 2317



View Profile
« Reply #20 on: August 09, 2010, 12:32:24 PM »

As I can not create the situation, I can only give the following hint to track down the affected file(s):

Create and login a new user and abort Kaptan.
In Dolphin goto  and right-click directory /home/old_user > Root actions > Change Permissions > Yes to "Do you wish... " > mark "Group/Others: readable > OK.
In Dolphin > Split  >  mark "Show Hidden Files (<repeat for every window) and you can copy file(s)/directory from old_user to new_user.
And in this way (and maybe repeat this procedure) try to find the file/directory which is responsible for this behavior.

Kdiff3 (from Package Manager) can be a big help to get an overview of differences in file(s) in a directory and can also show the actual difference in a particular file.
« Last Edit: August 09, 2010, 13:08:50 PM by atolboo » Logged
atolboo
Pardus Guru
****
Posts: 2317



View Profile
« Reply #21 on: August 09, 2010, 21:54:05 PM »

Have a look in System Settings > Advanced > Session Manager > General
  Is there a mark at "Offer shutdown options"
A change of the above setting results in a change of the file /home/your_username/.kde4/share/config/session/ksmserverrc
with variables "offerShutdown" and "shutdownType".
« Last Edit: August 09, 2010, 22:03:01 PM by atolboo » Logged
JoanRC
Pardus fellow craft
**
Posts: 39



View Profile
« Reply #22 on: January 19, 2011, 23:29:43 PM »

A recent kernel upgrade solved this issue. I still don't know what happened; but, at least it's resolved.
« Last Edit: January 19, 2011, 23:31:44 PM by JoanRC » Logged

Remember: only you can prevent forum fires!
Pages: 1 [2] Go Up Print 
« previous next »
Jump to:  


Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!