Looking over some broken deps reports, I came across some old packages:
Of these, the only one that's not a pure leaf package is perl-Qt (debconf-
kde depends on it).
any comment or objection to considering orphaning most (all minus
smokeqt/perl-Qt) or all of these ?
I'm Eduard Lucena, and I'm here in the behalf of the Marketing team. As you
should know, we prepare a lists of highlights about each release, called
Talking points are key highlights of the new release. There are different
> types of talking points for different types of people: general desktop
> users/everyone, developers, and sysadmins. They are meant to provide a
> short, effective answer to the question "What cool stuff is in the latest
> release of Fedora?" They are compelling, not necessarily comprehensive
This points help us, as Marketing team, as well to Ambassadors, to
publicize each release with the news and cool stuff.
For this matter and this release, we have this wiki page:
https://fedoraproject.org/wiki/Fedora_26_talking_points and we will be
happy to include the new things in the KDE Spin.
You can help us in both ways:
1. Editing the wiki directly with the points.
2. Throwing us the list, and we will put them in the wiki.
Thanks in advance for your help and for your efforts.
GNU/Linux User #589060
Ubuntu User #8749
Fedora Ambassador Latam
On Sat, 2017-04-29 at 00:15 +0200, Giulio E. wrote:
> Hi folks,
> I've been testing "Fedora-KDE-Live-x86_64-26-20170420.n.0.iso" on qemu-
> kvm tonight and I've had trouble following the login TestCase.
> Actually, the login process resulted to multiple crashes (large part of
> the KDE session, I guess). I reported what seems to be the most
> relevant one: https://bugzilla.redhat.com/show_bug.cgi?id=1446785
> I'm not sure this is the main cause for the misbehavior. Having said
> that, I think that sddm's login functionality might be quite broken at
> this time, since the entire KDE session crashed lots of times, during
> my login attempts.
> However, more testing may help in collecting more data for debugging
> the situation.
> As a footnote, I've also hit this (which is weird, but doesn't seem a
> big issue, at least for Beta): https://bugzilla.redhat.com/show_bug.cgi
> Thank you for your help.
As I mentioned in a status report mail yesterday, openQA seems to hit
crashes / hangs in KDE startup quite often also; it sometimes just gets
stuck with the KDE splash screen partly complete, or winds up at a
black screen with a KDE-ish cursor visible but nothing else. I haven't
had time to dig into the logs and see if I could diagnose a pattern to
the failures, though...
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
Has anyone else experienced this? Fairly frequently I find that kwin
on F25 is not starting on login, there are no window decorations (e.g.
title bar) and all new windows start at top left with no apparent way
to move them. The solution seems to be to start a console and run
This morning however I didn't even have a desktop, just a cursor and
an otherwise black screen. What was working was that typing brought up
the command bar at the top of the screen, so I was able to start
konsole. "kstart kwin" and "kstart kwin --replace" didn't seem to
achieve anything (though maybe I could have waited longer), eventually
tried "kstart plasmashell" and things seemed to run again.
This is the nouveau driver. I've had problems on F25 with getting
stuck at the splash screen ("K") after login, but adding nomodeset to
the kernel line in grub seemed to alleviate that, and I was using
nomodeset this morning.
Is it on purpose in 5.9.4 on F25 & F26 for clock to have more space under than
above? It looks to me like somebody screwed up Fedora theming somehow, as clock
looks perfectly centered vertically with 5.9.4 on Tumbleweed.
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/