December 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 455960] New: osc build: You can't build against RHEL cause it doesn' t provide vim.
by bugzilla_noreply＠novell.com 04 Dec '08

04 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=455960 Summary: osc build: You can't build against RHEL cause it doesn't provide vim. Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: anschneider(a)novell.com QAContact: adrian(a)novell.com Found By: --- You can't build locally against RHEL_4 or RHEL_5 with osc cause it doesn't provide vim. $ osc build RHEL_5 x86_64 samba.spec Building samba.spec for RHEL_5/x86_64 Getting buildinfo from server buildinfo is broken... it says: expansion error: nothing provides vim -- 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.

1 1

[Bug 449362] New: ntp-client in first stage messing up sysconfig variable NETCONFIG_NTP_POLICY
by bugzilla_noreply＠novell.com 04 Dec '08

04 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=449362 Summary: ntp-client in first stage messing up sysconfig variable NETCONFIG_NTP_POLICY Product: openSUSE 11.1 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mc(a)novell.com QAContact: jsrain(a)novell.com CC: milisav.radmanic(a)novell.com, mt(a)novell.com Found By: Development If in first stage yast2-ntp-client is started it seems to read this policy from a not existing file (/etc/sysconfig/network/config seems not to be part of the inst-sys). Then installation starts and the sysconfig package install a /etc/sysconfig/network/config where NETCONFIG_NTP_POLICY is set to "auto". After the ntp configuration is written (at the end of first stage) this variable is set to "". I may be a good idea umount the sysconfig agent and mount it again in case of first stage. -- 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.

1 5

[Bug 416108] New: update of SuSEfirewall2 removes entries from SuSEfirewall2 config file and makes it unusable
by bugzilla_noreply＠novell.com 04 Dec '08

04 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=416108 User opensuse(a)go4more.de added comment https://bugzilla.novell.com/show_bug.cgi?id=416108#c340926 Summary: update of SuSEfirewall2 removes entries from SuSEfirewall2 config file and makes it unusable Product: openSUSE 11.0 Version: Final Platform: PC OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: opensuse(a)go4more.de QAContact: jsrain(a)novell.com Depends on: 340926 Found By: Community User When updating the SuSEfirewall2 package, in my case it happened twice, with: - update from openSUSE 10.3 to openSUSE 11.0 (using the i386 DVD) and - by updating SuSEfirewall2 using you on the freshly installed openSUSE 11.0 the config file /etc/sysconfig/SuSEfirewall2 is changed. Thereby, variables on additional custom zones set in this file are removed. Before the update, I had the following entries in SuSEfirewall2: FW_ZONES="wlan" FW_DEV_wlan='eth5' FW_SERVICES_wlan_TCP="ssh" FW_REJECT_wlan="yes" After the update, the two lines FW_DEV_wlan='eth5' FW_SERVICES_wlan_TCP="ssh" were no longer existing. This causes SuSEfirewall not to come up properly, as the chains that ought to be created for 'wlan' cannot be created, which causes SuSEfirewall2 to print error messages and which results in a system with incomplete firewall rules set-up. This is why I chose 'Major' for severity. Note: in addition, some comments in the examples in area 30.) (a few lines above th variables discussed here) were deleted as well. Note: During these updates, the same thing described in bug #340926 happened to my SuSEfirewall2 config file as well (see my comment there). -- 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.

1 17

[Bug 443302] New: apport: Reports for openSUSE Factory are often Unreportable
by bugzilla_noreply＠novell.com 04 Dec '08

04 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=443302 Summary: apport: Reports for openSUSE Factory are often Unreportable Product: openSUSE 11.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: jblunck(a)novell.com ReportedBy: jblunck(a)novell.com QAContact: qa(a)suse.de CC: nderkach(a)gmail.com Found By: Development Most of the time when running Apport with openSUSE Factory, the report is unreportable since new versions of a dependent package are already available. In this example it is even a version with a different package architecture. We need a modus to let Apport work with Factory more conveniently. Probably a way to let us report problems for packages that are not older than 2 weeks or so would be an interesting idea. UnreportableReason: You have some obsolete package versions installed. Please upgrade the following packages and check if the problem still occurs: glibc $ zypper search -s glibc S | Name | Type | Version | Arch | Repository --+-------------------+------------+-------------+--------+-------------------- i | glibc | package | 2.8.90-16.1 | i686 | factory v | glibc | package | 2.8.90-16.2 | i586 | factory | glibc | srcpackage | 2.8.90-17.2 | noarch | home:janblunck:test | glibc | srcpackage | 2.8.90-16.1 | noarch | factory -- 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.

