May 2008 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] HDD Recognition in Beta3
by Stefan Kunze 26 May '08

26 May '08

Hi, i installed the Beta 3 (x86_64) in a PC with 2 SATA HDD and 1 IDE Drive. The Installation should be a dualboot with 10.3 and 11.0Beta3. Unfortunately the HDD are recognized in a different way. 10.3 SATA 1 - sda SATA 2 -sdb IDE - sdc 11.0 Beta3 - IDE - sda SATA1 - sdb SATA2 -sdc After the installation i have Problems booting the 10.3 because GRUB is looking for the wrong partitions. Should i report a bug or is this intended behavior? Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 7

Re: [opensuse-factory] 11.0 Beta3 gets different IP address from DHCP server
by Herbert Graeber 26 May '08

26 May '08

On Sunday 25 May 2008 21:07:03 Mark Gray wrote: > It appears that the DHCP client for 11.0 Beta3 consistently gets a > different IP address than 10.2 does from the DHCP server in my DSL > router. If this is not a bug, it might be well to mention this in the > release notes, because I am probably not the only one who uses > /etc/hosts to configure their local network. I hesitate to report > this as a bug because there are easy enough ways around this -- just > changing my /etc/hosts files being the easiest. Do not use DHCP and fixed IP-Addresses if possible. This isn't a good mix. DHCP servers usually are able to assign fixed IPs based on the MAC address of the network card. But the ones in DSL router usually don't have this option. The easiest solution for a small home network would be to use DHCP and let it do the whole configuration for you. There should be no need to make changes in /etc/hosts. Cheers, Herbert --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 6

[opensuse-factory] ALERT: Confirm this re 11.0 Beta3 current upgrades
by Basil Chupin 26 May '08

26 May '08

Confirm this for yourself. In recent messages it has been indicated that there is a problem with the kernel which was upgraded in the past (?)few days when zypper goes to upgrade 11.0 Beta3. Not so as far as I am concerned. The problem lies somewhere else. And this is what I am asking you to be aware of and to confirm. A short while ago I re-installed 11.0 Beta3 after trying a suggestion to fix the non-boot problem of 11.0 Beta3 after the recent upgrades by doing, amongst things, "rm /.buildenv and calling mkinitrd". Other suggestions also failed, so I decided to re-install 11.0 Beta3 from the DVD, but after installing it I wasn't going to allow zypper or smart to upgrade the kernel to 2.6.25.4-2 which is claimed to be the the cause of all the problems. Well, it's not the kernel ...25.4-2. Something else in the Factory to upgrade 11.0 Beta3 is causing the big-time problem. If you install 11.0 Beta3 to test it then do not allow it to be upgraded by zypper. (Just for the record, the version I have installed - and before the latest upgrades it was working fine - is the 32-bit version and I was using KDE4 to see what it looked liked.) Ciao. -- Vulgar language is the linguistic crutch of inarticulate brain-dead. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 7

[opensuse-factory] startx script no longer working
by Antenore Gatta 26 May '08

26 May '08

After the last X server upgrade the X server start only with xdm script and not with startx. I add "set -x " to the script for debugging purpose and this is the ouput. + xinit /etc/X11/xinit/xinitrc -- /usr/bin/Xorg :0 /etc/X11/xinit/xserverrc -auth /home/tmow/.serverauth.3211 -nolisten tcp Unrecognized option: /etc/X11/xinit/xserverrc Does this depend on my installation? Or is it a "factory" bug? Any idea on how to solve it? Thanks in advance. Best regards Antenore. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

[opensuse-factory] Beta 3 shows won't update on Battery?
by Larry Stotler 26 May '08

26 May '08

Well, this is a new one. I've got Beta3 installed on my Thinkpad 390X. It's got a really long life battery. It's currently at about 60% remaining. When I restored the kde taskbar updater, I got this message: Unable to check whether updates are available. The system is on battery. Please connect a power supply. Ok, why is this? I'm not "allowed" to update if I am running on battery? Shouldn't that be MY choice??? Thanx --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 4

[opensuse-factory] -factory (May 24) "zypper update" grabs ~100%cpu and cycles endlessly
by snowcrash+opensuse 25 May '08

25 May '08

