March 2007 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Automatic hardware detection and configuration.
by David Bolt 06 Mar '07

06 Mar '07

After numerous requests for information on what to do when replacing a graphics card and booting to end up with a black/blank screen, it's made me wonder: Why on earth isn't SUSE maintaining a list of all the devices attached, performing a check each time it boots, and asking the user if they'd like to configure any new devices that have been added? For a lot of devices it does ask about configuring them once you're at the desktop. The problem with this is that for a graphics card, that's a bit too late. It should take a matter of a couple of seconds, if that, to query all the device IDs attached to the PCI bus. If it finds a new device, it can then look up to see what type of device it is, whether one of the other devices has been removed and if the new card is of the same type, and then, if required, flag it to be configured. When a graphics card is no longer present, but another one is found, offer the choice to either configure it now or later. Where the user puts off configuring the card, put a flag against the card so same choice is presented during the next boot. What's more, in the case of a graphics card, it could then force a boot into run-level 3 so as to prevent the "black screen" problem. That way the user can either reboot the system, or log in at a console, so they can perform the configuration. It would then be a case of adding a small check to sax, or whichever YaST module is used to perform this configuration, so that it checks to see if the flag is present. If the flag is there, once the configuration is complete, remove the flag and the user isn't asked about this again. Regards, David Bolt -- Member of Team Acorn checking nodes at 50 Mnodes/s: http://www.distributed.net/ RISCOS 3.11 | SUSE 10.0 32bit | SUSE 10.0 64bit | openSUSE 10.2 32bit RISCOS 3.6 | SUSE 10.1 32bit | SUSE 10.1 64bit | openSUSE 10.2 64bit TOS 4.02 | SUSE 9.3 32bit | | openSUSE 10.3a1 32bit --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 3

[opensuse-factory] OpenSUSE, bugs and some considerations
by Alberto Passalacqua 06 Mar '07

06 Mar '07

After quite a long time, I decided to do some considerations on the status of OpenSUSE as a community and as a distribution, starting from everyday experience. I'll start from some bug reports, which affects me directly and which have been waiting for a solution for a long time since the release of 10.2 final. They're only examples, you can find many others on bugzilla. * main-menu Hangs https://bugzilla.novell.com/show_bug.cgi?id=240727 * Banshee doesn't recognize ipod https://bugzilla.novell.com/show_bug.cgi?id=215301 * yast is still unable to list printers https://bugzilla.novell.com/show_bug.cgi?id=240727 * Gimp can't print: https://bugzilla.novell.com/show_bug.cgi?id=230887 which sends to bug #226710, which is not accessible. The main menu bug is a blocker and it's really strange no-one in the development team noticed it during the development stage. A patch was recently released on bugzilla, but it only partially solves the problem for some user and does nothing for others, which indicates the issue is quite serious. The helix-banshee bug is really a mystery. It's there since beta stage, but no solution is coming. It seems that recompiling a package is impossible at SuSE. The yast-printer bug seems solved, but I still can't see my network printers in yast. I've just reopened the bug. The gimp problem was marked as duplicate of a FIXED bug, but this one links to an inaccessible report. In my opinion these issues are serious and the lack of consideration they receive is very disappointing considering that solutions were promised in many occasions, and they're not provided in an acceptable time (~3 months after the official release). The bugzilla is full of other examples of problems which could be easily solved in a short time, but never received a comment. There are many easily fixable bugs with many comments and no solution. OpenSUSE, in the opinion of most users, is the mean through which users know SUSE, evaluate it and start using it. There are many users who approached to SUSE through OpenSUSE to evaluate the enterprise line too and to see how the team/community works. I don't think OpenSUSE is giving a good image of itself neither as a distribution nor as a team/community. The quality of the distribution is lower then in the past due to the choice to release too quickly and the lack of testing. The issue of testing was addressed by adding a beta release for 10.3, but I don't think the team should expect significant improvements from testing provided by users if * a pre-testing is not done in-house. * no guidelines are given to community testers. * no consideration is given to their reports. Especially the pre-testing is important in my opinion, because community users often don't have enough experience and knowledge, or they don't test the distribution for enough time. Guidelines would help us a lot to look for problems in specific areas and to test things more carefully Of course all this makes sense only if reports will be considered in time and seriously, hopefully before release ;-) A final comment, to conclude this already long e-mail, is about the GNOME-KDE question (seriously, for once). Gnome users (not only me, there are a few, but there are) are quite bored to see GNOME considered the de-facto second choice of the distribution because it is less tested than KDE and less maintained. Now, I understand many developers at SUSE love KDE and that SUSE was a KDE based distribution. But in the past at least it was coherent: KDE was the default and SUSE was really optimised for KDE. It was so evident that GNOME appeared out of place, and it was OK. A user who chose SUSE knew it was a KDE distribution. Today SUSE has no defaults, so a user thinks he can choose what he likes more, but it's not that way. In openSUSE 10.2 it is so evident a lot of the efforts were put in creating a KDE which is better than GNOME. Examples are many: from the new kickoff menu, which was developed faster than the gnome main-menu and has none of the issues of the gnome one, to the opensuse-updater, which has no equivalent in GNOME (I know one is coming for 10.3). Both DE should be considered as alternatives, not as rivals. I do myself this mistake, I know. But it's really annoying to read "Use KDE" or "Use a KDE app" when a user asks for help about GNOME. Moreover GNOME is the default on SLED, and having a low quality GNOME on openSUSE doesn't help to give a good image to potential customers. If things are going to stay as they are at the moment, I would really prefer a strong but clear decision to make openSUSE again a KDE based distribution instead of having a two-DE distribution only in appearance. Sorry for the long message. Regards, Alberto --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

