#[Solved] Multitouch feature is not working after sudo systemctl restart gdm3

206 messages · Page 1 of 1 (latest)

dim ruin
#

I was trying to make my screen capture work in OBS, `

I found a solution.

Firstly you need to install the Xorg package

sudo apt-get update
sudo apt-get install xserver-xorg
In this file /etc/gdm3/custom.conf (to access it for editing, you could run sudo nano /etc/gdm3/custom.conf), uncomment (remove the leading #) this line

WaylandEnable=false
save and exit.

Then run this command in the terminal

sudo systemctl restart gdm3
Happy Ubuntu :)

`

I followed these steps, the obs seemed to work but now my multi touch feature doen't work

#

@ashen sluice

ashen sluice
#

hi!

#

you should undo this change

dim ruin
#

But then I won't be able to use the screen capture feature

ashen sluice
#

then try to start obs and show me what happens when you try

dim ruin
#

Okay

#

idk

ashen sluice
#

im already handling this thread

#

um

#

my plan is to find out what's making obs's wayland screen capture support not work for you, and fix it, so you can have both multitouch and screen capture

dim ruin
#

Got the multi touch working by undoing the things, but now this is the issue

#

Oh

#

Not pacman. I am using ubuntu

#

sudo apt install pipewire?

ashen sluice
#

no hold on

#

this isn't the right solution

dim ruin
#

It was already there

#

Didn't fix it

ashen sluice
#

@dim ruin the problem is that your source is trying to use x11 calls to capture the screen

#

you need to delete the source

#

and add a new one

#

of the type "Screen Capture (PipeWire)"

dim ruin
#

How do I do that?

ashen sluice
#

hit the trashcan button, then hit the plus

#

under the list of sources

#

this is not helpful

dim ruin
ashen sluice
#

we already know they're now on wayland

ashen sluice
ashen sluice
# dim ruin

hm ok, it looks like your build of OBS might not have wayland support enabled? another question: what DE are you running

dim ruin
#

Yeah, disabling wayland makes my multi touch not work

ashen sluice
#

they just said they have pipewire installed

dim ruin
ashen sluice
#

okay

ashen sluice
dim ruin
#

flatpak

ashen sluice
#

okay

#

NO

#

why are you telling them to enable the KDE Plasma service when they're on GNOME

dim ruin
#

yeah

#

he's trying to convert me to kde plasma like those church people

ashen sluice
#

run the following command to force OBS to directly talk to the Wayland compositor, instead of emulated X11: flatpak override --env=QT_QPA_PLATFORM=wayland com.obsproject.Studio

#

then fully quit OBS and restart it

dim ruin
#

okay, let me just reboot

#

it didn't work

ashen sluice
#

hm okay

#

can you go to help -> log files -> upload current log file, and send the link here?

dim ruin
#

okay

#

Which one?

#

nvm

ashen sluice
#

wait wha

dim ruin
#

what

ashen sluice
#

this is what i meant

dim ruin
#

oh

#

G

#

F

#

rookie mistake

ashen sluice
#

okay, so it seems like the issue here is that ubuntu ships pipewire by default, but doesn't use it by default

#

can you try doing the following:

#

run systemctl --user status pulseaudio.service

#

and systemctl --user status pipewire.service

#

post both

dim ruin
#

okay

#

another one

image.png
#

I did inxi -A

image.png
dim ruin
ashen sluice
dim ruin
#

Uh I got pipewire as my default but now I can't turn up my audio cause it's not there. Let me follow the link you sent

#

The sound thing is gone too, and the obs is still not working 💀

ashen sluice
#

umm

#

did you follow the exact steps at that link?

dim ruin
#

yes

ashen sluice
#

okay

#

what happens when you run the command pactl info | grep '^Server Name'

dim ruin
#

I think that is the only way to disable pulse audio and enable pipewire

dim ruin
ashen sluice
#

okay

#

run pw-cli info all > pw_info.txt and upload the resulting file pw_info.txt

dim ruin
ashen sluice
#

...?

#

that's okay

dim ruin
#

When I run pw-cli info all > pw_info.txt, it returns that

ashen sluice
#

the file should still have all the info we need

dim ruin
#

oh

#

Uh

#

UH how do I extract the file

