[Touch-packages] [Bug 2042710] Re: Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14, 1) due to missing kernel modules in initramfs

[Terence Tan]

With the entry, here's the dmesg:

** Attachment added: "dmesg-with-intel-lpss-pci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2042710/+attachment/5719168/+files/dmesg-with-intel-lpss-pci.txt

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

Title:
  Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14,1)
  due to missing kernel modules in initramfs

Status in initramfs-tools package in Ubuntu:
  Triaged
Status in initramfs-tools source package in Mantic:
  New

Bug description:
  I have a MacBook Pro 2017 (MacBookPro14,1) with an encrypted root
  partition, which I decrypt via passphrase during boot, at the "Please
  unlock disk nvme0n1p4_crypt" prompt.

  Using 23.04 "Lunar" this worked fine. However after upgrading to 23.10
  "Mantic", the built-in keyboard doesn't work for entering the
  passphrase.

  Quickest workaround: plug in a USB keyboard for entering the
  passphrase.

  Workaround: add the following modules to "/etc/initramfs-
  tools/modules":

  spi_pxa2xx_platform
  intel_lpss_pci

  ... then "sudo update-initramfs -u".

  I found that both kernel modules were required to get the keyboard
  recognised in initramfs.

  I did a bit of digging into what changed for 23.10. It could
  potentially (?) be commit 2df78bbb143884b9601a32608e12e43d40ccb0b0 "Do
  not install ARM/RISCV specific modules on other architectures".

  I had a look into how dracut handles it. Turns out that they
  specifically include "spi_pxa2xx_platform" after reporting a similar
  bug report in Fedora:
  https://bugzilla.redhat.com/show_bug.cgi?id=2166209

  I don't know how (if?) they handle the 2nd module, "intel_lpss_pci".

  Anyway, I don't need an immediate fix since the workaround works for
  me. Just posting this for further investigation, and for any other
  MacBook Pro users in the same situation. Thanks for working on Ubuntu,
  I think you're all amazing!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2042710/+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 2042710] Re: Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14, 1) due to missing kernel modules in initramfs

[Terence Tan]

And here's the output of "lspci -vv" -- sorry for the multiple messages,
couldn't figure out how to attach more than one attachment to a comment!

** Attachment added: "lspci-dash-vv.txt"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2042710/+attachment/5719169/+files/lspci-dash-vv.txt

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

Title:
  Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14,1)
  due to missing kernel modules in initramfs

Status in initramfs-tools package in Ubuntu:
  Triaged
Status in initramfs-tools source package in Mantic:
  New

Bug description:
  I have a MacBook Pro 2017 (MacBookPro14,1) with an encrypted root
  partition, which I decrypt via passphrase during boot, at the "Please
  unlock disk nvme0n1p4_crypt" prompt.

  Using 23.04 "Lunar" this worked fine. However after upgrading to 23.10
  "Mantic", the built-in keyboard doesn't work for entering the
  passphrase.

  Quickest workaround: plug in a USB keyboard for entering the
  passphrase.

  Workaround: add the following modules to "/etc/initramfs-
  tools/modules":

  spi_pxa2xx_platform
  intel_lpss_pci

  ... then "sudo update-initramfs -u".

  I found that both kernel modules were required to get the keyboard
  recognised in initramfs.

  I did a bit of digging into what changed for 23.10. It could
  potentially (?) be commit 2df78bbb143884b9601a32608e12e43d40ccb0b0 "Do
  not install ARM/RISCV specific modules on other architectures".

  I had a look into how dracut handles it. Turns out that they
  specifically include "spi_pxa2xx_platform" after reporting a similar
  bug report in Fedora:
  https://bugzilla.redhat.com/show_bug.cgi?id=2166209

  I don't know how (if?) they handle the 2nd module, "intel_lpss_pci".

  Anyway, I don't need an immediate fix since the workaround works for
  me. Just posting this for further investigation, and for any other
  MacBook Pro users in the same situation. Thanks for working on Ubuntu,
  I think you're all amazing!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2042710/+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 2042710] Re: Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14, 1) due to missing kernel modules in initramfs

[Terence Tan]

Hi Benjamin, I just tried again and can confirm that "intel_lpss_pci" is
necessary -- without it, no keyboard.

I removed the intel_lpss_pci entry and booted and collected the attached
dmesg.

** Attachment added: "dmesg-without-intel-lpss-pci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2042710/+attachment/5719167/+files/dmesg-without-intel-lpss-pci.txt

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

