November 2010 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] OpenOffice failure
by Donn Washburn 08 Nov '10

08 Nov '10

Open Office fail to get past it's openSuSE bootscreen. From a konsole - soffice error donn@m1lhs:~> soffice terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' KCrash: Application 'soffice.bin' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/donn/.kde4/socket-m1lhs/kdeinit4__0 This is the same error as seen on other programs. cd to /usr/lib/ooo3/program and run ./soffice.bin by passes the bootsplash and still gets the error. scalc geets a bootsplash and fails the same way/ -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb(a)comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 1

[opensuse-factory] empathy bug
by Roelof Wobben 08 Nov '10

08 Nov '10

Hello, I see that the empathy bug is still open and has a SR since the 28th. Can someone look what happens to the SR. Roelof -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 4

Re: [opensuse-factory] libjpeg-turbo
by Andrew Jorgensen 08 Nov '10

08 Nov '10

On Thu, 2010-11-04 at 15:30 -0300, Cristian Rodríguez wrote: > El 04/11/10 15:10, Andrew Jorgensen escribió: > > Moving to libjpeg-turbo would fix bnc#620175 Opensuse 11.3 Chrome Stable > > Crashes When Trying to Attach a File. > > > > Basically the problem is that Google's build of Chrome is against > > libjpeg6 (because Ubuntu and Fedora use 6 - Fedora 14 uses > > libjpeg-turbo, I haven't checked Ubuntu yet). This causes chrome to > > crash > > We have our chrome builds, do not use Google's build, unfortunately > vendors, as odd it may sound, having millions of dollars and huge > staffing have zero clue about how to deliver working/correct rpms. Many people, myself included, prefer to use Google's own upstream build. Similarly for a number of other packages. One reason is that our builds of chromium are not updated on the same schedule as upstream. Also our builds enable a number of unstable features that upstream does not. The fact that openSUSE is in third place means that in order to follow third-party apps that don't want to have a dedicated openSUSE channel means that we should follow what first (Ubuntu) and second (Fedora) are doing for their major underlying libraries. That's not a criticism of openSUSE, it's just the reality of our position in the community. The more we deviate the more third-party apps (and proprietary apps) will break on our distro, which unfortunately will make us less relevant, not more. There are other good reasons to use libjpeg-turbo, namely the 2-4X speed (also battery) improvement. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 10

[opensuse-factory] Help there's a problem with https://build.opensuse.org/package/show? action menu.
by Dave Plater 08 Nov '10

08 Nov '10

I am getting very frustrated with the build service : I can work around checkin to newly relinked packages that wants to mangle my spec file and delete the contents of local copies but now I'm pulling my hair out. I cannot access the "Alter Package Information" item in the "Actions" menu link in the overview page, "only report bug", in packages where I'm maintainer but not a project maintainer. I can alter the information via "osc meta pkg graphics openCOLLADA -e" and it appears after about 15 min to 1 hour but I cant do anything in the web ui except report a bug to myself. I tried a message to the build service list. This morning (UTC +2) I tried the #opensuse-buildservice irc and I got this : <davepl> Hi, can somebody help with a bug in the webui part of the build service. I can only access report bug on the action menu, when logged in via https://build.opensuse.org/ and https://build.opensuse.org/stage/. This happens in all packages where I'm package maintainer but not a project maintainer. ie. The Action menu link on the overview page in "multimedia:libs jack" gives me : report bug, delete package, edit package [11:12] <davepl> information, submit package, branch package and a second report bug at the bottom.The Action menu link on the overview page in "graphics blender" gives me : report bug only. I'm a project maintainer in multimedia:libs but only a package maintainer of graphics blender. I can use the command line osc meta pkg graphics openCOLLADA -e (the package I actually want to change) and the change goes through and further command line [11:12] <davepl> osc meta pkg shows the change but I can't see it in the web ui (yet). If I try "osc meta pkg graphics dcraw -e" I get "no permission to change package" which is expected. So we aren't back to normal. [11:12] [404] davepl #opensuse-buildservice Cannot send to channel [11:12] [404] davepl #opensuse-buildservice Cannot send to channel [11:12] [404] davepl #opensuse-buildservice Cannot send to channel [11:14] <-> nickserv> help register [11:14] [Notice] -NickServ- ***** NickServ Help ***** [11:14] [Notice] -NickServ- Help for REGISTER: [11:14] [Notice] -NickServ- [11:14] [Notice] -NickServ- This will register your current nickname with NickServ. [11:14] [Notice] -NickServ- This will allow you to assert some form of identity on [11:14] [Notice] -NickServ- the network and to be added to access lists. Furthermore, [11:14] [Notice] -NickServ- NickServ will warn users using your nick without [11:14] [Notice] -NickServ- identifying and allow you to kill ghosts. [11:14] [Notice] -NickServ- The password is a case-sensitive password that you make [11:14] [Notice] -NickServ- up. Please write down or memorize your password! You [11:14] [Notice] -NickServ- will need it later to change settings. [11:14] [Notice] -NickServ- [11:14] [Notice] -NickServ- You have to confirm the email address. To do this, [11:14] [Notice] -NickServ- follow the instructions in the message sent to the email [11:14] [Notice] -NickServ- address. [11:14] [Notice] -NickServ- [11:14] [Notice] -NickServ- Syntax: REGISTER <password> <email-address> [11:14] [Notice] -NickServ- [11:14] [Notice] -NickServ- Examples: [11:14] [Notice] -NickServ- /msg NickServ REGISTER bar foo(a)bar.com [11:14] [Notice] -NickServ- ***** End of Help ***** [11:16] <davepl> /msg NickServ REGISTER davepl1954 davejplater(a)gmail.com [11:16] [404] davepl #opensuse-buildservice Cannot send to channel My nick is davepl and has been for a long time. This is taking up my precious time. Please help, a bug report about build service takes a life time. I think it was just last weekend I couldn't log in for a day until it was fixed which put me back with packages I was working on. Dave P user plater -- 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] -lwrap
by Donn Washburn 08 Nov '10

