January 2013 - openSUSE Factory - openSUSE Mailing Lists

Re: [opensuse-factory] systemd handling of suspend/hibernate keys and lidswitch
by Richard Brown 23 Jan '13

23 Jan '13

On Wed, Jan 23, 2013 at 7:02 AM, Guido Berhoerster wrote: > Part of that responsibility for breakage also lies within > openSUSE, this is configurable and could easily be changed back > to the default setting acpid had. > The only advantage of the change in defaults is that now laptops > without a desktop environment installed will suspend/hibenate if > you press the corresponding keys/use the lidswitch. On the other > hand desktop environments (including GNOME) in openSUSE which > previously handled this and continue to handle this currently > have to be patched because the necessary changes are not upstream > or in a release yet. When it comes to GNOME, Dimstar (with a little help from myself) looked into this at the recent openSUSE Polish Hackathon You can see the patch here, which is now in Factory: https://build.opensuse.org/request/show/149461 Philosophically, I understand where the systemd developers are coming from and like the idea of there being some power management in the absence of a DE But that does mean the DE's need to do their part to either fully 'take over' from, or properly 'hand off' to systemd to avoid problems like this Hope this helps settle any concerns Richard Brown RBrownCCB(a)opensuse.org -- 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] Maintainer model clean up
by Robert Schweikert 23 Jan '13

23 Jan '13

Hi, This is also related to the "Coolo needs help thread". During osc12 we had various discussions related to the topic of getting the distribution out the door and how we can get there within the release schedule that we had agreed to a while back. Part of this discussion are the two sessions I had the opportunity to lead, both are available on youtube opensusetv, if you are interested in this topic please go and watch these sessions, as well as Stephan's session, also on youtube. Unfortunately we did not have video equipment in the BoF session. The basic proposal is, and this received general agreement at osc12, that we will move toward changing the model as proposed in the session. This implies the following: - In the web UI one will no longer see inherited project maintainers on the package page, only the "true" package maintainers. (Inherited "maintainers" will be hidden in an expandable tree) - We will collect information about all packages in all devel projects that feed factory. We will generate a list of packages that have no maintainer, and a list of packages that need help, i.e. a package that has fewer than 5 maintainers. In addition we will list packages that have more than 5 maintainers and try to encourage maintainers from those packages (to get the number to 5) to take on packages that need help. - We want to clean up the devel project maintainer list to a ratio of 10/500 packages with a max of 25. ~ In many cases package maintainers in a given project do not care about all the other packages in the project, yet they are on the project maintainer list. ~ Also many people have their Hermes notifications disabled as they get too many messages about packages they do not care, hopefully with the changes more people will re-enable their Hermes notifications (more on this below) - We would like to see a notification on the package page if the package fails to build in factory - Would like to see package build status information on the factory status page about the status of the package in it's devel project. - Having the monitor page and the status page presented in the current form is confusing, we need to somehow merge the information. - It would be really nice if there were some kind of policy engine that could enforce the "no more than 5 per package" and the "no more than 25 project maintainers" policies. ~ now OBS is not just for openSUSE, thus this cannot be hard coded into the OBS code, thus this is potentially a lot of work. - We would like to have some kind of rating system on the devel projects - We will produce guidelines for package and product maintainers outlining what is expected. ~ These guidelines are not hard rules, but provide help to new people stepping in to define the role they are comfortable with. There appears to be a problem that the complete void of guidelines in this area leads to paralysis and people just do not know what to do if they want to help. We have documents how to package, these guidelines will be a hopefully short list of "what is expected". These are the rough outlines of the "plan". Obviously there is work to be done and the OBS team already has plenty to do. It is up to me to document in more detail the requirements/use case before a potential timeline can be developed. I will also start a wiki page attempting to define the various roles in the devel process and then opening that up for discussion once the basics are in place. Now to a couple of counter points. - Yes we will step on some people's toe, sorry. Meaning if you get removed as project maintainer from a devel project and you really really want to be a project maintainer you are probably not going to be happy. Please do not take it personal and get yourself added back to the project. Preferably you would find one of the project maintainers that remained, by chance and chance alone, and get that person to drop of the list. Chances are you will find someone willing to "make space for you" ~ Sorry, but this process has to be somewhat arbitrary due to the large number on the various devel projects. ~ Please be not offended, there is no vicious intent, just the intent to help the project grow and scale better. - Yes, the "rules" are changing, and if you maintain a package that is also in factory there will now be some expectations ~ In the end we all should have the same goal, create a quality distro in the time frame we promise, thus this should really not be a big deal Before I close this rather long e-mail (sorry) I have a kind of survey question. I would like to have the hermes settings of package maintainers reset "automatically" as we move through the house keeping project such that package maintainers get notification of build failures of their packages. I realize many people have these turned off today, but again, this is probably due to the number of notifications due to the project maintainer mails that most people do not care about. OK, before I write another couple of pages about this subject I'll stop here. Thanks for your attention, please no flaming, bitching and moaning. Great ideas and help are welcome. Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjschwei(a)suse.com rschweik(a)ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 12

[opensuse-factory] Why was kio_sysinfo - My Computer removed for 12.3?
by Roman Bysh 23 Jan '13

23 Jan '13

Hello List mates, Does anyone know why kio_sysinfo was removed for 12.3? 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

5 12

[opensuse-factory] systemd handling of suspend/hibernate keys and lidswitch
by Guido Berhoerster 23 Jan '13

23 Jan '13

