[Touch-packages] [Bug 2062082] [NEW] 24.04 Wayland vs Nautilus performance problem

[Sam Bee]

Public bug reported:

Apologies if I have misfiled this bug - this is a report of an issue
affecting Wayland in Ubuntu 24.04 beta.

Using 24.04 beta logging in with Wayland. Nautilus has very significant
performance issues. Doesn't happen when logging in with Xorg instead of
Wayland.

Opening Nautilus windows - including normal windows navigation, and the
file download location dialogue in things like Chrome - extremely slow.
Takes approx. 10 seconds to process user double clicking to open folder.
Attempting to drag folder across screen usually doesn't work, or takes a
very long time.

Not very skilled at debugging, but programmes like Gimp, which has its
own built-in folder explorer for choosing a location to save an image,
do not have this problem. Ubuntu 24.04 with X does not have this
problem. No performance issues have been noticed with folder navigation,
stat'ing files etc. over the command line. It is only nautilus and
Wayland that give me this issue, so I suspect it is not an issue with my
SSD.

The following output was observed when starting nautilus over the
command line:

/home/me/ $ nautilus .
** Message: 23:43:50.560: Connecting to org.freedesktop.Tracker3.Miner.Files
libEGL warning: egl: failed to create dri2 screen


After approx. 10 seconds, the folder opened on screen. I double clicked on a 
sub directory, and it took about 9 seconds to open.

I have attempted to show that this is not an issue with my SSD here:

/home/me/ $ date; cd workspace/; touch foo.txt; ls foo*; cd ../; date;
Wed Apr 17 11:58:16 PM BST 2024
foo.txt
Wed Apr 17 11:58:16 PM BST 2024

As you can see, no unusual slowdown was observed.

Obtaining the following setting for my bug report, I note that the
'Settings' GUI utility is among the areas affect by my very significant
system slowdown. I have copied some details about my system including
its graphics card in case that helps.

# System Details Report
---

## Report details
- **Date generated:**  2024-04-17 23:59:54

## Hardware Information:
- **Hardware Model:**  ASUS ROG STRIX B550-F GAMING
- **Memory:**  32.0 GiB
- **Processor:**   AMD Ryzen™ 7 5800X × 16
- **Graphics:**zink Vulkan 1.3(NVIDIA 
GeForce GTX 1050 Ti (NVIDIA_PROPRIETARY))
- **Disk Capacity:**   2.0 TB

## Software Information:
- **Firmware Version:**2006
- **OS Name:** Ubuntu Noble Numbat 
(development branch)
- **OS Build:**(null)
- **OS Type:** 64-bit
- **GNOME Version:**   46
- **Windowing System:**Wayland
- **Kernel Version:**  Linux 6.8.0-22-generic

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..09.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  545.29.06  Thu Nov 16 01:59:08 
UTC 2023
 GCC version:
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 17 23:44:47 2024
DistUpgraded: 2024-04-11 13:09:51,904 DEBUG migrateToDeb822Sources()
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82]
InstallationDate: Installed on 2024-04-11 (6 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: ASUS System Product Name
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to noble on 2024-04-11 (6 days ago)
dmi.bios.date: 03/19/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2006
dmi.board.asset.tag: Default string
dmi.board.name: ROG STRIX B550-F GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x

[Touch-packages] [Bug 2044664] [NEW] HDMI plugin after boot, but display can't work

[sam shen]

Public bug reported:

[Summary]
HDMI plugin but display can't work after boot under HDMI only display
 
[Reproduce]
1. Set display configuration as single HDMI only
2. Boot into the system without plugging HDMI cable
3. Ensure system is booted (check it by debug console), then plug HDMI cable
4. Check the image on HDMI monitor
 
[Expected result]
Ubuntu desktop should be shown on HDMI monitor
 
[Actual result]
Ubuntu desktop was not shown on HDMI monitor
 
[Fail Rate]
100%
 
[Additional information]
Platform: Mediatek Genio1200 EVK
Ubuntu Version: 22.04.2 LTS
Image: baoshan-classic-desktop-2204-x01-20231005-133.tar.xz

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  HDMI plugin after boot, but display can't work

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  [Summary]
  HDMI plugin but display can't work after boot under HDMI only display
   
  [Reproduce]
  1. Set display configuration as single HDMI only
  2. Boot into the system without plugging HDMI cable
  3. Ensure system is booted (check it by debug console), then plug HDMI cable
  4. Check the image on HDMI monitor
   
  [Expected result]
  Ubuntu desktop should be shown on HDMI monitor
   
  [Actual result]
  Ubuntu desktop was not shown on HDMI monitor
   
  [Fail Rate]
  100%
   
  [Additional information]
  Platform: Mediatek Genio1200 EVK
  Ubuntu Version: 22.04.2 LTS
  Image: baoshan-classic-desktop-2204-x01-20231005-133.tar.xz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/2044664/+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 1957816] Re: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed

[Sam Wise]

Same issue here.  AMD gpu, two 4k monitors, one on Display Port @ 60Hz
and The other on HDMI @ 60Hz with audio playback high pitched and
increased speed. Lowering the HDMI refresh rate to 30Hz fixes the audio.

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

Title:
  Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double
  playback speed

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I have a desktop computer with a 60Hz 4K display connected through Display 
Port. The display is a ThinkVision X1 with built in audio. With the Display 
Port cable I am then able to output sound from the monitor and this works 
without any issues.
  I have now added a 4K Samsung television through HDMI to the same GPU, which 
also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only 
do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear 
however, that when it is set to 60Hz in Wayland, the animation on the 
television is much more smooth. 

  The problem is that whenever I set the television to 60Hz, the playback of 
any sound is both high pitched and faster than normal. If I play a video in 
YouTube, the video appears to playback about twice as fast as normal and and 
very high pitched sound (everyone sounds like chipmunks). This is the case on 
the entire system (also when playing the video or any other sounds on the X1 
display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz 
again does everything play and sound normal again. 
  It is only the playback of media that is doubled in speed. Everything else 
(animations, mouse, etc.) is still behaving as normal.

  If I change audio output to the ThinkVision X1 (or something else) at
  60Hz while also being connected to the television at 60Hz, the audio
  stays high pitched and sped up.

  If I unplug the main display, ThinkVision X1, then the playback of
  media on the television becomes normal.

  I have tried with different +100 USD HDMI cables, that are all rated
  as HDMI 2.0 and the behavior stays the same.

  My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the
  behavior was the same.

  I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI).

  As mentioned I cannot test it in Xorg, but that is only because it
  does not allow me to set the refresh rate to 60Hz.

  I am uncertain whether this is related to MESA, Pulseaudio or maybe
  Mutter/Wayland?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1957816/+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 1969709] Re: libreoffice font selection unusably slow

[Sam Townsend]

This is still a problem :(

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

Title:
  libreoffice font selection unusably slow

Status in LibreOffice:
  Won't Fix
Status in fontconfig package in Ubuntu:
  Incomplete
Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Trying to scroll through the font list in the menu bar, I experience
  an unacceptable degree of lagging. Just popping up the dropdown list
  takes 7-10 seconds and the system takes the same amount of time to
  respond to perform individidual scrolling gestures. The CPU jumps to
  100% and the whole system becomes unresponsive.

  I have tried deb, snap and even the packages offered on the site of
  the LibreOffice project. They all manifest the same behaviour. The
  only thing that works is disabling font previews. I have downgraded to
  7.2 for now, which appears to be unaffected.

  I have contacted the LibreOffice team and they tell me that this
  should be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is
  shipping 2.13...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice-core 1:7.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 21 05:01:24 2022
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2022-03-27 (24 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1969709/+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 2020604] Re: After Mesa upgrades, Chrome won't show graphics

[Sam]

Following Timo's instructions, aptitude upgraded those two packages
(along with three additional packages aptitude auto-selected) on one
test system:

[UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.2 -> 
22.2.5-0ubuntu0.1~22.04.3
[UPGRADE] libgbm1:amd64 22.2.5-0ubuntu0.1~22.04.2 -> 22.2.5-0ubuntu0.1~22.04.3
[UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.2 -> 
22.2.5-0ubuntu0.1~22.04.3
[UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.2 -> 
22.2.5-0ubuntu0.1~22.04.3
[UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.2 -> 
22.2.5-0ubuntu0.1~22.04.3

Rebooted and tested Chrome.  No immediate issues, graphics work.  Will
keep testing.

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

Title:
  After Mesa upgrades, Chrome won't show graphics

Status in chromium-browser package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in chromium-browser source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Committed
Status in chromium-browser source package in Lunar:
  Invalid
Status in mesa source package in Lunar:
  New

Bug description:
  [Impact]
  After patching Mesa with some driver updates, Chromium/Brave started seeing 
corrupt graphics. This was due to GPU acceleration being enabled in the browser 
by default now, and the old GPU shader cache is invalid in some ways and the 
browser is not able to recognize that the driver has changed, since the 
upstream version string hasn't changed. This is shown for instance with 
'glxinfo -B' or under 'chrome:gpu' from the browser.

  The fix is to make the upstream VERSION to have the full packaging
  version, this will then be used for the core profile version string as
  well.

  
  [Test case]

  - run stock jammy, install brave-browser from brave.com, launch brave-
  browser, check that 'brave://gpu' shows things are accelerated, then
  exit the browser

  - enable proposed, install libgl1-mesa-dri et al

  - launch brave-browser again, verify that gfx are not corrupted and
  brave://gpu is showing acceration being used

  with the pulled update, graphics would be severely corrupted

  
  [Where things could go wrong]
  There could be apps that expect the Mesa version string to only contain 
a.b.c, and break in some ways when that's no longer the case.

  
  --

  After today's Ubuntu 22.04 Mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The Mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to Mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with Mesa or Chrome or specific machine
  graphics or an interaction between them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 2020604] Re: After Mesa upgrades, Chrome won't show graphics

[Sam]

OK just a question about pinning since we would prefer to minimize
changes to user systems.  When we follow the instructions from Steve's
message on:

 https://wiki.ubuntu.com/Testing/EnableProposed

which sets the pin priority for proposed to 400, the page says to run a
simulated apt upgrade to verify that no packages are scheduled for
upgrade.  However when we try that we see 11 upgrade-able packages.

We can get that number to 0 if we set the pin priority to something less
than that of /var/lib/dpkg/status, i.e., to something less than 100.
But is that correct?

If we comment out all the pin restrictions we see 44 proposed packages
scheduled for upgrade.  Is that because some of the proposed packages
aren't controlled by /var/lib/dpkg/status?

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

Title:
  After Mesa upgrades, Chrome won't show graphics

Status in chromium-browser package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in chromium-browser source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Committed
Status in chromium-browser source package in Lunar:
  Invalid
Status in mesa source package in Lunar:
  New

Bug description:
  [Impact]
  After patching Mesa with some driver updates, Chromium/Brave started seeing 
corrupt graphics. This was due to GPU acceleration being enabled in the browser 
by default now, and the old GPU shader cache is invalid in some ways and the 
browser is not able to recognize that the driver has changed, since the 
upstream version string hasn't changed. This is shown for instance with 
'glxinfo -B' or under 'chrome:gpu' from the browser.

  The fix is to make the upstream VERSION to have the full packaging
  version, this will then be used for the core profile version string as
  well.

  
  [Test case]

  - run stock jammy, install brave-browser from brave.com, launch brave-
  browser, check that 'brave://gpu' shows things are accelerated, then
  exit the browser

  - enable proposed, install libgl1-mesa-dri et al

  - launch brave-browser again, verify that gfx are not corrupted and
  brave://gpu is showing acceration being used

  with the pulled update, graphics would be severely corrupted

  
  [Where things could go wrong]
  There could be apps that expect the Mesa version string to only contain 
a.b.c, and break in some ways when that's no longer the case.

  
  --

  After today's Ubuntu 22.04 Mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The Mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to Mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with Mesa or Chrome or specific machine
  graphics or an interaction between them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 2020604] Re: After Mesa upgrades, Chrome won't show graphics

[Sam]

Okay we'll wait for a later build.

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

Title:
  After Mesa upgrades, Chrome won't show graphics

Status in chromium-browser package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in chromium-browser source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Committed
Status in chromium-browser source package in Lunar:
  Invalid
Status in mesa source package in Lunar:
  New

Bug description:
  [Impact]
  After patching Mesa with some driver updates, Chromium/Brave started seeing 
corrupt graphics. This was due to GPU acceleration being enabled in the browser 
by default now, and the old GPU shader cache is invalid in some ways and the 
browser is not able to recognize that the driver has changed, since the 
upstream version string hasn't changed. This is shown for instance with 
'glxinfo -B' or under 'chrome:gpu' from the browser.

  The fix is to make the upstream VERSION to have the full packaging
  version, this will then be used for the core profile version string as
  well.

  
  [Test case]

  - run stock jammy, install brave-browser from brave.com, launch brave-
  browser, check that 'brave://gpu' shows things are accelerated, then
  exit the browser

  - enable proposed, install libgl1-mesa-dri et al

  - launch brave-browser again, verify that gfx are not corrupted and
  brave://gpu is showing acceration being used

  with the pulled update, graphics would be severely corrupted

  
  [Where things could go wrong]
  There could be apps that expect the Mesa version string to only contain 
a.b.c, and break in some ways when that's no longer the case.

  
  --

  After today's Ubuntu 22.04 Mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The Mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to Mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with Mesa or Chrome or specific machine
  graphics or an interaction between them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 2020604] Re: After Mesa upgrades, Chrome won't show graphics

[Sam]

Thank you very much Steve (and Timo and everyone else that has helped).
We will test it on a few systems this weekend.

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

Title:
  After Mesa upgrades, Chrome won't show graphics

Status in chromium-browser package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in chromium-browser source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Committed
Status in chromium-browser source package in Lunar:
  Invalid
Status in mesa source package in Lunar:
  New

Bug description:
  [Impact]
  After patching Mesa with some driver updates, Chromium/Brave started seeing 
corrupt graphics. This was due to GPU acceleration being enabled in the browser 
by default now, and the old GPU shader cache is invalid in some ways and the 
browser is not able to recognize that the driver has changed, since the 
upstream version string hasn't changed. This is shown for instance with 
'glxinfo -B' or under 'chrome:gpu' from the browser.

  The fix is to make the upstream VERSION to have the full packaging
  version, this will then be used for the core profile version string as
  well.

  
  [Test case]

  - run stock jammy, install brave-browser from brave.com, launch brave-
  browser, check that 'brave://gpu' shows things are accelerated, then
  exit the browser

  - enable proposed, install libgl1-mesa-dri et al

  - launch brave-browser again, verify that gfx are not corrupted and
  brave://gpu is showing acceration being used

  with the pulled update, graphics would be severely corrupted

  
  [Where things could go wrong]
  There could be apps that expect the Mesa version string to only contain 
a.b.c, and break in some ways when that's no longer the case.

  
  --

  After today's Ubuntu 22.04 Mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The Mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to Mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with Mesa or Chrome or specific machine
  graphics or an interaction between them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 2020604] Re: After Mesa upgrades, Chrome won't show graphics

[Sam]

** Summary changed:

- After mesa upgrades, Chrome won't show graphics
+ After Mesa upgrades, Chrome won't show graphics

** Description changed:

- After today's Ubuntu 22.04 mesa upgrades many of our users reported
+ After today's Ubuntu 22.04 Mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).
  
- The mesa upgrades we installed were:
+ The Mesa upgrades we installed were:
  
  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  
  We documented the problem in AskUbuntu before we realized it was
- probably related to mesa, so wanted to link to that report here:
+ probably related to Mesa, so wanted to link to that report here:
  
  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi
  
  There are several useful pointers and bypasses listed in that AskUbuntu
  link (one being to remove affected users' GPUCache directories, which
  does not destroy their profiles and seems to work in many but not all
  cases).
  
- Not sure if this is an issue with mesa or Chrome or specific machine
+ Not sure if this is an issue with Mesa or Chrome or specific machine
  graphics or an interaction between them.

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

Title:
  After Mesa upgrades, Chrome won't show graphics

Status in chromium-browser package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  Triaged

Bug description:
  After today's Ubuntu 22.04 Mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The Mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to Mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with Mesa or Chrome or specific machine
  graphics or an interaction between them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 2020604] Re: After mesa upgrades, Chrome won't show graphics

[Sam]

** Description changed:

  After today's Ubuntu 22.04 mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).
  
  The mesa upgrades we installed were:
  
  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  
  We documented the problem in AskUbuntu before we realized it was
  probably related to mesa, so wanted to link to that report here:
  
  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi
  
- There is a bypass listed in that article.  Not sure if this is an issue
- with mesa or Chrome or specific machine graphics or an interaction
- between them.
+ There are several useful pointers and bypasses listed in that AskUbuntu
+ link (one being to remove affected users' GPUCache directories, which
+ does not destroy their profiles, and seems to work in many but not all
+ cases).
+ 
+ Not sure if this is an issue with mesa or Chrome or specific machine
+ graphics or an interaction between them.

** Description changed:

  After today's Ubuntu 22.04 mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).
  
  The mesa upgrades we installed were:
  
  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  
  We documented the problem in AskUbuntu before we realized it was
  probably related to mesa, so wanted to link to that report here:
  
  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi
  
  There are several useful pointers and bypasses listed in that AskUbuntu
  link (one being to remove affected users' GPUCache directories, which
- does not destroy their profiles, and seems to work in many but not all
+ does not destroy their profiles and seems to work in many but not all
  cases).
  
  Not sure if this is an issue with mesa or Chrome or specific machine
  graphics or an interaction between them.

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

Title:
  After mesa upgrades, Chrome won't show graphics

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  After today's Ubuntu 22.04 mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with mesa or Chrome or specific machine
  graphics or an interaction between them.

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


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

[Touch-packages] [Bug 382938] Re: ufw should be enabled by default

[Sam T]

I've been a Ubuntu user for 10 years and was astonished to learn today
that iptables just lets everything through by default on Ubuntu desktop.
I'm a grad student in a CS department at a university, and had to learn
this the hard way after one of the desktop machines in our lab was
compromised.

In our case, the breach was a result of three layers of failure:

1. Some past owner of the machine let Docker listen on 0.0.0.0:2375.
This is a really bad idea because it gives root access to anyone on the
same network, but unfortunately there are people on the web that
recommend doing this without explaining the ramifications. For instance,
here is someone recommending this as a workaround for a minor
configuration issue in the default Docker install, which could easily be
resolved without listening on a public interface:
https://gist.github.com/styblope/dc55e0ad2a9848f2cc3307d4819d819f

2. This insecure default could have been caught by an OS firewall, but
unfortunately the FW was disabled by default.

3. Even the above two holes could have been made slightly less severe
with NAT, or firewalling at the university level, but unfortunately our
university assigns every ethernet-connected machine a public IP and
allows all traffic in by default (except port 22, because 'security').

The machine was in this configuration for years until the campus
intrusion detection system noticed some suspicious traffic to the
machine, which prompted our discovery of the three issues above.

Hopefully it's clear from my explanation that the problem here was not
just UFW. Docker should never have been configured to listen on a public
interface. The university should probably not be letting random inbound
traffic to desktop machines by default (or should at least clearly
communicate that this is the case). The person who set up the desktop
should have realized they had to enable a firewall.

