January 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 434546] New: Sensors reports seperate core temp as much higher than overall CPU temp
by bugzilla_noreply＠novell.com 07 Jan '09

07 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=434546 Summary: Sensors reports seperate core temp as much higher than overall CPU temp Product: openSUSE 11.1 Version: Beta 2 Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: quentin.jackson(a)exclamation.co.nz QAContact: qa(a)suse.de Found By: Customer As above, but as an example on my quad core I have cores 1-4 at 54, 37, 37, 40 degrees C and the overall CPU reads 14 degrees C. Obviously this can't be right, can it? -- 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 412567] New: encfs: all broken, refuses to mount
by bugzilla_noreply＠novell.com 07 Jan '09

07 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=412567 User jengelh(a)gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=412567#c408791 Summary: encfs: all broken, refuses to mount Product: openSUSE 11.0 Version: Final Platform: x86 OS/Version: Linux Status: NEW Severity: Blocker Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jengelh(a)gmx.de QAContact: qa(a)suse.de Found By: Customer encfs 1.4 cannot read its own volumes anymore (neither encfs6, as 1.4 creates, nor encfs5 containers as 1.3 creates, see bug #408791). Please downgrade to 1.3 and submit this "update". 05:42 linux-84vy:/dev/shm > encfs $PWD/{a,b} Creating new encrypted volume. Please choose from one of the following options: enter "x" for expert configuration mode, enter "p" for pre-configured paranoia mode, anything else, or an empty line will select standard mode. ?> p Paranoia configuration selected. Configuration finished. The filesystem to be created has the following properties: Filesystem cipher: "ssl/aes", version 2:1:1 Filename encoding: "nameio/block", version 3:0:1 Key Size: 256 bits Block Size: 1024 bytes, including 8 byte MAC header Each file contains 8 byte header with unique IV data. Filenames encoded using IV chaining mode. File data IV is chained to filename IV. -------------------------- WARNING -------------------------- The external initialization-vector chaining option has been enabled. This option disables the use of hard links on the filesystem. Without hard links, some programs may not work. The programs 'mutt' and 'procmail' are known to fail. For more information, please see the encfs mailing list. If you would like to choose another configuration setting, please press CTRL-C now to abort and start over. Now you will need to enter a password for your filesystem. You will need to remember this password, as there is absolutely no recovery mechanism. However, the password can be changed later using encfsctl. New Encfs Password: Verify Encfs Password: 05:42 linux-84vy:/dev/shm > l total 6040 drwxrwxrwt 5 root root 140 2008-07-28 05:42 . drwxr-xr-x 13 root root 4380 2008-07-28 05:26 .. drwxr-xr-x 2 jengelh users 60 2008-07-28 05:42 a drwxr-xr-x 2 jengelh users 60 2008-07-28 05:42 b drwxr-xr-x 3 root root 260 2008-07-28 05:26 sysconfig 05:42 linux-84vy:/dev/shm > fusermount -u b 05:42 linux-84vy:/dev/shm > encfs $PWD/{a,b} encfs: ./boost/spirit/utility/impl/chset/range_run.ipp:123: void boost::spirit::utility::impl::range_run<CharT>::set(const boost::spirit::utility::impl::range<CharT>&) [with CharT = char]: Assertion `r.is_valid()' failed. Aborted -- 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 42

[Bug 462829] New: YaST does not allow to remove network scanner
by bugzilla_noreply＠novell.com 07 Jan '09

07 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=462829 Summary: YaST does not allow to remove network scanner Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dieter.jurzitza(a)t-online.de QAContact: jsrain(a)novell.com Found By: --- After having configured my network scanner I added a second scanner and tried to remove the network scanner in YaST. Whenever I highlight the entry: Mustek ScanExpress 12000SP an net:172.16.41.10:mustek:/dev/sg2 and say "Löschen" I end on the net-configuration page for scanners, I cannot remove this entry by any means. In this regard "Bearbeiten" and "Löschen" have identical meaning what should not be the case. -- 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 463361] New: Firefox stops working
by bugzilla_noreply＠novell.com 07 Jan '09

07 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=463361 Summary: Firefox stops working Product: openSUSE 11.1 Version: Final Platform: PC OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Firefox AssignedTo: bnc-team-mozilla(a)forge.provo.novell.com ReportedBy: kristjan.ugrin(a)gmail.com QAContact: qa(a)suse.de Found By: --- This is the second time I got into this situation, seems like firefox breaks down after update. /usr/lib/firefox/firefox: symbol lookup error: /usr/lib/xulrunner-1.9.0.5/libxul.so: undefined symbol: PR_GetEnv mozilla-xulrunner190 1.9.0.5-1.1 (from updates) MozillaFirefox 3.0.5-1.1 (from updates) Reinstalling doesn't help (and purging xulrunner from disk), neither downgrading. I'm also not sure what is causing this. Only unstable software running here is KDE 4.2 from unstalbe repositories, but I cannot see how this would interfere. -- 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 464086] New: Cannot browse or send files from other bluetooth devices (mobile phones,etc...)
by bugzilla_noreply＠novell.com 07 Jan '09

07 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=464086 Summary: Cannot browse or send files from other bluetooth devices (mobile phones,etc...) Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE3 AssignedTo: kde-maintainers(a)suse.de ReportedBy: extigyro(a)abv.bg QAContact: qa(a)suse.de Found By: Localization Cannot browse or send files from other bluetooth devices. When i try to access the bluetooth on my Laptop (HP NX9420) through KBluetooth, Konqueror just says: The process for the bluetooth protocol died unexpectedly. -- 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 460557] New: ftp repository of 11.1 contains ia64 directory
by bugzilla_noreply＠novell.com 07 Jan '09

07 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=460557 Summary: ftp repository of 11.1 contains ia64 directory Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: adrian(a)novell.com ReportedBy: aj(a)novell.com QAContact: qa(a)suse.de Found By: --- We do not need the ia64 directory - and in the openSUSE Build Service we do not need the ia64 packages build at all, they do not need to be generated at all. So, my proposal is to not generate the ia64 rpms at all in the openSUSE Build Service. -- 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 459215] New: Iscan crashes when scanning to printer
by bugzilla_noreply＠novell.com 07 Jan '09

07 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=459215 User russbucket(a)nwi.net added comment https://bugzilla.novell.com/show_bug.cgi?id=459215#c1962 Summary: Iscan crashes when scanning to printer Product: openSUSE 11.0 Version: Final Platform: 64bit OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: russbucket(a)nwi.net QAContact: qa(a)suse.de Found By: Community User On Sunday 14 December 2008 16:41:39 Olaf Meeuwissen wrote: > Putting this back on sane-devel. > > Russ Fineman <russbucket(a)nwi.net> writes: > > On Thursday 11 December 2008 15:20:42 you wrote: > >> Russ Fineman <russbucket(a)nwi.net> writes: > >> > Can anyone tell me where to file bug report for Iscan? > >> > >> https://www.avasys.jp/secure/english/linux_e/support_form.html > >> > >> but if the problem is with any of the SUSE provides packages please > >> report it with SUSE. > >> > >> > I can scan to a file just fine (Epson CX6600) but try as I can to > >> > scan to a printer and Iscan just closes down. > >> > >> What do you mean with "just closes down"? > > > > GUI interface just disappears (closes) from the screen. > That's a bug. > > >> Can you scan to PNG file? If yes, change the print command (Click the > >> Configuration button) to > >> > >> cat > `date +%Y-%m-%d`.png > > > > No if I scan to file, and try to select PNG or TIFF they are greyed out. > > I can only select PNM or JPEG. See Below. > > Allright. No PNG support. That means you can't print because that > relies on an intermediate PNG file. You shouldn't have been able to > even select scanning to printer in that case. I can select scan to printer but GUI diseapears as above and get the error message. > > > [snip] > > > >> > Using Iscan version Epkowa driver from AVASYA. OpenSUSE 11.0. Ran > >> > fine on 10.3 and previous versions. Thought I saw something about > >> > have to use older version iscan-proprietary-drivers-2.10.0.1-10.1 > >> > iscan-2.10.0.1-21.1 iscan-firmware-2.8.0.1-48.1 > > You don't mention the iscan version you use, but I am assuming you are > using a self-built version of 2.12.0 or later. The following is based > on that assumption. No 2,12 is 2.10 as below. I can download 2.12 and compile it. See if that corrects problem. > > > [snip] > > The problem appears to be Iscan looking for libpng0.so shared object > > file: error message: terminate called after throwing an instance of > > 'std::runtime_error' > > what(): libpng.so: cannot open shared object file: No such file or > > directory > > > > there are two references to libpng.so: > > lrwxrwxrwx 1 root root 11 2008-11-13 10:18 /usr/lib64/libpng.so -> > > libpng12.so > > > > -rwxr-xr-x 1 root root 21522 2008-10-07 08:13 > > /usr/lib64/compiz/libpng.so > > > > Not sure if this is a SUSE problem or Iscan. Should the libpng.so link to > > libpng12.so? > > It's a problem with both really. You can work around this by running > iscan from the command-line as follows: > > LTDL_LIBRARY_PATH=/usr/lib64 iscan using this command starts iscan, selecting scan to printer still shows png and .tiff greyed out. cliclking scan gives following error: finemanruss@linux-f836:/usr/lib64> ltdl_library_path=/usr/lib64 iscan terminate called after throwing an instance of 'std::runtime_error' what(): /usr/lib64/libpng12.so.0: wrong ELF class: ELFCLASS64 Aborted I am in the process of reporting to Novell bugzilla now. Also tried to enter it on https://www.avasys.jp/secure/english/linux_e/support_form.html but I get a list of apache and java errors. says cannot contact server. Do I need to log on some where to report this? </snip> > If you file a bug report with SUSE, let me know (so I can follow it > and don't have to do it myself). You should probably file it against > the glibc package. > > Hope this helps, > -- > Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS Corporation > FSF Associate Member #1962 Help support software freedom > http://www.fsf.org/jf?referrer=1962 -- Russ Registered Linux User #441463 -- 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 456374] New: kontact crashes when accessing groupwise mail calender folder
by bugzilla_noreply＠novell.com 07 Jan '09

07 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=456374 Summary: kontact crashes when accessing groupwise mail calender folder Product: openSUSE 11.1 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: mc(a)novell.com QAContact: qa(a)suse.de Found By: Development With RC2 I had a new crash when I try to open the GW mail calender folder. This was not happen with RC1 or lower. Backtrace with debug symbols follow. -- 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 459681] New: korganizer4 unable to start after crash
by bugzilla_noreply＠novell.com 07 Jan '09

07 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=459681 Summary: korganizer4 unable to start after crash Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: rplewe(a)novell.com QAContact: qa(a)suse.de Found By: --- korganizer4 crashed while I tried to configure it. After the crash, the program is unable to start, there is simply no feedback at all starting it from the menu. Starting it from the command line results in: > /usr/bin/korganizer korganizer(27649): ""LastLoad" - conversion of "-4713,1,1,0,0,0" to QDateTime failed" korganizer(27649): ""LastSave" - conversion of "-4713,1,1,0,0,0" to QDateTime failed" korganizer(27649): ""LastLoad" - conversion of "-4713,1,1,0,0,0" to QDateTime failed" korganizer(27649): ""LastSave" - conversion of "-4713,1,1,0,0,0" to QDateTime failed" korganizer(27649)/kdepimlibs (kcal): Cannot read uid map file ' "/suse/rplewe/.kde4/share/apps/kcal/uidmaps/remote_ZVtgh3Nawy" ' icalerror.c:104: BADARG: Bad argument to function korganizer: icalerror.c:106: icalerror_set_errno: Assertion `0' failed. KCrash: Application 'korganizer' crashing... sock_file=/suse/rplewe/.kde4/socket-reboot/kdeinit4__0 <unknown program name>(27647)/: Communication problem with "korganizer" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " And a backtrace is generated, see attachment. -- 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 460762] New: pam_mount stuff overwritten in /etc/pam.d/login and /etc/ pam.d/xdm, resulting *NON-ACESSIBLE* encrypted homedirs
by bugzilla_noreply＠novell.com 07 Jan '09

07 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=460762 Summary: pam_mount stuff overwritten in /etc/pam.d/login and /etc/pam.d/xdm, resulting *NON-ACESSIBLE* encrypted homedirs Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: jsrain(a)novell.com Found By: --- Starting with a running and up-to-date opensuse 11.0 system, I upgraded using the 11.1 x86_64 DVD. After reboot, I (the non-root user) could log in but my home directory contents were gone. I tracked this to it not mounting my encrypted home directory image. Despite yast2's user configuration clearly showing an encrypted home directory, I eventually determined the cause: the login and xdm files in /etc/pam.d were overwritten and the pam_mount aspects were lost. IMO this is a pretty serious issue as *most* people with encrypted home directories would not likely be able to perform that diagnostic. Correcting the pam files (and removing the resmgr components) and things worked fine again. -- 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