Title:
  Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14,1)
  due to missing kernel modules in initramfs

Status in initramfs-tools package in Ubuntu:
  Triaged
Status in initramfs-tools source package in Mantic:
  New

Bug description:
  I have a MacBook Pro 2017 (MacBookPro14,1) with an encrypted root
  partition, which I decrypt via passphrase during boot, at the "Please
  unlock disk nvme0n1p4_crypt" prompt.

  Using 23.04 "Lunar" this worked fine. However after upgrading to 23.10
  "Mantic", the built-in keyboard doesn't work for entering the
  passphrase.

  Quickest workaround: plug in a USB keyboard for entering the
  passphrase.

  Workaround: add the following modules to "/etc/initramfs-
  tools/modules":

  spi_pxa2xx_platform
  intel_lpss_pci

  ... then "sudo update-initramfs -u".

  I found that both kernel modules were required to get the keyboard
  recognised in initramfs.

  I did a bit of digging into what changed for 23.10. It could
  potentially (?) be commit 2df78bbb143884b9601a32608e12e43d40ccb0b0 "Do
  not install ARM/RISCV specific modules on other architectures".

  I had a look into how dracut handles it. Turns out that they
  specifically include "spi_pxa2xx_platform" after reporting a similar
  bug report in Fedora:
  https://bugzilla.redhat.com/show_bug.cgi?id=2166209

  I don't know how (if?) they handle the 2nd module, "intel_lpss_pci".

  Anyway, I don't need an immediate fix since the workaround works for
  me. Just posting this for further investigation, and for any other
  MacBook Pro users in the same situation. Thanks for working on Ubuntu,
  I think you're all amazing!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2042710/+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 2043114] Re: sshd segmentation fault on 20.04.6 (focal)

[Athos Ribeiro]

Hi Ivaylo, thanks for all the information so far!

Can you consistently reproduce it?

Would you also mind sharing the exact steps it would take for us to
reproduce it from a fresh focal install?

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

Title:
  sshd segmentation fault on 20.04.6 (focal)

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  We have a physical server running Ubuntu 20.04.6 LTS (amd64) and 
openssh-server 1:8.2p1-4ubuntu0.9. Sometimes sshd crashes with a segmentation 
fault on remote login with key authentication:
  [193107.651745] sshd[1229630]: segfault at 5557eba6a008 ip 7f2326a2ca53 
sp 7ffcba40c510 error 4 in libc-2.31.so[7f23269b8000+178000]

  We’ve changed only the following values in the stock sshd_config file:

  LogLevel DEBUG
  PasswordAuthentication no
  MaxStartups 100:30:100

  The server is used for automated software testing, and sometimes our test 
suite might make a large amount of SSH connections in a short period of time, 
which seems to be correlated with the crashes. But at the same time, I have to 
note that the connection count was not near the MaxStartups limit, and we’ve 
had crashes before adding that setting.
  Since the backtrace shows the debug logging function in the stack, we’re 
currently experimenting with using `LogLevel INFO` to try and isolate the issue.

  I am attaching the backtrace. I could provide the full dump file,
  although I am hesitant due to the possibility of private keys or other
  sensitive information leaking.

  # apt-cache policy openssh-server
  openssh-server:
Installed: 1:8.2p1-4ubuntu0.9
Candidate: 1:8.2p1-4ubuntu0.9
Version table:
   *** 1:8.2p1-4ubuntu0.9 500
  500 http://mirrors.storpool.com/ubuntu/archive focal-updates/main 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:8.2p1-4 500
  500 http://mirrors.storpool.com/ubuntu/archive focal/main amd64 
Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Package: openssh-server 1:8.2p1-4ubuntu0.9
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-128.144-generic 5.4.210
  Tags:  focal
  Uname: Linux 5.4.0-128-generic x86_64
  UpgradeStatus: Upgraded to focal on 2021-01-13 (1030 days ago)
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2043114/+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 2043414] Re: Defaults to printing only 1 copy regardless

[Rico Tzschichholz]

** Package changed: libreoffice (Ubuntu) => cups (Ubuntu)

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

Title:
  Defaults to printing only 1 copy regardless

Status in cups package in Ubuntu:
  New

