November 2011 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 551705] New: boot process does not continue for 1,5 minutes, although the DE is already up and running
by bugzilla_noreply＠novell.com 28 Mar '12

28 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=551705 Summary: boot process does not continue for 1,5 minutes, although the DE is already up and running Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: sven.burmeister(a)gmx.net QAContact: qa(a)suse.de Found By: --- Created an attachment (id=325014) --> (http://bugzilla.novell.com/attachment.cgi?id=325014) boot.msg User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-1.1.2 Firefox/3.5.4 As you can see in the log, the boot process is not continued for 1,5 minutes. I'm not sure what the cause is, so I'll attach the whole log. The result of this issue however is that while the DE is already up and running NetworkManager was not started yet and hence the NM client did not set-up a networkc onnection yet when the applications restored as part of the DE session want to access the network. Starting acpid done <notice -- Nov 1 11:48:31.225966000> service acpid done <notice -- Nov 1 11:48:31.374109000> startproc: execve (/sbin/rsyslogd) [ /sbin/rsyslogd -c 4 -f /etc/rsyslog.early.conf ], [ DO_FASTBOOT=no SELINUX_INIT=YES CONSOLE=/dev/console ROOTFS_FSTYPE=ext3 TERM=linux SHELL=/bin/sh ROOTFS_FSCK=0 LC_ALL=POSIX INIT_VERSION=sysvinit-2.86 DO_BLOGD=yes REDIRECT=/dev/tty1 COLUMNS=156 PATH=/bin:/sbin:/usr/bin:/usr/sbin DO_CONFIRM=no vga=0x31a RUNLEVEL=5 SPLASHCFG=/etc/bootsplash/themes/openSUSE/config/bootsplash-1280x1024.cfg PWD=/ DO_QUIET=no PREVLEVEL=N LINES=60 SHLVL=2 HOME=/ DO_FORCEFSCK=no SPLASH=yes splash=silent ROOTFS_BLKDEV=/dev/disk/by-id/scsi-SATA_Maxtor_6Y080P0_Y2V5H71E-part1 _=/sbin/startproc DAEMON=/sbin/rsyslogd ] <notice -- Nov 1 11:48:31.541690000> service earlysyslog doneStarting syslog servicesdone <notice -- Nov 1 11:48:31.593602000> start_daemon: execve (/bin/dbus-daemon) [ /bin/dbus-daemon --system ], [ DO_FASTBOOT=no CONSOLE=/dev/console SELINUX_INIT=YES ROOTFS_FSTYPE=ext3 SHELL=/bin/sh TERM=linux ROOTFS_FSCK=0 LC_ALL=POSIX INIT_VERSION=sysvinit-2.86 DO_BLOGD=yes REDIRECT=/dev/tty1 COLUMNS=156 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x31a DO_CONFIRM=no RUNLEVEL=5 PWD=/ SPLASHCFG=/etc/bootsplash/themes/openSUSE/config/bootsplash-1280x1024.cfg DO_QUIET=no PREVLEVEL=N LINES=60 HOME=/ SHLVL=2 DO_FORCEFSCK=no splash=silent SPLASH=yes ROOTFS_BLKDEV=/dev/disk/by-id/scsi-SATA_Maxtor_6Y080P0_Y2V5H71E-part1 _=/sbin/start_daemon DAEMON=/bin/dbus-daemon ] Starting D-Bus daemon <notice -- Nov 1 11:48:31.681846000> service dbus donedone <notice -- Nov 1 11:48:31.682012000> service earlyxdm start <notice -- Nov 1 11:48:31.682719000> service network start <notice -- Nov 1 11:48:31.683418000> service haldaemon start <notice -- Nov 1 11:48:34.343634000> service network done <notice -- Nov 1 11:48:34.343719000> service syslog start <notice -- Nov 1 11:48:34.962833000> startproc: execve (/usr/bin/kdm) [ /usr/bin/kdm ], [ DO_FASTBOOT=no SELINUX_INIT=YES CONSOLE=/dev/console ROOTFS_FSTYPE=ext3 TERM=linux SHELL=/bin/sh ROOTFS_FSCK=0 INIT_VERSION=sysvinit-2.86 DO_BLOGD=yes KDEROOTHOME=/root/.kdm REDIRECT=/dev/tty1 COLUMNS=156 PATH=/bin:/sbin:/usr/bin:/usr/sbin DO_CONFIRM=no vga=0x31a RUNLEVEL=5 SPLASHCFG=/etc/bootsplash/themes/openSUSE/config/bootsplash-1280x1024.cfg PWD=/ DO_QUIET=no LANG=de_DE.UTF-8 PREVLEVEL=N LINES=60 QT_SYSTEM_DIR=/usr/share/desktop-data SHLVL=2 HOME=/ XCURSOR_THEME=DMZ DO_FORCEFSCK=no WINDOWMANAGER= SPLASH=yes splash=silent ROOTFS_BLKDEV=/dev/disk/by-id/scsi-SATA_Maxtor_6Y080P0_Y2V5H71E-part1 _=/sbin/startproc DAEMON=/usr/bin/kdm ] Starting service kdm4done <notice -- Nov 1 11:48:35.109595000> service earlyxdm doneLoading CPUFreq modulesdone Starting HAL daemondone <notice -- Nov 1 11:48:35.446919000> service haldaemon done <notice -- Nov 1 11:48:38.825405000> checkproc: /usr/bin/kdm 1351 <notice -- Nov 1 11:49:59.570305000> killproc: kill(1207,15) Re-Starting syslog services <notice -- Nov 1 11:49:59.678472000> startproc: execve (/sbin/rsyslogd) [ /sbin/rsyslogd -c 4 -f /etc/rsyslog.conf ], [ DO_FASTBOOT=no CONSOLE=/dev/console SELINUX_INIT=YES ROOTFS_FSTYPE=ext3 SHELL=/bin/sh TERM=linux ROOTFS_FSCK=0 LC_ALL=POSIX INIT_VERSION=sysvinit-2.86 DO_BLOGD=yes REDIRECT=/dev/tty1 COLUMNS=156 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x31a DO_CONFIRM=no RUNLEVEL=5 PWD=/ SPLASHCFG=/etc/bootsplash/themes/openSUSE/config/bootsplash-1280x1024.cfg DO_QUIET=no PREVLEVEL=N LINES=60 HOME=/ SHLVL=2 DO_FORCEFSCK=no splash=silent SPLASH=yes ROOTFS_BLKDEV=/dev/disk/by-id/scsi-SATA_Maxtor_6Y080P0_Y2V5H71E-part1 _=/sbin/startproc DAEMON=/sbin/rsyslogd ] <notice -- Nov 1 11:49:59.786658000> service syslog donedone 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 15

[Bug 685627] New: While ipv6 can be disabled for the browsers with difficulty yast2 always uses it causing dns problems for many users
by bugzilla_noreply＠novell.com 28 Mar '12

28 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=685627 https://bugzilla.novell.com/show_bug.cgi?id=685627#c0 Summary: While ipv6 can be disabled for the browsers with difficulty yast2 always uses it causing dns problems for many users Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: i586 OS/Version: openSUSE 11.4 Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: a.johnw(a)yahoo.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0b12) Gecko/20110222 Firefox/4.0b12 The usual way of disabling ipv6 was to use kernal load appends. This doesn't seem to do anything any more. The kde flag also does not stop konqueror from using it. Firefox has to be stopped from it's own configuration facility. Despite the kernel load appends and a change to sysctl.conf which does prevent Konqueror from using it YAST2 continues to use ipv6. This causes dns problems on many isp's when updates etc are run and they take for ever as a result - 18hrs and it didn't complete. This made worse by the fact that yast2 assumes the server is busy and extends the retry delay times. While all of this is going on both firefox and konqueror working on ipv4 can access and download the update files with ease. There are too many to use this as an update fix. Reproducible: Always Steps to Reproduce: 1.Clean 11.4 install from downloaded dvd 2. Try updating via a network that has problems with dns via ipv6 - many do 3.Read the forums and see how often this crops up, google brings up 500,000 hits many asking for fixes on a number of suse releases. Actual Results: DNS problems prevent a full update from occurring in anything like a reasonable time. Expected Results: There should be a method within yast of disabling ipv6 on all web traffic even from itself. Users can't be expected to find the existing methods which do not bear any relationship to previous ones so info on the web is misleading. Yast seems to be applying patches as they are loaded. I assume that nothing really happens until it has all of the updates it needs otherwise this might lead to a broken system. As YAST stands if an update is provided I could not be sure of being able to install it with yast as it can take hours to even check for repository updates. -- 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 15

[Bug 661539] New: [>96 DPI] Text preferences sizes do not appear in the preference panes
by bugzilla_noreply＠novell.com 27 Mar '12

27 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=661539 https://bugzilla.novell.com/show_bug.cgi?id=661539#c0 Summary: [>96 DPI] Text preferences sizes do not appear in the preference panes Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox AssignedTo: bnc-team-mozilla(a)forge.provo.novell.com ReportedBy: mrmazda(a)earthlink.net QAContact: qa(a)suse.de Found By: --- Blocker: --- Upstream is https://bugzilla.mozilla.org/show_bug.cgi?id=621462 which until fixed should block 11.4 release. -- 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 699400] New: Hardware clock never set on shutdown when ntp is active
by bugzilla_noreply＠novell.com 27 Mar '12

27 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=699400 https://bugzilla.novell.com/show_bug.cgi?id=699400#c0 Summary: Hardware clock never set on shutdown when ntp is active Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: seife(a)novell.slipkontur.de QAContact: qa(a)suse.de CC: werner(a)novell.com Found By: Third Party Developer/Partner Blocker: --- (This bug is also in 11.4) During shutdown, I always only see The System Time is in sync with Hardware Clock and hwclock is not set. The problem is IMHO in the ELEVENMIN_MODE code in /etc/init.d/boot.clock This test machine has a hw clock which is 1 hour off. For testing, I disabled ntp. strolchi:~ # adjtimex --print | grep status status: 64 In this case, ELEVENMIN_MODE == no and the clock is set on shutdown. Now I start ntp: strolchi:~ # /etc/init.d/ntp start 10 Jun 23:52:42 sntp[2883]: Started sntp 2011-06-10 23:52:42.303197 (-0100) -3599.902140 +/- 0.046265 secs Time synchronized with ntp.home.s3e.de Starting network time protocol daemon (NTPD) done strolchi:~ # adjtimex --print | grep status status: 8193 Now, ELEVENMIN_MODE == yes and the clock setting code is skipped on shutdown. So with the hwclock 1 hour off, this always leads to time warps during boot and th e hwclock is never corrected. I don't really understand the ELEVENMIN_MODE code, but it does not look too helpful. strolchi:~ # grep -v ^# /etc/sysconfig/clock HWCLOCK="-u" SYSTOHC="yes" TIMEZONE="Europe/Berlin" DEFAULT_TIMEZONE="US/Eastern" -- 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 39

[Bug 675370] New: large delay to open file picker from KSnapshot
by bugzilla_noreply＠novell.com 27 Mar '12

27 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=675370 https://bugzilla.novell.com/show_bug.cgi?id=675370#c0 Summary: large delay to open file picker from KSnapshot Classification: openSUSE Product: openSUSE 11.4 Version: RC 2 Platform: x86 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: mrmazda(a)earthlink.net QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=416403) --> (http://bugzilla.novell.com/attachment.cgi?id=416403) file picker screenshot I found this at least a month ago in RC6 or prior, but kept forgetting to report. An hour or so ago on one K7 system I counted about 15 seconds to open the save as window. This time on a 2.4G P4, it took 45 seconds - each time. In KDE3 the time to open is too short to measure, while 45 seconds will make many people think the system is hung. The difference between the two (15 vs. 45) possibly confirms the actual problem. Both systems have about about 110 lines in fstab of type nfs and noauto for infrequently available hosts. On the K7 I had done my usual manual mount of the four nfs lines most often mounted, but I hadn't on the P4. The save as dialog is populating the left pane with all the unmounted noauto nfs entries (and all 28 local partitions whether or not in fstab, plus samba share fstab lines), making the default window size have a scrollbar for the left pane of around 8-10 multiples of its height. Cutting fstab from 11469 bytes to 796 bytes (10 lines total) cut the open time to 5 seconds, but there are still unmounted local partitions in the list, making a scroll of about two heights of the pane in the default window size. I checked in Fedora 15 on same P4 system, which took 7 seconds with all 11k of fstab unmodified, showing all partitions mounted or not, but no unmounted nfs items. The left pane should show nothing in it that would first need to be mounted before saving to would be possible. -- 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 601649] New: installing kde4_basis pattern on M6 system with no X installed does not set KDM as display manager
by bugzilla_noreply＠novell.com 27 Mar '12

27 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=601649 http://bugzilla.novell.com/show_bug.cgi?id=601649#c0 Summary: installing kde4_basis pattern on M6 system with no X installed does not set KDM as display manager Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 6 Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Patterns AssignedTo: coolo(a)novell.com ReportedBy: mrmazda(a)earthlink.net QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=358407) --> (http://bugzilla.novell.com/attachment.cgi?id=358407) y2logs To reproduce: 1-install only base system with server & networking but no X 2-install patterns-openSUSE-kde4_basis (I used ncurses yast for this) 3-start runlevel 5 Actual results: 1-xdm starts Expected results: 2-kdm starts -- 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 732688] New: Kernel panic on every cold boot
by bugzilla_noreply＠novell.com 27 Mar '12

27 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=732688 https://bugzilla.novell.com/show_bug.cgi?id=732688#c0 Summary: Kernel panic on every cold boot Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: captainsheldon(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=464002) --> (http://bugzilla.novell.com/attachment.cgi?id=464002) dmesg, hwinfo, message log attached User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.121 Safari/535.2 I installed OpenSuSE 12.1 Release on a Packard Bell notebook. I got kernel panic on every power on (only cold boot!). hwinfo, dmesg etc attached. 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 3

[Bug 728248] New: MacBook Pro needs acpi=off to boot
by bugzilla_noreply＠novell.com 27 Mar '12

27 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=728248 https://bugzilla.novell.com/show_bug.cgi?id=728248#c0 Summary: MacBook Pro needs acpi=off to boot Classification: openSUSE Product: openSUSE 12.1 Version: RC 2 Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: robert.munteanu(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=460403) --> (http://bugzilla.novell.com/attachment.cgi?id=460403) yast hwinfo from the 12.1 live cd User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 I am unable to boot a MacBook Pro 2009 model with the OpenSUSE 12.1 RC2 x86_64 live cd. The process halts shortly with a garbled screen. I am unable to get a console output to see any messages. Booting with acpi=off allows the process to contine without any problems. This machine runs a 11.4 installation with no problems. Reproducible: Always Steps to Reproduce: 1. Boot with the 12.1 RC2 live cd 2. Leave the 'normal' kernel selected 3. Proceed with running the Live CD -- 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 648544] New: Build error samba-3.5.4-5.1.2.src.rpm
by bugzilla_noreply＠novell.com 27 Mar '12

27 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=648544 https://bugzilla.novell.com/show_bug.cgi?id=648544#c0 Summary: Build error samba-3.5.4-5.1.2.src.rpm Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Samba AssignedTo: samba-maintainers(a)SuSE.de ReportedBy: ribbon(a)users.sourceforge.jp QAContact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1) When rebuild samba-3.5.4-5.1.2.src.rpm, following error happen. RPM build errors: Installed (but unpackaged) file(s) found: /usr/share/man/man1/ad2oLschema.1.gz /usr/share/man/man1/oLschema2ldif.1.gz /usr/share/man/man3/ldb.3.gz Reproducible: Always Steps to Reproduce: 1. rpmbuild -ba samba.spec fix patch is here. ------------------------------------------------------------- --- samba.spec.org 2010-09-16 06:30:30.000000000 +0900 +++ samba.spec 2010-10-22 23:24:37.879039556 +0900 @@ -1553,6 +1553,9 @@ %attr(0644,root,root) %{_datadir}/omc/svcinfo.d/smb.xml %dir %{_datadir}/samba %doc %{_mandir}/man1/smbstatus.1.* +%doc %{_mandir}/man1/ad2oLschema.1.* +%doc %{_mandir}/man1/oLschema2ldif.1.* +%doc %{_mandir}/man3/ldb.3.* %doc %{_mandir}/man5/smbpasswd.5.* %doc %{_mandir}/man8/nmbd.8.* %doc %{_mandir}/man8/smbd.8.* -- 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 704123] New: When updating packages, same version numbers in different repositories confuse YaST (and zypper?)
by bugzilla_noreply＠novell.com 27 Mar '12

27 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=704123 https://bugzilla.novell.com/show_bug.cgi?id=704123#c0 Summary: When updating packages, same version numbers in different repositories confuse YaST (and zypper?) Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ulfie_monster(a)arcor.de QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.1.19) Gecko/20110420 SUSE/2.0.14-0.2.1 SeaMonkey/2.0.14 This problem occured several times before, currently it is relevant for package libeigen2-devel which is installed from http://download.opensuse.org/repositories/KDE:/Release:/46/openSUSE_11.4 with version number 2.0.16-16.1-x86_64. Now, an update to version 2.0.16-17.1-x86_64 is available from that same repository, but with that version number the package is also available from http://download.opensuse.org/repositories/Education/openSUSE_11.4/ . YaST seems to be trying to update to that second variant and cannot be forced to choose the correct one without disabling the unwanted repo. Actually, whenever the same version number of packages to be upgraded appears in two repositories, YaST seems to be choosing the wrong one (at least I have never seen it choose the right one in these cases). The same problem may be present in zypper, please instruct me what commands I will have to issue to check this (as I am not a regular zypper user). Reproducible: Always Steps to Reproduce: 1. Start YaST2, make sure the relevant repos are set up (not sure if order in which repos are added and/or repo naming is relevant), then go to software installation module. 2. Either go to package menu and select all packages - update if newer version is available, or search for e.g. libeigen2. Look at Versions tab for libeigen2-devel. 3. According to versions tab, 2.0.16-16.1-x86_64 is installed from obs://build.opensuse.org/KDE, build service KDE4.6 with priority 94 as well as build service Education with priority 100 provides 2.0.16-17.1-x86_64, radio button for Education is checked. 4. Check KDE4.6 button (optionally choose to update package, which you will have done anyway when using the menu method above), leave tab and come back. Actual Results: Education button gets checked again, and probably the package will be upgraded from the wrong repo (never let it go this far when the same problem occured with other packages in the past). Expected Results: There should not be a vendor change unless that has been selected using the radio buttons, and if a certain repo has been selected, the selection should not automagically change to some other repo just because that provides the same version number. To temporarily fix the problem, the unwanted repo can (read: has to) be disabled before trying to upgrade the package. -- 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 19

[Bug 632770] New: talloc.pc missing from libtalloc-devel
by bugzilla_noreply＠novell.com 27 Mar '12

27 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=632770 https://bugzilla.novell.com/show_bug.cgi?id=632770#c0 Summary: talloc.pc missing from libtalloc-devel Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: openSUSE 11.3 Status: ASSIGNED Severity: Normal Priority: P5 - None Component: Samba AssignedTo: lmuelle(a)novell.com ReportedBy: lmuelle(a)novell.com QAContact: samba-maintainers(a)SuSE.de CC: samba-maintainers(a)SuSE.de, zajec5(a)gmail.com Found By: Customer Blocker: No Reported by mail and passed to bugzilla for better tracking and sharing across the team. I installed 11.3 and libtalloc: > rpm -q libtalloc-devel --filesbypkg libtalloc-devel /usr/include/talloc.h libtalloc-devel /usr/lib/libtalloc.so This package misses something like /usr/lib/pkgconfig/talloc.pc and as result I get: > pkg-config --modversion talloc Package talloc was not found in the pkg-config search path. Perhaps you should add the directory containing `talloc.pc' to the PKG_CONFIG_PATH environment variable No package 'talloc' found This doesn't allow me to compile Mesa. Can you fix this? -- 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 8

[Bug 630845] New: Windows domain membership lost after every reboot
by bugzilla_noreply＠novell.com 27 Mar '12

27 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=630845 http://bugzilla.novell.com/show_bug.cgi?id=630845#c0 Summary: Windows domain membership lost after every reboot Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Samba AssignedTo: samba-maintainers(a)SuSE.de ReportedBy: toddrme13(a)gmail.com QAContact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-1.3 Firefox/3.6.8 I used YaST Windows Domain Membership module (Samba Client) to join an AD domain. When I logout, I have a list of domains I can login to in KDM. However, every time I reboot the computer the contents of the list are gone, with only "<local>" and "Null" available. If I login as root and run the windows domain membership YaST module, then just click okay then logout again, the list is back (I don't have to pick an OU again). This sort of thing happened occasionally under openSUSE 11.2 but it happens every time under openSUSE 11.3. Reproducible: Always Steps to Reproduce: 1. Open YaSt 2. Open the Windows Domain Membership module. 3. Join a windows domain. 4. Logout 5. Verify that there is a list of domains available in your login manager which at least contains the domain you joined. 6. Reboot 7. Wait for the login screen to appear. Actual Results: The list of domains contains "<local>" and "Null", nothing else. Expected Results: The list contains "<local>" and other domains present on the network, including the one you just joined. I only tested this under KDM, not GDM or any other login manager. -- 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 15

[Bug 627165] New: winbind fails to resolve usernames if 'wins server' is defined in smb.conf
by bugzilla_noreply＠novell.com 27 Mar '12

27 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=627165 http://bugzilla.novell.com/show_bug.cgi?id=627165#c0 Summary: winbind fails to resolve usernames if 'wins server' is defined in smb.conf Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86 OS/Version: openSUSE 11.2 Status: NEW Severity: Critical Priority: P5 - None Component: Samba AssignedTo: samba-maintainers(a)SuSE.de ReportedBy: kmgramm(a)code3pse.com QAContact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-1.1 Firefox/3.6.8 I've got over 15 11.2 machines running in two different Windows 2k3 domains. All machines run samba/winbind to link them to our Windows network and all use an identical smb.conf [global] section. workgroup = WORKGROUP server string = "" realm = WORKGROUP.EXMAPLE.COM security = ADS encrypt passwords = yes password server = server01 server02 usershare allow guests = no map to guest = Bad User wins server = server01 server02 wins support = no name resolve order = wins bcast prefered master = no idmap backend = rid:WORKGROUP=20000-30000 idmap uid = 20000-30000 idmap gid = 20000-30000 winbind use default domain = yes winbind enum users = yes winbind enum groups = yes winbind refresh tickets = yes template homedir = /home/%D/%U template shell = /bin/bash I've used this basic configuration for years with no problem. That is until the samba 3.4.3 update. Ever since then I've noticed that after a while (ie. 5-10 minutes) winbind "forgets" the username list and will fail to resolve AD usernames. It is most noticeable when logged into the GUI and the screensaver locks. I can not get the system to accept my password until I drop to a terminal screen and restart winbind. Then I can jump back to the desktop and successfully unlock the screen. Also the following problems will randomly pop-up: - I sometimes get 'I have no name' when I open a terminal window. - If I run getent passwd, only local accounts are shown - net ads testjoing will return 'No logon servers' - net ads status will also show 'No logon servers' All are cured by restarting winbind. I increased the logging for samba and noticed that it appears to be having issues resolving name with WINS: - Cache entry with key = NBT/SERVER01.WORKGROUP.EXAMPLE.COM#00 couldn't be found no entry for server01.workgroup.example.com#00 found - resolve_wins: Attempting wins lookup for name server01.workgroup.example.com<0x0> - name_resolve_bcast: Attempting bcast lookup for name server01.workgroup.example.com<0x0> To test things out, I created a completely separate third AD network with two server and a single 11.2 box. This time I didn't use my standard smb.conf file; I allowed the yast wizards to attach the test box to my test domain. It ran for days with no dropped usernames and/or net ads errors. Then I started adding some of my missing global options. Once I got to 'wins server =', my test machine started acting just like all of the other ones. After 5-10 minutes it would forget usernames, testjoin would show 'No logon server', etc... Removed 'wins sever' and the system starts behaving. Reproducible: Always Steps to Reproduce: 1. Load default machine 2. Join it to a AD network 3. Add wins server = X.X.X.X option to Global section of smb.conf 4. Restart winbind 5. Wait 5-10 minutes 6. Try to resolve AD usernames Actual Results: System can't find usernames Expected Results: System successfully resolve usernames. All machines are 32 bit. I didn't try out any x64 based machines. The problem exits in 11.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 4

[Bug 524576] New: Minor problems with the oidentd-2.0.8-1.87 RPM
by bugzilla_noreply＠novell.com 27 Mar '12

27 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=524576 Summary: Minor problems with the oidentd-2.0.8-1.87 RPM Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i586 OS/Version: openSUSE 11.1 Status: NEW Severity: Minor Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: opensuse(a)jeffshantz.com QAContact: qa(a)suse.de Found By: --- I installed oidentd-2.0.8-1.87 from the openSUSE 11.1 repository. Some files are missing on the system that are reported as being installed by the RPM: js3:/home/jeff # rpm -ql oidentd /etc/init.d/oidentd /etc/oidentd.conf /etc/oidentd_masq.conf /usr/sbin/oidentd /usr/sbin/rcoidentd /usr/share/doc/packages/oidentd /usr/share/doc/packages/oidentd/AUTHORS /usr/share/doc/packages/oidentd/COPYING /usr/share/doc/packages/oidentd/COPYING.DOC /usr/share/doc/packages/oidentd/ChangeLog /usr/share/doc/packages/oidentd/ChangeLog-1.x /usr/share/doc/packages/oidentd/INSTALL /usr/share/doc/packages/oidentd/NEWS /usr/share/doc/packages/oidentd/README /usr/share/doc/packages/oidentd/TODO /usr/share/man/man5/oidentd.conf.5.gz /usr/share/man/man5/oidentd_masq.conf.5.gz /usr/share/man/man8/oidentd.8.gz /var/adm/fillup-templates/sysconfig.oidentd However, the following files do not get installed: /etc/oidentd.conf /etc/oidentd_masq.conf Furthermore, /etc/init.d/oidentd is not installed with executable permissions, causing a minor annoyance when attempting to use rcoidentd. I should mention that I also tried a source-install (oidentd-2.0.8-1.70.src.rpm is currently available in the repository) and the same problems exist with this package. -- 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 497574] New: monit status says the monit daemon is not running, even if it really is.
by bugzilla_noreply＠novell.com 27 Mar '12

27 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=497574 Summary: monit status says the monit daemon is not running, even if it really is. Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i586 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jack_csk(a)yahoo.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.9) Gecko/2009040821 Firefox/3.0.9 (.NET CLR 3.5.30729) Issue "monit status" on the shell reports the monit daemon is not running, but the monit process is indeed running: ---------- 8< ---------- snail:~ # sudo monit status monit: no status available -- the monit daemon is not running snail:~ # ps -ef | grep monit root 2349 1 0 15:52 ? 00:00:00 /usr/bin/monit -c /etc/monitrc -p /var/run/monit/monit.pid -s /var/run/monit/monit.state root 5695 4874 0 16:39 pts/2 00:00:00 grep monit ---------- 8< ---------- If I supply the pid file path by the -p flag, i.e.: sudo monit -p /var/run/monit/monit.pid status It works as expected. That makes me believe the monit process can't find the pid file, so I have to explicitly add the pid file path in /etc/monitrc: set pidfile /var/run/monit/monit.pid After said line is added to /etc/monitrc, the "monit status" command works as expected. Such issue is not found on Fedora / Ubuntu, and I believe it has to do with the different pathname for the monit.pid file. My suggestion to fix this issue is either: a. Change the path of the monit.pid to that of the default one (i.e. /var/run/monit.pid) b. Add the "set pidfile /var/run/monit/monit.pid" to /etc/monitrc by default installation Reproducible: Always Steps to Reproduce: 1. Login to OpenSUSE, open a Linux terminal 2. Make sure the monit package is installed 3. Start the monit process: service /sbin/service monit start 4. Type in: sudo monit status 5. Compare the result with: ps -ef | grep monit 6. Type in this command, and see the difference: sudo monit -p /var/run/monit/monit.pid status Actual Results: monit displays the error message, even the process is running: monit: no status available -- the monit daemon is not running Expected Results: monit reports the system status -- 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 733107] New: greylistd isn't able to start due to missing socket directory
by bugzilla_noreply＠novell.com 27 Mar '12

