[Bug 1923881] Re: Lubuntu and Ubuntu Studio Hirsute incorrectly launch Ubiquity installer

2021-04-14 Thread Walter Lapchynski
@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 today's image and removed all the ubiquity-* packages, ran
Calamares, and it seemed like everything worked just fine. So I guess
you could make the depend calamares | ubiquity but that seems rather
bizarre to me. I mean, after all, the issue here is that the installer
requires this, right? So why not have casper depend on no installer and
make the installer have the dependency?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923881

Title:
  Lubuntu and Ubuntu Studio Hirsute incorrectly launch Ubiquity
  installer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1923881/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1923881] Re: Lubuntu and Ubuntu Studio Hirsute incorrectly launch Ubiquity installer

2021-04-14 Thread Walter Lapchynski
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:
https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1923833

** Package changed: calamares (Ubuntu) => casper (Ubuntu)

** Changed in: casper (Ubuntu)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923881

Title:
  Lubuntu and Ubuntu Studio Hirsute incorrectly launch Ubiquity
  installer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1923881/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919371] [NEW] picom needs a sane default configuration

2021-03-16 Thread Walter Lapchynski
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: lubuntu-default-settings 21.04.3
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu60
Architecture: amd64
CasperMD5CheckMismatches: ./casper/filesystem.manifest
CasperMD5CheckResult: fail
CasperVersion: 1.460
CurrentDesktop: LXQt
Date: Tue Mar 16 19:23:23 2021
LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210311)
PackageArchitecture: all
SourcePackage: lubuntu-default-settings
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lubuntu-default-settings (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919371

Title:
  picom needs a sane default configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-default-settings/+bug/1919371/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919370] [NEW] use picom instead of compton

2021-03-16 Thread Walter Lapchynski
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
ApportVersion: 2.20.11-0ubuntu60
Architecture: amd64
CasperMD5CheckMismatches: ./casper/filesystem.manifest
CasperMD5CheckResult: fail
CasperVersion: 1.460
CurrentDesktop: LXQt
Date: Tue Mar 16 19:27:02 2021
LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210311)
SourcePackage: lubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919370

Title:
  use picom instead of compton

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1919370/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919367] [NEW] compton recommends picom

2021-03-16 Thread Walter Lapchynski
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, installing
compton results in having two compositors (picom and compton) and since
picom doesn't come with a default config all set up, it will use
compton.conf and it will likely fail silently. This is just bad. If
anything, picom should be a suggest, or just simply not mentioned at
all.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: compton 1-1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu60
Architecture: amd64
CasperMD5CheckMismatches: ./casper/filesystem.manifest
CasperMD5CheckResult: fail
CasperVersion: 1.460
CurrentDesktop: LXQt
Date: Tue Mar 16 19:12:15 2021
LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210311)
SourcePackage: compton
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: compton (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919367

Title:
  compton recommends picom

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compton/+bug/1919367/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1798071] Re: Suspension fails and re-login screen is black

2021-03-16 Thread Walter Lapchynski
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 (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: lubuntu-artwork

** Changed in: linux (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/1798071

Title:
  Suspension fails and re-login screen is black

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798071/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919363] [NEW] provide warning to user about bad media when running installer

2021-03-16 Thread Walter Lapchynski
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
the background. It's plausible it can still be running *after* the GUI
loads. That's neat stuff, but there's no feedback to the user.

A file by the name of casper-md5check.json is in /run in the live
environment with the results. In turn, that will be dropped into
/var/log/installer on the installed system. This JSON file will report
which files did not match and what the overall result is (which can be
unknown, fail, success, or skip). Example:

{
  "checksum_missmatch": [ 
"./casper/filesystem.manifest"
],
  "result": "fail"
}

In turn, the results are reported by apport in any bugs filed.

Bug 1918733 was created to resolve this issue, but was marked Won't Fix,
at least for casper. In that bug, it was suggested that the various
installers would implement this in some way. Therefore, this bug exists
to resolve it in Calamares.

My proposed fix is a simple shell script or a small Python program. It
would be run before Calamares via the customized Desktop Entry (i.e. the
one that's on the desktop). I'm thinking of this instead of doing it in
Calamares as it will not allow us to create random dialogs. kdialog
would, though, so we should add that to the live seed and use that. I
would suggest that we run this with ; and not && because we don't want a
minor logic failure or something to prevent installation altogether.
Also, I don't think we want to get heavy handed. There may be a reason
one may want to continue with bad media (e.g. for testing).

The logic would be something like this:

 1. Check the status of the systemd casper-md5check.service
 2. If the service is still running, wait for a given timeout
 3. If the timeout is reached and the service is still running, exit gracefully 
(maybe submit a bug? or record the problem somewhere?)
 4. Parse the results
 5. Warn the user but do not prevent them from continuing

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: calamares-settings-lubuntu 1:21.04.2
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu60
Architecture: amd64
CasperMD5CheckMismatches: ./casper/filesystem.manifest
CasperMD5CheckResult: fail
CasperVersion: 1.460
CurrentDesktop: LXQt
Date: Tue Mar 16 18:33:36 2021
LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210311)
PackageArchitecture: all
SourcePackage: calamares-settings-ubuntu
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: calamares-settings-ubuntu (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919363

Title:
  provide warning to user about bad media when running installer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/1919363/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886561] Re: network manager applet for authentication is not working

2021-03-15 Thread Walter Lapchynski
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 => Triaged

** Changed in: nm-tray (Ubuntu)
   Importance: Undecided => Medium

** Bug watch added: github.com/palinek/nm-tray/issues #44
   https://github.com/palinek/nm-tray/issues/44

** Also affects: nm-tray via
   https://github.com/palinek/nm-tray/issues/44
   Importance: Unknown
   Status: Unknown

** Summary changed:

- network manager applet for authentication is not working 
+ nm-tray does not prompt for password with VPN connections

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886561

Title:
  nm-tray does not prompt for password with VPN connections

To manage notifications about this bug go to:
https://bugs.launchpad.net/nm-tray/+bug/1886561/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917590] Re: File integrity check at boot of install media no longer functional

2021-03-11 Thread Walter Lapchynski
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

Title:
  File integrity check at boot of install media  no longer functional

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1917590/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1918733] [NEW] file integrity check provides no feedback to the user

