[Touch-packages] [Bug 599808] Re: software-properties-gtk lacks version number

2022-03-12 Thread Mörgæs 
Still a problem in 21.10.

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

Title:
  software-properties-gtk lacks version number

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  Expected behaviour

  software-properties-gtk --version

  produces output with version number of the utility.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/599808/+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 1952353] Re: dmesg: read kernel buffer failed: Operation not permitted

2022-03-12 Thread Marji Cermak 
I can confirm dmesg on Ubuntu 21.10 gives me "Operation not permitted",
even though my user is in the "adm" group:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 21.10
Release:21.10
Codename:   impish

$ ls -l /var/log/dmesg*
-rw-r- 1 root adm 100336 Mar 13 17:01 /var/log/dmesg
-rw-r- 1 root adm  94365 Mar 13 16:40 /var/log/dmesg.0
-rw-r- 1 root adm  23990 Mar 13 15:00 /var/log/dmesg.1.gz
-rw-r- 1 root adm  23017 Mar  9 21:50 /var/log/dmesg.2.gz
-rw-r- 1 root adm  23295 Mar  4 18:51 /var/log/dmesg.3.gz
-rw-r- 1 root adm  23253 Feb 24 21:34 /var/log/dmesg.4.gz

$ id
uid=1000(marji) gid=1000(marji) 
groups=1000(marji),4(adm),5(tty),10(uucp),20(dialout),24(cdrom),27(sudo),30(dip),46(plugdev),121(lpadmin),132(lxd),133(sambashare),134(docker)

$ dmesg
dmesg: read kernel buffer failed: Operation not permitted

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

Title:
  dmesg: read kernel buffer failed: Operation not permitted

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Run /bin/dmesg, get:

  dmesg: read kernel buffer failed: Operation not permitted

  sudo dmesg works, but I should not have to do that.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: util-linux 2.36.1-8ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Thu Nov 25 11:13:58 2021
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/tcsh
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to impish on 2021-11-21 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1952353/+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 1964682] Re: IBus not starting properly at login with gnome-shell 42

2022-03-12 Thread Gunnar Hjalmarsson 
A no-change rebuild of ibus doesn't help.

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

Title:
  IBus not starting properly at login with gnome-shell 42

Status in gnome-shell package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New

Bug description:
  To get to the state in the bug summary I did:

  1. Installed Ubuntu via the 220312 ISO

  2. Made sure that all packages were updated

  3. Installed ibus-libpinyin, re-logged in, and added "Intelligent
  Pinyin" to the input sources

  4. Enabled -proposed

  5. Run this command:
  sudo apt install gnome-shell gnome-shell-common gir1.2-mutter-10 
libmutter-10-0 mutter-common

  6. Rebooted

  Now, once logged in, gnome-shell does not include "Intelligent Pinyin"
  in the input source menu. Several expected processes are missing:

  $ ps aux | grep ibus
  gunnar  3057  0.0  0.0 232404  7984 ?Sl   20:05   0:00 
ibus-daemon --panel disable -r --xim
  gunnar  3076  0.0  0.0 157280  6228 ?Sl   20:05   0:00 
/usr/libexec/ibus-memconf
  gunnar  5117  0.0  0.0  24492  2776 pts/0S+   20:06   0:00 grep 
--color=auto ibus

  If I start ibus-setup it shows the attached dialog. From there I can
  click "Yes" and successfully start IBus that way, and then it works as
  expected.

  Note that im-config is not involved. Nowadays, on GNOME desktops, we
  rely completely on the GNOME mechanisms for starting and configuring
  IBus.

  One thought is that ibus upstream has not released since August 20.
  Can it possibly be that some unreleased upstream ibus commits are
  needed for gnome-shell 42?

  https://github.com/ibus/ibus/commits/master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964682/+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 1948533] Re: any dns defined in network-manager doesnt go in openvpn tunnel (leaks on gnome/mate/xubuntu only in 21.10)

