October 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 851982] New: unable to install ibus due to libreoffice conflict
by bugzilla_noreply＠novell.com 10 Dec '19

10 Dec '19

https://bugzilla.novell.com/show_bug.cgi?id=851982 https://bugzilla.novell.com/show_bug.cgi?id=851982#c0 Summary: unable to install ibus due to libreoffice conflict Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: mrkfbrn(a)yahoo.co.nz QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 Am unable to install ibus due to a conflict with Libreoffice KDE integration. conflict message from yast is "ibus 1.5.4.4.1.x86_64 conflicts with libreoffice-kde4 provided by libreoffice-kde4-4.1.3.2-4.2.x86_64" Yast provides no option to ignore the conflict. ibus is required for Japanese input so this is a showstopper for me. 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 21

[Bug 536505] New: rrdtool graph has some problems with vertical auto-scaling
by bugzilla_noreply＠novell.com 09 Dec '19

09 Dec '19

http://bugzilla.novell.com/show_bug.cgi?id=536505 Summary: rrdtool graph has some problems with vertical auto-scaling Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: All OS/Version: SLES 10 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Ulrich.Windl(a)rz.uni-regensburg.de QAContact: qa(a)suse.de Found By: --- Created an attachment (id=316589) --> (http://bugzilla.novell.com/attachment.cgi?id=316589) Example with --rigid: No y scale displayed User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.21) Gecko/20090410 SUSE/1.1.16-1.1.2 SeaMonkey/1.1.16 (Found in current version of SLES10 SP2, rrdtool-1.2.12-13.2) Specific values (like all between 17.7 and 17.8) cause rrdtool's graph to autoscale the values at a range of 10 to 20, making actual variations practically invisible. There are other intervals where similar problems arise, like [42.0:42.2] where the scale is [40:50]. The --alt-autoscale improves the scaling, but has a problem with not enough numeric labels for the y-axis being shown, just as --rigid does. The author of the tool said the current version is much better regarding those issues. Reproducible: Sometimes Steps to Reproduce: 1. Create graphs with automatic scaling where the values vary a little bit around some undetermined value Actual Results: Some graphs are not good enough to show the variations. Expected Results: The vertical scale should respect the range of values more that it currently does. -- 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 7

[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 902401] New: plymouth segfault
by bugzilla_noreply＠novell.com 15 Nov '19

15 Nov '19

