new 5.9 kernel boots to black screen with cursor showing but "crashed"?? 5.8 kernel is OK???

English Install/Boot/Login
#21

Folks:

So far looks like we don’t have a fix in the tubes yet?? Ran a zypper and still am getting:

Problem: mate-menu-20.04.1-2.1.noarch requires python3-xdg, but this requirement cannot be provided
  deleted providers: python3-pyxdg-0.26-6.2.noarch
not installable providers: python3-xdg-4.0.1-1.1.noarch[download.opensuse.org-oss]
 Solution 1: Following actions will be done:
  deinstallation of mate-menu-20.04.1-2.1.noarch
  deinstallation of mate-panel-branding-openSUSE-42.1-4.44.noarch
  deinstallation of mate-menu-lang-20.04.1-2.1.noarch
 Solution 2: deinstallation of python3-pyxdg-0.26-6.2.noarch
 Solution 3: keep obsolete python3-pyxdg-0.26-6.2.noarch
 Solution 4: break mate-menu-20.04.1-2.1.noarch by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/4/c/d/?] (c):
#22

This time when I choose #3 . . . “keep obsolete python package” . . . there are a bunch of “kernel-firmware” packages that are selected to be “downgraded” . . . which I think were just “upgraded” in the recent zyppering . . . ???

The other choices seem to be to “de-install mate-menu” or “break it” . . . nothing seems too attractive . . . . I’m thinking that “Gene_S” provided some data on a “bashrc”??? file, but that is beyond my skillset . . . basic zypper commands is about it for me in OpenSUSEville . . . .

Any thoughts as to easy “solution” to this query-gate stumbling block???

#23

Go ahead and keep the obsolete package. The firmware downgrade is unrelated. Look at https://forums.opensuse.org/showthread.php/547072-Puzzled-by-total-downgrade-of-all-kernel-firmware for information on that issue.

Gene

#24

@Gene_S:

Thanks for the post back . . . I did check that other thread and saw your “I don’t have suspend” comment . . . I use suspend, or try to, seems like there have been “revival from suspend” issues in several of my distros lately . . . but, what I do find “odd” is that I did run the “keep obsolete python” choice previously and it shows it and mesa-dri-nouveau as “locked” in the console after running zypper dup -l . . . but it still gave me this question again about “Pick one of these four choices” . . . ??? Why, why, why is this happening to me . . . ??? : - ))

But, thanks for letting me know that the “downgrade” isn’t related . . . I guess most of this isn’t too serious . . . upgrade . . . downgrade . . . all in a days work . . . but maybe I’ll wait a day or two to see if anything changes before running the downgrade . . . sort of goes against the grain in the “rolling” realm . . . we always want to be rolling “forward” . . . never backward . . . relentlessly forward . . . .

#25

What do you see when you run:


> sudo zypper locks

# | Name           | Type    | Repository
--+----------------+---------+-----------
1 | *lsp-plugins*  | package | (any)
2 | *pulseeffects* | package | (any)
3 | python3-pyxdg  | package | (any)

If python3-pyxdg is locked, I’m not sure why you still get those 4 suggestions. Maybe you could post them? They may be about something else.

Gene

#26

@Gene_S:

I’m away from that machine right now, so I’ll try that command in the AM, but post #21 I believe is from this morning’s zypper dup -l attempts showing the 4 options . . . seems to relate to “mate-menu” and “python3” as before . . . no question in my mind on that one . . . .

#27

@Gene_S:

So, back in TW main channel, so I ran your “locks” command, and then I ran the zypper selecting #3 “keep obsolete” and it did 333 upgrades, including the downgrades I didn’t want to do . . . .

And then I rebooted and I ran the commands again, so you can see that it again showed the 4 choices to choose again . . . but under that it shows “2 locked packages” even though in the zypper locks command it only shows the one as locked . . . .

Anyway, it still seems like there is a “dependency problem” but it isn’t interfering with GUI the way it is in my new laptop, the one that shows the black log in screen. I guess I made the wrong choice in the 4 decisions, but over in the older desktop I guess I went with “keep obsolete” and it just is Groundhog Day" all over again??

sudo zypper locks
[sudo] password for root: 

# | Name             | Type    | Repository
--+------------------+---------+-----------
1 | Mesa-dri-nouveau | package | (any)

butoh-mind@linux-f6nl:~> sudo zypper ref && sudo zypper dup -l
Repository 'Main Repository (NON-OSS)' is up to date.                           
Repository 'Main Repository (OSS)' is up to date.                               
Repository 'Main Update Repository' is up to date.                              
Repository 'libdvdcss' is up to date.                                           
Repository 'Packman Repository' is up to date.                                  
All repositories have been refreshed.
Loading repository data...
Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...

