openSUSE Bugs September 2018

bugs@lists.opensuse.org

1 participants
3165 discussions

[Bug 1063638] New: 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

http://bugzilla.opensuse.org/show_bug.cgi?id=1063638 Bug ID: 1063638 Summary: btrfs balance renders system unresponsive and eventually even kills WiFi when quota is enabled - review I/O scheduling parameters of btrfsmaintenance Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de CC: Antoine.Saroufim(a)gmail.com, aschnell(a)suse.com, auxsvr(a)gmail.com, dmitry(a)roshchin.org, dsterba(a)suse.com, ecsos(a)schirra.net, enadolski(a)suse.com, fcrozat(a)suse.com, fliu(a)suse.com, friedhelm.stappert(a)web.de, guenther(a)mpanrw.de, gweberbh(a)gmail.com, hannsj_uhl(a)de.ibm.com, harald.achitz(a)gmail.com, ingo.goeppert+suse(a)mailbox.org, jeffm(a)suse.com, kdejaeger(a)gmail.com, lnussel(a)suse.com, lpechacek(a)suse.com, ndcunliffe(a)gmail.com, okurz(a)suse.com, ortsacs(a)yahoo.es, rgoldwyn(a)suse.com, richard(a)nod.at, ronisbr(a)gmail.com, slindomansilla(a)suse.com, suse(a)bugs.jan.ritzerfeld.org, sven.heithecker(a)web.de, t.rother(a)netzwissen.de, tneo(a)gmx.com, ulrich.hobelmann+suse(a)gmail.com Depends on: 1017461 Found By: --- Blocker: --- ## Observation +++ This bug was initially created as a clone of Bug #1017461 +++ The first part of fixes have been done in bug 1017461 but it seems the btrfs maintenance tasks can still have a significant impact on system responsiveness. Running the btrfs maintenance jobs, e.g. * /etc/cron.monthly/btrfs-scrub * /etc/cron.weekly/btrfs-balance * /etc/cron.weekly/btrfs-trim can make the clock with seconds displayed stop for some seconds or the mouse cursor to get stuck for seconds ## Reproducible * Somehow cause lot of "dirty" data that needs balancing/scrubbing * Run the cron jobs * Observe the system responsiveness is hindered ## Expected result Interactive use of a machine should not be impacted ## Suggestion It looks like /usr/share/btrfsmaintenance/btrfs-scrub.sh checks for the variable "$BTRFS_SCRUB_PRIORITY" equalling "normal" from /etc/sysconfig/btrfsmaintenance but this is set to "idle" for me in the config file which causes that no I/O scheduling parameters are forwarded to the call of scrub at all which does not seem to make sense to me. Should it set `-c 3` for idle or `-c 2 -n 7` for best-effort prio 7 instead? -- You are receiving this mail because: You are on the CC list for the bug.

3 weeks, 2 days

[Bug 1079393] New: libyui-ncurses contains file in conflict with shared library packaging policy

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1079393 Bug ID: 1079393 Summary: libyui-ncurses contains file in conflict with shared library packaging policy Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other URL: https://openqa.opensuse.org/tests/601880/modules/zdup/ steps/254 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: lnussel(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-15.0-DVD-x86_64-zdup-Leap-42.2-gnome@64bit fails in [zdup](https://openqa.opensuse.org/tests/601880/modules/zdup/steps/254) Independent of why this failure happens during zypper dup, the libyui-ncurses* package does not follow the shared library packaging policy. /usr/bin/libyui-terminal must not be in the shared library package as it prevents parallel installations with older versions obviously. -- You are receiving this mail because: You are on the CC list for the bug.

3 weeks, 2 days

