Not sure if this is just me or if others are experiencing this but my discord version still has not been updated from 0.0.44-1 to 0.0.45-1. I was wondering what the process is for updating one of the packages and would have thought that when it was updated on arch that it would have also been updated for the Manjaro Official Repositories. If anybody knows of the process and if there is any way to help in that process I’d be interested in learning. Thanks!
Btrfs is not comparable with other filesystems. You should not go over 80-90% full with btrfs, or you will regret it.
You can find good Information about Btrfs in the wiki
1 Like
0.0.45-1 is on unstable branch. It takes longer for new Arch packages to get to stable branch because they go through unstable and testing first. That’s the whole point of stable.
1 Like
It turns out I missed the update a couple days ago. I pushed it to testing & stable a couple of hours ago.
Normally that is the case. However, with Discord the application will not work if it detects there’s an update. Apparently upstream doesn’t care. 
4 Likes
Manjaro has no official support for AUR, same as Arch, and is suitable only for users who understand they are fully responsible for their actions
This forum does have an AUR section to seek help from other users, but cannot help with all of the 90,000+ AUR packages
You can always manually update it by using the “downgrade” package (unironically).
$ downgrade discord
It will give you a list of versions to chose from (Arch repo, not manjaro), including the lastest version.
Do keep in mind this is a “hack” and kind of and “advanced users only” thing.
This will NOT update package dependencies and can cause a “partial upgrade” situation where packages stop being compatible with each other and fail to work.
With that warning out of the way, for discord, this usually causes no issues
(and since old versions of discord always fail to open anyway, you dont lose anything really).
1 Like
Linux 6.6 seems that resume from suspend don’t work well.
On WorkStation (ThinkStation P720), when resuming, it completely froze in the TTY screen state and could not return to X.
Journal did’t have a log about resume.
Mar 14 16:30:58 pelargonium systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Mar 14 16:43:11 pelargonium systemd-logind[1194]: The system will suspend now!
Mar 14 16:43:11 pelargonium NetworkManager[1188]: <info> [1710402191.0797] manager: sleep: sleep requested (sleeping: no enabled>
Mar 14 16:43:11 pelargonium NetworkManager[1188]: <info> [1710402191.0800] manager: NetworkManager state is now ASLEEP
Mar 14 16:43:11 pelargonium ModemManager[1265]: <msg> [sleep-monitor-systemd] system is about to suspend
Mar 14 16:43:11 pelargonium systemd[1]: Reached target Sleep.
Mar 14 16:43:11 pelargonium systemd[1]: Starting System Suspend...
Mar 14 16:43:11 pelargonium systemd-sleep[33431]: Performing sleep operation 'suspend'...
Mar 14 16:43:11 pelargonium kernel: PM: suspend entry (deep)
Mar 14 16:43:11 pelargonium kernel: Filesystems sync: 0.038 seconds
This is end of log.
On Laptop (Dynabook RZ), it freezes with the lock screen. It is possible to move to the console and it took 10 minutes to restart LightDM.
It was also draining the battery in an unusual way.
Mar 14 21:06:55 solaruka-rz systemd[1]: Starting System Suspend...
Mar 14 21:06:55 solaruka-rz wpa_supplicant[1045]: wlo1: CTRL-EVENT-DSCP-POLICY clear_all
Mar 14 21:06:55 solaruka-rz systemd-sleep[513078]: Performing sleep operation 'suspend'...
Mar 14 21:06:55 solaruka-rz kernel: PM: suspend entry (s2idle)
Mar 14 21:06:55 solaruka-rz kernel: Filesystems sync: 0.017 seconds
Mar 15 09:51:03 solaruka-rz kernel: Freezing user space processes
Mar 15 09:51:03 solaruka-rz kernel: Freezing user space processes completed (elapsed 0.015 seconds)
Mar 15 09:51:03 solaruka-rz kernel: OOM killer disabled.
Mar 15 09:51:03 solaruka-rz kernel: Freezing remaining freezable tasks
Mar 15 09:51:03 solaruka-rz kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Mar 15 09:51:03 solaruka-rz kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 15 09:51:03 solaruka-rz kernel: e1000e: EEE TX LPI TIMER: 00000011
Mar 15 09:51:03 solaruka-rz kernel: ACPI: EC: interrupt blocked
Mar 15 09:51:03 solaruka-rz kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC._Q01.CHRG], AE_NOT_FOU>
Mar 15 09:51:03 solaruka-rz kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC._Q01 due to previous error (AE_NOT_FOUND) (>
Mar 15 09:51:03 solaruka-rz kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC._Q04 due to previous error (AE_NOT_FOUND) (>
Mar 15 09:51:03 solaruka-rz kernel: ACPI: EC: interrupt unblocked
Mar 15 09:51:03 solaruka-rz kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
...
These problems were reproduced after rebooting and trying again.
FZF history CTRL-R breaks terminal display.
tilix,wezterm+fzf-0.46.1-1
Conclusion of my environment::
tilix
profile-compatible
Ambiguous-width characters >> narrow
not use wide. 
wezterm
~/.config/wezterm/wezterm.lua
treat_east_asian_ambiguous_width_as_wide=true,
-- HACK true has a problem with fzf ctrl-r, same with tilix
I ended up downgrading. 0.44. official - extra.
fzf-0.46.1-1-x86_64.pkg.tar.zst to fzf-0.44.1-1-x86_64.pkg.tar.zst
–
From a resident who lives in a multi-byte, wide-character country. Being Japanese is sometimes inconvenient. lol)
1 Like
If an update fails due to lack of space do not reboot. The final stage of update process must complete successfully to update mkinitcpio and GRUB boot options
I would usually use pamac clean to free up some more space. But for a 9GiB update probably better to use maclean - a small script to automate safe cleaning functions to free up maximum possible space for update
This is simpler than using sudo manjaro-chroot -a and cleaning/updating via CLI
1 Like
Then only choice is to use free nouveau
No, it’s only one possible choice; he could optionally obtain a newer and supported graphics card. A Radeon RX 560/570/580/590 may still be compatible with his system, for example.
(excuse my pedanticism)
2 Likes
After installing this update, I have problem using webcam in firefox. When I turn on webcam, I see following error in a pup-op:
XML Parsing Error: no root element found
Location: chrome://browser/content/webrtcIndicator.xhtml
Line Number 1, Column 1:
It doesn’t allow me to close it unless I close webcam.
Other browsers don’t have this problem.
Restart didn’t fix the problem.
Update:
I fixed this problem by some searching. This problem is reported here too. You should check following steps:
- First off check if this problem exists in safe mode or not. This is the safest way which doesn’t result in lost of data.
- If problem exists in safe mode, you should check a new profile and see if a new profile fix the problem?
- If having a new profile doesn’t fix your problem, you are left with one option and it is a clean reinstall of Firefox.
I tried the first option using this link and fortunately, there was no problem in safe mode.
Then I came back to normal mode but I noticed that the problem is fixed automatically by just trying safe mode.
There is a strange internet icon in the tray bar.
And if I move anything on my left or centre desktop in the right bottom corner, the vertical scrollbar shows. But this doesn’t work on my right desktop (I have three monitors):
It seems wifi is broken after hibernation on linux67 for at least 2 updates now. Supposedly auth keeps just timing out. Linux66 is fine
Using Framework 13 AMD with mediatek adapter.
Left click on the down arrow, left click on the settings icon. Go to Entries and for Networks select Always hidden if you don’t want to see it there in your bar.
You either have widgets (if so, which ones?) on that desktop or icons linked on it. Try to move them upwards.
It could fix it if you right-click on that desktop > Configure Desktop and Wallpaper and choose Desktop instead of Folder View. However that might just move those/widgets & icons to another screen. Maybe screenshot the entire screen setup or figure it with my hint 
I want to see it in high quality, like in the previous updates:
I don’t have widgets.
I have tried to choose Desktop instead of Folder View. And when I try to move anything, it duplicates:
I think the desktop mode is not what I need.
1 Like
try to move the icons out via Dolphin, log out and in and them put them back. Are you using a third-party theme or Kvantum?
fzf-0.44.1-1-x86_64.pkg.tar.zst GOOD
fzf-0.46.1-1-x86_64.pkg.tar.zst No GOOD.
fzf-0.48.0-1-x86_64.pkg.tar.zst No GOOD. NEW