http://bugzilla.opensuse.org/show_bug.cgi?id=902401 Bug ID: 902401 Summary: plymouth segfault 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: idonmez(a)suse.com Reporter: mpluskal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- # systemd-coredumpctl gdb 169 TIME PID UID GID SIG EXE Čt 2014-10-23 14:42:07 CEST 169 0 0 11 /usr/sbin/plymouthd 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: Adresář nebo soubor neexistuje Reading symbols from /usr/sbin/plymouthd...Reading symbols from /usr/lib/debug/usr/sbin/plymouthd.debug...done. done. [New LWP 169] b[Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". Core was generated by `@usr/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-sessio'. Program terminated with signal SIGSEGV, Segmentation fault. #0 ply_event_loop_stop_watching_signal (loop=0x7665642f, signal_number=signal_number@entry=28) at ply-event-loop.c:869 t869 ply-event-loop.c: Adresář nebo soubor neexistuje. (gdb) bt #0 ply_event_loop_stop_watching_signal (loop=0x7665642f, signal_number=signal_number@entry=28) at ply-event-loop.c:869 #1 0xb76febe7 in ply_terminal_close (terminal=0x99f4008) at ply-terminal.c:707 #2 0xb7717159 in ply_hashtable_foreach (hashtable=0x99f3dc8, func=0xb76feb10 <ply_terminal_close>, user_data=user_data@entry=0x99f3e18) at ply-hashtable.c:272 #3 0xb76fb0fc in ply_close_all_terminals (manager=0x99f3e18) at ply-device-manager.c:954 #4 0x0805396c in quit_splash (state=state@entry=0xbff95794) at main.c:1083 #5 0x08053a4f in dump_details_and_quit_splash (state=state@entry=0xbff95794) at main.c:1114 #6 0x08053ccf in on_quit (state=0xbff95794, retain_splash=false, quit_trigger=0x99f6ac0) at main.c:1349 #7 0x0804ee27 in ply_boot_connection_on_request (connection=0x9a028e0) at ply-boot-server.c:534 #8 0xb7713fc6 in ply_event_loop_handle_met_status_for_source (status=PLY_EVENT_LOOP_FD_STATUS_HAS_DATA, source=0x99f1af0, loop=0x99ef0b0) at ply-event-loop.c:1060 #9 ply_event_loop_process_pending_events (loop=loop@entry=0x99ef0b0) at ply-event-loop.c:1327 #10 0xb7714508 in ply_event_loop_run (loop=0x99ef0b0) at ply-event-loop.c:1359 #11 0x0804c424 in main (argc=4, argv=0xbff95ab4) at main.c:2357 (gdb) bt full #0 ply_event_loop_stop_watching_signal (loop=0x7665642f, signal_number=signal_number@entry=28) at ply-event-loop.c:869 node = 0x19 #1 0xb76febe7 in ply_terminal_close (terminal=0x99f4008) at ply-terminal.c:707 __func__ = "ply_terminal_close" #2 0xb7717159 in ply_hashtable_foreach (hashtable=0x99f3dc8, func=0xb76feb10 <ply_terminal_close>, user_data=user_data@entry=0x99f3e18) at ply-hashtable.c:272 i = 5 #3 0xb76fb0fc in ply_close_all_terminals (manager=0x99f3e18) at ply-device-manager.c:954 No locals. #4 0x0805396c in quit_splash (state=state@entry=0xbff95794) at main.c:1083 __func__ = "quit_splash" #5 0x08053a4f in dump_details_and_quit_splash (state=state@entry=0xbff95794) at main.c:1114 No locals. #6 0x08053ccf in on_quit (state=0xbff95794, retain_splash=false, quit_trigger=0x99f6ac0) at main.c:1349 __func__ = "on_quit" #7 0x0804ee27 in ply_boot_connection_on_request (connection=0x9a028e0) at ply-boot-server.c:534 retain_splash = false quit_trigger = 0x99f6ac0 server = 0x99f1688 command = 0x99f69f8 "Q" argument = 0x99f6b40 "" __PRETTY_FUNCTION__ = "ply_boot_connection_on_request" __func__ = "ply_boot_connection_on_request" #8 0xb7713fc6 in ply_event_loop_handle_met_status_for_source (status=PLY_EVENT_LOOP_FD_STATUS_HAS_DATA, source=0x99f1af0, loop=0x99ef0b0) at ply-event-loop.c:1060 next_node = 0x0 destination = 0x9a02a50 node = <optimized out> #9 ply_event_loop_process_pending_events (loop=loop@entry=0x99ef0b0) at ply-event-loop.c:1327 source = 0x99f1af0 is_disconnected = <optimized out> number_of_received_events = 1 i = 0 events = {{events = 1, data = {ptr = 0x99f1af0, fd = 161422064, u32 = 161422064, u64 = 161422064}}, {events = 4294967295, data = {ptr = 0xffffffff, fd = -1, u32 = 4294967295, u64 = 18446744073709551615}} <repeats 63 times>} __PRETTY_FUNCTION__ = "ply_event_loop_process_pending_events" #10 0xb7714508 in ply_event_loop_run (loop=0x99ef0b0) at ply-event-loop.c:1359 No locals. #11 0x0804c424 in main (argc=4, argv=0xbff95ab4) at main.c:2357 state = {loop = 0x99ef0b0, boot_server = 0x99f1688, boot_splash = 0x0, session = 0x99f27e0, boot_buffer = 0x99f17c8, progress = 0x99f3d60, keystroke_triggers = 0x99ef5e0, entry_triggers = 0x99ef5f0, entry_buffer = 0x99f0660, messages = 0x99f1678, command_parser = 0x99ef008, mode = PLY_MODE_BOOT, local_console_terminal = 0x99f40d8, device_manager = 0x99f3e18, deactivate_trigger = 0x0, quit_trigger = 0x99f6ac0, start_time = 2.9794491600000002, splash_delay = nan(0x8000000000000), kernel_command_line = "BOOT_IMAGE=/boot/vmlinuz-3.17.1-0.g5c4d099-default root=UUID=04f6a8f9-ec8e-4fd8-9d03-9159c16a0a32 resume=/dev/disk/by-id/ata-ST3200827A_5ND4PPCL-part1 splash=silent quiet showopts Y2DEBUG=1\n", '\000' <repeats 321 times>, kernel_command_line_is_set = 1, no_boot_log = 0, showing_details = 1, system_initialized = 1, is_redirected = 0, is_attached = 0, should_be_attached = 1, should_retain_splash = 0, is_inactive = 1, is_shown = 0, should_force_details = 0, override_splash_path = 0x0, system_default_splash_path = 0x99f3e80 "/usr/share/plymouth/themes/openSUSE/openSUSE.plymouth", distribution_default_splash_path = 0x99f3f80 "/usr/share/plymouth/themes/openSUSE/openSUSE.plymouth", default_tty = 0x805641f "/dev/tty7", number_of_errors = 0} exit_code = <optimized out> should_help = false no_boot_log = false no_daemon = false debug = false attach_to_session = true daemon_handle = 0x99ef5a0 mode_string = 0x99ef5a0 " " kernel_command_line = 0x0 tty = 0x0 device_manager_flags = <optimized out> sa = {__sigaction_handler = {sa_handler = 0x80529e0 <dosigaction>, sa_sigaction = 0x80529e0 <dosigaction>}, sa_mask = {__val = {0 <repeats 32 times>}}, sa_flags = -2147483648, sa_restorer = 0x0} __func__ = "main" -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 935864] New: zlib: package minizip?
by bugzilla_noreply＠novell.com 12 Nov '19

