January 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 827010] New: mailx does not set correct mime types
by bugzilla_noreply＠novell.com 21 Jan '14

21 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=827010 https://bugzilla.novell.com/show_bug.cgi?id=827010#c0 Summary: mailx does not set correct mime types Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bastian(a)bastian-friedrich.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 When using "mailx" to send various file types, e.g. gif or jpeg, the files are sent as "application/octet-stream" instead of "image/<whatever>". The problem does NOT occur for mime types such as text/html. Reproducible: Always Steps to Reproduce: 1. mailx -a my-image.gif -s 'GIF test' your(a)address.com < /dev/null 2. View mail source after receiving Actual Results: Content-Type: application/octet-stream Content-Transfer-Encoding: base64 Expected Results: Content-Type: image/gif Content-Transfer-Encoding: base64 The problem did NOT occur in OpenSUSE 12.1 and was introduced with patch "mailx-12.5-mime.dif" in OpenSUSE 12.2. The file mime type is determined correctly, but the (new) code resets it to octet-stream again: ------------- + if (isclean & MIME_LATIN) { + tcs = value("charset"); + if (tcs == NULL && wantcharset && wantcharset != (char *)-1) + tcs = wantcharset; + } + if (tcs == NULL) { + contenttype = "application/octet-stream"; + charset = NULL; + convert = CONV_TOB64; ------------- The problem also goes away when calling charset=utf-8 mailx -a my-image.gif -s 'GIF test' your(a)address.com < /dev/null -- 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 17

[Bug 765769] New: 'Software Management' window disappears when selecting 'vlc' to be installed.
by bugzilla_noreply＠novell.com 21 Jan '14

21 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=765769 https://bugzilla.novell.com/show_bug.cgi?id=765769#c0 Summary: 'Software Management' window disappears when selecting 'vlc' to be installed. Classification: openSUSE Product: openSUSE 12.2 Version: Beta 1 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ximpox(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0 and leaves an error dialog: 'YaST got signal 11 at YCP file PackagesUI.ycp:280 /sbin/yast2: line 427: 4352 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS' Reproducible: Always Steps to Reproduce: 1.open yast control center 2.select Software Management 3.search 'vlc' 4.select from list 'vlc' Actual Results: Shows for a short moment all the files which should be installed. Then 'Software Management' window dies leaving mentioned error message. Expected Results: Should have installed 'vlc' and associated files. I have not encountred this problem with other softwares I have installed. -- 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 27

[Bug 818439] New: libvdpau_r300-9.0.2-34.6.1.x86_64 wrongly linked
by bugzilla_noreply＠novell.com 21 Jan '14

21 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=818439 https://bugzilla.novell.com/show_bug.cgi?id=818439#c0 Summary: libvdpau_r300-9.0.2-34.6.1.x86_64 wrongly linked Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: bradatajs(a)yahoo.com QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 No VDPAU applications work. vdpauinfo says cannot find libvdpau_r300.so I add it to library path /etc/ld.so.conf.d/vdpau.conf: /usr/lib64/vdpau /usr/lib/vdpau # ldconfig -v -> yes it is in right place now $ vdpauinfo ... Failed to open VDPAU backend /usr/lib64/vdpau/libvdpau_r300.so: undefined symbol: pthread_rwlock_unlock $ LD_PRELOAD=/lib64/libpthread.so.0 vdpauinfo display: :0 screen: 0 API version: 1 Information string: G3DVL VDPAU Driver Shared Library version 1.0 Video surface: name width height types ------------------------------------------- 420 2048 2048 NV12 YV12 422 2048 2048 NV12 YV12 444 2048 2048 NV12 YV12 Y .... Reproducible: Always Steps to Reproduce: As described Actual Results: Needed complex tweaks to get VDPAU working Expected Results: That VDPAU works out of the box (worked with 12.1) Probably r600 and 32bit versions are also broken as they dont link to pthreads -- 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 727911] New: no printer config file (ppd) found by yast
by bugzilla_noreply＠novell.com 21 Jan '14

