December 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 958314] New: osc install fails with traceback if osc-plugin-install is not installed
by bugzilla_noreply＠novell.com 30 Jan '18

30 Jan '18

http://bugzilla.suse.com/show_bug.cgi?id=958314 Bug ID: 958314 Summary: osc install fails with traceback if osc-plugin-install is not installed Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mgriessmeier(a)suse.com QA Contact: qa-bugs(a)suse.de CC: okurz(a)suse.com Found By: --- Blocker: --- Traceback (most recent call last): File "/usr/bin/X11/osc", line 41, in <module> r = babysitter.run(osccli) File "/usr/lib/python2.7/site-packages/osc/babysitter.py", line 61, in run return prg.main(argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 343, in main return self.cmd(args) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 366, in cmd retval = self.onecmd(argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 500, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 1230, in _dispatch_cmd return handler(argv[0], opts, *args) File "/usr/lib/python2.7/site-packages/osc/commandline.py", line 3958, in do_install (re.sub(':', ':/', args[0]), 'openSUSE_11.4', args[1]) IndexError: list index out of range -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 901361] New: IMAP+ plugin forces SSL 3.0
by bugzilla_noreply＠novell.com 30 Jan '18

30 Jan '18

http://bugzilla.opensuse.org/show_bug.cgi?id=901361 Bug ID: 901361 Summary: IMAP+ plugin forces SSL 3.0 Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Evolution Assignee: bnc-team-evolution(a)forge.provo.novell.com Reporter: sionescu(a)cddr.org QA Contact: lakhil(a)novell.com Found By: --- Blocker: --- Today(2014-10-15), FastMail disabled SSL 3.0 on all their servers because of a recently discovered vulnerability, and Evolution cannot connect to the imap server because it apparently forces SSL 3.0 on the outbound connection. I'm using Evolution 3.10.4-24.1 on x86_64 and the account is configured as follows: plugin IMAP+ on host "mail.messagingengine.com", port 993, encryption method "SSL on a dedicated port" The exact error message I get is "Could not connect to 'mail.messagingengine.com:993': Cannot communicate securely with peer: no common encryption algorithm(s)." -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 907982] New: Segfault with g_type_check_instance_cast
by bugzilla_noreply＠novell.com 30 Jan '18

30 Jan '18

http://bugzilla.opensuse.org/show_bug.cgi?id=907982 Bug ID: 907982 Summary: Segfault with g_type_check_instance_cast Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: toganm(a)dinamizm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 615610 --> http://bugzilla.opensuse.org/attachment.cgi?id=615610&action=edit darktable gdb backtrace for the segfault When using Darktable from home:toganm:photography repo which is based on darktable git master branch, I had segfaults. Darktable development thinks this is an issue with either gobject or glib. Attached is the latest gdb trace. Let me know if more info is needed Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 931595] New: YaST2 module network does not configure using wicked a working IPv6 network
by bugzilla_noreply＠novell.com 29 Jan '18

29 Jan '18

