October 2015 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Leap 42.1 beta: No network during DVD installation and more Fan noise
by Terje J. Hanssen 15 Oct '15

15 Oct '15

Some experiences: I have switched to Leap 42.1 x86_64/Gnome as my default boot system on two home machines, a stationary and a laptop workstation. While the DVD installation from M2 and Beta1 went well, I had bad experience with Build 222 and had to skip (ignore) several packages to come through the installation, and later zypper problems with the rpm database. The upgrade from the latest Build 223 and current repo went well again however. So now these two machines looks to work quite well, while waiting for the Packman 'multimedia repo' and Remmina ;) On the downside, I will remark that I was not able to configure neither wired nor wifi network for online repos during the installation or upgrade, After installation, both network were possible to configure normally using YaST. Another thing I have noticed, is more fan noise at full speed from the laptop, both during the installation itself and later often during startup and the first phase (minutes) after login. I had previous similar fan noise with the Nividia propriarity driver, but I see no reason why Leap should need more fan speed on a "cold laptop" than the "quiet 13.2" using Nouveau. --------------- Terje J. Hanssen -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 4

[opensuse-factory] Query about todays snapshot
by ianseeks 15 Oct '15

15 Oct '15

Hi Installing item 126/326 uninstalled the current version of kernel- desktop-4.2.1 and 155/326 installed the new version - shouldn't the new version be installed prior to the old being uninstalled in case the install procedure crashed badly between 127/326 and 154/326? regards Ian -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] todays snapshot raises a question
by ianseeks 15 Oct '15

15 Oct '15

Hi The installation of the following item finds all these outdated copies of vmlinuz/initrd in /boot, the question is, is (or should ) there an installation process to tidy up these files once they've been superseded or is it always seen as a housekeeping task for the admin? Ian ( 9/326) Installing: grub2-branding-openSUSE-13.2-11.3 .......................................................................................................................... [done] Additional rpm output: Generating grub configuration file ... Found theme: /boot/grub2/themes/openSUSE/theme.txt Found linux image: /boot/vmlinuz-4.2.1-1-desktop Found initrd image: /boot/initrd-4.2.1-1-desktop Found linux image: /boot/vmlinuz-4.1.6-3-desktop Found initrd image: /boot/initrd-4.1.6-3-desktop Found linux image: /boot/vmlinuz-4.1.6-2-desktop Found initrd image: /boot/initrd-4.1.6-2-desktop Found linux image: /boot/vmlinuz-4.1.6-1-desktop Found initrd image: /boot/initrd-4.1.6-1-desktop Found linux image: /boot/vmlinuz-4.1.5-1-desktop Found initrd image: /boot/initrd-4.1.5-1-desktop Found linux image: /boot/vmlinuz-4.1.4-1-desktop Found initrd image: /boot/initrd-4.1.4-1-desktop Found linux image: /boot/vmlinuz-4.1.3-2-desktop Found initrd image: /boot/initrd-4.1.3-2-desktop Found linux image: /boot/vmlinuz-4.1.3-1-desktop Found initrd image: /boot/initrd-4.1.3-1-desktop Found linux image: /boot/vmlinuz-4.1.2-1-desktop Found initrd image: /boot/initrd-4.1.2-1-desktop Found linux image: /boot/vmlinuz-4.1.1-1-desktop Found initrd image: /boot/initrd-4.1.1-1-desktop Found linux image: /boot/vmlinuz-4.0.5-3-desktop Found initrd image: /boot/initrd-4.0.5-3-desktop Found linux image: /boot/vmlinuz-4.0.5-1-desktop Found initrd image: /boot/initrd-4.0.5-1-desktop Found linux image: /boot/vmlinuz-4.0.4-3-desktop Found initrd image: /boot/initrd-4.0.4-3-desktop Found linux image: /boot/vmlinuz-4.0.4-2-desktop Found initrd image: /boot/initrd-4.0.4-2-desktop Found linux image: /boot/vmlinuz-4.0.4-1-desktop Found initrd image: /boot/initrd-4.0.4-1-desktop Found linux image: /boot/vmlinuz-4.0.3-1-desktop Found initrd image: /boot/initrd-4.0.3-1-desktop Found linux image: /boot/vmlinuz-4.0.1-1-desktop Found initrd image: /boot/initrd-4.0.1-1-desktop Found linux image: /boot/vmlinuz-4.0.0-1-desktop Found initrd image: /boot/initrd-4.0.0-1-desktop Found linux image: /boot/vmlinuz-3.19.4-1-desktop Found initrd image: /boot/initrd-3.19.4-1-desktop Found linux image: /boot/vmlinuz-3.19.3-1-desktop Found initrd image: /boot/initrd-3.19.3-1-desktop Found linux image: /boot/vmlinuz-3.19.2-1-desktop Found initrd image: /boot/initrd-3.19.2-1-desktop Found linux image: /boot/vmlinuz-3.19.1-2-desktop Found initrd image: /boot/initrd-3.19.1-2-desktop Found linux image: /boot/vmlinuz-3.19.1-1-desktop Found initrd image: /boot/initrd-3.19.1-1-desktop Found linux image: /boot/vmlinuz-3.19.0-2-desktop Found initrd image: /boot/initrd-3.19.0-2-desktop Found linux image: /boot/vmlinuz-3.19.0-1-desktop Found initrd image: /boot/initrd-3.19.0-1-desktop Found linux image: /boot/vmlinuz-3.18.3-2-desktop Found initrd image: /boot/initrd-3.18.3-2-desktop Found linux image: /boot/vmlinuz-3.18.3-1-desktop Found initrd image: /boot/initrd-3.18.3-1-desktop Found linux image: /boot/vmlinuz-3.18.1-1-desktop Found initrd image: /boot/initrd-3.18.1-1-desktop Found linux image: /boot/vmlinuz-3.17.4-1-desktop Found initrd image: /boot/initrd-3.17.4-1-desktop Found linux image: /boot/vmlinuz-3.17.2-1-desktop Found initrd image: /boot/initrd-3.17.2-1-desktop Found linux image: /boot/vmlinuz-3.17.1-1.g5c4d099-desktop Found initrd image: /boot/initrd-3.17.1-1.g5c4d099-desktop Found linux image: /boot/vmlinuz-3.16.6-2-desktop Found initrd image: /boot/initrd-3.16.6-2-desktop Found linux image: /boot/vmlinuz-3.11.10-21-desktop Found initrd image: /boot/initrd-3.11.10-21-desktop Found linux image: /boot/vmlinuz-3.11.6-4-desktop Found initrd image: /boot/initrd-3.11.6-4-desktop done -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] Opensuse Leap B1 - kded5, kdeinit5, kmix, kmixctrl crashing after login...
by André Verwijs 15 Oct '15