The systemd version in Factory now handles power/suspend/ hibernate keys and lidswitch by default which breaks power-managers which are not systemd-aware (see e.g. bnc#789057), that is everything except GNOME3/KDE4 such as xfce4-power-manager, empower, or kpowersave. All DEs handle lid-switches, power buttons etc. fine without it and pure WM users are likely to have mechanisms in place (such as a custom acpid configuration) if they need it, so this change in default behavior doesn't have any benefits. Can we change the systemd default settings back to what they are/were with acpid, that is handle only the power button (if possible, only if no DE is running)? -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

12 34

[opensuse-factory] openvpn
by Hans Witvliet 23 Jan '13

23 Jan '13

Hi all, I know you are all busy with 12.3... But any chance that the repo "./network:/vpn/...." got some modest attention? openvpn-2.3 has been released some time ago (8-jan). Besides bug-fixes, it has full IPv6 support. The most recent i can find is the rc1 in mludvig's home dir. Kind regards, Hans -- 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] 12.3 Beta1 - observations
by Jim Henderson 23 Jan '13

23 Jan '13

I've just installed 12.3 Beta1 in a VirtualBox VM and have run into a few issues that I'm wondering if anyone else has seen. 1. The VirtualBox guest components all seem to be outdated (result from the last milestone was a 640x480 display only, in Beta1 the GUI doesn't start at all). I worked around it by installing the 4.2.6 guest addons after removing the pre-installed packages (which are version 4.2.4). Could we get the 4.2.6 addons in the release? 1.a. Even with the 4.2.6 OSE addons installed, I cannot get 1280x1024 resolution. That may not be a 12.3-specific issue, but I thought I'd mention that I can only select 1280x960 (along with other "standard" resolutions). 2. When I log out and go to log back in, I never get a password prompt (I select the user, and it moves but then bounces back to selecting the user). If I select "Not listed?" and enter my username, I get the error message "[Invalid UTF-8]" (the username is "jhenderson", so I'm not sure what's invalid about that). 3. I installed GNOME3 as the default desktop, then added the other desktops later, but the login screen doesn't seem to have any place to select the DE. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 10

[opensuse-factory] thermal_sys
by Peter Czanik 22 Jan '13

22 Jan '13

Hello, I have a ThinkPad T410 running the latest Factory release since the last couple of days. For the first time ever my laptop was shut down automatically. I found this line in /var/log/messages: 2013-01-22T11:59:36.922822+01:00 linux-4xb2 kernel: [18838.761023] thermal_sys: Critical temperature reached (100 C), shutting down Is this a new feature (after 12.2, which I used until recently), that's why it never happened before? Or it's a bug in thermal management and / or sensors, so I should enter it into bugzilla? 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 7

[opensuse-factory] SR#149565: Revert libdvbpsi to 0.2.2
by Dominique Leuenberger a.k.a. Dimstar 22 Jan '13

22 Jan '13

Hi Coolo, and list I just submitted SR#149565 to Factory, which reverts libdvbpsi from 1.0.0 back to 0.2.2... Rationale: - libdvbpsi 1.0.0 has a bunch of (not very trivial) API changes... - The most prominent consumer of libdvbpsi is the VideoLAN Project (vlc media player) - To my knowledge, this is rather 'the only consumer of the lib' - VLC (incl. git master) does not yet support this new libdvbpsi API - Nothing in the Factory tree uses libdvbpsi (It's there for convenience only) The proposal to revert to 0.2.2 (last release before 1.0.0) is to - Make my life as VLC maintainer easier :) - Make the life of any user trying to build other packages relying on libdvbpsi easier (if any such package even exists). Please consider this exceptional version change. Best regards, Dominique PS: I'm not aware of any specific guideline on how such a revert is to be done correctly... I now did osc sr -r <rev>; but that obviously removes the .changes entries as well.. Is this sufficient? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

Fwd: Re: [opensuse-factory] Reminder: we're in feature freeze
by Sascha Peilicke 22 Jan '13

22 Jan '13

Sorry, this was intended for the list -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) --- Weitergeleitete Mail --- Von: Sascha Peilicke <saschpe(a)suse.de> Datum: 22. Januar 2013 10:24:35 Betreff: Re: [opensuse-factory] Reminder: we're in feature freeze An: Ismail Doenmez <idoenmez(a)suse.de> Am 21. Januar 2013 20:50:28 schrieb Ismail Doenmez <idoenmez(a)suse.de>: > Quoting Cristian Rodríguez <crrodriguez(a)opensuse.org>: > > > El 21/01/13 12:58, Stephan Kulow escribió: > >> 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. > > > > OK, then why isnt the product branched so factory can move along > > regardless of the release status ? > > Because we are supposed to do bugfixes for the release, branching it > off early will result in everyone ignoring and submitting shitloads of > new stuff to Factory. I get the impression that being a openSUSE release manager implies converging on a rather confronting language. Instead you should communicate clear messages. The last one I got was "submit, we gonna decide". The message I get now is "please don't submit for the time being". Which is good. I suspect coolo already disabled factory-auto submissions and he'll inform us once he re-enables that. In the meantime, I agree that it would help that the "forward to factory" checkbox should be disabled by default for now. > > -- > SUSE LINUX Products GmbH > Maxfeldstr. 5, 90409 Nürnberg, Germany > GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) > -- > To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org > -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) -- 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] About the reminder mails just sent
by Stephan Kulow 22 Jan '13

22 Jan '13

Hi, Just in case you may wonder: the reminder mails also include a reminder on version updates. This *does* not mean, I want them now. But I won't change the format now - just ignore the section not fitting the current release phase. Greetings, Stephan -- 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] SR 149536
by Robert Schweikert 22 Jan '13

22 Jan '13

Hi, SR 149536 contains the fix for image building and is expected to address the issues with "addon-lang" build. The fix for this issue is the only change from the current version in factory, thus the risk is low. Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjschwei(a)suse.com rschweik(a)ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

Fwd: Re: [opensuse-factory] Reminder: we're in feature freeze
by Sascha Peilicke 22 Jan '13

22 Jan '13

-- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) --- Weitergeleitete Mail --- Von: Sascha Peilicke <saschpe(a)suse.de> Datum: 22. Januar 2013 10:30:07 Betreff: Re: [opensuse-factory] Reminder: we're in feature freeze An: Stephan Kulow <coolo(a)suse.de> Am 21. Januar 2013 22:15:58 schrieb Stephan Kulow <coolo(a)suse.de>: > Am 21.01.2013 20:39, schrieb Robert Schweikert: > > I would argue that the devel project maintainers should be protected > > from themselves and release managers should be protected from auto > > submits after feature freeze. This implies that after feature freeze > > anything that goes through "auto submit" goes to a queue or that "auto > > submit" is disabled between feature freeze and branch. > > > > All of this should be reasonably easy to implement and will be more > > effective than expecting every devel project maintainer to remember at > > every hour of every day that we are now in feature freeze mode. > > > You're serious? I'm having a hard time replying to this - it sounds like > a bad joke. You make it sounds as if it depends on the moon phase if > we're in feature freeze or not. > > Greetings, Stephan > > -- > To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org > Please reply without ">" in front, makes it easier to follow the discussion. And I do think Robert has a point there but I'm not going to argue with anyone. My takeaway is that I'll try to not submit to Factory anymore until I'm told to do otherwise. -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) -- 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] replace LXDE with E17 on medium
by Tomas Cech 21 Jan '13

