[Touch-packages] [Bug 1990064] Re: unconfined profile denies userns_create for chromium based processes

2022-09-26 Thread John Johansen
So in short yes we are talking blocking this however its not as bad as
that makes it sound. There is the immediate technical side, and the
reason we must do that, and then there is longer term practical use
side.

So the technical short answer is yes that will be blocked at least
without additional confinement. Does it suck for people who want to
setup containers without using root privs. Yes. There is just no way
around this, we can't only block the bad uses, there is no way to know
what they are in advance. The best we can do is default deny and
selectively allow. And the ability to selectively allow can't be
something the attacker can do without privilege, or they have an easy
way to by-pass the restriction.

With that said. It should be fairly easy to make sure there is a generic
profile that will work with most lxc/lxd containers, and that can be
transparent to the user. LXD already offers support for apparmor and the
lxd devs are aware of the coming changes, so I expect the actual impact
on your use case will be minimal to none.

And there is always the option of adjust the sysctl to disable the
feature or your systems. We just can't make that a default for the
distro as it isn't secure.

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

Title:
  unconfined profile denies userns_create for chromium based processes

Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For Ubuntu 22.10, since the last kernel update, i can´t launch any
  chromium based browser, due to apparmor denying userns_create

  dmesg shows:
  apparmor="DENIED" operation="userns_create" class="namespace" info="User 
namespace creation restricted" error=-13 profile="unconfined" pid=21323 
comm="steamwebhelper" requested="userns_create" denied="userns_create"

  This happens for every process which uses a chromium engine, like
  google chrome itself or in this case steamwebhelper.

  Might be related to this change?:
  
https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/

  not sure if it got merged in this form though..

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


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


[Touch-packages] [Bug 1985887] Re: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s)

2022-09-26 Thread jeremyszu
It's interesting.
I would like to reproduce your scenario on my side.

Would you please share:
1. "ionice -c3 nice cp -a SRC DST" is mandatory? Does it reproducible through a 
normal "cp -a"?
2. What's the fail rate?
3. Would you please share the data type from "SRC"? a single large 29,613MB 
file? or a lot of small files? or 300MB * 100 files?

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

Title:
  systemd kills gnome-shell or gnome-terminal if gnome-terminal uses
  much memory (50% over 20s)

Status in OEM Priority Project:
  Invalid
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  [Steps to reproduce]
  0. Install Jammy image
  1. open gnome terminal
  2. issue stress_ng or Canonical certification tool checkbox as
  "checkbox-cli run com.canonical.certification::memory/memory_stress_ng"
  or
  "stress-ng --stack 0 --timeout 300"
  3. Terminal or Gnome-shell will be killed by systemd-oomd

  It's because all stressors are under same cgroup belongs to terminal.

  Both Wayland and Xorg can reproduce.

  over ssh and in multi-user.target work good.

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


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


[Touch-packages] [Bug 1477584] Re: package rsyslog 7.4.4-1ubuntu14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2022-09-26 Thread Launchpad Bug Tracker
[Expired for rsyslog (Ubuntu) because there has been no activity for 60
days.]