08 Nov '10

Once upon a time a person on this list someone told me how to solve a question with compiling when an error "-lwrap" shows up. I had this information stored away until a drive died. If that person is around HELP again. As information goes I remember it was a down loadable file dealing with NET. -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb(a)comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 3

Re: [opensuse-factory] libjpeg-turbo
by Andrew Jorgensen 07 Nov '10

07 Nov '10

It seems we should make sure other libraries mentioned in LSB are compiled against LSB versions of their dependencies wherever possible. So in this case we ought to modify QT and GTK+ to compile against libjpeg6 / -turbo. It may be a good idea to audit all LSB-related packages for dependencies on other versions. Even if that's not actually required by LSB it is something we ought to be doing to prevent conflicts. "Cristian Rodríguez<crrodriguez(a)opensuse.org>" <crrodriguez(a)opensuse.org> wrote: El 07/11/10 12:09, Cristian Morales Vega escribió: >>> That "libjpeg62 obsoletes and provides libjpeg8" is probably wrong? >>> Shouldn't it obsolete/provide libjpeg6? libjpeg-turbo has a different SONAME, so it SHOULD NOT not conflict, nor obsolete libjpeg8 in anyway. jpeg8 must remain installed on the user system on upgrade in case it is needed by other packages. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org -- 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] libjpeg-turbo
by Andrew Jorgensen 07 Nov '10

07 Nov '10

On Thu, 2010-11-04 at 18:06 -0300, Cristian Rodríguez wrote: > El 04/11/10 17:53, Andrew Jorgensen escribió: > > On Thu, 2010-11-04 at 21:16 +0100, Dirk Müller wrote: > >> On Thursday 04 November 2010, Pavol Rusnak wrote: > >> > >>> It seems only Arch and openSUSE have 8.0, all of the rest uses v6 or > >>> libjpeg-turbo. > >> > >> Thats correct, mainly due to LSB requirements, which we chose to ignore. > > > > I'm going to recommend that we stop ignoring LSB requirements. > > Oh really ? the LSB is non-sense. what good reasons ? At the risk of repeating myself: This pixbuf loader bug is just one example. The LSB exists to make it possible to run proprietary products on any LSB-compliant linux distro. And despite the tunnel-vision open source enthusiasts sometimes have there are a many important and useful proprietary products out there. When we fail to run some product that someone needs they go to Fedora or Ubuntu because the OS is irrelevant to the vast majority of customers. The only thing that matters is what the customer wants to /do/ with the OS. I realize that in some cases LSB fails to accomplish this goal but in this case it would have succeeded as it does in many cases. If you feel that LSB is failing to accomplish this in some way please step up and help give them constructive suggestions as to how it could be accomplished better. In the real world there will always be proprietary products and /we/ are better off if those products can run smoothly on our favorite distro. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 5

[opensuse-factory] New package for factory - openCOLLADA
by Dave Plater 06 Nov '10

06 Nov '10

