date:20180525

** Tags added: latest-bios-a15 regression-release

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

Title:
  X display is black after 18.04 upgrade from 17.10

Status in xorg package in Ubuntu:
  New

Bug description:
  I can manually start lightdm, and that will give me a login screen,

  Unfortunately, most of the desktop environments crash after login.

  Only plasma gives me a little bit of clients, though even plasma
  complains

  All shell packages missing
  And
  Vboxclient warning

  Under 17.10, I successfully used Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Wed May  9 19:15:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:0665]
  InstallationDate: Installed on 2015-05-18 (1087 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash 
i915.i915_enable_rc6=1 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell 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.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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/+bug/1770306/+subscriptions

-- 
Mailing list: https://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 1773485] [NEW] Supplement to 1772...@bugs.launchpad.net,

2018-05-25 Thread Roger Davis

Public bug reported:

Supplement to 1772...@bugs.launchpad.net,

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-43-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri May 25 22:06:57 2018
DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
InstallationDate: Installed on 2014-07-07 (1418 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic 
root=UUID=3d311d21-7c70-432e-a4ac-d9dd4986a2b5 ro plymouth:debug=1 splash quiet 
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-12-18 (524 days ago)
dmi.bios.date: 02/08/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904
dmi.board.name: DZ77BH-55K
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG39008-400
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:
dmi.product.family: To be filled by O.E.M.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Fri May 25 22:03:00 2018
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.5-0ubuntu2~16.04.1

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  Supplement to 1772...@bugs.launchpad.net,

Status in xorg package in Ubuntu:
  New

Bug description:
  Supplement to 1772...@bugs.launchpad.net,

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri May 25 22:06:57 2018
  DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
  InstallationDate: Installed on 2014-07-07 (1418 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic 
root=UUID=3d311d21-7c70-432e-a4ac-d9dd4986a2b5 ro plymouth:debug=1 splash quiet 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-12-18 (524 days ago)
  dmi.bios.date: 02/08/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904
  dmi.board.name: DZ77BH-55K
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG39008-400
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04

[Desktop-packages] [Bug 1770374] Re: My login screen stays black

Dieter Meyer, thank you for reporting this and helping make Ubuntu
better.

1) Is this something that started to happen after an update? If so,
which and when precisely?

2) Regarding the kernel you are using (4.13.0-37.42-generic 4.13.13) it
appears you are manually booting this or have it pinned. Could you
please update to a supported kernel (4.15.x) and advise to the results?

3) If you disable the nvidia card in your BIOS, does this provide a
WORKAROUND?

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Medium

** Changed in: xorg (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/1770374

Title:
  My login screen stays black

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I can't login to my desktop cause my login screen is black. So I read
  on the forums that you could bypass the login screen by typing startx
  in the tty screen but that also doesn't work please could help me.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May 10 12:02:11 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.13.0-38-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer 2nd Generation Core Processor Family 
Integrated Graphics Controller [1558:2500]
   NVIDIA Corporation GF108M [GeForce GT 520M] [10de:0ded] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: CLEVO/KAPOK Computer GF108M [GeForce GT 520M] [1558:2500]
  InstallationDate: Installed on 2018-02-27 (72 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20180105.2)
  MachineType: GIGABYTE Q1532N
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=8f567cdc-b8e0-4a0f-b10b-1104f687f111 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Q1532N
  dmi.board.vendor: GIGABYTE
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: GIGABYTE
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/15/2011:svnGIGABYTE:pnQ1532N:pvrN/A:rvnGIGABYTE:rnQ1532N:rvrN/A:cvnGIGABYTE:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Q1532N
  dmi.product.version: N/A
  dmi.sys.vendor: GIGABYTE
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  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/+bug/1770374/+subscriptions

-- 
Mailing list: https://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 1773198] Re: Sound volume for applications can become locked below global output volume.

Yes, I know that you can change the volume on a per-application basis.

The report is about applications being uncoupled from the master volume
setting through use of the volume control on a different application,
and then having the range of volume being limited below 100%.

Using the per-application volume settings is how you recover, but
recovery should not be necessary in the first place. It's not how Ubuntu
used to work before 18.04, it's unintuitive, and it's not at all obvious
what has happened.

Again, I don't think this is a bug in Totem, and I don't think the
things I was asked to add to the report serve any function besides
violating my privacy. But here you go.

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

Title:
  Sound volume for applications can become locked below global output
  volume.

Status in totem package in Ubuntu:
  New

Bug description:
  Normal behavior, as far as I understand, is for all applications to
  have the same sound volume unless you lower the volume for one
  manually in the applications section of the sound settings. However,
  some applications have their own own volume control that only affect
  the volume of themselves and the global output volume, not other
  applications. This can put those other applications below the global
  volume where they become stuck.

  An example: you have the output volume at 50%. Rhythmbox is locked to
  output volume and is also at 50%. Then you open a movie in totem.
  Sound volume is low for that movie so you use totem's volume slider to
  increase volume to 100%. When done you close totem and use the media
  keys on the keyboard to lower the volume back to 50%. Since rhythmbox
  stayed at 50% instead of following to 100%, it got stuck at half of
  global volume and after lowering is now down to 25%. It can never go
  above 50% with just the normal volume controls, you need to go into
  the applications section of the sound menu and move its volume slider
  to reset it to the same value as the global output volume.

  This is especially a problem since you might increase the global
  volume a lot in order to compensate for low volume, only for a newly
  opened application to start playing sound at way too high a volume, a
  danger to your ears and possibly your sound hardware. And a novice
  user is likely to not understand what's wrong with their audio all of
  a sudden, and feel forced to reboot to fix it.

  The same thing happens with the volume control in vlc so it's not just totem.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-02 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 
livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ nvidia_modeset nvidia
  Package: totem 3.26.0-0ubuntu6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-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/totem/+bug/1773198/+subscriptions

-- 
Mailing list: https://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 1755555] Re: nautilus crashed with SIGSEGV while trying to install Budgie Desktop applet

[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/175

Title:
  nautilus crashed with SIGSEGV  while trying to install Budgie Desktop
  applet

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  This problem happens on Ubuntu Budgie 18.04 when first time in session
  I try to install applet using Budgie Desktop Applets. Seems like it
  only happens when installing Global menu applet (budgie-appmenu-
  applet) which afterwards also does not show up in applet list, though
  apt says it installed. But Pixel Saver applet (budgie-pixel-saver-
  applet) which has similar functionality installs without any problems
  and works fine.

  Release:  18.04
  Description:  Ubuntu Bionic Beaver (development branch)

  budgie-appmenu-applet:
Installed: 0.6.92+repack1-3ubuntu1

  budgie-pixel-saver-applet:
Installed: 4.0+git20171102.30c1f94-0ubuntu1~bionic

  nautilus:
Installed: 1:3.26.2-0ubuntu3.1

  
  I should also mention that I could not login and got freezes after 
installation without nomodeset because of Nvidia drivers. I installed 
nvidia-384 driver and deleted xserver-xorg-video-nvidia-390 to fix these 
freezes and be able to login to desktop.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 13 19:11:31 2018
  Disassembly: No registers.
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+108+80'"
   b'org.gnome.nautilus.desktop' b'network-icon-visible' b'true'
   b'org.gnome.nautilus.desktop' b'volumes-visible' b'true'
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
  InstallationDate: Installed on 2018-03-12 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180312)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  Registers: The program has no registers now.
  SegvAnalysis: Failure: invalid literal for int() with base 16: 'program'
  Signal: 11
  SourcePackage: nautilus
  Stacktrace: No stack.
  StacktraceTop:
   
  ThreadStacktrace:
   
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  usr_lib_nautilus:

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

-- 
Mailing list: https://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 1691935] Re: Resuming from suspend requires no password

I haven't tested this in a long time.

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

Title:
  Resuming from suspend requires no password

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Resuming from suspend requires no password.

  Perhaps because we don't use gdm?

  Test case:
1. Click the power menu
2. Hold down Alt so the power button changes to a pause button.
3. Click it to suspend the system
4. Wake the system

  Expected: A password prompt
  Observed: My original desktop fully unlocked

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  Date: Fri May 19 13:28:57 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (16 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  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/1691935/+subscriptions

-- 
Mailing list: https://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 508959] Re: should start playing on enter after search

** Changed in: rhythmbox
   Status: New => Expired

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

Title:
  should start playing on enter after search

Status in Rhythmbox:
  Expired
Status in rhythmbox package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: rhythmbox

  When a particular song is entered in the "Search:" field and only one
  song is found with this title, it would be nice the song to be started
  directly with a single "Enter" key hit.

  ProblemType: Bug
  Architecture: amd64
  Date: Mon Jan 18 02:40:47 2010
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/rhythmbox
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  Package: rhythmbox 0.12.5-0ubuntu5.1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
  SourcePackage: rhythmbox
  Uname: Linux 2.6.31-17-generic x86_64

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

-- 
Mailing list: https://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 1731773] Re: Nautilus crashes when expanding folder after search

[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/1731773

Title:
  Nautilus crashes when expanding folder after search

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  This bug happens in Ubuntu 17.10 with Files (Nautilus) version 3.26.0.
  It did not happen in 17.04.

  - Make sure that in settings the setting "Allow folders to be expanded" is 
switched on.
  - Search for files and folders and make sure the result list contains folders.
  - Expand a folder with the arrow in front of the folder.
  - The application crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 12 17:50:04 2017
  InstallationDate: Installed on 2016-10-30 (377 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to artful on 2017-10-22 (21 days ago)

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

-- 
Mailing list: https://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 1755800] Re: Greeter/lockscreen fails to authenicate in an endless loop

[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/1755800

Title:
  Greeter/lockscreen fails to authenicate in an endless loop

Status in gdm3 package in Ubuntu:
  Expired

Bug description:
  After a recent install of the 18.04 (why is a separate story), I
  notice that after some number of successful screen locks, I become
  locked out of the desktop with an authentication failure.  During
  those unsuccessful attempts to log in, syslog shows:

  Mar 13 22:46:04 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"21"
  Mar 13 22:46:04 magpie kernel: [83554.367969] rfkill: input handler enabled
  Mar 13 22:46:04 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event2  - 
Power B
  utton: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"25"
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event4  - 
Video B
  us: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"27"
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event1  - 
Sleep B
  utton: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"24"
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event17 - 
Integra
  ted Camera: Integrated C: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"29"
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event3  - AT 
Tran
  slated Set 2 keyboard: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"28"
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event5  - 
SynPS/2 Synaptics TouchPad: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"30"
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event6  - 
TPPS/2 IBM TrackPoint: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"62"
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event7  - 
ThinkPad Extra Buttons: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) AIGLX: 
Suspending AIGLX clients for VT switch
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) 
systemd-logind: got pause for 13:81
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) 
systemd-logind: got pause for 13:68
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) 
systemd-logind: got pause for 226:0
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) 
systemd-logind: got pause for 13:71
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) 
systemd-logind: got pause for 13:66

  one new line for each attempted log in.  This is occurring once or
  twice a day.  Sometimes, it works again.  Last time, I needed to
  reboot.

  Since this is a fresh install, albeit with my desktop files being
  restored via CrashPlan (which could be part of the problem?), I
  thought that this warranted a report.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 14 07:58:11 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-03-12 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180114)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1773198] Re: Sound volume for applications can become locked below global output volume.

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

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

Title:
  Sound volume for applications can become locked below global output
  volume.

Status in totem package in Ubuntu:
  New

Bug description:
  Normal behavior, as far as I understand, is for all applications to
  have the same sound volume unless you lower the volume for one
  manually in the applications section of the sound settings. However,
  some applications have their own own volume control that only affect
  the volume of themselves and the global output volume, not other
  applications. This can put those other applications below the global
  volume where they become stuck.

  An example: you have the output volume at 50%. Rhythmbox is locked to
  output volume and is also at 50%. Then you open a movie in totem.
  Sound volume is low for that movie so you use totem's volume slider to
  increase volume to 100%. When done you close totem and use the media
  keys on the keyboard to lower the volume back to 50%. Since rhythmbox
  stayed at 50% instead of following to 100%, it got stuck at half of
  global volume and after lowering is now down to 25%. It can never go
  above 50% with just the normal volume controls, you need to go into
  the applications section of the sound menu and move its volume slider
  to reset it to the same value as the global output volume.

  This is especially a problem since you might increase the global
  volume a lot in order to compensate for low volume, only for a newly
  opened application to start playing sound at way too high a volume, a
  danger to your ears and possibly your sound hardware. And a novice
  user is likely to not understand what's wrong with their audio all of
  a sudden, and feel forced to reboot to fix it.

  The same thing happens with the volume control in vlc so it's not just totem.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-02 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 
livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ nvidia_modeset nvidia
  Package: totem 3.26.0-0ubuntu6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-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/totem/+bug/1773198/+subscriptions

-- 
Mailing list: https://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 1770479] Re: No graphics on dell xps 15 (nvidia GeForce GTX 1050 Mobile)

gmc, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770479/comments/3
regarding this being resolved by a reinstall. For future reference you
can manage the status of your own bugs by clicking on the current status
in the yellow line and then choosing a new status in the revealed drop
down box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

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

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

Title:
  No graphics on dell xps 15 (nvidia GeForce GTX 1050 Mobile)

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I had ubuntu 17.10 running on my dell xps 15, which worked fine for
  months. Today I made the mistake of upgrading to 18.04, and now I am
  not getting any graphics anymore with the nvidia driver.

  With the nouveau driver I do get a login screen (display manager), but
  logging in just returns me to the login screen (tried with default
  session, mate, plasma and xmonad).

  I tried installing older nvidia drivers (nvidia-384, nvidia-375,
  nvidia-361) but it made no difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu May 10 21:11:03 2018
  DistUpgraded: 2018-05-10 19:48:11,589 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
   virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07be]
 Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
  InstallationDate: Installed on 2017-12-16 (144 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=14e82bfb-9693-4da5-b107-280aeda9478e ro quiet splash 
nouveau.modeset=0 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (0 days ago)
  dmi.bios.date: 12/15/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell 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.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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/+bug/1770479/+subscriptions

-- 
Mailing list: https://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 1756559] Re: No status indicator for File Copy and/or Moves

[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/1756559

Title:
  No status indicator for File Copy and/or Moves

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Nautilus does not show a status indicator when the user is copying or moving 
a file from an NAS device to their local disk.
  This is very important to have, as the user risks data loss or corruption if 
not done correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-lowlatency 4.13.13
  Uname: Linux 4.13.0-37-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 17 11:10:31 2018
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1771062] Re: LG 27UK650 Monitor Won't Come Back On After Inactivity Turn Off

Lonnie Lee Best, thank you for reporting this and helping make Ubuntu
better.

1) Is this something that started to happen after an update? If so,
which and when precisely?

