@xnox that's a very good question. What I can say is that Calamares does
look for locales (/usr/share/i18n/SUPPORTED, locale.gen, `locale -a`, in
that order) and certainly does include its own functionality for
choosing through those options. That said, I don't *think* it needs it.
We did take
Looks like the real culprit here is having casper depend upon ubiquity. I
suspect before the removal of udeb packages (including localechooser-data which
was the alternative to the depend otherwise satisfied by ubiquity), we never
ran into this problem simply because of localechooser-data:
Public bug reported:
With bug 1919370 we will be changing from compton to picom. It doesn't
come with a default configuration and though picom can load a
compton.conf, it doesn't support all of its options, so we need to adapt
it accordingly.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package:
Public bug reported:
compton is dead and with the new rewrite/fork picom being packaged, we
should seed this instead.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: lubuntu-desktop 21.04.1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
Public bug reported:
compton's been pretty much abandoned and as such someone took it upon
themselves to fork/rewrite it and that is what has resulted in picom.
picom is partially compatible with compton but it does not support all
of its options. Since Recommends are installed by default,
Suspension is handled by the kernel, not by artwork (and it's buggy
depending on the hardware). Similarly, my guess is that any graphical
issues you had are related to the kernel modules, as well. Either way,
it doesn't seem like this is going anywhere, so Incomplete it is.
** Also affects: linux
Public bug reported:
Right now, we have this great check running at boot that tests the
integrity of various files contained on the ISO. Previously, it
interrupted the boot process but would report to the user whether or not
a failure occurred. Recent changes have made this test silently run in
nm-tray is light and based in Qt, which is great. Its VPN support,
however, is lacking, as you have discovered.
Incidentially, the workaround is discussed in the Lubuntu manual:
https://manual.lubuntu.me/stable/G/AdvancedNetworking.html
** Changed in: nm-tray (Ubuntu)
Status: New =>
I filed a separate report (bug 1918733) about the lack of feedback.
Technically, I would consider this bug fixed unless I'm missing
something.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917590
Public bug reported:
As of 1.460, it seems the file integrity check is now running silently,
which is great. It wasn't working correctly (bug 1917590) but that's now
resolved. Unfortunately, a failed result provides no feedback at any
time to the user.
Additionally, the installer can be run
It seems that 1.460 got the file check up and running again. However, a
failure doesn't result in any feedback to the user. I'm not sure that's
by design or not?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Gee, Thomas, great thinking! I'll get this resolved shortly. :)
** Changed in: lxqt-metapackages (Ubuntu)
Status: New => Confirmed
** Changed in: lxqt-metapackages (Ubuntu)
Status: Confirmed => Triaged
** Changed in: lxqt-metapackages (Ubuntu)
Status: Triaged => In Progress
Actually, this is intended behavior.
** Changed in: lubuntu-meta (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887530
Title:
Dragging icon from start menu
Same with the other bug you filed with VBox and Lubuntu: no Windows, but
can't reproduce.
** Changed in: lubuntu-meta (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok so now I'm less concerned, let's try to figure out how to actually
reproduce this. Clearly an existing partition table is necessary.
** Changed in: calamares (Ubuntu)
Importance: Critical => Undecided
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I don't have Windows 10, but I can't reproduce.
** Changed in: lubuntu-meta (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887681
Title:
Monitor settings
I have a wee bit of a concern that the kpmcore patch we added to get EFI
installs working in Calamares may have had an impact here. I hope not,
but I'm concerned. If that's the case, we may have to throw the latest
Git master of kpmcore in a PPA and rebuild Calamares against it and try
with that.
Michael, I did notice that systemd was complaining in the logs about the
lack of a service file so I think you're on to something.
I'll also add I love the idea of this happening transparently. If we can
actually get that working, even better. That will reduce the skips
significantly.
--
You
Thanks a lot, Heather! Experience tells me the likelihood that patch
will easily apply to older major versions is extremely small. That said,
I'm looking towards the future. Having this report "live" will help us
keep track of things until that time comes. Thanks again!
--
You received this bug
Also /run/casper-md5check.json is missing in the live system, as is
/var/log/installer/casper-md5check.json in the installed system.
Since this is a relatively new problem, I did see this commit, which sounds
like it attempts to continue to boot while the check is running. I wonder if
the
Of course making it Won't Fix will render this bug all but invisible,
though, and there are future release versions to consider. I don't want
to get into a status war especially given I'm not in the LibreOffice
team, but I'm sure this won't ever come up on my radar again given that
status. Even
** Changed in: casper (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917590
Title:
File integrity check at boot of install media no longer functional
To
I note here that CasperMD5CheckResult is unknown, which is to say that
no skip or fail has been recorded. In that sense, it would seem that the
check didn't even run. We certainly can't use it to verify ISO integrity
in bugs, and in that sense, I'd call this a pretty problematic
regression.
**
So our script for installing the EFI signed packages could use a
refactor. If it was properly constructed, **assuming Internet was
available**, one could have gotten around this issue. Right now, it
forces the assumption that there is no Internet, so some small blame can
be placed there.
One can
** Changed in: calamares (Ubuntu)
Status: New => Confirmed
** Changed in: calamares (Ubuntu)
Importance: Undecided => Critical
** Changed in: calamares (Ubuntu)
Milestone: None => ubuntu-21.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It seems that 1ubuntu37 comes from the ship-live seed (i.e. on the ISO)
while 1ubuntu40 is from the repos. Oddly, it seems to want to prefer the
former? Still, I don't know why we have an outdated package.
** Summary changed:
- Lubuntu Hirsute daily install failed -external command finished
Sorry for all the comments. Anyways, this is probably not a Calamares
bug. Calamares may be contributing but a stale package on the ISO is a
much bigger problem. Unfortunately, I'm not sure where the problem lies
so I'm not entirely sure where to file it against. I've asked at
#ubuntu-release and
Public bug reported:
Look at https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1917292
and you'll see the session.log is nearly devoid of information.
It seems that somewhere along the way (probably
https://github.com/calamares/calamares/commit/631923abf8c06289139895dbae96b07a547b550e)
Not sure what's up with the Calamares logs, but the full error is:
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
Flipped to Fix Committed from Fix Released for libreoffice in Ubuntu
since even Hirsute is still stuck on 7.0.4 and I'm not sure even +1 will
have 7.1.x, let alone 7.2.x.
** Changed in: libreoffice (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification
That's the default setting and I can't reproduce it.
** Changed in: pcmanfm-qt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916260
Title:
PCManFM-Qt
I could imagine that a failure in the bus could result in similar
behavior since the settings are device-based and not general. In other
words, if you had 5 touchpads, you'd really have 5 different natural
scrolling options to select. So if you have deviceX and the bus has a
hiccup, causing the
Something is really weird here, even outside of what problem there MAY
be with obconf-qt.
The setting for this in the Openbox config is
`yes` which is a default part of
the Lubuntu configuration (and technically Debian and upstream Openbox,
too).
The option is relatively new as previous
Excellent. Thanks for the confirmation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905947
Title:
lubuntu hirsute: display configuration doesn't survive logout/reboot
To manage notifications
Sounds like this is fixed. Thanks Chris!
** Changed in: lxqt-config (Ubuntu)
Status: Confirmed => 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/1905947
Title:
lubuntu hirsute:
Nevermind that test I mentioned; leok already figured it out. ;)
** Description changed:
See attached bugs for longer explanation but basically due to some
changes in core software (dosfstools) EFI installs fail to create
partitions because a null label is no longer acceptable. There is
If it "fixed itself" perhaps a little log out/on was all that's needed.
Marking as incomplete unless we have clear steps to reproduce.
** Changed in: pcmanfm-qt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It should be apparent that this affects EFI only. I wouldn't expect
secure boot or not to make a difference. Either way, let's hold off on
reporting any results on this for a bit.
The only one thing I'm thinking that might be worth testing is whether
or not manual partitioning with labels set on
You're looking at it all too much like a human :) There's a lot of stuff
going on under the hood that you may not realize is apparently a
necessary part of making your software work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It's on the development branch, so I wouldn't be surprised you have bugs
in general with any software.
Also, speaking with my Community Council hat on, the goal for the
community is to be inclusive and welcoming to all, so using language
that no one would consider offensive would be great.
I need exact steps to reproduce this, starting with required conditions.
This has been so elusive because of that.
** Changed in: calamares (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
P.S. added Hirsute and Groovy tags since the latest dupe shows it
affects Hirsute and thus should affect Groovy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795278
Title:
Michal, that's not how patching works, unfortunately. You can put all
that in a file and use the `patch` command. The easy way is to go to the
folder containing the file and run `sudo patch < /path/to/diff`.
Or you could simply edit the file (/usr/lib/python3/dist-
*** This bug is a duplicate of bug 1795278 ***
https://bugs.launchpad.net/bugs/1795278
Were you to `lxqt-sudo software-propreties-qt` you would see that this
is a duplicate of the other bug. Technically, it's got a fix. You might
want to try testing it and maybe we can actually get this
Upstream has this fixed:
https://github.com/calamares/calamares/commit/b9210721e6e8828c712fde33bc52406a0892236e
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909506
Title:
lubuntu hirsute daily
One other thing: "scrollingMethodEnabled=0" disables scrolling, natural
(it's not, IMHO) or not. That's typically for trackpads and so with a
normal mouse all of the other options would be greyed out, and in that
sense, the "disabled" option is more like "not applicable," but you
actually have a
Ah yes, you're right. That's rather remarkable. I wonder if you don't
have some sort of permissions issue or something. I would suggest
deleting the file, logging out and back in again. It should regenerate
the config.
I should also mention one other thing: I wouldn't recommend ever editing
any
Unfortunately without any information on what process changed it, all
that tells us is that something happened. So that number before the
colon in parentheses after audit is the date/time in based on the Unix
epoch. There are a bunch of ways to convert that to normal time. That
said, looking at
There is literally no folded for 48 icons the mimetype context. Didn't
check others, but that seems like an oversight.
** Package changed: pcmanfm-qt (Ubuntu) => breeze-icons (Ubuntu)
** Changed in: breeze-icons (Ubuntu)
Status: New => Confirmed
--
You received this bug notification
I wonder if this doesn't happen as a consequence of re-doing working
when specifying the partitioning scheme? If so, then it's a *REALLY*
minor bug. Otherwise, there's some validity to fixing it. However, if
this can't be reproduced in Groovy or Hirsuite, I wouldn't worry about
it, I'd just call
** Changed in: calamares (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864787
Title:
Lubuntu failed install "sfdisk --force --append /dev/sda"
To
Should be fixed as of Groovy and beyond as the fix came out in 3.2.24.
** Changed in: calamares (Ubuntu)
Status: Triaged => 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/1865955
I just checked this and I can confirm that it is still affecting Focal,
which is consistent with the fact that the upstream bug has not been
updated. Look at the picture in the upstream issue and it should be
clearer. Also the other two conditions of expected results aren't met.
** Tags added:
** Description changed:
STEPS TO REPRODUCE
1. Select manual partitioning
2. Select a partition
3. Click "Edit"
4. Click the "Format" radio button
5. Click "OK"
6. Note anywhere that formatting is mentioned
7. Select the partition
8. Click "Edit"
9. Click the "Format"
** Changed in: calamares (Ubuntu)
Status: New => Triaged
** Description changed:
STEPS TO REPRODUCE
- 1. Select manual partitioning
- 2. Select a partition
- 3. Click "Edit"
- 4. Click the "Format" radio button
- 5. Click "OK"
- 6. Note anywhere that formatting is mentioned
- 7.
BTW I happened to have an Eoan VM laying around and tested it out and
found the same problem. so this has actually been long standing. We'll
see what upstream says.
** Package changed: lxqt-admin (Ubuntu) => lxqt-policykit (Ubuntu)
** Changed in: lxqt-policykit (Ubuntu)
Importance: Undecided
Well, I've confirmed this with the latest upstream sources.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875774
Title:
Lubuntu 20.04 lxqt-admin-user Action (usermod) failed
To manage
So the steps to reproduce this are somewhat unclear, so let me know if I
did anything wrong:
1. Boot fresh installation of Lubuntu 20.04
2. Use lxqt-admin-user to create a second user (let's call it user2)
3. Use lxqt-admin-user to add user2 to sudo
4. Logout and back in again (yes, this is a
I'm pretty sure this is not a duplicate as no one else on the other bug
mention the general protection fault you're seeing.
However, I'm also not sure this is a bug, either.
I installed synaptic (why not just use Muon? it's the same thing—an apt
frontend—and comes with the install) and ran
Would love to but we've got more bugs than bug triagers. We welcome
contributions, though!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905483
Title:
Lubuntu installer cannot deal with a virgin
Oh, actually, looking deeper, I didn't notice you were on 19.10 to begin
with. I'm not sure that we were enforcing file checks then. My comment
is still relevant though.
If you can confirm that you did indeed verify the hashes of both the ISO
and installation media, then perhaps the next step
Well, I do see one rather concerning part of your bug report:
CasperMD5CheckResult: skip
This means that you didn't allow the system to check the files being
installed, which is to say you may have a corrupt installation.
Did you verify hashes of the ISO/installation media in some way? If not,
So what I'm hearing you say is it's a behavior that happened but upon
filing the bug report is no longer a problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910934
Title:
lxqt loses natural
"Seems" is the appropriate word. The reality is, it's long resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905483
Title:
Lubuntu installer cannot deal with a virgin disc.
To manage
Confirmed and tested with upstream Git master. Seems the issue is
specifically with the Win+Space shortcut. Other Win shortcuts are no
problem. Also the issue is getting *out* of certain layouts. Set Persian
as default and English to second and you can't switch at all. English
first, Persian
** Project changed: lubuntu-artwork => pcmanfm (Ubuntu)
** Changed in: pcmanfm (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750262
Title:
Lubuntu:
Assuming this is no longer valid and setting incomplete.
** Changed in: calamares (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869292
Title:
lubuntu
Until the associated upstream bug is fixed (which is ultimately a
problem with the XDG implementation in LXQt), this should continue to
happen in all releases, Focal and otherwise. We DO have the right
setting in the Desktop Entry, so once it is fixed upstream, packaged,
and released in Ubuntu,
I'm going to assume this is no longer relevant but please let me know if
not.
** Changed in: calamares (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864791
Actually, I can confirm this in the latest daily.
If you kill pcmanfm-qt and run `pcmanfm-qt --desktop` on the background,
on double click, you'll get the following:
sh: 1: exec: xterm: not found
I do notice that our configuration for file for libfm suggests
lxterminal, so that's a problem that
** Changed in: pcmanfm-qt (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827415
Title:
In Lubuntu 19.04, a file does not open on double-click when vim
Unfortunately, without clear steps to reproduce, detailed information
about your hardware, and system logs, it's hard to take any sort of
action.
To try to resolve this issue, please execute the following command only once,
as it will automatically gather debugging information, in a terminal:
** Changed in: lxqt-metapackages (Ubuntu)
Status: New => Incomplete
** Package changed: lxqt-metapackages (Ubuntu) => lxqt-config (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910934
To add to that, it looks like the way to implement that is
`NotShowIn=LXQt` in lubuntu-default-settings but we've got
https://github.com/lxqt/lxqt/issues/1743 keeping that from working.
** Bug watch added: github.com/lxqt/lxqt/issues #1743
https://github.com/lxqt/lxqt/issues/1743
--
You
Well, I mean, I guess we don't make any release notes about the fact
that the other two sessions (Openbox, LXQt) will look and act really
weird relative to what one expects for Lubuntu, so I'm inclined to leave
it be. I'm open to thoughts on the matter, though.
--
You received this bug
Ugh that comment was meant for another bug. Please ignore #4.
** No longer affects: calamares
** Bug watch added: Calamares Issues #1613
https://github.com/calamares/calamares/issues/1613
** Also affects: calamares via
https://github.com/calamares/calamares/issues/1613
Importance:
I'm surprised this hasn't come up before. I'm expecting to get someone
telling me this is a duplicate upstream, but I couldn't find a similar
issue, so we'll see.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So that is the Desktop Entry that comes with Calamares rather than being
our Ubuntu-specific one. Kind of like the Openbox session that comes
with Openbox, we don't exactly support it. That said, we have
`NotShowIn=LXQt` in it to keep it from showing up, but that's
misbehaving (see linked
So that is the Desktop Entry that comes with Calamares rather than being
our Ubuntu-specific one. Kind of like the Openbox session that comes
with Openbox, we don't exactly support it. That said, we have
`NotShowIn=LXQt` in it to keep it from showing up, but that's
misbehaving (see linked
It's remotely possible that we might SRU this, so it might end up
appearing in further point release ISOs, but I'm not very much in favor
of it.
Meanwhile, the "fix" will be updated release notes, which is in progress
as we speak.
Going forward, we're going to look into some mechanism to update
So I apologizing for the invalid status on the previous bug. I think it
was a bit premature, although it may be appropriate after all. Let me
explain a bit.
First off, as you can see in the issue, the problem was one specific to the
GeoIP provider we were using, ipapi.co:
Am I correct that this is only problematic in Focal? Groovy and Hirsute
are fine?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908846
Title:
lubuntu focal.2 calamares fails to parse GeoIP results
Hibernation seems to be poorly supported overall:
https://discourse.ubuntu.com/t/re-visiting-hibernate-on-ubuntu/15953
That said, the right "solution" here is likely to remove the hibernate
option from the shutdown options altogether.
--
You received this bug notification because you are a
Oh and Lubuntu is tracking this here:
https://phab.lubuntu.me/T181
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857364
Title:
group sambashare with gid 1000
To manage notifications about this
This was fixed in a recent version of Calamares which should be landing
in Hippo soon.
** Changed in: lubuntu-meta (Ubuntu)
Status: Confirmed => Fix Committed
** Package changed: lubuntu-meta (Ubuntu) => calamares (Ubuntu)
--
You received this bug notification because you are a member
I think you meant to link to the section about platform compatibility on Linux
and how file:/// links are no longer silently treated as smb:/// links:
https://wiki.documentfoundation.org/ReleaseNotes/7.0#Linux
I am pretty sure that's a non-issue in PCManFM-Qt.
--
You received this bug
I'm not entirely surprised at the read only thing (see
https://ask.libreoffice.org/en/question/3827/doc-files-open-as-read-
only/) though I'm a little surprised about the inconsistent behavior
that under some file managers that happens and under others, it doesn't.
That's not really relevant here,
So clearly the problem here is with Thunar and PCManFM-Qt, at least
something about how they handle the Samba connection that makes
LibreOffice (and only LibreOffice, apparently) unhappy.
So I have three thoughts:
1. Connect to the Samba share manually. This way we're not relying on
the logic
I just installed file-roller in Lubuntu, switched the archiver
integration, and again, both methods worked fine.
So I can think of three other possibilities:
1. I didn't think of this before but I guess it's possible there might
be something wrong with the zip file in some way. You might want
Using Lubuntu (where pcmanfm-qt is the default file manager) 20.04, I
had no problems with either method.
Lubuntu uses the "ark" archiver integration (see advanced preferences)
and none of the other ones work by default because none of the other
archivers are installed by default. If you are
** Changed in: pcmanfm-qt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908293
Title:
"extract here" doesn't work
To manage notifications about this bug
I wonder…
1. if you use pcmanfm-qt or thunar in any of the flavors, does it fail?
2. if you use one of the other file managers (say, nautilus or caja) in
Lubuntu or Xubuntu, does it succeed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Leó your steps to reproduce require using pcmanfm-qt, the default file
manager for Lubuntu. In testing on other desktop environments (including
Qt-based ones like KDE which uses Dolphin for the default file manager),
did you indeed use pcmanfm-qt or did you use the default file manager?
--
You
Also, have you checked other flavors besides Lubuntu, Xubuntu, Ubuntu
and Ubuntu Mate?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875717
Title:
Opening file from Samba share results in Document
Long story short: Lubuntu wants to use the qt5 VCL but we continue to
discover more and more areas where the functionality is incomplete still
relative to the other options.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So this is a non-issue, like the Lubuntu one, too? Perhaps this was
really a transitory problem in the state of packages overall and not due
to a software update mechanism at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So what I'm hearing you say is there is no issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904269
Title:
Apply full upgrade - fails with no error message
To manage notifications about this
Leó are those comments re: Xubuntu and Ubuntu Budgie using some other
updating mechanism beyond Discover? I presume so, in which case, it
should affect *ALL* flavors including canonical Ubuntu Desktop. In that
case, we need to refile this.
--
You received this bug notification because you are a
So it sounds like this is affecting Groovy, right, Chris? What about
Hirsuite?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864787
Title:
Lubuntu failed install "sfdisk --force --append /dev/sda"
For one, I think we should avoid the Snap, as the author of bashtop
doesn't recommend it as an installation method. Furthermore, the author
of the Snap is different.
Secondly, the author does recommend Qterminal, at least as one with true
color support.
It also seems to be really particular
1 - 100 of 1423 matches
Mail list logo
