December 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 552449] New: kdm does not install a logrotate rule
by bugzilla_noreply＠novell.com 16 Sep '12

16 Sep '12

http://bugzilla.novell.com/show_bug.cgi?id=552449 Summary: kdm does not install a logrotate rule Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: PC OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: danielm(a)ecoscentric.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/4.3; Linux) KHTML/4.3.2 (like Gecko) SUSE I noticed my kdm.log file is about 180 MiB (probably unrelated to X lockup). Reproducible: Always Steps to Reproduce: 1. cd /etc/logrotate.d; rpm -qf *|grep kdm 2. 3. Actual Results: <null> ;-) Expected Results: kdm-4.3.2-6.1 -- Configure bugmail: http://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 519137] New: java fails with "Could not reserve enough space for object heap"
by bugzilla_noreply＠novell.com 11 Sep '12

11 Sep '12

http://bugzilla.novell.com/show_bug.cgi?id=519137 Summary: java fails with "Could not reserve enough space for object heap" Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Java AssignedTo: bnc-team-java(a)forge.provo.novell.com ReportedBy: R.Vickers(a)cs.rhul.ac.uk QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.0.11) Gecko/2009060214 Firefox/3.0.11 On some memory configurations Java will not start: $ java -version Error occurred during initialization of VM Could not reserve enough space for object heap Could not create the Java virtual machine. You can make it start by specifying a maximum memory allocation pool, e.g. $java -Xmx3600m -version java version "1.6.0_0" IcedTea6 1.4 (suse-24.5.2-x86_64) Runtime Environment (build 1.6.0_0-b14) OpenJDK 64-Bit Server VM (build 14.0-b08, mixed mode) This test was done on a machine with 32GB real memory but with a virtual memory limit of about 4GB. The same thing happens on a 24 GB machine, but on a 4GB machine you have to reduce the virtual memory limit to around 1GB to trigger the bug. So it appears that java decides how much virtual memory it needs by looking at the physical memory without checking the virtual memory limit. On a shared computer (for example an LTSP server) it makes sense for the virtual memory limit (per process) to be much smaller than the physical memory size. The workround above helps to a certain extent, but I haven't found a way of getting eclipse to work. The -Xmx parameter has to be very early in the command line, for example it is no use saying java -version -Xmx3600m The same thing happens with Sun Java: $ /usr/lib64/jvm/java-1.6.0-sun/bin/java -version Error occurred during initialization of VM Could not reserve enough space for object heap Could not create the Java virtual machine. $ /usr/lib64/jvm/java-1.6.0-sun/bin/java -Xmx3600m -version java version "1.6.0_13" Java(TM) SE Runtime Environment (build 1.6.0_13-b03) Java HotSpot(TM) 64-Bit Server VM (build 11.3-b02, mixed mode) Reproducible: Always Steps to Reproduce: 1. Type java -version 2. If it works then experiment with lower virtual memory limits until it fails, e.g. ulimit -S -v 4000000 java -version ulimit -S -v 2000000 java -version ulimit -S -v 1000000 java -version Actual Results: Error occurred during initialization of VM Could not reserve enough space for object heap Could not create the Java virtual machine. Expected Results: java version "1.6.0_0" IcedTea6 1.4 (suse-24.5.2-x86_64) Runtime Environment (build 1.6.0_0-b14) OpenJDK 64-Bit Server VM (build 14.0-b08, mixed mode) I introduced the virtual memory limits because users were causing performance problems with very large jobs. I regard 4GB as a big limit, I don't think it is reasonable for Java to assume this is available without checking. -- Configure bugmail: http://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 525254] New: After login bug buddy launches
by bugzilla_noreply＠novell.com 11 Sep '12

11 Sep '12

