Do more on the web, with a fast and secure browser!
Download Opera browser with:
I also missed this feature the first time I wanted to reopen a closed tab... shit, where did that button go? Then I came here to find it, and yes, that flag works for now, but this really something they shouldn't have removed... it was one of the most useful features. It was just there, a click away, not hidden away in the menu... there is space for two buttons there Opera, just sayin'...
@ygbourhis: Yep, I've just updated from the official repository. 
Seems like they've come to senses as to not loose loyal users on a tiny thing like this...
After upgrading to the version mentioned in the title, when I start Opera, it hangs after a few seconds. Tried disabling extensions, and starting without sandbox. Tried with different versions of libffmpeg.so, as it used to go wrong sometimes. None helped. I don't want to reinstall it, because I have data in my extensions that I don't want to lose.
This seems to be the relevant parts of the startup log in terminal:
[22857:23523:0225/222623.088692:ERROR:nss_util.cc(283)] After loading Root Certs, loaded==false: NSS error code: -8018
[23025:1:0225/222624.188436:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
**[same message for 5 times]**
[22995:1:0225/222626.638499:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
[23688:1:0225/222632.513907:ERROR:child_thread_impl.cc(784)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer
[22886:22892:0225/222639.870152:ERROR:object_proxy.cc(632)] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd5: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
[22886:22892:0225/222639.870182:ERROR:kwallet_dbus.cc(100)] Error contacting kwalletd5 (isEnabled)
[22886:22892:0225/222639.871060:ERROR:object_proxy.cc(632)] Failed to call method: org.kde.KLauncher.start_service_by_desktop_name: object_path= /KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.klauncher was not provided by any .service files
[22886:22892:0225/222639.871090:ERROR:kwallet_dbus.cc(72)] Error contacting klauncher to start kwalletd5
[22886:22892:0225/222639.975071:ERROR:object_proxy.cc(632)] Failed to call method: org.kde.KWallet.close: object_path= /modules/kwalletd5: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
[22886:22892:0225/222639.975578:ERROR:kwallet_dbus.cc(414)] Error contacting kwalletd5 (close)
[22857:23040:0225/222641.153428:ERROR:object_proxy.cc(632)] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd5: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
[22857:23040:0225/222641.153567:ERROR:kwallet_dbus.cc(100)] Error contacting kwalletd5 (isEnabled)
[22857:23040:0225/222641.154065:ERROR:object_proxy.cc(632)] Failed to call method: org.kde.KLauncher.start_service_by_desktop_name: object_path= /KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.klauncher was not provided by any .service files
[22857:23040:0225/222641.154577:ERROR:kwallet_dbus.cc(72)] Error contacting klauncher to start kwalletd5
[22857:23040:0225/222641.259979:ERROR:object_proxy.cc(632)] Failed to call method: org.kde.KWallet.close: object_path= /modules/kwalletd5: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
[22857:23040:0225/222641.260475:ERROR:kwallet_dbus.cc(414)] Error contacting kwalletd5 (close)
[23717:1:0225/222644.632885:ERROR:child_thread_impl.cc(784)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer
[23727:1:0225/222647.097371:ERROR:child_thread_impl.cc(784)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer
[23743:1:0225/222652.782894:ERROR:child_thread_impl.cc(784)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer"
This is on Kubuntu 18.04 64-bit, kernel version 4.15.0-88-generic. LDD version shows this: ldd (Ubuntu GLIBC 2.27-3ubuntu1) 2.27 (not sure if it's glibc-related though, but might help).
Chromium works fine, Vivaldi works as well, so it seems to be an Opera-bug.
Please advise what worth a try, and does not delete my personal data, thank you.
@l33t4opera Thanks, tried, but it's still freezing. Resolved the kwallet issue though, but I think that was present before this problem appeared.
The main issue will be somewhere with these errors I guess:
"[920:1:0225/234506.590732:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
[920:1:0225/234506.592328:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
[1873:1:0225/234508.986148:ERROR:child_thread_impl.cc(784)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer
[891:1:0225/234515.099843:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
[1932:1:0225/234520.356869:ERROR:child_thread_impl.cc(784)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer
[1947:1:0225/234528.269767:ERROR:child_thread_impl.cc(784)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer
[1987:1:0225/234535.877741:ERROR:child_thread_impl.cc(784)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer
[1997:1:0225/234536.569890:ERROR:child_thread_impl.cc(784)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer"
@minho It was hard to do it fast enough, but eventually I got logged out of Sync, and yes, it seems to have solved the problem. In the meantime, someone replied to my bugreport from Opera, so I'll update him with this information.
Thank you so much for your help! Hopefully they'll find the bug within Sync, and I can use it again, it was working fine for me so far...