[Desktop-packages] [Bug 2062090] [NEW] background colour tool not working

[themusicgod1]

Public bug reported:

(although it seems similar to #1427346 it does seem to be a different
bug)

steps to reproduce
1) open new spreadsheet
2) type something in first cell
3) click on the 'background colour' dropdown, select a colour (from libreoffice 
pallet, say red) 
4) click on 'background colour' ie to make that cell that colour (say red)

what should happen:

the cell background should turn red

what does happen:

nothing

libreoffice-calc:
  Installed: 1:7.3.7-0ubuntu0.22.04.4
  Candidate: 1:7.3.7-0ubuntu0.22.04.4
  Version table:
 *** 1:7.3.7-0ubuntu0.22.04.4 500
500 http://muug.ca/mirror/ubuntu jammy-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
100 /var/lib/dpkg/status
 1:7.3.2-0ubuntu2 500
500 http://muug.ca/mirror/ubuntu jammy/main amd64 Packages

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.4 LTS"

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libreoffice-calc 1:7.3.7-0ubuntu0.22.04.4
Uname: Linux 6.0.7-gnulibre-squashfix x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 17 18:57:53 2024
InstallationDate: Installed on 2017-04-18 (2556 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: libreoffice
UpgradeStatus: Upgraded to jammy on 2023-06-14 (308 days ago)
mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/2062090

Title:
  background colour tool not working

Status in libreoffice package in Ubuntu:
  New

Bug description:
  (although it seems similar to #1427346 it does seem to be a different
  bug)

  steps to reproduce
  1) open new spreadsheet
  2) type something in first cell
  3) click on the 'background colour' dropdown, select a colour (from 
libreoffice pallet, say red) 
  4) click on 'background colour' ie to make that cell that colour (say red)

  what should happen:

  the cell background should turn red

  what does happen:

  nothing

  libreoffice-calc:
Installed: 1:7.3.7-0ubuntu0.22.04.4
Candidate: 1:7.3.7-0ubuntu0.22.04.4
Version table:
   *** 1:7.3.7-0ubuntu0.22.04.4 500
  500 http://muug.ca/mirror/ubuntu jammy-updates/main amd64 Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.3.2-0ubuntu2 500
  500 http://muug.ca/mirror/ubuntu jammy/main amd64 Packages

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=22.04
  DISTRIB_CODENAME=jammy
  DISTRIB_DESCRIPTION="Ubuntu 22.04.4 LTS"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice-calc 1:7.3.7-0ubuntu0.22.04.4
  Uname: Linux 6.0.7-gnulibre-squashfix x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 17 18:57:53 2024
  InstallationDate: Installed on 2017-04-18 (2556 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to jammy on 2023-06-14 (308 days ago)
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Desktop-packages] [Bug 2017447] Re: chromium installs cupsd snap

[themusicgod1]

Given Birgit Edel's comment this i'm flipping it back to "New".

** Changed in: chromium-browser (Ubuntu)
   Status: Opinion => New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2017447

