September 2009 - openSUSE Testing - openSUSE Mailing Lists

installation report
by Bernhard Wiedemann 04 Oct '09

04 Oct '09

yesterday I installed KDE-LiveCD-MS7 on my Laptop(FSC Amilo Pro 2030) and took notes what I liked (will usually not be seen on bugzilla): new Live-CD->USB http://en.opensuse.org/Live_USB_stick#openSUSE_11.2 partition manager UI allows "which partitions to use for install" - first time I did not have to use expert mode when there was already something on the HDD. function keys for brightness/volume working out-of-the-box even in Live-system default sound scheme suspend-to-* working in installed system === problems (did not check bugzilla for those yet): minor: syslinux suggested 800x600 resolution but internal TFT has 1024x768 KDE-live-system: S2RAM fails to resume (black screen, does not shutdown on power-button) ; works after installation minor: CD-tray was ejected after install from USB keyboard was back at us after install (I set german in syslinux) ; yast2 language helped prepare_preload on ext4 printed messages to console "/var/tmp/kdecache/...data has tail _and_ normal blocks" wontfix: b43 (WLAN) firmware missing -> install_bcm43xx_firmware helps NetworkManager failed to assign ipv4 addr/nameserver for eth0 after cable hotplug (only ipv6 from radvd) NetworkManager-0.7.1_git20090811-1.2.i586: system standstill after ethernet cable disconnect Segmentation fault in yast2 online-update-configuration (Register.ycp) => advanced/register => configure now => +Hardware Profile => Details|Next no automatic updates? has useless link to novell.com? ; re-tested after update to factory. still there. yast2 online repositories links to 11.1 factory seamonkey-2.0b2-1.3 /usr/lib/seamonkey/seamonkey-bin: symbol lookup error: /usr/lib/seamonkey/seamonkey-bin: undefined symbol: gdk_x11_window_get_drawable_impl -> zypper install gtk2 helped, so it was a missing dependency. seamonkey -mail can not save this mail to IMAP sent folder for some reason also already had two more system crashes, one of which needed a manual fsck.ext4 run afterwards. No backtrace available since I was in X11 and syslog had not caught it. === on my Phenom X4 + GeForce 9400 GT: Live-CD: LCD screen loosing signal randomly (approx 2/minute) overall there are still plenty of issues to be solved. I will probably retest with a later pre-release and/or test MS7 on my other laptop. You are welcome to confirm and file the above issues in bugzilla. Ciao Bernhard M. -- To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-testing+help(a)opensuse.org

7 15

oS Testing Core Team - Testing Targets & Scheduling
by Refilwe Seete 03 Oct '09

03 Oct '09

oS Testing Core Team, Since it looks like an IRC meeting may be a little while away, perhaps we can deal with more things on the mailing list before we lose too much momentum. I think the one of most important things we can do is decide what we want to test against and when we want to move on from a given release. This then gives all the team members a rough schedule to follow, and it also lets the dev team know what to expect from us - at least as far as testing the distro on real hardware goes. A quick and dirty general roadmap of a release looks like this: 1. Check-in new updated packages 2. Decide what new features will be targeted at the release 3. Develop new features 4. Progressively freeze elements [Milestone 5 & 6] 5. Final Round of Testing [Release Candidates] 6. Post-release critical bug-fixing [Gold Master] The points we can test are: 1. Factory, as components offered on top of a stable release (ex:KDE:Factory) 2. Factory, as a complete rolling distribution testing updates as they come 3. Factory, taking regular builds of our own choosing (ex: Every Thursday's build) 4. Official Snapshots, such as Milestones/RCs/GM IMHO, I think the oS TCT should also test the final release. Since the team was formed pretty late in the roadmap, we should run the final release for at least 2-4 weeks to help knock out bugs that squeaked through. This should be done for 11.2 at least. Looking ahead to 11.3, things are pretty wide open. Judging from some of the changes in Factory and comments online, I believe that openSUSE developers would really appreciate if more people ran Factory. However, there may be a reduction in our effectiveness if we end up fighting against obvious but big bugs (bad kernel builds, uninstallable images, etc.). Ideally we would thoroughly test both Factory as a distribution and Milestones, but that's probably not feasible team-wide. My first instinct is to test crap out of all the snapshots as that will also provide the simplest scheduling mechanism - We just test a given snapshot until the next one comes out...thus we test a final release until the devs deliver Milestone 0 of the next version. We can also leverage that time between GM and Milestone 0 to review the last run and adjust our procedures accordingly. However, we should decide as a team what to focus on - even if it means splitting the team down the into a Snapshot Team and a Rolling Release Team. Refilwe -- To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-testing+help(a)opensuse.org

3 6

Re: [opensuse-testing] Re: Benchmarking Suse
by Randy Appleton 30 Sep '09

30 Sep '09

> > In my experience, the only real variances in speed are for the > startup, as distributions use different methods and start different > processes. With regard to things such as launching basic applications, > I've never seen a serious statement about this backed up. Have you ever seen the opposite? Has anyone tested the distributions and found they are all about the same speed? This too would be useful data. > > There will be variances if you are using different desktop > environments, and those kind of results are interesting to see -- > particular with regards to memory. Lubos Lunak (an openSUSE/KDE > developer) did some testing into this a _long_ time ago[1]. I'm confused. I followed the link and read an excellent article about excess fonts and application slowdown. And in fact, if different distributions have different amount of fonts, that would be relevant and impact performance. Is this what you mean? Also, I assume without knowing that there are other ways distributions can effect the speed of their applications (even if just by installing different versions with different startup options). But if everything is the same speed, I'll just report that. > > However, if you are launching the same application in the same desktop > environment on a different distribution (making sure it is the same > app -- which wouldn't work for i.e. searching), I very much doubt > there will be a significant or material difference. But there are some > possibilities, and it might be interesting to just verify or disprove > that, but only if you would investigate why ;-). > > Anyhow, with regard to distribution boot times, I ran a test some time > ago on the differences between the boot times from some of the popular > distributions[2]. An update on something like that probably would not > take too long and it would be interesting. Yep. And one thing I'd very much like to do is get the data to Suse developers. > > [0] http://www.kdedevelopers.org/node/1654 > [1] http://ktown.kde.org/~seli/memory/desktop_benchmark.html > [2] http://francis.giannaros.org/blog/2007/08/23/comparing-distribution-boot-ti… > -- > Francis Giannaros http://francis.giannaros.org I love these suggestions. Anyone have any more? -- To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-testing+help(a)opensuse.org