#

pw-cli is not a directory

ashen sluice
#

what

dim ruin
#

how do I get pw_info.txt

ashen sluice
#

in what working directory did you run the command?

dim ruin
#

the default one

ashen sluice
#

um

dim ruin
#

root directory

#

it's root directory right

ashen sluice
#

no?

#

can you run pwd

dim ruin
#

oh

#

i am in usr

#

/home/[me]

ashen sluice
#

then the file is there

dim ruin
#

oh

#

yes

#

the file is empty

ashen sluice
#

...

crimson wraithBOT
#

Too few arguments for command note!
Usage: .note <name>

dim ruin
ashen sluice
#

huh

dim ruin
#

LMAO

ashen sluice
#

this is really weird

#

what happens if you run journalctl --user -u pipewire-pulse.service

dim ruin
#

this happens

ashen sluice
#

and just for good measure, i'd like you to run this command and post its output: systemctl --user status xdg-desktop-portal-gnome.service pipewire.service pipewire-pulse.service pulseaudio.service

dim ruin
ashen sluice
#

that's only the first bit

dim ruin
#

oh yeah

ashen sluice
#

but it gives me a pretty good clue of what the problem is

dim ruin
#

let me scroll it up a bit

ashen sluice
#

i would still like the rest though

#

yeah

dim ruin
ashen sluice
#

okay

dim ruin
#

What are we looking at here?

#

pipewire log files?

ashen sluice
#

checking whether the services all successfully started and ran

#

okay

#

one more try at checking whether pipewire sees anything

#

run pw-cli list-objects

dim ruin
#

uh a lot of ids came up

ashen sluice
#

okay

dim ruin
ashen sluice
#

this is good

dim ruin
ashen sluice
#

okay

dim ruin
#

Do you want all of them?

ashen sluice
#

no this is fine

#

okay

dim ruin
#

Okay

ashen sluice
#

so

#

i found the piece that's missing

#

install the package xdg-desktop-portal-gnome

#

then enable it with systemctl --user enable --now xdg-desktop-portal-gnome.service

#

then reboot. after that, check if audio works, and try adding a PipeWire source in OBS

dim ruin
# ashen sluice then enable it with `systemctl --user enable --now xdg-desktop-portal-gnome.serv...

The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.

Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.

ashen sluice
#

oh no

#

you're right

#

hang on

dim ruin
#

okay

ashen sluice
#

yeah that step isn't necessary because i forgot how desktop portals worked

#

skip it

dim ruin
#

okay

#

so reboot

ashen sluice
#

yes

dim ruin
#

nope didn't work

ashen sluice
#

which parts?

dim ruin
#

oh shit obs is working]

#

just the audio now

ashen sluice
#

does audio playback from applications work?

dim ruin
ashen sluice
#

can you run the two commands in the "install" section here?

dim ruin
#

it shows no output device

ashen sluice
#

yes

dim ruin
#

OHHH

#

IT WORKED

#

I think

ashen sluice
#

cool!

dim ruin
#

yayy

#

yep

ashen sluice
#

ok congrats! you have now made your linux system work as it should

dim ruin
#

I just installed alsa plugin

ashen sluice
#

i don't know why ubuntu maintainers neglected to do all of this as they should have

dim ruin
#

thank you, anna

ashen sluice
#

:/

#

fedora has all of this preconfigured

dim ruin
#

Anyways, thanks for the help!

ashen sluice
#

yw!

#

glad everything works now

dim ruin
#

yeah

ashen sluice
#

[Solved] Multitouch feature is not working after sudo systemctl restart gdm3

dim ruin
#

what's way land though?

ashen sluice
#

Wayland is a display server protocol, in other words it's a language that programs speak to your desktop in order to show things on the screen

dim ruin
#

Oh

ashen sluice
#

it replaces the old system for showing things on the screen, which relied on a server called X11 that was developed a really long time ago

#

it had a lot of design flaws and needed a lot of bad workarounds for them

dim ruin
#

So, if wayland is off and something is on, the program could be running in the background, but just not show on the desktop?

ashen sluice
#

if your desktop isn't running, then your programs can't talk to it, yes

dim ruin
#

Okay

#

Understandable

#

Have a nice day

ashen sluice
#

okay!