March 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 956357] New: Inconsistent fonts between Qt4 and GTK/Qt5 apps when using Roboto
by bugzilla_noreply＠novell.com 13 Jul '18

13 Jul '18

http://bugzilla.suse.com/show_bug.cgi?id=956357 Bug ID: 956357 Summary: Inconsistent fonts between Qt4 and GTK/Qt5 apps when using Roboto Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ronisbr(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 657030 --> http://bugzilla.suse.com/attachment.cgi?id=657030&action=edit qtconfig showing that Roboto Black is selected. Hi! I'm using openSUSE Tumbleweed with MATE 1.12 desktop and Qt theme is set to GTK+. After last snapshot, I switched the default font to Google's Roboto using `mate-appearance-properties`. I also changed it in KDE `systemsettings5`. However, I noticed that all Qt4 apps was showing a darker font. Then, when I tried to configure using `qtconfig`, it shows that the selected font was Roboto Black instead of Roboto Regular. I tried many things, but as far as GTK+ theme is selected, I could not change the font in `qtconfig` to Roboto Regular, which seems to be causing the problem. I'm uploading three figures: 1) The qtconfig showing that Roboto Black font is selected; 2) A screenshot of kwrite, showing the correct font (Roboto Regular); 3) A screenshot of digikam, showing the wrong font (Roboto Black). Here is additional information about my system: $cat /etc/os-release NAME=openSUSE VERSION="Tumbleweed" VERSION_ID="20151118" PRETTY_NAME="openSUSE Tumbleweed (20151118) (x86_64)" ID=opensuse ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:opensuse:20151118" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://opensuse.org/" ID_LIKE="suse" -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 953012] New: Unable (or at least wasn't shown) to do "just" remove a package with zypper
by bugzilla_noreply＠novell.com 05 Jul '18

05 Jul '18

http://bugzilla.opensuse.org/show_bug.cgi?id=953012 Bug ID: 953012 Summary: Unable (or at least wasn't shown) to do "just" remove a package with zypper Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: trifanstanislav(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/46.0.2490.71 Safari/537.36 Build Identifier: I try to remove firefox package. But zypper try to install another one, but I don't want it, and there is no option for skipping new install. Reproducible: Always Steps to Reproduce: $> sudo zypper remove firefox Actual Results: root's password: Loading repository data... Reading installed packages... 'firefox' not found in package names. Trying capabilities. Resolving package dependencies... The following NEW package is going to be installed: MozillaThunderbird The following application is going to be REMOVED: Firefox The following package is going to be REMOVED: MozillaFirefox 1 new package to install, 1 to remove. Overall download size: 33.1 MiB. Already cached: 0 B After the operation, 5.9 MiB will be freed. Continue? [y/n/p/? shows all options] (y): Expected Results: Add in the line: `Continue? [y/n/p/? shows all options] (y):` an option for remove only. It may be used `ro` option for remove only, and there should be information what it means. This actually is an usability bug. You may found tricks over the web that people do for that. That's totally not good and makes SUSE to loose points in usability versus other OSes. BTW: is not meaningful to use `p` for restart whatever it is. It make sense to put option with 2 or 3 chars that will make action intuitive to remember and use. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 899627] New: p7zip package is missing 7zr executable
by bugzilla_noreply＠novell.com 03 Jul '18

03 Jul '18

http://bugzilla.opensuse.org/show_bug.cgi?id=899627 Bug ID: 899627 Summary: p7zip package is missing 7zr executable Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: me(a)shadsterling.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- /usr/bin/7zr, the "stand-alone" program that only handles the 7-zip format is missing from the p7zip package. /usr/bin/7z and /usr/bin/7za are included, as are man pages are for 7z, 7za, and 7zr. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 964353] New: QT 5.5.based plasmashell and sddm-greeter can't cope with no monitor or monitor powered down
by bugzilla_noreply＠novell.com 22 Jun '18

22 Jun '18

