wayland session?

T

we're waiting on this to be fixed before shipping it into

:stable

:stable

on bazzite
https://bugzilla.mozilla.org/show_bug.cgi?id=1898476

1898476 - Firefox crashes on Wayland with Explicit Sync on Nvidia

ASSIGNED (stransky) in Core - Widget: Gtk. Last updated 2024-06-28.

T

tryhardsoccermomswagOP•6/29/24, 2:45 PM

especially because we're ditching X11 by default on KDE images after the 555 drivers drop

T

tryhardsoccermomswagOP•6/29/24, 2:47 PM

the workaround is to run firefox in XWayland or use a different browser but since we ship Firefox as a pre-installed application, its better if it was fixed upstream first

T

tryhardsoccermomswagOP•6/29/24, 2:47 PM

less people complaining that the newest update broke their browser

Ttryhardsoccermomswag wayland session?

V

vaGIF•6/29/24, 2:47 PM

yes

T

tryhardsoccermomswagOP•6/29/24, 2:48 PM

:clueless: and its not in XWayland mode or anything?

V

vaGIF•6/29/24, 2:48 PM

Oh it might actually be running on X Wayland

T

tryhardsoccermomswagOP•6/29/24, 2:48 PM

yea

T

tryhardsoccermomswagOP•6/29/24, 2:48 PM

thats the workaround

V

vaGIF•6/29/24, 2:48 PM

I am on EndeavourOS if that's relevant

V

vaGIF•6/29/24, 2:48 PM

They might have it implemented by default

T

tryhardsoccermomswagOP•6/29/24, 2:48 PM

no idea what changes endeavour does over arch tbh

B

byeproduct•6/29/24, 2:58 PM

so, I'm looking at connecting an external NTFS HDD on bazzite. I saw an article recommending running this command in fedora to install the necessary drivers: sudo dnf install ntfs-3g fuse
is that the correct way with bazzite? Obv a linux n00b here....

K

Kasher_CS•6/29/24, 2:59 PM

No, no need to install drivers now

T

tryhardsoccermomswagOP•6/29/24, 2:59 PM

yea

T

tryhardsoccermomswagOP•6/29/24, 2:59 PM

we have

ntfs-3g

ntfs-3g

ntfs-3g

ntfs-3g preinstalled btw

K

Kasher_CS•6/29/24, 2:59 PM

Drivers are built in

K

Kasher_CS•6/29/24, 2:59 PM

Wait we have it too?

T

tryhardsoccermomswagOP•6/29/24, 2:59 PM

yea

T

tryhardsoccermomswagOP•6/29/24, 2:59 PM

fedora includes it iirc

K

Kasher_CS•6/29/24, 3:00 PM

Huh, seems strange now but alright

Bbyeproduct so, I'm looking at connecting an external NTFS HDD on bazzite. I saw an article ...

T

tryhardsoccermomswagOP•6/29/24, 3:00 PM

also no

dnf

dnf

dnf

dnf here

T

tryhardsoccermomswagOP•6/29/24, 3:00 PM

and do not game on that NTFS drive on linux

K

Kasher_CS•6/29/24, 3:00 PM

Technically there is

dnf

dnf

dnf

dnf

T

tryhardsoccermomswagOP•6/29/24, 3:00 PM

its an alias

B

byeproduct•6/29/24, 3:00 PM

okay awesome. but... when I connect it via usb, it doesn't pick up the drive in dolphin. is there another app I should be using. I just wanna transfer data over from the old hdd

T

tryhardsoccermomswagOP•6/29/24, 3:00 PM

later on when bootc is mature and ready, there will be dnf again

Ttryhardsoccermomswag also no `dnf` here

B

byeproduct•6/29/24, 3:01 PM

what's the alternative for that?

Bbyeproduct what's the alternative for that?

T

tryhardsoccermomswagOP•6/29/24, 3:01 PM

rpm-ostree

rpm-ostree

but only use it as a last resort

K

Kasher_CS•6/29/24, 3:01 PM

Strange, dolphin should pick it fine. Partition manager picks it up?

K

Kasher_CS•6/29/24, 3:02 PM

If its an HDD, you using a USB adapter?

KKasher_CS If its an HDD, you using a USB adapter?

B

byeproduct•6/29/24, 3:02 PM

