from:"apt\-ghetto"

[Bug 1875774] Re: lxqt-policykit crashes with general protection fault in libgobject-2.0

2021-11-05 Thread apt-ghetto

** Patch added: "Debdiff for hirsute"
   
https://bugs.launchpad.net/ubuntu/+source/lxqt-policykit/+bug/1875774/+attachment/5538459/+files/lxqt-policykit_hirsute.debdiff

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

2021-11-05 Thread apt-ghetto

** Patch removed: "lxqt-policykit_focal.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/lxqt-policykit/+bug/1875774/+attachment/5523557/+files/lxqt-policykit_focal.debdiff

** Patch removed: "lxqt-policykit_hirsute.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/lxqt-policykit/+bug/1875774/+attachment/5523268/+files/lxqt-policykit_hirsute.debdiff

** Patch added: "Debdiff for focal"
   
https://bugs.launchpad.net/ubuntu/+source/lxqt-policykit/+bug/1875774/+attachment/5538458/+files/lxqt-policykit_focal.debdiff

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

2021-09-07 Thread apt-ghetto

debdiff for focal

** Description changed:

  [Impact]
  On Lubuntu systems with more than one sudoer, lxqt-policykit prior to version 
0.17.0 crashes due to calling g_object_unref twice on the same object.
  
  [Test Plan]
  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)
  
  EXPECTED RESULT
  ===
  Both the pkexec and the lxqt-admin-user change succeed without crashing.
  
  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]
  
  [Regression Potential]
  It might be possible, that not all sessions are deleted.
+ Or the patch was not properly updated and introduces new bugs.
  
  [Other info]
  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)

** Patch added: "lxqt-policykit_focal.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/lxqt-policykit/+bug/1875774/+attachment/5523557/+files/lxqt-policykit_focal.debdiff

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

2021-09-06 Thread apt-ghetto

debdiff for hirsute

** Patch added: "lxqt-policykit_hirsute.debdiff"
   
https://bugs.launchpad.net/lxqt/+bug/1875774/+attachment/5523268/+files/lxqt-policykit_hirsute.debdiff

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

2021-09-06 Thread apt-ghetto

** Description changed:

+ [Impact]
+ On Lubuntu systems with more than one sudoer, lxqt-policykit prior to version 
0.17.0 crashes due to calling g_object_unref twice on the same object.
+ 
+ [Test Plan]
  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)
+  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)
  
  EXPECTED RESULT
  ===
  Both the pkexec and the lxqt-admin-user change succeed without crashing.
  
  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]
  
+ [Regression Potential]
+ It might be possible, that not all sessions are deleted.
+ 
+ [Other info]
  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 1775980] Re: Add PolicyKit action to leafpad package

2021-05-22 Thread apt-ghetto

The support for Lubuntu 18.04 ended

** Changed in: leafpad (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/1775980

Title:
  Add PolicyKit action to leafpad package

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

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

[Bug 1878045] Re: doing dist-upgrade got error related do Broadcom

2021-01-30 Thread apt-ghetto

@supernoob3000

20.10 is still using kernel 5.8.

If you want help, you should open a new bug report and describe all the
steps and configuration changes.

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

Title:
  doing dist-upgrade got error related do Broadcom

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

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

[Bug 1862713] Re: Failed to verify signature archive-contents.sig

2020-08-05 Thread apt-ghetto

I had the same issue with emacs-nox, but I have installed it on Windows
10 inside of WSL2 with Ubuntu 18.04.

I was able to workaround the issue with:
gpg --homedir ~/.emacs.d/elpa/gnupg --keyserver hkps://keyserver.ubuntu.com:443 
--receive-keys 066DAFCB81E42C40

After successfully importing the key, a package-refresh-contents worked
fine.

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

Title:
  Failed to verify signature archive-contents.sig

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

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

[Bug 1878045] Re: doing dist-upgrade got error related do Broadcom

2020-05-24 Thread apt-ghetto

Thank you for this solution. It is working again.

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

Title:
  doing dist-upgrade got error related do Broadcom

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

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

[Bug 1876919] Re: 6.30.223.271+bdcom-0ubuntu6 fails when building on kernel 5.4.0-28-generic x86_64 (Ubuntu Groovy 20.10 dev.branch)

2020-05-14 Thread apt-ghetto

*** This bug is a duplicate of bug 1878045 ***
https://bugs.launchpad.net/bugs/1878045

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1878045, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.

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

Title:
  6.30.223.271+bdcom-0ubuntu6 fails when building on kernel
  5.4.0-28-generic x86_64 (Ubuntu Groovy 20.10 dev.branch)

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

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

[Bug 1877414] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu6: bcmwl kernel module failed to build

2020-05-14 Thread apt-ghetto

*** This bug is a duplicate of bug 1878045 ***
https://bugs.launchpad.net/bugs/1878045

** This bug is no longer a duplicate of bug 1876919
   6.30.223.271+bdcom-0ubuntu6 fails when building on kernel 5.4.0-28-generic 
x86_64 (Ubuntu Groovy 20.10 dev.branch)
** This bug has been marked a duplicate of bug 1878045
   doing dist-upgrade got error related do Broadcom

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu6: bcmwl kernel module
  failed to build

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

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

[Bug 1876919] Re: 6.30.223.271+bdcom-0ubuntu6 fails when building on kernel 5.4.0-28-generic x86_64 (Ubuntu Groovy 20.10 dev.branch)

2020-05-14 Thread apt-ghetto

*** This bug is a duplicate of bug 1878045 ***
https://bugs.launchpad.net/bugs/1878045

** This bug has been marked a duplicate of bug 1878045
   doing dist-upgrade got error related do Broadcom

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

Title:
  6.30.223.271+bdcom-0ubuntu6 fails when building on kernel
  5.4.0-28-generic x86_64 (Ubuntu Groovy 20.10 dev.branch)

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

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

[Bug 1877414] [NEW] bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu6: bcmwl kernel module failed to build

2020-05-07 Thread apt-ghetto

*** This bug is a duplicate of bug 1876919 ***
https://bugs.launchpad.net/bugs/1876919

Public bug reported:

Output from apt full-upgrade

bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu6) wird eingerichtet ...
Removing old bcmwl-6.30.223.271+bdcom DKMS files...

