Re: [opensuse-factory] classpath-webplugin
Andreas Vetter wrote: On Mon, 17 Sep 2007, Martin Schlander wrote: Can I suggest - Making the sun plugin conflict with the classpath webplugin. - Preferably don't install the classpath version at all, if you're worried about completely free java go for java 7 it would be more reliable than classpath. I had this problem too. This was on x86_64 however, but I installed 32-bit firefox and sun java-plugin and had problems getting it to work until I figured out that I must manually remove classpath-webplugin. I thought classpath-webplugin was only installed by default on 64-bit installations, but apparently it's also done on 32-bit - it doesn't do much good anywhere - but on 32-bit it's extra problematic. I support Benji's proposed resolutions. IMO it is a mistake to release a 64 bit firefox without a really (!) working java. Releasing a 32 bit firefox was much better in the older distros. Anyone opened a bug to let the plugins conflict? IMHO that's mandatory. It makes absolutely no sense to have more than one plugin installed for one type since at least all Mozilla stuff behaves non-deterministic in choosing one :-( And I agree that not having a working Java plugin is almost as bad as not having a working Flash player (which should basically work maybe only with manual interaction with nspluginwrapper though). So replacing Firefox with the 32bit version, removing classpath-webplugin and installing Sun's 32bit Java with plugin will be an FAQ :-( Wolfgang - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] classpath-webplugin
On Tue, 18 Sep 2007, Wolfgang Rosenauer wrote: Andreas Vetter wrote: On Mon, 17 Sep 2007, Martin Schlander wrote: Can I suggest - Making the sun plugin conflict with the classpath webplugin. - Preferably don't install the classpath version at all, if you're worried about completely free java go for java 7 it would be more reliable than classpath. I had this problem too. This was on x86_64 however, but I installed 32-bit firefox and sun java-plugin and had problems getting it to work until I figured out that I must manually remove classpath-webplugin. I thought classpath-webplugin was only installed by default on 64-bit installations, but apparently it's also done on 32-bit - it doesn't do much good anywhere - but on 32-bit it's extra problematic. I support Benji's proposed resolutions. IMO it is a mistake to release a 64 bit firefox without a really (!) working java. Releasing a 32 bit firefox was much better in the older distros. Anyone opened a bug to let the plugins conflict? IMHO that's mandatory. It makes absolutely no sense to have more than one plugin installed for one type since at least all Mozilla stuff behaves non-deterministic in choosing one :-( And I agree that not having a working Java plugin is almost as bad as not having a working Flash player (which should basically work maybe only with manual interaction with nspluginwrapper though). So replacing Firefox with the 32bit version, removing classpath-webplugin and installing Sun's 32bit Java with plugin will be an FAQ :-( I reopened [Bug 264228] nspluginwrapper + java plugin problems [Bug 288750] Home bank issues with java+firefox on x86_64 to get a final decision. I know it's really late, but a 64bit system without a working firefox/java combination is a blocker in my eyes. -- Mit freundlichen Gruessen, Andreas Vetter Fakultaet fuer Physik und Astronomie Tel: +49 (0)931 888-5890 Universitaet WuerzburgFax: +49 (0)931 888-5508 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] classpath-webplugin
Den Tuesday 18 September 2007 10:01:20 skrev Stephan Kulow: Easing the update path in adding conflicts is very fine with me though. This should be reported though. https://bugzilla.novell.com/show_bug.cgi?id=325912 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] classpath-webplugin
Am Dienstag 18 September 2007 schrieb Andreas Vetter: I reopened [Bug 264228] nspluginwrapper + java plugin problems [Bug 288750] Home bank issues with java+firefox on x86_64 to get a final decision. I know it's really late, but a 64bit system without a working firefox/java combination is a blocker in my eyes. And I disagree. If we don't make it obvious that Sun's x86_64 is for servers only, no-one needs firefox there is wrong, there is no chance either Sun changes that or the open source java catches up. You're free to put your money behind either side, but we took side - on the OSS side of life (with a hopefully easy way for our users to go with a NON-OSS alternative if present on that architecture). Easing the update path in adding conflicts is very fine with me though. This should be reported though. Greetings, Stephan -- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] classpath-webplugin
On Tue, 18 Sep 2007, Stephan Kulow wrote: Am Dienstag 18 September 2007 schrieb Andreas Vetter: I reopened [Bug 264228] nspluginwrapper + java plugin problems [Bug 288750] Home bank issues with java+firefox on x86_64 to get a final decision. I know it's really late, but a 64bit system without a working firefox/java combination is a blocker in my eyes. And I disagree. If we don't make it obvious that Sun's x86_64 is for servers only, no-one needs firefox there is wrong, there is no chance either Sun changes that or the open source java catches up. You're free to put your money behind either side, but we took side - on the OSS side of life (with a hopefully easy way for our users to go with a NON-OSS alternative if present on that architecture). Hmm, I agree that Sun is the culprit, but I think it will fall back to openSUSE. At least we need a simple to follow guide how to get a working firefox with java (including a complaint to Sun). Easing the update path in adding conflicts is very fine with me though. This should be reported though. -- Andreas Vetter Fakultaet fuer Physik und Astronomie Universitaet Wuerzburg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Inclusion of deltarpm in base system?
Hi, now that delta RPMs work after bug 309124 has been fixed (I just verified this), I think the deltarpm package should be included in the 1-cd installation media, or more commonly in the minimal base system. It's quite small (200KB), so this hopefully should not be a problem. IMHO delta rpms are a superior feature and are a huge advantage of openSUSE on slower connections, so this should work out of the box (and during installation). Maybe it also should be added to the recommend section of libzypp's spec file. Cheers, Robin PS.: libzypp is really great in 10.3 - even better than what I expected :) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] graphics card on t61p can not be supported by opensuse 10.3
I've installed nv driver and run sax2 -r -m 0=nvidia But the graphics card is recognized as Framebuffer vesa. lenove thinkpad t61p's graphics cards is nvidia quadro 740m.
Re: [opensuse-factory] Inclusion of deltarpm in base system?
Am Dienstag 18 September 2007 schrieb Robin Knapp: Hi, now that delta RPMs work after bug 309124 has been fixed (I just verified this), I think the deltarpm package should be included in the 1-cd installation media, or more commonly in the minimal base system. It's quite small (200KB), so this hopefully should not be a problem. IMHO delta rpms are a superior feature and are a huge advantage of openSUSE on slower connections, so this should work out of the box (and during installation). On slower connections we sure do not suggest to use the 1-CD installations. They are made for a market with high bandwith connection. And it's installed by default if you do a 1-CD+FTP or a DVD installation. Greetings, Stephan -- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Inclusion of deltarpm in base system?
Zitat von Stephan Kulow [EMAIL PROTECTED]: Am Dienstag 18 September 2007 schrieb Robin Knapp: Hi, now that delta RPMs work after bug 309124 has been fixed (I just verified this), I think the deltarpm package should be included in the 1-cd installation media, or more commonly in the minimal base system. It's quite small (200KB), so this hopefully should not be a problem. IMHO delta rpms are a superior feature and are a huge advantage of openSUSE on slower connections, so this should work out of the box (and during installation). On slower connections we sure do not suggest to use the 1-CD installations. They are made for a market with high bandwith connection. And it's installed by default if you do a 1-CD+FTP or a DVD installation. Well, it depends(tm)... There may also be people who download the 1-CD media because the do have a rather slow connection and want to try out openSUSE without having to download the whole DVD. If they see that the online update uses delta packages, this may eventually convince them to chose openSUSE as their distribution. Other people may install without network access (i.e. because the have wireless which doesn't work during installation in 10.3) and add additional software afterwards, so the deltarpm might not get installed in such a case. So if there's still a few KB space left, I suggest to include it. If not... well, it's not nice but most people will be able to live with it. Maybe 11.0? Cheers, Robin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Inclusion of deltarpm in base system?
Am Dienstag 18 September 2007 schrieb Robin Knapp: So if there's still a few KB space left, I suggest to include it. If not... well, it's not nice but most people will be able to live with it. Maybe 11.0? Well, there are a few KB left, but we need 172 KB, which is not my definition of few :) 734003200 is the maximum size and our latest KDE CD build is 732286976 for i386 (x86_64 is smaller as we already remove KDE4). So right now we even have over a MB free, but this changes daily so I'm not adding few KB right now. But it's top of my list now ;) Greetings, Stephan -- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] novell ati driver
Hi, On Monday, September 17, 2007 at 13:24:34, Andreas Jaeger wrote: Florin Samareanu [EMAIL PROTECTED] writes: Do you think that the new opensource ati driver developed by novell will make it in 10.3? i`m asking because with my card (ati x1600 mobility) It's not mature enough yet for the 10.3 release. Once it gets mature enough, I expect to see the driver in our build service. Release early, release often :) http://download.opensuse.org/repositories/X11:/Drivers:/Video:/radeonhd/ There is a mailinglist about it now http://lists.opensuse.org/radeonhd/ Also dont forget to check out the irc channel on freenode irc://irc.freenode.net/radeonhd Have fun... Henne -- Henne Vogelsang, openSUSE. Everybody has a plan, until they get hit. - Mike Tyson - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Inclusion of deltarpm in base system?
Zitat von Stephan Kulow [EMAIL PROTECTED]: So right now we even have over a MB free, but this changes daily so I'm not adding few KB right now. But it's top of my list now ;) Ookay, well, then let's get surprised :) Robin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] YaST team minutes digest. Tue, Sept 11.
(last digest was Sept 4, not 9) Table of contents: * Open bugs for 10.3 * YaST workshop * Python-bindings news * Package management stack bug squashing * SLE10 SP1 * ncurses * Applets * Misc * Miscellaneous bugfixes Open bugs for 10.3 -- * Everyone please check your open bugs for openSUSE 10.3, and move them to openSUSE 11, if they're not going to be fixed for 10.3. Optionally you may create feature requests for enhancements, if appropriate * For 10.3 RC1 fix only major, critical and blocker bugs YaST workshop - * Please send jsrain and dmacvicar topics you want to present on YaST workshop Python-bindings news -- * Importing other YaST modules functionality added * Basic type checking implemented * UI and SCR can now be called from python code, still WIP Package management stack bug squashing - * Always refreshing susetags repositories, even if they were up-to-date now fixed * Fixed package size + related disk usage calculation for YUM repositories (bug #308475) * Installation in text-mode stuck on reading repository cache was caused by not providing correct alternative solution of busy cursor animation for ncurses (bug #309376) * Focus on getting the update stack working. CD eject/changing bug (#308362). Michael working on disk space calculation bugs (#308362) Important note: if you are implementing alternative solutions for GUI and text mode, please make sure you test your feature (bugfix) in both UIs. Similarly, if you're implementing feature (fixing a bug) for installation, make sure it gets properly tested in inst-sys SLE10 SP1 - * Installation server providing NFS4-based repository does not work * update of migrate-to-SP1 patch Ncurses - Text mode installation broken in beta3. Memory corruption problems? (#305196). (UPDATE: fixed. Unclosed dialog) Michael initiated discussion about one memory corruption bug in libzypp Stefan shared experience with one in the UI and the trick to dlopen and dlclose the library to keep it in memory. Applets. - Looking good. Still some bugs filed against them. Some of them are zypper bugs really. Misc. -- - Christian Kornacker has been working on developing some y2make all enhancements (goal: prefixed yast together with a non-system libzypp) Miscellaneous bugfixes * yast2-squid now supports opening ports in firewall and contains sysconfig file with firewall ports definition (bug #247745) * showy2log tool improved - now it can read from stdin * backporting Xen support to SLE9 SP4 (paravirtualized machine installation, paravirtualized drivers support in full virtualization) (feature #301974) * static IP configuration + proxy setup in 1st stage should work correctly by now (bugs #298001, #287801) * Install notify messages should no longer pop-up during package update in ncurses UI (bug #308410) * Using obsolete 'getcfg-interface' tool made yast2-dhcp-server unable to retrieve subnet information, thus resulting in generating invalid config file - now fixed (bug #308258) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Firewall not consistent..
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Carlos E. R. schreef: The Monday 2007-09-17 at 17:12 +0200, M9. wrote: You know that there are handheld gadgets that you carry in your pocket when you have a walk and beep or buzz when they detect a wifi. I have been told of people doing it in their cars, putting a special aerial with a magnet on the car roof. They can use a portable computer running a certain windows program that detects the networks it finds, and writes all that in a report. Plus, if connected to a GPS and a map software, it plots the findings in the map, with colors showing how kind are the neighbors. The person that told me this said that they were thinking on doing this for their final project on university, and had a round of the industrial park here with that setup. The findings were very /interesting/, but refrained from making them public. But I had seen a similar report published in an article by the IEEE, it wasn't news to me. Not your case, but people should be way more cautious with their wifis. On another message I wrote a sample of what damage can get done to such trusting users. I know this is true, because a friend of mine for years allways only uses some neighbours wifi-networks, he says that they pay for it anyway, if he uses them or not, but he only uses the internet connection, and does not intrude their networks or pc's. I have tried to crack mine, but only thing that happened was that the whole network went down every time... ;-) - -- Have a nice day, M9. Now, is the only time that exists. OS: Linux 2.6.22.5-10-default x86_64 Huidige gebruiker: [EMAIL PROTECTED] Systeem: openSUSE 10.3 (X86-64) Beta3 KDE: 3.5.7 release 58 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFG78uDX5/X5X6LpDgRAgHhAKDOgmEXVOgPcqK86vlWD6aR6Fdh7ACgpSGE zCY5QxYPBwRTFU0+bkB/E50= =mrbB -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Firewall not consistent..
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Carlos E. R. schreef: The Monday 2007-09-17 at 17:03 +0200, jdd wrote: Carlos E. R. wrote: A cracker can make his PC look like one of yours and connect, instantly. that is a cracker can guess your wep key (don't ask me how :-(), at the moment lurking the net gives him the mac adresse of the various hosts. Yes, but he didn't say if he is using wep. My point is, that basing security only in giving IPs to known machines, using the hardware address, is not secure. Added to other methods, yes. And wep... I was told of an ISP technician that installed all routers in his area withe keys of the 012345678901234567890xx type, the last to digits being related to the customer. The customers were happy because they had a long key that was easy to remember. The crackers were even happier. the problem is: why should a cracker do this on your network? If this was one of a big company or if your work is highly important, may be. may be also an evil neigbor Or one without ISP, and just wanting to send his emails free. I have a friend in that case. Somebody told me that once he tested his neighbors wifi network, and got in easily. He then captured the traffic, and managed to learn his bank login and password - shame on the bank for sending that in clear -. He even tested it by entering the bank account, and exited. Obviously, that neighbor was using windows. He said that, had he being malign, he would have connected to the bank from a second neighbor network, and sent the money to a third one: there would be no way to track him, and the police would blame the second neighbor. Anyway, M9 doesn't have neighbors, so he probably doesn't those problems :-) Looking into my bank-account, he/she would probably get tears in his/her eyes, and in pity, he/she would send some money to my account ;-)) - -- Have a nice day, M9. Now, is the only time that exists. OS: Linux 2.6.22.5-10-default x86_64 Huidige gebruiker: [EMAIL PROTECTED] Systeem: openSUSE 10.3 (X86-64) Beta3 KDE: 3.5.7 release 58 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFG78nqX5/X5X6LpDgRAsQbAJ9qZpjkTKNxRVLjpx2WUFlJ9kMo3QCfW4Ie lu7vs9A4096QkXlm+H+shUk= =+jk9 -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] build vs. lbuild
Hello, I tried to compile a package using current factory sources, and ran into the following problem using lbuild: expanding package dependencies... expansion error nothing provides /lib/libreadline.so.5.2 needed by bash nothing provides /lib/libhistory.so.5.2 needed by bash and it is actually right: pegasos0917:/data/10.3/suse/ppc # rpm -qp --provides libreadline5-5.2-16.ppc.rpm bash:/lib/libreadline.so.5 readline = 5.2 libhistory.so.5 libreadline.so.5 libreadline5 = 5.2-16 On the other hand 'build' can build the package from the same spec file. It's just a lot more slow to start up, and inconvenient to use... Which one is right? And a bonus question: is it worth reporting this dependency bug, now that only critical bugs are fixed? Or belongs this to the critical category? Even if it's not in factory, It certainly makes lbuild useless, which is also used by the PackMan team... (actually, I ran into the problem by trying to recompile a packman package for 10.3 on PPC). Bye, CzP - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] build vs. lbuild
Peter Czanik wrote: Hello, I tried to compile a package using current factory sources, and ran into the following problem using lbuild: expanding package dependencies... expansion error nothing provides /lib/libreadline.so.5.2 needed by bash nothing provides /lib/libhistory.so.5.2 needed by bash and it is actually right: pegasos0917:/data/10.3/suse/ppc # rpm -qp --provides libreadline5-5.2-16.ppc.rpm bash:/lib/libreadline.so.5 readline = 5.2 libhistory.so.5 libreadline.so.5 libreadline5 = 5.2-16 /lib/libhistory.so.5.2 is a file dependency and _is_ provided by libreadline5.rpm: $ rpm -qlp libreadline5-5.2-16.ppc.rpm | grep -F /lib/libhistory.so.5.2 /lib/libhistory.so.5.2 On the other hand 'build' can build the package from the same spec file. It's just a lot more slow to start up, and inconvenient to use... Which one is right? lbuild is wrong. build ignores file dependencies AFAIK, so in a way it's right :) Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] classpath-webplugin
I reopened [Bug 264228] nspluginwrapper + java plugin problems [Bug 288750] Home bank issues with java+firefox on x86_64 to get a final decision. I know it's really late, but a 64bit system without a working firefox/java combination is a blocker in my eyes. -- Mit freundlichen Gruessen, Andreas Vetter I have to agree with Andreas Vetter. Firefox/java/flash should simply work, without manual intervention, on any gui installation (even x86_64). In my opinion, the decision to go with only OSS solutions - even though they don't work right - is likely to push end-users toward other distributions. Please pardon me for slipping off-topic for a minute, but I'm surprised that so many things still aren't working at this stage in the release. For example, I'm still fighting with these issues: nvidia 6800 video artifacts require frequent X restarts USB flash drives only mount for root alt-F2 commands for yast and sax2 bring up my router's web page kdetv fails even though the tuner was found during installation Whenever I install a new alpha/beta of openSUSE, it takes a couple days to get some of my favorite applications working again. Part of this time is spent removing the openSUSE versions of some applications so that I can install versions that aren't crippled (codecs and torrents). We can't expect to lure anyone away from other operating systems and distributions with a broken web browser experience and multimedia experience. Gregg Nicholas p.s. I've been manually installing kpodder and Miro since I haven't found a repository that includes them. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] graphics card on t61p can not be supported by opensuse 10.3
2007/9/18, James Li [EMAIL PROTECTED]: I've installed nv driver and run sax2 -r -m 0=nvidia But the graphics card is recognized as Framebuffer vesa. lenove thinkpad t61p's graphics cards is nvidia quadro 740m. Your procedure was wrong. The nv driver, is the opensource driver, and You do'nt need to execute sax2 -r -m 0=nvidia, because this parameters for sax2 are for the propietary driver. The propietary driver appear in xorg.conf as nividia, and the opensource driver appear as nv. For installing the propietary driver, You can download it from: http://www.nvidia.com/object/unix.html You must has installed the kernel source, and must go to init 3, and executing the file with sh nvidia*.run as root. Later after completed the nvidia script, execute sax2 -r -m 0=nvidia - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] classpath-webplugin
Den Tuesday 18 September 2007 16:27:22 skrev Gregg Nicholas: I reopened [Bug 264228] nspluginwrapper + java plugin problems [Bug 288750] Home bank issues with java+firefox on x86_64 to get a final decision. I know it's really late, but a 64bit system without a working firefox/java combination is a blocker in my eyes. I have to agree with Andreas Vetter. Firefox/java/flash should simply work, without manual intervention, on any gui installation (even x86_64). In my opinion, the decision to go with only OSS solutions - even though they don't work right - is likely to push end-users toward other distributions. As it can be seen from my bugreports that avetter reopened I share the opinion that 32-bit Firefox should be shipped. Especially since software.opensuse.org has no warning about downloading the x86_64 version. However I don't think the decision has anything to do with ideology. When people install x86_64 they don't want 32-bit Firefox - they want to run full 64-bit so they can enjoy all the imaginatory performance improvements. Now we even have 64-bit OOo.. Flash works with nspluginwrapper with 64-bit Firefox - I don't know how many people actually come across java webapplets - personally I only need it for homebanking - but that of course is enough to make me install 32-bit Firefox - which I tested and downgrading ran without incident, except for me having to remove classpath-webplugin - and that issue will be fixed. I think that x86_64 users should expect some bumps here and there - but I also think that this should be noted on s.o.o .. we had that discussion before, but since these events show it's relevance I'm bringing it up again. It should somehow be communicated that x86 is the safest/simplest choice - also with x86_64 hardware. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] classpath-webplugin
Am Dienstag 18 September 2007 schrieb Gregg Nicholas: I reopened [Bug 264228] nspluginwrapper + java plugin problems [Bug 288750] Home bank issues with java+firefox on x86_64 to get a final decision. I know it's really late, but a 64bit system without a working firefox/java combination is a blocker in my eyes. -- Mit freundlichen Gruessen, Andreas Vetter I have to agree with Andreas Vetter. Firefox/java/flash should simply work, without manual intervention, on any gui installation (even x86_64). In my opinion, the decision to go with only OSS solutions - even though they don't work right - is likely to push end-users toward other distributions. Can you name a distribution that has a working java on x86_64? perhaps we can check how they solved it. Greetings, Stephan -- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] build vs. lbuild
Peter Czanik wrote: I tried to compile a package using current factory sources, and ran into the following problem using lbuild: expanding package dependencies... expansion error nothing provides /lib/libreadline.so.5.2 needed by bash nothing provides /lib/libhistory.so.5.2 needed by bash and it is actually right: pegasos0917:/data/10.3/suse/ppc # rpm -qp --provides libreadline5-5.2-16.ppc.rpm bash:/lib/libreadline.so.5 readline = 5.2 libhistory.so.5 libreadline.so.5 libreadline5 = 5.2-16 On the other hand 'build' can build the package from the same spec file. It's just a lot more slow to start up, and inconvenient to use... Which one is right? And a bonus question: is it worth reporting this dependency bug, now that only critical bugs are fixed? Or belongs this to the critical category? Even if it's not in factory, It certainly makes lbuild useless, which is also used by the PackMan team... (actually, I ran into the problem by trying to recompile a packman package for 10.3 on PPC). Please file a bug and assign it to me. Please include more details how to reproduce. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] gtk tooltip error in eclipse based application
Just filed a bug (#326059) about this problem. IDM Designer (Eclipse based) SIGSEGVs as soon as hoovering over tooltip enabled parts of the canvas. Stack: [0xf7d46000,0xf7d97000), sp=0xf7d954f0, free space=317k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) C [libgtk-x11-2.0.so.0+0x25a15a] gtk_tooltips_set_tip+0x20a C [libswt-pi-gtk-3232.so+0x382ce] Java_org_eclipse_swt_internal_gtk_OS__1gtk_1tooltips_1set_1tip+0x74 cheers, Juergen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Warning: Don't install kernel-flavour-2.6.22.5-21 from Factory
leads to panic on boot see https://bugzilla.novell.com/show_bug.cgi?id=326099 Hans-Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] classpath-webplugin
I have to agree with Andreas Vetter. Firefox/java/flash should simply work, without manual intervention, on any gui installation (even x86_64). In my opinion, the decision to go with only OSS solutions - even though they don't work right - is likely to push end-users toward other distributions. Can you name a distribution that has a working java on x86_64? perhaps we can check how they solved it. Greetings, Stephan Sorry. openSUSE is the only 64-bit o/s that I've tested so far. I've tried a few other 32-bit distros, but I've been reluctant to spend much time with them because we use Novell OES at work. I tried installing 64-bit NLD on my work PC, but had to back off because too many things didn't work (at that time). I apologize for complaining without sufficiently testing other distros. Gregg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Warning: Don't install kernel-flavour-2.6.22.5-21 from Factory
On Tue, 2007-09-18 at 19:27 +0200, Hans-Peter Holler wrote: leads to panic on boot see https://bugzilla.novell.com/show_bug.cgi?id=326099 Hans-Peter Yet one more reason to keep the old kernel around, especially when using factory. Any Novell people have a _valid_ reason not to keep the most resent kernel when upgrading? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] after 17-SEP broken update
Hi. After 17 september broken update, I have got a lot of duplicate packages. I removed manually all them (is there another way?), except grub due to following error: atlantis:~ # rpm -qv grub grub-0.97-79 grub-0.97-80 atlantis:~ # apt-get remove grub=0.97-79 Reading Package Lists... Done Building Dependency Tree... Done The following packages will be REMOVED: grub#0.97-79 0 upgraded, 0 newly installed, 1 removed and 165 not upgraded. Need to get 0B of archives. After unpacking 1421kB disk space will be freed. Do you want to continue? [Y/n] y Committing changes... Preparing...### [100%] sbin/install-info: symbol lookup error: sbin/install-info: undefined symbol: fzopen sbin/install-info: symbol lookup error: sbin/install-info: undefined symbol: fzopen error: %preun(grub-0.97-79.i586) scriptlet failed, exit status 127 Any idea to solve it? Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] classpath-webplugin
On Tue, Sep 18, 2007 at 6:32 PM, Martin Schlander [EMAIL PROTECTED] wrote: Den Tuesday 18 September 2007 16:27:22 skrev Gregg Nicholas: I reopened [Bug 264228] nspluginwrapper + java plugin problems [Bug 288750] Home bank issues with java+firefox on x86_64 to get a final decision. I know it's really late, but a 64bit system without a working firefox/java combination is a blocker in my eyes. I have to agree with Andreas Vetter. Firefox/java/flash should simply work, without manual intervention, on any gui installation (even x86_64). In my opinion, the decision to go with only OSS solutions - even though they don't work right - is likely to push end-users toward other distributions. As it can be seen from my bugreports that avetter reopened I share the opinion that 32-bit Firefox should be shipped. Especially since software.opensuse.org has no warning about downloading the x86_64 version. However I don't think the decision has anything to do with ideology. When people install x86_64 they don't want 32-bit Firefox - they want to run full 64-bit so they can enjoy all the imaginatory performance improvements. Now we even have 64-bit OOo.. Flash works with nspluginwrapper with 64-bit Firefox - I don't know how many people actually come across java webapplets - personally I only need it for homebanking - but that of course is enough to make me install 32-bit Firefox - which I tested and downgrading ran without incident, except for me having to remove classpath-webplugin - and that issue will be fixed. I agree completely: flash works flawless with the nspluginwrapper and Java is one of the things I never need on a website (even my bank webinterfaces don't use it anymore). Also think about other impacts having a 32bit firefox imposes: I'm maintaining packages of a not to be called by name Video Client, and we offer a plugin for Firefox. Of course, when installing 64bit Video Client, the 64bit plugin get's installed. Having a 32bit version of Firefox forces the user also to 'downgrade' a lot of other applications. I think such cases have to be clear for everybody: if you need Java and you really can't live without it, go for 32bit. Yast/whatever tool and the Documentation should offer an easy way for this. And then it should clearly be noted that many other things might get broken. For those users, a pure 32bit system might be better suitable then (or maybe a VM) Greetings, Dominique TMF is a global management and accounting outsourcing firm with 73 offices in 57 countries and over 2,000 professionals (2007). TMF is expanding rapidly throughout the world. Learn more about our unique network and our services and visit our website at www.tmf-group.com. The information contained in this e-mail communication is confidential and solely intended for the person to whom it is addressed. If someone other than the intended recipient should receive or come into possession of this e-mail communication, he/she will not be entitled to read, disseminate, disclose or duplicate it. If you are not the intended recipient, you are requested to notify the sender and to destroy the original e-mail communication. TMF is neither liable for the correct and complete transmission of the information contained in this e-mail communication nor for any delay in its receipt. This footnote also confirms that this email message has been checked for the presence of computer viruses. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] after 17-SEP broken update
* Miquel A. Noguera [EMAIL PROTECTED] [09-18-07 15:45]: After 17 september broken update, I have got a lot of duplicate packages. I removed manually all them (is there another way?), except grub due to following error: atlantis:~ # rpm -qv grub grub-0.97-79 grub-0.97-80 atlantis:~ # apt-get remove grub=0.97-79 rpm -e grub-0.97-79 -- Patrick Shanahan Plainfield, Indiana, USAHOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535@ http://counter.li.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] after 17-SEP broken update
On Tuesday 18 September 2007 15:42, Patrick Shanahan wrote: * Miquel A. Noguera [EMAIL PROTECTED] [09-18-07 15:45]: After 17 september broken update, I have got a lot of duplicate packages. I removed manually all them (is there another way?), except grub due to following error: atlantis:~ # rpm -qv grub grub-0.97-79 grub-0.97-80 atlantis:~ # apt-get remove grub=0.97-79 rpm -e grub-0.97-79 And if 'postun' script fails again than: rpm -e --noscripts grub-0.97-79 -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Yast2 printer
Hey Group; In Beta 2 Yast2 seems not to create and pre configuredvia Yast printer termcap correctly. I have to re run Yast2HardwarePrinter each time I need to use the printer. -- 73 de Donn Washburn 307 Savoy Street Email: [EMAIL PROTECTED] Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : [EMAIL PROTECTED] VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador http://counter.li.org #279316 Did you know? The transistor was invented by three white men. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Warning: Don't install kernel-flavour-2.6.22.5-21 from Factory
On Tuesday 18 September 2007 13:40, Kenneth Schneider wrote: On Tue, 2007-09-18 at 19:27 +0200, Hans-Peter Holler wrote: leads to panic on boot see https://bugzilla.novell.com/show_bug.cgi?id=326099 Hans-Peter Yet one more reason to keep the old kernel around, especially when using factory. Any Novell people have a _valid_ reason not to keep the most resent kernel when upgrading? The whole story is what we select: update or installation. Update to new version will remove old one, installation of new version will retain the old one. Though, YaST will always update. There is no way to select installation instead of update, which is safe bet with new users, and old ones will find the way around with rpm. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] graphics card on t61p can not be supported by opensuse 10.3
- Original Message - From: Juan Erbes [EMAIL PROTECTED] To: James Li [EMAIL PROTECTED] Cc: opensuse-factory@opensuse.org Sent: Tuesday, September 18, 2007 11:01 PM Subject: Re: [opensuse-factory] graphics card on t61p can not be supported by opensuse 10.3 2007/9/18, James Li [EMAIL PROTECTED]: I've installed nv driver and run sax2 -r -m 0=nvidia But the graphics card is recognized as Framebuffer vesa. lenove thinkpad t61p's graphics cards is nvidia quadro 740m. Your procedure was wrong. The nv driver, is the opensource driver, and You do'nt need to execute sax2 -r -m 0=nvidia, because this parameters for sax2 are for the propietary driver. The propietary driver appear in xorg.conf as nividia, and the opensource driver appear as nv. For installing the propietary driver, You can download it from: http://www.nvidia.com/object/unix.html You must has installed the kernel source, and must go to init 3, and executing the file with sh nvidia*.run as root. Later after completed the nvidia script, execute sax2 -r -m 0=nvidia Sorry for I don't say very clear. I just installed the nvidia driver from www.nvidia.com and run sh nvidia*.run . And the graphics card still recognized as Framebuffer vesa - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Yast2 printer
On Tuesday 18 September 2007 18:30, Donn Washburn wrote: Hey Group; In Beta 2 Yast2 seems not to create and pre configuredvia Yast printer termcap correctly. I have to re run Yast2HardwarePrinter each time I need to use the printer. Don, https://bugzilla.novell.com/buglist.cgi?query_format=advancedshort_desc_type=allwordssubstrshort_desc=long_desc_type=fulltextlong_desc=classification=openSUSEproduct=openSUSE+10.3component=Printingbug_file_loc_type=allwordssubstrbug_file_loc=status_whiteboard_type=allwordssubstrstatus_whiteboard=keywords_type=anywordskeywords=bug_status=NEWbug_status=ASSIGNEDbug_status=NEEDINFObug_status=REOPENEDemailassigned_to1=1emailtype1=substringemail1=emailassigned_to2=1emailreporter2=1emailqa_contact2=1emailcc2=1emailtype2=substringemail2=bugidtype=includebug_id=votes=chfieldfrom=chfieldto=Nowchfieldvalue=cmdtype=doitorder=Reuse+same+sort+as+last+timefield0-0-0=nooptype0-0-0=noopvalue0-0-0= I have no time to look trough list right now. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] classpath-webplugin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stephan Kulow wrote: Easing the update path in adding conflicts is very fine with me though. This should be reported though. Why not to use alternatives instead? One could chose which plug-in one wants using update-alternatives. Cheers Fridrich -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFG8HUNu9a1imXPdA8RApmnAJ4jMu/o0EfvFpgXdNtj+OO02frCvQCfSryy sHFAgqfod1q/jr9IoCc1jUg= =BO1D -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Warning: Don't install kernel-flavour-2.6.22.5-21 from Factory
On Tue, 2007-09-18 at 18:44 -0500, Rajko M. wrote: On Tuesday 18 September 2007 13:40, Kenneth Schneider wrote: On Tue, 2007-09-18 at 19:27 +0200, Hans-Peter Holler wrote: leads to panic on boot see https://bugzilla.novell.com/show_bug.cgi?id=326099 Hans-Peter Yet one more reason to keep the old kernel around, especially when using factory. Any Novell people have a _valid_ reason not to keep the most recent kernel when upgrading? The whole story is what we select: update or installation. Update to new version will remove old one, installation of new version will retain the old one. Though, YaST will always update. There is no way to select installation instead of update, which is safe bet with new users, and old ones will find the way around with rpm. I would agree with that if it were the GM release _not_ the alpha/beta releases which people are trying to test. We should have a way to keep the old kernel _even in an upgrade_ when testing and as you pointed out YaST will always update. I can imagine how many people got stung by this one. Fortunately for me I use my laptop for testing and I only lost a couple of hours reverting back to the install kernel. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Warning: Don't install kernel-flavour-2.6.22.5-21 from Factory
On Tuesday 18 September 2007 19:05, Kenneth Schneider wrote: We should have a way to keep the old kernel _even in an upgrade_ when testing Agree. It is all in post install script. I didn't looked in details how it works, only the part that I had problem with - not creating initrd in some cases. I know that installation (make install) after compilation from sources leaves old kernel, but is that the same script I would have to find out. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] kradio compile
Hey Group; Trying to compile kradio for my old Hauppauge Model 401 card using the required unsermake it came across this error. It seem to be due to to many .. Also I notice Beta 2 has 2.95.3 and 4.2.1 compilers Why? /usar/bin/g++ goes to 4.2.1 Which item has the error? Does anyone see an easy way to beat the .. problem By the way SuSE is having it's Houston Forum on Thursday. Same place as last year. If you are going let me know direct. -- 73 de Donn Washburn 307 Savoy Street Email: [EMAIL PROTECTED] Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : [EMAIL PROTECTED] VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador http://counter.li.org #279316 Did you know? The transistor was invented by three white men. g++-4.2: /usr/lib/gcc/i586-suse-linux/4.1.2/../../../crti.o: No such file or directory g++-4.2: /usr/lib/gcc/i586-suse-linux/4.1.2/crtbeginS.o: No such file or directory g++-4.2: /usr/lib/gcc/i586-suse-linux/4.1.2/crtendS.o: No such file or directory g++-4.2: /usr/lib/gcc/i586-suse-linux/4.1.2/../../../crtn.o: No such file or directory Error creating ./kradio3/plugins/gui-docking-menu/libdocking-menu.la. Exit status 1. locate crti.o /usr/lib/crti.o
