July 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1029961] New: [META] Finalize /bin -> /usr/bin merge
by bugzilla_noreply＠novell.com 03 Jan '23

03 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1029961 Bug ID: 1029961 Summary: [META] Finalize /bin -> /usr/bin merge Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: daniel.molkentin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Some packages still install files to /bin that are not symlinks. A "find /bin -type f -exec rpm -qf {} \; | sort -u" on a recent TW yields: bash-4.4-95.1.x86_64 dbus-1-1.10.16-1.1.x86_64 keyutils-1.5.9-5.33.x86_64 ksh-93v-6.15.x86_64 net-tools-deprecated-1.60-770.1.x86_64 procps-3.3.12-3.1.x86_64 psmisc-22.21-6.9.x86_64 rpm-4.13.0.1-1.1.x86_64 sash-3.8-2.8.x86_64 sysvinit-tools-2.88+-103.1.x86_64 tar-1.29-3.1.x86_64 tcsh-6.20.00-3.1.x86_64 util-linux-2.29.1-1.1.x86_64 vim-8.0.324-2.1.x86_64 These packages should all install their binaries to %_bindir, i.e. /usr/bin, and have a symlink in /bin. This would finalize the /bin deprecation. I am opening bugs for each of the packages. Once they are all closed, I'll close this one. -- You are receiving this mail because: You are on the CC list for the bug.

2 67

[Bug 944832] New: installing updates during shutdown causes reboot
by bugzilla_noreply＠novell.com 22 Dec '22

22 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=944832 Bug ID: 944832 Summary: installing updates during shutdown causes reboot Classification: openSUSE Product: openSUSE Distribution Version: 42.1 Milestone 2 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- fresh leap milestone 2. I switched from the iso install source to the online oss repo. This repo had a few differend packages compared to the iso. The gnome software installer recognized them as updates. Once I had to shutdown the system it offered a knob to install pending updates, then shutdown. I enabled that box, and hit return. I think nothing was downloaded, but the box did a reboot instead of the expected shutdown. If that feature is not ready yet I suggest to hide it for the time being to really and always do a reliable powerdown if that was requested. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1024727] New: Cannot login to Bugzilla using Bugzilla "login" button
by bugzilla_noreply＠novell.com 04 Dec '22

04 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1024727 Bug ID: 1024727 Summary: Cannot login to Bugzilla using Bugzilla "login" button Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bugzilla Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: qantas94heavy(a)gmail.com QA Contact: novbugzilla-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Created attachment 713674 --> http://bugzilla.opensuse.org/attachment.cgi?id=713674&action=edit Unprocessed PHP file I attempted to login to Bugzilla by clicking the "Login" button on the Bugzilla home page, which took me to the following URL: https://login.microfocus.com/nidp/idff/sso?id=132&sid=5&option=credential&s… Instead of receiving the page as usual, it appears to load some scripts from the following URL: https://www.suse.com/common/inc/include.php?file=headers/hdr_head.html The PHP file there appears to be unprocessed, which is most likely causing the issue here. I was only able to login by going through the openSUSE wiki then going back to Bugzilla. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1047225] New: LUKS password doesn't show up when booting with nomodeset
by bugzilla_noreply＠novell.com 30 Nov '22

30 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1047225 Bug ID: 1047225 Summary: LUKS password doesn't show up when booting with nomodeset Classification: openSUSE Product: openSUSE Tumbleweed Version: Current 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: --- Install a TW system with the standard procedure for LVM+encrpption as suggested by installer on KVM. It works fine with the graphical LUKS password. But when you boot with nomodeset boot option, the boot process hangs without asking the LUKS password. This didn't happen on openSUSE Leap 42.2 / 42.3. And when I upgrade only plymouth packages on the Leap system, it starts showing the same problem. So, it's a regression in the recent plymouth package. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1029190] New: Support for package variants according to the evaluation of bigger regular expressions
by bugzilla_noreply＠novell.com 24 Nov '22

24 Nov '22

http://bugzilla.suse.com/show_bug.cgi?id=1029190 Bug ID: 1029190 Summary: Support for package variants according to the evaluation of bigger regular expressions Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: All Status: NEW Severity: Enhancement Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Markus.Elfring(a)web.de QA Contact: qa-bugs(a)suse.de CC: astieger(a)suse.com Found By: --- Blocker: --- I noticed that the parameter “--with-link-size=2” is used so far in a package specification. https://build.opensuse.org/package/view_file/openSUSE:Factory/pcre2/pcre2.s… This setting limits the size of regular expressions. I would like to work with bigger search patterns occasionally. So I suggest to generate also variants for this software with an internal link size of 3 (and 4) for the data processing with 8 and 16 bit characters. See also: Selection of system properties for the regular expressions engine at run time https://bugs.exim.org/show_bug.cgi?id=1922 By the way: How do you think about to use the specifications “LDFLAGS“ und “%{?_smp_mflags}“ as parameters for the script “%configure“ there? -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 987114] New: Bluetooth headset connected but not showing under 'Sound Settings'
by bugzilla_noreply＠novell.com 16 Nov '22

