May 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 381733] New: Firefox 3 can't handle extensions
by bugzilla_noreply＠novell.com 02 May '08

02 May '08

https://bugzilla.novell.com/show_bug.cgi?id=381733 Summary: Firefox 3 can't handle extensions Product: openSUSE 11.0 Version: Beta 1 Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Firefox AssignedTo: bnc-team-mozilla(a)forge.provo.novell.com ReportedBy: claes.backstrom(a)gmail.com QAContact: qa(a)suse.de Found By: --- I can't install or uninstall extensions in firefox 3 beta 5. The uninstall don't give any error message. But when firefox is restarted the extensions still are on the add-ons list. Saying "This add-on will be uninstalled when Firefox is restarted" When I try to install a new extension I get no error but the extension don't show up on the add-ons list. When I try to install a updated version of an extension (the one installed don't work with firefox 3) I get: "Firefox could not install the file at https://addons.mozilla.org/en-US/firefox/downloads/file/26635/adblock_plus-… because: Unexpected installation error Review the Error Console log for more details. -203" And after that it says: "This add-on will be updated when Firefox is restarted" But no matter how many restarts I do it still don't work. This is on an upgraded install from openSUSE 10.3 to openSUSE Factory. rpm -qa | grep -i firefox MozillaFirefox-2.9.95-5 beagle-firefox-0.3.5-9 rpm -qa | grep -i xulrunner mozilla-xulrunner190-1.8.99.5-7 mozilla-xulrunner190-gnomevfs-1.8.99.5-7 mozilla-xulrunner181-1.8.1.13-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 7

[Bug 381635] New: please rename mozilla-xulrunner190-lang
by bugzilla_noreply＠novell.com 02 May '08

02 May '08

https://bugzilla.novell.com/show_bug.cgi?id=381635 Summary: please rename mozilla-xulrunner190-lang Product: openSUSE 11.0 Version: Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox AssignedTo: bnc-team-mozilla(a)forge.provo.novell.com ReportedBy: coolo(a)novell.com QAContact: qa(a)suse.de Found By: --- -lang is taken for packages going to be bundled in a noarch package. As xulrunner lives in /usr/lib64 it can't be noarch. So please name it -translations as the rest of firefox. -- 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 381673] New: Adding repository uses old-style flickering progress display
by bugzilla_noreply＠novell.com 02 May '08

02 May '08

https://bugzilla.novell.com/show_bug.cgi?id=381673 Summary: Adding repository uses old-style flickering progress display Product: openSUSE 11.0 Version: Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: robin.knapp(a)fujitsu-siemens.com QAContact: jsrain(a)novell.com Found By: --- The progress for refreshing repos has been nicely improved, but adding a (community) repository still opens a new window for each 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 12

[Bug 385970] New: locks on non-existing packages are apparently ineffective
by bugzilla_noreply＠novell.com 02 May '08

02 May '08

https://bugzilla.novell.com/show_bug.cgi?id=385970 Summary: locks on non-existing packages are apparently ineffective Product: openSUSE 11.0 Version: Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: dmueller(a)novell.com QAContact: dmacvicar(a)novell.com Found By: --- oldboy:/suse/dmueller/src/rpm # rpm -q strigi package strigi is not installed oldboy:/suse/dmueller/src/rpm # zypper ll # | Name | Type | Repository --+-----------------+---------+----------- 1 | bash-completion | package | (any) 2 | strigi | package | (any) oldboy:/suse/dmueller/src/rpm # zypper dup -r stable-x86 Reading installed packages... The following packages are going to be downgraded: kde4-l10n-ja kde4-l10n-en_GB kde4-l10n-de The following NEW package is going to be installed: strigi The following packages are going to change vendor: kde4-l10n-ja kde4-l10n-en_GB kde4-l10n-de -- 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 346758] New: the logon screen is blocking
by bugzilla_noreply＠novell.com 02 May '08

02 May '08

https://bugzilla.novell.com/show_bug.cgi?id=346758 Summary: the logon screen is blocking Product: openSUSE 10.3 Version: Final Platform: x86 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: X.Org AssignedTo: sndirsch(a)novell.com ReportedBy: serge.tellier(a)opns.be QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: Field Engineer Since latest update, sometimes, my logon screen is blocking before viewing username/password (always the grey screen) I'm not alone on my company ! Serge Tellier serge.tellier(a)opns.be -- 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 345035] New: problem with Xsetup for compiz in xorg 7. 3 from Xorg74 sndirsch repository
by bugzilla_noreply＠novell.com 02 May '08

