okular has lost all functions on menus (not clickable)

Bug #1781163 reported by udippel
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
okular (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

For the last few days, okular has lost all functionality of the menu. The menu *does* show, but nothing in okular is clickable, including the menu.

It must have to make with the last update(s); and I am not the only one affected; see
https://forum.kde.org/viewtopic.php?f=251&t=153168

I am at okular 4:16.04.3
kubuntu 16.04, daily updates, 64 bit

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in okular (Ubuntu):
status: New → Confirmed
Revision history for this message
Martin (axiomize) wrote :

Since yesterday, the firefox menu (on the right upper corner) is not responding anymore either.

Revision history for this message
udippel (udippel) wrote :

Yup, here as well. It is becoming a major blocker at this very moment!
Question: Is this big report here enough, or should I also file for Firefox?

Revision history for this message
Martin (axiomize) wrote :

I think it would be good to file also for Firefox. I hope that this is fixed in the upcoming kubuntu 18.04 release, but I have to wait because the upgrade will only be available in late july, they say...

Revision history for this message
Reg Dodds (reg-dodds) wrote :

Linux teleman 4.4.0-130-generic #156-Ubuntu
Firefox \stackrel{=}{_} button and Okular menu not clickable.

But on
Linux teleman 4.4.0-128-generic #154 ...
both work fine.

Revision history for this message
Reg Dodds (reg-dodds) wrote :

Sorry. The previous evidence is true, but might be misleading. Note these are two machines both called teleman. They are two different machines.

Using the same machine where this bug appears and booting previous versions of the OS not = -130, i.e. -128 and -127, the bug is still present. The machine on -128 where the bug does NOT lie, has not been upgraded recently.

Revision history for this message
Reg Dodds (reg-dodds) wrote :

Symptoms:

Firefox "Open Menu" button still dead and
Okular menu buttons still not clickable
after upgrading to
Distributor ID: Ubuntu
Description: Ubuntu 16.04.5 LTS
Release: 16.04
Codename: xenial

4.4.0-131-generic #157-Ubuntu SMP

Any hope for a fix?

Revision history for this message
Wes (wesinator) wrote :
Revision history for this message
Reg Dodds (reg-dodds) wrote :

I have found a simple fix at last.

Set the compositor renderer to XRender by clicking your way through to the Compositer that sets it as follows:
KDE Start button ==>
Display and Monitor ==>
Compositor

Now set the rendering backend to anything BUT NOT THE DEFAULT: (OpenGL 3.1, GLX)
and NOT (OpenGL 2, GLX).

All the other settings work.
(Xrender)
and
(OpenGL 3.1, EGL)
(OpenGL 2, EGL)

I still hope this bug is fixed in the upgrade release of 18.04 LTS which has been promised for late July 2018. Today is 30 July 2018. There is still no release upgrade.

Revision history for this message
Martin (axiomize) wrote :

Wow, thank you!

Revision history for this message
udippel (udippel) wrote :

Don't, ever!!

I tried, and lost all my desktop.
Okay, here the alternatives were different:
No option on GLX, EGL, Only
OpenGL 2.0
OpenGL 3.1
Xrender

Changing from 2.0 to 3.1 removed my desktop settings, and Xrender left me with an absolutely black screen.

Revision history for this message
atul (sowani) wrote :

I have started discussion here: https://answers.launchpad.net/ubuntu/+question/670844 about this issue on 12th July 2018, but haven't received any solution yet. Still awaiting a fix...

Revision history for this message
sanette (sanette-linux) wrote :

Same bug here with Linux Mind KDE 18.3
(based on ubuntu 16.04)

siwtchin to Xrender works for me, but I suppose I loose some desktop effects (haven't checked this)

Revision history for this message
Patrick Wigmore (patrick-wigmore) wrote :

If those affected think this is the same bug, you could mark this bug as a duplicate of #1780664. Bug #1780664 has a fix committed now, which should be available in xenial-updates soon.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.