16 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=987114 Bug ID: 987114 Summary: Bluetooth headset connected but not showing under 'Sound Settings' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: damien.lloyd21(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0 Build Identifier: On openSUSE Tumbleweed, my bluetooth headset pairs and connects successfully through GNOME's bluetooth interface, but after going to the 'Sound Settings' my bluetooth headset doesn't show up, even though it is paired up. Because I can't see my bluetooth headset under 'Sound Settings' it's not possible to re-route sound through it, which means I can't use my bluetooth headset. Reproducible: Always Steps to Reproduce: 1. Make bluetooth headset discoverable; 2. Open up GNOME's bluetooth interface and select bluetooth headset; 3. Connect to bluetooth headset; 4. Once paired, access 'Sound Settings': bluetooth headset doesn't show up. Actual Results: The bluetooth headset doesn't show up under 'Sound Settings' even though it is connected and paired. Expected Results: The bluetooth headset should appear under 'Sound Settings' so that sound can be re-routed through it. My headset is a UE MEGABOOM and it worked under Ubuntu 14.04/16.04 extremely well. It doesn't work under openSUSE Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1028824] New: aide looking for a removed algorithm
by bugzilla_noreply＠novell.com 09 Nov '22

09 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1028824 Bug ID: 1028824 Summary: aide looking for a removed algorithm Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Upgrade Problems Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: tschaefer(a)t-online.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- After starting: aide -i comes the following notice: DBG: md_enable: algorithm 7 not available -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1031134] New: Since upgrade to GNOME 3.24 [TW 20170322] gnome-shell crashes and reloads often
by bugzilla_noreply＠novell.com 05 Nov '22

05 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1031134 Bug ID: 1031134 Summary: Since upgrade to GNOME 3.24 [TW 20170322] gnome-shell crashes and reloads often Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: badshah400(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since the upgrade to TW 201703022 which brought GNOME 3.24 (actually I also saw this while using the beta GNOME 3.23.9x version from GNOME:Next repository), gnome-shell seems to crash and reload every now and then (no specific process to trigger this specifically that I could find). This is nothing more than an annoyance, since the reload works just fine, so the only effect is that the application windows get rordered thereafter. I see messages like these on the journal: Mar 27 16:06:52 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/main.js 317]: reference to undefined property global.stage Mar 27 16:06:52 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 217]: reference to undefined property global.window_group Mar 27 16:06:52 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 899]: reference to undefined property this.monitors[this.findIndexForAct Mar 27 16:06:52 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to undefined property Meta.MonitorManager Mar 27 16:06:52 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/panel.js 1107]: reference to undefined property indicator.menu._openChangedId Mar 27 16:06:52 tp-yoga260 org.gnome.Shell.desktop[17371]: current session already has an ibus-daemon. Mar 27 16:06:52 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/slider.js 34]: reference to undefined property St.GenericAccessible Mar 27 16:06:52 tp-yoga260 polkitd[1043]: Registered Authentication Agent for unix-session:2 (system bus name :1.335 [/usr/bin/gnome-shell], object path /org/freedesktop/Pol Mar 27 16:06:52 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/gjs/modules/tweener/tweener.js 538]: reference to undefined property properties[istr].array Mar 27 16:06:52 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/search.js 432]: reference to undefined property provider.isRemoteProvider Mar 27 16:06:52 tp-yoga260 gnome-shell[17371]: Failed to add search provider /usr/share/gnome-shell/search-providers/org.gnome.bijiben-search-provider.ini: TypeError: appInf Mar 27 16:06:52 tp-yoga260 dbus[988]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' Mar 27 16:06:52 tp-yoga260 systemd[1]: Starting PackageKit Daemon... Mar 27 16:06:52 tp-yoga260 PackageKit[17397]: daemon start Mar 27 16:06:52 tp-yoga260 dbus[988]: [system] Successfully activated service 'org.freedesktop.PackageKit' Mar 27 16:06:52 tp-yoga260 systemd[1]: Started PackageKit Daemon. Mar 27 16:06:53 tp-yoga260 /usr/lib/gdm/gdm-x-session[2581]: (II) modeset(0): EDID vendor "CMN", prod id 4665 Mar 27 16:06:53 tp-yoga260 /usr/lib/gdm/gdm-x-session[2581]: (II) modeset(0): Printing DDC gathered Modelines: Mar 27 16:06:53 tp-yoga260 /usr/lib/gdm/gdm-x-session[2581]: (II) modeset(0): Modeline "1920x1080"x0.0 138.78 1920 1966 1996 2080 1080 1082 1086 1112 +hsync -vsync (66.7 Mar 27 16:06:53 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/misc/ibusManager.js 200]: reference to undefined property this._engines[id] Mar 27 16:06:53 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/messageList.js 353]: reference to undefined property this._useBodyMarkup Mar 27 16:06:53 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/messageList.js 386]: reference to undefined property this._useBodyMarkup Mar 27 16:06:53 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/messageList.js 169]: reference to undefined property this._container Mar 27 16:06:53 tp-yoga260 gnome-shell[17371]: nma_mobile_providers_database_lookup_cdma_sid: assertion 'sid > 0' failed Mar 27 16:06:53 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1885]: reference to undefined property this._mainConnectionState Mar 27 16:06:54 tp-yoga260 gnome-shell[17371]: GNOME Shell started at Mon Mar 27 2017 16:06:52 GMT+0200 (CEST) Mar 27 16:07:06 tp-yoga260 gnome-terminal-[17266]: Allocating size to GtkScrollbar 0xb06500 without calling gtk_widget_get_preferred_width/height(). How does the code know t Mar 27 16:07:09 tp-yoga260 kernel: SFW2-INext-DROP-DEFLT IN=wlp4s0 OUT= MAC=33:33:00:00:00:fb:a8:81:95:7d:ba:78:86:dd SRC=fe80:0000:0000:0000:aa81:95ff:fe7d:ba78 DST=ff02:00 Mar 27 16:07:13 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/dash.js 760]: reference to undefined property oldApps[oldIndex] Mar 27 16:07:13 tp-yoga260 PackageKit[17397]: daemon quit Mar 27 16:07:13 tp-yoga260 packagekitd[17397]: Source ID 10 was not found when attempting to remove it Mar 27 16:07:13 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/appDisplay.js 1298]: reference to undefined property this.name Mar 27 16:07:20 tp-yoga260 sudo[17463]: badshah400 : TTY=pts/1 ; PWD=/home/badshah400 ; USER=root ; COMMAND=/usr/bin/journalctl -b log Mar 27 16:07:20 tp-yoga260 sudo[17463]: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 27 16:07:20 tp-yoga260 sudo[17463]: pam_systemd(sudo:session): Cannot create session: Already occupied by a session Mar 27 16:07:20 tp-yoga260 sudo[17463]: pam_unix(sudo:session): session closed for user root Mar 27 16:07:24 tp-yoga260 sudo[17469]: badshah400 : TTY=pts/1 ; PWD=/home/badshah400 ; USER=root ; COMMAND=/usr/bin/journalctl -b Mar 27 16:07:24 tp-yoga260 sudo[17469]: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 27 16:07:24 tp-yoga260 sudo[17469]: pam_systemd(sudo:session): Cannot create session: Already occupied by a session -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1051356] New: Epiphany and therefore gnome-shell's portal checking fail with TLS handshake failure
by bugzilla_noreply＠novell.com 05 Nov '22