17 63

Re: [opensuse-factory] OpenSUSE, bugs and some considerations
by Alberto Passalacqua 05 Mar '07

05 Mar '07

Il giorno sab, 03/03/2007 alle 13.05 -0600, Rajko M. ha scritto: > Well, both is an extension, just one is fine for fast responses, and the other > allows more asynchronous work that will group more people that might be not > familiar with bugzilla and/or IRC, can't attend at the times that are > scheduled, but still can help. Sorting out to one medium will do just > opposite from what is wanted. > Yes and no. The goal is to work together on specific, serious problems. So doing asynchronous work seems pointless to me. > I can use IRC in the most basic form. > That and time constrains will prevent me from attending antibug fest. This is sad. Would a forum be better? > What is the best can be decided on the run. I don't see the need to insist on > one communication channel that fits for some purposes, and not for the other. In my opinion with multiple communication channels we risk to have a lot of duplicates and a significant loss in time/efficiency. For example different groups working on the same problem on IRC, on ML, by mail... Regards, Alberto --------------------------------------------------------------------- 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] The stanby option works outstanding on 10.2 x86_64 :-)
by M9. 05 Mar '07

05 Mar '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As subjectline, thnx for fixing this properly... - -- Have a nice day, M9. Now, is the only time that exists. OS: Linux 2.6.18.2-34-default x86_64 Huidige gebruiker: monkey9@tribal-sfn2 Systeem: openSUSE 10.2 (X86-64) KDE: 3.5.5 "release 45.2" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFF7B2IX5/X5X6LpDgRAnmQAKCjHQISdhJDav5SVhQdpTnwCGh6+wCgwFR0 nio4YpL5X4maWiWtkTSRmNs= =QEGk -----END PGP SIGNATURE----- --------------------------------------------------------------------- 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] Where can I find the package nss-mdns?
by Juan Erbes 05 Mar '07

05 Mar '07

I will update avahi and libgphoto2 to verify if the bug 239719 was resolved (as it appear in bugzilla), and then I update avahi and the dependents packages, but I could'nt find the package nss-mdns required by avahi-0.6.17-3.i586, because I got: # rpm -Uvh avahi-0.6.17-3.i586.rpm error: Failed dependencies: nss-mdns is needed by avahi-0.6.17-3.i586 Where can I find the package nss-mdns? Thanks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 7

[opensuse-factory] Recent factory updater
by Donn Washburn 05 Mar '07

05 Mar '07

Folks be aware of the fact the most recent update to this machine in attempt to just get audio files has removed about all of the development packages without replacing them. xine-lib will no longer compile due to missing gnome libs which were found to be missing the correct links to /usr/lib. So far about every required libfile.ls is missing. So, far taglibs, libdaemon and libdaemon-gtk.so are missing Advice - be very careful if you use the SuSE updater. Oh yea - the updater even screwed up Yast - it was looking for a .so.4 lib which was missing. I fixed the by linking it to the only file which was a .so.3 -- 73 de Donn Washburn 307 Savoy Street Email: " n5xwb(a)hal-pc.org " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 Did you know? The transistor was invented by three white men. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 3

