[Desktop-packages] [Bug 1731111] Re: libreoffice crashes immediately

[Launchpad Bug Tracker]

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

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

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

Title:
  libreoffice crashes immediately

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  kyle@SOONG:~/src/testing$ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="16.04.3 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.3 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial

  kyle@SOONG:~/src/testing$ apt-cache policy libreoffice
  libreoffice:
Installed: 1:5.1.6~rc2-0ubuntu1~xenial2
Candidate: 1:5.1.6~rc2-0ubuntu1~xenial2
Version table:
   *** 1:5.1.6~rc2-0ubuntu1~xenial2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.1.2-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  This is a relatively new install.  I can't open libreoffice at all
  without it instantly crashing.  Nothing unusual from the terminal,
  just some GTK warnings.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice 1:5.1.6~rc2-0ubuntu1~xenial2
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Wed Nov  8 21:18:44 2017
  InstallationDate: Installed on 2017-10-30 (10 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+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 1753576] Re: GDM freeze

[Launchpad Bug Tracker]

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

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

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

Title:
  GDM freeze

Status in gdm3 package in Ubuntu:
  Expired
Status in gnome-shell package in Ubuntu:
  Expired
Status in xorg package in Ubuntu:
  Expired

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Mar  5 11:17:58 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu2

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

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

[Desktop-packages] [Bug 1753576] Re: GDM freeze

[Launchpad Bug Tracker]

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

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

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

Title:
  GDM freeze

Status in gdm3 package in Ubuntu:
  Expired
Status in gnome-shell package in Ubuntu:
  Expired
Status in xorg package in Ubuntu:
  Expired

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Mar  5 11:17:58 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu2

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

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

[Desktop-packages] [Bug 1753576] Re: GDM freeze

[Launchpad Bug Tracker]

[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 xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1753576

Title:
  GDM freeze

Status in gdm3 package in Ubuntu:
  Expired
Status in gnome-shell package in Ubuntu:
  Expired
Status in xorg package in Ubuntu:
  Expired

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Mar  5 11:17:58 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu2

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

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

[Desktop-packages] [Bug 1761844] Re: Very large emojis displayed in subject line and in the email list

[Jeremy Bicha]

I think this bug is actually surprisingly a duplicate of bug 1644021
which we fixed in the PPA several months ago.

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

Title:
  Very large emojis displayed in subject line and in the email list

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

Bug description:
  The list of emails received from Thunderbird shows emojis. This does not 
happen with all accounts.
  It appears to be with the last email address added.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:52.6.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   diego  1607 F...m pulseaudio
   /dev/snd/controlC0:  diego  1607 F pulseaudio
   /dev/snd/controlC1:  diego  1607 F pulseaudio
  BuildID: 20180131200234
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 15:58:17 2018
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-04-05 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  IpRoute:
   default via 181.31.1.1 dev enp2s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp2s0 scope link metric 1000 
   181.31.1.0/24 dev enp2s0 proto kernel scope link src 181.31.1.84 metric 100
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=52.6.0/20180131200234 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: GA-78LMT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd08/14/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1769415] Re: package totem-plugins 3.26.0-0ubuntu1 failed to install/upgrade: there is no script in the new version of the package - giving up

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package totem-plugins 3.26.0-0ubuntu1 failed to install/upgrade: there
  is no script in the new version of the package - giving up

Status in totem package in Ubuntu:
  New

Bug description:
  Install failed after upgrade from 16.04 to 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: totem-plugins 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Sat May  5 10:48:45 2018
  ErrorMessage: there is no script in the new version of the package - giving up
  InstallationDate: Installed on 2016-11-16 (535 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: totem
  Title: package totem-plugins 3.26.0-0ubuntu1 failed to install/upgrade: there 
is no script in the new version of the package - giving up
  UpgradeStatus: Upgraded to artful on 2018-05-05 (0 days ago)

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

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

[Desktop-packages] [Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

Lars, I went to sites like Gmail or Youtube that I thought had a chance
of using optional NaCl, but I haven't been able to reproduce those error
messages. I don't think Firefox supports NaCl, even with a plugin. Is it
possible you imported browser settings from Chromium and it happened to
include their NaCl extension? You could rule this out by moving or
deleting ~/.mozilla/firefox then trying again.

herrtimson, an illegal instruction would indicate your system lacks NEON
or ARMv7 altogether, the same reason Firefox does not run on ARMv6
boards like Raspberry Pi B+ or Pi Zero. To check, cat /proc/cpuinfo

There's also a chance that ungültiger maschienenbefehl means bad
interpreter or not in executable format / File format not recognized.
You can troubleshoot this with the ldd and file commands. Compare
properties of /usr/lib/firefox/firefox to any working command under
/usr/bin

> Oh, and how do I revert this to the ubuntu one? *_*

sudo apt-get purge firefox
sudo apt-get install firefox

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

Status in Mozilla Firefox:
  Expired
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Firefox always crashes when launched after the 55.0.1 update on an
  Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi),
  even in safe mode.

  I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for
  ARM single-board computer) on a similar board (Orange Pi Plus 2e),
  installed Firefox and experienced the same problem--it won't load
  without crashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 55.0.1+build2-0ubuntu0.16.04.2
  Uname: Linux 3.4.113-sun8i armv7l
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: armhf
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jim1138 F pulseaudio
   /dev/snd/controlC0:  jim1138 F pulseaudio
  BuildID: 20170814194718
  Card0.Amixer.info:
   Card hw:0 'audiocodec'/'audiocodec'
 Mixer name : ''
 Components : ''
 Controls  : 12
 Simple ctrls  : 12
  Card1.Amixer.info:
   Card hw:1 'sndhdmi'/'sndhdmi'
 Mixer name : ''
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'hdmi audio format Function',0
 Capabilities: enum
 Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' 
'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO'
 Item0: 'pcm'
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Thu Aug 17 05:37:00 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.10.1 dev eth0 
   default via 192.168.10.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.10.0/24 dev eth0  proto kernel  scope link  src 192.168.10.107 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.108  
metric 600
  Locales: extensions.sqlite corrupt or missing
  PciMultimedia:
   
  PciNetwork:
   
  Profiles: Profile0 (Default) - LastVersion=55.0.1/20170814194718
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1769415] [NEW] package totem-plugins 3.26.0-0ubuntu1 failed to install/upgrade: there is no script in the new version of the package - giving up

[Tim Membrino]

Public bug reported:

Install failed after upgrade from 16.04 to 17.10

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: totem-plugins 3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
Date: Sat May  5 10:48:45 2018
ErrorMessage: there is no script in the new version of the package - giving up
InstallationDate: Installed on 2016-11-16 (535 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: totem
Title: package totem-plugins 3.26.0-0ubuntu1 failed to install/upgrade: there 
is no script in the new version of the package - giving up
UpgradeStatus: Upgraded to artful on 2018-05-05 (0 days ago)

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


** Tags: amd64 apport-package artful

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

Title:
  package totem-plugins 3.26.0-0ubuntu1 failed to install/upgrade: there
  is no script in the new version of the package - giving up

Status in totem package in Ubuntu:
  New

Bug description:
  Install failed after upgrade from 16.04 to 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: totem-plugins 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Sat May  5 10:48:45 2018
  ErrorMessage: there is no script in the new version of the package - giving up
  InstallationDate: Installed on 2016-11-16 (535 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: totem
  Title: package totem-plugins 3.26.0-0ubuntu1 failed to install/upgrade: there 
is no script in the new version of the package - giving up
  UpgradeStatus: Upgraded to artful on 2018-05-05 (0 days ago)

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

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

[Desktop-packages] [Bug 1769358] Re: Thumbnail previews in Files/Nautilus only show when zoom is 150% or more

[David]

** Tags added: regression-release

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

Title:
  Thumbnail previews in Files/Nautilus only show when zoom is 150% or
  more

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04 LTS
  Nautilus package: 1:3.26.3-0ubuntu4

  I don't get thumbnail previews in Files (Nautilus) at the default zoom
  level when using List view.

  If I select 150% in the hamburger menu the thumbnails are displayed,
  and they are displayed in Grid view at all sizes. They are also
  displayed in the Open File dialog, even though the icon size there is
  smaller than in Files!

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

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

[Desktop-packages] [Bug 1765911] Re: Major performance regression from Ubuntu 17.10 with i915

[Jacob Zimmermann]

UPDATE: I installed kernel 4.16.7 from http://kernel.ubuntu.com/~kernel-
ppa/mainline/ and things get much better. Not as good as it was on 17.10
but largely usable. Some regression in the i915 driver must have
occurred in 4.15 and now it's catching up again apparently.

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

Title:
  Major performance regression from Ubuntu 17.10 with i915

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Desktop performance on my laptop (Intel HD 520, driver: i915) used to
  be generally good on previous Ubuntu releases but on 18.04, there is a
  VERY noticeable regression. Moving windows around in GNOME is choppy
  and tearing. It gets dramatic after the laptop resumes from suspend,
  GNOME drops to literally ~1-2 FPS. Logging out and restarting the
  session usually fixes the problem in that it restores the barely
  acceptable performance level prior to suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 21 16:04:38 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:8079]
   Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] 
(rev 81) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f]
  InstallationDate: Installed on 2018-04-03 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  MachineType: HP HP EliteBook 850 G3
  ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-15-lowlatency.efi.signed 
root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro 
rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash 
module.sig_enforce=1 intel_pstate=skylake_hwp vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.10
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.6F
  dmi.chassis.asset.tag: 5CG6351LQL
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 850 G3
  dmi.sys.vendor: HP
  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/1765911/+subscriptions

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

[Desktop-packages] [Bug 1769410] [NEW] Some GNOME apps are not appearing on store.

[Anderson de Araujo]

Public bug reported:

Hi,
I m using Ubuntu Budgie 18.04 32-bits LTS.

A lot snap apps are not appearing on my Store, likes Spotify, Brave... When I 
try install Spotify from the Spotify website, I have a message: “dont know how 
to handle snap//spotify”.
Its happening with "repository apps" too, that I try install on Tilix: I have 
installed Opera Browser (opera-stable), but after the instalation, it does not 
appear in mine programs.

Someone can help me? (PS: I’m new to Ubuntu, and I know almost nothing.)

My PC: 
Intel® Core™2 Quad CPU Q6600 @ 2.40GHz × 4
RAM 4 GB
Graphics Intel® G33 x86/MMX/SSE2
GNOME 3.28.1

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic i686
ApportVersion: 2.20.9-0ubuntu7
Architecture: i386
CurrentDesktop: Budgie:GNOME
Date: Sat May  5 20:26:59 2018
InstallationDate: Installed on 2018-05-05 (0 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.28.1-0ubuntu4
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug bionic i386

** Attachment added: "Print screen: i search Spotify, but have no results"
   
https://bugs.launchpad.net/bugs/1769410/+attachment/5134593/+files/Captura%20de%20tela%20de%202018-05-05%2020-59-15.png

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

Title:
  Some GNOME apps are not appearing on store.

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Hi,
  I m using Ubuntu Budgie 18.04 32-bits LTS.

  A lot snap apps are not appearing on my Store, likes Spotify, Brave... When I 
try install Spotify from the Spotify website, I have a message: “dont know how 
to handle snap//spotify”.
  Its happening with "repository apps" too, that I try install on Tilix: I have 
installed Opera Browser (opera-stable), but after the instalation, it does not 
appear in mine programs.

  Someone can help me? (PS: I’m new to Ubuntu, and I know almost
  nothing.)

  My PC: 
  Intel® Core™2 Quad CPU Q6600 @ 2.40GHz × 4
  RAM 4 GB
  Graphics Intel® G33 x86/MMX/SSE2
  GNOME 3.28.1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic i686
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: i386
  CurrentDesktop: Budgie:GNOME
  Date: Sat May  5 20:26:59 2018
  InstallationDate: Installed on 2018-05-05 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1769409] [NEW] Support for global menu

[Dimitrij Mijoski]

Public bug reported:

The move to Gnome from Unity was ok except for two major features that
got lost and those are global menus and pixel saving when maximized.

Are there any chances of official support in future releases?

Gnome extension for global menus exists https://github.com/lestcape
/Gnome-Global-AppMenu and that may be used as a starting point. The
Ubuntu team already did similar move by including the plugin dash-to-
dock.

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

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

Title:
  Support for global menu

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The move to Gnome from Unity was ok except for two major features that
  got lost and those are global menus and pixel saving when maximized.

  Are there any chances of official support in future releases?

  Gnome extension for global menus exists https://github.com/lestcape
  /Gnome-Global-AppMenu and that may be used as a starting point. The
  Ubuntu team already did similar move by including the plugin dash-to-
  dock.

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

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

[Desktop-packages] [Bug 1722487] Re: Failing to open some pictures - Improper call to JPEG library in state 200

[Simon P.]

Bug is still present in 18.04 and eog 3.28.1

** Changed in: eog (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  Failing to open some pictures - Improper call to JPEG library in state
  200

Status in eog package in Ubuntu:
  Confirmed

Bug description:
  When I am inserting the SD card of my camera in the PC and have a look
  at the pictures, eog sometimes fails to show them, giving this error:
  Improper call to JPEG library in state 200

  I get that error when I am using the keyboard arrows to go back and forth 
between the pictures I took. The next time I try to open the picture, it is 
shown without a problem.
  --- 
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-09-30 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Package: eog 3.26.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1723362] Re: gnome-software spams error messages to journald and causes 100% CPU usage

[Jason]

This also affects me,

May  5 17:45:33 hulk gnome-software[8798]: g_byte_array_remove_range: assertion 
'index_ + length <= array->len' failed
May  5 17:45:33 hulk gnome-software[8798]: Ignoring unexpected response
May  5 17:45:33 hulk gnome-software[8798]: g_byte_array_remove_range: assertion 
'index_ + length <= array->len' failed
May  5 17:45:33 hulk gnome-software[8798]: Ignoring unexpected response
May  5 17:45:33 hulk gnome-software[8798]: g_byte_array_remove_range: assertion 
'index_ + length <= array->len' failed
May  5 17:45:33 hulk gnome-software[8798]: Ignoring unexpected response


Continues to fill up /var/log file system.

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

Title:
  gnome-software spams error messages to journald and causes 100% CPU
  usage

Status in GNOME Software:
  Unknown
Status in gnome-software package in Ubuntu:
  Invalid
Status in snapd-glib package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Confirmed
Status in snapd-glib source package in Xenial:
  Confirmed
Status in gnome-software source package in Artful:
  Confirmed
Status in snapd-glib source package in Artful:
  Confirmed
Status in gnome-software source package in Bionic:
  Invalid
Status in snapd-glib source package in Bionic:
  Fix Released

Bug description:
  gnome-software spams this message to journald:

  Okt 13 11:00:19 zenbook gnome-software[3582]: g_byte_array_remove_range: 
