February 2013 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] syslog-ng 3.4?
by Peter Czanik 08 Feb '13

08 Feb '13

Hello, I just read, that openSUSE 12.3 is already feature freeze now... syslog-ng just released 3.4 RC1 now and we expect a final release in the coming weeks. The beta was running stable on my machines for weeks. It's a leaf package, not installed by default. I wonder, if I could still update syslog-ng from 3.3 in Base:System and in Factory to 3.4RC1 and later on to 3.4.1 once released. Bye, CzP -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 3

[opensuse-factory] rc1 netinstall?
by Peter Czanik 08 Feb '13

08 Feb '13

Hello, I tried an rc1 netinstall, but it failed. First it complained, that it can only be done in insecure mode, then it downloaded a couple more files and failed without any possibility to continue. Is it a bug or it's because repos for network install are not yet on-line? Bye, CzP -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 5

[opensuse-factory] LVM not available in rescue mode
by Andrey Borzenkov 08 Feb '13

08 Feb '13

I had problems with root on LVM and booted from installation in rescue mode. No device node for LVM was available and no group was active. I activated them but still no device node. Apparently now "rescue mode" on DVD simply does "systemctl isolate emergency.target". So nothing is started including udevd. After manually launching it and reactivating LVM I finally got access to root. This is current 12.3 (net boot, loading miniroot from net). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] [12.3 RC1] nvidia driver 310.32 install fails
by 0x90 07 Feb '13

07 Feb '13

Hi, anybody already figured out why nvidia installer fails now in RC1 (installed from openSUSE-12.3-DVD-Build0024-x86_64.iso)? In Beta 1 nvidia installer worked with this old workaround: cd /usr/src/linux make cloneconfig make prepare cd /lib/modules/`uname -r`/source/arch/x86/include/ cp -v generated/asm/unistd*.h ./asm/ but now in RC1 this annoying error again: # cat /var/log/nvidia-installer.log nvidia-installer log file '/var/log/nvidia-installer.log' creation time: Thu Feb 7 16:38:49 2013 installer version: 310.32 PATH: /usr/lib64/mpi/gcc/openmpi/bin:/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/usr/lib/mit/bin:/usr/lib/mit/sbin nvidia-installer command line: ./nvidia-installer Using: nvidia-installer ncurses user interface -> License accepted. -> Installing NVIDIA driver version 310.32. -> Running distribution scripts executing: '/usr/lib/nvidia/pre-install'... -> done. -> Performing CC sanity check with CC="cc". -> Performing CC version check with CC="cc". -> Kernel source path: '/lib/modules/3.7.6-1.2-desktop/source' -> Kernel output path: '/lib/modules/3.7.6-1.2-desktop/build' ERROR: If you are using a Linux 2.4 kernel, please make sure you either have configured kernel sources matching your kernel or the correct set of kernel headers installed on your system. If you are using a Linux 2.6 kernel, please make sure you have configured kernel sources matching your kernel installed on your system. If you specified a separate output directory using either the "KBUILD_OUTPUT" or the "O" KBUILD parameter, make sure to specify this directory with the SYSOUT environment variable or with the equivalent nvidia-installer command line option. Depending on where and how the kernel sources (or the kernel headers) were installed, you may need to specify their location with the SYSSRC environment variable or the equivalent nvidia-installer command line option. ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for details. You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com. greetings, 0x90 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] NFS not mounting
by Steven Hess 07 Feb '13

07 Feb '13

I set up the NFS client in Yast2 but none of the shares I added are mounting. Any ideas? I see them in fstab If I open the directories they are empty. Fresh net install of 12.3 this afternoon my time. Steven -- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 Google Voice 661 769 6201 +SMS openSUSE Linux 12.1 KDE 4.7.2 Known as FlameBait and The Sock Puppet of Doom. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] [12.3RC1] install=nfs:// broken (tested with OSS Repo and Net DVD)
by Joschi Brauchle 07 Feb '13

07 Feb '13

Hi, I am testing 12.3 with NFS based installation but unfortunately this is broken currently. When specifying "install=nfs://..." boot parameter, the system hangs before fetching the installation system via NFS. This does not happen when specifying "install=http://...", so it may be a problem with the NFS module of the 3.7.x kernel/initrd? Running wireshark on the NFS server shows that nothing arrives there, so the install system seems to block before making any NFS requests. The bug was reported here: https://bugzilla.novell.com/show_bug.cgi?id=799496 but it's still stuck in the screening phase and I fear it may not make it until 12.3 final, hence this post. Who would be the right person to assign the above bug to? Best regards, -J Brauchle

1 0

[opensuse-factory] Beta1 stuck in boot phase after dup
by Josef Reidinger 06 Feb '13