--
Deleting module version: 6.30.223.271+bdcom
completely from the DKMS tree.
--
Done.
Loading new bcmwl-6.30.223.271+bdcom DKMS files...
Building for 5.4.0-26-generic
Building for architecture x86_64
Building initial module for 5.4.0-26-generic
ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/bcmwl-kernel-source.0.crash'
Error! Application of patch 0028-add-support-for-linux-5.6.patch failed.
Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information.
dpkg: Fehler beim Bearbeiten des Paketes bcmwl-kernel-source (--configure):
 »installiertes bcmwl-kernel-source-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 6 zurück
Fehler traten auf beim Bearbeiten von:
 bcmwl-kernel-source
E: Sub-process /usr/bin/dpkg returned an error code (1)

Lubuntu 20.10

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu6
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu32
Architecture: amd64
CasperMD5CheckResult: skip
DKMSKernelVersion: 5.4.0-26-generic
Date: Thu May  7 17:39:25 2020
InstallationDate: Installed on 2019-09-21 (229 days ago)
InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190920)
PackageVersion: 6.30.223.271+bdcom-0ubuntu6
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2
SourcePackage: bcmwl
Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu6: bcmwl kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package groovy

** This bug has been marked a duplicate of bug 1876919
   6.30.223.271+bdcom-0ubuntu6 fails when building on kernel 5.4.0-28-generic 
x86_64 (Ubuntu Groovy 20.10 dev.branch)

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu6: bcmwl kernel module
  failed to build

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

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

[Bug 1875476] [NEW] Calamares aborts because of an AttributeError

2020-04-27 Thread apt-ghetto

Public bug reported:

[Summary]

During the installation process, the file /etc/apt/sources.list is
generated from a template. If an HTTPError occurs, then instead of
logging a message, an AttributeError is raised.

[Test Case]

Steps to reproduce
--

1. Start the installer.
2. When the automirror module is executed, provoke an HTTPError from
urllib.request.urlopen

Expected behaviour
--

The error is logged and the installer continues.

Current behaviour
-

An AttributeError is raised.

[Regression Potential]

There shouldn't be any regression potential.

[Other Info]

This error seems to occur only under special conditions, because it was
not noticed so far.

Existing forum post => https://discourse.lubuntu.me/t/installation-
failed-class-attribute-error/1019

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

** Description changed:

  [Summary]
  
  During the installation process, the file /etc/apt/sources.list is
  generated from a template. If an HTTPError occurs, then instead of
  logging a message, an AttributeError is raised.
- 
  
  [Test Case]
  
  Steps to reproduce
  --
  
  1. Start the installer.
  2. When the automirror module is executed, provoke an HTTPError from
  urllib.request.urlopen
  
  Expected behaviour
  --
  
  The error is logged and the installer continues.
  
  Current behaviour
  -
  
  An AttributeError is raised.
  
- 
  [Regression Potential]
  
  There shouldn't be any regression potential.
- 
  
  [Other Info]
  
  This error seems to occur only under special conditions, because it was
  not noticed so far.
+ 
+ Existing forum post => https://discourse.lubuntu.me/t/installation-
+ failed-class-attribute-error/1019

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

Title:
  Calamares aborts because of an AttributeError

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

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

[Bug 1871880] Re: "EFI system partition flag not set" - false pop-up

2020-04-25 Thread apt-ghetto

*** This bug is a duplicate of bug 1871884 ***
https://bugs.launchpad.net/bugs/1871884

** This bug has been marked a duplicate of bug 1871884
"EFI system partition flag not set" - false pop-up

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

Title:
  "EFI system partition flag not set" - false pop-up

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

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

[Bug 1872977] Re: Installation of lubuntu-desktop fails