yes. straight connection. it does pick it up on windows like that

T

tryhardsoccermomswagOP•6/29/24, 3:03 PM

kind of weird but NTFS drives are beyond my knowledge tbh

Ttryhardsoccermomswag later on when bootc is mature and ready, there will be dnf again

W

Wojciech Pawlik•6/29/24, 3:03 PM

Instead of

rpm-ostree

rpm-ostree

?

WWojciech Pawlik Instead of `rpm-ostree`?

T

tryhardsoccermomswagOP•6/29/24, 3:03 PM

yea

B

byeproduct•6/29/24, 3:03 PM

partition manager says "no valid partition found on this device"

K

Kasher_CS•6/29/24, 3:04 PM

Huh, strange, most USB adapters need power to work

Ttryhardsoccermomswag yea

W

Wojciech Pawlik•6/29/24, 3:05 PM

What will be the difference from Workstation at that point?

K

Kasher_CS•6/29/24, 3:05 PM

This isn't a problem with the partition in this case

Z

Zeglius•6/29/24, 3:06 PM

so, Bazzite is supposed to rely in setroubeshootd for SELinux? Because I noticed this

Z

Zeglius•6/29/24, 3:06 PM

○ setroubleshootd.service - SETroubleshoot daemon for processing new SELinux denial logs
     Loaded: loaded (/usr/lib/systemd/system/setroubleshootd.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)

