February 2011 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] how debug shutdown not working?
by johnm_s2 15 Feb '11

15 Feb '11

11.4 RC1 x86_64 This system used to shutdown & poweroff just fine running 11.2. Now it doesn't poweroff though. It makes it to 'runlevel 0 reached', and hangs there. Magic sysrq keys won't even work. Ctrl-Alt-Del won't work. I have to manually power it off or reset it. I see nothing helpful in /var/log/messages. The console does say just before runlevel 0, '/etc/init.d/rc line 339 12345(some #) killed $link start' Don't know if that matters. -johnm -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

Re: [opensuse-factory] cdrecord licensing is NOT RESOLVED
by Jeff Mahoney 14 Feb '11

14 Feb '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/14/2011 12:55 PM, Joerg Schilling wrote: > Jeff Mahoney <jeffm(a)suse.com> wrote: > >> Kind of like this one. Take it elsewhere and leave the rest of us in peace. > > If you have nothing useful to say, please stay quiet...... > > This list needs collaborative people. [Re-posting this publicly since it is actually relevant to the discussion.] Agreed. The problem, Joerg, is that your behavior is not conducive to collaboration. It's divisive and noisy. I'm sick of the endless license discussions where everyone is wrong except for you. Anyone who disagrees is dismissed without discussing the merits of what they are saying, just that "they should go research" because "clearly" then they would agree with you. That's not productive. It's infuriating, insulting, and makes people dismiss you as a trolling crackpot. Seriously, Joerg, you must have noticed by now that this behavior makes most people just ignore or dismiss you outright. You declare to have private knowledge of events, use that as evidence to enhance your claims, yet never offer proof. When someone else disagrees with your position, you demand proof, which on its face is entirely acceptable - but for the fact that you are consistently hypocritical about adhering to that standard yourself. You assume that you're the only person who has ever talked to a lawyer and there's no evidence to back that up. Even some of your claims have been refuted by the people you have claimed to have made them. Ignoring all that, since it's clear you have no intention of ever changing your behavior, let's get back to the original topic. The simple fact is that most people on the opensuse-factory list _do not care_ about licensing issues. Yes, they're important to the life of the project but for most people they are irrelevant. You can debate the effectiveness of debian-legal all day but the single most important service it offers is removing the debate from the inboxes of people who simply do not care about it. When it's so easy to create another list, there's no reason to force members of _this_ list to be an audience to a discussion that they want no part of. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk1ZcDQACgkQLPWxlyuTD7KtUgCfTmc88DgiUN74JHVDWuoo/6Yu /DYAnj9kDvqS1Zv/paY5ceQBSYrINR/O =Gc/T -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 4

[opensuse-factory] cdrecord licensing is NOT RESOLVED
by Ray Cast 14 Feb '11

14 Feb '11

Hi,Someone here said that the licensing issues have been resolved. I cannot see how: nothing has changed.Schily will of course claim they *never existed*. But as long as there is *some doubt*, I consider shipping compiled cdrecord a certain legal *risk*. It doesn't need to be a proven copyright violation to be a risk; so Joergs claims are not sufficient for me. Apparently, RedHat, Debian etc. also still see this issue persist. Be careful with anything Joerg claims. He likes citing himself (e.g. his own "OSSCC" - yes, that is him, too!) and as you have seen at the same time claims that Eben Moglen backs his view and calls him a liar. To him, anything supporting his claims is sound and anything else thus must be a lie. And of course, calling someone a liar then is a fact, not an insult, to him?!? But actually none of his claims have been supported by a court so far either. The risk thus persists! As far as I can tell, the key point is what you consider to be a "derivative work" and what not.Schily says that linking a library and using header files only makes a "collective work", and thus he licence combinations are valid. There is little doubt that a "collective work" (such as SuSE as a whole) can contain both CDDL and GPL code. However, most people consider linking GPL code to form a "derivative work" (after all, this is why the LGPL was created - with Joergs interpretation, LGPL and GPL would be the same!). As far as I can tell, Joerg would concur that building a "derivative work" with GPL and CDDL breaks the licensing. His "workaround" is denying that it it a "derivative work" at all, but that it is a "collective work". Neither interpretation was so far tested in a court as far as I can tell. And of course I did not measure the term "most" in the previous sentence, nor am I a lawyer. But basically when you aren't 100% sure that cdrtools entirely qualifies as "collective work", you cannot distribute *compiled* versions. (The derived vs. collective work part is a compile time issue; distributing the uncompiled source code should be okay). We need to be *really careful* here, and it seems best to go the safe way and NOT ship cdrecord. Sooner or later, he will have a go at us then, call us liars, claims that we broke his software, slandered his name as author, introduced bugs and so on. Like he has done to everyone else so far! You already have him seen attack just about everyone on this list the last weeks; are you sure you want to have him as upstream author? I'd not be willing to take care of a cdrecord package given an upstream this hostile. And since there is no other upstream author, there is noone else to talk to. Schily has also shown very unwilling to adopt cdrecord to the users; instead the users are expected to adopt to cdrecord. For example, he has always told people to use the SCSI emulation and SCSI-like device ids instead of accepting that some users prefer referencing devices by their unix path name such as /dev/hda in particular for non-SCSI devices. From a user perspective this makes a lot of sense to use the same device name for both mounting and writing CDs. If I understood the early fights correctly, such patches have in fact been one of the things that Schily hated about Debian and wodim. Wodim has worked correctly for me every single time. (I don't use blueray though)And the future solution should be libburnia, which is actively developed and seems to have a sane upstream instead of a madm^W^W Schily. So I see no need at all to go the risky way of "shipping" cdrecord. Wodim is okay as an interim solution, and libburnia is the way to go on the long run!There is a cdrecord-like wrapper in libburnia called "cdrskin" that is meant to serve as drop-in replacement for the "cdrecord" command. Regards,Ray -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 18