21 Jan '13

Hi, I'd like to add E17 on installation medium which is pretty hard task. My estimation is that ~ 35 MB of space is needed for basic RPMs. I'd like to know what is your opinion, if E17 could replace LXDE on installation medium? Is this still even developed? Thanks. Tomas Cech Sleep_Walker

4 3

[opensuse-factory] VNC install not working
by Chuck Payne 21 Jan '13

21 Jan '13

Guys, Have VNC been remove or is broken on the 12.3 Beta. I have a remote site that I am doing install on. I am doing the following at boot prompt on the the grub menu has I have done in the past vnc=1 vncpassword=installme I get prompt for the network setting, I do set that up, and I can ping the server I am going to install on. Once it starts, I can't connect with vnc client, I have looked at the ps and I don't see any vnc agent. I have even did an nmap to see if the client is up and running, nothing. Please let me know if you need more informations. -- Terror PUP a.k.a Chuck "PUP" Payne (678) 636-9678 ----------------------------------------- Discover it! Enjoy it! Share it! openSUSE Linux. ----------------------------------------- openSUSE -- en.opensuse.org/User:Terrorpup openSUSE Ambassador/openSUSE Member Community Manager -- Southeast Linux Foundation (SELF) skype,twiiter,identica,friendfeed -- terrorpup freenode(irc) --terrorpup/lupinstein Register Linux Userid: 155363 Have you tried SUSE Studio? Need to create a Live CD, an app you want to package and distribute , or create your own linux distro. Give SUSE Studio a try. www.susestudio.com. See you at Southeast Linux Fest, June 7-9, 2013 in Charlotte, NC. www.southeastlinuxfest.org -- 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] Tomahawk 0.6.0 for Factory
by Dominik Schmidt 21 Jan '13

21 Jan '13

Hey list, hey Stephan, I would really like to see an exception from the Factory feature freeze for Tomahawk 0.6.0. It hardly introduces new features but does *A* *LOT* of polishing and fixing up rough edges compared to 0.5.5. We tested it very well before the release and haven't had any reports for regressions or new crashes since the beta1 a few weeks ago. I'm convinced this has much higher quality than the 0.5.5 release and every openSUSE should benefit from it. Best regards, Dominik -- 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] PulseAudio 3.0
by Ondrej Holecek 21 Jan '13

21 Jan '13

Hi, I noticed PA3 did not make it into factory, so it wont be in oS 12.3, is that correct? If so was there a reason to not include it? I noticed that PA in devel project is still being build against factory/snapshot with wrong Bluez thus failing. But against factory/standard is builds ok. I am using PA3 for some time now and was looking forward to not using home project for that in oS 12.3 :) Ondrej

2 2

[opensuse-factory] factory incomplete?
by Peter Czanik 21 Jan '13

21 Jan '13

Hello, I just switched my laptop to factory. The latest update seems to be incomplete from the KDE point of view. Zypper dup says: Problem: nothing provides nepomuk-core >= 4.9.98 needed by kdebase4-runtime-4.9.98-1.1.i586 Solution 1: keep obsolete kdebase4-runtime-4.9.97-1.1.i586 Solution 2: break kdebase4-runtime-4.9.98-1.1.i586 by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c): And looking at the repository I see: czanik@roxen:/pub/opensuse/factory/repo/oss/suse/i586$ ls *4.9.98* | wc -l 94 czanik@roxen:/pub/opensuse/factory/repo/oss/suse/i586$ ls *4.9.97* | wc -l 186 So, part of KDE is still the old version, part of it is later. I just checked, http://download.opensuse.org/factory/repo/oss/suse/i586/ also seems to be in a similar state, so it's not just my local mirror... 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 2

[opensuse-factory] Who decides what projects are on the yast2 community project list?
by Ralf Lang 20 Jan '13

20 Jan '13

When yast2 add repository dialog is opened, it offers a list of community projects, including packman and some obs projects. How is this list compiled, what are the criteria? If it lists server:php, is this just the top repository or including server:php:extensions and server:php:applications? I have googled a bit but did not find the answer. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

Re: [opensuse-factory] MariaDB as a default MySQL
by darx＠sent.com 20 Jan '13

20 Jan '13

