I am also running into the issue of java environments.
My starting point was that i had everything “jre11” and “jdk11” installed, after some suggestions i now have only “jdk11-openjdk” installed, but the upgrade pacman -Syu and pacman -Syu jdk-openjdk will still try to install “jre” packages, is this correct? Because from what i am reading about the change it should only use “jdk” now if jdk is needed and should actually conflicts, but they do not.
Package (130) Old Version New Version Net Change Download Size
extra/jdk11-openjdk 11.0.21.u9-2 11.0.21.u9-3 0.01 MiB 307.56 MiB
extra/jre11-openjdk 11.0.21.u9-3 0.53 MiB 0.19 MiB
extra/jre11-openjdk-headless 11.0.21.u9-3 159.98 MiB 36.02 MiB
My issue with the appindicator icons has escalated. It’s now the entire gnome-shell collapsing on me when trying to restart my nextcloud desktop client to display the proper icons.
Looking at the journalctl output, the following appears:
Also, when this crash happens, my gnome shell starts back with all the extensions disabled.
And, another gnome-shell crash when simply wanting to save a file in Librewolf, which is not even a Qt application:
journalctl logs:
Nov 13 12:38:36 karolyi-desktop gnome-shell[14119]: JS ERROR: TypeError: this._prepareStartupAnimation() is undefined
_loadBackground/signalId</id<@resource:///org/gnome/shell/ui/layout.js:693:26
@resource:///org/gnome/shell/ui/init.js:21:20
Nov 13 12:38:36 karolyi-desktop gnome-shell[14119]: Object .Gjs_workspace-indicator_gnome-shell-extensions_gcampax_github_com_extension_WindowPreview (0x55bfe74f29b0), has been already disposed — impossible to access it. Thi
s might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x55bfe1288f80 ==
#0 7fff286cd690 b resource:///org/gnome/shell/ui/layout.js:992 (1fa0a1ed7fb0 @ 32)
#1 55bfe1353310 i file:///usr/share/gnome-shell/extensions/workspace-indicator@gnome-shell-extensions.gcampax.github.com/extension.js:77 (307122a54ec0 @ 42)
#2 55bfe1353290 i file:///usr/share/gnome-shell/extensions/workspace-indicator@gnome-shell-extensions.gcampax.github.com/extension.js:66 (307122a54e20 @ 12)
#3 55bfe1353208 i resource:///org/gnome/gjs/modules/esm/_timers.js:72 (1fa0a1e70510 @ 77)
#4 55bfe1353178 i resource:///org/gnome/shell/ui/init.js:21 (1fa0a1e70ba0 @ 48)
Nov 13 12:38:36 karolyi-desktop gnome-shell[14119]: Object .Gjs_workspace-indicator_gnome-shell-extensions_gcampax_github_com_extension_WindowPreview (0x55bfe74f29b0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x55bfe1288f80 ==
#0 7fff286cd690 b resource:///org/gnome/shell/ui/layout.js:993 (1fa0a1ed7fb0 @ 231)
#1 55bfe1353310 i file:///usr/share/gnome-shell/extensions/workspace-indicator@gnome-shell-extensions.gcampax.github.com/extension.js:77 (307122a54ec0 @ 42)
#2 55bfe1353290 i file:///usr/share/gnome-shell/extensions/workspace-indicator@gnome-shell-extensions.gcampax.github.com/extension.js:66 (307122a54e20 @ 12)
#3 55bfe1353208 i resource:///org/gnome/gjs/modules/esm/_timers.js:72 (1fa0a1e70510 @ 77)
#4 55bfe1353178 i resource:///org/gnome/shell/ui/init.js:21 (1fa0a1e70ba0 @ 48)
Nov 13 12:38:36 karolyi-desktop gnome-shell[14119]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1e00014 specified for 0x1e00016.
There is a problem with VLC. I use VLC player to watch IPTV channels. I don’t know if it’s related to the update, but everything worked before. I show the logs:
$ sudo pacman -Syu jdk-openjdk
:: Synchronising package databases...
core is up to date
extra is up to date
multilib is up to date
:: Starting full system upgrade...
:: Replace kdsoap with extra/kdsoap-qt5? [Y/n]
:: Replace kuserfeedback with extra/kuserfeedback5? [Y/n]
:: Replace libqaccessibilityclient with extra/libqaccessibilityclient-qt5? [Y/n]
resolving dependencies...
looking for conflicting packages...
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: jdk-openjdk and jre-openjdk are in conflict
$ sudo pacman -Sy jdk-openjdk
:: Synchronising package databases...
core is up to date
extra is up to date
multilib is up to date
resolving dependencies...
looking for conflicting packages...
:: jdk-openjdk and jre-openjdk are in conflict. Remove jre-openjdk? [y/N] y
:: jdk-openjdk and jre-openjdk-headless are in conflict. Remove jre-openjdk-headless? [y/N] y
Packages (3) jre-openjdk-21.u35-3 [removal] jre-openjdk-headless-21.u35-3 [removal]
jdk-openjdk-21.u35-8
Total Download Size: 457.46 MiB
Total Installed Size: 1136.47 MiB
Net Upgrade Size: 634.32 MiB
:: Proceed with installation? [Y/n] Y
I sort of was hoping the Manjaro team would downgrade these 2 files with this upgrade, looks like they didn’t as the issue persists. I will use the downgrade tool.
After the last update (or possibly the one on November 6, not 100% sure) I have experienced problems with my Wacom Intuos Pros. I have two different computers (an HP laptop/i7 and a Lenovo desktop/Ryzen), both running Manjaro/Gnome/X11 and having identical Wacom Intuos Pro pen tablets. On both systems any use of the Wacom tablets seems to freeze the application I’m trying to interact with (in particular, both Inkscape and Xournal++). These apps work fine when using the mouse or trackpad as input device.
Any ideas on what could have gone wrong?
I get a conflicting error message when I try to update pamac.
Error: unresolvable package conflicts detected
Error: Failed to prepare transaction:
conflicting dependencies:
jdk-openjdk and jre-openjdk are in conflict.
Both are installed by default.
What do need to do?
$ manly pacman -R -dd jre-openjdk-headless
pacman - package manager utility
================================
-R, --remove
Remove package(s) from the system. Groups can also be specified to
be removed, in which case every package in that group will be
removed. Files belonging to the specified package will be deleted,
and the database will be updated. Most configuration files will be
saved with a .pacsave extension unless the --nosave option is used.
See Remove Options below.
TRANSACTION OPTIONS (APPLY TO -S, -R AND -U)
-d, --nodeps
Skips dependency version checks. Package names are still checked.
Normally, pacman will always check a package’s dependency fields to
ensure that all dependencies are installed and there are no package
conflicts in the system. Specify this option twice to skip all
dependency checks.
TRANSACTION OPTIONS (APPLY TO -S,-R AND -U)
-d, --nodeps
Skips dependency version checks. Package names are still checked.
Normally, pacman will always check a package’s dependency fields to
ensure that all dependencies are installed and there are no package
conflicts in the system. **Specify this option twice to skip all**
**dependency checks.**
-d, --deps
Restrict or filter output to packages installed as dependencies.
This option can be combined with -t for listing real orphans -
packages that were installed as dependencies but are no longer
required by any installed package.
Experienced the jdk-openjdk issue myself, resolved by running pacman -S jdk-openjdk then pacman -Syu normally. Hope future updates can avoid being as rushed to avoid situations like this, otherwise everything’s running normally after restart so the update itself is good.
It’s a Nvidia issue and cuda-12.3.0-4includes a workaround, but Manjaro Stable branch has cuda-12.3.0-1. In the meantime you could do just do export NVCC_PREPEND_FLAGS='-ccbin /opt/cuda/bin' yourself.
cuda has been updated from 12.2.2-1 to 12.3.0-4. Unfortunately, cuda 12.2 is not compatible with gcc 13. cuda 12.3 even more so. I can’t compile anything with nvcc at the moment.
/usr/include/bits/floatn-common.h(251): error: invalid combination of type specifiers
typedef double _Float64;
^
/usr/include/bits/floatn-common.h(268): error: invalid combination of type specifiers
typedef double _Float32x;
^
Since the Nvidia drivers remained on version 535 anyway, I downgraded cuda to version 12.2. Now it works again.
I would only update cuda to 12.3 when nvidia 545 is in the stable branch.
i tried cuda-12.3.0-4 with that workaround, but it do not work. I compile mpv-build-git with ffmpeg/cuda support and the compilation stops with the same error with cuda-12.3.0-4.