[Bug 2066483] Re: lock screen

2024-05-22 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709


You've reported this as a documentation issue, but haven't provided details of 
which address/page where the documentation needs correcting. ie.  Was it a page 
viewed after https://help.ubuntu.com/ and if so which page in ubuntu-docs needs 
correcting? and what exactly is the issue.

Are you seeking support?   If so I suggest a support site, this question
can be converted into a question which will change the emphasis to
support (instead of current focus on fixing an issues with ubuntu-docs
or documentation).

** Changed in: ubuntu-docs (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/2066483

Title:
  lock screen

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


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

[Bug 2066481] Re: lock screen

2024-05-22 Thread Chris Guiver
*** This bug is a duplicate of bug 2066483 ***
https://bugs.launchpad.net/bugs/2066483

** This bug has been marked a duplicate of bug 2066483
   lock screen

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

Title:
  lock screen

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


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

[Bug 2066309] Re: freezing, acting eratic

2024-05-22 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 2066309

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.


I've marked this report as INCOMPLETE, as no release details, package details 
etc were provided. Once you've run the `apport-collect` command on your box, 
please return the status to "New".

** Changed in: gimp (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/2066309

Title:
  freezing, acting eratic

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


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

[Bug 2066310] Re: freezing, acting eratic

2024-05-22 Thread Chris Guiver
*** This bug is a duplicate of bug 2066309 ***
https://bugs.launchpad.net/bugs/2066309

** This bug has been marked a duplicate of bug 2066309
   freezing, acting eratic

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

Title:
  freezing, acting eratic

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


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

[Bug 2066158] Re: Can't boot to SD OS when insert empty USB driver

2024-05-20 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 2066158

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.

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

Title:
  Can't boot to SD OS when insert empty USB driver

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


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

[Bug 2066158] Re: Can't boot to SD OS when insert empty USB driver

2024-05-20 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Please also ensure that you include the release and flavour of Ubuntu
that you are using.


Please note, bug reporting is about finding & fixing problems thus preventing 
future users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709.

** Changed in: grub2 (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/2066158

Title:
  Can't boot to SD OS when insert empty USB driver

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


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

[Bug 2066064] Re: Dell Latitude 5450 and 5550 Ethernet dropped packets (Intel Meteor Lake CPU with 8086:550a NIC)

2024-05-19 Thread Chris Guiver
** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

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

Title:
  Dell Latitude 5450 and 5550 Ethernet dropped packets (Intel Meteor
  Lake CPU with 8086:550a NIC)

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


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

[Bug 2066064] Re: Dell Latitude 5450 and 5550 Ethernet dropped packets (Intel Meteor Lake CPU with 8086:550a NIC)

2024-05-19 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

You've filed this bug against the Ubuntu-Release-Upgrader package, which
will upgrade a release from 22.04 to 23.10 (or 24.04 in the future), but
no logs or mention of problems with that are mentioned.

Ubuntu 22.04 LTS is a LTS release, thus has some kernel stack choices
(GA = 5.15, HWE = 6.5, OEM = ...) but no clues as to product (Server?
Desktop?) were provided, nor what install media was used (ie. kernel
stack defaults are unknown). Your description implies network issues,
where bug report is filed against the `do-release-upgrade` (or
equivalent) command without logs..

I suggest trying support first..  as your issue maybe more linked to the
linux kernel (or kernel modules) and not what you've filed the bug
against; but no details as to what you're running were actually provided
(release requires product & install media details to be known for LTS
releases with kernel stack choice).

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

Title:
  Dell Latitude 5450 and 5550 Ethernet dropped packets (Intel Meteor
  Lake CPU with 8086:550a NIC)

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


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

[Bug 2066098] Re: release upgrade doesn't work, way to many "Broken" to make sense of

2024-05-19 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

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

Title:
  release upgrade doesn't work, way to many "Broken" to make sense of

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2066098/+subscriptions


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

[Bug 2066081] Re: Nouveau failing to boot or glitches

2024-05-19 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 2066081

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.

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

Title:
  Nouveau failing to boot or glitches

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


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

[Bug 2065565] Re: package grub-pc 2.06-2ubuntu7.2 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 10

2024-05-13 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

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

Title:
  package grub-pc 2.06-2ubuntu7.2 failed to install/upgrade: installed
  grub-pc package post-installation script subprocess returned error
  exit status 10

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


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

[Bug 2064909] Re: Lubuntu and Kubuntu 24.04 fail to decrypt on boot when installed on encrypted partition

2024-05-07 Thread Chris Guiver
Thanks for the additional testing.

The erase disk & install using encryption gets more QA
(https://discourse.lubuntu.me/t/testing-checklist-noble/4809 shows six
QA tests for that), and whilst there are some manual partitioning
install tests, no encryption is mandated there.

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

Title:
  Lubuntu and Kubuntu 24.04 fail to decrypt on boot when installed on
  encrypted partition

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


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

[Bug 2064882] Re: web camera doesn't work after update

2024-05-06 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

You've filed this bug against the upgrade process of 18.04 that upgraded
you to 20.04 that was run 360 days ago?  (Ubuntu-release-upgrader
upgrades your release, last run 360 days ago, and won't be run again
until you upgrade to 22.04, but you mention this as a regular cycle?)  I
suggest support, as I'm unsure what your issue is.

It maybe helpful to convert this question into a question (ie. geared at
support), at least until its worked out what your issue, but its
unlikely the tool you ran 360 days ago & hasn't run again since. Maybe
kernel, kernel module instead is your issue.

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

Title:
  web camera doesn't work after update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2064882/+subscriptions


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

[Bug 2064909] Re: Lubuntu and Kubuntu 24.04 fail to decrypt on boot when installed on encrypted partition

2024-05-06 Thread Chris Guiver
Thanks for responding, AND asking for further help!

Sorry I didn't think thru my wording clear enough...   To be useful the 
`apport-collect` has to be run AFTER a failed install, however to confirm it 
failed (by your already provided description) you need to reboot & thus the 
report I want will have been lost (due to reboot).  My mistake Sorry.
-- NEW INSTRUCTIONS FOLLOW

Please boot your machine again (install media), run the install (as
you've done a number of times again) and then after install completes DO
NOT REBOOT when asked to.

Instead open a terminal and run

apport-collect 2064909

ie. it'll add details from that machine, your ISO used, and the install
report & other details from the currently 'it appeared to work'
install... THEN YOU CAN REBOOT.

On reboot, you can confirm the INSTALL FAILED (ie. you could NOT boot
into your installed system) or INSTALL SUCCEEDED...

At this time, return to this report & please just add a comment that
followed instructions I laid out here (comment #3) and run `apport-
collect` as requested, and please add the install FAILED TO BOOT (as
described in bug description), or worked perfectly etc... (or whatever
you feel compelled to add given you're running the install).

THANK YOU for taking time here to make our Ubuntu system better (Ubuntu
includes flavors like Lubuntu/Kubuntu..)

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

Title:
  Lubuntu and Kubuntu 24.04 fail to decrypt on boot when installed on
  encrypted partition

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


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

[Bug 2064909] Re: Lubuntu and Kubuntu 24.04 fail to decrypt on boot when installed on encrypted partition

2024-05-06 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

If possible, can you boot your system (using 24.04 media you tried to
install) and try the install again, assuming it fails again, please
follow the following instructions AFTER the error has [re-]occurred.

Please execute the following command only once, as it will automatically
gather debugging information, in a terminal:

apport-collect 2064909

( 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. )

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

Title:
  Lubuntu and Kubuntu 24.04 fail to decrypt on boot when installed on
  encrypted partition

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


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

[Bug 2064845] Re: Right clicking quickly will select the first menu entry

2024-05-05 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 2064845

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.

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

Title:
  Right clicking quickly will select the first menu entry

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


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

[Bug 2064846] Re: xfce4-panel should be upgraded to 4.18.6 if glib 2.80 is used

2024-05-05 Thread Chris Guiver
** Tags added: noble

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

Title:
  xfce4-panel should be upgraded to 4.18.6 if glib 2.80 is used

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/2064846/+subscriptions


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

[Bug 2064668] Re: Calamares/Kubuntu 24.04: Can't create encrypted LVM

2024-05-03 Thread Chris Guiver
Likely duplicate (or related) to
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1900266

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

Title:
  Calamares/Kubuntu 24.04: Can't create encrypted LVM

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


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

[Bug 2064180] Re: calamares-finish-oem.desktop is untrusted

2024-04-30 Thread Chris Guiver
** Tags added: oracular

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

Title:
  calamares-finish-oem.desktop is untrusted

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


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

[Bug 2063984] Re: package chromium-browser 1:124.0.6367.78-0ubuntu0.22.04.1sav0 failed to install/upgrade: le sous-processus nouveau chromium-browser paquet pre-installation script a renvoyé un état d

2024-04-28 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709.ReportingBugs.

The package of chromium for 24.04/noble is
https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/2:1snap1-0ubuntu2  which is not what you're using.  If you wish
to file a bug report on your chromium package, you'd have to file it
with whomever packaged it (PPA owner), as it's not a Ubuntu 24.04
package.


** Changed in: chromium-browser (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/2063984

Title:
  package chromium-browser 1:124.0.6367.78-0ubuntu0.22.04.1sav0 failed
  to install/upgrade: le sous-processus nouveau chromium-browser paquet
  pre-installation script a renvoyé un état de sortie d'erreur 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063984/+subscriptions


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

[Bug 2063500] Re: GIMP crashed with a fatal error: fatal error: Erreur de segmentation

2024-04-26 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 2063500

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.

(The pasted details are intended for filing bugs upstream with GNU Gimp;
Ubuntu system details have not been provided)

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

Title:
  GIMP crashed with a fatal error: fatal error: Erreur de segmentation

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


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

[Bug 2063516] Re: GIMP crashes on close

2024-04-26 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 2063516

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.

(The pasted details are intended for filing bugs upstream with GNU Gimp;
Ubuntu system details have not been provided)

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

Title:
  GIMP crashes on close

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


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

[Bug 2063513] Re: torbrowser unusable - not accepting keyboard input

2024-04-26 Thread Chris Guiver
*** This bug is a duplicate of bug 2056578 ***
https://bugs.launchpad.net/bugs/2056578

** This bug has been marked a duplicate of bug 2056578
   Tor Browser - keyboard not functioning

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

Title:
  torbrowser unusable - not accepting keyboard input

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/2063513/+subscriptions


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

[Bug 2063545] Re: package click 0.5.2-2ubuntu4 failed to install/upgrade: new click package pre-removal script subprocess returned error exit status 1

2024-04-26 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709.

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

Title:
  package click 0.5.2-2ubuntu4 failed to install/upgrade: new click
  package pre-removal script subprocess returned error exit status 1

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


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

[Bug 2063502] Re: 24.04: dvd image wont fit on dvd and missing libraries

2024-04-26 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Please also ensure that you include the release and flavour of Ubuntu
that you are using.

The capacity of a dual layer DVDR(W) is 8.3-8.5GB  (8.5GB unformatted),
which will fit a Ubuntu ISO though you didn't specify what Ubuntu
product/ISO you're meaning; eg. a Ubuntu Desktop 24.04 LTS ISO is
smaller (5.7GB) than this size for example. A single layer DVD is of
course smaller, but the intended install media today has been a USB
flash drive for some time.

Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709.

Thank you!

** Changed in: 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/2063502

Title:
  24.04: dvd image wont fit on dvd and missing libraries

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


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

[Bug 2060624] Re: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice

2024-04-25 Thread Chris Guiver
Thank you Mate for working out issue & great explanation..

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

Title:
  lubuntu/xubuntu reinstall (& install) on dual boot system, grub does
  appear & offer OS choice

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


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

[Bug 2060624] Re: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice

2024-04-24 Thread Chris Guiver
install using Lubuntu 20240425 ISO (latest RC as of now) and issue
reoccurred.  on ISO is

calamares   3.3.5-0ubuntu4


as before

- erase disk & install to dc7700
- install alongside (slider moved random amount as usual, so size [of 
partitions] aren't critical
- install & re-use SDA1 (first installed partition; what was shrunk) and 
critically NO-FORMAT is used

on reboot, no grub menu appears.
if I go to terminal and `sudo update-grub`... no other OS is shown, with 
'OS_PROBER will not be executed' message appears..

I can't boot into the other OS that was present before this QA-install
test.

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

Title:
  lubuntu/xubuntu reinstall (& install) on dual boot system, grub does
  appear & offer OS choice

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


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

[Bug 2063357] Re: attempting to use idle brightness in lxqt-powermanagement leads to crash on 22.04.4 LTS

2024-04-24 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

You mention it was "Reported 1 year 8 months ago" if so please provide
the bug report link, as you only provided reference to a support site
(which isn't a bug report). FYI: I'd have appreciated a picture of the
image in english; the picture provided via link to askubuntu alas wasn't
in english.

If you update your LXQt using Lubuntu backports, does the issue still
occur ??

ie. your report here mentions using

lxqt-powermanagement 0.17.1-0ubuntu1

where the version in Lubuntu backports (for 22.04/jammy) is

1.4.0-0ubuntu2~ppa1

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

Title:
  attempting to use idle brightness in lxqt-powermanagement leads to
  crash on 22.04.4 LTS

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


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

[Bug 2061214] Re: [SRU] Software Sources is not compatible with deb822

2024-04-24 Thread Chris Guiver
Booted an install made earlier today on hp_compaq_dc7700 of lubuntu
noble (20240424) ;
https://iso.qa.ubuntu.com/qatracker/milestones/453/builds/300235/testcases/1701/results/

sudo apt update; sudo apt full-upgrade & no updates are available.
(software-properties-qt 0.99.48.1)

Following the "Intended Functionality" listed in the Bug.Description at
the top of this bug report and behavior is what I'd expect.

The `/etc/apt/sources.list` file contained comments only ; with all
subsequent changes being reflected in
`/etc/apt/sources.list.d/ubuntu.sources` and looked appropriate to me.

However I'm tired, and fear I've missed something (that I can't 'put my
finger on'), but I've repeated steps 1..7 twice & didn't locate what
'irks' me sorry.

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

Title:
  [SRU] Software Sources is not compatible with deb822

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


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

[Bug 2060624] Re: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice

2024-04-23 Thread Chris Guiver
(
another FYI   I mentioned it's no longer re-creatable with Xubuntu due to 
forced FORMAT currently with `ubuntu-desktop-installer` ...

the issue i'm referring to is/was https://bugs.launchpad.net/ubuntu-
desktop-provision/+bug/2058638  .. current 'fix' being to force format ,
but my understanding is that will be reverted once time is available to
correct the current 'regression' format triggers with 24.04 over 23.10 &
earlier)

This bug (2060624) thus can only be triggered (I believe) by the calamares 
installer used Lubuntu, Kubuntu & Ubuntu.Unity;  as ubuntu-desktop-installer is 
forcing format (at least for now).
)

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

Title:
  lubuntu/xubuntu reinstall (& install) on dual boot system, grub does
  appear & offer OS choice

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


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

[Bug 2060624] Re: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice

2024-04-23 Thread Chris Guiver
Just an FYI... but on the two cases I've encountered this issue I didn't
install as per #14.  I'll have always performed a

1. full disk install (any prior partitioning erased); noble (may not have been 
lubuntu) but single partition only
2. install alongside (calamares wording; auto-resize type creating a second 
install)

(ie. I did two install types & achieved same result as steps 1 & 2 as
Mate (mkukri) in comment #14)

At step 3 my usual thing is a 'replace partition' (calamares wording)
install using one of the partitions (this is a FORMAT install).. where
which partition I use is ~random (usually opting to keep the partition
I'll most recognize as untouched; the install where I changed the
wallpaper usually so easily recognized)..

Any testing of 'install using existing partition' for me would be 4th
(or 5th) install almost guaranteed I believe..

My point is it can be triggered in other ways I believe, but again very
few users will encounter it... I rarely encountered it!


(then again what I listed ^ is what I did today, do most days probably too.. 
maybe why I've not experienced it much as I suspect i re-use SDA2 most days (& 
not sda1); ie. changing wallpaper on that first install (of the day) so its 
recognized on the many installs that usually follow...)

I concur with view not a release blocker.

--  said by me on #lubuntu-devel (matrix)
> It may worthwhile (if not fixed & I doubt it will be) for me to create a page 
> on [lubuntu]discourse(doco) for users should they encounter this issue  ... 
> to me it's not a big issue; I've only encountered it rarely, it requires 
> specific conditions I doubt many will encounter.. but could be mentioned in 
> release notes as well with somewhere we can point users too...

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

Title:
  lubuntu/xubuntu reinstall (& install) on dual boot system, grub does
  appear & offer OS choice

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


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

[Bug 2060624] Re: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice

2024-04-23 Thread Chris Guiver
I completed an install on dc7700

- two systems (noble) exist on drive
- boot install media (lubuntu noble RC)
- select partition (I selected SDA2, ignoring SDA1) for `/` WITHOUT FORMAT
- let it install

(this system is OLD, legacy-BIOS so no ESP; Lubuntu's calamares doesn't
create one by default for BIOS machine; iso.qa report at
https://iso.qa.ubuntu.com/qatracker/milestones/453/builds/300140/testcases/1701/results/)

on reboot; two options appeared in grub.

- SDA1 was in grub & when booted looked untouched
- SDA2 contained new install, file-system system directories all time-stamped 
mins ago (not hours ago) as expected for new install.. packages I added are 
present (fortune, clementine etc)..

I COULD NOT RE-CREATE THIS ISSUE..

Only difference between this and prior install could have been I
selected second partition (SDA2) where last time I selected SDA1?? but I
can't see that as making an difference; could it??


Given I've only experienced this issue twice, and could not re-create.. I'd be 
happy with marking bug as INCOMPLETE..


I could re-try by installing to SDA1 (same type of install) if you think there 
is any chance of difference.. but I couldn't re-create issue today (me 
attempting same type of install on same box)

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

Title:
  lubuntu/xubuntu reinstall (& install) on dual boot system, grub does
  appear & offer OS choice

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


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

[Bug 2060624] Re: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice

2024-04-23 Thread Chris Guiver
I have made many installs of various boxes, and exploring logs of the
iso.qa.ubu link in comment #3 i see only two references to this issue
(within a few days of each other), which include the following

---
hp dc7700 (c2d-e6320, 8gb, amd/ati rv610/radeon hd2400 pro/xt)
testcase: install using existing partition
---

I've made four installs on that box today
(https://iso.qa.ubuntu.com/qatracker/milestones/453/builds/300140/testcases/1701/results/)
yet did NOT experience the issue.  Currently the box has two installs
(first was full disk, then auto-resize equiv.. ) so I'll try and repeat
the install I made in the next hour+ and see if it occurs.

Lubuntu testcases are described here -
https://discourse.lubuntu.me/t/testing-checklist-understanding-the-
testcases/2743

but an INSTALL USING EXISTING PARTITION means

- boot install media
- using manual partitioning, selecting an existing partition (for /) BUT DO NOT 
FORMAT  (ie. re-use it...)


This is NO longer possible with Xubuntu as FORMAT is now mandatory (due to 
another bug, scheduled for fix post-release of noble..) 

I'll add some non-standard packages to one of my installed systems on
dc7700 (per testcase; something for installer to re-install), then
attempt to re-create this issue & reply back in an hour (or three) and
see if it re-occurs...  then provide detailed description of what I did
(if issue re-occurs).

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

Title:
  lubuntu/xubuntu reinstall (& install) on dual boot system, grub does
  appear & offer OS choice

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


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

[Bug 2013074] Re: changing monitor configuration & on next login, only one monitor is fully usable to LXQt

2024-04-22 Thread Chris Guiver
Another boot on next box

- hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)

This box shares same screens, so pretty much same change in
monitor.settings; except I didn't have to change the primary.display as
what booted in live mode is what I prefer.

identical issue & behavior though as last comment (#12)

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

Title:
  changing monitor configuration & on next login, only one monitor is
  fully usable to LXQt

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


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

[Bug 2013074] Re: changing monitor configuration & on next login, only one monitor is fully usable to LXQt

2024-04-22 Thread Chris Guiver
first boot of lubuntu noble RC on 
- hp prodesk 400 g1 sff (i5-4570, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)

live test, on adjusting displays to match my config... what was by
default.right monitor below the default.left, plus making my.bottom
(what was default.right) monitor the primary.display..

my.top monitor (what was default.right) now has no background, and
right-click on black has the options of

- terminal emulator
- web browser
- applications
- obconf
- reconfigure
- restart
- exit

operation of system though is not impacted.. and with play (3-5 mins) I
know I can revert the issue anyway (historically anyway)

--- i was going to close down LIVE testing.. so used the (on display)
EXIT menu to exit to see what it did...

On clicking the EXIT on obmenu

- both wallpapers now display
- lxqt-panel is now gone (would be annoying for non-technical users)
- right-click on background on both displays now shows LXQt menu
- no borders in the windows I had open (fair enough given I exited openbox)..

the wallpaper appearing on the BLACK SCREEN is what surprised me, thus
why this add of detail.

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

Title:
  changing monitor configuration & on next login, only one monitor is
  fully usable to LXQt

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


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

[Bug 2062428] Re: Install randomly crashes/fails/hangs on systems with 3GB or less

2024-04-18 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 2062428

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.

No clues as to product are provided (three flavors use calamares, though
Kubuntu is used as example so it maybe Kubuntu but we don't know; is
this 24.04? as its not said though mentioned too), nor clues as to what
ISO was used, nor package version details. It's likely nothing can be
done without this detail; as package versions have changed multiple
times in the last few days & no useful data (no logs etc) were provided.
Please in future use `ubuntu-bug`... which can be run even from terminal
even during operation (or calamares-hang).

If your system has already gone (ie. I assume it was LIVE and thus after
failure you shutdown box), some detail can be added to the report if you
BOOT the same ISO on the SAME HARDWARE and run `apport-collect 2062428`
as requested there. This will populate most missing fields, even if no
calamares-log will be attached (you'd need to re-run the install & have
the same issue to get that).

As currently little detail is provided, I'll mark this bug as
incomplete.  If you do run `apport-collect`, please change the status
back to "New".   Thank you for filing the bug report in attempts to make
Ubuntu better.

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

Title:
  Install randomly crashes/fails/hangs on systems with 3GB or less

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


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

[Bug 2060592] Re: lubuntu noble - another timeout issue (600 secs)

2024-04-18 Thread Chris Guiver
duplicate of
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2062106
maybe???

that message says 900 secs (not 600)  ... is there a condition for time
of internet  (900 for wifi; 600 for cable here.. but cause I see as
identical)

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

Title:
  lubuntu noble - another timeout issue (600 secs)

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


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

[Bug 2062106] Re: lubuntu noble - snap-seed-glue --seed ..calamares..snapd/seed krita -- failed to finish in 900 seconds

2024-04-18 Thread Chris Guiver
repeat only different timeout period? in
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2060592

duplicate?

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

Title:
  lubuntu noble - snap-seed-glue --seed ..calamares..snapd/seed krita
  -- failed to finish in 900 seconds

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


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

[Bug 2062106] Re: lubuntu noble - snap-seed-glue --seed ..calamares..snapd/seed krita -- failed to finish in 900 seconds

2024-04-18 Thread Chris Guiver
If this isn't changed... Lubuntu (me) could always add a page at

https://discourse.lubuntu.me/c/documentation/20

In summary; my install worked; except
- the third party packages however were not installed, 
- the `/var/log/installer` directory did NOT exist thus some metadata was 
missing from the install etc

Users have the option of

(a) testing their systems, if it was like mine, everything appeared to
work perfectly, and they can just add the 3rd party apps themselves &
expect no further problems (they're unlikely to notice the missing
metadata anyway)

OR

(b) restart install WITHOUT 3rd party apps... then reboot into their new
install, and add the third party apps themselves.  This option will
ensure they have all their metadata (ie. in the future can look up what
media they used for install, details of install etc, details that would
be missing with alternative (a))

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

Title:
  lubuntu noble - snap-seed-glue --seed ..calamares..snapd/seed krita
  -- failed to finish in 900 seconds

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


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

[Bug 2062106] [NEW] lubuntu noble - snap-seed-glue --seed ..calamares..snapd/seed krita -- failed to finish in 900 seconds

2024-04-17 Thread Chris Guiver
Public bug reported:

full install to sony vaio thingy
- sony vaio ultrabook svp11216cgb (i5-9400u, 4gb, intel haswell-ULT)

testcase: testcase: full, encryption, EFI, internet, swap, updates

no ethernet, so limited to wifi (300n so should be that bad, but still
aussie nbn so not fast)

---
2024-04-18 - 13:28:34 [1]: void 
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
2024-04-18 - 13:28:34 [1]: ERROR: Installation failed: "External command 
failed to finish." 
2024-04-18 - 13:28:34 [6]: .. - message: "External command failed to 
finish." 
2024-04-18 - 13:28:34 [6]: .. - details: Command snap-seed-glue --seed 
/tmp/calamares-root-8p789tsd/var/lib/snapd/seed krita failed to finish in 
900 seconds.
There was no output from the command.


ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: calamares 3.3.5-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
.etc.calamares.modules.finished.conf:
 ---
 restartNowMode: user-checked
 restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
 crypttabOptions: luks,keyscript=/bin/cat
 efiMountOptions: umask=0077
.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.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.497
CurrentDesktop: LXQt
Date: Thu Apr 18 13:31:43 2024
LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417)
RelatedPackageVersions:
 calamares-settings-ubuntu-common 1:24.04.31
 calamares-settings-lubuntu   1:24.04.31
 xfsprogs 6.6.0-1ubuntu2
 btrfs-progs  6.6.3-1.1build2
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug noble

** Description changed:

- add more later
+ full install to sony vaio thingy
+ - sony vaio ultrabook svp11216cgb (i5-9400u, 4gb, intel haswell-ULT)
+ 
+ testcase: testcase: full, encryption, EFI, internet, swap, updates
+ 
+ no ethernet, so limited to wifi (300n so should be that bad, but still
+ aussie nbn so not fast)
+ 
+ ---
+ 2024-04-18 - 13:28:34 [1]: void 
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
+ 2024-04-18 - 13:28:34 [1]: ERROR: Installation failed: "External command 
failed to finish." 
+ 2024-04-18 - 13:28:34 [6]: .. - message: "External command failed to 
finish." 
+ 2024-04-18 - 13:28:34 [6]: .. - details: Command snap-seed-glue --seed 
/tmp/calamares-root-8p789tsd/var/lib/snapd/seed krita failed to finish in 
900 seconds.
+ There was no output from the command.
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: calamares 3.3.5-0ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  .etc.calamares.modules.finished.conf:
-  ---
-  restartNowMode: user-checked
-  restartNowCommand: "systemctl -i reboot"
+  ---
+  restartNowMode: user-checked
+  restartNowCommand: "systemctl -i reboot"
  .etc.calamares.modules.fstab.conf:
-  crypttabOptions: luks,keyscript=/bin/cat
-  efiMountOptions: umask=0077
+  crypttabOptions: luks,keyscript=/bin/cat
+  efiMountOptions: umask=0077
  .etc.calamares.modules.shellprocess_logs.conf:
-  ---
-  dontChroot: true
-  timeout: 30
-  script:
-  - calamares-logs-helper ${ROOT}
+  ---
+  dontChroot: true
+  timeout: 30
+  script:
+  - calamares-logs-helper ${ROOT}
  .etc.calamares.modules.unpackfs.conf:
-  ---
-  unpack:
-  -   source: "/cdrom/casper/filesystem.squashfs"
-  sourcefs: "squashfs"
-  destination: ""
+  ---
+  unpack:
+  -   source: "/cdrom/casper/filesystem.squashfs"
+  sourcefs: "squashfs"
+  destination: ""
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.497
  CurrentDesktop: LXQt
  Date: Thu Apr 18 13:31:43 2024
  LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417)
  RelatedPackageVersions:
-  calamares-settings-ubuntu-common 1:24.04.31
-  calamares-settings-lubuntu   1:24.04.31
-  xfsprogs 6.6.0-1ubuntu2
-  btrfs-progs  6.6.3-1.1build2
+  calamares-settings-ubuntu-common 1:24.04.31
+  calamares-settings-lubuntu   1:24.04.31
+  xfsprogs 6.6.0-1ubuntu2
+  btrfs-progs  6.6.3-1.1build2
  SourcePackage: calamares
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- full install fail
+ lubuntu noble - snap-seed-glue --seed ..calamares..snapd/seed krita  -- 
failed to finish in 900 seconds

-- 
You received this bug 

[Bug 2060429] Re: lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30 seconds.

2024-04-17 Thread Chris Guiver
This bug is LOW PRIORITY in my view...

- not many people will use the INSTALL USING EXISTING PARTITION 
(non-destructive install)
- the error occurs which stops the installer, but most of what is required was 
already done, so system has booted for me each time I've encountered this error 
(even if some metadata will be invalid; system has been usable).

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

Title:
  lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30
  seconds.

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


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

[Bug 2060960] Re: lubuntu noble beta RC says 23.10 (not 24.04)

2024-04-17 Thread Chris Guiver
Possibly obvious, but this appears on installed systems too, as I booted
up a recent install on dell optiplex 780 to get details for Aaron
yesterday & the 23.10 plymouth was there at boot/shutdown.

(d780 another box that uses text plymouth instead of graphic)

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

Title:
  lubuntu noble beta RC says 23.10 (not 24.04)

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


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

[Bug 2060429] Re: lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30 seconds.

2024-04-16 Thread Chris Guiver
As requested by Aaron (matrix) I ran a command on dc7700 & reported
results... also booted & ran it on d780 (which I'm using now) and
results are rather slow.

guiverc@d780-noble:~$ time sudo update-initramfs -c -k all
update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic
update-initramfs: Generating /boot/initrd.img-5.11.0-27-generic
update-initramfs: Generating /boot/initrd.img-5.11.0-44-generic
update-initramfs: Generating /boot/initrd.img-5.13.0-28-generic
update-initramfs: Generating /boot/initrd.img-5.13.0-30-generic
update-initramfs: Generating /boot/initrd.img-5.15.0-41-generic
update-initramfs: Generating /boot/initrd.img-5.15.0-46-generic
update-initramfs: Generating /boot/initrd.img-5.4.0-72-generic
W: zstd compression (CONFIG_RD_ZSTD) not supported by kernel, using gzip
update-initramfs: Generating /boot/initrd.img-5.8.0-41-generic
W: zstd compression (CONFIG_RD_ZSTD) not supported by kernel, using gzip
update-initramfs: Generating /boot/initrd.img-5.8.0-50-generic
W: zstd compression (CONFIG_RD_ZSTD) not supported by kernel, using gzip
update-initramfs: Generating /boot/initrd.img-5.8.0-61-generic
W: zstd compression (CONFIG_RD_ZSTD) not supported by kernel, using gzip
update-initramfs: Generating /boot/initrd.img-5.8.0-64-generic
W: zstd compression (CONFIG_RD_ZSTD) not supported by kernel, using gzip
update-initramfs: Generating /boot/initrd.img-6.2.0-18-generic
update-initramfs: Generating /boot/initrd.img-6.2.0-19-generic
update-initramfs: Generating /boot/initrd.img-6.2.0-26-generic
update-initramfs: Generating /boot/initrd.img-6.2.0-33-generic
update-initramfs: Generating /boot/initrd.img-6.2.0-39-generic
update-initramfs: Generating /boot/initrd.img-6.5.0-9-generic
update-initramfs: Generating /boot/initrd.img-6.8.0-22-generic

real7m6.659s
user0m0.007s
sys 0m0.006s

Even though I initially filed this bug report on dc7700; the testcase is
listed as an "INSTALL USING EXISTING PARTITION" which is a no-format
install; meaning some old stuff can be found.. thus probably this
issue..

The copy/paste of command is from a very recent install of noble on this
box.

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

Title:
  lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30
  seconds.

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


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

[Bug 2060429] Re: lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30 seconds.

2024-04-16 Thread Chris Guiver
repeated install (using existing partition) to 
- dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)

again this issue

The install abends (abnormal end) with error & thus doesn't
continue/complete install...

/var/log/installer/mediainfo OR all contents in /var/log/installer
reflect a prior install (many ago).. but this install type is successful
..  after all it's a non-destructive install (no-format) so much data
survives from pre-install  (date/time stamps of system directories match
new install though, as most system directories get wiped)

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

Title:
  lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30
  seconds.

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


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

[Bug 2061698] Re: Editing image, selecting a region and it crashed GIMP_2_10_36

2024-04-15 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 2061698

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.

( No release, package details were provided, the developers the provided
paste was for are upstream developers )

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

Title:
  Editing image, selecting a region and it crashed GIMP_2_10_36

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


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

[Bug 2061711] Re: lubuntu noble - full (inc. 3rd party) install is kinda slow

2024-04-15 Thread Chris Guiver
Of no importance.. but the 10 mins nothing will likely be

2024-04-16 - 12:32:43 [6]: .. Running ("/bin/sh", "-c", "snap-seed-glue 
--seed /tmp/calamares-root-hazyaxmi/var/lib/snapd/seed krita") 
2024-04-16 - 12:45:09 [6]: .. Running ("/bin/sh", "-c", "snap-seed-glue 
--seed /tmp/calamares-root-hazyaxmi/var/lib/snapd/seed thunderbird") 

after krita I noticed (& mentioned)  a kf5 snap.. but that detail would
have come from my viewing `iotop` and the `snap download` command that
showed there.

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

Title:
  lubuntu noble - full (inc. 3rd party) install is kinda slow

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


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

[Bug 2061711] Re: lubuntu noble - full (inc. 3rd party) install is kinda slow

2024-04-15 Thread Chris Guiver
** Description changed:

  This is NOT a bug that can be fixed with code.
  
  At most a fix maybe a line in the release notes, that selecting all 3rd
  party software for inclusion can be SLOW IF you're using 3rd-world, some
  aussie NBN or other older/slower internet connections (or just
  infrastructure at canonical end anyway).
  
  This report has been filed ONLY for timing purposes; so I can look, and
  have record of how long install actually took (with calamares
  running)...
  
  A watched kettle always appears to take longer to boil... I was sitting
  watching this install & for a long time is stayed at 90% with slideshow
  repeating... I switched to show all messages and it didn't scroll up for
  maybe 10 mins there either..
  
  I actually CTRL+ALT+T and opened a terminal, made it full screen on this
  boxes other display & `sudo apt install iotop` and let that run... From
  there I could see downloads taking place (thru write) & eventually
- notice `snap download` progress to next page (krita, kf5 etc)... but the
- installer window remained at 90%.. then eventually 92%...  |
+ notice `snap download` progress to next package (krita, kf5 etc)... but
+ the installer window remained at 90%..  eventually 92%...  |
  
  Many users may assume the installer is 'looping' or dead...
  
  2024-04-16 - 02:17:35   (start of calamares)
  2024-04-16 - 12:17:43   (calamares switched to local time I assume)
  2024-04-16 - 12:48:06   (end calamares)
  
  So ~thirty minutes to install, I didn't let it sit at any dialog.. just
  selected items & continued...
  
  This box may not be quick... but I believe issue is mostly internet
  speed & what is required to be downloaded.. something we can't do much
  about it..
  
  Is a release note worth including??
  
  Could a end-user think the install has failed is looping, when in fact
  it isn't
  
  I don't see how we can change anything, as even viewing the messages
  calamares provides I didn't see progress for near 10 mins...   thus why
  I opened terminal & starting watching progress via `iotop`
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: calamares 3.3.5-0ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  .etc.calamares.modules.after_bootloader_context.conf:
   ---
   dontChroot: false
   timeout: 120
   firmwareType:
   "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .etc.calamares.modules.fstab.conf:
   crypttabOptions: luks,keyscript=/bin/cat
   efiMountOptions: umask=0077
  .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.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.496
  CurrentDesktop: LXQt
  Date: Tue Apr 16 12:48:16 2024
  LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240415)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:24.04.28
   calamares-settings-lubuntu   1:24.04.28
   xfsprogs 6.6.0-1ubuntu2
   btrfs-progs  6.6.3-1.1build2
  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/2061711

Title:
  lubuntu noble - full (inc. 3rd party) install is kinda slow

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


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

[Bug 2061711] Re: lubuntu noble - full (inc. 3rd party) install is kinda slow

2024-04-15 Thread Chris Guiver
** Description changed:

  This is NOT a bug that can be fixed with code.
  
  At most a fix maybe a line in the release notes, that selecting all 3rd
  party software for inclusion can be SLOW IF you're using 3rd-world, some
  aussie NBN or other older/slower internet connections (or just
  infrastructure at canonical end anyway).
  
  This report has been filed ONLY for timing purposes; so I can look, and
  have record of how long install actually took (with calamares
  running)...
  
  A watched kettle always appears to take longer to boil... I was sitting
  watching this install & for a long time is stayed at 90% with slideshow
  repeating... I switched to show all messages and it didn't scroll up for
  maybe 10 mins there either..
  
  I actually CTRL+ALT+T and opened a terminal, made it full screen on this
  boxes other display & `sudo apt install iotop` and let that run... From
  there I could see downloads taking place (thru write) & eventually
  notice `snap download` progress to next page (krita, kf5 etc)... but the
  installer window remained at 90%.. then eventually 92%...  |
  
  Many users may assume the installer is 'looping' or dead...
  
+ 2024-04-16 - 02:17:35   (start of calamares)
+ 2024-04-16 - 12:17:43   (calamares switched to local time I assume)
+ 2024-04-16 - 12:48:06   (end calamares)
+ 
+ So ~thirty minutes to install, I didn't let it sit at any dialog.. just
+ selected items & continued...
+ 
+ This box may not be quick... but I believe issue is mostly internet
+ speed & what is required to be downloaded.. something we can't do much
+ about it..
+ 
+ Is a release note worth including??
+ 
+ Could a end-user think the install has failed is looping, when in fact
+ it isn't
+ 
+ I don't see how we can change anything, as even viewing the messages
+ calamares provides I didn't see progress for near 10 mins...   thus why
+ I opened terminal & starting watching progress via `iotop`
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: calamares 3.3.5-0ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  .etc.calamares.modules.after_bootloader_context.conf:
-  ---
-  dontChroot: false
-  timeout: 120
-  firmwareType:
-  "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
+  ---
+  dontChroot: false
+  timeout: 120
+  firmwareType:
+  "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
  .etc.calamares.modules.finished.conf:
-  ---
-  restartNowMode: user-checked
-  restartNowCommand: "systemctl -i reboot"
+  ---
+  restartNowMode: user-checked
+  restartNowCommand: "systemctl -i reboot"
  .etc.calamares.modules.fstab.conf:
-  crypttabOptions: luks,keyscript=/bin/cat
-  efiMountOptions: umask=0077
+  crypttabOptions: luks,keyscript=/bin/cat
+  efiMountOptions: umask=0077
  .etc.calamares.modules.shellprocess_logs.conf:
-  ---
-  dontChroot: true
-  timeout: 30
-  script:
-  - calamares-logs-helper ${ROOT}
+  ---
+  dontChroot: true
+  timeout: 30
+  script:
+  - calamares-logs-helper ${ROOT}
  .etc.calamares.modules.unpackfs.conf:
-  ---
-  unpack:
-  -   source: "/cdrom/casper/filesystem.squashfs"
-  sourcefs: "squashfs"
-  destination: ""
+  ---
+  unpack:
+  -   source: "/cdrom/casper/filesystem.squashfs"
+  sourcefs: "squashfs"
+  destination: ""
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.496
  CurrentDesktop: LXQt
  Date: Tue Apr 16 12:48:16 2024
  LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240415)
  RelatedPackageVersions:
-  calamares-settings-ubuntu-common 1:24.04.28
-  calamares-settings-lubuntu   1:24.04.28
-  xfsprogs 6.6.0-1ubuntu2
-  btrfs-progs  6.6.3-1.1build2
+  calamares-settings-ubuntu-common 1:24.04.28
+  calamares-settings-lubuntu   1:24.04.28
+  xfsprogs 6.6.0-1ubuntu2
+  btrfs-progs  6.6.3-1.1build2
  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/2061711

Title:
  lubuntu noble - full (inc. 3rd party) install is kinda slow

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


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

[Bug 2061711] [NEW] lubuntu noble - full (inc. 3rd party) install is kinda slow

2024-04-15 Thread Chris Guiver
Public bug reported:

This is NOT a bug that can be fixed with code.

At most a fix maybe a line in the release notes, that selecting all 3rd
party software for inclusion can be SLOW IF you're using 3rd-world, some
aussie NBN or other older/slower internet connections (or just
infrastructure at canonical end anyway).

This report has been filed ONLY for timing purposes; so I can look, and
have record of how long install actually took (with calamares
running)...

A watched kettle always appears to take longer to boil... I was sitting
watching this install & for a long time is stayed at 90% with slideshow
repeating... I switched to show all messages and it didn't scroll up for
maybe 10 mins there either..

I actually CTRL+ALT+T and opened a terminal, made it full screen on this
boxes other display & `sudo apt install iotop` and let that run... From
there I could see downloads taking place (thru write) & eventually
notice `snap download` progress to next page (krita, kf5 etc)... but the
installer window remained at 90%.. then eventually 92%...  |

Many users may assume the installer is 'looping' or dead...

2024-04-16 - 02:17:35   (start of calamares)
2024-04-16 - 12:17:43   (calamares switched to local time I assume)
2024-04-16 - 12:48:06   (end calamares)

So ~thirty minutes to install, I didn't let it sit at any dialog.. just
selected items & continued...

This box may not be quick... but I believe issue is mostly internet
speed & what is required to be downloaded.. something we can't do much
about it..

Is a release note worth including??

Could a end-user think the install has failed is looping, when in fact
it isn't

I don't see how we can change anything, as even viewing the messages
calamares provides I didn't see progress for near 10 mins...   thus why
I opened terminal & starting watching progress via `iotop`

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: calamares 3.3.5-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
.etc.calamares.modules.after_bootloader_context.conf:
 ---
 dontChroot: false
 timeout: 120
 firmwareType:
 "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
.etc.calamares.modules.finished.conf:
 ---
 restartNowMode: user-checked
 restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
 crypttabOptions: luks,keyscript=/bin/cat
 efiMountOptions: umask=0077
.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.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.496
CurrentDesktop: LXQt
Date: Tue Apr 16 12:48:16 2024
LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240415)
RelatedPackageVersions:
 calamares-settings-ubuntu-common 1:24.04.28
 calamares-settings-lubuntu   1:24.04.28
 xfsprogs 6.6.0-1ubuntu2
 btrfs-progs  6.6.3-1.1build2
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug iso-testing noble

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

Title:
  lubuntu noble - full (inc. 3rd party) install is kinda slow

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


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

[Bug 2056578] Re: Tor Browser - keyboard not functioning

2024-04-15 Thread Chris Guiver
I'll add another affirmation that what Asciiwolf reports in comment #10
is working for me too on this (my primary) install where I've not had
keyboard working for some time (see comment #4; late February 2024)

Add line & restart apparmor, and start torbrowser & I can use it for the
first time in ages.

Thank you Asciiwolf - appreciate the solution.

I wonder if the package this bug report is filed against is incorrect;
but sorry I don't know.

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

Title:
  Tor Browser - keyboard not functioning

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/2056578/+subscriptions


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

[Bug 2061327] Re: 24.04 beta hangs at desktop

2024-04-15 Thread Chris Guiver
duplicate filing of
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2061326

** Changed in: mesa (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/2061327

Title:
  24.04 beta hangs at desktop

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


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

[Bug 2060960] [NEW] lubuntu noble beta RC says 23.10 (not 24.04)

2024-04-11 Thread Chris Guiver
Public bug reported:

On this box (hp 8200) the text plymouth is used... and this it reports
as Lubuntu 23.10 during boot.

- hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)

** expected result

On booting a Lubuntu noble beta (24.04) I expect it to say 24.04

** actual result

It reports itself as Lubuntu 23.10 with some dots during boot

---

I believe the issue is

lubuntu@lubuntu:/usr/share/plymouth/themes/lubuntu-text$ cat 
lubuntu-text.plymouth
[Plymouth Theme]
Name=Lubuntu Text
Description=Text mode theme based on kubuntu-logo theme
ModuleName=ubuntu-text

[ubuntu-text]
title=Lubuntu 23.10
black=0x0078C2
white=0xff
brown=0x009DFD
blue=0x00182C
lubuntu@lubuntu:/usr/share/plymouth/themes/lubuntu-text$ dpkg -S 
/usr/share/plymouth/themes/lubuntu-text/lubuntu-text.plymouth
plymouth-theme-lubuntu-text: 
/usr/share/plymouth/themes/lubuntu-text/lubuntu-text.plymouth

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: plymouth-theme-lubuntu-text 24.04.4
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.496
CurrentDesktop: LXQt
Date: Thu Apr 11 12:03:57 2024
LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410)
PackageArchitecture: all
SourcePackage: lubuntu-artwork
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug noble

** Description changed:

  On this box (hp 8200) the text plymouth is used... and this it reports
  as Lubuntu 23.10 during boot.
+ 
+ - hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
  
  ** expected result
  
  On booting a Lubuntu noble beta (24.04) I expect it to say 24.04
  
  ** actual result
  
  It reports itself as Lubuntu 23.10 with some dots during boot
  
  ---
  
  I believe the issue is
  
- lubuntu@lubuntu:/usr/share/plymouth/themes/lubuntu-text$ cat 
lubuntu-text.plymouth 
+ lubuntu@lubuntu:/usr/share/plymouth/themes/lubuntu-text$ cat 
lubuntu-text.plymouth
  [Plymouth Theme]
  Name=Lubuntu Text
  Description=Text mode theme based on kubuntu-logo theme
  ModuleName=ubuntu-text
  
  [ubuntu-text]
  title=Lubuntu 23.10
  black=0x0078C2
  white=0xff
  brown=0x009DFD
  blue=0x00182C
- lubuntu@lubuntu:/usr/share/plymouth/themes/lubuntu-text$ dpkg -S 
/usr/share/plymouth/themes/lubuntu-text/lubuntu-text.plymouth 
+ lubuntu@lubuntu:/usr/share/plymouth/themes/lubuntu-text$ dpkg -S 
/usr/share/plymouth/themes/lubuntu-text/lubuntu-text.plymouth
  plymouth-theme-lubuntu-text: 
/usr/share/plymouth/themes/lubuntu-text/lubuntu-text.plymouth
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: plymouth-theme-lubuntu-text 24.04.4
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.496
  CurrentDesktop: LXQt
  Date: Thu Apr 11 12:03:57 2024
  LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410)
  PackageArchitecture: all
  SourcePackage: lubuntu-artwork
  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/2060960

Title:
  lubuntu noble beta RC says 23.10 (not 24.04)

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


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

[Bug 2060624] Re: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice

2024-04-11 Thread Chris Guiver
I've NOT encountered this issue with a install.alongside
(calamares/lubuntu) or the ubuntu-desktop-installer equivalent
(auto(resize) testcase)... as both installs (prior + new) appear in GRUB
on second install when that is run.   This is where it matters most
anyway, and it works perfectly.

I've only encountered this on manual.partitioning (something-else
equivalent) and manually selecting a pre-existing partition for re-use
(ubuntu-desktop-install now marks that as with format compulsory)...

This will impact very few users.. and can easily be covered by a RELEASE
NOTES message if required anyway, as very few users will be impacted by
it (most will have no issue dealing with the PROBER edit)..

--

Alas the Xubuntu install no longer exists; that install being
overwritten by subsequent QA test installs.   I'd have to re-create the
issue, which won't be tonight...

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

Title:
  lubuntu/xubuntu reinstall (& install) on dual boot system, grub does
  appear & offer OS choice

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


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

[Bug 2060624] Re: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice

2024-04-10 Thread Chris Guiver
The Xubuntu install was an install into one partition (SDA2) where two
partitions exist both with OSes (SDA1 & SDA2).

The resulting Xubuntu install booted without grub appearing on boot, and
no way for a user to boot into prior SDA1 install of Lubuntu noble.

Attempt as in original post of `sudo update-grub` reports

Warning: os-prober will not be executed to detect other bootable
partitions.

thus my prior 24.04 system is not offered as boot option.


I've NOT encountered this issue with an auto(resize)/install-alongside install, 
ONLY with something-else/manual-partitioning type of installs.. so its not all 
installs.

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

Title:
  lubuntu/xubuntu reinstall (& install) on dual boot system, grub does
  appear & offer OS choice

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


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

[Bug 2060624] Re: lubuntu/xubuntu reinstall on dual boot system, grub does appear & offer OS choice

2024-04-10 Thread Chris Guiver
The Xubuntu install was an install into one partition (SDA2) where two
partitions exist both with OSes (SDA1 & SDA2).

The resulting Xubuntu install booted without grub appearing on boot, and
no way for a user to boot into prior SDA1 install of Lubuntu noble.

Attempt as in original post of `sudo update-grub` reports

Warning: os-prober will not be executed to detect other bootable
partitions.

thus my prior 24.04 system is not offered as boot option.

** Summary changed:

- lubuntu reinstall on dual boot system, grub does appear & offer OS choice
+ lubuntu/xubuntu reinstall on dual boot system, grub does appear & offer OS 
choice

** Summary changed:

- lubuntu/xubuntu reinstall on dual boot system, grub does appear & offer OS 
choice
+ lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & 
offer OS choice

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

Title:
  lubuntu/xubuntu reinstall (& install) on dual boot system, grub does
  appear & offer OS choice

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


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

[Bug 2060755] Re: grub fails when trying to install ubuntu 2020.04

2024-04-09 Thread Chris Guiver
Thank you for taking the time to report this issue and helping to make
Ubuntu better.

Examining the information you have given us, this does not appear to be
a bug report so we are closing it and converting it to a question in the
support tracker.

We understand the difficulties you are facing, but it is better to raise
problems you are having in the support tracker at
https://answers.launchpad.net/ubuntu if you are uncertain if they are
bugs.

If you would prefer live chat support, you can find an IRC support
channel for your flavor of Ubuntu here:
https://wiki.ubuntu.com/IRC/ChannelList.

You can also find help with your problem in the support forum of your
local Ubuntu community http://loco.ubuntu.com/ or asking at
https://askubuntu.com or https://ubuntuforums.org. For help on reporting
bugs, see https://help.ubuntu.com/community/ReportingBugs.

(FYI:  PPAs are Personal Package Archives and not supported by the
Ubuntu project, but by the PPA owner. Bugs/requests about PPAs should
likewise be filed with the PPA owner).

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

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/grub-installer/+question/809140

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

Title:
  grub fails when trying to install ubuntu 2020.04

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


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

[Bug 2060429] Re: lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30 seconds.

2024-04-09 Thread Chris Guiver
Just experienced this again..

Install to 
- dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)

this is a newer machine (2008) with faster cpu... alas still 'slow' by
todays standards...

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

Title:
  lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30
  seconds.

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


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

[Bug 2060624] Re: lubuntu reinstall on dual boot system, grub does appear & offer OS choice

2024-04-09 Thread Chris Guiver
I vaguely recall an indirect discussion with AndreaRighi (or someone)
who mentioned a (possible?) change coming thru for noble.. I'm wondering
if this is my discovery of what was mentioned..  alas I can't recall the
'comment' this reminds me of

My testing today can be read here -
https://iso.qa.ubuntu.com/qatracker/milestones/450/builds/299105/testcases/1701/results/


Either way my install is perfect, except the dual-booting option offered by 
GRUB got lost.. This is behavior I get on Debian, so I know how to fix it, just 
don't expect it with a Ubuntu re-install.

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

Title:
  lubuntu reinstall on dual boot system, grub does appear & offer OS
  choice

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


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

[Bug 2060624] [NEW] lubuntu reinstall on dual boot system, grub does appear & offer OS choice

2024-04-09 Thread Chris Guiver
Public bug reported:

Warning: os-prober will not be executed to detect other bootable partitions.


Lubuntu noble install to
- hp dc7700 (c2d-e6320, 8gb, amd/ati rv610/radeon hd2400 pro/xt)

System had two Lubuntu noble installs on box; original full disk install (sda1) 
+ install alongside (sda2)
This box is legacy (BIOS) or pre-uEFI (2005 HP Compaq) so no ESP was created at 
install time

guiverc@dc7700-3:~$   blkid
/dev/sda2: LABEL="lubuntu_2404" UUID="4b96ae36-ff60-46ff-888d-bab52f0664fc" 
BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="b22c54df-02"
/dev/sda1: LABEL="lubuntu_2404" UUID="2466-48e0-47e3-af47-4cd692dcdbd6" 
BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="b22c54df-01"

** expected result

On reboot post-install (Lubuntu so calamares install) I grub did NOT
appear, so I could boot into the untouched install & checked it worked
(grub offered me two options correctly prior to install).

** actual result

No grub menu appeared, so no dual boot option was offered??

No problem, I'll just `update-grub` and that should fix it won't it?

guiverc@dc7700-3:~$ sudo update-grub
[sudo] password for guiverc:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/lubuntu-grub-theme.cfg'
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/lubuntu-grub-theme/theme.txt
Found linux image: /boot/vmlinuz-6.8.0-22-generic
Found initrd image: /boot/initrd.img-6.8.0-22-generic
Found memtest86+x64 image: /boot/memtest86+x64.bin
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done

The issue is
Warning: os-prober will not be executed to detect other bootable partitions.

Prior releases of Ubuntu haven't done this (new grub 2.06 change) with a
patch (ubuntu-os-prober-auto.patch) carried by Ubuntu that reverses this
upstream change..

If this is new behavior (for noble) we (Lubuntu at least) just need to
document it, as its a change to mantic, lunar & prior releases (inc.
kinetic, jammy which were 2.06 or later, it was default prior to jammy
anyway).

Maybe I'm missing something... I'll correct/add more as I can

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: grub2-common 2.12-1ubuntu7
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: LXQt
Date: Tue Apr  9 16:21:14 2024
InstallationDate: Installed on 2024-04-09 (0 days ago)
InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240408)
SourcePackage: grub2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug noble

** Description changed:

  Warning: os-prober will not be executed to detect other bootable partitions.
  
  
- Lubuntu noble install.
+ Lubuntu noble install to
+ - hp dc7700 (c2d-e6320, 8gb, amd/ati rv610/radeon hd2400 pro/xt)
  
  System had two Lubuntu noble installs on box; original full disk install 
(sda1) + install alongside (sda2)
  This box is legacy (BIOS) or pre-uEFI (2005 HP Compaq) so no ESP was created 
at install time
  
  guiverc@dc7700-3:~$   blkid
  /dev/sda2: LABEL="lubuntu_2404" UUID="4b96ae36-ff60-46ff-888d-bab52f0664fc" 
BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="b22c54df-02"
  /dev/sda1: LABEL="lubuntu_2404" UUID="2466-48e0-47e3-af47-4cd692dcdbd6" 
BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="b22c54df-01"
  
  ** expected result
  
  On reboot post-install (Lubuntu so calamares install) I grub did NOT
  appear, so I could boot into the untouched install & checked it worked
  (grub offered me two options correctly prior to install).
  
  ** actual result
  
  No grub menu appeared, so no dual boot option was offered??
  
  No problem, I'll just `update-grub` and that should fix it won't it?
  
- 
  guiverc@dc7700-3:~$ sudo update-grub
- [sudo] password for guiverc: 
+ [sudo] password for guiverc:
  Sourcing file `/etc/default/grub'
  Sourcing file `/etc/default/grub.d/lubuntu-grub-theme.cfg'
  Generating grub configuration file ...
  Found theme: /usr/share/grub/themes/lubuntu-grub-theme/theme.txt
  Found linux image: /boot/vmlinuz-6.8.0-22-generic
  Found initrd image: /boot/initrd.img-6.8.0-22-generic
  Found memtest86+x64 image: /boot/memtest86+x64.bin
  Warning: os-prober will not be executed to detect other bootable partitions.
  Systems on them will not be added to the GRUB boot configuration.
  Check GRUB_DISABLE_OS_PROBER documentation entry.
  Adding boot menu entry for UEFI Firmware Settings ...
  done
  
  The issue is
  Warning: os-prober will not be executed to detect other bootable partitions.
  
  Prior releases of Ubuntu haven't done this (new grub 2.06 change) with a
- patch carried by Ubuntu that reverses this upstream 

[Bug 2060614] Re: lubuntu lxqt - space between touching monitors

2024-04-08 Thread Chris Guiver
*** This bug is a duplicate of bug 1882411 ***
https://bugs.launchpad.net/bugs/1882411


** Attachment added: "screen.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/2060614/+attachment/5762421/+files/screen.jpg

** This bug has been marked a duplicate of bug 1882411
   lubuntu monitor settings touching screens with gap between

** Description changed:

  This really is a re-file of
  https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1882411
  
- I've blamed OPENBOX here, as I don't experience this issue when I switch
- to to xfwm4
+ I've blamed OPENBOX here, quick play by switching to xfwm4 though... and
+ I could replicate issue with xfwm4 so my blaming openbox is incorrect..
+ Now marked duplicate.
  
- Lubuntu noble was only re-installed on this box today (re-install of an 
install earlier today)..
- Install went well, at least until I explored monitor position & adjusted to 
fix minor issue
+ Lubuntu noble was only re-installed on this box today (re-install of an
+ install earlier today)..  Install went well, at least until I explored
+ monitor position & adjusted to fix minor issue
  
  NOTE my resolution for monitors is NOT identical; which maybe significant in 
experiencing this issue!
  This is NOT a new issue either.
  
  ** expected result
  
  I adjust monitor position so my monitors correctly TOUCH instead of
  overlap (overlapping was default)  and click apply.
  
  The attached screen.jpg shows HOW I aligned my monitors..
  
  ** actual result
  
  There is a GAP between the monitors; my windows can disappear between
  them, and there is a delay when I move mouse-pointer between my
  'touching' monitors (pointer is in the gap).
  
  Note the left side of the clementine music player window cannot be seen.
  If I drag it a little left, I can have ~2cm of the window appear on both
  displays however it's useless as almost none of the window is actionable
  or readable.
  
- 
- This maybe a wrong filing, and is only a duplicate of aforementioned bug 
(1882411) report.
+ This maybe a wrong filing, and is only a duplicate of aforementioned bug
+ (1882411) report.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: openbox 3.6.1-12build4
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Tue Apr  9 15:22:24 2024
  InstallationDate: Installed on 2024-04-09 (0 days ago)
  InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240408)
  SourcePackage: openbox
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  This really is a re-file of
  https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1882411
  
  I've blamed OPENBOX here, quick play by switching to xfwm4 though... and
  I could replicate issue with xfwm4 so my blaming openbox is incorrect..
  Now marked duplicate.
  
  Lubuntu noble was only re-installed on this box today (re-install of an
  install earlier today)..  Install went well, at least until I explored
  monitor position & adjusted to fix minor issue
  
- NOTE my resolution for monitors is NOT identical; which maybe significant in 
experiencing this issue!
- This is NOT a new issue either.
+ NOTE my resolution for monitors is NOT identical; which maybe
+ significant in experiencing this issue!  This is NOT a new issue either.
  
  ** expected result
  
  I adjust monitor position so my monitors correctly TOUCH instead of
  overlap (overlapping was default)  and click apply.
  
  The attached screen.jpg shows HOW I aligned my monitors..
  
  ** actual result
  
  There is a GAP between the monitors; my windows can disappear between
  them, and there is a delay when I move mouse-pointer between my
  'touching' monitors (pointer is in the gap).
  
  Note the left side of the clementine music player window cannot be seen.
  If I drag it a little left, I can have ~2cm of the window appear on both
  displays however it's useless as almost none of the window is actionable
  or readable.
  
  This maybe a wrong filing, and is only a duplicate of aforementioned bug
  (1882411) report.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: openbox 3.6.1-12build4
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Tue Apr  9 15:22:24 2024
  InstallationDate: Installed on 2024-04-09 (0 days ago)
  InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240408)
  SourcePackage: openbox
  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/2060614

Title:
  lubuntu lxqt - space between touching monitors

To 

[Bug 2060614] [NEW] lubuntu lxqt - space between touching monitors

2024-04-08 Thread Chris Guiver
*** This bug is a duplicate of bug 1882411 ***
https://bugs.launchpad.net/bugs/1882411

Public bug reported:

This really is a re-file of
https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1882411

I've blamed OPENBOX here, quick play by switching to xfwm4 though... and
I could replicate issue with xfwm4 so my blaming openbox is incorrect..
Now marked duplicate.

Lubuntu noble was only re-installed on this box today (re-install of an
install earlier today)..  Install went well, at least until I explored
monitor position & adjusted to fix minor issue

NOTE my resolution for monitors is NOT identical; which maybe
significant in experiencing this issue!  This is NOT a new issue either.

** expected result

I adjust monitor position so my monitors correctly TOUCH instead of
overlap (overlapping was default)  and click apply.

The attached screen.jpg shows HOW I aligned my monitors..

** actual result

There is a GAP between the monitors; my windows can disappear between
them, and there is a delay when I move mouse-pointer between my
'touching' monitors (pointer is in the gap).

Note the left side of the clementine music player window cannot be seen.
If I drag it a little left, I can have ~2cm of the window appear on both
displays however it's useless as almost none of the window is actionable
or readable.

This maybe a wrong filing, and is only a duplicate of aforementioned bug
(1882411) report.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: openbox 3.6.1-12build4
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: LXQt
Date: Tue Apr  9 15:22:24 2024
InstallationDate: Installed on 2024-04-09 (0 days ago)
InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240408)
SourcePackage: openbox
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug noble

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

Title:
  lubuntu lxqt - space between touching monitors

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


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

[Bug 2060592] Re: lubuntu noble - another timeout issue (600 secs)

2024-04-08 Thread Chris Guiver
On reboot of install, system looks good (I didn't bother checking for
the optional components given error..) but standard Lubuntu  which even
had all updates applied!! was there...

EXCEPT no /var/log/installer/ or components; expected given calamares
abended with error

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

Title:
  lubuntu noble - another timeout issue (600 secs)

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


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

[Bug 2060592] Re: lubuntu noble - another timeout issue (600 secs)

2024-04-08 Thread Chris Guiver
** Description changed:

  Lubuntu full install to
- - dc7700
+ - hp dc7700 (c2d-e6320, 8gb, amd/ati rv610/radeon hd2400 pro/xt)
  
- timeout (>600) seconds as I recall the message, and calamares fell over.
+ testcase: FULL, no-encryption, BIOS, internet, swap, updates
  
- I'll add more shortly..  but I've had a number of timeout type issues on
- this old core2duo box recently
+ snap-seed-glue --seed /tmp/calamares-root-r00b_jf2/var/lib/snapd/seed
+ krita failed to finish in 600 seconds
+ 
+ I've had a number of timeout type issues on this old core2duo box
+ recently
  
  ---
  2024-04-09 - 12:00:31 [1]: void 
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
- 2024-04-09 - 12:00:31 [1]: ERROR: Installation failed: "External command 
failed to finish." 
- 2024-04-09 - 12:00:31 [6]: .. - message: "External command failed to 
finish." 
+ 2024-04-09 - 12:00:31 [1]: ERROR: Installation failed: "External command 
failed to finish."
+ 2024-04-09 - 12:00:31 [6]: .. - message: "External command failed to 
finish."
  2024-04-09 - 12:00:31 [6]: .. - details: Command snap-seed-glue --seed 
/tmp/calamares-root-r00b_jf2/var/lib/snapd/seed krita failed to finish in 
600 seconds.
  There was no output from the command.
  ---
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: calamares 3.3.5-0ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  .etc.calamares.modules.after_bootloader_context.conf:
   ---
   dontChroot: false
   timeout: 120
   firmwareType:
   "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .etc.calamares.modules.fstab.conf:
   crypttabOptions: luks,keyscript=/bin/cat
   efiMountOptions: umask=0077
  .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.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.495build1
  CurrentDesktop: LXQt
  Date: Tue Apr  9 12:02:52 2024
  LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240408)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:24.04.23
   calamares-settings-lubuntu   1:24.04.23
   xfsprogs 6.6.0-1ubuntu2
   btrfs-progs  6.6.3-1.1build2
  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/2060592

Title:
  lubuntu noble - another timeout issue (600 secs)

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


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

[Bug 2060592] [NEW] lubuntu noble - another timeout issue (600 secs)

2024-04-08 Thread Chris Guiver
Public bug reported:

Lubuntu full install to
- hp dc7700 (c2d-e6320, 8gb, amd/ati rv610/radeon hd2400 pro/xt)

testcase: FULL, no-encryption, BIOS, internet, swap, updates

snap-seed-glue --seed /tmp/calamares-root-r00b_jf2/var/lib/snapd/seed
krita failed to finish in 600 seconds

I've had a number of timeout type issues on this old core2duo box
recently

---
2024-04-09 - 12:00:31 [1]: void 
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
2024-04-09 - 12:00:31 [1]: ERROR: Installation failed: "External command 
failed to finish."
2024-04-09 - 12:00:31 [6]: .. - message: "External command failed to 
finish."
2024-04-09 - 12:00:31 [6]: .. - details: Command snap-seed-glue --seed 
/tmp/calamares-root-r00b_jf2/var/lib/snapd/seed krita failed to finish in 
600 seconds.
There was no output from the command.
---

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: calamares 3.3.5-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
.etc.calamares.modules.after_bootloader_context.conf:
 ---
 dontChroot: false
 timeout: 120
 firmwareType:
 "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
.etc.calamares.modules.finished.conf:
 ---
 restartNowMode: user-checked
 restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
 crypttabOptions: luks,keyscript=/bin/cat
 efiMountOptions: umask=0077
.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.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.495build1
CurrentDesktop: LXQt
Date: Tue Apr  9 12:02:52 2024
LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240408)
RelatedPackageVersions:
 calamares-settings-ubuntu-common 1:24.04.23
 calamares-settings-lubuntu   1:24.04.23
 xfsprogs 6.6.0-1ubuntu2
 btrfs-progs  6.6.3-1.1build2
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug noble

** Description changed:

- Lubuntu full install to 
+ Lubuntu full install to
  - dc7700
  
  timeout (>600) seconds as I recall the message, and calamares fell over.
  
- I'll add more shortly..
+ I'll add more shortly..  but I've had a number of timeout type issues on
+ this old core2duo box recently
+ 
+ ---
+ 2024-04-09 - 12:00:31 [1]: void 
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
+ 2024-04-09 - 12:00:31 [1]: ERROR: Installation failed: "External command 
failed to finish." 
+ 2024-04-09 - 12:00:31 [6]: .. - message: "External command failed to 
finish." 
+ 2024-04-09 - 12:00:31 [6]: .. - details: Command snap-seed-glue --seed 
/tmp/calamares-root-r00b_jf2/var/lib/snapd/seed krita failed to finish in 
600 seconds.
+ There was no output from the command.
+ ---
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: calamares 3.3.5-0ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  .etc.calamares.modules.after_bootloader_context.conf:
-  ---
-  dontChroot: false
-  timeout: 120
-  firmwareType:
-  "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
+  ---
+  dontChroot: false
+  timeout: 120
+  firmwareType:
+  "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
  .etc.calamares.modules.finished.conf:
-  ---
-  restartNowMode: user-checked
-  restartNowCommand: "systemctl -i reboot"
+  ---
+  restartNowMode: user-checked
+  restartNowCommand: "systemctl -i reboot"
  .etc.calamares.modules.fstab.conf:
-  crypttabOptions: luks,keyscript=/bin/cat
-  efiMountOptions: umask=0077
+  crypttabOptions: luks,keyscript=/bin/cat
+  efiMountOptions: umask=0077
  .etc.calamares.modules.shellprocess_logs.conf:
-  ---
-  dontChroot: true
-  timeout: 30
-  script:
-  - calamares-logs-helper ${ROOT}
+  ---
+  dontChroot: true
+  timeout: 30
+  script:
+  - calamares-logs-helper ${ROOT}
  .etc.calamares.modules.unpackfs.conf:
-  ---
-  unpack:
-  -   source: "/cdrom/casper/filesystem.squashfs"
-  sourcefs: "squashfs"
-  destination: ""
+  ---
+  unpack:
+  -   source: "/cdrom/casper/filesystem.squashfs"
+  sourcefs: "squashfs"
+  destination: ""
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.495build1
  CurrentDesktop: LXQt
  Date: Tue Apr  9 12:02:52 2024
  LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240408)
  RelatedPackageVersions:
-  calamares-settings-ubuntu-common 1:24.04.23
-  calamares-settings-lubuntu   1:24.04.23
-  

[Bug 2060429] Re: lubuntu noble install error

2024-04-08 Thread Chris Guiver
** Description changed:

- dc7700 install, error was like
+ install to
+ - hp dc7700 (c2d-e6230, 7gb, amd/ati rv610/radeon hd2400 pro/xt)
+ testcase: install using existing partition
  
- Command /usr/libexec/fixconkeys-part2 failed to finish in 30
- seconds.
+ 
+ Command /usr/libexec/fixconkeys-part2 failed to finish in 30 seconds.
  
  (i clicked install at try/install & thus copy of error didn't survive
  gui start)
  
- this was NOT a clean install (no format) BUT a 'install using existing
- partition'..
- 
- ie. boot & select the SDA1 as / partition without format... 
+ this was NOT a clean install (no format) BUT a 'install using existing 
partition'..
+ ie. boot & select the SDA1 as / partition without format...
  install on that partition was a lubuntu noble install (with some music files 
& a few basic packages installs such as music player (audacious i think, or 
clementine)
  
  ---
  2024-04-08 - 15:43:34 [1]: void 
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
  2024-04-08 - 15:43:34 [1]: ERROR: Installation failed: "External command 
failed to finish."
  2024-04-08 - 15:43:34 [6]: .. - message: "External command failed to 
finish."
  2024-04-08 - 15:43:34 [6]: .. - details: Command 
/usr/libexec/fixconkeys-part2 failed to finish in 30 seconds.
  There was no output from the command.
  2024-04-08 - 15:43:34 [6]: void 
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
  ---
+ 
+ install reported failure..
+ 
+ On reboot I can login and everything looks okay (will be passing QA
+ test), BUT /var/log/installer/mediainfo shows 0320.1 ISO which was
+ numerous installs ago & not today's ISO  (last install failed, different
+ issue but same type of install thus why numerous installs ago)
+ 
+ viewing / shows many directories date/timestamped matching a new
+ (re-)install, however some system directories do NOT reflect a re-
+ install; ie. calamares reached an error & stopped the system booted
+ correctly, but that's no doubt because it was a functional Lubuntu noble
+ system & it's using setup possibly from prior install...
+ 
  
  ProblemType: BugDistroRelease: Ubuntu 24.04
  Package: calamares 3.3.5-0ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  .etc.calamares.modules.after_bootloader_context.conf:
   ---
   dontChroot: false
   timeout: 120
   firmwareType:
   "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .etc.calamares.modules.fstab.conf:
   crypttabOptions: luks,keyscript=/bin/cat
   efiMountOptions: umask=0077
  .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.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.495build1
  CurrentDesktop: LXQt
  Date: Mon Apr  8 15:57:10 2024
  LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.3)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:24.04.23
   calamares-settings-lubuntu   1:24.04.23
   xfsprogs 6.6.0-1ubuntu2
   btrfs-progs  6.6.3-1.1build2
  SourcePackage: calamares
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- lubuntu noble install error
+ lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30 seconds.

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

Title:
  lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30
  seconds.

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


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

[Bug 2060429] [NEW] lubuntu noble install error

2024-04-08 Thread Chris Guiver
Public bug reported:

dc7700 install, error was like

Command /usr/libexec/fixconkeys-part2 failed to finish in 30
seconds.

(i clicked install at try/install & thus copy of error didn't survive
gui start)

this was NOT a clean install (no format) BUT a 'install using existing
partition'..

ie. boot & select the SDA1 as / partition without format... 
install on that partition was a lubuntu noble install (with some music files & 
a few basic packages installs such as music player (audacious i think, or 
clementine)

---
2024-04-08 - 15:43:34 [1]: void 
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
2024-04-08 - 15:43:34 [1]: ERROR: Installation failed: "External command 
failed to finish."
2024-04-08 - 15:43:34 [6]: .. - message: "External command failed to 
finish."
2024-04-08 - 15:43:34 [6]: .. - details: Command 
/usr/libexec/fixconkeys-part2 failed to finish in 30 seconds.
There was no output from the command.
2024-04-08 - 15:43:34 [6]: void 
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
---

ProblemType: BugDistroRelease: Ubuntu 24.04
Package: calamares 3.3.5-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
.etc.calamares.modules.after_bootloader_context.conf:
 ---
 dontChroot: false
 timeout: 120
 firmwareType:
 "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
.etc.calamares.modules.finished.conf:
 ---
 restartNowMode: user-checked
 restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
 crypttabOptions: luks,keyscript=/bin/cat
 efiMountOptions: umask=0077
.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.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.495build1
CurrentDesktop: LXQt
Date: Mon Apr  8 15:57:10 2024
LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.3)
RelatedPackageVersions:
 calamares-settings-ubuntu-common 1:24.04.23
 calamares-settings-lubuntu   1:24.04.23
 xfsprogs 6.6.0-1ubuntu2
 btrfs-progs  6.6.3-1.1build2
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug noble third-party-packages

** Description changed:

- dc7700 install, will add more once I get to remind myself of error
- (i clicked install & thus copy of error didn't survive gui start)
+ dc7700 install, error was like
  
- ProblemType: Bug
- DistroRelease: Ubuntu 24.04
+ Command /usr/libexec/fixconkeys-part2 failed to finish in 30
+ seconds.
+ 
+ (i clicked install at try/install & thus copy of error didn't survive
+ gui start)
+ 
+ ---
+ 2024-04-08 - 15:43:34 [1]: void 
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
+ 2024-04-08 - 15:43:34 [1]: ERROR: Installation failed: "External command 
failed to finish." 
+ 2024-04-08 - 15:43:34 [6]: .. - message: "External command failed to 
finish." 
+ 2024-04-08 - 15:43:34 [6]: .. - details: Command 
/usr/libexec/fixconkeys-part2 failed to finish in 30 seconds.
+ There was no output from the command.
+ 2024-04-08 - 15:43:34 [6]: void 
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
+ ---
+ 
+ 
+ ProblemType: BugDistroRelease: Ubuntu 24.04
  Package: calamares 3.3.5-0ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  .etc.calamares.modules.after_bootloader_context.conf:
-  ---
-  dontChroot: false
-  timeout: 120
-  firmwareType:
-  "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
+  ---
+  dontChroot: false
+  timeout: 120
+  firmwareType:
+  "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
  .etc.calamares.modules.finished.conf:
-  ---
-  restartNowMode: user-checked
-  restartNowCommand: "systemctl -i reboot"
+  ---
+  restartNowMode: user-checked
+  restartNowCommand: "systemctl -i reboot"
  .etc.calamares.modules.fstab.conf:
-  crypttabOptions: luks,keyscript=/bin/cat
-  efiMountOptions: umask=0077
+  crypttabOptions: luks,keyscript=/bin/cat
+  efiMountOptions: umask=0077
  .etc.calamares.modules.shellprocess_logs.conf:
-  ---
-  dontChroot: true
-  timeout: 30
-  script:
-  - calamares-logs-helper ${ROOT}
+  ---
+  dontChroot: true
+  timeout: 30
+  script:
+  - calamares-logs-helper ${ROOT}
  .etc.calamares.modules.unpackfs.conf:
-  ---
-  unpack:
-  -   source: "/cdrom/casper/filesystem.squashfs"
-  sourcefs: "squashfs"
-  destination: ""
+  ---
+  unpack:
+  -   source: "/cdrom/casper/filesystem.squashfs"
+  

[Bug 2060409] Re: Some slides in the Ubuntu MATE installer are no longer relevant

2024-04-07 Thread Chris Guiver
** Tags added: noble

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

Title:
  Some slides in the Ubuntu MATE installer are no longer relevant

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


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

[Bug 2060375] Re: Error appeared when updating Snap on Ubuntu 20

2024-04-07 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 2060375

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.

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

Title:
  Error appeared when updating Snap on Ubuntu 20

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


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

[Bug 2060346] Re: lubuntu noble install - apt-get failure?? temporary web issue or what?

2024-04-06 Thread Chris Guiver
Install looks good to me..   HOWEVER

/var/log/media/installer shows Ubuntu 24.04 20240320.1 and not 20240328 which 
is listed above.. 
some directory metadata (date/time stamps) are perfect and show an install only 
mins ago... HOWEVER some show 28-March-2024 which better fit the 20.1 ISO..

thus I gather calamares aborted & didn't complete install... and the
install is making up for missing details from a prior install (given no
format was performed)..

either way I'm passing install... but it worked in this particular
instance (I've done it before I'm sure and had login & looks okay
before, but missing metadata; where it's too-old metadata I'd say here)

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

Title:
  lubuntu noble install - apt-get failure?? temporary web issue or what?

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


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

[Bug 2060346] [NEW] lubuntu noble install - apt-get failure?? temporary web issue or what?

2024-04-06 Thread Chris Guiver
Public bug reported:

I've not yet looked at what happened, calamares just reported failure.

install on dc7700; using existing partition (single sda1), prior install
was Ubuntu Desktop booted ~15 mins prior to install...   partitioning
was made by prior full-disk install

---

I tried to copy/paste what I saw from calamares; but on closure the
'pasted' details cleared before LXQt desktop was fully functional, but
following matches what I saw.

2024-04-06 - 19:25:27 [1]: void 
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
2024-04-06 - 19:25:27 [1]: ERROR: Installation failed: "External command 
failed to finish." 
2024-04-06 - 19:25:27 [6]: .. - message: "External command failed to 
finish." 
2024-04-06 - 19:25:27 [6]: .. - details: Command apt-get -y 
full-upgrade failed to finish in 300 seconds.

Even if we can do nothing about this actual problem (SUCH AS IT being a
temporary internet failure..)... maybe we should write up something on
discourse/documentation (not worth manual) on the issue.. even if its
just a retry


ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: calamares 3.3.4-0ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
.etc.calamares.modules.after_bootloader_context.conf:
 ---
 dontChroot: false
 timeout: 120
 firmwareType:
 "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
.etc.calamares.modules.finished.conf:
 ---
 restartNowMode: user-checked
 restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
 crypttabOptions: luks,keyscript=/bin/cat
 efiMountOptions: umask=0077
.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.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.494
CurrentDesktop: LXQt
Date: Sat Apr  6 19:32:23 2024
LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240328)
RelatedPackageVersions:
 calamares-settings-ubuntu-common 1:24.04.16
 calamares-settings-lubuntu   1:24.04.16
 xfsprogs 6.6.0-1ubuntu1
 btrfs-progs  6.6.3-1.1
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug noble

** Description changed:

  I've not yet looked at what happened, calamares just reported failure.
  
  install on dc7700; using existing partition (single sda1), prior install
  was Ubuntu Desktop booted ~15 mins prior to install...   partitioning
  was made by prior full-disk install
+ 
+ ---
+ 
+ I tried to copy/paste what I saw from calamares; but on closure the
+ 'pasted' details cleared before LXQt desktop was fully functional, but
+ following matches what I saw.
+ 
+ 2024-04-06 - 19:25:27 [1]: void 
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
+ 2024-04-06 - 19:25:27 [1]: ERROR: Installation failed: "External command 
failed to finish." 
+ 2024-04-06 - 19:25:27 [6]: .. - message: "External command failed to 
finish." 
+ 2024-04-06 - 19:25:27 [6]: .. - details: Command apt-get -y 
full-upgrade failed to finish in 300 seconds.
+ 
+ Even if we can do nothing about this actual problem (SUCH AS IT being a
+ temporary internet failure..)... maybe we should write up something on
+ discourse/documentation (not worth manual) on the issue.. even if its
+ just a retry
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: calamares 3.3.4-0ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  .etc.calamares.modules.after_bootloader_context.conf:
-  ---
-  dontChroot: false
-  timeout: 120
-  firmwareType:
-  "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
+  ---
+  dontChroot: false
+  timeout: 120
+  firmwareType:
+  "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
  .etc.calamares.modules.finished.conf:
-  ---
-  restartNowMode: user-checked
-  restartNowCommand: "systemctl -i reboot"
+  ---
+  restartNowMode: user-checked
+  restartNowCommand: "systemctl -i reboot"
  .etc.calamares.modules.fstab.conf:
-  crypttabOptions: luks,keyscript=/bin/cat
-  efiMountOptions: umask=0077
+  crypttabOptions: luks,keyscript=/bin/cat
+  efiMountOptions: umask=0077
  .etc.calamares.modules.shellprocess_logs.conf:
-  ---
-  dontChroot: true
-  timeout: 30
-  script:
-  - calamares-logs-helper ${ROOT}
+  ---
+  dontChroot: true
+  timeout: 30
+  script:
+  - calamares-logs-helper ${ROOT}
  .etc.calamares.modules.unpackfs.conf:
-  ---
-  unpack:
-  -   source: "/cdrom/casper/filesystem.squashfs"
-  sourcefs: "squashfs"
- 

[Bug 2060091] Re: lubuntu noble daily never starts.. black screen; Lubuntu box & Connecting..

2024-04-03 Thread Chris Guiver
As I noted in testcase comment

at terminal I killed lubuntu-installer-prompt & I had a normal LXQt
session appear...

At last resort (this issue maybe very rare; if its not transitory..) we
can document how to kill lubuntu-installer-prompt as I did on
discourse.. no need to mention in release notes even if this is done...

After this attempt, I next booted box below this one that uses same 
keyboard/screens etc & using same thumb-drive have no issues like this at 
all...  no issue with this on
- hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)


I wonder if this relates to video card??  (I'll try another box), then again 
the Connecting makes me (no doubt end-users)  think of internet?? but I could 
`ubuntu-bug` file on the box so network makes little sense to me...  ICMP echo 
requests (ping) to web are returned

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

Title:
  lubuntu noble daily never starts.. black screen; Lubuntu box &
  Connecting..

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


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

[Bug 2060091] [NEW] lubuntu noble daily never starts.. black screen; Lubuntu box & Connecting..

2024-04-03 Thread Chris Guiver
Public bug reported:

Booted Lubuntu noble daily on
- hp prodesk 400 g1 sff (i5-4570, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)

Multiple attempts made, each end in black screens, with a small window
on one display titled "Lubuntu" and in the white window below it the
word "Connecting..." and a light-dark-blue moving line that doesn't
progress..

Multiple boots; and left for >15 mins (one attempt 25+ as I fed birds)

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: lubuntu-installer-prompt 24.04.3
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.494
Date: Wed Apr  3 06:03:29 2024
LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240328)
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=linux
 XDG_RUNTIME_DIR=
SourcePackage: lubuntu-installer-prompt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug noble

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

Title:
  lubuntu noble daily never starts.. black screen; Lubuntu box &
  Connecting..

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


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

[Bug 2059872] Re: Unable to listen on port 22 if multiple Port= present in sshd configuration

2024-04-01 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 2059872

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.

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

Title:
  Unable to listen on port 22 if multiple Port= present in sshd
  configuration

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


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

[Bug 2058638] Re: User account is missing from /etc/shadow & /etc/passwd

2024-03-25 Thread Chris Guiver
Dan wrote

> (I never saw it work on UEFI)


guiverc@d7050-next:~/uwn/issues/831$   cat /var/log/installer/media-info 
Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)

I'm on my primary box now (dell optiplex 7050) which uses Secure-uEFI
boot, and this install was last made after a problem during the mantic
cycle that caused 2 of my 5 screens to go dark (be it installed system
or LIVE boots). When the live boots no longer had an issue, but it had
remained on my installed system & I was unable to work out why; I just
non-destructively re-installed the system as fix.

FYI:  This system is a single-partition install (plus ESP), being
installed using a testcase that didn't create a separate /home.  Xubuntu
used `ubiquity` when I re-installed using daily 2023-08-29, ie. fix my
issue & a QA install.

Whilst I sometimes disable secure-boot (virtualbox is easier) the
machine is still uEFI & I use it regularly there in QA too (mostly
Xubuntu, with calamares).


Personally I'd prefer the boot as 'non-ideal' as the passwd/sudo issue can be 
easily resolved & just documentation suggesting FORMAT is used.  The loss of 
this re-install feature (something I've always loved about Ubuntu, and 
regularly use) would be a large loss, esp. on a LTS release.

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

Title:
  User account is missing from /etc/shadow & /etc/passwd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-provision/+bug/2058638/+subscriptions


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

[Bug 2058638] Re: User account is missing from /etc/shadow & /etc/passwd

2024-03-22 Thread Chris Guiver
I have zsync'd a Ubuntu Desktop ISO.. and attempted the same type of
install there

- Ubuntu Desktop noble ISO

- booted ISO, (0320 or 0320.1 I'm unsure sorry; whatever was current at time I 
ran zsync)
- installer offered upgrade; so I accepted that.. closed & restarted install

- selected the same partition (partition layout created by full disk install of 
xubuntu noble week+ ago) for / WITHOUT FORMAT, clicked extra options where 
offered
- used 'guiverc' as username, and 'please' as password..

install completed & asked me to reboot... all good as with Xubuntu.

ON booting the new install... it appeared to go into OEM mode.

I was ASKED for a Username, am being asked to enter PASSWORD  

THESE ARE DETAILS I GAVE THE INSTALLER.

** my opinion of what I'm seeing

I"m not familiar with OEM installs sorry; haven't QA-installed it in
years, but this is acting like a Xubuntu type of install issue where the
Ubuntu Desktop boot has just triggered an OEM type of setup thus the
repeat of question...

Either way why have the installer ask me these questions if they're
ignored on initial boot  (if this is intentional behavior; which I very
much doubt!!)

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

Title:
  User account is missing from /etc/shadow & /etc/passwd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-provision/+bug/2058638/+subscriptions


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

[Bug 2058491] Re: (mate-appearance-properties : GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process

2024-03-20 Thread Chris Guiver
Thank you for reporting this bug to Ubuntu.

Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it anymore. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

( No apport tools were used in the creation of this bug filing, but only
18.04 is mentioned in the text description, where Ubuntu MATE 22.04 LTS
is the oldest supported release of Ubuntu MATE.  Please re-file this if
detected on Ubuntu-MATE 23.10, or Ubuntu-MATE 22.04 LTS.  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. )

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

Title:
  (mate-appearance-properties : GTK+ 2.x symbols detected. Using GTK+
  2.x and GTK+ 3 in the same process

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


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

[Bug 2056581] Re: can't install xubuntu-core

2024-03-08 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 2056581

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.

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

Title:
  can't install xubuntu-core

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2056581/+subscriptions


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

[Bug 2056578] Re: Tor Browser - keyboard not functioning

2024-03-08 Thread Chris Guiver
I'll add for FYI sake.. I've experienced this myself on my primary box
(two weeks now); Lubuntu noble using LXQt/Xorg

I tried to re-create it using what was the Lubuntu current daily (this
was a few days ago now); and the torbrowser-launcher worked perfectly in
installing torbrowser for me to test & use..  No keyboard issues either
on the live system.

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

Title:
  Tor Browser - keyboard not functioning

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/2056578/+subscriptions


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

[Bug 2055270] Re: Buy Tramadol Online At Lowest Prices

2024-02-28 Thread Chris Guiver
requested delete via
https://answers.launchpad.net/launchpad/+question/709435

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

Title:
  Buy Tramadol Online At Lowest Prices

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


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

[Bug 2055256] Re: add-apt-repository ppa:ondrej/php is not working in ubuntu noble

2024-02-28 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

This is not an issue with Ubuntu, but with the mentioned Personal
Package Archive which the maintainer provides for Ubuntu 20.04 (focal)
and Ubuntu 22.04 (jammy)

The owner of the PPA decides what releases they'll package & provide
support for, please refer
https://launchpad.net/~ondrej/+archive/ubuntu/php

** Changed in: 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/2055256

Title:
  add-apt-repository ppa:ondrej/php is not working in ubuntu noble

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


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

[Bug 1977678] Re: Crash on close

2022-06-05 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1977678

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.

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

Title:
  Crash on close

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


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

[Bug 1977676] Re: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2022-06-05 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

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

Title:
  package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1977676/+subscriptions


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

[Bug 1977683] Re: Lubuntu error has_option: command not found / no ssh-agent after updating to 22.04

2022-06-05 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Lubuntu has used sddm for all LXQt releases (ie. since Lubuntu 18.10),
and the upgrade from an release that used lightdm/LXDE is unsupported
due to breakage as was warned about in documentation, eg.

https://lubuntu.me/focal-2-released/

"Note, due to the extensive changes required for the shift in desktop
environments, the Lubuntu team does not support upgrading from 18.04 or
below to any greater release. Doing so will result in a broken system.
If you are on 18.04 or below and would like to upgrade, please do a
fresh install."

The error you are describing is a user-created issue by using
unsupported upgrade procedures that were documented as creating issues
later, and this is warned about breakage.  The fresh install would have
prevented this.

As such I've marked this bug report as "opinion".  If you believe I'm in
error, please leave a comment explaining why and the bug report can then
be returned to "New" (you may find it'll then be marked as "Won't Fix")


** Changed in: lightdm (Ubuntu)
   Status: New => Opinion

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

Title:
  Lubuntu error has_option: command not found / no ssh-agent after
  updating to 22.04

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


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

[Bug 1977461] Re: not able to upgrade from ubuntu 14 lts to 20 lts

2022-06-02 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.

You may find a support site more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

Do note however that Ubuntu 14.04 LTS reached the end of it's standard
support back in April-2019 (5 years after release) thus support options
are now limited. This also applies to Ubuntu 16.04 LTS (the release
14.04 upgrades to).

- Ubuntu 16.04 (xenial) reached end-of-standard-support on - April 29, 2021.
- Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

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

Title:
  not able to upgrade from ubuntu 14 lts to 20 lts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1977461/+subscriptions


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

[Bug 1976611] Re: There is a problem in Ubuntu 22.04 LTS

2022-06-02 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

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.

You have not filed this report against any particular package; so until
the package is determined the required `apport-collect` cannot be run.

I am not sure what your video is actually trying to show.  I've thus
marked this bug as 'incomplete', and suggest you seek support.  You can
convert this bug report into a Question which is aimed at support.

** Changed in: 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/1976611

Title:
  There is a problem in Ubuntu 22.04 LTS

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


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

[Bug 1976556] Re: [Lenovo 300e 2nd GEN] ELAN Touchpad not working

2022-06-01 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1976556

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.

** Package changed: ubuntu => linux (Ubuntu)

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

Title:
   [Lenovo 300e 2nd GEN] ELAN Touchpad not working

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


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

[Bug 1976475] Re: Installer crash when try to enable disk encryption

2022-06-01 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1976475

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.

** Package changed: ubuntu => ubiquity (Ubuntu)

** Changed in: ubiquity (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/1976475

Title:
  Installer crash when try to enable disk encryption

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


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

[Bug 1976433] Re: package chromium-browser 101.0.4951.64-0ubuntu0.18.04.1 failed to install/upgrade: el subproceso nuevo paquete chromium-browser script pre-installation devolvió el código de salida d

2022-06-01 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Unfortunately, we cannot work on this bug because your description
didn't include enough information. You may find it helpful to read "How
to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Please also ensure that you include the release and flavour of Ubuntu
that you are using.

Your title & package details match bionic/18.04 (ie. "chromium-browser |
101.0.4951.64-0ubuntu0.18.04.1  | bionic-security/universe | source,
amd64, arm64, armhf, i386") but your release is shown as focal/20.04.

Are you sure you wouldn't benefit from support?  Bug reporting is mostly
about finding & fixing problems thus preventing future users from
hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

I've marked this bug report 'incomplete'; if you believe I'm in error,
please leave a comment saying why (or details as to your problem) and
the status can be returned to 'new'

Thank you!

** Changed in: chromium-browser (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/1976433

Title:
  package chromium-browser 101.0.4951.64-0ubuntu0.18.04.1 failed to
  install/upgrade: el subproceso nuevo paquete chromium-browser script
  pre-installation devolvió el código de salida de error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1976433/+subscriptions


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

[Bug 1976473] Re: Unable to change screen brightness in ubuntu desktop

2022-06-01 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1976473

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.

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

Title:
  Unable to change screen brightness in ubuntu desktop

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


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

[Bug 1976177] Re: Ubiquity not using password provided by UI

2022-05-29 Thread Chris Guiver
The media used is not a Ubuntu ISO.

For this bug to be explored, an official Ubuntu ISO (eg. 20.04.4) would
need to be used, to rule out issues created by the unsupported (by
Ubuntu) third party ISO used in the initial filing.

I've marked this bug report invalid.  If you believe this is a ubiquity
bug, please use a Ubuntu ISO to confirm the issue occurs there, and file
another bug report using `ubuntu-bug ubiquity` if the problem occurs.
You can provide a link to this report so additional details noted here
can also be used in locating & providing a fix.

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

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

** Changed in: ubiquity (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Ubiquity not using password provided by UI

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


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

[Bug 1976177] Re: Ubiquity not using password provided by UI

2022-05-29 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1976177

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.

Please note, if this is not Ubuntu official media, the report will
likely be closed as invalid, as it should be filed with the creator of
the non-Ubuntu media.

** Changed in: ubiquity (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/1976177

Title:
  Ubiquity not using password provided by UI

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


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

[Bug 1976167] Re: lubuntu 16.04 frequent crashes

2022-05-28 Thread Chris Guiver
Thank you for reporting this bug to Ubuntu.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

FYI: Lubuntu 16.04 LTS reached EOL end of April 2019.
FYI: The package you filed against is the installer itself; so if your system 
installed - it's not involved; but that support ended April 2019.

** Changed in: ubiquity (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/1976167

Title:
  lubuntu  16.04  frequent crashes

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


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

[Bug 1975635] Re: PC Freeze on 5.13.0.40

2022-05-24 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

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.

Please note: `ubuntu-bug`, `apport` & bug reporting tools are provided
with Ubuntu by default, many require manual addition for some releases
of downstream OSes based on Ubuntu (eg. Linux Mint). You should check
with your distribution first.

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

Title:
  PC Freeze on 5.13.0.40

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


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

[Bug 1975393] Re: Calamares - unable to select option "Next" after selecting "No Swap"

2022-05-22 Thread Chris Guiver
filed as #1959 upstream
(https://github.com/calamares/calamares/issues/1959) which was marked
duplicate of #1953 (https://github.com/calamares/calamares/issues/1953)

I looked before filing, but missed it :(

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

** Changed in: calamares
   Status: New => Unknown

** Changed in: calamares
 Remote watch: Calamares Issues #1959 => Calamares Issues #1953

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

Title:
  Calamares - unable to select option "Next" after selecting "No Swap"

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


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

[Bug 1975393] Re: Calamares - unable to select option "Next" after selecting "No Swap"

2022-05-21 Thread Chris Guiver
** Bug watch added: Calamares Issues #1959
   https://github.com/calamares/calamares/issues/1959

** Also affects: calamares via
   https://github.com/calamares/calamares/issues/1959
   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/1975393

Title:
  Calamares - unable to select option "Next" after selecting "No Swap"

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


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

[Bug 1975393] Re: Calamares - unable to select option "Next" after selecting "No Swap"

2022-05-21 Thread Chris Guiver
I can confirm this issue...  (Lubuntu kinetic daily)

I worked around it via clicking Encrypt.system & entering password twice
& NEXT showed.. I could then unclick Encrypt to get what was wanted..

What Leó suggested (check/uncheck manual partitioning) is easier

- sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)

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

Title:
  Calamares - unable to select option "Next" after selecting "No Swap"

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


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

[Bug 1974479] Re: Kubuntu 22.04 Dolphin authentication dialog failed

2022-05-21 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

You've filed this bug report against `ubiquity` as an installation
problem, but have provided no specifics as to what ISO you're trying to
install etc. The `ubiquity` installer doesn't use SaMBa.  You can
convert this bug report into a question, which is aimed at support.

I've marked this bug report as 'incomplete' as it appears you'd benefit
more from support. If this is changed to a question; after additional
details have been added the bug-report can be continued or a new one
filed.  If you believe I'm in error, please leave a comment as to why
and the status can be returned to "New".  You'll need to run `apport-
collect 1974479` once on the impacted box too so specific details can be
obtained.

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

** Tags added: jammy

** Package changed: ubiquity (Ubuntu) => samba (Ubuntu)

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

Title:
  Kubuntu 22.04 Dolphin authentication dialog failed

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


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

[Bug 1895905] Re: lubuntu groovy; flashing of sddm greeter

2022-05-20 Thread Chris Guiver
Thank you for reporting this bug to Ubuntu.

Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

(I don't think I still have the box this bug report was filed on, but
the video card was not my own so I cannot retest with that card)

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

Title:
  lubuntu groovy; flashing of sddm greeter

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


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

[Bug 1922342] Re: Impish live session takes ages to boot on BIOS systems

2022-05-20 Thread Chris Guiver
> If you now apply the remedy to the stick
>  dd if=/dev/zero bs=1 count=16 of=/dev/sdb conv=notrunc seek=462
>then i expect it to be permanently booting in reasonable time.
> ..  Please confirm.

Inserted thumb-drive(2)  [Ubuntu-MATE jammy] into box and

-- start paste
guiverc@d960-ubu2:/de2900/ubuntu_mate_64$   sudo dd if=/dev/zero bs=1 count=16 
of=/dev/sdb conv=notrunc seek=462
[sudo] password for guiverc: 
16+0 records in
16+0 records out
16 bytes copied, 0.0107609 s, 1.5 kB/s
-- end paste

booted it on j3400
- motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)

on boot (noting when at grub) it had reached maybe-ubiquity in ~3 mins
using room clock (no seconds as digital).   I made an error in typing
SysRq-REO  (intended REISUB) so as no sync.. ignoring this bot.

turned box back on & booted again; again at maybe-ubiquity in ~3 mins by
room clock.  Correctly used SysRq-REISUB to restart

another boot & again ~3 mins by room clock.  SysRq-REISUO now

NOTE: I didn't wait for clock to change minute & press enter this time,
thus the extra seconds (making 2+ mins ~3 mins) is just ME not starting
hitting the timing at ~:01 secs or hitting ENTER just after minute
changes..   Either way ~3 mins is NOT TEN minutes as the slow boot takes
to reach maybe-ubiquity.

This confirms what I believe you wanted.

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

Title:
  Impish live session takes ages to boot on BIOS systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1922342/+subscriptions


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

[Bug 1974268] Re: Does this package conflict with systemd oom?

2022-05-19 Thread Chris Guiver
** Tags added: jammy

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

Title:
  Does this package conflict with systemd oom?

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