If you want return to vanilla gnome remove
manjaro-gnome-maia-theme and create a new user and relogin with new user . If You want only the vanilla gnome screen only remove
manjaro-gnome-maia-theme and reboot…
If you want return to vanilla gnome remove
Good question because the images are in svg format so the extension have the control i think…
i have a boot missed with the kernel 184.108.40.206 , with a lock and BFQ , reboot is ok
Maybe I do misunderstand the concept of manjaro-gnome-settings.
Until last update we had preinstalled GTK 3, Shell themes and Extensions with this package. Please correct me if i’m wrong.
We also had the ability to chose the Default GNOME Shell theme (I do not mean the GTK3 themes).
Now if we chose the Default Shell theme we get the Adapta version, without any way to chose the GNOME shell theme.
Was that really intended that way?
No the last manjaro-gnome-settings install only Adapta but not gdm theme
Only the first version force the installation ( my wrong ) but not after my rebuild
Thank’s but just removing
manjaro-gnome-maia-theme hasn’t reset the gnome screen…
Have you rebooted after removing the pkg ? My remove script via pacman hook do the same thing as @pux do via command…
Of course… I have reinstalled it again and then removing it again and same thing.
What is the content of
ls /usr/share/gnome-shell extensions modes theme gnome-shell-theme.gresource perf-background.xml gnome-shell-theme.gresource.old search-providers
Version of manjaro-gnome-maia-theme ? The .old file is still present so the hook/script not apply fine …
Reinstall gnome-shell package…
Damn it … thank you i found my error … wait my post to try again
Pushed in all branch new
manjaro-gnome-maia-theme now all work fine … after remove check if the size of gresource file is less than 500kb … if is more than 1mb is wrong ( old script revision save again the gresource of adapta theme ) reinstall the gnome-shell pkg and remove manually the .old file if present . The new pkg contain a script revision so it work fine with a “vanilla” condition i.e. : if the gresource file and .old file have the same size before install manjaro.gnome-maia-theme re-install the gnome-shell pkg …
I’m sorry for this but during unstable and testing stage no one report the issue
Thank you very much! File was more than 1mb. Reinstalling
gnome-shell has restored the default gdm theme and made Adwaita the default entry in Tweaks.
PS: Count on me to test the Gnome version in testing .
Same issue like @jsbach but “elevator” doesn’t help, on two machines.
Is there a Update coming to solve this in the next days?
Booth machines works with intel, one I5 and one I7 6th gen.
If I start the Virtualbox both machines on Kernel 4.14 gaves me allso an error … TLC-deadline .
Kernel 4.9 runs fine otherwise I get Plasma crashes sometimes since I got the latest update (4.9, 4.13, 4.14.) the details of the chrash says " no details" !
I SSD (for / + /swap and /home) and HDD for all others on both machines
I have no issue booting 4.13 kernel with bfq-sq
System: Host: X201EP Kernel: 4.13.4-1-MANJARO x86_64 bits: 64 gcc: 7.2.0 Desktop: i3 4.14-non-git
Distro: Manjaro Linux
Machine: Device: laptop System: ASUSTeK product: X201EP v: 1.0 serial: N/A
Mobo: ASUSTeK model: X201EP v: 1.0 serial: N/A
UEFI: American Megatrends v: X201EP.210 date: 07/30/2014
Battery BAT0: charge: 11.6 Wh 45.9% condition: 25.3/38.0 Wh (66%) model: ASUSTek X202-51 status: Discharging
CPU: Dual core Intel Celeron 847 (-MCP-) arch: Sandy Bridge rev.7 cache: 2048 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 4391
clock speeds: max: 1100 MHz 1: 1097 MHz 2: 1097 MHz
Graphics: Card: Intel 2nd Generation Core Processor Family Integrated Graphics Controller bus-ID: 00:02.0
Display Server: x11 (X.Org 1.19.3 ) driver: intel Resolution: email@example.com
OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile version: 3.3 Mesa 17.2.1 Direct Render: Yes
Audio: Card Intel 7 Series/C216 Family High Definition Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0
Sound: Advanced Linux Sound Architecture v: k4.13.4-1-MANJARO
Network: Card-1: Qualcomm Atheros AR9485 Wireless Network Adapter driver: ath9k bus-ID: 02:00.0
IF: wlp2s0 state: up mac:
Card-2: Qualcomm Atheros AR8162 Fast Ethernet port: e000 bus-ID: 03:00.0
IF: N/A state: N/A speed: N/A duplex: N/A mac: N/A
Drives: HDD Total Size: 143.5GB (14.8% used)
ID-1: /dev/sda model: ADATA_SP900 size: 128.0GB
ID-2: USB /dev/sdb model: Card_Reader size: 15.5GB
Partition: ID-1: / size: 13G used: 6.6G (56%) fs: ext4 dev: /dev/sda5
ID-2: /home size: 4.8G used: 329M (8%) fs: ext4 dev: /dev/sda3
ID-3: swap-1 size: 2.10GB used: 0.00GB (0%) fs: swap dev: /dev/sda7
Sensors: System Temperatures: cpu: 52.0C mobo: 52.0C
Fan Speeds (in rpm): cpu: 3300
Info: Processes: 133 Uptime: 7:53 Memory: 1068.7/3839.5MB Init: systemd Gcc sys: N/A
Client: Shell (bash 4.4.121) inxi: 2.3.40
cat /proc/cmdline: BOOT_IMAGE=/boot/vmlinuz-4.13-x86_64 root=/dev/sda5 rw elevator=bfq-sq enable_mtrr_cleanup mtrr_spare_reg_nr=1 i915.modeset=1 acpi=force acpi_enforce_resources=lax ipv6.disable=1 rd.udev.log-priority=3 pcie_aspm=force quiet cat /sys/block/sda/queue/scheduler: noop deadline cfq [bfq-sq]
Hi! I’m the next affected by that outstanding BFQ scheduler related bug introduced in 4.13.4 kernel. I guess the kernel must be already removed from the Manjaro repo after so massive sad stories
Same problem as last upgrade, worked around same way, as below.
(29/29) checking package integrity [###################] 100%
error: pacman-mirrors: signature from “Frede Hundewadt firstname.lastname@example.org” is invalid
:: File /var/cache/pacman/pkg/pacman-mirrors-4.2.3-2-any.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.
[root@russ-laptop russell]# pacman -Syu --ignore pacman-mirrors