2) To clarify, could you please describe how your computer is connected
to monitor (e.g. using a HDMI cord connecting both, using a
dongle/adapter, etc.)?

3) Regarding the use of kernel boot parameter acpi_backlight=vendor is
this required? If you remove it, is this issue still reproducible?

4) If you remove the nvidia drivers and use nouveau, is this
reproducible?

5) As per nvidia.com the latest driver version available for your card
is 390.59. hence, to see if this is already resolved in Ubuntu, could
you please test http://cdimage.ubuntu.com/daily-live/current/ and advise
to the results?

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

** Changed in: xorg (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/1771062

Title:
  LG 27UK650 Monitor Won't Come Back On After Inactivity Turn Off

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After Ubuntu 16.04.4 turns off my monitor (due to inactivity timeout),
  I cannot get it to come back on without rebooting.

  Monitor: LG 27UK650
  Specs:   
http://www.lg.com/us/support/products/documents/27UK650-W%20Spec%20Sheet.pdf

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  BootLog:

  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon May 14 01:15:22 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-41-generic, x86_64: installed
   nvidia-384, 384.111, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.1.34, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.1.34, 4.4.0-124-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation Device [10de:1be1] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:087a]
  InstallationDate: Installed on 2018-05-12 (2 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: System76 Bonobo WS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed 
root=UUID=905343e7-683c-43f3-9ee8-b5e8909f865b ro acpi_backlight=vendor quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RSA5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Bonobo WS
  dmi.board.vendor: System76
  dmi.board.version: bonw13
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Bonobo WS
  dmi.product.version: bonw13
  dmi.sys.vendor: System76
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon May 14 01:02:31 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.19.5-0ubuntu2~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad

[Desktop-packages] [Bug 1758874] Re: package libxfont1:i386 1:1.5.1-1 [modified: usr/lib/i386-linux-gnu/libXfont.so.1.4.1 usr/share/doc/libxfont1/changelog.Debian.gz] failed to install/upgrade: packag

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

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

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

Title:
  package libxfont1:i386 1:1.5.1-1 [modified: usr/lib/i386-linux-
  gnu/libXfont.so.1.4.1 usr/share/doc/libxfont1/changelog.Debian.gz]
  failed to install/upgrade: package libxfont1:i386 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in libxfont package in Ubuntu:
  Expired

Bug description:
  Hi,
  I'm new to Ubuntu, however I suspect though the error might be due to the age 
and spec of the PC I installed Ubuntu on.
  Thanks
  Tim

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libxfont1:i386 1:1.5.1-1 [modified: 
usr/lib/i386-linux-gnu/libXfont.so.1.4.1 
usr/share/doc/libxfont1/changelog.Debian.gz]
  ProcVersionSignature: hostname 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2
  AptOrdering:
   libmircommon5: Remove
   libwacom-bin: Remove
   libxfont1: Configure
   xserver-xorg-core: Configure
   NULL: ConfigurePending
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Mar 26 10:03:44 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DuplicateSignature:
   Processing triggers for libc-bin (2.23-0ubuntu10) ...
   dpkg: error processing package libxfont1:i386 (--configure):
package libxfont1:i386 is not ready for configuration
  ErrorMessage: package libxfont1:i386 is not ready for configuration  cannot 
configure (current status 'half-installed')
  GraphicsCard:
   Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics 
Device [8086:2562] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: IBM NetVista A30p [1014:0267]
  InstallationDate: Installed on 2018-03-12 (13 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=c675b7f0-8dcd-4d78-a89e-520ae4314f43 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.10ubuntu1
  SourcePackage: libxfont
  Title: package libxfont1:i386 1:1.5.1-1 [modified: 
usr/lib/i386-linux-gnu/libXfont.so.1.4.1 
usr/share/doc/libxfont1/changelog.Debian.gz] failed to install/upgrade: package 
libxfont1:i386 is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/10/2005
  dmi.bios.vendor: IBM
  dmi.bios.version: 24KT55AUS
  dmi.board.name: IBM
  dmi.chassis.vendor: IBM
  dmi.modalias: 
dmi:bvnIBM:bvr24KT55AUS:bd05/10/2005:svnIBM:pn830321G:pvr:rvnIBM:rnIBM:rvr:cvnIBM:ct3:cvr:
  dmi.product.name: 830321G
  dmi.sys.vendor: IBM
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Mar 26 09:37:58 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   0 
   vendor NUL
  xserver.version: 2:1.18.4-0ubuntu0.7

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

-- 
Mailing list: https://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 1755800] Re: Greeter/lockscreen fails to authenicate in an endless loop

I'm a little rusty and lost now. Can you please reword the bug title to
better describe the problem, if any?

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

** Summary changed:

- Greeter/lockscreen fails to authenicate in an endless loop
+ Greeter/lockscreen fails to authenicate in an endless loop. Repeated "No 
space left on device" errors and strange swap file configuration

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

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

Title:
  Greeter/lockscreen fails to authenicate in an endless loop. Repeated
  "No space left on device" errors and strange swap file configuration

Status in gdm3 package in Ubuntu:
  Incomplete

Bug description:
  After a recent install of the 18.04 (why is a separate story), I
  notice that after some number of successful screen locks, I become
  locked out of the desktop with an authentication failure.  During
  those unsuccessful attempts to log in, syslog shows:

  Mar 13 22:46:04 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"21"
  Mar 13 22:46:04 magpie kernel: [83554.367969] rfkill: input handler enabled
  Mar 13 22:46:04 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event2  - 
Power B
  utton: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"25"
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event4  - 
Video B
  us: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"27"
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event1  - 
Sleep B
  utton: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"24"
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event17 - 
Integra
  ted Camera: Integrated C: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"29"
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event3  - AT 
Tran
  slated Set 2 keyboard: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"28"
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event5  - 
SynPS/2 Synaptics TouchPad: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"30"
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event6  - 
TPPS/2 IBM TrackPoint: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"62"
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event7  - 
ThinkPad Extra Buttons: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) AIGLX: 
Suspending AIGLX clients for VT switch
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) 
systemd-logind: got pause for 13:81
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) 
systemd-logind: got pause for 13:68
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) 
systemd-logind: got pause for 226:0
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) 
systemd-logind: got pause for 13:71
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) 
systemd-logind: got pause for 13:66

  one new line for each attempted log in.  This is occurring once or
  twice a day.  Sometimes, it works again.  Last time, I needed to
  reboot.

  Since this is a fresh install, albeit with my desktop files being
  restored via CrashPlan (which could be part of the problem?), I
  thought that this warranted a report.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 14 07:58:11 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-03-12 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180114)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1771111] Re: Freezes on Thinkpad R500

Michal, thank you for reporting this and helping make Ubuntu better.

1) Is this something that started to happen after an update? If so,
which and when precisely?

2) After the freezes, are there any crash files in the /var/crash
folder?

3) How often do the freezes occur?

4) To see if this is already resolved in Ubuntu, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

** Tags added: bios-outdated-3.20

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

