July 2014 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Migrating from Tumbleweed to Factory
by Patrick Shanahan 26 Jul '14

26 Jul '14

Took the plunge and migrated my production maching from Tumbleweed to Factory. Mind I have quite a few extra "Tumbleweed build" repos enabled. I made a copy of /etc/zypp/repos.d and edited all active to reflect the correct locations for openSUSE-Factory, including renaming for identity purposes. I backed up the current /etc/zypp and replaced repos.d with the edited copies. Major conflict/resolution list primarly between perl 5.20 and yast packages. Found easiest solution to singularly install perl 5.20 and allow a few package downgrades. Only took two steps and entire system appears as one would expect,ie: no conflicts New kernel 3.16 boots fine. Major Problems With Graphical Display: I have nVidia 450 GTS Had NVIDIA-Linux-x86_64-331.49-custom.run active but was unable to get it to work with kernel 3.16. Dl'd NVIDIA-Linux-x86_64-340.24.run and it installed fine, but... Now the graphic display was sunk in ~1 inch on all four sides and streatched widthwise Have now recovered the Graphical Display, found the /etc/X11/xorg.conf file was not good for the system for some unknown reason. It had been fine for 13.1/Tumbleweed and Tumbleweed previous from the beginning of Tumbleweed. I generated a new xorg.conf with nvidia-xconfig. But I do not know why this was necessary. I found the zypper locks have changed and I cannot figure how to lock multiple repos for a particular package so I made individual locks. The old locks were not correct for openSUSE-Factory. The Graphical Display really had me stumped and I really only recovered due to educated guesses. Life goes on. tks, questions welcome. -- (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-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] humongous /var/log/pbl.log
by Felix Miata 24 Jul '14

24 Jul '14

64 bit host big31: 12.3: total size 14,075K tail, all lines for most recent day's activity 992,744 bytes, 9553 lines 13.1: total size 38,404K tail, all lines for most recent day's activity 221,134 bytes, 2133 lines 13.2: total size 79,629K tail, all lines for most recent day's activity 682,444 bytes, 9001 lines Are these expected sizes? Shouldn't they be rotated out as .xz like happens to zypper.log and messages? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 8

[opensuse-factory] The future of Tumbleweed
by Greg KH 24 Jul '14

24 Jul '14

Hi all, This came up on the linux-kernel mailing list in a side thread, and I have since had a few people ask me about this on IRC, so I'd like to just consolidate all of the questions here into one thread. I no longer run openSUSE Tumbleweed on my main machines as it is not useful to me anymore. This is not to say that I am no longer maintaining Tumbleweed, thanks to the magic of obs, I am able to keep it up to date just fine by using the obs command line tools from any Linux distro. In fact, most of all of the updates in the past 6 months have been made from a server running Gentoo[1] :) But what this does mean is while I keep checking to see if I made any _major_ mistakes with it, by keeping a virtual machine up to date, and a spare laptop working with it, I am much less likely to notice any problems that occur when running the distro. So, what's my future plans with it? I don't know. I can keep on keeping it up to date as-is, which seems to work as I haven't had any complaints in the past 3-4 months, as no one seems to have noticed... Ideally, Tumbleweed will die with the use of Factory in its place. Factory is a great goal, and one that I really want to see happen, as it fits into my working model (constantly updating stable distro), but from what I have been told, it's just not quite there yet. thanks, 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

19 42

[opensuse-factory] Java:repositories cleanup
by Tomáš Chvátal 24 Jul '14

24 Jul '14

Hello guys, as I got the lucky task of playing with our Java packages I started bit of a late spring cleanup. From the list [1] I am going to reduce all the repos to following list: Java:packages Java:packages:maven Java:Factory Java:esemeska If you by any chance have package in any of those repositories that are going away, copy the package to your home and resubmit to Java:packages. There were quite few usefull packages I copied out so I might've overlook some :) So please let me know if you find something worth preserving, otherwise wave the remaining repositories good bye :) Cheers Tom [1] https://build.opensuse.org/project/subprojects/Java

1 0

[opensuse-factory] yast2 sw_single failing
by Felix Miata 23 Jul '14

23 Jul '14