Nevertheless, I'm sharing this anecdote to illustrate that even fairly
sophisticated users can easily get burned by insecure configurations.
Having no firewall enabled by default makes this worse. The desktop in
this story was previously used by a research engineer and then a CS PhD
student. If they can't get it right, then what hope does the average
Ubuntu user have?

I'm sympathetic to the concerns raised above about unexpected config
changes. It would be unacceptable if an apt upgrade suddenly brought
down a web server or cut off ssh access. However, I expect there are
ways that the majority of Ubuntu users could be protected without
hurting running systems. For instance, you could enable ufw by default
in the Ubuntu Desktop install media.

--

Addendum: you may think "hah, what idiot would open up a remote root
access hole on 0.0.0.0?" Unfortunately, I've seen this as the *default*
configuration for lots of software that really has no need to listen on
public interfaces. The worst was a somewhat-popular scientific
visualization tool that had no authentication and allowed for remote
code execution by design. It's surprising how many developers don't
realize what a terrible idea this is, and ultimately their users suffer
for it.

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

Title:
  ufw should be enabled by default

Status in ufw:
  Invalid
Status in ufw package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: ufw

  ufw should be enabled by default in Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ufw/+bug/382938/+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 2006123] [NEW] package linux-image-5.15.0-50-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Sam Lay]

Public bug reported:

Upgrading packages

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.15.0-50-generic (not installed)
ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.25
AptOrdering:
 linux-image-5.15.0-56-generic:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Feb  1 22:54:34 2023
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2021-07-18 (568 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.9
SourcePackage: initramfs-tools
Title: package linux-image-5.15.0-50-generic (not installed) failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package linux-image-5.15.0-50-generic (not installed) failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Upgrading packages

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-50-generic (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.25
  AptOrdering:
   linux-image-5.15.0-56-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Feb  1 22:54:34 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-07-18 (568 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: initramfs-tools
  Title: package linux-image-5.15.0-50-generic (not installed) failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2006123/+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 2006124] [NEW] package linux-image-5.15.0-56-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Sam Lay]

Public bug reported:

Upgrading packages

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.15.0-56-generic (not installed)
ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.25
AptOrdering:
 linux-image-5.15.0-56-generic:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Feb  1 22:54:44 2023
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2021-07-18 (568 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.9
SourcePackage: initramfs-tools
Title: package linux-image-5.15.0-56-generic (not installed) failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package linux-image-5.15.0-56-generic (not installed) failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Upgrading packages

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-56-generic (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.25
  AptOrdering:
   linux-image-5.15.0-56-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Feb  1 22:54:44 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-07-18 (568 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: initramfs-tools
  Title: package linux-image-5.15.0-56-generic (not installed) failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Re: [Touch-packages] [Bug 2003756] Re: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142."

[Sam Hartman]

>>>>> "Sergio" == Sergio Durigan Junior <2003...@bugs.launchpad.net> writes:
Sergio> systemd-invoke will try to run systemctl like this:

Sergio> systemctl --quiet --system restart krb5-kdc.service

Sergio> which fails because of the problem mentioned above.

So, there was a bug that made its way to the Debian TC asking what the
behavior ought to be when a maintainer script tried to restart a unit
and the unit failed.
The conclusion of that bug was that there is no general
policy--sometimes you want the maintainer script to fail, sometimes you
do not.
At least that was my recollection.

krb5-kdc is a service where you probably don't want the unit
restarting/starting to be a failure to cause the maintainer script to
fail.
How to I explain that to debhelper?

--Sam

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

Title:
  Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute
  systemctl:  at /usr/bin/deb-systemd-invoke line 142."

Status in init-system-helpers package in Ubuntu:
  New
Status in krb5 package in Ubuntu:
  New

Bug description:
  I have a fresh install of Ubuntu Server 22.04.01 LTS.  After
  installing the server and running all updates, I run the following
  command:

  apt -y install slapd ldap-utils schema2ldif sasl2-bin
  libsasl2-modules-gssapi-mit krb5-kdc-ldap krb5-admin-server krb5-kdc

  This will be installing krb5-kdc 1.19.2-2.

  This is in preparation for setting up an OpenLDAP server, a Kerberos
  server with an LDAP backend, and saslauthd for pass-through
  authentication.  krb5-kdc was auto-selected when running the steps in
  the guide here in my development environment:
  https://ubuntu.com/server/docs/service-kerberos-with-openldap-backend
  When installing that, I get the following in the output:

  Setting up krb5-kdc (1.19.2-2) ...
  Created symlink /etc/systemd/system/multi-user.target.wants/krb5-kdc.service 
→ /lib/systemd/system/krb5-kdc.service.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.

  I do get the prompts for the realm, kdc, and admin server hostnames,
  and they are reflected in /etc/krb5.conf.  If I then run the
  following:

  dpkg-reconfigure krb5-kdc

  I am prompted for whether I want the package to create the Kerberos
  KDC configuration automatically, and when I say yes, it then repeats
  the following error:

  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.

  I cannot find any further debug in the syslog or anything to indicate
  what the root cause is; the list of packages here are all installed
  together on a separate development server where I experimented with
  the configuration I will be deploying here in production so I don't
  think it's incompatible packages in the install list, but I am open to
  feedback on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/2003756/+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 1918044] Re: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore

[Sam Brightman]

This release was made specifically to help out older LTS distributions
which cannot migrate to newer libgweather. What needs to be done to get
it into 20.04?

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

Title:
  (Update libgweather to 3.36.2) Weather forecast and info is not
  available anymore

Status in libgweather:
  Fix Released
Status in gnome-weather package in Ubuntu:
  Fix Released
Status in libgweather package in Ubuntu:
  Fix Released
Status in gnome-weather source package in Focal:
  Confirmed
Status in libgweather source package in Focal:
  Confirmed
Status in gnome-weather package in Fedora:
  New

Bug description:
  [Impact]

  The weather forecast is not available since one week now. Also, the
  weather info is gone from gnome-shell.

  The weather service provider retired their old API.
  
https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/

  https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS

  ==
  Version 3.36.2
  ==

  This version switches the yr.no backend to use met.no instead. Please note
  that this backport is only meant as a compatibility layer. Where at all
  possible, the newer libgweather 40 should be used as applications cannot
  fully comply with the met.no ToS otherwise.

  
  [Test case]

  - gnome-weather shows the weather forecast
  - gnome-shell shows the weather forecast in the calendar menu

  
  [Regression potential]

  - Weather forecast is totally broken now and can't be more broken.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  7 09:54:52 2021
  InstallationDate: Installed on 2020-04-26 (314 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: libgweather
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgweather/+bug/1918044/+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

Re: [Touch-packages] [Bug 1981697] Re: KDC: weak crypto in default settings

[Sam Hartman]

>>>>> "Marc" == Marc Deslauriers <1981...@bugs.launchpad.net> writes:

Marc> Oh, so it only copies the file over on new installs, that
Marc> makes sense, and could be easily changed in stable releases.

It's actually even less likely to cause problems than it might appear.
That config value should only be used by kdb5_util create.
Once /etc/krb5kdc/stash is created, I'd expect the encryption type in
that file will be used, and even if somehow kdc.conf were updated, it
would still continue to work.

We probably should start thinking about how to upgrade existing
databases, because we're going to want to do that before 3DES is removed
from the code.
That's going to be tricky because of the various replication and
database storage strategies.  For example a Freeipa database is handled
differently than a raw Kerberos database than an LDAP database.
But we don't need to solve any of that today, and whatever we can do to
make new realms work better will help that eventual upgrade process
along.

--Sam

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

Title:
  KDC: weak crypto in default settings

Status in krb5 package in Ubuntu:
  Confirmed
Status in krb5 package in Debian:
  Unknown

Bug description:
  Default setting in /etc/krb5kdc/kdc.conf, as installed from krb5-kdc in 
Ubuntu 22.04 Server:
  master_key_type = des3-hmac-sha1

  3DES was deprecated by NIST in 2017, i.e. give years ago! Reference:
  https://csrc.nist.gov/News/2017/Update-to-Current-Use-and-Deprecation-
  of-TDEA . This should not be a default since a very long time, and
  particularly not for new installations. If a compatibility with out-
  of-date installations is necessary, this should be explicitly made be
  the administrator.

  SHA-1 was deprecated as well, in 2011, i.e. eleven years ago!
  Reference:
  https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-131a.pdf
  .

  A reasonable default would probably be:
  master_key_type = aes256-cts-hmac-sha384-192

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: krb5-kdc 1.19.2-2
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jul 14 12:34:22 2022
  InstallationDate: Installed on 2022-05-30 (45 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IE.UTF-8
   SHELL=/bin/bash
  SourcePackage: krb5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1981697/+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 1976563] [NEW] All text and images in Gnome Shell are corrupted

[Sam Magura]

Public bug reported:

See attached screenshot.

The corrupted text and images are only appearing in the Ubuntu desktop
environment (like the login screen, dock, and the bar at top of the
screen). Applications like Nautilus, the Terminal app, and Chrome are
not affected.

Maybe an Nvidia issue?

I'm going to restart my PC which will probably fix the issue. I'll edit
this if the issue persists after the restart.

Edit: To anyone investigating this issue, I recommend looking at some of
the other issues I've reported recently. It seems like they could all be
connected somehow, with Nvidia as the common thread.


ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
Uname: Linux 5.15.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..06.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.73.05  Sat May  7 05:30:26 
UTC 2022
 GCC version:
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun  1 18:58:22 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus: nvidia/510.73.05, 5.15.0-33-generic, x86_64: installed (WARNING! 
Diff between built and installed module!) (WARNING! Diff between built and 
installed module!) (WARNING! Diff between built and installed module!) 
(WARNING! Diff between built and installed module!)
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 
3GB] [1462:3287]
InstallationDate: Installed on 2022-04-23 (39 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic 
root=UUID=c4ac1391-7d4e-4282-94ba-fbae3c4c044c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/25/2019
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F4
dmi.board.asset.tag: Default string
dmi.board.name: B450M DS3H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: B450M DS3H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
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

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


** Tags: amd64 apport-bug corruption jammy ubuntu

** Attachment added: "Screenshot from 2022-06-01 18-57-55.png"
   
https://bugs.launchpad.net/bugs/1976563/+attachment/5594368/+files/Screenshot%20from%202022-06-01%2018-57-55.png

** Description changed:

  See attached screenshot.
  
  The corrupted text and images are only appearing in the Ubuntu desktop
  environment (like the login screen, dock, and the bar at top of the
  screen). Applications like Nautilus, the Terminal app, and Chrome are
  not affected.
  
  Maybe an Nvidia issue?
  
  I'm going to restart my PC which will probably fix the issue. I'll edit
  this if the issue persists after the restart.
+ 
+ Edit: To anyone investigating this issue, I recommend looking at some of
+ the other issues I've reported recently. It seems like they could all be
+ 

[Touch-packages] [Bug 1975650] Re: Display stuck in low resolution

[Sam Magura]

** Description changed:

  I often have to forcibly power down my PC because of this bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970808. Well, the
  most recent time I did that, when the computer restarted, the resolution
  is stuck on 1024x768 even though I am on a 1920x1080 monitor. I
  restarted my PC again and it is still stuck on the low resolution.
  
  This Ask Ubuntu answer (https://askubuntu.com/a/1167437/1589552) did
  allow me to force my resolution to 1920x1080, but a few things still
  seemed off:
  
  - The display settings page in the Gnome settings app still showed my display 
as "unknown display" and did not have any options for changing the resolution.
  - A WebGL-based application I use for work was very slow compared to normal.
  
  I reverted the change to my Grub config and now I'm back to 1024x768.
  
  I have an Nvidia GTX 1060 connected to a 1920x1080 monitor via HDMI. Let
  me know of any other information I can provide that would be helpful.
  Also let me know if there is a workaround other than reinstalling the
  OS.
  
+ Edit: I have a Windows dual boot on this PC, with Windows installed on a
+ separate SSD. I booted into Windows and everything seems completely
+ fine. This provides further evidence that this is a software issue, not
+ a hardware one.
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 24 20:14:55 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
-Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 
1060 3GB] [1462:3287]
+  NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
+    Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 
1060 3GB] [1462:3287]
  InstallationDate: Installed on 2022-04-23 (31 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/usr/bin/zsh
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic 
root=UUID=c4ac1391-7d4e-4282-94ba-fbae3c4c044c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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

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

Title:
  Display stuck in low resolution

Status in xorg package in Ubuntu:
  New

Bug description:
  I often have to forcibly power down my PC because of this bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970808. Well,
  the most recent time I did that, when the computer restarted, the
  resolution is stuck on 1024x768 even though I am on a 1920x1080
  monitor. I restarted my PC again and it is still stuck on the low
  resolution.

  This Ask Ubuntu answer 

[Touch-packages] [Bug 1975650] [NEW] Display stuck in low resolution

[Sam Magura]

Public bug reported:

I often have to forcibly power down my PC because of this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970808. Well, the
most recent time I did that, when the computer restarted, the resolution
is stuck on 1024x768 even though I am on a 1920x1080 monitor. I
restarted my PC again and it is still stuck on the low resolution.

This Ask Ubuntu answer (https://askubuntu.com/a/1167437/1589552) did
allow me to force my resolution to 1920x1080, but a few things still
seemed off:

- The display settings page in the Gnome settings app still showed my display 
as "unknown display" and did not have any options for changing the resolution.
- A WebGL-based application I use for work was very slow compared to normal.

I reverted the change to my Grub config and now I'm back to 1024x768.

I have an Nvidia GTX 1060 connected to a 1920x1080 monitor via HDMI. Let
me know of any other information I can provide that would be helpful.
Also let me know if there is a workaround other than reinstalling the
OS.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
Uname: Linux 5.15.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue May 24 20:14:55 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 
3GB] [1462:3287]
InstallationDate: Installed on 2022-04-23 (31 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic 
root=UUID=c4ac1391-7d4e-4282-94ba-fbae3c4c044c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/25/2019
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F4
dmi.board.asset.tag: Default string
dmi.board.name: B450M DS3H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: B450M DS3H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
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

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


** Tags: amd64 apport-bug jammy resolution ubuntu

** Attachment added: "Display settings"
   
https://bugs.launchpad.net/bugs/1975650/+attachment/5592732/+files/Screenshot%20from%202022-05-24%2020-18-45.png

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

Title:
  Display stuck in low resolution

Status in xorg package in Ubuntu:
  New

Bug description:
  I often have to forcibly power down my PC because of this bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970808. Well,
  the most recent time I did that, when the computer restarted, the
  resolution is stuck on 1024x768 even though I am on a 1920x1080
  monitor. I restarted my PC again and it is still stuck on the low
  resolution.

  This Ask Ubuntu answer (https://askubuntu.com/a/1167437/1589552) did
  allow me to force my resolution to 1920x1080, but a few things still
  seemed off:

  - The display settings page in the Gnome settings app still showed my display 
as "unknown display" and did not have any options for changing the resolution.
  - A WebGL-based application I use for work was very slow compared to normal.

  I reverted the change to my Grub config and now I'm back to 

[Touch-packages] [Bug 1952788] [NEW] [Latitude 7520, Realtek ALC289, Speaker, Internal] No sound at all

[Sam]

Private bug reported:

There is no audio output from internal speakers on Ubuntu 20.04 LTS.
Internal speakers work fine on Windows 10 Pro.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.13.0-1020.24-oem 5.13.19
Uname: Linux 5.13.0-1020-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  sam3861 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 30 19:58:52 2021
InstallationDate: Installed on 2021-11-23 (6 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:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1553 F pulseaudio
      sam3861 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [Latitude 7520, Realtek ALC289, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/19/2021
dmi.bios.release: 1.12
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.12.2
dmi.board.name: 08X1VY
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.2:bd11/19/2021:br1.12:svnDellInc.:pnLatitude7520:pvr:rvnDellInc.:rn08X1VY:rvrA01:cvnDellInc.:ct10:cvr:sku0A38:
dmi.product.family: Latitude
dmi.product.name: Latitude 7520
dmi.product.sku: 0A38
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Information type changed from Public to Private

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

Title:
  [Latitude 7520, Realtek ALC289, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  There is no audio output from internal speakers on Ubuntu 20.04 LTS.
  Internal speakers work fine on Windows 10 Pro.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-1020.24-oem 5.13.19
  Uname: Linux 5.13.0-1020-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sam3861 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 30 19:58:52 2021
  InstallationDate: Installed on 2021-11-23 (6 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:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1553 F pulseaudio
    sam3861 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Latitude 7520, Realtek ALC289, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.2
  dmi.board.name: 08X1VY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.2:bd11/19/2021:br1.12:svnDellInc.:pnLatitude7520:pvr:rvnDellInc.:rn08X1VY:rvrA01:cvnDellInc.:ct10:cvr:sku0A38:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7520
  dmi.product.sku: 0A38
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952788/+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 1943840] Re: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap

[Sam Van den Eynde]

Olivier, I am not sure what is the reasoning here.

That you obviously want to land this in a non-LTS version has nothing to
do with the fact the base product is not ready and that the change was
announced unacceptably late here. The Flutter-based installer is a nice
example. You can obviously develop something for years ánd still land it
in a non-LTS.

Locking out users is not just about "the deb still being available".
Some people will have the snap, others the deb, and others both. If they
have both I have no idea which one is run when they click the FF icon.
The upgrade scenario you mention in comment #7 does not seem to be the
real world case either.

We just got teleported back in time, where the only way for our helpdesk
to know what happens when a user calls the helpdesk, is to open a
terminal and run "apt-get" and "ps aux". This is a support hell,
especially at scale. Because of a non-critical move to another package
format.

And so far no guarantees on the LTS either.

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

Title:
  [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Impish:
  Fix Released
Status in ubuntu-release-upgrader source package in Impish:
  Fix Released
Status in ubuntu-settings source package in Impish:
  Fix Released

Bug description:
  Per Canonical's distribution agreement with Mozilla, we're making the
  snap¹ the default installation of firefox on desktop ISOs starting
  with Ubuntu 21.10.

  The snap is built and published for amd64, armhf and arm64. It is
  jointly maintained by Mozilla and the Ubuntu desktop team, and
  published by Mozilla.

  This requires updating the desktop-minimal seed, as well as ubuntu-
  release-upgrader.

  ¹ https://snapcraft.io/firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1943840/+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 1943840] Re: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap

[Sam Van den Eynde]

Honestly, to announce this one month before release without feature
parity, is baffling.

As it looks this puts us in a position where we probably have to stop
supporting Ubuntu after more than a decade, as the available browsers
can't work with our Belgian Identity Card.

And this because of a packaging format. It is honestly mind-boggling.

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

Title:
  [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Impish:
  Fix Released
Status in ubuntu-release-upgrader source package in Impish:
  Fix Released
Status in ubuntu-settings source package in Impish:
  Fix Released

Bug description:
  Per Canonical's distribution agreement with Mozilla, we're making the
  snap¹ the default installation of firefox on desktop ISOs starting
  with Ubuntu 21.10.

  The snap is built and published for amd64, armhf and arm64. It is
  jointly maintained by Mozilla and the Ubuntu desktop team, and
  published by Mozilla.

  This requires updating the desktop-minimal seed, as well as ubuntu-
  release-upgrader.

  ¹ https://snapcraft.io/firefox

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

Re: [Touch-packages] [Bug 1945795] [NEW] krb5: Fail to build against OpenSSL 3.0

[Sam Hartman]

> "Simon" == Simon Chopin <1945...@bugs.launchpad.net> writes:
Simon> We're planning to transition to OpenSSL 3.0 for the 22.04
Simon> release, and consider this issue as blocking for this
Simon> transition.

I expect things to be fixed in Debian within the next couple of months.

I attach the upstream patch for this issue in case Ubuntu needs to move
faster than Debian.


** Patch added: "0001-Fix-softpkcs11-build-issues-with-openssl-3.0.patch"
   
https://bugs.launchpad.net/bugs/1945795/+attachment/5529874/+files/0001-Fix-softpkcs11-build-issues-with-openssl-3.0.patch

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

Title:
  krb5: Fail to build against OpenSSL 3.0

Status in krb5 package in Ubuntu:
  New

Bug description:
  Hello,

  As part of a rebuild against OpenSSL3, this package failed to build on one or
  several architectures. You can find the details of the rebuild at 

  https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html

  or for the amd64 failed build, directly at

  
https://launchpad.net/~schopin/+archive/ubuntu/openssl-3.0.0/+build/22098576/+files/buildlog_ubuntu-
  impish-amd64.krb5_1.18.3-6.0~ssl3ppa1.1_BUILDING.txt.gz

  We're planning to transition to OpenSSL 3.0 for the 22.04 release, and 
consider
  this issue as blocking for this transition.

  You can find general migration informations at
  https://www.openssl.org/docs/manmaster/man7/migration_guide.html
  For your tests, you can build against libssl-dev as found in the PPA
  schopin/openssl-3.0.0

  Looking into the upstream master branch, I was able to find the following 
commits
  related to OpenSSL3:

  https://github.com/krb5/krb5/commit/00de1aad7b3647b91017c7009b0bc65cd0c8b2e0
  https://github.com/krb5/krb5/commit/d6bf42279675100e3e4fe7c6e08eef74d49624cb
  https://github.com/krb5/krb5/commit/aa9b4a2a64046afd2fab7cb49c346295874a5fb6

  Perhaps a simple cherry-pick of those would suffice?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1945795/+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 1911219] [NEW] Xorg freeze

[Sam John]

Public bug reported:


Also freezes when trying to open Libre Office new documents

Not sure if it is the video that is causing issues

Mouse and keyboard seems to be frozen and cant do anything without a
hard reboot

Some times the video keeps playing even if everything is frozen.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 12 11:29:12 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Within the last few days
GraphicsCard:
 NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: eVga.com. Corp. GT218 [GeForce 210] [3842:1212]
InstallationDate: Installed on 2021-01-09 (3 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Gigabyte Technology Co., Ltd. GA-970A-D3
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=598990d0-29d6-4e5b-a8aa-3c75c00bd284 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/30/2012
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F10
dmi.board.name: GA-970A-D3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd05/30/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-970A-D3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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 20.2.6-0ubuntu0.20.04.1
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

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


** Tags: amd64 apport-bug focal freeze ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  
  Also freezes when trying to open Libre Office new documents

  Not sure if it is the video that is causing issues

  Mouse and keyboard seems to be frozen and cant do anything without a
  hard reboot

  Some times the video keeps playing even if everything is frozen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 12 11:29:12 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last few days
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: eVga.com. Corp. GT218 [GeForce 210] [3842:1212]
  InstallationDate: Installed on 2021-01-09 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. GA-970A-D3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=598990d0-29d6-4e5b-a8aa-3c75c00bd284 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: 

[Touch-packages] [Bug 1903271] [NEW] package perl 5.30.0-9ubuntu0.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Sam Tyagaraj]

Public bug reported:

reports of dependancies not installed

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: perl 5.30.0-9ubuntu0.2
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
AptOrdering:
 perl-base:amd64: Install
 perl-base:amd64: Configure
 perl-modules-5.30:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Nov  6 08:10:34 2020
DuplicateSignature:
 package:perl:5.30.0-9ubuntu0.2
 Setting up libperl5.30:amd64 (5.30.0-9ubuntu0.2) ...
 dpkg: error processing package perl (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2020-11-05 (1 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: perl
Title: package perl 5.30.0-9ubuntu0.2 failed to install/upgrade: package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package perl 5.30.0-9ubuntu0.2 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in perl package in Ubuntu:
  New

Bug description:
  reports of dependancies not installed

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: perl 5.30.0-9ubuntu0.2
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  AptOrdering:
   perl-base:amd64: Install
   perl-base:amd64: Configure
   perl-modules-5.30:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Nov  6 08:10:34 2020
  DuplicateSignature:
   package:perl:5.30.0-9ubuntu0.2
   Setting up libperl5.30:amd64 (5.30.0-9ubuntu0.2) ...
   dpkg: error processing package perl (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2020-11-05 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: perl
  Title: package perl 5.30.0-9ubuntu0.2 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1903271/+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 1896627] [NEW] Windows flicker when being reized with the mouse

[Sam Lane]

Public bug reported:

When resizing a window with the mouse by dragging the edge or corner,
the window begins to flicker.  It only flickers when actively being
resized, and when I stop dragging, it looks normal.  This behavior is
does not occur on same pc in 20.04.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: Budgie:GNOME
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
Date: Tue Sep 22 10:21:51 2020
DistUpgraded: Fresh install
DistroCodename: groovy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2231]
InstallationDate: Installed on 2020-09-22 (0 days ago)
InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 (20200921)
MachineType: LENOVO 20FJS0AJ00
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=72bd1806-98fb-4fa6-be5b-638dec36ebc9 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/07/2016
dmi.bios.release: 1.13
dmi.bios.vendor: LENOVO
dmi.bios.version: N1KET26W (1.13 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FJS0AJ00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.5
dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET26W(1.13):bd10/07/2016:br1.13:efr1.5:svnLENOVO:pn20FJS0AJ00:pvrThinkPadT560:rvnLENOVO:rn20FJS0AJ00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T560
dmi.product.name: 20FJS0AJ00
dmi.product.sku: LENOVO_MT_20FJ_BU_Think_FM_ThinkPad T560
dmi.product.version: ThinkPad T560
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.7-1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug groovy reproducible ubuntu

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

Title:
  Windows flicker when being reized with the mouse

Status in xorg package in Ubuntu:
  New

Bug description:
  When resizing a window with the mouse by dragging the edge or corner,
  the window begins to flicker.  It only flickers when actively being
  resized, and when I stop dragging, it looks normal.  This behavior is
  does not occur on same pc in 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Tue Sep 22 10:21:51 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2231]
  InstallationDate: Installed on 2020-09-22 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 
(20200921)
  MachineType: LENOVO 20FJS0AJ00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=72bd1806-98fb-4fa6-be5b-638dec36ebc9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2016
  dmi.bios.release: 1.13
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET26W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS0AJ00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information

[Touch-packages] [Bug 1886245] [NEW] bluetooth freezing after boot

[Sam Srzen]

Public bug reported:

Boot system, the Bluetooth mouse will stop for about 4-9 seconds, then it will 
work as normal.
I am using a plugable USB Bluetooth adapter for Bluetooth connections.
I am using  blueman to connect.
Mouse used is a Kensington Exper Mouse Wireless Trackball
Issue does not occur with bluetooth speakers, or headphones.

Computer- Dell Precision 5520.


Logs show these errors as below

bt_uhid_send: Invalid argument (22)

Bluetooth: hci0: advertising data len corrected


Description:Ubuntu 20.04 LTS
Release:20.04

blueman:
  Installed: 2.1.2-1
  Candidate: 2.1.2-1
  Version table:
 *** 2.1.2-1 500
500 http://au.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Jul  4 13:24:01 2020
InstallationDate: Installed on 2020-06-03 (30 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0c45:6713 Microdia Integrated_Webcam_HD
 Bus 001 Device 002: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 5520
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezfsem@/vmlinuz-5.4.0-40-generic 
root=ZFS=rpool/ROOT/ubuntu_ezfsem ro quiet splash pcie_aspm=off vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/22/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.19.2
dmi.board.name: 06X96V
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.2:bd05/22/2020:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5520
dmi.product.sku: 07BF
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 5C:F3:70:7E:32:2F  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:193521 acl:13666 sco:0 events:137 errors:0
TX bytes:5858 acl:61 sco:0 commands:82 errors:0

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


** Tags: amd64 apport-bug focal

** Attachment added: "dmesg.txt"
   https://bugs.launchpad.net/bugs/1886245/+attachment/5389533/+files/dmesg.txt

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

Title:
  bluetooth freezing after boot

Status in bluez package in Ubuntu:
  New

Bug description:
  Boot system, the Bluetooth mouse will stop for about 4-9 seconds, then it 
will work as normal.
  I am using a plugable USB Bluetooth adapter for Bluetooth connections.
  I am using  blueman to connect.
  Mouse used is a Kensington Exper Mouse Wireless Trackball
  Issue does not occur with bluetooth speakers, or headphones.

  Computer- Dell Precision 5520.

  
  Logs show these errors as below

  bt_uhid_send: Invalid argument (22)

  Bluetooth: hci0: advertising data len corrected

  
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  blueman:
Installed: 2.1.2-1
Candidate: 2.1.2-1
Version table:
   *** 2.1.2-1 500
  500 http://au.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  4 13:24:01 2020
  InstallationDate: Installed on 2020-06-03 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6713 Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5520
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezfsem@/vmlinuz-5.4.0-40-generic 
root=ZFS=rpool/ROOT/ubuntu_ezfsem ro quiet splash pcie_aspm=off vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 

[Touch-packages] [Bug 1885024] Re: systemd patch fixes: krb5kdc.log Read-only file system

[Sam Hartman]

This is possibly a duplicate of 
https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1874915 at least if you 
are using freeipa.
As shipped, krb5-kdc does not log to /var/log, but instead logs to syslog
My position is that since krb5's systemd configuration is correct for the 
shipped configuration, if you reconfigure your krb5-kdc to log somewhere, you 
should at that point reconfigure the systemd unit to permit writing to that log.
I point to the freeipa bug because freeipa reconfigures this for you but does 
not update the systemd configuration.

** Changed in: krb5 (Ubuntu)
   Status: New => Invalid

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

Title:
  systemd patch fixes: krb5kdc.log Read-only file system

Status in krb5 package in Ubuntu:
  Invalid

Bug description:
  Jun 24 11:29:34 registry1 krb5kdc[1244]: Couldn't open log file
  /var/log/krb5kdc.log: Read-only file system

  can be fixed by adding

  ReadWriteDirectories= /var/log

  to the krb5-kdc.service unit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1885024/+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 1861177] Re: seccomp_rule_add is very slow

[Sam Whited]

Thanks for the follow ups. If the server team doesn't want to take this
on, could someone provide me with a team or person I could contact to
try and gently prod this forward (maybe someone on the security team)?
I've got some customers that are running into this and telling them to
rebuild this library themselves doesn't seem to have made them happy :)

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

Title:
  seccomp_rule_add is very slow

Status in snapd:
  Invalid
Status in libseccomp package in Ubuntu:
  In Progress

Bug description:
  There is a known and patched issue with version 2.4 of libseccomp
  where certain operations have a large performance regression. This is
  causing some packages that use libseccomp such as container
  orchestration systems to occasionally time out or otherwise fail under
  certain workloads.

  Please consider porting the patch into the various Ubuntu versions
  that have version 2.4 of libseccomp and into the backports. The
  performance patch from version 2.5 (yet to be released) applies
  cleanly on top of the 2.4 branch of libseccomp.

  For more information, and for a copy of the patch (which can also be
  cherry picked from the upstream libseccomp repos) see the similar
  Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1861177/+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 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Sam Weston]

This seems to have fixed the issue on my Dell XPS 15 9560. Thanks!
However if I leave my headphones plugged in, the speakers are selected
after a reboot, but that's a separate issue...

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  * Impact
  Sound isn't automatically redirected to headphones when those are connected 
to a jack interface

  * Test case
  Disconnect the headsets
  Start your webbrowser/music player/video player and play some sound
  Connect the headsets to the jack interface

  -> the sound should be directly redirected to the plugged headsets

  * Regression potential
  Check that audio routing when connecting/disconnecting devices to the hack 
entry is working correctly

  

  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
   State: RUNNING
   Name: alsa_input.pci-_00_1f.3.analog-stereo
   Description: Built-in Audio Analog Stereo
   Driver: module-alsa-card.c
   Sample Specification: s16le 2ch 44100Hz
   Channel Map: front-left,front-right
   Owner Module: 7
   Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+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 1861177] Re: seccomp_rule_add is very slow

[Sam Whited]

Gentle ping. Can this be assigned to someone? Thanks!

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

Title:
  seccomp_rule_add is very slow

Status in snapd:
  Triaged
Status in libseccomp package in Ubuntu:
  Triaged

Bug description:
  There is a known and patched issue with version 2.4 of libseccomp
  where certain operations have a large performance regression. This is
  causing some packages that use libseccomp such as container
  orchestration systems to occasionally time out or otherwise fail under
  certain workloads.

  Please consider porting the patch into the various Ubuntu versions
  that have version 2.4 of libseccomp and into the backports. The
  performance patch from version 2.5 (yet to be released) applies
  cleanly on top of the 2.4 branch of libseccomp.

  For more information, and for a copy of the patch (which can also be
  cherry picked from the upstream libseccomp repos) see the similar
  Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1861177/+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 1850103] Re: gnome-tweak-tool window keeps flickering on cursor hovering

[sam]

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

I encountered the same issue. I was planning to reinstall OS as
restarting/shuting down/reinstall application did not help. This issue
started happening after changing placement left to right in window
titlebars. If the placement is changed from left to right/right to left,
the flickering is appearing and menus in gnome tweak box are not
registering/clickable. So, above solution worked for me. Resize the
gnome tweak then change the placement setting then close it. Everything
should be normal after that as long as you do not touch/move the
settings of placement . Thanks, Xavier (xavierl)  for solution.

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

Title:
  gnome-tweak-tool window keeps flickering on cursor hovering

Status in gnome-tweaks package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  the gnome-tweak-tool window keeps flickering abnormally. this might be
  a bug as i have seen somebody else mention the issue somewhere in the
  internet.

  i do have the screencast of the phenomenon i can send it to you for
  the review of the problem i am facing.

  i am on ubuntu 19.10 system installed via bootable usb. before i had
  interrupted network upgrade of the system which was recovered via grub
  recovery mode. since i thought the flickering was due to all this, i
  fresh installed the system via bootable usb.

  still the problem is persistent and its abnormal irrespective of the 
animation button turned on or off.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-26 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Tags:  wayland-session eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

Re: [Touch-packages] [Bug 1874915] Re: krb5kdc[27833]: Couldn't open log file /var/log/krb5kdc.log: Read-only file system

[Sam Hartman]

I'm going to push back on the reassignment to krb5.
I think this is a freeipa bug.
Kerberos's systemd service unit is correct for Kerberos.
freeipa is the one that is deciding it wants to change the Kerberos
logging configuration, and thus is the one that should adjust the
permissions.
Honestly I'd rather see this fixed by freeipa not messing around with
Kerberos configs so much, but especially not logging config.

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

Title:
  krb5kdc[27833]: Couldn't open log file /var/log/krb5kdc.log: Read-only
  file system

Status in krb5 package in Ubuntu:
  New

Bug description:
  Hopefully this can trivially be corrected.

  Seems the systemd service file for the kerberos portion of freeipa
  could use a minor tweak.

  When restarting the kerberos service, it (incorrectly) reports that
  the default configured log file (/var/log/krb5kdc.log) is sending to a
  "read only filesystem".  This is a misleading error, since the
  /var/log directory by default -IS- writeable, but systemd is in fact
  preventing the daemon from writing.  Why systemd can't inject itself
  inappropriately and report that it's causing the trouble is another
  conversation. ;) [not personally a systemd fan]

  
  File:
  =
  /lib/systemd/system/krb5-kdc.service

  Command:
  =
  service krb5-kdc restart

  Error:
  =
  krb5kdc[27833]: Couldn't open log file /var/log/krb5kdc.log: Read-only file 
system

  
  Please make the following adjustment to the default systemd file.
  =
  13c13
  < ReadWriteDirectories=-/var/tmp /tmp /var/lib/krb5kdc -/var/run /run
  ---
  > ReadWriteDirectories=-/var/tmp /tmp /var/lib/krb5kdc -/var/run /run /var/log


  Thank you for all the help and support.  :)

  Cheers,
  -Chris

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1874915/+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 1863894] Re: /etc/bash.bashrc invokes groups command which is slow in large environments

[Sam Morris]

** Description changed:

  /etc/bash.bashrc runs groups(1) whenever a new shell is started.
  
  This command calls getgrgid(3) on every group of which the user is a
  member.
  
  In an environment where FreeIPA is used to allow users to log into their
  computers using their Active Directory accounts, I have seen each call
  to getgrid(3) take over ten seconds. My Active Directory user is a
  member of 30 groups and it is not uncommon for users to be a member of
  50 or more groups. This results in enormous delays when logging in to a
  system with SSH, launching a terminal emulator or even creating a new
  tab in an existing terminal emulator.
  
  The code from /etc/bash.bashrc wants to find out whether the user is a
  member of the 'sudo' or 'admin' groups in order to display a hint to the
  user.
  
  # sudo hint
  if [ ! -e "$HOME/.sudo_as_admin_successful" ] && [ ! -e "$HOME/.hushlogin" ] 
; then
- case " $(groups) " in *\ admin\ *|*\ sudo\ *)
- if [ -x /usr/bin/sudo ]; then
-   cat <<-EOF
-   To run a command as administrator (user "root"), use "sudo ".
-   See "man sudo_root" for details.
-   
-   EOF
- fi
- esac
+ case " $(groups) " in *\ admin\ *|*\ sudo\ *)
+ if [ -x /usr/bin/sudo ]; then
+  cat <<-EOF
+  To run a command as administrator (user "root"), use "sudo ".
+  See "man sudo_root" for details.
+ 
+  EOF
+ fi
+ esac
  fi
  
  This can be rewritten to avoid calling getgrgid(3) for every group that
  the user is a member of by doing something like this (untested):
  
  # sudo hint
  if [[ -x /usr/bin/sudo ]]; then
- if [[ ! -e $HOME/.sudo_as_admin_successful && ! -e $HOME/.hushlogin ]]; 
then
- sudo_gid=$(getent group sudo | cut -d: -f3)
- admin_gid=$(getent group admin | cut -d: -f3)
- for gid in $(id -G); do
- if [[ $gid -eq $sudo_gid || $gid -eq $admin_gid ]]; then
- cat <<-EOF
- To run a command as administrator (user "root"), use 
"sudo ".
- See "man sudo_root" for details.
- EOF
- break
- fi
- done
- fi
+ if [[ ! -e $HOME/.sudo_as_admin_successful && ! -e $HOME/.hushlogin ]]; 
then
+ sudo_gid=$(getent group sudo | cut -d: -f3)
+ admin_gid=$(getent group admin | cut -d: -f3)
+ for gid in $(id -G); do
+ if [[ $gid -eq $sudo_gid || $gid -eq $admin_gid ]]; then
+ cat <<-EOF
+ To run a command as administrator (user "root"), use 
"sudo ".
+ See "man sudo_root" for details.
+ EOF
+ break
+ fi
+ done
+ fi
  fi
  
  As an aside: the reason that getgrid(3) is so slow is because it must
  fetch the members of each group. There is no quick way to do this in
  Active Directory: a recursive search for group members must be
  performed, followed by a lookups to retrieve each of their their POSIX
  UIDs, and then more lookup to retrieve their POSIX username.
  
  Even when the 'ignore_group_members' sssd(8) option is enabled, which
  causes getgrid(3) to report that a group has no members, calling
  getgrid(3) on 30-40 groups still takes a few seconds. And this option is
  not the default.
  
  It's also not uncommon to have groups with spaces in their names, which
  causes groups(1) to produce ambiguous output.
  
  For these reasons it is best to avoid the use of groups(1) in scripts
  where more performant and robust alternatives are available.

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

Title:
  /etc/bash.bashrc invokes groups command which is slow in large
  environments

Status in bash package in Ubuntu:
  New

Bug description:
  /etc/bash.bashrc runs groups(1) whenever a new shell is started.

  This command calls getgrgid(3) on every group of which the user is a
  member.

  In an environment where FreeIPA is used to allow users to log into
  their computers using their Active Directory accounts, I have seen
  each call to getgrid(3) take over ten seconds. My Active Directory
  user is a member of 30 groups and it is not uncommon for users to be a
  member of 50 or more groups. This results in enormous delays when
  logging in to a system with SSH, launching a terminal emulator or even
  creating a new tab in an existing terminal emulator.

  The code from /etc/bash.bashrc wants to find out whether the user is a
  member of the 'sudo' or 'admin' groups in order to display a hint to
  the user.

  # sudo hint
  if [ ! -e "$HOME/.sudo_as_admin_successful" ] && [ ! -e "$HOME/.hushlogin" ] 
; then
  case " $(groups) " in *\ admin\ *|*\ sudo\ *)
  if [ -x /usr/bin/sudo ]; then
   cat <<-EOF
   To run a command as administrator (user "root"), use "sudo ".
   See "man sudo_root" for details.

   EOF
  

[Touch-packages] [Bug 1863894] [NEW] /etc/bash.bashrc invokes groups command which is slow in large environments

[Sam Morris]

Public bug reported:

/etc/bash.bashrc runs groups(1) whenever a new shell is started.

This command calls getgrgid(3) on every group of which the user is a
member.

In an environment where FreeIPA is used to allow users to log into their
computers using their Active Directory accounts, I have seen each call
to getgrid(3) take over ten seconds. My Active Directory user is a
member of 30 groups and it is not uncommon for users to be a member of
50 or more groups. This results in enormous delays when logging in to a
system with SSH, launching a terminal emulator or even creating a new
tab in an existing terminal emulator.

The code from /etc/bash.bashrc wants to find out whether the user is a
member of the 'sudo' or 'admin' groups in order to display a hint to the
user.

# sudo hint
if [ ! -e "$HOME/.sudo_as_admin_successful" ] && [ ! -e "$HOME/.hushlogin" ] ; 
then
case " $(groups) " in *\ admin\ *|*\ sudo\ *)
if [ -x /usr/bin/sudo ]; then
cat <<-EOF
To run a command as administrator (user "root"), use "sudo ".
See "man sudo_root" for details.

EOF
fi
esac
fi

This can be rewritten to avoid calling getgrgid(3) for every group that
the user is a member of by doing something like this (untested):

# sudo hint
if [[ -x /usr/bin/sudo ]]; then
if [[ ! -e $HOME/.sudo_as_admin_successful && ! -e $HOME/.hushlogin ]]; then
sudo_gid=$(getent group sudo | cut -d: -f3)
admin_gid=$(getent group admin | cut -d: -f3)
for gid in $(id -G); do
if [[ $gid -eq $sudo_gid || $gid -eq $admin_gid ]]; then
cat <<-EOF
To run a command as administrator (user "root"), use "sudo 
".
See "man sudo_root" for details.
EOF
break
fi
done
fi
fi

As an aside: the reason that getgrid(3) is so slow is because it must
fetch the members of each group. There is no quick way to do this in
Active Directory: a recursive search for group members must be
performed, followed by a lookups to retrieve each of their their POSIX
UIDs, and then more lookup to retrieve their POSIX username.

Even when the 'ignore_group_members' sssd(8) option is enabled, which
causes getgrid(3) to report that a group has no members, calling
getgrid(3) on 30-40 groups still takes a few seconds. And this option is
not the default.

It's also not uncommon to have groups with spaces in their names, which
causes groups(1) to produce ambiguous output.

For these reasons it is best to avoid the use of groups(1) in scripts
where more performant and robust alternatives are available.

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

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

Title:
  /etc/bash.bashrc invokes groups command which is slow in large
  environments

Status in bash package in Ubuntu:
  New

Bug description:
  /etc/bash.bashrc runs groups(1) whenever a new shell is started.

  This command calls getgrgid(3) on every group of which the user is a
  member.

  In an environment where FreeIPA is used to allow users to log into
  their computers using their Active Directory accounts, I have seen
  each call to getgrid(3) take over ten seconds. My Active Directory
  user is a member of 30 groups and it is not uncommon for users to be a
  member of 50 or more groups. This results in enormous delays when
  logging in to a system with SSH, launching a terminal emulator or even
  creating a new tab in an existing terminal emulator.

  The code from /etc/bash.bashrc wants to find out whether the user is a
  member of the 'sudo' or 'admin' groups in order to display a hint to
  the user.

  # sudo hint
  if [ ! -e "$HOME/.sudo_as_admin_successful" ] && [ ! -e "$HOME/.hushlogin" ] 
; then
  case " $(groups) " in *\ admin\ *|*\ sudo\ *)
  if [ -x /usr/bin/sudo ]; then