2022-03-12 Thread Launchpad Bug Tracker 
[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  any dns defined in network-manager doesnt go in openvpn tunnel (leaks
  on gnome/mate/xubuntu only in 21.10)

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  in all linux including ubuntu up to version 21.04, when dns is set to not 
automatic in network manager and one dns is set manually (exemple 1.1.1.1) when 
openvpn is used the dns is going through the vpn tunnel.
  On ubuntu 21.10 (I tested ubuntu, ubuntu mate and xubuntu)I can affirm the 
dns in this case is not going trough the vpn.it is leaking.I have used ubuntu 
for years this is first time this problem occurs (21.10).(and it s not just a 
question of packages because on my arch linux installs I never had such 
problem, so it must be a config problem.

  (when using packages stubby or dnscrypt-proxy (to encrypt dns queries)
  and dns 127.0.0.1 is set in network-manager the dns does goes trough
  the vpn (but stubby service needs to be sometimes reloded, it is less
  reliable that it used to be with previous versions of ubuntu)

  (I cannot speculate where the bug is from (network-manager, systemd
  resolved etc)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1948533/+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 1964693] Re: packagekitd crashed with SIGSEGV in AptCacheFile::resolvePkgID()

2022-03-12 Thread Apport retracing service 
*** This bug is a duplicate of bug 1964559 ***
https://bugs.launchpad.net/bugs/1964559

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1964693/+attachment/5568352/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1964693/+attachment/5568354/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1964693/+attachment/5568357/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1964693/+attachment/5568358/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1964693/+attachment/5568359/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1964693/+attachment/5568360/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1964693/+attachment/5568361/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1964559

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  packagekitd crashed with SIGSEGV in AptCacheFile::resolvePkgID()

Status in packagekit package in Ubuntu:
  New

Bug description:
  Estava atualizando o sistema e apareceu o erro, não sei do que se
  trata!

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: packagekit 1.2.5-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Mar 13 00:02:54 2022
  ExecutablePath: /usr/libexec/packagekitd
  InstallationDate: Installed on 2022-03-08 (5 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228)
  ProcCmdline: /usr/libexec/packagekitd
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   SHELL=/bin/sh
  RebootRequiredPkgs: Error: path contained symlinks.
  SegvAnalysis:
   Segfault happened at: 0x7f37f7239e0e <__strncasecmp_l_sse2+446>: adc
%al,(%rax)
   PC (0x7f37f7239e0e) ok
   source "%al" ok
   destination "(%rax)" (0x0efc) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: packagekit
  StacktraceTop:
   AptCacheFile::resolvePkgID(char const*) () from 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   AptIntf::resolvePackageIds(char**, unsigned long) () from 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   ?? ()
   g_tree_remove () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: packagekitd crashed with SIGSEGV in AptCacheFile::resolvePkgID()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1964693/+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 1964690] [NEW] Print jobs stuck in que unti reboot

2022-03-12 Thread Russel Lopez 
Public bug reported:

If I turn on my hardwired netowrked HP printer, after my computer is
booted, print jobs get stuck in the que.  If I then reboot my computer,
the print que will then print just fine.

This happens on two different ubuntu computers running 20.04 LTS.
Printing has been working fine since I installed ubuntu years ago.  I
think an update got me.

Thanks,

Russel


Description:Ubuntu 20.04.4 LTS
Release:20.04

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups 2.3.1-9ubuntu1.1
ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166
Uname: Linux 5.4.0-104-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 12 17:47:23 2022
Lpstat:
 device for Hewlett-Packard-HP-Color-LaserJet-CM3530-MFP: 
dnssd://HP%20Color%20LaserJet%20CM3530%20MFP%20%5B961274%5D._pdl-datastream._tcp.local/
 device for HP_Color_LaserJet_CM3530_MFP_961274_: 
implicitclass://HP_Color_LaserJet_CM3530_MFP_961274_/
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
 Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
 |__ Port 6: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
 |__ Port 13: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
MachineType: System manufacturer System Product Name
Papersize: letter
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_CM3530_MFP_961274_.ppd', 
'/etc/cups/ppd/Hewlett-Packard-HP-Color-LaserJet-CM3530-MFP.ppd'] failed with 
exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_CM3530_MFP_961274_.ppd: 
Permission denied
 grep: /etc/cups/ppd/Hewlett-Packard-HP-Color-LaserJet-CM3530-MFP.ppd: 
Permission denied
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-104-generic 
root=UUID=46e2f957-6453-4c88-b706-997f1104aa4c ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/10/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1005
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z390-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1005:bd04/10/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: ASUS_MB_CNL
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug focal

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

Title:
  Print jobs stuck in que unti reboot

Status in cups package in Ubuntu:
  New

Bug description:
  If I turn on my hardwired netowrked HP printer, after my computer is
  booted, print jobs get stuck in the que.  If I then reboot my
  computer, the print que will then print just fine.

  This happens on two different ubuntu computers running 20.04 LTS.
  Printing has been working fine since I installed ubuntu years ago.  I
  think an update got me.

  Thanks,

  Russel

  
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166
  Uname: Linux 5.4.0-104-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 12 17:47:23 2022
  Lpstat:
   device for Hewlett-Packard-HP-Color-LaserJet-CM3530-MFP: 
dnssd://HP%20Color%20LaserJet%20CM3530%20MFP%20%5B961274%5D._pdl-datastream._tcp.local/
   device for HP_Color_LaserJet_CM3530_MFP_961274_: 
implicitclass://HP_Color_LaserJet_CM3530_MFP_961274_/
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub,

[Touch-packages] [Bug 1872141] Re: evolution-source-registry crashed with SIGSEGV in invoke_set_property_in_idle_cb()

2022-03-12 Thread Claus7 
This happened using ubuntu 22.04 development version.

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

Title:
  evolution-source-registry crashed with SIGSEGV in
  invoke_set_property_in_idle_cb()

Status in evolution-data-server package in Ubuntu:
  Expired

Bug description:
  [Joshua Peisach]

  I was just installing:
  ubuntu-mate-desktop and ubuntu-mate-*
  Then for some reason it just crashed, I have no idea what happened. I was 
trying to add an addition to python code.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: evolution-data-server 3.36.1-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Fri Apr 10 16:34:34 2020
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/libexec/evolution-source-registry
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  ProcCmdline: /usr/libexec/evolution-source-registry
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   LANGUAGE=en_US
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: evolution-source-registry crashed with SIGSEGV in 
g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1872141/+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 1910938] Re: Text is missing from shell panel and menus

