http://bugzilla.opensuse.org/show_bug.cgi?id=1123960
Bug ID: 1123960
Summary: LibreOffice missing libreoffice-gtk3
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: openSUSE Factory
Status: NEW
Severity: Normal
Priority: P5 - None
Component: LibreOffice
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: knurpht(a)opensuse.org
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
After upgrading to TW 20190126, LO shows the Win95 like fallback interface.
Knowing it is a gtk based app, I ran 'zypper se -i -v libreoffice' I noticed
libreoffice-gtk3 was not installed, so as a try I installed that. LO back to
normal after doing so.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1165273
Bug ID: 1165273
Summary: zathura-plugin-pdf-mupdf not loaded due to error.
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: screening-team-bugs(a)suse.de
Reporter: dracaphallus(a)gmail.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/80.0.3987.100 Safari/537.36
Build Identifier:
Running zathura after the installation of zathura-plugin-pdf-mupdf the
following error output is produced:
```
error: Could not load plugin '/usr/lib64/zathura/libpdf-mupdf.so'
(/usr/lib64/zathura/libpdf-mupdf.so: undefined symbol: jpeg_resync_to_restart).
```
>From the error output I'd deduced that the package was packaged wrong and
therefore produced the error mentioned above. It has the plugin from working as
intended by making zathura incapable of opening the supported document formats
(PDF, ePub, and OpenXPS).
This issue was reported 14 days ago using the comment section of
openSUSE:Factory, while it was reported 8 days ago in the comment section of
`X11:Utilities` with no response. This has lead me to file a bug report in
OpenSUSE Bugzilla with the hope of getting this issue resolved.
Reproducible: Always
Steps to Reproduce:
1. Installing zathura-plugin-pdf-mupdf using zypper.
2. Running zathura through terminal.
Actual Results:
The following error was produced:
```
error: Could not load plugin '/usr/lib64/zathura/libpdf-mupdf.so'
(/usr/lib64/zathura/libpdf-mupdf.so: undefined symbol: jpeg_resync_to_restart).
```
Expected Results:
Zathura being able to open the supported document formats (PDF, ePub, and
OpenXPS).
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1173748
Bug ID: 1173748
Summary: System hangups in dual monitor use, likely Plasma/Xorg
related
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: P.Suetterlin(a)royac.iac.es
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
I am experiencing repeated issues with my laptop (running current TW, 20200701)
when sitting in the dock with a second monitor connected.
It usually starts with the second monitor going dark, then getting signal again
(and the monitor displays the current input as info, so indeed the signal seems
to have been gone?). Sometimes, it does stay black until I move the cursor in
there and/or go to a workspace that has a window on that screen.
Sometimes, in that situation where the monitor is black, moving the cursor to
that screen doesn't help, but short after that the whole computer freezes dead.
It also isn't pingable via network anymore, only 5s power button switchoff
helps.
I've seen it several times already over the last months, sometimes not for a
longer time. With the current release I had it 2 times already, plus a
coredump of kwin after a restart (the first coredump since many months)
Unfortunately I never found anything in the logfiles after a lockup. And the
system is configured not to write coredumps, so also nothing from the kwin
crash :(
In short, I don't really have a clue if that is software or hardware, or how to
narrow it down, as I have so far not found a way to produce the issue.
I *think* it is only happening after the monitors went to DPMS suspend, and
with no window on the second monitor.
Hardware is a Lenovo T460p, Skylake with HD530 graphics, and Xorg based
KDE/Plasma.
Maybe someone has an idea what to check/look for.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1166005
Bug ID: 1166005
Summary: 20s to unlock fully encrypted partition
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Bootloader
Assignee: jsrain(a)suse.com
Reporter: axel.braun(a)gmx.de
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
I have a new TW installation with a 940GB encrypted root partition (including
/boot, excluding /boot/efi).
When starting the machine, grub asks in text mode for the passphrase.
After entering the passphrase, it takes about 20s until the graphical boot
screen appears.
X1E:/home/test # lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme0n1 259:0 0 953,9G 0 disk
├─nvme0n1p1 259:1 0 500M 0 part /boot/efi
├─nvme0n1p2 259:2 0 937G 0 part
│ └─cr_root 254:0 0 937G 0 crypt /
└─nvme0n1p3 259:3 0 16,4G 0 part [SWAP]
linux:/home/test # cryptsetup luksDump /dev/nvme0n1p2
LUKS header information for /dev/nvme0n1p2
Version: 1
Cipher name: aes
Cipher mode: xts-plain64
Hash spec: sha256
Payload offset: 4096
MK bits: 512
MK digest: c3 b3 b9 a1 4b cd 08 8d 93 47 59 be f1 b8 f3 24 5f ae 81 75
MK salt: 8b 87 eb c4 bd 43 4e af 57 ef eb 9f 3c 38 a9 8a
f4 c5 63 2f 1b f6 98 1a 49 62 36 e0 9e 12 8a db
MK iterations: 153840
UUID: 720864c9-f8ed-405e-9a17-ccfa1d2f347b
Key Slot 0: ENABLED
Iterations: 1229280
Salt: 5f 9b 38 6b 29 b4 2e b0 80 35 c5 bd 88 9f 77 61
29 6c 34 00 54 3c af a5 5a d4 f6 15 7e e4 8d c4
Key material offset: 8
AF stripes: 4000
Key Slot 1: DISABLED
Key Slot 2: DISABLED
Key Slot 3: DISABLED
Key Slot 4: DISABLED
Key Slot 5: DISABLED
Key Slot 6: DISABLED
Key Slot 7: DISABLED
It is an i7-9750H machine, so CPU power should not be an issue...
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1166406
Bug ID: 1166406
Summary: Consider moving /boot/vmlinux-*.xz to a different
package
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-maintainers(a)forge.provo.novell.com
Reporter: fvogt(a)suse.com
QA Contact: qa-bugs(a)suse.de
CC: jeos-internal(a)suse.de
Found By: ---
Blocker: ---
Currently the kernel is installed twice into /boot (at least on x86_64 and
arm64), once as self-decompressing vmlinuz and then the raw compressed kernel
as vmlinux.xz
The latter isn't needed for booting and only used for debugging or by using
special tools (AFAIK, please correct me if I'm wrong), so not useful on most
systems.
Especially with kernel-default-base, this ~10MiB file is almost 30% of the
whole package in size, so dropping/moving that would have a noticeable impact
on size reduction.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157764
Bug ID: 1157764
Summary: [Feature request] Add local resolver with support for
DNS-over-TLS and DNS-over-HTTPS
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.1
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Network
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: sionescu(a)cddr.org
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Since Dnsmasq doesn't support either protocols, perhaps adding support for
Unbound or Stubby would be a good idea.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1172327
Bug ID: 1172327
Summary: YaST 2 ".desktop" files are not working with lxqt-sudo
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.2
Hardware: x86-64
OS: SUSE Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: LXQt
Assignee: mvetter(a)suse.com
Reporter: arkadii0324(a)gmail.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
I'm clicking on different links for YaST software from start menu in LXQt but
nothing happens after administrator's password typing in "lxqt-sudo" program. I
tried to enter the command from one of YaST links in
/usr/share/applications/YaST2:
$ LC_ALL=C xdg-su -c "/sbin/yast2 users"
No protocol specified
bash: /sbin/yast2 users: No such file or directory
$
I have installed my system from netinstall image (29 May) with basic X11
environment and "lxqt" pattern.
Thanks for help.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1101747
Bug ID: 1101747
Summary: no cursor after using e in plain text grub-efi menu
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Bootloader
Assignee: jsrain(a)suse.com
Reporter: mrmazda(a)earthlink.net
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
Created attachment 777365
--> http://bugzilla.opensuse.org/attachment.cgi?id=777365&action=edit
/etc/default/grub and /boot/grub2/grub.cfg from TW host ab250
initial summary: no cursor after using e in plain text grub-efi menu
First noticed in TW20180712 and continues in 20180714.
After entering "e" on any plain text grub-efi boot menu, there is no kind of
cursor blinking anywhere, and as a practical matter it's not possible to do any
editing of grub stanzas. All keyboard keys seem to work, but without cursor
they're virtually useless.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1088564
Bug ID: 1088564
Summary: "ssh-agent" is not started on login to Plasma5-Wayland
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.0
Hardware: x86-64
OS: SUSE Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: KDE Workspace (Plasma)
Assignee: opensuse-kde-bugs(a)opensuse.org
Reporter: nwr10cst-oslnx(a)yahoo.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
Firefox/52.0
Build Identifier:
This happens in both Leap 15.0 and Tumbleweed.
When I login to a Plasma5-Wayland session, "ssh-agent" is not running for the
desktop session. This happens whether I use SDDM or GDM for the login manager.
I'm aware that Plasma5-Wayland isn't really ready for prime time. Still, it
would be nice to have this fixed by the time Leap 15.0 is officially released.
My current workaround -- I'm starting "ssh-agent" in the shell startup file
(with cross checks so that it isn't started if already running).
Reproducible: Always
--
You are receiving this mail because:
You are on the CC list for the bug.