On Sat, Jan 19, 2013, at 04:12 PM, Michal Hrusecky wrote: > Well, these are using MySQL API, which is the same. There are reasons that many projects still fully support only one, and not the other. Despite the presumed "same" API. That situation will likely improve/change over time. > > -- a separate devel pkg , libs & includes, be made available. > > I was thinking about that, but it would made it more confusing, > transitions harder and there would be people in obs building against one > and people building against the other one and it will be more messy in > general... I couldn't disagree more. With the "more confusing" & "more messy", in particular. The potential already exists for people building across different libs/apis for a given package. Lua* is one example that causes headaches. That's a result of developer/packager sloppiness, not of having cleanly delineated and complete packaging. If the distro 'standard' should be "always build against _this_, not that, package's libraries, that's a documentation & standards issue. Hobbled or incomplete packaging of mainstream apps is, imo, a bad idea. > Yes, I know, but we are testing them living together for many openSUSE > versions so I believe that most of the issues were polished over the > years already. And during all those years, the default has been MySQL. Proposing the change of *default* at _this_ stage, _this_ late in the 12.3 release cycle, without a more thorough discussion is what I find problematic. MySQL et al are hardly leaf packages. I suspect this is likely happening anyway. In the end, it may be best for the general user/desktop segment. As that's not my own, personal interest, I'll likely add MySQL to my 'DIY' stack and eliminate the issue locally. At this point, I don't find real advantage or benefit in this change, see it as simply change for change's sake, and am concerned that it's a rushed process. Thanks. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] OpenStack stable fixes vs version freeze
by Vincent Untz 20 Jan '13

20 Jan '13

Hi all, Thanks to the fast reviews of the legal team and the factory reviewers, OpenStack 2012.2 is in Factory now. That's great news! Now to the next step :-) Some background: we package OpenStack directly from git, and we update to latest git every now and then. There's a nice diagram if you want to get a clear view of this: https://en.opensuse.org/OpenStack_and_Crowbar_development_process The reason we can do this is that there's a pretty strong focus on stability upstream, and changes can only be committed after reviews + automatic testing. So we're quite confident in the quality of what is in upstream git. On stable branches (like 2012.2, aka Folsom, that we have in Factory), committed changes are really only a few bug fixes (and no new features). For instance, between December 17 and today, here's the amount of changes in upstream git for core components of OpenStack: cinder: 1 glance: 4 horizon: 9 keystone: 7 nova: 6 quantum: 21 swift: 0 (I used 'git log --pretty=oneline --since="2012-12-17"' for this, not sure if it's the totally correct way; but it gives an idea of the amount of changes) So that's the amount of bug fixes we get in one month for the stable branch (and as it becomes older, there'll be fewer and fewer fixes). Now, to my question: to what extent would it be accepted that we push these upstream fixes to Factory after the version freeze? I was thinking that it could be okay to keep pushing them until the freeze for RC1. Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- 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] macbook/retina: 12.3beta1 install issues
by Petr Vaněk 19 Jan '13

19 Jan '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi all, was somebody able to install 12.3b1 on macbook pro (retina mid 2012)? I have some install issues: - - wifi does not work. Modules seems loaded but there is no net connection at all. firmware: Broadcom BCM43xx 1.0 (5.106.98.100.15) workaround: use ethernet adapter into thunderbolt port - - touchpad is not found and configured. workaround: standard USB mouse used. - - install process randomly freezes in the rpm installation (1st time grub2, 2nd time nouveau) workaround: none I found. Giving up for now. just asking before I'll fill bugreports... thanks, petr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJQ+pSuAAoJEC8yRjM4uE2tSuEH/2XdgoF+Q02id3AteP//w20A nTtrX4J+loOIaM+0pbtkJfggt9pB78x0vcw5lWCOGZQ5fkoFoMq6yKRqmIa4r+hq GJ+ADv7pNWglAk9mKDJdaxgb2YRC/9vZMe5Wbo37xOg71nS0lk8D3sqVYJy1JIju z6TG6JbaR8GkqaVMzYYj/8FkwlBNs0K2X5wGLnNQaGshMx7M3E5DsDWc4JtlP9Xt oKDhSALhafQpYx2dWstnQ5xVphuYmwknx3HIb/z7q0oBNYt95clXmwHwoxw9nWQ/ pDB/w6sLWJ5A32FCQv77MDA1J4EUYn9uppaCCM14aRzTxi6s2RbBjPDYxJ9Yp+k= =cG2k -----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

2 1

[opensuse-factory] Missing core.img after partially succeeded upgrade
by Jogchum Reitsma 18 Jan '13

18 Jan '13

Hi, I upgraded my x86_64 system from 12.2 to factory trough Yast. Upgrade went well up till installing gimp, then came suddenly to a halt, leaving the system dead. On reset the disk I use for this experiments was not found by the BIOS (which took a long time apparently trying to find it). After powering up the pc anew the disk was visible again, grub2 was started, gave 12.2! as default choice with no 12.3 or factory as other choices, then complained about missing (hd0,1)/grub2/core.img. No further boot of course. After booting up from another disk in the system I find indeed that the is no core.img in place, but instead it is in the i386-pc subdir. From the dates in the listing of /grub2 on that device I get the impression that grub2 only was installed partially: drwxr-xr-x 6 root root 4096 16 jan 21:57 ./ drwxr-xr-x 5 root root 4096 16 jan 22:21 ../ -rw------- 1 root root 358 10 mei 2012 device.map drwxr-xr-x 2 root root 4096 9 jul 2012 fonts/ -rw------- 1 root root 18209 16 jan 21:57 grub.cfg -rw-r--r-- 1 root root 1024 25 mei 2012 grubenv drwxr-xr-x 2 root root 12288 24 aug 15:39 i386-pc/ drwxr-xr-x 2 root root 4096 24 jul 19:19 locale/ drwxr-xr-x 3 root root 4096 16 jan 21:52 themes/ The date of the update was jan 16. What could have gone wrong? regards, Jogchum -- 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] MD5 checksum and sha1 checksum are wrong for openSUSE-KDE-LiveCD-Build0348-x86_64.iso
by Roman Bysh 17 Jan '13