cat <<-EOF
To run a command as administrator (user "root"), use "sudo ".
See "man sudo_root" for details.

EOF
  fi
  esac
  fi

  This can be rewritten to avoid calling getgrgid(3) for every group
  that the user is a member of by doing something like this (untested):

  # sudo hint
  if [[ -x /usr/bin/sudo ]]; then
  if [[ ! -e $HOME/.sudo_as_admin_successful && ! -e $HOME/.hushlogin ]]; 
then
  sudo_gid=$(getent group sudo | cut -d: -f3)
  admin_gid=$(getent group admin | cut -d: -f3)
  for gid in $(id -G); do
  if [[ $gid -eq $sudo_gid || $gid -eq $admin_gid ]]; then
  cat <<-EOF
  To run a command as administrator (user "root"), use 
"sudo ".
  See "man sudo_root" for details.
  EOF
  break
  fi
  done
  fi
  fi

  As an aside: the reason that getgrid(3) 

[Touch-packages] [Bug 1861177] [NEW] seccomp_rule_add is very slow

[Sam Whited]

Public bug reported:

There is a known and patched issue with version 2.4 of libseccomp where
certain operations have a large performance regression. This is causing
some packages that use libseccomp such as container orchestration
systems to occasionally time out or otherwise fail under certain
workloads.

Please consider porting the patch into the various Ubuntu versions that
have version 2.4 of libseccomp and into the backports. The performance
patch from version 2.5 (yet to be released) applies cleanly on top of
the 2.4 branch of libseccomp.

For more information, and for a copy of the patch (which can also be
cherry picked from the upstream libseccomp repos) see the similar Debian
issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913

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

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

Title:
  seccomp_rule_add is very slow

Status in libseccomp package in Ubuntu:
  New

Bug description:
  There is a known and patched issue with version 2.4 of libseccomp
  where certain operations have a large performance regression. This is
  causing some packages that use libseccomp such as container
  orchestration systems to occasionally time out or otherwise fail under
  certain workloads.

  Please consider porting the patch into the various Ubuntu versions
  that have version 2.4 of libseccomp and into the backports. The
  performance patch from version 2.5 (yet to be released) applies
  cleanly on top of the 2.4 branch of libseccomp.

  For more information, and for a copy of the patch (which can also be
  cherry picked from the upstream libseccomp repos) see the similar
  Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1861177/+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 1825963] Re: Abysmal memory leak on tracker-extract

[Sam Thursfield]

Thanks for providing the 'minimap_area.dds' file. How many other files
are there in the same directory? And what is the total size of all of
these .dds files?


Running `tracker extract` on the given gives the following message:

Call to gst_discoverer_discover_uri(file:///.../minimap_area.dds) failed: 
Internal data stream error.
file:///.../minimap_area.dds: No metadata or extractor modules found to handle 
this file

I think this is pretty normal, that GStreamer's type detection code
sometimes reports an error when it fails to detect the type of a file.
Running with `env GST_DEBUG=2` doesn't show any unexpected messages.
Running under `valgrind` doesn't show any dramatic memory leak.

It's possible that this code path blows up on some larger files that are
in the same directory, though. Could you run `tracker extract *` inside
the problematic directory and see what happens? (This will run in the
foreground so you should be able to CTRL+c if it starts to eat all your
RAM ... which it hopefully will do so we can narrow down the problem :).

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

Title:
  Abysmal memory leak on tracker-extract

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 18.10 to 19.04 my Ubuntu desktop started lagging
  madly. It became very difficult to use and I discovered the problem to
  be tracker-extract running and very rapidly leaking memory up to 100%
  and breaching into swap memory. I tried killing it several times but
  Tracker appears to relaunch it every time, so I deleted it from
  /usr/lib/tracker entirely.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: tracker 2.1.8-2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 23 13:02:25 2019
  InstallationDate: Installed on 2019-03-11 (42 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825963/+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 1829735] Re: Fresh install of 18.10 stuck at initializing ramdisk after sudo apt upgrade

[Sam]

** Package changed: texinfo (Ubuntu) => apt (Ubuntu)

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

Title:
  Fresh install of 18.10 stuck at initializing ramdisk after sudo apt
  upgrade

Status in apt package in Ubuntu:
  New

Bug description:
  **Specs**
  - Asus Zenbook 14 UX433FN (NVMe PCIe SSD)
  - Ubuntu 18.10 and Windows 10 dual boot, Windows 10 working fine.

  **Background**
  After successful FRESH install of Ubuntu 18.10 desktop using LiveUSB, and 
subsequent update using either command prompt (sudo apt upgrade) or via the GUI 
that appears after first reboot (security updates etc.)

  **How to reproduce the bug**
  1. Fresh (minimal) install of Ubuntu 18.10
  2. Reboot successfully.
  3. Either:
3a. Open terminal and run 
$ sudo apt upgrade
3b. Wait for Ubuntu to automatically show the GUI prompt asking for 
installation of important updates (eg. security)
  4. Update successful
  5. Reboot
  6. Boot stuck at `Loading initial ramdisk...`, even in recovery mode.

  **Suspected problem**
  Broken package. Note that minimal installation is used.

  
  More information in the AskUbuntu Forum: 
https://askubuntu.com/questions/1144688/ubuntu-18-10-stuck-at-initialising-ramdisk-after-fresh-install-and-subsequent-up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1829735/+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 1497806] Re: Mirrored display broken in Xubuntu

[Sam Fite]

I am using xfce 4.12 on Ubuntu 18.04 and am having a similar issue.
However, on startup, my laptop screen is mirrored on the intended
external monitor just before I reach lightdm. xrandr detects the monitor
however running 'xrandr --output <> --same-as <>' results in no effect
with no error messages or anything. When viewed through xfce4-settings-
manager, the external monitor shows up but is grayed out and is labeled
'(disabled);

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

Title:
  Mirrored display broken in Xubuntu

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Mirrored displays is not accessible (grayed out) when trying to
  activate this feature for multi-monitor support.  I am not sure which
  specific package to nominate for this bug, but it seems to only be
  happening on systems with XFCE4 installed and running (Including
  Xubuntu, Mint, and Debian).

  It maybe an error with the package xfce4-display-settings, but I am
  not sure.

  This bug is being reported from:
  Description:  Linux Mint 17.2 Rafaela
  Release:  17.2

  Here is a copy of this Bug Report on Bugzilla:  
https://bugzilla.xfce.org/show_bug.cgi?id=11712
  This bug report also has a picture attachment which is exactly what I am 
seeing.

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

Re: [Touch-packages] [Bug 1817955] [NEW] Getting new "DN is out of the realm subtree" error on adding principal

[Sam Hartman]

Yes, it is because of that change.
is the dn outside of the subtree?

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

Title:
  Getting new "DN is out of the realm subtree" error on adding principal

Status in krb5 package in Ubuntu:
  New

Bug description:
  Recently applied security update to 14.04.5 LTS kerberos (1.12+dfsg-
  2ubuntu5.4), and started getting errors when adding new principals to
  LDAP.

  Obfuscated example:

  kadmin.local -q "ank -x
  dn=\"uid=testuser,ou=People,dc=example,dc=com\" -pw \"dummypass\"
  testuser"

  now gives:
  Authenticating as principal root/ad...@test.example.com with password.
  NOTICE: no policy specified for testu...@test.example.com; assigning "default"
  add_principal: DN is out of the realm subtree while creating 
"testu...@test.example.com".

  
  This worked up through 1.12+dfsg-2ubuntu5.3, and I think it now fails due to 
changes in src/plugins/kdb/ldap/libkdb_ldap/ldap_principal2.c in response to 
CVE-2018-5729 or CVE-2018-5730.

  I'm going to attempt a downgrade to 1.12+dfsg-2ubuntu5.3 to check.

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

Re: [Touch-packages] [Bug 1817376] Re: krb5-admin-server postinst has broken debconf if RUN_KADMIND set in /etc/default/krb5-admin-server

[Sam Hartman]

Robie any chance I could get you to sync krb5 1.17-2 from Debian
unstable to disco?
It's probably not a big deal but there's no reason not to take the fix
into Disco.

>>>>> "Robie" == Robie Basak <1817...@bugs.launchpad.net> writes:

Robie> Thanks Clark and Sam.  Ubuntu doesn't support upgrade paths
Robie> that skip LTS releases. So, ignoring EOL releases, we only
Robie> need to consider Trusty->Xenial,
Xenial-> Bionic, Bionic->Cosmic and Cosmic->Disco. If only upgrading from 
1.12 is affected,
Robie> then from Ubuntu is Trusty->Xenial the only upgrade path
Robie> affected?

yes.

Robie> If so, is it just Xenial that we need to fix?


I was working with this a bit testing the upgrade from wheezy to buster
on the Debian side.  Wheezy is the only Debian release that is vaguely
extant where this could come up.
In my testing, Debconf didn't actually remove the template on an
upgrade.
So, The two cases where I found that I could reproduce the situation
Were:

* remove krb5-admin-server on the old release and install it on the new
  release (without doing an upgrade)

* Copy in a /etc/default/krb5-admin-server from another system.

Neither of those seems serious enough to backport a fix for.  I'd rather
wait until we get a better understanding of how this gets triggered
before doing any changes to xenial.  I agree though that if we need to
change any old release xenial is the only target.

--Sam

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

Title:
  krb5-admin-server postinst has broken debconf if RUN_KADMIND set in
  /etc/default/krb5-admin-server

Status in krb5 package in Ubuntu:
  Triaged

Bug description:
  Package installation fails on postinst due to broken debconf when
  /etc/default/krb5-admin-server sets RUN_KADMIND to a value.

  This happens because the .config script [0] sets debconf question krb5
  -admin-server/kadmind to the defaults file value when set to a value.
  But the .templates file [1] has no entry for this question resulting
  in a lookup failure.

  [0] 
https://git.launchpad.net/ubuntu/+source/krb5/tree/debian/krb5-admin-server.config#n16
  [1] 
https://git.launchpad.net/ubuntu/+source/krb5/tree/debian/krb5-admin-server.templates

  This bug seems to go back to at least Xenial (and also affects debian
  packaging too). We worked around this locally by removing RUN_KADMIND
  from our local defaults file, but this was an annoying bug to sort out
  and should probably be fixed. That said I'm not sure if it would be
  more appropraite to remove the db_set from [0] or add the question
  back to [1].

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1817376/+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 1817376] Re: krb5-admin-server postinst has broken debconf if RUN_KADMIND set in /etc/default/krb5-admin-server

[Sam Hartman]

I think this is basically only a problem on upgrade from older versions of 
krb5, in particular from prior to the 1.12 era to the current packaging.
As part of adding support for systemd units, I decided to drop support for the 
run_kadmind variable, and bungled the upgrade path.
This is an issue for upgrades from trusty or precise to anything newer if you 
are running krb5-admin-server.
There's a very simple work around: remove run_kadmind from 
/etc/default/krb5-admin-server.
I'll fix for Debian shortly.
What Ubuntu versions is this worth doing a fix for?

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

Title:
  krb5-admin-server postinst has broken debconf if RUN_KADMIND set in
  /etc/default/krb5-admin-server

Status in krb5 package in Ubuntu:
  Confirmed

Bug description:
  Package installation fails on postinst due to broken debconf when
  /etc/default/krb5-admin-server sets RUN_KADMIND to a value.

  This happens because the .config script [0] sets debconf question krb5
  -admin-server/kadmind to the defaults file value when set to a value.
  But the .templates file [1] has no entry for this question resulting
  in a lookup failure.

  [0] 
https://git.launchpad.net/ubuntu/+source/krb5/tree/debian/krb5-admin-server.config#n16
  [1] 
https://git.launchpad.net/ubuntu/+source/krb5/tree/debian/krb5-admin-server.templates

  This bug seems to go back to at least Xenial (and also affects debian
  packaging too). We worked around this locally by removing RUN_KADMIND
  from our local defaults file, but this was an annoying bug to sort out
  and should probably be fixed. That said I'm not sure if it would be
  more appropraite to remove the db_set from [0] or add the question
  back to [1].

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1817376/+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 1817376] Re: krb5-admin-server postinst has broken debconf if RUN_KADMIND set in /etc/default/krb5-admin-server

[Sam Hartman]

** Changed in: krb5 (Ubuntu)
   Status: New => Confirmed

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

Title:
  krb5-admin-server postinst has broken debconf if RUN_KADMIND set in
  /etc/default/krb5-admin-server

Status in krb5 package in Ubuntu:
  Confirmed

Bug description:
  Package installation fails on postinst due to broken debconf when
  /etc/default/krb5-admin-server sets RUN_KADMIND to a value.

  This happens because the .config script [0] sets debconf question krb5
  -admin-server/kadmind to the defaults file value when set to a value.
  But the .templates file [1] has no entry for this question resulting
  in a lookup failure.

  [0] 
https://git.launchpad.net/ubuntu/+source/krb5/tree/debian/krb5-admin-server.config#n16
  [1] 
https://git.launchpad.net/ubuntu/+source/krb5/tree/debian/krb5-admin-server.templates

  This bug seems to go back to at least Xenial (and also affects debian
  packaging too). We worked around this locally by removing RUN_KADMIND
  from our local defaults file, but this was an annoying bug to sort out
  and should probably be fixed. That said I'm not sure if it would be
  more appropraite to remove the db_set from [0] or add the question
  back to [1].

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1817376/+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 1799327] [NEW] screen display

