February 2013 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] [12.3] Anticipated fix for gtg / update of python-liblarch
by Dimstar / Dominique Leuenberger 05 Feb '13

05 Feb '13

Reference: https://bugzilla.novell.com/show_bug.cgi?id=800684 Hi coolo, et al. We are planning to submit an update of python-liblarch to Factory and for inclusion into the 12.3 tree. This is required in order to fix gtg, which currently fails to start for an out-dated dependency. The risk of the update is 0%: - gtg is the only package in 12.3 depending on liblarch - Should the update introduce any weird behavior, the gtg cannot work less than it does now. A total of three requests are anticipated: - Update of python-liblarch (from 1.0 to 2.1.. looks bigger than it is) - A deleterequest for python-liblarch_gtk (it is now integrated into liblarch source tarball.. on the 'resulting side', no change: it is split in a own sub package - A 'fixup' to gtg, changing the python-liblarch requires to be versioned, depending on >= 2. With the consensus of the project and the release manager, we will prepare the push. Best regards, Dominique -- 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] 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] Owl TCB patch uniq to suse and ASP linux glibc? Why? Are the GLIBC incompat symbols necessary?
by Linda Walsh 05 Feb '13

05 Feb '13

* Both archives also include the Owl tcb patch updated to apply after the corresponding crypt_blowfish support patch. Unfortunately, the documentation updates found in Owl have been dropped from this quick and dirty update of the patches. * Forward ports of the patches from Owl to shadow-4.0.12 by Vincent Danen crypt_blowfish is fully integrated into Owl, distributions by ALT Linux team, and Annvix as the default password hashing scheme. It is part of the glibc package on SUSE Linux and ASPLinux. ^^^^^^^^^^ Part of the reasoning for forcing various incompatible changes has been because everyone else is doing it -- just to note, that doesn't seem to be the case here. What is the Owl TCB patch and why was it included in SUSE and why did it define a uniq symbol that gets required by all the binaries built with it (so you can't upgrade to a newer glibc that doesn't have these special additions ... I'm not sure how much I care if I have blowfish or such, over the other crypt mechanisms..... at least not if it means my software portability is easily damaged... -- 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] Tumbleweed, klipper: have lost default config
by Patrick Shanahan 04 Feb '13

04 Feb '13

I use klipper quite frequently and recently lost all actions. I noticed some time ago, quite a while, that klipper appeared to have hidden actions somewhere, none appear in: configure klipper -> actions display window is blank But actions still worked, <rt><click> on a url and a menu pops up offering selectable actions. No more. A recient update seems to have cleared the ?? default actions and they are not in ~/.kde4/share/config/klipperrc. I have archives showing that they have not been there since at least 1 Sept 2012. I *can* add actions but would like to return to the default provided when installed. Where are they hidden, akonadi*? -- (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

1 0

[opensuse-factory] no sound from speakers on 12.3b1, vbox
by Patrick Shanahan 04 Feb '13

04 Feb '13

I get to sound output on 12.3b1 KDE setup test shows output on pavumeter but there is no sound. volume is set to 100% and not muted. systemctl says sound card loaded/active: 82801AA AC'97 Audio Controller set vlc backend, was gstreamer. no difference don't know where else to look tks, -- (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

4 5

[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] Default partition setup suggests removing of existing Linux (but keeps Windows :) )
by Andrey Borzenkov 02 Feb '13

02 Feb '13

I'm setting up multiboot system for testing; I installed Windows, Fedora and am installing current Factory. This has three HDD with each system on separate disk. Two disks are used, one is empty. I was a bit surprised to see default suggestion to remove existing Fedora install. Are we on war with Fedora or what? :) Third disk is completely empty and avaiable. So there was really no reason to offer to remove anything. Just wonder if this is intentional or should be considered a bug?\ P.S. one more annoying thing that there seems to be no way to actually return to this default suggestion. Once you click past initial Suggested Partitioning step, you never get back at it. -- 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] Can't submit bug report
by Andrey Borzenkov 02 Feb '13

02 Feb '13

I fill in bug report, press "Submit" - and nothing happens at all. It worked yesterday. Something with bnc? -- 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] [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