January 2013 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] How to use multiple versions of same library on 1 system?
by Linda Walsh 05 Feb '13

05 Feb '13

Unix has it, Linux has it, Windows has it -- the ability to have multiple versions of libraries (like GLIBC) on a system with the ability to run programs from multiple MAJOR OS releases, on the same system. So why aren't we building our apps and libs to work that way in OpenSuse? Starting with the 12.X series, it seems the problem has gotten significantly worse. Binaries from each of the 12.x versions are often mutually incompatible -- most often because each version has been hard-coded to accept only 1 version of GLIBC. GLIBC isn't supposed to be changing it's interface so radically that each app needs to be hard coded to only work with 1 version. In versions prior to 12.x, requirements were put on the rpm's to make sure the unique version of Glibc an app wanted was 'installed'. That wasn't hard to work around, as one could install the markers in the rpm-database and glibc linked apps would run fine with the newest version of libc installed. Currently we have version 6 of the libc library libc.so.6. All of the 12.x series is linked to this file, BUT all have specified exact internal versions of each compatible version of libc.so.6 : GLIBC_2.14, GLIBC_2.15, GLIBC_2.16? Why are apps specifying internal symbols to link against? linux has a facility for linking to specific versions of libc.so.6: libc.so.6.2.14 can live with libc.so.6.2.15 and libc.so.6.2.16. All can be installed , if *NECESSARY* (which, in my experience usually isn't necessary until 'libc.so.7' comes out), and apps provably have a need for a specific minor version, can specify which minor version by filename. So why are we hardcoding specific libc.so.6 revisions into the binaries? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

11 38

[opensuse-factory] X segfaulting on 12.3 B1?
by C 04 Feb '13

04 Feb '13

I've run into a problem with X segfaulting and crashing the Windows manager. This started happening on my 12.2 that was using Factory KDE4,9.97 and 98, and it's also happening on the same hardware with 12.3B1 with KDE4.9.97. Nvidia binary drivers are both 310 and 313, but currently 313.09. I'm not sure what is the root cause.. maybe someone here can help me track it down? On 12.3B1, I can run most desktop apps with no issues, but once in a while, depending on the app, it will crash to the login screen. I've been able to trigger this with Steam Linux (on 12.2 and 12.3), and with VMWare Player (on 12.2... will be testing on 12.3 as soon as I get it installed). The behaviour is the same every time; launch the app, and immediate SegFault. On the previous 12.2 install it only started happening when I updated KDE to 4.9.98. Previously I was running an older version of KDE4.9.X from Factory. I forget the exact build.. I think it was .93. /var/log/messages only contains one line at the time that X crashed (previous line is from several minutes earlier and unrelated): -------------------------------------------------- 2013-01-28T18:18:55.833377+01:00 linux-oqn4 kdm[569]: X server for display :0 terminated unexpectedly -------------------------------------------------- /var/log/Xorg.0.log contains this: -------------------------------------------------- [ 66721.084] (EE) Backtrace: [ 66721.090] (EE) 0: /usr/bin/Xorg (xorg_backtrace+0x36) [0x58f906] [ 66721.090] (EE) 1: /usr/bin/Xorg (0x400000+0x193769) [0x593769] [ 66721.090] (EE) 2: /lib64/libpthread.so.0 (0x7f6374927000+0xf1f0) [0x7f63749361f0] [ 66721.090] (EE) 3: /usr/lib64/libnvidia-glcore.so.313.09 (0x7f636fb79000+0x14dfbd0) [0x7f6371058bd0] [ 66721.090] (EE) 4: /usr/lib64/libnvidia-glcore.so.313.09 (0x7f636fb79000+0x15f409b) [0x7f637116d09b] [ 66721.090] (EE) 5: /usr/lib64/libnvidia-glcore.so.313.09 (0x7f636fb79000+0x15f67a8) [0x7f637116f7a8] [ 66721.090] (EE) 6: /usr/lib64/libnvidia-glcore.so.313.09 (0x7f636fb79000+0x12cec34) [0x7f6370e47c34] [ 66721.090] (EE) 7: /usr/lib64/xorg/modules/extensions/libglx.so (0x7f637227f000+0x4bb2ad) [0x7f637273a2ad] [ 66721.090] (EE) [ 66721.091] (EE) Segmentation fault at address 0x0 [ 66721.091] Fatal server error: [ 66721.091] Caught signal 11 (Segmentation fault). Server aborting -------------------------------------------------- Any tips an where to look for the cause? I don't want to raise a bug with no useful information. I've searched through the Factory bugs... and didn't find anything similar. C. -- openSUSE 12.3B1 x86_64, KDE 4.9.97 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 6