[Sam Salado]

Public bug reported:

my home and login screen looks like i had taken LSD vivid distorted
colours. and just solid color on normal start-up.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic i686
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Oct 22 18:54:19 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV515/M54 [Mobility Radeon X1400] 
[1002:7145] (prog-if 00 [VGA controller])
   Subsystem: Lenovo Thinkpad T60 model 2007 [17aa:2006]
InstallationDate: Installed on 2016-02-13 (982 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
MachineType: LENOVO 200763U
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=010804b7-21f1-4e4e-a968-18ae8286fbf2 ro recovery nomodeset
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 79ETE6WW (2.26 )
dmi.board.name: 200763U
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE6WW(2.26):bd04/01/2010:svnLENOVO:pn200763U:pvrThinkPadT60:rvnLENOVO:rn200763U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T60
dmi.product.name: 200763U
dmi.product.version: ThinkPad T60
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Oct 22 17:23:51 2018
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4

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


** Tags: apport-bug bionic i386 ubuntu

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

Title:
  screen display

Status in xorg package in Ubuntu:
  New

Bug description:
  my home and login screen looks like i had taken LSD vivid distorted
  colours. and just solid color on normal start-up.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic i686
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Oct 22 18:54:19 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV515/M54 [Mobility Radeon X1400] 
[1002:7145] (prog-if 00 [VGA controller])
 Subsystem: Lenovo Thinkpad T60 model 2007 [17aa:2006]
  InstallationDate: Installed on 2016-02-13 (982 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: LENOVO 200763U
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=010804b7-21f1-4e4e-a968-18ae8286fbf2 ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETE6WW (2.26 )
  dmi.board.name: 200763U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE6WW(2.26):bd04/01/2010:svnLENOVO:pn200763U:pvrThinkPadT60:rvnLENOVO:rn200763U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T60
  dmi.product.name: 200763U
  

[Touch-packages] [Bug 1713448] Re: Adobe Reader doesn't print on OKI C911

[sam]

I had a similar issue with Adobe Reader. I think you should check your
file because this bug is missing log files. It is also available Adobe's
Photoshop. It is a very interesting software. If you have any issue with
Photoshop, like error issue, then simply visit
https://www.adobesupportphonenumber.com/blog/fix-adobe-photoshop-
error-16/. They will solve your issue quickly.

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

Title:
  Adobe Reader doesn't print on OKI C911

Status in cups package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Out and over.
  I tried whatever I could think of, but whatever I send there, anything will 
make the printer blink, 'processing', forever, until I cancel the job. 
  The printer, however, prints the same files from okular, and from all other 
applications that I have tried so far. This would clearly point to acroread. 
  However, acroread prints to all other printers that we have standing about 
without any problem. 

  Logically, from what I could state so far, we have an AND-combination:
  everything works, except I print a file from acroread through OKI
  C911.

  Since I have other printers and other PDF-software, it is minor. And yet, I 
wouldn't mind helping to debug this thing.
  I'm using the OKI-provided ppd with cups. 

  adobereader-enu:i386 9.5.5
  cups 2.1.3-4
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CupsErrorLog:
   E [31/Aug/2018:11:08:02 +0200] Missing value on line 617 of 
/var/cache/cups/job.cache.
   E [31/Aug/2018:11:08:02 +0200] Missing value on line 668 of 
/var/cache/cups/job.cache.
   E [31/Aug/2018:11:08:02 +0200] Missing value on line 4277 of 
/var/cache/cups/job.cache.
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-04-01 (1247 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  Lpstat:
   device for BrotherColourMFC9970: socket://134.91.100.26:9100
   device for Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600: 
dnssd://hp%20color%20LaserJet%204600%40IC07CA93._printer._tcp.local/
   device for OKI_C911: dnssd://OKIC911-BB319._pdl-datastream._tcp.local/
   device for Samsung_M262x_282x_Series: 
dnssd://Samsung%20M262x%20282x%20Series%20(SEC001599EE3069)._printer._tcp.local/
  MachineType: LENOVO 2924WEG
  Package: linux
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/BrotherColourMFC9970.ppd', '/etc/cups/ppd/OKI_C911.ppd', 
'/etc/cups/ppd/Samsung_M262x_282x_Series.ppd', 
'/etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd'] 
failed with exit code 2: grep: /etc/cups/ppd/BrotherColourMFC9970.ppd: 
Permission denied
   grep: /etc/cups/ppd/OKI_C911.ppd: Permission denied
   grep: /etc/cups/ppd/Samsung_M262x_282x_Series.ppd: Permission denied
   grep: 
/etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  Tags:  xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2018-08-15 (15 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/11/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6UET70WW (1.50 )
  dmi.board.name: 2924WEG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WEG:pvrThinkPadT410s:rvnLENOVO:rn2924WEG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2924WEG
  dmi.product.version: ThinkPad T410s
  dmi.sys.vendor: LENOVO

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

Re: [Touch-packages] [Bug 1793594] [NEW] IAKERB-HEADER "Realm" field incorrectly encoded as OCTET STRING

[Sam Hartman]

So, is this a spec bug or an implementation bug.
Does the current behavior cause anything to break, or is it simply that
implementations have diverged from the spec in tagging of the string.

--Sam

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

Title:
  IAKERB-HEADER "Realm" field incorrectly encoded as OCTET STRING

Status in krb5 package in Ubuntu:
  New

Bug description:
  Background:

  Under some circumstances, when the client/initiator has a TGT but no
  ticket for a particular principal, it needs to communicate with the
  KDC. The GSSAPI protocol includes a mechanism, a subprotocol named
  IAKERB, for the client to tunnel/proxy through the server/acceptor
  instead of directly communicating with the KDC. (This is useful if
  e.g. the GSSAPI initiator does not have full network access but the
  acceptor does.)

  Problem:

  The formatting of the IAKERB messages is incorrect. Every draft of the
  IAKERB protocol I have been able to find defines the IAKERB-HEADER
  structure to have a field "Realm" which is a UTF8String, like this:

 IAKERB-HEADER ::= SEQUENCE {
 target-realm  [1] UTF8String,

  However, observed protocol exchanges tag the Realm field as an OCTET
  STRING.

  I believe the bug is in src/lib/krb5/asn.1/asn1_k_encode.c near line
  1146, where the DEFFIELD(iakerb_header_1,...) macro is invoked with
  "ostring_data". I think it should be invoked with "utf8_data" instead.

  Reproduction:

  I observed this using Firefox attempting to authenticate with a webserver 
using the "Negotiate" protocol. The first Negotiate message from the browser to 
the server contains:
GSSAPI token (RFC2743 3.3); mechanism 1.3.6.1.5.5.2 (SPNEGO)
  innerToken is a NegTokenInit (RFC4178 4.2.1)
mech = 1.3.6.1.5.2.5 (IAKERB)
mechToken is a (wrapped) GSSAPI token (RFC2743 again) with mech = 
1.3.6.1.5.2.5
  innerToken is the concatenation of:
TOK_ID 05 01 (IAKERB)
IAKERB-HEADER
a Kerberos TGS-REQ

  Dumping the IAKERB-HEADER with `openssl asnparse` produces:

  0:d=0  hl=2 l=  12 cons: SEQUENCE  
  2:d=1  hl=2 l=  10 cons:  cont [ 1 ]
  4:d=2  hl=2 l=   8 prim:   OCTET STRING  :.ORG

  As you can see the realm (.ORG) is tagged as OCTET STRING, rather
  than being tagged as UTF8String.

  Versions:

  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  libgssapi-krb5-2:
Installed: 1.13.2+dfsg-5ubuntu2
Candidate: 1.13.2+dfsg-5ubuntu2
Version table:
   *** 1.13.2+dfsg-5ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.13.2+dfsg-5 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1793594/+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 562006] Re: Cups Web Admin Authentication Fails

[sam]

I have the similar issue with Windows XP. I was very upset with that bug
then I found a link http://www.outlooktechnicalsupportnumbers.com/. This
was a really helpful link.

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

Title:
  Cups Web Admin Authentication Fails

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: cups

  My home office configuration is Karmic Koala server sharing a printer
  to be used by a Windows XP box on the local network. While attempting
  to manage CUPS from the XP box after connecting to the server port
  631, certain pages ask for a root login but the correct name and
  password apparently fail and the user name / password dialog reappears
  never completing. Escalating the Logging level to "debug" I found that
  cupsdAuthorize was failing with no user name data being passed .

  I tried many things and, as seems always to be the case with these
  things, ended up with a fix but not enough energy to start over with a
  fresh cupsd.conf, /etc/group, and lppasswd configuration to reproduce
  the problem and isolate the minimum number of changes needed to fix
  the problem. Thus, some or all of the following changes have fixed the
  problem:

  1. Add root to Shadow group in /etc/group
  2. Add root to lpadmin group in /etc/group
  2. Add root to lppasswd via lppaswd -a root and responding to the password 
prompt with my root password
  3. Change DefaultAuthType to BasicDigest

  Perhaps someone can identify the minimum set of changes required.

  On a side note, I receive, when connecting to certain locations, the
  426 Upgrade Required page mentioned elsewhere that changes from
  http://hostname:631 to a SSL connection on https://x.x.x.x:631. Simply
  clicking on the supplied link allows the web admin app to continue
  (not a bug, as far as I'm concerned, but an annoyance).

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

Re: [Touch-packages] [Bug 1791325] Re: freeipa server needs read access /var/lib/krb5kdc

[Sam Hartman]

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

I agree with Russ.
On the Debian side, I would not support a change to krb5-kdc to make
/var/lib/krb5kdc world readable.
I think putting the public cert in /etc/krb5kdc is fine: I can make a
case it's configuration not state.
If you don't like that, place it somewhere else under /var/lib.

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

Title:
  freeipa server needs read access /var/lib/krb5kdc

Status in freeipa package in Ubuntu:
  New
Status in krb5 package in Ubuntu:
  New

Bug description:
  After installing freeipa-server you cannot login via the browser. You'll get
  a message: "Login failed due to an unknown reason."

  In /var/log/apache2/error.log there is this:
  -8X-8X--
  [Thu Sep 06 12:00:28.720410 2018] [wsgi:error] [pid 6137:tid 140075658061568] 
[remote 10.83.0.11:38596] ipa: INFO: [jsonserver_kerb] 
host/usrv1.ijtest...@ijtest.nl: schema(version=u'2.170'): SUCCESS
  [Thu Sep 06 12:01:00.010427 2018] [:warn] [pid 6140:tid 140076243191552] 
[client 10.83.0.11:38608] failed to set perms (3140) on file 
(/var/run/ipa/ccaches/host~usrv1.ijtest...@ijtest.nl)!, referer: 
https://usrv1.ijtest.nl/ipa/xml
  [Thu Sep 06 12:01:00.099271 2018] [wsgi:error] [pid 6138:tid 140075658061568] 
[remote 10.83.0.11:38608] ipa: INFO: [jsonserver_session] 
host/usrv1.ijtest...@ijtest.nl: ping(): SUCCESS
  [Thu Sep 06 12:01:00.101695 2018] [:warn] [pid 6140:tid 140076130498304] 
[client 10.83.0.11:38608] failed to set perms (3140) on file 
(/var/run/ipa/ccaches/host~usrv1.ijtest...@ijtest.nl)!, referer: 
https://usrv1.ijtest.nl/ipa/xml
  [Thu Sep 06 12:01:00.273013 2018] [wsgi:error] [pid 6137:tid 140075658061568] 
[remote 10.83.0.11:38608] ipa: INFO: [jsonserver_session] 
host/usrv1.ijtest...@ijtest.nl: ca_is_enabled(version=u'2.107'): SUCCESS
  [Thu Sep 06 12:01:02.805635 2018] [:warn] [pid 6140:tid 140076234798848] 
[client 10.83.0.11:38608] failed to set perms (3140) on file 
(/var/run/ipa/ccaches/host~usrv1.ijtest...@ijtest.nl)!, referer: 
https://usrv1.ijtest.nl/ipa/xml
  [Thu Sep 06 12:01:02.999541 2018] [wsgi:error] [pid 6138:tid 140075658061568] 
[remote 10.83.0.11:38608] ipa: INFO: [jsonserver_session] 
host/usrv1.ijtest...@ijtest.nl: host_mod(u'usrv1.ijtest.nl', ipasshpubkey=(), 
updatedns=False, version=u'2.26'): EmptyModlist
  [Thu Sep 06 13:02:22.125841 2018] [wsgi:error] [pid 6138:tid 140075658061568] 
[remote 172.16.16.30:38014] mod_wsgi (pid=6138): Exception occurred processing 
WSGI script '/usr/share/ipa/wsgi.py'.
  [Thu Sep 06 13:02:22.125877 2018] [wsgi:error] [pid 6138:tid 140075658061568] 
[remote 172.16.16.30:38014] Traceback (most recent call last):
  [Thu Sep 06 13:02:22.125898 2018] [wsgi:error] [pid 6138:tid 140075658061568] 
[remote 172.16.16.30:38014]   File "/usr/share/ipa/wsgi.py", line 57, in 
application
  [Thu Sep 06 13:02:22.125961 2018] [wsgi:error] [pid 6138:tid 140075658061568] 
[remote 172.16.16.30:38014] return api.Backend.wsgi_dispatch(environ, 
start_response)
  [Thu Sep 06 13:02:22.125972 2018] [wsgi:error] [pid 6138:tid 140075658061568] 
[remote 172.16.16.30:38014]   File 
"/usr/lib/python2.7/dist-packages/ipaserver/rpcserver.py", line 265, in __call__
  [Thu Sep 06 13:02:22.128833 2018] [wsgi:error] [pid 6138:tid 140075658061568] 
[remote 172.16.16.30:38014] return self.route(environ, start_response)
  [Thu Sep 06 13:02:22.128846 2018] [wsgi:error] [pid 6138:tid 140075658061568] 
[remote 172.16.16.30:38014]   File 
"/usr/lib/python2.7/dist-packages/ipaserver/rpcserver.py", line 277, in route
  [Thu Sep 06 13:02:22.128860 2018] [wsgi:error] [pid 6138:tid 140075658061568] 
[remote 172.16.16.30:38014] return app(environ, start_response)
  [Thu Sep 06 13:02:22.128872 2018] [wsgi:error] [pid 6138:tid 140075658061568] 
[remote 172.16.16.30:38014]   File 
"/usr/lib/python2.7/dist-packages/ipaserver/rpcserver.py", line 935, in __call__
  [Thu Sep 06 13:02:22.128881 2018] [wsgi:error] [pid 6138:tid 140075658061568] 
[remote 172.16.16.30:38014] self.kinit(user_principal, password, 
ipa_ccache_name)
  [Thu Sep 06 13:02:22.128886 2018] [wsgi:error] [pid 6138:tid 140075658061568] 
[remote 172.16.16.30:38014]   File 
"/usr/lib/python2.7/dist-packages/ipaserver/rpcserver.py", line 971, in kinit
  [Thu Sep 06 13:02:22.128892 2018] [wsgi:error] [pid 6138:tid 140075658061568] 
[remote 172.16.16.30:38014] pkinit_anchors=[paths.KDC_CERT, 
paths.KDC_CA_BUNDLE_PEM],
  [Thu Sep 06 13:02:22.128898 2018] [wsgi:error] [pid 6138:tid 140075658061568] 
[remote 172.16.16.30:38014]   File 
"/usr/lib/python2.7/dist-packages/ipalib/install/kinit.py", line 125, in 
kinit_armor
  [Thu Sep 06 13:02:22.133878 2018] [wsgi:error] [pid 6138:tid 140075658061568] 
[remote 172.16.16.30:38014] run(args, env=env, 

[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

[Sam Bull]

Also just started seeing this after updating from Ubuntu GNOME 16.04 to
Ubuntu 18.04. The only relevant thing I can think of, is that I may have
changed the default login manager to GDM. Otherwise, can't think of
anything that might have triggered this.

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1508146/+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 1788293] [NEW] package libglib2.0-dev 2.40.2-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Sam]

Public bug reported:

i've got gcc-5 installed so changes following that probably caused this.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libglib2.0-dev 2.40.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
Uname: Linux 4.2.0-42-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
Date: Tue Aug 21 15:14:46 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2018-08-21 (0 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.8
 apt  1.0.1ubuntu2.18
SourcePackage: glib2.0
Title: package libglib2.0-dev 2.40.2-0ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package third-party-packages trusty

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

Title:
  package libglib2.0-dev 2.40.2-0ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  i've got gcc-5 installed so changes following that probably caused
  this.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libglib2.0-dev 2.40.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Tue Aug 21 15:14:46 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.18
  SourcePackage: glib2.0
  Title: package libglib2.0-dev 2.40.2-0ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1788293/+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 1710060] Re: Sound Chipmunks on playback with Jabra Evolve 65 UC Headset

[Sam Edney]

For what its worth, I had this issue on Ubuntu 18.04 - but also on
Antergos 18.7.

It happens with all audio playback that I have tested so far - including
Slack, Firefox and Chrome audio.

Changing the sample rate in `/etc/pulse/daemon.conf` then running
`pulseaudio -k` also resolves things.

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

Title:
  Sound Chipmunks on playback with Jabra Evolve 65 UC Headset

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Fedora:
  Won't Fix

Bug description:
  Whenever I choose the Jabra Evolve 65 UC Headset as the playback
  device, there are sound chipmunks. The same was the case with Jabra
  Motion Headset as well. But those two headsets worked perfectly in
  Windows, Mac OS and Android.

  There was a workaround mentioned in
  https://bugzilla.redhat.com/show_bug.cgi?id=1282285 by editing the
  contents of /etc/pulseaudio/daemon.conf :

  Changing

   ;default-sample-rate=44100

  to

   default-sample-rate=48000

  and then running

   pulseaudio -k

  made the sound on Jabra good (no more chipmunks). Also, when I opened
  the Sound Settings with the changes in daemon.conf in place, there
  seems to be some distortions in headset sound, which goes away few
  seconds after I close the sound settings window.

  This problem should be fixed, as many new Linux users will find it
  difficult to edit files requiring root access, and those who do not
  use command line won't be okay with it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Uname: Linux 4.4.0-89-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   itachi10880 F...m pulseaudio
   /dev/snd/controlC2:  itachi10880 F pulseaudio
   /dev/snd/controlC1:  itachi10880 F pulseaudio
   /dev/snd/controlC0:  itachi10880 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Aug 10 21:11:18 2017
  InstallationDate: Installed on 2016-08-27 (349 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: SEx
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-08-10T21:07:55.637386

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

Re: [Touch-packages] [Bug 1677881] Re: Missing dep8 tests

[Sam Hartman]

Hi.
For whatever reason I'm not getting mail when an MP is opened in the
krb5 gitlab.
In general, i think Debian uses its BTS as  the todo system of record
moreso than gitlab MPs.  I know for myself and I suspect a lot of other
debian developers, a wishlist bug against a package would be the best
way for me to consider a patch.

That said, since  I'm also looking at launchpad, I've reviewed the MP.

Other than the license question I raised there, I think this is a great
thing to include.
I've been swamped by non-Debian life events, but I'm mostly through that
and will dedicate a day to catching up on Debian in the next couple of
weeks.

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

Title:
  Missing dep8 tests

Status in krb5 package in Ubuntu:
  In Progress

Bug description:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA256

  As of March 29, 2017, this source package did not contain dep8 tests in
  the current development release of Ubuntu, named Zesty. This was
  determined by running `pull-lp-source krb5 zesty` and then
  checking for the existence of 'debian/tests/' and
  'debian/tests/control'.

  Test automation is essential to higher levels of quality and confidence
  in updates to packages. dep8 tests [1] specify how automatic testing can
  be integrated into packages and then run by package maintainers before
  new uploads.

  This defect is to report the absence of these tests and to report the
  opportunity as a potential item for development by both new and
  experienced contributors.

  [1] http://packaging.ubuntu.com/html/auto-pkg-test.html

   affects ubuntu/krb5
   status new
   importance wishlist
   tag needs-dep8

  - ---
  Joshua Powers
  Ubuntu Server
  Canonical Ltd

  -BEGIN PGP SIGNATURE-

  iQIcBAEBCAAGBQJY3YGVAAoJEIP8BxPaZgwlCIEP/36uotG3iLNIh5/fPc2FDzwV
  hqK5CLKbCLqlX7RmzkSzO303hJ051Q6uWIb1ZcnvZShO4h2mrQfyXXmWBXO3So/2
  imYe6Pg3j9v1aNYCxpvWKL6VIpN5beADCoWlAS9P89qSIdyEYTiaL6HFHzbA5hck
  7rtMhHnzw16mkT+ttZ39f4kqZ9jqqV1je0lPyCI3L+UicswkdeymHeZAZSkG13lW
  uSi5SVLFDpDeWq/23Ohj0tacLZbpBKG4vScRQ7+Me3ieGnC0gii8C1luXGPWpS9v
  CvW1JLPbuo3yHooBzJw6YAYI2TiWyNjtO2/9ESPxcmn+tPn7iXoeTBIstlQC2iY0
  fvoUrmxUjSJafgCyZE1NNy8gTlFLObpMP/qZPtw7YLKaD9t64+JZUK4vzSNr1tY5
  ltCXFf0mneUrUjTOS1Io+vigiBbMEIFuUjEXT3DxGEybf8rrl6fJdCD++1L0NTXR
  ImfhCBgSEYBrluRLHu1tGftin7wKgarl7uWLzZxGeJ/MiXkX0eWIgOVoXaQq6gnR
  HR7XF1x9x1VJYi2CGMrDDWSHWDHgXC5UOcBz/KLMSPMcyQakXyRrw1Hqplj3G3PM
  OkqR8uLWUYfTZvrVvnSj4jJPNRSiBOz95FFbfMZ43yxoE5F6QBhztwgcJC8/g+bn
  zu94s0Hiyv+yxmptMwgX
  =ibX0
  -END PGP SIGNATURE-

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1677881/+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 574712] Re: pelicula.mkv doesn't play

[sam tygier]

Closing an old bug. Plays fine in totem in ubuntu 18.04

** Changed in: gst-plugins-good1.0 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  pelicula.mkv doesn't play

Status in GStreamer:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released

Bug description:
  Not work totem with movie. With VLC work fine

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: libgstreamer0.10-0 0.10.28-1
  Uname: Linux 2.6.34-020634rc6-generic i686
  Architecture: i386
  Date: Mon May  3 15:14:49 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
  ProcEnviron:
   LANG=es_CL.utf8
   SHELL=/bin/bash
  SourcePackage: gstreamer0.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/574712/+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 1730116] Re: gstreamer's flac encoder creates corrupt files with sound-juicer

[sam tygier]

The file corruption is fixed. Now just back to missing the md5sums.

** Changed in: gst-plugins-good1.0 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  gstreamer's flac encoder creates corrupt files with sound-juicer

Status in gst-plugins-good:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released

Bug description:
  When ripping a CD to the FLAC format with Sound Juicer (and based on
  the upstream bug also Rhythmbox, and maybe also affects other
  applications), it creates corrupted files (e.g. when you test them
  with "flac -t").

To manage notifications about this bug go to:
https://bugs.launchpad.net/gst-plugins-good/+bug/1730116/+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 1742946] Re: "gio monitor" does not work

[sam tygier]

I can confirm that it does not work in ubuntu 17.10, but does work in
Fedora 27 (which has glib 2.54.3
http://ftp.gnome.org/pub/gnome/sources/glib/2.54/glib-2.54.3.news)

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

Title:
  "gio monitor" does not work

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  # ls -l /etc/adduser.conf
  -rw-r--r-- 1 root root 2981 Mar 11  2012 /etc/adduser.conf
  # gio monitor file:///etc/adduser.conf
  gio: No locations given

  Usage:
gio monitor [OPTION…] [LOCATION...]

  Monitor files or directories for changes.

  Options:
-d, --dir=LOCATIONMonitor a directory (default: depends on type)
-f, --file=LOCATION   Monitor a file (default: depends on type)
-D, --direct=LOCATION Monitor a file directly (notices changes made via 
hardlinks)
-s, --silent=LOCATION Monitors a file directly, but doesn’t report 
changes
-n, --no-movesReport moves and renames as simple 
deleted/created events
-m, --mounts  Watch for mount events

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libglib2.0-bin 2.54.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 12 14:29:42 2018
  InstallationDate: Installed on 2012-03-12 (2131 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120311)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/tcsh
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1742946/+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 840942] Re: set_size_request is ignored [update-manager details is one line]

[sam tygier]

Still an issue in Bionic. Can't see how to add the release. If I
understand comment #31 the bug is in update-manager now not apt-daemon

** Also affects: update-manager (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: update-manager (Ubuntu Oneiric)

** No longer affects: update-manager (Ubuntu Precise)

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

Title:
  set_size_request is ignored [update-manager details is one line]

Status in aptdaemon package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in update-manager package in Ubuntu:
  New
Status in aptdaemon source package in Oneiric:
  Won't Fix
Status in gtk+3.0 source package in Oneiric:
  Won't Fix
Status in aptdaemon source package in Precise:
  Fix Released
Status in gtk+3.0 source package in Precise:
  Confirmed

Bug description:
  update-manager details is one line (the terminal when expanding the
  details expander). This way you can't see what happens and is the
  function useless

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: update-manager 1:0.152.17
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic i686
  Architecture: i386
  Date: Sun Sep  4 14:04:42 2011
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  SourcePackage: update-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/840942/+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 511086] Re: Missing some Czech unicode characters in selected text

[sam tygier]

Seems to work fine in current evince 3.26.0-3 with poppler
0.57.0-2ubuntu5

** Changed in: poppler (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Missing some Czech unicode characters in selected text

Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: evince

  I have a small problem with Document Viewer 2.28.1 (evince). I have 
downloaded the time table (pdf file) of the Prague bus 165 
(http://jrportal.dpp.cz/jrportal/LineList.aspx?t=3=5=1=165=2010-01-04)
 in Firefox and it was opened by Document Viewer. It looked well including 
special Czech character. But when I selected the text by mouse, some Czech 
characters were missing. Like 'ř', 'š' etc. For example "Přístav Radotín" 
looked like 'P ístav Radotín' when selected etc. It seem that some fonts are 
missing and it is all but I think things like this should work automatically on 
Ubuntu.
  (Ubuntu 9.10, Czech language)

  ProblemType: Bug
  Architecture: i386
  Date: Fri Jan 22 09:55:54 2010
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/evince
  Package: evince 2.28.1-0ubuntu1.2
  ProcEnviron:
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
  SourcePackage: evince
  Uname: Linux 2.6.31-17-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/511086/+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 1730116] Re: gstreamer's flac encoder creates corrupt files with sound-juicer

[sam tygier]

That patch works great. Is it worth me trying to do and SRU? Or
requesting a backport of 1.12.4?

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

Title:
  gstreamer's flac encoder creates corrupt files with sound-juicer

Status in gst-plugins-good:
  Confirmed
Status in gst-plugins-good1.0 package in Ubuntu:
  Triaged

Bug description:
  When ripping a CD to the FLAC format with Sound Juicer (and based on
  the upstream bug also Rhythmbox, and maybe also affects other
  applications), it creates corrupted files (e.g. when you test them
  with "flac -t").

To manage notifications about this bug go to:
https://bugs.launchpad.net/gst-plugins-good/+bug/1730116/+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 1732074] [NEW] many errors upgrading to 17

[Sam]

Public bug reported:

will not update

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.5
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
Date: Tue Nov 14 00:07:39 2017
DistUpgraded: 2017-11-13 22:46:46,902 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:98e4] (rev c1) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:81b9]
InstallationDate: Installed on 2017-11-13 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: HP 24-b010
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=257f9bf8-7008-4b57-92ce-84998a9a4d88 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to zesty on 2017-11-14 (0 days ago)
dmi.bios.date: 04/14/2017
dmi.bios.vendor: AMI
dmi.bios.version: F.30
dmi.board.name: 81B9
dmi.board.vendor: HP
dmi.board.version: 1000
dmi.chassis.type: 13
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnAMI:bvrF.30:bd04/14/2017:svnHP:pn24-b010:pvr:rvnHP:rn81B9:rvr1000:cvnHP:ct13:cvr:
dmi.product.name: 24-b010
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Tue Nov 14 00:02:52 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.3
xserver.video_driver: amdgpu

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu zesty

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

Title:
  many errors upgrading to 17

Status in xorg package in Ubuntu:
  New

Bug description:
  will not update

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  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
  Date: Tue Nov 14 00:07:39 2017
  DistUpgraded: 2017-11-13 22:46:46,902 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:98e4] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:81b9]
  InstallationDate: Installed on 2017-11-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP 24-b010
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=257f9bf8-7008-4b57-92ce-84998a9a4d88 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to zesty on 2017-11-14 (0 days ago)
  dmi.bios.date: 04/14/2017
  dmi.bios.vendor: AMI
  dmi.bios.version: F.30
  dmi.board.name: 81B9
  dmi.board.vendor: HP
  dmi.board.version: 1000
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.30:bd04/14/2017:svnHP:pn24-b010:pvr:rvnHP:rn81B9:rvr1000:cvnHP:ct13:cvr:
  dmi.product.name: 24-b010
  