27 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=733107 https://bugzilla.novell.com/show_bug.cgi?id=733107#c0 Summary: greylistd isn't able to start due to missing socket directory Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: All OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: lmuelle(a)suse.com ReportedBy: lmuelle(a)suse.com QAContact: qa(a)suse.de Found By: Development Blocker: No The greylistd init script doesn't check if the path to create the socket is available. The patch attached to this bug checks if the directroy exists and if not creates one and changes the owner to mail:mail. -- 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 662093] New: clock drift in Xen pvm dom0 and 2.6.34 kernel
by bugzilla_noreply＠novell.com 27 Mar '12

27 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=662093 https://bugzilla.novell.com/show_bug.cgi?id=662093#c0 Summary: clock drift in Xen pvm dom0 and 2.6.34 kernel Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Xen AssignedTo: jdouglas(a)novell.com ReportedBy: samuel.kvasnica(a)ims.co.at QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 I observe clock drift of some second per day in pvm domUs on 2.6.34.7-xen kernel, xen 4.0.1. The dom0 clock is well synced using ntpd. /proc/sys/xen/independent_wallclock is set to 0 Using the previous 2.6.31-xen kernels, the clock in domU was well in sync with dom0. Is this supposed to work in pvm domU or did it work just by accident on 2.6.31 ? Currently, as a workaround, I'm using /proc/sys/xen/independent_wallclock is set to 1 and ntpd in each domU. Both systems where I can observe this are Nehalems / Xeon3450 and Xeon5500. Reproducible: Always Steps to Reproduce: 1.description is above 2. 3. Actual Results: clock drift Expected Results: stable clocks in domU, synced to dom0 -- 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 729547] New: Nomodeset / Fail Safe
by bugzilla_noreply＠novell.com 27 Mar '12

