Public bug reported:
With a desktop snap application open, you can go to "Show Details" and
it will launch GNOME Software which expects an app id. The desktop id is
being passed to Software and the result is Software displaying "Unable
to find gnome-clocks_gnome-clocks.desktop".
ProblemType: Bug
After testing this a bit more, I noticed that when plugging in the power
the battery percentage says 100% for *some period of time* before
changing to match the percentage that upower has. The time it takes for
the percentage to go from 100%->true% varies anywhere from a second to
minutes but it
Public bug reported:
Hardware: Lenovo T590
OS: 19.10
When the power is not connected when the laptop boots, and then
connected, the power icon in the top bar does not change to indicate
that the laptop is now charging.
$ upower -d
Device: /org/freedesktop/UPower/devices/line_power_AC
This issue is completely reproducible for me. Digging into the
journalctl logs around when the system is rebooting without power
plugged in, here are some lines that stand out and might be useful:
Note that the system was sent to reboot at 10:53:00
...
Sep 26 10:53:37 fenrir systemd[2088]:
I tried this in a 19.04 live boot from a usb stick and the behavior was
correct: if the system was booted without power, the charging symbol was
not there. Then when I connected the power, the charging symbol
appeared.
Also, when booting 19.04 without power connected, there is only the one
The following is the output of `journalctl | grep -i power` that covers
the duration between the reboot command and login times.
** Attachment added: "journal-power-keyword_no-power-connected-on-boot.out"
The following is the output of `journalctl | grep -i power` that covers
the duration between the reboot command and login times.
** Attachment added: "journal-power-keyword_with-power-connected-on-boot.out"
The only difference in journalctl between when the system boots with
power and without is that when the system boots without power, I see two
journalctl messages:
Sep 26 10:53:27 fenrir dbus-daemon[793]: [system] Activating via systemd:
service name='org.freedesktop.UPower' unit='upower.service'
In 19.10, with the error state, restarting upower fixes the issue. So if
you've booted without power connected, then connect power and don't see
the charging icon, execute `sudo systemctl restart upower` and see the
charging symbol.
--
You received this bug notification because you are a member
** Attachment added: "lspci network controller info"
https://bugs.launchpad.net/ubuntu/+bug/1808389/+attachment/5290971/+files/lspci_network_controller_info.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm seeing this very same issue on a new Lenovo T590 running 19.10 with
linux-firmware 1.182 and linux-image-generic 5.3.0.10.11. See attached
files for more verbose info on the network controller and journalctl
logs.
Thanks to the previous comment, I can say that the issue is only seen if
the
The output of `upower -d` with the power cable unplugged.
** Attachment added: "unplugged.out"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846000/+attachment/5292886/+files/unplugged.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The output of `upower -d` with the power cable plugged in.
** Attachment added: "plugged-in.out"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846000/+attachment/5292885/+files/plugged-in.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Hardware: Lenovo T590
OS: 19.10
I have the battery percentage displayed next to the battery icon in the
top bar (Tweaks -> Top Bar -> Battery Percentage). When the power cord
is connected, it says 100%. However, if I unplug the power cord, the
percentage drops down to 94%
Brief video displaying the behavior. You can see when the power is
connected or not because the lightning bolt shows up when the power is
connected.
** Attachment added: "1846000.mkv"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846000/+attachment/5292898/+files/1846000.mkv
--
Public bug reported:
Tab completion for `snap install` and `snap remove` works just fine but
does not work with `snap run`.
So for example, if you have gnome-clocks installed, `snap run gnome-
clo` should fill out gnome-clocks but it does not.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
On my workstation, this happens with fullscreen'd firefox too. Any
fullscreen'd app. So it's not limited to the terminal application.
However, this does not appear to happen on my thinkpad running 19.10. So
I think you're right, it is likely nvidia-specific.
--
You received this bug notification
Public bug reported:
I like some things like terminal to be fullscreen (F11). I've noticed
that whenever I look at what apps are running by tapping the Super key
and then go to any app that is in fullscreen mode (by either hit the
Super key again to give focus back to the app OR click the app I'd
Whenever I have a fullscreen app focused on, and then hit the super key,
I see this JS ERROR in the journalctl (see attachment). Note that if the
app is not fullscreen, there is no flashing and no journalctl error log.
** Attachment added: "journalctl.out"
** Also affects: webkit2gtk (Ubuntu Focal)
Importance: High
Status: Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687019
Title:
Cannot add a Google account using Online
Public bug reported:
On a freshly installed 20.04 system, going through the initial setup and
I'm presented with the Online Accounts panel where I selected Google,
entered my email and password. Then Google's 2-factor authentication
kicks in and instructs me to check my phone. I do and approve
Yep you're right. There weren't any updates as of yet so this bug I
think can be closed. Sorry about that.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The title pretty much sums it up. When installing xubuntu oem, I
unchecked the box "Download updates while installing Xubuntu" and
checked the box "Install third-party software". When I clicked continue,
I get a message saying that ubi-partman crashed (see attached). If it is
Public bug reported:
When installing xubuntu, we see a "Release Notes" link on the first page
(page with "Try Ubuntu" and "Install Ubuntu"). When that link is
clicked, the user is taken to
https://wiki.ubuntu.com/19.10/ReleaseNotes, which redirects you to:
Public bug reported:
On xubuntu oem install, I unchecked the box "Download updates while
installing Xubuntu" and checked the box "Install third-party software".
After the install was complete and the system rebooted, I went to `sudo
apt update && sudo apt dist-upgrade` and there were no updates,
Public bug reported:
When at the terminal, trying to file an issue with ubuntu-bug, I was
prompted for authentication. Only after the third try was the password
accepted.
1. I entered the password correctly and the authentication window closed and
reopened very quickly (no error message that I
Public bug reported:
I don't know what causes it but frequently I see my journalctl being
spammed with gnome-shell errors (see attached journalctl snippet). If I
do nothing about it, then within a few hours gnome-shell is slow and may
eventually freeze. So I end up rebooting to reset the system
A MIR has been opened: https://bugs.launchpad.net/ubuntu/+source
/libmail-dkim-perl/+bug/1853175
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851395
Title:
[MIR]
Public bug reported:
[Availability]
It is available for all architectures in the universe.
https://launchpad.net/ubuntu/+source/libmail-authenticationresults-perl
[Rationale]
A new dependency of libmail-dkim-perl.
[Security]
No known CVEs.
libmail-dkim-perl v0.54-1 is already in main:
https://launchpad.net/ubuntu/+source/libmail-dkim-perl/0.54-1
but the new v0.56-1 has a new dependency on libmail-authenticationresults-perl:
https://launchpad.net/ubuntu/+source/libmail-dkim-perl/0.56-1
libmail-authenticationresults-perl is
libscalar-list-utils-perl is being requested to satisfy a dependency of
libmail-authenticationresults-perl.
libmail-authenticationresults-perl also has an open MIR to satisfy a dependency
of libmail-dkim-perl:
https://bugs.launchpad.net/ubuntu/+source/libmail-dkim-perl/+bug/1853175
--
You
Public bug reported:
[Availability]
It is available for any architecture in the universe.
https://launchpad.net/ubuntu/+source/libscalar-list-utils-perl
[Rationale]
A dependency of libmail-authenticationresults-perl (which is a new dependency
of libmail-dkim-perl)
[Security]
No known CVEs.
Note that libmail-authenticationresults-perl requires libscalar-list-utils-perl
(in universe) so a new MIR for libscalar-list-utils-perl has been opened:
https://bugs.launchpad.net/ubuntu/+source/libmail-dkim-perl/+bug/1854849
** Description changed:
[Availability]
It is available for all
I just tested this on 20.04 with the 6.4.0-0ubuntu3 deb as well as the
6.4.0.3 snap.
For each package type, I created one of each of the 8 3D images
available, on 8 different slides. I animated two of the images. In both
the deb and snap, each 3D image looked fine when in slide show mode and
Launchpad is a great place for you to report bugs about the libreoffice snap so
you did it right :)
Since Canonical delivers both a deb and snap of libreoffice, it's handy for me
to know which one you're using.
Since you're using the snap, I recommend putting your libreoffice files
somewhere in
Thanks for the report! First off, what version of libreoffice are you
using? Your system info says "Package: libreoffice (not installed)".
What version is in the libreoffice -> Help -> About libreoffice ?
If you're using the deb that is provided in the 19.10 update archives,
then that should be
** Changed in: libreoffice (Ubuntu Eoan)
Assignee: Marcus Tomlinson (marcustomlinson) => Heather Ellsworth
(hellsworth)
** Changed in: libreoffice (Ubuntu Focal)
Assignee: (unassigned) => Heather Ellsworth (hellsworth)
--
You received this bug notification because you are a
Upgraded libreoffice from 1:6.3.4-0ubuntu0.19.10.1 to
1.6.3.5-0ubuntu0.19.10.1 from eoan-proposed in a clean and up-to-date
eoan amd64 VM, and successfully ran test plan at
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice.
** Tags removed: verification-needed verification-needed-eoan
Updated the bug link
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2310
https://gitlab.gnome.org/GNOME/gnome-shell/issues/2310
** Changed in: gnome-shell
Importance: Medium => Unknown
** Changed in: gnome-shell
Status: Confirmed => Unknown
** Changed in:
All failing autopkgtests for 6.3.5-0ubuntu0.19.10.1 have been rerun and
are passing now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864071
Title:
[SRU] libreoffice 6.3.5 for eoan
To manage
Public bug reported:
The problem is that a stray "B" character is being printed to the
terminal screen after switching work spaces with the Ctrl+Alt+{Up/Down
arrows}.
On the first workspace, I have a few applications running (Firefox is focused)
On the second workspace I have gnome terminal
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2314
https://gitlab.gnome.org/GNOME/gnome-shell/issues/2314
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/issues/2314
Importance: Unknown
Status: Unknown
--
You received this bug
A freshly installed focal system doesn't come with gimp and installing
it from apt and runnning it works just fine. On a system that
experiences this undefined symbol, uninstalling gimp (and autoremove)
and reinstalling it fixes the problem. I'm not sure why this fixes the
issue because libgegl is
Public bug reported:
I'm running focal and have both the snap and the deb of gimp installed.
The snap runs just fine (although there is a GeglBuffer leak:
https://forum.snapcraft.io/t/gimp-geglbuffer-leak/15732).
However, if I run the deb from the command line, it won't start and
fails with:
False alarm everyone. This was just an issue on my host that had some
weird things installed. I can't reproduce this on another system so
closing.
** Changed in: gimp (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I updated my focal system and rebooted. Shortly after logging in, I see
that PackageKit crashed. Here is the systemctl log from the time that
PackageKit started. Recording it here just in case it happens again.
ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package:
ete
** Changed in: libreoffice (Ubuntu)
Assignee: (unassigned) => Heather Ellsworth (hellsworth)
** Changed in: libreoffice (Ubuntu)
Importance: Undecided => Low
** Changed in: libreoffice (Ubuntu)
Importance: Low => Wishlist
--
You received this bug notification because yo
: libreoffice (Ubuntu)
Importance: High
Assignee: Heather Ellsworth (hellsworth)
Status: New
** Affects: libreoffice (Ubuntu Eoan)
Importance: High
Assignee: Heather Ellsworth (hellsworth)
Status: New
** Tags: verification-needed-eoan
** Also affects: df-libreoffice
Thanks for reporting your issue with the libreoffice snap.
Unfortunately, snaps are restricted from accessing files in hidden
folders because this is often where other applications keep their
configuration files. If you still need to access these files with
libreoffice, you should use the
)
Status: New => Confirmed
** Changed in: libreoffice (Ubuntu)
Assignee: (unassigned) => Heather Ellsworth (hellsworth)
** Changed in: libreoffice (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
I understand the issue with cert8.db and key3.db being used (#1862331)
but I don't see what the problem is with the other apparmor messages you
see in journalctl. Can you please make clear what the problem with these
messages are?
--
You received this bug notification because you are a member of
The snap without Turkish is 407.7 MiB:
https://code.launchpad.net/~libreoffice/+snap/libreoffice-6.4/+build/829652
Adding Turkish adds 7.7 MiB, for a total of 415.4:
https://code.launchpad.net/~hellsworth/+snap/libreoffice/+build/840498
I thinks this added amount is fine so I'm going to add this
** Changed in: libmail-authenticationresults-perl (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853175
Title:
[MIR] libmail-authenticationresults-perl
** Changed in: libscalar-list-utils-perl (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854849
Title:
[MIR] libscalar-list-utils-perl
To manage
No fractional scaling is enabled. I eventually started just not using
fullscreen to avoid the flashing annoyance. I have since upgraded to
20.04. I see now that when I put an app into fullscreen, I no longer see
the flashing I reported in this issue. So my guess is something was
fixed in focal.
** Tags added: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870564
Title:
Libreoffice's option "Customize" is imcompatble to decrease its
Window size in Ubuntu 19.10
To manage
Hmm, well I installed mesa-opencl-icd and was still able to open
libreoffice without issue. However, since it sounds like your setup is
fixed (and not yet reported by others), I'm going to close this issue.
Feel free to reopen if you continue to have issues.
** Changed in: libreoffice (Ubuntu)
Lee, thanks for your report!
I see that it says libreoffice is "not installed" so could you please
provide some additional information..
* Did you install this via snap? If so, what is the output of `snap info
libreoffice`
* If you didn't install the snap, then could you please provide the
I made this bug public because I didn't see any reason to keep it
private. It also opens the bug so others can identify if this issue
affects them too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi, thanks for the report! I have a few questions to try and narrow this
down..
I assume when you say you changed the icon size, it was in:
Tools -> Options -> LibreOffice -> View -> Icon size
* Which Libreoffice application were you running when you changed the icon size?
* What size did you
Ok so sounds like you did a fresh install of 20.04 and then launched
libreoffice (should be installed just fine ith a non-minimal install
like you did). Perhaps something went wrong with your install, but
everything went find for your VM install.
Could you please provide the journalctl output
I've reproduced this in an updated kubuntu 20.04 vm. There are no
journalctl logs made when I change the icon either.
Note that in the common gnome based Ubuntu, this is not an issue and any
symbol can be set in charts.
** Changed in: libreoffice (Ubuntu)
Status: New => Confirmed
** Tags
Well all of the libreoffice apparmor lines for the deb look normal. But
then there are a TON of snap.discord.discord denied apparmor messages, a
couple of them point to libreoffice:
Apr 06 19:08:48 pellenor audit[534568]: AVC apparmor="DENIED"
operation="ptrace" profile="snap.discord.discord"
> I have noticed that after trying to launch LibreOffice my system
memory usages goes crazy.
So you fixed the discord issue and then were able to launch your
libreoffice (original deb version) and it displayed?
> I uninstalled the snap version and re-installed via apt. But it still
fails to
I assume when you say "server based spreadsheet" you mean that the
spreadsheet is hosted on a different system than the system you are
using to change the spreadsheet. Can you provide more info on the setup?
Have you seen this issue repeatedly?
I'm removing the tag until more is known and making
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872103
Title:
After update to 6.4.2.2: Split database only accessible while running
in Safe Mode
To manage
** Changed in: libreoffice (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863097
Title:
apparmor messages for libreoffice about mesa
To manage
SejiSensei, do you have a link to the upstream bug you filed? I couldn't
find on in the document foundation that looks related.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870627
Title:
Cannot
*** This bug is a duplicate of bug 1852183 ***
https://bugs.launchpad.net/bugs/1852183
** This bug has been marked a duplicate of bug 1852183
[X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags added: rls-ff-incoming
** Changed in: libreoffice (Ubuntu)
Importance: Undecided => High
** Also affects: libreoffice (Ubuntu Focal)
Importance: High
Assignee: Heather Ellsworth (hellsworth)
Status: Confirmed
--
You received this bug notification because
The problem appears to be only in 6.4.X deb. Here's what I've tested.
* The 6.4.2 snap works probably because we are including the help directly, so
that help opens the actual help rather than directing the user to the web.
* 6.4.2.2 deb = broken
* 6.4.1-0ubuntu1 deb = broken
* 6.4.0-0ubuntu8 =
** Tags added: focal
** Changed in: libreoffice (Ubuntu)
Assignee: (unassigned) => Heather Ellsworth (hellsworth)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869561
Title:
Libreoffice H
I was actually unable to reproduce this.. on a fresh 18.04 vm that was
fully updated, I did a release upgrade to focal and saw that
libreoffice-base-core and libreoffice-common were both upgraded to
6.4.2-0ubuntu3 without any issue.
Robert, did you see this failure when you were doing the release
** Changed in: libreoffice (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874285
Title:
[SRU] libreoffice 6.4.3 for focal
To manage
: libreoffice (Ubuntu)
Importance: High
Assignee: Heather Ellsworth (hellsworth)
Status: In Progress
** Affects: libreoffice (Ubuntu Focal)
Importance: High
Assignee: Heather Ellsworth (hellsworth)
Status: In Progress
** Changed in: libreoffice (Ubuntu)
Assignee
** Changed in: libreoffice (Ubuntu)
Importance: Undecided => Critical
** Changed in: libreoffice (Ubuntu)
Importance: Critical => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875717
Upgraded libreoffice from 1:6.4.2-0ubuntu3 to 1:6.4.3-0ubuntu0.20.04.1
from focal-proposed in a clean and up-to-date focal amd64 VM, and
successfully ran test plan at
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice.
** Tags removed: verification-needed verification-needed-focal
**
The autopkgtest failure was a build hiccup. A relaunch of the test has
passed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874285
Title:
[SRU] libreoffice 6.4.3 for focal
To manage
Public bug reported:
According to the ZFS install testcase:
http://iso.qa.ubuntu.com/qatracker/milestones/412/builds/211063/testcases/1716/results
When installing ZFS, I was never prompted for any security passphrase.
This seems like a major problem.
After the installation, here is the output
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876510
Title:
Print window too big for a 1366x768 screen
To manage notifications about this bug go to:
I've verified that the Alt+X behavior is broken in
6.4.3-0ubuntu0.20.04.1 that is currently in the focal archive. And since
I was testing 6.4.4~rc2-0ubuntu1~ppa1 to prepare for the 6.4.4 release,
I went ahead and was able to easily check that indeed the Alt-X behavior
works in 6.4.4. So stand by
In case anyone else hits this, perhaps this will help...
Another user ran into this very issue on a Debian system but removing
gimp and reinstalling didn't fix the issue.
In order to find the conflicting library, the user removed gimp and it's
dependencies then searched for any remaining
In my investigation, I've found that a local armhf build fails but I do
not see the segmentation fault. To build, I'm just doing `dpkg-
buildpackage -us -uc`. I have the build log but it's 7.5Mb of
uninteresting stuff.. no smoking gun.
--
You received this bug notification because you are a
** Changed in: libreoffice (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893332
Title:
LibreOffice dialogs are garbled
To manage notifications about this
Upgraded libreoffice from 1:6.4.5-0ubuntu0.20.04.1 to
1:6.4.6-0ubuntu0.20.04.1 from focal-proposed in a clean and up-to-date
focal amd64 VM, and successfully ran test plan at
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice.
** Tags removed: verification-needed
Marking this as notfixing since it is not impacting users and should not
be targeted for the release.
** Tags removed: rls-gg-incoming
** Tags added: rls-gg-notfixing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Marking this as notfixing since it is not impacting users and should not
be targeted for the release.
** Tags removed: rls-gg-incoming
** Tags added: rls-gg-notfixing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Marking this as notfixing since it is not impacting users and should not
be targeted for the release.
** Tags removed: rls-gg-incoming
** Tags added: rls-gg-notfixing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Marking this as notfixing since it is not impacting users and should not
be targeted for the release.
** Tags removed: rls-gg-incoming
** Tags added: rls-gg-notfixing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can you please provide your full command used besides the paramaeters in
question? It takes some of the guessing out of the task :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894222
Title:
Thanks for the patch! I was looking at it and noticed that just a few
lines from the bottom there's this:
+export DEB_CFLAGS_MAINT_STRIP DEB_CXXFLAGS_MAINT_STRIP
+export DEB_CFLAGS_MAINT_PREPEND DEB_CXXFLAGS_MAINT_PREPEND
+export DEB_CFLAGS_MAINT_STRIP DEB_CXXFLAGS_MAINT_STRIP
Is that second
Thank you for reporting this issue to help improve Ubuntu!
I've confirmed the issue in a groovy vm with 7.0.2-0ubuntu1, I also
confirmed the issue in a debian testing vm with the upstream 7.0.2.2
packages, and I opened an upstream bug.
** Bug watch added: Document Foundation Bugzilla #137599
Hmm it sounds like something went wrong with the update. Could you
please just try to uninstall all libreoffice packages and then install
LO7 from the ppa?
1. Remove the current libreoffice install
$ sudo apt-get remove --purge libreoffice*
2. Add the ppa and make sure that the libreoffice 7.0
It seems that this bug was already reported upstream
(https://bugs.documentfoundation.org/show_bug.cgi?id=137248) and has
been reported as fixed with a target for the 7.1.0 release.
We can still leave this bug open though to verify it's fix when 7.1.0 is
released.
** Bug watch added: Document
Great idea! I'm currently working on releasing the libreoffice 7.0 snap
so I will add Polish support there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863468
Title:
Libreoffice Snap is not
/<>/dbaccess/source/core/api/StaticSet.cxx: In member function
‘virtual
com::sun::star::uno::Any dbaccess::OStaticSet::getBookmark()’:
/<>/dbaccess/source/core/api/StaticSet.cxx:47:1: internal compiler
error: Segmentation fault
--
You received this bug notification because you are a member of
Was this system installed as a 20.04 and then you just did an apt update and
upgrade?
It sounds like your system is in a funky state with these libreoffice packages
so to workaround it, try remove all libreoffice debs and reinstalling them with:
$ sudo apt-get remove --purge libreoffice*
$ sudo
Can you tell me more? What model of mouse are you using? So you click
save and while the save dialog is up, these mouse buttons don't do
anything - what do you expect to happen?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: libreoffice (Ubuntu)
Status: Confirmed => In Progress
** Changed in: libreoffice (Ubuntu)
Importance: Undecided => High
** Changed in: libreoffice (Ubuntu)
Assignee: (unassigned) => Heather Ellsworth (hellsworth)
--
You received this bug notification be
Public bug reported:
[Impact]
* LibreOffice 6.4.6 is in its sixth bugfix release of the 6.4 line. Version
6.4.5 is currently in focal.
For a list of fixed bugs compared to 6.4.5 see the list of bugs fixed in the
two release candidates:
1 - 100 of 374 matches
Mail list logo