assertion 'index_ + length <= array->len' failed
  Okt 13 11:00:19 zenbook gnome-software[3582]: Ignoring unexpected response

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 13 10:58:38 2017
  InstallationDate: Installed on 2016-10-25 (352 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.1-0ubuntu1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to artful on 2017-10-04 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1723362/+subscriptions

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

[Desktop-packages] [Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program

[Sergei Morozov]

> But there is one moment, keyboard layout still switch on key RELEASE

Same here. It's better than OOTB but still requires switching back after
Ctrl + Shift is pressed.

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

Title:
  Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes
  shortcuts with ctrl+shift, etc not working in any program

Status in GNOME Settings Daemon:
  Fix Released
Status in GNOME Shell:
  Won't Fix
Status in Unity:
  Confirmed
Status in X.Org X server:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in kubuntu-meta package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged
Status in gnome-settings-daemon package in ALT Linux:
  Unknown
Status in gnome-settings-daemon package in Debian:
  New
Status in gnome-settings-daemon package in Fedora:
  In Progress
Status in gnome-settings-daemon package in openSUSE:
  Confirmed

Bug description:
  Tried only with ctrl+shift, maybe behaves the same for other modifier
  key combinations when used as shortcut for switching layouts.

  - Set ctrl+shift as shortcut for switching keyboard layouts
  - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work 
(actually Terminal window loses focus when ctrl+shift is pressed, and layout is 
switched)

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Mon Oct 28 16:40:02 2013
  InstallationDate: Installed on 2013-10-23 (5 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1245473/+subscriptions

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

[Desktop-packages] [Bug 1727356] Re: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed

[Traumflug]

With 18.04 the situation got worse. Apparently, the login screen tries
to run now on Wayland as well, so the opportunity to turn it off is
gone. Booting simply stops at the Ubuntu logo, with the first of these
five dots filled.

Booting in recovery mode, then choosing 'continue'(?) gives a black
screen most of the time, with some text blinking up shortly from time to
time. Managed to catch it, see attached picture.

The only way I could get this PC up running after the 18.04 upgrade was
to boot into recovery mode, then get a root shell, then edit
/etc/gdm3/custom.conf to remove the comment sign in front of
WaylandEnable..., then reboot.

** Attachment added: "Screen photograph"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727356/+attachment/5134590/+files/DSCF1218.JPG

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

Title:
  Wayland does not start up on "Integrated Graphics Chipset: Intel(R)
  G33": Shader compilation failed

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

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  Upgraded from 17.04 today.

  Steps to reproduce:

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

  Expected to happen:

  Desktop appears.

  Actually happening:

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

  Partial diagnosis:

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

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

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

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

[Desktop-packages] [Bug 1589215] Re: 'Unknown Application Name' menu item in Indicator Applet Appmenu when LibreOffice is running

[G C]

Confirmed on Ubuntu 18.04 Unity, fresh install, latest LibreOffice 6.0.3 from 
repo.
Fine on 16.04.

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

Title:
  'Unknown Application Name' menu item in Indicator Applet Appmenu when
  LibreOffice is running

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Sometimes I get the issue of a menu having the name of a different
  application and being unusable, or being an application menu for the
  focused window but being titled 'Unknown Application Name', with
  LibreOffice. I also get this with GNOME apps but was told that this is
  a separate issue to the one I reported here:
  https://bugs.launchpad.net/ubuntu/+source/gnome-
  calculator/+bug/1584720 (see comment #5).

  The issue is with using Indicator Applet Appmenu in the panel on
  gnome-flashback installed on standard Ubuntu (which I call Ubuntu
  (GNOME) Flashback).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice-writer 1:5.1.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jun  5 10:32:35 2016
  InstallationDate: Installed on 2016-04-26 (39 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1381415] Re: Can't create new folder in "List" view

[Bug Watch Updater]

** Changed in: nautilus
   Status: Confirmed => Fix Released

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

Title:
  Can't create new folder in "List" view

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  If i click right button in list view of nautilus, i don't see "create
  folder" menuitem. And for creating new folder i must change view to
  "grid", create folder, and then change view back to list.

  I can create folder in list view only if in folder few files, and
  lower part of window is free from files, then my right click of mouse
  will be recognized as click_on_free_space, but in windows with many
  files, if i click anywere in windows, i click on file.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.3
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 15 20:58:37 2014
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2014-10-04 (11 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1637369] Re: Can no longer paste a file in nautilus without keyboard

[Bug Watch Updater]

** Changed in: nautilus
   Status: Confirmed => Fix Released

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

Title:
  Can no longer paste a file in nautilus without keyboard

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  In file list mode, nautilus used to either have a paste option in the
  titlebar menu or via a menu that could be opened from a "cog" symbol
  at the right-hand top of its window (and for a while, via the right-
  click menu if you right-clicked on whitespace instead of a file name).

  But the only non-keyboard option I can find in nautilus
  1:3.20.3-1ubuntu3.1 now is the right-click menu, but this is not
  available when the nautilus window is full of filenames (as in the
  attached screenshot), so pasting is impossible without the keyboard in
  this case.

  What happened to the "cog" menu? IIRC correctly this was present until
  quite recently.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 28 10:42:19 2016
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'885x494+65+24'"
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
  InstallationDate: Installed on 2016-08-12 (76 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160812)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

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

[Desktop-packages] [Bug 1768906] Re: Xorg crash

[Cyrus Harmon]

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

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

Title:
  Xorg crash

Status in gdm package in Ubuntu:
  Confirmed

Bug description:
  When attempting to log in to a newly updated bionic beaver via the
  display manager (I think this is the right term), I immediately see a
  crash, a return to the user selection/login screen and a no-longer
  functioning keyboard and mouse. This happens both with the proprietary
  driver installed drivers and with the apt installed nvidia-driver-396.

  some interesting tidbits from the syslog file are:

  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): 
Failed to acquire modesetting permission.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): 
Failing initialization of X screen 0
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: 
"nvidia"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "wfb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "fb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) 
found, but none have a usable configuration.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE)
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error:
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens 
found(EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency 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  396.24  Thu Apr 26 00:10:09 
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'
  CompositorRunning: None
  Date: Thu May  3 09:28:59 2018
  DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774]
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-lowlatency 
root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAXIMUS VI GENE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  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 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
  xserver.bootTime: Thu May  3 09:20:03 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1769403] [NEW] USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude

[KP]

Public bug reported:

Hi,

I am facing the problem that is similar to the one described in the
thread: https://ubuntuforums.org/showthread.php?t=2342985

Laptop (Dell Latitude 6420) randomly stops responding to the usb
Trackball and Keyboard. Unplugging & plugging them back into a different
port does not fix the problem. Sometimes the problem is fixed after
rebooting or suspending the laptopo, then turning it on; but the problem
re-appears almost immediately - after 10".

The problem is related to the Logitech trackman wheel & Mircosoft PS2
Keyboard, both are old.

Command "lsusb" for the 2 devices gives:
Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel
Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse 
Adapter

Command "tlp-stat -u" for the 2 devices gives:
Bus 002 Device 005 ID 046d:c404 control = on,   autosuspend_delay_ms = -1000 -- 
Logitech, Inc. TrackMan Wheel (usbhid)
Bus 002 Device 006 ID 0a81:0205 control = on,   autosuspend_delay_ms = -1000 -- 
Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid)

Command "uname -ra" gives:
Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

This problem tends to be very frustrating.

note: I think this is not related with autosuspend, but rather with
buffer overflow for the specific devices due to that they are not
supported in the kernel code.

Regards

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


** Tags: 16.04.4 autosuspend buffer freeze polling ubuntu usb

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

Title:
  USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate
  16.04.4 , and DELL latitude

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  I am facing the problem that is similar to the one described in the
  thread: https://ubuntuforums.org/showthread.php?t=2342985

  Laptop (Dell Latitude 6420) randomly stops responding to the usb
  Trackball and Keyboard. Unplugging & plugging them back into a
  different port does not fix the problem. Sometimes the problem is
  fixed after rebooting or suspending the laptopo, then turning it on;
  but the problem re-appears almost immediately - after 10".

  The problem is related to the Logitech trackman wheel & Mircosoft PS2
  Keyboard, both are old.

  Command "lsusb" for the 2 devices gives:
  Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel
  Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse 
Adapter

  Command "tlp-stat -u" for the 2 devices gives:
  Bus 002 Device 005 ID 046d:c404 control = on,   autosuspend_delay_ms = -1000 
-- Logitech, Inc. TrackMan Wheel (usbhid)
  Bus 002 Device 006 ID 0a81:0205 control = on,   autosuspend_delay_ms = -1000 
-- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid)

  Command "uname -ra" gives:
  Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  This problem tends to be very frustrating.

  note: I think this is not related with autosuspend, but rather with
  buffer overflow for the specific devices due to that they are not
  supported in the kernel code.

  Regards

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

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

[Desktop-packages] [Bug 1756610] Re: luks encrypted USB key cannot be opened on fully encrypted OS

[peterzay]

This bug is no longer present in the final release of Ubuntu 18.04 LTS.


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

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

Title:
  luks encrypted USB key cannot be opened on fully encrypted OS

Status in gedit package in Ubuntu:
  Fix Released

Bug description:
  ***
  Please change this bug from gedit to the correct package.
  ***

  A USB key encrypted with the Disks utility always pops up a password
  input window upon insertion into systems with an encrypted home
  directory.

  This is no longer the case.  Note that fully encrypted system
  installation was used for this OS (Ubuntu 18.04 beta) because
  encrypted home directory was not offered by the installation DVD (Bug
  #1756600).

  However, launching file manager does show an encrypted drive is
  available for mounting and opening.

  When clicking on the USB key in file manager to mount and open the
  drive, the expected password input window appears.

  Unfortunately, entering the password produces the following error (see
  attached screenshot): Error unlocking /dev/sdb1: The function
  'bd_cryto_luks_open_blob' called, but not implemented!

  In Ubuntu 16.04 with encrypted home directory, the drive opens like a
  charm in file manager after password input.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gedit 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 17 17:07:14 2018
  InstallationDate: Installed on 2018-03-10 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Kirill Romanov]

Why this have "Fix released" status? I cannot login after "prime-select
intel", I see only a black screen

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

Title:
  nvidia-390 fails to boot graphical display

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

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

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

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

[Desktop-packages] [Bug 1768906] Re: Xorg crash

[Cyrus Harmon]

Switching to lightdm instead of gdm3 gets around the problem. Should I
change the component to gdm3?

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When attempting to log in to a newly updated bionic beaver via the
  display manager (I think this is the right term), I immediately see a
  crash, a return to the user selection/login screen and a no-longer
  functioning keyboard and mouse. This happens both with the proprietary
  driver installed drivers and with the apt installed nvidia-driver-396.

  some interesting tidbits from the syslog file are:

  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): 
Failed to acquire modesetting permission.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): 
Failing initialization of X screen 0
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: 
"nvidia"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "wfb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "fb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) 
found, but none have a usable configuration.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE)
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error:
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens 
found(EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency 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  396.24  Thu Apr 26 00:10:09 
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'
  CompositorRunning: None
  Date: Thu May  3 09:28:59 2018
  DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774]
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-lowlatency 
root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAXIMUS VI GENE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  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 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
  xserver.bootTime: Thu May  3 09:20:03 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Emiliano]

I tried #116 by @minterior, and I now have a working desktop, but it
feels substantially more sluggish than it was under 17.10.

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

Title:
  nvidia-390 fails to boot graphical display

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

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

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

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

[Desktop-packages] [Bug 1769358] Re: Thumbnail previews in Files/Nautilus only show when zoom is 150% or more

[Launchpad Bug Tracker]

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

** Changed in: nautilus (Ubuntu)
   Status: New => Confirmed

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

Title:
  Thumbnail previews in Files/Nautilus only show when zoom is 150% or
  more

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04 LTS
  Nautilus package: 1:3.26.3-0ubuntu4

  I don't get thumbnail previews in Files (Nautilus) at the default zoom
  level when using List view.

  If I select 150% in the hamburger menu the thumbnails are displayed,
  and they are displayed in Grid view at all sizes. They are also
  displayed in the Open File dialog, even though the icon size there is
  smaller than in Files!

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

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

[Desktop-packages] [Bug 1769400] [NEW] suspend no longer functions after update to 18.04

[James]

Public bug reported:

Suspend does not complete. The system stops in an unknown state without
fully suspending and without ability to wake.

Problem began on upgrade to Ubuntu 18.04 LTS.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pm-utils 1.4.1-17
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: Unity:Unity7:ubuntu
Date: Sat May  5 13:31:03 2018
InstallationDate: Installed on 2015-03-25 (1137 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
PackageArchitecture: all
SourcePackage: pm-utils
UpgradeStatus: Upgraded to bionic on 2018-05-04 (1 days ago)

** Affects: pm-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  suspend no longer functions after update to 18.04

Status in pm-utils package in Ubuntu:
  New

Bug description:
  Suspend does not complete. The system stops in an unknown state
  without fully suspending and without ability to wake.

  Problem began on upgrade to Ubuntu 18.04 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pm-utils 1.4.1-17
  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: Unity:Unity7:ubuntu
  Date: Sat May  5 13:31:03 2018
  InstallationDate: Installed on 2015-03-25 (1137 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: Upgraded to bionic on 2018-05-04 (1 days ago)

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

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Emiliano]

I've just ran do-release-upgrade on a Lenovo P51, and the systems hangs
just after "Starting Session c1 of user gdm". I get a little further by
purging nvidia-* (I get the GDM greeter again) but after logging in
there, the screen freezes and a little later I'm kicked back to the
greeter.

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

Title:
  nvidia-390 fails to boot graphical display

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

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

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

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Cédric]

@Thijs Kaper: I have the exact same problem.

My alternative workaround:
Like you I authenticate, black screen after typing the password and hitting 
enter. Then I go to tty2, authenticate in the terminal, and type 'startx' (and 
4 times Ctrl+C). And finally KDE starts without problem on tty2. This is crazy.


Like @Bernadette Addison I had huge icons. It was impossible to set a higher 
resolution with the KDE display manager. So I used xrandr:
xrandr --output eDP-1-1 --mode 1920x1200 --scale 1x1
for example.
The resolution is fine even after a reboot.


I also want to add that I am actually using the nvidia driver 396.24. Because I 
had so much problems before... I tried to add the graphics-driver ppa as 
advised by @Chris McDonough. I do not know if finally this helped me a little. 
Maybe I should switch back to 390.