Bug description:
  Using calc every time I select 2 under "number of copies" (under
  print) only 1 physical copy gets printed.

  (Just tested using librewolf and the problem is the same so bug
  reporting was done under wrong package :()

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: libreoffice-calc 4:7.6.2-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Mon Nov 13 14:14:20 2023
  InstallationDate: Installed on 2023-04-14 (213 days ago)
  InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2043414/+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 2043414] [NEW] Defaults to printing only 1 copy regardless

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Using calc every time I select 2 under "number of copies" (under print)
only 1 physical copy gets printed.

(Just tested using librewolf and the problem is the same so bug
reporting was done under wrong package :()

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libreoffice-calc 4:7.6.2-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Mon Nov 13 14:14:20 2023
InstallationDate: Installed on 2023-04-14 (213 days ago)
InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
SourcePackage: libreoffice
UpgradeStatus: Upgraded to mantic on 2023-10-13 (31 days ago)

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


** Tags: amd64 apport-bug mantic
-- 
Defaults to printing only 1 copy regardless
https://bugs.launchpad.net/bugs/2043414
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to cups 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 412195] Re: ttf-tahoma-replacement makes some web-sites look ugly

[Gunnar Hjalmarsson]

On 2023-11-13 18:44, Marius Gedminas wrote:
> Debian reverted the change to isolate these low quality fonts from the
> rest of the system in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883973, and now this
> bug is back in Ubuntu 23.10.

Good catch! That Debian bug was filed in 2017, and "the fix" of it was
uploaded in Ubuntu here:

https://launchpad.net/ubuntu/+source/wine/8.0.1~repack-2

So: Some users like that the .ttf files in fonts-wine are treated as
system fonts, and some users dislike it. If you dislike it, please
submit a Debian bug and request that "the fix" of
 gets reverted. Given the subjective
nature of the issue, it would not make sense to change it back in Ubuntu
only.

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

Title:
  ttf-tahoma-replacement makes some web-sites look ugly

Status in fontconfig package in Ubuntu:
  Invalid
Status in wine1.2 package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: wine1.2

  This font package is good for wine 1.2; however, it also makes sites
  look ugly in Firefox and other browsers. I had to manually remove the
  fonts from /usr/share/fonts/ to rectfiy this, because removing the
  package through apt would have made me remove wine 1.2 and I didn't
  want that.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Aug 12 00:23:40 2009
  DistroRelease: Ubuntu 9.10
  Package: ttf-tahoma-replacement 1.1.27-0ubuntu1
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
  SourcePackage: wine1.2
  Uname: Linux 2.6.31-5-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/412195/+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 412195] Re: ttf-tahoma-replacement makes some web-sites look ugly

[BloodyIron]

Re-opening a bug that's of the same nature, how exactly is that
unacceptable? The version numbers may be different but it very much is
relevant to the topic. It's a regression, from what I read of the
situation, which warrants re-opening. Age is not relevant IMO. I do
agree with the premise of keeping tidy/clean bug reports and the sort,
but that can also include re-opening items due to regression too :^).

Besides, opening a new issue would make it a duplicate from what I can
tell ;)

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

Title:
  ttf-tahoma-replacement makes some web-sites look ugly

Status in fontconfig package in Ubuntu:
  Invalid
Status in wine1.2 package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: wine1.2

  This font package is good for wine 1.2; however, it also makes sites
  look ugly in Firefox and other browsers. I had to manually remove the
  fonts from /usr/share/fonts/ to rectfiy this, because removing the
  package through apt would have made me remove wine 1.2 and I didn't
  want that.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Aug 12 00:23:40 2009
  DistroRelease: Ubuntu 9.10
  Package: ttf-tahoma-replacement 1.1.27-0ubuntu1
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
  SourcePackage: wine1.2
  Uname: Linux 2.6.31-5-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/412195/+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 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)

[Heitor Alves de Siqueira]

Validated according to test case from description. No error messages
shown, and networking has been correctly configured.

root@halves-lp1907878-j:~# dpkg -l | grep ifupdown
ii  ifupdown 0.8.36+nmu1ubuntu3.1   
 amd64high level tools to configure network interfaces

