June 2012 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Pop-up error message
by Thomas Taylor 29 Jun '12

29 Jun '12

Ever since upgrading to OS 12.2-ß2 (build 0452 DVD 64 bit) I've been getting pop-up messages about curl not being able to connect with non-oss factory repo. These pop-ups occur at random intervals and don't seem connected with anything I have open on any of my desktops. Message logs and screenshot at pastebin as: openSuSE_Pop-up_Error I have un-installed tracker, disabled Nepomuk, and stopped the Nepomuk service daemon but the pop-up still occurs. What do I need to change or look at? Thanks, Tom -- “What we do for ourselves dies with us. What we do for others and the world remains and is immortal.” Albert Pine Tom Taylor - retired penguin AMD Phenom II x4 955 -- 4GB RAM -- 2x1.5TB sata2 openSUSE 12.1x86_64 openSUSE 12.2x86_64 KDE 4.7.2, FF 7.0 KDE 4.8.4, FF 13.0 claws-mail 3.8.0 registered linux user 263467 linxt-At-comcast-DoT-net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 1

[opensuse-factory] RFC: Please enable tap-to-click by default (redux)
by Atri 29 Jun '12

29 Jun '12

Hi! This has been discussed at length previously [1] with detailed arguments to both sides of the view, but with a couple of years having passed by since that discussion, and with many laptop shipping with touchpads lacking dedicated click-buttons [2] these days, it might be worthwhile to revisit the decision to disable tap-to-click by default on touchpads. At present, the tap-to-click capabilities in the xinput stack are configurable enough to be enabled by default while still allowing it to be deactivated upto a few seconds after the last keyboard stroke, thus preventing accidental tap-to-clicking while typing. As a result tap-to-click today provides a comfortable and safe input experience for (all?) users. I don't have any data really to make an honest claim, but from my experience most laymen users search for and turn on the configuration to tap-to-click the first thing on GNOME, KDE, etc. anyway. Turning this on by default reduces them that first "trouble". Enabling it by default will provide a welcome benefit for most users, not to mention new comers who are just used to tap-to-clicking on other user-enviroments (win, mac) from the get go. Also, along with this, enabling by default the option to deactivate tap-to-click for a few seconds after the last keystroke while typing takes care of accidental clicks and I think, therefore, this change will be welcome to all. I am surely out of my depth here, but I understand this change would likely involve modifications to the default xorg configuration and a few changed settings in the default settings of the desktop environments (GNOME, KDE, xfce, etc.) but nothing humongous. If there is broad agreement, I could try to work this myself with help and advice from the many experts here. Opinions please ;) Thanks for the attention and bye. -- Atri [1] In the mailing lists ( http://lists.opensuse.org/opensuse-factory/2010-06/msg00256.html ) and over at bugzilla ( https://bugzilla.novell.com/show_bug.cgi?id=554884 ) [2] Resembling this, for example: http://sp.sony-europe.com/da/977/292797.jpeg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

7 12

[opensuse-factory] XZ
by Nelson Marques 29 Jun '12

29 Jun '12

Do we still need to have: 'BuildRequires: xz' for Factory or has the situation changed ? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

Re: [opensuse-factory] Tumbleweed 12.1 - lost "Power Management Service"
by Patrick Shanahan 29 Jun '12

29 Jun '12

* Patrick Shanahan <paka(a)opensuse.org> [06-28-12 16:20]: > > opened systemsettings to adjust "Energy Savings" because my monitor was > not shutting down the backlight in the screen saver. > > I see: > > "Power Management configuration module could not be loaded. The Power > Management Service appears not to be runnint. This can be solved by > starting or scheduling it inside 'Startup and Shutdown'" > > When opening "Startup and Shutdown", "Service Manager" group is not > available. I get err msg: "Unable to contact KDED" and grayed-out options > which are not selectable. All "Load-on-Demand Services" and "Startup > Services" status is "Not Running". > > > openSUSE 12.1-> Tumbleweed > x86_64 > nvidia 295.59 > kdelibs4-4.8.4-7.4.x86_64 > kernel-desktop-3.4.3-30.1.x86_64 ps: My appologies for hijacking, corrected. and: my screen saver is now blanking completely but I still have no access to "Power Management" via systemsettings and no idea which app or cl options perform same function ???? 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

