Bug 17231 - No desktop manager with Live PLASMA install from 6dev1 live iso
Summary: No desktop manager with Live PLASMA install from 6dev1 live iso
Status: RESOLVED DUPLICATE of bug 17221
Alias: None
Product: Mageia
Classification: Unclassified
Component: Release (media or process) (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard: 6dev1
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-26 17:00 CET by Len Lawrence
Modified: 2016-01-19 09:30 CET (History)
6 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
Xorg log after running drakx11 during live boot (22.56 KB, text/x-log)
2015-11-26 18:20 CET, Len Lawrence
Details
Xorg.0.log from _before_ running XFdrake (7.56 KB, text/plain)
2015-11-27 16:00 CET, Marja Van Waes
Details

Description Len Lawrence 2015-11-26 17:00:27 CET
Description of problem:
Dell XPS 1730M laptop with GeForce 8700M
x86_64

This really a sort of progress report to help show what is going on with the new isos.
I escaped the Plymouth screen to see what was going on during the boot.

One of the first messages was "Failed to unlink live" or something similar but the rest of the log looked OK.
The installation stopped at "a problem with the graphics display" and the recommendation that the user hit any key to get a root prompt.  It took me a while to realize that the keyboard was being polled about once per second so the key needed to be depressed for a couple of seconds.  That enabled drakx11  to be run; chose the nvidia proprietary driver,
"Using /etc/nvidia340/ld.so.conf to provide 'gl_conf'" 
The nvidia logo flashed up on the test, then "You need to reboot for settings to take effect".  If the user does that it is a matter of running through the same loop so I ignored it the second time round and waited.
Finally: "Xauth: file /root/.Xauthority does not exist"
and a root prompt.  From there it was possible to login live.
Under live, ran startx --bpp 24
which produced a very basic desktop with two xterms without decorations on a black screen.  The mouse was configured for sloppy focus.  The screen resolution looked like the native setting, 1920x1200.  Both xdpyinfo and nvidia-settings confirm this.  konsole can be launched but all new windows pile up at +0+0.
mcc cannot be launched from a root console.
No way to logout.

I have Xorg.0.log and the output of xdpyinfo but don't know how to submit/attach them.

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

How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
claire robinson 2015-11-26 17:27:45 CET

CC: (none) => eeeemail, sysadmin-bugs, tmb
Component: Installer => Release (media or process)
Summary: No desktop manager with Live PLASMA install from dev1 iso => No desktop manager with Live PLASMA install from 6dev1 live iso
Whiteboard: (none) => 6dev1

Comment 1 Len Lawrence 2015-11-26 18:14:23 CET
Plasma5 desktop now running.

After drakx11 I had forgotten to run the 'systemctl default' command.

'startx startkde' failed for live user on what looked like a permissions problem (no authority to modprobe nvidia) so back to root.

That worked fine and the multicoloured Plasma desktop appeared and was usable.
The bug remains valid because the user has to trace these unexpected steps.
The drakx11 thing is a separate issue which needs a bug report of its own.
Comment 2 Len Lawrence 2015-11-26 18:20:26 CET
Created attachment 7239 [details]
Xorg log after running drakx11 during live boot

Not sure of the relevance of this in view of the successful boot.
Comment 3 Marja Van Waes 2015-11-27 16:00:26 CET
Created attachment 7242 [details]
Xorg.0.log from _before_ running XFdrake

I can confirm the problem with 
Mageia-6-dev1-LiveDVD-PLASMA5-x86_64-DVD
from 
Mon Nov 23 16:00:00 CET 2015

After loading Nouveau, it looks for the "nv" module, which can't be found.

[   165.445] (II) LoadModule: "nouveau"
[   165.445] (II) Loading /usr/lib64/xorg/modules/drivers/nouveau_drv.so
[   165.445] (II) Module nouveau: vendor="X.Org Foundation"
[   165.445]    compiled for 1.18.0, module version = 1.0.11
[   165.445]    Module class: X.Org Video Driver
[   165.445]    ABI class: X.Org Video Driver, version 20.0
[   165.445] (II) LoadModule: "nv"
[   165.446] (WW) Warning, couldn't open module nv
[   165.446] (II) UnloadModule: "nv"
[   165.446] (II) Unloading nv
[   165.446] (EE) Failed to load module "nv" (module does not exist, 0)

later there is

[   165.447] (WW) xf86OpenConsole: setpgid failed: Operation not permitted
[   165.447] (WW) xf86OpenConsole: setsid failed: Operation not permitted
[   167.108] (EE) [drm] Failed to open DRM device for pci:0000:01:00.0: -19
[   167.108] (EE) open /dev/dri/card0: No such file or directory
[   167.108] (WW) Falling back to old probe method for modesetting
[   167.108] (EE) open /dev/dri/card0: No such file or directory

etc (even trying and failing fbdev)

CC: (none) => marja11

Marja Van Waes 2015-11-27 16:03:10 CET

Assignee: bugsquad => tmb

Comment 4 Dick Gevers 2015-12-04 15:28:44 CET
I noticed with drakedm that gdm is the default WM of choice but gdm doe snot work hence no X, moreover in $PATH cannot find startplasmacompositor or startkde

CC: (none) => dvgevers

Comment 5 Florian Hubold 2015-12-13 16:24:31 CET
Sounds to me like an exact duplicate of bug 17221 which was also reported earlier.

FWIW, easiest way to check is to boot to runlevel 3 by pressing "F6" in boot menu, select "Default", then selecting "Boot Mageia" again and appending "3" (without the quotes) to the kernel line. Then login as root and start sddm via "systemctl start sddm" then wait a few seconds. Switch to e.g. tty2 and login as root. Then run
"journalctl -ab -p err" to show all journal entries of type error, the last one should be something like

Dec 21 10:18:49 localhost sddm-greeter[1774]: Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options

CC: (none) => doktor5000

Comment 6 Rémi Verschelde 2016-01-19 09:30:54 CET
Closing as duplicate as per comment 5.

*** This bug has been marked as a duplicate of bug 17221 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE


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