[Desktop-packages] [Bug 2085348] [NEW] package bubblewrap 0.9.0-1build1 failed to install/upgrade: subprocess dpkg-split returned error exit status 2

[Ted McIntosh]

Public bug reported:

just keeps freezing

ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: bubblewrap 0.9.0-1build1
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
AptOrdering:
 bubblewrap:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Oct 22 07:36:04 2024
DpkgTerminalLog:
 dpkg-split: error: error reading 
/var/cache/apt/archives/bubblewrap_0.9.0-1ubuntu0.1_amd64.deb: Input/output 
error
 dpkg: error processing archive 
/var/cache/apt/archives/bubblewrap_0.9.0-1ubuntu0.1_amd64.deb (--unpack):
  subprocess dpkg-split returned error exit status 2
ErrorMessage: subprocess dpkg-split returned error exit status 2
InstallationDate: Installed on 2024-09-04 (48 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 
3.12.3-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.22.6ubuntu6.1
 apt  2.7.14build2
SourcePackage: bubblewrap
Title: package bubblewrap 0.9.0-1build1 failed to install/upgrade: subprocess 
dpkg-split returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package noble

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

Title:
  package bubblewrap 0.9.0-1build1 failed to install/upgrade: subprocess
  dpkg-split returned error exit status 2

Status in bubblewrap package in Ubuntu:
  New

Bug description:
  just keeps freezing

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: bubblewrap 0.9.0-1build1
  ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
  Uname: Linux 6.8.0-45-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  AptOrdering:
   bubblewrap:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Oct 22 07:36:04 2024
  DpkgTerminalLog:
   dpkg-split: error: error reading 
/var/cache/apt/archives/bubblewrap_0.9.0-1ubuntu0.1_amd64.deb: Input/output 
error
   dpkg: error processing archive 
/var/cache/apt/archives/bubblewrap_0.9.0-1ubuntu0.1_amd64.deb (--unpack):
subprocess dpkg-split returned error exit status 2
  ErrorMessage: subprocess dpkg-split returned error exit status 2
  InstallationDate: Installed on 2024-09-04 (48 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 
3.12.3-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.22.6ubuntu6.1
   apt  2.7.14build2
  SourcePackage: bubblewrap
  Title: package bubblewrap 0.9.0-1build1 failed to install/upgrade: subprocess 
dpkg-split returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bubblewrap/+bug/2085348/+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 2084075] [NEW] XOrg crash in amdgpu after page fault

[Ted Cabeen]

Public bug reported:

XOrg is reliably crashing about every few hours when running graphics
off of the iGPU in my Ryzen 9 7950X on Oracular.  This crash is new to
Oracular, system was 100% stable on Noble.

Kernel:
Linux xxx 6.11.0-8-generic #8-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 16 13:41:20 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

xserver-xorg-video-amdgpu Version: 23.0.0-1build1

kernel log displays:
[Wed Oct  9 09:44:32 2024] amdgpu :17:00.0: amdgpu: [gfxhub] page fault 
(src_id:0 ring:24 vmid:4 pasid:32770)
[Wed Oct  9 09:44:32 2024] amdgpu :17:00.0: amdgpu:  in process Xorg pid 
539210 thread Xorg:cs0 pid 539211
[Wed Oct  9 09:44:32 2024] amdgpu :17:00.0: amdgpu:   in page starting at 
address 0x800123003000 from client 0x1b (UTCL2)
[Wed Oct  9 09:44:32 2024] amdgpu :17:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x00401031
[Wed Oct  9 09:44:32 2024] amdgpu :17:00.0: amdgpu:  Faulty UTCL2 
client ID: TCP (0x8)
[Wed Oct  9 09:44:32 2024] amdgpu :17:00.0: amdgpu:  MORE_FAULTS: 
0x1
[Wed Oct  9 09:44:32 2024] amdgpu :17:00.0: amdgpu:  WALKER_ERROR: 
0x0
[Wed Oct  9 09:44:32 2024] amdgpu :17:00.0: amdgpu:  
PERMISSION_FAULTS: 0x3
[Wed Oct  9 09:44:32 2024] amdgpu :17:00.0: amdgpu:  MAPPING_ERROR: 
0x0
[Wed Oct  9 09:44:32 2024] amdgpu :17:00.0: amdgpu:  RW: 0x0
[Wed Oct  9 09:44:32 2024] amdgpu :17:00.0: amdgpu: [gfxhub] page fault 
(src_id:0 ring:24 vmid:4 pasid:32770)
[Wed Oct  9 09:44:32 2024] amdgpu :17:00.0: amdgpu:  in process Xorg pid 
539210 thread Xorg:cs0 pid 539211
[Wed Oct  9 09:44:32 2024] amdgpu :17:00.0: amdgpu:   in page starting at 
address 0x80012300 from client 0x1b (UTCL2)
[Wed Oct  9 09:44:32 2024] amdgpu :17:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x
[Wed Oct  9 09:44:32 2024] amdgpu :17:00.0: amdgpu:  Faulty UTCL2 
client ID: CB/DB (0x0)
[Wed Oct  9 09:44:32 2024] amdgpu :17:00.0: amdgpu:  MORE_FAULTS: 
0x0
[Wed Oct  9 09:44:32 2024] amdgpu :17:00.0: amdgpu:  WALKER_ERROR: 
0x0
[Wed Oct  9 09:44:32 2024] amdgpu :17:00.0: amdgpu:  
PERMISSION_FAULTS: 0x0
[Wed Oct  9 09:44:32 2024] amdgpu :17:00.0: amdgpu:  MAPPING_ERROR: 
0x0
[Wed Oct  9 09:44:32 2024] amdgpu :17:00.0: amdgpu:  RW: 0x0

XOrg log:
[429834.278] (EE)
[429834.278] (EE) Backtrace:
[429834.278] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x14c) [0x6470bc83778c]
[429834.279] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) 
[0x759805045250]
[429834.279] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (pthread_kill+0x11c) 
[0x7598050a3f1c]
[429834.280] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x1e) 
[0x75980504519e]
[429834.280] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0xdf) 
[0x759805028902]
[429834.280] (EE) 5: /lib/x86_64-linux-gnu/libgallium-24.2.3-1ubuntu1.so 
(amdgpu_winsys_create+0x4840) [0x759802c31900]
[429834.280] (EE) 6: /lib/x86_64-linux-gnu/libgallium-24.2.3-1ubuntu1.so 
(amdgpu_winsys_create+0x7b6a) [0x759802c34c2a]
[429834.281] (EE) 7: /lib/x86_64-linux-gnu/libgallium-24.2.3-1ubuntu1.so 
(vdp_imp_device_create_x11+0x5ad71) [0x759802347c01]
[429834.281] (EE) 8: /lib/x86_64-linux-gnu/libgallium-24.2.3-1ubuntu1.so 
(vdp_imp_device_create_x11+0x7df1c) [0x75980236adac]
[429834.281] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 
(pthread_condattr_setpshared+0x68e) [0x7598050a1e2e]
[429834.281] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__clone+0x25c) 
[0x759805133a4c]
[429834.281] (EE)
[429834.281] (EE)
Fatal server error:
[429834.281] (EE) Caught signal 6 (Aborted). Server aborting
[429834.281] (EE)
[429834.281] (EE)
Please consult the The X.Org Foundation support
  at http://wiki.x.org
 for help.
[429834.281] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
[429834.281] (EE)
[429834.281] (II) AIGLX: Suspending AIGLX clients for VT switch
[429834.282] XXX fail to create fbo.
[429834.282] (EE)
[429834.282] (EE) Backtrace:
[429834.282] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x14c) [0x6470bc83778c]
[429834.282] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) 
[0x759805045250]
[429834.282] (EE) 2: /lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_composite_triangles+0x5fb0) [0x75980550ea40]
[429834.283] (EE) 3: /lib/x86_64-linux-gnu/libpixman-1.so.0 (pixman_fill+0x6a) 
[0x7598054afe8a]
[429834.283] (EE) 4: /usr/lib/xorg/Xorg (fbFill+0x425) [0x6470bc7fcd95]
[429834.283] (EE) 5: /usr/lib/xorg/Xorg (fbPolyFillRect+0x8d) [0x6470bc7fd3fd]
[429834.283] (EE) 6: /usr/lib/xorg/modules/libglamoregl.so 
(glamor_create_gc+0xeee9) [0x7597f9e78a19]
[429834.283] (EE) 7: /usr/lib/xorg/Xorg (DamageRegionAppend+0x1aa2) 
[0x6470bc79ddb2]
[429834.283] (EE) unw_get_proc_name failed: no unwind info found [-10]
[429834.283] (EE) 8: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) 
[0x75980499974c]
[429834.283] (EE) unw_get_proc_name failed: no unwind info found [-10]
[429834.28

[Desktop-packages] [Bug 2033590] Re: random crashes of gnome-characters

[Yensong Ted Li]

The "MEMORY-ERROR" message appears in ~/.xsession-errors rather than
syslog for me, but it's also the same random crashing of gnome-
characters that causes the application to suddenly exit; relevant lines
in ~/.xsession-errors:

Gjs-Message: 17:38:44.610: JS LOG: Characters Application started
Gjs-Message: 17:38:44.782: JS LOG: Characters Application activated
Gjs-Message: 17:38:54.534: JS LOG: Failed to search: search step already started
Gjs-Message: 17:38:55.994: JS LOG: Failed to search: search step already started
Gjs-Message: 17:38:57.856: JS LOG: Failed to search: search step already started
Gjs-Message: 17:38:58.958: JS LOG: Failed to search: search step already started

***MEMORY-ERROR***: org.gnome.Characters[4302]: GSlice: assertion
failed: sinfo->n_allocated > 0

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

Title:
  random crashes of gnome-characters

Status in gnome-characters package in Ubuntu:
  Confirmed

Bug description:
  Usually just a one-line record in syslog:

  Aug 30 19:10:45 COLOSSUS org.gnome.Characters[11012]: ***MEMORY-
  ERROR***: org.gnome.Characters[11012]: GSlice: assertion failed:
  sinfo->n_allocated > 0

  Aug 30 19:12:38 COLOSSUS org.gnome.Characters[11134]: ***MEMORY-
  ERROR***: org.gnome.Characters[11134]: GSlice: assertion failed:
  sinfo->n_allocated > 0

  Aug 30 19:17:29 COLOSSUS kernel: [ 2840.611031] pool-
  org.gnome.[11513]: segfault at 1c8 ip 7fd1854d1ae3 sp
  7fd1794ca9d8 error 6 in
  libglib-2.0.so.0.7200.4[7fd18547a000+8f000]

  Aug 30 22:44:26 COLOSSUS kernel: [15257.581416] gnome-
  character[18769]: segfault at 18 ip 7fb24db9eae3 sp
  7ffc99c29ca8 error 6 in
  libglib-2.0.so.0.7200.4[7fb24db47000+8f000]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-characters 41.0-4
  ProcVersionSignature: Ubuntu 5.15.0-82.91-generic 5.15.111
  Uname: Linux 5.15.0-82-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Wed Aug 30 22:52:57 2023
  InstallationDate: Installed on 2020-05-03 (1215 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gnome-characters
  UpgradeStatus: Upgraded to jammy on 2022-07-15 (412 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/2033590/+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 1997907] Re: [snap] Message 0 rejected by interface blink.mojom.WidgetHost

[Ted Saker]

Update: I was able to launch Chromium using a temporary profile.
Naturally it didn't save it. I uninstalled and reinstalled it. No
extensions. So far it's up and running.

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

Title:
  [snap] Message 0 rejected by interface blink.mojom.WidgetHost

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium shuts down and when restarted, says it didn't shut down
  properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 24 16:34:50 2022
  InstallationDate: Installed on 2022-03-19 (250 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Snap: chromium 107.0.5304.110 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+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 1997907] Re: [snap] Message 0 rejected by interface blink.mojom.WidgetHost

[Ted Saker]

Yes, wireless function is nominal.

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

Title:
  [snap] Message 0 rejected by interface blink.mojom.WidgetHost

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium shuts down and when restarted, says it didn't shut down
  properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 24 16:34:50 2022
  InstallationDate: Installed on 2022-03-19 (250 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Snap: chromium 107.0.5304.110 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+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 1997907] Re: [snap] Message 0 rejected by interface blink.mojom.WidgetHost

[Ted Saker]

Yes, wireless function is nominal.

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

Title:
  [snap] Message 0 rejected by interface blink.mojom.WidgetHost

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium shuts down and when restarted, says it didn't shut down
  properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 24 16:34:50 2022
  InstallationDate: Installed on 2022-03-19 (250 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Snap: chromium 107.0.5304.110 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+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 1997907] Re: [snap] trap invalid opcode

[Ted Saker]

** Attachment added: "journal.log"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+attachment/5641089/+files/journal.log

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

Title:
  [snap] trap invalid opcode

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium shuts down and when restarted, says it didn't shut down
  properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 24 16:34:50 2022
  InstallationDate: Installed on 2022-03-19 (250 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Snap: chromium 107.0.5304.110 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+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 1997907] Re: [snap] trap invalid opcode

[Ted Saker]

No idea. Starts to load then crashes.

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

Title:
  [snap] trap invalid opcode

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium shuts down and when restarted, says it didn't shut down
  properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 24 16:34:50 2022
  InstallationDate: Installed on 2022-03-19 (250 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Snap: chromium 107.0.5304.110 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+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 1997907] Re: [snap] trap invalid opcode

[Ted Saker]

Just ran the snap update to 109.0.5414.74 and now it crashes before it
fully loads.

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

Title:
  [snap] trap invalid opcode

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium shuts down and when restarted, says it didn't shut down
  properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 24 16:34:50 2022
  InstallationDate: Installed on 2022-03-19 (250 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Snap: chromium 107.0.5304.110 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+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 1997907] Re: [snap] trap invalid opcode

[Ted Saker]

Still doing the same thing.

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

Title:
  [snap] trap invalid opcode

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium shuts down and when restarted, says it didn't shut down
  properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 24 16:34:50 2022
  InstallationDate: Installed on 2022-03-19 (250 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Snap: chromium 107.0.5304.110 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+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 1997907] Re: [snap] trap invalid opcode

[Ted Saker]

Just upgraded kernel from 5.15.0-52 to 5.15.0-56 & monitoring.

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

Title:
  [snap] trap invalid opcode

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium shuts down and when restarted, says it didn't shut down
  properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 24 16:34:50 2022
  InstallationDate: Installed on 2022-03-19 (250 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Snap: chromium 107.0.5304.110 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+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 1997907] Re: [snap] trap invalid opcode

[Ted Saker]

Just updated to Version 108.0.5359.71 (Official Build) snap (64-bit),
still doing the same thing.

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

Title:
  [snap] trap invalid opcode

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium shuts down and when restarted, says it didn't shut down
  properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 24 16:34:50 2022
  InstallationDate: Installed on 2022-03-19 (250 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Snap: chromium 107.0.5304.110 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Re: [Desktop-packages] [Bug 1997907] Re: [Bug 1997596] Re: Chromium crashes without any apparent reason

[Ted Saker]

On Fri, Nov 25, 2022 at 4:35 PM Nathan Teodosio <1997...@bugs.launchpad.net>
wrote:

> Weird. That is a documented option in man journalctl.
>
> But anyway, -n1000 is just to show 1000 lines, the idea being we don't
> want to upload the whole journal, a thousand lines should suffice.
>
> You can do
>
>journalctl -r | head -n 1000 > /tmp/journal.log
>
> instead.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1997907
>
> Title:
>[Bug 1997596] Re: Chromium crashes without any apparent reason
>
> Status in chromium-browser package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Chromium shuts down and when restarted, says it didn't shut down
>   properly.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
>   Uname: Linux 5.15.0-53-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.25
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu Nov 24 16:34:50 2022
>   InstallationDate: Installed on 2022-03-19 (250 days ago)
>   InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
> (20210209.1)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   Snap: chromium 107.0.5304.110 (latest/stable)
>   SnapSource: ubuntu/+source/chromium-browser
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+subscriptions
>
>


** Attachment added: "journal.log"
   
https://bugs.launchpad.net/bugs/1997907/+attachment/5632856/+files/journal.log

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

Title:
   [Bug 1997596] Re: Chromium crashes without any apparent reason

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Chromium shuts down and when restarted, says it didn't shut down
  properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 24 16:34:50 2022
  InstallationDate: Installed on 2022-03-19 (250 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Snap: chromium 107.0.5304.110 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+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 1997907] Re: [Bug 1997596] Re: Chromium crashes without any apparent reason

[Ted Saker]

** Attachment added: "journal.log"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+attachment/5632855/+files/journal.log

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

Title:
   [Bug 1997596] Re: Chromium crashes without any apparent reason

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Chromium shuts down and when restarted, says it didn't shut down
  properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 24 16:34:50 2022
  InstallationDate: Installed on 2022-03-19 (250 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Snap: chromium 107.0.5304.110 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Re: [Desktop-packages] [Bug 1997907] Re: [Bug 1997596] Re: Chromium crashes without any apparent reason

[Ted Saker]

Tried running journalctl -rn1000 > /tmp/journal.log, Returned error
"journalctl: invalid option -- '1'"

On Fri, Nov 25, 2022 at 7:10 AM Nathan Teodosio <1997...@bugs.launchpad.net>
wrote:

> Sorry, Apport definitely did not report enough information for us. There
> are two independent things you can do. I recommend at least doing item
> 2, but doing both is better.
>
> 1. If you can, start chromium this way
>
>   snap run chromium --enable-logging=stderr --v=1 &> /tmp/chromium.log
>
> and attach /tmp/chromium.log to this bug report once you get a crash.
>
> 2. Once you get a crash, please run
>
>   journalctl -rn1000 > /tmp/journal.log
>
> and attach journal.log to this bug report.
>
> ** Changed in: chromium-browser (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1997907
>
> Title:
>[Bug 1997596] Re: Chromium crashes without any apparent reason
>
> Status in chromium-browser package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Chromium shuts down and when restarted, says it didn't shut down
>   properly.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
>   Uname: Linux 5.15.0-53-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.25
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu Nov 24 16:34:50 2022
>   InstallationDate: Installed on 2022-03-19 (250 days ago)
>   InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
> (20210209.1)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   Snap: chromium 107.0.5304.110 (latest/stable)
>   SnapSource: ubuntu/+source/chromium-browser
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+subscriptions
>
>

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

Title:
   [Bug 1997596] Re: Chromium crashes without any apparent reason

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Chromium shuts down and when restarted, says it didn't shut down
  properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 24 16:34:50 2022
  InstallationDate: Installed on 2022-03-19 (250 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Snap: chromium 107.0.5304.110 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+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 1997907] [NEW] [Bug 1997596] Re: Chromium crashes without any apparent reason

[Ted Saker]

Public bug reported:

Chromium shuts down and when restarted, says it didn't shut down
properly.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
Uname: Linux 5.15.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 24 16:34:50 2022
InstallationDate: Installed on 2022-03-19 (250 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Snap: chromium 107.0.5304.110 (latest/stable)
SnapSource: ubuntu/+source/chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)

** 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/1997907

Title:
   [Bug 1997596] Re: Chromium crashes without any apparent reason

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium shuts down and when restarted, says it didn't shut down
  properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 24 16:34:50 2022
  InstallationDate: Installed on 2022-03-19 (250 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Snap: chromium 107.0.5304.110 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+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 1997596] [NEW] Chromium crashes without any apparent reason

[Ted Saker]

Public bug reported:

Version 107.0.5304.110 (Official Build) snap (64-bit)
Ubuntu 20.04.5 LTS
+/- 6 tabs open at any given time. Browser shuts down randomly.

** Affects: chromium-browser (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/1997596

Title:
  Chromium crashes without any apparent reason

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Version 107.0.5304.110 (Official Build) snap (64-bit)
  Ubuntu 20.04.5 LTS
  +/- 6 tabs open at any given time. Browser shuts down randomly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997596/+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 1958267] Re: wpa can't connect to servers using TLS 1.1 or older

[Ted DeWitt]

#76 also works on my work's WPA2 Enterprise. PEAP Authentication, No CA
cert required; Auto PEAP; MSCHAPv2 inner authentication with user & pass
entered. 22.04 Jammy.

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

Title:
  wpa can't connect to servers using TLS 1.1 or older

Status in wpa package in Ubuntu:
  Fix Committed
Status in wpa source package in Jammy:
  Confirmed
Status in wpa package in Debian:
  New

Bug description:
  wpa built with in openssl3 fails to connect to TLS 1.1 or lower server

  those uses MD5-SHA1 as digest in its signature algorithm which no
  longer meets OpenSSL default level of security of 80 bits

  http://lists.infradead.org/pipermail/hostap/2022-May/040563.html

  Workaround are described in #22 and #36 by basically using 
  CipherString = DEFAULT@SECLEVEL=0

  which lowers the security level

  ---

  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1973564] Re: File dialog doesn't return current filter in Ubuntu 20.04

[Ted Gould]

I've installed the two packages and Inkscape behaves as expected. Played
around with some other apps and I haven't noticed any ill effects.

Thank you for everyone's help in getting this fixed!

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

Title:
  File dialog doesn't return current filter in Ubuntu 20.04

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Focal:
  Fix Committed
Status in xdg-desktop-portal-gtk source package in Focal:
  Fix Committed

Bug description:
  * Impact
  The file dialog implementation doesn't return the current filter. It is in 
the spec and it is fixed in newer versions of the portals. But the 1.6.0 
version doesn't return it.

  This is an issue for Inkscape which uses the filter to select which
  file format someone wishes to save as if they override the defaults.
  This works well on Ubuntu 22.04.

  * Test case

  $ snap install --candidate inkscape.

  In Inkscape if you just draw on the canvas and hit save a save dialog
  will appear. There is a selector at the bottom right that adjust which
  files you see, but also which format you want to save in. So if you
  make your file "test.pdf" and select "Portable Document Format
  (*.pdf)" in the selector you should get a PDF file. Before these
  patches you will get a file "test.pdf" which is actually an SVG file.
  After the patches you'll get a "test.pdf" that is actually a PDF.

  * Regression potential

  That's a change to the fileselector portal so check that opening and
  saving files in a few snaps and flatpaks still works as intended

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1973564/+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 1973564] Re: File dialog doesn't return current filter in Ubuntu 20.04

[Ted Gould]

The way that I'm testing this is with the candidate release for
Inkscape. Which is 1.2, you can grab as a snap with: snap install
--candidate inkscape.

In Inkscape if you just draw on the canvas and hit save a save dialog
will appear. There is a selector at the bottom right that adjust which
files you see, but also which format you want to save in. So if you make
your file "test.pdf" and select "Portable Document Format (*.pdf)" in
the selector you should get a PDF file. Before these patches you will
get a file "test.pdf" which is actually an SVG file. After the patches
you'll get a "test.pdf" that is actually a PDF.

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

Title:
  File dialog doesn't return current filter in Ubuntu 20.04

Status in xdg-desktop-portal package in Ubuntu:
  New
Status in xdg-desktop-portal-gtk package in Ubuntu:
  New
Status in xdg-desktop-portal source package in Focal:
  New
Status in xdg-desktop-portal-gtk source package in Focal:
  New

Bug description:
  The file dialog implementation doesn't return the current filter. It
  is in the spec and it is fixed in newer versions of the portals. But
  the 1.6.0 version doesn't return it.

  This is an issue for Inkscape which uses the filter to select which
  file format someone wishes to save as if they override the defaults.
  This works well on Ubuntu 22.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1973564/+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 1973564] Re: File dialog doesn't return current filter in Ubuntu 20.04

[Ted Gould]

Okay, so it turns out that the implementation wrapper also doesn't pass
the value.

** Also affects: xdg-desktop-portal (Ubuntu)
   Importance: Undecided
   Status: New

** Patch added: "xdg-desktop-portal-1.6.0-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1973564/+attachment/5590110/+files/xdg-desktop-portal-1.6.0-1ubuntu1.debdiff

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

Title:
  File dialog doesn't return current filter in Ubuntu 20.04

Status in xdg-desktop-portal package in Ubuntu:
  New
Status in xdg-desktop-portal-gtk package in Ubuntu:
  New
Status in xdg-desktop-portal source package in Focal:
  New
Status in xdg-desktop-portal-gtk source package in Focal:
  New

Bug description:
  The file dialog implementation doesn't return the current filter. It
  is in the spec and it is fixed in newer versions of the portals. But
  the 1.6.0 version doesn't return it.

  This is an issue for Inkscape which uses the filter to select which
  file format someone wishes to save as if they override the defaults.
  This works well on Ubuntu 22.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1973564/+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 1973564] Re: File dialog doesn't return current filter in Ubuntu 20.02

[Ted Gould]

Attaching a debdiff. For what ever reason this doesn't seem to fix
Inkscape. Though the D-Bus traffic is the same one 20.04 and 22.04 after
this change.

** Patch added: "xdg-desktop-portal-gtk-1.6.0-2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1973564/+attachment/5589943/+files/xdg-desktop-portal-gtk-1.6.0-2.debdiff

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

Title:
  File dialog doesn't return current filter in Ubuntu 20.02

Status in xdg-desktop-portal-gtk package in Ubuntu:
  New
Status in xdg-desktop-portal-gtk source package in Focal:
  New

Bug description:
  The file dialog implementation doesn't return the current filter. It
  is in the spec and it is fixed in newer versions of the portals. But
  the 1.6.0 version doesn't return it.

  This is an issue for Inkscape which uses the filter to select which
  file format someone wishes to save as if they override the defaults.
  This works well on Ubuntu 22.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1973564/+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 1973564] [NEW] File dialog doesn't return current filter in Ubuntu 20.02

[Ted Gould]

Public bug reported:

The file dialog implementation doesn't return the current filter. It is
in the spec and it is fixed in newer versions of the portals. But the
1.6.0 version doesn't return it.

This is an issue for Inkscape which uses the filter to select which file
format someone wishes to save as if they override the defaults. This
works well on Ubuntu 22.04.

** Affects: xdg-desktop-portal-gtk (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: xdg-desktop-portal-gtk (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Also affects: xdg-desktop-portal-gtk (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  File dialog doesn't return current filter in Ubuntu 20.02

Status in xdg-desktop-portal-gtk package in Ubuntu:
  New
Status in xdg-desktop-portal-gtk source package in Focal:
  New

Bug description:
  The file dialog implementation doesn't return the current filter. It
  is in the spec and it is fixed in newer versions of the portals. But
  the 1.6.0 version doesn't return it.

  This is an issue for Inkscape which uses the filter to select which
  file format someone wishes to save as if they override the defaults.
  This works well on Ubuntu 22.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1973564/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

[Ted DeWitt]

"Changed in wpa (Ubuntu):
status: Confirmed → Fix Released"

I am not sure how I did this, I am not an admin and was by complete
accident. I contacted Sebastien to correct this and bring it back to the
original status of "Confirmed". My apologies.

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Jammy:
  Confirmed
Status in wpa package in Debian:
  Fix Released

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

[Ted DeWitt]

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

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Jammy:
  Confirmed
Status in wpa package in Debian:
  Fix Released

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1908921] Re: No system tray detected by hp-systray

[Ted Cahall]

I am also affected.

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

Title:
  No system tray detected by hp-systray

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed

Bug description:
  I have hp-systray -x as one of the startup applications when I login.
  This app exits with the following error:

  HPLIP Status service
  No system tray detected on this system.
  Unable to start, exiting.

  Once logged in, if I start hp-systray -x from the terminal it works
  fine. This started happening after updating gnome-shell-extension-
  appindicator from version 33-1 to version 33.1-0ubuntu0.20.04.1.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 21 11:41:23 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-06-10 (1655 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1908921/+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 1917142] [NEW] Thunderbird Task "Show" filtering broken

[Ted Felix]

Public bug reported:

Thunderbird in Ubuntu 20.04 LTS was just upgraded to 78.7.1.
Unfortunately, that version has a bug which renders Tasks unusable for
those of us who depend on recurring tasks.  Completed tasks keep coming
back to life on restart of Thunderbird.  This results in incessant
reminders for tasks that were completed months and months ago.

The upstream bug report is here:

https://bugzilla.mozilla.org/show_bug.cgi?id=1686466

Bug 1686466: Task "Show" filtering broken in 78.6.1 - recurring tasks
are all being marked incomplete

Thunderbird version 78.8.0 has the fix.  Hopefully an upgrade to that
version can be expedited.

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

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

Title:
  Thunderbird Task "Show" filtering broken

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Thunderbird in Ubuntu 20.04 LTS was just upgraded to 78.7.1.
  Unfortunately, that version has a bug which renders Tasks unusable for
  those of us who depend on recurring tasks.  Completed tasks keep
  coming back to life on restart of Thunderbird.  This results in
  incessant reminders for tasks that were completed months and months
  ago.

  The upstream bug report is here:

  https://bugzilla.mozilla.org/show_bug.cgi?id=1686466

  Bug 1686466: Task "Show" filtering broken in 78.6.1 - recurring tasks
  are all being marked incomplete

  Thunderbird version 78.8.0 has the fix.  Hopefully an upgrade to that
  version can be expedited.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1917142/+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 1845801] Re: Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Ted Goddard]

Retested with Ubuntu 19.10 release. Auto login still causes login loop
on above system. Disabling auto login allows login to work as expected.

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

Title:
  Automatic login fails and then all subsequent logins fail. Killing
  gnome-session-binary fixes it, or just not using automatic login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  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.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+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 1845801] Re: Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Ted Goddard]

Confirmed: the user can successfully log in with auto login turned off.

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

Title:
  Automatic login fails and then all subsequent logins fail. Killing
  gnome-session-binary fixes it, or just not using automatic login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  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.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+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 1845801] Re: Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Ted Goddard]

I will test with auto login turned off. Is there a different video
driver setting that might be useful to test, like VGA only?

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

Title:
  Automatic login fails and then all subsequent logins fail. Killing
  gnome-session-binary fixes it, or just not using automatic login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  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.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+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 1848093] [NEW] Login loop with gdm3 and 19.10 beta

[Ted Goddard]

Public bug reported:

The user is unable to login from the login screen. The password is
accepted but the password prompt is displayed again.

Description:Ubuntu Eoan Ermine (development branch)
Release:19.10

gdm3:
  Installed: 3.34.1-1ubuntu1
  Candidate: 3.34.1-1ubuntu1
  Version table:
 *** 3.34.1-1ubuntu1 500
500 http://ca.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status


Note that the login screen appears even though I had specified auto login. 

Perhaps this one line is important:
Oct 14 14:41:24 carbon gdm3: GdmSession: Considering session (null) for 
username (null)

I am using an NVIDIA RTX 2080Ti with the bundled drivers.

When used via ssh, the following brings the system to a working desktop:

sudo service gdm restart

However, when this was used from a terminal from ctrl-alt-F3 the system
locked completely and was unresponsive over ssh.

/var/log/syslog is below:

Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: trying to get updated 
username
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: PAM conversation 
returning 0: Success
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: state AUTHENTICATED
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: trying to get updated 
username
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: username is 'ted'
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: old-username='ted' 
new-username='ted'
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: attempting to change 
state to AUTHORIZED
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: determining if 
authenticated user (password required:0) is authorized to session
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: state AUTHORIZED
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: attempting to change 
state to ACCREDITED
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: Set PAM environment 
variable: 'LOGNAME=ted'
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: Set PAM environment 
variable: 'USER=ted'
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: Set PAM environment 
variable: 'USERNAME=ted'
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: Set PAM environment 
variable: 'HOME=/home/ted'
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: Set PAM environment 
variable: 'PWD=/home/ted'
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: Set PAM environment 
variable: 'SHELL=/usr/bin/zsh'
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: Set PAM environment 
variable: 'PATH=/usr/local/bin:/usr/bin:/bin:/usr/games'
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: state ACCREDITED
Oct 14 14:41:24 carbon gdm-autologin]: GdmSessionWorker: pid 1802 
reauthenticated user 124 with service 'gdm-password'
Oct 14 14:41:24 carbon gdm-autologin]: GdmSession: Stopping all conversations
Oct 14 14:41:24 carbon gdm-autologin]: GdmSessionWorkerJob: Stopping job 
pid:3419
Oct 14 14:41:24 carbon gdm-autologin]: GdmCommon: sending signal 15 to process 
3419
Oct 14 14:41:24 carbon gdm-autologin]: GdmSessionWorkerJob: Waiting on process 
3419
Oct 14 14:41:24 carbon gdm-autologin]: GdmCommon: process (pid:3419) done 
(status:0)
Oct 14 14:41:24 carbon gdm-autologin]: GdmSessionWorkerJob: SessionWorkerJob 
died
Oct 14 14:41:24 carbon gdm-autologin]: GdmSessionWorker: client cancelled 
reauthentication request
Oct 14 14:41:24 carbon gdm-autologin]: GdmSession: Stopping all conversations
Oct 14 14:41:24 carbon gdm3: GdmSession: Emitting 'reauthenticated' signal 
Oct 14 14:41:24 carbon gdm3: GdmSession: type (null), program? no, seat seat0
Oct 14 14:41:24 carbon gdm3: GdmManager: Considering session 1 on seat seat0 
belonging to user ted
Oct 14 14:41:24 carbon gdm3: GdmManager: yes, found session 1
Oct 14 14:41:24 carbon gdm3: Unlocking session 1
Oct 14 14:41:24 carbon gdm3: GdmManager: trying to open new session
Oct 14 14:41:24 carbon gdm3: Finding a graphical session for user 124
Oct 14 14:41:24 carbon gdm3: Considering session 'c1'
Oct 14 14:41:24 carbon gdm3: GdmSession: Considering session (null) for 
username (null)
Oct 14 14:41:24 carbon gdm3: GdmDBusServer: new connection 0x5631e08edec0
Oct 14 14:41:24 carbon gdm3: GdmSession: Handling new connection from outside
Oct 14 14:41:24 carbon gdm3: GdmManager: client with pid 1802 connected
Oct 14 14:41:24 carbon gdm3: GdmDisplay: Got timed login details for display: 0
Oct 14 14:41:31 carbon xdg-desktop-por[1623]: Failed to get application states: 
GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: 
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not 
allowed
Oct 14 14:41:33 carbon gdm-autologin]: GdmSession: external connection closed
Oct 14 14:41:33 carbon gdm-autologin]: GdmSessionWorker: client disconnected 
from reauthentication serve

[Desktop-packages] [Bug 1824817] Re: CRTL+ALT+F7 bypasses the lock-screen with lightdm

[Ted]

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

** Summary changed:

- Security breach with CRTL+ALT+F7
+ CRTL+ALT+F7 bypasses the  lock-screen with lightdm

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

Title:
  CRTL+ALT+F7 bypasses the  lock-screen with lightdm

Status in lightdm package in Ubuntu:
  New

Bug description:
  This problem concerns every versions of Ubuntu 18 (Desktop or LTS) :

  When I lock my session with the padlock icon, I can open it with
  CRTL+ALT+F7 without password.

  This is the step to reproduce the problem:

  - Install Ubuntu 18 (Desktop or LTS) with the default option.
  The default windows manager is gnome

  - Install lightdm => the opening window logging will be replaced by
  the opening window logging of lightdm

  - Open a session

  - Lock the session with the padlock icon (in the right upper corner,
  click on the down arrow and click on the padlock icon)

  - The session seems lock because you can see the opening window
  logging wich asks you the password but press on CRTL+ALT+F7 and you
  can open the session without password.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: lightdm 1.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 15:26:04 2019
  InstallationDate: Installed on 2019-04-11 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1824817/+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 1740792] Re: Automatic login still requires user password after suspend/hibernate

[Ted Fry]

I've got this issue as well.  Automatic login, no requirement for a
password on the screen lock. When resuming from suspend, the password is
required.  The user account used for this is not an administrator user.
Fresh install, no changes.

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

Title:
  Automatic login still requires user password after suspend/hibernate

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

Bug description:
  Description:  Ubuntu 17.10
  Release:  17.10
  gnome-control-center 3.26.2

  When I set Ubuntu to automatically login a user the user still has to
  enter their password when resuming from a suspended session. The only
  option I can find to fix this is to disable the lock-screen
  completely, which I don't want to since I still want it to be an
  option to manually lock it. Setting Privacy > Screen Lock to off
  doesn't affect this behavior at all.

  The solution seems to be to use dconf-editor and change
  org.gnome.desktop.screensaver.ubuntu-lock-on-suspend to false. I got
  the solution after asking on askubuntu.com:
  https://askubuntu.com/questions/990056/turn-off-requesting-user-
  password-after-suspend-17-10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1740792/+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 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'

[Coomy Ted]

Partial from logfile. Dell 5378 13 i7 KabyLake fresh re-install of
Artful


Priority 3dbus:

Failed to construct signal

dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) 
none
(src/devices/nm-device.c:1452)): assertion '' failed

It's a shame that this bug has been around so long without fixes.

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

Title:
  wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The Wifi network can't connect after the wake up from suspend. Xubuntu
  15.04

  I'll post more useful details (journalctl log) as a comment to this
  bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dbus 1.8.12-1ubuntu5
  Uname: Linux 4.0.0-04rc5-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Apr  2 18:18:56 2015
  InstallationDate: Installed on 2015-03-27 (5 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+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 1728378] Re: NetworkManager: ((src/devices/nm-device.c:1452)): assertion '' failed

[Coomy Ted]

This bug affects my Dell 5378 13 i7 KabyLake. New re-install of Artful.

NetworkManager

(src/devices/nm-device.c:1452)): assertion '' failed

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

Title:
  NetworkManager: ((src/devices/nm-device.c:1452)): assertion
  '' failed

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This error shows up in boot logs:
  "NetworkManager: ((src/devices/nm-device.c:1452)): assertion '' 
failed".
  Ubuntu 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1728378/+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 1735363] Re: inkscape: Port to Python 3

[Ted Gould]

While I think it is fine for Inkscape to not be in main, there is a snap
for it, if there are those who want to still see it in main another
possible solution is to split out the Python extensions. They're
independent and could be a separate package with a recommends.

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

Title:
  inkscape: Port to Python 3

Status in Inkscape:
  New
Status in inkscape package in Ubuntu:
  New
Status in inkscape package in Debian:
  New

Bug description:
  inkscape: Use/Port of Python3 needed, or considering demotion.

  Currently seeded in usb (???), owned by desktop-packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1735363/+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 1700439] [NEW] package texlive-science-doc 2016.20170123-5 failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive-doc/latex/textgreek/README', which is also in

[Ted]

Public bug reported:

Error code (1) during installation.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: texlive-science-doc 2016.20170123-5
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
Date: Sun Jun 25 16:32:06 2017
DpkgTerminalLog:
 Preparing to unpack .../texlive-science-doc_2017.20170623-1_all.deb ...
 De-configuring texlive-latex-extra-doc (2016.20170123-5) ...
 Unpacking texlive-science-doc (2017.20170623-1) over (2016.20170123-5) ...
 dpkg: error processing archive 
/var/cache/apt/archives/texlive-science-doc_2017.20170623-1_all.deb (--unpack):
  trying to overwrite '/usr/share/doc/texlive-doc/latex/textgreek/README', 
which is also in package texlive-latex-extra-doc 2016.20170123-5
DuplicateSignature:
 package:texlive-science-doc:2016.20170123-5
 Unpacking texlive-science-doc (2017.20170623-1) over (2016.20170123-5) ...
 dpkg: error processing archive 
/var/cache/apt/archives/texlive-science-doc_2017.20170623-1_all.deb (--unpack):
  trying to overwrite '/usr/share/doc/texlive-doc/latex/textgreek/README', 
which is also in package texlive-latex-extra-doc 2016.20170123-5
ErrorMessage: trying to overwrite 
'/usr/share/doc/texlive-doc/latex/textgreek/README', which is also in package 
texlive-latex-extra-doc 2016.20170123-5
InstallationDate: Installed on 2016-08-06 (323 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.4.5
SourcePackage: texlive-extra
Title: package texlive-science-doc 2016.20170123-5 failed to install/upgrade: 
trying to overwrite '/usr/share/doc/texlive-doc/latex/textgreek/README', which 
is also in package texlive-latex-extra-doc 2016.20170123-5
UpgradeStatus: Upgraded to artful on 2017-05-20 (36 days ago)

** Affects: texlive-extra (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful need-duplicate-check package-conflict

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

Title:
  package texlive-science-doc 2016.20170123-5 failed to install/upgrade:
  trying to overwrite '/usr/share/doc/texlive-
  doc/latex/textgreek/README', which is also in package texlive-latex-
  extra-doc 2016.20170123-5

Status in texlive-extra package in Ubuntu:
  New

Bug description:
  Error code (1) during installation.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: texlive-science-doc 2016.20170123-5
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  Date: Sun Jun 25 16:32:06 2017
  DpkgTerminalLog:
   Preparing to unpack .../texlive-science-doc_2017.20170623-1_all.deb ...
   De-configuring texlive-latex-extra-doc (2016.20170123-5) ...
   Unpacking texlive-science-doc (2017.20170623-1) over (2016.20170123-5) ...
   dpkg: error processing archive 
/var/cache/apt/archives/texlive-science-doc_2017.20170623-1_all.deb (--unpack):
trying to overwrite '/usr/share/doc/texlive-doc/latex/textgreek/README', 
which is also in package texlive-latex-extra-doc 2016.20170123-5
  DuplicateSignature:
   package:texlive-science-doc:2016.20170123-5
   Unpacking texlive-science-doc (2017.20170623-1) over (2016.20170123-5) ...
   dpkg: error processing archive 
/var/cache/apt/archives/texlive-science-doc_2017.20170623-1_all.deb (--unpack):
trying to overwrite '/usr/share/doc/texlive-doc/latex/textgreek/README', 
which is also in package texlive-latex-extra-doc 2016.20170123-5
  ErrorMessage: trying to overwrite 
'/usr/share/doc/texlive-doc/latex/textgreek/README', which is also in package 
texlive-latex-extra-doc 2016.20170123-5
  InstallationDate: Installed on 2016-08-06 (323 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.4.5
  SourcePackage: texlive-extra
  Title: package texlive-science-doc 2016.20170123-5 failed to install/upgrade: 
trying to overwrite '/usr/share/doc/texlive-doc/latex/textgreek/README', which 
is also in package texlive-latex-extra-doc 2016.20170123-5
  UpgradeStatus: Upgraded to artful on 2017-05-20 (36 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1700439/+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 1612416] Re: Ugly shadow under Wayland

[ted]

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

Still exists in 17.04 running on GNOME

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

Title:
  Ugly shadow under Wayland

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  The window shadow looks good under X.Org Server, but under Wayland it
  is buggy and looks big and ugly and white.

  Other applications such as gnome-calculator, gedit, etc looks fine in
  Wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-terminal 3.20.2-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Thu Aug 11 22:33:36 2016
  InstallationDate: Installed on 2013-12-26 (958 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1612416/+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 1176127] Re: GLib Application Registers a DBus name under application confinement

[Ted Gould]

** Changed in: glib2.0 (Ubuntu)
 Assignee: Ted Gould (ted) => (unassigned)

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

Title:
  GLib Application Registers a DBus name under application confinement

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  Under application confinement applications won't be allowed to
  register names on DBus.  GApplication returns an error if it can't do
  that which makes programs unhappy.  Instead they should just believe
  they are the primary app instance if they're running under isolation.

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

[ted]

Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.3-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Wed Apr  5 22:40:25 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-06-20 (293 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: lightdm
Title: package lightdm 1.18.3-0ubuntu1.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

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

Status in lightdm package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Apr  5 22:40:25 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-06-20 (293 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: lightdm
  Title: package lightdm 1.18.3-0ubuntu1.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1681321/+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 1671731] Re: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU

[Ted Gould]

** No longer affects: ubuntu-app-launch (Ubuntu)

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

Title:
  [xmir] closing an app while a child window is opened leaves an Xmir
  process opened eating 100% CPU

Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Ubuntu 17.04 Unity 8
  [xmir] closing an app while a child window is opened leaves an Xmir process 
opened eating 100% CPU

  launch solitaire (just click on the sol icon from launcher, it will just run 
on Xmir)
  open the about window from the menu (Help \ About)
  now close the main window 

  now top in a terminal (see attached)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671731/+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 1672693] Re: GTK theme in apps appears different under Unity8 compared to Unity7

[Ted Gould]

** No longer affects: ubuntu-app-launch (Ubuntu)

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

Title:
  GTK theme in apps appears different under Unity8 compared to Unity7

Status in Canonical System Image:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.05 Unity8
  some submenus in GTK3 apps look like widgets (see attached screenshots)
  run whatever gtk3 apps native (without Xmir), sol or eog
  open the menu/submenus. the first time you open the menu everything is fine 
but the next times it shows this widget like submenus. just open and close 
submenus (hover the mouse over the main menu left right, right left)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672693/+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 1672950] Re: nautilus launched from Unity8 opens a 'Desktop' window

[Ted Gould]

** Changed in: ubuntu-app-launch (Ubuntu)
   Status: New => Invalid

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

Title:
  nautilus launched from Unity8 opens a 'Desktop' window

Status in Canonical System Image:
  New
Status in nautilus package in Ubuntu:
  New
Status in ubuntu-app-launch package in Ubuntu:
  Invalid

Bug description:
  nautilus launched from Unity8 opens a 'Desktop' window. It needs to be
  run with --no-desktop to avoid that.

  Although this issue is confused by two other bugs:
* Unity8 incorrectly chooses Xmir -> bug 1672931 ; and
* When using Xmir the desktop window is transparent -> bug 1672949

  These are three separate bugs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672950/+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 1668429] Re: X apps (LibreOffice, Thunderbird) fail to launch with failure to open display (no Xmir is running)

[Ted Gould]

** Branch linked: lp:~ted/ubuntu-app-launch/xmir-by-default

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

Title:
  X apps (LibreOffice, Thunderbird) fail to launch with failure to open
  display (no Xmir is running)

Status in Canonical System Image:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in libertine package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Feb 27 iso build of zesty, clean u8 exploration

  repro:
  1) open app drawer, find the thunderbird app
  2) click on icon to launch
  3) window closes immediately

  not a very useful journal log
  http://pastebin.ubuntu.com/24080860/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668429/+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 1639051] Re: gnome3 has black screen after upgrade: 304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2

[Ted]

Hi,

Have a similar issue here, I can no longer use my Blender, FreeCAD and OpenSCAD.
I do not get the black screen but Blender and FreeCAD crash and OpenSCAD will 
not display the model.  
Running Lubuntu 16.04 with the Nvidia Driver 304.132

Perhaps something about my configuration will be helpful with the
troubleshooting.

Have a second Lubuntu 16.04 computer that is not using the Nvidia Driver
and Blender runs fine on it.

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

Title:
  gnome3 has black screen after upgrade: 304.131-0ubuntu0.14.04.2,
  304.132-0ubuntu0.14.04.2

Status in gnome-shell:
  Expired
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed

Bug description:
  Gnome desktop session produces black screen. A Unity session works
  fine.

  reverting following packages fixes the problem:
  nvidia-current:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)
  nvidia-304:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)
  nvidia-libopencl1-304:amd64 (304.131-0ubuntu0.14.04.2, 
304.132-0ubuntu0.14.04.2)
  nvidia-opencl-icd-304:amd64 (304.131-0ubuntu0.14.04.2, 
304.132-0ubuntu0.14.04.2)
  libcuda1-304:amd64 (304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2)

  Hardware used:
  :~$ lspci
  00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RX790 Host 
Bridge
  00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RD790 PCI to 
PCI bridge (external gfx0 port A)
  00:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI 
bridge (PCI express gpp port E)
  00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI 
bridge (PCI express gpp port F)
  00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] (rev 40)
  00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller 
(rev 42)
  00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 IDE Controller (rev 40)
  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA) (rev 40)
  00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 
LPC host controller (rev 40)
  00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI 
Bridge (rev 40)
  00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
  00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 
PCI to PCI bridge (PCIE port 0)
  00:16.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:16.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
HyperTransport Configuration
  00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Address Map
  00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
DRAM Controller
  00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Miscellaneous Control
  00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Link Control
  01:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller 
(rev 03)
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
  03:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6315 Series Firewire 
Controller (rev 01)
  04:00.0 VGA compatible controller: NVIDIA Corporation GF106 [GeForce GTS 450] 
(rev a1)
  04:00.1 Audio device: NVIDIA Corporation GF106 High Definition Audio 
Controller (rev a1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1639051/+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 1576977] Re: Lots of GEGL-gegl-operation.c-WARNING on starting gimp

[Ted]

I've fully updated all my packages and I am still getting this bug when
running gimp from the command line. Has anyone found a fix to this or do
I need to revert to an older version of gimp for it to work again?

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

Title:
  Lots of GEGL-gegl-operation.c-WARNING on starting gimp

Status in gimp package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04
  gimp: 2.8.16-1ubuntu1

  rm ~/.gimp-2.8/
  LANG=en gimp

  
  (gimp:413): GLib-GObject-WARNING **: g_object_set_valist: object class 
'GeglConfig' has no property named 'cache-size'

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A3410 from "gimp:point-layer-mode" to "gimp
  :dissolve-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A39B0 from "gimp:point-layer-mode" to "gimp
  :behind-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A4090 from "gimp:point-layer-mode" to "gimp
  :multiply-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A43A0 from "gimp:point-layer-mode" to "gimp
  :screen-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A4790 from "gimp:point-layer-mode" to "gimp
  :overlay-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A4BC0 from "gimp:point-layer-mode" to "gimp
  :difference-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A5800 from "gimp:point-layer-mode" to "gimp
  :addition-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A5BC0 from "gimp:point-layer-mode" to "gimp
  :subtract-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A5F80 from "gimp:point-layer-mode" to "gimp
  :darken-only-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A63D0 from "gimp:point-layer-mode" to "gimp
  :lighten-only-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A68E0 from "gimp:point-layer-mode" to "gimp:hue-
  mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A6B40 from "gimp:point-layer-mode" to "gimp
  :saturation-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A6F70 from "gimp:point-layer-mode" to "gimp:color-
  mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A73E0 from "gimp:point-layer-mode" to "gimp:value-
  mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A7760 from "gimp:point-layer-mode" to "gimp
  :divide-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A7BE0 from "gimp:point-layer-mode" to "gimp:dodge-
  mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A7F50 from "gimp:point-layer-mode" to "gimp:burn-
  mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A83A0 from "gimp:point-layer-mode" to "gimp
  :hardlight-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A8740 from "gimp:point-layer-mode" to "gimp
  :softlight-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A8B40 from "gimp:point-layer-mode" to "gimp:grain-
  extract-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A90A0 from "gimp:point-layer-mode" to "gimp:grain-
  merge-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A93C0 from "gimp:point-layer-mode" to "gimp:color-
  erase-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A9730 from "gimp:point-layer-mode" to "gimp:erase-
  mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20AA080 from "gimp:point-layer-mode" to "gimp
  :replace-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20AA450 from "gimp:point-layer-mode" to "gimp:anti-
  erase-mode"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1576977/+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 1579837] Re: Issue after wizard with policykit

[Ted Gould]

Marking as low since we don't need the PK tools on the phone today,
backporting them to vivid is of low priority. We'll get them by default
when migrating to Xenial.

** Changed in: policykit-unity8 (Ubuntu)
   Importance: Undecided => Low

** Changed in: policykit-unity8 (Ubuntu)
   Status: In Progress => Triaged

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

Title:
  Issue after wizard with policykit

Status in Canonical System Image:
  In Progress
Status in accountsservice package in Ubuntu:
  Fix Released
Status in policykit-unity8 package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  1. Bootstrap flash a fresh image to a device
  2. Run through the wizard selecting pin for authentication
  3. Tap on the get started button
  4. Phone freezes for a while
  5. At some point it unfreezes and you see the dash
  6. Reboot and get password login instead of pin login

  EXPECTED:
  I expect no freeze (possibly due to apport) and pin dialogue on reboot

  ACTUAL:
  I get a long freeze and on reboot instead of getting the pin dialogue to 
unlock the phone I get the password dialogue and full osk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579837/+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 1579837] Re: Issue after wizard with policykit

[Ted Gould]

So I think what we're gonna do is use this bug for tracking the fixes
and landings for the touch images. This will be for OTA12, OTA11 will
not see the PK agent on it, we're just going to keep these bugs swept
under the rug like they were in OTA10.

At the root of it all the issue seems to be bug 1512002 where accounts
service was being too strict and we don't have a full session on the
phone. By applying the patch in that bug we remove the need for USS to
have a temporary PK agent and we remove the random prompts that are in
bug 1580086.

For this bug:

policykit-unity8 task: Fix the crash that was happening on timeout.
ubuntu-system-settings: Remove the PK agent code.
accountservice: Backport the bug 1512002 patch to vivid overlay

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

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

Title:
  Issue after wizard with policykit

Status in Canonical System Image:
  In Progress
Status in accountsservice package in Ubuntu:
  New
Status in policykit-unity8 package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  1. Bootstrap flash a fresh image to a device
  2. Run through the wizard selecting pin for authentication
  3. Tap on the get started button
  4. Phone freezes for a while
  5. At some point it unfreezes and you see the dash
  6. Reboot and get password login instead of pin login

  EXPECTED:
  I expect no freeze (possibly due to apport) and pin dialogue on reboot

  ACTUAL:
  I get a long freeze and on reboot instead of getting the pin dialogue to 
unlock the phone I get the password dialogue and full osk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579837/+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 1541787] Re: Printing from legacy apps on the pocket desktop

[Ted Gould]

I think that this probably belongs more with libertine as it tracks the
container's life. It'll probably also need to connect some sockets.

** Package changed: ubuntu-app-launch (Ubuntu) => libertine (Ubuntu)

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

Title:
  Printing from legacy apps on the pocket desktop

Status in avahi package in Ubuntu:
  New
Status in cups-filters package in Ubuntu:
  New
Status in libertine package in Ubuntu:
  New

Bug description:
  I have worked out a concept on how to introduce printing support to
  the phone (tablet, mobile devices) keeping the resource consumption
  low, starting the needed daemons on-demand.

  The daemons needed for printing are avahi-daemon, cups-browsed, and
  CUPS. avahi-daemon discovers printers on the network, cups-browsed
  creates local CUPS queues pointing to the remote printers and CUPS
  does the actual printing.

  CUPS is started socket-activated by Upstart and stops by itself when
  it gets idle. So CUPS for example starts when cups-browsed tries to
  create a print queue or an app sends a job to be printed. avahi-daemon
  and cups-browsed will be started by the print dialog of Ubuntu Touch,
  right before the dialog opens, making available printers on the
  network appear within seconds in the dialog. When the dialog closes,
  either because the user sent the print job or because he has
  cancelled, it kills avahi-daemon. cups-browsed and CUPS terminate
  automatically then as soon as the user's job is printed (plus a
  timeout).

  If you connect a monitor to the pone and so fire up the pocket desktop
  you are able to run legacy apps (apps designed for a conventional PC)
  which have print functionalities but their print dialogs do not start
  and kill daemons, they assume that all daemons and print queues are
  readily available. CUPS would be fired up automatically by any app's
  print functionality due to the socket activation, but then we would
  not have print queues on our phone as avahi-daemon and cups-browsed
  are not running.

  So what has to be made sure is that cups-browsed and avahi-daemon are
  running if at least one of

   - the native print dialog of Ubuntu Touch
   - any legacy app

  are running. So when one of these get started the two daemons need to
  get started and if all of these terminate avahi-daemon needs to get
  killed, so that the rest of the printing stack shuts down when all
  jobs get done.

  We assume that ubuntu-app-launch is the place where this should be
  done, please re-assign if this is not correct. I also add cups-filters
  (source of cups-browsed) and avahi-daemon tasks for the case that
  perhaps here something needs to get done, too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1541787/+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 1571154] Re: No wifi in 16.04 because of permission issue not having systemd-network permission

[Ted Hayes]

How did you achieve this?

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

Title:
  No wifi in 16.04 because of permission issue not having systemd-
  network permission

Status in network-manager package in Ubuntu:
  New

Bug description:
  After upgrading to 16.04, I had no access to wifi. It only worked as
  root. I fixed it by adding my user to the new "systemd-network" group.

  The existing users (or those in group netdev) should be automatically
  be added to "systemd-network" group during upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1571154/+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 303862] Re: Pidgin freezes when generating new OTR private key

[Ted]

** Changed in: pidgin-otr (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  Pidgin freezes when generating new OTR private key

Status in pidgin-otr:
  Invalid
Status in pidgin package in Ubuntu:
  Invalid
Status in pidgin-otr package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pidgin

  Package: pidgin-otr (Intrepid) 3.2.0-1
  Version of Ubuntu: Ubuntu 8.10 (Intrepid)
  Systems used: AMD XP 3200+, 1 GB DDR, 160 GB HDD running Ubuntu 8.10
   HP dv9500t laptop, 2.0 Ghz Core 2 Duo, 2 GB DDR, 160 
GB HDD running of Ubuntu 8.10 LiveCD

  When I enable the pidgin-otr plugin and attempt to generate a new
  private key, Pidgin pops up a dialog box telling me that a new private
  key is being generated. However, key generation never completes and
  eventually I receive a notification that Pidgin or "Generating Private
  Key" is not responding. I have attempted to generate keys for both a
  XMPP (GMail Account) and an AIM account with the same result, and have
  repeated the process on both systems multiple times.

  I have successfully generated keys using the same version of OTR on
  Windows XP SP3 on the HP dv9500t laptop.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  ExecutablePath: /usr/bin/pidgin
  Package: pidgin 1:2.5.2-0ubuntu1
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pidgin
  Uname: Linux 2.6.27-9-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/pidgin-otr/+bug/303862/+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 868904] Re: Redshift fails to start with session if no external location provider in available

[Ted]

@inoki -- can you attach the contents of /etc/geoclue/geoclue.conf??

I have also had this problem since upgrading, and I think it's related
to Geoclue's whitelisting. The redshift package should be editing
/etc/geoclue/geoclue.conf to add a stanza like these:

[redshift]
allowed=true
system=false
users=

[gtk-redshift]
allowed=true
system=false
users=


With this in /etc/geoclue/geoclue.conf, Redshift gets a location on startup and 
works correctly.

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

Title:
  Redshift fails to start with session if no external location provider
  in available

Status in Redshift:
  Confirmed
Status in Ubuntu GeoIP:
  Confirmed
Status in redshift package in Ubuntu:
  Fix Released
Status in ubuntu-geoip package in Ubuntu:
  Confirmed

Bug description:
  Since switching to oneiric redshift won't start.  It is listed as a
  startup application and these lines are present in .xsession-error
  from it:

  Unable to get location from provider.
  Started Geoclue provider `Geoclue Master'.
 Using provider `geoclue'.

  There is also no process in a ps listing.  If I start it from the
  command prompt then it starts just fine often with substantially
  similar messages.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: redshift 1.7-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu2
  Architecture: amd64
  Date: Wed Oct  5 22:39:15 2011
  SourcePackage: redshift
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Re: [Desktop-packages] [Bug 1472097] Re: Failed assertion in compCopyWindow

[Ted Gould]

On Mon, 2015-08-03 at 20:40 +, Christopher Townsend wrote:

> I guess it's easy enough to remove "-rootless" from the MP, but I
> wouldn't think Xmir should be crashing with that set either...


I think that, long term, we really want to be running -rootless in
general as well. So, I'd prefer to not drop if this is fixable.

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

Title:
  Failed assertion in compCopyWindow

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Ted has run into problems trying to integrate XMir with Unity8. When
  he starts an app, XMir aborts in compCopyWindow. (Log attached)

  This seems to be because compCopyWindow has been called before
  compConfigNotify (which in turn call compReallocPixmap, and set
  cw->oldx to valid values). This might be an initialisation order
  problem in XMir.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1472097/+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 1472097] Re: Failed assertion in compCopyWindow

[Ted Gould]

I think the big difference is connecting to Unity8 as the MIr server. So
I'm setting XMir as connecting to Unity8 and then the application
connecting to XMir. I think that Unity8 is doing "something" that the
demo server isn't doing. I'm not sure if that's an XMir issue or a
Unity8 one.

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

Title:
  Failed assertion in compCopyWindow

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Ted has run into problems trying to integrate XMir with Unity8. When
  he starts an app, XMir aborts in compCopyWindow. (Log attached)

  This seems to be because compCopyWindow has been called before
  compConfigNotify (which in turn call compReallocPixmap, and set
  cw->oldx to valid values). This might be an initialisation order
  problem in XMir.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1472097/+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 1424491] Re: apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5

[Ted Collins]

** Changed in: fglrx-installer (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5

Status in AMD fglrx video driver:
  Invalid
Status in fglrx-installer package in Ubuntu:
  In Progress
Status in fglrx-installer-updates package in Ubuntu:
  In Progress
Status in fglrx-installer source package in Precise:
  In Progress
Status in fglrx-installer-updates source package in Precise:
  In Progress
Status in fglrx-installer source package in Trusty:
  Fix Released
Status in fglrx-installer-updates source package in Trusty:
  Fix Committed

Bug description:
  
  SRU Request:

  [Impact]
  fglrx cannot be installed correctly together with the new lts stacks.

  [Test case]
  Installing the xserver from lts-utopic will prevent the current fglrx from 
being installed. The new fglrx will install correctly

  [Regression potential]
  Low. This fglrx release is already in use in 15.04 without any major issues.

  
  --

  Activity:  Install fglrx AMD driver on 12.04.5 and 14.02.2

  Expected behavior:  fglrx would intall

  Observed behavior:  fglrx is not installed as follows

  Attempt to install fglrx fails as follows:

  zack3@ZACK3:~$ sudo apt-get install fglrx-updates xvba-va-driver
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   fglrx-updates : Depends: xorg-video-abi-11 but it is not installable 
or
    xorg-video-abi-12 but it is not installable 
or
    xorg-video-abi-13 but it is not installable 
or
    xorg-video-abi-14 but it is not installable 
or
    xorg-video-abi-15
  E: Unable to correct problems, you have held broken packages.

  Attempt to insatll xorg-video-abi-15 yields:

  zack3@ZACK3:~$ sudo apt-get install xorg-video-abi-15
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Note, selecting 'xserver-xorg-core' instead of 'xorg-video-abi-15'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (>= 0.91.8) but it 
is not going to be installed
     Depends: libcogl15 (>= 1.15.8) but it is not going 
to be installed
   libcheese7 : Depends: libclutter-gst-2.0-0 (>= 0.10.0) but it is not 
going to be installed
    Depends: gstreamer1.0-clutter but it is not going to be 
installed
   libclutter-1.0-0 : Depends: libcogl-pango15 (>= 1.15.8) but it is 
not going to be installed
  Depends: libcogl15 (>= 1.15.8) but it is not 
going to be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be 
caused by held packages.

  Attempting to install xserver-xorg-core instead yields:

  zack3@ZACK3:~$ sudo apt-get install xserver-xorg-core
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (>= 0.91.8) but it 
is not going to be installed
     Depends: libcogl15 (>= 1.15.8) but it is not going 
to be installed
   libcheese7 : Depends: libclutter-gst-2.0-0 (>= 0.10.0) but it is not 
going to be installed
    Depends: gstreamer1.0-clutter but it is not going to be 
installed
   libclut

[Desktop-packages] [Bug 1263228] Re: icons in indicators are small (difficult to view on FullHD display and smaller than was on 12.04)

[Ted Gould]

Moving this over to an ido bug. The individual widgets live there, so
that's where it'll need to be fixed/tracked.

** No longer affects: indicator-application

** No longer affects: indicator-datetime

** No longer affects: indicator-keyboard

** No longer affects: indicator-messages

** No longer affects: indicator-session

** No longer affects: indicator-sound

** No longer affects: indicator-power

** No longer affects: libindicator

** No longer affects: gnome-panel (Ubuntu)

** Package changed: indicator-application (Ubuntu) => ido (Ubuntu)

** No longer affects: indicator-datetime (Ubuntu)

** No longer affects: indicator-keyboard (Ubuntu)

** No longer affects: indicator-messages (Ubuntu)

** No longer affects: indicator-session (Ubuntu)

** No longer affects: indicator-sound (Ubuntu)

** No longer affects: libindicator (Ubuntu)

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

Title:
  icons in indicators are small (difficult to view on FullHD display and
  smaller than was on 12.04)

Status in ido package in Ubuntu:
  Triaged
Status in indicator-power package in Ubuntu:
  Fix Released

Bug description:
  I have Ubuntu 14.04 with all updates installed.

  My screen resolution is 1920x1080 (FullHD) at 16.4 inches.
  Icons from the menu of newest indicator-keyboard and other gnome-panel icons 
are very small (difficult to read).

  Please adapt icon sizes to large screen resolutions.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-keyboard 0.0.0+14.04.20131125-0ubuntu1
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Dec 21 00:41:25 2013
  InstallationDate: Installed on 2013-10-20 (61 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  SourcePackage: indicator-keyboard
  UpgradeStatus: Upgraded to trusty on 2013-11-19 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1263228/+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 1425024] Re: indicator-sound-service can't get DBus in greeter session

[Ted Gould]

Reassigning to unity-greeter, I think it's pretty valid for indicator-
sound to crash if it can't get DBus…

** Summary changed:

- indicator-sound-service crashed with signal 5 in main()
+ indicator-sound-service can't get DBus in greeter session

** Package changed: indicator-sound (Ubuntu) => unity-greeter (Ubuntu)

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

Title:
  indicator-sound-service can't get DBus in greeter session

Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  Crashed in the greeter (lightdm).

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150219.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Tue Feb 24 21:50:39 2015
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  InstallationDate: Installed on 2015-01-31 (24 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_AU:en
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: indicator-sound
  StacktraceTop: main ()
  Title: indicator-sound-service crashed with signal 5 in main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1425024/+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 1401355] Re: package nvidia-opencl-icd-331-updates (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/i386-linux-gnu/libnvidia-opencl.so.331.113', which i

[Ted Shaw]

I have tried all the drivers that I can find and non of them seem to work.
Is there some comand in a terminal that I can use to fix this problem?
Thanks

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1401355

Title:
  package nvidia-opencl-icd-331-updates (not installed) failed to
  install/upgrade: trying to overwrite '/usr/lib/i386-linux-gnu
  /libnvidia-opencl.so.331.113', which is also in package nvidia-opencl-
  icd-331 331.113-0ubuntu0.0.4

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed

Bug description:
  There was an update of the driver this morning; since then I have been
  having difficulties with my CUDA code. I tried installing this
  alternative driver from the Additional Drivers manager, but the
  installation encountered this problem.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-opencl-icd-331-updates (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Thu Dec 11 11:31:01 2014
  DuplicateSignature: package:nvidia-opencl-icd-331-updates:(not 
installed):trying to overwrite 
'/usr/lib/i386-linux-gnu/libnvidia-opencl.so.331.113', which is also in package 
nvidia-opencl-icd-331 331.113-0ubuntu0.0.4
  ErrorMessage: trying to overwrite 
'/usr/lib/i386-linux-gnu/libnvidia-opencl.so.331.113', which is also in package 
nvidia-opencl-icd-331 331.113-0ubuntu0.0.4
  InstallationDate: Installed on 2014-08-04 (128 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: package nvidia-opencl-icd-331-updates (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/lib/i386-linux-gnu/libnvidia-opencl.so.331.113', which is also in package 
nvidia-opencl-icd-331 331.113-0ubuntu0.0.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1401355/+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 1412060] Re: Indicator sound fails to start with Asus Xonar

[Ted Gould]

It looks like pulseaudio is not running on your system.

** Package changed: indicator-sound (Ubuntu) => pulseaudio (Ubuntu)

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

Title:
  Indicator sound fails to start with Asus Xonar

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Replaced Audigy with Xonar.

  Clean installed to new drive and partition.

  sound indicator fails to start

  upstart --user --startup-event indicator-services-start

  tries to start indicator - space in indicators shows where it is,
  clicking and menu doesn't appear

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20141105-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jan 17 21:37:27 2015
  InstallationDate: Installed on 2015-01-09 (8 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150108)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1412060/+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 1405059] [NEW] nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build

[Ted Shaw]

Public bug reported:

Graphics driver problem

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-331 331.113-0ubuntu0.0.4
ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11
Uname: Linux 3.13.0-41-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
DKMSKernelVersion: 3.13.0-44-generic
Date: Sun Dec 21 21:24:48 2014
InstallationDate: Installed on 2014-10-20 (64 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageVersion: 331.113-0ubuntu0.0.4
SourcePackage: nvidia-graphics-drivers-331
Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-331 (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to
  build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  Graphics driver problem

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.113-0ubuntu0.0.4
  ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11
  Uname: Linux 3.13.0-41-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-44-generic
  Date: Sun Dec 21 21:24:48 2014
  InstallationDate: Installed on 2014-10-20 (64 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageVersion: 331.113-0ubuntu0.0.4
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1405059/+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 969359] Re: [keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking numlock)

[Ted Chen]

I am on 14.04 LTS and using Gnome. I encountered severe and frequent
high CPU consumption caused by gnome-settings-daemon process. I then
deleted /usr/lib/gnome-settings-daemon-3.0/keyboard.gnome-settings-
plugin. I also applied the num lock fix as explained in #107.

I noticed improved (less frequent) gnome-settings-daemon "hangs," but
still experienced them enough to be a big irritant.  I then started
performing traces. and noticed many failures in trying to open
/var/cache/fontconfig.  I then googled what could be causing that. I
then came across this page:
https://bugzilla.redhat.com/show_bug.cgi?id=612105

I then applied (as suggested on that page) restorecon -R
'/var/cache/fontconfig'

That seems to have done the trick. Everything is quiet now. I will post
again if I experience any further problems. Hope this helps someone
else!

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

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

Title:
  [keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking
  numlock)

Status in Gnome Settings Daemon:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Precise:
  Fix Released
Status in gnome-settings-daemon source package in Quantal:
  Fix Released
Status in gnome-settings-daemon package in Fedora:
  Unknown

Bug description:
  Impact:
  gnome-settings-daemon uses 100% cpu for ever in some cases

  Test Case:
  Seems to happen sometimes after docking or connecting with vnc, try to 
connect to the machine using a vnc client a few times and check there is no 
numlock cycle and cpu usage loop starting

  Regression potential:
  The numlock state could be wrongly set,restored on login in some cases

  -

  Original message:
  -

  I don't know how to reproduce this bug, but after varying amounts of
  normal usage of my laptop, I notice gnome-settings-daemon is consuming
  100% (approx) CPU.

  I am not sure how to restart gnome-settings-daemon, I tried opening a
  terminal and running gnome-settings-daemon again but this crashes my
  system - my external monitor switches off and my laptop locks up. I am
  able to reboot with SysRq+REISUB.

  Sorry I cannot provide more information - it happens twice now, maybe
  someone can tell me how to get more information for the next time this
  happens.

  $ lsb_release -rd
  Description:  Ubuntu precise (development branch)
  Release:  12.04

  $ apt-cache policy gnome-settings-daemon
  gnome-settings-daemon:
    Installed: 3.4.0-0ubuntu2
    Candidate: 3.4.0-0ubuntu2
    Version table:
   *** 3.4.0-0ubuntu2 0
  500 http://gb.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-settings-daemon 3.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  Date: Fri Mar 30 17:16:02 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/969359/+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 78435]

[Ted-f]

I haven't looked at any of this code in years, so I'm not a good person
to do this.

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

Title:
  temporary filenames should handle multiple extensions (.tar.gz)

Status in Mozilla Thunderbird Mail and News:
  Confirmed
Status in “thunderbird” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: mozilla-thunderbird

  When opening a file named foo.bar, the file is downloaded to /tmp. If
  the file is opened again in a short time, the file is again downloaded
  to /tmp but renamed foo-1.bar.

  If the file has a double extension (for example, opening a foo.tar.gz
  file with ark), the file is renamed as foo.tar-1.gz and thus ark is
  not able to open it properly. It should be foo-1.tar.gz instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/78435/+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 1111485] Re: dependency on glib >= 2.34.0 not reflected in configure.ac

[Ted Gould]

** Changed in: dbus-test-runner (Ubuntu)
   Status: New => In Progress

** Changed in: dbus-test-runner (Ubuntu)
 Assignee: (unassigned) => Ted Gould (ted)

** No longer affects: dbus-test-runner

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

Title:
  dependency on glib >= 2.34.0 not reflected in configure.ac

Status in “dbus-test-runner” package in Ubuntu:
  In Progress

Bug description:
  libdbustest uses g_clear_pointer(), which is only available since glib
  2.34. Please reflect this in the configure.ac and debian/control. A
  patch to do this is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-test-runner/+bug/485/+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 1101247] Re: autopkgtest of dbus-test-runner fails because g_type_init() deprecated and warning are treated as errors

[Ted Gould]

** Changed in: dbus-test-runner (Ubuntu)
   Status: New => Fix Released

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

Title:
  autopkgtest of dbus-test-runner fails because g_type_init() deprecated
  and warning are treated as errors

Status in “dbus-test-runner” package in Ubuntu:
  Fix Released

Bug description:
  dbus-test-runner autopkgtest [1] fails with:

  Making all in src
  make[3]: Entering directory 
`/tmp/tmp.j8ESTBPXxL/dsc0-build/dbus-test-runner-12.10.2daily13.01.10/src'
CC dbus_test_runner-dbus-test-runner.o
  dbus-test-runner.c: In function ‘main’:
  dbus-test-runner.c:184:2: error: ‘g_type_init’ is deprecated (declared at 
/usr/include/glib-2.0/gobject/gtype.h:669) [-Werror=deprecated-declarations]
  cc1: all warnings being treated as errors
  make[3]: *** [dbus_test_runner-dbus-test-runner.o] Error 1
  make[3]: Leaving directory 
`/tmp/tmp.j8ESTBPXxL/dsc0-build/dbus-test-runner-12.10.2daily13.01.10/src'
  make[2]: *** [all-recursive] Error 1
  make[2]: Leaving directory 
`/tmp/tmp.j8ESTBPXxL/dsc0-build/dbus-test-runner-12.10.2daily13.01.10'
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
`/tmp/tmp.j8ESTBPXxL/dsc0-build/dbus-test-runner-12.10.2daily13.01.10'
  dh_auto_build: make -j1 returned exit code 2
  make: *** [build] Error 2

  g_type_init() has been deprecated in glib 2.35.4

  [1] https://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/job
  /raring-adt-dbus-test-runner

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: dbus-test-runner (not installed)
  ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3
  Uname: Linux 3.8.0-0-generic x86_64
  ApportVersion: 2.8-0ubuntu2
  Architecture: amd64
  Date: Fri Jan 18 16:16:00 2013
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: dbus-test-runner
  UpgradeStatus: Upgraded to raring on 2012-01-31 (352 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-test-runner/+bug/1101247/+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 1315185] Re: pass in trusty, but fails ADT tests in utopic

[Ted Gould]

** No longer affects: dbus-test-runner

** Changed in: dbus-test-runner (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  pass in trusty, but fails ADT tests in utopic

Status in Déjà Dup Backup Tool:
  Fix Committed
Status in “dbus-test-runner” package in Ubuntu:
  Invalid
Status in “deja-dup” package in Ubuntu:
  Fix Released

Bug description:
  I've uploaded a no change rebuild of gvfs, yet it's currently blocked
  on deja-dup and dbus-test-runner ADT tests failing in utopic, yet they
  pass in trusty.

  This should be investigated and if something is wrong, appropriately
  fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1315185/+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 1214504] Re: unity-panel-service not running in non-upstart-sessions on Saucy (including guest session)

[Ted Gould]

** Changed in: unity
   Status: Triaged => Invalid

** Changed in: unity (Ubuntu)
   Status: Triaged => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1214504

Title:
  unity-panel-service not running in non-upstart-sessions on Saucy
  (including guest session)

Status in Light Display Manager:
  Fix Released
Status in Unity:
  Invalid
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  When changing to guest session on Saucy, you do not get the session gear 
indicator so to go back to a users session or logout or shutdown, all the 
indicators are missing in the top bar.
  See attached screenshot.
  The only way to get out of guest session once you are in, is CTRL+ALT+F1 and 
reboot on command line.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.7.9-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-3.6-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic x86_64
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Tue Aug 20 19:41:01 2013
  InstallationDate: Installed on 2013-03-28 (144 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130328)
  LightdmConfig:
   [SeatDefaults]
   user-session=ubuntu
   type=unity
   greeter-session=unity-greeter
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to saucy on 2013-05-19 (93 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1214504/+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 1157232] Re: ubuntu-geoip-provider crashed with SIGSEGV in _dbus_header_get_byte_order()

[Ted Gould]

** No longer affects: ubuntu-geoip

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

Title:
  ubuntu-geoip-provider crashed with SIGSEGV in
  _dbus_header_get_byte_order()

Status in “libproxy” package in Ubuntu:
  Confirmed
Status in “ubuntu-geoip” package in Ubuntu:
  Confirmed

Bug description:
  Bug came up when using the Dash's preview function. I richtclicked on
  an application and clicked away to close preview

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: geoclue-ubuntu-geoip 1.0.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-13.22-generic 3.8.3
  Uname: Linux 3.8.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Mar 19 16:00:04 2013
  ExecutablePath: /usr/lib/ubuntu-geoip/ubuntu-geoip-provider
  InstallationDate: Installed on 2013-03-18 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130227.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/ubuntu-geoip/ubuntu-geoip-provider
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f38b63207c3:movzbl (%rax),%eax
   PC (0x7f38b63207c3) ok
   source "(%rax)" (0x0106) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: ubuntu-geoip
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   dbus_message_get_reply_serial () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  Title: ubuntu-geoip-provider crashed with SIGSEGV in 
dbus_message_get_reply_serial()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/1157232/+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 1203344] Re: typo in com.ubuntu.geoip.gschema.xml.in file

[Ted Gould]

** Changed in: ubuntu-geoip
   Status: Fix Committed => Fix Released

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

Title:
  typo in com.ubuntu.geoip.gschema.xml.in file

Status in Ubuntu GeoIP Provider:
  Fix Released
Status in “ubuntu-geoip” package in Ubuntu:
  Fix Released
Status in “ubuntu-geoip” source package in Saucy:
  New

Bug description:
  In the file com.ubuntu.geoip.gschema.xml.in there is a missing
  apostrophe on line 6:

<_description>URL of a service that can be contacted and returns
  an XML file containing location information about the requestors IP
  address.

  should be:

<_description>URL of a service that can be contacted and returns
  an XML file containing location information about the requestor's IP
  address.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-geoip/+bug/1203344/+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 1185565] Re: Indicators should have Upstart jobs

[Ted Gould]

** No longer affects: indicator-application

** No longer affects: indicator-location

** No longer affects: indicator-sync

** No longer affects: libindicator

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1185565

Title:
  Indicators should have Upstart jobs

Status in The Date and Time Indicator:
  Fix Released
Status in Network Menu:
  Fix Released
Status in The Power Indicator:
  Fix Released
Status in The Session Menu:
  Fix Released
Status in Sound Menu:
  Fix Released
Status in Unity:
  Fix Released
Status in “indicator-application” package in Ubuntu:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Fix Released
Status in “indicator-location” package in Ubuntu:
  Fix Released
Status in “indicator-messages” package in Ubuntu:
  Fix Released
Status in “indicator-power” package in Ubuntu:
  Fix Released
Status in “indicator-session” package in Ubuntu:
  Fix Released
Status in “indicator-sound” package in Ubuntu:
  Fix Released
Status in “indicator-sync” package in Ubuntu:
  Fix Released
Status in “ubiquity” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity-greeter” package in Ubuntu:
  Fix Released

Bug description:
  Indicators should move over to using the upstart jobs to get better
  logging and management of their processes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1185565/+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 1296329] Re: dbus-test-runner pulls in a lot of questionable dependencies

[Ted Gould]

** Changed in: dbus-test-runner
   Status: New => Fix Released

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

Title:
  dbus-test-runner pulls in a lot of questionable dependencies

Status in The DBus Test Runner:
  Fix Released
Status in “dbus-test-runner” package in Ubuntu:
  Fix Released

Bug description:
  This may be intentional. If so, feel free to close this ticket.

  When installing dbus-test-runner on the phone, I notice it's pulling
  in a lot of questionable dependencies. libgphoto? libgl1-mesa-glx?
  gphoto? heimdal? THE ATHENA WIDGET SET?!? :)

  Does dbus-test-runner really use these (or have a runtime dependency
  on something that uses them?)

  $ sudo apt-get install dbus-test-runner
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following extra packages will be installed:
    desktop-file-utils gvfs gvfs-backends gvfs-common gvfs-daemons gvfs-libs 
libatasmart4 libcdio-cdda1 libcdio-paranoia1
    libcdio13 libfontenc1 libgd3 libgl1-mesa-glx libgphoto2-6 libgphoto2-port10 
libhdb9-heimdal libldb1 libmtp-common
    libmtp9 libntdb1 libparted0debian1 libpython2.7 libsmbclient libtalloc2 
libtevent0 libudisks2-0 libwbclient0 libxaw7
    libxcb-dri3-0 libxcb-glx0 libxcb-present0 libxft2 libxmu6 libxmuu1 libxpm4 
libxshmfence1 libxtst6 libxxf86dga1 parted
    psmisc python-talloc samba-libs udisks2 x11-utils
  Suggested packages:
    bustle gvfs-backends-goa obex-data-server samba-common libgd-tools gphoto2 
gtkam libparted0-dev libparted0-i18n
    parted-doc xfsprogs reiserfsprogs exfat-utils btrfs-tools mdadm 
cryptsetup-bin mesa-utils
  Recommended packages:
    gnome-keyring policykit-1-gnome libgphoto2-l10n libmtp-runtime dosfstools 
ntfs-3g gdisk
  The following NEW packages will be installed:
    dbus-test-runner desktop-file-utils gvfs gvfs-backends gvfs-common 
gvfs-daemons gvfs-libs libatasmart4 libcdio-cdda1
    libcdio-paranoia1 libcdio13 libfontenc1 libgd3 libgl1-mesa-glx libgphoto2-6 
libgphoto2-port10 libhdb9-heimdal libldb1
    libmtp-common libmtp9 libntdb1 libparted0debian1 libpython2.7 libsmbclient 
libtalloc2 libtevent0 libudisks2-0
    libwbclient0 libxaw7 libxcb-dri3-0 libxcb-glx0 libxcb-present0 libxft2 
libxmu6 libxmuu1 libxpm4 libxshmfence1
    libxtst6 libxxf86dga1 parted psmisc python-talloc samba-libs udisks2 
x11-utils
  0 upgraded, 45 newly installed, 0 to remove and 0 not upgraded.
  Need to get 7,610 kB of archives.
  After this operation, 28.7 MB of additional disk space will be used.
  Do you want to continue? [Y/n]

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus-test-runner/+bug/1296329/+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 1358340] Re: [Indicators] Complete greeter profiles

[Ted Gould]

** No longer affects: indicator-sound

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

Title:
  [Indicators] Complete greeter profiles

Status in The Date and Time Indicator:
  Invalid
Status in The Messaging Menu:
  Fix Released
Status in Transfer Indicator:
  Fix Released
Status in Ubuntu UX bugs:
  Fix Committed
Status in The Unity 8 shell:
  Fix Released
Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Invalid
Status in “indicator-messages” package in Ubuntu:
  Fix Released
Status in “indicator-sound” package in Ubuntu:
  Fix Released
Status in “indicator-transfer” package in Ubuntu:
  Fix Released
Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  A recent change in the interest of security removed access to the
  indicators when the phone is locked and the greeter is showing.

  This was an accentual change based on a misunderstanding

  There had been a plan to support media playback control via the sound
  indicator. Without this the user must unlock the phone in order to
  simply pause the music or change songs, etc.

  
  Desired resolution:

  - Revert the change that caused this issue

  - Add a switch to System Settings to enable security conscious user to
  switch off Launcher and Greeter access while the phone is locked.
  This setting should *always* be off by default.
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1358340/+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 1373404] Re: [notification] No warning of high volume level

[Ted Gould]

** No longer affects: indicator-sound

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

Title:
  [notification] No warning of high volume level

Status in Ubuntu UX bugs:
  Fix Committed
Status in “indicator-sound” package in Ubuntu:
  Fix Released
Status in “pulseaudio” package in Ubuntu:
  Invalid
Status in “ubuntu-system-settings” package in Ubuntu:
  In Progress
Status in “unity-notifications” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  In Progress
Status in “indicator-sound” package in Ubuntu RTM:
  Fix Released
Status in “unity-notifications” package in Ubuntu RTM:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  The EU has a legal requirement for personal music players to prevent hearing 
damage.
  http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490&rid=1
  

  Desired resolution:

  - For RTM the design spec'ed in the following section of the Sound
  wiki page should be implemented
  
https://wiki.ubuntu.com/Sound#Warnings_.28note:_This_section_should_be_implemented_for_RTM.29

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1373404/+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 957630] Re: Coverity PW.MISSING_DECL_SPECIFIERS - CID 10674

[Ted Gould]

** Changed in: sni-qt (Ubuntu)
   Importance: Undecided => Low

** Changed in: sni-qt (Ubuntu)
   Status: New => Confirmed

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

Title:
  Coverity PW.MISSING_DECL_SPECIFIERS - CID 10674

Status in Qt StatusNotifierItem plugin:
  Confirmed
Status in “sni-qt” package in Ubuntu:
  Confirmed

Bug description:
  This bug is exported from the Coverity Integration Manager on Canonical's 
servers. For information on how this is done please see this website: 
https://wiki.ubuntu.com/CanonicalProductStrategy/Coverity
  CID: 10674
  Checker: PW.MISSING_DECL_SPECIFIERS
  Category: No category available
  CWE definition: No definition available
  File: /usr/include/qt4/QtCore/qglobal.h
  Function: No function name available
  Code snippet:
  1178Utility macros and inline functions
  1179 */
  1180 
  1181 template 
  CID 10674 - PW.MISSING_DECL_SPECIFIERS
  this declaration has no storage class or type specifier
  During compilation of file 
'/tmp/buildd/sni-qt-0.2.5/obj-x86_64-linux-gnu/tests/auto/qrc_test.cxx'
  1182 Q_DECL_CONSTEXPR inline T qAbs(const T &t) { return t >= 0 ? t : -t; }
  1183 
  1184 Q_DECL_CONSTEXPR inline int qRound(qreal d)
  1185 { return d >= qreal(0.0) ? int(d + qreal(0.5)) : int(d - int(d-1) + 
qreal(0.5)) + int(d-1); }
  1186 
  1187 #if defined(QT_NO_FPU) || defined(QT_ARCH_ARM) || 
defined(QT_ARCH_WINDOWSCE) || defined(QT_ARCH_SYMBIAN)

To manage notifications about this bug go to:
https://bugs.launchpad.net/sni-qt/+bug/957630/+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 957631] Re: Coverity PW.MISSING_DECL_SPECIFIERS - CID 10673

[Ted Gould]

** Changed in: sni-qt (Ubuntu)
   Importance: Undecided => Low

** Changed in: sni-qt (Ubuntu)
   Status: New => Confirmed

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

Title:
  Coverity PW.MISSING_DECL_SPECIFIERS - CID 10673

Status in Qt StatusNotifierItem plugin:
  Confirmed
Status in “sni-qt” package in Ubuntu:
  Confirmed

Bug description:
  This bug is exported from the Coverity Integration Manager on Canonical's 
servers. For information on how this is done please see this website: 
https://wiki.ubuntu.com/CanonicalProductStrategy/Coverity
  CID: 10673
  Checker: PW.MISSING_DECL_SPECIFIERS
  Category: No category available
  CWE definition: No definition available
  File: /usr/include/qt4/QtCore/qglobal.h
  Function: No function name available
  Code snippet:
  2280 typedef void **Zero;
  2281 int i;
  2282 public:
  2283 typedef Enum enum_type;
  CID 10673 - PW.MISSING_DECL_SPECIFIERS
  this declaration has no storage class or type specifier
  During compilation of file 
'/tmp/buildd/sni-qt-0.2.5/obj-x86_64-linux-gnu/tests/auto/qrc_test.cxx'
  2284 Q_DECL_CONSTEXPR inline QFlags(const QFlags &f) : i(f.i) {}
  2285 Q_DECL_CONSTEXPR inline QFlags(Enum f) : i(f) {}
  2286 Q_DECL_CONSTEXPR inline QFlags(Zero = 0) : i(0) {}
  2287 inline QFlags(QFlag f) : i(f) {}
  2288 
  2289 inline QFlags &operator=(const QFlags &f) { i = f.i; return *this; }

To manage notifications about this bug go to:
https://bugs.launchpad.net/sni-qt/+bug/957631/+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 957627] Re: Coverity PW.MISSING_DECL_SPECIFIERS - CID 10675

[Ted Gould]

** Changed in: sni-qt (Ubuntu)
   Importance: Undecided => Low

** Changed in: sni-qt (Ubuntu)
   Status: New => Confirmed

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

Title:
  Coverity PW.MISSING_DECL_SPECIFIERS - CID 10675

Status in Qt StatusNotifierItem plugin:
  Confirmed
Status in “sni-qt” package in Ubuntu:
  Confirmed

Bug description:
  This bug is exported from the Coverity Integration Manager on Canonical's 
servers. For information on how this is done please see this website: 
https://wiki.ubuntu.com/CanonicalProductStrategy/Coverity
  CID: 10675
  Checker: PW.MISSING_DECL_SPECIFIERS
  Category: No category available
  CWE definition: No definition available
  File: /usr/include/qt4/QtCore/qglobal.h
  Function: No function name available
  Code snippet:
  1991 inline bool operator!=(QBool b1, bool b2) { return !b1 != !b2; }
  1992 inline bool operator!=(bool b1, QBool b2) { return !b1 != !b2; }
  1993 inline bool operator!=(QBool b1, QBool b2) { return !b1 != !b2; }
  1994 
  CID 10675 - PW.MISSING_DECL_SPECIFIERS
  this declaration has no storage class or type specifier
  During compilation of file 
'/tmp/buildd/sni-qt-0.2.5/obj-x86_64-linux-gnu/tests/auto/qrc_test.cxx'
  1995 Q_DECL_CONSTEXPR static inline bool qFuzzyCompare(double p1, double p2)
  1996 {
  1997 return (qAbs(p1 - p2) <= 0.0001 * qMin(qAbs(p1), qAbs(p2)));
  1998 }
  1999 
  2000 Q_DECL_CONSTEXPR static inline bool qFuzzyCompare(float p1, float p2)

To manage notifications about this bug go to:
https://bugs.launchpad.net/sni-qt/+bug/957627/+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 1209106] Re: system tray icon is next to launcher

[Ted Gould]

** Changed in: sni-qt (Ubuntu)
   Status: New => Confirmed

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

Title:
  system tray icon is next to launcher

Status in Qt:
  New
Status in Qt StatusNotifierItem plugin:
  Confirmed
Status in “sni-qt” package in Ubuntu:
  Confirmed

Bug description:
  The system tray icon is next to the launcher in the latest verion of
  Qt Creator.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qt/+bug/1209106/+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 1353858] Re: indicator problem

[Ted Gould]

** Changed in: sni-qt (Ubuntu)
   Importance: Undecided => High

** Changed in: sni-qt (Ubuntu)
   Status: New => Confirmed

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

Title:
  indicator problem

Status in Qt StatusNotifierItem plugin:
  Confirmed
Status in “sni-qt” package in Ubuntu:
  Confirmed

Bug description:
  I use qt4.8.4, and the development platform is ubuntukylin13.10.
  Sogou input method defines a menu on the indicator through QsystemTrayIcon. 
The signal:void QMenu::hovered(QAction*action) of the menu lost its efficacy in 
the unity desktop environment, but it’s effective in the cinnamon.The following 
two pictures are the same object, but there is no effect of hovered on the 
indicator

To manage notifications about this bug go to:
https://bugs.launchpad.net/sni-qt/+bug/1353858/+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 973480] Re: It's required to leak the default server

[Ted Gould]

** Changed in: libindicate (Ubuntu)
   Status: New => Triaged

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

Title:
  It's required to leak the default server

Status in Libindicate:
  Triaged
Status in “libindicate” package in Ubuntu:
  Triaged

Bug description:
  Because libindicate doesn't use GObject properties for
  IndicateIndicator::server there is a 'race condition' in
  indicate_indicator_new_with server. Calling it will cause a new
  indicator to be constructed on the default server, which unless the
  default server is already being used...will instantiate it and trigger
  an async request for the session bus.

  After g_object_new returns, the new server is set, the default server
  is unreffed, but the bus_get_cb is not cancelled.

  KABOOM

To manage notifications about this bug go to:
https://bugs.launchpad.net/libindicate/+bug/973480/+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 1358340] Re: [Indicators] Complete greeter profiles

[Ted Gould]

** Changed in: indicator-messages
   Status: In Progress => Fix Released

** Changed in: indicator-transfer
   Status: In Progress => Fix Released

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

Title:
  [Indicators] Complete greeter profiles

Status in The Date and Time Indicator:
  Invalid
Status in The Messaging Menu:
  Fix Released
Status in Sound Menu:
  In Progress
Status in Transfer Indicator:
  Fix Released
Status in Ubuntu UX bugs:
  Fix Committed
Status in The Unity 8 shell:
  Fix Released
Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Invalid
Status in “indicator-messages” package in Ubuntu:
  Fix Released
Status in “indicator-sound” package in Ubuntu:
  In Progress
Status in “indicator-transfer” package in Ubuntu:
  Fix Released
Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  A recent change in the interest of security removed access to the
  indicators when the phone is locked and the greeter is showing.

  This was an accentual change based on a misunderstanding

  There had been a plan to support media playback control via the sound
  indicator. Without this the user must unlock the phone in order to
  simply pause the music or change songs, etc.

  
  Desired resolution:

  - Revert the change that caused this issue

  - Add a switch to System Settings to enable security conscious user to
  switch off Launcher and Greeter access while the phone is locked.
  This setting should *always* be off by default.
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1358340/+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 1388892] [NEW] FTB dependent sources on Utopic/Vivid

[Ted Gould]

Public bug reported:

Projects using xorg-gtest become FTBFS. Attached a build log.

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

** Attachment added: "consoleText.txt"
   
https://bugs.launchpad.net/bugs/1388892/+attachment/4252109/+files/consoleText.txt

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

Title:
  FTB dependent sources on Utopic/Vivid

Status in “xorg-gtest” package in Ubuntu:
  New

Bug description:
  Projects using xorg-gtest become FTBFS. Attached a build log.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-gtest/+bug/1388892/+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 1382133] Re: Issue with servers with SSLv3 disabled due to Poodle

[Ted Guild]

It clearly addresses the issue, we can now connect to IMAP via TLS
protocols and SSLv3 disabled.

Thank you

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

Title:
  Issue with servers with SSLv3 disabled due to Poodle

Status in “evolution-data-server” package in Ubuntu:
  Fix Released
Status in “evolution-data-server” source package in Precise:
  Fix Committed
Status in “evolution-data-server” source package in Trusty:
  Fix Committed

Bug description:
  [ Description ]

  Cannot connect to servers with SSLv3 disabled, with a message "Cannot
  communicate securely with peer: no common encryption algorithm(s)."

  [ QA ]

  Try to connect to a server with SSLv3 disabled and see if you can
  retrieve mail (and that it errors before the update).

  [ Regression potential ]

  Might enable a different set of SSL/TLS versions, check with different
  servers.

  [ Original report ]

  Evolution developers asked me to relay that there is a fix to this
  issue available, please see

  https://mail.gnome.org/archives/evolution-
  list/2014-October/msg00113.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1382133/+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 1382133] [NEW] Issue with servers with SSLv3 disabled due to Poodle

[Ted Guild]

Public bug reported:

Evolution developers asked me to relay that there is a fix to this issue
available, please see

https://mail.gnome.org/archives/evolution-
list/2014-October/msg00113.html

** Affects: evolution-data-server (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Issue with servers with SSLv3 disabled due to Poodle

Status in “evolution-data-server” package in Ubuntu:
  New

Bug description:
  Evolution developers asked me to relay that there is a fix to this
  issue available, please see

  https://mail.gnome.org/archives/evolution-
  list/2014-October/msg00113.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1382133/+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 1373404] Re: No warning of high volume level

[Ted Gould]

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: Invalid => In Progress

** Changed in: ubuntu-system-settings (Ubuntu)
 Assignee: (unassigned) => Ted Gould (ted)

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

Title:
  No warning of high volume level

Status in Sound Menu:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “indicator-sound” package in Ubuntu:
  In Progress
Status in “pulseaudio” package in Ubuntu:
  Invalid
Status in “ubuntu-system-settings” package in Ubuntu:
  In Progress
Status in “unity-notifications” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  In Progress
Status in “indicator-sound” package in Ubuntu RTM:
  In Progress
Status in “unity-notifications” package in Ubuntu RTM:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  The EU has a legal requirement for personal music players to prevent hearing 
damage.
  http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490&rid=1
  

  Desired resolution:

  - For RTM the design spec'ed in the following section of the Sound
  wiki page should be implemented
  
https://wiki.ubuntu.com/Sound#Warnings_.28note:_This_section_should_be_implemented_for_RTM.29

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sound/+bug/1373404/+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 1373404] Re: No warning of high volume level

[Ted Gould]

** Changed in: indicator-sound (Ubuntu)
   Status: Triaged => In Progress

** Changed in: indicator-sound
   Status: Triaged => In Progress

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

Title:
  No warning of high volume level

Status in Sound Menu:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “indicator-sound” package in Ubuntu:
  In Progress
Status in “pulseaudio” package in Ubuntu:
  Invalid
Status in “ubuntu-system-settings” package in Ubuntu:
  Invalid
Status in “unity-notifications” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity-notifications” package in Ubuntu RTM:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  The EU has a legal requirement for personal music players to prevent hearing 
damage.
  http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490&rid=1
  

  Desired resolution:

  - For RTM the design spec'ed in the following section of the Sound
  wiki page should be implemented
  
https://wiki.ubuntu.com/Sound#Warnings_.28note:_This_section_should_be_implemented_for_RTM.29

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sound/+bug/1373404/+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 1373404] Re: No warning of high volume level

[Ted Gould]

** Changed in: indicator-sound (Ubuntu)
   Status: New => Triaged

** Changed in: indicator-sound
   Status: New => Triaged

** Changed in: indicator-sound
   Importance: Undecided => Critical

** Changed in: indicator-sound (Ubuntu)
   Importance: Undecided => Critical

** Changed in: indicator-sound (Ubuntu)
 Assignee: (unassigned) => Ted Gould (ted)

** Changed in: indicator-sound
 Assignee: (unassigned) => Ted Gould (ted)

** Changed in: pulseaudio (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  No warning of high volume level

Status in Sound Menu:
  Triaged
Status in Ubuntu UX bugs:
  Fix Committed
Status in “indicator-sound” package in Ubuntu:
  Triaged
Status in “pulseaudio” package in Ubuntu:
  Invalid
Status in “ubuntu-system-settings” package in Ubuntu:
  Triaged
Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  The EU has a legal requirement for personal music players to prevent hearing 
damage.
  http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490&rid=1
  

  Desired resolution:

  - For RTM the design spec'ed in the following section of the Sound
  wiki page should be implemented
  
https://wiki.ubuntu.com/Sound#Warnings_.28note:_This_section_should_be_implemented_for_RTM.29

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sound/+bug/1373404/+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 1358340] Re: [Indicators] Complete greeter profiles

[Ted Gould]

So we're basically looking at it as three levels:

1) Everything on lock screen. You like that, dont' care.
2) Reduced data, stuff is there, but it shouldn't be a really egregious leak or 
control things.
3) No Indicators

Basically the "MessagesWelcomeScreen" toggles between the first two.
Then the no indicators setting will turn on 3 or not. So for those who
are very worried about security they can turn off indicators entirely.
For those who'd like them to be a bit more restricted but still
available we can reduce the data set. And for those who live on a desert
island by themselves they have the full monty option as well.

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

Title:
  [Indicators] Complete greeter profiles

Status in The Date and Time Indicator:
  Invalid
Status in The Messaging Menu:
  In Progress
Status in Sound Menu:
  In Progress
Status in Transfer Indicator:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in The Unity 8 shell:
  Fix Released
Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Invalid
Status in “indicator-messages” package in Ubuntu:
  In Progress
Status in “indicator-sound” package in Ubuntu:
  In Progress
Status in “indicator-transfer” package in Ubuntu:
  In Progress
Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  A recent change in the interest of security removed access to the
  indicators when the phone is locked and the greeter is showing.

  This was an accentual change based on a misunderstanding

  There had been a plan to support media playback control via the sound
  indicator. Without this the user must unlock the phone in order to
  simply pause the music or change songs, etc.

  
  Desired resolution:

  - Revert the change that caused this issue

  - Add a switch to System Settings to enable security conscious user to
  switch off Launcher and Greeter access while the phone is locked.
  This setting should *always* be off by default.
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1358340/+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 1358340] Re: [Indicators] Complete greeter profiles

[Ted Gould]

Looked and there doesn't seem to be any actions for datetime.

** Changed in: indicator-sound
   Status: Confirmed => In Progress

** Changed in: indicator-datetime
   Status: Confirmed => Invalid

** Changed in: indicator-datetime (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: indicator-messages (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: indicator-sound (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: indicator-transfer
   Status: Confirmed => In Progress

** Changed in: indicator-transfer
 Assignee: (unassigned) => Ted Gould (ted)

** Changed in: indicator-transfer (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: indicator-transfer (Ubuntu)
     Assignee: (unassigned) => Ted Gould (ted)

** Branch linked: lp:~ted/indicator-transfer/fix-greeter-path

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

Title:
  [Indicators] Complete greeter profiles

Status in The Date and Time Indicator:
  Invalid
Status in The Messaging Menu:
  In Progress
Status in Sound Menu:
  In Progress
Status in Transfer Indicator:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in The Unity 8 shell:
  Fix Released
Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Invalid
Status in “indicator-messages” package in Ubuntu:
  In Progress
Status in “indicator-sound” package in Ubuntu:
  In Progress
Status in “indicator-transfer” package in Ubuntu:
  In Progress
Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  A recent change in the interest of security removed access to the
  indicators when the phone is locked and the greeter is showing.

  This was an accentual change based on a misunderstanding

  There had been a plan to support media playback control via the sound
  indicator. Without this the user must unlock the phone in order to
  simply pause the music or change songs, etc.

  
  Desired resolution:

  - Revert the change that caused this issue

  - Add a switch to System Settings to enable security conscious user to
  switch off Launcher and Greeter access while the phone is locked.
  This setting should *always* be off by default.
  <https://wiki.ubuntu.com/SecurityAndPrivacySettings#Locking>

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1358340/+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 1358340] Re: [Indicators] Complete greeter profiles

[Ted Gould]

Note: silo 13 is gathering all the pieces for this.

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

Title:
  [Indicators] Complete greeter profiles

Status in The Date and Time Indicator:
  Invalid
Status in The Messaging Menu:
  In Progress
Status in Sound Menu:
  In Progress
Status in Transfer Indicator:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in The Unity 8 shell:
  Fix Released
Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Invalid
Status in “indicator-messages” package in Ubuntu:
  In Progress
Status in “indicator-sound” package in Ubuntu:
  In Progress
Status in “indicator-transfer” package in Ubuntu:
  In Progress
Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  A recent change in the interest of security removed access to the
  indicators when the phone is locked and the greeter is showing.

  This was an accentual change based on a misunderstanding

  There had been a plan to support media playback control via the sound
  indicator. Without this the user must unlock the phone in order to
  simply pause the music or change songs, etc.

  
  Desired resolution:

  - Revert the change that caused this issue

  - Add a switch to System Settings to enable security conscious user to
  switch off Launcher and Greeter access while the phone is locked.
  This setting should *always* be off by default.
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1358340/+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 1358340] Re: [Indicators] Complete greeter profiles

[Ted Gould]

** Changed in: indicator-messages (Ubuntu)
 Assignee: (unassigned) => Ted Gould (ted)

** Changed in: indicator-messages (Ubuntu)
   Importance: Undecided => High

** Changed in: indicator-messages (Ubuntu)
   Status: New => Confirmed

** Changed in: indicator-sound (Ubuntu)
 Assignee: (unassigned) => Ted Gould (ted)

** Changed in: indicator-messages
   Status: Confirmed => In Progress

** Changed in: indicator-messages
 Assignee: (unassigned) => Ted Gould (ted)

** Changed in: indicator-sound
 Assignee: (unassigned) => Ted Gould (ted)

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

Title:
  [Indicators] Complete greeter profiles

Status in The Date and Time Indicator:
  Confirmed
Status in The Messaging Menu:
  In Progress
Status in Sound Menu:
  Confirmed
Status in Transfer Indicator:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in The Unity 8 shell:
  Fix Released
Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  New
Status in “indicator-messages” package in Ubuntu:
  Confirmed
Status in “indicator-sound” package in Ubuntu:
  Confirmed
Status in “indicator-transfer” package in Ubuntu:
  Confirmed
Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  A recent change in the interest of security removed access to the
  indicators when the phone is locked and the greeter is showing.

  This was an accentual change based on a misunderstanding

  There had been a plan to support media playback control via the sound
  indicator. Without this the user must unlock the phone in order to
  simply pause the music or change songs, etc.

  
  Desired resolution:

  - Revert the change that caused this issue

  - Add a switch to System Settings to enable security conscious user to
  switch off Launcher and Greeter access while the phone is locked.
  This setting should *always* be off by default.
  <https://wiki.ubuntu.com/SecurityAndPrivacySettings#Locking>

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1358340/+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 1358340] Re: [Indicators] Complete greeter profiles

[Ted Gould]

https://wiki.ubuntu.com/SecurityAndPrivacySettings#Phone

So I'm interpreting this as "Messages on Welcome Screen" is related to
the data being shown on the welcome screen. Where the messages and
notification settings is a Unity setting which just blocks the whole
panel.

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

Title:
  [Indicators] Complete greeter profiles

Status in The Date and Time Indicator:
  Confirmed
Status in The Messaging Menu:
  Confirmed
Status in Sound Menu:
  Confirmed
Status in Transfer Indicator:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in The Unity 8 shell:
  Fix Released
Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  New
Status in “indicator-messages” package in Ubuntu:
  New
Status in “indicator-sound” package in Ubuntu:
  Confirmed
Status in “indicator-transfer” package in Ubuntu:
  Confirmed
Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  A recent change in the interest of security removed access to the
  indicators when the phone is locked and the greeter is showing.

  This was an accentual change based on a misunderstanding

  There had been a plan to support media playback control via the sound
  indicator. Without this the user must unlock the phone in order to
  simply pause the music or change songs, etc.

  
  Desired resolution:

  - Revert the change that caused this issue

  - Add a switch to System Settings to enable security conscious user to
  switch off Launcher and Greeter access while the phone is locked.
  This setting should *always* be off by default.
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1358340/+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 1358340] Re: [Indicators] Complete greeter profiles

[Ted Gould]

** Tags removed: touch-2014-09-11
** Tags added: touch-2014-09-25

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

Title:
  [Indicators] Complete greeter profiles

Status in The Date and Time Indicator:
  Confirmed
Status in The Messaging Menu:
  Confirmed
Status in Sound Menu:
  Confirmed
Status in Transfer Indicator:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in The Unity 8 shell:
  Fix Released
Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  New
Status in “indicator-messages” package in Ubuntu:
  New
Status in “indicator-sound” package in Ubuntu:
  Confirmed
Status in “indicator-transfer” package in Ubuntu:
  Confirmed
Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  A recent change in the interest of security removed access to the
  indicators when the phone is locked and the greeter is showing.

  This was an accentual change based on a misunderstanding

  There had been a plan to support media playback control via the sound
  indicator. Without this the user must unlock the phone in order to
  simply pause the music or change songs, etc.

  
  Desired resolution:

  - Revert the change that caused this issue

  - Add a switch to System Settings to enable security conscious user to
  switch off Launcher and Greeter access while the phone is locked.
  This setting should *always* be off by default.
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1358340/+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 1366879] [NEW] external monitor flicker in radeon driver on RV710/M92 [Mobility Radeon HD 4530/4570/545v]

[Ted]

Public bug reported:

When using Compiz/Unity at my external monitor's full resolution
(1920x1080), my external display displays horizontal distortion.
Sometimes the vertical alignment will also waver.

This doesn't appear using metacity, so it's not a hardware issue. This
also doesn't appear using the next highest resolution (1680x1050).

I'm using the radeon open-source driver.

lspci -k:

02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV710/M92 [Mobility Radeon HD 4530/4570/545v]
Subsystem: CLEVO/KAPOK Computer Device 0770
Kernel driver in use: radeon

tedks@anglachel:~$ apt-cache policy xserver-xorg-video-ati
xserver-xorg-video-ati:
  Installed: 1:7.3.0-1ubuntu3.1
  Candidate: 1:7.3.0-1ubuntu3.1
  Version table:
 *** 1:7.3.0-1ubuntu3.1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:7.3.0-1ubuntu3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Sep  8 12:31:09 2014
DistUpgraded: 2014-06-09 15:06:48,193 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.3.10, 3.13.0-32-generic, x86_64: installed
 virtualbox, 4.3.10, 3.13.0-33-generic, x86_64: installed
 virtualbox, 4.3.10, 3.13.0-34-generic, x86_64: installed
 virtualbox, 4.3.10, 3.13.0-35-generic, x86_64: installed
 virtualbox, 4.3.10, 3.13.0-36-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 
4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer Device [1558:0770]
InstallationDate: Installed on 2012-04-18 (873 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120327.1)
MachineType: CLEVO W76x/M77xCUH
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-36-generic 
root=/dev/mapper/hostname-root ro quiet splash nomdmonddf nomdmonisw 
vt.handoff=7
SourcePackage: xserver-xorg-video-ati
UpgradeStatus: Upgraded to trusty on 2014-06-09 (90 days ago)
dmi.bios.date: 09/21/2010
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: CALPELLACRB.86C..X.00
dmi.board.asset.tag: Tag 12345
dmi.board.name: W76x/M77xCUH
dmi.board.vendor: CLEVO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: CLEVO
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrCALPELLACRB.86C..X.00:bd09/21/2010:svnCLEVO:pnW76x/M77xCUH:pvrNotApplicable:rvnCLEVO:rnW76x/M77xCUH:rvrNotApplicable:cvnCLEVO:ct9:cvrN/A:
dmi.product.name: W76x/M77xCUH
dmi.product.version: Not Applicable
dmi.sys.vendor: CLEVO
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2

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


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

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

Title:
  external monitor flicker in radeon driver on RV710/M92 [Mobility
  Radeon HD 4530/4570/545v]

Status in “xserver-xorg-video-ati” package in Ubuntu:
  New

Bug description:
  When using Compiz/Unity at my external monitor's full resolution
  (1920x1080), my external display displays horizontal distortion.
  Sometimes the vertical alignment will also waver.

  This doesn't appear using metacity, so it's not a hardware issue. This
  also doesn't appear using the next highest resolution (1680x1050).

  I'm using the radeon open-source driver.

  lspci -k:

[Desktop-packages] [Bug 1335093] Re: chromium-browser closes/crashes on "Save image as..."

[Ted]

Dupe of #1333477 and #1310163.

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

Title:
  chromium-browser closes/crashes on "Save image as..."

Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  Chromium closes/crashes when you right-click on a http:// image served
  on a https:// page and choose "Save image as..."

  $ chromium-browser 
  [18405:18436:0627/135735:FATAL:url_request.cc(707)] Trying to send secure 
referrer for insecure load
  Aborted

  $ uname -a
  Linux RedFenix 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  Distributor ID:   LinuxMint
  Description:  Linux Mint 17 Qiana
  Release:  17
  Codename: qiana

  $ dpkg -s chromium-browser
  Package: chromium-browser
  Status: install ok installed
  Priority: optional
  Section: web
  Installed-Size: 153832
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Version: 34.0.1847.116-0ubuntu2
  Replaces: chromium-browser-inspector
  Provides: chromium-browser-inspector, www-browser
  Depends: gconf-service, libasound2 (>= 1.0.16), libatk1.0-0 (>= 1.12.4), 
libc6 (>= 2.15), libcairo2 (>= 1.6.0), libcap2 (>= 2.10), libcomerr2 (>= 1.01), 
libcups2 (>= 1.4.0), libdbus-1-3 (>= 1.2.14), libexpat1 (>= 2.0.1), 
libfontconfig1 (>= 2.9.0), libfreetype6 (>= 2.3.9), libgcc1 (>= 1:4.1.1), 
libgconf-2-4 (>= 2.31.1), libgcrypt11 (>= 1.5.1), libgdk-pixbuf2.0-0 (>= 
2.22.0), libglib2.0-0 (>= 2.37.3), libgnome-keyring0 (>= 3.2.2-2~), libgnutls26 
(>= 2.12.17-0), libgssapi-krb5-2 (>= 1.6.dfsg.2), libgtk2.0-0 (>= 2.24.0), 
libk5crypto3 (>= 1.6.dfsg.2), libkrb5-3 (>= 1.6.dfsg.2), libnspr4 (>= 2:4.9-2~) 
| libnspr4-0d (>= 1.8.0.10), libnss3 (>= 2:3.14.3), libpango-1.0-0 (>= 1.22.0), 
libpangocairo-1.0-0 (>= 1.14.0), libpangoft2-1.0-0 (>= 1.14.0), libstdc++6 (>= 
4.6), libudev1 (>= 183), libx11-6 (>= 2:1.2.99.901), libxcomposite1 (>= 
1:0.3-1), libxcursor1 (>> 1.1.2), libxdamage1 (>= 1:1.1), libxext6, libxfixes3 
(>= 1:5.0), libxi6 (>= 2:1.2.99.4), libxrandr2 (>= 2:1.2.99.2), libxrender1, 
libxss1, libxtst6, zlib1g (>= 1:1.1.4), xdg-utils, chromium-codecs-ffmpeg-extra 
(>= 0.6) | chromium-codecs-ffmpeg (>= 0.6)
  Pre-Depends: dpkg (>= 1.15.6)
  Recommends: chromium-browser-l10n
  Suggests: webaccounts-chromium-extension, unity-chromium-extension, 
pepperflashplugin-nonfree
  Conflicts: chromium-browser-inspector
  Conffiles:
   /etc/default/chromium-browser 00f6b60b3a6a0b3ec9816ac3bae285eb
   /etc/chromium-browser/default 00f6b60b3a6a0b3ec9816ac3bae285eb
  Description: Chromium browser
   Chromium is an open-source browser project that aims to build a safer, 
faster,
   and more stable way for all Internet users to experience the web.
   .
   Chromium serves as a base for Google Chrome, which is Chromium rebranded 
(name
   and logo) with very few additions such as usage tracking and an auto-updater
   system.
   .
   This package contains the Chromium browser
  Homepage: http://code.google.com/chromium/

  $ apt-cache showpkg chromium-browser
  Package: chromium-browser
  Versions: 
  34.0.1847.116-0ubuntu2 
(/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_trusty_universe_binary-amd64_Packages)
 (/var/lib/dpkg/status)
   Description Language: 
   File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_trusty_universe_binary-amd64_Packages
MD5: f899058e5c597ae295f6ef23b467dade
   Description Language: en
   File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_trusty_universe_i18n_Translation-en
MD5: f899058e5c597ae295f6ef23b467dade

  
  Reverse Depends: 
chromium-browser:i386,chromium-browser
mythbuntu-desktop,chromium-browser
webaccounts-chromium-extension,chromium-browser
unity-chromium-extension,chromium-browser 20.0.1132.47~r144678-0ubuntu4
ubuntukylin-default-settings,chromium-browser
mozplugger,chromium-browser
lxde-core,chromium-browser
lxde,chromium-browser
djview-plugin,chromium-browser
djview-plugin,chromium-browser
chromium-chromedriver,chromium-browser 4.0.203.0~
chromium-browser-l10n,chromium-browser
chromium-browser-l10n,chromium-browser 34.0.1847.116-0ubuntu2.1~
chromium-browser-l10n,chromium-browser 34.0.1847.116-0ubuntu2
chromium-browser-dbg,chromium-browser 34.0.1847.116-0ubuntu2
  Dependencies: 
  34.0.1847.116-0ubuntu2 - gconf-service (0 (null)) libasound2 (2 1.0.16) 
libatk1.0-0 (2 1.12.4) libc6 (2 2.15) libcairo2 (2 1.6.0) libcap2 (2 2.10) 
libcomerr2 (2 1.01) libcups2 (2 1.4.0) libdbus-1-3 (2 1.2.14) libexpat1 (2 
2.0.1) libfontconfig1 (2 2.9.0) libfreetype6 (2 2.3.9) libgcc1 (2 1:4.1.1) 
libgconf-2-4 (2 2.31.1) libgcrypt11 (2 1.5.1) libgdk-pixbuf2.0-0 (2 2.22.0) 
libglib2.0-0 (2 2.37.3) libgnome-keyring0 (2 3.2.2-2~) libgnutls26 (2 
2.12.17-0) libgssapi-krb5-2 (2 1.6.dfsg.2

[Desktop-packages] [Bug 1333477] [NEW] Fatal debug logging causes unnecessary crashes

[Ted]

Public bug reported:

This is a simple one.  It relates to these upstream bug reports (dupes):

https://code.google.com/p/chromium/issues/detail?id=357473
https://code.google.com/p/chromium/issues/detail?id=371355

Basically, the Chromium devs put a LOG(FATAL) in unofficial builds. So
Chrome works fine, but not Chromium. The browser isn't actually crashing
on its own, instead the LOG(FATAL) is killing the browser in order to
get the attention of the user so they'll file a bug report.  This sounds
fine if it's a developer running the browser, but end users shouldn't
have their browser crash because of an arbitrary FATAL log message.

The Ubuntu package should remove the LOG(FATAL) entirely so that the
Chromium builds will work like the Chrome builds do, and not crash.  The
exact file/line/code is mentioned in the second bug report above.

** Affects: chromium-browser (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/1333477

Title:
  Fatal debug logging causes unnecessary crashes

Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  This is a simple one.  It relates to these upstream bug reports
  (dupes):

  https://code.google.com/p/chromium/issues/detail?id=357473
  https://code.google.com/p/chromium/issues/detail?id=371355

  Basically, the Chromium devs put a LOG(FATAL) in unofficial builds. So
  Chrome works fine, but not Chromium. The browser isn't actually
  crashing on its own, instead the LOG(FATAL) is killing the browser in
  order to get the attention of the user so they'll file a bug report.
  This sounds fine if it's a developer running the browser, but end
  users shouldn't have their browser crash because of an arbitrary FATAL
  log message.

  The Ubuntu package should remove the LOG(FATAL) entirely so that the
  Chromium builds will work like the Chrome builds do, and not crash.
  The exact file/line/code is mentioned in the second bug report above.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1333477/+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 1310163] Re: chromium-browser with multiple tabs crashes on startup in KDE environment

[Ted]

This appears to be related to this upstream bug report:

https://code.google.com/p/chromium/issues/detail?id=357473

Basically, the Chromium devs put a LOG(FATAL) in unofficial builds.  So
Chrome works fine, but not Chromium.  The browser isn't actually
crashing on its own, instead the LOG(FATAL) is killing the browser in
order to get the attention of the user so they'll file a bug report.

This is not related to KDE, KWallet, multiple tabs, or even starting up.
It has to do with sending secure referrers to insecure hosts, which one
of your tabs must have been doing.  Going to any HTTPS page, right
clicking a link and choosing "Save link as..." will cause this "crash".

** Bug watch added: code.google.com/p/chromium/issues #357473
   http://code.google.com/p/chromium/issues/detail?id=357473

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

Title:
  chromium-browser with multiple tabs crashes on startup in KDE
  environment

Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  first output is with kwallet disabled.

  second output is after re-enabling kwallet

  ruce@Pericles:~$ ATTENTION: default value of option force_s3tc_enable 
overridden by environment.
  [6251:6251:0419/183400:ERROR:sandbox_linux.cc(268)] InitializeSandbox() 
called with multiple threads in process gpu-process
  [6208:6239:0419/183401:ERROR:object_proxy.cc(566)] Failed to call method: 
org.kde.KWallet.isEnabled: object_path= /modules/kwalletd: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.kwalletd was not 
provided by any .service files
  [6208:6239:0419/183401:ERROR:native_backend_kwallet_x.cc(228)] Error 
contacting kwalletd (isEnabled)
  [6208:6239:0419/183401:ERROR:object_proxy.cc(566)] Failed to call method: 
org.kde.KWallet.isEnabled: object_path= /modules/kwalletd: 
org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by 
message bus)
  [6208:6239:0419/183401:ERROR:native_backend_kwallet_x.cc(228)] Error 