21 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=727911 https://bugzilla.novell.com/show_bug.cgi?id=727911#c0 Summary: no printer config file (ppd) found by yast Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jdd(a)dodin.org 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 have only network printer - when installing it yast do detect it due to the firewall. but then yast do not find either any ppd file. When instructed to look at the IP, yast find the printer (hp), but do not either find any driver. Hplip have the same problem However, cups at port 631 *do* find the drivers and install the printer. After that yast find all the drivers (I could change the printer driver with yast) 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 28

[Bug 856796] New: printer setup via yast2: no drivers shown
by bugzilla_noreply＠novell.com 21 Jan '14

21 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=856796 https://bugzilla.novell.com/show_bug.cgi?id=856796#c0 Summary: printer setup via yast2: no drivers shown Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: axel.braun(a)gmx.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 For whatever reason...printer configuration in Yast is a nightmare since ages. Reproducible: Always Steps to Reproduce: 1. Select printing via network and enter ipp: data 2. Check connection to print server: Connection OK 3. Enter HP as printer manufacturer 4. Try to find a printer driver: You can enter any search string or leave it blank, no printer driver is found 5. you cant finalize the printer configuration Actual Results: No printer drivers displayed, although all required packages are installed Expected Results: I just want a postscript printer driver...... -- 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 859271] New: Printing/cups: Bug - pkg updates to 1.5.4-136.1 failing
by bugzilla_noreply＠novell.com 21 Jan '14

21 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=859271 https://bugzilla.novell.com/show_bug.cgi?id=859271#c0 Summary: Printing/cups: Bug - pkg updates to 1.5.4-136.1 failing Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: crrodriguez(a)opensuse.org ReportedBy: ar(a)sent.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com CC: jsmeix(a)suse.com, jw(a)suse.com, werner(a)suse.com Found By: --- Blocker: --- current zypper update attempts are failing, .. Retrieving package cups-1.5.4-136.1.x86_64 (113/240), 7.2 MiB ( 11.0 MiB unpacked) Retrieving: cups-1.5.4-136.1.x86_64.rpm ......................................................................[done] (113/240) Installing: cups-1.5.4-136.1 ......................................................................[error] Installation of cups-1.5.4-136.1 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/share/cups/fonts: cpio: rename failed - Is a directory error: cups-1.5.4-136.1.x86_64: install failed error: cups-1.5.4-134.1.x86_64: erase skipped .. -- 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 826608] New: openSUSE:12.2/smlnj: Bug
by bugzilla_noreply＠novell.com 21 Jan '14

21 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=826608 https://bugzilla.novell.com/show_bug.cgi?id=826608#c0 Summary: openSUSE:12.2/smlnj: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: dmacvicar(a)suse.com ReportedBy: lambda(a)mail.upb.de QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: Community User Blocker: --- # sml Standard ML of New Jersey v110.74 [built: Sun Jul 15 18:57:07 2012] - val txt = "Standard ML is a formally defined programming language."; val c = String.sub(txt,0); val txt = "Standard ML is a formally defined programming language." : string - [autoloading] unexpected exception (bug?) in SML/NJ: Io [Io: openIn failed on "/home/abuild/rpmbuild/BUILD/smlnj-110.74/sml.boot.x86-unix/smlnj/basis/.cm/x86-unix/basis.cm", No such file or directory] raised at: Basis/Implementation/IO/bin-io-fn.sml:617.25-617.71 ../cm/util/safeio.sml:30.11 ../compiler/TopLevel/interact/evalloop.sml:44.55 ##################################################################### There seems to be no SMLNJ_HOME set so sml does not find the library. when setting SMLNJ_HOME=/usr/lib/smlnj/ before starting sml it works. I modified /usr/bin/sml (a shell script wrapper) in a crude way to set it statically, but I think this needs to be a bit cleaner. Please fix :) Thanks for your efforts. -- 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 792490] New: Wrong bluetooth (AR3011 - ath3k, btusb) adapter name after boot/suspend.
by bugzilla_noreply＠novell.com 21 Jan '14

