April 2008 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] beta1 does not umount rootfs at restart?
by Silviu Marin-Caea 27 Apr '08

27 Apr '08

Every time at boot, I see reiserfs replaying a lot of transactions with my user id. Can anyone confirm? --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 4

[opensuse-factory] Upgrade to 11.0beta1 - a bad experience
by Andras Mantia 26 Apr '08

26 Apr '08

Hi, I decided last evening to update my 10.3 system to 11.0 beta1. First of all, I have no problem running unstable versions of software, I use the KDE svn regularly and used (open)SUSE's previous releases starting from late alpha/beta state. Still, this 11.0 beta1 was a bad experience. Here are the problems I saw (with bug numbers); 1) first of all, the installer failed to find a repository on the DVD. I found that if I give dvd:///devices=/dev/hdc it will work. Funny, that /dev/sr0 also works from the console, but not from yast. Bug 383896. 2) so after I found how to go forward, I tried to update the system. IT failed to find and mount my partitions, I had to give the partition type (vfat, ext3) manually. Bug 384133. 3) After this step the Installation media showed no available repositories. I did not file a BR for this, but I can do if it makes sense. 4) Upgrade started, the total percentage went quickly to 100%, sat there for a while and fall back to 0% and remained there until the upgrade finished. Bug 384134. 5) System was rebooted, complains that fsck failed for /dev/sdb4. Turned out that the fstab is wrong that should be /dev/sda4. Bug 384133 (again). 6) corrected the fstab, rebooted the system (ctrl-d). And here came the disaster. Instead of getting a grub menu, the pc kept rebooting itself forever. So when it started from boot from the disk, it rebooted. No error, nothing on the screen, just reboot forever. Bug 384136. 7) Tried to fix the bootloader both with rescure disc, repair system and manually. No luck, same symptoms, so I had to reinstall the system over the broken installation, whatever will happen because of this. Bug 384136. 8) So the reinstall... After getting through the issue 1) I choose to install over the existing system. I had to use the expert partitioner, otherwise it would format two of my partitions that held data, not the old OS, and confirm that I really want to overwrite an existing system. I saw a visual bug: the percentage used in the progressbar is white on white, so it is not visible until around 50% is reached. Bug 384137/ 9) Reboot, yast starts, and gives an error: "No workflow defined for this installation mode" and exits. So I remained with an unfinished installation. Bug 384138. 10) I noticed a warning on boot: java: serif (and sans serif) fonts not found for Japanese/Chinese languages. I don't use those languages, so I did not report as a bug, but I mention it here. 11) during installation I was prompted to enter an user name, password, etc. When first time kdm start I tried to log in as that user (an user that already existed under 10.3, so it had its home dir during install time). I couldn't, and I found it why: the user was not created. I had to create it again manually. May be because of 9). Bug 384140. 12) Display was not configured, I ended up with an 1024x768@60Hz. Might be again because of 9). Fonts are ugly. :( Now I'm trying to make things work and look nice, as at least I can boot in the system. After hours spent fixing it... Andras -- Quanta Plus developer - http://quanta.kdewebdev.org K Desktop Environment - http://www.kde.org

2 3

[opensuse-factory] Firewall Configuration - Allowed Services List
by Gabriel 26 Apr '08

26 Apr '08

Why in the Service to Allow List are not listed HTTP and HTTPS ? I know this is really a minor thing, and it is possible to allow it by adding the ports in the advance section. For the other hand, are this two services allowed by default ? If so, what if I want to block them? -- Kind Regards --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 2

[opensuse-factory] aborting Configured Software repositories also abort package manager
by Gabriel 26 Apr '08

26 Apr '08

I'm in the Package Selection dialog (yast2-gtk), open the Configured Software Repositories dialog. If I click OK, then the Package Selection dialog appears again (which is fine), if I click Abort, the dialog is closed (both). Is this the expected behavior ? -- Kind Regards --------------------------------------------------------------------- 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] Repo priorities
by Volker Kuhlmann 26 Apr '08

26 Apr '08

The repo priorities are really useful, but wouldn't it make more sense to put the default at 50 than at 99, when the valid range is 1-99? Volker -- Volker Kuhlmann is list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me. --------------------------------------------------------------------- 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] Desktop Selection
by Stephan Kulow 26 Apr '08

