http://bugzilla.suse.com/show_bug.cgi?id=1087713http://bugzilla.suse.com/show_bug.cgi?id=1087713#c6
--- Comment #6 from Frank Kruger <fkrueger(a)mailbox.org> ---
(In reply to Wolfgang Rosenauer from comment #5)
> What in the screen shot do you think is wrong?
> Looks good to me.
According to the message in Tumbleweed's firefox "Firefox for openSUSE -
openSUSE-Tumbleweed" I expected for Leap 15.0 something like "Firefox for
openSUSE - openSUSE Leap 15.0". I just realized that the later nomenclature is
consistent with Leap 42.3. Anyway, this is a minor "issue". Thanks for your
efforts!
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1086739http://bugzilla.suse.com/show_bug.cgi?id=1086739#c15
Michael Henders <hendersm(a)shaw.ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(hendersm(a)shaw.ca) |
--- Comment #15 from Michael Henders <hendersm(a)shaw.ca> ---
I installed your updated kernel, and it seems to boot without problems; log
file is attached. Note -- YaST offered me the option to "Switch system
packages to the versions in this repository" with the new kernel. I wasn't
sure if I should do that or not, so went with "change as little as possible"
and did not switch. If that was the wrong choice, let me know, and I'll try
again.
And sure, add me to the patch -- might as well take a little credit, right? :)
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1087721
Bug ID: 1087721
Summary: Patterns not showing in software selection during
installation
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Minor
Priority: P5 - None
Component: Kubic
Assignee: kubic-bugs(a)opensuse.org
Reporter: rbrown(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
YaST software selection isn't showing any Patterns during installation
Probably because patterns-caasp is most likely missing the additional metadata
YaST uses to decide what to show, with which icons, and in which order
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1087714
Bug ID: 1087714
Summary: AUDIT-0: Renamed DBus files in kalarm
(suse-dbus-unauthorized-service)
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Security
Assignee: security-team(a)suse.de
Reporter: lbeltrame(a)kde.org
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
The new version of kalarm, which will be released with KDE Applications 18.04
in April 2018, has renamed its DBUs service files which are used together with
KAuth to enable RTC wake.
The previous files were called
/etc/dbus-1/system.d/org.kde.kalarmrtcwake.conf
/usr/share/dbus-1/system-services/org.kde.kalarmrtcwake.service
The new ones are instead
/usr/share/dbus-1/system-services/org.kde.kalarm.rtcwake.service
/etc/dbus-1/system.d/org.kde.kalarm.rtcwake.conf
The content and the nature of these files has not changed. They were simply
renamed. As this was already reviewed in the past, what would be needed would
be to whitelist these files as well. Note that the whitelist for the old files
should be kept, as both Leap 15 and 42.3 ship with the old versions of the
files.
The package with the unauthorized files currently lives in the
KDE:Unstable:Applications repository:
https://build.opensuse.org/package/show/KDE:Unstable:Applications/kalarm
There hasn't been a beta release yet, but this bug was filed earlier to get
enough time for the review.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1086739
Bug ID: 1086739
Summary: Kernel panic booting install DVD(s): kernel BUG at
../kernel/resource.c:722
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: i686
OS: SUSE Other
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Kernel
Assignee: kernel-maintainers(a)forge.provo.novell.com
Reporter: hendersm(a)shaw.ca
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:34.0) Gecko/20100101
Firefox/34.0 SeaMonkey/2.31
Build Identifier:
This issue prevents booting the installation disk with DVDs burned from the
following ISO images:
openSUSE-Tumbleweed-DVD-i586-Snapshot20180213-Media.iso
openSUSE-Tumbleweed-DVD-i586-Snapshot20180314-Media.iso
openSUSE-Tumbleweed-KDE-Live-i686-Snapshot20180314-Media.iso
Each image was verified by sha256sum before burning, and after burning, the
original ISO image and the new DVD were both mounted, then compared to each
other. All verification was good.
Boot fails for any of the options that try to launch a Linux kernel from the
DVD, i.e., "Installation", "Upgrade", "Rescue System", or "Check Install
Media". The progress box ("Starting...") comes up, runs through "Loading Linux
Kernel" to the 100% mark, then the screen blanks momentarily, there is a flurry
of boot-progress activity text, then the kernel panic. The entire thing occurs
within a couple of seconds of the screen change.
Reproducible: Always
Steps to Reproduce:
1. Load installation DVD for affected release -- see above.
2. Boot from DVD, and select "Installation" after the initial bootsplash.
3. Wait through the "Loading Linux Kernel" progress dialog.
4. Watch the ensuing system crash.
Actual Results:
Kernel panic/system crash.
Expected Results:
Entry into installer screens.
This appears to be a regression; I have no problem booting the DVD for the
20170129 snapshot of Tumbleweed (the most recent I have available prior to
this). It is also possible, however, that the regression is much more recent;
the 20180213 Tumbleweed snapshot (which fails) reports kernel 4.15.2-1, but I
am able to successfully boot kernel 4.15.0-10 (from a Kubuntu 18.04-beta1
disk). Other relatively recent kernels (4.12.7, 4.13, and 4.14.12) from
various distributions also boot successfully.
The target machine is a Toshiba Tecra M5 laptop, model ST8112; I can provide
further hardware information as required -- please specify. Of potential
interest, however: I have two of these Tecras, almost twins, but one uses an
NVidia Quadro NVS 110M/128 MB graphics adapter, and the other has integrated
Intel 945GM graphics. The NVidia machine crashes as described here; the Intel
one is unaffected, i.e., the above-noted Tumbleweed snapshots boot without
incident.
Finally, please see the attached file, containing a trace of the kernel panic
as dumped to my screen. Hopefully this will be helpful.
--
You are receiving this mail because:
You are on the CC list for the bug.