http://bugzilla.opensuse.org/show_bug.cgi?id=931595 Bug ID: 931595 Summary: YaST2 module network does not configure using wicked a working IPv6 network Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: freek(a)opensuse.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I used the YaST GUI in KDE on Tumbleweed 20150516 to configure the Ethernet interface having two IPv4 addresses and two IPv6 addresses. Using NetworkManager with the same configuration works OK. Also DNS and routing are configured the same as with NetworkManager. The first time I enabled this configuration I noticed that "ip -6 r" did not show a default route. A ping6 could not reach a IPv6 host. After that I went back to the NetworkManager setup. Now I changed it back to wicked and I see the following: eiktum:~ # ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether e0:cb:4e:cd:d7:b6 brd ff:ff:ff:ff:ff:ff inet 192.168.178.6/24 brd 192.168.178.255 scope global enp1s0 valid_lft forever preferred_lft forever inet 192.168.178.7/24 brd 192.168.178.255 scope global secondary enp1s0 valid_lft forever preferred_lft forever inet6 2001:980:xxxx::1:37/64 scope global valid_lft forever preferred_lft forever inet6 2001:980:xxxx::1:36/64 scope global valid_lft forever preferred_lft forever inet6 2001:980:xxxx:1::1:37/64 scope global valid_lft forever preferred_lft forever inet6 2001:980:xxxx:1::1:36/64 scope global valid_lft forever preferred_lft forever inet6 fe80::e2cb:4eff:fecd:d7b6/64 scope link valid_lft forever preferred_lft forever eiktum:~ # ip -4 r default via 192.168.178.1 dev enp1s0 default via 192.168.178.1 dev enp1s0 proto static metric 100 192.168.178.0/24 dev enp1s0 proto kernel scope link src 192.168.178.6 192.168.178.0/24 dev enp1s0 proto kernel scope link src 192.168.178.6 metric 100 eiktum:~ # ip -6 r 2001:980:xxxx::/64 dev enp1s0 proto kernel metric 256 2001:980:xxxx:1::/64 dev enp1s0 proto kernel metric 256 fd00::9ec7:a6ff:fe0a:1f48 dev enp1s0 proto static metric 100 fe80::/64 dev enp1s0 proto kernel metric 256 default via fd00::9ec7:a6ff:fe0a:1f48 dev enp1s0 proto static metric 100 eiktum:~ # more /etc/sysconfig/network/ifcfg-enp1s0 BOOTPROTO='static' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='192.168.178.6/24' MTU='' NAME='' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' DHCLIENT_SET_DEFAULT_ROUTE='yes' IPADDR_0='2001:980:xxxx::1:36/64' LABEL_0='eiktumb6' IPADDR_1='192.168.178.7/24' LABEL_1='eiktuml' IPADDR_2='2001:980:xxxx::1:37/64' LABEL_2='eiktuml6' eiktum:~ # more /etc/sysconfig/network/ifroute-enp1s0 default 192.168.178.1 - enp1s0 default fd00::9ec7:fe0a:1f48 - enp1s0 eiktum:~ # grep NETCONFIG_DNS_STATIC_SERVERS /etc/sysconfig/network/config NETCONFIG_DNS_STATIC_SERVERS="192.168.178.1 fd00::9ec7:fe0a:1f48" eiktum:~ # It looks like the problem is not so much YaST, but wicked, because these configuration files look OK. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 943845] New: X pegs CPU at 100%
by bugzilla_noreply＠novell.com 24 Jan '18

24 Jan '18

http://bugzilla.opensuse.org/show_bug.cgi?id=943845 Bug ID: 943845 Summary: X pegs CPU at 100% Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: rjschwei(a)suse.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Created attachment 645652 --> http://bugzilla.opensuse.org/attachment.cgi?id=645652&action=edit Xorg log file from run where condition was observed. > rpm -qa | grep -i xorg xorg-x11-Xvnc-1.5.0-2.1.x86_64 xorg-x11-fonts-7.6-31.4.noarch xorg-x11-essentials-7.6_1-16.1.noarch xorg-x11-server-7.6_1.16.2-1.3.x86_64 xorg-scripts-1.0.1-10.1.noarch xorg-x11-util-devel-7.6_1-10.1.noarch xorg-cf-files-1.0.5-5.1.noarch xorg-x11-server-extra-7.6_1.17.2-3.1.x86_64 xorg-x11-driver-video-7.6_1-15.1.x86_64 xorg-x11-driver-input-7.6_1-13.1.noarch xorg-sgml-doctools-1.11-9.1.noarch xorg-x11-libX11-ccache-7.6-20.2.noarch xorg-x11-fonts-core-7.6-31.4.noarch xorg-x11-devel-7.6-47.1.noarch On startup X loads the CPU 100% and makes the machine unresponsive. The condition has been observed to last 15 minutes after which I turned the machine off, forced off via power switch, shutdown did not work. The condition does luckily not exist 100% of the time, it appears that it occurs on start up, then after reboot by triggering a power cycle the 100% CPU condition only occurs for a short period of time, approximately 1 to 2 minutes. # hwinfo --gfxcard 09: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.366] Unique ID: _Znp.W2XlUwjUxL4 SysFS ID: /devices/pci0000:00/0000:00:02.0 SysFS BusID: 0000:00:02.0 Hardware Class: graphics card Model: "Intel 3rd Gen Core processor Graphics Controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x0166 "3rd Gen Core processor Graphics Controller" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x21f9 Revision: 0x09 Driver: "i915" Driver Modules: "drm" Memory Range: 0xf0000000-0xf03fffff (rw,non-prefetchable) Memory Range: 0xe0000000-0xefffffff (ro,non-prefetchable) I/O Ports: 0x4000-0x403f (rw) IRQ: 28 (385 events) Module Alias: "pci:v00008086d00000166sv000017AAsd000021F9bc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown Primary display adapter: #9 I am using XFCE as my desktop -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 928608] New: Mousepad: wrong syntax highlight
by bugzilla_noreply＠novell.com 24 Jan '18