Title:
  chromium installs cupsd snap

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  at some point, chromium has installed cupsd : cupsd isn't listed as
  installed in aptitude but it *is* listed under snap list

  if i wanted cups installed and printer support i would have installed
  it myself this shouldn't be installing itself through the backdoor via
  autoupdate

  there also doesn't seem to be anywhere in settings to turn it off

  Version 112.0.5615.49 (Official Build) snap (64-bit)
  (updated via snap refresh)
  ubuntu: 20.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Uname: Linux 6.0.7-gnulibre-squashfix x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 23 13:58:18 2023
  InstallationDate: Installed on 2017-04-18 (2196 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Snap: chromium 112.0.5615.49 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: Upgraded to focal on 2020-04-25 (1093 days ago)
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017447/+subscriptions


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

[Desktop-packages] [Bug 2035220] Re: cve-2023-4863

[themusicgod1]

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

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

** Also affects: firefox-esr (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2035220

Title:
  cve-2023-4863

Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  New
Status in firefox-esr package in Ubuntu:
  New
Status in libwebp package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in chromium package in Debian:
  New
Status in libwebp package in Debian:
  New

Bug description:
  [$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported 
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at 
The University of Torontoʼs Munk School on 2023-09-06
  
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html

  high profile remote vulnerability

  themusicgod1@eva1:~$ apt-cache policy chromium-browser
  chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:

  current available snap: 
  chromium 116.0.5845.179 

  fix is in:
  chromium 116.0.5845.187

  ubuntu: 22.04.3 LTS jammy

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 12 08:38:06 2023
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sda2  ext4   228G  162G   55G  75% /
   tmpfs  tmpfs  3.9G   66M  3.8G   2% /dev/shm
   /dev/sda2  ext4   228G  162G   55G  75% /
  InstallationDate: Installed on 2017-04-18 (2337 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7994
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
  Snap.Changes: no changes found
  Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179 
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
  Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
  dmi.bios.date: 12/16/2016
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.80
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M GAMING (MS-7994)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7994
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2035220/+subscriptions


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

[Desktop-packages] [Bug 2035238] Re: Trace/breakpoint trap (core dumped)

[themusicgod1]

sudo snap refresh got it working

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2035238

Title:
  Trace/breakpoint trap (core dumped)

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  fresh install

  running chromium on the terminal results in:

  /snap/chromium/2572/gnome-platform/command-chain/desktop-launch: line 52: 
/home/themusicgod1/.config/user-dirs.dirs: Permission denied
  sed: can't read /home/themusicgod1/.config/user-dirs.dirs: Permission denied
  /snap/chromium/2572/gnome-platform/command-chain/desktop-launch: line 269: 
/home/themusicgod1/.config/user-dirs.dirs: Permission denied
  cp: cannot open '/home/themusicgod1/.config/user-dirs.locale' for reading: 
Permission denied
  /snap/chromium/2572/gnome-platform/command-chain/desktop-launch: line 274: 
/home/themusicgod1/.config/user-dirs.locale: Permission denied
  Failed to move to new namespace: PID namespaces supported, Network namespace 
supported, but failed: errno = Operation not permitted
  [35914:35914:0912/103035.155665:FATAL:zygote_host_impl_linux.cc(201)] Check 
failed: . : No such file or directory (2)
  [0912/103035.194852:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not 
permitted (1)
  Trace/breakpoint trap (core dumped)

  chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu3
Candidate: 1:85.0.4183.83-0ubuntu3
Version table:
   *** 1:85.0.4183.83-0ubuntu3 500
  500 http://muug.ca/mirror/ubuntu mantic/universe amd64 Packages
  100 /var/lib/dpkg/statusthemusicgod1@fatima:~$ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=23.10
  DISTRIB_CODENAME=mantic
  DISTRIB_DESCRIPTION="Ubuntu Mantic Minotaur (development branch)"

  
  themusicgod1@fatima:~$ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=23.10
  DISTRIB_CODENAME=mantic
  DISTRIB_DESCRIPTION="Ubuntu Mantic Minotaur (development branch)"

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Tue Sep 12 10:43:34 2023
  InstallationDate: Installed on 2023-07-29 (45 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RebootRequiredPkgs: Error: path contained symlinks.
  Snap: chromium 116.0.5845.179 (latest/stable)
  SnapChanges:
   ID   Status  Spawn  Ready  Summary
   30   Done2023-09-12T09:55:45-06:00  2023-09-12T09:55:56-06:00  Connect 
chromium:password-manager-service to snapd:password-manager-service
   31   Done2023-09-12T10:32:20-06:00  2023-09-12T10:39:11-06:00  Refresh 
snaps "chromium", "core20", "firefox", "snapd"
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: Upgraded to mantic on 2023-08-01 (42 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2035238/+subscriptions


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

[Desktop-packages] [Bug 2035238] [NEW] Trace/breakpoint trap (core dumped)

[themusicgod1]

Public bug reported:

fresh install

running chromium on the terminal results in:

/snap/chromium/2572/gnome-platform/command-chain/desktop-launch: line 52: 
/home/themusicgod1/.config/user-dirs.dirs: Permission denied
sed: can't read /home/themusicgod1/.config/user-dirs.dirs: Permission denied
/snap/chromium/2572/gnome-platform/command-chain/desktop-launch: line 269: 
/home/themusicgod1/.config/user-dirs.dirs: Permission denied
cp: cannot open '/home/themusicgod1/.config/user-dirs.locale' for reading: 
Permission denied
/snap/chromium/2572/gnome-platform/command-chain/desktop-launch: line 274: 
/home/themusicgod1/.config/user-dirs.locale: Permission denied
Failed to move to new namespace: PID namespaces supported, Network namespace 
supported, but failed: errno = Operation not permitted
[35914:35914:0912/103035.155665:FATAL:zygote_host_impl_linux.cc(201)] Check 
failed: . : No such file or directory (2)
[0912/103035.194852:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not 
permitted (1)
Trace/breakpoint trap (core dumped)

chromium-browser:
  Installed: 1:85.0.4183.83-0ubuntu3
  Candidate: 1:85.0.4183.83-0ubuntu3
  Version table:
 *** 1:85.0.4183.83-0ubuntu3 500
500 http://muug.ca/mirror/ubuntu mantic/universe amd64 Packages
100 /var/lib/dpkg/statusthemusicgod1@fatima:~$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=23.10
DISTRIB_CODENAME=mantic
DISTRIB_DESCRIPTION="Ubuntu Mantic Minotaur (development branch)"


themusicgod1@fatima:~$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=23.10
DISTRIB_CODENAME=mantic
DISTRIB_DESCRIPTION="Ubuntu Mantic Minotaur (development branch)"

ProblemType: Bug
DistroRelease: Ubuntu 23.10
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: Budgie:GNOME
Date: Tue Sep 12 10:43:34 2023
InstallationDate: Installed on 2023-07-29 (45 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
RebootRequiredPkgs: Error: path contained symlinks.
Snap: chromium 116.0.5845.179 (latest/stable)
SnapChanges:
 ID   Status  Spawn  Ready  Summary
 30   Done2023-09-12T09:55:45-06:00  2023-09-12T09:55:56-06:00  Connect 
chromium:password-manager-service to snapd:password-manager-service
 31   Done2023-09-12T10:32:20-06:00  2023-09-12T10:39:11-06:00  Refresh 
snaps "chromium", "core20", "firefox", "snapd"
SnapSource: ubuntu/+source/chromium-browser
UpgradeStatus: Upgraded to mantic on 2023-08-01 (42 days ago)

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug mantic snap

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2035238

Title:
  Trace/breakpoint trap (core dumped)

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  fresh install

  running chromium on the terminal results in:

  /snap/chromium/2572/gnome-platform/command-chain/desktop-launch: line 52: 
/home/themusicgod1/.config/user-dirs.dirs: Permission denied
  sed: can't read /home/themusicgod1/.config/user-dirs.dirs: Permission denied
  /snap/chromium/2572/gnome-platform/command-chain/desktop-launch: line 269: 
/home/themusicgod1/.config/user-dirs.dirs: Permission denied
  cp: cannot open '/home/themusicgod1/.config/user-dirs.locale' for reading: 
Permission denied
  /snap/chromium/2572/gnome-platform/command-chain/desktop-launch: line 274: 
/home/themusicgod1/.config/user-dirs.locale: Permission denied
  Failed to move to new namespace: PID namespaces supported, Network namespace 
supported, but failed: errno = Operation not permitted
  [35914:35914:0912/103035.155665:FATAL:zygote_host_impl_linux.cc(201)] Check 
failed: . : No such file or directory (2)
  [0912/103035.194852:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not 
permitted (1)
  Trace/breakpoint trap (core dumped)

  chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu3
Candidate: 1:85.0.4183.83-0ubuntu3
Version table:
   *** 1:85.0.4183.83-0ubuntu3 500
  500 http://muug.ca/mirror/ubuntu mantic/universe amd64 Packages
  100 /var/lib/dpkg/statusthemusicgod1@fatima:~$ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=23.10
  DISTRIB_CODENAME=mantic
  DISTRIB_DESCRIPTION="Ubuntu Mantic Minotaur (development branch)"

  
  themusicgod1@fatima:~$ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=23.10
  DISTRIB_CODENAME=mantic
  DISTRIB_DESCRIPTION="Ubuntu Mantic Minotaur (development branch)"

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion:

[Desktop-packages] [Bug 1959848] Re: "_" not accepted within email addresses for copying

[themusicgod1]

** Tags added: jammy

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1959848

Title:
  "_" not accepted within email addresses for copying

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  step 1) hover the mouse over an email address with an _ in it like
  test_emai...@sharklasers.com

  2) 
  what happens

  only the part after the last _ is underlined (eg 1...@sharklasers.com )

  what should happen

  the whole email should be underlined (eg test_emai...@sharklasers.com
  )

  gnome-terminal: 3.36.1.1-1ubuntu1
  ubuntu 20.04 focal
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-04-18 (1751 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: gnome-terminal 3.36.1.1-1ubuntu1jeff2 [origin: unknown]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Tags: third-party-packages focal
  Uname: Linux 4.15.0-45-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: Upgraded to focal on 2020-04-25 (648 days ago)
  UserGroups: adm audio debian-tor docker
  _MarkForUpload: True
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Desktop-packages] [Bug 2017011] Re: [snap] unable to read /proc/pressure/{cpu, io, memory}

[themusicgod1]

** Tags added: jammy

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2017011

Title:
  [snap] unable to read /proc/pressure/{cpu,io,memory}

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  During normal operation, chromium wants to read
  /proc/pressure/{cpu,io,memory} but is denied by the Apparmor policy:

  $ journalctl -b0 -k --grep 'chromium.chromium' | grep -F 
'name="/proc/pressure/'
  Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400 
audit(1681915227.726:817): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=395005 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400 
audit(1681915227.726:818): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/io" pid=395005 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400 
audit(1681915227.726:819): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=395005 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  Note that simply starting the browser doesn't prompt it try and read
  those files, you need to do something more involving like watching
  Youtube for example.

  Additional information:

  $ snap list chromium core20
  Name  VersionRev   Tracking   Publisher   Notes
  chromium  112.0.5615.49  2424  latest/stable  canonical✓  -
  core2020230308   1852  latest/stable  canonical✓  base

  $ lsb_release -rd
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04

  $ uname -a
  Linux sdeziel-lemur 5.19.0-40-generic #41~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 
Fri Mar 31 16:00:14 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017011/+subscriptions


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

[Desktop-packages] [Bug 1875019] Re: ftbfs: Test failed: Basic functionality with the bind-mounted cache dir

[themusicgod1]

** Tags added: jammy

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1875019

Title:
  ftbfs:  Test failed: Basic functionality with the bind-mounted cache
  dir

Status in fontconfig package in Ubuntu:
  New

Bug description:
  1) apt-src install fontconfig
  2) cd fontconfig-2.13.1/
  3) debuild -us -uc -b

  gets to

  PASS: test-hash
  PASS: test-bz106632
  FAIL: run-test.sh
  
 fontconfig 2.13.1: test/test-suite.log
  

  # TOTAL: 7
  # PASS:  6
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0

  .. contents:: :depth: 2

  FAIL: run-test
  ==

  Running: Basic check
  Running: With a subdir
  Running: Subdir with a cache file
  Running: Complicated directory structure
  Running: Subdir with an out-of-date cache file
  Running: Dir with an out-of-date cache file
  Running: Re-creating .uuid
  Running: Consistency between .uuid and cache name
  
b41b6931-2503-44dd-a5d0-465a2c171511/home/z/fontconfig-2.13.1/test/cache.dir/08acdce6-36bc-4684-9a7b-0f24192abc6b-le64.cache-7
  Running: Keep mtime of the font directory
  Running: Basic functionality with the bind-mounted cache dir
  *** Test failed: Basic functionality with the bind-mounted cache dir
  cache was updated.
  FAIL run-test.sh (exit status: 1)

  
  ubuntu: focal 20.04 LTS
  fontconfig1: fontconfig:
Installed: 2.13.1-2ubuntu3
Candidate: 2.13.1-2ubuntu3
Version table:
   *** 2.13.1-2ubuntu3 500
  500 http://speglar.simnet.is/ubuntu focal/main amd64 Packages
  500 http://ubuntu.hysing.is/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: fontconfig 2.13.1-2ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Apr 25 13:15:14 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fontconfig
  UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago)

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


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

[Desktop-packages] [Bug 2023920] Re: cheese doesn't open after upgrade to 22.04

[themusicgod1]

how did this get assigned to "linux"? might be an apport bug

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cheese in Ubuntu.
https://bugs.launchpad.net/bugs/2023920

Title:
  cheese doesn't open after upgrade to 22.04

Status in cheese package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  current behaviour: when 'cheese' is run either via commandline or by
  search, either with -f or without, with webcam plugged in or not, it
  fails to bring up a cheese window

  this is what id displayed on the console:
  themusicgod1@eva1:~$ cheese -f

  ** (cheese:9307): WARNING **: 13:42:43.833: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.833: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  expected behavior: cheese should load as it did in 20.04

  what should happen: cheese runs

  ubuntu: 22.04 LTS
  Bus 001 Device 005: ID 046d:08c1 Logitech, Inc. QuickCam Fusion
  themusicgod1@eva1:~$ apt-cache policy cheese
  cheese:
Installed: 41.1-1build1
Candidate: 41.1-1build1
Version table:
   *** 41.1-1build1 500
  500 http://muug.ca/mirror/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome 42.5
  windowing system: wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  Uname: Linux 6.0.7-gnulibre-squashfix x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 14 13:40:09 2023
  InstallationDate: Installed on 2017-04-18 (2248 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7994
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2023-06-14 (0 days ago)
  dmi.bios.date: 12/16/2016
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.80
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M GAMING (MS-7994)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7994
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Desktop-packages] [Bug 2023920] Re: cheese doesn't open after upgrade to 22.04

[themusicgod1]

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cheese in Ubuntu.
https://bugs.launchpad.net/bugs/2023920

Title:
  cheese doesn't open after upgrade to 22.04

Status in cheese package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  current behaviour: when 'cheese' is run either via commandline or by
  search, either with -f or without, with webcam plugged in or not, it
  fails to bring up a cheese window

  this is what id displayed on the console:
  themusicgod1@eva1:~$ cheese -f

  ** (cheese:9307): WARNING **: 13:42:43.833: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.833: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  expected behavior: cheese should load as it did in 20.04

  what should happen: cheese runs

  ubuntu: 22.04 LTS
  Bus 001 Device 005: ID 046d:08c1 Logitech, Inc. QuickCam Fusion
  themusicgod1@eva1:~$ apt-cache policy cheese
  cheese:
Installed: 41.1-1build1
Candidate: 41.1-1build1
Version table:
   *** 41.1-1build1 500
  500 http://muug.ca/mirror/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome 42.5
  windowing system: wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  Uname: Linux 6.0.7-gnulibre-squashfix x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 14 13:40:09 2023
  InstallationDate: Installed on 2017-04-18 (2248 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7994
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2023-06-14 (0 days ago)
  dmi.bios.date: 12/16/2016
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.80
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M GAMING (MS-7994)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7994
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Desktop-packages] [Bug 508618] Re: Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp

[themusicgod1]

** Changed in: emacs25 (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs24 in Ubuntu.
https://bugs.launchpad.net/bugs/508618

Title:
  Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp

Status in emacs23 package in Ubuntu:
  New
Status in emacs24 package in Ubuntu:
  New
Status in emacs25 package in Ubuntu:
  Fix Released
Status in emacs25 package in Debian:
  New

Bug description:
  Binary package hint: emacs23

  Setting max-specpdl-size higher than 34295, and then running the following 
code results in a segfault of emacs.  I am 
  running a system of mostly 9.04 with some packages (such as this one) 
upgraded. I know it's kind of pushing emacs to the limit, but still;  this 
seems like an arbitrary limit on emacs' otherwise diety-like functionality.  
What should happen is emacs should continue to fail to execute with 
"file-truename: Variable binding depth exceeds max-specpdl-size"  as it does 
below 34295., or at the very least when setting max-specpdl-size higher than 
34295 it should warn you that you are making some kind of error if this is not 
acceptable.

  example code:

  (defun por (pcurrent pb numberleft)
 (if (= numberleft 0)
   pcurrent
   (por (- (+ pcurrent pb) (* pcurrent pb)) pb (- numberleft 1

  (por 0 0.01 1)

  (setq max-lisp-eval-depth 100)  ; this may be necessary, but doesn't 
appear to be the problem
  (setq max-specpdl-size 34295)  ; setting this lower results in 
predictable, expected behaviour - emacs refuses to run the result, citing 
max-specpdl-size not high enough.   Setting this higher (like...34296), results 
in a segfault of emacs

  emacs23:
Installé : 23.1+1-4ubuntu3
Candidat : 23.1+1-4ubuntu3
   Table de version :
   *** 23.1+1-4ubuntu3 0
  100 /var/lib/dpkg/status

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  Package: emacs23 23.1+1-4ubuntu3
  ProcEnviron:
   PATH=(custom, user)
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: emacs23
  Uname: Linux 2.6.28-16-generic x86_64
  UnreportableReason: Ceci n'est pas un authentique paquet Ubuntu

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


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

[Desktop-packages] [Bug 2017011] Re: [snap] unable to read /proc/pressure/{cpu, io, memory}

[themusicgod1]

** Tags added: focal

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2017011

Title:
  [snap] unable to read /proc/pressure/{cpu,io,memory}

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  During normal operation, chromium wants to read
  /proc/pressure/{cpu,io,memory} but is denied by the Apparmor policy:

  $ journalctl -b0 -k --grep 'chromium.chromium' | grep -F 
'name="/proc/pressure/'
  Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400 
audit(1681915227.726:817): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=395005 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400 
audit(1681915227.726:818): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/io" pid=395005 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400 
audit(1681915227.726:819): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=395005 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  Note that simply starting the browser doesn't prompt it try and read
  those files, you need to do something more involving like watching
  Youtube for example.

  Additional information:

  $ snap list chromium core20
  Name  VersionRev   Tracking   Publisher   Notes
  chromium  112.0.5615.49  2424  latest/stable  canonical✓  -
  core2020230308   1852  latest/stable  canonical✓  base

  $ lsb_release -rd
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04

  $ uname -a
  Linux sdeziel-lemur 5.19.0-40-generic #41~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 
Fri Mar 31 16:00:14 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017011/+subscriptions


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

[Desktop-packages] [Bug 2017447] [NEW] chromium installs cupsd snap

[themusicgod1]

Public bug reported:

at some point, chromium has installed cupsd : cupsd isn't listed as
installed in aptitude but it *is* listed under snap list

if i wanted cups installed and printer support i would have installed it
myself this shouldn't be installing itself through the backdoor via
autoupdate

there also doesn't seem to be anywhere in settings to turn it off

Version 112.0.5615.49 (Official Build) snap (64-bit)
(updated via snap refresh)
ubuntu: 20.04 LTS

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Uname: Linux 6.0.7-gnulibre-squashfix x86_64
ApportVersion: 2.20.11-0ubuntu27.26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 23 13:58:18 2023
InstallationDate: Installed on 2017-04-18 (2196 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Snap: chromium 112.0.5615.49 (latest/stable)
SnapSource: ubuntu/+source/chromium-browser
UpgradeStatus: Upgraded to focal on 2020-04-25 (1093 days ago)
mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal snap

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2017447

Title:
  chromium installs cupsd snap

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  at some point, chromium has installed cupsd : cupsd isn't listed as
  installed in aptitude but it *is* listed under snap list

  if i wanted cups installed and printer support i would have installed
  it myself this shouldn't be installing itself through the backdoor via
  autoupdate

  there also doesn't seem to be anywhere in settings to turn it off

  Version 112.0.5615.49 (Official Build) snap (64-bit)
  (updated via snap refresh)
  ubuntu: 20.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Uname: Linux 6.0.7-gnulibre-squashfix x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 23 13:58:18 2023
  InstallationDate: Installed on 2017-04-18 (2196 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Snap: chromium 112.0.5615.49 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: Upgraded to focal on 2020-04-25 (1093 days ago)
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017447/+subscriptions


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

[Desktop-packages] [Bug 1945760] Re: Window manager warning: WM_TRANSIENT_FOR window 0x56994b0 for 0x572b45a window override-redirect is an override-redirect window and this is not correct according t

[themusicgod1]

consistently get this when i right click in gnome-terminal and enter the
Profiles submenu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1945760

Title:
  Window manager warning: WM_TRANSIENT_FOR window 0x56994b0 for
  0x572b45a window override-redirect is an override-redirect window and
  this is not correct according to the standard, so we'll fallback to
  the first non-override-redirect window 0x560003f.

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Window manager warning: WM_TRANSIENT_FOR window 0x56994b0 for
  0x572b45a window override-redirect is an override-redirect window and
  this is not correct according to the standard, so we'll fallback to
  the first non-override-redirect window 0x560003f.

  Ubuntu 20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  Uname: Linux 5.13.0-9.1-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  1 10:48:53 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-06-28 (1190 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-12-05 (299 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-06-08T10:33:29.519300

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


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

[Desktop-packages] [Bug 2004095] [NEW] Unimplemented action: POPPLER_ACTION_JAVASCRIPT

[themusicgod1]

Public bug reported:

evince gives me a warning message :

** (evince:158186): WARNING **: 22:24:40.458: Unimplemented action:
POPPLER_ACTION_JAVASCRIPT, please post a bug report in Evince issue
tracker (https://gitlab.gnome.org/GNOME/evince/issues) with a testcase.


a whole bunch of times when i open the pdf of the following paper:

DOI:10.1161/CIRCULATIONAHA.122.061025

evince: 3.36.0-2 
ubuntu: 20.04 LTS

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: evince 3.36.0-2
Uname: Linux 6.0.7-gnulibre-squashfix x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 28 22:24:51 2023
InstallationDate: Installed on 2017-04-18 (2111 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: evince
UpgradeStatus: Upgraded to focal on 2020-04-25 (1008 days ago)
mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


** Tags: amd64 apparmor apport-bug focal

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/2004095

Title:
  Unimplemented action: POPPLER_ACTION_JAVASCRIPT

Status in evince package in Ubuntu:
  New

Bug description:
  evince gives me a warning message :

  ** (evince:158186): WARNING **: 22:24:40.458: Unimplemented action:
  POPPLER_ACTION_JAVASCRIPT, please post a bug report in Evince issue
  tracker (https://gitlab.gnome.org/GNOME/evince/issues) with a
  testcase.

  
  a whole bunch of times when i open the pdf of the following paper:

  DOI:10.1161/CIRCULATIONAHA.122.061025

  evince: 3.36.0-2 
  ubuntu: 20.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: evince 3.36.0-2
  Uname: Linux 6.0.7-gnulibre-squashfix x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 28 22:24:51 2023
  InstallationDate: Installed on 2017-04-18 (2111 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: evince
  UpgradeStatus: Upgraded to focal on 2020-04-25 (1008 days ago)
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Desktop-packages] [Bug 2003962] Re: chromium snap update makes system unresponsive, black screen

[themusicgod1]

root@eva1:/var/log# apt-cache policy xorg
xorg:
  Installed: 1:7.7+19ubuntu14
  Candidate: 1:7.7+19ubuntu14
  Version table:
 *** 1:7.7+19ubuntu14 500
500 http://muug.ca/mirror/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
Mesa Intel® HD Graphics 630 (KBL GT2)
gnome 3.36.1

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2003962

Title:
  chromium snap update makes system unresponsive, black screen

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Every day for the past few days I've been getting notification
  'pending update of chromium snap (n) days left'.  I noticed earlier
  that chromium seems to crash my system when it updates(at least it
  warns now so i can know it's doing it) - as in when i come back to log
  in after the update, to xorg/gnome, the caps lock doesn't turn on when
  pressed, and there's nothing but a black screen - ie the system is
  completely unresponsive.  tried hitting magic Sysrq+i to no avail.
  Had to hard reboot the system with the power button.

  system was working just fine last night at 1030pm, so whatever
  happened had to be after then is what did it:

  I just got another one saying 13 days left.

  from kern.log

  Jan 26 02:38:38 eva kernel: [2487580.958314] loop20: detected capacity change 
from 0 to 303936
  Jan 26 02:38:42 eva kernel: [2487585.064103] audit: type=1400 
audit(1674722322.852:26188): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="/snap/snapd/17950/usr/lib/snapd/snap-confine" pid=1586575 
comm="apparmor_parser"
  Jan 26 02:38:42 eva kernel: [2487585.064110] audit: type=1400 
audit(1674722322.852:26189): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="/snap/snapd/17950/usr/lib/snapd/snap-confine//mount-namespace-capture-helper"
 pid=1586575 comm="apparmor_parser"
  Jan 26 02:38:43 eva kernel: [2487585.240118] audit: type=1400 
audit(1674722323.028:26190): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="snap.chromium.hook.configure" pid=1586580 
comm="apparmor_parser"
  Jan 26 02:38:43 eva kernel: [2487585.933271] audit: type=1400 
audit(1674722323.721:26191): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="snap-update-ns.chromium" pid=1586577 
comm="apparmor_parser"
  Jan 26 02:38:43 eva kernel: [2487586.166852] audit: type=1400 
audit(1674722323.955:26192): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="snap.chromium.chromium" pid=1586579 
comm="apparmor_parser"
  Jan 26 02:38:43 eva kernel: [2487586.192853] audit: type=1400 
audit(1674722323.981:26193): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="snap.chromium.chromedriver" pid=1586578 
comm="apparmor_parser"
  Jan 26 02:38:44 eva kernel: [2487586.321626] audit: type=1400 
audit(1674722324.110:26194): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="snap-update-ns.cups" pid=1586582 comm="apparmor_parser"
  Jan 26 02:38:44 eva kernel: [2487586.330187] audit: type=1400 
audit(1674722324.118:26195): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="snap.cups.cups-browsed" pid=1586585 comm="apparmor_parser"
  Jan 26 02:38:44 eva kernel: [2487586.330708] audit: type=1400 
audit(1674722324.119:26196): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="snap.cups.cancel" pid=1586584 comm="apparmor_parser"
  Jan 26 02:38:44 eva kernel: [2487586.336931] audit: type=1400 
audit(1674722324.125:26197): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="snap.cups.accept" pid=1586583 comm="apparmor_parser"

  nothing in syslog from 2:38am

  ubuntu 20.04 
  linux: custom kernel 6.0.7 with squashfs bug hotfix  
  ( but it's been crashing during snap updates since at least the 5.x )

  root@eva1:/var/log# apt-cache policy chromium-browser
  chromium-browser:
Installed: 80.0.3987.163-0ubuntu1
Candidate: 80.0.3987.163-0ubuntu1
Version table:
   *** 80.0.3987.163-0ubuntu1 500
  500 http://muug.ca/mirror/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

  actual version post update:
  Version 109.0.5414.74 (Official Build) snap (64-bit)

  which is different than the last time I saw it ( 103.0.5060.134 ) so
  it's clearly updating itself, which supports the idea that the snap is
  updating during the crash

  but it would be nice to not hard lock my whole desktop system every 2
  weeks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Uname: Linux 6.0.7-gnulibre-squashfix x86_64
  ApportVersion: 2.20.11-0ub

[Desktop-packages] [Bug 2003962] Re: chromium snap update makes system unresponsive, black screen

[themusicgod1]

themusicgod1@eva1:~$ snap changes
ID   Status  Spawn   Ready   Summary
228  Donetoday at 02:38 CST  today at 02:38 CST  Auto-refresh snap 
"chromium"

also supports that the update happened, and that the system was doing at
least something until 2:38:44am when the last kern.log entry was found

video driver: intel:
root@eva1:/var/log# lsmod | grep vid
video  61440  1 i915
backlight  24576  4 video,drm_display_helper,i915,drm

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2003962

Title:
  chromium snap update makes system unresponsive, black screen

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Every day for the past few days I've been getting notification
  'pending update of chromium snap (n) days left'.  I noticed earlier
  that chromium seems to crash my system when it updates(at least it
  warns now so i can know it's doing it) - as in when i come back to log
  in after the update, to xorg/gnome, the caps lock doesn't turn on when
  pressed, and there's nothing but a black screen - ie the system is
  completely unresponsive.  tried hitting magic Sysrq+i to no avail.
  Had to hard reboot the system with the power button.

  system was working just fine last night at 1030pm, so whatever
  happened had to be after then is what did it:

  I just got another one saying 13 days left.

  from kern.log

  Jan 26 02:38:38 eva kernel: [2487580.958314] loop20: detected capacity change 
from 0 to 303936
  Jan 26 02:38:42 eva kernel: [2487585.064103] audit: type=1400 
audit(1674722322.852:26188): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="/snap/snapd/17950/usr/lib/snapd/snap-confine" pid=1586575 
comm="apparmor_parser"
  Jan 26 02:38:42 eva kernel: [2487585.064110] audit: type=1400 
audit(1674722322.852:26189): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="/snap/snapd/17950/usr/lib/snapd/snap-confine//mount-namespace-capture-helper"
 pid=1586575 comm="apparmor_parser"
  Jan 26 02:38:43 eva kernel: [2487585.240118] audit: type=1400 
audit(1674722323.028:26190): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="snap.chromium.hook.configure" pid=1586580 
comm="apparmor_parser"
  Jan 26 02:38:43 eva kernel: [2487585.933271] audit: type=1400 
audit(1674722323.721:26191): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="snap-update-ns.chromium" pid=1586577 
comm="apparmor_parser"
  Jan 26 02:38:43 eva kernel: [2487586.166852] audit: type=1400 
audit(1674722323.955:26192): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="snap.chromium.chromium" pid=1586579 
comm="apparmor_parser"
  Jan 26 02:38:43 eva kernel: [2487586.192853] audit: type=1400 
audit(1674722323.981:26193): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="snap.chromium.chromedriver" pid=1586578 
comm="apparmor_parser"
  Jan 26 02:38:44 eva kernel: [2487586.321626] audit: type=1400 
audit(1674722324.110:26194): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="snap-update-ns.cups" pid=1586582 comm="apparmor_parser"
  Jan 26 02:38:44 eva kernel: [2487586.330187] audit: type=1400 
audit(1674722324.118:26195): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="snap.cups.cups-browsed" pid=1586585 comm="apparmor_parser"
  Jan 26 02:38:44 eva kernel: [2487586.330708] audit: type=1400 
audit(1674722324.119:26196): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="snap.cups.cancel" pid=1586584 comm="apparmor_parser"
  Jan 26 02:38:44 eva kernel: [2487586.336931] audit: type=1400 
audit(1674722324.125:26197): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="snap.cups.accept" pid=1586583 comm="apparmor_parser"

  nothing in syslog from 2:38am

  ubuntu 20.04 
  linux: custom kernel 6.0.7 with squashfs bug hotfix  
  ( but it's been crashing during snap updates since at least t

[Desktop-packages] [Bug 1850282] Re: snap cannot be run while being upgraded − no user feedback

[themusicgod1]

newer versions seem to at least warn the user that an upgrade is coming
and to not have chromium open during the upgrade

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1850282

Title:
  snap cannot be run while being upgraded − no user feedback

Status in snapd:
  In Progress
Status in chromium-browser package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I've just upgraded to Ubuntu 19.10 with the new snap version of
  Chromium a week or two ago

  On starting my system today, I found that Chromium had disappeared
  from the launcher and wasn't even in the apps list.   using the
  command 'chromium' didn't work either, giving me the message that
  chromium wasn't installed.   "You can install it using snap install
  chromium".  Then when I try to install it, I get the message "chromium
  is already installed".

  After about 10 minutes of digging around, I discovered that the
  chromium snap was disabled.  I couldn't enable it because it was being
  refreshed.

  Come on!  this is unacceptable behaviour for any tool but especially a
  browser which must be one of the most heavily used applications on
  Ubuntu.  This will really hit the reputation of ubuntu with any user
  who has to take maybe more than 10 minutes to discover the problem, or
  may never discover it - Chromium may just mysteriously reappear some
  time later.

  Desired behaviour:   Never disappear.  Allow refresh to happen under the 
covers, transparently (as it used to with apt).
  Minimally acceptable behaviour: never disappear, but display a message 
"chromium is being refreshed.  Please try later".

  $ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
An open-source browser project that aims to build a safer, faster, and more
stable way for all Internet users to experience the web.
  commands:
- chromium.chromedriver
- chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: stable
  channels:
stable:78.0.3904.70 2019-10-29 (920) 160MB -
candidate: 78.0.3904.70 2019-10-29 (920) 160MB -
beta:  78.0.3904.70 2019-10-22 (907) 165MB -
edge:  79.0.3941.4  2019-10-21 (905) 159MB -
  installed:   78.0.3904.70(917) 167MB disabled

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


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

[Desktop-packages] [Bug 2003962] [NEW] chromium snap update makes system unresponsive, black screen

[themusicgod1]

Public bug reported:

Every day for the past few days I've been getting notification 'pending
update of chromium snap (n) days left'.  I noticed earlier that chromium
seems to crash my system when it updates(at least it warns now so i can
know it's doing it) - as in when i come back to log in after the update,
to xorg/gnome, the caps lock doesn't turn on when pressed, and there's
nothing but a black screen - ie the system is completely unresponsive.
tried hitting magic Sysrq+i to no avail.  Had to hard reboot the system
with the power button.

system was working just fine last night at 1030pm, so whatever happened
had to be after then is what did it:

I just got another one saying 13 days left.

from kern.log

Jan 26 02:38:38 eva kernel: [2487580.958314] loop20: detected capacity change 
from 0 to 303936
Jan 26 02:38:42 eva kernel: [2487585.064103] audit: type=1400 
audit(1674722322.852:26188): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="/snap/snapd/17950/usr/lib/snapd/snap-confine" pid=1586575 
comm="apparmor_parser"
Jan 26 02:38:42 eva kernel: [2487585.064110] audit: type=1400 
audit(1674722322.852:26189): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="/snap/snapd/17950/usr/lib/snapd/snap-confine//mount-namespace-capture-helper"
 pid=1586575 comm="apparmor_parser"
Jan 26 02:38:43 eva kernel: [2487585.240118] audit: type=1400 
audit(1674722323.028:26190): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="snap.chromium.hook.configure" pid=1586580 
comm="apparmor_parser"
Jan 26 02:38:43 eva kernel: [2487585.933271] audit: type=1400 
audit(1674722323.721:26191): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="snap-update-ns.chromium" pid=1586577 
comm="apparmor_parser"
Jan 26 02:38:43 eva kernel: [2487586.166852] audit: type=1400 
audit(1674722323.955:26192): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="snap.chromium.chromium" pid=1586579 
comm="apparmor_parser"
Jan 26 02:38:43 eva kernel: [2487586.192853] audit: type=1400 
audit(1674722323.981:26193): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="snap.chromium.chromedriver" pid=1586578 
comm="apparmor_parser"
Jan 26 02:38:44 eva kernel: [2487586.321626] audit: type=1400 
audit(1674722324.110:26194): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="snap-update-ns.cups" pid=1586582 comm="apparmor_parser"
Jan 26 02:38:44 eva kernel: [2487586.330187] audit: type=1400 
audit(1674722324.118:26195): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="snap.cups.cups-browsed" pid=1586585 comm="apparmor_parser"
Jan 26 02:38:44 eva kernel: [2487586.330708] audit: type=1400 
audit(1674722324.119:26196): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="snap.cups.cancel" pid=1586584 comm="apparmor_parser"
Jan 26 02:38:44 eva kernel: [2487586.336931] audit: type=1400 
audit(1674722324.125:26197): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="snap.cups.accept" pid=1586583 comm="apparmor_parser"

nothing in syslog from 2:38am

ubuntu 20.04 
linux: custom kernel 6.0.7 with squashfs bug hotfix  
( but it's been crashing during snap updates since at least the 5.x )

root@eva1:/var/log# apt-cache policy chromium-browser
chromium-browser:
  Installed: 80.0.3987.163-0ubuntu1
  Candidate: 80.0.3987.163-0ubuntu1
  Version table:
 *** 80.0.3987.163-0ubuntu1 500
500 http://muug.ca/mirror/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status

actual version post update:
Version 109.0.5414.74 (Official Build) snap (64-bit)

which is different than the last time I saw it ( 103.0.5060.134 ) so
it's clearly updating itself, which supports the idea that the snap is
updating during the crash

but it would be nice to not hard lock my whole desktop system every 2
weeks.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Uname: Linux 6.0.7-gnulibre-squashfix x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 26 09:44:00 2023
InstallationDate: Installed on 2017-04-18 (2108 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Snap: chromium 109.0.5414.74 (latest/stable)
SnapSource: ubuntu/+source/chromium-browser
UpgradeStatus: Upgraded to focal on 2020-04-25 (1005 days ago)
mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal snap

-- 
You received this bug notification because you are a member of Desktop
Packages, which is su

[Desktop-packages] [Bug 1993008] [NEW] ftbfs: E: fontconfig: alien-tag fc-cache-used-in-maintainer-script

[themusicgod1]

Public bug reported:

When trying to build from source using

debuild -us -uc -b

the result errors out with

Now running lintian fontconfig_2.13.1-4.4ubuntu1_amd64.changes ...
E: fontconfig: alien-tag fc-cache-used-in-maintainer-script 
[usr/share/lintian/overrides/fontconfig:1]
W: libfontconfig-doc: bad-whatis-entry 
[usr/share/man/man3/FcPatternIterNext.3.gz]

from:
https://www.mit.edu/afs.new/sipb/project/debathena/lintian/www/tags/fc-cache-used-in-maintainer-script.html

"This script apparently runs fc-cache. Updating of the fontconfig cache files 
is now handled automatically by triggers, so running fc-cache from maintainer 
scripts is no longer necessary."
  
 
ubuntu: kinetic kudu

libfontconfig1-dev:
  Installed: 2.13.1-4.4ubuntu1
  Candidate: 2.13.1-4.4ubuntu1
  Version table:
 *** 2.13.1-4.4ubuntu1 500
500 http://ubuntu.hysing.is/ubuntu kinetic/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: libfontconfig-dev 2.13.1-4.4ubuntu1
Uname: Linux 6.0.1-gnulibre x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Fri Oct 14 21:07:42 2022
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: fontconfig
UpgradeStatus: Upgraded to kinetic on 2022-10-14 (0 days ago)

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


** Tags: amd64 apport-bug ftbfs kinetic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1993008

Title:
  ftbfs: E: fontconfig: alien-tag fc-cache-used-in-maintainer-script

Status in fontconfig package in Ubuntu:
  New

Bug description:
  When trying to build from source using

  debuild -us -uc -b

  the result errors out with

  Now running lintian fontconfig_2.13.1-4.4ubuntu1_amd64.changes ...
  E: fontconfig: alien-tag fc-cache-used-in-maintainer-script 
[usr/share/lintian/overrides/fontconfig:1]
  W: libfontconfig-doc: bad-whatis-entry 
[usr/share/man/man3/FcPatternIterNext.3.gz]

  from:
  
https://www.mit.edu/afs.new/sipb/project/debathena/lintian/www/tags/fc-cache-used-in-maintainer-script.html

  "This script apparently runs fc-cache. Updating of the fontconfig cache files 
is now handled automatically by triggers, so running fc-cache from maintainer 
scripts is no longer necessary."

   
  ubuntu: kinetic kudu

  libfontconfig1-dev:
Installed: 2.13.1-4.4ubuntu1
Candidate: 2.13.1-4.4ubuntu1
Version table:
   *** 2.13.1-4.4ubuntu1 500
  500 http://ubuntu.hysing.is/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: libfontconfig-dev 2.13.1-4.4ubuntu1
  Uname: Linux 6.0.1-gnulibre x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Oct 14 21:07:42 2022
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fontconfig
  UpgradeStatus: Upgraded to kinetic on 2022-10-14 (0 days ago)

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


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

[Desktop-packages] [Bug 1689381] Re: FTBFS cp: cannot stat 'doc/fontconfig-user.html'

[themusicgod1]

no longer fails on this in kinetic...( still ftbfs tho )

** Changed in: fontconfig (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1689381

Title:
  FTBFS cp: cannot stat 'doc/fontconfig-user.html'

Status in fontconfig package in Ubuntu:
  Fix Committed

Bug description:
  while attempting to build with debuild:

  debuild -us -uc -b
  ...
  Adding cdbs dependencies to debian/libfontconfig1-dbg.substvars
  dh_installdirs -plibfontconfig1-dbg \

  dh_installdocs -pfontconfig ./README ./NEWS ./AUTHORS
  cp: cannot stat 'doc/fontconfig-user.html': No such file or directory
  dh_installdocs: cp --reflink=auto -a doc/fontconfig-user.html 
debian/fontconfig/usr/share/doc/fontconfig returned exit code 1
  /usr/share/cdbs/1/rules/debhelper.mk:235: recipe for target 
'binary-install/fontconfig' failed
  make: *** [binary-install/fontconfig] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
2
  debuild: fatal error at line 1116:
  dpkg-buildpackage -rfakeroot -us -uc -b failed
  z@aisha:~/fontconfig/fontconfig-2.11.94/debian$ 

  ubuntu: 17.10 artful
  libfontconfig1-dev:  2.11.94-0ubuntu2

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libfontconfig1-dev (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Mon May  8 19:23:10 2017
  InstallationDate: Installed on 2016-05-07 (366 days ago)
  InstallationMedia:
   
  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.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fontconfig
  UpgradeStatus: Upgraded to artful on 2017-05-08 (0 days ago)

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


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

[Desktop-packages] [Bug 1991006] [NEW] gnome-screensaver locked pointer as a crosshair

[themusicgod1]

Public bug reported:

(i've seen it do this before but it only happens very rarely)

what should happen:

1) run gnome-screenshot
2) it presents a little window of which kind of screenshot you want to take
3) select 'select area to grab'
4) the pointer is replaced by a crosshair and you can't click on anything 
except with that crosshair to select an area
5) after you are done selecting an area, the screenshot is taken and the cursor 
is returned to normal along with its functionality

what happened instead:

5) the pointer got stuck in this crosshair (only on particular areas of
the screen though, the dock(?) and a couple other windows like
audacious.

ironically

ubuntu-bug got the pointer back into a pointer again
but it still seems stuck and unable to click on icons such as the screenshot 
shortcut icon, changing the active window (unless you click in a text field), 
dragging windows around (alt-tab still works)

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"
gnome-screenshot:
  Installed: 3.36.0-1ubuntu1
  Candidate: 3.36.0-1ubuntu1
  Version table:
 *** 3.36.0-1ubuntu1 500
500 http://muug.ca/mirror/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-screenshot 3.36.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
Uname: Linux 5.4.0-26-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 27 11:27:50 2022
InstallationDate: Installed on 2017-04-18 (1987 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: gnome-screenshot
UpgradeStatus: Upgraded to focal on 2020-04-25 (885 days ago)
mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screenshot in Ubuntu.
https://bugs.launchpad.net/bugs/1991006

Title:
  gnome-screensaver locked pointer as a crosshair

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  (i've seen it do this before but it only happens very rarely)

  what should happen:

  1) run gnome-screenshot
  2) it presents a little window of which kind of screenshot you want to take
  3) select 'select area to grab'
  4) the pointer is replaced by a crosshair and you can't click on anything 
except with that crosshair to select an area
  5) after you are done selecting an area, the screenshot is taken and the 
cursor is returned to normal along with its functionality

  what happened instead:

  5) the pointer got stuck in this crosshair (only on particular areas
  of the screen though, the dock(?) and a couple other windows like
  audacious.

  ironically

  ubuntu-bug got the pointer back into a pointer again
  but it still seems stuck and unable to click on icons such as the screenshot 
shortcut icon, changing the active window (unless you click in a text field), 
dragging windows around (alt-tab still works)

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"
  gnome-screenshot:
Installed: 3.36.0-1ubuntu1
Candidate: 3.36.0-1ubuntu1
Version table:
   *** 3.36.0-1ubuntu1 500
  500 http://muug.ca/mirror/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
  Uname: Linux 5.4.0-26-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 27 11:27:50 2022
  InstallationDate: Installed on 2017-04-18 (1987 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to focal on 2020-04-25 (885 days ago)
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Desktop-packages] [Bug 1689381] Re: FTBFS cp: cannot stat 'doc/fontconfig-user.html'

[themusicgod1]

** Tags added: jammy

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1689381

Title:
  FTBFS cp: cannot stat 'doc/fontconfig-user.html'

Status in fontconfig package in Ubuntu:
  New

Bug description:
  while attempting to build with debuild:

  debuild -us -uc -b
  ...
  Adding cdbs dependencies to debian/libfontconfig1-dbg.substvars
  dh_installdirs -plibfontconfig1-dbg \

  dh_installdocs -pfontconfig ./README ./NEWS ./AUTHORS
  cp: cannot stat 'doc/fontconfig-user.html': No such file or directory
  dh_installdocs: cp --reflink=auto -a doc/fontconfig-user.html 
debian/fontconfig/usr/share/doc/fontconfig returned exit code 1
  /usr/share/cdbs/1/rules/debhelper.mk:235: recipe for target 
'binary-install/fontconfig' failed
  make: *** [binary-install/fontconfig] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
2
  debuild: fatal error at line 1116:
  dpkg-buildpackage -rfakeroot -us -uc -b failed
  z@aisha:~/fontconfig/fontconfig-2.11.94/debian$ 

  ubuntu: 17.10 artful
  libfontconfig1-dev:  2.11.94-0ubuntu2

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libfontconfig1-dev (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Mon May  8 19:23:10 2017
  InstallationDate: Installed on 2016-05-07 (366 days ago)
  InstallationMedia:
   
  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.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fontconfig
  UpgradeStatus: Upgraded to artful on 2017-05-08 (0 days ago)

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


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

[Desktop-packages] [Bug 884122] Re: xclock -digital shows seconds but redraws on the minute

[themusicgod1]

seems like a simple enough fix, at the end of the day: just change the
default timeout to something sensible

** Patch added: "884122.patch"
   
https://bugs.launchpad.net/ubuntu/+source/x11-apps/+bug/884122/+attachment/5549213/+files/884122.patch

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to x11-apps in Ubuntu.
https://bugs.launchpad.net/bugs/884122

Title:
  xclock -digital shows seconds but redraws on the minute

Status in x11-apps package in Ubuntu:
  Confirmed

Bug description:
  i.e., on start it will show, e.g. "Mon 31 Oct 2011 09:17:15 GMT"
  (en_GB format), and stay that way for 45 seconds, then show "Mon 31
  Oct 2011 09:18:00 GMT" for a minute, etc.

  It redraws to show the correct time, including seconds, when the
  window is resized.  Window manager is Unity, version as of oneric-
  updates: 4.24.0-0ubuntu2b1 0.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: x11-apps 7.6+4ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  CheckboxSubmission: b0d31efda01870980e2e5a89390b685c
  CheckboxSystem: 6ce041aeed0a2c17b3343b66d157175d
  Date: Mon Oct 31 09:11:52 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  SourcePackage: x11-apps
  UpgradeStatus: Upgraded to oneiric on 2011-05-03 (181 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x11-apps/+bug/884122/+subscriptions


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

[Desktop-packages] [Bug 1953196] Re: gnome-terminal misreads a fediverse identifier as an email

[themusicgod1]

this patch works a little better, but still needs a fediverse client to
capture the 'send toot' case


** Patch added: "1953196.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1953196/+attachment/5549197/+files/1953196.patch

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1953196

Title:
  gnome-terminal misreads a fediverse identifier as an email

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  On the fediverse ( the free software social media network of networks
  - https://jointhefedi.com/ ) the identifier format is

  @username@hostname

  unlike email which is

  username@hostname

  What happens:

  if you have a fediverse user displayed in your terminal, gnome-
  terminal deduces that it is an email and if you right click it, you
  are given the option to 'Copy Mail Address' and 'Send Mail To' instead
  of just 'Copy'

  What should happen:

  You should, instead, be given the option to 'Copy Fedi Address' (and,
  better yet, optionally 'Send DM To') instead of just 'Copy'.  Possibly
  including the 'Copy Mail Address', for backwards compatibility

  ubuntu: 20.04 LTS focal

  gnome-terminal:
Installed: 3.36.1.1-1ubuntu1
Candidate: 3.36.1.1-1ubuntu1
Version table:
   *** 3.36.1.1-1ubuntu1 500
  500 http://muug.ca/mirror/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-terminal 3.36.1.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
  Uname: Linux 5.4.0-26-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  3 13:47:26 2021
  InstallationDate: Installed on 2017-04-18 (1690 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to focal on 2020-04-25 (587 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Desktop-packages] [Bug 1953196] Re: gnome-terminal misreads a fediverse identifier as an email

[themusicgod1]

** Patch added: "1953196.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1953196/+attachment/5549196/+files/1953196.patch

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1953196

Title:
  gnome-terminal misreads a fediverse identifier as an email

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  On the fediverse ( the free software social media network of networks
  - https://jointhefedi.com/ ) the identifier format is

  @username@hostname

  unlike email which is

  username@hostname

  What happens:

  if you have a fediverse user displayed in your terminal, gnome-
  terminal deduces that it is an email and if you right click it, you
  are given the option to 'Copy Mail Address' and 'Send Mail To' instead
  of just 'Copy'

  What should happen:

  You should, instead, be given the option to 'Copy Fedi Address' (and,
  better yet, optionally 'Send DM To') instead of just 'Copy'.  Possibly
  including the 'Copy Mail Address', for backwards compatibility

  ubuntu: 20.04 LTS focal

  gnome-terminal:
Installed: 3.36.1.1-1ubuntu1
Candidate: 3.36.1.1-1ubuntu1
Version table:
   *** 3.36.1.1-1ubuntu1 500
  500 http://muug.ca/mirror/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-terminal 3.36.1.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
  Uname: Linux 5.4.0-26-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  3 13:47:26 2021
  InstallationDate: Installed on 2017-04-18 (1690 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to focal on 2020-04-25 (587 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Desktop-packages] [Bug 1953196] Re: gnome-terminal misreads a fediverse identifier as an email

[themusicgod1]

So this patch actually *does* kind of work but only on the gnome-
terminal level (and includes some shotgun debugging).  Something deeper
needs to happen in order to actually make this work - ie bringing up a
fediverse client of some kind or a web browser if that's not available.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1953196

Title:
  gnome-terminal misreads a fediverse identifier as an email

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  On the fediverse ( the free software social media network of networks
  - https://jointhefedi.com/ ) the identifier format is

  @username@hostname

  unlike email which is

  username@hostname

  What happens:

  if you have a fediverse user displayed in your terminal, gnome-
  terminal deduces that it is an email and if you right click it, you
  are given the option to 'Copy Mail Address' and 'Send Mail To' instead
  of just 'Copy'

  What should happen:

  You should, instead, be given the option to 'Copy Fedi Address' (and,
  better yet, optionally 'Send DM To') instead of just 'Copy'.  Possibly
  including the 'Copy Mail Address', for backwards compatibility

  ubuntu: 20.04 LTS focal

  gnome-terminal:
Installed: 3.36.1.1-1ubuntu1
Candidate: 3.36.1.1-1ubuntu1
Version table:
   *** 3.36.1.1-1ubuntu1 500
  500 http://muug.ca/mirror/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-terminal 3.36.1.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
  Uname: Linux 5.4.0-26-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  3 13:47:26 2021
  InstallationDate: Installed on 2017-04-18 (1690 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to focal on 2020-04-25 (587 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Desktop-packages] [Bug 1953196] Re: gnome-terminal misreads a fediverse identifier as an email

[themusicgod1]

this doesn't work, though i'm not sure why.  it's mostly what I'm going
for though

** Patch added: "something.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1953196/+attachment/5547038/+files/something.patch

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1953196

Title:
  gnome-terminal misreads a fediverse identifier as an email

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  On the fediverse ( the free software social media network of networks
  - https://jointhefedi.com/ ) the identifier format is

  @username@hostname

  unlike email which is

  username@hostname

  What happens:

  if you have a fediverse user displayed in your terminal, gnome-
  terminal deduces that it is an email and if you right click it, you
  are given the option to 'Copy Mail Address' and 'Send Mail To' instead
  of just 'Copy'

  What should happen:

  You should, instead, be given the option to 'Copy Fedi Address' (and,
  better yet, optionally 'Send DM To') instead of just 'Copy'.  Possibly
  including the 'Copy Mail Address', for backwards compatibility

  ubuntu: 20.04 LTS focal

  gnome-terminal:
Installed: 3.36.1.1-1ubuntu1
Candidate: 3.36.1.1-1ubuntu1
Version table:
   *** 3.36.1.1-1ubuntu1 500
  500 http://muug.ca/mirror/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-terminal 3.36.1.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
  Uname: Linux 5.4.0-26-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  3 13:47:26 2021
  InstallationDate: Installed on 2017-04-18 (1690 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to focal on 2020-04-25 (587 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Desktop-packages] [Bug 1953196] [NEW] gnome-terminal misreads a fediverse identifier as an email

[themusicgod1]

Public bug reported:

On the fediverse ( the free software social media network of networks -
https://jointhefedi.com/ ) the identifier format is

@username@hostname

unlike email which is

username@hostname

What happens:

if you have a fediverse user displayed in your terminal, gnome-terminal
deduces that it is an email and if you right click it, you are given the
option to 'Copy Mail Address' and 'Send Mail To' instead of just 'Copy'

What should happen:

You should, instead, be given the option to 'Copy Fedi Address' (and,
better yet, optionally 'Send DM To') instead of just 'Copy'.  Possibly
including the 'Copy Mail Address', for backwards compatibility

ubuntu: 20.04 LTS focal

gnome-terminal:
  Installed: 3.36.1.1-1ubuntu1
  Candidate: 3.36.1.1-1ubuntu1
  Version table:
 *** 3.36.1.1-1ubuntu1 500
500 http://muug.ca/mirror/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-terminal 3.36.1.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
Uname: Linux 5.4.0-26-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec  3 13:47:26 2021
InstallationDate: Installed on 2017-04-18 (1690 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to focal on 2020-04-25 (587 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1953196

Title:
  gnome-terminal misreads a fediverse identifier as an email

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  On the fediverse ( the free software social media network of networks
  - https://jointhefedi.com/ ) the identifier format is

  @username@hostname

  unlike email which is

  username@hostname

  What happens:

  if you have a fediverse user displayed in your terminal, gnome-
  terminal deduces that it is an email and if you right click it, you
  are given the option to 'Copy Mail Address' and 'Send Mail To' instead
  of just 'Copy'

  What should happen:

  You should, instead, be given the option to 'Copy Fedi Address' (and,
  better yet, optionally 'Send DM To') instead of just 'Copy'.  Possibly
  including the 'Copy Mail Address', for backwards compatibility

  ubuntu: 20.04 LTS focal

  gnome-terminal:
Installed: 3.36.1.1-1ubuntu1
Candidate: 3.36.1.1-1ubuntu1
Version table:
   *** 3.36.1.1-1ubuntu1 500
  500 http://muug.ca/mirror/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-terminal 3.36.1.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
  Uname: Linux 5.4.0-26-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  3 13:47:26 2021
  InstallationDate: Installed on 2017-04-18 (1690 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to focal on 2020-04-25 (587 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Desktop-packages] [Bug 1876219] Re: iris driver for old cpu

[themusicgod1]

pretty sure this isn't a ring/jami bug

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1876219

Title:
  iris driver for old cpu

Status in Mesa:
  Confirmed
Status in ring package in Ubuntu:
  Invalid
Status in vlc package in Ubuntu:
  Invalid
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I am not completely sure where I should file the bug. I am using
  Lubuntu 20.04 with lxqt, and since the upgrade to 20.04 iris is the
  default graphics driver, which results in crashes in multiple apps
  including guvcview and calibre. Setting
  MESA_LOADER_DRIVER_OVERRIDE=i965 fixed the problem. I am not sure but
  is it true that iris does not support older generations of Intel CPUs?
  If it is the case would it be possible to revert to i965 in those
  circumstances? Thanks!

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


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

[Desktop-packages] [Bug 1747706] Re: 'copy to clipboard' only copy/pastes the first 127 rows into gimp

[themusicgod1]

not sure if the same bug but does the same thing with different numbers
of line...occasionally in focal

** Tags added: focal

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screenshot in Ubuntu.
https://bugs.launchpad.net/bugs/1747706

Title:
  'copy to clipboard' only copy/pastes the first 127 rows into gimp

Status in gimp package in Ubuntu:
  New
Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  0) have a gimp running
  1) run gnome-screenshot
  2) take screen shot
  3) click copy to clipboard
  4) alt-tab to gimp
  5) edit
  6) paste as new image

  The new image has 127 rows of the screenshot data followed by the
  correct number of other rows EXCEPT the other rows are of a single
  greyish colour (0x979899).

  (Saving the screenshot to file, and opening file in gimp works fine as
  a workaround for opening screen data in gimp)

  What should happen

  When you 'copy to clipboard' it should copy the whole image to clipboard.
  and 'paste' should retrieve the image data from clipboard into the gimp 
canvas.

  (Whether this is a gimp issue retrieving from clipboard or gnome-
  screenshot giving the data to clipboard I am not sure, but somewhere
  the clipboard data is not being passed properly)

   Ubuntu : 17.10 artful
   Desktop: gnome/wayland
   gimp : 2.8.20-1
   gnome-screenshot : 3.25.0-0ubuntu2

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-screenshot 3.25.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  6 11:07:59 2018
  InstallationDate: Installed on 2017-04-18 (293 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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.
  SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to artful on 2017-10-19 (109 days ago)

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

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

[Desktop-packages] [Bug 884122] Re: xclock -digital shows seconds but redraws on the minute

[themusicgod1]

** Tags added: focal

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to x11-apps in Ubuntu.
https://bugs.launchpad.net/bugs/884122

Title:
  xclock -digital shows seconds but redraws on the minute

Status in x11-apps package in Ubuntu:
  Confirmed

Bug description:
  i.e., on start it will show, e.g. "Mon 31 Oct 2011 09:17:15 GMT"
  (en_GB format), and stay that way for 45 seconds, then show "Mon 31
  Oct 2011 09:18:00 GMT" for a minute, etc.

  It redraws to show the correct time, including seconds, when the
  window is resized.  Window manager is Unity, version as of oneric-
  updates: 4.24.0-0ubuntu2b1 0.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: x11-apps 7.6+4ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  CheckboxSubmission: b0d31efda01870980e2e5a89390b685c
  CheckboxSystem: 6ce041aeed0a2c17b3343b66d157175d
  Date: Mon Oct 31 09:11:52 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  SourcePackage: x11-apps
  UpgradeStatus: Upgraded to oneiric on 2011-05-03 (181 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x11-apps/+bug/884122/+subscriptions

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

[Desktop-packages] [Bug 1811724] Re: libbd_mdraid.so.2: cannot open shared object file

[themusicgod1]

Seems to be just the warning in the log for me

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1811724

Title:
  libbd_mdraid.so.2: cannot open shared object file

Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  Had some (probably unrelated?) trouble typing input into login console, and 
went looking through /var/log/syslog : 
  found

  Jan 14 21:10:21 vps39184 udisksd[611]: udisks daemon version 2.8.1 starting
  Jan 14 21:10:22 vps39184 udisksd[611]: failed to load module mdraid: 
libbd_mdraid.so.2: cannot open shared object file: No such file or directory
  Jan 14 21:10:22 vps39184 udisksd[611]: Failed to load the 'mdraid' 
libblockdev plugin

  Seems to give this warning every time I boot.

  udisks2:
Installed: 2.8.1-3
Candidate: 2.8.1-3

  ubuntu: 19.04 disco

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: udisks2 2.8.1-3
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu18
  Architecture: amd64
  CustomUdevRuleFiles: 80-net-setup-link.rules
  Date: Mon Jan 14 21:31:52 2019
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Red Hat KVM
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=/dev/vda1 ro vga16fb.modeset=0 quiet splash
  SourcePackage: udisks2
  UpgradeStatus: Upgraded to disco on 2018-11-23 (52 days ago)
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Seabios
  dmi.bios.version: 0.5.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: Red Hat
  dmi.modalias: 
dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.6.0PC:cvnRedHat:ct1:cvr:
  dmi.product.family: Red Hat Enterprise Linux
  dmi.product.name: KVM
  dmi.product.version: RHEL 6.6.0 PC
  dmi.sys.vendor: Red Hat

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

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

[Desktop-packages] [Bug 1811724] Re: libbd_mdraid.so.2: cannot open shared object file

[themusicgod1]

hasn't come up in awhile though

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1811724

Title:
  libbd_mdraid.so.2: cannot open shared object file

Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  Had some (probably unrelated?) trouble typing input into login console, and 
went looking through /var/log/syslog : 
  found

  Jan 14 21:10:21 vps39184 udisksd[611]: udisks daemon version 2.8.1 starting
  Jan 14 21:10:22 vps39184 udisksd[611]: failed to load module mdraid: 
libbd_mdraid.so.2: cannot open shared object file: No such file or directory
  Jan 14 21:10:22 vps39184 udisksd[611]: Failed to load the 'mdraid' 
libblockdev plugin

  Seems to give this warning every time I boot.

  udisks2:
Installed: 2.8.1-3
Candidate: 2.8.1-3

  ubuntu: 19.04 disco

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: udisks2 2.8.1-3
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu18
  Architecture: amd64
  CustomUdevRuleFiles: 80-net-setup-link.rules
  Date: Mon Jan 14 21:31:52 2019
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Red Hat KVM
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=/dev/vda1 ro vga16fb.modeset=0 quiet splash
  SourcePackage: udisks2
  UpgradeStatus: Upgraded to disco on 2018-11-23 (52 days ago)
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Seabios
  dmi.bios.version: 0.5.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: Red Hat
  dmi.modalias: 
dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.6.0PC:cvnRedHat:ct1:cvr:
  dmi.product.family: Red Hat Enterprise Linux
  dmi.product.name: KVM
  dmi.product.version: RHEL 6.6.0 PC
  dmi.sys.vendor: Red Hat

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

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

[Desktop-packages] [Bug 1875019] Re: ftbfs: Test failed: Basic functionality with the bind-mounted cache dir

[themusicgod1]

yeah i do

Running: Basic functionality with the bind-mounted cache dir
*** Test failed: Basic functionality with the bind-mounted cache dir
cache was updated.
FAIL run-test.sh (exit status: 1)


Testsuite summary for fontconfig 2.13.1

# TOTAL: 7
# PASS:  6
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See test/test-suite.log
Please report to https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/new

make[5]: *** [Makefile:954: test-suite.log] Error 1
make[5]: Leaving directory '/home/themusicgod1/workspace/fontconfig-2.13.1/test'
make[4]: *** [Makefile:1062: check-TESTS] Error 2
make[4]: Leaving directory '/home/themusicgod1/workspace/fontconfig-2.13.1/test'
make[3]: *** [Makefile:1171: check-am] Error 2
make[3]: Leaving directory '/home/themusicgod1/workspace/fontconfig-2.13.1/test'
make[2]: *** [Makefile:1173: check] Error 2
make[2]: Leaving directory '/home/themusicgod1/workspace/fontconfig-2.13.1/test'
make[1]: *** [Makefile:602: check-recursive] Error 1
make[1]: Leaving directory '/home/themusicgod1/workspace/fontconfig-2.13.1'
dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:10: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -i -I -b failed


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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1875019

Title:
  ftbfs:  Test failed: Basic functionality with the bind-mounted cache
  dir

Status in fontconfig package in Ubuntu:
  New

Bug description:
  1) apt-src install fontconfig
  2) cd fontconfig-2.13.1/
  3) debuild -us -uc -b

  gets to

  PASS: test-hash
  PASS: test-bz106632
  FAIL: run-test.sh
  
 fontconfig 2.13.1: test/test-suite.log
  

  # TOTAL: 7
  # PASS:  6
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0

  .. contents:: :depth: 2

  FAIL: run-test
  ==

  Running: Basic check
  Running: With a subdir
  Running: Subdir with a cache file
  Running: Complicated directory structure
  Running: Subdir with an out-of-date cache file
  Running: Dir with an out-of-date cache file
  Running: Re-creating .uuid
  Running: Consistency between .uuid and cache name
  
b41b6931-2503-44dd-a5d0-465a2c171511/home/z/fontconfig-2.13.1/test/cache.dir/08acdce6-36bc-4684-9a7b-0f24192abc6b-le64.cache-7
  Running: Keep mtime of the font directory
  Running: Basic functionality with the bind-mounted cache dir
  *** Test failed: Basic functionality with the bind-mounted cache dir
  cache was updated.
  FAIL run-test.sh (exit status: 1)

  
  ubuntu: focal 20.04 LTS
  fontconfig1: fontconfig:
Installed: 2.13.1-2ubuntu3
Candidate: 2.13.1-2ubuntu3
Version table:
   *** 2.13.1-2ubuntu3 500
  500 http://speglar.simnet.is/ubuntu focal/main amd64 Packages
  500 http://ubuntu.hysing.is/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: fontconfig 2.13.1-2ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Apr 25 13:15:14 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fontconfig
  UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago)

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

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

[Desktop-packages] [Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5

[themusicgod1]

dow manager warning: Overwriting 
existing binding of keysym 33 with keysym 33 (keycode c).
  Jun  6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting 
existing binding of keysym 34 with keysym 34 (keycode d).
  Jun  6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting 
existing binding of keysym 35 with keysym 35 (keycode e).
  Jun  6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting 
existing binding of keysym 36 with keysym 36 (keycode f).
  Jun  6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting 
existing binding of keysym 37 with keysym 37 (keycode 10).
  Jun  6 20:47:44 eva gnome-shell[338452]: GNOME Shell started at Sat Jun 06 
2020 20:47:41 GMT-0600 (CST)
  Jun  6 20:47:44 eva gnome-shell[338452]: Registering session with GDM

  Seems to recover fine afterwards, but it happens again further down
  the line.

  Seems like something mnemosyne is doing during the transition after I
  hit a number is triggering this...but only one out of every couple
  hundred(thousand?) cards.

  mnemosyne:
Installed: 2.7.1+ds-1
Candidate: 2.7.1+ds-1
Version table:
   *** 2.7.1+ds-1 500
  500 http://mirrors.layeronline.com/ubuntu focal/universe amd64 
Packages
  500 http://mirrors.layeronline.com/ubuntu focal/universe i386 Packages
  100 /var/lib/dpkg/status
  themusicgod1@eva1:~$ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.36.1-5ubuntu1
Candidate: 3.36.1-5ubuntu1
Version table:
   *** 3.36.1-5ubuntu1 500
  500 http://mirrors.layeronline.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  themusicgod1@eva1:~$ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
  Uname: Linux 5.4.0-26-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 20:52:49 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-04-18 (1145 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago)

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

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

[Desktop-packages] [Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5

[themusicgod1]

 of keysym 35 with keysym 35 (keycode e).
  Jun  6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting 
existing binding of keysym 36 with keysym 36 (keycode f).
  Jun  6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting 
existing binding of keysym 37 with keysym 37 (keycode 10).
  Jun  6 20:47:44 eva gnome-shell[338452]: GNOME Shell started at Sat Jun 06 
2020 20:47:41 GMT-0600 (CST)
  Jun  6 20:47:44 eva gnome-shell[338452]: Registering session with GDM

  Seems to recover fine afterwards, but it happens again further down
  the line.

  Seems like something mnemosyne is doing during the transition after I
  hit a number is triggering this...but only one out of every couple
  hundred(thousand?) cards.

  mnemosyne:
Installed: 2.7.1+ds-1
Candidate: 2.7.1+ds-1
Version table:
   *** 2.7.1+ds-1 500
  500 http://mirrors.layeronline.com/ubuntu focal/universe amd64 
Packages
  500 http://mirrors.layeronline.com/ubuntu focal/universe i386 Packages
  100 /var/lib/dpkg/status
  themusicgod1@eva1:~$ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.36.1-5ubuntu1
Candidate: 3.36.1-5ubuntu1
Version table:
   *** 3.36.1-5ubuntu1 500
  500 http://mirrors.layeronline.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  themusicgod1@eva1:~$ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
  Uname: Linux 5.4.0-26-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 20:52:49 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-04-18 (1145 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago)

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

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

[Desktop-packages] [Bug 1882410] Re: GNOME Shell crashed with signal 5

[themusicgod1]

ndow manager warning: Overwriting 
existing binding of keysym 35 with keysym 35 (keycode e).
  Jun  6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting 
existing binding of keysym 36 with keysym 36 (keycode f).
  Jun  6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting 
existing binding of keysym 37 with keysym 37 (keycode 10).
  Jun  6 20:47:44 eva gnome-shell[338452]: GNOME Shell started at Sat Jun 06 
2020 20:47:41 GMT-0600 (CST)
  Jun  6 20:47:44 eva gnome-shell[338452]: Registering session with GDM

  Seems to recover fine afterwards, but it happens again further down
  the line.

  Seems like something mnemosyne is doing during the transition after I
  hit a number is triggering this...but only one out of every couple
  hundred(thousand?) cards.

  mnemosyne:
Installed: 2.7.1+ds-1
Candidate: 2.7.1+ds-1
Version table:
   *** 2.7.1+ds-1 500
  500 http://mirrors.layeronline.com/ubuntu focal/universe amd64 
Packages
      500 http://mirrors.layeronline.com/ubuntu focal/universe i386 Packages
  100 /var/lib/dpkg/status
  themusicgod1@eva1:~$ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.36.1-5ubuntu1
Candidate: 3.36.1-5ubuntu1
Version table:
   *** 3.36.1-5ubuntu1 500
  500 http://mirrors.layeronline.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  themusicgod1@eva1:~$ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
  Uname: Linux 5.4.0-26-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 20:52:49 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-04-18 (1145 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago)

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

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

[Desktop-packages] [Bug 1882410] Re: GNOME Shell crashed with signal 5

[themusicgod1]

va gnome-shell[338452]: Window manager warning: Overwriting 
existing binding of keysym 36 with keysym 36 (keycode f).
  Jun  6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting 
existing binding of keysym 37 with keysym 37 (keycode 10).
  Jun  6 20:47:44 eva gnome-shell[338452]: GNOME Shell started at Sat Jun 06 
2020 20:47:41 GMT-0600 (CST)
  Jun  6 20:47:44 eva gnome-shell[338452]: Registering session with GDM

  Seems to recover fine afterwards, but it happens again further down
  the line.

  Seems like something mnemosyne is doing during the transition after I
  hit a number is triggering this...but only one out of every couple
  hundred(thousand?) cards.

  mnemosyne:
Installed: 2.7.1+ds-1
Candidate: 2.7.1+ds-1
Version table:
   *** 2.7.1+ds-1 500
  500 http://mirrors.layeronline.com/ubuntu focal/universe amd64 
Packages
  500 http://mirrors.layeronline.com/ubuntu focal/universe i386 Packages
  100 /var/lib/dpkg/status
  themusicgod1@eva1:~$ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.36.1-5ubuntu1
Candidate: 3.36.1-5ubuntu1
Version table:
   *** 3.36.1-5ubuntu1 500
  500 http://mirrors.layeronline.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  themusicgod1@eva1:~$ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
  Uname: Linux 5.4.0-26-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 20:52:49 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-04-18 (1145 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago)

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

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

[Desktop-packages] [Bug 1884925] Re: GNOME Shell crashed signal 5

[themusicgod1]

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

** Information type changed from Private to Private Security

** Information type changed from Private Security to Public Security

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1884925

Title:
  GNOME Shell crashed  signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I don't know why launchpad can't find #1882410 this is just a
  duplicate , but following instructions in that bug to file a bug using
  apport-cli

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
  Uname: Linux 5.4.0-26-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 24 03:08:54 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1586912446
  InstallationDate: Installed on 2017-04-18 (1162 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/themusicgod1
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/libgjs.so.0
   () at /usr/lib/libgjs.so.0
   () at /usr/lib/libgjs.so.0
   g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to focal on 2020-04-25 (59 days ago)
  UserGroups: audio debian-tor
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404
  separator:

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

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

[Desktop-packages] [Bug 1882410] Re: GNOME Shell crashed with signal 5

[themusicgod1]

  Jun  6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting 
existing binding of keysym 36 with keysym 36 (keycode f).
  Jun  6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting 
existing binding of keysym 37 with keysym 37 (keycode 10).
  Jun  6 20:47:44 eva gnome-shell[338452]: GNOME Shell started at Sat Jun 06 
2020 20:47:41 GMT-0600 (CST)
  Jun  6 20:47:44 eva gnome-shell[338452]: Registering session with GDM

  Seems to recover fine afterwards, but it happens again further down
  the line.

  Seems like something mnemosyne is doing during the transition after I
  hit a number is triggering this...but only one out of every couple
  hundred(thousand?) cards.

  mnemosyne:
Installed: 2.7.1+ds-1
Candidate: 2.7.1+ds-1
Version table:
   *** 2.7.1+ds-1 500
  500 http://mirrors.layeronline.com/ubuntu focal/universe amd64 
Packages
  500 http://mirrors.layeronline.com/ubuntu focal/universe i386 Packages
  100 /var/lib/dpkg/status
  themusicgod1@eva1:~$ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.36.1-5ubuntu1
Candidate: 3.36.1-5ubuntu1
Version table:
   *** 3.36.1-5ubuntu1 500
  500 http://mirrors.layeronline.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  themusicgod1@eva1:~$ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
  Uname: Linux 5.4.0-26-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 20:52:49 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-04-18 (1145 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago)

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

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

[Desktop-packages] [Bug 1882410] Re: GNOME Shell crashed with signal 5

[themusicgod1]

 eva gnome-shell[338452]: Window manager warning: Overwriting 
existing binding of keysym 36 with keysym 36 (keycode f).
  Jun  6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting 
existing binding of keysym 37 with keysym 37 (keycode 10).
  Jun  6 20:47:44 eva gnome-shell[338452]: GNOME Shell started at Sat Jun 06 
2020 20:47:41 GMT-0600 (CST)
  Jun  6 20:47:44 eva gnome-shell[338452]: Registering session with GDM

  Seems to recover fine afterwards, but it happens again further down
  the line.

  Seems like something mnemosyne is doing during the transition after I
  hit a number is triggering this...but only one out of every couple
  hundred(thousand?) cards.

  mnemosyne:
Installed: 2.7.1+ds-1
Candidate: 2.7.1+ds-1
Version table:
   *** 2.7.1+ds-1 500
  500 http://mirrors.layeronline.com/ubuntu focal/universe amd64 
Packages
  500 http://mirrors.layeronline.com/ubuntu focal/universe i386 Packages
  100 /var/lib/dpkg/status
  themusicgod1@eva1:~$ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.36.1-5ubuntu1
Candidate: 3.36.1-5ubuntu1
Version table:
   *** 3.36.1-5ubuntu1 500
  500 http://mirrors.layeronline.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  themusicgod1@eva1:~$ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
  Uname: Linux 5.4.0-26-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 20:52:49 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-04-18 (1145 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago)

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

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

[Desktop-packages] [Bug 1882410] Re: GNOME Shell crashed with signal 5

[themusicgod1]

 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting 
existing binding of keysym 36 with keysym 36 (keycode f).
  Jun  6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting 
existing binding of keysym 37 with keysym 37 (keycode 10).
  Jun  6 20:47:44 eva gnome-shell[338452]: GNOME Shell started at Sat Jun 06 
2020 20:47:41 GMT-0600 (CST)
  Jun  6 20:47:44 eva gnome-shell[338452]: Registering session with GDM

  Seems to recover fine afterwards, but it happens again further down
  the line.

  Seems like something mnemosyne is doing during the transition after I
  hit a number is triggering this...but only one out of every couple
  hundred(thousand?) cards.

  mnemosyne:
Installed: 2.7.1+ds-1
Candidate: 2.7.1+ds-1
Version table:
   *** 2.7.1+ds-1 500
  500 http://mirrors.layeronline.com/ubuntu focal/universe amd64 
Packages
      500 http://mirrors.layeronline.com/ubuntu focal/universe i386 Packages
  100 /var/lib/dpkg/status
  themusicgod1@eva1:~$ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.36.1-5ubuntu1
Candidate: 3.36.1-5ubuntu1
Version table:
   *** 3.36.1-5ubuntu1 500
  500 http://mirrors.layeronline.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  themusicgod1@eva1:~$ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
  Uname: Linux 5.4.0-26-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 20:52:49 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-04-18 (1145 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago)

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

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

[Desktop-packages] [Bug 1882410] Re: GNOME Shell crashed with signal 5

[themusicgod1]

dow manager warning: Overwriting 
existing binding of keysym 34 with keysym 34 (keycode d).
  Jun  6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting 
existing binding of keysym 35 with keysym 35 (keycode e).
  Jun  6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting 
existing binding of keysym 36 with keysym 36 (keycode f).
  Jun  6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting 
existing binding of keysym 37 with keysym 37 (keycode 10).
  Jun  6 20:47:44 eva gnome-shell[338452]: GNOME Shell started at Sat Jun 06 
2020 20:47:41 GMT-0600 (CST)
  Jun  6 20:47:44 eva gnome-shell[338452]: Registering session with GDM

  Seems to recover fine afterwards, but it happens again further down
  the line.

  Seems like something mnemosyne is doing during the transition after I
  hit a number is triggering this...but only one out of every couple
  hundred(thousand?) cards.

  mnemosyne:
Installed: 2.7.1+ds-1
Candidate: 2.7.1+ds-1
Version table:
   *** 2.7.1+ds-1 500
  500 http://mirrors.layeronline.com/ubuntu focal/universe amd64 
Packages
  500 http://mirrors.layeronline.com/ubuntu focal/universe i386 Packages
  100 /var/lib/dpkg/status
  themusicgod1@eva1:~$ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.36.1-5ubuntu1
Candidate: 3.36.1-5ubuntu1
Version table:
   *** 3.36.1-5ubuntu1 500
  500 http://mirrors.layeronline.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  themusicgod1@eva1:~$ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
  Uname: Linux 5.4.0-26-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 20:52:49 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-04-18 (1145 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago)

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

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

[Desktop-packages] [Bug 1882410] Re: GNOME Shell crashed with signal 5

[themusicgod1]

reproduced and got a crash file
but...

themusicgod1@eva1:~$ ubuntu-bug /var/crash/_usr_bin_gnome-
shell.1001.crash

consistently results in Sorry, Ubuntu 20.04 has experienced an internal
error

If you notice further problems, try restarting the computer
stack: 
/usr/bin/gnome-shell

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1882410

Title:
   GNOME Shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  A couple of times a day, I'm noticing all of the window dressing
  suddenly disappear from all of my open applications, then a second or
  two later returning.  Opening up /var/log/syslog I see:

  Jun  6 20:45:53 eva gnome-shell[335243]: Window manager warning: Invalid 
WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518.
  Jun  6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid 
WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f.
  Jun  6 20:47:40 eva gnome-shell[335243]: toggling down object 
GInotifyFileMonitor that's already queued to toggle down
  Jun  6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5
  Jun  6 20:47:40 eva gnome-shell[335243]: == Stack trace for context 
0x557e3a0446a0 ==
  Jun  6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=5/TRAP
  Jun  6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
  Jun  6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled 
restart job, restart counter is at 3.
  Jun  6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session 
(session: ubuntu).
  Jun  6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session: 
ubuntu).
  Jun  6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session.
  Jun  6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session.
  Jun  6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11.
  Jun  6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11.
  Jun  6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11.
  Jun  6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11...
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID 
vendor "ACI", prod id 8434
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Using hsync ranges from config file
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Using vrefresh ranges from config file
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "1600x900"x0.0  108.00  1600 1624 1704 1800  900 901 904 1000 +hsync 
+vsync (60.0 kHz eP)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync 
(37.9 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync 
(35.2 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync 
(37.5 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync 
(37.9 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync 
(35.0 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync 
(31.5 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync 
(31.5 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync 
+vsync (60.0 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync 
-vsync (56.5 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync 
-vsync (48.4 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync 
(49.7 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "800x600"x0.0   49.50  

[Desktop-packages] [Bug 1882410] Re: GNOME Shell crashed with signal 5

[themusicgod1]

ning: Overwriting 
existing binding of keysym 34 with keysym 34 (keycode d).
  Jun  6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting 
existing binding of keysym 35 with keysym 35 (keycode e).
  Jun  6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting 
existing binding of keysym 36 with keysym 36 (keycode f).
  Jun  6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting 
existing binding of keysym 37 with keysym 37 (keycode 10).
  Jun  6 20:47:44 eva gnome-shell[338452]: GNOME Shell started at Sat Jun 06 
2020 20:47:41 GMT-0600 (CST)
  Jun  6 20:47:44 eva gnome-shell[338452]: Registering session with GDM

  Seems to recover fine afterwards, but it happens again further down
  the line.

  Seems like something mnemosyne is doing during the transition after I
  hit a number is triggering this...but only one out of every couple
  hundred(thousand?) cards.

  mnemosyne:
Installed: 2.7.1+ds-1
Candidate: 2.7.1+ds-1
Version table:
   *** 2.7.1+ds-1 500
  500 http://mirrors.layeronline.com/ubuntu focal/universe amd64 
Packages
  500 http://mirrors.layeronline.com/ubuntu focal/universe i386 Packages
  100 /var/lib/dpkg/status
  themusicgod1@eva1:~$ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.36.1-5ubuntu1
Candidate: 3.36.1-5ubuntu1
Version table:
   *** 3.36.1-5ubuntu1 500
  500 http://mirrors.layeronline.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  themusicgod1@eva1:~$ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
  Uname: Linux 5.4.0-26-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 20:52:49 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-04-18 (1145 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago)

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

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

[Desktop-packages] [Bug 1882410] [NEW] GNOME Shell crashed with signal 5

[themusicgod1]

ut it happens again further down the
line.

Seems like something mnemosyne is doing during the transition after I
hit a number is triggering this...but only one out of every couple
hundred(thousand?) cards.

mnemosyne:
  Installed: 2.7.1+ds-1
  Candidate: 2.7.1+ds-1
  Version table:
 *** 2.7.1+ds-1 500
500 http://mirrors.layeronline.com/ubuntu focal/universe amd64 Packages
500 http://mirrors.layeronline.com/ubuntu focal/universe i386 Packages
100 /var/lib/dpkg/status
themusicgod1@eva1:~$ apt-cache policy gnome-shell
gnome-shell:
  Installed: 3.36.1-5ubuntu1
  Candidate: 3.36.1-5ubuntu1
  Version table:
 *** 3.36.1-5ubuntu1 500
500 http://mirrors.layeronline.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
themusicgod1@eva1:~$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
Uname: Linux 5.4.0-26-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun  6 20:52:49 2020
DisplayManager: gdm3
InstallationDate: Installed on 2017-04-18 (1145 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago)

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


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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1882410

Title:
   GNOME Shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  A couple of times a day, I'm noticing all of the window dressing
  suddenly disappear from all of my open applications, then a second or
  two later returning.  Opening up /var/log/syslog I see:

  Jun  6 20:45:53 eva gnome-shell[335243]: Window manager warning: Invalid 
WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518.
  Jun  6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid 
WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f.
  Jun  6 20:47:40 eva gnome-shell[335243]: toggling down object 
GInotifyFileMonitor that's already queued to toggle down
  Jun  6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5
  Jun  6 20:47:40 eva gnome-shell[335243]: == Stack trace for context 
0x557e3a0446a0 ==
  Jun  6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=5/TRAP
  Jun  6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
  Jun  6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled 
restart job, restart counter is at 3.
  Jun  6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session 
(session: ubuntu).
  Jun  6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session: 
ubuntu).
  Jun  6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session.
  Jun  6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session.
  Jun  6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11.
  Jun  6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11.
  Jun  6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11.
  Jun  6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11...
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID 
vendor "ACI", prod id 8434
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Using hsync ranges from config file
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Using vrefresh ranges from config file
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "1600x900"x0.0  108.00  1600 1624 1704 1800  900 901 904 1000 +hsync 
+vsync (60.0 kHz eP)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync 
(37.9 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync 
(35.2 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync 
(37.5 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync 
(37.9 kHz e)
  J

[Desktop-packages] [Bug 1876431] [NEW] windows invisible when there should have been a lock screen

[themusicgod1]

Public bug reported:

Shortly after upgrading to focal (a few days) I left my computer alone
and went and away for a good long while, long enough for the screen to
lock

Came back and
1) the screen was not locked, 
2) the dock at the right hand side was still available and i could manipulate 
it (ie click on the applications that were running, see the screenshots of them 
when i mouse'd over them)
2) no windows could be seen.

I managed to for example click on the running bitcoin icon in the top right 
hand corner, those were clickable too, but nothing did seemed to get the 
windows back. 
Alt-tab...
alt-crl up...
super-tab...
nothing i could think of

Wound up exiting out to terminal (ctrl-alt-f3, logging in) killing
gnome-shell and they all came back shortly there after.

ubuntu: focal 20.04 lts
gnome-shell:
  Installed: 3.36.1-5ubuntu1
  Candidate: 3.36.1-5ubuntu1
  Version table:
 *** 3.36.1-5ubuntu1 500
500 http://mirrors.layeronline.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
Uname: Linux 5.4.0-26-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat May  2 03:16:38 2020
DisplayManager: gdm3
InstallationDate: Installed on 2017-04-18 (1109 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-04-25 (6 days ago)

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


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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1876431

Title:
  windows invisible when there should have been a lock screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Shortly after upgrading to focal (a few days) I left my computer alone
  and went and away for a good long while, long enough for the screen to
  lock

  Came back and
  1) the screen was not locked, 
  2) the dock at the right hand side was still available and i could manipulate 
it (ie click on the applications that were running, see the screenshots of them 
when i mouse'd over them)
  2) no windows could be seen.

  I managed to for example click on the running bitcoin icon in the top right 
hand corner, those were clickable too, but nothing did seemed to get the 
windows back. 
  Alt-tab...
  alt-crl up...
  super-tab...
  nothing i could think of

  Wound up exiting out to terminal (ctrl-alt-f3, logging in) killing
  gnome-shell and they all came back shortly there after.

  ubuntu: focal 20.04 lts
  gnome-shell:
Installed: 3.36.1-5ubuntu1
Candidate: 3.36.1-5ubuntu1
Version table:
   *** 3.36.1-5ubuntu1 500
  500 http://mirrors.layeronline.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
  Uname: Linux 5.4.0-26-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  2 03:16:38 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-04-18 (1109 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-25 (6 days ago)

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

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

[Desktop-packages] [Bug 1875019] [NEW] ftbfs: Test failed: Basic functionality with the bind-mounted cache dir

[themusicgod1]

Public bug reported:

1) apt-src install fontconfig
2) cd fontconfig-2.13.1/
3) debuild -us -uc -b

gets to

PASS: test-hash
PASS: test-bz106632
FAIL: run-test.sh

   fontconfig 2.13.1: test/test-suite.log


# TOTAL: 7
# PASS:  6
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: run-test
==

Running: Basic check
Running: With a subdir
Running: Subdir with a cache file
Running: Complicated directory structure
Running: Subdir with an out-of-date cache file
Running: Dir with an out-of-date cache file
Running: Re-creating .uuid
Running: Consistency between .uuid and cache name
b41b6931-2503-44dd-a5d0-465a2c171511/home/z/fontconfig-2.13.1/test/cache.dir/08acdce6-36bc-4684-9a7b-0f24192abc6b-le64.cache-7
Running: Keep mtime of the font directory
Running: Basic functionality with the bind-mounted cache dir
*** Test failed: Basic functionality with the bind-mounted cache dir
cache was updated.
FAIL run-test.sh (exit status: 1)


ubuntu: focal 20.04 LTS
fontconfig1: fontconfig:
  Installed: 2.13.1-2ubuntu3
  Candidate: 2.13.1-2ubuntu3
  Version table:
 *** 2.13.1-2ubuntu3 500
500 http://speglar.simnet.is/ubuntu focal/main amd64 Packages
500 http://ubuntu.hysing.is/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: fontconfig 2.13.1-2ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Apr 25 13:15:14 2020
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: fontconfig
UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago)

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


** Tags: amd64 apport-bug focal ftbfs

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1875019

Title:
  ftbfs:  Test failed: Basic functionality with the bind-mounted cache
  dir

Status in fontconfig package in Ubuntu:
  New

Bug description:
  1) apt-src install fontconfig
  2) cd fontconfig-2.13.1/
  3) debuild -us -uc -b

  gets to

  PASS: test-hash
  PASS: test-bz106632
  FAIL: run-test.sh
  
 fontconfig 2.13.1: test/test-suite.log
  

  # TOTAL: 7
  # PASS:  6
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0

  .. contents:: :depth: 2

  FAIL: run-test
  ==

  Running: Basic check
  Running: With a subdir
  Running: Subdir with a cache file
  Running: Complicated directory structure
  Running: Subdir with an out-of-date cache file
  Running: Dir with an out-of-date cache file
  Running: Re-creating .uuid
  Running: Consistency between .uuid and cache name
  
b41b6931-2503-44dd-a5d0-465a2c171511/home/z/fontconfig-2.13.1/test/cache.dir/08acdce6-36bc-4684-9a7b-0f24192abc6b-le64.cache-7
  Running: Keep mtime of the font directory
  Running: Basic functionality with the bind-mounted cache dir
  *** Test failed: Basic functionality with the bind-mounted cache dir
  cache was updated.
  FAIL run-test.sh (exit status: 1)

  
  ubuntu: focal 20.04 LTS
  fontconfig1: fontconfig:
Installed: 2.13.1-2ubuntu3
Candidate: 2.13.1-2ubuntu3
Version table:
   *** 2.13.1-2ubuntu3 500
  500 http://speglar.simnet.is/ubuntu focal/main amd64 Packages
  500 http://ubuntu.hysing.is/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: fontconfig 2.13.1-2ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Apr 25 13:15:14 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fontconfig
  UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago)

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

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

[Desktop-packages] [Bug 1856941] [NEW] chinese input option just qwerty

[themusicgod1]

Public bug reported:

Not sure where to report this, but this is where to reproduce, at least:

to reproduce
1) click on triangle at top right hand corner of screen to get menu
2) click on settings icon
3) click on language and region
4) click on +
5) click on ...
6) click on other
7) click on chinese
8) click on add

9) you should now have a 'chinese' input source.  click on that
10) click on keyboard icon
this shows just a plain qwerty keyboard
alternatively 
click on the input language option at the top of the screen
select chinese (zh)
start typing on an input field somewhere
result: qwerty, not chinese input.

what should happen
the chinese (zh) input should actually generate chinese characters.  or 
something

ubuntu: 18.04 bionic
gnome-control-center: 3.28.2-0ubuntu0.18.04.5

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


** Tags: bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1856941

Title:
  chinese input option just qwerty

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Not sure where to report this, but this is where to reproduce, at
  least:

  to reproduce
  1) click on triangle at top right hand corner of screen to get menu
  2) click on settings icon
  3) click on language and region
  4) click on +
  5) click on ...
  6) click on other
  7) click on chinese
  8) click on add

  9) you should now have a 'chinese' input source.  click on that
  10) click on keyboard icon
  this shows just a plain qwerty keyboard
  alternatively 
  click on the input language option at the top of the screen
  select chinese (zh)
  start typing on an input field somewhere
  result: qwerty, not chinese input.

  what should happen
  the chinese (zh) input should actually generate chinese characters.  or 
something

  ubuntu: 18.04 bionic
  gnome-control-center: 3.28.2-0ubuntu0.18.04.5

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

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

[Desktop-packages] [Bug 1794033] Re: i965: Failed to submit batchbuffer: Bad address

[themusicgod1]

TFA above suggests that the change is related to 4.19, but the above
shows that 4.15 was also affected.  Does this matter?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1794033

Title:
   i965: Failed to submit batchbuffer: Bad address

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Fedora:
  Unknown

Bug description:
  cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
  gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
  00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20171229-1
Candidate: 2:2.99.917+git20171229-1
  ubuntu: 18.04 LTS bionic
  gnome: 3.28.2
  gdm3:
Installed: 3.28.2-0ubuntu1.4
Candidate: 3.28.2-0ubuntu1.4
  os type: 64 bit
  kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  mesa-va-drivers:
Installed: 18.0.5-0ubuntu0~18.04.1
Candidate: 18.0.5-0ubuntu0~18.04.1

  from syslog:

  Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
  Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
   - but 
  (followed by pages upon pages of applications within gnome failing.)

  nothing in kern.log around that time.

  Singular gnome crash, taking down all applications running within it.
  Not yet reproduced. gdm successfully started a new session afterwards.
  Was definitely in a palermoon session on some website or other.

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

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

[Desktop-packages] [Bug 1794033] Re: i965: Failed to submit batchbuffer: Bad address

[themusicgod1]

** Also affects: mesa via
   https://gitlab.freedesktop.org/mesa/mesa/issues/1680
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1794033

Title:
   i965: Failed to submit batchbuffer: Bad address

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Fedora:
  Unknown

Bug description:
  cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
  gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
  00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20171229-1
Candidate: 2:2.99.917+git20171229-1
  ubuntu: 18.04 LTS bionic
  gnome: 3.28.2
  gdm3:
Installed: 3.28.2-0ubuntu1.4
Candidate: 3.28.2-0ubuntu1.4
  os type: 64 bit
  kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  mesa-va-drivers:
Installed: 18.0.5-0ubuntu0~18.04.1
Candidate: 18.0.5-0ubuntu0~18.04.1

  from syslog:

  Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
  Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
   - but 
  (followed by pages upon pages of applications within gnome failing.)

  nothing in kern.log around that time.

  Singular gnome crash, taking down all applications running within it.
  Not yet reproduced. gdm successfully started a new session afterwards.
  Was definitely in a palermoon session on some website or other.

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

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

[Desktop-packages] [Bug 1811724] Re: libbd_mdraid.so.2: cannot open shared object file

[themusicgod1]

** Tags added: eoan

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1811724

Title:
  libbd_mdraid.so.2: cannot open shared object file

Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  Had some (probably unrelated?) trouble typing input into login console, and 
went looking through /var/log/syslog : 
  found

  Jan 14 21:10:21 vps39184 udisksd[611]: udisks daemon version 2.8.1 starting
  Jan 14 21:10:22 vps39184 udisksd[611]: failed to load module mdraid: 
libbd_mdraid.so.2: cannot open shared object file: No such file or directory
  Jan 14 21:10:22 vps39184 udisksd[611]: Failed to load the 'mdraid' 
libblockdev plugin

  Seems to give this warning every time I boot.

  udisks2:
Installed: 2.8.1-3
Candidate: 2.8.1-3

  ubuntu: 19.04 disco

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: udisks2 2.8.1-3
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu18
  Architecture: amd64
  CustomUdevRuleFiles: 80-net-setup-link.rules
  Date: Mon Jan 14 21:31:52 2019
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Red Hat KVM
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=/dev/vda1 ro vga16fb.modeset=0 quiet splash
  SourcePackage: udisks2
  UpgradeStatus: Upgraded to disco on 2018-11-23 (52 days ago)
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Seabios
  dmi.bios.version: 0.5.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: Red Hat
  dmi.modalias: 
dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.6.0PC:cvnRedHat:ct1:cvr:
  dmi.product.family: Red Hat Enterprise Linux
  dmi.product.name: KVM
  dmi.product.version: RHEL 6.6.0 PC
  dmi.sys.vendor: Red Hat

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

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

[Desktop-packages] [Bug 508618] Re: Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp

[themusicgod1]

emacs26 in disco gives the error 

 
"Re-entering top level after C stack overflow" which seems like an appropriate 
error.

** Changed in: emacs25 (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs24 in Ubuntu.
https://bugs.launchpad.net/bugs/508618

Title:
  Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp

Status in emacs23 package in Ubuntu:
  New
Status in emacs24 package in Ubuntu:
  New
Status in emacs25 package in Ubuntu:
  Fix Committed
Status in emacs25 package in Debian:
  New

Bug description:
  Binary package hint: emacs23

  Setting max-specpdl-size higher than 34295, and then running the following 
code results in a segfault of emacs.  I am 
  running a system of mostly 9.04 with some packages (such as this one) 
upgraded. I know it's kind of pushing emacs to the limit, but still;  this 
seems like an arbitrary limit on emacs' otherwise diety-like functionality.  
What should happen is emacs should continue to fail to execute with 
"file-truename: Variable binding depth exceeds max-specpdl-size"  as it does 
below 34295., or at the very least when setting max-specpdl-size higher than 
34295 it should warn you that you are making some kind of error if this is not 
acceptable.

  example code:

  (defun por (pcurrent pb numberleft)
 (if (= numberleft 0)
   pcurrent
   (por (- (+ pcurrent pb) (* pcurrent pb)) pb (- numberleft 1

  (por 0 0.01 1)

  (setq max-lisp-eval-depth 100)  ; this may be necessary, but doesn't 
appear to be the problem
  (setq max-specpdl-size 34295)  ; setting this lower results in 
predictable, expected behaviour - emacs refuses to run the result, citing 
max-specpdl-size not high enough.   Setting this higher (like...34296), results 
in a segfault of emacs

  emacs23:
Installé : 23.1+1-4ubuntu3
Candidat : 23.1+1-4ubuntu3
   Table de version :
   *** 23.1+1-4ubuntu3 0
  100 /var/lib/dpkg/status

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  Package: emacs23 23.1+1-4ubuntu3
  ProcEnviron:
   PATH=(custom, user)
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: emacs23
  Uname: Linux 2.6.28-16-generic x86_64
  UnreportableReason: Ceci n'est pas un authentique paquet Ubuntu

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

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

[Desktop-packages] [Bug 1814991] Re: 'lock' glitch

[themusicgod1]

1) Alas, my video camera is attached to the computer that does this, so
that won't be an option probably

2) triangle - https://niu.moe/@jeffcliff/101617368364604090

3) it locked properly on the first Windows+L, so unlocked and hit
Windows+L immediately.  It locked successfully on both times.

Also tried to Win+L twice, this only just lead to a working lock screen.
(I noticed the sidebar was also not present, not sure if this is
related.)

4) done.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1814991

Title:
  'lock' glitch

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  From within gnome:

  I left-click 'triangle' 
  I left-click on the lock

  the screen gets stuck where it doesn't go to the lock screen, but
  instead the lock icon flashes orange, then back to brown, then back to
  orange, then back to brown over and over again.

  I can still move the mouse but I can't click on anything

  Shift-Alt-F3 gets me to a terminal, then Shift-Alt-f2 or f1 gets me
  back...and then there's a lock screen.

  It's done this twice now.

  ubuntu: 18.04 LTS bionic
  gnome: 3.28.2
  graphics: Intel® HD Graphics 630 (Kaby Lake GT2)
  OS Type: 64-bit
  xserver-xorg-video-intel:  2:2.99.917+git20171229-1

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

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

[Desktop-packages] [Bug 1814991] [NEW] 'lock' glitch

[themusicgod1]

Public bug reported:

>From within gnome:

I left-click 'triangle' 
I left-click on the lock

the screen gets stuck where it doesn't go to the lock screen, but
instead the lock icon flashes orange, then back to brown, then back to
orange, then back to brown over and over again.

I can still move the mouse but I can't click on anything

Shift-Alt-F3 gets me to a terminal, then Shift-Alt-f2 or f1 gets me
back...and then there's a lock screen.

It's done this twice now.

ubuntu: 18.04 LTS bionic
gnome: 3.28.2
graphics: Intel® HD Graphics 630 (Kaby Lake GT2)
OS Type: 64-bit
xserver-xorg-video-intel:  2:2.99.917+git20171229-1

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


** Tags: bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1814991

Title:
  'lock' glitch

Status in gdm3 package in Ubuntu:
  New

Bug description:
  From within gnome:

  I left-click 'triangle' 
  I left-click on the lock

  the screen gets stuck where it doesn't go to the lock screen, but
  instead the lock icon flashes orange, then back to brown, then back to
  orange, then back to brown over and over again.

  I can still move the mouse but I can't click on anything

  Shift-Alt-F3 gets me to a terminal, then Shift-Alt-f2 or f1 gets me
  back...and then there's a lock screen.

  It's done this twice now.

  ubuntu: 18.04 LTS bionic
  gnome: 3.28.2
  graphics: Intel® HD Graphics 630 (Kaby Lake GT2)
  OS Type: 64-bit
  xserver-xorg-video-intel:  2:2.99.917+git20171229-1

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

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

[Desktop-packages] [Bug 1811724] [NEW] libbd_mdraid.so.2: cannot open shared object file

[themusicgod1]

Public bug reported:

Had some (probably unrelated?) trouble typing input into login console, and 
went looking through /var/log/syslog : 
found

Jan 14 21:10:21 vps39184 udisksd[611]: udisks daemon version 2.8.1 starting
Jan 14 21:10:22 vps39184 udisksd[611]: failed to load module mdraid: 
libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Jan 14 21:10:22 vps39184 udisksd[611]: Failed to load the 'mdraid' libblockdev 
plugin

Seems to give this warning every time I boot.

udisks2:
  Installed: 2.8.1-3
  Candidate: 2.8.1-3

ubuntu: 19.04 disco

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: udisks2 2.8.1-3
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu18
Architecture: amd64
CustomUdevRuleFiles: 80-net-setup-link.rules
Date: Mon Jan 14 21:31:52 2019
Lsusb:
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Red Hat KVM
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: root=/dev/vda1 ro vga16fb.modeset=0 quiet splash
SourcePackage: udisks2
UpgradeStatus: Upgraded to disco on 2018-11-23 (52 days ago)
dmi.bios.date: 01/01/2007
dmi.bios.vendor: Seabios
dmi.bios.version: 0.5.1
dmi.chassis.type: 1
dmi.chassis.vendor: Red Hat
dmi.modalias: 
dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.6.0PC:cvnRedHat:ct1:cvr:
dmi.product.family: Red Hat Enterprise Linux
dmi.product.name: KVM
dmi.product.version: RHEL 6.6.0 PC
dmi.sys.vendor: Red Hat

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


** Tags: amd64 apport-bug disco

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1811724

Title:
  libbd_mdraid.so.2: cannot open shared object file

Status in udisks2 package in Ubuntu:
  New

Bug description:
  Had some (probably unrelated?) trouble typing input into login console, and 
went looking through /var/log/syslog : 
  found

  Jan 14 21:10:21 vps39184 udisksd[611]: udisks daemon version 2.8.1 starting
  Jan 14 21:10:22 vps39184 udisksd[611]: failed to load module mdraid: 
libbd_mdraid.so.2: cannot open shared object file: No such file or directory
  Jan 14 21:10:22 vps39184 udisksd[611]: Failed to load the 'mdraid' 
libblockdev plugin

  Seems to give this warning every time I boot.

  udisks2:
Installed: 2.8.1-3
Candidate: 2.8.1-3

  ubuntu: 19.04 disco

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: udisks2 2.8.1-3
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu18
  Architecture: amd64
  CustomUdevRuleFiles: 80-net-setup-link.rules
  Date: Mon Jan 14 21:31:52 2019
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Red Hat KVM
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=/dev/vda1 ro vga16fb.modeset=0 quiet splash
  SourcePackage: udisks2
  UpgradeStatus: Upgraded to disco on 2018-11-23 (52 days ago)
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Seabios
  dmi.bios.version: 0.5.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: Red Hat
  dmi.modalias: 
dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.6.0PC:cvnRedHat:ct1:cvr:
  dmi.product.family: Red Hat Enterprise Linux
  dmi.product.name: KVM
  dmi.product.version: RHEL 6.6.0 PC
  dmi.sys.vendor: Red Hat

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

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

[Desktop-packages] [Bug 1422360] Re: 100% cpu & gnome-terminal frozen in _IO_new_file_underflow

[themusicgod1]

It's all good - I try to review & reproduce all my open bugs each
release (or at least each LTS release for GUI programs like gnome-
terminal).  I have not been able to reproduce this one since vivid.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1422360

Title:
  100% cpu & gnome-terminal frozen in  _IO_new_file_underflow

Status in gnome-terminal package in Ubuntu:
  Incomplete

Bug description:
  gnome-terminal stopped responding to input & completely froze when
  attempting to change between tabs.

  Weirder: it seemed to trigger / coincide with
  https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/1414345

  gnome terminal stack trace at the point where it was stuck:

  #0  0x7fbf8b99ae0d in read () at ../sysdeps/unix/syscall-template.S:81
  #1  0x7fbf8b929dc0 in _IO_new_file_underflow (fp=0x1a3b800) at 
fileops.c:605
  #2  0x7fbf8b928bb8 in __GI__IO_file_xsgetn (fp=0x1a3b800, data=, n=16) at fileops.c:1410
  #3  0x7fbf8b927d6e in __GI_fread_unlocked (buf=, size=1, 
count=16, fp=) at iofread_u.c:44
  #4  0x7fbf8dbb05ad in  () at /usr/lib/libvte-2.91.so.0
  #5  0x7fbf8dbb063b in  () at /usr/lib/libvte-2.91.so.0
  #6  0x7fbf8db8edd0 in  () at /usr/lib/libvte-2.91.so.0
  #7  0x7fbf8db91fa2 in  () at /usr/lib/libvte-2.91.so.0
  #8  0x7fbf8dba2655 in vte_terminal_set_size () at 
/usr/lib/libvte-2.91.so.0
  #9  0x0042987f in  ()
  #10 0x7fbf87b29d90 in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
  #11 0x7fbf87b297f8 in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  #16 0x7fbf8c3d0d7a in  (instance=0x13, detailed_signal=0x7fbf8df8a000 
"5qX")
  at /build/buildd/glib2.0-2.43.3/./gobject/gsignal.c:3388
  #12 0x7fbf8c3b6aa4 in g_cclosure_marshal_generic (closure=0x1332a20, 
return_gvalue=0x0, n_param_values=, param_values=, invocation_hint=, marshal_data=0x0) at 
/build/buildd/glib2.0-2.43.3/./gobject/gclosure.c:1448
  #13 0x7fbf8c3b6285 in g_closure_invoke (closure=0x1332a20, 
return_value=0x0, n_param_values=3, param_values=0x7fffb4942320, 
invocation_hint=0x7fffb49422c0)
  at /build/buildd/glib2.0-2.43.3/./gobject/gclosure.c:768
  #14 0x7fbf8c3c8272 in signal_emit_unlocked_R 
(node=node@entry=0x13b4e70, detail=detail@entry=0, 
instance=instance@entry=0x1460230, emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffb4942320) at 
/build/buildd/glib2.0-2.43.3/./gobject/gsignal.c:3606
  #15 0x7fbf8c3d05c8 in g_signal_emit_valist (instance=, 
signal_id=, detail=, var_args=)
  at /build/buildd/glib2.0-2.43.3/./gobject/gsignal.c:3292
  #17 0x00418332 in  ()
  #21 0x7fbf8c3d082f in  (instance=, signal_id=, 
detail=)
  at /build/buildd/glib2.0-2.43.3/./gobject/gsignal.c:3348
  #18 0x7fbf8c3b6285 in g_closure_invoke (closure=0x12630b0, 
return_value=0x0, n_param_values=3, param_values=0x7fffb4942860, 
invocation_hint=0x7fffb4942800)
  at /build/buildd/glib2.0-2.43.3/./gobject/gclosure.c:768
  #19 0x7fbf8c3c7e62 in signal_emit_unlocked_R 
(node=node@entry=0x1263140, detail=detail@entry=0, 
instance=instance@entry=0x1460230, emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffb4942860) at 
/build/buildd/glib2.0-2.43.3/./gobject/gsignal.c:3574
  #20 0x7fbf8c3d05c8 in g_signal_emit_valist (instance=, 
signal_id=, detail=, 
var_args=var_args@entry=0x7fffb4942a10)
  at /build/buildd/glib2.0-2.43.3/./gobject/gsignal.c:3292
  #22 0x7fbf8d4d50f1 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #23 0x7fbf8d4a70ad in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #27 0x7fbf8c3d082f in  (instance=, signal_id=, 
detail=)
  at /build/buildd/glib2.0-2.43.3/./gobject/gsignal.c:3348
  #24 0x7fbf8c3b6285 in g_closure_invoke (closure=0x125ca10, 
return_value=0x7fffb4942ca0, n_param_values=2, param_values=0x7fffb4942d50, 
invocation_hint=0x7fffb4942cf0)
  at /build/buildd/glib2.0-2.43.3/./gobject/gclosure.c:768
  #25 0x7fbf8c3c7e62 in signal_emit_unlocked_R 
