April 2019 - openSUSE Users - openSUSE Mailing Lists

[opensuse] tumbleweed update from 20190403 to 20190409 qemu-kvm windows-xp guest did not start
by Simon Becherer 16 Apr '19

16 Apr '19

Hi, update tumbleweed from 20190403 to 20190409 try to start with virt-manager qemu-kvm windows xp professionel guest. was running without problems before, now windows did not boot, not in save mode. always falling back to the windows screen where i could choose save mode or start normal. what must i change that it will start again? thanks, simooN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 3

RE: [opensuse] zypper up: access denied error
by Hermann-Josef Beckers 16 Apr '19

16 Apr '19

-----Original Message----- From: Hermann-Josef Beckers Sent: Thursday, April 11, 2019 3:43 PM To: 'Per Jessen' <per(a)computer.org> Subject: RE: [opensuse] zypper up: access denied error > I went back to the "download.opensuse.org" repo entries and it works again. > Thanks for all replies. Wrote to early. Since switching to download.opensuse.org I get no updates. My actual "zypper lr --details" output pasted as: http://susepaste.org/12434989 http://paste.opensuse.org/12434989 A "zypper -v up" run is pasted as: http://susepaste.org/41262599 http://paste.opensuse.org/41262599 A lot (117) of packages wont be installed? Yours Hermann-Josef Beckers

3 9

[opensuse] Enter password to unlock your keyring?
by Istvan Gabor 15 Apr '19

15 Apr '19

Hello: I tried to set up VPN in networkmanager. When I tried to save the configuration a window titled "Unlock login keyring" appeared saying: "Enter password to unlock your login keyring. The login keyring did not get unlocked when you logged into your computer." I uploaded a screenshot of that widow here: http://i64.tinypic.com/der886.jpg (susepaste.org did not load) This window completely disabled writing text in any other window (terminal, document editor). I have no idea what login keyring is and what password the window expects. I worked with vpn clients (cisco vpnclient and shrew ike) previously but they run their system service daemons and I did not have to enter any extra passwords to make them work (only my vpn password). Can someone please enlighten my what this is all about, what login keyring is, what password that window asks for and how to avoid constant requests for extra passwords? A link to some good manual or documentation would be also helpful. Thank you in advance, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

[opensuse] Flightgear causes removal of Nvidia driver.
by Carlos E. R. 15 Apr '19

15 Apr '19

#### YaST2 conflicts list - generated 2019-04-15 15:02:52 #### FlightGear-2017.3.1-lp150.1.8.x86_64 requires FlightGear-data = 2017.3.1, but this requirement cannot be provided not installable providers: FlightGear-data-2017.3.1-lp150.1.3.noarch[download.opensuse.org-oss] [ ] break FlightGear-2017.3.1-lp150.1.8.x86_64 by ignoring some of its dependencies [ ] do not install FlightGear-2017.3.1-lp150.1.8.x86_64 [ ] Following actions will be done: downgrade of FlightGear-data-2018.3.2-lp150.24.2.noarch to FlightGear-data-2017.3.1-lp150.1.3.noarch install FlightGear-data-2017.3.1-lp150.1.3.noarch (with vendor change) obs://build.opensuse.org/games --> openSUSE downgrade of FlightGear-docs-2018.3.2-lp150.24.2.noarch to FlightGear-docs-2017.3.1-lp150.1.3.noarch install FlightGear-docs-2017.3.1-lp150.1.3.noarch (with vendor change) obs://build.opensuse.org/games --> openSUSE deinstallation of nvidia-computeG03-340.107-lp151.12.2.x86_64 deinstallation of x11-video-nvidiaG03-340.107-lp151.12.2.x86_64 or: #### YaST2 conflicts list - generated 2019-04-15 15:06:16 #### FlightGear-2017.3.1-lp150.1.8.x86_64 requires libSimGearCore.so.2017.3.1()(64bit), but this requirement cannot be provided not installable providers: libSimGearCore-2017_3_1-2017.3.1-lp150.1.3.x86_64[download.opensuse.org-oss] [ ] Following actions will be done: deinstallation of nvidia-computeG03-340.107-lp151.12.2.x86_64 deinstallation of x11-video-nvidiaG03-340.107-lp151.12.2.x86_64 [ ] break FlightGear-2017.3.1-lp150.1.8.x86_64 by ignoring some of its dependencies [ ] do not install FlightGear-2017.3.1-lp150.1.8.x86_64 -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

1 0

[opensuse] Getting apcupsd to work
by James Knott 14 Apr '19

14 Apr '19

I just installed apcupsd and have connected an APC BE600M1 600VA UPS. I installed the apcupsd package, along with apcupsd cgi & gui. According to Yast Services Manager, apcupsd has failed. What am I missing to get this to work? tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 6

[opensuse] default ipv6 route is lost (after a while)
by Per Jessen 14 Apr '19

14 Apr '19