[opensuse-factory] python problems "ImportError: could not import gobject (could not find _PyGObject_API object)"
by Stefan Seyfried 14 Feb '11

14 Feb '11

seife@susi:/dev/shm> python Python 2.7 (r27:82500, Aug 07 2010, 16:54:59) [GCC] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import gtk Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py", line 40, in <module> from gtk import _gtk ImportError: could not import gobject (could not find _PyGObject_API object) >>> import gconf Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: could not import gobject (could not find _PyGObject_API object) Is this a transient failure or should I file a bugreport? (This hits e.g. virt-manager) -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 3

[opensuse-factory] RFC: webkitgtk 1.2.x or 1.3.x for 11.4?
by Vincent Untz 14 Feb '11

14 Feb '11

Hi, So far, for 11.4, we've chosen the "let's have latest webkitgtk in Factory to avoid bunches of security issues". But as I wanted to update to 1.3.11, I see it now requires libsoup 2.33. So I now wonder what to do: maybe we'd want to go back to the 1.2.x stable branch. Or should we go ahead and use libsoup 2.33? Here are some pros/cons: webkitgtk 1.2.x =============== Pros: + stable release + no need to require unstable libsoup Cons: - might not see tons of security updates once 1.4 is out - not latest webkit webkitgtk 1.3.x =============== Pros: + many nice improvements (accessibility, drag/drop, WebSocket, improved HTML5 support, HTTP cache, etc.) + probably includes more fixes for security bugs + probably easier maintenance after 11.4 is out since we'll likely just update to new upstream version Cons: - officially an unstable release (no major bug, though) - requires unstable libsoup As far as libsoup is concerned, 2.33 is API compatible, and contains some new features for the new webkit. 2.34 should be out in April, so we could update to it after 11.4 is released. Just to avoid some security-maintenance nightmares, I'm leaning towards staying with 1.3.x and updating libsoup. Opinions? Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 3

[opensuse-factory] 11.4RC1 problems
by Peter Nikolic 14 Feb '11

14 Feb '11

Hi . Right hardware Compaq Presario V5030 AMD Turion 64 1.5Gb Ram ATI video (shared memory) New install 11.4RC1 x86_64 downloaded last night several hard lockups needing me to force a restart Kmix is doing my head in how can i get away from this horrible tabbed layout where each slider is in it's own tab it wastes space and is very very clunky and amatuerish and look horrible is difficult to use I wanted to test the problem i saw mentioned about overheating on mobile broadband connections as the laptop is almost exclusively used with a mobile domgal but i coud not get the "vodafone-mobile-connect" to work on 11.4 and no network manager does not work with the vodafone dongal so it has to be the vodafone software no lockups on 11.3 and no problem with kmix or vodafone . Pete -- Powered by openSUSE 11.3 (x86_64) Kernel: 2.6.34.7-0.7-desktop KDE Development Platform: 4.5.5 (KDE 4.5.5) "release 1" 15:30 up 2 days 16:27, 4 users, load average: 0.54, 0.38, 0.28 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

8 12

[opensuse-factory] Can somebody please trigger a rebuild for factory standard blender x86_64
by Dave Plater 14 Feb '11

14 Feb '11

Hi, even though openCOLLADA was checked into factory 15 minutes before the x86_64 blender managed to build with the old openCOLLADA . Please trigger a rebuild. Thanks Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 2

[opensuse-factory] CPU frequency scaling doesn't work (RC1).
by Carlos E. R. 13 Feb '11

13 Feb '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I get a warning (two, actually) in gnome that frequency scaling is unsuported; and the applet says that both cores run at 2.09 GhZ. In 11.2 they run at 1.20. CPU is Intel T4300. This means higher temperature and more battery ussage (it is a laptop). Is this problem known? (test partition of system was upgraded from 11.3 to 11.4 RC1 sucesfully) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAk1V6KoACgkQtTMYHG2NR9WL6QCfSsWcsxta8nSxeIOC4bEjjm/f DvwAmwTRPuFEL6Be97D89cUHYiXbxc9d =7Cyz -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 6

[opensuse-factory] Problem after installing 11.4 RC1
by C 13 Feb '11

13 Feb '11

I did a test install (on a laptop, Atom CPU, Intel video) of 11.4RC1 from DVD iso. I selected Gnome as the desktop and did a default install. After the install completed, I was left with a desktop that looked like this: http://www.digitaldragon.ca/Screenshot.png (the two squares top left explained below) So, the bottom panel is empty. I cannot add anything to the panel either (eg I right click and add to panel.. anything I try to add never shows up). I tried creating a new user and logging in as that user... same thing. I hit Alt+F2 and started an xterm (actually did this twice), and got the squares you see in the top left of the screenshot. So... anyone else seeing this? C. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 2

[opensuse-factory] License question :-)
by Stefan Seyfried 13 Feb '11

13 Feb '11

Hi, not trolling, I promise. What's the license of the aaa_base package? The RPM says "GPLv2+" /usr/bin/old says nothing, only "Copyright ... SuSE Linux AG" Is the whole aaa_base "GPLv2 or later"? Thanks -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 4