** Changed in: xorg (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/177

Title:
  Freezes on Thinkpad R500

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Problem with black boxes on screen, freezing mouse, random freezes
  (1-2s).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  BootLog: /dev/sda1: clean, 586416/5447680 files, 15738435/21777920 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 14 14:36:13 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e5]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e5]
  InstallationDate: Installed on 2017-11-12 (182 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 271434G
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic 
root=UUID=0b74ca14-9767-4eca-95ac-fcbedc338d77 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7YET50WW (1.20 )
  dmi.board.name: 271434G
  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:bvr7YET50WW(1.20):bd10/30/2008:svnLENOVO:pn271434G:pvrThinkPadR500:rvnLENOVO:rn271434G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad R500
  dmi.product.name: 271434G
  dmi.product.version: ThinkPad R500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  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/ubuntu/+source/xorg/+bug/177/+subscriptions

-- 
Mailing list: https://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 1719678] Re: screen lock does not go off after resume from suspend

Being fixed in bug 1768786.

** This bug has been marked a duplicate of bug 1768786
   Lock screen is displayed when resuming from suspend

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

Title:
  screen lock does not go off after resume from suspend

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Not always reproducible, sometimes, screen lock doesn't go off when
  the device resumes from suspend.

  A reboot does not fix the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 26 12:11:12 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2013-09-03 (1483 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  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/1719678/+subscriptions

-- 
Mailing list: https://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 1773198] GstreamerVersions.txt

apport information

** Attachment added: "GstreamerVersions.txt"
   
https://bugs.launchpad.net/bugs/1773198/+attachment/517/+files/GstreamerVersions.txt

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

Title:
  Sound volume for applications can become locked below global output
  volume.

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Normal behavior, as far as I understand, is for all applications to
  have the same sound volume unless you lower the volume for one
  manually in the applications section of the sound settings. However,
  some applications have their own own volume control that only affect
  the volume of themselves and the global output volume, not other
  applications. This can put those other applications below the global
  volume where they become stuck.

  An example: you have the output volume at 50%. Rhythmbox is locked to
  output volume and is also at 50%. Then you open a movie in totem.
  Sound volume is low for that movie so you use totem's volume slider to
  increase volume to 100%. When done you close totem and use the media
  keys on the keyboard to lower the volume back to 50%. Since rhythmbox
  stayed at 50% instead of following to 100%, it got stuck at half of
  global volume and after lowering is now down to 25%. It can never go
  above 50% with just the normal volume controls, you need to go into
  the applications section of the sound menu and move its volume slider
  to reset it to the same value as the global output volume.

  This is especially a problem since you might increase the global
  volume a lot in order to compensate for low volume, only for a newly
  opened application to start playing sound at way too high a volume, a
  danger to your ears and possibly your sound hardware. And a novice
  user is likely to not understand what's wrong with their audio all of
  a sudden, and feel forced to reboot to fix it.

  The same thing happens with the volume control in vlc so it's not just totem.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-02 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 
livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ nvidia_modeset nvidia
  Package: totem 3.26.0-0ubuntu6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-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/totem/+bug/1773198/+subscriptions

-- 
Mailing list: https://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 1768786] Re: Desktop is displayed when resuming from suspend

Is this related to bug 1730543?

** Summary changed:

- Lock screen is displayed when resuming from suspend
+ Desktop is displayed when resuming from suspend

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

Title:
  Desktop is displayed when resuming from suspend

Status in budgie-desktop package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  In Progress
Status in ubuntu-unity-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce and description:

  First test case - where things work correctly:

  1.  Open Settings-> Privacy and make sure that Automatic screen lock is ON.
  2.  Suspend your machine
  3.  Resume your machine
  4.  Notice that the lockscreen is shown on resume and that you can't see the 
desktop

  Second test case - where things are broken

  1.  Open Settings -> Privacy and make sure that Automatic screen lock is OFF.
  2.  Suspend your machine
  3.  Resume your machine
  4.  Notice that the desktop is visible for a second, then the screen blanks, 
then the lock screen appears, then the screen blanks again.  You are left at a 
black screen and need to unlock.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1768786/+subscriptions

-- 
Mailing list: https://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 1773198] XorgLog.txt

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1773198/+attachment/5144450/+files/XorgLog.txt

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

Title:
  Sound volume for applications can become locked below global output
  volume.

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Normal behavior, as far as I understand, is for all applications to
  have the same sound volume unless you lower the volume for one
  manually in the applications section of the sound settings. However,
  some applications have their own own volume control that only affect
  the volume of themselves and the global output volume, not other
  applications. This can put those other applications below the global
  volume where they become stuck.

  An example: you have the output volume at 50%. Rhythmbox is locked to
  output volume and is also at 50%. Then you open a movie in totem.
  Sound volume is low for that movie so you use totem's volume slider to
  increase volume to 100%. When done you close totem and use the media
  keys on the keyboard to lower the volume back to 50%. Since rhythmbox
  stayed at 50% instead of following to 100%, it got stuck at half of
  global volume and after lowering is now down to 25%. It can never go
  above 50% with just the normal volume controls, you need to go into
  the applications section of the sound menu and move its volume slider
  to reset it to the same value as the global output volume.

  This is especially a problem since you might increase the global
  volume a lot in order to compensate for low volume, only for a newly
  opened application to start playing sound at way too high a volume, a
  danger to your ears and possibly your sound hardware. And a novice
  user is likely to not understand what's wrong with their audio all of
  a sudden, and feel forced to reboot to fix it.

  The same thing happens with the volume control in vlc so it's not just totem.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-02 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 
livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ nvidia_modeset nvidia
  Package: totem 3.26.0-0ubuntu6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-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/totem/+bug/1773198/+subscriptions

-- 
Mailing list: https://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 1719678] Re: screen lock does not go off after resume from suspend

Sorry. Bad wording in that bug. Not a duplicate.

** This bug is no longer a duplicate of bug 1768786
   Desktop is displayed when resuming from suspend

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

Title:
  screen lock does not go off after resume from suspend

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Not always reproducible, sometimes, screen lock doesn't go off when
  the device resumes from suspend.

  A reboot does not fix the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 26 12:11:12 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2013-09-03 (1483 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  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/1719678/+subscriptions

-- 
Mailing list: https://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 1773311] Re: Screen blanks a few seconds after resuming from suspend

Or a duplicate of bug 1719678?

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

Title:
  Screen blanks a few seconds after resuming from suspend

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After resuming from suspend screen blanking goes off after a few
  seconds even if the timeout is disabled or set to several minutes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 25 08:26:42 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-07-15 (1409 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to cosmic on 2018-03-24 (61 days ago)

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

-- 
Mailing list: https://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 1773198] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1773198/+attachment/519/+files/ProcEnviron.txt

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

Title:
  Sound volume for applications can become locked below global output
  volume.

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Normal behavior, as far as I understand, is for all applications to
  have the same sound volume unless you lower the volume for one
  manually in the applications section of the sound settings. However,
  some applications have their own own volume control that only affect
  the volume of themselves and the global output volume, not other
  applications. This can put those other applications below the global
  volume where they become stuck.

  An example: you have the output volume at 50%. Rhythmbox is locked to
  output volume and is also at 50%. Then you open a movie in totem.
  Sound volume is low for that movie so you use totem's volume slider to
  increase volume to 100%. When done you close totem and use the media
  keys on the keyboard to lower the volume back to 50%. Since rhythmbox
  stayed at 50% instead of following to 100%, it got stuck at half of
  global volume and after lowering is now down to 25%. It can never go
  above 50% with just the normal volume controls, you need to go into
  the applications section of the sound menu and move its volume slider
  to reset it to the same value as the global output volume.

  This is especially a problem since you might increase the global
  volume a lot in order to compensate for low volume, only for a newly
  opened application to start playing sound at way too high a volume, a
  danger to your ears and possibly your sound hardware. And a novice
  user is likely to not understand what's wrong with their audio all of
  a sudden, and feel forced to reboot to fix it.

  The same thing happens with the volume control in vlc so it's not just totem.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-02 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 
livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ nvidia_modeset nvidia
  Package: totem 3.26.0-0ubuntu6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-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/totem/+bug/1773198/+subscriptions

-- 
Mailing list: https://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 1773198] Re: Sound volume for applications can become locked below global output volume.

apport information

** Tags added: apport-collected bionic

** Description changed:

  Normal behavior, as far as I understand, is for all applications to have
  the same sound volume unless you lower the volume for one manually in
  the applications section of the sound settings. However, some
  applications have their own own volume control that only affect the
  volume of themselves and the global output volume, not other
  applications. This can put those other applications below the global
  volume where they become stuck.
  
  An example: you have the output volume at 50%. Rhythmbox is locked to
  output volume and is also at 50%. Then you open a movie in totem. Sound
  volume is low for that movie so you use totem's volume slider to
  increase volume to 100%. When done you close totem and use the media
  keys on the keyboard to lower the volume back to 50%. Since rhythmbox
  stayed at 50% instead of following to 100%, it got stuck at half of
  global volume and after lowering is now down to 25%. It can never go
  above 50% with just the normal volume controls, you need to go into the
  applications section of the sound menu and move its volume slider to
  reset it to the same value as the global output volume.
  
  This is especially a problem since you might increase the global volume
  a lot in order to compensate for low volume, only for a newly opened
  application to start playing sound at way too high a volume, a danger to
  your ears and possibly your sound hardware. And a novice user is likely
  to not understand what's wrong with their audio all of a sudden, and
  feel forced to reboot to fix it.
  
- The same thing happens with the volume control in vlc so it's not just
- totem.
+ The same thing happens with the volume control in vlc so it's not just totem.
+ --- 
+ ApportVersion: 2.20.9-0ubuntu7
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-05-02 (23 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
+ LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
+ NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 
livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ nvidia_modeset nvidia
+ Package: totem 3.26.0-0ubuntu6
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
+ Tags:  bionic
+ Uname: Linux 4.15.0-20-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  Sound volume for applications can become locked below global output
  volume.

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Normal behavior, as far as I understand, is for all applications to
  have the same sound volume unless you lower the volume for one
  manually in the applications section of the sound settings. However,
  some applications have their own own volume control that only affect
  the volume of themselves and the global output volume, not other
  applications. This can put those other applications below the global
  volume where they become stuck.

  An example: you have the output volume at 50%. Rhythmbox is locked to
  output volume and is also at 50%. Then you open a movie in totem.
  Sound volume is low for that movie so you use totem's volume slider to
  increase volume to 100%. When done you close totem and use the media
  keys on the keyboard to lower the volume back to 50%. Since rhythmbox
  stayed at 50% instead of following to 100%, it got stuck at half of
  global volume and after lowering is now down to 25%. It can never go
  above 50% with just the normal volume controls, you need to go into
  the applications section of the sound menu and move its volume slider
  to reset it to the same value as the global output volume.

  This is especially a problem since you might increase the global
  volume a lot in order to compensate for low volume, only for a newly
  opened application to start playing sound at way too high a volume, a
  danger to your ears and possibly your sound hardware. And a novice
  user is likely to not understand what's wrong with their audio all of
  a sudden, and feel forced to reboot to fix it.

  The same thing happens with the volume control in vlc so it's not just totem.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-02 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Rele

[Desktop-packages] [Bug 1773198] ProcCpuinfoMinimal.txt

apport information

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

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

Title:
  Sound volume for applications can become locked below global output
  volume.

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Normal behavior, as far as I understand, is for all applications to
  have the same sound volume unless you lower the volume for one
  manually in the applications section of the sound settings. However,
  some applications have their own own volume control that only affect
  the volume of themselves and the global output volume, not other
  applications. This can put those other applications below the global
  volume where they become stuck.

  An example: you have the output volume at 50%. Rhythmbox is locked to
  output volume and is also at 50%. Then you open a movie in totem.
  Sound volume is low for that movie so you use totem's volume slider to
  increase volume to 100%. When done you close totem and use the media
  keys on the keyboard to lower the volume back to 50%. Since rhythmbox
  stayed at 50% instead of following to 100%, it got stuck at half of
  global volume and after lowering is now down to 25%. It can never go
  above 50% with just the normal volume controls, you need to go into
  the applications section of the sound menu and move its volume slider
  to reset it to the same value as the global output volume.

  This is especially a problem since you might increase the global
  volume a lot in order to compensate for low volume, only for a newly
  opened application to start playing sound at way too high a volume, a
  danger to your ears and possibly your sound hardware. And a novice
  user is likely to not understand what's wrong with their audio all of
  a sudden, and feel forced to reboot to fix it.

  The same thing happens with the volume control in vlc so it's not just totem.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-02 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 
livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ nvidia_modeset nvidia
  Package: totem 3.26.0-0ubuntu6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-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/totem/+bug/1773198/+subscriptions

-- 
Mailing list: https://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 1730543] Re: In gnome-shell, unlocking screen before suspend completes means no password is required on resume

Does bug 1768786 sound similar to you?

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

Title:
  In gnome-shell, unlocking screen before suspend completes means no
  password is required on resume

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Sometimes it can take gnome-shell a few seconds after the lock screen
  appears before suspend completes. If during this time you enter your
  password and unlock gnome-shell, upon resume there is no lock screen.
  Obviously this is a security issue, because your data is available to
  whoever resumes the PC.

  To do this, you have to manually suspend the machine (eg by locking
  the screen and then pressing the suspend icon). I often have to do
  this of another bug whereby gnome-shell doesn't always suspend when
  you close the laptop lid if there is an external monitor connected
  (often it just switches to using the external monitor as primary when
  you close the lid).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  Uname: Linux 4.14.0-rc8-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 08:59:31 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-16 (82 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-08-17 (82 days ago)

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

-- 
Mailing list: https://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 1773311] Re: Screen blanks a few seconds after resuming from suspend

Maybe related to bug 1727770?

** Summary changed:

- Screen blanking goes off after a few seconds
+ Screen blanks a few seconds after resuming from suspend

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

Title:
  Screen blanks a few seconds after resuming from suspend

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After resuming from suspend screen blanking goes off after a few
  seconds even if the timeout is disabled or set to several minutes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 25 08:26:42 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-07-15 (1409 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to cosmic on 2018-03-24 (61 days ago)

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

-- 
Mailing list: https://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 1768786] Re: Lock screen is displayed when resuming from suspend

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

** Changed in: budgie-desktop (Ubuntu)
   Status: New => Confirmed

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

Title:
  Desktop is displayed when resuming from suspend

Status in budgie-desktop package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  In Progress
Status in ubuntu-unity-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce and description:

  First test case - where things work correctly:

  1.  Open Settings-> Privacy and make sure that Automatic screen lock is ON.
  2.  Suspend your machine
  3.  Resume your machine
  4.  Notice that the lockscreen is shown on resume and that you can't see the 
desktop

  Second test case - where things are broken

  1.  Open Settings -> Privacy and make sure that Automatic screen lock is OFF.
  2.  Suspend your machine
  3.  Resume your machine
  4.  Notice that the desktop is visible for a second, then the screen blanks, 
then the lock screen appears, then the screen blanks again.  You are left at a 
black screen and need to unlock.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1768786/+subscriptions

-- 
Mailing list: https://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 1768786] Re: Lock screen is displayed when resuming from suspend

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

** Changed in: ubuntu-unity-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  Desktop is displayed when resuming from suspend

Status in budgie-desktop package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  In Progress
Status in ubuntu-unity-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce and description:

  First test case - where things work correctly:

  1.  Open Settings-> Privacy and make sure that Automatic screen lock is ON.
  2.  Suspend your machine
  3.  Resume your machine
  4.  Notice that the lockscreen is shown on resume and that you can't see the 
desktop

  Second test case - where things are broken

  1.  Open Settings -> Privacy and make sure that Automatic screen lock is OFF.
  2.  Suspend your machine
  3.  Resume your machine
  4.  Notice that the desktop is visible for a second, then the screen blanks, 
then the lock screen appears, then the screen blanks again.  You are left at a 
black screen and need to unlock.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1768786/+subscriptions

-- 
Mailing list: https://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 1773167] Re: [Intel HDMI LPE driver] Audio is not working; pulseaudio consumes 100% of a single CPU core

** Changed in: pulseaudio
   Status: Unknown => Confirmed

** Changed in: pulseaudio
   Importance: Unknown => Medium

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

Title:
  [Intel HDMI LPE driver] Audio is not working; pulseaudio consumes 100%
  of a single CPU core

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  On a krez ninja 1103 laptop audio is not working; pulseaudio consumes
  100% of a single CPU core. Pulseaudio log atached.

  According to perf, most CPU is consumed at __memset_erms.

  Below is the GDB stacktrace of pulseaudio.

  # gdb -p 1009 -batch -eval-command="thread apply all bt"
  [New LWP 1028]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  0x7fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, 
expected=0, futex_word=0x56318e574a30) at 
../sysdeps/unix/sysv/linux/futex-internal.h:205
  205   ../sysdeps/unix/sysv/linux/futex-internal.h: No such file or directory.

  Thread 2 (Thread 0x7fe2a7458700 (LWP 1028)):
  #0  0x7fe2ab063339 in _IO_str_init_static_internal 
(sf=sf@entry=0x7fe2a7453700, ptr=ptr@entry=0x7fe2a7453b80 "", 
size=size@entry=255, pstart=pstart@entry=0x7fe2a7453b80 "") at strops.c:36
  #1  0x7fe2ab10515b in ___vsnprintf_chk (s=0x7fe2a7453b80 "", 
maxlen=, flags=1, slen=, format=0x7fe2ac698e8d 
"%s%c: %s", args=0x7fe2a74538a0) at vsnprintf_chk.c:62
  #2  0x7fe2ac6601ca in pa_vsnprintf () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #3  0x7fe2ac660366 in pa_snprintf () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #4  0x7fe2ac66bda8 in pa_log_levelv_meta () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #5  0x7fe2ac66b655 in pa_log_level_meta () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #6  0x7fe2a52b36ae in ?? () from 
/usr/lib/pulse-11.1/modules/libalsa-util.so
  #7  0x7fe2ac68c2a8 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #8  0x7fe2abb756db in start_thread (arg=0x7fe2a7458700) at 
pthread_create.c:463
  #9  0x7fe2ab0f488f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  Thread 1 (Thread 0x7fe2acfe7500 (LWP 1009)):
  #0  0x7fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, 
abstime=0x0, expected=0, futex_word=0x56318e574a30) at 
../sysdeps/unix/sysv/linux/futex-internal.h:205
  #1  do_futex_wait (sem=sem@entry=0x56318e574a30, abstime=0x0) at 
sem_waitcommon.c:111
  #2  0x7fe2abb7e7c8 in __new_sem_wait_slow (sem=0x56318e574a30, 
abstime=0x0) at sem_waitcommon.c:181
  #3  0x7fe2ac68c502 in pa_semaphore_wait () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #4  0x7fe2ac8cca24 in pa_asyncmsgq_send () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-11.1.so
  #5  0x7fe2a6841119 in ?? () from 
/usr/lib/pulse-11.1/modules/libprotocol-native.so
  #6  0x7fe2ac675ee2 in pa_pdispatch_run () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #7  0x7fe2a6844695 in ?? () from 
/usr/lib/pulse-11.1/modules/libprotocol-native.so
  #8  0x7fe2ac678bef in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #9  0x7fe2ac67b6ab in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #10 0x7fe2ac67ba49 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #11 0x7fe2ac67c2cf in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #12 0x7fe2ac40e0d8 in pa_mainloop_dispatch () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #13 0x7fe2ac40e4ae in pa_mainloop_iterate () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #14 0x7fe2ac40e530 in pa_mainloop_run () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #15 0x56318d445b82 in main ()

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices:  List of CAPTURE Hardware Devices 
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   user   1009 F...m pulseaudio
   /dev/snd/controlC0:  user   1009 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Audio'/'Intel HDMI/DP LPE Audio'
 Mixer name : ''
 Components : ''
 Controls  : 15
 Simple ctrls  : 0
  Card0.Amixer.values:
   
  CurrentDesktop: LXDE
  Date: Thu May 24 16:04:13 2018
  InstallationDate: Installed on 2018-05-22 (1 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64

[Desktop-packages] [Bug 1773244] Re: gnome-shell using high cpu

Yuri - please log a separate bug so we can diagnose your issue
separately.

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

Title:
  gnome-shell using high cpu

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  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
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu May 24 22:16:07 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-09-14 (252 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (23 days ago)

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

-- 
Mailing list: https://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 1768786] Re: Lock screen is displayed when resuming from suspend

** Summary changed:

- Screen is displayed when resuming from suspend
+ Lock screen is displayed when resuming from suspend

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

Title:
  Desktop is displayed when resuming from suspend

Status in budgie-desktop package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  In Progress
Status in ubuntu-unity-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce and description:

  First test case - where things work correctly:

  1.  Open Settings-> Privacy and make sure that Automatic screen lock is ON.
  2.  Suspend your machine
  3.  Resume your machine
  4.  Notice that the lockscreen is shown on resume and that you can't see the 
desktop

  Second test case - where things are broken

  1.  Open Settings -> Privacy and make sure that Automatic screen lock is OFF.
  2.  Suspend your machine
  3.  Resume your machine
  4.  Notice that the desktop is visible for a second, then the screen blanks, 
then the lock screen appears, then the screen blanks again.  You are left at a 
black screen and need to unlock.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1768786/+subscriptions

-- 
Mailing list: https://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 1770725] Re: [i915 SNB] You can not see the image of the movie in Wayland sessions

** Summary changed:

- You can not see the image of the movie
+ [i915 SNB] You can not see the image of the movie in Wayland sessions

** Changed in: gstreamer1.0 (Ubuntu)
   Status: Incomplete => New

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

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

Title:
  [i915 SNB] You can not see the image of the movie in Wayland sessions

Status in Gstreamer1.0:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  Hello,

  You can not see the image of the movie.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.0-1
  Uname: Linux 4.16.7-041607-generic x86_64
  ApportVersion: 2.20.10-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri May 11 15:35:17 2018
  InstallationDate: Installed on 2017-10-13 (210 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions

-- 
Mailing list: https://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 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)

It's interesting osdWindow.js appears at the top of the stacks.

Do you see any overlay/popups very often?

Does the problem persist after rebooting?

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

Title:
  gnome-shell filling up syslog with thousands of entries (stack traces
  ending in osdWindow.js:206/207)

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm seeing a several gigs (more than 70GB) a day of the following
  entries on syslog:

  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 gnome-shell[1469]: Object St.Icon (0x557eca1b2e90), 
has been already finalized. Impossible to set any property to it.
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)

  gnome-shell:
    Installed: 3.28.1-0ubuntu2
    Candidate: 3.28.1-0ubuntu2
    Version table:
   *** 3.28.1-0ubuntu2 500
  500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic

  There's similar bug that should be related to this one 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747566 but that fix 
didn't work for me.
  --- 
  ApportV

[Desktop-packages] [Bug 1773198] Re: Sound volume for applications can become locked below global output volume.

Please check the per-application volume settings in your system
settings. You can adjust the volume per application separately.

Please also run this command to send us information about the system:
  apport-collect 1773198

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

Title:
  Sound volume for applications can become locked below global output
  volume.

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Normal behavior, as far as I understand, is for all applications to
  have the same sound volume unless you lower the volume for one
  manually in the applications section of the sound settings. However,
  some applications have their own own volume control that only affect
  the volume of themselves and the global output volume, not other
  applications. This can put those other applications below the global
  volume where they become stuck.

  An example: you have the output volume at 50%. Rhythmbox is locked to
  output volume and is also at 50%. Then you open a movie in totem.
  Sound volume is low for that movie so you use totem's volume slider to
  increase volume to 100%. When done you close totem and use the media
  keys on the keyboard to lower the volume back to 50%. Since rhythmbox
  stayed at 50% instead of following to 100%, it got stuck at half of
  global volume and after lowering is now down to 25%. It can never go
  above 50% with just the normal volume controls, you need to go into
  the applications section of the sound menu and move its volume slider
  to reset it to the same value as the global output volume.

  This is especially a problem since you might increase the global
  volume a lot in order to compensate for low volume, only for a newly
  opened application to start playing sound at way too high a volume, a
  danger to your ears and possibly your sound hardware. And a novice
  user is likely to not understand what's wrong with their audio all of
  a sudden, and feel forced to reboot to fix it.

  The same thing happens with the volume control in vlc so it's not just
  totem.

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

-- 
Mailing list: https://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 1773308] Re: gnome-shell crashed with signal 5

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

That's odd. This doesn't look like bug 1748450. I think apport might
have got that wrong.

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Crash when I log in after resume from suspend.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 25 08:02:52 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-07-15 (1409 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_cancellable_make_pollfd () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_socket_condition_timed_wait () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_input_stream_read () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to cosmic on 2018-03-24 (61 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

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

-- 
Mailing list: https://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 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from

What?! Two reports from cosmic
https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95

Or three, if you count bug 1773308.

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler(message="Connection
  to xwayland lost") from g_logv() from g_log() from 

Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Invalid
Status in mutter source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  * Xwayland is failing frequently (not crashing), which triggers a
  crash in gnome-shell because gnome-shell doesn't know how to survive
  after Xwayland has reset itself.

  * The frequent gnome-shell crashes create frequent problem reports and
  annoying dialogs for users, after they log in to an apparently working
  gnome-shell.

  * This affects Xorg sessions too, because the gdm login screen itself
  is a Wayland session. And Xorg users will see the problem dialog after
  they have logged into a Xorg session.

  * The fix simply converts the crash into a silent exit (as decided by
  Gnome upstream). This avoids the mountain of crash reports and
  annoying error dialogs at least. It does not fix the root causes that
  remain in Xwayland, but this is considered acceptable because there
  really isn't a bug in gnome-shell here other than it doesn't know how
  to survive without a connection to Xwayland.

  * For users of Xorg sessions, like bionic default, this is a full fix
  as Xorg users will never get an Xwayland instance after logging in.
  And hence the Xwayland bugs are irrelevant.

  [Test Case]

  * Just install bionic, use it lightly and reboot a few times.

  * Observe crash files are left in /var/crash and problem report
  dialogs after logging in.

  [Regression Potential]

  Medium. The fix does not really change the structure of the existing
  error handling, only changes it from a core dump into a silent exit.
  For Xorg users this should be invisible as the affected login screen
  restarts automatically.

  [Other Info]

  This is a whole class of gnome-shell crash which includes bug 1505409, bug 
1748450 and bug 1556601. All three should be considered the same crash for the 
sake of this SRU. Just don't mark them as duplicates of each other
  because they are all still collecting duplicates of their own.

  -

  *** This is a duplicate of bug 1505409, but is being kept separate so
  as to automatically collect duplicate reports since the stacktrace
  signature has changed recently. Any resolution and discussion should
  occur in bug 1505409. ***

  See also:
  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
  Uname: Linux 4.13.0-33-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Feb  8 23:50:23 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2016-03-21 (690 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
  UserGroups:

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

-- 
Mailing list: https://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 1706460] Re: Outdated Totem documentation describes and mentions features absent from the software

Now tracking in:
https://gitlab.gnome.org/GNOME/totem/issues/108

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

Title:
  Outdated Totem documentation describes and mentions features absent
  from the software

Status in Totem:
  Expired
Status in totem package in Ubuntu:
  Triaged

Bug description:
  'man totem' mentions "F9   toggle display of the playlist" and
  the Help document in totem often describes choosing the "sidebar"
  option from the "View" menu.

  Pressing F9 does nothing.  There is no "sidebar" option in the "View"
  menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jul 25 18:47:38 2017
  InstallationDate: Installed on 2016-06-05 (415 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: totem
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (103 days ago)

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

-- 
Mailing list: https://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 1720465] Re: HiDPI scaling does not hold across reboot

Sébastien,

After you upgrade to 18.04, please run 'apport-collect 1720465' to
provide us with newer system information.

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

Title:
  HiDPI scaling does not hold across reboot

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 17.10 Beta (updated as of 29 Sept 2017) on Parallels
  Desktop 13.  When changing the HiDPI scaling to 200% everything looks
  good, but on restart the settings are reset to 100%.

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

-- 
Mailing list: https://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 1773167] Re: Audio is not working; pulseaudio consumes 100% of a single CPU core

Now tracking upstream in:
https://bugs.freedesktop.org/show_bug.cgi?id=100488

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

** Changed in: pulseaudio
   Importance: High => Unknown

** Changed in: pulseaudio
   Status: Invalid => Unknown

** Changed in: pulseaudio
 Remote watch: freedesktop.org Bugzilla #106645 => freedesktop.org Bugzilla 
#100488

** Summary changed:

- Audio is not working; pulseaudio consumes 100% of a single CPU core
+ [Intel HDMI LPE driver] Audio is not working; pulseaudio consumes 100% of a 
single CPU core

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

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

Title:
  [Intel HDMI LPE driver] Audio is not working; pulseaudio consumes 100%
  of a single CPU core

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  On a krez ninja 1103 laptop audio is not working; pulseaudio consumes
  100% of a single CPU core. Pulseaudio log atached.

  According to perf, most CPU is consumed at __memset_erms.

  Below is the GDB stacktrace of pulseaudio.

  # gdb -p 1009 -batch -eval-command="thread apply all bt"
  [New LWP 1028]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  0x7fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, 
expected=0, futex_word=0x56318e574a30) at 
../sysdeps/unix/sysv/linux/futex-internal.h:205
  205   ../sysdeps/unix/sysv/linux/futex-internal.h: No such file or directory.

  Thread 2 (Thread 0x7fe2a7458700 (LWP 1028)):
  #0  0x7fe2ab063339 in _IO_str_init_static_internal 
(sf=sf@entry=0x7fe2a7453700, ptr=ptr@entry=0x7fe2a7453b80 "", 
size=size@entry=255, pstart=pstart@entry=0x7fe2a7453b80 "") at strops.c:36
  #1  0x7fe2ab10515b in ___vsnprintf_chk (s=0x7fe2a7453b80 "", 
maxlen=, flags=1, slen=, format=0x7fe2ac698e8d 
"%s%c: %s", args=0x7fe2a74538a0) at vsnprintf_chk.c:62
  #2  0x7fe2ac6601ca in pa_vsnprintf () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #3  0x7fe2ac660366 in pa_snprintf () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #4  0x7fe2ac66bda8 in pa_log_levelv_meta () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #5  0x7fe2ac66b655 in pa_log_level_meta () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #6  0x7fe2a52b36ae in ?? () from 
/usr/lib/pulse-11.1/modules/libalsa-util.so
  #7  0x7fe2ac68c2a8 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #8  0x7fe2abb756db in start_thread (arg=0x7fe2a7458700) at 
pthread_create.c:463
  #9  0x7fe2ab0f488f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  Thread 1 (Thread 0x7fe2acfe7500 (LWP 1009)):
  #0  0x7fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, 
abstime=0x0, expected=0, futex_word=0x56318e574a30) at 
../sysdeps/unix/sysv/linux/futex-internal.h:205
  #1  do_futex_wait (sem=sem@entry=0x56318e574a30, abstime=0x0) at 
sem_waitcommon.c:111
  #2  0x7fe2abb7e7c8 in __new_sem_wait_slow (sem=0x56318e574a30, 
abstime=0x0) at sem_waitcommon.c:181
  #3  0x7fe2ac68c502 in pa_semaphore_wait () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #4  0x7fe2ac8cca24 in pa_asyncmsgq_send () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-11.1.so
  #5  0x7fe2a6841119 in ?? () from 
/usr/lib/pulse-11.1/modules/libprotocol-native.so
  #6  0x7fe2ac675ee2 in pa_pdispatch_run () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #7  0x7fe2a6844695 in ?? () from 
/usr/lib/pulse-11.1/modules/libprotocol-native.so
  #8  0x7fe2ac678bef in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #9  0x7fe2ac67b6ab in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #10 0x7fe2ac67ba49 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #11 0x7fe2ac67c2cf in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #12 0x7fe2ac40e0d8 in pa_mainloop_dispatch () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #13 0x7fe2ac40e4ae in pa_mainloop_iterate () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #14 0x7fe2ac40e530 in pa_mainloop_run () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #15 0x56318d445b82 in main ()

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices:  List of CAPTURE Hardware De

[Desktop-packages] [Bug 1773448] Re: Shortcut to move Windows between monitors is wrong.

2018-05-25 Thread Gunnar Hjalmarsson

Thanks for your report!

I don't have a multi-monitor setup, so can't test.

But that page is from the upstream GNOME Help and should be changed
there, so it would be great if you could submit an upstream issue too:

https://gitlab.gnome.org/GNOME/gnome-user-docs/issues

If you do, please post the URL of the upstream issue here.

** Package changed: ubuntu-docs (Ubuntu) => gnome-user-docs (Ubuntu)

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

Title:
  Shortcut to move Windows between monitors is wrong.

Status in gnome-user-docs package in Ubuntu:
  New

Bug description:
  Two of the shortcuts in the following document seem to be wrong.

  https://help.ubuntu.com/stable/ubuntu-help/shell-keyboard-
  shortcuts.html.en

  
  Move the current window one monitor to the right.
  Should be  Ctrl+Shift+Super <--

  
  Move the current window one monitor to the right.
  Should be   Ctrl+Shift+Super -->

  Used <-- to indicate arrow keys.

  
  Also should add the following. 
  CTRL+Super+  and the directions left right or up  move the screen to that side
  of the monitor divided in half.  using  UP results in maximizing the screen 
again.

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

-- 
Mailing list: https://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 1773448] [NEW] Shortcut to move Windows between monitors is wrong.

You have been subscribed to a public bug:

Two of the shortcuts in the following document seem to be wrong.

https://help.ubuntu.com/stable/ubuntu-help/shell-keyboard-
shortcuts.html.en


Move the current window one monitor to the right.
Should be  Ctrl+Shift+Super <--


Move the current window one monitor to the right.
Should be   Ctrl+Shift+Super -->

Used <-- to indicate arrow keys.


Also should add the following. 
CTRL+Super+  and the directions left right or up  move the screen to that side
of the monitor divided in half.  using  UP results in maximizing the screen 
again.

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

-- 
Shortcut to move Windows between monitors is wrong. 
https://bugs.launchpad.net/bugs/1773448
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-user-docs in Ubuntu.

-- 
Mailing list: https://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 1773167] Re: Audio is not working; pulseaudio consumes 100% of a single CPU core

** Changed in: pulseaudio
   Status: Unknown => Invalid

** Changed in: pulseaudio
   Importance: Unknown => High

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

Title:
  Audio is not working; pulseaudio consumes 100% of a single CPU core

Status in PulseAudio:
  Invalid
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On a krez ninja 1103 laptop audio is not working; pulseaudio consumes
  100% of a single CPU core. Pulseaudio log atached.

  According to perf, most CPU is consumed at __memset_erms.

  Below is the GDB stacktrace of pulseaudio.

  # gdb -p 1009 -batch -eval-command="thread apply all bt"
  [New LWP 1028]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  0x7fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, 
expected=0, futex_word=0x56318e574a30) at 
../sysdeps/unix/sysv/linux/futex-internal.h:205
  205   ../sysdeps/unix/sysv/linux/futex-internal.h: No such file or directory.

  Thread 2 (Thread 0x7fe2a7458700 (LWP 1028)):
  #0  0x7fe2ab063339 in _IO_str_init_static_internal 
(sf=sf@entry=0x7fe2a7453700, ptr=ptr@entry=0x7fe2a7453b80 "", 
size=size@entry=255, pstart=pstart@entry=0x7fe2a7453b80 "") at strops.c:36
  #1  0x7fe2ab10515b in ___vsnprintf_chk (s=0x7fe2a7453b80 "", 
maxlen=, flags=1, slen=, format=0x7fe2ac698e8d 
"%s%c: %s", args=0x7fe2a74538a0) at vsnprintf_chk.c:62
  #2  0x7fe2ac6601ca in pa_vsnprintf () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #3  0x7fe2ac660366 in pa_snprintf () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #4  0x7fe2ac66bda8 in pa_log_levelv_meta () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #5  0x7fe2ac66b655 in pa_log_level_meta () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #6  0x7fe2a52b36ae in ?? () from 
/usr/lib/pulse-11.1/modules/libalsa-util.so
  #7  0x7fe2ac68c2a8 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #8  0x7fe2abb756db in start_thread (arg=0x7fe2a7458700) at 
pthread_create.c:463
  #9  0x7fe2ab0f488f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  Thread 1 (Thread 0x7fe2acfe7500 (LWP 1009)):
  #0  0x7fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, 
abstime=0x0, expected=0, futex_word=0x56318e574a30) at 
../sysdeps/unix/sysv/linux/futex-internal.h:205
  #1  do_futex_wait (sem=sem@entry=0x56318e574a30, abstime=0x0) at 
sem_waitcommon.c:111
  #2  0x7fe2abb7e7c8 in __new_sem_wait_slow (sem=0x56318e574a30, 
abstime=0x0) at sem_waitcommon.c:181
  #3  0x7fe2ac68c502 in pa_semaphore_wait () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #4  0x7fe2ac8cca24 in pa_asyncmsgq_send () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-11.1.so
  #5  0x7fe2a6841119 in ?? () from 
/usr/lib/pulse-11.1/modules/libprotocol-native.so
  #6  0x7fe2ac675ee2 in pa_pdispatch_run () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #7  0x7fe2a6844695 in ?? () from 
/usr/lib/pulse-11.1/modules/libprotocol-native.so
  #8  0x7fe2ac678bef in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #9  0x7fe2ac67b6ab in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #10 0x7fe2ac67ba49 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #11 0x7fe2ac67c2cf in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #12 0x7fe2ac40e0d8 in pa_mainloop_dispatch () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #13 0x7fe2ac40e4ae in pa_mainloop_iterate () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #14 0x7fe2ac40e530 in pa_mainloop_run () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #15 0x56318d445b82 in main ()

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices:  List of CAPTURE Hardware Devices 
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   user   1009 F...m pulseaudio
   /dev/snd/controlC0:  user   1009 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Audio'/'Intel HDMI/DP LPE Audio'
 Mixer name : ''
 Components : ''
 Controls  : 15
 Simple ctrls  : 0
  Card0.Amixer.values:
   
  CurrentDesktop: LXDE
  Date: Thu May 24 16:04:13 2018
  InstallationDate: Installed on 2018-05-22 (1 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: pulsea

[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

2018-05-25 Thread BobvanderPoel

I just installed 18.04 and had the same problem ... so it's not fixed
yet.

Seems that copying the epkowa files from /usr/lib/sane to
/usr/lib/x86_64-linux-gnu/sane does the trick.

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions

-- 
Mailing list: https://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 220994] Re: No automatic delete function in rythmbox

** Changed in: rhythmbox
   Status: New => Expired

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

Title:
  No automatic delete function in rythmbox

Status in Rhythmbox:
  Expired
Status in rhythmbox package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: rhythmbox

  One of my audio podcasts delivers news every day. Wouldn't it make
  sense to implement a function, that deletes after some specified days
  the old audio files?

  This would enhance the podcast management.

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

-- 
Mailing list: https://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 525255] Re: [f-req] manipulation of radio station titles

** Changed in: rhythmbox
   Status: New => Expired

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

Title:
  [f-req] manipulation of radio station titles

Status in Rhythmbox:
  Expired
Status in rhythmbox package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: rhythmbox

  When i use shoutcast.com to add radiostations to rythmbox, 
  it always (stupidly, they wont change this) a station-count number before the 
actual title, in the title.

  Also, i get multiple entries from the .pls (1 per server for the
  station).

  This results in a very messy station list.

  The fix isn't that hard to implement;

  0) keep the current raw list as-is, but re-use as the base-list for
  the next steps;

  1) use the "radio station title conversion list" (rstcl) to display a
  proper list; no dupes, and no messy extra info

  the rstcl should be (partially) pre-configured, save-able & loadable (append 
at bottom), and have a configuration window with these abilities:
  - specify rules for pre-aggregate conversion, consisting of rows with the 
following:
- (optional) criterium : domain .pls is loaded from (with a special case 
keyword for "FROM_DESKTOP", which catches at least nautilus plz)
- criterium : raw title must match some regexp
- conversion regexp
 - checkbox whether or not to stop processing the next rules if this one 
hits (on by default).

  rule rows must be able to be arranged (top->bottom=priority) by
  dragndrop plz.

  with these rules, all multiple-server stations are aggregated into identical 
titles.
  only 1 entry needs to be shown, but then rythmbox must change a little 
internally too, to auto-skip to the next server in case of outage.
  a (yellow backgr?) statusmsg in a statusbar (see other new bug) would be 
ideal to notify the user.
  after looping through all the stations, continue looping at 1x per 10-20 
seconds try.

  yes, this is real work, but i believe it'll be well worth it.

  ProblemType: Bug
  Architecture: i386
  Date: Sun Feb 21 12:10:58 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  NonfreeKernelModules: nvidia
  Package: rhythmbox 0.12.5-0ubuntu5.2
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
  SourcePackage: rhythmbox
  Uname: Linux 2.6.31-19-generic i686

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

-- 
Mailing list: https://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 1440381] Re: please build bindings for Python3

2018-05-25 Thread Jelmer Vernooij

python3-ldb appears to have come from an ubuntu-specific patch that got
dropped at some point.

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

Title:
  please build bindings for Python3

Status in ldb package in Ubuntu:
  New
Status in samba package in Ubuntu:
  Triaged
Status in talloc package in Ubuntu:
  New
Status in tdb package in Ubuntu:
  Fix Released
Status in samba package in Debian:
  New

Bug description:
  There is still the goal to remove Python2 from the desktop images, and
  to use Python3 only. please build bindings for Python3

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

-- 
Mailing list: https://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 1735346] Re: bittornado: Python3 port needed, or demotion to universe

What is deployed on torrent.ubuntu.com should not be taken as the best
example of how to deploy torrent trackers =)

And in 2018, I would not recommend anybody to deploy a brand new python2
service.

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

Title:
  bittornado: Python3 port needed, or demotion to universe

Status in bittornado package in Ubuntu:
  Fix Committed
Status in bittornado package in Debian:
  New

Bug description:
  bittornado: Python3 port needed, or demotion to universe.

  Currently seeded in supported-desktop-extra

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

-- 
Mailing list: https://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 1735346] Re: bittornado: Python3 port needed, or demotion to universe


revno: 2680
fixes bug: https://launchpad.net/bugs/1735346
committer: Dimitri John Ledkov 
branch nick: ubuntu.cosmic
timestamp: Sat 2018-05-26 00:11:41 +0100
message:
  The command line tool for torrents is called trasmission-cli
diff:
=== modified file 'supported-desktop-extra'
--- supported-desktop-extra 2018-04-24 16:21:11 +
+++ supported-desktop-extra 2018-05-25 23:11:41 +
@@ -22,10 +22,6 @@
  * icc-profiles-free
  * vim-gnome
 
-= Command line tools =
-
- * bittornado
-
 == Restricted drivers ==
 
  * fglrx-amdcccle-updates


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

** Changed in: bittornado (Ubuntu)
Milestone: None => ubuntu-18.10

** Changed in: bittornado (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  bittornado: Python3 port needed, or demotion to universe

Status in bittornado package in Ubuntu:
  Fix Committed
Status in bittornado package in Debian:
  New

Bug description:
  bittornado: Python3 port needed, or demotion to universe.

  Currently seeded in supported-desktop-extra

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

-- 
Mailing list: https://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 1735346] Re: bittornado: Python3 port needed, or demotion to universe

** Branch linked: lp:~ubuntu-core-dev/ubuntu-seeds/ubuntu.cosmic

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

Title:
  bittornado: Python3 port needed, or demotion to universe

Status in bittornado package in Ubuntu:
  Fix Committed
Status in bittornado package in Debian:
  New

Bug description:
  bittornado: Python3 port needed, or demotion to universe.

  Currently seeded in supported-desktop-extra

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

-- 
Mailing list: https://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 1735346] Re: bittornado: Python3 port needed, or demotion to universe

And we already have transmission seeded in the desktops. Which is a lot
nicer client. I thought it can be a server too, no?!

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

Title:
  bittornado: Python3 port needed, or demotion to universe

Status in bittornado package in Ubuntu:
  Fix Committed
Status in bittornado package in Debian:
  New

Bug description:
  bittornado: Python3 port needed, or demotion to universe.

  Currently seeded in supported-desktop-extra

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

-- 
Mailing list: https://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 1772542] Re: after waking from sleep i get text radeon error message then return login screen

2018-05-25 Thread Chris Guiver

1) understood (I'd guessed that)

2) NO I didn't have the issues in 17.10/artful.

I didn't use xfce for 2-3 weeks post release-upgrade to 18.04/bionic
because I couldn't login (login loop xfce only).   Your (4) "there could
have been some cruft left over from the upgrade" makes me happy; as it
fits my initial trouble getting xfce running :)