17 Jan '13

Hello List mates, The following sums for openSUSE-KDE-LiveCD-Build0348-x86_64.iso are correct: SHA-256 Hash: 049433c6512f549a09a5ca9c7f8c12f87d0437248cc8a7adf62fba96fe12c37d SHA-1 Hash: 6b8e3c805aadb8835672f761e5db36122179d0fb MD5 Hash: edc27ffcb34cbb33adf25afc699df098 However, when I click on the MD5 checksum link, I see a different number. 5a947a36bae4154f11b2b9aa38e4d088 The sha1 checksum link provides this number which is also incorrect. 5fde24f109aea45aea7559c357fe74cf41f24c63 Can some one check the checksum links please? 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

1 0

[opensuse-factory] [13.1] Change for Alacarte and exo-desktop-item-edit
by Dominique Leuenberger a.k.a. Dimstar 17 Jan '13

17 Jan '13

Hi all (specifically Guido). This is a heads up for after feature unfreeze of Factory... by when most of GNOME 3.7.x will come you way :) Alacarte had some substantial changes and no longer interfaces with *-desktop-item-edit binaries, but has internal code for this now (but it allows to edit different structures than applications.menu). So, this mail serves as a heads up that the patch on alacarte has been dropped for 13.1 / GNOME 3.8. 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

2 2

[opensuse-factory] what's new in openSUSE?
by Jos Poortvliet 17 Jan '13

17 Jan '13

Heya all, If you've uploaded major new versions of the software you maintain to Factory please add a note to https://en.opensuse.org/openSUSE:Major_features so we can reference these changes when we write the release notes. You don't have to write a book about each change, but at least a version number (old and new) and a link to release notes would be appreciated. We can't talk about features we don't know about and we don't know about features nobody tells us about so if you'd like our users to know what you did, please add it to this list! Suggestions on how to make it easier to track what improvements end up in openSUSE are very much welcome - with the last release, some people had to sit down and spend many, many hours carefully combing through all of factory to find out what is new and that really doesn't work. Greetings, Jos

2 2

Re: [opensuse-factory] branding packages republish many times a day
by "Stefan Brüns" 17 Jan '13

17 Jan '13

Am 16.01.13, schrieb Stephan Kulow <coolo(a)suse.de>: > Am 15.01.2013 17:02, schrieb Cristian Rodríguez: > > Hi: > > > > Does anyone know if the constant republishing of branding packages is > > the expected behaviour ? new builds of: > > > > the following packages are going to be upgraded: > > branding-openSUSE gfxboot-branding-openSUSE grub2-branding-openSUSE > > kdebase4-openSUSE kdebase4-runtime-branding-openSUSE > > kdebase4-workspace-branding-openSUSE kdelibs4-branding-openSUSE > > kdm-branding-openSUSE ksplash-qml-branding-openSUSE > > ksplashx-branding-openSUSE plymouth-branding-openSUSE > > susegreeter-branding-openSUSE wallpaper-branding-openSUSE > > yast2-qt-branding-openSUSE > > > > appear at least 2 o 3 times a day and I dont believe they really change > > that many times.. > > They are rebuild whenever their build dependencies change - which is > often. And if build-compare does not catch it, they are synced out. > > Greetings, Stephan Hi Christian, if you want to get more information which is causing this: in zypper, when asked to "Continue? [y/n/?] (y):", press "d" (for details), which will give you a list of packages to be updated, including repository information and version numbers of the old and new packages (Hint - this would be useful for anyone trying to debug this). Now go to the OBS, select the appropriate project (KDE:Release:49, KDE:Distro:Factory?) and package, fetch the build log and, starting from the tail, look for compare. Every mismatch (which causes the new package to by synced out) will be shown there. Regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen phone: +49 241 53809034 mobile: +49 151 50412019 -- 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] How to test updated package version during installation?
by Andrey Borzenkov 17 Jan '13

17 Jan '13

How to test fix in a package if bug happens during initial installation? I.e. - how to make installer use updated package version? I do not see how to do it with DUD. I can run scripts before/after installation, but in this case it is too late because bug happens during package installation itself (when post is run). Solution would be to use multiple repositories but I do not see how I can do it. Also I am not sure installer would use local package repository with unknown signature. Any idea? TIA P.S. in this case I speak about https://bugzilla.novell.com/show_bug.cgi?id=798604. grub2 post triggers bug in os-prober so I need to make updated os-prober available before grub2 is installed. And I cannot test fix after installation because it happens only during install. -andrey -- 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] New packages, mozc, zinnia, zinna-tomoe, for Factory
by Fuminobu TAKEYAMA 16 Jan '13

16 Jan '13

Hi all, I would like to submit a new package named mozc and its dependent packages, zinnia, zinnia-tomoe. Mozc is a Japanese input method engine developed by Google. It is becoming a de facto standard in Linux community because it provides more precise conversion and it seems that the previous standard engine, Anthy, is not maintained recently. Zinnia and zinnia-tomoe provide hand-writing recognition for mozc. # Input method engine is essential especially for CJK users. # Without it, we cannot input letters used in those countries. The package of Mozc have been incubated for more than a year in the M17N project. Now many people uses this package. However, it is not desirable to ask continuously all Japanese users to install it from M17N, which is a devel project for other packages. There is a problem in development process by the upstream. The upstream, Google, currently would not accept any patches written in a programming language since Mozc is a part of their proprietary product. Our package, thereby, contains a big patch to support Fcitx. This upstream's policy might cause difficulty of maintenance. Through discussion in the opensuse-ja list, we think the benefit from shipping it with openSUSE is much bigger than the risk of maintainability. I am sorry for a late proposal. I hope Mozc will be shipped with openSUSE 12.3. Best regards, -- Fuminobu TAKEYAMA -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 8