02 May '08

https://bugzilla.novell.com/show_bug.cgi?id=345035 Summary: problem with Xsetup for compiz in xorg 7.3 from Xorg74 sndirsch repository Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Blocker Priority: P5 - None Component: X.Org AssignedTo: sndirsch(a)novell.com ReportedBy: sebastien.rohaut(a)free.fr QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: Customer Created an attachment (id=185317) --> (https://bugzilla.novell.com/attachment.cgi?id=185317) Xorg.0.log details Hi, Due to a mail exchange between Matthias Hopf and me here is a bug report. I'm using your Xorg74 experimental repository (from Stefan Dirsch) for Opensuse 10.3 to test your lastest packages. I put Severity to Blocker because of this bug xdm/kdm/gdm is not launched and users can't connect. It seems that /etc/X11/xdm/Xsetup in xorg-x11-7.3-24.1 has a "little" problem. I'm using the lastest flgrx ATI driver (8.43.2) on a ATI RADEON XPRESS 200M (II) fglrx(0): VESA VBE OEM: ATI RADEON XPRESS 200 Series (II) fglrx(0): VESA VBE OEM Software Rev: 1.0 (II) fglrx(0): VESA VBE OEM Vendor: ATI Technologies Inc. (II) fglrx(0): VESA VBE OEM Product: RS48 (II) fglrx(0): VESA VBE OEM Product Rev: 01.00 and when I start X11, it stops loading just before launching xdm or other graphical session manager (in fact kdm for me). Under a console (Ctrl+Alt+F1), I can see two process : glxinfo grep -q GLX_EXT_texture_from_pixmap launched by Xsetup, especially here, line 233-245 : if test -x $glxinfo -a -x $compiz; then if $glxinfo | grep -q GLX_EXT_texture_from_pixmap ; then if test "$gdm" = "yes" ; then $compiz --sm-disable decoration fade place & if test -x $gwd ; then $gwd --minimal & fi fi fi fi If I manually kill glxinfo kdm/xdm/gdm is launched and all is working well. It don't know why theses instructions are not working here, because when I'm logging and opening a X console (xterm, kconsole), it works : seb@p64p17bicb3:/etc/X11/xdm> glxinfo | grep -q GLX_EXT_texture_from_pixmap echo $? 0 Another thing, it seems that this code is used only if gdm is used, not kdm, so it is possible to modify as this to test it (it works for me because I use KDE) : # # Compiz # if test "$gdm" = "yes" ; then if test -x $glxinfo -a -x $compiz; then if $glxinfo | grep -q GLX_EXT_texture_from_pixmap ; then $compiz --sm-disable decoration fade place & if test -x $gwd ; then $gwd --minimal & fi fi fi fi Last : This problem occurs on my professional desktop computer (with ATI). At home, with the same Xorg release and a Nvidia card (with the lastest commercial nvidia driver), it works perfectly. It seems it's an issue with this release of Xorg and the use of fglrx driver. I will make some additional tests tomorrow at work as described by Matthias Hopf in his answer (in the next comment). I also have a notebook (HP NC6000) with Radeon 9600, I will upgrade it to this bugging release of Xorg and fglrx driver to see if I have the same problem. -- 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 26

[Bug 380267] New: All wxGTK applications are crashing on exit
by bugzilla_noreply＠novell.com 02 May '08

02 May '08