27 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=729547 https://bugzilla.novell.com/show_bug.cgi?id=729547#c0 Summary: Nomodeset / Fail Safe Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: i386 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: predieri(a)alice.it QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0) With my hardware configuration (old ATI video card AGP HD 3650) openSUSE 12.1 RC2 only starts: 1) in fail safe mode 2) with nomodeset option Given that other distributions (Fedora 16, Kubuntu, Chakra, etc. ..) do not have this considerable limitation (no 3D acceleration), think that this serious problem can be solved soon? Thank you for your attention John 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 3

[Bug 728318] New: KDE hardlocks when attempting to install IBM Lotus Symphony
by bugzilla_noreply＠novell.com 26 Mar '12

26 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=728318 https://bugzilla.novell.com/show_bug.cgi?id=728318#c0 Summary: KDE hardlocks when attempting to install IBM Lotus Symphony Classification: openSUSE Product: openSUSE 12.1 Version: RC 2 Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: roland(a)logikalsolutions.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 Fresh install from new live CD. Attempt to install the RPM (which installs perfectly on 11.4) and system hardlocks. Must use reset button. Reproducible: Always Steps to Reproduce: 1.download symphony 3.0 RPM 2. double click to install 3. confirm install Actual Results: hard lock Expected Results: successful install -- 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 723632] New: broken screen and no X with radeon HD 3450
by bugzilla_noreply＠novell.com 26 Mar '12