> Removing libproxy1-config-kde4 makes software management in YaST work. > It seems that YaST was rewritten in QT5 and crashes when it tries to > access QT4 libraries. > Now to make Chrome WebGL work again with Mesa 10 and Intel GM45... > - [1601:1601:0722/054908:ERROR:context_group.cc(193)] : > ContextGroup::Initialize failed because too few texture units. > - [1601:1601:0722/054908:ERROR:gles2_cmd_decoder.cc(2355)] : > GpuScheduler::InitializeCommon failed because group failed to > initialize. 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) On 20140721 updated just minutes ago, trying to run YaST2 software in KDE4 I get this instead: Run command: /sbin/yast2 sw_single & terminate called after throwing an instance of 'YUIPluginException' what(): Couldn't load plug-in qt YaST got signal 6 at file /usr/share/YaST2/modules/Wizard.rb:836 /sbin/yast2: line 434: 1565 Aborted $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS Changing to rv380 radeon on same installation it's slightly different: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV380 [Radeon X600] Run command: /sbin/yast2 sw_single & terminate called after throwing an instance of 'YUIPluginException' what(): Couldn't load plug-in qt YaST got signal 6 at file /usr/share/YaST2/modules/Wizard.rb:836 /sbin/yast2: line 434: 1450 Aborted $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- 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] Mobile broadband suddenly broken
by Richard Weinberger 22 Jul '14

22 Jul '14

Hi! I'm on 13.1+Tumbeweed and mobile broadband stopped working a few days before. I don't exactly know when as I don't use it every day. This is the output of the NetworkManager log: ---cut--- 2014-07-21T16:16:17.003299+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) starting connection 'A1/Telekom Austria - A1 Breitband' 2014-07-21T16:16:17.004086+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2): device state change: disconnected -> prepare (reason 'none') [30 40 0] 2014-07-21T16:16:17.005044+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled... 2014-07-21T16:16:17.008557+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) started... 2014-07-21T16:16:17.009246+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2): device state change: prepare -> need-auth (reason 'none') [40 60 0] 2014-07-21T16:16:17.009845+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) complete. 2014-07-21T16:16:17.021023+02:00 sandpuppy NetworkManager[963]: get_secret_flags: assertion 'is_secret_prop (setting, secret_name, error)' failed 2014-07-21T16:16:17.106087+02:00 sandpuppy NetworkManager[963]: message repeated 18 times: [ get_secret_flags: assertion 'is_secret_prop (setting, secret_name, error)' failed] 2014-07-21T16:16:17.140734+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled... 2014-07-21T16:16:17.143215+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) started... 2014-07-21T16:16:17.154112+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2): device state change: need-auth -> prepare (reason 'none') [60 40 0] 2014-07-21T16:16:17.154754+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) complete. 2014-07-21T16:16:17.159736+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2) modem state changed, 'registered' --> 'connecting' (reason: user-requested) 2014-07-21T16:16:17.197258+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2) modem state changed, 'connecting' --> 'connected' (reason: user-requested) 2014-07-21T16:16:17.197792+02:00 sandpuppy NetworkManager[963]: <warn> (ttyUSB2): failed to look up interface index 2014-07-21T16:16:17.198256+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 2 of 5 (Device Configure) scheduled... 2014-07-21T16:16:17.198701+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 2 of 5 (Device Configure) starting... 2014-07-21T16:16:17.216351+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2): device state change: prepare -> config (reason 'none') [40 50 0] 2014-07-21T16:16:17.216866+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 2 of 5 (Device Configure) successful. 2014-07-21T16:16:17.217392+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 3 of 5 (IP Configure Start) scheduled. 2014-07-21T16:16:17.218061+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 2 of 5 (Device Configure) complete. 2014-07-21T16:16:17.218620+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 3 of 5 (IP Configure Start) started... 2014-07-21T16:16:17.219016+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2): device state change: config -> ip-config (reason 'none') [50 70 0] 2014-07-21T16:16:17.219581+02:00 sandpuppy NetworkManager[963]: <info> using modem-specified IP timeout: 20 seconds 2014-07-21T16:16:17.220212+02:00 sandpuppy NetworkManager[963]: <info> starting PPP connection 2014-07-21T16:16:17.221205+02:00 sandpuppy NetworkManager[963]: <info> pppd started with pid 3014 2014-07-21T16:16:17.221705+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 4 of 5 (IPv6 Configure Timeout) scheduled... 2014-07-21T16:16:17.222148+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 3 of 5 (IP Configure Start) complete. 2014-07-21T16:16:17.222896+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 4 of 5 (IPv6 Configure Timeout) started... 2014-07-21T16:16:17.223911+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 4 of 5 (IPv6 Configure Timeout) complete. 2014-07-21T16:16:17.224339+02:00 sandpuppy NetworkManager[963]: <warn> pppd pid 3014 exited with error: pppd options error 2014-07-21T16:16:17.224923+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 4 of 5 (IPv4 Configure Timeout) scheduled... 2014-07-21T16:16:17.225522+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 4 of 5 (IPv4 Configure Timeout) started... 2014-07-21T16:16:17.226128+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5] 2014-07-21T16:16:17.227762+02:00 sandpuppy NetworkManager[963]: <warn> Activation (ttyUSB2) failed for connection 'A1/Telekom Austria - A1 Breitband' 2014-07-21T16:16:17.228595+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 4 of 5 (IPv4 Configure Timeout) complete. 2014-07-21T16:16:17.229424+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2): device state change: failed -> disconnected (reason 'none') [120 30 0] 2014-07-21T16:16:17.230159+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2): deactivating device (reason 'none') [0] 2014-07-21T16:16:17.231608+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2) modem state changed, 'connected' --> 'disconnecting' (reason: user-requested) 2014-07-21T16:16:19.248718+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2) modem state changed, 'disconnecting' --> 'registered' (reason: user-requested) 2014-07-21T16:16:36.266449+02:00 sandpuppy NetworkManager[963]: get_secret_flags: assertion 'is_secret_prop (setting, secret_name, error)' failed ---cut--- Any ideas? -- Thanks, //richard -- 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] Factory as a distro factory
by Felix Miata 22 Jul '14