2022-03-12 Thread Nicholas Schell 
Just got a new Lenovo Thinkpad and using Ubuntu 20.04, and I think I'm
seeing a very similar issue. After leaving the laptop on for so long
eventually a ton of the text menues and displays either show NO text at
all, or half of the characters are missing. I'll attempt a screenshot
the next time it happens, it doesn't take longer than a day it seems as
already reported.

I also use Discord so I wonder if that is part of the culprit as well.
Will try using without Discord for about a day.

I have found a simple logout/login is enough to fix all text menues. So
it doesn't seem a full reboot is strictly necessary.

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

Title:
  Text is missing from shell panel and menus

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hello [happy new year :) ! ]

  Text information in the Ubuntu dialogs aren't displayed, or some times just a 
part of it.
  I don't see the hours, but i see the icons like Firefox actually opened, my 
battery etc. and notifications are empty (just the "!" icon).
  Text normally displayed when mouse-hover the applications icons is not 
displayed, when Ubuntu ask for my password the frame display only 3 or 4 
characters, when i put the computer in standby and reopen it doesn't change 
anything, and the bullets of my password aren't displayed when i login.
  The text normally displayed on the menus aren't displayed too, same for the 
application menu (when hitting the bottom left corner button) and icons of 
applications (like Discord options on the top right of the screen).
  The only text from xorg that is displayed (if it's from xorg…) is the 
window's title (like "#Room - Discord" for Discord application, or 
"me@computer: ~/" above the terminal).
  What is left works : Firefox can display text, and text is displayed in 
settings for example.

  P.S: a reboot solved the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
  Uname: Linux 5.4.0-59-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 11 02:26:55 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo HD Graphics 620 [17aa:39e9]
  InstallationDate: Installed on 2020-11-15 (56 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 80V0
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=2342b448-1302-426d-9afd-b40fd298cdab ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/03/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3PCN20WW(V2.04)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo ideapad 510S-13IKB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 510S-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr3PCN20WW(V2.04):bd07/03/2018:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80V0
  dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB
  dmi.product.version: Lenovo ideapad 510S-13IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Touch-packages] [Bug 1964682] [NEW] IBus not starting properly at login with gnome-shell 42