Hi, with the new blender-2.55.32862 waiting be submitted to factory, I'm submitting (sr#52321) the openCOLLADA library package to factory as it's needed for blenders new collada import export feature and resides in the same graphics devel project as blender. Collada 3D import and export libraries COLLADA is a royalty-free XML schema that enables digital asset exchange within the interactive 3D industry. OpenCOLLADA is a Google summer of code opensource project providing libraries for 3D file interchange between applications like blender. COLLADABaseUtils : Utils used by many of the other projects COLLADAFramework : Datamodel used to load COLLADA files COLLADAStreamWriter : sources (Library to write COLLADA files) COLLADASaxFrameworkLoader : Library that loads COLLADA files in a sax like manner into the framework data model COLLADAValidator : XML validator for COLLADA files, based on the COLLADASaxFrameworkLoader GeneratedSaxParser : Library used to load xml files in the way used by COLLADASaxFrameworkLoader Authors ------- sebastian(a)opencollada.org gtempaccount.com robert(a)opencollada.org gtempaccount.com License = MIT See : https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exch… and http://www.opencollada.org/ Regards Dave P -- 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] libjpeg-turbo
by Andrew Jorgensen 05 Nov '10

05 Nov '10

On Thu, 2010-11-04 at 21:16 +0100, Dirk Müller wrote: > On Thursday 04 November 2010, Pavol Rusnak wrote: > > > It seems only Arch and openSUSE have 8.0, all of the rest uses v6 or > > libjpeg-turbo. > > Thats correct, mainly due to LSB requirements, which we chose to ignore. I'm going to recommend that we stop ignoring LSB requirements. There are some very good reasons to comply with LSB and we fail when we don't. This pixbuf loader bug is just one example. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

10 14

Re: [opensuse-factory] libjpeg-turbo
by Andrew Jorgensen 05 Nov '10

05 Nov '10

Moving to libjpeg-turbo would fix bnc#620175 Opensuse 11.3 Chrome Stable Crashes When Trying to Attach a File. Basically the problem is that Google's build of Chrome is against libjpeg6 (because Ubuntu and Fedora use 6 - Fedora 14 uses libjpeg-turbo, I haven't checked Ubuntu yet). This causes chrome to crash when a gtk filechooser dialog sees a jpeg file (tries to load the pixbuf loader which crashes because the loader is linked to libjpeg8). This mixed jpeg problem will also cause problems for any app or browser plugin compiled for other distros that happens to use gtk for file choosers. For example it causes a crash with Novell's Moonlight plugin on chrome for a similar reason (we use pixbuf loaders for all images, we're looking at switching). The fun part is that our own plugin only crashes in this way on our own distro. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 2

[opensuse-factory] libjpeg-turbo
by Cristian Morales Vega 04 Nov '10

04 Nov '10

Fedora 14 has been released with libjpeg-turbo (http://libjpeg-turbo.virtualgl.org/) I see we have multiple packages in home repos (home:Lazy_Kent, home:felfert, home:iboss32, home:mkromer and home:prusnak)... so someone can comment about this? Fedora sells this as a libjpeg API/ABI compatible changes that is just faster. From a quick look it seems to be API/ABI compatible with the old 6.2 version that was available for years, but 11.3 already provides the binary incompatible 8.0. What other distros do? Also, not sure if featurewise they are 100% equivalent (see https://bugzilla.redhat.com/show_bug.cgi?id=639672) Finally, this probably would be mostly a x86-64 improvement? Since we target i586 for x86-32, that doesn't provides MMX/SSE support, the speed improvement seems to be limited to a "25%" there. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

7 7

Version symbols in libraries that upstream doesn't (Was: [opensuse-factory] libjpeg-turbo)
by Cristian Morales Vega 04 Nov '10

04 Nov '10

2010/11/4 Andrew Jorgensen <ajorgensen(a)novell.com>: > Moving to libjpeg-turbo would fix bnc#620175 Opensuse 11.3 Chrome Stable > Crashes When Trying to Attach a File. > > Basically the problem is that Google's build of Chrome is against > libjpeg6 (because Ubuntu and Fedora use 6 - Fedora 14 uses > libjpeg-turbo, I haven't checked Ubuntu yet). This causes chrome to > crash when a gtk filechooser dialog sees a jpeg file (tries to load the > pixbuf loader which crashes because the loader is linked to libjpeg8). > > This mixed jpeg problem will also cause problems for any app or browser > plugin compiled for other distros that happens to use gtk for file > choosers. For example it causes a crash with Novell's Moonlight plugin > on chrome for a similar reason (we use pixbuf loaders for all images, > we're looking at switching). The fun part is that our own plugin only > crashes in this way on our own distro. Never looked too deep into this. But Debian seems to version symbols in a way that would solve this kind of problems (http://wiki.debian.org/Projects/ImprovedDpkgShlibdeps) Since for any precompiled binary this can happen with a lot of libraries this could be something good to copy. As a side effect it would also remove the need for macros as "%kde4_runtime_requires" (in an ideal case). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] libdbi Contrib -> Factory
by Peter Czanik 04 Nov '10

04 Nov '10

Hello, I wonder, if libdbi and libdbi-drivers could be moved from Contrib to Factory. Reason: syslog-ng's database support is based libdbi. If libdbi(-drivers) is moved to Factory, then database could be enabled as part of the next release. Bye, -- Peter Czanik (CzP) <czanik(a)balabit.hu> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 3

[opensuse-factory] SLES 11 Update Server broken
by Günther J. Niederwimmer 04 Nov '10

04 Nov '10

Hello, is this known? I will only tell all the people the update server for SLE is broken last night. The bad thing is to reregister the system after a broken connect, zypper disabled the repository :(. -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- 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] Status: Milestone3
by Stephan Kulow 03 Nov '10

03 Nov '10

Hi, The most annoying M2 bug is still not fixed (Xorg crashes) and I don't consider releasing Milestone3 in this state useful ;( So I will cancel Milestone3 and move it to hopefully next week. If we can't get to the core of it, we may need to disable compositing use in KDE. Greetings, Stephan -- Sent from openSUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

[opensuse-factory] Systemd and sysconfig
by Cristian Rodríguez 03 Nov '10

03 Nov '10

Hi: While I personally object the whole idea of "sysconfig" files, they are a reality and are widely used, what is the proper way to reference them from systemd units ? ExecStartPre is the only thing I need right ? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] Dead link in factory iso readme
by pistazienfresser (see profile) 03 Nov '10

