After the last update Tumbleweed, Network does not work

I would suggest using coredumpctl (maybe add --all) to see previous coredumps. With “ls” you will only see if there is still a real coredump and previous coredumps may be an indication of more systemic problems.

Also, as root. Check the journal to see if networkmanager is behaving odd since boot.

journalctl -u NetworkManager.service

or this to get only the syslog identifier “NetworkManager”
journalctl -b SYSLOG_IDENTIFIER=NetworkManager

compare with last boot (or last working boot=number)

journalctl -b 1 SYSLOG_IDENTIFIER=NetworkManager
journalctl -b 2 SYSLOG_IDENTIFIER=NetworkManager

When you find something weird. Have a look around for odd things with a more broder journalctl statement and around that point in time:

journalctl --since ‘2023-10-01 07:00:00’ --until ‘2023-10-03 23:00:00’

If you do find something odd please post it to I usually do:
journalctl --since ‘2023-10-01 07:00:00’ --until ‘2023-10-01 23:00:00’ | xclip -i

and then paste it to You can pipe it directly to the command susepaste but it sometimes doesn’t work correctly.

Sorry, I meant:
journalctl -b -u NetworkManager.service

I apologize for the graphic format of these logs. Please tell me this information is enough?

Perhaps this problem is similar to my problem? -

Unfortunately, the graphic information is not enough. It lacks information for the entire session.

You are not seeing all things in the system log as you should run the journalctl command as root (with sudo). There is user specific journal log but in this case it doesn’t help as NetworkManager is logged in system journal.

Please run this and paste the output to Make it last at least 1 month as other may need to have a look. It’s the Remove after 1 month field in the bottom right corner.

sudo journalctl -b -u NetworkManager.service | xclip -i

If you don’t have xclip just install it through yast or directly in a command shell. Like so:

sudo zypper in xclip

It could be, but since there is zero, zilch, zip, nada info besides the topic in that thread, it’s hard to tell.

I do not have the Internet on a PC where the Opensuse Tumblewhed is installed. is unattainable for me.

I have no opportunity to work for two days. I suppose I have no other choice now, except for the transition to Fedora.

And I have to say many thanks to the Opensuse programmers for the excellent results of their work.

Okay. If you boot to last working snapshot and then rollback you have your working system again.

I do not use btrfs.

I saw a new Tumbleweed snapshot 20231005 with a glibc update coming by and did a “zypper dup” and after a reboot things seems to be fine again for me.

If I write down the snapshot on the flash drive, is it possible to update the existing operating system from it? What do you think about it, Marel?

I think it is a bad idea to run Tumbleweed on a PC without Internet, for that Leap, Leap Micro or MicroOS a much better choice.

Updating without Internet is possible but far from easy, see Updating opensuse 15.3 without internet

You wrote:

After yesterday’s upgrade and rebooting

How did you do that upgrade?

marel, you will get the answer to your question if you read the title of this thread.

Tumbleweed update caused the modem to be unable to connect via usb. I am unpleasantly surprised by the unprofessionalism of OpenSuse maintainers who worked on the service pack. I am now looking for a way to solve a ridiculous problem that is the fault of the OpenSuse programming team.

Perhaps you can give me some good advice on how to do this optimally? I’m sure many Tumbleweed users are without internet.

For example:

There is not a single bugreport regarding broken network for this update…so it seems more something special for your machine…

I’m not sure if you want advice from others since you’re directing your question to one person.

  1. Is the only way to connect to your phone via USB? Can you put it in “WIFI hotspot mode”? Or is the WIFI also broken on your computer?

  2. Download the snapshot. Install it on a USB stick. Copy all rpms from x86_64/ and noarch/ to /var/cache/zypper/RPMS/, which is the directory zypper dup --download-only saves rpms to . Start zypper dup. This is just a suggestion. I’ve never done it myself and it’s up to you to decide if you want to try it.

Hui, there are three posts on this forum about similar network interface errors in the last. I am sorry that you are adding lies to the unprofessional work of Tumbleweed maintainers.

Bug reports are not made here. To actually get things fixed you have to go to bugzilla. People on the forum are just people like you and me trying to help. Nothing more.

Aggplanta, I’m happy for any advice to help me find a solution to a silly situation I owe to the Tumbleweed team. And, believe me, I’m grateful for that advice. But I would like to get a solution that has been proven correct by real experience.

Unfortunately, this computer does not use WiFi. I connected to the internet via USB modem on this host, and that was enough for me. It never occurred to me that today’s ridiculous case is possible.

Aggplanta, I consider several similar posts on this forum to be the kind of sign that needs attention. The lack of bug reports on bugzilla only tells me that people don’t have the time. You can see that one Tumbleweed user chose to switch to debian instead of a long discussion. And I can probably understand that person’s emotions and frustration. .

I really have no words in the context of what happened. This case dropped the reputation of the distribution and the OpenSuse maintainer team. This is my subjective assessment, and the forum moderator can remove my words if he wants.