date:20181108

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  i go to the site and firefox error

Status in firefox package in Ubuntu:
  Expired

Bug description:
  i go to http://www.exploit-db.com/download/18531/  and click go.
  firefox error

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: firefox 10.0.2+build1-0ubuntu0.11.10.1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic i686
  NonfreeKernelModules: fglrx
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cagatay1651 F pulseaudio
   /dev/snd/controlC0:  cagatay1651 F pulseaudio
  BuildID: 20120216101208
  CRDA: Error: [Errno 2] Böyle bir dosya ya da dizin yok
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xe310 irq 44'
 Mixer name : 'Realtek ALC662 rev1'
 Components : 'HDA:10ec0662,1458a002,00100101'
 Controls  : 34
 Simple ctrls  : 18
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xe101 irq 45'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,0010'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Channel: release
  Date: Thu Mar  1 22:09:22 2012
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  IpRoute:
   default via 192.168.2.1 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.2.0/24 dev wlan0  proto kernel  scope link  src 192.168.2.2  metric 2
  ProcEnviron:
   LANGUAGE=tr_CY:tr
   PATH=(custom, no user)
   LANG=tr_CY.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=10.0.2/20120216101208 (Running)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: G31M-S2L
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd06/05/2008:svnGigabyteTechnologyCo.,Ltd.:pnG31M-S2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-S2L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G31M-S2L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/944305/+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 692856] Re: Secure Connection Failed

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Secure Connection Failed

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Binary package hint: firefox

  I tried to access https://ib.bankmandiri.co.id and this error
  appeared:

  Secure Connection Failed

  An error occurred during a connection to ib.bankmandiri.co.id.

  Peer's Certificate has been revoked.

  (Error code: sec_error_revoked_certificate)

  *   The page you are trying to view can not be shown because the
  authenticity of the received data could not be verified.

  *   Please contact the web site owners to inform them of this
  problem. Alternatively, use the command found in the help menu to
  report this broken site.

  but if I access the site with firefox windows version, the site is OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: firefox 3.6.3+nobinonly-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic i686
  Architecture: i386
  Date: Tue Dec 21 12:14:47 2010
  FirefoxPackages:
   firefox 3.6.3+nobinonly-0ubuntu4
   firefox-gnome-support 3.6.3+nobinonly-0ubuntu4
   firefox-branding 3.6.3+nobinonly-0ubuntu4
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/692856/+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 800517] Re: While the pages are loading , firefox freezes(minimise it and it disturbs my screen)

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  While the pages are loading , firefox freezes(minimise it and it
  disturbs my screen)

Status in firefox package in Ubuntu:
  Expired

Bug description:
  I am using 
  Ubuntu release 11.04(natty)
  Kernel Linux 2.6.38-8-generic 
  GNOME 2.32.1
  While the pages are loading , firefox freezes and the screen dims (minimise 
it and it disturbs my screen)
  SO until the page is fully loaded it hangs and there is also the same problem 
when I switch tabs , It has been a problem of late . I had updated to latest 
firefox update but the bug keeps on bugging .

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: firefox 5.0+build1+nobinonly-0ubuntu0.11.04.1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Wed Jun 22 11:54:20 2011
  FirefoxPackages:
   firefox 5.0+build1+nobinonly-0ubuntu0.11.04.1
   flashplugin-installer 10.3.181.26ubuntu0.11.04.1
   adobe-flashplugin N/A
   icedtea-plugin 1.1~20110420-0ubuntu1.1
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_IN:en
   LANG=en_IN
   LC_MESSAGES=en_IN.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/800517/+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 988155] Re: Sometimes left mouse button can't use.

[Expired for unity (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Sometimes left mouse button can't use.

Status in Unity:
  Incomplete
Status in chromium-browser package in Ubuntu:
  Expired
Status in unity package in Ubuntu:
  Expired

Bug description:
  Sometimes left mouse button can't use.But right mouse button can use.
  Can this be fixed by pressing the button about 20 times or use other mouse.

  I'm using
  
http://shopap.lenovo.com/SEUILibrary/controller/e/jpweb/LenovoPortal/ja_JP/catalog.workflow:item.detail?GroupID=460=06P4069
  
  id=3FB2CEB78A0F49D18148731559AF4603_menu_area=yes#learnMore

  [How To Reproduce]

  Maybe use Chromium browser.This problem happen whereever.

  [Actual Result]

  Sometimes left mouse button can't use.But right mouse button can use.
  And wait for a minutes, it can use.

  [Expected Result]

  Nothing

  Sorry for my bad English.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: unity 4.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-17.30-generic-pae 3.0.22
  Uname: Linux 3.0.0-17-generic-pae i686
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  CheckboxSubmission: e0db21cad67afb16c9db682e9874ca13
  CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,move,snap,place,resize,grid,gnomecompat,session,imgpng,vpswitch,regex,mousepoll,unitymtgrabhandles,wall,animation,expo,ezoom,workarounds,fade,scale,unityshell]
  CompositorRunning: compiz
  Date: Wed Apr 25 12:57:11 2012
  DistUpgraded: Fresh install
  DistroCodename: oneiric
  DistroVariant: ubuntu
  DkmsStatus: fglrx, 8.881, 3.0.0-17-generic-pae, i686: installed
  GraphicsCard:
   ATI Technologies Inc Device [1002:9641] (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21eb]
   ATI Technologies Inc NI Seymour [AMD Radeon HD 6470M] [1002:6760] (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21eb]
  InstallationMedia: Ubuntu 11.10 "Oneiric" - Build i386 LIVE Binary 
20111015-16:02
  JockeyStatus:
   xorg:fglrx_updates - ATI/AMD プロプライエタリ FGLRX グラフィックスドライバー（リリースアップデート） 
(プロプライエタリ, 使用しない, 使用されていません)
   xorg:fglrx - ATI/AMD プロプライエタリ FGLRX グラフィックスドライバー (プロプライエタリ, 有効にする, 使用中)
  MachineType: LENOVO 1198CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-17-generic-pae 
root=UUID=5d0c8080-7869-4fb0-a8e7-c0c7d2cedfa9 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GBET01WW(1.01)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 1198CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGBET01WW(1.01):bd09/27/2011:svnLENOVO:pn1198CTO:pvrThinkPadE425:rvnLENOVO:rn1198CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 1198CTO
  dmi.product.version: ThinkPad E425
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6.1
  version.fglrx-installer: fglrx-installer N/A
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3.2
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.15.901-1ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/988155/+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 790144] Re: address bar popup, bookmarks toolbar popup broken under certain conditions

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  address bar popup, bookmarks toolbar popup broken under certain
  conditions

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Binary package hint: firefox

  Steps to produce the problem (mostly, unfortunately not every time):
  switch to another workspace in Unity (Ctrl-Alt left/right/up/down), then 
switch back to the workspace where firefox is, press Ctrl-T to open a new tab 
and type in the address bar.
  No popup will be shown. Also if you have bookmarks in the bookmark toolbar, 
the popups will not open.

  This also is likely to happen if the screensaver was active before.
  Pressing Alt-Tab to push the window in the background and back to foreground 
again makes the popup work.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: firefox 4.0.1+build1+nobinonly-0ubuntu0.11.04.3
  ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4
  Uname: Linux 2.6.38-9-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Mon May 30 11:54:04 2011
  FirefoxPackages:
   firefox 4.0.1+build1+nobinonly-0ubuntu0.11.04.3
   flashplugin-installer 10.3.181.14ubuntu0.11.04.1
   adobe-flashplugin N/A
   icedtea-plugin N/A
  ProcEnviron:
   LANGUAGE=de_AT:en
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: Upgraded to natty on 2011-05-22 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/790144/+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 988155] Re: Sometimes left mouse button can't use.

[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Sometimes left mouse button can't use.

Status in Unity:
  Incomplete
Status in chromium-browser package in Ubuntu:
  Expired
Status in unity package in Ubuntu:
  Expired

Bug description:
  Sometimes left mouse button can't use.But right mouse button can use.
  Can this be fixed by pressing the button about 20 times or use other mouse.

  I'm using
  
http://shopap.lenovo.com/SEUILibrary/controller/e/jpweb/LenovoPortal/ja_JP/catalog.workflow:item.detail?GroupID=460=06P4069
  
  id=3FB2CEB78A0F49D18148731559AF4603_menu_area=yes#learnMore

  [How To Reproduce]

  Maybe use Chromium browser.This problem happen whereever.

  [Actual Result]

  Sometimes left mouse button can't use.But right mouse button can use.
  And wait for a minutes, it can use.

  [Expected Result]

  Nothing

  Sorry for my bad English.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: unity 4.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-17.30-generic-pae 3.0.22
  Uname: Linux 3.0.0-17-generic-pae i686
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  CheckboxSubmission: e0db21cad67afb16c9db682e9874ca13
  CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,move,snap,place,resize,grid,gnomecompat,session,imgpng,vpswitch,regex,mousepoll,unitymtgrabhandles,wall,animation,expo,ezoom,workarounds,fade,scale,unityshell]
  CompositorRunning: compiz
  Date: Wed Apr 25 12:57:11 2012
  DistUpgraded: Fresh install
  DistroCodename: oneiric
  DistroVariant: ubuntu
  DkmsStatus: fglrx, 8.881, 3.0.0-17-generic-pae, i686: installed
  GraphicsCard:
   ATI Technologies Inc Device [1002:9641] (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21eb]
   ATI Technologies Inc NI Seymour [AMD Radeon HD 6470M] [1002:6760] (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21eb]
  InstallationMedia: Ubuntu 11.10 "Oneiric" - Build i386 LIVE Binary 
20111015-16:02
  JockeyStatus:
   xorg:fglrx_updates - ATI/AMD プロプライエタリ FGLRX グラフィックスドライバー（リリースアップデート） 
(プロプライエタリ, 使用しない, 使用されていません)
   xorg:fglrx - ATI/AMD プロプライエタリ FGLRX グラフィックスドライバー (プロプライエタリ, 有効にする, 使用中)
  MachineType: LENOVO 1198CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-17-generic-pae 
root=UUID=5d0c8080-7869-4fb0-a8e7-c0c7d2cedfa9 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GBET01WW(1.01)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 1198CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGBET01WW(1.01):bd09/27/2011:svnLENOVO:pn1198CTO:pvrThinkPadE425:rvnLENOVO:rn1198CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 1198CTO
  dmi.product.version: ThinkPad E425
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6.1
  version.fglrx-installer: fglrx-installer N/A
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3.2
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.15.901-1ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/988155/+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 614761] Re: audio and video will not play in browser, Sound Preferences report no application is currently playing or recording audio

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  audio and video will not play in browser, Sound Preferences report no
  application is currently playing or recording audio

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Binary package hint: firefox

  Firefox Package.

  Video screen comes up black on YouTube, no sound or video.

  mp3.walmart.com - no audio previews work.

  RhythmBox application plays mp3's flawlessly.  I know the audio is
  working.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: firefox 3.6.8+build1+nobinonly-0ubuntu0.10.04.1
  ProcVersionSignature: Ubuntu 2.6.32-24.39-server 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-24-server x86_64
  Architecture: amd64
  Date: Sat Aug  7 12:02:49 2010
  FirefoxPackages:
   firefox 3.6.8+build1+nobinonly-0ubuntu0.10.04.1
   firefox-gnome-support 3.6.8+build1+nobinonly-0ubuntu0.10.04.1
   firefox-branding 3.6.8+build1+nobinonly-0ubuntu0.10.04.1
   abroswer N/A
   abrowser-branding N/A
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/614761/+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 1789356] Re: Dark purple (noise) background flashes up briefly during the login animation

This bug was fixed in the package gnome-shell - 3.30.1-2ubuntu2

---
gnome-shell (3.30.1-2ubuntu2) disco; urgency=medium

  [ Didier Roche ]
  * debian/patches/ubuntu/background_login.patch:
- match Yaru theme in the ubuntu session instead of our previous GDM
  background (LP: #1789356)
  * debian/patches/ubuntu/resolve_alternate_theme_path.patch:
- ensure we resolve finale theme file path to correctly load assets
  under gdm (LP: #1798747)

  [ Marco Trevisan (Treviño) ]
  * debian/patches/st-button-Ignore-pointer-emulated-touch-events.patch:
- Don't emit two click events on touch under X11 (LP: #1745888)

 -- Iain Lane   Wed, 07 Nov 2018 11:05:30 +

** Changed in: gnome-shell (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Dark purple (noise) background flashes up briefly during the login
  animation

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Cosmic:
  In Progress

Bug description:
  [Impact]

  Dark purple (noise) background flashes up briefly (for a split second) during 
the login animation.
  The login screen and gnome-shell's system background are meant to be the same 
image so that the login procedure can VT switch without the user noticing. Then 
the final desktop expands over the system background. However it appears the 
login background and system background are not the same image any more, causing 
a visible glitch during login.

  [Test Case]

  1. Install new version, logout
  2. Log in into GDM
  -> Check that at login startup, the background matches GDM ones (same color, 
same gradient)
  3. Logout, install gnome-session
  4. Reboot so that GDM takes gnome-session into account
  5. Select GNOME session and login
  -> At login startup, the background will matche the GNOME default one (from 
the lockscreen: grey noise), which matches GDM one if reset to default GNOME 
via update-alternatives.

  [Regression Potential]

  This code is loaded at session startup, if there is a syntax error, the 
session wouldn't start at all.
  This has been of course tested before committed (both on ubuntu and GNOME 
sessions)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: yaru-theme-gnome-shell 18.10.2
  ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12
  Uname: Linux 4.17.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Tue Aug 28 14:19:48 2018
  Dependencies:

  InstallationDate: Installed on 2018-05-26 (93 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: yaru-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789356/+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 1768271] Re: sudo update-desktop-database results in "font/ttf" is an invalid MIME type ("font" is an unregistered media type)

This bug was fixed in the package desktop-file-utils - 0.23-4ubuntu1

---
desktop-file-utils (0.23-4ubuntu1) disco; urgency=medium

  * Resynchronize on Debian, remaining changes
  * debian/defaults.list, debian/desktop-file-utils.install,
debian/desktop-file-utils.links:
- install the defaults handlers list

desktop-file-utils (0.23-4) unstable; urgency=medium

  * Team upload
  * Add add-font-as-valid-media-type.patch:
- Fix update-desktop-error with gnome-font-viewer 3.28 (LP: #1768271)

 -- Sebastien Bacher   Tue, 06 Nov 2018 16:23:28
+0100

** Changed in: desktop-file-utils (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  sudo update-desktop-database results in "font/ttf" is an invalid MIME
  type ("font" is an unregistered media type)

Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in desktop-file-utils source package in Bionic:
  Triaged

Bug description:
  * Impact

  The "update-desktop-database" command outputs some "invalid MIME type"
  warnings

  * Test case

  - install gnome-font-viewer if it's not installed
  - $ sudo update-desktop-database

  you should not get warnings like those
  Error in file "/usr/share/applications/org.gnome.font-viewer.desktop": 
"font/ttf" is an invalid MIME type ("font" is an unregistered media type)
  Error in file "/usr/share/applications/org.gnome.font-viewer.desktop": 
"font/otf" is an invalid MIME type ("font" is an unregistered media type)

  * Regression potential

  Check that fonts files can still be opened from nautilus and preview
  (browse e.g /usr/share/fonts/type1/gsfonts in nautilus and open a file
  from there)

  --

  I think this is the same bug as this one:
  https://bugzilla.redhat.com/show_bug.cgi?id=1564650

  Other info:
  1.
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  2.
  $ apt-cache policy desktop-file-utils
  desktop-file-utils:
    Installed: 0.23-1ubuntu3
    Candidate: 0.23-1ubuntu3
    Version table:
   *** 0.23-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. Expected `sudo update-desktop-database` to not return an error
  4. Error regarding invalid MIME type (see above) was returned.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: desktop-file-utils 0.23-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 11:11:05 2018
  InstallationDate: Installed on 2018-04-29 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: desktop-file-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1768271/+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 1787907] Re: Nautilus cannot resolve remote adress using sftp

[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Nautilus cannot resolve remote adress using sftp

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  This happens after reinstall Ubuntu 14.04. LTS. The machine is a HP with 5,8 
GiB RAM, Intel® Xeon(R) CPU W3503 @ 2.40GHz × 2. All necessary packages are 
installed (gvs backend etc.)and the machine was updated 19th of August 2018. 
Connections with SSH to  all servers are working well in the console. The sftü 
command in Nautilus gives me the error: Adress is unresolvable Check your 
network connection and settings. The file under.ssh in home directory is up to 
date with the keys due to the connections via terminal.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  GsettingsChanges: org.gnome.nautilus.list-view default-column-order ['name', 
'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']
  InstallationDate: Installed on 2018-08-22 (18 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  Package: nautilus 1:3.10.1-0ubuntu9.11
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-134.160~14.04.1-generic 4.4.140
  Tags:  trusty
  Uname: Linux 4.4.0-134-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1787907/+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 1791289] Re: Shows duplicate xdg directories for snaps

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Shows duplicate xdg directories for snaps

Status in gnome-shell package in Ubuntu:
  Expired
Status in tracker package in Ubuntu:
  Expired

Bug description:
  See attached screenshot. If I search for Downloads, I also get
  symlinks to ~/Downloads generated in ~/snap/spotify/16/Downloads, for
  example.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791289/+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 1745888] Re: Two instances of a program launch whenever you touch a favorites icon

This bug was fixed in the package gnome-shell - 3.30.1-2ubuntu2

---
gnome-shell (3.30.1-2ubuntu2) disco; urgency=medium

  [ Didier Roche ]
  * debian/patches/ubuntu/background_login.patch:
- match Yaru theme in the ubuntu session instead of our previous GDM
  background (LP: #1789356)
  * debian/patches/ubuntu/resolve_alternate_theme_path.patch:
- ensure we resolve finale theme file path to correctly load assets
  under gdm (LP: #1798747)

  [ Marco Trevisan (Treviño) ]
  * debian/patches/st-button-Ignore-pointer-emulated-touch-events.patch:
- Don't emit two click events on touch under X11 (LP: #1745888)

 -- Iain Lane   Wed, 07 Nov 2018 11:05:30 +

** Changed in: gnome-shell (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Two instances of a program launch whenever you touch a favorites icon

Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  In Progress
Status in gnome-shell source package in Cosmic:
  In Progress

Bug description:
  [ Impact ]

  Using a touch screen, if you tap on a favorites icon on the ubuntu
  dock, two (or more) instances of an application launch.

  [ Test case ]

  - Look for xterm in gnome-shell activities and add it to favourtes
  - With the ubuntu-dock showing in the desktop, touch the xterm icon
  - Only one instance if it should open
  - Tapping the app icons grid should properly open the g-s overview
  - Tapping on dock icons when in overview mode should work normally

  [ Regression potential ]

  Taps on other gnome-shell buttons could not work poperly (like some
  menu items or app grid)


  
  ProblemType: BugDistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-ubuntu-dock 0.7.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jan 28 19:47:17 2018
  InstallationDate: Installed on 2018-01-28 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2018.01.26 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1745888/+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 1643361] Re: hp-testpage fails AttributeError: module 'base.pexpect' has no attribute 'EOF'

[Expired for hplip (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  hp-testpage fails AttributeError: module 'base.pexpect' has no
  attribute 'EOF'

Status in hplip package in Ubuntu:
  Expired

Bug description:
  Ubuntu 16.04, hplip 3.16.3+repack0-1

  $ hp-testpage
  Traceback (most recent call last):
File "/usr/bin/hp-testpage", line 37, in 
  from base import device, utils, tui, module
File "/usr/share/hplip/base/device.py", line 38, in 
  from . import utils
File "/usr/share/hplip/base/utils.py", line 110, in 
  pexpect.EOF, # 0

  Because,  

  $ ll -d /usr/share/hplip/base/pexpect/
  drwx-- 3 root root 4096 Nov 15 22:40 /usr/share/hplip/base/pexpect/

  # chmod 755 /usr/share/hplip/base/pexpect/

  fixes the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: hplip-data 3.16.3+repack0-1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 20 14:53:53 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-23 (1396 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. Inspiron 530s
  PackageArchitecture: all
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=83a64b80-5a37-4659-b797-221b88ef41f8 ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.16
  dmi.board.name: 0RY007
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.16:bd12/12/2008:svnDellInc.:pnInspiron530s:pvr:rvnDellInc.:rn0RY007:rvr:cvnDellInc.:ct3:cvrOEM:
  dmi.product.name: Inspiron 530s
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1643361/+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 1798747] Re: Ticks in gdm do not show

This bug was fixed in the package gnome-shell - 3.30.1-2ubuntu2

---
gnome-shell (3.30.1-2ubuntu2) disco; urgency=medium

  [ Didier Roche ]
  * debian/patches/ubuntu/background_login.patch:
- match Yaru theme in the ubuntu session instead of our previous GDM
  background (LP: #1789356)
  * debian/patches/ubuntu/resolve_alternate_theme_path.patch:
- ensure we resolve finale theme file path to correctly load assets
  under gdm (LP: #1798747)

  [ Marco Trevisan (Treviño) ]
  * debian/patches/st-button-Ignore-pointer-emulated-touch-events.patch:
- Don't emit two click events on touch under X11 (LP: #1745888)

 -- Iain Lane   Wed, 07 Nov 2018 11:05:30 +

** Changed in: gnome-shell (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Ticks in gdm do not show

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Cosmic:
  In Progress

Bug description:
  [Impact]
  At the login screen (gdm) the a11y menu has a number of options, such as 
large text, screen reader etc. If you turn on screen reader you can then hover 
over the menu items and they will be read to you.

  If you hover over an option that is enabled, the screen reader will
  tell you, for example:

  Screen reader. TICKED

  The entry in the menu item should have a tick next to it.

  This is what happens using the default GNOME theme.

  [Test Case]
  1. Install new version from proposed
  2. Reboot your laptop
  3. Check the accessibility menu in the login screen (GDM) and ensure you have 
ticks near the label
  4. Login and check there is no regression.
  5. For bonus point, you can try GDM using vanilla gnome-shell theme by sudo 
update-alternatives --config gdm3.css + a reboot and GNOME Shell vanilla 
session (apt install gnome-session + select GNOME session on login screen)

  
  [Regression Potential]
  The new function exposed to gjs is calling realpath and is idempotent: it 
returns the filename given as a parameter on any error, or the realpath() 
result if there is any result, not changing the fundamental logic.
  If there was a regression, the Shell wouldn't even load.
  By checking the 5. point, we are checking we didn't impact gresources.

  
  From https://github.com/ubuntu/yaru/issues/917.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1798747/+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 1780672] Re: login screen "greyed out", no mouse or keyboard inputs

[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  login screen "greyed out", no mouse or keyboard inputs

Status in gdm3 package in Ubuntu:
  Expired

Bug description:
  Unable to log into 18.04. Worked for about a month, then suddenly
  stopped. Boot appeared normal until login screen. Login screen
  appeared to be "greyed out", mouse and keyboard did not work. System
  clock appeared ok.

  CTL-ALT-F2 did not open new terminal. CTL-ALT-F7 did not reset login
  screen or desktop.

  Changed boot process to verbose. No errors observed on startup.

  I've recovered a lot of Ubuntu machines, this problem is new to me.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.14
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  8 13:02:50 2018
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   LANGUAGE=en_US.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: grub-installer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780672/+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 1802429] Re: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: unable to clean up mess surrounding './usr/include/jerror.h' before installing another versio

2018-11-08 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: libjpeg-turbo (Ubuntu)
   Importance: Undecided => Low

** Changed in: libjpeg-turbo (Ubuntu)
   Status: New => Invalid

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

Title:
  package libjpeg-turbo8-dev (not installed) failed to install/upgrade:
  unable to clean up mess surrounding './usr/include/jerror.h' before
  installing another version: Read-only file system

Status in libjpeg-turbo package in Ubuntu:
  Invalid

Bug description:
  during installation of hp printer

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libjpeg-turbo8-dev (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  AptOrdering:
   libjpeg9:amd64: Install
   libjpeg-progs:amd64: Install
   libjpeg-turbo8-dev:amd64: Install
   libjpeg8-dev:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Nov  9 08:17:11 2018
  DuplicateSignature:
   package:libjpeg-turbo8-dev:(not installed)
   Unpacking libjpeg9:amd64 (1:9b-2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libjpeg9_1%3a9b-2_amd64.deb (--unpack):
unable to clean up mess surrounding 
'./usr/lib/x86_64-linux-gnu/libjpeg.so.9.2.0' before installing another 
version: Read-only file system
  ErrorMessage: unable to clean up mess surrounding './usr/include/jerror.h' 
before installing another version: Read-only file system
  InstallationDate: Installed on 2018-11-07 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: libjpeg-turbo
  Title: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: 
unable to clean up mess surrounding './usr/include/jerror.h' before installing 
another version: Read-only file system
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1802429/+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 1791289] Re: Shows duplicate xdg directories for snaps

[Expired for tracker (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Shows duplicate xdg directories for snaps

Status in gnome-shell package in Ubuntu:
  Expired
Status in tracker package in Ubuntu:
  Expired

Bug description:
  See attached screenshot. If I search for Downloads, I also get
  symlinks to ~/Downloads generated in ~/snap/spotify/16/Downloads, for
  example.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791289/+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 1791465] Re: Xorg freeze

[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Xorg freeze

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Whole system is locked up and the only fix is a hard reset

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  8 20:45:01 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Once a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Turks XT [Radeon HD 
6670/7670] [174b:e198]
  InstallationDate: Installed on 2018-08-18 (21 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0808
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T SE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0808:bd03/08/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TSE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1791465/+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 1802139] Re: Typing a long password in to the polkit dialog causes the dots to overflow the input field

Also, fix committed in mutter 3.28.4 already. Just waiting for a release
:)

https://gitlab.gnome.org/GNOME/mutter/commit/2ad5a39b

** Tags added: fixed-in-3.28.4

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

Title:
  Typing a long password in to the polkit dialog causes the dots to
  overflow the input field

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  On Bionic when I am prompted to enter my password via polkit I can
  type a lot of characters in to the input field, above 24 characters
  the dots hiding the actual characters overflows the input field.

  I can reproduced this by:

  Logging out of snapd (snap logout)
  snap refresh   (note, not sudo)
  polkit prompt appears
  type > 25 chars
  notice the overflow

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1802139/+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 1774587] Re: nautilus crashes in recent_thread_func -> is_file_valid_recursive -> g_local_file_query_info -> free(): invalid pointer

This bug was fixed in the package nautilus - 1:3.26.4-0ubuntu8

---
nautilus (1:3.26.4-0ubuntu8) disco; urgency=medium

  * d/p/0016-search-engine-add-a-recent-search-engine-listing-Gtk.patch:
- Don't start a new search thread until the one running is over
  (LP: #1774587)
  * d/p/0017-recent-add-function-to-update-manager-on-file-rename.patch:
- Do not try to update the position of a recent file if it didn't change
  (LP: #1760569)

 -- Marco Trevisan (Treviño)   Thu, 08 Nov 2018
02:32:03 -0600

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

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

Title:
  nautilus crashes in recent_thread_func -> is_file_valid_recursive ->
  g_local_file_query_info -> free(): invalid pointer

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
nautilus.  This problem was most recently seen with package version 
1:3.26.3-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  Similar crash in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1638389
  Trace at: https://bugzilla.redhat.com/attachment.cgi?id=1492907

  https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9
  https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45
  https://errors.ubuntu.com/problem/43301aeee406cdbd57ba7d571ff838f0340d72a2
  https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1
  https://errors.ubuntu.com/problem/7e550b34e134ed57f0684a8c554e3219191cd7f9

  Similar but related to this thread (so likely the same issue):
  https://errors.ubuntu.com/problem/b0ad24ee4008e11e2adf5d14b6b0463e14aa8637
  https://errors.ubuntu.com/problem/cec510782baf291622cd2bdd5a3761d27d587523
  https://errors.ubuntu.com/problem/a829a6947498ae1bc279781b820f2409238af3a0
  https://errors.ubuntu.com/problem/5ac15513eba57b72b1b09bafc448ffa1a7f3aa7f
  https://errors.ubuntu.com/problem/c3b2e8a30a1ccdd23e1155f0c0067a89dea5eb6a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774587/+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 1760569] Re: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved

This bug was fixed in the package nautilus - 1:3.26.4-0ubuntu8

---
nautilus (1:3.26.4-0ubuntu8) disco; urgency=medium

  * d/p/0016-search-engine-add-a-recent-search-engine-listing-Gtk.patch:
- Don't start a new search thread until the one running is over
  (LP: #1774587)
  * d/p/0017-recent-add-function-to-update-manager-on-file-rename.patch:
- Do not try to update the position of a recent file if it didn't change
  (LP: #1760569)

 -- Marco Trevisan (Treviño)   Thu, 08 Nov 2018
02:32:03 -0600

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

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

Title:
  Nautilus crashes in g_free -> g_bookmark_file_move_item ->
  gtk_recent_manager_move_item -> nautilus_recent_update_file_moved

Status in glib2.0 package in Ubuntu:
  In Progress
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Happens when there's a "rename" to a file to its same value, no known
  reproducer though.

  Upstream fix: https://gitlab.gnome.org/GNOME/glib/merge_requests/456

  https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45
  https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9

  ProblemType: CrashDistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AssertionMessage: munmap_chunk(): invalid pointer
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  2 09:04:45 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'223'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+117+77'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2018-03-31 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8Signal: 6SourcePackage: nautilus
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f1a46fcfb9a 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f1a46fd17a8 "munmap_chunk(): invalid 
pointer") at malloc.c:5350
   munmap_chunk (p=0x55f2e55b71f0) at malloc.c:2846
   __GI___libc_free (mem=0x55f2e55b7200) at malloc.c:3117
   g_bookmark_file_move_item () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus assert failure: munmap_chunk(): invalid pointer
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1760569/+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 1798091] Re: thumbnailer cannot create tempfiles (with apparmor denials)

This bug was fixed in the package evince - 3.30.2-1

---
evince (3.30.2-1) unstable; urgency=medium

  [ Jeremy Bicha ]
  * New upstream release

  [ Jamie Strandboge ]
  * debian/apparmor-profile: Update thumbnailer policy
for temporary file path with and without bubblewrap (LP: #1798091)
(Closes: #911161)

 -- Jeremy Bicha   Sat, 03 Nov 2018 17:30:50 -0400

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

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

Title:
  thumbnailer cannot create tempfiles (with apparmor denials)

Status in evince package in Ubuntu:
  Fix Released
Status in evince source package in Cosmic:
  Fix Committed
Status in evince source package in Disco:
  Fix Released
Status in evince package in Debian:
  Fix Released

Bug description:
  * Impact

  Nautilus fails to generate previews for pdf files

  * Test case

  Download/copy a pdf, open the directory in nautilus, a preview image
  should be displayed

  * Regression potential

  Check that there are no other apparmor denials and the thumbnailer
  works

  
  -

  While trying to create thumbnails in a directory from within nautilus,
  I got:

  [781429.784125] audit: type=1400 audit(1539694722.247:989): apparmor="DENIED" 
operation="mknod" profile="/usr/bin/evince-thumbnailer" 
name="/tmp/gnome-desktop-thumbnailer.png" pid=30937 comm="evince-thumbnai" 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
  [781429.940592] audit: type=1400 audit(1539694722.403:990): apparmor="DENIED" 
operation="mknod" profile="/usr/bin/evince-thumbnailer" 
name="/tmp/gnome-desktop-thumbnailer.png" pid=30941 comm="evince-thumbnai" 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
  [781430.314591] audit: type=1400 audit(1539694722.779:991): apparmor="DENIED" 
operation="mknod" profile="/usr/bin/evince-thumbnailer" 
name="/tmp/gnome-desktop-thumbnailer.png" pid=30945 comm="evince-thumbnai" 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
  [781431.283522] audit: type=1400 audit(1539694723.747:992): apparmor="DENIED" 
operation="mknod" profile="/usr/bin/evince-thumbnailer" 
name="/tmp/gnome-desktop-thumbnailer.png" pid=30949 comm="evince-thumbnai" 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
  [781431.518566] audit: type=1400 audit(1539694723.983:993): apparmor="DENIED" 
operation="mknod" profile="/usr/bin/evince-thumbnailer" 
name="/tmp/gnome-desktop-thumbnailer.png" pid=30953 comm="evince-thumbnai" 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evince 3.30.1-1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 16 14:59:00 2018
  InstallationDate: Installed on 2014-06-19 (1580 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to cosmic on 2018-10-07 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1798091/+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 1552792] Re: gnome software leaves dependencies installed

** Changed in: gnome-software (Ubuntu Bionic)
   Status: Triaged => Fix Committed

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

Title:
  gnome software leaves dependencies installed

Status in GNOME Software:
  Invalid
Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in packagekit package in Ubuntu:
  Fix Released
Status in gnome-software source package in Bionic:
  Fix Committed
Status in packagekit source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Released
Status in packagekit source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Installing an application them removing it leaves dependencies behind.

  [Test Case]
  1. Ensure that GNOME Sudoku is not installed:
  $ sudo apt remove gnome-sudoku libqqwing2v5
  2. Check if you have any packages that need autoremoval:
  $ sudo apt autoremove --no-act
  3. Open GNOME Software.
  4. Search for and install GNOME Sudoku (make sure to install the .deb, not 
the snap).
  5. Uninstall GNOME Sudoku.
  6. Check if you have any packages that need autoremoval:
  $ sudo apt autoremove --no-act

  Expected result:
  The packages in step 6 are the same as in step 2 (which might be none).

  Observed result:
  The packages in step 6 includes libqqwing2v5, which is a dependency of 
gnome-sudoku and not useful without the game installed.

  [Regression Potential]
  This requires a fix to PackageKit which used to autoremove all packages (too 
aggressive), not just the ones related to the current transaction. A bug in the 
code could cause more packages to be removed than is suitable. GNOME Software 
previously didn't use this autoremove functionality, so by enabling it we could 
trigger a problem in either the existing code or the new fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1552792/+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 1785240] Re: Cancelling snapd authorization triggers error notification

** Changed in: gnome-software (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: gnome-software (Ubuntu Bionic)
 Assignee: Andrea Azzarone (azzar1) => Robert Ancell (robert-ancell)

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

Title:
  Cancelling snapd authorization triggers error notification

Status in gnome-software package in Ubuntu:
  Fix Released
Status in snapd-glib package in Ubuntu:
  Fix Released
Status in gnome-software source package in Bionic:
  Fix Committed
Status in snapd-glib source package in Bionic:
  Fix Released
Status in gnome-software source package in Cosmic:
  Fix Released
Status in snapd-glib source package in Cosmic:
  Fix Released

Bug description:
  To reproduce:

  1. Open gnome-software
  2. Try to install a snap application
  3. Cancel the polkit authorization

  Expected results:
  Nothing happens

  Actual results:
  An error notification is shown as per attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1785240/+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 1802429] Re: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: unable to clean up mess surrounding './usr/include/jerror.h' before installing another versio

2018-11-08 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libjpeg-turbo8-dev (not installed) failed to install/upgrade:
  unable to clean up mess surrounding './usr/include/jerror.h' before
  installing another version: Read-only file system

Status in libjpeg-turbo package in Ubuntu:
  New

Bug description:
  during installation of hp printer

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libjpeg-turbo8-dev (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  AptOrdering:
   libjpeg9:amd64: Install
   libjpeg-progs:amd64: Install
   libjpeg-turbo8-dev:amd64: Install
   libjpeg8-dev:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Nov  9 08:17:11 2018
  DuplicateSignature:
   package:libjpeg-turbo8-dev:(not installed)
   Unpacking libjpeg9:amd64 (1:9b-2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libjpeg9_1%3a9b-2_amd64.deb (--unpack):
unable to clean up mess surrounding 
'./usr/lib/x86_64-linux-gnu/libjpeg.so.9.2.0' before installing another 
version: Read-only file system
  ErrorMessage: unable to clean up mess surrounding './usr/include/jerror.h' 
before installing another version: Read-only file system
  InstallationDate: Installed on 2018-11-07 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: libjpeg-turbo
  Title: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: 
unable to clean up mess surrounding './usr/include/jerror.h' before installing 
another version: Read-only file system
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1802429/+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 1802429] [NEW] package libjpeg-turbo8-dev (not installed) failed to install/upgrade: unable to clean up mess surrounding './usr/include/jerror.h' before installing another vers

2018-11-08 Thread Arup Sinha

Public bug reported:

during installation of hp printer

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libjpeg-turbo8-dev (not installed)
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
AptOrdering:
 libjpeg9:amd64: Install
 libjpeg-progs:amd64: Install
 libjpeg-turbo8-dev:amd64: Install
 libjpeg8-dev:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Nov  9 08:17:11 2018
DuplicateSignature:
 package:libjpeg-turbo8-dev:(not installed)
 Unpacking libjpeg9:amd64 (1:9b-2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libjpeg9_1%3a9b-2_amd64.deb (--unpack):
  unable to clean up mess surrounding 
'./usr/lib/x86_64-linux-gnu/libjpeg.so.9.2.0' before installing another 
version: Read-only file system
ErrorMessage: unable to clean up mess surrounding './usr/include/jerror.h' 
before installing another version: Read-only file system
InstallationDate: Installed on 2018-11-07 (1 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: libjpeg-turbo
Title: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: 
unable to clean up mess surrounding './usr/include/jerror.h' before installing 
another version: Read-only file system
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libjpeg-turbo (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package libjpeg-turbo8-dev (not installed) failed to install/upgrade:
  unable to clean up mess surrounding './usr/include/jerror.h' before
  installing another version: Read-only file system

Status in libjpeg-turbo package in Ubuntu:
  New

Bug description:
  during installation of hp printer

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libjpeg-turbo8-dev (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  AptOrdering:
   libjpeg9:amd64: Install
   libjpeg-progs:amd64: Install
   libjpeg-turbo8-dev:amd64: Install
   libjpeg8-dev:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Nov  9 08:17:11 2018
  DuplicateSignature:
   package:libjpeg-turbo8-dev:(not installed)
   Unpacking libjpeg9:amd64 (1:9b-2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libjpeg9_1%3a9b-2_amd64.deb (--unpack):
unable to clean up mess surrounding 
'./usr/lib/x86_64-linux-gnu/libjpeg.so.9.2.0' before installing another 
version: Read-only file system
  ErrorMessage: unable to clean up mess surrounding './usr/include/jerror.h' 
before installing another version: Read-only file system
  InstallationDate: Installed on 2018-11-07 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: libjpeg-turbo
  Title: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: 
unable to clean up mess surrounding './usr/include/jerror.h' before installing 
another version: Read-only file system
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1802429/+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 1802349] Re: video is not playing in the default player and ear phone sound is not working

Can you please:

1. Take a photo/screenshot of the problem; and

2. Run 'lspci -k' and send us the output?


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

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

Title:
  video is not playing in the default player and ear phone sound is not
  working

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  the video is not playing in the default video player and if I plug my
  earphone, the sound is not coming

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  8 22:57:31 2018
  InstallationDate: Installed on 2018-05-21 (170 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1802349/+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 1802366] Re: i dont know

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!


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

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

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

Title:
  i dont know

Status in Ubuntu:
  Incomplete

Bug description:
  + i don't speak English+i am not informatics just a user

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  410.73  Sat Oct 20 22:12:33 
CDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Nov  8 19:13:59 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 410.73, 4.15.0-39-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-33-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-39-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GM204M [GeForce GTX 970M] [1043:22da]
  InstallationDate: Installed on 2017-12-29 (313 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 
(20170926)
  MachineType: ASUSTeK COMPUTER INC. G751JT
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=3b41e99c-b074-4029-826b-39ad3587 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G751JT.202
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G751JT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG751JT.202:bd09/10/2014:svnASUSTeKCOMPUTERINC.:pnG751JT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG751JT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G751JT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Nov  8 15:34:32 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1802366/+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 1802139] Re: Typing a long password in to the polkit dialog causes the dots to overflow the input field

Already fixed in cosmic with this fix in mutter 3.30.0:

https://gitlab.gnome.org/GNOME/mutter/commit/b8340f1355b


** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)

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

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Tags added: bionic

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

Title:
  Typing a long password in to the polkit dialog causes the dots to
  overflow the input field

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  On Bionic when I am prompted to enter my password via polkit I can
  type a lot of characters in to the input field, above 24 characters
  the dots hiding the actual characters overflows the input field.

  I can reproduced this by:

  Logging out of snapd (snap logout)
  snap refresh   (note, not sudo)
  polkit prompt appears
  type > 25 chars
  notice the overflow

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1802139/+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 1802243] Re: ubuntu 18.10 boots to black screen with blinking cursor

Please run this command to send us more information about the machine:

  apport-collect 1802243

** Tags added: cosmic

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

Title:
  ubuntu 18.10 boots to black screen with blinking cursor

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Software update center prompted me to reboot pc after installing
  updates.. After rebooting, it just shows a black screen with a
  blinking cursor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1802243/+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 1802402] Re: [UX430UNR, Realtek ALC294, Black Headphone Out, Left] No sound

Please run this command:

  dpkg -l > allpackages.txt

and then send us the resulting file 'allpackages.txt'.

** Package changed: alsa-driver (Ubuntu) => pulseaudio (Ubuntu)

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

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

Title:
  [UX430UNR, Realtek ALC294, Black Headphone Out, Left] No sound

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I expected speaker and headphones to work.
  I found speaker silent and headphones slight popping sound only.
  But HDMI audio works, also speaker and headphones work on my dualbooted 
windows 10.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jita   1798 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  8 22:45:36 2018
  InstallationDate: Installed on 2018-11-07 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jita   1798 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [UX430UNR, Realtek ALC294, Black Headphone Out, Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/13/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UNR.T157
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UNR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Tarasovic Jiri
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX430UNR.T157:bd03/13/2018:svnASUSTeKCOMPUTERINC.:pnUX430UNR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UNR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX430UNR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-11-08T22:34:00.520280

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1802402/+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 1723181] Re: shotwell crashed with SIGSEGV in g_menu_model_get_n_items()

This bug was fixed in the package shotwell - 0.30.1-0ubuntu4

---
shotwell (0.30.1-0ubuntu4) disco; urgency=medium

  * debian/patches/git_notification_segfault.patch:
- direct: Fix crash when dismissing modifications (lp: #1723181)

 -- Sebastien Bacher   Wed, 07 Nov 2018 15:39:16
+0100

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

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

Title:
  shotwell crashed with SIGSEGV in g_menu_model_get_n_items()

Status in shotwell package in Ubuntu:
  Fix Released
Status in shotwell package in Fedora:
  Confirmed

Bug description:
  * Impact

  Shotwell hits a segfault in some situations

  * Test case

  There is no specific steps described to lead to the issue. The
  upstream commit "Fix crash when dismissing modifications".

  The issue is being reported to e.u.c though at least under those ids
  https://errors.ubuntu.com/problem/9dfc154a07b6ec76929e2c3c74419ac85a1de015
  https://errors.ubuntu.com/problem/44455d848d6d64d4838e9a5af557eb0b092bd669

  If the fix is right the new version should get no report

  * Regression potential

  Check that the notifications still work as they should and that there
  is no other visible regressions

  

  It happened during opening and closing some raw photos.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: shotwell 0.26.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 18:27:38 2017
  ExecutablePath: /usr/bin/shotwell
  InstallationDate: Installed on 2017-10-06 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: shotwell /media/username/podatki\ in\ backup/SLIKE\ iz\ MY\ 
PICTURES\ 18GB/PIKNIK\ 3.VS/IMG_3803.CR2
  SegvAnalysis:
   Segfault happened at: 0x7fa291b2e510 : mov
(%rdi),%rax
   PC (0x7fa291b2e510) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: shotwell
  StacktraceTop:
   g_menu_model_get_n_items () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: shotwell crashed with SIGSEGV in g_menu_model_get_n_items()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1723181/+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 1801602] Re: Gnome 3 fullscreen doesn't work for some applications

Sounds like equal blame on the application, window manager (mutter) and
the user :)

* Application: Is 640x480 still so may be to blame for ignoring window
resize requests.

* Window manager: May be ignoring the "Fullscreen" state on the
window(?). But not sure, since it works with the above workaround.

* User: Added custom mode "960x540" which seems to be confusing the
system.


** Summary changed:

- Gnome 3 fullscreen doesn't work for some applications
+ Gnome 3 fullscreen doesn't work for some applications when a custom display 
mode (960x540) is active

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

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Low

** Changed in: mutter (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  Gnome 3 fullscreen doesn't work for some applications when a custom
  display mode (960x540) is active

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Using Gnome 3 or Ubuntu session (default in 18.04) when you try to run
  some game in fullscreen mode  instead it opens at top left small
  window. This happens for example for Way to Go! Steam game and perhaps
  any SDL 1 game. It's easy to reproduce, install a game using SDL 1
  library for example abe (apt install abe) and try to run it. There are
  two kinds of effect, the abe and perhaps other games from Ubuntu
  repository fails to run properly fullscreen only on first use after
  login. On second and further run they launch properly on fullscreen.
  The Steam game (Way to Go !) fails to run fullscreen each time.
  Sometimes you see only part of the game screen at top left window and
  you even can't operate it, sometimes whole screen is shown. When you
  manage to reach game settings switching fullscreen on and off few
  times makes the fullscreen run properly. The problem doesn't exist for
  example using Unity or Windowmaker sessions. It exists using any Gnome
  3 Xorg sessions, even the classic one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1801602/+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 1789925] Re: Link to Ubuntu Report legal notice points at the wrong page

This bug was fixed in the package gnome-initial-setup - 3.30.0-1ubuntu4

---
gnome-initial-setup (3.30.0-1ubuntu4) disco; urgency=medium

  * debian/patches/0001-Add-Ubuntu-mode-with-special-pages.patch:
- update the "legal notice" URL to use the one which is specific about
  ubuntu report (lp: #1789925)

 -- Sebastien Bacher   Wed, 31 Oct 2018 15:41:49
+0100

** Changed in: gnome-initial-setup (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Link to Ubuntu Report legal notice points at the wrong page

Status in gnome-initial-setup package in Ubuntu:
  Fix Released
Status in gnome-initial-setup source package in Bionic:
  Fix Committed
Status in gnome-initial-setup source package in Cosmic:
  Fix Committed

Bug description:
  * Impact

  The legal notice URL is not pointing to the right page of the website

  * Test case

  - rm ~/.config/gnome-initial-setup-done
  - gnome-initial-setup
  - click on the 'legal notice' URL from the livepatch page

  -> it should open https://www.ubuntu.com/legal/terms-and-policies
  /systems-information-notice

  * Regression potential

  It's just an URL change so just check that this reference is working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1789925/+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 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic

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

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

Title:
  Bluetooth headset HSP/HFP mode not working in Bionic

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  There is a previous bug with almost the same title, but for Xenial
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I
  have had this issue in Artful, and when commented on the old bug, I
  was asked to raise a new one instead. I waited to see if Bionic fixed
  it for me, but it does not seem to work still. So!

  Steps to reproduce:
  1. enable bluetooth on computer and switch on the headset.
  2. pair and connect the headset
  3. go to settings to switch headset to HSP/HFP mode to enable mic
  4. save and close window.

  Expected behaviour:
  1. mic should be enabled and headset should be usable to attend calls on 
laptop.

  Behaviour in error:
  1. Headset profile switches back to A2DP and mic is not enabled.

  I am using a generic bluetooth headset on a fresh updated Kubuntu
  18.04 bionic with plasma DE.

  Software versions:
  Kernel: 4.15.0-20-generic
  Bluez version: 5.48-0ubuntu3
  pulseaudio: 1:11.1-1ubuntu7
  pulseaudio-module-bluetooth: 1:11.1-1ubuntu7

  
  Additional information:
  Running "pacmd list-cards" says that HSF/HFP is 'not available' on the 
headset:

  Output from Headset section:
  profiles:
  a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, 
available: unknown)
  headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, 
available: no)
  off: Off (priority 0, available: yes)
  active profile: 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+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 1014264] Re: totem fails to recognize mkv-header crop values

Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: totem (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  totem fails to recognize mkv-header crop values

Status in Totem:
  Expired
Status in totem package in Ubuntu:
  Won't Fix

Bug description:
  MKV-file headers may contains values to be used for players affecting
  top-, left-, right-, and bottom-pixels cropping. Totem does not
  currently recognize those header values, and just ignores them.

  This can be demonstrated using the mkvmerge GUI program and its header
  editor to fiddle with such values, and them running the resulting
  files through totem. Another player than totem (VLC) was tried, which
  recognized those values, and therefore cropped the video upon playing
  to remove the annoying border flickering that was experienced in that
  given file, without the need for the stream to be reencoded, and
  either suffering from a deterioration in quality, or becoming huge
  through lossless reencoding. (Consider this as an argument for the
  pertinence of this bug.)

  This bug can be experienced under Precise, using the as-of-current
  latest build of totem.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: totem 3.0.1-0ubuntu21
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic-pae 3.2.18
  Uname: Linux 3.2.0-25-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
  Date: Sun Jun 17 06:41:52 2012
  ExecutablePath: /usr/bin/totem
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/totem/+bug/1014264/+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 200846] Re: Totem fails to jump to times in video

Thank you for reporting this bug to Ubuntu.
Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: totem (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  Totem fails to jump to times in video

Status in Totem:
  Expired
Status in totem package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: totem

  When I watch a movie, doesn't matter what format. If I try to jump to
  a time with the bar below the video, it will jump to a time past the
  end of the video and freeze. The program does not crash but it fails
  to work and has to be closed. Here is some further information:

  Dist: Hardy Alpha 6
  Package: Totem
  Version: 2.21.95
  Expectation: Go to the time displayed while dragging
  What did happen: It jumps way past, in this case the play time indicates 
(199:09:34 / 1:58:32)
  Other: I am using Compiz on an ATI X1400 card with the 8.3 fglrx driver

  Feel free to contact me with any more questions

  ProblemType: Bug
  Architecture: i386
  Date: Mon Mar 10 21:13:12 2008
  DistroRelease: Ubuntu 8.04
  ExecutablePath: /usr/bin/totem-gstreamer
  NonfreeKernelModules: fglrx
  Package: totem-gstreamer 2.21.95-0ubuntu1
  PackageArchitecture: i386
  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: totem
  Uname: Linux 2.6.24-12-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/totem/+bug/200846/+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 1721248] Re: Totem could not get a screenshot of the video when using gstreamer1.0-vaapi plugin on supported videos

** Description changed:

+ https://gitlab.gnome.org/GNOME/mutter/issues/146
+ 
+ ---
+ 
  I try to get a screenshot from my video and totem shows a message saying
  it could not get a screenshot of the video and suggesting to open a bug.
  See attached screenshot.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.25.90.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 14:54:16 2017
  InstallationDate: Installed on 2017-09-29 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

** Tags removed: artful
** Tags added: disco

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

Title:
  Totem could not get a screenshot of the video when using
  gstreamer1.0-vaapi plugin on supported videos

Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/146

  ---

  I try to get a screenshot from my video and totem shows a message
  saying it could not get a screenshot of the video and suggesting to
  open a bug. See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.25.90.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 14:54:16 2017
  InstallationDate: Installed on 2017-09-29 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1721248/+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 385970] Re: Doesn't load subtitles from .VOB

Thank you for reporting this bug to Ubuntu.
Ubuntu 9.04 (jaunty) reached end-of-life on October 23, 2010.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: totem (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  Doesn't load subtitles from .VOB

Status in Totem:
  Expired
Status in totem package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: totem

  Dear friends,

  I double click the .VOB file and Totem plays it. It doesn't show that
  there are any subtitles available when in fact VLC does.

  Selecting the .VOB file as the subtitles file manually also doesn't
  help it.

  Many blessings.

  There's a bounty on this bug:
  http://www.fossfactory.org/project/p188

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/bin/totem-gstreamer
  Package: totem-gstreamer 2.26.1-0ubuntu5
  ProcEnviron:
   LANG=he_IL.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  Uname: Linux 2.6.28-11-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/totem/+bug/385970/+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 413018] Re: Cannot disable subtitles in mkv video file

Thank you for reporting this bug to Ubuntu.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: totem (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  Cannot disable subtitles in mkv video file

Status in Totem:
  Expired
Status in totem package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: totem

  In Karmic.

  Using vobsub subtitles in an mkv video file, totem always displays
  them, and doesn't give the option to turn them off.  The "Subtitles"
  right-click submenu shows only "Empty", which is ghosted.

  Obviously, it should give the option to turn these subtitles off.

To manage notifications about this bug go to:
https://bugs.launchpad.net/totem/+bug/413018/+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 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

** Description changed:

  Monitor is set to 144hz, but on Wayland it visually fails to go above
- 60Hz.  On XOrg it  runs higher and feels much smoother.  I have
- confirmed the monitor is running at 144Hz during the Wayland session,
- and that is also the setting in the Settings control panel.
+ 60Hz. I have confirmed the monitor is running at 144Hz during the
+ Wayland session, and that is also the setting in the Settings control
+ panel.
  
  Using the additional NVidia drivers installed using the Ubuntu software
  control panel.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libwayland-bin (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 08:43:29 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
-  NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
-Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 
1070] [1462:3301]
+  NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
+    Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 
1070] [1462:3301]
  InstallationDate: Installed on 2018-03-30 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed 
root=UUID=4f8fe8e2-8445-4034-bae3-dc8afb789c64 ro quiet splash vt.handoff=7
  SourcePackage: wayland
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0610
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-P
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0610:bd01/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

Title:
  144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

Status in Mutter:
  Confirmed
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Monitor is set to 144hz, but on Wayland it visually fails to go above
  60Hz. I have confirmed the monitor is running at 144Hz during the
  Wayland session, and that is also the setting in the Settings control
  panel.

  Using the additional NVidia drivers installed using the Ubuntu
  software control panel.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libwayland-bin (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 08:43:29 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 
1070] [1462:3301]
  InstallationDate: Installed on 2018-03-30 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed 
root=UUID=4f8fe8e2-8445-4034-bae3-dc8afb789c64 ro quiet splash vt.handoff=7
  SourcePackage: wayland
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0610
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-P

[Desktop-packages] [Bug 1552792] Re: gnome software leaves dependencies installed

** Changed in: packagekit (Ubuntu Bionic)
   Status: Triaged => Fix Committed

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

Title:
  gnome software leaves dependencies installed

Status in GNOME Software:
  Invalid
Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in packagekit package in Ubuntu:
  Fix Released
Status in gnome-software source package in Bionic:
  Triaged
Status in packagekit source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Released
Status in packagekit source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Installing an application them removing it leaves dependencies behind.

  [Test Case]
  1. Ensure that GNOME Sudoku is not installed:
  $ sudo apt remove gnome-sudoku libqqwing2v5
  2. Check if you have any packages that need autoremoval:
  $ sudo apt autoremove --no-act
  3. Open GNOME Software.
  4. Search for and install GNOME Sudoku (make sure to install the .deb, not 
the snap).
  5. Uninstall GNOME Sudoku.
  6. Check if you have any packages that need autoremoval:
  $ sudo apt autoremove --no-act

  Expected result:
  The packages in step 6 are the same as in step 2 (which might be none).

  Observed result:
  The packages in step 6 includes libqqwing2v5, which is a dependency of 
gnome-sudoku and not useful without the game installed.

  [Regression Potential]
  This requires a fix to PackageKit which used to autoremove all packages (too 
aggressive), not just the ones related to the current transaction. A bug in the 
code could cause more packages to be removed than is suitable. GNOME Software 
previously didn't use this autoremove functionality, so by enabling it we could 
trigger a problem in either the existing code or the new fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1552792/+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 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

When this bug was first reported in 17.10 it was a Wayland-only bug and the fix 
for that is awaiting review:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/171

However since 18.04, a patch was introduced to Ubuntu/Debian that seems
to be affecting Xorg sessions now too. So I think that also needs
removing to fix this bug: clutter-Smooth-out-master-clock-to-smooth-
visuals.patch

** Summary changed:

- 144Hz/120Hz monitor but Wayland sessions seem to cap rendering at 60FPS
+ 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

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

Title:
  144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

Status in Mutter:
  Confirmed
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Monitor is set to 144hz, but on Wayland it visually fails to go above
  60Hz. I have confirmed the monitor is running at 144Hz during the
  Wayland session, and that is also the setting in the Settings control
  panel.

  Using the additional NVidia drivers installed using the Ubuntu
  software control panel.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libwayland-bin (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 08:43:29 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 
1070] [1462:3301]
  InstallationDate: Installed on 2018-03-30 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed 
root=UUID=4f8fe8e2-8445-4034-bae3-dc8afb789c64 ro quiet splash vt.handoff=7
  SourcePackage: wayland
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0610
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-P
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0610:bd01/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1763892/+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 1767264] Re: Window manager refresh rate is different from monitor refresh rate

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1763892, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1763892
   144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

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

Title:
  Window manager refresh rate is different from monitor refresh rate

Status in Ubuntu Budgie:
  New
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Budgie 18.04
  budgie-desktop 10.4

  The refresh rate of the window manager in Ubuntu Budgie appears to be
  locked at 60hz regardless of the actual monitor refresh rate (144hz in
  my case).

  xrandr reports the proper refresh rate glxgears runs synced to the
  correct refresh rate but moving windows and animations in the desktop
  do not.

  Unfortunately I have only been able to test this using an nVidia GPU,
  but the problem happens with both nouveau and proprietary drivers.

  This issue seems limited specifically to Ubuntu Budgie, and does not
  exist when using Budgie Desktop in Solus Linux or Arch which is why
  I'm reporting it here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1767264/+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 1782399] Re: Specified monitor refresh rate is applied to mouse cursor only and not the applications' windows on 18.04 with Nouveau or NVIDIA's driver from Ubuntu's repo

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1763892, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1763892
   144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

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

Title:
  Specified monitor refresh rate is applied to mouse cursor only and not
  the applications' windows on 18.04 with Nouveau or NVIDIA's driver
  from Ubuntu's repo

Status in mutter package in Ubuntu:
  New

Bug description:
  I suspect this to be a bug related to mutter, but I'm not sure.

  On Ubuntu 18.04 using either Nouveau or NVIDIA's driver (from Ubuntu's
  "Additional Drivers" utility), when I select and apply a higher
  available refresh rate for my monitor (e.g: 240hz), the change is only
  applied to mouse movements, whereas if I drag applications' windows
  around I can clearly see their movement is still at the default 60hz.
  Linux Mint 19 with either the Cinnamon or MATE DE does *not* show this
  issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1782399/+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 1754864] Re: Flatpak related refs are not installed when using GNOME Software on Ubuntu 18.04

I've re-uploaded the SRU with these changes removed. If someone can re-
propose fixed patches and/or additional patches to resolve this then we
can consider it for another SRU.

** Changed in: gnome-software (Ubuntu Bionic)
   Status: Fix Committed => Triaged

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

Title:
  Flatpak related refs are not installed when using GNOME Software on
  Ubuntu 18.04

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Bionic:
  Triaged

Bug description:
  When installing a Flatpak application that depends on some runtimes
  and they depend on some additional runtime extensions (related refs)
  using GNOME Software on Ubuntu 18.04, the runtime extensions are not
  installed. They are installed if you run "flatpak update" from
  Terminal after the installation. This issue should be already fixed in
  GNOME Software upstream so I believe that this is a downstream Ubuntu
  issue. Please, fix this.

  Steps to Reproduce:
  1. Use the latest, fully updated Ubuntu 18.04 image.
  2. Install "flatpak" and "gnome-software-plugin-flatpak" packages.
  3. Restart the system.
  4. Download and add the Flathub repo file: 
https://dl.flathub.org/repo/flathub.flatpakrepo
  5. Search and install the "GNOME Web" Flatpak package using GNOME Software.
  6. Run the installed "Web" application.

  Actual results:
  GNOME Web is started with the default (Adwaita) theme (and without the 
correct locale if you use non-English system).

  Expected results:
  GNOME Web is started with the correct (Ubuntu) theme (and with the correct 
locale if you use non-English system).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1754864/+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 1792893] Re: Update to 3.7.0

2018-11-08 Thread Jeremy Bicha

This bug was fixed in the package liblouis - 3.7.0-1

---
liblouis (3.7.0-1) unstable; urgency=medium

  * New upstream release.
- debian/patches/automake-1.16: upstream.
- debian/patches/cve-2018-12085: upstream.
- debian/patches/da-dk: upstream.

 -- Samuel Thibault   Sat, 15 Sep 2018 10:11:03
+0200

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

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

Title:
  Update to 3.7.0

Status in liblouis package in Ubuntu:
  Fix Released

Bug description:
  Debian updated but the NEWS suggest that update would require a ffe

  "* Noteworthy changes in release 3.7.0 (2018-09-03)
  This release implements major improvements for back-translation thanks
  to concerted efforts by Bue Vester-Andersen, Bert Frees, Timothy Lee
  and others. In particular the input/output positions are now correct
  also for back-translation. There are new and improved Chinese Braille
  tables and some long awaited improvements to UEB. The release also has
  some code cleanups and documentation improvements."

  I'm unsure how to properly test those changes so unless someone steps
  up and request a ffe with testing steps then it's for next cycle

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/liblouis/+bug/1792893/+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 1797224] Re: Stay on 2.0 for cosmic, update next cycle

2018-11-08 Thread Jeremy Bicha

This is blocked by LP: #1793550

** Changed in: tracker (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  Stay on 2.0 for cosmic, update next cycle

Status in tracker package in Ubuntu:
  Fix Committed

Bug description:
  The new version requires the MIR situation to be sorted out

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1797224/+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 1792360] Re: Update to 0.18.0

2018-11-08 Thread Jeremy Bicha

This bug was fixed in the package spice-vdagent - 0.18.0-1

---
spice-vdagent (0.18.0-1) unstable; urgency=medium

  * Team upload.
  [ Laurent Bigonville ]
  * debian/watch: Update the URL
  * New upstream version 0.18.0 (Closes: #905771)
- Quote the save directory before passing to shell (Closes: #883238
  CVE-2017-15108)
- Drop the patches merged upstream
- debian/patches/systemd_service_default_file.patch: Refreshed
- debian/control: Bump the build-dependencies
  * debian/control: Build-depend against udev
  * debian/control: Drop dh-systemd, not needed with debhelper >= 10
  * debian/control: Bump Standards-Version to 4.2.1 (no further changes)
  * debian/control: Update Vcs- fields to the new URL
  * Enable GTK support, the X11 backend is deprecated
  * debian/rules: Reduce the number of runtime dependencies
  * debian/control: Fix typos in the Description.
Thanks to Ludovic Rousseau  (Closes: #874678)
  * debian/rules: Use dh_auto_install instead of calling make directly
  * debian/rules: Use dh_missing --list-missing instead of dh_install

  [ Helmut Grohne ]
  * Fix FTCBFS: Let dh_auto_configure pass --host to ./configure.
(Closes: #894116)

 -- Laurent Bigonville   Wed, 03 Oct 2018 01:22:06
+0200

** Changed in: spice-vdagent (Ubuntu)
   Status: Triaged => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15108

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

Title:
  Update to 0.18.0

Status in spice-vdagent package in Ubuntu:
  Fix Released
Status in spice-vdagent package in Debian:
  New

Bug description:
  The new version is not in Debian yet and includes features (new gtk
  backend, systemd socket activation, ...), marked as blocked by
  feature-freeze

  Update request in Debian https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=905771

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1792360/+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 1788235] Re: lirc broken on 18.04

2018-11-08 Thread xekon

I actually have lirc 0.10.0-2 working again:

I actually had lirc_0.10.0-2 installed and working (and it still does on
my other system)

but for some reason after dist-upgrade and a reboot it was broken.

I followed the workaround listed 0.9, it worked.
I then unmarked the package as held and dist-upgraded again to see if it would 
work again with 0.10.0 (nope)

I then tried the workaround to 0.9 again! this time nothing worked.
I then did:

sudo apt purge ir-keytable lirc
sudo apt-get install -y lirc lirc-compat-remotes
sudo dpkg-reconfigure lirc
sudo irw

and now my remote is back to working with lirc_0.10.0-2

If I narrow down the exact cause I will post back, its very odd for
sure, but for the moment I am working again with lirc_0.10.0-2

with lirc_0.10.0-2 irw shows output like this:

8001006c 00 KEY_DOWN devinput-32
80010067 00 KEY_UP devinput-32
8001006c 00 KEY_DOWN devinput-32
80010160 00 KEY_OK devinput-32
800100ae 00 KEY_EXIT devinput-32

under lirc 0.9 for the few minutes I tried the 0.9 workaround irw showed
like this:

00037ff07bde 00 KEY_RIGHT mceusb
00037ff07be6 00 KEY_STOP mceusb
00037ff07be6 01 KEY_STOP mceusb
00037ff07be9 00 KEY_PLAY mceusb
00037ff07be9 01 KEY_PLAY mceusb
00037ff07be7 00 KEY_PAUSE mceusb

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

Title:
  lirc broken on 18.04

Status in lirc package in Ubuntu:
  Confirmed

Bug description:
  Lirc 0.10.0-2 is never configured after installation. Manually running
  "dpkg-reconfigure lirc " also does not do anything. I also noticed
  that /usr/share/lirc/remotes is empty, which is where I had my config
  file for Ubuntu 16.04.

  This was an upgrade install from 16.04.
  Searching the web indicates others have this problem. Some have reverted to 
the lirc from 16.04. Others recommend using pip3 to install lirc 0.10.10, but I 
have been unsuccessful so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/+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 1788235] Re: lirc broken on 18.04

2018-11-08 Thread xekon

I just wanted to report that initially I was using Ubuntu 18.04 and the
lirc from the repository worked, appears to be:

apt-cache show lirc
Package: lirc   


Architecture: amd64 


Version: 0.10.0-2

Thats on my system where it still works.

However a few days ago I updated another 18.04 system that had a working
lirc, and it just completely stopped working after sudo apt-get update
&& sudo apt-get dist-upgrade

sudo irw (which was working perfectly fine) now shows:

Cannot connect to socket /var/run/lirc/lircd: No such file or directory

I noticed my arrow keys on the remote controller worked, but none of the
other buttons did, and the only thing that changed was doing the dist-
upgrade and rebooting. That caused one of my perfectly working system to
quit working.

So I followed this workaround:
https://twosortoftechguys.wordpress.com/2018/07/24/make-lirc-work-in-
ubuntu-18-04/

It does indeed get me back to working.

My other system that is still using 0.10.0-2 will likely break next time
I update it. I will have to use the workaround on it next im sure, will
hold off a few days in case I think of anything else to investigate on
the system prior to updating.

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

Title:
  lirc broken on 18.04

Status in lirc package in Ubuntu:
  Confirmed

Bug description:
  Lirc 0.10.0-2 is never configured after installation. Manually running
  "dpkg-reconfigure lirc " also does not do anything. I also noticed
  that /usr/share/lirc/remotes is empty, which is where I had my config
  file for Ubuntu 16.04.

  This was an upgrade install from 16.04.
  Searching the web indicates others have this problem. Some have reverted to 
the lirc from 16.04. Others recommend using pip3 to install lirc 0.10.10, but I 
have been unsuccessful so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2018-11-08 Thread Krzysztof Janowicz

@Andrew, @Alberto: Looks like many Thinkpad X1 Extreme users are
reporting the same issue where prime-select seems to work but does not
power of the nvidia card nor shows up in nvidia-settings. I followed the
instructions the same way Andrew did and got the same 'not found'
message. I assumed the packages are in updates by now and we should all
have them anyway. Apt tells me that 390.77-0ubuntu0.18.04.1 is the
newest version. Am I missing something? I have the same issue as I had
before (NVIDIA GTX 1050 TI). Thanks for your help.

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)

2018-11-08 Thread Treviño

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Login screen never appears on early generation Intel GPUs (Core2 and
  Atom etc)

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Committed
Status in mutter source package in Cosmic:
  Fix Released

Bug description:
  [ Impact ]

  In some early intel GPUs gdm can't start in wayland mode, and so
  gnome-shell

  [ Test case ]

  - Start the pc or logout/end session
  - Try to login with the "Ubuntu on Wayland" session
  - Ubuntu should start

  [ Regression potential ]

  Possible false positive on wayland support check on some cards

  
  ---

  
  https://gitlab.gnome.org/GNOME/mutter/issues/127

  ---

  Wayland sessions (including the login screen itself) don't start up on
  older Intel GPUs.

  ---

  Workaround:

  Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line:
  #WaylandEnable=false

  ---

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  Upgraded from 17.04 today.

  Steps to reproduce:

  - Start the PC or log out/end session in case it's running with an Xorg 
desktop already.
  - Attempt to log in, using 'Ubuntu'

  Expected to happen:

  Desktop appears.

  Actually happening:

  5 seconds of black screen, then the login screen appears again.

  Partial diagnosis:

  - Logging in using 'Ubuntu on Xorg' works fine and as expected.

  - Extracted a syslog of such a failed attempt, see attached file.
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOMEDisplayManager: gdm3DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-05-04 (539 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: gnome-shell 3.26.1-0ubuntu5
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags: artful package-from-proposed third-party-packages
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/+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 1802349] Re: video is not playing in the default player and ear phone sound is not working

2018-11-08 Thread Alex Murray

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  video is not playing in the default player and ear phone sound is not
  working

Status in totem package in Ubuntu:
  New

Bug description:
  the video is not playing in the default video player and if I plug my
  earphone, the sound is not coming

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  8 22:57:31 2018
  InstallationDate: Installed on 2018-05-21 (170 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1802349/+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 1801804] Re: Nautilus crashes in nautilus_query_matches_string recent_thread_func

2018-11-08 Thread Treviño

I've the feeling this is also related to lp:1774587

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

Title:
  Nautilus crashes in nautilus_query_matches_string recent_thread_func

Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
nautilus.  This problem was most recently seen with package version 
1:3.26.4-0ubuntu7, the problem page at 
https://errors.ubuntu.com/problem/dc2906efffd8825626072ed9a92ce045cb9e67e7 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1801804/+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 1028267] Re: thunderbird license change not reflected in /usr/share/doc/thunderbird/copyright

2018-11-08 Thread gf

Thanks for changing the importance for me, C!
Take care
:)
G

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

Title:
  thunderbird license change not reflected in
  /usr/share/doc/thunderbird/copyright

Status in Mozilla Thunderbird:
  Unknown
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Now that thunderbird (and firefox, see
  https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1028266) have
  switched from the MPLv1/GPL/LGPL tri-license to MPL 2.0,
  /usr/share/doc/thunderbird/copyright should reflect this. Also,
  /usr/share/doc/thunderbird/MPL.gz should be updated, or removed if the
  MPL 2.0 would be included in /usr/share/doc/thunderbird/copyright.

  Also, based on a quick look, the license list in this file seem to
  lack quite a few of the licenses in the list one can see at
  about:license (help -> about thunderbird -> licensing information).

  This is for thunderbird 14.0 in Ubuntu 10.04 and 12.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1028267/+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 1181708] Re: HP Laserjet Pro MFP M225dn, duplex printing, prints too many copies.

2018-11-08 Thread gf

Thanks for updating the ticket, C!
Have a great day!
:)
G

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

Title:
  HP Laserjet Pro MFP M225dn, duplex printing, prints too many copies.

Status in system-config-printer package in Ubuntu:
  Triaged

Bug description:
  Duplex printing doesn't work when printing multiple copies of a single
  page.

  This has been verified printing pdfs from Okular and Firefox, text
  files from Geddit, and html pages from Firefox. Behaviour same in all
  cases.

  E.g.

  1.

  Duplex printing works correctly with the following options in the
  system-config-printer dialogue:

  Range - Page(s): 1-2
  Copies: 1
  Duplex option: Long-edge

  Result > prints two pages on one sheet of paper.

  2.

  Duplex printing does not work with the following options in the
  system-config-printer dialogue:

  Range - Page(s): 1
  Copies: 2
  Duplex option: Long-edge

  Result > prints two pages on two sheets of paper
  Expected result > two pages on one sheet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1181708/+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 1743736] Re: In overview, windows from all workspaces are shown for the second display (when using "Workspaces span displays")

2018-11-08 Thread Bug Watch Updater

** Changed in: gnome-shell
   Status: Unknown => Confirmed

** Changed in: gnome-shell
   Importance: Unknown => Medium

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

Title:
  In overview, windows from all workspaces are shown for the second
  display (when using "Workspaces span displays")

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I have disabled workspaces on primary display only, and I have enabled
  workspaces to span displays, in tweak tool.

  Now things mostly work how I expect. Windows are isolated to the
  workspace they are and I can move them between displays (monitors).
  The issue is if I go into an overview mode. Then, for the primary
  display, I see only windows from my current workspace. But for the
  secondary display, I see windows from all workspaces being shown in
  the overview mode.

  I would expect that only the windows from the current workspace are
  shown also on the secondary display in the overview mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 02:19:13 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-11-20 (57 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

  This bug also affects the new LTS release:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 23 15:25:07 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-05-18 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1743736/+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 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2018-11-08 Thread Peter Goodall

Is there a related error happening with gnome-session-binary?

>journalctl -b SYSLOG_IDENTIFIER=spice-vdagent SYSLOG_IDENTIFIER=gnome-
session-binary

Nov 09 08:07:47 (...) gnome-session-binary[1191]: WARNING: App 
'org.gnome.Shell.desktop' exited with code 1
Nov 09 08:07:47 (...) gnome-session-binary[1191]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
Nov 09 08:07:52 (...) spice-vdagent[1637]: Cannot access vdagent virtio channel 
/dev/virtio-ports/com.redhat.spice.0
Nov 09 08:07:52 (...) gnome-session-binary[1391]: WARNING: App 
'spice-vdagent.desktop' exited with code 1
Nov 09 08:07:52 (...) gnome-session-binary[1391]: Entering running state
Nov 09 08:09:19 (...) spice-vdagent[2048]: Cannot access vdagent virtio channel 
/dev/virtio-ports/com.redhat.spice.0
Nov 09 08:09:19 (...) gnome-session-binary[1785]: WARNING: App 
'spice-vdagent.desktop' exited with code 1
Nov 09 08:09:19 (...) gnome-session-binary[1785]: Entering running state

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

Title:
  spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-
  ports/com.redhat.spice.0

Status in spice-vdagent package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  $ journalctl -b

  [...]

  oct 26 07:26:57 romanescu spice-vdagent[1345]: Cannot access vdagent
  virtio channel /dev/virtio-ports/com.redhat.spice.0

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: spice-vdagent 0.17.0-1ubuntu2
  Uname: Linux 4.19.0-gnu x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 26 14:34:00 2018
  InstallationDate: Installed on 2017-10-13 (378 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: spice-vdagent
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1800196/+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 1802402] [NEW] [UX430UNR, Realtek ALC294, Black Headphone Out, Left] No sound

2018-11-08 Thread Jiri Tarasovic

Public bug reported:

I expected speaker and headphones to work.
I found speaker silent and headphones slight popping sound only.
But HDMI audio works, also speaker and headphones work on my dualbooted windows 
10.

Description:Ubuntu 18.04.1 LTS
Release:18.04

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jita   1798 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  8 22:45:36 2018
InstallationDate: Installed on 2018-11-07 (1 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jita   1798 F pulseaudio
Symptom_Jack: Black Headphone Out, Left
Symptom_Type: No sound at all
Title: [UX430UNR, Realtek ALC294, Black Headphone Out, Left] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/13/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX430UNR.T157
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX430UNR
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: Tarasovic Jiri
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX430UNR.T157:bd03/13/2018:svnASUSTeKCOMPUTERINC.:pnUX430UNR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UNR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX430UNR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-11-08T22:34:00.520280

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


** Tags: amd64 apport-bug bionic

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

Title:
  [UX430UNR, Realtek ALC294, Black Headphone Out, Left] No sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I expected speaker and headphones to work.
  I found speaker silent and headphones slight popping sound only.
  But HDMI audio works, also speaker and headphones work on my dualbooted 
windows 10.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jita   1798 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  8 22:45:36 2018
  InstallationDate: Installed on 2018-11-07 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jita   1798 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [UX430UNR, Realtek ALC294, Black Headphone Out, Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/13/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UNR.T157
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UNR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Tarasovic Jiri
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX430UNR.T157:bd03/13/2018:svnASUSTeKCOMPUTERINC.:pnUX430UNR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UNR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX430UNR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-11-08T22:34:00.520280

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1802402/+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 1769383] Re: Ubuntu dock/launcher is shown on the lock screen

2018-11-08 Thread Mike Chaberski

This seems like a duplicate of #1716982, but maybe it's a regression
after that was fixed. Anyway, commenter ernstp identifies the cause in
comment #12 [1]:

> Is it some global variable name conflict between the two extensions?
"dockManager" perhaps?

You can edit /usr/share/gnome-shell/extensions/ubuntu-
d...@ubuntu.com/extension.js to check for a null dockManager in the
disable() function. That is, change

dockManager.destroy()

to

if (dockManager != null) {
dockManager.destroy();
}

and the dock disappears when the screen is locked, as expected.

I'm guessing the problem is that Dash To Dock sets dockManager to null
after calling destroy(), and then Ubuntu Dock throws a TypeError when it
tries to do the same, so Ubuntu Dock never reaches the
ExtensionSystem.disconnect() call.

[1] https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-
ubuntu-dock/+bug/1716982/comments/12

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

Title:
  Ubuntu dock/launcher is shown on the lock screen

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete

Bug description:
  After an update from ubuntu 16.04 to 18.04 the dock is aviable on the 
lockscreen after user login.
  I did not configure this knowingly. Also i can start every application which 
is available on the dock.
  Settings, virtual box, visualstudio code and so on.

  After the update to 18.04 i just configure the screen frequency to
  144Hz and the night mode on. And attach the dock on bottom.

  I later undid these customizations back to configuration before, but
  the dock is stil aviable on lockscreen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 18:30:16 2018
  InstallationDate: Installed on 2018-04-08 (27 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (27 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell-extension-ubuntu-dock 0.9.1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+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 1802350] Re: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem

2018-11-08 Thread Cristian Aravena Romero

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1802350

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

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

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

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

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

Title:
  [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem

Status in alsa-driver package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a fresh install of ubutu 18.04 all sound work (youtube and system
  sounds) I connected external hdmi monitor with speakers. I switched
  audio output to hdmi in settings

  Then all audio was channeled to external monitor speakers (youtube and
  system sounds)

  Then I disconnected external monitor and did not touch the audio
  output

  Now only system sounds are working. Youtube in chrome does not work.
  Audio settings says internal speakers.

  Firefox youtube has audio normally

  After reboot same issue

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ed 1412 F pulseaudio
   /dev/snd/controlC1:  ed 1412 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  8 12:28:37 2018
  InstallationDate: Installed on 2018-11-01 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0598GM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A11
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd01/24/2018:svnDellInc.:pnInspiron5547:pvrA11:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA11:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5547
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1802350/+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 1802366] Re: i dont know

2018-11-08 Thread Cristian Aravena Romero

** Changed in: xorg (Ubuntu)
 Assignee: François ZOLIN (ustas) => (unassigned)

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

Title:
  i dont know

Status in xorg package in Ubuntu:
  New

Bug description:
  + i don't speak English+i am not informatics just a user

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  410.73  Sat Oct 20 22:12:33 
CDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Nov  8 19:13:59 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 410.73, 4.15.0-39-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-33-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-39-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GM204M [GeForce GTX 970M] [1043:22da]
  InstallationDate: Installed on 2017-12-29 (313 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 
(20170926)
  MachineType: ASUSTeK COMPUTER INC. G751JT
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=3b41e99c-b074-4029-826b-39ad3587 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G751JT.202
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G751JT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG751JT.202:bd09/10/2014:svnASUSTeKCOMPUTERINC.:pnG751JT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG751JT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G751JT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Nov  8 15:34:32 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1802366/+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 1760068] Re: Wrong resolution at unlock screen

Well, as mentioned in comment #10, this bug is not limited to the unlock
screen (which happens to be a second Xorg instance if you use light-
locker).

Does the workaround in bug 1757202 fix the issue for you?

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

Title:
  Wrong resolution at unlock screen

Status in light-locker package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  After coming out of suspend - the unlock screen is at 640x480
  resolution.

  Expect to see unlock screen at 1920x1080 resolution.

  Using nvidia-340.

  Previously tested using nouveau driver where resolution at unlock
  screen was correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-locker 1.8.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 30 11:31:20 2018
  InstallationDate: Installed on 2017-09-02 (209 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1760068/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-11-08 Thread bblrlo

On KUbuntu 18.04 same problem with card GT630M and 390,396 nvidia drivers
#lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename:   bionic
# cat /etc/X11/default-display-manager 
/usr/bin/sddm

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1799665] Re: [cosmic regression] fails to parse known_hosts, resulting in SSH_SERVER_FOUND_OTHER error for hostkey verification

2018-11-08 Thread Martin Pitt

I installed libssh-4 0.8.1-1ubuntu0.2 from cosmic-proposed, and confirm
that the manual ssh connection with "cockpit-ssh" as well as all the
integration tests that involve talking to remote machines through ssh
now work.

** Tags removed: verification-needed verification-needed-cosmic
** Tags added: verification-done verification-done-cosmic

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

Title:
  [cosmic regression] fails to parse known_hosts, resulting in
  SSH_SERVER_FOUND_OTHER error for hostkey verification

Status in libssh package in Ubuntu:
  In Progress
Status in libssh source package in Cosmic:
  Fix Committed

Bug description:
  Ubuntu 18.10's libssh 0.8.1 regresses parsing of known_hosts. This
  happens (sometimes) if there are multiple known_host key types (e. g.
  ssh-rsa and ssh-ed25519), then it can happen that
  ssh_session_is_known_server() fails with SSH_SERVER_FOUND_OTHER [1].

  I noticed this with testing Cockpit on Ubuntu 18.10 [2], which has a
  few test cases exercising cockpit-ssh (which uses libssh), e. g. [3].
  The scenario is a FreeIPA centrally managed known_hosts file with
  these entries:

  x0.cockpit.lan ssh-rsa 
B3NzaC1yc2EDAQABAAABAQCv5sLKfLDuEAbTcHC3eOgJM+Ot7F077KewD4e1lGzfw300Jo4xnuPsoJEVSCR7OjsYQCnuVGlqtlavMCLFzIBNk06iTBg/nl+W+xa3CFNITbAjiBif7SeY0XL6Xeqzb1VYXNVfwKQKpcGIbDne6jyou4wRZV1eay03FHTSkd2+XKM6GOUGlkEUoPyAwYPHqoKUYiiyBxJs20l/peXVx6jsGgs2Sc6gl3KJP0TB2E7ncD1pWHGRtiNshFFVarw/YKr+Rs+KhiVS3CAAfYDhpBNWXOwTKyx2euJjAhsRF10bx6pnuadSEpT8Ufo5/YFIVAD1GHptULSzVjUoJm6ktoHB
  x0.cockpit.lan ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBCkJ6CaqhzUhrbpbVmZ8BmZZgM3u6BukZ6HFB2a4NLQBdgpHlHbxoJ47ocTImctyFMiDi0y6vCb4tFuZgp6Krmk=
 root@(none)
  x0.cockpit.lan ssh-ed25519 
C3NzaC1lZDI1NTE5INK6gcOyH4OhiKPcNr33Kl6e+wFAUy9tGFBU/o4yWkxh root@(none)

  Connecting to that host with the standard ssh client works:

  $ ssh -vv x0.cockpit.lan
  [...]
  debug1: Server host key: ecdsa-sha2-nistp256 
SHA256:MgfkN6HEl+pdz0X7+6q08IVkUZOtEDzfA6V18Wm9DgA
  debug1: Host 'x0.cockpit.lan' is known and matches the ECDSA host key.
  debug1: Found key in /var/lib/sss/pubconf/known_hosts:3
  [...]
  ad...@cockpit.lan@x0:~$

  But not with cockpit-ssh. This shows the JSON protocol (note that you
  need to copy the correct cookie value from the response):

  $ G_MESSAGES_DEBUG=cockpit-ssh cockpit-bridge --interact=---

  { "command": "open", "channel": "c", "payload": "echo", "host": 
"x0.cockpit.lan", "user": "ad...@cockpit.lan" }
  ---

  {"command":"authorize","challenge":"*","cookie":"session107271540364829"}
  ---

  {"command":"authorize", "response": "password foobarfoo", "cookie": 
"session107271540364829"}
  ---
  (cockpit-ssh:10814): cockpit-ssh-DEBUG: 03:11:51.049: cockpit-ssh 
x0.cockpit.lan: host not known in any local file, asking sssd
  (cockpit-ssh:10814): cockpit-ssh-DEBUG: 03:11:51.472: cockpit-ssh 
x0.cockpit.lan: using known hosts file /tmp/known-hosts.IDKNRZ
  (cockpit-ssh:10814): cockpit-ssh-DEBUG: 03:11:51.542: cockpit-ssh 
x0.cockpit.lan: connected
  cockpit-ssh-Message: 03:07:30.828: cockpit-ssh x0.cockpit.lan: host key for 
this server changed key type: ssh-ed25519

  {"command":"close","host-key":"x0.cockpit.lan ssh-ed25519 
C3NzaC1lZDI1NTE5INK6gcOyH4OhiKPcNr33Kl6e+wFAUy9tGFBU/o4yWkxh\n","host-fingerprint":"a0:27:1e:80:de:fd:4b:8a:0d:9d:a9:b6:42:7d:5c:b9","problem":"invalid-hostkey","error":"invalid-hostkey","auth-method-results":{},"channel":"c"}
  ---

  The "host key for this server changed key type" is the effect of this
  bug.


  SRU INFORMATION:

  [IMPACT]: libssh connections that worked in previous Ubuntu releases
  now may fail on host key verification

  [TEST CASE]: See reproducer below. This isn't too easy to reproduce
  for someone else, so I'm happy to do the validation myself. This can
  also be verified with the Cockpit integration tests:

  bots/image-prepare ubuntu-stable
  TEST_OS=ubuntu-stable test/verify/check-realms TestRealms.testIpa

  [REGRESSION POTENTIAL]: In principle these patches could break known_hosts 
validation further. However, these fixes have been in Debian testing for a 
while and validated through e. g. Cockpit's tests (which exercise cockpit-ssh 
quite heavily). There are also upstream unit tests, and while they didn't pick 
up that particular regression, they at least make sure that known_hosts 
verification still works for common  cases.
  Also, libssh-4 does not have that many reverse dependencies. So overall, I 
think this is bearable for an SRU, especially as the impact is quite high.

  [1] 
http://api.libssh.org/master/group__libssh__session.html#gac%20bc5d04fe66beee863a0c61a93fdf765
  [2] https://github.com/cockpit-project/cockpit/pull/10357
  [3]

[Desktop-packages] [Bug 1580123] Re: xrandr --scale (again) confines mouse to native solution

2018-11-08 Thread Joseph Long

Will this fix be backported to 18.04 LTS when released? Apologies for
not understanding the bug workflow here, but I can't find a way to
indicate that I'm experiencing this bug on 18.04 LTS.

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

Title:
  xrandr --scale (again) confines mouse to native solution

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  This might be a regression where the original issue is:
  https://bugs.launchpad.net/xorg-server/+bug/883319

  It can be easily reproduced by doing something like:

  xrandr --output DP1 --scale 1.25x1.25

  The mouse will be still constrained to the native solution (aka you
  can't move the mouse outside a box of whatever DP1 had as resolution
  before.

  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ xrandr --version
  xrandr program version   1.5.0
  Server reports RandR version 1.5

  $ apt-cache policy xserver-xorg-core
  xserver-xorg-core:
Installed: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1580123/+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 964705] Re: System policy prevents modification of network settings for all users

2018-11-08 Thread Wendell Nichols

I just installed kubuntu 18 after a long absence.  I found that to make any 
change to the network settings I had to key in my (16 digit) password multiple 
times.  About 5 times in fact.
Its a laptop.  The user has to be able to do things like this.  
If I have to modify system files (and reapply those changes after maintenance) 
then its just not worth it.

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

Title:
  System policy prevents modification of network settings for all users

Status in NetworkManager:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Debian:
  Fix Released
Status in network-manager package in openSUSE:
  Fix Released

Bug description:
  This seems like a regression? The screen shot is at
  http://thesii.org/Screenshot.jpg The nearest link I can find is from
  the forum area at http://ubuntuforums.org/showthread.php?p=1146

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory
  Date: Sun Mar 25 19:36:45 2012
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Alpha amd64 (20120323)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/964705/+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 1760068] Re: Wrong resolution at unlock screen

2018-11-08 Thread Hélio Nunes

I'm using the 340.107 and the problem persists.

As I told in #7, a second X user is affected too, not only the unlock
screen. That's the big problem with this bug: it is not only an
aesthetic problem.

I confirm that all works as intended with the nouveau driver.

I did not found any error messages in the /var/log/lightdm/ files.

Where and what should I look to contribute more?

Thanks.

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

Title:
  Wrong resolution at unlock screen

Status in light-locker package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  After coming out of suspend - the unlock screen is at 640x480
  resolution.

  Expect to see unlock screen at 1920x1080 resolution.

  Using nvidia-340.

  Previously tested using nouveau driver where resolution at unlock
  screen was correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-locker 1.8.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 30 11:31:20 2018
  InstallationDate: Installed on 2017-09-02 (209 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1760068/+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 1802375] [NEW] network printer OKI mc352 not working any more (after update?)

2018-11-08 Thread Helmut Raiger

Public bug reported:

The printer shows up using lpinfo -v:

network beh
file cups-brf:/
network ipp
serial serial:/dev/ttyS0?baud=115200
serial serial:/dev/ttyS4?baud=115200
serial serial:/dev/ttyS5?baud=115200
network lpd
network socket
network http
network https
network ipps
direct parallel:/dev/lp0
direct parallel:/dev/lp1
direct hp
direct hpfax
network dnssd://OKI-MC352-26F106._pdl-datastream._tcp.local/

but stays in 'processing' mode forever when I tell it to print the test
page.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CupsErrorLog:
 E [08/Nov/2018:15:21:22 +0100] Unknown directive JobPrivateAccess on line 123 
of /etc/cups/cupsd.conf.
 E [08/Nov/2018:15:21:22 +0100] Unknown directive JobPrivateValues on line 124 
of /etc/cups/cupsd.conf.
 E [08/Nov/2018:15:21:22 +0100] Unknown directive SubscriptionPrivateAccess on 
line 125 of /etc/cups/cupsd.conf.
 E [08/Nov/2018:15:21:22 +0100] Unknown directive SubscriptionPrivateValues on 
line 126 of /etc/cups/cupsd.conf.
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  8 20:07:16 2018
InstallationDate: Installed on 2018-06-19 (142 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lpstat: device for OKI-DATA-CORP-MC352: 
dnssd://OKI-MC352-26F106._pdl-datastream._tcp.local/
MachineType: System manufacturer System Product Name
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/OKI-DATA-CORP-MC352.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/OKI-DATA-CORP-MC352.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic 
root=UUID=5a33fc23-a448-4980-a91b-fc81d565dc39 ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/23/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2105
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A785TD-V EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2105:bd07/23/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-VEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apparmor apport-bug bionic

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

Title:
  network printer OKI mc352 not working any more (after update?)

Status in cups package in Ubuntu:
  New

Bug description:
  The printer shows up using lpinfo -v:

  network beh
  file cups-brf:/
  network ipp
  serial serial:/dev/ttyS0?baud=115200
  serial serial:/dev/ttyS4?baud=115200
  serial serial:/dev/ttyS5?baud=115200
  network lpd
  network socket
  network http
  network https
  network ipps
  direct parallel:/dev/lp0
  direct parallel:/dev/lp1
  direct hp
  direct hpfax
  network dnssd://OKI-MC352-26F106._pdl-datastream._tcp.local/

  but stays in 'processing' mode forever when I tell it to print the
  test page.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CupsErrorLog:
   E [08/Nov/2018:15:21:22 +0100] Unknown directive JobPrivateAccess on line 
123 of /etc/cups/cupsd.conf.
   E [08/Nov/2018:15:21:22 +0100] Unknown directive JobPrivateValues on line 
124 of /etc/cups/cupsd.conf.
   E [08/Nov/2018:15:21:22 +0100] Unknown directive SubscriptionPrivateAccess 
on line 125 of /etc/cups/cupsd.conf.
   E [08/Nov/2018:15:21:22 +0100] Unknown directive SubscriptionPrivateValues 
on line 126 of /etc/cups/cupsd.conf.
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  8 20:07:16 2018
  InstallationDate: Installed on 2018-06-19 (142 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat: device for OKI-DATA-CORP-MC352: 
dnssd://OKI-MC352-26F106._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/OKI-DATA-CORP-MC352.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/OKI-DATA-CORP-MC352.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic 
root=UUID=5a33fc23-a448-4980-a91b-fc81d565dc39 ro quiet splash vt.handoff=1

[Desktop-packages] [Bug 1802353] Re: Ubuntu 18.04 falls back to LLVMpipe (CPU render) with Intel graphics

2018-11-08 Thread Crati

** Description changed:

  A fresh Xubuntu 18.04.1 install (from an ISO), on a machine with only the 
Intel integrated graphics  (i9-9900k => UHD-630). The graphic drivers module 
seems to be properly loaded, but X rendering seems to fallback to LLVMpipe.
- This was the case immediately after the install. The performance of the SW 
rendering improved after the first update with the latest packages but it is 
still very problematic, for ex. Eclipse has very severe flashing glitches as it 
redraws the editor windows.
+ This was the case immediately after the install. The performance of the SW 
rendering improved significantly after the first update with the latest 
packages.
  
  $ glxinfo | grep "OpenGL"
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits)
  OpenGL version string: 3.0 Mesa 18.0.5
  OpenGL shading language version string: 1.30
  OpenGL context flags: (none)
  
  dmesg output:
  [4.725296] [drm] Replacing VGA console driver
  [4.731702] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [4.731704] [drm] Driver supports precise vblank timestamp query.
  [4.733885] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [4.734288] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [5.003709] [drm] failed to retrieve link info, disabling eDP
  [5.004608] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on 
minor 0
  [5.005628] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
  [5.005799] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
  [5.174759] fbcon: inteldrmfb (fb0) is primary device
  [5.209969] Console: switching to colour frame buffer device 320x90
  [5.229823] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  
  I tried using the latest stable mesa from ubuntu-x-swat/updates but it
  did not help (I ppa-purge'd it before generating the bug report)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libegl1 1.0.0-2ubuntu2.2
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Nov  8 17:52:03 2018
  InstallationDate: Installed on 2018-11-06 (2 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: libglvnd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Ubuntu 18.04 falls back to LLVMpipe (CPU render) with Intel graphics

Status in libglvnd package in Ubuntu:
  New

Bug description:
  A fresh Xubuntu 18.04.1 install (from an ISO), on a machine with only the 
Intel integrated graphics  (i9-9900k => UHD-630). The graphic drivers module 
seems to be properly loaded, but X rendering seems to fallback to LLVMpipe.
  This was the case immediately after the install. The performance of the SW 
rendering improved significantly after the first update with the latest 
packages.

  $ glxinfo | grep "OpenGL"
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits)
  OpenGL version string: 3.0 Mesa 18.0.5
  OpenGL shading language version string: 1.30
  OpenGL context flags: (none)

  dmesg output:
  [4.725296] [drm] Replacing VGA console driver
  [4.731702] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [4.731704] [drm] Driver supports precise vblank timestamp query.
  [4.733885] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [4.734288] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [5.003709] [drm] failed to retrieve link info, disabling eDP
  [5.004608] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on 
minor 0
  [5.005628] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
  [5.005799] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
  [5.174759] fbcon: inteldrmfb (fb0) is primary device
  [5.209969] Console: switching to colour frame buffer device 320x90
  [5.229823] i915 :00:02.0: fb0: inteldrmfb frame buffer device

  I tried using the latest stable mesa from ubuntu-x-swat/updates but it
  did not help (I ppa-purge'd it before generating the bug report)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libegl1 1.0.0-2ubuntu2.2
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Nov  8 17:52:03 2018
  InstallationDate: Installed on 2018-11-06 (2 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS

[Desktop-packages] [Bug 1797178] Re: gnome-shell activities / application icon touches not fully registering

2018-11-08 Thread Joe Barnett

And with more testing, it seems like the activities button target is
smaller and/or lower under Wayland than it is in Xorg.  I can get it to
work if i aim for the bottom of the black top bar, vs the middle of it
(while aiming for the middle results in the flash, but not activation of
the Activites text).

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

Title:
  gnome-shell activities / application icon touches not fully
  registering

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  On a dell xps 15 2-in-1 (model 9575), the touchscreen mostly works.
  However, in gnome-shell, touching the top-left 'Activities' menu
  results in a quick flash of the menu button, but not the launching of
  the overview.  Once in the overview (via mouse/keyboard/swipe-from-
  left), touching on an application icon (in either the left tray or the
  applications grid) results in the application icon flashing, but not
  activating.  A long-touch will bring up a menu in which touching on
  "new window" works properly.  Additionally, touching the "show
  applications" grid button works, as do other components of the top
  bar, its only the the "activities" menu button and app icon launchers
  that are "registering" a touch but not activating properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 10 09:13:40 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-26 (14 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to cosmic on 2018-09-28 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797178/+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 1802366] Re: i dont know

2018-11-08 Thread François ZOLIN

thank you

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

Title:
  i dont know

Status in xorg package in Ubuntu:
  New

Bug description:
  + i don't speak English+i am not informatics just a user

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  410.73  Sat Oct 20 22:12:33 
CDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Nov  8 19:13:59 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 410.73, 4.15.0-39-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-33-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-39-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GM204M [GeForce GTX 970M] [1043:22da]
  InstallationDate: Installed on 2017-12-29 (313 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 
(20170926)
  MachineType: ASUSTeK COMPUTER INC. G751JT
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=3b41e99c-b074-4029-826b-39ad3587 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G751JT.202
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G751JT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG751JT.202:bd09/10/2014:svnASUSTeKCOMPUTERINC.:pnG751JT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG751JT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G751JT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Nov  8 15:34:32 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1802366/+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 1802366] [NEW] i dont know

2018-11-08 Thread François ZOLIN

Public bug reported:

+ i don't speak English+i am not informatics just a user

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  410.73  Sat Oct 20 22:12:33 
CDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Nov  8 19:13:59 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 410.73, 4.15.0-39-generic, x86_64: installed
 virtualbox, 5.2.18, 4.15.0-33-generic, x86_64: installed
 virtualbox, 5.2.18, 4.15.0-39-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GM204M [GeForce GTX 970M] [1043:22da]
InstallationDate: Installed on 2017-12-29 (313 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 
(20170926)
MachineType: ASUSTeK COMPUTER INC. G751JT
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=3b41e99c-b074-4029-826b-39ad3587 ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/10/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G751JT.202
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G751JT
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG751JT.202:bd09/10/2014:svnASUSTeKCOMPUTERINC.:pnG751JT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG751JT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G751JT
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Thu Nov  8 15:34:32 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4.2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Assignee: François ZOLIN (ustas)
 Status: New


** Tags: amd64 apport-bug bionic ubuntu

** Changed in: xorg (Ubuntu)
 Assignee: (unassigned) => François ZOLIN (ustas)

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

Title:
  i dont know

Status in xorg package in Ubuntu:
  New

Bug description:
  + i don't speak English+i am not informatics just a user

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  410.73  Sat Oct 20 22:12:33 
CDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Nov  8 19:13:59 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 410.73, 4.15.0-39-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-33-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-39-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GM204M [GeForce GTX 970M] [1043:22da]

[Desktop-packages] [Bug 1802353] [NEW] Ubuntu 18.04 falls back to LLVMpipe (CPU render) with Intel graphics

2018-11-08 Thread Crati

Public bug reported:

A fresh Xubuntu 18.04.1 install (from an ISO), on a machine with only the Intel 
integrated graphics  (i9-9900k => UHD-630). The graphic drivers module seems to 
be properly loaded, but X rendering seems to fallback to LLVMpipe.
This was the case immediately after the install. The performance of the SW 
rendering improved after the first update with the latest packages but it is 
still very problematic, for ex. Eclipse has very severe flashing glitches as it 
redraws the editor windows.

$ glxinfo | grep "OpenGL"
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits)
OpenGL version string: 3.0 Mesa 18.0.5
OpenGL shading language version string: 1.30
OpenGL context flags: (none)

dmesg output:
[4.725296] [drm] Replacing VGA console driver
[4.731702] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[4.731704] [drm] Driver supports precise vblank timestamp query.
[4.733885] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
[4.734288] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
[5.003709] [drm] failed to retrieve link info, disabling eDP
[5.004608] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0
[5.005628] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[5.005799] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
[5.174759] fbcon: inteldrmfb (fb0) is primary device
[5.209969] Console: switching to colour frame buffer device 320x90
[5.229823] i915 :00:02.0: fb0: inteldrmfb frame buffer device

I tried using the latest stable mesa from ubuntu-x-swat/updates but it
did not help (I ppa-purge'd it before generating the bug report)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libegl1 1.0.0-2ubuntu2.2
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Nov  8 17:52:03 2018
InstallationDate: Installed on 2018-11-06 (2 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
SourcePackage: libglvnd
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Description changed:

  A fresh Xubuntu 18.04.1 install (from an ISO), on a machine with only the 
Intel integrated graphics  (i9-9900k => UHD-630). The graphic drivers module 
seem to be properly loaded, but X rendering seems to fallback to LLVMpipe.
  This was the case immediately after the install. The performance of the SW 
rendering improved after the first update with the latest packages but it is 
still very problematic, for ex. Eclipse has very severe flashing glitches as it 
redraws the editor windows.
  
  $ glxinfo | grep "OpenGL"
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits)
  OpenGL version string: 3.0 Mesa 18.0.5
  OpenGL shading language version string: 1.30
  OpenGL context flags: (none)
  
  dmesg output:
  [4.725296] [drm] Replacing VGA console driver
  [4.731702] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [4.731704] [drm] Driver supports precise vblank timestamp query.
  [4.733885] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [4.734288] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [5.003709] [drm] failed to retrieve link info, disabling eDP
  [5.004608] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on 
minor 0
  [5.005628] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
  [5.005799] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
  [5.174759] fbcon: inteldrmfb (fb0) is primary device
  [5.209969] Console: switching to colour frame buffer device 320x90
  [5.229823] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  
- I tried to get the latest stable mesa from ubuntu-x-swat/updates but it
+ I tried using the latest stable mesa from ubuntu-x-swat/updates but it
  did not help (I ppa-purge'd it before generating the bug report)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libegl1 1.0.0-2ubuntu2.2
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Nov  8 17:52:03 2018
  InstallationDate: Installed on 2018-11-06 (2 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: libglvnd
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

- A fresh Xubuntu 18.04.1 install (from an ISO), on a machine with

[Desktop-packages] [Bug 1802352] [NEW] package emacs-gtk 1:25.2+1-11 failed to install/upgrade: installed emacs-gtk package post-installation script subprocess returned error exit status 1

2018-11-08 Thread Andrew Allcock

Public bug reported:

Automatically generated bug report on software upgrade

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: emacs-gtk 1:25.2+1-11
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
Date: Thu Nov  8 17:44:38 2018
ErrorMessage: installed emacs-gtk package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2015-12-11 (1063 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt  1.7.0
SourcePackage: emacs
Title: package emacs-gtk 1:25.2+1-11 failed to install/upgrade: installed 
emacs-gtk package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: Upgraded to cosmic on 2018-10-20 (19 days ago)

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


** Tags: amd64 apport-package cosmic

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

Title:
  package emacs-gtk 1:25.2+1-11 failed to install/upgrade: installed
  emacs-gtk package post-installation script subprocess returned error
  exit status 1

Status in emacs package in Ubuntu:
  New

Bug description:
  Automatically generated bug report on software upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: emacs-gtk 1:25.2+1-11
  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
  Date: Thu Nov  8 17:44:38 2018
  ErrorMessage: installed emacs-gtk package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2015-12-11 (1063 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.0
  SourcePackage: emacs
  Title: package emacs-gtk 1:25.2+1-11 failed to install/upgrade: installed 
emacs-gtk package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1802352/+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 1783903] Re: DHCP Renewal Kills Anyconnect VPN Connections

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  DHCP Renewal Kills Anyconnect VPN Connections

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When using the Cisco Anyconnect client to connect to my works VPN. The
  VPN is unstable and drops into re configuring mode when a DHCP request
  is sent. From my research if I remove the network-manager-config-
  connectivity-ubuntu package the connection is stable.

  Similar Issues for like package with FC28:
  https://bugzilla.redhat.com/show_bug.cgi?id=1576910

  Description:  Linux Mint 19 Tara
  Release:  19

  network-manager:
    Installed: 1.10.6-2ubuntu1
    Candidate: 1.10.6-2ubuntu1
    Version table:
   *** 1.10.6-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  network-manager-config-connectivity-ubuntu:
    Installed: 1.10.6-2ubuntu1
    Candidate: 1.10.6-2ubuntu1
    Version table:
   *** 1.10.6-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status

  Log attached next comment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1783903/+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 1802350] Re: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem

2018-11-08 Thread Edgard Aspilcueta

On a fresh install of ubutu 18.04 all sound work (youtube and system
sounds) I connected external hdmi monitor with speakers. I switched
audio output to hdmi in settings

Then all audio was channeled to external monitor speakers (youtube and
system sounds)

Then I disconnected external monitor and did not touch the audio output

Now only system sounds are working. Youtube in chrome does not work.
Audio settings says internal speakers.

Firefox youtube has audio normally

After reboot same issue

Seems issue is in Chrome.

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

Title:
  [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On a fresh install of ubutu 18.04 all sound work (youtube and system
  sounds) I connected external hdmi monitor with speakers. I switched
  audio output to hdmi in settings

  Then all audio was channeled to external monitor speakers (youtube and
  system sounds)

  Then I disconnected external monitor and did not touch the audio
  output

  Now only system sounds are working. Youtube in chrome does not work.
  Audio settings says internal speakers.

  Firefox youtube has audio normally

  After reboot same issue

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ed 1412 F pulseaudio
   /dev/snd/controlC1:  ed 1412 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  8 12:28:37 2018
  InstallationDate: Installed on 2018-11-01 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0598GM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A11
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd01/24/2018:svnDellInc.:pnInspiron5547:pvrA11:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA11:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5547
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1802350/+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 1802350] [NEW] [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem

2018-11-08 Thread Edgard Aspilcueta

Public bug reported:

On a fresh install of ubutu 18.04 all sound work (youtube and system
sounds) I connected external hdmi monitor with speakers. I switched
audio output to hdmi in settings

Then all audio was channeled to external monitor speakers (youtube and
system sounds)

Then I disconnected external monitor and did not touch the audio output

Now only system sounds are working. Youtube in chrome does not work.
Audio settings says internal speakers.

Firefox youtube has audio normally

After reboot same issue

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ed 1412 F pulseaudio
 /dev/snd/controlC1:  ed 1412 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  8 12:28:37 2018
InstallationDate: Installed on 2018-11-01 (6 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Only some of outputs are working
Title: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/24/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0598GM
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A11
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd01/24/2018:svnDellInc.:pnInspiron5547:pvrA11:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA11:
dmi.product.family: 00
dmi.product.name: Inspiron 5547
dmi.product.version: A11
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On a fresh install of ubutu 18.04 all sound work (youtube and system
  sounds) I connected external hdmi monitor with speakers. I switched
  audio output to hdmi in settings

  Then all audio was channeled to external monitor speakers (youtube and
  system sounds)

  Then I disconnected external monitor and did not touch the audio
  output

  Now only system sounds are working. Youtube in chrome does not work.
  Audio settings says internal speakers.

  Firefox youtube has audio normally

  After reboot same issue

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ed 1412 F pulseaudio
   /dev/snd/controlC1:  ed 1412 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  8 12:28:37 2018
  InstallationDate: Installed on 2018-11-01 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0598GM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A11
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd01/24/2018:svnDellInc.:pnInspiron5547:pvrA11:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA11:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5547
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1802350] Re: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem

2018-11-08 Thread Edgard Aspilcueta

I also submitted bug in Chrome for ubuntu

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

Title:
  [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On a fresh install of ubutu 18.04 all sound work (youtube and system
  sounds) I connected external hdmi monitor with speakers. I switched
  audio output to hdmi in settings

  Then all audio was channeled to external monitor speakers (youtube and
  system sounds)

  Then I disconnected external monitor and did not touch the audio
  output

  Now only system sounds are working. Youtube in chrome does not work.
  Audio settings says internal speakers.

  Firefox youtube has audio normally

  After reboot same issue

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ed 1412 F pulseaudio
   /dev/snd/controlC1:  ed 1412 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  8 12:28:37 2018
  InstallationDate: Installed on 2018-11-01 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0598GM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A11
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd01/24/2018:svnDellInc.:pnInspiron5547:pvrA11:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA11:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5547
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1802350/+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 1801832] Re: Input method toggled when using the numeric pad

2018-11-08 Thread Randy Tang

Ubuntu 18.04 LTS

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

Title:
  Input method toggled when using the numeric pad

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.04 LTS

  During the Chinese character input mode, when I enter numbers using
  the numeric pad, the input method will be switched to English
  automatically, which is very annoying. Any suggestions?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1801832/+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 1801832] Re: Input method toggled when using the numeric pad

What desktop environment/session are you using?

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

Title:
  Input method toggled when using the numeric pad

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.04 LTS

  During the Chinese character input mode, when I enter numbers using
  the numeric pad, the input method will be switched to English
  automatically, which is very annoying. Any suggestions?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1801832/+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 1802331] [NEW] Drop down menus appear in wrong position when using multiple monitors arranged vertically

2018-11-08 Thread Paul Crockett

Public bug reported:

I am using multiple monitors arranged as shown below:

++++
|__3_||__2_|
||||
++++
   +-+
   |1|
   |_|
   +-+

Monitors 1 and 3 have different resolutions (1920x1080 and 1600x900) and
are arranged so that their right edges align.

When opening a drop down menu (such as the 'File' menu in terminal) that
appears to the top left of a full-screen application on monitor 3, the
drop down menu position is offset horizontally. It is as if menus that
appear at the left of monitor 3 are 'pushed' to the right so that they
are in line with monitor 1.

The attached screen capture shows roughly where the File menu drop down
appears.

Menus on monitors 1 and 2 appear in the expected location.

I imagine this is a problem with GNOME 3, as I never had this problem
with Unity on Ubuntu 16, and it seems to affect all applications.

Description:Ubuntu 18.04.1 LTS
Release:18.04

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  8 15:26:34 2018
ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
InstallationDate: Installed on 2018-11-02 (6 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "Mocked-up screen shot"
   
https://bugs.launchpad.net/bugs/1802331/+attachment/5210387/+files/menupos.png

** Description changed:

  I am using multiple monitors arranged as shown below:
  
  ++++
- |  3 || 2  |
- ||||
+ |__3_||__2_|
+ ||||
  ++++
-+-+
-|   1 |
-| |
-+-+
+    +-+
+    |1|
+    |_|
+    +-+
  
- 
- Monitors 1 and 3 have different resolutions (1920x1080 and 1600x900) and are 
arranged so that their right edges align.
+ Monitors 1 and 3 have different resolutions (1920x1080 and 1600x900) and
+ are arranged so that their right edges align.
  
  When opening a drop down menu (such as the 'File' menu in terminal) that
  appears to the top left of a full-screen application on monitor 3, the
  drop down menu position is offset horizontally. It is as if menus that
  appear at the left of monitor 3 are 'pushed' to the right so that they
  are in line with monitor 1.
  
  The attached screen capture shows roughly where the File menu drop down
  appears.
  
  Menus on monitors 1 and 2 appear in the expected location.
  
  I imagine this is a problem with GNOME 3, as I never had this problem
  with Unity on Ubuntu 16, and it seems to affect all applications.
  
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  8 15:26:34 2018
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2018-11-02 (6 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
-  LANG=en_GB.UTF-8
-  LANGUAGE=en_GB:en
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  XDG_RUNTIME_DIR=
+  LANG=en_GB.UTF-8
+  LANGUAGE=en_GB:en
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Drop down menus appear in wrong position when using multiple monitors
  arranged vertically

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I am using multiple monitors arranged as shown below:

  ++++
  |__3_||__2_|
  ||||
  ++++
     +-+
     |1|
     |_|
     +-+

  Monitors 1 and 3 have different resolutions (1920x1080 and 1600x900)
  and are arranged so that their right edges align.

  When opening a drop down menu (such as the 'File' menu in terminal)
  that appears to the top left of a

[Desktop-packages] [Bug 1783637] Re: light-locker causes tty to change

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

** This bug has been marked a duplicate of bug 1760068
   Wrong resolution at unlock screen

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

Title:
  light-locker causes tty to change

Status in light-locker package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  After upgrading to 18.04, on xfce4 with Display Power Management
  (xfce4-power-manager) enabled, or any of the three sliders set to non-
  zero, then when the time limit is hit after inactivity two monitors
  power down, but then the tty switches to tty8, and the third monitor
  just shows a black with a cursor flashing. Switching back to tty7
  shows text saying that the session is locked, but no amount of
  keyboard or mouse activity brings up a prompt to unlock it.

  Two Xorg logs are created when this happens (see attached). Ctrl-
  Alt-F# will switch to other ttys at this point, but only briefly
  before switching back to the one that is black with a single flashing
  cursor. After a few switchings between ttys, it stops automatically
  going back to tty8.

  This problem also occurs when xscreensaver is used to control the
  display power management as well. However on switching back to tty7 in
  this case, the unlock dialog is presented as expected and things
  continue to work. So it would appear it is something more fundamental
  than xfce4-power-manager that is causing the active tty to change when
  the screens go sleep.

  The screen power off that occurs while the lightdm's graphical login
  is presented (i.e. before logging in) works fine.

  This problem appears to be due to light-locker. If I stop it from
  running the problem goes away.

  (I would expect things to happen as in 17.10, namely that the displays
  blank/switch off as selected, and then when further input is given
  they unblank/switch on.)

  Please let me know what further information I can provide to narrow
  down the problem.

  lsb_release -rd:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  apt-cache policy xfce4-power-manager:
  xfce4-power-manager:
    Installed: 1.6.1-0ubuntu1
    Candidate: 1.6.1-0ubuntu1
    Version table:
   *** 1.6.1-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xfce4-power-manager 1.6.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jul 25 21:10:33 2018
  InstallationDate: Installed on 2017-05-13 (438 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: xfce4-power-manager
  UpgradeStatus: Upgraded to bionic on 2018-07-16 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1783637/+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 1760068] Re: Wrong resolution at unlock screen

A new version of nvidia-graphics-drivers-340 is available in -updates.

Please check if it resolves the bug.

https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-340/340.107-0ubuntu0.18.04.1

** Changed in: light-locker (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Wrong resolution at unlock screen

Status in light-locker package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  After coming out of suspend - the unlock screen is at 640x480
  resolution.

  Expect to see unlock screen at 1920x1080 resolution.

  Using nvidia-340.

  Previously tested using nouveau driver where resolution at unlock
  screen was correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-locker 1.8.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 30 11:31:20 2018
  InstallationDate: Installed on 2017-09-02 (209 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1760068/+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 1802200] Re: /usr/bin/file-roller:11:g_list_foreach:_g_string_list_free:_fr_window_ask_overwrite_dialog:query_info_ready_for_overwrite_dialog_cb:g_simple_async_result_complete

There is no report since 17.10, considering that one as fixed, the
number of report is rather low on xenial too so not a candidate to SRU
there

** Changed in: file-roller (Ubuntu)
   Importance: Undecided => Low

** Changed in: file-roller (Ubuntu)
   Status: New => Fix Released

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

Title:
  /usr/bin/file-
  
roller:11:g_list_foreach:_g_string_list_free:_fr_window_ask_overwrite_dialog:query_info_ready_for_overwrite_dialog_cb:g_simple_async_result_complete

Status in file-roller package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
file-roller.  This problem was most recently seen with package version 
3.22.3-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/de2163c7e1ac3121ceee359e1cc10fe3bb471d7c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1802200/+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 1775280] Re: The second user cannot start their session, login screen has low resolution

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

** This bug has been marked a duplicate of bug 1760068
   Wrong resolution at unlock screen

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

Title:
  The second user cannot start their session, login screen has low
  resolution

Status in lightdm package in Ubuntu:
  New

Bug description:
  The first user can start their session successfully with autologin.
  When I try to switch to the second user, the login screen has very low
  resolution and it cannot start the secondary user session. I tried to
  change the value of the autologin user, than the other user session
  start well, but the original user session failed. That's why I think
  this is not a user related error, always the second user session fail,
  does not matter which one is the first user. The only differences
  between the default settings that passwordless login switch on the pam
  config and use nvidia-340 driver instead of noveau. The strange thing
  that this lightdm config works well with noveau driver, the problem
  with noveau driver that the video playing freeze the computer.
  Previously lightdm and nvidia driver work well on 16.04. This is a
  clean install not an upgrade from 16.04. I think the problem somewhere
  virtual X terminals handled by ligthDm.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Tue Jun  5 23:07:11 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-27 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.pam.d.lightdm: 2018-05-27T21:23:23.664631

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1775280/+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 1802313] Re: Update gnome-control-center to 3.30.2

2018-11-08 Thread Andrea Azzarone

** Merge proposal linked:
   
https://code.launchpad.net/~azzar1/ubuntu/+source/gnome-control-center/+git/gnome-control-center/+merge/358511

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

Title:
  Update gnome-control-center to 3.30.2

Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  Merge with Debian Unstable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1802313/+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 1709194] Re: Power notification appears with no detail

Upstream is working on fixing that issue now, discussions on
https://gitlab.gnome.org/GNOME/gnome-shell/issues/726

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

Title:
  Power notification appears with no detail

Status in GNOME Settings Daemon:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  I locked my laptop screen. Some time later a notification appeared
  (see screenshot).

  "Power"
  "1 new notification"

  If I move the mouse the notification disappears. If I unlock the
  laptop there are no notifications pending anywhere. I have no idea
  where this text comes from or what it means. Is my battery low? is it
  full? Is there some other issue?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-power-manager 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug  7 23:26:58 2017
  InstallationDate: Installed on 2017-08-02 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1709194/+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 1801380] Re: Right side of window and menu area is duplicated every time on first run

2018-11-08 Thread spm2011

Happened again, this time when opening firefox right after gnome-
terminal was opened and moved to the right side of the screen. The
terminal window portion can be seen in the firefox window area.

Dragging and remaximising Firefox fixed the window.

** Attachment added: "ff_terminal_right_window.png"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1801380/+attachment/5210376/+files/ff_terminal_right_window.png

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

Title:
  Right side of window and menu area is duplicated every time on first
  run

Status in firefox package in Ubuntu:
  New

Bug description:
  Every time I open Firefox with previous session tabs the first time
  right after logging in, the usable portion of the window is shrunk,
  and the right side of the window with the last tab, menus, and
  extension icons is duplicated on the right side of the window. (See
  screenshot)

  Closing and reopening Firefox almost always fixes the issue. I may
  have had this happen once on a non-first run after resuming.

  Started happening recently I think in 62.0.3

  
  Expected: Window opens normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 63.0+build2-0ubuntu0.18.04.2
  ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1745 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1745 F pulseaudio
  BuildID: 20181023214826
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  2 10:55:29 2018
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-09-12 (50 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.224 metric 
600
  MostRecentCrashID: bp-5252eef0-71dd-4e49-8315-64d660180929
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=63.0/20181023214826 (In use)
   Profile1 - LastVersion=62.0/20180913170346 (Out of date)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-5252eef0-71dd-4e49-8315-64d660180929
   bp-57477e57-d8dd-4ea9-ba66-270d80180929
   bp-821e4afc-cb3c-4fe2-a7ba-586440180929
   bp-8b4ffe0f-54ef-4969-b8fa-7d6bd0180929
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (34 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd07/09/2018:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3340
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1801380/+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 1028267] Re: thunderbird license change not reflected in /usr/share/doc/thunderbird/copyright

2018-11-08 Thread C de-Avillez

marking as Low per request.

** Changed in: thunderbird (Ubuntu)
   Importance: Undecided => Low

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

Title:
  thunderbird license change not reflected in
  /usr/share/doc/thunderbird/copyright

Status in Mozilla Thunderbird:
  Unknown
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Now that thunderbird (and firefox, see
  https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1028266) have
  switched from the MPLv1/GPL/LGPL tri-license to MPL 2.0,
  /usr/share/doc/thunderbird/copyright should reflect this. Also,
  /usr/share/doc/thunderbird/MPL.gz should be updated, or removed if the
  MPL 2.0 would be included in /usr/share/doc/thunderbird/copyright.

  Also, based on a quick look, the license list in this file seem to
  lack quite a few of the licenses in the list one can see at
  about:license (help -> about thunderbird -> licensing information).

  This is for thunderbird 14.0 in Ubuntu 10.04 and 12.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1028267/+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 1181708] Re: HP Laserjet Pro MFP M225dn, duplex printing, prints too many copies.

2018-11-08 Thread C de-Avillez

Marking Truiaged/Low per request from gf at #ubuntu-bugs.

** Changed in: system-config-printer (Ubuntu)
Importance: Undecided => Low

** Changed in: system-config-printer (Ubuntu)
Status: New => Triaged

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

Title:
HP Laserjet Pro MFP M225dn, duplex printing, prints too many copies.

Status in system-config-printer package in Ubuntu:
Triaged

Bug description:
Duplex printing doesn't work when printing multiple copies of a single
page.

This has been verified printing pdfs from Okular and Firefox, text
files from Geddit, and html pages from Firefox. Behaviour same in all
cases.

E.g.

Duplex printing works correctly with the following options in the
system-config-printer dialogue:

Range - Page(s): 1-2
Copies: 1
Duplex option: Long-edge

Result > prints two pages on one sheet of paper.

Duplex printing does not work with the following options in the
system-config-printer dialogue:

Range - Page(s): 1
Copies: 2
Duplex option: Long-edge

Result > prints two pages on two sheets of paper
Expected result > two pages on one sheet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1181708/+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 1641423] Re: Backup fails with message: 'Failed to execute child process "duplicity" (No such file or directory)' or 'No module named gi.repository': missing deja-dup-backend-g

2018-11-08 Thread vkapas

Bug marked is fixing but still reproduced in 16.04 with last updates.

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

Title:
  Backup fails with message: 'Failed to execute child process
  "duplicity" (No such file or directory)' or 'No module named
  gi.repository': missing deja-dup-backend-gvfs, duplicity, and/or
  python-gi packages

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  Ubantu 16.04

  Cant find out version of backup but it was loaded with distro 16.04
  and all software is up to date so it should be latest

  I dont know how to get the information
   in 3 & 4

  from the error maessage:
  Failed to execute child process "duplicity" (No such file or directory)
  It looks like a required file is missing

  I tried removing backup and reinstalling but it still fails with the
  same error

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1641423/+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 1225629] Re: shotwell crashed with SIGSEGV in publishing_accounts_uoa_publisher_authenticator_on_processed()

the uoa support got removed in
https://launchpad.net/ubuntu/+source/shotwell/0.26.1-0ubuntu1

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

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

Title:
  shotwell crashed with SIGSEGV in
  publishing_accounts_uoa_publisher_authenticator_on_processed()

Status in shotwell package in Ubuntu:
  Invalid

Bug description:
  Shotwell crashed when attempting to publish photos to Facebook.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: shotwell 0.15.0~pr1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: amd64
  Date: Sun Sep 15 16:28:25 2013
  ExecutablePath: /usr/bin/shotwell
  InstallationDate: Installed on 2013-08-16 (29 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130815)
  MarkForUpload: True
  ProcCmdline: shotwell
  SegvAnalysis:
   Segfault happened at: 0x7f8481617d3a:mov(%rax),%rax
   PC (0x7f8481617d3a) ok
   source "(%rax)" (0x3802432e) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: shotwell
  StacktraceTop:
   ?? () from /usr/lib/shotwell/plugins/builtin/shotwell-publishing.so
   ?? () from /usr/lib/shotwell/plugins/builtin/shotwell-publishing.so
   ?? () from /usr/lib/x86_64-linux-gnu/libsignon-glib.so.1
   g_simple_async_result_complete () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: shotwell crashed with SIGSEGV in g_simple_async_result_complete()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1225629/+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 1802313] [NEW] Update gnome-control-center to 3.30.2

2018-11-08 Thread Andrea Azzarone

Public bug reported:

Merge with Debian Unstable.

** Affects: gnome-control-center (Ubuntu)
 Importance: Medium
 Assignee: Andrea Azzarone (azzar1)
 Status: In Progress


** Tags: upgrade-software-version

** Changed in: gnome-control-center (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

** Changed in: gnome-control-center (Ubuntu)
   Importance: Wishlist => Medium

** Changed in: gnome-control-center (Ubuntu)
   Status: New => In Progress

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

Title:
  Update gnome-control-center to 3.30.2

Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  Merge with Debian Unstable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1802313/+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 1190018] Re: Shotwell shouldn't hard-depend on UOA