Re: [opensuse-factory] [Tumbleweed] Calibre 0.9.13 failed to install
by Greg KH 04 Feb '13

04 Feb '13

On Thu, Jan 31, 2013 at 10:07:58AM +1100, Trent Hawkins wrote: > Hi Greg, > > I'm still getting this error on latest Zypper dup. > > Although the latest version available now is calibre-0.9.16-118.1.x86_64 from > obs://build.opensuse.org/KDE. This fails to install with the same error as > before. Please file a bug against the calibre package, nothing I can do here, sorry. greg k-h -- 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] [openSUSE 12.3 Beta 1] No battery discharge information available - powertop or acpi
by Trent Hawkins 02 Feb '13

02 Feb '13

Hi, I'm running - openSUSE-KDE-LiveCD-Build0348-x86_64.iso, on a live-usb. I was trying to determine the power discharge rate on my laptop while the adapter was unplugged, but could not do this. Powertop gives me no power consumption rate as it would normally with the adapter offline and running acpi gives the following output: linux:/home/linux # acpi -V Battery 0: Discharging, 90%, rate information unavailable Battery 0: design capacity 5600 mAh, last full capacity 5055 mAh = 90% Adapter 0: on-line Thermal 0: ok, 53.5 degrees C Thermal 0: trip point 0 switches to mode critical at temperature 99.0 degrees C Cooling 0: Processor 0 of 3 Cooling 1: Processor 0 of 3 Cooling 2: Processor 0 of 3 Cooling 3: Processor 0 of 3 Cooling 4: LCD 0 of 15 Cooling 5: LCD 0 of 15 So the adapter is On-line (even though it certainly disconnected), but the battery reports that it is discharging at a rate that is unavailable! Any thoughts? Otherwise shaping up to be a great release! Regards, Trent -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 6

[opensuse-factory] Net install iso 12.3b1 build-348 fails
by Patrick Shanahan 01 Feb '13

01 Feb '13

x86_64 VirtualBox three attempts to install 12.3 beta 1 Net iso (build 348) failed. Each at install of grub2. subsequent attempt with kde-live-cd-build-351 also fails in graphics mode, but doesn't get as far. It doesn't even open the graphics install screen. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

[opensuse-factory] Mono maintainership
by Cristian Morales Vega 01 Feb '13

01 Feb '13

Could somebody clarify the situation with Mono in openSUSE after Attachmate fired the entire mono team? First, somebody knows for sure if bnc-team-mono(a)forge.provo.novell.com goes somewhere other than /dev/null? And then, given Andrew doesn't want to be the *main* maintainer of anything (https://bugzilla.novell.com/show_bug.cgi?id=796901#c3). Could whoever is a real maintainer of the Mono projects clean the situation? "ajorgensen" is set as the only maintainer of a lot of packages. And what's worse, that's a dead account... Andrew now uses the user "ajorg". There are six packages from Mono:Factory failing to build for Factory... it has been that way for more than a month and a half. If there is a lack of real maintainers (I hope there is at least one) you should publicly ask for more. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 12

[opensuse-factory] Fast Startup patch for the ntfs-3g driver in openSUSE 12.3?
by Roman Bysh 01 Feb '13

01 Feb '13