[opensuse-factory] branding packages republish many times a day
by Cristian Rodríguez 16 Jan '13

16 Jan '13

Hi: Does anyone know if the constant republishing of branding packages is the expected behaviour ? new builds of: the following packages are going to be upgraded: branding-openSUSE gfxboot-branding-openSUSE grub2-branding-openSUSE kdebase4-openSUSE kdebase4-runtime-branding-openSUSE kdebase4-workspace-branding-openSUSE kdelibs4-branding-openSUSE kdm-branding-openSUSE ksplash-qml-branding-openSUSE ksplashx-branding-openSUSE plymouth-branding-openSUSE susegreeter-branding-openSUSE wallpaper-branding-openSUSE yast2-qt-branding-openSUSE appear at least 2 o 3 times a day and I dont believe they really change that many times.. -- 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] Removing whaawmp media player
by Guido Berhoerster 16 Jan '13

16 Jan '13

whaawmp media player in X11:xfce is an rather obscure gstreamer-based media player written in python without any unique features. There's an abundance of gstreamer-based media players and we already have parole and pragha in X11:xfce. So if someone cares about it please let me know, otherwise I'd to get rid of it before 12.3. -- Guido Berhoerster -- 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] RFC: new package: shelldap
by Adam Spiers 15 Jan '13

15 Jan '13

Hi all, I would like to propose submitting shelldap from network:utils to Factory. It has two dependencies which are not already in Factory, so they would need adding too: perl-Term-Shell and perl-Digest-MD5. --------- 8< --------- 8< --------- 8< --------- 8< --------- 8< --------- Name: shelldap License: BSD-3-Clause Summary: Shell-like interface to LDAP servers Url: http://projects.martini.nu/shelldap Group: Productivity/Networking/LDAP/Clients Devel-Package: network:ldap Description: Shelldap is a program for interacting with an LDAP server via a shell-like interface. This is not meant to be an exhaustive LDAP editing and browsing interface, but rather an intuitive shell for performing basic LDAP tasks quickly and with minimal effort. --------- 8< --------- 8< --------- 8< --------- 8< --------- 8< --------- This is my first time submitting to Factory, so I thought I'd ask for feedback before sending a submitrequest. Thanks, Adam -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 7

[opensuse-factory] Fixing bug in Factory package
by Togan Muftuoglu 15 Jan '13

15 Jan '13

Hi, For shorewall package there was a recent bug report <https://bugzilla.novell.com/show_bug.cgi?id=798525> as the shorewall install script messes up the exec path of the systemd service files. I have fixed the problem in the devel project security:netfilter, however I have not submitted the package to factory as this devel project's shorewall version is ahead of factory. In my opinion shorewall is a leaf package as no other package depends on it and the devel project version fixes some other bugs related to the xtable-addon modules. a) Therefore if I can submit the devel project to factory that would be great. b) Else if I understand correctly I need to branch the package from factory directly to provide the fix as the 12.3 project is not there yet osc bco --nodevelproject openSUSE:Factory shorewall I would prefer to be able to choose option A, but rather then getting a decline I guess it is better to get opinion first Thanks Togan -- 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] The validator fun continues!
by Jan Engelhardt 15 Jan '13

15 Jan '13

The /suse/coolo path is new. Le message de la soirée, c'est... ---------- Forwarded message ---------- Subject: [obs submit-request 147981] openSUSE:Factory/arptables: declined by factory-auto State of submit-request #147981 was changed by factory-auto: review -> declined Comment: Output of check script: Error creating temp directory from template /tmp/obs-XXXXXXX: Could not create directory /tmp/obs-zshsjm8: No space left on device at /suse/coolo/checker/source-checker.pl line 147 https://build.opensuse.org/request/diff/147981 Source project: security:netfilter package: arptables revision: 12 Target: project: openSUSE:Factory package: arptables -- Hermes messaging (http://hermes.opensuse.org) openSUSE Build Service (https://build.opensuse.org/) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 4

[opensuse-factory] Tumbleweed: gdk-pixbuf-query-loaders: undefined symbol: g_type_ensure
by Hendrik Woltersdorf 15 Jan '13

15 Jan '13

Hi, after today's "zyper dup" I got this error: -> /usr/bin/gdk-pixbuf-query-loaders /usr/bin/gdk-pixbuf-query-loaders: symbol lookup error: /usr/bin/gdk-pixbuf-query-loaders: undefined symbol: g_type_ensure installed version: -> rpm -qa | grep gdk-pixbuf-query-loaders gdk-pixbuf-query-loaders-2.26.5-2.2.i586 available versions: -> zypper wp gdk-pixbuf-query-loaders ... S | Name | Typ | Version | Arch | Repository --+--------------------------+-------+--------------+------+--------------------- i | gdk-pixbuf-query-loaders | Paket | 2.26.5-2.2 | i586 | Tumbleweed v | gdk-pixbuf-query-loaders | Paket | 2.26.1-2.1.4 | i586 | openSUSE Current OSS Is this an incomplete update or is there something broken? Hendrik -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 9

[opensuse-factory] openSUSE 12.3 Hackaton this Friday in Nue
by Jos Poortvliet 14 Jan '13

14 Jan '13

Heya all, This Friday (Jan 18) a bunch of us will gather in meeting rooms Rome and Paris in Nuremberg for a hacking frenzy on openSUSE 12.3. We'd like to invite anyone interested to join the fun and help make this release more Awesome! Of course, we'll not only provide good company but also food and snacks and good stuff to hack on. We'll keep hacking in the All Hands area on Saturday and we plan to have some mini presentations about tech around openSUSE. Again, food, snacks and fun provided! We expect a little over 20 participants - including people from the SUSE offices and some who'll need a visitor pass ;-) Anyone is welcome to join at any time. Of course, it's not practical for all of you to come to Nuremberg but we've got something if you want to join remotely: a Google Hangout. We'll have a hangout open between 10 and 12 in the morning and 14:00 and 18:00 in the afternoon on both Friday and Saturday (all CET). If you have a G+ account and let us know we can invite you for the sessions and you can of course also join us on irc: #opensuse-factory on Freenode as usual. Virtual food and hugs will be provided. Don't worry and hack on! the openSUSE Team