http://bugzilla.opensuse.org/show_bug.cgi?id=964353 Bug ID: 964353 Summary: QT 5.5.based plasmashell and sddm-greeter can't cope with no monitor or monitor powered down Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: lorenzodes(a)fastwebnet.it QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Plasmashell crashes or displays malfunctions if a monitor is unplugged or powered off. The problem is reported here: https://forums.opensuse.org/showthread.php/512997-Plasma-5-KDE-Switching-mo… To reproduce: xrandr --output DP3 --off ; xrandr --output DP3 --auto (change DP3 to the pertinent display name) This is the crash report: (gdb) bt #0 0x00007f7d08147ded in nanosleep () at /lib64/libc.so.6 #1 0x00007f7d08147c84 in sleep () at /lib64/libc.so.6 #2 0x00007f7d0e89bbac in startProcessInternal(int, char const**, bool, bool) (argc=<optimized out>, argv=0x7ffe4b4744b0, waitAndExit=waitAndExit@entry=true, directly=directly@entry=false) at /usr/src/debug/kcrash-5.18.0/src/kcrash.cpp:650 #3 0x00007f7d0e89c22a in KCrash::startProcess(int, char const**, bool) (argc=argc@entry=21, argv=argv@entry=0x7ffe4b4744b0, waitAndExit=waitAndExit@entry=true) at /usr/src/debug/kcrash-5.18.0/src/kcrash.cpp:616 #4 0x00007f7d0e89c675 in KCrash::defaultCrashHandler(int) (sig=<optimized out>) at /usr/src/debug/kcrash-5.18.0/src/kcrash.cpp:527 #5 0x00007f7d080c6200 in <signal handler called> () at /lib64/libc.so.6 #6 0x00007f7d08fb8290 in QScreen::handle() const (this=0x0) at kernel/qscreen.cpp:112 #7 0x00007f7cfa7f4be9 in QXcbIntegration::createPlatformWindow(QWindow*) const (this=<optimized out>, window=0x2ae79d0) at qxcbintegration.cpp:196 #8 0x00007f7d08f98e25 in QWindowPrivate::create(bool) (this=0x1175d80, recursive=recursive@entry=false) at kernel/qwindow.cpp:392 #9 0x00007f7d08f9901b in QWindow::create() (this=this@entry=0x2ae79d0) at kernel/qwindow.cpp:548 #10 0x00007f7d08f990a8 in QWindow::winId() const (this=0x2ae79d0) at kernel/qwindow.cpp:567 #11 0x00007f7d0e667175 in () at /usr/lib64/libKF5PlasmaQuick.so.5 #12 0x00007f7d0e6699f9 in () at /usr/lib64/libKF5PlasmaQuick.so.5 #13 0x00007f7d08a70cc6 in QMetaObject::activate(QObject*, int, int, void**) (sender=0x297d830, signalOffset=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3713 #14 0x00007f7d08a7073f in QMetaObject::activate(QObject*, int, int, void**) (a=0x7ffe4b474f90, r=0x297d830, this=0x29a86f0) at ../../src/corelib/kernel/qobject_impl.h:124 #15 0x00007f7d08a7073f in QMetaObject::activate(QObject*, int, int, void**) (sender=0xdf8370, signalOffset=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3698 #16 0x00007f7d08a70cc6 in QMetaObject::activate(QObject*, int, int, void**) (sender=sender@entry=0xdf41e0, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3713 #17 0x00007f7d08a712e7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0xdf41e0, m=m@entry=0x7f7d08e8f860 <QTimer::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3578 #18 0x00007f7d08af2a90 in QTimer::timeout(QTimer::QPrivateSignal) (this=this@entry=0xdf41e0) at .moc/moc_qtimer.cpp:197 #19 0x00007f7d08a7df22 in QTimer::timerEvent(QTimerEvent*) (this=0xdf41e0, e=<optimized out>) at kernel/qtimer.cpp:247 #20 0x00007f7d08a718bc in QObject::event(QEvent*) (this=0xdf41e0, e=<optimized out>) at kernel/qobject.cpp:1220 #21 0x00007f7d09db9e7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0xc666a0, receiver=receiver@entry=0xdf41e0, e=e@entry= 0x7ffe4b4754f0) at kernel/qapplication.cpp:3716 #22 0x00007f7d09dbecc8 in QApplication::notify(QObject*, QEvent*) (this=0x7ffe4b4758a0, receiver=0xdf41e0, e=0x7ffe4b4754f0) at kernel/qapplication.cpp:3499 #23 0x00007f7d08a40e95 in QCoreApplication::notifyInternal(QObject*, QEvent*) (this=0x7ffe4b4758a0, receiver=0xdf41e0, event=event@entry=0x7ffe4b4754f0) at kernel/qcoreapplication.cpp:965 #24 0x00007f7d08a9777d in QTimerInfoList::activateTimers() (event=0x7ffe4b4754f0, receiver=<optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:224 #25 0x00007f7d08a9777d in QTimerInfoList::activateTimers() (this=0xcadc50) at kernel/qtimerinfo_unix.cpp:637 #26 0x00007f7d08a97aa1 in timerSourceDispatch(GSource*, GSourceFunc, gpointer) (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:177 #27 0x00007f7d0484ec84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #28 0x00007f7d0484eed8 in () at /usr/lib64/libglib-2.0.so.0 #29 0x00007f7d0484ef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #30 0x00007f7d08a97d8b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0xca3db0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #31 0x00007f7d08a3ed53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffe4b475730, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #32 0x00007f7d08a468f6 in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1229 #33 0x00007f7d08f8a79c in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1527 #34 0x00007f7d09db6605 in QApplication::exec() () at kernel/qapplication.cpp:2976 #35 0x0000000000436ab6 in main(int, char**) (argc=2, argv=<optimized out>) at /usr/src/debug/plasma-workspace-5.5.4/shell/main.cpp:181 sddm-greeter exits if the monitor is not switched on when the gretter is shown. The problem is reported here: https://forums.opensuse.org/showthread.php/513153-ssdm-greeter-exits-or-han… System logs: 2016-01-28T23:11:19.980147+01:00 kenshiro sddm[1091]: Running display setup script "/etc/X11/xdm/Xsetup" 2016-01-28T23:11:19.993288+01:00 kenshiro sddm[1091]: Display server started. 2016-01-28T23:11:19.993497+01:00 kenshiro sddm[1091]: Socket server starting... 2016-01-28T23:11:19.993639+01:00 kenshiro sddm[1091]: Socket server started. 2016-01-28T23:11:19.993885+01:00 kenshiro sddm[1091]: Greeter starting... 2016-01-28T23:11:19.994039+01:00 kenshiro sddm[1091]: Adding cookie to "/run/sddm/{5ab51fe3-b0e9-41b7-b2ed-294821cc0322}" 2016-01-28T23:11:19.998523+01:00 kenshiro sddm-helper[1653]: [PAM] Starting... 2016-01-28T23:11:19.998753+01:00 kenshiro sddm-helper[1653]: [PAM] Authenticating... 2016-01-28T23:11:19.998916+01:00 kenshiro sddm-helper[1653]: [PAM] returning. 2016-01-28T23:11:19.999052+01:00 kenshiro sddm-helper: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0) 2016-01-28T23:11:20.014407+01:00 kenshiro sddm[1091]: Greeter session started successfully 2016-01-28T23:11:20.027505+01:00 kenshiro sddm-greeter[1655]: Reading from "/usr/share/xsessions/enlightenment.desktop" 2016-01-28T23:11:20.027786+01:00 kenshiro sddm-greeter[1655]: Reading from "/usr/share/xsessions/gnome.desktop" 2016-01-28T23:11:20.027936+01:00 kenshiro sddm-greeter[1655]: Reading from "/usr/share/xsessions/icewm.desktop" 2016-01-28T23:11:20.028071+01:00 kenshiro sddm-greeter[1655]: Reading from "/usr/share/xsessions/kde-plasma.desktop" 2016-01-28T23:11:20.028204+01:00 kenshiro sddm-greeter[1655]: Reading from "/usr/share/xsessions/plasma5.desktop" 2016-01-28T23:11:20.028340+01:00 kenshiro sddm-greeter[1655]: Connected to the daemon. 2016-01-28T23:11:20.028474+01:00 kenshiro sddm[1091]: Message received from greeter: Connect 2016-01-28T23:11:20.062294+01:00 kenshiro sddm-greeter[1655]: QObject::installEventFilter(): Cannot filter events for objects in a different thread. 2016-01-28T23:11:20.250847+01:00 kenshiro sddm-greeter[1655]: QObject::installEventFilter(): Cannot filter events for objects in a different thread. 2016-01-28T23:11:20.404977+01:00 kenshiro sddm-greeter[1655]: file:///usr/share/sddm/themes/breeze/components/InfoPane.qml:52:22: Unable to assign [undefined] to int 2016-01-28T23:11:20.405245+01:00 kenshiro sddm-greeter[1655]: Adding view for "HDMI2" QRect(0,0 1920x1080) 2016-01-28T23:11:20.408967+01:00 kenshiro sddm-greeter[1655]: Message received from daemon: Capabilities 2016-01-28T23:11:20.409139+01:00 kenshiro sddm-greeter[1655]: Message received from daemon: HostName 2016-01-28T23:15:03.058840+01:00 kenshiro sddm-helper[1653]: [PAM] Ended. 2016-01-28T23:15:03.059337+01:00 kenshiro sddm[1091]: Auth: sddm-helper exited successfully 2016-01-28T23:15:03.059517+01:00 kenshiro sddm[1091]: Greeter stopped. Apparently both are related to this upstream bug: https://bugreports.qt.io/browse/QTBUG-42985 Leap 42.1 KDE is basically unusable in this state and, as far as I can tell, upstream provided a bugfix but decided not to implement it in QT 5.5. Would it be possible to upgrade QT in Leap to 5.6? -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 892893] New: Unable to Configure NFS Server a Reboot is Required
by bugzilla_noreply＠novell.com 19 Jun '18

