I was asking if you were able to post a screenshot or image of the log but it would probably be a lot easier for you to just backup any important files and reinstall paying careful attention to any of the docs that are posted and perhaps re read the docs before just to help ensure a smooth process. I still am not quite sure what you mean by switching screens with it being a dual boot. Do you have dual monitors on your laptop?
No, I only have one screen. What i mean by switching screens is going from something like the terminal to firefox, or vise versa, or even when firefox opens and closes a dialog box.
Thanks for clarifying I understand a lot better about your setup description but I’ve never had an issue with it hanging up or glitching like that while the service isnt stopping or switching or starting so I’m not sure at all what it might be. Can you provide the information for your graphics drivers being used and the VGA and display services/drivers that your system is loading and having the issues while doing so? I think that may at least narrow it down. Also double check your dependencies and configs for them to ensure they are all squared away on that end.
Also I apologize I thought I had addressed this in one of my replies but I now see that I did not but I believe using apt upgrade instead of dist-upgrade is problematic. Do you have issues reloading your repo sources or any apt-key errors?
The problem is both before the update (right after the installation of the latest distribution) and after the update ( Apt upgrade & apt dist-upgrade)
I think the problem is in the driver, but the official installer of AMD drivers can not recognize the distr.
dpkg -i *amd64.deb in the folder with the driver also do not solve the problem.
and as I said at the time of glitch i have
“(EE) client bug : timer event28 debounce short: offset negative (-0ms)”
in /var/log/Xorg.0.log - I think it’s important
and get out these errors during the update
W: Possible missing firmware /lib/firmware/amdgpu/vega12_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_sdma1.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_sdma.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_sdma1.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_sdma.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma1.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_uvd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_uvd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_uvd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_vce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_vce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_vce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_smc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_smc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_smc.bin for module amdgpu
; no errors in sources or apt-key
Anybody? this OS is obviously more often used on laptops, many people will simply stop using such bugs without solving it, because not everyone who comes across the same bug reaches the forum and complains, it simply installs another OS
I’m not going to lie, that’s kinda what I did. I’m not running the 64bit kali KDE release
I’m sorry for the very late response, but I did kinda give up, and am now running kali.
I really apologize I was away for work and couldn’t get on here. I run a dedicated gpu (also unfortunately not amd) so I have not run into that issue (also a desktop) maybe @palinuro knows a little more? I did see some updates today that involved bumblebee I believe from what I was reading while it updated. Will check back later tonight hopefully with more info!
Unfortunately I can’t get my Lenovo resurrected and I don’t have any other laptops to use right now so hopefully palinuro will have some insight!
I’m having the exact same problems as described. Has anyone found a way to figure out the problem? I assume it has something do to with the internal graphics, but I wouldn’t know where to start to fix the issue. Thanks
Is there any solution? Ive got same problem… Im using amd card also
I apologize i thought it had posted but i suppose not, the drivers work for nvidia i thonk still sometimes iffy on AMD the main cause is probably to do ith lack of a package(s) or held ones that you dont need or want or acpi settings, needing nomodeset com,and at grub boot etc
and you point the real problem of this distro… there is no help for all problems users meet… they lose a lot of users like that… they make ton of useless post about update and upgrade, and dev posts without dev but they dont solve problems like that… this distro will die if they dont put a lot of effort in that before want upgrade and upgrade!!! Kali and backbox etc laugh about this forum…
Well to be fair thats sometimes (like the graphics drivers) uncontrollable if its not supported by what it is based off of (debian hasnt supported it yet, thus the instances in that code arent defined so it cant be executed and expected to know what to do) it definitely takes reading the docs not just on here (which is an issue that is being addressed but unfortunately it takes time as well) and sometimes on debian.org and the package/modules website or whathaveyou. Being a test distro rather than a “safe guaranteed everything has support 100% and works” sometimes the work just needs needs to be done because its never been designed to run on that specific environment or in collaboration with a different object etc i think its great that more emphasis on keeping true to the constantly updated promise parrot is based on. Most of the time though when things are “broken” its more that it required the user to use certain parameters or have certain prerequisites that was in the documentation that users miss or dont read entirely.
I have same problem too,but i fixed.
At the System>Preferences>Hardware>Displays
Change the Resolution to lower i used 1280x720 before that 1366x768 and apply.
The problem now are fixed.Your screen resolution now have A Little blurry but not too blurry but its ok.I hope the developer will fixed it soon at the next Updates for user have a full resolution,Thanks.
Hey all, I found a solution to this.
Go into your MATE Tweak settings, go to Windows, and in the Window Manager box change it from Macro (Adaptive compositer) to Macro (Compton GPU compositer)
It worked perfectly for me!
From Display Serttings Change Screen Resolution to your actual Screen Size & Change Refresh Rate hope that works 
Have not seen the replies until now but that did work. Thanks!
Solved this as far as for being unable to install parrot 4.6 because of the flickering screen.
- boot into your usb stick with parrot 4.6 on it
- First screen should be displayed normal. The display bug starts after chosing an install method (at least here).
- in this menu you can edit the screen resolution by pushing the TAB button on your keyboard. Now you will see a command line at the bottom.
- Here it says for example xrdhrtjc VGA=788 jhfghlkgumjfnt VESA and so on.
5 I edited the 788 to 1600 and pushed enter - It tells me that this resolution is unknown and I get many possible resolutions shown on my laptop now.
- I chose “o” which here is the resolution for 1920x1080x32 VESA
DONE! Now parrot displays the installation process without any graphic problems.
What you really need to know is that you can change settings by pushing the TAB button while in the first screen after booting parrot from usb! The screen which tells you “live”, “encrypted”, “install”, and so on. Also you can edit settings for each entry! So let’s say you want do do a “standard install”: you will need to select “standard install” but DO NOT confirm it! First push the TAB button and change the commandline that shows up in order to change display settings! Now you can go on with the installation without getting stucked because of the display glitches that make an installation impossible. This goes for each entry in the parrot boot menu, ok? If you want do do “GTK Install”, then you need to change settings for this special entry.