15 Oct '15

Opensuse Leap B1 - kded5, kdeinit5, kmix, kmixctrl crashing after login... see backtrace files...

2 1

[opensuse-factory] systemd ordering cycles affecting systemd-fsck-root.service?
by Brian "DragonLord" Wong 15 Oct '15

15 Oct '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Sorry if I sent this twice, Enigmail might have messed up the signature. After updating my experimental openSUSE Tumbleweed server to the latest snapshot, I experienced an unexpected technical issue that caused networking to randomly fail. After having stumbled upon the solution on the mailing list archives (http://lists.opensuse.org/opensuse-factory/2015-10/msg00243.html) I rebooted the server and continued to experience some systemd ordering cycle issues. Relevant dmesg output: > [ 1.797448] systemd[1]: nss-lookup.target: Dependency Before=nss-lookup.target dropped > [ 1.835699] systemd[1]: systemd-readahead-collect.service: > Cannot add dependency job, ignoring: Unit systemd-readahead-collect.service failed to load: No such file or directory. > [ 1.838411] systemd[1]: systemd-readahead-replay.service: > Cannot add dependency job, ignoring: Unit systemd-readahead-replay.service failed to load: No such file or directory. > [ 1.841274] systemd[1]: systemd-fsck-root.service: Found > ordering cycle on systemd-fsck-root.service/start > [ 1.842965] systemd[1]: systemd-fsck-root.service: Found > dependency on systemd-journald.socket/start > [ 1.844430] systemd[1]: systemd-fsck-root.service: Found > dependency on haveged.service/start > [ 1.845664] systemd[1]: systemd-fsck-root.service: Found > dependency on systemd-random-seed.service/start > [ 1.847163] systemd[1]: systemd-fsck-root.service: Found > dependency on systemd-remount-fs.service/start > [ 1.848607] systemd[1]: systemd-fsck-root.service: Found > dependency on systemd-fsck-root.service/start > [ 1.850116] systemd[1]: systemd-fsck-root.service: Breaking ordering cycle by deleting job systemd-journald.socket/start > [ 1.851787] systemd[1]: systemd-journald.socket: Job systemd-journald.socket/start deleted to break ordering cycle starting with systemd-fsck-root.service/start Is there still an issue with the way systemd or its units are configured? I'm a noob at systemd, so I might need some pointers to understand what's going on here. For clarity, it's a Linode VPS on a paravirtualized KVM hypervisor using their most current kernel (4.1.5-x86_64-linode61), but I doubt the kernel is the issue here as both my production server (openSUSE 13.2) and the experimental server prior to the upgrade were running properly with this kernel. Any idea what might be wrong here? - -- Brian "DragonLord" Wong http://www.fierydragonlord.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWHyWGAAoJEEUv29mnaAr0yasQAKuCxdTP4fWdVCMu8c/+SUq4 xo/AXf56ALrmnwqjjQcg0i+lFn5pvmdUkq7kzDuWnde3aLwhdG4F/5zkdEYIzOy5 UlVLUlGcBfQlBT3lFkx5S2B5yHJJUcr7U9DWkJ2cdM+7/ndjHCisK8d8VNNCi2Hk xsfdHl+BWZWCHvQy2lwq19kJV0waeRdcungt8VfaYZiQazc0AS1vdNdKaEymfzr5 2iJKShUy1yJlghLISQPy68vroHw3LudFOPtUMdgbEuRT8S2p2tZcudTfMgWU4CEt inJ7w5yzgwYQlOMeQAd+9pMAAd+qoVh5YTLPbDpd4awQmjUC5Dcdtb9i9Cy9Ma/r 8eqVLoWoNhV+nDXnRWmZMqpmjAwJ4HYC8x7lY+y36/FDWKv1kjfmy7msq6TzpxDf UJbt4RYNiLxeh21d/fWXwYt8Nc7LA5u7H7oKp7frG+6xB8VNquFVAxgMHCwjFPQO TUDoxxgmSEbeGeuqGuD2TbNqUoWDBrwrWiQDSjxPpStyKe473b++KsMutWGvlRrX t7uHytdR1kO2x99BESpv+RARwQsRhJf+bUTyeFeyKHs3m1Uvdct0fBeTLWZFfuqZ euxPu6gfnZG8Xx5cVVydtgqgz/5S6kpvHSuFjVeYph964M5fptp2jMKp+zB0izjw pLjGYmMhvHTVON1/q8cS =XWyq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] systemd ordering cycles affecting systemd-fsck-root.service?
by Brian "DragonLord" Wong 15 Oct '15

