[Desktop-packages] [Bug 1817393] [NEW] Unable to view details on top panel

[shivdhwaj pandey]

Public bug reported:

Unable to view details on the top panel

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

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

Title:
  Unable to view details on top panel

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

Bug description:
  Unable to view details on the top panel

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

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

[Desktop-packages] [Bug 66566]

[Bmorrison025]

My Apple laptop has a Ctrl key on the left side only, which means this
functionality is no longer a one-handed operation. For me this is a
frustrating downgrade, but for others I expect it's an accessibility
issue. No? I'd also like an option to restore the longstanding behavior.

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

Title:
  Inconsistent shortcuts for new tab

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Won't Fix
Status in firefox-3.0 package in Ubuntu:
  Won't Fix
Status in firefox-3.5 package in Ubuntu:
  Won't Fix

Bug description:
  There are currently too many shortcuts when opening a link in a new
  tab:

   - location bar:  + 
   - GO button:  + click
   - search bar:  + 
   - SEARCH button  + click
   - links:  + click
   - menu bar:  + click
   - BACKWARD/FORWARD button:  + click

  This is one of the reasons I'm keeping with Opera. There it is always
  the shift key and I have to remember only one key.

  Thanks for reading!

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

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

[Desktop-packages] [Bug 66566]

[Gijskruitbosch+bugs]