26 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=723632 https://bugzilla.novell.com/show_bug.cgi?id=723632#c0 Summary: broken screen and no X with radeon HD 3450 Classification: openSUSE Product: openSUSE 12.1 Version: Beta 1 Platform: x86-64 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: ohering(a)suse.com QAContact: qa(a)suse.de Found By: Outsourced Testing Blocker: --- After installing 12.1-beta1 on a Dell Optiplex 980 with a Radeon card the screen is all garbage once the driver modules are loaded in initrd. Later X11 does not start either, or maybe it does but the screen has the same garbage. Updating to todays Factory does not fix it either. The connected CRT is a LG 702BE. Booting with nomodeset avoids the garbage, but then X11 does not start. I was able to start and perform a graphical 12.1-beta1 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 5

[Bug 714633] New: mcstrans: use of /var/lock/subsys unsupported
by bugzilla_noreply＠novell.com 26 Mar '12

26 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=714633 https://bugzilla.novell.com/show_bug.cgi?id=714633#c0 Summary: mcstrans: use of /var/lock/subsys unsupported Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: All OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: prusnak(a)suse.com ReportedBy: lnussel(a)suse.com QAContact: qa(a)suse.de Found By: --- Blocker: --- mcstrans uses /var/lock/subsys which is unsupported on openSUSE. On openSUSE /var/lock is reserved for device lock files and must not be used for other purposes. Due to the use of tmpfs on /var/lock the subsys directory does not exist anymore either so if your package used /var/lock/subsys for any real purpose it might be silently broken already. Please fix your packge to not use /var/lock/subsys. http://en.opensuse.org/openSUSE:Packaging_checks#subsys-unsupported -- 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 727974] New: FirmwareUpdateKit: non bootable small cd images created
by bugzilla_noreply＠novell.com 26 Mar '12

26 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=727974 https://bugzilla.novell.com/show_bug.cgi?id=727974#c0 Summary: FirmwareUpdateKit: non bootable small cd images created Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: haveaniceday(a)cv-sv.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110929 Firefox/7.0.1 SeaMonkey/2.4.1 This might be a genisoimage bug. A small 3GB cd-image created with fuk (FirmwareUpdateKit) does not boot. Reproducible: Always Steps to Reproduce: 1. create a small isoimage ( ~3MB ) 2. try to start with qemu -cdrom <isoimage> Shell commands to create such images: TMPDIR=/tmp/fuk.err mkdir -p $TMPDIR cd $TMPDIR || exit 99 rm -f empty cdimage() { echo "create ${BLOCKS}M image." dd if=/dev/zero bs=1M count=$BLOCKS of=$TMPDIR/empty fuk -iso /tmp/fuk.$BLOCKS.iso * } BLOCKS=4 cdimage echo "/tmp/fuk.$BLOCKS.iso boots with qemu -cdrom /tmp/fuk.$BLOCKS.iso" BLOCKS=3 cdimage echo "/tmp/fuk.$BLOCKS.iso doesn't boot with qemu -cdrom /tmp/fuk.$BLOCKS.iso" # The small image does not boot with qemu. the larger does. Actual Results: The small image does not boot. Expected Results: The small image should boot also the size is small. genisoimage might be the cause of the error. Just adding some zeros to fwupdate.img for the 3MB image creates a bootable cd. dd if=/dev/zero count=2 bs=1M >> fwupdate.img ... genisoimage -o ... Addings just to the iso-image itself does not help. ( if qemu should be the source of the error) -- 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 12

[Bug 714621] New: policycoreutils: use of /var/lock/subsys unsupported
by bugzilla_noreply＠novell.com 26 Mar '12

26 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=714621 https://bugzilla.novell.com/show_bug.cgi?id=714621#c0 Summary: policycoreutils: use of /var/lock/subsys unsupported Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: All OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: prusnak(a)suse.com ReportedBy: lnussel(a)suse.com QAContact: qa(a)suse.de Found By: --- Blocker: --- policycoreutils uses /var/lock/subsys which is unsupported on openSUSE. On openSUSE /var/lock is reserved for device lock files and must not be used for other purposes. Due to the use of tmpfs on /var/lock the subsys directory does not exist anymore either so if your package used /var/lock/subsys for any real purpose it might be silently broken already. Please fix your packge to not use /var/lock/subsys. http://en.opensuse.org/openSUSE:Packaging_checks#subsys-unsupported -- 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 719247] New: Excessive Amount Of Dropped RX Packets On Network
by bugzilla_noreply＠novell.com 26 Mar '12

26 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=719247 https://bugzilla.novell.com/show_bug.cgi?id=719247#c0 Summary: Excessive Amount Of Dropped RX Packets On Network Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: drichard(a)largo.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20100101 Firefox/7.0 We use OpenSuse to deliver Xwindows applications to a lot of concurrent users. In versions up to OS 11.3, the network layer has never produced any problems. On SLED 11 running hundreds of Evolution sessions (no problems): linux-jobu:~ # ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:1A:4B:E6:BC:F2 inet addr:128.222.246.247 Bcast:128.222.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1453879713 errors:0 dropped:0 overruns:0 frame:0 On OpenSuse 11.3 running around hundred concurrent Firefox sessions (no problems): linux-xmvz:~ # ifconfig eth0 eth0 Link encap:Ethernet HWaddr F4:CE:46:C0:EA:A8 inet addr:128.222.233.237 Bcast:128.222.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2874124377 errors:0 dropped:17 overruns:0 frame:0 But on OpenSuse 11.4, which is used to deliver GNOME desktops to about 50 concurrent users: linux-gsss:~ # ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:1C:C4:93:DF:72 inet addr:128.222.99.243 Bcast:128.222.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:191008718 errors:0 dropped:529044 overruns:0 frame:0 The hardware is: linux-gsss:~ # lspci | grep Ether 06:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) 08:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) We did a physical to virtual copy of this server and put it into VMware as part of our disaster recovery plan and it's doing the same thing: linux-gsss:~ # ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:50:56:8B:00:30 inet addr:128.222.99.242 Bcast:128.222.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10471493 errors:0 dropped:293473 overruns:0 frame:0 The hardware on the VM server is a blade and completely different network drivers: linux-gsss:~ # lspci | grep Ether 02:00.0 Ethernet controller: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) (rev 01) 02:01.0 Ethernet controller: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) (rev 01) Here is what I have noted: - This issue seems not to slow anything down, everything is running well now. - This issue happens even when there is no user load. A fresh booted machine will begin dropping packets immediately. - We thought this was related to the upgrade from 11.3 to 11.4, and a fresh/clean install of OS 11.4 did not improve the situation - Kernel 2.6.37.6-0.7 did the same thing. Current Kernel level is : 3.0.4-2 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 2