I'm running Leap15 on a couple of small NanoPi Neo Air. The network is configured with dhcp and radvd, the latter also hands out the default route. Today I noticed that both had lost their default routes: nano1:~ # uptime 18:06:44 up 9 days 7:31, 1 user, load average: 0.00, 0.00, 0.00 nano1:~ # ip -6 route show 2001:db8::1::/64 dev wlan0 proto kernel metric 256 expires 85071sec pref medium fe80::/64 dev wlan0 proto kernel metric 256 pref medium After a reboot, the default route is back: nano1:~ # uptime 18:22:47 up 0:00, 1 user, load average: 1.03, 0.29, 0.10 nano1:~ # ip -6 route show 2001:db8::1::/64 dev wlan0 proto kernel metric 256 expires 86381sec pref medium fe80::/64 dev wlan0 proto kernel metric 256 pref medium default via fe80::1 dev wlan0 proto ra metric 1024 expires 1781sec hoplimit 64 pref medium I've put up some monitoring to try to determine when the route is lost, but why would it be lost at all?? -- Per Jessen, Zürich (9.2°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 45

[opensuse] Permission problem - I need another pair of eyes.
by Carlos E. R. 14 Apr '19

14 Apr '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In a nutshell: cer-g@Isengard:/data/My_Book/Fusion/Videos> l Conviction/ ls: cannot open directory 'Conviction/': Permission denied cer-g@Isengard:/data/My_Book/Fusion/Videos> l | grep Conviction/ drwxrwxr-T+ 3 cer cer 33 Jun 21 2017 Conviction/ cer-g@Isengard:/data/My_Book/Fusion/Videos> pwd /data/My_Book/Fusion/Videos cer-g@Isengard:/data/My_Book/Fusion/Videos> whoami cer-g cer-g@Isengard:/data/My_Book/Fusion/Videos> groups users cer cer-g@Isengard:/data/My_Book/Fusion/Videos> cer-g@Isengard:/data/My_Book/Fusion> l total 12 drwxr-xr-x 3 cer cer 28 Jul 20 2018 ./ drwxr-xr-x 4 root root 34 Nov 3 18:29 ../ drwxrwxr-T+ 52 cer cer 8192 Apr 12 03:43 Videos/ cer-g@Isengard:/data/My_Book/Fusion> cer-g@Isengard:/data/My_Book/Fusion/Videos> mount | grep My /dev/mapper/cr_my_book on /data/My_Book type xfs (rw,nosuid,nodev,relatime,lazytime,attr2,inode64,noquota,user) cer-g@Isengard:/data/My_Book/Fusion/Videos> User "cer-g" is member of groups "users" and "cer" Directory has group permission "rwx" and is owned by "cer:cer" Same for parent directory. The user "cer-g" is denied access to the directory "Conviction/" and others. Why? I also have this: cer-g@Isengard:/data/My_Book/Fusion/Videos> getfacl Conviction # file: Conviction # owner: cer # group: cer # flags: --t user::rwx user:wwwrun:r-x group::--- mask::rwx other::r-- man getfacl says: Lines 5, 7 and 10 correspond to the user, group and other fields of the file mode permission bits. These three are called the base ACL entries. Lines 6 and 8 are named user and named group entries. Line 9 is the effective rights mask. This entry limits the effective rights granted to all groups and to named users. (The file owner and others permissions are not affected by the effective rights mask; all other entries are.) Lines 11--15 display the default ACL associated with this directory. Directories may have a default ACL. Regular files never have a default ACL. I'm a bit list here. My intention was to give user wwwrun read access (which it does have, apache works). But the line "group::---" confuses me. - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXLDu4xwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVHX8AoJTG6pR9Y04Len/nOv3B G0CzH+WQAJwJCuu3RAvvQLdQDjAsNmKe2Pz2tQ== =Iaxt -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 21

[opensuse] KDE *.desktop app association
by Roger Oberholtzer 11 Apr '19

11 Apr '19

I posted a question a while back about an issue with icons on the KDE desktop. No conclusion was drawn. I have new info. The issue is that when clicking on a file.desktop icon in Dolphin, the file is opened in kate. The expected behavior is, or course, to run the application defined in the file.desktop file. An example of such a file is: #!/usr/bin/env xdg-open [Desktop Entry] BinaryPattern= Comment[en_US]=Configure RSofT Comment=Configure RSofT Exec=xterm -geometry 110x55 -T "Configure RSofT" -e change GenericName[en_US]= GenericName= Icon=/opt/rsoft/lib/images/icons/setup.png MimeType= Name[en_US]=Configure RSofT Name=Configure RSofT Path= ServiceTypes= StartupNotify=true SwallowExec= SwallowTitle= Terminal=false Type=Application X-DBUS-ServiceName= X-DBUS-StartupType=none X-DCOP-ServiceType=none X-KDE-SubstituteUID=false X-KDE-Username= Things are inconsistent. In Dolphin, the Type is correctly listed as "desktop configuration file". And the icon shown for it is the one defined in the file. And when right-clicking on it to edit it's Properties, a dialog for editing these kinds of files is shown. The Application tab has the expected fields for a .desktop file. However, when clicking on the icon, it opens in the kate editor. Upon further investigation, I see that the file association for *.desktop files is set to kate. It is like this on openSUSE 42.3 and on Tumbleweed. Surely this is incorrect. The icon does everything it should do - except it's main business: run the application it defines. There is not much utility in an icon that does not execute the command it defines. Am I missing something? Is the file association for *.desktop files wrong? If so, what should it be? If not, what use are these files? Note that when on the desktop, they do execute when clicked on. But they do not do this anywhere else. I am fairly certain that back in the dark days of KDE3 they executed in Dolphin no matter where they were located. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

[opensuse] zypper up: access denied error
by Hermann-Josef Beckers 11 Apr '19

11 Apr '19

Since updating to 15.0, a "zypper -v up" sometimes gives an "access denied" error for some files (see below). Looking with a browser into the "ftp.gwdg.de/..." structure, I can see the files and can/could download them. "LANG=En_US zypper -v up ... Overall download size: 178.1 MiB. Already cached: 229.4 MiB. After the operation, additional 394.8 MiB will be used. Continue? [y/n/...? shows all options] (y): y committing In cache MozillaFirefox-60.6.1-lp150.3.45.1.x86_64.rpm (1/149), 41.4 MiB (154.4 MiB unpacked) Retrieving package apache2-utils-2.4.33-lp150.2.14.1.x86_64 (2/149), 158.5 KiB (202.2 KiB unpacked) Retrieving: apache2-utils-2.4.33-lp150.2.14.1.x86_64.rpm ......................[error] Permission to access 'http://ftp.gwdg.de/pub/opensuse/update/leap/15.0/oss/rpms/x86_64/apache2-ut…' denied. Abort, retry, ignore? [a/r/i/...? shows all options] (a): r Retrieving: apache2-utils-2.4.33-lp150.2.14.1.x86_64.rpm ......................[error] Permission to access 'http://ftp.gwdg.de/pub/opensuse/update/leap/15.0/oss/rpms/x86_64/apache2-ut…' denied. Abort, retry, ignore? [a/r/i/...? shows all options] (a): a Problem occurred during or after installation or removal of packages: Installation aborted by user Please see the above error message for a hint." List of my repositories: "zypper lr Die Repository-Prioritäten sind ohne Effekt. Alle aktivierten Repositorys teilen sich die gleiche Priorität. # | Alias | Name | Aktiviert | GPG-Überprüfung | Aktualisierung ---+-------------------------------------+-----------------------------------------------------------------------------------+-----------+-----------------+--------------- 1 | CODE | CODE | Nein | ---- | ---- 2 | adobe | adobe | Nein | ---- | ---- 3 | devel_libraries_c_c++ | A project for basic libraries shared among multiple projects (openSUSE_Leap_15.0) | Nein | ---- | ---- 4 | http-download.opensuse.org-3d6396a6 | openSUSE:infrastructure | Ja | (r ) Ja | Ja 5 | http-download.opensuse.org-cef1e4ca | home:vitsoft:freepbx | Ja | (r ) Ja | Ja 6 | oss150dvd | oss150dvd | Ja | ( p) Ja | Nein 7 | repo-non-oss | openSUSE-Leap-15.0-Non-Oss | Nein | ---- | ---- 8 | repo-oss | openSUSE-Leap-15.0-Oss | Nein | ---- | ---- 9 | repo-update | openSUSE-Leap-15.0-Update | Ja | (r ) Ja | Ja 10 | repo-update-non-oss | openSUSE-Leap-15.0-Update-Non-Oss | Ja | (r ) Ja | Ja " Any hints? Thanks Hermann-Josef Beckers -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 6

[opensuse] Trying to understand the opensuse release cycle of updates, packages, patches, security updates
by cagsm 11 Apr '19

11 Apr '19

Kind LPs, was always trying to understand the opensuse release mechanisms and cycles of packages, updates, patches, security fixes etc. To bridle the horse from behind, updates/fixes arrive e.g. at: <http://download.opensuse.org/update/leap/15.0/oss/rpms/x86_64/?C=M;O=D> Before that, I kinda figured, there would be the place at: <http://download.opensuse.org/update/leap/15.0-test/> How does stuff from -test move over to the final area? Are the files the very same and are only moved over, so binary identical, signatures and hash files identical? I recall this recent incident when the whole final update directory was hosed and needed to be rebuilt from scratch just like a week ago and files were regenerated all over. So before test, or related to test, there is the build system with all kinds of weird things and abbreviations :), swamp integration, obs build request tickets <https://build.opensuse.org/request/show/690934> inside bugzilla tickets there be whiteboard entry lines > obs:running:123456:important and what not Often I see respins of packages (e.g. kernel here) with the hints of adding or removing stuff over again due to regressions etc. intel i915 module and so on just as an example. Anyone care to explain a bit more details of these things, especially the last steps, from aboce, when and how does a package file land in test, do all of the releases land in there, who or what tests them, voluntarily community testing, or some automated testing of those files as well, and how and when do they move over to the final area and be released, or do they be built over again from scratch to make em land in final place and so forth. Is the testing directory area be discussed somewhere? Is there a list or a place or a group or forum, who and where they test this place and then they push or flag them after successfull testing for a general release? TIA. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2