03 Nov '10

Hello! Maybe someone could and would update the link to the wiki in the README.FIRST (and maybe the article in the actual wiki, too)? Regards pistazienfresser http://download.opensuse.org/factory/iso/README.FIRST http://old-en.opensuse.org/Factory/Status http://en.opensuse.org/Portal:Factory -- - openSUSE 11.2 with GNOME 2.28.2 (or KDE 4.3.5) and Kernel Linux 2.6.31.14-0.1-desktop (or ~pae, ~default, Ubuntu 10.4 LTS 'lucid' 2.6.33-24-genetic, MS Win XP) - Samsung X20 Pentium M 740 (1730 MHz) Intel 915GM 1400x1050 - openSUSE profile: https://users.opensuse.org/show/pistazienfresser -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

[opensuse-factory] Suggesting network:samba:misc as devel-project for SMBTA
by Holger Hetterich 02 Nov '10

02 Nov '10

Hi, I would like to suggest network:samba:misc as the devel-project for SMB Traffic Analyzer ( http://holger123.wordpress.com/smb-traffic-analyzer/ ). Basically it produces two packages "smbtad" and "smbtatools". I've done a submitrequest for factory for both of them today. Holger -- Holger Hetterich, hhetter(a)novell.com, SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

[opensuse-factory] All factory lists, what to do with them?
by Rajko M. 02 Nov '10

02 Nov '10

http://lists.opensuse.org/opensuse-factory-base List of the developers of the openSUSE:Factory devel project Base:System Last post: http://lists.opensuse.org/opensuse-factory-base/2009-08/date.html http://lists.opensuse.org/opensuse-factory-graphics List of the developers of the openSUSE:Factory devel project graphics The only post: http://lists.opensuse.org/opensuse-factory-graphics/2009-10/date.html http://lists.opensuse.org/opensuse-factory-mozilla List of the developers of the openSUSE:Factory devel project mozilla Last post: http://lists.opensuse.org/opensuse-factory-mozilla/2010-10/date.html It seems that creating developers lists wasn't that big success. Only the last one has few entries in 2010, and majority of conversation was in: http://lists.opensuse.org/opensuse-factory-mozilla/2010-09/msg00000.html In my humble, we should get rid of all in order not to confuse unsuspecting potential developers, that would like to contribute to development version, but after review of mail lists find there is no activity and just go away. I know that mail lists are not the only way to check project activity, but imagine someone that checks 4-5 projects, with intention to join the one. How much time and thoughts one will give to project with dead development mail lists. Nowadays, no one will hunt down development communication channels, when some other places offer clear pointer to development communication. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 4

[opensuse-factory] Factory mail list description.
by Rajko M. 02 Nov '10

02 Nov '10

I would like to see somewhat different (better) list description. Now it is: "Discussion about all Alpha, Beta, RC and Factory versions of openSUSE." It would be better to have: "Discussions about development of next openSUSE version." -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1