** Changed in: rsyslog (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package rsyslog 7.4.4-1ubuntu14 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in rsyslog package in Ubuntu:
  Expired

Bug description:
  Identified the issue after upgrade to 15.04 from 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: rsyslog 7.4.4-1ubuntu14
  ProcVersionSignature: Ubuntu 3.16.0-43.58-generic 3.16.7-ckt13
  Uname: Linux 3.16.0-43-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  Date: Thu Jul 23 14:34:45 2015
  DuplicateSignature: package:rsyslog:7.4.4-1ubuntu14:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-07-12 (11 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: rsyslog
  Title: package rsyslog 7.4.4-1ubuntu14 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1899638] Re: ubuntu-bug won't show GUI window in pure wayland-sessions

2022-09-26 Thread Launchpad Bug Tracker
[Expired for apport (Ubuntu) because there has been no activity for 60
days.]

** Changed in: apport (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  ubuntu-bug won't show GUI window in pure wayland-sessions

Status in apport package in Ubuntu:
  Expired

Bug description:
  In case only `WAYLAND_DISPLAY` env variable is set (but no `DISPLAY`
  as XWayland is disabled), ubuntu-bug won't show its window, even
  though GTK will use the Wayland backend.

  Test case, in an Ubuntu wayland session:
   - Run:
env -u DISPLAY ubuntu-bug -w apport

  
  You will get:

  *** Collecting problem information

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

  *** Send problem report to the developers?

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

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

  *** Uploading problem information

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

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

https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/.. ?

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

  
  Choices:
1: Launch a browser now
C: Cancel
  Please choose (1/C): 1
  marco@marco-virtual-machine:~$ Error: no DISPLAY environment variable 
specified
  ^C

  ---

  So, ubuntu-bug should both consider `DISPLAY` and `WAYLAND_DISPLAY` to
  be enough to use a graphical session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu49
  ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14
  Uname: Linux 5.8.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports: 640:1000:125:21823957:2020-10-13 15:15:42.354004383 
+0200:2020-10-13 15:15:43.354004383 
+0200:/var/crash/_usr_bin_gnome-shell.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 13 15:22:34 2020
  InstallationDate: Installed on 2020-10-13 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1990902] Re: Ubuntu-bug not submitting bug to website

2022-09-26 Thread Konstantin
It seems to work now so I guess you can close this bug report.

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

Title:
  Ubuntu-bug not submitting bug to website

Status in apport package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  $ ubuntu-bug apport
  Gtk-Message: 10:30:47.890: Failed to load module "xapp-gtk3-module"
  Gtk-Message: 10:30:47.920: Failed to load module "canberra-gtk-module"
  Gtk-Message: 10:30:47.921: Failed to load module "canberra-gtk-module"

  A web browser opens with bugs.launchpad.net saying it will reload the
  page in 10 seconds to see if the report is there. It keeps checking
  every 10 seconds but the report never shows up.

  The system runs is Ubuntu 22.04, recently upgraded from 20.04.

  I attached the output of ubuntu-bug apport --save=filename

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


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


Re: [Touch-packages] [Bug 1990902] Re: Ubuntu-bug not submitting bug to website

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

Title:
  Ubuntu-bug not submitting bug to website

Status in apport package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  $ ubuntu-bug apport
  Gtk-Message: 10:30:47.890: Failed to load module "xapp-gtk3-module"
  Gtk-Message: 10:30:47.920: Failed to load module "canberra-gtk-module"
  Gtk-Message: 10:30:47.921: Failed to load module "canberra-gtk-module"

  A web browser opens with bugs.launchpad.net saying it will reload the
  page in 10 seconds to see if the report is there. It keeps checking
  every 10 seconds but the report never shows up.

  The system runs is Ubuntu 22.04, recently upgraded from 20.04.

  I attached the output of ubuntu-bug apport --save=filename

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


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


[Touch-packages] [Bug 1990902] Re: Ubuntu-bug not submitting bug to website

2022-09-26 Thread Brian Murray
Can you still recreate this issue? I ask as there was some unexpected
downtime with Launchpad a few hours ago.

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

Title:
  Ubuntu-bug not submitting bug to website

Status in apport package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  $ ubuntu-bug apport
  Gtk-Message: 10:30:47.890: Failed to load module "xapp-gtk3-module"
  Gtk-Message: 10:30:47.920: Failed to load module "canberra-gtk-module"
  Gtk-Message: 10:30:47.921: Failed to load module "canberra-gtk-module"

  A web browser opens with bugs.launchpad.net saying it will reload the
  page in 10 seconds to see if the report is there. It keeps checking
  every 10 seconds but the report never shows up.

  The system runs is Ubuntu 22.04, recently upgraded from 20.04.

  I attached the output of ubuntu-bug apport --save=filename

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


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


[Touch-packages] [Bug 1990448] Re: Show Ubuntu Pro settings

2022-09-26 Thread Robert Ancell
This bug is a bit of a placeholder at the moment - we'll get this landed
into kinetic first and then update this to SRU the change back to the
older releases.

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

Title:
  Show Ubuntu Pro settings

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New
Status in software-properties source package in Jammy:
  Incomplete
Status in software-properties source package in Kinetic:
  New

Bug description:
  Expose more of the Ubuntu Pro (aka Ubuntu Advantage) services instead
  of just Livepatch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1990448/+subscriptions


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


[Touch-packages] [Bug 1990891] Re: after today's Kinetic updates, WiFi no longer working, so laptop basically useless

2022-09-26 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  after today's Kinetic updates, WiFi no longer working, so laptop
  basically useless

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  ThinkPad X1 Carbon 6th Gen
  WiFi was working fine.
  Installed today's batch of Kinetic updates.
  Laptop can no longer see any WiFi networks (had to dig out my old ThinkPad 
USB dongle and plug into my router to be able to submit this bug report).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: network-manager 1.40.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 17:09:25 2022
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-08-16 (1137 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.4.1 dev enp0s31f6 proto dhcp src 192.168.4.158 metric 
100 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.158 
metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (2 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

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


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


[Touch-packages] [Bug 1990891] Re: after today's Kinetic updates, WiFi no longer working, so laptop basically useless

2022-09-26 Thread darkshadow
Today's update installed iwd to replace wpa_supplicant but that is still 
installed and conflicting.
Run the following and restart

systemctl disable wpa_supplicant

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

Title:
  after today's Kinetic updates, WiFi no longer working, so laptop
  basically useless

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  ThinkPad X1 Carbon 6th Gen
  WiFi was working fine.
  Installed today's batch of Kinetic updates.
  Laptop can no longer see any WiFi networks (had to dig out my old ThinkPad 
USB dongle and plug into my router to be able to submit this bug report).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: network-manager 1.40.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 17:09:25 2022
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-08-16 (1137 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.4.1 dev enp0s31f6 proto dhcp src 192.168.4.158 metric 
100 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.158 
metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (2 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

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


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


[Touch-packages] [Bug 1643239] Re: Xorg crash on compiz login, with Intel 945

2022-09-26 Thread Henry Wertz
No problem!  I don't still have the D620 (or run 16.04 on anything...).

Side note, Intel GPU drivers sure have come along way since then!  Back
in the day, the Intel driver OpenGL was somewhat questionable, it worked
or it didn't with various games and 3D-using stuff see this very bug
report.  Now I can generally run anything even under wine and proton up
to the limits of the hardware.  I.e. you won't be running dx12 games on
a 10 year old Intel GPU but it'll do dx11...whether it'll do it fast
enough is another matter but better drivers can't do anything for the
GPU being too slow. Well apparently they can to some extent -- the
cherry on the cake, my friend's (almost as old as the D620) Sandy Bridge
system got about a 40-50% FPS improvement with some Mesa/Intel stack
changes in 2020 or so (and has kept that extra speed in 22.04) and I saw
30%+ speedups on a few other Intel GPU systems I had around that time.

(This was not a matter of Intel GPU drivers being slow before; on the
contrary, running some games on Intel GPU head-to-head between Windows
and Linux with wine or proton shows higher framerates in Linux virtually
across the board.)

Great job Xorg, Mesa, and Intel driver devs!
--Henry

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

Title:
  Xorg crash on compiz login, with Intel 945

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I went to install Ubuntu (via systemback) onto some Dell D620s, and found 
"Gnome Flashback (compiz)" crashes back to login prompt, while "Gnome Flashback 
(Metacity)" does not.  The attached logs reflect booting up, (attempting to) 
log in with Flashback (compiz) then logging in with Flashback (Metacity) to 
file a bug report.  This may be chipset-specific, as I have several other 
rather antiquated systems:
  Intel 865-based (Compaq DC5000): Works. (Using LLVMPipe -- this chip is 
missing a few OpenGL features compiz requires.)

  Intel 915-based (Dell Inspiron 2200): Works.
  Intel 945-based (Dell Latitude D620): Crashes to login prompt (this is the 
machine in this bug report.)
  Intel 965-based (Dell Latitude 755?): Works.
  Intel G35-based (slightly newer Dell Latitude 755): Works.

  I can rule out software differences; since I knew Compiz worked on a
  915, I assumed I'd screwed up my systemback LiveUSB somehow, and test-
  ran it on the D620, 2200, and one of the 755s, and it worked on the
  2200 and 755.

  Left up to me, I'd categorize this as severity "low", I'm just setting
  these to Flashback Metacity and then stability seems fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  BootLog: SB@: clean, 208182/2244608 files, 1302234/8973568 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sat Nov 19 10:12:40 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [1028:01c2]
 Subsystem: Dell Mobile 945GM/GMS/GME, 943/940GML Express Integrated 
Graphics Controller [1028:01c2]
  InstallationDate: Installed on 2016-04-29 (203 days ago)
  InstallationMedia:
   
  MachineType: Dell Inc. Latitude D620
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=702f73f8-ca72-4102-9c59-48f182329bfa ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0TD761
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd05/16/2008:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0TD761:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  

[Touch-packages] [Bug 1810241] Re: NULL dereference when decompressing specially crafted archives

2022-09-26 Thread Alex Murray
Thanks I have updated the status of this CVE in the Ubuntu CVE tracker.

** Changed in: tar (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  NULL dereference when decompressing specially crafted archives

Status in tar package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  Fuzzing tar with checksums disabled reveals a NULL pointer dereference
  when parsing certain archives that have malformed extended headers.
  This affects tar from (at least) Trusty, Bionic and Cosmic. I haven't
  tested Xenial's version.

  A test case with fixed checksums is attached. To avoid breaking
  anything that looks inside tar archives, I have converted it to text
  with xxd. To reproduce:

  $ xxd -r gnutar-crash.tar.txt gnutar-crash.tar
  $ tar Oxf gnutar-crash.tar 
  tar: Ignoring unknown extended header keyword 'GNU.sparse.minTr'
  tar: Malformed extended header: missing length
  Segmentation fault (core dumped)

  I have also attached a patch against the latest upstream git and
  against 1.30 (in Cosmic). This fixes the issue by detecting the null
  result before it is dereferenced.

  Regards,
  Daniel

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


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


[Touch-packages] [Bug 1990646] Re: Report a bug

2022-09-26 Thread Daniel van Vugt
Please explain what kind of problem you are experiencing.

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Report a bug

Status in Ubuntu:
  Incomplete

Bug description:
  Report a bug

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 23 12:17:07 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:8544]
  InstallationDate: Installed on 2022-09-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek 
Bluetooth 4.2 Adapter
   Bus 001 Device 003: ID 04ca:7092 Lite-On Technology Corp. HP TrueVision HD 
Camera
   Bus 001 Device 002: ID 3044:eac6 MIIIW MIIIW USB Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 14-df0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=f923f152-9747-4348-b5c2-f8d1f6320e44 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2021
  dmi.bios.release: 15.64
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.64
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8544
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 74.37
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 74.37
  dmi.modalias: 
dmi:bvnInsyde:bvrF.64:bd07/23/2021:br15.64:efr74.37:svnHP:pnHPLaptop14-df0xxx:pvrType1ProductConfigId:rvnHP:rn8544:rvrKBCVersion74.37:cvnHP:ct10:cvrChassisVersion:sku4XN68UA#ABA:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 14-df0xxx
  dmi.product.sku: 4XN68UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Touch-packages] [Bug 1990647] Re: Report a bug

2022-09-26 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1990646 ***
https://bugs.launchpad.net/bugs/1990646

Please explain what kind of problem you are experiencing.

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

** Changed in: ubuntu
   Status: New => Incomplete

** This bug has been marked a duplicate of bug 1990646
   Report a bug

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

Title:
  Report a bug

Status in Ubuntu:
  Incomplete

Bug description:
  Report a bug

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 23 12:17:07 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:8544]
  InstallationDate: Installed on 2022-09-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek 
Bluetooth 4.2 Adapter
   Bus 001 Device 003: ID 04ca:7092 Lite-On Technology Corp. HP TrueVision HD 
Camera
   Bus 001 Device 002: ID 3044:eac6 MIIIW MIIIW USB Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 14-df0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=f923f152-9747-4348-b5c2-f8d1f6320e44 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2021
  dmi.bios.release: 15.64
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.64
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8544
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 74.37
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 74.37
  dmi.modalias: 
dmi:bvnInsyde:bvrF.64:bd07/23/2021:br15.64:efr74.37:svnHP:pnHPLaptop14-df0xxx:pvrType1ProductConfigId:rvnHP:rn8544:rvrKBCVersion74.37:cvnHP:ct10:cvrChassisVersion:sku4XN68UA#ABA:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 14-df0xxx
  dmi.product.sku: 4XN68UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Touch-packages] [Bug 1367386] Re: Xorg crash with Trident driver after Xubuntu upgrade to Trusty

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Xorg crash with Trident driver after Xubuntu upgrade to Trusty

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After upgrading Xubuntu 12.04 LTS -> 14.04.1 LTS, system boots to
  black screen instead of desktop environment,  but single user command
  line works fine. Problem traced to xorg-server segfault crash in the
  Trident driver as below (summary of details already uploaded). The
  code attempts a call to an offset against eax which is a null pointer.

  After changing the acceleration architecture from XAA to EXA with 
  Option "AccelMethod""exa"
  in the Trident Device section of xorg.conf, the desktop environment loaded 
successfully.

  Maybe this option should now be the default for Trident?

  ProblemType: Crash
  Architecture: i386
  CrashCounter: 1
  Date: Tue Sep  9 13:26:36 2014
  DistroRelease: Ubuntu 14.04
  ExecutablePath: /usr/bin/Xorg
  ExecutableTimestamp: 1406679727
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nol
  isten tcp vt7 -novtswitch
  ProcCwd: /etc/X11
  ProcEnviron: 

  Disassembly:
   => 0xb6cb39d1:   call   *0x6c(%eax)
  0xb6cb39d4:   jmp0xb6cb3979
  0xb6cb39d6:   lea0x0(%esi),%esi
  0xb6cb39d9:   lea0x0(%edi,%eiz,1),%edi
  0xb6cb39e0:   push   %ebp
  0xb6cb39e1:   mov%eax,%ebp
  0xb6cb39e3:   push   %edi
  0xb6cb39e4:   xor%edi,%edi
  0xb6cb39e6:   push   %esi
  0xb6cb39e7:   mov$0x2,%esi
  0xb6cb39ec:   push   %ebx
  0xb6cb39ed:   sub$0x1c,%esp
  0xb6cb39f0:   mov0x18(%eax),%eax
  0xb6cb39f3:   call   0xb6caa4f0
  0xb6cb39f8:   add$0x14608,%ebx
  0xb6cb39fe:   sub$0x17,%eax
  Package: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  PackageArchitecture: i386
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Registers:
   eax0x0   0
   ecx0x0   0
   edx0xb96d7cb0-1184006992
   ebx0xb6cc8000-1228111872
   esp0xbf8873000xbf887300
   ebp0xb96d56880xb96d5688
   esi0xb96d3f98-1184022632
   edi0xb96d43f8-1184021512
   eip0xb6cb39d10xb6cb39d1
   eflags 0x213202  [ IF #12 #13 RF ID ]
   cs 0x73  115
   ss 0x7b  123
   ds 0x7b  123
   es 0x7b  123
   fs 0x0   0
   gs 0x33  51
  SegvAnalysis:
   Segfault happened at: 0xb6cb39d1:call   *0x6c(%eax)
   PC (0xb6cb39d1) ok
   source "*0x6c(%eax)" ok
   destination "(%esp)" (0xbf887300) ok
   SP (0xbf887300) ok
   Reason could not be automatically determined.
  SourcePackage: xorg-server
  ...
  Title: Xorg crashed with SIGSEGV in xf86VTSwitch()
  UpgradeStatus: Upgraded to trusty on 2014-09-07 (2 days ago)
  _MarkForUpload: True

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic i686
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Sep  9 18:09:01 2014
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-09-07 (2 days ago)

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


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


[Touch-packages] [Bug 1369535] Re: Xmodmap works abnormally on Ubuntu14.04,the key mappings will be reset after a few minutes

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Xmodmap works abnormally on Ubuntu14.04,the key mappings will be reset
  after a few minutes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to swap theses two keys: Caps_Lock and Control_L, my configuration 
file as follows:
  ~/.profile:
  if [ -f "$HOME/.xmodmaprc" ]; then
  xmodmap  ~/.xmodmaprc
  fi

  ~/.xmodmaprc : 
  remove Lock = Caps_Lock
  remove Control = Control_L
  keysym Control_L = Caps_Lock
  keysym Caps_Lock = Control_L
  add Lock = Caps_Lock
  add Control = Control_L

  The same configuration, On Ubuntu12.04, it worked  properly. After the
  upgrade, it works abnormally, after a few minutes, the key mappings
  will be rest, I have to run 'xmodmap ~/.xmodmaprc'  again and again.

  I also use a virtual machine, and  the key mapping  changes can't map
  to the guest system, but ubuntu12.04 don't have this problem.

  I am sure my configuration file “.xmodmaprc“  had not been “called” by
  other softs or system repeatedly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Sep 15 18:41:41 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:308c]
  InstallationDate: Installed on 2014-08-25 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: LENOVO ThinkCentre M4350t-N000
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=39fe2c92-19ee-477b-a71c-26c88f621769 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/17/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: F1KT65AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: NOK
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvrF1KT65AUS:bd03/17/2014:svnLENOVO:pnThinkCentreM4350t-N000:pvrLenovo:rvnLENOVO:rn:rvrNOK:cvnLENOVO:ct3:cvr:
  dmi.product.name: ThinkCentre M4350t-N000
  dmi.product.version: Lenovo
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Sep 15 08:09:58 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   24746 
   vendor LEN
  xserver.version: 2:1.15.1-0ubuntu2.1

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


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


[Touch-packages] [Bug 1652646] Re: Xorg freeze

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Playing video, e.g. in vlc or chrome causes the whole machine to hang
  after 5-10m of video playing.

  I also tried

  vlc --avcodec-hw none

  which I found in another similar bug but it still crashes.

  It happens with DVDs and also more modern codecs.

  Everything worked fine on 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic i686
  .tmp.unity_support_test.0:
   
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Dec 27 01:36:55 2016
  DistUpgraded: 2016-11-28 21:23:59,982 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1849:0f31]
  InstallationDate: Installed on 2012-10-07 (1541 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=fd3296ae-ab46-4a5b-8f5d-0fb54245618d ro quiet splash pci=use_crs 
viafb.modeset=0 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-11-28 (28 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.00
  dmi.board.name: Q1900DC-ITX
  dmi.board.vendor: ASRock
  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.:bvrP1.00:bd04/30/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnQ1900DC-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Dec 27 01:01:28 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

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


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

[Touch-packages] [Bug 1655709] Re: Spurious crash report dialog on every login

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

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

Title:
  Spurious crash report dialog on every login

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  For the last few years, on nearly all my computers, ubuntu has
  rewarded my logging in with a crash dialog.  Nothing's actually
  wrong; xorg probably trips over its shoelaces every time it
  shuts down, but so late in the process that it doesn't matter.

  Today I went through the crash upload procedure, but no
  web browser window opened, so either I did something wrong,
  or the bug is marked 'ignore uploads' somehow... hence
  this manual report.

  This bug has to have been reported before, but has probably
  been marked WONTFIX or something because it is benign.

  But it does matter, and it's not benign, because I, my wife, 
  and my son get those darn crash dialogs.

  It doesn't seem to matter what graphics card or driver is in use.

  Want the crash file left behind after the last upload?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  Uname: Linux 4.4.0-43-generic x86_64
  NonfreeKernelModules: nvidia_uvm 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.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.96  Sun Nov  8 22:33:28 
PST 2015
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Jan 11 08:56:26 2017
  DistUpgraded: 2016-04-26 16:26:11,919 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c]
  InstallationDate: Installed on 2014-07-18 (908 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC 
Webcam / CNF7129
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK Computer Inc. G60JX
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-43-generic 
root=UUID=28258489-6453-456a-9ecc-c41a02ad0631 ro rootflags=subvol=@ nomodeset 
quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (259 days ago)
  dmi.bios.date: 08/16/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G60JX
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr208:bd08/16/2010:svnASUSTeKComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
  dmi.product.name: G60JX
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
 

[Touch-packages] [Bug 1268151] Re: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep

2022-09-26 Thread Paul White
This issue has sat with a status of 'Incomplete' for over three years
now. There has been no response to comment #47 and the bug report only
references Ubuntu releases that are now EOL so it is being closed with a
status of 'Invalid'.

Please feel free to re-open this bug report if this is still an issue
when using a currently supported release of Ubuntu but please make sure
that you tell us in which release(s) you still experience this issue.

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

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

Title:
  [Dell M4800] DPMS support broken, fails to wake up the monitor after
  putting it to sleep

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  With my Dell Precision M4800, GK106GLM [Quadro K2100M], QHD+ display, and 
either nvidia-graphics-drivers-331 or nvidia-graphics-drivers-319 once the 
display shuts off, it will not wake up anymore, and the screen stays dark. A 
cycle of the following will leave the display dark:
  xset dpms force off; sleep 30; xset dpms force on

  WORKAROUND: A restart of the Xserver will bring back the display.

  WORKAROUND: Don't allow DPMS to switch off the display:
  xset dpms 0 0 0

  xset -q -d :0.0
  Keyboard Control:
    auto repeat:  onkey click percent:  0LED mask:  
    XKB indicators:
  00: Caps Lock:   off01: Num Lock:off02: Scroll Lock: off
  03: Compose: off04: Kana:off05: Sleep:   off
  06: Suspend: off07: Mute:off08: Misc:off
  09: Mail:off10: Charging:off11: Shift Lock:  off
  12: Group 2: off13: Mouse Keys:  off
    auto repeat delay:  500repeat rate:  20
    auto repeating keys:  00ffdbbf
  fadfffefffed
  9fff
  fff7
    bell percent:  50bell pitch:  400bell duration:  100
  Pointer Control:
    acceleration:  2/1threshold:  4
  Screen Saver:
    prefer blanking:  yesallow exposures:  yes
    timeout:  0cycle:  0
  Colors:
    default colormap:  0x20BlackPixel:  0x0WhitePixel:  0xff
  Font Path:
    
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins
  DPMS (Energy Star):
    Standby: 0Suspend: 0Off: 0
    DPMS is Enabled
    Monitor is On

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  Date: Sat Jan 11 12:06:30 2014
  InstallationDate: Installed on 2014-01-07 (3 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1318422] Re: Login + Virtualbox

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Login + Virtualbox

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Not sure if matter. You can delete this if is not related.
  Expected: login interface is blocking all access to the system
  Whats happen: Login give access to the virtualbox

  how to replicate:

  - Use virtualbox in steamless mode
  - Cursor focus on the VM
  - close the laptop to sleep
  - Open the latptop to wake it up
  - The keyboard on the login is locked and when you type you are actually 
typing on the VM, givin full acess to the VM inclusing the shared folders by 
the keyboard

  workaround
  - Using the mouse we can click in the option switch user on the top of login 
screen and with this even using the same user we can login as expected.

  thanks. As a mention I'm not sure if is related. I just trying to help
  in somehow.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun May 11 14:14:41 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 3.13.0-24-generic, x86_64: installed
   nvidia-331-updates, 331.38, 3.13.0-24-generic, x86_64: installed
   vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:181d]
   NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2014-05-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=\"Linux\" vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.29
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 181F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.24
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.29:bd10/03/2013:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr078F10010020571620100:rvnHewlett-Packard:rn181F:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 078F10010020571620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat May 10 22:48:05 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 643 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:

[Touch-packages] [Bug 1318465] Re: xorg will fail to start with error log /var/log/Xorg.0.log

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  xorg will fail to start with error log /var/log/Xorg.0.log

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  xorg will fail to start upon the first time reboot after switch to iGPU 
mode(Broadwell + AMD Topaz XT Radeon R7 M260)
  
  (EE) AIGLX: reverting to software rendering
  (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
failed (/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: undefined symbol: 
_glapi_tls_Dispatch)
  (EE) GLX: could not load software renderer
  (II) GLX: no usable GL providers found for screen 0
  ..

  Steps to reproduce:
  1. install amd fglrx driver and switch iGPU mode.
  2. reboot and issue will happen.
  3. after another reboot, issue will disappear and swrast_dri.so would load 
successfully, xorg could start successfully.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins:
   (gconftool-2:2984): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
   Did not receive a reply. Possible causes include: the remote application did 
not send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.
   Failed to get value for 
`/apps/compiz-1/general/screen0/options/active_plugins': No D-BUS daemon running
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon May 12 11:19:52 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1606] (rev 06) 
(prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:2112]
 Subsystem: Intel Corporation Device [8086:2112]
  InstallationDate: Installed on 2014-05-07 (4 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 9710:7830 MosChip Semiconductor MCS7830 10/100 Mbps 
Ethernet adapter
   Bus 001 Device 003: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
   Bus 001 Device 002: ID 045e:0750 Microsoft Corp. Wired Keyboard 600
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation Broadwell Client platform
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=b53ace64-f4ad-4558-ad20-6268412b06bd ro quiet splash vt.handoff=7 
nogpumanager
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2014
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: BDW-E1R1.86C.0069.R00.1403240209
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: WhiteTip Mountain 1
  dmi.board.vendor: Intel Corp.
  dmi.board.version: 3
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrBDW-E1R1.86C.0069.R00.1403240209:bd03/24/2014:svnIntelCorporation:pnBroadwellClientplatform:pvr0.1:rvnIntelCorp.:rnWhiteTipMountain1:rvr3:cvnIntelCorporation:ct9:cvr0.1:
  dmi.product.name: Broadwell Client platform
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  

[Touch-packages] [Bug 1574243] Re: Unable to adjust screen backlight on login screen on Macbook Pro (early 2015)

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Unable to adjust screen backlight on login screen on Macbook Pro
  (early 2015)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu

  Fresh install of 16.04.

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  Don't know. The guide to identify the package told me all login screen
  issues were "LightDM". ubuntu-bug told me that package was not
  installed.

  3) What you expected to happen

  To be able to adjust screen backlight brightness with the dedicated
  hardware buttons on the login screen, in order to be able log in. This
  works as expected whenever I'm logged in.

  4) What happened instead

  I had to log in from an almost black login screen with no backlight.

  I believe this bug was present in 15.10 as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Apr 24 13:58:00 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:162b] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Broadwell-U Integrated Graphics [106b:013f]
  InstallationDate: Installed on 2016-04-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=dd7fd213-44e3-45de-afe3-efd8c5825c1e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/11/2016
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B16.1602111810
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B16.1602111810:bd02/11/2016:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Apr 24 02:40:40 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   41002 
   vendor APP
  xserver.version: 2:1.18.3-1ubuntu2

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


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


[Touch-packages] [Bug 1622268] Re: Xorg freeze

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The mouse still moves, seems almost like just mouse clicks are missing.
  Happened most recently when switching desktops.

  syslog shows around the time of hang:

  Sep 10 21:08:19 abe systemd[1]: Started CUPS Scheduler.
  Sep 10 21:08:19 abe colord[1045]: (colord:1045): Cd-WARNING **: failed to get 
session [pid 12509]: No such device or address
  Sep 10 21:09:39 abe gnome-session[1968]: gnome-session-binary[1968]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  Sep 10 21:09:39 abe gnome-session[1968]: gnome-session-binary[1968]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  Sep 10 21:09:39 abe gnome-session-binary[1968]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  Sep 10 21:09:39 abe gnome-session-binary[1968]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  Sep 10 21:09:39 abe gnome-session[1968]: gnome-session-binary[1968]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  Sep 10 21:09:39 abe gnome-session-binary[1968]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  Sep 10 21:09:39 abe gnome-session-binary[1968]: Entering running state
  Sep 10 21:10:25 abe kernel: [127582.457059] [ cut here 
]
  Sep 10 21:10:25 abe kernel: [127582.457109] WARNING: CPU: 0 PID: 1095 at 
/build/linux-a2WvEb/linux-4.4.0/drivers/gpu/drm/drm_irq.c:1326 
drm_wait_one_vblank+0x1b5/0x1c0 [drm]()
  Sep 10 21:10:25 abe kernel: [127582.457111] vblank wait timed out on crtc 0
  Sep 10 21:10:25 abe kernel: [127582.457189] Modules linked in: btrfs xor 
raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c cpuid 
hid_generic usbhid hid iwldvm mac80211 iwlwifi cfg80211 ctr ccm intel_rapl drbg 
ansi_cprng x86_pkg_temp_thermal intel_powerclamp nls_iso8859_1 dm_crypt 
coretemp kvm_intel kvm arc4 irqbypass crct10dif_pclmul crc32_pclmul uvcvideo 
aesni_intel videobuf2_vmalloc videobuf2_memops aes_x86_64 lrw videobuf2_v4l2 
snd_hda_codec_hdmi gf128mul glue_helper snd_hda_codec_realtek videobuf2_core 
snd_hda_codec_generic v4l2_common ablk_helper snd_hda_intel joydev cryptd 
videodev snd_hda_codec input_leds snd_hda_core media serio_raw snd_hwdep 
thinkpad_acpi snd_pcm nvram snd_seq_midi snd_seq_midi_event lpc_ich shpchp 
snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore mei_me mei mac_hid 
parport_pc ppdev lp parport autofs4 bcache i915 i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect psmouse sysimgblt fb_sys_fops ahci libahci drm 
sdhci_pci e1000e sdhci
  ptp pps_core wmi fjes video [last unloaded: cfg80211]
  Sep 10 21:10:25 abe kernel: [127582.457217] CPU: 0 PID: 1095 Comm: Xorg Not 
tainted 4.4.0-36-generic #55-Ubuntu
  Sep 10 21:10:25 abe kernel: [127582.457219] Hardware name: LENOVO 
2349S7W/2349S7W, BIOS G1ETA8WW (2.68 ) 03/06/2015
  Sep 10 21:10:25 abe kernel: [127582.457225]  0286 
c8d4ae99 8803091b7838 813f13b3
  Sep 10 21:10:25 abe kernel: [127582.457228]  8803091b7880 
c00deb38 8803091b7870 810810f2
  Sep 10 21:10:25 abe kernel: [127582.457232]  880309c00800 
  002a9d59
  Sep 10 21:10:25 abe kernel: [127582.457233] Call Trace:
  Sep 10 21:10:25 abe kernel: [127582.457247]  [] 
dump_stack+0x63/0x90
  Sep 10 21:10:25 abe kernel: [127582.457256]  [] 
warn_slowpath_common+0x82/0xc0
  Sep 10 21:10:25 abe kernel: [127582.457260]  [] 
warn_slowpath_fmt+0x5c/0x80
  Sep 10 21:10:25 abe kernel: [127582.457269]  [] ? 
finish_wait+0x55/0x70
  Sep 10 21:10:25 abe kernel: [127582.457299]  [] 
drm_wait_one_vblank+0x1b5/0x1c0 [drm]
  Sep 10 21:10:25 abe kernel: [127582.457305]  [] ? 
wake_atomic_t_function+0x60/0x60
  Sep 10 21:10:25 abe kernel: [127582.457375]  [] 
intel_atomic_commit+0x43a/0x6f0 [i915]
  Sep 10 21:10:25 abe kernel: [127582.457414]  [] ? 
drm_atomic_add_affected_connectors+0x27/0xf0 [drm]
  Sep 10 21:10:25 abe kernel: [127582.457445]  [] 
drm_atomic_commit+0x37/0x60 [drm]
  Sep 10 21:10:25 abe 

[Touch-packages] [Bug 1680726] Re: Xorg.freeze

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Xorg.freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  We cannot login via lightdm if we wait too long after boot:

  Cursor in password input field stops blinking and if user inputs password 
anyways, then pc freezes. No switcht go VT or login via ssh possible. Only 
magic sysreq helps for rebooting.
  When user switches to a virtual terminal via ctrl-alt-F(1..6) and back into 
gui, then the cursor is blinking again and everything is normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Uname: Linux 4.4.0-63-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri Apr  7 08:57:59 2017
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1674943] Re: Intel Compatible Graphic Driver

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Intel Compatible Graphic Driver

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Intel Compatible Graphic Driver

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-112.159-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-112-generic x86_64
  NonfreeKernelModules: wl fglrx
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Mar 22 15:43:42 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:8101]
 Subsystem: Hewlett-Packard Company Device [103c:811c]
  InstallationDate: Installed on 2017-03-21 (1 days ago)
  InstallationMedia: Ubuntu-Linux-14.04-eCommittee 14.04 - Release amd64
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint 
Reader
   Bus 001 Device 003: ID 0a5c:640b Broadcom Corp. 
   Bus 001 Device 002: ID 05c8:0383 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProBook 450 G3
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-112-generic 
root=UUID=cdb25244-934f-4613-8f38-c3ab5ef041e0 ro quiet splash radeon.runpm=0 
vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N78 Ver. 01.15
  dmi.board.name: 8101
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 40.63
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN78Ver.01.15:bd11/07/2016:svnHP:pnHPProBook450G3:pvr:rvnHP:rn8101:rvrKBCVersion40.63:cvnHP:ct10:cvr:
  dmi.product.name: HP ProBook 450 G3
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 
11.0.4~git20151026+11.0.ec14e6f8-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
11.0.4~git20151026+11.0.ec14e6f8-0ubuntu0ricotz~trusty
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20151202.da9ad388-0ubuntu0sarvatt~trusty
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11+git20141030.3fb97d78-0ubuntu0sarvatt~trusty2
  xserver.bootTime: Wed Mar 22 15:32:55 2017
  xserver.configfile: /etc/X11/xorg.conf
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.7

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


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


[Touch-packages] [Bug 1692036] Re: Xorg crash after HWE update on Ubuntu 16.04 LTS

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Xorg crash after HWE update on Ubuntu 16.04 LTS

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Seems to be related to Bug #1509622

  I installed HWE kernel on Ubuntu 16.04 LTS laptop and now it crashes
  after every reboot and it fails to send crash report to Ubuntu.

  Hopefully this info will help you troubleshoot the issue.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri May 19 22:30:10 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-78-generic, x86_64: installed
   virtualbox, 5.0.40, 4.8.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer 3rd Gen Core processor Graphics Controller 
[1558:2702]
  MachineType: System76, Inc. Gazelle Professional
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic 
root=UUID=f6494394-e52a-4bfd-89e7-d5d1450baa8f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp7
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/16/2012:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp7:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp7:cvnNoEnclosure:ct9:cvrN/A:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp7
  dmi.sys.vendor: System76, Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri May 19 22:08:35 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
  xserver.video_driver: modeset

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


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


[Touch-packages] [Bug 1691496] Re: Display doesn't lower its brightness

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Display doesn't lower its brightness

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I have intel graphic driver installed but still i can't lower
  brightness,its always on 100 percent could not lower it. Also 2 keys
  have interchanged i don't know how. In windows both of them work
  properly, but here in ubuntu @ and " have interchanged their place
  from its normal place. @ does not comes with shift+2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed May 17 20:37:54 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:3975]
  InstallationDate: Installed on 2017-05-06 (11 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO HuronRiver Platform
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic 
root=UUID=886e3bbe-f8ee-4f08-ba68-daec4c289ba0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 44CN28WW
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Emerald Lake
  dmi.board.vendor: LENOVO
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnLENOVO:bvr44CN28WW:bd02/22/2011:svnLENOVO:pnHuronRiverPlatform:pvrLenovoB570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
  dmi.product.name: HuronRiver Platform
  dmi.product.version: Lenovo B570
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu May 18 01:57:35 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5543 
   vendor CMO
  xserver.version: 2:1.18.4-0ubuntu0.2

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


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


[Touch-packages] [Bug 1574648] Re: Xorg freeze

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Laptop is suspended with no external monitor.  Upon connecting a VGA
  external monitor and opening lid (resume) laptop resumes and
  everything is okay.  Attempting to connect bluetooth mouse causes
  immediate freeze of GUI and machine.  Cannot drop down into low run
  mode (CTL-ALT-F6).  Hard reset required.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 25 09:29:17 2016
  DistUpgraded: 2016-04-21 09:24:43,092 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:2425]
  InstallationDate: Installed on 2015-12-14 (132 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:068f Acer, Inc 
   Bus 001 Device 006: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Lemur
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=578caace-46fb-497c-9b81-f99b65518a27 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (4 days ago)
  dmi.bios.date: 11/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06RS76
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Lemur
  dmi.board.vendor: System76, Inc.
  dmi.board.version: lemu6
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06RS76:bd11/29/2015:svnSystem76,Inc.:pnLemur:pvrlemu6:rvnSystem76,Inc.:rnLemur:rvrlemu6:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.name: Lemur
  dmi.product.version: lemu6
  dmi.sys.vendor: System76, Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 25 09:07:39 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1094 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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


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


[Touch-packages] [Bug 1589110] Re: !6.04 + Nvidia drivers won't wotk with dual monitors

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


** Summary changed:

- !6.04 + Nvidia drivers won't wotk with dual monitors
+ 16.04 + Nvidia drivers won't work with dual monitors

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

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

Title:
  16.04 + Nvidia drivers won't work with dual monitors

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  been trying to get my dual monitors working on Ubuntu 16.04 LTS and a
  nVidia GeForce 960 using 361.42

  Server version 11.0
  Server Vendor version 1.18.3
  NV Control version 1.29

  Can only get one to display the desktop. Whichever is plugged into the
  DVI-I port, the other is not recognised whether it is in the DVI-D or
  HDMI (using converters to VGA)


  I can move the mouse to the blank screen where it shows as a large
  (but moveable) X

  Tried ubuntu forums for a solution but no improvement

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Jun  4 18:54:29 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-22-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Device [1b4c:1138]
  InstallationDate: Installed on 2016-05-22 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Supermicro X8ST3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=a29bc0eb-97b8-41fb-b334-a8755dd8ac15 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0b
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: X8ST3
  dmi.board.vendor: Supermicro
  dmi.board.version: 1234567890
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd04/23/2009:svnSupermicro:pnX8ST3:pvr1234567890:rvnSupermicro:rnX8ST3:rvr1234567890:cvnSupermicro:ct3:cvr1234567890:
  dmi.product.name: X8ST3
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Jun  4 18:49:12 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 

[Touch-packages] [Bug 1596288] Re: Xorg freeze

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a while using Ubuntu-Mate 16.04 on raspbery pi 3.

  The mouse and screen just freezes and are not responding!

  I have many issues using a PC computer with Ubuntu for the 64 -x86
  intel CPU as well.

  It just hangs and the mouse and the screen are not responding at all!

  This have been an issues since last 12.04 distro.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.13-v7+ armv7l
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: armhf
  Date: Sun Jun 26 19:25:55 2016
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1584386] Re: Main monitor doesn't wake up after system suspend

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Main monitor doesn't wake up after system suspend

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  If I lock my Unity session (Super+L) and power down my two monitors
  using external power switch, when after a few minutes I restore the
  power to monitors and wake up Ubuntu only my VGA connected LG display
  wakes up. My main monitor - a DisplayPort connected Dell U2410 wakes
  up only for a brief moment (it's power led goes blue from yellow) but
  before any picture would be displayed it goes back to sleep mode (led
  goes yellow again).

  All of this is true only for X session. If I switch to tty1
  (Ctrl+Alt+F1) the Dell wakes up correctly and shows tty1. Going back
  to X (Ctrl+Alt+F7) causes this monitor to go to power save mode again.

  The only means for me to get my main display back in X is to restart
  the computer, as logging in and out of X doesn't help. I have also
  tried running Displays configuration tool while in X, but what it only
  does is that once I click "Detect Displays" button Dell's power led
  goes blue for a brief moment and then immediately back to yellow
  (power save mode).

  I haven't encountered such behavior with Ubuntu 14.04, nor have I
  experienced right after migrating to 16.04. I believe this regression
  showed up with some update within the last two weeks.

  Both monitors are hooked up to AMD Radeon 5850 graphics card.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems
   Ubuntu_Root: clean, 690241/3670016 files, 6292028/14652416 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat May 21 21:22:43 2016
  DistUpgraded: 2016-04-23 22:19:53,020 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cypress PRO [Radeon HD 5850] 
[1002:6899] (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Cypress PRO [Radeon HD 
5850] [1002:0b00]
  InstallationDate: Installed on 2015-08-22 (272 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7583
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=a709e3c2-0c9b-4102-8135-3a38cc17bd0b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (27 days ago)
  dmi.bios.date: 08/18/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P55-GD65 (MS-7583)
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.11:bd08/18/2011:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7583:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnP55-GD65(MS-7583):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7583
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: 

[Touch-packages] [Bug 1609900] Re: Unplugging and re-plugging keyboard forgets xmodmap

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Unplugging and re-plugging keyboard forgets xmodmap

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  [I'm not sure against which package I can report this, so I've
  preliminary done it against `qemu`]

  Since I have a non-standard keyboard (a Kinesis, without Super key), I 
remapped a key on my system (XUbuntu 16.04).
  This is accomplished via:

  ~$ cat ~/.Xmodmap
  keycode 108 = Super_L

  This works fine, but after any qemu execution, with passthrough of my
  USB keyboard, the mapping is lost - more precisely, the system it
  starts behaving like the key is not mapped.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu 1:2.5+dfsg-5ubuntu10.2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Aug  4 19:11:24 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-11 (24 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0  1261 2  0.0 [kvm-irqfd-clean]
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=7f35da3f-4f3a-40e1-8af0-3f02cfbf9884 ro
  SourcePackage: qemu
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XN-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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


[Touch-packages] [Bug 1636473] Re: random cursor jumps when clicking on dell xps 13

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

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

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

Title:
  random cursor jumps when clicking on dell xps 13

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  1 out of 20-40 clicks on the touch pad results in a pointer jump and a
  "random" click.

  Hard to reproduce, but mostly happens when I use my middle finger to
  move the cursor and click with index finger. Sometimes the double
  touch of middle/index finger is interpreted as mouse move, the jump is
  more or less the same distance as if i had moved the index to the
  middle finger position.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Oct 25 22:04:10 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:0704]
  InstallationDate: Installed on 2016-09-08 (46 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=fe8099eb-a258-42d6-8f67-69496f1e0fcf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.4
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Oct 22 20:20:44 2016
  xserver.configfile: default
  xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193 
   vendor SHP
  xserver.version: 2:1.18.4-0ubuntu0.1

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


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


[Touch-packages] [Bug 1643239] Re: Xorg crash on compiz login, with Intel 945

2022-09-26 Thread Paul White
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
Further to comment #3 I'm closing this  at the request of the reporter.
Henry, I'm sorry that it took us nearly six years to see your comment :o)

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

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

Title:
  Xorg crash on compiz login, with Intel 945

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I went to install Ubuntu (via systemback) onto some Dell D620s, and found 
"Gnome Flashback (compiz)" crashes back to login prompt, while "Gnome Flashback 
(Metacity)" does not.  The attached logs reflect booting up, (attempting to) 
log in with Flashback (compiz) then logging in with Flashback (Metacity) to 
file a bug report.  This may be chipset-specific, as I have several other 
rather antiquated systems:
  Intel 865-based (Compaq DC5000): Works. (Using LLVMPipe -- this chip is 
missing a few OpenGL features compiz requires.)

  Intel 915-based (Dell Inspiron 2200): Works.
  Intel 945-based (Dell Latitude D620): Crashes to login prompt (this is the 
machine in this bug report.)
  Intel 965-based (Dell Latitude 755?): Works.
  Intel G35-based (slightly newer Dell Latitude 755): Works.

  I can rule out software differences; since I knew Compiz worked on a
  915, I assumed I'd screwed up my systemback LiveUSB somehow, and test-
  ran it on the D620, 2200, and one of the 755s, and it worked on the
  2200 and 755.

  Left up to me, I'd categorize this as severity "low", I'm just setting
  these to Flashback Metacity and then stability seems fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  BootLog: SB@: clean, 208182/2244608 files, 1302234/8973568 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sat Nov 19 10:12:40 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [1028:01c2]
 Subsystem: Dell Mobile 945GM/GMS/GME, 943/940GML Express Integrated 
Graphics Controller [1028:01c2]
  InstallationDate: Installed on 2016-04-29 (203 days ago)
  InstallationMedia:
   
  MachineType: Dell Inc. Latitude D620
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=702f73f8-ca72-4102-9c59-48f182329bfa ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0TD761
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd05/16/2008:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0TD761:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Nov 19 10:12:01 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   0 
   vendor LPL
  xserver.version: 2:1.18.4-0ubuntu0.2

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


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


[Touch-packages] [Bug 1645993] Re: Highly loaded desktop loses keyboard autorepeat setting

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Highly loaded desktop loses keyboard autorepeat setting

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hi. I have a custom keyboard autorepeat setting configured with xset:

  $ xset q | grep 'auto repeat delay'
auto repeat delay:  150repeat rate:  50

  It works fine. My LUbuntu desktop is used for developing. It heavily
  utilizes system resources - CPU and memory. After some time the
  autorepeat setting is lost and reverted back to it default value:

  $ xset q | grep 'auto repeat delay'
auto repeat delay:  660repeat rate:  25

  If the system doesn't utilize much system resources, the autorepeat
  setting is preserved.

  Observed with KUbuntu 16.04 too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Wed Nov 30 09:08:19 2016
  InstallationDate: Installed on 2016-10-13 (47 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160720)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1651150] Re: Mouse clicks not registered in first monitor

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Mouse clicks not registered in first monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  This is a laptop, I added a monitor via VGA and now the desktop area
  from the first monitor does not register clicks nor mouse movement (No
  hover effects at all). However it does detect clicks in the menu bar
  and tray area, and in the app launcher. Keyboard commands are
  responsive. Xev didn't register movement when window was used in the
  laptop's own monitor either.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: symap_custom_dkms_x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Dec 19 08:32:19 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: openclient-savap-config, 1.0.14, 4.4.0-53-generic, x86_64: 
installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06e0]
  InstallationDate: Installed on 2016-11-17 (32 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  LightdmLog: [+349.39s] DEBUG: User /org/freedesktop/Accounts/User65534 added
  MachineType: Dell Inc. Precision 3510
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-53-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.3
  dmi.board.name: 0XC72F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.3:bd06/15/2016:svnDellInc.:pnPrecision3510:pvr:rvnDellInc.:rn0XC72F:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 3510
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Dec 19 08:21:02 2016
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1199 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.2

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


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


[Touch-packages] [Bug 1654744] Re: Upon booting was prompted with a message about reporting a graphics issues bug

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Upon booting was prompted with a message about reporting a graphics
  issues bug

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm new, and too tired to learn how to look into the bug.  I hope the
  info the message said would automatically be sent with this is
  helpful.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Jan  7 09:17:25 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [1028:01c2]
 Subsystem: Dell Mobile 945GM/GMS/GME, 943/940GML Express Integrated 
Graphics Controller [1028:01c2]
  InstallationDate: Installed on 2016-09-19 (109 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude D620
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-53-generic 
root=/dev/mapper/ubuntu--vg-root ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0FT292
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd12/18/2006:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0FT292:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Jan  7 03:46:53 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16980 
   vendor SEC
  xserver.version: 2:1.18.4-0ubuntu0.2

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


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


[Touch-packages] [Bug 1659089] Re: Ubuntu acting up when working with Virtualbox and other programs

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) giving us full details of the issues that you are seeing
otherwise this bug report can be left to expire in approximately 60 days
time.


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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Ubuntu acting up when working with Virtualbox and other programs

Status in Ubuntu:
  Incomplete

Bug description:
  Bug report has been added.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  NonfreeKernelModules: nvidia_uvm 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.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.101  Thu Dec  1 15:52:31 
PST 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Jan 24 11:27:19 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-59-generic, x86_64: installed
   nvidia-340, 340.101, 4.4.0-59-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-59-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Apple Inc. G84M [GeForce 8600M GT] [106b:00a3]
  InstallationDate: Installed on 2017-01-19 (5 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Apple Inc. MacBookPro4,1
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=a7dc4c24-c475-4254-a40b-2452715de03b ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/27/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP41.88Z.00C1.B03.0802271651
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F42C89C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F42C89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP41.88Z.00C1.B03.0802271651:bd02/27/08:svnAppleInc.:pnMacBookPro4,1:pvr1.0:rvnAppleInc.:rnMac-F42C89C8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F42C89C8:
  dmi.product.name: MacBookPro4,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Jan 24 11:14:50 2017
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go 

[Touch-packages] [Bug 1660328] Re: amd radeon

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s), giving us full details of the problem that you are seeing
otherwise this bug report can be left to expire in approximately 60 days
time.


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

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

Title:
  amd radeon

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  amd radeon fglrx modul

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-107.154-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-107-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jan 30 13:52:07 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx-updates-core, 15.201, 3.13.0-107-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV730 XT [Radeon HD 4670] [1002:9490] 
(prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e100]
  InstallationDate: Installed on 2014-10-05 (847 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-107-generic 
root=UUID=8adf77a0-2e26-4a04-b145-251f1a274ce8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 5: Error: GLX is not available on the system
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: 960GM-GS3 FX
  dmi.board.vendor: ASRock
  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.:bvrP1.10:bd09/22/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM-GS3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.7
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Jan 30 13:46:41 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.7

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


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


[Touch-packages] [Bug 1676002] Re: Xorg freeze

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The system freezes randomly since I installed Ubuntu 16.04. I think
  there's a problem with nvidia drivers. The graphic card is Nvidia
  GeForce 7050/NForce 610i. I use the nouveau driver. Before this I used
  Ubuntu 12.04 without problems for almost 5 years with 173 Nvidia
  driver (which it's recommended), but it's not avaliable. Now when I
  try to use privete drivers the only avaliable driver is Nvidia 304.xx,
  but it causes a black screen at start the PC. I can use the terminal
  to uninstall the nvidia drivers and login, but then the system freezes
  very frecuently.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-41-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Mar 25 08:11:57 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation C73 [GeForce 7050 / nForce 610i] [10de:07e3] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. C73 [GeForce 7050 / nForce 610i] 
[1043:82ae]
  InstallationDate: Installed on 2017-03-18 (6 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic 
root=UUID=5edf19ce-c17b-4661-bfff-4b32af86a9e4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS P5N73-AM ACPI BIOS Revision 0201
  dmi.board.name: P5N73-AM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 2.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N73-AMACPIBIOSRevision0201:bd06/11/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N73-AM:rvr2.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Mar 25 08:05:47 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button 

[Touch-packages] [Bug 1675653] Re: screen freezing

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  screen freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  after suspend screen freezing and only mouse moving. can not open none of the 
consoles
   tty,

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems
   SB@: recovering journal
   SB@: clean, 274819/3203072 files, 2081321/1280 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Mar 24 09:55:07 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Broadwell-U Integrated Graphics [1028:066e]
  MachineType: Dell Inc. Inspiron 7548
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-67-generic root=/dev/sda1 
ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0AM6N0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd03/17/2016:svnDellInc.:pnInspiron7548:pvrA07:rvnDellInc.:rn0AM6N0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 7548
  dmi.product.version: A07
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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


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


[Touch-packages] [Bug 1694379] Re: Crash with multi-screen

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Crash with multi-screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  XORG crash if I plug a second screen with the DVI input on my laptop.

  The bug appear after a recent update of Ubuntu 16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  364.19  Tue Apr 19 14:44:55 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May 30 08:25:47 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:221d]
   NVIDIA Corporation GK208M [GeForce GT 730M] [10de:1290] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK208M [GeForce GT 730M] [17aa:221d]
  InstallationDate: Installed on 2016-06-20 (343 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20AWS5H500
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=3598049e-4f06-494b-82cc-d5a007b0e461 ro quiet splash "acpi=Windows 
2013" vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/19/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET82WW (2.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AWS5H500
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET82WW(2.36):bd01/19/2016:svnLENOVO:pn20AWS5H500:pvrThinkPadT440p:rvnLENOVO:rn20AWS5H500:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AWS5H500
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue May 30 08:18:29 2017
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2

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


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


[Touch-packages] [Bug 1709712] Re: Xorg freeze

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Xorg freeze

Status in Ubuntu:
  Incomplete

Bug description:
  Computer freezes without apparent cause.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Aug  9 17:35:26 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last few days
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:80d1]
  InstallationDate: Installed on 2017-03-18 (144 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: HP HP Pavilion x360 Convertible
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic.efi.signed 
root=UUID=8352e01f-2580-4315-98ff-f584b17874d1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D1
  dmi.board.vendor: HP
  dmi.board.version: 84.33
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd06/13/2017:svnHP:pnHPPavilionx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D1:rvr84.33:cvnHP:ct31:cvrChassisVersion:
  dmi.product.name: HP Pavilion x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Aug  9 17:34:56 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: modeset

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


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


[Touch-packages] [Bug 1703561] Re: Xorg crash on startup

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Xorg crash on startup

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04.2 LTS
  Xorg 1:7.7+13ubuntu3

  Occasionally upon initial login system reports that an error has
  occurred. It does not seem to happen every time on startup, but occurs
  quite often. Afterward it does not seem to affect operation and
  stability.

  Please let me know if I can provide any other useful information for
  debugging (I'm a linux newbie so may require some guidance for this).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Jul 11 11:52:10 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
     Subsystem: Dell Skylake Integrated Graphics [1028:06de]
  InstallationDate: Installed on 2017-05-18 (53 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Dell Inc. Latitude E5470
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic.efi.signed 
root=UUID=ac09168b-59a5-4108-8e61-e713ae6d45ab ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.4
  dmi.board.name: 0MT53G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.4:bd05/12/2017:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn0MT53G:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5470
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


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


[Touch-packages] [Bug 1702684] Re: Xorg freeze

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Display freezes very frequently and have to hard start every time. I
  have checked if the graphics driver exists and it is fine. Its a new
  laptop with NVIDIA geforce GTX 1050 card. Please help fix this
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jul  6 14:42:33 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:5912] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:651a]
 Subsystem: CLEVO/KAPOK Computer Device [1558:651a]
  InstallationDate: Installed on 2017-06-28 (8 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Notebook W65KJ1_KK1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic 
root=UUID=7b6d5d19-08f6-4b44-9f83-8fdeabaebba5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65KJ1_KK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd03/10/2017:svnNotebook:pnW65KJ1_KK1:pvrW65KJ1_KK1:rvnNotebook:rnW65KJ1_KK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: W65KJ1_KK1
  dmi.product.version: W65KJ1_KK1
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Jul  6 14:14:48 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
  xserver.video_driver: modeset

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


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


[Touch-packages] [Bug 1706702] Re: Can't login after lock screen (black screen)

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Can't login after lock screen (black screen)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After locking screen and as a result the monitor going into sleep
  mode, I can't get the login screen anymore, the monitor stays in sleep
  mode forever.

  In previous Ubuntu versions after pressing any key or the mouse, the
  login screen showed up, but not anymore. I have to do a
  Ctrl+Alt+Backspace

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-27-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog: /dev/sdc5: clean, 307593/23363584 files, 5157711/93435648 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Jul 26 11:47:17 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK107GL [Quadro K2000] [10de:0ffe] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GK107GL [Quadro K2000] [103c:094c]
  InstallationDate: Installed on 2017-07-17 (8 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Hewlett-Packard HP Z620 Workstation
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic 
root=UUID=5db25c2a-88a7-429c-9a7d-445e7694f7d6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J61 v03.18
  dmi.board.asset.tag: 2UA33318D4
  dmi.board.name: 158A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 0.00
  dmi.chassis.asset.tag: 2UA33318D4
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ61v03.18:bd07/01/2013:svnHewlett-Packard:pnHPZ620Workstation:pvr:rvnHewlett-Packard:rn158A:rvr0.00:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Z620 Workstation
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Jul 26 11:43:34 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB CAT5 KEYBOARD, id 8
   inputUSB CAT5 MOUSE, id 9
   inputHP WMI hotkeys   KEYBOARD, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.2
  xserver.video_driver: nouveau

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


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


[Touch-packages] [Bug 1705398] Re: Xorg freeze

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Freeze has happened in two situations - first was when opening Totem,
  the second occurred when opening the Plex Media Manager (which opens
  in Chrome browser).

  WORKAROUND: Use the nvidia-375 driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,imgpng,resize,compiztoolbox,gnomecompat,regex,move,animation,vpswitch,mousepoll,snap,wall,grid,place,unitymtgrabhandles,expo,workarounds,session,fade,scale,ezoom,unityshell]
  Date: Thu Jul 20 17:51:44 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-38-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-79-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-83-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-79-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-83-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last few days
  GraphicsCard:
   NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. GF116 [GeForce GTX 550 Ti] [1043:83be]
  InstallationDate: Installed on 2016-10-02 (291 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=c1765f93-69c1-4371-9aed-52f9168c068d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FE
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-S2PV
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFE:bd06/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S2PV:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Jul 20 17:32:21 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: nouveau

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


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

[Touch-packages] [Bug 1711837] Re: Xorg freeze

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  16.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Aug 19 15:41:09 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: I don't know
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:191d]
  InstallationDate: Installed on 2016-02-11 (554 days ago)
  InstallationMedia: Ubuntu  "Xenial" - Build amd64 LIVE Binary 20160421-22:07
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 13d3:3408 IMC Networks 
   Bus 001 Device 003: ID 0bda:57bc Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 
Optical USB Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X751SA
  ProcEnviron:
   LANGUAGE=hu
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic 
root=UUID=1e0aa7c7-81be-4834-941a-d90cc5664ac6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X751SA.403
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X751SA
  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.:bvrX751SA.403:bd03/01/2016:svnASUSTeKCOMPUTERINC.:pnX751SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX751SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X751SA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Aug 19 15:37:16 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5940 
   vendor CMN
  xserver.version: 2:1.18.4-0ubuntu0.3

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


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


[Touch-packages] [Bug 1727733] Re: Screen acts strangely when clicking Dash icon

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Screen acts strangely when clicking Dash icon

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm new to Ubuntu One so I don't really know what info to submit, but
  my problem is as follows:

  Everything seems to work just fine in 16.04 - except for one thing:
  Dash. When I click the icon (or press the superkey) the screen goes
  sort of crazy: coloured strips and odd stuff appear. Sometimes the
  computer freezes and I have to start all over again; sometimes it is
  possible to save the day by (fairly quickly)clicking the Dash icon
  once again - and sometimes things work out by themselves. I have
  searched for a solution on the internet, but in vain. Maybe it has
  something to do with memory mapping?

  Computer info: AMD Athlon 64 Processor 3500+ with 3 GB RAM (I think it
  was originally 1 GB but I extended it some years ago) in HP Pavilion
  3510no desktop (old stuff; probably at least 10 years old). Graphics
  Gallium 0.4 on NV 46 (according to Settings - what do I know ...)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 25 14:52:42 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. G72 [GeForce 7300 LE] [1043:0346]
  InstallationDate: Installed on 2017-06-27 (120 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 002: ID 0951:1666 Kingston Technology DataTraveler G4
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: HP Pavilion 061 RA975AA-ABS t3510.se
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, no user)
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic 
root=UUID=099bfe13-94a1-482f-b3aa-13341d87945d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.11
  dmi.board.name: Nash
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.11:bd06/16/2006:svnHPPavilion061:pnRA975AA-ABSt3510.se:pvr0nx0211RE101NASHM00:rvnMSI:rnNash:rvr1.0:cvn:ct3:cvr:
  dmi.product.name: RA975AA-ABS t3510.se
  dmi.product.version: 0nx0211RE101NASHM00
  dmi.sys.vendor: HP Pavilion 061
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Oct 25 14:43:13 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse 

[Touch-packages] [Bug 1716078] Re: problem regarding detecting intel graphic card and changing my resolution

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  problem regarding detecting intel graphic card and changing my
  resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 14.04 cannot detect my graphic card, which is intel HD graphics
  630, and I cannot change my resolution.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-129.178-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-129-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Sep  8 18:11:33 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:5912] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:108e]
  InstallationDate: Installed on 2017-09-09 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Acer Aspire TC-780
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-129-generic.efi.signed 
root=UUID=957edbfd-0d99-4b8f-8c66-a16283cc26ed ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R02-A2
  dmi.board.name: Aspire TC-780(KBL)
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR02-A2:bd02/21/2017:svnAcer:pnAspireTC-780:pvr:rvnAcer:rnAspireTC-780(KBL):rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Aspire TC-780
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Sep  8 18:03:21 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2

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


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


[Touch-packages] [Bug 1730621] Re: My graphics driver is not working properly

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  My graphics driver is not working properly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The size of icons is not getting reduced. Please help me out. More
  over my resolution is also not changeing apart from 1024x768 (4:3)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Nov  7 14:59:33 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200e [Pilot] ServerEngines (SEP1) 
[102b:0522] (rev 05) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation MGA G200e [Pilot] ServerEngines (SEP1) 
[8086:0103]
  InstallationDate: Installed on 2017-11-06 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Intel Corporation S2600CP
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic 
root=/dev/mapper/hostname--vg-root ro
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SE5C600.86B.01.06.0001.090720121056
  dmi.board.asset.tag: 
  dmi.board.name: S2600CP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G50768-509
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrSE5C600.86B.01.06.0001.090720121056:bd09/07/2012:svnIntelCorporation:pnS2600CP:pvr:rvnIntelCorporation:rnS2600CP:rvrG50768-509:cvn..:ct17:cvr..:
  dmi.product.name: S2600CP
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Nov  7 13:56:58 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.7

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


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


[Touch-packages] [Bug 1732513] Re: Unable to access windows on second display

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Unable to access windows on second display

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 16.04.3 on a Macbook Pro using a dock with two
  monitors. While docked, the internal display is not operational,
  instead using only the two monitors. I have repeatedly encountered
  issues where application windows that are active on the left display
  are not selectable with the mouse. I can still use the Unity launcher
  bar and the top menu bar but not any open windows. The windows on the
  right monitor still work properly. If I drag applications from the
  right display to the left display, that application also becomes
  unclickable with the mouse. Windows that span across both display and
  clickable on the right display, but not the left display. This
  behavior happens occasionally (about once a week) with any running
  applications, and I have not been able to cause the behavior
  repeatably. I can still use the applications by using the Unity
  launcher to switch to the application, then using keyboard commands. I
  would note that usually when this happens, I have a Windows virtual
  machine running in Virtualbox. I'm not sure if that is related or just
  a coincidence. At times, I can get the OS operating correctly again by
  closing all open application windows. Other times, it requires a
  complete reboot to restore operation to the left side monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  .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.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.66  Mon May  1 15:29:16 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Nov 15 11:39:50 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller 
[106b:00f7]
   NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2]
  InstallationDate: Installed on 2016-05-04 (559 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Apple Inc. MacBookPro10,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=398390d3-f6be-4e80-8a20-f036f9ec4d26 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP101.88Z.00EE.B09.1506081405
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C3EC7CD22292981F
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-C3EC7CD22292981F
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B09.1506081405:bd06/08/2015:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
  dmi.product.name: MacBookPro10,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: 

[Touch-packages] [Bug 1736159] Re: Xorg freeze

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Xorg freeze

Status in Ubuntu:
  Incomplete

Bug description:
  System doesn't boot if 2 MSI Radeons RX 570 Gaming X are attached.
  (System working fine if only one is attached). I Have MSI Gaming Plus
  B350 mobo and overclocked Ryzen 7 1700. PSU is strong enough to handle
  2 GPU's. Windows boots properly on this machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Mon Dec  4 15:28:12 2017
  InstallationDate: Installed on 2017-11-23 (11 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1743211] Re: ubuntu crashed on VM started

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

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

Title:
  ubuntu crashed on VM  started

Status in Ubuntu:
  Incomplete

Bug description:
  ubuntu crashed on VM (virtualbox) started

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:03:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Jan 14 14:01:04 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-42-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-26-generic, x86_64: installed
   nvidia-384, 384.111, 4.10.0-42-generic, x86_64: installed
   nvidia-384, 384.111, 4.13.0-26-generic, x86_64: installed
   virtualbox, 5.0.40, 4.13.0-26-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:3824]
 Subsystem: Lenovo Device [17aa:3824]
  InstallationDate: Installed on 2017-11-12 (63 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 80SM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic 
root=UUID=fd53ae53-c812-4c0c-8109-89e7c0c7310d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN37WW:bd10/03/2016:svnLENOVO:pn80SM:pvrLenovoideapad310-15ISK:rvnLENOVO:rnToronto5A2:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad310-15ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80SM
  dmi.product.version: Lenovo ideapad 310-15ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Jan 14 13:47:58 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.4

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


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


[Touch-packages] [Bug 1743677] Re: Xorg freeze

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

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

Title:
  Xorg freeze

Status in Ubuntu:
  Incomplete

Bug description:
  When I try to open applications some open after multiple times of
  trying or do not at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Jan 16 20:32:08 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  InstallationDate: Installed on 2018-01-14 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 2537ZSL
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET74WW (1.34 )
  dmi.board.name: 2537ZSL
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET74WW(1.34):bd10/25/2010:svnLENOVO:pn2537ZSL:pvrThinkPadT410:rvnLENOVO:rn2537ZSL:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2537ZSL
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Jan 16 20:18:13 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: modeset

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


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


[Touch-packages] [Bug 1746332] Re: Error in login after installing AMD driver

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

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

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  Error in login after installing AMD driver

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After installing the AMD Radeon R7 M445 video card driver, login no
  longer works. The password is typed, however, it looks like it will
  load Unity into Ubuntu 16.04.3 LTS and it returns the login screen
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Jan 30 16:50:56 2018
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   amdgpu-pro, 16.30.3-320002e, 4.4.0-112-generic, x86_64: installed
   amdgpu-pro, 16.30.3-320002e, 4.4.0-23-generic, x86_64: installed
   amdgpu-pro, 16.30.3-320002e, 4.4.0-36-generic, x86_64: built
   oem-audio-hda-daily, 0.201708030416~ubuntu16.04.1, 4.4.0-112-generic, 
x86_64: installed
   oem-audio-hda-daily, 0.201708030416~ubuntu16.04.1, 4.4.0-23-generic, x86_64: 
installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0767]
 Subsystem: Device [03ea:1af4]
  InstallationDate: Installed on 2018-01-30 (0 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Inspiron 5567
  ProcEnviron:
   LANGUAGE=pt_BR:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=ad173464-db7e-409e-847d-8329d5d6030b ro acpi_rev_override 
locale=pt_BR quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.9
  dmi.board.name: 0P02J3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.9:bd12/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn0P02J3:rvrA03:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 5567
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Jan 30 15:41:03 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5574 
   vendor CMN
  xserver.version: 2:1.18.3-1ubuntu2

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


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


[Touch-packages] [Bug 1750883] Re: X session does no more start after upgrade - hybrid-gfx no such file or directory

2022-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug report has any relevance when using
a currently maintained release of Ubuntu then please let us know which
one(s) otherwise this bug report can be left to expire in approximately
60 days time.


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

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

Title:
  X session does no more start after upgrade - hybrid-gfx no such file
  or directory

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Xorg.log finish with

  [   104.348] (II) config/udev: Adding input device HID 046d:c31b 
(/dev/input/mouse0)
  [   104.348] (II) No input driver specified, ignoring this device.
  init: Failed to spawn hybrid-gfx main process: unable to execute: No such 
file or directory

  as previous one which started OK finished with

  [87.952] (II) config/udev: Adding input device HID 046d:c31b 
(/dev/input/mouse0) 
 
  [87.952] (II) No input driver specified, ignoring this device. 
  [87.952] (II) This device may have been added with another device file.   


  [   101.619] (II) XKB: reuse xkmfile 
/var/lib/xkb/server-79DA8A0BAEB4CF1B2497C5C30BA2CA0B8D85.xkm
 
  [   101.629] (II) XKB: reuse xkmfile 
/var/lib/xkb/server-79DA8A0BAEB4CF1B2497C5C30BA2CA0B8D85.xkm
 
  [   103.104] (II) evdev: HID 046d:c31b: Close 


  [   103.104] (II) UnloadModule: "evdev"   


  [   103.104] (II) evdev: HID 046d:c31b: Close 


  [   103.104] (II) UnloadModule: "evdev"   


  [   103.104] (II) evdev: HID 046d:c31b: Close 


  [   103.104] (II) UnloadModule: "evdev"   


  [   103.104] (II) evdev: Power Button: Close  


  [   103.104] (II) UnloadModule: "evdev"   


  [   103.428] (II) MGA(0): UNMAPPING framebuffer 0x7F8E49569000, 0x7F. 


  [   103.483] (EE) Server terminated successfully (0). Closing log file. 

  /etc/init/hybrid-gfx.conf
  start on (starting lightdm
or starting kdm
or starting xdm
or starting lxdm)
  task
  exec hybrid-detect

  But no hybrid-detect script or binary

  dh@srvfwstr:/etc/init$ lsb_release -rd
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Wed Feb 21 18:59:15 2018
  DistUpgraded: 2017-11-04 16:16:22,019 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04dd]
  MachineType: Dell Inc. PowerEdge R210 II
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic 
root=/dev/mapper/vg0-DomU0 ro
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  

[Touch-packages] [Bug 1870111] Re: Thunderbird freezes graphical session except mouse cursor on second launch or clicking the icon after email setup on the first launch

2022-09-26 Thread Paul White
This Thunderbird issue has sat with a status of 'Incomplete' for over
two years now without any response from the reporter who seems to have
deactivated his account. As no-one else has confirmed or commented on
this issue I'll close this as being an invalid bug report.

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

** Changed in: thunderbird (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Thunderbird freezes graphical session except mouse cursor on second
  launch or clicking the icon after email setup on the first launch

Status in network-manager package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  When Launching thunderbird (pinned on Favourites) from the dock/dash
  it shows 2 orange dots on default theme that is one for email setup
  and the other for the main window. After setting up an email and
  closing the email config window, the two dots are still shown on the
  dash/dock before the icon. Thunderbird causes the graphical session
  except for the mouse cursor to freeze until I switch to a TTY and
  reboot. Also when closing thunderbird, one dot is shown and when
  launching the application the graphical session except for mouse
  cursor freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: thunderbird 1:68.4.1+build1-0ubuntu0.19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.7
  Architecture: amd64
  BuildID: 20200110143530
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  1 13:26:59 2020
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2020-03-31 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=68.4.1/20200110143530
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1990902] [NEW] Ubuntu-bug not submitting bug to website

2022-09-26 Thread Konstantin
Public bug reported:

Steps to reproduce:

$ ubuntu-bug apport
Gtk-Message: 10:30:47.890: Failed to load module "xapp-gtk3-module"
Gtk-Message: 10:30:47.920: Failed to load module "canberra-gtk-module"
Gtk-Message: 10:30:47.921: Failed to load module "canberra-gtk-module"

A web browser opens with bugs.launchpad.net saying it will reload the
page in 10 seconds to see if the report is there. It keeps checking
every 10 seconds but the report never shows up.

The system runs is Ubuntu 22.04, recently upgraded from 20.04.

I attached the output of ubuntu-bug apport --save=filename

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

** Attachment added: "Apport data"
   https://bugs.launchpad.net/bugs/1990902/+attachment/5619289/+files/gaga

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

Title:
  Ubuntu-bug not submitting bug to website

Status in apport package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  $ ubuntu-bug apport
  Gtk-Message: 10:30:47.890: Failed to load module "xapp-gtk3-module"
  Gtk-Message: 10:30:47.920: Failed to load module "canberra-gtk-module"
  Gtk-Message: 10:30:47.921: Failed to load module "canberra-gtk-module"

  A web browser opens with bugs.launchpad.net saying it will reload the
  page in 10 seconds to see if the report is there. It keeps checking
  every 10 seconds but the report never shows up.

  The system runs is Ubuntu 22.04, recently upgraded from 20.04.

  I attached the output of ubuntu-bug apport --save=filename

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


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


[Touch-packages] [Bug 1990903] [NEW] Openconnect crashes on auth dialog

2022-09-26 Thread Konstantin
Public bug reported:

The authentication dialog of openconnect crashes.

Steps to reproduce:

Add net vpn connection in Gui: 
* Settings -> Network -> VPN -> +
* Selecct "Multi-protocol vpn client (openconnect)"
* Select "Cisco AnyConnect or openconnect"
* Enter as gateway "vpn.sydney.edu.au"
* Click "Add"
* Activate the newly added VPN
* Click "Connect"

Now the login window briefly shows up before it disappears without error
message or anything.

The syslog contains the following lines indicating that the
authentication dialog segfaulted.

Sep 27 10:44:06 durian kernel: [214841.848187] nm-openconnect-[150897]: 
segfault at 0 ip 5602eb992570 sp 7ffc8f6abd40 error 4 in 
nm-openconnect-auth-dialog[5602eb98e000+6000]
Sep 27 10:44:06 durian kernel: [214841.848205] Code: 66 2e 0f 1f 84 00 00 00 00 
00 49 8b 3e 49 83 c6 08 e8 f4 d1 ff ff 4c 39 f5 75 ef 48 8b 7c 24 10 31 ed e8 
e3 d1 ff ff 0f 1f 00 <49> 8b 3c ec 48 83 c5 01 e8 d3 d1 ff ff 39 eb 7f ef 4c 89 
e7 e8 c7


The system is Ubuntu 22.04, recently updated from 20.04. I attached the output 
of 
ubuntu-bug network-manager-openconnect --save=filename
To this report.

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

** Attachment added: "Apport data"
   
https://bugs.launchpad.net/bugs/1990903/+attachment/5619290/+files/apportdata.txt

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

Title:
  Openconnect crashes on auth dialog

Status in apport package in Ubuntu:
  New

Bug description:
  The authentication dialog of openconnect crashes.

  Steps to reproduce:

  Add net vpn connection in Gui: 
  * Settings -> Network -> VPN -> +
  * Selecct "Multi-protocol vpn client (openconnect)"
  * Select "Cisco AnyConnect or openconnect"
  * Enter as gateway "vpn.sydney.edu.au"
  * Click "Add"
  * Activate the newly added VPN
  * Click "Connect"

  Now the login window briefly shows up before it disappears without
  error message or anything.

  The syslog contains the following lines indicating that the
  authentication dialog segfaulted.

  Sep 27 10:44:06 durian kernel: [214841.848187] nm-openconnect-[150897]: 
segfault at 0 ip 5602eb992570 sp 7ffc8f6abd40 error 4 in 
nm-openconnect-auth-dialog[5602eb98e000+6000]
  Sep 27 10:44:06 durian kernel: [214841.848205] Code: 66 2e 0f 1f 84 00 00 00 
00 00 49 8b 3e 49 83 c6 08 e8 f4 d1 ff ff 4c 39 f5 75 ef 48 8b 7c 24 10 31 ed 
e8 e3 d1 ff ff 0f 1f 00 <49> 8b 3c ec 48 83 c5 01 e8 d3 d1 ff ff 39 eb 7f ef 4c 
89 e7 e8 c7

  
  The system is Ubuntu 22.04, recently updated from 20.04. I attached the 
output of 
  ubuntu-bug network-manager-openconnect --save=filename
  To this report.

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


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


[Touch-packages] [Bug 1926256] Re: Pasted text in the terminal is always highlighted and selected

2022-09-26 Thread Egmont Koblinger
Freshly released bash-5.2 allows to disable the highlighting of pasted
text (while keeping the "bracketed paste mode" functionality enabled),
or even to define custom highlighting.

You need to place something like this in your .inputrc:

  set enable-active-region off

or

  set active-region-start-color "\e[42m"  # change it to whatever you wish
  set active-region-end-color "\e[m"

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

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

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

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

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

  Actual result:
  * pasted command is selected and highlighted

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

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


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


[Touch-packages] [Bug 1990729] Re: gdb crashes when run from VSCode

2022-09-26 Thread Michael Hudson-Doyle
Could you try the gdb from proposed? I think it should help.

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

Title:
  gdb crashes when run from VSCode

Status in gdb package in Ubuntu:
  New

Bug description:
  I had no pre-existing breakpoints in VSCode, then added a breakpoint,
  and used F5 to run the debugger to the one breakpoint.  It crashed
  before it got there.  This is a C++ executable compiled for debugging
  using CMAKE.  I can successfully debug the program using the TUI mode
  of gdb, so I think the problem likes in the vscode interface to gdb.

  /build/gdb-wIRHdd/gdb-12.0.90/gdb/value.c:1731: internal-error: value_copy: 
Assertion `arg->contents != nullptr' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) [answered Y; input not from terminal]
  /build/gdb-wIRHdd/gdb-12.0.90/gdb/value.c:1731: internal-error: value_copy: 
Assertion `arg->contents != nullptr' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) [answered Y; input not from terminal]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdb 12.0.90-0ubuntu1
  ProcVersionSignature: Ubuntu 5.14.0-1051.58-oem 5.14.21
  Uname: Linux 5.14.0-1051-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 11:10:11 2022
  InstallationDate: Installed on 2022-02-15 (221 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gdb
  UpgradeStatus: Upgraded to jammy on 2022-09-06 (18 days ago)

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


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


[Touch-packages] [Bug 1990891] [NEW] after today's Kinetic updates, WiFi no longer working, so laptop basically useless

2022-09-26 Thread Jonathan Kamens
Public bug reported:

ThinkPad X1 Carbon 6th Gen
WiFi was working fine.
Installed today's batch of Kinetic updates.
Laptop can no longer see any WiFi networks (had to dig out my old ThinkPad USB 
dongle and plug into my router to be able to submit this bug report).

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: network-manager 1.40.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 26 17:09:25 2022
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2019-08-16 (1137 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
IpRoute:
 default via 192.168.4.1 dev enp0s31f6 proto dhcp src 192.168.4.158 metric 100 
 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
 192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.158 metric 
100
SourcePackage: network-manager
UpgradeStatus: Upgraded to kinetic on 2022-09-24 (2 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

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


** Tags: amd64 apport-bug kinetic

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

Title:
  after today's Kinetic updates, WiFi no longer working, so laptop
  basically useless

Status in network-manager package in Ubuntu:
  New

Bug description:
  ThinkPad X1 Carbon 6th Gen
  WiFi was working fine.
  Installed today's batch of Kinetic updates.
  Laptop can no longer see any WiFi networks (had to dig out my old ThinkPad 
USB dongle and plug into my router to be able to submit this bug report).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: network-manager 1.40.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 17:09:25 2022
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-08-16 (1137 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.4.1 dev enp0s31f6 proto dhcp src 192.168.4.158 metric 
100 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.158 
metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (2 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

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


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


[Touch-packages] [Bug 1946192] Re: "Press Ctrl+C to cancel all filesystem checks in process" on every boot

2022-09-26 Thread miguelquiros
In my case, if I introduce the boot parameter fsck.mode=skip, then the
message "Press Ctrl+C to cancel all filesystem checks in process" does
not appear and the boot is faster, hence I deduce that the checks are
indeed performed when the boot parameter is not present.

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

Title:
  "Press Ctrl+C to cancel all filesystem checks in process" on every
  boot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I installed Kubuntu 20.04 on Latitude 5591 laptop using flash drive.
  Installation run without any issues but now on every boot I notice a
  message "Press Ctrl+C to cancel all filesystem checks in process" on
  the Plymouth screen with Kubuntu logo. It flashes quickly and
  disappears. I've got fast NVMe drive so I cannot say for sure whether
  it runs any checks or not.

  I booted from LiveCD and performed fsck checks of all my partitions:
  fsck.vfat /dev/nvme0n1p1 (EFI partition)
  fsck.vfat /dev/nvme0n1p2 (Dell service partition, not mounted)
  e2fsck -f /dev/nvme0n1p3 (Root partition)
  e2fsck -f /dev/nvme0n1p5 (Home partition)
  These checks showed no problems.

  I changed mount counter to set periodic checks:
  sudo tune2fs -c 29 /dev/nvme0n1p3
  sudo tune2fs -c 30 /dev/nvme0n1p5
  But despite these settings this message still appears on every boot.

  Operating System: Kubuntu 20.04.3
  Kernel Version: 5.4.0-88-generic
  OS Type: 64-bit
  Processors: 12 × Intel® Core™ i7-8850H CPU @ 2.60GHz
  Memory: 15,4 GiB of RAM

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DefaultPlymouth: /usr/share/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-09 (57 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:568c Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5591
  Package: plymouth 0.9.4git20200323-0ubuntu6.2
  PackageArchitecture: amd64
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic 
root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet 
splash vt.handoff=7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic 
root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Tags:  focal
  TextPlymouth: /usr/share/plymouth/themes/kubuntu-text/kubuntu-text.plymouth
  Uname: Linux 5.4.0-88-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 06/10/2021
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0DVVG1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd06/10/2021:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0DVVG1:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5591
  dmi.product.sku: 0819
  dmi.sys.vendor: Dell Inc.

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


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


[Touch-packages] [Bug 1990668] Re: package python3-oauthlib 3.2.0-1ubuntu0.1 failed to install/upgrade: problemas de dependencias - se deja sin configurar

2022-09-26 Thread Sergio Durigan Junior
Thank you for taking the time to file a bug report.

>From DpkgTerminalLog.txt, I see the following errors:

Configurando python3 (3.10.6-1~22.04) ...
running python rtupdate hooks for python3.10...
E: py3compile:212: cannot create directory /usr/share/hplip/base/__pycache__: 
FileNotFoundError(2, 'No such file or directory')
E: py3compile:212: cannot create directory 
/usr/share/hplip/base/pexpect/__pycache__: FileNotFoundError(2, 'No such file 
or directory')
...

The files under /usr/share/hplip/ belong to the hplip-data package,
which contains data files for HP printers/scanners.  Did you remove
these files manually by any chance?  I'm wondering why they could not be
found in your system.

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.

However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, explain why you believe this is a bug in Ubuntu
rather than a problem specific to your system, and then change the bug
status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

** Changed in: python-oauthlib (Ubuntu)
   Status: New => Incomplete

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

Title:
  package python3-oauthlib 3.2.0-1ubuntu0.1 failed to install/upgrade:
  problemas de dependencias - se deja sin configurar

Status in python-oauthlib package in Ubuntu:
  Incomplete

Bug description:
  Failed to get installed

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: python3-oauthlib 3.2.0-1ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  Date: Fri Sep 23 06:58:07 2022
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2022-06-22 (92 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  SourcePackage: python-oauthlib
  Title: package python3-oauthlib 3.2.0-1ubuntu0.1 failed to install/upgrade: 
problemas de dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-oauthlib/+bug/1990668/+subscriptions


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


[Touch-packages] [Bug 1990877] [NEW] Ubuntu 22.04 crash when I connect an external monitor with different refresh (Hz)

2022-09-26 Thread Noctis Bennington
Public bug reported:

When I connect from my laptop an external monitor with different
refresh, instantly crash the session and get me back to the gdm. After
connect the monitor from the restart the session, I can use it without
any issues, but if I disconnect it and I connect it again, the session
crash again.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 26 19:57:38 2022
DistUpgraded: 2022-04-03 23:19:05,278 INFO cache.commit()
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus: openrazer-driver/3.2.0: added
ExtraDebuggingInterest: Yes
GraphicsCard:
 Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 5600 
OEM/5600 XT / 5700/5700 XT] [1462:12ce]
 Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Renoir [1462:12ce]
InstallationDate: Installed on 2021-05-24 (489 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: Micro-Star International Co., Ltd. Alpha 17 A4DEK
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=d028c740-1e9e-4c72-a093-c9bef7123709 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to jammy on 2022-04-03 (175 days ago)
dmi.bios.date: 10/26/2020
dmi.bios.release: 1.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17EKAMS.101
dmi.board.asset.tag: Default string
dmi.board.name: MS-17EK
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
dmi.product.family: Al
dmi.product.name: Alpha 17 A4DEK
dmi.product.sku: 17EK.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug crash jammy third-party-packages ubuntu 
wayland-session

** Description changed:

  When I connect from my laptop an external monitor with different
- refresh, instantly crash the session and get me back to the gdm.
+ refresh, instantly crash the session and get me back to the gdm. After
+ connect the monitor from the restart the session, I can use it without
+ any issues, but if I disconnect it and I connect it again, the session
+ crash again.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 19:57:38 2022
  DistUpgraded: 2022-04-03 23:19:05,278 INFO cache.commit()
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.2.0: added
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 5600 
OEM/5600 XT / 5700/5700 XT] [1462:12ce]
-  Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 
00 [VGA controller])
-Subsystem: Micro-Star International Co., Ltd. [MSI] Renoir [1462:12ce]
+  Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 5600 
OEM/5600 XT / 5700/5700 XT] [1462:12ce]
+  Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 
00 [VGA controller])
+    Subsystem: Micro-Star International Co., Ltd. [MSI] Renoir [1462:12ce]
  InstallationDate: Installed on 2021-05-24 (489 days ago)
  InstallationMedia: Ubuntu 21.04 

[Touch-packages] [Bug 1985887] Re: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s)

2022-09-26 Thread Daniel Johnson
I've had two more instances, one on the 18th and one (multiple,
actually) today.  Both were triggered by copying a file as I'd described
(from CLI, "ionice -c3 nice cp -a SRC DST").  Today's OOM events also
killed a Firefox window for some reason.  I captured an sosreport on
both days, but last week's event showed I'd neglected to activate
sysstat/sar.  I am only uploading today's sosreport, but if the older
one may be useful I can add it as well.

All of the recent OOMs had this reason, with a varying initial percentage:
"due to memory pressure for /user.slice/user-1000.slice/user@1000.service being 
99.00% > 50.00% for > 20s with reclaim activity"


** Attachment added: "SOS report and systemd-oomd status"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1985887/+attachment/5619231/+files/sosreport_20220926.tar

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

Title:
  systemd kills gnome-shell or gnome-terminal if gnome-terminal uses
  much memory (50% over 20s)

Status in OEM Priority Project:
  Invalid
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  [Steps to reproduce]
  0. Install Jammy image
  1. open gnome terminal
  2. issue stress_ng or Canonical certification tool checkbox as
  "checkbox-cli run com.canonical.certification::memory/memory_stress_ng"
  or
  "stress-ng --stack 0 --timeout 300"
  3. Terminal or Gnome-shell will be killed by systemd-oomd

  It's because all stressors are under same cgroup belongs to terminal.

  Both Wayland and Xorg can reproduce.

  over ssh and in multi-user.target work good.

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


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


[Touch-packages] [Bug 1990869] [NEW] gnucash: segmentation fault when generating reports

2022-09-26 Thread JK
Public bug reported:

Whenever I try to generate a report in GnuCash it fails with a
segmentation fault. It doesn't matter which report I generate or which
accounts / files I am using.

About two weeks ago, everything was working fine. GnuCash package
version: 1:4.8-1build2

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

** Package changed: glib2.0 (Ubuntu) => gnucash (Ubuntu)

** Description changed:

  Whenever I try to generate a report in GnuCash it fails with a
  segmentation fault. It doesn't matter which report I generate or which
  accounts / files I am using.
  
- About two weeks ago, everything was working fine. Package version:
- 1:4.8-1build2
+ About two weeks ago, everything was working fine. GnuCash package
+ version: 1:4.8-1build2

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

Title:
  gnucash: segmentation fault when generating reports

Status in gnucash package in Ubuntu:
  New

Bug description:
  Whenever I try to generate a report in GnuCash it fails with a
  segmentation fault. It doesn't matter which report I generate or which
  accounts / files I am using.

  About two weeks ago, everything was working fine. GnuCash package
  version: 1:4.8-1build2

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


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


[Touch-packages] [Bug 1989830] Re: vmwgfx_dri.so not built on aarch64

2022-09-26 Thread Launchpad Bug Tracker
This bug was fixed in the package mesa - 22.2.0-1ubuntu1

---
mesa (22.2.0-1ubuntu1) kinetic; urgency=medium

  * Merge from Debian. (LP: #1990387)
  * patches: Drop DG2 patches that won't be getting applied upstream.
  * control, rules: Migrate to llvm-15.

mesa (22.2.0-1) unstable; urgency=medium

  * New upstream release.
  * nv50-ir-fix-OP_UNION-resolving-when-used-for-vector.diff: Dropped,
upstream.
  * rules: Enable svga (vmwgfx) for armhf/arm64. (LP: #1989830)
  * control: Drop x32 from mesa-vulkan-drivers archs. (Closes: #1020386)

mesa (22.2.0~rc3-2) unstable; urgency=medium

  * nv50-ir-fix-OP_UNION-resolving-when-used-for-vector.diff: Fix a
regression on nouveau. (Closes: #1017499)

mesa (22.2.0~rc3-1) unstable; urgency=medium

  * New upstream release candidate.
  * rules: Enable video codecs. (Closes: #1016687)
  * control: Add python3 to mesa-vulkan-drivers depends.

mesa (22.2.0~rc2-1) unstable; urgency=medium

  * New upstream release candidate. (Closes: #1016801)

mesa (22.2.0~rc1-1) unstable; urgency=medium

  * New upstream release candidate.
  * revert-enabling-tlsdesc-support.diff: Dropped, obsolete.

 -- Timo Aaltonen   Mon, 26 Sep 2022 12:12:03 +0300

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  vmwgfx_dri.so not built on aarch64

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu currently isn't building the vmwgfx_dri.so driver on aarch64 which 
makes graphics acceleration not work on VMware hypervisors running aarch64. Any 
Mesa3D version 22.1.4 or higher has full 3D support for the svga device, 
unfortunately only in:
  
https://gitlab.freedesktop.org/mesa/mesa/-/commit/6e311dd7229b2afb478e65afe2f17d7fb422d01e
  we've added it to the default/auto compile options, before then it had to be 
manually enabled.

  It would be great if mesa packages for 22.10 could build the
  vmwgfx_dri.so by enabling the svga device in mesa packages. That would
  make accelerated GL work on aarch64 with VMware products.

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


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


[Touch-packages] [Bug 1990387] Re: FFE: Mesa 22.2.0

2022-09-26 Thread Launchpad Bug Tracker
This bug was fixed in the package mesa - 22.2.0-1ubuntu1

---
mesa (22.2.0-1ubuntu1) kinetic; urgency=medium

  * Merge from Debian. (LP: #1990387)
  * patches: Drop DG2 patches that won't be getting applied upstream.
  * control, rules: Migrate to llvm-15.

mesa (22.2.0-1) unstable; urgency=medium

  * New upstream release.
  * nv50-ir-fix-OP_UNION-resolving-when-used-for-vector.diff: Dropped,
upstream.
  * rules: Enable svga (vmwgfx) for armhf/arm64. (LP: #1989830)
  * control: Drop x32 from mesa-vulkan-drivers archs. (Closes: #1020386)

mesa (22.2.0~rc3-2) unstable; urgency=medium

  * nv50-ir-fix-OP_UNION-resolving-when-used-for-vector.diff: Fix a
regression on nouveau. (Closes: #1017499)

mesa (22.2.0~rc3-1) unstable; urgency=medium

  * New upstream release candidate.
  * rules: Enable video codecs. (Closes: #1016687)
  * control: Add python3 to mesa-vulkan-drivers depends.

mesa (22.2.0~rc2-1) unstable; urgency=medium

  * New upstream release candidate. (Closes: #1016801)

mesa (22.2.0~rc1-1) unstable; urgency=medium

  * New upstream release candidate.
  * revert-enabling-tlsdesc-support.diff: Dropped, obsolete.

 -- Timo Aaltonen   Mon, 26 Sep 2022 12:12:03 +0300

** Changed in: mesa (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  FFE: Mesa 22.2.0

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Mesa 22.2.0 was released yesterday, a month late. This is an important
  release which brings support for AMD RDNA3 (together with llvm-15),
  Intel Arc (aka DG2) etc.

  Debian unstable has had 22.2.0-rc's since the start, because it was
  mistakenly uploaded there.. anyway, there was only one regression
  filed for x86 which is now fixed. Another one is for aarch64/virtio
  (Debian bug 1020391) and is unclear at this point if it's fixed by the
  final version or not.

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


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


[Touch-packages] [Bug 1946192] Re: "Press Ctrl+C to cancel all filesystem checks in process" on every boot

2022-09-26 Thread Oleg Moiseichuk
It seems that it runs after all at every boot. For example, I started my
system and checked afterwards:

> journalctl | grep fsck | grep 'sep 26'
sep 26 19:20:41 L-5591 systemd[1]: Created slice system-systemd\x2dfsck.slice.
sep 26 19:20:41 L-5591 systemd[1]: Listening on fsck to fsckd communication 
Socket.
sep 26 19:20:42 L-5591 systemd-fsck[637]: /dev/nvme0n1p5: clean, 59131/48832512 
files, 22974937/195312640 blocks
sep 26 19:20:42 L-5591 systemd-fsck[664]: fsck.fat 4.1 (2017-01-24)
sep 26 19:20:42 L-5591 systemd-fsck[664]: /dev/nvme0n1p1: 42 files, 
10823/190976 clusters
sep 26 19:21:11 L-5591 systemd[1]: systemd-fsckd.service: Succeeded.

Similar entries can be found in previous days' journal.

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

Title:
  "Press Ctrl+C to cancel all filesystem checks in process" on every
  boot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I installed Kubuntu 20.04 on Latitude 5591 laptop using flash drive.
  Installation run without any issues but now on every boot I notice a
  message "Press Ctrl+C to cancel all filesystem checks in process" on
  the Plymouth screen with Kubuntu logo. It flashes quickly and
  disappears. I've got fast NVMe drive so I cannot say for sure whether
  it runs any checks or not.

  I booted from LiveCD and performed fsck checks of all my partitions:
  fsck.vfat /dev/nvme0n1p1 (EFI partition)
  fsck.vfat /dev/nvme0n1p2 (Dell service partition, not mounted)
  e2fsck -f /dev/nvme0n1p3 (Root partition)
  e2fsck -f /dev/nvme0n1p5 (Home partition)
  These checks showed no problems.

  I changed mount counter to set periodic checks:
  sudo tune2fs -c 29 /dev/nvme0n1p3
  sudo tune2fs -c 30 /dev/nvme0n1p5
  But despite these settings this message still appears on every boot.

  Operating System: Kubuntu 20.04.3
  Kernel Version: 5.4.0-88-generic
  OS Type: 64-bit
  Processors: 12 × Intel® Core™ i7-8850H CPU @ 2.60GHz
  Memory: 15,4 GiB of RAM

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DefaultPlymouth: /usr/share/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-09 (57 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:568c Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5591
  Package: plymouth 0.9.4git20200323-0ubuntu6.2
  PackageArchitecture: amd64
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic 
root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet 
splash vt.handoff=7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic 
root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Tags:  focal
  TextPlymouth: /usr/share/plymouth/themes/kubuntu-text/kubuntu-text.plymouth
  Uname: Linux 5.4.0-88-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 06/10/2021
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0DVVG1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd06/10/2021:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0DVVG1:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5591
  dmi.product.sku: 0819
  dmi.sys.vendor: Dell Inc.

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


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


[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-09-26 Thread Brian Murray
** Tags removed: foundations-todo

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

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in bedtools package in Ubuntu:
  Fix Released
Status in htslib package in Ubuntu:
  Invalid
Status in zlib package in Ubuntu:
  Fix Released
Status in bedtools source package in Focal:
  Invalid
Status in htslib source package in Focal:
  Fix Committed
Status in zlib source package in Focal:
  Fix Committed
Status in bedtools source package in Impish:
  Won't Fix
Status in htslib source package in Impish:
  Won't Fix
Status in zlib source package in Impish:
  Won't Fix
Status in bedtools source package in Jammy:
  Fix Released
Status in htslib source package in Jammy:
  Invalid
Status in zlib source package in Jammy:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  * On top of this actual zlib fix, there is another patch needed:
   'Remove compressBound assertions. (PR #1258)' for htslib.

  * But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected by the zlib issue.

  * The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.

  * The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.

  * Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427  

  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  

[Touch-packages] [Bug 1990187] Re: systemd-resolved recommends libnss-resolve in kinetic, pulls it into minimal system where it was explicitly excluded before

2022-09-26 Thread Matthieu Clemenceau
** Tags removed: foundations-todo

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

Title:
  systemd-resolved recommends libnss-resolve in kinetic, pulls it into
  minimal system where it was explicitly excluded before

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  In kinetic, systemd-resolved now Recommends: libnss-resolve, pulling
  it into the ubuntu-minimal seed.

  In the past we briefly had libnss-resolve seeded (between xenial and
  bionic LTSes but not in any LTS) but it was removed because:

   - it was redundant; /etc/resolv.conf was consistent and correct.
   - its presence could mask wrong DNS configuration resulting in 
difficult-to-debug differences in behavior between applications that did use 
nss_resolved via /etc/nsswitch.conf and those that did not (examples: i386 
binaries that could not use nss_resolved because it was not installed; 
statically-linked go implementations that parsed /etc/resolve.conf directly and 
did not load NSS modules)

  This new recommends was noticed specifically because of some broken
  kinetic container images where /etc/resolv.conf was broken (empty) and
  *some* applications still worked via nss but others failed by trying
  to use the DNS protocol directly.  (I.e.: 2nd point above)

  I believe systemd-resolved should drop its recommends on libnss-
  resolve for Ubuntu.

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


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


[Touch-packages] [Bug 1989989] Re: Microphone not working on Lenovo Yoga 7 Gen 7 AMD (14ARB7)

2022-09-26 Thread Saverio Miroddi
This patch:

https://bugzilla.kernel.org/show_bug.cgi?id=216299#c3

fixes the problem. The volume is low, but better than not working at all
:)

** Bug watch added: Linux Kernel Bug Tracker #216299
   https://bugzilla.kernel.org/show_bug.cgi?id=216299

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

Title:
  Microphone not working on Lenovo Yoga 7 Gen 7 AMD (14ARB7)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On my Lenovo Yoga 7 Gen 7 AMD (14ARB7), the microphone doesn't work.
  I'm not familiar with the area, but I think that there is no
  recognized input device at all.

  When I try to record with any program, no sound is recorded.

  I think that this problem affects other Lenovo Yoga laptops.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  Uname: Linux 6.0.0-06rc3-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  saverio1949 F pulseaudio
   /dev/snd/controlC0:  saverio1949 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Sep 16 18:15:09 2022
  InstallationDate: Installed on 2022-09-15 (1 days ago)
  InstallationMedia: Ubuntu-MATE 22.04.1-6.0rc3 "Custom Jammy Jellyfish" 
(20220910)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) :   N o   s u c h   f i l e  
 o r   d i r e c t o r y
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   m a i n : 8 3 1 :   a u d 
i o   o p e n   e r r o r :   N o   s u c h   f i l e   o r   d i r e c t o r y
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  saverio1949 F pulseaudio
   /dev/snd/controlC0:  saverio1949 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HD-Audio Generic, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2022
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: K5CN27WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76463 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 7 14ARB7
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrK5CN27WW:bd05/08/2022:br1.27:efr1.27:svnLENOVO:pn82QF:pvrYoga714ARB7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga714ARB7:skuLENOVO_MT_82QF_BU_idea_FM_Yoga714ARB7:
  dmi.product.family: Yoga 7 14ARB7
  dmi.product.name: 82QF
  dmi.product.sku: LENOVO_MT_82QF_BU_idea_FM_Yoga 7 14ARB7
  dmi.product.version: Yoga 7 14ARB7
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2022-09-15T11:39:08.571662

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


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


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

2022-09-26 Thread Jonathan Kamens
Public bug reported:

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

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

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

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


** Tags: amd64 apport-bug kinetic

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

Title:
  conversion from sshd service to socket is too bumpy

Status in openssh package in Ubuntu:
  New

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

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

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

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


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


[Touch-packages] [Bug 1990767] Re: Drivers error

2022-09-26 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Drivers error

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have a fresh install of Ubuntu 22.04 on my new laptop.
  Laptop: MSI Summit E16 flip Evo  MFG: 2022/01

  When my laptop boots up, I see the following errors on the display:

  [   26.677123] kernel: ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.UBTC.CR03._PLD], AE_NOT_FOUND (20210730/psargs-330)
  [   26.677133] kernel:
  [   26.677134] kernel: No Local Variables are initialized for Method [RUCC]
  [   26.677135] kernel:
  [   26.677136] kernel: Initialized Arguments for Method [RUCC]:  (2 arguments 
defined for method invocation)
  [   26.677137] kernel:   Arg0:   57d68be0Integer 
0003
  [   26.677142] kernel:   Arg1:   6ae5efd8Integer 
0002
  [   26.677145] kernel:
  [   26.677147] kernel: ACPI Error: Aborting method \_SB.UBTC.RUCC due to 
previous error (AE_NOT_FOUND) (20210730/psparse-529)
  [   26.677152] kernel: ACPI Error: Aborting method 
\_SB.PC00.TXHC.RHUB.SS03._PLD due to previous error (AE_NOT_FOUND) 
(20210730/psparse-529)
  [   26.677198] kernel: ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.UBTC.CR04._PLD], AE_NOT_FOUND (20210730/psargs-330)
  [   26.677203] kernel:
  [   26.677204] kernel: No Local Variables are initialized for Method [RUCC]
  [   26.677204] kernel:
  [   26.677205] kernel: Initialized Arguments for Method [RUCC]:  (2 arguments 
defined for method invocation)
  [   26.677206] kernel:   Arg0:   6ae5efd8Integer 
0004
  [   26.677209] kernel:   Arg1:   c5813084Integer 
0002
  [   26.677213] kernel:
  [   26.677214] kernel: ACPI Error: Aborting method \_SB.UBTC.RUCC due to 
previous error (AE_NOT_FOUND) (20210730/psparse-529)
  [   26.677219] kernel: ACPI Error: Aborting method 
\_SB.PC00.TXHC.RHUB.SS04._PLD due to previous error (AE_NOT_FOUND) 
(20210730/psparse-529)
  [   26.690809] kernel: sof-audio-pci-intel-tgl :00:1f.3: Firmware info: 
version 2:0:0-b678a
  [   26.690813] kernel: sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 
3:20:0 Kernel ABI 3:18:0
  [   26.690814] kernel: sof-audio-pci-intel-tgl :00:1f.3: warn: FW ABI is 
more recent than kernel
  [   26.699117] kernel: sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 
3:20:0 Kernel ABI 3:18:0
  [   26.699122] kernel: sof-audio-pci-intel-tgl :00:1f.3: warn: topology 
ABI is more recent than kernel
  [   26.731884] kernel: hid-sensor-hub 001F:8087:0AC2.0007: 
hid_field_extract() called with n (192) > 32! (kworker/6:0)
  [   26.734344] kernel: sof-audio-pci-intel-tgl :00:1f.3: ASoC: Parent 
card not yet available, widget card binding deferred
  [   26.766928] kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for 
ALC285: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
  [   26.766933] kernel: snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [   26.766934] kernel: snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [   26.766936] kernel: snd_hda_codec_realtek ehdaudio0D0:mono: 
mono_out=0x0
  [   26.766937] kernel: snd_hda_codec_realtek ehdaudio0D0:inputs:
  [   26.766938] kernel: snd_hda_codec_realtek ehdaudio0D0:  Mic=0x19
  [   27.301459] kernel: ACPI BIOS Error (bug): Could not resolve symbol 
[\_TZ.ETMD], AE_NOT_FOUND (20210730/psargs-330)
  [   27.301469] kernel:
  [   27.301470] kernel: No Local Variables are initialized for Method [_OSC]
  [   27.301471] kernel:
  [   27.301472] kernel: Initialized Arguments for Method [_OSC]:  (4 arguments 
defined for method invocation)
  [   27.301473] kernel:   Arg0:   322401caBuffer(16) 
5D A8 3B B2 B7 C8 42 35
  [   27.301482] kernel:   Arg1:   d63d1c67Integer 
0001
  [   27.301485] kernel:   Arg2:   c7663632Integer 
0002
  [   27.301489] kernel:   Arg3:   d2f230a3Buffer(8) 
00 00 00 00 05 00 00 00
  [   27.301495] kernel:
  [   27.301497] kernel: ACPI Error: Aborting method \_SB.IETM._OSC due to 
previous error (AE_NOT_FOUND) (20210730/psparse-529)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 25 14:19:01 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: 

Re: [Touch-packages] [Bug 1990638] Re: package libdebuginfod-common 0.187-3 failed to install/upgrade: installed libdebuginfod-common package post-installation script subprocess returned error exit st

2022-09-26 Thread Sergio Durigan Junior
On Monday, September 26 2022, Hadrien Mary wrote:

> I confirm the fix on Ubuntu 22.10 recently updated.

Thanks, Hadrien.

-- 
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14

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

Title:
  package libdebuginfod-common 0.187-3 failed to install/upgrade:
  installed libdebuginfod-common package post-installation script
  subprocess returned error exit status 1

Status in elfutils package in Ubuntu:
  Fix Released

Bug description:
  installer crashed while doing an update. Something with updating elf
  dwarf libraries, asked to modify some configuration with a dialog I
  replied OK and then the installation crashed.

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: libdebuginfod-common 0.187-3
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Sep 23 09:13:00 2022
  DuplicateSignature:
   package:libdebuginfod-common:0.187-3
   Setting up libdebuginfod-common (0.187-3) ...
   chmod: cannot access '/etc/profile.d/debuginfod.sh': No such file or 
directory
   dpkg: error processing package libdebuginfod-common (--configure):
installed libdebuginfod-common package post-installation script subprocess 
returned error exit status 1
  ErrorMessage: installed libdebuginfod-common package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2022-03-11 (195 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220310)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.2
  SourcePackage: elfutils
  Title: package libdebuginfod-common 0.187-3 failed to install/upgrade: 
installed libdebuginfod-common package post-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to kinetic on 2022-09-13 (9 days ago)

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


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


[Touch-packages] [Bug 1990813] Re: Failed to start NVIDIA Persistence Daemon - pci 0000:02:00.0: can't change power state from D3cold to D0 (config space inaccessible)

2022-09-26 Thread Nick Rosbrook
This does not look like a systemd bug, so I am re-assigning to linux.
But, this sounds similar to your issue:
https://forums.developer.nvidia.com/t/nvidia-probe-of-00-0-failed-
with-error-1/199301, based on looking at your attached CurrentDmesg.txt.



** Package changed: systemd (Ubuntu) => linux (Ubuntu)

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

Title:
  Failed to start NVIDIA Persistence Daemon - pci :02:00.0: can't
  change power state from D3cold to D0 (config space inaccessible)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I don't get this message every time at boot but sometimes it happens.
  I sent logs in attachments

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd 249.11-0ubuntu3.6
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 10:07:16 2022
  InstallationDate: Installed on 2022-03-02 (207 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512FLC_R564FL
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=2d8fb36c-c4c1-48be-b649-9fffa7a1440c ro loglevel=1 quiet splash 
loglevel=1 vt.handoff=7
  SourcePackage: systemd
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X512FLC.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X512FLC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX512FLC.304:bd01/26/2021:br5.16:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512FLC_R564FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X512FLC_R564FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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


[Touch-packages] [Bug 1946192] Re: "Press Ctrl+C to cancel all filesystem checks in process" on every boot

2022-09-26 Thread Benjamin Drung
Since most reporters say that the message "Press Ctrl+C to cancel all
filesystem checks in process" appears only for a short period of time,
the question is: Are there filesystem checks on every boot or is this
message shown despite no check were running?

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

Title:
  "Press Ctrl+C to cancel all filesystem checks in process" on every
  boot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I installed Kubuntu 20.04 on Latitude 5591 laptop using flash drive.
  Installation run without any issues but now on every boot I notice a
  message "Press Ctrl+C to cancel all filesystem checks in process" on
  the Plymouth screen with Kubuntu logo. It flashes quickly and
  disappears. I've got fast NVMe drive so I cannot say for sure whether
  it runs any checks or not.

  I booted from LiveCD and performed fsck checks of all my partitions:
  fsck.vfat /dev/nvme0n1p1 (EFI partition)
  fsck.vfat /dev/nvme0n1p2 (Dell service partition, not mounted)
  e2fsck -f /dev/nvme0n1p3 (Root partition)
  e2fsck -f /dev/nvme0n1p5 (Home partition)
  These checks showed no problems.

  I changed mount counter to set periodic checks:
  sudo tune2fs -c 29 /dev/nvme0n1p3
  sudo tune2fs -c 30 /dev/nvme0n1p5
  But despite these settings this message still appears on every boot.

  Operating System: Kubuntu 20.04.3
  Kernel Version: 5.4.0-88-generic
  OS Type: 64-bit
  Processors: 12 × Intel® Core™ i7-8850H CPU @ 2.60GHz
  Memory: 15,4 GiB of RAM

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DefaultPlymouth: /usr/share/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-09 (57 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:568c Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5591
  Package: plymouth 0.9.4git20200323-0ubuntu6.2
  PackageArchitecture: amd64
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic 
root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet 
splash vt.handoff=7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic 
root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Tags:  focal
  TextPlymouth: /usr/share/plymouth/themes/kubuntu-text/kubuntu-text.plymouth
  Uname: Linux 5.4.0-88-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 06/10/2021
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0DVVG1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd06/10/2021:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0DVVG1:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5591
  dmi.product.sku: 0819
  dmi.sys.vendor: Dell Inc.

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


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


[Touch-packages] [Bug 1990187] Re: systemd-resolved recommends libnss-resolve in kinetic, pulls it into minimal system where it was explicitly excluded before

2022-09-26 Thread Dimitri John Ledkov
we do not need or want libnss-resolve anymore, because we created stub-
resolv.conf which exports 1) local nameserver resolver 2) with correct
options 3) and search domains. We only needed libnss-resolve back when
we dind't have /run/systemd/resolve/stub-resolv.conf

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

Title:
  systemd-resolved recommends libnss-resolve in kinetic, pulls it into
  minimal system where it was explicitly excluded before

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  In kinetic, systemd-resolved now Recommends: libnss-resolve, pulling
  it into the ubuntu-minimal seed.

  In the past we briefly had libnss-resolve seeded (between xenial and
  bionic LTSes but not in any LTS) but it was removed because:

   - it was redundant; /etc/resolv.conf was consistent and correct.
   - its presence could mask wrong DNS configuration resulting in 
difficult-to-debug differences in behavior between applications that did use 
nss_resolved via /etc/nsswitch.conf and those that did not (examples: i386 
binaries that could not use nss_resolved because it was not installed; 
statically-linked go implementations that parsed /etc/resolve.conf directly and 
did not load NSS modules)

  This new recommends was noticed specifically because of some broken
  kinetic container images where /etc/resolv.conf was broken (empty) and
  *some* applications still worked via nss but others failed by trying
  to use the DNS protocol directly.  (I.e.: 2nd point above)

  I believe systemd-resolved should drop its recommends on libnss-
  resolve for Ubuntu.

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


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


[Touch-packages] [Bug 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used

2022-09-26 Thread Benjamin Drung
** Tags added: foundation-triage-discuss

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

Title:
  [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is
  used

Status in Ubuntu on IBM z Systems:
  New
Status in zlib package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Ilya Leoshkevich  - 2022-09-21 05:02:24 ==
  inflate() does not update strm.adler if DFLTCC is used.

  Found with a JDK test.

  zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349

  Updated zlib PR: https://github.com/madler/zlib/pull/410

  zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920

  zlib diff:
  
https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620

  Ubuntu 20.04 and later need to be fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+subscriptions


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


[Touch-packages] [Bug 1965293] Re: systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with linux/5.13.0-37.42

2022-09-26 Thread Nick Rosbrook
*** This bug is a duplicate of bug 1967576 ***
https://bugs.launchpad.net/bugs/1967576

This was fixed in bug 1967576, so I am marking this a duplicate of that.

** This bug has been marked a duplicate of bug 1967576
   systemd: autopkgtest: tests-in-lxd fails because of remaining snap .mount 
units

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

Title:
  systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with
  linux/5.13.0-37.42

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Impish:
  Incomplete
Status in systemd source package in Impish:
  Won't Fix
Status in linux source package in Jammy:
  Incomplete
Status in systemd source package in Jammy:
  Confirmed

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.13.0-37.42 on impish. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220317_104248_4bc6b@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220316_141606_ab727@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220317_110143_b6ced@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/s/systemd/20220317_103032_3d4bf@/log.gz

  The "tests-in-lxd" testcase is failing with all kernels in Impish:

  test_no_failed (__main__.ServicesTest)
  No failed units ...  journal for failed service snap-lxd-22662.mount 
---
  -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 
10:01:49 UTC. --
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for 
lxd, revision 22662...
  Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[91]: mount: /snap/lxd/22662: 
mount failed: Operation not permitted.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: 
Mount process exited, code=exited, status=1/FAILURE
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: 
Failed with result 'exit-code'.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit 
for lxd, revision 22662.
   journal for failed service snap-snapd-15177.mount ---
  -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 
10:01:49 UTC. --
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for 
snapd, revision 15177...
  Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[92]: mount: /snap/snapd/15177: 
mount failed: Operation not permitted.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: 
Mount process exited, code=exited, status=1/FAILURE
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: 
Failed with result 'exit-code'.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit 
for snapd, revision 15177.
  FAIL
  [...]
  ==
  FAIL: test_no_failed (__main__.ServicesTest)
  No failed units
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.HBv169/build.sBq/real-tree/debian/tests/boot-and-services", 
line 69, in test_no_failed
  self.assertEqual(failed, [])
  AssertionError: Lists differ: ['snap-lxd-22662.mount   loaded failed fai[119 
chars]177'] != []

  First list contains 2 additional elements.
  First extra element 0:
  'snap-lxd-22662.mount   loaded failed failed Mount unit for lxd, revision 
22662'

  + []
  - ['snap-lxd-22662.mount   loaded failed failed Mount unit for lxd, revision '
  -  '22662',
  -  'snap-snapd-15177.mount loaded failed failed Mount unit for snapd, 
revision '
  -  '15177']

  
  This testcase started to fail with the latest re-spin of the kernels 
(uploaded on mar-16), however the only patch applied between the previous 
kernels and the current ones is a CVE fix which is unlikely to be causing this 
failure:

  "ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()"
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/impish/commit/?id=da5043b3ed2889300211ba35d5a7d2f3b9255d1b

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


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


[Touch-packages] [Bug 1810241] Re: NULL dereference when decompressing specially crafted archives

2022-09-26 Thread Jeffrey Hawkins
Update to my comment, issue is applicable to versions prior to 1.32 of
TAR.  Be that as it may, Jammy is not affected.

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

Title:
  NULL dereference when decompressing specially crafted archives

Status in tar package in Ubuntu:
  Triaged

Bug description:
  Hi,

  Fuzzing tar with checksums disabled reveals a NULL pointer dereference
  when parsing certain archives that have malformed extended headers.
  This affects tar from (at least) Trusty, Bionic and Cosmic. I haven't
  tested Xenial's version.

  A test case with fixed checksums is attached. To avoid breaking
  anything that looks inside tar archives, I have converted it to text
  with xxd. To reproduce:

  $ xxd -r gnutar-crash.tar.txt gnutar-crash.tar
  $ tar Oxf gnutar-crash.tar 
  tar: Ignoring unknown extended header keyword 'GNU.sparse.minTr'
  tar: Malformed extended header: missing length
  Segmentation fault (core dumped)

  I have also attached a patch against the latest upstream git and
  against 1.30 (in Cosmic). This fixes the issue by detecting the null
  result before it is dereferenced.

  Regards,
  Daniel

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


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


[Touch-packages] [Bug 1810241] Re: NULL dereference when decompressing specially crafted archives

2022-09-26 Thread Jeffrey Hawkins
This issue is shown as Open on Jammy.  The CVE is applicable to 1.32 and
prior versions of TAR.  Jammy uses 1.34, so this status should be not
affected or closed.  This was fixed in Focal in
1.30+dfsg-7ubuntu0.20.04.1.  Please update the CVE status on Jammy.

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

Title:
  NULL dereference when decompressing specially crafted archives

Status in tar package in Ubuntu:
  Triaged

Bug description:
  Hi,

  Fuzzing tar with checksums disabled reveals a NULL pointer dereference
  when parsing certain archives that have malformed extended headers.
  This affects tar from (at least) Trusty, Bionic and Cosmic. I haven't
  tested Xenial's version.

  A test case with fixed checksums is attached. To avoid breaking
  anything that looks inside tar archives, I have converted it to text
  with xxd. To reproduce:

  $ xxd -r gnutar-crash.tar.txt gnutar-crash.tar
  $ tar Oxf gnutar-crash.tar 
  tar: Ignoring unknown extended header keyword 'GNU.sparse.minTr'
  tar: Malformed extended header: missing length
  Segmentation fault (core dumped)

  I have also attached a patch against the latest upstream git and
  against 1.30 (in Cosmic). This fixes the issue by detecting the null
  result before it is dereferenced.

  Regards,
  Daniel

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


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


[Touch-packages] [Bug 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise

2022-09-26 Thread Konstantin
have the same issue with hp envy 16 Alder Lake-P and Realtek ALC245.
With latest packages at the moment (kernel 5.15.0-48-generic)

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

Title:
  [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal]
  No sound except loud crackling (popping) noise

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake-
  LP audio controller. When playing any audio, the internal speaker
  plays no sound except periodic loud crackling noise. The 3.5mm jack
  does not work either, producing the same craclking noise alongside
  some eletrical noise. HDMI audio skimmishly tested, but also gave no
  sound. Curiously, USB headphone (along with microphone) works
  perfectly, also the internal microphone.

  As attempts to fix the problem, I have tried the following separately, with 
no avail:
  - Installing some Ubuntu OEM version of the 5.17 kernel
  - Updating to the v2.2 firmware from Sound Open Firmware Project 
(thesofproject on github), reverted afterwards

  I found exactly the same problem reported in the Fedora community:
  
https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound=1860086

  As the pre-installed Windows has been destroyed, no further test on
  Windows has been done.

  Since USB headphone and internal microphone work, I think that there
  is no problem on the Intel Tiger Lake-LP controller and its driver.
  The bug probably lies elsewhere, like in the handling of ALC245 on
  this new laptop model.

  Thank you very much for your time and effort in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fwjmath2810 F pulseaudio
fwjmath   72467 F alsamixer
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Thu Jul  7 10:59:22 2022
  InstallationDate: Installed on 2022-06-29 (7 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fwjmath2810 F pulseaudio
fwjmath   72467 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] 
No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2022
  dmi.bios.release: 9.1
  dmi.bios.vendor: HP
  dmi.bios.version: T37 Ver. 01.09.01
  dmi.board.name: 8AB8
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 58.03.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 88.3
  dmi.modalias: 
dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 G8 Notebook PC
  dmi.product.sku: 6A3P3AV
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239

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


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


[Touch-packages] [Bug 1990824] Re: initramfs-tools: out-of-memory failures during autopkgtest

2022-09-26 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

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

Title:
  initramfs-tools: out-of-memory failures during autopkgtest

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  [Impact]

  Some autopkgtest tests are failing due to out-of-memory conditions,
  especially amd64-ata-only and net.

  It seems that we are creating a VM with 1GB only to run the amd64-ata-
  only test and even just 512MB for the net test.

  It probably makes sense to create larger VMs (at least 2GB) to run
  these tests with a more recent kernels (that will likely require a
  little more RAM).

  [Test case]

  sudo autopkgtest . -- null

  [Fix]

  Increase memory size of instances used to run the autopkgtests to 2GB.

  [Regression potential]

  We may experience regressions in small cloud instances, or systems
  with less than 2GB or RAM that are using a recent kernel (but this is
  more a generic potential regression, not strictly related to
  initramfs-tools).

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


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


[Touch-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

2022-09-26 Thread Hannu E K N
The empty blacklist.conf seems to have caused all this.

- CLOSE -

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 0.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G731GU_G731GU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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


[Touch-packages] [Bug 1876376] Re: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: update-initramfs: Generating /boot/initrd.img-5.4.0-28-generic write error: cannot write compressed b

2022-09-26 Thread Benjamin Drung
** Summary changed:

- package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed 
initramfs-tools package post-installation script subprocess returned error exit 
status 1
+ package initramfs-tools 0.136ubuntu6 failed to install/upgrade: 
update-initramfs: Generating /boot/initrd.img-5.4.0-28-generic write error: 
cannot write compressed block

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

Title:
  package initramfs-tools 0.136ubuntu6 failed to install/upgrade:
  update-initramfs: Generating /boot/initrd.img-5.4.0-28-generic write
  error: cannot write compressed block

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  package failed to install during 18.04 to 20.04 upgrade

  DpkgTerminalLog.txt says:

  update-initramfs: Generating /boot/initrd.img-5.4.0-28-generic
  Error 24 : Write error : cannot write compressed block 
  E: mkinitramfs failure cpio 141 lz4 -9 -l 24
  update-initramfs: failed for /boot/initrd.img-5.4.0-28-generic with 1.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May  1 21:41:12 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2014-05-14 (2179 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-05-01 (0 days ago)

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


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


[Touch-packages] [Bug 1990684] Re: grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but 2.06-2ubuntu10 is to be installed

2022-09-26 Thread Julian Andres Klode
This issue seems to have been a funny bug in the solver, actually, and
not a bug in the phased update code itself.

So what happened is that we kept back grub-efi-amd64-signed, and it was
broken. So now the solver iterates over its dependencies and tries to
keep them back too. Except well, when looking at whether the dependency
could be kept back, it checked if parent package - grub-efi-amd64-signed
- was protected and not the dependency.

Hilarious, but fixed in

https://salsa.debian.org/apt-
team/apt/-/merge_requests/262/diffs?commit_id=ac2a5196326388b3a0a60090fe787b1eb85ed22a


with a simplified test case.

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

Title:
  grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but
  2.06-2ubuntu10 is to be installed

Status in apt package in Ubuntu:
  In Progress
Status in grub2-signed package in Ubuntu:
  Fix Released

Bug description:
  # apt clean

  # apt update
  Hit:1 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy InRelease
  Hit:2 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy-updates 
InRelease
  Hit:3 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy-backports 
InRelease
  Hit:4 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  24 packages can be upgraded. Run 'apt list --upgradable' to see them.

  # apt upgrade
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  The following packages have unmet dependencies:
   grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but 
2.06-2ubuntu10 is to be installed
  E: Broken packages

  # apt show -a grub-efi-arm64 2>/dev/null | grep -P "Version:|APT-Sources:"
  Version: 2.06-2ubuntu10
  APT-Sources: http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports 
jammy-updates/main arm64 Packages
  Version: 2.06-2ubuntu7
  APT-Sources: http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy/main 
arm64 Packages

  # curl -s 
"http://ports.ubuntu.com/ubuntu-ports/dists/jammy/main/binary-arm64/Packages.gz;
 | zgrep -B 13 "Depends: grub-efi-arm64" | grep -P "Package:|Depends:"
  Package: grub-efi-arm64-dbg
  Depends: grub-efi-arm64-bin (= 2.06-2ubuntu7)
  Package: grub-efi-arm64-signed
  Depends: grub-efi-arm64 (= 2.06-2ubuntu7)

  # curl -s 
"http://ports.ubuntu.com/ubuntu-ports/dists/jammy-updates/main/binary-arm64/Packages.gz;
 | zgrep -B 13 "Depends: grub-efi-arm64" | grep -P "Package:|Depends:"
  Package: grub-efi-arm64-dbg
  Depends: grub-efi-arm64-bin (= 2.06-2ubuntu10)
  Package: grub-efi-arm64-signed
  Depends: grub-efi-arm64 (= 2.06-2ubuntu10)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: grub-efi-arm64-signed 1.180+2.06-2ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-1020.24-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Fri Sep 23 13:12:07 2022
  Ec2AMI: ami-092d30890417a55e5
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ca-central-1d
  Ec2InstanceType: t4g.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   SHELL=/bin/bash
   LANG=C.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: grub2-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1990638] Re: package libdebuginfod-common 0.187-3 failed to install/upgrade: installed libdebuginfod-common package post-installation script subprocess returned error exit status

2022-09-26 Thread Hadrien Mary
I confirm the fix on Ubuntu 22.10 recently updated.

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

Title:
  package libdebuginfod-common 0.187-3 failed to install/upgrade:
  installed libdebuginfod-common package post-installation script
  subprocess returned error exit status 1

Status in elfutils package in Ubuntu:
  Fix Released

Bug description:
  installer crashed while doing an update. Something with updating elf
  dwarf libraries, asked to modify some configuration with a dialog I
  replied OK and then the installation crashed.

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: libdebuginfod-common 0.187-3
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Sep 23 09:13:00 2022
  DuplicateSignature:
   package:libdebuginfod-common:0.187-3
   Setting up libdebuginfod-common (0.187-3) ...
   chmod: cannot access '/etc/profile.d/debuginfod.sh': No such file or 
directory
   dpkg: error processing package libdebuginfod-common (--configure):
installed libdebuginfod-common package post-installation script subprocess 
returned error exit status 1
  ErrorMessage: installed libdebuginfod-common package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2022-03-11 (195 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220310)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.2
  SourcePackage: elfutils
  Title: package libdebuginfod-common 0.187-3 failed to install/upgrade: 
installed libdebuginfod-common package post-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to kinetic on 2022-09-13 (9 days ago)

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


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


[Touch-packages] [Bug 1990684] Re: grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but 2.06-2ubuntu10 is to be installed

2022-09-26 Thread Julian Andres Klode
** Changed in: apt (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: apt (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

Title:
  grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but
  2.06-2ubuntu10 is to be installed

Status in apt package in Ubuntu:
  In Progress
Status in grub2-signed package in Ubuntu:
  Fix Released

Bug description:
  # apt clean

  # apt update
  Hit:1 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy InRelease
  Hit:2 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy-updates 
InRelease
  Hit:3 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy-backports 
InRelease
  Hit:4 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  24 packages can be upgraded. Run 'apt list --upgradable' to see them.

  # apt upgrade
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  The following packages have unmet dependencies:
   grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but 
2.06-2ubuntu10 is to be installed
  E: Broken packages

  # apt show -a grub-efi-arm64 2>/dev/null | grep -P "Version:|APT-Sources:"
  Version: 2.06-2ubuntu10
  APT-Sources: http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports 
jammy-updates/main arm64 Packages
  Version: 2.06-2ubuntu7
  APT-Sources: http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy/main 
arm64 Packages

  # curl -s 
"http://ports.ubuntu.com/ubuntu-ports/dists/jammy/main/binary-arm64/Packages.gz;
 | zgrep -B 13 "Depends: grub-efi-arm64" | grep -P "Package:|Depends:"
  Package: grub-efi-arm64-dbg
  Depends: grub-efi-arm64-bin (= 2.06-2ubuntu7)
  Package: grub-efi-arm64-signed
  Depends: grub-efi-arm64 (= 2.06-2ubuntu7)

  # curl -s 
"http://ports.ubuntu.com/ubuntu-ports/dists/jammy-updates/main/binary-arm64/Packages.gz;
 | zgrep -B 13 "Depends: grub-efi-arm64" | grep -P "Package:|Depends:"
  Package: grub-efi-arm64-dbg
  Depends: grub-efi-arm64-bin (= 2.06-2ubuntu10)
  Package: grub-efi-arm64-signed
  Depends: grub-efi-arm64 (= 2.06-2ubuntu10)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: grub-efi-arm64-signed 1.180+2.06-2ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-1020.24-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Fri Sep 23 13:12:07 2022
  Ec2AMI: ami-092d30890417a55e5
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ca-central-1d
  Ec2InstanceType: t4g.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   SHELL=/bin/bash
   LANG=C.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: grub2-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1946192] Re: "Press Ctrl+C to cancel all filesystem checks in process" on every boot

2022-09-26 Thread Benjamin Drung
** Changed in: systemd (Ubuntu)
   Importance: Undecided => Low

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

Title:
  "Press Ctrl+C to cancel all filesystem checks in process" on every
  boot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I installed Kubuntu 20.04 on Latitude 5591 laptop using flash drive.
  Installation run without any issues but now on every boot I notice a
  message "Press Ctrl+C to cancel all filesystem checks in process" on
  the Plymouth screen with Kubuntu logo. It flashes quickly and
  disappears. I've got fast NVMe drive so I cannot say for sure whether
  it runs any checks or not.

  I booted from LiveCD and performed fsck checks of all my partitions:
  fsck.vfat /dev/nvme0n1p1 (EFI partition)
  fsck.vfat /dev/nvme0n1p2 (Dell service partition, not mounted)
  e2fsck -f /dev/nvme0n1p3 (Root partition)
  e2fsck -f /dev/nvme0n1p5 (Home partition)
  These checks showed no problems.

  I changed mount counter to set periodic checks:
  sudo tune2fs -c 29 /dev/nvme0n1p3
  sudo tune2fs -c 30 /dev/nvme0n1p5
  But despite these settings this message still appears on every boot.

  Operating System: Kubuntu 20.04.3
  Kernel Version: 5.4.0-88-generic
  OS Type: 64-bit
  Processors: 12 × Intel® Core™ i7-8850H CPU @ 2.60GHz
  Memory: 15,4 GiB of RAM

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DefaultPlymouth: /usr/share/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-09 (57 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:568c Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5591
  Package: plymouth 0.9.4git20200323-0ubuntu6.2
  PackageArchitecture: amd64
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic 
root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet 
splash vt.handoff=7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic 
root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Tags:  focal
  TextPlymouth: /usr/share/plymouth/themes/kubuntu-text/kubuntu-text.plymouth
  Uname: Linux 5.4.0-88-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 06/10/2021
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0DVVG1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd06/10/2021:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0DVVG1:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5591
  dmi.product.sku: 0819
  dmi.sys.vendor: Dell Inc.

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


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


[Touch-packages] [Bug 1876376] Re: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2022-09-26 Thread Benjamin Drung
From looking at the available logs, the first guess why lz4 failed to
write is that the partition is full. Can you check how much space you
have left on /boot?

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

Title:
  package initramfs-tools 0.136ubuntu6 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  package failed to install during 18.04 to 20.04 upgrade

  DpkgTerminalLog.txt says:

  update-initramfs: Generating /boot/initrd.img-5.4.0-28-generic
  Error 24 : Write error : cannot write compressed block 
  E: mkinitramfs failure cpio 141 lz4 -9 -l 24
  update-initramfs: failed for /boot/initrd.img-5.4.0-28-generic with 1.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May  1 21:41:12 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2014-05-14 (2179 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-05-01 (0 days ago)

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


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


[Touch-packages] [Bug 1876376] Re: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2022-09-26 Thread Benjamin Drung
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather more debugging information, in a terminal:

apport-collect -p ubuntu-release-upgrader 1876376

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

Title:
  package initramfs-tools 0.136ubuntu6 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  package failed to install during 18.04 to 20.04 upgrade

  DpkgTerminalLog.txt says:

  update-initramfs: Generating /boot/initrd.img-5.4.0-28-generic
  Error 24 : Write error : cannot write compressed block 
  E: mkinitramfs failure cpio 141 lz4 -9 -l 24
  update-initramfs: failed for /boot/initrd.img-5.4.0-28-generic with 1.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May  1 21:41:12 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2014-05-14 (2179 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-05-01 (0 days ago)

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


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


[Touch-packages] [Bug 1876376] Re: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2022-09-26 Thread Benjamin Drung
** Description changed:

  package failed to install during 18.04 to 20.04 upgrade
+ 
+ DpkgTerminalLog.txt says:
+ 
+ update-initramfs: Generating /boot/initrd.img-5.4.0-28-generic
+ Error 24 : Write error : cannot write compressed block 
+ E: mkinitramfs failure cpio 141 lz4 -9 -l 24
+ update-initramfs: failed for /boot/initrd.img-5.4.0-28-generic with 1.
  
  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May  1 21:41:12 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2014-05-14 (2179 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
-  dpkg 1.19.7ubuntu3
-  apt  2.0.2
+  dpkg 1.19.7ubuntu3
+  apt  2.0.2
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-05-01 (0 days ago)

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

Title:
  package initramfs-tools 0.136ubuntu6 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  package failed to install during 18.04 to 20.04 upgrade

  DpkgTerminalLog.txt says:

  update-initramfs: Generating /boot/initrd.img-5.4.0-28-generic
  Error 24 : Write error : cannot write compressed block 
  E: mkinitramfs failure cpio 141 lz4 -9 -l 24
  update-initramfs: failed for /boot/initrd.img-5.4.0-28-generic with 1.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May  1 21:41:12 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2014-05-14 (2179 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-05-01 (0 days ago)

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


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


[Touch-packages] [Bug 1990586] Re: 22.04: python3* mismatched phasing breaks dist-upgrades

2022-09-26 Thread Benjamin Drung
** Tags added: foundtations-todo

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

Title:
  22.04: python3* mismatched phasing breaks dist-upgrades

Status in apt package in Ubuntu:
  In Progress
Status in python3-defaults package in Ubuntu:
  Fix Released
Status in python3-stdlib-extensions package in Ubuntu:
  Fix Released
Status in python3.10 package in Ubuntu:
  Fix Released

Bug description:
  Impact
  --
  Users who manually run sudo apt dist-upgrade without paying attention can 
remove essential parts of their system

  Test Case
  -
  This test case won't work as well if phasing is set to 0% or 100%

  Create /etc/apt/apt.conf.d/phasing and set its contents to
  APT::Machine-ID 2c030cfce3b4487f9810f12a3ac6e87c;

  Then run

  sudo apt update
  sudo apt dist-upgrade

  Workaround In Advance
  -
  Don't run sudo apt dist-upgrade. Just run sudo apt upgrade
  Or use Update Manager or the Ubuntu Store to apply updates

  Workaround Afterwards
  -
  Fortunately, apt phasing is ignored for new package installs. So to get your 
Ubuntu Desktop back, just run

  sudo apt install ubuntu-desktop

  Other Info
  --
  These 3 updates were published today:
  python3-stdlib-extensions
  python3-defaults
  python3.10

  Suggested Fix
  -
  Fully phase those 3 source packages to 100%

  Apt Output
  --
  The following packages were automatically installed and are no longer 
required:
    apg apport-symptoms aptdaemon-data avahi-utils cups-pk-helper distro-info 
gdb gedit-common genisoimage gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 
gir1.2-goa-1.0 gir1.2-gst-plugins-base-1.0
    gir1.2-gtksource-4 gir1.2-gudev-1.0 gir1.2-notify-0.7 
gir1.2-packagekitglib-1.0 gir1.2-rb-3.0 gir1.2-secret-1 gir1.2-snapd-1 
gir1.2-totem-1.0 gir1.2-totemplparser-1.0 gir1.2-udisks-2.0
    gir1.2-unity-7.0 gir1.2-vte-2.91 gir1.2-wnck-3.0 gnome-control-center-faces 
gnome-software-common gnome-terminal-data hplip-data ibus-data ibus-gtk4 
libbabeltrace1 libboost-regex1.74.0
    libc6-dbg libcolord-gtk1 libdebuginfod-common libdebuginfod1 
libdmapsharing-3.0-2 libglu1-mesa libgpod-common libgpod4 libgsound0 
libgssdp-1.2-0 libgupnp-1.2-1 libgupnp-av-1.0-3
    libgupnp-dlna-2.0-4 libhpmud0 libimagequant0 libipt2 liblirc-client0 
libmalcontent-0-0 libnetplan0 libraqm0 librsync2 librygel-core-2.6-2 
librygel-db-2.6-2 librygel-renderer-2.6-2
    librygel-server-2.6-2 libsane-hpaio libsgutils2-2 
libsource-highlight-common libsource-highlight4v5 libwhoopsie-preferences0 
libwnck-3-0 libwnck-3-common libxatracker2 libxres1 libxss1
    libxvmc1 mobile-broadband-provider-info network-manager-gnome patch 
printer-driver-hpcups printer-driver-postscript-hp python-apt-common 
python3-blinker python3-certifi python3-cffi-backend
    python3-chardet python3-click python3-colorama python3-cryptography 
python3-dateutil python3-debconf python3-debian python3-defer 
python3-distro-info python3-fasteners python3-future
    python3-httplib2 python3-idna python3-importlib-metadata python3-jeepney 
python3-jwt python3-keyring python3-launchpadlib python3-lazr.restfulclient 
python3-lazr.uri python3-lockfile
    python3-louis python3-monotonic python3-more-itertools python3-oauthlib 
python3-olefile python3-pexpect python3-pkg-resources python3-problem-report 
python3-ptyprocess python3-pyparsing
    python3-requests python3-rfc3339 python3-secretstorage python3-six 
python3-tz python3-urllib3 python3-wadllib python3-xkit python3-zipp rygel 
whoopsie-preferences x11-apps x11-session-utils
    xbitmaps xbrlapi xcvt xfonts-scalable xinit xinput xserver-xorg-core 
xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-input-wacom 
xserver-xorg-video-all
    xserver-xorg-video-amdgpu xserver-xorg-video-ati xserver-xorg-video-fbdev 
xserver-xorg-video-intel xserver-xorg-video-nouveau xserver-xorg-video-qxl 
xserver-xorg-video-radeon
    xserver-xorg-video-vesa xserver-xorg-video-vmware
  Use 'sudo apt autoremove' to remove them.
  The following packages will be REMOVED:
    apport apport-gtk aptdaemon apturl apturl-common command-not-found deja-dup 
duplicity gedit gnome-control-center gnome-online-accounts gnome-software 
gnome-software-plugin-snap gnome-terminal
    hplip ibus ibus-table language-selector-common language-selector-gnome 
nautilus-extension-gnome-terminal nautilus-share netplan.io networkd-dispatcher 
orca python3-apport python3-apt
    python3-aptdaemon python3-aptdaemon.gtk3widgets python3-bcrypt 
python3-brlapi python3-cairo python3-commandnotfound python3-cups 
python3-cupshelpers python3-dbus python3-distupgrade
    python3-gi python3-gi-cairo python3-ibus-1.0 python3-macaroonbakery 
python3-mako python3-markupsafe python3-nacl python3-netifaces python3-paramiko 
python3-pil python3-protobuf
    python3-pyatspi python3-pymacaroons 

[Touch-packages] [Bug 1990293] Re: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 )

2022-09-26 Thread Benjamin Drung
** Description changed:

  Hi , when i delete a file where is in another partition than " / " or
  mounted in /media/ , i obtain the message in title.
  
  how can i use trash again please ?
  
  iznobe@iznobe-PC:~$ cat /etc/fstab
  # /etc/fstab: static file system information.
  #
  # Use 'blkid' to print the universally unique identifier for a
  # device; this may be used with UUID= as a more robust way to name devices
  # that works even if disks are added and removed. See fstab(5).
  #
  # 
 
  # / was on /dev/nvme0n1p2 during installation
  UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e /   ext4
noatime,errors=remount-ro   0   1
  
  # /boot/efi was on /dev/nvme0n1p1 during installation
  UUID=C071-9050/boot/efi   
vfatdefaults0   0
  
  # swap was on /dev/sdc3 during installation
  UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap
sw,pri=10   0
  
  # partition de données separée comune aux OS linux
  UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas  ext4
defaults0   0
  LABEL=WD8 /Vidéos/WD8 ext4
defaults0   0
  #/dev/disk/by-label/WD8PRO2  /media/WD8PRO2 ext4  
  defaults0   0
  
  LABEL=WD8PRO2   /Vidéos/WD8PRO2
  ext4defaults 0   0
  
  LABEL=WD8PRO1 /media/WD8PRO1  ext4
defaults0   0
  LABEL=Seagate_4T  /media/Seagate_4T   ext4
defaults,noauto 0   0
  
  trash is working for filesysteme mounted on /media/WD8PRO1 but not in FS
  mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS .
  
  Exactly same file systeme mounted on same directory , with same trash
  directory is working fine on ubuntu 20.04
+ 
+ [Workaround]
+ 
+ Rename the mount point to not include non-ASCII characters.

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

Title:
  Cannot move file to trash, do you want to delete immediately?" on EXT4
  partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on
  ubuntu 20.04 )

Status in glib2.0 package in Ubuntu:
  Triaged
Status in glib2.0 source package in Jammy:
  New

Bug description:
  Hi , when i delete a file where is in another partition than " / " or
  mounted in /media/ , i obtain the message in title.

  how can i use trash again please ?

  iznobe@iznobe-PC:~$ cat /etc/fstab
  # /etc/fstab: static file system information.
  #
  # Use 'blkid' to print the universally unique identifier for a
  # device; this may be used with UUID= as a more robust way to name devices
  # that works even if disks are added and removed. See fstab(5).
  #
  # 
 
  # / was on /dev/nvme0n1p2 during installation
  UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e /   ext4
noatime,errors=remount-ro   0   1

  # /boot/efi was on /dev/nvme0n1p1 during installation
  UUID=C071-9050/boot/efi   
vfatdefaults0   0

  # swap was on /dev/sdc3 during installation
  UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap
sw,pri=10   0

  # partition de données separée comune aux OS linux
  UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas  ext4
defaults0   0
  LABEL=WD8 /Vidéos/WD8 ext4
defaults0   0
  #/dev/disk/by-label/WD8PRO2  /media/WD8PRO2 ext4  
  defaults0   0

  LABEL=WD8PRO2   /Vidéos/WD8PRO2
  ext4defaults 0   0

  LABEL=WD8PRO1 /media/WD8PRO1  ext4
defaults0   0
  LABEL=Seagate_4T  /media/Seagate_4T   ext4
defaults,noauto 0   0

  trash is working for filesysteme mounted on /media/WD8PRO1 but not in
  FS mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS
  .

  Exactly same file systeme mounted on same directory , with same trash
  directory is working fine on ubuntu 20.04

  [Workaround]

  Rename the mount point to not include non-ASCII characters.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1990824] Re: initramfs-tools: out-of-memory failures during autopkgtest

2022-09-26 Thread Andrea Righi
All the initramfs-tools autopkgtest tests seem to run fine on a recent
kernel (5.19) with the debdiff in attach applied.

** Patch added: "initramfs-tools-increase-ram-2GB.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1990824/+attachment/5619021/+files/initramfs-tools-increase-ram-2GB.debdiff

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

Title:
  initramfs-tools: out-of-memory failures during autopkgtest

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  [Impact]

  Some autopkgtest tests are failing due to out-of-memory conditions,
  especially amd64-ata-only and net.

  It seems that we are creating a VM with 1GB only to run the amd64-ata-
  only test and even just 512MB for the net test.

  It probably makes sense to create larger VMs (at least 2GB) to run
  these tests with a more recent kernels (that will likely require a
  little more RAM).

  [Test case]

  sudo autopkgtest . -- null

  [Fix]

  Increase memory size of instances used to run the autopkgtests to 2GB.

  [Regression potential]

  We may experience regressions in small cloud instances, or systems
  with less than 2GB or RAM that are using a recent kernel (but this is
  more a generic potential regression, not strictly related to
  initramfs-tools).

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


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


[Touch-packages] [Bug 1990824] [NEW] initramfs-tools: out-of-memory failures during autopkgtest

2022-09-26 Thread Andrea Righi
Public bug reported:

[Impact]

Some autopkgtest tests are failing due to out-of-memory conditions,
especially amd64-ata-only and net.

It seems that we are creating a VM with 1GB only to run the amd64-ata-
only test and even just 512MB for the net test.

It probably makes sense to create larger VMs (at least 2GB) to run these
tests with a more recent kernels (that will likely require a little more
RAM).

[Test case]

sudo autopkgtest . -- null

[Fix]

Increase memory size of instances used to run the autopkgtests to 2GB.

[Regression potential]

We may experience regressions in small cloud instances, or systems with
less than 2GB or RAM that are using a recent kernel (but this is more a
generic potential regression, not strictly related to initramfs-tools).

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

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

Title:
  initramfs-tools: out-of-memory failures during autopkgtest

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  [Impact]

  Some autopkgtest tests are failing due to out-of-memory conditions,
  especially amd64-ata-only and net.

  It seems that we are creating a VM with 1GB only to run the amd64-ata-
  only test and even just 512MB for the net test.

  It probably makes sense to create larger VMs (at least 2GB) to run
  these tests with a more recent kernels (that will likely require a
  little more RAM).

  [Test case]

  sudo autopkgtest . -- null

  [Fix]

  Increase memory size of instances used to run the autopkgtests to 2GB.

  [Regression potential]

  We may experience regressions in small cloud instances, or systems
  with less than 2GB or RAM that are using a recent kernel (but this is
  more a generic potential regression, not strictly related to
  initramfs-tools).

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


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


[Touch-packages] [Bug 1990387] Re: FFE: Mesa 22.2.0

2022-09-26 Thread Graham Inggs
Considering this adds hardware support and Kinetic is an interim
release, and the (accidental) testing it's already had in Debian, FFe
granted, please go ahead.

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  FFE: Mesa 22.2.0

Status in mesa package in Ubuntu:
  Triaged

Bug description:
  Mesa 22.2.0 was released yesterday, a month late. This is an important
  release which brings support for AMD RDNA3 (together with llvm-15),
  Intel Arc (aka DG2) etc.

  Debian unstable has had 22.2.0-rc's since the start, because it was
  mistakenly uploaded there.. anyway, there was only one regression
  filed for x86 which is now fixed. Another one is for aarch64/virtio
  (Debian bug 1020391) and is unclear at this point if it's fixed by the
  final version or not.

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


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


  1   2   >