1 0

Re: Benchmarking Suse
by Larry Finger 29 Sep '09

29 Sep '09

Randy Appleton wrote: > Hello. > > I'm a computer science professor at Northern Michigan University. I > found your email address at > http://en.opensuse.org/OpenSUSE_Testing_Core_Team. I'm considering > offering a student research project and thought you might be able to > provide some input. Or, could you suggest someone better to contact? > > Has anyone timed various operations in Suse vs Ubuntu vs Fedora? I'm > curious if it's quicker to log in, find a file, open a document, etc. in > Suse, Ubuntu or Fedora? > > Does anyone already have data on these questions? Or, if we do the > benchmarking myself, is anyone interested in the results? Finally, is > there some particular operation you'd like to see benchmarked? I'm copying this reply to the opensuse-testing mailing list. I have heard anecdotal reports that distro XX is faster than YY while doing ZZ, but I am not aware of any properly designed studies. I am confident that the other members of the Testing Team will post such studies if they exist. Certainly, the distro packagers would be interested in the results. My suspicion is that the most important factor will be the kernel itself, and that there will be only small differences when all are using the same kernel version; however, that is certainly a testable hypothesis. Larry -- To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-testing+help(a)opensuse.org

3 2

How to work in openSUSE Core Testing Team?
by Vojtěch Zeisek 28 Sep '09

28 Sep '09

Hello, few days ago Holger asked for some discussion of future work of openSUSE Core Testing Team, but I have not received any message regarding this topic. Well, I'm not professional software tester, so I would appreciate some introduction or short how to from someone more skilled. According to Holger's first mail, where he welcomed us in the team he mentioned "What I personally do expect from the new openSUSE Testing Core is not mainly executing test cases. From my point of view the team is responsible to decide what to test and how to test. This can be done by creating test plans containing test cases either developed by the developers itself or members with good knowledge in that specific area. Good contact to the development teams would for sure support that." It sounds good, but it does not say to me, where and how to start. I'm afraid because of great time shift between Europe and America we are not able to meet in #opensuse-testing IRC channel. I'm not absolutely sure what is difference between https://bugzilla.novell.com/tr_show_run.cgi?run_id=19162 and https://bugzilla.novell.com/tr_show_run.cgi?run_id=19163 - it is for different versions, yes, but I mean in basic idea. After short experimentation I hope I'm familiar with this technology, but short how to would be nice. :-) Finally, here is my basic idea ("the null hypothesis") how to start work of openSUSE Core Testing Team. I try to start the discussion, not to make exact plane of the work. Everyone of us is interested in different areas (I suppose), so let's divide the field of all applications. For example I use KDE, I like its graphical software (digiKam, ...), I use, I'd say, "scientific" applications (R, Kile, ...) and I run a LAMP server. So I would test basically this class of applications. And like this we can divide whole distribution. Some groups, like games :-), might be wished by more people, but I hope we will be able to cover whole field. I hope everyone of us has some deeper knowledge about his favorite applications, so he can say what should be tested, what might be problematic, what is important and so on. I have sens our role should be partially coordinating the testing, shouldn't it? Is it usable basic idea? In Testopia we can then create plans similar to those for YaST (already presented). It can be the coordinating place, right? But who will follow the plans we make in Testopia? Only our group plus developers? Finally, I hope our team will help openSUSE to be the best Linux distribution. :-) Have a nice day, Vojtěch Zeisek

