I performed a internet in-line update of Mageia 7 to 8, first time I
tried this method of update. After a few hours it said the update
installation was successful, and have had zero issues, other than
needing to change the odd thing here and there due to updated way of
doing certain things.

As per the errata, I disabled 3D ergo compiz-fusion before the update.

However, with the system working again, I re-enabled 3D, and when
logging in to a user account, the desktop is black, nothing is loaded as
my "loading" tune does not play, the cube works - but apart from the top
and bottom, is completely black. Only the mouse is visible.

I've had a go at lots of old solutions, but nothing seems to solve the
problem.

If I executed in the non 3D enabled desktop "compiz --replace &" in a
console session, I get some of the Compiz 3D and also by magic emerald
also works. Unfortunately I can't use emerald without Compiz, and ALL
the window decorations in Plasma look terrible.

None of these issues were in Mageia7 before the upgrade. Any
suggestions? KWin isn't doing any 3D as Compiz takes over at login.

On Sun, 4 Jul 2021 20:42:38 +0100, Ar wrote:
> I performed a internet in-line update of Mageia 7 to 8, first time I
> tried this method of update. After a few hours it said the update
> installation was successful, and have had zero issues, other than
> needing to change the odd thing here and there due to updated way of
> doing certain things.
>
> As per the errata, I disabled 3D ergo compiz-fusion before the update.
>
> However, with the system working again, I re-enabled 3D, and when
> logging in to a user account, the desktop is black, nothing is loaded as
> my "loading" tune does not play, the cube works - but apart from the top
> and bottom, is completely black. Only the mouse is visible.

First thing to verify is if the problem is with user account or system.

I use a test account, junk. Makes it easy to wipe and login again
when testing anything.

If you log into junk and have no problem, then you know the problem is
in the user account.

If junk is broke you know is is a system wide problem.

I hope it is not a video driver problem.

On Sun, 04 Jul 2021 15:42:38 -0400, Ar <Ar@127.0.0.1> wrote:

> I performed a internet in-line update of Mageia 7 to 8, first time I
> tried this method of update. After a few hours it said the update
> installation was successful, and have had zero issues, other than
> needing to change the odd thing here and there due to updated way of
> doing certain things.
>
> As per the errata, I disabled 3D ergo compiz-fusion before the update.
>
> However, with the system working again, I re-enabled 3D, and when
> logging in to a user account, the desktop is black, nothing is loaded as
> my "loading" tune does not play, the cube works - but apart from the top
> and bottom, is completely black. Only the mouse is visible.
>
> I've had a go at lots of old solutions, but nothing seems to solve the
> problem.
>
> If I executed in the non 3D enabled desktop "compiz --replace &" in a
> console session, I get some of the Compiz 3D and also by magic emerald
> also works. Unfortunately I can't use emerald without Compiz, and ALL
> the window decorations in Plasma look terrible.
>
> None of these issues were in Mageia7 before the upgrade. Any
> suggestions? KWin isn't doing any 3D as Compiz takes over at login.

First thing to do is create a new user and see if the problem is present for
that user (Mageia bug) or not (user config file(s) need changing).

Regards, Dave Hodgins

--
Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
email replies.

On 04/07/2021 20:52, David W. Hodgins wrote:

>> None of these issues were in Mageia7 before the upgrade. Any
>> suggestions? KWin isn't doing any 3D as Compiz takes over at login.
>
> First thing to do is create a new user and see if the problem is
> present for that user (Mageia bug) or not (user config file(s) need
> changing).

I forgot to do that..

On 04/07/2021 21:00, Bit Twister wrote:

> First thing to verify is if the problem is with user account or system.
>
> I use a test account, junk. Makes it easy to wipe and login again
> when testing anything.
>
> If you log into junk and have no problem, then you know the problem is
> in the user account.
>
> If junk is broke you know is is a system wide problem.
>
> I hope it is not a video driver problem.

I set up a brand new user, and that has a completely black screen also,
with mouse visible. As there would be no settings set uo for Compiz, no
"box" displays. Click anywhere you like, nothing happens.

Doesn't seem to matter if nvidia or nueveo (or however you spell it) driver.

On Sun, 4 Jul 2021 23:50:30 +0100, Ar wrote:
> On 04/07/2021 21:00, Bit Twister wrote:
>

>> I hope it is not a video driver problem.
>
> I set up a brand new user, and that has a completely black screen also,
> with mouse visible. As there would be no settings set uo for Compiz, no
> "box" displays. Click anywhere you like, nothing happens.

I understand.

> Doesn't seem to matter if nvidia or nueveo (or however you spell it) driver.

Or Display Manger: gdm, lightdm, sddm, xdm, ...

I did/do not know where the setting is because I do not use any of the
whizzbang stuff.

I thought the 3D stuff was in
mcc Hardware-->Configure graphics-->Configure 3D Desktop effects

