Bug 98918 - kdm fails to 'Turn Off Computer' as advertized
Summary: kdm fails to 'Turn Off Computer' as advertized
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-kde (group)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-14 02:20 UTC by Brad Huntting
Modified: 2006-06-17 17:50 UTC (History)
0 users

See Also:


Attachments
file.diff (715 bytes, patch)
2006-06-14 02:20 UTC, Brad Huntting
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Brad Huntting 2006-06-14 02:20:12 UTC
	kdm's 'Turn Off Computer' button halts the machine, but
	does not power down.

	There was a time (before portupgrade) when this bug seemed
	only a minor anoyance.  But with the magic of 'portupgrade
	-a', and the increasing age of my brain, I now get burned
	every time the kdebase port changes.

Fix: The fix would appear to be trivial:
How-To-Repeat: 	run kdm (on laptop)
	press 'Turn Off Computer'
	unplug power cord
	board airplane
	deplane to find dead battery
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2006-06-14 02:32:57 UTC
Responsible Changed
From-To: freebsd-ports-bugs->kde

Over to maintainer
Comment 2 Michael Nottebrock freebsd_committer freebsd_triage 2006-06-14 16:59:35 UTC
It certainly makes sense to change the default to -p - you can however adjust
the reboot/halt commands through the KDE Control Center (Login Manager), and
these settings will persist through portupgrades as well.
Comment 3 Michael Nottebrock freebsd_committer freebsd_triage 2006-06-14 20:15:56 UTC
State Changed
From-To: open->closed

Fixed, thanks for reporting!
Comment 4 huntting 2006-06-15 10:02:08 UTC
> It certainly makes sense to change the default to -p - you can
> however adjust the reboot/halt commands through the KDE Control
> Center (Login Manager), and these settings will persist through
> portupgrades as well.

Not so.  Unfortunately, changes to kdmrc do not persist through
portupgrades.  They are overritten by genkdmconf every time kdebase
is updated.


brad
Comment 5 Michael Nottebrock freebsd_committer freebsd_triage 2006-06-16 07:19:39 UTC
Yes, they do. genkdmconf parses the existing configuration and keeps 
modifications intact or translates them to the new format if the 
configuration file layout has changed.
Comment 6 huntting 2006-06-16 20:46:37 UTC
> Yes, they do. genkdmconf parses the existing configuration and keeps 
> modifications intact or translates them to the new format if the 
> configuration file layout has changed.

Well, I know that's what it's supposed to do.  But ever since I
first started using portupgrade and kde (a few years ago), I've
found myself reediting my kdmrc file a couple times every year
because something has overwritten the 'shutdown -p now' command.
The most recent insident was just a few weeks ago.


brad
Comment 7 Michael Nottebrock freebsd_committer freebsd_triage 2006-06-16 23:34:40 UTC
The ports haven't been overwriting kdmrc for a good while now, and certainly 
not as recent as a few weeks ago. I myself have been carrying over a 
customized kdmrc since at least KDE 3.4 (which is also why I managed to 
continually miss the fact that the default HALT_CMD was still shutdown -h).
Comment 8 huntting 2006-06-17 17:44:05 UTC
> The ports haven't been overwriting kdmrc for a good while now, and certainly 
> not as recent as a few weeks ago. I myself have been carrying over a 
> customized kdmrc since at least KDE 3.4 (which is also why I managed to 
> continually miss the fact that the default HALT_CMD was still shutdown -h).

Ok, I probably fat fingered something somewhere.  I keep such files
RCSed, perhaps I forgot to check in the shutdown -p change and
subsequently lost it.


thanx,
brad