Hello all, Is openSUSE including the "Fast Startup" patch for the ntfs-3g driver in openSUSE 12.3? I've read that Knoppix 7.05 already includes the Fast Startup patches in the ntfs-3g driver. Cheers! Roman ------------------------------------------------------- openSUSE -- Get it! Discover it! Share it! ------------------------------------------------------- http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 6

[opensuse-factory] Reminder: we're in feature freeze
by Stephan Kulow 31 Jan '13

31 Jan '13

Hi, I'm still getting tons of stupid version updates thrown at me. Get real guys - unless you come up with *really* good arguments *on this list* I don't see any reason to take it. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

15 41

[opensuse-factory] YaST text interface colors (ncurses)
by Karl Eichwalder 30 Jan '13

30 Jan '13

Are there still YST text interface users out there? I just install 12.3 Beta1 (build 348) in vbox (on 12.2). First part was pretty ok (blueish), but now the second part is rather green: Some text are unreadable, and after staring more than a minute at it, I have the feeling that I'm somehow blinded. Trying to attach a screen shot: Do we want to keep it that way? If yes, there need to be an easy way to switch back to the traditional blue skin. -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)

12 12

[opensuse-factory] MariaDB as a default MySQL
by Michal Hrusecky 30 Jan '13

30 Jan '13

Hi everybody, as some of you might know, we have two MySQL implementations in openSUSE: * mysql-community-server - MySQL Community Server as provided by Oracle * mariadb - MariaDB from Monty Program We were offering both for a long time, letting users choose and we are still doing that and I don't see that changing in a near future. But one of these variants has to be default and I sent a request to change this default to MariaDB for openSUSE 12.3. What does it mean? ================== Actually, not much. As written on MariaDB web page[1], MariaDB is a binary drop in replacement for MySQL. So from almost all points of view it behaves completely the same. If you will switch, you probably wouldn't even notice. And as we are still providing Oracles MySQL (don't worry, that one will NOT go away, I know some of you really need it), you can decide to stick with it. Switching on server part can be done easily[2], so you can switch there and back as much as you want. So what will actually change? We do provide only one devel package, so everything will be compiled against MariaDB and embedded library will be using MariaDB. But as protocol is still the same, all programs will be able to talk to both MySQL and MariaDB no matter against what they were compiled. And if you wouldn't choose and wouldn't care, you'll end up with MariaDB. If you are using Oracles MySQL and you will update to 12.3, you'll still be using Oracles MySQL after the update. So overall, even though there is a change, you shouldn't notice much difference ;-) Why to switch? ============== MariaDB is getting a lot of attention[3] and frankly I'm using it since 11.4 on my own server so it is even more tested by me. They periodically merge with Oracles MySQL and add some of their own or Perconas or somebody else goodies[4] on top of that. Originally I was sticking to Oracles MySQL as a default to keep it conservative and stable, but over the years MariaDB proved to be stable and lately they were even faster in fixing some security issues (although they might be the guys who found them, so comparison might not be fair). I'm not saying that I'm unhappy with Oracles MySQL, I know that there is plenty of people doing great job at Oracle pushing MySQL forward, but I believe that new default will bring some more goodies to our users without any unpleasant side-effects. And as we believe in choice, you can still choose Oracles MySQL over MariaDB. It's up to you. And as I said before, what is default MySQL actually doesn't mean much in openSUSE ;-) [1] https://kb.askmonty.org/en/mariadb-versus-mysql-compatibility/ [2] http://en.opensuse.org/SDB:Switching_between_MySQL_variants [3] http://www.zdnet.com/wikipedia-moving-from-mysql-to-mariadb-7000008912/ [4] https://kb.askmonty.org/en/mariadb-versus-mysql-features/ -- Michal HRUSECKY SUSE LINUX, s.r.o openSUSE Team Lihovarska 1060/12 PGP 0xFED656F6 19000 Praha 9 mhrusecky[at]suse.cz Czech Republic http://michal.hrusecky.net http://www.suse.cz -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 7