root@halves-lp1907878-j:~# ifdown enp5s0; ifup enp5s0
Killed old client process
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/enp5s0/00:16:3e:a6:40:b0
Sending on   LPF/enp5s0/00:16:3e:a6:40:b0
Sending on   Socket/fallback
DHCPRELEASE of 10.125.177.48 on enp5s0 to 10.125.177.1 port 67 (xid=0x66ead755)
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/enp5s0/00:16:3e:a6:40:b0
Sending on   LPF/enp5s0/00:16:3e:a6:40:b0
Sending on   Socket/fallback
DHCPDISCOVER on enp5s0 to 255.255.255.255 port 67 interval 3 (xid=0x58e2)
DHCPOFFER of 10.125.177.48 from 10.125.177.1
DHCPREQUEST for 10.125.177.48 on enp5s0 to 255.255.255.255 port 67 
(xid=0xe258)
DHCPACK of 10.125.177.48 from 10.125.177.1 (xid=0x58e2)
bound to 10.125.177.48 -- renewal in 1555 seconds.


** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy

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

Title:
  wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]:
  /etc/network/if-up.d/resolved: 12: mystatedir: not found)

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Jammy:
  Fix Committed

Bug description:
  Syslog error:

     nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir:
  not found

  I think it's because of this line:

    if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then
    mystatedir statedir ifindex interface <- this 
is interpreted as a 'mystatedir' command and fails

    interface=$IFACE
    if [ ! "$interface" ]; then

  Perhaps the intention was to 'export mystatedir statedir ...'

  SRU for Jammy:

  [ Impact ]

 * /etc/network/if-{up,down}.d/resolved have a mistype:
 
 mystatedir statedir ifindex interface
 
 And when this line is executed, mystatedir is not found (not a valid 
command)
 and it generates an error log in /var/log/syslog and the terminal output. 
 It's not fatal, and the rest of the code gets executed, but it generates 
the
 message.
 
 # ifup ens3
 /etc/network/if-up.d/resolved: 12: mystatedir: not found

 # ifdown ens3
 /etc/network/if-down.d/resolved: 12: mystatedir: not found 
 
 The fix accepted in kinetic is only to remove this line. The same fix can 
be
 applied to Jammy.
 
  [ Test Plan ]

 With the new package installed, remove netplan configuration and add a 
valid
 /etc/network/interfaces file and then use the commands:
 
 # ifdown 
 # ifup 
 
 And confirm the messages are not displayed and the network configuration
 succeeds.
 
  [ Where problems could occur ]

 If mystatedir would be a valid command or function, which is not the case,
 that could break the script.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878/+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 412195] Re: ttf-tahoma-replacement makes some web-sites look ugly

[Gunnar Hjalmarsson]

@Jaromir, @Bloodyiron: This bug was closed more than a decade ago.
Please don't waste time with adding new comments here.

If you see issues (beyond personal preferences) with fonts-wine, please
submit a new bug:

ubuntu-bug wine

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

Title:
  ttf-tahoma-replacement makes some web-sites look ugly

Status in fontconfig package in Ubuntu:
  Invalid
Status in wine1.2 package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: wine1.2

  This font package is good for wine 1.2; however, it also makes sites
  look ugly in Firefox and other browsers. I had to manually remove the
  fonts from /usr/share/fonts/ to rectfiy this, because removing the
  package through apt would have made me remove wine 1.2 and I didn't
  want that.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Aug 12 00:23:40 2009
  DistroRelease: Ubuntu 9.10
  Package: ttf-tahoma-replacement 1.1.27-0ubuntu1
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
  SourcePackage: wine1.2
  Uname: Linux 2.6.31-5-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/412195/+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 412195] Re: ttf-tahoma-replacement makes some web-sites look ugly

[Marius Gedminas]

Debian reverted the change to isolate these low quality fonts from the
rest of the system in https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=883973, and now this bug is back in Ubuntu 23.10.

** Bug watch added: Debian Bug tracker #883973
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883973

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

Title:
  ttf-tahoma-replacement makes some web-sites look ugly

Status in fontconfig package in Ubuntu:
  Invalid
Status in wine1.2 package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: wine1.2

  This font package is good for wine 1.2; however, it also makes sites
  look ugly in Firefox and other browsers. I had to manually remove the
  fonts from /usr/share/fonts/ to rectfiy this, because removing the
  package through apt would have made me remove wine 1.2 and I didn't
  want that.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Aug 12 00:23:40 2009
  DistroRelease: Ubuntu 9.10
  Package: ttf-tahoma-replacement 1.1.27-0ubuntu1
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
  SourcePackage: wine1.2
  Uname: Linux 2.6.31-5-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/412195/+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 1715749] Re: Intermittent black screen on HP EliteBook 840 G1

[Michael von Glasow]

I still have the HP 840 G1, currently on 22.04. I’ll keep an eye on the
black screen issue and will report back as soon as it happens again.

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

