- openSUSE Support

[opensuse-support] cups-browsed dies - where to start looking?
by Peter Suetterlin 31 Jul '19

31 Jul '19

Hi list, just wanted to print from my laptop (don't do this too often). Its cups is supposed to connect to our local printserver, but didn't print. Checking the logs I find No destination host name supplied by cups-browsed for printer "samsung", is cups-browsed running? Hm, no, it's not. Restarting it doesn't help, so I check the error log Wed Jul 31 15:40:17 2019 main() in THREAD 140070619588288 Wed Jul 31 15:40:17 2019 cups-browsed: Creating http connection to local CUPS daemon: /var/run/cups/cups.sock:631 Wed Jul 31 15:40:17 2019 update_netifs() in THREAD 140070619588288 Wed Jul 31 15:40:17 2019 network interface lo: Local host name/address: 127.0.0.1 Wed Jul 31 15:40:17 2019 network interface lo: Local host name/address: localhost Wed Jul 31 15:40:17 2019 network interface eth0: Local host name/address: Wed Jul 31 15:40:17 2019 network interface eth0: Local host name/address: woodstock.xxx Wed Jul 31 15:40:17 2019 Network interface eth0 at xx.xx.xx.xx for legacy CUPS browsing/broadcasting Wed Jul 31 15:40:17 2019 cups-browsed [BrowsePoll /var/run/cups/cups.sock:0]: IPP-Create-Subscription Wed Jul 31 15:40:17 2019 cups-browsed [BrowsePoll /var/run/cups/cups.sock:0]: subscription ID=1530 Wed Jul 31 15:40:17 2019 cups-browsed (/var/run/cups/cups.sock): cupsEnumDests Wed Jul 31 15:40:17 2019 Could not determine system default printer! Wed Jul 31 15:40:17 2019 find_previous_queue() in THREAD 140070619588288 Wed Jul 31 15:40:17 2019 get-printer-attributes IPP call failed on printer samsung (implicitclass://samsung/). Wed Jul 31 15:40:17 2019 ERROR: Unable to create print queue, ignoring printer. Wed Jul 31 15:40:17 2019 ERROR: Unable to allocate memory. Not sure where to continue now. I checked /etc/cups for changes in config files (.rpmsave), but nothing obvious there. Printing on the printserver or from another host does work. Those two run Leap 42.3. My laptop has Tumbleweed. Any hints? -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 0

[opensuse-support] Display is stuttering with kernel 5.2.x
by Mykola Krachkovsky 28 Jul '19

28 Jul '19

Hi, I've updated yesterday and got video stuttering, everything else works fine, system doesn't hang, no errors in journal. With kernel 5.1.16 displaying doesn't stutter. Bug is present in TTY as well as in X (actually in TTY it even worse). Here is bugreport: https://bugzilla.opensuse.org/show_bug.cgi?id=1143139 -- Kind regards, Mykola Krachkovsky -- Найкращі побажання, Микола Крачковський

3 3

[opensuse-support] 15.1 upgrade weirdness (bug?)
by Ralph 25 Jul '19

25 Jul '19

[Leap 15.0, xfce] A week or so ago I started to upgrade a Leap 15.0 system to 15.1 from DVD but yast installer could not find my wifi dongle. No functioning ethernet wire on this machine. The kernel in 15.1 does not have the drivers for the dongle (nor does 15; I use a kernel from stable which does have the module). Since I am going to upgrade to bigger nvme hardware on this machine soon, and thus will have to do a fresh install on the new hardware anyway, I just simply aborted the current really unnecessary upgrade through the normal yast installer buttons. Today I noticed that the repositories were all messed up. The extra repositories which I had elected to keep and manually edited from 15.0 to 15.1 during the preliminary upgrade process were still there, now correctly returned to their 15.0 versions, but the standard opensuse repositories were completely gone (oss, non-oss, updates, the dvd). No 15.0 versions nor 15.1 versions. I've manually reinstalled the standard 15.0 repositories but it seems to me this might be a bug in yast installer if it doesn't automatically completely revert a properly aborted upgrade process to its original configuration. Yes, bug? Or is this simply a case of "don't do that (abort an upgrade) and you won't ever have this problem"? Ralph -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 3

[opensuse-support] Two IP addresses on one interface and martians
by Peter Suetterlin 25 Jul '19

25 Jul '19

Hi list, I wonder if one of the network gurus around here can give me some hints on an issue I'm seeing here: We have a normal, visible IP address range for our observatory network. As we also have lots of guests that want internet access, I prefer to have them in a separate subnet (192.168 class), but using the same infrastructure. For this, the central server has two IP addresses on its (bonded) interface, and unknown clients get (via dhcp) an address in the 192 subnet, with the servers 192 address as gateway, and its set up to do forwarding and masquerading for them. This works fine (AFAICT) However, the server log is full of martians (ARP requests) like this Jul 25 09:00:26 helios kernel: IPv4: martian source 192.168.13.51 from 192.168.13.1, on dev bond0 Jul 25 09:00:26 helios kernel: ll header: 00000000: ff ff ff ff ff ff 00 e0 81 24 72 bf 08 06 .........$r... 13.51 is one of those unknown clients, 13.1 is the secondary address of bond0 As I understand martians, they would be packets arriving on an interface that is not configured for that network. But I do have both the address and a routing entry for it, so I'm not really sure why it is regarding those as martian. Is something wrong in my setup? Are they only logged, or completely discarded? Can/should I just disable martian logging for this interface? Or are there better solutions? -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 1

[opensuse-support] well supported usb wifi dongle ?
by Daniele 25 Jul '19

25 Jul '19

Hy guys, I need to move my router to another room so I have to switch my connection from cable to wifi. I don't want "small/nano dongle" (usually low range), I've found few models with good reviews but they need the rtl8822bu driver that is not in the kernel. Often all compatibility list are outdated. Any advices ? Thanks, Daniele. -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

4 4

[opensuse-support] Akonadi fails to start after latest Tumbleweed update (snapshot 20190721)
by Rodney Baker 25 Jul '19

25 Jul '19

Hi all, Sending this from Thunderbird because my KMail/Akonadi install is non-functional after updating to Tumbleweed snapshot 20190721). Running akonadictl start --verbose produces the following output: org.kde.pim.akonadiserver: Found mysql_install_db: "/usr/bin/mysql_install_db" org.kde.pim.akonadiserver: Found mysqlcheck: "/usr/bin/mysqlcheck" org.kde.pim.akonadiserver: Using mysqld: "/usr/sbin/mysqld" org.kde.pim.akonadiserver: Database "akonadidb" opened using driver "QMYSQL" org.kde.pim.akonadiserver: Running DB initializer org.kde.pim.akonadiserver: checking table "SchemaVersionTable" org.kde.pim.akonadiserver: "ALTER TABLE SchemaVersionTable ADD COLUMN version INTEGER NOT NULL DEFAULT 0" org.kde.pim.akonadiserver: "\nSql error: Duplicate column name 'version' QMYSQL: Unable to execute query\nQuery: ALTER TABLE SchemaVersionTable ADD COLUMN version INTEGER NOT NULL DEFAULT 0" org.kde.pim.akonadiserver: Unable to initialize database. org.kde.pim.akonadiserver: terminating connection threads org.kde.pim.akonadiserver: terminating service threads org.kde.pim.akonadiserver: Shutting down "NotificationManager" ... org.kde.pim.akonadiserver: stopping db process org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally... I've tried dropping the column in question so akonadi can recreate it, but then it generates the same error for the second column in SchemaVersionTable. If I drop SchemaVersionTable from the database, it fails on the next table. It seems as though akonadi is now trying to initialise the database from scratch, when it should simply be using the existing database as-is. I have no idea what's caused this - nothing has changed apart from zypper dup to the latest snapshot. It was working prior to the upgrade, and stopped working after the reboot. Yes, I can login to MariaDB using the configured akonadi user/password, I can use the configured database, I can view the schema and the tables and I can select data from the tables. I can't find a configuration option anywhere that could be forcing akonadi to initialise the database from scratch, but I may be looking in the wrong places. Any suggestions welcome. If there's no quick fix, looks like a bug report on the way. Regards, Rodney. -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 4

[opensuse-support] btrfs backup and reconstruction - to/from 2nd machine via ssh on Leap 15.1
by Sebastian M. Ernst 23 Jul '19

23 Jul '19

Hi all, I thought this was a pretty "standard scenario" - however, I failed to find reasonable tutorials or wikis about this subject. Please correct me if I am wrong. Idea: I have two machines, both running openSUSE Leap 15.1. Both use btrfs in openSUSE's standard configuration (except for /home, but this is beyond the scope of my question). I.e. there are subvolumes for /var, /usr/local, /tmp, /srv, /root, /opt, /boot/grub2/x86_64-efi and /boot/grub2/i386-pc. Both machines also run snapper, also in openSUSE's standard configuration. One machine is a workstation, the other is a data sink (i.e. a backup system or NAS). The backup system has plenty of unpartitioned and unformatted space available. The workstation is supposed to backup its subvolumes and snapshots (created by snapper) to the backup system. Right now, I do not care whether this is manual labor or a cron job - it's about principles. I am interested in how to configure both systems so that in the event of e.g. a disk failure in the workstation I am able to recover quickly and efficiently from my backups on the backup system. Just for fun, let's say in one scenario I want to recover to the exact same (wiped) harddrive in the workstation and in another scenario I want to recover to a new hard drive in the workstation. So far, I have not had a defect requiring such actions. And I surely do not want to provoke anything similar. However, I'd be very interested in going through the steps with two "live" virtual machines - all the way from system configuration, backup and "failure" to recovery. *Would someone here on this mailing list be willing to support this little experiment? I'd be more than happy to wrap the eventual findings into a readable wiki article / tutorial.* I have performed similar actions successfully with ZFS before (though not for root/system partitions). As far as ZFS is concerned, I am fairly certain about procedures and terminology. However, btrfs has slightly different interpretations of snapshots, subvolumes and mounting (configurations) and how (incremental) send/receive works on top of that. After studying various articles at btrfs.wiki.kernel.org I am admittedly left somewhat more confused than before. Best regards, Sebastian -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 3

Aw: [opensuse-support] Re: Re: Many problems since about Kernel 5.1.x on Tumbleweed Client - KDE isn't useable anymore
by ulfbart＠gmx.net 19 Jul '19

19 Jul '19

Hi Pete, > Gesendet: Mittwoch, 17. Juli 2019 um 11:39 Uhr; Von: "Hans-Peter Jansen" > > first of all, given our subscriptions succeeded, let's keep the discussion > here and only here, please, which will automatically avoid HTML as well ;-) OK, yes - I expected this - but was not simple possible with the webclient from gmx.net which I use due to the KDE trouble. > Am Dienstag, 16. Juli 2019, 15:39:08 CEST schrieb ulfbart(a)gmx.net: > > > Gesendet: Dienstag, 16. Juli 2019 um 13:07 Uhr; Von: "Hans-Peter Jansen" > > > Am Montag, 15. Juli 2019, 09:58:32 CEST schrieb ub22@xxxxxxx: > > > > Server (NFS 4 Server which is sharing /home config via YaST): > > |- Client1 (/home mounted via & user via NIS) > > > > > Using a similar setup here. > > FYI: I'm using {open,}SUSE since > 20 years as well in both, commercial and > private, settings. In the moment only private (network) for the Family. And as demonstrator for my LUG e.V. director. > > Yes, allways done by YasT: > > 1. Install NIS Client with Automount enabled > > This is the automount fstab pattern, that I use now: > > server:/path /net/server/path nfs noauto,x-systemd.automount,x-systemd.device- > timeout=10,timeo=14 0 0 OK, I will test them now. So my main PC I changed it and after the halt today night I will test it tomorrow. > > Depends on the user. I switched to an newer user and the > > Problem seams to be not available on it. I've only trouble > > to forward some settings like the kwallet which was > > encrypted with a key which seams to be on the new > > user in kleopatra and also in kwallet5 not visible. > > If kwallet5 finds a plain kwallet4 config, it tries to convert the wallet to > the new format with an assistant asking for both credentials. You need to > remove the damaged kwallet5 settings beforehand. You can export/import > kwallets manually as well. Is there a detailed description how to do it? So in the moment I find kwallet in: ~/.kde/share/apps/kwallet # the oldest ones ;-) ~/.kde4/share/apps/kwallet # the old ones ~/keys/ # ??? my copy ? - but I don't remind it ~/.local/share/RecentDocuments/kwallet_ulfi.xml.asc.desktop # ?? ~/.local/share/kwalletd # I think the new one ~/.mozilla/firefox/abc.default/extensions/kde5wallet(a)guillermo.molina # from old kwalletmanager or a new one ??? ~/.config/kwalletrc # the settings > I've had cases with very old KDE{3,4} configs, which had some trouble as well. > I tend to start with a new config then, and recover selective configs (e.g. > firefox bookmarks and passwords). kmail config should be started anew. Due to migration topics on KDE2, 3 and 4 I generated a new user but still the issue is similar with a totally new user > > > A general note: > > > > > > A NFS homed KDE is sub-optimal, when it comes to (heavy uses of) akonadi > > > et.al. Thus, I'm using a different scheme for power users: I place /home > > > on a > > > local ssd, and symlink everything interesting from my shared server home. > > > > akonadi on this user don't work, due to a mail account which can't be > > changed > > since years, so kmail crashes before I can open it. > > Given, you get the basics behave again, you can reanimate akonadi with: > > rm -rf /home/$USER/.local/share/akonadi I prevere to move it (backup was some days old - and stopped in the moment): $ mv ~/.local/share/akonadi ~/.local/share/akonadi.$(date +%F) how to proceed with the other folders in ~/.local/share/ ? akonadi-davgroupware/ akonadi_maildir_resource_0/ akonadi_migration_agent/ > and start over again. You need to adjust the folders for all email identities > in this case. This is anyway no issue, I will test it tomorrow, so it is to late today. > > But anyway, this looks crazy, so I expect that temporary files should be > > used > > on local /tmp which is on my side always on a fast SSD > > No, akonadi stores its databases in the path above. Use a symlink to relocate > that one onto your local ssd. OK, this option I can verify later. > > > server:/home /home/nfs nfs > > > nfsvers=4,x-systemd.requires=nfs-mountd.service,x- > > > > > >systemd.requires=/home 0 0 > > > > > > If kmail is still too slow, switch to postgresql for akonadi. > > > > I will doublecheck this later on. So in the moment I don't use kmail anymore > > I cannot confirm your experience. I'm using TW and KDE including kmail > successfully in NFS shared environments, but manage users with ldap, not yp. > Most data is hosted by NFS, including VBox VMs(!), and all is working well. OK, I will setup an LDAP as well, but at first I must refresh my LDAP knowladge which is very old and poor - any proposal for a good (best case german) manual? > Server: openSUSE 15.0, Clients: TW. All smooth. So today I made fschk on the Server on /boot/efi fs- and now it is empty :-( But I'm thinking to install the server again. Than I can use LEAP 15.1 as well instead of TW Regards Ulf -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 0

[opensuse-support] Since latest snapshot: TW does start only in rescue mode. "couln't get uefi list"
by stakanov 19 Jul '19

19 Jul '19

more or less that is what I find. the machine was running for long time and was suspended before the update. NVRAM may be full? How could I free it in order to boot? Thank you. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

4 7

[opensuse-support] Mailinglist outage yesterday
by Christian Boltz 19 Jul '19

19 Jul '19

Hello, (sorry for the massive cross-post - if you answer, please reply only on one mailinglist) TL;DR: If you sent a mail to one of the openSUSE mailinglists yesterday and it didn't arrive, please re-send it. Please also re-send any mail you sent to admin(a)o.o or board(a)o.o yesterday. Longer version: As you probably noticed by observing the silence in your inbox, the mailinglists were down yesterday. This downtime which had two reasons: a) postfix not starting on our outgoing mailserver after a kernel update and reboot - one of the server's IPs wasn't configured fast enough on boot and prevented starting postfix b) our mailinglist software needing additional AppArmor permissions after a kernel update. This is a known change for newer kernel versions, but shouldn't happen as part of a kernel update, therefore I opened https://bugzilla.opensuse.org/show_bug.cgi?id=1142120 The downtime started around 7:00 UTC (9:00 CEST). I noticed it in the evening, and around 21:50 UTC (23:50 CEST) everything worked again. a) wouldn't be too bad - the sending mailservers queues the mails, and they "just" get delayed. Unfortunately issue b) is more problematic - it seems the mailinglist software failed with $? = 0 so postfix thought the mails were successfully delivered, but in fact they are more or less lost. (Our mailinglist admin found them in the incoming/ directory, but he's on vacation with terrible internet access and probably can't do much about this in the next days. Sending out the then-old mails when he's back doesn't really make sense IMHO.) Therefore: If you sent a mail to one of our mailinglists yesterday and it didn't arrive, please re-send it. Please also re-send any mail you sent to admin(a)o.o or board(a)o.o yesterday. Regards, Christian Boltz -- Should you ever feel lonely or be overwhelmed with spare time: you know where to find us. [Dominique Leuenberger in opensuse-project] -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 0