2020-04-25 Thread apt-ghetto

*** This bug is a duplicate of bug 1873008 ***
https://bugs.launchpad.net/bugs/1873008

** This bug has been marked a duplicate of bug 1873008
   package lubuntu-grub-theme (not installed) failed to install/upgrade: error 
creating symbolic link 
'./boot/grub/themes/lubuntu-grub-theme/icons/ubuntu.png': Operation not 
permitted - symbolic link on  vfat filesystem

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

Title:
  Installation of lubuntu-desktop fails

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

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

[Bug 1872669] Re: BIOS logo reappears after the Lubuntu dots

2020-04-19 Thread apt-ghetto

** Also affects: lubuntu-artwork (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: lubuntu-artwork (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/1872669

Title:
  BIOS logo reappears after the Lubuntu dots

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

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

[Bug 1873008] Re: package lubuntu-grub-theme (not installed) failed to install/upgrade: error creating symbolic link './boot/grub/themes/lubuntu-grub-theme/icons/ubuntu.png': Operation not permitted -

2020-04-18 Thread apt-ghetto

@jibel Your typical use case (install in BIOS mode and reboot into UEFI
mode) ends typically in an error. There is no bootloader installed on
/boot/efi/EFI/ubuntu and there is no boot entry in the NVRAM, which
would point to shim or grub on the ESP.

The typical user has to replace grub-pc with grub-efi-* and create a
boot entry in the NVRAM (/sys/firmware/efi doesn't exist, neither in the
installed system, nor in the live-system). I guess, most users won't  do
that. They would simply reinstall in the desired mode.

Another possible problem I spotted: The installer created a msdos partition 
table on an empty disk (which isn't a problem). The problem starts, if the user 
installs Windows on this disk. Windows will be installed in BIOS mode and if 
you change the boot mode of Ubuntu, you don't have a dualboot anymore.
I didn't test it, but if the ESP is created as a logical partition, there are 
surely errors, if the system is booted in UEFI mode.

Meanwhile, I try to find a Lubuntu dev to fix lubuntu-artwork.

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

Title:
  package lubuntu-grub-theme (not installed) failed to install/upgrade:
  error creating symbolic link './boot/grub/themes/lubuntu-grub-
  theme/icons/ubuntu.png': Operation not permitted - symbolic link on
  vfat filesystem

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

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

[Bug 1873008] Re: package lubuntu-grub-theme (not installed) failed to install/upgrade: error creating symbolic link './boot/grub/themes/lubuntu-grub-theme/icons/ubuntu.png': Operation not permitted -

2020-04-17 Thread apt-ghetto

@jibel Thank you for explaining this.

Is it somewhere documented, why a EFI system partition is created on a
system, which is installed in BIOS mode?

I would expect a separate /boot partition with ext2 or ext4 and the ESP
(with the efi images for grub, shim and mok) only for systems which are
booting in EFI mode.

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

Title:
  package lubuntu-grub-theme (not installed) failed to install/upgrade:
  error creating symbolic link './boot/grub/themes/lubuntu-grub-
  theme/icons/ubuntu.png': Operation not permitted - symbolic link on
  vfat filesystem

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

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

[Bug 1873008] Re: package lubuntu-grub-theme (not installed) failed to install/upgrade: error creating symbolic link './boot/grub/themes/lubuntu-grub-theme/icons/ubuntu.png': Operation not permitted

2020-04-16 Thread apt-ghetto

Thank you for reporting this bug. I can confirm this behaviour with:
- virtual machine (qemu)
- booted in BIOS mode
- use the empty disk and choose ZFS automatism

I am not sure, if the created /etc/fstab is product of a bug or an
feature.

** Changed in: lubuntu-artwork (Ubuntu)
   Status: Incomplete => Confirmed

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

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

Title:
  package lubuntu-grub-theme (not installed) failed to install/upgrade:
  error creating symbolic link './boot/grub/themes/lubuntu-grub-
  theme/icons/ubuntu.png': Operation not permitted

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

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

[Bug 1873008] Re: package lubuntu-grub-theme (not installed) failed to install/upgrade: error creating symbolic link './boot/grub/themes/lubuntu-grub-theme/icons/ubuntu.png': Operation not permitted

2020-04-15 Thread apt-ghetto

Where does the fstab entry "/boot/efi/grub /boot/grub none defaults,bind
0 0" come from? Was it added automatically by the installer? Or did you
add it manually?

** Changed in: lubuntu-artwork (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/1873008

Title:
  package lubuntu-grub-theme (not installed) failed to install/upgrade:
  error creating symbolic link './boot/grub/themes/lubuntu-grub-
  theme/icons/ubuntu.png': Operation not permitted

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

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

[Bug 1872978] Re: Install of lubuntu-grub-theme fails

2020-04-15 Thread apt-ghetto

*** This bug is a duplicate of bug 1873008 ***
https://bugs.launchpad.net/bugs/1873008

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Marking this as a duplicate of bug 1873008. Please look
at the other bug report to see if there is any missing information that
you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1873008
   package lubuntu-grub-theme (not installed) failed to install/upgrade: error 
creating symbolic link 
'./boot/grub/themes/lubuntu-grub-theme/icons/ubuntu.png': Operation not 
permitted

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

Title:
  Install of lubuntu-grub-theme fails

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

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

[Bug 1871602] Re: /snap/bin not in environment variable Lubuntu

2020-04-10 Thread apt-ghetto

After installing snapd, do a logout and login. Then you should see, that
both $PATH and $XDG_DATA_DIRS contain the paths for snappy applications.

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

Title:
  /snap/bin not in environment variable Lubuntu

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

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

[Bug 1871602] Re: /snap/bin not in environment variable Lubuntu

2020-04-10 Thread apt-ghetto

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

** Changed in: snapd (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/1871602

Title:
  /snap/bin not in environment variable Lubuntu

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

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

[Bug 1800280] Re: Setting ZSH as login shell causes various issues because it doesn't source /etc/profile

2020-01-05 Thread apt-ghetto

Maybe the snapd packagers should not rely on the assumption, that every
user is using bash as login shell? More and more programs are only
available as snaps, e.g. chromium-browser.

Meanwhile I have added "emulate sh -c  'source /etc/profile'" to
/etc/zsh/zprofile to work around this issue. But a real solution would
be very nice.

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

Title:
  Setting ZSH as login shell causes various issues because it doesn't
  source /etc/profile

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

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

[Bug 1288786] Re: pkexec does not launch graphical authentication

2019-11-13 Thread apt-ghetto

No, pkexec per default does not start a graphical application for security 
reasons.
If you want to start a graphical application with pkexec, you need a policy in 
/usr/share/polkit-1/actions.

But, nowadays, it mostly isn't necessary to start a graphical
application with elevated privileges, because there are better
alternatives.

On *buntu 18.04, synaptic does have a policy => 
https://packages.ubuntu.com/bionic/amd64/synaptic/filelist
You can start it with synaptic-pkexec. The same command is used in 
/usr/share/applications/synaptic.desktop

If it does not work and you have a policy, please check, that the
PolicyKit Authentication Agent is running (lxsession-default-apps in
section autostart) and logout/login.

I don't understand, how "su -l $other_user" is related to this bug
report?

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

Title:
  pkexec does not launch graphical authentication

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

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

[Bug 1814407] Re: gnome-terminal thinks it is byobu (under LXQt)

2019-10-10 Thread apt-ghetto

Setting to incomplete, because 18.10 is out of support and with 19.04 I
could not reproduce it.

** Changed in: lxqt-panel (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/1814407

Title:
  gnome-terminal thinks it is byobu (under LXQt)

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

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

[Bug 1812594] Re: Lubuntu 18.04 mistakenly sets the default lock problem to lxlock instead of light-locker

2019-07-31 Thread apt-ghetto

Hi Chris Guiver,

Thank you for testing. I think, you are getting the results as described
in "Current behaviour". And yes, you should not install "lxlock".

Please check the installed version of "lubuntu-default-settings" with `apt 
policy lubuntu-default-settings`.
If you have version 0.54.2, then enable the "-proposed" sources, and `sudo apt 
install lubuntu-default-settings`.
This should install version 0.54.3, with the fix.
Then you can execute the test case and should have the same result as in 
"Expected behaviour".

You can check also (different results for 0.54.2 and 0.54.3):
`grep lock /etc/xdg/lxsession/Lubuntu/desktop.conf`
`grep lock ~/.config/lxsession/Luubntu/desktop.conf`

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

Title:
  Lubuntu 18.04 mistakenly sets the default lock problem to lxlock
  instead of light-locker

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

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

[Bug 1812594] Re: Lubuntu 18.04 mistakenly sets the default lock problem to lxlock instead of light-locker

2019-07-29 Thread apt-ghetto

** Patch added: "lubuntu-default-settings_0.54.3.debdiff"
   
https://bugs.launchpad.net/ubuntu/bionic/+source/lubuntu-default-settings/+bug/1812594/+attachment/5279787/+files/lubuntu-default-settings_0.54.3.debdiff

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

Title:
  Lubuntu 18.04 mistakenly sets the default lock problem to lxlock
  instead of light-locker

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

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

[Bug 1812594] Re: Lubuntu 18.04 mistakenly sets the default lock problem to lxlock instead of light-locker

2019-07-28 Thread apt-ghetto

** Description changed:

+ [Summary]
+
+ Instead to light-locker-command, the keyboard shortcut to lock the screen is
bound to lxlock. The problem is, that lxlock is not included in the iso of the
first two point releases (18.04 and 18.04.1) and therefore, the shortcut does
not work.
+ The ability to lock the screen is a basic security feature and should work as
expected, even with the provided shortcut.
+
+
+ [Test Case]
+
+ Steps to reproduce
+ --
+
+ 1. Boot Lubuntu 18.04 (installed from an older iso, not 18.04.2)
+ 2. Login
+ 3. Delete ~/.config/lxsession/Lubuntu/desktop.conf
+ 4. Logout
+ 5. Login
+ 6. Press CTRL-ALT-L
+
+ Expected behaviour
+ --
+
+ The desktop session is locked and requires the password to unlock.
+
+ Current behaviour
+ -
+
+ Nothing happens.
+
+
+ [Regression Potential]
+
+ If the command in the Exec line does not exist, nothing is executed, so the
behaviour does not change. Users with lxlock installed, won't notice any change
in the behaviour.
+ lxlock is a shell script, which calls light-locker-command (see:
https://github.com/lxde/lxsession/blob/master/lxlock/lxlock#L27), so the
regression potential is very, very small.
+
+
+ [Other Info]
+
+ Lubuntu uses another desktop environment from version 18.10 onwards. The
+ only version, which contains the patched file is 18.04. The Lubuntu Team
+ does not support Xenial anymore (16.04 has reached its end of life after
+ 3 years of community support).
+
+
+ -
+
+ [Previous Description]
+
Lubuntu 18.04 lxsession defines `lxlock` as the default for
"lock_manager/command" which lxhotkey calls via `lxsession-default lock`
when Ctrl-Alt-L is pressed. This should be changed in
/etc/xdg/lxsession/Lubuntu/desktop.conf to `light-locker`.

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

Title:
Lubuntu 18.04 mistakenly sets the default lock problem to lxlock
instead of light-locker

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

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

[Bug 1833490] Re: lubuntu grub-install puts efi in the wrong directory - could create an unbootable state

2019-07-23 Thread apt-ghetto

Thank you for filing this bug report.

In my opinion, this bug is not caused by grub2, but by a configuration
file in calamares-settings-ubuntu.

During installation the variable GRUB_DISTRIBUTOR in /etc/default/grub
is set to 'Lubuntu 19.04' instead of `lsb_release -i -s 2> /dev/null ||
echo Debian`.



[Test Case]
1. Install Lubuntu 19.04 in EFI mode
2. Check that there is a boot entry named "ubuntu" with: sudo efibootmgr -v
3. Install Grub: sudo grub-install
4. Check that there are now two boot entries for Lubuntu: One named "ubuntu" 
with "File(\EFI\ubuntu\shimx64.efi)"and another named "lubuntu" with 
"File(\EFI\lubuntu\shimx64.efi)"
5. Edit /etc/default/grub and replace "GRUB_DISTRIBUTOR='Lubuntu 19.04'" with 
"GRUB_DISTRIBUTOR='bug'"
6. Reinstall Grub
7. Check that there are now three boot entries for Lubuntu: "ubuntu", 
"lubuntu", and "bug"

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

Title:
  lubuntu grub-install puts efi in the wrong directory - could create an
  unbootable state

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

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

[Bug 1833490] Re: lubuntu grub-install puts efi in the wrong directory - could create an unbootable state

2019-07-23 Thread apt-ghetto

** Changed in: calamares-settings-ubuntu (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/1833490

Title:
  lubuntu grub-install puts efi in the wrong directory - could create an
  unbootable state

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

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

[Bug 1833490] Re: lubuntu grub-install puts efi in the wrong directory - could create an unbootable state

2019-07-23 Thread apt-ghetto

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

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

Title:
  lubuntu grub-install puts efi in the wrong directory - could create an
  unbootable state

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

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

[Bug 1812594] Re: Lubuntu 18.04 mistakenly sets the default lock problem to lxlock instead of light-locker

2019-07-16 Thread apt-ghetto

** Changed in: lubuntu-default-settings (Ubuntu)
   Status: Triaged => In Progress

** Changed in: lubuntu-default-settings (Ubuntu)
 Assignee: (unassigned) => apt-ghetto (apt-ghetto)

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

Title:
  Lubuntu 18.04 mistakenly sets the default lock problem to lxlock
  instead of light-locker

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

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

[Bug 1829693] Re: Lubuntu Daily ISO (May 19) QtPass error GnuPG not found

2019-06-24 Thread apt-ghetto

Hi @rinni,

On Lubuntu 19.10, the value for gpgExecutable in ~/.config/IJHack/QtPass.conf 
is not set.
After installing gnupg2 and moving/deleting ~/.config/IJHack/QtPass.conf and 
starting QtPass, it recreates the config file with gptExecutable=/usr/bin/gpg2 
and it works.

After git grepping:
I guess, the problem starts in 
https://github.com/IJHack/QtPass/blob/master/src/qtpasssettings.cpp#L289 
Interesting: 
https://github.com/IJHack/QtPass/blob/master/src/configdialog.cpp#L241

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

Title:
  Lubuntu Daily ISO (May 19) QtPass error GnuPG not found

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

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

[Bug 1827501] Re: keyboard layout different changes during installation set-up and boot for de-encrypting unencrypting hard drive

2019-05-08 Thread apt-ghetto

Now I understand, what you mean with the asterisks.
I think, it is normal to hide the passwords. And you have to enter the password 
twice, to ensure, that there are no typos. (And from a security point of view, 
it would be even better not to show the asterisks)
During the installation, it uses the keyboard layout, which you have selected. 
(Unless there is another bug.)

The problem is, that Grub does not have the information about the keyboard 
layout, when it attempts to open the LUKS container (because these informations 
are inside the LUKS container). It uses the American keyboard layout as default.
The other flavours don't have the /boot directory in an encrypted partition. So 
Grub loads the kernel (or a part of it), and the kernel then opens the LUKS 
container.

I would say, that dropping to a Grub rescue shell when entering the wrong 
password is a bug, that should be solved.
And there is a request to improve the Calamares UI to provide a clear 
information/message/warning, that Grub is using the American keyboard layout 
for unlocking the LUKS container.
I am not sure, if it would be possible, to change the keyboard layout of Grub. 
The packages of Grub are in main, and are not maintained by the team of Lubuntu.

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

Title:
  keyboard layout different changes during installation set-up and boot
  for de-encrypting unencrypting hard drive

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

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

[Bug 1827501] Re: keyboard layout different changes during installation set-up and boot for de-encrypting unencrypting hard drive

2019-05-08 Thread apt-ghetto

Thank you for reporting this issue.

I have made a new installation of Lubuntu 19.04 in a virtual machine
(Fedora 30 with Gnome Boxes). I choose the automatic installation with
full disk encryption in BIOS mode (legacy mode: bootloader in the MBR).
Calamares creates one encrypted LUKS container.

After rebooting, Grub asks for the passphrase to unlock the encrypted
LUKS container. I don't see any asterisks. How did you install Lubuntu
19.04?

Grub uses by default the American keyboard layout (it is Grub, that opens the 
LUKS containter, not the kernel from an unencrypted /boot, like the other 
flavours).
Let's assume, the passphrase contains a 'z', but with the American keyboard 
layout, it is a 'y'. After entering the "wrong" passphrase, I was dropped into 
the Grub rescue shell, which is a bug, in my opinion. At least it should 
permit, for example, 3 attempts to enter the passphrase before dropping into 
the Grub rescue shell. The error messages (UUID shortened) are:
error: access denied.
error: no such cryptodisk found.
error: disk `cryptouid/ad25aed...` not found.
Entering rescue mode

Possible workaround/solution: LUKS allows you to define up to 8 different 
passphrases. Let's assume, the LUKS container is on /dev/sda1. You can check 
first, how many key slots are free:
sudo cryptsetup luksDump /dev/sda1

There are normally 6 free key slots. Then add a passphrase, which you would 
receive if you use the American keyboard layout:
sudo cryptsetup luksAddKey /dev/sda1

After rebooting, you can enter the "wrong" passphrase and be able to
unlock the LUKS container.

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

Title:
  keyboard layout different changes during installation set-up and boot
  for de-encrypting unencrypting hard drive

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

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

[Bug 1814407] Re: gnome-terminal thinks it is byobu (under LXQt)

2019-02-09 Thread apt-ghetto

Hi,

I was unable to reproduce this bug on an up-to-date Lubuntu 19.04. But
then I tried it also on an up-to-date Lubuntu 18.10 and found out, that
this bug is reproducible under certain circumstances. Additionally I
used also xprop WM_CLASS:

On 18.10:
  - install first gnome-terminal and in a second step byobu
Using lxqt-runner it opens byobu in a gnome-terminal
Using lxqt-runner you cannot open gnome-terminal, because it is not 
suggested
  WM_CLASS(STRING) = "gnome-terminal-server", "us.kirkland.terminals.byobu"
  - install first byobu and in a second step gnome-terminal
Using lxqt-runner it opens byobu in a qterminal
Using lxqt-runner it opens gnome-terminal
  WM_CLASS(STRING) = "qterminal", "qterminal"
  WM_CLASS(STRING) = "gnome-terminal-server", "Gnome-terminal"

On 19.04:
  - install first gnome-terminal and in a second step byobu
Using lxqt-runner it opens byobu in a gnome-terminal
Using lxqt-runner you can open also gnome-terminal
  WM_CLASS(STRING) = "gnome-terminal-server", "us.kirkland.terminals.byobu"
  WM_CLASS(STRING) = "gnome-terminal-server", "Gnome-terminal"
Ergo: It is not reproducible
  - install first byobu and in a second step gnome-terminal
Using lxqt-runner it opens byobu in a qterminal
  WM_CLASS(STRING) = "qterminal", "qterminal"
  WM_CLASS(STRING) = "gnome-terminal-server", "Gnome-terminal"

On 18.10, installing first gnome-terminal and then byobu: if you purge
gnome-terminal, byobu doesn't work anymore.

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

Title:
  gnome-terminal thinks it is byobu (under LXQt)

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

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

[Bug 1775980] Re: Add PolicyKit action to leafpad package

2018-08-04 Thread apt-ghetto

** Package changed: leafpad (Ubuntu) => lubuntu-default-settings

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

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

Title:
  Add PolicyKit action to leafpad package

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

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

[Bug 1775980] Re: Add PolicyKit action to leafpad package

2018-06-09 Thread apt-ghetto

** Tags removed: lubuntu

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

Title:
  Add PolicyKit action to leafpad package

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

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

[Bug 1775980] [NEW] Add PolicyKit action to leafpad package

2018-06-09 Thread apt-ghetto

Public bug reported:

The package gksu has been removed from 18.04 and sudo should not be used
to start a graphical application, because of problems caused by
environment variables (e.g. $HOME, $XAUTHORITY) not set in the right
way.

Please add a PolicyKit action to the package, so that you can edit for
example the /etc/fstab configuration file by typing: pkexec leafpad
/etc/fstab

I suggest to add the file 
/usr/share/polkit-1/actions/com.ubuntu.pkexec.leafpad.policy with the content 
like:

http://www.freedesktop.org/standards/PolicyKit/1/policyconfig.dtd;>


  
Authentication is required to run the Leafpad Editor
leafpad

  auth_admin
  auth_admin
  auth_admin

/usr/bin/leafpad
true
  



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

** Tags added: lubuntu

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

Title:
  Add PolicyKit action to leafpad package

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

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

[Bug 1767703] Re: Calling 'apt-install grub-efi-amd64-signed' failed

2018-05-22 Thread apt-ghetto

To get a working dual boot, you have to install both operating systems in the 
same mode.
Of course, if you have a lot of time and patience, you can reinstall Windows. 
Reinstalling Ubuntu in the same mode as Windows is normally the faster way.

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

Title:
  Calling 'apt-install grub-efi-amd64-signed' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1767703/+subscriptions

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

[Bug 1767703] Re: Calling 'apt-install grub-efi-amd64-signed' failed

2018-05-19 Thread apt-ghetto

As far as I can see, the problem occurs only if the disk is MBR/MSDOS
formatted and the installer is booted in the EFI mode. So we should
create some test cases and test.


Test case 1:
Prerequisites:
 - one disk; partition table -> GPT
 - no EFI-System-Partition
 - The installer is booted in EFI mode => [ -d /sys/firmware/efi ] && echo UEFI 
|| echo BIOS
Expected result:
 - Warning is printed about missing ESP, no crash


Test case 2:
Prerequisites:
 - one disk; partition table -> MBR/MSDOS
 - no EFI-System-Partition
 - The installer is booted in EFI mode => [ -d /sys/firmware/efi ] && echo UEFI 
|| echo BIOS
Expected result:
 - Warning is printed about missing ESP, no crash


Test case 3:
Prerequisites:
 - one disk; partition table -> GPT
 - EFI-System-Partition exists
 - The installer is booted in EFI mode
Expected result:
 - Installation succeeds

Test case 4:
Prerequisites:
 - one disk; partition table -> MBR/MSDOS
 - EFI-System-Partition exists
 - The installer is booted in EFI mode
Expected result:
 - Installation succeeds

In my opinion, it is a bug in ubiquity, that it is not complaining about
a missing ESP before the installation begins.

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

Title:
  Calling 'apt-install grub-efi-amd64-signed' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1767703/+subscriptions

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

[Bug 1771651] Re: The installation fails with a "GRUB installation failed" message.

2018-05-19 Thread apt-ghetto

The installation fails because you have booted the installer in UEFI
mode and there is no EFI-System-Partition.

Your workaround describes how to install Grub in the BIOS legacy mode,
which works because Grub can be installed into the MBR.

First of all, the workaround is not really necessary because you can install 
Ubuntu in BIOS mode simply by booting the installer in the BIOS mode. 
(Depending on the UEFI you have and how you created the USB stick, this is not 
always a simple task)
And there is probably another problem, because during the installation in UEFI 
mode, some Grub packages are removed, e.g. grub-pc. Therefore I am not sure if 
you have really a complete installation or a standalone Grub, that will never 
receive updates.

Unfortunately there are no log files.

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

Title:
  The installation fails with a "GRUB installation failed" message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1771651/+subscriptions

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

[Bug 1767703] Re: Calling 'apt-install grub-efi-amd64-signed' failed

2018-05-02 Thread apt-ghetto

@Gil0224, that is not true.

GPT is part of the UEFI standard, but you can install a Linux OS also in
BIOS Legacy mode on a GPT formatted disk (you need a bios_grub-
partition). On the other side you can install a Linux OS on a MBR
formatted disk in UEFI mode.

If you install in the UEFI mode, you just need an EFI-System-Partition
with FAT32 as filesystem.

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

Title:
  Calling 'apt-install grub-efi-amd64-signed' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1767703/+subscriptions

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

[Bug 1763554] Re: grub install failed along with ubuntu installation crashing, left unbootable

2018-04-27 Thread apt-ghetto

You started the installer in UEFI mode, but your installation is in the BIOS 
legacy mode.
Booting the installer in BIOS mode should resolve your installation problem.

** Changed in: grub-installer (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/1763554

Title:
  grub install failed along with ubuntu installation crashing, left
  unbootable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1763554/+subscriptions

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

[Bug 1763441] Re: Installation of ubuntu 1804 crashed around the time of installing grub

2018-04-27 Thread apt-ghetto

You try to install Ubuntu in EFI mode, but you do not have an EFI System 
partition.
But if you have Windows installed on the disk, you should boot the installer in 
BIOS legacy mode and you will get a working dualboot (no EFI System partition 
needed).

** Changed in: grub-installer (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/1763441

Title:
  Installation of ubuntu 1804 crashed around the time of installing grub

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1763441/+subscriptions

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

[Bug 1763162] Re: won't boot grub missing someting

2018-04-27 Thread apt-ghetto

You try to install Ubuntu in EFI mode, but you do not have an EFI System 
partition.
If you have a Windows installed on the same disk, you should boot the installer 
in the BIOS legacy mode to get a working dualboot.

** Changed in: grub-installer (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/1763162

Title:
  won't boot grub missing someting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1763162/+subscriptions

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

[Bug 1762919] Re: not installing grub

2018-04-27 Thread apt-ghetto

You try to install Ubuntu in EFI mode, but you do not have an EFI System 
partition.
Either create a EFI System partition and install in UEFI mode, or boot the 
installer in the BIOS legacy mode and install Ubuntu (no ESP needed).

** Changed in: grub-installer (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/1762919

Title:
  not installing grub

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1762919/+subscriptions

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

[Bug 1762943] Re: grub fails to install in target partition, installer bail out.

2018-04-27 Thread apt-ghetto

You try to install Ubuntu in UEFI mode, but you do not have an EFI System 
Partition.
I see some NTFS partitions, so if you have a Windows installed on the disk, you 
should boot the installer in the BIOS legacy mode t get a working dualboot.

** Changed in: grub-installer (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/1762943

Title:
  grub fails to install in target partition, installer bail out.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1762943/+subscriptions

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

[Bug 1762209] Re: trying to install ubuntu 18.04 grub install failed

2018-04-27 Thread apt-ghetto

You try to install in UEFI mode, but you do not have an EFI System
Partition.

** Changed in: grub-installer (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  trying to install ubuntu 18.04 grub install failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1762209/+subscriptions

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

[Bug 1704510] Re: Installing GRUB EFI failed on USB3 stick.

2017-10-04 Thread apt-ghetto

The custom mode is for experienced users. And experienced users should
know the basics about booting an OS and partitioning.

** Changed in: grub-installer (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/1704510

Title:
  Installing GRUB EFI failed on USB3 stick.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1704510/+subscriptions

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

[Bug 1716192] Re: Dell 7560 a30s

2017-09-27 Thread apt-ghetto

You try to install Ubuntu in UEFI mode, but you do not have an EFI-
System-Partition.

** Changed in: grub-installer (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/1716192

Title:
  Dell 7560 a30s

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1716192/+subscriptions

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

[Bug 1716211] Re: Installation of OS failed

2017-09-27 Thread apt-ghetto

You try to install Ubuntu in UEFI mode, but you do not have an EFI-
System-Partition. If you have a Windows installed on the same disk, then
you should install Ubuntu in BIOS mode to get a working dual boot.

** Changed in: grub-installer (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/1716211

Title:
  Installation of OS failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1716211/+subscriptions

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

[Bug 1715675] Re: Grub installation on new computer crashed

2017-09-27 Thread apt-ghetto

You try to install Ubuntu in UEFI mode, but you do not have an EFI-
System-Partition. Your Windows seems to be installed in BIOS mode on
your first disk. To get a working dual boot, you have to start the
installer in BIOS mode and create an bios_grub partition on your GPT
disk for Grub or install Grub on your first disk.

** Changed in: grub-installer (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/1715675

Title:
  Grub installation on new computer crashed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1715675/+subscriptions

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

[Bug 1715326] Re: grub not installed during ubuntu installation

2017-09-27 Thread apt-ghetto

You try to install Ubuntu in UEFI mode, but you do not have an EFI-
System-Partition. If you have a Windows installed on the same disk, then
you should install Ubuntu in BIOS mode to get a working dual boot.

** Changed in: grub-installer (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/1715326

Title:
  grub not installed during ubuntu installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1715326/+subscriptions

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

[Bug 1705225] Re: Wouldn't install GRUB on installation (UEFI boot)

2017-07-21 Thread apt-ghetto

This bug report is being closed due to your last comment. For future
reference you can manage the status of your own bugs by clicking on the
current status in the yellow line and then choosing a new status in the
revealed drop down box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

** Changed in: grub-installer (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Wouldn't install GRUB on installation (UEFI boot)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1705225/+subscriptions

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

1 2 >

1 - 100 of 171 matches

Mail list logo