Title:
  Intermittent black screen on HP EliteBook 840 G1

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Once every couple hours, the internal laptop display goes black for a
  few seconds.

  This was reproducible:
  + With the laptop connected to a port replicator and the external display 
connected into the port replicator DP port via DP-DVI adapter. The external 
display remains on during this time.
  + With the laptop not connected into a port replicator but connected to an 
external display. The external display remains on during this time.
  + With the laptop not connected to either a port replicator or an external 
display.

  The hard disk was originally installed with Ubuntu MATE 14.10 in a HP
  EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and
  finally moved to the EliteBook 840 G1. The problem started immediately
  after the drive move.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Sep  8 00:53:24 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-09 (1002 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
  InstallationDate: Installed on 2014-12-09 (1158 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-112-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.37
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: CNU407CM0V
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715749/+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 412195] Re: ttf-tahoma-replacement makes some web-sites look ugly

[BloodyIron]

Removing that package "fonts-wine" (not purge) and rebooting, the fonts
used by websites (that were known to use the problematic fonts) look
actually good now!

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

Title:
  ttf-tahoma-replacement makes some web-sites look ugly

Status in fontconfig package in Ubuntu:
  Invalid
Status in wine1.2 package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: wine1.2

  This font package is good for wine 1.2; however, it also makes sites
  look ugly in Firefox and other browsers. I had to manually remove the
  fonts from /usr/share/fonts/ to rectfiy this, because removing the
  package through apt would have made me remove wine 1.2 and I didn't
  want that.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Aug 12 00:23:40 2009
  DistroRelease: Ubuntu 9.10
  Package: ttf-tahoma-replacement 1.1.27-0ubuntu1
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
  SourcePackage: wine1.2
  Uname: Linux 2.6.31-5-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/412195/+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 412195] Re: ttf-tahoma-replacement makes some web-sites look ugly

[BloodyIron]

I have the same issue as Jaromir Obr and I'm about to try to remove the
fonts-wine package. But I game heavily so I'm hoping this doesn't break
my gaming. It's absurd that such a package would lead to horrible web
rendering, and this sure has been a doosie to nail down! Thanks Jaromir
for your investigation :)

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

Title:
  ttf-tahoma-replacement makes some web-sites look ugly

Status in fontconfig package in Ubuntu:
  Invalid
Status in wine1.2 package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: wine1.2

  This font package is good for wine 1.2; however, it also makes sites
  look ugly in Firefox and other browsers. I had to manually remove the
  fonts from /usr/share/fonts/ to rectfiy this, because removing the
  package through apt would have made me remove wine 1.2 and I didn't
  want that.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Aug 12 00:23:40 2009
  DistroRelease: Ubuntu 9.10
  Package: ttf-tahoma-replacement 1.1.27-0ubuntu1
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
  SourcePackage: wine1.2
  Uname: Linux 2.6.31-5-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/412195/+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 2039235] Re: gnome-online-accounts -> when signing into google account, infinite loading after entering password

[Felix Stoltenberg]

I also have a YubiKey on my Google account. However, I just wanted to
try the suggested workaround, BUT IT JUST WORKED WITHOUT THE WORKAROUND!

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

Title:
  gnome-online-accounts -> when signing into google account, infinite
  loading after entering password

Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  1) What you expected to happen
  - sign in is successful, which will allow google services to populate the 
appropriate applications (calendar, mail, google drive)

  2) What actually happened
  - sign in hangs infinitely after entering the password
  - the process is able to detect that the password is correct or incorrect. 
