thanks for your message… yeah, i’ve installed Manjaro Gnome edition.
Thanks for the scripts, I will check, maybe I willl have a fresh install via the net version.
But maybe I will test some gnome os like ubuntu gnome, korora gnome or apricityos gnome before manjaro and to see their advancement…
Dropped to a console and ran the suggested commands. KDE icons were too small which I fixed as the others did with iconSize=2. The panel/system tray is set to autohide which causes flickering. Sometimes it will hang there for a while. A minor annoyance and I’m not sure what causes it.
Fixed the issue with the flickering by messing with the Compositor under Display settings. Changing things like OpenGL and full redraws didn’t help. Moving the slider to instantaneous for animations appears to have fixed the flickering.
since I’m really busy currently I tried to answer as much questions posted by you. I’m sorry if I didn’t catched all. I’m sure others of our community might help out.
I still hope for most of you this update was smooth.
Seems the widget has some issue. Please sort it up-side-down to see the US mirrors.[quote=“Madh, post:43, topic:11416”]
left computer while it was installing updates. When I back the monitor wasn’t detecting video signal, so I rebooted manually. Now Manjaro freezes in boot splash screen.
Hmm, some went wrong. Since I had no time yesterday to do a proper announcement the troubleshoot hints are now added. Do you have still access to a TTY or do you stuck during bootup? Is it a real installation or inside of VirtualBox? If needed use chroot to fix your installation.
Why so harsh? The given rc2 install ISOs will install also Manjaro 16.10 for you. I only tagged it as second release candidate as I might have missed something. So please test the given ISO and prove me otherwise
You’re correct. This function might not work properly with the new gtk3 version of xfce4-terminal. However it might get fixed soon.
Sorry to hear that. Every major Gnome Update might create issues. Please try to use a different theme. Adwaita or Arc might work just fine for you.
Hi my friend. I’m sorry to hear that this kernel might not work for that user. Seems to be a regression. Does he also have another kernel installed than linux44 series?
That is an AUR package …
Seems Santa came a little earlier to you. Joke aside: please search for the flicker problem. Seems to be a common issue with Gnome 3.22.
There is a workaround for that. Check the troubleshoots for it in first post:
Use nmcli to set 802-11-wireless.mac-address-randomization to never on a per connection basis or set
in /etc/NetworkManager/NetworkManager.conf to disable the feature completely.
Which user do you use for makepkg? It can’t be root. Use your normal user account for it. The wiki is your friend
Sorry to hear that. systemd had a security issue and we had to fix it. Gnome is one of the desktop environments which lost the X-Session. That is why we recommend to use a TTY session for the systemd update. All can be fixed. However this issue won’t happen with Manjaro 16.10, as this version of Manjaro includes the proper patched systemd already. Also the RC1 release was released, which included that package also. More than writing about it we can’t do.
Seems you try to install some drivers for this kernel from source code. The missing package is called linux48-headers.
Your issues might be different and depending on packages you have installed. Please download our current KDE release and try it as live-session on your PC. When everything works as expected some local setting on your machine might cause the issue. To rule that out, please test the default settings given by that install media first.
Does cable work? Which driver do you use for your wlan card? The textoutput of mhwd -lh might help here. Also hwinfo --network might give some clue.
I’ve been just using the community Vmware Tools. I’ve run my Manjaro VM using only the open-vmtools, xf86-video-vmware, and xf86-imput-vmmouse (in the vm, all from manjaro repositories)
Since inception, and not limited to manjaro, several linux virtual machine have to have their window size actually be manually changed to trigger the video drivers into allowing auto resize so that you can maximize them. (Other wise you can maximize them but the vm doesn’t seem to notice and continues at the small little square in a huge expanse of unused screen.
Unset full screen (reverting to windowed mode, drag it bigger or smaller and it realizes it should resize the VM. Then click full screen again and all is good.
What ever you do, don’t go down the road of compiling VMWare’s own tools because its not necessary, and unless you are using a mainstream distro it won’t work anyway. Makes a big mess).
Seems you have an old hardware there. The Wlan-Hardware is - well - not the best
Here some tips for it anyway:
iwlegacy is the wireless driver for Intel’s 4965 wireless chip. The firmware is included in the linux-firmware package. udev/systemd should load the driver automatically, otherwise load iwl4965 manually with sudo modprobe iwl4965. If you have problems connecting to networks in general or your link quality is very poor, try to disable 802.11n:
options iwl4965 11n_disable=1
You may need to reboot your system so the config takes affect.
I have an issue and I’m hoping one of you can help.
I am wanting to try the Manjaro XFCE RC2 16.10 and I want to install to my hard drive. But I have another Linux distro on that drive controlling the boot process and I want to keep it that way.
When I install Manjaro and select “do not install a bootloader”, I can get to the other distros grub screen and after running os-prober and updating grub in the other distro, manjaro shows in the boot selection screen. But when I click on Manajaro it won’t boot.
The error message basically says that Manjaro is not configured properly to boot.
What can I do to resolve that?
Thanks for your help!
Manjaro uses a special approach for Intel CPUs. Either you uninstall the package intel-ucode or you modify your bootloader config. For Arch and Manjaro we have grubpatched to handle this matter properly. Currently used only for Arch-based distros.
Check the given line in your grub.cfg and search for initrd. Modify it as needed to by adding the right kernel image. Check if /boot is needed on your end: