Firedragon broken after 1:11:17 update

After updating to the new firedragon an rebooting. i noticed i couldnt really open addons or the settings menu though since I use the side bar I was able to verify the settings for the theme to make sure it was not that.
Floorp does not have this same issue. This one has me stumped.

Name : firedragon
Version : 1:11.17.4-2.1
Description : Floorp fork build using custom branding and settings
Architecture : x86_64
URL : https://garudalinux.org
Licenses : MPL2
Groups : None
Provides : None
Depends On : dbus dbus-glib ffmpeg gtk3 libevent libjpeg libpulse libvpx libwebp libxss libxt
mime-types nss pipewire ttf-font zlib
Optional Deps : hunspell-dictionary: Spell checking
libnotify: Notification integration [installed]
networkmanager: Location detection via available WiFi networks [installed]
profile-sync-daemon: Load the browser profile into RAM [installed]
pulseaudio: Audio support
searx: Searching the web using a locally running searX instance
speech-dispatcher: Text-to-Speech [installed]
whoogle: Searching the web using a locally running Whoogle instance
xdg-desktop-portal: Screensharing with Wayland [installed]
Required By : None
Optional For : None
Conflicts With : None
Replaces : None
Installed Size : 284.28 MiB
Packager : Garuda Builder [email protected]
Build Date : Tue 20 Aug 2024 11:25:28 AM CDT
Install Date : Tue 20 Aug 2024 08:23:32 PM CDT
Install Reason : Explicitly installed
Install Script : No
Validated By : SHA-256 Sum Signature


System:
Kernel: 6.10.6-1-cachyos arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-cachyos
root=UUID=ed618e85-c1b1-4a62-9eef-7263837ec30d rw rootflags=subvol=@
resume=UUID=9e39bce2-8148-4e68-83a2-8185da8c85fb loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.1.4 tk: Qt v: N/A info: frameworks v: 6.5.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME X570-PRO v: Rev X.0x
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 5013 date: 03/22/2024
CPU:
Info: model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2 gen: 3
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701033
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
L3: 32 MiB desc: 2x16 MiB
Speed (MHz): avg: 3264 high: 3980 min/max: 550/4426 boost: enabled
scaling: driver: amd-pstate-epp governor: powersave cores: 1: 3975 2: 3843
3: 3931 4: 550 5: 3975 6: 3980 7: 3976 8: 3971 9: 3978 10: 3611 11: 550
12: 3685 13: 3697 14: 3977 15: 550 16: 3976 bogomips: 115205
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX/7900M] vendor: Sapphire
driver: amdgpu v: kernel arch: RDNA-3 code: Navi-3x process: TSMC n5 (5nm)
built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-1
empty: DP-2, HDMI-A-1, HDMI-A-2, Writeback-1 bus-ID: 0c:00.0
chip-ID: 1002:744c class-ID: 0300
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.2
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu display-ID: 0
Monitor-1: DP-1 res: 3127x1309 size: N/A modes: N/A
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: 24.3.0-devel
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 7900 GRE (radeonsi
navi31 LLVM 18.1.8 DRM 3.57 6.10.6-1-cachyos) device-ID: 1002:744c
memory: 15.62 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 13 device: 0 type: discrete-gpu name: AMD
Radeon RX 7900 GRE (RADV NAVI31) driver: mesa radv
v: 24.3.0-devel (git-8ee7f89641) device-ID: 1002:744c
surfaces: xcb,xlib,wayland device: 1 type: cpu name: llvmpipe (LLVM
18.1.8 256 bits) driver: mesa llvmpipe v: 24.3.0-devel (git-8ee7f89641)
(LLVM 18.1.8) device-ID: 10005:0000 surfaces: xcb,xlib,wayland
Audio:
Device-1: AMD Navi 31 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0c:00.1 chip-ID: 1002:ab30
class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0e:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: Texas Instruments PCM2900C Audio CODEC
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 5-2:3 chip-ID: 08bb:29c0 class-ID: 0300
API: ALSA v: k6.10.6-1-cachyos status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 1.2.2 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Wireless 7260 driver: iwlwifi v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:08b1 class-ID: 0280
IF: wlp5s0 state: down mac: <filter>
Device-2: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 06:00.0
chip-ID: 8086:1539 class-ID: 0200
IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB
rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-6:3 chip-ID: 8087:07dc
class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0
lmp-v: 6 sub-v: e00 hci-v: 6 rev: e00 class-ID: 6c0104
Info: acl-mtu: 1021:5 sco-mtu: 96:6 link-policy: rswitch hold sniff
link-mode: peripheral accept service-classes: rendering, capturing, audio,
telephony
Drives:
Local Storage: total: 4.68 TiB used: 3.83 TiB (81.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: HP model: SSD EX920 1TB
size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 32A0T2IA temp: 45.9 C
scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:7 vendor: Samsung model: SSD 980 PRO 2TB
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 5B2QGXA7 temp: 49.9 C
scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: OCZ model: VERTEX3 size: 111.79 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD
serial: <filter> fw-rev: 2.22 scheme: GPT
ID-4: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD20EZAZ-00L9GB0 size: 1.82 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
Partition:
ID-1: / raw-size: 1.8 TiB size: 1.8 TiB (100.00%) used: 1.43 TiB (79.4%)
fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:9
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 27.6 MiB (9.2%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:8
ID-3: /home raw-size: 1.8 TiB size: 1.8 TiB (100.00%)
used: 1.43 TiB (79.4%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:9
ID-4: /var/log raw-size: 1.8 TiB size: 1.8 TiB (100.00%)
used: 1.43 TiB (79.4%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:9
ID-5: /var/tmp raw-size: 1.8 TiB size: 1.8 TiB (100.00%)
used: 1.43 TiB (79.4%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:9
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 15.53 GiB used: 2.24 GiB (14.4%)
priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16
dev: /dev/zram0
ID-2: swap-2 type: partition size: 17.07 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme1n1p3 maj-min: 259:10
Sensors:
System Temperatures: cpu: 45.0 C mobo: 45.0 C gpu: amdgpu temp: 56.0 C
mem: 74.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 603
Info:
Memory: total: 16 GiB available: 15.53 GiB used: 6.47 GiB (41.6%)
Processes: 409 Power: uptime: 6m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 6.18 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: 2669 pm: pacman pkgs: 2622 libs: 635 tools: octopi,pacseek,paru
pm: flatpak pkgs: 47 Compilers: clang: 18.1.8 gcc: 14.2.1 alt: 13
Shell: garuda-inxi default: fish v: 3.7.1 running-in: yakuake inxi: 3.3.35
Garuda (2.6.26-1):
System install date:     2024-05-15
Last full system update: 2024-08-20
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
1 Like

Tnx for reporting.

For follow-up you can go here.

In the meantime can you try the AppImage?

You can also try with a new Profile.

3 Likes

I can replicate it with the appimage. And also a new plasma user.

One weird thing is when you first open it as a appimage or a new user/new profile, is it opens in 1,578x751 every time unless you make a window rule.

I don’t have any non kde test distros installed so I cant test it in that.

Image from appimage

And appimage I had no idea but now im excited!

1 Like

Yeah it’s new stuff and really really useful for testing, but also to use daily, I am using it now, see what downsides I’ll get. Managing profiles needs to be done through about:profiles as I could not pass de -P parm when launching AppImage. There’s also another hack to perform for those uninstalling completely the native Arch package of Firedragon, but so far AppImage works a lot better than I expected.

This is off topic though.

Your issue is very strange cuz neither the native package, AppImage nor firedragon-bin package were able to cause the issue on my machine.

Now what happens if you close FD, rename

/usr/lib/firedragon/firedragon.cfg
~/.firedragon/firedragon.overrides.cfg

and then launch again?

EDIT:

This means also a new Firedragon PROFILE? Not just Plasma user?

1 Like

Do you use fractional display scaling? Or just have differing scaling between displays? Or something along those lines?

2 Likes

@elite try turning that one off in about:config:

widget.wayland.fractional-scale.enabled
3 Likes

Yes I forgot I had that turned on from testing it way back. But yea fractional scaling in kde is the cause.
Only one ultra-wide here as well.

Still interesting bug though.

Shutting this off works as well. and turning off scaling in plasma as well.


I tested it in a newly made kde user profile. Which comes slandered with fractional scaling.

Well, I don’t think you are to blame here:

:sweat_smile:

Am currently preparing the commit to revert this one.

2 Likes

I think down the line it might be more useful for sure. but happy we got it all solved.

2 Likes

Yes I am using this config on my machine since we moved to Floorp.
Not sure whether the issue is on the Firefox side or Plasma on this one…

3 Likes

Let’s add it to Tipps & tricks section (worth creating one? :smiley: ) in the docs?

2 Likes

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