October 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 629374] New: desktop-data-openSUSE contains some KDE-specific bits
by bugzilla_noreply＠novell.com 25 Nov '18

25 Nov '18

http://bugzilla.novell.com/show_bug.cgi?id=629374 http://bugzilla.novell.com/show_bug.cgi?id=629374#c0 Summary: desktop-data-openSUSE contains some KDE-specific bits Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: vuntz(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Here are some bits in desktop-data-openSUSE that should probably live in some of the kde branding packages (or in qt): + etc/kde4/: contains kdm/backgroundrc (should live in kdm-branding-openSUSE) + etc/profile.d/desktop-data.* and usr/share/desktop-data: the scripts have a line to set QT_SYSTEM_DIR to /usr/share/desktop-data. This should really live in a qt package. I'm also wondering about everything in etc/xdg/menus/, usr/share/desktop-directories/ and usr/share/icons/: this contains the XDG menu structure, except that GNOME now uses something else since we were not happy with this structure and were unable to make any real progress on changing it. LXDE also doesn't use it. So it's now more or less KDE-specific... Finally, etc/skel/ contains public_html. Is this something you want to keep? I know it annoys me to have this directory created. -- Configure bugmail: http://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 867041] New: fontforge segfaults if both libpng12-0 and libpng15-15 are installed
by bugzilla_noreply＠novell.com 12 Nov '18

12 Nov '18

https://bugzilla.novell.com/show_bug.cgi?id=867041 https://bugzilla.novell.com/show_bug.cgi?id=867041#c0 Summary: fontforge segfaults if both libpng12-0 and libpng15-15 are installed Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: openSUSE 12.3 Status: NEW Severity: Critical Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: wl(a)gnu.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:27.0) Gecko/20100101 Firefox/27.0 [fontforge 20120731-2.1.2] [libpng12-0 1.2.50-3.1.1] [libpng15-15 1.5.13-3.1.1] Calling fontforge gives Copyright (c) 2000-2012 by George Williams. Executable based on sources from 14:57 GMT 31-Jul-2012. Library based on sources from 14:57 GMT 31-Jul-2012. Application was compiled with png.h from libpng-1.5.13 Application is running with png.c from libpng-1.2.50 Incompatible libpng version in application and library Segmentation Fault Recompiling fontforge from the original sources fixed this issue for me. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 12

[Bug 900558] New: Impossible to boot in single user mode with root mounted read only
by bugzilla_noreply＠novell.com 03 Nov '18

03 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=900558 Bug ID: 900558 Summary: Impossible to boot in single user mode with root mounted read only Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: archie(a)dellroad.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have a 13.1 system with all the latest updates as of today and it is spitting out the UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY message for the root filesystem, and then booting normally with root mounted root read-write. First of all, I would expect it to not boot normally in this case, but whatever. Anyway, when I try to do what it says, it's impossible! Here's why: even though I reboot with "single ro" on the boot line and it does in fact go into single user mode, it still mounts root read-write (after complaining of the same fsck errors). Since the 1980's single user mode has always left root mounted read-only so you can run fsck if needed, and you can always remount it read-write if you want. Why did this change? Of course "mount -o remount,ro /" doesn't work. Because root is mounted read-write and it's impossible to get the system to boot with root mounted read-only, then even in single user mode, it's impossible to run fsck and fix the problem. So it's impossible to resolve this problem without the use of a rescue disk. Please fix, this is a bad dead-end people can fall into. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 872984] New: /etc/apparmor.d/usr.lib.apache2.mpm-prefork.apache2 too broad
by bugzilla_noreply＠novell.com 30 Oct '18

30 Oct '18

https://bugzilla.novell.com/show_bug.cgi?id=872984 https://bugzilla.novell.com/show_bug.cgi?id=872984#c0 Summary: /etc/apparmor.d/usr.lib.apache2.mpm-prefork.apache2 too broad Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor AssignedTo: suse-beta(a)cboltz.de ReportedBy: meissner(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- /etc/apparmor.d/usr.lib.apache2.mpm-prefork.apache2 does / rw, /** mrwlkix, so basically ... every process can do everything. Correct me if I am wrong, but this profile is then not necessary. -- 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 803057] New: PostgreSQL 9.2.3, 9.1.8, 9.0.12, 8.4.16 and 8.3.23 released
by bugzilla_noreply＠novell.com 23 Oct '18

