July 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1099899] btrfs maintenance makes OS unresponsive
by bugzilla_noreply＠novell.com 02 Jul '18

02 Jul '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1099899 http://bugzilla.opensuse.org/show_bug.cgi?id=1099899#c2 --- Comment #2 from Daniel Pecka <nettezzaumanaa(a)gmail.com> --- moreover, in this scope I can realize that it also significantly increases harddrive utilization decreasing the hardrive lifetime, making softerrors just killers and triggering not healthy drives to fail earlier and sudden regards, ddd ps. I think that Geeko hates this and fears that ... don't make Geeko suffer, don't torment him .. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1099899] btrfs maintenance makes OS unresponsive
by bugzilla_noreply＠novell.com 02 Jul '18

02 Jul '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1099899 http://bugzilla.opensuse.org/show_bug.cgi?id=1099899#c1 --- Comment #1 from Daniel Pecka <nettezzaumanaa(a)gmail.com> --- here is some discussion about btrfs-balance: https://github.com/firehol/netdata/issues/3203 btrfs-balance is very intensive operation and it's completely situational .. doing that at weekly basis as generic default for everybody who has btrfs is utterly and painfully wrong !!! in the other words, this hammer-style generic default is wrong and insane .. it's human-factor bug .. I wonder how it could sneak into the distro .. let's please find another solution to this .. regards, daniel -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1092839] brltty hogs USB serial ports without obvious way to disable
by bugzilla_noreply＠novell.com 02 Jul '18

02 Jul '18

http://bugzilla.suse.com/show_bug.cgi?id=1092839 http://bugzilla.suse.com/show_bug.cgi?id=1092839#c20 --- Comment #20 from Stanislav Brabec <sbrabec(a)suse.com> --- Stefan Brüns, comment 19: Sorry, I misunderstood. Move to a an optional sub-package will work. Maybe a combination of ZYPP USB hardware supplements would end with a ZYPP dialog similar to bug 1093378 comment 23 point 2, just on installation level. Supplements: modalias(usb:v10c4pea60d*dc*dsc*dp*ic*isc*ip*) Provides: udev_usb_rule_10c4_ea60 Conflicts: otherproviders(udev_usb_rule_10c4_ea60) It will complain that you are trying to install conflicting packages: brltty-udev-rules-serialbridge gpsd-udev-rules-serialbridge udev-udev-rules-generic-serialbridge and ask you to pick one. A problem will occur when a person will have more devices with the same id. None of these packages will fulfill the requirement. But as you pointed to, use of ATTRS{busnum} and ATTRS{devpath} would make possible to write rules that will be capable of doing that. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1093378] conflicting udev rules completely break USB Serial bridges
by bugzilla_noreply＠novell.com 02 Jul '18

02 Jul '18

http://bugzilla.suse.com/show_bug.cgi?id=1093378 http://bugzilla.suse.com/show_bug.cgi?id=1093378#c24 --- Comment #24 from Stanislav Brabec <sbrabec(a)suse.com> --- Stefan Brüns, comment 22: Thanks for the hint. So it is already possible. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1063638] btrfs balance renders system unresponsive and eventually even kills WiFi when quota is enabled - review I/O scheduling parameters of btrfsmaintenance
by bugzilla_noreply＠novell.com 02 Jul '18

02 Jul '18