3) will re-test with 30-50 minute cycles & add comment(s) here.  I had
no issues this morning from last night's 'sleep' :)  (i usually have
machine on all day; in 'sleep' overnight)

4) Thank you


** Attachment added: "limited value - yesterday's syslog.1  
(may22.0941-may25.1256 aest so +1000)"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/+attachment/5144437/+files/syslog.1_2018-05.25.txt

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

Title:
  after waking from sleep i get text radeon error message then return
  login screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE
  desktops added)

  I sleep my XFCE (xubuntu) machine rather than turning it off at night.

  Today as with yesterday morning, instead of getting the locker-screen
  after hitting the power-button to wake my machine, i get a blank
  screen with a RADEON two-line text message top left on screen which
  appear only momentarily as screen is erased and I get the
  login/greeter screen.

  (it's happened 4-5 times, but does NOT happen every time)

  I can login fine, but my xfce session is new.

  I have grep'd for the message I see (yesterday & today), but can't
  find it as i usually recall little but the radeon word...

  sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:01:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0
     resources: irq:30 memory:e000-efff memory:f7de-f7df 
ioport:dc00(size=256) memory:c-d

  guiverc@d960-ubu2:/var/crash$   pwd
  /var/crash
  guiverc@d960-ubu2:/var/crash$   ls -la
  total 35332
  drwxrwsrwt  2 rootwhoopsie 4096 May 22 09:41 .
  drwxr-xr-x 15 rootroot 4096 Nov 16  2017 ..
  -rw-r-  1 guiverc whoopsie50003 May 21 10:32 
_usr_bin_caffeine.1000.crash
  -rw-r-  1 guiverc whoopsie   880121 May 21 10:33 
_usr_bin_light-locker.1000.crash
  -rw-rw-r--  1 guiverc whoopsie0 May 21 10:33 
_usr_bin_light-locker.1000.upload
  -rw-r-  1 guiverc whoopsie 35234566 May 21 10:32 
_usr_lib_xorg_Xorg.1000.crash
  (these files are dated yesteday - i didn't find anything for today)

  extract of /var/log/auth.log  (copied from `view` hence line numbers)
  // last-night
   48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
  // overnight
   52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
opened for user root by (uid=0)
   53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
closed for user root
   54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' 
finished.
   58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): 
session closed for user guiverc
   59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed 
for user root
   60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
   62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22.
   63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send 
message, 2 matched rules; type="m

[Desktop-packages] [Bug 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

Krishnan Sreenivas:

>"No the windows boot mgr got corrupted"

Regarding strong claims like, "... got corrupted" please post
logs/evidence, advise what caused the corruption, what the configuration
or log file looks like now, and what it should look like precisely to
not be considered corrupted.

1) Can you still dual boot into Windows? If so, run the following as an 
administrator and post the full results:
bcdedit /enum

2) When you boot into Windows, do you have "Turn on fast startup"
enabled? If so, does disabling this help?

"(removed from BIOS)"

As per your partition screenshot, you have an UEFI partition (i.e. not
BIOS).

3) In Ubuntu, did you manually edit fstab entries?

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  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/+bug/1773235/+subscriptions

-- 
Mailing list: https://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 1440381] Re: please build bindings for Python3

** Changed in: ldb (Ubuntu)
   Importance: Undecided => Critical

** Changed in: ldb (Ubuntu)
Milestone: None => ubuntu-18.10

** Changed in: samba (Ubuntu)
   Importance: Wishlist => Critical

** Changed in: samba (Ubuntu)
Milestone: None => ubuntu-18.10

** Changed in: talloc (Ubuntu)
   Importance: Undecided => Critical

** Changed in: talloc (Ubuntu)
Milestone: None => ubuntu-18.10

** Changed in: tdb (Ubuntu)
   Importance: Undecided => Critical

** Changed in: tdb (Ubuntu)
Milestone: None => ubuntu-18.10

** Changed in: tdb (Ubuntu)
   Status: New => Fix Released

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

Title:
  please build bindings for Python3

Status in ldb package in Ubuntu:
  New
Status in samba package in Ubuntu:
  Triaged
Status in talloc package in Ubuntu:
  New
Status in tdb package in Ubuntu:
  Fix Released
Status in samba package in Debian:
  New

Bug description:
  There is still the goal to remove Python2 from the desktop images, and
  to use Python3 only. please build bindings for Python3

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

-- 
Mailing list: https://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 1440381] Re: please build bindings for Python3

Hm python3-ldb used to be there in xenial, but not anymore? What has
happened to that?

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

Title:
  please build bindings for Python3

Status in ldb package in Ubuntu:
  New
Status in samba package in Ubuntu:
  Triaged
Status in talloc package in Ubuntu:
  New
Status in tdb package in Ubuntu:
  Fix Released
Status in samba package in Debian:
  New

Bug description:
  There is still the goal to remove Python2 from the desktop images, and
  to use Python3 only. please build bindings for Python3

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

-- 
Mailing list: https://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 1440372] Re: please port duplicity to Python3

** Branch linked: lp:~xnox/ubuntu-seeds/demote-duplicity-py2

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

Title:
  please port duplicity to Python3

Status in Duplicity:
  New
Status in duplicity package in Ubuntu:
  Triaged

Bug description:
  There is still the goal to remove Python2 from the desktop images, and
  to use Python3 only. deja-dup should be ported to Python3.

  There seems to be some progress upstream.

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

-- 
Mailing list: https://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 1440372] Re: please port duplicity to Python3

So what should we do now? To drop python2 from main, we will need to
demote duplicity.

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

Title:
  please port duplicity to Python3

Status in Duplicity:
  New
Status in duplicity package in Ubuntu:
  Triaged

Bug description:
  There is still the goal to remove Python2 from the desktop images, and
  to use Python3 only. deja-dup should be ported to Python3.

  There seems to be some progress upstream.

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

-- 
Mailing list: https://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 1773087] Re: Remove python3-apport as dependency of xserver-xorg

2018-05-25 Thread Nish Aravamudan

xserver-xorg now has an apport hook. So in order of ubuntu-bug to work,
it is necessary to have python3-apport installed, per LP: #1730035.
Definitely not a bug.

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

Title:
  Remove python3-apport as dependency of xserver-xorg

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Distro: Bionic
  Binary Package: xserver-xorg
  Version: 1:7.7+19ubuntu7

  Hello!
  The package xserver-xorg depends on python3-apport. I don't want to use 
apport on my systems.
  Can the dependency be removed?

  Also, it doesn't work anyway. That's how I noticed that the package is
  installed:

  root@00debac04ddf:~# foo
  Traceback (most recent call last):
File "/usr/bin/foo", line 3, in 
  raise Exception
  Exception
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 145, in 
apport_excepthook
  os.O_WRONLY | os.O_CREAT | os.O_EXCL, 0o640), 'wb') as f:
  FileNotFoundError: [Errno 2] No such file or directory: 
