January 2015 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Re: INSTALL FAILS: Upcoming update for shim requires confirmation on reboot
by jsegitz＠suse.com 23 Jan '15

23 Jan '15

On Thu, Jan 22, 2015 at 02:21:51PM -0500, Patrick Shanahan wrote: > Installation fails on my 13.1 server. > Hangs at: + /sbin/update-bootloader --reinit I just tried to reproduce the problem but couldn't. Please open a bug (and try if update-bootloader --reinit hangs if you run it manually. It should not) Johannes -- GPG Key E7C81FA0 EE16 6BCE AD56 E034 BFB3 3ADD 7BF7 29D5 E7C8 1FA0 Subkey fingerprint: 250F 43F5 F7CE 6F1E 9C59 4F95 BC27 DD9D 2CC4 FD66 SUSE LINUX GmbH Maxfeldstraße 5 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg)

2 2

Re: [opensuse] dropbox
by Roger Oberholtzer 23 Jan '15

23 Jan '15

For me, on a 13.1 system, dropbox always wants to update itself when I log in if my network includes a wired connection. If it is wireless-only, it does not do this. I have decided to consider it a quirky cute feature as I do not usually have a wired connection on this computer. My network is not managed by ifup/traditional, so neither interface is up when I log in. But maybe the wired one comes up quicker so dropbox gets a chance to look for updates. Just a guess. On Fri, Jan 23, 2015 at 7:46 AM, Roger Oberholtzer <roger.oberholtzer(a)gmail.com> wrote: > For me, on a 13.1 system, dropbox always wants to update itself when I log > in if my network includes a wired connection. If it is wireless-only, it > does not do this. I have decided to consider it a quirky cute feature as I > do not usually have a wired connection on this computer. My network is not > managed by ifup/traditional, so neither interface is up when I log in. But > maybe the wired one comes up quicker so dropbox gets a chance to look for > updates. Just a guess. > > On Thu, Jan 22, 2015 at 8:51 PM, John Andersen <jsamyth(a)gmail.com> wrote: >> >> On 01/22/2015 10:22 AM, Paul Groves wrote: >> > For the last couple of weeks on my desktop only (not on my laptop or >> > work computer) dropbox is showing in the system tray with a big black >> > box surrounding the usual white logo. >> > >> > I have not installed anything new other than the regular updates. >> > I have rolled back using snapper >> > I have removed dropbox and the .dropbox and .dropbox-dist directories >> > from my home folder and re-installed dropbox. >> > >> > Any ideas? >> > >> >> Dropbox started going through the install process every time I reboot. >> >> >> This happened when I encrypted my home directory. >> It turns out that dropbox silently updates itself in ~/.dropbox.dist >> and that is where your dropbox loads from. >> >> But it seems to load and try to run before I even get a chance to key in >> my decryption password for >> home, and as such it can't launch, and drops back to thinking I need to >> authenticate and add my >> account again. >> >> I think I read that some part of systemd is involved somehow, but its not >> clear to me how >> this could work. >> >> >> >> >> -- >> After all is said and done, more is said than done. >> -- >> To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org >> To contact the owner, e-mail: opensuse+owner(a)opensuse.org >> > > > > -- > Roger Oberholtzer -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] dropbox
by Paul Groves 22 Jan '15

22 Jan '15

For the last couple of weeks on my desktop only (not on my laptop or work computer) dropbox is showing in the system tray with a big black box surrounding the usual white logo. I have not installed anything new other than the regular updates. I have rolled back using snapper I have removed dropbox and the .dropbox and .dropbox-dist directories from my home folder and re-installed dropbox. Any ideas? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] INSTALL FAILS: Upcoming update for shim requires confirmation on reboot
by Patrick Shanahan 22 Jan '15

22 Jan '15