http://bugzilla.novell.com/show_bug.cgi?id=1063638 http://bugzilla.novell.com/show_bug.cgi?id=1063638#c84 Daniel Pecka <nettezzaumanaa(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nettezzaumanaa(a)gmail.com --- Comment #84 from Daniel Pecka <nettezzaumanaa(a)gmail.com> --- it makes system unresponsive at all for couple of minutes ... here with fast ssd just 7 minutes ... it's crazy .. I've observed on servers a HA app doing switchover every times this takes a place .. we need to get rid of it # journalctl -b 0 -u btrfs\* -- Logs begin at Mon 2018-07-02 20:55:02 CEST, end at Mon 2018-07-02 21:11:01 CEST. -- Jul 02 20:55:16 linux-1b6m systemd[1]: Started Scrub btrfs filesystem, verify block checksums. Jul 02 20:55:16 linux-1b6m systemd[1]: Started Watch /etc/sysconfig/btrfsmaintenance. Jul 02 20:55:16 linux-1b6m systemd[1]: Started Balance block groups on a btrfs filesystem. Jul 02 20:55:16 linux-1b6m systemd[1]: Starting Update cron periods from /etc/sysconfig/btrfsmaintenance... Jul 02 20:55:16 linux-1b6m btrfsmaintenance-refresh-cron.sh[1678]: Refresh script btrfs-scrub.sh for uninstall Jul 02 20:55:16 linux-1b6m btrfsmaintenance-refresh-cron.sh[1678]: Refresh script btrfs-defrag.sh for uninstall Jul 02 20:55:16 linux-1b6m btrfsmaintenance-refresh-cron.sh[1678]: Refresh script btrfs-balance.sh for uninstall Jul 02 20:55:16 linux-1b6m btrfsmaintenance-refresh-cron.sh[1678]: Refresh script btrfs-trim.sh for uninstall Jul 02 20:55:16 linux-1b6m btrfsmaintenance-refresh-cron.sh[1678]: Refresh timer btrfs-scrub for monthly Jul 02 20:55:16 linux-1b6m btrfsmaintenance-refresh-cron.sh[1678]: Refresh timer btrfs-defrag for none Jul 02 20:55:17 linux-1b6m btrfsmaintenance-refresh-cron.sh[1678]: Refresh timer btrfs-balance for weekly Jul 02 20:55:17 linux-1b6m systemd[1]: Started Balance block groups on a btrfs filesystem. Jul 02 20:55:17 linux-1b6m btrfsmaintenance-refresh-cron.sh[1678]: Refresh timer btrfs-trim for none Jul 02 20:55:17 linux-1b6m btrfs-balance.sh[1888]: Before balance of / Jul 02 20:55:17 linux-1b6m btrfs-balance.sh[1888]: Data, single: total=15.01GiB, used=12.50GiB Jul 02 20:55:17 linux-1b6m btrfs-balance.sh[1888]: System, single: total=32.00MiB, used=16.00KiB Jul 02 20:55:17 linux-1b6m btrfs-balance.sh[1888]: Metadata, single: total=1.01GiB, used=745.58MiB Jul 02 20:55:17 linux-1b6m btrfs-balance.sh[1888]: GlobalReserve, single: total=44.00MiB, used=0.00B Jul 02 20:55:17 linux-1b6m btrfs-balance.sh[1888]: Filesystem Size Used Avail Use% Mounted on Jul 02 20:55:17 linux-1b6m btrfs-balance.sh[1888]: /dev/mapper/rpool-root 33G 15G 18G 45% / Jul 02 20:55:17 linux-1b6m systemd[1]: Started Update cron periods from /etc/sysconfig/btrfsmaintenance. Jul 02 20:55:19 linux-1b6m btrfs-balance.sh[1888]: Done, had to relocate 0 out of 22 chunks Jul 02 20:55:19 linux-1b6m btrfs-balance.sh[1888]: Dumping filters: flags 0x1, state 0x0, force is off Jul 02 20:55:19 linux-1b6m btrfs-balance.sh[1888]: DATA (flags 0x2): balancing, usage=1 Jul 02 20:55:19 linux-1b6m btrfs-balance.sh[1888]: Done, had to relocate 0 out of 22 chunks Jul 02 20:55:19 linux-1b6m btrfs-balance.sh[1888]: Dumping filters: flags 0x1, state 0x0, force is off Jul 02 20:55:19 linux-1b6m btrfs-balance.sh[1888]: DATA (flags 0x2): balancing, usage=5 Jul 02 20:55:19 linux-1b6m btrfs-balance.sh[1888]: Done, had to relocate 0 out of 22 chunks Jul 02 20:55:19 linux-1b6m btrfs-balance.sh[1888]: Dumping filters: flags 0x1, state 0x0, force is off Jul 02 20:55:19 linux-1b6m btrfs-balance.sh[1888]: DATA (flags 0x2): balancing, usage=10 Jul 02 20:55:19 linux-1b6m btrfs-balance.sh[1888]: Done, had to relocate 0 out of 22 chunks Jul 02 20:55:19 linux-1b6m btrfs-balance.sh[1888]: Dumping filters: flags 0x1, state 0x0, force is off Jul 02 20:55:19 linux-1b6m btrfs-balance.sh[1888]: DATA (flags 0x2): balancing, usage=20 Jul 02 20:55:19 linux-1b6m btrfs-balance.sh[1888]: Done, had to relocate 0 out of 22 chunks Jul 02 20:56:47 linux-1b6m btrfs-balance.sh[1888]: Dumping filters: flags 0x1, state 0x0, force is off Jul 02 20:56:47 linux-1b6m btrfs-balance.sh[1888]: DATA (flags 0x2): balancing, usage=30 Jul 02 20:56:47 linux-1b6m btrfs-balance.sh[1888]: Done, had to relocate 1 out of 22 chunks Jul 02 20:57:29 linux-1b6m btrfs-balance.sh[1888]: Dumping filters: flags 0x1, state 0x0, force is off Jul 02 20:57:29 linux-1b6m btrfs-balance.sh[1888]: DATA (flags 0x2): balancing, usage=40 Jul 02 20:57:29 linux-1b6m btrfs-balance.sh[1888]: Done, had to relocate 1 out of 22 chunks Jul 02 20:58:10 linux-1b6m btrfs-balance.sh[1888]: Dumping filters: flags 0x1, state 0x0, force is off Jul 02 20:58:10 linux-1b6m btrfs-balance.sh[1888]: DATA (flags 0x2): balancing, usage=50 Jul 02 20:58:10 linux-1b6m btrfs-balance.sh[1888]: Done, had to relocate 1 out of 22 chunks Jul 02 20:58:10 linux-1b6m btrfs-balance.sh[1888]: Done, had to relocate 0 out of 22 chunks Jul 02 20:58:10 linux-1b6m btrfs-balance.sh[1888]: Dumping filters: flags 0x6, state 0x0, force is off Jul 02 20:58:10 linux-1b6m btrfs-balance.sh[1888]: METADATA (flags 0x2): balancing, usage=1 Jul 02 20:58:10 linux-1b6m btrfs-balance.sh[1888]: SYSTEM (flags 0x2): balancing, usage=1 Jul 02 20:58:10 linux-1b6m btrfs-balance.sh[1888]: Done, had to relocate 1 out of 22 chunks Jul 02 20:58:10 linux-1b6m btrfs-balance.sh[1888]: Dumping filters: flags 0x6, state 0x0, force is off Jul 02 20:58:10 linux-1b6m btrfs-balance.sh[1888]: METADATA (flags 0x2): balancing, usage=5 Jul 02 20:58:10 linux-1b6m btrfs-balance.sh[1888]: SYSTEM (flags 0x2): balancing, usage=5 Jul 02 20:58:10 linux-1b6m btrfs-balance.sh[1888]: Done, had to relocate 1 out of 22 chunks Jul 02 20:58:10 linux-1b6m btrfs-balance.sh[1888]: Dumping filters: flags 0x6, state 0x0, force is off Jul 02 20:58:10 linux-1b6m btrfs-balance.sh[1888]: METADATA (flags 0x2): balancing, usage=10 Jul 02 20:58:10 linux-1b6m btrfs-balance.sh[1888]: SYSTEM (flags 0x2): balancing, usage=10 Jul 02 20:58:10 linux-1b6m btrfs-balance.sh[1888]: Done, had to relocate 1 out of 22 chunks Jul 02 20:58:11 linux-1b6m btrfs-balance.sh[1888]: Dumping filters: flags 0x6, state 0x0, force is off Jul 02 20:58:11 linux-1b6m btrfs-balance.sh[1888]: METADATA (flags 0x2): balancing, usage=20 Jul 02 20:58:11 linux-1b6m btrfs-balance.sh[1888]: SYSTEM (flags 0x2): balancing, usage=20 Jul 02 20:58:11 linux-1b6m btrfs-balance.sh[1888]: Done, had to relocate 1 out of 22 chunks Jul 02 21:02:26 linux-1b6m btrfs-balance.sh[1888]: Dumping filters: flags 0x6, state 0x0, force is off Jul 02 21:02:26 linux-1b6m btrfs-balance.sh[1888]: METADATA (flags 0x2): balancing, usage=30 Jul 02 21:02:26 linux-1b6m btrfs-balance.sh[1888]: SYSTEM (flags 0x2): balancing, usage=30 Jul 02 21:02:26 linux-1b6m btrfs-balance.sh[1888]: Done, had to relocate 2 out of 22 chunks Jul 02 21:02:26 linux-1b6m btrfs-balance.sh[1888]: After balance of / Jul 02 21:02:26 linux-1b6m btrfs-balance.sh[1888]: Data, single: total=15.01GiB, used=12.50GiB Jul 02 21:02:26 linux-1b6m btrfs-balance.sh[1888]: System, single: total=32.00MiB, used=16.00KiB Jul 02 21:02:26 linux-1b6m btrfs-balance.sh[1888]: Metadata, single: total=1.01GiB, used=746.77MiB Jul 02 21:02:26 linux-1b6m btrfs-balance.sh[1888]: GlobalReserve, single: total=44.50MiB, used=0.00B Jul 02 21:02:26 linux-1b6m btrfs-balance.sh[1888]: Filesystem Size Used Avail Use% Mounted on Jul 02 21:02:26 linux-1b6m btrfs-balance.sh[1888]: /dev/mapper/rpool-root 33G 15G 18G 45% / regards, daniel -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1093378] conflicting udev rules completely break USB Serial bridges
by bugzilla_noreply＠novell.com 02 Jul '18