2022-03-12 Thread Gunnar Hjalmarsson 
Public bug reported:

To get to the state in the bug summary I did:

1. Installed Ubuntu via the 220312 ISO

2. Made sure that all packages were updated

3. Installed ibus-libpinyin, re-logged in, and added "Intelligent
Pinyin" to the input sources

4. Enabled -proposed

5. Run this command:
sudo apt install gnome-shell gnome-shell-common gir1.2-mutter-10 libmutter-10-0 
mutter-common

6. Rebooted

Now, once logged in, gnome-shell does not include "Intelligent Pinyin"
in the input source menu. Several expected processes are missing:

$ ps aux | grep ibus
gunnar  3057  0.0  0.0 232404  7984 ?Sl   20:05   0:00 ibus-daemon 
--panel disable -r --xim
gunnar  3076  0.0  0.0 157280  6228 ?Sl   20:05   0:00 
/usr/libexec/ibus-memconf
gunnar  5117  0.0  0.0  24492  2776 pts/0S+   20:06   0:00 grep 
--color=auto ibus

If I start ibus-setup it shows the attached dialog. From there I can
click "Yes" and successfully start IBus that way, and then it works as
expected.

Note that im-config is not involved. Nowadays, on GNOME desktops, we
rely completely on the GNOME mechanisms for starting and configuring
IBus.

One thought is that ibus upstream has not released since August 20. Can
it possibly be that some unreleased upstream ibus commits are needed for
gnome-shell 42?

https://github.com/ibus/ibus/commits/master

** Affects: gnome-shell (Ubuntu)
 Importance: High
 Status: New

** Affects: ibus (Ubuntu)
 Importance: High
 Status: New


** Tags: jammy rls-jj-incoming

** Attachment added: "ibus-setup_response.png"
   
https://bugs.launchpad.net/bugs/1964682/+attachment/5568298/+files/ibus-setup_response.png

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

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

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

Title:
  IBus not starting properly at login with gnome-shell 42

Status in gnome-shell package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New

Bug description:
  To get to the state in the bug summary I did:

  1. Installed Ubuntu via the 220312 ISO

  2. Made sure that all packages were updated

  3. Installed ibus-libpinyin, re-logged in, and added "Intelligent
  Pinyin" to the input sources

  4. Enabled -proposed

  5. Run this command:
  sudo apt install gnome-shell gnome-shell-common gir1.2-mutter-10 
libmutter-10-0 mutter-common

  6. Rebooted

  Now, once logged in, gnome-shell does not include "Intelligent Pinyin"
  in the input source menu. Several expected processes are missing:

  $ ps aux | grep ibus
  gunnar  3057  0.0  0.0 232404  7984 ?Sl   20:05   0:00 
ibus-daemon --panel disable -r --xim
  gunnar  3076  0.0  0.0 157280  6228 ?Sl   20:05   0:00 
/usr/libexec/ibus-memconf
  gunnar  5117  0.0  0.0  24492  2776 pts/0S+   20:06   0:00 grep 
--color=auto ibus

  If I start ibus-setup it shows the attached dialog. From there I can
  click "Yes" and successfully start IBus that way, and then it works as
  expected.

  Note that im-config is not involved. Nowadays, on GNOME desktops, we
  rely completely on the GNOME mechanisms for starting and configuring
  IBus.

  One thought is that ibus upstream has not released since August 20.
  Can it possibly be that some unreleased upstream ibus commits are
  needed for gnome-shell 42?

  https://github.com/ibus/ibus/commits/master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964682/+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 1946538] Re: Update to Maliit 2.x

2022-03-12 Thread sacharja 
Worse: login screen unusable in a Kubuntu Wayland session because the
old Maliit is blocking the whole screen.

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

Title:
  Update to Maliit 2.x

Status in maliit-framework package in Ubuntu:
  Confirmed