05 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1051356 Bug ID: 1051356 Summary: Epiphany and therefore gnome-shell's portal checking fail with TLS handshake failure Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: badshah400(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- While connecting to a portal network, epiphany fails with the following error The precise error was: Error performing TLS handshake: Could not negotiate a supported cipher suite. Because epiphany fails, so does gnome-shell's portal checking window, which launches immediately upon detecting a portal network but promptly shows the same message with no way to load the portal login page. Firefox, on the other hand, goes ahead and loads the portal login page on the same network. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1006958] New: gdb build often stalls on OBS
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1006958 Bug ID: 1006958 Summary: gdb build often stalls on OBS Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- gdb is among the list of packages that often cause a stall in OBS - OBS detects this after a while and cancels the build. The issue though is that unreliable builds are a pain and must not happen (especially when being a ring package; it is built very often in the stagings and every fail requires the staging managers to interact) The current fail I have here stops with: <[ 6299s] Running target unix/-m32/-fPIC/-pie >[ 6299s] Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. >[ 6299s] Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. >[ 6299s] Using /home/abuild/rpmbuild/BUILD/gdb-7.11.1/gdb/testsuite/config/unix.exp as tool-and-target-specific interface file. >[ 6299s] Running /home/abuild/rpmbuild/BUILD/gdb-7.11.1/gdb/testsuite/gdb.xml/tdesc-arch.exp ... >[ 6299s] /home/abuild/rpmbuild/BUILD/gdb-7.11.1/build-x86_64-suse-linux/gdb/gdb version 7.11.1 -nw -nx -data-directory /home/abuild/rpmbuild/BUILD/gdb-7.11.1/build-x86_64-suse-linux/gdb/testsuite.unix.-m32.-fPIC.-pie/../data-directory >[ 6299s] >[ 6299s] >[ 6299s] === gdb Summary === >[ 6299s] >[ 6299s] # of expected passes 8 >[ 6300s] /home/abuild/rpmbuild/BUILD/gdb-7.11.1/build-x86_64-suse-linux/gdb/gdb version 7.11.1 -nw -nx -data-directory /home/abuild/rpmbuild/BUILD/gdb-7.11.1/build-x86_64-suse-linux/gdb/testsuite.unix.-m32.-fPIC.-pie/../data-directory >[ 6300s] >[35104s] ### WATCHDOG MARKER END ### >[35104s] No buildstatus set, either the base system is broken (kernel/initrd/udev/glibc/bash/perl) >[35104s] or the build host has a kernel or hardware problem... > > >Job seems to be stuck here, killed. (after 28800 seconds of inactivity) -- You are receiving this mail because: You are on the CC list for the bug.

2 2