[Desktop-packages] [Bug 1730460] [NEW] Framerate drops when moving windows across physical displays

[Luis Alberto Pabón]

Public bug reported:

When dragging a window between displays, I can see cpu usage increase
while framerate drops dramatically to single numbers.

Desktop scaling is 1.0, one is a WXGA screen and another FHD.

Ubuntu session (wayland), 17.10.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
Uname: Linux 4.13.0-16-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Mon Nov  6 17:09:20 2017
DisplayManager: lightdm
GsettingsChanges:
 b'org.gnome.shell' b'favorite-apps' 
b"['/home/development/bin/firefox.desktop', 'org.gnome.Nautilus.desktop', 
'jetbrains-phpstorm.desktop', 'code.desktop', 'postman.desktop', 
'standard_notes.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'icon-theme' b"'ePapirus'"
 b'org.gnome.desktop.interface' b'gtk-theme' b"'DarkNumix'"
InstallationDate: Installed on 2016-03-13 (603 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2017-10-19 (17 days ago)

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


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

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

Title:
  Framerate drops when moving windows across physical displays

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When dragging a window between displays, I can see cpu usage increase
  while framerate drops dramatically to single numbers.

  Desktop scaling is 1.0, one is a WXGA screen and another FHD.

  Ubuntu session (wayland), 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Nov  6 17:09:20 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' 
b"['/home/development/bin/firefox.desktop', 'org.gnome.Nautilus.desktop', 
'jetbrains-phpstorm.desktop', 'code.desktop', 'postman.desktop', 
'standard_notes.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'icon-theme' b"'ePapirus'"
   b'org.gnome.desktop.interface' b'gtk-theme' b"'DarkNumix'"
  InstallationDate: Installed on 2016-03-13 (603 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-19 (17 days ago)

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

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

[Desktop-packages] [Bug 1730325] Re: Backup "Failed with an unknown error" with "No module named gi.repository"

[Michael Terry]

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

This was fixed in 17.10. The dependency is sorta there, but not as
tightly coupled as it could be.

But yeah you can install a package as a workaround.

** This bug has been marked a duplicate of bug 1641423
   Backup fails with message: 'Failed to execute child process "duplicity" (No 
such file or directory)' or 'No module named gi.repository': missing 
deja-dup-backend-gvfs, duplicity, and/or python-gi packages

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

Title:
  Backup "Failed with an unknown error" with "No module named
  gi.repository"

Status in deja-dup package in Ubuntu:
  New

Bug description:
  On a fresh install of Ubuntu 17.04, deja-dup consistently failed doing
  backup, both over SSH, to an external hard drive and to the internal
  drive. I tried initiating the backup both using the terminal and from
  the GUI. The backup window would show up for a couple of seconds
  before displaying «Failed with an unknown error».

  Running deja-dup --backup with DEJA_DUP_DEBUG=1 gave me the following:

  DUPLICITY: . Detaljer fra bakstykke-feilmelding: Traceback (most recent call 
last):
  DUPLICITY: .   File "/usr/bin/duplicity", line 1532, in 
  DUPLICITY: . with_tempdir(main)
  DUPLICITY: .   File "/usr/bin/duplicity", line 1526, in with_tempdir
  DUPLICITY: . fn()
  DUPLICITY: .   File "/usr/bin/duplicity", line 1364, in main
  DUPLICITY: . action = commandline.ProcessCommandLine(sys.argv[1:])
  DUPLICITY: .   File 
"/usr/lib/python2.7/dist-packages/duplicity/commandline.py", line 1122, in 
ProcessCommandLine
  DUPLICITY: . globals.backend = backend.get_backend(args[0])
  DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", 
line 223, in get_backend
  DUPLICITY: . obj = get_backend_object(url_string)
  DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", 
line 211, in get_backend_object
  DUPLICITY: . raise BackendException(_("Could not initialize backend: %s") 
% str(sys.exc_info()[1]))
  DUPLICITY: . BackendException: Klarte ikke \xe5 starte bakstykke. No module 
named gi.repository

  It turned out that installing the package python-gi solved the
  problem, and the backup now runs as expected. It seems to me that this
  package should have been a dependency of deja-dup.

  I am running deja-dup 34.4-0ubuntu1 and duplicity 0.7.06-2ubuntu3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1730325/+subscriptions

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

[Desktop-packages] [Bug 815626] Re: ERROR105 on browsing every 5 minutes

[Olivier Tilloy]

Given the age of the bug, I'll assume this is not relevant any longer.
Please file a new bug if you're facing similar issues.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  ERROR105 on browsing every 5 minutes

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  I have Ubuntu 11.04 and from time to time when Im browsing on chrome
  it gives me error 105:

  Error 105 (net::ERR_NAME_NOT_RESOLVED): Unable to resolve the server's
  DNS address.

  I'm getting sick of it is there anyway to fix this?

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

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

[Desktop-packages] [Bug 820329] Re: ebay sellers form does not work

[Olivier Tilloy]

Given the age of the bug, I'll assume this is not relevant any longer.
Please re-open if the issue is still affecting you.

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

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

Title:
  ebay sellers form does not work

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Selling form does not work. It always reports error:

  "Please provide the correct information in the highlighted fields.
  PayPal - To list this item, you need to accept PayPal as a payment method."

  This occurs even though paypal is accepted as a payment method. Works
  fine under Firefox.

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

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

[Desktop-packages] [Bug 813946] Re: Huge No. of interrupts by SignalSender in Chromium-Browser

[Olivier Tilloy]

The description seems to indicate that this bug was most likely fixed upstream.
Given the age of the bug, I'll assume this is not relevant any longer. Please 
file a new bug if you're facing similar issues.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Huge No. of interrupts by SignalSender in Chromium-Browser

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Huge number of interrupts are being generated by Chromium-Browser with the 
heading 'SignalSender' and 'chromium-browser' as reported by powertop.
  Steps:
  1. Open powertop and keep it ready in background.
  2. Open chromium browser and open a tab or two.
  3. Monitor the interrupts in powertop and look for number of interrupts under 
'chromium-browser' and 'SignalSender'.
  4. Close and observe powertop again.  The number of interrupts are largely 
reduced.
  5. Open something with flash or video content. The number of interrupts again 
goes beyond the roof and CPU usage becomes very high.

  It seems to be a upstream bug and moving to version 14 or above seems
  to have resolved this regression. Needs to be tested and recent
  versions made available in the Ubuntu repository. I have not myself
  tested it, because of lack to tools and expertise, but the upstream
  bug reports in chromium-browser project seems to indicate so.

  What you expected to happen - No. of interrupts / CPU usage should be
  under reasonable limits.

  What happened instead - High CPU usage.

  $ lsb_release -rd
  Description:  Ubuntu 10.10
  Release:  10.10

  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 12.0.742.112~r90304-0ubuntu0.10.10.1
Candidate: 12.0.742.112~r90304-0ubuntu0.10.10.1
Version table:
   *** 12.0.742.112~r90304-0ubuntu0.10.10.1 0
  500 http://archive.ubuntu.com/ubuntu/ maverick-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu/ maverick-security/universe 
amd64 Packages
  100 /var/lib/dpkg/status
   6.0.472.63~r59945-0ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ maverick/universe amd64 Packages

  $ uname -a
  Linux ubnode6 2.6.35-30-server #54-Ubuntu SMP Tue Jun 7 20:13:05 UTC 2011 
x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 843620] Re: lubuntu / gnome mplayer freezes

[Olivier Tilloy]

Given the age of the bug, I'll assume this is not relevant any longer.
Please file a new bug if you're facing similar issues.

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

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

Title:
  lubuntu / gnome mplayer freezes

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  I have lubuntu 11.04. I have had continuous trouble with gnome mplayer
  freezing entire computer. It only happens somtimes, but often, and
  only when video/film ends; the second video ends it freezes. It
  happens in browser (embedded mplayer), both Chromium and Firefox (
  with the flash video replacer adddon).  Sometimes entire desktop is
  frozen, sometimes the indicator arrow can be moved around, but cannot
  make anything work. Keys functions don't work either (like ctrl-
  alt-w). F keys still work; F1 logs out, and I can log in to a terminal
  like black screen, and then command "sudo reboot".

  The freeze problem is quite consistent, even after new clean install
  from CD the same problem occurs. I replaced the internal hard drive
  recently, and the same issue appeared shortly after lubuntu install.
  It is quite and old Packard Bell laptop, but I doubt it is unique.

  VLC does not result in freeze, only use of gnome mplayer.

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

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

[Desktop-packages] [Bug 1730469] [NEW] Xorg freezes constitently on login

[Maxime Chambonnet]

Public bug reported:

Hello,
I have a Sandybridge-B970 X301-Asus laptop. I am used to dual boot on it : 
win10 and Ubuntu Xenial on a 275 GB SSD.
Yesterday I manually forced shut down on win10 which looked hung on 
~"preparation... do not shut down".
Windows recovered, but Ubuntu was corrupted it seems.
Grub2 launches, Ubuntu boots. I reach (Unity?) graphical login. Then I cannot 
input mouse nor keyboard, and after a few inputs login prompt hangs. The UI 
displays "connected to ethernet". I cannot Alt Gr Fx to other ttys.
I can REISUB, I can launch a recovery mode and get a root shell. I can SSH 
after normal boot from an external Debian system.
Filesystem looks OK. Not sure but for some reason directories seems to have 
appeared in /root (git..)

My SSD partitions : https://postimg.org/image/2hmo7pgfiz/, on top of
debug info.

Best regards!

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg (not installed)
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
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Mon Nov  6 18:38:53 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:14f7]
InstallationDate: Installed on 2017-03-04 (247 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: ASUSTeK COMPUTER INC. X301A1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic.efi.signed 
root=UUID=84fd9c9d-fdb2-4ebf-a754-115d068500e0 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/02/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X301A1.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X301A1
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.:bvrX301A1.204:bd05/02/2012:svnASUSTeKCOMPUTERINC.:pnX301A1:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX301A1:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X301A1
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Mon Nov  6 18:33:32 2017
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.7
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug false-gpu-hang freeze ubuntu xenial

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

Title:
  Xorg freezes constitently on login

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello,
  I have a Sandybridge-B970 X301-Asus laptop. I am used to dual boot on it : 
win10 and Ubuntu Xenial on a 275 GB SSD.
  Yesterday I manually forced shut down on win10 which looked hung on 
~"preparation... do not shut down".
  Windows recovered, but Ubuntu was corrupted it seems.
  Grub2 launches, Ubuntu boots. I reach (Unity?) graphical login. Then I cannot 
input mouse nor keyboard, and after a few inputs login prompt hangs. The UI 
displays "connected to ethernet". I cannot Alt Gr Fx to other ttys.
  I can REISUB, I can launch a recovery mode and get a root shell. I can SSH 
after normal boot from an external Debian system.
  Filesystem looks OK. Not sure but for some reason directories seems to have 
appeared in /root (git..)

  My SSD partitions : https://postimg.org/image/2hmo7pgfiz/, on top of
  debug info.

  Best regards!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  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
  

[Desktop-packages] [Bug 1730458] [NEW] Ubuntu (gnome) freezes temporarily upon login

[Luis Alberto Pabón]

Public bug reported:

I have noticed that gnome-shell CPU usage shoots up to over 100% for a
few seconds shortly after logging in, completely freezing the shell for
a good 10-20s.

This happens on a migrated Unity 7 > Ubuntu session as well as on a
completely new Ubuntu session (eg a user just created to test this).

Ubuntu 17.10 (upgraded from 17.04), Ubuntu session (Wayland).

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
Uname: Linux 4.13.0-16-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Mon Nov  6 17:05:45 2017
DisplayManager: lightdm
GsettingsChanges:
 b'org.gnome.shell' b'favorite-apps' 
b"['/home/development/bin/firefox.desktop', 'org.gnome.Nautilus.desktop', 
'jetbrains-phpstorm.desktop', 'code.desktop', 'postman.desktop', 
'standard_notes.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'icon-theme' b"'ePapirus'"
 b'org.gnome.desktop.interface' b'gtk-theme' b"'DarkNumix'"
InstallationDate: Installed on 2016-03-13 (603 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2017-10-19 (17 days ago)

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


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

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

Title:
  Ubuntu (gnome) freezes temporarily upon login

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have noticed that gnome-shell CPU usage shoots up to over 100% for a
  few seconds shortly after logging in, completely freezing the shell
  for a good 10-20s.

  This happens on a migrated Unity 7 > Ubuntu session as well as on a
  completely new Ubuntu session (eg a user just created to test this).

  Ubuntu 17.10 (upgraded from 17.04), Ubuntu session (Wayland).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Nov  6 17:05:45 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' 
b"['/home/development/bin/firefox.desktop', 'org.gnome.Nautilus.desktop', 
'jetbrains-phpstorm.desktop', 'code.desktop', 'postman.desktop', 
'standard_notes.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'icon-theme' b"'ePapirus'"
   b'org.gnome.desktop.interface' b'gtk-theme' b"'DarkNumix'"
  InstallationDate: Installed on 2016-03-13 (603 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-19 (17 days ago)

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

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

[Desktop-packages] [Bug 828182] Re: Chromium occasionally locks the entire desktop

[Olivier Tilloy]

This report is against a release of Ubuntu that is not supported any
longer. Given the age of the bug let's assume this is not relevant any
longer. Please file a new bug if you're facing similar issues.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Chromium occasionally locks the entire desktop

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Occasionally, Chromium 13.0.782.107 will grab the cursor and never
  give it back.  This locks the entire desktop, with no way to regain
  control short of a reboot.  It's difficult to reproduce though.  As
  far as I can tell, it's always related to trying to scroll, or
  clicking on a link in a different window (yes, it's my default
  browser).  When the cursor changes, it sometimes never gives up the
  grab.

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

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

[Desktop-packages] [Bug 824455] Re: popup window dimensions should follow zoom factor

[Olivier Tilloy]

In recent versions of chromium, fixed-size popups are still fixed (i.e.
not following zoom factor of the caller). I'm guessing this is by
design. Please file a bug at https://crbug.com/ to discuss this
upstream.

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

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

Title:
  popup window dimensions should follow zoom factor

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  The dimensions of a popup window are specified by the web-developer in
  javascript using pixel sizes. However if a user sets a zoom factor
  other than 100%, the popup window still uses the fixed pixel
  dimensions. This results in parts of the website invisible/laying
  outside of the popup window.

  Thus the window dimensions of a popup should be scaled by the zoom
  factor too (but not bigger than the screen).

  For example a 400px*500px popup has a search or login  field on the
  right side and the website is displayed with 150% zoom factor. The
  site is now 600px wide, but the popup is still 400px wide, so the
  search field lays outside the popup.

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

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

[Desktop-packages] [Bug 832710] Re: video.canPlayType reports h264 report even though this is not true

[Olivier Tilloy]

This appears to be fixed.

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

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

Title:
  video.canPlayType reports h264 report even though this is not true

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Version: 13.0.782.215~r97094-0ubuntu1
  Description:  Ubuntu oneiric (development branch)
  Release:  11.10

  with chromium-codecs-ffmpeg installed(default, only ogg and webm
  support)

  chromium still reports it might be able to play back h264 video
  document.createElement('video').canPlayType('video/mp4; codecs*="avcl.42001E, 
mp4a.40.2"')
  should return "" and not "maybe"

  this is used to detect which format works,

  example page using this: http://www.youtube.com/html5

  this will cause video playback to fail on pages that prefere h264 over webm 
support,
  on those pages, videos will just not work.
  video.canPlayType was specifically added to the video tag api to prevent this 
from happening.

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

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

[Desktop-packages] [Bug 1730082] Re: 17.10 Shutdown Delayed 10 Min Due To Wifi

[Brian Murray]

** Tags added: artful

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

Title:
  17.10 Shutdown Delayed 10 Min Due To Wifi

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

Bug description:
  My Lenovo G50 laptop takes roughly 10 min to shut down, due to the
  wifi. After turning off the "automatically connect" option, shutdown
  occurs normally. I have found the following processes to have caused
  the delay:

  WPA supplicant
  Network manager
  Raise network interfaces

  I hope this can be resolved soon! Thankyou.

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

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

[Desktop-packages] [Bug 1724923] Re: VLANs are not always listed in Settings - Network

[Launchpad Bug Tracker]

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

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

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

Title:
  VLANs are not always listed in Settings - Network

Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when I open Settings - Network I see my VLANs, sometimes I
  don't.  I don't think changes made in nm-connection-editor are being
  properly recognized by Gnome.

  I use nm-connection-editor to add and configure VLANs.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-gnome 1.8.4-1ubuntu1
  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: Thu Oct 19 11:33:19 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.50.253 dev vlan757 proto static metric 400 
   169.254.0.0/16 dev vlan757 scope link metric 1000 
   192.168.50.0/24 dev vlan757 proto kernel scope link src 192.168.50.222 
metric 400
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH SLAVE 
   VLAN Camera 1a430a37-b4b3-461c-87bd-d60b547dd369  vlan
1508437983  Thu 19 Oct 2017 11:33:03 AM PDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/4  yes vlan757  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8  --
   Wired connection 1  23ca82a4-d9c5-3d59-ac84-56db17873201  802-3-ethernet  
1508433170  Thu 19 Oct 2017 10:12:50 AM PDT  no   4294966297
no/org/freedesktop/NetworkManager/Settings/1  no  --   --   
  --  --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1724923] Re: VLANs are not always listed in Settings - Network

[Halvor Lyche Strandvoll]

Also experiencing the same issue, sometimes when they show up it's in
the Bluetooth section.

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

Title:
  VLANs are not always listed in Settings - Network

Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when I open Settings - Network I see my VLANs, sometimes I
  don't.  I don't think changes made in nm-connection-editor are being
  properly recognized by Gnome.

  I use nm-connection-editor to add and configure VLANs.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-gnome 1.8.4-1ubuntu1
  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: Thu Oct 19 11:33:19 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.50.253 dev vlan757 proto static metric 400 
   169.254.0.0/16 dev vlan757 scope link metric 1000 
   192.168.50.0/24 dev vlan757 proto kernel scope link src 192.168.50.222 
metric 400
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH SLAVE 
   VLAN Camera 1a430a37-b4b3-461c-87bd-d60b547dd369  vlan
1508437983  Thu 19 Oct 2017 11:33:03 AM PDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/4  yes vlan757  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8  --
   Wired connection 1  23ca82a4-d9c5-3d59-ac84-56db17873201  802-3-ethernet  
1508433170  Thu 19 Oct 2017 10:12:50 AM PDT  no   4294966297
no/org/freedesktop/NetworkManager/Settings/1  no  --   --   
  --  --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1730478] [NEW] using shift key to wake up display causes invalid password

[Scott Moser]

Public bug reported:

Summary: hitting 'shift' before typing your password can get "stuck" down and
cause you to not be able to log in.

I have a habit of using the shift key wake the display of my system
after i've been away from it for a while, and then typing my password.

I started having trouble logging in, as if my fingers weren't typing the
right password.  It took me a while to figure out what was going on, but i
thought maybe that I'd inadvertantly hit 'caps-lock' and that was causing
the issue.  So I hit it again, and then logged in successfully.

However, upon login I found that caps-lock was enabled.

So to reproduce:
 a.) let the screen lock or lock it manually.
 b.) hit shift key (i hit left shift)
 c.) type password correctly: watch fail to login
 d.) note that you can hit caps-lock and then successfully login
 e.) note that after login, caps lock is set, that you didn't make this all up.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-screensaver 3.6.1-7ubuntu6
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov  6 13:12:29 2017
EcryptfsInUse: Yes
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GsettingsGnomeSession:
 org.gnome.desktop.session session-name 'ubuntu'
 org.gnome.desktop.session idle-delay uint32 300