* Johannes Segitz <jsegitz(a)suse.com> [01-16-15 09:09]: > we will release a security update for shim next week that fixes three > security issues, tracked in bnc#889332: > - OOB read access when parsing DHCPv6 packets (remote DoS) (CVE-2014-3675). > - Heap overflow when parsing IPv6 addresses provided by tftp:// DHCPv6 boot > option (RCE) (CVE-2014-3676). > - Memory corruption when processing user provided MOK lists (CVE-2014-3677). > > Because of those issues we update shim to version 0.7.318.81ee561d. This > version includes a patch that requires the user to confirm a dialog once > on the first boot after the update is installed. You will need to be able > to confirm this dialog, which appears before the bootloader, or your system > will not boot. This only affects users that are still on openSUSE 13.1 and > use a secure boot setup. You can check with 'bootctl' if you're using a > secure boot configuration if you're not sure. Installation fails on my 13.1 server. Hangs at: + /sbin/update-bootloader --reinit Logs: 08:29 wahoo: /var/cache/zypp/packages/repo-update/x86_64 # rpm -Uhvvv ./shim-0.7.318.81ee561d-7.2.x86_64.rpm D: ============== ./shim-0.7.318.81ee561d-7.2.x86_64.rpm D: loading keyring from pubkeys in /var/lib/rpm/pubkeys/*.key D: couldn't find any keys in /var/lib/rpm/pubkeys/*.key D: loading keyring from rpmdb D: opening db environment /var/lib/rpm cdb:private:0x201 D: opening db index /var/lib/rpm/Packages 0x400 mode=0x0 D: locked db index /var/lib/rpm/Packages D: opening db index /var/lib/rpm/Name nofsync:0x400 mode=0x0 D: read h# 1 Header SHA1 digest: OK (b0d86230a3899ea0e94d19d76dfc7a9700fca8c5) D: added key gpg-pubkey-307e3d54-4be01a65 to keyring D: read h# 1310 Header SHA1 digest: OK (1469533e8536aa7267f6567bbdc17415c8547785) D: added key gpg-pubkey-392ffa88-51f00be3 to keyring D: read h# 1396 Header SHA1 digest: OK (0238a3db899f61935a55058a369d6763351a1386) D: added key gpg-pubkey-9591c39b-51971adb to keyring D: read h# 1708 Header SHA1 digest: OK (cda5c10fb660a86cf544f1585c79dc83f951cae3) D: added key gpg-pubkey-ddcd7f1a-51318b5b to keyring D: read h# 1953 Header SHA1 digest: OK (c26f82e18c835b10068e54dbfa94818941ecd435) D: added key gpg-pubkey-9056621d-50f6ef88 to keyring D: read h# 1992 Header SHA1 digest: OK (195ca3394a33f95be4c5a9c5498c55a0f3424f57) D: added key gpg-pubkey-0f2672c8-50f6b041 to keyring D: read h# 2722 Header SHA1 digest: OK (22c19fc0b82edc93ba43a149752cac323eb3284f) D: added key gpg-pubkey-c0951497-53515432 to keyring D: read h# 2723 Header SHA1 digest: OK (3710dbdc7146d5f5e2879c64dfe4b8a1542b865d) D: added key gpg-pubkey-ee454f98-53515440 to keyring D: read h# 2725 Header SHA1 digest: OK (66971eaf91d670b694659a33e42061c5b5467075) D: added key gpg-pubkey-3dbdc284-53674dd4 to keyring D: read h# 2730 Header SHA1 digest: OK (4588eb4871596b18274e6ea8198fc72ba31b5011) D: added key gpg-pubkey-0ae6233b-53ba5c52 to keyring D: read h# 2799 Header SHA1 digest: OK (f69ae5ae97d84ceb4d7845419921d071c276c66a) D: added key gpg-pubkey-ce4c0d2f-53b4640d to keyring D: read h# 2966 Header SHA1 digest: OK (feaa68173c427f2e313f06558ff561275666ba7a) D: added key gpg-pubkey-bd6d129a-510add01 to keyring D: Using legacy gpg-pubkey(s) from rpmdb D: Expected size: 472700 = lead(96)+sigs(772)+pad(4)+data(471828) D: Actual size: 472700 D: ./shim-0.7.318.81ee561d-7.2.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 3dbdc284: OK D: read h# 424 Header V3 RSA/SHA256 Signature, key ID 3dbdc284: OK D: added binary package [0] D: found 0 source and 1 binary packages D: opening db index /var/lib/rpm/Conflictname nofsync:0x400 mode=0x0 D: ========== +++ shim-0.7.318.81ee561d-7.2 x86_64/linux 0x0 D: opening db index /var/lib/rpm/Basenames nofsync:0x400 mode=0x0 D: read h# 2981 Header V3 RSA/SHA256 Signature, key ID 3dbdc284: OK D: Requires: /bin/bash YES (db files) D: Requires: /bin/sh YES (db files) D: opening db index /var/lib/rpm/Providename nofsync:0x400 mode=0x0 D: read h# 1754 Header V3 RSA/SHA256 Signature, key ID 3dbdc284: OK D: Requires: grub2-efi YES (db provides) D: read h# 579 Header V3 RSA/SHA256 Signature, key ID 3dbdc284: OK D: Requires: perl-Bootloader YES (db provides) D: Requires: /bin/sh YES (cached) D: Requires: rpmlib(PayloadFilesHavePrefix) <= 4.0-1 YES (rpmlib provides) D: Requires: rpmlib(CompressedFileNames) <= 3.0.4-1 YES (rpmlib provides) D: Requires: rpmlib(PayloadIsLzma) <= 4.4.6-1 YES (rpmlib provides) D: opening db index /var/lib/rpm/Obsoletename nofsync:0x400 mode=0x0 D: ========== --- shim-0.2-3.1 x86_64/linux 0x0 D: opening db index /var/lib/rpm/Requirename nofsync:0x400 mode=0x0 D: ========== recording tsort relations D: ========== tsorting packages (order, #predecessors, #succesors, depth) D: 0 0 0 1 +shim-0.7.318.81ee561d-7.2.x86_64 D: 1 0 0 1 -shim-0.2-3.1.x86_64 D: installing binary packages D: Selinux disabled. D: closed db index /var/lib/rpm/Obsoletename D: closed db index /var/lib/rpm/Conflictname D: closed db index /var/lib/rpm/Providename D: closed db index /var/lib/rpm/Requirename D: closed db index /var/lib/rpm/Basenames D: closed db index /var/lib/rpm/Name D: closed db index /var/lib/rpm/Packages D: closed db environment /var/lib/rpm D: opening db environment /var/lib/rpm cdb:private:0x201 D: opening db index /var/lib/rpm/Packages (none) mode=0x42 D: locked db index /var/lib/rpm/Packages D: sanity checking 2 elements D: opening db index /var/lib/rpm/Name nofsync mode=0x42 D: read h# 424 Header V3 RSA/SHA256 Signature, key ID 3dbdc284: OK D: running pre-transaction scripts D: computing 20 file fingerprints D: opening db index /var/lib/rpm/Basenames nofsync mode=0x42 D: opening db index /var/lib/rpm/Group nofsync mode=0x42 D: opening db index /var/lib/rpm/Requirename nofsync mode=0x42 D: opening db index /var/lib/rpm/Providename nofsync mode=0x42 D: opening db index /var/lib/rpm/Conflictname nofsync mode=0x42 D: opening db index /var/lib/rpm/Obsoletename nofsync mode=0x42 D: opening db index /var/lib/rpm/Triggername nofsync mode=0x42 D: opening db index /var/lib/rpm/Dirnames nofsync mode=0x42 D: opening db index /var/lib/rpm/Installtid nofsync mode=0x42 D: opening db index /var/lib/rpm/Sigmd5 nofsync mode=0x42 D: opening db index /var/lib/rpm/Sha1header nofsync mode=0x42 Preparing... D: computing file dispositions D: 0x0000fd01 4096 11598826 3150267 / D: 0x0000fd02 4096 3817577 1301974 /var ################################# [100%] D: ========== +++ shim-0.7.318.81ee561d-7.2 x86_64-linux 0x0 D: Expected size: 472700 = lead(96)+sigs(772)+pad(4)+data(471828) D: Actual size: 472700 D: shim-0.7.318.81ee561d-7.2.x86_64: Header V3 RSA/SHA256 Signature, key ID 3dbdc284: OK D: install: shim-0.7.318.81ee561d-7.2 has 12 files Updating / installing... 1:shim-0.7.318.81ee561d-7.2 D: ========== Directories not explicitly included in package: D: 0 /etc/ D: 3 /usr/lib64/ D: 5 /usr/sbin/ D: 6 /usr/share/doc/packages/ D: ========== D: create 040755 3 ( 0, 0) 0 /etc/uefi D: create 040755 2 ( 0, 0) 0 /etc/uefi/certs D: create 100644 1 ( 0, 0) 1144 /etc/uefi/certs/4659838C.crt;54c0fb6d D: create 040755 2 ( 0, 0) 0 /usr/lib64/efi D: create 100644 1 ( 0, 0)1283752 /usr/lib64/efi/MokManager.efi;54c0fb6d D: create 100644 1 ( 0, 0) 64512 /usr/lib64/efi/fallback.efi;54c0fb6d D: create 100444 1 ( 0, 0) 1144 /usr/lib64/efi/shim-opensuse.der;54c0fb6d D: create 100755 1 ( 0, 0)1294048 /usr/lib64/efi/shim-opensuse.efi;54c0fb6d ################################# [ 50%] D: create 120777 1 ( 0, 0) 17 /usr/lib64/efi/shim.efi;54c0fb6d D: create 100755 1 ( 0, 0) 7868 /usr/sbin/shim-install;54c0fb6d D: create 040755 2 ( 0, 0) 0 /usr/share/doc/packages/shim D: create 100644 1 ( 0, 0) 1411 /usr/share/doc/packages/shim/COPYRIGHT;54c0fb6d XZDIO: 83 reads, 2655680 total bytes in 0.055314 secs D: adding "shim" to Name index. D: adding 12 entries to Basenames index. D: adding "System/Boot" to Group index. D: adding 8 entries to Requirename index. D: adding 2 entries to Providename index. D: adding 8 entries to Dirnames index. D: adding 1 entries to Installtid index. D: adding 1 entries to Sigmd5 index. D: adding "b345736ed59e558e4179a4e84f1dfee17c4b737b" to Sha1header index. D: %post(shim-0.7.318.81ee561d-7.2.x86_64): scriptlet start D: %post(shim-0.7.318.81ee561d-7.2.x86_64): execv(/bin/sh) pid 30193 + /sbin/update-bootloader --reinit -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] please replace/repair the packages made previously availble in patch openSUSE-2015-42
by grantksupport＠operamail.com 22 Jan '15

