Today I’ve found a notification about more than 1000 packages to be updated. After the installation was completed, I’ve returned back to my notebook and I have immediately noticed something wrong: the internet connection was no more available.
I tried to restart the computer, but the option was no more available in the KDE menu (???), so I turned off and on the machine.
Unfortunately, now the notebook hangs up during the boot at the line “started local service”. After that nothings happens, but the screen starts cycling between tre states: turned off for a fraction of a second -> turned on (but black/blank) for a fraction of a second -> displaying the boot commands in the textual interface.
Quite curiously, I also noticed some repeated error messages about the Network Manager that cannot be started. : (
No way to get a console by pressing CTRL-ALT-F3-F6.
The only way I’ve found to get the login-prompt is to edit the “linuxefi” line in the GRUB, by removing the “quite” and “splash” options, as well as by adding the option “3” to run the system without starting the GUI.
As I saw by inspecting the GRUB options, the previous kernel version (4.12.x) is still there but I get the same results when I run it.
My notebook is a crappy ASUS model F550Z with a “Radeon Dual Graphics” (whatever it means).
There is no way to make my notebook running again?
As usually, this kind of things happens always when I need to use the computer for a work dead-line… : ( : ( : (
At the moment, I’m writing to you by using the notebook of my wife (she is so happy of this!)
Nobody has an idea for helping me?
inxi is installed on the system. I’m trying to follow the suggestions reported here, but no success until now… 
There appears to be a problem that if you run snapper (and maybe even if you don’t ) it can mess up the update because it’s scripts may be running when there is an update…
Can you boot to a terminal and run zypper dup from there to complete the update?? There are several recent threads about this
Welcome to the cutting edge. You did bring bandages right??? 
4.12.x is a Leap kernel. You seem to be describing having accidentally and incompletely switched to Tumbleweed from Leap. This commonly happens as a result of doing a 1-click installation from software search and not appropriately following the 1-click instructions.
Please boot using 3 on cmdline again and give us the output from:
sudo zypper lr -d
inxi -GxxSM
inxi -V | head -n1
Inxi is best run from a GUI terminal if you can get X to run, maybe by using nomodeset instead of 3 on Grub’s linux cmdline, or with both nomodeset and 3, logging in, then trying startx. If startx fails as normal user, try as root just to collect the data, then close the X session.
Hallo gogal.
running zypper dup give me the following result:
Segmentation fault (core dumped)
More than this, while booting. I saw some [FAILED] message about ModemManager and NetworkManager both. The system could not start them, so I think my internet connection is not working…
Hallo gogal.
running zypper dup give me the following result:
Segmentation fault (core dumped)
More than this, while booting, I saw some [FAILED] message about ModemManager and NetworkManager both. The system could not start them, so I think my internet connection is not working…
I simply saw the notification of new updates available from the notification-panel in the bottom bar. Then, I just clicked on “install updates”. That’s all…
Ok. I will find a way to copy the outputs here (via an USB key or a screen photo).
Mount the USB, then redirect each command’s output to one or more files on the USB, then copy and paste the file(s)’ contents here. e.g.:
inxi -GxxSM > /mnt/inxiout.txt
Done.
**
inxi -GxxSM**
System: Host: linux-2fqt Kernel: 5.1.7-1-default x86_64 bits: 64 compiler: gcc v: 9.1.1 Console: tty 1 dm: N/A
Distro: openSUSE Tumbleweed 20190605
Machine: Type: Laptop System: ASUSTeK product: X550ZE v: 1.0 serial: ECN0CV43269351H
Mobo: ASUSTeK model: X550ZE v: 1.0 serial: BSN12345678901234567 UEFI: American Megatrends v: 208 date: 10/15/2015
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R6 Graphics] vendor: ASUSTeK driver: radeon v: kernel
bus ID: 00:01.0 chip ID: 1002:130d
Device-2: AMD Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] vendor: ASUSTeK driver: radeon v: kernel
bus ID: 01:00.0 chip ID: 1002:6665
Display: server: X.org 1.19.6 driver: none tty: 170x48
Message: Advanced graphics data unavailable in console for root.
inxi -V | head -n1
inxi 3.0.32-00 (2019-02-07)
**
zypper lr -d**
Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
---+-------------------------------------+-----------------------------------------+---------+-----------+---------+----------+--------+--------------------------------------------------------------------------+--------
1 | http-download.opensuse.org-9ebb6e9a | openSUSE:Factory | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/oss/ |
2 | openSUSE-Leap-15.0-1 | openSUSE-Leap-15.0-1 | Yes | (r ) Yes | No | 99 | rpm-md | cd:///?devices=/dev/disk/by-id/ata-MATSHITADVD-RAM_UJ8E2_S_H090_553558 |
3 | repo-debug | openSUSE-Leap-15.0-Debug | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/distribution/leap/15.0/repo/oss/ |
4 | repo-debug-non-oss | openSUSE-Leap-15.0-Debug-Non-Oss | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/distribution/leap/15.0/repo/non-oss/ |
5 | repo-debug-update | openSUSE-Leap-15.0-Update-Debug | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/update/leap/15.0/oss/ |
6 | repo-debug-update-non-oss | openSUSE-Leap-15.0-Update-Debug-Non-Oss | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/update/leap/15.0/non-oss/ |
7 | repo-non-oss | openSUSE-Leap-15.0-Non-Oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.0/repo/non-oss/ |
8 | repo-oss | openSUSE-Leap-15.0-Oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.0/repo/oss/ |
9 | repo-source | openSUSE-Leap-15.0-Source | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/distribution/leap/15.0/repo/oss/ |
10 | repo-source-non-oss | openSUSE-Leap-15.0-Source-Non-Oss | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/distribution/leap/15.0/repo/non-oss/ |
11 | repo-update | openSUSE-Leap-15.0-Update | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.0/oss/ |
12 | repo-update-non-oss | openSUSE-Leap-15.0-Update-Non-Oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.0/non-oss/ |
Note
If I remember right, trying to mount OpenSUSE on this crappy notebook with windows pre-installed. Wiping out Windows was a huge PITA. The UEFI-BIOS always required a windows partition to boot.
I tried to install Leap 15.0 and Leap 42.x with no success. The installation was succesful but was impossible to boot from those partitions. I gave up…
A week later I tried with Tumbleweed and it succeed (another kick in the ass of Bill Gates). So the partitions with old OpenSuse(s) are still there (but I never used).
Also, during this months, I applied the suggested updates (from the notification widget in the toolbar) two or three times with no problems, until yesterday…
Factory is TW you have mixed repos. With Internet and zypper broken the easiest thing is to reinstall. Note you can keep you home partition just mount it as /home and not format it.
ALL repos must point to the save version numbers
I was correct in comment #4. You do have a Leap installation corrupted by enabling a TW repo. If your Leap 15.0 is using the default BTRFS filesystem, you should attempt to roll back to a state prior to the addition of the TW repo. Details I cannot provide. I’ve never used BTRFS or Snapper. https://en.opensuse.org/openSUSE%3ASnapper_Tutorial seems to provide the instruction you need.
Officially, Tumbleweed users should never ever click on install updates in the notification widget. Traditionally, TW can only be properly upgraded by using zypper dup. Last I heard, changing that was a work in progress. Until that project completes, updating does not apply to TW. Every release of TW is considered a new release, subject only to upgrading, which is recommended to be done from one of the vttys (outside of X), so that a restart of X because of the upgrade cannot abort the upgrade process.
If you actually intended to be running TW, all those 15.0 repos should have been removed.
This project (whatever you mean here) has completed months ago - PackageKit recognizes Tumbleweed and performs equivalent of “zypper dup” since 2019-02-14.
That’s the project I meant. With PackageKit should use “zypper dup” instead of “zypper up” on Tumbleweed remaining an open bug I wouldn’t consider the project complete. It hasn’t appeared on https://news.opensuse.org/ yet either.
Anyway, it would not likely be relevant to a mixed repo mess as this thread’s OP apparently has. 
I don’t know if there is a previous “snapshot” available. I heard something about Snapper, but I have no practical knowledge of it. Anyway I will check it today.
P.S.
Sometimes I remember the old times when all you have is the autoexec.bat… lol!
Here the output of snapper list:
Type | # | Pre # | Date | User | Cleanup | Description | Userdata
-------+----+-------+--------------------------+------+---------+----------------------------+--------------
single | 0 | | | root | | current |
single | 1 | | Sat Dec 15 13:33:01 2018 | root | | first root filesystem |
pre | 43 | | Thu Mar 14 19:45:53 2019 | root | number | zypp(zypper) | important=yes
post | 46 | 43 | Thu Mar 14 19:50:47 2019 | root | number | | important=yes
pre | 60 | | Sun Apr 21 13:00:47 2019 | root | number | zypp(zypper) | important=yes
post | 61 | 60 | Sun Apr 21 13:15:53 2019 | root | number | | important=yes
pre | 62 | | Sun Apr 21 13:56:32 2019 | root | number | zypp(packagekitd) | important=yes
post | 63 | 62 | Sun Apr 21 14:00:25 2019 | root | number | | important=yes
pre | 66 | | Fri May 31 11:46:33 2019 | root | number | zypp(zypper) | important=yes
pre | 75 | | Fri May 31 12:46:25 2019 | root | number | zypp(packagekitd) | important=yes
post | 76 | 75 | Fri May 31 12:54:54 2019 | root | number | | important=yes
pre | 77 | | Wed Jun 5 15:32:26 2019 | root | number | zypp(packagekitd) | important=no
post | 78 | 77 | Wed Jun 5 15:33:02 2019 | root | number | | important=no
pre | 79 | | Thu Jun 6 18:37:52 2019 | root | number | zypp(packagekitd) | important=no
post | 80 | 79 | Thu Jun 6 18:38:07 2019 | root | number | | important=no
pre | 81 | | Thu Jun 6 23:29:39 2019 | root | number | yast OneClickInstallWorker |
pre | 82 | | Thu Jun 6 23:31:15 2019 | root | number | zypp(ruby.ruby2.5) | important=no
post | 83 | 82 | Thu Jun 6 23:31:20 2019 | root | number | | important=no
post | 84 | 81 | Thu Jun 6 23:31:23 2019 | root | number | |
pre | 85 | | Fri Jun 7 10:48:28 2019 | root | number | zypp(packagekitd) | important=yes
post | 86 | 85 | Fri Jun 7 12:16:07 2019 | root | number | | important=yes
The system doesn’t boot from 7 June, so I think I should apply the command undochange 85…86 (i.e. the last change). Or it would be safer to go more back in time? :shame:
Given that 1-click is the probable root cause of your trouble, I’d first try to find out what 1-click was used to install, then choose to go back to 80, and after confirming the system is OK, update 15.1, then add in conventional fashion (yast or zypper) whatever 1-click was used to install.
Here some outputs.
snapper diff 80…81:
--- /.snapshots/80/snapshot/etc/cups/subscriptions.conf 2019-06-06 18:34:30.195229363 +0200
+++ /.snapshots/81/snapshot/etc/cups/subscriptions.conf 2019-06-06 23:26:09.980856084 +0200
@@ -1,5 +1,5 @@
# Subscription configuration file for CUPS v2.2.7
-# Written by cupsd on 2019-06-06 18:34
+# Written by cupsd on 2019-06-06 23:26
NextSubscriptionId 56
<Subscription 55>
Events job-state-changed job-created job-completed job-stopped job-config-changed job-progress server-restarted server-started server-stopped server-audit
@@ -7,6 +7,6 @@
Recipient dbus://
LeaseDuration 3600
Interval 0
-ExpirationTime 1559842439
+ExpirationTime 1559859938
NextEventId 1
</Subscription>
--- /.snapshots/80/snapshot/etc/cups/subscriptions.conf.O 2019-06-05 22:27:44.807059031 +0200
+++ /.snapshots/81/snapshot/etc/cups/subscriptions.conf.O 2019-06-06 22:27:49.976360153 +0200
@@ -1,3 +1,12 @@
# Subscription configuration file for CUPS v2.2.7
-# Written by cupsd on 2019-06-05 22:27
-NextSubscriptionId 55
+# Written by cupsd on 2019-06-06 22:27
+NextSubscriptionId 56
+<Subscription 55>
+Events job-state-changed job-created job-completed job-stopped job-config-changed job-progress server-restarted server-started server-stopped server-audit
+Owner mila
+Recipient dbus://
+LeaseDuration 3600
+Interval 0
+ExpirationTime 1559856438
+NextEventId 1
+</Subscription>
snapper diff 81…82 :*
--- /.snapshots/81/snapshot/etc/zypp/repos.d/http-download.opensuse.org-9ebb6e9a.repo 1970-01-01 01:00:00.000000000 +0100
+++ /.snapshots/82/snapshot/etc/zypp/repos.d/http-download.opensuse.org-9ebb6e9a.repo 2019-06-06 23:31:07.588387109 +0200
@@ -0,0 +1,7 @@
+[http-download.opensuse.org-9ebb6e9a]
+name=openSUSE:Factory
+enabled=1
+autorefresh=1
+baseurl=http://download.opensuse.org/tumbleweed/repo/oss/
+type=rpm-md
+keeppackages=0
So, as I see, there was minor changes applied with the “1-click-installer”. Something related to cups (print management?).
On the other hand, commands like
*
snapper diff 79…80
snapper diff 85…86*
produces tons of rows/changes (I have to press CTRL-C to stop the screen text from scrolling).
Anyway, I think I will go for restoring the snapshot #80 to stay on the safe side.
Should I use
snapper undochange 80…86
or the sequence
snapper undochange 85…86
snapper undochange 84…85
snapper undochange 83…84
snapper undochange 82…83
snapper undochange 81…82
snapper undochange 80…81
???
The documentation is not clear about that. :shame:
Boom!
Problem solved!
After executing the command snapper undochange 85…86 the system boot normally! 
I have my notebook back again. lol!
Everything works normally as before, all applications runs properly, and the NetworkManager is launched at the boot without problems.
Two important facts as result:
- the option to run Tumbleweed is disappeared from the boot list when I turn on the notebook
- I have received (again) the notification of 1148 updates available for my Leap 15 system (see the image below)
Why the heck I receive a notification of updates that will try (again) to transform my Leap 15 into a Tumbleweed system???
There is a valid reason for that?
No Guru can respond me?
https://i.ibb.co/b65n245/Screenshot-from-2019-06-10-23-17-44.jpg](https://ibb.co/b65n245)
P.S.
I have deleted the snapshot #85 and @86 by using the command snapper delete 85 86
P.P.S
I have no tumbleweed repos listed in my system:
linux-2fqt:/home/mila # zypper lr
Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Name | Enabled | GPG Check | Refresh
---+-------------------------------------+-----------------------------------------+---------+-----------+--------
1 | http-download.opensuse.org-9ebb6e9a | openSUSE:Factory | Yes | (r ) Yes | Yes
2 | openSUSE-Leap-15.0-1 | openSUSE-Leap-15.0-1 | Yes | (r ) Yes | No
3 | repo-debug | openSUSE-Leap-15.0-Debug | No | ---- | ----
4 | repo-debug-non-oss | openSUSE-Leap-15.0-Debug-Non-Oss | No | ---- | ----
5 | repo-debug-update | openSUSE-Leap-15.0-Update-Debug | No | ---- | ----
6 | repo-debug-update-non-oss | openSUSE-Leap-15.0-Update-Debug-Non-Oss | No | ---- | ----
7 | repo-non-oss | openSUSE-Leap-15.0-Non-Oss | Yes | (r ) Yes | Yes
8 | repo-oss | openSUSE-Leap-15.0-Oss | Yes | (r ) Yes | Yes
9 | repo-source | openSUSE-Leap-15.0-Source | No | ---- | ----
10 | repo-source-non-oss | openSUSE-Leap-15.0-Source-Non-Oss | No | ---- | ----
11 | repo-update | openSUSE-Leap-15.0-Update | Yes | (r ) Yes | Yes
12 | repo-update-non-oss | openSUSE-Leap-15.0-Update-Non-Oss | Yes | (r ) Yes | Yes