Problem: mate-menu-20.04.1-2.1.noarch requires python3-xdg, but this requirement cannot be provided
  deleted providers: python3-pyxdg-0.26-6.2.noarch
not installable providers: python3-xdg-4.0.1-1.1.noarch[download.opensuse.org-oss]
 Solution 1: Following actions will be done:
  deinstallation of mate-menu-20.04.1-2.1.noarch
  deinstallation of mate-panel-branding-openSUSE-42.1-4.44.noarch
  deinstallation of mate-menu-lang-20.04.1-2.1.noarch
 Solution 2: deinstallation of python3-pyxdg-0.26-6.2.noarch
 Solution 3: keep obsolete python3-pyxdg-0.26-6.2.noarch
 Solution 4: break mate-menu-20.04.1-2.1.noarch by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/4/c/d/?] (c): 3
Resolving dependencies...
Computing distribution upgrade...

The following 2 items are locked and will not be changed by any action:
 Available:
  Mesa-dri-nouveau
 Installed:
  python3-pyxdg

Nothing to do.
#28

Try this:


sudo zypper removelock python3-pyxdg

sudo zypper addlock python3-pyxdg

sudo zypper locks

You should now see a lock for python3-pyxdg. Then try the sudo zypper dup command.

Gene

#29

@Gene_S:

Thanks for those commands, I’ll check them out in a bit . . . from what you are suggesting it seems like we are at a “stalemate” on getting a solution to the problem, as the banana is getting tossed around and nobody is catching it???

#30

(RANT)
It appears that the OpenSUSE community does not support MATE desktop.

It would be fixed by now if they did. I am wondering if it is time to go to Ubuntu or Mint Linux as they support MATE native and not as one-click afterthought.

I dislike gnome 3 and kde - MATE is gnome 2 resurrected after being abandoned. I don’t like my linux desktop to look like a tablet or cell phone. I like the old “Windows XP” feel. I have converted over 100 people to OpenSUSE and MATE from windows 8, 8.1 and 10. I have gotten around the issue by allowing it to update and installing an old version via rpm so zypper does not complain.

Teamviewer thought I was commercial user and stopped me from connecting for more than 5 minutes - had to install anydesk - it works and I got most of my OpenSUSE MATE converts to install it so I can fix the MATE desktop issues.
(/RANT)

12 days and only MATE users have updated bugzilla with their me too’s.

https://bugzilla.opensuse.org/show_bug.cgi?id=1178323

#31

@larryr:

“I feel you,” as they say on the streets of LA . . . I also prefer MATE as my clean and simple DE . . . I had a number of MATE installs running in various platforms, including ubuntu-mate, which up until recently was doing a pretty good job of keeping the MATE DE up to snuff . . . but seemingly in 20.10 stuff started crashing, causing very slow boot times as the system “read through the crash reports”??? I finally gave up on it and install Debian Bullseye in that slot, running XFCE, tried and true, etc. So, point being, not sure if leaving OpenSUSE will be worth the time . . . years back an irritable guy on the main ubuntu forum said something like, "OpenSUSE is a newer stack and is my system of choice . . . " . . . he never explained what “newer stack” meant, but I assume it mean it was “stacked on newness” . . . whereas in the drive to become the number one system for all users I think ubuntu has become . . . what’s the best linux dig??? . . . “bloated”???

In this case it actually appears that it is the MATE devs who aren’t picking up the banana, according to the reply I got from the post I made in their forum . . . “not our problem,” and he closed the ticket . . . . After Gene_S posted his testing of the issue pointing toward mate-menu, I posted back to the thread . . . to wit, no response there . . . .

Linux is a “work in progress” . . . which is both the fun and the bane of it, I’m suggesting that rather than jumping from pan into fire . . . add another DE onto the OpenSUSE “stack of newness” . . . a lot quicker to log in and out of a DE than installing something that isn’t radically different . . . SUSE has a lot going for it, especially this forum which is quite active and responsive . . . . At some point in the nearing future, somebody at MATE will drink a cup of coffee, and make some mods and the problem will “just disappear.”

n_s

#32

Please don’t blame the MATE devs. Fedora has a very active MATE maintainer and I’ve always had quick turn around on distribution issues. This is definitely an Opensuse issue, not a MATE issue. I’m not sure how to escalate a response, but it’s obvious that KDE is the primary DE for Opensuse.

Gene