Bug description:
  https://github.com/maliit/framework/releases

  Your package is ancient.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1946538/+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 1961477] Re: software-properties-gtk not running

2022-03-12 Thread Hans Joachim Desserud 
Thanks for adding the error message.

I'm afraid don't know what goes wrong, all I could find when searching
for the error message was an ancient bug report (bug 1191700) which I
don't know if is relevant or not. Setting status back to New, hopefully
someone else can take a look at this and see what's going on.

** Changed in: software-properties (Ubuntu)
   Status: Incomplete => New

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

Title:
  software-properties-gtk not running

Status in software-properties package in Ubuntu:
  New

Bug description:
  When I try to run the program from Ubuntu nothing happens. An error
  occurs when trying to run the program from the console. Attempts to
  roll back the version were unsuccessful.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.99.9.8
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 19 15:33:18 2022
  InstallationDate: Installed on 2022-01-10 (39 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1961477/+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 1926256] Re: Pasted text in the terminal is always highlighted and selected

2022-03-12 Thread Norbert 
Still a problem for Ubuntu MATE 22.04 LTS. Please fix it on distro
level.

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

Title:
  Pasted text in the terminal is always highlighted and selected

Status in bash package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in mate-terminal package in Ubuntu:
  Confirmed
Status in readline package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 21.04 installed
  2. Launch terminal
  3a. Execute some command, select this command to copy it, then paste command
  3b. Paste some command from clipboard to terminal

  Expected result:
  * pasted command is not highlighted and is not selected

  Actual result:
  * pasted command is selected and highlighted

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: mate-terminal 1.24.1-1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue Apr 27 09:43:56 2021
  InstallationDate: Installed on 2021-04-23 (3 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  SourcePackage: mate-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1926256/+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 1964665] Re: packagekitd crashed with SIGSEGV in __strcmp_avx2()

2022-03-12 Thread Apport retracing service 
*** This bug is a duplicate of bug 1962702 ***
https://bugs.launchpad.net/bugs/1962702

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1964665/+attachment/5568186/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1964665/+attachment/5568188/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1964665/+attachment/5568191/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1964665/+attachment/5568192/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1964665/+attachment/5568193/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1964665/+attachment/5568194/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1964665/+attachment/5568195/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1962702

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  packagekitd crashed with SIGSEGV in __strcmp_avx2()

Status in packagekit package in Ubuntu:
  New

Bug description:
  Trying to install 3rd party software.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: packagekit 1.2.5-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Mar 12 06:52:40 2022
  ExecutablePath: /usr/libexec/packagekitd
  InstallationDate: Installed on 2022-03-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220310)
  ProcCmdline: /usr/libexec/packagekitd
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/sh
  SegvAnalysis:
   Segfault happened at: 0x7f6d7bcc5ade <__strcmp_avx2+30>: vmovdqu 
(%rdi),%ymm1
   PC (0x7f6d7bcc5ade) ok
   source "(%rdi)" (0x7f6dfa6f26dc) not located in a known VMA region (needed 
readable region)!
   destination "%ymm1" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: packagekit
  StacktraceTop:
   __strcmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:115
   AptCacheFile::resolvePkgID(char const*) () from 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   AptIntf::resolvePackageIds(char**, unsigned long) () from 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   ?? ()
  Title: packagekitd crashed with SIGSEGV in __strcmp_avx2()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1964665/+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 1948877] Re: Bluetooth headphones media buttons no longer work

2022-03-12 Thread Roman 
The bug is not present in the current development release of Ubuntu
22.04. Moreover, I've noticed that OS volume control is tied directly to
the headphones.

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

Title:
  Bluetooth headphones media buttons no longer work

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  In KUbuntu 21.10, most media buttons in my bluetooth headphones
  stopped working. This includes the "play/pause" button, "play next"
  (calls after long press of volume increase), and "play previous" (long
  press of volume decrease). The volume +/- buttons themselves are
  working, but this seemingly is implemented entirely in the headphones
  and does not require any communication over bluetooth.

  In previous ubuntu (21.04) these buttons worked, and I expect them
  working.

  My headset is Qumo Accord 3.

  Here is output of "inxi -Eaz" in terminal:

  Bluetooth: Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 