21 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=792490 https://bugzilla.novell.com/show_bug.cgi?id=792490#c0 Summary: Wrong bluetooth (AR3011 - ath3k, btusb) adapter name after boot/suspend. Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: i686 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: 0x4721(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=515457) --> (http://bugzilla.novell.com/attachment.cgi?id=515457) Lsusb -v output with Atheros card visible User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Firefox/17.0 Every time i return from suspend or i boot my laptop, bluetooth adapter name is changed to "Azure:Dec 3 2010,00:24:03". I've changed names in /etc/bluetooth/main.conf, /var/lib/bluetooth/MACADDR/config, added /etc/machine-info (file was not created during update from openSUSE 12.1 to 12.2) for no avail. Only way to change name so that it survives warm reboot or suspend is to suspend with hci0 device up (it comes back up), or kill bluetoothd and then reenable it from console. Reproducible: Always Steps to Reproduce: 1.Boot machine with ath3k AR3011 device 2.hciconfig hci0 up 3.hciconfig hci0 name Actual Results: hciconfig hci0 name returns "Azure:Dec 3 2010,00:24:03" Expected Results: Bluetooth adapter name should retain name set by user. I'm using Toshiba NB520 Netbook with Atheros AR3011 Bluetooth module. Kernel 3.6.8.1-desktop kernel (Situation is same with stock openSUSE 12.2 kernel). Before updating to 12.2 setting name to bluetooth adapter worked well. Bluetoothd version 4.99 I have found that string "Azure:Dec 3 2010,00:24:03" can be found in firmware file /usr/lib/firmware/ath3k-1.fw -- 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 828442] New: Can't use autofs if NFS server only offers NFSv4
by bugzilla_noreply＠novell.com 20 Jan '14

20 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=828442 https://bugzilla.novell.com/show_bug.cgi?id=828442#c0 Summary: Can't use autofs if NFS server only offers NFSv4 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: roland.mainz.bugzilla-suse(a)nrubsig.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111101 SUSE/3.6.24-0.2.1 Firefox/3.6.24 We've tried to access OpenSuSE 12.3's nfs server running in NFSv4-only mode (e.g. NFSv2/NFSv3 protocols are disabled since we have to pass some firewalls (later... not in this test setup which is completely without any firewalls... don't worry :-))) via autofs (several variations, including OpenSuSE 12.2, Solaris 11, Solaris 11.1, Illumos etc.) and all clients can't automount it... ;-( ** Server config (IPv4 address is 192.168.2.105): $ exportfs /nfs4test <world> $ ps -ef | fgrep nfs root 2556 1 0 10:29 ? 00:00:00 /usr/sbin/rpc.mountd --no-nfs-version 2 --no-nfs-version 3 root 2559 2 0 10:29 ? 00:00:00 [nfsd4] root 2560 2 0 10:29 ? 00:00:00 [nfsd4_callbacks] root 2561 2 0 10:29 ? 00:00:00 [nfsd] root 2562 2 0 10:29 ? 00:00:00 [nfsd] root 2563 2 0 10:29 ? 00:00:00 [nfsd] root 2564 2 0 10:29 ? 00:00:00 [nfsd] ** Client config (Solaris 11 in this case, IPv4 address is 192.168.2.81, hostname="indianab134x86"): - Server machine is pingable and otherwise reachable without problems (e.g. ssh, X11 etc. all work between server and clients in both directions) - "snoop" (Solaris network traffic analyser) shows the following traffic during an attempt to do $ cd /net/192.168.2.105/ #: -- snip -- $ snoop 192.168.2.105 Using device e1000g0 (promiscuous mode) 192.168.2.105 -> 224.0.0.251 IGMP v2 membership report indianab134x86 -> 192.168.2.105 TCP D=2049 S=47294 Syn Seq=246940684 Len=0 Win=64240 Options=<mss 1460,nop,nop,tstamp 98806 0,nop,wscale 1,nop,nop,sackOK> 192.168.2.105 -> indianab134x86 TCP D=47294 S=2049 Syn Ack=246940685 Seq=2501028985 Len=0 Win=14480 Options=<mss 1460,sackOK,tstamp 1654279 98806,nop,wscale 7> indianab134x86 -> 192.168.2.105 TCP D=2049 S=47294 Ack=2501028986 Seq=246940685 Len=0 Win=64436 Options=<nop,nop,tstamp 98806 1654279> indianab134x86 -> 192.168.2.105 NFS C NULL4 192.168.2.105 -> indianab134x86 TCP D=47294 S=2049 Ack=246940729 Seq=2501028986 Len=0 Win=114 Options=<nop,nop,tstamp 1654280 98806> 192.168.2.105 -> indianab134x86 NFS R NULL4 indianab134x86 -> 192.168.2.105 TCP D=2049 S=47294 Ack=2501029014 Seq=246940729 Len=0 Win=64436 Options=<nop,nop,tstamp 98806 1654280> indianab134x86 -> 192.168.2.105 TCP D=2049 S=47294 Fin Ack=2501029014 Seq=246940729 Len=0 Win=64436 Options=<nop,nop,tstamp 98806 1654280> 192.168.2.105 -> indianab134x86 TCP D=47294 S=2049 Fin Ack=246940730 Seq=2501029014 Len=0 Win=114 Options=<nop,nop,tstamp 1654281 98806> indianab134x86 -> 192.168.2.105 TCP D=2049 S=47294 Ack=2501029015 Seq=246940730 Len=0 Win=64436 Options=<nop,nop,tstamp 98806 1654281> indianab134x86 -> 192.168.2.105 PORTMAP C GETPORT prog=100005 (MOUNT) vers=1 proto=TCP 192.168.2.105 -> indianab134x86 PORTMAP R GETPORT port=0 indianab134x86 -> 192.168.2.105 PORTMAP C GETPORT prog=100005 (MOUNT) vers=1 proto=UDP 192.168.2.105 -> indianab134x86 PORTMAP R GETPORT port=0 -- snip -- Uhm... I'm stuck at this point. The same thing works OK between a Solaris 11 server (running in NFSv4-only mode) and any kind of NFSv4 client. Reproducible: Always Steps to Reproduce: 1. See above Actual Results: Can't use automounter to access test share. Expected Results: Can use automounter to access test share, e.g. $ cd /net/192.168.2.105/ # ... Goal is to get the automounter functional for all operating systems required by the project (e.g. SuSE Linux and Solaris 10/11+Illumos). Severity: Set to "major" since we can't move forward (unless we pick an all-Solaris config if we can't get the Linux trouble fixed). -- 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 779430] New: nfs mounts from /etc/fstab are not mounted in boot time if network manager is disabled
by bugzilla_noreply＠novell.com 20 Jan '14