26 Apr '08

Hi, I spent some hours today to refresh my ycp knowledge: https://bugzilla.novell.com/attachment.cgi?id=209654 This is how we want to go into beta2. Greetings, Stephan -- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

28 73

[opensuse-factory] Fwd: [opensuse] OpenSuse 10.3 and mod_php5 installation does not execute index.php
by Andreas van dem Helge 25 Apr '08

25 Apr '08

---------- Forwarded message ---------- From: Andreas van dem Helge <joakimsen(a)gmail.com> Date: Fri, Apr 25, 2008 at 7:13 PM Subject: Re: [opensuse] OpenSuse 10.3 and mod_php5 installation does not execute index.php To: Marcel Ruff <mr(a)marcelruff.info> Make sure the file file /etc/apache2/conf.d/php5.conf does exsist and that it contains the line (and is not commented out) AddHandler application/x-httpd-php .php If that doesnt work try to tail -f the files in /var/log/apache2 Also each time you edit the apache configuration you need to issue the command # service apache2 reload On Fri, Apr 25, 2008 at 7:10 AM, Marcel Ruff <mr(a)marcelruff.info> wrote: > Hi, > > i have upgraded from 10.1 to 103 and now > suddenly the Apache2 PHP module does not work anymore. > (apache2-2.2.4-70.4 apache2-mod_php5-5.2.5-8.1) > > If i want to access index.php in my firefox > it wants to *download* the file instead of processing > it server side. > > In /etc/apache2/httpd.conf if have > Include /etc/apache2/conf.d/php5.conf > (which has DirectoryIndex index.php) > > # httpd2 -M > Loaded Modules: > ... > php5_module (shared) > > > How can i approach this? > > Thank you > Marcel > > -- > Marcel Ruff > http://www.xmlBlaster.org > http://watchee.net > Phone: +49 7551 309371 > > -- > To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > For additional commands, e-mail: opensuse+help(a)opensuse.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

[opensuse-factory] Why is a bug in Factory yast2-qt-pkg dismissed as not being in beta1?
by Dave Plater 25 Apr '08

25 Apr '08

Hi, I filed bug 382202 thinking I was doing good in alerting the developers of a problem that could cause future problems. I have an up to date factory system and filed the bug as being in factory. I am obviously confused as to how to file a bug because it is marked as resolved with this comment :- "Really, I don't care what any random FACTORY snapshot does. There is no way to support FACTORY on that level. Please test a released version like Beta1." Unfortunately I do not have bandwidth, until next month, to download Beta1 so I do not know which yast2 version is in factory. Is it pre yast2-qt-pkg-2.16.37 with dummy version tags, The bug has been there for quite a while and I do not have time to trace which version it came from but it definitely exist in yast2-qt-pkg-2.16.36. It is not easy to report a bug, trying to do so in words that would be clearly understood and upload necessary logs. I thought I was doing my bit for the opensuse community. Am I lead to believe that reporting bugs in factory is no longer wanted? Your reply appreciated. Dave Plater --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 5

[opensuse-factory] Removing multiple version packages
by Felix Miata 25 Apr '08

25 Apr '08

Is there some utility to find and remove packages that had upgrade failures that left both old and new versions both installed? My last smart upgrade gave lots of no such file messages while executing, and now I see with 'rpm -qa | sort' a lot of multi version packages are installed. -- "Either the constitution controls the judges, or the judges rewrite the constitution." Judge Robert Bork Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 2

[opensuse-factory] Question concerning choices..
by Oddball 25 Apr '08

25 Apr '08

