May 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 911302] New: fontforge-python-module-name.diff seems plain wrong
by bugzilla_noreply＠novell.com 29 May '17

29 May '17

http://bugzilla.opensuse.org/show_bug.cgi?id=911302 Bug ID: 911302 Summary: fontforge-python-module-name.diff seems plain wrong Classification: openSUSE Product: openSUSE Factory Version: 201412* Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mgd(a)qata.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In the fontforge source package fontforge-20120731-14.2.src.rpm is the patch fontforge-python-module-name.diff that changes the names of the created python modules from fontforge.so and psMat.so to python-fontforge.so and python-psMat.so respectively. This results in python (2.7.9) not being able to find these modules. Creating symbolic links via ln -s python-fontforge.so fontforge.so ln -s python-psMat.so psMat.so seems to solve the problem - at least for me. Why is there the above mentioned patch in the first place anyway ? Either remove that patch or if you really insist on the name change fix python module loading. Kind regards, Michael -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 916816] New: Release Notes do not show in yast
by bugzilla_noreply＠novell.com 24 May '17

24 May '17

http://bugzilla.opensuse.org/show_bug.cgi?id=916816 Bug ID: 916816 Summary: Release Notes do not show in yast Classification: openSUSE Product: openSUSE Factory Version: 201502* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- https://openqa.opensuse.org/tests/47014/modules/user_settings/steps/1 By 'accident' the openQA installer currently presses alt-l (in the hope to get LXDE), but due to the button re-assignment, this is now release notes (not a problem in itself). But, as can be seen on the linked test, the window loaded is actually empty. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 899252] New: sudo: "ignoring time stamp from the future" message after each boot
by bugzilla_noreply＠novell.com 23 May '17

23 May '17

http://bugzilla.suse.com/show_bug.cgi?id=899252 Bug ID: 899252 Summary: sudo: "ignoring time stamp from the future" message after each boot Classification: openSUSE Product: openSUSE Factory Version: 201409* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: bpoirier(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am also experiencing on openSUSE Factory what is described here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762465 ben@f1:~$ rpm -qi sudo Name : sudo Version : 1.8.10p3 Release : 1.2 Architecture: x86_64 Install Date: Thu 18 Sep 2014 04:25:51 AM PDT Group : System/Base [...] -- You are receiving this mail because: You are on the CC list for the bug.

1 29

[Bug 904712] New: Network Manager
by bugzilla_noreply＠novell.com 14 May '17

14 May '17

http://bugzilla.opensuse.org/show_bug.cgi?id=904712 Bug ID: 904712 Summary: Network Manager Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: Other OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jzimm0007(a)aol.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The following bug report has been submitted: Product: SUSE 13.1 32bit I bet it's all of them. Patch Level: Defect: I have a printer (Canon MX749) that requires the wpa/wpa2 key to be lowercase and the SSID for the router has to be lowercase for it to connect to the router so I can print from SUSE wirelessly. (Yes it is possible, the driver is just hard to find) Every time I boot up the system I have to reconnect and fiddle with the network manager to get it to recognize that the hidden SSID is lowercase, because it automatically capitalizes the first letter in the SSID, it won't connect or sometimes it asks for a password even though it's properly entered in the network manager app. I actually installed it on a Gigabyte computer for my dad and it also kept asking for the password to the wifi (totally different router) even though it was typed properly. Other Software and Versions Being Used: I'm guessing it's in all of them since this is the first time (I'm assuming) it's been noticed. Steps to Duplicate: 1.)rename the router to a lowercase SSID with a lowercase 'Mixed WPA/WPA2' AES key The key renewal interval was set to 3600 if that's relevant. It's an 8 letter lowercase word password. 2.)Delete all the wireless connections like where it says when they are last used under manage connections in the network manager app if there are any. Reboot the computer 3.)Click on the network manager app in the tray. Click hidden network>Type in the lowercase SSID name and hit enter. 4.)Type in the correct WPA/WPA2 key (8 letter lowercase password) Notice it capitalizes the SSID so you have to make it lowercase. (Don't lowercase it until you want it to work) Go to the Wireless screen and click on select and random. 5.)Click apply and okay or whatever to keep the settings. 6.)Now if you didn't lowercase the SSID first letter it won't connect or sometimes it'll ask for the password after it's entered properly. I didn't use the KDE Wallet (I don't think I'm pretty sure I just canceled it or hit finish to make it so I didn't have to use it) 7.)So basically to get it to work in Network Manager I had to keep typing in the lowercase SSID and the WPA/WPA2 password every time I booted the computer and it kept adding entries to the network management, but it would eventually connect. I hit cancel in the authentication dialog and kept trying it again and things like that to make it want to connect. Other Scenarios: Yes Environment Description: I'm using a laptop and two desktops all with SUSE 13.1. It's a Netgear PCI Card with a Tenda Router (It has no external antennas and it's white) The netgear has a white box antenna with 2 wires to connect to the HP Computer. I have an MSI E45 gaming computer it's on also. The laptop is a Toshiba Sattelite L25-S119 that randomly freezes when it unlocks like when it adjusts the brightness or something and it uses the Atheros driver which doesn't work right either, but those are other bugs. Problem Environment: Don't know Testing Environment: Didn't try that Fix: Just make the name lowercase when it pops up and asks you, but you keep getting entries in Network Manager after you type in the new lowercase SSID;s Additional: I have all the latest updates installed and it's because I have a wireless printer that requires it to be setup that way. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 916771] New: no traffic through sshuttle possible while SuSEfirewall2 is running
by bugzilla_noreply＠novell.com 02 May '17

02 May '17

