Last night Discovery was flagging updates, so I fired up myrlyn and processed them. Then ran a restart, but now I can’t browse in Firefox. The wired network is up and I can see the local hardware, and myrlyn has no problem accessing packages. Also some pages such as opensuse.org are visible so something is blocking the rest? In addition, the wireless connection is also failing to connect as it can’t authenticate. Just where should I been kicking to reset this?
Well I’ve said before and I’ll say it again … too many points of failure … I only update TW with zypper dup from a terminal … then and only then after a reboot (if necessary) will I let discover(whatever) update … try running a zypper dup again … then discover … I’ve never had a problem
1 Like
On Tumbleweed, only a
zypper dup
is the way to get any Update.
With Discover, Yast or zypper up you will get also Updates but that will break at some time.
So only use
zypper dup
for Updates on Tumbleweed.
I’m using myrlyn BECAUSE it provides a dup option and it tells me what packages it’s going to process. I’d been pointed in that direction previously and up until now it has been working fine. That said, zypper dup just removed libgdal36 and that is all.
Some links from opensuse.org are working so it is the dns side of things that is screwed currently … I’m adding this reply from Firefox on the desktop which is what is more irritating …
Well apparently it doesn’t work out quite right … listen to me an @Sauerland … zypper dup in a terminal
PS: I’ve found Myrlyn to be a bit sketchy
So does DUP from a terminal
Well if myrlyn is not doing the job properly then I’ll stop using it again. I was told it was a safe way to see just what was going to be updated and it HAS been good at providing that information.
The problem NOW is how do I repair the damage it has done? just what do I need to clear out to get dns working properly again?
First thing is to do thatzypper dupand explain here that you did.
Then
that is the same as the infamous “it does not work”. Tell exactly what you do and what you get. We can not look over your shoulders.
And when this is about DNS, then show what you have configured in that area.
cat /etc/resolv.conf
and
cat /etc/nsswitch.conf
Mystery solved … KDEWallet was hidden in the background expecting me to put a password in. Once that was done, the wireless connection fired up without a problem, and everything started working again in Firefox, rather than just a few sites.
The question NOW is “Why is resolution of addresses failing when only the wired connection is available?” If I switch off wireless I’m back in the situation where some sites do work but not others. It is now obvious that this is nothing to do with the last updates at all, but something to do with how the two network connections are interacting?
(myrlyn lists all the updates and I can simply disable ones if I want something that CAN’T be done from a command prompt as easily … it can also identify updates that NEED dup which have tended to be the network stuff in previous updates)
Do what @hcvv said
My experience here is that you can jump high and low and argue what you want. And it even could be that some tool does a proper zypper dup behind the scene. But many potential helpers here will require that you do a zypper dup so that everybody can be sure for 1000% that it was done, before they will even try providing further help.
From second post …
I will be 70 in a few months time, so being able to tell a client which line of code to change from memory while on the phone to them 40 odd years ago is a thing of the past. I need crib sheets to remind me today things that I did only recently 
From resolv.conf
Call “netconfig update -f” to force adjusting of /etc/resolv.conf.
(!something I had done this morning)
search lan
nameserver 192.168.1.254
nameserver 1.1.1.1
nameserver 1.0.0.1
- 192.168.1.254 is the BT router and I suspect I could change the other two addresses to something UK based?
And nsswitch.conf
passwd: compat systemd
group: compat systemd
shadow: compat
hosts: files mdns_minimal [NOTFOUND=return] dns
networks: files dns
aliases: files usrfiles
ethers: files usrfiles
gshadow: files usrfiles
netgroup: files nis
protocols: files usrfiles
publickey: files
rpc: files usrfiles
services: files usrfiles
automount: files nis
bootparams: files
netmasks: files
Cracked it … the wired connection was looking at the local server rather than the BT router for DNS. I’d had to have the router changed a week ago as it had failed and it seems while that was off line the local network was using the local ‘dns’. Switched back to automatic on the wired connection and I’m sorted.
Don‘t spread nonsense and false informations. Myrlyn is capable of performing a zypper dup and zypper up.
This is one of the main reason why it was developed (beside deprecation of YaST). As many Tumbleweed users struggled to upgrade the machine via terminal, Stefan coded Myrlyn to overcome this issue and have a nice GUI.
IF you have real proof of a bug, report it properly.
2 Likes
@hui I’ll assume you’re talking to me … example: I search “apparmor” in myrlyn and find a bunch of results but none of them checked … I zypper se -si apparmor and find this
windeath:/home/dart # zypper se -si apparmor
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+---------------+---------+-----------+--------+-----------
i | libapparmor1 | package | 4.1.1-1.1 | x86_64 | repo-oss
i | perl-apparmor | package | 4.1.1-1.1 | x86_64 | repo-oss
Makes me wonder what else you are continuously wrong about … the truth never equals FUD
But did you file a bug report when you are convinced of it being an error? Ranting here with other users as audience does not make the product any better.
1 Like
@hcvv that was not a rant … believe me you’ll know when I rant … this was a simple pointer to what I perceive to be a flaw … I keep hearing that users should follow the mailing list but do the developers even bother to check out the “bugs” that us lowly users find on our lists?
I’m gonna wait a few updates to see if it gets fixed or not … or I can just delete myrlyn … are you seriously telling me nobody else noticed this?
You do not even understand that the mailing list is no bugreporting tool.
Waiting and hoping doesn‘t fix anything.
If you have proof for a bug you need to report it to get it fixed.
1 Like
And you’re wrong again …
huiBusy Penguin
You do not even understand that the mailing list is no bugreporting tool.
And I Never said it was … so maybe I understand more than you think … I said “do the developers even bother to check” … no posts … just an “FYI” of “hmmm…this seems to be an issue”
Yes I wait and hope for the best … and then I nuke what doesn’t work