2021-03-11 Thread Walter Lapchynski
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 despite the bad media. That's
probably a separate bug for the installer.

Either way, the software shouldn't let a user continue to waste their
time on something that's broken.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: casper 1.460
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu60
Architecture: amd64
CasperMD5CheckMismatches: ./casper/filesystem.manifest
CasperMD5CheckResult: fail
CasperVersion: 1.460
CurrentDesktop: LXQt
Date: Thu Mar 11 21:10:01 2021
LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210311)
SourcePackage: casper
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.casper.conf: 2021-03-11T21:09:00.584000

** Affects: casper (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918733

Title:
  file integrity check provides no feedback to the user

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1918733/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917590] Re: File integrity check at boot of install media no longer functional

2021-03-11 Thread Walter Lapchynski
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.
https://bugs.launchpad.net/bugs/1917590

Title:
  File integrity check at boot of install media  no longer functional

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1917590/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1918564] Re: Multiple archiver applications appear in Lubuntu 21.04 (Hirsute Hippo)

2021-03-10 Thread Walter Lapchynski
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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918564

Title:
  Multiple archiver applications appear in Lubuntu 21.04 (Hirsute Hippo)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxqt-metapackages/+bug/1918564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887530] Re: Dragging icon from start menu to desktop changes the way it works

2021-03-04 Thread Walter Lapchynski
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 to desktop changes the way it works

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1887530/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887532] Re: virtualbox-guest-additions-iso package does not work (works in Ubuntu)

2021-03-04 Thread Walter Lapchynski
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.
https://bugs.launchpad.net/bugs/1887532

Title:
  virtualbox-guest-additions-iso package does not work (works in Ubuntu)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1887532/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917724] Re: lubuntu hirsute install fail mkfs.xfs

2021-03-04 Thread Walter Lapchynski
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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917724

Title:
  lubuntu hirsute install fail mkfs.xfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1917724/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887681] Re: Monitor settings dialog does not open when Lubuntu runs in virtualbox

2021-03-04 Thread Walter Lapchynski
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 dialog does not open when Lubuntu runs in virtualbox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1887681/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917724] Re: lubuntu hirsute install fail mkfs.xfs

2021-03-04 Thread Walter Lapchynski
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. In which case we may have to either drop that patch and issue
release notes with a workaround for the label issue or ship Git master
(probably not).

To reduce noise, can we just forget about reusing and extra partitions
and stuff and simply do a fresh partition table with either xfs,
reiserfs, or btrfs (i.e. 3 separate tests) and see if it fails
similarly? In other words, I want to test just whether or not creating
the file system on a fresh table works. This should just work. It
certainly should just work in kpm, as it has in the past. If those fail
and especially if they all fail, that's trouble.

** Changed in: calamares (Ubuntu)
   Status: New => Incomplete

** Changed in: calamares (Ubuntu)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917724

Title:
  lubuntu hirsute install fail mkfs.xfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1917724/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917590] Re: File integrity check at boot of install media no longer functional

2021-03-03 Thread Walter Lapchynski
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 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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1917590/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1883886] Re: Print dialogue's height in Libreoffice Writer is too high to see and click buttons.

2021-03-03 Thread Walter Lapchynski
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 notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883886

Title:
   Print dialogue's height in Libreoffice Writer is too high to see and
  click buttons.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1883886/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917590] Re: File integrity check at boot of install media no longer functional

2021-03-03 Thread Walter Lapchynski
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 problem doesn't lie here somewhere:
https://git.launchpad.net/ubuntu/+source/casper/commit/?id=8415b4102e5c59064a5acff878aa2c3c8aa10e96

-- 
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1917590/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1883886] Re: Print dialogue's height in Libreoffice Writer is too high to see and click buttons.

2021-03-03 Thread Walter Lapchynski
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 just setting it as Triaged or Confirmed would be
sufficient.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883886

Title:
   Print dialogue's height in Libreoffice Writer is too high to see and
  click buttons.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1883886/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917590] Re: File integrity check at boot of install media no longer functional

2021-03-03 Thread Walter Lapchynski
** 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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1917590/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917590] Re: File integrity check at boot of install media no longer visible

2021-03-03 Thread Walter Lapchynski
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.

** Changed in: casper (Ubuntu)
   Importance: Undecided => High

** Summary changed:

- File integrity check at boot of install media  no longer visible
+ File integrity check at boot of install media  no longer functional

-- 
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1917590/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917292] Re: Lubuntu Hirsute daily install failed due to grub packaging errors

2021-03-01 Thread Walter Lapchynski
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 resolve this by removing the following lines from
/etc/calamares/modules/before_bootloader_context.conf:

-command: sed -i '/deb http/d' /etc/apt/sources.list
 timeout: 10

There's a task to fix up the script here:
https://phab.lubuntu.me/T200

However, this is still not the cause of our problems.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917292

Title:
  Lubuntu Hirsute daily install failed due to grub packaging errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1917292/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917292] Re: Lubuntu Hirsute daily install failed due to grub packaging errors

2021-03-01 Thread Walter Lapchynski
** 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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917292

Title:
  Lubuntu Hirsute daily install failed due to grub packaging errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1917292/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917292] Re: Lubuntu Hirsute daily install failed due to grub packaging errors

2021-03-01 Thread Walter Lapchynski
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 w/errors 
+ Lubuntu Hirsute daily install failed due to grub packaging errors

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917292

Title:
  Lubuntu Hirsute daily install failed due to grub packaging errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1917292/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917292] Re: Lubuntu Hirsute daily install failed due to grub packaging errors

2021-03-01 Thread Walter Lapchynski
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 no response so far.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917292

Title:
  Lubuntu Hirsute daily install failed due to grub packaging errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1917292/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917360] [NEW] where have the logs gone?

2021-03-01 Thread Walter Lapchynski
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)
default logging behavior changed.

We could call with `-d` but that includes the debug button which has
potential to freak out users, so better would be to set our preferred
log level with e.g. `-D6` in the call to the installer in the Desktop
Entry.

** Affects: calamares-settings-ubuntu (Ubuntu)
 Importance: Medium
 Assignee: Dan Simmons (kc2bez)
 Status: Triaged

** Package changed: calamares (Ubuntu) => calamares-settings-ubuntu
(Ubuntu)

** Changed in: calamares-settings-ubuntu (Ubuntu)
   Importance: Undecided => Medium

** Changed in: calamares-settings-ubuntu (Ubuntu)
   Status: New => Triaged

** Changed in: calamares-settings-ubuntu (Ubuntu)
Milestone: None => ubuntu-21.04

** Changed in: calamares-settings-ubuntu (Ubuntu)
 Assignee: (unassigned) => Dan Simmons (kc2bez)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917360

Title:
  where have the logs gone?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/1917360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917292] Re: Lubuntu Hirsute daily install failed -external command finished w/errors

2021-03-01 Thread Walter Lapchynski
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.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 grub-efi-amd64-bin : Depends: grub-common (= 2.04-1ubuntu37) but 
2.04-1ubuntu40 is to be installed
  Recommends: efibootmgr but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

This is the result of trying to install grub-efi-amd64-signed. src:grub2
and src:grub2-signed have been released (as 1ubuntu40) as of the 25th
and efibootmgr hasn't changed in forever. Something is weird here with
regards to packages.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917292

Title:
  Lubuntu Hirsute daily install failed -external command finished
  w/errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1917292/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1883886] Re: Print dialogue's height in Libreoffice Writer is too high to see and click buttons.

2021-02-28 Thread Walter Lapchynski
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 because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883886

Title:
   Print dialogue's height in Libreoffice Writer is too high to see and
  click buttons.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1883886/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1916260] Re: PCManFM-Qt opens files with a single click only

2021-02-26 Thread Walter Lapchynski
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 opens files with a single click only

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1916260/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1910934] Re: lxqt loses natural scrolling

2021-02-26 Thread Walter Lapchynski
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 device to be re-enumerated, you may then have
deviceX+1, which has its own setting. At some point, I would imagine
that trying to connect to deviceX would time out and it would get
dropped. Logging out and back in again would likely force LXQt to re-
read the devices, leaving only deviceX+1.

-- 
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 scrolling

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1910934/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1916897] Re: Option has no effect and reset itself

2021-02-25 Thread Walter Lapchynski
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 centering solutions were buggy, as 
evidenced by this bug:
https://bugzilla.icculus.org/show_bug.cgi?id=5946

However, as you can see there, it was resolved with a new commit:
https://github.com/danakj/openbox/commit/f866c034bf6e954791442ff029d5ae51ab0bd616

Despite all that, I can't get it to work no way, no how.

That said, I'm going to add Openbox and investigate a bit further.

** Bug watch added: bugzilla.icculus.org/ #5946
   http://bugzilla.icculus.org/show_bug.cgi?id=5946

** Also affects: openbox (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: openbox (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/1916897

Title:
  Option has no effect and reset itself

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/obconf-qt/+bug/1916897/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1905947] Re: lubuntu hirsute: display configuration doesn't survive logout/reboot

2021-02-23 Thread Walter Lapchynski
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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1905947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1905947] Re: lubuntu hirsute: display configuration doesn't survive logout/reboot

2021-02-23 Thread Walter Lapchynski
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: display configuration doesn't survive logout/reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1905947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1916356] Re: The installer failed to create partition on disk with EFI (not BIOS)

2021-02-23 Thread Walter Lapchynski
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 now a
  fix in kpmcore, which is what Calamares uses to do this work, that
  essentially sets "NO_LABEL" instead of a null ("") label.
+ 
+ Workaround: manual partitioning expressly setting labels on all
+ partitions.
  
  ---
  
  Testing Lubuntu Hirsute ISO 20210220 -
  Test machine Lenovo V14 IIL - booting in UEFI+secure boot mode
  
  Connected to WiFi network and ran the installer -
  
  I selected "Erase disk with swap file" and then Calamares crashed with
  the error: "the installer failed to create partition on disk "WDC PC
  SN20 ..." see attached screenshot and files.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: calamares 3.2.35-0ubuntu2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .etc.calamares.modules.shellprocess_logs.conf:
   ---
   dontChroot: true
   timeout: 30
   script:
   - calamares-logs-helper @@ROOT@@
  .etc.calamares.modules.unpackfs.conf:
   ---
   unpack:
   -   source: "/cdrom/casper/filesystem.squashfs"
   sourcefs: "squashfs"
   destination: ""
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.456
  CurrentDesktop: LXQt
  Date: Sat Feb 20 20:23:48 2021
  LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210220)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:21.04.1
   calamares-settings-lubuntu   1:21.04.1
   xfsprogs 5.6.0-1ubuntu4
   btrfs-progs  5.10.1-1
  SourcePackage: calamares
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916356

Title:
  The installer failed to create partition on disk with EFI (not BIOS)

To manage notifications about this bug go to:
https://bugs.launchpad.net/calamares/+bug/1916356/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1916497] Re: PCManFM-Qt does not respect systemw-wide Qt widget style

2021-02-23 Thread Walter Lapchynski
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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916497

Title:
  PCManFM-Qt does not respect systemw-wide Qt widget style

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1916497/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1916356] Re: The installer failed to create partition on disk with EFI

2021-02-23 Thread Walter Lapchynski
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 all partitions makes a
difference. If it does, we at least have a workaround.

Meanwhile kc2bez is testing the fix. Applying to kpmcore alone wasn't
sufficient, so we'll rebuild Calamares against that and see how it goes.

