[Bug 2063005] Re: Some shell elements don't respond to touchscreen in Xorg sessions

[Austin Thomas]

Is there a known workaround for this bug? I've found that holding an
additional finger on the screen before pressing an element will
sometimes work.

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

Title:
  Some shell elements don't respond to touchscreen in Xorg sessions

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


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

[Bug 2069357] Re: Multimonitor support broken on kernel 6.5.0-1024.25_oem on Lenovo Thunderbolt 3 Gen 2 USB-C dock

[Austin Esquirell]

6.8.0-40-generic appears to be working just fine now. My team has no
major issues anymore.

If upgrading to 6.8 is the official solution, this ticket can be marked
as "Won't Fix".

Thank you for all the work on the 6.8 kernel!

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

Title:
  Multimonitor support broken on kernel 6.5.0-1024.25_oem on Lenovo
  Thunderbolt 3 Gen 2 USB-C dock

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


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

[Bug 2070096] Re: [amdgpu] Graphics driver issue: Display goes black for a second at random: [drm:link_enc_cfg_validate [amdgpu]] *ERROR* link_enc_cfg_validate: Invalid link encoder assignments - 0x1c

[Austin Esquirell]

I am seeing the same thing - also thought it was something I must have
done to stay on 1023, but maybe it is a different issue.

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

Title:
  [amdgpu] Graphics driver issue: Display goes black for a second at
  random: [drm:link_enc_cfg_validate [amdgpu]] *ERROR*
  link_enc_cfg_validate: Invalid link encoder assignments - 0x1c

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


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

[Bug 2069357] Re: Multimonitor support broken on kernel 6.5.0-1024.25_oem on Lenovo Thunderbolt 3 Gen 2 USB-C dock

[Austin Esquirell]

Just tried the 6.8.0-40-generic kernel and it seems to be fixed
(installed automatically via sudo apt upgrade).

Not sure if the other display-related issues are fixed though, such as
the one mentioned here: https://bugs.launchpad.net/ubuntu/+source/linux-
oem-6.5/+bug/2070096

We saw the above issue on 6.8.0-38-generic. I'll use 6.8.0-40-generic
for a bit and see if anything else is broken.

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

Title:
  Multimonitor support broken on kernel 6.5.0-1024.25_oem on Lenovo
  Thunderbolt 3 Gen 2 USB-C dock

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


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

[Bug 2069357] Re: Multimonitor support broken on kernel 6.5.0-1024.25_oem on Lenovo Thunderbolt 3 Gen 2 USB-C dock

[Austin Esquirell]

I think you mean 1025.26, and yes, it is still broken in that release.

My team has also experienced other monitor related issues on the
6.8.0-38-generic kernel, so we are still hoping for a fix on 6.5 oem. We
are using 6.5.0-1023 for the time being.

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

Title:
  Multimonitor support broken on kernel 6.5.0-1024.25_oem on Lenovo
  Thunderbolt 3 Gen 2 USB-C dock

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


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

[Bug 2069357] Re: Multimonitor support broken on kernel 6.5.0-1024.25_oem on Lenovo Thunderbolt 3 Gen 2 USB-C dock

[Austin Esquirell]

The 6.8.0-38-generic kernel seems to work correctly with my Lenovo
Thunderbolt 3 Gen 2 USB-C dock (but I have not tested other features or
stability).

Will a 6.8 oem kernel will be released that users can automatically
update to? If so, perhaps the solution could be to just upgrade to 6.8.
But for the time being the broken 6.5 kernel is confusing for people who
have Ubuntu preinstalled from the factory with the oem kernel as it will
appear to be broken out of the box. But maybe there is something else I
am not understanding about the kernel workflow. Could you shed some
light on this?

Thanks!

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

Title:
  Multimonitor support broken on kernel 6.5.0-1024.25_oem on Lenovo
  Thunderbolt 3 Gen 2 USB-C dock

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


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

[Bug 2069357] [NEW] Multimonitor support broken on kernel 6.5.0-1024.25_oem on Lenovo Thunderbolt 3 Gen 2 USB-C dock

[Austin Esquirell]

Public bug reported:

Updating to 6.5.0-1024.25_oem from 6.5.0-1023.24_oem breaks HDMI video
on the Lenovo Thunderbolt 3 Gen 2 USB-C dock. I am using a Thinkpad P16s
with a Ryzen 7 PRO 7840U CPU and Ubuntu 22.04.4 LTS.

When using this new kernel version, all monitors plugged in via the dock
display nothing during boot and after logging in to Ubutnu. The monitors
are also not detected in the Settings->Displays section. I am using 2
HDMI Dell monitors in addition to the built-in display on the Laptop.
The monitors show that they do not detect any input (as opposed to
receiving a blank/black input).

Manually booting to the old 6.5.0-1023.24_oem kernel in GRUB fixes the
issue.

It looks like there was a fix for HDMI/DP audio using USB-C docks in the
new 6.5.0-1024.25_oem kernel; Maybe the issue is there.

This was the changelog entry:

