June 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1095169] Packaged Syncthing binary attempts to update itself
by bugzilla_noreply＠novell.com 01 Jun '18

01 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=1095169 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|obs:running:8200:low |obs:running:8200:moderate -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1095652] New: Install media freezes on boot
by bugzilla_noreply＠novell.com 01 Jun '18

01 Jun '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1095652 Bug ID: 1095652 Summary: Install media freezes on boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: sionescu(a)cddr.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 772193 --> http://bugzilla.opensuse.org/attachment.cgi?id=772193&action=edit Screenshot Both the netinstall and the full image fails to boot from a USB dongle. The boot process freezes after a few seconds. The hardware is a Lenovo P50 laptop, CPU Intel(R) Xeon(R) CPU E3-1505M v5 @ 2.80GHz, and secure boot enabled (UEFI-only). The attached screenshot was taken after attempting to boot without splash=silent and with "debug initcall_debug". -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1094751] New: Blank screen after Xorg shutdown on Intel GPU after upgrade to Leap 15.0
by bugzilla_noreply＠novell.com 01 Jun '18

01 Jun '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1094751 Bug ID: 1094751 Summary: Blank screen after Xorg shutdown on Intel GPU after upgrade to Leap 15.0 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: srid(a)rkmail.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I've upgraded openSUSE Leap 42.3 to 15.0 on my laptop. After the upgrade, if I choose to shut down Plasma session either with logout command or by killing XOrg, the screen goes dark and computer stops responding keyboard commands. I use 'modesetting' xorg driver. If I install the xf86-video-intel driver, the screen goes dark even before that, while logging into KDE. The GPU is 2nd gen sandybridge. I'm not sure what other info I can provide. It's possible to ssh into computer while the screen is dark. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1095607] New: server:messaging/telegram-desktop: Bug
by bugzilla_noreply＠novell.com 01 Jun '18

01 Jun '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1095607 Bug ID: 1095607 Summary: server:messaging/telegram-desktop: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: nix(a)opensuse.org Reporter: eduardo.querido(a)gmail.com QA Contact: bnc-team-screening(a)forge.provo.novell.com Found By: --- Blocker: --- du@Cammy:~> telegram-desktop QApplication: invalid style override passed, ignoring it. (telegram-desktop:4432): GLib-GObject-WARNING **: 08:27:20.510: cannot register existing type 'GdkDisplayManager' (telegram-desktop:4432): GLib-CRITICAL **: 08:27:20.510: g_once_init_leave: assertion 'result != 0' failed (telegram-desktop:4432): GLib-GObject-CRITICAL **: 08:27:20.510: g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT (object_type)' failed I simply can't run the program thru the command line and the GUI is not working either. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1095425] The ICU library ignores the users locale setting
by bugzilla_noreply＠novell.com 01 Jun '18

01 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=1095425 http://bugzilla.suse.com/show_bug.cgi?id=1095425#c2 --- Comment #2 from Lothar Paltins <lopa(a)mailbox.org> --- But the current behavior is the big change. Until now, KDE and QT respected the setting of the env variables LANG or LC_CTYPE. This has changed since one of the last OpenSuse Tumbleweed updates. Now a hard coded character encoding is assumed and the users environment setting is ignored. I've also filed a bug against QT, because I thought, that this is a QT issue before I found out, that it's caused by ICU. And the QT maintainer said, that on his system, ICU still uses the environment setting and not a harcoded value. Here's an excerpt from the readme.html file in the icu-61.1 package: Hardcode the default charset to UTF-8: On platforms where the default charset is always UTF-8, like MacOS X and some Linux distributions, we recommend hardcoding ICU's default charset to UTF-8. This means that some implementation code becomes simpler and faster, and statically linked ICU libraries become smaller. (See the U_CHARSET_IS_UTF8 API documentation for more details.) The hardcoding is only a recommendation. The question is, does Suse really want to give up the freedom of choice of character encodings? I would expect such an attitude from Microsoft and Apple, but not from a Linux distribution. I have compiled the Suse icu-61.1-1.1 package with U_CHARSET_IS_UTF8=0 without problems and with all regression tests passing. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1092017] MicroSD card reader not recognized
by bugzilla_noreply＠novell.com 01 Jun '18