(In reply to cousteau from comment #163)

> I don't see how removing shift-enter and ctrl-shift-enter is even
remotely related to the original request of making ctrl-enter open URLs
in a new tab.

The point of the bug as filed was to make link opening modifiers work
the same between the url bar and other usecases. That applies to shift
and ctrl-shift as much as it does to just ctrl.

> Personally, if this feature were really necessary (in which case it
should have been opened as a separate bug), I would rather have it moved
to an unused combination.  For example, Windows-enter could be "open in
new window" and Windows-alt-enter for "open in new tab, but on the
background".

We don't use any windows+ shortcuts inside Firefox and doing
so would be going against platform convention, which we wouldn't do
without very good reasons, so this is a non-starter.

> Ultimately, removing the shortcut for .net and .org but keeping it for
.com somehow suggests that .net and .org sites are "less important" than
.com ones.  I could expect that from a browser developed by google.com
or microsoft.com, but not from one developed by mozilla.org.

In the global alexa top 50 there is 1 .org site (wikipedia), 1 .net site
(a Chinese site), and 48 .com sites, and so .com sites are pretty
conclusively more commonly used. Not to mention the fact that, if for
whatever reason .net (or any other suffix) is more common in your own
browsing habits, you can configure the default suffix in about:config
(both before and after this change), and it was never possible to
configure the suffix for shift-enter and ctrl-shift-enter.


I'm going to restrict comments here. The recent history of comments is just 
repeated complaints that reiterate ground that has already been covered, and as 
such isn't productive anymore. To reiterate:

- we won't (add a pref to) revert this behavior change. See comment #143. There 
are always trade-offs when making changes to frequently-used parts of the 
browser like the URL bar. We considered these trade-offs carefully before 
making the change. That doesn't mean we believe there are no negative 
side-effects, or that we don't regret people having to retrain muscle memory - 
it means we made the change despite those side-effects, because we believe the 
upsides outweigh those negative side-effects.
- yes, there's remaining ground to cover in terms of fixing up shortcuts to be 
even more consistent with other browsers and/or with other uses of modifier 
keys within Firefox. See bug 1513830, bug 1506203, bug 1506247 . If there's 
other inconsistencies that got missed, please file separate follow-up bugs.
- you can already change the default completion for ctrl-enter to something 
else in about:config using browser.fixup.alternate.suffix , if that's 
preferable over .com .
- there are extant bugs on file for improving webextension control over 
shortcuts via bug 1215061 and deps.

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

Title:
  Inconsistent shortcuts for new tab

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Won't Fix
Status in firefox-3.0 package in Ubuntu:
  Won't Fix
Status in firefox-3.5 package in Ubuntu:
  Won't Fix

Bug description:
  There are currently too many shortcuts when opening a link in a new
  tab:

   - location bar:  + 
   - GO button:  + click
   - search bar:  + 
   - SEARCH button  + click
   - links:  + click
   - menu bar:  + click
   - BACKWARD/FORWARD button:  + click

  This is one of the reasons I'm keeping with Opera. There it is always
  the shift key and I have to remember only one key.

  Thanks for reading!

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

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

[Desktop-packages] [Bug 66566]

[cousteau]

I don't see how removing shift-enter and ctrl-shift-enter is even remotely 
related to the original request of making ctrl-enter open URLs in a new tab.  
In addition, it breaks a preexisting functionality of having shift-enter 
automatically add www. .net and ctrl-shift-enter add www. .org.
Personally, if this feature were really necessary (in which case it should have 
been opened as a separate bug), I would rather have it moved to an unused 
combination.  For example, Windows-enter could be "open in new window" and 
Windows-alt-enter for "open in new tab, but on the background".
Or, if it is really that important to have these shortcuts on shift and 
ctrl-shift, even despite of breaking preexisting behavior and getting a lot of 
users upset, at least make windows-enter and ctrl-windows-enter the new .net 
and .org shortcuts so that this functionality is not lost.
(Or going further: use alt for .com, windows for .net, and alt-windows for 
.org, so that ctrl is left for opening on a new tab, be it from the URL bar or 
from a link on the page; now THAT would solve the inconsistency issue the bug 
originally complained about.)

Ultimately, removing the shortcut for .net and .org but keeping it for
.com somehow suggests that .net and .org sites are "less important" than
.com ones.  I could expect that from a browser developed by google.com
or microsoft.com, but not from one developed by mozilla.org.

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

Title:
  Inconsistent shortcuts for new tab

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Won't Fix
Status in firefox-3.0 package in Ubuntu:
  Won't Fix
Status in firefox-3.5 package in Ubuntu:
  Won't Fix

Bug description:
  There are currently too many shortcuts when opening a link in a new
  tab:

   - location bar:  + 
   - GO button:  + click
   - search bar:  + 
   - SEARCH button  + click
   - links:  + click
   - menu bar:  + click
   - BACKWARD/FORWARD button:  + click

  This is one of the reasons I'm keeping with Opera. There it is always
  the shift key and I have to remember only one key.

  Thanks for reading!

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

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

[Desktop-packages] [Bug 1437974] Re: xchat-gnome Prefences window too big to display all content

[Bug Watch Updater]

** Changed in: xchat-gnome
   Status: Confirmed => Won't Fix

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

Title:
  xchat-gnome Prefences window too big to display all content

Status in XChat-GNOME:
  Won't Fix
Status in xchat-gnome package in Ubuntu:
  Triaged

Bug description:
  xchat-gnome Prefences window too big to display all content as per
  attach screenshot. I used to be able to WORKAROUND this type of
  problem with other programs by creating four workspaces, and moving
  the windows half way down the workspace, then switching to the
  workspace vertically below it, but it doesn't show anything in gnome-
  session-flashback (metacity).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xchat-gnome 1:0.30.0~git20141005.816798-0ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Mar 29 19:46:05 2015
  InstallationDate: Installed on 2014-06-21 (281 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: xchat-gnome
  UpgradeStatus: Upgraded to vivid on 2015-03-13 (16 days ago)

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

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

[Desktop-packages] [Bug 108818] Re: Join/leave messages make chatrooms with many members almost unreadable

[Bug Watch Updater]

** Changed in: xchat-gnome
   Status: New => Won't Fix

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

Title:
  Join/leave messages make chatrooms with many members almost unreadable

Status in XChat-GNOME:
  Won't Fix
Status in xchat-gnome package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: xchat-gnome

  When joining a large Chat-Room (such as #ubuntu or #ubuntu-release-
  party) the discussion gets totally bogged down by the join leave
  messages.

  So if more than 1000 members are in a chatroom sometimes more than 7
  of 10 messages are just join/leave which leaves much less room to the
  already fast moving conversation and makes it very difficult to follow
  it.

  Other irc-clients have a sort of conference mode for this, so that if
  a room contains more than N members, they stop showing the join/leave
  messages. I'd like that. :)

  Good numbers for N could be either 10, 30 or 60 members, though that
  could also be determined empirically, that is the number of members to
  a chatroom when the join / leave messages start to get more on the
  nerves than they are useful.

  :) Martin

  ProblemType: Bug
  Architecture: i386
  Date: Sun Apr 22 09:22:48 2007
  DistroRelease: Ubuntu 7.04
  ExecutablePath: /usr/bin/xchat-gnome
  Package: xchat-gnome 1:0.16-0ubuntu3
  PackageArchitecture: i386
  ProcCmdline: xchat-gnome
  ProcCwd: /home/dwt
  ProcEnviron:
   LANGUAGE=de_DE:de:en_GB:en
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: xchat-gnome
  Uname: Linux dwts-laptop 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 
2007 i686 GNU/Linux

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

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

[Desktop-packages] [Bug 185171] Re: gnome-open has no manpage

[Bug Watch Updater]

** Changed in: libgnome
   Status: New => Won't Fix

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

Title:
  gnome-open has no manpage

Status in libgnome:
  Won't Fix
Status in libgnome package in Ubuntu:
  Fix Released
Status in libgnome package in Debian:
  Fix Released

Bug description:
  [rainct, ~]$ man gnome-open
  No manual entry for gnome-open

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

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

[Desktop-packages] [Bug 716607] Re: Scrolls to top of window when started up with existing backlog

[Bug Watch Updater]

** Changed in: xchat-gnome
   Status: New => Won't Fix

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

Title:
  Scrolls to top of window when started up with existing backlog

Status in XChat-GNOME:
  Won't Fix
Status in xchat package in Ubuntu:
  Confirmed
Status in xchat-gnome package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: xchat-gnome

  When xchat-gnome fires up, tabs load up logged chat text from the
  previous sessions, which is really nice.  However, initially xchat-
  gnome starts with the text areas showing the top of the text (position
  0 I guess), rather than scrolling the text area to the bottom to show
  the most recent comments.

  It seems that after any comment or activity on the respective channel,
  the text area automatically moves to the bottom as it should.  So it's
  a minor issue, but confusing.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: xchat-gnome 1:0.26.1+git20101206.557c940-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-2.29-generic-pae 2.6.38-rc3
  Uname: Linux 2.6.38-2-generic-pae i686
  Architecture: i386
  Date: Thu Feb 10 10:47:12 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=C
   SHELL=/bin/bash
  SourcePackage: xchat-gnome

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

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

[Desktop-packages] [Bug 1817346] Re: Printing blue pages after upgrading ghostscript to 9.26~dfsg+0-0ubuntu0.16.04.5

[Amin]

Note that when I print from my phone via Wifi, it prints just fine.

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

Title:
  Printing blue pages after upgrading ghostscript to
  9.26~dfsg+0-0ubuntu0.16.04.5

Status in ghostscript package in Ubuntu:
  Confirmed

Bug description:
  Various machines running Ubuntu 16-04 are printing blue background
  pages after upgrading 9.26~dfsg+0-0ubuntu0.16.04.4 to
  9.26~dfsg+0-0ubuntu0.16.04.5 in the automatic updates. The issue is
  bigger because, after solving by manually installing the 16.04.4
  version, any upgrade in hplip or automatic system upgrades reinstall
  the lastest version.

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

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

[Desktop-packages] [Bug 1817346] Re: Printing blue pages after upgrading ghostscript to 9.26~dfsg+0-0ubuntu0.16.04.5

[Amin]

I have the same problem. Installed hplip today for my HP OJ 6958 printer
and blue color printed all over the page.

Package: ghostscript
Version: 9.26~dfsg+0-0ubuntu0.18.04.5


$ hp-check

HP Linux Imaging and Printing System (ver. 3.19.1)
Dependency/Version Check Utility ver. 15.1

Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Note: hp-check can be run in three modes:
1. Compile-time check mode (-c or --compile): Use this mode before compiling 
the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper 
dependencies are installed to
successfully compile HPLIP. 

  
2. Run-time check mode (-r or --run): Use this mode to determine if a distro 
supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball 
has the proper dependencies
installed to successfully run.  

  
3. Both compile- and run-time check mode (-b or --both) (Default): This mode 
will check both of the above cases (both compile- and run-time dependencies).   
 

Check types:

  
a. EXTERNALDEP - External Dependencies  

  
b. GENERALDEP - General Dependencies (required both at compile and run time)

  
c. COMPILEDEP - Compile time Dependencies   

  
d. [All are run-time checks]

  
PYEXT SCANCONF QUEUES PERMISSION

  

Status Types:
OK
MISSING   - Missing Dependency or Permission or Plug-in
INCOMPAT  - Incompatible dependency-version or Plugin-version

 
---
| SYSTEM INFO |
---

 Kernel: 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 GNU/Linux
 Host: future
 Proc: 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 GNU/Linux
 Distribution: 12 18.04
 Bitness: 64 bit


---
| HPLIP CONFIGURATION |
---

HPLIP-Version: HPLIP 3.19.1
HPLIP-Home: /usr/share/hplip
HPLIP-Installation: Auto installation is supported for ubuntu distro  18.04 
version 

Current contents of '/etc/hp/hplip.conf' file:
# hplip.conf.  Generated from hplip.conf.in by configure.

[hplip]
version=3.19.1

[dirs]
home=/usr/share/hplip
run=/var/run
ppd=/usr/share/ppd/HP
ppdbase=/usr/share/ppd
doc=/usr/share/doc/hplip-3.19.1
html=/usr/share/doc/hplip-3.19.1
icon=/usr/share/applications
cupsbackend=/usr/lib/cups/backend
cupsfilter=/usr/lib/cups/filter
drv=/usr/share/cups/drv/hp
bin=/usr/bin
apparmor=/etc/apparmor.d
# Following values are determined at configure time and cannot be changed.
[configure]
network-build=yes
libusb01-build=no
pp-build=no
gui-build=yes
scanner-build=yes
fax-build=yes
dbus-build=yes
cups11-build=no
doc-build=yes
shadow-build=no
hpijs-install=no
foomatic-drv-install=no
foomatic-ppd-install=no
foomatic-rip-hplip-install=no
hpcups-install=yes
cups-drv-install=yes
cups-ppd-install=no
internal-tag=3.19.1
restricted-build=no
ui-toolkit=qt4
qt3=no
qt4=yes
qt5=no
policy-kit=no
lite-build=no
udev_sysfs_rules=no
hpcups-only-build=no
hpijs-only-build=no
apparmor_build=yes
class-driver=no


Current contents of '/var/lib/hp/hplip.state' file:
Plugins are not installed. Could not access file: No such file or directory

Current contents of '~/.hplip/hplip.conf' file:
[upgrade]
notify_upgrade = true
last_upgraded_time = 155014
pending_upgrade_time = 0
latest_available_version = 3.17.10

[last_used]
device_uri = hp:/net/OfficeJet_6950?ip=10.0.0.133

[installation]
date_time = 02/22/2019 21:42:54
version = 3.19.1


 


--
| COMPILEDEP |
--

 gcc  gcc - GNU Project C and C++ Compiler  
   REQUIRED-   7.3.0   OK 

[Desktop-packages] [Bug 1817334] Re: dock disappears after apt dist-upgrade, needed to install gnome-shell-extension-dashtodock by hand, restart gnome-shell, and enable extension in tweaks

[Jonathan Kamens]

Can you clarify? Do you mean that the new version of gnome-shell has the
dock functionality built in, or that it has a dependency on the dash-to-
dock deb which means when the new version of gnome-shell is installed
dash-to-dock will get installed automatically?

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

Title:
  dock disappears after apt dist-upgrade, needed to install gnome-shell-
  extension-dashtodock by hand, restart gnome-shell, and enable
  extension in tweaks

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Committed

Bug description:
  I did an apt dist-upgrade and got a message telling me that gnome-
  shell had crashed and asking if I wanted to report it. I figured it
  was just something funky about the upgrade so didn't bother. Instead,
  I restarted my machine just to get everything back into a sane state.
  Upon logging in after doing that, I had no dock.

  I dug around to try to figure out what was going on, and finally
  stumbled upon the description for "Ubuntu Dock" in gnome-tweaks, which
  told me to install dash to dock.

  So I installed that with apt and then restarted gnome-shell and then
  restarted gnome-tweaks and then enabled dash to dock and finally my
  dock was back.

  This is, shall we say, not an ideal upgrade experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-ubuntu-dock 64ubuntu3
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 22 10:05:57 2019
  InstallationDate: Installed on 2019-01-02 (51 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to disco on 2019-01-21 (31 days ago)

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

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

[Desktop-packages] [Bug 1817391] [NEW] Audio stuttering

[Andrew Crome]

Public bug reported:

Since installing Ubuntu 18.10 on my system which previously had windows
10 I now get an intermittent stutter or hiccup for want of a better
word. It happens in Firefox Quantum and Chrome/Chromium I have tried a
number of fixes from you tube and various forums, but it still happens
and I'm at my wits end as it is so random.

My system is a Acer Aspire XC-603

1tb HDD
4gb ram
Intel Celeron J1900 @ 1.99 GHz

The sound card is integrated on the mother board

HDA-Intell-HDA intel PCH this problem is so random i never know when its
going to happen some times it does it one sometimes multiple times.

I'm totally at a loss

Can any one help ? I'm relatively new to this

I'm unable to locate the package version

I expected a clean audio output without any bugs and I'm getting hiccups
and stuttering

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  andrew 5045 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 23 16:10:25 2019
InstallationDate: Installed on 2019-02-22 (1 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
SourcePackage: alsa-driver
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/16/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P11-B1
dmi.board.name: Aspire XC-603
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11-B1:bd06/16/2014:svnAcer:pnAspireXC-603:pvr:rvnAcer:rnAspireXC-603:rvr:cvnAcer:ct3:cvr:
dmi.product.family: Acer Desktop
dmi.product.name: Aspire XC-603
dmi.sys.vendor: Acer
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-02-23T12:07:26.743044

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


** Tags: amd64 apport-bug cosmic

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

Title:
  Audio stuttering

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Since installing Ubuntu 18.10 on my system which previously had
  windows 10 I now get an intermittent stutter or hiccup for want of a
  better word. It happens in Firefox Quantum and Chrome/Chromium I have
  tried a number of fixes from you tube and various forums, but it still
  happens and I'm at my wits end as it is so random.

  My system is a Acer Aspire XC-603

  1tb HDD
  4gb ram
  Intel Celeron J1900 @ 1.99 GHz

  The sound card is integrated on the mother board

  HDA-Intell-HDA intel PCH this problem is so random i never know when
  its going to happen some times it does it one sometimes multiple
  times.

  I'm totally at a loss

  Can any one help ? I'm relatively new to this

  I'm unable to locate the package version

  I expected a clean audio output without any bugs and I'm getting
  hiccups and stuttering

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrew 5045 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 23 16:10:25 2019
  InstallationDate: Installed on 2019-02-22 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P11-B1
  dmi.board.name: Aspire XC-603
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11-B1:bd06/16/2014:svnAcer:pnAspireXC-603:pvr:rvnAcer:rnAspireXC-603:rvr:cvnAcer:ct3:cvr:
  dmi.product.family: Acer Desktop
  dmi.product.name: Aspire XC-603
  dmi.sys.vendor: Acer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-02-23T12:07:26.743044

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

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

[Desktop-packages] [Bug 1817391] Re: Audio stuttering

[Andrew Crome]

As a side note I did not have this problem when using windows 10

This needs to be fixed some how

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

Title:
  Audio stuttering

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Since installing Ubuntu 18.10 on my system which previously had
  windows 10 I now get an intermittent stutter or hiccup for want of a
  better word. It happens in Firefox Quantum and Chrome/Chromium I have
  tried a number of fixes from you tube and various forums, but it still
  happens and I'm at my wits end as it is so random.

  My system is a Acer Aspire XC-603

  1tb HDD
  4gb ram
  Intel Celeron J1900 @ 1.99 GHz

  The sound card is integrated on the mother board

  HDA-Intell-HDA intel PCH this problem is so random i never know when
  its going to happen some times it does it one sometimes multiple
  times.

  I'm totally at a loss

  Can any one help ? I'm relatively new to this

  I'm unable to locate the package version

  I expected a clean audio output without any bugs and I'm getting
  hiccups and stuttering

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrew 5045 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 23 16:10:25 2019
  InstallationDate: Installed on 2019-02-22 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P11-B1
  dmi.board.name: Aspire XC-603
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11-B1:bd06/16/2014:svnAcer:pnAspireXC-603:pvr:rvnAcer:rnAspireXC-603:rvr:cvnAcer:ct3:cvr:
  dmi.product.family: Acer Desktop
  dmi.product.name: Aspire XC-603
  dmi.sys.vendor: Acer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-02-23T12:07:26.743044

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

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

[Desktop-packages] [Bug 1817334] Re: dock disappears after apt dist-upgrade, needed to install gnome-shell-extension-dashtodock by hand, restart gnome-shell, and enable extension in tweaks

[Sebastien Bacher]

Thank you for your bug report. Indeed not an "ideal upgrade experience"
but that's part of using a non stable serie of Ubuntu. The problem is
that the dock migrated out of disco-proposed before the new gnome-shell
version did, you can either downgrade to the previous version of ubuntu
dock or get the new gnome-shell version out of proposed

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => High

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  dock disappears after apt dist-upgrade, needed to install gnome-shell-
  extension-dashtodock by hand, restart gnome-shell, and enable
  extension in tweaks

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Committed

Bug description:
  I did an apt dist-upgrade and got a message telling me that gnome-
  shell had crashed and asking if I wanted to report it. I figured it
  was just something funky about the upgrade so didn't bother. Instead,
  I restarted my machine just to get everything back into a sane state.
  Upon logging in after doing that, I had no dock.

  I dug around to try to figure out what was going on, and finally
  stumbled upon the description for "Ubuntu Dock" in gnome-tweaks, which
  told me to install dash to dock.

  So I installed that with apt and then restarted gnome-shell and then
  restarted gnome-tweaks and then enabled dash to dock and finally my
  dock was back.

  This is, shall we say, not an ideal upgrade experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-ubuntu-dock 64ubuntu3
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 22 10:05:57 2019
  InstallationDate: Installed on 2019-01-02 (51 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to disco on 2019-01-21 (31 days ago)

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

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

[Desktop-packages] [Bug 1817269] Re: New Desktop Icons Overlap Existing Icons

[Sebastien Bacher]

It's a bug, and it's fixed in the current serie/next version of Ubuntu,
there is no proper solution/fix planned for 18.10

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

Title:
  New Desktop Icons Overlap Existing Icons

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Behaviour observed in Ubuntu Cosmic 18.10
  gnome-shell 3.30.2-0ubuntu1.18.10.1 from cosmic-proposed

  The expected behaviour is for new icons to populate unoccupied cells
  below the column, or occupy the first cell of a new column, or
  displace other icons to maintain alpha-numeric organization.

  The unexpected bevaviour is observed when desktop icons are created,
  such as when disk or network drives are mounted or files are saved to
  the desktop, they overlap the existing icons. They do not seem to take
  any specific position through a column, but they will always be within
  a column (assuming as such, as I always have 'Keep Aligned' enabled).

  An image depicting a series of screenshots is attached to illustrate
  the observed behaviour. From left to right, the images depict: first,
  a single column of organized, aligned icons occupy the desktop;
  second, a network drive is mounted using Files, overlapping (and
  aligned with) the uppermost icon; third, a second network drive is
  mounted, overlapping (and aligned with) the initial and second icon in
  that placement; fourth, an optical medium is mounted, and occupies a
  space two 'cells' below the original column; fifth, the desktop icons
  are arranged using 'Organize Desktop by Name'; sixth, an appimage is
  moved to the desktop using Files 'Move to...' function, overlapping
  half (and not aligned with) the top-most icon; seventh, a docx file is
  moved to the desktop using the same method, overlapping (and aligned
  with) the icon in the second cell of the column; finally, the desktop
  is organized again using the same method.

  Appendum on unexpected behaviour: after the intial creation of this
  bug-report, a third file was moved to the desktop using Files,
  occupying the empty cell in the first column, after it was seen that
  manually moving an icon into that cell was not preserved by 'Organize
  Desktop by Name'. After moving the file to the desktop, using the
  organize function moves that file into the second column, emptying the
  bottom cell in the first column.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.2-0ubuntu1.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 22 00:40:39 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-12-30 (54 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  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/nautilus/+bug/1817269/+subscriptions

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

[Desktop-packages] [Bug 924149] Re: package gnome-terminal-data 3.0.1-0ubuntu3 failed to install/upgrade: ErrorMessage: dependency problems - leaving unconfigured

[Launchpad Bug Tracker]

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

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

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

Title:
  package gnome-terminal-data 3.0.1-0ubuntu3 failed to install/upgrade:
  ErrorMessage: dependency problems - leaving unconfigured

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  Upgrading from Natty for Oneiric on an AMD Athon XP with low
  connection.

  ProblemType: Package
  DistroRelease: Ubuntu 11.10
  Package: gnome-terminal-data 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-13.54-generic 2.6.38.8
  Uname: Linux 2.6.38-13-generic i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Tue Jan 31 05:01:01 2012
  ErrorMessage: ErrorMessage: dependency problems - leaving unconfigured
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  PackageArchitecture: all
  SourcePackage: gnome-terminal
  Title: package gnome-terminal-data 3.0.1-0ubuntu3 failed to install/upgrade: 
ErrorMessage: dependency problems - leaving unconfigured
  UpgradeStatus: Upgraded to oneiric on 2012-01-31 (0 days ago)

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

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

[Desktop-packages] [Bug 970568] Re: can't upgrade

[Launchpad Bug Tracker]

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

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

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

Title:
  can't upgrade

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  when I try to upgrde through the trminal, it says 37 not upgraded. The
  number that is not upgraded keeps increasing.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
  Uname: Linux 3.0.0-16-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Sat Mar 31 21:24:32 2012
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to oneiric on 2011-12-08 (114 days ago)
  XsessionErrors:
   (nautilus:1714): libnotify-WARNING **: Failed to connect to proxy
   (nm-applet:1705): libnotify-WARNING **: Failed to connect to proxy

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

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

[Desktop-packages] [Bug 492598] Re: "extract here" doesn't refresh nautilus directory GUI

[Launchpad Bug Tracker]

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

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

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

Title:
  "extract here" doesn't refresh nautilus directory GUI

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Binary package hint: nautilus

  Directories do not automatically refresh using the right-click
  ``Extract Here'' method of extracting a tarball in nautilus. Users
  have to press the ``reload'' button in nautilus after extracting a
  tarball with this method. Bug could lead users to extract multiple
  versions of the tarball into the parent directory before realizing the
  error.

  This bug is similar to a prior issue with Nautilus not refreshing
  after user creates files (cannot find bug tracker for this issue).

  Bug in Nautilus ``Extract Here''
  > uname -a 
  2.6.31-15-generic #50-Ubuntu SMP Tue Nov 10 14:53:52 UTC 2009 x86_64 GNU/Linux

  >nautilus --version
  GNOME nautilus 2.28.1

  ProblemType: Bug
  Architecture: amd64
  Date: Fri Dec  4 11:36:50 2009
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  NonfreeKernelModules: wl
  Package: nautilus 1:2.28.1-0ubuntu2
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
  SourcePackage: nautilus
  Uname: Linux 2.6.31-15-generic x86_64

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

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

[Desktop-packages] [Bug 945275] Re: gnome-terminal crashed with SIGABRT in g_assertion_message()

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-terminal crashed with SIGABRT in g_assertion_message()

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  Terminal Closed unexpectedly. No action.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: gnome-terminal 3.3.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  ApportVersion: 1.94-0ubuntu1
  Architecture: amd64
  Date: Sat Mar  3 01:35:55 2012
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcCmdline: gnome-terminal
  Signal: 6
  SourcePackage: gnome-terminal
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-terminal crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to precise on 2012-03-02 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 838765] Re: gnome-terminal crashed with SIGSEGV in g_type_check_instance_cast()

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-terminal crashed with SIGSEGV in g_type_check_instance_cast()

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  ?

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
  Uname: Linux 3.0.0-9-generic i686
  Architecture: i386
  Date: Thu Sep  1 14:05:39 2011
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcCmdline: gnome-terminal
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7bc5d8 :  mov
(%eax),%ebp
   PC (0x007bc5d8) ok
   source "(%eax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%ebp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-terminal
  StacktraceTop:
   g_type_check_instance_cast () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/libgtk-3.so.0
   g_cclosure_marshal_VOID__VOID () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: gnome-terminal crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: Upgraded to oneiric on 2011-08-24 (8 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 852219] Re: gnome-terminal crashed with signal 5 in _XError()

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-terminal crashed with signal 5 in _XError()

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  gnome-terminal seems to have crashed as a resumed my machine from
  suspend.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  ApportVersion: 1.22.1-0ubuntu2
  Architecture: amd64
  Date: Fri Sep 16 23:50:28 2011
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
  ProcCmdline: gnome-terminal
  Signal: 5
  SourcePackage: gnome-terminal
  StacktraceTop:
   ?? () from /usr/lib/libgdk-3.so.0
   ?? () from /usr/lib/libgdk-3.so.0
   _XError () 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
  Title: gnome-terminal crashed with signal 5 in _XError()
  UpgradeStatus: Upgraded to oneiric on 2011-09-13 (3 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 1023927] Re: gnome-terminal crashed with SIGSERVG in free()

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-terminal crashed with SIGSERVG in free()

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  This bug is almost identical to bug # 260838 except

  This is at DistrRelease Ubuntu 12.04.

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

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

[Desktop-packages] [Bug 1015715] Re: at every startup I get three or four crash reports

[Launchpad Bug Tracker]

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

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

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

Title:
  at every startup I get three or four crash reports

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  at every startup I get three or four crush reports, but it lets me
  click on OK and lets me continue.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-terminal 3.4.1.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
  Uname: Linux 3.2.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Wed Jun 20 10:33:31 2012
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to precise on 2012-04-29 (52 days ago)

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

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

[Desktop-packages] [Bug 852408] Re: gnome-terminal crashed with SIGABRT in __kernel_vsyscall()

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-terminal crashed with SIGABRT in __kernel_vsyscall()

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  2

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic i686
  ApportVersion: 1.23-0ubuntu1
  Architecture: i386
  Date: Sat Sep 17 15:49:30 2011
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcCmdline: gnome-terminal
  Signal: 6
  SourcePackage: gnome-terminal
  StacktraceTop:
   __kernel_vsyscall ()
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: gnome-terminal crashed with SIGABRT in __kernel_vsyscall()
  UpgradeStatus: Upgraded to oneiric on 2011-09-16 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  XsessionErrors: (gwibber-service:2023): libindicate-WARNING **: Menu being 
changed when the indicator is visible.  Listeners will NOT be notified of this 
change.

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

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

[Desktop-packages] [Bug 1005659] Re: Probably a reported bug 12.10. it seams to display when Ubuntu software Center check for updates

[Launchpad Bug Tracker]

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

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

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

Title:
  Probably a reported bug 12.10. it seams to display when Ubuntu
  software Center check for updates

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  I have a HP G60.
  Probably a reported bug 12.10. it seams to display when Ubuntu software 
Center check for updates
  i Can try to help if I can.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-terminal 3.4.1.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.4.0-3.8-generic 3.4.0
  Uname: Linux 3.4.0-3-generic x86_64
  ApportVersion: 2.1-0ubuntu1
  Architecture: amd64
  Date: Mon May 28 16:30:04 2012
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120527)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)
  XsessionErrors:
   (compiz:1787): GConf-CRITICAL **: gconf_client_add_dir: assertion 
`gconf_valid_key (dirname, NULL)' failed
   (gnome-control-center:3284): background-cc-panel-WARNING **: Could not load 
/usr/share/themes/Adwaita/index.theme: No such file or directory

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

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

[Desktop-packages] [Bug 1024150] Re: Nautilus crashes when opening a new tab on a opening usb

[Launchpad Bug Tracker]

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

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

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

Title:
  Nautilus crashes when opening a new tab on a opening usb

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

Bug description:
  While I was opening a new tab on an opening usb in Ubuntu 11.10 it
  caused all open Nautilus windows to close. I have repeated the process
  many times and the bugs continue.I expected it to be able to open the
  tab with the opening USB but it caused Nautilus to close

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

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

[Desktop-packages] [Bug 939755] Re: can not remove video drivers to get my multi-screens

[Launchpad Bug Tracker]

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

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

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

Title:
  can not remove video drivers to get my multi-screens

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  i went to add drivers and load one and now i can not remove it. when i
  loaded it i lost my due screens on the same video card

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
  Uname: Linux 3.0.0-16-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Thu Feb 23 13:14:00 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-terminal
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 853563] Re: A problem installing mailutils.

[Launchpad Bug Tracker]

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

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

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

Title:
  A problem installing mailutils.

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  BRB

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-terminal 2.32.1-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  Architecture: i386
  Date: Sun Sep 18 17:28:50 2011
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 863046] Re: gnome-terminal crashed with SIGSEGV in gtk_menu_item_set_submenu()

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-terminal crashed with SIGSEGV in gtk_menu_item_set_submenu()

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  Crashes after I start him with keyboard-shurcut: Alt+F1

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportVersion: 1.23-0ubuntu2
  Architecture: amd64
  Date: Fri Sep 30 09:46:00 2011
  ExecutablePath: /usr/bin/gnome-terminal
  ProcCmdline: gnome-terminal
  SegvAnalysis:
   Segfault happened at: 0x7fb54ece0d6a : mov
0x30(%rdi),%r12
   PC (0x7fb54ece0d6a) ok
   source "0x30(%rdi)" (0x0030) not located in a known VMA region (needed 
readable region)!
   destination "%r12" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-terminal
  StacktraceTop:
   gtk_menu_item_set_submenu () from /usr/lib/libgtk-3.so.0
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-terminal crashed with SIGSEGV in gtk_menu_item_set_submenu()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 1028952] Re: Office program freezes on PDF

[Launchpad Bug Tracker]

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

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

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

Title:
  Office program freezes on PDF

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  PDF freezes when opened then unable to close program.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-terminal 3.4.1.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic i686
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: i386
  Date: Wed Jul 25 08:55:05 2012
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to precise on 2012-07-23 (2 days ago)

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

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

[Desktop-packages] [Bug 840313] Re: gnome-terminal crashed with SIGSEGV in gdk_property_change()

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-terminal crashed with SIGSEGV in gdk_property_change()

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  Terminal wasnt active or being used at the time, just in the
  background whilst I was using the user dialogue (which I guess isn't
  relevant)

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
  Uname: Linux 3.0.0-9-generic i686
  Architecture: i386
  Date: Sat Sep  3 13:51:50 2011
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
  ProcCmdline: gnome-terminal
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x60608b : mov
0xc(%eax),%edx
   PC (0x0060608b) ok
   source "0xc(%eax)" (0x000c) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-terminal
  StacktraceTop:
   gdk_property_change () from /usr/lib/libgdk-3.so.0
   ?? () from /usr/lib/libgtk-3.so.0
   ?? () from /usr/lib/libgtk-3.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: gnome-terminal crashed with SIGSEGV in gdk_property_change()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 976602] Re: I'm getting this: EXCEPTION: NSt8ios_base7failureE CAutoFile::read : end of file bitcoin in AppInit()

[Launchpad Bug Tracker]

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

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

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

Title:
  I'm getting this: EXCEPTION: NSt8ios_base7failureE
  CAutoFile::read : end of filebitcoin in AppInit()

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  When I try to log in I'm getting this: EXCEPTION: NSt8ios_base7failureE   
  CAutoFile::read : end of file   
  bitcoin in AppInit()   
  When I click OK, I get this: EXCEPTION: NSt8ios_base7failureE   
  CAutoFile::read : end of file   
  bitcoin in CMyApp::OnUnhandledException()   

  I'm running bitcoin on a ubuntu 10.10

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: gnome-terminal 2.32.0-0ubuntu1.1
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: fglrx
  Architecture: amd64
  Date: Sun Apr  8 07:14:27 2012
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal

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

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

[Desktop-packages] [Bug 873594] Re: It just stopped, I reboot and do nothing

[Launchpad Bug Tracker]

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

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

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

Title:
  It just stopped, I reboot and do nothing

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  I started the upgrade via internet and it just stopped. I reboot and
  do nothing, no buttons seem to  work

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4
  Uname: Linux 2.6.38-9-generic i686
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Thu Oct 13 21:41:36 2011
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=el_GR.UTF-8
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to oneiric on 2011-10-13 (0 days ago)

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

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

[Desktop-packages] [Bug 984899] Re: right-click menu profile preference does not work

[Launchpad Bug Tracker]

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

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

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

Title:
  right-click menu profile preference does not work

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  Right click at the terminal area and choose profile -> profile preferences, 
nothing happens. While Edit->profile preferences works properly.
  --- 
  ApportVersion: 2.0.1-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  Package: gnome-terminal 3.4.1.1-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Tags:  precise
  Uname: Linux 3.2.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1061472] Re: Ubuntu Mono font shows squares

[Launchpad Bug Tracker]

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

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

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

Title:
  Ubuntu Mono font shows squares

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  Ubuntu mono fonts show up as sqaures in GNOME Terminal. 
  I'm able to use other mono fonts, which show ok. e.g. Droid Sans Mono etc.

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

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

[Desktop-packages] [Bug 1456290] Re: package gnome-terminal 3.14.2-0ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura

[Launchpad Bug Tracker]

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

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

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

Title:
  package gnome-terminal 3.14.2-0ubuntu3 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  N/A

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: gnome-terminal 3.14.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Sun Apr 26 11:59:04 2015
  DuplicateSignature: package:gnome-terminal:3.14.2-0ubuntu3:package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2013-10-28 (566 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: gnome-terminal
  Title: package gnome-terminal 3.14.2-0ubuntu3 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)

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

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

[Desktop-packages] [Bug 1073451] Re: an upgrade from precise to oneiric is not supported with this tool

[Launchpad Bug Tracker]

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

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

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

Title:
  an upgrade from precise to oneiric is not supported with this tool

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  caused  by previous upgrade which ddnt complete
  prblems with some of the software installed

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-26.43-generic 3.0.43
  Uname: Linux 3.0.0-26-generic i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Wed Oct 31 08:51:38 2012
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANGUAGE=en_ZA:en
   LANG=en_ZA.UTF-8
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to precise on 2012-10-30 (0 days ago)

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

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

[Desktop-packages] [Bug 1515227] Re: [CRITICAL] Cannot type certain characters after upgrade

[Launchpad Bug Tracker]

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

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

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

Title:
  [CRITICAL] Cannot type certain characters after upgrade

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  Hello,

  After performing latest online upgrade (November 11, 2015), some keys
  on my keyboard perform erratically, preventing me to type certain
  characters.

  - Letter "s" shows as "s000"
  - Digit keys (above letters) trigger printscreens instead of typing, forcing 
me to use the numeric keypad.
  - x key shows "128"

  Ubuntu is 15.10 amd64, kernel 4.2.0-17-generic

  I am using a simple Logitech keyboard (Y-BP62a), with stock Romanian
  layout.

  I expect that keyboard performs normally.

  Regards,
  Răzvan

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gnome-terminal 3.16.2-1ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 11 14:10:30 2015
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2012-10-30 (1106 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=ro_RO
   PATH=(custom, no user)
   LANG=ro_RO.UTF-8
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to wily on 2015-10-23 (18 days ago)

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

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

[Desktop-packages] [Bug 1159271] Re: gnome-terminal crashed with signal 7 in g_markup_parse_context_parse()

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-terminal crashed with signal 7 in g_markup_parse_context_parse()

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  No addtional comments

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gnome-terminal 3.6.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
  Uname: Linux 3.8.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu2
  Architecture: amd64
  Date: Sun Mar 24 00:45:51 2013
  ExecutablePath: /usr/bin/gnome-terminal
  ExecutableTimestamp: 1360614252
  InstallationDate: Installed on 2011-12-10 (469 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  ProcCmdline: gnome-terminal
  ProcCwd: /home/perfe
  Signal: 7
  SourcePackage: gnome-terminal
  StacktraceTop:
   g_markup_parse_context_parse () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_ui_manager_add_ui_from_file () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-terminal crashed with signal 7 in g_markup_parse_context_parse()
  UpgradeStatus: Upgraded to raring on 2013-02-25 (26 days ago)
  UserGroups: adm admin audio avahi avahi-autoipd backup bluetooth cdrom clamav 
colord couchdb crontab dialout dip disk fax floppy fuse games iocard lp lpadmin 
mail netdev news ntp operator pcscd plugdev proxy pulse pulse-access sambashare 
saned scanner scard science src ssh ssl-cert staff tape timidity tty users 
video voice

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

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

[Desktop-packages] [Bug 1297597] Re: can not update ore upgrade to new ubuntu linix?> ships:=))))))))?please help?sos new upgrades?

[Launchpad Bug Tracker]

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

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

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

Title:
  can not update ore upgrade to new ubuntu linix?>
  ships:=?please help?sos new upgrades?

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  apt-get update; apt-get install gdb apport bugs to updat?

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: gnome-terminal 2.32.0-0ubuntu1.1
  ProcVersionSignature: Ubuntu 2.6.35-32.67-generic 2.6.35.14
  Uname: Linux 2.6.35-32-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Wed Mar 26 03:24:31 2014
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=nl_NL:en
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  XsessionErrors:
   (polkit-gnome-authentication-agent-1:1675): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (gnome-power-manager:1585): Gtk-WARNING **: A floating object was finalized. 
This means that someone
   (nautilus:1683): GConf-CRITICAL **: gconf_value_free: assertion `value != 
NULL' failed

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

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

[Desktop-packages] [Bug 1535011] Re: package gnome-terminal 3.16.2-1ubuntu4 failed to install/upgrade: s'està intentant sobreescriure «/usr/share/appdata/gnome-terminal.appdata.xml», que també està en

[Launchpad Bug Tracker]

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

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

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

Title:
  package gnome-terminal 3.16.2-1ubuntu4 failed to install/upgrade:
  s'està intentant sobreescriure «/usr/share/appdata/gnome-
  terminal.appdata.xml», que també està en el paquet gnome-terminal-data
  3.12.3-0ubuntu1~trusty1

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  cada vez que se inicia ubuntu me sale la ventana de reportar el bug

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: gnome-terminal 3.16.2-1ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-43-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Tue Jan 12 15:07:09 2016
  DuplicateSignature: package:gnome-terminal:3.16.2-1ubuntu4:s'està intentant 
sobreescriure «/usr/share/appdata/gnome-terminal.appdata.xml», que també està 
en el paquet gnome-terminal-data 3.12.3-0ubuntu1~trusty1
  ErrorMessage: s'està intentant sobreescriure 
«/usr/share/appdata/gnome-terminal.appdata.xml», que també està en el paquet 
gnome-terminal-data 3.12.3-0ubuntu1~trusty1
  InstallationDate: Installed on 2015-09-24 (114 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: gnome-terminal
  Title: package gnome-terminal 3.16.2-1ubuntu4 failed to install/upgrade: 
s'està intentant sobreescriure «/usr/share/appdata/gnome-terminal.appdata.xml», 
que també està en el paquet gnome-terminal-data 3.12.3-0ubuntu1~trusty1
  UpgradeStatus: Upgraded to wily on 2016-01-12 (4 days ago)

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

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

[Desktop-packages] [Bug 1699758] Re: lost desk top icons

[Launchpad Bug Tracker]

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

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

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

Title:
  lost desk top icons

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  I have installed 11.04 Unity but while tweaking with Compiz Sett  I lost all 
desktop icons and dont even see APP menu at top of page the only thing i have 
is docky. I tryed nautilus -k; killall gnome-panel in terminal and got  ~$ 
nautilus -k; killall gnome-panel
  Could not parse arguments: Unknown option -k
  gnome-panel: no process found
   Any ideas??

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

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

[Desktop-packages] [Bug 1481835]

[Vasyĺ V . Vercynśkyj]

(In reply to Marcin from comment #30)
> Do you wait until this bug can legally buy a beer?! It is already 8 years
> old...

++ :)

6.1.5.2 still reproduces

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

Title:
  [UPSTREAM] Unable to group raster image(s) with drawing object(s)

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
 1. Create new document in LibreOffice Writer
 2. put rester images into document and put on images some drawing objects 
(arrows, other shapes), text. 
 3. try to group images with drawing objects.

  Expected behaviour:
 User can select and group image(s) with drawing object(s)

  Actual behaviour:
 User can not select and group image(s) with drawing object(s)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice 1:3.5.7-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-61.100~precise1-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  Date: Wed Aug  5 18:59:59 2015
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1481835/+subscriptions

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

[Desktop-packages] [Bug 1796979] Re: Intermittently can't connect to the server

[Bug Watch Updater]

** Changed in: firefox
   Status: New => Invalid

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

Title:
  Intermittently can't connect to the server

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

Bug description:
  Intermittently while browsing old and new sites, I run into a Server
  Not Found, "Hmm. We’re having trouble finding that site.", "We can’t
  connect to the server" page. To workaround I will often hold down the
  enter key to rapidly re-attempt to get to the page or close the tab,
  try again, and repeat until I get through. The latter is successful
  much more often than the former.

  Running in a new Firefox profile and in safe mode seems to make no
  difference.

  I had mistakenly made a submission to launchpad without running
  ubuntu-bug firefox. This is the submission using ubuntu-bug. The old
  submission is here: https://bugs.launchpad.net/bugs/1792402

  Linux Mint 18.3 Cinnamon

  apt-cache policy firefox
  firefox:
Installed: 63.0~b13+build1-0ubuntu0.16.04.1

  ProblemType: Bug
  DistroRelease: Linux 18.3
  Package: firefox 63.0~b13+build1-0ubuntu0.16.04.1 [modified: 
usr/lib/firefox/browser/defaults/preferences/vendor-firefox.js 
usr/lib/firefox/distribution/distribution.ini] [origin: 
LP-PPA-mozillateam-firefox-next]
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rex3357 F pulseaudio
  BuildID: 20181009094547
  Channel: beta
  CurrentDesktop: X-Cinnamon
  Date: Tue Oct  9 15:54:39 2018
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePlugins: Shockwave Flash - 
/usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin)
  DefaultProfilePrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
   prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-12 (635 days ago)
  InstallationMedia: Linux Mint 17.2 "Rafaela" - Release amd64 20150627
  IpRoute:
   default via 192.168.103.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.103.0/24 dev wlan0  proto kernel  scope link  src 192.168.103.222  
metric 600
  MostRecentCrashID: bp-392336ee-2be7-4d6e-89e0-e40350180301
  Profile0BrokenPermissions:
   browser-extension-data/ublo...@raymondhill.net/storage.js.corrupt (0o600, 
wrong owner)
   extension-settings.json.corrupt (0o600, wrong owner)
   saved-telemetry-pings/ba50588c-e150-45ec-9d22-916c98101815 (0o600, wrong 
owner)
   saved-telemetry-pings/f50808ab-da4a-421b-8acd-2795287134d8 (0o600, wrong 
owner)
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0Plugins: Shockwave Flash - 
/usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin)
  Profile0PrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
   prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 - LastVersion=62.0/20180911150120 (Out of date)
   Profile1 (Default) - LastVersion=63.0/20181009094547 (In use)
  RelatedPackageVersions: adobe-flashplugin 1:20181009.1-0ubuntu0.16.04.1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs: bp-392336ee-2be7-4d6e-89e0-e40350180301
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1B
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 165A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 10.31
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1B:bd10/05/2011:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr058D11244620001620100:rvnHewlett-Packard:rn165A:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 058D11244620001620100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications 

[Desktop-packages] [Bug 1796979]

[Rex]

No worries, Michal. Thank you for your help diagnosing to this level.
I'm rolling along just fine with WINS removed from my nsswitch.conf and
am happy to have helped reach a conclusion on this bug.

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

Title:
  Intermittently can't connect to the server

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

Bug description:
  Intermittently while browsing old and new sites, I run into a Server
  Not Found, "Hmm. We’re having trouble finding that site.", "We can’t
  connect to the server" page. To workaround I will often hold down the
  enter key to rapidly re-attempt to get to the page or close the tab,
  try again, and repeat until I get through. The latter is successful
  much more often than the former.

  Running in a new Firefox profile and in safe mode seems to make no
  difference.

  I had mistakenly made a submission to launchpad without running
  ubuntu-bug firefox. This is the submission using ubuntu-bug. The old
  submission is here: https://bugs.launchpad.net/bugs/1792402

  Linux Mint 18.3 Cinnamon

  apt-cache policy firefox
  firefox:
Installed: 63.0~b13+build1-0ubuntu0.16.04.1

  ProblemType: Bug
  DistroRelease: Linux 18.3
  Package: firefox 63.0~b13+build1-0ubuntu0.16.04.1 [modified: 
usr/lib/firefox/browser/defaults/preferences/vendor-firefox.js 
usr/lib/firefox/distribution/distribution.ini] [origin: 
LP-PPA-mozillateam-firefox-next]
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rex3357 F pulseaudio
  BuildID: 20181009094547
  Channel: beta
  CurrentDesktop: X-Cinnamon
  Date: Tue Oct  9 15:54:39 2018
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePlugins: Shockwave Flash - 
/usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin)
  DefaultProfilePrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
   prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-12 (635 days ago)
  InstallationMedia: Linux Mint 17.2 "Rafaela" - Release amd64 20150627
  IpRoute:
   default via 192.168.103.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.103.0/24 dev wlan0  proto kernel  scope link  src 192.168.103.222  