jun 29 16:54:45 fedora setroubleshoot[10540]: cannot create file /var/lib/setroubleshoot/setroubleshoot_database.xml [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chmod /var/lib/setroubleshoot/setroubleshoot_database.xml to 600 [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chown /var/lib/setroubleshoot/setroubleshoot_database.xml to setroubleshoot:setroubleshoot [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot create file /var/lib/setroubleshoot/email_alert_recipients [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chmod /var/lib/setroubleshoot/email_alert_recipients to 600 [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chown /var/lib/setroubleshoot/email_alert_recipients to setroubleshoot:setroubleshoot [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: could not write /var/lib/setroubleshoot/setroubleshoot_database.xml: [Errno 2] No such file or directory: '/var/lib/setroubleshoot/setroubleshoot_database.xml'
jun 29 16:54:59 fedora setroubleshoot[10540]: could not write /var/lib/setroubleshoot/setroubleshoot_database.xml: [Errno 2] No such file or directory: '/var/lib/setroubleshoot/setroubleshoot_database.xml'
jun 29 16:54:59 fedora systemd[1]: setroubleshootd.service: Deactivated successfully.
jun 29 16:54:59 fedora systemd[1]: setroubleshootd.service: Consumed 1.365s CPU time.

○ setroubleshootd.service - SETroubleshoot daemon for processing new SELinux denial logs
     Loaded: loaded (/usr/lib/systemd/system/setroubleshootd.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)

jun 29 16:54:45 fedora setroubleshoot[10540]: cannot create file /var/lib/setroubleshoot/setroubleshoot_database.xml [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chmod /var/lib/setroubleshoot/setroubleshoot_database.xml to 600 [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chown /var/lib/setroubleshoot/setroubleshoot_database.xml to setroubleshoot:setroubleshoot [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot create file /var/lib/setroubleshoot/email_alert_recipients [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chmod /var/lib/setroubleshoot/email_alert_recipients to 600 [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chown /var/lib/setroubleshoot/email_alert_recipients to setroubleshoot:setroubleshoot [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: could not write /var/lib/setroubleshoot/setroubleshoot_database.xml: [Errno 2] No such file or directory: '/var/lib/setroubleshoot/setroubleshoot_database.xml'
jun 29 16:54:59 fedora setroubleshoot[10540]: could not write /var/lib/setroubleshoot/setroubleshoot_database.xml: [Errno 2] No such file or directory: '/var/lib/setroubleshoot/setroubleshoot_database.xml'
jun 29 16:54:59 fedora systemd[1]: setroubleshootd.service: Deactivated successfully.
jun 29 16:54:59 fedora systemd[1]: setroubleshootd.service: Consumed 1.365s CPU time.

○ setroubleshootd.service - SETroubleshoot daemon for processing new SELinux denial logs
     Loaded: loaded (/usr/lib/systemd/system/setroubleshootd.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)

jun 29 16:54:45 fedora setroubleshoot[10540]: cannot create file /var/lib/setroubleshoot/setroubleshoot_database.xml [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chmod /var/lib/setroubleshoot/setroubleshoot_database.xml to 600 [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chown /var/lib/setroubleshoot/setroubleshoot_database.xml to setroubleshoot:setroubleshoot [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot create file /var/lib/setroubleshoot/email_alert_recipients [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chmod /var/lib/setroubleshoot/email_alert_recipients to 600 [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chown /var/lib/setroubleshoot/email_alert_recipients to setroubleshoot:setroubleshoot [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: could not write /var/lib/setroubleshoot/setroubleshoot_database.xml: [Errno 2] No such file or directory: '/var/lib/setroubleshoot/setroubleshoot_database.xml'
jun 29 16:54:59 fedora setroubleshoot[10540]: could not write /var/lib/setroubleshoot/setroubleshoot_database.xml: [Errno 2] No such file or directory: '/var/lib/setroubleshoot/setroubleshoot_database.xml'
jun 29 16:54:59 fedora systemd[1]: setroubleshootd.service: Deactivated successfully.
jun 29 16:54:59 fedora systemd[1]: setroubleshootd.service: Consumed 1.365s CPU time.

○ setroubleshootd.service - SETroubleshoot daemon for processing new SELinux denial logs
     Loaded: loaded (/usr/lib/systemd/system/setroubleshootd.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)

jun 29 16:54:45 fedora setroubleshoot[10540]: cannot create file /var/lib/setroubleshoot/setroubleshoot_database.xml [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chmod /var/lib/setroubleshoot/setroubleshoot_database.xml to 600 [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chown /var/lib/setroubleshoot/setroubleshoot_database.xml to setroubleshoot:setroubleshoot [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot create file /var/lib/setroubleshoot/email_alert_recipients [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chmod /var/lib/setroubleshoot/email_alert_recipients to 600 [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chown /var/lib/setroubleshoot/email_alert_recipients to setroubleshoot:setroubleshoot [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: could not write /var/lib/setroubleshoot/setroubleshoot_database.xml: [Errno 2] No such file or directory: '/var/lib/setroubleshoot/setroubleshoot_database.xml'
jun 29 16:54:59 fedora setroubleshoot[10540]: could not write /var/lib/setroubleshoot/setroubleshoot_database.xml: [Errno 2] No such file or directory: '/var/lib/setroubleshoot/setroubleshoot_database.xml'
jun 29 16:54:59 fedora systemd[1]: setroubleshootd.service: Deactivated successfully.
jun 29 16:54:59 fedora systemd[1]: setroubleshootd.service: Consumed 1.365s CPU time.

Z

Zeglius•6/29/24, 3:07 PM

seems the selinux troubleshooter is kneecapped by selinux itself

KKasher_CS This isn't a problem with the partition in this case

B

byeproduct•6/29/24, 3:12 PM

If its not a problem, is there anything else I can try?

ZZeglius seems the selinux troubleshooter is kneecapped by selinux itself 😂

M

M2•6/29/24, 3:13 PM

It doesn't create /var/lib/setroubleshoot so it freaks out

Z

Zeglius•6/29/24, 3:13 PM

Yeah can see that

Z

Zeglius•6/29/24, 3:17 PM

rather cant touch anything at /var/lib/setroubleshoot ( that after

 mkdir -p /var/lib/setroubleshoot/; touch /var/lib/setroubleshoot/setroubleshoot_database.xml

mkdir -p /var/lib/setroubleshoot/; touch /var/lib/setroubleshoot/setroubleshoot_database.xml

 mkdir -p /var/lib/setroubleshoot/; touch /var/lib/setroubleshoot/setroubleshoot_database.xml

mkdir -p /var/lib/setroubleshoot/; touch /var/lib/setroubleshoot/setroubleshoot_database.xml)

A

antheas•6/29/24, 3:19 PM

xwayland is not x11

A

antheas•6/29/24, 3:19 PM

its not going away

A

antheas•6/29/24, 3:19 PM

its perfectly fine to use xwayland right now, apart from fractional scaling

A

antheas•6/29/24, 3:19 PM

which looks like garbage on x11 apps

Similar Threads

Similar Threads

Similar Threads