June 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 853379] New: qemu cannot access internal smb share
by bugzilla_noreply＠novell.com 15 Jun '14

15 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=853379 https://bugzilla.novell.com/show_bug.cgi?id=853379#c0 Summary: qemu cannot access internal smb share Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: KVM AssignedTo: kvm-bugs(a)forge.provo.novell.com ReportedBy: rickscafe.casablanca(a)gmx.net QAContact: jdouglas(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 Since upgrading to 13.1 from 12.3 qemu virtual windows can no longer access samba shares as defined by -smb /foo/bar command line options to qemu. As samba was upgraded to version 4, it is likely that this is a problem of qemu interacting with the installed samba server. Specifically, a Debian bug suggests that the configuration file that qemu passes to samba does not work with newer samba, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727756 Reproducible: Always Steps to Reproduce: 1. pass -smb /some/dir to qemu 2. try to access the samba share from within a virtual windows via \\10.0.2.4\qemu 3. Actual Results: Windows error: The server refused the connection (or something to that end) Expected Results: working connection to samba share -- 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 882746] New: pnp4nagios can't write to it's log file due to wrong permission
by bugzilla_noreply＠novell.com 15 Jun '14

15 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=882746 https://bugzilla.novell.com/show_bug.cgi?id=882746#c0 Summary: pnp4nagios can't write to it's log file due to wrong permission Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: wagner-thomas(a)gmx.at QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux x86_64) Presto/2.12.388 Version/12.16 Installing pnp4nagios from the "monitoring" repo creates /var/log/pnp4nagios as folder for logfiles. However, this folder has only write access for user "root" not for user "nagios" so no log file ever will be written there. Reproducible: Always -- 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 860478] New: BT helper crashes when I try to connect a BT keyboard
by bugzilla_noreply＠novell.com 14 Jun '14

14 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=860478 https://bugzilla.novell.com/show_bug.cgi?id=860478#c0 Summary: BT helper crashes when I try to connect a BT keyboard Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: roeland(a)linux-it.nl QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 https://bugs.kde.org/show_bug.cgi?id=330394 the bt helper triggers a crash. Reproducible: Always Steps to Reproduce: 1. discover bt keyboard and enter the passkey 2. now when tryng to connect it triggers a crash 3. Actual Results: none specific Expected Results: shudl conenct to the keyboard https://bugs.kde.org/show_bug.cgi?id=330394 for all the details as well. -- Backtrace: Application: Bluetooth Input Helper (bluedevil-input), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #5 BlueDevil::Device::UUIDs (this=this@entry=0x0) at /usr/src/debug/libbluedevil/bluedevil/bluedevildevice.cpp:218 #6 0x0000000000404621 in InputHelper::InputHelper (this=0x2791c30, address=...) at /usr/src/debug/bluedevil/src/actionplugins/input/helper/inputhelper.cpp:42 #7 0x0000000000403ffe in main (argc=2, argv=0x7fffc357ebc8) at /usr/src/debug/bluedevil/src/actionplugins/input/helper/main.cpp:49 -- 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 853906] New: bluedevil-audio Segmentation fault error
by bugzilla_noreply＠novell.com 14 Jun '14

14 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=853906 https://bugzilla.novell.com/show_bug.cgi?id=853906#c0 Summary: bluedevil-audio Segmentation fault error Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: mcaj(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Field Engineer Blocker: --- HI, Today I tried to connect my headset via blue-tooth in the OpenSUSe 13.1. and it run into Segmentation fault error. there is step by step howto: 1. Turn you BT device on in the broadcast status, so OS is able to scan and see the device. 2. click on BT system icon and try to Add device. - there allow to BT to usi it for audio. - The pulse audio`ll see the device as unplug for now. 4. disable broadcast status on your device. 5. try to connect your device with the OS via command : <pre> bluedevil-audio 00:0d:44:XX:XX:XX </pre> or you can use KDE app as well to connect the device with the same results The application bluedevil-audio crash ASAP like this: KCrash: Application 'bluedevil-audio' crashing... KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit sock_file=/home/mcaj/.kde4/socket-nobby.suse.cz/kdeinit4__0 [2]- Stopped bluedevil-audio --sync 00:0d:44:XX:XX:XX [3]+ Stopped bluedevil-audio 00:0d:44:XX:XX:XX 6. in the KDE4 I can also see crash output from Drkonqi: Application: Bluetooth Audio Helper (bluedevil-audio), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #5 BlueDevil::Device::isPaired (this=this@entry=0x0) at /usr/src/debug/libbluedevil/bluedevil/bluedevildevice.cpp:203 #6 0x0000000000402f1e in AudioHelper::AudioHelper (this=0x1642480, address=...) at /usr/src/debug/bluedevil/src/actionplugins/audio/helper/audiohelper.cpp:41 #7 0x0000000000402bde in main (argc=2, argv=0x7fff0c7ca6b8) at /usr/src/debug/bluedevil/src/actionplugins/audio/helper/main.cpp:49 reproducible: always. I think it should work out of box and don't need any special hacking skills. And Segfault is always bad. Martin -- 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 882745] New: home:dkxls:cfd/openfoam22x: Bug
by bugzilla_noreply＠novell.com 14 Jun '14

