http://bugzilla.opensuse.org/show_bug.cgi?id=1023734
Bug ID: 1023734
Summary: openSUSE:Factory/golang-org-x-oauth2 fails to build
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: ---
The package golang-org-x-oauth2 fails to build in openSUSE:Factory. Earlier
notifications by email to the bugowner and Maintainer have remained without
reaction / fix. If the package is not being fixed within 2 weeks, it will be
scheduled for removal from Tumbleweed
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=971006
Bug ID: 971006
Summary: rpmlint: no-dependency-on perl-base 5.22.1
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: 2015*
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: ---
rpmlint does not understand how openSUSE specifies perl dependencies and falsly
reports:
no-dependency-on perl-base 5.22.1
in openSUSE, we use the macro
%perl_requires
which translates to:
Requires: perl(:MODULE_COMPAT_5.22.1)
It would be great to get this recognized as dependency being satisfied
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
Bug ID: 1041742
Summary: Filetriggers do not fire (reliably)
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: libzypp
Assignee: zypp-maintainers(a)forge.provo.novell.com
Reporter: dimstar(a)opensuse.org
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
In GNOME:Next, we started experimenting with file triggers (with the goal to
lower the number of bugs based on missing post scripts)
As a sample, I implemented this trigger (on glib2-tools):
%transfiletriggerin -n glib2-tools -- %{_datadir}/glib-2.0/schemas
%{_bindir}/glib-compile-schemas %{_datadir}/glib-2.0/schemas
%transfiletriggerpostun -n glib2-tools -- %{_datadir}/glib-2.0/schemas
%{_bindir}/glib-compile-schemas %{_datadir}/glib-2.0/schemas
The trigger is confirmed to work, but in some cases, it seems not to fire, eg
on the package 'gdm'
(which is currently the reason why
http://download.opensuse.org/repositories/GNOME:/Medias/images/iso/?P=GNOME…
fails to boot to desktop)
zypper in --no-recommends gdm => the file trigger is not executed
rpm -i gdm-3.24.1.rpm => the trigger actually seems to work (which is
why I file it against libzypp)
This currently stops us from moving forward and proposing file triggers to be
more widely used (even though I think they can solve quite some packaging bugs)
The packages in question for testing are all in the GNOME:Next repository
(glib2 which has the trigger, it has the %glib2_gsettings_schema_post set to
%nil, so packages that use it in their post script only get a dummy - once the
implementation is complete, we will of course go and clean those out
completely)
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1093168
Bug ID: 1093168
Summary: pacemaker: using service template in preun/postun
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: High Availability
Assignee: ha-bugs(a)suse.de
Reporter: ro(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
you can not used a service template (foo@.service) without parameter
in a specfile with the %service_add/del macros:
%preun cts
%service_del_preun pacemaker-cts-dummyd@.service
%postun cts
%service_del_postun pacemaker-cts-dummyd@.service
this will just result in errors during uninstall
of the package:
(1/1) Removing pacemaker-cts-1.1.18+20180430.b12c320f5-1.4.noarch
........[done]
Additional rpm output:
Failed to stop pacemaker-cts-dummyd@.service: Unit name
pacemaker-cts-dummyd@.service is missing the instance name.
See system logs and 'systemctl status pacemaker-cts-dummyd@.service' for
details.
Failed to get load state of pacemaker-cts-dummyd@.service: Unit name
pacemaker-cts-dummyd@.service is neither a valid invocation ID nor unit name.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1088177
Bug ID: 1088177
Summary: Default Active Titlebar color on openSUSEdark and
openSUSEdarkalternate colorchemes
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Enhancement
Priority: P5 - None
Component: KDE Workspace (Plasma)
Assignee: opensuse-kde-bugs(a)opensuse.org
Reporter: andretiago(a)outlook.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 766009
--> http://bugzilla.suse.com/attachment.cgi?id=766009&action=edit
Titlebar active color
Default Active Titlebar color of openSUSEdark and openSUSEdarkalternate color
schemes looks out of place and it's hard to read.
https://i.imgur.com/vshYSxz.png
I think the default color should be replaced
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1008674
Bug ID: 1008674
Summary: Login difficulties with LightDM 1.20
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: SUSE Other
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Basesystem
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: Markus.Elfring(a)web.de
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Today I dared to update the display manager to the version “LightDM
1.20.0-1.1”.
Unfortunately, I observed that the corresponding graphical login did not work
as expected. The information “exist status: 1” was recorded in the systemd
journal.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1029919
Bug ID: 1029919
Summary: zypper crashes when baseurl does not contain
http/https
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: libzypp
Assignee: zypp-maintainers(a)forge.provo.novell.com
Reporter: wattersm(a)watters.ws
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
zypper crashes when a repo file is missing the protocol in the download URL.
For example, the following repo file causes zypper to crash.
[home_Ximi1970_openSUSE_Extra]
baseurl=download.opensuse.org/repositories/home:/Ximi1970:/openSUSE:/Extra/…
enabled=1
gpgcheck=1
gpgkey=download.opensuse.org/repositories/home:/Ximi1970:/openSUSE:/Extra/o…
priority=99
autorefresh=1
keeppackages=1
type=rpm-md
Running any zypper command results in a crash as follows.
linux-0yvh:~ # zypper search bacula
Unexpected exception.
Url scheme is a required component
Please file a bug report about this.
See http://en.opensuse.org/Zypper/Troubleshooting for instructions
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=920901
Bug ID: 920901
Summary: USB mouse disconnects every 60 seconds without X
Classification: openSUSE
Product: openSUSE 13.1
Version: Final
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-maintainers(a)forge.provo.novell.com
Reporter: oneukum(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Some mice need X to run or will disconnects and reconnect every 60 seconds. The
fix is a new quirk to always poll.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1062518
Bug ID: 1062518
Summary: x2gothinclient(d) is missing File/Path/Expand.pm perl
module
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: openSUSE Factory
Status: NEW
Severity: Normal
Priority: P5 - None
Component: X11 3rd Party Driver
Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com
Reporter: werner(a)suse.com
QA Contact: sndirsch(a)suse.com
Found By: ---
Blocker: ---
Starting x2gothinclientd cause the message
Can't locate File/Path/Expand.pm in @INC (you may need to install the
File::Path::Expand module) (@INC contains:
/usr/lib/perl5/site_perl/5.26.1/x86_64-linux-thread-multi
/usr/lib/perl5/site_perl/5.26.1
/usr/lib/perl5/vendor_perl/5.26.1/x86_64-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.26.1
/usr/lib/perl5/5.26.1/x86_64-linux-thread-multi /usr/lib/perl5/5.26.1
/usr/lib/perl5/site_perl) at /usr/sbin/x2gothinclientd line 23.
AFAICS there is no such file below /usr/lib/perl5/ nor any provides of
'perl(File::Path::Expand)'
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1041794
Bug ID: 1041794
Summary: Recent update breaks some Youtube videos
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.2
Hardware: x86-64
OS: Linux
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: james.knott(a)rogers.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
An update around mid May caused some Youtube videos to fail. When this
happens, loading the video stops, leaving only the dot going around a circle
showing. This happens with Firefox, Seamonkey and Chromium browsers. The
videos that fail play OK in Windows. To verify the problem, I tried the videos
with a VirtualBox VM or a fresh 42.2 install. The problem videos played. I
then cloned the VM and ensured the videos played. I then updated the clone to
the latest updates and now the videos fail. The original non-updated VM still
continued to play the videos. It appears the problem is related to the type of
codec used. For example, videos with the vp9 codec play, but those with
avc1.4d400d now fail.
Here are 2 links, this one plays OK:
https://www.youtube.com/watch?v=Rzqq581Q3Us
But this one doesn't:
https://www.youtube.com/watch?v=t8tdmaEhMHE
Again, this problem occurred recently. Videos that played a few weeks ago now
fail.
--
You are receiving this mail because:
You are on the CC list for the bug.