No problems here on xfce with 4.18.12
Great job Manjaro Team!!!
No problems here on xfce with 4.18.12
PLease, I search for you
thank you my friend … but unfortunately i ended with error in grub ‘grub_key_is_interrupted’ … any solution
you are not alone
Thank you very much for your great work. All went fine on this machine and the packard bell lm98
(cannot set in markdown —weird–)
System: Kernel: 4.18.12-1-MANJARO x86_64 bits: 64 Desktop: KDE Plasma 5.13.5
Distro: Manjaro Linux
CPU: Quad Core: Intel Core i5-7500 type: MCP speed: 800 MHz min/max: 800/3800 MHz
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X]
driver: amdgpu v: kernel
Display: x11 server: X.Org 1.20.1 driver: amdgpu,ati unloaded: modesetting
resolution: 1920x1080~60Hz, 1920x1080~60Hz
OpenGL: renderer: AMD Radeon RX 480 Graphics (POLARIS10 DRM 3.26.0 4.18.12-1-MANJARO LLVM 7.0.0)
v: 4.5 Mesa 18.2.2
Drives: Local Storage: total: 954.81 GiB used: 83.18 GiB (8.7%)
Info: Processes: 211 Uptime: 3m Memory: 15.63 GiB used: 1.30 GiB (8.3%) Shell: bash inxi: 3.0.26
Try steps suggested in reply 18 . if this does not work read original post. For me both worked.
Had a couple of keys fail to sign. Easily fixed by running:
sudo rm -rf /etc/pacman.d/gnupg sudo pacman-key --init sudo pacman-key --populate archlinux manjaro
Since the update GNOME top bar missing when using magnifier. Therefore unable to see time, notifications, extensions on the top bar, and unable to shut down PC without terminal.
Can’t use Super key either to access activities, with or without magnification on
EDIT: just noticed dialog boxes also not fully viable when magnifier is on.
I had the same message and used pamac. I have rebooted and everything seems ok. Wait and see I suppose.
I don’t think this is how rolling distros work. Also, it would cause an exponential increase in package maintenance headaches. Downgrading packages on a case-by-case basis because of a bug also means each downgraded package has to be tested again in the future by the Manjaro team (with a particular bug in mind) when another update is pushed upstream. Since pretty much every package has a bug of some severity, doing this as policy would not be possible.
The only times I’ve seen it happen is driver packages that result in system breaking behavior.
Is currently not compatible with Gnome 3.30. However there is a version that will work for now
wget -c "https://github.com/andyholmes/gnome-shell-extension-gsconnect/files/2377746/gsconnect.andyholmes.github.io.zip" unzip -o gsconnect.andyholmes.github.io.zip -d ~/.email@example.com/
logout, login. (This only works if GSConnect was installed via browser, NOT via pacman/pamac))
‘Transaction cannot be prepared’ - error, but does not seem to affect anything.
Gnome 3.30 messed up several extensions like TOP Icons Plus, No Title Bar, and Global Menu. First 2 can be fixed following the recommendations from their gnome extensions page, the last and most important one I could not fix . My custom theme got a bit screwed in Nautilus. So far everything else seems to be fine. I think Gnome 3.30 is the main culprit.
This is a known issue (which is promptly closed by the dev as it only happens in Arch and Manjaro).
You can also have a look at the arch linux forum thread which is linked inside the issue for more information. tldr:
The best way for me as I see it - using CLI when root is needed.
Everything went smooth!
Kernel: linux 414 & linux49.
I also got the “Transaction Not Prepared” notice but all seems to be working properly so far after I closed out the message window and rebooted. My headphone output stopped working but I think it is a hardware issue and not an OS problem as it’s a 9-and-a-half year old Lenovo laptop and was having audio issues just before the update.
Update on 12 Machines and 1 VB without Problems.
I has a problem with dnsmasq. This problem appeared after the upgrade.
$ dnsmasq -k --enable-dbus --user=dnsmasq --pid-file dnsmasq: failed to create listening socket for 127.0.0.1: Permission denied $ sudo dnsmasq -k --enable-dbus --user=dnsmasq --pid-file  10029 segmentation fault sudo dnsmasq -k --enable-dbus --user=dnsmasq --pid-file
Oct 08 17:29:52 - dnsmasq: failed to create listening socket for 127.0.0.1: Permission denied Oct 08 17:29:52 - dnsmasq: FAILED to start up ... Oct 08 17:31:45 - dnsmasq: started, version 2.79 cachesize 1000 Oct 08 17:31:45 - dnsmasq: compile time options: IPv6 GNU-getopt DBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify Oct 08 17:31:45 - dnsmasq: DBus support enabled: connected to system bus Oct 08 17:31:45 - dnsmasq-dhcp: IPv6 router advertisement enabled Oct 08 17:31:45 - dnsmasq: using local addresses only for domain 0.0.0.0 Oct 08 17:31:45 - audit: ANOM_ABEND auid=1000 uid=991 gid=991 ses=3 pid=10020 comm="dnsmasq" exe="/usr/bin/dnsmasq" sig=11 res=1 Oct 08 17:31:45 - kernel: dnsmasq: segfault at 0 ip 000055a564a62f9a sp 00007ffeeeec4c00 error 4 in dnsmasq[55a564a47000+45000] Oct 08 17:31:45 - kernel: Code: 01 00 00 48 8d 0d 62 9d 02 00 48 89 4c 24 08 f6 42 05 20 0f 85 f7 01 00 00 a8 08 0f 84 1f 02 00 00 49 8b 46 58 ba 05 00 00 00 <80> 38 00 0f 84 8d 02 00 00 48 8d 35 d6 00 03 00 31 ff ff 15 16 be Oct 08 17:31:45 - kernel: audit: type=1701 audit(1539009105.789:171): auid=1000 uid=991 gid=991 ses=3 pid=10020 comm="dnsmasq" exe="/usr/bin/dnsmasq" sig=11 res=1
Any thoughts ?
I notice that pamac this time attempts to start a full system upgrade for a second time after the system finishes upgrading. Since no transactions are prepared for this second full system upgrade, it fails in error. I suspect this is either a pamac bug, or a bug in the upgrade process. I presume it is safe to ignore.
After the update, everytime I launch an application everything freezes for a couple of seconds before the app is launched.