February 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1023761] New: VUL-0: mupdf: heap-based buffer overflow in fz_subsample_pixmap
by bugzilla_noreply＠novell.com 06 Feb '17

06 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1023761 Bug ID: 1023761 Summary: VUL-0: mupdf: heap-based buffer overflow in fz_subsample_pixmap Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: mikhail.kasimov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Ref: http://seclists.org/oss-sec/2017/q1/322 ================================================== Hello, there in an heap overflow in fz_subsample_pixmap. The bug was discovered by Kamil Frankowicz which said to have tested it against the current git head. The same testcase does not crash the current stable 1.10a, but I can confirm (with a round of fuzzing on 1.10a) that stable is affected. No fix atm. Details: https://bugs.ghostscript.com/show_bug.cgi?id=697515 Reproducer for 1.10a: https://github.com/asarubbo/poc/blob/master/00148-mupdf-heapoverflow-fz_sub… -- Agostino Sarubbo Gentoo Linux Developer ================================================== https://software.opensuse.org/package/mupdf TW and 42.2: 1.10a 42.1: 1.7a -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1023635] New: Regression with synergy 1.8.7: right half of screen not reachable any more
by bugzilla_noreply＠novell.com 06 Feb '17

06 Feb '17

http://bugzilla.novell.com/show_bug.cgi?id=1023635 Bug ID: 1023635 Summary: Regression with synergy 1.8.7: right half of screen not reachable any more Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The recent synergy update in tumbleweed to 1.8.7 broke my synergy setup. The mouse on the synergy client couldn't be moved past ~1200 pixel from the left corner of the screen any more. I am certain that the update of the synergy package was causing the problem. synergy 1.8.2-1.3 worked fine. This is how my screen looks like. I have 2 1920x1080 set up vertically next to each other (DP1-3 then DP1-1), plus my 1920x1080 laptop screen to the right (eDP-1). mwilck@apollon:~> xrandr Screen 0: minimum 320 x 200, current 4080 x 1920, maximum 8192 x 8192 eDP-1 connected 1920x1080+2160+840 (normal left inverted right x axis y axis) 309mm x 174mm 1920x1080 60.02*+ 47.99 DP-1-1 connected 1080x1920+1080+0 left (normal left inverted right x axis y axis) 527mm x 297mm 1920x1080 60.00*+ DP-1-3 connected primary 1080x1920+0+0 left (normal left inverted right x axis y axis) 518mm x 324mm 1920x1080 60.00* The synergy server ("artemis") is synergy 1.7.6 running on a Fedora 24 system. synergy.conf looks as follows. The Tumbleweed system that failed was "apollon". System "zeus" was switched off. section: screens artemis: halfDuplexCapsLock = false halfDuplexNumLock = false halfDuplexScrollLock = false xtestIsXineramaUnaware = false switchCorners = none switchCornerSize = 0 apollon: halfDuplexCapsLock = false halfDuplexNumLock = false halfDuplexScrollLock = false xtestIsXineramaUnaware = false switchCorners = none switchCornerSize = 0 zeus: halfDuplexCapsLock = false halfDuplexNumLock = false halfDuplexScrollLock = false xtestIsXineramaUnaware = false switchCorners = none switchCornerSize = 0 end section: aliases apollon: apollon.local apollon.suse.de apollon.mittagstun.de artemis: artemis.local artemis.mittagstun.de zeus: zeus.local zeus.mittagstun.de end section: links artemis: right = apollon down = zeus apollon: left = artemis down = zeus zeus: up = artemis left = artemis right = apollon end section: options relativeMouseMoves = false screenSaverSync = false win32KeepForeground = false switchCorners = none switchCornerSize = 0 end -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1023760] New: VUL-0: mupdf: NULL pointer dereference in dodrawpage
by bugzilla_noreply＠novell.com 06 Feb '17

