Ah, that's what I was looking for, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971559
Title:
After Ugrade, Jammy requires me to create a new user, although users
are present
To manage
> Non system accounts flagged as systemuser should perhaps could as an
existing user in that logic even if they aren't explicitly displayed?
I'd expect that to depend very much on the installation at hand (in our
case it would), but that can't be decided programmatically. I'd opt for
a way of
Sebastien, thanks for your reply.
First of all, considering that this is a somewhat special (though not unlikely)
setup on our side, you may demote this bug from importance high to lower. This
is to remove strain on you developers, this bug will only concern special
institutional setups like
Behaviour in 20.04 was like it is in 22.04: Once I went through the
dialog and created one no-system user, the login screen shows all
accounts not listed as "system". I.e. all of our LDAP users (which are
the only ones relevant to our users).
I manually marked those accounts as system, to have
Indeed, all local accounts are marked as system accounts, because they
all serve administrative uses in one way or the other, and shall not be
seen by normal users.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
root@rechner2-3-12:~# /usr/libexec/accounts-daemon --debug
(accounts-daemon:9005): DEBUG: entering main loop
(accounts-daemon:9005): DEBUG: Changing permission of
/var/lib/AccountsService/users/vorlage to 0600
(accounts-daemon:9005): DEBUG: Changing permission of
root@rechner2-3-12:~# cat /var/lib/AccountsService/users/linadmin
# do not show user in greeter
[User]
SystemAccount=true
Ah! This could be it! lindamin is marked as SystemAccount, because our users
shall not see it in the list of accounts on the login screen …
--
You received this bug
Don't know if this helps:
root@rechner2-3-12:~# ps -ef|grep initial
gnome-i+20441829 0 08:20 tty1 00:00:00 /usr/libexec/gdm-x-session
dbus-run-session -- gnome-session --autostart /usr/share/gdm/greeter/autostart
--session gnome-initial-setup
gnome-i+20812044 0 08:20 tty1
linadmin is definitely a user with ultimate sudo rights:
root@rechner2-3-12:~# sudo -U linadmin --list
Passende Defaults-Einträge für linadmin auf rechner2-3-12:
env_reset, mail_badpass,
secure_path=/usr/local/sbin\:/usr/local/bin\:/usr/sbin\:/usr/bin\:/sbin\:/bin\:/snap/bin
Der Benutzer
Yes, system is still in this state. I went through the dialog once and created
a user. After that the machine booted into th login screen and worked. Then I
removed the new user with "deluser" and at next boot I was back at the dialog.
So, yes, it appears the code does not detect that there are
/bin/bash is availble, I can su to linadmin and even connect as linadmin
by ssh.
Journal is attached.
** Attachment added: "journal"
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+attachment/5587019/+files/journal
--
You received this bug notification because
root@rechner2-3-12:~# grep linadmin /etc/passwd
linadmin:x:1000:1000:Linux-Administrator,,,:/home/linadmin:/bin/bash
/home/linadmin is a local directory and linadmin is a locally configured
user, no LDAP account.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The local user with sudo rights has uid 1000:
root@rechner2-3-12:~# id linadmin
uid=1000(linadmin) gid=1000(linadmin)
Gruppen=4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),113(lpadmin),128(sambashare),1000(linadmin)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: "image20220505_082109516.jpg"
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+attachment/5586888/+files/image20220505_082109516.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That's the dialog.
** Attachment added: "image20220505_082026251.jpg"
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+attachment/5586887/+files/image20220505_082026251.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sorry, I'm far from that machine at the moment, but I'll try describing:
- Desktop environment: GNOME (standard Ubuntu Desktop)
- I don't see the login screen, Ubuntu boots through to the desktop and shows
the dialog.
- dialog fills almost the whole desktop and nothing can be done except
Not sure if ubiquoty package is the right place, please change if
necessary.
** Package changed: ubuntu => ubiquity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971559
Title:
After
Public bug reported:
I upgraded from 20.04 to 22.04 using "do-release-upgrade". At reboot, I
see a kind of "first-run wizard" requiring me to create a new user and
her profile. The dialog cannot be canncelled or skipped.
There is no need creating a new user: there are already local users with
I ran into this problem today with LO Version: 6.4.7.2. (Both the
crashes and the jagged, flickering transitions.) Is it possible that
this was never fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Addition to #5: Fluffychat seems to have solved how to do that: once in
a while it slips in reminders as a circle message and this message
always appears first after boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
See also
https://github.com/ubports/ubuntu-touch/issues/1391#issuecomment-600214923.
It suggestes using the "circle message" app in order to display emergency data
on the lock screen. However, it is not very useful if the message is not shown
directly after boot.
** Bug watch added:
I'd like to add that it would be useful if one could customize the order
of messages displayed. Especially which message is displayed right after
bootup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Still a very good idea.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458336
Title:
Allow users to decide which apps can display anything in the circle
To manage notifications about this bug go
Is this issue related to Bug #1890905?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856738
Title:
access always denied when using @{HOME} tunable in peer_addr for
abstract socket
To manage
(Sorry for the double posting.)
Yes, I now see how this is to be meant, but it's not a direct popup but what
you see when you select "Main Window" *from* the popup menu. – Anyway,
unrelated to this issue, you are right, thanks!
--
You received this bug notification because you are a member of
Interesting. Here's how it looks on my desktop. The netcloud window
disappears as soon as I click anywhere on the desktop.
** Attachment added: "Bildschirmfoto von 2021-04-26 20-35-20.png"
Interesting. Here's how it looks on my desktop. The netcloud window
disappears as soon as I click anywhere on the desktop.
** Attachment added: "Bildschirmfoto von 2021-04-26 20-35-20.png"
nextcloud-desktop is back in hirsute-proposed, testing. Here's what I see:
The client starts up and sync seems to work, but the main window ist next to
unusable. Window shows, but has no title bar. Erratically, it switches to some
text output and back again. The window cannot be moved, unless
All right, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923053
Title:
[SRU] nextcloud crashed with SIGSEGV.
To manage notifications about this bug go to:
I can't find the package in proposed, what happened?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923053
Title:
[SRU] nextcloud crashed with SIGSEGV.
To manage notifications about this bug go
Package from Butterfly (kelebek333) works with Hirsute. Thanks for the
work, guys!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916640
Title:
Nvidia 340.108 fails to install with kernels 5.11.x
Your are right that Chromium seems often affected, but this is by no
means limited to Chromium. See next screen shot, where Document Viewer
(evince) is affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Evince showing distorted graphics"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+attachment/5446243/+files/Bildschirmfoto%20von%202020-12-23%2012-06-11.png
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "Bildschirmfoto von 2020-11-24 12-21-43.png"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+attachment/5445242/+files/Bildschirmfoto%20von%202020-11-24%2012-21-43.png
--
You received this bug notification because you are a member of
** Attachment added: "Bildschirmfoto von 2020-11-25 19-15-41.png"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+attachment/5445241/+files/Bildschirmfoto%20von%202020-11-25%2019-15-41.png
--
You received this bug notification because you are a member of
** Attachment added: "Bildschirmfoto von 2020-11-25 19-16-06.png"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+attachment/5445240/+files/Bildschirmfoto%20von%202020-11-25%2019-16-06.png
--
You received this bug notification because you are a member of
** Attachment added: "Bildschirmfoto von 2020-12-02 20-30-48.png"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+attachment/5445239/+files/Bildschirmfoto%20von%202020-12-02%2020-30-48.png
--
You received this bug notification because you are a member of
** Attachment added: "Bildschirmfoto von 2020-12-03 15-17-09.png"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+attachment/5445238/+files/Bildschirmfoto%20von%202020-12-03%2015-17-09.png
--
You received this bug notification because you are a member of
** Attachment added: "Bildschirmfoto von 2020-12-03 15-17-46.png"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+attachment/5445237/+files/Bildschirmfoto%20von%202020-12-03%2015-17-46.png
--
You received this bug notification because you are a member of
Public bug reported:
On my Thinkpad T61 using Nvidia 340.108 driver, I regularly see graphics
distortions returning from suspend. (Not completely sure if it also
appears after screen lock.)
See attached screen shots.
** Affects: nvidia-graphics-drivers-340 (Ubuntu)
Importance: Undecided
I'm sorry to say we were forced to move from Chromium to Google Chrome
(unconfined deb package). I am not at all happy with that, as our software is
now less secure than it was before (with the unconfined Chromium). But I never
managed to get the snap running for my users, snaps are just not
On my Thinkpad T61 I still see garbled screen content resuming from
sleep. Is this to e expected, or are will still missing some patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872950
Title:
Thanks, that worked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872950
Title:
Nvidia 340.108 fails to install with kernels 5.5 onward
To manage notifications about this bug go to:
Missing depedencies?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903729
Title:
Fails to start in xenial
To manage notifications about this bug go to:
Public bug reported:
CDalling pylang in a recent xenial install yields:
```
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/pylang/pylang.py", line 20, in
from view.pylang import Practice
File "/usr/lib/python2.7/dist-packages/pylang/view/pylang.py", line 20,
Confirming: 340.108-0ubuntu5.20.10.1 installs, compiles and runs.
It does however compain:
> /var/lib/dkms/nvidia-340/340.108/source/dkms.conf: Zeile 16:
> PATCH{7]=do-not-call-pci_save_state.patch: Befehl nicht gefunden
(/var/lib/dkms/nvidia-340/340.108/source/dkms.conf: line 16: PATCH{7
This patch needa the /kernel/ path prefixes removed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896878
Title:
Doesn't compile for groovy
To manage notifications about this bug go to:
Here's how to resolve the issue:
- put the two patches above into /usr/src/nvidia-340-340.108/patches/
- modify /usr/src/nvidia-340-340.108/dkms.conf:
- remove any PATCH[] lines
- add
PATCH[0]="kernel-5.7.patch"
PATCH[1]="0002-kernel-5.8.patch"
- dpkg --configure nvidia-340
--
You
Here's how to resolve the issue:
- put the two patches above into /usr/src/nvidia-340-340.108/patches/
- modify /usr/src/nvidia-340-340.108/dkms.conf:
- remove any PATCH[] lines
- add
```PATCH[0]="kernel-5.7.patch"
PATCH[1]="buildfix_kernel_5.8.patch"```
- dpkg --configure nvidia-340
--
You
** Patch added: "patch for kernel-5.8"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1896878/+attachment/5427736/+files/0002-kernel-5.8.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Answering my own question:
No, this was the wrong file. I extracted the right one from the gut repository
here:
https://aur.archlinux.org/pkgbase/nvidia-340xx/
Needed to adjust the paths in the .patch file, but now it works.
Attaching the adjusted patch.
--
You received this bug notification
@satmandu: buildfix_kernel_5.8.patch is no longer accessible via the link you
mention. Is this the same patch as mentioned here? (002-kernel-5.8.patch)
https://aur.archlinux.org/packages/nvidia-340xx
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Please, can this be fixed in time? Users on hardware that requires this driver
have no other option: either this works or they are left with an anusable
system (like myself right now).
This is a »leave-Ubuntu«-impulse for everyone affected.
Please!! Fix this.
--
You received this bug
*** This bug is a duplicate of bug 1896878 ***
https://bugs.launchpad.net/bugs/1896878
Thanks for redirecting!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901493
Title:
fails to build on
Public bug reported:
nvidia-340 fails to build after update to 20.10. Attaching crash log.
Note: This is fatal on the Thinkpad T61. Desktop does not start.
apt-cache policy nvidia-340
nvidia-340:
Installiert: (keine)
Installationskandidat: 340.108-0ubuntu5
Versionstabelle:
Sorry, I mixed up `.cache` and `.config` in the bug description
(corrected).
I originally found this problem referring to the users CACHE directory.
But as ibus needs both, .cache and .config, it is to be expected that
the same problem appears when users' CONFIG is relocated (wich is as
easily
I gave up on Firefox. Switched to Chromium instead. I'm sorry, but you
need to take action at some time (and time means: 7 years and 10 months
since I reported this). I hope the Firefox community can work this out,
I am not longer part of it.
--
You received this bug notification because you are
Attaching relevant portions from journalctl: Once with and without
XDG_CACHE_HOME set. Each time I launched the chrome snap, typed some
keys, and quit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Log with XDG:CACHE_HOME unset (working)"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1890905/+attachment/5400722/+files/log-working
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Log with XDG:CACHE_HOME set (not working)"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1890905/+attachment/5400723/+files/log-notworking2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
This is a follow-up to #1580463. (Note: I am not an expert in snap or
apparmor related things, please correct me in anything I say below,
thank you ;-).)
Bug #1580463 dealt with a problem in snaps achieving a correct path for
accessing IBus and has since been
For your reference: Bug #1890905
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580463
Title:
Snap blocks access to system input methods (ibus, fcitx, ...)
To manage notifications about this bug
** Description changed:
This is a follow-up to #1580463. (Note: I am not an expert in snap or
apparmor related things, please correct me in anything I say below,
thank you ;-).)
Bug #1580463 dealt with a problem in snaps achieving a correct path for
accessing IBus and has since been
Cross references:
- https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463/comments/39
indicating that /home/* may be hard coded for snap access (breaking the
freedesktop.org specs)
- https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463/comments/40
stating that this *should* have
Public bug reported:
This is a follow-up to #1580463. (Note: I am not an expert in snap or
apparmor related things, please correct me in anything I say below,
thank you ;-).)
Bug #1580463 dealt with a problem in snaps achieving a correct path for
accessing IBus and has since been closed as
Agreed. I'll be referencing this issue there. And I'll have a look into
the journal, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580463
Title:
Snap blocks access to system input methods
We are talking about recent Ubuntu focal, thst is: Ubuntu 20.04.1. This
is deemed safe for LTS upgrade! It is not! It will make petfectly
working installs of 18.04 LTS unusable without any warning.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This will affect many installs, notably in professional multi user
environments. It is absurd assuming that $XDG_CACHE_HOME is unset (any
installation with a few hundred users will have homes on a network share
and consequently caches moved elsewhere).
--
You received this bug notification
Test case: chromium snap with $XDG_CACHE_HOME set.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580463
Title:
Snap blocks access to system input methods (ibus, fcitx, ...)
To manage
Our $XDG_CACHE_HOME points to /var/cache/usercache//
I tried adding /var/cache/usercache/ to @{HOMEDIRS} in apparmor, but it did not
work. How do I tell my snaps that user caches are in /var/cache/usercache/ ??
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This is *not* fixed. I still see this issue in a recent install of Ubuntu
20.04, where $XDG_CACHE_HOME is set.
We have home dirs mounted via network, so user caches were moved to local
storage to sanitize network load. The right and perfectly valid way of doing so
is setting $XDG_CACHE_HOME.
@akkzilla is right, this is more like a problem of general
intercommunication of snaps. It probably needs a decent framework for
snaps as a whole, not only the chromium snap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Snaps do have that concept of plugs and sockets. Shouldn't that be the
way of solving this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776873
Title:
Whitelisted allowedURLschemes breaks some
Jusr wanted to comment on Samuele Pedroni referring to "rudeness" – then
I saw that Balazs Gyurak already did: Yes, I saw the comment that has
subsequently been removed from this forum post, and Samuele was
completely right to object. Please remove this part of your article.
--
You received this
*** This bug is a duplicate of bug 1776873 ***
https://bugs.launchpad.net/bugs/1776873
Thanks for referring!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871844
Title:
[Snap] xdg-open not
Public bug reported:
Several services register handlers for opening links in their external
applications (examples: zoom.us, Microsoft Teams). Following a link to
the respective content makes chromium display a box asking if xdg-open
should be called. When I choose yes, nothing happens at all.
Still true on 19.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1598665
Title:
Option "use this connection only for resources on its network" not
respected
To manage notifications about this
Sorry, my reply got lost in conversation.
Yes, I did set disable-user-list=true. Thanks for pointing me to the red
hat bug report, that's obviously the same bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- TimedLogin feature not working in Ubuntu 18.04
+ TimedLogin feature not working when user list is disabled
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856289
Title:
Public bug reported:
In Ubuntu 18.04.3, gdm3's TimedLogin feature is not working.
Steps to reproduce:
In /etc/gdm3/custom.conf, uncomment these lines
TimedLoginEnable = true
TimedLogin = user1
TimedLoginDelay = 10
and change "user1" to an exiting user name. Reboot. Observe that nothing
I do not use the respective hardware any longer, but it still exists.
Going to test it if I find the time. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839019
Title:
bringing up 10ec:8185
Hello Chris Guiver,
I am not currently using Lubuntu on any device, so I cannot easily test if the
problem still exists. User deutrino could have more information.
@deutrino: Has the bug reached attention upstream? Is it still present
in recent Lubuntu installs?
--
You received this bug
Well, at least Suma Byrappa is the person that has this bug assigned,
and Amarnath Chitumalla is listes as "may be notified" on this page. The
two should probably know the answer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Is the hpcups driver actually being maintained by HP? Or is this a
community driver?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036236
Title:
hpcups and hpijs driver use different rasterization
For the record: Upstream bug is at
https://bugs.launchpad.net/hplip/+bug/1036236. But projects are linked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036236
Title:
hpcups and hpijs driver use
Hello J T,
thanks for reporting that this is still a problem. I had originally filed this
report in 2012, but since it never moved forward I just resigned and kept using
the HPIJS driver, which produces much better (in terms of visually accurate)
output. However, Till Kamppeter says that Ubuntu
@torzsmokus
> the Activities (and the hot corner) on the secondary display shows windows on
> all workspaces
I had noticed that too, but it appears this bug was fixed. I cannot
reproduce it in a current Ubuntu Cosmic install.
--
You received this bug notification because you are a member of
This bugh is no longer present in recent Ubuntu. Thanks for caring,
Paul.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1502644
Title:
nm-applet frequentyl fails with broadband activated
To manage
Na problem, here it is:
https://bugs.documentfoundation.org/show_bug.cgi?id=121927
** Bug watch added: Document Foundation Bugzilla #121927
https://bugs.documentfoundation.org/show_bug.cgi?id=121927
** Also affects: df-libreoffice via
I don't know if the bug is related to the snap. Probably not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806385
Title:
[snap] Creating new slide by double click not working correctly
To manage
Public bug reported:
Version: 6.1.3.2
Build-ID: libreoffice-6.1.3.2-snap1
You can create new slides in impress by double clicking on the empty
part of the slides pane (below the existing slide). However, this works
only as expected while the slides pane actually has empty space at the
bottom.
For me, the file opens in impress. I see only one (incomplete) slide, as
shijing described.
Version: 6.1.3.2
Build-ID: libreoffice-6.1.3.2-snap1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393688
Thanks Olivier, I see the potential leak. However, it makes LO somewhat
less useful for me, because I very frequently access files form the
recently used list. All in all, it seems that the question is, how snaps
can be integrated into a desktop shell so as to give the user a flawless
experience
For me, this disrupts the daily workflow with LO to an extent where I
consider changing back from the snap to deb.
** Summary changed:
- [Snap] Documents opened with linbreoffice snap do not appear in "recent
files" list of nautilus
+ [Snap] Documents opened with libreoffice snap do not appear
Public bug reported:
I'm not sure of it's nautilus or Gnome shell keeping the list of recent files.
I#m talking about this file:
~/.local/share/recently-used.xbel
It usually contains all recently used files. However, if you open some file
with the libreoffice snap, it won't get added to this
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1036168/+attachment/5201257/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Locale.txt"
https://bugs.launchpad.net/bugs/1036168/+attachment/5201258/+files/Locale.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036168
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1036168/+attachment/5201256/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello,
interestingly, the problem still exists in bionic. There are two "advanced
options", "print-color-ode" and "job-cancel-after" that cannot be removed or
changed (as meilan pointed out above).
** Tags added: apport-collected bionic
** Description changed:
Drivers:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1036168/+attachment/5201266/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036168
1 - 100 of 844 matches
Mail list logo