22 Jul '14

As a rolling distro, I can't see Factory as the apropos name it was. It's now just an assembly plant, not a manufacturing plant, roughly equivalent to Fedora's post-branching TS builds. IMO, Tumbleweed, or something entirely different, ought to be the name applied going forward to the rolling release Factory. No longer will Factory be a good way to discover bugs, since ostensibly all but inconsequential or undiscoverable bugs have been squashed before acceptance of newer versions from BS into Factory. What the name "Factory" ought to be now is (a) recommended collection(s) of BS repos designed to do one of the things the old Factory did, enable user-testers to find the problems the builders missed or couldn't have found using the hardware at their disposal. Even without any name changing going forward, there still needs to be something describing a or several recommended BS repo collection(s) for those wishing to remain testers, at least a wiki page with a suitable name nicely describing what it's for, so people so desiring can continue to do everything they had been doing with Factory past (and still can with such as Cauldron, Rawhide or Sid). -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

10 19

[opensuse-factory] submitrequest about etckeeper (was: Do you know about the cause by which the zypper-etckeeper.py does not operate ?)
by 1xx 21 Jul '14

21 Jul '14

2014-06-25 9:13 GMT+09:00 1xx <itsango(a)gmail.com>: > 2014-06-22 8:18 GMT+09:00 1xx <itsango(a)gmail.com>: >> 2014-06-20 11:22 GMT+09:00 1xx <itsango(a)gmail.com>: >>> https://build.opensuse.org/package/show/home:Mitsutoshi:branches:utilities/… >>> >>> I am testing etckeeper 1.12 now, it seems to work normally. >>> >>> Are there those who want to test new etckeeper? >>> It can download from the following. >>> http://software.opensuse.org/download.html?project=home%3AMitsutoshi%3Abran… >> >> >> I submitrequested it. >> https://build.opensuse.org/request/show/238255 It was declined. So I changed comments (etckeeper,changes, etckeeper.spec, and etckeeper-zypp.patch). And I re-submited a request. https://build.opensuse.org/request/show/239404 Please review it and accept or decline it. -- 1xx <ItSANgo(a)gmail.com> <https://twitter.com/ItSANgo> Mitsutoshi NAKANO <bkbin005(a)rinku.zaq.ne.jp> <http://d.hatena.ne.jp/Itisango/> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 22

[opensuse-factory] Factory broken
by Stephan Kulow 21 Jul '14

21 Jul '14

Hi, There are various problems shown on https://openqa.opensuse.org/tests/overview?distri=opensuse&version=FTT The most prominent is the btrfs crash on i586 filed as https://bugzilla.novell.com/show_bug.cgi?id=887046 But there are various others - not affecting the staging prjs for some unclear reason. One reason for this is that kernel on i586 is less stable, but we have no resources to stage also i586. Another bug is seen at - the upgrade path is now broken for a while ;( https://openqa.opensuse.org/tests/11570/modules/upgrade_select/steps/5 So don't wonder why there are no factory updates... Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 9

[opensuse-factory] o:F/icu failure (Re: Reminder for openSUSE:Factory work)
by Jan Engelhardt 21 Jul '14

21 Jul '14

On Monday 2014-07-21 12:26, Stephan Kulow wrote: > >Dear openSUSE contributor, >Project X11:common:Factory > > icu fails for 27 days (time dependent failure): > http://s.kulow.org/bf-icu Hm. openSUSE:Factory/icu still contains 52.1. Has the LibreOffice team addressed their issues with the pending 53.1 (where there is a fix)? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1