On Sun, 04 Jul 2021 18:50:30 -0400, Ar <Ar@127.0.0.1> wrote:

> On 04/07/2021 21:00, Bit Twister wrote:
>
>> First thing to verify is if the problem is with user account or system.
>>
>> I use a test account, junk. Makes it easy to wipe and login again
>> when testing anything.
>>
>> If you log into junk and have no problem, then you know the problem is
>> in the user account.
>>
>> If junk is broke you know is is a system wide problem.
>>
>> I hope it is not a video driver problem.
>
> I set up a brand new user, and that has a completely black screen also,
> with mouse visible. As there would be no settings set uo for Compiz, no
> "box" displays. Click anywhere you like, nothing happens.
>
> Doesn't seem to matter if nvidia or nueveo (or however you spell it) driver.

Try booting to run level 3 - edit boot parameters at login and append " 3"
without the quotes.

Then run "XDG_SESSION_TYPE=wayland dbus-run-session startplasmacompositor" to
see if plasma is working under wayland. If that fails try again with
"startx startkde" to run it under x11.

Do either of them work?

Regards, Dave Hodgins

--
Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
email replies.

On 7/4/21 3:50 PM, Ar wrote:

> I set up a brand new user, and that has a completely black screen also,
> with mouse visible. As there would be no settings set uo for Compiz, no
> "box" displays. Click anywhere you like, nothing happens.
>
> Doesn't seem to matter if nvidia or nueveo (or however you spell it)
> driver.

Happened to me with a Radeon. I don't know enough about X or compiz to
manually diagnose it, and it was a fresh install, so I just did a
reinstall.

On 05/07/2021 02:06, red floyd wrote:

>> Doesn't seem to matter if nvidia or nueveo (or however you spell it)
>> driver.
>
> Happened to me with a Radeon.   I don't know enough about X or compiz to
> manually diagnose it, and it was a fresh install, so I just did a
> reinstall.

I had this problem once before, but that was before Compiz got forked to
Beryl and Beryl "just worked" - and consumed vastly less system
resources than Compiz (something that the rejoining was never carried in
to the Compiz code).

Because it was so long ago, I go rid of most the Compiz print outs I did
because it never screwed up again. I won't be re-installing an entire OS
just to get Compiz to work, other issues I've had have been fixed, so
the system is running nice.

On 05/07/2021 01:31, David W. Hodgins wrote:

Before starting, I enabled 3D before rebooting to do the init3 commands
you suggested.

> Then run "XDG_SESSION_TYPE=wayland dbus-run-session
> startplasmacompositor" to see if plasma is working under wayland.

Not running, the exact error displayed is..

dbus-run-session: failed to exec 'startplasmacompositor': No such file
or directory

> If that fails try again with "startx startkde" to run it under x11.

With this, KDE starts with a black screen with mouse on screen, but if I
use the mouse I can get the Compiz cube to rotate etc. No applications load.

BTW, if I have 3D disabled and run the latter command, I'm just dumped
in to a normal non 3D KDE desktop.

On Mon, 05 Jul 2021 04:44:17 -0400, Ar <Ar@127.0.0.1> wrote:

> On 05/07/2021 01:31, David W. Hodgins wrote:
>
> Before starting, I enabled 3D before rebooting to do the init3 commands
> you suggested.
>
>> Then run "XDG_SESSION_TYPE=wayland dbus-run-session
>> startplasmacompositor" to see if plasma is working under wayland.
>
> Not running, the exact error displayed is..
>
> dbus-run-session: failed to exec 'startplasmacompositor': No such file
> or directory

Sorry, that was the command for Mageia 7. In Mageia 8 kde changed it to
XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland
which requires the package plasma-workspace-wayland to be installed first.

>> If that fails try again with "startx startkde" to run it under x11.
>
> With this, KDE starts with a black screen with mouse on screen, but if I
> use the mouse I can get the Compiz cube to rotate etc. No applications load.
>
>
> BTW, if I have 3D disabled and run the latter command, I'm just dumped
> in to a normal non 3D KDE desktop.

Might end up having to accept that 3d kde doesn't work on that hardware anymore.

Regards, Dave Hodgins

--
Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
email replies.

On 5/7/21 5:46 pm, Ar wrote:

> Because it was so long ago, I go rid of most the Compiz print outs I did
> because it never screwed up again. I won't be re-installing an entire OS
> just to get Compiz to work, other issues I've had have been fixed, so
> the system is running nice.

Is Compiz and the Desktop effects in "System Settings" an independent
setup.
I use Desktop effects because I had a bad time with Compiz many releases
ago. and steered clear ever since
--
faeychild
Running plasmashell 5.20.4 on 5.10.41-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso

On 05/07/2021 19:17, David W. Hodgins wrote:

> Sorry, that was the command for Mageia 7. In Mageia 8 kde changed it to
> XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland
> which requires the package plasma-workspace-wayland to be installed first.

Still didn't work, the errors that came up are (shortened for UID pid etc):