[Touch-packages] [Bug 1610534] Re: Open tabs keep getting forgotten

[Sam Bull]

So, I think I've found the cause to atleast part of the issue. Recently,
the app broke again failing to remember my tabs at all.

Looking in my files, I noticed a ~/.local/share/webbrowser-
app/session.json.lock file, even though the app wasn't running. The
actual session file was absolutely fine, and still contained my session
from a couple of weeks earlier, the app just wasn't loading it due to
the lock file. Deleting the lock file had my old session back up and
running.

Before I deleted it, I had a look at the lock file, and found that it
was an empty file. I would have expected the app to write its PID into
the lock file when creating it. Then, when the app opens and sees a lock
file, it can check if the given PID exists, and if so exit. If the
process no longer exists, then it can take over ownership of the lock
file.

Perhaps implementing this kind of basic behaviour would be enough to fix
this issue, as it looks like it may just be a crashing application
failing to remove its lock file.

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

Title:
  Open tabs keep getting forgotten

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  The browser app keeps forgetting my open tabs on a semi-regular basis.
  It seems to happen to me every couple of weeks or so, I will open the
  app and all my tabs are gone. This is very frustrating, as there is no
  easy way to recover them.

  I think it may actually happen more frequently when there are around
  7/8 tabs or more open.

  OTA-12 (and previous versions), mako.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1610534/+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 1702676] [NEW] package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Sam Bond]

Public bug reported:

sbondarev@sbondarev-desktop:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libpango1.0-0 libpangox-1.0-0 linux-headers-4.4.0-78 
linux-headers-4.4.0-78-generic linux-headers-4.4.0-79 
linux-headers-4.4.0-79-generic linux-image-4.4.0-78-generic 
linux-image-4.4.0-79-generic
  linux-image-extra-4.4.0-78-generic linux-image-extra-4.4.0-79-generic 
linux-signed-image-4.4.0-78-generic linux-signed-image-4.4.0-79-generic
Use 'sudo apt autoremove' to remove them.
The following packages have been kept back:
  libmirclient9
The following packages will be upgraded:
  adobe-flash-properties-gtk adobe-flashplugin gnome-software 
gnome-software-common grub-common grub-efi-amd64 grub-efi-amd64-bin 
grub-efi-amd64-signed grub2-common less libblkid1 libepoxy0 libfdisk1
  libmirprotobuf3 libmount1 libnautilus-extension1a libpulse-mainloop-glib0 
libpulse0 libpulsedsp libsmartcols1 libuuid1 libuuid1:i386 linux-firmware mount 
nautilus nautilus-data opera-stable pulseaudio
  pulseaudio-module-bluetooth pulseaudio-module-x11 pulseaudio-utils 