Re: [opensuse-factory] OpenSUSE, bugs and some considerations
by M9. 05 Mar '07

05 Mar '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 jdd schreef: > M9. wrote: > >> You mean like skype or ekiga? > > not even... in Frances adsl is given through "boxes" (the older is > "freebox", and phone with this is IP phone, free to many countries > (fixed phones) > > jdd > > Yes, IP-phone, it begins to become popular around these region also... But I must say, that i myself still do not use them... But they get offered, might consider to take one, for future use... On the other hand, i believe that the intention to do something 'collective', is great! And knowing this is happening, and be able to join, will make it even greater... Maybe using a message board specific for the purpose? Or as Carlos suggested: the Novel Private Newsserver? (if permitted?) - -- Have a nice day, M9. Now, is the only time that exists. OS: Linux 2.6.18.2-34-default x86_64 Huidige gebruiker: monkey9@tribal-sfn2 Systeem: openSUSE 10.2 (X86-64) KDE: 3.5.5 "release 45.2" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFF7AILX5/X5X6LpDgRAhntAJ9ojI/5feX7VcMzvr1MSmSbbAo6qQCdGETV ofq2TBjr/aygWGJuaqZOM28= =hOQ6 -----END PGP SIGNATURE----- --------------------------------------------------------------------- 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] kernel update
by Chema 04 Mar '07

04 Mar '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, Since last month I upgrade/update my system with smart 3 or 4 times,but my kernel(you can see on my signature)is the same... There are any problem with kernels now? Thanks and regards __ Chema Ollés Usuario Linux: #198057 Linux 2.6.20-rc7-2-default #1 SMP Thu Feb 1 13:34:44 UTC 2007 i686 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.1rc1 (GNU/Linux) iD8DBQFF6s06m5lTdgS9W18RAmIFAKCbbrvf/vK6Xeq1gQT6lUi0QLdH5gCggC9+ n/7DFLCnUbs2+Flo7nBKuLQ= =NNMD -----END PGP SIGNATURE----- --------------------------------------------------------------------- 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] 33 1/3RPM to wav
by Donn Washburn 04 Mar '07

04 Mar '07

Hey Group; I am about to embark on a job helping someone to get a 33 1/3 RPM old audio record (as if you could find a new one. Question number one is - I don't recall a true line level stereo input on PC sound card. I do recall a AUX/CD stereo connector on the card or a 1/8" stereo Line IN (at least I would like to see one) that can accept a line from a HIFI type amp stereo line out. From there I would have a linux mixer (qamix, kmix or the like) play back over the speakers that signal. From a mixer I could create a audiofile.wav. Question #2 Anyone have knowledge from that point? I would ultimately like to burn the audiofile.wav to a CD Even better capture the music on www.sky.fm/smoothjazz which amarok does so well. -- 73 de Donn Washburn 307 Savoy Street Email: " n5xwb(a)hal-pc.org " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 Did you know? The transistor was invented by three white men. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 2

Re: [opensuse-factory] OpenSUSE, bugs and some considerations
by Christian Jäger 03 Mar '07

03 Mar '07

Marcus Meissner wrote: > > Il giorno ven, 02/03/2007 alle 23.05 +0100, Richard Bos ha scritto: > > > Op vrijdag 2 maart 2007 22:52, schreef Alberto Passalacqua: > > > > * main-menu Hangs > > > > https://bugzilla.novell.com/show_bug.cgi?id=240727 > > > > > > This bug number is incorrect. What is the right one? > > > > I'm sorry. I pasted the wrong link. Here's the right one: > > > > https://bugzilla.novell.com/show_bug.cgi?id=229190 > > This bug does not even seem to be fully evaluated yet... > > A bit of insistence of the bug reporter is _always_ helpful, in > any opensource scenario. > > Ciao, Marcus It would help a lot IMHO if someone went over the open bugs and had a look at least at the CRITICAL ones in order to determin whether any immediate action is necessary. I mean, gnome-main-menu is extremely bothersome, it really make working an unpleasant experience. But still, it is not serious. How come, on the other hand, that really critical bugs like the following one go completely unrealized although several users have confirmed it? Bug 231256 - Zen-updater's repositories are lost after boot https://bugzilla.novell.com/show_bug.cgi?id=231256 Other than that I'm tremendously enjoying openSUSE and just hope it tackles some of the main issues in 10.3; like the aforementioned gnome-main-menu annoyance and ZMD-problems. Thanks, Christian --------------------------------------------------------------------- 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] Heads up for 2.6.21
by Sid Boyce 02 Mar '07

02 Mar '07

On openSUSE 10.2 (KDE-3.5.5) and 10.3 Alpha (KDE-3.5.6), I've encountered a problem with vanilla 2.6.21-rc1 up to 2.6.21-rc2-git1. KDE is setup not to require a password to unlock the screen, but it asks for password. When given the password, it unlocks, but kwin, kicker, klauncher and may be other kdeinit stuff have died with no errors reported. Doing straces do not show errors. If I start those 3 from the command line, everything comes back except the desktop icons and the next lock will repeat the same sequence. The workaround I've found is to move kdesktop_lock out of /opt/kde3/bin, everything comes back intact when a key is pressed or the mouse is moved after the screen is blanked. NOTE, this is just a heads up, so no action is expected. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- 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] [RFC] autofs5
by Matthias Koenig 02 Mar '07

