August 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 398512] New: button labeling in CASA module
by bugzilla_noreply＠novell.com 07 Mar '09

07 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=398512 Summary: button labeling in CASA module Product: openSUSE 11.0 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mschmidkunz(a)novell.com QAContact: jsrain(a)novell.com Found By: --- According to FATE 120373 the buttons in the main dialog should be labeled "Cancel"/"OK". -- 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 372328] New: CASA Module Does Not Close
by bugzilla_noreply＠novell.com 07 Mar '09

07 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=372328 Summary: CASA Module Does Not Close Product: openSUSE 11.0 Version: Alpha 3 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mschmidkunz(a)novell.com QAContact: jsrain(a)novell.com Found By: --- When clicking on close ("x"-Symbol) in the window decoration the module is not closed. As Benji mentioned in a similar bug: I expect it's using Wizard::UserInput which maps `cancel to `back. The close button emits `cancel global any UserInput() { any input = UI::UserInput(); if ( input == `accept ) return `next; if ( input == `cancel ) return `back; return input; } -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 6

[Bug 420488] New: KDE: KDE3 has packages with lower release number than official 11.0 packages
by bugzilla_noreply＠novell.com 07 Mar '09

07 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=420488 Summary: KDE:KDE3 has packages with lower release number than official 11.0 packages Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: cmorve69(a)yahoo.es QAContact: adrian(a)novell.com CC: zypp-maintainers(a)forge.provo.novell.com Found By: --- KDE:KDE3 repo has the following packages: - fdupes-1.40-43.4 - fileshareset-2.0-95.1 - libakode-2.0.2-148.12 - suse-desktop-utils-1.0-16.1 11.0 comes with: - fdupes-1.40-82.1 - fileshareset-2.0-501.2 - libakode-2.0.2-151.1 - suse-desktop-utils-1.0-24.1 They are the same versions but KDE:KDE3 release numbers are lower. Now a normal user wants to update KDE 3.5.9 from 11.0 to KDE 3.5.10 from KDE:KDE3 and uses "zypper -v up -t package" or "zypper -v dup". He will end with kdemultimedia3 from KDE 3.5.10, that was built against libakode-2.0.2-148.12... but with libakode-2.0.2-151.1. Not sure where the fix should go, so I CC zypp-maintainers. pd. Smart will downgrade the packages if KDE:KDE3 has a higher priority than the official repo. pd2. No, I have not seen any real problem because the different libakode... but openSUSE rebuilds so many packages for a reason. -- 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 408897] New: git-svn 'fetch' broke in opensuse 11.0
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=408897 Summary: git-svn 'fetch' broke in opensuse 11.0 Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- The only message I get is this (between ===): === Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi/SVN/Core.pm line 584. Error from SVN, (220001): Item is not readable: === -- 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 408818] New: apparmor parser hangs when started after updating to 11.0
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=408818 Summary: apparmor parser hangs when started after updating to 11.0 Product: openSUSE 11.0 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: AppArmor AssignedTo: jjohansen(a)novell.com ReportedBy: poeml(a)novell.com QAContact: qa(a)suse.de Found By: --- I updated from 10.1 to 11.0, and to be safe I disabled apparmor on first boot, so to make sure that everything else works first. Now, time to start apparmor and see if the profiles still work / adjust / update them. Problem: it doesn't start; it hangs when parsing a profile: root@doozer ~ # rcapparmor start Mounting securityfs on /sys/kernel/security done Loading AppArmor profiles Found reference to variable PROC, but is never declared Profile /etc/apparmor.d/bin.hostname failed to load [hanging here] root 2107 0.0 0.1 6236 1132 ? Ss Jul11 0:00 /usr/sbin/sshd -o PidFile=/var/run/sshd.init.pid root 21717 0.0 0.2 8820 2692 ? Ss 10:38 0:00 \_ sshd: root@pts/1 root 21719 0.6 0.3 6000 3480 pts/1 Ss 10:38 0:00 | \_ -zsh root 21761 0.0 0.1 3180 1516 pts/1 S+ 10:38 0:00 | \_ /bin/sh /sbin/rcapparmor start root 21801 101 14.4 150008 148432 pts/1 R+ 10:38 0:19 | \_ /sbin/apparmor_parser -I/etc/apparmor.d --add /etc/apparmor.d/usr.sbin.httpd2-prefork The httpd2-prefork profile (I can attach it privately) contains some hats for vhosts, and I must admit that I always had problems to get the profile right with 10.1; the logging was known to be difficult with 10.1, so that it was hard to get it right; I was looking forward to finish the profile after the 11.0 update ;) however, the profile could well be broken. -- 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 350590] New: apache will not start with the subversion module installed
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=350590 Summary: apache will not start with the subversion module installed Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: Apache AssignedTo: bnc-team-apache(a)forge.provo.novell.com ReportedBy: j.p.drawneek(a)durham.ac.uk QAContact: qa(a)suse.de Found By: Customer Sorry if this is a dup but i could find this in the bug tree Ok the ordering of loading modules is wrong for subversion it is: authz_svn dav_svn when it should be: dav_svn authz_svn So out the box you get this error Starting httpd2 (prefork) httpd2-prefork: Syntax error on line 116 of /etc/apach e2/httpd.conf: Syntax error on line 28 of /etc/apache2/sysconfig.d/loadmodule.co nf: Cannot load /usr/lib64/apache2/mod_authz_svn.so into server: /usr/lib64/apac he2/mod_authz_svn.so: undefined symbol: dav_svn_split_uri The really kicker is that when ever you edit the file with yast it swaps them back, so I also guess this would be the case for any patch, so your apache2 will break - yay Also dav should be turned on when dav_svn is turned on as it depends on it, but thats a problem with the subversion-server package. Also how the hell do you change your email with this bug system??? -- 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 382889] New: logrotate's "mailfirst" option is not correctly working
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=382889 Summary: logrotate's "mailfirst" option is not correctly working Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: andreas.pfaller(a)gmail.com QAContact: qa(a)suse.de Found By: --- logrotate mails the "about-to-expire" files in addition to the "just-rotated" files despite the use of the "mailfirst" option if mailing of logs is requested with the "mail" option. -- 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 337072] New: XEN Can't start a Domain: Error: (12, ' Cannot allocate memory')
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=337072 Summary: XEN Can't start a Domain: Error: (12, 'Cannot allocate memory') Product: openSUSE 10.3 Version: Final Platform: x86 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Xen AssignedTo: cgriffin(a)novell.com ReportedBy: franz.fleischmann(a)landshut.org QAContact: qa(a)suse.de Found By: --- Created an attachment (id=180802) --> (https://bugzilla.novell.com/attachment.cgi?id=180802) Output from dmesg On our xen-server there was running during the last week no domain. Today I started a PVM-Domain without any problems. When I try to start a HVM-Domain i get the error-msg: Error: (12, 'Cannot allocate memory'). But this should not be possible. The system has 12 GB memory and the pvm-domain uses only 396 M. The free command in the dom0 shows more than 11 GB free: total used free shared buffers cached Mem: 12059648 797592 11262056 0 170612 277596 -/+ buffers/cache: 349384 11710264 Swap: 506036 0 506036 After reducing the memory in Dom0 to 1 GB with xm mem-set Domain-0 1024 i tried to start the PVM-domain again and the system freezes. After a reboot of the system there is no problem to start both PVM and HVM-domains. For better diagnostics i attached some files. Most important are the output from "xm desg" and the xend.log -- 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 327391] New: Pidgin doesn't use keyring
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=327391 Summary: Pidgin doesn't use keyring Product: openSUSE 10.3 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: alberto.passalacqua(a)tin.it QAContact: qa(a)suse.de Found By: --- Pidgin doesn't save passwords in GNOME keyring, but it uses its own file. -- 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 14