06 Feb '13

Hi, Yesterday I upgrade my virtual machine via zypper dup to current opensuse snapshot. After dup system works fine. Problem happen when I reboot. Then system stuck during boot. Few notable things I see * plymouth boot failed with see systemctl ... * xdm start succeed but nothing shown * I get no console where I can login ( even if systemd start all services except failed plymouth), how can I login to obtain some logs or see what and why failed? after 11 minutes multiple lines of segfault in mandb start occuring with lines mandb[<pid>]: segfault at 7fffd708c000 ip 00007fc543de5a6b sp 00007fffd7089fe8 error 4 in libc-2.17.so[7fc543d5e000+1a3000] If I boot with 3 to just console with X it stuck same way ( just no xdm of course ). In this case mandb do not print segfaults. Any ideas how can I proceed at least to console login and to start debugging it? Thanks Josef -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

7 23

[opensuse-factory] IS grub2 dead or not?!
by Basil Chupin 06 Feb '13

06 Feb '13

Saturday, February 02, 2013: The Linux Foundation has sponsored a major revamp of the mini bootloader to help users to launch any version of Linux on computers that come with UEFI Secure Boot. Whenever UEFI Secure Boot is talked along with Linux, the first thought that comes to our mind is Windows 8. Though UEFI Secure Boot is not something new or synonymous with Windows 8 but Microsoft made Secure Boot popular particularly when it was initially discovered that Windows 8 devices won't allow Linux to boot. The restructuring of the bootloader boots in a different manner, allowing it to work well together with Gummiboot. Unlike GRUB, the Gummiboot accesses the EFI mechanisms before starting Linux. So, the Gummiboot keeps the structure simple as compared to GRUB. However, when the user has activated the Secure Boot, the procedure changes and other firmware-related mechanisms comes to play to verify the kernel before launching it. http://www.efytimes.com/e1/fullnews.asp?edid=99636 BC -- Using openSUSE 12.2 x86_64 KDE 4.10.0 & kernel 3.7.5-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

11 24

[opensuse-factory] Applications linking against both gstreamer-0.10 and gstreamer-1.0
by Guido Berhoerster 06 Feb '13

06 Feb '13

Since the introduction of gstreamer-1.0 into Factory we now have a mix of programs and libraries linking against one or the other. The trouble is that the gstreamer-* libraries do not use symbol versioning and in some cases progams end up linking to both versions, mostly through indirect shared library dependencies or object which are dlopen'd at runtime. E.g. currently all GTK2/3 applications indirectly link to gstreamer-1.0 through the libcanberra-gtk-module and some directly link against gstreamer-0.10 at the same time, see https://bugzilla.novell.com/show_bug.cgi?id=800963. While this particular case may be solved by removing libcanberra-gtk-module as Dominique offered, there are probably more of such cases and there is the problem that people developing on openSUSE will run into trouble when linking against certain combinations of libraries which have different gstreamer versions in their dependency tree. Identifying such cases is also not straightforward, the dependency information from repository metadata is not helpful since it only covers the package level, directly resolving library dependency trees via recursive ldd turns out to be extremely slow and also does not cover dlopen'd plugins etc. Any ideas how to systematically determine which packages are actually affected by this and how to address this probem before the 12.3 release? -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 14

[opensuse-factory] [12.3] Polished Branding
by Richard Brown 05 Feb '13

05 Feb '13

RE: Submit Request 151407 https://build.opensuse.org/request/show/151407 Hi coolo, et al. We've opened the above SR for an update of branding-openSUSE to Factory and would also like it's inclusion into the 12.3 tree This is needed as the current branding package includes several rough drafts that were thrown in at the last minute before freeze to ensure that 12.3 would have at least something 'new' in many core branding areas The new package is the product of the artwork team working at the Marketing hackathon to polish up 12.3 ready for release. This new package includes the following: Cleaner plymouth booth theme with fade down on shutdown (myself). Welcome text in multiple foreign languages have been removed to address user concerns (eg. bnc#801872) Improved Grub 2 Theme (by myself & anditosan) - this Grub2 theme is not only in the 12.3 style but attempts to make the display of the terminal window more acceptable than the clashing black square we had to deal with in 12.2 Improved xfce splash in 12.3 style (victorhck) Updated gfxboot backgrounds (tux93) These improvements will improve the users first experience with 12.3 when they first boot up their ISO/CD/DVD, which is why we cant realistically provide these improvements through 12.3/Update We don't expect any more changes to this package, and if they are, it is almost certain they will be best delivered as Updates (ie. I'm hoping to break with tradition and make sure you get asked this only once this release ;-p Next time, we aim for zero!) Thank you for considering the request Regards Richard Brown Branding Package Maintainer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0