15.3 The worst distribution since the 42. Hyper slow start when it starts, startup bug, impossible shutdown, not mounting the network are some of the most common problems. Problem of installation of some software like vmware for example because of this polkit dung are others.
For me, Leap 15.3 is working quite well.
Yes, it got off to a rough start. But the early problems have been resolved. Startup and shutdown times seem as good as, say, 15.2. And actually, shutdown time seems faster. However, a recent change did slow startup when there is a new kernel. That’s because the purge kernels service is now being required to complete before startup finishes. I don’t know why they made that change, and there is already a bug report complaining about it.
Odd that you’re having problems with VMware - I run VMware Worksation 16.2.3 here without any issues whatsoever. Perhaps you should ask for help with your issues (either here or on the VMware forums) rather than just complaining.
I can finish vmware install starting gui as root to avoid polkit ********. My 15.3 is up to date and shutdown is impossible, system freeze always.
Nope. Due to excellent installation of systemd Leap startup is as fast as can be. Tumbleweed is even faster:https://www.youtube.com/watch?v=yraNeOaYQBw
Startup is fast:
**erlangen:~ #** systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @1.947s
└─**display-manager.service @1.094s +853ms**
└─**apache2.service @983ms +109ms**
└─time-sync.target @979ms
└─**chronyd.service @913ms +65ms**
└─nss-lookup.target @911ms
└─**systemd-resolved.service @838ms +72ms**
└─**systemd-networkd.service @600ms +235ms**
└─**systemd-udevd.service @435ms +137ms**
└─**systemd-tmpfiles-setup-dev.service @396ms +27ms**
└─**kmod-static-nodes.service @333ms +53ms**
└─systemd-journald.socket
└─system.slice
└─-.slice
**erlangen:~ #**
Shutdown is fast too:
[FONT=monospace]**erlangen:~ #** journalctl -b -1 -g Stopped --since 9:36 -o short-monotonic --no-pager
[75357.720447] erlangen systemd[1]: Stopped target Graphical Interface.
[75357.720514] erlangen systemd[1]: Stopped target Multi-User System.
[75357.720598] erlangen systemd[1]: Stopped target Login Prompts.
[75357.720673] erlangen systemd[1]: Stopped target Sound Card.
[75357.720735] erlangen systemd[1]: Stopped target Timer Units.
[75357.720868] erlangen systemd[1]: Stopped Backup of /home.
[75357.720978] erlangen systemd[1]: Stopped Backup of RPM database.
[75357.721084] erlangen systemd[1]: Stopped Backup of /etc/sysconfig.
[75357.721216] erlangen systemd[1]: Stopped Balance block groups on a btrfs filesystem.
[75357.721323] erlangen systemd[1]: Stopped Scrub btrfs filesystem, verify block checksums.
[75357.721429] erlangen systemd[1]: Stopped Check if mainboard battery is Ok.
[75357.721519] erlangen systemd[1]: Stopped Discard unused blocks once a week.
[75357.721614] erlangen systemd[1]: Stopped Daily rotation of log files.
[75357.722020] erlangen systemd[1]: Stopped Daily man-db regeneration.
[75357.722135] erlangen systemd[1]: Stopped Daily locate database update.
[75357.722265] erlangen systemd[1]: Stopped Systemd timer to update the system daily with PackageKit.
[75357.722384] erlangen systemd[1]: Stopped Daily Cleanup of Snapper Snapshots.
[75357.722496] erlangen systemd[1]: Stopped Daily Cleanup of Temporary Directories.
[75357.722777] erlangen systemd[1]: Stopped auditd rules generation.
[75357.724462] erlangen systemd[1]: Stopped Apply settings from /etc/sysconfig/keyboard.
[75357.726228] erlangen systemd[1]: Stopped irqbalance daemon.
[75357.726375] erlangen systemd[1]: Stopped Machine Check Exception Logging Daemon.
[75357.726463] erlangen systemd[1]: Stopped Daemon for power management.
[75357.726556] erlangen systemd[1]: Stopped RealtimeKit Scheduling Policy Service.
[75357.726681] erlangen systemd[1]: Stopped A remote-mail retrieval utility.
[75357.799448] erlangen systemd[1]: Stopped hd-idle disk spindown service.
[75357.799582] erlangen systemd[1]: Stopped Getty on tty1.
[75357.803819] erlangen systemd[1]: Stopped Command Scheduler.
[75357.805751] erlangen systemd[1]: Stopped Authorization Manager.
[75357.806077] erlangen systemd[1]: Stopped Save/Restore Sound Card State.
[75357.806367] erlangen systemd[1]: Stopped Restore /run/initramfs on shutdown.
[75357.806701] erlangen systemd[1]: Stopped Load/Save Random Seed.
[75357.820145] erlangen systemd[1]: Stopped Disk Manager.
[75357.820844] erlangen systemd[1]: Stopped Start fetchmail.
[75357.820957] erlangen systemd[1]: Stopped Hold until boot process finishes up.
[75357.821349] erlangen systemd[1]: Stopped CUPS Scheduler.
[75357.850306] erlangen systemd[1]: Stopped Session 2 of User karl.
[75357.868230] erlangen systemd[1182]: Stopped target Main User Target.
[75357.868671] erlangen systemd[1182]: Stopped Sound Service.
[75357.869308] erlangen systemd[1182]: Stopped Save jAlbum Project Files.
[75357.869401] erlangen systemd[1182]: Stopped Virtual filesystem metadata service.
[75357.869438] erlangen systemd[1182]: Stopped sandboxed app permission store.
[75357.869481] erlangen systemd[1182]: Stopped Xdg Desktop Portal For KDE.
[75357.873221] erlangen systemd[1182]: Stopped Virtual filesystem service.
[75357.878768] erlangen systemd[1182]: Stopped User preferences database.
[75357.884552] erlangen systemd[1182]: Stopped D-Bus User Message Bus.
[75357.884795] erlangen systemd[1182]: Stopped Portal service.
[75357.886609] erlangen systemd[1182]: Stopped flatpak document portal service.
[75357.895207] erlangen systemd[1182]: Stopped Multimedia Service Session Manager.
[75357.898811] erlangen systemd[1182]: Stopped PipeWire Multimedia Service.
[75357.904990] erlangen systemd[1]: Stopped MiniDLNA is a DLNA/UPnP-AV server software.
[75357.905794] erlangen systemd[1]: Stopped target Network is Online.
[75357.913495] erlangen systemd[1182]: Stopped jAlbum - Make web photo albums with thumbnail pages and slide shows.
[75357.938849] erlangen systemd[1182]: Stopped KRunner.
[75357.956693] erlangen systemd[1182]: Stopped Firefox - Web Browser.
[75357.987524] erlangen systemd[1182]: Stopped KMail - E-Mail-Programm.
[75358.021494] erlangen systemd[1182]: Stopped Accessibility services bus.
[75358.021949] erlangen systemd[1182]: Stopped target Basic System.
[75358.022137] erlangen systemd[1182]: Stopped target Paths.
[75358.022337] erlangen systemd[1182]: Stopped target Sockets.
[75358.022531] erlangen systemd[1182]: Stopped target Timers.
[75358.022704] erlangen systemd[1182]: Stopped Daily Cleanup of User's Temporary Directories.
[75358.023466] erlangen systemd[1182]: Stopped Create User's Volatile Files and Directories.
[75358.085573] erlangen systemd[1]: Stopped Postfix Mail Transport Agent.
[75358.246569] erlangen systemd[1182]: Stopped Terminal - Super User Mode.
[75358.250931] erlangen systemd[1]: Stopped User Manager for UID 1000.
[75358.260935] erlangen systemd[1]: Stopped User Runtime Directory /run/user/1000.
[75358.354285] erlangen systemd[1]: Stopped Session 4 of User charlemagne.
[75358.364203] erlangen systemd[2787]: Stopped KActivityManager Activity manager Service.
[75358.374403] erlangen systemd[2787]: Stopped target Main User Target.
[75358.384291] erlangen systemd[2787]: Stopped Sound Service.
[75358.386660] erlangen systemd[2787]: Stopped Portal service (GTK/GNOME implementation).
[75358.387866] erlangen systemd[2787]: Stopped Xdg Desktop Portal For KDE.
[75358.390256] erlangen systemd[2787]: Stopped sandboxed app permission store.
[75358.404923] erlangen systemd[2787]: Stopped Multimedia Service Session Manager.
[75358.405781] erlangen systemd[2787]: Stopped User preferences database.
[75358.417093] erlangen systemd[2787]: Stopped D-Bus User Message Bus.
[75358.417259] erlangen systemd[2787]: Stopped Portal service.
[75358.417391] erlangen systemd[2787]: Stopped PipeWire Multimedia Service.
[75358.471505] erlangen systemd[2787]: Stopped flatpak document portal service.
[75358.540238] erlangen systemd[2787]: Stopped Virtual filesystem service.
[75358.542376] erlangen systemd[2787]: Stopped KMail - Mail Client.
[75358.568320] erlangen systemd[2787]: Stopped Firefox - Web Browser.
[75358.605761] erlangen systemd[2787]: Stopped Accessibility services bus.
[75358.606239] erlangen systemd[2787]: Stopped target Basic System.
[75358.606402] erlangen systemd[2787]: Stopped target Paths.
[75358.606568] erlangen systemd[2787]: Stopped target Sockets.
[75358.606738] erlangen systemd[2787]: Stopped target Timers.
[75358.606880] erlangen systemd[2787]: Stopped Daily Cleanup of User's Temporary Directories.
[75358.607627] erlangen systemd[2787]: Stopped Create User's Volatile Files and Directories.
[75358.821582] erlangen systemd[2787]: Stopped /usr/bin/korgac.
[75358.827547] erlangen systemd[1]: Stopped User Manager for UID 1001.
[75358.973872] erlangen systemd[1]: Stopped User Runtime Directory /run/user/1001.
[75358.993117] erlangen systemd[1]: Stopped D-Bus System Message Bus.
[75359.677955] erlangen systemd[1]: Stopped X Display Manager.
[75359.688285] erlangen systemd[1]: Stopped Permit User Sessions.
[75359.742034] erlangen systemd[1]: Stopped The Apache Webserver.
[75359.742407] erlangen systemd[1]: Stopped target Remote File Systems.
[75359.742570] erlangen systemd[1]: Stopped target System Time Synchronized.
[75359.742691] erlangen systemd[1]: Stopped target System Time Set.
[75359.745110] erlangen systemd[1]: Stopped NTP client/server.
[75359.745424] erlangen systemd[1]: Stopped target Network.
[75359.745582] erlangen systemd[1]: Stopped target Host and Network Name Lookups.
[75359.755598] erlangen systemd[1]: Stopped Network Name Resolution.
[75359.760941] erlangen systemd[1]: Stopped User Login Management.
[75359.761234] erlangen systemd[1]: Stopped target Basic System.
[75359.761363] erlangen systemd[1]: Stopped target Path Units.
[75359.776847] erlangen systemd[1]: Stopped Watch /etc/sysconfig/btrfsmaintenance.
[75359.824566] erlangen systemd[1]: Stopped Watch for changes in CA certificates.
[75359.824978] erlangen systemd[1]: Stopped CUPS Scheduler.
[75359.848529] erlangen systemd[1]: Stopped Watch for changes in issue snippets.
[75359.864554] erlangen systemd[1]: Stopped Watch for changes in smartmontools sysconfig file.
[75359.864878] erlangen systemd[1]: Stopped target Slice Units.
[75359.865839] erlangen systemd[1]: Stopped target Socket Units.
[75359.867361] erlangen systemd[1]: Stopped target System Initialization.
[75359.867795] erlangen systemd[1]: Stopped target Local Encrypted Volumes.
[75359.880576] erlangen systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
[75359.880801] erlangen systemd[1]: Stopped target Local Integrity Protected Volumes.
[75359.880942] erlangen systemd[1]: Stopped target Local Verity Protected Volumes.
[75359.896699] erlangen systemd[1]: Stopped Network Configuration.
[75359.904108] erlangen systemd[1]: Stopped Apply Kernel Variables.
[75359.904439] erlangen systemd[1]: Stopped Apply Kernel Variables for 5.17.3-1-default.
[75359.904832] erlangen systemd[1]: Stopped Load Kernel Modules.
[75359.905565] erlangen systemd[1]: Stopped Record System Boot/Shutdown in UTMP.
[75360.011450] erlangen systemd[1]: Stopped Security Auditing Service.
[75360.011681] erlangen systemd[1]: Stopped Create Volatile Files and Directories.
[75360.011725] erlangen systemd[1]: Stopped target Local File Systems.
**erlangen:~ #**
[/FONT] Total shutdown time including two graphical logins is 2.3 seconds.
Which Filesystem are you using for the system partition?
- If Btrfs then, has the Btrfs housekeeping been executed?
Is the system partition large enough?
- Does the “/var” partition have enough free space for the systemd Journal to write shutdown entries?
Is the system disk healthy?
- Does the SMART information indicate any issues with the hardware device?
I can only add that with each upgrade Leap is getting better, IMHO. I waited long with 15.3 due to many reported issues but I didn’t actually have anything serious.
Further to this issue: How long do you actually wait? while shutting down and in “frozen” state, did you try hitting the ESC key? It will show you the live system messages. Sometimes, there’s something along the line of: “A stop job is running for …” which is usually counting down 1:30 min or so. That may indeed be a bit annoying. There’s a couple of threads here on that subject. I have to admit the suggested solutions either didn’t work for me or I didn’t bother to dig as far into systemd’s secrets as would have been required.
What actually (most of the time) works for me is not using the KDE starter button for shutdown but hitting the hardware power button. First time it will just log me out of KDE, second will shut down very fast. I don’t know why this works better for me.
Also, running as root: “systemctl poweroff” is very fast but it seems to go round my syncing scripts I configured for shutdown in KDE settings, so it’s not the regular option for me.
I run Leap 15.3 on an Acer desktop, a PCSpecialist laptop and a 2007 Dell notebook and, apart from the occasional stop job problem, have experienced no problems starting up and shutting down. Speed of start up appears to be solely related to hardware. The Dell notebook with only 2GB RAM takes longest to start up but shuts down very quickly. The laptop, with an SSD hard drive, starts up and shuts down like lightning.
There are a whole bunch of questions that you need to provide answers to in order to get help - just saying “this thing doesn’t work” without providing details about configuration items isn’t enough to get help.
I run VMware as a user, and it just works. New kernel install happens, start VMware, and I get prompted for the root password so it can compile and install updated vmmon and vmnet modules. Does that, and it just starts right up.
“Shutdown is impossible” provides no detail about what’s happening. If you look at the system logs, what do you see in them? If you start a shutdown and switch to a console, what do you see on the console?
What additional services are installed?
Are you running network-based filesystems (either being shared with other systems from your system, or connecting to other filesystems using NFS, sshfs, SAMBA, or something else?)
Are you running containerized apps in Docker or podman?
“It doesn’t work” doesn’t provide enough information - but answering questions like the ones I’ve posed here can give people ideas about places to look.
Otherwise, anyone answering is just guessing at what’s going on in your system. The more relevant information you can provide, the better the answers you’ll get.
I’d suggest taking each of your issues and starting a thread in the appropriate forum - that way, you’ll have the eyes of people who know about those particular things.
And, BTW, do so politely. Swearing about it isn’t going to impress anyone, and it’s more than likely going to turn people off from helping you. The community is here to help, but generally doesn’t take kindly to people being rude when they’re trying to get things working.
To all here.
This is General Chit-Chat, thus there is no need for the OP to provide any details about what he sees to happen. When the OP had wanted real technical help, I have no doubt he would have gone to the appropriate technical help sub-forums.
So please either refrain from posting here in a serious technical manner, or answer in the style of this Chit-Chat sub-forum: as if you met in the pub.
Agreed, but also more to the point - coming into a community forum to vent about “this stuff doesn’t work” isn’t productive or helpful for anyone. It’s always better to take stock of the problems one is having, go to an appropriate support forum to ask for help, and then to (a) provide useful information to help people troubleshoot (not knowing what that is is fine, just ask for what would be useful information), and (b) do so politely rather than swearing up a blue streak.
People having issues should always remember a few things: We have a lot of users. If it were as broken for everyone as it is for you, then of course it would be fixed. That it isn’t means that you’ve likely stumbled on an edge case in a very complex system, so have some patience and ask for help. Answer the questions that those who are trying to help you are asking, because the information they’re asking for is information they think is relevant to fixing your issue. They’re not asking the questions for kicks, or to waste your time (after all, it’s wasting their time as well). Most people who are here to help are here to help. But they also generally don’t want to play 20 questions; they only know what you tell them about the issue you’re having. They’re volunteers, so don’t expect them to reproduce your problem unless they choose to do so (which often means it’s something that maybe affects them as well).
“Leap uses source from SUSE Linux Enterprise (SLE), which gives Leap a level of stability unmatched by other Linux distributions” rotfl!
So we can hope a distribution without big bugs. It’s not the case. This morning Leap enter two times in rescue mode. It start after the second reset. My usb ocr pen need to be disconnected and reconnected to function. I don’t have any of this problem with 15.1. I upgrade because it was the only solution to have the last version of Firefox. Now I have two option : downgrade to 15.1 or 15.2 or go to a less Enterprise and less buggy distribution.
All software can have bugs. Whether those are “big” depends on what you are doing.
This morning Leap enter two times in rescue mode. It start after the second reset.
I have not had that problem.
My usb ocr pen need to be disconnected and reconnected to function.
Have you filed a bug report on that?
So submit a but report on bugzilla.opensuse.org - or open a thread in a support group and provide some details. There’s a third option that actually not only helps you get a resolution, but also helps others get a resolution. If it isn’t reported, it can’t be investigated and fixed. Developers aren’t psychics - they need information from individuals having issues in order to fix bugs.
To expect that complex software be completely bug-free is unreasonable. There are literally millions of lines of highly complex code involved in a full distribution. Sometimes fixing one bug causes a regression, and the developer doesn’t have the same hardware you do, so how are they to know that the thing they changed to fix one thing didn’t affect the driver your hardware uses?
And as for rescue mode: hard drives fail, data gets corrupted. There are lots of things that can cause this that are completely out of the control of any developer. How could you expect a developer to build something that’s impervious to failing hardware or other factors outside of your control? It’s not reasonable to blame the developers for a system protecting itself from further data corruption because something’s starting to show signs of wear.