24 Jan '18

http://bugzilla.opensuse.org/show_bug.cgi?id=928608 Bug ID: 928608 Summary: Mousepad: wrong syntax highlight Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: Other OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce(a)forge.provo.novell.com Reporter: justaz.home(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 632366 --> http://bugzilla.opensuse.org/attachment.cgi?id=632366&action=edit Bad highlight Mousepad 0.4.0 Color scheme "Tango" language: Script > sh Wrong syntax highlight near line 56 and further (attached images) -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 944653] New: Mouse pointer disappers
by bugzilla_noreply＠novell.com 17 Jan '18

17 Jan '18

http://bugzilla.opensuse.org/show_bug.cgi?id=944653 Bug ID: 944653 Summary: Mouse pointer disappers Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce(a)forge.provo.novell.com Reporter: rjschwei(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After logging out from XFCE (click on Name in panel, select "Log Out", confirm "Log Out") the mouse pointer is no longer available on the login screen. Therefore the user cannot reach the buttons in the upper right hand corner (switch icon to shutdown the machine) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 913686] New: Jack detection for Thinkpad T420 in docking station regresses to openSUSE 13.1
by bugzilla_noreply＠novell.com 17 Jan '18

17 Jan '18

http://bugzilla.opensuse.org/show_bug.cgi?id=913686 Bug ID: 913686 Summary: Jack detection for Thinkpad T420 in docking station regresses to openSUSE 13.1 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: markus.zimmermann(a)nethead.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am using a Thinkpad T420 in a docking station. I use the audio out of the docking station. When I play music the sound is working fine coming from the docking station. However, when I plug in my headphones to the Thinkpad audio out I expect that the sound of the docking station is muted but sound is then coming out of both, the docking station and headphones. This was working with openSUSE 13.1. Furthermore when I unplug the audio of the docking station and headphones I expect that the Thinkpad speakers are used. However, this only works when I plugout the audio of the docking station as last. When I plug out the headphones as last the speakers are muted. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 958329] New: postfix fails to start when openslp is not installed
by bugzilla_noreply＠novell.com 13 Jan '18

13 Jan '18

http://bugzilla.suse.com/show_bug.cgi?id=958329 Bug ID: 958329 Summary: postfix fails to start when openslp is not installed Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jdsn(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 658701 --> http://bugzilla.suse.com/attachment.cgi?id=658701&action=edit patch for cond_slp.systemd in the postfix-SuSE tarball Via a sysconfig variable an admin can disable to promote the postfix service via SLP. The script that handles this checks for the openslp binary and exits with exit code 1 if the binary is missing. This exit 1 is interpreted by systemd as a failure and as a result it kills the postfix service (right after starting it). As the default of the sysconfig variable to promote postfix via SLP it is not possible to start postfix with the default configuration. There is even no error or hint in the logs, why it fails. Background: I installed a minimal server system with only postfix, this image does not contain openslp (as it is not requried by anything in the minimal server pattern or postfix - which is fine). My proposed fix would be to regard the absence of the openslp binary the same as disabling the above mentioned variable. The attached patch solves the isse. Thanks for adding this to the package and including it into the next regular update for openSUSE Leap 42.1. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 946555] New: Yast fails to setup Automount
by bugzilla_noreply＠novell.com 13 Jan '18

13 Jan '18

http://bugzilla.suse.com/show_bug.cgi?id=946555 Bug ID: 946555 Summary: Yast fails to setup Automount Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: Other OS: openSUSE 13.1 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: k.fb(a)vink-slott.dk QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Configuring a fresh install (minimum server textmode) to use ldap for automount and with "Use TLS" enabled will not succeed. At autofs startup the log shows: automount[3276]: bind_ldap_simple: lookup(ldap): Unable to bind to the LDAP server: (default), error Can't contact LDAP server To make autofs work I installed openldap-client and configured /etc/openldap/ldap.conf with relevant entries. uri ldap://my.server.dk base dc=whatever... TLS_CACERTDIR /etc/ssl/certs I would think this should have been setup by Yast. -- You are receiving this mail because: You are on the CC list for the bug.

1 2