InstallationDate: Installed on 2015-07-23 (837 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-screensaver
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  using shift key to wake up display causes invalid password

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  Summary: hitting 'shift' before typing your password can get "stuck" down and
  cause you to not be able to log in.

  I have a habit of using the shift key wake the display of my system
  after i've been away from it for a while, and then typing my password.

  I started having trouble logging in, as if my fingers weren't typing the
  right password.  It took me a while to figure out what was going on, but i
  thought maybe that I'd inadvertantly hit 'caps-lock' and that was causing
  the issue.  So I hit it again, and then logged in successfully.

  However, upon login I found that caps-lock was enabled.

  So to reproduce:
   a.) let the screen lock or lock it manually.
   b.) hit shift key (i hit left shift)
   c.) type password correctly: watch fail to login
   d.) note that you can hit caps-lock and then successfully login
   e.) note that after login, caps lock is set, that you didn't make this all 
up.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screensaver 3.6.1-7ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 13:12:29 2017
  EcryptfsInUse: Yes
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 300
  InstallationDate: Installed on 2015-07-23 (837 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1724557] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()

[Brian Neltner]

I am not certain if my crash is the same as this bug, but this seems
most likely the same issue that I see when I attempt to lock my session.
Upon locking the session it immediately crashes gnome-shell. I am using
an Intel NUC.

My dmesg reports:

gnome-shell[17362]: segfault at 38 ip 7fe14c425c30 sp
7ffc4f950868 error 4 in libmutter-1.so.0.0.0[7fe14c3d3000+141000]

I have attached the /var/crash file for more information, please let me
know if I should look elsewhere for this bug as I am not 100% certain it
is the same cause. It is currently using gnome-shell 3.26.1-0ubuntu4.

** Attachment added: "_usr_bin_gnome-shell.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724557/+attachment/5004930/+files/_usr_bin_gnome-shell.1000.crash

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

Title:
  gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()

Status in Mutter:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Hi all, 
  Originally I was reporting bug 1717170, about session crash after monitor 
disconnect/switch-off/input change on desktop PC and the bug was fixed 
according to bug tracker. But now, after gnome-shell and mutter update, the 
crash goes worse. Now it is not just session kick-out but complete crash. Same 
events can be used to reproduce the crash. This time also crash files was 
created.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  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: Wed Oct 18 13:52:07 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-09-11 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f475acbac30 :   
movss  0x38(%rdi),%xmm0
   PC (0x7f475acbac30) ok
   source "0x38(%rdi)" (0x0038) not located in a known VMA region (needed 
readable region)!
   destination "%xmm0" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_logical_monitor_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_wayland_get_geometry_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_sync_state () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

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

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

[Desktop-packages] [Bug 775971] Re: Webpages often not loading in Chromium-browser

[Olivier Tilloy]

Given the age of the bug, I'll assume this is not relevant any longer.
Please file a new bug if you're facing similar issues.

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

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

Title:
  Webpages often not loading in Chromium-browser

Status in Linux Mint:
  Triaged
Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Webpages often not loading in Chromium-browser, version 11.0.696.57
  (82915). This is the latest version. Built on Ubuntu 10.04, running on
  Linux Mint 9 Xfce "Isadora". There is this same problem in Google
  Chrome, version 11.0.696.57. This, too, is the latest version.
  Sometimes the pages partially load, then cease loading. I'll get a
  window giving me the choices of "Kill Page" or "Wait".

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

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

[Desktop-packages] [Bug 1730453] Re: package xserver-xorg-input-evdev (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/share/X11/xorg.conf.d/10-evdev.conf', que também está no

[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 xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/1730453

Title:
  package xserver-xorg-input-evdev (not installed) failed to
  install/upgrade: a tentar sobre-escrever
  '/usr/share/X11/xorg.conf.d/10-evdev.conf', que também está no pacote
  xserver-xorg-core-lts-utopic 2:1.16.0-1ubuntu1.2~trusty2

Status in xserver-xorg-input-evdev package in Ubuntu:
  New

Bug description:
  Updating.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-input-evdev (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-77.99~14.04.1-generic 3.16.7-ckt27
  Uname: Linux 3.16.0-77-generic i686
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: i386
  Date: Mon Nov  6 13:51:27 2017
  DuplicateSignature: package:xserver-xorg-input-evdev:(not installed):a tentar 
sobre-escrever '/usr/share/X11/xorg.conf.d/10-evdev.conf', que também está no 
pacote xserver-xorg-core-lts-utopic 2:1.16.0-1ubuntu1.2~trusty2
  ErrorMessage: a tentar sobre-escrever 
'/usr/share/X11/xorg.conf.d/10-evdev.conf', que também está no pacote 
xserver-xorg-core-lts-utopic 2:1.16.0-1ubuntu1.2~trusty2
  InstallationDate: Installed on 2016-10-27 (375 days ago)
  InstallationMedia: Lubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: xserver-xorg-input-evdev
  Title: package xserver-xorg-input-evdev (not installed) failed to 
install/upgrade: a tentar sobre-escrever 
'/usr/share/X11/xorg.conf.d/10-evdev.conf', que também está no pacote 
xserver-xorg-core-lts-utopic 2:1.16.0-1ubuntu1.2~trusty2
  UpgradeStatus: Upgraded to xenial on 2017-10-27 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1730453/+subscriptions

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

[Desktop-packages] [Bug 1729028] Re: gnome-shell crashes after period of inactivity

[Echo Nolan]

I opened up the .crash file and it has the same stack trace as in
#1724557. I also get the crash turning the monitor off. I don't know if
you guys want to mark this one as duplicate or what.

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

Title:
  gnome-shell crashes after period of inactivity

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Gnome shell crashes reliably and only after a period of inactivity
  (15+ minutes). I have not seen it crash while using the desktop - even
  for hours at a time. I suspect it has something to do with locking the
  screen or turning off the monitor. However even after attempting to
  disable both lockscreen and blank screen it still happens.

  After a crash dmesg shows [ 3726.608957] gnome-shell[2666]: segfault
  at 38 ip 7fc6a7330c30 sp 7fff0d12fe78 error 4 in
  libmutter-1.so.0.0.0[7fc6a72de000+141000]

  When the crash happens it goes back to the login screen. Logging in
  works fine.

  It happens pretty reliably but will sometimes successfully lock and
  blank the screen. I would say it happens 90% of the time I leave the
  computer alone for awhile.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 11:34:11 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'google-chrome.desktop', 'firefox.desktop', 'code.desktop', 
'org.gnome.Terminal.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25'
  InstallationDate: Installed on 2017-07-18 (105 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-18 (12 days ago)

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

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

[Desktop-packages] [Bug 778445] Re: Package name conflicts with chromium-browser

[Olivier Tilloy]

There's no binary package called chromium in ubuntu any longer.

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

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Package name conflicts with chromium-browser

Status in chromium package in Ubuntu:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: chromium

  The package name "chromium" for "chromium-bsu" is assigned
  inappropriately and is confusing when taken into account the growing
  web browser chromium with the package name "chromium-browser" . Its
  nice that chrmoium-browser is the name given to the browser because of
  an already existing package called "chromium" but the name "chromium"
  to a shooting game will trick users to install it

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

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

[Desktop-packages] [Bug 780863] Re: /usr/bin/chromium-browser doesn't pass through user-agent flag

[Olivier Tilloy]

Given the age of the bug, I'll assume this is not relevant any longer.
Please file a new bug if you're facing similar issues.

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

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

Title:
  /usr/bin/chromium-browser doesn't pass through user-agent flag

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: chromium-browser

  I'm trying to test a website's mobile interface on my desktop.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Natty 11.04
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  11.0.696.57~r82915-0ubuntu0.11.04.1
  3) What you expected to happen
  Launching chromium with `chromium-browser --user-agent="foobar"`, then 
confirming the user-agent by typing "about:" in the address bar should show the 
user agent to be "foobar"
  4) What happened instead
  The /usr/bin/chromium-browser script didn't pass on the user-agent flag to 
/usr/lib/chromium-browser/chromium-browser, so when i went to check "about:", 
it still showed up with the default chromium user agent.

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

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

[Desktop-packages] [Bug 795969] Re: Session management - Restore previous session results in unable state after crash

[Olivier Tilloy]

This sort of issue has hopefully been fixed upstream, with the many
versions since the bug was initially reported. I myself use the restore
session option heavily, and sometimes run into a gnome shell crash that
corrupts my current browser session, but it has always restored just
fine.

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

Title:
  Session management - Restore previous session results in unable state
  after crash

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  With 'Restore previous session and Chrome active at moment of crash results 
in 100% reproducible unusable state.
  Because the 'Restore'-button of Chrome  when clicked, will inevitably render 
the cursor into a 'finger' like a hyperlink without any way out but a hard 
reboot.
  At that reboot, Chrome will come up inevitably, with the offer to 'Restore' 
with a click, which will result in a cursor showing a 'finger' like a hyperlink 
without any way out but a hard reboot.
  Ad infinitum.
  My only way out here was to NOT click 'Restore' in Chrome, wait sufficiently, 
and then all my 30+ tabs were gone; lost. It took me almost an hour to get them 
back; hopefully complete.

  How to reproduce: 
  1. Set 'Session management' to 'Restore previous session'
  2. Start Chrome, open a plurality of tabs.
  3. Reset PC hard
  4. After reboot, click the automatically offered button 'Restore' 

  Expected: Normal start of all previously open sessions and proper
  restauration of Chrome tabs

  Actual result: Cursor turns into 'finger'-shape, keyboard becomes
  unusable, so does any mouse interaction (no click, neither on
  applications nor buttons ('shutdown'!))

  Workaround: Disable  'Session management'  'Restore previous session'
  and change it to 'Session management' 'Start with an empty session'

  Reproducibility. 100%

  Linux mybox 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 
x86_64 x86_64 x86_64 GNU/Linux
  11.04 at daily most recent upgrade state

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

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

[Desktop-packages] [Bug 795969] Re: Session management - Restore previous session results in unable state after crash

[Olivier Tilloy]

Given the age of the bug, I'll assume this is not relevant any longer.
Please file a new bug if you're facing similar issues.

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

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

Title:
  Session management - Restore previous session results in unable state
  after crash

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  With 'Restore previous session and Chrome active at moment of crash results 
in 100% reproducible unusable state.
  Because the 'Restore'-button of Chrome  when clicked, will inevitably render 
the cursor into a 'finger' like a hyperlink without any way out but a hard 
reboot.
  At that reboot, Chrome will come up inevitably, with the offer to 'Restore' 
with a click, which will result in a cursor showing a 'finger' like a hyperlink 
without any way out but a hard reboot.
  Ad infinitum.
  My only way out here was to NOT click 'Restore' in Chrome, wait sufficiently, 
and then all my 30+ tabs were gone; lost. It took me almost an hour to get them 
back; hopefully complete.

  How to reproduce: 
  1. Set 'Session management' to 'Restore previous session'
  2. Start Chrome, open a plurality of tabs.
  3. Reset PC hard
  4. After reboot, click the automatically offered button 'Restore' 

  Expected: Normal start of all previously open sessions and proper
  restauration of Chrome tabs

  Actual result: Cursor turns into 'finger'-shape, keyboard becomes
  unusable, so does any mouse interaction (no click, neither on
  applications nor buttons ('shutdown'!))

  Workaround: Disable  'Session management'  'Restore previous session'
  and change it to 'Session management' 'Start with an empty session'

  Reproducibility. 100%

  Linux mybox 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 
x86_64 x86_64 x86_64 GNU/Linux
  11.04 at daily most recent upgrade state

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

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

[Desktop-packages] [Bug 1729028] Re: gnome-shell crashes after period of inactivity

[David Burke]

Turning off the monitor is a VERY simple way to reproduce the issue. I
was able to work around it by changing my sleep settings (super
wasteful!) so that the monitor never goes off. I thought I tried this
before...but it works now.

I attempted to follow the generic crash report instructions. I got a
apport gui to ask about submitting and I hit submit. I didn't get any
confirmation it did anything however. I made a copy of the .crash file
if that is helpful - let me know what to do with it.

** Summary changed:

- gnome-shell crashes after period of inactivity
+ gnome-shell crashes when monitor sleeps or is turned off

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

Title:
  gnome-shell crashes when monitor sleeps or is turned off

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Gnome shell crashes reliably and only after a period of inactivity
  (15+ minutes). I have not seen it crash while using the desktop - even
  for hours at a time. I suspect it has something to do with locking the
  screen or turning off the monitor. However even after attempting to
  disable both lockscreen and blank screen it still happens.

  After a crash dmesg shows [ 3726.608957] gnome-shell[2666]: segfault
  at 38 ip 7fc6a7330c30 sp 7fff0d12fe78 error 4 in
  libmutter-1.so.0.0.0[7fc6a72de000+141000]

  When the crash happens it goes back to the login screen. Logging in
  works fine.

  It happens pretty reliably but will sometimes successfully lock and
  blank the screen. I would say it happens 90% of the time I leave the
  computer alone for awhile.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 11:34:11 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'google-chrome.desktop', 'firefox.desktop', 'code.desktop', 
'org.gnome.Terminal.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25'
  InstallationDate: Installed on 2017-07-18 (105 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-18 (12 days ago)

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

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

[Desktop-packages] [Bug 1729985] Re: /usr/lib/epiphany-search-provider:11:wl_list_insert_list:wl_priv_signal_emit:wl_display_destroy:WebCore::PlatformDisplayWayland::~PlatformDisplayWayland:WebCore::P

[Launchpad Bug Tracker]

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

** Changed in: epiphany-browser (Ubuntu)
   Status: New => Confirmed

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

Title:
  /usr/lib/epiphany-search-
  
provider:11:wl_list_insert_list:wl_priv_signal_emit:wl_display_destroy:WebCore::PlatformDisplayWayland::~PlatformDisplayWayland:WebCore::PlatformDisplayWayland::~PlatformDisplayWayland

Status in epiphany-browser package in Ubuntu:
  Confirmed

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

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

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

[Desktop-packages] [Bug 840153] Re: Menu can't be activated by keyboard

[Olivier Tilloy]

Tested in xenial with chromium 63, Alt+F and Alt+F10 both display
chromium's menu.

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

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

Title:
  Menu can't be activated by keyboard

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  The Unity menu bar doesn't work in Chromium using the keyboard.

  Holding down Alt makes the Chromium menu entries appear in the menu
  bar, as with other apps, but then pressing one of the underlined
  letters ('F' for 'File', 'V' for 'View', etc) doesn't do anything.

  Nor does pressing F10 activate the menu.

  The only way of choosing a menu option involves using the mouse.

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

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

[Desktop-packages] [Bug 1730469] Re: Display session freezes constitently on login after Win10 dual boot crash - Ubuntu 16.04

[Maxime Chambonnet]

** Summary changed:

- Xorg freezes constitently on login
+ Display session freezes constitently on login after Win10 dual boot crash - 
Ubuntu 16.04

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

Title:
  Display session freezes constitently on login after Win10 dual boot
  crash - Ubuntu 16.04

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello,
  I have a Sandybridge-B970 X301-Asus laptop. I am used to dual boot on it : 
win10 and Ubuntu Xenial on a 275 GB SSD.
  Yesterday I manually forced shut down on win10 which looked hung on 
~"preparation... do not shut down".
  Windows recovered, but Ubuntu was corrupted it seems.
  Grub2 launches, Ubuntu boots. I reach (Unity?) graphical login. Then I cannot 
input mouse nor keyboard, and after a few inputs login prompt hangs. The UI 
displays "connected to ethernet". I cannot Alt Gr Fx to other ttys.
  I can REISUB, I can launch a recovery mode and get a root shell. I can SSH 
after normal boot from an external Debian system.
  Filesystem looks OK. Not sure but for some reason directories seems to have 
appeared in /root (git..)

  My SSD partitions : https://postimg.org/image/2hmo7pgfiz/, on top of
  debug info.

  Best regards!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Nov  6 18:38:53 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:14f7]
  InstallationDate: Installed on 2017-03-04 (247 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: ASUSTeK COMPUTER INC. X301A1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic.efi.signed 
root=UUID=84fd9c9d-fdb2-4ebf-a754-115d068500e0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X301A1.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X301A1
  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.:bvrX301A1.204:bd05/02/2012:svnASUSTeKCOMPUTERINC.:pnX301A1:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX301A1:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X301A1
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Nov  6 18:33:32 2017
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: modeset

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

-- 
Mailing list: https://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 1706889] Re: package chromium-browser 59.0.3071.109-0ubuntu0.17.04.1360 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it befo

[Olorunsegun Olajide Idowu]

Thanks, will try that.

On Nov 6, 2017 4:02 PM, "Olivier Tilloy" 
wrote:

> Are you still affected by that issue?
> If so, can you try the following command in a terminal:
>
> sudo apt-get install --reinstall chromium-browser
>
> ** Changed in: chromium-browser (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1706889
>
> Title:
>   package chromium-browser 59.0.3071.109-0ubuntu0.17.04.1360 failed to
>   install/upgrade: package is in a very bad inconsistent state; you
>   should  reinstall it before attempting a removal
>
> Status in chromium-browser package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Nothing really. Just get popups that the chromium browser is closing
>   when I start it, so I reported this. Using the 17.04 and fully updated
>   as on Thursday 27th July 2017.
>
>   Thanks. Great OS, great tools. Will never use Windows anymore.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 17.04
>   Package: chromium-browser 59.0.3071.109-0ubuntu0.17.04.1360
>   ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
>   Uname: Linux 4.10.0-28-generic x86_64
>   ApportVersion: 2.20.4-0ubuntu4.5
>   AptOrdering:
>chromium-browser:amd64: Remove
>NULL: ConfigurePending
>   Architecture: amd64
>   DRM.card0-DP-1:
>enabled: disabled
>dpms: Off
>status: disconnected
>edid-base64:
>modes:
>   DRM.card0-HDMI-A-1:
>enabled: disabled
>dpms: Off
>status: disconnected
>edid-base64:
>modes:
>   DRM.card0-LVDS-1:
>enabled: enabled
>dpms: On
>status: connected
>edid-base64: AP///wAOFMcUAA8VAQOAIhN4Ck5Nnld
> UkSYPUFQBAQEBAQEBAQEBAQEBAQEBeB1WwlAAJjA7JzYAWMIQAAAYeB1
> WwlAAJjA7JzYAWMIQAAAY/gBDUFQKICAgICAgICAgAABDTEFBMTU2V0IxMUEgANo=
>modes: 1366x768
>   DRM.card0-VGA-1:
>enabled: disabled
>dpms: Off
>status: disconnected
>edid-base64:
>modes:
>   Date: Wed Jul 26 16:07:08 2017
>   Desktop-Session:
>'None'
>'None'
>'None'
>   DpkgTerminalLog:
>dpkg: error processing package chromium-browser (--remove):
> package is in a very bad inconsistent state; you should
> reinstall it before attempting a removal
>   Env:
>'None'
>'None'
>   ErrorMessage: package is in a very bad inconsistent state; you should
> reinstall it before attempting a removal
>   InstallationDate: Installed on 2017-07-25 (1 days ago)
>   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
>   InstalledPlugins:
>
>   Load-Avg-1min: 4.96
>   Load-Processes-Running-Percent:   0.4%
>   Lsusb:
>Bus 002 Device 003: ID 090c:37b0 Silicon Motion, Inc. - Taiwan
> (formerly Feiya Technology Corp.)
>Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching
> Hub
>Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching
> Hub
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: Hewlett-Packard HP G62 Notebook PC
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic
> root=UUID=f03b9429-c787-4532-a66b-a145f1b1e393 ro quiet splash
> vt.handoff=7
>   SourcePackage: chromium-browser
>   Title: package chromium-browser 59.0.3071.109-0ubuntu0.17.04.1360
> failed to install/upgrade: package is in a very bad inconsistent state; you
> should  reinstall it before attempting a removal
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 02/10/2010
>   dmi.bios.vendor: Hewlett-Packard
>   dmi.bios.version: F.07
>   dmi.board.asset.tag: Base Board Asset Tag
>   dmi.board.name: 1425
>   dmi.board.vendor: Hewlett-Packard
>   dmi.board.version: 54.13
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Hewlett-Packard
>   dmi.chassis.version: N/A
>   dmi.modalias: dmi:bvnHewlett-Packard:bvrF.07:bd02/10/2010:svnHewlett-
> Packard:pnHPG62NotebookPC:pvr049D102027102:
> rvnHewlett-Packard:rn1425:rvr54.13:cvnHewlett-Packard:ct10:cvrN/A:
>   dmi.product.name: HP G62 Notebook PC
>   dmi.product.version: 049D102027102
>   dmi.sys.vendor: Hewlett-Packard
>   modified.conffile..etc.default.chromium-browser: [deleted]
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1706889/+
> subscriptions
>

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

Title:
  package chromium-browser 59.0.3071.109-0ubuntu0.17.04.1360 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting a removal

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Nothing really. Just get popups that the chromium browser is closing
  

[Desktop-packages] [Bug 1730253] [NEW] Clamshell mode only works immediately after changing display settings

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have just upgraded to Ubuntu 17.10 (and so switched from Unity to
Gnome 3).

I have a laptop and I sometimes use an external monitor with the laptop
closed (clamshell mode), and I sometimes use the laptop monitor with no
external monitor.

If I change my display settings, eg if I change from mirrored display
mode to extended desktop, or vice versa, it doesn't which direction I
change it, the point is that I change it, then after that change, I can
close my laptop lid, and the laptop will switch to just displaying on
the external monitor, ie, it will work in clamshell mode.

If I then unplug the external monitor, open the laptop and start using
it with its own monitor, and then later I plug the monitor back in (at
this time the monitor turns back on and displays according to whatever I
had the settings at), and then close the laptop lid again, the laptop
suspends, the external monitor turns off, ie clamshell mode doesn't
work.

The thing that seems to trigger to make clamshell mode work again is
that I have to change the display settings, from mirrored to extended
desktop or vice versa, doesn't matter which direction I change it in, as
long as I change it, that seems to tell the laptop that it's allowed to
go into clamshell mode when I close the lid.

So it seems that unplugging the monitor (or maybe plugging it in) resets
whatever prevents the laptop from suspending when the lid is closed, and
reconfiguring the display settings turns it back on.

I've Googled for solutions, most recommend configuring the laptop to not
suspend when the lid is closed, but that's not an acceptable solution -
I don't want the laptop to stay on when I unplug it and put it in my
bag.

Everything worked as expected with Ubuntu 17.04. The laptop suspended
when I expected it to (I'm actually not sure if suspending was caused by
unplugging the external monitor while the lid was closed, or unplugging
the power while the lid was closed, I expect the latter), while closing
the lid while an external monitor was connected didn't suspend (and
again, perhaps this was actually closing the lid when power was
connected that caused it to stay on, not sure).

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


** Tags: bot-comment
-- 
Clamshell mode only works immediately after changing display settings
https://bugs.launchpad.net/bugs/1730253
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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

[Desktop-packages] [Bug 1730467] [NEW] my laptop has freezed

[davesh singh]

Public bug reported:

Recently i have installed ubuntu 16.04 insted of windows8 . now after
installation when i work on system 10 to 15 min. auto matic my pc has
freezed and bottom of my pc has heated . tell me the what is the exect
problem and how to fix it

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
BootLog:
 [  OK  ] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
 [  OK  ] Started LSB: Speech Dispatcher.
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Nov  6 23:07:42 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1025:0905]
InstallationDate: Installed on 2017-11-04 (2 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b452 Chicony Electronics Co., Ltd 
 Bus 001 Device 005: ID 04ca:300b Lite-On Technology Corp. Atheros AR3012 
Bluetooth
 Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire E5-511
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=1e92417b-ea6a-4d89-9b74-b2a600d48848 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/16/2014
dmi.bios.vendor: Acer
dmi.bios.version: V1.03
dmi.board.name: Aspire E5-511
dmi.board.vendor: Acer
dmi.board.version: V1.03
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAcer:bvrV1.03:bd05/16/2014:svnAcer:pnAspireE5-511:pvrV1.03:rvnAcer:rnAspireE5-511:rvrV1.03:cvnAcer:ct10:cvrChassisVersion:
dmi.product.name: Aspire E5-511
dmi.product.version: V1.03
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Mon Nov  6 22:48:23 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
xserver.video_driver: modeset

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


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

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

Title:
  my laptop has freezed

Status in xorg package in Ubuntu:
  New

Bug description:
  Recently i have installed ubuntu 16.04 insted of windows8 . now after
  installation when i work on system 10 to 15 min. auto matic my pc has
  freezed and bottom of my pc has heated . tell me the what is the exect
  problem and how to fix it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
   [  OK  ] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
   [  OK  ] Started LSB: Speech Dispatcher.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Nov  6 23:07:42 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 

[Desktop-packages] [Bug 1730082] Re: 17.10 Shutdown Delayed 10 Min Due To Wifi

[Dimitri John Ledkov]

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

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

Title:
  17.10 Shutdown Delayed 10 Min Due To Wifi

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

Bug description:
  My Lenovo G50 laptop takes roughly 10 min to shut down, due to the
  wifi. After turning off the "automatically connect" option, shutdown
  occurs normally. I have found the following processes to have caused
  the delay:

  WPA supplicant
  Network manager
  Raise network interfaces

  I hope this can be resolved soon! Thankyou.

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

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

[Desktop-packages] [Bug 1730063] Re: [USB-Audio - Audioengine HD3, playback] fails after a while

[Arach Hirmanpour]

Issue seems to disappear when pulseaudio default sample rate is set to
48000 instead of 44100.

Speaker test with sample rate of 44100 produces no sound.

Don't know why as device is supposed to accept both sample rates.

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

Title:
  [USB-Audio - Audioengine HD3, playback] fails after a while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The speakers are connected to USB.

  "Digital Output (S/PDIF) - Audioengine HD3" appears in Sound settings.

  At first try, testing speakers (in sound settings) produced sound, but
  there was no sound in other applications (like Chromium or Rhythmbox).

  I had to add "install snd_hda_intel /bin/false" to /etc/modprobe.d
  /alsa-base.conf to get sound to work in other applications (presumably
  s/pdif was not directed to default sound card).

  But then, after a few minutes there is no sound any more (even speaker
  testing in settings does not produce any sound any more). Turning off
  the speakers and then back on doesn't help. Nor does disconnecting and
  reconnecting usb cord. So far, only rebooting restores sound for a
  while.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   arach  2475 F...m pulseaudio
   /dev/snd/controlC1:  arach  2475 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Sat Nov  4 11:17:43 2017
  InstallationDate: Installed on 2017-09-24 (40 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Audioengine HD3 - Audioengine HD3
  Symptom_Type: Sound works for a while, then breaks
  Title: [USB-Audio - Audioengine HD3, playback] fails after a while
  UpgradeStatus: Upgraded to artful on 2017-10-19 (15 days ago)
  dmi.bios.date: 10/17/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J61 v03.91
  dmi.board.asset.tag: CZC3195C9B
  dmi.board.name: 158A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 0.00
  dmi.chassis.asset.tag: CZC3195C9B
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ61v03.91:bd10/17/2016:svnHewlett-Packard:pnHPZ620Workstation:pvr:rvnHewlett-Packard:rn158A:rvr0.00:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53335X G=D
  dmi.product.name: HP Z620 Workstation
  dmi.sys.vendor: Hewlett-Packard
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-11-04T10:57:25.798374

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

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

[Desktop-packages] [Bug 711567] Re: Double window controls in Chromium after enabling "Use System Title Bar and Borders"

[Olivier Tilloy]

Closing because of lack of feedback from original reporter. I cannot
observe the issue on xenial with the latest chromium.

** Changed in: chromium-browser (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  Double window controls in Chromium after enabling "Use System Title
  Bar and Borders"

Status in Chromium Browser:
  Unknown
Status in Compiz:
  Invalid
Status in Compiz Core:
  Invalid
Status in chromium-browser package in Ubuntu:
  Invalid
Status in compiz package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: unity

  Steps to reproduce:
  1) Make sure "Use System Title Bar and Borders" is unticked (It is in the 
right click menu of the tab bar)
  2) Maximize Chromium
  3) Tick "Use System Title Bar and Borders"
  4) Untick "Use System Title Bar and Borders"
  5) Restore Chromium

  Result:
  At step 2 we see two sets of window controls, one drawn by Chromium and one 
