June 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1037891] All YaST module window names show "ruby" instead of a more specifc name (was: Yast module windows in Plasma: generic x window icon and grouped as "ruby" in task manager)
by bugzilla_noreply＠novell.com 12 Jun '17

12 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1037891 http://bugzilla.suse.com/show_bug.cgi?id=1037891#c37 --- Comment #37 from Lukas Ocilka <locilka(a)suse.com> --- But there wasn't "nothing", it was IMO just invisible (hidden by QSS). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1043602] systemd fstrim timer defaults is insanely long
by bugzilla_noreply＠novell.com 12 Jun '17

12 Jun '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1043602 http://bugzilla.opensuse.org/show_bug.cgi?id=1043602#c6 Stanislav Brabec <sbrabec(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #6 from Stanislav Brabec <sbrabec(a)suse.com> --- Well, the interval was selected by the upstream after a long discussion. We have no plans to diverge util-linux from the upstream. If there are new facts about recent SSD discs and there is a statistics about SSD lifetime and performance with various fstrim setups, please open a new discussion in the util-linux-ng mailing list (and include people from the thread below to Cc). Running fstrim more often has unwanted side effects: - Running TRIM has performance impact. - TRIM itself can take long time to complete. - TRIM can shorten life of the SSD disc. Better heuristics would be fstrim based on the amount of data written. But something like that is not yet implemented and not easy to implement. Here is the reference to the discussion: http://www.spinics.net/lists/util-linux-ng/msg09133.html Especially this mail explains the interval: http://www.spinics.net/lists/util-linux-ng/msg09132.html From: "Theodore Ts'o" <tytso@xxxxxxx> Subject: Re: [PATCH] fstrim: add systemd units Date: Wed, 9 Apr 2014 14:39:54 -0400 For those SSD's that have a problem, "mount -o discard" is a disaster. Some turn into bricks, others will have a degraded flash cells, many will cause extremely degraded performance for other processes. What I usually tell people as far as who ask me for advice is that once a week is usually sufficient, especially for most desktop and server systems. If you are running an extreme workload which is doing a huge number of random writes, then sure, running fstrim more frequently, or even using "mount -o discard" might make a lot more sense --- especially if you are using PCIe attached flash. But in those cases, the system administrator might not want be willing to tolerate the random latencies in performance that might show up when fstrim is running (for pretty much all SATA and SAS attached SSD's out there, they don't yet support queued trim, so each trim command requires draining the NCQ queue, which is why sending trim commands, whether via "mount -o discard" or via fstrim will incur a performance penalty to whatever else might be trying to use the disk at the time). I'll note BTW that even using "fstrim" could potentially brick an especially inexpensive/trashy SSD, although the vendor for whose drive had been most commonly accused of promulgating those to the world is out of business (although there are probably plenty of those SSD's still in use in various community distros' audiences.) Cheers, - Ted -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1030891] New: Split off ibdiagui from ibutils
by bugzilla_noreply＠novell.com 12 Jun '17

12 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1030891 Bug ID: 1030891 Summary: Split off ibdiagui from ibutils Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: pth(a)suse.com Reporter: behlert(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Due to ibdiagui the package ibutils requires graphiz (via graphiz-tcl). Please split this into a separate package, so that it's possible to use ibutils even if only a terminal exists and no graphical packages are installed. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1043414] umount hangs on ppc64le -> reduced build power on OBS
by bugzilla_noreply＠novell.com 12 Jun '17

12 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1043414 http://bugzilla.suse.com/show_bug.cgi?id=1043414#c14 --- Comment #14 from Adrian Schröter <adrian(a)suse.com> --- The system has no /sys/block/*/wbt* file. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1043414] umount hangs on ppc64le -> reduced build power on OBS
by bugzilla_noreply＠novell.com 12 Jun '17

12 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1043414 http://bugzilla.suse.com/show_bug.cgi?id=1043414#c13 Adrian Schröter <adrian(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(adrian(a)suse.com) | --- Comment #13 from Adrian Schröter <adrian(a)suse.com> --- Created attachment 728611 --> http://bugzilla.suse.com/attachment.cgi?id=728611&action=edit kernel.trace.second.gz -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1043414] umount hangs on ppc64le -> reduced build power on OBS
by bugzilla_noreply＠novell.com 12 Jun '17

12 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1043414 http://bugzilla.suse.com/show_bug.cgi?id=1043414#c12 --- Comment #12 from Adrian Schröter <adrian(a)suse.com> --- Created attachment 728610 --> http://bugzilla.suse.com/attachment.cgi?id=728610&action=edit iostat.second.gz -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1043414] umount hangs on ppc64le -> reduced build power on OBS
by bugzilla_noreply＠novell.com 12 Jun '17

12 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1043414 http://bugzilla.suse.com/show_bug.cgi?id=1043414#c11 --- Comment #11 from Adrian Schröter <adrian(a)suse.com> --- It was (at least) hanging on mount point /var/cache/obs/worker/root_7/.mount that should be /dev/loop0 according to losetup. Doing the iostate and trace now again, loop devices number 0 1 2 und 3 are hanging atm. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1043653] Sensitivity/pressure data untweakable on Microsoft Precision touchpad on Dell XPS 13
by bugzilla_noreply＠novell.com 12 Jun '17

12 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1043653 http://bugzilla.suse.com/show_bug.cgi?id=1043653#c5 --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- It seems that the touchpad on your machine is supported by HID multitouch driver, i.e. it's dealt like a touchscreen stuff. That's the reason why synaptics setup doesn't take any effect. Although the hardware declares the synaptics device, too, the actually working device is hid-multitouch. Maybe the former is present for compatibility reason. You can try to blacklist hid-multitouch, for example, to see if there gives any behavior difference. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 997757] fstrim takes almost an hour, starves other IO-bound processes
by bugzilla_noreply＠novell.com 12 Jun '17

12 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=997757 http://bugzilla.suse.com/show_bug.cgi?id=997757#c7 Jeff Mahoney <jeffm(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jeffm(a)suse.com) | --- Comment #7 from Jeff Mahoney <jeffm(a)suse.com> --- Missed the very old needinfo on me. FITRIM is being called multiple times on the same file system. The only thing the file system can do here is cache past runs so we know what's already been trimmed and what hasn't. That's been pretty low on the priority list. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1041122] New: systemd-journal-remote missing from openSUSE 42.3
by bugzilla_noreply＠novell.com 12 Jun '17

12 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1041122 Bug ID: 1041122 Summary: systemd-journal-remote missing from openSUSE 42.3 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSUSE Tumbleweed provides systemd-journal-remote, however this subpackage is missing from 42.3. I would like to make use of that in the OpenStack infra for testing openSUSE in the OpenStack gating upstream. Please add it . -- You are receiving this mail because: You are on the CC list for the bug.

1 17