February 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1007325] Kernel oops when dial up usb modem is plugged
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1007325 http://bugzilla.opensuse.org/show_bug.cgi?id=1007325#c6 Luiz Angelo Daros de Luca <luizluca(a)tre-sc.jus.br> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(luizluca(a)tre-sc.j | |us.br) | --- Comment #6 from Luiz Angelo Daros de Luca <luizluca(a)tre-sc.jus.br> --- Sorry, I missed your request. Yes, with your build does not oops when I plug the kernel. As an "extra", the modem actually works. I also tested with a newer kernel 4.8.13 and it was also OK. The only residual problem is that I get this message every time I plug it: [ 395.138460] usb 3-2: device descriptor read/64, error -71 [ 395.374461] usb 3-2: device descriptor read/64, error -71 Even on kernel 4.9.3. Anyway, it works as expected. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 902612] New: systemd automounts manually umounted devices again
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=902612 Bug ID: 902612 Summary: systemd automounts manually umounted devices again Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sweet_f_a(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Just noticed that systemd automatically mounts devices again allthough I've manually umounted them. Here is what I did $ mount | grep local /dev/mapper/vg0-local on /mnt/local type ext4 (rw,relatime,data=ordered) ## umount and disable that lvm device $ umount /mnt/local $ lvchange -an vg0/local systemd[1]: Stopping File System Check on /dev/vg0/local... systemd[1]: Stopped File System Check on /dev/vg0/local. ## enable device again $ lvchange -ay vg0/local systemd[1]: Found device /dev/mapper/vg0-local. systemd[1]: Found device /dev/disk/by-uuid/177a415d-174d-4c30-8897-5502c0419ef8. systemd[1]: Found device /dev/disk/by-id/dm-uuid-LVM-uF33oY4c9yu00EPAP42a8A2XZCfQTRRPGfiv0cNZRwPKIRJnOboscsc1z60174dd. systemd[1]: Found device /dev/disk/by-id/dm-name-vg0-local. systemd[1]: Found device /dev/dm-0. systemd[1]: Found device /sys/devices/virtual/block/dm-0. systemd[1]: Starting File System Check on /dev/vg0/local... systemd-fsck[6386]: /dev/mapper/vg0-local: clean, 648240/3276800 files, 9308645/13107200 blocks systemd[1]: Started File System Check on /dev/vg0/local. systemd[1]: Mounting /mnt/local... kernel: [ 5542.579700] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: acl,user_xattr systemd[1]: Mounted /mnt/local. $ mount | grep local /dev/mapper/vg0-local on /mnt/local type ext4 (rw,relatime,data=ordered) So what kind of automount is this? How to disable this odd behaviour? -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1017695] openSuse 42.2: Boot on broken RAID 1 with missing disk fails. Looks linked to dracut premount hook script (start job running with nolimit timeout)
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1017695 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|ibs:running:1835:moderate |ibs:running:1835:moderate | |ibs:running:4068:moderate | |ibs:running:4115:moderate -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 902375] mkinitrd/dracut ignores symlink in kernel argument
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=902375 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|ibs:running:4068:low |ibs:running:4068:moderate -- 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 02 Feb '17