in the top panel.
  After step 3 we see two sets of window controls, one in the top panel, one in 
Chromium's titlebar.
  When step 5 is executed we will find again that we have two sets of window 
controls, but this time one is drawn by Chromium and one by Unity.

  Expected result:
  At step 2: One set of window controls, the one drawn by Chromium.
  At step 3: One set of window controls; in the top panel (Unity).
  At step 5: One set of window controls, the one drawn by Chromium.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: unity 3.4.0-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
  Uname: Linux 2.6.38-1-generic x86_64
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell]
  Date: Tue Feb  1 18:52:53 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110127)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   LC_MESSAGES=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: unity

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

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

[Desktop-packages] [Bug 777283] Re: chromium icon in unity launcher not showing it's open

[Olivier Tilloy]

Given the age of the bug, I'll assume this is not relevant any longer.
Please file a new bug if you're facing similar issues.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  chromium icon in unity launcher not showing it's open

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: chromium-browser

  if you look at chromium icon in unity launcher, it doesn't show it has
  been opened (i mean the small white arrow on the left side of the
  icon)

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

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

[Desktop-packages] [Bug 1730253] Re: Clamshell mode only works immediately after changing display settings

[Brian Murray]

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

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

Title:
  Clamshell mode only works immediately after changing display settings

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have just upgraded to Ubuntu 17.10 (and so switched from Unity to
  Gnome 3).

  I have a laptop and I sometimes use an external monitor with the
  laptop closed (clamshell mode), and I sometimes use the laptop monitor
  with no external monitor.

  If I change my display settings, eg if I change from mirrored display
  mode to extended desktop, or vice versa, it doesn't which direction I
  change it, the point is that I change it, then after that change, I
  can close my laptop lid, and the laptop will switch to just displaying
  on the external monitor, ie, it will work in clamshell mode.

  If I then unplug the external monitor, open the laptop and start using
  it with its own monitor, and then later I plug the monitor back in (at
  this time the monitor turns back on and displays according to whatever
  I had the settings at), and then close the laptop lid again, the
  laptop suspends, the external monitor turns off, ie clamshell mode
  doesn't work.

  The thing that seems to trigger to make clamshell mode work again is
  that I have to change the display settings, from mirrored to extended
  desktop or vice versa, doesn't matter which direction I change it in,
  as long as I change it, that seems to tell the laptop that it's
  allowed to go into clamshell mode when I close the lid.

  So it seems that unplugging the monitor (or maybe plugging it in)
  resets whatever prevents the laptop from suspending when the lid is
  closed, and reconfiguring the display settings turns it back on.

  I've Googled for solutions, most recommend configuring the laptop to
  not suspend when the lid is closed, but that's not an acceptable
  solution - I don't want the laptop to stay on when I unplug it and put
  it in my bag.

  Everything worked as expected with Ubuntu 17.04. The laptop suspended
  when I expected it to (I'm actually not sure if suspending was caused
  by unplugging the external monitor while the lid was closed, or
  unplugging the power while the lid was closed, I expect the latter),
  while closing the lid while an external monitor was connected didn't
  suspend (and again, perhaps this was actually closing the lid when
  power was connected that caused it to stay on, not sure).

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

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

[Desktop-packages] [Bug 801926] Re: focusing a text input field in a web page doesn't open virtual keyboard

[Olivier Tilloy]

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

** This bug has been marked a duplicate of bug 1697641
   Chromium doesn't open OSK under GNOME Shell

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

Title:
  focusing a text input field in a web page doesn't open virtual
  keyboard

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Focusing a text input field on a web page does not cause the virtual
  keyboard (florence) to open. The url entry field in the main ui does,
  however.  This makes it difficult for tablet users to use chromium to
  interact with web sites.

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

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

[Desktop-packages] [Bug 839963] Re: "Blocked" tab doesn't work in "Cookies set by this page" window.

[Olivier Tilloy]

Cannot reproduce the issue, the "Blocked" tab works.
Given the age of the bug, I'll assume this is not relevant any longer.

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

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

Title:
  "Blocked" tab doesn't work in "Cookies set by this page" window.

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Chrome Version   : 13.0.782.218
  URLs (if applicable) : http://appdb.winehq.org/index.php

  What steps will reproduce the problem?
  1. Set the browser to reject cookies.
  2. Click the cookie blocked icon at the right end of the URL entry box.
  3. Select "Show cookies and other site data..."
  4. Try to click the "Blocked" tab.

  What is the expected result?
  Show the blocked tab.

  What happens instead?
  Nothing happens; the "Allowed" tab is still displayed.

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

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

[Desktop-packages] [Bug 1721833] Re: Can't type numbers in the evolution search box

[Joe Barnett]

I can confirm the same as @sleepingkyoto, that 789 work fine.

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

Title:
  Can't type numbers in the evolution search box

Status in evolution package in Ubuntu:
  Confirmed

Bug description:
  Trying to type numeric characters into the evolution search box is not
  working when using the numeric keys above the letters on the keyboard.
  Shift+numeric key for a special symbol works, and then numpad keys
  work, but the "regular" number keys don't appear to do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evolution 3.26.1-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct  6 10:35:25 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-08-21 (777 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04

[Thomas P.]

Bought the device some days ago. Had no chance to test earlier Ubuntu
releases.

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

Title:
  wifi driver: mt7601u not work on 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in usb-modeswitch-data package in Ubuntu:
  Confirmed

Bug description:
  In the beginning, when the adapter is pluged in, it's mounted as a disk 
including driver files for Windows, and
  $> lsusb
  Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp.

  after eject the disk,
  $> lsusb
  Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless 
Adapter

  I tried following 3 drivers:
  1) the default mt7601u included in the kernel: 4.4.0-91-generic
  after eject the disk,
  $> lsmod|grep mt
  mt7601u 102400 0
  mac80211 737280 1 mt7601u
  cfg80211 565248 2 mac80211,mt7601u
  binfmt_misc 20480 1
  $> modinfo mt7601u
  filename: 
/lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko
  srcversion: E8B632D369E0C2A9F1CF7D8
  alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in*
  ..
  depends: mac80211,cfg80211
  intree: Y
  vermagic: 4.4.0-91-generic SMP mod_unload modversions

  $> dmesg
  // begin
  [ 4581.094119] usb 3-4: USB disconnect, device number 6
  [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd
  [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4585.001416] usb 3-4: Product: Љ
  [ 4585.001418] usb 3-4: Manufacturer: Љ
  [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4585.001873] scsi host6: usb-storage 3-4:1.0
  [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0
  [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5
  [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4619.691737] ISOFS: changing to secondary root
  [ 4691.563347] usb 3-4: USB disconnect, device number 7
  [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd
  [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4693.766903] usb 3-4: Product: Љ
  [ 4693.766905] usb 3-4: Manufacturer: Љ
  [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4693.768063] scsi host7: usb-storage 3-4:1.0
  [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0
  [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5
  [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4728.427856] ISOFS: changing to secondary root
  [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00
  [ 4733.824218] usb 3-4: USB disconnect, device number 8
  [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 
00 00 00 00 00
  [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd
  [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601
  [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 4734.238757] usb 3-4: Product: 802.11 n WLAN
  [ 4734.238772] usb 3-4: Manufacturer: MediaTek
  [ 4734.238775] usb 3-4: SerialNumber: 1.0
  [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd
  [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500
  [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build 
time: 201302052146
  [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110
  [ 4742.131399] mt7601u 3-4:1.0: Vendor request req:02 off:09a8 failed:-110
  [ 4745.251254] mt7601u 3-4:1.0: Vendor request req:07 off:0734 failed:-110
  [ 4748.371056] mt7601u 3-4:1.0: Vendor request req:42 off:0230 failed:-110
  [ 4751.490880] mt7601u 3-4:1.0: Vendor request req:07 off:0080 failed:-110
  [ 4754.610694] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730501] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730548] mt7601u: probe of 3-4:1.0 failed with error -110
  [ 4757.730870] usbcore: registered new interface driver mt7601u
  // end 

  $> sudo ifconfig -a // do not list any new 

[Desktop-packages] [Bug 938751] Re: jpeg images are washed out or colors are skewed

[Henry]

Can conform, I have the exact same problem in all apps described in
previous reactions, with the inclusion of https://web.whatsapp.com/ ..
all my images look washed out greenish.

PLEASE UPGRADE THIS PRIORITY!

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

Title:
  jpeg images are washed out or colors are skewed

Status in Eye of GNOME:
  New
Status in eog package in Ubuntu:
  Confirmed
Status in eog source package in Precise:
  Confirmed

Bug description:
  Not all images are affected but enough are. Below is a screen shot of
  the issue with the image highlighted in nautilus to show that the
  color corruption seems to be eog rather than libjpeg.

  http://ubuntuone.com/1oFONmmTFXBzlHbM436Rwd

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: eog 3.3.90-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-17.26-generic-pae 3.2.6
  Uname: Linux 3.2.0-17-generic-pae i686
  ApportVersion: 1.92-0ubuntu1
  Architecture: i386
  CheckboxSubmission: ba9c4255a69726424c6447d1c48d6601
  CheckboxSystem: d00f84de8a555815fa1c4660280da308
  Date: Wed Feb 22 09:13:48 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 
(20120201.1)
  SourcePackage: eog
  UpgradeStatus: Upgraded to precise on 2012-02-21 (1 days ago)

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

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

[Desktop-packages] [Bug 1728778] Re: Touchpad not working after resuming from suspend

[Daniel van Vugt]

Pick the one that sounds like a touchpad :)

Can you copy and paste the list here?

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

Title:
  Touchpad not working after resuming from suspend

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

Bug description:
  I am using ubuntu 17.10 (intel i3, 16gb ram ). my mouse doesn't works
  once I have suspended the pc when i close the lid and reopens it

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

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

[Desktop-packages] [Bug 1730325] [NEW] Backup "Failed with an unknown error" with "No module named gi.repository"

[Mathias Bynke]

Public bug reported:

On a fresh install of Ubuntu 17.04, deja-dup consistently failed doing
backup, both over SSH, to an external hard drive and to the internal
drive. I tried initiating the backup both using the terminal and from
the GUI. The backup window would show up for a couple of seconds before
displaying «Failed with an unknown error».

Running deja-dup --backup with DEJA_DUP_DEBUG=1 gave me the following:

DUPLICITY: . Detaljer fra bakstykke-feilmelding: Traceback (most recent call 
last):
DUPLICITY: .   File "/usr/bin/duplicity", line 1532, in 
DUPLICITY: . with_tempdir(main)
DUPLICITY: .   File "/usr/bin/duplicity", line 1526, in with_tempdir
DUPLICITY: . fn()
DUPLICITY: .   File "/usr/bin/duplicity", line 1364, in main
DUPLICITY: . action = commandline.ProcessCommandLine(sys.argv[1:])
DUPLICITY: .   File 
"/usr/lib/python2.7/dist-packages/duplicity/commandline.py", line 1122, in 
ProcessCommandLine
DUPLICITY: . globals.backend = backend.get_backend(args[0])
DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", 
line 223, in get_backend
DUPLICITY: . obj = get_backend_object(url_string)
DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", 
line 211, in get_backend_object
DUPLICITY: . raise BackendException(_("Could not initialize backend: %s") % 
str(sys.exc_info()[1]))
DUPLICITY: . BackendException: Klarte ikke \xe5 starte bakstykke. No module 
named gi.repository

It turned out that installing the package python-gi solved the problem,
and the backup now runs as expected. It seems to me that this package
should have been a dependency of deja-dup.

I am running deja-dup 34.4-0ubuntu1 and duplicity 0.7.06-2ubuntu3.

** Affects: deja-dup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: gi.repository python-gi

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

Title:
  Backup "Failed with an unknown error" with "No module named
  gi.repository"

Status in deja-dup package in Ubuntu:
  New

Bug description:
  On a fresh install of Ubuntu 17.04, deja-dup consistently failed doing
  backup, both over SSH, to an external hard drive and to the internal
  drive. I tried initiating the backup both using the terminal and from
  the GUI. The backup window would show up for a couple of seconds
  before displaying «Failed with an unknown error».

  Running deja-dup --backup with DEJA_DUP_DEBUG=1 gave me the following:

  DUPLICITY: . Detaljer fra bakstykke-feilmelding: Traceback (most recent call 
last):
  DUPLICITY: .   File "/usr/bin/duplicity", line 1532, in 
  DUPLICITY: . with_tempdir(main)
  DUPLICITY: .   File "/usr/bin/duplicity", line 1526, in with_tempdir
  DUPLICITY: . fn()
  DUPLICITY: .   File "/usr/bin/duplicity", line 1364, in main
  DUPLICITY: . action = commandline.ProcessCommandLine(sys.argv[1:])
  DUPLICITY: .   File 
"/usr/lib/python2.7/dist-packages/duplicity/commandline.py", line 1122, in 
ProcessCommandLine
  DUPLICITY: . globals.backend = backend.get_backend(args[0])
  DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", 
line 223, in get_backend
  DUPLICITY: . obj = get_backend_object(url_string)
  DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", 
line 211, in get_backend_object
  DUPLICITY: . raise BackendException(_("Could not initialize backend: %s") 
% str(sys.exc_info()[1]))
  DUPLICITY: . BackendException: Klarte ikke \xe5 starte bakstykke. No module 
named gi.repository

  It turned out that installing the package python-gi solved the
  problem, and the backup now runs as expected. It seems to me that this
  package should have been a dependency of deja-dup.

  I am running deja-dup 34.4-0ubuntu1 and duplicity 0.7.06-2ubuntu3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1730325/+subscriptions

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

[Desktop-packages] [Bug 1728778] Re: Touchpad not working after resuming from suspend

[gavish]

it shows suspend. but I am not sure which option to choose(0-9) when I
give test command

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

Title:
  Touchpad not working after resuming from suspend

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

Bug description:
  I am using ubuntu 17.10 (intel i3, 16gb ram ). my mouse doesn't works
  once I have suspended the pc when i close the lid and reopens it

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

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

[Desktop-packages] [Bug 1730320] [NEW] package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' partilhado, que é diferente de o

[Teixeira]

Public bug reported:

o erro ocorre ao isstalar o winehq

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
Date: Mon Nov  6 05:40:21 2017
ErrorMessage: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' 
partilhado, que é diferente de outras instâncias do pacote libsane1:i386
InstallationDate: Installed on 2017-11-04 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
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
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to 
install/upgrade: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' 
partilhado, que é diferente de outras instâncias do pacote libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (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 sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1730320

Title:
  package libsane1 1.0.27-1~experimental2ubuntu1 failed to
  install/upgrade: a tentar sobreescrever
  '/lib/udev/hwdb.d/20-sane.hwdb' partilhado, que é diferente de outras
  instâncias do pacote libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  o erro ocorre ao isstalar o winehq

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Mon Nov  6 05:40:21 2017
  ErrorMessage: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' 
partilhado, que é diferente de outras instâncias do pacote libsane1:i386
  InstallationDate: Installed on 2017-11-04 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to 
install/upgrade: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' 
partilhado, que é diferente de outras instâncias do pacote libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time

[Daniel van Vugt]

Thanks Paul. The only slightly conclusive information I got from that so
far is:

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

So let's see how that one goes first. Looks like that's a secondary
issue though and not the biggest repeating issue.

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

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

Title:
  gnome-shell uses lots of memory, and grows over time

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

Bug description:
  gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
  almost 2 GiB.

  user  3039  1.8 16.1 4302340 1968476 tty2  Sl+  Mar09 120:17
  /usr/bin/gnome-shell

  strace output is voluminous; here is a representative sample:

  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\231\n\10\0\n\0 
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0 
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  open("/proc/self/stat", O_RDONLY)   = 36
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  fcntl(36, F_GETFL)  = 0x8000 (flags O_RDONLY|O_LARGEFILE)
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
  read(36, "", 3072)  = 0
  close(36)   = 0
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 117885) = 
1 ([{fd=4, revents=POLLIN}])
  read(4, "\1\0\0\0\0\0\0\0", 16) = 8
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, {msg_name(0)=NULL, 
msg_iov(1)=[{"[\2\327\0@\0i\0@\0(nu\22\n\0I\0\336\2\232\1\265\0038\2\362\2\355\1",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 

[Desktop-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04

[Kai-Heng Feng]

Forgot to ask an important question, did the device work on on earlier
Ubuntu Release, e.g. Precise & Trusty?

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

Title:
  wifi driver: mt7601u not work on 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in usb-modeswitch-data package in Ubuntu:
  Confirmed

Bug description:
  In the beginning, when the adapter is pluged in, it's mounted as a disk 
including driver files for Windows, and
  $> lsusb
  Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp.

  after eject the disk,
  $> lsusb
  Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless 
Adapter

  I tried following 3 drivers:
  1) the default mt7601u included in the kernel: 4.4.0-91-generic
  after eject the disk,
  $> lsmod|grep mt
  mt7601u 102400 0
  mac80211 737280 1 mt7601u
  cfg80211 565248 2 mac80211,mt7601u
  binfmt_misc 20480 1
  $> modinfo mt7601u
  filename: 
/lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko
  srcversion: E8B632D369E0C2A9F1CF7D8
  alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in*
  ..
  depends: mac80211,cfg80211
  intree: Y
  vermagic: 4.4.0-91-generic SMP mod_unload modversions

  $> dmesg
  // begin
  [ 4581.094119] usb 3-4: USB disconnect, device number 6
  [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd
  [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4585.001416] usb 3-4: Product: Љ
  [ 4585.001418] usb 3-4: Manufacturer: Љ
  [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4585.001873] scsi host6: usb-storage 3-4:1.0
  [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0
  [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5
  [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4619.691737] ISOFS: changing to secondary root
  [ 4691.563347] usb 3-4: USB disconnect, device number 7
  [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd
  [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4693.766903] usb 3-4: Product: Љ
  [ 4693.766905] usb 3-4: Manufacturer: Љ
  [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4693.768063] scsi host7: usb-storage 3-4:1.0
  [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0
  [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5
  [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4728.427856] ISOFS: changing to secondary root
  [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00
  [ 4733.824218] usb 3-4: USB disconnect, device number 8
  [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 
00 00 00 00 00
  [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd
  [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601
  [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 4734.238757] usb 3-4: Product: 802.11 n WLAN
  [ 4734.238772] usb 3-4: Manufacturer: MediaTek
  [ 4734.238775] usb 3-4: SerialNumber: 1.0
  [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd
  [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500
  [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build 
time: 201302052146
  [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110
  [ 4742.131399] mt7601u 3-4:1.0: Vendor request req:02 off:09a8 failed:-110
  [ 4745.251254] mt7601u 3-4:1.0: Vendor request req:07 off:0734 failed:-110
  [ 4748.371056] mt7601u 3-4:1.0: Vendor request req:42 off:0230 failed:-110
  [ 4751.490880] mt7601u 3-4:1.0: Vendor request req:07 off:0080 failed:-110
  [ 4754.610694] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730501] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730548] mt7601u: probe of 3-4:1.0 failed with error -110
  [ 4757.730870] usbcore: registered new interface driver mt7601u
  // end 

  $> sudo ifconfig -a 

[Desktop-packages] [Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time

[Daniel van Vugt]

P.S. To start gnome-shell manually, this seems to do the trick:

 1. Log into a virtual terminal.
 2. gnome-shell --display-server --wayland --mode=ubuntu

So you can modify that command as required.

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

Title:
  gnome-shell uses lots of memory, and grows over time

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

Bug description:
  gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
  almost 2 GiB.

  user  3039  1.8 16.1 4302340 1968476 tty2  Sl+  Mar09 120:17
  /usr/bin/gnome-shell

  strace output is voluminous; here is a representative sample:

  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\231\n\10\0\n\0 
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0 
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  open("/proc/self/stat", O_RDONLY)   = 36
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  fcntl(36, F_GETFL)  = 0x8000 (flags O_RDONLY|O_LARGEFILE)
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
  read(36, "", 3072)  = 0
  close(36)   = 0
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 117885) = 
1 ([{fd=4, revents=POLLIN}])
  read(4, "\1\0\0\0\0\0\0\0", 16) = 8
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, {msg_name(0)=NULL, 
msg_iov(1)=[{"[\2\327\0@\0i\0@\0(nu\22\n\0I\0\336\2\232\1\265\0038\2\362\2\355\1",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, 

[Desktop-packages] [Bug 1730343] [NEW] firmware update breaks Ubuntu

[Merlijn Sebrechts]

Public bug reported:

Two users have reported that fwupd breaks their Ubuntu installation
because the "Ubuntu" EFI boot option disappears after an update.

It might be best to consider turning off firmware updates until this
issue is fixed.


Upstream issue: https://github.com/juju-solutions/charms.reactive/issues/139

** Affects: fwupd
 Importance: Unknown
 Status: Unknown

** Affects: ubiquity
 Importance: Undecided
 Status: New

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

** Bug watch added: github.com/juju-solutions/charms.reactive/issues #139
   https://github.com/juju-solutions/charms.reactive/issues/139

** Also affects: gnome-software via
   https://github.com/juju-solutions/charms.reactive/issues/139
   Importance: Unknown
   Status: Unknown

** Project changed: gnome-software => fwupd

** Also affects: ubiquity
   Importance: Undecided
   Status: New

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

Title:
  firmware update breaks Ubuntu

Status in Fwupd:
  Unknown
Status in ubiquity:
  New
Status in gnome-software package in Ubuntu:
  New

Bug description:
  Two users have reported that fwupd breaks their Ubuntu installation
  because the "Ubuntu" EFI boot option disappears after an update.

  It might be best to consider turning off firmware updates until this
  issue is fixed.

  
  Upstream issue: https://github.com/juju-solutions/charms.reactive/issues/139

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

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

[Desktop-packages] [Bug 1730488] [NEW] Filters don't work when folder name contains space character

[Markus1978]

Public bug reported:

I have set up several folders on an imap account to organize my mail and
wrote some filter rules, mainly to move incoming mail to those folders.

When filters are run that point to a folder whose name contains spaces,
i get an error message complaining about an invalid folder address,
quoting the offending address roughly like this
"some_number_path/to/folder/firstword%20secondword"

I tried to rename folders to eliminate the space character shown as %20.
That solved the problem for me and filters run.


If spaces are allowed in the IMAP standard, evolution should be able to handle 
them. 
If not, it should provide a meaningful message to the user suggesting to rename 
the offending folder(s).

Thanks to the team,

Markus

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: evolution 3.26.1-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov  6 20:29:08 2017
InstallationDate: Installed on 2017-10-21 (15 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: evolution
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  Filters don't work when folder name contains space character

Status in evolution package in Ubuntu:
  New

Bug description:
  I have set up several folders on an imap account to organize my mail
  and wrote some filter rules, mainly to move incoming mail to those
  folders.

  When filters are run that point to a folder whose name contains
  spaces, i get an error message complaining about an invalid folder
  address, quoting the offending address roughly like this
  "some_number_path/to/folder/firstword%20secondword"

  I tried to rename folders to eliminate the space character shown as
  %20. That solved the problem for me and filters run.

  
  If spaces are allowed in the IMAP standard, evolution should be able to 
handle them. 
  If not, it should provide a meaningful message to the user suggesting to 
rename the offending folder(s).

  Thanks to the team,

  Markus

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evolution 3.26.1-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 20:29:08 2017
  InstallationDate: Installed on 2017-10-21 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1582986] Re: NetworkManager service does not start during bootup

[Norbert]

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

Got this bug again other Ubuntu 16.04.3 LTS system:

$ journalctl | grep -i network
ноя 06 22:49:57 norbert-vaio kernel: FUJITSU Extended Socket Network Device 
Driver - version 1.0 - Copyright (c) 2015 FUJITSU LIMITED
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Found ordering cycle 
on network.target/start
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Found dependency on 
NetworkManager.service/start
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Found dependency on 
basic.target/start
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Found dependency on 
sockets.target/start
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Found dependency on 
uuidd.socket/start
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Found dependency on 
sysinit.target/start
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Found dependency on 
console-cyrillic.service/start
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Found dependency on 
remote-fs.target/start
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Found dependency on 
remote-fs-pre.target/start
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Found dependency on 
nfs-server.service/start
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Found dependency on 
network.target/start
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Breaking ordering 
cycle by deleting job NetworkManager.service/start
ноя 06 22:49:57 norbert-vaio systemd[1]: NetworkManager.service: Job 
NetworkManager.service/start deleted to break ordering cycle starting with 
network.target/start


$ journalctl | grep -i break
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Breaking ordering 
cycle by deleting job NetworkManager.service/start
ноя 06 22:49:57 norbert-vaio systemd[1]: NetworkManager.service: Job 
NetworkManager.service/start deleted to break ordering cycle starting with 
network.target/start
ноя 06 22:49:57 norbert-vaio systemd[1]: nfs-server.service: Breaking ordering 
cycle by deleting job rpcbind.socket/start
ноя 06 22:49:57 norbert-vaio systemd[1]: rpcbind.socket: Job 
rpcbind.socket/start deleted to break ordering cycle starting with 
nfs-server.service/start

I'm trying to remove nfs-kernel-server. But it is still critical bug.

** Also affects: nfs-utils (Ubuntu)
   Importance: Undecided
   Status: New

** This bug has been marked a duplicate of bug 1487679
   Breaking ordering cycle by deleting job nbd-client.service/start

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

Title:
  NetworkManager service does not start during bootup

Status in network-manager package in Ubuntu:
  Confirmed
Status in nfs-utils package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 4.4.0-22
  systemd 229-4
  network-manager 1.1.93
  network-manager-gnome 1.2.0

  Multiple services and targets are deleted by systemd to "break
  ordering cycle" (cf. boot.log), but NetworkManager is the only one of
  them (network.target,rpcbind,sysinit.target,open-iscsi.service,remote-
  fs-pre.target,iscsid.service,zfs-fuse.service - cf. their respective
  logs) which is not started after bootup:

  sudo systemctl status NetworkManager.service
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: inactive (dead)

  May 18 05:00:10 samsung-ubuntu systemd[1]: NetworkManager.service: Job
  NetworkManager.service/verify-active deleted to break ordering cycle
  starting with network.target/start

  Attachments:
  ---
  - journalctl -l -b0 --system _COMM=systemd > boot.log
  - systemctl -l status rpcbind  > rpcbind.log
  - systemctl -l status network.target  > network.target.txt
  - systemctl -l status remote-fs-pre.target  > remote-fs-pre.target.log
  - systemctl -l status sysinit.target  > sysinit.target.log
  - systemctl -l status zfs-fuse.service  > zfs-fuse.service.log
  - systemctl -l status open-iscsi.service  > open-iscsi.service.log
  - systemctl -l status iscsid.service  > iscsid.service.log

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

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

[Desktop-packages] [Bug 1729441] Re: changing display mode after login terminates session

[Penna Panna]

ubuntu-bug and (sudo) apport-cli exits immediately after I click send
and thereafter it doesn't show me anything. (It just creates
.upload{,ed} files.)

I have no recent entries.

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

Title:
  changing display mode after login terminates session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When I login, I type the password on the laptop screen. (Maybe it's
  important.) After a while, while I'm waiting to get logged in, Ubuntu
  changes the display mode. Both monitor goes black, laptop screen
  becomes the secondary and my external monitor becomes the primary
  display. Because of Ubuntu is unable to remember to the previously set
  display mode, I usually change it a bit after I have logged in.
  However, if I (would like to) do this too quickly, say... less than
  4-5 seconds after I can see my desktop, my session gets terminated and
  I'm returned to the login screen. You can repeat it indefinitely, it
  always worked for me.

  I thought it's because of one of my extensions but I could reproduce it after 
I have disabled them.
  I haven't found any useful log entries.

  
  UPDATE 1:
  While I was writing this, I thought it has something to do with theme loading 
or something like this, so I continued to test with startup applications.
  I just rarely managed to reproduce this bug when I didn't execute the 
following script (as a file) at login:
  ```
  #!/bin/bash
  sleep 1s; firefox &
  sleep 1s; thunderbird &
  ```

  I also noticed that after I have some faulty logins and then I login
  without changing display mode, I >sometimes< have no desktop, no
  startup applications and when I click power off/logout buttons nothing
  happens, but that's sure I will being logged out randomly in the near
  future - even if I don't touch my computer (I'm talking about
  minutes).

  Plus, I can see the desktop and the top bar (so it's the primary
  screen) with two wide black bars on the two sides of my laptop monitor
  for a moment before I get logged out. (However, I don't see any
  resolution changes so I guess it's not 640x480, or 800x600, etc.)

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: vtsspp sep4_1 socperf2_0 pax
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Nov  1 21:00:45 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-08 (85 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-21 (10 days ago)

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

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

[Desktop-packages] [Bug 1487679] Re: Breaking ordering cycle by deleting job nbd-client.service/start

[Launchpad Bug Tracker]

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

** Changed in: util-linux (Ubuntu)
   Status: New => Confirmed

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

Title:
  CRITICAL BUG: Breaking ordering cycle by deleting job
  NetworkManager.service/start

Status in systemd:
  Unknown
Status in avahi package in Ubuntu:
  Confirmed
Status in nbd package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Won't Fix
Status in nfs-utils package in Ubuntu:
  Confirmed
Status in open-iscsi package in Ubuntu:
  New
Status in rpcbind package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:

  $ lsb_release -rd
  Description:  Ubuntu 15.04
  Release:  15.04

  $ apt-cache policy nbd-client
  nbd-client:
    Installed: 1:3.8-4ubuntu0.1
    Candidate: 1:3.8-4ubuntu0.1
    Version table:
   *** 1:3.8-4ubuntu0.1 0
  500 http://ch.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.8-4 0
  500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages

  I'm using the nbd-client to mount some raw disk images over the
  network but starting the nbd-client automatically during bootup does
  not happen due to the following:

  Aug 22 08:54:20 fractal kernel: [   11.875885] systemd[1]: Found dependency 
on nbd-client.service/start
  Aug 22 08:54:20 fractal kernel: [   11.875890] systemd[1]: Breaking ordering 
cycle by deleting job nbd-client.service/start
  Aug 22 08:54:20 fractal kernel: [   11.875891] systemd[1]: Job 
nbd-client.service/start deleted to break ordering cycle starting with 
basic.target/start

  Meaning after boot, I have to manually run `sudo ndb-client start`
  every time I want to access these images. Note that this is no
  diskless system, the images I mount via NBD do not contain the local
  system, they are totally unrelated.

  
  -
  Bug with NFS-server and RPC-bind is indicated by messages:

  $ journalctl | grep -i break
  ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Breaking ordering 
cycle by deleting job NetworkManager.service/start
  ноя 06 22:49:57 norbert-vaio systemd[1]: NetworkManager.service: Job 
NetworkManager.service/start deleted to break ordering cycle starting with 
network.target/start
  ноя 06 22:49:57 norbert-vaio systemd[1]: nfs-server.service: Breaking 
ordering cycle by deleting job rpcbind.socket/start
  ноя 06 22:49:57 norbert-vaio systemd[1]: rpcbind.socket: Job 
rpcbind.socket/start deleted to break ordering cycle starting with 
nfs-server.service/start

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

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

[Desktop-packages] [Bug 1573206] Re: GNOME Software does not install third-party .deb packages

[sul aga]

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

This issue affects me.
Ubuntu 16.04.3 LTS
4.10.0-38-generic

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

Title:
  GNOME Software does not install third-party .deb packages

Status in gdebi:
  New
Status in GNOME Software:
  New
Status in GRadio:
  New
Status in SoundConverter:
  New
Status in Ubuntu GNOME:
  Triaged
Status in Ubuntu Studio:
  Triaged
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 16.04 LTS (clean install). 64-bit. Final release.
  Gnome-software version: 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2
    Version table:
   *** 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 500
  500 http://no.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  I intended to install MEGA Sync Client, Google Chrome and Dropbox by
  downloading the needed packages from their websites (respectively
  https://mega.nz/#sync and https://www.google.com/chrome/ and
  https://www.dropbox.com/install?os=lnx ). I opened the packages one by
  one with gnome-software and pressed Install - nothing, except for a
  super-quick progress bar animation, happened. No matter how many times
  I tried, same result. Also, an icon pops up on the panel saying
  "Waiting to install", but nothing seems to happen.

  This only seems to happen with third-party packages; installing a
  random deb from packages.ubuntu.com/xenial worked.

  I even tried to reinstall the system to make this work, but same
  problem.

  Gdebi, however, installs the packages as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 21 21:01:52 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2016-04-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=nn_NO:nn:no_NO:no:nb_NO:nb:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nn_NO.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1487679] Re: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start

[Bug Watch Updater]

Launchpad has imported 4 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=908123.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-02-05T23:47:21+00:00 John wrote:

Description of problem:
With NFS mounts in an fstab it appears that NetworkManager and the 
autogenerated mount units get into a dependency loop which causes a number of 
important units to get discarded while trying to resolve the issue.

Version-Release number of selected component (if applicable):
Seen in FC16,17,18

How reproducible:
Every boot with NFS mounts in the fstab

Steps to Reproduce:
1. Try and boot a system with NFS mounts in the fstab.
2.
3.
  
Actual results:
Several units are deleted and never attempt to stop, several others fail 
because the root filesystem doesn't get remounted RW until other units time out.

Expected results:
System should come up, remount the root filesystem RW, mount NFS volumes in the 
fstab without dependency loops or units timing out.


Additional info:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/1487679/comments/0


On 2013-02-06T04:42:24+00:00 John wrote:

[6.943559] systemd[1]: Found ordering cycle on 
NetworkManager-wait-online.service/start
[6.943707] systemd[1]: Walked on cycle path to NetworkManager.service/start
[6.943810] systemd[1]: Walked on cycle path to dbus.socket/start
[6.943912] systemd[1]: Walked on cycle path to sysinit.target/start
[6.944039] systemd[1]: Walked on cycle path to local-fs.target/start
[6.944141] systemd[1]: Walked on cycle path to 
var-storage-fuse-mp3.mount/start
[6.944287] systemd[1]: Walked on cycle path to var-storage.mount/start
[6.944388] systemd[1]: Walked on cycle path to remote-fs-pre.target/start
[6.944490] systemd[1]: Walked on cycle path to network.target/start
[6.944588] systemd[1]: Walked on cycle path to 
NetworkManager-wait-online.service/start
[6.944735] systemd[1]: Breaking ordering cycle by deleting job 
NetworkManager.service/start
[6.944883] systemd[1]: Job NetworkManager.service/start deleted to break 
ordering cycle starting with NetworkManager-wait-online.service/start
[6.945103] systemd[1]: Deleting job 
NetworkManager-wait-online.service/start as dependency of job 
NetworkManager.service/verify-active

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/1487679/comments/1


On 2013-08-04T20:44:30+00:00 Raman wrote:

Same problem here during reboot on Fedora 19:

Aug  4 16:18:43 edison systemd[1]: Found ordering cycle on local-fs.target/stop
Aug  4 16:18:43 edison systemd[1]: Walked on cycle path to nfs-darwin.mount/stop
Aug  4 16:18:43 edison systemd[1]: Walked on cycle path to network.target/stop
Aug  4 16:18:43 edison systemd[1]: Walked on cycle path to 
NetworkManager.service/stop
Aug  4 16:18:43 edison systemd[1]: Walked on cycle path to dbus.socket/stop
Aug  4 16:18:43 edison systemd[1]: Walked on cycle path to sysinit.target/stop
Aug  4 16:18:43 edison systemd[1]: Walked on cycle path to local-fs.target/stop
Aug  4 16:18:43 edison systemd[1]: Breaking ordering cycle by deleting job 
nfs-darwin.mount/stop
Aug  4 16:18:43 edison systemd[1]: Job nfs-darwin.mount/stop deleted to break 
ordering cycle starting with local-fs.target/stop
Aug  4 16:18:43 edison systemd[1]: Found ordering cycle on local-fs.target/stop
Aug  4 16:18:43 edison systemd[1]: Walked on cycle path to 
nfs-darwin-home.mount/stop

/etc/fstab contains:

darwin:/ /nfs/darwin nfs4rw,soft,intr,noauto  0 0

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/1487679/comments/2


On 2013-12-09T01:47:35+00:00 Zbigniew wrote:

This should be fixed by the latest f18 systemd update.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/1487679/comments/3


** Changed in: systemd
   Status: Unknown => Fix Released

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

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

Title:
  CRITICAL BUG: Breaking ordering cycle by deleting job
  NetworkManager.service/start

Status in systemd:
  Fix Released
Status in avahi package in Ubuntu:
  Confirmed
Status in nbd package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Won't Fix
Status in nfs-utils package in Ubuntu:
  Confirmed
Status in open-iscsi package in Ubuntu:
  New
Status in rpcbind package in Ubuntu:
  New
Status in systemd package in 

[Desktop-packages] [Bug 1730241] Re: Evolution segfaults when NVidia driver is installed but not used

[Michael Scott]

** Also affects: evolution
   Importance: Undecided
   Status: New

** No longer affects: evolution

** Also affects: clutter-gtk (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Evolution segfaults when NVidia driver is installed but not used

Status in clutter-gtk package in Ubuntu:
  New
Status in cogl package in Ubuntu:
  New
Status in evolution package in Ubuntu:
  New

Bug description:
  To use CUDA I have installed the NVidia driver but disabled the card
  in the BIOS and set the main output to the onboard GPU.  I also edited
  the xorg.conf accordingly.  Now I can no longer start evolution.  It
  crashes with a segfault.  I cannot reproduce the segfault with other
  clutter apps.

  Attached is a backtrace of the crash, my xorg.conf, and the Xorg log.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clutter-gtk/+bug/1730241/+subscriptions

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

[Desktop-packages] [Bug 1487679] Re: Breaking ordering cycle by deleting job nbd-client.service/start

[Norbert]

** Also affects: nfs-utils (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  CRITICAL BUG: Breaking ordering cycle by deleting job
  NetworkManager.service/start

Status in systemd:
  Unknown
Status in avahi package in Ubuntu:
  Confirmed
Status in nbd package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Won't Fix
Status in nfs-utils package in Ubuntu:
  Confirmed
Status in open-iscsi package in Ubuntu:
  New
Status in rpcbind package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

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

  $ apt-cache policy nbd-client
  nbd-client:
Installed: 1:3.8-4ubuntu0.1
Candidate: 1:3.8-4ubuntu0.1
Version table:
   *** 1:3.8-4ubuntu0.1 0
  500 http://ch.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.8-4 0
  500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages

  I'm using the nbd-client to mount some raw disk images over the
  network but starting the nbd-client automatically during bootup does
  not happen due to the following:

  Aug 22 08:54:20 fractal kernel: [   11.875885] systemd[1]: Found dependency 
on nbd-client.service/start
  Aug 22 08:54:20 fractal kernel: [   11.875890] systemd[1]: Breaking ordering 
cycle by deleting job nbd-client.service/start
  Aug 22 08:54:20 fractal kernel: [   11.875891] systemd[1]: Job 
nbd-client.service/start deleted to break ordering cycle starting with 
basic.target/start

  Meaning after boot, I have to manually run `sudo ndb-client start`
  every time I want to access these images. Note that this is no
  diskless system, the images I mount via NBD do not contain the local
  system, they are totally unrelated.

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

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

[Desktop-packages] [Bug 1487679] Re: Breaking ordering cycle by deleting job nbd-client.service/start

[Launchpad Bug Tracker]

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

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

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

Title:
  CRITICAL BUG: Breaking ordering cycle by deleting job
  NetworkManager.service/start

Status in systemd:
  Unknown
Status in avahi package in Ubuntu:
  Confirmed
Status in nbd package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Won't Fix
Status in nfs-utils package in Ubuntu:
  Confirmed
Status in open-iscsi package in Ubuntu:
  New
Status in rpcbind package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

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

  $ apt-cache policy nbd-client
  nbd-client:
Installed: 1:3.8-4ubuntu0.1
Candidate: 1:3.8-4ubuntu0.1
Version table:
   *** 1:3.8-4ubuntu0.1 0
  500 http://ch.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.8-4 0
  500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages

  I'm using the nbd-client to mount some raw disk images over the
  network but starting the nbd-client automatically during bootup does
  not happen due to the following:

  Aug 22 08:54:20 fractal kernel: [   11.875885] systemd[1]: Found dependency 
on nbd-client.service/start
  Aug 22 08:54:20 fractal kernel: [   11.875890] systemd[1]: Breaking ordering 
cycle by deleting job nbd-client.service/start
  Aug 22 08:54:20 fractal kernel: [   11.875891] systemd[1]: Job 
nbd-client.service/start deleted to break ordering cycle starting with 
basic.target/start

  Meaning after boot, I have to manually run `sudo ndb-client start`
  every time I want to access these images. Note that this is no
  diskless system, the images I mount via NBD do not contain the local
  system, they are totally unrelated.

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

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

[Desktop-packages] [Bug 1487679] Re: Breaking ordering cycle by deleting job nbd-client.service/start

[Launchpad Bug Tracker]

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

** Changed in: nfs-utils (Ubuntu)
   Status: New => Confirmed

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

Title:
  CRITICAL BUG: Breaking ordering cycle by deleting job
  NetworkManager.service/start

Status in systemd:
  Unknown
Status in avahi package in Ubuntu:
  Confirmed
Status in nbd package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Won't Fix
Status in nfs-utils package in Ubuntu:
  Confirmed
Status in open-iscsi package in Ubuntu:
  New
Status in rpcbind package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

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

  $ apt-cache policy nbd-client
  nbd-client:
Installed: 1:3.8-4ubuntu0.1
Candidate: 1:3.8-4ubuntu0.1
Version table:
   *** 1:3.8-4ubuntu0.1 0
  500 http://ch.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.8-4 0
  500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages

  I'm using the nbd-client to mount some raw disk images over the
  network but starting the nbd-client automatically during bootup does
  not happen due to the following:

  Aug 22 08:54:20 fractal kernel: [   11.875885] systemd[1]: Found dependency 
on nbd-client.service/start
  Aug 22 08:54:20 fractal kernel: [   11.875890] systemd[1]: Breaking ordering 
cycle by deleting job nbd-client.service/start
  Aug 22 08:54:20 fractal kernel: [   11.875891] systemd[1]: Job 
nbd-client.service/start deleted to break ordering cycle starting with 
basic.target/start

  Meaning after boot, I have to manually run `sudo ndb-client start`
  every time I want to access these images. Note that this is no
  diskless system, the images I mount via NBD do not contain the local
  system, they are totally unrelated.

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

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

[Desktop-packages] [Bug 1487679] Re: Breaking ordering cycle by deleting job nbd-client.service/start

[Norbert]

Got this bug again other Ubuntu 16.04.3 LTS system:

$ journalctl | grep -i network
ноя 06 22:49:57 norbert-vaio kernel: FUJITSU Extended Socket Network Device 
Driver - version 1.0 - Copyright (c) 2015 FUJITSU LIMITED
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Found ordering cycle 
on network.target/start
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Found dependency on 
NetworkManager.service/start
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Found dependency on 
basic.target/start
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Found dependency on 
sockets.target/start
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Found dependency on 
uuidd.socket/start
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Found dependency on 
sysinit.target/start
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Found dependency on 
console-cyrillic.service/start
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Found dependency on 
remote-fs.target/start
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Found dependency on 
remote-fs-pre.target/start
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Found dependency on 
nfs-server.service/start
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Found dependency on 
network.target/start
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Breaking ordering 
cycle by deleting job NetworkManager.service/start
ноя 06 22:49:57 norbert-vaio systemd[1]: NetworkManager.service: Job 
NetworkManager.service/start deleted to break ordering cycle starting with 
network.target/start

$ journalctl | grep -i break
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Breaking ordering 
cycle by deleting job NetworkManager.service/start
ноя 06 22:49:57 norbert-vaio systemd[1]: NetworkManager.service: Job 
NetworkManager.service/start deleted to break ordering cycle starting with 
network.target/start
ноя 06 22:49:57 norbert-vaio systemd[1]: nfs-server.service: Breaking ordering 
cycle by deleting job rpcbind.socket/start
ноя 06 22:49:57 norbert-vaio systemd[1]: rpcbind.socket: Job 
rpcbind.socket/start deleted to break ordering cycle starting with 
nfs-server.service/start

I'm trying to remove nfs-kernel-server. But it is still critical bug.


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

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

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

** Also affects: systemd via
   https://bugzilla.redhat.com/show_bug.cgi?id=908123
   Importance: Unknown
   Status: Unknown

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

Title:
  CRITICAL BUG: Breaking ordering cycle by deleting job
  NetworkManager.service/start

Status in systemd:
  Unknown
Status in avahi package in Ubuntu:
  Confirmed
Status in nbd package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Won't Fix
Status in nfs-utils package in Ubuntu:
  Confirmed
Status in open-iscsi package in Ubuntu:
  New
Status in rpcbind package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:

  $ lsb_release -rd
  Description:  Ubuntu 15.04
  Release:  15.04

  $ apt-cache policy nbd-client
  nbd-client:
    Installed: 1:3.8-4ubuntu0.1
    Candidate: 1:3.8-4ubuntu0.1
    Version table:
   *** 1:3.8-4ubuntu0.1 0
  500 http://ch.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.8-4 0
  500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages

  I'm using the nbd-client to mount some raw disk images over the
  network but starting the nbd-client automatically during bootup does
  not happen due to the following:

  Aug 22 08:54:20 fractal kernel: [   11.875885] systemd[1]: Found dependency 
on nbd-client.service/start
  Aug 22 08:54:20 fractal kernel: [   11.875890] systemd[1]: Breaking ordering 
cycle by deleting job nbd-client.service/start
  Aug 22 08:54:20 fractal kernel: [   11.875891] systemd[1]: Job 
nbd-client.service/start deleted to break ordering cycle starting with 
basic.target/start

  Meaning after boot, I have to manually run `sudo ndb-client start`
  every time I want to access these images. Note that this is no
  diskless system, the images I mount via NBD do not contain the local
  system, they are totally unrelated.

  
  -
  Bug with NFS-server and RPC-bind is indicated by messages:

  $ journalctl | grep -i break
  ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Breaking ordering 

[Desktop-packages] [Bug 1487679] Re: Breaking ordering cycle by deleting job nbd-client.service/start

[Launchpad Bug Tracker]

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

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

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

Title:
  CRITICAL BUG: Breaking ordering cycle by deleting job
  NetworkManager.service/start

Status in systemd:
  Unknown
Status in avahi package in Ubuntu:
  Confirmed
Status in nbd package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Won't Fix
Status in nfs-utils package in Ubuntu:
  Confirmed
Status in open-iscsi package in Ubuntu:
  New
Status in rpcbind package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:

  $ lsb_release -rd
  Description:  Ubuntu 15.04
  Release:  15.04

  $ apt-cache policy nbd-client
  nbd-client:
    Installed: 1:3.8-4ubuntu0.1
    Candidate: 1:3.8-4ubuntu0.1
    Version table:
   *** 1:3.8-4ubuntu0.1 0
  500 http://ch.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.8-4 0
  500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages

  I'm using the nbd-client to mount some raw disk images over the
  network but starting the nbd-client automatically during bootup does
  not happen due to the following:

  Aug 22 08:54:20 fractal kernel: [   11.875885] systemd[1]: Found dependency 
on nbd-client.service/start
  Aug 22 08:54:20 fractal kernel: [   11.875890] systemd[1]: Breaking ordering 
cycle by deleting job nbd-client.service/start
  Aug 22 08:54:20 fractal kernel: [   11.875891] systemd[1]: Job 
nbd-client.service/start deleted to break ordering cycle starting with 
basic.target/start

  Meaning after boot, I have to manually run `sudo ndb-client start`
  every time I want to access these images. Note that this is no
  diskless system, the images I mount via NBD do not contain the local
  system, they are totally unrelated.

  
  -
  Bug with NFS-server and RPC-bind is indicated by messages:

  $ journalctl | grep -i break
  ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Breaking ordering 
cycle by deleting job NetworkManager.service/start
  ноя 06 22:49:57 norbert-vaio systemd[1]: NetworkManager.service: Job 
NetworkManager.service/start deleted to break ordering cycle starting with 
network.target/start
  ноя 06 22:49:57 norbert-vaio systemd[1]: nfs-server.service: Breaking 
ordering cycle by deleting job rpcbind.socket/start
  ноя 06 22:49:57 norbert-vaio systemd[1]: rpcbind.socket: Job 
rpcbind.socket/start deleted to break ordering cycle starting with 
nfs-server.service/start

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

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

[Desktop-packages] [Bug 1730091] Re: session freezes/hangs after undetermined amount of time

[Nathanel Titane]

Here it is. Copied from /var/crash/ - original name _usr_bin_gnome-
shell.1000.crash

** Attachment added: "gnome-shell crash log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730091/+attachment/5004940/+files/gnome-shell-crash.crash

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

Title:
  session freezes/hangs after undetermined amount of time

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Currently using the default wayland session on 17.10: the computer
  eventually hangs/freezes after an undetermined amount of time, whether
  it'S still powered on and unused or when put on standby. Resuming the
  session is impossible as the device is frozen and needs to bee reset
  with power button.

  Critical bug as the issues has provoked major data loss and work in
  progress loss.

  Possibly a functional regression due to the use of wayland or the
  newer kernel provided with this release.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  4 12:29:03 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-20 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1487679] Re: Breaking ordering cycle by deleting job nbd-client.service/start

[Norbert]

** Also affects: open-iscsi (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Breaking ordering cycle by deleting job nbd-client.service/start
+ metabug: Breaking ordering cycle by deleting job NetworkManager.service/start

** Summary changed:

- metabug: Breaking ordering cycle by deleting job NetworkManager.service/start
+ CRITICAL BUG: Breaking ordering cycle by deleting job 
NetworkManager.service/start

** Tags added: xenial

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

** Description changed:

+ 
  $ lsb_release -rd
  Description:  Ubuntu 15.04
  Release:  15.04
  
  $ apt-cache policy nbd-client
  nbd-client:
-   Installed: 1:3.8-4ubuntu0.1
-   Candidate: 1:3.8-4ubuntu0.1
-   Version table:
-  *** 1:3.8-4ubuntu0.1 0
- 500 http://ch.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 
Packages
- 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  1:3.8-4 0
- 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
+   Installed: 1:3.8-4ubuntu0.1
+   Candidate: 1:3.8-4ubuntu0.1
+   Version table:
+  *** 1:3.8-4ubuntu0.1 0
+ 500 http://ch.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 
Packages
+ 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  1:3.8-4 0
+ 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  
  I'm using the nbd-client to mount some raw disk images over the network
  but starting the nbd-client automatically during bootup does not happen
  due to the following:
  
  Aug 22 08:54:20 fractal kernel: [   11.875885] systemd[1]: Found dependency 
on nbd-client.service/start
  Aug 22 08:54:20 fractal kernel: [   11.875890] systemd[1]: Breaking ordering 
cycle by deleting job nbd-client.service/start
  Aug 22 08:54:20 fractal kernel: [   11.875891] systemd[1]: Job 
nbd-client.service/start deleted to break ordering cycle starting with 
basic.target/start
  
  Meaning after boot, I have to manually run `sudo ndb-client start` every
  time I want to access these images. Note that this is no diskless
  system, the images I mount via NBD do not contain the local system, they
  are totally unrelated.
+ 
+ 
+ -
+ Bug with NFS-server and RPC-bind is indicated by messages:
+ 
+ $ journalctl | grep -i break
+ ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Breaking ordering 
cycle by deleting job NetworkManager.service/start
+ ноя 06 22:49:57 norbert-vaio systemd[1]: NetworkManager.service: Job 
NetworkManager.service/start deleted to break ordering cycle starting with 
network.target/start
+ ноя 06 22:49:57 norbert-vaio systemd[1]: nfs-server.service: Breaking 
ordering cycle by deleting job rpcbind.socket/start
+ ноя 06 22:49:57 norbert-vaio systemd[1]: rpcbind.socket: Job 
rpcbind.socket/start deleted to break ordering cycle starting with 
nfs-server.service/start

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

Title:
  CRITICAL BUG: Breaking ordering cycle by deleting job
  NetworkManager.service/start

Status in systemd:
  Unknown
Status in avahi package in Ubuntu:
  Confirmed
Status in nbd package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Won't Fix
Status in nfs-utils package in Ubuntu:
  Confirmed
Status in open-iscsi package in Ubuntu:
  New
Status in rpcbind package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:

  $ lsb_release -rd
  Description:  Ubuntu 15.04
  Release:  15.04

  $ apt-cache policy nbd-client
  nbd-client:
    Installed: 1:3.8-4ubuntu0.1
    Candidate: 1:3.8-4ubuntu0.1
    Version table:
   *** 1:3.8-4ubuntu0.1 0
  500 http://ch.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.8-4 0
  500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages

  I'm using the nbd-client to mount some raw disk images over the
  network but starting the nbd-client automatically during bootup does
  not happen due to the following:

  Aug 22 08:54:20 fractal kernel: [   11.875885] systemd[1]: Found dependency 
on nbd-client.service/start
  Aug 22 08:54:20 fractal kernel: [   11.875890] systemd[1]: Breaking ordering 
cycle by deleting job nbd-client.service/start
  Aug 22 08:54:20 fractal kernel: [   11.875891] systemd[1]: Job 
nbd-client.service/start deleted to break ordering cycle starting with 
basic.target/start

  Meaning after boot, I have to manually run `sudo ndb-client start`
  every time I want to access these images. 

[Desktop-packages] [Bug 1728810] Re: CUPS ERRORS

[Till Kamppeter]

How did you report this bug? Did you simply start in your web browser?
Or did you use some application on your desktop? Which application?

I am asking as your bug report did get auto-assigned to xorg, which has
nothing to do with the printing infrastructure. Especially also the
automatically added info is about xorg and not about printing and
therefore not helpful.

Can you please follow the instructions on
https://wiki.ubuntu.com/DebuggingPrintingProblems to get a more useful
bug report?

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

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

Title:
  CUPS ERRORS

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  There are problems in my PC about the "Server".-When I am traying to
  use my printer (wireless printer).-An advice apairs as: "failed to
  connect to server".

  I would have your help,thank You in advance.Sincerely Fernando
  Espinosa.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
   [  OK  ] Started Network Manager.
Starting Network Manager Wait Online...
   [  OK  ] Reached target Network.
   [  OK  ] Started Unattended Upgrades Shutdown.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Oct 31 00:32:15 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7310] [1002:9809] 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Wrestler [Radeon HD 7310] [17aa:365d]
  InstallationDate: Installed on 2016-11-27 (337 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 10103
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic 
root=UUID=e9b7906b-8c2c-4887-89be-701551b926e7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EKKT30BUS
  dmi.board.name: Remore CRB
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD EM DPK IPG
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrEKKT30BUS:bd03/05/2013:svnLENOVO:pn10103:pvrLenovoC345:rvnLENOVO:rnRemoreCRB:rvrWin8STDEMDPKIPG:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
  dmi.product.name: 10103
  dmi.product.version: Lenovo C345
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Oct 30 16:40:55 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1730420] Re: Window size when LibreOffice starts

[J-Paul BERARD]

LibreOffice window with menu only

** Attachment added: "Capture menu seul.png"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1730420/+attachment/5004681/+files/Capture%20menu%20seul.png

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

Title:
  Window size when LibreOffice starts

Status in libreoffice package in Ubuntu:
  New

Bug description:
  With Artful 17.10 Wayland, any app of LibreOffice opens with a small window. 
Previously, it opened with a "common size" or the size you used previously (see 
attachment)
  If it was opened with a full screen window the previous time, it opens in 
full-screen mode. If you check the "windows size" button, you may get a more 
smaller window with only the menu of LibreOffice.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-calc 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 16:11:00 2017
  InstallationDate: Installed on 2016-04-30 (554 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-10-23 (14 days ago)

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

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

[Desktop-packages] [Bug 1730420] [NEW] Window size when LibreOffice starts

[J-Paul BERARD]

Public bug reported:

With Artful 17.10 Wayland, any app of LibreOffice opens with a small window. 
Previously, it opened with a "common size" or the size you used previously (see 
attachment)
If it was opened with a full screen window the previous time, it opens in 
full-screen mode. If you check the "windows size" button, you may get a more 
smaller window with only the menu of LibreOffice.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libreoffice-calc 1:5.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov  6 16:11:00 2017
InstallationDate: Installed on 2016-04-30 (554 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: Upgraded to artful on 2017-10-23 (14 days ago)

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


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

** Attachment added: "screen"
   
https://bugs.launchpad.net/bugs/1730420/+attachment/5004676/+files/Capture%20calc.png

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

Title:
  Window size when LibreOffice starts

Status in libreoffice package in Ubuntu:
  New

Bug description:
  With Artful 17.10 Wayland, any app of LibreOffice opens with a small window. 
Previously, it opened with a "common size" or the size you used previously (see 
attachment)
  If it was opened with a full screen window the previous time, it opens in 
full-screen mode. If you check the "windows size" button, you may get a more 
smaller window with only the menu of LibreOffice.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-calc 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 16:11:00 2017
  InstallationDate: Installed on 2016-04-30 (554 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-10-23 (14 days ago)

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

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

[Desktop-packages] [Bug 1722044] Re: package chromium-browser 61.0.3163.100-0ubuntu0.16.04.1306 failed to install/upgrade: nelze zkopírovat rozbalená data „./usr/lib/chromium-browser/icudtl.dat“ do „/

[Olivier Tilloy]

This looks like a download error. Please try the following command in a
terminal:

sudo apt-get clean
sudo apt update
sudo apt install --reinstall chromium-browser

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

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

Title:
  package chromium-browser 61.0.3163.100-0ubuntu0.16.04.1306 failed to
  install/upgrade: nelze zkopírovat rozbalená data „./usr/lib/chromium-
  browser/icudtl.dat“ do „/usr/lib/chromium-browser/icudtl.dat.dpkg-
  new“: neočekávaný konec souboru nebo proudu

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  It happened when I was trying to install chromium with sudo aptitude
  install chromium-browser-i10n chromium-browser

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 61.0.3163.100-0ubuntu0.16.04.1306
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   chromium-browser: Install
   chromium-browser-l10n: Install
   chromium-browser: Configure
   chromium-browser-l10n: Configure
   NULL: ConfigurePending
  Architecture: amd64
  DRM.card0-DVI-D-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAebWtW1rQAAAcRAQPqMSB46q7FoldKnCUSUFSna4CVAIGAgUBxTwEBAQEBAQEBfC6QoGAaHkAwIDYA2igRAAAaITmQMGIaJ0BosDYA2igRAAAc/QA4SxxTDwAKICAgICAg/ABMMjI2VyAKICAgICAgAM8=
   modes: 1680x1050 1680x1050 1280x1024 1280x1024 1440x900 1280x960 1152x864 
1024x768 1024x768 832x624 800x600 800x600 800x600 640x480 640x480 720x400
  DRM.card0-TV-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-VGA-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Sun Oct  8 10:48:11 2017
  Desktop-Session:
   'None'
   'None'
   'None'
  Env:
   'None'
   'None'
  ErrorMessage: nelze zkopírovat rozbalená data 
„./usr/lib/chromium-browser/icudtl.dat“ do 
„/usr/lib/chromium-browser/icudtl.dat.dpkg-new“: neočekávaný konec souboru nebo 
proudu
  InstallationDate: Installed on 2017-10-08 (0 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Load-Avg-1min: 1.22
  Load-Processes-Running-Percent:   0.5%
  Lsusb:
   Bus 001 Device 003: ID 0424:2228 Standard Microsystems Corp. 9-in-2 Card 
Reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=eb9444ff-a658-42eb-ad86-fe6743d699fa ro quiet splash vt.handoff=7
  SourcePackage: chromium-browser
  Title: package chromium-browser 61.0.3163.100-0ubuntu0.16.04.1306 failed to 
install/upgrade: nelze zkopírovat rozbalená data 
„./usr/lib/chromium-browser/icudtl.dat“ do 
„/usr/lib/chromium-browser/icudtl.dat.dpkg-new“: neočekávaný konec souboru nebo 
proudu
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/02/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2N8L ACPI BIOS Revision 0301
  dmi.board.name: M2N8L
  dmi.board.vendor: ASUSTek Computer INC.
  dmi.board.version: 1.xx
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N8LACPIBIOSRevision0301:bd11/02/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTekComputerINC.:rnM2N8L:rvr1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1719200] Re: package chromium-browser 61.0.3163.79-0ubuntu0.16.04.1300 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before a

[Olivier Tilloy]

Please try the following command in a terminal, and paste the output
here:

sudo apt-get install --reinstall chromium-browser

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

Title:
  package chromium-browser 61.0.3163.79-0ubuntu0.16.04.1300 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  i am not sure

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 61.0.3163.79-0ubuntu0.16.04.1300
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   chromium-codecs-ffmpeg-extra: Install
   chromium-codecs-ffmpeg-extra: Configure
   chromium-browser: Configure
   chromium-browser-l10n: Configure
   NULL: ConfigurePending
  Architecture: amd64
  DRM.card0-DVI-I-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAJ0QV5RVQAABASAQMOKRp4LuW1o1VJmScTUFSla4BxAIEAlQCVD4GAgUABAQEBmimg0FGEIDBQmDYAmgARAAAc/wBINDgwNDk5MzAyNgog/QA3TB9TDwAKICAgICAg/ABCZW5RIEU5MDBXCiAgAJ4=
   modes: 1440x900 1280x1024 1280x1024 1440x900 1280x960 1280x800 1152x864 
1152x720 1024x768 1024x768 832x624 800x600 800x600 640x480 640x480 720x400
  Date: Sun Sep 24 21:54:56 2017
  Desktop-Session:
   'None'
   'None'
   'None'
  DuplicateSignature:
   package:chromium-browser:61.0.3163.79-0ubuntu0.16.04.1300
   Setting up chromium-codecs-ffmpeg-extra (61.0.3163.79-0ubuntu0.16.04.1300) 
...
   dpkg: error processing package chromium-browser (--configure):
package is in a very bad inconsistent state; you should
  Env:
   'None'
   'None'
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-09-13 (11 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Load-Avg-1min: 0.99
  Load-Processes-Running-Percent:   0.3%
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=74485bcf-c032-443d-b00d-9ceb759fd9f5 ro quiet splash vt.handoff=7
  SourcePackage: chromium-browser
  Title: package chromium-browser 61.0.3163.79-0ubuntu0.16.04.1300 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0802
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX3 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd10/08/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX3R2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1706948] Re: [Ubuntu 1710] [Feature] Inconsistent report of pm CanSuspend state by systemd and pm-utils

[Manoj Iyer]

** Changed in: pm-utils (Ubuntu)
Milestone: ubuntu-17.10 => ubuntu-18.04

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

Title:
  [Ubuntu 1710] [Feature] Inconsistent report of pm CanSuspend state by
  systemd and pm-utils

Status in The Ubuntu-power-systems project:
  Incomplete
Status in pm-utils package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - Balamuruhan S <> - 2017-06-28 03:39:15 ==
  systemd and pm-utils interprets CanSuspend states differently and reports it 
as supported or not in a conflicting way.

  # gdbus call --system --dest org.freedesktop.login1 --object-path 
/org/freedesktop/login1 --method org.freedesktop.login1.Manager.CanSuspend
  ('yes',)

  # pm-is-supported --suspend
  # echo $?
  1

  Both systemd and pm-is-supported looks into /sys/power/state file to
  check if suspend is supported.

  pm-is-supported --suspend returns true if either "standby" or "mem" is 
present in the file.
  ( /usr/lib/pm-utils/pm-functions )

  systemd(Manager.CanSuspend) returns true if "standby", "freeze" or "mem" is 
present in the file.
  ( 
https://github.com/systemd/systemd/blob/dd8352659c9428b196706d04399eec106a8917ed/src/shared/sleep-config.c
 )

  # cat /sys/power/state
  freeze

  So here, pm-is-supported --suspend returns false and gdbus returns
  true.

  Both these utilities interpret /sys/power/state differently.

  Secondly, systemd should split CanSuspend to Cansuspend+CanFreeze Or
  don't report freeze as CanSuspend.

  Impact of this inconsistency can be felt from Libvirt supported pm
  states:

  To reduce ABI dependency, libvirt queries the available states via
  dbus, if not falls to pm-utils. Libvirt won't check for strings in
  sys/power/state and interpret directly.

  so due to this, libvirt will list that suspend_to_mem is supported
  from virsh capabilities but ideally it might not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1706948/+subscriptions

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

[Desktop-packages] [Bug 1528915] Re: Allow changing of the top panel's colour and transparency levels without need to install extension - feature request

[Nikita Yerenkov-Scott]

@Dave, Yes, I know, that's the one I'm referring to in my bug
description (in fact it's quite obvious from the title of the bug). I
meant that I was requesting for this functionality to be built-in rather
than having to install the extension. Anyway, this bug is almost 2
-years-old, and I'm on Arch now so you Ubuntu can do what you want with
it. But it should be noted that there has been a little upstream
activity on the bug so maybe this will get implemented in at least a
similar way to the way I requested.

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

Title:
  Allow changing of the top panel's colour and transparency levels
  without need to install extension - feature request

Status in gnome-control-center:
  Won't Fix
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Currently if one wants to change the colour or transparency levels of
  the top panel they have to install an extension, I think that this
  functionality should be built-in so that one can just change these
  settings in the gnome-control-center rather than having to install
  some third-party extension.

  I am running Ubuntu GNOME 15.10 with GNOME 3.18.

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

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

[Desktop-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones

[JM]

The solution by @robertjjoynt worked for me on 2017 ASUS ZenBook 3
(ux490ua) with Debian 9 with Kernel 4.9.0-4.

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

Title:
  Crackling and popping sound when using headphones

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New

Bug description:
  Laptop is  HP Pavilion - 15-au118tx. The laptop has B and O play and
  the output from speakers are just fine, when using headphones there is
  some kind of crackling and popping sound in both ears but prominently
  in the left ear.

  The issue happens only when the sound is played, if i reduce the PCM
  way low using alsamixer, the effect is minimized but the volume is
  also reduced. Increasing the volume in the panel increases the PCM as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antony 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  7 23:30:05 2016
  InstallationDate: Installed on 2016-11-20 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689

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

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

[Desktop-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

[Daniel van Vugt]

Thanks. I learned something new.

Yes, as you discovered I would only expect VLC hardware decoding to work
in a "Ubuntu on Xorg" session with the VLC option "VA-API video decoder
via X11". Because that's the only combination of session and VLC option
that's even theoretically compatible at all. Although performance in
this mode is still relatively poor compared to MPV or even Totem. So I'd
recommend those first.

Using "VA-API video decoder via DRM" I would not expect to work under
Wayland. And it doesn't.

It sounds like someone needs to log an enhancement/bug with VLC upstream
to add a new option "VA-API video decoder via Wayland". Because that's
the missing option (where the possible options are
https://github.com/01org/libva/blob/master/va/va_backend.h#L39 ).

** No longer affects: vlc (Ubuntu)

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

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Confirmed
Status in Totem:
  Confirmed
Status in VLC media player:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Won't Fix
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

[Daniel van Vugt]

Andrea, it appears bug 1716800 already covers the problem to some
extent. I suggest you subscribe there instead.

This bug is already conflated by different issues in different players.

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

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Confirmed
Status in Totem:
  Confirmed
Status in VLC media player:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Won't Fix
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1730343] Re: firmware update breaks Ubuntu

[Merlijn Sebrechts]

** Bug watch added: github.com/rhboot/fwupdate/issues #86
   https://github.com/rhboot/fwupdate/issues/86

** Changed in: fwupd
   Status: New => Unknown

** Changed in: fwupd
 Remote watch: github.com/juju-solutions/charms.reactive/issues #139 => 
github.com/rhboot/fwupdate/issues #86

** Description changed:

  Two users have reported that fwupd breaks their Ubuntu installation
  because the "Ubuntu" EFI boot option disappears after an update.
  
  It might be best to consider turning off firmware updates until this
  issue is fixed.
  
- 
- Upstream issue: https://github.com/juju-solutions/charms.reactive/issues/139
+ Upstream issue: https://github.com/rhboot/fwupdate/issues/86

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

Title:
  firmware update breaks Ubuntu

Status in Fwupd:
  Unknown
Status in ubiquity:
  New
Status in gnome-software package in Ubuntu:
  New

Bug description:
  Two users have reported that fwupd breaks their Ubuntu installation
  because the "Ubuntu" EFI boot option disappears after an update.

  It might be best to consider turning off firmware updates until this
  issue is fixed.

  Upstream issue: https://github.com/rhboot/fwupdate/issues/86

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

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

[Desktop-packages] [Bug 1615734] Re: Multiple monitors broken

[fabio.hipolito]

Same problems with nvidia-384.90 on both ubuntu-gnome 17.04 and 17.10.
The workarounds for 17.04 still minimize part of the issues on 17.10.

** Changed in: nvidia-graphics-drivers-384 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Multiple monitors broken

Status in nvidia-graphics-drivers-361 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo P50 with Nvidia Optimus (Quadro M1000M), installed with 
Ubuntu 16.04 and the recommended Nvidia drivers (361.42). 
  I added two external monitors connected to DP sockets in the docking station. 
I would like to have display shift to those two monitors when the laptop is 
docked. One monitor has native resolution of 1680x1050 and the other is 
1920x1080. The laptop native resolution is 1920x1080.

  Expected result: 
  laptop monitor shut off, two external monitors running in native resolution, 
display shared on both monitors (not mirrored).

  Process:
  I configured the display using the "Displays" applet in the unity control 
center. However, pressing "Apply" when changing a specific display setting 
(such as resolution, location of screen relative to others, turning on/off), 
results in a long period of darkness, usually followed by display falling back 
to mirroring of all 3 monitors, using a similar-size screen (either low on all 
or high on all with the low-res monitor using panning). The applet remains 
frozen for some time, with the dialog "Is the display ok" open but 
unresponsive. Later I realized this is because there is another dialog of 
"Cannot set screen CRTCXXX" hidden under the two above windows, which needs to 
by ok-ed first.

  Extra:
  I also tried setting the display manually with 'xrandr', which lead to a 
similar result as above - with the "cannot set screen" dialog, and falling back 
to mirroring. This convinced me that the problem is probably with the nvidia 
driver and not the higher plumbing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: symap_custom_dkms_x86_64 nvidia_uvm nvidia_modeset 
nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug 22 19:14:55 2016
  InstallationDate: Installed on 2016-07-17 (36 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1615734/+subscriptions

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

[Desktop-packages] [Bug 1728778] Re: Touchpad not working after resuming from suspend

[Jonathan Elchison]

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

** This bug has been marked a duplicate of bug 1718654
   Touchpad input doesn't work after longer suspend.

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

Title:
  Touchpad not working after resuming from suspend

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

Bug description:
  I am using ubuntu 17.10 (intel i3, 16gb ram ). my mouse doesn't works
  once I have suspended the pc when i close the lid and reopens it

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

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

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

[Jeremy Bicha]

Staedtler, despite the scary version number, libsane 1.0.27 itself is
not experimental. As you pointed out, Arch has been using 1.0.27 since
May.

https://www.archlinux.org/packages/extra/i686/sane/

I am a bit surprised at the number of people reporting an issue here
that is claimed to be new.

Ubuntu 12.04 LTS (and the newer LTS's) also uses the same multiarch
directory ( /usr/lib/x86_64-linux-gnu/sane/ for typical 64-bit
computers) !

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

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

Status in sane-backends package in Ubuntu:
  Confirmed

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

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

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

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

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

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

[Desktop-packages] [Bug 1609009] Re: gnome-terminal should allow the disabling of text wrapping (so that there is a scroll bar at the bottom instead)

[Nikita Yerenkov-Scott]

@Marius, This could still be done as a downstream patch and they haven't
rejected that yet so there's no reason to close it as just "Opinion", in
fact it would make more sense for them to close this as "Won't fix"
because really "Opinion" refers to something completely different.

I must admit that after looking at the description given for this option
it does look like it's at least very close, but I've always been told
that this is not what the option is for when others use it on my bugs.

** Changed in: ubuntu-gnome
   Status: Opinion => Confirmed

** Changed in: gnome-terminal (Ubuntu)
   Status: Opinion => Confirmed

** Changed in: vte2.91 (Ubuntu)
   Status: Opinion => Confirmed

** Changed in: ubuntu-gnome
   Status: Confirmed => New

** Changed in: gnome-terminal (Ubuntu)
   Status: Confirmed => New

** Changed in: vte2.91 (Ubuntu)
   Status: Confirmed => New

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

Title:
  gnome-terminal should allow the disabling of text wrapping (so that
  there is a scroll bar at the bottom instead)

Status in Ubuntu GNOME:
  New
Status in Gnome Virtual Terminal Emulator:
  Won't Fix
Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  New

Bug description:
  I would find it rather useful, especially with certain types of
  outputs, if gnome-terminal would allow me to disable text wrapping,
  that is so that there would be a horizontal scroll bar that would
  allow me to see the rest of the text.

  I don't know if this should/would include the commands you type it,
  but maybe there could be a separate option for the wrapping of that.

  There are other Terminals which support this, and I think it would be
  really nice if gnome-terminal would too so that one doesn't have to
  put all of the output into another program like 'less' or similar in
  order to disable the wrapping.

  I am running Ubuntu GNOME 16.04 with GNOME 3.20 and would find this a
  very useful feature.

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

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

[Desktop-packages] [Bug 1631663] [NEW] wnck-applet crashed with signal 5 in _XReply()

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

wnck-applet crashed with signal 5 in _XReply()

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: mate-panel 1.16.0-1
ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
Uname: Linux 4.8.0-21-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: MATE
Date: Sun Oct  9 00:16:18 2016
ExecutablePath: /usr/lib/mate-panel/wnck-applet
InstallationDate: Installed on 2016-10-08 (0 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20161007)
ProcCmdline: /usr/lib/mate-panel/wnck-applet
Signal: 5
SourcePackage: mate-panel
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XGetSelectionOwner () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libwnck-3.so.0
Title: wnck-applet crashed with signal 5 in _XReply()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: libwnck3 (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash yakkety
-- 
wnck-applet crashed with signal 5 in _XReply()
https://bugs.launchpad.net/bugs/1631663
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to libwnck3 in Ubuntu.

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

[Desktop-packages] [Bug 1728778] Re: Touchpad not working after resuming from suspend

[gavish]

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

No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:  Lid Switch
/dev/input/event1:  Power Button
/dev/input/event2:  Sleep Button
/dev/input/event3:  Power Button
/dev/input/event4:  AT Translated Set 2 keyboard
/dev/input/event5:  Video Bus
/dev/input/event6:  Synaptics TM3108-002
/dev/input/event7:  DELL Wireless hotkeys
/dev/input/event8:  Integrated_Webcam_HD: Integrate
/dev/input/event9:  Dell WMI hotkeys
/dev/input/event10: HDA Intel HDMI HDMI/DP,pcm=3
/dev/input/event11: HDA Intel HDMI HDMI/DP,pcm=7
/dev/input/event12: HDA Intel HDMI HDMI/DP,pcm=8
/dev/input/event13: HDA Intel HDMI HDMI/DP,pcm=9
/dev/input/event14: HDA Intel HDMI HDMI/DP,pcm=10
/dev/input/event15: HDA Intel PCH Headphone Mic

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

Title:
  Touchpad not working after resuming from suspend

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

Bug description:
  I am using ubuntu 17.10 (intel i3, 16gb ram ). my mouse doesn't works
  once I have suspended the pc when i close the lid and reopens it

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

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

[Desktop-packages] [Bug 1730378] [NEW] "Save email as template" menu option has disappeared

[Patryk "LeadMan" Benderz]

Public bug reported:

1)
Description:Ubuntu 17.10
Release:17.10

2)
evolution:
  Zainstalowana: 3.26.1-1
  Kandydująca:   3.26.1-1
  Tabela wersji:
 *** 3.26.1-1 500
500 http://pl.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
100 /var/lib/dpkg/status

In recent Evolution distributed with Ubuntu, the "Save email as template" menu 
option has disappeared.
It was there before.

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

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

Title:
  "Save email as template" menu option has disappeared

Status in evolution package in Ubuntu:
  New

Bug description:
  1)
  Description:  Ubuntu 17.10
  Release:  17.10

  2)
  evolution:
Zainstalowana: 3.26.1-1
Kandydująca:   3.26.1-1
Tabela wersji:
   *** 3.26.1-1 500
  500 http://pl.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  In recent Evolution distributed with Ubuntu, the "Save email as template" 
menu option has disappeared.
  It was there before.

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

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

[Desktop-packages] [Bug 1092559] Re: package chromium-browser 22.0.1229.94~r161065-0ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/chromium-browser/theme_resources_100_pe

[Olivier Tilloy]

This looks like a download error. Given the age of the bug let's assume
this is not relevant any longer. If you run into a similar situation
again, please run:

sudo apt-get clean
sudo apt update

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

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

Title:
  package chromium-browser 22.0.1229.94~r161065-0ubuntu1 failed to
  install/upgrade: cannot copy extracted data for './usr/lib/chromium-
  browser/theme_resources_100_percent.pak' to '/usr/lib/chromium-
  browser/theme_resources_100_percent.pak.dpkg-new': final inesperado
  del archivo o flujo

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  adfsdfasdf

  ProblemType: Package
  DistroRelease: Ubuntu 12.10
  Package: chromium-browser 22.0.1229.94~r161065-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
  Uname: Linux 3.5.0-21-generic i686
  ApportVersion: 2.6.1-0ubuntu9
  AptOrdering:
   chromium-browser: Install
   chromium-codecs-ffmpeg: Configure
   chromium-browser: Configure
   chromium-browser-l10n: Configure
  Architecture: i386
  ChromiumPrefs: can't open profile /root/.config/chromium/Default/Preferences
  Date: Tue Dec 18 02:04:59 2012
  Desktop-Session:
   DESKTOP_SESSION = None
   XDG_CONFIG_DIRS = None
   XDG_DATA_DIRS = None
  DiskUsage:
   b'S.ficheros Tipo Tama\xc3\xb1o Usado  Disp Uso% Montado 
en\n/dev/sdc5  ext419G   15G  2,8G  85% /\nudev   devtmpfs  
 1,3G  4,0K  1,3G   1% /dev\ntmpfs  tmpfs  505M  836K  504M   1% 
/run\nnone   tmpfs  5,0M 0  5,0M   0% /run/lock\nnone   
tmpfs  1,3G  152K  1,3G   1% /run/shm\nnone   tmpfs  100M   32K 
 100M   1% /run/user\n/dev/sda1  fuseblk 75G   69G  6,5G  92% 
/media/jimetory/A4905D05905CDF7C\n'
   
   Inodes:
   b'S.ficheros Nodos-i NUsados NLibres NUso% Montado en\n/dev/sdc5 
1,2M447K725K   39% /\nudev  211K 574210K1% 
/dev\ntmpfs 214K 482214K1% /run\nnone  214K 
  3214K1% /run/lock\nnone  214K   6214K1% 
/run/shm\nnone  214K  21214K1% /run/user\n/dev/sda1 
6,5M 38K6,5M1% /media/jimetory/A4905D05905CDF7C\n'
  DpkgTerminalLog:
   Desempaquetando chromium-browser (de 
.../chromium-browser_22.0.1229.94~r161065-0ubuntu1_i386.deb) ...
   dpkg-deb (subproceso): decompressing archive member: error lzma: los datos 
comprimidos están dañados
   dpkg-deb: error: el subproceso  devolvió el código de salida 
de error 2
   dpkg: error al procesar 
/var/cache/apt/archives/chromium-browser_22.0.1229.94~r161065-0ubuntu1_i386.deb 
(--unpack):
cannot copy extracted data for 
'./usr/lib/chromium-browser/theme_resources_100_percent.pak' to 
'/usr/lib/chromium-browser/theme_resources_100_percent.pak.dpkg-new': final 
inesperado del archivo o flujo
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/chromium-browser/theme_resources_100_percent.pak' to 
'/usr/lib/chromium-browser/theme_resources_100_percent.pak.dpkg-new': final 
inesperado del archivo o flujo
  InstallationDate: Installed on 2012-10-24 (56 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MarkForUpload: True
  SourcePackage: chromium-browser
  Title: package chromium-browser 22.0.1229.94~r161065-0ubuntu1 failed to 
install/upgrade: cannot copy extracted data for 
'./usr/lib/chromium-browser/theme_resources_100_percent.pak' to 
'/usr/lib/chromium-browser/theme_resources_100_percent.pak.dpkg-new': final 
inesperado del archivo o flujo
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b''/desktop/gnome/url-handlers/https/command = 
b''/desktop/gnome/url-handlers/https/enabled = 
b''/desktop/gnome/url-handlers/http/command = 
b''/desktop/gnome/url-handlers/http/enabled = 
b''/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n'

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

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

[Desktop-packages] [Bug 1730343] Re: firmware update breaks Ubuntu

[Bug Watch Updater]

** Changed in: fwupd
   Status: Unknown => New

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

Title:
  firmware update breaks Ubuntu

Status in Fwupd:
  New
Status in ubiquity:
  New
Status in gnome-software package in Ubuntu:
  New

Bug description:
  Two users have reported that fwupd breaks their Ubuntu installation
  because the "Ubuntu" EFI boot option disappears after an update.

  It might be best to consider turning off firmware updates until this
  issue is fixed.

  
  Upstream issue: https://github.com/juju-solutions/charms.reactive/issues/139

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

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

[Desktop-packages] [Bug 1730343] Re: firmware update breaks Ubuntu

[Bug Watch Updater]

** Changed in: fwupd
   Status: Unknown => New

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

Title:
  firmware update breaks Ubuntu

Status in Fwupd:
  New
Status in ubiquity:
  New
Status in gnome-software package in Ubuntu:
  New

Bug description:
  Two users have reported that fwupd breaks their Ubuntu installation
  because the "Ubuntu" EFI boot option disappears after an update.

  It might be best to consider turning off firmware updates until this
  issue is fixed.

  Upstream issue: https://github.com/rhboot/fwupdate/issues/86

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

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

[Desktop-packages] [Bug 1730365] [NEW] pulseaudio keeps crashing and the audiom drops out

[Grizzly(Francis Smit)]

Public bug reported:

1). 21:48:17 ⌂197% grizzlysmit@killashandra:~ 4m23s $ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
21:54:30 ⌂217% grizzlysmit@killashandra:~ 2s $ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.10
Release:17.10
Codename:   artful

2).  $ apt-cache policy pulseaudio
pulseaudio:
  Installed: 1:10.0-2ubuntu3
  Candidate: 1:10.0-2ubuntu3
  Version table:
 *** 1:10.0-2ubuntu3 500
500 http://au.archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status

3). I expected pulse to just keep running like it always did under
previous releases of Ubuntu

4). It keeps dropping out after a day or so no sound and settings
(gnome-control-center sound) to it cannot connect to it running
pulseaudio& in a shell fixes it

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov  6 21:44:08 2017
InstallationDate: Installed on 2017-07-24 (104 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to artful on 2017-10-20 (16 days ago)
dmi.bios.date: 08/06/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A18
dmi.board.name: 0G261D
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd08/06/2013:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0G261D:rvrA00:cvnDellInc.:ct15:cvr:
dmi.product.name: OptiPlex 960
dmi.sys.vendor: Dell Inc.

** Affects: pulseaudio (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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1730365

Title:
  pulseaudio keeps crashing and the audiom drops out

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  1). 21:48:17 ⌂197% grizzlysmit@killashandra:~ 4m23s $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  21:54:30 ⌂217% grizzlysmit@killashandra:~ 2s $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.10
  Release:  17.10
  Codename: artful

  2).  $ apt-cache policy pulseaudio
  pulseaudio:
Installed: 1:10.0-2ubuntu3
Candidate: 1:10.0-2ubuntu3
Version table:
   *** 1:10.0-2ubuntu3 500
  500 http://au.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  3). I expected pulse to just keep running like it always did under
  previous releases of Ubuntu

  4). It keeps dropping out after a day or so no sound and settings
  (gnome-control-center sound) to it cannot connect to it running
  pulseaudio& in a shell fixes it

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 21:44:08 2017
  InstallationDate: Installed on 2017-07-24 (104 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to artful on 2017-10-20 (16 days ago)
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0G261D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd08/06/2013:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0G261D:rvrA00:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 960
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1528915] Re: Allow changing of the top panel's colour and transparency levels without need to install extension - feature request

[Nikita Yerenkov-Scott]

@James, No, you misunderstand what I mean, I just mean the black, not
all the icons and everything:


** Attachment added: "Screenshot from 2017-11-06 11-15-57.png"
   
https://bugs.launchpad.net/ubuntu-gnome/+bug/1528915/+attachment/5004604/+files/Screenshot%20from%202017-11-06%2011-15-57.png

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

Title:
  Allow changing of the top panel's colour and transparency levels
  without need to install extension - feature request

Status in gnome-control-center:
  Unknown
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Currently if one wants to change the colour or transparency levels of
  the top panel they have to install an extension, I think that this
  functionality should be built-in so that one can just change these
  settings in the gnome-control-center rather than having to install
  some third-party extension.

  I am running Ubuntu GNOME 15.10 with GNOME 3.18.

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

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

[Desktop-packages] [Bug 1631663] Re: wnck-applet crashed with signal 5 in _XReply()

[Vlad Orlov]

** This bug is no longer a duplicate of bug 1609597
   wnck-applet crashed with signal 5 in _XReply()

** Package changed: mate-panel (Ubuntu) => libwnck3 (Ubuntu)

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

Title:
  wnck-applet crashed with signal 5 in _XReply()

Status in libwnck3 package in Ubuntu:
  New

Bug description:
  wnck-applet crashed with signal 5 in _XReply()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: mate-panel 1.16.0-1
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Oct  9 00:16:18 2016
  ExecutablePath: /usr/lib/mate-panel/wnck-applet
  InstallationDate: Installed on 2016-10-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20161007)
  ProcCmdline: /usr/lib/mate-panel/wnck-applet
  Signal: 5
  SourcePackage: mate-panel
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XGetSelectionOwner () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libwnck-3.so.0
  Title: wnck-applet crashed with signal 5 in _XReply()
  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/libwnck3/+bug/1631663/+subscriptions

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

[Desktop-packages] [Bug 1718654] Re: Touchpad input doesn't work after longer suspend.

[Jonathan Elchison]

Concur, thanks for the guidance.  This touchpad behavior seems to have
been introduced between 4.10.0-37-generic and 4.13.0-16-generic.

Other folks experiencing this issue should attempt booting into your
last-known-good kernel.

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

Title:
  Touchpad input doesn't work after longer suspend.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When I resume my laptop from a longer (not sure what the threshold is
  yet) suspend, I don't get input from the touchpad, a short suspend
  cycle fixes it.

  Touchscreen works all the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 14:20:56 2017
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1728067] Re: CUPS : wrong imageable area A4 for Canon MG4200

[Till Kamppeter]

Can you attach your PPD file? So I can see from which driver it comes.

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

Title:
  CUPS : wrong imageable area A4 for Canon MG4200

Status in cups package in Ubuntu:
  New

Bug description:
  Prints are shifted to the bottom, end of the page is never printed. 
  I have a look on the ppd file of my printer and the imageablearea for size A4 
seems wrong.

  It's should be

  ImageableArea A4/A4: "18 36 577 806"

  but it's ImageableArea A4: "18 106 577 819"

  I tried to edit and change it, but on each reload of cups the wrong
  version come in place.

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

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

[Desktop-packages] [Bug 1730433] Re: Keyboard not working at login screen

[Sebastien Bacher]

Thank you for your bug report. Could you make a photo of your login
screen? The gdm in 17.10 is gdm not unity-greeter so are you sure you
are using the later one? Could you add your syslog to the bug?

** Changed in: unity-greeter (Ubuntu)
   Importance: Undecided => Low

** Changed in: unity-greeter (Ubuntu)
   Status: New => Incomplete

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

Title:
  Keyboard not working at login screen

Status in unity-greeter package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10 in use, keyboard (USB Corsair Strafe) often not working
  on login screen, especially after cold boot.

  I've checked other bug reports, but none show this as being fixed and
  it's affecting the latest Ubuntu at the time of writing this (version
  17.10). All latest updates installed.

  The keyboard is plugged in properly and when Ubuntu does recognise it
  after unplugging and reconnecting, the keyboard works fine (which
  rules out any hardware fault). Latest BIOS installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1730433/+subscriptions

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

[Desktop-packages] [Bug 1730513] [NEW] korganiser reminders do not trigger with 17.04.3

[Rik Mills]

Public bug reported:

akonadi:  4:17.04.3-0ubuntu in artful and  4:17.04.3-0ubuntu1 and
ubuntu2 in bionic

When the korganizer tray daemon (koragc) is set to enable event
reminders, these silently fail to appear.

Seemingly upstream KDE bug: https://bugs.kde.org/show_bug.cgi?id=384212

With back-portable fix from the 17.08 branch:
https://cgit.kde.org/akonadi.git/commit/?h=Applications/17.08=d3c6ba904798768b0c83c2e182c27b1c624f78ca

Test build for artful in:
https://launchpad.net/~rikmills/+archive/ubuntu/akonadi-bug

** Affects: akonadi
 Importance: Unknown
 Status: Unknown

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

** Affects: akonadi (Ubuntu Artful)
 Importance: Undecided
 Status: Confirmed

** Affects: akonadi (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Also affects: akonadi (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: akonadi (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Bug watch added: KDE Bug Tracking System #384212
   https://bugs.kde.org/show_bug.cgi?id=384212

** Also affects: akonadi via
   https://bugs.kde.org/show_bug.cgi?id=384212
   Importance: Unknown
   Status: Unknown

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

** Description changed:

  akonadi:  4:17.04.3-0ubuntu in artful and  4:17.04.3-0ubuntu1 and
  ubuntu2 in bionic
  
  When the korganizer tray daemon (koragc) is set to enable event
  reminders, these silently fail to appear.
  
  Seemingly upstream KDE bug: https://bugs.kde.org/show_bug.cgi?id=384212
  
- With back-portable fix form the 17.08 branch:
+ With back-portable fix from the 17.08 branch:
  
https://cgit.kde.org/akonadi.git/commit/?h=Applications/17.08=d3c6ba904798768b0c83c2e182c27b1c624f78ca
  
  Test build for artful in:
  https://launchpad.net/~rikmills/+archive/ubuntu/akonadi-bug

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

Title:
  korganiser reminders do not trigger with 17.04.3

Status in Akonadi:
  Unknown
Status in akonadi package in Ubuntu:
  New
Status in akonadi source package in Artful:
  Confirmed
Status in akonadi source package in Bionic:
  New

Bug description:
  akonadi:  4:17.04.3-0ubuntu in artful and  4:17.04.3-0ubuntu1 and
  ubuntu2 in bionic

  When the korganizer tray daemon (koragc) is set to enable event
  reminders, these silently fail to appear.

  Seemingly upstream KDE bug:
  https://bugs.kde.org/show_bug.cgi?id=384212

  With back-portable fix from the 17.08 branch:
  
https://cgit.kde.org/akonadi.git/commit/?h=Applications/17.08=d3c6ba904798768b0c83c2e182c27b1c624f78ca

  Test build for artful in:
  https://launchpad.net/~rikmills/+archive/ubuntu/akonadi-bug

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

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

[Desktop-packages] [Bug 1730521] [NEW] transparencey gone in dock panel (wayland)

[ventrical]

Public bug reported:

After update/upgrade transparency is gone on the dock panel.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.26.1-0ubuntu6
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov  6 17:38:38 2017
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'app-picker-view' b'uint32 1'
 b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 
'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2017-10-13 (24 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  transparencey gone in dock panel (wayland)

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After update/upgrade transparency is gone on the dock panel.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.1-0ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 17:38:38 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 
'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-13 (24 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1730521] Re: transparencey gone in dock panel (wayland)

[Launchpad Bug Tracker]

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

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

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

Title:
  transparencey gone in dock panel (wayland)

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After update/upgrade transparency is gone on the dock panel.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.1-0ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 17:38:38 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 
'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-13 (24 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1730513] Re: korganiser reminders do not trigger with 17.04.3

[Bug Watch Updater]

** Changed in: akonadi
   Status: Unknown => Fix Released

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

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

Title:
  korganiser reminders do not trigger with 17.04.3

Status in Akonadi:
  Fix Released
Status in akonadi package in Ubuntu:
  New
Status in akonadi source package in Artful:
  Confirmed
Status in akonadi source package in Bionic:
  New

Bug description:
  akonadi:  4:17.04.3-0ubuntu in artful and  4:17.04.3-0ubuntu1 and
  ubuntu2 in bionic

  When the korganizer tray daemon (koragc) is set to enable event
  reminders, these silently fail to appear.

  Seemingly upstream KDE bug:
  https://bugs.kde.org/show_bug.cgi?id=384212

  With back-portable fix from the 17.08 branch:
  
https://cgit.kde.org/akonadi.git/commit/?h=Applications/17.08=d3c6ba904798768b0c83c2e182c27b1c624f78ca

  Test build for artful in:
  https://launchpad.net/~rikmills/+archive/ubuntu/akonadi-bug

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

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

[Desktop-packages] [Bug 1730253] Re: Clamshell mode only works immediately after changing display settings

[James]

Thanks for this, I went and checked the upstream project and found it
has already been reported there and a patch was created just yesterday:

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

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

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

Title:
  Clamshell mode only works immediately after changing display settings

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have just upgraded to Ubuntu 17.10 (and so switched from Unity to
  Gnome 3).

  I have a laptop and I sometimes use an external monitor with the
  laptop closed (clamshell mode), and I sometimes use the laptop monitor
  with no external monitor.

  If I change my display settings, eg if I change from mirrored display
  mode to extended desktop, or vice versa, it doesn't which direction I
  change it, the point is that I change it, then after that change, I
  can close my laptop lid, and the laptop will switch to just displaying
  on the external monitor, ie, it will work in clamshell mode.

  If I then unplug the external monitor, open the laptop and start using
  it with its own monitor, and then later I plug the monitor back in (at
  this time the monitor turns back on and displays according to whatever
  I had the settings at), and then close the laptop lid again, the
  laptop suspends, the external monitor turns off, ie clamshell mode
  doesn't work.

  The thing that seems to trigger to make clamshell mode work again is
  that I have to change the display settings, from mirrored to extended
  desktop or vice versa, doesn't matter which direction I change it in,
  as long as I change it, that seems to tell the laptop that it's
  allowed to go into clamshell mode when I close the lid.

  So it seems that unplugging the monitor (or maybe plugging it in)
  resets whatever prevents the laptop from suspending when the lid is
  closed, and reconfiguring the display settings turns it back on.

  I've Googled for solutions, most recommend configuring the laptop to
  not suspend when the lid is closed, but that's not an acceptable
  solution - I don't want the laptop to stay on when I unplug it and put
  it in my bag.

  Everything worked as expected with Ubuntu 17.04. The laptop suspended
  when I expected it to (I'm actually not sure if suspending was caused
  by unplugging the external monitor while the lid was closed, or
  unplugging the power while the lid was closed, I expect the latter),
  while closing the lid while an external monitor was connected didn't
  suspend (and again, perhaps this was actually closing the lid when
  power was connected that caused it to stay on, not sure).

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

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

[Desktop-packages] [Bug 1641284] Re: libatk-adaptor breaks down the LibreOffice TexMaths extension

[Roland]

Bug confirmed on Debian 9 (stretch), too.
Here, libatk-adaptor is installed by default as a dependency of orca und 
task-xfce-desktop.
So i cannot purge it without breaking my system.

After disabling atk-adaptor

  mv /etc/X11/Xsession.d/90atk-adaptor /etc/X11/Xsession.d/90atk-
adaptor.bak

as suggested by Roland65 here

  https://sourceforge.net/p/texmaths/bugs/69/#822d

my TexMaths-Plugin works fine.

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

Title:
  libatk-adaptor breaks down the LibreOffice TexMaths extension

Status in at-spi2-atk package in Ubuntu:
  Confirmed

Bug description:
  Package: libatk-adaptor 2.18.1-2ubuntu1
  System: Ubuntu 16.04.1 LTS (Xenial Xerus)

  If the package libatk-adaptor is installed on Ubuntu (as a depency of
  gnome-orca for example), it breaks down the LibreOffice TexMaths
  extension. TexMaths is a popular extension used to enter / edit LaTeX
  equations on LibreOffice (see http://roland65.free.fr/texmaths).

  Step to reproduce the bug:

  1. It is assumed that LibreOffice 5.1.4 (with at least the Writer and
  Draw components) is installed on Ubuntu. It is also assumed that
  libatk-adaptor is installed.

  2. Install texlive:
  sudo apt-get install texlive

  3. Download and install the TexMaths extension (version 0.42) from
  there: https://sourceforge.net/projects/texmaths/files/0.42/

  4. Create a new empty Writer document, then click on the Pi icon (this
  is the TexMaths icon) and in the window that opens, type: 'x(t)+y(t)'
  (without the quotes), then click on the LaTeX button. This generates
  an SVG image of the 'x(t)+y(t)' equation.

  5. Select the SVG image of the equation by left clicking on it. Then
  click on the Pi icon. Now, instead of editing the equation, an error
  message is displayed: "The selected object is not a TexMaths
  equation... Please unselect it and call the macro again...".

  6. Now, right click on the SVG image and select the 'Description' menu
  voice. In the window that opens, the description is empty and does not
  contain the equation text, as it should.

  7. Now purge (and not just remove) the libatk-adaptor package:

  sudo apt-get purge libatk-adaptor

  then logout and login and repeat the steps 4, 5, and 6: everything is
  OK and the equation can be edited as usual.

  Another way to remove the bug instead of purging libatk-adaptor is to
  rename the file: /etc/X11/Xsession.d/90atk-adaptor to
  /etc/X11/Xsession.d/90atk-adaptor.orig . Then logout and login.

  Note there is another bug #1584795 that relates libatk-adaptor and
  LibreOffice, see there https://bugs.launchpad.net/ubuntu/+source/at-
  spi2-atk/+bug/1584795

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1641284/+subscriptions

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

[Desktop-packages] [Bug 1730528] [NEW] Dragging a folder to create a bookmark makes the folder unreadable

[rahul]

Public bug reported:

When dragging a folder to create a bookmark on the left panel, deletes
the folder and makes the folder unreadable. The folder cannot be found
even in trash, you can see the folders until the next restart but in
properties it shows unreadable

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  7 00:25:18 2017
InstallationDate: Installed on 2017-10-23 (14 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: nautilus
UpgradeStatus: Upgraded to artful on 2017-11-03 (3 days ago)

** Affects: nautilus (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 nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1730528

Title:
  Dragging a folder  to create a bookmark makes the folder unreadable

Status in nautilus package in Ubuntu:
  New

Bug description:
  When dragging a folder to create a bookmark on the left panel, deletes
  the folder and makes the folder unreadable. The folder cannot be found
  even in trash, you can see the folders until the next restart but in
  properties it shows unreadable

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 00:25:18 2017
  InstallationDate: Installed on 2017-10-23 (14 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to artful on 2017-11-03 (3 days ago)

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

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

[Desktop-packages] [Bug 1730469] Re: Display session freezes constitently on login after Win10 dual boot crash - Ubuntu 16.04

[Maxime Chambonnet]

** Tags added: lightdm

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

Title:
  Display session freezes constitently on login after Win10 dual boot
  crash - Ubuntu 16.04

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello,
  I have a Sandybridge-B970 X301-Asus laptop. I am used to dual boot on it : 
win10 and Ubuntu Xenial on a 275 GB SSD.
  Yesterday I manually forced shut down on win10 which looked hung on 
~"preparation... do not shut down".
  Windows recovered, but Ubuntu was corrupted it seems.
  Grub2 launches, Ubuntu boots. I reach (Unity?) graphical login. Then I cannot 
input mouse nor keyboard, and after a few inputs login prompt hangs. The UI 
displays "connected to ethernet". I cannot Alt Gr Fx to other ttys.
  I can REISUB, I can launch a recovery mode and get a root shell. I can SSH 
after normal boot from an external Debian system.
  Filesystem looks OK. Not sure but for some reason directories seems to have 
appeared in /root (git..)

  My SSD partitions : https://postimg.org/image/2hmo7pgfiz/, on top of
  debug info.

  Best regards!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Nov  6 18:38:53 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:14f7]
  InstallationDate: Installed on 2017-03-04 (247 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: ASUSTeK COMPUTER INC. X301A1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic.efi.signed 
root=UUID=84fd9c9d-fdb2-4ebf-a754-115d068500e0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X301A1.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X301A1
  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.:bvrX301A1.204:bd05/02/2012:svnASUSTeKCOMPUTERINC.:pnX301A1:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX301A1:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X301A1
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Nov  6 18:33:32 2017
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1730469] Re: Display session freezes constitently on login after Win10 dual boot crash - Ubuntu 16.04

[Maxime Chambonnet]

** Attachment added: "buggedx-0.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1730469/+attachment/5005020/+files/buggedx-0.log

** Description changed:

  Hello,
  I have a Sandybridge-B970 X301-Asus laptop. I am used to dual boot on it : 
win10 and Ubuntu Xenial on a 275 GB SSD.
  Yesterday I manually forced shut down on win10 which looked hung on 
~"preparation... do not shut down".
  Windows recovered, but Ubuntu was corrupted it seems.
- Grub2 launches, Ubuntu boots. I reach (Unity?) graphical login. Then I cannot 
input mouse nor keyboard, and after a few inputs login prompt hangs. The UI 
displays "connected to ethernet". I cannot Alt Gr Fx to other ttys.
+ Grub2 launches, Ubuntu boots. I reach lightdm greeter. Then I cannot input 
mouse nor keyboard, and after a few inputs login prompt hangs. The UI displays 
"connected to ethernet". I cannot Alt Gr Fx to other ttys.
  I can REISUB, I can launch a recovery mode and get a root shell. I can SSH 
after normal boot from an external Debian system.
  Filesystem looks OK. Not sure but for some reason directories seems to have 
appeared in /root (git..)
  
  My SSD partitions : https://postimg.org/image/2hmo7pgfiz/, on top of
  debug info.
  
  Best regards!
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Nov  6 18:38:53 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:14f7]
+  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:14f7]
  InstallationDate: Installed on 2017-03-04 (247 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: ASUSTeK COMPUTER INC. X301A1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic.efi.signed 
root=UUID=84fd9c9d-fdb2-4ebf-a754-115d068500e0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X301A1.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X301A1
  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.:bvrX301A1.204:bd05/02/2012:svnASUSTeKCOMPUTERINC.:pnX301A1:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX301A1:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X301A1
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Nov  6 18:33:32 2017
  xserver.configfile: default
  xserver.devices:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: modeset

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

Title:
  Display session freezes constitently on login after Win10 dual boot
  crash - Ubuntu 16.04

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello,
  I have a Sandybridge-B970 X301-Asus laptop. I am used to dual boot on it : 
win10 and Ubuntu Xenial on a 275 GB SSD.
  Yesterday I manually forced shut down on win10 which looked hung on 
~"preparation... do not shut down".
  Windows recovered, but Ubuntu was corrupted it seems.
  Grub2 launches, Ubuntu boots. I reach lightdm greeter. Then I cannot input 
mouse nor keyboard, and after a 

[Desktop-packages] [Bug 1730469] Re: Display session freezes constitently on login after Win10 dual boot crash - Ubuntu 16.04

[Maxime Chambonnet]

- a hung lightdm login

** Attachment added: "buggedlightdm.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1730469/+attachment/5005016/+files/buggedlightdm.log

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

Title:
  Display session freezes constitently on login after Win10 dual boot
  crash - Ubuntu 16.04

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello,
  I have a Sandybridge-B970 X301-Asus laptop. I am used to dual boot on it : 
win10 and Ubuntu Xenial on a 275 GB SSD.
  Yesterday I manually forced shut down on win10 which looked hung on 
~"preparation... do not shut down".
  Windows recovered, but Ubuntu was corrupted it seems.
  Grub2 launches, Ubuntu boots. I reach lightdm greeter. Then I cannot input 
mouse nor keyboard, and after a few inputs login prompt hangs. The UI displays 
"connected to ethernet". I cannot Alt Gr Fx to other ttys.
  I can REISUB, I can launch a recovery mode and get a root shell. I can SSH 
after normal boot from an external Debian system.
  Filesystem looks OK. Not sure but for some reason directories seems to have 
appeared in /root (git..)

  My SSD partitions : https://postimg.org/image/2hmo7pgfiz/, on top of
  debug info.

  Best regards!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Nov  6 18:38:53 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:14f7]
  InstallationDate: Installed on 2017-03-04 (247 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: ASUSTeK COMPUTER INC. X301A1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic.efi.signed 
root=UUID=84fd9c9d-fdb2-4ebf-a754-115d068500e0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X301A1.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X301A1
  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.:bvrX301A1.204:bd05/02/2012:svnASUSTeKCOMPUTERINC.:pnX301A1:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX301A1:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X301A1
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Nov  6 18:33:32 2017
  xserver.configfile: default
  xserver.devices:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1730537] [NEW] package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[GG]

Public bug reported:

I am not a sure about details, other than I had issues upgrading from
14.04 and now have many errors.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic i686
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
Date: Mon Nov  6 12:02:31 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2012-09-04 (1889 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: tex-common
Title: package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2017-11-06 (0 days ago)

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


** Tags: apport-package i386 xenial

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  I am not a sure about details, other than I had issues upgrading from
  14.04 and now have many errors.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  Date: Mon Nov  6 12:02:31 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2012-09-04 (1889 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-11-06 (0 days ago)

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

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