02 Jul '18

http://bugzilla.suse.com/show_bug.cgi?id=1093378 http://bugzilla.suse.com/show_bug.cgi?id=1093378#c23 --- Comment #23 from Stanislav Brabec <sbrabec(a)suse.com> --- The installer itself should run with enabled brltty. Otherwise blind people cannot install. But the installed system should have brltty as optional. The short time solution: - According to comment 12, there is anm initial probe. If it fails, brltty should avoid further handling of the device, and especially its rebind from serial to input device. My idea of perfect solution consists of: 1. Make possible to create udev rules active for one physical port only and rules active for selected amount of time (1 hour, until reboot,...) 2. Write a GUI tool that can provide feedback for indistinguishable devices, and load only correct rules. That tool will pop-up and ask user: Generic USB device was connected. Please select a device from list: Braille terminal Watts Up? Pro Wattmeter MTK GPS device SiRF Star III GPS Modem device Generic USB Serial bridge AVR programmer JETI & KLEIN Spectrophotometer Bus watching device (CEM DT-8852, Buspirate, ChronoVu LA8, ChronoVu LA16) []remember for this physical USB port []remember for this USB id []remember for [v]1 hour 3. Response from that tool will generate udev event, and rules can be based on reply. Something like that: # SiRF Star III 20ch Gmouse GPS (a.k.a Cygnal Integrated Products, Inc.) KERNEL=="ttyUSB*", ATTR{idVendor}=="10c4", ATTR{idProduct}=="ea60", NAME='SiRF Star III GPS' RUN="askuser-uncertain-usb-device" KERNEL=="ttyUSB*", ATTR{idVendor}=="10c4", ATTR{idProduct}=="ea60", USER_RESPONSE=="sirf-star-iii", RUN="gpsd.sh" Note on indistinguishable devices: For example, GPS devices using USB serial chip can be completely indistinguishable from USB serial bridge, even with serial probe. My Qstarz BT-Q1000P has a mechanical switch. In the position Off, only the bridge chip is connected, and no communication occurs. No probe can recognize that a GPS device was connected. Only after switching the mechanical switch to "Bluetooth mode" or "Logger mode" the device starts to communicate and respond to probes. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1098928] New: X11:terminals/terminator: Add plugin to make bug-tracker references clickable
by bugzilla_noreply＠novell.com 02 Jul '18