14 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=882745 https://bugzilla.novell.com/show_bug.cgi?id=882745#c0 Summary: home:dkxls:cfd/openfoam22x: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: dkxls23(a)gmail.com ReportedBy: kshkss+suse2(a)gmail.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- In order to set up a environment, I have typed this command: $ source /opt/openfoam/OpenFOAM-2.2.x/etc/bashrc and I have got these messages: bash: /opt/OpenFOAM-2.2.x/bin/foamEtcFile: No such file or directory bash: /opt/OpenFOAM-2.2.x/bin/foamCleanPath: No such file or directory bash: /opt/OpenFOAM-2.2.x/bin/foamCleanPath: No such file or directory bash: /opt/OpenFOAM-2.2.x/bin/foamCleanPath: No such file or directory bash: /opt/OpenFOAM-2.2.x/etc/config/settings.sh: No such file or directory bash: /opt/OpenFOAM-2.2.x/etc/config/aliases.sh: No such file or directory bash: /opt/OpenFOAM-2.2.x/bin/foamEtcFile: No such file or directory bash: /opt/OpenFOAM-2.2.x/bin/foamEtcFile: No such file or directory bash: /opt/OpenFOAM-2.2.x/bin/foamEtcFile: No such file or directory bash: /opt/OpenFOAM-2.2.x/bin/foamCleanPath: No such file or directory bash: /opt/OpenFOAM-2.2.x/bin/foamCleanPath: No such file or directory bash: /opt/OpenFOAM-2.2.x/bin/foamCleanPath: No such file or directory I think OpenFOAM-2.2.x should be installed under /opt directly. -- 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 882750] New: tumblerd uses 100% cpu
by bugzilla_noreply＠novell.com 14 Jun '14

14 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=882750 https://bugzilla.novell.com/show_bug.cgi?id=882750#c0 Summary: tumblerd uses 100% cpu Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Xfce AssignedTo: bnc-team-xfce(a)forge.provo.novell.com ReportedBy: vdziewiecki(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Community User Blocker: --- On my xfce desktop, I just noticed that tumblerd uses 100% cpu, and I don't even have a file manager open, I closed all desktop applications but the problem remains. I will try to find a way to reproduce it and write it here. -- 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 882656] New: Totem Will Not Play Videos From YouTube
by bugzilla_noreply＠novell.com 13 Jun '14

13 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=882656 https://bugzilla.novell.com/show_bug.cgi?id=882656#c0 Summary: Totem Will Not Play Videos From YouTube Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: Antoine.Saroufim(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 Totems will complain about a missing text/html decoder whenever the user browses and chooses to view a YouTube video from within the player. Reproducible: Always Steps to Reproduce: 1.Click on Browse 2.Select YouTube 3.Type in the name of a video and try to play it Actual Results: YouTube complains about missing decoder Expected Results: YouTube video plays when I was testing the 3.11 branch on Factory, this wasn't an issue. -- 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 0

[Bug 780179] New: Strange IPv6 download request in non-IPv6 environment during Yast2 download/install (during short network failure on providers side)
by bugzilla_noreply＠novell.com 13 Jun '14

13 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=780179 https://bugzilla.novell.com/show_bug.cgi?id=780179#c0 Summary: Strange IPv6 download request in non-IPv6 environment during Yast2 download/install (during short network failure on providers side) Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dirk(a)goe.net QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20100101 Firefox/14.0.1 Installed openSuSE 12.2 from USB stick (KDE CD). Then used Yast2 (graphical) to add lots of packages to install them. Worked fine for quite a while (ca. 60 %). Then the download stopped. Retrying it did not produce any progress but the report that the machine "2001:...." (forgot the rest, obviously the IPv6 address of download.opensuse.org) The download machine was temporarily not ping able (for whatever reason, another machine in the same subnet download.suse.com still was, so I suspect some strange problem on my cable providers side). Then stopped the procedure (skipped the installation) and restarted and everything went on properly. Added quite some packages this way again and never saw the bug again (did not see any network problems further on). My environment is IPv4 only, I did not have any IPv6 address configured (sitting behind a router machine running OpenSuSE 12.1 with IPv4 DHCP). No IPv6 addresses beside the link local ones. Ping6 immediately reported "no route" when trying to ping IPv6 addresses. Reproducible: Couldn't Reproduce Steps to Reproduce: 1. 2. 3. Actual Results: Further installation was not possible. Expected Results: Installation should have completed. With "Retrying" the download should have completed after network recovery. -- 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 863047] New: Zypper reports IPv6 error when an IPv4 error occurs
by bugzilla_noreply＠novell.com 13 Jun '14