** Summary changed:

- The installer failed to create partition on disk
+ The installer failed to create partition on disk with EFI

** Changed in: calamares (Ubuntu)
   Status: Confirmed => Triaged

** Bug watch added: Calamares Issues #1637
   https://github.com/calamares/calamares/issues/1637

** Also affects: calamares via
   https://github.com/calamares/calamares/issues/1637
   Importance: Unknown
   Status: Unknown

** Also affects: kpmcore (Ubuntu)
   Importance: Undecided
   Status: New

** Bug watch added: KDE Bug Tracking System #432941
   https://bugs.kde.org/show_bug.cgi?id=432941

** Also affects: kpmcore via
   https://bugs.kde.org/show_bug.cgi?id=432941
   Importance: Unknown
   Status: Unknown

** Changed in: kpmcore (Ubuntu)
   Status: New => Triaged

** Changed in: calamares (Ubuntu)
   Importance: Undecided => Critical

** Changed in: kpmcore (Ubuntu)
   Importance: Undecided => Critical

** Summary changed:

- The installer failed to create partition on disk with EFI
+ The installer failed to create partition on disk with EFI (not BIOS)

** 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 now a
+ fix in kpmcore, which is what Calamares uses to do this work, that
+ essentially sets "NO_LABEL" instead of a null ("") label.
+ 
+ ---
+ 
  Testing Lubuntu Hirsute ISO 20210220 -
  Test machine Lenovo V14 IIL - booting in UEFI+secure boot mode
  
  Connected to WiFi network and ran the installer -
  
  I selected "Erase disk with swap file" and then Calamares crashed with
  the error: "the installer failed to create partition on disk "WDC PC
  SN20 ..." see attached screenshot and files.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: calamares 3.2.35-0ubuntu2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .etc.calamares.modules.shellprocess_logs.conf:
   ---
   dontChroot: true
   timeout: 30
   script:
   - calamares-logs-helper @@ROOT@@
  .etc.calamares.modules.unpackfs.conf:
   ---
   unpack:
   -   source: "/cdrom/casper/filesystem.squashfs"
   sourcefs: "squashfs"
   destination: ""
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.456
  CurrentDesktop: LXQt
  Date: Sat Feb 20 20:23:48 2021
  LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210220)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:21.04.1
   calamares-settings-lubuntu   1:21.04.1
   xfsprogs 5.6.0-1ubuntu4
   btrfs-progs  5.10.1-1
  SourcePackage: calamares
  UpgradeStatus: No upgrade log present (probably fresh install)

** Changed in: calamares (Ubuntu)
 Assignee: (unassigned) => Dan Simmons (kc2bez)

** Changed in: kpmcore (Ubuntu)
 Assignee: (unassigned) => Dan Simmons (kc2bez)

** Changed in: calamares (Ubuntu)
Milestone: None => ubuntu-21.04

** Changed in: kpmcore (Ubuntu)
Milestone: None => ubuntu-21.04

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916356

Title:
  The installer failed to create partition on disk with EFI (not BIOS)

To manage notifications about this bug go to:
https://bugs.launchpad.net/calamares/+bug/1916356/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1916481] Re: qterminal: undefined symbol

2021-02-23 Thread Walter Lapchynski
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.
https://bugs.launchpad.net/bugs/1916481

Title:
  qterminal: undefined symbol

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qterminal/+bug/1916481/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1916481] Re: qterminal: undefined symbol

2021-02-22 Thread Walter Lapchynski
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.

Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916481

Title:
  qterminal: undefined symbol

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qterminal/+bug/1916481/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1914521] Re: lubuntu focal.2 "sfdisk --force --append /dev/sda"

2021-02-04 Thread Walter Lapchynski
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.
https://bugs.launchpad.net/bugs/1914521

Title:
  lubuntu focal.2 "sfdisk --force --append /dev/sda"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1914521/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist

2021-02-03 Thread Walter Lapchynski
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:
  software-properties-{qt,kde} attempts to use KUrl but it doesn't exist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist

2021-02-03 Thread Walter Lapchynski
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-
packages/softwareproperties/qt/SoftwarePropertiesQt.py) according to the
instructions given by the diff:

 1. Starting at line 709, look at it and the following 7 lines for a total of 
eight lines (this is what "-709,8" refers to in the original)
 2. Note, too, that after the change, the same hunk is referenced as "+709,7" 
meaning that the end result is one less line.
 3. Remove the definition of the "url" variable in line 712.
 4. In the next line (which is now 712) which defines the "filename" variable, 
change it from using the KFileDialog.getOpenFileName method to the 
QFileDialog.getOpenFileName method. Note that the arguments and their order are 
different.
 5. Save it and try again.

** Tags added: groovy hirsute

-- 
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:
  software-properties-{qt,kde} attempts to use KUrl but it doesn't exist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1914461] Re: Unable to import key file in "authentication" in Software sources"

2021-02-03 Thread Walter Lapchynski
*** 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 resolved once
and for all.

** This bug has been marked a duplicate of bug 1795278
   software-properties-{qt,kde} attempts to use KUrl but it doesn't exist

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914461

Title:
  Unable to import key file in "authentication" in Software sources"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1914461/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909506] Re: lubuntu hirsute daily install failed - error message to large for screen

2021-02-02 Thread Walter Lapchynski
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 install failed  - error message to large for
  screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/calamares/+bug/1909506/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1910934] Re: lxqt loses natural scrolling

2021-01-30 Thread Walter Lapchynski
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 button option. So that may be worth looking into.

-- 
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 scrolling

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1910934/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1910934] Re: lxqt loses natural scrolling

2021-01-30 Thread Walter Lapchynski
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 of the LXQt config files. They are meant to be changed via the GUI.
I'm used to editing text files so it's a bit of a strange thing to me,
but I've seen strange behaviors from doing so with LXQt so I avoid it.

If none of that helps, you might want to use `strace` to see what's
opened when.