3 2

YaST automatic partitioner
by Vojtěch Zeisek 27 Sep '09

27 Sep '09

Hello, have You ever tried to install openSUSE to computer with already installed Windows and use YaST automatic division of hard disc (accepting defaults)? Although I do not have Windows, I have seen it on several computers and I was not satisfied. Proposed solutions are very strange and complicated. For example I had an older computer with 2 windows hard discs (one big FAT partition on each), YaST tried to shrink both discs and create 4 partitions (swap, /, /home, /usr), on my friend's laptop it tried to delete both Windows partitions (disc was divided to Windows system a data), but aim was to install whole openSUSE instead of only one Windows partition (dualboot). Is it only my sense or do You have similar experience with automatic disc division during installation? More over I still have sense that installation from Live CD is even more strange in this way... I use expert mode and it is OK, but for "an average user" it is very confusing. I know people understanding basics of disc partitioning, but not understanding YaST's proposals... Have a nice day, Vojtěch Zeisek

3 2

[opensuse-testing]
by Stefanie Dotzler 23 Sep '09

23 Sep '09

Hello, I've encountered a problem with the 11.2 M7 release. After some working time my machine (Acer Aspire 5315, Intel Celeron Processor 550) is completely crashing. It goes off immediately with no warning or clean shutdown. This is reproducible but the time it takes to crash differs a lot (between 5 minutes - 24 hours). However, the notebook works flawlessly except for this happens. With the 11.1 final release this problem doesn't occur. Here are the logs which I found interesting: Sep 19 12:43:01 ebcoM7 kernel: [ 1583.711112] CPU0: Temperature above threshold, cpu clock throttled (total events = 1) Sep 19 12:43:01 ebcoM7 kernel: [ 1583.711184] Disabling lock debugging due to kernel taint Sep 19 12:43:01 ebcoM7 kernel: [ 1583.712061] CPU0: Temperature/speed normal Sep 19 12:43:02 ebcoM7 kernel: [ 1584.083749] CPU0: Temperature above threshold, cpu clock throttled (total events = 2) Sep 19 12:43:02 ebcoM7 kernel: [ 1584.084732] CPU0: Temperature/speed normal Sep 19 12:43:02 ebcoM7 kernel: [ 1584.092081] CPU0: Temperature above threshold, cpu clock throttled (total events = 3) Sep 19 12:43:02 ebcoM7 kernel: [ 1584.093043] CPU0: Temperature/speed normal ....... I cut the purview in the middle! Sep 19 12:45:47 ebcoM7 kernel: [ 1749.644472] CPU0: Temperature above threshold, cpu clock throttled (total events = 19287) Sep 19 12:45:47 ebcoM7 kernel: [ 1749.650429] CPU0: Temperature/speed normal Sep 19 12:45:47 ebcoM7 kernel: [ 1749.650485] CPU0: Temperature above threshold, cpu clock throttled (total events = 19288) Sep 19 12:45:57 ebcoM7 kernel: [ 1759.123985] CPU0: Temperature/speed normal Sep 19 12:45:57 ebcoM7 kernel: [ 1759.124049] CPU0: Temperature above threshold, cpu clock throttled (total events = 19295) following a lsmod: Module Size Used by nfs 344624 0 lockd 81452 1 nfs fscache 46520 1 nfs nfs_acl 3264 1 nfs auth_rpcgss 43360 1 nfs sunrpc 225152 5 nfs,lockd,nfs_acl,auth_rpcgss af_packet 23616 4 ip6t_LOG 6468 7 xt_tcpudp 3136 2 xt_pkttype 1632 3 ipt_LOG 6276 8 xt_limit 2628 15 snd_pcm_oss 51424 0 snd_mixer_oss 18432 1 snd_pcm_oss snd_seq 64688 0 snd_seq_device 8556 1 snd_seq edd 10440 0 ip6t_REJECT 5472 3 nf_conntrack_ipv6 22100 4 ip6table_raw 3008 1 xt_NOTRACK 1632 4 ipt_REJECT 3168 3 xt_state 2208 8 iptable_raw 2848 1 iptable_filter 3616 1 ip6table_mangle 4160 0 nf_conntrack_netbios_ns 2432 0 nf_conntrack_ipv4 11688 4 i915 246856 1 drm 183936 2 i915 i2c_algo_bit 6884 1 i915 nf_conntrack 84444 5 nf_conntrack_ipv6,xt_NOTRACK,xt_state,nf_conntrack_netbios_ns,nf_conntrack_ipv4 nf_defrag_ipv4 2112 1 nf_conntrack_ipv4 ip_tables 13488 2 iptable_raw,iptable_filter ip6table_filter 3616 1 ip6_tables 14928 4 ip6t_LOG,ip6table_raw,ip6table_mangle,ip6table_filter x_tables 19108 11 ip6t_LOG,xt_tcpudp,xt_pkttype,ipt_LOG,xt_limit,ip6t_REJECT,xt_NOTRACK,ipt_REJECT,xt_state,ip_tables,ip6_tables ipv6 305748 21 ip6t_REJECT,nf_conntrack_ipv6,ip6table_mangle fuse 75548 3 loop 17196 0 dm_mod 84548 0 arc4 1952 2 ecb 3264 2 cryptomgr 95216 0 aead 8640 1 cryptomgr pcompress 2752 1 cryptomgr crypto_blkcipher 14820 2 ecb,cryptomgr crypto_hash 14432 1 cryptomgr snd_hda_codec_realtek 230692 1 crypto_algapi 21252 7 arc4,ecb,cryptomgr,aead,pcompress,crypto_blkcipher,crypto_hash ath5k 137704 0 mac80211 214744 1 ath5k ath 8608 1 ath5k snd_hda_intel 31936 3 snd_hda_codec 94560 2 snd_hda_codec_realtek,snd_hda_intel snd_hwdep 8580 1 snd_hda_codec snd_pcm 97348 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec acer_wmi 17696 0 led_class 4804 2 ath5k,acer_wmi snd_timer 26760 2 snd_seq,snd_pcm i2c_i801 12788 0 sr_mod 17316 0 cfg80211 103392 3 ath5k,mac80211,ath iTCO_wdt 12452 0 snd 74884 16 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer soundcore 8416 1 snd pcspkr 2784 0 joydev 11456 0 i2c_core 32212 4 i915,drm,i2c_algo_bit,i2c_i801 sg 32532 0 cdrom 40448 1 sr_mod iTCO_vendor_support 3876 1 iTCO_wdt video 24600 1 i915 rfkill 22772 2 acer_wmi,cfg80211 tg3 123076 0 snd_page_alloc 10216 2 snd_hda_intel,snd_pcm output 3328 1 video battery 12772 0 ac 4900 0 wmi 7720 1 acer_wmi button 6544 0 intel_agp 30300 1 ext4 358244 1 jbd2 95616 1 ext4 crc16 1952 1 ext4 uhci_hcd 29104 0 rtc_cmos 14928 0 ehci_hcd 56144 0 rtc_core 22652 1 rtc_cmos rtc_lib 3168 1 rtc_core fan 5028 0 processor 49968 1 ide_pci_generic 4036 0 piix 6760 0 ide_core 122444 2 ide_pci_generic,piix ata_generic 4836 0 ata_piix 25256 3 ahci 39184 0 libata 198732 3 ata_generic,ata_piix,ahci thermal 21020 0 thermal_sys 18120 4 video,fan,processor,thermal hwmon 3676 1 thermal_sys If there are further details or logs needed or if someone can advise me how I can dig deeper into the problem please let me know. Can anybody tell me the best way for the next action? Because it seems to have to do with some driver for the mainboard/cpu. I can test it to confirm my supposition or anybody tell me the next step. So I will wait of an answer. Personally: Please let me know my mistakes(write on the incorrect place or other wrong things) because this is the best way to reform! Best regards Stefanie Dotzler -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser -- To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-testing+help(a)opensuse.org

3 2

*** vital issues *** for OpenSuSE 11.2
by Elmar Stellnberger 22 Sep '09

22 Sep '09

While we already have a list of the most annoying bugs causing hazards or blocking users I wanna encourage something new: A list of vital-issues which are of elevated importance to desktop users. I would regard the following as candidate issues: * Firefox: bookmarks can not be added any more (bug 540629) * Thunderbird: can not select default browser (bug 540631) * pairing of bluetooth devices does not work in user mode (bug 513123) -- To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-testing+help(a)opensuse.org

3 2

*** vital issues *** for OpenSuSE 11.2
by Elmar Stellnberger 21 Sep '09

21 Sep '09

Have created a vital issues sample list at http://en.opensuse.org/Bugs:Vital_Issues_11.2_dev; You are welcome to add your own features! -- To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-testing+help(a)opensuse.org

2 2

Conference Slides
by Steven Harms 19 Sep '09

19 Sep '09

Can we get the opensuse-testing slides posted? Thanks, Steven Harms -- GPG Key ID: C92EF367 / 1428 FE8E 1E07 DDA8 EFD7 195F DCCD F5B3 C92E F367 WWW: http://www.sharms.org/blog -- To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-testing+help(a)opensuse.org

1 0