(node=node@entry=0x125ca60, detail=detail@entry=0, 
instance=instance@entry=0x1460230, 
emission_return=emission_return@entry=0x7fffb4942e00, 
instance_and_params=instance_and_params@entry=0x7fffb4942d50) at 
/build/buildd/glib2.0-2.43.3/./gobject/gsignal.c:3574
  #26 0x7fbf8c3d00d5 in g_signal_emit_valist (instance=, 
signal_id=, detail=, 
var_args=var_args@entry=0x7fffb4942ee0)
  at /build/buildd/glib2.0-2.43.3/./gobject/gsignal.c:3302
  #28 0x7fbf8d5d83a4 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #29 0x7fbf8d4a4abe in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #30 0x7fbf8d4a66ce in gtk_main_do_event () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #31 0x7fbf8d043a22 in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  #3

[Desktop-packages] [Bug 1794033] Re: i965: Failed to submit batchbuffer: Bad address

[themusicgod1]

also happened with
 
Linux: 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1794033

Title:
   i965: Failed to submit batchbuffer: Bad address

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Fedora:
  Unknown

Bug description:
  cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
  gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
  00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20171229-1
Candidate: 2:2.99.917+git20171229-1
  ubuntu: 18.04 LTS bionic
  gnome: 3.28.2
  gdm3:
Installed: 3.28.2-0ubuntu1.4
Candidate: 3.28.2-0ubuntu1.4
  os type: 64 bit
  kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  mesa-va-drivers:
Installed: 18.0.5-0ubuntu0~18.04.1
Candidate: 18.0.5-0ubuntu0~18.04.1

  from syslog:

  Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
  Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
   - but 
  (followed by pages upon pages of applications within gnome failing.)

  nothing in kern.log around that time.

  Singular gnome crash, taking down all applications running within it.
  Not yet reproduced. gdm successfully started a new session afterwards.
  Was definitely in a palermoon session on some website or other.

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

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

[Desktop-packages] [Bug 1797999] [NEW] eog segfaults in gtk_tree_model_get_valist ()

[themusicgod1]

Public bug reported:

Happens 100% of the time, but only in one directory.

1) cd into that directory (cd ~/gplus)
2) eog .
3) segfault

stack trace:
#0  0x76c8db8d in gtk_tree_model_get_valist () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#1  0x76c8de7d in gtk_tree_model_get () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#2  0x77b89256 in  () at /usr/lib/x86_64-linux-gnu/eog/libeog.so
#3  0x77b8a487 in  () at /usr/lib/x86_64-linux-gnu/eog/libeog.so
#4  0x73a87dae in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
#5  0x73a8771f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
#6  0x7791aced in g_cclosure_marshal_generic_va () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7  0x7791a346 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x7793596f in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9  0x7793609f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x7733dda9 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#11 0x77640287 in g_main_context_dispatch () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x776404c0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x7764054c in g_main_context_iteration () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x772f7ddd in g_application_run () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#15 0x52b2 in main ()