15 Oct '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 After updating my experimental openSUSE Tumbleweed server to the latest snapshot, I experienced an unexpected technical issue that caused networking to randomly fail. After having stumbled upon the solution on the mailing list archives (http://lists.opensuse.org/opensuse-factory/2015-10/msg00243.html) I rebooted the server and continued to experience some systemd ordering cycle issues. Relevant dmesg output: > [ 1.797448] systemd[1]: nss-lookup.target: Dependency Before=nss-lookup.target dropped > [ 1.835699] systemd[1]: systemd-readahead-collect.service: Cannot add dependency job, ignoring: Unit systemd-readahead-collect.service failed to load: No such file or directory. > [ 1.838411] systemd[1]: systemd-readahead-replay.service: Cannot add dependency job, ignoring: Unit systemd-readahead-replay.service failed to load: No such file or directory. > [ 1.841274] systemd[1]: systemd-fsck-root.service: Found ordering cycle on systemd-fsck-root.service/start > [ 1.842965] systemd[1]: systemd-fsck-root.service: Found dependency on systemd-journald.socket/start > [ 1.844430] systemd[1]: systemd-fsck-root.service: Found dependency on haveged.service/start > [ 1.845664] systemd[1]: systemd-fsck-root.service: Found dependency on systemd-random-seed.service/start > [ 1.847163] systemd[1]: systemd-fsck-root.service: Found dependency on systemd-remount-fs.service/start > [ 1.848607] systemd[1]: systemd-fsck-root.service: Found dependency on systemd-fsck-root.service/start > [ 1.850116] systemd[1]: systemd-fsck-root.service: Breaking ordering cycle by deleting job systemd-journald.socket/start > [ 1.851787] systemd[1]: systemd-journald.socket: Job systemd-journald.socket/start deleted to break ordering cycle starting with systemd-fsck-root.service/start Is there still an issue with the way systemd or its units are configured? I'm a noob at systemd, so I might need some pointers to understand what's going on here. For clarity, it's a Linode VPS on a paravirtualized KVM hypervisor using their most current kernel (4.1.5-x86_64-linode61), but I doubt the kernel is the issue here as both my production server (openSUSE 13.2) and the experimental server prior to the upgrade were running properly with this kernel. Any idea what might be wrong here? - -- Brian "DragonLord" Wong http://www.fierydragonlord.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWHyTrAAoJEEUv29mnaAr0RI0QALWHHZ1sa/iSXujH17pHME8S 8gRtdvANsFSv3mTldAMhNwTYsL8pFj8kNcAitXzLN2dH97/eO6+gqjh0MtO/b1zD w5C22J25n8LT3Afwy3xyBR9cdfHIq31H1o0nK9Ut1Uzgno9+/zovA514tirBQDeC D0w5wlkBNIKnGeANbvkbt+NSiE3wep1iAKSH1sNQ+pREyxrI9hcGorPfrSBptkcI UAm8NZ5BwA/L1cN8xBeZDA/J90QNuniLTitI04AF79bmnmnwql2jLUgMLFj+kxMW iVke4/XmFNKVnQhaPXibEukJonCRQe7EcPziyqDyu2WlyTLGQNXVW9Apr7OzRaBE UOIgBxFWJyz6sEgWLcL/XFuZ7MhvPo+Xa8nC1yjdJ7LBJPevU01OO3iMaxhNx75B 53seVZyMFARvASrvVbfPWadMoK5gXaMA8yCMTMIZulFyqVbjWg5nXfU7xbrNH77G dv84GeMl40ZH47aRZmkqCTZ3CKpUjKMQdqawwVsmxmaBeyvbjGhQ1S39JosX96i1 QXbJFIVs7c6xB4AIqKLd8rryHsXbGzwJSeM8vyYifJ7qoBZxB1hOvs8KtcPrx0h6 pvGaAx2C6tR7pW/yQsBJIwwdNFUVcuo2TyEkWVCtOTzW7gUHgwI1MKxHx3FZZ3+I jlDhS+DzC3FZYmYVckQW =l/3g -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Shutter missing in leap
by Michael Melcher 14 Oct '15