http://bugzilla.suse.com/show_bug.cgi?id=916771 Bug ID: 916771 Summary: no traffic through sshuttle possible while SuSEfirewall2 is running Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: wagner-thomas(a)gmx.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On openSUSE 13.1, I investigated sshuttle from the security repository and noticed that is doesn't work while SuSEfirewall2 is running with default settings. "Doesn't work" means: When sshuttle is started all network-traffic is blocked (can't ping, can't do nslookup) instead of tunneled. However, there is no sign in /var/log/messages or /var/log/firewall that SuSEfirewall2 would have blocked something. I used the following command line to start sshuttle as root sshuttle --dns -r user@ssh-tunnel-host 0.0.0.0/0 -v When doing a "rcSuSEfirwall2 stop" prior starting sshuttle, tunneling works fine. Now I wonder: Can the default setting of SuSEfirewall2 can be modified in order to let sshuttle do it's work? -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 929471] New: hostname is not initialized so postfix default hostname/domainname faile
by bugzilla_noreply＠novell.com 02 May '17

02 May '17

http://bugzilla.suse.com/show_bug.cgi?id=929471 Bug ID: 929471 Summary: hostname is not initialized so postfix default hostname/domainname faile Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dgolden(a)golden-consulting.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 633096 --> http://bugzilla.suse.com/attachment.cgi?id=633096&action=edit console output 1) When the system is booted, the hostname is never initialized. 2) Postfix uses the gethostname() system call to establish the "myhostname" and "mydomain" variables; therefore setting the domain name wrong. This causes all the postfix configuration files to fail on systems upgraded to 13.2. -- You are receiving this mail because: You are on the CC list for the bug.

1 39

[Bug 906379] New: autofs - "Local domain name not set" during booting
by bugzilla_noreply＠novell.com 01 May '17

01 May '17

http://bugzilla.opensuse.org/show_bug.cgi?id=906379 Bug ID: 906379 Summary: autofs - "Local domain name not set" during booting Classification: openSUSE Product: openSUSE Factory Version: 201411* Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: renda.krell(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.65 Safari/537.36 Build Identifier: I use autofs for mounting some NFS and CIFS shares. In OpenSUSE 13.1 I haven't seen any error with the same configuration. In OpenSUSE 13.2 incl. Tumbleweed/Factory, 'systemctl status' returns: --- autofs.service - Automounts filesystems on demand Loaded: loaded (/usr/lib/systemd/system/autofs.service; enabled) Active: active (running) since Thu 2014-11-20 08:54:52 CET; 1h 47min ago Docs: man:automount(8) man:autofs(5) Process: 1709 ExecStart=/usr/sbin/automount ${AUTOFS_OPTIONS} -p /var/run/automount.pid (code=exited, status=0/SUCCESS) Main PID: 1712 (automount) CGroup: /system.slice/autofs.service └─1712 /usr/sbin/automount -p /var/run/automount.pid Nov 20 08:54:52 rkrell automount[1712]: lookup_init:139: lookup(yp): map auto.master: Local domain name not set --- In fact, the domain name is not set: rkrell:~ # hostname rkrell rkrell:~ # domainname (none) but the network is set up correctly using NetworkManager and a local LAN connection. Reproducible: Always Steps to Reproduce: 1. Boot the system 2. 3. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 909695] New: segmentation fault after pack & ioctl & unpack
by bugzilla_noreply＠novell.com 28 Apr '17

28 Apr '17

http://bugzilla.suse.com/show_bug.cgi?id=909695 Bug ID: 909695 Summary: segmentation fault after pack & ioctl & unpack Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Ruby Assignee: ruby-devel(a)suse.de Reporter: bkutil(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This snippet (requires sudo due to ioctl call) produces a segmentation fault on the 13.2 ruby [1], affecting current ruby2.0 and ruby2.1 packages. The bug is currently tracked upstream [2], but not yet fixed, however, a patch is known to work as a fix when backported [3]. require 'socket' SIOCETHTOOL = 0x8946 i = ["lo", "\n"].pack("a16p") s = Socket.new(Socket::AF_INET, Socket::SOCK_DGRAM, 0) s.ioctl(SIOCETHTOOL, i) i.unpack("a16p")[1] [1] ruby 2.1.3p242 (2014-09-19 revision 47630) [x86_64-linux-gnu] [2] https://bugs.ruby-lang.org/issues/10568 [3] https://github.com/ruby/ruby/commit/4b146b25333c52ca4503dfc3c4215b583e8e9963 -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 926766] New: rpm: BuildArch resets %patches and %sources
by bugzilla_noreply＠novell.com 26 Apr '17

26 Apr '17

http://bugzilla.suse.com/show_bug.cgi?id=926766 Bug ID: 926766 Summary: rpm: BuildArch resets %patches and %sources Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: mls(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- %patches and %sources are lua scripts that should print the patches and sources. That works fine as long as Source and Patch lines are before BuildArch. Anything that comes after BuildArch is ignored. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 695322] New: home:dannori: Bug
by bugzilla_noreply＠novell.com 23 Apr '17

23 Apr '17

https://bugzilla.novell.com/show_bug.cgi?id=695322 https://bugzilla.novell.com/show_bug.cgi?id=695322#c0 Summary: home:dannori: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: dannoritzer(a)web.de ReportedBy: melchiaros(a)aol.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: Other Blocker: No Hi, I try to install ghdl from your repo. Yast shows me that ghdl-grt needs libada >= 3.1. A look at my system shows that I´ve installed libada46 from devel:/gcc. So all what ghdl need should be there?! Please make a correction when it is necessary. Greetings -- 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