19 Jun '18

https://bugzilla.novell.com/show_bug.cgi?id=892893 https://bugzilla.novell.com/show_bug.cgi?id=892893#c0 Summary: Unable to Configure NFS Server a Reboot is Required Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: secure(a)aphofis.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Enter Yast>Network Services>NFS Server> Start Services, Open Firewall, Disable NFSv4, Export 2 Directories>Finish ERROR Unable to stop idmapd. Reproducible: Always Steps to Reproduce: 1.Enter Yast>Network Services>NFS Server> Start Services, Open Firewall, Disable NFSv4, Export 2 Directories>Finish ERROR Unable to stop idmapd. 2. 3. Actual Results: ERROR Unable to stop idmapd. -- 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 5

[Bug 869116] New: Apper No Longer Requires escalation to root auth to make changes to installing O/S changes
by bugzilla_noreply＠novell.com 19 Jun '18

19 Jun '18

https://bugzilla.novell.com/show_bug.cgi?id=869116 https://bugzilla.novell.com/show_bug.cgi?id=869116#c0 Summary: Apper No Longer Requires escalation to root auth to make changes to installing O/S changes Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: secure(a)aphofis.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 Apper in its now current for will not call for escalation to root authority to modify and install changes to O/S. If we wanted to copy MS convention where updates and changes to the O/S....we would use it. This is one of the stand-out security features thats sets our O/S above the rest and to enable these changes without root authority sets a dangerous precedent Reproducible: Always Steps to Reproduce: 1. Every time apper wants to make changes to the O/S 100% reproducable 2. 3. Actual Results: No escalation to root authority is called by apper Expected Results: Changes to O/S should be the privilege of root and no user authority and escalation to root should be called for before we let any application change the O/S With so much log data files I don’t really no what to supply to support this...Please provide details of what audit log files you require to solve. Priority set as this is a direct threat to O/S security and its now broken as previously root auth was always required. Please do not close as DOWNSTREAM OR UPSTREAM..Apper is an integral and non optional inclusion to the packing list of 12.3 and as such the product opensuse is the arbiter and coordinator of Apper -- 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 1