14 Oct '15

Hi, I noticed that shutter https://software.opensuse.org/package/shutter Is missing in Leap. Is it too late to add it? Kind regards Michael -- Kind regards Michael Melcher Sent from my phone -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Remmina missing in Leap 42.1 Milestone2
by Terje J. Hanssen 14 Oct '15

14 Oct '15

Hi List, Leap 42.1 Milestone 2 looks fine. I've installed it in tripple boot with openSUSE 13.2 and Tumbleweed. However, Remmina the remote desktop gui frontend is missing among the applications I use often on 13.2. It should be available in the OSS repo as it is on 13.2 Thanks, Terje J. Hanssen -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 5

[opensuse-factory] [opensuse] Re: why is perl broken?
by Yamaban 13 Oct '15

13 Oct '15

On Tue, 13 Oct 2015 20:37, Ruben Safir <ruben.safir@...> wrote: > On 10/13/2015 02:30 PM, Malcolm wrote: >> On Tue 13 Oct 2015 02:05:36 PM CDT, Ruben Safir wrote: >> >>> Can't locate ctime.pl in @INC (@INC contains: >>> /usr/lib/perl5/site_perl/5.20.1/i586-linux-thread-multi >>> /usr/lib/perl5/site_perl/5.20.1 >>> /usr/lib/perl5/vendor_perl/5.20.1/i586-linux-thread-multi >>> /usr/lib/perl5/vendor_perl/5.20.1 >>> /usr/lib/perl5/5.20.1/i586-linux-thread-multi /usr/lib/perl5/5.20.1 >>> /usr/lib/perl5/site_perl .) at /usr/lib/majordomo/config-test line 129. >>> >>> >>> is there a fix for this. I always end up recompiling perl and then >>> modperl and then apache. >> Hi >> Not broken it was deprecated.... >> >> Here's a thread, change the code to use POSIX; >> http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-viewthread+2376+2377 > > > that is a problem for majordomo and a ton of my own written scripts. Have a look at "perl-Time-modules", it contains the module Time::CTime. Maybe that could be a start for a workaround. - Yamaban. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Virtualbox broken on tumbleweed
by Flavio Castelli 13 Oct '15

13 Oct '15

Hi, Virtualbox is currently broken on tumbleweed because its kernel module has not been rebuilt against the latest kernel release. Right now on my machine I have the following packages: virtualbox-5.0.4-1.1.x86_64 virtualbox-host-kmp-desktop-5.0.4_k4.1.6_3-1.1.x86_64 virtualbox-guest-kmp-desktop-5.0.4_k4.1.6_3-1.1.x86_64 kernel-desktop-4.2.1-1.2.x86_64 I thought a kernel upgrade should automatically trigger a rebuilt of the virtualbox kernel packages. Cheers Flavio -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

20 41