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=1105268
Bug ID: 1105268
Summary: Wayland: Screen rotation to left or right gives blank
screen from second attempt onward
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: X.Org
Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com
Reporter: badshah400(a)gmail.com
QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com
Found By: ---
Blocker: ---
GNOME 3.28.2 on Wayland
Rotating the screen to the left or right from its default orientation works the
first time, but gives a blank screen thereafter, with the following log
recorded on the journal:
Aug 18 03:08:41 kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic
update failure on pipe A (start=140995 end=140996) time 1818 us, min 1907, max
1919, scanline start 1870, end 89
Aug 18 03:08:42 gsd-color[4609]: failed to set screen _ICC_PROFILE: Failed to
open file
“/home/badshah/.local/share/icc/edid-400eada130818d341c3ea2fa3de67f03.icc”:
Permission denied
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:43 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:43 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:43 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:43 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:43 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:44 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:44 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:44 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:44 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:44 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:44 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:45 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:45 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:45 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:45 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:45 gnome-shell[4401]: Failed to read EDID from 'eDP-1': No such
file or directory
Aug 18 03:08:45 gnome-shell[4401]: Failed to read EDID from 'eDP-1': No such
file or directory
Aug 18 03:08:45 gnome-shell[4401]: Failed to read EDID from 'eDP-1': No such
file or directory
Aug 18 03:08:45 gsd-color[4609]: failed to set screen _ICC_PROFILE: Failed to
open file
“/home/badshah/.local/share/icc/edid-400eada130818d341c3ea2fa3de67f03.icc”:
Permission denied
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1116034
Bug ID: 1116034
Summary: Please convert SysV init scripts by safte-monitor into
native systemd services
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: fbui(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
It would be great if the SysV init scrips shipped by this package could
be converted into systemd native services.
Indeed most packages shipped by openSUSE Factory switched to native
systemd unit files years ago and we plan to drop the obsolete/limited
SysV compat support in the future.
If this appears to be a big task, one quick way to solve it is to copy
and ship (as is) the .service unit wrappers generated automatically by
systemd-sysv-generator at boot. Indeed such wrappers are generated by
systemd in order to support SysV init scripts similarly to native
units.
You can see the content of a wrapper unit with:
$ systemctl cat <sysvinit-script>.service
As you could see the wrapper unit simply calls the SysV script, which
should be moved out of /etc/init.d, probably in a directory owned by
your package.
In all cases we would be glad to provide any help if needed in this
task.
Thanks in advance.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1095671
Bug ID: 1095671
Summary: sg3_utils: sg_turs command in Leap broken
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.0
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: dmarkh(a)cfl.rr.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
I have this little script that shows my problem.
#!/bin/bash
sg_turs /dev/sr0 > /dev/null
RDY=$?
echo "RDY = ${RDY}"
This script always says the sg_turs commands exit status is 0. Even with the
door open and no disk installed.
The man page for the sg_turs command says:
EXIT STATUS
The exit status of sg_turs is 0 when it is successful (e.g. in the case
of a mechanical disk, it is spun up and ready to accept commands). For this
utility the other exit status of interest is 2 corresponding to the "not
ready" sense key. For other exit status values see the sg3_utils(8) man page.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1118099
Bug ID: 1118099
Summary: aws-cli-1.16.48-1.1.noarch requires python3-colorama
<= 0.3.9, but this requirement cannot be provided
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Cloud:Tools
Assignee: public-cloud-maintainers(a)suse.de
Reporter: rombert(a)apache.org
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
It seems that the aws-cli / python3-colorama dance is up again :-)
Problem: aws-cli-1.16.48-1.1.noarch requires python3-colorama <= 0.3.9, but
this requirement cannot be provided
deleted providers: python3-colorama-0.3.9-1.3.noarch
Solution 1: deinstallation of aws-cli-1.16.48-1.1.noarch
Solution 2: keep obsolete python3-colorama-0.3.9-1.3.noarch
Solution 3: break aws-cli-1.16.48-1.1.noarch by ignoring some of its
dependencies
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1101785
Bug ID: 1101785
Summary: rubygem-mysql2 update to 0.5 broke velum
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Ruby
Assignee: ruby-devel(a)suse.de
Reporter: dimstar(a)opensuse.org
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
The package rubygem-mysql2 has been updated to version 0.5; this in turned made
velum unresolvable (and uninstallable)
Velum seems, as far as I saw on quick glance, to be the only consumer of
rubygem-mysql2
--
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.