1 0

[opensuse-factory] Request to promote/include "chrony" as official package; use case: Roaming Laptops
by darx＠sent.com 14 Jan '13

14 Jan '13

I have/use a Roaming Laptop (Opensuse 12.2/KDE) that connects to a variety of networks, with varying assigned IPs, frequently offline. It's a very common use-case. For network managemet, I use NetworkManager. I need to manage clock-sync, conditionally using different servers depending on LAN/IP state. E.g., (1) @ local only / offline, use NO server, local clock only (2) @ LAN ip = specific IP (e.g., @ my office LAN, 10.11.12.13), use ntp server = 10.11.12.100 (3) @ a roaming-assigned, random IP, use a set of external/public stratum servers. Opensuse 12.2/Factory 'officially' package/release ntpd. I currently launch ntpd with a systemd unit file. Conditional ntp config could be implemented by building logic into (1) systemd unit (2) NetworkManager up/down/change scripts Discussing upstream @ both 'systemd' and 'ntp', neither is recommended. >From both, for such roaming use cases, the use of "chrony" (http://chrony.tuxfamily.org/FAQ.html#question_2.1) is recommended. Particularly as ntpd sync/slew is not reliable if the host machine is often disconnected. Checking opensuse* for chrony packaging, I find we do NOT package it for 12.2 at all, and for -factory there's no official release, only in network:time. For such a frequent/common use case, I'm requesting that chrony be considered for promotion/inclusion as an official product, and enabled for both factory and current stable release. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

12 21

[opensuse-factory] firstboot autorefresh fails
by Felix Miata 13 Jan '13

13 Jan '13

Am I the only one this happens to? I don't recall ever seeing the topic come up here or on Bugzilla. Most of my installs are fixed IP HTTP from downloads.opensuse.org started via Grub. Virtually always when YaST2 wants to refresh repos, it stops to tell me they are inaccessible, at least from factory and factory-snapshot, from which I click skip to let it finish setup. I do rather few fresh installs from GM releases, and can't recall whether it happens there too. -- "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] Tumbleweed: tomahawk cannot fined libquazip.so.1
by Patrick Shanahan 12 Jan '13

12 Jan '13