My graphical interface is really a mess since the upgrade to 18.04 :-(

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

Title:
  nvidia-390 fails to boot graphical display

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

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

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

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

[Desktop-packages] [Bug 386037] Re: Nautilus gives no error message if an application fails to start

[Bug Watch Updater]

** Changed in: nautilus
   Status: Confirmed => 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/386037

Title:
  Nautilus gives no error message if an application fails to start

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: nautilus

  If I try to run an application by double clicking it in Nautilus and
  the application for some reason fails to start I get no error message.
  If I try to run the same application in the Terminal, I always get an
  error message such as "Segmentation fault (core dumped)", "error while
  loading shared libraries: xx.so.0: cannot open shared object file:
  No such file or directory" or "./a.out: Permission denied".  Without
  an error message it is impossible to tell what went wrong and if the
  application did something or not. Nautilus should show the error
  messages too. Even better it should give a solution to the problem
  such as offering to install a missing package or asking if the user
  want's to give the file execute permission.

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

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

[Desktop-packages] [Bug 1748656] Re: Black Screen of Death after logging into Ubuntu Bionic: "Failed to acquire modesetting permission"

[Cyrus Harmon]

I'm wondering if this could be related to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768906

Might it make sense to unexpire this 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/1748656

Title:
  Black Screen of Death after logging into Ubuntu Bionic: "Failed to
  acquire modesetting permission"

Status in xorg package in Ubuntu:
  Expired

Bug description:
  **Specs:** Ubuntu Bionic; NVidia GTX 1070 w/`nvidia-387` drivers.

  **Problem:** After installing a new GTX 1070 and installing
  `nvidia-387`, I get a black screen of death AFTER logging into Ubuntu
  (i.e., the login screen shows up just fine). I'm not even able to
  access other TTYs (the error logs below were retrieved via SSH).

  **/var/log/Xorg.0.log** There doesn't seem to be anything problematic
  in this file.

  **/var/log/Xorg.1.log** The problematic message seems to be:

  [26.455] (EE) NVIDIA(GPU-0): Failed to acquire modesetting permission.
  [26.455] (EE) NVIDIA(0): Failing initialization of X screen 0
  [26.455] (II) UnloadModule: "nvidia"
  [26.455] (II) UnloadSubModule: "wfb"
  [26.455] (II) UnloadSubModule: "fb"
  [26.455] (EE) Screen(s) found, but none have a usable configuration.
  [26.455] (EE) 
  Fatal server error:
  [26.455] (EE) no screens found(EE) 
  [26.455] (EE) 
  Please consult the The X.Org Foundation support 
  at http://wiki.x.org
  for help. 
  [26.455] (EE) Please also check the log file at "/var/log/Xorg.1.log" 
for additional information.
  [26.455] (EE) 
  [26.457] (EE) Server terminated with error (1). Closing log file.

  **Conf files.** Here are my conf files:

  $ cd /usr/share/X11
  $ find . -name "*.conf"
  ./xorg.conf.d/glamoregl.conf
  ./xorg.conf.d/10-amdgpu.conf
  ./xorg.conf.d/40-libinput.conf
  ./xorg.conf.d/50-nvidia-drm-outputclass.conf
  ./xorg.conf.d/50-nvidia-drm-outputclass.conf/nvidia-drm-outputclass.conf
  ./xorg.conf.d/10-quirks.conf
  ./xorg.conf.d/10-radeon.conf
  ./xorg.conf.d/70-wacom.conf

  I tried deleting all of these except for the nvidia one and rebooting,
  and the error persists. In addition, I tried deleting all of them and
  generating a new one via `sudo X -configure` but get

  $ cd /usr/share/X11$ 
  $ sudo pkill X && sudo X -configure  
  _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
  _XSERVTransMakeAllCOTSServerListeners: server already running
  (EE) 
  Fatal server error:
  (EE) Cannot establish any listening sockets - Make sure an X server isn't 
already running(EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
  at http://wiki.x.org
  for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.

  **kms.** Finally, in case relevant:

  $ lsmod | grep kms
  drm_kms_helper167936  1 nvidia_drm
  syscopyarea16384  1 drm_kms_helper
  sysfillrect16384  1 drm_kms_helper
  sysimgblt  16384  1 drm_kms_helper
  fb_sys_fops16384  1 drm_kms_helper
  drm   356352  6 nvidia_drm,drm_kms_helper

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-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  387.34  Tue Nov 21 03:09:00 
PST 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-18ubuntu2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Feb 10 13:14:48 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-25-generic, x86_64: installed
   nvidia-387, 387.34, 4.13.0-25-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 

[Desktop-packages] [Bug 1769380] Re: gnome-disk-utility translation issue in French

[Gunnar Hjalmarsson]

Hmm.. The strings are not:

"Edit Partition Type"
"Edit Filesystem Label"

They are:

"Edit Partition..."
"Edit Filesystem..."

"Type" and "Label" are separate strings which are shown in separate
windows.

Given that, I'm not convinced that anything is wrong here. So @Ame,
before suggesting any changes, can you please clarify which problem you
see in the light of what I just wrote.

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

** Changed in: gnome-disk-utility (Ubuntu)
   Status: New => Invalid

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

Title:
  gnome-disk-utility translation issue in French

Status in Ubuntu Translations:
  Incomplete
Status in gnome-disk-utility package in Ubuntu:
  Invalid

Bug description:
  In Ubuntu 18.04 in gnome-disk-utility 3.28.1,

  The menu on a partition says in English:
  -"Edit Partition Type"
  -"Edit Filesystem Label"

  In French, the translation is just wrong:
  -"Modifier la partition" NO
  -"Modifier le système de fichier" NO

  It SHOULD be:
  -"Modifier le système de fichier" YES
  -"Modifier le nom de la partition" YES

  Thank you to correct that soon, it's kind of a big deal.
  The bug was there before, I just didn't reported it.

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

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

[Desktop-packages] [Bug 1769395] [NEW] screen fade out

[serkan türkkolu]

Public bug reported:

screen fade out

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
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sat May  5 22:44:15 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 620 [17aa:505b]
InstallationDate: Installed on 2018-04-07 (28 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint 
Reader
 Bus 001 Device 003: ID 5986:2109 Acer, Inc 
 Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20H1006MTX
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=5fcf40ca-beff-4360-9559-5c878a16f54b ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/09/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: R0DET83W (1.83 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20H1006MTX
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR0DET83W(1.83):bd06/09/2017:svnLENOVO:pn20H1006MTX:pvrThinkPadE470:rvnLENOVO:rn20H1006MTX:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E470
dmi.product.name: 20H1006MTX
dmi.product.version: ThinkPad E470
dmi.sys.vendor: LENOVO
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
xserver.bootTime: Sat May  5 22:36:58 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4
xserver.video_driver: modeset

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


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

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

Title:
  screen fade out

Status in xorg package in Ubuntu:
  New

Bug description:
  screen fade out

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat May  5 22:44:15 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:505b]
  InstallationDate: Installed on 2018-04-07 (28 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint 
Reader
   Bus 001 Device 003: ID 5986:2109 Acer, Inc 
   Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20H1006MTX
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=5fcf40ca-beff-4360-9559-5c878a16f54b ro quiet splash vt.handoff=1
  

[Desktop-packages] [Bug 1765911] Re: Major performance regression from Ubuntu 17.10 with i915

[Max Bowsher]

Similar/same issue observed on HP Spectre 13 (2017 model) which has
exactly the same Intel HD 520 graphics. Bad enough that I had to
reinstall 17.10.

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

Title:
  Major performance regression from Ubuntu 17.10 with i915

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Desktop performance on my laptop (Intel HD 520, driver: i915) used to
  be generally good on previous Ubuntu releases but on 18.04, there is a
  VERY noticeable regression. Moving windows around in GNOME is choppy
  and tearing. It gets dramatic after the laptop resumes from suspend,
  GNOME drops to literally ~1-2 FPS. Logging out and restarting the
  session usually fixes the problem in that it restores the barely
  acceptable performance level prior to suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 21 16:04:38 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:8079]
   Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] 
(rev 81) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f]
  InstallationDate: Installed on 2018-04-03 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  MachineType: HP HP EliteBook 850 G3
  ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-15-lowlatency.efi.signed 
root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro 
rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash 
module.sig_enforce=1 intel_pstate=skylake_hwp vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.10
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.6F
  dmi.chassis.asset.tag: 5CG6351LQL
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 850 G3
  dmi.sys.vendor: HP
  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/1765911/+subscriptions

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

[Desktop-packages] [Bug 1765911] Re: Major performance regression from Ubuntu 17.10 with i915

[Launchpad Bug Tracker]

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

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

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

Title:
  Major performance regression from Ubuntu 17.10 with i915

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Desktop performance on my laptop (Intel HD 520, driver: i915) used to
  be generally good on previous Ubuntu releases but on 18.04, there is a
  VERY noticeable regression. Moving windows around in GNOME is choppy
  and tearing. It gets dramatic after the laptop resumes from suspend,
  GNOME drops to literally ~1-2 FPS. Logging out and restarting the
  session usually fixes the problem in that it restores the barely
  acceptable performance level prior to suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 21 16:04:38 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:8079]
   Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] 
(rev 81) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f]
  InstallationDate: Installed on 2018-04-03 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  MachineType: HP HP EliteBook 850 G3
  ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-15-lowlatency.efi.signed 
root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro 
rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash 
module.sig_enforce=1 intel_pstate=skylake_hwp vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.10
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.6F
  dmi.chassis.asset.tag: 5CG6351LQL
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 850 G3
  dmi.sys.vendor: HP
  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/1765911/+subscriptions

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

[Desktop-packages] [Bug 1769392] [NEW] BUG: networkmanager not able to disable IPv6 on OpenVPN Tap interface

[Gijs Peskens]

Public bug reported:

The system is configured to connect to an OpenVPN server set-up with tap
bridging.

On the remote server radvd is running on the bridged interface, in
assisted set-up mode. radvd advertises a ULA prefix (assisted with
DHCPv6) and a GUA prefix (slaac only)

The remote-server is set-up to push def1 gateway by default.

On the client 2 profiles are created; one with the intention of routing
all traffic through the VPN, one with the intention of only accessing
remote network sources.

For the secondary profile IPv4 address assignment is left on automatic,
route on manual with a static route configured for 10.0.0.0/8 through
10.0.1.1, the checkbox 'use network only for resources on its network'
is ticked.

For IPv6 every permutation of settings has been tried, none result in no IPv6 
addresses and associated routes getting assigned.
Even setting the IPv6 address assignment to Disabled still results in RA 
addresses getting assigned. 

Setting assignment to 'Disabled' /must/  remove the link local address on the 
tap interface, automatically failing any autoconf (RA autoconf depends on link 
local multicast) 
Setting assignment to 'Link-Local only' /must/ leave the ll address intact, 
while disabling autoconf (perhaps via sysctl)

Ideally (low priority) an extra variant setting would be introduced that
disallows GUA addressing to be assigned, but allows ULA addressing to be
assigned.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager-openvpn-gnome 1.2.10-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat May  5 21:25:43 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-03-18 (47 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
SourcePackage: network-manager-openvpn
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  BUG: networkmanager not able to disable IPv6 on OpenVPN Tap interface

Status in network-manager-openvpn package in Ubuntu:
  New

Bug description:
  The system is configured to connect to an OpenVPN server set-up with
  tap bridging.

  On the remote server radvd is running on the bridged interface, in
  assisted set-up mode. radvd advertises a ULA prefix (assisted with
  DHCPv6) and a GUA prefix (slaac only)

  The remote-server is set-up to push def1 gateway by default.

  On the client 2 profiles are created; one with the intention of
  routing all traffic through the VPN, one with the intention of only
  accessing remote network sources.

  For the secondary profile IPv4 address assignment is left on
  automatic, route on manual with a static route configured for
  10.0.0.0/8 through 10.0.1.1, the checkbox 'use network only for
  resources on its network' is ticked.

  For IPv6 every permutation of settings has been tried, none result in no IPv6 
addresses and associated routes getting assigned.
  Even setting the IPv6 address assignment to Disabled still results in RA 
addresses getting assigned. 

  Setting assignment to 'Disabled' /must/  remove the link local address on the 
tap interface, automatically failing any autoconf (RA autoconf depends on link 
local multicast) 
  Setting assignment to 'Link-Local only' /must/ leave the ll address intact, 
while disabling autoconf (perhaps via sysctl)

  Ideally (low priority) an extra variant setting would be introduced
  that disallows GUA addressing to be assigned, but allows ULA
  addressing to be assigned.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-openvpn-gnome 1.2.10-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 21:25:43 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-03-18 (47 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Thijs Kaper]

I'm using a Dell m4800, with "NVIDIA GK107GLM Quadro K1100M" (3840x2160
pixels). Symptom; gdm login screen shows normally, but after typing
password and hitting enter, I end up on black screen. This is after
upgrade from 17.10 to 18.04.

I found a silly workaround (after trying many many other suggestions /
driver re-installs), now using nvidia-driver-396 or nvidia-driver-390;
create (if not exists) a file /etc/rc.local, with this content:

#!/bin/bash

sleep 1

exit 0


And make it executable: chmod 755 /etc/rc.local

What also worked for me, is start laptop, wait for login screen, and use 
another machine to ssh into the laptop, and execute "sudo service gdm stop ; 
sleep 5 ; sudo service gdm start".
After that, I could normally log on.

For me this seems to indicate some sort of timing or initialization
issue...

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

Title:
  nvidia-390 fails to boot graphical display

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

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

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

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

[Desktop-packages] [Bug 1769380] Re: gnome-disk-utility translation issue in French

[Hans Joachim Desserud]

Thanks for taking your time to report this issue and help making Ubuntu
better.

Based on your description, the texts in question are:
https://translations.launchpad.net/ubuntu/bionic/+source/gnome-disk-utility/+pots/gnome-disk-utility/fr/583/+translate
https://translations.launchpad.net/ubuntu/bionic/+source/gnome-disk-utility/+pots/gnome-disk-utility/fr/608/+translate
https://translations.launchpad.net/ubuntu/bionic/+source/gnome-disk-utility/+pots/gnome-disk-utility/fr/584/+translate

Everyone can suggest translation, but as it says at the bottom of the
page they will need to be reviewed by the Ubuntu French Translators
team.

** Also affects: ubuntu-translations
   Importance: Undecided
   Status: New

** Tags added: bionic

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

Title:
  gnome-disk-utility translation issue in French

Status in Ubuntu Translations:
  New
Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  In Ubuntu 18.04 in gnome-disk-utility 3.28.1,

  The menu on a partition says in English:
  -"Edit Partition Type"
  -"Edit Filesystem Label"

  In French, the translation is just wrong:
  -"Modifier la partition" NO
  -"Modifier le système de fichier" NO

  It SHOULD be:
  -"Modifier le système de fichier" YES
  -"Modifier le nom de la partition" YES

  Thank you to correct that soon, it's kind of a big deal.
  The bug was there before, I just didn't reported it.

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

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

[Desktop-packages] [Bug 1675496] Re: Scrollbars are tiny in Firefox (since FF 52)

[Steve Cohen]

still an issue with Ubuntu 18.04/FF 59.2

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