When entering an incorrect password, it will correctly and quickly complain 
that the password is incorrect. When entering the correct password, the bug 
will occur.

  3) Steps to reproduce
    a) start the program
    b) select online accounts
    c) select google
    d) enter email
    e) enter password
    f) loads forever

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-online-accounts 3.48.0-2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 22:27:59 2023
  InstallationDate: Installed on 2023-10-12 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

  Hardware info (not sure if relevant):
  cpu: intel
  gpu: nvidia (driver version: "Using NVIDIA driver metapackage from 
nvidia-driver-535(proprietary, tested)")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2039235/+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 2043321] Re: intel ekran kartı çalışmıyor

[Paul White]

** Description changed:

  intel ekran kartı çalışmıyor hatalı sürücüler var
+ 
+ Google translates as:
+ Intel graphics card is not working, there are faulty drivers
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 12 18:43:17 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
-  Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) 
(prog-if 00 [VGA controller])
-Subsystem: Dell Iris Plus Graphics G1 (Ice Lake) [1028:09e8]
+  Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) 
(prog-if 00 [VGA controller])
+    Subsystem: Dell Iris Plus Graphics G1 (Ice Lake) [1028:09e8]
  InstallationDate: Installed on 2023-11-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Dell Inc. Inspiron 14 5401
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=tr_TR.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=tr_TR.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-36-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2023
  dmi.bios.release: 1.25
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.25.0
  dmi.board.name: 06DNFY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.25.0:bd09/19/2023:br1.25:svnDellInc.:pnInspiron145401:pvr:rvnDellInc.:rn06DNFY:rvrA02:cvnDellInc.:ct10:cvr:sku09E8:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 14 5401
  dmi.product.sku: 09E8
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

** Summary changed:

- intel ekran kartı çalışmıyor
+ intel ekran kartı çalışmıyor (Intel graphics card not working)

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

Title:
  intel ekran kartı çalışmıyor (Intel graphics card not working)

Status in xorg package in Ubuntu:
  New

Bug description:
  intel ekran kartı çalışmıyor hatalı sürücüler var

  Google translates as:
  Intel graphics card is not working, there are faulty drivers

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 12 18:43:17 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) 
(prog-if 00 [VGA controller])
     Subsystem: Dell Iris Plus Graphics G1 (Ice Lake) [1028:09e8]
  InstallationDate: Installed on 2023-11-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Dell Inc. Inspiron 14 5401
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=tr_TR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-36-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2023
  dmi.bios.release: 1.25
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.25.0
  dmi.board.name: 06DNFY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.25.0:bd09/19/2023:br1.25:svnDellInc.:pnInspiron145401:

[Touch-packages] [Bug 2043255] Re: Wayland user session terminates when screen is disabled on inactivity

[Paul White]

** Package changed: xorg (Ubuntu) => wayland (Ubuntu)

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

Title:
  Wayland user session terminates when screen is disabled on inactivity

Status in wayland package in Ubuntu:
  New

