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.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.
http://bugzilla.suse.com/show_bug.cgi?id=993401
Bug ID: 993401
Summary: grub2-install for EFI installs an EFI entry that is
not bootable
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.1
Hardware: aarch64
OS: openSUSE 42.1
Status: NEW
Severity: Minor
Priority: P5 - None
Component: Bootloader
Assignee: jsrain(a)suse.com
Reporter: alan(a)softiron.co.uk
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
Running grub2-install does not yield a bootable entry in EFI's boot menu. On
Leap and Tumbleweed, this means booting relies instead on the startup.nsh in
the EFI partition.
This occurs on Aarch64 with both AMD/AMI firmware and
Tianocore/edk2/OpenPlatformPkg firmware.
Steps to reproduce:
1. Install Leap 42.1 from the OEM image
2. Restart and boot the system
2a. Observe that the startup.nsh (in the EFI partition) is used to boot the
system.
3. Reboot again, but During boot-up, enter the EFI menu.
3a. Observe that in the boot manager in the EFI menus, there is no entry for
Leap.
4. Restart the system or select the UEFI shell option, booting from startup.nsh
5. From the command prompt in Leap, run:
grub2-install /dev/sda
6. Reboot the system
7. During start-up enter the EFI menu.
7a. Observe that in the EFI menu there is an entry called
opensuse-leap42.1-arm-jeos-devel-efi, or something like it.
8. Select the opensuse-leap* boot menu item and try to boot it.
9. Observe that it does not boot, and returns to the boot menu.
10. Select the UEFI Shell option, and observe that it will boot using
startup.nsh.
11. From the Linux command prompt, run "efibootmgr -v"
11a. Observe that the entry for opensuse-leap* is truncated :(
11b. Note the same can be observed by running "dumpstore" from the EFI
environment.
Note: The same thing happens if the bootloader is re-installed using "yast2
bootloader".
Note that this is broken in Leap, but works fine in SLES, probably because the
path and OS name for SLES is so much shorter.
Interestingly, if I try to add my own entry with the proper path:
efibootmgr -c -d /dev/sda -p 1 --loader
"EFI\\opensuse-leap42.1-arm-jeos-devel-efi\\grubarm64.efi" -L
Test_Entry_By_Alan
and then inspect it with:
efibootmgr -v
I see my entry is truncated too :(
Boot0007* Test_Entry_By_Alan
HD(1,800,64004,cb3a713f-f051-4c9c-b643-b9e1358f6c2d)File(EFI\opensuse-leap42.1-arm-jeos-devel-ef)
In summary, grub2-install and/or efibootmgr is simply putting a boot entry into
NVRAM that is truncated and not valid.
Thanks!
Alan.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1062260
Bug ID: 1062260
Summary: Repository medical gone ... where are the packages?
Classification: openSUSE
Product: openSUSE.org
Version: unspecified
Hardware: All
OS: openSUSE Factory
Status: NEW
Severity: Major
Priority: P5 - None
Component: 3rd party software
Assignee: opensuse-communityscreening(a)forge.provo.novell.com
Reporter: werner(a)suse.com
QA Contact: opensuse-communityscreening(a)forge.provo.novell.com
Found By: ---
Blocker: ---
I'd like to know where the packages of the former repository medical are
located?
I'm missing the packages aeskulap, xmedcon, ...
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1046309
Bug ID: 1046309
Summary: Popup title is not hidden in installation
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
URL: https://trello.com/c/jO8YkgSc
OS: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: YaST2
Assignee: yast2-maintainers(a)suse.de
Reporter: jreidinger(a)suse.com
QA Contact: jsrain(a)suse.com
CC: dimstar(a)opensuse.org, fabian(a)ritter-vogt.de,
fvogt(a)suse.com, jreidinger(a)suse.com, kossebau(a)kde.org,
lnussel(a)suse.com, lslezak(a)suse.com, mkravec(a)suse.com,
okurz(a)suse.com
Depends on: 1037891
Found By: ---
Blocker: ---
+++ This bug was initially created as a clone of Bug #1037891 +++
IMHO the regression is (see comment #36):
* openSUSE Leap 42.1 had no title whatsoever for popups during installation
(unless remote ssh install)
* openSUSE Leap 42.3 has a title that is overly long and prone to touch the
border of the window -> ugly and not adding information
--
You are receiving this mail because:
You are on the CC list for the bug.