Title:
  Scrollbars are tiny in Firefox (since FF 52)

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  == Update 2018-02-27: While this report was created for Firefox 52
  under Ubuntu 16.10, it is still valid for all newer Firefox
  version/Ubuntu releases. ==

  In Firefox 52, the size of scrollbars has become smaller so that it is
  really tiny and hard to grab by the mouse. For me, this is a usability
  issue.

  The scrollbars were considerably bigger in Firefox 51 and previous
  releases. To illustrate this, I have attached two screeenshots for
  comparision between Firefox 51 and 52.

  While other GTK3-applications (e.g. Gedit) also have very slim
  scrollbars, they on the other hand have a mechanismn that makes their
  scrollbars broaden automatically when you move the mouse over them, so
  grabbing them isn't an issue. If the same would be possible in
  Firefox, this would of course be also an acceptable resolution.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 52.0.1+build2-0ubuntu0.16.10.1
  ProcVersionSignature: Ubuntu 4.8.0-43.46-generic 4.8.17
  Uname: Linux 4.8.0-43-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jan2427 F pulseaudio
   /dev/snd/controlC0:  jan2427 F pulseaudio
  BuildID: 20170317212642
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Thu Mar 23 17:48:02 2017
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePlugins: Shockwave Flash - 
/usr/lib/flashplugin-installer/libflashplayer.so
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-11 (163 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  IpRoute:
   default via 192.168.2.1 dev enp4s0  proto static  metric 100
   192.168.2.0/24 dev enp4s0  proto kernel  scope link  src 192.168.2.110  
metric 100
  IwConfig:
   enp4s0no wireless extensions.

   vboxnet0  no wireless extensions.

   lono wireless extensions.
  MostRecentCrashID: bp-fd3ffe0d-b587-4fd6-9f51-0e92e2161201
  Profile0IncompatibleExtensions:
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  Profile0Plugins: Shockwave Flash - 
/usr/lib/flashplugin-installer/libflashplayer.so
  Profile0PrefSources:
   prefs.js
   user.js
   
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
  Profile1IncompatibleExtensions:
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  Profile1Plugins: Shockwave Flash - 
/usr/lib/flashplugin-installer/libflashplayer.so
  Profile1PrefSources:
   prefs.js
   user.js
  Profile2IncompatibleExtensions:
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  Profile2Plugins: Shockwave Flash - 
/usr/lib/flashplugin-installer/libflashplayer.so
  Profile2PrefSources: prefs.js
  Profile3IncompatibleExtensions:
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  Profile3Plugins: Shockwave Flash - 
/usr/lib/flashplugin-installer/libflashplayer.so
  Profile3PrefSources: prefs.js
  Profile4Extensions: extensions.sqlite corrupt or missing
  Profile4IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile4Locales: extensions.sqlite corrupt or missing
  Profile4Plugins: Shockwave Flash - 
/usr/lib/flashplugin-installer/libflashplayer.so
  Profile4PrefSources: prefs.js
  Profile4Themes: 

[Desktop-packages] [Bug 544286] Re: Allow setting passing password=... in .vnc file

[Launchpad Bug Tracker]

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

** Changed in: vinagre (Ubuntu)
   Status: New => Confirmed

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

Title:
  Allow setting passing password=... in .vnc file

Status in Vinagre: VNC client for GNOME:
  New
Status in vinagre package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: vinagre

  Vinagre is an VNC-protocol remote desktop client.  To connect to a remote 
machine, requires the IP address, an IP port number and optionally (but 
generally) a pssw.  I have encounter a grid provide that setups up a randomised 
short-term IP:port:password combination on an intermediate proxy server that 
then hands the data back and forth, hi

  Luckily it is possible to specify the connection to load in a '.vnc' file, 
which is mostly unconnection, but similar to:

 [connection]
 host=abcdef
 port=12345

  In the situation I'm hitting, I'd like to grab the one-time random
  tuple of IP:port:password, write these to a /tmp file and start up
  Vinagre.

  Ideally Vinagre should allow passing the password in a config/bookmark
  file to save the most complicated bit of re-typing.

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

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

[Desktop-packages] [Bug 1769388] [NEW] Unable to install package # 66.5159: dependency problems - leaving unconfigured

[antonio balentinu]

Public bug reported:

Unable to install package 
/tmp/apt-dpkg-install-hCWHsS/0412-libp11-kit-gnome-keyring_3.280.2-1ubuntu1_all.deb
# 66.5159: dependency problems - leaving unconfigured
I UPDATED FROM UBUNTU 17.10 TO UBUNTU 18.04 AND I HAVE BEEN REPORTED TO THE BUG 
TO MAKE ITEM WITH
 # 66.5159 WHAT DO YOU TELL ME?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libp11-kit-gnome-keyring 3.20.1-1ubuntu1
Uname: Linux 4.15.15-041515-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sat May  5 19:35:12 2018
Dependencies:
 gcc-8-base 8-20180414-1ubuntu2
 libc6 2.27-3ubuntu1
 libgcc1 1:8-20180414-1ubuntu2
InstallationDate: Installed on 2010-11-27 (2716 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LD_PRELOAD=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-keyring
UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)

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


** Tags: amd64 apport-bug bionic

** Description changed:

  Unable to install package 
/tmp/apt-dpkg-install-hCWHsS/0412-libp11-kit-gnome-keyring_3.280.2-1ubuntu1_all.deb
  # 66.5159: dependency problems - leaving unconfigured
- I UPDATED FROM UBUNTU 17.10 TO UBUNTU 18.04 AND I HAVE BEEN REPORTED TO THE 
BUG TO MAKE ITEM WITH 
-  # 66.5159 WHAT DO YOU TELL ME?
+ I UPDATED FROM UBUNTU 17.10 TO UBUNTU 18.04 AND I HAVE BEEN REPORTED TO THE 
BUG TO MAKE ITEM WITH
+  # 66.5159 WHAT DO YOU TELL ME?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libp11-kit-gnome-keyring 3.20.1-1ubuntu1
  Uname: Linux 4.15.15-041515-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat May  5 19:35:12 2018
  Dependencies:
-  gcc-8-base 8-20180414-1ubuntu2
-  libc6 2.27-3ubuntu1
-  libgcc1 1:8-20180414-1ubuntu2
+  gcc-8-base 8-20180414-1ubuntu2
+  libc6 2.27-3ubuntu1
+  libgcc1 1:8-20180414-1ubuntu2
  InstallationDate: Installed on 2010-11-27 (2716 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LD_PRELOAD=
-  LANG=it_IT.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LD_PRELOAD=
+  LANG=it_IT.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)

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

Title:
  Unable to install package # 66.5159: dependency problems - leaving
  unconfigured

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  Unable to install package 
/tmp/apt-dpkg-install-hCWHsS/0412-libp11-kit-gnome-keyring_3.280.2-1ubuntu1_all.deb
  # 66.5159: dependency problems - leaving unconfigured
  I UPDATED FROM UBUNTU 17.10 TO UBUNTU 18.04 AND I HAVE BEEN REPORTED TO THE 
BUG TO MAKE ITEM WITH
   # 66.5159 WHAT DO YOU TELL ME?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libp11-kit-gnome-keyring 3.20.1-1ubuntu1
  Uname: Linux 4.15.15-041515-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat May  5 19:35:12 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  InstallationDate: Installed on 2010-11-27 (2716 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LD_PRELOAD=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)

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

-- 
Mailing list: https://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 1768182] Re: The "Search" input field of "New Tab" of the Firefox browser can not be used depending on the theme.

[ichro furuya]

When reporting a problem with the Firefox browser, network setting
information and setting file are also attached and published. So I treated
it private.

This time, I deleted them myself. So, I think that there is no problem with
security even if it is made public.
Thank you.

2018-05-02 4:32 GMT+09:00 Seth Arnold <1768...@bugs.launchpad.net>:

> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. We appreciate the difficulties you are facing, but this appears
> to be a "regular" (non-security) bug.  I have unmarked it as a security
> issue since this bug does not show evidence of allowing attackers to
> cross privilege boundaries nor directly cause loss of data/privacy.
> Please feel free to report any other bugs you may find.
>
> ** Information type changed from Private Security to Public
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1768182
>
> Title:
>   The "Search" input field of "New Tab" of the Firefox browser can not
>   be used depending on the theme.
>
> Status in firefox package in Ubuntu:
>   New
>
> Bug description:
>   Ubuntu 18.04 LTS (Japanese environment)
>
>   kernel: 4.15.0-20-generic
>   GNOME Tweaks 3.28.1
>   GTK+ 3.22.30
>   Firefox Quantum 59.0.2(64 bit)
>
>   In "Adwaita-dark" theme, "Search" input field of "New Tab" of Firefox
>   browser can not be used.
>
>   1. Install Ubuntu 18.04 LTS in Japanese, with minimum configuration.
>   2. Install the "GNOME Tweaks" application.
>   3. Launch the "GNOME Tweaks" application and specify the "Appearance"
> tab -> Application: "Adwaita - dark".
>   4. Start Firefox and open "New Tab".
>   5. The above "URL address input field" is black, but since the input
> character is white, it is possible to judge the input character.
>   6. The "Search the web" entry below it is also black. The character I
> entered is black. So, I can not use it because I can not see the characters.
>
>   [Workaround](?)
>   Click the "gear" icon on the right side of the "Web search" input field,
> open the "New tab setting" screen and uncheck "Search".
>   The "Web search" input field disappears.
>
>   ---
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: firefox 59.0.2+build1-0ubuntu1
>   ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
>   Uname: Linux 4.15.0-20-generic x86_64
>   AddonCompatCheckDisabled: False
>   ApportVersion: 2.20.9-0ubuntu7
>   Architecture: amd64
>   BuildID: 20180406121424
>   Channel: Unavailable
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue May  1 12:28:13 2018
>   Extensions: extensions.sqlite corrupt or missing
>   ForcedLayersAccel: False
>   IfupdownConfig:
># interfaces(5) file used by ifup(8) and ifdown(8)
>auto lo
>iface lo inet loopback
>   IncompatibleExtensions: Unavailable (corrupt or non-existant
> compatibility.ini or extensions.sqlite)
>   InstallationDate: Installed on 2018-04-29 (1 days ago)
>   InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
>   Locales: extensions.sqlite corrupt or missing
>   PrefSources: prefs.js
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=ja_JP.UTF-8
>SHELL=/bin/bash
>   Profiles: Profile0 (Default) - LastVersion=59.0.2/20180406121424 (In
> use)
>   RunningIncompatibleAddons: False
>   SourcePackage: firefox
>   Themes: extensions.sqlite corrupt or missing
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 10/03/2014
>   dmi.bios.vendor: coreboot
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: GOOGLE
>   dmi.modalias: dmi:bvncoreboot:bvr:bd10/03/2014:svnGOOGLE:pnPanther:pvr1.
> 0:cvnGOOGLE:ct3:cvr:
>   dmi.product.name: Panther
>   dmi.product.version: 1.0
>   dmi.sys.vendor: GOOGLE
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/
> 1768182/+subscriptions
>

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

Title:
  The "Search" input field of "New Tab" of the Firefox browser can not
  be used depending on the theme.

Status in firefox package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 LTS (Japanese environment)

  kernel: 4.15.0-20-generic
  GNOME Tweaks 3.28.1
  GTK+ 3.22.30
  Firefox Quantum 59.0.2(64 bit)

  In "Adwaita-dark" theme, "Search" input field of "New Tab" of Firefox
  browser can not be used.

  1. Install Ubuntu 18.04 LTS in Japanese, with minimum configuration.
  2. Install the "GNOME Tweaks" application.
  3. Launch the "GNOME Tweaks" application and specify the "Appearance" tab -> 
Application: "Adwaita - dark".
  4. Start Firefox and open "New Tab".
  5. The above "URL address input field" is black, but since the input 
character is white, it is possible to judge the input character.
  6. The "Search the web" entry below 

[Desktop-packages] [Bug 1769386] Re: Cable network does not get recognized anymore, wifi works

[lotuspsychje]

*-network   
   description: Ethernet interface
   product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0.1
   bus info: pci@:02:00.1
   logical name: enp2s0f1
   version: 12
   serial: 80:fa:5b:3e:45:e2
   size: 1Gbit/s
   capacity: 1Gbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=full firmware=rtl8411-2_0.0.1 07/08/13 
latency=0 link=yes multicast=yes port=MII speed=1Gbit/s
   resources: irq:124 ioport:e000(size=256) memory:df114000-df114fff 
memory:df11-df113fff
  *-network
   description: Wireless interface
   product: Intel Corporation
   vendor: Intel Corporation
   physical id: 0
   bus info: pci@:03:00.0
   logical name: wlp3s0
   version: 78
   serial: 00:28:f8:81:66:ef
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
   configuration: broadcast=yes driver=iwlwifi 
driverversion=4.13.0-39-generic firmware=31.560484.0 ip=192.168.1.2 latency=0 
link=yes multicast=yes wireless=IEEE 802.11
   resources: irq:127 memory:df00-df001fff
maj@maj-N750BU:~$

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

Title:
  Cable network does not get recognized anymore, wifi works

Status in network-manager package in Ubuntu:
  New

Bug description:
  ubuntu 16.04 LTS cable does not connect anymore, wifi working

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May  5 19:27:18 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-09-30 (217 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.2  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICETYPE  STATE DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   wlp3s0wifi  connected /org/freedesktop/NetworkManager/Devices/1  
WiFi-2.4-3569  7103236e-31c4-43d6-871d-14f3cda4b657  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp2s0f1  ethernet  disconnected  /org/freedesktop/NetworkManager/Devices/2  
-- ---- 

   loloopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
-- ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1769386] [NEW] Cable network does not get recognized anymore, wifi works

[lotuspsychje]

Public bug reported:

ubuntu 16.04 LTS cable does not connect anymore, wifi working

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.6-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CurrentDesktop: Unity
Date: Sat May  5 19:27:18 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-09-30 (217 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
IpRoute:
 default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
 169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
 192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.2  metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICETYPE  STATE DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

 wlp3s0wifi  connected /org/freedesktop/NetworkManager/Devices/1  
WiFi-2.4-3569  7103236e-31c4-43d6-871d-14f3cda4b657  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 enp2s0f1  ethernet  disconnected  /org/freedesktop/NetworkManager/Devices/2  
-- ---- 

 loloopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
-- ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug xenial

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

Title:
  Cable network does not get recognized anymore, wifi works

Status in network-manager package in Ubuntu:
  New

Bug description:
  ubuntu 16.04 LTS cable does not connect anymore, wifi working

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May  5 19:27:18 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-09-30 (217 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.2  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICETYPE  STATE DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   wlp3s0wifi  connected /org/freedesktop/NetworkManager/Devices/1  
WiFi-2.4-3569  7103236e-31c4-43d6-871d-14f3cda4b657  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp2s0f1  ethernet  disconnected  /org/freedesktop/NetworkManager/Devices/2  
-- ---- 

   loloopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
-- ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1769380] [NEW] gnome-disk-utility translation issue in French

[Ame Nomade]

Public bug reported:

In Ubuntu 18.04 in gnome-disk-utility 3.28.1,

The menu on a partition says in English:
-"Edit Partition Type"
-"Edit Filesystem Label"

In French, the translation is just wrong:
-"Modifier la partition" NO
-"Modifier le système de fichier" NO

It SHOULD be:
-"Modifier le système de fichier" YES
-"Modifier le nom de la partition" YES

Thank you to correct that soon, it's kind of a big deal.
The bug was there before, I just didn't reported it.

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

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

Title:
  gnome-disk-utility translation issue in French

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  In Ubuntu 18.04 in gnome-disk-utility 3.28.1,

  The menu on a partition says in English:
  -"Edit Partition Type"
  -"Edit Filesystem Label"

  In French, the translation is just wrong:
  -"Modifier la partition" NO
  -"Modifier le système de fichier" NO

  It SHOULD be:
  -"Modifier le système de fichier" YES
  -"Modifier le nom de la partition" YES

  Thank you to correct that soon, it's kind of a big deal.
  The bug was there before, I just didn't reported it.

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

-- 
Mailing list: https://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 1768661] Re: can't make WIFI work

[Richard Schneider]

Thank you Dave,

I did get it working by some sort of magic that I cant quite explain. It 
works and I'm happy.

Thank you for the suggestion though.

Best regards,

Rich S.


On 05/05/2018 03:08 AM, Dave Goldsbrough wrote:
> At a terminal screen have you tried entering the command?
>
> sudo service network-manager restart
>

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

Title:
  can't make WIFI work

Status in xorg package in Ubuntu:
  New

Bug description:
  I can't make the WIfFI operate Compact Presario V2000

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic i686
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.27
  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: Wed May  2 17:05:59 2018
  DistUpgraded: 2018-05-01 16:52:36,093 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: ndiswrapper, 1.59: added
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS480M [Mobility Radeon Xpress 200] 
[1002:5955] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:3091]
  InstallationDate: Installed on 2018-05-01 (1 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  Lsusb:
   Bus 001 Device 011: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 
802.11n Wireless Network Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Hewlett-Packard Presario V2000 (EP377UA#ABA)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic 
root=UUID=3698752e-32a7-443e-959d-c4578e3e85a3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2018-05-01 (1 days ago)
  dmi.bios.date: 01/02/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.22
  dmi.board.name: 3097
  dmi.board.vendor: Quanta
  dmi.board.version: 47.0F
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.22:bd01/02/2006:svnHewlett-Packard:pnPresarioV2000(EP377UA#ABA):pvrRev1:rvnQuanta:rn3097:rvr47.0F:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: Presario V2000 (EP377UA#ABA)
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 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: Wed May  2 12:26:46 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1~trusty1
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1769372] Re: Ubuntu 18.04 LTS does not ask for action when I press ACPI Power button/key - immediately shutdowns

[Jeremy Bicha]

** No longer affects: gnome-power-manager (Ubuntu)

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

** No longer affects: policykit-1 (Ubuntu)

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

** No longer affects: ubuntu-meta (Ubuntu)

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

Title:
  Ubuntu 18.04 LTS does not ask for action when I press ACPI Power
  button/key - immediately shutdowns

Status in gnome-settings-daemon package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 18.04 LTS
  2. Login to session
  3. Press ACPI Power button/key

  
  Expected behavior:
  * Ubuntu asks user about action

  Actual behavior:
  * Ubuntu immediately shutdowns

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-desktop 1.417
  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: Sat May  5 18:32:06 2018
  InstallationDate: Installed on 2018-04-28 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1769372] [NEW] Ubuntu 18.04 LTS does not ask for action when I press ACPI Power button/key - immediately shutdowns

[Norbert]

Public bug reported:

Steps to reproduce:
1. Install Ubuntu 18.04 LTS
2. Login to session
3. Press ACPI Power button/key


Expected behavior:
* Ubuntu asks user about action

Actual behavior:
* Ubuntu immediately shutdowns

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-desktop 1.417
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: Sat May  5 18:32:06 2018
InstallationDate: Installed on 2018-04-28 (7 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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

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

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

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

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: apport-bug bionic

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

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

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

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

** Also affects: gnome-settings-daemon (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-power-manager (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

Title:
  Ubuntu 18.04 LTS does not ask for action when I press ACPI Power
  button/key - immediately shutdowns

Status in gnome-power-manager package in Ubuntu:
  New
Status in gnome-session package in Ubuntu:
  New
Status in gnome-settings-daemon package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in policykit-1 package in Ubuntu:
  New
Status in policykit-gnome package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 18.04 LTS
  2. Login to session
  3. Press ACPI Power button/key

  
  Expected behavior:
  * Ubuntu asks user about action

  Actual behavior:
  * Ubuntu immediately shutdowns

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-desktop 1.417
  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: Sat May  5 18:32:06 2018
  InstallationDate: Installed on 2018-04-28 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1769357] Re: I've been pirated - so am trying to change passwords - & apparently this doesn't work

[dino99]

The error message is : Error BrokenCount>0 & tells me that this usually means 
that my "installed packages have unmet dependencies".


Pirated ? Unmet dependencies ?  what's the relationship ?

But you really should not have that version installed; the valid ones
are 45 (main) or 59 (security)
https://launchpad.net/ubuntu/+source/firefox

So open a terminal, and run:
- sudo apt-get clean
- sudo apt-get autoclean
- sudo apt-get autoremove

If you have installed some ppa's packages, then use ppa-purge to set
back the genuine version.

- sudo apt-get update
- sudo apt-get upgrade
- sudo apt-get install --reinstall ubuntu-desktop
- sudo apt-get install -f
- sudo dpkg --configure -a

If firefox 59 has not been proposed for upgrade, then your system needs
more serious tech support. You should glance at dsmeg log errors to get
an idea of the problems.

Note that xenial (LTS) can be upgraded to the next LTS (bionic) too.
Simply read & follow the steps : https://linuxconfig.org/how-to-upgrade-
to-ubuntu-18-04-lts-bionic-beaver

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

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

Title:
  I've been pirated - so am trying to change passwords - & apparently
  this doesn't work

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  I'm sorry but I'm not an expert.
  Its the red "no entry" disk that tells me to run Package Manager - just I 
can't find where to right click it ... The error message is : Error 
BrokenCount>0 & tells me that this usually means that my "installed packages 
have unmet dependencies".
  Since I have Ubuntu I've never managed to update anything because of 
authentication problems. I'm the only user & since I've changed my password it 
doesn't work - but the one before didn't either. To get in here I had to use 
the 1st one. 
  I'm really lost with all this. 
  For info - I have half the computer still on Windows 7 - till I get used to 
Firefox - where I've also downloaded it.
  I hope you can get me out of this. I regularly get a warning that my Firefox 
is critically out of date - but the update just aborts ... But it's version 
59.0.3 (64 bits) in W7.
  Thank you for you help ...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 54.0+build3-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  utilisateur   1527 F pulseaudio
   /dev/snd/controlC1:  utilisateur   1527 F pulseaudio
  BuildID: 20170612122310
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sat May  5 15:56:18 2018
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.1.1 dev enp2s0  proto static  metric 100 
   169.254.0.0/16 dev enp2s0  scope link  metric 1000 
   192.168.1.0/24 dev enp2s0  proto kernel  scope link  src 192.168.1.10  
metric 100
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=54.0/20170612122310 (In use)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 202
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K70AF
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr202:bd02/02/2010:svnASUSTeKComputerInc.:pnK70AF:pvr1.0:rvnASUSTeKComputerInc.:rnK70AF:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
  dmi.product.name: K70AF
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Desktop-packages] [Bug 1768906] Re: Xorg crash

[Cyrus Harmon]

I am able to reproduce this following a reinstall of 18.04 from the ISO
image, but only on the same box. No problems on two other computers.
Will try reverting to 17.10 to see if that fixes the problem.

As for the component, can I test with alternative session managers, or
is gdm3 the only game in town? thanks!

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When attempting to log in to a newly updated bionic beaver via the
  display manager (I think this is the right term), I immediately see a
  crash, a return to the user selection/login screen and a no-longer
  functioning keyboard and mouse. This happens both with the proprietary
  driver installed drivers and with the apt installed nvidia-driver-396.

  some interesting tidbits from the syslog file are:

  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): 
Failed to acquire modesetting permission.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): 
Failing initialization of X screen 0
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: 
"nvidia"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "wfb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "fb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) 
found, but none have a usable configuration.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE)
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error:
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens 
found(EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency 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  396.24  Thu Apr 26 00:10:09 
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'
  CompositorRunning: None
  Date: Thu May  3 09:28:59 2018
  DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774]
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-lowlatency 
root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAXIMUS VI GENE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  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 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
  xserver.bootTime: Thu May  3 09:20:03 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  