metric 600
  MostRecentCrashID: bp-392336ee-2be7-4d6e-89e0-e40350180301
  Profile0BrokenPermissions:
   browser-extension-data/ublo...@raymondhill.net/storage.js.corrupt (0o600, 
wrong owner)
   extension-settings.json.corrupt (0o600, wrong owner)
   saved-telemetry-pings/ba50588c-e150-45ec-9d22-916c98101815 (0o600, wrong 
owner)
   saved-telemetry-pings/f50808ab-da4a-421b-8acd-2795287134d8 (0o600, wrong 
owner)
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0Plugins: Shockwave Flash - 
/usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin)
  Profile0PrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
   prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 - LastVersion=62.0/20180911150120 (Out of date)
   Profile1 (Default) - LastVersion=63.0/20181009094547 (In use)
  RelatedPackageVersions: adobe-flashplugin 1:20181009.1-0ubuntu0.16.04.1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs: bp-392336ee-2be7-4d6e-89e0-e40350180301
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1B
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 165A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 10.31
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1B:bd10/05/2011:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr058D11244620001620100:rvnHewlett-Packard:rn165A:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  

[Desktop-packages] [Bug 1796979]

[Michal-novotny]

I'm closing this as WFM because the bug isn't limited only to firefox.
Any application that calls getaddrinfo quickly enough will trigger it.

