October 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 922992] New: Enable GNU Terry Pratchett in default Apache configuration
by bugzilla_noreply＠novell.com 03 Aug '21

03 Aug '21

http://bugzilla.suse.com/show_bug.cgi?id=922992 Bug ID: 922992 Summary: Enable GNU Terry Pratchett in default Apache configuration Classification: openSUSE Product: openSUSE Factory Version: 201502* Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: lmb(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- As per http://www.gnuterrypratchett.com/#apache, I suggest to enable this in the default apache configuration on openSUSE. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 955233] New: Software Updates applet shows "Network is offline"
by bugzilla_noreply＠novell.com 25 Jul '21

25 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=955233 Bug ID: 955233 Summary: Software Updates applet shows "Network is offline" Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: madakis1988(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The applet occasionally shows that the "Network is offline" even though there's an active connection to the internet. There's no other connection enabled. This results in inability to check for updates. It usually goes back to normal after a reboot. YaST -> Online Update works fine every time. -- You are receiving this mail because: You are on the CC list for the bug.

2 14

[Bug 940851] New: kye-data contains works with non-OSI license
by bugzilla_noreply＠novell.com 03 Jul '21

03 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=940851 Bug ID: 940851 Summary: kye-data contains works with non-OSI license Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: All OS: All Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de CC: cfarrell(a)suse.com, dimstar(a)opensuse.org, nemysis(a)gmx.ch Found By: --- Blocker: --- openSUSE:Factory/kye-data has Training.zip, whose txt file reads: 1. This is freeware so you can use it yourself or let others try it but I don't want you SELLING IT!!! TTBOMK, this incompatible with OSI-compatible licensing. Most of the other works (shipped in .zip files) have no license notice, however small, at all. vexkyelevels.zip does not appear to permit "use" (merely copying, distribution and modification). -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 977967] New: global package's gtag command cannot work with the option '--gtagslabel=pygments'
by bugzilla_noreply＠novell.com 30 Jun '21

30 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=977967 Bug ID: 977967 Summary: global package's gtag command cannot work with the option '--gtagslabel=pygments' Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Minor Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: goto.inct(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.75 Safari/537.36 Build Identifier: I installed 'global' package using zypper and typed 'gtags --gtagslabel=pygments' in the terminal, then I get following warning. gtags: cannot open shared object '/usr/lib/gtags/pygments-parser.la'. Of course, gtags does not work correctly. Reproducible: Always Steps to Reproduce: 1. Install global (# zypper install global) 2. Use gtags (> gtags --gtagslabel-pygments) Actual Results: gtags: cannot open shared object '/usr/lib/gtags/pygments-parser.la'. Expected Results: Get GPATH, GRTAGS, GTAGS file into current directory without warning. Solution: This bug caused by inconsistence between /etc/gtags.conf and the path of 'pygments-parser.la'. 'gtags.conf' assume that 'pygments-parser.la' is in '/usr/lib/gtags/'. But actually, 'pygments-parser.la' is located in '/usr/lib64/gtags/'. Therefore we can fix this problem following commands: 'sudo sed -i -e "s/lib/lib64/g" /etc/gtags.conf'. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 997368] New: Application:Geo/qgis: Bug qgis-master-160801-1.6 breaks compatibility with some plugins
by bugzilla_noreply＠novell.com 01 Jun '21

01 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=997368 Bug ID: 997368 Summary: Application:Geo/qgis: Bug qgis-master-160801-1.6 breaks compatibility with some plugins Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: dassau(a)gbd-consult.de Reporter: dmitri.chubarov(a)gmail.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: opensuse(a)dstoecker.de, tzotsos(a)gmail.com Found By: --- Blocker: --- Created attachment 690938 --> http://bugzilla.opensuse.org/attachment.cgi?id=690938&action=edit a patch for the Python files A recent change to QGIS Python interface "Rename QGis class to Qgis, for capitalisation consistency" commited on July 21, 2016 (https://github.com/qgis/QGIS/commit/1a2231f10c65c2bef992e02046baebf3bc4975f6) breaks some plugins that depend on qgis.core API. For instance, the latest OpenLayers plugin version 1.4.1 fails to install with the message "The plugin is broken. Python said: cannot import name QGis". This happens because QGis class was renamed to Qgis. A temporary solution for an end-user would be to install the plugin, ignore the error message and replace all occurrences of QGis to Qgis in the files $HOME/.qgis-dev/python/plugins/openlayers_plugin/openlayers_plugin.py (6 occurrences) $HOME/.qgis-dev/python/plugins/openlayers_plugin/openlayers_layer.py (1 occurrence) $HOME/.qgis-dev/python/plugins/openlayers_plugin/weblayers/weblayer.py (2 occurrences) There are 9 occurrences altogether. A solution for plugin developers would be to catch ImportError on from qgis.core import QGis and import the class by its new name. It is not clear what would be a good solution for packagers. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 905418] New: No audio/no sound when headphone is plugged in -- choosing "Headphones (unplugged)" in pavucontrol then works
by bugzilla_noreply＠novell.com 28 May '21

28 May '21

http://bugzilla.suse.com/show_bug.cgi?id=905418 Bug ID: 905418 Summary: No audio/no sound when headphone is plugged in -- choosing "Headphones (unplugged)" in pavucontrol then works Classification: openSUSE Product: openSUSE Factory Version: 201411* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: gp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 613619 --> http://bugzilla.suse.com/attachment.cgi?id=613619&action=edit Screenshot showing pavucontrol vs GNOME Sound panel when external jack is unplugged This is an interesting one, current Factory with kernel 3.16.4-1.g7a8842b-default (and before that also with kernel-default-3.17.1-1.2.g5c4d099 I believe). Sounds on this Lenovo T430s notebook works just fine. Except when I plug in speakers or a headset, instead of switching off the internal speakers and activating that external audio -- silence. The GNOME Sound panel provides no way to address this. pavucontrol, however shows "Headphones (unplugged)", and when I select that as Output Device, everything works as it used to (with 13.1, 13.2 and Factory until a few days ago). 14: PCI 1b.0: 0403 Audio device [Created at pci.328] Unique ID: u1Nb.0TDI6CRLz81 SysFS ID: /devices/pci0000:00/0000:00:1b.0 SysFS BusID: 0000:00:1b.0 Hardware Class: sound Model: "Intel 7 Series/C210 Series Chipset Family High Definition Audio Controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x1e20 "7 Series/C210 Series Chipset Family High Definition Audio Controller" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x21fb Revision: 0x04 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xf2530000-0xf2533fff (rw,non-prefetchable) IRQ: 46 (1867 events) Module Alias: "pci:v00008086d00001E20sv000017AAsd000021FBbc04sc03i00" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=yes, avail=yes, need=no, active=unknown -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 921577] New: doxygen build failure for Power8 because double free or corruption
by bugzilla_noreply＠novell.com 21 May '21

21 May '21

http://bugzilla.suse.com/show_bug.cgi?id=921577 Bug ID: 921577 Summary: doxygen build failure for Power8 because double free or corruption Classification: openSUSE Product: openSUSE Factory Version: 201502* Hardware: PowerPC-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem 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: --- doxygen build failure for Power8 because double free or corruption === ... [ 241s] Generating docs for compound B/home/abuild/rpmbuild/BUILD/doxygen-1.8.9.1/vhdlparser/TokenManager.h:19: warning: Unsupported xml/html tag <EOF> found [ 248s] *** Error in `./bin/doxygen': double free or corruption (fasttop): 0x000001001077bcf0 *** [ 248s] ======= Backtrace: ========= [ 248s] /lib64/libc.so.6(+0x836c0)[0x3fffa7ec36c0] [ 248s] /lib64/libc.so.6(+0x8ba84)[0x3fffa7ecba84] [ 248s] /lib64/libc.so.6(+0x8cadc)[0x3fffa7eccadc] [ 248s] /lib64/libc.so.6(cfree+0xd0)[0x3fffa7ed0a30] [ 248s] /usr/lib64/libstdc++.so.6(_ZdlPv+0x20)[0x3fffa819ce10] [ 248s] ./bin/doxygen[0x106620e4] [ 248s] ./bin/doxygen[0x1053ba84] [ 248s] ./bin/doxygen[0x1053bb18] [ 248s] ./bin/doxygen[0x106a0a44] [ 248s] /lib64/libpthread.so.0(+0x9454)[0x3fffa8299454] [ 248s] /lib64/libc.so.6(clone+0xe4)[0x3fffa7f4e0c4] ... === detailed log in doxygen_opensuse_ppc64le_failure.log attachment -- You are receiving this mail because: You are on the CC list for the bug.

2 42

[Bug 1003362] New: server:monitoring/nagios: Bug
by bugzilla_noreply＠novell.com 11 May '21

11 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1003362 Bug ID: 1003362 Summary: server:monitoring/nagios: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: lars.vogdt(a)suse.com Reporter: ian.mcconnell(a)denbridgemarine.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: nix(a)opensuse.org Found By: --- Blocker: --- Created attachment 696185 --> http://bugzilla.opensuse.org/attachment.cgi?id=696185&action=edit Fix permissions on command files. nagios creates the following files with the wrong permissions: # ls -l /var/spool/nagios/ srw-rw---- 1 nagios nagios 0 Oct 6 13:47 live prw-rw---- 1 nagios nagios 0 Oct 6 13:47 nagios.cmd For nagvis to access them, they need to be in group "nagcmd" srw-rw---- 1 nagios nagcmd 0 Oct 6 13:47 live prw-rw---- 1 nagios nagcmd 0 Oct 6 13:47 nagios.cmd Since "nagios.cmd" is a named pipe, the permission can be changed once to correct it, but "live" needs changing each time "nagios" is run. The following lines in /etc/nagios/nagios.cfg set these files: command_file=/var/spool/nagios/nagios.cmd broker_module=/usr/lib/check_mk/livestatus-nagios4.o /var/spool/nagios/live I noticed that the file "/usr/lib/nagios/nagios-exec-start-pre" tried to set these permissions by setting the variable nagios_cmdgrp. nagios_cmdgrp="$(get_var nagios_cmdgrp)" but nagois_cmdgrp isn't in /etc/nagios/nagios.cfg. It can't be added as nagios complains about an unknown definition and won't start. Also the line : ${nagios_cmdgrp:-nagcmd} doesn't seem to work for me when /bin/sh is linked to bash /bin/sh --version GNU bash, version 4.2.47(1)-release (x86_64-suse-linux-gnu) nagios_cmdgrp="" echo $nagios_cmdgrp : ${nagios_cmdgrp:-nagcmd} echo $nagios_cmdgrp : ${nagios_cmdgrp:=nagcmd} echo $nagios_cmdgrp nagcmd nagios_cmdgrp="xxxx" : ${nagios_cmdgrp:=nagcmd} echo $nagios_cmdgrp xxxx Unfortunately changing : ${nagios_cmdgrp:-nagcmd} to : ${nagios_cmdgrp:=nagcmd} doesn't fix the permissions on the command files # ls -l /var/spool/nagios/ srw-rw---- 1 nagios nagios 0 Oct 6 14:16 live prw-rw---- 1 nagios nagios 0 Oct 6 14:16 nagios.cmd as these are created after the process "nagios" starts. A workaround is to add the line ExecStartPost=/usr/lib/nagios/nagios-exec-start-post to nagios.service. I have attached the nagios-exec-start-post script. This works with # systemctl start nagios.service # systemctl restart nagios.service but for # systemctl reload nagios.service I get the wrong permissions: # ls -l /var/spool/nagios/ srw-rw---- 1 nagios nagios 0 Oct 6 14:23 live prw-rw---- 1 nagios nagcmd 0 Oct 6 14:16 nagios.cmd These are the nagios packages I installed: nagios-4.2.1-1.1.x86_64 nagios-www-4.2.1-1.1.x86_64 nagios-www-dch-4.2.1-1.1.x86_64 pnp4nagios-0.6.25-6.24.x86_64 pnp4nagios-nagios-0.6.25-6.24.x86_64 nagvis-1.8.5-3.1.noarch mk-livestatus-1.2.8p11-3.2.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 986593] New: security/john: Tools in run/ not packaged and undefined maintainer of john
by bugzilla_noreply＠novell.com 25 Apr '21

25 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=986593 Bug ID: 986593 Summary: security/john: Tools in run/ not packaged and undefined maintainer of john Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: opensuse-communityscreening(a)forge.provo.novell.com Reporter: sebix+novell.com(a)sebix.at QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: meissner(a)suse.com Found By: --- Blocker: --- The tools which are in run/ in the jumbo-repository[2] are not packaged. The tools like pdf2john.py (and other *2john programs) are very helpful (or essential) to work with john. Beside packing them into the john-package, another possibility would be to create a john-tools package. Which variant do you prefer? (I can help with packaging in July) And: The mentioned maintainer-email on OBS (solar(a)false.com) is not reachable (no MX or A record for that domain. And: By clicking "report bug" on https://build.opensuse.org/package/show/security/john "lars.vogdt(a)microfocus.dmm" was assigned, but bugzilla did not accept this input. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 927268] New: clang link fails with undefined reference to `__stack_chk_guard'
by bugzilla_noreply＠novell.com 18 Apr '21

18 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=927268 Bug ID: 927268 Summary: clang link fails with undefined reference to `__stack_chk_guard' Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: PowerPC-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dap(a)open.by QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 631137 --> http://bugzilla.opensuse.org/attachment.cgi?id=631137&action=edit Full build log. Upstream report: https://llvm.org/bugs/show_bug.cgi?id=22248 My build log error: [ 35s] CMakeFiles/huffar.dir/compress.c.o:(.toc+0x0): undefined reference to `__stack_chk_guard' [ 35s] CMakeFiles/huffar.dir/extract.c.o:(.toc+0x0): undefined reference to `__stack_chk_guard' [ 35s] clang-3.5: error: linker command failed with exit code 1 (use -v to see invocation) [ 35s] CMakeFiles/huffar.dir/build.make:163: recipe for target 'huffar' failed [ 35s] make[2]: *** [huffar] Error 1 Check attachment for full log. #opensuse-ppc(a)irc.freenode.net: k0da: dark_ss, it seems you've hit an LLVM bug. It adds extra symbol. k0da: dark_ss, you can open an opensuse bug though for that issue. -- You are receiving this mail because: You are on the CC list for the bug.

2 5