On Thu, Jun 30, 2011 at 8:38 AM, r...@mageia.org wrote:
Revision 116308 Author ze Date 2011-06-30 08:38:32 +0200 (Thu, 30 Jun 2011)
Log Message
- add missing files
- fix minor errors
- list dirs so that can be removed in uninstall
Modified Paths
'Twas brillig, and Funda Wang at 30/06/11 00:11 did gyre and gimble:
2011/6/30 Dexter Morgan dmorga...@gmail.com:
On Wed, Jun 29, 2011 at 7:42 PM, Zé mmode...@gmail.com wrote:
2011/6/27 Funda Wang fundaw...@gmail.com:
Hello,
How is the obsoleted binaries be removed currently in Mageia? Does
Le jeudi 30 juin 2011 à 09:41 +0100, Colin Guthrie a écrit :
'Twas brillig, and Funda Wang at 30/06/11 00:11 did gyre and gimble:
2011/6/30 Dexter Morgan dmorga...@gmail.com:
On Wed, Jun 29, 2011 at 7:42 PM, Zé mmode...@gmail.com wrote:
2011/6/27 Funda Wang fundaw...@gmail.com:
Hello,
On Thu, Jun 30, 2011 at 11:08 AM, Michael Scherer m...@zarb.org wrote:
Le jeudi 30 juin 2011 à 09:41 +0100, Colin Guthrie a écrit :
'Twas brillig, and Funda Wang at 30/06/11 00:11 did gyre and gimble:
2011/6/30 Dexter Morgan dmorga...@gmail.com:
On Wed, Jun 29, 2011 at 7:42 PM, Zé
On Thu, Jun 30, 2011 at 11:24 AM, r...@mageia.org wrote:
Revision 116351 Author ze Date 2011-06-30 11:24:58 +0200 (Thu, 30 Jun 2011)
Log Message
- set default files attibutes
No this is useless, please remove them
'Twas brillig, and Michael Scherer at 30/06/11 10:08 did gyre and gimble:
Le jeudi 30 juin 2011 à 09:41 +0100, Colin Guthrie a écrit :
'Twas brillig, and Funda Wang at 30/06/11 00:11 did gyre and gimble:
2011/6/30 Dexter Morgan dmorga...@gmail.com:
On Wed, Jun 29, 2011 at 7:42 PM, Zé
2011/6/30 Balcaen John mik...@mageia.org:
On Thursday 30 June 2011 04:45:15 Mageia Team wrote:
Name : libkdeedu Relocations: (not relocatable)
Version : 4.6.90 Vendor: Mageia.Org
Release : 4.mga2 Build Date:
On Thursday 30 June 2011 04:45:15 Mageia Team wrote:
Name: libkdeeduRelocations: (not relocatable)
Version : 4.6.90Vendor: Mageia.Org
Release : 4.mga2Build Date: Thu Jun 30 04:40:17
2011 Install Date: (not
On Thu, Jun 30, 2011 at 1:01 PM, Funda Wang fundaw...@gmail.com wrote:
2011/6/30 Balcaen John mik...@mageia.org:
On Thursday 30 June 2011 04:45:15 Mageia Team wrote:
Name : libkdeedu Relocations: (not relocatable)
Version : 4.6.90
Hello,
People who want to receive notifications of updates on the stable release
can subscribe to the updates-announce mailing list :
https://ml.mageia.org/wwsympa-wrapper.fcgi/info/updates-announce
Le jeudi 30 juin 2011 à 14:33 +0200, nicolas vigier a écrit :
Hello,
People who want to receive notifications of updates on the stable release
can subscribe to the updates-announce mailing list :
https://ml.mageia.org/wwsympa-wrapper.fcgi/info/updates-announce
Is there a simple web page
On Thu, 30 Jun 2011, Manuel Hiebel wrote:
Le jeudi 30 juin 2011 à 14:33 +0200, nicolas vigier a écrit :
Hello,
People who want to receive notifications of updates on the stable release
can subscribe to the updates-announce mailing list :
Le vendredi 24 juin 2011 02:15:03, Michael Scherer a écrit :
Hi,
The last mail from the backport trilogy. And like all good trilogy,
that's where the suspens is present ( as for the 1 and 2 part, you know
there is another episode )
This mail is about handling update on the backport
Le mardi 28 juin 2011 03:44:24, andre999 a écrit :
2) Backports would not be removed from repos when a newer backport arrives,
except those affected by security updates.
This allows reverting to previous backports if a user finds a problem with
a backport on their system.
I'd prefer that
Le jeudi 30 juin 2011 15:59:21, Samuel Verschelde a écrit :
Le vendredi 24 juin 2011 02:15:03, Michael Scherer a écrit :
However, this mean that someone will have to check if the bug
is fixed, and the question is who ( and I do not have a answer that I
find good enough yet ). This could
On Thu, 30 Jun 2011, Samuel Verschelde wrote:
Le mardi 28 juin 2011 03:44:24, andre999 a écrit :
2) Backports would not be removed from repos when a newer backport arrives,
except those affected by security updates.
This allows reverting to previous backports if a user finds a problem
Le mardi 28 juin 2011 03:44:24, andre999 a écrit :
2) Backports would not be removed from repos when a newer backport
arrives, except those affected by security updates.
This allows reverting to previous backports if a user finds a problem
with a backport on their system.
I'd prefer
Hi All,
I would like to participate to your project and to help you by packaging
rpms.
As I don't know what needs to be packed, I've tried to make rpm for
ZoneMinder 1.24.4. But it fails to install into BUILDROOT environment. I
must have done something wrong while setting installation
2011/6/30 Vincent vincent.hervi...@gmail.com
Hi All,
I would like to participate to your project and to help you by packaging
rpms.
As I don't know what needs to be packed, I've tried to make rpm for
ZoneMinder 1.24.4. But it fails to install into BUILDROOT environment. I
must have done
Hello,
i would like us to update to gnome 3.1 ( which will give gnome 3.2 ).
Is there someone against ?
2011/6/29 John Balcaen mik...@mageia.org:
2011/6/29 r...@mageia.org:
Revision 115962 Author ze Date 2011-06-29 15:57:57 +0200 (Wed, 29 Jun 2011)
Log Message
- no need to buildrequire and use kde-macros
- use rpm native macros and not variables
[...]
We were using kde4-macros especially
2011/6/29 John Balcaen mik...@mageia.org:
2011/6/29 r...@mageia.org:
Revision 115561 Author fwang Date 2011-06-29 06:48:40 +0200 (Wed, 29 Jun
[...]
Modified: cauldron/libkipi/current/SPECS/libkipi.spec
===
---
On Thursday 30 June 2011 22:09:15 Zé wrote:
2011/6/29 John Balcaen mik...@mageia.org:
2011/6/29 r...@mageia.org:
Revision 115962 Author ze Date 2011-06-29 15:57:57 +0200 (Wed, 29 Jun
2011)
Log Message
- no need to buildrequire and use kde-macros
- use rpm native macros and not
Samuel Verschelde a écrit :
Le mardi 28 juin 2011 03:44:24, andre999 a écrit :
2) Backports would not be removed from repos when a newer backport arrives,
except those affected by security updates.
This allows reverting to previous backports if a user finds a problem with
a backport on their
On Thu, 23 Jun 2011, Luc Menut wrote:
Le 23/06/2011 07:58, Dexter Morgan a écrit :
On Thu, Jun 23, 2011 at 7:29 AM, Thierry Vignaud
thierry.vign...@gmail.com wrote:
On 22 June 2011 19:41, Florian Hubolddoktor5...@arcor.de wrote:
Well, it's quite possible that we have to include that in
This is making me crazy. After upgrading to KDE 4.6.90 (cauldron, of course),
the bloody m*f*er kded4 (the worse idea in KDE4) constantly takes 55-75% CPU.
Of course, killing it is possible, but this affects the plasmoids. (E.g. it
made me inadvertently filling an invalid bug report 1981, which
On Thu, 30 Jun 2011, Dexter Morgan wrote:
Hello,
i would like us to update to gnome 3.1 ( which will give gnome 3.2 ).
When is the release of gnome 3.2 planned ?
On Thu, Jun 30, 2011 at 19:34, Radu-Cristian FOTESCU
beranger...@yahoo.cawrote:
This is making me crazy. After upgrading to KDE 4.6.90 (cauldron, of
course), the bloody m*f*er kded4 (the worse idea in KDE4) constantly takes
55-75% CPU.
Of course, killing it is possible, but this affects the
On Fri, Jul 1, 2011 at 12:41 AM, nicolas vigier bo...@mars-attacks.org wrote:
On Thu, 30 Jun 2011, Dexter Morgan wrote:
Hello,
i would like us to update to gnome 3.1 ( which will give gnome 3.2 ).
When is the release of gnome 3.2 planned ?
in october so we will at least have gnome 3.2.x
The solution which worked most of the time for such issues in kde 4.6.xx was:
1. open a terminal
2. run killall plasma-desktop
3. plasma-desktop
the plasmoids and the desktop come back, and kded4 stops using that much CPU.
Last time I looked what it was looking CPU at, it was caused by
2011/6/30 Balcaen John mik...@mageia.org:
On Thursday 30 June 2011 22:09:15 Zé wrote:
2011/6/29 John Balcaen mik...@mageia.org:
2011/6/29 r...@mageia.org:
Revision 115962 Author ze Date 2011-06-29 15:57:57 +0200 (Wed, 29 Jun
2011)
Log Message
- no need to buildrequire and use
On Thursday 30 June 2011 15:34:50 Radu-Cristian FOTESCU wrote:
This is making me crazy. After upgrading to KDE 4.6.90 (cauldron, of
course), the bloody m*f*er kded4 (the worse idea in KDE4) constantly takes
55-75% CPU.
Of course, killing it is possible, but this affects the plasmoids. (E.g.
On Thursday 30 June 2011 16:10:46 Radu-Cristian FOTESCU wrote:
[...]
Now, I know my KDE is somewhat b0rken, because akonadiserver can't start --
but I could live just fine this way in KDE 4.6.3-4.6.4, if not even better
than with it.
Well only kdepim is broken so it's not a big deal if you're
Le 2011-06-30 18:34, Radu-Cristian FOTESCU a écrit :
This is making me crazy. After upgrading to KDE 4.6.90 (cauldron, of
course), the bloody m*f*er kded4 (the worse idea in KDE4) constantly
takes 55-75% CPU.
Of course, killing it is possible, but this affects the plasmoids. (E.g.
it made me
On Thursday, June 30, 2011 12:16:47 am Cazzaniga Sandro wrote:
Le 30/06/2011 06:54, Ahmad Samir a écrit :
It seems libperl.so is hiding
It is wehre it should be but cyrus-imap cannot find it.
Maybe we have to check cyrus-imap instead of libperl.so, so.
it gives the pretty much same
On Thursday, June 30, 2011 05:23:58 pm Marc Paré wrote:
Le 2011-06-30 18:34, Radu-Cristian FOTESCU a écrit :
This is making me crazy. After upgrading to KDE 4.6.90 (cauldron, of
course), the bloody m*f*er kded4 (the worse idea in KDE4) constantly
takes 55-75% CPU.
Of course, killing it
On 1 July 2011 03:24, Thomas Spuhler tho...@btspuhler.com wrote:
On Thursday, June 30, 2011 12:16:47 am Cazzaniga Sandro wrote:
Le 30/06/2011 06:54, Ahmad Samir a écrit :
It seems libperl.so is hiding
It is wehre it should be but cyrus-imap cannot find it.
Maybe we have to check
On Thursday, June 30, 2011 08:08:48 pm Ahmad Samir wrote:
On 1 July 2011 03:24, Thomas Spuhler tho...@btspuhler.com wrote:
On Thursday, June 30, 2011 12:16:47 am Cazzaniga Sandro wrote:
Le 30/06/2011 06:54, Ahmad Samir a écrit :
It seems libperl.so is hiding
It is wehre it should be
On 1 July 2011 05:35, Thomas Spuhler tho...@btspuhler.com wrote:
On Thursday, June 30, 2011 08:08:48 pm Ahmad Samir wrote:
On 1 July 2011 03:24, Thomas Spuhler tho...@btspuhler.com wrote:
On Thursday, June 30, 2011 12:16:47 am Cazzaniga Sandro wrote:
Le 30/06/2011 06:54, Ahmad Samir a écrit
(This is making me crazy. Otherwise, I'll tell you some day about a
bug/crash that was *accidentally* fixed by KDE 4.6.90.)
Which one ? ;o)
See
https://mageia.org/pipermail/mageia-dev/2011-July/006180.html
R-C
Could it be that it is indexing all of your files?
NOPE. I never ever use indexing, no matter what the OS is.
R-C
Well only kdepim is broken so it's not a big deal if you're not using
it.
(You should be able to use akregator).
Yes, akregator works just fine.
R-C
However here killing this process does not seems to affect my plasmoids.
I'm surprised to see you writing it. After killing kded4:
1. Klipper was not reacting.
2. The keyboard layout systray icon was dead.
3. Any changes in the way the clock is displayed (hour/date format) were not
applied.
https://bugs.mageia.org/show_bug.cgi?id=1836
There's a special plasmoid which can help with user experience of
those who used input method, but ever since the package request,
there's no response. Would someone help with this one?
Since we have determined to use iBus as the default input
I was trying to investigate the kded4 high CPU load, and I started to
investigate some upstream reports, even if not necessarily reported for 4.6.90.
Some such reports were related to ntrack, e.g. http://bugs.kde.org/268038
What the heck is ntrack and why do we need it? (The official
2011/7/1 Marc Paré m...@marcpare.com
Mine was doing this and I tried to stop it (I don't really know how to do
this), so in the end I let it go. It has now stopped. Could it be that it is
indexing all of your files? I know that I have 600 gigs of data, and, if
KDE4 was trying to index all of
46 matches
Mail list logo