dbus-daemon: Activating service name='org.freedesktop.systemd1'
requested by ':1.0'.... comm="startplasma-wayland")

dbus-daemon: Activated service 'org.freedesktop.systemd1' failed:
process org.freedesktop.system1 exited with status 1

dbus-daemon: Activating service name='org.freedesktop.systemd1'
requested by ':1.0'.... comm="startplasma-wayland")

dbus-daemon: Activated service 'org.freedesktop.systemd1' failed:
process org.freedesktop.system1 exited with status 1

No backend specified through command line argument, trying auto resolution

And the session hangs, needing a hard reboot, no keyboard response at all.

>> BTW, if I have 3D disabled and run the latter command, I'm just dumped
>> in to a normal non 3D KDE desktop.
>
> Might end up having to accept that 3d kde doesn't work on that hardware
> anymore.

It should work, it's not an old graphics card. I can get the the Compiz
cube etc, just not the desktop on it.

On Tue, 06 Jul 2021 14:15:38 -0400, Ar <Ar@127.0.0.1> wrote:
> It should work, it's not an old graphics card. I can get the the Compiz
> cube etc, just not the desktop on it.

Please open a bug report for it so the right questions can be asked and hopefully,
a solution found. I never use any desktop effects myself (except when specifically
testing updates that effect them). With the way I'm used to using my systems, I
view them as just a waste of resources that slow things down.

Regards, Dave Hodgins

--
Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
email replies.

On 7/6/21 12:10 PM, David W. Hodgins wrote:
> On Tue, 06 Jul 2021 14:15:38 -0400, Ar <Ar@127.0.0.1> wrote:
>> It should work, it's not an old graphics card. I can get the the Compiz
>> cube etc, just not the desktop on it.
>
> Please open a bug report for it so the right questions can be asked and
> hopefully,
> a solution found. I never use any desktop effects myself (except when
> specifically
> testing updates that effect them). With the way I'm used to using my
> systems, I
> view them as just a waste of resources that slow things down.
>
> Regards, Dave Hodgins
>

Yes just go to KDE System Settings and shut off those
special effects. Like Dave H. I regard too many special effects
as a waste of resources.

bliss- - “Nearly any fool can use a Linux computer. Many do.” After all
here I am...

--
bliss dash SF 4 ever at dslextreme dot com

On 06/07/2021 19:15, Ar wrote:

I deleted the nVidia driver, and xorg.conf, hoping to rely on nouveau
driver. The nouveau driver hung the pc and needed a hard reboot. So I
init3 and re-installed the nVidia driver to carry on.

I found some very old notes I made with my Mageia 3 install, I long
forgot about the "compositing-wm" file.

/etc/sysconfig/compositing-wm

I changed compiz-fusion entry to kwin. I re-enabled 3D and rebooted. The
desktop loaded as normal. I noticed there is now a "Start Compiz" icon
in the KDE menus, so I clicked that, and Compiz and Emerald started
flawlessly, running as it did in Mageia 7.

If I change the entry back to "compiz-fusion" log out and log back in
again, I get the black box and no loaded applications.

So I performed another test, I put all the Compiz settings to default,
meaning nothing is selected. Performing the "Start Compiz" starts it,
but it does nothing as the defaults mean it does nothing.

Putting "compiz-fusion" in to compositing-wm and restarting, I am still
back to a black box with a mouse. So not working.

As a temporary work around, I am running 3D with the "Start Compiz"
icon, and compositing-wm set to kwin (but Compiz/Emerald running).

On 06/07/2021 20:10, David W. Hodgins wrote:

> Please open a bug report for it so the right questions can be asked and
> hopefully, a solution found.

Will look to do so. It's a weird problem.

> I never use any desktop effects myself (except when specifically
> testing updates that effect them). With the way I'm used to using my
> systems, I view them as just a waste of resources that slow things down.

I'm not bothered about the less than 1% of CPU the 3D is using.

On 06/07/2021 21:49, Bobbie Sellers wrote:

>     Yes just go to KDE System Settings and shut off those
> special effects.  Like Dave H. I regard too many special effects
> as a waste of resources.
>
> bliss- - “Nearly any fool can use a Linux computer. Many do.” After all
> here I am...

That's OK, but on my system (when the 3D was working properly in Mageia
7), the 3D uses less than 1% of CPU most the time it doesn't even
register in ksysguard (and certainly barely shows up any percentage in
"top").

On Tue, 06 Jul 2021 17:29:50 -0400, Ar <Ar@127.0.0.1> wrote:
> I'm not bothered about the less than 1% of CPU the 3D is using.

Same here. For me it's just that when I click on a running application in the
taskbar, I want it shown as quickly as the hardware will allow. I see no benefit
in adding a delay to rotate a qube or explode a window.

I disable all desktop effects and set everything that allows setting a delay to
use the shortest delay it allows.

Regards, Dave Hodgins

--
Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
email replies.