Message: previous - next
Month: August 2017

Re: [trinity-users] Mageia 6 crash on login, can't start desktop

From: Tim Williams <tmw@...>
Date: Sun, 6 Aug 2017 20:57:43 +0100
On 06/08/17 20:14, Felix Miata wrote:
> Tim Williams composed on 2017-08-06 17:11 (UTC+0100):
> Installed in what context? Upgrade from 5 to 6, or fresh 6? I saw a lot of
> trouble on Mageia dev and user mailing lists in pre-release testing of upgrades.
> If upgrade, fresh might turn out to be your expedient solution.

In all cases upgraded from 5. I removed Trinity during the upgrade to
make dependency resolution easier and re-installed it later. All the
upgrades were done using the command line method from the installation
instructions. After the upgrade was finished I manually scanned for any
remaining mga5 packages and removed or upgraded as appropriate, so there
shouldn't be any mga5 hangovers on the system in terms of code, although
that doesn't exclude the possibility of an issue with a config file.

If no other suggestions are forthcoming I'll try a clean install on a
spare hard disk with the same hardware, I'll also use this to check it
isn't the NFS mounted home causing an issue.

> I have 4 TDE on Mageia PCs, but ATM I have no recollection which have upgrades
> from 5 to 6 or even have TDE instead of KDE5. What I can say for sure ATM is:
> 1-I don't have gdm, sddm or lightdm installed on any of them. All have either
> TDM or KDM4.

I was using TDM on 2 of my 3 systems, I only switched when it crashed!

> 2-None of my PCs have or ever had an NVidia proprietary Linux driver installed.
> Maybe a search for NVidia in the Mageia mailing list archives would turn up a clue?
> The mga6 Xorg server version has the modesetting driver incorporated, moved from
> being a separate driver package as of 1.17.x. Eradicating NVidia and
> x11-driver-video-nouveau (and remembering to get nomodeset off the kernel
> cmdline) to let it be used might be worth trying.

There's no sign of nomodeset in the boot parameters.

I'll see if any clues turn up, although I'm tempted to try the spare HD

For reference, running ksmserver with gdb gives the following, which may
or may not be relevant:

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff4c196a0 in TQString::TQString(TQString const&) ()
   from /lib64/

Thanks again!

Tim W

Tim Williams BSc MSc MBCS
58 Jacoby Place
Priory Road
B5 7UW
United Kingdom

Web :,
Tel : +44 (0)844 487 4117

AutoTrain is a trading name of EuroMotor-AutoTrain LLP
Registered in the United Kingdom, number: OC317070.