12 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=935864 Bug ID: 935864 Summary: zlib: package minizip? Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: tchvatal(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: security-team(a)suse.de Found By: --- Blocker: --- zlib contains contrib/minizip which at least by judging from the use of unzip.h is contained as copy in 30 other packages. What about building minizip as separate sub package? -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 911355] New: Job for spamd.service failed
by bugzilla_noreply＠novell.com 11 Nov '19

11 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=911355 Bug ID: 911355 Summary: Job for spamd.service failed 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: stephan.barth(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After the upgrade from 12.3 I found out that spmad was not running anymore. When trying to start it manually I get: # /etc/init.d/spamd restart redirecting to systemctl restart spamd.service Job for spamd.service failed. See "systemctl status spamd.service" and "journalctl -xn" for details. Running the latter command yields: Dec 29 16:40:11 linux-wulv echo[6901]: Starting spamd: Dec 29 16:40:11 linux-wulv spamd[6903]: logger: removing stderr method Dec 29 16:40:11 linux-wulv spamd[6905]: config: no rules were found! Do you need to run 'sa-update'? Dec 29 16:40:12 linux-wulv spamd[6903]: child process [6905] exited or timed out without signaling production of a PID file: exit 255 at /us Dec 29 16:40:12 linux-wulv spamd[6903]: child process [6905] exited or timed out without signaling production of a PID file: exit 255 at /us Dec 29 16:40:12 linux-wulv systemd[1]: Failed to start Daemonized version of spamassassin. -- Subject: Unit spamd.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit spamd.service has failed. -- -- The result is failed. # rpm -q perl-Mail-SpamAssassin perl-Mail-SpamAssassin-3.4.0-44.1.3.x86_64 # rpm -q spamassassin spamassassin-3.4.0-44.1.3.x86_64 Solution: Running sa-update manually makes spamd start with '/etc/init.d/spamd restart'. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 950955] New: Error Messages from rtkit-daemon caused by CONFIG_RT_GROUP_SCHED
by bugzilla_noreply＠novell.com 04 Nov '19

04 Nov '19

http://bugzilla.opensuse.org/show_bug.cgi?id=950955 Bug ID: 950955 Summary: Error Messages from rtkit-daemon caused by CONFIG_RT_GROUP_SCHED Classification: openSUSE Product: openSUSE Factory Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Jan.Hebler(a)Kabeldeutschland.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- rtkit-daemon produces the following Error-Messages: ... Okt 19 07:06:19 tablette rtkit-daemon[3051]: Failed to make ourselves RT: Operation not permitted ... If i understand Lennart Poettering here https://bugzilla.redhat.com/show_bug.cgi?id=1229700 correct, the Kernel-Option CONFIG_RT_GROUP_SCHED should turned off. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 941758] New: grub-once isn't called at hibernate
by bugzilla_noreply＠novell.com 22 Oct '19

22 Oct '19

http://bugzilla.opensuse.org/show_bug.cgi?id=941758 Bug ID: 941758 Summary: grub-once isn't called at hibernate Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: tiwai(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since the recent change of systemd, grub-once isn't called any longer, thus at thawing, the normal GRUB menu is shown instead of the direct boot to the target kernel. The regression was introduced in openSUSE:Factory/systemd changeset 215: Wed Feb 18 05:01:38 UTC 2015 - crrodriguez(a)opensuse.org .... - systemd-sleep-grub: moved to the grub2 package where it belongs as a suspend/resume hook (SR#286533) (drops prepare-suspend-to-disk.patch) However, SR#286533 was declined and it's lost since then. The fix would be either revert the change in systemd or put the hook properly into grub2 package. The latter method has a potential bug, however. systemd-sleep doesn't call hooks to restore when writing to /sys/power/state fails. That is, if we have a hook to set up grubenv, it'll left when the hibernation fails, and the next boot would go wrong. This didn't happen in the past because it invoked the grubenv setup in a different manner. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 939248] New: gnome-shell not having correct SSH_AUTH_SOCK variable
by bugzilla_noreply＠novell.com 20 Oct '19

20 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=939248 Bug ID: 939248 Summary: gnome-shell not having correct SSH_AUTH_SOCK variable Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: vuntz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Any process that I start through gnome-shell seems to have a SSH_AUTH_SOCK matching a ssh-agent process (probably started through the X11 session scripts). However, if I start a process through gnome-settings-daemon (like a terminal, through the shortcurt for that), it has SSH_AUTH_SOCK set to the path for gnome-keyring. The result is that any app I start through gnome-shell actually has, by default, not access to my ssh keys :/ (also, I thought I had fixed a long time ago the bit starting ssh-agent on gnome sessions -- this shouldn't happen because of the keyring) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 939153] New: Thunderbird 38: Integrated Lightning calendar is not properly localized
by bugzilla_noreply＠novell.com 27 Sep '19

27 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=939153 Bug ID: 939153 Summary: Thunderbird 38: Integrated Lightning calendar is not properly localized Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Translations Assignee: ke(a)suse.com Reporter: lashkevi(a)landau.ac.ru QA Contact: ke(a)suse.com Found By: --- Blocker: --- Created attachment 641749 --> http://bugzilla.opensuse.org/attachment.cgi?id=641749&action=edit Snapshot for a fresh profile. Integrated Lightning in the Thundebird 38.1.0 from the last official update is not localized. Its whole UI is in English. Versions: MozillaThunderbird-38.1.0-70.57.1.x86_64 MozillaThunderbird-translations-common-38.1.0-70.57.1.x86_64 Steps to reproduce: 1. Update TB to 38.1. It removes the Lightning add-on substituting it by its integrated version as well as I understand. 2. Start TB in Russian (LANG=ru_RU.UTF-8 LANGUAGE=ru) locale. Actual results: Calendar (Lightning) menu items, config options and the whole UI is in English. Expected results: Calendar (Lightning) menu items, config options and UI should be in Russian. The issue is corrected after installing Lightning from a file (lightning-4.0.1-sm+tb-linux.xpi). But such workaround must make thundebird use more memory. The vanilla Russian version <https://download.mozilla.org/?product=thunderbird-38.1.0&os=linux64&lang=ru> does not show this issue, so that it is a problem of the OpenSUSE build. -- You are receiving this mail because: You are on the CC list for the bug.

1 35