02 Mar '07

Hi, I would like to update to autofs5. autofs5 is a major rewrite of autofs4 and while there might still be some problems I hope it is stable enough. Fedora is already shipping this. We really should have it in Code 11, so I want this to be tested in openSUSE 10.3. Most of the new features enhance the functionality to be more compliant with industry standard. For testing purposes I already provide packages for factory and 10.2 in the buildservice: http://build.opensuse.org/project/show?project=home%3Amakoenig Here is a list of changes: Differences v4 vs. v5 --------------------- - Master map is now read and parsed by the `automount' daemon - The master map default is "auto.master" and nsswitch is used to locate it. The line "+auto.master" has been added to the default installed "/etc/auto.master" to ensure that those using NIS will still find their master map. This is in line with other industry automount implementations. - The `automount' daemon is now a multi-threaded application - `autofs' filesystem mounts only appear in /proc/mounts and not /etc/mtab. - `autofs' version 5.0.0 will refuse to run if it cannot find an autofs4 kernel module that supports protocol version 5.00 or above. - mount options present in the master map are now overridden by mount options in map entries instead of being accumulated. This behaviour is in line with other industry automount implementations. New features in v5 ------------------ - improved direct mount map support - `+' map inclusion - added nsswitch map source support - rewrote multi-mount map code - added LDAP encryption and authentication support - improved shutdown and restart - a "hosts" map module has been added Before going to factory, any comments on this update? Matthias --------------------------------------------------------------------- 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] Invisible Network: tree connect failed: NT_STATUS_BAD_NETWORK_NAME
by M9. 01 Mar '07

01 Mar '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The strange thing is, that the networkfolder, i made for easy acces, is accessible, but the printer is not, while it is attached to the PC which can be accessed from the networkfolder... (ty (Default Printer) "Unable to connect to CIFS host, will retry in 60 seconds..." Description: ty Location: Make and Model: Epson Stylus C64 - CUPS+Gutenprint v5.0.0 Simplified Printer State: processing, accepting jobs, published. Device URI: smb://mshome/192.168.1.2/EPSONSty) What can i do to get rid of the tree connect failure? - -- Have a nice day, M9. Now, is the only time that exists. OS: Linux 2.6.18.2-34-default x86_64 Huidige gebruiker: monkey9@tribal-sfn2 Systeem: openSUSE 10.2 (X86-64) KDE: 3.5.5 "release 45.2" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFF5WvzX5/X5X6LpDgRAig0AJ9w1+rKfmsXfUFuCj/InjLwFA87RgCgu5V7 0/yJBJEyNykwvps6lWoQUXc= =1MdR -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 1

[opensuse-factory] Network profiles in NetworkManager
by Alberto Passalacqua 01 Mar '07

01 Mar '07

An interesting enhancement, which seems to be already present in Fedora, was suggested by a user (psp250) in IRC. NetworkManager at the moment is able to connect to manage only a single static IP, and if static DNS are specified, it's unable to update them when it connects to a dynamic network. The suggestion is to: * Make NM able to manage more configurations for the same network card (for example, if the wireless card is used to connect to different AP's, some with fixed configurations, some with dynamic ones). * Make NM able to manage static and dynamic DNS without having to change the settings in Yast. Regards, Alberto --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 2