06 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1023760 Bug ID: 1023760 Summary: VUL-0: mupdf: NULL pointer dereference in dodrawpage Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: mikhail.kasimov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Ref: http://seclists.org/oss-sec/2017/q1/321 ============================================= Hello, A null pointer dereference discovered by Kamil Frankowicz was fixed in mupdf. Commit fix: http://git.ghostscript.com/?p=mupdf.git;a=commitdiff;h=40ac85bfb676bb4373bd… Details: https://bugs.ghostscript.com/show_bug.cgi?id=697514 -- Agostino Sarubbo Gentoo Linux Developer ============================================= https://software.opensuse.org/package/mupdf TW and 42.2: 1.10a 42.1: 1.7a -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1022441] Marvell 88SE91xx raid not detected during install
by bugzilla_noreply＠novell.com 06 Feb '17

06 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1022441 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Normal -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1022727] yast2 problem: Window does not open if started remotely via ssh
by bugzilla_noreply＠novell.com 06 Feb '17

06 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1022727 http://bugzilla.suse.com/show_bug.cgi?id=1022727#c15 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #15 from Stefan Hundhammer <shundhammer(a)suse.com> --- OK, so we did things in parallel. Sorry for that. Reopening to minimize the confusion. BNC screening team: Please notice that this is an X11 or Qt problem, not a YaST problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1023460] systemd on s390x cannot cope with RestrictAddressFamilies in service files
by bugzilla_noreply＠novell.com 06 Feb '17

06 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1023460 http://bugzilla.opensuse.org/show_bug.cgi?id=1023460#c3 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fbui(a)suse.com --- Comment #3 from Franck Bui <fbui(a)suse.com> --- How about disabling RestrictAddressFamilies= on s390 as well instead of backporting a big chunk of new code ? After all this is TW and it can wait for the release of v233 in order to get this new feature like it was decided for i686 ? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 904015] outlined fonts didn't get their antialias enabled by fontconfig in openSUSE 13.2 and above
by bugzilla_noreply＠novell.com 06 Feb '17

06 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=904015 http://bugzilla.suse.com/show_bug.cgi?id=904015#c58 --- Comment #58 from Petr Gajdos <pgajdos(a)suse.com> --- (In reply to Petr Gajdos from comment #57) > This looks correctly to me: for size=8, antialias is of, autohinting not antialias is off -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 904015] outlined fonts didn't get their antialias enabled by fontconfig in openSUSE 13.2 and above
by bugzilla_noreply＠novell.com 06 Feb '17

06 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=904015 http://bugzilla.suse.com/show_bug.cgi?id=904015#c57 --- Comment #57 from Petr Gajdos <pgajdos(a)suse.com> --- (In reply to Vadim Krevs from comment #55) > $ fc-match -v sans:size=8 | grep 'family\|hint\|alias' > Fontconfig warning: "/home/vadymk/.config/fontconfig/fonts.conf", line 37: > Having multiple values in <test> isn't supported and may not work as expected > Fontconfig warning: "~/.fonts.conf", line 37: Having multiple values in > <test> isn't supported and may not work as expected > family: "Arial"(s) > familylang: "en"(s) > antialias: False(w) > hintstyle: 3(i)(w) > hinting: True(w) > autohint: False(w) > force_hintstyle: "none"(w) > force_autohint: False(w) > search_metric_aliases: True(w) This looks correctly to me: for size=8, antialias is of, autohinting not forced, hintstyle full, hinting true. But note you have Arial instead of Tahoma standing for sans-serif. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 904015] outlined fonts didn't get their antialias enabled by fontconfig in openSUSE 13.2 and above
by bugzilla_noreply＠novell.com 06 Feb '17

