Hi, everyone! I upgraded from Leap 15.3 to Leap 15.4 yesterday (actually, from Linux Kamarada 15.3, which is Leap-based, to Leap 15.4) following the same upgrade procedure I'm used to years now: https://linuxkamarada.com/en/2021/12/23/linux-kamarada-and-opensuse-leap-how... (of course, I replaced 15.3 by 15.4, for it to work) https://en.opensuse.org/SDB:System_upgrade Now I'm not able to log in to the graphical interface as usual. Plymouth stops spinning, GDM should appear next, but it doesn't. The only thing I'm able to do is switch to the first terminal (Ctrl + Alt + F1) and reboot using Ctrl + Alt + Del. I'm not even able to log in to the terminal, if I don't change the kernel. Back to GRUB, if I enter the advanced options and select the recovery mode of the 5.14.21-150400.22-default kernel (the one from the Main repo, not the Update repo), at least I'm able to switch to the first terminal (Ctrl + Alt + F1), log in to the terminal and do: $ startx Then I have a fully functional GNOME desktop. Inspecting /var/log/messages, I found the following that caught my attention, I'm not sure it is related to the problem: 2022-08-18T00:53:01.675443-03:00 kamarada-pc /usr/lib/gdm/gdm-x-session[4082]: #011(WW) warning, (EE) error, (NI) not implemented, (??) unknown. 2022-08-18T00:53:01.794755-03:00 kamarada-pc /usr/lib/gdm/gdm-x-session[4153]: > Internal error: Could not resolve keysym XF86WWAN 2022-08-18T00:53:01.794810-03:00 kamarada-pc /usr/lib/gdm/gdm-x-session[4153]: > Internal error: Could not resolve keysym XF86RFKill 2022-08-18T00:53:01.837606-03:00 kamarada-pc /usr/lib/gdm/gdm-x-session[4183]: > Internal error: Could not resolve keysym XF86WWAN 2022-08-18T00:53:01.837667-03:00 kamarada-pc /usr/lib/gdm/gdm-x-session[4183]: > Internal error: Could not resolve keysym XF86RFKill 2022-08-18T00:53:02.122276-03:00 kamarada-pc gnome-session[4211]: gnome-session-binary[4211]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed 2022-08-18T00:53:02.122366-03:00 kamarada-pc gnome-session[4211]: gnome-session-binary[4211]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed 2022-08-18T00:53:02.122442-03:00 kamarada-pc gnome-session-binary[4211]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed 2022-08-18T00:53:02.122491-03:00 kamarada-pc gnome-session-binary[4211]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Does anyone have any idea on what's going on and/or how it can be solved? Thanks! Antonio The Linux Kamarada Project https://linuxkamarada.com/
Hello, In the Message; Subject : Leap 15.4 - GDM won't start Message-ID : <CAGiRJVKySm4UOmX_-rL5SdX+vN9DT=YgWozj_z-OgmmXyATkSQ@mail.gmail.com> Date & Time: Thu, 18 Aug 2022 10:09:04 -0300 Linux Kamarada <linuxkamarada@gmail.com> has written: [...]
Now I'm not able to log in to the graphical interface as usual. Plymouth stops spinning, GDM should appear next, but it doesn't. [...] Inspecting /var/log/messages, I found the following that caught my attention, I'm not sure it is related to the problem:
2022-08-18T00:53:01.675443-03:00 kamarada-pc /usr/lib/gdm/gdm-x-session[4082]: #011(WW) warning, (EE) error, (NI) not implemented, (??) unknown. 2022-08-18T00:53:01.794755-03:00 kamarada-pc /usr/lib/gdm/gdm-x-session[4153]: > Internal error: Could not resolve keysym XF86WWAN 2022-08-18T00:53:01.794810-03:00 kamarada-pc /usr/lib/gdm/gdm-x-session[4153]: > Internal error: Could not resolve keysym XF86RFKill 2022-08-18T00:53:01.837606-03:00 kamarada-pc /usr/lib/gdm/gdm-x-session[4183]: > Internal error: Could not resolve keysym XF86WWAN 2022-08-18T00:53:01.837667-03:00 kamarada-pc /usr/lib/gdm/gdm-x-session[4183]: > Internal error: Could not resolve keysym XF86RFKill [...]
You have to make other changes to .xinitrc, not just adding. Should all be covered in the wiki. Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Tim Cook, the C.E.O. of Apple, said earlier this year that he would not let his nephew join social networks. Bill Gates banned cellphone until his children were teenagers, and Melinda Gates wrote that she wished they had waited even longer. Steve Jobs would not let his young children near iPads." -- The New York Times --
On Thu, Aug 18, 2022 at 10:39 PM Masaru Nomiya <nomiya@galaxy.dti.ne.jp> wrote:
You have to make other changes to .xinitrc, not just adding. Should all be covered in the wiki.
I don't believe there is a problem with my ~/.xinitrc, because GDM does not start. The problem occurs before I log in with my user. It seems to be system-wide, not user-specific. I booted with Leap 15.4 GNOME Live and compared its /etc/X11/xinit folder with mine. The xinitrc scripts were identical. I removed from my installation some packages that added files to the xinitrc.d folder (Cadence and virtualbox-guest-x11), but that didn't change the described behavior. What I did next: I set up my repos exactly the same as the Live system, did a zypper up (that updated the kernel), installed LightDM and changed the default display manager, according to: https://en.opensuse.org/SDB:Change_Display_Manager Now, LightDM also does not start, but tty1 (Ctrl + Alt + F1) shows the login prompt faster. I'm able to get to GNOME the same way I described before, but I'm not able to lock the screen, since I'm not using GDM. I thought about giving SDDM a try, but that would cause a lot of KDE and Qt packages to be installed. I prefer to try another thing first. Antonio The Linux Kamarada Project https://linuxkamarada.com/
On Thu, Sep 1, 2022 at 9:51 AM Linux Kamarada <linuxkamarada@gmail.com> wrote:
Now, LightDM also does not start, but tty1 (Ctrl + Alt + F1) shows the login prompt faster. I'm able to get to GNOME the same way I described before, but I'm not able to lock the screen, since I'm not using GDM.
Now I realized that the Live system uses Wayland, while my system uses X11. Maybe is that? How can I enable Wayland by default? I installed the xwayland and gnome-session-wayland packages, but that didn't change the described behavior as well (LightDM does not start). Is there anything else I need to do? I'm able to start GNOME Wayland with: $ dbus-run-session -- gnome-shell --display-server --wayland (source: https://stackoverflow.com/a/38546347) Some things are strange (i.e. some settings were lost, e.g. I had to login to Chrome again) but the system is working somehow. Antonio The Linux Kamarada Project https://linuxkamarada.com/
On 01.09.2022 16:49, Linux Kamarada wrote:
On Thu, Sep 1, 2022 at 9:51 AM Linux Kamarada <linuxkamarada@gmail.com> wrote:
Now, LightDM also does not start, but tty1 (Ctrl + Alt + F1) shows the login prompt faster. I'm able to get to GNOME the same way I described before, but I'm not able to lock the screen, since I'm not using GDM.
Now I realized that the Live system uses Wayland, while my system uses X11. Maybe is that?
Reboot and provide full output of "journalctl -b" (upload to https://susepaste.org).
How can I enable Wayland by default?
I installed the xwayland and gnome-session-wayland packages, but that didn't change the described behavior as well (LightDM does not start). Is there anything else I need to do?
I'm able to start GNOME Wayland with:
$ dbus-run-session -- gnome-shell --display-server --wayland
(source: https://stackoverflow.com/a/38546347)
Some things are strange (i.e. some settings were lost, e.g. I had to login to Chrome again) but the system is working somehow.
Antonio The Linux Kamarada Project https://linuxkamarada.com/
On Thu, Sep 1, 2022 at 1:27 PM Andrei Borzenkov <arvidjaar@gmail.com> wrote:
On 01.09.2022 16:49, Linux Kamarada wrote:
On Thu, Sep 1, 2022 at 9:51 AM Linux Kamarada <linuxkamarada@gmail.com> wrote:
Now, LightDM also does not start, but tty1 (Ctrl + Alt + F1) shows the login prompt faster. I'm able to get to GNOME the same way I described before, but I'm not able to lock the screen, since I'm not using GDM.
Now I realized that the Live system uses Wayland, while my system uses X11. Maybe is that?
Reboot and provide full output of "journalctl -b" (upload to https://susepaste.org).
Here it is: https://susepaste.org/22200178 Also, I'm not sure that helps, I did the same after booting from the Leap 15.4 GNOME Live: https://susepaste.org/9526612 Maybe it's useful for comparison. In both cases, after I got to the GNOME desktop, I opened the Terminal, logged in as root (su) and ran: # journalctl -b > journal Antonio The Linux Kamarada Project https://linuxkamarada.com/
On 01.09.2022 22:17, Linux Kamarada wrote:
On Thu, Sep 1, 2022 at 1:27 PM Andrei Borzenkov <arvidjaar@gmail.com> wrote:
On 01.09.2022 16:49, Linux Kamarada wrote:
On Thu, Sep 1, 2022 at 9:51 AM Linux Kamarada <linuxkamarada@gmail.com> wrote:
Now, LightDM also does not start, but tty1 (Ctrl + Alt + F1) shows the login prompt faster. I'm able to get to GNOME the same way I described before, but I'm not able to lock the screen, since I'm not using GDM.
Now I realized that the Live system uses Wayland, while my system uses X11. Maybe is that?
Reboot and provide full output of "journalctl -b" (upload to https://susepaste.org).
Here it is: https://susepaste.org/22200178
set 01 16:00:59 kamarada-pc display-manager[3732]: Starting service lightdm..done ... set 01 16:01:00 kamarada-pc display-manager[4036]: Failed to get information on user lightdm: Success set 01 16:01:00 kamarada-pc systemd[1]: display-manager.service: Main process exited, code=exited, status=1/FAILURE If user lightdm exists, the problem could be in accounts service; set 01 16:00:59 kamarada-pc dbus-daemon[3011]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service' requested by ':1.19' (uid=0 pid=3844 comm="/usr/sbin/lightdm ") set 01 16:00:59 kamarada-pc systemd[1]: Starting Accounts Service... set 01 16:00:59 kamarada-pc accounts-daemon[3854]: started daemon version 0.6.55 set 01 16:00:59 kamarada-pc dbus-daemon[3011]: [system] Successfully activated service 'org.freedesktop.Accounts' set 01 16:00:59 kamarada-pc accounts-daemon[3854]: g_dbus_interface_skeleton_get_object_path: assertion 'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed I do not have this last error on Leap 15.4. bor@10:~> rpm -qf /usr/lib/accounts-daemon accountsservice-0.6.55-150400.12.8.x86_64 bor@10:~>
Also, I'm not sure that helps, I did the same after booting from the Leap 15.4 GNOME Live:
Maybe it's useful for comparison.
Well, here accounts service starts without errors.
In both cases, after I got to the GNOME desktop, I opened the Terminal, logged in as root (su) and ran:
# journalctl -b > journal
Antonio The Linux Kamarada Project https://linuxkamarada.com/
On Fri, Sep 2, 2022 at 1:07 AM Andrei Borzenkov <arvidjaar@gmail.com> wrote:
If user lightdm exists, the problem could be in accounts service;
set 01 16:00:59 kamarada-pc dbus-daemon[3011]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service' requested by ':1.19' (uid=0 pid=3844 comm="/usr/sbin/lightdm ") set 01 16:00:59 kamarada-pc systemd[1]: Starting Accounts Service... set 01 16:00:59 kamarada-pc accounts-daemon[3854]: started daemon version 0.6.55 set 01 16:00:59 kamarada-pc dbus-daemon[3011]: [system] Successfully activated service 'org.freedesktop.Accounts' set 01 16:00:59 kamarada-pc accounts-daemon[3854]: g_dbus_interface_skeleton_get_object_path: assertion 'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed
I do not have this last error on Leap 15.4.
In fact: # systemctl status accounts-daemon.service ● accounts-daemon.service - Accounts Service Loaded: loaded (/usr/lib/systemd/system/accounts-daemon.service; disabled; vendor preset: disabled) Active: active (running) since Wed 2022-09-07 09:31:35 -03; 12min ago Main PID: 1594 (accounts-daemon) Tasks: 3 (limit: 4915) CGroup: /system.slice/accounts-daemon.service └─ 1594 /usr/lib/accounts-daemon set 07 09:31:35 kamarada-pc systemd[1]: Starting Accounts Service... set 07 09:31:35 kamarada-pc accounts-daemon[1594]: started daemon version 0.6.55 set 07 09:31:35 kamarada-pc systemd[1]: Started Accounts Service. set 07 09:31:35 kamarada-pc accounts-daemon[1594]: g_dbus_interface_skeleton_get_object_path: assertion 'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed This last error doesn't occur when I boot from the Live system. The service is disabled on my system, I thought that could be a problem, but it's also disabled on the Live system.
bor@10:~> rpm -qf /usr/lib/accounts-daemon accountsservice-0.6.55-150400.12.8.x86_64 bor@10:~>
This command outputs the same result on my system (we have the same versions of this package installed). Antonio The Linux Kamarada Project https://linuxkamarada.com/
On Fri, Sep 2, 2022 at 1:07 AM Andrei Borzenkov <arvidjaar@gmail.com> wrote:
If user lightdm exists, the problem could be in accounts service;
I realized that the lightdm user was not created while installing the lightdm package. $ id lightdm id: 'lightdm': no such user So I created a lightdm user myself: # useradd -c "LightDM daemon" -d /var/lib/lightdm -r -s /bin/false -U lightdm (not sure it should be done this way, but I believe so) But, after rebooting, the problem remains.
set 01 16:00:59 kamarada-pc dbus-daemon[3011]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service' requested by ':1.19' (uid=0 pid=3844 comm="/usr/sbin/lightdm ") set 01 16:00:59 kamarada-pc systemd[1]: Starting Accounts Service... set 01 16:00:59 kamarada-pc accounts-daemon[3854]: started daemon version 0.6.55 set 01 16:00:59 kamarada-pc dbus-daemon[3011]: [system] Successfully activated service 'org.freedesktop.Accounts' set 01 16:00:59 kamarada-pc accounts-daemon[3854]: g_dbus_interface_skeleton_get_object_path: assertion 'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed
I do not have this last error on Leap 15.4.
I found this Tumbleweed bug: https://bugzilla.opensuse.org/show_bug.cgi?id=1181243 I commented on it pointing to this thread. Antonio The Linux Kamarada Project https://linuxkamarada.com/
Hello, You seem to have been DM'd by me, but the address I use for Mailing List is for Miling List only, because there is too much spam, and all mails from non-Mailing List are set to be sent to /dev/null. Please understand this. Anyway. In the Message; Subject : Re: Leap 15.4 - display manager won't start (it was: GDM won't start) Message-ID : <CAGiRJVLm-kdAEwnJTXDimx8ZgMKJ0ptEwuFrXYZrtyVs1spAOw@mail.gmail.com> Date & Time: Thu, 1 Sep 2022 10:49:36 -0300 [LK] == Linux Kamarada <linuxkamarada@gmail.com> has written: LK> On Thu, Sep 1, 2022 at 9:51 AM Linux Kamarada <linuxkamarada@gmail.com> wrote: LK> > LK> > Now, LightDM also does not start, but tty1 (Ctrl + Alt + F1) shows the LK> > login prompt faster. I'm able to get to GNOME the same way I described LK> > before, but I'm not able to lock the screen, since I'm not using GDM. LK> > LK> Now I realized that the Live system uses Wayland, while my system uses LK> X11. Maybe is that? LK> How can I enable Wayland by default? Which video card are you using? Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "A bachelor’s degree still holds prestige as a ticket to the middle class, but its value has received increasing scrutiny. In the last several years, rising tuition and student loan debt have led more Americans to reconsider an investment in postsecondary education." -- Washington Post --
On Fri, Sep 2, 2022 at 1:38 AM Masaru Nomiya <nomiya@galaxy.dti.ne.jp> wrote:
LK> How can I enable Wayland by default?
Which video card are you using?
TL;DR Intel HD Graphics 5500 Full answer: I followed this: https://www.howtogeek.com/508993/how-to-check-which-gpu-is-installed-on-linu... And I got: # lshw -numeric -C display *-display description: VGA compatible controller product: HD Graphics 5500 [8086:1616] vendor: Intel Corporation [8086] physical id: 2 bus info: pci@0000:00:02.0 logical name: /dev/fb0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom fb configuration: depth=32 driver=i915 latency=0 resolution=1366,768 resources: irq:47 memory:c0000000-c0ffffff memory:b0000000-bfffffff ioport:4000(size=64) memory:c0000-dffff (same output on both installed and Live system, but on the Live system I had to install lshw) Curiously, if I go to the GNOME Settings app, from my installed system, it shows my GPU model as: llvmpipe (LLVM 11.0.1, 256 bits) Screenshot: https://paste.opensuse.org/37248211 From the Live system, I get the actual GPU model: Mesa Intel® HD Graphics 5500 (BDW GT2) Screenshot: https://paste.opensuse.org/38787654 Antonio The Linux Kamarada Project https://linuxkamarada.com/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2022-08-18 at 10:09 -0300, Linux Kamarada wrote:
Hi, everyone!
I upgraded from Leap 15.3 to Leap 15.4 yesterday (actually, from Linux Kamarada 15.3, which is Leap-based, to Leap 15.4) following the same upgrade procedure I'm used to years now:
https://linuxkamarada.com/en/2021/12/23/linux-kamarada-and-opensuse-leap-how... (of course, I replaced 15.3 by 15.4, for it to work)
Hum. I'm not familiar with Linux Kamarada, I don't know what differences there might be. So I would like to know first your repository list; run: zypper lr --details > somefile.txt and attach the resulting "somefile.txt" file to your reply. Please do not paste the text to the email, the lines wrap are and become very difficult to read. Also, run this concoction: rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist \ | egrep -v "openSUSE Leap 15\.4|openSUSE_Leap_15.4|\-lp153|SUSE Linux Enterprise 15" | less -S I don't have 15.4, so I'm guessing the filters: you may have to adjust them yourself. The idea is to get a list of packages that don't belong to 15.4. If the list is small, you can attach the file; if it is long, upload to susepaste. Or, don't upload if you figure out from that text what you have to do ;-) You also said:
I booted with Leap 15.4 GNOME Live and compared its /etc/X11/xinit folder with mine. The xinitrc scripts were identical. I removed from my installation some packages that added files to the xinitrc.d folder (Cadence and virtualbox-guest-x11), but that didn't change the described behavior.
Are you running this machine as a virtual machine? - -- Cheers, Carlos E. R. (from openSUSE 15.3 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYxEHCxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVaCYAnRa/Nx05wPXSb2wedwX0 JruG0thSAJ4tR19m/PuVwuX98QmK/RN+zj57ww== =D7qp -----END PGP SIGNATURE-----
On Thu, Sep 1, 2022 at 4:25 PM Carlos E. R. <robin.listas@telefonica.net> wrote:
I'm not familiar with Linux Kamarada, I don't know what differences there might be. So I would like to know first your repository list; run:
Please note that Linux Kamarada 15.4 is not out (yet). So I upgraded from Linux Kamarada 15.3 to openSUSE Leap 15.4. That's possible because Linux Kamarada 15.3 is based on openSUSE Leap 15.3 (hence the same version numbers).
zypper lr --details > somefile.txt
TL;DR My repos are: Leap 15.4 defaults (same as Live system) + Packman + Kamarada 15.4 Dev Full answer: https://paste.opensuse.org/8252643
Also, run this concoction:
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist \ | egrep -v "openSUSE Leap 15\.4|openSUSE_Leap_15.4|\-lp153|SUSE Linux Enterprise 15" | less -S
I don't have 15.4, so I'm guessing the filters: you may have to adjust them yourself.
I just changed the less -S part to output the result to a text file: $ rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist \ | egrep -v "openSUSE Leap 15\.4|openSUSE_Leap_15.4|\-lp153|SUSE Linux Enterprise 15" > concoction.txt Here is the output: https://gist.github.com/vinyanalista/c228cfb99a3b741cfd152c0929965d95 (I had to use GitHub Gist because openSUSE Past said I was a spammer)
You also said:
I booted with Leap 15.4 GNOME Live and compared its /etc/X11/xinit folder with mine. The xinitrc scripts were identical. I removed from my installation some packages that added files to the xinitrc.d folder (Cadence and virtualbox-guest-x11), but that didn't change the described behavior.
Are you running this machine as a virtual machine?
No. In this thread, everytime I refer to the Live system it's one I boot using Ventoy, as described here: https://linuxkamarada.com/en/2020/07/29/ventoy-create-a-multiboot-usb-drive-... Antonio The Linux Kamarada Project https://linuxkamarada.com/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2022-09-07 a las 06:48 -0400, Linux Kamarada escribió:
On Thu, Sep 1, 2022 at 4:25 PM Carlos E. R. <robin.listas@telefonica.net> wrote:
I'm not familiar with Linux Kamarada, I don't know what differences there might be. So I would like to know first your repository list; run:
Please note that Linux Kamarada 15.4 is not out (yet). So I upgraded from Linux Kamarada 15.3 to openSUSE Leap 15.4. That's possible because Linux Kamarada 15.3 is based on openSUSE Leap 15.3 (hence the same version numbers).
zypper lr --details > somefile.txt
TL;DR My repos are: Leap 15.4 defaults (same as Live system) + Packman + Kamarada 15.4 Dev
Full answer: https://paste.opensuse.org/8252643
It seems ok, except this message on top I don't know about: Warning: The /etc/products.d/baseproduct symlink is dangling or missing! The link must point to your core products .prod file in /etc/products.d.
Also, run this concoction:
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist \ | egrep -v "openSUSE Leap 15\.4|openSUSE_Leap_15.4|\-lp153|SUSE Linux Enterprise 15" | less -S
I don't have 15.4, so I'm guessing the filters: you may have to adjust them yourself.
I just changed the less -S part to output the result to a text file:
:-) There is a file already included in the concoction, named "rpmlist", but it is the entire unfiltered rpm list.
$ rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist \ | egrep -v "openSUSE Leap 15\.4|openSUSE_Leap_15.4|\-lp153|SUSE Linux Enterprise 15" > concoction.txt
Here is the output: https://gist.github.com/vinyanalista/c228cfb99a3b741cfd152c0929965d95
(I had to use GitHub Gist because openSUSE Past said I was a spammer)
Heh! :-} Well, these are the "true" "obsolete" entries: ter nov 17 2020 dom nov 01 2020 libsecp256k1-0 20200615-lp152.1.2 x86_64 obs://build.opensuse.org/home:kamarada (none) == home:kamarada:15.2:dev / openSUSE_Leap_15.2 (none) ter nov 17 2020 dom nov 01 2020 libx265-192 3.4-pm152.1.2 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_Leap_15.2 (none) sex jan 15 2021 dom mar 22 2020 dissenter-browser 1.5.114-1 x86_64 Gab AI IncGab AI Inc <support@dissenter.com> == (none) (none) seg jan 25 2021 ter nov 10 2020 libvpx6 1.9.0-lp152.121.1 x86_64 obs://build.opensuse.org/network (none) == network:im:signal / openSUSE_Leap_15.2 (none) qui fev 11 2021 ter fev 02 2021 bisq 1.5.5-1 x86_64 Bisq (none) == (none) (none) qua fev 17 2021 sáb fev 06 2021 signal-desktop 1.39.6-lp152.1.4 x86_64 obs://build.opensuse.org/network (none) == network:im:signal / openSUSE_Leap_15.2 (none) dom fev 28 2021 sex fev 26 2021 hugo-bash-completion 0.81.0-lp152.11.3 noarch obs://build.opensuse.org/devel:languages:go (none) == devel:languages:go / openSUSE_Leap_15.2 (none) dom fev 28 2021 sex fev 26 2021 hugo 0.81.0-lp152.11.3 x86_64 obs://build.opensuse.org/devel:languages:go (none) == devel:languages:go / openSUSE_Leap_15.2 (none) qui mar 04 2021 qui jan 28 2021 megasync 4.4.0-1.1 x86_64 MEGA LimitedMEGA Linux Team <linux@mega.co.nz> == (none) (none) qui mar 11 2021 qui jan 16 2020 gpg-pubkey f23c6aa3-5e208a55 (none) (none)multimedia OBS Project <multimedia@build.opensuse.org> == (none) (none) dom abr 25 2021 seg abr 12 2021 wsdd 0.6.4-lp152.12.1 noarch obs://build.opensuse.org/network (none) == network / openSUSE_Leap_15.2 (none) sáb ago 28 2021 ter ago 24 2021 jack_mixer 15.1-pm153.1.49 x86_64 http://packman.links2linux.de packman@links2linux.de == Multimedia / openSUSE_Leap_15.3 (none) qua dez 22 2021 qua dez 22 2021 pdfsam-basic 4.2.10-1 x86_64 obs://build.opensuse.org/home:kamarada (none) == home:kamarada:15.3:dev / openSUSE_Leap_15.3 (none) ter mar 22 2022 qua set 08 2021 lacuna-webpki 2.11.6-1 x86_64 Lacuna Software (none) == (none) (none) sex jun 17 2022 qua mai 18 2022 brave-keyring 1.10-1 noarch (none) (none) == (none) (none) qua ago 17 2022 qua ago 17 2022 brave-browser 1.42.97-1 x86_64 Brave Software, Inc.Brave Software <support@brave.com> == (none) (none) Some of them are from packman, thus easy to upgrade/replace/delete. I don't know if any of them can cause your problems.
You also said:
I booted with Leap 15.4 GNOME Live and compared its /etc/X11/xinit folder with mine. The xinitrc scripts were identical. I removed from my installation some packages that added files to the xinitrc.d folder (Cadence and virtualbox-guest-x11), but that didn't change the described behavior.
Are you running this machine as a virtual machine?
No. In this thread, everytime I refer to the Live system it's one I boot using Ventoy, as described here:
https://linuxkamarada.com/en/2020/07/29/ventoy-create-a-multiboot-usb-drive-...
Then why did you have virtualbox-guest-x11 installed? That might cause problems. - -- Cheers, Carlos E. R. (from openSUSE 15.3 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYxipDRwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVMsEAn0PrdD9uIEslno2oi6Wk fCAG3U6IAJ9o8rlS0W8XBuMJdLPCperqDNecVQ== =wd0R -----END PGP SIGNATURE-----
On Wed, Sep 7, 2022 at 11:23 AM Carlos E. R. <robin.listas@telefonica.net> wrote:
It seems ok, except this message on top I don't know about:
Warning: The /etc/products.d/baseproduct symlink is dangling or missing! The link must point to your core products .prod file in /etc/products.d.
Thanks for noticing. On the Leap 15.4 GNOME Live system that message does not appear. I've seen that /etc/products.d/baseproduct is a symlink to /etc/products.d/Leap.prod. Both files belong to the openSUSE-release package. Back to my system, I realized that, curiously, that package was installed. But /etc/products.d/baseproduct was a broken symbolic link to /etc/products.d/openSUSE.prod. I fixed it: # rm /etc/products.d/baseproduct # ln -s /etc/products.d/Leap.prod /etc/products.d/baseproduct And that message stopped appearing. But the main problem remains (display manager won't start).
Well, these are the "true" "obsolete" entries:
Some of them are from packman, thus easy to upgrade/replace/delete. I don't know if any of them can cause your problems.
From those packages, I removed what I could, rebooted, but the problem remains. Me too, I don't believe those packages are causing the problem.
Then why did you have virtualbox-guest-x11 installed? That might cause problems.
Linux Kamarada comes with it installed by default. It's to make the Live system work better with VirtualBox. If installed to a real machine (such as mine), it's safe to remove that package, but it should do no harm. Anyway, I removed it and nothing changed. Antonio The Linux Kamarada Project https://linuxkamarada.com/
Thanks to everyone who has tried to help me, but I thought it would be easier and faster to format my existing installation and do a fresh one. Now I'm using openSUSE Leap 15.4 with GNOME, GDM and Wayland and everything works fine. This bug is still open and received no reply after mine: https://bugzilla.opensuse.org/show_bug.cgi?id=1181243 See you! Antonio The Linux Kamarada Project https://linuxkamarada.com/
participants (4)
-
Andrei Borzenkov -
Carlos E. R. -
Linux Kamarada -
Masaru Nomiya