[Bug 848914] New: Publish Information around Partitioning Requirements of Boot Requirements with UEFI BIOS
by bugzilla_noreply＠novell.com 19 Jun '18

19 Jun '18

https://bugzilla.novell.com/show_bug.cgi?id=848914 https://bugzilla.novell.com/show_bug.cgi?id=848914#c0 Summary: Publish Information around Partitioning Requirements of Boot Requirements with UEFI BIOS Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: secure(a)aphofis.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 If ever we are going to see changed in PC BIOS's it will be in this decade. Current UEFI BIOS's are standard with most all X_64 Motherboards. The UEFI BIOS is a temporary measure to permit backwardly compatible Processors and Motherboards and my enhancement would be to publish partitioning information on screen thats not an option before the partitioning phase of Installation. Current warnings generated by the Partitioner itself do warn of requirements for /boot/uefi with FAT. As there will be many changes to BIOS this decade I think we need a mandatory full screen explanation of partitioning changes that can be written for all coming versions as it will be needed and under that preface every installation from 13.x to anything can all make use of a text screen before the partitioner is displayed on screen as part of every Installation Reproducible: Always Steps to Reproduce: 1. Try to configure a boot partition with an X_64 UEFI BIOS and a warning is generated on the users final acceptance of the chosen partitioning. 2. The warning is too late and there is not sufficient space to provide detailed instructions and the reasoning and its going to get more problematic. Additionally as soon as M.S come out with a new file formation partitioning we will need to spell partitioning out in a clear concise way before the user does anything with the partitioner 3. Expected Results: Its a small and advantages addition to the Install Program to have a text screen available before the partitioning part of our current installation is reached. Currently we only knock back the partitioning with a warning after the partitioner has been used. It needs full explanation before not a single line after. It should be very easy to implement this text screen as the need far outweighs the man hour time factor it would take to implement above. I believe this should be assigned and completed as an urgent undertaking before we ship another version as its benefit now and future is so very important. -- 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 922997] New: Enable GNU Terry Pratchett in postfix
by bugzilla_noreply＠novell.com 18 Jun '18