* Fix inaudible HDMI/DP audio on USB-C MST dock (LP: #2064689)
- SAUCE: drm/i915/audio: Fix audio time stamp programming for DP

And here is a link to that issue: https://launchpad.net/bugs/2064689

If there are any logs or additional details I can provide, I am happy to
help.

** Affects: linux-oem-6.5 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Multimonitor support broken on kernel 6.5.0-1024.25_oem on Lenovo
  Thunderbolt 3 Gen 2 USB-C dock

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


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

[Bug 2064689] Re: Fix inaudible HDMI/DP audio on USB-C MST dock

[Austin Esquirell]

Updating to 6.5.0-1024.25_oem from 6.5.0-1023.24_oem breaks HDMI video
on the Lenovo Thunderbolt 3 Gen 2 USB-C dock. Since this is the only
bugfix relating to HDMI/USB-C docks it would seem that this is the
change that causes the issue.

If there are any logs or additional details I can provide, I am happy to
help.

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

Title:
  Fix inaudible HDMI/DP audio on USB-C MST dock

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2064689/+subscriptions


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

[Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall

[Austin Dunham]

I was able to reproduce this on our test system with comment 13.

This effects our LDAP system too.

We use LDAP for single sign on and with Radius for WiFi, so when it
locks up people can't login to a lot of our systems and WiFi
authentication stops.

This happens anywhere from once a week to once a month.

We have some work to do on our virtualization platform before we can
update to something other than Ubuntu 18.04 LTS.

I don't see lincvz's PPA anymore. . . and if my understanding is correct
that would basically make LDAP static until we did upgrade.

Is there a recommended way forward at this point if one stays on 18.04?

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

Title:
  slapd enter in infinite loop on sched_yield syscall

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


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

[Bug 1966921] Re: Display freezes after entering password from login screen

[Matt Austin]

Thanks Daniel.

You were right about the extensions, thank you for the suggestion.

It appears to be caused by the "Nothing to Say" gnome extension. I
uninstalled this, and can now use the wayland session again.

It looks like it's probably the same issue as reported here (by a user running 
20.04):
https://github.com/wbolster/nothing-to-say/issues/49

Thanks for your time, sorry if I wasted it by suggesting the bug was was
mutter-related.

** Bug watch added: github.com/wbolster/nothing-to-say/issues #49
   https://github.com/wbolster/nothing-to-say/issues/49

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

Title:
  Display freezes after entering password from login screen

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


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

[Bug 1966921] Re: Display freezes after entering password from login screen

[Matt Austin]

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1966921/+attachment/5574561/+files/prevboot.txt

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

Title:
  Display freezes after entering password from login screen

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


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

[Bug 1966921] Re: Display freezes after entering password from login screen

[Matt Austin]

Thanks Daniel,

I have attached the requested output.

** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1966921/+attachment/5574560/+files/lspci.txt

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

Title:
  Display freezes after entering password from login screen

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


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

[Bug 1966921] [NEW] Display freezes after entering password from login screen

[Matt Austin]

Public bug reported:

The display freezes with the same background colour as the login screen.
The mouse pointer no longer moves. I was unable to change to another VT
when the display freezes. Only a press of the power button seemed to
make the laptop respond by triggering a shutdown.

I've had to switch to "GNOME on Xorg" to be able to login/see the
desktop. Wayland was working fine until some time around the last week.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter 42~beta-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Tue Mar 29 18:34:41 2022
InstallationDate: Installed on 2021-09-13 (196 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: mutter
UpgradeStatus: Upgraded to jammy on 2022-02-19 (38 days ago)

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


** Tags: amd64 apport-bug jammy

** Description changed:

- I was unable to change to another VT when the display freezes. Only a
- press of the power button seemed to make the laptop respond by
- triggering a shutdown.
+ The display freezes with the same background colour as the login screen.
+ The mouse pointer no longer moves. I was unable to change to another VT
+ when the display freezes. Only a press of the power button seemed to
+ make the laptop respond by triggering a shutdown.
  
  I've had to switch to "GNOME on Xorg" to be able to login/see the
  desktop. Wayland was working fine until some time around the last week.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter 42~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Mar 29 18:34:41 2022
  InstallationDate: Installed on 2021-09-13 (196 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to jammy on 2022-02-19 (38 days ago)

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

Title:
  Display freezes after entering password from login screen

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


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

[Bug 1944018] Re: ath11k_pci sometimes crashes on suspend/resume on Dell XPS 13 9310

[Matt Austin]

It appears installing linux-oem-20.04c resolves this issue for me (it
installs kernel 5.13).

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

Title:
  ath11k_pci sometimes crashes on suspend/resume on Dell XPS 13 9310

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


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

[Bug 1951034] [NEW] XPS 9310: wifi adapter not working when using linux-image-5.13.0-1019-oem (was working in linux-image-5.13.0-1017-oem)

[Matt Austin]

Public bug reported:

I have been using linux-oem-20.04c with my XPS 9310 with no problems,
but the recent update to 5.13.0-1019-oem caused my wifi to become
inoperative (ath11k_pci, 72:00.0 Network controller: Qualcomm Device
1101 (rev 01)). Choosing 5.13.0-1017-oem from the grub menu is my
current work around as the wifi is still working there.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-1019-oem 5.13.0-1019.23
ProcVersionSignature: Ubuntu 5.13.0-1017.21-oem 5.13.14
Uname: Linux 5.13.0-1017-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Tue Nov 16 08:10:20 2021
InstallationDate: Installed on 2021-09-13 (63 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: linux-signed-oem-5.13
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-oem-5.13 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal wayland-session

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

Title:
  XPS 9310: wifi adapter not working when using linux-
  image-5.13.0-1019-oem (was working in linux-image-5.13.0-1017-oem)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.13/+bug/1951034/+subscriptions


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

[Bug 1944018] Re: ath11k_pci sometimes crashes on suspend/resume on Dell XPS 13 9310

[Matt Austin]

I should also note that after this happens, attempting to "rmmod
ath11k_pci" results in a wait of several minutes before then getting a
segmentation fault error.

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

Title:
  ath11k_pci sometimes crashes on suspend/resume on Dell XPS 13 9310

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


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

[Bug 1944018] Re: ath11k_pci sometimes crashes on suspend/resume on Dell XPS 13 9310

[Matt Austin]

Adding log snippet form kernel.log - where the following is repeated:

Sep 18 11:46:57 perseverance kernel: [314619.796128] ath11k_pci :72:00.0: 
wmi command 16387 timeout
Sep 18 11:46:57 perseverance kernel: [314619.796134] ath11k_pci :72:00.0: 
failed to send WMI_PDEV_SET_PARAM cmd
Sep 18 11:46:57 perseverance kernel: [314619.796139] ath11k_pci :72:00.0: 
failed to enable PMF QOS: (-11


** Attachment added: "kernal-snippet.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1944018/+attachment/5526093/+files/kernal-snippet.log

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

Title:
  ath11k_pci sometimes crashes on suspend/resume on Dell XPS 13 9310

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


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

[Bug 1944018] [NEW] ath11k_pci sometimes crashes on suspend/resume on Dell XPS 13 9310

[Matt Austin]

Public bug reported:

Sometimes when my Dell XPS 13 9310 resumes from suspend, the display
fails to show anything for a short while. When the display does show,
the wireless network is no longer working.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-modules-5.10.0-1045-oem 5.10.0-1045.47
ProcVersionSignature: Ubuntu 5.10.0-1045.47-oem 5.10.46
Uname: Linux 5.10.0-1045-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Sat Sep 18 12:04:49 2021
Dependencies:
 
InstallationDate: Installed on 2021-09-13 (4 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: linux-oem-5.10
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-oem-5.10 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal wayland-session

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

Title:
  ath11k_pci sometimes crashes on suspend/resume on Dell XPS 13 9310

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


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

Re: [Bug 1939743] Re: No Touchpad on TravelMate-P2 laptop

[Stephen Austin Hale]

Hello, I think the issue must have been Ubermix-specific it seems. Pop-OS,
which uses the same Ubuntu version, does not have any trackpad related
issues. If you would still like that command result I can get that to you,
I'll just have to re-flash Ubermix. Thank you for your quick replies and
help!

On Wed, Aug 18, 2021 at 10:50 AM Chris Chiu <1939...@bugs.launchpad.net>
wrote:

> It's weird there's a mouse detected but not recognized as an input device.
> Can you show me the result of the command `ls  /sys/bus/acpi/devices/`?
> Since there's a PS2M(ps/2 touchpad) device and a TPD0 (i2c interface)
> device in the ACPI dsdt file which should represent the Touchpad. I need to
> know which one is recognized by ACPI and I can tell the touchpad is from
> Elantech or Synaptic. The we can dig further for what really happened.
> Thanks
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1939743
>
> Title:
>   No Touchpad on TravelMate-P2 laptop
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   On the TravelMate P215-53 V1.10 by Acer when running Ubuntu, the
>   trackpad is entirely non-functional and does not appear in the
>   /proc/bus/input/devices list. A wired usb mouse works perfectly, but
>   there does not seem to be a tweak that enables the trackpad to be seen
>   by the kernel.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: linux-image-5.4.0-54-generic 5.4.0-54.60
>   ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
>   Uname: Linux 5.4.0-54-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.18
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu Aug 12 14:30:39 2021
>   InstallationDate: Installed on 2020-12-09 (245 days ago)
>   InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
> (20200731)
>   MachineType: Acer TravelMate P215-53
>   ProcFB: 0 EFI VGA
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic
> root=/dev/nvme0n1p2 ro quiet splash vt.handoff=1
>   RelatedPackageVersions:
>linux-restricted-modules-5.4.0-54-generic N/A
>linux-backports-modules-5.4.0-54-generic  N/A
>linux-firmware1.187.15
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   WifiSyslog:
>
>   dmi.bios.date: 12/17/2020
>   dmi.bios.vendor: INSYDE Corp.
>   dmi.bios.version: V1.10
>   dmi.board.asset.tag: Type2 - Board Asset Tag
>   dmi.board.name: BassDrum_TL
>   dmi.board.vendor: TGL
>   dmi.board.version: V1.10
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Chassis Manufacturer
>   dmi.chassis.version: Chassis Version
>   dmi.modalias:
> dmi:bvnINSYDECorp.:bvrV1.10:bd12/17/2020:svnAcer:pnTravelMateP215-53:pvrV1.10:rvnTGL:rnBassDrum_TL:rvrV1.10:cvnChassisManufacturer:ct10:cvrChassisVersion:
>   dmi.product.family: TravelMate P2
>   dmi.product.name: TravelMate P215-53
>   dmi.product.sku: 
>   dmi.product.version: V1.10
>   dmi.sys.vendor: Acer
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939743/+subscriptions
>
>

--

Stephen Hale
Systems Administrator, West Fork Schools
(479) 839-2231 Ext: 4050 <+(479)+839-2231+Ext:+4050>
sh...@wftigers.org
359 School Ave. West Fork, AR 72774


Create your own email signature

‌

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

Title:
  No Touchpad on TravelMate-P2 laptop

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


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

Re: [Bug 1939743] Re: No Touchpad on TravelMate-P2 laptop

[Stephen Austin Hale]

The suspend/resume does not seem to make any difference, and I cannot see
the device listed in dmesg. The BIOS for this device doesn't appear to have
an advanced mode, but if it helps the device is only capable of UEFI
booting, so ubermix has been installed as UEFI.
Attached is the output of the dmesg command.

On Mon, Aug 16, 2021 at 11:10 PM Chris Chiu <1939...@bugs.launchpad.net>
wrote:

> Per the dmesg output, your touchpad should connect via i8042 interface and
> seems detected.
> [0.549357] serio: i8042 KBD port at 0x60,0x64 irq 1
> [0.549493] mousedev: PS/2 mouse device common for all mice
>
> Does the suspend/resume makes any difference?
>
> If not, you can go back to BIOS menu and change the BIOS setting from
> "Basic mode" to "Advanced mode", then boot into Ubuntu to see if it's
> detected or not. Please also paste the dmesg output here for the Advance
> mode. Thanks.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1939743
>
> Title:
>   No Touchpad on TravelMate-P2 laptop
>
> Status in linux package in Ubuntu:
>   New
>
> Bug description:
>   On the TravelMate P215-53 V1.10 by Acer when running Ubuntu, the
>   trackpad is entirely non-functional and does not appear in the
>   /proc/bus/input/devices list. A wired usb mouse works perfectly, but
>   there does not seem to be a tweak that enables the trackpad to be seen
>   by the kernel.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: linux-image-5.4.0-54-generic 5.4.0-54.60
>   ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
>   Uname: Linux 5.4.0-54-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.18
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu Aug 12 14:30:39 2021
>   InstallationDate: Installed on 2020-12-09 (245 days ago)
>   InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
> (20200731)
>   MachineType: Acer TravelMate P215-53
>   ProcFB: 0 EFI VGA
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic
> root=/dev/nvme0n1p2 ro quiet splash vt.handoff=1
>   RelatedPackageVersions:
>linux-restricted-modules-5.4.0-54-generic N/A
>linux-backports-modules-5.4.0-54-generic  N/A
>linux-firmware1.187.15
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   WifiSyslog:
>
>   dmi.bios.date: 12/17/2020
>   dmi.bios.vendor: INSYDE Corp.
>   dmi.bios.version: V1.10
>   dmi.board.asset.tag: Type2 - Board Asset Tag
>   dmi.board.name: BassDrum_TL
>   dmi.board.vendor: TGL
>   dmi.board.version: V1.10
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Chassis Manufacturer
>   dmi.chassis.version: Chassis Version
>   dmi.modalias:
> dmi:bvnINSYDECorp.:bvrV1.10:bd12/17/2020:svnAcer:pnTravelMateP215-53:pvrV1.10:rvnTGL:rnBassDrum_TL:rvrV1.10:cvnChassisManufacturer:ct10:cvrChassisVersion:
>   dmi.product.family: TravelMate P2
>   dmi.product.name: TravelMate P215-53
>   dmi.product.sku: 
>   dmi.product.version: V1.10
>   dmi.sys.vendor: Acer
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939743/+subscriptions
>
>


** Attachment added: "dmesg"
   https://bugs.launchpad.net/bugs/1939743/+attachment/5518518/+files/dmesg

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

Title:
  No Touchpad on TravelMate-P2 laptop

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


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

Re: [Bug 1939743] Re: No Touchpad on TravelMate-P2 laptop

[Stephen Austin Hale]

Hello, I added those options to the boot menu (via esc -> e -> adding it to
the end of the linux line in the boot config -> f10) and the trackpad is
still entirely unresponsive. The function key for enable/disable trackpad
did not make a difference. The device also doesn't appear in the xinput
devices list. Thank you for reaching out!

On Mon, Aug 16, 2021 at 10:10 AM Chris Chiu <1939...@bugs.launchpad.net>
wrote:

> Could you try to add "i8042.reset i8042.nomux i8042.nopnp i8042.noloop"
> to the kernel boot options to check whether it makes any difference?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1939743
>
> Title:
>   No Touchpad on TravelMate-P2 laptop
>
> Status in linux package in Ubuntu:
>   New
>
> Bug description:
>   On the TravelMate P215-53 V1.10 by Acer when running Ubuntu, the
>   trackpad is entirely non-functional and does not appear in the
>   /proc/bus/input/devices list. A wired usb mouse works perfectly, but
>   there does not seem to be a tweak that enables the trackpad to be seen
>   by the kernel.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: linux-image-5.4.0-54-generic 5.4.0-54.60
>   ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
>   Uname: Linux 5.4.0-54-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.18
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu Aug 12 14:30:39 2021
>   InstallationDate: Installed on 2020-12-09 (245 days ago)
>   InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
> (20200731)
>   MachineType: Acer TravelMate P215-53
>   ProcFB: 0 EFI VGA
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic
> root=/dev/nvme0n1p2 ro quiet splash vt.handoff=1
>   RelatedPackageVersions:
>linux-restricted-modules-5.4.0-54-generic N/A
>linux-backports-modules-5.4.0-54-generic  N/A
>linux-firmware1.187.15
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   WifiSyslog:
>
>   dmi.bios.date: 12/17/2020
>   dmi.bios.vendor: INSYDE Corp.
>   dmi.bios.version: V1.10
>   dmi.board.asset.tag: Type2 - Board Asset Tag
>   dmi.board.name: BassDrum_TL
>   dmi.board.vendor: TGL
>   dmi.board.version: V1.10
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Chassis Manufacturer
>   dmi.chassis.version: Chassis Version
>   dmi.modalias:
> dmi:bvnINSYDECorp.:bvrV1.10:bd12/17/2020:svnAcer:pnTravelMateP215-53:pvrV1.10:rvnTGL:rnBassDrum_TL:rvrV1.10:cvnChassisManufacturer:ct10:cvrChassisVersion:
>   dmi.product.family: TravelMate P2
>   dmi.product.name: TravelMate P215-53
>   dmi.product.sku: 
>   dmi.product.version: V1.10
>   dmi.sys.vendor: Acer
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939743/+subscriptions
>
>

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

Title:
  No Touchpad on TravelMate-P2 laptop

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


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

[Bug 1939743] [NEW] No Touchpad on TravelMate-P2 laptop

[Stephen Austin Hale]

Public bug reported:

On the TravelMate P215-53 V1.10 by Acer when running Ubuntu, the
trackpad is entirely non-functional and does not appear in the
/proc/bus/input/devices list. A wired usb mouse works perfectly, but
there does not seem to be a tweak that enables the trackpad to be seen
by the kernel.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-54-generic 5.4.0-54.60
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 12 14:30:39 2021
InstallationDate: Installed on 2020-12-09 (245 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Acer TravelMate P215-53
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=/dev/nvme0n1p2 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-54-generic N/A
 linux-backports-modules-5.4.0-54-generic  N/A
 linux-firmware1.187.15
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
 
dmi.bios.date: 12/17/2020
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: V1.10
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: BassDrum_TL
dmi.board.vendor: TGL
dmi.board.version: V1.10
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnINSYDECorp.:bvrV1.10:bd12/17/2020:svnAcer:pnTravelMateP215-53:pvrV1.10:rvnTGL:rnBassDrum_TL:rvrV1.10:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: TravelMate P2
dmi.product.name: TravelMate P215-53
dmi.product.sku: 
dmi.product.version: V1.10
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug focal

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

Title:
  No Touchpad on TravelMate-P2 laptop

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


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

[Bug 306003] Re: smartctl short test hangs at 90%

[Austin]

I can confirm this bug as well.

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename:   focal

Self-test execution status:  ( 249) Self-test routine in progress...
90% of test remaining.

Appears to be common for WD shucked drives. 
Ran across it on my wd 8 TB HDD WD80EMAZ-00WJTA0 (FW ver. 83.H0A83)
Some via CLI finished the smart test, some are hung, the ubuntu disk manager 
did not complete its scans either.

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

Title:
  smartctl short test hangs at 90%

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


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

[Bug 1934603] [NEW] doc-base/intel-mkl-documentation references non-existent file

[Randy Austin]

Public bug reported:

The documentation file for intel-mkl in doc-base references a 2019 file
that is now 2020.

 lengthy normal apt install output 

Processing 8 added doc-base files...
Error in `/usr/share/doc-base/intel-mkl-documentation', line 9: all `Format' 
sections are invalid.
Note: `install-docs --verbose --check file_name' may give more details about 
the above error.
root@vb-math:/home/randy# install-docs --verbose --check file_name
Doc-base file `file_name' does not exist.
root@vb-math:/home/randy# install-docs --verbose --check 
/usr/share/doc-base/intel-mkl-documentation
Warning in `/usr/share/doc-base/intel-mkl-documentation', line 9: file 
`/usr/share/doc/intel-mkl/documentation_2019/en/mkl/ps2019/get_started.htm' 
does not exist.
Error in `/usr/share/doc-base/intel-mkl-documentation', line 9: all `Format' 
sections are invalid.
/usr/share/doc-base/intel-mkl-documentation: Fatal error found, the file won't 
be registered.
root@vb-math:/home/randy# l /usr/share/doc/intel-mkl/documentation_2019/en/mkl/
ls: cannot access '/usr/share/doc/intel-mkl/documentation_2019/en/mkl/': No 
such file or directory
root@vb-math:/home/randy# install-docs --verbose --check 
/usr/share/doc-base/intel-mkl-documentation
Warning in `/usr/share/doc-base/intel-mkl-documentation', line 9: file 
`/usr/share/doc/intel-mkl/documentation_2019/en/mkl/ps2019/get_started.htm' 
does not exist.
Error in `/usr/share/doc-base/intel-mkl-documentation', line 9: all `Format' 
sections are invalid.
/usr/share/doc-base/intel-mkl-documentation: Fatal error found, the file won't 
be registered.
root@vb-math:/home/randy# l /usr/share/doc/intel-mkl/documentation_2019/en/mkl/
ls: cannot access '/usr/share/doc/intel-mkl/documentation_2019/en/mkl/': No 
such file or directory
root@vb-math:/home/randy# ls -la 
/usr/share/doc/intel-mkl/documentation_2020/en/mkl/ps2020/get_started.htm 
-rw-r--r-- 1 root root 13086 Sep 17  2020 
/usr/share/doc/intel-mkl/documentation_2020/en/mkl/ps2020/get_started.htm
root@vb-math:/home/randy# 


root@vb-math:/home/randy# lsb_release -rd
Description:Ubuntu 21.04
Release:21.04
root@vb-math:/home/randy# apt list | fgrep intel-mkl-doc

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.

intel-mkl-doc/hirsute,now 2020.4.304-2 all [installed,automatic]

root@vb-math:/home/randy# dpkg -S /usr/share/doc-base/intel-mkl-documentation
intel-mkl-doc: /usr/share/doc-base/intel-mkl-documentation
root@vb-math:/home/randy# 


In the /usr/share/doc-base/intel-mkl-documentation file there are references to 
2019 that should be 2020.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: intel-mkl-doc (not installed)
ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
Uname: Linux 5.11.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul  4 10:03:37 2021
InstallationDate: Installed on 2021-06-22 (12 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: intel-mkl
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: intel-mkl (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute wayland-session

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

Title:
  doc-base/intel-mkl-documentation references non-existent file

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

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

[Bug 1915762] [NEW] package linux-image-4.4.0-198-generic 4.4.0-198.230 failed to install/upgrade: run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 1

[Austin Javier De Leon Martinez]

Public bug reported:

I am trying to install the aduini IDE and also some serial libraries for
the communication between arduino and the system and in both occasions I
get this error

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-198-generic 4.4.0-198.230
ProcVersionSignature: Ubuntu 4.4.0-201.233-generic 4.4.247
Uname: Linux 4.4.0-201-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.30
Architecture: amd64
Date: Thu Feb 11 13:49:25 2021
ErrorMessage: run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return 
code 1
InstallationDate: Installed on 2021-01-06 (40 days ago)
InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release amd64 (20190304.5)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.6
 apt  1.2.32ubuntu0.2
SourcePackage: grub
Title: package linux-image-4.4.0-198-generic 4.4.0-198.230 failed to 
install/upgrade: run-parts: /etc/kernel/postrm.d/zz-update-grub exited with 
return code 1
UpgradeStatus: Upgraded to xenial on 2021-01-06 (40 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package linux-image-4.4.0-198-generic 4.4.0-198.230 failed to
  install/upgrade: run-parts: /etc/kernel/postrm.d/zz-update-grub exited
  with return code 1

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

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

[Bug 971221]

[Austin English]

Closing.

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

Title:
  Can not login to Picasa 3.9 under Wine

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

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

[Bug 971221]

[Austin English]

Closing.

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

Title:
  Can not login to Picasa 3.9 under Wine

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

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

[Bug 1905631] [NEW] unable to upgrade from 18.04 to 20.04

[Austin]

Public bug reported:

when attempting to upgrade from 18.04 to 20.04 i get:

Calculating the changes

Could not calculate the upgrade

An unresolvable problem occurred while calculating the upgrade.

This was likely caused by: 
* Unofficial software packages not provided by Ubuntu 
Please use the tool 'ppa-purge' from the ppa-purge 
package to remove software from a Launchpad PPA and 
try the upgrade again. 

If none of this applies, then please report this bug using the 
command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If 
you want to investigate this yourself the log files in 
'/var/log/dist-upgrade' will contain details about the upgrade. 
Specifically, look at 'main.log' and 'apt.log'. 


I have tried using ppa-purge, but this did not make a difference

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.40
ProcVersionSignature: Ubuntu 5.4.0-54.60~18.04.1-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 25 17:10:19 2020
InstallationDate: Installed on 2020-10-12 (44 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2020-11-25 (0 days ago)

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic dist-upgrade

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

Title:
  unable to upgrade from 18.04 to 20.04

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

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

[Bug 1904700] Re: Mouse settings not reapplied after reconnect or resume

[Austin Riedhammer]

Same issue here, except I noticed the problem because my mouse speed was
getting reset after every reboot and most times I resumed from sleep.
The speed displayed on the slider is correct so I usually just have to
wiggle the slider to get it to actually apply the correct speed, but the
same thing happens if I set the primary button to right instead of left.

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

Title:
  Mouse settings not reapplied after reconnect or resume

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

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

[Bug 1767361] Re: 4.6.6deb5 not working on Bionic as PHP 7.2 is default

[Austin Dunham]

Hi William,
   I realize I never responded.
   I ended up using the PPA on Ubuntu 18.04 and it's working.

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

Title:
  4.6.6deb5 not working on Bionic as PHP 7.2 is default

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

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

[Bug 534179] Re: Feature Request: Include bash syslog package

[Austin Parker]

Any progress on this? It's still an issue in 18.04(bash 4) and
20.04(bash 5)

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

Title:
  Feature Request: Include bash syslog package

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

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

[Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices

[Austin Abraham A H]

You're a lifesaver Kai!!

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

Title:
  Lenovo ThinkBook 14-IML Touchpad not showing up in
  /proc/bus/input/devices

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

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

[Bug 1767361] Re: 4.6.6deb5 not working on Bionic as PHP 7.2 is default

[Austin Dunham]

I re-read William Desportes's comment #22 and the fix is in Debian's 
buster-backports repository.
It does not appear to be in Ubuntu's bionic-backports.

I'm not sure if this is right, but it may be simpler to apply the patch
that's attached to this bug rather than trying to use a backport from a
whole different, if related, distro.

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

Title:
  4.6.6deb5 not working on Bionic as PHP 7.2 is default

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

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

[Bug 1767361] Re: 4.6.6deb5 not working on Bionic as PHP 7.2 is default

[Austin Dunham]

It says this is fixed/released in Ubuntu.
I'm running Ubuntu 18.04.5 LTS
I'm still seeing phpmyadmin Version information: 4.6.6deb5

Is this only fixed in the non-LTS version of Ubuntu?
I've done apt-get update, but that doesn't seem to bring down a new version of 
the software.
I can add the PPA if I have to, but I'm wondering if there's something else I'm 
missing here.

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

Title:
  4.6.6deb5 not working on Bionic as PHP 7.2 is default

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

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

[Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape

[Matt Austin]

Thank you for fixing this bug. Installing mutter 3.36.4-0ubuntu0.20.04.1
and libmutter 3.36.4-0ubuntu0.20.04.1 from focal-proposed has resolved
this issue for me.

Note: The updated libmutter from focal-proposed also had to be
explicitly installed by me, as it was not automatically pulled in when
updating mutter.

Steps:
1) Enabled focal-proposed
2) apt update
3) apt install mutter libmutter
4) Disabled focal-proposed
5) Removed ~/.config/monitors.xml and ~gdm/config/monitors.xml
6) Rebooted
7) After login, I successfully applied my desired monitor configuration 
(changing the primary monitor and setting other monitor to portrait 
orientation).


Side notes:
1) I still had to copy ~/.config/monitors.xml to ~gdm/.config/monitors.xml for 
the correct primary monitor and orientation to be set on the login screen.
2) After applying the display configuration, the icons in the top-right of the 
gnome panel appeared blured (network/bluetooth). This was resolved by applying 
150% fractional scaling and then applying 100% scaling again in the gnome 
display settings. I haven't had time to reproduce this to know if it's a 
one-off or ongoing bug.

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

Title:
  [nvidia] Rotating secondary monitor to portrait fails, results in
  landscape

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1874567/+subscriptions

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

[Bug 1868699] Re: jlink fails due to unexpected hash of java.* modules

[Austin Lehman]

I had this issue with openjdk-14-jdk. I then installed the AdoptOpenJDK
repository instance (adoptopenjdk-14-hotspot) and have the same error.

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

Title:
  jlink fails due to unexpected hash of java.* modules

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

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

[Bug 1874567] Re: Secondary (rotated) monitor configuration is not applied correctly in gnome settings

[Matt Austin]

** Attachment added: "Screenshot from 2020-04-24 08-37-43.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1874567/+attachment/5358812/+files/Screenshot%20from%202020-04-24%2008-37-43.png

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

Title:
  Secondary (rotated) monitor configuration is not applied correctly in
  gnome settings

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

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

[Bug 1874567] [NEW] Secondary (rotated) monitor configuration is not applied correctly in gnome settings

[Matt Austin]

Public bug reported:

I have two monitors, with the secondary one rotated in a portrait
orientation. Using the nvidia 440 drivers, the orientation is not
applied when configuring in gnome settings (the displays go blank for a
second, and then reappear in landscape orientation).

Using nvidia settings, I can set the monitor rotation and offset
correctly, however these settings do not persist on next boot (even when
selecting to save to xorg.conf).


When using the nouveau drivers, the orientation is applied correctly in gnome 
settings, and is persisted.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.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  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: GNOME
Date: Fri Apr 24 08:30:41 2020
DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] 
[1462:2871]
InstallationDate: Installed on 2018-05-01 (723 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Shuttle Inc. SZ77
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago)
dmi.bios.date: 10/13/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.13
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: FZ77
dmi.board.vendor: Shuttle Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: SZ77
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Shuttle Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
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:1.20.8-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-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 nvidia ubuntu

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

Title:
  Secondary (rotated) monitor configuration is not applied correctly in
  gnome settings

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

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

[Bug 1817244]

[Austin English]

Closing.

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

Title:
  Game needs gstreamer1.0-plugins-good

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

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

[Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock

[Matt Austin]

** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853094/+attachment/5310910/+files/Xorg.0.log

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

Title:
  Screen tearing in xorg gnome session on Latitude 7480 with WD19TB
  Thunderbolt dock

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

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

[Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock

[Matt Austin]

** Attachment added: "lspci -k"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853094/+attachment/5310908/+files/lspcik.txt

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

Title:
  Screen tearing in xorg gnome session on Latitude 7480 with WD19TB
  Thunderbolt dock

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

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

[Bug 1846398] Re: Fractional scaling has significant visible tearing in Xorg sessions

[Matt Austin]

Thanks for the feedback, but I don't believe I am using fractional
scaling. My scaling is set to 100%, but I have changed the font scaling
to 1.25.

If I set font scaling to 1.0, then I see the same tearing.

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

Title:
  Fractional scaling has significant visible tearing in Xorg sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1846398/+subscriptions

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

[Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock

[Matt Austin]

** Attachment added: "tearing-1.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+attachment/5307224/+files/tearing-1.mp4

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

Title:
  Screen tearing in xorg gnome session on Latitude 7480 with WD19TB
  Thunderbolt dock

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

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

[Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock

[Matt Austin]

** Attachment added: "tearing-2.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+attachment/5307225/+files/tearing-2.mp4

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

Title:
  Screen tearing in xorg gnome session on Latitude 7480 with WD19TB
  Thunderbolt dock

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

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

[Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock

[Matt Austin]

*-display 
   description: VGA compatible controller
   product: HD Graphics 620
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 02
   width: 64 bits
   clock: 33MHz
   capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:140 memory:eb00-ebff memory:a000-afff 
ioport:f000(size=64) memory:c-d


The two monitors are 2560x1440, with no scaling. But I do use a 1.25
font scaling factor in gnome-tweaks.


I am using the ubuntu-x-swat ppa, which was an attempt to resolve some previous 
graphics issues, but I can try removing this again if you'd like me to test?

libdrm-amdgpu1: ubuntu-x-swat/updates/ubuntu
libdrm-common: ubuntu-x-swat/updates/ubuntu
libdrm-dev: ubuntu-x-swat/updates/ubuntu
libdrm-intel1: ubuntu-x-swat/updates/ubuntu
libdrm-nouveau2: ubuntu-x-swat/updates/ubuntu
libdrm-radeon1: ubuntu-x-swat/updates/ubuntu
libdrm2: ubuntu-x-swat/updates/ubuntu
libegl-mesa0: ubuntu-x-swat/updates/ubuntu
libegl1-mesa: ubuntu-x-swat/updates/ubuntu
libgbm1: ubuntu-x-swat/updates/ubuntu
libgl1-mesa-dev: ubuntu-x-swat/updates/ubuntu
libgl1-mesa-dri: ubuntu-x-swat/updates/ubuntu
libgl1-mesa-glx: ubuntu-x-swat/updates/ubuntu
libglapi-mesa: ubuntu-x-swat/updates/ubuntu
libglx-mesa0: ubuntu-x-swat/updates/ubuntu
libllvm9: ubuntu-x-swat/updates/ubuntu
libxatracker2: ubuntu-x-swat/updates/ubuntu
mesa-common-dev: ubuntu-x-swat/updates/ubuntu
mesa-va-drivers: ubuntu-x-swat/updates/ubuntu
mesa-vdpau-drivers: ubuntu-x-swat/updates/ubuntu


** Attachment added: "journalctl.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+attachment/5306546/+files/journalctl.txt

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

Title:
  Screen tearing in xorg gnome session on Latitude 7480 with WD19TB
  Thunderbolt dock

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

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

[Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock

[Matt Austin]

** Attachment added: "modinfo-i915.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+attachment/5306547/+files/modinfo-i915.txt

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

Title:
  Screen tearing in xorg gnome session on Latitude 7480 with WD19TB
  Thunderbolt dock

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

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

[Bug 1853094] [NEW] Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock

[Matt Austin]

Public bug reported:

I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480
laptop with two external displays. The laptop itself is closed (internal
display is not used).

In a gnome xorg session, there is severe tearing on parts of the screen
when dragging windows or scrolling content.

Under a wayland session there is no screen tearing, but I have keyboard
key repetition problems which make this mostly unusable day-to-day
(https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405).

I can supply short phone videos of tearing occurring on the screens if
required.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: mutter 3.28.4-0ubuntu18.04.2
ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Nov 19 14:02:09 2019
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Summary changed:

- Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thubderbolt 
dock
+ Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt 
dock

** Description changed:

- I have the WD19TB Thubderbolt dock connected to a Dell Latitude 7480
+ I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480
  laptop with two external displays. The laptop itself is closed (internal
  display is not used).
  
  In a gnome xorg session, there is severe tearing on parts of the screen
  when dragging windows or scrolling content.
  
  Under a wayland session there is no screen tearing, but I have keyboard
  key repetition problems which make this mostly unusable day-to-day
  (#1849405).
  
  I can supply short phone videos of tearing occurring on the screens if
  required.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Nov 19 14:02:09 2019
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_AU.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_AU.UTF-8
+  SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480
  laptop with two external displays. The laptop itself is closed (internal
  display is not used).
  
  In a gnome xorg session, there is severe tearing on parts of the screen
  when dragging windows or scrolling content.
  
  Under a wayland session there is no screen tearing, but I have keyboard
  key repetition problems which make this mostly unusable day-to-day
- (#1849405).
+ (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405).
  
  I can supply short phone videos of tearing occurring on the screens if
  required.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Nov 19 14:02:09 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Screen tearing in xorg gnome session on Latitude 7480 with WD19TB
  Thunderbolt dock

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

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

[Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

[Austin Coleman]

This happens to me about three times a week on Ubuntu 18.04.3 LTS with
kernel 4.15.0-70-generic. I have not been able to find a way to
consistently reproduce it. It is a random complete system freeze. The
mouse does not respond, caps lock and numlock do not change light on
keyboard, ctrl alt f2/f3/etc does not work, and even Alt + SysRq REISUB
does not respond. Only a hard reset works by pressing the power button
will reboot the system. The first sign of it happening is the mouse
begins to stutter for a couple seconds before the whole screen
completely freezes. Here is some system info:

CPU: AMD Ryzen Threadripper 1950X 16-Core Processor
Graphics: Nvidia Quadro P4000 
Motherboard: Asus ROG STRIX X399-E GAMING
Ubuntu version: 18.04.3
Memory: 62.8 GiB
Gnome: 3.28.2
Disk capacity: 903.7 GB

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

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

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

[Bug 1849405] Re: Repeated keypresses from bluetooth keyboard

[Matt Austin]

I've now been using an Xorg session rather than Wayland and haven't seen
the repeated keys issue. I do get some very nasty screen tearing when
scrolling (e.g. websites) on Xorg however, so ideally I'd like to
continue using Wayland.

Does that mean that this is likely a mutter bug, rather than bluez?

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

Title:
  Repeated keypresses from bluetooth keyboard

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

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

[Bug 1849405] [NEW] Repeated keypresses from bluetooth keyboard

[Matt Austin]

Public bug reported:

I have a Microsoft Surface bluetooth keyboard, and semi-frequently (e.g.
around every 10-15mins) end up with repeated keypresses being made (e.g.
apppt get update).

This seems to happen when the machine is under slight stress, or when a
new notification pops up in gnome, so it could be related to wayland
possibly - but even if wayland or other processes are causing stress, I
should imagine the bluetooth hid driver should not cause repeated key
presses.

Please let me know if you require further information about my
environment, it's difficult to know where to begin with determining
which process is the root cause of this.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3.2
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
Date: Wed Oct 23 09:38:20 2019
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Latitude 7480
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=/dev/mapper/sarasota--kf--vg-root ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.1
dmi.board.name: 00F6D3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd07/04/2019:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 7480
dmi.product.sku: 07A0
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: F8:63:3F:E9:51:8C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:1658613 acl:66750 sco:0 events:15708 errors:0
TX bytes:605292 acl:98 sco:0 commands:2484 errors:0

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


** Tags: amd64 apport-bug bionic

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

Title:
  Repeated keypresses from bluetooth keyboard

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

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

[Bug 1735099] Re: Realtek Card Reader not working (kernel driver)

[Austin]

Just wanted to update, I am the user TJ is referring to. The issue was
resolved after running "sudo update-initramfs -u" after the commands in
the readme of the linked github repository as detailed here: http
://baby-panda.github.io/linux/RTS5229_driver/

The new driver installation be verified by running "lspci -v"

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

Title:
  Realtek Card Reader not working (kernel driver)

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

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

[Bug 1809826] ProcCpuinfoMinimal.txt

[Austin Lehman]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1809826/+attachment/5227745/+files/ProcCpuinfoMinimal.txt

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

Title:
  Gnome Activites view on multiple desktops wrong applications

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

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

[Bug 1809826] GsettingsChanges.txt

[Austin Lehman]

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1809826/+attachment/5227744/+files/GsettingsChanges.txt

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

Title:
  Gnome Activites view on multiple desktops wrong applications

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

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

[Bug 1809826] Re: Gnome Activites view on multiple desktops wrong applications

[Austin Lehman]

The bug 1743736 seems to be the same issue from what I can tell from the
description. I ran the apport-collect. Please let me know if there's
anything else I can provide to help with this. Much thanks!

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

Title:
  Gnome Activites view on multiple desktops wrong applications

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

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

[Bug 1809826] Re: Gnome Activites view on multiple desktops wrong applications

[Austin Lehman]

apport information

** Tags added: apport-collected

** Description changed:

  I have 2 monitors and have configured through tweak tool on the
  "Workspaces" tab "Dynamic Workspaces" and "Workspaces span displays".
  Everything is working as advertised except that when I hit the
  Meta/Windows key or use hot corner to open the Gnome Activities view on
  the second monitor only it shows the application windows for all 2nd
  monitor workspaces together. On the primary monitor it only shows the
  applications that exist for that monitor on that workspace. I believe it
  should show on the 2nd display only the applications that exist for that
  display in the current work space. This is how it functioned on the
  previous version of Ubuntu I was using prior to install of Ubuntu 18.10.
  
  Thanks!
  
  Description:  Ubuntu 18.10
  Release:  18.10
  Gnome 3.30.1
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu13.1
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 18.10
+ InstallationDate: Installed on 2018-12-19 (20 days ago)
+ InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
+ Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
+ Tags:  cosmic
+ Uname: Linux 4.18.0-13-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1809826/+attachment/5227743/+files/Dependencies.txt

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

Title:
  Gnome Activites view on multiple desktops wrong applications

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

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

[Bug 1809826] [NEW] Gnome Activites view on multiple desktops wrong applications

[Austin Lehman]

Public bug reported:

I have 2 monitors and have configured through tweak tool on the
"Workspaces" tab "Dynamic Workspaces" and "Workspaces span displays".
Everything is working as advertised except that when I hit the
Meta/Windows key or use hot corner to open the Gnome Activities view on
the second monitor only it shows the application windows for all 2nd
monitor workspaces together. On the primary monitor it only shows the
applications that exist for that monitor on that workspace. I believe it
should show on the 2nd display only the applications that exist for that
display in the current work space. This is how it functioned on the
previous version of Ubuntu I was using prior to install of Ubuntu 18.10.

Thanks!

Description:Ubuntu 18.10
Release:18.10
Gnome 3.30.1

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

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

Title:
  Gnome Activites view on multiple desktops wrong applications

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

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

[Bug 626321]

[Austin English]

This was inadvertently caught up in my unclosed bugs filter. NOTOURBUG
should only be closed when fixed upstream.

Setting back to RESOLVED NOTOURBUG.

Sorry for the spam.

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

Title:
  X.org server should keep track of and restore its initial (desktop)
  resolution and refresh rate

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

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

[Bug 978678]

[Austin English]

Closing.

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

Title:
  Starcraft II crashes before login in 12.04 (regression from 11.10)

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

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

[Bug 1014671]

[Austin English]

Closing.

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

Title:
  Wine "iWisoft Flash SWF to Video Converter" crashes Unity

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

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

[Bug 1014671]

[Austin English]

This was inadvertently caught up in my unclosed bugs filter. NOTOURBUG
should only be closed when fixed upstream.

Setting back to RESOLVED NOTOURBUG.

Sorry for the spam.

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

Title:
  Wine "iWisoft Flash SWF to Video Converter" crashes Unity

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

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

[Bug 900901]

[Austin English]

Closing.

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

Title:
  Steam overlay does not work due to GCC-4.6 issues

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

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

[Bug 626321]

[Austin English]

Closing.

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

Title:
  X.org server should keep track of and restore its initial (desktop)
  resolution and refresh rate

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

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

[Bug 978678]

[Austin English]

This was inadvertently caught up in my unclosed bugs filter. NOTOURBUG
should only be closed when fixed upstream.

Setting back to RESOLVED NOTOURBUG.

Sorry for the spam.

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

Title:
  Starcraft II crashes before login in 12.04 (regression from 11.10)

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

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

[Bug 900901]

[Austin English]

This was inadvertently caught up in my unclosed bugs filter. NOTOURBUG
should only be closed when fixed upstream.

Setting back to RESOLVED NOTOURBUG.

Sorry for the spam.

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

Title:
  Steam overlay does not work due to GCC-4.6 issues

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

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

[Bug 1792998] [NEW] wont work on my VM

[Austin Brouse]

Public bug reported:

wont work on my vm.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.6
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 17 11:04:32 2018
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu

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

Title:
  wont work on my VM

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

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

[Bug 1706780] Re: pthread_mutex_lock robust hangs

[Austin Hendrix]

I'm using robust mutexes in a similar way, and I've found that if I use
PTHREAD_PRIO_INHERIT attribute on my mutexes, I can no longer reproduce
this bug.

It looks like this is similar to
https://bugzilla.redhat.com/show_bug.cgi?id=1401665 .

** Bug watch added: Red Hat Bugzilla #1401665
   https://bugzilla.redhat.com/show_bug.cgi?id=1401665

** Attachment added: "Fixed test"
   
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1706780/+attachment/5188152/+files/tr.c

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

Title:
  pthread_mutex_lock robust hangs

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

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

[Bug 1766325] Re: sudo: pam_unix(sudo:auth): conversation failed

[Austin]

Currently without any changes to my setup...

Only one user after upgrade can be granted sudo privileges in my ubuntu
installation.

Therefore adding sudo privileges only works once after upgrading my
machine.

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

Title:
  sudo: pam_unix(sudo:auth): conversation failed

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

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

[Bug 1766325] Re: sudo: pam_unix(sudo:auth): conversation failed

[Austin]

I have the same issue.
Both after adding a new user or doing a password change to a current user I 
have the same problem.

I cannot do a clean install because my server service provider had an
older distribution for installation only, not 18.04

Luckily I have multiple user accounts with sudo access from 17.10,
however this is a really annoying bug and a security problem for myself
personally, as I am afraid that if I change my passwords something bad
might happen.

Does Ubuntu do bounty for bugs? I would definitely pay/contribute to
have this fixed?

I will continue looking for now.

I have changed my password multiple times and made it as short as
possible to make sure the character input was correct.

I am willing to ugrade again if that will fix things.


Does this have something to do with my /etc/shadow and possibly the hash
salt changing?

Error log:

Sep  7 15:37:31 localhost sudo: pam_unix(sudo:auth): authentication failure; 
logname=user1 uid=1003 euid=0 tty=/dev/pts/1 ruser=user1 rhost=  user=user1
Sep  7 15:40:41 localhost sudo: pam_unix(sudo:auth): auth could not identify 
password for [user1]
Sep  7 15:40:41 localhost sudo: user1 : 1 incorrect password attempt ; 
TTY=pts/1 ; PWD=/home/user1 ; USER=root ; COMMAND=/usr/bin/test


sudoers:

#
# This file MUST be edited with the 'visudo' command as root.
#
# Please consider adding local content in /etc/sudoers.d/ instead of
# directly modifying this file.
#
# See the man page for details on how to write a sudoers file.
#
Defaultsenv_reset
Defaultsmail_badpass
Defaults
secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin"

# Host alias specification

# User alias specification

# Cmnd alias specification

# User privilege specification
rootALL=(ALL:ALL) ALL

# Members of the admin group may gain root privileges
%admin ALL=(ALL) ALL

# Allow members of group sudo to execute any command
%sudo   ALL=(ALL:ALL) ALL

# See sudoers(5) for more information on "#include" directives:

#includedir /etc/sudoers.d

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

Title:
  sudo: pam_unix(sudo:auth): conversation failed

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

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

[Bug 194271]

[Austin English]

Is this still an issue in current (1.7.36 or newer) wine? Can it be
reproduced in any of the free trials?

http://www.acdsee.com/en/free-trials

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

Title:
  'acdsee pro 2' doesn't start with wine

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

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

[Bug 194271]

[Austin English]

Over 2 years with no reply, marking abandoned.

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

Title:
  'acdsee pro 2' doesn't start with wine

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

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

[Bug 565342]

[Austin English]

*** Bug 45164 has been marked as a duplicate of this bug. ***

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

Title:
  System-wide installation of Windows applications

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

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

[Bug 1570769] Re: Bottom solder mask omitted

[David Austin]

Hi Bert,

All fab houses that I've dealt with want a bottom mask gerber - even
if there's no apertures.

David

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

Title:
  Bottom solder mask omitted

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

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

[Bug 1570769] Re: Bottom solder mask omitted

[David Austin]

Hi Bert,

I believe that this is still a bug.  Unchecking "all-layers"
clearly suppresses any layer with no apertures.  This is 
incorrect behaviour for the bottom-mask when there are 
tracks on the bottom layer.

Checking the "all-layers" is a work-around - but isn't ideal - 
perfectly valid PCBs require manual intervention to generate
gerbers correctly.

David

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

Title:
  Bottom solder mask omitted

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

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

[Bug 1570769] Re: Bottom solder mask omitted

[David Austin]

Please see attached PCB.  It has tracks on the bottom side and so should have a 
solder mask for that side.  However, no solder mask is generated.

** Attachment added: "test.pcb"
   
https://bugs.launchpad.net/ubuntu/+source/pcb/+bug/1570769/+attachment/513/+files/test.pcb

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

Title:
  Bottom solder mask omitted

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

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

[Bug 1570769] Re: Bottom solder mask omitted

[David Austin]

Yes - that's correct.  In some cases, there is no output file for the
bottom soldermask, even though there is a bottom layer.  My guess is
that this occurs when there's no openings in the bottom soldermask (no
pads or pins).  However, this isn't correct behaviour IMHO - it should
generate a bottom soldermask file.

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

Title:
  Bottom solder mask omitted

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

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

[Bug 357456]

[Austin English]

(In reply to Andy P from comment #138)
> Thanks, Zebediah. Does that mean -staging builds from then on? Or -devel too?

Just staging.

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

Title:
  Wine 1.1.20 crashes while installing Photoshop CS4

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

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

[Bug 702452]

[Austin English]

(In reply to Eike Hein from comment #19)
> I've tested this now and I can confirm it works nicely. Thanks, this
> improves the experience for our users quite a bit.

Reported fixed (please reopen if it's not).

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

Title:
  [launcher] Wine applications are wrongly matched

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

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

[Bug 1103833]

[Austin English]

(In reply to Eike Hein from comment #19)
> I've tested this now and I can confirm it works nicely. Thanks, this
> improves the experience for our users quite a bit.

Reported fixed (please reopen if it's not).

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

Title:
  Wine's icon and description appears for all Windows applications

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

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

[Bug 1733605] Re: elantech touchpad of Lenovo L480/580 failed to detect hw_version

[Austin Riedhammer]

I believe this may also be the same issue I'm having with my Lenovo
T480s, which has an Elantech touchpad and I see the same error on boot
from a "dmesg | grep elantech".  I'm running 17.10, current kernel
version is 4.13.0-36-generic, and I have the same symptoms (no
multitouch, two finger scroll, etc.).

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

Title:
  elantech touchpad of Lenovo L480/580 failed to detect hw_version

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1733605/+subscriptions

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

[Bug 1751644] [NEW] package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers looping, abandoned

[Austin]

Public bug reported:

Ubuntu 18.04 (beta)
package dbus 1.12.2-1

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: dbus 1.12.2-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Sun Feb 25 04:24:01 2018
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2018-02-19 (6 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~alpha7ubuntu2
SourcePackage: dbus
Title: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to bionic on 2018-02-25 (0 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers
  looping, abandoned

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

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

[Bug 1747786] [NEW] package xfstt 1.9.3-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Austin]

Public bug reported:

While installing Autodesk Maya

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: xfstt 1.9.3-1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
AptOrdering:
 xfstt:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Tue Feb  6 18:30:26 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2018-02-06 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: xfstt
Title: package xfstt 1.9.3-1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful

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

Title:
  package xfstt 1.9.3-1 failed to install/upgrade: subprocess installed
  post-installation script returned error exit status 1

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

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

[Bug 1741671] Re: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build [nv-linux.h:199:2: error: #error "This driver requires the ability to change memory types!"]

[Matt Austin]

Possible duplicate of #1724872.

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

Title:
  nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed
  to build [nv-linux.h:199:2: error: #error "This driver requires the
  ability to change memory types!"]

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

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

[Bug 1741671] Re: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build [nv-linux.h:199:2: error: #error "This driver requires the ability to change memory types!"]

[Matt Austin]

Thank you - I can confirm that installing nvidia-340 from xenial-
proposed resolved this for me.

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

Title:
  nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed
  to build [nv-linux.h:199:2: error: #error "This driver requires the
  ability to change memory types!"]

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

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

Re: [Bug 1735798] Re: Unable to access any subdomain provided by VPN provider until reboot.

[Austin Hester]

I have figured this out as well. It would be nice to be able to use
gnome-network-manager though.

On Jan 9, 2018 18:25, "mash" <1735...@bugs.launchpad.net> wrote:

> The problem occurs when I use network-manager to initiate the VPN.
>
>
> The problem does not occur when I run openconnect from the command line:
>
> sudo openconnect --cafile /etc/ssl/certs/ca-certificates.crt --juniper
> https://vpn.myschool.edu
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1735798
>
> Title:
>   Unable to access any subdomain provided by VPN provider until reboot.
>
> Status in network-manager package in Ubuntu:
>   Confirmed
> Status in openconnect package in Ubuntu:
>   Confirmed
>
> Bug description:
>   After disconnecting from VPN, ubuntu is unable to reconnect to the VPN
>   and any domain hosted by the server. For reference, this is my
>   school's VPN, and I am unable to get on mygateway or even the school's
>   main website after I disconnect from the VPN or the computer sleeps
>   after the VPN has been started. It uses EAP authentication.
>
>   Here is the log after connecting once, turning off, and restarting:
>   LOG:
>   POST https://vpn.myschool.edu/
>   getaddrinfo failed for host 'vpn.myschool.edu': Name or service not
> known
>   Failed to open HTTPS connection to vpn.myschool.edu
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: network-manager 1.8.4-1ubuntu3
>   ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
>   Uname: Linux 4.13.0-17-generic x86_64
>   ApportVersion: 2.20.7-0ubuntu3.5
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Dec  1 11:39:56 2017
>   IfupdownConfig:
># interfaces(5) file used by ifup(8) and ifdown(8)
>auto lo
>iface lo inet loopback
>   InstallationDate: Installed on 2016-12-02 (364 days ago)
>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
>   IpRoute:
>default via 192.168.1.1 dev wlp5s0 proto static metric 600
>169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
>192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.144
> metric 600
>192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
> linkdown
>   NetworkManager.state:
>[main]
>NetworkingEnabled=true
>WirelessEnabled=true
>WWANEnabled=true
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: network-manager
>   UpgradeStatus: Upgraded to artful on 2017-10-24 (38 days ago)
>   nmcli-nm:
>RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING
> WIFI-HW  WIFI WWAN-HW  WWAN
>running  1.8.4connected  started  full  enabled
>  enabled  enabled  enabled  enabled
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1735798/+
> subscriptions
>

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

Title:
  Unable to access any subdomain provided by VPN provider until reboot.

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

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

[Bug 1735798] [NEW] Unable to access any subdomain provided by VPN provider until reboot.

[Austin Hester]

Public bug reported:

After disconnecting from VPN, ubuntu is unable to reconnect to the VPN
and any domain hosted by the server. For reference, this is my school's
VPN, and I am unable to get on mygateway or even the school's main
website after I disconnect from the VPN or the computer sleeps after the
VPN has been started. It uses EAP authentication.

Here is the log after connecting once, turning off, and restarting:
LOG:
POST https://vpn.myschool.edu/
getaddrinfo failed for host 'vpn.myschool.edu': Name or service not known
Failed to open HTTPS connection to vpn.myschool.edu

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec  1 11:39:56 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-12-02 (364 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
IpRoute:
 default via 192.168.1.1 dev wlp5s0 proto static metric 600
 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
 192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.144 metric 600
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to artful on 2017-10-24 (38 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug artful wayland-session

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

** Description changed:

  After disconnecting from VPN, ubuntu is unable to reconnect to the VPN
  and any domain hosted by the server. For reference, this is my school's
  VPN, and I am unable to get on mygateway or even the school's main
  website after I disconnect from the VPN or the computer sleeps after the
- VPN has been started.
+ VPN has been started. It uses EAP authentication.
+ 
+ Here is the log after connecting once, turning off, and restarting:
+ LOG:
+ POST https://vpn.myschool.edu/
+ getaddrinfo failed for host 'vpn.myschool.edu': Name or service not known
+ Failed to open HTTPS connection to vpn.myschool.edu
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  1 11:39:56 2017
  IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  auto lo
-  iface lo inet loopback
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
  InstallationDate: Installed on 2016-12-02 (364 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
-  default via 192.168.1.1 dev wlp5s0 proto static metric 600 
-  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
-  192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.144 metric 
600 
-  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
+  default via 192.168.1.1 dev wlp5s0 proto static metric 600
+  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
+  192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.144 metric 
600
+  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
-  [main]
-  NetworkingEnabled=true
-  WirelessEnabled=true
-  WWANEnabled=true
+  [main]
+  NetworkingEnabled=true
+  WirelessEnabled=true
+  WWANEnabled=true
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to artful on 2017-10-24 (38 days ago)
  nmcli-nm:
-  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
-  running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled
+  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
+  running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

-- 
You received this bug notification beca

[Bug 357456]

[Austin English]

(In reply to Giacomo Orlandi from comment #126)
> (In reply to fjfrackiewicz from comment #125)
> [...]
> > > > I submitted the patch to Wine Staging:
> > > > https://dev.wine-staging.com/patches/132/
> > > > Let's hope this gets accepted.
> > > 
> > > It has been accepted into Staging. Yay!
> > 
> > Shouldn't the status be set to "staging" along with the accepted patchset?
> 
> The description of the patch above says it's only a workaround to make the
> apps work until there is a proper fix.
> 
> I can't see a policy for this in https://wiki.winehq.org/Bugs
> but I assume that a bug can be marked as "fixed on staging" only if it's a
> proper fix, even if it hasn't been merged into the main codebase yet because
> it needs reviewing and some improvements.

That's not such an easy distinction to make. If the fix is proper, it
wouldn't be in staging anyway, but in vanilla Wine.

If the bug exists in vanilla wine, but not wine-staging, it is
reasonable to make the status 'STAGED'.

Side note: the staging version is less hacky than the original
submission..

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

Title:
  Wine 1.1.20 crashes while installing Photoshop CS4

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

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

[Bug 1706485] [NEW] Installer crashed?

[Austin Harshberger]

Public bug reported:

Don't really have any further details except for that the install
crashed during the later stages .. I was messing around on my computer
during the installation, I'm not sure if that has anything to do with
it?

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ubiquity 17.04.9
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CasperVersion: 1.380
CurrentDesktop: KDE
Date: Tue Jul 25 19:46:58 2017
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/kubuntu.seed 
boot=casper maybe-ubiquity quiet splash ---
LiveMediaBuild: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kubuntu third-party-packages ubiquity-17.04.9 zesty

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

Title:
  Installer crashed?

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

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

[Bug 619403] Re: [KDE] no option for mouse wheel acceleration

[Austin]

** Changed in: xorg-server (Ubuntu)
   Status: Opinion => Confirmed

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

Title:
  [KDE] no option for mouse wheel acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions

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

[Bug 1679366] Re: (update-manager) package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status

[Austin Dempewolff]

I had the same crash while using the additional drivers GUI to switch
the the proprietary nvidia drivers.

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

Title:
  (update-manager) package shim-signed
  1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

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

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

[Bug 1650846] [NEW] shellcheck: unable to decommit memory: Invalid argument (0.4.4)

[Austin English]

Public bug reported:

I reported this upstream [1], but there's been a release since then, and
the author hasn't seen the issue either.

When I run shellcheck on my upstream project under Travis-CI, I see several 
occurrences of:
shellcheck: unable to decommit memory: Invalid argument
shellcheck: unable to decommit memory: Invalid argument
shellcheck: unable to decommit memory: Invalid argument
shellcheck: unable to decommit memory: Invalid argument
shellcheck: unable to decommit memory: Invalid argument
shellcheck: unable to decommit memory: Invalid argument
shellcheck: unable to decommit memory: Invalid argument
shellcheck: unable to decommit memory: Invalid argument
shellcheck: unable to decommit memory: Invalid argument

>From upstream:
"I haven't seen this error before. From what I can tell from GHC issues 12865 
and 12495, it may happen when GHC/shellcheck is built on a newer system but 
runs on one with an older kernel."

Note that this does NOT occur on OS X with 0.4.5, so either it's an
issue in the older version (and the package needs an update), or it's a
Ubuntu specific build issue.

To reproduce:
* ensure you have shellcheck-0.4.4-4 installed
* wget 
https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetricks
* shellcheck winetricks

1: https://github.com/koalaman/shellcheck/issues/785

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

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

Title:
  shellcheck: unable to decommit memory: Invalid argument (0.4.4)

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

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

[Bug 1637683] Re: ubuntu 16.10 internal speakers don't work, but headphones do

[Austin Clements]

PSA: This may be related to a broken headphone jack that is supposed to
detect whether headphones are plugged in and change output accordingly.
Work around in ubuntu right now is to run alsamixer from terminal,
select correct soundcard, then disable auto-mute, then unmute and turn
up speakers.

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

Title:
  ubuntu 16.10 internal speakers don't work, but headphones do

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

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

[Bug 1637683] [NEW] ubuntu 10.16 internal speakers don't work, but headphones do

[Austin Clements]

Public bug reported:

Under sound settings only headphone output is listed as an option, no
internal speakers are listed. Headphone playback does work. In
alsamixer, speaker output was at 0 and muted, but unmuting and
increasing volume does not produce playback in speakers.

ASUS X550LB laptop

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  austinclem1   1647 F pulseaudio
 /dev/snd/controlC0:  austinclem1   1647 F pulseaudio
CurrentDesktop: Unity
Date: Fri Oct 28 20:42:56 2016
InstallationDate: Installed on 2016-10-29 (0 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
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/controlC1:  austinclem1   1647 F pulseaudio
 /dev/snd/controlC0:  austinclem1   1647 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [X550LB, Realtek ALC3236, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/26/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X550LB.403
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X550LB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550LB.403:bd06/26/2014:svnASUSTeKCOMPUTERINC.:pnX550LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X550LB
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  ubuntu 10.16 internal speakers don't work, but headphones do

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

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

[Bug 1603608] [NEW] Scribus freezes with 100%+ CPU usage when editing styles

[Austin Dempewolff]

Public bug reported:

Occasionally when I create a new style I can't edit it right away.  This
usually is resolved by clicking on another style and then clicking back
on the new style.

This time however, clicking on another style caused scribus to freeze.
Using htop I saw that cpu usage was consistently at 100% or more (multi-
core machine).  As I write this, cpu usage has been constantly at this
rate for about 5 minutes and scribus is still frozen.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: scribus 1.4.6+dfsg-2ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jul 16 13:25:16 2016
InstallationDate: Installed on 2016-07-08 (7 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: scribus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "screenshot of problem"
   
https://bugs.launchpad.net/bugs/1603608/+attachment/4701854/+files/scribus-freeze.png

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

Title:
  Scribus freezes with 100%+ CPU usage when editing styles

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

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

[Bug 1600452] Re: "Failed to set variable: (2) Invalid Parameter" when enrolling MOK

[Austin Dempewolff]

filed an issue at shim's Github page here:
https://github.com/rhinstaller/shim/issues/55

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

Title:
  "Failed to set variable: (2) Invalid Parameter" when enrolling MOK

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

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

[Bug 1600452] [NEW] "Failed to set variable: (2) Invalid Parameter" when enrolling MOK

[Austin Dempewolff]

Public bug reported:

## Testing Environment:
Lenovo Thinkpad P50, fresh install of Ubuntu 16.04

$ apt-cache policy mokutil
mokutil:
  Installed: 0.3.0-0ubuntu3
  Candidate: 0.3.0-0ubuntu3
  Version table:
 *** 0.3.0-0ubuntu3 500
500 http://cn.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

$ apt-cache policy shim
shim:
  Installed: 0.8-0ubuntu2
  Candidate: 0.8-0ubuntu2
  Version table:
 *** 0.8-0ubuntu2 500
500 http://cn.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status


## Steps to reproduce:
(1) do not disable SecureBoot as suggested during the install.

(2) install virtualbox-5.0 from the virtualbox ppa (deb
http://download.virtualbox.org/virtualbox/debian xenial contrib)

(3) Follow instructions here to manually sign the vboxdrv kernel module
(https://askubuntu.com/questions/760671/could-not-load-vboxdrv-after-
upgrade-to-ubuntu-16-04-and-i-want-to-keep-secur/768310#768310)

$ openssl req -new -x509 -newkey rsa:2048 -keyout MOK.priv -outform DER
-out MOK.der -nodes -days 36500 -subj "/CN=Descriptive name/"

$ sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256
./MOK.priv ./MOK.der $(modinfo -n vboxdrv)

$ sudo mokutil --import MOK.der

(enter password)

(4) reboot, click "enroll mok", "continue", "yes", enter password,
(screenshots here: https://sourceware.org/systemtap/wiki/SecureBoot)

## Expected behavior:

new mok will be enrolled and I will be asked to reboot (several users
from the original askubuntu answer indicated that these exact steps
worked for them.

## Actual behaviour:

"Error: Failed to set variable: (2) Invalid Parameter"

## Troubleshooting steps taken:
- tried different passwords, and was able to eliminate that being the cause.
- found relevant lines of code producing the error: lines 919-931 in 
https://github.com/rhinstaller/shim/blob/master/MokManager.c

/# C code
efi_status = uefi_call_wrapper(RT->SetVariable, 5, db_name,
   &shim_lock_guid,
   EFI_VARIABLE_NON_VOLATILE
   | EFI_VARIABLE_BOOTSERVICE_ACCESS
   | EFI_VARIABLE_APPEND_WRITE,
   MokNewSize, MokNew);
}

if (efi_status != EFI_SUCCESS) {
console_error(L"Failed to set variable", efi_status);
return efi_status;
}
C Code #/
- unable to find where uefi_call_wrapper() is defined

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: mokutil 0.3.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jul  9 18:56:59 2016
InstallationDate: Installed on 2016-07-08 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: mokutil
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug mokutil shim xenial

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

Title:
  "Failed to set variable: (2) Invalid Parameter" when enrolling MOK

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

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

[Bug 1504445] Re: FocalTech touchpad stops working after suspend

[Austin Imperial]

This bug also affects my Asus X455LF-WX055T with FocalTech Touchpad with
Ubuntu 16.04 LTS installed.

I noticed a change in `xinput list` before and after suspending

Before I suspend, my `xinput list` contains `PS/2 FocalTech FocalTech
Touchpad`:

xinput list
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ Logitech K270 id=10   [slave  pointer  (2)]
⎜   ↳ Logitech M315/M235id=11   [slave  pointer  (2)]
⎜   ↳ PS/2 FocalTech FocalTech Touchpad id=15   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Video Bus id=7[slave  keyboard (3)]
↳ Video Bus id=8[slave  keyboard (3)]
↳ Sleep Button  id=9[slave  keyboard (3)]
↳ USB2.0 VGA UVC WebCam id=12   [slave  keyboard (3)]
↳ Asus WMI hotkeys  id=13   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=14   [slave  keyboard (3)]

When I wake it up after suspending it, my `xinput list` does not contain
`PS/2 FocalTech FocalTech Touchpad` but it was replaced(?) by `AT Raw
Set 2 keyboard id=15 [slave  keyboard (3)]` which was not present before
I suspend:

xinput list
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ Logitech K270 id=10   [slave  pointer  (2)]
⎜   ↳ Logitech M315/M235id=11   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Video Bus id=7[slave  keyboard (3)]
↳ Video Bus id=8[slave  keyboard (3)]
↳ Sleep Button  id=9[slave  keyboard (3)]
↳ USB2.0 VGA UVC WebCam id=12   [slave  keyboard (3)]
↳ Asus WMI hotkeys  id=13   [slave  keyboard (4)]
↳ AT Translated Set 2 keyboard  id=14   [slave  keyboard (3)]
↳ AT Raw Set 2 keyboard id=15   [slave  keyboard (3)]

I hope this helps...

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

Title:
   FocalTech touchpad stops working after suspend

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

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

[Bug 1587956]

[Austin English]

Hi shankao,

Thanks for the patch. You should submit it to wine-patc...@winehq.org,
as patches are not picked up from bugzilla.

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

Title:
  Wine should use dosbox's user config instead of creating a new one

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

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

[Bug 1572659] Re: bcmwl driver does not work with kernel 4.4.0-21 when secure boot enabled

[Matt Austin]

Same problem continues with 4.4.0-22.

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

Title:
  bcmwl driver does not work with kernel 4.4.0-21 when secure boot
  enabled

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

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

[Bug 1575712] Re: "Browser C: Drive" menu entry will do nothing if Wine has never been launched

[Austin English]

Hint: you can use 'wineboot' for that.

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

Title:
  "Browser C: Drive" menu entry will do nothing if Wine has never been
  launched

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

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

[Bug 1574681] Re: Merge or sync with Debian unstable

[Austin English]

That said, it should just be a matter of updating the version in the
package, not much has changed from a packaging perspective that I can
think of, with one notable exception: add an Suggests for torify (It can
download things via tor for censored networks).

Other than that, verify deps against the ones listed in the early
comments.

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

Title:
  Merge or sync with Debian unstable

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

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