02 Jul '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1098928 Bug ID: 1098928 Summary: X11:terminals/terminator: Add plugin to make bug-tracker references clickable Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: openSUSE Factory Status: NEW Severity: Enhancement Priority: P5 - None Component: 3rd party software Assignee: tchvatal(a)suse.com Reporter: kevin.legouguec(a)gmail.com QA Contact: bnc-team-screening(a)forge.provo.novell.com CC: meissner(a)suse.com Found By: --- Blocker: --- Created attachment 775126 --> http://bugzilla.opensuse.org/attachment.cgi?id=775126&action=edit Terminator plugin to make bug tracker references clickable Hi, I wrote a simple plugin for Terminator that makes clickable links from various bug tracker references that one can find in RPM changelogs. You can try it out by - dropping the attachment in ~/.config/terminator/plugins/, - running Terminator, - checking SuseTrackersURLHandler in the Plugins tab in Preferences, - then running e.g. "rpm --query --changelog gtk3-devel". Clicking on bug tracker references should open a web browser tab and load the corresponding bug's page. For example: - "bgo#NNNN" takes you to "https://bugzilla.gnome.org/show_bug.cgi?id=NNNN", - "glgo#GNOME/GTK#NNN" takes you to "https://gitlab.gnome.org/GNOME/gtk/issues/NNNN", - "boo#NNNN" takes you to "https://bugzilla.opensuse.org/show_bug.cgi?id=NNNN", - etc. I am submitting this plugin here because I figure these abbreviations may be OpenSUSE-specific, but maybe it should be distributed and maintained by the upstream Terminator team themselves. If it indeed seems better to distribute this plugin through OpenSUSE, there is still a choice to make on where to install it: ~/.config/terminator/plugins/, or /usr/lib/python2.7/site-packages/terminatorlib/plugins/. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1092839] brltty hogs USB serial ports without obvious way to disable
by bugzilla_noreply＠novell.com 02 Jul '18