Rex, I didn't find anything strange in any config file you've posted. I
tried to reproduce it on Fedora and Valentin tried it on Ubuntu, but we
were unable to reproduce it. If you would like to track the bug down to
nsswitch level, I would recommend to run the python test with rr (https
://rr-project.org/) and if it's reproducible using rr, then you should
be able to debug it after installing appropriate debug packages.

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

Title:
  Intermittently can't connect to the server

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

Bug description:
  Intermittently while browsing old and new sites, I run into a Server
  Not Found, "Hmm. We’re having trouble finding that site.", "We can’t
  connect to the server" page. To workaround I will often hold down the
  enter key to rapidly re-attempt to get to the page or close the tab,
  try again, and repeat until I get through. The latter is successful
  much more often than the former.

  Running in a new Firefox profile and in safe mode seems to make no
  difference.

  I had mistakenly made a submission to launchpad without running
  ubuntu-bug firefox. This is the submission using ubuntu-bug. The old
  submission is here: https://bugs.launchpad.net/bugs/1792402

  Linux Mint 18.3 Cinnamon

  apt-cache policy firefox
  firefox:
Installed: 63.0~b13+build1-0ubuntu0.16.04.1

  ProblemType: Bug
  DistroRelease: Linux 18.3
  Package: firefox 63.0~b13+build1-0ubuntu0.16.04.1 [modified: 
usr/lib/firefox/browser/defaults/preferences/vendor-firefox.js 
usr/lib/firefox/distribution/distribution.ini] [origin: 
LP-PPA-mozillateam-firefox-next]
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rex3357 F pulseaudio
  BuildID: 20181009094547
  Channel: beta
  CurrentDesktop: X-Cinnamon
  Date: Tue Oct  9 15:54:39 2018
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePlugins: Shockwave Flash - 
/usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin)
  DefaultProfilePrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
   prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-12 (635 days ago)
  InstallationMedia: Linux Mint 17.2 "Rafaela" - Release amd64 20150627
  IpRoute:
   default via 192.168.103.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.103.0/24 dev wlan0  proto kernel  scope link  src 192.168.103.222  
metric 600
  MostRecentCrashID: bp-392336ee-2be7-4d6e-89e0-e40350180301
  Profile0BrokenPermissions:
   browser-extension-data/ublo...@raymondhill.net/storage.js.corrupt (0o600, 
wrong owner)
   extension-settings.json.corrupt (0o600, wrong owner)
   saved-telemetry-pings/ba50588c-e150-45ec-9d22-916c98101815 (0o600, wrong 
owner)
   saved-telemetry-pings/f50808ab-da4a-421b-8acd-2795287134d8 (0o600, wrong 
owner)
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0Plugins: Shockwave Flash - 
/usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin)
  Profile0PrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
   prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 - LastVersion=62.0/20180911150120 (Out of date)
   Profile1 (Default) - LastVersion=63.0/20181009094547 (In use)
  RelatedPackageVersions: adobe-flashplugin 1:20181009.1-0ubuntu0.16.04.1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs: bp-392336ee-2be7-4d6e-89e0-e40350180301
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1B
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 165A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 10.31
  dmi.chassis.asset.tag: Chassis Asset Tag
  

[Desktop-packages] [Bug 97253] Re: On reconnects, xchat's net-monitor plugin doesn't reuse SSL, the port number or server password

[Bug Watch Updater]

** Changed in: xchat-gnome
   Status: Confirmed => Won't Fix

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

Title:
  On reconnects, xchat's net-monitor plugin doesn't reuse SSL, the port
  number or server password

Status in XChat-GNOME:
  Won't Fix
Status in xchat-gnome package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: xchat-gnome

  I have feisty's xchat configured with a server (the canonical server)
  on a non-default port number and using ssl, and set to autoconnect at
  startup.  When I start xchat it connects successfully.  However, if
  the connection drops, it tries to reconnect on the default port
  number, not the configured port.

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

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

[Desktop-packages] [Bug 1815339]

[Michael-vrhel]

OK.  Taking a look at this now.

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

Title:
  Printer stopped printing paper size 4"x6" after update ghostscript to
  9.26

Status in GS-GPL:
  Fix Released
Status in ghostscript package in Ubuntu:
  Fix Released
Status in ghostscript source package in Trusty:
  Fix Released
Status in ghostscript source package in Xenial:
  Fix Released
Status in ghostscript source package in Bionic:
  Fix Released
Status in ghostscript source package in Cosmic:
  Fix Released
Status in ghostscript source package in Disco:
  Fix Released

Bug description:
  
  I have an issue with Ghostscript and printing.
  I use Gutenprint for my Canon MG5440, and I cannot print a photo 4"x6" (or 
6"x4"), it does not print anything, however I still able to print A4 paper size.
  I use Ubuntu 18.04 and Gutenprint 5.3.1.

  The printing fail with message:
  
  [Job 143] Start rendering...
  [Job 143] Processing page 1...
  [Job 143]  Unable to open the initial device, quitting.
  [Job 143] Rendering completed
  ...
  [Job 143] PID 24869 (/usr/lib/cups/filter/gstoraster) stopped with status 1.
  ...
  [Job 143] printer-state-message="Filter failed"
  [Job 143] printer-state-reasons=none

  The message "Unable to open the initial device, quitting" comes from
  Ghostscript.

  
  When I downgrade Ghostscript to 9.22, 
  I am again able to print 4"x6" paper size.

  To downgrade: apt install ghostscript=9.22~dfsg+1-0ubuntu1
  libgs9=9.22~dfsg+1-0ubuntu1 libgs9-common=9.22~dfsg+1-0ubuntu1

  I found similar issue for HP printer at Debian https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=908205

  
  System info:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ghostscript:
Installed: 9.26~dfsg+0-0ubuntu0.18.04.4
Candidate: 9.26~dfsg+0-0ubuntu0.18.04.4
Versions:
   *** 9.26~dfsg+0-0ubuntu0.18.04.4 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   9.22~dfsg+1-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  cups:
Installed: 2.2.7-1ubuntu2.3
Candidate: 2.2.7-1ubuntu2.3
Versions:
   *** 2.2.7-1ubuntu2.3 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.2.7-1ubuntu2.2 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   2.2.7-1ubuntu2 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/gs-gpl/+bug/1815339/+subscriptions

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

[Desktop-packages] [Bug 1815339]

[Michael-vrhel]

OK.  I do see the blue background for the output with
-dcupsColorSpace=17 (RGBW colorspace ) using Mike Sweet's rasterview
program.

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

Title:
  Printer stopped printing paper size 4"x6" after update ghostscript to
  9.26

Status in GS-GPL:
  Fix Released
Status in ghostscript package in Ubuntu:
  Fix Released
Status in ghostscript source package in Trusty:
  Fix Released
Status in ghostscript source package in Xenial:
  Fix Released
Status in ghostscript source package in Bionic:
  Fix Released
Status in ghostscript source package in Cosmic:
  Fix Released
Status in ghostscript source package in Disco:
  Fix Released

Bug description:
  
  I have an issue with Ghostscript and printing.
  I use Gutenprint for my Canon MG5440, and I cannot print a photo 4"x6" (or 
6"x4"), it does not print anything, however I still able to print A4 paper size.
  I use Ubuntu 18.04 and Gutenprint 5.3.1.

  The printing fail with message:
  
  [Job 143] Start rendering...
  [Job 143] Processing page 1...
  [Job 143]  Unable to open the initial device, quitting.
  [Job 143] Rendering completed
  ...
  [Job 143] PID 24869 (/usr/lib/cups/filter/gstoraster) stopped with status 1.
  ...
  [Job 143] printer-state-message="Filter failed"
  [Job 143] printer-state-reasons=none

  The message "Unable to open the initial device, quitting" comes from
  Ghostscript.

  
  When I downgrade Ghostscript to 9.22, 
  I am again able to print 4"x6" paper size.

  To downgrade: apt install ghostscript=9.22~dfsg+1-0ubuntu1
  libgs9=9.22~dfsg+1-0ubuntu1 libgs9-common=9.22~dfsg+1-0ubuntu1

  I found similar issue for HP printer at Debian https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=908205

  
  System info:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ghostscript:
Installed: 9.26~dfsg+0-0ubuntu0.18.04.4
Candidate: 9.26~dfsg+0-0ubuntu0.18.04.4
Versions:
   *** 9.26~dfsg+0-0ubuntu0.18.04.4 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   9.22~dfsg+1-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  cups:
Installed: 2.2.7-1ubuntu2.3
Candidate: 2.2.7-1ubuntu2.3
Versions:
   *** 2.2.7-1ubuntu2.3 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.2.7-1ubuntu2.2 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   2.2.7-1ubuntu2 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/gs-gpl/+bug/1815339/+subscriptions

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

[Desktop-packages] [Bug 1815339]

[Till Kamppeter]

The Ubuntu security team has applied the fix for this bug to the
GhostScript 9.26 which they have issued as security update to several
Ubuntu versions.

Unfortunately, this fix has caused a regression. It was reported here:

https://bugs.launchpad.net/bugs/1817308

The user tells that all pages come out with a blue background now.

I will ask the user for further information.

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

Title:
  Printer stopped printing paper size 4"x6" after update ghostscript to
  9.26

Status in GS-GPL:
  Fix Released
Status in ghostscript package in Ubuntu:
  Fix Released
Status in ghostscript source package in Trusty:
  Fix Released
Status in ghostscript source package in Xenial:
  Fix Released
Status in ghostscript source package in Bionic:
  Fix Released
Status in ghostscript source package in Cosmic:
  Fix Released
Status in ghostscript source package in Disco:
  Fix Released

Bug description:
  
  I have an issue with Ghostscript and printing.
  I use Gutenprint for my Canon MG5440, and I cannot print a photo 4"x6" (or 
6"x4"), it does not print anything, however I still able to print A4 paper size.
  I use Ubuntu 18.04 and Gutenprint 5.3.1.

  The printing fail with message:
  
  [Job 143] Start rendering...
  [Job 143] Processing page 1...
  [Job 143]  Unable to open the initial device, quitting.
  [Job 143] Rendering completed
  ...
  [Job 143] PID 24869 (/usr/lib/cups/filter/gstoraster) stopped with status 1.
  ...
  [Job 143] printer-state-message="Filter failed"
  [Job 143] printer-state-reasons=none

  The message "Unable to open the initial device, quitting" comes from
  Ghostscript.

  
  When I downgrade Ghostscript to 9.22, 
  I am again able to print 4"x6" paper size.

  To downgrade: apt install ghostscript=9.22~dfsg+1-0ubuntu1
  libgs9=9.22~dfsg+1-0ubuntu1 libgs9-common=9.22~dfsg+1-0ubuntu1

  I found similar issue for HP printer at Debian https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=908205

  
  System info:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ghostscript:
Installed: 9.26~dfsg+0-0ubuntu0.18.04.4
Candidate: 9.26~dfsg+0-0ubuntu0.18.04.4
Versions:
   *** 9.26~dfsg+0-0ubuntu0.18.04.4 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   9.22~dfsg+1-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  cups:
Installed: 2.2.7-1ubuntu2.3
Candidate: 2.2.7-1ubuntu2.3
Versions:
   *** 2.2.7-1ubuntu2.3 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.2.7-1ubuntu2.2 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   2.2.7-1ubuntu2 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/gs-gpl/+bug/1815339/+subscriptions

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

[Desktop-packages] [Bug 1815339]

[Michael-vrhel]

The issue with the RGBW color space should be resolved with