contacting kwalletd (isEnabled)
  [6208:6208:0419/183402:ERROR:profile_sync_service.cc(1315)] History Delete 
Directives datatype error was encountered: Delete directives not supported with 
encryption.
  [6208:6313:0419/183404:ERROR:download.cc(109)] PostClientToServerMessage() 
failed during GetUpdates
  [6208:6244:0419/183411:FATAL:url_request.cc(707)] Trying to send secure 
referrer for insecure load

  [1]+  Aborted (core dumped) chromium-browser
  bruce@Pericles:~$ chromium-browser &
  [1] 7505
  bruce@Pericles:~$ ATTENTION: default value of option force_s3tc_enable 
overridden by environment.
  [7548:7548:0419/183625:ERROR:sandbox_linux.cc(268)] InitializeSandbox() 
called with multiple threads in process gpu-process
  [7505:7505:0419/183628:ERROR:profile_sync_service.cc(1315)] History Delete 
Directives datatype error was encountered: Delete directives not supported with 
encryption.
  [7505:7541:0419/183635:FATAL:url_request.cc(707)] Trying to send secure 
referrer for insecure load

  [1]+  Aborted (core dumped) chromium-browser

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr 19 22:46:35 2014
  Desktop-Session:
   DESKTOP_SESSION = kde-plasma
   XDG_CONFIG_DIRS = /etc/xdg/xdg-kde-plasma:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share:/usr/share/kde-plasma:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2013-02-26 (417 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (0 days ago)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'firefox 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'firefox 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1310163/+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 1300844] Re: No sound kernel 3.13 ALC887-VD but kernel 3.14 fixes it

[ted chang]

Nope,

my fix was updating the hda audio drivers. I realize there wasnt any
audio support for my gigabyte mobo.

I alsa had the problem where the sound is not emitting from the green
audio jack. My computer doesnt have an hdmi cord plug in. I was using
dvi cable for my monitor and audio jack for my headphones.

Pulseaudio is not showing the audio card. alsamixer is not showing the
proper volume options.

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

Title:
  No sound kernel 3.13 ALC887-VD but kernel 3.14 fixes it

Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  My sound hardware doesnt seem to be supported on the vanilla ubuntu
  13.10 or 14.04. However, the fix seems to be updating the kernel to
  3.14. This sound card is integrated in the motherboard and I am using
  the analog jack. I am not sure whether or not to report it as a bug or
  something.

  http://www.gigabyte.us/products/product-page.aspx?pid=4716#sp

  3.14.0-031400-generic

  aplay -l

   List of PLAYBACK Hardware Devices 
  card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 1: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD 
Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 1: Generic_1 [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD 
Digital]
    Subdevices: 1/1
    Subdevice #0: subdevice #0

  lspci -v

  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia 
Controller (rev 01)
   Subsystem: Gigabyte Technology Co., Ltd Device a002
   Flags: bus master, slow devsel, latency 32, IRQ 16
   Memory at feb6 (64-bit, non-prefetchable) [size=16K]
   Capabilities: 
   Kernel driver in use: snd_hda_intel

  alsa info under 3.14 kernel

   http://www.alsa-
  project.org/db/?f=c76bbb46111cbb9bfcd7a1f1cc5d9abde8f4f6a8

  alsa info under vanilla 14.04 kernel

  http://www.alsa-
  project.org/db/?f=3219c41b19ff4b97586f2589895b461251e0baec

  reporting it as a bug as actionparsnip (andrew-woodhead666) suggestion

  https://answers.launchpad.net/ubuntu/+source/linux/+question/246337
  --- 
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  poison 1944 F pulseaudio
   /dev/snd/controlC0:  poison 1944 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=02989b06-ff3e-4ac9-b73f-a69797aa4933
  InstallationDate: Installed on 2014-04-01 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-19-generic 
root=UUID=0a2fcf96-eec0-439b-9ae4-c6eb8f897712 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-19-generic N/A
   linux-backports-modules-3.13.0-19-generic  N/A
   linux-firmware 1.127
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XM-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1300844/+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 1300844] Re: No sound kernel 3.13 ALC887-VD but kernel 3.14 fixes it

[ted chang]

Opps, i realize what you mean by the bug.

It is it seriously the bug that affects most gigabyte mobos?

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

Title:
  No sound kernel 3.13 ALC887-VD but kernel 3.14 fixes it

Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  My sound hardware doesnt seem to be supported on the vanilla ubuntu
  13.10 or 14.04. However, the fix seems to be updating the kernel to
  3.14. This sound card is integrated in the motherboard and I am using
  the analog jack. I am not sure whether or not to report it as a bug or
  something.

  http://www.gigabyte.us/products/product-page.aspx?pid=4716#sp

  3.14.0-031400-generic

  aplay -l

   List of PLAYBACK Hardware Devices 
  card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 1: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD 
Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 1: Generic_1 [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD 
Digital]
    Subdevices: 1/1
    Subdevice #0: subdevice #0

  lspci -v

  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia 
Controller (rev 01)
   Subsystem: Gigabyte Technology Co., Ltd Device a002
   Flags: bus master, slow devsel, latency 32, IRQ 16
   Memory at feb6 (64-bit, non-prefetchable) [size=16K]
   Capabilities: 
   Kernel driver in use: snd_hda_intel

  alsa info under 3.14 kernel

   http://www.alsa-
  project.org/db/?f=c76bbb46111cbb9bfcd7a1f1cc5d9abde8f4f6a8

  alsa info under vanilla 14.04 kernel

  http://www.alsa-
  project.org/db/?f=3219c41b19ff4b97586f2589895b461251e0baec

  reporting it as a bug as actionparsnip (andrew-woodhead666) suggestion

  https://answers.launchpad.net/ubuntu/+source/linux/+question/246337
  --- 
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  poison 1944 F pulseaudio
   /dev/snd/controlC0:  poison 1944 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=02989b06-ff3e-4ac9-b73f-a69797aa4933
  InstallationDate: Installed on 2014-04-01 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-19-generic 
root=UUID=0a2fcf96-eec0-439b-9ae4-c6eb8f897712 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-19-generic N/A
   linux-backports-modules-3.13.0-19-generic  N/A
   linux-firmware 1.127
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XM-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1300844/+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 1302253] Re: [GA-78LMT-USB3, Realtek ALC887-VD, Green Line Out, Rear] Pulseaudio fails to detect card

[ted chang]

I dont think this is a pulseaudio bug. I actually have a similar bug
with similar behavior but I decided to update the alsa stack and it
fixed it.

https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1300844

Try updating sound as these instructions

https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS

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

Title:
  [GA-78LMT-USB3, Realtek ALC887-VD, Green Line Out, Rear] Pulseaudio
  fails to detect card

Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  No sound on any package, sound settings shows "Dummy Output".  Just allowed 
Software Updater to install large upgrade, 300+ packages.
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu10
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', 
'/dev/snd/pcmC1D7p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Thu Apr  3 18:30:55 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-03-30 (4 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA ATI SB
  Symptom_Jack: Green Line Out, Rear
  Title: [GA-78LMT-USB3, Realtek ALC887-VD, Green Line Out, Rear] Pulseaudio 
fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/19/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/19/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1302253/+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 1300844] Re: No sound kernel 3.13 ALC887-VD but kernel 3.14 fixes it

[ted chang]

Thanks, Raymond. I decided to update the alsa driver stack. basd on
these instructions

https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS

https://code.launchpad.net/~ubuntu-audio-dev/+archive/alsa-
daily/+packages

I am using

 oem-audio-hda-daily-dkms - 0.201404230703~ubuntu14.04.1

which fixes the problem

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

Title:
  No sound kernel 3.13 ALC887-VD but kernel 3.14 fixes it

Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  My sound hardware doesnt seem to be supported on the vanilla ubuntu
  13.10 or 14.04. However, the fix seems to be updating the kernel to
  3.14. This sound card is integrated in the motherboard and I am using
  the analog jack. I am not sure whether or not to report it as a bug or
  something.

  http://www.gigabyte.us/products/product-page.aspx?pid=4716#sp

  3.14.0-031400-generic

  aplay -l

   List of PLAYBACK Hardware Devices 
  card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 1: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD 
Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 1: Generic_1 [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD 
Digital]
    Subdevices: 1/1
    Subdevice #0: subdevice #0

  lspci -v

  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia 
Controller (rev 01)
   Subsystem: Gigabyte Technology Co., Ltd Device a002
   Flags: bus master, slow devsel, latency 32, IRQ 16
   Memory at feb6 (64-bit, non-prefetchable) [size=16K]
   Capabilities: 
   Kernel driver in use: snd_hda_intel

  alsa info under 3.14 kernel

   http://www.alsa-
  project.org/db/?f=c76bbb46111cbb9bfcd7a1f1cc5d9abde8f4f6a8

  alsa info under vanilla 14.04 kernel

  http://www.alsa-
  project.org/db/?f=3219c41b19ff4b97586f2589895b461251e0baec

  reporting it as a bug as actionparsnip (andrew-woodhead666) suggestion

  https://answers.launchpad.net/ubuntu/+source/linux/+question/246337
  --- 
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  poison 1944 F pulseaudio
   /dev/snd/controlC0:  poison 1944 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=02989b06-ff3e-4ac9-b73f-a69797aa4933
  InstallationDate: Installed on 2014-04-01 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-19-generic 
root=UUID=0a2fcf96-eec0-439b-9ae4-c6eb8f897712 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-19-generic N/A
   linux-backports-modules-3.13.0-19-generic  N/A
   linux-firmware 1.127
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XM-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1300844/+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 1296715] Re: Menu items are greyed out in Libreoffice menu.

[Ted Gould]

It looks like this is an LO issue. Looking at the example of insert
table, the action is set to disabled:

$ gdbus call --session --dest :1.194 --object-path 
/org/libreoffice/window/88080484/menus/menubar --method org.gtk.Menus.Start [0]
([(uint32 0, uint32 0, [{':section': <(uint32 0, uint32 5)>}]), (0, 5, 
[{':section': <(uint32 0, uint32 6)>}]), (0, 6, [{'command': <'.uno:PickList'>, 
'label': <'_File'>, 'submenu-action': <'win..uno:PickList'>, ':submenu': 
<(uint32 72, uint32 0)>}, {'command': <'.uno:EditMenu'>, 'label': <'_Edit'>, 
'submenu-action': <'win..uno:EditMenu'>, ':submenu': <(uint32 73, uint32 0)>}, 
{'command': <'.uno:ViewMenu'>, 'label': <'_View'>, 'submenu-action': 
<'win..uno:ViewMenu'>, ':submenu': <(uint32 74, uint32 0)>}, {'command': 
<'.uno:InsertMenu'>, 'label': <'_Insert'>, 'submenu-action': 
<'win..uno:InsertMenu'>, ':submenu': <(uint32 75, uint32 0)>}, {'command': 
<'.uno:FormatMenu'>, 'label': <'F_ormat'>, 'submenu-action': 
<'win..uno:FormatMenu'>, ':submenu': <(uint32 76, uint32 0)>}, {'command': 
<'.uno:TableMenu'>, 'label': <'T_able'>, 'submenu-action': 
<'win..uno:TableMenu'>, ':submenu': <(uint32 77, uint32 0)>}, {'command': 
<'.uno:ToolsMenu'>, 'label': <'_Tools'>, 'submenu-action': 
<'win..uno:ToolsMenu'>, ':submenu': <(uint32 78, uint32 0)>}, {'command': 
<'.uno:WindowList'>, 'label': <'_Window'>, 'submenu-action': 
<'win..uno:WindowList'>, ':submenu': <(uint32 79, uint32 0)>}, {'command': 
<'.uno:HelpMenu'>, 'label': <'_Help'>, 'submenu-action': <'win..uno:HelpMenu'>, 
':submenu': <(uint32 80, uint32 0)>}])],)
$ gdbus call --session --dest :1.194 --object-path 
/org/libreoffice/window/88080484/menus/menubar --method org.gtk.Menus.Start [75]
([(uint32 75, uint32 6, [{'action': <'win..uno:InsertDoc'>, 'command': 
<'.uno:InsertDoc'>, 'label': <'_File...'>}]), (75, 0, [{':section': <(uint32 
75, uint32 1)>}, {':section': <(uint32 75, uint32 2)>}, {':section': <(uint32 
75, uint32 3)>}, {':section': <(uint32 75, uint32 4)>}, {':section': <(uint32 
75, uint32 5)>}, {':section': <(uint32 75, uint32 6)>}]), (75, 1, [{'action': 
<'win..uno:InsertBreak'>, 'command': <'.uno:InsertBreak'>, 'label': <'Manual 
_Break...'>}, {'command': <'.uno:FieldMenu'>, 'label': <'Fiel_ds'>, 
'submenu-action': <'win..uno:FieldMenu'>, ':submenu': <(uint32 94, uint32 0)>}, 
{'action': <'win..uno:InsertSymbol'>, 'command': <'.uno:InsertSymbol'>, 
'label': <'S_pecial Character...'>}, {'command': <'.uno:FormattingMarkMenu'>, 
'label': <'Formatting Mark'>, 'submenu-action': 
<'win..uno:FormattingMarkMenu'>, ':submenu': <(uint32 95, uint32 0)>}]), (75, 
3, [{'command': <'.uno:InsertPageHeader'>, 'label': <'He_ader'>, 
'submenu-action': <'win..uno:InsertPageHeader'>, ':submenu': <(uint32 96, 
uint32 0)>}, {'command': <'.uno:InsertPageFooter'>, 'label': <'Foote_r'>, 
'submenu-action': <'win..uno:InsertPageFooter'>, ':submenu': <(uint32 97, 
uint32 0)>}, {'action': <'win..uno:InsertFootnoteDialog'>, 'command': 
<'.uno:InsertFootnoteDialog'>, 'label': <'Footnote/Endnote_...'>}, {'action': 
<'win..uno:InsertCaptionDialog'>, 'command': <'.uno:InsertCaptionDialog'>, 
'label': <'Caption...'>}, {'action': <'win..uno:InsertBookmark'>, 'command': 
<'.uno:InsertBookmark'>, 'label': <'Bookmar_k...'>}, {'action': 
<'win..uno:InsertReferenceField'>, 'command': <'.uno:InsertReferenceField'>, 
'label': <'Cross-reference...'>}, {'action': <'win..uno:InsertAnnotation'>, 
'command': <'.uno:InsertAnnotation'>, 'label': <'Comme_nt'>, 'accel': 
<'c'>}, {'action': <'win..uno:InsertScript'>, 'command': 
<'.uno:InsertScript'>, 'label': <'S_cript...'>}, {'command': 
<'.uno:IndexesMenu'>, 'label': <'Inde_xes and Tables'>, 'submenu-action': 
<'win..uno:IndexesMenu'>, ':submenu': <(uint32 98, uint32 0)>}]), (75, 2, 
[{'action': <'win..uno:InsertSection'>, 'command': <'.uno:InsertSection'>, 
'label': <'_Section...'>}, {'action': <'win..uno:HyperlinkDialog'>, 'command': 
<'.uno:HyperlinkDialog'>, 'label': <'_Hyperlink'>, 'accel': <'k'>}]), 
(75, 5, [{'action': <'win..uno:InsertFrame'>, 'command': <'.uno:InsertFrame'>, 
'label': <'Fra_me...'>}, {'action': <'win..uno:InsertTable'>, 'command': 
<'.uno:InsertTable'>, 'label': <'_Table...'>, 'accel': <'F12'>}, 
{'command': <'.uno:GraphicMenu'>, 'label': <'_Image'>, 'submenu-action': 
<'win..uno:GraphicMenu'>, ':submenu': <(uint32 99, uint32 0)>}, {'action': 
<'win..uno:InsertAVMedia'>, 'command': <'.uno:InsertAVMedia'>, 'label': 
<'Mo_vie and Sound...'>}, {'command': <'.uno:ObjectMenu'>, 'label': 
<'_Object'>, 'submenu-action': <'win..uno:ObjectMenu'>, ':submenu': <(uint32 
100, uint32 0)>}, {'action': <'win..uno:InsertObjectFloatingFrame'>, 'command': 
<'.uno:InsertObjectFloatingFrame'>, 'label': <'Float_ing Frame...'>}]), (75, 4, 
[{'action': <'win..uno:InsertEnvelope'>, 'command': <'.uno:InsertEnvelope'>, 
'label': <'En_velope...'>}])],)
$ gdbus call --session --dest :1.194 --object-path 
/org/libreoffice/window/88080484 --method org.gtk.Actions.Describe 
.uno:InsertTable
((false, signa