I am starting to think that the problem resides in gcc-4.7. With 4.8.90 and mysql the problem persists.

- With a empty config akregator starts and donwload feeds.
- When try to read any feed, akregator crash.
- Then akregator freeze and consume 100% of one core.

any idea?

PS: Akregator did also not compile with lto.
PPS: O.o It also happens with akregator 4.8.4
PPPS: Moreover, compiled with 4.6.3 also happen even with very conservative flags. I'm statring to think that the problem are in oder place of the stack

I am running now akregator compiled with gcc 4.7.1 with no problems with same configuration as you mention, but no lto.

I am stating to consider that as a problem. My brother have update to 4.8.90 with gcc 4.6.3 and can use akregator. So I suspect that the problem is in another part of the stack and is related to lto or graphite (or both).

-----------------------------------------------------------------------------
-- The following OPTIONAL packages could NOT be located on your system.
-- Consider installing them to enable more features from this software.
-----------------------------------------------------------------------------
* HUPnP <http://www.herqq.org>
UPnP support for Solid
Allows Solid to provide information about UPnP devices on the network
* media-player-info <http://www.freedesktop.org/wiki/Software/media-player-info>
Enables identification and querying of portable media players
Runtime-only dependency of the udev solid backend. Support for m-p-i is included even if not found during build
* GSSAPI <http://web.mit.edu/kerberos/www>
Allows KIO to make use of certain HTTP authentication services
A MIT or HEIMDAL flavor of GSSAPI can be used
* Aspell <http://aspell.net/>
Spell checking support via Aspell
This is not needed for spell checking if Enchant is provided or only Hebrew spell checking is required
* HSpell <http://ivrix.org.il/projects/spell-checker/>
Spell checking support for Hebrew
Hebrew support can also be provided via Enchant, providing the correct Enchant backends are installed
* JasPer <http://www.ece.uvic.ca/~mdadams/jasper>
Support for JPEG-2000 images
* Avahi <http://avahi.org>
Facilities for service discovery on a local network (DNSSD)
Either Avahi or DNSSD is required for KDE applications to make use of multicast DNS/DNS-SD service discovery
* DNSSD <http://avahi.org>
Facilities for service discovery on a local network
Either Avahi or DNSSD is required for KDE applications to make use of multicast DNS/DNS-SD service discovery

Observed with "kde" overlay, kde version 4.8.90:
Starting several applications (e.g. dolphin, firefox) took much longer than previously (compared with old KDE 4.8, but also kde 4.8.80 from kde overlay). During the delayed startup, within a konsole a lot of traces from this new udisks2 backend code for all system block devices were emitted:

Code:

qDebug() << "devnum:" << m_devNum << "dev file:" << m_devFile;

This seemed to be related to the new udisks2 backend patch, recently added to Gentoo overlay, as mentioned in "Documentation/maintainers/meetings/meeting-2012-06":

Quote:

On request from Samuli I've added the Udisks2 patch from RedHat to kdelibs. This *replaces* the udisks:0 solid backend with a new udisks:2 version. Has according to Wulf (philantrop) still some issues.
Feedback? Experiences? Keep for 4.9.0 or (temporarily) ditch again?

It is unclear to me whether sys-fs/udisks2-1.98.0 causes the issue, or the new kde udisks2 backend code. But my feedback would be clear -- udisks2 backend in its current state for me is much worse than the old one

When trying to set use flag "-udisks" on kdelibs, the startup delay was still observed. The "libsolid.so" library still seemed to contain+use the new udisks2 backend regardless of the use flag.

Only after manually coping the kdelibs ebuild into my local overlay, removing the gentoo udisks2 patch, changing the udisks dependency back to "udisks:0", apps like dolphin started again almost immediately.

Anyone else observed this? If yes, try it out and revert back to udisks:0 backend.

As you can see, I still have a good portion of packages to emerge before kde is up any running so any support would be greatly appreciated._________________Don't ever tell anybody anything. If you do, you start missing everybody.

Does anyone of you have external monitor(s) attached to a notebook system? I am still fighting with an infamous panel auto resize bug in plasma since pretty much the beginning of KDE4, and now I suspect it's this particular configuration that causes trouble for just a fraction of KDE userbase._________________backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic

I use external monitor at work. After plugging in, I set it up via "Size & Rotation" (I always have krandrtray running for ease of this). There I set up my notebook panel to be main and right of external.

Panels, when locked, do not extend to the size their inhabiting widgets would actually need. It's extremely tiring to the eye and very embarassing for a DE that soon goes into it's 9th major iteration.

I have some hopes for KDE SC 4.9 since parts of plasma seem to be rewritten, but it needs to get a bit less hot until I start to emerge some 4.9 RC

My exact config is a 1440x900 laptop screen, which always remains closed when sitting on its docking station when output goes to the 1920x1200 screen.

akregator, when used outside of kontact, also has an annoying window size bug when working with two different resolutions. The mere existence of different resolution settings inside akregatorrc makes it behave badly. That's what made me curious if it's a similar issue with plasma panels._________________backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic

You want to save a file from a webpage? You can make a coffee in the time the dialog needs to pop up.
Login is painfull. All icons are done bouncing, but the box just sits there and does nothing - for ages.
Open a directory in konqueror or dolphin? Bad move. Now you can father a family while waiting for the greyed out box to show the acutal contents - and don't even dream of trying to click on something. Using gwenview to open a pic, for example....

I let the rc1 packages build over night and everything seems to be fine so far. Of course, as with every KDE upgrade, it killed my wallpaper setting for starters.

@energyman76b: The udisks2 trouble is known and comes from the Red Hat patch, but it seems not everyone is affected._________________backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic