@mpdesouza Yeah, it looks like awesome tool so it is a shame. Like something less involved than full subscription to a new subsystem ML.

Lately I helped a bit with tracing subsystem in Linux but otherwise it is not what I'm working on so in that sort of scenario lei would probably help somewhat...

@itaru @LWN For Linux kernel it is best thing to get bird eye view "what has been going on past week".. With the amount of traffic at LKML would be practically impossible to keep track of everything that way. So it is a necessity to exist, not just valuable :-)

Does not recognize any of the lei commands tho (tried ls-search, edit-search and up).

Took the symlink install route:

git clone https://public-inbox.org/public-inbox.git && cd public-inbox
perl Makefile.PL
make symlink-install prefix=$HOME/.local

There’s a spec file in OBS but no official package to this date (b4 has an official package).

@Aissen @liw clippy with all and pedantic for every commit.

Is there off-the-shelf OpenSUSE RPM package of local email interface (lei)?

I also tried to seek for the source code but it is not available here: https://git.kernel.org/pub/scm/utils

After trial and error (earlier post), I’ve found out that only three steps that are required to migrate SDDM/KDE to a Wayland-only system in OpenSUSE Tumbleweed:

# systemctl disable xdm.service
# systemctl enable sddm.service
# cat > /etc/sddm.conf.d/10-display-server.conf << EOF
[General]
DisplayServer=wayland

[Wayland]
CompositorCommand=kwin_wayland --drm --no-global-shortcuts --no-lockscreen --locale1
EOF

End result:

$ pstree `pidof sddm`
sddm─┬─sddm-helper───startplasma-way───{startplasma-way}
     └─{sddm}

Also sanity-checked ps aux | grep -i xorg. Makes sense now that I know the steps but was pretty hard to find the correct steps because did not really know what I was doing :-) The default value for DisplayServer is x11 and then default value for CompositorCommand is weston. Thus both need to be updated.

#OpenSUSE #Wayland #KDE

@Conan_Kudo @fedora that utpm error is weird and does not report where it tries access the accounting db so i just ignore it for now :-) no idea how to tackle the problem right now

@Conan_Kudo @fedora Deleted my own config. It seems to use /usr/lib/sddm/sddm.conf.d/11-kwin_wayland.conf as long as sddm.service is enabled instead of xdm.service.

@Conan_Kudo @fedora

With trial and error I got OpenSUSE working with only Wayland. I did first:

$ sudo systemctl disable xdm.service
$ sudo systemctl enable sddm.service

And created a config file:

$ cat /etc/sddm.conf.d/wayland.conf 
[General]
DisplayServer=wayland
GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell

[Wayland]
EnableHiDPI=true

Only glitch I see is in systemctl status sddm:

Apr 01 17:58:05 suppilovahvero sddm-helper[2368]: Failed to write utmpx:  No such file or directory

Not sure what kind of side-effects that might have…

@Conan_Kudo @fedora Actually in my running session also:

$ echo $WINDOWMANAGER 
/usr/bin/startplasma-x11

I’d expect it to be different within the session, does not feel aligned with the value of XGD_SESSION_TYPE but I don’t have deep knowledge of their semantics so I guess I’m lacking some knowledge.

@Conan_Kudo @fedora

Right:

$ sudo cat /proc/2975/environ | tr '\0' '\n'                        
PIDFILE=/run/sddm.pid
PWD=/
SYSTEMD_EXEC_PID=2940
LANG=en_US.UTF-8
INVOCATION_ID=6e2dee533d9f4aab932067246e07ffa8
USER=root
SHLVL=1
WINDOWMANAGER=/usr/bin/startplasma-x11
JOURNAL_STREAM=8:16977
XDG_DATA_DIRS=/var/lib/flatpak/exports/share:/usr/local/share/:/usr/share/
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
_=/usr/sbin/startproc
PREVLEVEL=N
RUNLEVEL=?
DAEMON=/usr/bin/sddm

However:

$
 echo $XDG_SESSION_TYPE 
wayland

So I guess I have two instances of Plasma running, one for SDDM and other for the running session, i.e. the GUI selector for windows manager does nothing the to SDDM itself.

@orva I recall seeing in Ubuntu xwayland process as xwayland not xorg but could be wrong because do not have Ubuntu installation available to check :-) And if I recall correctly it should be child process of wayland...

If I interpret this correctly the desktop is running on top of Wayland. Just wondering the purpose of xorg instances.

Do not understand this:

$ pstree `pidof sddm`
sddm─┬─Xorg.bin───7*[{Xorg.bin}]
     ├─sddm-helper───startplasma-way───{startplasma-way}
     └─{sddm}

I did select wayland session, do not understand what those xorg instances are for…

it is sometimes pretty weird how almost any problem you have at, then you post about, and instead of measured arguments, you get stuff like "blame capitalism" for that.

it is a huge society issue in modern society really. blame something big instead of fixing the issue and call it a day.

i mean it never helps fixing the leak, even if it if the big bad venture capitalist or whatever is your dystopian monster made it possible.

Probably also something incorrectly configured in permissions because of this transcript from strace -Z -e trace=openat zypper se qemu-s390x > /dev/null show below the paragraph. (qemu-s390x is a randomly picked keyword). I AB tested with “sudo” version and this is the difference.

openat(AT_FDCWD, "/var/cache/zypp/raw/download.opensuse.org-non-oss/cookie", O_RDONLY) = -1 EACCES (Permission denied)
Error retrieving metadata for 'Main Repository (NON-OSS)':
Can't create metadata cache directory.
Problem loading data from 'Main Repository (NON-OSS)'
openat(AT_FDCWD, "/var/cache/zypp/raw/download.opensuse.org-oss/cookie", O_RDONLY) = -1 EACCES (Permission denied)
Error retrieving metadata for 'Main Repository (OSS)':
Can't create metadata cache directory.
Problem loading data from 'Main Repository (OSS)'
openat(AT_FDCWD, "/var/cache/zypp/raw/download.opensuse.org-tumbleweed/cookie", O_RDONLY) = -1 EACCES (Permission denied)
Error retrieving metadata for 'Main Update Repository':
Can't create metadata cache directory.
Problem loading data from 'Main Update Repository'
openat(AT_FDCWD, "/usr/lib/sysimage/rpm/Index.db", O_RDWR) = -1 EACCES (Permission denied)
openat(AT_FDCWD, "/sys/kernel/tracing", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 EACCES (Permission denied)
openat(AT_FDCWD, "/sys/kernel/debug", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 EACCES (Permission denied)
openat(AT_FDCWD, "/sys/fs/pstore", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 EACCES (Permission denied)
openat(AT_FDCWD, "/sys/fs/bpf", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 EACCES (Permission denied)
openat(AT_FDCWD, "/sys/fs/fuse/connections/84", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 EACCES (Permission denied)
openat(AT_FDCWD, "/sys/fs/fuse/connections/78", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 EACCES (Permission denied)
openat(AT_FDCWD, "/var/lib/zypp/LastDistributionFlavor", O_WRONLY|O_CREAT|O_TRUNC, 0666) = -1 EACCES (Permission denied)
+++ exited with 0 +++

This other issue is something that I’ve yet to find a reason:

$ zypper se qemu-s390x
Repository 'Main Repository (NON-OSS)' is out-of-date. You can run 'zypper refresh' as root to update it.
Repository 'Main Repository (OSS)' is out-of-date. You can run 'zypper refresh' as root to update it.
Repository 'Main Update Repository' is out-of-date. You can run 'zypper refresh' as root to update it.
Repository 'Open H.264 Codec (openSUSE Tumbleweed)' is out-of-date. You can run 'zypper refresh' as root to update it.
Repository 'Sublime Text - x86_64 - Stable' is out-of-date. You can run 'zypper refresh' as root to update it.
Loading repository data...
Retrieving repository 'Main Repository (NON-OSS)' data...
Error retrieving metadata for 'Main Repository (NON-OSS)':
Can't create metadata cache directory.
Problem loading data from 'Main Repository (NON-OSS)'
Warning: Repository 'Main Repository (NON-OSS)' could not be refreshed. Using old cache.
Retrieving repository 'Main Repository (OSS)' data...
Error retrieving metadata for 'Main Repository (OSS)':
Can't create metadata cache directory.
Problem loading data from 'Main Repository (OSS)'
Warning: Repository 'Main Repository (OSS)' could not be refreshed. Using old cache.
Retrieving repository 'Main Update Repository' data...
Error retrieving metadata for 'Main Update Repository':
Can't create metadata cache directory.
Problem loading data from 'Main Update Repository'
Warning: Repository 'Main Update Repository' could not be refreshed. Using old cache.
Reading installed packages...

S | Name       | Summary                                                  | Type
--+------------+----------------------------------------------------------+--------
  | qemu-s390x | Machine emulator and virtualizer for S/390 architectures | package

~ on  main 
$ sudo zypper se qemu-s390x
Loading repository data...
Reading installed packages...

S | Name       | Summary                                                  | Type
--+------------+----------------------------------------------------------+--------
  | qemu-s390x | Machine emulator and virtualizer for S/390 architectures | package

my favorite tool for working with #polyend #tracker: #discodsp bliss 2. it is almost like instrument editor for polyend tracker because it comes also with standalone version.
i.e. it allows to do in minutes:

key-mapped multisample along the lines of https://www.youtube.com/watch?v=bn4vPrTU9js
e.g. octave interval multisample and use multiple sample slots and instrument number to pick the octave.

if polyend published PTI specification fully then tools such as bliss could easily implement direct export for it. it would be win-win for the ecosystem and the company...
without open specs for file format it is a bit fake to use terms such as "tracker scene" in the advertisements. actually it is not a bit fake, it is fake literally.

Tried to login to bugzilla but had some account issue so waiting for that before moving forward.

With 022 umask:

$ sudo sudo bootctl --make-machine-id-directory=yes install
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/efi/EFI/systemd/systemd-bootx64.efi".
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/efi/EFI/BOOT/BOOTX64.EFI".
⚠ Mount point '/boot/efi' which backs the random seed file is world accessible, which is a security hole! ⚠
⚠ Random seed file '/boot/efi/loader/random-seed' is world accessible, which is a security hole! ⚠
Random seed file /boot/efi/loader/random-seed successfully refreshed (32 bytes).
Created EFI boot entry "Linux Boot Manager".

With 077 umask:

Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/efi/EFI/systemd/systemd-bootx64.efi".
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/efi/EFI/BOOT/BOOTX64.EFI".
Random seed file /boot/efi/loader/random-seed successfully refreshed (32 bytes).
Created EFI boot entry "Linux Boot Manager".