Re: [Test-Announce] Fedora 25 Candidate RC-1.1 Available Now!
by Adam Williamson
On Wed, 2016-11-09 at 00:36 -0800, rawhide(a)fedoraproject.org wrote:
> According to the schedule [1], Fedora 25 Candidate RC-1.1 is now
> available for testing. Please help us complete all the validation
> testing! For more information on release validation testing, see:
> https://fedoraproject.org/wiki/QA:Release_validation_test_plan
>
> Test coverage information for the current release can be seen at:
> https://www.happyassassin.net/testcase_stats/25
>
> You can see all results, find testing instructions and image download
> locations, and enter results on the Summary page:
>
> https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.1_Summary
>
> The individual test result pages are:
>
> https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.1_Installation
> https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.1_Base
> https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.1_Server
> https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.1_Cloud
> https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.1_Desktop
> https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.1_Security_Lab
>
> All RC priority test cases for each of these test pages [2] must
> pass in order to meet the RC Release Criteria [3].
>
> Help is available on #fedora-qa on irc.freenode.net [4], or on the
> test list [5].
>
> Current Blocker and Freeze Exception bugs:
> http://qa.fedoraproject.org/blockerbugs/current
>
> [1] http://fedorapeople.org/groups/schedule/f-25/f-25-quality-tasks.html
> [2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan
> [3] https://fedoraproject.org/wiki/Fedora_25_RC_Release_Criteria
> [4] irc://irc.freenode.net/fedora-qa
> [5] https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/
Hi folks! Sending this along to more lists, with an extra note: the
Fedora 25 Go/No-Go is on Thursday - yes, tomorrow for most of the world
- so we need YOU to help run all the tests! We need to fill out all of
the Alpha, Beta and Final (not 'RC', as the mail says...I should fix
that) tests on all the validation pages. Some particular tests that
it'd be great to have people working on are the Server tests, non-
English installs, and the Desktop 'menus' tests, which basically mean
'install Workstation or KDE and run every single app that's installed
and make sure they all at least basically work'.
If you run into any serious issues, please propose them as Final
blockers, either using blockerbugs:
https://qa.fedoraproject.org/blockerbugs/propose_bug
or simply by marking the bug as 'Blocks: FinalBlocker' (and please add
a comment with an explanation of why you think it should block
release).
Thanks a lot, everyone!
Note, there is one bug currently accepted as a blocker which is not
addressed by this compose:
https://bugzilla.redhat.com/show_bug.cgi?id=1382001
but there is clearly some sentiment to drop its blocker status, so we
decided to go ahead and run a compose and get it tested so if we do
decide to drop that bug from the blocker list, and no other blockers
appear, we can ship.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
7 years, 5 months
F25 i686 lockup with radeon 7500 (rv200)
by Felix Miata
[ 281.400022] radeon 0000:01:00.0: ring 0 stalled for more than 47834msec
[ 281.400028] radeon 0000:01:00.0: GPU lockup (current fence id
0x0000000000000e9d last fence id 0x000000000000107a on ring 0)
[ 281.904021] radeon 0000:01:00.0: ring 0 stalled for more than 48338msec
[ 281.904027] radeon 0000:01:00.0: GPU lockup (current fence id
0x0000000000000e9d last fence id 0x000000000000107e on ring 0)
Got those via remote login before Plasma locked up the machine. I tried to
kill session via remote after success to run ps -A, but response was horribly
slow, then ceased entirely before I could execute a kill.
Plasma in F23 & F24 seems to work fine on same host (gx27b).
--
"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/
7 years, 5 months
Panel mutually exclusive with root window actions
by CLOSE Dave
After some recent upgrades to F24, I see a strange problem. I run in the
systemd equivalent of runlevel 3 and start KDE with startx.
The first time I use startx after reboot, I get my normal panel but no
desktop toolbox. Clicking anywhere on the root window does nothing even
though mouse actions are defined for that. If I then logout and start
KDE again, I get a normal looking desktop except that no panel is
visible. The desktop toolbox is present and root window actions work as
they should. The scenario is repeated for all subsequent startx calls
until the next boot. On one occasion, I manually added a second panel
while in the second scenario (even though I couldn't see the first
panel). The second panel also did not appear but the desktop toolbox
went away and root window clicks became inactive. After the next boot,
both panels were visible, the desktop toolbox was not visible, and the
root window clicks were inactive.
Any ideas? Is this known or do I need to open a bug report (I didn't see
one that seemed to match).
--
Dave Close
7 years, 5 months
Re: F24, KDE Plasma 5.7.5: Menu and desktop widgets react to mouse events
with seconds of delay
by Fredy Neeser
Hi,
Fortunately, I was able to resolve this problem today with
- the upgrade to Plasma 5.8.2 (from copr repo
'group_kdesig-plasma-5-unstable')
and KDE Frameworks 5.27.0 (from repo 'updates') - system fully upgraded
today
- combined with a cleanup of Plasma configuration files -- see below.
Fredy Neeser wrote on 29.09.2016 11:49:42:
> Hi list,
>
> Two days ago, I upgraded from F22 to F24. The dnf upgrade succeeded
> and applications seem to work, but there's a new, serious desktop
> usability problem:
>
> I'm using a dual-screen setup (LVDS + external monitor), where I
> usually set Primary display = external monitor. Moreover, I place
> the KDE Panel also on the external monitor. When I do that and try
> to navigate through the Application Menu (launcher with cascading
> popup menus) or when I click / move over a desktop widget, the
> following happens:
>
> - After a mouse left click on the KDE menu icon (left hand side of
> KDE Panel), the menu pops up only after a delay of >= 1 second
> - When the mouse pointer is moved to another item in a popup menu,
> the focus visibly jumps from item to item, and a delay of at least 1
> second is added on every intermediate item.
> - When I click / move over a desktop widget, the desktop reacts with
> a delay of >= 1 second
>
> The delay problem consistently disappears when I set Primary display
> = Laptop Screen, even though the KDE Panel remains on the external
> monitor. It's strange that the KDE Panel does not move to the
> Primary display -- I'm likely seeing the following bug
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1322724
> Bug 1322724 - Plasma panel not on primary screen
>
> in F24 as well.
>
> Also, the delay problem typically reappears when I go back to
> Primary display = external monitor. Only in two out of perhaps a
> dozen logout-login cycles, I observed that the delay problem was
> gone, despite the fact that I had Primary dIsplay = external
> monitor. This may indicate some kind of race condition.
>
> Since this was an upgrade, I also tried the following, but the delay
> problem behaved the same:
> - Remove the contents of ~/.cache
> - Temporarily remove ~/.config, ~/.local and ~/.kde and login to KDE
> - Login to KDE as another user
>
> Version-release numbers:
> kscreen-5.7.5-1.fc24.x86_64
> kwin-5.7.5-1.fc24.x86_64
> plasma-desktop-5.7.5-1.fc24.x86_64
> plasma-systemsettings-5.7.5-1.fc24.x86_64
> plasma-workspace-5.7.5-2.fc24.x86_64
> plasma-workspace-libs-5.7.5-2.fc24.x86_64
> qt5-qtbase-5.6.1-3.fc24.x86_64
The problems actually first got worse with the upgrades to
Plasma 5.8.1 and 5.8.2:
- Widgets and panel respond only with seconds of delay to mouse events
(in my case, only when Primary Display = external monitor
and only for widgets and panel shown on the external monitor)
- Second panel can be added ok, but suddenly disappears in a later session
- Windows are minimizing to a second panel that is invisible
(Only <Alt>-<TAB> allowed me to find the application window in that case)
- Application icons are shown on Primary Display only
- Inconsistent size and alignment of application icons
> Any idea which component should be blamed or how to debug this problem?
Here's the solution:
Today I realized that certain Plasma config files in ~/.config
got messed up, possibly as a result of the Plasma upgrades and/or
as a result of changing the Primary Display setting back and forth,
which swaps panels.
***************************************************************
After cleaning up the Plasma config files today (see below) and
recreating my Panel and Desktop, the above problems (including
the delay problem) were all gone!!!
***************************************************************
I started to suspect a problem with Plasma desktop config files
when I read
https://www.kde.org/announcements/plasma-5.8.2-5.8.3-changelog.php
- See in particular the change
"Update screen pool connector ID ordering before adjusting
desktop containments. Commit. See bug #370711"
and the related bugs
https://bugs.kde.org/show_bug.cgi?id=369665
Impossible to modify the layout of the second screen
- where Comment 12 suggests to clean
~/.config/plasmashellrc and
~/.config/plasma-org.kde.plasma.desktop-appletsrc
https://bugs.kde.org/show_bug.cgi?id=370711
wallpaper on second monitor is always set to default
My problems did not look exactly like those in bug #369665, but
the cleaning procedure suggested by Comment 12 saved my day:
I removed
~/.config/plasmashellrc and
~/.config/plasma-org.kde.plasma.desktop-appletsrc
executed 'kquitapp5 plasmashell' from a konsole window,
and then 'kstart5 plasmashell' to restart it.
This resulted in clean (almost empty) desktop containments with
fresh wallpapers (one on LVDS, the other on the external monitor)
and one (default) panel placed on the primary display.
After this cleanup, adding an application to Desktop creates
an icon on each desktop containment. Application icons are
consistent in size and nicely aligned; moreover, their position
can be adjusted separately on each desktop containment.
I should add that this cleanup causes plasmashell to create
(default) desktop containments with
Layout = Folder View
rather than
Layout = Desktop
which I had before.
So the nice behavior with application icons can be attributed
to the Folder View layout (you can see the layout by right
clicking the desktop > Desktop Settings > Wallpaper).
Icons added to Folder View layout are visible on each screen;
they are not shown when you convert the layout to Desktop
but reappear when you go back to Folder View.
Icons added to Desktop layout are visible only on the screen
to which they are added; otoh, they are also shown when the
layout is switched to Folder View.
Somewhat inconsistent ... so it seems best to stick to
one layout ...
I really think my previous Plasma config files were corrupted:
The file ~/.config/plasma-org.kde.plasma.desktop-appletsrc
contained
- 3 containments of type org.kde.desktopcontainment,
with references to lastScreen=0, 1, and 2,
even though I'm using two screens only.
- 2 containments of type org.kde.panel and
2 containments of type org.kde.plasma.private.systemtray
but only one panel (and systemtray) was shown.
Here's the relevant portion of
~/.config/plasma-org.kde.plasma.desktop-appletsrc
showing just Desktop Containments, Panels, and System Trays:
// Desktop Containments
[Containments][169]
activityId=abb2c567-3754-4794-ab37-4b3f73a33619
formfactor=0
immutability=1
lastScreen=2
location=0
plugin=org.kde.desktopcontainment
wallpaperplugin=org.kde.image
[Containments][19]
activityId=abb2c567-3754-4794-ab37-4b3f73a33619
formfactor=0
immutability=1
lastScreen=0
location=0
plugin=org.kde.desktopcontainment
wallpaperplugin=org.kde.image
[Containments][26]
activityId=abb2c567-3754-4794-ab37-4b3f73a33619
formfactor=0
immutability=1
lastScreen=1
location=0
plugin=org.kde.desktopcontainment
wallpaperplugin=org.kde.image
// Panels
[Containments][111]
activityId=
formfactor=2
immutability=1
lastScreen=2
location=4
plugin=org.kde.panel
wallpaperplugin=org.kde.image
[Containments][139]
activityId=
formfactor=2
immutability=1
lastScreen=1
location=4
plugin=org.kde.panel
wallpaperplugin=org.kde.image
// System Trays
[Containments][116]
activityId=
formfactor=2
immutability=1
lastScreen=2
location=4
plugin=org.kde.plasma.private.systemtray
wallpaperplugin=org.kde.image
[Containments][144]
activityId=
formfactor=2
immutability=1
lastScreen=1
location=4
plugin=org.kde.plasma.private.systemtray
wallpaperplugin=org.kde.image
// End of snippets from ~/.config/plasma-org.kde.plasma.desktop-appletsrc
Regards
Fredy Neeser
IBM Zurich Research
7 years, 5 months
Re: Panel mutually exclusive with root window actions
by Fredy Neeser
Fredy Neeser/Zurich/IBM wrote on 01.11.2016 20:33:36:
...
> I removed
> ~/.config/plasmashellrc and
> ~/.config/plasma-org.kde.plasma.desktop-appletsrc
>
> executed 'kquitapp5 plasmashell' from a konsole window,
> and then 'kstart5 plasmashell' to restart it.
> This resulted in clean (almost empty) desktop containments with
> fresh wallpapers (one on LVDS, the other on the external monitor)
> and one (default) panel placed on the primary display.
>
> After this cleanup, adding an application to Desktop creates
> an icon on each desktop containment. Application icons are
> consistent in size and nicely aligned; moreover, their position
> can be adjusted separately on each desktop containment.
I should add that this cleanup causes plasmashell to create
(default) desktop containments with
Layout = Folder View
rather than
Layout = Desktop
which I had before.
So the nice behavior with application icons can be attributed
to the Folder View layout (you can see the layout by right
clicking the desktop > Desktop Settings > Wallpaper).
Icons added to Folder View layout are visible on each screen;
they are not shown when you convert the layout to Desktop
but reappear when you go back to Folder View.
Icons added to Desktop layout are visible only on the screen
to which they are added; otoh, they are also shown when the
layout is switched to Folder View.
Somewhat inconsistent ... so it seems best to stick to
one layout ...
Cheers,
Fredy Neeser
IBM Research Zurich
7 years, 5 months
KMail not working (again)
by Timothy Murphy
When I start KMail I get gobbledygook in the Message window.
When I run "sudo akonadictl restart" I am told akonadi is not running.
I see no way to start it.
=========================
[tim@william ~]$ sudo akonadictl start
[tim@william ~]$ sudo akonadictl restart
Akonadi is not running.
[tim@william ~]$ /bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/tmp/akonadi-
root.ZrNeSQ/mysql.socket' (2 "No such file or directory")'
Check that mysqld is running and that the socket: '/tmp/akonadi-
root.ZrNeSQ/mysql.socket' exists!
[tim@william ~]$ ps aux | grep mysql
tim 1708 0.5 1.5 2568696 127296 ? Sl 17:06 0:05
/usr/libexec/mysqld --defaults-
file=/home/tim/.local/share/akonadi/mysql.conf --
datadir=/home/tim/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-
tim.G41xdj/mysql.socket
[tim@william ~]$ sudo ls /tmp/akonadi-root.ZrNeSQ/mysql.socket
ls: cannot access '/tmp/akonadi-root.ZrNeSQ/mysql.socket': No such file or
directory
=========================
I've been getting the KMail message mix-up for some days,
but have always been able to recover with "sudo akonadictl restar".
But today after the latest updates I get the above.
Any advice or elucidation gratefully received.
--
Timothy Murphy
gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin
7 years, 5 months