23 Oct '18

https://bugzilla.novell.com/show_bug.cgi?id=803057 https://bugzilla.novell.com/show_bug.cgi?id=803057#c0 Summary: PostgreSQL 9.2.3, 9.1.8, 9.0.12, 8.4.16 and 8.3.23 released Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: lijewski.stefan(a)zabka.pl QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 >From postgresql.org: The PostgreSQL Global Development Group has released a security update to all current versions of the PostgreSQL database system, including versions 9.2.3, 9.1.8, 9.0.12, 8.4.16, and 8.3.23. This update fixes a denial-of-service (DOS) vulnerability. All users should update their PostgreSQL installations as soon as possible. The security issue fixed in this release, CVE-2013-0255, allows a previously authenticated user to crash the server by calling an internal function with invalid arguments. This issue was discovered by independent security researcher Sumit Soni this week and reported via Secunia SVCRP, and we are grateful for their efforts in making PostgreSQL more secure. Today's update also fixes a performance regression which caused a decrease in throughput when using dynamic queries in stored procedures in version 9.2. Applications which use PL/pgSQL's EXECUTE are strongly affected by this regression and should be updated. Additionally, we have fixed intermittent crashes caused by CREATE/DROP INDEX CONCURRENTLY, and multiple minor issues with replication. Reproducible: Always -- 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 6

[Bug 820566] New: wireshark security updates to 1.8.7 and 1.6.15
by bugzilla_noreply＠novell.com 19 Oct '18

19 Oct '18

https://bugzilla.novell.com/show_bug.cgi?id=820566 https://bugzilla.novell.com/show_bug.cgi?id=820566#c0 Summary: wireshark security updates to 1.8.7 and 1.6.15 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: Andreas.Stieger(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:20.0) Gecko/20100101 Firefox/20.0 https://www.wireshark.org/docs/relnotes/wireshark-1.8.7.html wnpa-sec-2013-23 CVE-2013-2486 CVE-2013-2487 The RELOAD dissector could go into an infinite loop. wnpa-sec-2013-24 The GTPv2 dissector could crash. wnpa-sec-2013-25 The ASN.1 BER dissector could crash. wnpa-sec-2013-26 The PPP CCP dissector could crash. wnpa-sec-2013-27 The DCP ETSI dissector could crash. wnpa-sec-2013-28 The MPEG DSM-CC dissector could crash. wnpa-sec-2013-29 The Websocket dissector could crash. wnpa-sec-2013-30 The MySQL dissector could go into an infinite loop. wnpa-sec-2013-31 The ETCH dissector could go into a large loop. https://www.wireshark.org/docs/relnotes/wireshark-1.6.15.html 1.6.15 wnpa-sec-2013-25 The ASN.1 BER dissector could crash Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 15

[Bug 800701] New: X windows is corrupt after logging in on an AMD A10-5800K APU
by bugzilla_noreply＠novell.com 31 Jul '18

31 Jul '18

https://bugzilla.novell.com/show_bug.cgi?id=800701 https://bugzilla.novell.com/show_bug.cgi?id=800701#c0 Summary: X windows is corrupt after logging in on an AMD A10-5800K APU Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Xen AssignedTo: jdouglas(a)suse.com ReportedBy: ajbiii(a)comcast.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 Installed 12.3. The regular kernel and X windows works fine. Reboot to the xen kernel. The login screen is displayed correctly. After logging in, the display is corrupt. The mouse pointer is ok and I can see that the menu is active by putting the cursor in the lower left corner and clicking but the display is unusable. Just an aside: The xen kernel wouldn't even boot on the APU with 12.1 or 12.2. Reproducible: Always Steps to Reproduce: 1. Install 12.3 on an AMD Trinity APU. 2. Boot regular kernel, log in and verify X is working. 3. Reboot with the xen kernel. 4. Log in and observe the corruption Actual Results: Screen is corrupt Expected Results: Normal X windows operation -- 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 23

[Bug 902352] New: snapperd crashed shortly after boot
by bugzilla_noreply＠novell.com 29 Jul '18

29 Jul '18

http://bugzilla.opensuse.org/show_bug.cgi?id=902352 Bug ID: 902352 Summary: snapperd crashed shortly after boot Classification: openSUSE Product: openSUSE Factory Version: NO 13.2 BUGS!! Hardware: i686 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: aschnell(a)suse.com Reporter: mpluskal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After reboot of recent opensuse factory, I have noticed that snapperd crashed (for no apparent reason): # systemd-coredumpctl gdb 3614 TIME PID UID GID SIG EXE Tue 2014-10-21 22:11:37 CEST 3614 0 0 6 /usr/sbin/snapperd GNU gdb (GDB; openSUSE Factory) 7.8 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i586-suse-linux". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://bugs.opensuse.org/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... warning: /etc/gdbinit.d/gdb-heap.py: No such file or directory Reading symbols from /usr/sbin/snapperd...Reading symbols from /usr/lib/debug/usr/sbin/snapperd.debug...done. done. [New LWP 3614] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". Core was generated by `/usr/sbin/snapperd'. Program terminated with signal SIGABRT, Aborted. #0 0xb77bae60 in __kernel_vsyscall () (gdb) bt full #0 0xb77bae60 in __kernel_vsyscall () No symbol table info available. #1 0xb73f2437 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 resultvar = <optimized out> resultvar = <optimized out> pid = -1219051520 selftid = 3614 #2 0xb73f3b8e in __GI_abort () at abort.c:78 save_stage = 1 act = {__sigaction_handler = {sa_handler = 0x83fd424, sa_sigaction = 0x83fd424}, sa_mask = {__val = {64, 3074638989, 3075918176, 3078479804, 3077059232, 5, 3220034192, 3078403714, 3077059672, 3070747136, 1, 5, 0, 3075915776, 3075918176, 3075922024, 3220034164, 3076988956, 3076153812, 3076093316, 138392728, 3075915776, 3075918176, 3074203892, 3075918176, 3074619692, 3076988928, 3076988928, 3075919228, 138400804, 138399352, 3078429072}}, sa_flags = 138392632, sa_restorer = 0xb73f3a80 <__GI_abort>} sigs = {__val = {32, 0 <repeats 31 times>}} #3 0xb75ddfe5 in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95 terminating = true t = <optimized out> #4 0xb75dbc53 in __cxxabiv1::__terminate (handler=0xb75dde50 <__gnu_cxx::__verbose_terminate_handler()>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:38 No locals. #5 0xb75dab75 in __cxa_call_terminate (ue_header=0x83fb468) at ../../../../libstdc++-v3/libsupc++/eh_call.cc:54 No locals. #6 0xb75db791 in __cxxabiv1::__gxx_personality_v0 (version=1, actions=6, exception_class=5138137972254386944, ue_header=0x83fb468, context=0xbfedd550) at ../../../../libstdc++-v3/libsupc++/eh_personality.cc:670 action_record = <optimized out> p = <optimized out> thrown_ptr = 0x0 info = {Start = 3078108587, LPStart = 0, ttype_base = 0, TType = 0x0, action_table = 0xfffffffc <error: Cannot access memory at address 0xfffffffc>, ttype_encoding = 0 '\000', call_site_encoding = 192 '\300'} landing_pad = <optimized out> ip = <optimized out> handler_switch_value = 0 foreign_exception = false found_type = <optimized out> language_specific_data = 0xb779200c "\377\233\021\001\005>\005\342\001\003" ip_before_insn = 0 #7 0xb758506c in _Unwind_RaiseException_Phase2 (exc=exc@entry=0x83fb468, context=context@entry=0xbfedd550) at ../../../libgcc/unwind.inc:62 fs = {regs = {reg = {{loc = {reg = 0, offset = 0, exp = 0x0}, how = REG_UNSAVED}, {loc = {reg = 0, offset = 0, exp = 0x0}, how = REG_UNSAVED}, {loc = {reg = 0, offset = 0, exp = 0x0}, how = REG_UNSAVED}, {loc = { reg = 4294967276, offset = -20, exp = 0xffffffec <error: Cannot access memory at address 0xffffffec>}, how = REG_SAVED_OFFSET}, {loc = {reg = 0, offset = 0, exp = 0x0}, how = REG_UNSAVED}, {loc = { reg = 4294967288, offset = -8, exp = 0xfffffff8 <error: Cannot access memory at address 0xfffffff8>}, how = REG_SAVED_OFFSET}, {loc = {reg = 4294967280, offset = -16, exp = 0xfffffff0 <error: Cannot access memory at address 0xfffffff0>}, how = REG_SAVED_OFFSET}, {loc = {reg = 4294967284, offset = -12, exp = 0xfffffff4 <error: Cannot access memory at address 0xfffffff4>}, how = REG_SAVED_OFFSET}, {loc = {reg = 4294967292, offset = -4, exp = 0xfffffffc <error: Cannot access memory at address 0xfffffffc>}, how = REG_SAVED_OFFSET}, {loc = {reg = 0, offset = 0, exp = 0x0}, how = REG_UNSAVED}, {loc = {reg = 0, offset = 0, exp = 0x0}, how = REG_UNSAVED}, {loc = {reg = 0, offset = 0, exp = 0x0}, how = REG_UNSAVED}, {loc = {reg = 0, offset = 0, exp = 0x0}, how = REG_UNSAVED}, {loc = { reg = 0, offset = 0, exp = 0x0}, how = REG_UNSAVED}, {loc = {reg = 0, offset = 0, exp = 0x0}, how = REG_UNSAVED}, {loc = {reg = 0, offset = 0, exp = 0x0}, how = REG_UNSAVED}, {loc = {reg = 0, offset = 0, exp = 0x0}, how = REG_UNSAVED}, {loc = {reg = 0, offset = 0, exp = 0x0}, how = REG_UNSAVED}}, prev = 0x0, cfa_offset = 64, cfa_reg = 4, cfa_exp = 0x0, cfa_how = CFA_REG_OFFSET}, pc = 0xb772a690 <snapper::Snapper::~Snapper()+144>, personality = 0x8053950 <__gxx_personality_v0@plt>, data_align = -4, code_align = 1, retaddr_column = 8, fde_encoding = 27 '\033', lsda_encoding = 27 '\033', saw_z = 1 '\001', signal_frame = 0 '\000', eh_ptr = 0x0} match_handler = 4 code = _URC_NO_REASON #8 0xb75855ad in _Unwind_Resume (exc=exc@entry=0x83fb468) at ../../../libgcc/unwind.inc:230 this_context = {reg = {0xbfedd5d4, 0x0, 0xbfedd5d8, 0xbfedd5dc, 0x0, 0xbfedd5e8, 0xbfedd5e0, 0xbfedd5e4, 0xbfedd5ec, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, cfa = 0xbfedd5f0, ra = 0xb774b85f <snapper::logStreamClose(snapper::LogLevel, char const*, unsigned int, char const*, std::basic_ostringstream<char, std::char_traits<char>, std::allocator<char> >*)+431>, lsda = 0x0, bases = { tbase = 0x0, dbase = 0xb758c000, func = 0xb7585550 <_Unwind_Resume>}, flags = 1073741824, version = 0, args_size = 0, by_value = '\000' <repeats 17 times>} cur_context = {reg = {0xbfedd5d4, 0x0, 0xbfedd5d8, 0xbfedd62c, 0x0, 0xbfedd638, 0xbfedd630, 0xbfedd634, 0xbfedd63c, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, cfa = 0xbfedd640, ra = 0xb772a6dd <snapper::Snapper::~Snapper()+221>, lsda = 0xb779200c, bases = {tbase = 0x0, dbase = 0xb779b000, func = 0xb772a600 <snapper::Snapper::~Snapper()>}, flags = 1073741824, version = 0, args_size = 0, by_value = '\000' <repeats 17 times>} code = <optimized out> #9 0xb774b85f in ~basic_string (this=<optimized out>, __in_chrg=<optimized out>) at /usr/include/c++/4.8/bits/basic_string.h:539 No locals. #10 snapper::logStreamClose (level=level@entry=snapper::MILESTONE, file=file@entry=0xb777ade3 "Snapper.cc", line=line@entry=112, func=func@entry=0xb777b348 <snapper::Snapper::~Snapper()::__FUNCTION__> "~Snapper", stream=stream@entry=0x83fca40) at Log.cc:64 No locals. #11 0xb772a6dd in snapper::Snapper::~Snapper (this=0xb67007f0, __in_chrg=<optimized out>) at Snapper.cc:112 __buf = 0x83fca40 ---Type <return> to continue, or q <return> to quit--- #12 0x08063118 in MetaSnapper::~MetaSnapper (this=0x83fd498, __in_chrg=<optimized out>) at MetaSnapper.cc:117 No locals. #13 0x08063197 in ~_List_node (this=0x83fd490, __in_chrg=<optimized out>) at /usr/include/c++/4.8/bits/stl_list.h:106 No locals. #14 destroy<std::_List_node<MetaSnapper> > (this=<optimized out>, __p=0x83fd490) at /usr/include/c++/4.8/ext/new_allocator.h:124 No locals. #15 _M_clear (this=0x80788e8 <meta_snappers>) at /usr/include/c++/4.8/bits/list.tcc:75 __tmp = 0x83fd490 __cur = 0x80788e8 <meta_snappers> #16 ~_List_base (this=0x80788e8 <meta_snappers>, __in_chrg=<optimized out>) at /usr/include/c++/4.8/bits/stl_list.h:378 No locals. #17 ~list (this=0x80788e8 <meta_snappers>, __in_chrg=<optimized out>) at /usr/include/c++/4.8/bits/stl_list.h:438 No locals. #18 MetaSnappers::~MetaSnappers (this=0x80788e8 <meta_snappers>, __in_chrg=<optimized out>) at MetaSnapper.cc:196 No locals. #19 0xb73f52f1 in __run_exit_handlers (status=status@entry=0, listp=0xb756c3c4 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 atfct = <optimized out> onfct = <optimized out> cxafct = <optimized out> f = <optimized out> #20 0xb73f534d in __GI_exit (status=0) at exit.c:104 No locals. #21 0xb73dd99b in __libc_start_main (main=0x8053ca0 <main(int, char**)>, argc=1, argv=0xbfedd7a4, init=0x8069a10 <__libc_csu_init>, fini=0x8069a80 <__libc_csu_fini>, rtld_fini=0xb77cc660 <_dl_fini>, stack_end=0xbfedd79c) at libc-start.c:319 result = <optimized out> unwind_buf = {cancel_jmp_buf = {{jmp_buf = {-1219051520, 0, 0, 0, -2067208107, 617901124}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x1, 0x805462f <_start>}, data = {prev = 0x0, cleanup = 0x0, canceltype = 1}}} not_first_call = <optimized out> #22 0x08054650 in _start () at ../sysdeps/i386/start.S:115 No locals. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 879402] New: date format of atq is unusable for sorting
by bugzilla_noreply＠novell.com 29 Jul '18

