Description of problem: upgraded mdv to mageia alpha 2 see attachment Reproducible: Steps to Reproduce:
Blocks: (none) => 56
Created attachment 139 [details] weird shutdown menu artifact bug
Same here, using Mageia1 Alpha2 in VMPlayer.
CC: (none) => isis2000
Blocks: 56 => (none)
Same here, using Mageia 1 Beta 2 KDE Live CD.
CC: (none) => piscestong
Same experience, using Mageia 1 RC i586 version, On my KDE logout screen, the entire background is disturbed.
CC: (none) => g.sprikHardware: x86_64 => All
Looks like the KDE4 desktop effects are enabled. (Desktop effects in a virtual machine is like asking for trouble, my 0.002 â¬).
Summary: shutdown menu has odd artifacts above => shutdown menu has odd artifacts above when the KDE4 desktop effects are enabledSource RPM: (none) => kdebase4-workspace
Assignee: bugsquad => balcaen.john
(In reply to comment #5) > (Desktop effects in a virtual machine is like asking for trouble, my 0.002 â¬). I can add to my comment that I do NOT use a virtual machine. This bug is not only visible in VM-environments.
(In reply to comment #6) > (In reply to comment #5) > > > (Desktop effects in a virtual machine is like asking for trouble, my 0.002 â¬). > > I can add to my comment that I do NOT use a virtual machine. > This bug is not only visible in VM-environments. Agreed.
IIRC the reporter, AL13N, got the bug running in virtualbox. Also isadora said he's running under vmware. So if you're not running in a virtual machine you should say so in this particular sort of report.... Please post the output of: lspcidrake -v | grep -Ei "card|display"
(In reply to comment #8) > IIRC the reporter, AL13N, got the bug running in virtualbox. Also isadora said > he's running under vmware. So if you're not running in a virtual machine you > should say so in this particular sort of report.... ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sorry for my poor English, but does that mean we should file another bug report? > > Please post the output of: > lspcidrake -v | grep -Ei "card|display" I'll try to get and post its output.
(In reply to comment #9) > (In reply to comment #8) > > IIRC the reporter, AL13N, got the bug running in virtualbox. Also isadora said > > he's running under vmware. So if you're not running in a virtual machine you > > should say so in this particular sort of report.... > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > Sorry for my poor English, but does that mean we should file another bug > report? > > > > > Please post the output of: > > lspcidrake -v | grep -Ei "card|display" > > I'll try to get and post its output. I've filed a new bug report (Bug 1403 - https://bugs.mageia.org/show_bug.cgi?id=1403), for I'm not running in a virtual machine and my KDE4 desktop effects are disabled. And there I've provided more screenshots and details.
@Jin-tong: excellent, thanks.
CC: (none) => thierry.vignaudComponent: Installer => RPM PackagesAssignee: balcaen.john => bugsquad
setting back assignee after tv changed it accidentally when changing component
Well desktop effect are disabled by default, thoses effects depends of the virtualisation tools used (& not really kwin/kdebase4-workspace ). Also is it still valid ?
CC: (none) => balcaen.johnAssignee: balcaen.john => bugsquad
Keywords: (none) => NEEDINFO
afaik the alpha isn't released yet, so i can't test...
CC: thierry.vignaud => (none)
Can anyb(In reply to comment #13) > Well desktop effect are disabled by default, thoses effects depends of the > virtualisation tools used (& not really kwin/kdebase4-workspace ). > Also is it still valid ? (In reply to comment #14) > afaik the alpha isn't released yet, so i can't test... Now it is, please test
CC: (none) => marja11
couldn't reproduce in cauldron, i even tried setting desktop effects to on, it reported that it wasn't able to turn on 3 of them, but it even worked quite well, even though a bit slow... perhaps this was mdv upgrade related... i'd like to test with physical hardware, but it seems there's a diff bugreport for that...
(In reply to comment #16) > couldn't reproduce in cauldron, i even tried setting desktop effects to on, it > reported that it wasn't able to turn on 3 of them, but it even worked quite > well, even though a bit slow... > > perhaps this was mdv upgrade related... > > i'd like to test with physical hardware, but it seems there's a diff bugreport > for that... Yep, and you already commented in it: https://bugs.mageia.org/show_bug.cgi?id=1403#c19 @ Gerald @ Isadora Can you reproduce the issue in Mga2alpha?
@Gerald @Isadora Could you please reply to the previous question? If you won't reply within two weeks from now, I will have to close this bug as OLD. Thank you.
Problem solved right here. No pointer however to a reason why.
(In reply to comment #19) > Problem solved right here. > No pointer however to a reason why. Thanks, Isadora :) Must have been an update that fixed it. @ Gerald Closing as fixed, but feel free to reopen if needed
Status: NEW => RESOLVEDResolution: (none) => FIXED
(In reply to comment #20) > (In reply to comment #19) > > Problem solved right here. > > No pointer however to a reason why. > > Thanks, Isadora :) > > Must have been an update that fixed it. > > @ Gerald > > Closing as fixed, but feel free to reopen if needed Because of bug 4124 I am not able to test in Mageia 2 (Alpha3). Moreover, I don't use a virtual machine. Closing this bugreport is o.k. for me.