I have already had Mageia 2 running with the KDE desktop. Then I entered the Mageia Control Center and entered the Boot Configuration of the graphical desktop environment. I clicked abort. But somehow the KDE start has been deactivated by this. I cannot reset it. It now always starts GNOME instead of KDE.
CC: (none) => flinkHardware: i586 => x86_64
Hi, sorry but I don't understand your description, can you explain a bit more ? also have you error in /var/log/syslog or ~/.xsession-errors .xsession-errors.old
The Mandriva Control Center allows to set the display manager as the boot option. If I set KDE here, then KDE does not start but GNOME. Is this still unclear? There are several ERROR lines in /var/log/syslog. e.g. ----------- Aug 5 06:32:40 localhost kernel: [ 3.437014] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state Aug 5 06:32:40 localhost kernel: [ 3.438001] render error detected, EIR: 0x00000010 Aug 5 06:32:40 localhost kernel: [ 3.438001] IPEIR: 0x00000000 Aug 5 06:32:40 localhost kernel: [ 3.438001] IPEHR: 0x00000000 Aug 5 06:32:40 localhost kernel: [ 3.438001] INSTDONE: 0xfffffffe Aug 5 06:32:40 localhost kernel: [ 3.438001] INSTPS: 0x00000000 Aug 5 06:32:40 localhost kernel: [ 3.438001] INSTDONE1: 0xffffffff Aug 5 06:32:40 localhost kernel: [ 3.438001] ACTHD: 0x00000000 Aug 5 06:32:40 localhost kernel: [ 3.438001] page table error Aug 5 06:32:40 localhost kernel: [ 3.438001] PGTBL_ER: 0x00000001 Aug 5 06:32:40 localhost kernel: [ 3.438001] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking Aug 5 06:32:40 localhost kernel: [ 3.573709] checking generic (c0000000 3ff0000) vs hw (c0000000 10000000) Aug 5 06:32:40 localhost kernel: [ 3.573712] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver ------ and many others. ~/.xsession-errors: ------------ (gnome-panel:27147): Gtk-CRITICAL **: _gtk_style_properties_set_property_by_property: assertion `_gtk_css_value_holds (value, _gtk_css_style_property_get_computed_type (style_prop))' failed (notification-daemon:27174): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -23 and height 27 (gnome-panel:27147): Gtk-CRITICAL **: _gtk_style_properties_set_property_by_property: assertion `_gtk_css_value_holds (value, _gtk_css_style_property_get_computed_type (style_prop))' failed (gnome-panel:27147): Gtk-CRITICAL **: _gtk_style_properties_set_property_by_property: assertion `_gtk_css_value_holds (value, _gtk_css_style_property_get_computed_type (style_prop))' failed (operapluginwrapper-ia32-linux:9616): Gtk-WARNING **: Impossible de trouver le moteur de thème dans module_path : « clearlooks » Gtk-Message: Failed to load module "canberra-gtk-module" (fluendo-dvd:12750): GLib-GObject-CRITICAL **: Read-only property 'read-only-view' on class 'GeeAbstractList' has type 'GeeCollection' which is not equal to or more restrictive than the type 'GeeList' of the property on the interface 'GeeList' Cannot open /dev/input/eventX: Permission non accordée -------------- .xsession-errors.old: /etc/X11/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- /usr/share/X11/xdm/Xsession KDE4 localhost being added to access control list Running update-menus... menu generation finished startkde: Starting up... Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kbuildsycoca4 running... kbuildsycoca4(3614) KConfigGroup::readXdgListEntry: List entry x-scheme-handler/file in "/home/franz/.local/share/applications/mimeapps.list" is not compliant with XDG standard (missing trailing semicolon). kbuildsycoca4(3614) KConfigGroup::readXdgListEntry: List entry x-scheme-handler/trash in "/home/franz/.local/share/applications/mimeapps.list" is not compliant with XDG standard (missing trailing semicolon). QObject::connect: Cannot connect (null)::deviceFound(Device*) to BlueDevilDaemon::deviceFound(Device*) QObject::connect: Cannot connect QTimer::timeout() to (null)::stopDiscovery() QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.9' OpenGL vendor string: Tungsten Graphics, Inc OpenGL renderer string: Mesa DRI Mobile Intelî GM45 Express Chipset OpenGL version string: 2.1 Mesa 8.0.2 OpenGL shading language version string: 1.20 Driver: Intel GPU class: i965 OpenGL version: 2.1 GLSL version: 1.20 Mesa version: 8.0.2 X server version: 1.11.4 Linux kernel version: 3.3.6 Direct rendering: yes Requires strict binding: yes GLSL shaders: yes Texture NPOT support: yes kwin(3872): ""fsrestore1" - conversion of "0,0,0,0" to QRect failed" kwin(3872): ""restore2" - conversion of "0,0,0,0" to QRect failed" kwin(3872): ""fsrestore2" - conversion of "0,0,0,0" to QRect failed" kwin(3872): ""restore3" - conversion of "0,0,0,0" to QRect failed" kwin(3872): ""fsrestore3" - conversion of "0,0,0,0" to QRect failed" ---------------------------
ok so you are talking about the autologin, what about if you re-run the apps ? check also the modified files aka /var/lib/mageia/kde4-profiles/Default/share/config/kdm/kdmrc /etc/X11/gdm/custom.conf /etc/sysconfig/autologin /etc/sysconfig/desktop /home/$USER/.desktop (thanks to syslog)
Source RPM: (none) => autologin
Created attachment 2614 [details] kdmrc
I wanted to switch back to KDE. How can I start it again? I thought that the Mandriva Control Center Boot option should do the job. The autologin works fine, but only under GNOME.
Created attachment 2615 [details] custom.conf
Created attachment 2616 [details] autologin
Created attachment 2617 [details] desktop
>I wanted to switch back to KDE. How can I start it again? In the "Boot Configuration of the graphical desktop environment" in the MCC what you have used for now or try to modify the line DESKTOP=GNOME to DESKTOP=KDE in the desktop file or search the kde system-settings, conf of kdm, autologin or something like that (but disable the mcc autologin if you use the last way)
After retry to start the already preset "Boot Configuration" in the MCC to KDE, the computer shuts down and ends up finally in a black page with error messages: syslog: Aug 7 09:30:02 localhost kernel: [ 4.440014] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state Aug 7 09:30:02 localhost kernel: [ 4.442064] render error detected, EIR: 0x00000010 Aug 7 09:30:02 localhost kernel: [ 4.442064] IPEIR: 0x00000000 Aug 7 09:30:02 localhost kernel: [ 4.442064] IPEHR: 0x00000000 Aug 7 09:30:02 localhost kernel: [ 4.442064] INSTDONE: 0xfffffffe Aug 7 09:30:02 localhost kernel: [ 4.442064] INSTPS: 0x00000000 Aug 7 09:30:02 localhost kernel: [ 4.442064] INSTDONE1: 0xffffffff Aug 7 09:30:02 localhost kernel: [ 4.442064] ACTHD: 0x00000000 Aug 7 09:30:02 localhost kernel: [ 4.442064] page table error Aug 7 09:30:02 localhost kernel: [ 4.442064] PGTBL_ER: 0x00000001 Aug 7 09:30:02 localhost kernel: [ 4.442064] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking Aug 7 09:30:02 localhost kernel: [ 4.580688] checking generic (c0000000 3ff0000) vs hw (c0000000 10000000) Aug 7 09:30:02 localhost kernel: [ 4.580692] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver Aug 7 09:30:02 localhost kernel: [ 4.580711] Console: switching to colour dummy device 80x25 Aug 7 09:30:02 localhost kernel: [ 4.581153] fbcon: inteldrmfb (fb0) is primary device Aug 7 09:30:02 localhost kernel: [ 5.005017] Console: switching to colour frame buffer device 160x50 Aug 7 09:30:02 localhost kernel: [ 5.036113] fb0: inteldrmfb frame buffer device Aug 7 09:30:02 localhost kernel: [ 5.036115] drm: registered panic notifier Aug 7 09:30:02 localhost kernel: [ 5.041285] ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x0000000000000005) is beyond end of object (20120111/exoparg2-418) Aug 7 09:30:02 localhost kernel: [ 5.041295] ACPI Error: Method parse/execution failed [\_SB_.PCI0.GFX0._DOD] (Node ffff8801b404baf0), AE_AML_PACKAGE_LIMIT (20120111/psparse-536) Aug 7 09:30:02 localhost kernel: [ 5.041304] ACPI Exception: AE_AML_PACKAGE_LIMIT, Evaluating _DOD (20120111/video-1147) Aug 7 09:30:02 localhost kernel: [ 5.042178] acpi device:06: registered as cooling_device0 Aug 7 09:30:02 localhost kernel: [ 5.042335] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input5 .... ug 7 09:30:02 localhost NetworkManager[985]: <warn> failed to allocate link cache: (-10) Operation not supported Aug 7 09:30:02 localhost kernel: [ 56.716819] PPP generic driver version 2.4.2 Aug 7 09:30:02 localhost kernel: [ 56.718539] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated). Use CAP_NET_ADMIN and alias netdev-ppp0 instead Aug 7 09:30:02 localhost NetworkManager[985]: read_mac_address: assertion `*error == NULL' failed Aug 7 09:30:02 localhost NetworkManager[985]: ifcfg-rh: warning: Unable to discover MAC address: ioctl error Aug 7 09:30:02 localhost kernel: [ 56.721011] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated). Use CAP_NET_ADMIN and alias netdev-ppp0 instead Aug 7 09:30:02 localhost NetworkManager[985]: ifcfg-rh: read connection 'Système ppp0' Aug 7 09:30:02 localhost NetworkManager[985]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-wlan0 ... Aug 7 09:30:02 localhost NetworkManager[985]: <warn> failed to allocate link cache: (-10) Operation not supported Aug 7 09:30:02 localhost NetworkManager[985]: ifcfg-rh: error: Missing SSID Aug 7 09:30:02 localhost NetworkManager[985]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ... Aug 7 09:30:02 localhost NetworkManager[985]: <info> trying to start the modem manager... Aug 7 09:30:02 localhost dbus[1053]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper) Aug 7 09:30:02 localhost dbus-daemon[1053]: dbus[1053]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper) --------------- I had to press the power button and it restarts with GNOME and not KDE. I will edit now the .desktop file of the local user: DESKTOP=KDE instead of DESKTOP=GNOME However the bug in the MCC Boot Option should be fixed.
.desktop: DESKTOP=KDE This has no effect at all. The GNOME desktop starts even if this line is set to KDE.
Which dm are you using? Are you sure it is not gdm eventually ?
CC: (none) => balcaen.john
Created attachment 2622 [details] GDM - The GNOME Display Manager The desktop looks like the GNOME Display Manager (gdm)
Check: cat /etc/sysconfig/desktop
cat /etc/sysconfig/desktop: DISPLAYMANAGER=KDM DESKTOP=GNOME So I have now changed it to: DISPLAYMANAGER=KDM DESKTOP=KDE And this has no effect. Still GNOME is getting started.
You're confusing the desktop with the DM. /etc/sysconfig/desktop just determines the default desktop. All DMs can start most desktop types, and they have a widget (the pencil/paper in KDM) to let you choose between KDE, GNOME, etc. Once you choose a desktop, that's what you'll continue to get until you choose another. So just use your DM's widget to choose KDE4, and you should be fine. Each DM has a hidden file in your $HOME which records your last choice.
CC: (none) => ftg
In addition to modifying ~/.desktop instead of /etc/sysconfig/desktop, the value used for DESKTOP= must be the same as the one shown by grep NAME /etc/X11/wmsession.d/* So for kde, you need DESKTOP=KDE4 Just to clarify, /etc/sysconfig/desktop is used to select the default desktop, when the user doesn't have a ~/.desktop file. Once the display manager is used to select a specific desktop, the ~/.desktop file is created, and will override the value set in /etc/sysconfig/desktop.
CC: (none) => davidwhodgins
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD