Libreoffice UI shrunk to unreadable size

Support Graphics & Display
1

I just installed another bunch of upgrades, but before I removed a file of which I thought it’s not necessary: xwaylandvideobridge (from AUR). After that, LibreOffice showed extreme strange behaviour: the interface shrunk to an almost unreadable size. I’m not sure if that’s related to xwaylandvideobridge, but if not, what else could cause this? Anyway, after the upgrade I started Manjaro again in the hope the update would fix it, but no, LO still shows a much smaller UI than before.

Hence I tried to install xwaylandvideobridge using yay, which tells me that a key needs to be imported. Well, I allow it and get immediately the response: Reception from keyserver failed: no keyserver available.

I tried manual installation of the required key, no luck. Then I tried to install the key as root, and it worked fine. However, the installation of xwaylandvideobridge still doesn’t work, because the key is in root’s wallet and not in mine. Internet connection is fine, and I haven’t changed anything except for removing that software before the upgrade.

I know this is more or less off topic, but I feel it’s still related because screen resolution etc. seem all be messed up to a certain extent (particularly with LO) since I installed the second monitor. If you wish, I can open a new topic for this.

2

I moved this to a new topic, feel free to improve upon the title.

I’ve posted it under AUR for now, as you mentioned xwaylandvideobridge, however I suspect it may be a red herring. :man_shrugging:

I’ve never even heard of xwaylandvideobridge, and my LibreOffice is fine. You shouldn’t need it.

Do you mean the UI elements are smaller, if so then it may be scaling related.

Can you describe it better or post a screenshot so we can see what you’re talking about.

3 Likes
3

I also fail to see how the removal of xwaylandvideobridge could be causing the issue. It was designed for sharing Wayland screens with X11 applications that are running under Xwayland. In early 2023, there were still a lot of commonly-used X11 applications that had not yet been made Wayland-compatible, so the xwaylandvideobridge was meant to be a stopgap measure to deal with the issue until developers got on board with Wayland (which rapidly accelerated after Fedora announced they would make Wayland the default session for Plasma).

I remember posting about the xwaylandvideobridge well over 2 years ago:

The original announcement of xwaylandvideobridge:

According to System / XWayland Video Bridge · GitLab:

This project is archived. Its data is read-only.

So it is no longer under active development, with the last update being 7 months ago.

My view is that @dmt’s suggestion about Plasma’s scaling being the cause of the issue should be looked at first.

I do also wonder if the issue could be related to the version of libreoffice installed on @DrMartinus system: libreoffice-fresh or libreoffice-still? However, my knowledge of libreoffice is non-existent as I don’t use any office applications, so that may have nothing to do with the issue.

Also possible as a cause, having casually monitored their other thread relating to monitors over the past few days, is that some KDE/Plasma packages might still be missing from their system. @DrMartinus had to manually install kscreen, which should have already been on their system as it is included in the plasma package group:

Output of pacman -Qg plasma 
pacman -Qg plasma 
plasma aurorae
plasma bluedevil
plasma breeze
plasma breeze-gtk
plasma kactivitymanagerd
plasma kde-cli-tools
plasma kde-gtk-config
plasma kdecoration
plasma kdeplasma-addons
plasma kglobalacceld
plasma kinfocenter
plasma kmenuedit
plasma kpipewire
plasma kscreen
plasma kscreenlocker
plasma ksshaskpass
plasma ksystemstats
plasma kwallet-pam
plasma kwayland
plasma kwin
plasma kwrited
plasma layer-shell-qt
plasma libkscreen
plasma libksysguard
plasma libplasma
plasma milou
plasma ocean-sound-theme
plasma plasma-activities
plasma plasma-activities-stats
plasma plasma-browser-integration
plasma plasma-desktop
plasma plasma-integration
plasma plasma-nm
plasma plasma-pa
plasma plasma-systemmonitor
plasma plasma-thunderbolt
plasma plasma-welcome
plasma plasma-workspace
plasma plasma-workspace-wallpapers
plasma plasma5support
plasma polkit-kde-agent
plasma powerdevil
plasma print-manager
plasma qqc2-breeze-style
plasma sddm-kcm
plasma spectacle
plasma systemsettings
plasma xdg-desktop-portal-kde

So, maybe some other packages from the plasma group are still missing.

Try reinstalling the complete plasma group:

sudo pacman -Syu plasma

Reboot and see if that fixes the issue. If it doesn’t, there could be other package groups associated with Plasma still missing some of their packages. My guess for the most likely would be KDE’s Frameworks (the kf6 group), so it wouldn’t do any harm to ensure that everything from that group is installed too:

sudo pacman -Syu kf6
2 Likes
9

Sorry for not replying earlier. I did that, I missed to count how many packages were newly installed, it seemed that most were just reinstalled. Anyway, after a restart LO still looks the same. It’s LO-still.

From kf6 it seems that 4 packages are missing:

kdav, kimageformats, kpeople, kplotting.

I will restart now and see how it is then.

I made a screenshot, but that doesn’t really help, because it can give the impression that everything is fine. There is no way to display in a screenshot the actual size of images etc. The thing is, when I open a document, if it’s set to 100% magnification (i.e. original), I can’t read it. I have to magnify it to 200%, then it becomes readable. Earlier, 100% was ok, though sometimes I chose to enhance magnification to 120%, which is then for me very comfortable.

Now, imagine the menu (Files, Edit etc.) are all written in 100% ratio, the icons in relation to this are written in maybe 25%. Every dialogbox is equally reduced to 25% (while the size of the box, i.e. length and height, is like the one it used to be when everything was displayed at 100%, so there is plenty of empty room). Well, I restart my machine and let you know if the full installation of kf6 changed anything.

10

On the chance that the issue might be with LibreOffice itself, try installing libreoffice-fresh to see it the issue persists.

sudo pacman -S libreoffice-fresh

You will be prompted to remove libreoffice-still in the process; choose y.

This will serve to rule out LibreOffice as the culprit and can be reverted at any time in the same fashion.

Regards.

11

After the restart, LO still behaves exactly as before, the installation of plasma and kf6 hasn’t had any effect. It strikes me that every other software works just fine, only LO does not. Very strange… (oh, BTW, OpenOffice is fine, too…).

Regarding xwaylandvideobridge, I have no intention to reinstall it. It just was the only piece of software that I consciously removed before I restarted the PC and found out the strange behaviour of LO.

12

I tried that, no change. I replaced libreoffice-still and libreoffice-fresh with each other, both behave the same way.

13

It was a longshot, but ruled out, it is.

My guess is that it’s a general scaling issue. If you go to;

System Settings → Input & Output → Display & Monitor → Display Configuration;

How is your scaling configured? As an example, with my settings (following) I have no such issue:

  • Scale: 100%
  • Legacy applications (X11): :white_check_mark: Apply scaling themselves

Note that I’m using Wayland, AMD graphics, 1080p display. :eyes:

As always, your system information is requested.

inxi -zv8
3 Likes
18

Ok, that was a good suggestion. The point was the “Apply scaling themselves”. That was set to “Apply scaling by the system” (or similar). After changing that and restarting LO, LO appears as it should.

It’s strange that those things change on their own, probably because of some upgrade. Well, I consider it solved for the time being.

Thanks a lot for your immediate help!

I just noticed that the virtual desktop switcher has suffered. It doesn’t show any longer the windows that are active on the various virtual desktops. I believe it displayed them until I made that change, but I am not sure. Well, I have to do other things right now, and this is another topic. If it doesn’t resolve itself with the next restart, I’ll start a new thread…

Hm, I just restarted the PC, because LO started behaving erratically (documents weren’t sized properly, there were remnants of another display of the document left in spaces that actually shouldn’t display anything, etc.), I thought that would solve these new issues. After restart, the old problem is back, I checked the system settings, they weren’t changed.

Anyway, I try to work with that now, because the work is more important than getting the display right at the moment.

1 Like
19

So strange as to render the possibility virtually impossible; but it’s good to know the issue is resolved.

It is customary – in fact, almost always required – that you mark a post that helped the most as the solution to a given topic; this allows others with the same (or similar) issue to easily find the resolution, if relevant.

You have been reminded of this a few times in other topics – please remember to tend to this as a courtesy for others, and to allow a topic to close automatically as a matter of course.

I have marked the solution post for you, in this instance.

No charge. :wink:

20

I apologize for not doing it right with the solution thing. I am still struggling with this forum software, and my memory isn’t working like that of a computer any more, I tend to forget things. Sorry!

3 Likes
21

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.

22

I know I had this issue already reported, but the discussion had been closed due to inactivity. I was busy for a longer period with other things, but now I need to work with LO and am often unable to do certain tasks, or it takes much longer, because of this issue.

In short and as a reminder: After installing a second monitor (which has a lower resolution than the main monitor), LO UI keeps the letter size according to the resolution of the secondary monitor, when accessed on the main monitor. This makes the UI almost unreadable, because the letters shrink enormously. This effects mainly the dialogs (like print, but also editing dialogs and all the kind) and the toolbars. Strangely, the menu (File, Edit…) is in normal size. Bit e.g. font names or template names in the drop down lists are almost unreadable. Documents are always being opened at 100% display size, which is extremely small and unreadable (to me), I need to enlarge the view to 200%.

The above described situation occurs always, independent of where LO is being started.

I could move the LO window to the secondary monitor, but that is ergonomically not advisable, because the secondary monitor is above the primary one, I couldn’t work on documents on that monitor not for more than approximately 2 minutes. The position of the monitors can not be changed.

I tried changing the scaling settings (scaling by application or scaling by system), this time nothing changes.

23

Your LO version is current.

You could try changing some environment variables:

$ SAL_USE_VCLPLUGIN=qt6
$ WAYLAND_DISPLAY=libreoffice

and restart the session.

24

I had a similar problem, and what worked for me was to set the SAL_USE_VCLPLUGIN in my /etc/profile.d/libreoffice-still.sh file (for you it might be called /etc/profile.d/libreoffice-fresh.sh) to use gtk3:

#
# https://wiki.documentfoundation.org/Development/Environment_variables
#

# to force a certain look'n feel

#export SAL_USE_VCLPLUGIN=gen
#export SAL_USE_VCLPLUGIN=kf6
#export SAL_USE_VCLPLUGIN=qt5
#export SAL_USE_VCLPLUGIN=qt6
export SAL_USE_VCLPLUGIN=gtk3
#export SAL_USE_VCLPLUGIN=gtk4

There is considerable discussion in this bug: 141578 – Libreoffice unusable with different scale factors used for different screens in multimonitor setup (on kf5/qt5/qt6 vcl + wayland)

25

If the variable setting works, I would rather use /etc/environment to make them being set already at boot time.

27

The correct procedure is to ask a Moderation staff member to re-open a closed topic when you have additional information to add.

Your threads have been merged for the sake of continuity and to maintain the general “one issue, one topic” rule.

Please provide your system information as described (below).

System Information

For the purposes of Support requests it’s better to ask your system directly for information. :eyes:

Output from the inxi command (with appropriate parameters) will generate information more useful for those who might wish to help.

Command output (or code) should be formatted according to forum guidelines. See How to Post Command Output as Preformatted Text :eyes:

Suggested inxi command (use either):
inxi -zv8 (short-form)
inxi --filter --verbosity=8 (long-form)
inxi man pages (manual)
If running `inxi` within a `chroot` environment
  • Add --color=0 to the long-form command, or…
  • Change the short-form command to inxi -zv8c0
Your privacy is respected

I’d be remiss if I didn’t remind you that we helped you solve this issue once before. Can you revisit those settings again?

1 Like
30

I mentioned already in my “reopening”-post, that this did not help. It worked once, and that was it. Why it worked this one time, I don’t know. After restarting the computer, it was back to downsizing everything, and changing the settings for Legacy applications didn’t end it, no matter what it was set to.

Regarding the reopening, I am sorry, I wasn’t aware of the option to ask a moderator. It may be a good idea to mention that in the closing message, I guess. The sentence “New replies are no longer allowed” gives the impression that there is no option to reopen the issue. I would of course have preferred to continue discussing this issue here.

Regarding the other info (inxi…), I’ll get that and post it in a few moments (I hope).

Here is the inxi-Information:

System:
  Kernel: 6.17.9-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.17-x86_64
    root=UUID=ec6cf098-6a61-40fd-aa92-49cc5fef7f26 rw quiet apparmor=1
    security=apparmor udev.log_priority=3
  Desktop: KDE Plasma v: 6.5.3 tk: Qt v: N/A info: frameworks v: 6.20.0
    wm: kwin_wayland tools: avail: swayidle,swaylock vt: 1 dm: SDDM
    Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: X470 GAMING PRO (MS-7B79) v: 1.0
    serial: <superuser required> uuid: <superuser required> Firmware: UEFI
    vendor: American Megatrends LLC. v: 1.L4 date: 07/17/2024
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 64 GiB available: 62.72 GiB used: 13.28 GiB (21.2%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 128 GiB slots: 4 modules: 4 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: Channel-A DIMM 0 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 16 GiB speed: 2400 MT/s volts: note: check curr: 1
    min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: Corsair
    part-no: CMK32GX4M2Z3600C18 serial: N/A
  Device-2: Channel-A DIMM 1 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 16 GiB speed: 2400 MT/s volts: note: check curr: 1
    min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: Corsair
    part-no: CMK32GX4M2Z3600C18 serial: N/A
  Device-3: Channel-B DIMM 0 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 16 GiB speed: 2400 MT/s volts: note: check curr: 1
    min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: Corsair
    part-no: CMK32GX4M2Z3600C18 serial: N/A
  Device-4: Channel-B DIMM 1 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 16 GiB speed: 2400 MT/s volts: note: check curr: 1
    min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: Corsair
    part-no: CMK32GX4M2Z3600C18 serial: N/A
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: AMD Ryzen 5 2600 bits: 64 type: MT MCP arch: Zen+ gen: 1+
    level: v3 note: check built: 2018-21 process: GF 12nm family: 0x17 (23)
    model-id: 8 stepping: 2 microcode: 0x800820D
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 6 threads: 12 tpc: 2
    smt: enabled cache: L1: 576 KiB desc: d-6x32 KiB; i-6x64 KiB L2: 3 MiB
    desc: 6x512 KiB L3: 16 MiB desc: 2x8 MiB
  Speed (MHz): avg: 3186 min/max: 1550/3400 boost: enabled scaling:
    driver: acpi-cpufreq governor: schedutil cores: 1: 3186 2: 3186 3: 3186
    4: 3186 5: 3186 6: 3186 7: 3186 8: 3186 9: 3186 10: 3186 11: 3186 12: 3186
    bogomips: 81603
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext clflush clflushopt clzero cmov cmp_legacy constant_tsc cpb
    cpuid cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid f16c
    flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb lahf_lm lbrv
    lm mca mce misalignsse mmx mmxext monitor movbe msr mtrr mwaitx
    nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae pat pausefilter
    pclmulqdq pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pni
    popcnt pse pse36 rapl rdrand rdseed rdtscp rep_good sep sev sev_es sha_ni
    skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 succor svm
    svm_lock syscall tce topoext tsc tsc_scale v_vmsave_vmload vgif
    vmcb_clean vme vmmcall wdt xgetbv1 xsave xsavec xsaveerptr xsaveopt
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: old_microcode status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT vulnerable
  Type: spec_rstack_overflow mitigation: Safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; STIBP:
    disabled; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX
    470/480/570/570X/580/580X/590] vendor: Sapphire driver: amdgpu v: kernel
    arch: GCN-4 code: Arctic Islands process: GF 14nm built: 2016-20 pcie:
    gen: 3 speed: 8 GT/s lanes: 16 ports: active: HDMI-A-1,HDMI-A-2
    empty: DP-1,DP-2,DVI-D-1 bus-ID: 27:00.0 chip-ID: 1002:67df class-ID: 0300
    temp: 51.0 C
  Device-2: Microdia USB 2.0 Camera driver: snd-usb-audio,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 5-4.1.2.3:11
    chip-ID: 0c45:636b class-ID: 0102
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
    alternate: fbdev,vesa dri: radeonsi gpu: amdgpu d-rect: 5760x3240
    display-ID: 0
  Monitor-1: HDMI-A-1 pos: top-right model: HP 24o serial: <filter>
    built: 2017 res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 92 gamma: 1.2
    chroma: red: x: 0.655 y: 0.333 green: x: 0.314 y: 0.620 blue: x: 0.149
    y: 0.063 white: x: 0.314 y: 0.329 size: 531x299mm (20.91x11.77")
    diag: 609mm (24") ratio: 16:9 modes: 1920x1080, 1680x1050, 1600x900,
    1280x1024, 1440x900, 1280x800, 1280x720, 1024x768, 800x600, 720x576,
    720x480, 640x480, 720x400
  Monitor-2: HDMI-A-2 pos: bottom-l model: Samsung LU28R55 serial: <filter>
    built: 2024 res: mode: 3840x2160 hz: 60 scale: 150% (1.5) to: 2560x1440
    dpi: 154 gamma: 1.2 chroma: red: x: 0.678 y: 0.314 green: x: 0.267
    y: 0.620 blue: x: 0.145 y: 0.059 white: x: 0.314 y: 0.329
    size: 632x360mm (24.88x14.17") diag: 727mm (28.6") ratio: 16:9
    modes: 3840x2160, 2560x1440, 1920x1200, 1920x1080, 1600x1200, 1680x1050,
    1600x900, 1280x1024, 1440x900, 1280x800, 1152x864, 1280x720, 1024x768,
    832x624, 800x600, 720x576, 720x480, 640x480, 720x400
  EDID-Warnings: 1: parse_edid: unhandled CEA mode 97 2: parse_edid:
    unhandled CEA mode 96 3: parse_edid: unhandled CEA mode 95
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
    wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.2.7-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 570 Series (radeonsi
    polaris10 ACO DRM 3.64 6.17.9-1-MANJARO) device-ID: 1002:67df
    memory: 7.81 GiB unified: no display-ID: :1.0
  API: Vulkan v: 1.4.328 layers: 1 device: 0 type: discrete-gpu name: AMD
    Radeon RX 570 Series (RADV POLARIS10) driver: mesa radv v: 25.2.7-arch1.1
    device-ID: 1002:67df surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: radeontop wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere HDMI Audio [Radeon RX
    470/480 / 570/580/590] vendor: Sapphire driver: snd_hda_intel v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s
    bus-ID: 27:00.1 chip-ID: 1002:aaf0 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio
    vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 bus-ID: 29:00.3 chip-ID: 1022:1457 class-ID: 0403
  Device-3: Microdia USB 2.0 Camera driver: snd-usb-audio,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 5-4.1.2.3:11
    chip-ID: 0c45:636b class-ID: 0102
  API: ALSA v: k6.17.9-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: jack_control
  Server-3: PipeWire v: 1.4.9 status: off with: pipewire-media-session
    status: active tools: pw-cat,pw-cli
  Server-4: PulseAudio v: 17.0-93-gbe2efb status: active with:
    1: pulseaudio-alsa type: plugin 2: pulseaudio-jack type: module
    tools: pacat,pactl
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: f000 bus-ID: 22:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp34s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Info: services: httpd,NetworkManager
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 11.48 TiB used: 4.08 TiB (35.6%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
    model: WD30EZRX-00SPEB0 size: 2.73 TiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
    fw-rev: 0A80 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital
    model: WD30EZRX-00D8PB0 size: 2.73 TiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
    fw-rev: 0A80 scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 840 Series
    size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 6B0Q scheme: MBR
  ID-4: /dev/sdd maj-min: 8:48 vendor: Seagate model: ST6000DM003-2CY186
    size: 5.46 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 5425 serial: <filter> fw-rev: 0001 scheme: GPT
  ID-5: /dev/sde maj-min: 8:64 vendor: Samsung model: SSD 860 EVO 500GB
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
  Optical-1: /dev/sr0 vendor: Optiarc model: DVD RW AD-7191S rev: 1.00
    dev-links: cdrom
  Features: speed: 94 multisession: yes audio: yes dvd: yes
    rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition:
  ID-1: / raw-size: 152.09 GiB size: 152.09 GiB (100.00%)
    used: 115.42 GiB (75.9%) fs: f2fs dev: /dev/sde4 maj-min: 8:68
    label: Dateisystem f2fs auf der Partition
    \xe2\x80\x9e/dev/sde4\xe2\x80\x9c erstellen
    uuid: ec6cf098-6a61-40fd-aa92-49cc5fef7f26
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%)
    used: 1.8 MiB (0.7%) fs: vfat dev: /dev/sde2 maj-min: 8:66 label: ESP
    uuid: E7F1-3B24
  ID-3: /data raw-size: 994.85 GiB size: 978.17 GiB (98.32%)
    used: 16.26 GiB (1.7%) fs: ext4 dev: /dev/sdd2 maj-min: 8:50 label: network
    uuid: 36b02e3e-a948-43de-b32a-343ffe2e57d6
  ID-4: /home raw-size: 4.49 TiB size: 4.45 TiB (99.19%)
    used: 2.42 TiB (54.4%) fs: ext4 dev: /dev/sdd1 maj-min: 8:49 label: Home
    uuid: 576c77a0-e6e4-4e3e-9bdc-fdf47c0a0cf2
  ID-5: /home/<filter>/Bilder raw-size: 2.73 TiB size: 2.69 TiB (98.42%)
    used: 1.53 TiB (57.1%) fs: ext4 dev: /dev/sdb1 maj-min: 8:17 label: Fotos
    uuid: 9eec6b6b-033e-4ad2-979d-df407491ec3f
Swap:
  Kernel: swappiness: 180 (default 60) cache-pressure: 100 (default)
    zswap: yes compressor: zstd max-pool: 20%
  ID-1: swap-1 type: zram size: 12 GiB used: 238.5 MiB (1.9%) priority: 100
    comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 dev: /dev/zram0
Unmounted:
  ID-1: /dev/sda1 maj-min: 8:1 size: 1.85 TiB fs: ext4 label: home-DRM
    uuid: 83b6baa8-b6bf-40d8-939f-a8215c548bd1
  ID-2: /dev/sda2 maj-min: 8:2 size: 586.69 GiB fs: ext4 label: Musik
    uuid: 4406a5c8-ff25-4485-b189-fa9ea3b6f649
  ID-3: /dev/sda3 maj-min: 8:3 size: 6.26 GiB fs: swap label: Swap
    uuid: a452f55a-acf3-4379-a4e6-f44665d53b4b
  ID-4: /dev/sda4 maj-min: 8:4 size: 77.33 GiB fs: ext4 label: Testsys1
    uuid: 4d4d7d9c-6456-4713-9ead-66ed221a2af4
  ID-5: /dev/sda5 maj-min: 8:5 size: 85.85 GiB fs: ext4 label: Testsys2
    uuid: f3f24a40-14e3-48e3-970d-23326f2ecc73
  ID-6: /dev/sda6 maj-min: 8:6 size: 81.91 GiB fs: ext4 label: Testsys3
    uuid: b119b06a-d9ad-4ae8-baf3-86090a56f007
  ID-7: /dev/sdc1 maj-min: 8:33 size: 37.41 GiB fs: ext4 label: N/A
    uuid: 41944751-3661-44e7-918a-ea6d5e515311
  ID-8: /dev/sdc2 maj-min: 8:34 size: 73.82 GiB fs: ext4 label: Manjaro
    uuid: c5303561-8dbd-4c72-87a3-4789eacda253
  ID-9: /dev/sdc3 maj-min: 8:35 size: 570 MiB fs: vfat label: ESP
    uuid: 64A4-C845
  ID-10: /dev/sde1 maj-min: 8:65 size: 151.37 GiB fs: f2fs label: N/A
    uuid: 0d0931b9-c791-49b1-aef6-3ea0d65766c8
  ID-11: /dev/sde3 maj-min: 8:67 size: 162.05 GiB fs: f2fs label: System3
    uuid: ec3d7801-185e-4251-b653-3c291f4f31e6
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 14 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-13:6 info: -- USB keyboard type: keyboard,HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0
    speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
    chip-ID: 260d:0021 class-ID: 0300
  Hub-2: 2-0:1 info: super-speed hub ports: 8 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-4: 4-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-5: 5-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 5-1:2 info: Brother Industries MFC-J6920DW
    type: printer,mass storage driver: usb-storage,usblp interfaces: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 2mA
    chip-ID: 04f9:02f5 class-ID: 0806 serial: <filter>
  Device-2: 5-2:3 info: Frys MEC0003 type: HID driver: hid-generic,usbhid
    interfaces: 1 rev: 1.1 speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0
    power: 100mA chip-ID: 0001:0000 class-ID: 0300
  Device-3: 5-3:4 info: PERIMICE-520 type: mouse,keyboard
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 260d:1019 class-ID: 0301
  Hub-6: 5-4:5 info: Realtek RTS5411 Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 0bda:5411
    class-ID: 0900
  Hub-7: 5-4.1:6 info: Realtek RTS5411 Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 0bda:5411
    class-ID: 0900
  Hub-8: 5-4.1.2:7 info: Huasheng USB2.0 HUB ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 214b:7250 class-ID: 0900
  Device-1: 5-4.1.2.2:10 info: Genesys Logic microSD Card Reader
    type: mass storage driver: usb-storage interfaces: 1 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 98mA
    chip-ID: 05e3:0751 class-ID: 0806
  Device-2: 5-4.1.2.3:11 info: Microdia USB 2.0 Camera type: video,audio
    driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 500mA
    chip-ID: 0c45:636b class-ID: 0102
  Hub-9: 6-0:1 info: super-speed hub ports: 4 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-10: 6-4:2 info: Realtek Hub ports: 4 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 0bda:0411
    class-ID: 0900
  Hub-11: 6-4.1:3 info: Realtek Hub ports: 4 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 0bda:0411
    class-ID: 0900
  Device-1: 6-4.3:4 info: SanDisk Ultra Fit type: mass storage
    driver: usb-storage interfaces: 1 rev: 3.0 speed: 5 Gb/s (596.0 MiB/s)
    lanes: 1 mode: 3.2 gen-1x1 power: 896mA chip-ID: 0781:5583 class-ID: 0806
    serial: <filter>
Sensors:
  System Temperatures: cpu: 43.5 C mobo: N/A gpu: amdgpu temp: 51.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 990
Repos:
  Packages: 3257 pm: pacman pkgs: 3204 libs: 588 tools: octopi,pamac,yay
    pm: flatpak pkgs: 53
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://manjaro.kurdy.org/testing/$repo/$arch
    2: https://mirror.23m.com/manjaro/testing/$repo/$arch
    3: https://mirror.alpix.eu/manjaro/testing/$repo/$arch
    4: https://ftp.gwdg.de/pub/linux/manjaro/testing/$repo/$arch
Processes:
  CPU top: 5 of 470
  1: cpu: 116% command: gs pid: 26580 mem: 26.9 MiB (0.0%)
  2: cpu: 100% command: ps pid: 26588 mem: 4.45 MiB (0.0%)
  3: cpu: 15.0% command: thumbnail.so started-by: kioworker pid: 3744
    mem: 507.7 MiB (0.7%)
  4: cpu: 10.4% command: firefox pid: 6475 mem: 817.4 MiB (1.2%)
  5: cpu: 9.8% command: baloo_file_extractor pid: 4344 mem: 71.8 MiB (0.1%)
  Memory top: 5 of 470
  1: mem: 1031.0 MiB (1.6%) command: kwin_wayland pid: 1331 cpu: 4.0%
  2: mem: 899.2 MiB (1.4%) command: thunderbird pid: 3559 cpu: 3.8%
  3: mem: 886.9 MiB (1.3%) command: firefox pid: 6874 cpu: 3.5%
  4: mem: 817.4 MiB (1.2%) command: firefox pid: 6475 cpu: 10.4%
  5: mem: 617.5 MiB (0.9%) command: soffice.bin pid: 7614 cpu: 0.4%
Info:
  Processes: 470 Power: uptime: 16m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 25.07 GiB services: org_kde_powerdevil,upowerd
    Init: systemd v: 258 default: graphical tool: systemctl
  Compilers: clang: 21.1.6 gcc: 15.2.1 Shell: Bash v: 5.3.3
    running-in: konsole inxi: 3.3.40
2 Likes
31

Have you tried changing the mentioned environment variables? If you ask for help and get advice at least a feedback would be welcome.

1 Like
32

I agree. I believe the word is written somewhere, but an automated addition of some kind when a topic is closed might be a good idea, even if it’s only a link to the information concerned.

Whether that’s actually possible with the Discourse software (on which the Manjaro forum is based), I can’t say.

You’re special :star: :slight_smile:

As you created the original post of the topic you have that privilege, whereas others don’t. If the need is legitimate, a Moderation staff member may re-open your topic, at their discretion.

Regards.

1 Like