https://bugzilla.novell.com/show_bug.cgi?id=380267 Summary: All wxGTK applications are crashing on exit Product: openSUSE 11.0 Version: Factory Platform: x86 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: andreas.hanke(a)gmx-topmail.de QAContact: sndirsch(a)novell.com Found By: --- All wxGTK applications are crashing on exit. I noticed that with aMule (not just the main application, also the other tools like alc and wxcas - not part of the distribution), but it happens also with sffview (which is part of the distribution). The console output looks like this: # sffview /usr/share/doc/packages/sffview/testfax.sff 26584c1d-912f-28b8-09828839-4c715952 is dumped gdb backtrace (with sffview-debuginfo, wxGTK-debuginfo and glibc-debuginfo installed) looks like this: # gdb --args sffview /usr/share/doc/packages/sffview/testfax.sff [...] (gdb) run Starting program: /usr/bin/sffview /usr/share/doc/packages/sffview/testfax.sff [Thread debugging using libthread_db enabled] [New Thread 0xb6afb6d0 (LWP 14583)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb6afb6d0 (LWP 14583)] 0xb6772990 in ?? () (gdb) bt full #0 0xb6772990 in ?? () No symbol table info available. #1 0xb7507931 in *__GI_exit (status=0) at exit.c:75 atfct = <value optimized out> onfct = <value optimized out> cxafct = (void (*)(void *, int)) 0xb6772990 old = <value optimized out> #2 0xb74f05fe in __libc_start_main (main=0x8056c40 <main>, argc=2, ubp_av=0xbfbba484, init=0x805ba60 <__libc_csu_init>, fini=0x805ba50 <__libc_csu_fini>, rtld_fini=0xb7faf650 <_dl_fini>, stack_end=0xbfbba47c) at libc-start.c:252 result = 0 unwind_buf = {cancel_jmp_buf = {{jmp_buf = {-1218342924, 0, 134557696, -1078221736, -2027805362, 1851872095}, mask_was_saved = 0}}, priv = { pad = {0x0, 0x0, 0xb7fb4890, 0xb74f051d}, data = {prev = 0x0, cleanup = 0x0, canceltype = -1208268656}}} not_first_call = <value optimized out> #3 0x08053021 in _start () No locals. -- 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 346759] New: KDESU: No longer accepts root password
by bugzilla_noreply＠novell.com 02 May '08

02 May '08

https://bugzilla.novell.com/show_bug.cgi?id=346759 Summary: KDESU: No longer accepts root password Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: linux(a)sdprice.plus.com QAContact: qa(a)suse.de Found By: Customer After a period of using SuSE 10.3 (and installing various packages) I have ended up in the situation where kdesu no longer accepts the root password with: "Incorrect password; please try again" I can happily run su from the command line (using root password); but am unable to get kdesu to accept the same password. This has now been seen on 2 totally different machines, both running SuSE 10.3 GM. Unfortunately, I'm not sure when kdesu stopped working. I'm pretty sure it worked just after the virgin install. All installed packages came from the approved repositories (i.e. those provided in 'community repositories' yast2 dialog) -- 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 381299] New: kde4-updater progress on top of screen
by bugzilla_noreply＠novell.com 02 May '08

02 May '08

https://bugzilla.novell.com/show_bug.cgi?id=381299 Summary: kde4-updater progress on top of screen Product: openSUSE 11.0 Version: Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: tgoettlicher(a)novell.com ReportedBy: msvec(a)novell.com QAContact: qa(a)suse.de Found By: --- Created an attachment (id=208935) --> (https://bugzilla.novell.com/attachment.cgi?id=208935) screenshot Instead of the bottom, like usual (see screenshot). -- 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 340311] New: kdesu should name the user whose password is being requested
by bugzilla_noreply＠novell.com 02 May '08

02 May '08

https://bugzilla.novell.com/show_bug.cgi?id=340311 Summary: kdesu should name the user whose password is being requested Product: openSUSE 10.3 Version: Final Platform: 32bit OS/Version: openSUSE 10.3 Status: NEW Severity: Enhancement Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: carlos.lange(a)ualberta.ca QAContact: qa(a)suse.de Found By: --- When /etc/sudoers is modified to authenticate with user's password, kdesu also authenticates only with user's password, but the pop-up window text mentions incorrectly the root password. In order to give every student in the lab control over their workstation without needing the root password, I modified /etc/sudoers with: User_Alias FULLADMIN = clange,slange Defaults:FULLADMIN authenticate FULLADMIN PLACE = PASSWD: ALL Since kdesu wraps around sudo, it also requires the user password to authenticate. This is a feature of kdesu, not a bug, as explained in Bug 339922. But sudo informs correctly which password is being requested: > sudo mount clange's password: (or slange's password if slange is logged in) while the kdesu pop-up window misleadingly asks to "Please enter the Administrator (root) password to continue." I suggest that the pop-up window mentions the proper user, whose password is being requested, as with sudo in the command line. -- 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