#wayland on 2023-08-15 — irc logs at oftc.irclog.whitequark.org

2023-04-28 11:16 ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput

00:15 columbarius has joined #wayland

00:16 co1umbarius has quit [Ping timeout: 480 seconds]

00:31 _DOOM_ has quit [Ping timeout: 480 seconds]

00:51 nerdopolis has joined #wayland

01:09 fmuellner has quit [Ping timeout: 480 seconds]

01:51 nerdopolis has quit [Ping timeout: 480 seconds]

02:19 nerdopolis has joined #wayland

02:31 nerdopolis has quit [Ping timeout: 480 seconds]

03:33 sevz has quit [Quit: WeeChat 4.0.2]

03:50 rv1sr has joined #wayland

04:49 Company has quit [Remote host closed the connection]

05:01 sevz has joined #wayland

05:17 _DOOM_ has joined #wayland

05:18 _DOOM_ has quit []

06:00 sima has joined #wayland

06:07 sevz has quit [Quit: WeeChat 4.0.2]

06:07 sevz has joined #wayland

06:24 sevz has left #wayland [WeeChat 4.0.2]

07:01 junaid has joined #wayland

07:22 Satan2 has joined #wayland

07:24 Satan2 has quit [Remote host closed the connection]

07:29 MrCooper has joined #wayland

07:39 ___nick___ has joined #wayland

07:49 ___nick___ has quit []

07:52 ___nick___ has joined #wayland

07:53 mblenc has joined #wayland

07:54 ___nick___ has quit []

07:54 mblenc has quit [Remote host closed the connection]

07:55 mblenc has joined #wayland

07:56 ___nick___ has joined #wayland

07:59 mblenc1 has joined #wayland

08:01 <mblenc> hi, i have an issue with my wayland compositor and an external monitor ive hooked up. the model number is WJ1980PI, and it is hooked up via a hdmi-to-vga adapter, as the monitor only have a soldered vga-in

08:02 <mblenc> the monitor works fine under windows, but under wayland and X it constantly resets when anything bright (i.e. the google.com homepage) is placed on it

08:02 <mblenc> this issue persists across multiple wayland compositors (ive tried dwl and sway), and nothing shows up under dmesg, so im a little confused

08:03 <mblenc> where can i find additional logs for this kind of issue? and if this is not the correct place to ask for support, where should i direct my query to?

08:08 lsd|2 has joined #wayland

08:10 <MrCooper> sounds like a KMS driver issue

08:20 ___nick___ has quit [Ping timeout: 480 seconds]

08:22 <mblenc> how can i debug that?

08:24 <mblenc> for a video showcasing the error: https://mblenczewski.com/pastebin/monitor-reset.mp4

08:25 <emersion> check dmesg maybe

08:26 <mblenc> dmesg shows no errors relating to KMS, or otherwise, when the monitor resets

08:27 <orowith2os[m]> MrCooper: if it were a KMS driver issue, it wouldn't happen on X though, would it?

08:27 <orowith2os[m]> IIRC X still does some weird framebuffer f*ckery

08:30 mvlad has joined #wayland

08:32 <MrCooper> not sure what you mean by that, Xorg has been using KMS since before Wayland was a thing

08:39 <orowith2os[m]> I need to look into it a bit more, or have someone explain it to me, bleh

08:40 <orowith2os[m]> my understanding thus far has been that X liked to go directly to a framebuffer, something something root userspace

08:40 <orowith2os[m]> and kms drivers have been available, but were a bit buggy?

08:41 <orowith2os[m]> I'd like to correct that if it's at all wrong

08:41 <jadahl> orowith2os[m]: Xorg either uses the modsetting driver (i.e. KMS) or vendor specific equivalent API in xorg video drivers

08:41 <jadahl> "equivalent"

08:42 <orowith2os[m]> I'm *assuming* in this case it would be the intel modesetting driver, but mblenc would have to confirm that

08:43 <orowith2os[m]> not "intel modesetting driver", bleh, xf86-video-intel

08:44 <mblenc> im on a radeon rx580, so have xf86-video-{amdgpu,ati}

08:53 <MrCooper> orowith2os[m]: all major vendor Xorg drivers (with the notable exception of nvidia) have been using KMS since "forever" as well

08:53 <MrCooper> what you're describing is outdated by over a decade

08:53 <orowith2os[m]> good to know, thanks

08:54 <orowith2os[m]> back to the main issue, mblenc: can you reproduce with the same adapter on another monitor, and without the adapter?

08:54 <orowith2os[m]> worth a shot

08:55 <mblenc> unfortunately, i do not have another monitor to reproduce this with. and my laptop doesn't have any vga-out

08:56 <mblenc> actually, i can probably get a live-usb running on another laptop i have lying around

08:56 <orowith2os[m]> alsooo what kernel version, and distro?

08:57 <orowith2os[m]> worth changing those up a bit too

08:57 <mblenc> 6.4.8-gentoo

08:57 <mblenc> ill try with an ubuntu live-usb then

09:00 lsd|2 has quit [Quit: KVIrc 5.0.1 Aria http://www.kvirc.net/]

09:06 mblenc1 has quit [Ping timeout: 480 seconds]

09:08 <mblenc> i forgot how long it takes to download and prepare an ubuntu live disk

09:10 <orowith2os[m]> Ventoy is a lifesaver, at least for hotswapping images :)

09:13 <mblenc> i might very well have to set that up. i currently have like 7 usbs lying around, some for memtest, some for gparted, and the rest as insallation disks in various states of functioning

09:15 mblenc1 has joined #wayland

09:15 <orowith2os[m]> they don't want you to know this but the Linux and debugging ISOs are all free, I have 12 of them on my USB with a full distro in a virtual hard disk too

09:20 rv1sr has quit []

09:24 cmichael has joined #wayland

09:50 <mblenc> took a long time, but got the live-iso running

09:50 <mblenc> ubuntu 23.0, works fine on both adapter and vga directly

09:51 <orowith2os[m]> what kernel does Ubuntu ship?

09:51 <mblenc> 6.2.0-20-generic

09:58 mblenc has quit [Remote host closed the connection]

10:01 <mblenc1> Testing my default laptop with the ubuntu live iso, maybe it is an issue with how i have configured my kernel and lsmod will give me some pointers

10:01 rasterman has joined #wayland

10:04 <mblenc1> No, the same issue is present even on ubuntu

10:05 <mblenc1> So the only constant is my laptop

10:05 <orowith2os[m]> wanna go back a bit more, and try a 5.x kernel?

10:05 <mblenc1> And even then, the hardware is probably at fault

10:05 <orowith2os[m]> (Ubuntu 22.xx)

10:05 <mblenc1> Sure, ill try that

10:08 <mblenc1> The 22.xx iso is even larger (by 100MB) than the 23.xx version :(

10:12 mblenc has joined #wayland

10:16 mblenc1 has quit [Ping timeout: 480 seconds]

10:16 <mblenc> Installing the iso now, should just take another 30 minutes or so

10:45 <mblenc> Trying ubuntu now, will take another 10 minutes to load and reach steady state

10:46 <mblenc> I wish i had bought a faster pendrive :(

10:56 <mblenc> The same issue occurs

10:57 <mblenc> And nothing is shows in the dmesg output on ubuntu 22.04 either

10:57 <orowith2os[m]> okay, good to know

10:58 <orowith2os[m]> so it's probably not the kernel - could be hardware, or a long-lasting kernel bug :P

10:58 <mblenc> I think its very probably a hardware issue

10:58 <mblenc> As loathe as i am to say that

10:59 <mblenc> I was able to run a test application under wayland and experienced the issue when the screen was filled with the rbg value of 220,220,220

10:59 <mblenc> Or thereabouts

10:59 <mblenc> Values of 200,200,200 ran just fine

10:59 <mblenc> Which is *very* wierd to me

10:59 <mblenc> Im wondering of its not a psu issue on the monitor side

11:00 <mblenc> But that wouldnt explain why it works seemingly just fine under windows

11:00 nerdopolis has joined #wayland

11:00 <mblenc> Or when connected to the other laptop

11:01 <mblenc> Ive read (and personally experienced) that the rx 580 isnt particularly well supported under linux when it comes to stability and suspend

11:01 <orowith2os[m]> my RX570 worked just fine fwiw

11:01 <mblenc> But then again my laptop (GL702ZC) is a buggy platform in general

11:01 <orowith2os[m]> I want to say it could be some difference in how everything's getting to your display on each OS; if Windows does something different, that could affect it

11:02 <orowith2os[m]> anyways, from here I'll leave it to the more experienced folks

11:02 <mblenc> Mine fails to start the display on boot sometimes, has random panics during boot, and suspend is completely broken

11:02 <mblenc> But thats beside the point

11:13 mblenc has quit [Quit: Quit]

11:14 mblenc has joined #wayland

11:14 mblenc1 has joined #wayland

11:16 * kennylevinsen hands daniels a cough drop

11:22 nerdopolis has quit [Ping timeout: 480 seconds]

11:23 zumbi has joined #wayland

11:25 <zumbi> Hello! On RISCV, we hit a segfault in a gtk4 testcase, which seems to be related to wayland, we have a backtrace - https://paste.debian.net/1288941/ - do you understand what could be happening there?

11:26 <kennylevinsen> zumbi: maybe the surface is destroyed? maybe there's a bug in gtk4? Collecting wayland debug (WAYLAND_DEBUG=1) and looking at gdksruface-wayland.c would be useful

11:27 <kennylevinsen> and printf debugging to the rescue

11:31 nerdopolis has joined #wayland

12:17 fmuellner has joined #wayland

12:58 nerdopolis has quit [Remote host closed the connection]

12:59 nerdopolis has joined #wayland

13:01 rasterman has quit [Quit: Gettin' stinky!]

13:10 nerdopolis has quit [Ping timeout: 480 seconds]

13:23 _whitelogger has joined #wayland

14:29 rv1sr has joined #wayland

14:39 kts has joined #wayland

14:42 mblenc1 has quit [Ping timeout: 480 seconds]

14:43 mblenc1 has joined #wayland

14:47 Company has joined #wayland

14:53 junaid has quit [Remote host closed the connection]

14:59 jmdaemon has quit [Ping timeout: 480 seconds]

15:09 cmichael has quit [Quit: Leaving]

15:23 junaid has joined #wayland

15:35 mohit815 has quit [Quit: mohit815]

15:36 mohit815 has joined #wayland

15:36 junaid has quit [Quit: leaving]

15:37 vyivel has quit [Ping timeout: 480 seconds]

15:57 mblenc1 has quit [Ping timeout: 480 seconds]

15:58 mblenc1 has joined #wayland

17:01 fmuellner has quit [Ping timeout: 480 seconds]

17:07 fmuellner has joined #wayland

17:10 junaid has joined #wayland

17:29 mblenc has quit [Remote host closed the connection]

17:32 pbsds is now known as Guest8981

17:32 pbsds has joined #wayland

17:34 Guest8981 has quit [Ping timeout: 480 seconds]

17:36 vsyrjala has joined #wayland

17:50 bodiccea has joined #wayland

17:53 bodiccea_ has quit [Ping timeout: 480 seconds]

18:14 gspbirel56873408867 has joined #wayland

18:19 gspbirel5687340886 has quit [Ping timeout: 480 seconds]

18:41 junaid has quit [Read error: No route to host]

18:42 junaid_ has joined #wayland

18:49 rv1sr has quit []

19:05 mvlad is now known as Guest8991

19:05 mvlad has joined #wayland

19:11 Guest8991 has quit [Ping timeout: 480 seconds]

19:18 fmuellner has quit [Ping timeout: 480 seconds]

19:30 sunrise890 has joined #wayland

19:32 sunrise890 has quit []

20:01 Moprius has joined #wayland

20:01 vyivel has joined #wayland

20:05 tent405 has quit [Ping timeout: 480 seconds]

20:17 Moprius has quit [Quit: bye]

20:23 junaid_ has quit [Ping timeout: 480 seconds]

20:24 tent405 has joined #wayland

20:24 junaid has joined #wayland

20:48 mvlad has quit [Remote host closed the connection]

20:59 junaid has quit [Ping timeout: 480 seconds]

21:57 sima has quit [Ping timeout: 480 seconds]

22:14 nerdopolis has joined #wayland

22:16 fmuellner has joined #wayland

22:52 Brainium has joined #wayland

22:55 Moprius has joined #wayland

23:05 nerdopolis has quit [Ping timeout: 480 seconds]

23:15 jmdaemon has joined #wayland

23:17 Moprius has quit [Quit: bye]

23:28 nerdopolis has joined #wayland

23:37 <RAOF> 2

23:38 <RAOF> Ahem.

23:53 bodiccea has quit [Ping timeout: 480 seconds]

23:58 nerdopolis has quit [Ping timeout: 480 seconds]

23:59 kts has quit [Quit: Konversation terminated!]