Tumbleweed tomahawk-0.5.5-3.3.x86_64 Tomahawk fails to load: tomahawk: error while loading shared libraries: libquazip.so.1: cannot open shared object file: No such file or directory libquazip.so.1 is at /usr/lib64/freemedforms-common/libquazip.so.1 -- (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

2 5

Re: [opensuse-factory] Cursed intel graphics card, freezes desktop at random. Tried 3 different kernels
by Roger Luedecke 12 Jan '13

12 Jan '13

On Thu, 2012-12-27 at 17:11 -0500, Felix Miata wrote: > Respond back to list if you want. > > On 2012-12-27 13:56 (GMT-0800) Roger Luedecke composed: > > > On Thu, 2012-12-27 at 15:49 -0500, Felix Miata wrote: > > >> On 2012-12-27 11:54 (GMT-0800) Roger Luedecke composed: > > >> > On Thu, 2012-12-27 at 14:24 -0500, Felix Miata wrote: > > >> >> Does it help to put http://fm.no-ip.com/Tmp/Linux/Xorg/70-composite.conf in > >> >> /etc/X11/xorg.conf.d/ ? > > >> > Going to apply this now, and will reboot and pray. > > >> Rebooting is for new kernels and for Windows. Restarting GDM is all you need > >> to implement that config file. > > > SO that is GDM specific then. > > _What_ is GDM specific? xorg.conf.d/ content is global X, regardless of DE. > What you did previously was probably as most troubleshooters do, to disable > bling only in the user environment via a personal setting, leaving it running > at the GDM level. With composite disabled globally there could be an > important functional difference from only disabling it personally. > > > Either way, so far so stable. But, this > > newer kernel plays a little nicer than the 12.2 stock kernel. Yeah, I set it to force fallback mode. Still froze though. -- 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] Pushing OpenStack Folsom to Factory
by Vincent Untz 12 Jan '13

12 Jan '13

Hi, In order to get the last stable version of OpenStack (Folsom) in 12.3, we'd like to push it to Factory now-ish. Keeping the old version of OpenStack in 12.3 makes nearly no sense -- nobody will want to use it. This has some impact: - I'll file changedevel requests for several packages so that they are developed in Cloud:OpenStack:Factory instead of Cloud:OpenStack:Essex (that last project being versioned, we can't keep using it as a devel project) - there will be a few new packages: - openstack-macros: some macros to build OpenStack packages - openstack-cinder, openstack-quantum, python-cinderclient, python-heatclient: new components of OpenStack - for Factory reviewers: because we develop OpenStack packages in versioned projects, the history of the packages is not fully linear. This means that some of the changes that we did for Essex packages (old stable version) are not in Folsom packages. This is because we worked on both versions in parallel. Of course, the past history is common. I'll do the changedevel requests now. Hopefully, people are fine with the other points, and I'll submit the updated packages afterwards. Cheers, Vincent -- Les gens heureux ne sont pas pressés. -- 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] minor fault in pm-utils intel-audio-powersave
by dieter 11 Jan '13

11 Jan '13

Hi, I have opened a minor bug for pm-utils: https://bugzilla.novell.com/show_bug.cgi?id=797966 it is only a cosmetic problem which exists in current factory (and also 12.2), but the correction is also a minimal change: /usr/lib/pm-utils/power.d/intel-audio-powersave 25c25 < printf "Setting power savings for %s to %d..." "${dev##*/}" "$1" --- > printf "Setting power savings for $s to %d..." "{$dev##*/}" "$1" Kind regards, Dieter -- 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] sr#147759 for sawfish
by Togan Muftuoglu 11 Jan '13

11 Jan '13

hi, the. request #147759 for sawfish was declined per the following reason http://lists.opensuse.org/opensuse-factory/2013-01/msg00083.html in this case i would request a reconsideration as the sr# provides a fix for firefox 17 usage with sawfish window manager and this is the main reason for the version upgrade. of course i understand the logic Coolo provided and but this is not a version upgrade for the sake of a bigger number would it be possible to reconsider the decision thanks togan -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- 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] Tumbleweed: libraw2 breaks shotwell, compicc, kolor-manager
by Patrick Shanahan 10 Jan '13

10 Jan '13

libraw2 update provides libraw_r.so.5, but shotwell, compicc and kolor-manager require libraw_r.so.2. There may be others but these are the only ones I see. -- (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 2

Re: [opensuse-factory] Re: [opensuse-packaging] Can libreoffice be updated to version 3.6.4 in factory
by Malcolm Moore 10 Jan '13

10 Jan '13

The version I tested also has the bug where charts in Writer disappear when you save the document ( bug 791201 ) Mal _____ From: Graham P Davis [mailto:hacker@scarlet-jade.com] To: opensuse-factory(a)opensuse.org Sent: Thu, 10 Jan 2013 11:47:56 +0000 Subject: Re: [opensuse-factory] Re: [opensuse-packaging] Can libreoffice be updated to version 3.6.4 in factory On Thu, 10 Jan 2013 10:42:13 +0100 Petr Mladek <pmladek(a)suse.cz> wrote: > doiggl(a)velocitynet.com.au píše v So 05. 01. 2013 v 19:19 +1100: > > Hello > > Can libreoffice be updated to version 3.6.4 in factory[1] > > source at [2] > > I am sorry but I do not plan it right now. I concentrate on LO-4.0 > packaging in the LibreOffice:Unstable project which takes a lot of > time. > > The good news is that the package in factory includes most fixes from > the upstream 3.6.4 release. We merged them when preparing the stable > 3.6 release for SUSE. > Unfortunately, the Calc problem with vanishing graphs (https://bugzilla.novell.com/show_bug.cgi?id=794698) is still present in the latest factory version that I've tested (3.6.3.2.4-21.4). This is important for 12.3 as LO 3.5 isn't available - apart from LO site itself of course. -- Graham Davis, Bracknell, Berks. openSUSE 12.2 (64-bit); KDE 4.9.97; AMD Phenom II X2 550 Processor; Video: nVidia GeForce 210 (using nouveau driver); Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org -- 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] Can libreoffice be updated to version 3.6.4 in factory
by doiggl＠velocitynet.com.au 10 Jan '13

10 Jan '13

Hello Can libreoffice be updated to version 3.6.4 in factory[1] source at [2] Thanks Glenn [1] https://build.opensuse.org/package/show?package=libreoffice&project=LibreOf… https://build.opensuse.org/package/show?package=libreoffice-branding-upstre… [2] http://www.libreoffice.org/index.php/download/?type=src&version=3.6.4 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 3

[opensuse-factory] Why did we switch to jpeg-turbo as our libjpeg implementation
by Ismail Doenmez 10 Jan '13

10 Jan '13

Hi, I am sorry it look such a long time to write this email. During openSUSE 12.2 development we switched to jpeg-turbo as our libjpeg implementation. This has several reasons: - jpeg-turbo has SSE optimizations for baseline JPEG. - Its used by Google Chrome so it has many bugfixes (and security fixes). - And upstream libjpeg is getting more irrelevant everyday [1][2] Sadly I failed to communicate this properly. If your package fails due to this change I am willing to take a look and fix it. [1] http://hardwarebug.org/2010/02/01/ijg-swings-again-and-misses/ [2] http://sourceforge.net/mailarchive/forum.php?thread_name=50E29F02.9060804%4… Thanks! -- Ismail Dönmez - openSUSE Team SUSE LINUX Products GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- 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] subscribe
by Markus Fischer 10 Jan '13

10 Jan '13

-- 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 syslog after clean factory installation
by Andrey Borzenkov 09 Jan '13

09 Jan '13

In new install (minimal text only) I got no syslog (and empty /var/log/messages). This is not that bad as we have new and shiny systemd journal. Unfortunately, it is not configured to store entries persistent either which means only messages since current boot are visible. It makes debugging fun ... Is it intentional? -andrey -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

11 23

[opensuse-factory] restart req'd to replace obsoleted systemd processes?
by Patrick Shanahan 09 Jan '13

09 Jan '13

When a newer ver of systemd is installed, is the only way to restart the obsolete process a reboot? I see systemd listed as pid 1. -- (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 4

[opensuse-factory] Tumbleweed update broke vgaswitcheroo
by Trent Hawkins 09 Jan '13

09 Jan '13

Hi there, Just zypper dupped to Linux Kernel: 3.7.1-17-desktop Tried my usual trick of running vgaswitcheroo to turn off my second graphics card (hybrid graphics i915 + AMD Radeon HD 6400M), but it didn't work. This is the usual command: # echo OFF > /sys/kernel/debug/vgaswitcheroo/switch System Monitor plasma widget gives me a temperature reading that would normally indicate the AMD card has been switched off (-127.9DegC), but the fan is still going hard and my power usage is half what it should be. Has anyone had a similar experience? Running # grep -i switcheroo /boot/config-* Gives me: CONFIG_VGA_SWITCHEROO=y So the kernel has been properly compiled with this option. Bit baffled. Any advice welcome. Regards, Trent -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1