'/var/crash/_usr_bin_foo.0.crash'

  Original exception was:
  Traceback (most recent call last):
File "/usr/bin/foo", line 3, in 
  raise Exception
  Exception

  Thanks
  Jörn Heissler

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

-- 
Mailing list: https://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 1773087] Re: Remove python3-apport as dependency of xserver-xorg

2018-05-25 Thread Joern Heissler

Caused by #1730035

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

Title:
  Remove python3-apport as dependency of xserver-xorg

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Distro: Bionic
  Binary Package: xserver-xorg
  Version: 1:7.7+19ubuntu7

  Hello!
  The package xserver-xorg depends on python3-apport. I don't want to use 
apport on my systems.
  Can the dependency be removed?

  Also, it doesn't work anyway. That's how I noticed that the package is
  installed:

  root@00debac04ddf:~# foo
  Traceback (most recent call last):
File "/usr/bin/foo", line 3, in 
  raise Exception
  Exception
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 145, in 
apport_excepthook
  os.O_WRONLY | os.O_CREAT | os.O_EXCL, 0o640), 'wb') as f:
  FileNotFoundError: [Errno 2] No such file or directory: 
'/var/crash/_usr_bin_foo.0.crash'

  Original exception was:
  Traceback (most recent call last):
File "/usr/bin/foo", line 3, in 
  raise Exception
  Exception

  Thanks
  Jörn Heissler

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

-- 
Mailing list: https://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 1184699] Re: Canon LIDE 110 can only scan once, then I need to replug the usb cable

2018-05-25 Thread Marcus Mikulcak

I can confirm that the problem persists for my Canon DR-2580 which works
perfectly fine with ehci in Ubuntu 16.04 but can only scan a single page
using xhci on Ubuntu 16.04 (tested on different machines: the first has
a USB 2 port, the second one doesn't and connecting using a USB 2 cable
doesn't help). Both run sane 1.0.27

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

Title:
  Canon LIDE 110 can only scan once, then I need to replug the usb cable

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  I have a Canon LIDE 110 scanner which works by default on ubuntu 13.04. 
  The problem is after first scan, I can not scan for second time. I need to 
reconnect the USB cable to use the scanner again.

  # TEST 1 : without reconnecting the usb cable
  francois@pc:~$ scanimage -v > test1.jpg # success
  scanimage: scanning image of size 636x885 pixels at 8 bits/pixel
  scanimage: acquiring gray frame
  scanimage: min/max graylevel value = 0/255
  scanimage: read 562860 bytes in total
  # I don't unplug plug the usb cable.
  francois@pc:~$ scanimage -v > test2.jpg # FAIL
  scanimage: no SANE devices found

  # TEST 2 : reconnect usb cable between scan attempts
  francois@pc:~$ scanimage -v > test1.jpg # success
  scanimage: scanning image of size 636x885 pixels at 8 bits/pixel
  scanimage: acquiring gray frame
  scanimage: min/max graylevel value = 0/255
  scanimage: read 562860 bytes in total
  # I unplug and replug the usb cable.
  francois@pc:~$ scanimage -v > test2.jpg # SUCCESS
  scanimage: scanning image of size 636x885 pixels at 8 bits/pixel
  scanimage: acquiring gray frame
  scanimage: min/max graylevel value = 0/255
  scanimage: read 562860 bytes in total

  francois@pc:~$ dmesg # extract
  [  829.365158] usb 3-1: USB disconnect, device number 2
  [  834.935000] usb 3-1: new high-speed USB device number 4 using xhci_hcd
  [  834.952515] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909
  [  834.952519] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [  834.952522] usb 3-1: Product: CanoScan
  [  834.952524] usb 3-1: Manufacturer: Canon
  [ 1623.738811] usb 3-1: USB disconnect, device number 4
  [ 1623.739072] xhci_hcd :00:14.0: Slot 3 endpoint 6 not removed from BW 
list!
  [ 1625.528827] usb 3-1: new high-speed USB device number 5 using xhci_hcd
  [ 1625.546327] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909
  [ 1625.546331] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 1625.546334] usb 3-1: Product: CanoScan
  [ 1625.546336] usb 3-1: Manufacturer: Canon

  francois@pc:~$ uname -a && cat /etc/issue
  Linux pc 3.8.0-22-generic #33-Ubuntu SMP Thu May 16 15:17:14 UTC 2013 x86_64 
x86_64 x86_64 GNU/Linux
  Ubuntu 13.04 \n \l

  The problem was reported here by someone else :
  http://askubuntu.com/questions/278473/canon-lide-110-should-reconnect-
  usb-for-each-scan

  Thanks
  François

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1184699/+subscriptions

-- 
Mailing list: https://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 1527663] Re: firefox 43 Accept-Language header does not follow preferences

** Changed in: firefox-esr (Debian)
   Status: Unknown => New

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

Title:
  firefox 43 Accept-Language header does not follow preferences

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in firefox-esr package in Debian:
  New

Bug description:
  on a french firefox, possibly on all non english installs of firefox 43 on 
Ubuntu 15.10,
  the Accept-Language header is set to en_US regardless of the language 
preferences.
  It started with the upgrade to ff43, and the issue exists event when creating 
a new profile.

  How to Reproduce :
  Create a new profile on a firefox in french, go to any website, 
Accept-Language HTTP header does not contain "fr"
  (I could reproduce the bug in a virtualized 15.10)

  Workaround :
  about:preferences#content > Languages: choose
  Change order, click OK
  Languages: choose (again) Change order back, click OK
  Now the Accept-Language header is correctly set

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

-- 
Mailing list: https://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 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

No the windows boot mgr got corrupted (removed from BIOS) and only
Ubuntu was available i did not format the drive. I am not too
knowledgeable to troubleshoot Ubuntu in case something happens.

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  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/+bug/1773235/+subscriptions

-- 
Mailing list: https://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 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

Krishnan Sreenivas:

>"The issue was reproducible with only Ubuntu boot,"

To clarify, you completely deleted everything on the drive, only
installed Ubuntu on it (no dual boot) and the problem was reproducible?

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  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/+bug/1773235/+subscriptions

-- 
Mailing list: https://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 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

The issue was reproducible with only Ubuntu boot, the issue did not
exist with the budgie flavor of 18.04.

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  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/+bug/1773235/+subscriptions

-- 
Mailing list: https://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 1773244] Re: gnome-shell using high cpu

2018-05-25 Thread Yuri

Similar issue, seems related to the graphical activities: Xorg is often on the 
top of the CPU usage, web content or Firefox too.
I use a fresh install of 18.04.

** Attachment added: "CPU usage"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773244/+attachment/5144413/+files/Capture%20du%202018-05-25%2022-41-33.png

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