[Bug 716757] New: Machine keeps freezing swap_free or get_page_from_freelist problem?
by bugzilla_noreply＠novell.com 26 Mar '12

26 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=716757 https://bugzilla.novell.com/show_bug.cgi?id=716757#c0 Summary: Machine keeps freezing swap_free or get_page_from_freelist problem? Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: dhall(a)wustl.edu QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 My machine keeps freezing (about once a day) on 11.4, I copy the kernel messages from /var/log/message right before and after the freeze in hopes that they explain what is happening. I have a smolt profile at http://www.smolts.org/client/show/pub_82276d41-30c9-43dc-941c-e5e8c0393589 if this provides any info you additionally need. Sep 8 12:35:07 japetus kernel: [93005.834213] swap_free: Bad swap offset entry 20000000000000 Sep 8 12:35:07 japetus kernel: [93005.834224] BUG: Bad page map in process httpd2-prefork pte:4000000000000000 pmd:1ff53067 Sep 8 12:35:07 japetus kernel: [93005.834232] addr:00007f4a1b936000 vm_flags:08000070 anon_vma: (null) mapping:ffff880132be0228 index:22f Sep 8 12:35:07 japetus kernel: [93005.834247] vma->vm_ops->fault: filemap_fault+0x0/0x4a0 Sep 8 12:35:07 japetus kernel: [93005.834310] vma->vm_file->f_op->mmap: ext4_file_mmap+0x0/0x50 [ext4] Sep 8 12:35:07 japetus kernel: [93005.834319] Pid: 29271, comm: httpd2-prefork Tainted: G B 2.6.37.6-0.7-desktop #1 Sep 8 12:35:07 japetus kernel: [93005.834333] Call Trace: Sep 8 12:35:07 japetus kernel: [93005.834364] [<ffffffff810059b9>] dump_trace+0x79/0x340 Sep 8 12:35:07 japetus kernel: [93005.834379] [<ffffffff81522672>] dump_stack+0x69/0x6f Sep 8 12:35:07 japetus kernel: [93005.834394] [<ffffffff8111d7fb>] print_bad_pte+0x1bb/0x260 Sep 8 12:35:07 japetus kernel: [93005.834407] [<ffffffff8111f474>] zap_pte_range+0x2f4/0x410 Sep 8 12:35:07 japetus kernel: [93005.834421] [<ffffffff8111f75a>] unmap_page_range+0x1ca/0x2b0 Sep 8 12:35:07 japetus kernel: [93005.834432] [<ffffffff8111fe7e>] unmap_vmas+0x12e/0x360 Sep 8 12:35:07 japetus kernel: [93005.834443] [<ffffffff81126c37>] exit_mmap+0xe7/0x1b0 Sep 8 12:35:07 japetus kernel: [93005.834458] [<ffffffff81056a07>] mmput+0x37/0x100 Sep 8 12:35:07 japetus kernel: [93005.834470] [<ffffffff8105d4aa>] exit_mm+0x11a/0x150 Sep 8 12:35:07 japetus kernel: [93005.834480] [<ffffffff8105d63a>] do_exit+0x15a/0x440 Sep 8 12:35:07 japetus kernel: [93005.834490] [<ffffffff8105dac1>] do_group_exit+0x51/0xc0 Sep 8 12:35:07 japetus kernel: [93005.834499] [<ffffffff8105db42>] sys_exit_group+0x12/0x20 Sep 8 12:35:07 japetus kernel: [93005.834511] [<ffffffff81002f8b>] system_call_fastpath+0x16/0x1b Sep 8 12:35:07 japetus kernel: [93005.834530] [<00007f4a24f56c98>] 0x7f4a24f56c98 Sep 8 12:52:45 japetus kernel: [94063.187009] general protection fault: 0000 [#1] PREEMPT SMP Sep 8 12:52:45 japetus kernel: [94063.187009] last sysfs file: /sys/devices/system/cpu/cpu1/cache/index2/shared_cpu_map Sep 8 12:52:45 japetus kernel: [94063.187009] CPU 1 Sep 8 12:52:45 japetus kernel: [94063.187009] Modules linked in: ip6t_LOG xt_tcpudp xt_pkttype ipt_LOG xt_limit snd_pcm_oss snd_mixer_oss hwmon_vid snd_seq_midi snd_seq_midi_event snd_seq edd ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_raw xt_NOTRACK ipt_REJECT iptable_raw iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables xt_conntrack nf_conntrack ip6table_filter ip6_tables x_tables cpufreq_conservative cpufreq_userspace cpufreq_powersave powernow_k8 mperf dm_mod snd_intel8x0 snd_ac97_codec ac97_bus ppdev snd_pcm snd_mpu401 snd_timer snd_mpu401_uart sr_mod joydev snd_rawmidi snd_seq_device snd parport_pc shpchp cdrom floppy pcspkr skge parport pci_hotplug asus_atk0110 snd_page_alloc soundcore sg edac_core edac_mce_amd firewire_ohci i2c_nforce2 firewire_core forcedeth crc_itu_t ns558 gameport k8temp serio_raw ext4 jbd2 crc16 nouveau ttm drm_kms_helper drm i2c_algo_bit video button fan processor ata_generic sata_sil thermal thermal_sys pata_amd sata_nv [las Sep 8 12:52:45 japetus kernel: t unloaded: preloadtrace] Sep 8 12:52:45 japetus kernel: [94063.187009] Sep 8 12:52:45 japetus kernel: [94063.187009] Pid: 29966, comm: pymol.exe Tainted: G B 2.6.37.6-0.7-desktop #1 System manufacturer System Product Name/A8N-SLI DELUXE Sep 8 12:52:45 japetus kernel: [94063.187009] RIP: 0010:[<ffffffff811030ed>] [<ffffffff811030ed>] get_page_from_freelist+0x47d/0x6c0 Sep 8 12:52:45 japetus kernel: [94063.187009] RSP: 0000:ffff88012022bb98 EFLAGS: 00010046 Sep 8 12:52:45 japetus kernel: [94063.187009] RAX: ffffea0003babb20 RBX: ffff88013ffece00 RCX: dead000000100100 Sep 8 12:52:45 japetus kernel: [94063.187009] RDX: ffffea0003babb48 RSI: 0000000000000001 RDI: 0000000000000000 Sep 8 12:52:45 japetus kernel: [94063.187009] RBP: 0000000000000002 R08: ffff88013ffece88 R09: 0000000000000010 Sep 8 12:52:45 japetus kernel: [94063.187009] R10: dead000000100100 R11: 0000000000000000 R12: 0000000000000000 Sep 8 12:52:45 japetus kernel: [94063.187009] R13: ffffea0003babb48 R14: 000000000000000d R15: 000000000000001f Sep 8 12:52:45 japetus kernel: [94063.187009] FS: 00007fdd6f8fd760(0000) GS:ffff8800bfd00000(0000) knlGS:0000000000000000 Sep 8 12:52:45 japetus kernel: [94063.187009] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 8 12:52:45 japetus kernel: [94063.187009] CR2: 00007fdd4ac4f000 CR3: 00000001292f7000 CR4: 00000000000006e0 Sep 8 12:52:45 japetus kernel: [94063.187009] DR0: Sep 8 13:16:20 japetus kernel: imklog 5.6.5, log source = /proc/kmsg started. 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 4

[Bug 523353] New: amtu-1.0.4-102.2: possible missing call to fclose
by bugzilla_noreply＠novell.com 26 Mar '12

26 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=523353 Summary: amtu-1.0.4-102.2: possible missing call to fclose Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dcb314(a)hotmail.com QAContact: qa(a)suse.de Found By: --- I just had a look at factory package amtu-1.0.4-102.2 For source code amtu-1.0.4/src/memsep.c, around line 324 is the source code for the function memsep. I notice the following line fp = fopen("/proc/self/maps", "r"); but no matching calls to fclose. Suggest add one to close this resource leak. -- 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 719382] New: Check Image Conversion Result (Missing picture of US Keyboard Layout)
by bugzilla_noreply＠novell.com 26 Mar '12

26 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=719382 https://bugzilla.novell.com/show_bug.cgi?id=719382#c0 Summary: Check Image Conversion Result (Missing picture of US Keyboard Layout) Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Development AssignedTo: fs(a)suse.com ReportedBy: ke(a)suse.com QAContact: qa(a)suse.de CC: fs(a)suse.com, giecrilj(a)stegny.2a.pl Depends on: 718743 Found By: Documentation Blocker: --- +++ This bug was initially created as a clone of Bug #718743 +++ The picture of US Keyboard Layout, as advertised in the Troubleshooting manual, is missing from the installed documentation. [...] ============================================================================= ke: "Because of a misssing dependency, the SVG to PNG transformation failed in the BS." ============================================================================= To avoid such trouble in the future, we must check whether the image conversion succeeded. If not, I'd recommend to stop immediately. Maybe, it would be sufficient to add "|| false" to the inkscape commands. -- 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 718743] New: Missing picture of US Keyboard Layout
by bugzilla_noreply＠novell.com 26 Mar '12