-- 
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 scrolling

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1910934/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1910934] Re: lxqt loses natural scrolling

2021-01-29 Thread Walter Lapchynski
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 your logs, where along in the boot process does that
happen?

-- 
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 scrolling

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1910934/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1908203] Re: breeze icons set to monochrome on 48x48

2021-01-29 Thread Walter Lapchynski
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 because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908203

Title:
  breeze icons set to monochrome on 48x48

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/breeze-icons/+bug/1908203/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913513] Re: lubuntu focal.2 calamares summary repeats details

2021-01-29 Thread Walter Lapchynski
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 it fix released.

** 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/1913513

Title:
  lubuntu focal.2 calamares summary repeats details

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1913513/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1864787] Re: Lubuntu failed install "sfdisk --force --append /dev/sda"

2021-01-28 Thread Walter Lapchynski
** 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 manage notifications about this bug go to:
https://bugs.launchpad.net/calamares/+bug/1864787/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1865955] Re: Calamares warns "no ESP flag set, " but there is no ESP flag to choose

2021-01-28 Thread Walter Lapchynski
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

Title:
  Calamares warns "no ESP flag set," but there is no ESP flag to choose

To manage notifications about this bug go to:
https://bugs.launchpad.net/calamares/+bug/1865955/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1773610] Re: no clear indication that format has been selected

2021-01-28 Thread Walter Lapchynski
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: focal

** 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" radio button
  10. Click "OK"
  
  EXPECTED BEHAVIOR
   * The main screen would have a column showing whether or not formatting has 
been selected
   * The "Format" radio button would be selected in the dialog upon further 
edits
   * In the summary screen, formatting is only done once
  
  ACTUAL BEHAVIOR
   * The main screen shows no information about whether or not formatting is to 
occur
   * The "Keep" radio button is selected in the dialog upon further edits
   * In the summary screen, formatting is shown twice
  
  AFFECTED VERSIONS
  calamares 3.2.0-1 - 3.2.4-0ubuntu3
- 18.10 - 19.10
+ 18.10 - 20.04 (and possibly more)

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773610

Title:
  no clear indication that format has been selected

To manage notifications about this bug go to:
https://bugs.launchpad.net/calamares/+bug/1773610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1773610] Re: no clear indication that format has been selected

2021-01-28 Thread Walter Lapchynski
** 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" radio button
  10. Click "OK"
  
  EXPECTED BEHAVIOR
   * The main screen would have a column showing whether or not formatting has 
been selected
   * The "Format" radio button would be selected in the dialog upon further 
edits
   * In the summary screen, formatting is only done once
  
  ACTUAL BEHAVIOR
   * The main screen shows no information about whether or not formatting is to 
occur
   * The "Keep" radio button is selected in the dialog upon further edits
   * In the summary screen, formatting is shown twice
  
  AFFECTED VERSIONS
  calamares 3.2.0-1 - 3.2.4-0ubuntu3
- 18.10 - 20.04 (and possibly more)
+ 18.10 - 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/1773610

Title:
  no clear indication that format has been selected

To manage notifications about this bug go to:
https://bugs.launchpad.net/calamares/+bug/1773610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1773610] Re: no clear indication that format has been selected

2021-01-27 Thread Walter Lapchynski
** 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. Select the partition
-  8. Click "Edit"
-  9. Click the "Format" radio button
+  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" radio button
  10. Click "OK"
  
  EXPECTED BEHAVIOR
-  * The main screen would have a column showing whether or not formatting has 
been selected
-  * The "Format" radio button would be selected in the dialog upon further 
edits
-  * In the summary screen, formatting is only done once
+  * The main screen would have a column showing whether or not formatting has 
been selected
+  * The "Format" radio button would be selected in the dialog upon further 
edits
+  * In the summary screen, formatting is only done once
  
  ACTUAL BEHAVIOR
-  * The main screen shows no information about whether or not formatting is to 
occur
-  * The "Keep" radio button is selected in the dialog upon further edits
-  * In the summary screen, formatting is shown twice
+  * The main screen shows no information about whether or not formatting is to 
occur
+  * The "Keep" radio button is selected in the dialog upon further edits
+  * In the summary screen, formatting is shown twice
  
  AFFECTED VERSIONS
  calamares 3.2.0-1 - 3.2.4-0ubuntu3
- 18.10 - 19.04
+ 18.10 - 20.04 (and possibly more)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773610

Title:
  no clear indication that format has been selected

To manage notifications about this bug go to:
https://bugs.launchpad.net/calamares/+bug/1773610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1875774] Re: Lubuntu 20.04 lxqt-admin-user Action (usermod) failed

2021-01-26 Thread Walter Lapchynski
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 => High

** Changed in: lxqt-policykit (Ubuntu)
   Status: Confirmed => Triaged

** Bug watch added: github.com/lxqt/lxqt-policykit/issues #105
   https://github.com/lxqt/lxqt-policykit/issues/105

** Also affects: lxqt via
   https://github.com/lxqt/lxqt-policykit/issues/105
   Importance: Unknown
   Status: Unknown

** Summary changed:

- Lubuntu 20.04 lxqt-admin-user Action (usermod) failed
+ lxqt-policykit crashes with general protection fault in libgobject-2.0

** Description changed:

- This is testing was performed as a result of a user support request on a
- fresh install (screen position & wallpaper changed; nfs-common added &
- that's about all)
+ STEPS TO REPRODUCE
+ ==
+  1. Boot post-18.04 Lubuntu
+  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 requirement to reproduce— if you 
want, you can first remove user2's sudo and it will work, but then add it back 
and continue on)
+  5. User lxqt-admin-user to try to remove user2's membership in the sudo 
group (fail)
+  6. Try running pkexec against something. Since synaptic is well set up for 
it, this is a good example, so install synaptic and run `synaptic-pkexec` (fail)
+  7. Remove user2's membership in the sudo group for sure with `sudo usermod 
-G "" user2`
+  8. Try running the pkexec command again (success)
  
- https://discourse.lubuntu.me/t/no-authorization-after-adding-user/1033/
+ EXPECTED RESULT
+ ===
+ Both the pkexec and the lxqt-admin-user change succeed without crashing.
  
- A new user was added "pw_admin", logout & some testing done without
- issue.
- 
- I logged back in as me and tried to remove "sudo" rights from "pw_admin"
- user logged in as "guiverc" which is where I first had noticed this
- error.
- 
- On testing, it appears to occur on retracting/removing rights rather
- than adding them, and after the privileges are added only (though my
- testing is incomplete; takes awhile  for rights to drop & thus be asked
- again; no issue if elevated-privileges already exists it so far appears
- to me)
- 
- Expected Result:
- 
- The 'sudo' permission gets removed
- 
- Actual Result:
- 
- I get an error show in discourse site, or uploaded here
- 
- When the error pop-up (
- 
- "Action (usermod) failed:
- Error executing command as another user: Not authorized
- This incident has been report" occurs
- 
- the following is written to `dmesg` output
- 
- [ 764.849494] traps: lxqt-policykit-[1598] general protection fault
- ip:7f8c94773671 sp:7ffc5acf6618 error:0 in
- libgobject-2.0.so.0.6400.2[7f8c94745000+36000]
- 
- and in /var/crash/ (it was submitted)
- -rw-r- 1 guiverc whoopsie 3.2M Apr 29 11:37 
_usr_bin_lxqt-policykit-agent.1000.crash
+ ACTUAL RESULT
+ =
+ lxqt-policykit crashes, e.g:
+ [ 764.849494] traps: lxqt-policykit-[1598] general protection fault 
ip:7f8c94773671 sp:7ffc5acf6618 error:0 in 
libgobject-2.0.so.0.6400.2[7f8c94745000+36000]
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lxqt-admin 0.14.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Wed Apr 29 12:04:34 2020
  InstallationDate: Installed on 2020-04-28 (0 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: lxqt-admin
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
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:
  lxqt-policykit crashes with general protection fault in libgobject-2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/lxqt/+bug/1875774/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1875774] Re: Lubuntu 20.04 lxqt-admin-user Action (usermod) failed

2021-01-26 Thread Walter Lapchynski
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxqt-admin/+bug/1875774/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1875774] Re: Lubuntu 20.04 lxqt-admin-user Action (usermod) failed

2021-01-26 Thread Walter Lapchynski
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 requirement to reproduce— if you 
want, you can first remove user2's sudo and it will work, but then add it back 
and continue on)
 5. User lxqt-admin-user to try to remove user2's membership in the sudo group 
(fail)
 6. Try running pkexec against something. Since synaptic is well set up for it, 
this is a good example, so install synaptic and run `synaptic-pkexec` (fail)
 7. Remove user2's membership in the sudo group for sure with `sudo usermod -G 