Bug description:
  Reproducibly, the user is logged out the moment the screen gets
  disabled due to inactivity. Can be worked around by disabling the
  "screen disabling on inactivity" feature in the system settings.

  Issue started after upgrade from 23.04 to 23.10. Wayland is used.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 11 09:21:02 2023
  DistUpgraded: 2023-11-03 18:23:57,803 DEBUG icon theme changed, re-reading
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Lucienne [17aa:5097]
  InstallationDate: Installed on 2021-08-27 (806 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=86fa7801-2441-4de0-bdff-28c460a157ee ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to mantic on 2023-11-03 (8 days ago)
  dmi.bios.date: 05/17/2021
  dmi.bios.release: 1.6
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1OET27W (1.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20YHS00A00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1OET27W(1.06):bd05/17/2021:br1.6:efr1.6:svnLENOVO:pn20YHS00A00:pvrThinkPadE15Gen3:rvnLENOVO:rn20YHS00A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20YH_BU_Think_FM_ThinkPadE15Gen3:
  dmi.product.family: ThinkPad E15 Gen 3
  dmi.product.name: 20YHS00A00
  dmi.product.sku: LENOVO_MT_20YH_BU_Think_FM_ThinkPad E15 Gen 3
  dmi.product.version: ThinkPad E15 Gen 3
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.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-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2043255/+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 1715749] Re: Intermittent black screen on HP EliteBook 840 G1

[Paul White]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

Comments #50 and #51 suggest that this issue may have been fixed in a
recent release of Ubuntu.

Does anyone when using the hardware that was being used when making the
initial report still experience the reported issue?


** Changed in: xorg (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Intermittent black screen on HP EliteBook 840 G1

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Once every couple hours, the internal laptop display goes black for a
  few seconds.

  This was reproducible:
  + With the laptop connected to a port replicator and the external display 
connected into the port replicator DP port via DP-DVI adapter. The external 
display remains on during this time.
  + With the laptop not connected into a port replicator but connected to an 
external display. The external display remains on during this time.
  + With the laptop not connected to either a port replicator or an external 
display.

  The hard disk was originally installed with Ubuntu MATE 14.10 in a HP
  EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and
  finally moved to the EliteBook 840 G1. The problem started immediately
  after the drive move.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Sep  8 00:53:24 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-09 (1002 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
  InstallationDate: Installed on 2014-12-09 (1158 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-112-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.37
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: CNU407CM0V
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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


-- 
Mailing list: https://

[Touch-packages] [Bug 1592544] Re: ubuntu is using gallium graphics instead of intel graphics

[Paul White]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

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

Do you still see a problem related to the one that was reported when
using a currently supported version of  Ubuntu?

If so, please let us know which currently supported releases(s) are
affected otherwise this bug report can be left to expire in
approximately 60 days time.

Thank you for helping make Ubuntu better.

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

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

Title:
  ubuntu is using gallium graphics instead of intel graphics

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  xorg file empty, I tried to uninstall the gallium drivers but it
  didn't work

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.27  Thu Jun  9 18:53:27 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1)
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Jun 14 21:50:15 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-22-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   nvidia-367, 367.27, 4.4.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:05fe]
 Subsystem: Dell GK107M [GeForce GT 750M] [1028:05fe]
  InstallationDate: Installed on 2016-04-25 (50 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. XPS 15 9530
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed 
root=UUID=f565161c-e76f-4b59-b989-60ea2a0b51a6 ro nomodeset nomodeset 
nouveau.modeset=0
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: XPS 15 9530
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd07/30/2015:svnDellInc.:pnXPS159530:pvrA09:rvnDellInc.:rnXPS159530:rvrA09:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 15 9530
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Jun 14 21:48:10 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1592544/+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 2043393] [NEW] Report.get_logind_session fails to determine session on cgroup2 systems

[Benjamin Drung]

Public bug reported:

Ubuntu >= 22.04 uses only cgroup2 (Ubuntu 20.04 used both and Ubuntu
18.04 only cgroup version 1). Report.get_logind_session will fail to
determine the logind session and always return None if only cgroup2 is
used.

get_logind_session searches for cgroup lines with "name=systemd:" and
then extracts the session from "/session-". This worked in Ubuntu 16.04
but started failing in 18.04.

Content of /proc/self/cgroup when printed from a terminal inside a
Ubuntu desktop session:

Ubuntu 16.04 (xenial)
-

```
12:cpuset:/
11:perf_event:/
10:pids:/user.slice/user-1000.slice
9:blkio:/
8:hugetlb:/
7:net_cls,net_prio:/
6:cpu,cpuacct:/
5:devices:/user.slice
4:freezer:/
3:rdma:/
2:memory:/
1:name=systemd:/user.slice/user-1000.slice/session-c1.scope
```

Ubuntu 18.04 (bionic)
-

```
12:freezer:/
11:net_cls,net_prio:/
10:memory:/
9:rdma:/
8:cpu,cpuacct:/
7:devices:/user.slice
6:perf_event:/
5:cpuset:/
4:pids:/user.slice/user-1000.slice/user@1000.service
3:hugetlb:/
2:blkio:/
1:name=systemd:/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service
0::/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service
```

Ubuntu 20.04 (focal)
-

```
13:memory:/user.slice/user-1000.slice/user@1000.service
12:perf_event:/
11:misc:/
10:pids:/user.slice/user-1000.slice/user@1000.service
9:hugetlb:/
8:cpuset:/
7:blkio:/
6:devices:/user.slice
5:cpu,cpuacct:/
4:freezer:/
3:rdma:/
2:net_cls,net_prio:/
1:name=systemd:/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope
0::/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope
```

Ubuntu 22.04 (jammy)
-

```
0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-0c3f8b02-b112-4cab-accc-764cbb223bac.scope
```

** Affects: apport
 Importance: Undecided
 Status: New

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

** Also affects: apport
   Importance: Undecided
   Status: New

** Description changed:

  Ubuntu >= 22.04 uses only cgroup2 (Ubuntu 20.04 used both and Ubuntu
  18.04 only cgroup version 1). Report.get_logind_session will fail to
  determine the logind session and always return None if only cgroup2 is
  used.
+ 
+ get_logind_session searches for cgroup lines with "name=systemd:" and
+ then extracts the session from "/session-". This worked in Ubuntu 16.04
+ but started failing in 18.04.
  
  Content of /proc/self/cgroup when printed from a terminal inside a
  Ubuntu desktop session:
  
  Ubuntu 16.04 (xenial)
  -
  
  ```
  12:cpuset:/
  11:perf_event:/
  10:pids:/user.slice/user-1000.slice
  9:blkio:/
  8:hugetlb:/
  7:net_cls,net_prio:/
  6:cpu,cpuacct:/
  5:devices:/user.slice
  4:freezer:/
  3:rdma:/
  2:memory:/
  1:name=systemd:/user.slice/user-1000.slice/session-c1.scope
  ```
  
  Ubuntu 18.04 (bionic)
  -
  
  ```
  12:freezer:/
  11:net_cls,net_prio:/
  10:memory:/
  9:rdma:/
  8:cpu,cpuacct:/
  7:devices:/user.slice
  6:perf_event:/
  5:cpuset:/
  4:pids:/user.slice/user-1000.slice/user@1000.service
  3:hugetlb:/
  2:blkio:/
  
1:name=systemd:/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service
  0::/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service
  ```
  
  Ubuntu 20.04 (focal)
  -
  
  ```
  13:memory:/user.slice/user-1000.slice/user@1000.service
  12:perf_event:/
  11:misc:/
  10:pids:/user.slice/user-1000.slice/user@1000.service
  9:hugetlb:/
  8:cpuset:/
  7:blkio:/
  6:devices:/user.slice
  5:cpu,cpuacct:/
  4:freezer:/
  3:rdma:/
  2:net_cls,net_prio:/
  
1:name=systemd:/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope
  
0::/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope
  ```
  
  Ubuntu 22.04 (jammy)
  -
  
  ```
  
0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-0c3f8b02-b112-4cab-accc-764cbb223bac.scope
  ```

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

Title:
  Report.get_logind_session fails to determine session on cgroup2
  systems

Status in Apport:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  Ubuntu >= 22.04 uses only cgroup2 (Ubuntu 20.04 used both and Ubuntu
  18.04 only cgroup version 1). Report.get_logind_session will fail to
  determine the logind session and always return None if only cgroup2 is
  used.

  get_logind_session searches for cgroup li

[Touch-packages] [Bug 2042710] Re: Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14, 1) due to missing kernel modules in initramfs

[Benjamin Drung]

Terence, can you verify that intel_lpss_pci is needed and that
spi_pxa2xx_platform is not enough?

I found the relevant difference between Fedora and Ubuntu: Fedora builds
intel_lpss_pci into the kernel:

```
$ podman run -it fedora:latest /bin/bash
[root@a0c841a1d76f /]# dnf install kernel-core
[root@a0c841a1d76f /]# grep INTEL_LPSS_PCI 
/lib/modules/6.5.11-300.fc39.x86_64/config 
CONFIG_MFD_INTEL_LPSS_PCI=y
```

but Ubuntu builds it as module:

```
$ grep INTEL_LPSS_PCI /boot/config-6.5.0-10-generic 
CONFIG_MFD_INTEL_LPSS_PCI=m
```

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

Title:
  Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14,1)
  due to missing kernel modules in initramfs