26 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=718743 https://bugzilla.novell.com/show_bug.cgi?id=718743#c0 Summary: Missing picture of US Keyboard Layout Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: ke(a)suse.com ReportedBy: giecrilj(a)stegny.2a.pl QAContact: ke(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0.2) Gecko/20100101 Firefox/6.0.2 The picture of US Keyboard Layout, as advertised in the Troubleshooting manual, is missing from the installed documentation. Reproducible: Always Steps to Reproduce: 1. Tell KDE Help Center to display the document "A.2. Common Problems and Their Solutions" [1] 2. Review the section "A.2.2.4. Booting from Installation Media Fails", Figure A.1. US Keyboard Layout 3. Actual Results: 2. Missing picture [2]. Expected Results: 2. Embedded picture of US Keyboard Layout [3] [1] <URL: file:///usr/share/doc/manual/opensuse-manuals_en/manual/bk01apa.html#cha.trouble > [2] <URL: file:///usr/share/doc/manual/opensuse-manuals_en/manual/images/keyboard_us.png > [3] <URL: http://www.novell.com/documentation/opensuse114/book_opensuse_startup/graph… > -- 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 12

[Bug 733130] New: sha1 sum for opensuse 12.2 repository is not correct
by bugzilla_noreply＠novell.com 26 Mar '12

26 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=733130 https://bugzilla.novell.com/show_bug.cgi?id=733130#c0 Summary: sha1 sum for opensuse 12.2 repository is not correct Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: melchiaros(a)aol.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 I´ve used build 20 64 bit network install from today. I got the message on installation system initialisation that the sha1 sum for openSUSE 12.2 repository is not correct. Reproducible: Always Steps to Reproduce: 1.get build 20 64bit for openSUSE12.2 2.start installation 3.See the error message like described Actual Results: Incorrect sha1 sum for openSUSe 12.1 repository for net install Expected Results: checksums should be correct(every time, also during development). I´ve downloaded the net iso with downthemall and sha256 check. So from this side should be no error. -- 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 715426] New: Kernel doesn't interpret the extended file attribute "security.capability"
by bugzilla_noreply＠novell.com 26 Mar '12

26 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=715426 https://bugzilla.novell.com/show_bug.cgi?id=715426#c0 Summary: Kernel doesn't interpret the extended file attribute "security.capability" Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: All OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: nice(a)titanic.nyme.hu QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 Althought CONFIG_SECURITY_FILE_CAPABILITIES is enabled at compilation time, the kernel doesn't interpret the extended file attribute "security.capability". This means that adding capabilities to a file's permitted set and enabling it's effective bit can't be used instead setuid bits, and setting inheritable (+effecive) capabilities also don't make processes being able to inherit permitted and effective capabilties form their parents. The utilities in the PRM package libcap-progs are able to correctly set filesystem (and process) capabilities, but the kernel simply omits using them. 3.0.x kernels from http://download.opensuse.org/repositories/Kernel:/stable/standard however, are implementing file capabilities correctly! It's even bigger problem that SLES11 SP1 also suffers from the same bug. Please fix it if possible! CentOS 6.0 also using 2.6.32 (like SLES11 SP1) works well, so the problem may be caused by some SuSE kernel patch. Reproducible: Always Steps to Reproduce: As root: 1. cp /bin/ping / 2. chmod 0755 /ping 3. setcap CAP_NET_RAW=pe /ping As a normal user: /ping index.hu Actual Results: ping: icmp open socket: Operation not permitted Expected Results: PING index.hu (217.20.130.97) 56(84) bytes of data. 64 bytes from sportgeza.hu (217.20.130.97): icmp_req=1 ttl=58 time=4.25 ms 64 bytes from sportgeza.hu (217.20.130.97): icmp_req=2 ttl=58 time=3.95 ms 64 bytes from sportgeza.hu (217.20.130.97): icmp_req=3 ttl=58 time=3.94 ms -- 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 732784] New: Plasma Desktop crashed after PolicyKit1-KDE crash
by bugzilla_noreply＠novell.com 26 Mar '12

26 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=732784 https://bugzilla.novell.com/show_bug.cgi?id=732784#c0 Summary: Plasma Desktop crashed after PolicyKit1-KDE crash Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: kamikazow(a)web.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20100101 Firefox/8.0 After PolicyKit1-KDE crashed because I wanted to remove a network connection (see bug 732780 ), Plasma Desktop crashed as well. Reproducible: Always Steps to Reproduce: 1. 2. 3. Application: Plasma-Desktop-Umgebung (kdeinit4), signal: Segmentation fault [Current thread is 1 (Thread 0xb57df710 (LWP 1616))] Thread 2 (Thread 0xae89eb70 (LWP 1619)): #0 0xb5b11c96 in clock_gettime () from /lib/librt.so.1 #1 0xb6d9dc35 in do_gettime (frac=0xae89e020, sec=0xae89e018) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0xb6e70206 in QTimerInfoList::updateCurrentTime (this=0x839cbcc) at kernel/qeventdispatcher_unix.cpp:339 #4 0xb6e7056a in QTimerInfoList::timerWait (this=0x839cbcc, tm=...) at kernel/qeventdispatcher_unix.cpp:442 #5 0xb6e6edc3 in timerSourcePrepareHelper (src=<optimized out>, timeout=0xae89e12c) at kernel/qeventdispatcher_glib.cpp:136 #6 0xb6e6ee5d in timerSourcePrepare (source=0x839cb98, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:169 #7 0xb5a5844c in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #8 0xb5a59207 in ?? () from /usr/lib/libglib-2.0.so.0 #9 0xb5a597fa in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #10 0xb6e6f897 in QEventDispatcherGlib::processEvents (this=0x84b5420, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #11 0xb6e4044d in QEventLoop::processEvents (this=0xae89e2b0, flags=...) at kernel/qeventloop.cpp:149 #12 0xb6e40691 in QEventLoop::exec (this=0xae89e2b0, flags=...) at kernel/qeventloop.cpp:201 #13 0xb6d4375b in QThread::exec (this=0x8532460) at thread/qthread.cpp:498 #14 0xb6e2108d in QInotifyFileSystemWatcherEngine::run (this=0x8532460) at io/qfilesystemwatcher_inotify.cpp:248 #15 0xb6d46613 in QThreadPrivate::start (arg=0x8532460) at thread/qthread_unix.cpp:331 #16 0xb6cc9a7d in start_thread () from /lib/libpthread.so.0 #17 0xb60928fe in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb57df710 (LWP 1616)): [KCrash Handler] #6 Knm::Connection::uuid (this=0x0) at /usr/src/debug/networkmanagement-0.9.2.65git.1321935457/libs/internals/connection.cpp:323 #7 0xa8d04123 in ManageConnectionWidget::editGotSecrets (this=0x876b690, valid=false, errorMessage=..., uuid=...) at /usr/src/debug/networkmanagement-0.9.2.65git.1321935457/settings/config/manageconnectionwidget.cpp:546 #8 0xa8d023b4 in ManageConnectionWidget::qt_metacall (this=0x876b690, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0xbfe7e990) at /usr/src/debug/networkmanagement-0.9.2.65git.1321935457/build/settings/config/moc_manageconnectionwidget.cpp:100 #9 0xb6e477dd in metacall (argv=0xbfe7e990, idx=41, cl=QMetaObject::InvokeMetaMethod, object=0x876b690) at kernel/qmetaobject.cpp:237 #10 QMetaObject::metacall (object=0x876b690, cl=QMetaObject::InvokeMetaMethod, idx=41, argv=0xbfe7e990) at kernel/qmetaobject.cpp:232 #11 0xb6e56710 in QMetaObject::activate (sender=0x9b112f8, m=0xa87d8ac8, local_signal_index=1, argv=0xbfe7e990) at kernel/qobject.cpp:3287 #12 0xa8779fad in NMDBusSettingsConnectionProvider::getConnectionSecretsCompleted (this=0x9b112f8, _t1=false, _t2=..., _t3=...) at /usr/src/debug/networkmanagement-0.9.2.65git.1321935457/build/backends/NetworkManager/moc_nmdbussettingsconnectionprovider.cpp:128 #13 0xa87be039 in NMDBusSettingsConnectionProvider::onConnectionSecretsArrived (this=0x9b112f8, watcher=0x9c98108) at /usr/src/debug/networkmanagement-0.9.2.65git.1321935457/backends/NetworkManager/nmdbussettingsconnectionprovider.cpp:520 #14 0xa877a1d5 in NMDBusSettingsConnectionProvider::qt_metacall (this=0x9b112f8, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0xbfe7ec48) at /usr/src/debug/networkmanagement-0.9.2.65git.1321935457/build/backends/NetworkManager/moc_nmdbussettingsconnectionprovider.cpp:106 #15 0xb6e477dd in metacall (argv=0xbfe7ec48, idx=11, cl=QMetaObject::InvokeMetaMethod, object=0x9b112f8) at kernel/qmetaobject.cpp:237 #16 QMetaObject::metacall (object=0x9b112f8, cl=QMetaObject::InvokeMetaMethod, idx=11, argv=0xbfe7ec48) at kernel/qmetaobject.cpp:232 #17 0xb6e56710 in QMetaObject::activate (sender=0x9c98108, m=0xb5c61bd8, local_signal_index=0, argv=0xbfe7ec48) at kernel/qobject.cpp:3287 #18 0xb5c448c5 in QDBusPendingCallWatcher::finished (this=0x9c98108, _t1=0x9c98108) at .moc/release-shared/moc_qdbuspendingcall.cpp:92 #19 0xb5c44973 in _q_finished (this=<optimized out>) at qdbuspendingcall.cpp:482 #20 QDBusPendingCallWatcher::qt_metacall (this=0x9c98108, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x85891a8) at moc/release-shared/moc_qdbuspendingcall.cpp:80 #21 0xb6e477dd in metacall (argv=0x85891a8, idx=5, cl=QMetaObject::InvokeMetaMethod, object=0x9c98108) at kernel/qmetaobject.cpp:237 #22 QMetaObject::metacall (object=0x9c98108, cl=QMetaObject::InvokeMetaMethod, idx=5, argv=0x85891a8) at kernel/qmetaobject.cpp:232 #23 0xb6e52305 in QMetaCallEvent::placeMetaCall (this=0x97c6318, object=0x9c98108) at kernel/qobject.cpp:535 #24 0xb6e5982f in QObject::event (this=0x9c98108, e=0x97c6318) at kernel/qobject.cpp:1226 #25 0xb635cee4 in notify_helper (e=0x97c6318, receiver=0x9c98108, this=0x8123c90) at kernel/qapplication.cpp:4481 #26 QApplicationPrivate::notify_helper (this=0x8123c90, receiver=0x9c98108, e=0x97c6318) at kernel/qapplication.cpp:4453 #27 0xb6362272 in QApplication::notify (this=0x97c6318, receiver=0x9c98108, e=0x97c6318) at kernel/qapplication.cpp:4228 #28 0xb7585681 in KApplication::notify (this=0x8117780, receiver=0x9c98108, event=0x97c6318) at /usr/src/debug/kdelibs-4.7.2/kdeui/kernel/kapplication.cpp:311 #29 0xb6e4142e in QCoreApplication::notifyInternal (this=0x8117780, receiver=0x9c98108, event=0x97c6318) at kernel/qcoreapplication.cpp:787 #30 0xb6e44bf4 in sendEvent (event=<optimized out>, receiver=<optimized out>) at kernel/qcoreapplication.h:215 #31 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x805b568) at kernel/qcoreapplication.cpp:1428 #32 0xb6e44d3c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1321 #33 0xb6e6f404 in sendPostedEvents () at kernel/qcoreapplication.h:220 #34 postEventSourceDispatch (s=0x81238a0) at kernel/qeventdispatcher_glib.cpp:277 #35 0xb5a58e2f in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #36 0xb5a59560 in ?? () from /usr/lib/libglib-2.0.so.0 #37 0xb5a597fa in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #38 0xb6e6f837 in QEventDispatcherGlib::processEvents (this=0x8123ef8, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #39 0xb6410aaa in QGuiEventDispatcherGlib::processEvents (this=0x8123ef8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #40 0xb6e4044d in QEventLoop::processEvents (this=0xbfe7f404, flags=...) at kernel/qeventloop.cpp:149 #41 0xb6e40691 in QEventLoop::exec (this=0xbfe7f404, flags=...) at kernel/qeventloop.cpp:201 #42 0xb6e44dea in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064 #43 0xb635ad64 in QApplication::exec () at kernel/qapplication.cpp:3755 #44 0xb017c7cb in kdemain (argc=1, argv=0x80e3f18) at /usr/src/debug/kde-workspace-4.7.2/plasma/desktop/shell/main.cpp:120 #45 0x0804fbcd in _start () -- 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 724410] New: RTL8191SEvB Wireless no detected during installation
by bugzilla_noreply＠novell.com 26 Mar '12