[Desktop-packages] [Bug 1720310] Re: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not installed

[Dan Christensen]

I installed version 3.28.1-0ubuntu3 of gnome-session-bin gnome-session-common
and ubuntu-session from bionic-proposed, and the problem went away.

(When I upgraded from 16.04 to 18.04, do-release-upgrade stopped with an error,
so I did the rest of the upgrade manually.)

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

Title:
  unity-gnome-shell-migration.18.08.py crashed with signal 5 in
  g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not
  installed

Status in gnome-session package in Ubuntu:
  Triaged
Status in gnome-session source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * People having this particular setup:
 - removed ubuntu-desktop metapackage from their system
 - upgrading from 16.04 to 18.04 (or previously to 17.10) by manually 
editing /etc/apt/sources.lists without using do-release-upgrade (which 
reinstalls ubuntu-desktop).
  They end up with:
  - no ubuntu-dock installed
  - and consequentely, the settings migration script would trigger an apport 
dialog (crashing) due to lack of gsettings schema.
   * Even if this is an unsupported case (people shouldn't cowboy sources.list 
and use our upgrader tools), we can easily prevent this crash, ignoring 
settings migration in such a case.

  [Test Case]

   1. Install 16.04
   2. Remove ubuntu-desktop metapackage
   3. Change your sources.list from "xenial" to "bionic"
   4. apt update && apt full-upgrade
   5. Reboot and log into a new session once upgrade is done.
  -> you won't get the ubuntu-dock, but the session migration script shouldn't 
crash.

  [Regression Potential]

   * The script was crashing (even if there is no settings to migrate,
  so it was a no-op). We prevents gsettings to segfault by guarding for
  schema existence in the standard way.

  --

  Upgrade...

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-session 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 08:15:13 2017
  ExecutablePath: 
/usr/share/session-migration/scripts/unity-gnome-shell-migration.18.08.py
  InstallationDate: Installed on 2017-09-25 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterpreterPath: /usr/bin/python3.6
  ProcCmdline: /usr/bin/python3 
/usr/share/session-migration/scripts/unity-gnome-shell-migration.18.08.py
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 
3.6.2-1ubuntu4
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  Signal: 5
  SourcePackage: gnome-session
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: unity-gnome-shell-migration.18.08.py crashed with signal 5 in 
g_object_new_valist()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1625712] Re: Power button no longer opens interactive menu in Xenial

[Norbert]

** Tags added: xenial

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

Title:
  Power button no longer opens interactive menu in Xenial

Status in GNOME Settings Daemon:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  In gnome-shell, the hardware power button does not open the
  interactive power menu. It sleeps the computer instead.

  The configuration backend to customize this behaviour was intentionally 