13 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=863047 https://bugzilla.novell.com/show_bug.cgi?id=863047#c0 Summary: Zypper reports IPv6 error when an IPv4 error occurs Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: MathematicalOrchid(a)hotmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0 I just wasted FOUR HOURS trying to figure out why Zypper is using IPv6 on a network that doesn't have IPv6 configured. It turns out that Zypper ISN'T actually using IPv6 at all; it's just that the error message SAYS it is. If I had known that four hours ago, I could have saved myself a hell of a lot of trouble! Reproducible: Always Steps to Reproduce: 1. Disable IPv6 in YaST. 2. Prevent IPv4 from connecting somehow. (E.g., firewall everything.) 3. Do zypper refresh. Actual Results: Zypper sits there for about 5 minutes, and then says - and I quote: "Failed to connect to 2001:67c:2178:8::13: Network is unreachable" Which is true - but why is it trying to use IPv6 when that's disabled?? Expected Results: The ACTUAL error would be far more accurately described as something like "cannot connect to 195.135.221.134: the operation timed out". Running strace reveals the following: .. 1179 socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 5 1179 connect(5, {sa_family=AF_INET6, sin6_port=htons(80), inet_pton(AF_INET6, "2001:67c:2178:8::13", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 ENETUNREACH (Network is unreachable) 1179 close(5) = 0 1179 madvise(0x7ff48750c000, 8368128, MADV_DONTNEED) = 0 1179 _exit(0) = ? 1179 +++ exited with 0 +++ 1177 <... poll resumed> ) = 0 (Timeout) 1177 socket(PF_INET, SOCK_STREAM|SOCK_CLOEXEC, IPPROTO_TCP) = 5 1177 fcntl(5, F_GETFL) = 0x2 (flags O_RDWR) 1177 fcntl(5, F_SETFL, O_RDWR|O_NONBLOCK) = 0 1177 connect(5, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("195.135.221.134")}, 16) = -1 EINPROGRESS (Operation now in progress) 1177 poll([{fd=5, events=POLLOUT|POLLWRNORM}], 1, 0) = 0 (Timeout) 1177 poll([{fd=5, events=POLLOUT}], 1, 1000) = 0 (Timeout) 1177 poll([{fd=5, events=POLLOUT|POLLWRNORM}], 1, 0) = 0 (Timeout) 1177 poll([{fd=5, events=POLLOUT}], 1, 1000) = 0 (Timeout) 1177 poll([{fd=5, events=POLLOUT|POLLWRNORM}], 1, 0) = 0 (Timeout) 1177 poll([{fd=5, events=POLLOUT}], 1, 1000) = 0 (Timeout) .. As you can see, Zypper is CLEARLY timing out while trying to connect to the IPv4 address. The problem has nothing to do with IPv6 at all - yet the error message says it is. -- 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 853016] New: Online update hangs with IPv6 when WAN is IPv4 only
by bugzilla_noreply＠novell.com 13 Jun '14

13 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=853016 https://bugzilla.novell.com/show_bug.cgi?id=853016#c0 Summary: Online update hangs with IPv6 when WAN is IPv4 only Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: volker3204(a)paradise.net.nz QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) konqueror/4.10.5 Safari/534.34 Running yast online update results in a random server to be selected. Some of these servers are IPv6 capable. My ISP and WAN are not. The default openSUSE configuration is to always enable IPv6, and there are use cases for doing this even with an IPv4-only WAN (the LAN for example has no such limitation). And it is the default setting. So the situation is: * Yast times out every 30s with a network error, until clicking "skip" on this repo, for every single repo worst case. * There is no "cancel" button. * Clicking the window's "close" button brings up a "terminate this application"; clicking yes does nothing. So the user has an obnoxious application that does only offline "updates", keeps on wasting time, AND does not take "bugger off" for an answer! Updating the system is impossible with this. Reproducible: Always Steps to Reproduce: 1. Use WAN that is IPv4 only. Use LAN that is IPv6 capable (e.g. from default openSUSE installs). 2. Run online update. 3. Repeat until a IPv6 updates server is selected. Actual Results: Yast times out with a network error every 30s, until clicking "skip". Yast times out with a network error with the next repository, every 30s, until clicking skip. Yast keeps on doing nothing useful until the last repo has been dealt with. Expected Results: Update server being addresses in IPv4 when IPv6 doesn't work. -- 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