http://bugzilla.opensuse.org/show_bug.cgi?id=1090240
Bug ID: 1090240
Summary: document Qt/sddm hidpy options
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.0
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Release Notes
Assignee: sknorr(a)suse.com
Reporter: lnussel(a)suse.com
QA Contact: lnussel(a)suse.com
CC: fvogt(a)suse.com
Found By: ---
Blocker: ---
The options Fabian listed in
https://bugzilla.opensuse.org/show_bug.cgi?id=1083873#c5 need to be documented
in the release notes.
QT_AUTO_SCREEN_SCALE_FACTOR=1 can be passed on the bootloader command line of
the installation.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1085372
Bug ID: 1085372
Summary: RN: add notes about font rendering change
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.0
Hardware: All
OS: All
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Release Notes
Assignee: sknorr(a)suse.com
Reporter: jengelh(a)inai.de
QA Contact: lnussel(a)suse.com
Found By: ---
Blocker: ---
Created attachment 763734
--> http://bugzilla.opensuse.org/attachment.cgi?id=763734&action=edit
Original behavior aka interpreter v35
Please add this information to the release notes:
In wanting to mimic the contemporary Microsoft Windows font rendering more
closely, freetype 2.6.4 has changed the way it hints font glyphs. To restore
the previous FreeType behavior, set the following environment variable at any
level (system-wide, user-specific, or program-specific) of your choice.
FREETYPE_PROPERTIES="truetype:interpreter-version=35"
[2 screenshots for comparison]
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1074097
Bug ID: 1074097
Summary: RN: "systemctl stop apparmor" intentionally broken
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.0
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Release Notes
Assignee: sknorr(a)suse.com
Reporter: suse-beta(a)cboltz.de
QA Contact: lnussel(a)suse.com
Found By: ---
Blocker: ---
Please add this information about AppArmor to the Leap 15 release notes
(copy&paste from
https://blog.cboltz.de/archives/77-AppArmor-2.12-The-Grinch-is-confined!.ht…
and assuming that Leap 15 will pick up AppArmor 2.12 or newer)
---
One important change in the [AppArmor 2.12] packages is that I intentionally
broke "systemctl stop apparmor". The reason for this is "systemctl restart
apparmor" - systemd maps this to stop, followed by start. This resulted in
unloading all AppArmor profiles by the "stop" part and, even if they get loaded
again a second later, running processes will stay unconfined unless you restart
them. The systemd developers were unwilling to implement the proposed
ExecRestart= option for unit files, therefore breaking "stop" is the best thing
I can do. (See boo#996520 and boo#853019 for more details.)
"systemctl reload apparmor" will continue to work and is still the recommended
way to reload the AppArmor profiles, but accidently typing "restart" instead of
"reload" can easily happen. Therefore I chose to break "stop" - that's
annoying, but more secure than accidently removing the AppArmor confinement
from running processes.
If you really want to unload all AppArmor profiles, you can use the new
"aa-teardown" command which does what "systemctl stop apparmor" did before -
but who would do that? ;-)
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1050519
Bug ID: 1050519
Summary: Description about kernel graphics update
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.3
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Release Notes
Assignee: sknorr(a)suse.com
Reporter: tiwai(a)suse.com
QA Contact: lnussel(a)suse.com
Found By: ---
Blocker: ---
Created attachment 733812
--> http://bugzilla.opensuse.org/attachment.cgi?id=733812&action=edit
Patch to release-notes.xml
Some information about Leap 42.3 kernel graphics update, as Ludwig suggested in
opensuse-factory ML.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1048692
Bug ID: 1048692
Summary: version downgrade of libgcj_bc1
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.3
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
Assignee: rguenther(a)suse.com
Reporter: lnussel(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
42.2 vs 42.3:
libgcj48: libgcj_bc1-4.8.5-24.14.x86_64 is older than
libgcj_bc1-6.2.1+r239768-5.5.2.x86_64
in 42.2 libgcj_bc1 came from libgcj-gcc6 which isn't in 42.3. What is correct
here?
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1048660
Bug ID: 1048660
Summary: LibreOffice 5.3.3 update: Type 1 (Postscript) fonts
are no longer supported.
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.2
Hardware: x86-64
OS: openSUSE 42.2
Status: NEW
Severity: Major
Priority: P5 - None
Component: Release Notes
Assignee: sknorr(a)suse.com
Reporter: bugrprt21882(a)online.de
QA Contact: lnussel(a)suse.com
Found By: ---
Blocker: ---
13th July 2017:
With the Leap 42.2 upgrade of LibreOffice from version 5.2.5 to version 5.3.3
the fact that, with version 5.3 LibreOffice has dropped support for Type 1
(Postscript) fonts was a not so pleasant surprise.
Please consider placing a note indicating that, LibreOffice as of version 5.3
no longer supports Type 1 (Postscript) fonts in the Release Notes.
Is also, possibly an issue for the Leap 42.3 Release Notes.
---------------------------------------------------------
I haven't found anything in the LibreOffice Release Notes indicating this
issue:
<https://www.libreoffice.org/download/release-notes/>
There's only this article in "Linux Magazine":
<http://www.linux-magazine.com/Online/Blogs/Off-the-Beat-Bruce-Byfield-s-Blo…>
There's information in this Document Foundation Bug Report: Bug 104701
<https://bugs.documentfoundation.org/show_bug.cgi?id=104701>
---------------------------------------------------------
There's possibly help for the folks (like me) with a suite of Type 1 fonts
here:
<https://slackbuilds.org/repository/14.2/system/afdko/>
Haven't tried to build the "Adobe Font Development Kit for OpenType" yet --
will happen later today.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1048392
Bug ID: 1048392
Summary: [doc] Extended Permission bits: Konqueror is also the
Plasma 5 version
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.3
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Release Notes
Assignee: sknorr(a)suse.com
Reporter: bugrprt21882(a)online.de
QA Contact: lnussel(a)suse.com
Found By: ---
Blocker: ---
3.2 Dolphin Does Not Set Extended Permission Bits
https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/42.3/#sec.gener…
Unfortunately, with Leap 42.3, Konqueror is also the Plasma 5 version and, it
also can not set the Extended Permissions bits . . .
Therefore, the Leap 42.3, CLI only to toggle the Extended Permission bits . . .
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1111572
Bug ID: 1111572
Summary: patch segfaults if it can't write *.orig
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Development
Assignee: jdelvare(a)suse.com
Reporter: suse-beta(a)cboltz.de
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 785784
--> http://bugzilla.opensuse.org/attachment.cgi?id=785784&action=edit
reproducer (tar.gz)
Tumbleweed 20181009, patch-2.7.6-3.5.x86_64
I tried to apply a (non-matching) patch, and when patch tried to create the
*.orig file, it printed a long list of error messages:
# patch cleanprofile.py < changes.diff
patch: **** Can't create file cleanprofile.py.orig : Permission denied
patch: **** Can't create file cleanprofile.py.orig : Permission denied
patch: **** Can't create file cleanprofile.py.orig : Permission denied
patch: **** Can't create file cleanprofile.py.orig : Permission denied
patch: **** Can't create file cleanprofile.py.orig : Permission denied
[...]
patch: **** Can't create file cleanprofile.py.orig : Permission denied
patch: **** Can't create file cleanprofile.py.orig : Permission denied
patch: **** Can't create file cleanprofile.py.orig : Permission denied
patch: **** Can't create file cleanprofile.py.origSegmentation fault (core
dumped)
I'd expect _one_ "Permission denied" message, and no segfault.
Reproducer:
- unpack the attached tarball (as user)
- chown root cleanprofile.py.orig (obviously as root)
- run patch cleanprofile.py < changes.diff as user
Note: This seems to be related to the files in the attached tarball. If I try
with a simple one-line file and a boring patch, patch doesn't segfault. The
reproducer files must have something special that send patch into an endless
loop.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1103239
Bug ID: 1103239
Summary: valgrind doesn't understand -z separate-code linked
objects
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Development
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: rguenther(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
When linking with -z separate-code (which is the default on x86_64 starting
with binutils 2.31 currently in staging) valgrind doesn't seem to find
debuginfo
anymore.
Reproduce like
> echo 'int main() { return 0; }' | gcc -g -Wl,-z,separate-code -x c -
> valgrind --tool=callgrind ./a.out
> grep main callgrind.out.*
fn=(220) (below main)
fn=(14) dl_main
while the correct one looks like
cfn=(220) (below main)
fn=(246) main
fn=(14) dl_main
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1131299
Bug ID: 1131299
Summary: fontconfig creates an enormous number of files in
/var/cache/fontconfig that are never cleaned up
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: shundhammer(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Earlier today I discovered that I had over 350,000 files in
/var/cache/fontconfig that had accumulated in the 4 years that I have been
using Tumbleweed.
This not only consumed a lot of disk space, it also brought the system to a
screeching halt every once in a while: All those files were in that single
directory without any subdirectory. Even modern filesystems like XFS (which is
what I use on that filesystem) break down completely in terms of performance
when so many files are dumped into a single directory.
It took more than 20 minutes (!) to remove the files (which needed "ls | xargs
rm" because the argument list was much too long).
So this directory needs to be cleaned up automatically every once in a while.
Better yet, don't create so many files there in the first place. And even
better, if so many files are needed, do it like the browsers (for their cache
directories) and use an intermediate subdirectory (maybe on multiple levels)
for better performance.
[shundhammer @ morgul] ~ % cat /etc/os-release
NAME="openSUSE Tumbleweed"
# VERSION="20190318"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20190318"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:tumbleweed:20190318"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"
[shundhammer @ morgul] ~ % rpm -q fontconfig
fontconfig-2.13.1-2.1.x86_64
After the cleanup, some files were recreated:
[shundhammer @ morgul] ~ % ls -1 /var/cache/fontconfig
4bc6e738-4f14-4bb3-b1c1-113e1440c1c9-x86_64.cache-7
62a2cfd2-5b41-4739-9b75-5f646215de71-x86_64.cache-7
66f92a5c-8bae-4b9c-ba14-cf0cecec77a2-x86_64.cache-7
6f5661a4-b4de-4837-a6cb-77408b27d222-x86_64.cache-7
81ea5785-41f1-4169-a014-a9180af45296-x86_64.cache-7
8bfbb25c-ea26-45ef-9fa8-8bc1cd23e6c8-x86_64.cache-7
a74dc887-85ed-4c63-a0b3-3520f4be1244-x86_64.cache-7
b77b3349-5612-4eeb-95e2-a017bef0b7b7-x86_64.cache-7
be89a7c6-246d-476f-9e7e-e63a135fcfea-x86_64.cache-7
c210a518-33c5-48da-a1b9-55b4a4895c28-x86_64.cache-7
cbe681e7-c178-45ed-a1dd-523a6515af68-x86_64.cache-7
e0f28a10-064e-443c-9da1-1ad111a20ab1-x86_64.cache-7
e50cc437-bedf-4c0d-a1fb-f06def71d136-x86_64.cache-7
f5d4db0f-7acc-412e-b184-266c457f1a79-x86_64.cache-7
f6c4cbb4-f12c-4f74-8d69-264c5d8bbf56-x86_64.cache-7
That is a reasonable number. 350,000+ is not.
--
You are receiving this mail because:
You are on the CC list for the bug.