removed in commit [50564cde49ca2][1] (for [bug 753713][2]). After [some 
discussion](https://bugzilla.gnome.org/show_bug.cgi?id=755953), it's returned 
in [gnome-settings-daemon
  3.20](https://bugzilla.gnome.org/show_bug.cgi?id=755953#c29).

  Unfortunately, 3.20 is not in the [16.04 ubuntu
  repos](https://launchpad.net/ubuntu/+source/gnome-settings-daemon)
  (however there is a 3.20 release for Yakkety 16.10).

  Can 3.20 be released in xenial-updates?

  Removing this functionality is a disruptive change and it appears it
  was introduced in the Xenial LTS release (3.17 was not in Wily). While
  I understand gnome doesn't follow Ubuntu's stable release strategy and
  this is one in a large system of applications, can we get gnome-
  settings-daemon upgraded to 3.20 in Xenial?

  

  Use case scenarios for why this is disruptive:

  * [Accidentally hitting the power 
button](https://www.reddit.com/r/gnome/comments/3oddse/buttonpower_gone_in_318/cvwd2ho)
 sleeps the computer without recourse. The interactive menu gives you 60 
seconds to cancel.
  * Laptops can already suspend when the lid is closed. While the power button 
can be configured to hibernate instead of sleep, my laptop does not support 
hibernate. Now I have a nonfunctional button (when configured to hibernate) or 
two ways to do the same action.
  * Laptops with low battery life cannot last long in suspend state. (And 
again, hibernate does not always work.)
  * The initial change was made to make the media buttons do what their labels 
say, but the "power" button no longer controls powering off the machine.

  Removing "shutdown" from the list of configurations is reasonable on
  the grounds that it is destructive, but removing "interactive" doesn't
  follow since it's the least destructive. The power button was the most
  convenient way to invoke that menu.

  Thank you for your consideration.

  

  Additional information:

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

  $ apt-cache policy gnome-settings-daemon
  gnome-settings-daemon:
Installed: 3.18.2-0ubuntu3
Candidate: 3.18.2-0ubuntu3.1
Version table:
   3.18.2-0ubuntu3.1 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
   *** 3.18.2-0ubuntu3 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  
[1]: 
https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=50564cde49ca2
[2]: https://bugzilla.gnome.org/show_bug.cgi?id=753713

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1625712/+subscriptions

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

[Desktop-packages] [Bug 1423773] Re: Gnome-Shell don't free ram when I change a wallpaper

[Mike L]

It does seem to increase memory usage. GNOME shell sure is leaky. Glad I
have the luxury of 16GB of RAM. Still should be fixed in the LTS, IMO.
Even if not high priority.

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

Title:
  Gnome-Shell don't free ram when I change a wallpaper

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Sorry for my bad english, here is the link to see the error by
  yourself: https://www.youtube.com/watch?v=O53tt-6v81Y=youtu.be

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

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

[Desktop-packages] [Bug 1769348] Re: libfreerdp does not support h264

[Hans Joachim Desserud]

** Tags added: bionic

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

Title:
  libfreerdp does not support h264

Status in freerdp2 package in Ubuntu:
  New

Bug description:
  am on ubuntu 18.04  upgraded from  16.04

  now am seeing this bug on 18.04 only

  earlier i had no problem with color depth using remmina.

  
  could you please upgrade freerdp to support h264 mode.

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

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

[Desktop-packages] [Bug 1769361] [NEW] package postgresql-common 190 failed to install/upgrade: installed postgresql-common package post-installation script subprocess was killed by signal (Terminated

[Daman]

Public bug reported:

This issue happened when trying to install xrdp.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: postgresql-common 190
ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Sat May  5 07:23:18 2018
ErrorMessage: installed postgresql-common package post-installation script 
subprocess was killed by signal (Terminated)
InstallationDate: Installed on 2017-11-22 (163 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: postgresql-common
Title: package postgresql-common 190 failed to install/upgrade: installed 
postgresql-common package post-installation script subprocess was killed by 
signal (Terminated)
UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
mtime.conffile..etc.logrotate.d.postgresql-common: 2015-05-06T17:25:15

** Affects: postgresql-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package postgresql-common 190 failed to install/upgrade: installed
  postgresql-common package post-installation script subprocess was
  killed by signal (Terminated)

Status in postgresql-common package in Ubuntu:
  New

Bug description:
  This issue happened when trying to install xrdp.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: postgresql-common 190
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sat May  5 07:23:18 2018
  ErrorMessage: installed postgresql-common package post-installation script 
subprocess was killed by signal (Terminated)
  InstallationDate: Installed on 2017-11-22 (163 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: postgresql-common
  Title: package postgresql-common 190 failed to install/upgrade: installed 
postgresql-common package post-installation script subprocess was killed by 
signal (Terminated)
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
  mtime.conffile..etc.logrotate.d.postgresql-common: 2015-05-06T17:25:15

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1769361/+subscriptions

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

[Desktop-packages] [Bug 1769357] [NEW] I've been pirated - so am trying to change passwords - & apparently this doesn't work

[Oleandra RIOU]

Public bug reported:

I'm sorry but I'm not an expert.
Its the red "no entry" disk that tells me to run Package Manager - just I can't 
find where to right click it ... The error message is : Error BrokenCount>0 & 
tells me that this usually means that my "installed packages have unmet 
dependencies".
Since I have Ubuntu I've never managed to update anything because of 
authentication problems. I'm the only user & since I've changed my password it 
doesn't work - but the one before didn't either. To get in here I had to use 
the 1st one. 
I'm really lost with all this. 
For info - I have half the computer still on Windows 7 - till I get used to 
Firefox - where I've also downloaded it.
I hope you can get me out of this. I regularly get a warning that my Firefox is 
critically out of date - but the update just aborts ... But it's version 59.0.3 
(64 bits) in W7.
Thank you for you help ...

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 54.0+build3-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-58-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  utilisateur   1527 F pulseaudio
 /dev/snd/controlC1:  utilisateur   1527 F pulseaudio
BuildID: 20170612122310
Channel: Unavailable
CurrentDesktop: Unity
Date: Sat May  5 15:56:18 2018
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
IpRoute:
 default via 192.168.1.1 dev enp2s0  proto static  metric 100 
 169.254.0.0/16 dev enp2s0  scope link  metric 1000 
 192.168.1.0/24 dev enp2s0  proto kernel  scope link  src 192.168.1.10  metric 
100
Locales: extensions.sqlite corrupt or missing
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=54.0/20170612122310 (In use)
RfKill:
 0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 202
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K70AF
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr202:bd02/02/2010:svnASUSTeKComputerInc.:pnK70AF:pvr1.0:rvnASUSTeKComputerInc.:rnK70AF:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
dmi.product.name: K70AF
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  I've been pirated - so am trying to change passwords - & apparently
  this doesn't work

Status in firefox package in Ubuntu:
  New

Bug description:
  I'm sorry but I'm not an expert.
  Its the red "no entry" disk that tells me to run Package Manager - just I 
can't find where to right click it ... The error message is : Error 
BrokenCount>0 & tells me that this usually means that my "installed packages 
have unmet dependencies".
  Since I have Ubuntu I've never managed to update anything because of 
authentication problems. I'm the only user & since I've changed my password it 
doesn't work - but the one before didn't either. To get in here I had to use 
the 1st one. 
  I'm really lost with all this. 
  For info - I have half the computer still on Windows 7 - till I get used to 
Firefox - where I've also downloaded it.
  I hope you can get me out of this. I regularly get a warning that my Firefox 
is critically out of date - but the update just aborts ... But it's version 
59.0.3 (64 bits) in W7.
  Thank you for you help ...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 54.0+build3-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  utilisateur   1527 F pulseaudio
   /dev/snd/controlC1:  utilisateur   1527 F pulseaudio
  BuildID: 20170612122310
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sat May  5 15:56:18 2018
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   

[Desktop-packages] [Bug 1769358] [NEW] Thumbnail previews in Files/Nautilus only show when zoom is 150% or more

[Loïc Alejandro]

Public bug reported:

Ubuntu 18.04 LTS
Nautilus package: 1:3.26.3-0ubuntu4

I don't get thumbnail previews in Files (Nautilus) at the default zoom
level when using List view.

If I select 150% in the hamburger menu the thumbnails are displayed, and
they are displayed in Grid view at all sizes. They are also displayed in
the Open File dialog, even though the icon size there is smaller than in
Files!

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

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

Title:
  Thumbnail previews in Files/Nautilus only show when zoom is 150% or
  more

Status in nautilus package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 LTS
  Nautilus package: 1:3.26.3-0ubuntu4

  I don't get thumbnail previews in Files (Nautilus) at the default zoom
  level when using List view.

  If I select 150% in the hamburger menu the thumbnails are displayed,
  and they are displayed in Grid view at all sizes. They are also
  displayed in the Open File dialog, even though the icon size there is
  smaller than in Files!

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

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Bernadette Addison]

@Tom - getting closer! I can now login...but icons are HUGE!!!  Lol.
Need to fix resolution

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

Title:
  nvidia-390 fails to boot graphical display

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

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

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

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

[Desktop-packages] [Bug 1769348] [NEW] libfreerdp does not support h264

[Ravi Shanker KV]

Public bug reported:

am on ubuntu 18.04  upgraded from  16.04

now am seeing this bug on 18.04 only

earlier i had no problem with color depth using remmina.


could you please upgrade freerdp to support h264 mode.

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

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

Title:
  libfreerdp does not support h264

Status in freerdp2 package in Ubuntu:
  New

Bug description:
  am on ubuntu 18.04  upgraded from  16.04

  now am seeing this bug on 18.04 only

  earlier i had no problem with color depth using remmina.

  
  could you please upgrade freerdp to support h264 mode.

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

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

[Desktop-packages] [Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[herrtimson]

Well, for me it doesn't really work. Downloaded this deb file from the
github repo: firefox_59.0.2.build1-0ubuntu0.14.04.4_armhf.deb ,
installed it with dpkg -i , and got the error of 'ungültiger
maschienenbefehl', which I am not sure what it does mean at all. Could
be illegal assembler instruction.

Oh, and how do I revert this to the ubuntu one? *_*

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

Status in Mozilla Firefox:
  Expired
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Firefox always crashes when launched after the 55.0.1 update on an
  Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi),
  even in safe mode.

  I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for
  ARM single-board computer) on a similar board (Orange Pi Plus 2e),
  installed Firefox and experienced the same problem--it won't load
  without crashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 55.0.1+build2-0ubuntu0.16.04.2
  Uname: Linux 3.4.113-sun8i armv7l
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: armhf
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jim1138 F pulseaudio
   /dev/snd/controlC0:  jim1138 F pulseaudio
  BuildID: 20170814194718
  Card0.Amixer.info:
   Card hw:0 'audiocodec'/'audiocodec'
 Mixer name : ''
 Components : ''
 Controls  : 12
 Simple ctrls  : 12
  Card1.Amixer.info:
   Card hw:1 'sndhdmi'/'sndhdmi'
 Mixer name : ''
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'hdmi audio format Function',0
 Capabilities: enum
 Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' 
'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO'
 Item0: 'pcm'
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Thu Aug 17 05:37:00 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.10.1 dev eth0 
   default via 192.168.10.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.10.0/24 dev eth0  proto kernel  scope link  src 192.168.10.107 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.108  
metric 600
  Locales: extensions.sqlite corrupt or missing
  PciMultimedia:
   
  PciNetwork:
   
  Profiles: Profile0 (Default) - LastVersion=55.0.1/20170814194718
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1237999] Re: Amazon webapp always going to amazon.com

[Paul White]

Still an issue in 18.04. The Amazon website correctly shows my UK
delivery location at the top of the front page once I have logged in but
I am on amazon.com and see prices in US dollars. I was asked if the app
could use my location settings and said yes.

I need to use the buttons at the foot of the page to change to the UK
website.

** Tags added: bionic

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

Title:
  Amazon webapp always going to amazon.com

Status in webapps-applications package in Ubuntu:
  Confirmed

Bug description:
  On up to date Saucy Beta the amazon webapp always goes to amazon.com rather 
than amazon.co.uk
  When I run
  unity-webapps-runner --amazon --app-id=ubuntu-amazon-default
  I see
  ** (unity-webapps-runner:4259): WARNING **: Could not get a proper accuracy 
from Geoclue (NONE)
  which I guess may be the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity-webapps-common 2.4.17+13.10.20130924.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  Date: Thu Oct 10 13:53:52 2013
  InstallationDate: Installed on 2012-08-01 (434 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120730.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: webapps-applications
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webapps-applications/+bug/1237999/+subscriptions

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

[Desktop-packages] [Bug 1714659] Re: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.)

[Russell Keating]

Just purchased and installed an HP printer with software from HP web
page, device. I have this same bug.  Ubuntu 18.04, HPLIP 3.18.4, device
manager 15.0 (Qt4)

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

Title:
  HPLIP is not compatible with modern GNOME (No system tray detected on
  this system. Unable to start, exiting.)

Status in HPLIP:
  Confirmed
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install hplip-gui
  3. Launch GNOME session.
  4. Get error message window with header "HPLIP Status Service"
  and text
  "No system tray detected on this system.
  Unable to start, exiting."

  Expected results:
  hp-systray is compatible with modern GNOME

  Actual results:
  hp-systray is not compatible with modern GNOME

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: hplip-gui 3.17.7+repack0-3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: i386
  CupsErrorLog: W [01/Sep/2017:17:24:48 +0300] Notifier for subscription 112 
(dbus://) went away, retrying!
  CurrentDesktop: GNOME
  Date: Sat Sep  2 14:10:19 2017
  InstallationDate: Installed on 2017-08-26 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: ASUSTeK COMPUTER INC. UX32A
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=c2d4f47c-f1c6-4731-b8d0-dc268c6bf996 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1768074] Re: Mouseover does not show folder names reliably

[Bug Watch Updater]

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

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

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

Title:
  Mouseover does not show folder names reliably

Status in baobab:
  Confirmed
Status in baobab package in Ubuntu:
  New

Bug description:
  When holding my cursor still over a folder in the visualization (in
  either mode) I expect the name and size of the folder to appear in a
  floating box, as well as the names the folders contained in it.

  In my brand new install of Ubuntu 18.04, however, this does not happen most 
of the time. When holding my cursor over a folder, it «lights up» as usual, but 
after a second or two, it gets darker again, and nothing appears.
  However, it sometimes does work for certain folders. Based on a small amount 
of testing, those folders seem to be close to 8 or 9 o'clock when using the pie 
chart mode, and mostly only folders at the bottom of the hierarchy. I can then 
move the cursor within the visualization and see the names of all the folders 
as usual. But if the cursor is outside any folder for some small amount of 
time, I have to «activate» it again by holding the cursor over a working folder 
again.

  The behavior is quite strange and unpredictable, and I have no idea
  what is causing it or what to do about it. But I thought I would
  report it here as it makes it very difficult for me to use this
  application. I am happy to answer any questions.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: baobab 3.28.0-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 17:43:39 2018
  InstallationDate: Installed on 2018-04-27 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: baobab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1769341] [NEW] Can't find HDMI

[Sigurd Holmen]

Public bug reported:

The machine cannot find the HDMI port of the computer. It was working
fine in version 17.10, but not after upgrading to 18.04. When looking at
the graphics part of inxi, it is reporting that modesetting has failed.

command: inxi -G

Graphics:  Card: Intel HD Graphics 520
   Display Server: x11 (X.Org 1.19.6 ) driver: FAILED: modesetting
   Resolution: 1920x1080@60.00hz
   OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
   version: 4.5 Mesa 18.0.0-rc5

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
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat May  5 14:27:56 2018
DistUpgraded: 2018-05-05 12:31:36,611 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] [1025:1094]
InstallationDate: Installed on 2017-10-31 (186 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:57f3 Realtek Semiconductor Corp. 
 Bus 001 Device 003: ID 0489:e0a3 Foxconn / Hon Hai 
 Bus 001 Device 002: ID 062a:4101 Creative Labs Wireless Keyboard/Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire E5-575
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=98508690-a9ad-4456-9e28-f3d867db01e9 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
dmi.bios.date: 04/26/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ironman_SK
dmi.board.vendor: Acer
dmi.board.version: V1.04
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd04/26/2016:svnAcer:pnAspireE5-575:pvrV1.04:rvnAcer:rnIronman_SK:rvrV1.04:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: SKL
dmi.product.name: Aspire E5-575
dmi.product.version: V1.04
dmi.sys.vendor: Acer
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 N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue Oct 31 16:01:19 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "fbdev" (module does not exist, 0)
 Failed to load module "vesa" (module does not exist, 0)
 Failed to load module "fbdev" (module does not exist, 0)
 Failed to load module "vesa" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.3
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Can't find HDMI

Status in xorg package in Ubuntu:
  New

Bug description:
  The machine cannot find the HDMI port of the computer. It was working
  fine in version 17.10, but not after upgrading to 18.04. When looking
  at the graphics part of inxi, it is reporting that modesetting has
  failed.

  command: inxi -G

  Graphics:  Card: Intel HD Graphics 520
 Display Server: x11 (X.Org 1.19.6 ) driver: FAILED: modesetting
 Resolution: 1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
 version: 4.5 Mesa 18.0.0-rc5

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 14:27:56 2018
  DistUpgraded: 2018-05-05 12:31:36,611 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  

[Desktop-packages] [Bug 1768074] Re: Mouseover does not show folder names reliably

[Mathias Bynke]

I have now reported the bug i Bugzilla. This is my first report there,
so feel free to correct any mistakes I may have made.

https://bugzilla.gnome.org/show_bug.cgi?id=795832

** Bug watch added: GNOME Bug Tracker #795832
   https://bugzilla.gnome.org/show_bug.cgi?id=795832

** Also affects: baobab via
   https://bugzilla.gnome.org/show_bug.cgi?id=795832
   Importance: Unknown
   Status: Unknown

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

Title:
  Mouseover does not show folder names reliably

Status in baobab:
  Unknown
Status in baobab package in Ubuntu:
  New

Bug description:
  When holding my cursor still over a folder in the visualization (in
  either mode) I expect the name and size of the folder to appear in a
  floating box, as well as the names the folders contained in it.

  In my brand new install of Ubuntu 18.04, however, this does not happen most 
of the time. When holding my cursor over a folder, it «lights up» as usual, but 
after a second or two, it gets darker again, and nothing appears.
  However, it sometimes does work for certain folders. Based on a small amount 
of testing, those folders seem to be close to 8 or 9 o'clock when using the pie 
chart mode, and mostly only folders at the bottom of the hierarchy. I can then 
move the cursor within the visualization and see the names of all the folders 
as usual. But if the cursor is outside any folder for some small amount of 
time, I have to «activate» it again by holding the cursor over a working folder 
again.

  The behavior is quite strange and unpredictable, and I have no idea
  what is causing it or what to do about it. But I thought I would
  report it here as it makes it very difficult for me to use this
  application. I am happy to answer any questions.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: baobab 3.28.0-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 17:43:39 2018
  InstallationDate: Installed on 2018-04-27 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: baobab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1769022] Re: ubuntu 18.04 freezes after the login

[Ghassan Mina]

Thank you for your support but I was able to resolve the issue. The problem
was due to the extensions that I had before upgrading. I wiped all the
extensions and everything worked as a charm

On 5 May 2018 at 03:00, Dave Goldsbrough  wrote:

> Many bugs are now accumulating with this and similar issues surrounding
> Xorg. This is just one example https://bugs.launchpad.net/
> ubuntu/+source/xorg/+bug/1764087
> There are others. Some are related to Lenovo laptops but not all.
> Shame that 18.04 LTS has been allowed to be released without this inherent
> bug being fixed. It is damaging Ubuntu reputation.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1769022
>
> Title:
>   ubuntu 18.04 freezes after the login
>
> Status in xorg package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I am not able to log to ubuntu 18.04 after the upgrade. When I login I
>   get setup screen with the word "Welcome" and the system freezes
>
>   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
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.9-0ubuntu7
>   Architecture: amd64
>   CompizPlugins: No value set for `/apps/compiz-1/general/
> screen0/options/active_plugins'
>   CompositorRunning: None
>   Date: Thu May  3 23:29:56 2018
>   DistUpgraded: 2018-05-03 01:59:32,397 ERROR got error from
> PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to
> execute child process “./xorg_fix_proprietary.py” (No such file or
> directory) (8))
>   DistroCodename: bionic
>   DistroVariant: ubuntu
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G]
> [1002:9647] (prog-if 00 [VGA controller])
>  Subsystem: Lenovo BeaverCreek [Radeon HD 6520G] [17aa:3971]
>   InstallationDate: Installed on 2016-11-19 (530 days ago)
>   InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
> (20160719)
>   MachineType: LENOVO 129925U
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic
> root=UUID=91dffd26-787f-4656-94b0-9568086633ac ro radeon.dpm=1
>   SourcePackage: xorg
>   UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)
>   dmi.bios.date: 07/20/2011
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: 54CN18WW
>   dmi.board.asset.tag: Base Board Asset Tag Unknown
>   dmi.board.name: Torpedo
>   dmi.board.vendor: LENOVO
>   dmi.board.version: 109-C06210-00B
>   dmi.chassis.asset.tag: Chassis Asset Tag Unknown
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Chassis Version Unknown
>   dmi.modalias: dmi:bvnLENOVO:bvr54CN18WW:bd07/20/2011:svnLENOVO:
> pn129925U:pvrIdeapadZ575:rvnLENOVO:rnTorpedo:rvr109-
> C06210-00B:cvnLENOVO:ct10:cvrChassisVersionUnknown:
>   dmi.product.family: IDEAPAD
>   dmi.product.name: 129925U
>   dmi.product.version: Ideapad Z575
>   dmi.sys.vendor: LENOVO
>   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
>   xserver.bootTime: Thu May  3 22:52:41 2018
>   xserver.configfile: default
>   xserver.errors:
>
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.version: 2:1.19.6-1ubuntu4
>   xserver.video_driver: radeon
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769022/+subscriptions
>


-- 
Ghassan Mina
IT/GIS Specialist

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

Title:
  ubuntu 18.04 freezes after the login

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am not able to log to ubuntu 18.04 after the upgrade. When I login I
  get setup screen with the word "Welcome" and the system freezes

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May  3 23:29:56 2018
  DistUpgraded: 2018-05-03 01:59:32,397 ERROR got error from PostInstallScript 

[Desktop-packages] [Bug 1769337] [NEW] ubuntu-drivers manual is missing

[Bump]

Public bug reported:

man ubuntu-drivers
No manual entry for ubuntu-drivers
See 'man 7 undocumented' for help when manual pages are not available.

** Affects: ubuntu-drivers-common (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  ubuntu-drivers manual is missing

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  man ubuntu-drivers
  No manual entry for ubuntu-drivers
  See 'man 7 undocumented' for help when manual pages are not available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1769337/+subscriptions

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

[Desktop-packages] [Bug 1725078] Re: Can't set Ctrl+Shift as a shortcut

[Emil Limarenko]

Repository with xserver fix. Works on ubuntu 16.04, 18.04.

https://launchpad.net/~nrbrtx/+archive/ubuntu/xorg-hotkeys

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

Title:
  Can't set Ctrl+Shift as a shortcut

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Can't set Ctrl+Shift (and many other key combinations) as a shortcut
  in new and shiny Ubuntu 17.10. Nothing happens when I press these
  keys. For example, when setting "Switch to next input source"
  shortcut, a window pops up waiting for a key combination, but nothing
  happens at all when I press Ctrl+Shift. I can still set some
  combinations like Super+Space, though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-shortcuts (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 04:03:29 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gnome-shell-extension-shortcuts
  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/1725078/+subscriptions

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

[Desktop-packages] [Bug 1767549] Re: org.gnome.Characters.desktop untranslated

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-characters - 3.28.0-4

---
gnome-characters (3.28.0-4) unstable; urgency=medium

  * Recommends fonts-noto-color-emoji since it's the only color
emoji font in Debian currently
  * Drop obsolete dh_translations overrides (LP: #1767549)

 -- Jeremy Bicha   Fri, 04 May 2018 18:36:18 -0400

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

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

Title:
  org.gnome.Characters.desktop untranslated

Status in gnome-characters package in Ubuntu:
  Fix Released
Status in gnome-characters source package in Bionic:
  In Progress

Bug description:
  [Impact]

  The version of dh_translations, which was present when gnome-
  characters was last uploaded, resulted in a .desktop file with the
  wrong gettext domain, so the name of the application in e.g. the
  Activities overview is always shown in English.

  Meson support has been added to dh_translations since, so a no-change
  rebuild is sufficient to fix the issue.

  [Test Case]

  On a system with some other language but English:

  * Install the gnome-characters .deb package

  -> find that its name is "Characters".

  * Install the rebuilt version of gnome-characters

  * Relogin

  -> find that its name is the translation of "Characters"

  [Regression Potential]

  None.

  [Original description]

  $ tail -n1 /usr/share/applications/org.gnome.Characters.desktop
  X-Ubuntu-Gettext-Domain=$PACKAGE_NAME

  dh_translations is confused by files in the source package belonging
  to the old build system. configure.ac contains this line:

  GETTEXT_PACKAGE=$PACKAGE_NAME

  and dh_translations happily uses it to do its things.

  The gnome-characters source package should apparently be cleaned up,
  but I think that dh_translations should also be changed to not accept
  a domain starting with '$'.

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

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

[Desktop-packages] [Bug 1769330] [NEW] 18.04 regression: liberation text highlight is too small in web browsers.

[Plurtu]

Public bug reported:

When Liberation font is selected in Firefox 59 and Chromium 65, the
highlight does not cover the top part of the text. On Chromium it
affects the first line of a paragraph, on Firefox it affects every line.

This is a regression in 1:1.07.4-5, rolling back to the previous version
(1:1.07.4-2) restores the correct behavior.

The same font in gedit, libreoffice and terminal does not have this
problem, however since both browsers are affected and other fonts
highlight normally it suggests the fault lies with the font.

** Affects: fonts-liberation (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  When Liberation font is selected in Firefox 59 and Chromium 65, the
  highlight does not cover the top part of the text. On Chromium it
  affects the first line of a paragraph, on Firefox it affects every line.
  
- https://i.imgur.com/3lZ7Car.png
- 
  This is a regression in 1:1.07.4-5, rolling back to the previous version
- restores the correct behavior.
+ (1:1.07.4-2) restores the correct behavior.
  
  The same font in gedit, libreoffice and terminal does not have this
  problem, however since both browsers are affected and other fonts
  highlight normally it suggests the fault lies with the font.

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

Title:
  18.04 regression: liberation text highlight is too small in web
  browsers.

Status in fonts-liberation package in Ubuntu:
  New

Bug description:
  When Liberation font is selected in Firefox 59 and Chromium 65, the
  highlight does not cover the top part of the text. On Chromium it
  affects the first line of a paragraph, on Firefox it affects every
  line.

  This is a regression in 1:1.07.4-5, rolling back to the previous
  version (1:1.07.4-2) restores the correct behavior.

  The same font in gedit, libreoffice and terminal does not have this
  problem, however since both browsers are affected and other fonts
  highlight normally it suggests the fault lies with the font.

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

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

[Desktop-packages] [Bug 1769330] Re: 18.04 regression: liberation text highlight is too small in web browsers.

[Plurtu]

** Attachment added: "Screenshot of incomplete highlight with top edge cut off."
   
https://bugs.launchpad.net/ubuntu/+source/fonts-liberation/+bug/1769330/+attachment/5134288/+files/liberation-highlight.png

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

Title:
  18.04 regression: liberation text highlight is too small in web
  browsers.

Status in fonts-liberation package in Ubuntu:
  New

Bug description:
  When Liberation font is selected in Firefox 59 and Chromium 65, the
  highlight does not cover the top part of the text. On Chromium it
  affects the first line of a paragraph, on Firefox it affects every
  line.

  This is a regression in 1:1.07.4-5, rolling back to the previous
  version (1:1.07.4-2) restores the correct behavior.

  The same font in gedit, libreoffice and terminal does not have this
  problem, however since both browsers are affected and other fonts
  highlight normally it suggests the fault lies with the font.

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

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

[Desktop-packages] [Bug 1720438] Re: brightness control broken nvidia

[Bump]

Switching to integrated graphics the Fn works perfectly on gnome. Also:

ls -l /sys/class/backlight/
total 0
lrwxrwxrwx 1 root root 0 may  5 12:12 intel_backlight -> 
../../devices/pci:00/:00:02.0/drm/card0/card0-eDP-1/intel_backlight

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

Title:
  brightness control broken nvidia

Status in gnome-power:
  Confirmed
Status in gnome-power-manager package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 beta 2 
  Nvidia 310M, 340.x official driver installed with Additional Drivers program

  The brightness control built into the laptop (Dell Vostro 3300) isn't 
changing the brightness. Normally I can use Fn + Up/Down arrow keys to change 
the brightness.
  The brightness control works fine in Ubuntu 16.04 with the same driver series.

  I don't know if this is a GNOME 3.26 bug but it's likely as I'm having
  the exact same problem with Fedora 26 on this laptop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-power/+bug/1720438/+subscriptions

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

[Desktop-packages] [Bug 1769056] Re: driverless printing generates wrong language/encoding PPD

[Naruhiko Ogasawara]

CUPS generate non-globalized PPD in this context, so I believe it should
put LanguageVersion/LanguageEncoding as follows the locale of strings,
not hard-code to English/ISOLatin1.

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

Title:
  driverless printing generates wrong language/encoding PPD

Status in cups package in Ubuntu:
  New

Bug description:
  The printing option dialog (see attached PNG file) is broken with Bionic 
Japanese environment.
  This issue seems to be coming from the generated PPD file with wrong 
language/encoding.

  I tried with Epson EP-879AW.

  Steps to reproduce:

  1) generate a print queue by driverless feature with ja-JP locale:

  $ LANG-ja_JP.UTF-8 lpadmin -p driverlesstest-ja -E -v `driverless` -m
  everywhere

  2) check the generated PPD (attached driverlesstest-ja.ppd)

  $ sudo less /etc/cups/ppd/driverlesstest-ja.ppd

  Expected: PPD have same language/encoding with content (if the content
  have Japanese, language/encoding should be Japanese/UTF-8)

  Actual: PPD has Japanese strings, but language/encoding is
  English/ISOLatin1

  
  
  Attached files:
   
  EPSON_EP_879A_Series_007.png: screenshot of printing option dialog of 
EP-879AW driverless print queue
  driverless-ja.ppd: PPD generated with ja_JP.UTF-8 locale
  driverless-en.ppd: PPD generated with C locale
  ipptool.txt: output of ipptool, by following command:

  $ ipptool -tv `driverless` get-printer-attributes.test > ipptool.txt

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

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

[Desktop-packages] [Bug 1769329] [NEW] package hostapd 2:2.6-15ubuntu2 failed to install/upgrade: installed hostapd package post-installation script subprocess returned error exit status 1

[noufal]

Public bug reported:

nothing just prompted me to do so

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: hostapd 2:2.6-15ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
AptOrdering:
 hostapd:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sat May  5 14:05:44 2018
ErrorMessage: installed hostapd package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2017-12-18 (137 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: wpa
Title: package hostapd 2:2.6-15ubuntu2 failed to install/upgrade: installed 
hostapd package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package hostapd 2:2.6-15ubuntu2 failed to install/upgrade: installed
  hostapd package post-installation script subprocess returned error
  exit status 1

Status in wpa package in Ubuntu:
  New

Bug description:
  nothing just prompted me to do so

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: hostapd 2:2.6-15ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  AptOrdering:
   hostapd:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  5 14:05:44 2018
  ErrorMessage: installed hostapd package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2017-12-18 (137 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: wpa
  Title: package hostapd 2:2.6-15ubuntu2 failed to install/upgrade: installed 
hostapd package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)

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

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

[Desktop-packages] [Bug 1720438] Re: brightness control broken nvidia

[Bump]

Probably just waiting for the gnome team to fix it is just enough.

** Changed in: gnome-power-manager (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  brightness control broken nvidia

Status in gnome-power:
  Confirmed
Status in gnome-power-manager package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 beta 2 
  Nvidia 310M, 340.x official driver installed with Additional Drivers program

  The brightness control built into the laptop (Dell Vostro 3300) isn't 
changing the brightness. Normally I can use Fn + Up/Down arrow keys to change 
the brightness.
  The brightness control works fine in Ubuntu 16.04 with the same driver series.

  I don't know if this is a GNOME 3.26 bug but it's likely as I'm having
  the exact same problem with Fedora 26 on this laptop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-power/+bug/1720438/+subscriptions

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

[Desktop-packages] [Bug 1720438] Re: brightness control broken nvidia

[Bump]

I confirm that 'xbacklight -set 60' works (as user, no root required),
in both desktop sessions: ubuntu and plasma. However, the Fn key + arrow
only works on plasma.

Being on ubuntu session, inside the directory '/sys/class/backlight'
there is nothing, yet xbacklight works. So it's almost sure a
gnome/wayland whatever issue.

The graphics card is a nvidia 1060 on a gaming notebook, which you can
switch to IGPU instead of DGPU on the BIOS but you need to reboot,
doesn't have "optimus" or "on-the-fly" switching.

I'll answer here as well:

https://bugzilla.gnome.org/show_bug.cgi?id=688052

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

Title:
  brightness control broken nvidia

Status in gnome-power:
  Confirmed
Status in gnome-power-manager package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 beta 2 
  Nvidia 310M, 340.x official driver installed with Additional Drivers program

  The brightness control built into the laptop (Dell Vostro 3300) isn't 
changing the brightness. Normally I can use Fn + Up/Down arrow keys to change 
the brightness.
  The brightness control works fine in Ubuntu 16.04 with the same driver series.

  I don't know if this is a GNOME 3.26 bug but it's likely as I'm having
  the exact same problem with Fedora 26 on this laptop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-power/+bug/1720438/+subscriptions

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

[Desktop-packages] [Bug 1768741] Re: hplip does not wake up printer

[Wolf Rogner]

Cudos to my wife: Here is a more detailed and accurate description of
the issue:

Preset: Printer is installed on Ubuntu 18.04

Turning on the printer and printing any document -> works
Putting notebook into suspend, after wakeup printing a document -> not printing
Mitigation:
- reboot printer
- reinstall printer software

After printer suspended (usually after 5 mins), printing a document -> not 
printing
After manually waking up the printer from the display and printing a document 
-> not printing

In all cases of not printing:
If the printer queue was held, resuming from the GUI (both methods, from 
Settings and the Additional printer settings queue view) the queue goes into 
printing status and reverts to held.

If the printer is freshly rebooted, starting a held queue leads to
printing the document.

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

Title:
  hplip does not wake up printer

Status in hplip package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 fresh install
  Printer: Color Laserjet Pro MFP M477fdw

  The printer suspends after 5 mins to save power.

  Expected: A print request should wake the printer and print.
  Actual: The printer queue goes on hold

  Mitigation measures:
  1) wake printer manually (from the display) + unpause queue -> does not print
  2) wake printer manually + restart queue -> does not print
  3) restart printer (WHY???) + unpause queue -> PRINTS !!!

  This behaviour can be reproduced in 18.04 and does not exist in
  previous versions of Ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: hplip 3.17.10+repack0-5
  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: Thu May  3 08:30:01 2018
  InstallationDate: Installed on 2018-04-30 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat: device for HP_Color_LaserJet_MFP_M477fdw: 
hp:/net/HP_Color_LaserJet_MFP_M477fdw?ip=10.1.0.21
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0171.B00.1708080033
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Desktop-packages] [Bug 1764087] Re: Wrongly boots into low graphics mode

[Dave Goldsbrough]

Cross reference now to a lightdm bug which has been raised as a consequence of 
https://bugs.freedesktop.org/show_bug.cgi?id=106407
saying it is not a xorg 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/1764087

Title:
  Wrongly boots into low graphics mode

Status in X.Org X server:
  Won't Fix
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  Lenovo T410 with VGA compatible controller [0300]: Intel Corporation
  Core Processor Integrated Graphics Controller [8086:0046] (rev 02)

  Booting from latest kernel ThinkPad-T410 4.13.0-38-generic
  #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64
  x86_64 GNU/Linux goes into low graphics mode and also effects wi-fi
  connection insofar as it does not connect to my router.

  Whereas booting from 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar
  7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux works most of the
  time but occasionally has the same effects.

  I have had to submit this report after booting from 4.13.0.37 in order
  to submit bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Apr 15 10:40:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  InstallationDate: Installed on 2016-09-24 (567 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2519Y11
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2519Y11
  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:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T410
  dmi.product.name: 2519Y11
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO
  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: Sun Apr 15 08:52:27 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1764087/+subscriptions

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

[Desktop-packages] [Bug 1764087] Re: Wrongly boots into low graphics mode

[Bug Watch Updater]

** Changed in: xorg-server
   Status: Unknown => Won't Fix

** Changed in: xorg-server
   Importance: Unknown => High

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

Title:
  Wrongly boots into low graphics mode

Status in X.Org X server:
  Won't Fix
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  Lenovo T410 with VGA compatible controller [0300]: Intel Corporation
  Core Processor Integrated Graphics Controller [8086:0046] (rev 02)

  Booting from latest kernel ThinkPad-T410 4.13.0-38-generic
  #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64
  x86_64 GNU/Linux goes into low graphics mode and also effects wi-fi
  connection insofar as it does not connect to my router.

  Whereas booting from 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar
  7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux works most of the
  time but occasionally has the same effects.

  I have had to submit this report after booting from 4.13.0.37 in order
  to submit bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Apr 15 10:40:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  InstallationDate: Installed on 2016-09-24 (567 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2519Y11
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2519Y11
  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:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T410
  dmi.product.name: 2519Y11
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO
  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: Sun Apr 15 08:52:27 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1764087/+subscriptions

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

[Desktop-packages] [Bug 1769299] Re: universal access zoom unusable

[whitis]

Problem reproduced on separate (virtual) machine, unmodified ubuntu live image.
   - Host system AMD Phenom II X6 1090T with 16GB RAM Ubuntu 14.04.4 LTS
   - virtualbox 14.3.36-dfsg-...
   - SATA 0: 8GB VMDK drive (new)
   - SATA 1: CD/ROM: ubuntu-18.04-desktop-amd64.iso
   - Base memory: 4GB (important, if you use 1GB, ubuntu will boot to 
desktop but nothing works)
 must have enough ram on host machine to permit this
   - Specific Virtual machine -> System -> Motherboard: Enable EFI: On
 otherwise it will not boot 
- Boot menu: TRY ubuntu without installing
- Show Applications (dash)-> Terminal
- Show Applications -> Settings-> Universal Access -> Always Show Universal 
Access Menu: On
- don't dismiss settings, we will use it about 8 steps below.
- Universal Access menu (round man in circle on top panel) -> Zoom: on
- Move pointer to upper left corner of desktop: note left panel (launcher) 
icons 
  cut in hafl, note top panel cut in half
- move to top right
- click on whats left of universal access menu icon to pull down menu, note 
it is drawn incorrectly
- move mouse down and to the left and notice how these panels/pull down 
menus scroll independently and incorrectly.
- try to turn off the zoom in the univeral access pull down menu.  Try to 
read the word zoom, now you cant see the control, move to see the control now 
you can't see the word.  But in this case, you can actually get there.  
 - turn zoom back on
 - move mouse pointer to upper right hand corner.  Make sure either the 
universal access or the system menu is pulled down
 - move mouse down and left to the words "sound keys" in the settings menu 
(control panel,
 not the pull down menu) for universal access.  Leave the mouse pointer 
there for a 
 few seconds.   Display will pan to upper right hand corner without 
permission.
  - If you repeat this without either of the two pull down menus activated, 
it will jump
to the highlighted "Universal Access" on the left side of the settings 
window.
 This jumping action severely interfered with issuing screenshot commands 
in terminal and
 it will interfere with many other operations as well.   


  


Behavior of program suggests that the screen is being composited of the 
following elements:
   - desktop background
   - application window 1
   - application window 2
   - application window 3 ...
   - top panel
   - left panel (launcher)
   - pull down menu
The first four items appear to be correctly composited together before applying 
the zoom and pan operation but the last three appear to not be composited onto 
the desktop+applications before zoom and pan is applied.  The size of their 
windows has not been enlarged, only the contents.

Add to paragraph about obfuscating the identity of the programs the user
is interacting with: Universal Pull down menu also doesn't have "Help"
or report bug menu items.

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

Title:
  universal access zoom unusable

Status in xorg package in Ubuntu:
  New

Bug description:
  
  Filed by mark on behalf of low vision user Ken.   Ken is able to read 56 
point type without magnification at normal reading distance and can barely read 
the universal access "large text" from a distance of about 2.5 inches from a 
26inch monitor at 1360x768.   So he really needs magnification and a lot more 
than the 2x default I used here for testing.   We do not live in the same town 
so providing additional details would be slow.

  Turned on zoom from the universal access button on top panel.
  Default settings were used including Zoom = 2.0, screen part = full

  Several areas are corrupted.  These zoom and scroll separately from
  the rest of the screen and in a way that severely impairs use as
  portions may not ever be visible.   Portions of these subwindows
  cannot be used because you have to move the mouse off them to be able
  see them so you can either see or click but not both.

  These areas are:
- The top panel
- The left panel (launcher)  (intermittently)
- pull down menus, particularly the universal access pull down from the top 
panel

  
  Also, the zoom randomly every couple seconds. jumps to a different position 
without the user's consent.   This appeared to be because text was printed by a 
program running in the terminal window (long apt-get install) but continued to 
happen even when that window was minimized and even when that program stopped 
printing.

  These problems persisted with all the other zoom modes.   One mode,
  however, created new bugs.  With "magnifier extends outside of
  screen", you lose the ability to see the top and left panels at all;
  you can pan over where they would be but they are not drawn.   Can't
  open the pulldown menu since there is no 

[Desktop-packages] [Bug 1764087] Re: Wrongly boots into low graphics mode

[Dave Goldsbrough]

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

** Also affects: xorg-server via
   https://bugs.freedesktop.org/show_bug.cgi?id=106407
   Importance: Unknown
   Status: Unknown

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

Title:
  Wrongly boots into low graphics mode

Status in X.Org X server:
  Unknown
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  Lenovo T410 with VGA compatible controller [0300]: Intel Corporation
  Core Processor Integrated Graphics Controller [8086:0046] (rev 02)

  Booting from latest kernel ThinkPad-T410 4.13.0-38-generic
  #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64
  x86_64 GNU/Linux goes into low graphics mode and also effects wi-fi
  connection insofar as it does not connect to my router.

  Whereas booting from 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar
  7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux works most of the
  time but occasionally has the same effects.

  I have had to submit this report after booting from 4.13.0.37 in order
  to submit bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Apr 15 10:40:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  InstallationDate: Installed on 2016-09-24 (567 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2519Y11
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2519Y11
  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:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T410
  dmi.product.name: 2519Y11
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO
  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: Sun Apr 15 08:52:27 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1764087/+subscriptions

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

[Desktop-packages] [Bug 1768906] Re: Xorg crash

[dino99]

Difference between remove & purge:
- 'remove' uninstall the package, but does not remove the package settings, 
which can disturb the system and conflict with an other driver choice.
- 'purge' remove both package & its settings; that is way recommended.

About /etc/X11/xorg.conf, this is no more used since a couple releases.
so your system should not finf such a path anyway.

Your real problem is not about 'xorg' as you have reported but 'gdm' and/or 
'gnome-session'
**
May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): 
Failed to acquire modesetting permission.
May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): 
Failing initialization of X screen 0
**

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When attempting to log in to a newly updated bionic beaver via the
  display manager (I think this is the right term), I immediately see a
  crash, a return to the user selection/login screen and a no-longer
  functioning keyboard and mouse. This happens both with the proprietary
  driver installed drivers and with the apt installed nvidia-driver-396.

  some interesting tidbits from the syslog file are:

  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): 
Failed to acquire modesetting permission.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): 
Failing initialization of X screen 0
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: 
"nvidia"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "wfb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "fb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) 
found, but none have a usable configuration.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE)
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error:
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens 
found(EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency 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  396.24  Thu Apr 26 00:10:09 
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'
  CompositorRunning: None
  Date: Thu May  3 09:28:59 2018
  DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774]
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-lowlatency 
root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAXIMUS VI GENE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  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
 

[Desktop-packages] [Bug 1768906] Re: Xorg crash

[Launchpad Bug Tracker]

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

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

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When attempting to log in to a newly updated bionic beaver via the
  display manager (I think this is the right term), I immediately see a
  crash, a return to the user selection/login screen and a no-longer
  functioning keyboard and mouse. This happens both with the proprietary
  driver installed drivers and with the apt installed nvidia-driver-396.

  some interesting tidbits from the syslog file are:

  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): 
Failed to acquire modesetting permission.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): 
Failing initialization of X screen 0
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: 
"nvidia"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "wfb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "fb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) 
found, but none have a usable configuration.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE)
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error:
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens 
found(EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency 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  396.24  Thu Apr 26 00:10:09 
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'
  CompositorRunning: None
  Date: Thu May  3 09:28:59 2018
  DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774]
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-lowlatency 
root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAXIMUS VI GENE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  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 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
  xserver.bootTime: Thu May  3 09:20:03 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1768661] Re: can't make WIFI work

[Dave Goldsbrough]

At a terminal screen have you tried entering the command?

sudo service network-manager restart

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

Title:
  can't make WIFI work

Status in xorg package in Ubuntu:
  New

Bug description:
  I can't make the WIfFI operate Compact Presario V2000

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic i686
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.27
  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: Wed May  2 17:05:59 2018
  DistUpgraded: 2018-05-01 16:52:36,093 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: ndiswrapper, 1.59: added
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS480M [Mobility Radeon Xpress 200] 
[1002:5955] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:3091]
  InstallationDate: Installed on 2018-05-01 (1 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  Lsusb:
   Bus 001 Device 011: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 
802.11n Wireless Network Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Hewlett-Packard Presario V2000 (EP377UA#ABA)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic 
root=UUID=3698752e-32a7-443e-959d-c4578e3e85a3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2018-05-01 (1 days ago)
  dmi.bios.date: 01/02/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.22
  dmi.board.name: 3097
  dmi.board.vendor: Quanta
  dmi.board.version: 47.0F
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.22:bd01/02/2006:svnHewlett-Packard:pnPresarioV2000(EP377UA#ABA):pvrRev1:rvnQuanta:rn3097:rvr47.0F:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: Presario V2000 (EP377UA#ABA)
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 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: Wed May  2 12:26:46 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1~trusty1
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1769022] Re: ubuntu 18.04 freezes after the login

[Dave Goldsbrough]

Many bugs are now accumulating with this and similar issues surrounding Xorg. 
This is just one example 
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087
There are others. Some are related to Lenovo laptops but not all.
Shame that 18.04 LTS has been allowed to be released without this inherent bug 
being fixed. It is damaging Ubuntu reputation.

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

Title:
  ubuntu 18.04 freezes after the login

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am not able to log to ubuntu 18.04 after the upgrade. When I login I
  get setup screen with the word "Welcome" and the system freezes

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May  3 23:29:56 2018
  DistUpgraded: 2018-05-03 01:59:32,397 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G] 
[1002:9647] (prog-if 00 [VGA controller])
 Subsystem: Lenovo BeaverCreek [Radeon HD 6520G] [17aa:3971]
  InstallationDate: Installed on 2016-11-19 (530 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 129925U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=91dffd26-787f-4656-94b0-9568086633ac ro radeon.dpm=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 54CN18WW
  dmi.board.asset.tag: Base Board Asset Tag Unknown
  dmi.board.name: Torpedo
  dmi.board.vendor: LENOVO
  dmi.board.version: 109-C06210-00B
  dmi.chassis.asset.tag: Chassis Asset Tag Unknown
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Chassis Version Unknown
  dmi.modalias: 
dmi:bvnLENOVO:bvr54CN18WW:bd07/20/2011:svnLENOVO:pn129925U:pvrIdeapadZ575:rvnLENOVO:rnTorpedo:rvr109-C06210-00B:cvnLENOVO:ct10:cvrChassisVersionUnknown:
  dmi.product.family: IDEAPAD
  dmi.product.name: 129925U
  dmi.product.version: Ideapad Z575
  dmi.sys.vendor: LENOVO
  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
  xserver.bootTime: Thu May  3 22:52:41 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1769022] Re: ubuntu 18.04 freezes after the login

[Launchpad Bug Tracker]

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

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

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

Title:
  ubuntu 18.04 freezes after the login

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am not able to log to ubuntu 18.04 after the upgrade. When I login I
  get setup screen with the word "Welcome" and the system freezes

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May  3 23:29:56 2018
  DistUpgraded: 2018-05-03 01:59:32,397 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G] 
[1002:9647] (prog-if 00 [VGA controller])
 Subsystem: Lenovo BeaverCreek [Radeon HD 6520G] [17aa:3971]
  InstallationDate: Installed on 2016-11-19 (530 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 129925U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=91dffd26-787f-4656-94b0-9568086633ac ro radeon.dpm=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 54CN18WW
  dmi.board.asset.tag: Base Board Asset Tag Unknown
  dmi.board.name: Torpedo
  dmi.board.vendor: LENOVO
  dmi.board.version: 109-C06210-00B
  dmi.chassis.asset.tag: Chassis Asset Tag Unknown
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Chassis Version Unknown
  dmi.modalias: 
dmi:bvnLENOVO:bvr54CN18WW:bd07/20/2011:svnLENOVO:pn129925U:pvrIdeapadZ575:rvnLENOVO:rnTorpedo:rvr109-C06210-00B:cvnLENOVO:ct10:cvrChassisVersionUnknown:
  dmi.product.family: IDEAPAD
  dmi.product.name: 129925U
  dmi.product.version: Ideapad Z575
  dmi.sys.vendor: LENOVO
  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
  xserver.bootTime: Thu May  3 22:52:41 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1769058] Re: Xorg freeze

[Launchpad Bug Tracker]

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

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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded ubuntu form 17.10 to 18.04, but after login in Gnome or 
Ubuntu desktop environment, UI is not responding. No mouse no keyboard, every 
thing is frozen, even i can't logout from screen. i have to manually turnoff 
the laptop.
  Currently i am using deepin desktop environment.
  Please do the needful.

  Thanks

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Deepin
  Date: Fri May  4 12:02:20 2018
  DistUpgraded: 2018-04-28 03:31:09,905 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:5002]
  InstallationDate: Installed on 2017-03-30 (399 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20140
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=871acc38-6b5a-4871-8105-c9af13662669 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (6 days ago)
  dmi.bios.date: 04/10/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H1ET73WW(1.16)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20140
  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:bvrH1ET73WW(1.16):bd04/10/2013:svnLENOVO:pn20140:pvrLenovoB480:rvnLENOVO:rn20140:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: Lenovo B480
  dmi.product.name: 20140
  dmi.product.version: Lenovo B480
  dmi.sys.vendor: LENOVO
  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/1769058/+subscriptions

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

[Desktop-packages] [Bug 1769029] Re: Display on Dell 1440x900 is not available

[Launchpad Bug Tracker]

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

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

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

Title:
  Display on Dell 1440x900 is not available

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Monitor resolution is limited to 1024x768 with no option for higher
  resolution

  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
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  4 09:44:54 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd 82945G/GZ Integrated Graphics 
Controller [1458:d000]
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 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
  MachineType: Gigabyte Technology Co., Ltd. 945GZM-S2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=2429ce45-7592-4cb5-974d-7446cb495a5b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FG
  dmi.board.name: 945GZM-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFG:bd04/26/2007:svnGigabyteTechnologyCo.,Ltd.:pn945GZM-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn945GZM-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: 945GZM-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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/1769029/+subscriptions

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

[Desktop-packages] [Bug 1769029] Re: Display on Dell 1440x900 is not available

[Dave Goldsbrough]

Many bugs are now accumulating with this and similar issues surrounding Xorg. 
This is just one example 
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087
There are others. Some are related to Lenovo laptops but not all.
Shame that 18.04 LTS has been allowed to be released without this inherent bug 
being fixed. It is damaging Ubuntu reputation.

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

Title:
  Display on Dell 1440x900 is not available

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Monitor resolution is limited to 1024x768 with no option for higher
  resolution

  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
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  4 09:44:54 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd 82945G/GZ Integrated Graphics 
Controller [1458:d000]
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 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
  MachineType: Gigabyte Technology Co., Ltd. 945GZM-S2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=2429ce45-7592-4cb5-974d-7446cb495a5b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FG
  dmi.board.name: 945GZM-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFG:bd04/26/2007:svnGigabyteTechnologyCo.,Ltd.:pn945GZM-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn945GZM-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: 945GZM-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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/1769029/+subscriptions

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

[Desktop-packages] [Bug 1609466] Re: gnome-keyring-daemon crashed with SIGABRT in g_assertion_message()

[Launchpad Bug Tracker]

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

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

** Changed in: gnome-keyring (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-keyring-daemon crashed with SIGABRT in g_assertion_message()

Status in gnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  System configured with automatic login. Keyring dialog shows twice on
  login, but crashes both times. Left without a ssh agent running.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: gnome-keyring 3.18.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Aug  4 00:48:04 2016
  ExecutablePath: /usr/bin/gnome-keyring-daemon
  InstallationDate: Installed on 2016-05-12 (83 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  ProcCmdline: /usr/bin/gnome-keyring-daemon --start --components=ssh
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-keyring
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: gnome-keyring-daemon crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip docker libvirt libvirtd lpadmin plugdev 
sambashare sudo

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

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

[Desktop-packages] [Bug 1769091] Re: Xorg freeze on login

[Launchpad Bug Tracker]

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

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

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

Title:
  Xorg freeze on login

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04.
  If I give a wrong password during the login, it of course fails, and write an 
error message.
  But after I give the correct passord, the display freezes, I have to stop the 
PC, and start again.
  If after the giving the wrong password, I push the cancel and then I give the 
correct passord, everything is fine.
  This behavior occurs either on my real laptop either on vitualbox gest.

  Other problem:
  On virtualbox many thime (50%) freeses during the startup with the splash 
image, but this only happened on virtualbox gest, but not on the real laptop.

  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
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  4 10:05:01 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GpuHangFrequency: I don't know
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=03a9742e-c894-4b5a-9000-099248693bf6 ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  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/1769091/+subscriptions

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

[Desktop-packages] [Bug 1769091] Re: Xorg freeze on login

[Dave Goldsbrough]

Many bugs are now accumulating with this and similar issues surrounding Xorg. 
This is just one example 
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087
There are others. Some are related to Lenovo laptops but not all.
Shame that 18.04 LTS has been allowed to be released without this inherent bug 
being fixed. It is damaging Ubuntu reputation.

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

Title:
  Xorg freeze on login

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04.
  If I give a wrong password during the login, it of course fails, and write an 
error message.
  But after I give the correct passord, the display freezes, I have to stop the 
PC, and start again.
  If after the giving the wrong password, I push the cancel and then I give the 
correct passord, everything is fine.
  This behavior occurs either on my real laptop either on vitualbox gest.

  Other problem:
  On virtualbox many thime (50%) freeses during the startup with the splash 
image, but this only happened on virtualbox gest, but not on the real laptop.

  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
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  4 10:05:01 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GpuHangFrequency: I don't know
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=03a9742e-c894-4b5a-9000-099248693bf6 ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  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/1769091/+subscriptions

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

[Desktop-packages] [Bug 1769270] Re: Xorg freeze

[Launchpad Bug Tracker]

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

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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo T430.
  When I reboot the screen will freeze (requires reboot) before the login 
prompt if I have both my digital display port and vga plugged in while my 
laptop is open. If I unplug the external monitors it boots fine. If I boot then 
quickly close the laptop screen it boots fine.

  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
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  4 14:14:56 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3]
  InstallationDate: Installed on 2018-05-04 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 23472P2
  ProcEnviron:
   PATH=(custom, no User Name)
   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 quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET93WW (2.53 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23472P2
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET93WW(2.53):bd03/08/2013:svnLENOVO:pn23472P2:pvrThinkPadT430:rvnLENOVO:rn23472P2:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 23472P2
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  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/1769270/+subscriptions

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

[Desktop-packages] [Bug 1769270] Re: Xorg freeze

[Dave Goldsbrough]

Many bugs are now accumulating with this and similar issues surrounding Xorg.  
This is just one example 
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087
There are others.  Some are related to Lenovo laptops but not all.
Shame that 18.04 LTS has been allowed to be released without this inherent bug 
being fixed.  It is damaging Ubuntu reputation.

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo T430.
  When I reboot the screen will freeze (requires reboot) before the login 
prompt if I have both my digital display port and vga plugged in while my 
laptop is open. If I unplug the external monitors it boots fine. If I boot then 
quickly close the laptop screen it boots fine.

  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
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  4 14:14:56 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3]
  InstallationDate: Installed on 2018-05-04 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 23472P2
  ProcEnviron:
   PATH=(custom, no User Name)
   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 quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET93WW (2.53 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23472P2
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET93WW(2.53):bd03/08/2013:svnLENOVO:pn23472P2:pvrThinkPadT430:rvnLENOVO:rn23472P2:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 23472P2
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  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/1769270/+subscriptions

-- 
Mailing list: https://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 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[Lars Nyqvist]

Hi Donald,
I am writing this e-mail using your new
firefox_59.0.2+build1-0ubuntu0.14.04.4_armhf.deb version on a
TinkerOS, Debian GNU/Linux 9.4 (stretch) , kernel 4.4.71+
I started firefox in Downloads folder from terminal and got the following lines:
linaro@tinkerboard:~/Downloads$ firefox
[fresh] [error] probe_ppp_module, can't find libppGoogleNaClPluginChrome.so
[fresh] [error] probe_ppp_module, can't find libppGoogleNaClPluginChrome.so
[fresh] [error] probe_ppp_module, can't find libppGoogleNaClPluginChrome.so
[fresh] [error] probe_ppp_module, can't find libppGoogleNaClPluginChrome.so
[fresh] [error] probe_ppp_module, can't find libppGoogleNaClPluginChrome.so
[fresh] [error] probe_ppp_module, can't find libppGoogleNaClPluginChrome.so

Best regards and than you again Lars Nyqvist

On 5/5/18, James Donald <1711...@bugs.launchpad.net> wrote:
> @herrtimson I looked in the tarball and don't even see mention of my use
> of clang in mozconfig.
>
> Note I'm using a procedure similar to what Chituc outlined. If I kick
> off dpkg-buildpackage, interrupt it, then edit the generated backend.mk
> I would not expect that to appear in patch files. It's also possible
> that due to use of the -b flag it skips version control comparisons, so
> the C++ source diffs are not appearing either.
>
> For now I have documented pieces manually in this repo:
> https://github.com/jdonald/firefox-armhf
>
> I'll update that repo as more steps come to mind.
> firefox_59.0.2.build1-0ubuntu0.14.04.4.debian.tar.xz is available for
> download there in the releases tab if you'd like to take a look through
> it.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1733340).
> https://bugs.launchpad.net/bugs/1711337
>
> Title:
>   Firefox crashes at start on armv7L after 55.0.1 update
>
> Status in Mozilla Firefox:
>   Expired
> Status in firefox package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Firefox always crashes when launched after the 55.0.1 update on an
>   Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi),
>   even in safe mode.
>
>   I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for
>   ARM single-board computer) on a similar board (Orange Pi Plus 2e),
>   installed Firefox and experienced the same problem--it won't load
>   without crashing.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: firefox 55.0.1+build2-0ubuntu0.16.04.2
>   Uname: Linux 3.4.113-sun8i armv7l
>   AddonCompatCheckDisabled: False
>   AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
>   ApportVersion: 2.20.1-0ubuntu2.10
>   Architecture: armhf
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  jim1138 F pulseaudio
>/dev/snd/controlC0:  jim1138 F pulseaudio
>   BuildID: 20170814194718
>   Card0.Amixer.info:
>Card hw:0 'audiocodec'/'audiocodec'
>  Mixer name   : ''
>  Components   : ''
>  Controls  : 12
>  Simple ctrls  : 12
>   Card1.Amixer.info:
>Card hw:1 'sndhdmi'/'sndhdmi'
>  Mixer name   : ''
>  Components   : ''
>  Controls  : 1
>  Simple ctrls  : 1
>   Card1.Amixer.values:
>Simple mixer control 'hdmi audio format Function',0
>  Capabilities: enum
>  Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC'
> 'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO'
>  Item0: 'pcm'
>   Channel: Unavailable
>   CurrentDesktop: XFCE
>   Date: Thu Aug 17 05:37:00 2017
>   Extensions: extensions.sqlite corrupt or missing
>   ForcedLayersAccel: False
>   IncompatibleExtensions: Unavailable (corrupt or non-existant
> compatibility.ini or extensions.sqlite)
>   IpRoute:
>default via 192.168.10.1 dev eth0
>default via 192.168.10.1 dev wlan0  proto static  metric 600
>169.254.0.0/16 dev eth0  scope link  metric 1000
>192.168.10.0/24 dev eth0  proto kernel  scope link  src 192.168.10.107
>192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.108
> metric 600
>   Locales: extensions.sqlite corrupt or missing
>   PciMultimedia:
>
>   PciNetwork:
>
>   Profiles: Profile0 (Default) - LastVersion=55.0.1/20170814194718
>   RfKill:
>0: phy0: Wireless LAN
>   Soft blocked: no
>   Hard blocked: no
>   RunningIncompatibleAddons: False
>   SourcePackage: firefox
>   Themes: extensions.sqlite corrupt or missing
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/firefox/+bug/1711337/+subscriptions
>

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

Status in Mozilla Firefox:
  Expired
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Firefox always crashes