ubuntu-software uuid-runtime yarn
34 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
1 not fully installed or removed.
Need to get 0 B/108 MB of archives.
After this operation, 6 951 kB disk space will be freed.
Do you want to continue? [Y/n] y
Extracting templates from packages: 100%
Preconfiguring packages ...
Setting up util-linux (2.27.1-6ubuntu3.3) ...
insserv: warning: script 'S99LicenseServer' missing LSB tags and overrides
insserv: warning: script 'IntelliJLicenseServer' missing LSB tags and overrides
insserv: There is a loop at service plymouth if started
insserv: There is a loop between service plymouth and procps if started
insserv:  loop involving service procps at depth 2
insserv:  loop involving service udev at depth 1
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting IntelliJLicenseServer depends on plymouth and therefore on 
system facility `$all' which can not be true!
insserv: Starting 

[Touch-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

[Sam Banks]

On 17.04 running 4.10.0-20-generic I get it loud in one ear and quiet in
the other.

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

Title:
  [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
  while

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I'm experiencing a strange behavior with a headphone jack on my
  laptop.

  I have an external audio speaker connected to it. When I disconnect the 
speaker and reconnect it again it stops working.
  Even more, laptop audio stops working too. And after the reboot, I don't even 
see any of the audio devices.

  I've googled a lot and tried different fixes from forums with no luck.
  After a while, I've accidentally discovered that putting the laptop to
  the sleep mode and rebooting system after brings audio back to live.
  Even more, if speakers were attached during this sleep-reboot
  procedure, they are starting to work as well.

  However, after the next reboot speakers are not working again. And if
  I will plug them out and in - problem with completely missing audio
  returns.

  P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
  hibernation made me believe that it's somehow related. But after
  uninstalling this package nothing really changed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   kop3224 F...m pulseaudio
   /dev/snd/controlC0:  kop3224 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 26 12:17:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Встроенное аудио - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Sound works for a while, then breaks
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after 
a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575078/+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 1690962] [NEW] [XPS 15 9560, Realtek ALC3266, Black Headphone Out, Left] Audio Quiet in Left Channel

[Sam Banks]

Public bug reported:

When listening to music through the headphone jack it is normal in the
right channel but very quiet in the left.

Have tried different headphones with the same result.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   sbanks 1581 F...m pulseaudio
 /dev/snd/pcmC0D0p:   sbanks 1581 F...m pulseaudio
 /dev/snd/controlC0:  sbanks 1581 F pulseaudio
CurrentDesktop: GNOME
Date: Tue May 16 10:51:17 2017
InstallationDate: Installed on 2017-05-15 (0 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: None of the above
Title: [XPS 15 9560, Realtek ALC3266, Black Headphone Out, Left] Playback 
problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/21/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.2
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.2:bd03/21/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.name: XPS 15 9560
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

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

Title:
  [XPS 15 9560, Realtek ALC3266, Black Headphone Out, Left] Audio Quiet
  in Left Channel

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When listening to music through the headphone jack it is normal in the
  right channel but very quiet in the left.

  Have tried different headphones with the same result.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   sbanks 1581 F...m pulseaudio
   /dev/snd/pcmC0D0p:   sbanks 1581 F...m pulseaudio
   /dev/snd/controlC0:  sbanks 1581 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue May 16 10:51:17 2017
  InstallationDate: Installed on 2017-05-15 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: None of the above
  Title: [XPS 15 9560, Realtek ALC3266, Black Headphone Out, Left] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.2
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.2:bd03/21/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

Re: [Touch-packages] [Bug 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS

[Sam Hartman]

> "Joshua" == Joshua Powers  writes:

Joshua> If we want to fix this in zesty, then a release with only
Joshua> the bug fixes would be desired. That could be SRU'ed
Joshua> assuming it is not too big of a change such that it would
Joshua> limit the exposure to new issues or changes in
Joshua> features/functionality.

Hi.
I uploaded 1.15-2 to Debian experimental.
It includes two fixes to regressions from jessie (also regressions in
Ubuntu):
1) this bug -- OTP users don't work with DNS discovery

2) Another upstream issue where enhancements to the IPv6 support break
IPv4 only systems.
I haven't seen Debian reports of that issue, but code changes are
minimal and are easy to audit for impact.

I'm not volunteering to file the SRU paperwork on the Ubuntu side, but
I'm happy to provide technical assistance for anyone who wants to do
that.
I believve that a sync of 1.15-2 over 1.15-1 would be appropriate and in
terms of code change complexity would be within Ubuntu's policies.

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

Title:
  krb5-user: kinit fails for OTP user when using kdc discovery via DNS

Status in krb5 package in Ubuntu:
  Triaged
Status in krb5 package in Debian:
  New

Bug description:
  Zesty is now affected, please see the debian bug 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307
  and upstream bug http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554

  Would it be possible to get 1.15.1 (already released upstream) in
  zesty/zesty-updates?

  Thanks
  Jochen

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

Re: [Touch-packages] [Bug 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS

[Sam Hartman]

> "Joshua" == Joshua Powers  writes:

Joshua> If we want to fix this in zesty, then a release with only
Joshua> the bug fixes would be desired. That could be SRU'ed
Joshua> assuming it is not too big of a change such that it would
Joshua> limit the exposure to new issues or changes in
Joshua> features/functionality.

OK, I'll look at pulling a bugfix release into experimental now.  I sure
hope stretch releases before  17.10:-)

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

Title:
  krb5-user: kinit fails for OTP user when using kdc discovery via DNS

Status in krb5 package in Ubuntu:
  Triaged
Status in krb5 package in Debian:
  New

Bug description:
  Zesty is now affected, please see the debian bug 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307
  and upstream bug http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554

  Would it be possible to get 1.15.1 (already released upstream) in
  zesty/zesty-updates?

  Thanks
  Jochen

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

Re: [Touch-packages] [Bug 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS

[Sam Hartman]

I can put something in debian experimental if that makes the sync
easier.
So, you'd prefer just the Debian 1.15-1 with bug fixes rather than a
1.15.1?

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

Title:
  krb5-user: kinit fails for OTP user when using kdc discovery via DNS

Status in krb5 package in Ubuntu:
  Triaged
Status in krb5 package in Debian:
  New

Bug description:
  Zesty is now affected, please see the debian bug 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307
  and upstream bug http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554

  Would it be possible to get 1.15.1 (already released upstream) in
  zesty/zesty-updates?

  Thanks
  Jochen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1683237/+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 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS

[Sam Hartman]

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

** Also affects: krb5 (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307
   Importance: Unknown
   Status: Unknown

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

Title:
  krb5-user: kinit fails for OTP user when using kdc discovery via DNS

Status in krb5 package in Ubuntu:
  New
Status in krb5 package in Debian:
  Unknown

Bug description:
  Zesty is now affected, please see the debian bug 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307
  and upstream bug http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554

  Would it be possible to get 1.15.1 (already released upstream) in
  zesty/zesty-updates?

  Thanks
  Jochen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1683237/+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 1679872] [NEW] When boot from grub, the display goes blank and can hear login page come up because of sound but display continues to be blank

[Sam Shepard]

Public bug reported:

Since I upgraded to 16.04, my display does not always come up when I
boot. The grub land display comes up for selection of what to boot, then
after choosing, the display goes blank.  I can hear when system loads to
logon page because system makes the alert sound for when that page comes
up, but my screen continues to be blank.  I am guessing that this has
something to do with lightdm, but I have very little skills for delving
into such issues.  Sometimes I can close the laptop lib and open it,
then display will come on, but this is not always the case:

lsb_release -rd
Description:Ubuntu 16.04.2 LTS
Release:16.04

apt-cache policy lightdm
lightdm:
  Installed: 1.18.3-0ubuntu1
  Candidate: 1.18.3-0ubuntu1
  Version table:
 *** 1.18.3-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1.18.1-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.3-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-45.48~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Apr  4 19:33:27 2017
InstallationDate: Installed on 2017-04-01 (3 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  When boot from grub, the display goes blank and can hear login page
  come up because of sound but display continues to be blank

Status in lightdm package in Ubuntu:
  New

Bug description:
  Since I upgraded to 16.04, my display does not always come up when I
  boot. The grub land display comes up for selection of what to boot,
  then after choosing, the display goes blank.  I can hear when system
  loads to logon page because system makes the alert sound for when that
  page comes up, but my screen continues to be blank.  I am guessing
  that this has something to do with lightdm, but I have very little
  skills for delving into such issues.  Sometimes I can close the laptop
  lib and open it, then display will come on, but this is not always the
  case:

  lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy lightdm
  lightdm:
Installed: 1.18.3-0ubuntu1
Candidate: 1.18.3-0ubuntu1
Version table:
   *** 1.18.3-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.18.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-45.48~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  4 19:33:27 2017
  InstallationDate: Installed on 2017-04-01 (3 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1679872/+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 1671003] Re: unable to "apt-get install libsystemd-dev"

[Sam Hamilton]

Ok it was a clean install on Aliyun.com, I just tried on a clean box
elsewhere and its fine. Sorry about the false alarm.

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

Title:
  unable to "apt-get install libsystemd-dev"

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  1)
  # lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  2) 
  # apt-cache policy libsystemd-dev
  libsystemd-dev:
Installed: (none)
Candidate: 229-4ubuntu16
Version table:
   229-4ubuntu16 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   229-4ubuntu10 500
  500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   229-4ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  
  3) I expected the package to be installed

  4) 
  # apt-get install libsystemd-dev
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libsystemd-dev : Depends: libsystemd0 (= 229-4ubuntu16) but 229-4ubuntu17 is 
to be installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671003/+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 1302004] Re: Indicator-datetime doesn't list in-progress events

[Sam Bull]

It might be an idea to create separate bug reports for each condition
that still fails to show all events.

Another one, if I remember correctly, is multi-day events, I believe it
only shows the event on it's start date and it's end date. e.g. event
starts Mon and ends Friday, it will not appear in indicator Tue-Thu.

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

Title:
  Indicator-datetime doesn't list in-progress events

Status in Canonical System Image:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  This bug is related to this bug: Bug #1293646 (Which is marked as fix
  released)

  With latest update of indicator (13.10.0+14.04.20140328-0ubuntu1) it
  lists all events for all past selected dates properly (which was fixed
  in bug Bug #1293646) except today's date. When I click on any past
  date in calendar it shows:

  1. all all-day events for the day.
  2. all events with time for the day
  3. upcoming (future) all-day events
  4. upcoming (future) events with time

  But when I click on today's date it only shows:

  1. future all day events
  2. future events with time

  I still have to click on previous day's date to find out all all-day
  events for today.

  The behavior (showing all events for a day) should be same for any
  date, including today's date.

  : "If there are more
  than five, the events shown should be, in order of priority, * any
  events that start or end (a) for today, after the current minute, or
  (b) for any other date, at any time on that date, * any full-day
  events that span all of the selected date..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1302004/+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 1671003] [NEW] unable to "apt-get install libsystemd-dev"

[Sam Hamilton]

Public bug reported:

1)
# lsb_release -rd
Description:Ubuntu 16.04.2 LTS
Release:16.04

2) 
# apt-cache policy libsystemd-dev
libsystemd-dev:
  Installed: (none)
  Candidate: 229-4ubuntu16
  Version table:
 229-4ubuntu16 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
 229-4ubuntu10 500
500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages
 229-4ubuntu4 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages


3) I expected the package to be installed

4) 
# apt-get install libsystemd-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libsystemd-dev : Depends: libsystemd0 (= 229-4ubuntu16) but 229-4ubuntu17 is 
to be installed

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

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

Title:
  unable to "apt-get install libsystemd-dev"

Status in systemd package in Ubuntu:
  New

Bug description:
  1)
  # lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  2) 
  # apt-cache policy libsystemd-dev
  libsystemd-dev:
Installed: (none)
Candidate: 229-4ubuntu16
Version table:
   229-4ubuntu16 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   229-4ubuntu10 500
  500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   229-4ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  
  3) I expected the package to be installed

  4) 
  # apt-get install libsystemd-dev
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libsystemd-dev : Depends: libsystemd0 (= 229-4ubuntu16) but 229-4ubuntu17 is 
to be installed

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

Re: [Touch-packages] [Bug 1643708] Re: Add SPNEGO special case for NTLMSSP+MechListMIC

[Sam Hartman]

>>>>> "Robie" == Robie Basak <1643...@bugs.launchpad.net> writes:

Robie> @Bruce Thank you for detailing your testing. In your test
Robie> suite, do you cover any interoperability with SPNEGO but
Robie> not-Windows, whether in integration or code path coverage?
Robie> That's the use case I'm concerned about - that someone will
Robie> come along and tell us that we regressed SPNEGO against
Robie> WebSphere or something because we focused on just testing
Robie> Windows.

Hi.
As I understand it, this is a backport of an upstream change.
It's always possible there is an interop regression.
In this instance though, given where the patch comes from originally,
and that it's been in upstream releases for a while, I think you're
relatively safe.
SPNEGO interop is really hard to test though; it's not something that
you can get good coverage for without a specific interoperability lab
and careful test plans.

I don't know if upstream has done that for this patch, although I do
have high confidence that people do interop tests against the upstream
version.

So, while I think your concern is reasonable, I'd urge you to consider
that you're setting a really high bar here for backporting a patch that
an interoperability-conscious upstream has vetted.
Yes, the MIT folks have messed up interop (just as everyone else), but
they are fairly careful and conservative.

If you do want to do interop testing, the interesting cases to cover
are:

* Initiator prefers Kerberos; other side does not support it

* Acceptor prefers Kerberos, initiator does not support it

* Initiator prefers NTLM and some non-Kerberos third mechanism

* Acceptor prefers NTLM, doesn't have Kerberos, but does have some third
  mechanism

I think setting all that up is a good week's worth of work with someone
who really knows what they are doing.

--Sam

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

Title:
  Add SPNEGO special case for NTLMSSP+MechListMIC

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Trusty:
  Fix Committed
Status in krb5 source package in Xenial:
  Fix Committed
Status in krb5 source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  MS-SPNG section 3.3.5.1 documents an odd behavior the SPNEGO layer
  needs to implement specifically for the NTLMSSP mechanism.  This is
  required for compatibility with Windows services.

  Upstream commit:
  https://github.com/krb5/krb5/commit/cb96ca52a3354e5a0ea52e12495ff375de54f9b7

  We've run into this issue with Linux to Windows negotiation with
  encrypted http using GSSAPI.

  [Test Case]

  create a file with some credentials:

  $ echo F23:guest:guest > ~/ntlmcreds.txt
  $ export NTLM_USER_FILE=~/ntlmcreds.txt
  $ python
  import gssapi

  spnego = gssapi.raw.oids.OID.from_int_seq('1.3.6.1.5.5.2')
  c = gssapi.creds.Credentials(mechs=[spnego], usage='initiate')
  tname = gssapi.raw.names.import_name("F23/server", 
name_type=gssapi.raw.types.NameType.hostbased_service)
  ac = gssapi.creds.Credentials(mechs=[spnego], usage='accept')

  seci = gssapi.SecurityContext(creds=c, name=tname, mech=spnego, 
usage='initiate')
  seca = gssapi.SecurityContext(creds=ac, usage='accept')
  it = seci.step(token=None)
  ot = seca.step(token=it)
  it = seci.step(token=ot)
  ot = seca.step(token=it)
  it = seci.step(token=ot)

  e = seci.wrap("Secrets", True)
  o = seca.unwrap(e.message)

  o.message
  'Secrets'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1643708/+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 1637779] Re: ext4 filesystem fails randomly with checksum error

[Sam Wisdom]

Also got this issue after using ext2fsd (dual-boot), never had any
issues before

I have attached my dumpe2fs output

** Attachment added: "dumpe2fs.txt"
   
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1637779/+attachment/4790759/+files/dumpe2fs.txt

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

Title:
  ext4 filesystem fails randomly with checksum error

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.10
  Release:  16.10

  package version:
  linux-image-4.8.0-26-generic:
Installed: 4.8.0-26.28
Candidate: 4.8.0-26.28
Version table:
   *** 4.8.0-26.28 500
  500 http://sk.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu yakkety-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  
  fresh installation of Ubunut 16.10, all updates included

  While I am working with system after few minutes root filesystem /dev/sdb5 
switches into readonly mode
  in dmesg is this:

  [  304.921552] EXT4-fs error (device sdb5): ext4_iget:4476: inode #24577: 
comm updatedb.mlocat: checksum invalid
  [  304.925565] Aborting journal on device sdb5-8.
  [  304.926507] EXT4-fs (sdb5): Remounting filesystem read-only
  [  304.927416] EXT4-fs error (device sdb5): ext4_journal_check_start:56: 
Detected aborted journal
  [  304.943408] EXT4-fs error (device sda1): ext4_iget:4476: inode #12: comm 
updatedb.mlocat: checksum invalid

  when it happens I must do fsck f /dev/sdb1 once, second time it says
  everything is fine. after reboot when I start dto do something it soon
  happens again

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

Re: [Touch-packages] [Bug 1644595] Re: krb5-1.13.2+dfsg-5 source contains source subject to the aladdin license

[Sam Hartman]

As a FYI, upstream has relicensed the file under their standard license
with permission from the author.
Coming to Debian soon.

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

Title:
  krb5-1.13.2+dfsg-5 source contains source subject to the aladdin
  license

Status in Kerberos:
  Unknown
Status in krb5 package in Ubuntu:
  Confirmed

Bug description:
  The krb5-1.13.2+dfsg-5 package source contains a file autolock.hxx  in
  the directory
  
krb5-1.13.2+dfsg-5\krb5_1.13.2+dfsg.orig\krb5-1.13.2+dfsg\src\ccapi\common\win\OldCC.
  Although not declared in any other licensing file for this package the
  file contains comments indicating its subject to the Aladdin license
  which has implications for any commercial distribution of the
  software, specifically:

  “2(a) Distribution of the Program or any work based on the Program by
  a commercial organization to any third party is prohibited if any
  payment is made in connection with such distribution, whether directly
  (as in payment for a copy fo the Program) or indirectly (as in payment
  for some service related to the Program, or payment for some product
  or service that includes a copy of the Program ‘without charge’ . . .”

  This file clearly is not needed or used for any Linux build as it
  appears specific to windows.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kerberos/+bug/1644595/+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 1641867] [NEW] GtkMenu: Submenu navigation triangle doesn't work

[Sam Douglas]

Public bug reported:

The navigation triangle code for keeping a submenu open when the mouse
is moving diagonally toward it is broken due to incorrect rounding.

This was reported upstream at:
https://bugzilla.gnome.org/show_bug.cgi?id=710388

The attached patch (also submitted upstream) rounds the cursor location
when calculating the navigation triangle bounds.

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "Fix for navigation triangle bug"
   
https://bugs.launchpad.net/bugs/1641867/+attachment/4777560/+files/submenu_navigation_region_fix.patch

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

Title:
  GtkMenu: Submenu navigation triangle doesn't work

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  The navigation triangle code for keeping a submenu open when the mouse
  is moving diagonally toward it is broken due to incorrect rounding.

  This was reported upstream at:
  https://bugzilla.gnome.org/show_bug.cgi?id=710388

  The attached patch (also submitted upstream) rounds the cursor
  location when calculating the navigation triangle bounds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1641867/+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 1623666] Re: iOS10 will not connect to Ubuntu

[Sam Gleske]

J McDonald, I recommend you learning more about public key
infrastructure.  Essentially, encryption and security have different
options available to it (called algorithms and parameters to said
algorithms).  libimobiledevice, using the GnuTLS library, specified
incompatible options for it to work in iOS 10.  When it was built with
another library (OpenSSL instead of GnuTLS), it worked.

TL;DR Ubuntu used GnuTLS version of libimobiledevice which had the bug
and said bug has was fixed in libimobiledevice.

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

Title:
  iOS10 will not connect to Ubuntu

Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS10 device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice:

  https://github.com/libimobiledevice/libimobiledevice/issues/327

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1623666/+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 1639852] [NEW] Phone button appears on non-number messages

[Sam Bull]

Public bug reported:

When looking at text messages from a company, which is identified by
name rather than phone number, the phone button is still present and
will open the dialer app with no number.

I'd expect the phone button to be removed when there is no phone number
present.

** Affects: messaging-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Phone button appears on non-number messages

Status in messaging-app package in Ubuntu:
  New

Bug description:
  When looking at text messages from a company, which is identified by
  name rather than phone number, the phone button is still present and
  will open the dialer app with no number.

  I'd expect the phone button to be removed when there is no phone
  number present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1639852/+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 1623666] Re: iOS10 will not connect to Ubuntu

[Sam Gleske]

This issue has been resolved after working with upstream maintainers.

See https://gitlab.com/gnutls/gnutls/issues/145

For the resolution see
https://github.com/libimobiledevice/libimobiledevice/issues/413

** Bug watch added: github.com/libimobiledevice/libimobiledevice/issues #413
   https://github.com/libimobiledevice/libimobiledevice/issues/413

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

Title:
  iOS10 will not connect to Ubuntu

Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS10 device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice:

  https://github.com/libimobiledevice/libimobiledevice/issues/327

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1623666/+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 1623666] Re: iOS10 will not connect to Ubuntu

[Sam Gleske]

Nikos, patch didn't work.  I commented in
https://gitlab.com/gnutls/gnutls/issues/145

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

Title:
  iOS10 will not connect to Ubuntu

Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS10 device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice:

  https://github.com/libimobiledevice/libimobiledevice/issues/327

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1623666/+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 1623666] Re: iOS10 will not connect to Ubuntu

[Sam Gleske]

Nikos, I will try your patch this evening and report back (it is morning
for me right now so I must work).

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

Title:
  iOS10 will not connect to Ubuntu

Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS10 device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice:

  https://github.com/libimobiledevice/libimobiledevice/issues/327

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1623666/+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 1623666] Re: iOS10 will not connect to Ubuntu

[Sam Gleske]

I reported the issue to the GnuTLS project -
https://gitlab.com/gnutls/gnutls/issues/145

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

Title:
  iOS10 will not connect to Ubuntu

Status in gnutls28 package in Ubuntu:
  New
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS10 device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice:

  https://github.com/libimobiledevice/libimobiledevice/issues/327

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1623666/+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 1623666] Re: iOS10 will not connect to Ubuntu

[Sam Gleske]

** Tags added: xenial

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

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

Title:
  iOS10 will not connect to Ubuntu

Status in gnutls28 package in Ubuntu:
  New
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS10 device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice:

  https://github.com/libimobiledevice/libimobiledevice/issues/327

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1623666/+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 1623666] Re: iOS10 will not connect to Ubuntu

[Sam Gleske]

I am using Ubuntu 16.04.

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

Title:
  iOS10 will not connect to Ubuntu

Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS10 device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice:

  https://github.com/libimobiledevice/libimobiledevice/issues/327

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1623666/+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 1623666] Re: iOS10 will not connect to Ubuntu

[Sam Gleske]

The libimobiledevice package for Ubuntu was built with --disable-openssl
which forces GnuTLS. GnuTLS does not work with the recent iOS10 update.

Solution: rebuild the package so that it links against OpenSSL again.
This will resolve issues connecting to iOS 10 devices.

I tested the latest development version of GnuTLS (@ commit
1e84b90feed97ee458b7113665300e6bc444798f of master HEAD) and it does not
work with iOS 10 devices.

Upstream issue reference:
https://github.com/libimobiledevice/ifuse/issues/32

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

Title:
  iOS10 will not connect to Ubuntu

Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS10 device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice:

  https://github.com/libimobiledevice/libimobiledevice/issues/327

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1623666/+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 1623666] Re: iOS10 will not connect to Ubuntu

[Sam Gleske]

I actually discovered the root cause.  GnuTLS doesn't work with iOS.
Rebuilding the package using OpenSSL resolves this issue.

** Bug watch added: github.com/libimobiledevice/ifuse/issues #32
   https://github.com/libimobiledevice/ifuse/issues/32

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

Title:
  iOS10 will not connect to Ubuntu

Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS10 device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice:

  https://github.com/libimobiledevice/libimobiledevice/issues/327

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1623666/+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 1638177] Re: libimobiledevice: GnuTLS does not work with iOS10

[Sam Gleske]

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

** This bug has been marked a duplicate of bug 1623666
   iOS10 will not connect to Ubuntu

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

Title:
  libimobiledevice: GnuTLS does not work with iOS10

Status in libimobiledevice package in Ubuntu:
  New

Bug description:
  Problem:
  The libimobiledevice package for Ubuntu was built with --disable-openssl 
which forces GnuTLS.  GnuTLS does not work with the recent iOS10 update.

  Solution: rebuild the package so that it links against OpenSSL again.
  This will resolve issues connecting to iOS 10 devices.

  I tested the latest development version of GnuTLS (@ commit
  1e84b90feed97ee458b7113665300e6bc444798f of master HEAD) and it does
  not work with iOS 10 devices.

  Upstream issue reference:
  https://github.com/libimobiledevice/ifuse/issues/32

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1638177/+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 1638177] [NEW] libimobiledevice: GnuTLS does not work with iOS10

[Sam Gleske]

Public bug reported:

Problem:
The libimobiledevice package for Ubuntu was built with --disable-openssl which 
forces GnuTLS.  GnuTLS does not work with the recent iOS10 update.

Solution: rebuild the package so that it links against OpenSSL again.
This will resolve issues connecting to iOS 10 devices.

I tested the latest development version of GnuTLS (@ commit
1e84b90feed97ee458b7113665300e6bc444798f of master HEAD) and it does not
work with iOS 10 devices.

Upstream issue reference:
https://github.com/libimobiledevice/ifuse/issues/32

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

** Summary changed:

- libimobiledevice: iOS10 does not work with GnuTLS
+ libimobiledevice: GnuTLS does not work with iOS10

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

Title:
  libimobiledevice: GnuTLS does not work with iOS10

Status in libimobiledevice package in Ubuntu:
  New

Bug description:
  Problem:
  The libimobiledevice package for Ubuntu was built with --disable-openssl 
which forces GnuTLS.  GnuTLS does not work with the recent iOS10 update.

  Solution: rebuild the package so that it links against OpenSSL again.
  This will resolve issues connecting to iOS 10 devices.

  I tested the latest development version of GnuTLS (@ commit
  1e84b90feed97ee458b7113665300e6bc444798f of master HEAD) and it does
  not work with iOS 10 devices.

  Upstream issue reference:
  https://github.com/libimobiledevice/ifuse/issues/32

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1638177/+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 1637862] JournalErrors.txt

[Sam Brightman]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1637862/+attachment/4769867/+files/JournalErrors.txt

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

Title:
  Disabling module-suspend-on-idle results in no sound

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Prior to 16.10, I always disabled module-suspend-on-idle in
  /etc/pulse/default.pa. With it enabled (the default), I often lose the
  beginning of audio being played because of the time it or my receiver
  takes to start up. I also sometimes gets cracks/pops.

  Commenting out the line (to disable it) in 16.10 results in no audio at all. 
I tried restarting pulseaudio (killall pulseaudio) and restarting the system. 
Re-enabling the module and restarting pulseaudio immediately fixes it.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  sam   13057 F pulseaudio
   /dev/snd/controlC0:  sam   13057 F pulseaudio
   /dev/snd/controlC1:  sam   13057 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-2ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-100027.29+disablepmp-generic 4.8.1
  Tags:  yakkety
  Uname: Linux 4.8.0-100027-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-22 (8 days ago)
  UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev 
sambashare saned scanner tape video
  _MarkForUpload: True
  dmi.bios.date: 08/17/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9b
  dmi.board.name: GA-MA790XT-UD4P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9b:bd08/17/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790XT-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790XT-UD4P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA790XT-UD4P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.system.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-10-30T17:16:29.535056
  mtime.conffile..etc.pulse.system.pa: 2015-05-18T19:33:30.464175

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1637862/+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 1637862] Dependencies.txt

[Sam Brightman]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1637862/+attachment/4769866/+files/Dependencies.txt

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

Title:
  Disabling module-suspend-on-idle results in no sound

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Prior to 16.10, I always disabled module-suspend-on-idle in
  /etc/pulse/default.pa. With it enabled (the default), I often lose the
  beginning of audio being played because of the time it or my receiver
  takes to start up. I also sometimes gets cracks/pops.

  Commenting out the line (to disable it) in 16.10 results in no audio at all. 
I tried restarting pulseaudio (killall pulseaudio) and restarting the system. 
Re-enabling the module and restarting pulseaudio immediately fixes it.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  sam   13057 F pulseaudio
   /dev/snd/controlC0:  sam   13057 F pulseaudio
   /dev/snd/controlC1:  sam   13057 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-2ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-100027.29+disablepmp-generic 4.8.1
  Tags:  yakkety
  Uname: Linux 4.8.0-100027-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-22 (8 days ago)
  UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev 
sambashare saned scanner tape video
  _MarkForUpload: True
  dmi.bios.date: 08/17/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9b
  dmi.board.name: GA-MA790XT-UD4P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9b:bd08/17/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790XT-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790XT-UD4P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA790XT-UD4P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.system.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-10-30T17:16:29.535056
  mtime.conffile..etc.pulse.system.pa: 2015-05-18T19:33:30.464175

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1637862/+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 1637862] PulseList.txt

[Sam Brightman]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1637862/+attachment/4769869/+files/PulseList.txt

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

Title:
  Disabling module-suspend-on-idle results in no sound

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Prior to 16.10, I always disabled module-suspend-on-idle in
  /etc/pulse/default.pa. With it enabled (the default), I often lose the
  beginning of audio being played because of the time it or my receiver
  takes to start up. I also sometimes gets cracks/pops.

  Commenting out the line (to disable it) in 16.10 results in no audio at all. 
I tried restarting pulseaudio (killall pulseaudio) and restarting the system. 
Re-enabling the module and restarting pulseaudio immediately fixes it.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  sam   13057 F pulseaudio
   /dev/snd/controlC0:  sam   13057 F pulseaudio
   /dev/snd/controlC1:  sam   13057 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-2ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-100027.29+disablepmp-generic 4.8.1
  Tags:  yakkety
  Uname: Linux 4.8.0-100027-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-22 (8 days ago)
  UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev 
sambashare saned scanner tape video
  _MarkForUpload: True
  dmi.bios.date: 08/17/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9b
  dmi.board.name: GA-MA790XT-UD4P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9b:bd08/17/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790XT-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790XT-UD4P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA790XT-UD4P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.system.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-10-30T17:16:29.535056
  mtime.conffile..etc.pulse.system.pa: 2015-05-18T19:33:30.464175

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1637862/+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 1637862] ProcEnviron.txt

[Sam Brightman]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1637862/+attachment/4769868/+files/ProcEnviron.txt

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

Title:
  Disabling module-suspend-on-idle results in no sound

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Prior to 16.10, I always disabled module-suspend-on-idle in
  /etc/pulse/default.pa. With it enabled (the default), I often lose the
  beginning of audio being played because of the time it or my receiver
  takes to start up. I also sometimes gets cracks/pops.

  Commenting out the line (to disable it) in 16.10 results in no audio at all. 
I tried restarting pulseaudio (killall pulseaudio) and restarting the system. 
Re-enabling the module and restarting pulseaudio immediately fixes it.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  sam   13057 F pulseaudio
   /dev/snd/controlC0:  sam   13057 F pulseaudio
   /dev/snd/controlC1:  sam   13057 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-2ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-100027.29+disablepmp-generic 4.8.1
  Tags:  yakkety
  Uname: Linux 4.8.0-100027-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-22 (8 days ago)
  UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev 
sambashare saned scanner tape video
  _MarkForUpload: True
  dmi.bios.date: 08/17/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9b
  dmi.board.name: GA-MA790XT-UD4P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9b:bd08/17/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790XT-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790XT-UD4P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA790XT-UD4P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.system.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-10-30T17:16:29.535056
  mtime.conffile..etc.pulse.system.pa: 2015-05-18T19:33:30.464175

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1637862/+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 1637862] CurrentDmesg.txt

[Sam Brightman]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1637862/+attachment/4769865/+files/CurrentDmesg.txt

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

Title:
  Disabling module-suspend-on-idle results in no sound

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Prior to 16.10, I always disabled module-suspend-on-idle in
  /etc/pulse/default.pa. With it enabled (the default), I often lose the
  beginning of audio being played because of the time it or my receiver
  takes to start up. I also sometimes gets cracks/pops.

  Commenting out the line (to disable it) in 16.10 results in no audio at all. 
I tried restarting pulseaudio (killall pulseaudio) and restarting the system. 
Re-enabling the module and restarting pulseaudio immediately fixes it.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  sam   13057 F pulseaudio
   /dev/snd/controlC0:  sam   13057 F pulseaudio
   /dev/snd/controlC1:  sam   13057 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-2ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-100027.29+disablepmp-generic 4.8.1
  Tags:  yakkety
  Uname: Linux 4.8.0-100027-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-22 (8 days ago)
  UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev 
sambashare saned scanner tape video
  _MarkForUpload: True
  dmi.bios.date: 08/17/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9b
  dmi.board.name: GA-MA790XT-UD4P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9b:bd08/17/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790XT-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790XT-UD4P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA790XT-UD4P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.system.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-10-30T17:16:29.535056
  mtime.conffile..etc.pulse.system.pa: 2015-05-18T19:33:30.464175

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1637862/+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 1637862] Re: Disabling module-suspend-on-idle results in no sound

[Sam Brightman]

apport information

** Tags added: apport-collected yakkety

** Description changed:

  Prior to 16.10, I always disabled module-suspend-on-idle in
  /etc/pulse/default.pa. With it enabled (the default), I often lose the
  beginning of audio being played because of the time it or my receiver
  takes to start up. I also sometimes gets cracks/pops.
  
- Commenting out the line (to disable it) in 16.10 results in no audio at
- all. I tried restarting pulseaudio (killall pulseaudio) and restarting
- the system. Re-enabling the module and restarting pulseaudio immediately
- fixes it.
+ Commenting out the line (to disable it) in 16.10 results in no audio at all. 
I tried restarting pulseaudio (killall pulseaudio) and restarting the system. 
Re-enabling the module and restarting pulseaudio immediately fixes it.
+ --- 
+ ApportVersion: 2.20.3-0ubuntu8
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  sam   13057 F pulseaudio
+  /dev/snd/controlC0:  sam   13057 F pulseaudio
+  /dev/snd/controlC1:  sam   13057 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.10
+ Package: pulseaudio 1:9.0-2ubuntu2
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.8.0-100027.29+disablepmp-generic 4.8.1
+ Tags:  yakkety
+ Uname: Linux 4.8.0-100027-generic x86_64
+ UpgradeStatus: Upgraded to yakkety on 2016-10-22 (8 days ago)
+ UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev 
sambashare saned scanner tape video
+ _MarkForUpload: True
+ dmi.bios.date: 08/17/2012
+ dmi.bios.vendor: Award Software International, Inc.
+ dmi.bios.version: F9b
+ dmi.board.name: GA-MA790XT-UD4P
+ dmi.board.vendor: Gigabyte Technology Co., Ltd.
+ dmi.board.version: x.x
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
+ dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9b:bd08/17/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790XT-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790XT-UD4P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
+ dmi.product.name: GA-MA790XT-UD4P
+ dmi.sys.vendor: Gigabyte Technology Co., Ltd.
+ modified.conffile..etc.pulse.daemon.conf: [modified]
+ modified.conffile..etc.pulse.system.pa: [modified]
+ mtime.conffile..etc.pulse.daemon.conf: 2016-10-30T17:16:29.535056
+ mtime.conffile..etc.pulse.system.pa: 2015-05-18T19:33:30.464175

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1637862/+attachment/4769864/+files/AlsaInfo.txt

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

Title:
  Disabling module-suspend-on-idle results in no sound

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Prior to 16.10, I always disabled module-suspend-on-idle in
  /etc/pulse/default.pa. With it enabled (the default), I often lose the
  beginning of audio being played because of the time it or my receiver
  takes to start up. I also sometimes gets cracks/pops.

  Commenting out the line (to disable it) in 16.10 results in no audio at all. 
I tried restarting pulseaudio (killall pulseaudio) and restarting the system. 
Re-enabling the module and restarting pulseaudio immediately fixes it.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  sam   13057 F pulseaudio
   /dev/snd/controlC0:  sam   13057 F pulseaudio
   /dev/snd/controlC1:  sam   13057 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-2ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-100027.29+disablepmp-generic 4.8.1
  Tags:  yakkety
  Uname: Linux 4.8.0-100027-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-22 (8 days ago)
  UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev 
sambashare saned scanner tape video
  _MarkForUpload: True
  dmi.bios.date: 08/17/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9b
  dmi.board.name: GA-MA790XT-UD4P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9b:bd08/17/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790XT-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790XT-UD4P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA790XT-UD4P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.system.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-10-30T17:16:29.535056
  mtime.conffile..etc.pulse.system.pa: 2015-05-18T19:33:30.464175

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

[Touch-packages] [Bug 1637862] [NEW] Disabling module-suspend-on-idle results in no sound

[Sam Brightman]

Public bug reported:

Prior to 16.10, I always disabled module-suspend-on-idle in
/etc/pulse/default.pa. With it enabled (the default), I often lose the
beginning of audio being played because of the time it or my receiver
takes to start up. I also sometimes gets cracks/pops.

Commenting out the line (to disable it) in 16.10 results in no audio at
all. I tried restarting pulseaudio (killall pulseaudio) and restarting
the system. Re-enabling the module and restarting pulseaudio immediately
fixes it.

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

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

Title:
  Disabling module-suspend-on-idle results in no sound

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Prior to 16.10, I always disabled module-suspend-on-idle in
  /etc/pulse/default.pa. With it enabled (the default), I often lose the
  beginning of audio being played because of the time it or my receiver
  takes to start up. I also sometimes gets cracks/pops.

  Commenting out the line (to disable it) in 16.10 results in no audio
  at all. I tried restarting pulseaudio (killall pulseaudio) and
  restarting the system. Re-enabling the module and restarting
  pulseaudio immediately fixes it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1637862/+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 1610534] Re: Open tabs keep getting forgotten

[Sam Bull]

Back to the original bug. It's been 2-3 weeks, and now it has forgotten
my tabs yet again. Friday night, I closed the browser with 7 tabs,
afterwards I shutdown the phone. Saturday morning, I turned my phone on,
opened a twitter link, the browser app opened with only this tab, having
forgotten my other 7 tabs.

** Summary changed:

- Restore previous session doesn't work
+ Open tabs keep getting forgotten

** Changed in: webbrowser-app (Ubuntu)
   Status: Invalid => New

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

Title:
  Open tabs keep getting forgotten

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  The browser app keeps forgetting my open tabs on a semi-regular basis.
  It seems to happen to me every couple of weeks or so, I will open the
  app and all my tabs are gone. This is very frustrating, as there is no
  easy way to recover them.

  I think it may actually happen more frequently when there are around
  7/8 tabs or more open.

  OTA-12 (and previous versions), mako.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1610534/+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 1629370] Re: PKINIT fails with PKCS#11 middlware that implements PKCS#1 V2.1

[Sam Hartman]

I've forwarded this to upstream krbdev.mit.edu #8506
I don't know if this is pkcs 11 2.10 specific or specific to the backend in 
question, but it's worth having upstream take a look.

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

Title:
  PKINIT fails with PKCS#11 middlware that implements PKCS#1 V2.1

Status in krb5 package in Ubuntu:
  New

Bug description:
  Problem: can't do PK-INIT with a smartcard PKCS#11 middleware that
  implements PKCS#1 v2.10

  $ kinit -E name.surname@something@REALM

  -> fails

  Diagnostic using PKCS11-SPY from OpenSC:

  16: C_Sign
  2016-09-16 14:31:53.265
  [in] hSession = 0x6bc3a70e
  [in] pData[ulDataLen] 0931e898 / 33
    30 1F 30 07 06 05 2B 0E 03 02 1A 04 14 17 07 D3  
0.0...+.
  0010  5A 2B F8 78 C0 FD CD 87 EE 25 08 C2 DD AA 50 3D  
Z+.x.%P=
  0020  DC   .  
 
  Returned:  32 CKR_DATA_INVALID

  The signing algorithm is SHA1. However the Data Formatting is
  incorrect:

  30 1F 30 07 06 05 2B 0E 03 02 1A 04 14 17 07 D3 5A 2B F8 78 C0 FD CD
  87 EE 25 08 C2 DD AA 50 3D DC

  instead it should be:

  30 21 30 09 06 05 2B 0E 03 02 1A 05 00 04 14 17 07 D3 5A 2B F8 78 C0 FD CD 87 
EE 25 08 C2 DD AA 50 3D DC  

  See the PKCS#1 paper (page 43) https://tools.ietf.org/html/rfc3447

  Extract:
  " 
  1. For the six hash functions mentioned in Appendix B.1, the DER
encoding T of the DigestInfo value is equal to the following:

MD2: (0x)30 20 30 0c 06 08 2a 86 48 86 f7 0d 02 02 05 00 04
 10 || H.
MD5: (0x)30 20 30 0c 06 08 2a 86 48 86 f7 0d 02 05 05 00 04
 10 || H.
SHA-1:   (0x)30 21 30 09 06 05 2b 0e 03 02 1a 05 00 04 14 || H.
  "

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: krb5-pkinit 1.12+dfsg-2ubuntu5.2
  Uname: Linux 3.13.0-68-generic x86_64
  Architecture: amd64
  Date: Fri Sep 30 12:49:09 CEST 2016
  ProcEnviron:
   PATH=(custom, user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: krb5-pkinit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1629370/+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 1554504] Re: Calendar reminder does not wake phone when airplane mode is enabled

[Sam Bull]

And, that's also on a Nexus 4, using the stable releases. Failed again
this morning on OTA-13.

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

Title:
  Calendar reminder does not wake phone when airplane mode is enabled

Status in Canonical System Image:
  Incomplete
Status in indicator-datetime package in Ubuntu:
  Incomplete

Bug description:
  If airplane mode is enabled, the phone seems to go into a deep sleep
  where it doesn't wake up for a calendar reminder. The reminder does
  not sound until the power button is pressed to wake the phone, in some
  cases this has been more than an hour after the reminder was scheduled
  for.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554504/+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 1610534] Re: Restore previous session doesn't work

[Sam Bull]

Seems to be working better, having deleted that file. So, maybe some
better logic for detecting/handling corrupted session files is needed.

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

Title:
  Restore previous session doesn't work

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  The browser app keeps forgetting my open tabs on a semi-regular basis.
  It seems to happen to me every couple of weeks or so, I will open the
  app and all my tabs are gone. This is very frustrating, as there is no
  easy way to recover them.

  I think it may actually happen more frequently when there are around
  7/8 tabs or more open.

  OTA-12 (and previous versions), mako.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1610534/+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 1554504] Re: Calendar reminder does not wake phone when airplane mode is enabled

[Sam Bull]

Since filing this bug, the issue has only got worse. It has been 100%
reproducible for me for the past couple of months. I have a calendar
reminder to go off at 8am. Every morning, it only goes off when I
actually wake up the phone myself, in some cases this has been over an
hour past the time it was supposed to remind me. The only time it
successfully works, is if I have woken the phone a few minutes early
(presumably the phone doesn't go back to a deep sleep for a few minutes
or something).

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

Title:
  Calendar reminder does not wake phone when airplane mode is enabled

Status in Canonical System Image:
  Incomplete
Status in indicator-datetime package in Ubuntu:
  Incomplete

Bug description:
  If airplane mode is enabled, the phone seems to go into a deep sleep
  where it doesn't wake up for a calendar reminder. The reminder does
  not sound until the power button is pressed to wake the phone, in some
  cases this has been more than an hour after the reminder was scheduled
  for.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554504/+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 1610534] Re: Open tabs keep getting forgotten

[Sam Bull]

This feature simply doesn't seem to work anymore. I don't remember it
correctly restoring tabs in the past couple of months.

** Summary changed:

- Open tabs keep getting forgotten
+ Restore previous session doesn't work

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

Title:
  Restore previous session doesn't work

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  The browser app keeps forgetting my open tabs on a semi-regular basis.
  It seems to happen to me every couple of weeks or so, I will open the
  app and all my tabs are gone. This is very frustrating, as there is no
  easy way to recover them.

  I think it may actually happen more frequently when there are around
  7/8 tabs or more open.

  OTA-12 (and previous versions), mako.

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