02 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1022727 Arvin Schnell <aschnell(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|yast-internal(a)suse.de |bnc-team-screening(a)forge.pr | |ovo.novell.com -- 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 02 Feb '17

02 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1022727 Arvin Schnell <aschnell(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |X11 Applications QA Contact|jsrain(a)suse.com |qa-bugs(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1023198] New: Leap 42.2 bails out with signal 11 during initial installation
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1023198 Bug ID: 1023198 Summary: Leap 42.2 bails out with signal 11 during initial installation Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: magnus(a)linuxtag.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I downloaded the installation Leap 42.2 ISO from https://software.opensuse.org/422/en and verified its SHA 256 checksum: $ ls -l insgesamt 4281368 -rw-r--r-- 1 magnus magnus 4384096256 Feb 2 00:44 openSUSE-Leap-42.2-DVD-x86_64.iso -rw-r--r-- 1 magnus magnus 630 Feb 2 00:44 openSUSE-Leap-42.2-DVD-x86_64.iso.sha256 $ sha256sum -c openSUSE-Leap-42.2-DVD-x86_64.iso.sha256 openSUSE-Leap-42.2-DVD-x86_64.iso: OK I wrote the image to a verified and working USB stick with 32 GByte capacity with # dd if=openSUSE-Leap-42.2-DVD-x86_64.iso of=/dev/sdb When booting this image on either a Lenovo Thinkpad X1 Carbon, 3rd gen or a Lenovo Thinkpad T460p (bought 2016), the slash screen pops up. Selecting the boot Linux item to start the live CD the kernel boots, but is interrupted by a "Signal 11" message on the lower part of the screen. Please advise how to further debug this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1023243] New: Openjdk crashes frequently possibly since Firefox NSS updates
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1023243 Bug ID: 1023243 Summary: Openjdk crashes frequently possibly since Firefox NSS updates Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Critical Priority: P5 - None Component: Java Assignee: bnc-team-java(a)forge.provo.novell.com Reporter: jweberhofer(a)weberhofer.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Java crashes in many situations since since some days. It seems to be related with the update to NSS 3.28. For users of Java (Remote Applications, Eclipse, Maven) the system gets unusable. Please read: https://bugzilla.redhat.com/show_bug.cgi?id=1415137 https://bugzilla.mozilla.org/show_bug.cgi?id=1334108 https://bugs.gentoo.org/show_bug.cgi?id=605430 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1023240] New: ask dialog selection returns label instead of value when type=symbol
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1023240 Bug ID: 1023240 Summary: ask dialog selection returns label instead of value when type=symbol Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST Assignee: autoyast-maintainers(a)suse.de Reporter: luizluca(a)tre-sc.jus.br QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, I configured a simple ask combo like: <ask> <dialog config:type="integer">2</dialog> <element config:type="integer">2</element> <title>Configuração do Armazenamento</title> <help/> <stage>initial</stage> <frametitle>Disco SSD (Solid State Disk)</frametitle> <question>Qual disco &SSD será utilizado para sistema e cache?</question> <selection config:type="list"> <entry> <value>sdb</value> <label>sdb: ATA VBOX HARDDISK (29.3G)</label> </entry> </selection> <default>sdb</default> <pathlist config:type="list"> <path>partitioning,0,device</path> </pathlist> </ask> If I add <type>symbol</type>, autoyast writes the label contents into partitioning,0,device. If I remove it, it works. According to what I understood from docs, type=symbol is default when a select is present. Is this expected? -- 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 02 Feb '17

02 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=904015 http://bugzilla.suse.com/show_bug.cgi?id=904015#c45 --- Comment #45 from Petr Gajdos <pgajdos(a)suse.com> --- Let's try step by step on 42.2 leap system. I do not have access to Tahoma font, I will try Arial which is downloaded by fetchmsttfonts instead. (1) Let us first look at the font, if it meet the requirments as displayed with freetype2: $ ftview 10 /usr/share/fonts/truetype/arial.ttf then hit 'a' to turn off antialiasing and Up/Down to change size. Does the font fulfill your expectation for small sizes as rendered by freetype2? (2) Then, we need to ensure fontconfig gives correct rendering algorithm parameters. Before I do any configuration, I get: $ fc-match -v 'Arial:size=10' | grep 'alias\|hint' antialias: True(w) hintstyle: 3(i)(w) hinting: True(w) autohint: False(w) force_hintstyle: "none"(w) force_autohint: False(w) search_metric_aliases: True(w) $ Three last can be ignored, they just imply real rendering options. For size=10 we get full hinting (hintstyle=3, which is, iirc the only option anyway for BCI), rendering with BCI when the freetype library decides it has usable rendering instructions (autohint=false, it actually means 'do not force autohint') and antialias on. $ fc-match -v 'Arial:size=5' | grep 'alias\|hint\|size' Pattern has 44 elts (size 48) size: 5(f)(s) pixelsize: 5.20833(f)(s) antialias: True(w) hintstyle: 3(i)(w) hinting: True(w) autohint: False(w) [..] $ Lovering the size, fontconfig does not change rendering options, as expected. Now edit ~/.config/fontconfig/fonts.conf: <?xml version="1.0"?> <!DOCTYPE fontconfig SYSTEM "fonts.dtd"> <fontconfig> <alias> <family>sans-serif</family> <prefer> <family>Arial</family> </prefer> </alias> <match target="font"> <test name="font_type"> <string>TT Instructed Font</string> </test> <test name="pixelsize" compare="less_eq"> <double>8.0</double> </test> <edit name="antialias"> <bool>false</bool> </edit>  <edit name="autohint"> <bool>false</bool> </edit> </match> </fontconfig> <alias> is there to make sure Arial is preferred for given user. font_type='TT Instructed Font' is set for all fonts listed in /etc/fonts/conf.d/10-group-tt-hinted-fonts.conf, including Tahoma and Arial. Now: $ fc-match -v Arial:size=10 | grep 'hint\|alias\|size' Pattern has 44 elts (size 48) size: 10(f)(s) pixelsize: 10.4167(f)(s) antialias: True(w) hintstyle: 3(i)(w) hinting: True(w) autohint: False(w) [..] $ $ fc-match -v Arial:size=5 | grep 'hint\|alias\|size' Pattern has 44 elts (size 48) size: 5(f)(s) pixelsize: 5.20833(f)(s) antialias: False(w) hintstyle: 3(i)(w) hinting: True(w) autohint: False(w) [..] $ Antialias is off for the Arial:size=5. hinting need to be true in both cases. autohint is False to allow freetype2 to use font's instructions if there are any; again in both cases. NOTE: you see above the pixelsize is slightly above the requested size. If you want to request size=8, rather use 9.0 inside the fontconfig rule above. Webpage similar to following one should confirm it works: <html> <body> Pack my box with five dozen liquor jugs. Pack my box with five dozen liquor jugs. Pack my box with five dozen liquor jugs. Pack my box with five dozen liquor jugs. Pack my box with five dozen liquor jugs. Pack my box with five dozen liquor jugs. Pack my box with five dozen liquor jugs. Pack my box with five dozen liquor jugs. Pack my box with five dozen liquor jugs. Pack my box with five dozen liquor jugs. </body> </html> The jump between non-antialiased and antialiased font is evident or can be proved by xmag utility. Now the system should use this settings. Well. It depends how given application honor fontconfig recommendation how to render a font, of course. You should try another applications, kde, non-kde, etc. If that does not work only for kde applications, for example, then it might be there is some clash between kde and base system fontconfig settings or its interpretion. I needed to increase pixelsize to 14.0 in the fontconfig rule though as 8.0 is simply too low. Arial and even Liberation families are rendered black&white for me on fx. firefox, icewm and pidgin as expected. -- You are receiving this mail because: You are on the CC list for the bug.

1 0