http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=1bc4205dca71ca075af6ca95aa53a33f5a724586

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

Title:
  Printer stopped printing paper size 4"x6" after update ghostscript to
  9.26

Status in GS-GPL:
  Fix Released
Status in ghostscript package in Ubuntu:
  Fix Released
Status in ghostscript source package in Trusty:
  Fix Released
Status in ghostscript source package in Xenial:
  Fix Released
Status in ghostscript source package in Bionic:
  Fix Released
Status in ghostscript source package in Cosmic:
  Fix Released
Status in ghostscript source package in Disco:
  Fix Released

Bug description:
  
  I have an issue with Ghostscript and printing.
  I use Gutenprint for my Canon MG5440, and I cannot print a photo 4"x6" (or 
6"x4"), it does not print anything, however I still able to print A4 paper size.
  I use Ubuntu 18.04 and Gutenprint 5.3.1.

  The printing fail with message:
  
  [Job 143] Start rendering...
  [Job 143] Processing page 1...
  [Job 143]  Unable to open the initial device, quitting.
  [Job 143] Rendering completed
  ...
  [Job 143] PID 24869 (/usr/lib/cups/filter/gstoraster) stopped with status 1.
  ...
  [Job 143] printer-state-message="Filter failed"
  [Job 143] printer-state-reasons=none

  The message "Unable to open the initial device, quitting" comes from
  Ghostscript.

  
  When I downgrade Ghostscript to 9.22, 
  I am again able to print 4"x6" paper size.

  To downgrade: apt install ghostscript=9.22~dfsg+1-0ubuntu1
  libgs9=9.22~dfsg+1-0ubuntu1 libgs9-common=9.22~dfsg+1-0ubuntu1

  I found similar issue for HP printer at Debian https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=908205

  
  System info:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ghostscript:
Installed: 9.26~dfsg+0-0ubuntu0.18.04.4
Candidate: 9.26~dfsg+0-0ubuntu0.18.04.4
Versions:
   *** 9.26~dfsg+0-0ubuntu0.18.04.4 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   9.22~dfsg+1-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  cups:
Installed: 2.2.7-1ubuntu2.3
Candidate: 2.2.7-1ubuntu2.3
Versions:
   *** 2.2.7-1ubuntu2.3 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.2.7-1ubuntu2.2 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   2.2.7-1ubuntu2 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/gs-gpl/+bug/1815339/+subscriptions

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

[Desktop-packages] [Bug 1817334] Re: dock disappears after apt dist-upgrade, needed to install gnome-shell-extension-dashtodock by hand, restart gnome-shell, and enable extension in tweaks

[Launchpad Bug Tracker]

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

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: New => Confirmed

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

Title:
  dock disappears after apt dist-upgrade, needed to install gnome-shell-
  extension-dashtodock by hand, restart gnome-shell, and enable
  extension in tweaks

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

