On 06/22/16 12:59, Ed Greshko wrote:
On 06/22/16 18:40, Joachim Backes wrote:
Starting brasero in F24 takes about 40 (fourty!!) seconds until it's window appears on the screen. Until this moment, one CPU is completely busy (100%). Starting it a second time, the startup time is shorter and takes only about 1 sec.
The ldd command for /usr/bin/brasero lists 128 libs.
This happens with brasero-3.12.1-4.fc24.x86_64.
Anybody sees this too?
Takes about 20 seconds on a very old laptop. Everything is slow to start on this system....so it seems normal to me. I started it from a KDE session on the konsole command line.
It started much faster the second time. I guess needed libs were not flushed.
Hi Ed,
seems to be comparable with my issue. I started brasero not from a KDE session, but inside a gnome3 session. My board has 4 Intel cores, each with 2.5 GHz. Seems not be a memory problem, because gnome-system-monitor did not point out a memory overloeading, only one fully running CPU core.
I agree that if started a second time, the libs had not been flushed. That is my impression too.
Thanks for your remarks.
Kind regards
Joachim Backes