[Bug 1047218] New: trackerbug: packages do not build reproducibly from including build time

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1047218 Bug ID: 1047218 Summary: trackerbug: packages do not build reproducibly from including build time Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: SUSE Other Status: CONFIRMED Severity: Normal Priority: P5 - None Component: Development Assignee: bwiedemann(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Development Blocker: --- See also https://reproducible-builds.org/ and https://reproducible-builds.org/specs/source-date-epoch/ When packages include the current time of build it results in binaries that differ on every build and thus trigger rebuilds of depending packages and are published to mirrors and users when actually nothing really changed. -- You are receiving this mail because: You are on the CC list for the bug.

3 weeks, 4 days

[Bug 1081754] New: trackerbug: packages do not build reproducibly

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1081754 Bug ID: 1081754 Summary: trackerbug: packages do not build reproducibly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: CONFIRMED Severity: Normal Priority: P5 - None Component: Development Assignee: bwiedemann(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Depends on: 1040589, 1041090, 1047218, 1061219, 1062303 Found By: Development Blocker: --- This bug is a meta entry to collect bugs about packages that produce different results on every build and thus waste OBS build power for rebuilding depending packages and waste network bandwidth to sync results to mirrors and users. See also https://reproducible-builds.org/ for other reasons -- You are receiving this mail because: You are on the CC list for the bug.

3 weeks, 5 days

[Bug 1102408] New: trackerbug: packages do not build reproducibly from race conditions

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1102408 Bug ID: 1102408 Summary: trackerbug: packages do not build reproducibly from race conditions Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: CONFIRMED Severity: Normal Priority: P5 - None Component: Development Assignee: bwiedemann(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Depends on: 1021335, 1021353 Blocks: 1081754 Found By: Development Blocker: --- See also https://reproducible-builds.org/ and https://github.com/bmwiedemann/theunreproduciblepackage/tree/master/race When packages build with make -j$N (N>1), it sometimes results in binaries that differ between builds and thus trigger rebuilds of depending packages and are published to mirrors and users when actually nothing really changed. Build results can also be incorrect due to races. Often it is possible to fix races by adding proper dependencies between build targets (e.g. https://bugzilla.sudo.ws/show_bug.cgi?id=842 ) or fixing involved racy tools -- You are receiving this mail because: You are on the CC list for the bug.

4 weeks

[Bug 1033081] New: fetchmail hardcoded to use log file - syslogging thus unavailable

by bugzilla_noreply＠novell.com

http://bugzilla.suse.com/show_bug.cgi?id=1033081 Bug ID: 1033081 Summary: fetchmail hardcoded to use log file - syslogging thus unavailable Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jmozdzen(a)nde.ag QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- :~ # rpm -qi fetchmail Name : fetchmail Version : 6.3.26 Release : 18.1 Architecture: x86_64 Looking at fetchmail.service -> /usr/lib/fetchmail-systemd-exec, I see that using logging to log file is hard-coded there: --- cut here: /usr/lib/fetchmail-systemd-exec --- [...] exec /usr/bin/fetchmail $OPTS $FETCHMAIL_EXPERT_OPTIONS \ -f $FETCHMAIL_RC_PATH -L /var/log/fetchmail --- cut here --- Hence, activating logging to syslog via options doesn't work: --- cut here --- :~ # grep syslog /etc/fetchmailrc set syslog :~ # systemctl restart fetchmail :~ # 2017-04-09T17:36:13.480966+02:00 myhost fetchmail[4441]: syslog and logfile options are both set, ignoring syslog, and logging to /var/log/fetchmail --- cut here --- A possible change would be to move "-L /var/log/fetchmail" to /etc/sysconfig/fetchmail (i.e. to FETCHMAIL_EXPERT_OPTIONS variable, or a new one). -- You are receiving this mail because: You are on the CC list for the bug.

1 month

[Bug 927832] New: libreoffice does not discover printers in client only mdns setup

by bugzilla_noreply＠novell.com

http://bugzilla.suse.com/show_bug.cgi?id=927832 Bug ID: 927832 Summary: libreoffice does not discover printers in client only mdns setup Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: LibreOffice Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- libreoffice only offers "Generic Printer" when run without cupsd. Printers can be discovered nevertheless using mdns and e.g. evince works fine. LO probably needs to be compiled to use the new cups 1.6 APIs: http://www.cups.org/documentation.php/doc-2.0/api-cups.html#cupsEnumDests -- You are receiving this mail because: You are on the CC list for the bug.

1 month

[Bug 1052150] New: ASIX ax88179 USB ethernet disconnects with error

by bugzilla_noreply＠novell.com

http://bugzilla.suse.com/show_bug.cgi?id=1052150 Bug ID: 1052150 Summary: ASIX ax88179 USB ethernet disconnects with error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: tonyj(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 735177 --> http://bugzilla.suse.com/attachment.cgi?id=735177&action=edit supportconfig Anker USB 3.0 ethernet adapter randomly disconnects. Seems a known issue but I don't see any fixes: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1333003 https://bugzilla.redhat.com/show_bug.cgi?id=1238617 link comes up after inserting adapter into USB3 port, generate some minor traffic (nature of traffic not relevant, ftp/scp/ssh all reproduce) and link drops. amount of time it takes varies. supposedly doesn't occur on USB2 but I've not tried this. latest 4.11.8-2-default kernel but it's been broken for a fair while. Hardware in question is a Macbook Pro (USB3) but I don't think it is on above redhat/ubuntu bugs. dmesg below, support config attached [11493.769864] usb 4-1: new SuperSpeed USB device number 3 using xhci_hcd [11493.796691] usb 4-1: New USB device found, idVendor=0b95, idProduct=1790 [11493.796696] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [11493.796699] usb 4-1: Product: AX88179 [11493.796701] usb 4-1: Manufacturer: ASIX Elec. Corp. [11493.796703] usb 4-1: SerialNumber: 0000000000015E [11494.131928] ax88179_178a 4-1:1.0 eth0: register 'ax88179_178a' at usb-0000:00:14.0-1, ASIX AX88179 USB 3.0 Gigabit Ethernet, 00:00:0d:00:ee:30 [11494.153818] ax88179_178a 4-1:1.0 enp0s20u1: renamed from eth0 [11494.204082] IPv6: ADDRCONF(NETDEV_UP): enp0s20u1: link is not ready [11494.529718] IPv6: ADDRCONF(NETDEV_UP): enp0s20u1: link is not ready [11497.127891] ax88179_178a 4-1:1.0 enp0s20u1: ax88179 - Link status is: 1 [11497.133370] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s20u1: link becomes ready [12021.041777] xhci_hcd 0000:00:14.0: Cannot set link state. [12021.041788] usb usb4-port1: cannot disable (err = -32) [12021.041793] usb 4-1: USB disconnect, device number 3 [12021.042026] ax88179_178a 4-1:1.0 enp0s20u1: unregister 'ax88179_178a' usb-0000:00:14.0-1, ASIX AX88179 USB 3.0 Gigabit Ethernet [12021.042053] ax88179_178a 4-1:1.0 enp0s20u1: Failed to read reg index 0x0002: -19 [12021.042056] ax88179_178a 4-1:1.0 enp0s20u1: Failed to write reg index 0x0002: -19 [12021.061697] ax88179_178a 4-1:1.0 enp0s20u1 (unregistered): Failed to write reg index 0x0002: -19 [12021.061699] ax88179_178a 4-1:1.0 enp0s20u1 (unregistered): Failed to write reg index 0x0001: -19 [12021.061700] ax88179_178a 4-1:1.0 enp0s20u1 (unregistered): Failed to write reg index 0x0002: -19 -- You are receiving this mail because: You are on the CC list for the bug.

1 month, 1 week

[Bug 973590] New: weird layout of bootloader screen

by bugzilla_noreply＠novell.com

http://bugzilla.suse.com/show_bug.cgi?id=973590 Bug ID: 973590 Summary: weird layout of bootloader screen Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: dmueller(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- While updating the openQA needle for openSUSE on AArch64 people noted that the "indentation" of the items in the ncurses ui looks slightly awkward. Is it intended that there is this huge empty space at the top left corner? -- You are receiving this mail because: You are on the CC list for the bug.

1 month, 1 week

[Bug 1041742] New: Filetriggers do not fire (reliably)

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1041742 Bug ID: 1041742 Summary: Filetriggers do not fire (reliably) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In GNOME:Next, we started experimenting with file triggers (with the goal to lower the number of bugs based on missing post scripts) As a sample, I implemented this trigger (on glib2-tools): %transfiletriggerin -n glib2-tools -- %{_datadir}/glib-2.0/schemas %{_bindir}/glib-compile-schemas %{_datadir}/glib-2.0/schemas %transfiletriggerpostun -n glib2-tools -- %{_datadir}/glib-2.0/schemas %{_bindir}/glib-compile-schemas %{_datadir}/glib-2.0/schemas The trigger is confirmed to work, but in some cases, it seems not to fire, eg on the package 'gdm' (which is currently the reason why http://download.opensuse.org/repositories/GNOME:/Medias/images/iso/?P=GNOME… fails to boot to desktop) zypper in --no-recommends gdm => the file trigger is not executed rpm -i gdm-3.24.1.rpm => the trigger actually seems to work (which is why I file it against libzypp) This currently stops us from moving forward and proposing file triggers to be more widely used (even though I think they can solve quite some packaging bugs) The packages in question for testing are all in the GNOME:Next repository (glib2 which has the trigger, it has the %glib2_gsettings_schema_post set to %nil, so packages that use it in their post script only get a dummy - once the implementation is complete, we will of course go and clean those out completely) -- You are receiving this mail because: You are on the CC list for the bug.

1 month, 1 week

← Newer
1
2
3
4
5
6
7
...
317
Older →

Jump to page:

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs September 2018