Bug 16725 - Cauldron update on 64-bit KDE Mageia-5 netbook fails to offer Plasma5 at Login, and fails on KDE login
Summary: Cauldron update on 64-bit KDE Mageia-5 netbook fails to offer Plasma5 at Logi...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Nicolas Lécureuil
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 17523
  Show dependency treegraph
 
Reported: 2015-09-09 19:12 CEST by Maurice Batey
Modified: 2016-01-19 11:14 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
(MB) Log of cauldron update 9/9/15 "Packages are up to date" (564 bytes, text/plain)
2015-09-09 19:21 CEST, Maurice Batey
Details

Description Maurice Batey 2015-09-09 19:12:44 CEST
Description of problem:

After updating a 64-bit Mageia-5 installation with Cauldron (to the point where Urpmi reports "Packages are up to date"):

  (1) 'Plasma' is not offered at Login

  (2) After Logging in with KDE, the screen goes blank and stays blank,
EXCEPT for a confirmation that Yakuake (from a user startup config) has been started - and can be used from PF12.

Version-Release number of selected component (if applicable):

  Cauldron as of 9/9/2015.

How reproducible:


Steps to Reproduce:
1. Install 64-bit KDE Mageia-5 on netbook (Samsung NC110).

2. urpmi -auto-update --auto  (checked first with "--test" option) until  reports "Packages are up to date" (in this case 9/9/2015)

3. Reboot and  note that:

   (a) At login, 'KDE' is offered; no sign of 'Plasma'
   (b) After KDE login, screen goes blank, except for a report that 'Yakuake has been started' (and is usable!)

   
 



Reproducible: 

Steps to Reproduce:
Comment 1 Maurice Batey 2015-09-09 19:21:47 CEST
Created attachment 7001 [details]
(MB) Log of cauldron update 9/9/15 "Packages are up to date"

Log of update showing 'Packages are up to date".

N.B. One difference between the updates on netbook and on PC is:

   On netbook, booting shows "Starting version 225", whereas
        on PC. booting shows "Starting version 224".
Maurice Batey 2015-09-09 19:22:11 CEST

CC: (none) => maurice

Samuel Verschelde 2015-09-10 10:29:36 CEST

Assignee: bugsquad => mageia

Comment 2 Nicolas Lécureuil 2015-09-10 11:36:53 CEST
please provide:

rpm -qa | grep plasma
Comment 3 Maurice Batey 2015-09-10 13:37:00 CEST
rpm -qa | grep plasma
lib64plasmacomicprovidercore1-5.4.0-1.mga6
lib64plasma3-4.14.11-4.mga6
lib64plasmagenericshell4-4.11.16-5.mga5
task-plasma5-5.3.2-2.mga6
lib64plasma-geolocation-interface5-5.4.0-1.mga6
lib64plasma_applet_system_monitor4-4.11.16-5.mga5
kdebase4-workspace-plasma-config-4.11.16-5.mga5
plasma-workspace-5.4.0-1.mga6
lib64plasmaclock4-4.11.16-5.mga5
lib64kf5plasma5-5.13.0-1.mga6
plasma-framework-5.13.0-1.mga6
plasma-desktop-5.4.0-1.mga6
plasma-desktop-handbook-5.4.0-1.mga6
lib64plasmaweather4-4.14.3-4.mga5
task-plasma5-minimal-5.3.2-2.mga6
lib64plasma-geolocation-interface4-4.11.16-5.mga5
lib64kf5plasmaquick5-5.13.0-1.mga6
kdeplasma-addons-5.4.0-1.mga6
plasma-workspace-handbook-5.4.0-1.mga6
Comment 4 Maurice Batey 2015-09-13 17:21:58 CEST
I'm wondering if something in the netbook's spec is failing the criteria for offering Plasma5.

(E.g. screen resolution of 1024x600, which I saw somewhere prevents Windows 10 running.)

There has been no problem installing/running Mageia-5 and earlier, although I've never been able to get the video output onto an external monitor.
Comment 5 Maurice Batey 2015-09-14 19:20:34 CEST
After this afternoon's Cauldron update including plasma-workspace and a reboot, I now - for the 1st time - see 'Plasma' offered as DM on login screen rather than KDE!

Sadly, Login once again gave a blank screen (apart from  a hollow 'X'  mouse pointer and a report that 'Yakuake has been started').

Suggestions?!
Comment 6 Maurice Batey 2015-09-17 14:43:28 CEST
> screen resolution of 1024x600

In today's Cauldron update (including new kernel) I saw that a 'default screen resolution of 1024x768' had been set.

 Still wondering what is preventing a successful Plasma5 login.
(Get just blank screen, apart from "Yakuake started" report.)
Comment 7 Rémi Verschelde 2015-09-17 14:45:14 CEST
(In reply to Maurice Batey from comment #6)
> > screen resolution of 1024x600
> 
> In today's Cauldron update (including new kernel) I saw that a 'default
> screen resolution of 1024x768' had been set.

That's an expected behaviour due to bug 763.
Comment 8 Maurice Batey 2015-09-17 15:49:11 CEST
> That's an expected behaviour due to bug 763.

Which says "...leave this bug for mga6 and list ALL the DMs and DE's (possibly in different BZs and have them blocking this one... in order to get it fixed for real."

Is that what's failing the Plasma5 login here, though?
Comment 9 Rémi Verschelde 2015-09-17 16:01:20 CEST
(In reply to Maurice Batey from comment #8)
> > That's an expected behaviour due to bug 763.
> 
> Which says "...leave this bug for mga6 and list ALL the DMs and DE's
> (possibly in different BZs and have them blocking this one... in order to
> get it fixed for real."
> 
> Is that what's failing the Plasma5 login here, though?

No I don't think it's related to your issue at all. Bug 763 is just about the default background symlink pointed to an image of the wrong resolution, in the worst case if it affected Plasma you would have a badly scaled background. And the bug itself is worked around via a script at boot, so it shouldn't be an issue. I was just pointed you to the bug report FYI, but that was to indicate that it's a false alert probably non relevant for your issue.
Comment 10 Maurice Batey 2015-09-25 14:21:13 CEST
> ... for the 1st time - see 'Plasma' offered as DM on login screen

But - after 11 days of clean Cauldron updates - the plasma login still ends up with a blank screen instead of the kaleidoscope - though Yakuake is usable.
Comment 11 Maurice Batey 2015-10-09 20:39:49 CEST
By removing Yakuake (thanks to a hint from Claire), I can now achieve a successful Plasma5 login on the netbook.

Will raise bug report if necessary.

Question is, why does Yakuake freeze the Plasma login on the netbook  when it doesn't on the PC?
Comment 12 Maurice Batey 2015-10-10 19:07:46 CEST
N.B. The Yakuake problem is now in:

     https://bugs.mageia.org/show_bug.cgi?id=16934
Comment 13 Maurice Batey 2015-10-11 15:52:03 CEST
Broadcom WiFi working fine on netbook, though cannot see 'network status' icon (presumably because of missing systray).
Comment 14 Rémi Verschelde 2016-01-19 11:14:58 CET
Issue was fixed as of comment 5, the rest is about different issues (some fixed, some current, but they don't belong in this bug report).

Status: NEW => RESOLVED
Blocks: (none) => 17523
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.