I still cannot help with something specific, but i tested a little.
Firstly, i downloaded it from the site. The right download is the tar.gz one at the top, not the zip. Unpack. It contains desktop file that should work on doubleclick, it didn’t (it was missing ./ in the exec line ./tvbrowser.sh, i fixed it), It works, except the tray icon menu. Without any warning for screen sharing.
So at least on XFCE it works as it should. With java 22.
So it has to do either something with the wrong download, or java, but most probably it is Plasma or Wayland stuff, which are both not present in my case.
it’s a good recommendation to switch from wayland to x11 cause a lot of these iptv-programms rely on x11 and fail with wayland. especially because this application uses virtual displays ! wayland still fails on virtual-communication-apps.
second problem is the using of nouveau. that’s a bad decission if you’re running gpu-related stuff on nvidia with nouveau. the possibility that it doesn’t work is very high. switch to the propietary nvidia driver
It does not actually play video, so it is probably not the video driver.
The desktop portal is by the way triggered if you click to open the entry in browser. Shouldn’t be triggered from any other actions. Somehow in your case the app/java/plasma does not know what exactly to trigger and kind of turns on all the portal features…at least looks that way.
But whatever you do, do not remove the portals. They are used for many things behind the scenes so a lot of programs will start to crash.
in /etc/default/grub
before GRUB_CMDLINE_LINUX="" and now GRUB_CMDLINE_LINUX="nvidia_drm.fbdev=1"
and
in `/etc/mkinitcpio.conf`
before MODULES=() and now MODULES=(nvidia_drm)
brings no change.
It still boots into black blank screen
than strg + alt 3
login + pssword
than startplasma-wayland
and than I am able to login into the desktop.
And the main problem still persist.
So if I do a new clean install with open source driver,
without the proprietary driver because I would like to have wayland functional.
And it comes up again?
How do I get rid of this screen sharing thing “Bildschirmübertragung”
If it comes up again?
~ sudo mkinitcpio -P ✔
[sudo] Passwort für tony:
==> Building image from preset: /etc/mkinitcpio.d/linux69.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-6.9-x86_64 -g /boot/initramfs-6.9-x86_64.img
==> Starting build: '6.9.0-1-MANJARO'
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [kms]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> ERROR: module not found: 'nvidia_drm'
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.9-x86_64.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux69.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-6.9-x86_64 -g /boot/initramfs-6.9-x86_64-fallback.img -S autodetect
==> Starting build: '6.9.0-1-MANJARO'
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> ERROR: module not found: 'nvidia_drm'
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.9-x86_64-fallback.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
~ sudo update-grub 1 ✘ 40s
GRUB-Konfigurationsdatei wird erstellt …
Thema gefunden: /usr/share/grub/themes/manjaro/theme.txt
Linux-Abbild gefunden: /boot/vmlinuz-6.9-x86_64
Initrd-Abbild gefunden: /boot/intel-ucode.img /boot/initramfs-6.9-x86_64.img
Found initrd fallback image: /boot/initramfs-6.9-x86_64-fallback.img
Warnung: Zur Erkennung anderer bootfähiger Partitionen wird os-prober ausgeführt.
Dessen Ausgabe wird zur Erkennung bootfähiger Programmdateien und Erzeugen neuer Boot-Einträge verwendet.
grub-probe: Fehler: Für /dev/sdb1 konnte kein GRUB-Laufwerk gefunden werden. Überprüfen Sie Ihre device.map.
grub-probe: Fehler: Für /dev/sdb1 konnte kein GRUB-Laufwerk gefunden werden. Überprüfen Sie Ihre device.map.
Windows Boot Manager auf /dev/nvme1n1p1@/EFI/Microsoft/Boot/bootmgfw.efi gefunden
Bootmenü-Eintrag für UEFI-Firmware-Einstellungen wird hinzugefügt …
Root filesystem isn't btrfs
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: Warnung: Unbekannter Gerätetyp nvme1n1.
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
/usr/bin/grub-probe: Warnung: Unbekannter Gerätetyp nvme1n1.
abgeschlossen
~
no result still stays blank at start of Plasma.
But I remember that I try to uninstall after I had that black screen.
sudo pacman -R linux69-nvidia
After someone gave me the tip to run “sudo mhwd -a pci nonfree 0300”
So When I new reinstalling with manjaro-kde-24.0-minimal-240513-linux69.iso.
Should I Install with Open source or proprietary drivers?
When I change to Wayland and reboot?
When I reinstall and tell the Installer that I want a seperate /home partition.
And leave it unformated.
Will the System recognize as my /home and all will be as it was before Install?
I later I ran <sudo grub-mkconfig -o /boot/grub/grub.cfg>
sudo grub-mkconfig -o /boot/grub/grub.cfg ✔
[sudo] Passwort für tony:
GRUB-Konfigurationsdatei wird erstellt …
Thema gefunden: /usr/share/grub/themes/manjaro/theme.txt
Linux-Abbild gefunden: /boot/vmlinuz-6.9-x86_64
Initrd-Abbild gefunden: /boot/intel-ucode.img /boot/initramfs-6.9-x86_64.img
Found initrd fallback image: /boot/initramfs-6.9-x86_64-fallback.img
Warnung: Zur Erkennung anderer bootfähiger Partitionen wird os-prober ausgeführt.
Dessen Ausgabe wird zur Erkennung bootfähiger Programmdateien und Erzeugen neuer Boot-Einträge verwendet.
grub-probe: Fehler: Für /dev/sdb1 konnte kein GRUB-Laufwerk gefunden werden. Überprüfen Sie Ihre device.map.
grub-probe: Fehler: Für /dev/sdb1 konnte kein GRUB-Laufwerk gefunden werden. Überprüfen Sie Ihre device.map.
Windows Boot Manager auf /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi gefunden
Bootmenü-Eintrag für UEFI-Firmware-Einstellungen wird hinzugefügt …
Root filesystem isn't btrfs
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: Warnung: Unbekannter Gerätetyp nvme0n1.
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
/usr/bin/grub-probe: Warnung: Unbekannter Gerätetyp nvme0n1.
abgeschlossen
~
And than Installed “linux69-nvidia”
Reboot and I booted in a Wayland Session.
But my Mail Problem still exsists.
How do I get rid of this screen sharing thing “Bildschirmübertragung”???
Many Thanks for your help
Greetings Tony
PS
should I open a new questions for
So When I new reinstalling with manjaro-kde-24.0-minimal-240513-linux69.iso or newer ISO.
When I reinstall and tell the Installer that I want a seperate /home partition.
And leave it unformated.
Will the System recognize as my /home and all will be as it was before Install?
Thanks
Tony
If you already have a separate /home partition. then you can use the manual installation/partitioning and tell the installer about your partition and that you want to use it as /home in the new install
and(!) that it should not be touched or, god forbid, reformatted.
But I would not trust any installer not to fail at this - nor would I trust myself to not make an error or to not forget to check some box.
If you do not yet have a separate partition for /home, then no - this won’t be possible.
I’d make a backup of /home
and then install and afterward restore the contents of /home from the backup.
/etc/mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES=(usbhid xhci_hcd)
MODULES=(**nvidia_drm**)
And than I Installed “linux69-nvidia” in pamac-manager GUI
Run sudo update-grub and mkinitcpio -P and later also sudo grub-mkconfig -o /boot/grub/grub.cfg
Reboot and I booted in a Wayland Session.
-#####-
Should I still change it to
GRUB boot loader configuration
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=“Manjaro”
GRUB_CMDLINE_LINUX_DEFAULT=“quiet splash udev.log_priority=3”
GRUB_CMDLINE_LINUX=“nvidia_drm.fbdev=1” to
“nvidia_drm.fbdev=1 nvidia_drm.modeset=1”
???
and
/etc/mkinitcpio.conf
MODULES=(nvidia_drm) to MODULES=
to
(nvidia nvidia_modeset nvidia_uvm nvidia_drm)
I have not tried to start in X11 becuase wayland functions for now.
Da steht ja, unter der Titelleiste:
“Bildschirm zum teilen mit der anfragenden Anwendung auswählen”
Meine Frage daraufhin wäre:
Welche Anwendung würde denn das Bildschirmteilen anfragen?
… irgendwas Wayland spezifisches, was automatisch gestartet wird?
Außerdem is da unten eine Checkbox (die ist auf englisch):
Allow restoring on future settings.
Vielleicht mal dieses Häkchen entfernen?
the essence in english:
re the screenshot
“Bildschirm zum teilen mit der anfragenden Anwendung auswählen”
means:
“choose the screen to share with the requesting application”
and I suggested to ask:
what application would request to share and why?
Remove/uninstall the version of tvbrowser that you downloaded from their site, then delete/rename your ~/.config/tvbrowser folder, and then install the version that is in the AUR (pamac build tvbrowser): AUR (en) - tvbrowser
I just installed it on my Plasma Wayland machine and had no issues opening it and downloading an Australian TV Guide:
I can’t guarantee that will get rid of the screen-sharing popups (they could be related to having multiple video outputs & having to choose the correct screen for Wayland to display the application on), but using the version in the AUR will at least ensure that you have the correct dependencies for an Arch-based distro such as Manjaro.
When this is all you are concerned about then simply stay logging in X11 until this is solved or is there any disadvantage for you to use X11? Wayland on Plasma is still immature in some belongings and it’s no shame to stay on X11 until it’s fixed.
