October 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 943757] New: yast storage with ncurses does not due to nokogiri error message
by bugzilla_noreply＠novell.com 04 Oct '18

04 Oct '18

http://bugzilla.suse.com/show_bug.cgi?id=943757 Bug ID: 943757 Summary: yast storage with ncurses does not due to nokogiri error message Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: aschnell(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- For various ruby programs I have installed a bunch of gems from different sources (which I have no overview of). Anyway, many ruby programs print an error during startup, this can be show using irb: aschnell@thalassa:~> irb irb(main):001:0> require "dbus" WARNING: Nokogiri was built against LibXML version 2.9.2, but has dynamically loaded 2.9.1 => true Unfortunately for yast ncurses this causes a program termination since stderr is in a bad state (I suppose closed): [Y2Ruby] binary/Y2RubyUtils.cc(y2_require):25 cannot require yast:Bad file descriptor @ io_write - <STDERR> at /usr/lib64/ruby/gems/2.1.0/gems/nokogiri-1.6.6.2/lib/nokogiri/version.rb:94:in `write' The rest of y2log is very misleading, e.g. stating the Storage.rb does not provide the module Storage. But with the Qt frontend YaST does start. The system is openSUSE 13.2 with YaST:Head and various ruby gems. -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 944302] New: php5 and openhpi fails to build if MD5 and DES support disabled in net-snmp
by bugzilla_noreply＠novell.com 02 Oct '18

02 Oct '18

http://bugzilla.suse.com/show_bug.cgi?id=944302 Bug ID: 944302 Summary: php5 and openhpi fails to build if MD5 and DES support disabled in net-snmp Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: meissner(a)suse.com Reporter: mlin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The latest net-snmp SR https://build.opensuse.org/request/show/323040 has disabled md5 and des support, however php5 and openhpi fails to build then. The same issue also effected Leap as https://build.opensuse.org/request/show/325654 which has the similar changes and pending in Leap for same reason. -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 911587] New: Message at shutdown: "kernel: watchdog watchdog0: watchdog did not stop!"
by bugzilla_noreply＠novell.com 30 Sep '18

30 Sep '18

http://bugzilla.opensuse.org/show_bug.cgi?id=911587 Bug ID: 911587 Summary: Message at shutdown: "kernel: watchdog watchdog0: watchdog did not stop!" Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Each shutdown seems to hang for a while, then the message "kernel: watchdog watchdog0: watchdog did not stop!" appears. I guess this is not expected. (Next log message is "dmeventd[945]: dmeventd shutting down."; maybe this helps) -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 904303] New: gnome-keyring hijacked the GPG socket
by bugzilla_noreply＠novell.com 07 Sep '18

07 Sep '18

http://bugzilla.opensuse.org/show_bug.cgi?id=904303 Bug ID: 904303 Summary: gnome-keyring hijacked the GPG socket Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: All OS: All Status: NEW Severity: Minor Priority: P5 - None Component: Xfce Assignee: gber(a)opensuse.org Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- gpg starts throwing new warnings since openSUSE 13.2. $ gpg -ab blah.txt You need a passphrase to unlock the secret key for user: "Jan Engelhardt <jengelh(a)gmx.de>" 4096-bit RSA key, ID 19FC338D, created 2011-05-09 gpg: WARNING: The GNOME keyring manager hijacked the GnuPG agent. gpg: WARNING: GnuPG will not work properly - please configure that tool to not interfere with the GnuPG system! $ env GPG_AGENT_INFO=/run/user/25121/keyring/gpg:0:1 $ lsof|grep keyring/gpg gnome-key 3799 jengelh 11u unix 0x0000000000000000 0t0 32398 /run/user/25121/keyring/gpg ... (started by xfce or so) -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 941862] New: GNOME Software won't open RPM files
by bugzilla_noreply＠novell.com 03 Sep '18

03 Sep '18

http://bugzilla.opensuse.org/show_bug.cgi?id=941862 Bug ID: 941862 Summary: GNOME Software won't open RPM files Classification: openSUSE Product: openSUSE Distribution Version: 42.1 Milestone 1 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: castar(a)cipelli.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:40.0) Gecko/20100101 Firefox/40.0 Build Identifier: When downloading RPMs from the internet, the option is given to open them with GNOME Software (presumably to install them). However, when doing so, Software opens with an error: "GetDetailsLocal not supported by backend". Reproducible: Always Steps to Reproduce: 1. Download an RPM for openSUSE. 2. Open it using GNOME Software. Actual Results: Gave error "GetDetailsLocal not supported by backend" Expected Results: Given details about the package. This happened on my old laptop and my new computer (HP G56 with AMD V140 and custom-built with AMD A10-7700K respectively). -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 909418] New: when ejecting DVD using hardware button, system thinks DVD is still mounted
by bugzilla_noreply＠novell.com 27 Aug '18

27 Aug '18

http://bugzilla.opensuse.org/show_bug.cgi?id=909418 Bug ID: 909418 Summary: when ejecting DVD using hardware button, system thinks DVD is still mounted Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When I used a mounted DVD (in a BluRay writer) and press eject-button on the drive, the media ejects, and I close the tray. In GNOME (at least) the system still thinks the media is mounted, even if I inserted another DVD into the drive in the meantime. -- You are receiving this mail because: You are on the CC list for the bug.

1 40

[Bug 915996] New: LibreOffice doesn't show internal Help
by bugzilla_noreply＠novell.com 07 Aug '18

07 Aug '18

http://bugzilla.opensuse.org/show_bug.cgi?id=915996 Bug ID: 915996 Summary: LibreOffice doesn't show internal Help Classification: openSUSE Product: openSUSE Factory Version: 201502* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: LibreOffice Assignee: bnc-team-ooo(a)forge.provo.novell.com Reporter: lazy.kent(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- LibreOffice v4.4.0.2 doesn't show internal Help. Using locale "ru_RU". Calling Help from the menu "Help" or "F1" key opens a browser with URL https://help.libreoffice.org/scalc/.uno:HelpIndex?Language=ru&System=UNIX&V… (in case of calc) or https://help.libreoffice.org/swriter/.uno:HelpIndex?Language=ru&System=UNIX… (in case of writer). Installed packages: % rpm -qa | grep libreoffice libreoffice-math-4.4.0.2-1.1.x86_64 libreoffice-draw-4.4.0.2-1.1.x86_64 libreoffice-l10n-en-4.4.0.2-1.1.noarch libreoffice-icon-theme-crystal-4.4.0.2-1.1.noarch libreoffice-calc-extensions-4.4.0.2-1.1.x86_64 libreoffice-calc-4.4.0.2-1.1.x86_64 libreoffice-gnome-4.4.0.2-1.1.x86_64 libreoffice-icon-theme-oxygen-4.4.0.2-1.1.noarch libreoffice-writer-4.4.0.2-1.1.x86_64 libreoffice-branding-openSUSE-4.0-5.1.noarch libreoffice-4.4.0.2-1.1.x86_64 libreoffice-impress-4.4.0.2-1.1.x86_64 libreoffice-mailmerge-4.4.0.2-1.1.x86_64 libreoffice-base-4.4.0.2-1.1.x86_64 libreoffice-pyuno-4.4.0.2-1.1.x86_64 libreoffice-templates-ru-3.3-13.1.noarch libreoffice-icon-theme-galaxy-4.4.0.2-1.1.noarch libreoffice-filters-optional-4.4.0.2-1.1.x86_64 libreoffice-writer-extensions-4.4.0.2-1.1.x86_64 libreoffice-l10n-ru-4.4.0.2-1.1.noarch openSUSE Tumbleweed x86_64. And I remember, it was OK in 4.4.0.1. -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[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