http://bugzilla.suse.com/show_bug.cgi?id=1052740
Bug ID: 1052740
Summary: convert X keyboards into kbd and set unicode console
font for languages with non-Latin alphabets
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: All
OS: openSUSE Factory
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: opensuse.lietuviu.kalba(a)gmail.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Now openSUSE for languages with Latin alphabets use converted keyboard layouts
from X into kbd, also use unicode console font (as converted layouts supports
it).
Remaining task is to do same transition for non-Latin console keyboard layouts
and set appropriate console font. Perhaps we should preconfigure option to
switch between native and US QWERTY in console for these non-Latin languages
and keyboard layouts.
As noted in https://bugzilla.suse.com/show_bug.cgi?id=942896#c70 ,
As noted in https://bugzilla.suse.com/show_bug.cgi?id=942896#c69
Greek seems not have converted console keyboard layout from X into kbd.
For Greek perhaps we can use eurlatgr console font (like for Latin alphabets)
All Cyrillic layouts now use UniCyr_8x16.psf font, but this font seems to be
compatible with cp866, cp1251, iso8859-5 and koi8-r (according
http://www.tldp.org/HOWTO/Belarusian-HOWTO/x28.html) and not compatible with
unicode per se. But openSUSE seems don't provide converted layouts for Russian,
Ukrainian, Serbian, Bulgarian, Tajik.
For Cyrillic alphabets we should use LatArCyrHeb-14, LatArCyrHeb-16+ or
LatArCyrHeb-16 console font, that support unicode.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1082318
Bug ID: 1082318
Summary: Packages must not mark license files as %doc
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: All
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: fvogt(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Certain licenses require that license files must be shipped together with the
binaries in all cases.
By using the %doc marker, this is no longer guaranteed (e.g. by enabling
excludedocs).
Thus it is important that for such cases, %license is used instead of %doc.
The effect is that the file is always installed, stored in a different
directory (/usr/share/licenses/<pkg>/) and can be queried using rpm (e.g. "rpm
-qL kernel-firmware").
--
You are receiving this mail because:
You are on the CC list for the bug.
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.
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.
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.
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.
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.
http://bugzilla.opensuse.org/show_bug.cgi?id=993011
Bug ID: 993011
Summary: [openQA] CTRL-ALT-DEL does not show the logout dialog
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: KDE Workspace (Plasma)
Assignee: opensuse-kde-bugs(a)opensuse.org
Reporter: dimstar(a)opensuse.org
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Seen by openQA tests, e.g. https://openqa.opensuse.org/tests/239654
After the system was upgraded from openSUSE 13.2 to Tumbleweed (20160808, first
to have plasma 5.7.2), the logout dialog no longer shows when pressing
ctrl-alt-del
This appears on updates performed using the DVD and boot from the Network CD,
but seems not to happen in the case when the system was updated using zdup.
The tests had been re-run a couple times.
--
You are receiving this mail because:
You are on the CC list for the bug.