22 Jan '15

Could whoever/whatever broke, removed, or otherwise 'disappeared' the packages/versions previously made available in distro patch/update @ http://lists.opensuse.org/opensuse-updates/2015-01/msg00044.html please put them back? specifically, the libzypp versions >= 14.30. those had been introduced https://bugzilla.suse.com/show_bug.cgi?id=899510#c3 and enabled backward INCOMPATIBLE changes to repo files. with those versions removed, zypper up's forcing downgrades to libzypp <= 14.29 -- which will now cause zypper to break with those changes in place. the newer versions are no longer available in the repos, nor is the referenced patch, openSUSE-2015-42 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] Re: How to recover a damaged partition
by Joseph Loo 22 Jan '15

22 Jan '15

On 01/21/2015 08:45 PM, Kevin O'Gorman wrote: > > > On Wed, Jan 21, 2015 at 8:13 PM, Kevin O'Gorman <kogorman(a)gmail.com > <mailto:kogorman@gmail.com>> wrote: > > > > On Wed, Jan 21, 2015 at 7:27 PM, Joseph Loo <jloo20111002(a)gmail.com > <mailto:jloo20111002@gmail.com>> wrote: > > On 01/21/2015 06:53 PM, Kevin O'Gorman wrote: > > I'm working with new 4TB drives, and one of them just had a > bad spot in > a fairly awkward place. > The very first block of an ext4 partition was unreadable, > and caused > problems in booting, as well as anything else that wanted to > scan > partitions. > > I overwrote the first 4K with zeroes, deleted the partition > (with gdisk) > and created a new unformatted partition to cover the area. > Now that > partition passes a read test, and I'm checking the other > partitions. > > The damaged partition has been inactive for a while, so I'm > quite sure I > have adequate backups. But now seems to be a time for me to > learn -- > lots of things have been going wrong, and I've been learning > how to cope. > > So I wonder if there's a way to get that partition back, at > least in > part, without using my backups. > > Any hints, pointers, tutorials, or opinions welcome. > > Have you tried doing a badblocks on the partition. This will try > reading and writing data to the partition to check the disk > drive. I generally do this on my drive before deploying. It > tends to remove the bad blocks. > > You can also try grc's Spinrite (cost money) at grc.com > <http://grc.com> > > -- > > > I have not run it, but following the advice in its man page, I'll > run e2fsck with the -c option on the two partitions that showed > errors in ddrescue. > > Bad blocks in an inode table. Yuck. Too many errors to make the > partition recoverable I'll finish up with ddrescue... Sheesh! > > Now the question is whether I can score a warranty return. All the new drives have a lot of disk errors. The 750 GB drives and higher have higher error rates. The reason I do a badblock, is to exercise the drive and try to remove the bad blocks before they become a problem. The spare sectors on the drive will then replace the bad blocks thus saving the sector issue. badblocks probably will work but I found out that spinrite (all of them take a long time) seems to clean more of the errors before the drive starts showing problems. In the old days, the disk manufacturers use to do formats that clean out these problems. Another way of doing it is to use windows and do an ntfs full format. It too will try to remove all the bad blocks. The current drives do not do this. -- Joseph Loo jloo(a)acm.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