20 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=779430 https://bugzilla.novell.com/show_bug.cgi?id=779430#c0 Summary: nfs mounts from /etc/fstab are not mounted in boot time if network manager is disabled Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ondrej.hrstka(a)iba-group.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=504958) --> (http://bugzilla.novell.com/attachment.cgi?id=504958) Workaround - files changed User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.89 Safari/537.1 My situation is: - systemd initialization - network manager is disabled (it cannot assign hostname from the DHCP response) - DHCP is used to obtain IP address + hostname - several NFS mount points are defined in /etc/fstab In this case, NFS mountpoints are not mounted during boot. There are basically 2 problems. In 32-bits system, some dependencies are missing in the systemd configuration. If this is fixed, NFS is mounted correctly at boot time. In 64-bits system, on top of this, there is probably a bug causing systemd not to wait until the network is completelly up (i.e. we have IP address). Reproducible: Always Steps to Reproduce: 1. Disable network manager 2. Configure the system to use DHCP to obtain IP address + hostname 3. Define several NFS mount points in /etc/fstab 4. Boot the system. Actual Results: NFS mount points are not mounted. Expected Results: NFS mount points should be mounted. See attachment - there are files which I've changed to workaround the problem on my system. 1. Place network-wait-online.service remote-fs-pre.target rpcbind.service rpcbind.socket files into /lib/systemd/system 2. Place wait.sh into /usr/local/bin 3. Make link ln -s /lib/systemd/system/network-wait-online.service /etc/systemd/system/network.target.wants/network-wait-online.service (Steps 2 and 3 are not necessary on 64-bits 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 9