01 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=1092017 http://bugzilla.suse.com/show_bug.cgi?id=1092017#c14 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(r.cabane(a)free.fr) --- Comment #14 from Takashi Iwai <tiwai(a)suse.com> --- The KMP is being rebuilt now with a debug patch. Once after the build finishes, please reinstall KMP. At best, uninstall the old package and install the new one, to be sure. Then boot with ampesd.verbose=9 option, and see any relevant messages. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1092017] MicroSD card reader not recognized
by bugzilla_noreply＠novell.com 01 Jun '18

01 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=1092017 http://bugzilla.suse.com/show_bug.cgi?id=1092017#c13 --- Comment #13 from Robert Cabane <r.cabane(a)free.fr> --- Created attachment 772178 --> http://bugzilla.suse.com/attachment.cgi?id=772178&action=edit Output of dmesg I launched dmesg. The insertion or extraction of a micro-sd card has strictly no effect on the dmesg output. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1095096] Leap 42.3: update broke boot with encrypted partitions on NVMe
by bugzilla_noreply＠novell.com 01 Jun '18

01 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=1095096 http://bugzilla.suse.com/show_bug.cgi?id=1095096#c15 --- Comment #15 from Dariusz Ostolski <dariusz.ostolski(a)gmail.com> --- Unfortunately I don't have any previous fs snapshots(not using btrfs). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1092017] MicroSD card reader not recognized
by bugzilla_noreply＠novell.com 01 Jun '18

01 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=1092017 http://bugzilla.suse.com/show_bug.cgi?id=1092017#c12 --- Comment #12 from Takashi Iwai <tiwai(a)suse.com> --- OK, at least, it's a not bad start, it doesn't crash :) Please give the dmesg output after inserting / removing the SD card. (And the device should be not /dev/sd* but /dev/mmc0p* or such, in anyway.) I'll put some debug prints to track more deeply. Stay tuned. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1095631] New: Console logging stops after "Switching root."
by bugzilla_noreply＠novell.com 01 Jun '18

01 Jun '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1095631 Bug ID: 1095631 Summary: Console logging stops after "Switching root." Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: openSUSE 42.3 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: smartinds(a)gmail.com QA Contact: qa-bugs(a)suse.de CC: Ulrich.Windl(a)rz.uni-regensburg.de Depends on: 1076887 Found By: --- Blocker: --- Created attachment 772176 --> http://bugzilla.opensuse.org/attachment.cgi?id=772176&action=edit /var/log/boot.log In openSUSE Leap 15.0 (net install) without D.E (Only for server). [0m] Started Cleanup udevd DB. [0m] Started Setup Virtual Console. [0m] Reached target Switch Root. Starting Switch Root... [0m] A start job is running for Flush Journal to Persistent Storage (8s / 1min 30s) [0m] A start job is running for Flush Journal to Persistent Storage (9s / 1min 30s) ... ... (wait, wait, wait, many times) [0m] Failed to start Flush Journal to Persistent Storage. See 'systemctl status systemd-journal-flush.service' for details. # systemctl status systemd-journal-flush.service ● systemd-journal-flush.service - Flush Journal to Persistent Storage Loaded: loaded (/usr/lib/systemd/system/systemd-journal-flush.service; static; vendor preset: disabled) Active: failed (Result: timeout) since Fri 2018-06-01 13:51:18 -05; 17min ago Docs: man:systemd-journald.service(8) man:journald.conf(5) Main PID: 416 (code=killed, signal=TERM) jun 01 13:49:48 lime systemd[1]: Starting Flush Journal to Persistent Storage... jun 01 13:51:18 lime systemd[1]: systemd-journal-flush.service: Start operation timed out. Terminating. jun 01 13:51:18 lime systemd[1]: systemd-journal-flush.service: Main process exited, code=killed, status=15/TERM jun 01 13:51:18 lime systemd[1]: Failed to start Flush Journal to Persistent Storage. jun 01 13:51:18 lime systemd[1]: systemd-journal-flush.service: Unit entered failed state. jun 01 13:51:18 lime systemd[1]: systemd-journal-flush.service: Failed with result 'timeout'. I attach the /var/log/boot.log +++ This bug was initially created as a clone of Bug #1076887 +++ This bug is somewhat newly introduced with 42.3: When pressing ESC during boot, systemd messages fly by, but then stop with "Starting Switch Root...". There is a log pause with no output, and the next thing is that the X-cursor appears (meaning that the graphical display has started already) systemd-228-38.1.x86_64 kernel-default-4.4.103-36.1.x86_64 plymouth-0.9.2-6.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 0