March 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 768947] New: purge-kernels does not log to /var/log/zypp/history
by bugzilla_noreply＠novell.com 09 Dec '19

09 Dec '19

https://bugzilla.novell.com/show_bug.cgi?id=768947 https://bugzilla.novell.com/show_bug.cgi?id=768947#c0 Summary: purge-kernels does not log to /var/log/zypp/history Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: Other OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: mmarek(a)suse.com ReportedBy: suse-beta(a)cboltz.de QAContact: qa-bugs(a)suse.de Found By: Beta-Customer Blocker: --- purge-kernels logs to /var/log/messages - but that's a logfile nobody reads when he wants to check the package installation/removal history. /var/log/zypp/history is a much better logfile for this - purge-kernels should write it's removal log there (additional or instead of /var/log/messages). (Yes, I know that purge-kernels calls rpm directly ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2

[Bug 1085806] New: [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training
by bugzilla_noreply＠novell.com 09 Dec '19

09 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1085806 Bug ID: 1085806 Summary: [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: jnwang(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- uname -r 4.4.120-8.g7186d16-default [12134.670905] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training [12134.755941] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to start channel equalization [12134.837753] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [12135.307256] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [12197.851460] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [12198.225571] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [12213.764182] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1061213] New: php5-pear-Mail_Mime-1.10.0-1.9 provides PHP7 module
by bugzilla_noreply＠novell.com 06 Dec '19

06 Dec '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1061213 Bug ID: 1061213 Summary: php5-pear-Mail_Mime-1.10.0-1.9 provides PHP7 module Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jimc(a)math.ucla.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is for Tumbleweed as of 2017-10-01. php5-pear-Mail_Mime-1.10.0-1.9.noarch from server:php:applications delivers its payload module into /usr/share/php7/PEAR/Mail/mime.php , and of course the php5-based roundcubemail-1.2.5-2.2.noarch cannot find it. php5-pear-Mail_Mime-1.10.0-1.2.noarch from openSUSE:Factory:zSystems has /usr/share/php5/PEAR/Mail/mime.php , and works with RoundCube. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1055266] New: libssh fails to build with openssl-1.1
by bugzilla_noreply＠novell.com 05 Dec '19

05 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1055266 Bug ID: 1055266 Summary: libssh fails to build with openssl-1.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: jmcdonough(a)suse.com Reporter: vcizek(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1042629 Found By: --- Blocker: --- The package fails to build with OpenSSL 1.1. We need to migrate Factory to OpenSSL 1.1 as it would become the default on SLE-15. For more information see the blocker bug. Currently testing in staging project: https://build.opensuse.org/project/show/openSUSE:Factory:Staging:SSL11 Fails with: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 985557] New: KDE:Applications/dolphin: Bug
by bugzilla_noreply＠novell.com 05 Dec '19

05 Dec '19

http://bugzilla.opensuse.org/show_bug.cgi?id=985557 Bug ID: 985557 Summary: KDE:Applications/dolphin: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: tittiatcoke(a)gmail.com Reporter: w.pelser(a)web.de QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Before QT5 I could always see in the headline of dolphin, whether it was opened as SU or as a normal user. (So I think this as a regression.) Actually it is only mentioned there, when dolphin is started as SU. After opening a new file the headline is the same as a normal user. If during compilation I have opened both kinds of dolphin side by side, I need to see a obviously difference between the two windows. There are some kinds of workaround to find out the difference, but they are annoying. I tried to make two screen-shots, but the difference is hardly to be seen, because if I make a screen-shot, dolphin is not the inactive window. But this could be reproduced very easy by everyone. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 976985] New: tcl plugin for firefox throws error "undefined symbol: Tcl_Init"
by bugzilla_noreply＠novell.com 05 Dec '19

05 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=976985 Bug ID: 976985 Summary: tcl plugin for firefox throws error "undefined symbol: Tcl_Init" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: hguo(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a freshly installed tumbleweed snapshot 20160417. When starting firefox while tclplug is installed, an error is printed in the firefox output: LoadPlugin: failed to initialize shared library /usr/lib64/browser-plugins/libnptcl3.1.so [/usr/lib64/browser-plugins/libnptcl3.1.so: undefined symbol: Tcl_Init] Hence the plugin is not usable. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1047897] New: conflict in cups debuginfo
by bugzilla_noreply＠novell.com 05 Dec '19

05 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1047897 Bug ID: 1047897 Summary: conflict in cups debuginfo Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing Assignee: jsmeix(a)suse.com Reporter: ohering(a)suse.com QA Contact: jsmeix(a)suse.com Found By: --- Blocker: --- openSUSE Tumbleweed 20170524-0 -> 20170708-0 File /usr/lib/debug/usr/lib/cups/filter/foomatic-rip.debug from install of cups-filters-debuginfo-1.14.0-1.1.x86_64 (debug) conflicts with file from package cups-filters-foomatic-rip-debuginfo-1.13.3-2.2.x86_64 (@System) File /usr/lib/debug/usr/lib/cups/filter/gstoraster.debug from install of cups-filters-debuginfo-1.14.0-1.1.x86_64 (debug) conflicts with file from package cups-filters-ghostscript-debuginfo-1.13.3-2.2.x86_64 (@System) File /usr/lib/debug/usr/lib64/libcupsfilters.so.1.0.0.debug from install of cups-filters-debuginfo-1.14.0-1.1.x86_64 (debug) conflicts with file from package cups-filters-ghostscript-debuginfo-1.13.3-2.2.x86_64 (@System) File /usr/lib/debug/usr/sbin/cups-browsed.debug from install of cups-filters-debuginfo-1.14.0-1.1.x86_64 (debug) conflicts with file from package cups-filters-cups-browsed-debuginfo-1.13.3-2.2.x86_64 (@System) -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1057979] New: ghostscript defining default papersize
by bugzilla_noreply＠novell.com 05 Dec '19

05 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1057979 Bug ID: 1057979 Summary: ghostscript defining default papersize Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Ralf.Friedl(a)online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Ghostscript PAPERSIZE defaults to letter, which is unfortunate if you want to use A4. According to the Ghostscript documentation at https://ghostscript.com/doc/7.07/Use.htm#Change_default_size this can be changed by editing the initialization file gs_init.ps, located in the Resource/Init directory. Editing a file that will be replaced with the next update would not be good, but there is another problem, there is no file gs_init.ps to edit. Also according to https://www.ghostscript.com/doc/current/Use.htm#Finding_files if built with COMPILE_INITS=1 (currently the default build) the files in the Resource directory are built into the executable. So how to change the default paper size, preferably in a way that will survive the next update? It should be possible to change the file gs_init.ps before building Ghostscript so that it would read something like /etc/sysconfig/ghostscript. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1072657] New: tcl make check transient failures
by bugzilla_noreply＠novell.com 04 Dec '19

04 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1072657 Bug ID: 1072657 Summary: tcl make check transient failures Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: normand(a)linux.vnet.ibm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 752840 --> http://bugzilla.suse.com/attachment.cgi?id=752840&action=edit tcl_ring0_tw_ppc64le.log tcl make check transient failures last one reported in https://build.opensuse.org/package/show/openSUSE:Factory:PowerPC:Rings:0-Bo… there were 3 failing tests: === [ 319s] ==== chan-io-53.9 CopyData: -size and event interaction, Bug 780533 FAILED [ 357s] ==== event-12.4 Tcl_UpdateCmd procedure FAILED [ 801s] ==== timer-2.1 Tcl_DeleteTimerHandler procedure FAILED === $osc jobhist -l10 openSUSE:Factory:PowerPC:Rings:0-Bootstrap/tcl standard ppc64le time package reason code build time worker 2017-11-30 18:48:43 tcl new build succeeded 11m 45s obs-power8-05:10 2017-11-30 23:54:19 tcl meta change failed 14m 53s obs-power8-02:7 2017-12-01 12:55:07 tcl new build succeeded 12m 54s obs-power8-05:3 2017-12-01 15:19:25 tcl meta change succeeded 9m 33s obs-power8-04:15 2017-12-06 12:01:48 tcl meta change failed 11m 37s obs-power8-03:18 2017-12-13 00:14:48 tcl meta change failed 14m 15s obs-power8-03:7 === -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1079905] New: py2pack advertises obsolete upstream URL
by bugzilla_noreply＠novell.com 04 Dec '19

04 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1079905 Bug ID: 1079905 Summary: py2pack advertises obsolete upstream URL Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: x86-64 OS: openSUSE 42.3 Status: NEW Severity: Minor Priority: P5 - None Component: Documentation Assignee: fs(a)suse.com Reporter: giecrilj(a)stegny.2a.pl QA Contact: fs(a)suse.com Found By: --- Blocker: --- Reading <URL: file:///usr/share/doc/packages/python-py2pack//README.rst >: :target: https://travis-ci.org/saschpe/py2pack Travis CI: We couldn't find the repository saschpe/py2pack -- You are receiving this mail because: You are on the CC list for the bug.

1 4