February 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1123898] new rule for libmtp-udev
by bugzilla_noreply＠novell.com 01 Feb '19

01 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1123898 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening(a)forge.pr |meissner(a)suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1121076] midori 7.0.git20181130-1.1 segfaults
by bugzilla_noreply＠novell.com 01 Feb '19

01 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1121076 http://bugzilla.suse.com/show_bug.cgi?id=1121076#c3 --- Comment #3 from Maurizio Galli <maurizio.galli(a)gmail.com> --- I asked midori developer to take a look at it too and I’m adding him in the loop. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1119649] Realtek r8169 receive performance regression in kernel 4.19
by bugzilla_noreply＠novell.com 01 Feb '19

01 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1119649 http://bugzilla.suse.com/show_bug.cgi?id=1119649#c37 --- Comment #37 from david chang <dchang(a)suse.com> --- (In reply to Martti Laaksonen from comment #31) > (In reply to david chang from comment #30) > > (In reply to david chang from comment #29) > > > Hi, > > > > > > There is a similar issue upstream but with different chip. > > > https://lore.kernel.org/netdev/aead4da3-e1b0-ab6c-2842-634e175b33ab@gmail. > > > com/ > > > > > > Could you give it a try with the following kernel parameter separately. > > > - pcie_aspm=off > > > - pcie_aspm.policy=performance > > > > > > Thanks! > > > > Also could you please get the register dump of the interface from v4.18 and > > v4.19 kernel? > > # ethtool -d enp1s0 > > Alright, I tried both kernel parameters with 4.18.15 and 4.19.11 kernels but > did not see any change in receive performance, i.e. kernel 4.18.15 performs > well whereas kernel 4.19.11 crawls at 12 MB/s when receiving. > > That PCIe ASPM policy setting probably does nothing since the kernel reports > this: > tammi 31 18:20:52 darkangel kernel: ACPI FADT declares the system doesn't > support PCIe ASPM, so disable it > tammi 31 18:20:52 darkangel kernel: acpi PNP0A08:00: _OSC: OS supports > [ExtendedConfig ASPM ClockPM Segments MSI] > tammi 31 18:20:52 darkangel kernel: acpi PNP0A08:00: FADT indicates ASPM is > unsupported, using BIOS configuration > > Test results attached. The register dumps you asked are also included in the > results. Thank you for the testing! Did you ever do the performance test without NFS? ex: download directly or iperf.. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1121052] ghc should not use fixed subpackage versions
by bugzilla_noreply＠novell.com 01 Feb '19

01 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1121052 http://bugzilla.suse.com/show_bug.cgi?id=1121052#c4 --- Comment #4 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1121052) was mentioned in https://build.opensuse.org/request/show/669503 15.1 / ghc-bootstrap -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1095688] Missing package when installing digikam on OpenSUSE with GNOME
by bugzilla_noreply＠novell.com 01 Feb '19

01 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1095688 http://bugzilla.suse.com/show_bug.cgi?id=1095688#c1 --- Comment #1 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1095688) was mentioned in https://build.opensuse.org/request/show/669933 15.1 / digikam -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1120143] Raspberry Pi display is black after 20181214 update
by bugzilla_noreply＠novell.com 01 Feb '19

01 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1120143 http://bugzilla.suse.com/show_bug.cgi?id=1120143#c3 James Carter <jimc(a)math.ucla.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jimc(a)math.ucla.ed | |u) | --- Comment #3 from James Carter <jimc(a)math.ucla.edu> --- Created attachment 795761 --> http://bugzilla.suse.com/attachment.cgi?id=795761&action=edit Syslog at boot with dmesg output Starting with the Tumbleweed instance about a week before openSUSE-release-20190125-8.1.aarch64, the display is magically back to normal. (I was diverted by another issue and didn't get onto trying to identify just what went right, just was glad that I can see the screen again.) I'm still betting on a device tree issue. This isn't the Raspberry Pi laptop; it's a standard RPi 3B with a HDMI connection to the monitor. When it failed, the X-server would not start, sayind "no screens found" in Xorg.0.log, and no video went out to the monitor, causing the black screen. Now the X-server, display manager, and desktop are behaving as they did before 2018-12-14. I haven't had issues with I2C, but haven't tried anything fancy on that bus, so I wouldn't have noticed problems. At boot I dump dmesg into syslog, and I've attached all the boot messages that were logged, but this is for the *working* kernel; messages from failing versions have rotated into oblivion, sorry. Please ignore chaotic clock sync, which is "normal" on a RPi (no realtime clock). Search for "Booting Linux" to find the start of dmesg. We'll probably never be sure what went wrong in 2018-12-14. Let's close this report. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1120087] NFS server fails after a suspend system
by bugzilla_noreply＠novell.com 01 Feb '19

01 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1120087 http://bugzilla.suse.com/show_bug.cgi?id=1120087#c3 Neil Brown <nfbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #3 from Neil Brown <nfbrown(a)suse.com> --- Thanks. After the suspend/resume we see: /proc/fs/nfsd/threads:0 where is was '4' before hand. So the nfs server had been stopped - no threads running any more. Also 4 services have disappears from sys systemctl listing: nfsserver.service nfs-mountd.service nfs-server.service nfs-idmapd.service Presumably that have been stopped - inactive services aren't matched by wildcards. It might be useful to see systemctl status nfsserver nfs-mountd nfs-server nfs-idmapd after the suspend/resume. It seems like something ran systemctl stop nfs-server or similar. I cannot think of anything that would do that. running systemctl restart nfs-server after the suspend/resume would getting you working again, but you don't really want to do that. Maybe getting systemd debug logs would help. You would need to reboot and add debug printk.devkmsg=on to the command line (interrupt grub with 'e' to edit) Then suspend/resume, then dmesg > file and attach the file. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1120747] Unknown symbols listed when loading snd_hda_core
by bugzilla_noreply＠novell.com 01 Feb '19

01 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1120747 http://bugzilla.suse.com/show_bug.cgi?id=1120747#c19 --- Comment #19 from Daniel Molkentin <daniel.molkentin(a)suse.com> --- I guess the problem is that files in /etc/sysconfig usually are supposed to take effect without more action. Otherwise, I would have proposed to either force-load or blacklist the modules, but that needs some script running after editing the file. -- You are receiving this mail because: You are on the CC list for the bug.

1 0