26 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=724410 https://bugzilla.novell.com/show_bug.cgi?id=724410#c0 Summary: RTL8191SEvB Wireless no detected during installation Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: luis_xp(a)yahoo.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:5.0) Gecko/20100101 Firefox/5.0 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8191SEvB Wireless LAN Controller (rev 10) Subsystem: Realtek Semiconductor Co., Ltd. Device e020 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 3

[Bug 728923] New: Black screen freeze on start with kernel-desktop 2.6.37.6-0.9.1
by bugzilla_noreply＠novell.com 26 Mar '12

26 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=728923 https://bugzilla.novell.com/show_bug.cgi?id=728923#c0 Summary: Black screen freeze on start with kernel-desktop 2.6.37.6-0.9.1 Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86 OS/Version: openSUSE 11.4 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: charles(a)totalkreyol.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 After this morning kernel update, PC can not complete boot sequence and freezes while loading the graphical desktop. Workaround: I've added "x11failsafe"to kernel boot parameters but then xorg falls back on FBDEV instead of the Radeon driver its automatic detection usually loads. Reproducible: Always Steps to Reproduce: 1. 2. 3. PC Hardware MOTHERBOARD: Asus M2N-MX (NForce chipset) CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ VIDEO: VGA compatible controller: ATI Technologies Inc RV730 PRO [Radeon HD 4650] Kernel: Linux athlas 2.6.37.6-0.9-desktop #1 SMP PREEMPT 2011-10-19 22:33:27 +0200 i686 athlon i386 GNU/Linux -- 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 728540] New: During booting up system display show splash screen with horizontal stripes and flickering
by bugzilla_noreply＠novell.com 26 Mar '12

26 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=728540 https://bugzilla.novell.com/show_bug.cgi?id=728540#c0 Summary: During booting up system display show splash screen with horizontal stripes and flickering Classification: openSUSE Product: openSUSE 12.1 Version: RC 2 Platform: i586 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: f.leerink(a)xs4all.nl QAContact: qa(a)suse.de Found By: Customer Blocker: --- Hello, I had installed openSUSE 12.1 beta on my laptop and during boot-up and normal running display was oke (Geforce FX Go53xx, nouveau (2D),nouveau gallium 7.11 (3D). I have now installed openSUSE 12.1 RC2 on my laptop and during initial boot up process system display shows splash screen with horizontal stripes and flickering. After login details are entered the display behaves normal again. During initial boot up vga=0x317 is used. Regards, Frans -- 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 619743] New: No apparent way to switch back to 'normal' after activating 'newspaper activity'
by bugzilla_noreply＠novell.com 25 Mar '12

25 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=619743 http://bugzilla.novell.com/show_bug.cgi?id=619743#c0 Summary: No apparent way to switch back to 'normal' after activating 'newspaper activity' Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: x86 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: madworm_de.novell(a)spitzenpfeil.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.6) Gecko/20100626 SUSE/3.6.6-1.1 Firefox/3.6.6 Once having switched to 'newspaper activity' I've found no way to go back to normal again. Right-clicks on the desktop are ignored, the plasma-thingy in the top right corner is gone and I didn't find anything useful in the kde setup app. 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 2

[Bug 726698] New: Num Lock not preserved during boot
by bugzilla_noreply＠novell.com 25 Mar '12

25 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=726698 https://bugzilla.novell.com/show_bug.cgi?id=726698#c0 Summary: Num Lock not preserved during boot Classification: openSUSE Product: openSUSE 12.1 Version: RC 1 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: howard.bryan.webb(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 I've got a dual boot system (same 32bit hardware): OpenSuse 11.4, and OpenSuse 12.1 RC1. I've got my BIOS set to assert/enable NumLock upon boot. I configure my systems to come up in Run Level 3, then run startx manually. On 11.4, the keyboard NumLock is ON when the login prompt is displayed. On 12.1RC1, the NumLock is OFF when the login prompt is displayed. My password has some num chars, I'd rather fix Suse than retrain my "muscle memory" depending on which version of suse I'm booting. Reproducible: Always Steps to Reproduce: 1. Boot system in Run Level 3 2. At the login prompt, observe the state of the keyboard NumLock indicator 3. Actual Results: On 12.1 RC1, keyboard NumLock is not asserted/enabled/lit Expected Results: I expect 12.1 to behave the same as 11.4 did with regard to keyboard NumLock upon boot, i.e. at the login prompt it should be asserted/enabled/lit (as I believe it was when grub took over from the BIOS). -- 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 635003] New: akonadi does not start - D-Bus problem?
by bugzilla_noreply＠novell.com 24 Mar '12