[opensuse] wicked, save-apply configurations
by Stanislav Baiduzhyi 22 Jan '15

22 Jan '15

Decided to install the system without NM, only with wicked. Now I cannot find any info anywhere on how to apply full network configuration with wicked. At home I have wifi, static IP, manually set route and DNS. At the office I have ethernet+DHCP. Leaving as is does not work because of DNS (not sure about the route), so every time I move to another location I have to open yast and change route/DNS settings accordingly. It is ok for me to run that as a command after the boot manually. Or maybe it is possible to change the configuration in /etc/sysconfig/network and then tell either yast or wicked to reinitialize the network to apply the changes in that config? -- Regards, Stas -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 8

Re: [opensuse] please replace/repair the packages made previously availble in patch openSUSE-2015-42
by grantksupport＠operamail.com 22 Jan '15

22 Jan '15

On Wed, Jan 21, 2015, at 05:47 PM, Patrick Shanahan wrote: > * grantksupport(a)operamail.com <grantksupport(a)operamail.com> [01-21-15 20:24]: > > On Wed, Jan 21, 2015, at 05:10 PM, Patrick Shanahan wrote: > > > an answer to this question/demand was posted to list in the last several > > > hours. The zypper package was "broken" and slipped bye. > > > > Thanks. > > > > For anyone interested, found it here: http://lists.opensuse.org/opensuse/2015-01/msg00612.html > > > > Imo, we have too many lists, &/or no clear guidance/policy where breakage like this is announced; you'd think that if a patch/update is announced on opensuse-updates, then any change/breakage/rollback to it should also be posted there. > > > > Also re-raises old questions of why/how it's allowed to push & publish updates before a stable, non-broken state is verified, AND that once done, there's no "current-1" snapshot, or other backup, to rollback to. Other topics ... > > You do realize that your post is private, not to the list, or both lists > against list netiquette. > > You do realize that your post is private, not to the list, or both lists > against list netiquette. Seriously? Well, gee-willikers -- my bad for just clicking "Reply to all ..." oh wait. Then again -- maybe you shouldn't have first responded to ME only "against list nettiquette": ------ Return-Path: <ptilopteri(a)gmail.com> ... Date: Wed, 21 Jan 2015 20:10:53 -0500 From: Patrick Shanahan <ptilopteri(a)gmail.com> To: grantksupport(a)operamail.com Subject: Re: [opensuse] please replace/repair the packages made previously availble in patch openSUSE-2015-42 Message-ID: <20150122011053.GC3960(a)wahoo.no-ip.org> Mail-Followup-To: grantksupport(a)operamail.com References: <1421886690.4030279.217141201.0F8A1C99(a)webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1421886690.4030279.217141201.0F8A1C99(a)webmail.messagingengine.com> X-Operating-System: Linux 3.11.10-25-desktop x86_64 openSUSE 13.1 Organization: Ptilopteri in Pandemonium User-Agent: Mutt/1.5.21 (2010-09-15) X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 ------ How's that? better ON the list? Wow ... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] zypper went backwards?
by John Andersen 21 Jan '15

21 Jan '15

In Yast today, I noticed that Zypper (and friends) is in red (newer than what is available) Alternate Version Installed Version 1.11.14-2.1 1.11.17-5.1 I haven't changed repositories since many months. Why is this going backwards in version numbers? -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3

[opensuse] Accessing a USB-disk as normal user
by Koenraad Lelong 21 Jan '15

21 Jan '15

Hi, This is not the first time I experience this, but now I wanted to ask. I formatted (EXT4) a new disk in a USB-to-SATA enclosure. All is fine. But when it is mounted via the "tray", I can't access it, I don't have rights to write on the disk. What I'm doing now is adding a directory as root and chowning that directory to my user. Then I can use that directory as storage. Is this the way to go or am I missing something ? On OS13.1. Koenraad. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 15