1 1

[Bug 450884] New: "View File" shows "Edit File" as window title
by bugzilla_noreply＠novell.com 04 Dec '08

04 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=450884 Summary: "View File" shows "Edit File" as window title Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: wstephenson(a)novell.com QAContact: adrian(a)novell.com Found By: --- C&P error in the readonly view file page as above. -- 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.

1 1

[Bug 443676] New: Inconsistent meaning of [OK] button in YaST
by bugzilla_noreply＠novell.com 04 Dec '08

04 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=443676 Summary: Inconsistent meaning of [OK] button in YaST Product: openSUSE 11.1 Version: Factory Platform: All OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Usability AssignedTo: mschmidkunz(a)novell.com ReportedBy: jsmeix(a)novell.com QAContact: qa(a)suse.de Found By: Development In the YaST style guide http://en.opensuse.org/YaST/Style_Guide#Single_Configuration.2FOverview.2FE… it is not clear what the [OK] button in a Single Configuration/Overview/Edit Dialog should do because it only reads: "OK - The settings are applied and the screen is closed." It is not clear what "the screen is closed" means. Should it close the dialog and return to the overview or should it close the dialog and exit the whole YaST module? The current YaST printer module, behaves inconsistently because of this. If there is a single step configuration dialog as a branch of another configuration dialog (i.e. the "Add Driver" and "Driver Options" dialogs which are called e.g. from the "Modify print queue" dialog) the [OK] button in a single step configuration branch dialog returns to the caller (e.g. the "Modify print queue" dialog). In conrast if there is a single step configuration dialog on the top level of the tree of dialogs (e.g. the "Printing via Network" and "Share Printers" dialogs) the [OK] button in a top-level single step configuration dialog exits the whole YaST printer module. The problem here is that for the user it is not obvious if the current configuration dialog is at a lower-level ([OK] returns to the caller) or at top-level ([OK] exits the whole YaST printer module). At least for me (am I the only one?) it happens often that I click [OK] and get the whole module closed but I liked to do some other settings in other top-level dialogs so that I have to re-launch the module again. -- 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.

1 7

[Bug 456402] New: Clamav claims that it is outdated ( Your ClamAV installation is OUTDATED!)
by bugzilla_noreply＠novell.com 04 Dec '08

04 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=456402 Summary: Clamav claims that it is outdated (Your ClamAV installation is OUTDATED!) Product: openSUSE 11.0 Version: Final Platform: Other OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: robin.listas(a)telefonica.net QAContact: qa(a)suse.de Found By: --- This is popping up in the WARNING log periodically: Dec 4 13:02:13 nimrodel freshclam[3795]: Your ClamAV installation is OUTDATED! Dec 4 13:02:13 nimrodel freshclam[3795]: Local version: 0.94.1 Recommended version: 0.94.2 Dec 4 13:02:14 nimrodel freshclam[3795]: Your ClamAV installation is OUTDATED! Dec 4 13:02:14 nimrodel freshclam[3795]: Current functionality level = 37, recommended = 38 Dec 4 13:02:14 nimrodel freshclam[3795]: Current functionality level = 37, recommended = 38 This is an ongoing problem. Look: /var/log/mail.debug-20080610.gz:Jun 9 15:44:50 nimrodel freshclam[9428]: Local version: 0.93 Recommended version: 0.93.1 .. /var/log/mail.debug-20080703.gz:Jul 1 20:13:45 nimrodel freshclam[5059]: Local version: 0.93 Recommended version: 0.93.1 (a month!) /var/log/mail.debug-20080711.gz:Jul 7 22:21:04 nimrodel freshclam[5151]: Local version: 0.93.1 Recommended version: 0.93.3 .. /var/log/mail.debug-20080714.gz:Jul 12 10:39:33 nimrodel freshclam[5140]: Local version: 0.93.1 Recommended version: 0.93.3 /var/log/mail.debug-20080907.gz:Sep 3 20:21:39 nimrodel freshclam[5004]: Local version: 0.93.3 Recommended version: 0.94 .. /var/log/mail.debug-20080914.gz:Sep 11 19:13:47 nimrodel freshclam[3772]: Local version: 0.93.3 Recommended version: 0.94 /var/log/mail.debug-20081103.gz:Nov 3 20:29:59 nimrodel freshclam[3747]: Local version: 0.94 Recommended version: 0.94.1 . /var/log/mail.debug-20081121.gz:Nov 21 12:23:23 nimrodel freshclam[3739]: Local version: 0.94 Recommended version: 0.94.1 (two weeks!) /var/log/mail.debug-20081128.gz:Nov 26 18:06:40 nimrodel freshclam[3795]: Local version: 0.94.1 Recommended version: 0.94.2 .. I know that this is an ongoing problem, and that the fault is not yours. But a solution should be found. It is bad that the devs push a new version, force that message into the warning log, and the security update gets ready by the time the devs push a new one, outdating the one you just released. And all the time, the systems supposedly protected by clamav, are not. It is not a problem for me, but for others it is. -- 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.

1 1

[Bug 449714] New: A defined connection can't be deleted
by bugzilla_noreply＠novell.com 04 Dec '08

04 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=449714 Summary: A defined connection can't be deleted Product: openSUSE 11.1 Version: Beta 5 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mgyhardsoft(a)freestart.hu QAContact: jsrain(a)novell.com Found By: --- In YaST2 printer wizard if there is a connection defined it cannot be really deleted. When it is removed and adding a new connection is started the removed connection data appear again. The only way to loose them is to exit and re-enter the YaST printer module (just like if it were a Microsoft program). How to reproduce: 1. Start YaST2 printer module 2. Try to add a new print queue (I tried CUPS and Windows). 3. Fill in the necessary data and press OK. 4. YaST2 says that adding the print queue is unsuccessful - even if the connection string is perfectly perfect. Press OK. 5. Now you get back to Point 2. Try to add another print queue. The dialog popping up contains the previously entered connection string, and there is no way to remove or replace it - at least I couldn't discover the way. -- 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.

1 20

[Bug 441354] New: Kontact crash2
by bugzilla_noreply＠novell.com 04 Dec '08

04 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=441354 Summary: Kontact crash2 Product: openSUSE 11.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: mc(a)novell.com QAContact: qa(a)suse.de Found By: Development Another kontact crash. Backtrace follows... -- 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.

1 10

[Bug 430486] New: Data access query
by bugzilla_noreply＠novell.com 04 Dec '08

04 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=430486 Summary: Data access query Product: openSUSE 11.1 Version: Beta 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Blocker Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: doiggl(a)velocitynet.com.au QAContact: qa(a)suse.de Found By: --- Hello, I've installed 11.1x (beta1) on a system and I am trying to access some data on a separate disk which I cant access at this time. Question: How do i get to this data [I need commands] (There-in lies the problem) First some details: - The data in question is on the disk(dev/sdc1) as indicated by #fdisk -l (below) - The data is on one big reiserfs partition on this disk it takes up the whole disk and it is located on a extended partition in the disk. - The disk itself (dev/sdc1) has not been touched since this installation. I know the data is there I just cannot get to it. - The disk itself (dev/sdc1) has 1 big reiserfs partition which is on a extended partition. [its not a primary partition]. - The system boots from a diferent disk. Device Boot Start End Blocks Id System /dev/sdc1 2 91201 732564000 f W95 Ext'd (LBA) # fdisk -l Disk /dev/sda: 80.0 GB, 80026361856 bytes 255 heads, 63 sectors/track, 9729 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00060053 Device Boot Start End Blocks Id System /dev/sda1 1 262 2104483+ 82 Linux swap / Solaris /dev/sda2 * 263 4901 37262767+ 83 Linux /dev/sda3 4902 9729 38780910 83 Linux Disk /dev/sdb: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System Disk /dev/sdc: 750.1 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x000ddf82 Device Boot Start End Blocks Id System /dev/sdc1 2 91201 732564000 f W95 Ext'd (LBA) Can you help with this problem I have encountered so I can access the data on this disk please. do I need special tools to get to the data ? Glenn -- 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.

1 5