November 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 909119] New: Evince is compiled without XPS support
by bugzilla_noreply＠novell.com 07 Feb '18

07 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=909119 Bug ID: 909119 Summary: Evince is compiled without XPS support Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: a7169932(a)drdrb.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have libgxps2 installed (I think I got it OOTB), but I can't open OXPS file in Evince. I guess it's compiled without XPS support. Can you change it? -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 927851] New: Firefox 37 always crashes on streaming start at www.sport1.fm
by bugzilla_noreply＠novell.com 06 Feb '18

06 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=927851 Bug ID: 927851 Summary: Firefox 37 always crashes on streaming start at www.sport1.fm Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86 OS: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: schaefer.frank(a)gmx.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Firefox always crashes on streaming start at www.sport1.fm Console output: ** (firefox:11698): CRITICAL **: gst_app_src_set_size: assertion 'GST_IS_APP_SRC (appsrc)' failed [NPAPI 11728] ###!!! ABORT: Aborting on channel error.: file /home/abuild/rpmbuild/BUILD/mozilla/ipc/glue/MessageChannel.cpp, line 1591 [NPAPI 11728] ###!!! ABORT: Aborting on channel error.: file /home/abuild/rpmbuild/BUILD/mozilla/ipc/glue/MessageChannel.cpp, line 1591 Tested 37.0.1 (Update-repo) and 37.0.2 (Mozilla-repo) Firefox 36 (and older) didn't crash. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 904321] New: Evince can't render certain letter combinations
by bugzilla_noreply＠novell.com 06 Feb '18

06 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=904321 Bug ID: 904321 Summary: Evince can't render certain letter combinations Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: hogg.bob.2(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 612734 --> http://bugzilla.opensuse.org/attachment.cgi?id=612734&action=edit Snippet of a PDF document showing the rendering issue (in PNG format) Evince cannot seem to render certain combinations of sequential letters - particularly the sequences "fi" and "fl". It just displays blank space in that area. But the letters "f", "i", and "l" all display correctly in different sequences. gv/GhostView can display them fine, so I doubt this is a font issue. (I did uninstall most of the non-English fonts that come installed with openSUSE by default to save space, but that should not cause English text to display incorrectly) The attachment is a snippet of a PDF document that shows the rendering issue - the words with the problem are "specified"/"unspecified". (I can't post the PDF itself because of copyright issues, but I can make a minimal example if needed). The bug has been fairly consistently reproducible across more than one PDF document. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 954143] New: Leap (KDE5) doesn't know what to do with an .rpm file. Chrome 64bit and Skype tested.
by bugzilla_noreply＠novell.com 05 Feb '18

05 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=954143 Bug ID: 954143 Summary: Leap (KDE5) doesn't know what to do with an .rpm file. Chrome 64bit and Skype tested. Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: jedibeeftrix(a)ymail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0 Build Identifier: Downloaded the rpm from google for 64bit Chrome and tried to click on it. Ark! Yast not even suggested, why? So, I add Yast as the preferred option for .rpm files and click on it again. Little Yast symbol pops up in a 'egg-timer' kind of way, few seconds later it disappears. Nothing. So i load up Yast, select import, and point it at the rpm. Error message. Is the whole problem because Leap is being clever and knows the 'opensuse' .rpm file is incompatible, or is this buggy behaviour? Same thing happens with Skype i586 .rpm from MS. Using 13.2 on my laptop i can open "apper software management" from the start menu. However, on Leap a start menu search for "apper" finds nothing. Likewise, "open with" on file properties cannot locate apper in system or utilities. Opening konsole in su and typing "run apper" gets nothing either... Reproducible: Always Steps to Reproduce: 1. download .rpm with "open with" (Yast) selected 2. open .rpm from download folder using Yast 3. open Yast, and "import" .rpm package from download folder 4. search for apper to use instead of Yast (nowhere to be found) Actual Results: nothing. system does not currently do anything with an .rpm file. Expected Results: .rpm opened with Yast, then proceeds to install using the Yast GUI Vanilla leap install working fine out the box, just can't modify it with new .rpm packages. -- You are receiving this mail because: You are on the CC list for the bug.

1 23

[Bug 904089] New: can not add openvpn connection with gnome-control-center
by bugzilla_noreply＠novell.com 30 Jan '18

30 Jan '18

http://bugzilla.opensuse.org/show_bug.cgi?id=904089 Bug ID: 904089 Summary: can not add openvpn connection with gnome-control-center Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mgoppold(a)web.de 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/37.0.2062.94 Safari/537.36 Build Identifier: fresh install: try to add a openvpn connection but all entries are disabled Reproducible: Always Steps to Reproduce: 1. open gnome-control-center 2. open network 3. dismiss incompatible network service 4. click [+] to add a connection 5. select VPN 6. select OpenVPN 7. Dialog open but all disabled same result as user and root -- 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