Status in initramfs-tools package in Ubuntu:
  Triaged
Status in initramfs-tools source package in Mantic:
  New

Bug description:
  I have a MacBook Pro 2017 (MacBookPro14,1) with an encrypted root
  partition, which I decrypt via passphrase during boot, at the "Please
  unlock disk nvme0n1p4_crypt" prompt.

  Using 23.04 "Lunar" this worked fine. However after upgrading to 23.10
  "Mantic", the built-in keyboard doesn't work for entering the
  passphrase.

  Quickest workaround: plug in a USB keyboard for entering the
  passphrase.

  Workaround: add the following modules to "/etc/initramfs-
  tools/modules":

  spi_pxa2xx_platform
  intel_lpss_pci

  ... then "sudo update-initramfs -u".

  I found that both kernel modules were required to get the keyboard
  recognised in initramfs.

  I did a bit of digging into what changed for 23.10. It could
  potentially (?) be commit 2df78bbb143884b9601a32608e12e43d40ccb0b0 "Do
  not install ARM/RISCV specific modules on other architectures".

  I had a look into how dracut handles it. Turns out that they
  specifically include "spi_pxa2xx_platform" after reporting a similar
  bug report in Fedora:
  https://bugzilla.redhat.com/show_bug.cgi?id=2166209

  I don't know how (if?) they handle the 2nd module, "intel_lpss_pci".

  Anyway, I don't need an immediate fix since the workaround works for
  me. Just posting this for further investigation, and for any other
  MacBook Pro users in the same situation. Thanks for working on Ubuntu,
  I think you're all amazing!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2042710/+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