24 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=635003 https://bugzilla.novell.com/show_bug.cgi?id=635003#c0 Summary: akonadi does not start - D-Bus problem? Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: axel.braun(a)gmx.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-0.1.1 Firefox/3.6.8 I upgraded from11.2 to 11.3 with zypper dup. Now KMail etc does not work as akonadi fails to start. I deleted ~/.config/akonadi and ~/.local/share/akonadi. Starting akonadi: axel@southpole:~> akonadictl start Starting Akonadi Server... done. Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) axel@southpole:~> [akonadiserver] process 6908: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/var/lib/dbus/machine-id": Keine Berechtigung [akonadiserver] See the manual page for dbus-uuidgen to correct this issue. [akonadiserver] D-Bus not built with -rdynamic so unable to print a backtrace [akonadiserver] QIODevice::putChar: Closed device [akonadiserver] "[ [akonadiserver] 0: akonadiserver(_Z11akBacktracev+0x35) [0x8053065] [akonadiserver] 1: akonadiserver() [0x80535fc] [akonadiserver] 2: [0xffffe400] [akonadiserver] 3: [0xffffe424] [akonadiserver] 4: /lib/libc.so.6(gsignal+0x4f) [0xb70077ff] [akonadiserver] 5: /lib/libc.so.6(abort+0x180) [0xb7009140] [akonadiserver] 6: /lib/libdbus-1.so.3(+0x2c915) [0xb6ba5915] [akonadiserver] 7: /lib/libdbus-1.so.3(+0x28751) [0xb6ba1751] [akonadiserver] 8: /lib/libdbus-1.so.3(+0x28ebe) [0xb6ba1ebe] [akonadiserver] 9: /lib/libdbus-1.so.3(+0x30c4a) [0xb6ba9c4a] [akonadiserver] 10: /lib/libdbus-1.so.3(+0x247cc) [0xb6b9d7cc] [akonadiserver] 11: /lib/libdbus-1.so.3(+0x24653) [0xb6b9d653] [akonadiserver] 12: /lib/libdbus-1.so.3(+0xe66b) [0xb6b8766b] [akonadiserver] 13: /lib/libdbus-1.so.3(+0x9b3a) [0xb6b82b3a] [akonadiserver] 14: /usr/lib/libQtDBus.so.4(_ZN15QDBusConnection12connectToBusENS_7BusTypeERK7QString+0x11d) [0xb72d5dad] [akonadiserver] 15: /usr/lib/libQtDBus.so.4(_ZN15QDBusConnection10sessionBusEv+0xac) [0xb72d5f4c] [akonadiserver] 16: akonadiserver(_ZN13AkApplicationC1ERiPPc+0xb4) [0x804fc64] [akonadiserver] 17: akonadiserver(main+0x30) [0x804d2c0] [akonadiserver] 18: /lib/libc.so.6(__libc_start_main+0xfe) [0xb6ff2c0e] [akonadiserver] 19: akonadiserver() [0x804d1c1] [akonadiserver] ] [akonadiserver] " ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error) Looking ath the dbus-message, and the file /var/lib/dbus/machine-id: southpole:/home/axel # dir /var/lib/db* insgesamt 4 -rw-r--r-- 1 root root 33 2. Nov 2009 machine-id .it should be readable for everyone. No idea what to do, but I need desperately a solution. I upgraded to KDE 4.5.0 from SUSE Factory, but that did not fix it. KMail crashes, so on one on that box is able to work.... Reproducible: Always Steps to Reproduce: 1. akonadictl start 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 1

[Bug 601782] New: Update Applet - su/root password always needed (illogical default entry in policy kid?)
by bugzilla_noreply＠novell.com 24 Mar '12

24 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=601782 http://bugzilla.novell.com/show_bug.cgi?id=601782#c0 Summary: Update Applet - su/root password always needed (illogical default entry in policy kid?) Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i686 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: Martin.Seidler(a)web.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100317 SUSE/3.5.9-0.1.1 Firefox/3.5.9 I. 1. I have a problem with my "Update Applet 2.28.0" in GNOME (The same in KDE 4.3.5). It occurs when I want to make the applet do one or more suggested update(s). It always asks me for the password of superuser/root: "Authenticate : Authentication is required to update packages. [...]". I think under my installation before (11.1 maybe updated from an older version) I could tell the automatic/semi automatic updater to remember the su password (in YaST or in the authentication dialog?). 2. It is also a documentation bug: In the help manual on my computer (and in the internet) there is the possibility to make the updater remember the password via policy kit: ("Access to all privileged operations is controlled via PolicyKit." See: GNOME Documentation Library : gnome-packagekit Manual : Introduction) II. That policy make no sense: 1. The necessarily to use the root password should be reserved to actions you should think about twice and not to normal (security) updates. 2. The default policies are just contradictorily to the possible risk: 2. 1.They allow (by default) the root/someone with a root password 2.1.1 to tell the system to update complete automatically (without any human thinking or intentional acting) 2.1.2 to give (in KDE) a normal user access to the hole graphical operating system setup and configuration tool (/sbin/yast2). 2.2. But they allow not the automatic updater to remember the root password. (With a change in the policies the root may be able to change that?) 2.2. In contrast to that in my knowledge: 2.2.. The GNOME "Update Applet 2.28.0" (and the KDE equivalent) can only install the suggested updates (or not, if access to the cosing is given to that) so the risk is lower. 2.3. But by default you cannot tell the updater to save the root password. Reproducible: Always Steps to Reproduce: 1. Wait for an suggested automatic update. 2. Click on the red star with "!" 3. Click on "install updates" Actual Results: The Update Applet asks for the root password every time. Expected Results: To the user the choice/alternative the choice should be given to save the root password for the Update Applet (so it is not needed in the next case). http://www.novell.com/documentation/opensuse111/opensuse111_security/data/s… http://www.novell.com/documentation/opensuse111/opensuse111_security/?page=… http://hal.freedesktop.org/docs/PolicyKit/ -- 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 681705] New: Gwibber crashes when trying to add a Twitter account
by bugzilla_noreply＠novell.com 24 Mar '12

24 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=681705 https://bugzilla.novell.com/show_bug.cgi?id=681705#c0 Summary: Gwibber crashes when trying to add a Twitter account Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: i686 OS/Version: openSUSE 11.4 Status: NEW Severity: Critical Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: matthias_hueller(a)gmx.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b12) Gecko/20110222 Firefox/4.0b12 Gwibber crashes when trying to add a Twitter account. The console output says: (gwibber-accounts:7750): libnotify-WARNING **: Missing symbol 'gdk_screen_make_display_name' /usr/lib64/python2.7/site-packages/gwibber/gwui.py:726: GtkWarning: IA__gtk_range_set_range: assertion `min < max' failed self.scrollbar.set_range(0, len(self.messages) - 1) Reproducible: Always Steps to Reproduce: 1. Open Gwibber 2. In "Add new account for:" select "Gwibber" 3. Click the "Add" button 4. Click "Authorize" 5. Gwibber crashes :-( Actual Results: Gwibber crashes Expected Results: Authorize Gwibber to use my Twitter account. -- 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 8

[Bug 550440] New: Xserver pulls 100% cpu time
by bugzilla_noreply＠novell.com 24 Mar '12

24 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=550440 Summary: Xserver pulls 100% cpu time Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: koenig(a)linux.de QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- strace only shows select(256, [1 3 5 7 12 13 14 15 16 17 18 19 20 21 22 23 24 25 27 28 29 30 31 32 33 34 35 36 37 38 39 40 42 43], NULL, NULL, {0, 0}) = 0 (Timeout) setitimer(ITIMER_REAL, {it_interval={0, 20000}, it_value={0, 20000}}, NULL) = 0 setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 0}}, NULL) = 0 select(256, [1 3 5 7 12 13 14 15 16 17 18 19 20 21 22 23 24 25 27 28 29 30 31 32 33 34 35 36 37 38 39 40 42 43], NULL, NULL, {0, 0}) = 0 (Timeout) setitimer(ITIMER_REAL, {it_interval={0, 20000}, it_value={0, 20000}}, NULL) = 0 setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 0}}, NULL) = 0 select(256, [1 3 5 7 12 13 14 15 16 17 18 19 20 21 22 23 24 25 27 28 29 30 31 32 33 34 35 36 37 38 39 40 42 43], NULL, NULL, {0, 0}) = 0 (Timeout) setitimer(ITIMER_REAL, {it_interval={0, 20000}, it_value={0, 20000}}, NULL) = 0 setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 0}}, NULL) = 0 select(256, [1 3 5 7 12 13 14 15 16 17 18 19 20 21 22 23 24 25 27 28 29 30 31 32 33 34 35 36 37 38 39 40 42 43], NULL, NULL, {0, 0}) = 0 (Timeout) setitimer(ITIMER_REAL, {it_interval={0, 20000}, it_value={0, 20000}}, NULL) = 0 and Xorg.0.org doesn't give any hints either: harald harald > tail /var/log/Xorg.0.log (II) NV(0): 010101010101e73a808c70b014401e50 (II) NV(0): 24004bcf100000191631808c70b01440 (II) NV(0): 1e5024004bcf100000190000000f00d1 (II) NV(0): 0a32d10a28110100320c0000000000fe (II) NV(0): 004c503135345755312d544c4231009a (II) NV(0): EDID vendor "LEN", prod id 16469 (II) NV(0): Printing DDC gathered Modelines: (II) NV(0): Modeline "1920x1200"x0.0 150.79 1920 1950 2030 2060 1200 1202 1206 1220 -hsync -vsync (73.2 kHz) (II) NV(0): Modeline "1920x1200"x0.0 125.66 1920 1950 2030 2060 1200 1202 1206 1220 -hsync -vsync (61.0 kHz) (II) NV(0): EDID vendor "LEN", prod id 16469 from top: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 4458 root 20 0 490m 138m 9.9m R 100 3.6 40:56.11 Xorg 1 root 20 0 8072 752 628 S 0 0.0 0:02.10 init 2 root 15 -5 0 0 0 S 0 0.0 0:00.00 kthreadd 3 root RT -5 0 0 0 S 0 0.0 0:00.00 migration/0 no X client seems to be involved ?!? today I installed the pkg xfce4-power-manager (I'm running xfce4) and now I see two power managers running: harald harald > ps uaxOT | grep pow harald 7578 0.0 0.2 215200 9112 ? Ss 16:15 0:00 xfce4-power-manager harald 7618 0.0 0.2 205536 9064 ? Ss 16:15 0:00 gnome-power-manager root 7691 0.0 0.0 48856 2992 ? S 16:15 0:00 /usr/lib/DeviceKit-power/devkit-power-daemon killing xfce4-power-manager stops the Xserver sucking more cpu time! restarting xfce4-power-manager does not immediately trigger new cpu hog, but after a while (few minutes, while playing with xfce4-power-manager settings but not reproducable, Xorgs sucks cpu again:( killing/restarting does not generate any output in Xorg.0.log. right now I can't trigger the cpu sucking anymore, so I can't test what happens when I try to kill gmome-power-manager instead:( any idea what's going on? -- 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 11