06 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=904015 http://bugzilla.suse.com/show_bug.cgi?id=904015#c56 --- Comment #56 from Petr Gajdos <pgajdos(a)suse.com> --- Indeed, looks like a user setting problem. Here you are: (In reply to Vadim Krevs from comment #55) > <?xml version='1.0'?> > <!DOCTYPE fontconfig SYSTEM 'fonts.dtd'> > <fontconfig> > <match target="font"> Turn on autohint for every font. > <edit mode="assign" name="autohint"> > <bool>true</bool> > </edit> > </match> > <match target="font"> > <test compare="more" name="weight"> > <const>medium</const> > </test> > <edit mode="assign" name="autohint"> > <bool>false</bool> > </edit> Do not force autohint, for _every_font_, for weight >= demibold for whatever reason. > </match> > <match target="font"> > <test name="family"> > <string>Tahoma</string> > <string>Andale Mono</string> > <string>Arial</string> > <string>Comic Sans MS</string> > <string>Georgia</string> > <string>Impact</string> > <string>Trebuchet MS</string> > <string>Verdana</string> > <string>Courier New</string> > <string>Times New Roman</string> > <string>Webdings</string> > <string>Albany AMT</string> > <string>Thorndale AMT</string> > <string>Cumberland AMT</string> > <string>Andale Sans</string> > <string>Andy MT</string> > <string>Bell MT</string> > <string>Monotype Sorts</string> > </test> >  > <test compare="more_eq" name="size" qual="any"> > <double>0</double> > </test> > <test compare="less_eq" name="size" qual="any"> > <double>9</double> > </test> > <edit name="autohint"> > <bool>false</bool> > </edit> Do not force autohint for smaller sizes for certain font families. > <edit mode="assign" name="antialias"> > <bool>false</bool> > </edit> > </match> > <match target="font"> > <edit mode="assign" name="rgba"> > <const>rgb</const> > </edit> > </match> > <dir>~/.fonts</dir> > <match target="font"> > <edit mode="assign" name="hinting"> > <bool>true</bool> > </edit> > </match> > <match target="font"> > <edit mode="assign" name="hintstyle"> > <const>hintfull</const> > </edit> > </match> > <match target="font"> > <edit mode="assign" name="antialias"> > <bool>true</bool> > </edit> > </match> > <match target="font"> > <test compare="more_eq" name="size" qual="any"> > <double>0</double> > </test> > <test compare="less_eq" name="size" qual="any"> > <double>8</double> > </test> > <edit mode="assign" name="antialias"> > <bool>false</bool> > </edit> > </match> > <match target="font"> > <test compare="more_eq" name="pixelsize" qual="any"> > <double>0</double> > </test> > <test compare="less_eq" name="pixelsize" qual="any"> > <double>11</double> > </test> > <edit mode="assign" name="antialias"> > <bool>false</bool> > </edit> > </match> > </fontconfig> All in all, autohint is forced for all fonts with weight <= medium and size, even for Tahoma and others listed in the long match which should not. Also antialias is set to false for certain families/sizes, then it is set to true for all fonts and again set to false for all fonts for certain sizes. Also following warning should not be overlooked: > Fontconfig warning: "/home/vadymk/.config/fontconfig/fonts.conf", line 37: > Having multiple values in <test> isn't supported and may not work as expected It is evident that the file was written by more entities. I guess you have two possibilities after backuping and removing this file: 1. rely on distro setting: we do not support for excluding ranges from antialias though [in fonts-config and/or yast2-fonts, I will consider to add it at least for fonts-config, for yast2-fonts it won't be trivial and even include libfontspecimen changes], so you need to add to your ~/.config/fontsconfig/fonts.conf: <?xml version="1.0"?> <!DOCTYPE fontconfig SYSTEM "fonts.dtd"> <fontconfig> <match target="font"> <test name="font_type"> <string>TT Instructed Font</string> </test> <test name="size" compare="less_eq"> <double>8.0</double> </test> <edit name="antialias"> <bool>false</bool> </edit> </match> </fontconfig> Do not use KDE font setting afterwards, without removing the file again. 2. rely on settings written by KDE: After backuping and removing /home/vadymk/.config/fontconfig/fonts.conf, KDE should write a new one. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1022727] yast2 problem: Window does not open if started remotely via ssh
by bugzilla_noreply＠novell.com 06 Feb '17

06 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1022727 http://bugzilla.suse.com/show_bug.cgi?id=1022727#c14 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |INVALID --- Comment #14 from Stefan Hundhammer <shundhammer(a)suse.com> --- Well, but then this is a completely separate problem. Please file a separate bug report for this, otherwise everything gets confused. Closing this one again so we can keep track of things. -- You are receiving this mail because: You are on the CC list for the bug.

1 0