Granted, it's a big directory: at least 56,000 pictures, but still.

eog:
  Installed: 3.28.1-1
  Candidate: 3.28.1-1
  Version table:
 *** 3.28.1-1 500
500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu bionic/main 
amd64 Packages
500 https://mirror.its.sfu.ca/mirror/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
libgtk-3-0:
  Installed: 3.22.30-1ubuntu1
  Candidate: 3.22.30-1ubuntu1
  Version table:
 *** 3.22.30-1ubuntu1 500
500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu bionic/main 
amd64 Packages
500 https://mirror.its.sfu.ca/mirror/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
ubuntu: 18.04.1 bionic
gnome: 3.28.2 
linux: Linux eva1 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

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


** Tags: bionic

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

Title:
  eog segfaults in gtk_tree_model_get_valist ()

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Happens 100% of the time, but only in one directory.

  1) cd into that directory (cd ~/gplus)
  2) eog .
  3) segfault

  stack trace:
  #0  0x76c8db8d in gtk_tree_model_get_valist () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #1  0x76c8de7d in gtk_tree_model_get () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #2  0x77b89256 in  () at /usr/lib/x86_64-linux-gnu/eog/libeog.so
  #3  0x77b8a487 in  () at /usr/lib/x86_64-linux-gnu/eog/libeog.so
  #4  0x73a87dae in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
  #5  0x73a8771f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  #6  0x7791aced in g_cclosure_marshal_generic_va () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #7  0x7791a346 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #8  0x7793596f in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #9  0x7793609f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #10 0x7733dda9 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #11 0x77640287 in g_main_context_dispatch () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #12 0x776404c0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #13 0x7764054c in g_main_context_iteration () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #14 0x772f7ddd in g_application_run () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #15 0x52b2 in main ()

  Granted, it's a big directory: at least 56,000 pictures, but still.

  eog:
Installed: 3.28.1-1
Candidate: 3.28.1-1
Version table:
   *** 3.28.1-1 500
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu bionic/main 
amd64 Packages
  500 https://mirror.its.sfu.ca/mirror/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  libgtk-3-0:
Installed: 3.22.30-1ubuntu1
Candidate: 3.22.30-1ubuntu1
Version table:
   *** 3.22.30-1ubuntu1 500
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu bionic/main 
amd64 Packages
  500 https://mirror.its.sfu.ca/mirror/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  ubuntu: 18.04.1 bionic
  gnome:

[Desktop-packages] [Bug 1794033] Re: i965: Failed to submit batchbuffer: Bad address

[themusicgod1]

** Tags added: bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1794033

Title:
   i965: Failed to submit batchbuffer: Bad address

Status in xserver-xorg-video-intel package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Fedora:
  Unknown

Bug description:
  cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
  gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
  00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20171229-1
Candidate: 2:2.99.917+git20171229-1
  ubuntu: 18.04 LTS bionic
  gnome: 3.28.2
  gdm3:
Installed: 3.28.2-0ubuntu1.4
Candidate: 3.28.2-0ubuntu1.4
  os type: 64 bit
  kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  mesa-va-drivers:
Installed: 18.0.5-0ubuntu0~18.04.1
Candidate: 18.0.5-0ubuntu0~18.04.1

  from syslog:

  Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
  Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
   - but 
  (followed by pages upon pages of applications within gnome failing.)

  nothing in kern.log around that time.

  Singular gnome crash, taking down all applications running within it.
  Not yet reproduced. gdm successfully started a new session afterwards.
  Was definitely in a palermoon session on some website or other.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1794033/+subscriptions

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

[Desktop-packages] [Bug 1794033] [NEW] i965: Failed to submit batchbuffer: Bad address

[themusicgod1]

Public bug reported:

cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
xserver-xorg-video-intel:
  Installed: 2:2.99.917+git20171229-1
  Candidate: 2:2.99.917+git20171229-1
ubuntu: 18.04 LTS bionic
gnome: 3.28.2
gdm3:
  Installed: 3.28.2-0ubuntu1.4
  Candidate: 3.28.2-0ubuntu1.4
os type: 64 bit
kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
mesa-va-drivers:
  Installed: 18.0.5-0ubuntu0~18.04.1
  Candidate: 18.0.5-0ubuntu0~18.04.1

from syslog:

Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
 - but 
(followed by pages upon pages of applications within gnome failing.)

nothing in kern.log around that time.

Singular gnome crash, taking down all applications running within it.
Not yet reproduced. gdm successfully started a new session afterwards.
Was definitely in a palermoon session on some website or other.

** Affects: xserver-xorg-video-intel (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: xserver-xorg-video-intel (Fedora)
 Importance: Unknown
 Status: Unknown

** Bug watch added: freedesktop.org Bugzilla #104778
   https://bugs.freedesktop.org/show_bug.cgi?id=104778

** Also affects: xserver-xorg-video-intel (Fedora) via
   https://bugs.freedesktop.org/show_bug.cgi?id=104778
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1794033

Title:
   i965: Failed to submit batchbuffer: Bad address

Status in xserver-xorg-video-intel package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Fedora:
  Unknown

Bug description:
  cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
  gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
  00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20171229-1
Candidate: 2:2.99.917+git20171229-1
  ubuntu: 18.04 LTS bionic
  gnome: 3.28.2
  gdm3:
Installed: 3.28.2-0ubuntu1.4
Candidate: 3.28.2-0ubuntu1.4
  os type: 64 bit
  kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  mesa-va-drivers:
Installed: 18.0.5-0ubuntu0~18.04.1
Candidate: 18.0.5-0ubuntu0~18.04.1

  from syslog:

  Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
  Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
   - but 
  (followed by pages upon pages of applications within gnome failing.)

  nothing in kern.log around that time.

  Singular gnome crash, taking down all applications running within it.
  Not yet reproduced. gdm successfully started a new session afterwards.
  Was definitely in a palermoon session on some website or other.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1794033/+subscriptions

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

[Desktop-packages] [Bug 1299747] Re: Cannot create PGP key in Ubuntu 14.04

[themusicgod1]

upstream links new URL at
https://gitlab.gnome.org/GNOME/seahorse/issues/108 but can't figure out
how to link it to the expired ticket.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to seahorse in Ubuntu.
https://bugs.launchpad.net/bugs/1299747

Title:
  Cannot create PGP key in Ubuntu 14.04

Status in seahorse:
  Expired
Status in seahorse package in Ubuntu:
  Confirmed

Bug description:
  When I try to create a PGP key, enter my informations, passphrase and
  click ok, nothing happens. I am using Ubuntu 14.04 beta.

  I don't know if this is related to security.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: seahorse 3.10.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sun Mar 30 17:49:49 2014
  ExecutablePath: /usr/bin/seahorse
  InstallationDate: Installed on 2014-03-20 (10 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140225)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: seahorse
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 508618] Re: Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp

[themusicgod1]

** Tags added: cosmic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs24 in Ubuntu.
https://bugs.launchpad.net/bugs/508618

Title:
  Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp

Status in emacs23 package in Ubuntu:
  New
Status in emacs24 package in Ubuntu:
  New
Status in emacs25 package in Ubuntu:
  New
Status in emacs25 package in Debian:
  New

Bug description:
  Binary package hint: emacs23

  Setting max-specpdl-size higher than 34295, and then running the following 
code results in a segfault of emacs.  I am 
  running a system of mostly 9.04 with some packages (such as this one) 
upgraded. I know it's kind of pushing emacs to the limit, but still;  this 
seems like an arbitrary limit on emacs' otherwise diety-like functionality.  
What should happen is emacs should continue to fail to execute with 
"file-truename: Variable binding depth exceeds max-specpdl-size"  as it does 
below 34295., or at the very least when setting max-specpdl-size higher than 
34295 it should warn you that you are making some kind of error if this is not 
acceptable.

  example code:

  (defun por (pcurrent pb numberleft)
 (if (= numberleft 0)
   pcurrent
   (por (- (+ pcurrent pb) (* pcurrent pb)) pb (- numberleft 1

  (por 0 0.01 1)

  (setq max-lisp-eval-depth 100)  ; this may be necessary, but doesn't 
appear to be the problem
  (setq max-specpdl-size 34295)  ; setting this lower results in 
predictable, expected behaviour - emacs refuses to run the result, citing 
max-specpdl-size not high enough.   Setting this higher (like...34296), results 
in a segfault of emacs

  emacs23:
Installé : 23.1+1-4ubuntu3
Candidat : 23.1+1-4ubuntu3
   Table de version :
   *** 23.1+1-4ubuntu3 0
  100 /var/lib/dpkg/status

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  Package: emacs23 23.1+1-4ubuntu3
  ProcEnviron:
   PATH=(custom, user)
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: emacs23
  Uname: Linux 2.6.28-16-generic x86_64
  UnreportableReason: Ceci n'est pas un authentique paquet Ubuntu

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

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

[Desktop-packages] [Bug 1635310] Re: privacy settings not saved

[themusicgod1]

It no longer does this as of at least bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1635310

Title:
  privacy settings not saved

Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  steps to reproduce;

  1) open gnome-control-center
  2) click on privacy
  3) screen lock
  4) click on 'on' (to turn off)

  error message in the console:

  (gnome-control-center:25678): dconf-WARNING **: failed to commit
  changes to dconf:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to
  execute program ca.desrt.dconf: No such file or directory

  switch bounces back to 'on'

  You can change 'Lock screen after blank for' (screen turns off)
  ...but it seems to have no effect, and if you exit back to main control 
centre menu and go back to privacy it's re set to (screen turns off).

  similarly
  Show Notifications bounces back to default 'on' once clicked, 
  as does 'recently used' 
  and dropdowns 'retain history' in usage &  history also go back to default 
'forever' once you go back to them.

  tl;dr privacy settings don't actually do anything

  This did not seem to be the case in Ubuntu xenial ( 16.04 ), but has
  been so since upgrade to ubuntu yakkety ( 16.10 ).

  
  gnome-control-center: 1:3.20.1-2ubuntu3
  dconf-service: 0.26.0-2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-control-center 1:3.20.1-2ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 20 11:02:11 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-09 (833 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (3 days ago)

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

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

[Desktop-packages] [Bug 884122] Re: xclock -digital shows seconds but redraws on the minute

[themusicgod1]

** Tags added: bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to x11-apps in Ubuntu.
https://bugs.launchpad.net/bugs/884122

Title:
  xclock -digital shows seconds but redraws on the minute

Status in x11-apps package in Ubuntu:
  Confirmed

Bug description:
  i.e., on start it will show, e.g. "Mon 31 Oct 2011 09:17:15 GMT"
  (en_GB format), and stay that way for 45 seconds, then show "Mon 31
  Oct 2011 09:18:00 GMT" for a minute, etc.

  It redraws to show the correct time, including seconds, when the
  window is resized.  Window manager is Unity, version as of oneric-
  updates: 4.24.0-0ubuntu2b1 0.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: x11-apps 7.6+4ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  CheckboxSubmission: b0d31efda01870980e2e5a89390b685c
  CheckboxSystem: 6ce041aeed0a2c17b3343b66d157175d
  Date: Mon Oct 31 09:11:52 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  SourcePackage: x11-apps
  UpgradeStatus: Upgraded to oneiric on 2011-05-03 (181 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x11-apps/+bug/884122/+subscriptions

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

[Desktop-packages] [Bug 1478088] Re: doubleclicking video button makes no button selected

[themusicgod1]

** Tags added: bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cheese in Ubuntu.
https://bugs.launchpad.net/bugs/1478088

Title:
  doubleclicking video button makes no button selected

Status in cheese package in Ubuntu:
  New

Bug description:
  Minor UI glitch: 
  if you single click on the photo button, the photo button is clearly selected 
 (it is shaded darker)
  if you single click on the video button,  the video button is clearly 
selected  (it is shaded darker)
  if you double click on the video button, it is not clear what button is 
selected -- but it does seem like cheese is ready to take video otherwise (ie 
the timer is on the screen)

  Ubuntu: 15.10 wily werewolf.
  Cheese:  
Installed: 3.16.1-1ubuntu1
Candidate: 3.16.1-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: cheese 3.16.1-1ubuntu1
  Uname: Linux 4.1.0-040100rc1-generic x86_64
  ApportVersion: 2.18-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jul 24 12:47:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-09 (379 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  SourcePackage: cheese
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1682544] Re: xkill doesn't grab pointer in gnome/wayland

[themusicgod1]

This seems to be working properly as of bionic
x11-utils: 7.7+3build1
gnome: 3.28.1

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to x11-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1682544

Title:
  xkill doesn't grab pointer in gnome/wayland

Status in x11-utils package in Ubuntu:
  Triaged

Bug description:
  1. 
  > xkill 

  expected result:
  a) output: "Select the window whose client you wish to kill with button 1..."
  b) pointer turns to an X
  c) you can click on a window
  d) that window's process gets killed

  what actually happens
  a) output: "Select the window whose client you wish to kill with button 1..."
  b) The pointer goes invisible, until you move it, then it goes to the normal 
pointer.
  ...that's it.

  Ubuntu: 17.04 / zesty
  Desktop environment: Gnome/Weyland 
  x11-utils: 7.7+3

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: x11-utils 7.7+3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Thu Apr 13 13:40:03 2017
  DistUpgraded: 2017-04-13 12:41:16,896 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: zesty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0689]
 Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0689]
  InstallationDate: Installed on 2014-07-09 (1008 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  MachineType: Acer TravelMate P273-MG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=885e04f0-bd26-4885-aa1c-f134c674b8ff ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  SourcePackage: x11-utils
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  dmi.bios.date: 11/27/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BA70_HC
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.11:bd11/27/2013:svnAcer:pnTravelMateP273-MG:pvrV2.11:rvnAcer:rnBA70_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: TravelMate P273-MG
  dmi.product.version: V2.11
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Thu Apr 13 12:45:10 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x11-utils/+bug/1682544/+subscriptions

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

[Desktop-packages] [Bug 1749985] Re: dpkg: error processing package libc-bin (--configure): triggers looping, abandoned

[themusicgod1]

using aptitude:

removed ufw, libav-tools
reinstalled tex-common, gconf2, menu, libc-bin

and then

reinstalled libav-tools

and I did not get this error.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libav in Ubuntu.
https://bugs.launchpad.net/bugs/1749985

Title:
  dpkg: error processing package libc-bin (--configure):  triggers
  looping, abandoned

Status in gconf2 package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in libav package in Ubuntu:
  New
Status in ufw package in Ubuntu:
  New

Bug description:
  While installing the latest round of updates for bionic via aptitude:

  Setting up libav-tools (7:3.4.2-1) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
ufw -> gconf2
   packages' pending triggers which are or may be unresolvable:
libc-bin: ldconfig
menu: /usr/share/menu
tex-common: texmf-format
gconf2: /usr/share/GConf/gsettings
ufw: /etc/ufw/applications.d
  dpkg: error processing package libc-bin (--configure):
   triggers looping, abandoned
  ...
  Setting up python3-all-dev (3.6.4-1) ...
  Processing triggers for menu (2.1.47ubuntu1) ...
  Processing triggers for tex-common (6.09) ...
  Building format(s) --all.
This may take some time... done.
  Errors were encountered while processing:
   libc-bin
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  Setting up libc-bin (2.26-0ubuntu2) ...
  Press Return to continue, 'q' followed by Return to quit.

  Ubuntu: bionic 18.04

  dpkg:
Installed: 1.19.0.5ubuntu1
Candidate: 1.19.0.5ubuntu1
Version table:
   *** 1.19.0.5ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  aptitude:
Installed: 0.8.10-6ubuntu1
Candidate: 0.8.10-6ubuntu1
Version table:
   *** 0.8.10-6ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  libc-bin:
Installed: 2.26-0ubuntu2
Candidate: 2.26-0ubuntu2
Version table:
   *** 2.26-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  menu:
Installed: 2.1.47ubuntu1
Candidate: 2.1.47ubuntu1
Version table:
   *** 2.1.47ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  tex-common:
Installed: 6.09
Candidate: 6.09
Version table:
   *** 6.09 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status
  gconf2:
Installed: 3.2.6-4ubuntu1
Candidate: 3.2.6-4ubuntu1
Version table:
   *** 3.2.6-4ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  ufw:
Installed: 0.35-5
Candidate: 0.35-5
Version table:
   *** 0.35-5 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status
  libav-tools:
Installed: 7:3.4.2-1
Candidate: 7:3.4.2-1
Version table:
   *** 7:3.4.2-1 500
  500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libc-bin 2.26-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Fri Feb 16 16:08:12 2018
  Dependencies:
   gcc-8-base 8-20180208-0ubuntu1
   libc6 2.26-0ubuntu2
   libgcc1 1:8-20180208-0ubuntu1
  InstallationDate: Installed on 2016-05-07 (649 days ago)
  InstallationMedia:
   
  JournalErrors:
   Hint: You are currently not seeing messages from other users and the system.
 Users in groups 'adm', 'systemd-journal' can see all messages.
 Pass -q to turn off this notice.
   -- Logs begin at Thu 2018-01-04 17:12:35 UTC, end at Fri 2018-02-16 04:45:37 
UTC. --
   -- No entries --
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: glibc
  UpgradeStatus: Upgraded to bionic on 2017-11-20 (87 days ago)

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

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

[Desktop-packages] [Bug 1749985] Re: dpkg: error processing package libc-bin (--configure): triggers looping, abandoned

[themusicgod1]

installed packages via dpkg -l

** Attachment added: "installed packages via dpkg -l"
   
https://bugs.launchpad.net/ubuntu/+source/gconf2/+bug/1749985/+attachment/5056751/+files/installed.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libav in Ubuntu.
https://bugs.launchpad.net/bugs/1749985

Title:
  dpkg: error processing package libc-bin (--configure):  triggers
  looping, abandoned

Status in gconf2 package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in libav package in Ubuntu:
  New
Status in ufw package in Ubuntu:
  New

Bug description:
  While installing the latest round of updates for bionic via aptitude:

  Setting up libav-tools (7:3.4.2-1) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
ufw -> gconf2
   packages' pending triggers which are or may be unresolvable:
libc-bin: ldconfig
menu: /usr/share/menu
tex-common: texmf-format
gconf2: /usr/share/GConf/gsettings
ufw: /etc/ufw/applications.d
  dpkg: error processing package libc-bin (--configure):
   triggers looping, abandoned
  ...
  Setting up python3-all-dev (3.6.4-1) ...
  Processing triggers for menu (2.1.47ubuntu1) ...
  Processing triggers for tex-common (6.09) ...
  Building format(s) --all.
This may take some time... done.
  Errors were encountered while processing:
   libc-bin
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  Setting up libc-bin (2.26-0ubuntu2) ...
  Press Return to continue, 'q' followed by Return to quit.

  Ubuntu: bionic 18.04

  dpkg:
Installed: 1.19.0.5ubuntu1
Candidate: 1.19.0.5ubuntu1
Version table:
   *** 1.19.0.5ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  aptitude:
Installed: 0.8.10-6ubuntu1
Candidate: 0.8.10-6ubuntu1
Version table:
   *** 0.8.10-6ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  libc-bin:
Installed: 2.26-0ubuntu2
Candidate: 2.26-0ubuntu2
Version table:
   *** 2.26-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  menu:
Installed: 2.1.47ubuntu1
Candidate: 2.1.47ubuntu1
Version table:
   *** 2.1.47ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  tex-common:
Installed: 6.09
Candidate: 6.09
Version table:
   *** 6.09 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status
  gconf2:
Installed: 3.2.6-4ubuntu1
Candidate: 3.2.6-4ubuntu1
Version table:
   *** 3.2.6-4ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  ufw:
Installed: 0.35-5
Candidate: 0.35-5
Version table:
   *** 0.35-5 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status
  libav-tools:
Installed: 7:3.4.2-1
Candidate: 7:3.4.2-1
Version table:
   *** 7:3.4.2-1 500
  500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libc-bin 2.26-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Fri Feb 16 16:08:12 2018
  Dependencies:
   gcc-8-base 8-20180208-0ubuntu1
   libc6 2.26-0ubuntu2
   libgcc1 1:8-20180208-0ubuntu1
  InstallationDate: Installed on 2016-05-07 (649 days ago)
  InstallationMedia:
   
  JournalErrors:
   Hint: You are currently not seeing messages from other users and the system.
 Users in groups 'adm', 'systemd-journal' can see all messages.
 Pass -q to turn off this notice.
   -- Logs begin at Thu 2018-01-04 17:12:35 UTC, end at Fri 2018-02-16 04:45:37 
UTC. --
   -- No entries --
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: glibc
  UpgradeStatus: Upgraded to bionic on 2017-11-20 (87 days ago)

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

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

[Desktop-packages] [Bug 1749985] [NEW] dpkg: error processing package libc-bin (--configure): triggers looping, abandoned

[themusicgod1]

Public bug reported:

While installing the latest round of updates for bionic via aptitude:

Setting up libav-tools (7:3.4.2-1) ...
dpkg: cycle found while processing triggers:
 chain of packages whose triggers are or may be responsible:
  ufw -> gconf2
 packages' pending triggers which are or may be unresolvable:
  libc-bin: ldconfig
  menu: /usr/share/menu
  tex-common: texmf-format
  gconf2: /usr/share/GConf/gsettings
  ufw: /etc/ufw/applications.d
dpkg: error processing package libc-bin (--configure):
 triggers looping, abandoned
...
Setting up python3-all-dev (3.6.4-1) ...
Processing triggers for menu (2.1.47ubuntu1) ...
Processing triggers for tex-common (6.09) ...
Building format(s) --all.
This may take some time... done.
Errors were encountered while processing:
 libc-bin
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up libc-bin (2.26-0ubuntu2) ...
Press Return to continue, 'q' followed by Return to quit.

Ubuntu: bionic 18.04

dpkg:
  Installed: 1.19.0.5ubuntu1
  Candidate: 1.19.0.5ubuntu1
  Version table:
 *** 1.19.0.5ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
aptitude:
  Installed: 0.8.10-6ubuntu1
  Candidate: 0.8.10-6ubuntu1
  Version table:
 *** 0.8.10-6ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
libc-bin:
  Installed: 2.26-0ubuntu2
  Candidate: 2.26-0ubuntu2
  Version table:
 *** 2.26-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
menu:
  Installed: 2.1.47ubuntu1
  Candidate: 2.1.47ubuntu1
  Version table:
 *** 2.1.47ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
100 /var/lib/dpkg/status
tex-common:
  Installed: 6.09
  Candidate: 6.09
  Version table:
 *** 6.09 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages
100 /var/lib/dpkg/status
gconf2:
  Installed: 3.2.6-4ubuntu1
  Candidate: 3.2.6-4ubuntu1
  Version table:
 *** 3.2.6-4ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
100 /var/lib/dpkg/status
ufw:
  Installed: 0.35-5
  Candidate: 0.35-5
  Version table:
 *** 0.35-5 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages
100 /var/lib/dpkg/status
libav-tools:
  Installed: 7:3.4.2-1
  Candidate: 7:3.4.2-1
  Version table:
 *** 7:3.4.2-1 500
500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic/universe i386 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libc-bin 2.26-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Fri Feb 16 16:08:12 2018
Dependencies:
 gcc-8-base 8-20180208-0ubuntu1
 libc6 2.26-0ubuntu2
 libgcc1 1:8-20180208-0ubuntu1
InstallationDate: Installed on 2016-05-07 (649 days ago)
InstallationMedia:
 
JournalErrors:
 Hint: You are currently not seeing messages from other users and the system.
   Users in groups 'adm', 'systemd-journal' can see all messages.
   Pass -q to turn off this notice.
 -- Logs begin at Thu 2018-01-04 17:12:35 UTC, end at Fri 2018-02-16 04:45:37 
UTC. --
 -- No entries --
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: glibc
UpgradeStatus: Upgraded to bionic on 2017-11-20 (87 days ago)

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

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

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

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


** Tags: amd64 apport-bug bionic

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

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libav in Ubuntu.
https://bugs.launchpad.net/bugs/1749985

Title:
  dpkg: error processing package libc-bin (--configure):  triggers
  looping, abandoned

Status in gconf2 package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in libav package in Ubuntu:
  New
Status in ufw package in Ubuntu:
  New

Bug description:
  While installing the latest round of updates for bionic via aptitude:

  Setting up libav-tools (7:3.4.2-1) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
uf

[Desktop-packages] [Bug 1747706] [NEW] 'copy to clipboard' only copy/pastes the first 127 rows into gimp

[themusicgod1]

Public bug reported:

0) have a gimp running
1) run gnome-screenshot
2) take screen shot
3) click copy to clipboard
4) alt-tab to gimp
5) edit
6) paste as new image