Title:
  gnome-shell using high cpu

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  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
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu May 24 22:16:07 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-09-14 (252 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (23 days ago)

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

-- 
Mailing list: https://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 1732222] Re: Language support not installed matching locale

2018-05-25 Thread David

Still present on Ubuntu 18.04.

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

Title:
  Language support not installed matching locale

Status in language-selector package in Ubuntu:
  Triaged

Bug description:
  When Ubuntu is installed with UK locale settings during setup, all of
  the language support is not installed and some applications e.g.
  LibreOffice display with non-UK English. The extra language support is
  prompted to be installed *the first time* the user accesses the
  language options (see screenshot attached).

  When this language support is installed, these applications then
  (correctly) display menus etc in UK English.

  Ubuntu setup appears to not install the matching locale languages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/173/+subscriptions

-- 
Mailing list: https://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 1484869] Re: Crossfade produces beeping sound when playing some tracks from silence or when changing tracks

** Changed in: rhythmbox
   Status: Confirmed => Expired

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

Title:
  Crossfade produces beeping sound when playing some tracks from silence
  or when changing tracks

Status in Rhythmbox:
  Expired
Status in rhythmbox package in Ubuntu:
  New

Bug description:
  I have Crossfade on for 3 seconds. When I play some tracks, a very
  clear beeping sound appears. It happens when the tracks are played
  from silence (nothing was playing before), or when tracks change (and
  of course crossfade). The beeping sound appears for some seconds at
  the beginning and stops. It doesn't stay for the whole track.

  This doesn't happen when Crossfade is off, or when I play the same
  tracks in Totem (Totem doesn't have Crossfade). It also doesn't happen
  when I play the same tracks in a media player which is not Gstreamer-
  based, like gnome-mplayer.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: rhythmbox 3.0.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  NonfreeKernelModules: fglrx wl
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 14 11:24:50 2015
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2015-06-16 (58 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 294795] Re: Per-process network usage information (Integrate nethogs functionality?)

2018-05-25 Thread Robert Pollak

The gnome-system-monitor bug has been migrated to
https://gitlab.gnome.org/GNOME/gnome-system-monitor/issues/18 in GNOME's
GitLab instance. (Trying to update the Remote Watch field gives me an
error.)

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

Title:
  Per-process network usage information (Integrate nethogs
  functionality?)

Status in Gnome System Monitor:
  Expired
Status in gnome-system-monitor package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-system-monitor

  System Monitor should be able to show per-process network usage (and
  hard drive usage, for that matter)

  Network usage might be able to incorporate functionality from Nethogs
  http://nethogs.sourceforge.net/

  (Based on http://brainstorm.ubuntu.com/idea/12915/ )

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-system-monitor/+bug/294795/+subscriptions

-- 
Mailing list: https://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 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

Krishnan Sreenivas:

To confirm, if you reinstall Ubuntu by completely deleting the entire
drive and only install Ubuntu (no dual boots, manual partitions NTFS,
etc.) is this still reproducible?

If not reproducible, it is advised to keep it this way, and fire up
Windows in a virtual machine if you must use it. Otherwise, you may be
in for a protracted debugging session of ntfs-3g, and potentially
whatever else is going wrong.

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  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/+bug/1773235/+subscriptions

-- 
Mailing list: https://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 1762307] Re: Cannot access encrypted volume

2018-05-25 Thread Howard Moreland

I booted the system from the encrypted hard drive, and it seemed to
unlock, but Dolphin could not access it.

This is for version 20180408, 32-bit. I have since replaced it. Would it
help to install that version again for testing?

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

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

Title:
  Cannot access encrypted volume

Status in udisks2 package in Ubuntu:
  New

Bug description:
  At the screen preparing to install Kubuntu, I selected the button
  "Guided - use entire disk and set up encrypted LVM". System has two
  hard drives, sda with both Mint 18.3 and Bionic 18.04; sdb with Bionic
  18.04. The installer graphic showed it would use all of sda for
  Kubuntu.

  In Dolphin, trying to access the encrypted volume on sda returns:
  An error occurred while accessing '58.9 GiB Encrypted Drive', the system 
responded: The requested operation has failed: Error unlocking /dev/sda5: The 
function 'bd_crypto_luks_open_blob' called, but not implemented!

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

-- 
Mailing list: https://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 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default

2018-05-25 Thread Gunnar Hjalmarsson

To make sure that I'm not wandering, I made an own experiment, where I
put some code in postinst which prints the variables. (I uploaded it to
the same PPA.) Please see the result in the attached file.

So, considering that we must distinguish between upgrades and pure
configuration, only testing if $2 exists is not sufficient. I still
think that the code I proposed does the right thing. ;)

** Attachment added: "postinst-variables.txt"

https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+attachment/5144410/+files/postinst-variables.txt

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

Title:
Alternative shortcut for layout switching Alt+Shift unexpectedly set
by default

Status in console-setup package in Ubuntu:
In Progress
Status in gnome-control-center package in Ubuntu:
Confirmed

Bug description:
Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in
18.04

Steps to reproduce:
1. Define two keyboard input methods in Settings -> Region & Language ->
Input Sources
2. Open several applications
3. Observe that application windows can be iterated with Alt + Tab
4. Once application window iteration was begun with Alt + Tab, try to iterate
backwards with Alt + Shift + Tab.
5. Try to change keyboard input method switching hotkeys in Settings ->
Region & Language -> Input Sources -> Options.
6. Observe that Keyboard shortcut for "Alternative switch to next source" is
set to "Alt + Shift" and that keyboard shortcuts can only be changed in
Settings -> Devices -> Keyboard -> Keyboard Shortcuts.
7. Observe that the shortcut for "Alternative switch to next source" is not
available for configuration in Settings -> Devices -> Keyboard -> Keyboard
Shortcuts.

Actual state:
* Performing step 4 does not select the previous app in application switcher
but instead changes keyboard input method.

Expected state:
* The shortcut for "Alternative switch to next source" can be changed and /
or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts.

Notes:
* The above was working fine in Ubuntu 17.10. I assume "Alternative switch to
next source" did not exist in that version of Gnome Shell.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions

--
Mailing list: https://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 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

The system is dual boot but Ubuntu and windows, both having their
separate partitions and DATA is the large common access partition for
both operating systems. The 158.43 GB primary is ubuntu with the
previous 3.73 GB as linux swap. DATA is the dump for both OSes

** Attachment added: "disk partitions.PNG"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773235/+attachment/5144411/+files/disk%20partitions.PNG

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  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/+bug/1773235/+subscriptions

-- 
Mailing list: https://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 1769654] Re: Ubuntu 18.04 embedded fonts Liberation have corrupted metrics

2018-05-25 Thread Scott Cowles Jacobs

I am using LibreOffice-Writer 1:6.0.3-0ubuntu1 on Lubuntu Next 18.04, and found 
when opening a previously-created document, that the pages did not line up.
Searching for LO-W bugs that referenced line-spacing, eventually led me to the 
original reporter's bug, and then to the debian bug report that you list in 
comment #5:
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898116)
where they reported that the bug had been:
"Fixed in version fonts-liberation/1:1.07.4-6"
The version I had was 1:1.07.4-5, just as the original reporter.

So, I snagged the "cosmic" package* (not yet available for "bionic")
and tried it, and it definitely solves my problem.

*see: https://packages.ubuntu.com/cosmic/all/fonts-liberation/download
and (probably) follow the advice at the top: add the deb line to your
repository list (selecting an appropriate URI mirror site for your area).

I suppose that it will be available for bionic, soon, but needed it
sooner...

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

Title:
  Ubuntu 18.04 embedded fonts Liberation have corrupted metrics

Status in fonts-liberation package in Ubuntu:
  New
Status in fonts-liberation2 package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Confirmed
Status in fonts-liberation package in Debian:
  Fix Released
Status in fonts-liberation2 package in Debian:
  Fix Released

Bug description:
  Ubuntu/Xubuntu 18.04 package includes fonts "Liberation Sans" (etc
  "Liberation") with sligtly shrinked font metrics. This issue leads to
  all office documents typed in Liberation Sans fonts have corrupted
  formatting in Ubuntu 18.04 (but these documents correctly opened in
  other OS's, for example Ubuntu 17.10). Documents with corrupted
  formatting can not print properly: all paragraphs are shifted up,
  embedded tables in text - splitted on page breaks. Document
  circulation in system based on Ubuntu 18.04 operating systems
  temporarily paralized, because Liberation fonts are basic fonts for
  open-source document circulation.

  In attachment I have type a example office document with 2 pages and
  enumerated strings. On normal ordinary conditions this document have
  54 strings on first page and 54 string on second page. But if this
  document open in Ubuntu 18.04, it's found than 5 strings from second
  page moves to first page. Compare font versions embedded with Ubuntu
  packages we can see that versions are different (sudo apr search
  fonts-liberation* command):

  Ubuntu 17.10 - 1:1.07.4-2, 2.00.1-3
  Ubuntu 18.04 - 1:1.07.4-5, 2.00.1-5

  I have create a bug 117411 "Font metrics slightly changed after update
  OS to Ubuntu 18.04", see
  https://bugs.documentfoundation.org/show_bug.cgi?id=117411, but I
  think that this bug concerns a Ubuntu/Xubuntu 18.04 package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-liberation/+bug/1769654/+subscriptions

-- 
Mailing list: https://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 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

This is when the system goes into emergency mode

** Attachment added: "IMG_20180525_215300112[1].jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773235/+attachment/5144409/+files/IMG_20180525_215300112%5B1%5D.jpg

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  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/+bug/1773235/+subscriptions

-- 
Mailing list: https://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 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

Krishnan Sreenivas:

To clarify, regarding the drive you installed Ubuntu on, are you either
dual booting with Windows, or manually created an NTFS partition?

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  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/+bug/1773235/+subscriptions

-- 
Mailing list: https://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 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

This is when the system boots to the login even though DATA.mount failed

** Attachment added: "IMG_20180525_214648275_HDR[1].jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773235/+attachment/5144408/+files/IMG_20180525_214648275_HDR%5B1%5D.jpg

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  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/+bug/1773235/+subscriptions

-- 
Mailing list: https://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 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

How do i upload the video of event happening with quiet splash disabled
(file size of video is 684 MB), Downscaling can bring it to 37mb but the
system does not boot into the gui and that is not the error that comes
up when quiet splash is turned off. I will run the code in the above
comment and get back to you

** Attachment added: "Issue.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773235/+attachment/5144389/+files/Issue.png

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  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/+bug/1773235/+subscriptions

-- 
Mailing list: https://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 11222] Re: Add auto-organize support

** Changed in: rhythmbox
   Status: New => Expired

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

Title:
  Add auto-organize support

Status in Banshee:
  Fix Released
Status in Exaile:
  Confirmed
Status in Rhythmbox:
  Expired
Status in rhythmbox package in Ubuntu:
  Invalid

Bug description:
  In iTunes, there is a feature which, when enabled, automatically sorts all 
music
  files
  into directories by artist and album.  While Sound Juicer does do this to an
  extent, there is no
  current way to achieve this when importing already-ripped songs into Rhythmbox
  (like backups made in iTunes - 
  which aren't sorted into directories).  Thus, it would be nice if the ability 
to
  auto-sort imported music files
  into directories was added to Rhythmbox.

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

-- 
Mailing list: https://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 1629633] Re: evince displays blank thumbnails for some pages

** Changed in: evince
   Status: Unknown => Expired

** Changed in: evince
   Importance: Unknown => Medium

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

Title:
  evince displays blank thumbnails for some pages

Status in Evince:
  Expired
Status in evince package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  To reproduce this bug:

   - load the attached PS file into evince
   - if thumbnails are not displayed then press F9 and choose to display 
thumbnails
   - evince displayd a blank thumbnail for pages 6 and 7

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: evince 3.22.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8
  Uname: Linux 4.8.0-19-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Oct  2 10:10:28 2016
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1773087] Re: Remove python3-apport as dependency of xserver-xorg

Jörn Heissler, as mentioned previously, apport (which python3-apport is a 
dependent of) is used to capture and process program crashes (e.g. xorg and 
related packages). For more on apport, please see:
https://wiki.ubuntu.com/Apport

apt-rdepends apport
Reading package lists... Done
Building dependency tree   
Reading state information... Done
apport
  Depends: gir1.2-glib-2.0 (>= 1.29.17)
  Depends: lsb-base (>= 3.0-6)
  Depends: python3
  Depends: python3-apport (>= 2.20.9-0ubuntu7)
  Depends: python3-gi
gir1.2-glib-2.0
  Depends: libgirepository-1.0-1 (>= 1.45.4)
  Depends: libglib2.0-0 (>= 2.56.1)
libgirepository-1.0-1
  Depends: libc6 (>= 2.14)
  Depends: libffi6 (>= 3.0.4)
  Depends: libglib2.0-0 (>= 2.56.1)
libc6
  Depends: libgcc1
libgcc1
  Depends: gcc-8-base (= 8-20180414-1ubuntu2)
  Depends: libc6 (>= 2.14)
gcc-8-base
libffi6
  Depends: libc6 (>= 2.14)
libglib2.0-0
  Depends: libc6 (>= 2.17)
  Depends: libffi6 (>= 3.0.4)
  Depends: libmount1 (>= 2.19.1)
  Depends: libpcre3
  Depends: libselinux1 (>= 1.32)
  Depends: zlib1g (>= 1:1.2.2)
libmount1
  Depends: libblkid1 (>= 2.17.2)
  Depends: libc6 (>= 2.25)
  Depends: libselinux1 (>= 2.6-3~)
libblkid1
  Depends: libc6 (>= 2.25)
  Depends: libuuid1 (>= 2.16)
libuuid1
  Depends: libc6 (>= 2.25)
libselinux1
  Depends: libc6 (>= 2.14)
  Depends: libpcre3
libpcre3
  Depends: libc6 (>= 2.14)
zlib1g
  Depends: libc6 (>= 2.14)
lsb-base
python3
  Depends: libpython3-stdlib (= 3.6.5-3)
  Depends: python3.6 (>= 3.6.5-2~)
  PreDepends: python3-minimal (= 3.6.5-3)
libpython3-stdlib
  Depends: libpython3.6-stdlib (>= 3.6.5-2~)
libpython3.6-stdlib
  Depends: libbz2-1.0
  Depends: libc6 (>= 2.15)
  Depends: libdb5.3
  Depends: libffi6 (>= 3.0.4)
  Depends: liblzma5 (>= 5.1.1alpha+20120614)
  Depends: libmpdec2
  Depends: libncursesw5 (>= 6)
  Depends: libpython3.6-minimal (= 3.6.5-3)
  Depends: libreadline7 (>= 7.0~beta)
  Depends: libsqlite3-0 (>= 3.5.9)
  Depends: libtinfo5 (>= 6)
  Depends: mime-support
libbz2-1.0
  Depends: libc6 (>= 2.4)
libdb5.3
  Depends: libc6 (>= 2.17)
liblzma5
  Depends: libc6 (>= 2.17)
libmpdec2
  Depends: libc6 (>= 2.14)
libncursesw5
  Depends: libc6 (>= 2.14)
  Depends: libtinfo5 (= 6.1-1ubuntu1)
libtinfo5
  Depends: libc6 (>= 2.16)
libpython3.6-minimal
  Depends: libc6 (>= 2.14)
  Depends: libssl1.1 (>= 1.1.0)
libssl1.1
  Depends: debconf (>= 0.5)
  Depends: debconf-2.0
  Depends: libc6 (>= 2.14)
debconf
  PreDepends: perl-base (>= 5.20.1-3~)
perl-base
  PreDepends: dpkg (>= 1.17.17)
  PreDepends: libc6 (>= 2.23)
dpkg
  Depends: tar (>= 1.28-1)
  PreDepends: libbz2-1.0
  PreDepends: libc6 (>= 2.14)
  PreDepends: liblzma5 (>= 5.2.2)
  PreDepends: libselinux1 (>= 2.3)
  PreDepends: libzstd1 (>= 1.3.2)
  PreDepends: zlib1g (>= 1:1.1.4)
tar
  PreDepends: libacl1 (>= 2.2.51-8)
  PreDepends: libc6 (>= 2.17)
  PreDepends: libselinux1 (>= 1.32)
libacl1
  Depends: libattr1 (>= 1:2.4.46-8)
  Depends: libc6 (>= 2.14)
libattr1
  Depends: libc6 (>= 2.4)
libzstd1
  Depends: libc6 (>= 2.14)
debconf-2.0
libreadline7
  Depends: libc6 (>= 2.15)
  Depends: libtinfo5 (>= 6)
  Depends: readline-common
readline-common
  Depends: dpkg (>= 1.15.4)
  Depends: install-info
install-info
  Depends: libc6 (>= 2.14)
  PreDepends: dpkg (>= 1.16.1)
libsqlite3-0
  Depends: libc6 (>= 2.14)
mime-support
python3.6
  Depends: libpython3.6-stdlib (= 3.6.5-3)
  Depends: mime-support
  Depends: python3.6-minimal (= 3.6.5-3)
python3.6-minimal
  Depends: libexpat1 (>= 2.1~beta3)
  Depends: libpython3.6-minimal (= 3.6.5-3)
  Depends: zlib1g (>= 1:1.2.0)
  PreDepends: libc6 (>= 2.25)
libexpat1
  Depends: libc6 (>= 2.25)
python3-minimal
  Depends: dpkg (>= 1.13.20)
  Depends: python3.6-minimal (>= 3.6.5-2~)
python3-apport
  Depends: lsb-release
  Depends: python3-apt (>= 0.7.9)
  Depends: python3-httplib2
  Depends: python3-problem-report (>= 0.94)
  Depends: python3-requests-unixsocket
  Depends: python3:any (>= 3.3.2-2~)
lsb-release
  Depends: distro-info-data
  Depends: python3:any (>= 3.4~)
distro-info-data
python3:any
python3-apt
  Depends: libapt-inst2.0 (>= 1.4~beta3)
  Depends: libapt-pkg5.0 (>= 1.4~beta3)
  Depends: libc6 (>= 2.14)
  Depends: libgcc1 (>= 1:3.0)
  Depends: libstdc++6 (>= 5.2)
  Depends: python-apt-common
  Depends: python3 (>= 3.6~)
  Depends: python3:any (>= 3.3.2-2~)
libapt-inst2.0
  Depends: libapt-pkg5.0 (>= 1.1~exp9)
  Depends: libc6 (>= 2.14)
  Depends: libgcc1 (>= 1:3.0)
  Depends: libstdc++6 (>= 5.2)
libapt-pkg5.0
  Depends: libbz2-1.0
  Depends: libc6 (>= 2.27)
  Depends: libgcc1 (>= 1:3.0)
  Depends: liblz4-1 (>= 0.0~r127)
  Depends: liblzma5 (>= 5.1.1alpha+20120614)
  Depends: libstdc++6 (>= 5.2)
  Depends: libudev1 (>= 183)
  Depends: libzstd1 (>= 1.3.2)
  Depends: zlib1g (>= 1:1.2.2.3)
liblz4-1
  Depends: libc6 (>= 2.14)
libstdc++6
  Depends: gcc-8-base (= 8-20180414-1ubuntu2)
  Depends: libc6 (>= 2.18)
  Depends: libgcc1 (>= 1:4.2)
libudev1
  Depends: libc6 (>= 2.25)
python-apt-common
python3-httplib2
  Depends: ca-certificates
  Depe

[Desktop-packages] [Bug 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

Krishnan Sreenivas:

1) The boot log attached notes:
[[0;1;31mFAILED[0m] Failed to mount /media/DATA.
See 'systemctl status media-DATA.mount' for details.

Please execute the following command in a terminal from a failed boot and post 
the full results here:
systemctl status media-DATA.mount

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  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/+bug/1773235/+subscriptions

-- 
Mailing list: https://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 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_c

This bug was fixed in the package gnome-control-center -
1:3.28.1-0ubuntu4

---
gnome-control-center (1:3.28.1-0ubuntu4) cosmic; urgency=medium

  [ Andrea Azzarone ]
* debian/patches/git_invalid_dereferencing.patch:
- Avoid dereferencing invalid pointer (lp: #1759468)

 -- Sebastien Bacher   Fri, 25 May 2018 16:25:16
+0200

** Changed in: gnome-control-center (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  gnome-control-center (11) gtk_style_context_clear_property_cache →
  gtk_css_widget_node_update_style → gtk_css_node_ensure_style →
  gtk_css_node_ensure_style → gtk_css_node_validate_internal

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  gnome-control-center sometimes hits a segfault

  * Test case
  - Check if the e.u.c reports stop with the new version

  or

  - Open GNOME Control Center
  - Go to Devices->Display panel
  - Close the window
  - Open GNOME Control Center again (in overview mode) 

  the settings should open without error

  * Regression potential
  check the panels can be opened without error and that switching between them 
works as well

  --

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.28.0-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/6b1f4dd86167bf5eb53ddca8469b5084208ddd22 
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/gnome-control-center/+bug/1759468/+subscriptions

-- 
Mailing list: https://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 1766799] Re: gnome-control-center (ERROR) ../shell/cc-panel-list.c → 926 → cc_panel_list_set_active_panel → assertion failed → (data != NULL)

This bug was fixed in the package gnome-control-center -
1:3.28.1-0ubuntu4

---
gnome-control-center (1:3.28.1-0ubuntu4) cosmic; urgency=medium

  [ Andrea Azzarone ]
* debian/patches/git_invalid_dereferencing.patch:
- Avoid dereferencing invalid pointer (lp: #1759468)

 -- Sebastien Bacher   Fri, 25 May 2018 16:25:16
+0200

** Changed in: gnome-control-center (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  gnome-control-center (ERROR) ../shell/cc-panel-list.c → 926 →
  cc_panel_list_set_active_panel → assertion failed → (data != NULL)

Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.28.1-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/73835fe215683e2f5f85df231eb2750a57e96c65 
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/gnome-control-center/+bug/1766799/+subscriptions

-- 
Mailing list: https://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 1773378] Re: New thunderbolt panel

This bug was fixed in the package gnome-control-center -
1:3.28.1-0ubuntu4

---
gnome-control-center (1:3.28.1-0ubuntu4) cosmic; urgency=medium

  [ Andrea Azzarone ]
* debian/patches/git_invalid_dereferencing.patch:
- Avoid dereferencing invalid pointer (lp: #1759468)

 -- Sebastien Bacher   Fri, 25 May 2018 16:25:16
+0200

** Changed in: gnome-control-center (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  New thunderbolt panel

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

Bug description:
  * Impact

  Ubuntu 18.04 includes desktop integration for thunderbolt devices
  though bolt and recent GNOME integration. The settings part of the
  feature missed 18.04 but landed upstream since. The new panel allows
  to review the list of authorized devices and revoke access, see
  https://christian.kellner.me/2018/04/23/the-state-of-thunderbolt-3-in-
  fedora-28/ for details (fedora backported the feature in there recent
  28 version)

  * Test case

  - Connect a thunderbolt device
  - Accept the authentification
  - Go to settings -> devices -> thunderbolt

  The device should be listed as "authorized"

  You can also try to disable the authorization and see that the device
  gets correctly denied then

  * Regression impact

  It's a new UI so there is no possible regression in an existing
  fonctionnality.

  Note that the new strings have been manually added to the bionic translations 
template some time ago which means they should have a correct level of 
translations in the next langpacks update
  https://lists.ubuntu.com/archives/ubuntu-translators/2018-May/007496.html

  The patches serie has a small change of behaviour in that subpanel use
  the main settings icons now, that solves the issue were some panels
  didn't have a correct icon (including the thunderbolt one).

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

-- 
Mailing list: https://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 1773431] [NEW] polkid uses CPU extensively, laptop becomes very hot

2018-05-25 Thread Ivan Yarych

Public bug reported:

At some point polkitd starts to consume CPU power and nothing helps to
make it eat less - only a reboot. This causes laptop to overheat and
coolers spin like crazy.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: policykit-1 0.105-20
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Fri May 25 21:28:23 2018
ExecutablePath: /usr/lib/policykit-1/polkitd
InstallationDate: Installed on 2017-01-31 (478 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: policykit-1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: policykit-1 (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  polkid uses CPU extensively, laptop becomes very hot

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  At some point polkitd starts to consume CPU power and nothing helps to
  make it eat less - only a reboot. This causes laptop to overheat and
  coolers spin like crazy.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: policykit-1 0.105-20
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri May 25 21:28:23 2018
  ExecutablePath: /usr/lib/policykit-1/polkitd
  InstallationDate: Installed on 2017-01-31 (478 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1773431/+subscriptions

-- 
Mailing list: https://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 1527663] Re: firefox 43 Accept-Language header does not follow preferences

2018-05-25 Thread Yvan Masson

** Bug watch added: Debian Bug tracker #873672
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873672

** Also affects: firefox-esr (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873672
   Importance: Unknown
   Status: Unknown

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

Title:
  firefox 43 Accept-Language header does not follow preferences

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in firefox-esr package in Debian:
  Unknown

Bug description:
  on a french firefox, possibly on all non english installs of firefox 43 on 
Ubuntu 15.10,
  the Accept-Language header is set to en_US regardless of the language 
preferences.
  It started with the upgrade to ff43, and the issue exists event when creating 
a new profile.

  How to Reproduce :
  Create a new profile on a firefox in french, go to any website, 
Accept-Language HTTP header does not contain "fr"
  (I could reproduce the bug in a virtualized 15.10)

  Workaround :
  about:preferences#content > Languages: choose
  Change order, click OK
  Languages: choose (again) Change order back, click OK
  Now the Accept-Language header is correctly set

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

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

Re: [Desktop-packages] [Bug 1768615] Re: Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

2018-05-25 Thread Tomáš Klos

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

Title:
  Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  in Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu desktop via 
X.org, a wrong display driver is used (llvmpipe). It will cause a horribly poor 
performance due to software acceleration.
  When I switch to Wayland, the correct driver (intel) with enabled hardware 
acceleration is loaded.

  I have two exactly the same laptops, the same issue on both.

  Hardware:
  HP ProBook 4330s
  Intel i5-2430M
  8GB RAM
  512GB SDD
  Kernel: 4.15.0-20-generic

  Installed packages:

  ii  intel-gpu-tools1.22-1 
 
  ii  intel-microcode3.20180312.0~ubuntu18.04.1 
 
  ii  libdrm-intel1:amd642.4.91-2   

  ii  libdrm-intel1:i386 2.4.91-2  

  ii  libegl-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libegl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:i386   18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:i386   18.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:i386 18.0.0~rc5-1ubuntu1
 
  ii  libgles2-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglu1-mesa:amd64 9.0.0-2.1build1
 
  ii  libglu1-mesa:i386  9.0.0-2.1build1
 
  ii  libglx-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libglx-mesa0:i386  18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:amd64   18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:i38618.0.0~rc5-1ubuntu1
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  mesa-utils 8.4.0-1
 
  ii  mesa-va-drivers:amd64  18.0.0~rc5-1ubuntu1
 
  ii  mesa-vdpau-drivers:amd64   18.0.0~rc5-1ubuntu1 

  ii  libva-wayland2:amd64   2.1.0-3
 
  ii  libwayland-client0:amd64   1.14.0-2   
 
  ii  libwayland-cursor0:amd64   1.14.0-2   
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libwayland-server0:amd64   1.14.0-2   
 
  ii  xwayland   2:1.19.6-1ubuntu4 

  ii  xserver-xorg-video-intel   2:2.99.917+git20171229-1
  ii  xorg-docs-core 1:1.7.1-1.1
 
  ii  xserver-xorg   1:7.7+19ubuntu7
 
  ii  xserver-xorg-core  2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-input-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-input-libinput0.27.1-1   
 
  ii  xserver-xorg-input-wacom   1:0.36.1-0ubuntu1  
 
  ii  xserver-xorg-legacy2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-video-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-video-amdgpu  18.0.1-1   
 
  ii  xserver-xorg-video-ati 1:18.0.1-1 
 
  ii  xserver-xorg-

[Desktop-packages] [Bug 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

** Summary changed:

- I get booted into recovery mode every third boot or from sleep when on battery
+ [ASUS R554LA] I get booted into recovery mode every third boot or from sleep 
when on battery

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  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/+bug/1773235/+subscriptions

-- 
Mailing list: https://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 38759] Re: Rhythmbox 'forgets' what's on my iRiver H320 DAP (and takes 5 min. to rescan every time I execute it)

** Changed in: rhythmbox
   Status: Confirmed => Expired

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

Title:
  Rhythmbox 'forgets' what's on my iRiver H320 DAP (and takes 5 min. to
  rescan every time I execute it)

Status in Rhythmbox:
  Expired
Status in rhythmbox package in Ubuntu:
  Triaged

Bug description:
  *Every* time I restart Rhythmbox it has to rescan the entire player
  (20gigs!). I have to wait approx. 5 minutes before I can access all my
  music.

  Does it do the same with an iPod?

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

-- 
Mailing list: https://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 1734541] Re: encrypted home-directory is not unmounted on logout

2018-05-25 Thread Star Man

Sorry, this are my system specs:

Ubuntu 18.04 LTS amd64
GNOME Shell desktop
Ecryptfs IN USE
kernel Linux 4.15.0-22-generic x86_64

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

Title:
  encrypted home-directory is not unmounted on logout

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

Bug description:
  Current Situation:

  If you log out from an user account with an encrypted home directory,
  it is not automatically unmounted and encrypted again.

  Expected behaviour:

  If I log out from an user account with an encrypted home directory, Id expect 
the homedir to be unmounted and encrypted again.
  Stepts to reproduce:

  log into an account with encrypted home directory. (lets call it: user)
  Log out again
  log into another account (which has sudo rights, lets call it: user2)

  and now enter the following into a terminal:

  user2@ubuntu: sudo su
  user2@ubuntu: ls -la /home/user

  you can see the files of the user

  Reasons:
  This is a security issue, because as a user you can reasonable expect your 
data to be safe, if you log out. if you would simply log in as another user but 
keep your data accessable you would simply switch user, instead of loggin out.
  Many users only suspend their laptop while carrying it with them. Logging out 
and suspending the user expects to have at least the home directory encrypted.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.26.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 26 16:18:39 2017
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1769614] Re: Unable to set "When the Power Button is pressed" to Ask or Interactive

2018-05-25 Thread Jeremy Bicha

The Power Off option in that drop down **is** the 'interactive'
gsettings setting. I believe that is an intentional decision by the
gnome-control-center maintainers to use that for Power Off.

See this upstream report:
https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/39

In the Ubuntu session, "Power Off" (interactive) is the default in
Ubuntu 18.04 LTS.

I'm closing this bug since this is a bit of a design decision and should
be handled upstream if changes need to be made.

One thing you could do though is have the gnome-user-docs user help
explain what "Power Off" does. (It does the same thing as the power
button in the system status menu in the top right of GNOME Shell.)

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  Unable to set "When the Power Button is pressed" to Ask or Interactive

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

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 18.04 on real hardware (since there is a some bug 1769372 
VirtualBox)
  2. Login to session
  3. Open GNOME Control Center, Power (or simply `gnome-control-center power`)
  4. Try to set "When the Power Button is pressed" to Ask or Interactive

  Expected results:
  there is an option to Ask user (or Interactive) dialog

  Actual results:
  there is no option to Ask user (or Interactive) dialog

  Workaround:
  set such option from terminal with `gsettings set 
org.gnome.settings-daemon.plugins.power power-button-action interactive` (it 
will work, but will not be shown in `gnome-control-center power`)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  7 13:10:19 2018
  InstallationDate: Installed on 2018-05-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1772542] Re: after waking from sleep i get text radeon error message then return login screen

Chris Guiver:

1) Regarding hibernate not working, if you would like to pursue a fix for this, 
it is out of scope for this report. However, you may file a new report about it 
via a terminal:
ubuntu-bug linux

2) To clarify, did you have issues after sleep/resume in 17.10?

3) In regards to sleep/resume testing, when folks are vetting
sleep/resume, they typically do 30-50 consecutive sleep cycles to rule
out one offs. It wouldn't hurt to do this to see if a sleep/resume issue
may be reproduced this way.

4) With regard to root cause, a few other possibilities:
* This issue could be the fall out of a failed sleep/resume versus apps not 
working. The reproduction of this could depend on how long you have the 
computer in sleep, how long it was in use prior to sleep, what apps you have 
running prior to sleep, and/or other factors (i.e. misbehaving 
drivers/firmware).
* When you upgraded from 17.10, there could have been some cruft left over from 
the upgrade, that when caffeine was removed and re-installed, it was reset to 
default configuration.

Hence, we can keep an eye on this given you did some preliminary testing
without reproduction, and allow more testing results to be reviewed.

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

Title:
  after waking from sleep i get text radeon error message then return
  login screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE
  desktops added)

  I sleep my XFCE (xubuntu) machine rather than turning it off at night.

  Today as with yesterday morning, instead of getting the locker-screen
  after hitting the power-button to wake my machine, i get a blank
  screen with a RADEON two-line text message top left on screen which
  appear only momentarily as screen is erased and I get the
  login/greeter screen.

  (it's happened 4-5 times, but does NOT happen every time)

  I can login fine, but my xfce session is new.

  I have grep'd for the message I see (yesterday & today), but can't
  find it as i usually recall little but the radeon word...

  sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:01:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0
     resources: irq:30 memory:e000-efff memory:f7de-f7df 
ioport:dc00(size=256) memory:c-d

  guiverc@d960-ubu2:/var/crash$   pwd
  /var/crash
  guiverc@d960-ubu2:/var/crash$   ls -la
  total 35332
  drwxrwsrwt  2 rootwhoopsie 4096 May 22 09:41 .
  drwxr-xr-x 15 rootroot 4096 Nov 16  2017 ..
  -rw-r-  1 guiverc whoopsie50003 May 21 10:32 
_usr_bin_caffeine.1000.crash
  -rw-r-  1 guiverc whoopsie   880121 May 21 10:33 
_usr_bin_light-locker.1000.crash
  -rw-rw-r--  1 guiverc whoopsie0 May 21 10:33 
_usr_bin_light-locker.1000.upload
  -rw-r-  1 guiverc whoopsie 35234566 May 21 10:32 
_usr_lib_xorg_Xorg.1000.crash
  (these files are dated yesteday - i didn't find anything for today)

  extract of /var/log/auth.log  (copied from `view` hence line numbers)
  // last-night
   48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
  // overnight
   52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
opened for user root by (uid=0)
   53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
closed for user root
   54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' 
finished.
   58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): 
session closed

[Desktop-packages] [Bug 1773235] Re: I get booted into recovery mode every third boot or from sleep when on battery

I now got an error like this after the plymouth splash screen and now the 
system just hangs up after the splash screen.
A start job is running for Hold until boot process finishes up (42m/no limit)

at the boot if i use alt+ctrl+f2,
I have only run sudo apt update && sudo apt upgrade and have installed wine 
from ubuntu database, Zotero and calibre. This issue was present from the 
initial install but increased in frequency. Please do tell me the location of 
the files you will need and i can use a linux reader on windows to get the 
files. The system goes into emergency mode or just hangs up when entering the 
command line now, I have tried dpkg using recovery mode only and it returns 
with no changes. I also had changed the Plymouth logo from the ubuntu directory 
but did not encounter issues after the change

** Attachment added: "the boot log file that was not attached"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773235/+attachment/5144357/+files/boot.log

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

Title:
  I get booted into recovery mode every third boot or from sleep when on
  battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  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/+bug/1773235/+subscriptions

-- 
Mailing list: https://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 1772414] Re: Justifying Syriac text creates clutter in LibreOffice Writer

2018-05-25 Thread Miikka-Markus Alhonen

Here's the PDF for the Arabic example, where you can see additional
lines in the first paragraph (justified) but not in the second one
(right-aligned).

** Attachment added: "arabic-clutter.pdf"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1772414/+attachment/5144359/+files/arabic-clutter.pdf

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

Title:
  Justifying Syriac text creates clutter in LibreOffice Writer

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Justifying a paragraph in LibreOffice Writer with text written in the
  Syriac script (Unicode block U+0700-U+074F) creates graphic clutter
  between every word. See the attached screenshot where the first
  paragraph is justified and the second is right-aligned. The second
  paragraph looks as it should, whereas the first paragraph shows a
  small line added at the end of each word. If you zoom in or out, some
  of the lines may disappear, but when you create a PDF, they are all
  there.

  The same problem occurs with nearly all the Syriac fonts I have tried,
  including Serto Batnan, Estrangelo Antioch, East Syriac Ctesiphon and
  Serto Urhoy (all part of the ttf-xfree86-nonfree-syriac package). For
  the last two, the clutter is not visible on screen but shows up if you
  create a PDF. With East Syriac Adiabene, the problem doesn't seem to
  occur. I have attached a screenshot, a PDF and the document used to
  create them.

  Description:  Ubuntu 17.10
  Release:  17.10

  libreoffice-writer:
Installed: 1:5.4.6-0ubuntu0.17.10.1
Candidate: 1:5.4.6-0ubuntu0.17.10.1
Version table:
   *** 1:5.4.6-0ubuntu0.17.10.1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.4.5-0ubuntu0.17.10.5 500
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
   1:5.4.1-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 21 13:26:09 2018
  InstallationDate: Installed on 2017-02-13 (462 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-11-05 (196 days ago)

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

-- 
Mailing list: https://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 34795] Re: "authentication failed" on "switch user" with timed login