[Bug 335555] New: scim/skim input method causes serious focus problems
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=335555 Summary: scim/skim input method causes serious focus problems Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: sndirsch(a)novell.com ReportedBy: kq8z67r6309fo9001(a)sneakemail.com QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Under a variety of circumstances, having skim running can cause applications to permanently lose the ability to receive keyboard input. Many programs seem to be affected, including xterm, opera, swing-based java applications, but triggering the bug reliably is not simple. Sometimes switching desktops will do it. Sometimes rapidly opening and closing a dialog, or otherwise changing focus within an application will do it. The following is the only completely reliable trigger I've found: 1. Log in to kde, making sure skim starts (it appears to do so automatically if it's installed) 2. Start openoffice.org calc 3. ctrl+f to open the find dialog 4. esc to close the find dialog The result is that OO apparently no longer receives keyboard events. The program itself operates properly otherwise, and responds to the mouse. As mentioned previously, there are many other instances where similar results can be obtained, though in some cases the application can be revived up opening a new window, typing in it, and closing it. In other cases, it appears to be a complete loss. Using the gtk-scim panel applet rather than skim or using a different window manager seems to influence some of these bugs, but never eliminates them. This is with: skim-1.4.5-120 scim-anthy-1.2.4-28 scim-m17n-0.2.2-70 scim-1.4.7-24 scim-qtimm-0.9.4-121 installed and no manual configuration. I've verified this on two 10.3 installs and a 10.2 install, so this has probably been around for awhile. Sorry if this is a duplicate: Novell bugzilla's search has just been returning "gateway unreachable" for me. -- 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 16