The new image has 127 rows of the screenshot data followed by the
correct number of other rows EXCEPT the other rows are of a single
greyish colour (0x979899).

(Saving the screenshot to file, and opening file in gimp works fine as a
workaround for opening screen data in gimp)

What should happen

When you 'copy to clipboard' it should copy the whole image to clipboard.
and 'paste' should retrieve the image data from clipboard into the gimp canvas.

(Whether this is a gimp issue retrieving from clipboard or gnome-
screenshot giving the data to clipboard I am not sure, but somewhere the
clipboard data is not being passed properly)

 Ubuntu : 17.10 artful
 Desktop: gnome/wayland
 gimp : 2.8.20-1
 gnome-screenshot : 3.25.0-0ubuntu2

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-screenshot 3.25.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb  6 11:07:59 2018
InstallationDate: Installed on 2017-04-18 (293 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
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.
SourcePackage: gnome-screenshot
UpgradeStatus: Upgraded to artful on 2017-10-19 (109 days ago)

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

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


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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screenshot in Ubuntu.
https://bugs.launchpad.net/bugs/1747706

Title:
  'copy to clipboard' only copy/pastes the first 127 rows into gimp

Status in gimp package in Ubuntu:
  New
Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  0) have a gimp running
  1) run gnome-screenshot
  2) take screen shot
  3) click copy to clipboard
  4) alt-tab to gimp
  5) edit
  6) paste as new image

  The new image has 127 rows of the screenshot data followed by the
  correct number of other rows EXCEPT the other rows are of a single
  greyish colour (0x979899).

  (Saving the screenshot to file, and opening file in gimp works fine as
  a workaround for opening screen data in gimp)

  What should happen

  When you 'copy to clipboard' it should copy the whole image to clipboard.
  and 'paste' should retrieve the image data from clipboard into the gimp 
canvas.

  (Whether this is a gimp issue retrieving from clipboard or gnome-
  screenshot giving the data to clipboard I am not sure, but somewhere
  the clipboard data is not being passed properly)

   Ubuntu : 17.10 artful
   Desktop: gnome/wayland
   gimp : 2.8.20-1
   gnome-screenshot : 3.25.0-0ubuntu2

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-screenshot 3.25.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  6 11:07:59 2018
  InstallationDate: Installed on 2017-04-18 (293 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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.
  SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to artful on 2017-10-19 (109 days ago)

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

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

[Desktop-packages] [Bug 1738050] Re: [drm] GPU HANG: ecode 9:0:0x84dfbffc, in Xwayland [2102], reason: Hang on rcs0, action: reset

[themusicgod1]

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

https://bugs.archlinux.org/task/55629 claims this issue(if it is the
same issue) is fixed in the linux kernel itself ( 4.13.5-1 )

(also relevant 
https://groups.google.com/forum/?_escaped_fragment_=topic/android-x86/BdssZxkt1Gs#!topic/android-x86/BdssZxkt1Gs
 
https://bugs.freedesktop.org/show_bug.cgi?id=103076 
https://bugs.freedesktop.org/show_bug.cgi?id=89360 
https://bugs.freedesktop.org/show_bug.cgi?id=101237

)... and there's other ubuntu bugs for this it appears, which I'll mark
as duplicate next.

** Bug watch added: freedesktop.org Bugzilla #103076
   https://bugs.freedesktop.org/show_bug.cgi?id=103076

** Bug watch added: freedesktop.org Bugzilla #89360
   https://bugs.freedesktop.org/show_bug.cgi?id=89360

** Bug watch added: freedesktop.org Bugzilla #101237
   https://bugs.freedesktop.org/show_bug.cgi?id=101237

** This bug has been marked a duplicate of bug 1723680
   GPU Hang in Xorg rcs0 drm/i915

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1738050

Title:
  [drm] GPU HANG: ecode 9:0:0x84dfbffc, in Xwayland [2102], reason: Hang
  on rcs0, action: reset

Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  Gnome/Weyland locked up while I was using my web browser(pale moon
  Version: 27.3.0 (64-bit)).  I tried to Alt-Ctrl-F1 / Alt-Ctrl-F2 but
  was just presented with a new login after what seemed like a few
  minutes of the system being unresponsive. /sys/class/drm/card0/error
  was an empty file when I went to check it.

  Very similar to #1728474 ( 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728474 ) and 
#1730184 ( https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730184 )
  , but unlike those it provided the following in syslog/kern.log:

  ubuntu: 17.10 artful
  xserver-xorg-video-intel: 2.99.917+git20170309-0ubuntu1
  gnome-shell: 3.26.2-0ubuntu0.1
  xwayland: 2:1.19.5-0ubuntu2

  syslog

  Dec 13 12:18:05 eva kernel: [393803.048295] [drm] GPU HANG: ecode 
9:0:0x84dfbffc, in Xwayland [2102], reason: Hang on rcs0, action: reset
  Dec 13 12:18:05 eva kernel: [393803.048297] [drm] GPU hangs can indicate a 
bug anywhere in the entire gfx stack, including userspace.
  Dec 13 12:18:05 eva kernel: [393803.048299] [drm] Please file a _new_ bug 
report on bugs.freedesktop.org against DRI -> DRM/Intel
  Dec 13 12:18:05 eva kernel: [393803.048300] [drm] drm/i915 developers can 
then reassign to the right component if it's not a kernel issue.
  Dec 13 12:18:05 eva kernel: [393803.048301] [drm] The gpu crash dump is 
required to analyze gpu hangs, so please always attach it.
  Dec 13 12:18:05 eva kernel: [393803.048303] [drm] GPU crash dump saved to 
/sys/class/drm/card0/error
  Dec 13 12:18:05 eva kernel: [393803.048372] drm/i915: Resetting chip after 
gpu hang
  Dec 13 12:18:05 eva kernel: [393803.048568] [drm] RC6 on
  Dec 13 12:18:08 eva kernel: [393806.116135] asynchronous wait on fence 
i915:gnome-shell[2071]/1:d8ce9 timed out
  Dec 13 12:18:12 eva kernel: [393811.044302] drm/i915: Resetting chip after 
gpu hang
  Dec 13 12:18:12 eva kernel: [393811.044433] [drm] RC6 on
  Dec 13 12:18:21 eva kernel: [393819.176496] drm/i915: Resetting chip after 
gpu hang
  Dec 13 12:18:21 eva kernel: [393819.176881] [drm] RC6 on
  Dec 13 12:18:28 eva kernel: [393827.044627] drm/i915: Resetting chip after 
gpu hang
  Dec 13 12:18:29 eva kernel: [393827.044867] [drm] RC6 on
  Dec 13 12:18:37 eva kernel: [393835.048780] drm/i915: Resetting chip after 
gpu hang
  Dec 13 12:18:37 eva kernel: [393835.050029] [drm] RC6 on
  Dec 13 12:18:37 eva org.gnome.Shell.desktop[2071]: intel_do_flush_locked 
failed: Input/output error
  Dec 13 12:18:37 eva gnome-shell[2071]: Connection to xwayland lost
  Dec 13 12:18:37 eva kernel: [393835.251940] do_trap: 32 callbacks suppressed
  Dec 13 12:18:37 eva kernel: [393835.251944] traps: gnome-shell[2071] trap 
int3 ip:7f30322a6961 sp:7ffece458ea0 error:0 in 
libglib-2.0.so.0.5400.1[7f3032256000+111000]
  Dec 13 12:18:37 eva org.a11y.atspi.Registry[2115]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0"
  Dec 13 12:18:37 eva org.a11y.atspi.Registry[2115]:   after 264385 
requests (264385 known processed) with 0 events remaining. 

  kern.log

  Dec 13 12:18:05 eva kernel: [393803.048295] [drm] GPU HANG: ecode 
9:0:0x84dfbffc, in Xwayland [2102], reason: Hang on rcs0, action: reset
  Dec 13 12:18:05 eva kernel: [393803.048297] [drm] GPU hangs can indicate a 
bug anywhere in the entire gfx stack, including userspace.
  Dec 13 12:18:05 eva kernel: [393803.048299] [drm] Please file a _new_ bug 
report on bugs.freedesktop.org against DRI -> DRM/Intel
  Dec 13 12:18:05 eva kernel: [393803.048300] [drm] drm/i915 developers can 
then reassign to the right component if it's not a kernel 

[Desktop-packages] [Bug 1738050] Re: [drm] GPU HANG: ecode 9:0:0x84dfbffc, in Xwayland [2102], reason: Hang on rcs0, action: reset

[themusicgod1]

this looks very similar to
https://bugzilla.freedesktop.org/show_bug.cgi?id=103745

** Bug watch added: freedesktop.org Bugzilla #103745
   https://bugs.freedesktop.org/show_bug.cgi?id=103745

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1738050

Title:
  [drm] GPU HANG: ecode 9:0:0x84dfbffc, in Xwayland [2102], reason: Hang
  on rcs0, action: reset

Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  Gnome/Weyland locked up while I was using my web browser(pale moon
  Version: 27.3.0 (64-bit)).  I tried to Alt-Ctrl-F1 / Alt-Ctrl-F2 but
  was just presented with a new login after what seemed like a few
  minutes of the system being unresponsive. /sys/class/drm/card0/error
  was an empty file when I went to check it.

  Very similar to #1728474 ( 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728474 ) and 
#1730184 ( https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730184 )
  , but unlike those it provided the following in syslog/kern.log:

  ubuntu: 17.10 artful
  xserver-xorg-video-intel: 2.99.917+git20170309-0ubuntu1
  gnome-shell: 3.26.2-0ubuntu0.1
  xwayland: 2:1.19.5-0ubuntu2

  syslog

  Dec 13 12:18:05 eva kernel: [393803.048295] [drm] GPU HANG: ecode 
9:0:0x84dfbffc, in Xwayland [2102], reason: Hang on rcs0, action: reset
  Dec 13 12:18:05 eva kernel: [393803.048297] [drm] GPU hangs can indicate a 
bug anywhere in the entire gfx stack, including userspace.
  Dec 13 12:18:05 eva kernel: [393803.048299] [drm] Please file a _new_ bug 
report on bugs.freedesktop.org against DRI -> DRM/Intel
  Dec 13 12:18:05 eva kernel: [393803.048300] [drm] drm/i915 developers can 
then reassign to the right component if it's not a kernel issue.
  Dec 13 12:18:05 eva kernel: [393803.048301] [drm] The gpu crash dump is 
required to analyze gpu hangs, so please always attach it.
  Dec 13 12:18:05 eva kernel: [393803.048303] [drm] GPU crash dump saved to 
/sys/class/drm/card0/error
  Dec 13 12:18:05 eva kernel: [393803.048372] drm/i915: Resetting chip after 
gpu hang
  Dec 13 12:18:05 eva kernel: [393803.048568] [drm] RC6 on
  Dec 13 12:18:08 eva kernel: [393806.116135] asynchronous wait on fence 
i915:gnome-shell[2071]/1:d8ce9 timed out
  Dec 13 12:18:12 eva kernel: [393811.044302] drm/i915: Resetting chip after 
gpu hang
  Dec 13 12:18:12 eva kernel: [393811.044433] [drm] RC6 on
  Dec 13 12:18:21 eva kernel: [393819.176496] drm/i915: Resetting chip after 
gpu hang
  Dec 13 12:18:21 eva kernel: [393819.176881] [drm] RC6 on
  Dec 13 12:18:28 eva kernel: [393827.044627] drm/i915: Resetting chip after 
gpu hang
  Dec 13 12:18:29 eva kernel: [393827.044867] [drm] RC6 on
  Dec 13 12:18:37 eva kernel: [393835.048780] drm/i915: Resetting chip after 
gpu hang
  Dec 13 12:18:37 eva kernel: [393835.050029] [drm] RC6 on
  Dec 13 12:18:37 eva org.gnome.Shell.desktop[2071]: intel_do_flush_locked 
failed: Input/output error
  Dec 13 12:18:37 eva gnome-shell[2071]: Connection to xwayland lost
  Dec 13 12:18:37 eva kernel: [393835.251940] do_trap: 32 callbacks suppressed
  Dec 13 12:18:37 eva kernel: [393835.251944] traps: gnome-shell[2071] trap 
int3 ip:7f30322a6961 sp:7ffece458ea0 error:0 in 
libglib-2.0.so.0.5400.1[7f3032256000+111000]
  Dec 13 12:18:37 eva org.a11y.atspi.Registry[2115]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0"
  Dec 13 12:18:37 eva org.a11y.atspi.Registry[2115]:   after 264385 
requests (264385 known processed) with 0 events remaining. 

  kern.log

  Dec 13 12:18:05 eva kernel: [393803.048295] [drm] GPU HANG: ecode 
9:0:0x84dfbffc, in Xwayland [2102], reason: Hang on rcs0, action: reset
  Dec 13 12:18:05 eva kernel: [393803.048297] [drm] GPU hangs can indicate a 
bug anywhere in the entire gfx stack, including userspace.
  Dec 13 12:18:05 eva kernel: [393803.048299] [drm] Please file a _new_ bug 
report on bugs.freedesktop.org against DRI -> DRM/Intel
  Dec 13 12:18:05 eva kernel: [393803.048300] [drm] drm/i915 developers can 
then reassign to the right component if it's not a kernel issue.
  Dec 13 12:18:05 eva kernel: [393803.048301] [drm] The gpu crash dump is 
required to analyze gpu hangs, so please always attach it.
  Dec 13 12:18:05 eva kernel: [393803.048303] [drm] GPU crash dump saved to 
/sys/class/drm/card0/error
  Dec 13 12:18:05 eva kernel: [393803.048372] drm/i915: Resetting chip after 
gpu hang
  Dec 13 12:18:05 eva kernel: [393803.048568] [drm] RC6 on
  Dec 13 12:18:08 eva kernel: [393806.116135] asynchronous wait on fence 
i915:gnome-shell[2071]/1:d8ce9 timed out
  Dec 13 12:18:12 eva kernel: [393811.044302] drm/i915: Resetting chip after 
gpu hang
  Dec 13 12:18:12 eva kernel: [393811.044433] [drm] RC6 on
  Dec 13 12:18:21 eva kernel: [393819.176496] drm/i915: Resetting chip after 
gpu hang
  Dec 13 12:18:21 eva kernel: [393819.176881] [drm] RC6 on
  Dec 13 12:18:28 eva kernel

[Desktop-packages] [Bug 1738050] Re: [drm] GPU HANG: ecode 9:0:0x84dfbffc, in Xwayland [2102], reason: Hang on rcs0, action: reset

[themusicgod1]

this time it had an additional message:

Jan  2 06:55:10 eva kernel: [1421025.300859] ath: phy0: DMA failed to stop in 
10 ms AR_CR=0x0024 AR_DIAG_SW=0x4220 DMADBG_7=0x02c0
Jan  2 09:25:54 eva kernel: [1430069.377369] [drm:intel_fbc_work_fn [i915]] 
*ERROR* vblank not available for FBC on pipe A
Jan  2 14:56:04 eva kernel: [1449879.399238] [drm] GPU HANG: ecode 
9:0:0x84dfbffc, in Xwayland [1347], reason: Hang on rcs0, action: reset
Jan  2 14:56:04 eva kernel: [1449879.399316] drm/i915: Resetting chip after gpu 
hang
Jan  2 14:56:04 eva kernel: [1449879.400080] [drm] RC6 on

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1738050

Title:
  [drm] GPU HANG: ecode 9:0:0x84dfbffc, in Xwayland [2102], reason: Hang
  on rcs0, action: reset

Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  Gnome/Weyland locked up while I was using my web browser(pale moon
  Version: 27.3.0 (64-bit)).  I tried to Alt-Ctrl-F1 / Alt-Ctrl-F2 but
  was just presented with a new login after what seemed like a few
  minutes of the system being unresponsive. /sys/class/drm/card0/error
  was an empty file when I went to check it.

  Very similar to #1728474 ( 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728474 ) and 
#1730184 ( https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730184 )
  , but unlike those it provided the following in syslog/kern.log:

  ubuntu: 17.10 artful
  xserver-xorg-video-intel: 2.99.917+git20170309-0ubuntu1
  gnome-shell: 3.26.2-0ubuntu0.1
  xwayland: 2:1.19.5-0ubuntu2

  syslog

  Dec 13 12:18:05 eva kernel: [393803.048295] [drm] GPU HANG: ecode 
9:0:0x84dfbffc, in Xwayland [2102], reason: Hang on rcs0, action: reset
  Dec 13 12:18:05 eva kernel: [393803.048297] [drm] GPU hangs can indicate a 
bug anywhere in the entire gfx stack, including userspace.
  Dec 13 12:18:05 eva kernel: [393803.048299] [drm] Please file a _new_ bug 
report on bugs.freedesktop.org against DRI -> DRM/Intel
  Dec 13 12:18:05 eva kernel: [393803.048300] [drm] drm/i915 developers can 
then reassign to the right component if it's not a kernel issue.
  Dec 13 12:18:05 eva kernel: [393803.048301] [drm] The gpu crash dump is 
required to analyze gpu hangs, so please always attach it.
  Dec 13 12:18:05 eva kernel: [393803.048303] [drm] GPU crash dump saved to 
/sys/class/drm/card0/error
  Dec 13 12:18:05 eva kernel: [393803.048372] drm/i915: Resetting chip after 
gpu hang
  Dec 13 12:18:05 eva kernel: [393803.048568] [drm] RC6 on
  Dec 13 12:18:08 eva kernel: [393806.116135] asynchronous wait on fence 
i915:gnome-shell[2071]/1:d8ce9 timed out
  Dec 13 12:18:12 eva kernel: [393811.044302] drm/i915: Resetting chip after 
gpu hang
  Dec 13 12:18:12 eva kernel: [393811.044433] [drm] RC6 on
  Dec 13 12:18:21 eva kernel: [393819.176496] drm/i915: Resetting chip after 
gpu hang
  Dec 13 12:18:21 eva kernel: [393819.176881] [drm] RC6 on
  Dec 13 12:18:28 eva kernel: [393827.044627] drm/i915: Resetting chip after 
gpu hang
  Dec 13 12:18:29 eva kernel: [393827.044867] [drm] RC6 on
  Dec 13 12:18:37 eva kernel: [393835.048780] drm/i915: Resetting chip after 
gpu hang
  Dec 13 12:18:37 eva kernel: [393835.050029] [drm] RC6 on
  Dec 13 12:18:37 eva org.gnome.Shell.desktop[2071]: intel_do_flush_locked 
failed: Input/output error
  Dec 13 12:18:37 eva gnome-shell[2071]: Connection to xwayland lost
  Dec 13 12:18:37 eva kernel: [393835.251940] do_trap: 32 callbacks suppressed
  Dec 13 12:18:37 eva kernel: [393835.251944] traps: gnome-shell[2071] trap 
int3 ip:7f30322a6961 sp:7ffece458ea0 error:0 in 
libglib-2.0.so.0.5400.1[7f3032256000+111000]
  Dec 13 12:18:37 eva org.a11y.atspi.Registry[2115]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0"
  Dec 13 12:18:37 eva org.a11y.atspi.Registry[2115]:   after 264385 
requests (264385 known processed) with 0 events remaining. 

  kern.log

  Dec 13 12:18:05 eva kernel: [393803.048295] [drm] GPU HANG: ecode 
9:0:0x84dfbffc, in Xwayland [2102], reason: Hang on rcs0, action: reset
  Dec 13 12:18:05 eva kernel: [393803.048297] [drm] GPU hangs can indicate a 
bug anywhere in the entire gfx stack, including userspace.
  Dec 13 12:18:05 eva kernel: [393803.048299] [drm] Please file a _new_ bug 
report on bugs.freedesktop.org against DRI -> DRM/Intel
  Dec 13 12:18:05 eva kernel: [393803.048300] [drm] drm/i915 developers can 
then reassign to the right component if it's not a kernel issue.
  Dec 13 12:18:05 eva kernel: [393803.048301] [drm] The gpu crash dump is 
required to analyze gpu hangs, so please always attach it.
  Dec 13 12:18:05 eva kernel: [393803.048303] [drm] GPU crash dump saved to 
/sys/class/drm/card0/error
  Dec 13 12:18:05 eva kernel: [393803.048372] drm/i915: Resetting chip after 