18 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=922997 Bug ID: 922997 Summary: Enable GNU Terry Pratchett in postfix 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: --- http://www.gnuterrypratchett.com/#postfix should be enabled by default on openSUSE's postfix installation. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 813340] New: Suspected memory corruption in standard capi20 lib
by bugzilla_noreply＠novell.com 17 Jun '18

17 Jun '18

https://bugzilla.novell.com/show_bug.cgi?id=813340 https://bugzilla.novell.com/show_bug.cgi?id=813340#c0 Summary: Suspected memory corruption in standard capi20 lib Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 0 Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jan.fengler(a)adviqo.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.43 Safari/537.31 The capi20 lib from the i4l-base source-package from http://download.opensuse.org/repositories/home:/kkeil:/ISDN/openSUSE_Factor… (and also Version 3.23-100.1 which is newer) seems to create memory corruption during capi20_put_message sending data_b3_req, because no memory is assigned for the data that is put behind the original message in the function capi_processMessage (capi20.c row 962ff). Unfortunately this seems to be a private function and so i could not easily write a test against the entire lib. Reproducible: Always Steps to Reproduce: I provide an example program that uses a 1:1 copy of the original function. I use capi via JNI from Java and it crashes when freeing memory exactly as the test program does. Actual Results: Memory corruption when freeing the memory used for the data_b3_req-message. Expected Results: No memory corruption, the program should terminate without a problem. The last known working version (from openSuSE 10.3) assigned memory for SND_BUFSIZ bytes and copied the original message to this before copying the data bytes after the message and that worked. I will change the code of the function standardPutMessage to do this to avoid the problem and add a patch to this bug report if it works with the patch. I must admit that i could have overseen something, but unfortunately it seems not so far. -- 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 9

[Bug 872264] New: 'hostname -s' returns "hostname: Name or service not known" when content of /etc/HOSTNAME omits domain
by bugzilla_noreply＠novell.com 15 Jun '18

15 Jun '18

https://bugzilla.novell.com/show_bug.cgi?id=872264 https://bugzilla.novell.com/show_bug.cgi?id=872264#c0 Summary: 'hostname -s' returns "hostname: Name or service not known" when content of /etc/HOSTNAME omits domain Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mrmazda(a)earthlink.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- To reproduce: 1-configure /etc/HOSTNAME sans domain (no dots contained therein) 2-run any script containing 'hostname -s' Actual behavior: 1-script output disrupted by return of "hostname: Name or service not known" Expected behavior: 1-same output as if -s had been omitted from hostname call Comments: 1-Cauldron and Rawhide both sensibly produce same short hostname output from 'hostname' as from 'hostname -s' when /etc/hostname omits dot(s)/domain. 2-According to the man page, 'hostname -s' should "Display the short host name. This is the host name cut at the first dot.", as it does in current Cauldron and Rawhide, whose hostname man page contains the identical description of -s as Factory's. -- 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 8