2 1

[opensuse-factory] akonadi will not start :^(
by Patrick Shanahan 28 Jun '12

28 Jun '12

somehow akonadi is broken and will not start meaning no calendar, ... openSUSE 12.1+ Tumbleweed error messages at: http://wahoo.no-ip.org/~pat/akonadi-selftest-report-20120627.txt possible troubleshooting from google provides no solution route as I can determine, but .... 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 7

[opensuse-factory] Yast Grub2 Boot Loader missing title edit field
by Roman Bysh 28 Jun '12

28 Jun '12

Hello all, Beta 2 was when the new Grub2 Boot Loader first came out with more editing features - similar to Grub1. As in Grub1, we were able to edit the title. However,this field is missing. Is it up and coming? Or should I report it as a bug? 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

3 6

[opensuse-factory] Repository GNOME:Contrib is dead
by Atri 28 Jun '12

28 Jun '12

Hi! Please note that the repository GNOME:Contrib [1] is now dead. Packages previously in this repository have all been pushed to Factory. If this is in the list of your subscribed repositories, please remove it (using zypper rr <reponame> or from YaST, etc.) Thanks and bye. -- Atri [1] This used to be the development branch of GNOME packages living in Contrib http://download.opensuse.org/repositories/GNOME:/Contrib/ -- 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] Python for after 12.2
by todd rme 27 Jun '12

27 Jun '12

Considering all of the talk about improving openSUSE quality, and with 12.2 branched, I would like to discuss somewhat how to move forward with Python packaging in openSUSE. There are three big things happening right now with Python for openSUSE. First, and most prominently, is Python 3. Python 3 has been supported on openSUSE since at the latest 11.4. However, Python 2.x still remains the default, but it will no longer be getting upstream updates. At the present time I don't see that being quite ready to change, since some critical packages (like django, wxpython, and matplotlib) are still Python 2-only. Unless all of those, and probably some others, support Python 3 by the next openSUSE release, I don't think switching will work. We probably need a list of packages that need python 3 support before we switch to python 3 by default. That doesn't mean Python 3 doesn't matter. I and several others have been working to get Python 3 support for most critical Python packages available for openSUSE 12.2. I think we have largely succeeded. For the next openSUSE release, I think we should have a policy that, if a new python package is submitted that has upstream Python 3 support, it must be submitted with both Python 2 and Python 3 versions of the package. There might even be a policy that any packaging of a new version of a python package that supports Python 3 should also have the Python 3 version packaged, but that may be going too far. Further, I think we should have an embargo on any new Python packages that do not have Python 3 versions and don't appear to have been updated within the last couple of years, since it is unlikely such packages would ever get a Python 3 version. Of course exceptions can be made on a case-by-case basis, for instance if the package is a dependency of an important Python package. In the end I don't think we really want unmaintained software to begin with, but this is all the more serious when it is unmaintained software that depends on deprecated, unmaintained software. There is an issue that some Python packages install non-versions software, such as in /usr/bin. This makes installing Python 2 and 3 versions in parallel difficult. For the next openSUSE release I intend to implement update-alternatives for these files, so users can easily switch between running Python 2 and Python 3 versions. This also solves some issues where Python 3 versions of packages depend on the Python 2 versions. I know there is a Python Package Index Reader that scans pypi for updated packages. I don't know how it works myself, but is there a way to also scan to see if the package supports Python 3? They should have one or more of the following categories: "Programming Language :: Python :: 3", "Programming Language :: Python :: 3.0", "Programming Language :: Python :: 3.1", "Programming Language :: Python :: 3.2", or "Programming Language :: Python :: 3.3". Sending regular email alerts about such packages that do not yet have Python 3 versions would be nice. Also, currently most Python 3 packages that use the same tarballs as the Python 2 versions have the Python 3 version link to the Python 2 version, which has Python 2 and Python 3 spec files. I would like to turn this around for the next openSUSE release, so the Python 2 version links to the Python 3 version and the Python 3 version is the official factory devel package. The point of all of this is to ease the transition to having Python 3 as the default easier, which I expect will likely will happen wit2 release after 12.2, judging by the rate of progress of upstream Python 3 porting. Basically most or all of the tasks that are needed before we would be ready to switch the default Python version should be done for the next openSUSE release. There are 3 other issues, which are more openSUSE-specific. First is the new python autodeps system, which should allow the requires of Python 2 and 3 packages to be automatically detected. This will make packaging python easier and installing python packages more reliable. It still needs testing. I suggest a tiered approach: first, which I am doing now, I am testing it against all the python packages in devel:languages:python3. If that seems to work, I will then switch to implementing it directly in devel:languages:python3. If that works, I also implement it in devel:languages:python. If that works, it can be implemented globally (at least for Factory build targets). The second is --record-rpm. This allows python to automatically list files that are then used by rpm file lists. As far as I understand this is an openSUSE-specific hack whose use is now discouraged. It also leads to some problems, especially if the upstream package name changed. If this understanding is correct, I think this should be officially deprecated, with a plan to remove it for 2 releases after 12.2. For the release after 12.2, I think it should go through a few stages. First, add an rpmlint warning about the use of this build option. After a couple months, upgrade the badness of this warning so it causes an automatic package failure. A few months after that, change the warning to an error. No packages in Factory should use the option. Finally, there is the use of the common %{python_sitelib}/* and %{python_sitearch}/* items in the rpm files list. These have been used a lot because they make packaging easier. However, they have the disadvantage, in my opinion, that there can be (and are) major changes in the upstream package, even complete name changes, that go undetected because these commands essentially match every possible python file. I think we should discourage this in the wiki, reject new packages that use it, and add an rpmlint warning for it, with the goal of removing this entirely from the next openSUSE release. So does anyone have opinions on these proposals? I know this is a big wall of text, so I can break it up into individual messages with different issues you think that would simplify reading or discussion. -Todd -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 8

[opensuse-factory] KDE and Gnome Live CD Builds broken
by Larry Finger 27 Jun '12

27 Jun '12

Coolo, I am not sure how long I should wait to report a broken build. Please give me some guidance. Since at least June 25 at 16:00 UTC, the KDE Live CD fails to build with buildinfo is broken... it says: unresolvable: nothing provides libqt4 = 4.8.1 needed by libqca2, nothing provides libqt4-sql = 4.8.1 needed by libqt4-sql-mysql, nothing provides libqt4 = 4.8.1 needed by qt4-qtscript Since the update of GCC4.7 on June 27, the Gnome Live CD fails with [364/1566] installing libquadmath47-4.7.1_20120615-4.3 file /usr/lib64/libquadmath.so.0.0.0 from install of libquadmath47-4.7.1_20120615-4.3.x86_64 conflicts with file from package libquadmath46-4.6.3_20120301-6.1.x86_64 Thanks, Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] 12.2 repo availability
by Felix Miata 27 Jun '12

27 Jun '12

I keep seeing comments like "I changed my package list update script to point to openSUSE:12.2" & "branched 12.2", but on mirrors all I see that ID as 12.2 (as opposed to 12.2M5 or 12.2Beta2) when "installed" are: http://download.opensuse.org/factory/ http://download.opensuse.org/factory-snapshot/ http://download.opensuse.org/factory-tested/ Has 12.2 actually branched off of Factory, or am I just not finding the latest's secret hiding place(s) on the mirrors? -- "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