Your message dated Sun, 16 Jan 2005 21:03:18 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug no longer relevant, so closing
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 26 Oct 2003 22:30:05 +0000
>From [EMAIL PROTECTED] Sun Oct 26 16:30:05 2003
Return-path: <[EMAIL PROTECTED]>
Received: from hawk.mail.pas.earthlink.net [207.217.120.22]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1ADtOe-0007la-00; Sun, 26 Oct 2003 16:30:04 -0600
Received: from sdn-ap-002neomahp0238.dialsprint.net ([63.186.8.238])
by hawk.mail.pas.earthlink.net with esmtp (Exim 3.33 #1)
id 1ADtOd-0004i8-00
for [EMAIL PROTECTED]; Sun, 26 Oct 2003 14:30:03 -0800
From: Craig Hempenius <[EMAIL PROTECTED]>
Organization: Craig's Place
To: [EMAIL PROTECTED]
Subject: kcontrol: unable to set clock
Date: Sun, 26 Oct 2003 17:29:59 -0600
User-Agent: KMail/1.5.4
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-4.0 required=4.0
tests=BAYES_60,HAS_PACKAGE
version=2.53-bugs.debian.org_2003_10_21
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_10_21
(1.174.2.15-2003-03-30-exp)
Package: kcontrol
Version: 3.1.3-1
Trying to set clock using KDE control center > System Administration > Date &
Time > Administrator Mode.
I get the following error:
There was an error loading the module.
Details: <this is blank>
The diagnostics is: <this is blank>
Possible reasons:
- An error occurred during your last KDE upgrade leaving an orphaned
control
- You have old third party modules lying around.
Check these points carefully and try to remove the module mentioned in the
error message. If this fails consider contacting your distributor or
packager.
........also.......
[EMAIL PROTECTED]:~$ sudo kcmshell clock
sudo: unable to lookup mobile via gethostbyname()
Password:
---------------------------------
It looks like dcopserver is already running. If you are sure
that it is not already running, remove /home/craig/.DCOPserver_mobile__0
and start dcopserver again.
---------------------------------
WARNING: Already running!
kdeinit: Communication error with launcher. Exiting!
kio (KSycoca): ERROR: No database available!
kcmshell: WARNING: No K menu group with X-KDE-BaseGroup=settings found !
Defaulting to Settings/
kio (KSycoca): ERROR: No database available!
kio (KSycoca): ERROR: No database available!
kcontrol: ERROR: Module clock not found!
QMutex::unlock: unlock from different thread than locker
was locked by 0, unlock attempt from 16384
[EMAIL PROTECTED]:~$ KDE Daemon (kded) already running.
........also............
[EMAIL PROTECTED]:~$ sudo kcontrol
sudo: unable to lookup mobile via gethostbyname()
[EMAIL PROTECTED]:~$ sudo kcontrol
sudo: unable to lookup mobile via gethostbyname()
---------------------------------
It looks like dcopserver is already running. If you are sure
that it is not already running, remove /home/craig/.DCOPserver_mobile__0
and start dcopserver again.
---------------------------------
WARNING: Already running!
kdeinit: Communication error with launcher. Exiting!
kio (KSycoca): ERROR: No database available!
kcontrol: WARNING: No K menu group with X-KDE-BaseGroup=settings found !
Defaulting to Settings/
KDE Daemon (kded) already running.
ERROR: Communication problem with kcontrol, it probably crashed.
Running Sid,
Craig Hempenius
---------------------------------------
Received: (at 217717-done) by bugs.debian.org; 17 Jan 2005 02:03:27 +0000
>From [EMAIL PROTECTED] Sun Jan 16 18:03:27 2005
Return-path: <[EMAIL PROTECTED]>
Received: from tomts25-srv.bellnexxia.net [209.226.175.188]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CqMEo-0002G9-00; Sun, 16 Jan 2005 18:03:26 -0800
Received: from [192.168.0.100] ([70.49.17.55])
by tomts25-srv.bellnexxia.net
(InterMail vM.5.01.06.10 201-253-122-130-110-20040306) with ESMTP
id <[EMAIL PROTECTED]>;
Sun, 16 Jan 2005 21:03:22 -0500
From: Christopher Martin <[EMAIL PROTECTED]>
Reply-To: Christopher Martin <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: Bug no longer relevant, so closing
Date: Sun, 16 Jan 2005 21:03:18 -0500
User-Agent: KMail/1.7.1
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
X-CrossAssassin-Score: 30
Hello,
This bug is being closed because of its age and the vanishingly small
chance that it is still relevant to the current KDE packages, as it was
clearly since fixed, a random unreproducible bug that never had enough of
a follow-up to be useful, or else was forwarded upstream, where it was
marked fixed some time ago.
In case I'm mistaken, please do re-open the bug report in question, and
explain how the report is still relevant.
Thanks,
Christopher Martin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
