What Happened to KMLDonkey
by Eli Wapniarski
Hi All
It seems that kmldonkey is missing? Any ideas as to why?
Eli
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
14 years, 1 month
Kauth problem
by Christian Jann
Hello,
Could somebody get
svn://anonsvn.kde.org/home/kde/trunk/KDE/kdeexamples/authorization
to work with F12 or F13, I can't
F12 KDE 4.4.1 (kde-unsable repo)
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdeexamples/authorization
cd authorization/
sed -i '1i\cmake_minimum_required(VERSION 2.6.2 FATAL_ERROR)' CMakeLists.txt
mkdir build
cd build
cmake ..
make
sudo make install
./kauth_example
now when I try to save /testfile I get an SELinux alert:
SELinux is preventing /lib/dbus-1/dbus-daemon-launch-helper "execute_no_trans"
access on /usr/local/lib/kde4/libexec/kauth_example_helper.
su -
audit2allow -m local -l -i /var/log/audit/audit.log > local.te
vim local.te
################
module local 1.0;
require {
type lib_t;
type system_dbusd_t;
class file execute_no_trans;
}
#============= system_dbusd_t ==============
allow system_dbusd_t lib_t:file execute_no_trans;
#################
checkmodule -M -m -o local.mod local.te
semodule -i local.pp
exit
./kauth_example
now no SELINUX alert anymore but I get only:
"Launch helper exited with unknown return code 255"
when I try to save /testfile but I should get some authorization window like
here:
pkexec touch /testfile
changing date and time in systemsettings works also
I hope somebody can help me to get some more debug output or knows what the
problem is
I hope this behavior is only F12 special, maybe somebody with F13 can try this
14 years, 1 month
Re: kde Digest, Vol 16, Issue 36
by long2015
2010/3/14 <kde-request(a)lists.fedoraproject.org>
> Send kde mailing list submissions to
> kde(a)lists.fedoraproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://admin.fedoraproject.org/mailman/listinfo/kde
> or, via email, send a message with subject or body 'help' to
> kde-request(a)lists.fedoraproject.org
>
> You can reach the person managing the list at
> kde-owner(a)lists.fedoraproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of kde digest..."
>
>
> Today's Topics:
>
> 1. Re: Maximum number of clients reached (Anne Wilson)
> 2. Re: Maximum number of clients reached (Patrick O'Callaghan)
> 3. Re: KMail again (Eli Wapniarski)
> 4. Re: Document Viewer can not open latest PDF? (Kevin Kofler)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 13 Mar 2010 15:26:16 +0000
> From: Anne Wilson <cannewilson(a)googlemail.com>
> Subject: Re: Maximum number of clients reached
> To: KDE on Fedora discussion <kde(a)lists.fedoraproject.org>
> Message-ID: <201003131526.22680.cannewilson(a)googlemail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Saturday 13 March 2010 14:26:17 Patrick Boutilier wrote:
> > On 03/13/2010 10:11 AM, Anne Wilson wrote:
> > > On Friday 12 March 2010 16:43:54 Neal Becker wrote:
> > >> I keep getting X errors:
> > >> Maximum number of clients reached
> > >>
> > >> I've never seen these before, but recently it's happening all the
> time.
> > >> How can I debug this?
> > >
> > > I doubt if you can. This generally occurs when the site you are
> > > addressing is using a database and there are literally too many queries
> > > happening at the same moment. Sometimes it's a denial-of-service
> attack
> > > on the server. Sometimes it's just coincidence, and a few moments later
> > > you can connect. I have seen it regardless of web browser being used -
> > > not surprising, really.
> >
> > Isn't Neal taking about X errors, not website errors?
> > I am sorry, I do not know how to use it, how to replay?
Apologies - I should read more carefully. Googling for the error message
> gives guidance.
>
> Anne
> --
> KDE Community Working Group
> New to KDE Software? - get help from http://userbase.kde.org
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 198 bytes
> Desc: This is a digitally signed message part.
> Url :
> http://lists.fedoraproject.org/pipermail/kde/attachments/20100313/4f71224...
>
> ------------------------------
>
> Message: 2
> Date: Sat, 13 Mar 2010 13:01:42 -0430
> From: Patrick O'Callaghan <pocallaghan(a)gmail.com>
> Subject: Re: Maximum number of clients reached
> To: kde(a)lists.fedoraproject.org
> Message-ID: <1268501502.21405.8.camel(a)bree.homelinux.com>
> Content-Type: text/plain; charset="UTF-8"
>
> On Sat, 2010-03-13 at 15:25 +0000, Timothy Murphy wrote:
> > Patrick O'Callaghan wrote:
> >
> > > I use Chrome as my day-to-day browser and mostly it works well, but if
> > > for any reason it crashes, or you shut down or log out without quitting
> > > it, it tends to leave several processes lying around, as has already
> > > been said. AFAIK these processes will stay there forever unless you
> > > explicitly kill them (pgrep -fl chrome; pkill -9 chrome).
> > >
> > > Then you often have to clean up the mess by removing stuff from
> > > ~/.cache/google-chrome/Cache and possibly ~/.config/google-chrome. I
> > > haven't completely figured it out yet, but if you don't do this then a
> > > new session of Chrome is likely to hang on some of your tabs. The exact
> > > conditions aren't clear to me.
> >
> > As a matter of interest, why do you use it
> > as your "day-to-day browser" if it what seems like
> > fairly serious deficiencies?
>
> The deficiencies are outweighed by the advantages, or to put it another
> way, by the deficiencies of other browsers. I don't want to get into a
> browser war here, but I though I've used FF for many years and still
> keep it up to date, I find Chrome extremely fast (both to start up and
> in page rendering) and on the whole more reliable than FF, in large part
> because of the process-per-tab model, which I believe FF will adopt in a
> future version. It's also less of a cpu hog.
>
> The problems I mentioned above are annoying, but I know about them and
> they only affect me at well-defined moments.
>
> Also, none of the above precludes me from going back to FF if/when it
> catches up with Chrome in these areas. Competition is good :-)
>
> poc
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 13 Mar 2010 19:33:22 +0200
> From: Eli Wapniarski <eli(a)orbsky.homelinux.org>
> Subject: Re: KMail again
> To: kde(a)lists.fedoraproject.org
> Message-ID: <201003131933.22511.eli(a)orbsky.homelinux.org>
> Content-Type: Text/Plain; charset="iso-8859-1"
>
> It's been a long time since I've used dovecote. Currently using cyrus-imap
> and
> I have not seen that kind of error. Right now, I'm seriously thinking about
> zarafa.
>
> Be that as I may. If I remember correctly. You will have to go to your mail
> cache which should be somewhere in /var/mail (could be wrong about the
> exact
> location) and go through a process of elimination.
>
> 1) shut down your MTA (etc, sendmail, postfix, etc.).
> 2) Shutdown your imap server.
> 3) Make a backup copy of your mail cache
> 4) Delete the email that is causing you the grief (be mindful of the first
> message that says don't delete me. And be mindful of the seperator
> between
> emails.
> 5) a) Restart your imap server and mta
> b) If that didn't fix the server go through steps 1 -5a again only
> delete
> a different email or section of emails.
> c) If you've only deleted 1 email then thats that. If you've deleted
> a section of emails, you will need to restore the backup, and go
> through steps 1- 5a making the section you delete smaller and smaller
> until you eliminate the email causing you the trouble.
>
>
> I wish there was an easier way to do that, but I couldn't find any
>
>
> Eli
>
>
> On Saturday 13 March 2010 16:08:57 Timothy Murphy wrote:
> > I am running KMail on my laptop
> > to access a dovecot/IMAP server on my desktop.
> >
> > KMail works fine most of the time,
> > except that there are a couple of "sick" messages
> > which I can't get rid of.
> > As soon as I click on them KMail crashes.
> >
> > I've been waiting for this KMail bug to be solved,
> > but that doesn't seem to be coming very soon
> > (I've submitted a bugzilla, as have many others).
> >
> > I'm wondering now if there is a simple way
> > of dealing with the symptom,
> > by getting rid of these bad messages.
> >
> > I've seen a suggestion that the problem is due to
> > some corruption of a dovecot/KMail cache,
> > but I'm not sure what that refers to.
> >
> > If any KMail/kdepim expert has a solution
> > I should be very grateful.
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
>
> ------------------------------
>
> Message: 4
> Date: Sun, 14 Mar 2010 01:36:27 +0100
> From: Kevin Kofler <kevin.kofler(a)chello.at>
> Subject: Re: Document Viewer can not open latest PDF?
> To: kde(a)lists.fedoraproject.org
> Message-ID: <hnhb2b$aho$1(a)dough.gmane.org>
> Content-Type: text/plain; charset="ISO-8859-1"
>
> Patrick Boutilier wrote:
> > Open with Okular then save the embedded file. Then open the embedded
> > file with Okular.
>
> But unfortunately, there may be more embedded files hidden behind some
> weird
> magic which Okular does not understand. :-( (In the case of the form in the
> linked thread, that was the case.)
>
> Kevin Kofler
>
>
>
> ------------------------------
>
> _______________________________________________
> kde mailing list
> kde(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/kde
>
> End of kde Digest, Vol 16, Issue 36
> ***********************************
>
--
“可与言而不与之言,失人;不可与言而与之言,失言。” ——《论语·卫灵公》
14 years, 1 month
KMail again
by Timothy Murphy
I am running KMail on my laptop
to access a dovecot/IMAP server on my desktop.
KMail works fine most of the time,
except that there are a couple of "sick" messages
which I can't get rid of.
As soon as I click on them KMail crashes.
I've been waiting for this KMail bug to be solved,
but that doesn't seem to be coming very soon
(I've submitted a bugzilla, as have many others).
I'm wondering now if there is a simple way
of dealing with the symptom,
by getting rid of these bad messages.
I've seen a suggestion that the problem is due to
some corruption of a dovecot/KMail cache,
but I'm not sure what that refers to.
If any KMail/kdepim expert has a solution
I should be very grateful.
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
14 years, 1 month
k3b-1.70 x86_64
by John Armitage
How come the latest k3b has gone from the x86_64 repo?
14 years, 1 month
KMail problem
by Timothy Murphy
I'm surprised the recent KMail problem has not been solved.
The symptoms in my case, in brief, are
1. I am using KMail on my laptop with dovecot/IMAP
to read mail collected on my desktop;
2. KMail crashes when reading, or even accessing, certain messages.
These are nearly all, if not all, mailing list digests.
I guess the property they have in common might be
that they have a large number of references to other messages or URLs.
I submitted a bugzilla, which bizarrely to me
was declared a duplicate of a bugzilla over a year old
<https://bugs.kde.org/show_bug.cgi?id=186502>
and which appeared to deal with another symptom,
KMail crashing when it starts.
There are a large number of duplicates listed,
nearly all very recent.
It seems to me fairly obvious that the problem has arisen recently,
and is due to a recent change in KMail (or possibly dovecot).
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
14 years, 1 month
unlock screen dialog box empty
by Dj YB
hello,
after the update to 4.4 the unlock screen dialog box is empty,
does anyone else have this problem?
if you need more info please tell me what and I'll post it here.
thanks,
YB.
14 years, 1 month
RFC: kde stability proposal (redux)
by Rex Dieter
One more call for discussion around another proposal that came out of FUDCon
Toronto. Short version of this is that we'd consider slowing down updates a
step, esp for the second half of a fedora release's lifetime, and to limit
kde 4.x-type upgrades to at most 1 per release.
http://fedoraproject.org/wiki/SIGs/KDE/Stability_Proposal
Whatever we decide, increasing our transparency by documenting our update
practices will hopefully help shape everyone''s plans and expectations. As
it is, seems these vary wildly.
-- Rex
14 years, 1 month