02 Jul '18

http://bugzilla.suse.com/show_bug.cgi?id=1092839 http://bugzilla.suse.com/show_bug.cgi?id=1092839#c19 --- Comment #19 from Stefan Brüns <stefan.bruens(a)rwth-aachen.de> --- (In reply to Stanislav Brabec from comment #18) > Stefan Brüns: All conflicting devices use FTDI chip as well. And vendor of > these devices were too lazy to change USB identification. So the FTDI serial > bridge is indistinguishable from a Braille terminal or Braille display on > the USB level. Only serial communication can determine the device. The conflicting devices use chips from FTDI or Silabs (Cygnal), and some of these use the generic product IDs. I am completely aware of the USB standards (having implemented several USB host and device drivers), and how udev works. Actually, I don't know what you are trying to tell me, or to which part of my comment you are referring to. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1052793] New: QT5 KDE Apps - printing silently failing
by bugzilla_noreply＠novell.com 02 Jul '18

02 Jul '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1052793 Bug ID: 1052793 Summary: QT5 KDE Apps - printing silently failing Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: x86-64 OS: openSUSE 42.3 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: ericj(a)mcalvin.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since re-installing from OpenSUSE 42.1 to 42.3, KDE (QT5) apps such as Okular, Konsole, Kate, and even assistant-qt5 are unable to print to remote printers (served via a CUPS print server). The GUI will not throw any exceptions. However, Okular will print the following to the console (if started that way): lpr: The printer or class does not exist. In another case, it printed to the first printer in the list rather than the one selected. Note that we have 149 printers defined (as shown in lpstat -t). Perhaps the long list of printers is causing some sort of overflow ? Note that other software such as firefox is printing fine from the same user session. Here is what is printed on the console with QT logging enabled: $ QT_LOGGING_RULES=org.kde.okular.core=true okular org.kde.okular.core: Executing "lpr" with arguments ("-P", "", "-#1", "-J", "Dell.pdf", "-r", "/tmp/okular_S21220.ps") lpr: The printer or class does not exist. Bug opened with KDE Okular developers. They confirmed it is an upstream bug. Bugzilla opened with KDE: https://bugs.kde.org/show_bug.cgi?id=383139 They also referenced another distro that had the same type of bug which was fixed by rebuilding cups-filters against another version of libqpdf: http://advisories.mageia.org/MGAA-2017-0055.html -- You are receiving this mail because: You are on the CC list for the bug.

1 28

[Bug 1098915] New: Intel Microcode isn't loaded during boot
by bugzilla_noreply＠novell.com 02 Jul '18

02 Jul '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1098915 Bug ID: 1098915 Summary: Intel Microcode isn't loaded during boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: tischuer(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 Build Identifier: On my system I get the following error message during boot: [Firmware Bug] TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x20 The kernel/initrd isn't loading the microcode updates for my CPU properly. I've tried to rebuild initrd with the same results. Package ucode-intel is installed. Other linux distributions are loading the microcode at bootup. My CPU is a Intel Core i7-6800K. Reproducible: Always Steps to Reproduce: 1. Install current version of Tumbleweed 2. Boot the system Actual Results: [Firmware Bug] TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x20 Expected Results: Firmeware is loaded. -- You are receiving this mail because: You are on the CC list for the bug.

1 6