#33

@Gene_S:

O . . . OK . . . what are the commands for that . . . “sudo unblame MATE && sudo redistribute blame opensuse -l” ???

I was just going by your post on where, bugzilla, that “mate-menu” was the issue that needed fixing rather than python . . . so now I’m “realizing” that was for opensuse devs/maintainers for MATE??? Based on the posts here it seems like there are only three guys who are running MATE pattern . . . seems like Plasma is the DE of choice for most users these days . . . . I had a Plasma GUI for my Siduction install . . . it was “full-figured” . . . I just like MATE and the Floating Feet screensaver . . . .

#34

In the bug report, I was asking the Opensuse maintainer to rebuild the Opensuse package, not making a reference to the package on the Mate git page. But, did you try executing all three of those commands I posted earlier in that order? That should fix your problem until mate-menu is rebuilt in the repo.

Gene

#35

@Gene_S:

Got that now . . . some things take a long time to get done in linux-land . . . like over in ubuntu there has been an issue with grub2 for at least a year . . . don’t believe it has been addressed or even if it’s likely to be addressed because so few people do multi-boot . . . .

Didn’t get the chance to run those commands in TW yet . . . I rotate into a new distro every day, Monday was OpenSUSE day . . . today was Gecko rolling day . . . and in Gecko I just did #3 and it upgraded 365??? packages . . . . When TW bubbles back up in the order I’ll run them . . . just for kicks; the only place where there is a problem is in my new computer where I must have made the wrong choice, like maybe I went #1 . . . because it was offered first . . . and that is where the log in password has to be typed into black void . . . TW . . . once I click return key the GUI loads and all is well. It’s not an overwhelming problem once I figured out that the vert cursor was indicating a password was being requested . . . .

#36

@Gene_S:

Ran those commands as you suggested . . . “locks” now shows the “mesa-dri-nouveau” and “python3-pyxdg” packages as locked in the MacPro desktop . . . ran the “dup -l” and it showed “244” packages to upgrade, no questionnaire to make a decision about . . . rebooted back into the GUI w/o issue.

So, because I previously made the “right” decision on “#3” in the desktop I never had the “black” log in screen in this computer, but over in the new laptop I guess I chose #1??? and in so doing the problem of the logging in via blindly typing the password . . . works to get into the GUI, but, still the blackness . . . O . . . the blackness, remains.

I saw a couple of other posts on the forum with subject lines of “blackness after upgrade” and so forth . . . gave a quick scan, didn’t exactly seem related to TW in one case, but traced to “sddm” problems . . . so don’t know if that relates to our “MATE menu incompatible with python3” issues . . . or just other packages finding dependency problems resulting in black screen for logging in syndrome???

#37

You can eliminate the “SDDM problem” by temporarily changing the DM to, say, LightDM

If you don’t already have LightDM installed:

zypper in lightdm

Then:

update-alternatives --config default-displaymanager

and change the DM

I’ve not read the whole thread by any means, but I don’t think SDDM is the culprit in this case, still worth eliminating though.

Edit: But then again as you’re using Mate I doubt you’re using SDDM anyway …

#38

@tannington:

Thanks for stopping by . . . yes, there are a couple of us who are using MATE . . . . And that was my question before reading your edit . . . is there a simple command to run to first check what DM is being used . . . before starting to mess around with it, etc???

#39

Use “update-alternatives --config default-displaymanager” it will indicate the available DMs and the currently used (indicated by the asterisk):

paul@HP255G7:~> su -
Password: 
HP255G7:~ # update-alternatives --config default-displaymanager
There are 4 choices for the alternative default-displaymanager (providing /usr/lib/X11/displaymanagers/default-displaymanager).

  Selection    Path                                  Priority   Status
------------------------------------------------------------
  0            /usr/lib/X11/displaymanagers/sddm      25        auto mode
  1            /usr/lib/X11/displaymanagers/console   5         manual mode
* 2            /usr/lib/X11/displaymanagers/lightdm   15        manual mode
  3            /usr/lib/X11/displaymanagers/sddm      25        manual mode
  4            /usr/lib/X11/displaymanagers/xdm       10        manual mode

Press <enter> to keep the current choice
[li], or type selection number: [/li]HP255G7:~ # exit
logout
paul@HP255G7:~>
#40

@Paul:

OK, thanks for that . . . looks “safe” enough . . . but is there anything like in the ubuntu flavors where you can “sudo cat” the request to just look at the data, without being able to change or edit??? I try to eliminate any chances for “pilot error” whenever possible . . . . : _ ))))