gpu hang
  Dec 13 12:18:05 eva kernel: [393803.048568] [drm] RC6 on
  Dec 13 12:18:08 eva kernel: [393

[Desktop-packages] [Bug 1738050] [NEW] [drm] GPU HANG: ecode 9:0:0x84dfbffc, in Xwayland [2102], reason: Hang on rcs0, action: reset

[themusicgod1]

Public bug reported:

Gnome/Weyland locked up while I was using my web browser(pale moon
Version: 27.3.0 (64-bit)).  I tried to Alt-Ctrl-F1 / Alt-Ctrl-F2 but was
just presented with a new login after what seemed like a few minutes of
the system being unresponsive. /sys/class/drm/card0/error was an empty
file when I went to check it.

Very similar to #1728474 ( 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728474 ) and 
#1730184 ( https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730184 )
, but unlike those it provided the following in syslog/kern.log:

ubuntu: 17.10 artful
xserver-xorg-video-intel: 2.99.917+git20170309-0ubuntu1
gnome-shell: 3.26.2-0ubuntu0.1
xwayland: 2:1.19.5-0ubuntu2

syslog

Dec 13 12:18:05 eva kernel: [393803.048295] [drm] GPU HANG: ecode 
9:0:0x84dfbffc, in Xwayland [2102], reason: Hang on rcs0, action: reset
Dec 13 12:18:05 eva kernel: [393803.048297] [drm] GPU hangs can indicate a bug 
anywhere in the entire gfx stack, including userspace.
Dec 13 12:18:05 eva kernel: [393803.048299] [drm] Please file a _new_ bug 
report on bugs.freedesktop.org against DRI -> DRM/Intel
Dec 13 12:18:05 eva kernel: [393803.048300] [drm] drm/i915 developers can then 
reassign to the right component if it's not a kernel issue.
Dec 13 12:18:05 eva kernel: [393803.048301] [drm] The gpu crash dump is 
required to analyze gpu hangs, so please always attach it.
Dec 13 12:18:05 eva kernel: [393803.048303] [drm] GPU crash dump saved to 
/sys/class/drm/card0/error
Dec 13 12:18:05 eva kernel: [393803.048372] drm/i915: Resetting chip after gpu 
hang
Dec 13 12:18:05 eva kernel: [393803.048568] [drm] RC6 on
Dec 13 12:18:08 eva kernel: [393806.116135] asynchronous wait on fence 
i915:gnome-shell[2071]/1:d8ce9 timed out
Dec 13 12:18:12 eva kernel: [393811.044302] drm/i915: Resetting chip after gpu 
hang
Dec 13 12:18:12 eva kernel: [393811.044433] [drm] RC6 on
Dec 13 12:18:21 eva kernel: [393819.176496] drm/i915: Resetting chip after gpu 
hang
Dec 13 12:18:21 eva kernel: [393819.176881] [drm] RC6 on
Dec 13 12:18:28 eva kernel: [393827.044627] drm/i915: Resetting chip after gpu 
hang
Dec 13 12:18:29 eva kernel: [393827.044867] [drm] RC6 on
Dec 13 12:18:37 eva kernel: [393835.048780] drm/i915: Resetting chip after gpu 
hang
Dec 13 12:18:37 eva kernel: [393835.050029] [drm] RC6 on
Dec 13 12:18:37 eva org.gnome.Shell.desktop[2071]: intel_do_flush_locked 
failed: Input/output error
Dec 13 12:18:37 eva gnome-shell[2071]: Connection to xwayland lost
Dec 13 12:18:37 eva kernel: [393835.251940] do_trap: 32 callbacks suppressed
Dec 13 12:18:37 eva kernel: [393835.251944] traps: gnome-shell[2071] trap int3 
ip:7f30322a6961 sp:7ffece458ea0 error:0 in 
libglib-2.0.so.0.5400.1[7f3032256000+111000]
Dec 13 12:18:37 eva org.a11y.atspi.Registry[2115]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0"
Dec 13 12:18:37 eva org.a11y.atspi.Registry[2115]:   after 264385 requests 
(264385 known processed) with 0 events remaining. 

kern.log

Dec 13 12:18:05 eva kernel: [393803.048295] [drm] GPU HANG: ecode 
9:0:0x84dfbffc, in Xwayland [2102], reason: Hang on rcs0, action: reset
Dec 13 12:18:05 eva kernel: [393803.048297] [drm] GPU hangs can indicate a bug 
anywhere in the entire gfx stack, including userspace.
Dec 13 12:18:05 eva kernel: [393803.048299] [drm] Please file a _new_ bug 
report on bugs.freedesktop.org against DRI -> DRM/Intel
Dec 13 12:18:05 eva kernel: [393803.048300] [drm] drm/i915 developers can then 
reassign to the right component if it's not a kernel issue.
Dec 13 12:18:05 eva kernel: [393803.048301] [drm] The gpu crash dump is 
required to analyze gpu hangs, so please always attach it.
Dec 13 12:18:05 eva kernel: [393803.048303] [drm] GPU crash dump saved to 
/sys/class/drm/card0/error
Dec 13 12:18:05 eva kernel: [393803.048372] drm/i915: Resetting chip after gpu 
hang
Dec 13 12:18:05 eva kernel: [393803.048568] [drm] RC6 on
Dec 13 12:18:08 eva kernel: [393806.116135] asynchronous wait on fence 
i915:gnome-shell[2071]/1:d8ce9 timed out
Dec 13 12:18:12 eva kernel: [393811.044302] drm/i915: Resetting chip after gpu 
hang
Dec 13 12:18:12 eva kernel: [393811.044433] [drm] RC6 on
Dec 13 12:18:21 eva kernel: [393819.176496] drm/i915: Resetting chip after gpu 
hang
Dec 13 12:18:21 eva kernel: [393819.176881] [drm] RC6 on
Dec 13 12:18:28 eva kernel: [393827.044627] drm/i915: Resetting chip after gpu 
hang
Dec 13 12:18:29 eva kernel: [393827.044867] [drm] RC6 on
Dec 13 12:18:37 eva kernel: [393835.048780] drm/i915: Resetting chip after gpu 
hang
Dec 13 12:18:37 eva kernel: [393835.050029] [drm] RC6 on
Dec 13 12:18:37 eva kernel: [393835.251940] do_trap: 32 callbacks suppressed
Dec 13 12:18:37 eva kernel: [393835.251944] traps: gnome-shell[2071] trap int3 
ip:7f30322a6961 sp:7ffece458ea0 error:0 in 
libglib-2.0.so.0.5400.1[7f3032256000+111000]
Dec 13 12:18:37 eva kernel: [393835.810878] bitcoin-msghand[2826]: segfault at 
50 ip 557cc56cbb74 sp 7f2c927fa9c0 error 4 in 
b

[Desktop-packages] [Bug 508618] Re: Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp

[themusicgod1]

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

** Also affects: emacs25 (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882957
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs24 in Ubuntu.
https://bugs.launchpad.net/bugs/508618

Title:
  Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp

Status in emacs23 package in Ubuntu:
  New
Status in emacs24 package in Ubuntu:
  New
Status in emacs25 package in Ubuntu:
  New
Status in emacs25 package in Debian:
  Unknown

Bug description:
  Binary package hint: emacs23

  Setting max-specpdl-size higher than 34295, and then running the following 
code results in a segfault of emacs.  I am 
  running a system of mostly 9.04 with some packages (such as this one) 
upgraded. I know it's kind of pushing emacs to the limit, but still;  this 
seems like an arbitrary limit on emacs' otherwise diety-like functionality.  
What should happen is emacs should continue to fail to execute with 
"file-truename: Variable binding depth exceeds max-specpdl-size"  as it does 
below 34295., or at the very least when setting max-specpdl-size higher than 
34295 it should warn you that you are making some kind of error if this is not 
acceptable.

  example code:

  (defun por (pcurrent pb numberleft)
 (if (= numberleft 0)
   pcurrent
   (por (- (+ pcurrent pb) (* pcurrent pb)) pb (- numberleft 1

  (por 0 0.01 1)

  (setq max-lisp-eval-depth 100)  ; this may be necessary, but doesn't 
appear to be the problem
  (setq max-specpdl-size 34295)  ; setting this lower results in 
predictable, expected behaviour - emacs refuses to run the result, citing 
max-specpdl-size not high enough.   Setting this higher (like...34296), results 
in a segfault of emacs

  emacs23:
Installé : 23.1+1-4ubuntu3
Candidat : 23.1+1-4ubuntu3
   Table de version :
   *** 23.1+1-4ubuntu3 0
  100 /var/lib/dpkg/status

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  Package: emacs23 23.1+1-4ubuntu3
  ProcEnviron:
   PATH=(custom, user)
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: emacs23
  Uname: Linux 2.6.28-16-generic x86_64
  UnreportableReason: Ceci n'est pas un authentique paquet Ubuntu

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

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

[Desktop-packages] [Bug 1649768] Re: FTBFS : Segmentation fault (core dumped) ./temacs --batch

[themusicgod1]

can't reproduce in bionic/emacs25

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs24 in Ubuntu.
https://bugs.launchpad.net/bugs/1649768

Title:
  FTBFS : Segmentation fault  (core dumped) ./temacs --batch

Status in emacs24 package in Ubuntu:
  New

Bug description:
  Ubuntu: 16.10 yakkety
  emacs24:
Installed: 24.5+1-6ubuntu3
Candidate: 24.5+1-6ubuntu3
Version table:
   *** 24.5+1-6ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status
  gcc:
Installed: 4:6.1.1-1ubuntu2
Candidate: 4:6.1.1-1ubuntu2
  gcc-5:
Installed: 5.4.1-2ubuntu2
Candidate: 5.4.1-2ubuntu2
  Linux Hedy 4.8.0-22-generic #24-Ubuntu SMP Sat Oct 8 09:15:00 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

  cd debian;
  debuild -us -us -b

  ...
  gcc -Demacs  -I. -I. -I../lib -I./../lib   -pthread -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient 
-I/usr/include/mircommon -I/usr/include/mircookie -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2  
-I/usr/include/alsa -pthread -I/usr/include/librsvg-2.0 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/cairo 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 
-fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 
-I/usr/include/x86_64-linux-gnu/ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/x86_64-linux-gnu/ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/libxml2 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include   -pthread -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/freetype2 -I/usr/include/freetype2 -I/usr/include/freetype2  
-MMD -MF deps/.d -MP -I/usr/include/p11-kit-1 -pthread -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include   -g -O2 
-fdebug-prefix-map=/home/themusicgod1/emacs-24/emacs24-24.5+1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -no-pie  
-Wl,-znocombreloc  -Wl,-Bsymbolic-functions -Wl,-z,relro -no-pie  \
-o temacs  vm-limit.o dispnew.o frame.o scroll.o xdisp.o menu.o xmenu.o 
window.o charset.o coding.o category.o ccl.o character.o chartab.o bidi.o cm.o 
term.o terminal.o xfaces.o xterm.o xfns.o xselect.o xrdb.o xsmfns.o xsettings.o 
gtkutil.o emacsgtkfixed.o dbusbind.o emacs.o keyboard.o macros.o keymap.o 
sysdep.o buffer.o filelock.o insdel.o marker.o minibuf.o fileio.o dired.o 
cmds.o casetab.o casefiddle.o indent.o search.o regex.o undo.o alloc.o data.o 
doc.o editfns.o callint.o eval.o floatfns.o fns.o font.o print.o lread.o 
syntax.o unexelf.o bytecode.o process.o gnutls.o callproc.o region-cache.o 
sound.o atimer.o doprnt.o intervals.o textprop.o composite.o xml.o 
gfilenotify.o profiler.o decompress.o xfont.o ftfont.o xftfont.o ftxfont.o  
fontset.o fringe.o image.o xgselect.o  terminfo.o lastfile.o gmalloc.o ralloc.o 
   ../lib/libgnu.a   -ltiff -ljpeg -lpng16 -lz -lm -lgif -lXpm -lgtk-3 
-lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject -lcairo 
-lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lSM -lICE -lX11 -lXrender 
-lXft -lasound -lrsvg-2 -lm -lgio-2.0 -lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0 
-lcairo -lMagickWand-6.Q16 -lMagickCore-6.Q16 -lacl-lrt  -ldbus-1  -lXrandr 
-lXinerama -lxml2 -lgpm   -ltinfo  -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lgconf-2 
-lglib-2.0 -lgobject-2.0 -lglib-2.0 -lselinux -lfreetype -lfontconfig 
-lfreetype -lfreetype -lotf -lfreetype -lm17n-core -lm17n-flt -lm17n-core 
-lgnutls -lpthread  -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lm -lz
  /bin/mkdir -p ../etc
  :
  test "no" = "yes" || \
test "X" = X ||  -r temacs
  test "no" = "yes" || test -z "setfattr" || \
setfattr -n user.pax.flags -v er temacs
  cd ../lisp; /usr/bin/make -w update-subdirs
  make[4]: Entering directory 
'/home/themusicgod1/emacs-24/emacs24-24.5+1/debian/build-x/lisp'
  for file in `find . -type d -print`; do case $file in .*/cedet* | .*/leim* ) 
;; *) wins="$win

[Desktop-packages] [Bug 508618] Re: Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp

[themusicgod1]

Looks like my example code needed 'map' 
(defun map (f l) 
  "map function?"
  (if 
 (nullp l)
 '()
(if (listp l)
   (if (= 1 (length l))
  (list (funcall f (car l)))
(if (> (length l) 1)
 (cons (map f (car l))
 (map f (cdr l)
 (funcall f l)
 )))

** Tags added: bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs23 in Ubuntu.
https://bugs.launchpad.net/bugs/508618

Title:
  Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp

Status in emacs23 package in Ubuntu:
  New
Status in emacs24 package in Ubuntu:
  New
Status in emacs25 package in Ubuntu:
  New

Bug description:
  Binary package hint: emacs23

  Setting max-specpdl-size higher than 34295, and then running the following 
code results in a segfault of emacs.  I am 
  running a system of mostly 9.04 with some packages (such as this one) 
upgraded. I know it's kind of pushing emacs to the limit, but still;  this 
seems like an arbitrary limit on emacs' otherwise diety-like functionality.  
What should happen is emacs should continue to fail to execute with 
"file-truename: Variable binding depth exceeds max-specpdl-size"  as it does 
below 34295., or at the very least when setting max-specpdl-size higher than 
34295 it should warn you that you are making some kind of error if this is not 
acceptable.

  example code:

  (defun por (pcurrent pb numberleft)
 (if (= numberleft 0)
   pcurrent
   (por (- (+ pcurrent pb) (* pcurrent pb)) pb (- numberleft 1

  (por 0 0.01 1)

  (setq max-lisp-eval-depth 100)  ; this may be necessary, but doesn't 
appear to be the problem
  (setq max-specpdl-size 34295)  ; setting this lower results in 
predictable, expected behaviour - emacs refuses to run the result, citing 
max-specpdl-size not high enough.   Setting this higher (like...34296), results 
in a segfault of emacs

  emacs23:
Installé : 23.1+1-4ubuntu3
Candidat : 23.1+1-4ubuntu3
   Table de version :
   *** 23.1+1-4ubuntu3 0
  100 /var/lib/dpkg/status

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  Package: emacs23 23.1+1-4ubuntu3
  ProcEnviron:
   PATH=(custom, user)
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: emacs23
  Uname: Linux 2.6.28-16-generic x86_64
  UnreportableReason: Ceci n'est pas un authentique paquet Ubuntu

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

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

[Desktop-packages] [Bug 1730184] [NEW] org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad address

[themusicgod1]

Public bug reported:

Went to log into my fairly newly upgraded ubuntu artful system today but
was presented with a new login instead of a login with all my
applications running, similar to #1728474 (
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728474 ),
only I didn't have to Ctrl-Alt-F1 to get a new login, I was presented
with one when I came to log in in the morning.

syslog gives a clue:

Nov  5 02:17:43 eva org.gnome.Shell.desktop[29954]: intel_do_flush_locked 
failed: Bad address
Nov  5 02:17:44 eva gnome-shell[29954]: Connection to xwayland lost
Nov  5 02:17:44 eva kernel: [1339701.543472] traps: gnome-shell[29954] trap 
int3 ip:7fcceb716961 sp:7ffd8b486020 error:0 in 
libglib-2.0.so.0.5400.1[7fcceb6c6000+111000]

This, followed by everything that was running failing to various degrees
of cleanness.

intel-microcode:
  Installed: 3.20170707.1
  Candidate: 3.20170707.1
  Version table:
 *** 3.20170707.1 500
500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu 
artful/restricted amd64 Packages
500 https://mirror.its.sfu.ca/mirror/ubuntu artful/restricted amd64 
Packages
100 /var/lib/dpkg/status

xserver-xorg-video-intel:
  Installed: 2:2.99.917+git20170309-0ubuntu1
  Candidate: 2:2.99.917+git20170309-0ubuntu1
  Version table:
 *** 2:2.99.917+git20170309-0ubuntu1 500
500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/main 
amd64 Packages
500 https://mirror.its.sfu.ca/mirror/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status

libglib2.0-0:
  Installed: 2.54.1-1ubuntu1
  Candidate: 2.54.1-1ubuntu1
  Version table:
 *** 2.54.1-1ubuntu1 500
500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/main 
amd64 Packages
500 https://mirror.its.sfu.ca/mirror/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  5 07:27:04 2017
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'libreoffice-calc.desktop', 'gnome-control-center.desktop', 
'org.gnome.Terminal.desktop', 'userapp-New Moon-YU8MZY.desktop', 
'onioncircuits.desktop', 'org.gnome.Screenshot.desktop', 'emacs25.desktop', 
'ricochet-im.desktop', 'gpa.desktop', 'org.gnome.Cheese.desktop']"
 b'org.gnome.desktop.interface' b'cursor-blink-time' b'1264'
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2017-04-18 (200 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
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.
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2017-10-19 (16 days ago)

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


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

** Description changed:

  Went to log into my fairly newly upgraded ubuntu artful system today but
  was presented with a new login instead of a login with all my
- applications running, similar to #1728474, only I didn't have to Ctrl-
- Alt-F1 to get a new login, I was presented with one when I came to log
- in in the morning.
+ applications running, similar to #1728474 (
+ https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728474 ),
+ only I didn't have to Ctrl-Alt-F1 to get a new login, I was presented
+ with one when I came to log in in the morning.
  
  syslog gives a clue:
  
  Nov  5 02:17:43 eva org.gnome.Shell.desktop[29954]: intel_do_flush_locked 
failed: Bad address
  Nov  5 02:17:44 eva gnome-shell[29954]: Connection to xwayland lost
  Nov  5 02:17:44 eva kernel: [1339701.543472] traps: gnome-shell[29954] trap 
int3 ip:7fcceb716961 sp:7ffd8b486020 error:0 in 
libglib-2.0.so.0.5400.1[7fcceb6c6000+111000]
  
  This, followed by everything that was running failing to various degrees
  of cleanness.
  
  intel-microcode:
-   Installed: 3.20170707.1
-   Candidate: 3.20170707.1
-   Version table:
-  *** 3.20170707.1 500
- 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu 
artful/restricted amd64 Packages
- 500 https://mirror.its.sfu.ca/mirror/ubuntu artful/restricted amd64 
Packages
- 100 /var/lib/dpkg/status
+   Installed: 3.20170707.1
+   Candidate: 3.20170707.1
+   Version table:
+  *** 3.20170707.1 500
+ 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu 
artful/restricted amd64 Packages
+ 500 https://mirror.its.sfu.ca/m

[Desktop-packages] [Bug 1728474] [NEW] ctrl-alt-f1 closes all running programs

[themusicgod1]

Public bug reported:

Since upgrading to Ubuntu 17.10 artful when I go to tty via alt-ctrl-f1,
I am presented with a gdm3 login screen.  This in and of itself is OK,
as long as it's a lock screen.  But it's not - all of my running
programs were closed(most of them without saving).

This makes the desktop behave similar to a phone, so I could see this as
being a potential feature to some...but for those of us running servers
and all kinds of programs, with 1000s of tabs open...it's kind of an
abrupt surprise to enable by default

end result

actual behaviour: 
alt-ctrl-f1 logs out & closes all running applications

desired behaviour:
alt-ctrl-f1 either does nothing (if you are on tty 1) or locks the screen, does 
not close all running applications.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 29 22:06:55 2017
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'libreoffice-calc.desktop', 'gnome-control-center.desktop', 
'org.gnome.Terminal.desktop', 'userapp-New Moon-YU8MZY.desktop', 
'onioncircuits.desktop', 'org.gnome.Screenshot.desktop', 'emacs25.desktop', 
'ricochet-im.desktop', 'gpa.desktop', 'org.gnome.Cheese.desktop']"
 b'org.gnome.desktop.interface' b'cursor-blink-time' b'1264'
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2017-04-18 (194 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
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.
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2017-10-19 (10 days ago)

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


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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1728474

Title:
  ctrl-alt-f1 closes all running programs

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Since upgrading to Ubuntu 17.10 artful when I go to tty via alt-
  ctrl-f1, I am presented with a gdm3 login screen.  This in and of
  itself is OK, as long as it's a lock screen.  But it's not - all of my
  running programs were closed(most of them without saving).

  This makes the desktop behave similar to a phone, so I could see this
  as being a potential feature to some...but for those of us running
  servers and all kinds of programs, with 1000s of tabs open...it's kind
  of an abrupt surprise to enable by default

  end result

  actual behaviour: 
  alt-ctrl-f1 logs out & closes all running applications

  desired behaviour:
  alt-ctrl-f1 either does nothing (if you are on tty 1) or locks the screen, 
does not close all running applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 29 22:06:55 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'libreoffice-calc.desktop', 'gnome-control-center.desktop', 
'org.gnome.Terminal.desktop', 'userapp-New Moon-YU8MZY.desktop', 
'onioncircuits.desktop', 'org.gnome.Screenshot.desktop', 'emacs25.desktop', 
'ricochet-im.desktop', 'gpa.desktop', 'org.gnome.Cheese.desktop']"
   b'org.gnome.desktop.interface' b'cursor-blink-time' b'1264'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-04-18 (194 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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.
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-19 (10 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpa

[Desktop-packages] [Bug 1537146] Re: gnome-termnial visual glitch: 100% transparent

[themusicgod1]

cannot reproduce on 17.10 artful

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1537146

Title:
  gnome-termnial visual glitch: 100% transparent

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  To reproduce:

  0) open  gnome-terminal

  1) Open a profile *without* transparent background. ie a solid colour
  background

  2) position a firefox window or something with a lot of white beneath
  the majority of the gnome-terminal

  3) hit enter enough times to reach the bottom.  This should 'clear'
  the state of whether it shows transparent background or not

  4)

  > clear

  to clear the terminal and present a prompt at the top

  5)  notice that the screen is unreadable as gnome-terminal has somehow
  100% transparent background.  See screenshot.

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.04
  DISTRIB_CODENAME=trusty
  DISTRIB_DESCRIPTION="Ubuntu 14.04.3 LTS"

  * Ubuntu 12.04+unity (+/- compiz) did the same thing.

  bash:
Installed: 4.3-7ubuntu1.5
Candidate: 4.3-7ubuntu1.5
  gnome-terminal:
Installed: 3.6.2-0ubuntu1
Candidate: 3.6.2-0ubuntu1
  Openbox:
Installed: 3.5.2-6
Candidate: 3.5.2-6
  xserver-xorg-video-nouveau:
Installed: 1:1.0.10-1ubuntu2
Candidate: 1:1.0.10-1ubuntu2 
  xserver-xorg:
Installed: 1:7.7+1ubuntu8.1
Candidate: 1:7.7+1ubuntu8.1

  Other visual glitches exhibit themselves on this computer so this may
  be a nouveau issue:

  see:
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1537124

  makerspace@accounting1:~$ lspci | grep -i 'vga'
  01:00.0 VGA compatible controller: NVIDIA Corporation NV18GL [Quadro NVS 280 
SD] (rev a2)

  makerspace@accounting1:~$ uname -a
  Linux accounting1 3.13.0-76-generic #120-Ubuntu SMP Mon Jan 18 15:58:41 UTC 
2016 i686 i686 i686 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-terminal 3.6.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-76.120-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-76-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Fri Jan 22 10:11:02 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-16 (5 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to trusty on 2016-01-19 (2 days ago)

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

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

[Desktop-packages] [Bug 1682544] Re: xkill doesn't grab pointer in gnome/weyland

[themusicgod1]

** Tags added: artful

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to x11-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1682544

Title:
  xkill doesn't grab pointer in gnome/weyland

Status in x11-utils package in Ubuntu:
  Triaged

Bug description:
  1. 
  > xkill 

  expected result:
  a) output: "Select the window whose client you wish to kill with button 1..."
  b) pointer turns to an X
  c) you can click on a window
  d) that window's process gets killed

  what actually happens
  a) output: "Select the window whose client you wish to kill with button 1..."
  b) The pointer goes invisible, until you move it, then it goes to the normal 
pointer.
  ...that's it.

  Ubuntu: 17.04 / zesty
  Desktop environment: Gnome/Weyland 
  x11-utils: 7.7+3

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: x11-utils 7.7+3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Thu Apr 13 13:40:03 2017
  DistUpgraded: 2017-04-13 12:41:16,896 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: zesty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0689]
 Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0689]
  InstallationDate: Installed on 2014-07-09 (1008 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  MachineType: Acer TravelMate P273-MG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=885e04f0-bd26-4885-aa1c-f134c674b8ff ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  SourcePackage: x11-utils
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  dmi.bios.date: 11/27/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BA70_HC
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.11:bd11/27/2013:svnAcer:pnTravelMateP273-MG:pvrV2.11:rvnAcer:rnBA70_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: TravelMate P273-MG
  dmi.product.version: V2.11
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Thu Apr 13 12:45:10 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x11-utils/+bug/1682544/+subscriptions

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

[Desktop-packages] [Bug 1725389] [NEW] 'authentication required to change privacy settings' you don't actually need to authenticate

[themusicgod1]

Public bug reported:

Setup : 
* 2 users.  one of them has sudo access, the one i'm logged into (gnome/weyland 
default in artful desktop) doesn't
* ubuntu 17.10 artful 
* gnome-control-center:
  Installed: 1:3.26.1-0ubuntu4 
* redshift:
  Installed: 1.11-1ubuntu1

Went to settings->privacy->location settings and changed to location
services = on and then hit the 'x' on the 'location services' window.
it did not change from 'off' to 'on' on the 'privacy' window, however
when i restarted redshift (which until that point had not been working)
redshift immediately started working.  (This suggests to me that until
that point location services was, in fact off, and when i turned it on,
it was turned on).  However, a few seconds later the authorization
prompt came up, graying the screen asking to authenticate to make
changes to my privacy settings(the change which was already made and
working, as evidenced both by working redshift and the fact that if I
went into privacy settings, I would see location services 'in use'
instead of 'off')

"Authentication Required"
"To change your privacy settings you need to authenticate..."

I hit 'escape', and it reopened, I hit 'escape' and it went away, for
about 3 minutes.

Then it came back.  It would continue to come back, prompting me twice
every about 3 minutes until I gave the password to the user (that was
not logged in).

This seems broken.   If authentication is required to enable location
services...it shouldn't work without authentication.  If authentication
is *not* required to enable location services...it shouldn't nag you
twice every ~3 minutes until you acquiesce.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 13:21:04 2017
InstallationDate: Installed on 2017-04-18 (184 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
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.
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)

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


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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1725389

Title:
  'authentication required to change privacy settings' you don't
  actually need to authenticate

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Setup : 
  * 2 users.  one of them has sudo access, the one i'm logged into 
(gnome/weyland default in artful desktop) doesn't
  * ubuntu 17.10 artful 
  * gnome-control-center:
Installed: 1:3.26.1-0ubuntu4 
  * redshift:
Installed: 1.11-1ubuntu1

  Went to settings->privacy->location settings and changed to location
  services = on and then hit the 'x' on the 'location services' window.
  it did not change from 'off' to 'on' on the 'privacy' window, however
  when i restarted redshift (which until that point had not been
  working) redshift immediately started working.  (This suggests to me
  that until that point location services was, in fact off, and when i
  turned it on, it was turned on).  However, a few seconds later the
  authorization prompt came up, graying the screen asking to
  authenticate to make changes to my privacy settings(the change which
  was already made and working, as evidenced both by working redshift
  and the fact that if I went into privacy settings, I would see
  location services 'in use' instead of 'off')

  "Authentication Required"
  "To change your privacy settings you need to authenticate..."

  I hit 'escape', and it reopened, I hit 'escape' and it went away, for
  about 3 minutes.

  Then it came back.  It would continue to come back, prompting me twice
  every about 3 minutes until I gave the password to the user (that was
  not logged in).

  This seems broken.   If authentication is required to enable location
  services...it shouldn't work without authentication.  If
  authentication is *not* required to enable location services...it
  shouldn't nag you twice every ~3 minutes until you acquiesce.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date:

[Desktop-packages] [Bug 884122] Re: xclock -digital shows seconds but redraws on the minute

[themusicgod1]

** Tags added: artful

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to x11-apps in Ubuntu.
https://bugs.launchpad.net/bugs/884122

Title:
  xclock -digital shows seconds but redraws on the minute

Status in x11-apps package in Ubuntu:
  Confirmed

Bug description:
  i.e., on start it will show, e.g. "Mon 31 Oct 2011 09:17:15 GMT"
  (en_GB format), and stay that way for 45 seconds, then show "Mon 31
  Oct 2011 09:18:00 GMT" for a minute, etc.

  It redraws to show the correct time, including seconds, when the
  window is resized.  Window manager is Unity, version as of oneric-
  updates: 4.24.0-0ubuntu2b1 0.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: x11-apps 7.6+4ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  CheckboxSubmission: b0d31efda01870980e2e5a89390b685c
  CheckboxSystem: 6ce041aeed0a2c17b3343b66d157175d
  Date: Mon Oct 31 09:11:52 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  SourcePackage: x11-apps
  UpgradeStatus: Upgraded to oneiric on 2011-05-03 (181 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x11-apps/+bug/884122/+subscriptions

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

[Desktop-packages] [Bug 508618] Re: Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp

[themusicgod1]

** Tags added: artful

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs23 in Ubuntu.
https://bugs.launchpad.net/bugs/508618

Title:
  Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp

Status in emacs23 package in Ubuntu:
  New
Status in emacs24 package in Ubuntu:
  New
Status in emacs25 package in Ubuntu:
  New

Bug description:
  Binary package hint: emacs23

  Setting max-specpdl-size higher than 34295, and then running the following 
code results in a segfault of emacs.  I am 
  running a system of mostly 9.04 with some packages (such as this one) 
upgraded. I know it's kind of pushing emacs to the limit, but still;  this 
seems like an arbitrary limit on emacs' otherwise diety-like functionality.  
What should happen is emacs should continue to fail to execute with 
"file-truename: Variable binding depth exceeds max-specpdl-size"  as it does 
below 34295., or at the very least when setting max-specpdl-size higher than 
34295 it should warn you that you are making some kind of error if this is not 
acceptable.

  example code:

  (defun por (pcurrent pb numberleft)
 (if (= numberleft 0)
   pcurrent
   (por (- (+ pcurrent pb) (* pcurrent pb)) pb (- numberleft 1

  (por 0 0.01 1)

  (setq max-lisp-eval-depth 100)  ; this may be necessary, but doesn't 
appear to be the problem
  (setq max-specpdl-size 34295)  ; setting this lower results in 
predictable, expected behaviour - emacs refuses to run the result, citing 
max-specpdl-size not high enough.   Setting this higher (like...34296), results 
in a segfault of emacs

  emacs23:
Installé : 23.1+1-4ubuntu3
Candidat : 23.1+1-4ubuntu3
   Table de version :
   *** 23.1+1-4ubuntu3 0
  100 /var/lib/dpkg/status

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  Package: emacs23 23.1+1-4ubuntu3
  ProcEnviron:
   PATH=(custom, user)
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: emacs23
  Uname: Linux 2.6.28-16-generic x86_64
  UnreportableReason: Ceci n'est pas un authentique paquet Ubuntu

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

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

[Desktop-packages] [Bug 508618] Re: Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp

[themusicgod1]

reproduced same kind of issue in emacs 25 using slightly more
complicated lisp code, plenty of ram left:

first file seqfile1:

(setq undo-outer-limit (expt 2 23))
(setq max-lisp-eval-depth (expt 2 17))
(setq max-specpdl-size (expt 2 17))
(setq message-log-max 4)
(setq shell-command-default-error-buffer 'stderror-buffe)
(setq max-lisp-eval-depth (expt 2 16))
(defun insert (L)
  (message "insert into urls values ('%s',%i);" L counter)
  (setq counter (+ 1  counter))
)
(defun insertall (L)
  (map 'insert L))
(setq counter 28531843)
(insertall 
'(

seqfile2:
seq 11718 > seqfile1 

seqfile3:
))

cat seqfile1 seqfile2 seqfile3 > seqfile4

run each command in seqfile4 in order, same result: emacs segfault after
#77287 frames, plent of ram left

slightly different stack trace (but that could be because it's got
different lisp code leading to it)

virtual memory at segfault; 458mb 
resident memory: 75mb
shared memory 34.9mb


#0  0x7fb13d43b53f in raise (sig=sig@entry=11)
at ../sysdeps/unix/sysv/linux/raise.c:58
#1  0x004f0f04 in terminate_due_to_signal (sig=sig@entry=11, 
backtrace_limit=backtrace_limit@entry=40) at emacs.c:381
#2  0x0050929e in handle_fatal_signal (sig=sig@entry=11)
at sysdep.c:1601
#3  0x005094c9 in deliver_thread_signal (sig=sig@entry=11, 
handler=0x509290 ) at sysdep.c:1575
#4  0x0050952f in deliver_fatal_thread_signal (sig=11) at sysdep.c:1613
#5  0x0050952f in handle_sigsegv (sig=11, siginfo=, 
arg=) at sysdep.c:1695
#6  0x7fb13d43b670 in  ()
at /lib/x86_64-linux-gnu/libpthread.so.0
#7  0x004aa56c in bidi_resolve_weak 
(bidi_it=bidi_it@entry=0x7ffd69b29600) at bidi.c:2173
#8  0x004ab31f in bidi_find_bracket_pairs 
(bidi_it=bidi_it@entry=0x7ffd69b29600) at bidi.c:2679
#9  0x004ab9e5 in bidi_resolve_brackets 
(bidi_it=bidi_it@entry=0x7ffd69b29600) at bidi.c:2852
#10 0x004abadc in bidi_resolve_neutral 
(bidi_it=bidi_it@entry=0x7ffd69b29600) at bidi.c:2953
#11 0x004ac018 in bidi_type_of_next_char (bidi_it=0x7ffd69b29600)
at bidi.c:3158
#12 0x004ac018 in bidi_level_of_next_char 
(bidi_it=bidi_it@entry=0x7ffd69b29600) at bidi.c:3225
#13 0x004acf1f in bidi_move_to_visually_next 
(bidi_it=bidi_it@entry=0x7ffd69b29600) at bidi.c:3418
#14 0x00444350 in set_iterator_to_next (it=it@entry=0x7ffd69b28c60, 
reseat_p=reseat_p@entry=true) at xdisp.c:7428
#15 0x0044557f in move_it_in_display_line_to 
(it=it@entry=0x7ffd69b28c60, to_charpos=to_charpos@entry=105, 
to_x=to_x@entry=-1, op=op@entry=MOVE_TO_POS)
at xdisp.c:9012
#16 0x00446fd2 in move_it_to (it=it@entry=0x7ffd69b28c60, 
to_charpos=105, to_x=to_x@entry=-1, to_y=to_y@entry=-1, 
to_vpos=to_vpos@entry=-1, op=op@entry=8) at xdisp.c:9333
#17 0x004513d8 in resize_mini_window (w=w@entry=0x112cc30, 
exact_p=exact_p@entry=false) at xdisp.c:10989
#18 0x0045158e in display_echo_area_1 (a1=18009136, a2=)
at xdisp.c:10864
#19 0x00431e1d in with_echo_area_buffer (w=w@entry=0x112cc30, 
which=which@entry=0, fn=fn@entry=
0x451550 , a1=a1@entry=18009136, a2=a2@entry=0)
at xdisp.c:10642
#20 0x00455dae in display_echo_area (w=0x112cc30) at xdisp.c:10830
#21 0x00455dae in echo_area_display 
(update_frame_p=update_frame_p@entry=true) at xdisp.c:11331
---Type  to continue, or q  to quit---
#22 0x004560aa in message3_nolog (m=m@entry=65134084) at xdisp.c:10344
#23 0x004561fc in message3 (m=m@entry=65134084) at xdisp.c:10273
#24 0x0055ecdc in Fmessage (nargs=, args=) at editfns.c:3698
#25 0x005650a0 in eval_sub (form=) at eval.c:2137
#26 0x0056567d in Fprogn (body=31458307) at eval.c:426
#27 0x0056567d in funcall_lambda (fun=31458371, nargs=nargs@entry=1, 
arg_vector=arg_vector@entry=0x7ffd69b2a388) at eval.c:2914
#28 0x0056590b in Ffuncall (nargs=2, args=0x7ffd69b2a380)
at eval.c:2754
#29 0x005650a0 in eval_sub (form=) at eval.c:2137
#30 0x00565265 in Fprogn (body=21179555) at eval.c:426
#31 0x00565265 in Fif (args=) at eval.c:384
#32 0x00564ed4 in eval_sub (form=) at eval.c:2119
#33 0x00565265 in Fprogn (body=21179539) at eval.c:426
#34 0x00565265 in Fif (args=) at eval.c:384
#35 0x00564ed4 in eval_sub (form=) at eval.c:2119
#36 0x0056567d in Fprogn (body=21179491) at eval.c:426
#37 0x0056567d in funcall_lambda (fun=fun@entry=21179347, 
nargs=nargs@entry=2, arg_vector=arg_vector@entry=0x7ffd69b2a670) at eval.c:2914
#38 0x00564988 in apply_lambda (fun=21179347, args=, 
count=count@entry=47536) at eval.c:2794
#39 0x00564cea in eval_sub (form=) at eval.c:2241
---Type  to continue, or q  to quit---
#22 0x004560aa in message3_nolog (m=m@entry=65134084) at xdisp.c:10344
#23 0x004561fc in message3 (m=m@entry=65134084) at xdisp.c:10273
#24 0x0055ecdc in Fmessage (nargs=, args=) at editfn