bus-ID: 1-7:3 chip-ID: 0bda:b008 class-ID: e001
     serial: 
     Report: hciconfig ID: hci0 rfk-id: 1 state: up address:  
bt-v: 2.1 lmp-v: 4.0 sub-v: 9f73 hci-v: 4.0
     rev: e2f
     Info: acl-mtu: 820:8 sco-mtu: 255:16 link-policy: rswitch hold 
sniff park link-mode: slave accept
     service-classes: rendering, capturing, object transfer, audio, 
telephony

  Some possible workarounds that I found suggest to "modprobe uinput",
  but the uinput module does not get loaded (lsmod does not list it even
  after modprobe'ing).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1948877/+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 1964642] Re: Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4 but can connect to Ubuntu 20.4

2022-03-12 Thread Barto 
I am not sure of this bug being related to the openssh package, but the
Ubuntu Foundations Team Bug Bot has asked me to fill this field.

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

-- 
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/1964642

Title:
  Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4
  but can connect to Ubuntu 20.4

Status in openssh package in Ubuntu:
  New

Bug description:
  Two years ago I was able to create a Virtualbox Ubuntu 20.04 guest in a 
Windows 10 host with Packer 1.5.6, using an unattended installation.
  The Packer command was:
    "boot_command": [
  " ",
  "autoinstall ds=nocloud-net;s=http://{{ .HTTPIP }}:{{ .HTTPPort }}/",
  ""
    ],
  The user-data file was:
  #cloud-config
  autoinstall:
    version: 1
    identity:
  realname: mclibre
  hostname: ubuntu
  password: 
'$6$mclibre$YiuRPSZM3ZXVe4UyIqv1dvy9rUjf5/LsGCkDyaex.WN45wzVTuRmW5QLuctuicGAFZIO2M3QR8NLdtQYatKTn1'
  username: mclibre
    locale: es_ES.UTF-8
    keyboard:
  layout: es
    network:
  network:
    version: 2
    ethernets:
  ens33: {dhcp4: true, dhcp-identifier: mac}
    ssh:
  install-server: true
    late-commands:
  - sed -i 's/^#*\(send dhcp-client-identifier\).*$/\1 = hardware;/' 
/target/etc/dhcp/dhclient.conf
  - 'sed -i "s/dhcp4: true/&\n  dhcp-identifier: mac/" 
/target/etc/netplan/00-installer-config.yaml'
  Now, I have tried to create a Virtualbox Ubuntu 20.04.4/.3/.2/.1 guest using 
packer 1.5.6 but Packer can't create the image because once the installation is 
done, after rebooting the SSH server does not answer (the packer log error 
says: SSH handshake err: Timeout during SSH handshake).
  I have tried with the last version of Packer, Packer 1.8.0, and the result is 
the same. I can create a Ubuntu Server 20.4 image but not a Ubuntu Server 
20.4.1, .2, .3 or .4 image.
  I can provide as much aditional information as you want.
  Thanking you in advance,
  Bartolome Sintes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1964642/+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 1964642] [NEW] Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4 but can connect to Ubuntu 20.4

2022-03-12 Thread Launchpad Bug Tracker 
You have been subscribed to a public bug:

Two years ago I was able to create a Virtualbox Ubuntu 20.04 guest in a Windows 
10 host with Packer 1.5.6, using an unattended installation.
The Packer command was:
  "boot_command": [
" ",
"autoinstall ds=nocloud-net;s=http://{{ .HTTPIP }}:{{ .HTTPPort }}/",
""
  ],
The user-data file was:
#cloud-config
autoinstall:
  version: 1
  identity:
realname: mclibre
hostname: ubuntu
password: 
'$6$mclibre$YiuRPSZM3ZXVe4UyIqv1dvy9rUjf5/LsGCkDyaex.WN45wzVTuRmW5QLuctuicGAFZIO2M3QR8NLdtQYatKTn1'
username: mclibre
  locale: es_ES.UTF-8
  keyboard:
layout: es
  network:
network:
  version: 2
  ethernets:
ens33: {dhcp4: true, dhcp-identifier: mac}
  ssh:
install-server: true
  late-commands:
- sed -i 's/^#*\(send dhcp-client-identifier\).*$/\1 = hardware;/' 
/target/etc/dhcp/dhclient.conf
- 'sed -i "s/dhcp4: true/&\n  dhcp-identifier: mac/" 
/target/etc/netplan/00-installer-config.yaml'
Now, I have tried to create a Virtualbox Ubuntu 20.04.4/.3/.2/.1 guest using 
packer 1.5.6 but Packer can't create the image because once the installation is 
done, after rebooting the SSH server does not answer (the packer log error 
says: SSH handshake err: Timeout during SSH handshake).
I have tried with the last version of Packer, Packer 1.8.0, and the result is 
the same. I can create a Ubuntu Server 20.4 image but not a Ubuntu Server 
20.4.1, .2, .3 or .4 image.
I can provide as much aditional information as you want.
Thanking you in advance,
Bartolome Sintes

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


** Tags: bot-comment packer ssh unattended virtualbox
-- 
Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4 but can 
connect to Ubuntu 20.4
https://bugs.launchpad.net/bugs/1964642
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to openssh in Ubuntu.

-- 
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-03-12 Thread thijs 
(In reply to darnellkeithj from comment #574)
> Can't someone just make a kernel build for ubuntu or some widely used Linux
> version and put it on github? There is a lot of patching going on here but
> no good documentation on how to do it.

Probably yes, but not sure you should trust and install a kernel hosted
by just anyone ;-) I'm hoping that this patch will just soon find it's
way to the official distributed kernels...

-- 
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 pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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-03-12 Thread thijs 
(In reply to Fer Korol from comment #572)
> Here is another variant, now with RC6, works the sound and the nvidia
> drivers at the same time! (with some tricks):
> 
> A) FIRST TIME
> 1) install kernel build tools:
> (https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel):
> 
> * sudo apt install libncurses-dev gawk flex bison openssl libssl-dev dkms
> libelf-dev libudev-dev libpci-dev libiberty-dev autoconf git p7zip-full
> 
> 2) clone the kernel from github and checkout to v5.17 branch (Rather large,
> multiple GB's):
> 
> * git clone https://github.com/torvalds/linux.git
> 
> 3)Make a 7z of the linux folder in a clear state
> 7z a linux-clean.7z linux
> 
> 3) get the patch and let it in one superior level of the linux folder:
> 
> https://patchwork.kernel.org/project/linux-acpi/patch/20220121172431.6876-4-
> sbind...@opensource.cirrus.com/
> 
> 
> A) FOR EACH RC RELEASE:
> 7z x linux-clean.7z
> cp Support-Spi-in-i2c-multi-instantiate-driver.patch linux/
> cd linux
> git pull
> git checkout v5.17-rc6
> git am Support-Spi-in-i2c-multi-instantiate-driver.patch
> make olddefconfig
> ./scripts/config --enable CONFIG_SERIAL_MULTI_INSTANTIATE
> ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_I2C
> ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_SPI
> ./scripts/config --disable CONFIG_DEBUG_INFO
> ./scripts/config --set-str CONFIG_SYSTEM_TRUSTED_KEYS ""
> ./scripts/config --set-str CONFIG_SYSTEM_REVOCATION_KEYS ""
> make -j 16
> make modules_install
> make install
> 
> 
> The patch is mandatory to enable the sound in ubuntu, im tried without the
> path and the sound don't work. With this steps will do.
> In order to make work the nvidia drivers in the 17-rc6 im just change in
> "more drivers" option of ubuntu, the current versión of the nvidia driver
> for another (511 to 470 for example).
> Im using hybrid graphics mode in the bios.

Thanks! I just tried this rc6 version on my machine, and sound plus
nvidia drivers work fine with this. In addition to the described steps,
I also did run a "make headers_install", to make sure that nvidia could
compile it's module.

My machine: Lenovo Legion 7 16ACHg6 82N6 - Laptop 16" IPS 2560 x 1600
(WQXGA) 165 Hz - AMD Ryzen - with 3 external monitors connected and
working (2560x1440).

I hope the patch gets propagated soon to a real release.

-- 
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 pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: