openSUSE Bugs March 2009

bugs@lists.opensuse.org

1 participants
2070 discussions

[Bug 467272] New: logwatch is missing directory /etc/logwatch/scripts/services
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=467272 Summary: logwatch is missing directory /etc/logwatch/scripts/services Classification: openSUSE Product: openSUSE 11.1 Version: RC 2 Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: asvetter(a)cip.physik.uni-wuerzburg.de QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-0.1 Firefox/3.0.5 The logwatch rpm does not create the directory /etc/logwatch/scripts/services on installation. The result is the following error message: wpyc001:/root # /etc/cron.daily/0logwatch ################### Logwatch 7.3.6 (05/19/07) #################### Processing Initiated: Mon Jan 19 10:23:10 2009 Date Range Processed: yesterday ( 2009-Jan-18 ) Period is day. Detail Level of Output: 0 Type of Output: unformatted Logfiles for Host: wpyc001 ################################################################## --------------------- Dmeventd Errors Begin ------------------------ No such file or directory at /usr/share/logwatch/scripts/services/dmeventd line 44. ---------------------- Dmeventd Errors End ------------------------- Workaround: mkdir /etc/logwatch/scripts/services Reproducible: Always Steps to Reproduce: 1. Install logwatch rpm 2. run /etc/cron.daily/0logwatch or wait for execution of the daily cronjob 3. notice error message 4. mkdir /etc/logwatch/scripts/services 5. run /etc/cron.daily/0logwatch again 6. no error message -- 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 436688] New: zypper "Sort the list by repository priority" doesn' t uses numeric sort
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=436688 Summary: zypper "Sort the list by repository priority" doesn't uses numeric sort Product: openSUSE 11.0 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: cmorve69(a)yahoo.es QAContact: qa(a)suse.de Found By: Community User zypper "Sort the list by repository priority" doesn't uses numeric sort. See packman postion... $ LC_ALL=C zypper lr -P # | Alias | Name | Enabled | Refresh | Priority ---+----------------------+----------------------+---------+---------+--------- 5 | home_reddwarf | RedDwarf's Home | Yes | Yes | 1 6 | kde3 | KDE3 | Yes | Yes | 25 8 | kde4_factory_desktop | KDE4 Factory Desktop | Yes | Yes | 25 10 | kde_qt | Current Qt 4.x | Yes | Yes | 25 11 | mozilla | Mozilla | Yes | Yes | 25 13 | nvidia | NVIDIA | Yes | Yes | 25 14 | openoffice | OpenOffice.org | Yes | Yes | 25 21 | smart | Smart | Yes | Yes | 25 25 | wine | Wine | Yes | Yes | 25 15 | opensuse-dvd | openSUSE DVD | Yes | No | 50 18 | repo-debug | openSUSE Debug | No | No | 50 19 | repo-non-oss | openSUSE Non-Oss | Yes | No | 50 20 | repo-oss | openSUSE Oss | Yes | No | 50 22 | updates | Updates | Yes | Yes | 50 1 | education | Education | Yes | Yes | 75 2 | emulators | Emulators | Yes | Yes | 75 3 | games | Games | Yes | Yes | 75 7 | kde4_community | KDE4 Community | Yes | Yes | 75 9 | kde_backports | KDE Backports | Yes | Yes | 75 12 | network_utilities | Network Utilities | Yes | Yes | 75 16 | opensuse_tools | openSUSE tools | Yes | Yes | 75 24 | virtualbox | VirtualBox | Yes | Yes | 75 26 | yast_svn | YaST svn snapshots | Yes | Yes | 75 27 | zypp_svn | ZYPP SVN Builds | Yes | Yes | 75 17 | packman | Packman | Yes | Yes | 8 4 | home_mvyskocil | mvyskocil's Home | Yes | Yes | 93 23 | videolan | VideoLan | Yes | Yes | 99 -- 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 3

[Bug 483897] New: man ntpq: section peers, missing char for "The character in the left margin"
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=483897 Summary: man ntpq: section peers, missing char for "The character in the left margin" Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: All OS/Version: All Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: ke(a)novell.com ReportedBy: Ori_Tzoran(a)bmc.com QAContact: ke(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.9 (like Gecko) SUSE characters aren't shown for "The character in the left margin". i guess the original omission comes from the NTP doc. i found the "good" doc accidentally in IBM's AIX collection at : http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.… Reproducible: Always Steps to Reproduce: 1.man ntpq 2./character in the left margin indicates 3. Actual Results: the list of properties doesn't indicate the actual char in the left margin -- 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 9

[Bug 481422] New: Popup "No checksum found" is impossible to understand
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=481422 Summary: Popup "No checksum found" is impossible to understand Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mvancura(a)novell.com QAContact: jsrain(a)novell.com Found By: L3 The following popup appeared several times (approx. 6) during the opensuse 11.1 installation: once before the final "install button" and cca 5 times after it. "No checksum for file /mnt/var/tmp/var/tmp/TmpDir.bxEZG5/images/details-x86_64.xml was found in repository, but the list of checksum in this repository does not mention this file. Using the file may put the integrity of your system at risk. Use it anyway? Yes - No" This popup is 100% useless for the usual opensuse user because (at least): 1. it doesn't say which repository is this problem about 2. it doesn't say what the file in question really is - is that strange-looking path usual in the installation process? Or not? How can the user know? 3. it doesn't say what is the reason why it pops up 6th time. Especially if, for example, I used one repository only. (and expect there is one file with checksums for each repository, of course) 4. it doesn't say what each answer really means and will mean in the future. What if one clicks 'No'? The installation stops? Or the repository will be skipped? And, if yes, how YaST will continue if this was the only repository?... ...and similar for 'Yes' -- 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 4

[Bug 481354] New: Factory doesn't boot in VirtualBox anymore
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=481354 Summary: Factory doesn't boot in VirtualBox anymore Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Blocker Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: poeml(a)novell.com QAContact: qa(a)suse.de Found By: --- Every Factory image upgraded yesterday or the day before ceased to work for me, and the current images out there fail in the same way. They all stop with a black screen at the time where the kernel should be loading (or starting to be loaded maybe). VirtualBox aborts and says "aborted". It doesn't seem to be a quirk in VirtualBox, and not a bug in the handling of the snapshots I had accumulated (which was my first suspicion). It didn't change anything to start with a fresh harddisk without snapshots. Other images I have around (FreeBSD, Ubuntu, ArchLinux, 11.1) work. I played with VirtualBox config options, to no avail. Reinstalling the bootloader didn't help. I booted a rescue system, recreated the initial ramdisk, and noticed that mkinitrd includes about 87 modules into the initial ramdisk, which seems weird. (It gives an initrd 13 megs in size, uncompressed). I wondered why the initrd is just a simple gzipped cpio archive, I had expected something fancier, but maybe this is the way things are done today. I later was able to boot the system with an 11.1 kernel, with an initrd created with 11.1 mkinitrd. -- 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 13

[Bug 472803] New: missing used_by for MD RAID using device-mapper devices
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=472803 Summary: missing used_by for MD RAID using device-mapper devices Classification: openSUSE Product: openSUSE 11.2 Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: aschnell(a)novell.com ReportedBy: aschnell(a)novell.com QAContact: jsrain(a)novell.com Found By: Development With YaST it's possible to create a MD RAID using two device-mapper devices. The used_by information is correct directly after creation. But after a restart of YaST the used_by information is missing. -- 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 2

[Bug 490634] New: NetworkManager-kde4 for Opensuse 11.0
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=490634 Summary: NetworkManager-kde4 for Opensuse 11.0 Classification: openSUSE Product: openSUSE 11.0 Version: Final Platform: All OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: anshulajain(a)gmail.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5) Gecko/2008032600 SUSE/2.9.95-25.1 Firefox/3.0b5 Networkmanager-kde4 is available for Opensuse 11.1, but is not available for 11.0. I have to use 11.0 instead of 11.1 due to certain restrictions due to hardware. I would really really appreciate if Networkmanager-kde4 was made available for Opensuse 11.0, through the KDE4 BS project. I have tried to package the 11.1 version for 11.0 through the BS, but have faced several problems. I am willing to work on this through my BS Project (anshuljain), if I can get some guidance on this. -Anshul Reproducible: Always -- 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 490319] New: missing dependency in kdebase4-workspace
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=490319 Summary: missing dependency in kdebase4-workspace Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: richard(a)nod.at QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1 Firefox/3.0.6 hi! /usr/bin/startkde from kdebase4-workspace needs dbus-launch to start up kde4. please add dbus-1-x11 as dependency to kdebase4-workspace or to the kde4 pattern. it took my quite long to figure out why my minimal kde4-livecd failed to start kde4. :-( Reproducible: Always Steps to Reproduce: 1. build with kiwi a live-iso which uses only the patterns default and kde4 2. boot it up 3. startkde fails with "Could not start D-Bus. Check your installation." -- 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 488692] New: Bad description of kernel-trace
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=488692 Summary: Bad description of kernel-trace Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: aidamos(a)seznam.cz QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; cs-CZ; rv:1.9.0.7) Gecko/2009022800 SUSE/3.0.7-2.1 Firefox/3.0.7 In YaST: the package "kernel-trace" has description "The Realtime Linux Kernel" It isn't true! Kernel-trace is not a real-time kernel. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 6

[Bug 464727] New: yast product creator mixes up architectures
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=464727 Summary: yast product creator mixes up architectures Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bart(a)geesink.org QAContact: jsrain(a)novell.com Found By: --- When I try to make a installation CD with yast product creator it creates an unbootable CD. /boot/i386 is completely empty. I think the problem is related to architecture. When I choose the installation source, this message is displayed: source http://192.168.1.240/suse/11.1 does not support the current architecture (i386). Change the target architecture? Then a checkbox where you can only choose i586. This same problem also prevents making a kiwi image. There you get this message: Target architecure of the current configuration (i586) does not match the system configuration (i386). Kiwi cannot create images for different architectures. Attached my y2log. The image is used for testing this is named test_for_begreport (yes that was a typo, my English is not *that* bad ;)). Thanks! -- 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 13

← Newer
1
2
3
4
5
6
7
8
...
207
Older →

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs March 2009