November 2006 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 217218] New: two 11_* files for slide show
by bugzilla_noreply＠novell.com 12 Aug '07

12 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=217218 Summary: two 11_* files for slide show Product: openSUSE 10.2 Version: Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: suse-beta(a)cboltz.de QAContact: jsrain(a)novell.com http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/s… has two files named 11_*.rtf: 11_docs.rtf and 11_novell.rtf. http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/s… also has two 11_* files. I'm not sure if this causes any problems, but since the other files are all numbered correctly, it is at least not correct ;-) Additionally, there's a 13_register.png which seems to be unused according to the number (I did not check all the *.rtf files). Please remove it if it is no longer needed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 8

[Bug 220368] New: yast2-bootloader: use special vga kernel option for fbdev based configurations
by bugzilla_noreply＠novell.com 12 Aug '07

12 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=220368 Summary: yast2-bootloader: use special vga kernel option for fbdev based configurations Product: openSUSE 10.2 Version: Beta 2 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: odabrunz(a)novell.com ReportedBy: sndirsch(a)novell.com QAContact: jsrain(a)novell.com CC: mhopf(a)novell.com, ms(a)novell.com Meanwhile nearly all ATI GPUs need to be driven with the fbdev driver. :-( Since many users install with a low resolution and afterwards want to configure a higher resolution, the kernel vga option needs to be adjusted. SaX2 could do this itself, but then it will conflict with the setting of yast2-bootloader (next time yast2-bootloader runs the setting witll be overwritten immediately again). Proposal would be that SaX2 writes a meta file with this setting, which is read by yast2-bootloader to resolve this conflict. Something like this: /etc/sysconfig/framebuffer: SPECIAL_FBMODE="yes" (default: no) FBMODE="0x318" (default: unset) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 8

[Bug 222184] New: png files in /etc/opt/kde3/
by bugzilla_noreply＠novell.com 12 Aug '07

12 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=222184 Summary: png files in /etc/opt/kde3/ Product: openSUSE 10.2 Version: Beta 2 plus Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: dkukawka(a)novell.com QAContact: qa(a)suse.de There are several PNG files under /etc/opt/kde3/icons and /etc/opt/kde3/doc. FHS 2.3 say this about /etc: ---------------------------------------- /etc/opt : Configuration files for /opt Purpose Host-specific configuration files for add-on application software packages must be installed within the directory /etc/opt/<subdir>, where <subdir> is the name of the subtree in /opt where the static data from that package is stored. ---------------------------------------- And IMO PNGs are not config files ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 5

[Bug 215892] New: Problem with detecting mouse after suspend2disk
by bugzilla_noreply＠novell.com 11 Aug '07

11 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=215892 Summary: Problem with detecting mouse after suspend2disk Product: SUSE Linux 10.1 Version: Final Platform: i686 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: lashkevi(a)landau.ac.ru QAContact: qa(a)suse.de On my Thinkpad 600X I usually use an external mouse and normally make suspend2disk after my work. From time to time I resume the computer without the external mouse, work and then suspend it again. The next time I resume it WITH the external mouse (I plug it in before switching on the computer!) the computer makes something mad when I start to move the mouse. Then I unplug the external mouse and plug it again on the running computer. After this manipulation the computer begins understand the mouse moving and buttons, except the wheel. It is easy to see (by unplugging the external mouse and trying the internal one) that the kernal thinks that it still works with the internal mouse only. The only way to restore full functionality of the mouse (including the wheel) is to reboot the computer. I believe that the problem is with the detecting mouse after resume. There was no such problem when I used SuSE 9.3. With SuSE 9.3 it gave a message in "/var/log/messages" and on the screen: "...kernel: logips2pp: Detected unknown logitech mouse model 85", when I resumed with the external mouse, and a message: "...kernel: input: PS/2 Generic Mouse on isa0060/serio1", when I resumed without it. Now, with SuSE 10.1, there are no kernel messages concerning mouse after resume. Computer: Thinkpad 600X / 650MHz / 261MB RAM External mouse moel: Logitech SBF95 Kernel: 2.6.16.21-0.25-default BIOS: # biosdecode 2.7 SMBIOS 2.2 present. Structure Table Length: 2374 bytes Structure Table Address: 0x000F7690 Number Of Structures: 55 Maximum Structure Size: 118 bytes PCI Interrupt Routing 1.0 present. Router ID: 00:07.0 Exclusive IRQs: 11 Slot Entry 1: ID 00:07, on-board Slot Entry 2: ID 00:02, on-board Slot Entry 3: ID 01:00, on-board Slot Entry 4: ID 00:04, on-board Slot Entry 5: ID 00:06, on-board Slot Entry 6: ID 00:03, on-board ACPI 1.0 present. OEM Identifier: IBM RSD Table 32-bit Address: 0x0FFD0000 BIOS32 Service Directory present. Revision: 0 Calling Interface Address: 0x000FD820 PNP BIOS 1.0 present. Event Notification: Polling Event Notification Flag Address: 0x00000415 Real Mode 16-bit Code Address: F000:E721 Real Mode 16-bit Data Address: F000:0000 16-bit Protected Mode Code Address: 0x000FE724 16-bit Protected Mode Data Address: 0x000F0000 SYSID present. Revision: 0 Structure Table Address: 0x000FF811 Number Of Structures: 1 VPD present. BIOS Build ID: ITET54WW Box Serial Number: 78ZPDN2 Motherboard Serial Number: J1D94145790 Machine Type/Model: 26459WU -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 7

[Bug 223625] New: pine-4.64N-10 crashes with index-rules defined
by bugzilla_noreply＠novell.com 11 Aug '07

11 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=223625 Summary: pine-4.64N-10 crashes with index-rules defined Product: SUSE Linux 10.1 Version: Final Platform: x86-64 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: djm(a)eastlink.ca QAContact: qa(a)suse.de This is a recent install with 2.6.16.21-0.25-default kernel Pine began crashing after a filter was defined. It seemed to work at first but each time sent-mail is accessed it crashes. The filter used was index-rules=_FOLDER_ == {sent-mail} => _INDEX_{IMAPSTATUS DATE RECIPS(33%) SIZE SUBJECT(67%)} Also tried filter index-rules=_FOLDER_ == {sent-mail;postponed-msgs} => _INDEX_{IMAPSTATUS DATE RECIPS(33%) SIZE SUBJECT(67%)} with the same results. The crash occurs immediately upon selecting sen-mail folder and hitting <return>. I can send .pinerc and anything else required upon request rather than post here. Best wishes, David Murdoch -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 4

[Bug 207903] New: No Sound With Suse 10.1 Using Device CM8738/C3DX PCI
by bugzilla_noreply＠novell.com 11 Aug '07

11 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=207903 Summary: No Sound With Suse 10.1 Using Device CM8738/C3DX PCI Product: SUSE Linux 10.1 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound AssignedTo: tiwai(a)novell.com ReportedBy: diprob(a)yahoo.com QAContact: qa(a)suse.de I am running 10.1 in parallel with an Suse 9.3 Installation. With Suse 9.3 sound works fine. With Suse 10.1 I was not able to get any sound out of my speakers. The error looks similar to bug 127738 (Suse 10.0) however none of the described work arounds made any difference. Installation with yast does not show any error message however the test button does not deliver any sound. I tried alsaconf and alsamixer as well. Messages show succesful restart of the sound driver but there wasn`t any success either. Please find some information below: hwinfo --sound: 14: PCI 0b.0: 0401 Multimedia audio controller [Created at pci.300] UDI: /org/freedesktop/Hal/devices/pci_13f6_111 Unique ID: gZD2.leFtcOMtGx0 SysFS ID: /devices/pci0000:00/0000:00:0b.0 SysFS BusID: 0000:00:0b.0 Hardware Class: sound Model: "C-Media Electronics CMI8738/C3DX PCI Audio Device" Vendor: pci 0x13f6 "C-Media Electronics Inc" Device: pci 0x0111 "CM8738" SubVendor: pci 0x13f6 "C-Media Electronics Inc" SubDevice: pci 0x0111 "CMI8738/C3DX PCI Audio Device" Revision: 0x10 Driver: "C-Media PCI" I/O Ports: 0xe400-0xe4ff (rw) IRQ: 185 (468 events) Module Alias: "pci:v000013F6d00000111sv000013F6sd00000111bc04sc01i00" Driver Info #0: Driver Status: cmpci is not active Driver Activation Cmd: "modprobe cmpci" Driver Info #1: Driver Status: snd_cmipci is active Driver Activation Cmd: "modprobe snd_cmipci" Config Status: cfg=yes, avail=yes, need=no, active=unknown File: hwcfg-bus-pci-0000:00:0b.0 MODULE='snd-cmipci' STARTMODE='auto' file: hwcfg-bus-pci-0000:00:0b.0 MODULE='via-rhine' MODULE_OPTIONS='' STARTMODE='auto' file: modprobe.d/sound options snd-cmipci enable=1 index=0 # gZD2.leFtcOMtGx0:CMI8738/C3DX PCI Audio Device alias snd-card-0 snd-cmipci Thanks for your help -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 9

[Bug 212218] New: Adaptec 2100S drivers for Linux Suse 10
by bugzilla_noreply＠novell.com 11 Aug '07

11 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=212218 Summary: Adaptec 2100S drivers for Linux Suse 10 Product: openSUSE 10.2 Version: Alpha 5 Platform: i386 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Major Priority: P5 - None Component: Zenworks AssignedTo: zlm-code10-bugs(a)forge.provo.novell.com ReportedBy: pmoro(a)optec-srl.com QAContact: jtariq(a)novell.com The installation of openSuse 10.1 has been very difficult, because of frequent hangs of the system (as reported in other messages). The configuration of the hw (that work fine, and where I can easily install a SL8) has an Adaptec 2100S SCSI driver and Seagate RAID1 hd's. I was able to perform the installation going step by step, starting from a minimal text based setup, and adding othen packages later. Now, when trying to put the system to work, it uses to hang after some time. It can be ping'ed from another pc, but no other answer. I have seen in the net other messages regarding this drive and problems related to it. >From the Linux Support I have been proposed to investigate if the problem has been solved with patches to 10.1 (unfortunately I haveonly the first release of it), or at least will be solved in 10.2. I would ask you to consider this problem. The involved hw is good and work fine, and can usefully used. Thank you. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 2

[Bug 216104] New: NetworkManager applet doesn't show message boxes
by bugzilla_noreply＠novell.com 11 Aug '07

11 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=216104 Summary: NetworkManager applet doesn't show message boxes Product: openSUSE 10.2 Version: Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: alberto.passalacqua(a)tin.it QAContact: qa(a)suse.de NetworkManager applet in GNOME doesn't show message boxes to confirm connection as happened in SuSE 10.1 and SLED 10. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 6

[Bug 219950] New: Sorting Application Browser
by bugzilla_noreply＠novell.com 11 Aug '07

11 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=219950 Summary: Sorting Application Browser Product: openSUSE 10.2 Version: Beta 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: ke(a)novell.com QAContact: qa(a)suse.de You must not sort the entries of the Application Browser alphabetically by "Groups". Why? 1/ It depends on the locale 2/ In English (US) "Games" are displayed on top ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 3

[Bug 208451] New: YaST: replace 'progressbar by task' with 'progressbar in total' (or add a PiT)
by bugzilla_noreply＠novell.com 11 Aug '07

11 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=208451 Summary: YaST: replace 'progressbar by task' with 'progressbar in total' (or add a PiT) Product: openSUSE 10.2 Version: Alpha 4 plus Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: azerion(a)gmail.com QAContact: jsrain(a)novell.com In the latest update of Factory there is a huge improvement with the added progress-bar. However, it shows a new progressbar for each seperated task. Now: Downloading X 0 [======================= ] 100 (of task X) refresh screen Downloading Y 0 [===== ] 100 (of task Y) See that in Y the progressbar is a new bar that shows only that task Y is about 10%. I think that does show that the progress is still being made. But it does not indicate how long it is gonna take. I don't know how many of those task will come and how long they will take. Maybe there are 100 tasks that will take 60 minutes....in that case I would want to know I can get some coffee, eat my dinner and watch some TV :P Therefor I request an TOTAL-progressbar. Only one bar that shows the progress of all tasks in total. The only refreshment in the screen should be the taskname. New: Now: Downloading X 0 [======= ] 100 (of all tasks) refresh screen Downloading Y 0 [================ ] 100 (of all tasks) In this case I can conclude that it ook 2 minutes to get to 50% and I can do some math so I know it will take aprox. 4 minutes in total so i can do something else for 2 minutes. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 11

[Bug 223150] New: rug not installed == cannot start /etc/init.d/novell-zmd service
by bugzilla_noreply＠novell.com 11 Aug '07

11 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=223150 Summary: rug not installed == cannot start /etc/init.d/novell-zmd service Product: openSUSE 10.2 Version: Beta 2 plus Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: mvidner(a)novell.com ReportedBy: locilka(a)novell.com QAContact: jsrain(a)novell.com Beta2plusplus (Tuesday's build) -- maybe it's already fixed... During the update from 10.0 to 10.2, I've deselected the entire ZenWorks Management pattern, but it seems some packages from it are still installed: definitely zmd and zen-updater. When the second stage boots, I've got and error that /etc/init.d/novell-zmd service cannot be started. This is because rug is not installed and this fact is not well-evaluated. ZMD status: 127, err ["sh /usr/bin/rug: No such file or directory"] -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 8

[Bug 219926] New: inst_source has 'Synchronize with ZMD' checked when zmd is not running
by bugzilla_noreply＠novell.com 11 Aug '07

11 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=219926 Summary: inst_source has 'Synchronize with ZMD' checked when zmd is not running Product: openSUSE 10.2 Version: Beta 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: wstephenson(a)novell.com QAContact: jsrain(a)novell.com Apparently this checkbox should be unchecked when zmd is not running. Instead, it is checked if zmd is installed but not running. This will cause an attempted sync and timeouts. The correct behaviour should be to have the checkbox widget enabled but not checked. --- If zmd is not installed at all, the widget is disabled, correctly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 5

[Bug 223467] New: growisofs burns only at 1.1x if not having root privileges
by bugzilla_noreply＠novell.com 11 Aug '07

11 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=223467 Summary: growisofs burns only at 1.1x if not having root privileges Product: openSUSE 10.2 Version: Beta 2 plus Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: sven.burmeister(a)gmx.net QAContact: qa(a)suse.de Using k3b and growisofs provided with beta2 or 10.1, my DVD-recorder burns at 1.1x only. It is capable of 16x and does so, if one gives it root-privileges. This is on a 1.4GHz Athlon with 512MB RAM and no other processes using more than 1% CPU. I was told that growisofs does not get these privileges by default because it is not necessary. Having only 1/16 of the max-burn-speed is different than "not necessary". Since users will hardly put up with this slow speed, they will either assign the privileges themselves or be pushed to use packman-builds (with k3bsetup2). If this is a bug in growisofs, it should get fixed in order not to push people to mess with privileges or install 3rd-party packages. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 6

[Bug 215901] New: When installing 101.1 Remastered DVD on machine where master is CD and slave is DVD
by bugzilla_noreply＠novell.com 11 Aug '07

11 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=215901 Summary: When installing 101.1 Remastered DVD on machine where master is CD and slave is DVD Product: SUSE Linux 10.1 Version: Final Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST AssignedTo: ug(a)novell.com ReportedBy: thomasmlee(a)yahoo.com QAContact: qa(a)suse.de When installing 101.1 Remastered DVD on machine where master is CD and slave is DVD I get this problem: After initial loading of the Unix Kernal, it keeps on asking me to load CD 1. I currently have SUSE 9.1 loaded onto the machine, and burned the 10.1 Remastered SUSE on my DVD drive. It seems this new version assumes whatever the master CD device is, is what is going to be used to install onto the system. 9.1 didn't have this problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 10

[Bug 221574] New: Confirming New Installation Source Leads to Hang while "Synchronizing with ZENworks"
by bugzilla_noreply＠novell.com 11 Aug '07

11 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=221574 Summary: Confirming New Installation Source Leads to Hang while "Synchronizing with ZENworks" Product: openSUSE 10.2 Version: Beta 2 Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rschulz(a)sonic.net QAContact: jsrain(a)novell.com Thes summary pretty much says it. The "Synchronizing..." alert remains indefinitely and must be aborted. The symptom has occurred twice, once in Beta 1 and once in Beta 2. It appears to occur the first time an installation source is added, but not after it is merely refreshed, though I have only read-only local sources (CD and DVD), so they don't ever change after being added. RRS -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 16

[Bug 220790] New: ipw2220 eats 100% CPU
by bugzilla_noreply＠novell.com 10 Aug '07

10 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=220790 Summary: ipw2220 eats 100% CPU Product: openSUSE 10.2 Version: Beta 2 Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gholmer(a)ameritech.net QAContact: qa(a)suse.de This same setup works fine in SUSE 10.1. I have several network setups using SCPM, and both my WEP at home and an open connection elsewhere work fine with this wireless interface in 10.2. IBM ThinkPad T43, YaST identifies Intel PRO/Wireless 2200BG using "traditional method - ifup" ethernet set to device activation "on cable connection" wireless set to device activation "manually - user controlled" using kinternet to activate wireless interface wireless set to automatic address setup (DHCP), change hostname via DHCP, update name servers and search list via DHCP operating mode: managed ESSID is specified correctly authentication mode is WPA-PSK key is specified as passphrase After activating the interface, kinternet's "Wireless LAN" dialog shows that I am associated to an access point, and displays its MAC address correctly. log shows: Nov 14 07:35:00 orac ifup: eth1 device: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05) Nov 14 07:35:00 orac ifup: eth1 configuration: wlan-id-00:16:6f:3e:87:c0 Nov 14 07:35:01 orac ifup-wireless: eth1 starting wpa_supplicant Nov 14 07:35:01 orac ifup-dhcp: Starting DHCP Client Daemon on eth1... Nov 14 07:35:01 orac ifup-dhcp: . Nov 14 07:35:02 orac ifup-dhcp: . Nov 14 07:35:03 orac ifup-dhcp: . Nov 14 07:35:04 orac ifup-dhcp: . Nov 14 07:35:05 orac gconfd (shadow-4879): GConf server is not in use, shutting down. Nov 14 07:35:05 orac gconfd (shadow-4879): Exiting Nov 14 07:35:05 orac ifup-dhcp: . Nov 14 07:35:06 orac ifup-dhcp: no IP address yet... backgrounding. Nov 14 07:35:12 orac kernel: eth1: no IPv6 routers present Nov 14 07:35:27 orac kernel: ipw2200: Failed to send ASSOCIATE: Already sending a command. Nov 14 07:35:41 orac kernel: eth1: NETDEV_TX_BUSY returned; driver should report queue full via ieee_device->is_queue_full. I never get a network connection, and shortly afterward, CPU goes to 100% and stays there. top shows that "ipw2200/0" has 99.9% CPU. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 15

[Bug 217472] New: Several rpm packages contain Makefile* junk
by bugzilla_noreply＠novell.com 10 Aug '07

10 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=217472 Summary: Several rpm packages contain Makefile* junk Product: openSUSE 10.2 Version: Beta 1 plus Platform: Other OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: balazs.melikant(a)univie.ac.at QAContact: qa(a)suse.de CC: balazs.melikant(a)univie.ac.at As previously reported for SUSE 10.0 beta(s) and just minutes ago for sylpheed-claws reparately (#217465), there are still lots of Makefile* files around the system. I'm sorry, now just giving you a file-list exclusively from my running system, of course as it was suggested earlier, ARCHIVES.gz could be easily zgrep-ed for all 'hits': /opt/kde3/share/apps/krita/brushes/Makefile.am /opt/kde3/share/apps/krita/brushes/Makefile.in /opt/kde3/share/apps/krita/palettes/Makefile.am /opt/kde3/share/apps/krita/palettes/Makefile.in /usr/lib/perl5/5.8.8/Encode/Makefile_PL.e2x /usr/share/doc/packages/blt/html/Makefile.vc /usr/share/doc/packages/cyrus-sasl/doc/Makefile /usr/share/doc/packages/cyrus-sasl/doc/Makefile.am /usr/share/doc/packages/cyrus-sasl/doc/Makefile.in /usr/share/doc/packages/cyrus-sasl/doc/NTMakefile /usr/share/doc/packages/fftw3/FAQ/Makefile /usr/share/doc/packages/fftw3/FAQ/Makefile.am /usr/share/doc/packages/fftw3/FAQ/Makefile.in /usr/share/doc/packages/fftw3/Makefile /usr/share/doc/packages/fftw3/Makefile.am /usr/share/doc/packages/fftw3/Makefile.in /usr/share/doc/packages/freeciv/de/Makefile /usr/share/doc/packages/freeciv/de/Makefile.am /usr/share/doc/packages/freeciv/de/Makefile.in /usr/share/doc/packages/freeciv/fr/Makefile /usr/share/doc/packages/freeciv/fr/Makefile.am /usr/share/doc/packages/freeciv/fr/Makefile.in /usr/share/doc/packages/freeciv/it/Makefile /usr/share/doc/packages/freeciv/it/Makefile.am /usr/share/doc/packages/freeciv/it/Makefile.in /usr/share/doc/packages/freeciv/ja/Makefile /usr/share/doc/packages/freeciv/ja/Makefile.am /usr/share/doc/packages/freeciv/ja/Makefile.in /usr/share/doc/packages/freeciv/Makefile /usr/share/doc/packages/freeciv/Makefile.am /usr/share/doc/packages/freeciv/Makefile.in /usr/share/doc/packages/freeciv/man/Makefile /usr/share/doc/packages/freeciv/man/Makefile.am /usr/share/doc/packages/freeciv/man/Makefile.in /usr/share/doc/packages/freeciv/nl/Makefile /usr/share/doc/packages/freeciv/nl/Makefile.am /usr/share/doc/packages/freeciv/nl/Makefile.in /usr/share/doc/packages/freeciv/sv/Makefile /usr/share/doc/packages/freeciv/sv/Makefile.am /usr/share/doc/packages/freeciv/sv/Makefile.in /usr/share/doc/packages/fvwm2/docs/Makefile /usr/share/doc/packages/fvwm2/docs/Makefile.am /usr/share/doc/packages/fvwm2/docs/Makefile.in /usr/share/doc/packages/fvwm2/sample.fvwmrc/Makefile /usr/share/doc/packages/fvwm2/sample.fvwmrc/Makefile.am /usr/share/doc/packages/fvwm2/sample.fvwmrc/Makefile.in /usr/share/doc/packages/gle/html/Makefile /usr/share/doc/packages/gle/html/Makefile.am /usr/share/doc/packages/gle/html/Makefile.in /usr/share/doc/packages/gnutls/examples/Makefile /usr/share/doc/packages/gnutls/examples/Makefile.am /usr/share/doc/packages/gnutls/examples/Makefile.in /usr/share/doc/packages/htdig/contrib/multidig/Makefile /usr/share/doc/packages/htdig/contrib/rtf2html/Makefile /usr/share/doc/packages/htdig/htdoc/Makefile /usr/share/doc/packages/htdig/htdoc/Makefile.am /usr/share/doc/packages/htdig/htdoc/Makefile.in /usr/share/doc/packages/ImageMagick/scenes/Makefile /usr/share/doc/packages/libsamplerate/doc/Makefile /usr/share/doc/packages/libsamplerate/doc/Makefile.am /usr/share/doc/packages/libsamplerate/doc/Makefile.in /usr/share/doc/packages/liferea/doc/html/Makefile /usr/share/doc/packages/liferea/doc/html/Makefile.am /usr/share/doc/packages/liferea/doc/html/Makefile.in /usr/share/doc/packages/liferea/doc/Makefile /usr/share/doc/packages/liferea/doc/Makefile.am /usr/share/doc/packages/liferea/doc/Makefile.in /usr/share/doc/packages/lvm2/Makefile /usr/share/doc/packages/lvm2/Makefile.in /usr/share/doc/packages/netcat/data/Makefile /usr/share/doc/packages/nfs-utils/Makefile /usr/share/doc/packages/nfs-utils/Makefile.am /usr/share/doc/packages/nfs-utils/Makefile.in /usr/share/doc/packages/opensc/doc/Makefile /usr/share/doc/packages/opensc/doc/Makefile.am /usr/share/doc/packages/opensc/doc/Makefile.in /usr/share/doc/packages/postfix/html/Makefile.in /usr/share/doc/packages/pstoedit/examples/Makefile /usr/share/doc/packages/pstoedit/examples/Makefile.am /usr/share/doc/packages/pstoedit/examples/Makefile.in /usr/share/doc/packages/python-gtk/examples/Makefile /usr/share/doc/packages/python-gtk/examples/Makefile.am /usr/share/doc/packages/python-gtk/examples/Makefile.in /usr/share/doc/packages/rpm/manual/Makefile /usr/share/doc/packages/rpm/manual/Makefile.am /usr/share/doc/packages/rpm/manual/Makefile.in /usr/share/doc/packages/sane/sane-backends/plustek/Makefile.kernel24 /usr/share/doc/packages/sane/sane-backends/plustek/Makefile.kernel26 /usr/share/doc/packages/tix/c-code/Makefile.in /usr/share/frozen-bubble/gfx/shoot/Makefile /usr/share/games/pysol/src/games/contrib/Makefile /usr/share/games/pysol/src/games/Makefile /usr/share/games/pysol/src/games/special/Makefile /usr/share/games/pysol/src/tk/Makefile /usr/share/groff/1.18.1/font/devdvi/generate/Makefile /usr/share/groff/1.18.1/font/devlj4/generate/Makefile /usr/share/groff/1.18.1/font/devps/generate/Makefile /usr/share/vim/vim70/macros/maze/Makefile -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 13

[Bug 208196] New: missing tools in rescue system
by bugzilla_noreply＠novell.com 10 Aug '07

10 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=208196 Summary: missing tools in rescue system Product: SUSE Linux 10.1 Version: Final Platform: All OS/Version: SuSE Linux 10.1 Status: NEW Severity: Blocker Priority: P5 - None Component: Usability AssignedTo: siegfried.olschner(a)novell.com ReportedBy: mhoppe(a)novell.com QAContact: siegfried.olschner(a)novell.com The rescue system of 10.1, SLES10 and SLED10 is unusable. There is no wget, ftp and/or w3m available. This is not really nice ti restore a machine which has only ftp for backup space. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 4

[Bug 220759] New: Additional installation sources need more information
by bugzilla_noreply＠novell.com 09 Aug '07

09 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=220759 Summary: Additional installation sources need more information Product: openSUSE 10.2 Version: Beta 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: marcel(a)hilzinger.hu QAContact: jsrain(a)novell.com After finishing installation you can ad additional installation sources. Currently this is factory factory-debug inst-source-extra The dialog should provide more informations on the content of the sources. Otherwise I fear, that many users will click on debug without knowing, what they do. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 4

[Bug 221272] New: Screen goes in standby mode during install
by bugzilla_noreply＠novell.com 09 Aug '07

09 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=221272 Summary: Screen goes in standby mode during install Product: openSUSE 10.2 Version: Beta 2 Platform: i386 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: romain.pelissier(a)sqliaison.com QAContact: jsrain(a)novell.com I have a Dell Latitude D610 and have installed the Beta 2 of Opensuse 10.2. It happens that during the setup, the screen goes in standby mode (the screen goes black and is turned off), which is not really convenient for a setup. Is it possible to avoid this behaviour during the setup of the OS? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 29

[Bug 212307] New: acx firmware images changed their filenames
by bugzilla_noreply＠novell.com 09 Aug '07

09 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=212307 Summary: acx firmware images changed their filenames Product: openSUSE 10.2 Version: Alpha 5 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: felix(a)derklecks.de QAContact: qa(a)suse.de The last paragraph of the file /usr/share/doc/packages/wireless-tools/README.firmware is outdated. The imgages changed their names, see: http://acx100.sourceforge.net/wiki/Firmware#Firmware_names Why is the firmware not included as non-oss? It can be downloaded at: http://acx100.erley.org/acx_fw/acx100_dlink_dwl650+/fw1/ The files from dlink are at: ftp://ftp.dlink.com/Wireless/dwl520+/Driver/ It would help to write this information in README.firmware... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 7

[Bug 207322] New: seccheck improvements
by bugzilla_noreply＠novell.com 08 Aug '07

08 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=207322 Summary: seccheck improvements Product: openSUSE 10.2 Version: Alpha 4 plus Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Other AssignedTo: thomas(a)novell.com ReportedBy: thomas(a)novell.com QAContact: qa(a)suse.de For me: From: Michael James <Michael.James(a)csiro.au> To: suse-security(a)suse.com Date: Thu, 21 Sep 2006 09:38:21 +1000 User-Agent: KMail/1.8 Subject: [suse-security] Improvements to seccheck Who is looking after seccheck these days? The header says: Daily security check v2.0 by Marc Heuse <marc(a)suse.de> But I sent an email to him and it bounced. Has he moved on? Here's what I am suggesting: The seccheck scripts provide some interesting reading for the systems administrator, pointers for tightening things etc. But I get pages of false positives from the writeable, executable, and suid parts of the script. You see some partitions on my disks contain regular rsync-ed backups of other machines, including machines not under my control. To protect my machine, backup partitions are mounted noexec,nosuid. When your scripts get the list of mounts they take no account of this. Would it be an improvement to split your $MNT list into 3? Say: $MNT_WRITE $MNT_EXEC $MNT_SUID This would allow the find to only be fired into the branches of the filesystem where the permissions matter. I'd be happy to work out and suggest some patches, but if you think it better left simple, I won't bother you... michaelj -- Michael James michael.james(a)csiro.au System Administrator voice: 02 6246 5040 CSIRO Bioinformatics Facility fax: 02 6246 5166 -- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help(a)suse.com Security-related bug reports go to security(a)suse.de, not here -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 1

[Bug 207944] New: NetworkManager does not work with prism54
by bugzilla_noreply＠novell.com 08 Aug '07

08 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=207944 Summary: NetworkManager does not work with prism54 Product: SUSE Linux 10.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: sven.burmeister(a)gmx.net QAContact: qa(a)suse.de If I try to use a WEP connection via NetworkManager it fails because it tries to use wpa_supplicant for it, which the prism54-driver does not work with, I think. Using the standard ifup-etc. method does work, yet for the "normal user" it is not obvious why NetworkManager fails, since it does not give any notification but just stops at 28%. Expected behaviour would at a minimum be to inform the user that prism54 will not work with WEP and NetworkManager and that one should use the traditional method. Best would be to not use wpa_supplicant for prism54 as long as they do not work together and use an alternative method within NM. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 38

[Bug 216564] New: Include switch to not load ACPI modules explicitly in userspace services
by bugzilla_noreply＠novell.com 08 Aug '07

08 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=216564 Summary: Include switch to not load ACPI modules explicitly in userspace services Product: openSUSE 10.2 Version: Beta 1 plus Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: thoenig(a)novell.com ReportedBy: trenn(a)novell.com QAContact: qa(a)suse.de This bug is in fact not against 10.2, it's enough if it's implemented shortly after. ACPI modules will get loaded automatically soon via udev. We should have temperary solution where we have a variable in /etc/init.d/service (should be enough) to easily switch back to manual loading if we experience problems and to be able to rip out the manual loading easily as soon as we are sure the stuff works fine. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 4

[Bug 205550] New: use yaboot for booting Pegasos PPC
by bugzilla_noreply＠novell.com 08 Aug '07

08 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=205550 Summary: use yaboot for booting Pegasos PPC Product: openSUSE 10.2 Version: Alpha 4 Platform: PowerPC OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: olh(a)novell.com ReportedBy: pczanik(a)fang.fa.gau.hu QAContact: jsrain(a)novell.com As discussed in e-mail, please use yaboot to boot Pegasos PPC machines: "It just needs some tweaking in the lilo script to do the right thing with copying yaboot and possible the yaboot.conf file over to the boot partition." -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 16