"" user2`
 8. Try running the pkexec command again (success)

I did check this also against the adm group and it didn't seem to have
an effect.

Anyways, I'm pretty sure the error, if anywhere, exists in lxqt-
policykit. It's had like almost zero upstream issues, so that's
interesting.

It's also possible this is a pkexec issue of some kind. It has caused
many headaches for folks.

I'm updating my machine running off of LXQt's git master and we'll see
if it behaves any better.

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxqt-admin/+bug/1875774/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1899782] Re: lxqt-policykit-agent crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

2021-01-26 Thread Walter Lapchynski
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 synaptic-pkexec and had no
issues.

If /var/log/installer/casper-md5check.json exists, then you skipped the
file check at the beginning of the installation process and that right
there may indicate you have a corrupt installation, which could explain
this strange behavior.

** This bug is no longer a duplicate of bug 1875774
   Lubuntu 20.04 lxqt-admin-user Action (usermod) failed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899782

Title:
  lxqt-policykit-agent crashed with SIGSEGV in
  g_type_check_instance_is_fundamentally_a()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxqt-policykit/+bug/1899782/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1905483]

2021-01-25 Thread Walter Lapchynski
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 disc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1905483/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1910934] Re: lxqt loses natural scrolling

2021-01-25 Thread Walter Lapchynski
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 might be to use
something like auditd
(https://manpages.ubuntu.com/manpages/focal/man8/auditd.8.html) to
figure out what process is changing the file and how often.

-- 
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 scrolling

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1910934/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1910934] Re: lxqt loses natural scrolling

2021-01-25 Thread Walter Lapchynski
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,
I suspect that's where your problem lies.

-- 
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 scrolling

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1910934/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1910934] Re: lxqt loses natural scrolling

2021-01-25 Thread Walter Lapchynski
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 scrolling

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1910934/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1905483] Re: Lubuntu installer cannot deal with a virgin disc.

2021-01-25 Thread Walter Lapchynski
"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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1905483/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1912841] Re: keyboard layout switch keys don't work correctly for the specific English/Persian combination

2021-01-22 Thread Walter Lapchynski
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 second at least allows one switch to Persian. Just can't
get out of it. Other layouts are affected as well, notably Afghani.

** Changed in: lxqt-config (Ubuntu)
   Status: New => Triaged

** Changed in: lxqt-config (Ubuntu)
   Importance: Undecided => Medium

** Bug watch added: github.com/lxqt/lxqt-config/issues #711
   https://github.com/lxqt/lxqt-config/issues/711

** Also affects: lxqt via
   https://github.com/lxqt/lxqt-config/issues/711
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912841

Title:
  keyboard layout switch keys don't work correctly for the specific
  English/Persian combination

To manage notifications about this bug go to:
https://bugs.launchpad.net/lxqt/+bug/1912841/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1750262] Re: Lubuntu: Desktop manager is not active.

2021-01-20 Thread Walter Lapchynski
** 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: Desktop manager is not active.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1750262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1869292] Re: lubuntu 20.04 qa-install, however calamares is freezing/stopping

2021-01-20 Thread Walter Lapchynski
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 20.04 qa-install, however calamares is freezing/stopping

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1869292/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909622] Re: lubuntu focal hirsute install; calamares error

2021-01-15 Thread Walter Lapchynski
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, everything will Just Work™.

That said, I wouldn't necessarily discourage reporting of this issue on
the ISO tracker (so we don't forget about it), but I wouldn't bother
with any more extensive testing or troubleshooting.

The release notes should cover us for those people that don't just
select the icon on the desktop or pick the Lubuntu-specific option from
the menu.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909622

Title:
  lubuntu focal hirsute install; calamares error

To manage notifications about this bug go to:
https://bugs.launchpad.net/calamares/+bug/1909622/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1864791] Re: Lubuntu failed install "wipefs --all /dev/sda9"

2021-01-11 Thread Walter Lapchynski
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

Title:
  Lubuntu failed install "wipefs --all /dev/sda9"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1864791/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1827415] Re: In Lubuntu 19.04, a file does not open on double-click when vim is configured as default application for this filetype

2021-01-11 Thread Walter Lapchynski
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 should probably be fixed, but
fixing that doesn't solve the problem. I'm a little baffled.

-- 
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 is
  configured as default application for this filetype

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1827415/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1827415] Re: In Lubuntu 19.04, a file does not open on double-click when vim is configured as default application for this filetype

2021-01-11 Thread Walter Lapchynski
** 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 is
  configured as default application for this filetype

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1827415/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1910934] Re: lxqt loses natural scrolling

2021-01-11 Thread Walter Lapchynski
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:
apport-collect BUGNUMBER

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

-- 
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 scrolling

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1910934/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1910934] Re: lxqt loses natural scrolling

2021-01-11 Thread Walter Lapchynski
** 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

Title:
  lxqt loses natural scrolling

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1910934/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1902497] Re: Hibernation fails Lubuntu 20.10 and 21.04

2021-01-07 Thread Walter Lapchynski
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 received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902497

Title:
  Hibernation fails Lubuntu 20.10 and 21.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxqt-session/+bug/1902497/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909622] Re: lubuntu hirsute install; calamares error

2021-01-06 Thread Walter Lapchynski
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 notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909622

Title:
  lubuntu hirsute install; calamares error

To manage notifications about this bug go to:
https://bugs.launchpad.net/calamares/+bug/1909622/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909506] Re: lubuntu hirsute daily install failed - error message to large for screen

2021-01-06 Thread Walter Lapchynski
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: Unknown
   Status: Unknown

-- 
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 install failed  - error message to large for
  screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/calamares/+bug/1909506/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909506] Re: lubuntu hirsute daily install failed - error message to large for screen

2021-01-06 Thread Walter Lapchynski
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.
https://bugs.launchpad.net/bugs/1909506

Title:
  lubuntu hirsute daily install failed  - error message to large for
  screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/calamares/+bug/1909506/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909622] Re: lubuntu hirsute install; calamares error

2021-01-06 Thread Walter Lapchynski
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 Calamares bug).

tl;dr only use the Lubuntu one :)


** Changed in: calamares (Ubuntu)
   Status: Confirmed => Triaged

** Bug watch added: github.com/lxqt/lxqt/issues #1743
   https://github.com/lxqt/lxqt/issues/1743

** Also affects: calamares via
   https://github.com/lxqt/lxqt/issues/1743
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909622

Title:
  lubuntu hirsute install; calamares error

To manage notifications about this bug go to:
https://bugs.launchpad.net/calamares/+bug/1909622/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909506] Re: lubuntu hirsute daily install failed - error message to large for screen

2021-01-06 Thread Walter Lapchynski
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 Calamares bug).

tl;dr only use the Lubuntu one :)

** Changed in: calamares (Ubuntu)
   Status: New => Triaged

** Bug watch added: github.com/lxqt/lxqt/issues #1743
   https://github.com/lxqt/lxqt/issues/1743

** Also affects: calamares via
   https://github.com/lxqt/lxqt/issues/1743
   Importance: Unknown
   Status: Unknown

-- 
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 install failed  - error message to large for
  screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1909506/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1908846] Re: lubuntu focal.2 calamares fails to parse GeoIP results correctly in JSON (refile)

2021-01-06 Thread Walter Lapchynski
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
Calamares and its settings on launching the installer. This won't keep
us from having to go through the SRU process, but it will mean that we
won't have to respin ISOs to get installer-releated fixes in place.

** Changed in: calamares (Ubuntu)
 Assignee: (unassigned) => Dan Simmons (kc2bez)

** Changed in: calamares (Ubuntu)
   Status: Confirmed => In Progress

-- 
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 correctly in
  JSON (refile)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1908846/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1908846] Re: lubuntu focal.2 calamares fails to parse GeoIP results correctly in JSON (refile)

2021-01-06 Thread Walter Lapchynski
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:
https://github.com/calamares/calamares/issues/1540

You will also see there that as of v3.2.32 of Calamares that there is now 
additional debug information (mentioned in the issue):
https://github.com/calamares/calamares/commit/d63e23b289f1f285d190c711ee296778bb7f5259

Unfortunately, that doesn't exist in versions before Hirsute, so I can't
very well confirm that is the situation in this case, but it is highly
likely.

Additionally, the two changes that resulted in using Ubuntu's GeoIP service 
that are ultimately the fix for this problem weren't added until after Focal:
https://phab.lubuntu.me/rCALASETTINGS01c0bcafc8f3b7c089a7e7d9a6ca2cb4b793e009
https://phab.lubuntu.me/rCALASETTINGS63230172e442ac55db7bc3ba0bd54f842c210edd

tl;dr if we're going to fix this, it would have to be via an SRU of
calamares-settings-lubuntu. The problem is getting it on the ISO. That
is much harder. I guess we could get it in a point release, but is that
worth the effort? I'm kind of thinking not.

** Bug watch added: Calamares Issues #1540
   https://github.com/calamares/calamares/issues/1540

-- 
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 correctly in
  JSON (refile)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1908846/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1908846] Re: lubuntu focal.2 calamares fails to parse GeoIP results correctly in JSON (refile)

2021-01-05 Thread Walter Lapchynski
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 correctly in
  JSON (refile)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1908846/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1902497] Re: Hibernation fails Lubuntu 20.10 and 21.04

2021-01-04 Thread Walter Lapchynski
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 member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902497

Title:
  Hibernation fails Lubuntu 20.10 and 21.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxqt-session/+bug/1902497/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1857364] Re: group sambashare with gid 1000

2020-12-24 Thread Walter Lapchynski
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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1857364/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1857364] Re: group sambashare with gid 1000

2020-12-24 Thread Walter Lapchynski
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 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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1857364/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1875717] Re: Opening file from Samba share results in Document in Use

2020-12-17 Thread Walter Lapchynski
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 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 in Use

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1875717/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1875717] Re: Opening file from Samba share results in Document in Use

2020-12-17 Thread Walter Lapchynski
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, but may be worth some investigating.

My past experience tells me that the dialog about the file being locked
for editing comes up when someone using the share has the file open and
someone else tries to open it. Another possibility is if someone has it
open and then their system/LibreOffice crashes. I haven't investigated
this but I suspect a lock file is being used to indicate whether or not
it's being used.

The output from PCManFM-Qt is actually quite useful. Those "file monitor
cannot be created" warnings originate from some SMB-specific code. It
would be interesting to compare this to what Thunar is doing, so if you
could test it, that would be great.

As always, thank you, Leó!

-- 
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 in Use

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1875717/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1875717] Re: Opening file from Samba share results in Document in Use

2020-12-15 Thread Walter Lapchynski
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 in the file manager to do the mounting. Assuming this works
correctly for all file managers, then we can safely put the blame on the
file managers themselves even though there must be something about
LibreOffice that makes it particular.
https://help.ubuntu.com/community/Samba/SambaClientGuide#Connecting_using_CIFS

 2. Run the file manager on the command line and see if it spits
anything out. I know with PCManFM-Qt, it also handles desktop
management, so there's a daemon running. You can find that and kill it
and then run `pcmanfm-qt --profile=lxqt 2>&1`. I'm less intimately
familiar with Thunar so I'll leave it as an exercise to the reader to
figure that out. :)

-- 
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 in Use

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1875717/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1908293] Re: "extract here" doesn't work

2020-12-15 Thread Walter Lapchynski
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 to run
file-roller (or unzip) against it manually to check that.

 2. The way the USB is mounted you don't have permissions to create
files on it.

 3. Something about Ubuntu is preventing you from doing this. I find
this really unlikely, but it's remotely possible.

-- 
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 go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1908293/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1908293] Re: "extract here" doesn't work

2020-12-15 Thread Walter Lapchynski
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 using one of the other
archiver methods but don't have the right archiver installed, that could
be the problem.

It could also be a problem with some other archiver, but we would need
to know which archiver you're using.

It could finally be a problem (given the fact that root works) with
permissions. If your archive is in / (for example), it won't work. But
you could do "Extract to" and it would, by default, offer you to put it
in your $HOME folder, which would not need root and would work fine.

Also: pcmanfm-qt and pcmanfm are completely different pieces of software
that ultimately do not share much in the way of a common core.

-- 
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 go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1908293/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1908293] Re: "extract here" doesn't work

2020-12-15 Thread Walter Lapchynski
** 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 go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1908293/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1875717] Re: Opening file from Samba share results in Document in Use

2020-12-14 Thread Walter Lapchynski
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 Ubuntu.
https://bugs.launchpad.net/bugs/1875717

Title:
  Opening file from Samba share results in Document in Use

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1875717/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1875717] Re: Opening file from Samba share results in Document in Use

2020-12-13 Thread Walter Lapchynski
@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 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 in Use

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1875717/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1875717] Re: Opening file from Samba share results in Document in Use

2020-12-13 Thread Walter Lapchynski
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 in Use

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1875717/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906162] Re: Lubuntu 20.04 and 20.10: Libreoffice: font of some dialog-windows is too small

2020-11-29 Thread Walter Lapchynski
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.
https://bugs.launchpad.net/bugs/1906162

Title:
  Lubuntu 20.04 and 20.10: Libreoffice: font of some dialog-windows is
  too small

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1906162/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1904866] Re: Software updater fails to update with errors

2020-11-21 Thread Walter Lapchynski
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.
https://bugs.launchpad.net/bugs/1904866

Title:
  Software updater fails to update with errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1904866/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1904269] Re: Apply full upgrade - fails with no error message

2020-11-21 Thread Walter Lapchynski
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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1904269/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1904269] Re: Apply full upgrade - fails with no error message

2020-11-18 Thread Walter Lapchynski
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 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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1904269/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1864787] Re: Lubuntu failed install "sfdisk --force --append /dev/sda"

2020-11-09 Thread Walter Lapchynski
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"

To manage notifications about this bug go to:
https://bugs.launchpad.net/calamares/+bug/1864787/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1901313] Re: Incorrect output when running bashtop

2020-10-25 Thread Walter Lapchynski
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 about locales and fonts. Freemono
should have excellent support for all of the required Unicode tables.

There's some mention of need for "wide characters" with no real
explanation of what, exactly, that means.

That said, without clearly defined requirements, I think it's much more
appropriate to blame bashtop itself here.

Finally: the description of the problem is poor to say the very least.
Linking elsewhere is not great, especially to somewhere that requires a
log in to see screenshots. Even there, there's some argument as to what
the problem is, or at least that's how I see it. That said, I'm setting
this as incomplete, to boot.

** Package changed: qterminal (Ubuntu) => bashtop (Ubuntu)

** Changed in: bashtop (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/1901313

Title:
  Incorrect output when running bashtop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bashtop/+bug/1901313/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

  1   2   3   4   5   6   7   8   9   10   >