date:20221001

[Touch-packages] [Bug 1990863] Re: conversion from sshd service to socket is too bumpy

2022-10-01 Thread Steve Langasek

I don't have a complete solution to this, but I do have several points.

- debconf prompts on upgrade are not, in general, good UX.  It disrupts
the flow of the upgrade.  Sometimes it's necessary, but if all it's
doing is telling the user they *may* have a broken config after
upgrading, well, if every package for which that's true did that
upgrades would be very slow indeed.  And for users upgrading a large
number of systems, that becomes one more nuisance.  So no, I don't think
we should add a prompt on upgrade for this.  (There's also the practical
problem that if we introduced such a prompt at this point in the release
cycle, it would not realistically get translated, reducing accessibility
for our users vs communicating this in other ways that could be
localized out-of-band.)

- As Robie pointed out in comment #4, there is no guarantee that ansible 
playbooks work consistently across releases.  Regardless of whether we made 
changes that would have allowed the migration of settings in your case, if you 
had had to reinstall kinetic instead of upgrading from jammy, those changes in 
the openssh-server maintainer scripts would not have taken effect.  Your 
ansible playbook is therefore buggy wrt kinetic, and should be fixed, which is 
out of scope for Ubuntu and the bug tracker.  But the following contents in a 
file named /etc/systemd/system/ssh.socket.d/addresses.conf should set you on 
the right path:
  [Socket]
  ListenStream=
  ListenStream=$portnum

- I have long been displeased with ucf's three-way-merge support.  In
particular, when identical content exists both in the user's version and
in the new version but not in the base version, ucf will treat this as a
merge conflict.  This is awful, and specifically caused problems for
upgrades from all cloud images when the user had not modified the sshd
config at all (LP: #1990863).  I've applied a workaround for this in
openssh 1ubuntu7 (currently in the unapproved queue) that's specific to
the cloud image case and ensures clean upgrades without prompting for
users that have not modified sshd_config.  I could generalize this to
all users with modified configs, resulting in two prompts on upgrade but
a better chance of successful three-way merging.  Do you think that
would be an improvement over the status quo?

- Finally, there is some code I'm evaluating landing that would add a
systemd generator for the listenstream settings.  This would only take
effect at boot, but would make it possible for users to continue
managing their port/listenaddress settings in sshd.conf as before.
However, we would not land this in time for the kinetic release, but
would instead consider it for the next release to improve our LTS-to-LTS
compatibility.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1990863

Title:
  conversion from sshd service to socket is too bumpy

Status in openssh package in Ubuntu:
  New

Bug description:
  During upgrade from Jammy to Kinetic, I get asked what to do because
  my sshd_config has been modified. I say to do a 3-way merge. It says
  3-way merge fails. I shrug, figure I'll just restore my customizations
  with Ansible after the upgrade like I always do, and tell it to use
  the vendor version of the file. This removes my custom Port settings,
  so they are not migrated over to the ssh.socket settings like
  https://discourse.ubuntu.com/t/sshd-now-uses-socket-based-activation-
  ubuntu-22-10-and-later/30189 says they would be. I subsequently run my
  Ansible which restores the customizations and enables the ssh service,
  but now ssh.service and ssh.socket are enabled at the same time, sshd
  isn't listening on my specified ports, and everything is a mess. I've
  never used socket-based activation before and have no idea how to
  configure it so now I have to go reading man pages, Googling all over
  the place, and generally struggle to figure out what the heck is going
  wrong.

  I don't know what the right answer is here, but I really feel like
  some effort needs to be put into figuring out a smoother transition
  for people who are upgrading to Kinetic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: openssh-server 1:9.0p1-1ubuntu6
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 11:41:58 2022
  InstallationDate: Installed on 2019-08-16 (1136 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: openssh
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (1 days ago)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to :

[Touch-packages] [Bug 1833863] Re: Incorrect logic for

2022-10-01 Thread Sean Davis

** Bug watch added: gitlab.xfce.org/xfce/garcon/-/issues #32
   https://gitlab.xfce.org/xfce/garcon/-/issues/32

** Also affects: garcon via
   https://gitlab.xfce.org/xfce/garcon/-/issues/32
   Importance: Unknown
   Status: Unknown

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pyxdg in Ubuntu.
https://bugs.launchpad.net/bugs/1833863

Title:
  Incorrect logic for 

Status in Garcon:
  Unknown
Status in PyXDG:
  New
Status in garcon package in Ubuntu:
  Triaged
Status in pyxdg package in Ubuntu:
  New
Status in xubuntu-default-settings package in Ubuntu:
  Fix Released

Bug description:
  XFCE & Xubuntu use  in their menu files, which
  python-xdg currently (all current versions) does not handle correctly:

  https://gitlab.freedesktop.org/xdg/pyxdg/issues/12

  I think the fix is as simple as

  --- Menu.py.a   2019-06-23 17:44:24.992850139 +0100
  +++ Menu.py.b   2019-06-23 17:44:41.052807584 +0100
  @@ -997,7 +997,7 @@
   for menuentry in menu.MenuEntries:
   if menuentry not in tmp_e:
   menu.Entries.append(menuentry)
  -elif order[1] == "menus" or order[1] == "all":
  +if order[1] == "menus" or order[1] == "all":
   menu.Submenus.sort()
   for submenu in menu.Submenus:
   if submenu.Name not in tmp_s:

  But as it can also be trivially worked around by replacing  with , I
  wonder if this should be done in XFCE/Xubuntu?

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

2022-10-01 Thread Peter Klausner

For 22.04, I can additionally confirm the problem for Vivaldi's save dialog.
Whereas the seemingly identical dialog in LibreOffice works as intended.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1949340

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1910913] Re: Deprecating gdebi

2022-10-01 Thread Coeur Noir

https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1524053 ?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/1910913

Title:
  Deprecating gdebi

Status in gdebi package in Ubuntu:
  Invalid

Bug description:
  Purpose of gdebi is to allow installing packages from a file. However,
  it's been 6 years since apt supported installation from a file¹. Let's
  make it easier on both maintainers and the people who have to
  install/use `gdebi` and then may need to search nuances, like passing
  options to dpkg.

  As far as I read gdebi man page, its functional seems fully covered by
  apt. The only thing I'm a bit in doubts about is the `root` option.
  But from my reading of docs, it seems that `gdebi --root=/foo
  myfile.deb` would be analogous to `apt install -o Dpkg::Options::="--
  root=/foo" ./myfile.deb`.

  So, my suggesttion: installing gdebi on currently supported releases
  should print a deprecation notice that explains how a user can install
  local files with `apt` instead. Then eventually remove gdebi from
  repositories.

  I tried contacting maintainers of gdebi to ask whether it's worth
  adding a deprecation notice, but haven't found any ways to do that,
  and so I went straight to creating a report here.

  1: https://mvogt.wordpress.com/2015/11/30/apt-1-1-released/

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1524053] Re: Gdebi 0.9.5.7 doesn't show required dependencies list on non Xubuntu Session than a line.

2022-10-01 Thread Coeur Noir

Soon 7 years later, no improvement ?

On 22.04 the part of window showing needed dependencies won't resize,
only 3~4 lines displayed.

Same kind of readability issues in « Users and Groups ( provided by 
gnome-system-tools )
see https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/1978245

** Attachment added: "gdebi window that does not resize accordingly to its 
content."
   
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1524053/+attachment/5620446/+files/gdebi.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/1524053

Title:
  Gdebi 0.9.5.7 doesn't show required dependencies list on non Xubuntu
  Session than a line.

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  I've tried both Ubuntu Minimal+XFCE & Xubuntu 16.04
  This gravely affect of XFCE, Openbox session on Ubuntu 16.04.
  However this doesn't happen on Xubuntu 16.04 Session at all it shows 
dependencies list normally
  But on XFCE, Openbox session it only shows a line.

  We need more tester to  confirm other session as well such as:
  Unity, Ubuntu, KDE, Kubuntu, lxde, lxde, Lubuntu, Edubuntu, Mythbuntu,
  To confirm if it's only affect on non-Ubuntu flavor Sessions.
  or are they affect to all Sessions Except Xubuntu Session?

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1958019]

2022-10-01 Thread cam

You could share your dmesg.

The other possibility is that the kernel doesn't include the 
configuration (arch IIRC?).

On 10/1/22 04:48, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #698 from jochemp...@gmail.com ---
> (In reply to Cameron Berkenpas from comment #697)
>> Created attachment 301907 [details]
>> attachment-12523-0.html
>>
>> Almost certainly your laptop doesn't have the _DSD entries needed to
>> properly get sound working.
>>
>> Check dmesg for either of these messages:
>> dmesg | grep -i "Platform not supported -EINVAL"
>> or
>> dmesg | grep -i "Error: ACPI _DSD Properties are missing for HID"
>>
>> For reference, see:
>> https://www.spinics.net/lists/alsa-devel/msg146157.html
>> https://bugzilla.kernel.org/show_bug.cgi?id=216194
>>
>> I have the same problem with the Lenovo Legion 2022 Gen 7 (16IAX7). I
>> filed a support ticket with Lenovo a few weeks back, but when support
>> followed back they wanted to text during work hours, and I was too busy
>> to deal with that then and too busy to deal with it since. I think I may
>> actually have some time today.
>>
>> If you have either message in your dmesg, I'd suggest filing a support
>> ticket. If enough people complain about these issues, it may compel them
>> to add the proper _DSD entries into a BIOS update.
>>
>> There's no reason that Lenovo can't include this information in a BIOS
>> update. It does seem that going forward that the intention of Cirrus
>> Logic is for the vendors to include this information in the BIOS. For
>> vendors where this is not the case, likely what's happening is that
>> these values are hard coded in the vendor provided drivers or firmware.
>>
>> It doesn't require them to touch Linux at all.
>>
>> It should be relatively simple for them to add this information as
>> there's already an incomplete entry in the ACPI table as it is.
>>
>> In the kernel bug linked above, I attached a hacky patch that gets sound
>> working on the 16IAX7... But it's a hack where I guessed and hard-coded
>> the values and these could physically damage your speakers if the
>> settings are too inappropriate for your model of laptop (including the
>> 16IAX7). This is very much a USE AT YOUR OWN RISK scenario, and I
>> sincerely recommend against using my patches to avoid any possibility of
>> damage to your laptop. Furthermore, sound doesn't work after resume anyway.
>>
>> Although it could be argued that if people start trying to use hacks
>> like these to enable sound under Linux for their laptop, vendors such as
>> Lenovo may need to issue BIOS updates to address this to avoid costly
>> laptop repairs.
>>
>> On 9/30/22 05:11, bugzilla-dae...@kernel.org wrote:
>>> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>>>
>>> jochemp...@gmail.com  changed:
>>>
>>>  What|Removed |Added
>>>
>> 
>>>CC||jochemp...@gmail.com
>>>
>>> --- Comment #696 fromjochemp...@gmail.com  ---
>>> I seem to have the same issue on a lenovo Legion S7 16ARHA7, here is my
>>> alsa-info hopefully it's of some use:
>>> http://alsa-project.org/db/?f=59acbf18b993b0a49edaaee0027d4b57fcf2055c
>>>
> Thanks for the info, appreciate it.
> using grep i didn't find any of those messages though. so might not be the
> same
> issue after all then.
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1958019

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic

[Touch-packages] [Bug 1958019]

2022-10-01 Thread jochempmgo

(In reply to Cameron Berkenpas from comment #697)
> Created attachment 301907 [details]
> attachment-12523-0.html
> 
> Almost certainly your laptop doesn't have the _DSD entries needed to 
> properly get sound working.
> 
> Check dmesg for either of these messages:
> dmesg | grep -i "Platform not supported -EINVAL"
> or
> dmesg | grep -i "Error: ACPI _DSD Properties are missing for HID"
> 
> For reference, see:
> https://www.spinics.net/lists/alsa-devel/msg146157.html
> https://bugzilla.kernel.org/show_bug.cgi?id=216194
> 
> I have the same problem with the Lenovo Legion 2022 Gen 7 (16IAX7). I 
> filed a support ticket with Lenovo a few weeks back, but when support 
> followed back they wanted to text during work hours, and I was too busy 
> to deal with that then and too busy to deal with it since. I think I may 
> actually have some time today.
> 
> If you have either message in your dmesg, I'd suggest filing a support 
> ticket. If enough people complain about these issues, it may compel them 
> to add the proper _DSD entries into a BIOS update.
> 
> There's no reason that Lenovo can't include this information in a BIOS 
> update. It does seem that going forward that the intention of Cirrus 
> Logic is for the vendors to include this information in the BIOS. For 
> vendors where this is not the case, likely what's happening is that 
> these values are hard coded in the vendor provided drivers or firmware.
> 
> It doesn't require them to touch Linux at all.
> 
> It should be relatively simple for them to add this information as 
> there's already an incomplete entry in the ACPI table as it is.
> 
> In the kernel bug linked above, I attached a hacky patch that gets sound 
> working on the 16IAX7... But it's a hack where I guessed and hard-coded 
> the values and these could physically damage your speakers if the 
> settings are too inappropriate for your model of laptop (including the 
> 16IAX7). This is very much a USE AT YOUR OWN RISK scenario, and I 
> sincerely recommend against using my patches to avoid any possibility of 
> damage to your laptop. Furthermore, sound doesn't work after resume anyway.
> 
> Although it could be argued that if people start trying to use hacks 
> like these to enable sound under Linux for their laptop, vendors such as 
> Lenovo may need to issue BIOS updates to address this to avoid costly 
> laptop repairs.
> 
> On 9/30/22 05:11, bugzilla-dae...@kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=208555
> >
> > jochemp...@gmail.com  changed:
> >
> > What|Removed |Added
> >
> 
> >   CC||jochemp...@gmail.com
> >
> > --- Comment #696 fromjochemp...@gmail.com  ---
> > I seem to have the same issue on a lenovo Legion S7 16ARHA7, here is my
> > alsa-info hopefully it's of some use:
> > http://alsa-project.org/db/?f=59acbf18b993b0a49edaaee0027d4b57fcf2055c
> >

Thanks for the info, appreciate it.
using grep i didn't find any of those messages though. so might not be the same 
issue after all then.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1958019

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F

[Touch-packages] [Bug 1989803] Re: Adjust apport for the new Ubuntu debuginfod service

2022-10-01 Thread Benjamin Drung

** Changed in: apport (Ubuntu)
 Assignee: Sergio Durigan Junior (sergiodj) => Benjamin Drung (bdrung)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1989803

Title:
  Adjust apport for the new Ubuntu debuginfod service

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  In Progress

Bug description:
  With the new Ubuntu debuginfod service
  (https://debuginfod.ubuntu.com), and with the prospect of having the
  system automatically fetch debuginfo from the internet without user
  intervention, it is necessary to adjust apport to cope with this
  scenario.

  I had a conversation with bdmurray and he was concerned that having a
  debuginfod-enabled GDB generate the corefiles that are eventually
  submitted to Ubuntu can be a problem.

  My proposed solution is to disable GDB's debuginfod support when
  collecting the corefile.  This should keep things as is and not
  disturb the retrace service.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1967648] Re: lubuntu jammy - `ubuntu-bug lxqt-config` isn't opening firefox

2022-10-01 Thread Benjamin Drung

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

Yes, xdg-open detects the desktop environment and behaves differently
depending on it. This is a duplicate of bug #1973470.

** This bug has been marked a duplicate of bug 1973470
   Ubuntu-bug command can't find Firefox on Lubuntu Kinetic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1967648

Title:
  lubuntu jammy - `ubuntu-bug lxqt-config` isn't opening firefox

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  /usr/bin/xdg-open: 882: firefox: not found
  /usr/bin/xdg-open: 882: firefox: not found
  xdg-open: no method available for opening 
'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?'

  
  Lubuntu jammy install test on dell optiplex 780

  I adjusted displays as mouse-movements were annoying me, noticed an
  issue thus filed a bug report using `ubuntu-bug lxqt-config`

  ** expected output

  on executing `ubuntu-but lxqt-config` I expected firefox to start

  ** actual output

  ---
  lubuntu@lubuntu:~$ ubuntu-bug lxqt-config

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ...

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
    S: Send report (19.6 KB)
    V: View report
    K: Keep report file for sending later or copying to somewhere else
    I: Cancel and ignore future crashes of this program version
    C: Cancel
  Please choose (S/V/K/I/C): s

  *** Uploading problem information

  The collected information is being sent to the bug tracking system.
  This might take a few minutes.
  98%

  *** To continue, you must visit the following URL:

    https://bugs.launchpad.net/ubuntu/+source/lxqt-
  config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?

  You can launch a browser now, or copy this URL into a browser on
  another computer.

  Choices:
    1: Launch a browser now
    C: Cancel
  Please choose (1/C): 1
  /usr/bin/xdg-open: 882: firefox: not found
  /usr/bin/xdg-open: 882: firefox: not found
  xdg-open: no method available for opening 
'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?'
  ---

  ie. `firefox` doesn't start as it's now a snap package

  first attempt to file `ubuntu-bug apport` ended up with

  ---
  *** To continue, you must visit the following URL:

    https://bugs.launchpad.net/ubuntu/+source/lxqt-
  config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?

  You can launch a browser now, or copy this URL into a browser on
  another computer.

  Choices:
    1: Launch a browser now
    C: Cancel
  Please choose (1/C): 1
  /usr/bin/xdg-open: 882: firefox: not found
  /usr/bin/xdg-open: 882: firefox: not found
  xdg-open: no method available for opening 
'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?'
  lubuntu@lubuntu:~$
  ---

  ** other notes

  - I don't know if this only impacts lubuntu, or others too
  - I've not (yet) looked for other/existing bugs

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu80
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.468
  CurrentDesktop: LXQt
  Date: Sun Apr  3 12:09:05 2022
  LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220402)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1991324] Re: Initramfs-tools: iSCSI boot resulting in modprobe not found error message