[Desktop-packages] [Bug 1694566] [NEW] black screen white pointer

[themusicgod1]

Public bug reported:

gnome-screenshot by dash results in spinning cursor and then nothing

gnome-screenshot by commandline ...results in black screen with white
pointer and nothing else.  Have to alt-f1 to log into a new shell to
find & kill gnome-screenshot process which gets unity back.

once i kill the process further instances of gnome-screenshot work fine.

errors in the meanwhile: 
Error creating proxy: GDBus.Error:org.freedesktop.DBus.Error.LimitsExceeded: 
Failed to determine seats of user "1001": Too many open files 
(g-dbus-error-quark, 8)

desktop environment: unity 7.5.0+17.04.20170407.1-0ubuntu1
xorg : 1:7.7+16ubuntu3
ubuntu: 17.04 zesty
Linux eva1 4.10.0-21-generic #23-Ubuntu SMP Fri Apr 28 16:14:22 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux

   *-display
 description: VGA compatible controller
 product: Intel Corporation
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 04
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm vga_controller bus_master cap_list 
rom
 configuration: driver=i915 latency=0
 resources: irq:128 memory:de00-deff 
memory:c000-cfff ioport:f000(size=64) memory:c-d

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-screenshot 3.22.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Tue May 30 19:48:41 2017
InstallationDate: Installed on 2017-04-18 (42 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
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.
SourcePackage: gnome-screenshot
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug zesty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screenshot in Ubuntu.
https://bugs.launchpad.net/bugs/1694566

Title:
  black screen white pointer

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  gnome-screenshot by dash results in spinning cursor and then nothing

  gnome-screenshot by commandline ...results in black screen with white
  pointer and nothing else.  Have to alt-f1 to log into a new shell to
  find & kill gnome-screenshot process which gets unity back.

  once i kill the process further instances of gnome-screenshot work
  fine.

  errors in the meanwhile: 
  Error creating proxy: GDBus.Error:org.freedesktop.DBus.Error.LimitsExceeded: 
Failed to determine seats of user "1001": Too many open files 
(g-dbus-error-quark, 8)

  desktop environment: unity 7.5.0+17.04.20170407.1-0ubuntu1
  xorg : 1:7.7+16ubuntu3
  ubuntu: 17.04 zesty
  Linux eva1 4.10.0-21-generic #23-Ubuntu SMP Fri Apr 28 16:14:22 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

 *-display
   description: VGA compatible controller
   product: Intel Corporation
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 04
   width: 64 bits
   clock: 33MHz
   capabilities: pciexpress msi pm vga_controller bus_master 
cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:128 memory:de00-deff 
memory:c000-cfff ioport:f000(size=64) memory:c-d

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-screenshot 3.22.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue May 30 19:48:41 2017
  InstallationDate: Installed on 2017-04-18 (42 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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.
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1694566/+subsc

[Desktop-packages] [Bug 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg()

[themusicgod1]

( It's not marked on this ticket/updating the status on launchpad but
the freedesktop.org ticket merged a fix yesterday, those affected may
want to pull that fix )

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1539209

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
  source_set_volume_cb() from pa_source_process_msg()

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Appears randomly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:7.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   potato12883 F...m pulseaudio
   /dev/snd/controlC0:  potato12883 F pulseaudio
   /dev/snd/controlC1:  potato12883 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 28 22:16:03 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-17 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/libpulsecore-7.1.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113

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

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

[Desktop-packages] [Bug 1689381] [NEW] FTBFS cp: cannot stat 'doc/fontconfig-user.html'

[themusicgod1]

Public bug reported:

while attempting to build with debuild:

debuild -us -uc -b
...
Adding cdbs dependencies to debian/libfontconfig1-dbg.substvars
dh_installdirs -plibfontconfig1-dbg \

dh_installdocs -pfontconfig ./README ./NEWS ./AUTHORS
cp: cannot stat 'doc/fontconfig-user.html': No such file or directory
dh_installdocs: cp --reflink=auto -a doc/fontconfig-user.html 
debian/fontconfig/usr/share/doc/fontconfig returned exit code 1
/usr/share/cdbs/1/rules/debhelper.mk:235: recipe for target 
'binary-install/fontconfig' failed
make: *** [binary-install/fontconfig] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
debuild: fatal error at line 1116:
dpkg-buildpackage -rfakeroot -us -uc -b failed
z@aisha:~/fontconfig/fontconfig-2.11.94/debian$ 

ubuntu: 17.10 artful
libfontconfig1-dev:  2.11.94-0ubuntu2

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libfontconfig1-dev (not installed)
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Mon May  8 19:23:10 2017
InstallationDate: Installed on 2016-05-07 (366 days ago)
InstallationMedia:
 
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.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: fontconfig
UpgradeStatus: Upgraded to artful on 2017-05-08 (0 days ago)

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


** Tags: amd64 apport-bug artful

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1689381

Title:
  FTBFS cp: cannot stat 'doc/fontconfig-user.html'

Status in fontconfig package in Ubuntu:
  New

Bug description:
  while attempting to build with debuild:

  debuild -us -uc -b
  ...
  Adding cdbs dependencies to debian/libfontconfig1-dbg.substvars
  dh_installdirs -plibfontconfig1-dbg \

  dh_installdocs -pfontconfig ./README ./NEWS ./AUTHORS
  cp: cannot stat 'doc/fontconfig-user.html': No such file or directory
  dh_installdocs: cp --reflink=auto -a doc/fontconfig-user.html 
debian/fontconfig/usr/share/doc/fontconfig returned exit code 1
  /usr/share/cdbs/1/rules/debhelper.mk:235: recipe for target 
'binary-install/fontconfig' failed
  make: *** [binary-install/fontconfig] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
2
  debuild: fatal error at line 1116:
  dpkg-buildpackage -rfakeroot -us -uc -b failed
  z@aisha:~/fontconfig/fontconfig-2.11.94/debian$ 

  ubuntu: 17.10 artful
  libfontconfig1-dev:  2.11.94-0ubuntu2

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libfontconfig1-dev (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Mon May  8 19:23:10 2017
  InstallationDate: Installed on 2016-05-07 (366 days ago)
  InstallationMedia:
   
  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.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fontconfig
  UpgradeStatus: Upgraded to artful on 2017-05-08 (0 days ago)

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

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

[Desktop-packages] [Bug 1162475] Re: [hostnamed] Changing hostname doesn't update /etc/hosts

[themusicgod1]

** Tags added: zesty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1162475

Title:
  [hostnamed] Changing hostname doesn't update /etc/hosts

Status in gnome-control-center package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Triaged
Status in unity-control-center package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Debian:
  Fix Released

Bug description:
  GUI
  ---
  1a. Run sudo gnome-control-center, or...
  1b. Save the gnome-control-center.pkla from 
https://bazaar.launchpad.net/~ubuntu-desktop/gnome-control-center/ubuntu/revision/556
 to /var/lib/polkit-1/localauthority/10-vendor.d/ and then run 
gnome-control-center as an admin user

  2. Enter the Details panel
  3. The "Device name" (hostname) text field should be editable; change the 
text to something else.
  4. The hostname is updated instantly which can be verified by looking in 
/etc/hostname. However /etc/hosts/ is not updated.

  Command line
  
  hostnamectl set-hostname

  The hostnamed documentation at 
http://www.freedesktop.org/wiki/Software/systemd/hostnamed says
  "To properly handle name lookups with changing local hostnames without having 
to edit /etc/hosts for them we recommend using hostnamed in combination with 
nss-myhostname: http://0pointer.de/lennart/projects/nss-myhostname/ "

  Without /etc/hosts being handled correctly, the hostnamed integration
  is only half-working.


  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu18
  ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
  Uname: Linux 3.8.0-15-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Sun Mar 31 08:52:57 2013
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup26.0-0ubuntu1
   gnome-control-center-signon 0.1.5-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.03.26-0ubuntu1

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

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

[Desktop-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present

[themusicgod1]

So editing NetworkManager.conf didn't help.
I did some digging though and found that in /etc/dbus-1/system.d in element 
busconfig in org.freedesktop.thermald.conf:






this is owned by thermald

thermald: 1.5.4-4


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

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

Title:
  during recovery mode, enable network failed due to /etc/resolv.conf
  not being present

Status in network-manager package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  New

Bug description:
  Something went wrong that required me to boot to recovery mode via
  grub.  The important part here, is that while I got as far as the
  recovery screen asking to "Enable Networking" and other options fsck
  filesystems, drop to root shell, etc.

  and selected "Enable Networking":

  the result was:

  grep: /etc/resolv.conf: No such File or directory.

  Unknown group "power" in message bus configuration file.


  (Networking did not enable, leaving me stranded at root shell without
  network which would have made adding/removing packages to troubleshoot
  easier)

  Ubuntu: zesty 17.04
  Linux: Linux Hedy 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  network-manager: 1.4.4-1ubuntu3

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Apr 13 16:40:19 2017
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-09 (1009 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  IpRoute:
   default via 192.168.250.1 dev wlan1 proto static metric 600 
   10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 
   169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 
   192.168.250.0/24 dev wlan1 proto kernel scope link src 192.168.250.3 metric 
600
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   lxcbr0  bridgeconnected/org/freedesktop/NetworkManager/Devices/3  
lxcbr0  46595dd8-757b-4d93-ade3-c066f72d9e2e  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlan1   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
Brisbane House  2b25e748-f9c5-4c84-9fe6-0f64071fcf0b  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eth1ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  disabled

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

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

[Desktop-packages] [Bug 1647159] Re: Steam can't install/update itself or any games (zesty)

[themusicgod1]

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1650927 *

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

Title:
  Steam can't install/update itself or any games (zesty)

Status in network-manager package in Ubuntu:
  New

Bug description:
  Today I've noticed that Steam can't install/update anything. For instance, 
when running steam for the first time I'm getting:
  > Fatal Error: Steam needs to be online to update. Please confirm your 
network connection and try again.

  I've seen DNS-related updated recently, they might be a reason for
  this issue.

  I don't have any issues in browsers though.

  Workaround is to change `127.0.0.53` to `8.8.8.8` in
  `/etc/resolv.conf` manually.

  I'm connected to the Internet via router using Ethernet cable and I've
  manually specified DNS servers `8.8.8.8` and `8.8.4.4` in nm-applet's
  (I believe it is an applet) GUI.

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

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

[Desktop-packages] [Bug 1647159] Re: Steam can't install/update itself or any games (zesty)

[themusicgod1]

Is this #1650927 ? ie when this happens can you ping out to

whatver the IP address of your local gateway?
microsoft.com ?
8.8.8.8?

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

Title:
  Steam can't install/update itself or any games (zesty)

Status in network-manager package in Ubuntu:
  New

Bug description:
  Today I've noticed that Steam can't install/update anything. For instance, 
when running steam for the first time I'm getting:
  > Fatal Error: Steam needs to be online to update. Please confirm your 
network connection and try again.

  I've seen DNS-related updated recently, they might be a reason for
  this issue.

  I don't have any issues in browsers though.

  Workaround is to change `127.0.0.53` to `8.8.8.8` in
  `/etc/resolv.conf` manually.

  I'm connected to the Internet via router using Ethernet cable and I've
  manually specified DNS servers `8.8.8.8` and `8.8.4.4` in nm-applet's
  (I believe it is an applet) GUI.

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

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

[Desktop-packages] [Bug 1650927] Re: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc)

[themusicgod1]

can you ping things that are not domain names but are out on the public 
internet?
ie ping 8.8.8.8 ?

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

Title:
  accessing local ethernet is possible, accessing internet is not
  possible (Ubuntu MATE 17.04, ppc)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Access to local ethernet is possible (e.g. ping 192.168.2.2), access to 
internet is not possible:
  ping: ports.ubuntu.com: Name or service not known
  ping: www.google.com: Name or service not known

  It does not matter if my PowerBook G4 is connected via WLAN or
  ethernet, the effect is the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.2-2ubuntu4
  ProcVersionSignature: Ubuntu 4.9.0-11.12-powerpc-smp 4.9.0
  Uname: Linux 4.9.0-11-powerpc-smp ppc
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: powerpc
  CasperVersion: 1.379
  Date: Thu Nov  3 18:13:07 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.3.1 dev wlP1p17s0  proto static  metric 600 
   169.254.0.0/16 dev wlP1p17s0  scope link  metric 1000 
   192.168.3.0/24 dev wlP1p17s0  proto kernel  scope link  src 192.168.3.2  
metric 600
  LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha powerpc (20161218)
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   TERM=xterm
   PATH=(custom, no user)
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE STATE  
ACTIVE-PATH
   Carcosa 82f9a6ba-8a34-4aa8-8bba-6520f8b73c62  802-11-wireless  
1478196808  Thu 03 Nov 2016 06:13:28 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlP1p17s0  
activated  /org/freedesktop/NetworkManager/ActiveConnection/4 
   Wired connection 1  1a0d2e10-42f2-3154-b4f6-dfbec067bff3  802-3-ethernet   
1478196172  Thu 03 Nov 2016 06:02:52 PM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  no  -- -- 
--
  nmcli-dev:
   DEVICETYPE  STATEDBUS-PATH   
   CONNECTION  CON-UUID  CON-PATH   

   wlP1p17s0 wifi  connected
/org/freedesktop/NetworkManager/Devices/2  Carcosa 
82f9a6ba-8a34-4aa8-8bba-6520f8b73c62  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   enP2p36s15f0  ethernet  unavailable  
/org/freedesktop/NetworkManager/Devices/1  --  --   
 -- 
   loloopback  unmanaged
/org/freedesktop/NetworkManager/Devices/0  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present

[themusicgod1]

but did you boot into recovery mode in grub?  Might be a different bug
if not

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

Title:
  during recovery mode, enable network failed due to /etc/resolv.conf
  not being present

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Something went wrong that required me to boot to recovery mode via
  grub.  The important part here, is that while I got as far as the
  recovery screen asking to "Enable Networking" and other options fsck
  filesystems, drop to root shell, etc.

  and selected "Enable Networking":

  the result was:

  grep: /etc/resolv.conf: No such File or directory.

  Unknown group "power" in message bus configuration file.


  (Networking did not enable, leaving me stranded at root shell without
  network which would have made adding/removing packages to troubleshoot
  easier)

  Ubuntu: zesty 17.04
  Linux: Linux Hedy 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  network-manager: 1.4.4-1ubuntu3

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Apr 13 16:40:19 2017
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-09 (1009 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  IpRoute:
   default via 192.168.250.1 dev wlan1 proto static metric 600 
   10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 
   169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 
   192.168.250.0/24 dev wlan1 proto kernel scope link src 192.168.250.3 metric 
600
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   lxcbr0  bridgeconnected/org/freedesktop/NetworkManager/Devices/3  
lxcbr0  46595dd8-757b-4d93-ade3-c066f72d9e2e  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlan1   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
Brisbane House  2b25e748-f9c5-4c84-9fe6-0f64071fcf0b  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eth1ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  disabled

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

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

[Desktop-packages] [Bug 1682544] Re: xkill doesn't grab pointer gnome/weyland

[themusicgod1]

Still works fine in XFCE4

** Summary changed:

- xkill doesn't grab pointer
+ xkill doesn't grab pointer  gnome/weyland

** Summary changed:

- xkill doesn't grab pointer  gnome/weyland
+ xkill doesn't grab pointer in gnome/weyland

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to x11-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1682544

Title:
  xkill doesn't grab pointer in gnome/weyland

Status in x11-utils package in Ubuntu:
  New

Bug description:
  1. 
  > xkill 

  expected result:
  a) output: "Select the window whose client you wish to kill with button 1..."
  b) pointer turns to an X
  c) you can click on a window
  d) that window's process gets killed

  what actually happens
  a) output: "Select the window whose client you wish to kill with button 1..."
  b) The pointer goes invisible, until you move it, then it goes to the normal 
pointer.
  ...that's it.

  Ubuntu: 17.04 / zesty
  Desktop environment: Gnome/Weyland 
  x11-utils: 7.7+3

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: x11-utils 7.7+3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Thu Apr 13 13:40:03 2017
  DistUpgraded: 2017-04-13 12:41:16,896 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: zesty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0689]
 Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0689]
  InstallationDate: Installed on 2014-07-09 (1008 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  MachineType: Acer TravelMate P273-MG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=885e04f0-bd26-4885-aa1c-f134c674b8ff ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  SourcePackage: x11-utils
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  dmi.bios.date: 11/27/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BA70_HC
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.11:bd11/27/2013:svnAcer:pnTravelMateP273-MG:pvrV2.11:rvnAcer:rnBA70_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: TravelMate P273-MG
  dmi.product.version: V2.11
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Thu Apr 13 12:45:10 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x11-utils/+bug/1682544/+subscriptions

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

[Desktop-packages] [Bug 1682637] [NEW] during recovery mode, enable network failed due to /etc/resolv.conf not being present

[themusicgod1]

Public bug reported:

Something went wrong that required me to boot to recovery mode via grub.
The important part here, is that while I got as far as the recovery
screen asking to "Enable Networking" and other options fsck filesystems,
drop to root shell, etc.

and selected "Enable Networking":

the result was:

grep: /etc/resolv.conf: No such File or directory.

Unknown group "power" in message bus configuration file.


(Networking did not enable, leaving me stranded at root shell without
network which would have made adding/removing packages to troubleshoot
easier)

Ubuntu: zesty 17.04
Linux: Linux Hedy 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
network-manager: 1.4.4-1ubuntu3

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: network-manager 1.4.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Apr 13 16:40:19 2017
EcryptfsInUse: Yes
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2014-07-09 (1009 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708)
IpRoute:
 default via 192.168.250.1 dev wlan1 proto static metric 600 
 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 
 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 
 192.168.250.0/24 dev wlan1 proto kernel scope link src 192.168.250.3 metric 600
NetworkManager.conf:
 [main]
 plugins=ifupdown,keyfile
 
 [ifupdown]
 managed=false
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=false
SourcePackage: network-manager
UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 lxcbr0  bridgeconnected/org/freedesktop/NetworkManager/Devices/3  
lxcbr0  46595dd8-757b-4d93-ade3-c066f72d9e2e  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 wlan1   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
Brisbane House  2b25e748-f9c5-4c84-9fe6-0f64071fcf0b  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 eth1ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  --   
   ---- 

 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  --   
   ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN 
 running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  disabled

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


** Tags: amd64 apport-bug zesty

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

Title:
  during recovery mode, enable network failed due to /etc/resolv.conf
  not being present

Status in network-manager package in Ubuntu:
  New

Bug description:
  Something went wrong that required me to boot to recovery mode via
  grub.  The important part here, is that while I got as far as the
  recovery screen asking to "Enable Networking" and other options fsck
  filesystems, drop to root shell, etc.

  and selected "Enable Networking":

  the result was:

  grep: /etc/resolv.conf: No such File or directory.

  Unknown group "power" in message bus configuration file.


  (Networking did not enable, leaving me stranded at root shell without
  network which would have made adding/removing packages to troubleshoot
  easier)

  Ubuntu: zesty 17.04
  Linux: Linux Hedy 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  network-manager: 1.4.4-1ubuntu3

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Apr 13 16:40:19 2017
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-09 (1009 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  IpRoute:
   default via 192.168.250.1 dev wlan1 proto static metric 600 
   10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 
   169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 
   192.168.250.0/24 dev wlan1 proto kernel scope link src 192.168.250.3 metric 
6

[Desktop-packages] [Bug 1682544] [NEW] xkill doesn't grab pointer

[themusicgod1]

Public bug reported:

1. 
> xkill 

expected result:
a) output: "Select the window whose client you wish to kill with button 1..."
b) pointer turns to an X
c) you can click on a window
d) that window's process gets killed

what actually happens
a) output: "Select the window whose client you wish to kill with button 1..."
b) The pointer goes invisible, until you move it, then it goes to the normal 
pointer.
...that's it.

Ubuntu: 17.04 / zesty
Desktop environment: Gnome/Weyland 
x11-utils: 7.7+3

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: x11-utils 7.7+3
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Thu Apr 13 13:40:03 2017
DistUpgraded: 2017-04-13 12:41:16,896 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: zesty
DistroVariant: ubuntu
EcryptfsInUse: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0689]
   Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0689]
InstallationDate: Installed on 2014-07-09 (1008 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708)
MachineType: Acer TravelMate P273-MG
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=885e04f0-bd26-4885-aa1c-f134c674b8ff ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
SourcePackage: x11-utils
UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
dmi.bios.date: 11/27/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.11
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: BA70_HC
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.11:bd11/27/2013:svnAcer:pnTravelMateP273-MG:pvrV2.11:rvnAcer:rnBA70_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: TravelMate P273-MG
dmi.product.version: V2.11
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Thu Apr 13 12:45:10 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1
xserver.video_driver: modeset

** Affects: x11-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubuntu wayland-session zesty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to x11-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1682544

Title:
  xkill doesn't grab pointer

Status in x11-utils package in Ubuntu:
  New

Bug description:
  1. 
  > xkill 

  expected result:
  a) output: "Select the window whose client you wish to kill with button 1..."
  b) pointer turns to an X
  c) you can click on a window
  d) that window's process gets killed

  what actually happens
  a) output: "Select the window whose client you wish to kill with button 1..."
  b) The pointer goes invisible, until you move it, then it goes to the normal 
pointer.
  ...that's it.

  Ubuntu: 17.04 / zesty
  Desktop environment: Gnome/Weyland 
  x11-utils: 7.7+3

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: x11-utils 7.7+3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Thu Apr 13 13:40:03 2017
  DistUpgraded: 2017-04-13 12:41:16,896 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: zesty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Gr

[Desktop-packages] [Bug 508618] Re: Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp

[themusicgod1]

I don't remember and don't see anything in debian's bug tracking system.
That said... I can no longer crash emacs25 in zesty with the above sample code. 
 The code still doesn't work...but the bug in question here (crashing the 
entirety of emacs) no longer exists.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs23 in Ubuntu.
https://bugs.launchpad.net/bugs/508618

Title:
  Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp

Status in emacs23 package in Ubuntu:
  New
Status in emacs24 package in Ubuntu:
  New

Bug description:
  Binary package hint: emacs23

  Setting max-specpdl-size higher than 34295, and then running the following 
code results in a segfault of emacs.  I am 
  running a system of mostly 9.04 with some packages (such as this one) 
upgraded. I know it's kind of pushing emacs to the limit, but still;  this 
seems like an arbitrary limit on emacs' otherwise diety-like functionality.  
What should happen is emacs should continue to fail to execute with 
"file-truename: Variable binding depth exceeds max-specpdl-size"  as it does 
below 34295., or at the very least when setting max-specpdl-size higher than 
34295 it should warn you that you are making some kind of error if this is not 
acceptable.

  example code:

  (defun por (pcurrent pb numberleft)
 (if (= numberleft 0)
   pcurrent
   (por (- (+ pcurrent pb) (* pcurrent pb)) pb (- numberleft 1

  (por 0 0.01 1)

  (setq max-lisp-eval-depth 100)  ; this may be necessary, but doesn't 
appear to be the problem
  (setq max-specpdl-size 34295)  ; setting this lower results in 
predictable, expected behaviour - emacs refuses to run the result, citing 
max-specpdl-size not high enough.   Setting this higher (like...34296), results 
in a segfault of emacs

  emacs23:
Installé : 23.1+1-4ubuntu3
Candidat : 23.1+1-4ubuntu3
   Table de version :
   *** 23.1+1-4ubuntu3 0
  100 /var/lib/dpkg/status

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  Package: emacs23 23.1+1-4ubuntu3
  ProcEnviron:
   PATH=(custom, user)
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: emacs23
  Uname: Linux 2.6.28-16-generic x86_64
  UnreportableReason: Ceci n'est pas un authentique paquet Ubuntu

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

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