Bug description:
  I did an apt dist-upgrade and got a message telling me that gnome-
  shell had crashed and asking if I wanted to report it. I figured it
  was just something funky about the upgrade so didn't bother. Instead,
  I restarted my machine just to get everything back into a sane state.
  Upon logging in after doing that, I had no dock.

  I dug around to try to figure out what was going on, and finally
  stumbled upon the description for "Ubuntu Dock" in gnome-tweaks, which
  told me to install dash to dock.

  So I installed that with apt and then restarted gnome-shell and then
  restarted gnome-tweaks and then enabled dash to dock and finally my
  dock was back.

  This is, shall we say, not an ideal upgrade experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-ubuntu-dock 64ubuntu3
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 22 10:05:57 2019
  InstallationDate: Installed on 2019-01-02 (51 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to disco on 2019-01-21 (31 days ago)

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

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

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[John Hart]

>From https://launchpad.net/~lafricain79
For Ubuntu 16.04:
sudo apt install ghostscript=9.18~dfsg~0-0ubuntu2 libgs9=9.18~dfsg~0-0ubuntu2 
libgs9-common=9.18~dfsg~0-0ubuntu2

This corrected for me, thanks

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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

[Desktop-packages] [Bug 1817335] Re: Freeze when changing the volume with the mouse wheel

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

Title:
  Freeze when changing the volume with the mouse wheel

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  = Problem =
  Since today 2019-02-22 after upgrade:

  * Ubuntu (Gnome) desktop freeze when changing the volume with mouse wheel, no 
keyboard/mouse input possible, hard reboot or restart gdm over ssh required
  * (possibly related?) gnome-shell extensions {system-monitor, SomaFM internet 
radio} not working anymore

  = System = 
  lsb_release -rd
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  apt-cache policy gnome-shell
  gnome-shell:
Installiert:   3.31.90-1ubuntu1
Installationskandidat: 3.31.90-1ubuntu1
Versionstabelle:
   *** 3.31.90-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu disco-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.30.2-2ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu disco/main amd64 Packages

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

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

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[John Hart]

I have the problem also, Have turned off the printer, then on several time, 
have rebooted computer several times, I have dumped printer and re-added it, 
still getting the blue pages.  I suspect I have the same BUG as all those 
reporting before me.
Next question is who fixes it and when will it be fixed?

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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

[Desktop-packages] [Bug 1817269] Re: New Desktop Icons Overlap Existing Icons

[Bryce]

So to resolve the issue, the default package (which is deprecated) must be 
manually changed?
Should I simply install gnome-shell-extensions to resolve it? I'm not clear on 
what you mean, or why the issue is invalid.

As installed from the disc, the issue is present so I'm unsure what I'm
supposed to do, or why this isn't considered a bug.

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

Title:
  New Desktop Icons Overlap Existing Icons

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Behaviour observed in Ubuntu Cosmic 18.10
  gnome-shell 3.30.2-0ubuntu1.18.10.1 from cosmic-proposed

  The expected behaviour is for new icons to populate unoccupied cells
  below the column, or occupy the first cell of a new column, or
  displace other icons to maintain alpha-numeric organization.

  The unexpected bevaviour is observed when desktop icons are created,
  such as when disk or network drives are mounted or files are saved to
  the desktop, they overlap the existing icons. They do not seem to take
  any specific position through a column, but they will always be within
  a column (assuming as such, as I always have 'Keep Aligned' enabled).

  An image depicting a series of screenshots is attached to illustrate
  the observed behaviour. From left to right, the images depict: first,
  a single column of organized, aligned icons occupy the desktop;
  second, a network drive is mounted using Files, overlapping (and
  aligned with) the uppermost icon; third, a second network drive is
  mounted, overlapping (and aligned with) the initial and second icon in
  that placement; fourth, an optical medium is mounted, and occupies a
  space two 'cells' below the original column; fifth, the desktop icons
  are arranged using 'Organize Desktop by Name'; sixth, an appimage is
  moved to the desktop using Files 'Move to...' function, overlapping
  half (and not aligned with) the top-most icon; seventh, a docx file is
  moved to the desktop using the same method, overlapping (and aligned
  with) the icon in the second cell of the column; finally, the desktop
  is organized again using the same method.

  Appendum on unexpected behaviour: after the intial creation of this
  bug-report, a third file was moved to the desktop using Files,
  occupying the empty cell in the first column, after it was seen that
  manually moving an icon into that cell was not preserved by 'Organize
  Desktop by Name'. After moving the file to the desktop, using the
  organize function moves that file into the second column, emptying the
  bottom cell in the first column.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.2-0ubuntu1.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 22 00:40:39 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-12-30 (54 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  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/nautilus/+bug/1817269/+subscriptions

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

[Desktop-packages] [Bug 1817381] [NEW] After the most recent software updates to xubuntu, my printer prints normal pages (from a word processor for instance) with a blue background.

[TJ Schares]

Public bug reported:

This has happened to both of my computers running xubuntu.  My first
computer, I updated yesterday.  The second computer did not exhibit the
problem this morning.  Once I updated the software with Software
Updater, it acquired the same issue.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.3
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CupsErrorLog:
 W [22/Feb/2019:16:38:45 -0600] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Deskjet-3050-J610-series-Gray..\' already exists
 W [22/Feb/2019:16:38:45 -0600] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Deskjet-3050-J610-series-RGB..\' already exists
CurrentDesktop: XFCE
Date: Fri Feb 22 17:00:53 2019
InstallationDate: Installed on 2018-02-05 (382 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
Lpstat:
 device for HP-Deskjet-3050-J610-series: 
hp:/net/Deskjet_3050_J610_series?hostname=HPFDBBD9.local
 device for HP-Officejet-6600: hp:/net/Officejet_6600?hostname=HP2D4AAF.local
 device for Officejet_6600_2D4AAF_: ipp://HP2D4AAF.local:631/ipp/printer
 device for Roger-Router-Fax: roger-cups:/
MachineType: Hewlett-Packard HP 15 TS Notebook PC
Papersize: letter
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Officejet_6600_2D4AAF_.ppd', 
'/etc/cups/ppd/HP-Deskjet-3050-J610-series.ppd', 
'/etc/cups/ppd/HP-Officejet-6600.ppd', '/etc/cups/ppd/Roger-Router-Fax.ppd'] 
failed with exit code 2: grep: /etc/cups/ppd/Officejet_6600_2D4AAF_.ppd: 
Permission denied
 grep: /etc/cups/ppd/HP-Deskjet-3050-J610-series.ppd: Permission denied
 grep: /etc/cups/ppd/HP-Officejet-6600.ppd: Permission denied
 grep: /etc/cups/ppd/Roger-Router-Fax.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: Upgraded to bionic on 2018-05-04 (294 days ago)
dmi.bios.date: 11/14/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.33
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2211
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 86.46
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd11/14/2014:svnHewlett-Packard:pnHP15TSNotebookPC:pvr0972110021405F0620180:rvnHewlett-Packard:rn2211:rvr86.46:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP 15 TS Notebook PC
dmi.product.version: 0972110021405F0620180
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apparmor apport-bug bionic

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

Title:
  After the most recent software updates to xubuntu, my printer prints
  normal pages (from a word processor for instance) with a blue
  background.

Status in cups package in Ubuntu:
  New

Bug description:
  This has happened to both of my computers running xubuntu.  My first
  computer, I updated yesterday.  The second computer did not exhibit
  the problem this morning.  Once I updated the software with Software
  Updater, it acquired the same issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.3
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CupsErrorLog:
   W [22/Feb/2019:16:38:45 -0600] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Deskjet-3050-J610-series-Gray..\' already exists
   W [22/Feb/2019:16:38:45 -0600] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Deskjet-3050-J610-series-RGB..\' already exists
  CurrentDesktop: XFCE
  Date: Fri Feb 22 17:00:53 2019
  InstallationDate: Installed on 2018-02-05 (382 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lpstat:
   device for HP-Deskjet-3050-J610-series: 
hp:/net/Deskjet_3050_J610_series?hostname=HPFDBBD9.local
   device for HP-Officejet-6600: hp:/net/Officejet_6600?hostname=HP2D4AAF.local
   device for Officejet_6600_2D4AAF_: ipp://HP2D4AAF.local:631/ipp/printer
   device for Roger-Router-Fax: roger-cups:/
  MachineType: Hewlett-Packard HP 15 TS Notebook PC
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Officejet_6600_2D4AAF_.ppd', 
'/etc/cups/ppd/HP-Deskjet-3050-J610-series.ppd', 
'/etc/cups/ppd/HP-Officejet-6600.ppd', '/etc/cups/ppd/Roger-Router-Fax.ppd'] 
failed with exit code 2: grep: 

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[William Seward]

Having the same blue background problem with an HP Deskjet 1510, on
Linux Mint 17.3. Could not get Ghostscript to downgrade, but the
grayscale works for now. Most of my printing is b/w, but hope things get
resolved soon.

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[Sim Inthavong]

I have an HP Officejet 8600 Pro, running Ubuntu 18.04.2 LTS, with Kernel
4.15.0-45 (I do believe that 18.04.2 LTS is suppose to install 4.18, but
I think I read somewhere that for anyone running VirtualBox the new
Kernel won't install? I could be wrong on this, but if am correct I
assume at some point Canonical will correct this as well. At first I
thought it was a driver (HPLIP 3.19.1) issue, so I uninstalled and
reinstalled. Then I loaded up Windows i VirtualBox and did a print from
there, no issue at all. And I also attempted to diagnose the issue on
the printer directly and there didn't seem to be any issue either. I
even did a factory reset on the printer. Then when I came across this
forum, just about everyone seem to mention that the Ghostscript update
seem to be the culprit. So I downloaded the source for Ghostscript 9.26,
compiled and installed it. The issue now seems resolved! So there is no
need to revert to an older version of Ghostscript, just compile and
install it. Canonical will probably correct the issue in a future update
as well.

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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

[Desktop-packages] [Bug 1817346] Re: Printing blue pages after upgrading ghostscript to 9.26~dfsg+0-0ubuntu0.16.04.5

[Launchpad Bug Tracker]

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

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

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

Title:
  Printing blue pages after upgrading ghostscript to
  9.26~dfsg+0-0ubuntu0.16.04.5

Status in ghostscript package in Ubuntu:
  Confirmed

Bug description:
  Various machines running Ubuntu 16-04 are printing blue background
  pages after upgrading 9.26~dfsg+0-0ubuntu0.16.04.4 to
  9.26~dfsg+0-0ubuntu0.16.04.5 in the automatic updates. The issue is
  bigger because, after solving by manually installing the 16.04.4
  version, any upgrade in hplip or automatic system upgrades reinstall
  the lastest version.

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

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

[Desktop-packages] [Bug 1802569] Re: RM openssl1.0 from Ubuntu

[Steve Langasek]

Removing packages:
freerdp 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco
freerdp-x11 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in 
disco amd64
freerdp-x11 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in 
disco arm64
freerdp-x11 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in 
disco armhf
freerdp-x11 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in 
disco i386
freerdp-x11 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in 
disco ppc64el
freerdp-x11 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in 
disco s390x
freerdp-x11-dbgsym 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 
in disco amd64
freerdp-x11-dbgsym 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 
in disco arm64
freerdp-x11-dbgsym 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 
in disco armhf
freerdp-x11-dbgsym 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 
in disco i386
freerdp-x11-dbgsym 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 
in disco ppc64el
freerdp-x11-dbgsym 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 
in disco s390x
libfreerdp-cache1.1 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 
in disco amd64
libfreerdp-cache1.1 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 
in disco arm64
libfreerdp-cache1.1 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 
in disco armhf
libfreerdp-cache1.1 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 
in disco i386
libfreerdp-cache1.1 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 
in disco ppc64el
libfreerdp-cache1.1 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 
in disco s390x
libfreerdp-cache1.1-dbgsym 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco amd64
libfreerdp-cache1.1-dbgsym 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco arm64
libfreerdp-cache1.1-dbgsym 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco armhf
libfreerdp-cache1.1-dbgsym 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco i386
libfreerdp-cache1.1-dbgsym 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco ppc64el
libfreerdp-cache1.1-dbgsym 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco s390x
libfreerdp-client1.1 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco amd64
libfreerdp-client1.1 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco arm64
libfreerdp-client1.1 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco armhf
libfreerdp-client1.1 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco i386
libfreerdp-client1.1 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco ppc64el
libfreerdp-client1.1 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco s390x
libfreerdp-client1.1-dbgsym 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco amd64
libfreerdp-client1.1-dbgsym 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco arm64
libfreerdp-client1.1-dbgsym 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco armhf
libfreerdp-client1.1-dbgsym 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco i386
libfreerdp-client1.1-dbgsym 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco ppc64el
libfreerdp-client1.1-dbgsym 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco s390x
libfreerdp-codec1.1 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 
in disco amd64
libfreerdp-codec1.1 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 
in disco arm64
libfreerdp-codec1.1 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 
in disco armhf
libfreerdp-codec1.1 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 
in disco i386
libfreerdp-codec1.1 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 
in disco ppc64el
libfreerdp-codec1.1 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 
in disco s390x
libfreerdp-codec1.1-dbgsym 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco amd64
libfreerdp-codec1.1-dbgsym 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco arm64
libfreerdp-codec1.1-dbgsym 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco armhf
libfreerdp-codec1.1-dbgsym 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco i386
libfreerdp-codec1.1-dbgsym 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco ppc64el
libfreerdp-codec1.1-dbgsym 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco s390x
libfreerdp-common1.1.0 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco amd64
libfreerdp-common1.1.0 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 in disco arm64
 

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[peter]

what amazing support from you folk;

I downgraded as L'Africain described and put the hold as Matthew said
and now it prints as it should.

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[Matthew T. Sano]

After you reinstall the older version of ghostscript, you may want to
prevent them from having their updates from being automatically picked
up by using:

sudo apt-mark hold 

For example:
sudo apt-mark hold ghostscript=9.22~dfsg+1-0ubuntu1

If you have a different package manager change apt to correspond with
it.

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[L'Africain]

For Ubuntu 16.04:
sudo apt install ghostscript=9.18~dfsg~0-0ubuntu2 libgs9=9.18~dfsg~0-0ubuntu2 
libgs9-common=9.18~dfsg~0-0ubuntu2
And Ubuntu 18.04:
sudo apt install ghostscript=9.22~dfsg+1-0ubuntu1 libgs9=9.22~dfsg+1-0ubuntu1 
libgs9-common=9.22~dfsg+1-0ubuntu1

For 18.04, it is 22 and not 25.

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[Frank]

(Original Poster)

I should mention that - like Brian above - I have neither web services
nor auto-update active on my printer.

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[Kelsey Duerksen]

Same here. I'm running Kubuntu 18.04 and printing on an HP CP1025nw (old
printer). I tried the command as well to revert to the old ghostscript
but it gave me the same error Brian Foster got.

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[peter]

It's happened to me too ... ghostscript update yesterday evening and now blue 
backgrounds.

Using Ubuntu 18.04 with HP Deskjet 3720 ...

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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

[Desktop-packages] [Bug 1817216] Re: Xorg freeze

[Ramiro Caamano]

** Description changed:

- Hi just wanted to report in addition I had two webpages open no other 
programs running. 
+ Hi just wanted to report in addition I had two webpages open no other 
programs running.
  The webpages were youtube and msn when the page froze - the cursor/mouse did 
not respond and the keyboard was locked.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
- Package: xorg 1:7.7+19ubuntu7.1
- ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
- Uname: Linux 4.18.0-15-generic x86_64
- ApportVersion: 2.20.9-0ubuntu7.5
- Architecture: amd64
- BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
- CompositorRunning: None
- CurrentDesktop: ubuntu:GNOME
- Date: Thu Feb 21 20:58:48 2019
- DistUpgraded: Fresh install
- DistroCodename: bionic
- DistroVariant: ubuntu
- GpuHangFrequency: This is the first time
- GraphicsCard:
-  NVIDIA Corporation GT218 [NVS 300] [10de:10d8] (rev a2) (prog-if 00 [VGA 
controller])
-Subsystem: Hewlett-Packard Company GT218 [NVS 300] [103c:0862]
- InstallationDate: Installed on 2019-02-20 (1 days ago)
- InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
- MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L
- ProcEnviron:
-  LANGUAGE=en_GB:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
- ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
- SourcePackage: xorg
- Symptom: display
- Title: Xorg freeze
- UpgradeStatus: No upgrade log present (probably fresh install)
- dmi.bios.date: 02/24/2010
- dmi.bios.vendor: Award Software International, Inc.
- dmi.bios.version: FG
- dmi.board.name: G31M-ES2L
- dmi.board.vendor: Gigabyte Technology Co., Ltd.
- dmi.board.version: x.x
- dmi.chassis.type: 3
- dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
- dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFG:bd02/24/2010:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-ES2L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
- dmi.product.name: G31M-ES2L
- dmi.sys.vendor: Gigabyte Technology Co., Ltd.
- version.compiz: compiz N/A
- version.libdrm2: libdrm2 2.4.95-1~18.04.1
- version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
- version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.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

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

Title:
  Xorg freeze

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Hi just wanted to report in addition I had two webpages open no other 
programs running.
  The webpages were youtube and msn when the page froze - the cursor/mouse did 
not respond and the keyboard was locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04

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

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

[Desktop-packages] [Bug 1817222] Re: [nouveau] Xorg freeze

[Ramiro Caamano]

** Description changed:

  Update 22/2/2019 Hi again , logged in to my computer today and noted the
  driver was not set to nvidia the selection option was on xorg driver and
  would not change this would revert after selection. Attempted changing
  driver as user and also as admin no effect.  Did a manual update via
  terminal of all drivers '34 approximately' and then software updater
  allowed the selection of nvidia display driver. I mention this as I
  posted yesterday that I had selected nvidia driver and found the same
  issue, based on today's finding this may have been factually incorrect
  and maybe the two crashes occurred while using xorg driver.
  
  21/2/2019
  I have selected the NVIDIA driver instead and can report the same problem - 
screen frozen one internet page open no other programs. Using Firefox as per 
original install, each time this freeze has occurred only when connected to 
wireless network and using the internet. So this is an update to the original 
logged error report.
  
  Have been using Ubuntu online/offline for occasional browsing or offline
  use since installation and no issues.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
- Package: xorg 1:7.7+19ubuntu7.1
- ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
- Uname: Linux 4.18.0-15-generic x86_64
- ApportVersion: 2.20.9-0ubuntu7.5
- Architecture: amd64
- BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
- CompositorRunning: None
- CurrentDesktop: ubuntu:GNOME
- Date: Thu Feb 21 21:49:33 2019
- DistUpgraded: Fresh install
- DistroCodename: bionic
- DistroVariant: ubuntu
- ExtraDebuggingInterest: No
- GpuHangFrequency: Very infrequently
- GraphicsCard:
-  NVIDIA Corporation GT218 [NVS 300] [10de:10d8] (rev a2) (prog-if 00 [VGA 
controller])
-    Subsystem: Hewlett-Packard Company GT218 [NVS 300] [103c:0862]
- InstallationDate: Installed on 2019-02-20 (1 days ago)
- InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
- MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L
- ProcEnviron:
-  LANGUAGE=en_GB:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
- ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
- SourcePackage: xorg
- Symptom: display
- Title: Xorg freeze
- UpgradeStatus: No upgrade log present (probably fresh install)
- dmi.bios.date: 02/24/2010
- dmi.bios.vendor: Award Software International, Inc.
- dmi.bios.version: FG
- dmi.board.name: G31M-ES2L
- dmi.board.vendor: Gigabyte Technology Co., Ltd.
- dmi.board.version: x.x
- dmi.chassis.type: 3
- dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
- dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFG:bd02/24/2010:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-ES2L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
- dmi.product.name: G31M-ES2L
- dmi.sys.vendor: Gigabyte Technology Co., Ltd.
- version.compiz: compiz N/A
- version.libdrm2: libdrm2 2.4.95-1~18.04.1
- version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
- version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.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

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

Title:
  [nouveau] Xorg freeze

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Update 22/2/2019 Hi again , logged in to my computer today and noted
  the driver was not set to nvidia the selection option was on xorg
  driver and would not change this would revert after selection.
  Attempted changing driver as user and also as admin no effect.  Did a
  manual update via terminal of all drivers '34 approximately' and then
  software updater  allowed the selection of nvidia display driver. I
  mention this as I posted yesterday that I had selected nvidia driver
  and found the same issue, based on today's finding this may have been
  factually incorrect and maybe the two crashes occurred while using
  xorg driver.

  21/2/2019
  I have selected the NVIDIA driver instead and can report the same problem - 
screen frozen one internet page open no other programs. Using Firefox as per 
original install, each time this freeze has occurred only when connected to 
wireless network and using the internet. So this is an update to the original 
logged error report.

  Have been using Ubuntu online/offline for occasional browsing or
  offline use since installation and no issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04

To manage notifications about this bug go to:

Re: [Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[Brian Foster]

Thanks for the tip!
When I just tried that I got:

# sudo apt install ghostscript=9.25~dfsg+1-0ubuntu1
libgs9=9.25~dfsg+1-0ubuntu1 libgs9-common=9.25~dfsg+1-0ubuntu1
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version '9.25~dfsg+1-0ubuntu1' for 'ghostscript' was not found
E: Version '9.25~dfsg+1-0ubuntu1' for 'libgs9' was not found
E: Version '9.25~dfsg+1-0ubuntu1' for 'libgs9-common' was not found
#

Obviously I need to configure(?) something, but am at a bit of a loss
as to what,
as I don't really know much about the Debian/Ubuntu packaging system.  (Any
tips or pointers?)

Fortunately, the "High Qualify Grayscale" CUPS workaround is Ok(-ish)
for now

cheers!
 -blf-

On Fri, 22 Feb 2019 at 18:20, Jarl <1817...@bugs.launchpad.net> wrote:
> I have downgraded to 9.25 using
> sudo apt install ghostscript=9.25~dfsg+1-0ubuntu1 libgs9=9.25~dfsg+1-0ubuntu1 
> libgs9-common=9.25~dfsg+1-0ubuntu1
>
> That solved the problem.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1817308
>
> Title:
>   GhostScript Update causes Blue Background
>
> Status in ghostscript package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
>   kernel 4.15.0-45-generic.
>
>   Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
>   was applied to two of my machines (One is an Intel and one is an AMD,
>   but both are kept fully updated) that share a networked HP OfficeJet
>   6700 Printer.
>
>   At some point following the update, I happened to print a document,
>   and ended up with a blue background on every page, even otherwise
>   blank second sides. This occured regardless of a variety of
>   originating applications I used, such as LibreOffice, various text
>   editors, and even the CUPS "print test page" option.
>
>   It took me a while to troubleshoot this on that first machine (trying
>   different apps, reinstalling CUPS and so forth) until I realized the
>   new ghostscript update was the issue and that (after trying to print
>   from the second machine) it was affecting both machines.
>
>   I should note that, using the "non-CUPS" appearance of the same
>   printer, no blue background is present, but of course this provides no
>   features like ink-level reporting, dual-sided printing, etc.
>
>   I "restored" the ghostscript stuff from the last Timeshift backup and
>   that cured the issue but I think this is a serious matter that should
>   be addressed immediately (not the least because it's hard to read
>   black text on a blue background and it wastes a lot of ink).
>
>   I first posted this at
>   
>   and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
>   on the update information) who advised me to post this bug here.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1817308/+subscriptions


-- 
“How many surrealists does it take to|  Brian Foster
 change a lightbulb?  Three.  One calms  |  somewhere in south of France
 the warthog, and two fill the bathtub   |
 with brightly-coloured machine tools.”  |

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and 

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[Brian Foster]

My printer does NOT auto-upgrade and it started having the problem immediately 
after the `ghostscript' "upgrade".
There is no doubt about this, colour printing was working fine yesterday until 
the upgrade, then it went all blue-background.

I have not (yet?) tried reverting `ghostscript', I am happy(?) with the
"High Quality Grayscale" workaround.

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

-- 
Mailing list: https://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 1817308] Re: GhostScript Update causes Blue Background

[Brian Foster]

Not a bad idea, but I can confirm this is NOT what happened in my case.
My printer (HP OfficeJet Pro 6970) does NOT auto-upgrade, and it was
indisputably working fine until the `ghostscript' "upgrade" mentioned in
the bug report.  I was doing printing all day yesterday (in colour) and
everything worked fine until after that upgrade.  Also, asking the printer
to generate reports (either on the front panel or via HPLIP from Linux)
works fine, as does copying.  Its very probably only stuff from Linux/CUPS
which goes wrong.  (Having said that, I haven't tried "raw" PostScript, but
I also don't want to waste any more blue ink.
cheers!
-blf-

On Fri, 22 Feb 2019 at 18:05, Matthew Covington  wrote:
> I started having the same problem today on an Ubuntu 16.04 machine and
> an HP OfficeJet Pro 6978. However, I haven't updated ghostscript (or
> anything else recently). I was wondering whether it was an HP update
> that broke the printing. My printer is automatically installing HP
> updates.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1817308
>
> Title:
>   GhostScript Update causes Blue Background
>
> Status in ghostscript package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
>   kernel 4.15.0-45-generic.
>
>   Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
>   was applied to two of my machines (One is an Intel and one is an AMD,
>   but both are kept fully updated) that share a networked HP OfficeJet
>   6700 Printer.
>
>   At some point following the update, I happened to print a document,
>   and ended up with a blue background on every page, even otherwise
>   blank second sides. This occured regardless of a variety of
>   originating applications I used, such as LibreOffice, various text
>   editors, and even the CUPS "print test page" option.
>
>   It took me a while to troubleshoot this on that first machine (trying
>   different apps, reinstalling CUPS and so forth) until I realized the
>   new ghostscript update was the issue and that (after trying to print
>   from the second machine) it was affecting both machines.
>
>   I should note that, using the "non-CUPS" appearance of the same
>   printer, no blue background is present, but of course this provides no
>   features like ink-level reporting, dual-sided printing, etc.
>
>   I "restored" the ghostscript stuff from the last Timeshift backup and
>   that cured the issue but I think this is a serious matter that should
>   be addressed immediately (not the least because it's hard to read
>   black text on a blue background and it wastes a lot of ink).
>
>   I first posted this at
>   
>   and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
>   on the update information) who advised me to post this bug here.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1817308/+subscriptions

-- 
“How many surrealists does it take to|  Brian Foster
 change a lightbulb?  Three.  One calms  |  somewhere in south of France
 the warthog, and two fill the bathtub   |
 with brightly-coloured machine tools.”  |

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue 

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[Jarl]

I have downgraded to 9.25 using
sudo apt install ghostscript=9.25~dfsg+1-0ubuntu1 libgs9=9.25~dfsg+1-0ubuntu1 
libgs9-common=9.25~dfsg+1-0ubuntu1

That solved the problem.

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[Brian Foster]

Also "(HP) Deskjet 1510 All in one", "HP Officejet 7310";
e.g., see 
https://h30434.www3.hp.com/t5/Inkjet-Printing/Printer-has-suddenly-started-printing-solid-blue-background/td-p/7027024

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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

[Desktop-packages] [Bug 1802569] Re: RM openssl1.0 from Ubuntu

[Steve Langasek]

Removing packages from disco:
guacamole-client 0.9.9+dfsg-1 in disco
guacamole 0.9.9+dfsg-1 in disco amd64
guacamole 0.9.9+dfsg-1 in disco arm64
guacamole 0.9.9+dfsg-1 in disco armhf
guacamole 0.9.9+dfsg-1 in disco i386
guacamole 0.9.9+dfsg-1 in disco ppc64el
guacamole 0.9.9+dfsg-1 in disco s390x
Comment: FTBFS, removed from Debian testing, blocks freerdp removal; Debian bug 
#866704, LP: #1802569
1 package successfully removed.


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

** Also affects: guacamole-client (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: guacamole-client (Ubuntu)
   Status: New => Fix Released

** Also affects: netkit-ftp-ssl (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: moonshot-trust-router (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: moonshot-trust-router (Ubuntu)
   Status: New => Fix Released

** Changed in: netkit-ftp-ssl (Ubuntu)
   Status: New => Fix Released

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

** Also affects: guacamole-server (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  RM openssl1.0 from Ubuntu

Status in freerdp package in Ubuntu:
  Confirmed
Status in guacamole-client package in Ubuntu:
  Fix Released
Status in guacamole-server package in Ubuntu:
  Fix Released
Status in libpam-freerdp package in Ubuntu:
  Fix Released
Status in moonshot-trust-router package in Ubuntu:
  Fix Released
Status in netkit-ftp-ssl package in Ubuntu:
  Fix Released
Status in openssl1.0 package in Ubuntu:
  Incomplete
Status in pidentd package in Ubuntu:
  Fix Released
Status in freerdp package in Debian:
  Fix Released
Status in openssl1.0 package in Debian:
  New

Bug description:
  RM openssl1.0 from Ubuntu

  reconserver has multiple ftbfs issues / bugs.

  freerdp is superseeded by freerdp2.

  =

  Step 1:
  migrate
  https://launchpad.net/ubuntu/+source/guacamole-server/0.9.9-2ubuntu2
  as it drops dependency on freerdp

  Step 2:
  remove libpam-freerdp ; OpenSSL 1.0 removal and freerdp

  Step 3:
  remove freerdp -> the only outstanding reverse-dep (apart from step1,2) is 
ltsp-client which has an alternative:
  'freerdp2-x11 | freerdp-x11 | rdesktop'

  Step 4:
  remove openssl1.0

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

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

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[Matthew Covington]

I started having the same problem today on an Ubuntu 16.04 machine and
an HP OfficeJet Pro 6978. However, I haven't updated ghostscript (or
anything else recently). I was wondering whether it was an HP update
that broke the printing. My printer is automatically installing HP
updates.

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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

[Desktop-packages] [Bug 1802569] Re: RM openssl1.0 from Ubuntu

[Steve Langasek]

Removing packages from disco:
libpam-freerdp 1.0.1+15.04.2014-0ubuntu1 in disco
libpam-freerdp 1.0.1+15.04.2014-0ubuntu1 in disco amd64
libpam-freerdp 1.0.1+15.04.2014-0ubuntu1 in disco arm64
libpam-freerdp 1.0.1+15.04.2014-0ubuntu1 in disco armhf
libpam-freerdp 1.0.1+15.04.2014-0ubuntu1 in disco i386
libpam-freerdp 1.0.1+15.04.2014-0ubuntu1 in disco ppc64el
libpam-freerdp 1.0.1+15.04.2014-0ubuntu1 in disco s390x
Comment: Ubuntu-specific, unmaintained, blocks freerdp removal; LP: #1802569
1 package successfully removed.


** Changed in: libpam-freerdp (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  RM openssl1.0 from Ubuntu

Status in freerdp package in Ubuntu:
  Confirmed
Status in guacamole-client package in Ubuntu:
  Fix Released
Status in guacamole-server package in Ubuntu:
  Fix Released
Status in libpam-freerdp package in Ubuntu:
  Fix Released
Status in moonshot-trust-router package in Ubuntu:
  Fix Released
Status in netkit-ftp-ssl package in Ubuntu:
  Fix Released
Status in openssl1.0 package in Ubuntu:
  Incomplete
Status in pidentd package in Ubuntu:
  Fix Released
Status in freerdp package in Debian:
  Fix Released
Status in openssl1.0 package in Debian:
  New

Bug description:
  RM openssl1.0 from Ubuntu

  reconserver has multiple ftbfs issues / bugs.

  freerdp is superseeded by freerdp2.

  =

  Step 1:
  migrate
  https://launchpad.net/ubuntu/+source/guacamole-server/0.9.9-2ubuntu2
  as it drops dependency on freerdp

  Step 2:
  remove libpam-freerdp ; OpenSSL 1.0 removal and freerdp

  Step 3:
  remove freerdp -> the only outstanding reverse-dep (apart from step1,2) is 
ltsp-client which has an alternative:
  'freerdp2-x11 | freerdp-x11 | rdesktop'

  Step 4:
  remove openssl1.0

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

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

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[Brian Foster]

Some more info (in case it helps):

Ubuntu 18.04.2 LTS x86_64 [fully up-to-date Kubuntu]
HP OfficeJet Pro 6970 [has worked flawlessly]

A bit of searching on the 'Net has found complaints this is happening
for other printers not mentioned in _this_ bug report, including (but
not necessarily limited to) "HP Photosmart C7280", "HP 3520 All-in-one";
e.g., see 
https://askubuntu.com/questions/1120379/my-printer-adds-a-blue-background

I have not noticed/found any complaints (yet?) for non-HP printers.

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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

[Desktop-packages] [Bug 1802569] Re: RM openssl1.0 from Ubuntu

[Steve Langasek]

Removing packages from disco:
guacamole-server 0.9.9-2ubuntu2 in disco
guacd 0.9.9-2ubuntu2 in disco amd64
guacd 0.9.9-2ubuntu2 in disco arm64
guacd 0.9.9-2ubuntu2 in disco armhf
guacd 0.9.9-2ubuntu2 in disco i386
guacd 0.9.9-2ubuntu2 in disco ppc64el
guacd 0.9.9-2ubuntu2 in disco s390x
libguac-client-ssh0 0.9.9-2ubuntu2 in disco amd64
libguac-client-ssh0 0.9.9-2ubuntu2 in disco arm64
libguac-client-ssh0 0.9.9-2ubuntu2 in disco armhf
libguac-client-ssh0 0.9.9-2ubuntu2 in disco i386
libguac-client-ssh0 0.9.9-2ubuntu2 in disco ppc64el
libguac-client-ssh0 0.9.9-2ubuntu2 in disco s390x
libguac-client-telnet0 0.9.9-2ubuntu2 in disco amd64
libguac-client-telnet0 0.9.9-2ubuntu2 in disco arm64
libguac-client-telnet0 0.9.9-2ubuntu2 in disco armhf
libguac-client-telnet0 0.9.9-2ubuntu2 in disco i386
libguac-client-telnet0 0.9.9-2ubuntu2 in disco ppc64el
libguac-client-telnet0 0.9.9-2ubuntu2 in disco s390x
libguac-client-vnc0 0.9.9-2ubuntu2 in disco amd64
libguac-client-vnc0 0.9.9-2ubuntu2 in disco arm64
libguac-client-vnc0 0.9.9-2ubuntu2 in disco armhf
libguac-client-vnc0 0.9.9-2ubuntu2 in disco i386
libguac-client-vnc0 0.9.9-2ubuntu2 in disco ppc64el
libguac-client-vnc0 0.9.9-2ubuntu2 in disco s390x
libguac-dev 0.9.9-2ubuntu2 in disco amd64
libguac-dev 0.9.9-2ubuntu2 in disco arm64
libguac-dev 0.9.9-2ubuntu2 in disco armhf
libguac-dev 0.9.9-2ubuntu2 in disco i386
libguac-dev 0.9.9-2ubuntu2 in disco ppc64el
libguac-dev 0.9.9-2ubuntu2 in disco s390x
libguac11 0.9.9-2ubuntu2 in disco amd64
libguac11 0.9.9-2ubuntu2 in disco arm64
libguac11 0.9.9-2ubuntu2 in disco armhf
libguac11 0.9.9-2ubuntu2 in disco i386
libguac11 0.9.9-2ubuntu2 in disco ppc64el
libguac11 0.9.9-2ubuntu2 in disco s390x
Comment: removed from Debian testing, blocks freerdp removal; Debian bug 
#888321, LP: #1802569
1 package successfully removed.


** Changed in: guacamole-server (Ubuntu)
   Status: New => Fix Released

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

Title:
  RM openssl1.0 from Ubuntu

Status in freerdp package in Ubuntu:
  Confirmed
Status in guacamole-client package in Ubuntu:
  Fix Released
Status in guacamole-server package in Ubuntu:
  Fix Released
Status in libpam-freerdp package in Ubuntu:
  Fix Released
Status in moonshot-trust-router package in Ubuntu:
  Fix Released
Status in netkit-ftp-ssl package in Ubuntu:
  Fix Released
Status in openssl1.0 package in Ubuntu:
  Incomplete
Status in pidentd package in Ubuntu:
  Fix Released
Status in freerdp package in Debian:
  Fix Released
Status in openssl1.0 package in Debian:
  New

Bug description:
  RM openssl1.0 from Ubuntu

  reconserver has multiple ftbfs issues / bugs.

  freerdp is superseeded by freerdp2.

  =

  Step 1:
  migrate
  https://launchpad.net/ubuntu/+source/guacamole-server/0.9.9-2ubuntu2
  as it drops dependency on freerdp

  Step 2:
  remove libpam-freerdp ; OpenSSL 1.0 removal and freerdp

  Step 3:
  remove freerdp -> the only outstanding reverse-dep (apart from step1,2) is 
ltsp-client which has an alternative:
  'freerdp2-x11 | freerdp-x11 | rdesktop'

  Step 4:
  remove openssl1.0

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

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

[Desktop-packages] [Bug 1817222] Re: [nouveau] Xorg freeze

[Ramiro Caamano]

** Description changed:

- I have selected the NVIDIA driver instead and can report the same
- problem - screen frozen one internet page open no other programs. Using
- Firefox as per original install, each time this freeze has occurred only
- when connected to wireless network and using the internet. So this is an
- update to the original logged error report.
+ Update 22/2/2019 Hi again , logged in to my computer today and noted the
+ driver was not set to nvidia the selection option was on xorg driver and
+ would not change this would revert after selection. Attempted changing
+ driver as user and also as admin no effect.  Did a manual update via
+ terminal of all drivers '34 approximately' and then software updater
+ allowed the selection of nvidia display driver. I mention this as I
+ posted yesterday that I had selected nvidia driver and found the same
+ issue, based on today's finding this may have been factually incorrect
+ and maybe the two crashes occurred while using xorg driver.
+ 
+ 21/2/2019
+ I have selected the NVIDIA driver instead and can report the same problem - 
screen frozen one internet page open no other programs. Using Firefox as per 
original install, each time this freeze has occurred only when connected to 
wireless network and using the internet. So this is an update to the original 
logged error report.
  
  Have been using Ubuntu online/offline for occasional browsing or offline
  use since installation and no issues.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 21 21:49:33 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GpuHangFrequency: Very infrequently
  GraphicsCard:
-  NVIDIA Corporation GT218 [NVS 300] [10de:10d8] (rev a2) (prog-if 00 [VGA 
controller])
-Subsystem: Hewlett-Packard Company GT218 [NVS 300] [103c:0862]
+  NVIDIA Corporation GT218 [NVS 300] [10de:10d8] (rev a2) (prog-if 00 [VGA 
controller])
+    Subsystem: Hewlett-Packard Company GT218 [NVS 300] [103c:0862]
  InstallationDate: Installed on 2019-02-20 (1 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L
  ProcEnviron:
-  LANGUAGE=en_GB:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_GB:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FG
  dmi.board.name: G31M-ES2L
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFG:bd02/24/2010:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-ES2L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G31M-ES2L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.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

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

Title:
  [nouveau] Xorg freeze

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Update 22/2/2019 Hi again , logged in to my computer today and noted
  the driver was not set to nvidia the selection option was on xorg
  driver and would not change this would revert after selection.
  Attempted changing driver as user and also as admin no effect.  Did a
  manual update via terminal of all drivers '34 approximately' and then
  software updater  allowed the selection of nvidia display driver. I
  mention this as I posted yesterday that I had selected nvidia driver
  and found the same issue, based on today's finding this may have been
  factually incorrect and maybe the two 

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[Steve Langasek]

** Changed in: ghostscript (Ubuntu)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[Brian Foster]

I can also confirm setting "High Quality Grayscale" (in CUPS) works-around the 
problem.
There's no colour (obviously), but also no wasting Blue ink on a useless 
background.

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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

[Desktop-packages] [Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

[Simen Aas Henriksen]

When do you expect to get into Bionic?

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

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

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Triaged
Status in mutter source package in Cosmic:
  In Progress

Bug description:
  [Impact]

  Gnome Shell redraws at 60 FPS at most, regardless of the hardware
  refresh rate, and regardless of the current display mode. This is
  particularly annoying for owners of 144Hz/120Hz/240Hz displays.

  [Test Case]

  0. Find a monitor or laptop with a high refresh rate (120Hz or more),
  noting NOT to trust gnome-control-center or xrandr because an
  unrelated bug in mutter may cause those to report 120Hz even on 60Hz
  displays. Make sure the advertised hardware specs show the display is
  a high frame rate.

  1. Edit /etc/environment and add:
     CLUTTER_SHOW_FPS=1

  2. Reboot.

  3. Open a terminal window and run:
     journalctl -f | grep FPS

  4. In a new window run 'glmark2' or some other OpenGL benchmark that
  is not frame rate limited (note: glxgears for unrelated reasons IS
  frame rate limited in Wayland sessions, but can be used in Xorg
  sessions).

  5. Verify the terminal window from step 4 shows high FPS values coming
  from the journalctl log that match the hardware spec, and are much
  higher than 60.

  [Regression Potential]

  Medium to low. This patch has been used upstream and in Ubuntu 19.04
  for some months already without any issues. Although minor syntactical
  changes had to be made to avoid conflicts when backporting it from
  mutter 3.32 to mutter 3.30. If regressions did occur they would be
  visible in the frame rate of the entire screen.

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

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

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[Brian Foster]

I also can confirm this started happening after the following upgrade:

Start-Date: 2019-02-21  20:42:54
Commandline: apt-get dist-upgrade
Requested-By: [redacted]
Upgrade: libgs9:amd64 (9.26~dfsg+0-0ubuntu0.18.04.4, 
9.26~dfsg+0-0ubuntu0.18.04.5), ghostscript-dbg:amd64 
(9.26~dfsg+0-0ubuntu0.18.04.4, 9.26~dfsg+0-0ubuntu0.18.04.5), 
ghostscript-doc:amd64 (9.26~dfsg+0-0ubuntu0.18.04.4, 
9.26~dfsg+0-0ubuntu0.18.04.5), ghostscript:amd64 (9.26~dfsg+0-0ubuntu0.18.04.4, 
9.26~dfsg+0-0ubuntu0.18.04.5), ghostscript-x:amd64 
(9.26~dfsg+0-0ubuntu0.18.04.4, 9.26~dfsg+0-0ubuntu0.18.04.5), 
libgs9-common:amd64 (9.26~dfsg+0-0ubuntu0.18.04.4, 9.26~dfsg+0-0ubuntu0.18.04.5)
End-Date: 2019-02-21  20:45:26

There is no doubt it is due to that "upgrade".

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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

[Desktop-packages] [Bug 1817346] [NEW] Printing blue pages after upgrading ghostscript to 9.26~dfsg+0-0ubuntu0.16.04.5

[Matheus Carminatti Angelo]

Public bug reported:

Various machines running Ubuntu 16-04 are printing blue background pages
after upgrading 9.26~dfsg+0-0ubuntu0.16.04.4 to
9.26~dfsg+0-0ubuntu0.16.04.5 in the automatic updates. The issue is
bigger because, after solving by manually installing the 16.04.4
version, any upgrade in hplip or automatic system upgrades reinstall the
lastest version.

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

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

Title:
  Printing blue pages after upgrading ghostscript to
  9.26~dfsg+0-0ubuntu0.16.04.5

Status in ghostscript package in Ubuntu:
  New

Bug description:
  Various machines running Ubuntu 16-04 are printing blue background
  pages after upgrading 9.26~dfsg+0-0ubuntu0.16.04.4 to
  9.26~dfsg+0-0ubuntu0.16.04.5 in the automatic updates. The issue is
  bigger because, after solving by manually installing the 16.04.4
  version, any upgrade in hplip or automatic system upgrades reinstall
  the lastest version.

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

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

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[Steve Dodson]

Half my office began printing blue today after an unattended update. As
a workaround, I set each of the printers to use "High-Quality-Grayscale"
until a fix is pushed.

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[Claus Tondering]

Here is a CUPS error log in debug mode when executing a job that was
printed with a blue background.

** Attachment added: "CUPS error log"
   
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1817308/+attachment/5240958/+files/error_log

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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

[Desktop-packages] [Bug 1802569] Re: RM openssl1.0 from Ubuntu

[Dimitri John Ledkov]

** No longer affects: moonshot-trust-router (Debian)

** No longer affects: moonshot-trust-router (Ubuntu)

** Description changed:

  RM openssl1.0 from Ubuntu
  
  reconserver has multiple ftbfs issues / bugs.
  
  freerdp is superseeded by freerdp2.
  
  =
- 
  
  Step 1:
  migrate
  https://launchpad.net/ubuntu/+source/guacamole-server/0.9.9-2ubuntu2
  as it drops dependency on freerdp
  
  Step 2:
  remove libpam-freerdp ; OpenSSL 1.0 removal and freerdp
  
  Step 3:
  remove freerdp -> the only outstanding reverse-dep (apart from step1,2) is 
ltsp-client which has an alternative:
  'freerdp2-x11 | freerdp-x11 | rdesktop'
+ 
+ Step 4:
+ remove openssl1.0

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

Title:
  RM openssl1.0 from Ubuntu

Status in freerdp package in Ubuntu:
  Confirmed
Status in libpam-freerdp package in Ubuntu:
  Triaged
Status in openssl1.0 package in Ubuntu:
  Incomplete
Status in freerdp package in Debian:
  Fix Released
Status in openssl1.0 package in Debian:
  New

Bug description:
  RM openssl1.0 from Ubuntu

  reconserver has multiple ftbfs issues / bugs.

  freerdp is superseeded by freerdp2.

  =

  Step 1:
  migrate
  https://launchpad.net/ubuntu/+source/guacamole-server/0.9.9-2ubuntu2
  as it drops dependency on freerdp

  Step 2:
  remove libpam-freerdp ; OpenSSL 1.0 removal and freerdp

  Step 3:
  remove freerdp -> the only outstanding reverse-dep (apart from step1,2) is 
ltsp-client which has an alternative:
  'freerdp2-x11 | freerdp-x11 | rdesktop'

  Step 4:
  remove openssl1.0

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

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

[Desktop-packages] [Bug 1817335] Re: Freeze when changing the volume with the mouse wheel

[SamuelB.]

** Tags added: disco

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

Title:
  Freeze when changing the volume with the mouse wheel

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  = Problem =
  Since today 2019-02-22 after upgrade:

  * Ubuntu (Gnome) desktop freeze when changing the volume with mouse wheel, no 
keyboard/mouse input possible, hard reboot or restart gdm over ssh required
  * (possibly related?) gnome-shell extensions {system-monitor, SomaFM internet 
radio} not working anymore

  = System = 
  lsb_release -rd
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  apt-cache policy gnome-shell
  gnome-shell:
Installiert:   3.31.90-1ubuntu1
Installationskandidat: 3.31.90-1ubuntu1
Versionstabelle:
   *** 3.31.90-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu disco-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.30.2-2ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu disco/main amd64 Packages

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

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

[Desktop-packages] [Bug 1817338] [NEW] HDMI sound output not available

[Franck]

Public bug reported:

In 19.04, HDMI sound stopped working after some upgrade.

The sink is somehow availalbe, but cannot be selected.
In gnome-control-center, HDMI output device is listed, but if I choose it, no 
configuration list appears (see screen capture attached).

aplay -l gives me:
~$ aplay -l
 Liste des Périphériques Matériels PLAYBACK 
carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC Analog]
  Sous-périphériques: 0/1
  Sous-périphérique #0: subdevice #0
carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0]
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0
carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1]
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0
carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2]
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0

pavucontrol shows HDMI as unplugged.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: pulseaudio 1:12.2-2ubuntu1
ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
Uname: Linux 4.19.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  franck 5998 F pulseaudio
 /dev/snd/pcmC1D0c:   franck 5998 F...m pulseaudio
 /dev/snd/controlC0:  franck 5998 F pulseaudio
CurrentDesktop: GNOME
Date: Fri Feb 22 16:16:56 2019
EcryptfsInUse: Yes
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/27/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: G7ETA9WW (2.69 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2353CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T430s
dmi.product.name: 2353CTO
dmi.product.sku: LENOVO_MT_2353
dmi.product.version: ThinkPad T430s
dmi.sys.vendor: LENOVO

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


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

** Attachment added: "gnome-control-center not showing configuration options 
for HDMI"
   
https://bugs.launchpad.net/bugs/1817338/+attachment/5240948/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202019-02-22%2016-24-51.png

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

Title:
  HDMI sound output not available

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  In 19.04, HDMI sound stopped working after some upgrade.

  The sink is somehow availalbe, but cannot be selected.
  In gnome-control-center, HDMI output device is listed, but if I choose it, no 
configuration list appears (see screen capture attached).

  aplay -l gives me:
  ~$ aplay -l
   Liste des Périphériques Matériels PLAYBACK 
  carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC 
Analog]
Sous-périphériques: 0/1
Sous-périphérique #0: subdevice #0
  carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0

  pavucontrol shows HDMI as unplugged.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  franck 5998 F pulseaudio
   /dev/snd/pcmC1D0c:   franck 5998 F...m pulseaudio
   /dev/snd/controlC0:  franck 5998 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb 22 16:16:56 2019
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ETA9WW (2.69 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2353CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[Patrick Demonguères]

I've got the same issue : all my printed page have a blue background.
$ lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04

I tried unsuccessfully to update HPLIP package for my HP ENVY 5642
printer. Hplip package does not seem to be involved.

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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

[Desktop-packages] [Bug 1802569] Re: RM openssl1.0 from Ubuntu

[Dimitri John Ledkov]

** No longer affects: netkit-ftp-ssl (Ubuntu)

** No longer affects: netkit-ftp-ssl (Debian)

** No longer affects: pidentd (Ubuntu)

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

Title:
  RM openssl1.0 from Ubuntu

Status in freerdp package in Ubuntu:
  Confirmed
Status in libpam-freerdp package in Ubuntu:
  Triaged
Status in openssl1.0 package in Ubuntu:
  Incomplete
Status in freerdp package in Debian:
  Fix Released
Status in openssl1.0 package in Debian:
  New

Bug description:
  RM openssl1.0 from Ubuntu

  reconserver has multiple ftbfs issues / bugs.

  freerdp is superseeded by freerdp2.

  =

  
  Step 1:
  migrate
  https://launchpad.net/ubuntu/+source/guacamole-server/0.9.9-2ubuntu2
  as it drops dependency on freerdp

  Step 2:
  remove libpam-freerdp ; OpenSSL 1.0 removal and freerdp

  Step 3:
  remove freerdp -> the only outstanding reverse-dep (apart from step1,2) is 
ltsp-client which has an alternative:
  'freerdp2-x11 | freerdp-x11 | rdesktop'

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

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

[Desktop-packages] [Bug 1817335] [NEW] Freeze when changing the volume with the mouse wheel

[SamuelB.]

Public bug reported:

= Problem =
Since today 2019-02-22 after upgrade:

* Ubuntu (Gnome) desktop freeze when changing the volume with mouse wheel, no 
keyboard/mouse input possible, hard reboot or restart gdm over ssh required
* (possibly related?) gnome-shell extensions {system-monitor, SomaFM internet 
radio} not working anymore

= System = 
lsb_release -rd
Description:Ubuntu Disco Dingo (development branch)
Release:19.04

apt-cache policy gnome-shell
gnome-shell:
  Installiert:   3.31.90-1ubuntu1
  Installationskandidat: 3.31.90-1ubuntu1
  Versionstabelle:
 *** 3.31.90-1ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu disco-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 3.30.2-2ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu disco/main amd64 Packages

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

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

Title:
  Freeze when changing the volume with the mouse wheel

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  = Problem =
  Since today 2019-02-22 after upgrade:

  * Ubuntu (Gnome) desktop freeze when changing the volume with mouse wheel, no 
keyboard/mouse input possible, hard reboot or restart gdm over ssh required
  * (possibly related?) gnome-shell extensions {system-monitor, SomaFM internet 
radio} not working anymore

  = System = 
  lsb_release -rd
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  apt-cache policy gnome-shell
  gnome-shell:
Installiert:   3.31.90-1ubuntu1
Installationskandidat: 3.31.90-1ubuntu1
Versionstabelle:
   *** 3.31.90-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu disco-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.30.2-2ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu disco/main amd64 Packages

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

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

[Desktop-packages] [Bug 1802569] Re: RM openssl1.0 from Ubuntu

[Dimitri John Ledkov]

** Description changed:

  RM openssl1.0 from Ubuntu
  
  reconserver has multiple ftbfs issues / bugs.
  
+ freerdp is superseeded by freerdp2.
  
- freerdp is superseeded by freerdp2.
+ =
+ 
+ 
+ Step 1:
+ migrate
+ https://launchpad.net/ubuntu/+source/guacamole-server/0.9.9-2ubuntu2
+ as it drops dependency on freerdp
+ 
+ Step 2:
+ remove libpam-freerdp ; OpenSSL 1.0 removal and freerdp
+ 
+ Step 3:
+ remove freerdp -> the only outstanding reverse-dep (apart from step1,2) is 
ltsp-client which has an alternative:
+ 'freerdp2-x11 | freerdp-x11 | rdesktop'

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

Title:
  RM openssl1.0 from Ubuntu

Status in freerdp package in Ubuntu:
  Confirmed
Status in libpam-freerdp package in Ubuntu:
  Triaged
Status in moonshot-trust-router package in Ubuntu:
  Fix Released
Status in openssl1.0 package in Ubuntu:
  Incomplete
Status in freerdp package in Debian:
  Fix Released
Status in moonshot-trust-router package in Debian:
  New
Status in openssl1.0 package in Debian:
  New

Bug description:
  RM openssl1.0 from Ubuntu

  reconserver has multiple ftbfs issues / bugs.

  freerdp is superseeded by freerdp2.

  =

  
  Step 1:
  migrate
  https://launchpad.net/ubuntu/+source/guacamole-server/0.9.9-2ubuntu2
  as it drops dependency on freerdp

  Step 2:
  remove libpam-freerdp ; OpenSSL 1.0 removal and freerdp

  Step 3:
  remove freerdp -> the only outstanding reverse-dep (apart from step1,2) is 
ltsp-client which has an alternative:
  'freerdp2-x11 | freerdp-x11 | rdesktop'

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

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

[Desktop-packages] [Bug 1817335] [NEW] Freeze when changing the volume with the mouse wheel

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

= Problem =
Since today 2019-02-22 after upgrade:

* Ubuntu (Gnome) desktop freeze when changing the volume with mouse wheel, no 
keyboard/mouse input possible, hard reboot or restart gdm over ssh required
* (possibly related?) gnome-shell extensions {system-monitor, SomaFM internet 
radio} not working anymore

= System = 
lsb_release -rd
Description:Ubuntu Disco Dingo (development branch)
Release:19.04

apt-cache policy gnome-shell
gnome-shell:
  Installiert:   3.31.90-1ubuntu1
  Installationskandidat: 3.31.90-1ubuntu1
  Versionstabelle:
 *** 3.31.90-1ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu disco-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 3.30.2-2ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu disco/main amd64 Packages

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

-- 
Freeze when changing the volume with the mouse wheel
https://bugs.launchpad.net/bugs/1817335
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 1817308] Re: GhostScript Update causes Blue Background

[Frank]

As for Till Kamppeter's request, there doesn't seem to be any CUPS error
log that I could locate.

Also, someone else reported the same issue on the Mint Forums if you're 
interested. It's at:
https://forums.linuxmint.com/viewtopic.php?f=47=288613

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[Frank]

** Attachment added: "history.log"
   
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1817308/+attachment/5240943/+files/history.log

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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

[Desktop-packages] [Bug 1817334] [NEW] dock disappears after apt dist-upgrade, needed to install gnome-shell-extension-dashtodock by hand, restart gnome-shell, and enable extension in tweaks

[Jonathan Kamens]

Public bug reported:

I did an apt dist-upgrade and got a message telling me that gnome-shell
had crashed and asking if I wanted to report it. I figured it was just
something funky about the upgrade so didn't bother. Instead, I restarted
my machine just to get everything back into a sane state. Upon logging
in after doing that, I had no dock.

I dug around to try to figure out what was going on, and finally
stumbled upon the description for "Ubuntu Dock" in gnome-tweaks, which
told me to install dash to dock.

So I installed that with apt and then restarted gnome-shell and then
restarted gnome-tweaks and then enabled dash to dock and finally my dock
was back.

This is, shall we say, not an ideal upgrade experience.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell-extension-ubuntu-dock 64ubuntu3
ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
Uname: Linux 4.19.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 22 10:05:57 2019
InstallationDate: Installed on 2019-01-02 (51 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: Upgraded to disco on 2019-01-21 (31 days ago)

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


** Tags: amd64 apport-bug disco

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

Title:
  dock disappears after apt dist-upgrade, needed to install gnome-shell-
  extension-dashtodock by hand, restart gnome-shell, and enable
  extension in tweaks

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

Bug description:
  I did an apt dist-upgrade and got a message telling me that gnome-
  shell had crashed and asking if I wanted to report it. I figured it
  was just something funky about the upgrade so didn't bother. Instead,
  I restarted my machine just to get everything back into a sane state.
  Upon logging in after doing that, I had no dock.

  I dug around to try to figure out what was going on, and finally
  stumbled upon the description for "Ubuntu Dock" in gnome-tweaks, which
  told me to install dash to dock.

  So I installed that with apt and then restarted gnome-shell and then
  restarted gnome-tweaks and then enabled dash to dock and finally my
  dock was back.

  This is, shall we say, not an ideal upgrade experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-ubuntu-dock 64ubuntu3
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 22 10:05:57 2019
  InstallationDate: Installed on 2019-01-02 (51 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to disco on 2019-01-21 (31 days ago)

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

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

[Desktop-packages] [Bug 1802569] Re: RM openssl1.0 from Ubuntu

[Steve Langasek]

Removing packages from disco:
netkit-ftp-ssl 0.17.34+0.2-4 in disco
ftp-ssl 0.17.34+0.2-4 in disco amd64
ftp-ssl 0.17.34+0.2-4 in disco arm64
ftp-ssl 0.17.34+0.2-4 in disco armhf
ftp-ssl 0.17.34+0.2-4 in disco i386
ftp-ssl 0.17.34+0.2-4 in disco ppc64el
ftp-ssl 0.17.34+0.2-4 in disco s390x
Comment: Depends on obsolete opensss1.0, removed from Debian testing; Debian 
bug #859224, LP: #1802569
1 package successfully removed.


** Changed in: netkit-ftp-ssl (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: moonshot-trust-router (Ubuntu)
   Status: Triaged => Fix Released

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

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

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

Title:
  RM openssl1.0 from Ubuntu

Status in freerdp package in Ubuntu:
  Confirmed
Status in libpam-freerdp package in Ubuntu:
  Triaged
Status in moonshot-trust-router package in Ubuntu:
  Fix Released
Status in netkit-ftp-ssl package in Ubuntu:
  Fix Released
Status in openssl1.0 package in Ubuntu:
  Incomplete
Status in pidentd package in Ubuntu:
  Fix Released
Status in freerdp package in Debian:
  Fix Released
Status in moonshot-trust-router package in Debian:
  New
Status in netkit-ftp-ssl package in Debian:
  New
Status in openssl1.0 package in Debian:
  New

Bug description:
  RM openssl1.0 from Ubuntu

  reconserver has multiple ftbfs issues / bugs.

  
  freerdp is superseeded by freerdp2.

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

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

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[Frank]

** Attachment added: "term.log"
   
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1817308/+attachment/5240942/+files/term.log

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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