29 Jul '18

https://bugzilla.novell.com/show_bug.cgi?id=879402 https://bugzilla.novell.com/show_bug.cgi?id=879402#c0 Summary: date format of atq is unusable for sorting Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: martin(a)oneiros.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 The atq in 13.1 uses a date/time format that is unsuitable for sorting by date/time and there is no way to set the date format used (e.g. to ISO8601). Reproducible: Always Steps to Reproduce: 1. Set up some jobs with at 2. Run atq Actual Results: > atq 1377 Thu May 29 15:04:00 2014 a ms 1387 Thu May 22 21:59:00 2014 a ms 1376 Thu May 29 18:39:00 2014 a ms 1372 Wed May 28 21:32:00 2014 a ms 1 Fri May 23 21:04:00 2014 a ms 1361 Sun May 25 08:04:00 2014 a ms 1373 Thu May 29 09:29:00 2014 a ms 1367 Tue May 27 20:02:00 2014 a ms 4 Fri May 23 22:03:00 2014 a ms 1369 Wed May 28 21:04:00 2014 a ms 7 Sat May 24 19:04:00 2014 a ms 10 Sat May 24 23:03:00 2014 a ms Expected Results: The date format should be ISO 8601 - or there should be a switch to set the date format used. The atq up to 12.3 used ISO 8601, so this is a regression. See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612075 -- 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 13

[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