Mageia forum

I've got an absolutely bizarre problem with my laptop. A while ago I had a heavy system crash which stopped me using the latest kernel (it would only boot into the older one). Today I had another less heavy crash, in that I was at least able to CTL ALT Backspace and relog. However, since the reboot, the screen seems to have gone to something like a 800x600 window within the full resolution of the monitor (it's a 1920 x 1200). As I move the mouse around the screen and the mouse hits the edge of the screen, the screen moves so that the low res section of the screen moves to show the full extent of the screen resolution.

I have tried the following:

Delete the nvidia driver, use nouveau, reinstall nvidia driver. No help.

Delete xorg.conf and reconfigure. No help.

Reinstall Mageia completely. No help.

Delete .kde4 directory. No help.

Does this seem familiar to anyone? Have I explained it OK? Can anyone suggest what might be going on?

Thanks.

Well, I deleted xorg.conf and rebooted BEFORE recreating it, then it automatically used nouveau which, for once worked well enough to install all the updates and the latest kernel does work with the nvidia driver.

Bah.

These last two Mageia versions have been very unreliable and the Bluetooth bug I filed that COMPLETELY locks up my machine has not even had a reply to it. Poor stuff.

DiBosco wrote:.....
These last two Mageia versions have been very unreliable and the Bluetooth bug I filed that COMPLETELY locks up my machine has not even had a reply to it. Poor stuff.

This completely contradicts the general feel and experience by the majority of users,
So, i guess, your conclusion is a bit beaten up, isn't it?

Nevertheless, we are Mageia all together; you, me and all others around using and working on it.
We build it all together by means of use and commenting, or contributing in more constructive ways.
So, to have a distribution, as you would like to see it, don't hesitate and jump in, get involved into the making.
https://www.mageia.org/en/contribute/

Don't be so defensive. That does the distribution no good. You need to accept that just because it works for you, does not mean it works well for everyone. Even if it works for the majority does not mean there are BIG issues for others. I have had more crashes with M2 and M3 than in all my thirteen years using Linux put together. That is *not* good. This is not on juust one machine either, this is across three machines.

For me, on my two laptops, especially with rhw Broadcom drivers on Mageia 2, it's been so bad I had to switch to SuSE. Although the Broadcom issue is fixed, on the laptop I did switch back to Mageia, not only does Bluetooth completely lock up my machine (to an extent I need a forced ungraceful power down), but the only way to get graphics working properly is to install the nvidia driver from the nvidia website. So, my conclusion is most definitely not beaten up and you dissing my experience is just a splendid impression of an ostrich. Had I not been using Mandrake since year 2000 and have so much loyalty to Mageia I'd have changed to else on all machines. If that's not unreliable, I don't know what is.

As for getting into the making of Mageia, I've been asking for over a year for someone to mentor me wirh packaging. I posted a bug request for the Bluetooth problem and not even had a reply. A new package request for Mageia 2 never got actioned and when I requested the same package for 3 I was told it was a duplicate of 2's, so it's clear there's a shortage of packagers.

It's not that much about defending, concerning myself.
My reaction is about trying, to prevent generalizing.

The impression to the reader could be given, that the work of so many volunteers,
in the end resulted in two releases that should be labeled as: "have been very unreliable".

Well, this is two-fold:

Yes, we are definitely short on packagers, and hence also on mentors. BUT, our mentoring program recently underwent an overhaul, please see https://ml.mageia.org/l/arc/dev/2013-05/msg00592.html and contact our mentoring manager Malo directly via mail.
(you need to click the "no a spammer" button and re-visit the URL again to see the mail)

For the bugreport and you hardware issues: At first for hardware/kernel developers we're even shorter, actually kernel updates
bugfixes and stuff is done by only one person. If he cannot reproduce your issue, and you have no proposed solution/workaround,
chances are it can and will not be fixed, only by random chance if it gets fixed upstream.