http://bugzilla.novell.com/show_bug.cgi?id=525254 User rastislav.krupansky(a)gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525254#c1 Summary: After login bug buddy launches Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: rastislav.krupansky(a)gmail.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; sk; rv:1.9.1.1) Gecko/20090714 SUSE/3.5.1-1.1 Firefox/3.5.1 I'm not sure whether this is upstream issue, or specific for openSUSE. After login, bug buddy is launched and all Gnome desktop lags. I'm not able to launch start menu and applications. Here you are review crash details: Distribution: openSUSE 11.1 (i586) Gnome Release: 2.26.2 (null) (SUSE) BugBuddy Version: 2.26.0 System: Linux 2.6.27.25-0.1-default #1 SMP 2009-07-01 15:37:09 +0200 i686 X Vendor: The X.Org Foundation X Vendor Release: 10502000 Selinux: No Accessibility: Disabled GTK+ Theme: Gilouche Icon Theme: oxygen GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors --------------------- (nautilus:3946): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorHal: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bu (nautilus:3946): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.8902 for volume monitor org.gtk.Private.HalVolumeMonitor connected to the bus; seeding drives/volumes/mounts (gnome-panel:3715): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorHal: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message (gnome-panel:3715): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.8897 for volume monitor org.gtk.Private.HalVolumeMonitor connected to the bus; seeding drives/volumes/mounts (nautilus:3946): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorHal: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bu (nautilus:3946): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.8907 for volume monitor org.gtk.Private.HalVolumeMonitor connected to the bus; seeding drives/volumes/mounts (gnome-panel:3715): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorHal: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message (gnome-panel:3715): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.8902 for volume monitor org.gtk.Private.HalVolumeMonitor connected to the bus; seeding drives/volumes/mounts -------------------------------------------------- Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://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 506721] New: Skip network check doesn't work.
by bugzilla_noreply＠novell.com 10 Sep '12

10 Sep '12

http://bugzilla.novell.com/show_bug.cgi?id=506721 Summary: Skip network check doesn't work. Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bitdealer(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- I'm not sure when that crap started but at least since 11.1 the installer asks me if I would like to test my internet connection by downloading the latest release notes and updates and although I always select "NO, do NOT try to connect anywhere" it still tries over and over and naturally fails if no network is available. This behavior annoys the heck out of me over and over again! As in, regardless if I have a working network atm or not, IF I choose "Don't touch my internet connection" I expect & want it to respect my decision and not to do what it wants. Further it's a total waste of time which I simply would like to be able to avoid once again. So please fix that check. Last verified with build 0106. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 47

[Bug 535101] New: autoyast installation fails while using a very simple xml config
by bugzilla_noreply＠novell.com 28 Aug '12

28 Aug '12

http://bugzilla.novell.com/show_bug.cgi?id=535101 Summary: autoyast installation fails while using a very simple xml config Classification: openSUSE Product: openSUSE 11.2 Version: Milestone 6 Platform: i586 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: AutoYaST AssignedTo: ug(a)novell.com ReportedBy: pierre.berthier(a)ini.phys.ethz.ch QAContact: qa(a)suse.de Found By: --- Created an attachment (id=315755) --> (http://bugzilla.novell.com/attachment.cgi?id=315755) autoyast XML configuration file User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.13) Gecko/2009080315 Ubuntu/9.04 (jaunty) Firefox/3.0.13 Starting autoyast installation with a simplistic install.xml file (in textmode). After installing all packages, the installer stops with an error message: "An error occurred during initrd creation." Reproducible: Always Steps to Reproduce: 1. boot autoyast with the attached install.xml Actual Results: The installer stops with an error message: "An error occurred during initrd creation." Expected Results: The installer should complete the installation without error messages. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 14

[Bug 561131] New: Provide a Qt build with graphicssystem=raster
by bugzilla_noreply＠novell.com 28 Aug '12

28 Aug '12

http://bugzilla.novell.com/show_bug.cgi?id=561131 http://bugzilla.novell.com/show_bug.cgi?id=561131#c0 Summary: Provide a Qt build with graphicssystem=raster Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: cyberbeat(a)gmx.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux i686; U; de) Presto/2.2.15 Version/10.10 I have tested this on many (older) pcs, on which I like to use actual opensuse-distribution: on all my test hardware kde4 and its applications (even when used in kde3) are much too slow, to be able to work with. Tested hardware:combinations: GFX-Cards: ATI Radeon 7000, 9000, 9200, 9250 NVidia FX 5200, Geforce 4 Mainboards: PC-Chips m848a Elitegroup K7s5a Elitgroup K7s6a ASROCK K7S41GX With CPUs: Athlon XP 1700 Athlon XP 2000 Athlon XP 2200 On all these combinations most problems disappear when starting qt4 applications with graphicssystem=raster A good test example is the folderview-panel on the left of dolphin: open the tree (for example /usr/lib) and scroll. This is really sluggish without raster. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://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 511321] New: Enforce patch tagging by rpmlint check
by bugzilla_noreply＠novell.com 28 Aug '12