2022-10-01 Thread Pascal van Dam

Herewitht the bootlog from serial console of the PI (btw this is from
Kinetic Kudo e.g. bug is persistent in multiple versions 22.04.1 and
22.10)

To reproduce:

1. Install pristine Ubuntu Server for PI/ARM64 on SD or USB.
2. Install open-iscsi, lvm2, nfs-common
3. Configure iSCSI initiator
4. Attach iSCSI volume from NAS
5. Create LVM on iSCSI volume
6. Reinstall linux-image, linux-modules and linux-modules-extra to generate
initramfs
6. Rsync SD card to iSCSI
7. Copy /boot/firmware to TFTPBOOT dir on NAS
8. Alter cmdline.txt for iSCSI boot
9. Reboot PI from iSCSI
9a PI4 gets vmlinuz, cmdline.txt, config.txt and initrd.img from NAS
9b Kernel boots succesfully
9c Init in RAM disk complains about binaries that it cannot find

Hope this helps

** Attachment added: "pi4-iscsi-initramfs-boot.log"

https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1991324/+attachment/5620431/+files/pi4-iscsi-initramfs-boot.log

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1991324

Title:
Initramfs-tools: iSCSI boot resulting in modprobe not found error
message

Status in initramfs-tools package in Ubuntu:
Incomplete

Bug description:
My RPi4's are having their rootvg on iSCSI and boot from them. The
kernel modules etc are in the initramfs. However since 22.04 the
initramfs is not generated corrected and while booting from it it
results in error messages stating various binaries/scripts are not
locatable.

E.g. modprobe, systemd-udev, mdadm etc.

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

--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp

41 matches

Mail list logo