Hi, I just wanted to update newest factory. The solver wanted me to make choices about the installation of pkgs. If the solver asks not to install a newer pkg, because of unsolvable deps, does that mean: The old version is going to be removed, without being updated?, or, The old version stays installed, but does not get updated? I ask this because for some reason some pkgs were uninstalled whch i was not aware of, and never installed again, which showed later, when i had to reinstall the pkgs manualy. As illustration please see the attachment... -- Enjoy your time around, Oddball (Now or never...) OS: Linux 2.6.25-rc8-12-default x86_64 Current user: oddball@AMD64x2-sfn1 System: openSUSE 11.0 (x86_64) Alpha3 KDE: 4.00.68 (KDE 4.0.68 >= 20080402) "release 6.4" #### YaST2 conflicts list - generated 2008-04-25 13:48:10 #### niets levert libgpod.so.2()(64bit) nodig door amarok-1.4.9.1-18.1.x86_64 [ ] amarok-1.4.9.1-18.1.x86_64 niet installeren niets levert libtalloc.so.1()(64bit) nodig door libsmbclient0-3.2.0-2.x86_64 [ ] libsmbclient0-3.2.0-2.x86_64 niet installeren niets levert libtalloc.so.1 nodig door libsmbclient0-32bit-3.2.0-2.x86_64 [ ] libsmbclient0-32bit-3.2.0-2.x86_64 niet installeren niets levert libtalloc.so.1()(64bit) nodig door samba-3.2.0-2.x86_64 [ ] samba-3.2.0-2.x86_64 niet installeren niets levert libtalloc.so.1()(64bit) nodig door samba-client-3.2.0-2.x86_64 [ ] samba-client-3.2.0-2.x86_64 niet installeren niets levert libtalloc.so.1 nodig door samba-client-32bit-3.2.0-2.x86_64 [ ] samba-client-32bit-3.2.0-2.x86_64 niet installeren akonadi-4.0.69-26.1.x86_64 vereist libakonadiprotocolinternals.so.4()(64bit), Maar aan deze eis kan niet voldaan worden verwijderde leveranciers: libakonadi4-4.0.70-3.3.x86_64[@System] geen installeerbare aanbieders: libakonadi4-4.0.69-6.x86_64[Factory] libakonadi4-4.0.69-6.x86_64[Factory1] [ ] De volgende acties zullen uitgevoerd worden: deïnstallatie van kdepim4-4.0.69-26.1.x86_64 deïnstallatie van kde4-kmail-4.0.69-26.1.x86_64 deïnstallatie van kde4-korganizer-4.0.69-26.1.x86_64 deïnstallatie van kde4-kaddressbook-4.0.69-26.1.x86_64 deïnstallatie van kdepim4-wizards-4.0.69-26.1.x86_64 deïnstallatie van kde4-knotes-4.0.69-26.1.x86_64 deïnstallatie van kde4-akregator-4.0.69-26.1.x86_64 kdepim4-4.0.69-26.1.x86_64 vereist libakonadi-kcal.so.4()(64bit), Maar aan deze eis kan niet voldaan worden niet-installeerbare aanbieders: akonadi-4.0.69-12.x86_64[Factory] akonadi-4.0.69-12.x86_64[Factory1] [ ] De volgende acties zullen uitgevoerd worden: deïnstallatie van kde4-kontact-4.0.69-26.1.x86_64 deïnstallatie van kde4-kaddressbook-4.0.69-26.1.x86_64 deïnstallatie van kdepim4-wizards-4.0.69-26.1.x86_64 deïnstallatie van kde4-korganizer-4.0.69-26.1.x86_64 deïnstallatie van kde4-kmail-4.0.69-26.1.x86_64 deïnstallatie van kde4-knotes-4.0.69-26.1.x86_64 deïnstallatie van kde4-akregator-4.0.69-26.1.x86_64 [ ] kdepimlibs4-4.0.71-7.1.x86_64 niet installeren kdepim4-4.0.69-26.1.x86_64 vereist libakonadi-kcal.so.4()(64bit), Maar aan deze eis kan niet voldaan worden niet-installeerbare aanbieders: akonadi-4.0.69-12.x86_64[Factory] akonadi-4.0.69-12.x86_64[Factory1] [ ] kdebase4-runtime-4.0.3-12.5.x86_64 niet installeren [ ] De volgende acties zullen uitgevoerd worden: deïnstallatie van libkdepim4-4.0.69-26.1.x86_64 deïnstallatie van kdepim4-wizards-4.0.69-26.1.x86_64 deïnstallatie van kde4-korganizer-4.0.69-26.1.x86_64 deïnstallatie van kde4-kmail-4.0.69-26.1.x86_64 deïnstallatie van kde4-knotes-4.0.69-26.1.x86_64 deïnstallatie van kde4-akregator-4.0.69-26.1.x86_64 #### YaST2 conflicts list END ###

1 2