28 Aug '12

http://bugzilla.novell.com/show_bug.cgi?id=511321 Summary: Enforce patch tagging by rpmlint check Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: dmueller(a)novell.com ReportedBy: prusnak(a)novell.com QAContact: qa(a)suse.de CC: ro(a)novell.com, mrueckert(a)novell.com Found By: Development We are trying to use patch tagging in packages .spec files. This is documented here: http://en.opensuse.org/Packaging/Patches I suggest to create a simple RPMlint check which does the following: ("patch lines" are the lines in spec preamble which match "^Patch.*:") * checks if any of the patch lines contain %version or %{version} macro * checks if any of the patch lines have missing patch comment on the previous line * checks if all of the patch comments match this regexp: ^# PATCH-\{FIX\|FEATURE\}-\{OPENSUSE\|SLE\|UPSTREAM\} .*\.patch .* .*@.*\..* If the spec does not follow these points a warning with a link to the wiki should be emitted. We might want to raise an error, but this is better to be discussed with darix. -- Configure bugmail: http://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 523791] New: Done feature still appears in "top features" and "my features"
by bugzilla_noreply＠novell.com 27 Aug '12

27 Aug '12

http://bugzilla.novell.com/show_bug.cgi?id=523791 Summary: Done feature still appears in "top features" and "my features" Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: openFATE AssignedTo: tschmidt(a)novell.com ReportedBy: vuntz(a)novell.com QAContact: freitag(a)novell.com Found By: --- I implemented https://features.opensuse.org/305296 and it's now marked as done. However, it still appears in "top features" and "my features". This could be because it's not marked as done for some internal products. However, from the openSUSE point of view, it should really be done... -- Configure bugmail: http://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 543424] New: include documentation on installation dvd
by bugzilla_noreply＠novell.com 27 Aug '12

27 Aug '12

http://bugzilla.novell.com/show_bug.cgi?id=543424 Summary: include documentation on installation dvd Classification: openSUSE Product: openSUSE 11.2 Version: Milestone 7 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Usability AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: estellnb(a)gmail.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.10 (like Gecko) SUSE The full inclusion of all available documentation is vital for the offline-usability of the OpenSuSE-dvd. You can not make use of python without having python-doc installed and without access to the internet. It is the same for selfhtml and selflinux. Please assure that at least the most important doku is available on DVD as this is vital if you do not have access to the internet; it will then be the only source of information. Better leave some little used software out. Reproducible: Always -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 8

[Bug 493157] New: YasT2 tftp configuration fails to open firewall
by bugzilla_noreply＠novell.com 24 Aug '12

24 Aug '12

http://bugzilla.novell.com/show_bug.cgi?id=493157 Summary: YasT2 tftp configuration fails to open firewall Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i586 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: poolbarde(a)web.de QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.7) Gecko/2009022800 SUSE/3.0.7-1.1.6 Firefox/3.0.7 When trying to enable tftp service, the firewall port is not enabled properly (using YasT2 tftp setup tool). No error message is displayed, but when entering configuration dialog again, firewall port is disabled again. Also connection from outside not possible. Using firewall configuration dialoge for opening UDP port 69 is a workaround for getting tftp service up and runnign propperly. YasT2 logs added as attachment. Reproducible: Always Steps to Reproduce: 1.Use YasT2 tftp configruation dialog for setting up tftp service (make sure that o'open firewall' is enabled. 2.After clicking OK, firewall port is still closed. 3. Actual Results: Firewall port is not opened propperly. Expected Results: Firewall port should be opened by tftp configuration tool. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4