a netinstall using 24 May's -factory boot.iso goes smoothly. after system boot, uname -a Linux server 2.6.25.4-2-default #1 SMP 2008-05-16 20:46:39 +0200 x86_64 x86_64 x86_64 GNU/Linux a check of zypper -vv update with zypper repos # | Alias | Name | Enabled | Refresh --+-----------------------+---------------------------+---------+-------- 1 | factory-non-oss | Main Repository (NON-OSS) | Yes | Yes 2 | factory | Main Repository (OSS) | Yes | Yes 3 | factory-debug | Main Repository (Debug) | No | No 4 | openSUSE-FACTORY 11.0 | openSUSE-FACTORY 11.0 | No | No 5 | updates | Updates for 11.0 | Yes | Yes starts by retrieving repo media correctly, then loops @ ~ 100% cpu Verbosity: 2 Initializing Target Checking whether to refresh metadata for Main Repository (NON-OSS) Downloading: http://download.opensuse.org/distribution/SL-Factory-non-oss/inst-source-ex… [done] Downloading: http://download.opensuse.org/distribution/SL-Factory-non-oss/inst-source-ex… [done] Downloading: http://download.opensuse.org/distribution/SL-Factory-non-oss/inst-source-ex… [done] Downloading: http://download.opensuse.org/distribution/SL-Factory-non-oss/inst-source-ex… [done] Downloading: http://download.opensuse.org/distribution/SL-Factory-non-oss/inst-source-ex… [done] Downloading: http://download.opensuse.org/distribution/SL-Factory-non-oss/inst-source-ex… [done] Downloading: http://download.opensuse.org/distribution/SL-Factory-non-oss/inst-source-ex… [done] Downloading: http://download.opensuse.org/distribution/SL-Factory-non-oss/inst-source-ex… [done] Downloading: http://download.opensuse.org/distribution/SL-Factory-non-oss/inst-source-ex… [done] Downloading: http://download.opensuse.org/distribution/SL-Factory-non-oss/inst-source-ex… [done] Downloading: http://download.opensuse.org/distribution/SL-Factory-non-oss/inst-source-ex… [done] Downloading repository 'Main Repository (NON-OSS)' metadata [done] Building repository 'Main Repository (NON-OSS)' cache [done] Checking whether to refresh metadata for Main Repository (OSS) Downloading: http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/content [done] Downloading: http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/media.… [done] Checking whether to refresh metadata for Updates for 11.0 Downloading: http://download.opensuse.org/update/11.0/repodata/repomd.xml [done] Reading installed packages... where, checking @ console, top shows zypper still grabbing ~ 100% cpu after 46 mins ... top - 09:16:00 up 38 min, 2 users, load average: 0.99, 0.81, 0.67 Tasks: 81 total, 4 running, 77 sleeping, 0 stopped, 0 zombie Cpu(s): 27.4%us, 22.8%sy, 0.0%ni, 49.8%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 8133060k total, 4207828k used, 3925232k free, 11396k buffers Swap: 524280k total, 0k used, 524280k free, 3997392k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 3191 root 20 0 105m 21m 7016 R 96 0.3 46:23.18 zypper ... trying again with, zypper ref -f All repositories have been refreshed. zypper -vv update makes no difference -- still loops endlessly. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

RE: [opensuse-factory] Beta 3 shows won't update on Battery?
by Putrycz, Erik 25 May '08

25 May '08

Agreed, a warning would be better. > -----Original Message----- > From: Larry Stotler [mailto:larrystotler@gmail.com] > Sent: May-25-08 2:08 PM > To: Putrycz, Erik > Subject: Re: [opensuse-factory] Beta 3 shows won't update on Battery? > > On Sun, May 25, 2008 at 1:38 PM, Putrycz, Erik > <Erik.Putrycz(a)nrc-cnrc.gc.ca> wrote: > > Makes sense to me, if the battery is low or is depleting quickly then > > updating your system may leave the computer on an unstable state. > > I bet that zypper sucks seriously the battery (I/O + cpu). > > Actually, it doesn't. Like Andreas pointed out recently: zypper is NOT > ZMD > > I was able to run BOTH YOU and zypper from the command line with no > issues. I had 60% battery remaining. Neither took more than 5 > minutes to refresh or check for new updates. > > My complaint is that it should WARN you that you are on battery power > and then ASK if you still wish to proceed. It should be up to the > user to decide, not the program. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] using firefox over ssh -X
by Dominique Leuenberger 25 May '08

25 May '08

Hi, I experiance a strange and actually very annoying thing: I ssh -X to my other box (openSUSE 10.2) from my Factory box. I'll call the 10.2 install PC, and the Factory NB. So, I ssh -X from the NB to the PC. I can start all sort of X-Applications on PC and have the screen pointing on NB. Exactly what I want to happen. rpm -q MozillaFirefox on PC shows it's version 2.x.x.x installed if in a terminal on PC (connected using ssh -X) I type firefox, as requested, a firefox is showed on my display on NB. BUT: It's the locally installed FF 3.0 from the factory installation on my NB. this is NOT what I want to happen. If I'd want THIS, then I'd NOT ssh to the other box. There IS a reason for me to do so (beyond the scope of this mail). Can you confirm that this is happening? Is this supposed to happen? If yes: Why? If no: already a bug filed or shall I do so? I'm not sure if it's rather a factory issue or a 10.2 issue, or FF in general. Dominique --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 2

[opensuse-factory] proposal to drop the greeter for 11.1
by Jakub Steiner 25 May '08

25 May '08

Hi. I'd like to propose dropping the greeter dialog. If it's too late for 11.0, then at least for 11.1. I consider it to be just a nag screen similar to the welcome page in Windows 95(?) that nobody actually reads and it just gets in the way. For more info see bugs #386485 and #386486. -- Jakub Steiner <jimmac(a)gmail.com> http://jimmac.musichall.cz --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

7 6

[opensuse-factory] How do changed & new modules enter 'openSUSE'?
by Linda Walsh 25 May '08

25 May '08

So how do changed and new modulels get into the openSUSE factory tree? Is there any control on how packages are added to the tree both at its creation and during its pre-release testing? I'm wondering how a package gets checked into the tree that doesn't appear to have a source that builds? To developers make changes then check them into the openSUSE tree to be 'tested' by the community or do developers ensure they compile before checking them in? Maybe the developer's have something different in their environment than I'm using? Else I don't see how the openssh-keyconverter sub-util in the openssh-5.0p1 source package would not block re-generation of the RPM from the source RPM... ??? --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 8