Upstream has merged this fix patch:
https://github.com/PackageKit/PackageKit-Qt/commit/e6cb7890c4193b65a55cf295eb963ac4463c81c1
Dear Maintainer,
Looks like I am affected too. Checking for updates in Discover reproduces the
bug too.
Logs before crash:
> Jan 03 15:24:23 debian kded5[20091]: apper.daemon: Creating Helper
> Jan 03 15:24:23 debian kded5[20091]: apper.daemon: System is not ready,
> application should
Package: openjdk-8-jre
Version: 8u181-b13-1
Severity: normal
Dear Maintainer,
Package openjdk-8-jre has Provides:
java2-runtime, java5-runtime, java6-runtime, java7-runtime,
java8-runtime
It is missing "java-runtime". As result, some other packages that
depend on java-runtime will force
Package: clvm
Version: 2.02.66-3
Severity: normal
Just setting up a cluster on a different box and, in configuring
pacemaker found that I could not use ocf:lvm2:clvmd as the required
file (/usr/lib/ocf/resource.d/lvm2/clvmd) is missing.
It would be a good idea to include this in squeeze
When trying to load an fsf file (design file) in the feat gui (one that
ran successfully under 4.0) I got the following error output:
can't read fmri(confoun: no such variable
can't read fmri(confoun: no such variable
while executing
set fmri(confoun
(file
Show your hot date a sizzling time in the sack.
http://www.albagrowths.com/
Slap that cute tight ass
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
All the soma you will ever need, here - http://Diplodoubles.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Get Prescrpitions tomorrow
www.austriaabater.apr.claimhuge.com
and addedaward
barstow may baroque
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hello
If you experience some lapses in your sexual life, please, do not hesitate or
make your life worse. Just a blue-pill will cure all your doubts and restore
the life you will not help enjoying.
http://besthotelsoxford.com
Regards
The ePharmacy Team.
--
To UNSUBSCRIBE, email to [EMAIL
On Sun, Sep 23, 2007 at 09:33:05AM +0200, Christian Perrier wrote:
I'd agree except that this isn't necessarily set in stone. It's only
present in an in-flux distribution of Debian (Lenny/Sid) and Etch
doesn't even have the switch at all (and is currently stuck with a
default totally
On Sat, Sep 22, 2007 at 10:39:17AM +0200, Christian Perrier wrote:
Would it be possible to modify this slightly to say that if a GROUP=
line is given in the configuration file then -n is implied and that is
used, otherwise make a new one? It seems to me to be slightly better
behaviour as
On Thu, Sep 20, 2007 at 09:06:05AM +, Debian Bug Tracking System wrote:
This was fixed in the version 1:4.0.18.1-8 of shadow (and passwd).
This version is not available on Etch.
In the Etch version, the default behavior, when -g is not specified, is
always to use/create the primary user
Package: php5-cgi
Version: 5.2.0-8+etch7
Severity: normal
It would appear that php5-cgi reads the file specified by -c first,
parses it and then follows it up with the global config files
(/etc/php5/...). The end effect of this is that there is no way to
override the globals for, say, some site
Package: passwd
Version: 1:4.0.18.1-7
Severity: normal
I am trying to add a new user to the system whose group will
automatically be set to 'users' but useradd fails to do so:
# useradd test
# id test
uid=1007(test) gid=1007(test) groups=1007(test)
# userdel test
# useradd -D
GROUP=100
On Fri, Nov 24, 2006 at 10:23:38AM +0100, Marc Haber wrote:
On Fri, Nov 24, 2006 at 05:11:25PM +1100, CaT wrote:
So there is absolutely no need for the create option in logrotate
Not having the logs created might break monitoring mechanisms.
Well it is kind of a choice between maybe
On Fri, Nov 24, 2006 at 01:15:01PM +0100, Marc Haber wrote:
On Fri, Nov 24, 2006 at 10:58:28PM +1100, CaT wrote:
On Fri, Nov 24, 2006 at 10:23:38AM +0100, Marc Haber wrote:
On Fri, Nov 24, 2006 at 05:11:25PM +1100, CaT wrote:
So there is absolutely no need for the create option
On Fri, Nov 24, 2006 at 10:23:38AM +0100, Marc Haber wrote:
On Fri, Nov 24, 2006 at 05:11:25PM +1100, CaT wrote:
So there is absolutely no need for the create option in logrotate
Not having the logs created might break monitoring mechanisms.
Sorry, the other thing about this:
Testing
Actually, the permissions on the exim created logfile will be correct
seeing as
#--
# The log files themselves are created as required, with a mode that
# defaults
# to 0640, but which can be changed here.
#
Package: exim4
Version: 4.50-8sarge2
Severity: normal
Yesterday exim died with the following error in the panic log:
2006-11-22 06:25:23 +1100 Cannot open main log file /var/log/exim4/mainlog:
Permission denied: euid=102 egid=102
This was a fairly busy server so by the time I managed to get
Package: apt-file
Version: 2.0.3-7
Severity: wishlist
Tags: patch
Please? For the sweet sweet love of god have mercy! :/
--- /usr/bin/apt-file.old 2005-08-01 14:27:35.0 +1000
+++ /usr/bin/apt-file 2005-08-01 14:28:45.0 +1000
@@ -281,6 +281,7 @@
Action:
update
On Mon, Jul 11, 2005 at 01:58:36PM +0200, Santiago Vila wrote:
severity 317598 normal
thanks
I reiterate that I can't take this report seriously unless you tell me
a way to reproduce it. In particular, you didn't tell me about your
Have we spoken about this previously? I had a look at the
idea:
Jul 10 10:35:07 theirongiant fetchmail[1063]: 4 messages for cat at
zipworld.com.au (13738 octets).
Jul 10 10:35:07 theirongiant fetchmail[1063]: reading message [EMAIL
PROTECTED]:1 of 4 (2949 octets)
Jul 10 10:35:08 theirongiant fetchmail[1063]: flushed
Jul 10 10:35:08 theirongiant
22 matches
Mail list logo
