Re: [opensuse-factory] broken mirrors again?
On Sunday 27 January 2008 02:27:08 am Viljo Mustonen wrote: > Magnus Boman kirjoitti: ... > > Yeah, there are no issues upgrading an existing install if you already > > had the repos registered. The issue is when you want do a new install. > > Well, I am trying just new install. Have you tried to manually point installer to: ftp://ftp5.gwdg.de/pub/opensuse/distribution/SL-OSS-factory/inst-source/ I had issues with signature on latest updates where all sources were http://download.opensuse.org/.. When I switched to above mirror, installation went without glitches. -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Installing from opensuse factory
On Friday 25 January 2008 06:24:19 am M9. wrote: > Rajko M. schreef: > > On Wednesday 23 January 2008 11:48:24 am Viljo Mustonen wrote: > >> Hi > >> > >> > >> from URL > >> 'http://download.opensuse.org/distribution/SL-OSS.factory/inst-sorce' > >> > >> > >> > >> Do I something wrong or is there error in repository ? > > > >'sorce' does not exis: read: 'source', ;-) The moral of the story is that one has to read after first error and before cut'n'paste ... and that Viljo needs someone that actually downloaded and used miniiso ;-) -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Installing from opensuse factory
On Wednesday 23 January 2008 02:11:54 pm Viljo Mustonen wrote: > Rajko M. kirjoitti: > > On Wednesday 23 January 2008 11:48:24 am Viljo Mustonen wrote: ... > >> Do I something wrong or is there error in repository ? > > > > SL-OSS-factory > > SL-OSS.factory > > > > Compare URLs. > > The message tells that there is no repository on given URL, which means > > either wrong URL or missing repodata. > > Boot disk's default http URL should be correct: > http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/ > > I have typos in previous error messages. Correct URL in error messages is: > > Unable to create repository > from URL > 'http://download.opensuse.org/distribution/SL-OSS-factory/inst-source' > > It seems also correct. So, missing or invalid repodata? But why I get > working rescue system? Rescue system should be located on mini iso CD. When using Factory you should have in mind that it is system with minimal testing before it goes online, so there are possible all kind of errors. What I do is to try later, few hours or a day, and if it doesn't work again than ask this list. I had no time to download mini iso my self and check details. Hopefull,y someone that did can tell more. -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Installing from opensuse factory
On Wednesday 23 January 2008 11:48:24 am Viljo Mustonen wrote: > Hi > > I have down loaded many times/days > > http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/boot/b >ootdisk > > With it I can download and boot rescue system. If I start install I get > error dialog > at "System Probing / Initialize package manager" stage. The dialog > says: > > Unable to create repository > from URL > 'http://download.opensuse.org/distribution/SL-OSS.factory/inst-sorce' > > Details: > Valid metadata root not fount at specified URL(s) > History > - File /var/cahe/zypt/raw/openSUSE-FACTORY 11.0ZiwCQi/content.key > doesn't public key data > > Try again? > > Do I something wrong or is there error in repository ? SL-OSS-factory SL-OSS.factory Compare URLs. The message tells that there is no repository on given URL, which means either wrong URL or missing repodata. -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] beagle
On Thursday 17 January 2008 02:37:40 pm Christian Jäger wrote: > It is perfectly normal that an indexing tool is especially active when > building an initial index. Whoever doesn't have the patience to wait > this out and instead uninstalls Beagle instantly cannot really say > anything about its footprint or usefulness IMHO. > > Apple users, for example, just _know_ that their search-tool (Sherlock > or whatever it's called) put quite a load on in the beginning. > > I think removing Beagle would mean a serious regression. Someone that knows about search tools and required properties should create benchmarks or anything like that. We had almost endless discussion in [EMAIL PROTECTED] with bunch of opinions, and even google search results that should confirm that beagle is nasty resource hog. That contradicts my experience, but except taking under loop google results, where it showed mix of obsolete articles and opinions, I had no much tools to prove my point that beagle is not a problem, at least not in that many cases. I can agree that Beagle is development version, with bugs that can make it chase its tail, but I really can't see, in last couple of months, that it hogs resources. I had literally no 99% CPU usage where beagle would be the culprit, so I can't confirm any claim that tells so. What is needed is some comparative study, with numbers that will describe real situation. -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] How to rebuild database when: SQL logic error or missing database ?
On Sunday 06 January 2008 07:38:11 am M9. wrote: > M9. schreef: > > Hi, > > > > After a system hung, i had to reboot, cold, with button, because no > > reaction whatsoever. > > The hung occurred during a repo refresh. > > > > Now the 'openSUSE-debuginfo-FTP 11.0' cannot be rebuild or refreshed. > > > > I think remove the repo, and install it again, should do the trick? > > No it does not work this way: > > Can not save the changes in the configuration of the installation source. > Details: Record not found in the cache history: > -SQL logic error or missing database > > What was possible though was shut it off, and switch on a brother (other > mirror), which i did. The easiest way to rebuild zypper database is to: - delete /var/cache/zypp/zypp.db and - run 'zypper refresh' to create new one -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Is it possible to completely do without Gnome?
On Thursday 03 January 2008 02:43:27 am Andreas Jaeger wrote: > "Rajko M." <[EMAIL PROTECTED]> writes: > > Let me jump in, as I had the same problem. > > I don't use GNOME, but I guess that I have almost all installed. I > > laughed when Metacity and evolution data server were listed as > > dependency, but I had no time to play with, so I just let zypper install > > everything. I can't recall what pulled them in, but I'll try to see is > > there anything in zypper log. > > It would be interesting to see which packages exactly pull those - or > others in. Please check the specifics, > > Andreas I'm trying to locate log file that may contain recent problem, but it is probably the same as this one: http://lists.opensuse.org/archive/opensuse-factory/2007-09/msg00630.html That above was on 64 bit installation (a guess), and this is 32 bit. -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Is it possible to completely do without Gnome?
On Wednesday 02 January 2008 03:40:44 am Andreas Jaeger wrote: > "M9." <[EMAIL PROTECTED]> writes: > > Hi, > > > > I upgraded all pkgs manualy choosen.. > > When trying to get rid of gnome, this was impossible... > > Very anoying, to have to install pkgs and apps to your system, you never > > use, just to fullfill deps. > > Which packages exactly are on your system that you want to get rid of? > > > Is there a way to check which gnome specific pkgs are realy needed to > > run suse? > > I am satisfied with KDE and if xfce is dependable on gnome, i will get > > rid of it also. > > > > I want to run a 'gnomeclean' KDE environment. > > Is this possible? > > (strange that these have to be mixed to function anyway.) > > > > This way i am forced to 'check' gnome also, which i do not want. > > You should not need to check the GNOME pattern at all > > > It is silly, that it is not possible to update a system, due to an > > invalid DE, one not wants to use, don't you agree? > > There are packages like flashplayer, acrobat reader and gimp that use > the gtk libraries - are you speaking about these? Or what is your > problem? A lot of libraries are kind of system libraries, you cannot > get rid of them, > > Andreas Let me jump in, as I had the same problem. I don't use GNOME, but I guess that I have almost all installed. I laughed when Metacity and evolution data server were listed as dependency, but I had no time to play with, so I just let zypper install everything. I can't recall what pulled them in, but I'll try to see is there anything in zypper log. Last time it happened with Beagle, some time ago. Joe Shaw was puzzled as Beagle has no so many dependencies. That time I had time to play and remove all that wasn't direct dependency. Though it is install all then remove those that are not listed as direct dependency. -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Splitting manpages out of package is *fundamentally* wrong
On Monday 31 December 2007 10:24:35 am James Tremblay wrote: > P.S. not one of these tools comes with an on board manual, that is what > training and research are for. That's the right point James. It is time to rethink about tradition to have manuals as a part of package. I need manuals to learn how to use tools (I missed many lectures), but I know that I use very small portion of installed software. The rest is used by other guys in my "shop", those that created scripts, and they don't need manuals. So, what would be the best option if I want to have small, slick collection of software, but manuals available if want them. I guess separate collection of manuals, and package manager that will install them on request. -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Update channel for patches or broken pkgs?
On Sunday 30 December 2007 06:02:41 am M9. wrote: > Rajko M. schreef: [...] > > Try to use > > zypper se yast2 > > than > > zypper up -t package > > The list is manually created with paste and copy from first list. > > Exactly so does not work, but, when 'se' the list, i found out that many > packages were not updated. (if a V in front of the pkg, means: update > available, if not, these pkgs were not present.) > Anyway: the command you suggested had too many arguments, but > 'sudo zypper in ... did the trick, eventualy. [...] Right, the zypper up -t package takes only options, no wanted file names, but you found right command, suggested in 'man zypper'. zypper in I do what I wrote often and when 'zypper up' complains than I change 'up' to 'in' and get what I want installed. -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Update channel for patches or broken pkgs?
On Saturday 29 December 2007 06:32:04 am M9. wrote: > Hi, > > It might sound stupid and... > Maybe i am mistaken, or dreamed it, but was there not an url for to > update broken factory pkgs? > If there was or is such a 'channel',or url, would the one who knows the > adress please put it in this list? > > The reason i ask this, is to be able to repair broken apps, like Yast or > smart. > Some pkgs where these depend on are broken, and thus unuseable... > The Factory is strange repository. It is like end of assembly line, before inspection, in real manufacturing plant ie. factory. It doesn't need repair repository. You as a inspector just drop bad assembly, write findings in the bugzilla, or this list, and take another piece that is comming. Try to use zypper se yast2 than zypper up -t package The list is manually created with paste and copy from first list. -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Splitting manpages out of package is *fundamentally* wrong
On Thursday 27 December 2007 07:22:13 pm Joerg Mayer wrote: > On Thu, Dec 27, 2007 at 06:29:36PM -0600, Rajko M. wrote: > > > While it may in may cases be OK to not include additional documentation > > > in the base package, the manpages need to stay there - no matter what > > > that means for the build process. > > > > So far I recall there was idea to remove documents from main package, to > > make base package and whole base distro slimmer, easier to put on CD, > > Live CD etc. The above excerpt is something new to me. > > Removing manpages is a broken concept: They are needed to actually use > the programs. Additional documentation may well be moved into another > package, but not manpages. That's similar to removing the --help part > from the binaries to make them smaller. ... I can understand that, as I am heavy user of man pages, but there was a pressure to make distro smaller. What was behind wasn't explained, but the goal was set to 128 MB for the very base system and AJ email appeared to be very serious. BTW, for guys that know how to use man pages installation of extra package is a bit more work, but far from a problem ;-) -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Splitting manpages out of package is *fundamentally* wrong
On Wednesday 26 December 2007 12:00:10 pm Joerg Mayer wrote: > Hi, > > I'd just discuss something that I got hit with: > The PolicyKit package no longer contains the manpages - if you want them > you need to install PolicyKit-doc as well. > IMO, this is a *relly* *really* ... *really* wrong decision, which was > obviously made because of *build* reasons: > > * Sat Aug 11 2007 [EMAIL PROTECTED] > - Make separate spec file for PolicyKit-doc so that PolicyKit does > not require TeX for building. > > While it may in may cases be OK to not include additional documentation > in the base package, the manpages need to stay there - no matter what > that means for the build process. > > ciao > Joerg Hi Joerg, So far I recall there was idea to remove documents from main package, to make base package and whole base distro slimmer, easier to put on CD, Live CD etc. The above excerpt is something new to me. -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Missing deps..20/12/07
On Thursday 20 December 2007 07:43:17 am M9. wrote: > My queston: should zypper not uninstall the allready installed (older) > version(s) first, and than install the newer version(s), or am i wrong > here? You don't want that. https://bugzilla.novell.com/show_bug.cgi?id=301676 -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] new live cd 2.5
On Monday 17 December 2007 11:22:48 pm Rajko M. wrote: > On Monday 17 December 2007 10:45:09 pm Rajko M. wrote: ... > > Installation worked perfectly, and network worked fast, When I said perfectly, I mean it. It was so simple, anyone can do it. Click button to start installation, wait until you see message that files are copied, reboot, remove CD, create root password, create user and password, download updates, done. Though, it was virtual machine and empty virtual hard disk, but this kind of installation should be set as a goal. Though, it should provide 'Advanced setup' button/installation option, for those that need to tweak settings. Now, when I have running system, I can add whatever software I like. Thanks Stephan. -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] new live cd 2.5
On Monday 17 December 2007 10:45:09 pm Rajko M. wrote: > On Monday 17 December 2007 09:45:04 pm Rajko M. wrote: > ... > > > BTW, it works fine in VirtualBox. > > Network was instantly available. > > It seems to boot much faster than some previous versions. > > Installation worked perfectly, and network worked fast, > but than popped up window about new discovered hardware - network card and > question would I like to configure it. > > Yes I would, give root password, and I have forgotten that first popped up window saying that another program is using software management. Hmm ... who would be that? Ah, yes. Software updater was running. I finished updates and went back to network device dialog, told to retry and than got network device configuration. This is for sure not obvious for first time users. > get network device configuration > window. Simple press 'Next' replaced working routing table with one that > had only loopback device, and network was shut down. > > Additional 'rcnetwork restart' did nothing (as expected), and network was > still down. > > Back to network devices, set default gateway and press 'Next' solved > problem. > > IMHO, default gateway should be found by running dhcpcd, so it was not > necessary to set anything in network device configuration. -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] new live cd 2.5
On Monday 17 December 2007 09:45:04 pm Rajko M. wrote: ... > BTW, it works fine in VirtualBox. > Network was instantly available. > It seems to boot much faster than some previous versions. Installation worked perfectly, and network worked fast, but than popped up window about new discovered hardware - network card and question would I like to configure it. Yes I would, give root password, and get network device configuration window. Simple press 'Next' replaced working routing table with one that had only loopback device, and network was shut down. Additional 'rcnetwork restart' did nothing (as expected), and network was still down. Back to network devices, set default gateway and press 'Next' solved problem. IMHO, default gateway should be found by running dhcpcd, so it was not necessary to set anything in network device configuration. -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] yast2 qt frontend broken on x86_64
On Monday 17 December 2007 02:25:19 pm Markus Koßmann wrote: > If I start yast2 it doesn't start it's qt frontend: > > libpy2wfm.so.2 => not found > warning: the qt frontend is installed but does not work > Qt GUI wanted but not found, falling back to ncurses. > > But libpy2wfm.so.2 exists in /usr/lib64/YaST2/plugin an is a link to > /usr/lib64/YaST2/plugin/libpy2wfm.so.2.0.0 The same here with update from Alpha0 to Factory using Factory update module, This is 32 bit running in VirtualBox. -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] new live cd 2.5
On Monday 17 December 2007 03:12:26 am Stephan Kulow wrote: > Am Sonntag 16 Dezember 2007 schrieb Ted Bullock: > > Stephan Kulow wrote: > > > Hi! > > > > > > I updated the live CDs again to fix the remaining X config problem, > > > so if you want to try it - grab 2.5 of either gnome or kde from > > > ftp://beta.suse.com/private/10.3-livecd > > > > > > If no-one got a new problem, I'll push it on download tomorrow > > > > > > Greetings, Stephan > > > > Sorry, is this going to be pushed out to replace the version listed at > > http://software.opensuse.org/ or just on the above beta link. > > I got very little feedback and the feedback I got was: still has the same > problems booting even with the work around added. So as this got so little > interest, I kind of thought that it's no longer worth my time. > > The original idea though was to push it on software, yes. The problem can be the factory list. BTW, it works fine in VirtualBox. Network was instantly available. It seems to boot much faster than some previous versions. -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] factory kernel-default-2.6.24_rc5_git2-2.i586.rpm
Hi, http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/i586/ kernel-default-2.6.24_rc5_git2-2.i586.rpm used in factory installation in VirtualBox (latest) can start only with acpi=off, but then system timer runs very fast. Old kernel is, as usually, removed. Booting in runlevel 3 and changing clock source from pit to tsc seems to be work. I guess it is a time to reload Alpha0 and start again. -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] How to add /home/RPM/ to the rpm database?
On Sunday 09 December 2007 01:56:01 pm M9. wrote: > How to specify such a directory than? > I do not mind to move the rpm's to another directory, or change the > name... but this is not very obvious, if you ask me? From man: SYNOPSIS createrepo [options] When you are in /home/monkey9/RPM: createrepo ./ will create directory /home/monkey9/RPM/repodata/ and files filelists.xml.gz other.xml.gz primary.xml.gz repomd.xml -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] How to add /home/RPM/ to the rpm database?
On Sunday 09 December 2007 01:33:37 pm M9. wrote: > I presume the 2th defciency will be corrected? > Not that it matters to me to do things more than nessesary, but just to > know that progression will happen. https://bugzilla.novell.com/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=fulltext&long_desc=&classification=openSUSE&product=openSUSE+10.3&component=YaST2&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=anywords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&bug_severity=Enhancement&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= There is the list of all Enhancement requests ever made for YaST2. I remember that adding local repos without hassle to use createrepo manually was one discussed quite some time ago, but it seems to be forgotten. The bad is that it was an option before, and it worked with no problems. -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] How to add /home/RPM/ to the rpm database?
On Sunday 09 December 2007 07:59:30 am M9. wrote: > Hi, > > Is there a reason that a /home/dir can not be added to the install sources? > Than there should be a workaround, which is:? I'm a bit late with answer. It was written an hour ago, before lunch, but it adds more info, so here it is: /home/RPM/ can be added, but it has to contain metadata about packages. The way I use is to run program 'createrepo' in that directory which will create subdirectory 'repodata' and than add /home/RPM/ to package sources. With this procedure YaST etc, will complain that packages are not signed, but you can tell to use them anyway. Second deficiency of this method is that you have to run 'createrepo' on every change otherwise YaST or 'zypper refresh' will not find any changes you made, ie. will not find new packages or complain about missing packages. -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Two separate bug numbers, same problem?
On Sunday 09 December 2007 03:53:28 am Vahis wrote: > In 10.3 I have this message repeatedly: > > PAM audit_log_acct_message() failed: Operation not permitted > > It seems to be bug #334559 > > I found another one in bugzilla , bug #331683 > > I don't have this one because I don't have that application on that > machine. > > The first one is said to be "assigned" and the second one "new" > > They both obviously are about PAM > > I don't know if posting my findings here help in any way, though... Adding your findings in bugzilla reports and/or voting for bug can help to have that fixed earlier. -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Help Wanted: Move YaST tutorials from forgeftp.novell.com to openSUSE WIKI
On Tuesday 04 December 2007 03:28:23 pm J. Daniel Schmidt wrote: > > > don't !! looks like making several subpages levels is not that good > > > (see other thread) > > Which thread are you referring to? In opensuse-wiki: http://lists.opensuse.org/opensuse-wiki/2007-12/msg1.html One of ideas is to reduce usage of subpages. Please see if you can come up with some idea(s). -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Help Wanted: Move YaST tutorials from forgeftp.novell.com to openSUSE WIKI
On Monday 03 December 2007 01:37:08 pm jdd wrote: > J. Daniel Schmidt wrote: > > On Saturday 01 December 2007, jdd wrote: > >>> and also WIKI page for every single YaST module: > >>> http://en.opensuse.org/YaST/Modules > >>> > >>> Your example (YaST Printer): > >>> http://en.opensuse.org/YaST_Printer > >> > >> for example, why is not the printer page under > >> YaST/modules/printer??? > > > > Not yet moved there. But YaST/Modules/Printer is definitely the correct > > location. > > In my reorganisation of the YaST-pages I did not touch these sites. But > > as it is a wiki everybody is invited to help :) > > don't !! looks like making several subpages levels is not that good > (see other thread) > > and this was just an example Done. You can see wiki: recent changes. Daniel made quite some effort to bring all related pages presented in the same way. That it gives some of us headache is another question. We have to establish new guidelines, so that at least frequent editors do all in the same way. Wiki is no more little pet that can be moved around at will, and it is still growing, thanks to guys like Daniel that are not afraid of work. -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Xgl/Compiz 11.0 Notes (DRAFT)
On Monday 26 November 2007 07:07:18 pm Benji Weber wrote: > On 27/11/2007, Juan Erbes <[EMAIL PROTECTED]> wrote: > > 3- The option "1-Click-uninstall" to remove easy xgl/aiglx from the > > system. > > It is possible to make YMPs which will uninstall packages, but one can > just as easily use yast -> software management. They're primarily > useful for installing packages from repositories the user's package > management may not be aware of. IMHO, "1-Click-uninstall" is just as important. It is more work trough YaST under condition that user knows what was installed, and for majority of "1-Click-Install" users that is not the case. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] YaST (or KDE4) problem [SOLVED]
On Monday 12 November 2007 03:44:23 am Stephan Kulow wrote: > Am Montag 12 November 2007 schrieb Rajko M.: > > On Friday 26 October 2007 01:02:42 pm Rajko M. wrote: > > > Tried to update KDE4 to newest and got dependency problem that seems to > > > be software management problem (or KDE4 packaging): > > > > > > Message 1 (there is another 2 about libkdefx.so.5()(64bit) ) > > > -- > > > Can't satisfy requirement libkdefx.so.5()(64bit) > > > for kde4-fsview-3.93.0.svn712059-13.x86_64 > > > > > > === kde4-fsview-3.93.0.svn712059-13.x86_64 === > > > libkde4-3.93.0.svn712047-5.x86_64 > > > provides > > > libkdefx.so.5()(64bit), > > > but is scheduled to be uninstalled. > > > > > > libkde4-3.93.0.svn712047-5.x86_64[repo-standard] > > > provides > > > libkdefx.so.5()(64bit), > > > but another version of that package is already installed. > > > > > > kde4-fsview-3.93.0.svn712059-13.x86_64 > > > depends on libkde4 > > > kde4-fsview-3.93.0.svn712059-13.x86_64 > > > is lacking the requirement libkdefx.so.5()(64bit) > > > (null) > > > Conflict Resolution: > > > ( ) delete kde4-ksig > > > ( ) Ignore this requirement just here > > > ( ) Generally ignore this requirement > > > Can't satisfy requirement libkdefx.so.5()(64bit) for > > > kdeaddons4-konqueror-3.93.0.svn712059-13.x86_64 > > > -- > > > > > > This resembles on some old libzypp bug. I can't recall right now which > > > one and got no time to investigate. > > > > It is a Software Management bug. > > In such cases, make sure to do a zypper up --debug-solver and > save /var/log/zypper.testcase (typos in the file name aside) as tar. Hi Stephan, this was YaST and all that is saved is in this mail and y2logs. I have to try to reproduce it first, on fresh installation (one of this days). -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] YaST (or KDE4) problem [SOLVED]
On Friday 26 October 2007 01:02:42 pm Rajko M. wrote: > Tried to update KDE4 to newest and got dependency problem that seems to be > software management problem (or KDE4 packaging): > > Message 1 (there is another 2 about libkdefx.so.5()(64bit) ) > -- > Can't satisfy requirement libkdefx.so.5()(64bit) > for kde4-fsview-3.93.0.svn712059-13.x86_64 > > === kde4-fsview-3.93.0.svn712059-13.x86_64 === > libkde4-3.93.0.svn712047-5.x86_64 > provides > libkdefx.so.5()(64bit), > but is scheduled to be uninstalled. > > libkde4-3.93.0.svn712047-5.x86_64[repo-standard] > provides > libkdefx.so.5()(64bit), > but another version of that package is already installed. > > kde4-fsview-3.93.0.svn712059-13.x86_64 > depends on libkde4 > kde4-fsview-3.93.0.svn712059-13.x86_64 > is lacking the requirement libkdefx.so.5()(64bit) > (null) > Conflict Resolution: > ( ) delete kde4-ksig > ( ) Ignore this requirement just here > ( ) Generally ignore this requirement > Can't satisfy requirement libkdefx.so.5()(64bit) for > kdeaddons4-konqueror-3.93.0.svn712059-13.x86_64 > -- > > This resembles on some old libzypp bug. I can't recall right now which one > and got no time to investigate. It is a Software Management bug. There was installed libkde4-32bit and that is the one in 'another version of that package is already installed' message. Marking manually libkde4-32bit for removal solved problem. Though, looking for solution I think that I stumbled over one bug old as Troy. In first attempt I just locked libkde4 to prevent removal, and dependency problem disappeared, so I installed what was possible to install and then came back to unlock libkde4, but lock disappeared. Locking package was not persisten in the same sw_single session. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Discussing problems with 10.3
On Friday 09 November 2007 09:49:44 pm Volker Kuhlmann wrote: > Which list is meant for discussing problems with 10.3? opensuse@ is not > the answer, and I've been told off several times here. Now it is. Before 10.3 was development version and that is opensuse-factory mail list, now it is released and it is opensuse mail list. Whoever tell different should read descriptions on http://lists.opensuse.org -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: bug 234533 should be solved?
On Tuesday 06 November 2007 01:05:10 pm jdd wrote: > jdd wrote: > > I'm hit by the bug #234533. It's resolved "wont fix" "because it's a > > feature, not a bug" > > > > but > > > > 1) it's a bug only on pci-e (here mini pci, laptop), why this special > > hardware hve such a feature? > > 2) the comment on bugzilla say: the patch will be enclosed with 2.6.20 > > kernel. I have 2.6.22.9.0-4-default and I have still the bug > > 3) a web search shows that ndiswraper don't works reliably with the > > bcm43xx module > > > > what can I do? do i need to reopen the bug or to try using ndiswraper > > anyway? > > > > thanks > > jdd > > solved thanks to an ubuntu forum :-). > > I had to extract the firmware and give it to the module. I still have > to figure how to make this permanent, but i wont too much be a > problem. I will test and report to the wiki (may be just adding > indexes, I didn't find it there but it may be :-) > > I wil also report to bugzilla > > thanks http://en.opensuse.org/SDB:Broadcom_%28BCM4306%29_WLAN_Installation_under_SUSE section 'openSUSE 10.2 Option 1 - Original Driver Procedure'. You can use wl_apsta.o or original bcmwl5 or whatever you can find in windows. It works here, with a small glitch(es) that I still didn't solved, but with time ... -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] YaST (or KDE4) problem
Tried to update KDE4 to newest and got dependency problem that seems to be software management problem (or KDE4 packaging): Message 1 (there is another 2 about libkdefx.so.5()(64bit) ) -- Can't satisfy requirement libkdefx.so.5()(64bit) for kde4-fsview-3.93.0.svn712059-13.x86_64 === kde4-fsview-3.93.0.svn712059-13.x86_64 === libkde4-3.93.0.svn712047-5.x86_64 provides libkdefx.so.5()(64bit), but is scheduled to be uninstalled. libkde4-3.93.0.svn712047-5.x86_64[repo-standard] provides libkdefx.so.5()(64bit), but another version of that package is already installed. kde4-fsview-3.93.0.svn712059-13.x86_64 depends on libkde4 kde4-fsview-3.93.0.svn712059-13.x86_64 is lacking the requirement libkdefx.so.5()(64bit) (null) Conflict Resolution: ( ) delete kde4-ksig ( ) Ignore this requirement just here ( ) Generally ignore this requirement Can't satisfy requirement libkdefx.so.5()(64bit) for kdeaddons4-konqueror-3.93.0.svn712059-13.x86_64 -- This resembles on some old libzypp bug. I can't recall right now which one and got no time to investigate. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Both 10.2 and 10.3 invalid now.
On Wednesday 17 October 2007 08:36:17 am Monkey 9 wrote: > Robison, Jonathon (M.) schreef: > >On Wed, 2007-10-17 at 12:22 +0200, Monkey 9 wrote: > >>Hi, > >> > >>x-server update on 10.3 this morning, made the os unuseable, the same > >>goes for the kernel-update on 10.2, misplaced entrances in the > >>bootloader made the os impossible to boot. > >>Now both my SuSE's are down :-( > >>How to fix them if not able to enter either of them? > > > >Rescue CD or LiveCD or even Knoppix, mount the root drive, edit and > >fix /boot/grub/menu.lst ??? > > > >--Jonathon M. Robison > > Offcourse, thnx ;-), i did not think about that yet, but i did that > before... It is just that i was a little mad, because the same thing > happened a while ago few times, and i realy thought we would be over > this... Why change things that are fixed back to broken again? > These kind of things test my patience in a negative way. > I do not understand that invalid or untested pkgs are suggested as updates? M9, sorry to interrupt you, but 10.3 is now released ;-) It belongs to [EMAIL PROTECTED] mail list. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Looking outside the box
On Wednesday 17 October 2007 09:52:33 am Sid Boyce wrote: > I must have a good look at the opeSUSE wiki, I'm > sure there is noteworthy stuff that describes HOWTO on openSUSE, This will be good. If we would put so much time writing on wiki, as we use on mail lists the openSUSE wiki will be cited as reference on Linux, not only as good documented distro. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] A Zypper question
On Friday 12 October 2007 09:29:45 am Robert Lewis wrote: > On 10/12/07, Stanislav Visnovsky <[EMAIL PROTECTED]> wrote: > > Dňa Friday 12 October 2007 14:39:40 Igor Jagec ste napísal: > > > I don't know which features for Zypper you plan to develop, so I'd like > > > to ask for one. Do you have any plans to include a feature which would > > > install a set of local rpm files? > > > > > > Smart can handle situations like this: > > > > > > # smart install foo.rpm > > > > > > Yum also > > > > > > #yum localinstall foo.rpm > > > > > > I'm not sure what features you plan to implement, so I'm just asking :) > > > > On the radar... > > > > A workaround exists in the meantime: create a temp dir, put the packag > > there, add the repo as PlainDir and install. > > > > Stano > > I must be missing something in this discussion. Word 'zypper' ;-) > I just use Konqueror file manager and go find the RPM in any directory. > Then right click and then Open With i-> install software. Though there is more then on way around. For instance I put rpm files in directory, than run createrepo and add that to list of repositories. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] [status report] openSUSE distribution, week 41
On Tuesday 09 October 2007 10:33:15 am Sid Boyce wrote: > Stephan Kulow wrote: > > Hi! > > > > There is little to report status on this time, beside this: > > > > * WE'VE PUBLISHED OPENSUSE 10.3 - and it looks like a > > success all in all ( > > * Of course we've seen plenty of bugs that users report > > (they always do that :) > > * We released already quite some online updates and testing > > some more > > * We're still preparing promo DVD / live CDs - looking pretty > > good already > > * Oh, we've seen release parties at different locations. Thanks > > to everyone organizing > > > > Greetings, Stephan > > It's a pity that most reviewers do not follow this list or check the > archives. I've seen one review on linuxtoday, plus the comments where > 10.3 is being slated for not having a livecd. > Their methodology is download, install, boot up, try a few things, then > write an article with criticsms, get it published and say job done. > You'll not see any follow-ups. > http://abhay-techzone.blogspot.com/2007/10/why-suse-why.html > Regards > Sid. With this particular I have seen quite a few answers from 'abhay'. Simple click trough will always make some people happy, some not. He listed few distros as examples, and that are examples make good choice in his opinion (and he repeated that later in answers). Some other people on the other end of user sectrum will complain on openSUSE way and list Gentoo and Slackware as right choices. For me (so unbiased), openSUSE is the optimum between complexity and simplicity. However, as 10.3 is not ultimate edition we still have a chance to make it better ;-) -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: Incomplete suseboot directory in 10.3?
On Monday 08 October 2007 01:12:58 pm Manfred Tremmel wrote: > Am Sonntag, 7. Oktober 2007 schrieb Rajko M.: > > What is the reason not to use: > > ftp://ftp5.gwdg.de/pub/opensuse/distribution/10.3/repo/oss/suse/ppc > > install-initrd-1.0-228.ppc.rpm > > kernel-default-2.6.22.5-31.ppc.rpm > > > > It seems from the openSUSE article that it doesn't matter which > > initrd and kernel are used. > > Sorry, doesn't work, too. I can boot using BootX and I get a menu to > select installation properties, but there is no network and no access > to the cd drive and I can't load any modules. > So it's not easy to install... Than you have 2 ways left. Use 10.2 to install openSUSE and then you can upgrade, or install as dual boot, or create your own initrd that will include network and CD drivers. Maybe you can get some ideas using: http://en.opensuse.org/Portal/OpenSUSE_Installation -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: Incomplete suseboot directory in 10.3?
On Sunday 07 October 2007 10:59:31 am Manfred Tremmel wrote: > I see, I have to invest more time in betatesting next time and not only > in VirtualBox. The VirtualBox is kind of ideal world. All hardware is the same. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: Incomplete suseboot directory in 10.3?
On Saturday 06 October 2007 16:05, Manfred Tremmel wrote: > Am Samstag, 6. Oktober 2007 21:39 schrieb Rajko M.: > > I found both in factory oss repository in large mini iso that was all > > in one. Now it is split into ppc and x86 part. > > > > http://download.opensuse.org/distribution/10.3/iso/cd/openSUSE-10.3-G > >M-ppc-mini.iso Here is yaboot.txt in above mini iso: > > Welcome to openSuSE 10.3 (PPC)! > > > > Type "install" to start the YaST installer on this CD/DVD > > Type "slp" to start the YaST install via network > > Type "rescue" to start the rescue system on this CD/DVD > > > > It seems that all you need is this mini iso. > > No chance! It's a "Old World" Powerbook, yaboot can't be used for it. I > have to use BootX and can't start from the CD. And BootX needs > > See: > http://en.opensuse.org/Booting_on_PowerMac_(OldWorld) > > At the moment I've installed Debian, but I would like to use the > PowerBook to build my Packman-Packages also for PPC, so I would need to > have a SUSE running. What is the reason not to use: ftp://ftp5.gwdg.de/pub/opensuse/distribution/10.3/repo/oss/suse/ppc install-initrd-1.0-228.ppc.rpm kernel-default-2.6.22.5-31.ppc.rpm It seems from the openSUSE article that it doesn't matter which initrd and kernel are used. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: Incomplete suseboot directory in 10.3?
On Saturday 06 October 2007 04:31, Manfred Tremmel wrote: > Am Samstag, 6. Oktober 2007 05:58 schrieb Rajko M.: > > On Friday 05 October 2007 03:34:35 pm Manfred Tremmel wrote: > > > Am Freitag, 5. Oktober 2007 22:02 schrieb Manfred Tremmel: > > > > Am Freitag, 5. Oktober 2007 21:53 schrieb Manfred Tremmel: > > > > > after three years I was able to reanimate my old PowerBook. I > > > > > would like to install openSUSE 10.3 on it, but the suseboot > > > > > directory contains no initrd32 and no linux32.gz, like the 10.2 > > > > > suseboot directory. Any idea where to find this files? > > > > > > > > Ok, found the Answer on > > > > http://en.opensuse.org/Booting_on_PowerMac, but would be nice, to > > > > have this files also on the ftp-server. > > > > > > "Hint: on OpenSUSE 10.3 the files (linux32.gz, initrd32) can be > > > located on CD2 or CD3." > > > > > > Hm, but where to find CD2 or CD3? > > > > ftp://ftp.gwdg.de/pub/opensuse/distribution/10.3/repo/oss/suseboot/ > > And where in this directory I can find linux32.gz or initrd32? > Take a look into the 10.2 directory and you will see the difference. I found both in factory oss repository in large mini iso that was all in one. Now it is split into ppc and x86 part. http://download.opensuse.org/distribution/10.3/iso/cd/openSUSE-10.3-GM-ppc-mini.iso Here is yaboot.txt in above mini iso: Welcome to openSuSE 10.3 (PPC)! Type "install" to start the YaST installer on this CD/DVD Type "slp" to start the YaST install via network Type "rescue" to start the rescue system on this CD/DVD It seems that all you need is this mini iso. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: Incomplete suseboot directory in 10.3?
On Friday 05 October 2007 03:34:35 pm Manfred Tremmel wrote: > Am Freitag, 5. Oktober 2007 22:02 schrieb Manfred Tremmel: > > Am Freitag, 5. Oktober 2007 21:53 schrieb Manfred Tremmel: > > > after three years I was able to reanimate my old PowerBook. I would > > > like to install openSUSE 10.3 on it, but the suseboot directory > > > contains no initrd32 and no linux32.gz, like the 10.2 suseboot > > > directory. Any idea where to find this files? > > > > Ok, found the Answer on http://en.opensuse.org/Booting_on_PowerMac, > > but would be nice, to have this files also on the ftp-server. > > "Hint: on OpenSUSE 10.3 the files (linux32.gz, initrd32) can be located > on CD2 or CD3." > > Hm, but where to find CD2 or CD3? ftp://ftp.gwdg.de/pub/opensuse/distribution/10.3/repo/oss/suseboot/ -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] suggested work around for zypper/libzypp
On Thursday 04 October 2007 08:33:19 pm Igor Jagec wrote: > On Čet, 2007-10-04 at 19:08 -0500, Rajko M. wrote: > > On Thursday 04 October 2007 06:35:28 pm Igor Jagec wrote: > > > BTW what is the difference between 'zypper update' and 'zypper update > > > -t package? > > > > 'zypper update' == 'zypper update -t patch' > > Meaning, the patch option pulls delta rpms? I saw some .delta.rpm > and .patch.rpm packages in Zypper's output so I'm asking :) The .delta.rpm is a way to deliver patches. When is used delta vs. rpm that can answer some of YaST/zypper guys. This is from 'man zypper': -- Package Management Commands zypper works with several types of resource objects, called resolvables. A resolvable is a package, patch, pattern, language, or a product. package - all RPM packages including patch and delta packages patch- update of the packages, it can include special scripts and messages pattern - group of packages language - group of packages with language support product - group of packages, which are necessary to install a product -- > If so, that's great because, as I figured, that consumes less > bandwidth :) > > > > Which one of these 2 commands is used by GNOME/KDE update > > > applet? > > > > Whatever is for patches :-) > > I experienced some package removal while I was playing with that applet > on Factory, so I was just asking :) Removal will happen if package is listed for removal in rpm, but how it lands in that list can answer some of guys that actually do packaging. > > It will not install packages that doesn't meet dependencies. > > All checks are done in advance as you will notice. > > That's great, thanks! -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] suggested work around for zypper/libzypp
On Thursday 04 October 2007 06:35:28 pm Igor Jagec wrote: ... > BTW what is the difference between 'zypper update' and 'zypper update -t > package? 'zypper update' == 'zypper update -t patch' > Which one of these 2 commands is used by GNOME/KDE update > applet? Whatever is for patches :-) > Is it possible for Zypper to remove packages if it doesn't met > dependencies? I'm just asking that in case I decide to update my system > manually :) It will not install packages that doesn't meet dependencies. All checks are done in advance as you will notice. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] 10.3 install problem
On Thursday 04 October 2007 09:47:58 am Kenneth Schneider wrote: > Hardware: > > Compaq Presario 1720US laptop > P3 1G cpu > 256M ram > > During first attempt to install (fresh) while selecting custom software > choices the system became very sluggish and eventually crashed the > installer. In trying to recreate the problem the system became sluggish > again but did not crash and once swap was added the system became > responsive again. This could become a big issue for low ram systems > where a custom software selection is made. I believe this can be > verified by someone else that has a low ram system and by using the > "expert" area of the software selection. If you poke around in the > various patterns and also use search to select and deselect packages I > think this problem can be easily reproduced. Perhaps asking to mount the > swap partition before going to the summary screen would be appropriate. > After my laptop install is finished I will repeat the process and try to > reproduce the crash. If successful I will open a bug report. > > Ken What are minimum system requirements for 10.3? It is better to tell new users not to make custom software selection on systems that are below minimum. BTW, the low memory can be "emulated" with kernel parameter mem=256M or whatever small amount one wants to test. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Some 10.3 Bug Statistics
On Sunday 30 September 2007 01:58:24 pm Christian Boltz wrote: > Hello, > > on Donnerstag, 27. September 2007, Francis Giannaros wrote: > [Bug statistics] > > I have another interesting statistics: bugs per component, compared with > the releases before. First the raw data, see below for comments. > > +---+ > > | |SUSE |SUSE |openSUSE|openSUSE|openSUSE| | > | |LINUX|Linux|10.2|10.3|11.0|Total| > | |10.0 |10.1 |||| | > | > |--+-+-++++-| > | GNOME| 412 | 371 | 459 | 733 | 26 | 2001| 2) > | GNOME - Admin|.|2| 2| 16 | .| 20| > | GNOME - Platform .| 11| 13 | 22 | 3| 49| ... > | KDE| 547 | 607 | 762 | 415 | 20 | 2351| 3) ... > 2) I have no real idea why the Gnome bug count increased that much. My >guess (as a KDE user) is a) the move to /usr/bin and b) the major >version upgrade caused some problems. ... GNOME leads for now, but will catch up with KDE4 ;-) For now I know only 1 bug that comes in mind ... ... it doesn't run at all :-D -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] beagle-thunderbird has too many dependencies.
On Monday 24 September 2007 10:04:14 am Joe Shaw wrote: > Hi, > > On 9/23/07, Rajko M. <[EMAIL PROTECTED]> wrote: > > linux-kw92:~ # zypper in beagle-thunderbird > > > > The following NEW packages are going to be installed: > > MozillaThunderbird art-sharp2 beagle-gui beagle-thunderbird > > control-center2 eel > > evolution-data-server gail gconf-sharp2 glade-sharp2 gnome-desktop > > gnome-keyring gnome-main-menu gnome-menus gnome-panel gnome-sharp2 > > gnome-vfs-sharp2 gtk2-engines libbonoboui libcroco libgnome-certauth0 > > libgnomecanvas libgnomecups libgnomekbd libgnomeprint libgnomeprintui > > libgnomesu libgnomeui libgtop libgtop-2_0-7 librsvg libsoup libssui > > libwnck-1-22 libwnck metacity nautilus yast2-control-center-gnome > > bundle-lang-gnome-en gnome-audio gnome-icon-theme gnome-themes > > gnome2-user-docs tango-icon-theme > > > > Though to have it you need 123.4 M of other software, where without > > detailed checking: > > control-center2 evolution-data-server gnome-desktop gnome-main-menu > > gnome-menus gnome-panel metacity nautilus yast2-control-center-gnome > > bundle-lang-gnome-en gnome-audio > > seems to be essential for the package to work ;-) > > I'm not really sure why all these additional packages are necessary. > I am guessing you are a KDE user though. :) Yes Joe. I would like to have some mix between 2 desktops, but there is too many differences to make easy switch between them. GIMP is my favorite, so there is already plenty of GNOME installed, and there is no problem. Hard disks are large nowadays. I'm merely amused that small package pulls in bits that I would never install, like evolution-data-server, and in any case it is funny to see 123.4 MB as precondition for 144 kB. > The only explicit dep beagle-thunderbird has is on MozillaThunderbird. > It does require beagle-gui though, because Thunderbird has no way to > display an addressbook contact externally, and the tool to do that > lives in beagle-gui. Thunderbird alone requires much lesser. > beagle-gui, in turn, only explicitly requires gconf-sharp2, > glade-sharp2, glib-sharp2, gtk-sharp2. These are all only Mono > bindings for GNOME libraries, and shouldn't require bringing in things > like gnome-desktop, gnome-main-menu, metacity, etc. I tried some other gnome packages and they require lesser. For instance metacity: metacity bundle-lang-gnome-en Hmm... It seems that the rest of GNOME desktop is already installed. > So I think there is something else wrong in the chain here at a lower > level in the GNOME stack. Is there a way with zypper to see why > dependencies are being pulled in? If would know easy way I would probably walk little bit further to find a culprit. Looking in the /var/log/zypper.log even after extraction of yesterdays logs is not viable option (3 MB) for me. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] beagle-thunderbird has too many dependencies.
linux-kw92:~ # zypper in MozillaThunderbird beagle-thunderbird * Reading repository 'Main Update Repository' cache * Reading repository 'Main Repository (NON-OSS)' cache * Reading repository 'Main Repository (OSS)' cache * Reading repository 'openSUSE BuildService - Virtualization (QEMU)' cache * Reading repository 'openSUSE-10.3-OSS-KDE 10.3' cache * Reading installed packages [100%] The following NEW packages are going to be installed: MozillaThunderbird art-sharp2 beagle-thunderbird beagle-gui control-center2 eel evolution-data-server gail gconf-sharp2 glade-sharp2 gnome-desktop gnome-keyring gnome-main-menu gnome-menus gnome-panel gnome-sharp2 gnome-vfs-sharp2 gtk2-engines libbonoboui libcroco libgnome-certauth0 libgnomecanvas libgnomecups libgnomekbd libgnomeprint libgnomeprintui libgnomesu libgnomeui libgtop libgtop-2_0-7 librsvg libsoup libssui libwnck-1-22 libwnck metacity nautilus yast2-control-center-gnome bundle-lang-gnome-en gnome-audio gnome-icon-theme gnome-themes gnome2-user-docs tango-icon-theme Overall download size: 46.4 M. After the operation, additional 123.4 M will be used. Continue? [yes/no]: n *** It seems to much. linux-kw92:~ # zypper in MozillaThunderbird * Reading repository 'Main Update Repository' cache * Reading repository 'Main Repository (NON-OSS)' cache * Reading repository 'Main Repository (OSS)' cache * Reading repository 'openSUSE BuildService - Virtualization (QEMU)' cache * Reading repository 'openSUSE-10.3-OSS-KDE 10.3' cache * Reading installed packages [100%] The following NEW packages are going to be installed: MozillaThunderbird gail gnome-keyring libbonoboui libgnomecanvas libgnomeui gnome-icon-theme Overall download size: 12.9 M. After the operation, additional 39.3 M will be used. Continue? [yes/no]: n *** linux-kw92:~ # zypper in beagle-thunderbird * Reading repository 'Main Update Repository' cache * Reading repository 'Main Repository (NON-OSS)' cache * Reading repository 'Main Repository (OSS)' cache * Reading repository 'openSUSE BuildService - Virtualization (QEMU)' cache * Reading repository 'openSUSE-10.3-OSS-KDE 10.3' cache * Reading installed packages [100%] The following NEW packages are going to be installed: MozillaThunderbird art-sharp2 beagle-gui beagle-thunderbird control-center2 eel evolution-data-server gail gconf-sharp2 glade-sharp2 gnome-desktop gnome-keyring gnome-main-menu gnome-menus gnome-panel gnome-sharp2 gnome-vfs-sharp2 gtk2-engines libbonoboui libcroco libgnome-certauth0 libgnomecanvas libgnomecups libgnomekbd libgnomeprint libgnomeprintui libgnomesu libgnomeui libgtop libgtop-2_0-7 librsvg libsoup libssui libwnck-1-22 libwnck metacity nautilus yast2-control-center-gnome bundle-lang-gnome-en gnome-audio gnome-icon-theme gnome-themes gnome2-user-docs tango-icon-theme Overall download size: 46.4 M. After the operation, additional 123.4 M will be used. Continue? [yes/no]: n *** Information for package beagle-thunderbird: Repository: Main Repository (OSS) Name: beagle-thunderbird Version: 0.2.18-21 Arch: i586 Installed: No Status: not installed Installed Size: 144.1 K Summary: Thunderbird plugin for the Desktop search application Beagle *** Who said that beagle(-thunderbird) is a resource hog? It is only 144.1 K. Though to have it you need 123.4 M of other software, where without detailed checking: control-center2 evolution-data-server gnome-desktop gnome-main-menu gnome-menus gnome-panel metacity nautilus yast2-control-center-gnome bundle-lang-gnome-en gnome-audio seems to be essential for the package to work ;-) -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] RC1 i386 Installation
On Sunday 23 September 2007 11:07:23 am nordi wrote: > Rajko M. wrote > > > The problem can be slow server response. > > I had that few times on normal days. > > Press Retry few times and installation continues. > > > > IMHO, there is no ideal solution. > > If default is to try few times before pops the window with message asking > > user decision, than with bad repository it will take forever to download > > files. > > Why not handle it the same way as the reboot messages? They say "System > will reboot in xx seconds. [OK] [Cancel]" and automatically count down. > Why not have a message like: > > "Downloading xyz.rpm failed because of connection timeout. Will retry > downloading in xx seconds." > > This way, a user sitting in front of the system will get a quick reply > from the installer and someone that installs over night is also happy. Even better, it retries later with that package, and uses time to download some other package from the list, but either way it is not implemented right now, so feel free and add this to the: http://en.opensuse.org/Feature_Wishlist/YAST_related -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Encrypted filesystem problem in 10.3
On Sunday 23 September 2007 08:58:31 am Carlos E. R. wrote: > Juan Erbes wrote: > > 2007/9/23, Carlos E. R. <>: > >> Hi, > >> > >> I have the following defined on 10.2 (works fine): > >> > >> /dev/dvd /mnt/dvd.crypta.x auto \ > >> ro,noauto,user,loop,encryption=twofish256 0 0 > > > > You must set this in the udev rules, because the removable devices are > > now managed by the udev rules, and the permissions by Policikit. > > The settings for removable devices in fstab make no sense. > > The only removable device that continues appearing in fstab is the > > floppy. > > Could you please expand on this, giving exact instructions? I guess this is one practical project for openSUSE wiki. Article that will explain use of udev, with few more articles with examples will be something that many will appreciate. > Remember that it works in 10.2 perfectly. Has udev changed in 10.3 so > much? There is no comment about this in the release notes. Can't DVDs be > mounted manually, then? I don't believe it. > > This is something solely related to encryption changes, not udev. > > Proof: I mounted my external USB drive manually via fstab. No problem at > all: > > LABEL=usb_sg60 /mnt/usb/usb_sg60 reiserfs \ > noatime,user,noauto,acl,user_xattr 0 0 It can be mounted manually, but if you can configure udev rules to do that for you why not to use them. Reduction of typing is the primary reason for existence of fstab, modprobe.conf, etc. Problem with udev is that it is new and not really explained on openSUSE example. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] RC1 i386 Installation
On Sunday 23 September 2007 06:24:15 am Carlos E. R. wrote: > nordi wrote: > > Stephan Kulow schrieb: > > > > > > Not to speak about the timeouts that occured and caused the installation > > to be interrupted until I pressed the "try downloading again" button. > > Shouldn't the downloader be able to retrieve some files via internet > > without me pressing a button all the time? > > It would be preferable that the installation continued with the next > file automatically, or at least after some time of no user response, > with an option to cancel that repo, or to find another repo. The problem can be slow server response. I had that few times on normal days. Press Retry few times and installation continues. IMHO, there is no ideal solution. If default is to try few times before pops the window with message asking user decision, than with bad repository it will take forever to download files. It will never pop the message, but process will spend more time trying again than actually installing files. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] RC1 install not completing
On Saturday 22 September 2007 16:15, Glenn Holmer wrote: > OK, I can see the details in 326942, which my issue was marked as a > duplicate of within minutes. Now I can breathe again... :) The SUSE guys are everywhere ;-) -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Warning: Don't install kernel--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]
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 Yast2>Hardware>Printer each time I > need to use the printer. Don, https://bugzilla.novell.com/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=fulltext&long_desc=&classification=openSUSE&product=openSUSE+10.3&component=Printing&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=anywords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-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] 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]
Re: [opensuse-factory] Warning: Don't install kernel--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] Firewall not consistent..
On Saturday 15 September 2007 12:38:53 pm jdd wrote: > M9. wrote: > >> informed? > > > > spyware and datamining.. ;-) > > ( i know this is unknown to linux :-) Not yet, but when LSB kick in and it would be easy to install any program to any distro, situation may change. > if you let your computer infected, there is nothing a firewall can do. > it should be some sort of "apparmor" for Windows, monitoring wich > application do what. That is what most 'firewalls' for windows do. They call it firewall, as it sounds good, but it is actually proxy that monitors all traffic. ... > default openSUSE install are usually quite defensives and allow little > open ports and little running servers (I'm not even sure that sshd is > running by default) It is not enabled by default. > >> access must be done on the host: > >> > >> * by a standard protocol (smb, ssh, ftp, http...) accepted by a server > >> * by two applications sharing the same port > > > > yes that is the procedures.. > > so what is the server you fear to be broken? ... Don't forget that there is few computers in M9 network wireless. and problem can come from that side too. They are part of internal network, they probably have enabled ad hoc wireless and if some neighbor has no wireless access point it can without knowing what he is doing connect to any windows computers in range. If he has viruses they will find the way in. Taking how easy most of windows users dismiss firewall popups it opens unlimited possibilities. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] /etc/modprobe.d/unsupported.blacklist
On Wednesday 12 September 2007 12:19, Michal Marek wrote: > tail -1 /etc/modprobe.d/unsupported.blacklist Yes. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] opensuse wiki: proposal for Bugs:Most Annoying Bugs page format
When adding bug to the list of most annoying bugs it would be good that everybody follow the same system. == openSUSE 10.3 Beta 3 == * the newest bug * already listed bugs that follows overall schema on the page, where newer versions are listed at the top of the page. It is also usefull to have listed Workround: or/and Solution: summary, like Workround: nspluginwrapper -a -i Solution: online update published -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] 10.3 Beta3 - YAST reports file size incorrectly when adding software after an install
On Saturday 08 September 2007 14:30, Clayton wrote: > On 9/8/07, Martin Schlander <[EMAIL PROTECTED]> wrote: > > Den Saturday 08 September 2007 21:09:37 skrev Clayton: > > > I just installed 10.3 Beta3 in VMWare. The install went OK taking > > > defaults only. Post install I started YAST and selected gcc and the > > > kernel-sources. YAST then reported that this install would take +/- > > > 265Gb of diskspace. Of course since there is only 5Gb in / YAST > > > wasn't all that happy. I was able to ignore and complete the install. > > > > > > Anyone else bump into this? > > > > https://bugzilla.novell.com/show_bug.cgi?id=308362 > > OK, I obviously need to practice searching bugzilla :-P I will spend > a little more time poking about next time. I would look first at: http://en.opensuse.org/Bugs:Most_Annoying_Bugs_10.3_dev it is easier than bugzilla and covers, well ... most annoying bugs ;-) -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] beta 3 fails in virtual box 1.3.6
On Saturday 08 September 2007 13:40, jdd wrote: > Clayton wrote: > > There is a bug open on this... number 307676 (mentioned in the other > > thread on this problem) > > > > Some have said that if you manually switch the bigsmp kernel with the > > default, that it will work > > probably not the same bug: my opensuse 10.3 boots perfectly, but stops > in kdm prompt and not having asked for pass before... I can't go further > > I had already this problem and solution involve botting rescue, making > a chroot and changing pass, but it need also mounting some system > folders and I have no time to do this today :-( > > jdd You mean: mount --bind /sys /mnt/sys mount --bind /proc /mnt/proc mount --bind /dev /mnt/dev I got glitch with bootloader that is not yet resolved, but without /dev/ I couldn't get any hard disk to appear. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] openSUSE 10.3 BETA3 refuses to run on VirtualBox
On Saturday 08 September 2007 09:55:04 am Alexey Eremenko wrote: > hi all ! > > openSUSE 10.3 BETA3 refuses to run on VirtualBox 1.5.0. BETA2 worked. > > Host: openSUSE 10.2, Athlon XP. > > When booting kernel, it says: "PANIC: CPU too old for this kernel.". > Plus for some strange reason openSUSE 10.3 BETA3 chooses bigsmp > instead of default kernel. > > See: http://forums.virtualbox.org/viewtopic.php?t=1625 Bug 307676 - CPU is too old for this kernel -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] broken grub after update from beta1
On Saturday 08 September 2007 05:46:36 am Andreas Vetter wrote: > On Sat, 8 Sep 2007, Richard C Creighton wrote: > > Andreas Vetter wrote: > > > Hi, > > > > > > I updated a x86_64 machine from beta1 to beta3. After the packages were > > > installed I found the machine in a reboot loop. The grub boot loader > > > was not working any longer. So I tried Repair System. The automatic one > > > obviously deleted Windows from menu.lst. Then it threw an error about > > > not being able to access /dev/fd/62. A second try with this one left me > > > with a single entry for linux (i.e. failsafe and xen were gone, too). This is a bug in Repair system. > > > So I tried the Expert option Repair Boot Loader. It recreated the > > > default and failsafe entries in menu.lst, but was not able to create > > > initrd. the script complained about not being able to access /dev/sda6 > > > which is the root / partition of my system (xfs containing /boot, too). It acts like xfs driver is missing. > > > After that wreckage I decided to try a new installation of beta3. So I > > > have no logs for the above problems. > > > > > > Has anybody similar behaviour? > > > > check out https://bugzilla.novell.com/show_bug.cgi?id=304657#c11 and see > > if anything rings a bell in your case and if it does, leave them a > > comment giving as much info as possible. > > Hm, I don't think this is related to my case. I think the bug in the 10.3 > update kernel package is the culprit in that case. The primary reason that you needed Repair System is kernel update, but -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] openSUSE 10.3, kernel update 2.6.22.5-12 doesn't create initrd
On Saturday 08 September 2007 01:04:40 am Marcus Meissner wrote: > On Fri, Sep 07, 2007 at 07:14:33PM -0500, Rajko M. wrote: > > The latest kernel 2.6.22.5-12-default from update repositories has bug in > > postinstall script that prevents creation of initrd, making system > > unbootable. > > > > Bootloader is on different partition and script test for menu.lst fails, > > making script to skip creation of initrd. This has happened in 10. (bug > > 2290959), but it was corrected in 10.3 kernels and I closed the bug > > report. Now it is added new function in script and bug reintroduced. > > > > I guess that this should be a new bug, but not sure? > > Open a new bugreport, but refer to the old. Thanks. https://bugzilla.novell.com/show_bug.cgi?id=308970 -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] openSUSE 10.3, kernel update 2.6.22.5-12 doesn't create initrd
The latest kernel 2.6.22.5-12-default from update repositories has bug in postinstall script that prevents creation of initrd, making system unbootable. Bootloader is on different partition and script test for menu.lst fails, making script to skip creation of initrd. This has happened in 10. (bug 2290959), but it was corrected in 10.3 kernels and I closed the bug report. Now it is added new function in script and bug reintroduced. I guess that this should be a new bug, but not sure? -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Kmail keeps its own list of read messages instead of quering the IMAP server
On Friday 07 September 2007 05:55:57 am Silviu Marin-Caea wrote: > Misfeature? > > It might coincide with the time that the kmail build is called > "enterprise". > > I didn't see this happen in earlier betas. But this might be because I was > carrying the home directory over installations. Now I have started with a > fresh home directory and configured everything from scratch. All messages > appear as unread. If I use the webmail it's a totally different picture. You mean you moved kmail directories to new installation? If that is the case, I have something similar on every move. Kmail forgets folder settings like threading, that is a mail list in the folder, custom color for folders with new messages, the only thing that it accepted last time was message status read/unread :-) -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Device already mounted or mountpoint busy error after some beta2 update, I guess
On Wednesday 05 September 2007 09:25:10 am Wolfgang Woehl wrote: > Mittwoch, 5. September 2007 Dirk Mueller: > > On Wednesday, 5. September 2007, Wolfgang Woehl wrote: > > > No. And again: I did not configure or invoke device-mapper explivitly. > > > This is a non-tweaked 10.3beta2 install and the mount behaviour changed > > > a day after the install with -- i guess -- an automatic update. > > > > The bug is tracked in #302422 and its marked as fixed for Beta3. please > > try there again. > > Thank you. Sorry for not reading through 302422 up to the multipath-tools > and kpartx change comment. > > How can i "upgrade" to beta3? > Wolfgang 1) Download Beta 3 CD/DVD and update. 2) Using YaST module Update to Factory. I guess it is already frozen in Beta3 Status. This is how I'm going to update. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Device already mounted or mountpoint busy error after some beta2 update, I guess
On Tuesday 04 September 2007 15:50, Wolfgang Woehl wrote: > Dienstag, 4. September 2007 Wolfgang Woehl: > > Montag, 3. September 2007 Rajko M.: > > > On Sunday 02 September 2007 16:15, Wolfgang Woehl wrote: > > > > But my initial posting was about an internal device > > > > disappearing from the usual mount infrastructure. > > > > > > It is solved. > > > > I still don't know why the internal device got grabbed by device-mapper. > > I suspect not having it in fstab (which was on purpose) led to it. > > Although I never conciously configured or invoked dm-mechanisms. > > Plus, I realize this just now, plugging in a usb mass-storage device makes > kde pop up "open in window?" which it tries but fails to show the content > of because device-mapper grabbed it. Is this the default behaviour? It > can't be. I'm pretty sure it is not. Is this happening after deleting /etc/udev/rules.d/62-dm_linear.rules and dmsetup remove_all -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] High number of serious bugs in GNOME
On Monday 03 September 2007 13:06, Alberto Passalacqua wrote: > > And for instance: > > 301716Cri P5 open NEW Pidgin segfaults when sending > > AIM message to yourself. > > > > Taking the type of application is it really critical? > > Is that mean that critical is used for any crash? > > Funny, indeed. > > The reporter is Bryan Perry @ Novell, so it is probably considered > important. It might be the company policy to set critical if application crashes, I have seen such comment in one of bugs that you can find on the list. If you look the list than you can see few similar reports. Later I'm going to see more, but if there are many of the above kind GNOME is safe :-) -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] High number of serious bugs in GNOME
On Sunday 02 September 2007 10:52:54 am Alberto Passalacqua wrote: > Hello everyone, > during a discussion on IRC it emerged that GNOME still has a very high > number of blockers and critical bugs. > As it can be seen here: The numbers seems to be lower today. https://bugzilla.novell.com/report.cgi?x_axis_field=&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&long_desc_type=fulltext&long_desc=&classification=openSUSE&product=openSUSE+10.3&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=anywords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=REOPENED&bug_severity=Blocker&bug_severity=Critical&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= > GNOME + Evolution has 26 of them. Now 23 > Plus, from bugzilla it appears that GNOME + GNOME Admin/Platform + > Evolution have 201 bugs: https://bugzilla.novell.com/report.cgi?x_axis_field=&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&long_desc_type=fulltext&long_desc=&classification=openSUSE&product=openSUSE+10.3&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=anywords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=REOPENED&bug_severity=Blocker&bug_severity=Critical&bug_severity=Major&bug_severity=Normal&bug_severity=Minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Now 189 > Considering the short time before the final release (~1 month), I think > it would be helpful to know the actual situation of the fixes, and if > there's enough time to solve all these issues before the release date. I looked further: https://bugzilla.novell.com/buglist.cgi?action=wrap&bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=Blocker&bug_severity=Critical&bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=REOPENED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&classification=openSUSE&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailqa_contact2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field0-0-0=noop&keywords=&keywords_type=anywords&long_desc=&long_desc_type=fulltext&product=openSUSE%2010.3&short_desc=&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type0-0-0=noop&value0-0-0=&votes=&=&component=GNOME And for instance: 301716Cri P5 open NEW Pidgin segfaults when sending AIM message to yourself. Taking the type of application is it really critical? Is that mean that critical is used for any crash? -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Device already mounted or mountpoint busy error after some beta2 update, I guess
On Sunday 02 September 2007 16:15, Wolfgang Woehl wrote: ... > > Be aware that abandoning mount by device path was forced by increasing > > number of devices that can be mounted in different order on each boot > > which results in different path. All SATA and USB devices are prone to > > that. > > Internal sata devices could be mounted in different order each boot? My bad :-( SATA is not in the same bag as USB. SATA device placement can be changed on hardware changes. Adding or removing PATA drive will automatically change SATA placement reported by BIOS and goof mounting if it is defined by device path. This is not a big problem if you know that it exists, but there is no problem if you use present schema or mounting by label (haven't checked the rest). > > In order to access them you have to know where they are located, with > > different path each time you have to find something that doesn't change. > > Serial numbers are safe bet, they will be the same even across multiple > > installations, or large systems with whole a lot of hard disks. Lables > > would be too, but than you risk to create system that is today fine, but > > with increase in number of devices can run out of available labels in the > > future. The present system will hardly hit the limit any soon. > > Ok, I've read up a bit on udev and am aware now of the possibilities. But > I'm not running a serverfarm here. The openSUSE is created for many different users, and present schema works for all of them. Besides if you replace disk with present schema mount will report error even if disk is formatted ie. mountable, but content doesn't fit in your system. This will prompt you to update configuration. Mount by path on the other hand can happily accept that disk which can lead to problems later. The label system can do the same if label is the same. > I change disks once in 2 years maybe. For most desktop users this is not an issue, except the case with SATA drives that happen not so often. > Anyway, if all this worked I couldn't care less, except for the serial > number notion (which i realize is not trivial to get rid of if you want the > above safety net). If disk serial number is problem as privacy concern, than forget it. The Ethernet card has unique number, motherboard, if computer is brand name, has another one, than IP address, and more can be used to identify person. Of course not by everyone, but privacy in the Internet is illusion. Those that sell privacy services with very broad claims of protection count on peoples lack of knowledge. "Browse Internet anonymously" is one of slogans I can recall. They protect to some extent, but far from total. > But my initial posting was about an internal device > disappearing from the usual mount infrastructure. It is solved. > Thank you again for your advice, Wolfgang Have fun! -- Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Device already mounted or mountpoint busy error after some beta2 update, I guess
On Sunday 02 September 2007 07:42, Wolfgang Woehl wrote: > I've looked > at /etc/udev/rules.d/60-persistent-storage.rules and I wonder: Is that the > only/the right spot to get rid of serial numbers? I guess it is, but you can also use YaST Partitioner (command 'yast2 disk'). Select partition that you want to change, click on Edit button. In window that pops up click on 'Fstab Options' and in new window you can tell system to mount volume in different way. Be aware that abandoning mount by device path was forced by increasing number of devices that can be mounted in different order on each boot which results in different path. All SATA and USB devices are prone to that. In order to access them you have to know where they are located, with different path each time you have to find something that doesn't change. Serial numbers are safe bet, they will be the same even across multiple installations, or large systems with whole a lot of hard disks. Lables would be too, but than you risk to create system that is today fine, but with increase in number of devices can run out of available labels in the future. The present system will hardly hit the limit any soon. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Device already mounted or mountpoint busy error after some beta2 update, I guess
On Saturday 01 September 2007 18:30, Wolfgang Woehl wrote: > Hi, > > On a 10.3beta2 couple days ago my /dev/sdb1 was perfectly mountable. It was > not in in fstab on purpose, mind you. Then something got updated by > opensuse updater and sdb1 was not mountable anymore. > > mount /dev/sdb1 /mnt > said "already mounted or /mnt busy" which was so not true. Errk. > > Googling I found people almost back in the last century debating this. The > good advice pointed towards device-mapper. > > Turned out that device-mapper had grabbed sdb. So can _I_ do something with > it too? Like use my hard disk? Not that I ever configured, invoked, > worshipped device-mapper at all. > > dmsetup ls > gave me 2 strings garbled together from device-mapper lingo and the name > and serial number of my disk. Like > linear-scsi-SATA_ST3500630A_serial_number (253, 0) and > linear-scsi-SATA_ST3500630A_serial_number_part1 (253, 1) > > dmsetup remove linear-scsi-SATA_ST3500630A_serial_number_part1 and > dmsetup remove linear-scsi-SATA_ST3500630A_serial_number > and > mount /dev/sdb1 /mnt > and things are back the way they were. > > Am I missing something deep? Plus: Apart from police people who in this > whole wide world thinks having serial numbers of your disks all over the > system was cool? Could that be, like, an _option_ please? My face turns all > yellow when I look at /etc/fstab these days. Can someone tell me the > advantages of this? > > Thanks, and thank you for a pretty amazing beta2. > Wolfgang It seems to be the same as this: https://bugzilla.novell.com/show_bug.cgi?id=307044 but looking another similar bug, leads to: https://bugzilla.novell.com/show_bug.cgi?id=302422 origin. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] 10.3 Beta-2 + nvidia-drivers
On Friday 31 August 2007 06:53:19 am Patrick Shanahan wrote: > * Rajko M. <[EMAIL PROTECTED]> [08-31-07 07:30]: > > Although someone removed advice for; > >cd /usr/src/linux > >make oldconfig > >make prepare > > from article > > http://en.opensuse.org/NVIDIA > > in my experience, nvidia installer will not work without at least first 2 > > lines, ie, changing working directory to /usr/src/linux and than copy of > > current configuration: > >cd /usr/src/linux > >make oldconfig > > the only line that last version of nvidia installer didn't really needed > > was 'make prepare' . I added that too, just to make sure that every > > possible effort is made to have all bits ready. > > > > The guy that removed above 3 commands from article is, so far I know, one > > of kernel developers, and I don't go in discussion what is right, the > > SUSE kernel or nvidia installer creators. > > I have not ever found those steps necessary when installing NVidia's > package, just " sh ./NVIDIA-Linuxrun -a" from runlevel 3, then > return to runlevel 5. I know that when I started to compile nvidia drivers it was not necessary to run any of above commands. Than someone asked for advice, and I pointed to article. Than he came again with error that I wasn't able to see before, so I checked, and it worked for me, but my kernel sources are usually configured, as nvidia is not only reason that I have them. After removing kernel sources, installing and trying again I found out that it doesn't work as before and put advice online. That is whole story. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] 10.3 Beta-2 + nvidia-drivers
On Friday 31 August 2007 01:04:46 am TooMany Secrets wrote: > 2007/8/31, Rajko M. <[EMAIL PROTECTED]>: > > But there is another question, is it necessary 'bigsmp'. > > TooMany Secrets should have a big machine (> 4GB RAM, etc) to need it. > > No. My machine has 1 Gb RAM. The only question about to any > especiallity into linux kernel, is about to smp, although it is not > necessary. > > Thanks. In that case I would install kernel that ends with -default. That is smp kernel and perfectly fits your machine. The sources have to match running kernel, and than nvidia installation will not complain. Although someone removed advice for; cd /usr/src/linux make oldconfig make prepare from article http://en.opensuse.org/NVIDIA in my experience, nvidia installer will not work without at least first 2 lines, ie, changing working directory to /usr/src/linux and than copy of current configuration: cd /usr/src/linux make oldconfig the only line that last version of nvidia installer didn't really needed was 'make prepare' . I added that too, just to make sure that every possible effort is made to have all bits ready. The guy that removed above 3 commands from article is, so far I know, one of kernel developers, and I don't go in discussion what is right, the SUSE kernel or nvidia installer creators. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] 10.3 Beta-2 + nvidia-drivers
On Thursday 30 August 2007 04:05:05 pm Patrick Shanahan wrote: > > > rpm -q kernel-smp kernel-source > > > to see that you do have the *same* versions installed > > You indicated that you used kernel-smp, but Philipp Thomas says that > kernel-default is SMP, so It was 'bigsmp' in error report >> The kernel header file >> '/lib/modules/2.6.22.3-7-bigsmp/build/include/linux/kernel.h' >> does not exist... But there is another question, is it necessary 'bigsmp'. TooMany Secrets should have a big machine (> 4GB RAM, etc) to need it. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: Re: [opensuse-factory] Re: [opensuse-factory] I‘m not able to install software via "software management" in Beta2
On Sunday 26 August 2007 03:12:40 pm Rastislav Krupanský wrote: > still the same > > > linux:/home/user # zypper in -n opera > Refreshing 'local' > * Cleaning repository 'local' cache > * Building repository 'local' cache > * Reading repository 'openSUSE-10.3-OSS-KDE 10.3' cache > * Reading repository > 'http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/' > cache * Reading repository > 'http://download.opensuse.org/distribution/SL-Factory-non-oss/inst-source-e >xtra/' cache * Reading repository > 'http://download.opensuse.org/distribution/SL-OSS-factory-debug/inst-source >-debug/' cache * Reading repository 'local' cache > * Reading installed packages [100%] > > > The following NEW package is going to be installed: > opera > > Overall download size: 6.3 M. After the operation, additional 18.8 M will > be used. Continue? [y/n]: y > Downloading package opera-9.23-3.i586, 6.3 M (18.8 M unpacked) > Unexpected exception. > Can't provide file ./suse/i586/opera-9.23-3.i586.rpm from repository > http://download.opensuse.org/distribution/SL-Factory-non-oss/inst-source-ex >tra/ Please file a bug report about this. > See http://en.opensuse.org/Zypper#Troubleshooting for instructions. OK. The some other exception problem was symptom of known bug, corrupt /var/cache/zypper/zypper.db which can be deleted and recreated with zypper ref or simply by starting YaST Software Management. Maybe very verbose zypper - ref will give more information, if needed. I would recommend to use the same - for installation etc. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: [opensuse-factory] I‘m not able to install software via "software management" in Beta2
On Sunday 26 August 2007 02:44:30 pm Krupanský Rastislav wrote: > linux:/home/user # zypper in opera Can you try zypper in -n opera -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Configuring update Factory
On Friday 24 August 2007 06:08:23 am Stanislav Visnovsky wrote: > Dňa Friday 24 August 2007 11:58:25 Rajko M. ste napísal: > > On Friday 24 August 2007 04:41:38 am Christoph Thiel wrote: > > > On Fri, Aug 24, 2007 at 04:35:59AM -0500, Rajko M. wrote: > > > > On Friday 24 August 2007 03:43:43 am Stanislav Visnovsky wrote: > > > > > Dňa Friday 24 August 2007 10:33:46 Andreas Jaeger ste napísal: > > > > > > "Rajko M." <[EMAIL PROTECTED]> writes: > > > > > > > I added 10.3 update repository, and it takes quite some time to > > > > > > > see the end Online Update configuration. > > > > > > > > > > > > > > What is purpose of refreshing all repositories when one wants > > > > > > > to configure online update? > > > > > > > > > > > > No idea - I suggest to file a bugreport > > > > > > > > > > Definitely. > > > > > > > > > > Stano > > > > > > > > Done. > > > > bug #304211 > > > > > > > > BTW, Martin Vidner question about zypper > > > > [zypp-devel] listing patches - consider only some repos? > > > > seems to address the same. > > > > > > IIRC we used to have a flag in susetags, that could flag a repository > > > to be "none-changing". Metadata for a repository like that (e.g. the > > > ftp tree for a released product), would never have to be > > > downloaded/checked again. Klaus? > > > > > > > > > Best, > > > Christoph > > > > Under 'update/10.3' I don't expect anything except patches and there is > > no need to run all repositories refresh to get data for patches. > > AFAIK there is no way to flag a repository to be one providing patches. So, > this is almost impossible right now and will definitely fail in some use > cases. The flag can be the name, like 'update'. > I think it is correct to refresh all repos that have autorefresh enabled. Just to make sure: - enabled repositories, with - enabled refresh. > You never know the dependencies among the packages, it might turn out that > a patch will trigger an update from a different repository. I got always feeling that (security) update repository is stand alone, it doesn't contain patches (packages) that lead to use of other repositories. If it will demand other repositories than for successful update I have to make sure that all of them are online and up to date, which brings more conditions in equation and rises chance for intermittent failures. Something that we had never before. If I was able to contact update server, I was able to get all updates. > However, configuring repositories should not refresh, there is no need to > do it. I considered first YOU start right after as a part of configuration. Having URL listed doesn't mean that I can use repository. The complaint was about long time it took to start you, like repository initialization. > Stano > > > Current setup here has only one repository that is disabled as it is > > duplicate, the rest is Factory and in a few days it will start to change > > again, so I'll keep that with refresh on. BTW, I noticed download of root and boot files, when new Factory installation was initialized!? That is increasing initialization time substantially. I stopped zypper twice, considering endles download to be another bug or metadata corruption, and then used YaST that is more verbose by default, to see what is downloaded. My Internet connection is good pipe. I can imagine how this appear on dial up. What would be need for them? Why it loads ppc in a system that is x86_64? I can see need for x86, but ppc. It will save some initialization time if there will be switch to list all architectures, and default should be the installed one. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Configuring update Factory
On Friday 24 August 2007 04:41:38 am Christoph Thiel wrote: > On Fri, Aug 24, 2007 at 04:35:59AM -0500, Rajko M. wrote: > > On Friday 24 August 2007 03:43:43 am Stanislav Visnovsky wrote: > > > Dňa Friday 24 August 2007 10:33:46 Andreas Jaeger ste napísal: > > > > "Rajko M." <[EMAIL PROTECTED]> writes: > > > > > I added 10.3 update repository, and it takes quite some time to see > > > > > the end Online Update configuration. > > > > > > > > > > What is purpose of refreshing all repositories when one wants to > > > > > configure online update? > > > > > > > > No idea - I suggest to file a bugreport > > > > > > Definitely. > > > > > > Stano > > > > Done. > > bug #304211 > > > > BTW, Martin Vidner question about zypper > > [zypp-devel] listing patches - consider only some repos? > > seems to address the same. > > IIRC we used to have a flag in susetags, that could flag a repository to be > "none-changing". Metadata for a repository like that (e.g. the ftp tree for > a released product), would never have to be downloaded/checked again. > Klaus? > > > Best, > Christoph Under 'update/10.3' I don't expect anything except patches and there is no need to run all repositories refresh to get data for patches. Current setup here has only one repository that is disabled as it is duplicate, the rest is Factory and in a few days it will start to change again, so I'll keep that with refresh on. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Configuring update Factory
On Friday 24 August 2007 03:43:43 am Stanislav Visnovsky wrote: > Dňa Friday 24 August 2007 10:33:46 Andreas Jaeger ste napísal: > > "Rajko M." <[EMAIL PROTECTED]> writes: > > > I added 10.3 update repository, and it takes quite some time to see the > > > end Online Update configuration. > > > > > > What is purpose of refreshing all repositories when one wants to > > > configure online update? > > > > No idea - I suggest to file a bugreport > > Definitely. > > Stano Done. bug #304211 BTW, Martin Vidner question about zypper [zypp-devel] listing patches - consider only some repos? seems to address the same. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Konqueror KDE 3.5.7-6 from Factory.
On Friday 24 August 2007 02:30:32 am Peter Buschbacher wrote: > Rajko M. schrieb: > > Konqueror 3.5.7-6 is freezing on many pages, waiting on missing images. > > It can be terminated by the system, otherwise no response. > > > > http://blogs.zdnet.com/hardware/?p=697&tag=nl.e539 > > http://newsletter.infoworld.com/t?ctl=18E26C3:C77A76F176CA0254F8962FADCC4 > >E786AEFF29049075316B4 etc. > > > > Anybody noticed that? > > Yes its an http://en.opensuse.org/Bugs:Most_Annoying_Bugs_10.3_dev. > both sides contain flash ads. > > Peter Buschbacher Thanks Peter. It is funny that Firefox has no problems. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Konqueror KDE 3.5.7-6 from Factory.
Konqueror 3.5.7-6 is freezing on many pages, waiting on missing images. It can be terminated by the system, otherwise no response. http://blogs.zdnet.com/hardware/?p=697&tag=nl.e539 http://newsletter.infoworld.com/t?ctl=18E26C3:C77A76F176CA0254F8962FADCC4E786AEFF29049075316B4 etc. Anybody noticed that? -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Configuring update Factory
I added 10.3 update repository, and it takes quite some time to see the end Online Update configuration. What is purpose of refreshing all repositories when one wants to configure online update? -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: Changes with boot/init for 10.3 ? Kernel locks in 10.3, not in 10.2 ?
On Thursday 16 August 2007 06:04, Andreas Vetter wrote: > > The other method to isolate script would be add echo command to scripts > > that will give on the screen script name. For instance > > echo $0 >> /tmp/startup.log > > > > That will at least tell what was loaded before lockup and it will be > > preserved after new boot. > > maybe a sync after the echo would be a good idea Yes. It will be. One more line that will mark regular end of the script would be good too, but than one needs script that will change all scripts in /etc/init.d, or change scripts manually and save set for future. Than on next release use diff and look only scripts that are changed. I wonder what openSUSE developers use for debugging of start up? -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: Changes with boot/init for 10.3 ? Kernel locks in 10.3, not in 10.2 ?
On Wednesday 15 August 2007 22:22, Kevin Valko wrote: > On Wednesday 15 August 2007 09:10:45 pm Rajko M. wrote: > > On Wednesday 15 August 2007 12:54, Kevin Valko wrote: > > > and maybe disabling parallel > > > services as well. > > > > I would start with that. > > Than you have better chance to find service that makes trouble. > > Disabling parallel services did allow the system to boot normally without > requiring interactive confirmations, so there is definitely a conflict > happening somewhere with the boot services running in parallel. > > Unfortunately I'm not sure which one, I tried disabling a number of them > individually but the boot still hard-locked when parallel services were > enabled, I guess I can try to change the S/K sequences in boot.d, to see if > grouping the services (the culprit lies in S12) instead of all together can > point out the issue. G. > > On the plus side, disabling parallel loading didn't have a too significant > impact on my boot time, it's still more or less in line with what I had in > 10.2, so it's hardly the end of the world, but it is kind of a drag since > faster booting is one of the significant improvements for 10.3. > > Cheers, > KV Hi Kevin, If parallel booting makes problem, than is some of scripts the culprit. It doesn't wait for it's dependencies to be performed. Grouping services will not help much as they are not ran sequentially anyway, but cleaning log files, booting and after lockup, booting Live CD and looking in logs may help to debug issue. The other method to isolate script would be add echo command to scripts that will give on the screen script name. For instance echo $0 >> /tmp/startup.log That will at least tell what was loaded before lockup and it will be preserved after new boot. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: Changes with boot/init for 10.3 ? Kernel locks in 10.3, not in 10.2 ?
On Wednesday 15 August 2007 12:54, Kevin Valko wrote: > and maybe disabling parallel > services as well. I would start with that. Than you have better chance to find service that makes trouble. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] 10.3 CD1 Gnome Beta1 issues
On Sunday 12 August 2007 11:00:10 am James Tremblay wrote: > On Sat, 2007-08-11 at 23:33 -0400, James Tremblay wrote: > > Today I put my play disk back in my laptop (IBM r51) to try CD1 B1 and > > it still does not have the kernel modules to configure the IPW2200 from > > Intel (same issue as beta7), I look at the Intel wireless firmware > > offerings and the ipw2200 is not there, I can not delete the > > semi-configured card, I can not install a duplicate. so I'm back on > > SLED10SP1 which definitely not a problem ;) > > I connected My laptop to a wired network added the "community > repositories" and then installed the "IPW-firmeware" module which then > allowed me to configure the wireless nic. > Should I bug-report this? Yes and not. The GOME CD is still oversized and they look how to kick out some stuff that is not essential. Probably good workaround might be what you did, but integrated in the system as default, ie. additional repositories should be included withut asking for any manual intervention, so that user can find missing stuff by simply going online. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Beta1 on VMWare requesting host clock rate change
On Sunday 12 August 2007 06:49:32 am Vahis wrote: > So M$ supports Linux quite well... If you ask them ;-) With QEMU I've seen that kernel switched to clock pit during installation or boot, but I can't recall was that with Beta1 or Alpha 7 where I started using QEMU with kqemu (kernel level accelerator). -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Call for testing: Alpha7 Live CDs
On Sunday 05 August 2007 09:48:41 am Stephan Kulow wrote: > Hi! > > With openSUSE 10.3 we want to try something different: > have live CDs available already during beta phase, so > as a start I created live CDs of the installation set of > the i386 GNOME CD and i386 KDE CD (the final version > might come with a live installer if it works out). > > So please give these a try: > > http://download.opensuse.org/distribution/10.3-Alpha7/iso/cd/openSUSE-10.3- >Alpha7-GNOME-Live-i386.iso > http://download.opensuse.org/distribution/10.3-Alpha7/iso/cd/openSUSE-10.3- >Alpha7-KDE-Live-i386.iso > > Report problems in this thread - this is a very first try of 10.3 live CDs, > so we better wait for the beta with bugs :) 1) QEMU without acceleration is still usable (about 300 MHz CPU) 2) QEMU with acceleration is fine except one has to configure default gateway. 3) eMachines 6528 (64 bit, AMD 3500, with 1 GB MB RAM, IDE hard disk) Dual screen has the same problem as in regular 10.3 a7, but end result is one good screen. 4) MSI motherboard, Athlon 2000+, IDE hard disks, nVidia MX 4000 AGP Boots with errors mentioned in other posts. Has icon on a desktop that gives back greeter. Nice. Openoffice has somewhat dark splash ;-) -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] More packages to remove from Gnome CD.
On Wednesday 08 August 2007 14:32, Claes Bäckström wrote: > On 8/8/07, Bernhard Walle <[EMAIL PROTECTED]> wrote: > > * Claes Bäckström <[EMAIL PROTECTED]> [2007-08-05 22:37]: > > > sensors > > > > Isn't that needed for some GNOME applet that displays the CPU > > temperature? At least gkrellm uses it, but I don't know if that is on > > the GNOME CD. > > Well gnome-applets don't depend on it so if it needs it then we have a > bug there. > Sensors is not essential nor large and it can be left in FTP repository for those few that would like to have it. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] support r/w for ntfs in aplha7
On Monday 06 August 2007 02:48:33 am Krupanský Rastislav wrote: > hello > i´d like to test support for r/w on ntfs partition, but i don´t know how i > can enable support for r/w on ntfs partition in aplha7.i installed alpha7 > cd and dvd also, but partitions ( i have /dev/sda1) with ntfs is not > mounted.what should i do?i know that you planned to integrate it via > ntfs-3g driver. > btw i sent a bug #297043 about it. > > Thanks Hi Rastislav, check is it installed ntfs-3g package and than enable rw access in fstab. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Yast2 Alpha 5
On Sunday 05 August 2007 08:03:10 pm Donn Washburn wrote: > Rajko M. wrote: > > On Sunday 05 August 2007 04:14:43 pm Donn Washburn wrote: > >> Key Group; > >> > >> I decided last night to try a "Yast2 > Software Management" on this > >> machine ($HOSTNAME=m1l). I deselected the Yast check dependencies every > >> time box due to the time it takes. I selected what I wanted and hit > >> "Accept". At that point Yast did a automatic dependency check. That is > >> where the problem came up - Yast failed to return. It did after about 8 > >> hours (last night to this AM) return an error stating that it was > >> looking for "$HOSTNAME=localhost". It appears the variable $HOSTNAME is > >> not being carried correctly. > >> > >> I have selected about 10 to 15 "Update Source" sites, Yast seems to be > >> happy with networking the URL. It goes out and finds the URL and > >> repodata plus subdirectories. > > > > Is that alpha 7? > > No Sir; > > It is Alpha 5. If I get caught up today on all my duties I may install > Alpha 7 It was just a thought because Alpha 7 is current. I had bad slowdown after selection of additional packages, but network worked. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] openSUSE 10.3 alpha 7 KDE CD plus Factory
It is amazing. It has some rough edges, but it works so good that it will be here default for a while. *** Package management: Runs really fast. There is no need to keep "yast2 sw_single" opened longer than needed just to skip long repository scan. Show spoiler (to major): Text mode yast (GUI not checked) module "Additional Product Repositories": Missing progress bars or any indication that yast runs during repodata download. Screen stay on selection screen that doesn't accept any commands, and only indication that yast works is "top" in another terminal. This is not good as it looks like YaST went south. Minor: Missing keyboard shortcut in the module "Software Repositories" that will bring focus back to list of repositories after Alt-e (for edit). Shit-TAB will do the same, but it is not obvious as other shortcuts, and the same fuctionality is provided in (I guess) in "Additional Product Repositories". Minor: Screen goes black when time zone selection has to be done. Moving mouse brings GUI back. GUI configuration: Minor?: The sax2 never made dual screen configuration. Here it is a bit complicated as 2 different monitors are connected to 2 nvidia cards, one onboard and one added, but it worked in 10.2 with 32 and 64 bit, with nv dirver and nvidia copiled, so it should work in 10.3. The problem was that: sax2 -m 0=nv,1=nv generated xorg.conf that had one Device section: Section "Device" Driver "nv" EndSection and the other correct. The section Monitor listed monitor connected to another adpater. *** In first attempt the installation method was: Start installation with alpha 4 DVD and give as source local KDE iso. Ignore warning that this method can invalidate bug reports. It will some of early problems, the rest after new splash should be valid. 1) Change default partitioning proposal that was result of some detection, but not really good choice. If accepted it would format 10.2 / and /home. Which would be the most of damage that can be done. There was previous alpha installation that was not taken in consideration. In complex installations where installation programs can't find empty space it is better option to user determine what to do: - to select partition that should be used from the list in popup window, like it was years ago in text mode installation, and in that window, give option: - to go straight to Expert Partitioner; one that created 10 partitions on a hard disk probably has idea how to use it, or ask others for advice. 2) Change package selection adding some stuff that is probably default on DVD, but not on KDE CD. Annoyance was long dependency checking after each package added. Unchecking "Autocheck" speed up further selection. Proceed was very slow. Checking in console with "free" it was used 700 MB RAM out of 900. I didn't let it hang all night long, and after some time of network inactivity I rebooted. In second attempt I skipped package selection changes, and installation went fine. This time YaST used whole RAM. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Yast2 Alpha 5
On Sunday 05 August 2007 04:14:43 pm Donn Washburn wrote: > Key Group; > > I decided last night to try a "Yast2 > Software Management" on this > machine ($HOSTNAME=m1l). I deselected the Yast check dependencies every > time box due to the time it takes. I selected what I wanted and hit > "Accept". At that point Yast did a automatic dependency check. That is > where the problem came up - Yast failed to return. It did after about 8 > hours (last night to this AM) return an error stating that it was > looking for "$HOSTNAME=localhost". It appears the variable $HOSTNAME is > not being carried correctly. > > I have selected about 10 to 15 "Update Source" sites, Yast seems to be > happy with networking the URL. It goes out and finds the URL and > repodata plus subdirectories. Is that alpha 7? -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] New susegreeter / one-click help
On Saturday 04 August 2007 18:25, Benji Weber wrote: > Indeed, I think a clearly labled desktop icon is essential to return > to the greeter/support options. Many users are conditioned to close > all the clutter that opens on first start without much more than > glancing at it. Greeter resembles to splash screens or popups and it can be expected to be closed without reading. I guess that old idea from 9.x times with a desktop item that opens greeter again was good. > Would it be possible in any way to give the user a > visual cue on closing the window that it could be re-accessed through > the icon on the desktop? Something like KDE's minimise to tray warning > perhaps. I would also add offline help that is (can be) installed on the computer. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: Results of survey on use of proprietary software in openSUSE
On Saturday 07 July 2007 09:27, Andreas Jaeger wrote: > Michael Löffler wrote on opensuse-announce: > > Hi, > > > > the survey we did on proprietary software can be found here: > > http://en.opensuse.org/UX#Surveys > > > > It shows that we ship on the media some software which is hardly used > > (e.g. PlanMaker, SEPsesam etc.). Software which is hardly used we don't > > neet to ship on our media. Therfor my suggestion is to drop some software > > totally and offer some software only via ftp. To be discussed on > > opensuse-project. > > > > Best > > Michael > > > > PS: The question on TexLive was confusing. TexLive is open source but we > > wanted to know the use of it as it needs meanwhile so much space. > > So, Michael and myself *propose* the following actions: > > * Remove ARCAD completely since it does not work at all on x86-64 (see > bug #248873) It has also problem to recognize that it runs on dual screen which is, for the type of program, serious problem. > * Offer software that reached either > 80% on "Never" or less than 15 % > on "Often" + "Very often" only via *ftp* with 10.3. The following > software would be affected: > Planmaker > SEPsesam > > TeXlive > > Moneyplex falls also under this role, due to its usecase we suggest to > leave it on the media. > > What do you think? > > Andreas I would bring up again idea to create add on media or FTP snapshot. Add on can go with retail version and/or media that one can order separately online, FTP snapshot as online order only. It shouldn't be big problem to create media after online purchase. Many companies that produce small series of software use burners to produce media after customer order is confirmed. I don't know price details, but it shouldn't be big problem for SUSE too. The effort to squeeze as much as possible on limited media has it's cost too. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] opensuse-updater: "Check for any kind updates" option?
On Wednesday 04 July 2007 13:23, Rafał Miłecki wrote: > 2007/7/4, Carlos E. R. <[EMAIL PROTECTED]>: > > Anyway, I suppose that if the user has activated a dozen repos, he must > > be prepared for some confussion, but he surely must be interested in > > knowing what is new from all, sorted somehow. > > It depends what we want openSUSE to be. I installed openSUSE on > computers of a few people and I *had to* add them at least 3 > repositories. Packman, Guru and repo with "kadu" is "must be" for a > common user. Belive me, these ppl know quite nothing about systems and > they use openSUSE with 3 additional repositories. > > Method of managing updates is hard to create but is also hightly > needed. Lack of updaing applications from 3rd party repositories may > be really dangerous. There is difference between repositories. OpenSUSE are static except updates. The rest is dynamic and it is designed to keep system stable, just to provide new version of software. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] opensuse-updater: "Check for any kind updates" option?
Hi Benji, On Monday 02 July 2007 15:51, Benji Weber wrote: > It may be we need 3 policies: > > - Updates only (as default now) This is important for every user, and leaves system stable. > - Updates and version upgrades from same vendor as installed package > (e.g. if you install xine from packman you will get upgrades always > from packman, but not from an alternative vendor, fixes the bouncing > problem) This is fine for repositories that have no updates (fixes) like openSUSE, but offer newer version instead, which may require newer versions of dependencies, which can lead to avalanche of upgrade requests to satisfy newly created dependencies, and even if it is possible to find solution, after that system can't receive any security fixes trough regular updates. Some security holes will be patched by itself trough newer version of programs, some not. > - Upgrades from all vendors indiscriminately - like smart upgrade etc. > (For people who have the knowledge to fix their system if the package > manager does something stupid.) Even if package manager doesn't do anything bad, users will at some point by telling PM to ignore dependencies, and end result is for sure system in undefined state, which mean it can be anything from stable to fairly broken. > There are some strong opinions on this subject, It might be worth > re-opening the discussion though. It is opened, for anyone that has opinion ;-) -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Bug Day/s Lets Get it going.
Hi Ted, On Friday 01 June 2007 08:34, Ted Bullock wrote: > Now is probably the latest time to run this bug day thing if it is going > to have any sizable effect on 10.3. Alpha period is almost over (only > two alpha releases left to make changes in). > > Suggessted Wiki Node for Bug Triage Day > (http://en.opensuse.org/Bug:Triage_Day) Colon is in Mediawiki used to mark namespaces. Considering that our wiki is used for different purpose than Mediawiki software was developed for it is possible to introduce namespace Bug: and use for debugging related articles. To see this happen we need just few more votes on opensuse-wiki mail list. > I'd like to schedule this for next week/weekend > > -Ted I think this way: Any day is good with followups on above page used to prevent duplicate effort. Take ownership of few bugs, look around, mail to software developers, mail to bug reporter, solve what is possible by yourself, in short take care of what is possible to be solved. The example, how I would organize this is written on http://en.opensuse.org/Bug:Triage_Day ;-) In example list GIMP I know that one of bugs is already solved upstream ;-) > > Thoughts? Do you agree with proposal? -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Grub-entries, partitioning differences between 10.2 > 10.3.
On Thursday 24 May 2007 04:45, M9. wrote: > M9. schreef: > > M9. schreef: > >> Rajko M. schreef: > >>> On Wednesday 23 May 2007 14:05, M9. wrote: > >>>> M9. schreef: > >>>> > >>>> in the 10.2 grub is written: title openSUSE 10.3 (/dev/hdd7) > >>>> It is the second hdd, is called now /dev/sdb, or what? > >>>> then i know to call it /dev/sdd7, so it will work.. > >>>> > >>>> thnx > >>> > >>> Look in thread "kernel update brake the boot" by jdd from Tuesday. > >>> My second mail offers solution how to boot 10.3 from 10.2 boot loader. > >>> It works here. > >> > >> Ah, yes right..thnx ;-) > > > > Well, it is not quite the same, because i have to know how a second HDD > > is called now, take a look at my list, and see what i mean: /dev/sdb > > > > # Modified by YaST2. Last modification on Wed May 23 20:10:48 CEST 2007 > > default 0 > > timeout 8 > > gfxmenu (hd1,13)/boot/message > > > > title openSUSE 10.2 - 2.6.18.8-0.3 > > root (hd1,13) > > kernel /boot/vmlinuz-2.6.18.8-0.3-default root=/dev/hdd14 vga=0x31a > > resume=/dev/hdd13 splash=silent showopts > > initrd /boot/initrd-2.6.18.8-0.3-default > > > > title Failsafe -- openSUSE 10.2 - 2.6.18.8-0.3 > > root (hd1,13) > > kernel /boot/vmlinuz-2.6.18.8-0.3-default root=/dev/hdd14 vga=normal > > showopts ide=nodma apm=off acpi=off noresume edd=off > > initrd /boot/initrd-2.6.18.8-0.3-default > > Here it is: > > ###Don't change this comment - YaST2 identifier: Original name: openSUSE > > 10.3 (/dev/hdd7)### > > title openSUSE 10.3 (/dev/hdd7)=wrong : must be: /dev/sdb7 Title is for YaST and I find easier to use editor built in Midnight Commander, so in my case it doesn't matter if there is no YaST comment at all. > > kernel (hd1,6)/vmlinuz-2.6.21-8-default > > root=/dev/disk/by-id/scsi-SATA_ST380021A_3HV4E5VM-part8 vga=0x31a /dev/sda7 will do it. > > [resume=/dev/sdb14]= wrong must be /dev/sdb7] splash=silent showopts > > initrd (hd1,6)/initrd-2.6.21-8-default The resume= where is stored RAM snapshot. Usually it is swap partition, but in multiboot systems where swap is used for more of them it is not safe place for snapshot. ... > Now see if it is allright, thnx ;-) -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
