date:20180511

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

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

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

Title:
  Chromium shows "aw snap" error on every page

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  I am using Chromium 30.0.1599.114 on Ubuntu 13.10 and I get a aw snap error 
message on every page I try to load, including the settings page. I tried 
reinstalling, deleting ~/.config/chrome and ~/.cache/chromium and I still have 
the same issue. The debug log shows a 
[6:6:1201/143302:WARNING:plugin_module.cc(673)] PPP_InitializeModule returned 
failure -2, but I don't know what that means. I would appreciate any help.
  Cheers,
  Oier

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

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

[Desktop-packages] [Bug 844582] Re: "Invalid argument" when trying to scan

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

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

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

Title:
  "Invalid argument" when trying to scan

Status in gscan2pdf package in Ubuntu:
  Expired
Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  I'm using a Fujitsu M3091DCd scanner with SANE. From the command line
  it works more or less well with Ubuntu.

  I can't use it with gscan2pdf v0.9.31, but gscan2pdf works with
  another scanner.

  All I get is a meaningless "Invalid argument" when I hit the scan
  button.

  When I start gscan2pdf from the command line I see these lines
  appearing when I hit the scan button:

  Error running process: Died at (eval 39) line 7.

$device->start;
$shash{$sane_thread}{status} = $Sane::STATUS+0;
if ($Sane::STATUS != SANE_STATUS_GOOD) {
 print "$prog_name: sane_start: $Sane::STATUS\n" if $debug;
 $shash{$sane_thread}{go} = 0;
 die; # quickest way out of the eval block
}

my $path = $shash{$sane_thread}{data};
if (not open($fh, ">", $path)) {
 $device->cancel;
 $shash{$sane_thread}{status} = SANE_STATUS_ACCESS_DENIED;
 $shash{$sane_thread}{go} = 0;
 die; # quickest way out of the eval block
}
scan_page($device, $fh);
$shash{$sane_thread}{status} = $Sane::STATUS+0;
close $fh;
printf "Scanned page %s.", $path if $debug;
printf " (scanner status = %d)\n", $Sane::STATUS if $debug;
$shash{$sane_thread}{status} = $Sane::STATUS+0;
$shash{$sane_thread}{go} = 0;

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gscan2pdf 0.9.31-2
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  NonfreeKernelModules: fglrx
  Architecture: amd64
  Date: Thu Sep  8 09:44:25 2011
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no username)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gscan2pdf
  UpgradeStatus: Upgraded to natty on 2011-06-01 (98 days ago)

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

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

[Desktop-packages] [Bug 1388593] Re: after update ubuntu chrome not display arabic language correctly

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

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

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

Title:
  after update ubuntu chrome not display arabic language correctly

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  After i  update Ubuntu, chrome not display Arabic language correctly in some 
sites like Facebook and some other site
  before update it was good
  and other browser not have this problem
  please help
  thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-release-upgrader-core 1:0.220.5
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Sun Nov  2 18:52:35 2014
  InstallationDate: Installed on 2014-06-13 (142 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1620980] Re: After updating Chromium its GUI is absurdly large (DPI settings ignored?)

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

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

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

Title:
  After updating Chromium its GUI is absurdly large (DPI settings
  ignored?)

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  Today I updated Chromium. After that update the browser gui is
  absurdly large, like on a 800x600 screen - it seems like it ignores
  DPI settings now. I have DPI set to 144 in my xfce desktop.

  How to change that behavior?

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

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

[Desktop-packages] [Bug 1755150] Re: package python3-uno (not installed) failed to install/upgrade: problemes de dependències - es deixa sense configurar

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

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

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

Title:
  package python3-uno (not installed) failed to install/upgrade:
  problemes de dependències - es deixa sense configurar

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  ha deixat de funcionar junt amb altres programes

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: python3-uno (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  AptOrdering:
   libreoffice-style-galaxy:amd64: Install
   libreoffice-style-elementary:amd64: Install
   libreoffice-common:amd64: Install
   python3-uno:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Mar 12 12:36:35 2018
  ErrorMessage: problemes de dependències - es deixa sense configurar
  InstallationDate: Installed on 2017-11-27 (104 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: libreoffice
  Title: package python3-uno (not installed) failed to install/upgrade: 
problemes de dependències - es deixa sense configurar
  UpgradeStatus: Upgraded to artful on 2017-11-27 (104 days ago)

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

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

[Desktop-packages] [Bug 1755181] Re: chromium-browser crashed with signal 5

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

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

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

Title:
  chromium-browser crashed with signal 5

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  $ apt-cache policy chromium-browser
  chromium-browser:
Instal·lat: 65.0.3325.146-0ubuntu1
Candidat:   65.0.3325.146-0ubuntu1
Taula de versió:
   *** 65.0.3325.146-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.146-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBMLTINRTZQMCMaAQOAPCJ4KlKVpVZUnSUOUFS7jACzAIHAgQCBgJUAqcABAQEBAjqAGHE4LUBYLEUAVlAhAAAe/QAySB5REQAKICAgICAg/ABDMjdGMzkwCiAgICAg/wBIVFFIODAzNjYyCiAgAeQCAxrxRpAEHxMSAyMJBweDAQAAZgMMABAAgAEdALxS0B4guChVQFZQIQAAHowK0JAgQDEgDEBVAFZQIQAAGIwK0Iog4C0QED6WAFZQIQAAGAAAYQ==
   modes: 1920x1080 1920x1080 1920x1080 1680x1050 1600x900 1280x1024 1440x900 
1280x800 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600 800x600 
720x576 720x480 720x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-3:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wANryAXAAIVAQSQJhV4Au2Vo1RMnCYPUFQBAQEBAQEBAQEBAQEBAQEB4TaArnA4JkA0IzYAftcQAAAaHSSAoHA4H0AwIDUAftcQAAAa/gBIQzlHS4AxNzNIR0UKQTGeAAIBCiAgAPM=
   modes: 1920x1080 1920x1080
  Date: Mon Mar 12 14:58:32 2018
  Desktop-Session:
   'gnome'
   '/etc/xdg/xdg-gnome:/etc/xdg'
   
'/home/cubells/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2014-08-20 (1300 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Load-Avg-1min: 2.69
  Load-Processes-Running-Percent:   0.1%
  MachineType: Notebook P17SM-A
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=zygote\ 
--ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so\ 
--ppapi-flash-version=28.0.0.126
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=9b47749a-0a02-480a-b6d4-c0cd3de49bf8 ro quiet splash vt.handoff=1
  Signal: 5
  SourcePackage: chromium-browser
  StacktraceTop:
   ()
   ()
   ()
   ()
   ChromeMain ()
  Title: chromium-browser crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-01-02 (68 days ago)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev pulse pulse-access 
sambashare sudo video www-data
  dmi.bios.date: 03/27/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P17SM-A
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/27/2014:svnNotebook:pnP17SM-A:pvrNotApplicable:rvnNotebook:rnP17SM-A:rvrNotApplicable:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: Not Applicable
  dmi.product.name: P17SM-A
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]

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

-- 
Mailing list:

[Desktop-packages] [Bug 1769240] Re: Images in chromium are distorted

2018-05-11 Thread Mark Scott

Issue persists with Chromium 66.0.3359.139

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

Title:
  Images in chromium are distorted

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  See this images
  https://drive.google.com/open?id=1V83Jb-k1zsgRr5pBIUIy8csvgOWLbmha
  https://drive.google.com/open?id=1YG_xB_9iCOcseoqNEdqBSyKrf58beHA7
  https://drive.google.com/open?id=1P_lgxbKMpV3VK9UaLEPcBrE7W6YsGuDP

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.181-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri May  4 21:08:06 2018
  Desktop-Session:
   'plasma'
   
'/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings'
   '/usr/share/plasma:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2017-12-16 (139 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  InstalledPlugins:
   
  Load-Avg-1min: 0.97
  Load-Processes-Running-Percent:   0.3%
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=e3723f86-9a4d-4166-960b-88262212fcc6 ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to bionic on 2018-04-02 (32 days ago)
  dmi.bios.date: 08/31/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0408
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0408:bd08/31/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

This bug was fixed in the package initramfs-tools - 0.130ubuntu6

---
initramfs-tools (0.130ubuntu6) cosmic; urgency=medium

  * Fix formatting for the generated netplan config: headers were
missing.

 -- Mathieu Trudel-Lapierre   Thu, 10 May 2018
12:12:03 -0400

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  replacement of resolvconf with systemd needs integration

Status in android-androresolvd package in Ubuntu:
  Triaged
Status in avahi package in Ubuntu:
  Triaged
Status in bind9 package in Ubuntu:
  Triaged
Status in cloud-init package in Ubuntu:
  Incomplete
Status in cloud-initramfs-tools package in Ubuntu:
  Invalid
Status in dhcpcd5 package in Ubuntu:
  Confirmed
Status in dibbler package in Ubuntu:
  Won't Fix
Status in dnscrypt-proxy package in Ubuntu:
  Confirmed
Status in dnsmasq package in Ubuntu:
  Invalid
Status in dnssec-trigger package in Ubuntu:
  Invalid
Status in fetchmail package in Ubuntu:
  Confirmed
Status in freedombox-setup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in ndisc6 package in Ubuntu:
  Fix Released
Status in netscript-2.4 package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  Triaged
Status in openvpn package in Ubuntu:
  Confirmed
Status in postfix package in Ubuntu:
  Invalid
Status in pppconfig package in Ubuntu:
  Confirmed
Status in pump package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid
Status in sendmail package in Ubuntu:
  Invalid
Status in squid3 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in unbound package in Ubuntu:
  Triaged
Status in vpnc package in Ubuntu:
  Invalid
Status in vpnc-scripts package in Ubuntu:
  Invalid
Status in whereami package in Ubuntu:
  Triaged

Bug description:
  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)

  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714308: dns does not work in initramfs after configure_networking
   * bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-androresolvd/+bug/1713803/+subscriptions

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

[Desktop-packages] [Bug 1769735] Re: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers looping, abandoned

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

** Changed in: hicolor-icon-theme (Ubuntu)
   Status: New => Confirmed

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

Title:
  package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers
  looping, abandoned

Status in hicolor-icon-theme package in Ubuntu:
  Confirmed

Bug description:
  No se cual es el error, solo salio el msj de erorr y lo reporto

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: hicolor-icon-theme 0.17-2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May  6 16:55:18 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2014-05-08 (1460 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-05-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1769735/+subscriptions

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

[Desktop-packages] [Bug 1226962] Re: Keyboard shortcuts (hotkeys) not functional in some cases in non-latin keyboard layouts

2018-05-11 Thread Bryce Harrington

** Changed in: inkscape
   Status: Fix Committed => Fix Released

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

Title:
  Keyboard shortcuts (hotkeys) not functional in some cases in non-latin
  keyboard layouts

Status in aptana-studio-installer:
  New
Status in Default settings and artwork for Baltix OS:
  New
Status in LibreOffice:
  Fix Released
Status in ibus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Inkscape:
  Fix Released
Status in Intellij Idea:
  New
Status in monodevelop:
  New
Status in Mutter:
  Fix Released
Status in okular:
  New
Status in OpenOffice:
  New
Status in sigram:
  New
Status in Unity:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-terminal package in Ubuntu:
  Triaged
Status in kdevelop package in Ubuntu:
  Confirmed
Status in mc package in Ubuntu:
  Confirmed
Status in openjdk-7 package in Ubuntu:
  Incomplete
Status in terminator package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  In Progress
Status in gnome-settings-daemon source package in Xenial:
  Triaged
Status in gnome-terminal source package in Xenial:
  Triaged
Status in kdevelop source package in Xenial:
  Confirmed
Status in mc source package in Xenial:
  Confirmed
Status in openjdk-7 source package in Xenial:
  Incomplete
Status in terminator source package in Xenial:
  Confirmed
Status in unity source package in Xenial:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  In Progress
Status in gnome-shell package in Fedora:
  Won't Fix
Status in openoffice package in Fedora:
  Won't Fix

Bug description:
  Keyboard shortcuts are key combinations like Alt+F (usually opens the
  File menu) and Ctrl+O (usually opens the File→Open... dialog box).

  There is an issue with non-latin keyboard layouts that the keys under F or O 
(for Alt+F and Ctrl+O respectively) would correspond to some other character.
  What should happen then? There is some smart functionality (at least in the 
GTK+ library) that when we press a shortcut, it will try to make Alt+F or 
Ctrl+O work, even if the active keyboard layout is not English.

  For this smart functionality to work, it requires us to have as first 
keyboard layout the English (en) layout. Then, GTK+ will be able to
  check whether the shortcut makes sense for English, and if so, will run it.
  All that even if the active layout is Greek or Russian or something else. 

  This report has over 300 comments and these comments include all sort of 
corner cases that indeed shortcuts do not work. In general, shortcuts work,
  but in specific cases there are issues that need to be fixed.

  What we need to do, is collect those corner cases and create new
  separate reports.

  Here are the corner cases:

  1. In Dash (in Unity 7), shortcuts like Super+S/W work (for example, Greek, 
Russian), but they do not work for Super+A/F/M/C/V. 
  Report: 

  2. Java GUI applications on Linux do not support shortcuts in non-latin 
languages. This is an issue with Java and should be reported there.
  Java GUI apps are not included in any of the Ubuntu ISOs. 
  Report: 

  3. Shortcuts that use Ctrl on LibreOffice work for several languages (like 
Greek, Russian), but has been reported not to work on Hebrew.
  This should be a separate bug report specific to Hebrew and other languages 
affected in the same way.
  Report: 

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions

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

[Desktop-packages] [Bug 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update

2018-05-11 Thread Hilikus

I'm having the same issue. It seems we have the same laptop, based on what you 
attached. 
I think I have found some interesting details about this bug:
1) In my case, i'm dual booting with windows 10, the problem only occurs after 
booting into windows and then rebooting into ubuntu. A shutdown + start 
straight to ubuntu fixes the problem (I think this is why your sound came 
back). So, although this is a workaround, there is definitely something wrong. 
I describe the problem here in more detail 
https://askubuntu.com/q/1032543/172846
2) I think the problem is the windows Realtek drive putting the sound card in 
some kind of stand-by state that the linux driver cannot wake up from. Some 
people have reported with similar problems that downgrading the windows Realtek 
driver fixes the issue, but to me it is still clear that the problem is the 
linux driver not waking up correctly the device, not the windows driver using a 
feature intended to save power
3) With this idea that the problem is power-saving, I enabled the power-save 
feature in the linux driver: `echo 10 
>/sys/module/snd_hda_intel/parameters/power_save`
If I wait 10 seconds and then trigger a sound (i'm using a terminal's bell), 
the sound now works, it sounds weird at first (crackling) but it keeps 
improving after like 2 seconds where it sounds AFAICT normal, but then 2 
seconds later the volume starts to decrease like when speakers are running out 
of battery until sound is completely gone again. So it seems the linux drivers 
are somewhat capable of waking up the sound card, but not permanently


** Attachment added: "alsa-info-not-working"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852/+attachment/5138104/+files/alsa-info-not-working

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

Title:
  [hostname, Realtek ALC294, Speaker, Internal] No sound at all after
  windows update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After a windows update I lost all the sound on my ubuntu machine. It's the 
second time that this happends.
  My sound is unmuted and at a loud level and nothing is comming out of my 
speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  CurrentDesktop: Unity
  Date: Thu Jan 11 22:21:23 2018
  InstallationDate: Installed on 2017-11-29 (43 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   gbergeron   2408 F...m pulseaudio
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UAR.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX430UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1767027] Re: Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu 18.04)

2018-05-11 Thread Treviño

In what directory are you searching?

And what's the path of the files that should not be there?
Could you post an anonymized list of them (using find results in case)?

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

Title:
  Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu
  18.04)

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to Ubuntu 18.04 prerelease from Ubuntu 17.10 and am finding
  that Nautilus searches all subfolders when I start typing, not just
  the present folder, even though I have the "search only current
  folder" option selected in its preferences, and "Only searching the
  current folder" does appear in the GUI as I am searching. Nonetheless
  results appear from subfolders (which I wouldn't mind, but which I
  turn off due to its poor performance compared to current-folder-only).

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

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

[Desktop-packages] [Bug 1730231] Re: Nautilus opens for every mediafile a seperate player when selecting a group of files and pressing Enter

The correct upstream bug for this is
https://gitlab.gnome.org/GNOME/nautilus/issues/117

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

Title:
  Nautilus opens for every mediafile a seperate player when selecting a
  group of files and pressing Enter

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Expected behavior:
  The Player selected as standard opens with a playlist of the (media)files.
  (This is what actually happens if you select an application with the open 
with ... dialog)

  What happens:
  Nautilus launches for each file a separate instance of the 
standard-application.
  Example: 10 mp3 files selected opens 10 player-windows of audacious, qmmp, 
vlc, mpv or what ever is selected as standard. (I did try all of the named 
programs)
  This happens only if the group of files is open via pressing Return or 
selecting 'open' in context-menu. It does not happen when selecting an 
application via 'open with ...' in context-menu.

  Same behavior with groups of png or jpg files and photo-viewers.

  Reconstruction:
  1. Open Nautilus
  2. Set a mediaplayer as standard-application for mp3-files.
  3. Open a group of mp3-files by selecting them and pressing 'Enter' or using 
the 'Open'-Item in the context-menu

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1 [modified: 
usr/share/applications/org.gnome.Nautilus.desktop]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov  5 21:02:23 2017
  InstallationDate: Installed on 2017-10-28 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1770725] Re: You can not see the image of the movie

2018-05-11 Thread Bug Watch Updater

** Changed in: gstreamer1.0
   Status: Unknown => Confirmed

** Changed in: gstreamer1.0
   Importance: Unknown => Medium

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

Title:
  You can not see the image of the movie

Status in Gstreamer1.0:
  Confirmed
Status in gstreamer1.0 package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  Hello,

  You can not see the image of the movie.

  Regards,
  --
  Cristian Aravena Romero (caravena)

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

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

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

[Desktop-packages] [Bug 1770779] [NEW] language locales not compatible with firefox 60 update

2018-05-11 Thread Star Man

Public bug reported:

On Ubuntu LTS 18.04, after the recent Firefox update to version
60.0+build2, localization is deactivated presenting the browser only in
english. In the languages section all language packs are deactivated
citing incompatibilities with the present version.

Performing a language support check in Ubuntu Settings do not resolve
this issue.

Summary:
Ubuntu LTS 18.04 amd64
firefox 60.0+build2
Browser only shows in english; localization is deactivated due to 
incomptibilities with the installed language packs.
Browser should be presented in my locale language (spanish).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firefox 60.0+build2-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0p:   julian 1560 F...m pulseaudio
 /dev/snd/controlC1:  julian 1560 F pulseaudio
 /dev/snd/controlC0:  julian 1560 F pulseaudio
BuildID: 20180509234620
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Fri May 11 20:24:31 2018
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2018-05-08 (3 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IpRoute:
 default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp2s0 scope link metric 1000 
 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.37 metric 600
Locales: extensions.sqlite corrupt or missing
PrefSources: prefs.js
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_PE.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=60.0/20180509234620 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL552VW.218
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL552VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.218:bd03/16/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: GL
dmi.product.name: GL552VW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug bionic

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

Title:
  language locales not compatible with firefox 60 update

Status in firefox package in Ubuntu:
  New

Bug description:
  On Ubuntu LTS 18.04, after the recent Firefox update to version
  60.0+build2, localization is deactivated presenting the browser only
  in english. In the languages section all language packs are
  deactivated citing incompatibilities with the present version.

  Performing a language support check in Ubuntu Settings do not resolve
  this issue.

  Summary:
  Ubuntu LTS 18.04 amd64
  firefox 60.0+build2
  Browser only shows in english; localization is deactivated due to 
incomptibilities with the installed language packs.
  Browser should be presented in my locale language (spanish).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 60.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   julian 1560 F...m pulseaudio
   /dev/snd/controlC1:  julian 1560 F pulseaudio
   /dev/snd/controlC0:  julian 1560 F pulseaudio
  BuildID: 20180509234620
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 11 20:24:31 2018
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-05-08 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64

[Desktop-packages] [Bug 1766100] Re: Desktop keeps showing files that are no longer there

2018-05-11 Thread teo1978

> I'm not able to reproduce this bug [...] so I'm assuming this is Fix
Released

You know the saying "'ass-u-me' makes an *** out of u and me..."

There has never been any way to SYSTEMATICALLY reproduce the bug, I have
just observed it RANDOMLY from time to time, so, you being unable to
reproduce it doesn't mean it's fixed. It could be, but that's not
something you can just assume.

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

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

Title:
  Desktop keeps showing files that are no longer there

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Hours after downloading a few pdf files with  Chrome into the Desktop and 
being done with them, I went to delete them.
  I was surprised to find a file called something.pdf.chdownload. These are the 
temporary files that Chrome creates while downloading the files, then it 
renames them to their final filename without the .chrdownload suffix when they 
are complete. All of the files had been downloaded completely and succesfully 
(I had actually opened all of them) so this file shouldn't exist.

  And indeed, when I went to download it, I got an error "Cannot move 
 to trash. Delete it permanently?" (this is actually stupid in the 
first place: the reason why I'm getting this error, it turns out, is that the 
file does not exist, so it makes no sense to give me the option to permanently 
delete it, which will fail for the exact same reason).
  So I chose "delete", and got an error again, that the file could not be 
deleted. I retried several times and finally looked at "details" and found out 
that the source of the error was "no such file or directory".

  So, the file was not there.

  So why the fuck was it being shown on the desktop if it was no longer
  there? I can assume it might happen some rare times (it's a bug
  anyway) that you for some reason "miss" when a file ceases existing,
  and hence it is still falsely visible on the desktop. But there should
  come a point where Nautilus "realises" the file no longer exists and
  stops showing it. In other words, the contents of the desktop should
  be "refreshed" from time to time or on certain events. And trying to
  delete a file, triggering an error that says that the file doesn't
  fucking exist, should be such a case where you refresh the information
  and stop showing a file that doesn't exist.

  It's pathetic that you keep showing it forever until I kill and
  restart nautilus or fucking reboot.

  
  I'm sick of reporting such idiotic bugs on Nautilus. Ubuntu, for fuck's sake, 
switch to some better, decently maintained file manager. Nautilus is CRAP.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 22 18:04:34 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1369x817+258+98'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-11 (1653 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1747171] Re: "New Tab" disappeared from the GNOME Terminal menu

** Description changed:

  Impact
  --
  GNOME Terminal removed the New Tab menu option before Ubuntu 16.04 LTS. Tabs 
are a really popular feature in terminals and it's annoying to have this 
feature hidden.
  
  Test Case
  -
  Install the update.
  Close all terminals.
  Open a terminal.
  In the File menu should be New Tab and New Window menu items. Both should 
work.
  
  Regression Potential
  
  Restoring the previous behavior is now a one-line hidden configure option.
  
  Enabling that option removes the "Open new terminals in" option
  mentioned in the workaround.
  
- This build option is set in Fedora and is not believed to have any
- negative consequences.
+ This build option is set in Fedora (and other distros that use the
+ Fedora tweaks) and is not believed to have any negative consequences.
  
  Other Info
  --
  There are no plans at this time to try to backport this change to Ubuntu 
16.04 LTS or 17.10 because it would not be a simple one-line change there. (The 
configure flag was enabled in git commit 0820b385 .)
  
  https://debarshiray.wordpress.com/2018/05/11/gnome-terminal-separate-
  menu-items-for-opening-tabs-and-windows/
  
  Workaround
  --
  In Edit > Preferences (General) you can set "Open new terminals in Tab". Now, 
the File > New Window menu item opens a new tab instead of a new window.
  
  Original Bug Report
  ---
  There is not a "New Tab" option in the file menu of GNOME Terminal anymore on 
Ubuntu Bionic. It looks like it disappeared after some recent update. However, 
the CTRL + Shift + T shortcut works as expected.

** Changed in: gnome-terminal (Ubuntu Bionic)
   Status: Triaged => In Progress

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

Title:
  "New Tab" disappeared from the GNOME Terminal menu

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

Bug description:
  Impact
  --
  GNOME Terminal removed the New Tab menu option before Ubuntu 16.04 LTS. Tabs 
are a really popular feature in terminals and it's annoying to have this 
feature hidden.

  Test Case
  -
  Install the update.
  Close all terminals.
  Open a terminal.
  In the File menu should be New Tab and New Window menu items. Both should 
work.

  Regression Potential
  
  Restoring the previous behavior is now a one-line hidden configure option.

  Enabling that option removes the "Open new terminals in" option
  mentioned in the workaround.

  This build option is set in Fedora (and other distros that use the
  Fedora tweaks) and is not believed to have any negative consequences.

  Other Info
  --
  There are no plans at this time to try to backport this change to Ubuntu 
16.04 LTS or 17.10 because it would not be a simple one-line change there. (The 
configure flag was enabled in git commit 0820b385 .)

  https://debarshiray.wordpress.com/2018/05/11/gnome-terminal-separate-
  menu-items-for-opening-tabs-and-windows/

  Workaround
  --
  In Edit > Preferences (General) you can set "Open new terminals in Tab". Now, 
the File > New Window menu item opens a new tab instead of a new window.

  Original Bug Report
  ---
  There is not a "New Tab" option in the file menu of GNOME Terminal anymore on 
Ubuntu Bionic. It looks like it disappeared after some recent update. However, 
the CTRL + Shift + T shortcut works as expected.

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

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

[Desktop-packages] [Bug 1765556] Re: nvidia-prime needs a reboot to switch between dGPU/hGPU

2018-05-11 Thread gallopelado

También tengo el mismo problema que detalla el señor.

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

Title:
  nvidia-prime needs a reboot to switch between dGPU/hGPU

Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  I previously used Ubuntu 16.04 and Nvidia 375 driver with a Nvidia
  Geforce 635M and Sandy Bridge i7. To switch between the 2 Optimus
  cards (Intel hybrid and Nvidia discrete), one had to go into nvidia-
  settings, switch, logoff, login back, and the change was applied.

  I now have a Nvidia Quadro M2000 and a Skylake Xeon which has some
  Sync/Mux feature (whatever does that mean) with the Nvidia 390 driver.
  First of all, installing nivida-prime doesn't install bbswitch-dkms.
  Then, once the GPU switch is made, it triggers update-initramfs,
  recompile the kernel modules, and one needs to reboot the system to
  get the GPU change. Even when we install bbswitch-dkms.

  So am I getting a wrong impression or is there something twisted here
  ?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-prime 0.8.7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 19:20:01 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-04-08 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765556/+subscriptions

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

[Desktop-packages] [Bug 1770776] [NEW] update to desktop sessions on 11 May, 2018 causes jerky mouse action and inconsistent input. Applies to gnome and ubuntu sessions on wayland including gnome clas

2018-05-11 Thread Faron Anslow

Public bug reported:

Todays updates:

2018-05-11 12:05:17 upgrade firefox:amd64 59.0.2+build1-0ubuntu1 
60.0+build2-0ubuntu1
2018-05-11 12:05:26 upgrade firefox-locale-en:amd64 59.0.2+build1-0ubuntu1 
60.0+build2-0ubuntu1
2018-05-11 12:05:27 upgrade ubuntu-session:amd64 3.28.1-0ubuntu2 3.28.1-0ubuntu3
2018-05-11 12:05:28 upgrade gnome-startup-applications:amd64 3.28.1-0ubuntu2 
3.28.1-0ubuntu3
2018-05-11 12:05:28 upgrade gnome-session:amd64 3.28.1-0ubuntu2 3.28.1-0ubuntu3
2018-05-11 12:05:28 upgrade gnome-session-common:all 3.28.1-0ubuntu2 
3.28.1-0ubuntu3
2018-05-11 12:05:29 upgrade gnome-session-bin:amd64 3.28.1-0ubuntu2 
3.28.1-0ubuntu3
2018-05-11 12:05:29 upgrade gnome-session-wayland:all 3.28.1-0ubuntu2 
3.28.1-0ubuntu3
2018-05-11 12:05:29 upgrade openjdk-8-jre:amd64 8u162-b12-1 
8u171-b11-0ubuntu0.18.04.1
2018-05-11 12:05:30 upgrade openjdk-8-jre-headless:amd64 8u162-b12-1 
8u171-b11-0ubuntu0.18.04.1

Have resulted in VERY poor mouse tracking and mouse freezes and overall
poor performance of the desktop.

Ubuntu version: 18.04
Package versions are given above. 
I expect the mouse to track smoothly across the screen
What's actually happening is jerky mouse tracking and overall UI stutter.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-session 3.28.1-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri May 11 17:33:56 2018
InstallationDate: Installed on 2016-11-19 (538 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-session
UpgradeStatus: Upgraded to bionic on 2018-04-27 (14 days ago)

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


** Tags: amd64 apport-bug bionic

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

Title:
  update to desktop sessions on 11 May, 2018 causes jerky mouse action
  and inconsistent input. Applies to gnome and ubuntu sessions on
  wayland including gnome classic.

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Todays updates:

  2018-05-11 12:05:17 upgrade firefox:amd64 59.0.2+build1-0ubuntu1 
60.0+build2-0ubuntu1
  2018-05-11 12:05:26 upgrade firefox-locale-en:amd64 59.0.2+build1-0ubuntu1 
60.0+build2-0ubuntu1
  2018-05-11 12:05:27 upgrade ubuntu-session:amd64 3.28.1-0ubuntu2 
3.28.1-0ubuntu3
  2018-05-11 12:05:28 upgrade gnome-startup-applications:amd64 3.28.1-0ubuntu2 
3.28.1-0ubuntu3
  2018-05-11 12:05:28 upgrade gnome-session:amd64 3.28.1-0ubuntu2 
3.28.1-0ubuntu3
  2018-05-11 12:05:28 upgrade gnome-session-common:all 3.28.1-0ubuntu2 
3.28.1-0ubuntu3
  2018-05-11 12:05:29 upgrade gnome-session-bin:amd64 3.28.1-0ubuntu2 
3.28.1-0ubuntu3
  2018-05-11 12:05:29 upgrade gnome-session-wayland:all 3.28.1-0ubuntu2 
3.28.1-0ubuntu3
  2018-05-11 12:05:29 upgrade openjdk-8-jre:amd64 8u162-b12-1 
8u171-b11-0ubuntu0.18.04.1
  2018-05-11 12:05:30 upgrade openjdk-8-jre-headless:amd64 8u162-b12-1 
8u171-b11-0ubuntu0.18.04.1

  Have resulted in VERY poor mouse tracking and mouse freezes and
  overall poor performance of the desktop.

  Ubuntu version: 18.04
  Package versions are given above. 
  I expect the mouse to track smoothly across the screen
  What's actually happening is jerky mouse tracking and overall UI stutter.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.28.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 11 17:33:56 2018
  InstallationDate: Installed on 2016-11-19 (538 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (14 days ago)

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

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

[Desktop-packages] [Bug 1767027] Re: Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu 18.04)

2018-05-11 Thread Chris Billington

I'm using 1:3.26.3-0ubuntu4

Attached is a screenshot demonstrating the problem

** Attachment added: "screenshot of nautilus bug"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767027/+attachment/5138067/+files/nautilus_search_bug.png

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

Title:
  Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu
  18.04)

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to Ubuntu 18.04 prerelease from Ubuntu 17.10 and am finding
  that Nautilus searches all subfolders when I start typing, not just
  the present folder, even though I have the "search only current
  folder" option selected in its preferences, and "Only searching the
  current folder" does appear in the GUI as I am searching. Nonetheless
  results appear from subfolders (which I wouldn't mind, but which I
  turn off due to its poor performance compared to current-folder-only).

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

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

[Desktop-packages] [Bug 1729695] Re: ASCII decode error, but not due to filenames in backup target

2018-05-11 Thread Paul Nickerson

I just installed Windows 10's April 2018 Update, and it looks like it
enabled Fast Startup again.

I've got Ubuntu 18.04 now, with duplicity/bionic,now 0.7.17-0ubuntu1
amd64 [installed]. And the bug remains:

Traceback (innermost last):
  File "/usr/bin/duplicity", line 1555, in 
with_tempdir(main)
  File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
  File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
  File "/usr/bin/duplicity", line 1523, in do_backup
incremental_backup(sig_chain)
  File "/usr/bin/duplicity", line 668, in incremental_backup
globals.backend)
  File "/usr/bin/duplicity", line 454, in write_multivol
(tdp, dest_filename, vol_num)))
  File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
return self.__run_synchronously(fn, params)
  File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
ret = fn(*params)
  File "/usr/bin/duplicity", line 453, in 
vol_num: put(tdp, dest_filename, vol_num),
  File "/usr/bin/duplicity", line 342, in put
backend.put(tdp, dest_filename)
  File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in 
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
  File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
 UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)

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

Title:
  ASCII decode error, but not due to filenames in backup target

Status in Duplicity:
  Fix Released
Status in duplicity package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 17.10, I have deja-dup 36.2-0ubuntu1 installed. When I run
  "DEJA_DUP_DEBUG=1 deja-dup", it starts a backup as soon as it opens,
  as expected. But the backup fails. I get the following at the end of
  the output. I tried uninstalling Dropbox and deleting its .dropbox-
  dist directory, and then deja-dup crashed when trying to back up a
  completely different file (but the same byte in the same position). So
  I don't think this is due to any of the filenames I have in my backup
  target. I also tried a few commands to find non-ASCII filenames, with
  no luck. I'm not sure what else I can do to troubleshoot.

  
  DUPLICITY: INFO 4 
'home/paul/.dropbox-dist/dropbox-lnx.x86_64-38.4.27/PyQt5.QtGui.so'
  DUPLICITY: . A 
home/paul/.dropbox-dist/dropbox-lnx.x86_64-38.4.27/PyQt5.QtGui.so

  DUPLICITY: DEBUG 1
  DUPLICITY: . Removing still remembered temporary file 
/home/paul/.cache/deja-dup/1499b6292f58faddd30853ffbbfefcf6/duplicity-S72EWc-tempdir/mktemp-hYd54u-1

  DUPLICITY: DEBUG 1
  DUPLICITY: . Removing still remembered temporary file 
/home/paul/.cache/deja-dup/1499b6292f58faddd30853ffbbfefcf6/duplicity-VyBN42-tempdir/mktemp-BO1DKJ-1

  DUPLICITY: INFO 11
  DUPLICITY: . AsyncScheduler: running task synchronously (asynchronicity 
disabled)

  DUPLICITY: INFO 1
  DUPLICITY: . Writing duplicity-full.20171102T205615Z.vol1.difftar.gz

  DUPLICITY: DEBUG 1
  DUPLICITY: . Releasing lockfile 
/home/paul/.cache/deja-dup/1499b6292f58faddd30853ffbbfefcf6/lockfile.lock

  DUPLICITY: DEBUG 1
  DUPLICITY: . Removing still remembered temporary file 
/tmp/duplicity-c9BMvB-tempdir/mktemp-RtijDc-270

  DUPLICITY: DEBUG 1
  DUPLICITY: . Removing still remembered temporary file 
/tmp/duplicity-c9BMvB-tempdir/mkstemp-3cxG5G-1

  DUPLICITY: ERROR 30 UnicodeDecodeError
  DUPLICITY: . Traceback (most recent call last):
  DUPLICITY: .   File "/usr/bin/duplicity", line 1546, in 
  DUPLICITY: . with_tempdir(main)
  DUPLICITY: .   File "/usr/bin/duplicity", line 1540, in with_tempdir
  DUPLICITY: . fn()
  DUPLICITY: .   File "/usr/bin/duplicity", line 1391, in main
  DUPLICITY: . do_backup(action)
  DUPLICITY: .   File "/usr/bin/duplicity", line 1510, in do_backup
  DUPLICITY: . full_backup(col_stats)
  DUPLICITY: .   File "/usr/bin/duplicity", line 575, in full_backup
  DUPLICITY: . globals.backend)
  DUPLICITY: .   File "/usr/bin/duplicity", line 456, in write_multivol
  DUPLICITY: . (tdp, dest_filename, vol_num)))
  DUPLICITY: .   File 
"/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 146, in 
schedule_task
  DUPLICITY: . return self.__run_synchronously(fn, params)
  DUPLICITY: .   File 
"/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 172, in 
__run_synchronously
  DUPLICITY: . ret = fn(*params)
  DUPLICITY: .   File "/usr/bin/duplicity", line 455, in 
  DUPLICITY: . vol_num: put(tdp, dest_filename, vol_num),
  DUPLICITY: .   File "/usr/bin/duplicity", line 344, in put
  DUPLICITY: . backend.put(tdp, dest_filename)
  DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", 
line 376, in inner_retry

[Desktop-packages] [Bug 1770774] [NEW] ubuntu-MATE - top of windows disappear under panel

2018-05-11 Thread Chris Guiver

Public bug reported:

UBUNTU-MATE or MATE (1.20.1)

// see also https://github.com/mate-desktop/mate-panel/issues/303
rflbianco's comment may 10, 2018  (I opted not to comment there)

I have two monitors, one above & slightly to right of the primary one
(primary is bottom, and to left of one above it; overlap is about 66%).
When I typed `ubuntu-bug` into mate-terminal and apport window opened,
the top of it including minimize/maximize/close buttons were hidden by
top panel (primary or my lower monitor).

My theme is Panetheon (with dock on left on bottom/primary monitor with
'show hide buttons' naturally ticked to enable me to access hidden top
of windows.

Most new windows are opened top left on my primary (lower) monitor  (eg.
just now I opened "about me" & its top left without minimize/close or
"Mugshot title bar visible UNTIL i click 'hide panel'. To view the
button top left of window requires me to click 'hide' on the right side
of monitor which requires mouse movement.

This does NOT cause crashes or anything. Its just annoying and I'm
opting to use XFCE (which is also installed on my box).  It's been doing
this since I dist-upgraded to 18.04 (from 17.10). I can re-produce
easily as top left appears to be default position for windows to open
(with exceptions; eg. chromium doesn't open top left under panel, but in
its last position).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: MATE
Date: Sat May 12 09:55:31 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.10, 4.15.0-19-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Radeon HD 6350 [103c:2126]
InstallationDate: Installed on 2017-11-16 (176 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Dell Inc. OptiPlex 960
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=afa7971f-3dd5-4b30-9c98-0af3e56a6f2b ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/05/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0F428D
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: 1701283234
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/05/2011:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0F428D:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: OptiPlex 960
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  ubuntu-MATE - top of windows disappear under panel

Status in xorg package in Ubuntu:
  New

Bug description:
  UBUNTU-MATE or MATE (1.20.1)

  // see also https://github.com/mate-desktop/mate-panel/issues/303
  rflbianco's comment may 10, 2018  (I opted not to comment there)

  I have two monitors, one above & slightly to right of the primary one
  (primary is bottom, and to left of one above it; overlap is about
  66%).  When I typed `ubuntu-bug` into mate-terminal and apport window
  opened, the top of it including minimize/maximize/close buttons were
  hidden by top panel (primary or my lower monitor).

  My theme is Panetheon (with dock on left on bottom/primary monitor
  with 'show hide buttons' naturally ticked to enable me to access
  hidden top of windows.

  Most new windows are opened top left on my primary (lower) monitor
  (eg. just now I opened "about me" & its top left without
  minimize/close or "Mugshot title bar visible UNTIL i click 'hide
  panel'. To view the button top left of window requires me to click
  'hide' on the right side of monitor which

[Desktop-packages] [Bug 1747171] Re: "New Tab" disappeared from the GNOME Terminal menu

This bug was fixed in the package gnome-terminal - 3.28.1-1ubuntu2

---
gnome-terminal (3.28.1-1ubuntu2) cosmic; urgency=medium

  * Restore File > New Tab menu item. Thanks Debarshi Ray for the suggestion.
(LP: #1747171)

 -- Jeremy Bicha   Fri, 11 May 2018 17:15:21 -0400

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

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

Title:
  "New Tab" disappeared from the GNOME Terminal menu

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

Bug description:
  Impact
  --
  GNOME Terminal removed the New Tab menu option before Ubuntu 16.04 LTS. Tabs 
are a really popular feature in terminals and it's annoying to have this 
feature hidden.

  Test Case
  -
  Install the update.
  Close all terminals.
  Open a terminal.
  In the File menu should be New Tab and New Window menu items. Both should 
work.

  Regression Potential
  
  Restoring the previous behavior is now a one-line hidden configure option.

  Enabling that option removes the "Open new terminals in" option
  mentioned in the workaround.

  This build option is set in Fedora and is not believed to have any
  negative consequences.

  Other Info
  --
  There are no plans at this time to try to backport this change to Ubuntu 
16.04 LTS or 17.10 because it would not be a simple one-line change there. (The 
configure flag was enabled in git commit 0820b385 .)

  https://debarshiray.wordpress.com/2018/05/11/gnome-terminal-separate-
  menu-items-for-opening-tabs-and-windows/

  Workaround
  --
  In Edit > Preferences (General) you can set "Open new terminals in Tab". Now, 
the File > New Window menu item opens a new tab instead of a new window.

  Original Bug Report
  ---
  There is not a "New Tab" option in the file menu of GNOME Terminal anymore on 
Ubuntu Bionic. It looks like it disappeared after some recent update. However, 
the CTRL + Shift + T shortcut works as expected.

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

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

[Desktop-packages] [Bug 1770773] [NEW] HSP/HFP not working

2018-05-11 Thread Mike Holmes

Public bug reported:

Using the 18.04 release, paired bluetooth headsets' do not work in
HSP/HFP mode.

[Steps to reproduce]
1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build
2. Go to sound settings > output tab > try switching mode to HSP/HFP mode
3. Press the "test sound" button and try playing sound
4. Go to the input tab and check if bluetooth headset mic is listed

[Expected result]
After step 3, a window for mono audio test should pop up
After step 4, the input tab should list a bluetooth headset mic device

[Actual result]
After step 3, the window that pops up is for stereo (A2DP) audio test
After step 4, the input tab does not list any bluetooth headset mic

Logitech H800

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

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

Title:
  HSP/HFP not working

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Using the 18.04 release, paired bluetooth headsets' do not work in
  HSP/HFP mode.

  [Steps to reproduce]
  1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build
  2. Go to sound settings > output tab > try switching mode to HSP/HFP mode
  3. Press the "test sound" button and try playing sound
  4. Go to the input tab and check if bluetooth headset mic is listed

  [Expected result]
  After step 3, a window for mono audio test should pop up
  After step 4, the input tab should list a bluetooth headset mic device

  [Actual result]
  After step 3, the window that pops up is for stereo (A2DP) audio test
  After step 4, the input tab does not list any bluetooth headset mic

  Logitech H800

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

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

[Desktop-packages] [Bug 1770748] Re: ilmbase symbols files were dropped by the forced merge

2018-05-11 Thread Bug Watch Updater

** Changed in: ilmbase (Debian)
   Status: Unknown => Confirmed

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

Title:
  ilmbase symbols files were dropped by the forced merge

Status in ilmbase package in Ubuntu:
  New
Status in ilmbase package in Debian:
  Confirmed

Bug description:
  the last ilmbase forced sync dropped the ilmbase symbols files "just
  for convenience", because maintenance apparently costs too much
  effort.  So we are dropping the patches which we required for the
  package to be in main.

  I don't think this is a sensible move, and the symbol files should be
  re-added before the package migrates to the release pocket.

  I also think that the behavior of "delegating" these changes to
  another maintenance team is inappropriate.

  Setting the block-proposed flag for now, until the symbol filed are
  re-added again.

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

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

[Desktop-packages] [Bug 1770667] Re: package python-libxml2 2.9.1+dfsg1-3ubuntu4.7 failed to install/upgrade: subprocess new pre-removal script returned error exit status 126

2018-05-11 Thread Mattia Rizzolo

/var/lib/dpkg/info/apport.prerm: 14: /var/lib/dpkg/info/apport.prerm:
pyclean: Permission denied

and then

/var/lib/dpkg/tmp.ci/prerm: 14: /var/lib/dpkg/tmp.ci/prerm: pyclean:
Permission denied

and then

/var/lib/dpkg/info/apport.postinst: 13:
/var/lib/dpkg/info/apport.postinst: pycompile: Permission denied


etc.

Your system is in a weird state, the package is not at fault.  Please
contact user support.

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

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

Title:
  package python-libxml2 2.9.1+dfsg1-3ubuntu4.7 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 126

Status in libxml2 package in Ubuntu:
  Invalid

Bug description:
  I keep getting an error message about python. I am a new user to
  ubuntu.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-libxml2 2.9.1+dfsg1-3ubuntu4.7
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  Uname: Linux 3.19.0-61-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Fri May 11 10:19:24 2018
  DpkgHistoryLog:
   Start-Date: 2018-05-11  10:19:23
   Commandline: apt-get install tor
   Install: tor:amd64 (0.2.4.27-1build0.14.04.1), torsocks:amd64 (1.3-3, 
automatic), tor-geoipdb:amd64 (0.2.4.27-1build0.14.04.1, automatic)
   Upgrade: python-samba:amd64 (4.3.9+dfsg-0ubuntu0.14.04.1, 
4.3.11+dfsg-0ubuntu0.14.04.14), python-libxml2:amd64 (2.9.1+dfsg1-3ubuntu4.7, 
2.9.1+dfsg1-3ubuntu4.12), apport:amd64 (2.14.1-0ubuntu3.19, 2.14.1-0ubuntu3.27)
  DuplicateSignature: package:python-libxml2:2.9.1+dfsg1-3ubuntu4.7:subprocess 
new pre-removal script returned error exit status 126
  ErrorMessage: subprocess new pre-removal script returned error exit status 126
  InstallationDate: Installed on 2016-05-15 (726 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.14
  SourcePackage: libxml2
  Title: package python-libxml2 2.9.1+dfsg1-3ubuntu4.7 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 
126
  UpgradeStatus: Upgraded to trusty on 2018-05-09 (1 days ago)

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

-- 
Mailing list: https://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 1770600] Re: Firefox v60: does not work after updating, many "DENIED" log entries.

2018-05-11 Thread Simon Déziel

Hi Daniel,

On 2018-05-11 04:46 PM, daniel CURTIS wrote:
> Thank You very much for an informations. Yes, there was some changes to
> the Sandbox (vide 'about:support'), because after update there was one
> new option with 'false' value (I have had similar issue in the past but
> it's not important now) and levels for the "Content Separation" and
> "Effective Content Separation" has changed to "4" (while in Firefox 59.0
> version it was "3") etc.
> 
> I will also add an "owner" prefix to the '@{PROC}' rules. Thanks for
> clarifications; I waited for something like this, because I had no idea
> if "owner" should be used in such situation.

When the denial message have "fsuid" equal to "ouid" it's a good hint to
try the "owner" prefix. fsuid is the UID of the file system object
accessed by the "ouid" which corresponds to the UID of the runnig
process trying to make the access. Those denials all had "fsuid=1000
ouid=1000".

> Anyway, if it's about the last rule in my report and this one mentioned
> in my comment #2: it seems, that when everything is commented, there is
> a problem with opening new tab (e.g. by clicking "+") - after ~2 hours
> of Firefox using there is an error message that "this tab has failed",
> "We can help!" etc. Everything else is working okay.
> 
> For now I decided to comment this rule, because I think it's a wrong
> rule (see my post #2 for more informations). As I already mentioned,
> "abstractions/X" file contains rule related with "/tmp/.X11-unix/X0" and
> "connect" operation. However, there is also "type" and "peer" options
> (see report; last rule) - which is not in the log entry! So, here is
> what I've done for now:
> 
> # Here are a rules from an "abstractions/X" file. However I used "rw" access. 
> Reason:
> # "r" access added because of log entries with 'requested{,denied}_mask=r' 
> (see bug report) 
> #
> /tmp/.X11-unix/* rw,

Looking at etckeeper logs, "r" was added to abstractions/X on December
21st 2016. It was apparently a local/manual fix I made on that date.

> #unix (connect, receive, send)
> #type=stream
> #peer=(addr="@/tmp/.X11-unix/X[0-9]*"), 
> 
> And everything seems to work okay: just as before update to 60.0
> version. Okay, so for now I will:
> 
> ✗ add an "owner" prefix for all '@{PROC}' rules (thanks Simon!);
> ✗ use only "/tmp/.X11-unix/* rw," rule (until more information will be 
> gathered);
> ✗ monitor the log files, journalctl(1) command etc. 
> 
> Once again: thank You Simon for an informations! I hope also that
> someone else will confirm the correctness of all these rules.
> (Especially these mentioned in bug report).
> 
> By the way: Simon, what about two rules: mentioned above "unix" and
> "dbus" rule (see bug report and 7. rule) Have you seen such an entries
> in your log files etc.? Did you have had a similar issues with firefox,
> just before adding rules (see bug report)?

I must admit I've been too lazy to do proper upstreaming of my local
Apparmor delta for firefox. I run with the following
local/usr.bin.firefox profile: https://paste.ubuntu.com/p/z5KFTQCkWC/

Since the FF profile is disabled by default, Ubuntu/Canonical folk do
not test it when releasing FF updates so you have to expect breakage if
you opted in for Apparmor containment.

It's too bad that Firefox's snap (https://snapcraft.io/firefox) is
lagging behind otherwise we'd have Apparmor protection and more.

Regards,
Simon

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

Title:
  Firefox v60: does not work after update, many "DENIED" log entries
  etc.

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Hello.

  Today, Firefox has been updated to v60. After first start there was so
  many problems: with new tab (errors), Sandbox option (one new option
  with 'false' value). There were so many issues. No website was
  working, I can not click on anything, there was no menu bar and so on.
  Firefox main windows has been resized etc.

  Anyway, there was also a lot of "DENIED" entries in a log files. Here
  are the AppArmor rules, that helped and now Firefox works okay. Maybe
  it will help someone too?

  # apparmor="DENIED" operation="capable" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" comm="firefox"capability=21 
  # capname="sys_admin" 
  #
  capability sys_admin,

  # apparmor="DENIED" operation="capable" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" comm="firefox" 
  # capability=19 capname="sys_ptrace" 
  #
  capability sys_ptrace, 

  # apparmor="DENIED" operation="capable" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" comm="Gecko_IOThread" 
  # capability=18  capname="sys_chroot" 
  #
  capability sys_chroot, 

  # NOTE: what about an "owner" prefix?
  #
  # apparmor="DENIED" operation="open" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/proc/4137/uid_map" 
  # comm="Gecko_IOThread"

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

2018-05-11 Thread Milan Pultar

I am not sure whether it is ok to post here, but I have lately found
this github repo dedicated to making Ubuntu run on XPS 9560. It works
for Ubuntu 17.10 and 18.04 will be hopefully added as well. Many of us
have this laptop and the repo partly adresses the issues mentioned here
so I thought posting the link here might not be a bad idea. I have not
tried this myself yet, but I guess installing U17.10 is the only option
now because of the drivers problem...


https://github.com/stockmind/dell-xps-9560-ubuntu-respin

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

Title:
  nvidia-390 fails to boot graphical display

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

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

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

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

[Desktop-packages] [Bug 1770762] [NEW] NetworkManager does not merge dhclient config correctly

2018-05-11 Thread ts

Public bug reported:

Adding a lease section to a dhclient config file does not work, the
closing bracket is not merged into the generated config file, leading to
a broken config file. Is this a bug?

More specific: Trying to add a static fallback IP in case DHCP does not work. I 
added into /etc/dhcp/dhclient.conf:
lease {
  interface "eno2";
  fixed-address 10.0.0.100;
  option subnet-mask 255.0.0.0;
  option routers 10.0.1.1;
  option domain-name-servers 10.0.1.1;
  renew 2 2025/1/12 00:00:01;
  rebind 2 2025/1/12 00:00:01;
  expire 2 2025/1/12 00:00:01;
}

In the resulting merged config file for the eno2-interface
/var/lib/NetworkManager/dhclient-eno2.conf, the closing "}" is missing,
so the file is broken. Running dhclient manually does work.

--
Ubuntu release: 18.04
Package version: network-manager 1.10.6-2ubuntu1

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

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

** No longer affects: ubuntu

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

Title:
  NetworkManager does not merge dhclient config correctly

Status in network-manager package in Ubuntu:
  New

Bug description:
  Adding a lease section to a dhclient config file does not work, the
  closing bracket is not merged into the generated config file, leading
  to a broken config file. Is this a bug?

  More specific: Trying to add a static fallback IP in case DHCP does not work. 
I added into /etc/dhcp/dhclient.conf:
  lease {
interface "eno2";
fixed-address 10.0.0.100;
option subnet-mask 255.0.0.0;
option routers 10.0.1.1;
option domain-name-servers 10.0.1.1;
renew 2 2025/1/12 00:00:01;
rebind 2 2025/1/12 00:00:01;
expire 2 2025/1/12 00:00:01;
  }

  In the resulting merged config file for the eno2-interface
  /var/lib/NetworkManager/dhclient-eno2.conf, the closing "}" is
  missing, so the file is broken. Running dhclient manually does work.

  --
  Ubuntu release: 18.04
  Package version: network-manager 1.10.6-2ubuntu1

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

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

[Desktop-packages] [Bug 1758363] Re: push and pop warning can generate "Operation not permitted" error

2018-05-11 Thread Philippe Cloutier

I'm sorry to report that this is not merely "cosmetic". I just noticed
there is also a behavioral impact; when such a warning is triggered
while running - for example - quilt pop 5, if the first de-application
causes the warning, only 1 patch will be popped.

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

Title:
  push and pop warning can generate "Operation not permitted" error

Status in quilt package in Ubuntu:
  New

Bug description:
  The push and pop quilt subcommands call touch for each patched file.
  The way it is called, touch can generate an error due to insufficient
  permissions, and that error is sent straight to the terminal.

  The touch call intends to set file modification times. As explained in
  https://stackoverflow.com/questions/953098/change-file-time-touch
  Linux does not allow changing mtime for a user which is neither root
  nor the user owning the file. This means that it is impossible for
  several people each owning some files to manage the same patched
  software, even if they are part of the same group and that group has
  full permissions on all files, unless they have access to a common
  account.

  Either quilt should manage times in a way that does not depend on a
  single user managing the software, or the failure can be considered
  unimportant, and quilt should just report failures differently. The
  latter approach could involve replacing touch's output with a clear
  error/warning message, limiting the number of errors displayed to 1,
  or adding an option to quiet such issues.

  cloph2@SWIKID02:/var/www/html/foncierpedia$ quilt pop
  Removing patch tracker_prevent_edit_conflict.diff
  Restoring lang/fr/language.php
  Restoring lang/fr/language.js
  Restoring templates/tiki-view_tracker_item.tpl
  Restoring tiki-view_tracker_item.php
  Restoring lib/core/Services/Tracker/Controller.php
  touch: setting times of './lang/fr/language.php': Operation not permitted
  cloph2@SWIKID02:/var/www/html/foncierpedia$ quilt push
  touch: setting times of 
'.pc/tracker_prevent_edit_conflict.diff/lang/fr/language

   .php': Operation not permitted
  Applying patch tracker_prevent_edit_conflict.diff
  patching file lang/fr/language.js
  patching file lang/fr/language.php
  patching file lib/core/Services/Tracker/Controller.php
  patching file templates/tiki-view_tracker_item.tpl
  patching file tiki-view_tracker_item.php

  Now at patch tracker_prevent_edit_conflict.diff
  cloph2@SWIKID02:/var/www/html/foncierpedia$

  
  Ubuntu 14.04.5, using quilt 0.61-1
  I could not find any hint that this is fixed in quilt 0.65.

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

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

[Desktop-packages] [Bug 1577927] Re: After upgrade, can no longer set tab titles

Fedora ships patches for this feature using this fork:

https://github.com/debarshiray/gnome-terminal

** Changed in: gnome-terminal (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  After upgrade, can no longer set tab titles

Status in GNOME Terminal:
  Unknown
Status in gnome-terminal package in Ubuntu:
  Triaged
Status in gnome-terminal package in Debian:
  Confirmed
Status in gnome-terminal package in Fedora:
  Unknown

Bug description:
  Under the previous version, 14.04 LTS, I could quickly hit 'ALT-t',
  then 's', then type in the text that would appear on that terminal
  tab. This is HUGELY IMPORTANT, as the main reason I run Linux is so
  that I can quickly and easily do my work, involving dozens of terminal
  tabs, ssh'ed into dozens of different servers. Generally, when I open
  a new tab, I label it for future reference. Imagine having a dozen
  tabs open, some of them connected to production databases, and others
  connected to development databases. I need to be able to easily
  identify which ones are which. (I also edited the config files, to
  make the active tab be red instead of grey.)

  But now that I've upgraded to 16.04 LTS, I'm crippled! I can't find
  any way to set the names of the terminal tabs. I'm not sure what I'll
  do! Go hunting for a different terminal program, maybe?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_uvm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May  3 14:23:28 2016
  InstallationDate: Installed on 2016-04-27 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1770748] Re: ilmbase symbols files were dropped by the forced merge

Could the Foundations Team please take over maintenance of ilmbase?

ilmbase was added to main with LP: #240943. It is only in main because
of imagemagick (via openexr) and the Foundations Team maintains
imagemagick.

There is nothing the Ubuntu Desktop Team needs from ilmbase and the
Ubuntu Desktop Team is not interested in manually maintaining C++
symbols across architectures every time Debian wants to update this
package.

Also, if having a symbols file is indeed Required for inclusion in main
even for C++ packages, it ought to be added to
https://wiki.ubuntu.com/MainInclusionRequirements

I understand that force syncing ilmbase today so quickly looks bad, but
it was able to clean up the 20+ openexr reverse dependencies that failed
to build because the new openexr version required ilmbase to be updated.

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

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

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

Title:
  ilmbase symbols files were dropped by the forced merge

Status in ilmbase package in Ubuntu:
  New
Status in ilmbase package in Debian:
  Unknown

Bug description:
  the last ilmbase forced sync dropped the ilmbase symbols files "just
  for convenience", because maintenance apparently costs too much
  effort.  So we are dropping the patches which we required for the
  package to be in main.

  I don't think this is a sensible move, and the symbol files should be
  re-added before the package migrates to the release pocket.

  I also think that the behavior of "delegating" these changes to
  another maintenance team is inappropriate.

  Setting the block-proposed flag for now, until the symbol filed are
  re-added again.

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

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

[Desktop-packages] [Bug 1770748] Re: ilmbase symbols files were dropped by the forced merge

I suggested on #ubuntu-devel today that a compromise that might be
acceptable for Debian while addressing the API stability concerns would
be to have a symbols file only for amd64.

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

Title:
  ilmbase symbols files were dropped by the forced merge

Status in ilmbase package in Ubuntu:
  New
Status in ilmbase package in Debian:
  Unknown

Bug description:
  the last ilmbase forced sync dropped the ilmbase symbols files "just
  for convenience", because maintenance apparently costs too much
  effort.  So we are dropping the patches which we required for the
  package to be in main.

  I don't think this is a sensible move, and the symbol files should be
  re-added before the package migrates to the release pocket.

  I also think that the behavior of "delegating" these changes to
  another maintenance team is inappropriate.

  Setting the block-proposed flag for now, until the symbol filed are
  re-added again.

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

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

[Desktop-packages] [Bug 1747171] Re: "New Tab" disappeared from the GNOME Terminal menu

** Description changed:

  Impact
  --
  GNOME Terminal removed the New Tab menu option before Ubuntu 16.04 LTS. Tabs 
are a really popular feature in terminals and it's annoying to have this 
feature hidden.
  
  Test Case
  -
  Install the update.
  Close all terminals.
  Open a terminal.
  In the File menu should be New Tab and New Window menu items. Both should 
work.
  
  Regression Potential
  
  Restoring the previous behavior is now a one-line hidden configure option.
  
  Enabling that option removes the "Open new terminals in" option
  mentioned in the workaround.
  
  This build option is set in Fedora and is not believed to have any
  negative consequences.
  
  Other Info
  --
- There are no plans at this time to try to backport this change to Ubuntu 
16.04 LTS or 17.10. If I understand the blog post correctly, it would not be a 
simple one-line change there.
+ There are no plans at this time to try to backport this change to Ubuntu 
16.04 LTS or 17.10 because it would not be a simple one-line change there. (The 
configure flag was enabled in git commit 0820b385 .)
  
  https://debarshiray.wordpress.com/2018/05/11/gnome-terminal-separate-
  menu-items-for-opening-tabs-and-windows/
  
  Workaround
  --
  In Edit > Preferences (General) you can set "Open new terminals in Tab". Now, 
the File > New Window menu item opens a new tab instead of a new window.
  
  Original Bug Report
  ---
  There is not a "New Tab" option in the file menu of GNOME Terminal anymore on 
Ubuntu Bionic. It looks like it disappeared after some recent update. However, 
the CTRL + Shift + T shortcut works as expected.

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

Title:
  "New Tab" disappeared from the GNOME Terminal menu

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

Bug description:
  Impact
  --
  GNOME Terminal removed the New Tab menu option before Ubuntu 16.04 LTS. Tabs 
are a really popular feature in terminals and it's annoying to have this 
feature hidden.

  Test Case
  -
  Install the update.
  Close all terminals.
  Open a terminal.
  In the File menu should be New Tab and New Window menu items. Both should 
work.

  Regression Potential
  
  Restoring the previous behavior is now a one-line hidden configure option.

  Enabling that option removes the "Open new terminals in" option
  mentioned in the workaround.

  This build option is set in Fedora and is not believed to have any
  negative consequences.

  Other Info
  --
  There are no plans at this time to try to backport this change to Ubuntu 
16.04 LTS or 17.10 because it would not be a simple one-line change there. (The 
configure flag was enabled in git commit 0820b385 .)

  https://debarshiray.wordpress.com/2018/05/11/gnome-terminal-separate-
  menu-items-for-opening-tabs-and-windows/

  Workaround
  --
  In Edit > Preferences (General) you can set "Open new terminals in Tab". Now, 
the File > New Window menu item opens a new tab instead of a new window.

  Original Bug Report
  ---
  There is not a "New Tab" option in the file menu of GNOME Terminal anymore on 
Ubuntu Bionic. It looks like it disappeared after some recent update. However, 
the CTRL + Shift + T shortcut works as expected.

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

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

[Desktop-packages] [Bug 1770600] Re: Firefox v60: does not work after updating, many "DENIED" log entries.

2018-05-11 Thread daniel CURTIS

Hello Simon.

Thank You very much for an informations. Yes, there was some changes to
the Sandbox (vide 'about:support'), because after update there was one
new option with 'false' value (I have had similar issue in the past but
it's not important now) and levels for the "Content Separation" and
"Effective Content Separation" has changed to "4" (while in Firefox 59.0
version it was "3") etc.

I will also add an "owner" prefix to the '@{PROC}' rules. Thanks for
clarifications; I waited for something like this, because I had no idea
if "owner" should be used in such situation.

Anyway, if it's about the last rule in my report and this one mentioned
in my comment #2: it seems, that when everything is commented, there is
a problem with opening new tab (e.g. by clicking "+") - after ~2 hours
of Firefox using there is an error message that "this tab has failed",
"We can help!" etc. Everything else is working okay.

For now I decided to comment this rule, because I think it's a wrong
rule (see my post #2 for more informations). As I already mentioned,
"abstractions/X" file contains rule related with "/tmp/.X11-unix/X0" and
"connect" operation. However, there is also "type" and "peer" options
(see report; last rule) - which is not in the log entry! So, here is
what I've done for now:

# Here are a rules from an "abstractions/X" file. However I used "rw" access. 
Reason:
# "r" access added because of log entries with 'requested{,denied}_mask=r' (see 
bug report) 
#
/tmp/.X11-unix/* rw,

#unix (connect, receive, send)
#type=stream
#peer=(addr="@/tmp/.X11-unix/X[0-9]*"), 

And everything seems to work okay: just as before update to 60.0
version. Okay, so for now I will:

✗ add an "owner" prefix for all '@{PROC}' rules (thanks Simon!);
✗ use only "/tmp/.X11-unix/* rw," rule (until more information will be 
gathered);
✗ monitor the log files, journalctl(1) command etc. 

Once again: thank You Simon for an informations! I hope also that
someone else will confirm the correctness of all these rules.
(Especially these mentioned in bug report).

By the way: Simon, what about two rules: mentioned above "unix" and
"dbus" rule (see bug report and 7. rule) Have you seen such an entries
in your log files etc.? Did you have had a similar issues with firefox,
just before adding rules (see bug report)?

Thanks, best regards.

** Summary changed:

- Firefox v60: does not work after updating, many "DENIED" log entries.
+ Firefox v60: does not work after update, many "DENIED" log entries etc.

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

Title:
  Firefox v60: does not work after update, many "DENIED" log entries
  etc.

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Hello.

  Today, Firefox has been updated to v60. After first start there was so
  many problems: with new tab (errors), Sandbox option (one new option
  with 'false' value). There were so many issues. No website was
  working, I can not click on anything, there was no menu bar and so on.
  Firefox main windows has been resized etc.

  Anyway, there was also a lot of "DENIED" entries in a log files. Here
  are the AppArmor rules, that helped and now Firefox works okay. Maybe
  it will help someone too?

  # apparmor="DENIED" operation="capable" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" comm="firefox"capability=21 
  # capname="sys_admin" 
  #
  capability sys_admin,

  # apparmor="DENIED" operation="capable" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" comm="firefox" 
  # capability=19 capname="sys_ptrace" 
  #
  capability sys_ptrace, 

  # apparmor="DENIED" operation="capable" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" comm="Gecko_IOThread" 
  # capability=18  capname="sys_chroot" 
  #
  capability sys_chroot, 

  # NOTE: what about an "owner" prefix?
  #
  # apparmor="DENIED" operation="open" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/proc/4137/uid_map" 
  # comm="Gecko_IOThread" requested_mask="w" denied_mask="w" 
  # fsuid=1000 ouid=1000 
  #
  @{PROC}/@{pid}/uid_map w,

  # NOTE: what about an "owner" prefix?
  #
  # apparmor="DENIED" operation="open" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/proc/4282/gid_map" 
  # comm="Gecko_IOThread" requested_mask="w" denied_mask="w" 
  # fsuid=1000 ouid=1000 
  #
  @{PROC}/@{pid}/gid_map w,

  # NOTE: what about an "owner" prefix?
  #
  # apparmor="DENIED" operation="open" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/pro /4282/setgroups" 
  # comm="Gecko_IOThread" requested_mask="w" denied_mask="w" 
  # fsuid=1000 ouid=1000 
  #
  @{PROC}/@{pid}/setgroups w,

  # NOTE: what about an "owner" prefix?
  #
  # apparmor="DENIED" operation="dbus_bind"  bus="session" 
  # name="org.mozilla.firefox.WAJxENJayq__" mask="bind" 
  # label="/usr/lib/firefox/firefox{,*[^s][^h]}" 
  #
  dbus bind bus=session

[Desktop-packages] [Bug 1747171] Re: "New Tab" disappeared from the GNOME Terminal menu

** Description changed:

- There is not a "New Tab" option in the file menu of GNOME Terminal
- anymore on Ubuntu Bionic. It looks like it disappeared after some recent
- update. However, the CTRL + Shift + T shortcut works as expected.
+ Impact
+ --
+ GNOME Terminal removed the New Tab menu option before Ubuntu 16.04 LTS. Tabs 
are a really popular feature in terminals and it's annoying to have this 
feature hidden.
+ 
+ Test Case
+ -
+ Install the update.
+ Close all terminals.
+ Open a terminal.
+ In the File menu should be New Tab and New Window menu items. Both should 
work.
+ 
+ Regression Potential
+ 
+ Restoring the previous behavior is now a one-line hidden configure option.
+ 
+ Enabling that option removes the "Open new terminals in" option
+ mentioned in the workaround.
+ 
+ This build option is set in Fedora and is not believed to have any
+ negative consequences.
+ 
+ Other Info
+ --
+ There are no plans at this time to try to backport this change to Ubuntu 
16.04 LTS or 17.10. If I understand the blog post correctly, it would not be a 
simple one-line change there.
+ 
+ https://debarshiray.wordpress.com/2018/05/11/gnome-terminal-separate-
+ menu-items-for-opening-tabs-and-windows/
+ 
+ Workaround
+ --
+ In Edit > Preferences (General) you can set "Open new terminals in Tab". Now, 
the File > New Window menu item opens a new tab instead of a new window.
+ 
+ Original Bug Report
+ ---
+ There is not a "New Tab" option in the file menu of GNOME Terminal anymore on 
Ubuntu Bionic. It looks like it disappeared after some recent update. However, 
the CTRL + Shift + T shortcut works as expected.

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

** Changed in: gnome-terminal (Ubuntu)
   Importance: Undecided => Medium

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

** Changed in: gnome-terminal (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: gnome-terminal (Ubuntu Bionic)
   Status: New => Triaged

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

Title:
  "New Tab" disappeared from the GNOME Terminal menu

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

Bug description:
  Impact
  --
  GNOME Terminal removed the New Tab menu option before Ubuntu 16.04 LTS. Tabs 
are a really popular feature in terminals and it's annoying to have this 
feature hidden.

  Test Case
  -
  Install the update.
  Close all terminals.
  Open a terminal.
  In the File menu should be New Tab and New Window menu items. Both should 
work.

  Regression Potential
  
  Restoring the previous behavior is now a one-line hidden configure option.

  Enabling that option removes the "Open new terminals in" option
  mentioned in the workaround.

  This build option is set in Fedora and is not believed to have any
  negative consequences.

  Other Info
  --
  There are no plans at this time to try to backport this change to Ubuntu 
16.04 LTS or 17.10. If I understand the blog post correctly, it would not be a 
simple one-line change there.

  https://debarshiray.wordpress.com/2018/05/11/gnome-terminal-separate-
  menu-items-for-opening-tabs-and-windows/

  Workaround
  --
  In Edit > Preferences (General) you can set "Open new terminals in Tab". Now, 
the File > New Window menu item opens a new tab instead of a new window.

  Original Bug Report
  ---
  There is not a "New Tab" option in the file menu of GNOME Terminal anymore on 
Ubuntu Bionic. It looks like it disappeared after some recent update. However, 
the CTRL + Shift + T shortcut works as expected.

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

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

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

2018-05-11 Thread Volodymyr Buell

Got back screen yesterday but for my case it was a disk space issue.
Booted into recovery mode, freed up space in root partition and
rebooted. Everything seems work ok after that... Apparently nvidia does
need some free space to boot up (it wasn't an issue before i think. My
system partition is really tiny so it's almost normal to have zero free
space on it)

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

Title:
  nvidia-390 fails to boot graphical display

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

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

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

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

[Desktop-packages] [Bug 1770748] [NEW] ilmbase symbols files were dropped by the forced merge

2018-05-11 Thread Matthias Klose

Public bug reported:

the last ilmbase forced sync dropped the ilmbase symbols files "just for
convenience", because maintenance apparently costs too much effort.  So
we are dropping the patches which we required for the package to be in
main.

I don't think this is a sensible move, and the symbol files should be
re-added before the package migrates to the release pocket.

I also think that the behavior of "delegating" these changes to another
maintenance team is inappropriate.

Setting the block-proposed flag for now, until the symbol filed are re-
added again.

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


** Tags: block-proposed

** Description changed:

  the last ilmbase forced sync dropped the ilmbase symbols files "just for
  convenience", because maintenance apparently costs too much effort.  So
  we are dropping the patches which we required for the package to be in
  main.
  
  I don't think this is a sensible move, and the symbol files should be
  re-added before the package migrates to the release pocket.
  
  I also think that the behavior of "delegating" these changes to another
- maintenance team is appropriate.
+ maintenance team is inappropriate.
  
  Setting the block-proposed flag for now, until the symbol filed are re-
  added again.

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

Title:
  ilmbase symbols files were dropped by the forced merge

Status in ilmbase package in Ubuntu:
  New

Bug description:
  the last ilmbase forced sync dropped the ilmbase symbols files "just
  for convenience", because maintenance apparently costs too much
  effort.  So we are dropping the patches which we required for the
  package to be in main.

  I don't think this is a sensible move, and the symbol files should be
  re-added before the package migrates to the release pocket.

  I also think that the behavior of "delegating" these changes to
  another maintenance team is inappropriate.

  Setting the block-proposed flag for now, until the symbol filed are
  re-added again.

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

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

[Desktop-packages] [Bug 1770494] Re: Does not display VT-100 control codes correctly/consistently

2018-05-11 Thread Scott

This appears fixed in Ubuntu 18.04.  I just checked in a virtualbox VM.
This can be closed.

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

Title:
  Does not display VT-100 control codes correctly/consistently

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I'm writing a shell script that draws in color to any VT-100 terminal.
  The terminal in Ubuntu consistently and randomly drops out of graphics
  mode producing huge glitches.  This does not occur in Xterm or Gnome
  Terminal on CentOS.

  Appearance:
    The image from the file below should look like a color filled square, what 
you see is a "glitch" which looks like the second half of an escape command 
followed by a lot of "a"'s where the graphical checkerboard character should be 
rendered (in Ubuntu Gnome terminal it is rendered as a cursor that is the color 
of a 50% blend between the background and foreground color, making it the best 
appearing terminal I've used)

  Reproducibility:
  It is 100% reproducible with the instructions below.

  To reproduce:
    Using the attached screen-capture.txt file:

    In Gnome-Terminal try "cat screen-capture.txt" over and over to see
  the error.

    In Gnome-Terminal try "less -r screen-capture.txt" and scale the
  terminal window to see variation

  Comments:
     I don't know if there is a problem where characters are dropped from 
stdin, or if the pipe is getting reset, or if the emulator can't keep up with 
the commands, or if there is a(n inconsisent) limit to the number of command 
codes that can be sent to the terminal. Or if it is being interrupted, or if it 
randomly resets...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-terminal 3.6.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-147.196-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-147-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 10 15:10:57 2018
  InstallationDate: Installed on 2014-12-02 (1255 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  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/1770494/+subscriptions

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

[Desktop-packages] [Bug 1770742] [NEW] Cannot find -lGL

2018-05-11 Thread DeathByDenim

Public bug reported:

I was trying to compile a OpenGL program, but it fails to compile. I
suppose the package this bug is in is really libglvnd-dev, but I could
not find that in Launchpad.

Anyway, the linking error is:
/usr/bin/x86_64-linux-gnu-ld: cannot find -lGL
collect2: error: ld returned 1 exit status

This seems to be because the symlink libGL.so is missing. If I go to 
/usr/lib/x86_64-linux-gnu and type:
  sudo ln -s libGL.so.1 libGL.so
then compiling works.

Here is a (nonsensical) test program:
#include 

int main(int argc, char *argv[])
{
glEnable(GL_DEPTH_TEST);

return 0;
}

which I compile with:
  gcc testgl.c -lGL

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libgl1 1.0.0-2ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: KDE
Date: Fri May 11 15:48:17 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-04-29 (12 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: libglvnd
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Cannot find -lGL

Status in libglvnd package in Ubuntu:
  New

Bug description:
  I was trying to compile a OpenGL program, but it fails to compile. I
  suppose the package this bug is in is really libglvnd-dev, but I could
  not find that in Launchpad.

  Anyway, the linking error is:
  /usr/bin/x86_64-linux-gnu-ld: cannot find -lGL
  collect2: error: ld returned 1 exit status

  This seems to be because the symlink libGL.so is missing. If I go to 
/usr/lib/x86_64-linux-gnu and type:
sudo ln -s libGL.so.1 libGL.so
  then compiling works.

  Here is a (nonsensical) test program:
  #include 

  int main(int argc, char *argv[])
  {
  glEnable(GL_DEPTH_TEST);

  return 0;
  }

  which I compile with:
gcc testgl.c -lGL

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgl1 1.0.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri May 11 15:48:17 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-04-29 (12 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: libglvnd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1020657] Re: spinning mouse cursor when using gnome shell

I don't have this problem when launching from the Ubuntu Dock (gnome-
shell-extension-ubuntu-dock), nor from launching form Frippery Panel
Favourites. I haven't tried the last one but I don't think this bug is
reproducible then either.

All-in-one-Places doesn't work on GNOME 3.28 on Ubuntu 18.04:

```
TypeError: Gtk.HScale.new_with_range is not a constructor

Stack trace:
  
Widgets.prototype.slider@/home/adam/.local/share/gnome-shell/extensions/all-in-one-places@jofer/prefs.js:157:22
  
buildPrefsWidget@/home/adam/.local/share/gnome-shell/extensions/all-in-one-places@jofer/prefs.js:68:22
  _selectExtension@resource:///org/gnome/shell/extensionPrefs/main.js:91:22
  wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
  _onCommandLine@resource:///org/gnome/shell/extensionPrefs/main.js:243:17
  wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
  main@resource:///org/gnome/shell/extensionPrefs/main.js:397:5
  @:1:43
```

I'm closing this bug as fixed, please change back to New if you can
reproduce this on Ubuntu 18.04 or 18.10.

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

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

Title:
  spinning mouse cursor when using gnome shell

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  When using the gnome-shell desktop environment in Ubuntu (tested on
  11.10 and 12.04) there is an annoying bug with nautilus regarding the
  mouse cursor on nautilus startup.

  When you start nautilus by clicking on the gnome-shell-icon the mouse
  cursor will keep spinning for at least half a minute. (sometimes there
  also is a spinning wheel on the top panel.

  This happens only when you have nautilus handle the desktop.

  I have found out when the bug occurs and when it does not:

  Bug occurs when:

  clicking the icon on the gnome-shell-panel
  clicking on the icon of the gnome-extension (Frippery Panel Favorites)
  clicking on the link to a subfolder of the homedirectory using the 
gnome-shell extension All-in-one-Places
  clicking on the notivication which appears when inserting a harddrive of some 
kind

  
  Bug does not occur when:

  clicking on the link to the homedirectory using the gnome-shell extension 
All-in-one-Places
  clicking on a direct desktop icon to the home folder or any other folder
  starting nautilus via terminal

  
  I also tested this using the ubuntu server version (12.04) and installing the 
hgnome shell manually without any unity files 

  
  This bug does not occur on Fedora or any other distribution using 
gnome-shell, therefore I assume it must have something to do with Ubuntu and 
Nautilus.

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

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

[Desktop-packages] [Bug 1030247] Re: Duplicate entries in left panel

I can't reproduce this issue (albeit not when launching from Places
since I don't have this button on GNOME 3.28 on Ubuntu 18.04) with Files
3.26.3-0ubuntu4 on Ubuntu 18.04. Am assuming this is fixed, please
change this back to New if you can reproduce the issue on 18.04 or
18.10.

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

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

Title:
  Duplicate entries in left panel

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Under Precise (12.04) updated to today.
  Clicking on "Places" opens the file browser (Nautilus, I believe)
  In the left panel, under the heading "Computer" there are two entries for 
"Desktop", 
  both of which when clicked give identical results in the right panel.

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

  $ apt-cache policy nautilus
  nautilus:
Installed: 1:3.4.2-0ubuntu3
Candidate: 1:3.4.2-0ubuntu3
Version table:
   *** 1:3.4.2-0ubuntu3 0
  500 http://mirror.isoc.org.il/pub/ubuntu/ precise-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.4.1-0ubuntu1 0
  500 http://mirror.isoc.org.il/pub/ubuntu/ precise/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.2-0ubuntu3
  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: Sat Jul 28 11:48:42 2012
  GsettingsChanges:
   org.gnome.nautilus.window-state geometry '1198x557+38+129'
   org.gnome.nautilus.window-state sidebar-width 373
  InstallationMedia: Backup-Precise-May-2012 12.04 - Release i386
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1032224] Re: Renaming a file causes infinite loop when going up in the folder hierarchy when text selected

I can't reproduce this on Files 3.26.3-0ubuntu4 on Ubuntu 18.04, please
change the status of the bug back to New if you can reproduce it on
Ubuntu 18.04 or 18.10.

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

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

Title:
  Renaming a file causes infinite loop when going up in the folder
  hierarchy when text selected

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  If you select a file to rename and press F2 to rename it, before
  validating the rename if you go back in the folder hierarchy while the
  text is selected to be renamed, nautilus dies (or the current tab in
  which you do the renaming dies). By dying I mean nothing can be
  clicked anymore and you get the busy mouse icon forever.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: amd64
  Date: Thu Aug  2 17:40:56 2012
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   org.gnome.nautilus.window-state maximized true
   org.gnome.nautilus.window-state side-pane-view 'tree'
   org.gnome.nautilus.window-state sidebar-width 282
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to precise on 2012-04-25 (99 days ago)

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

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

[Desktop-packages] [Bug 1000223] Re: system is working but constant beep sound is coming

Thank you for reporting this bug to Ubuntu.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.

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

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

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

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

Title:
  system is working but constant beep sound is coming

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  plz inform us how to tackle it

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: nautilus 1:2.32.0-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11
  Uname: Linux 2.6.35-27-generic i686
  Architecture: i386
  Date: Wed May 16 18:14:44 2012
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-dell-maverick-une-20101010-0
  ExecutablePath: /usr/bin/nautilus
  InstallationMedia: Ubuntu 10.10 "Maverick" - Build i386 LIVE Binary 
20101010-01:50
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus

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

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

[Desktop-packages] [Bug 1001456] Re: After right-clicking on the desktop background, the menu flickers if the cursor is moved just below "Change Desktop Background"

I can't reproduce this issue on Files 3.26.3-0ubuntu4 on Ubuntu 18.04.
Assuming fixed, please change the bug status back to New if you can
reproduce this issue on a supported release of Ubuntu.

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

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

Title:
  After right-clicking on the desktop background, the menu flickers if
  the cursor is moved just below "Change Desktop Background"

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  http://www.youtube.com/watch?v=CZCgvP1XZNM - A video showing the
  result of the bug.

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

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

[Desktop-packages] [Bug 1001399] Re: Nautilus + Ctrl-Alt-F1 -> Desktop hang

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

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

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

There is no release of Ubuntu where Unity 2D is still supported, but if
you can reproduce this issue on another version of Ubuntu then do change
the status of this bug to New.

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

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

Title:
  Nautilus + Ctrl-Alt-F1 -> Desktop hang

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  To reproduce (done it five times now):
  1. Start the computer.
  2. Select Ubuntu 2D on the login screen.
  3. Log in.
  4. Start Nautilus.
  5. Press Ctrl-Alt-F1

  What happens: The screen hangs - Nothing updates anymore. I can still
  use Alt-SysRq-REISUB, but that's all.

  What should happen: No hangs, please :)

  To ensure that the problem is really Nautilus, I tried to start all
  the programs which were running the last time it hung, one at a time,
  leaving the others on in the background, and switching to VT1 and
  back. It worked fine with no applications, GNOME Terminal, and
  Firefox, but crashed when I also opened Nautilus.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Fri May 18 20:48:10 2012
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   org.gnome.nautilus.window-state geometry '836x1023+67+80'
   org.gnome.nautilus.window-state sidebar-width 162
   org.gnome.nautilus.window-state start-with-status-bar true
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  XsessionErrors:
   gnome-session[2112]: WARNING: Could not parse desktop file 
/home/victor/.config/autostart/indicator-weather.desktop: No such file or 
directory
   gnome-session[2112]: WARNING: could not read 
/home/victor/.config/autostart/indicator-weather.desktop

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

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

[Desktop-packages] [Bug 1019429] Re: Unable to double-click or drag after a while

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

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

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

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

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

Title:
  Unable to double-click or drag after a while

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Installed Ubuntu 12.04 32-bit on a Dell Inspiron One 2310.  After a
  period of time I am unable to click on any folders. Single or double-
  click doesn't highlight/open folders respecively, and right-clicking
  doesn't bring up the context-sensitive menu that you would expect from
  right-clicking on a folder (you just get the option to create new
  folder, etc. Not rename or delete or anything like that).  Single-
  clicking an icon for an application in the Launcher does work however.

  Applications such as Google Chrome also don't respond to a right-click
  or dragging the scrollbar.  However double-click works if I go into
  System Settings... Mouse and Trackpad and use the test face. I can
  also rubber band around icons and they get highlighted, but if I try
  to move them it just starts drawing another rubber band.

  Problem has been experienced by at least one other user:
  http://ubuntuforums.org/showthread.php?p=12059885#post12059885

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic-pae 3.2.18
  Uname: Linux 3.2.0-25-generic-pae i686
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
  Date: Fri Jun 29 22:13:22 2012
  GsettingsChanges: org.gnome.nautilus.window-state geometry '800x550+65+24'
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1019482] Re: nautilus crash

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

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

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

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

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

Title:
  nautilus crash

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  nautilus crash autoreport don´t open launchpad

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.2-0ubuntu3
  Uname: Linux 3.4.4-030404-generic i686
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
  Date: Sat Jun 30 05:23:33 2012
  GsettingsChanges:
   org.gnome.nautilus.window-state geometry '800x550+238+90'
   org.gnome.nautilus.window-state sidebar-width 221
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.autostart.nautilus.autostart.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 
2012-05-20T17:42:47.474814

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

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

[Desktop-packages] [Bug 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable w

2018-05-11 Thread Michał Faflik

Installed libp11-kit-gnome-keyring:amd64 (3.28.0.2-1ubuntu1.18.04.1)
without any problems

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

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

Status in gnome-keyring package in Ubuntu:
  Fix Released
Status in gnome-keyring source package in Bionic:
  Fix Committed

Bug description:
  installation of this package failed, upgrading from 17.10.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libp11-kit-gnome-keyring 3.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May  2 01:39:47 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DuplicateSignature:
   package:libp11-kit-gnome-keyring:3.20.1-1ubuntu1
   Unpacking gnome-keyring (3.28.0.2-1ubuntu1) over (3.20.1-1ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-PlRQuy/0830-libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1_all.deb
 (--unpack):
libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not 
co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances
  ErrorMessage: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) 
is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: gnome-keyring
  Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to 
install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: 
no) is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

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

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

[Desktop-packages] [Bug 1770494] Re: Does not display VT-100 control codes correctly/consistently

2018-05-11 Thread Egmont Koblinger

What's the version of GNOME Terminal on CentOS that you're referring to,
where you don't face these issues?

GNOME Terminal (more precisely, the underlying VTE widget) was improved
a lot during the last 4 years, tons of emulation (and other) bugs were
fixed. The most relevant one is probably
https://bugzilla.gnome.org/show_bug.cgi?id=732586.

I can't reproduce the issues on Ubuntu 18.04 (gnome-terminal 3.28, vte
0.52).

I personally recommend to you to upgrade to 18.04 soon (14.04 will EOL
in a year anyway). It's pretty unlikely that these emulation fixes will
be backported to 14.04. (My guess is that GNOME Terminal in Ubuntu 16.04
is most likely already fixed.) (Disclaimer: I'm a GNOME Terminal / VTE
guy, but not an Ubuntu developer, so it's not Ubuntu's recommendation to
you to upgrade.)

> in Ubuntu Gnome terminal it is rendered as a cursor that is the color
of a 50% blend between the background and foreground color, making it
the best appearing terminal I've used

Thanks; not everyone shares your opinion though, see
https://bugzilla.gnome.org/show_bug.cgi?id=778122 :)

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

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

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

Title:
  Does not display VT-100 control codes correctly/consistently

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I'm writing a shell script that draws in color to any VT-100 terminal.
  The terminal in Ubuntu consistently and randomly drops out of graphics
  mode producing huge glitches.  This does not occur in Xterm or Gnome
  Terminal on CentOS.

  Appearance:
    The image from the file below should look like a color filled square, what 
you see is a "glitch" which looks like the second half of an escape command 
followed by a lot of "a"'s where the graphical checkerboard character should be 
rendered (in Ubuntu Gnome terminal it is rendered as a cursor that is the color 
of a 50% blend between the background and foreground color, making it the best 
appearing terminal I've used)

  Reproducibility:
  It is 100% reproducible with the instructions below.

  To reproduce:
    Using the attached screen-capture.txt file:

    In Gnome-Terminal try "cat screen-capture.txt" over and over to see
  the error.

    In Gnome-Terminal try "less -r screen-capture.txt" and scale the
  terminal window to see variation

  Comments:
     I don't know if there is a problem where characters are dropped from 
stdin, or if the pipe is getting reset, or if the emulator can't keep up with 
the commands, or if there is a(n inconsisent) limit to the number of command 
codes that can be sent to the terminal. Or if it is being interrupted, or if it 
randomly resets...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-terminal 3.6.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-147.196-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-147-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 10 15:10:57 2018
  InstallationDate: Installed on 2014-12-02 (1255 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  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/1770494/+subscriptions

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

[Desktop-packages] [Bug 988666] Re: Error creating folder in Nautilus.

MonoDevelop is no longer available in Software so I installed it with
`flatpak install --user --from https://download.mono-
project.com/repo/monodevelop.flatpakref` as per
http://www.monodevelop.com/download/linux/ This is version 7.3.3 (build
5).

This no longer seems to be a problem in that version of MonoDevelop (I'm
on Ubuntu 18.04).

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

Title:
  Error creating folder in Nautilus.

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Steps:
  1. Install MonoDevelop from Ubuntu Store
  2. Open MonoDevelop
  3. Click "Start New Solution"
  4. Select "Console Project"
  5. Enter any "Name"
  6. Click on "Browse..." button
  7. Press "Create New Folder"
  8. Wait few seconds...
  ... why this happens?

  Video was made with DesktopRecorder: http://youtu.be/BuJzO6Z3zug
  ps.
  use HD on YouTube

  Q: https://answers.launchpad.net/ubuntu/+source/nautilus/+question/194713
  --- 
  ApportVersion: 2.0.1-0ubuntu6
  Architecture: i386
  DistroRelease: Ubuntu 12.04
  GsettingsChanges:
   org.gnome.nautilus.window-state geometry '877x688+236+27'
   org.gnome.nautilus.window-state maximized true
   org.gnome.nautilus.window-state sidebar-width 240
   org.gnome.nautilus.window-state start-with-status-bar true
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  Package: nautilus 1:3.4.1-0ubuntu1
  PackageArchitecture: i386
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Tags:  precise
  Uname: Linux 3.2.0-23-generic i686
  UpgradeStatus: Upgraded to precise on 2012-04-02 (23 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

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

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

[Desktop-packages] [Bug 988666] Re: Error creating folder in Nautilus.

And I'm on Files 3.26.3-0ubuntu4

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

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

Title:
  Error creating folder in Nautilus.

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Steps:
  1. Install MonoDevelop from Ubuntu Store
  2. Open MonoDevelop
  3. Click "Start New Solution"
  4. Select "Console Project"
  5. Enter any "Name"
  6. Click on "Browse..." button
  7. Press "Create New Folder"
  8. Wait few seconds...
  ... why this happens?

  Video was made with DesktopRecorder: http://youtu.be/BuJzO6Z3zug
  ps.
  use HD on YouTube

  Q: https://answers.launchpad.net/ubuntu/+source/nautilus/+question/194713
  --- 
  ApportVersion: 2.0.1-0ubuntu6
  Architecture: i386
  DistroRelease: Ubuntu 12.04
  GsettingsChanges:
   org.gnome.nautilus.window-state geometry '877x688+236+27'
   org.gnome.nautilus.window-state maximized true
   org.gnome.nautilus.window-state sidebar-width 240
   org.gnome.nautilus.window-state start-with-status-bar true
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  Package: nautilus 1:3.4.1-0ubuntu1
  PackageArchitecture: i386
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Tags:  precise
  Uname: Linux 3.2.0-23-generic i686
  UpgradeStatus: Upgraded to precise on 2012-04-02 (23 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

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

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

[Desktop-packages] [Bug 991368] Re: nautilus does not seem to fork when run from terminal

Filed upstream at https://gitlab.gnome.org/GNOME/nautilus/issues/423

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

Title:
  nautilus does not seem to fork when run from terminal

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Usually, launching nautilus from a terminal used to give the prompt
  back. It does not anymore.

  What I expect to happen is this (comments are within "[]"):

  ~$ cd Documents
  ~/Documents$ nautilus .
  [Here, a nautilus window opens show contents of ~/Documents.]
  ~/Documents$ 

  But what happens is this:

  ~$ cd Documents
  ~/Documents$ nautilus .
  Initializing nautilus-gdu extension
  [Here, I don't get the prompt back. Only after I close the resulting nautilus 
window, I get the prompt back.]
  Shutting down nautilus-gdu extension
  ~/Documents$

  Further information:

  $ lsb_release -dr
  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  $ apt-cache policy nautilus
  nautilus:
Installed: 1:3.4.1-0ubuntu1
Candidate: 1:3.4.1-0ubuntu1
Version table:
   *** 1:3.4.1-0ubuntu1 0
  500 http://se.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 991368] Re: nautilus does not seem to fork when run from terminal

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

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

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

Title:
  nautilus does not seem to fork when run from terminal

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Usually, launching nautilus from a terminal used to give the prompt
  back. It does not anymore.

  What I expect to happen is this (comments are within "[]"):

  ~$ cd Documents
  ~/Documents$ nautilus .
  [Here, a nautilus window opens show contents of ~/Documents.]
  ~/Documents$ 

  But what happens is this:

  ~$ cd Documents
  ~/Documents$ nautilus .
  Initializing nautilus-gdu extension
  [Here, I don't get the prompt back. Only after I close the resulting nautilus 
window, I get the prompt back.]
  Shutting down nautilus-gdu extension
  ~/Documents$

  Further information:

  $ lsb_release -dr
  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  $ apt-cache policy nautilus
  nautilus:
Installed: 1:3.4.1-0ubuntu1
Candidate: 1:3.4.1-0ubuntu1
Version table:
   *** 1:3.4.1-0ubuntu1 0
  500 http://se.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1770731] [NEW] multimonitor display artifacts

2018-05-11 Thread nixderek

Public bug reported:

On Ubuntu 18.04, running nvidia-390 driver (on a GTX 1080), and gnome
shell 3.28.1.

I have a 3 monitor setup. When I open a terminal in the middle window
and some other window, like nautilus on the left, and quickly drag the
nautilus window to the right, covering the terminal, and back without
releasing the mouse, a flickering ghost of the window remains on the
terminal for about a minute or so.

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

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

Title:
  multimonitor display artifacts

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  On Ubuntu 18.04, running nvidia-390 driver (on a GTX 1080), and gnome
  shell 3.28.1.

  I have a 3 monitor setup. When I open a terminal in the middle window
  and some other window, like nautilus on the left, and quickly drag the
  nautilus window to the right, covering the terminal, and back without
  releasing the mouse, a flickering ghost of the window remains on the
  terminal for about a minute or so.

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

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

[Desktop-packages] [Bug 1438789] Re: New feature : drag one file and drop onto another file to create a folder with both the files

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

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

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

Title:
  New feature : drag one file and drop onto another file to create a
  folder with both the files

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Some one probably thought of this but this feature should be there in
  nautilus just like it is in mobile operating systems. Ubuntu 14.04

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

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

[Desktop-packages] [Bug 1438789] Re: New feature : drag one file and drop onto another file to create a folder with both the files

Filed upstream at https://gitlab.gnome.org/GNOME/nautilus/issues/422

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

Title:
  New feature : drag one file and drop onto another file to create a
  folder with both the files

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Some one probably thought of this but this feature should be there in
  nautilus just like it is in mobile operating systems. Ubuntu 14.04

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

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

[Desktop-packages] [Bug 988134] Re: gedit opening twice instead of in new tab

This seems to be fixed as of Files 3.26.3-0ubuntu4 and Text Editor
3.28.1-1ubuntu1 on Ubuntu 18.04.

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

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

Title:
  gedit opening twice instead of in new tab

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  I apologize if in advance if I'm filing this bug in the wrong place. This 
problem is related to gedit, but may be related to other programs too?
  If I have gedit already open with a file, then click on a text file in 
nautilus, it starts a new instance of gedit instead of opening it in a new tab. 
Clicking another text file in nautilus opens it in a new tab in the new gedit 
instance.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
  Uname: Linux 3.2.0-23-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: i386
  Date: Tue Apr 24 21:58:04 2012
  GsettingsChanges:
   org.gnome.nautilus.window-state geometry '785x415+237+24'
   org.gnome.nautilus.window-state sidebar-width 125
   org.gnome.nautilus.window-state start-with-status-bar true
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1478132] Re: When "Icons on Desktop" is off still no Desktop in side bar in Nautilus

Nikita could you clarify what you mean here please? Do you want Desktop
to be a shortcut in Files when icons are enabled on the desktop or when
they're not? And why?

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

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

Title:
  When "Icons on Desktop" is off still no Desktop in side bar in
  Nautilus

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I find that even when turning off "Icons on Desktop", that "Desktop"
  still does not appear as a place to which you can navigate to in the
  Nautilus side bar. I would expect it to, and then disappear again if
  the option gets disabled.

  ---

  OS Information:

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 15.04
  Release:  15.04
  Codename: vivid

  Package Information:

  gnome-tweak-tool:
    Installed: 3.14.2-2
    Candidate: 3.14.2-2
    Version table:
   *** 3.14.2-2 0
  500 http://gb.archive.ubuntu.com/ubuntu/ vivid/universe amd64 
Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1770473] Re: Don't hardcode Ubuntu font name in Settings > Details

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

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

  * Rename ubuntu-gnome-version.patch to distro-logo.patch for proposed
upstreaming to Debian. Drop the hardcoded use of the Ubuntu font.
(LP: #1770473)
  * debian/control.in:
- Drop now unnecessary fonts-ubuntu dependency
- Don't recommend libnss-myhostname since systemd-resolved handles this
  functionality (LP: #1766575)
- Demote network-manager-gnome dependency back to recommends
  (LP: #1770673)
- Depend on system-config-printer instead of system-config-printer-common
  for the Additional Printer Settings button (LP: #1770695)
  * Add 0007-fix-open-last-page.patch:
- Proposed patch fixes the "open last opened page" feature for Devices and
  Details pages (LP: #1770699)

 -- Jeremy Bicha   Fri, 11 May 2018 12:59:17 -0400

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

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

Title:
  Don't hardcode Ubuntu font name in Settings > Details

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

Bug description:
  Impact
  --
  On the About screen found in Settings > Details, the distro name and version 
(Ubuntu 18.04 LTS) is hard-coded to use the Ubuntu font.

  While the rest of the distro-logo.patch (or ubuntu-gnome-
  version.patch) has a reasonable chance of being applied upstream, that
  tweak would need to be a permanent Ubuntu patch.

  The Ubuntu patch causes an issue for derivatives that are not Ubuntu
  like System76's Pop!_OS. They could remove or modify the Ubuntu patch,
  but it might be nicer to derivatives if they didn't need to do that.

  Test Case
  -
  1. From Ubuntu 18.04 LTS, open the Activities Overview.
  2. Enter About and open the Settings > About screen.

  Does the Ubuntu version number look ok?

  3. Install GNOME Tweaks
  4. Open GNOME Tweaks. Switch to the Fonts page and change the interface font 
to a recognizable font.
  5. Look at the Settings > About window. Does the Ubuntu version number use 
that font?

  Regression Potential
  
  Users that use custom fonts won't have the Ubuntu font represent the Ubuntu 
version number.

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

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

[Desktop-packages] [Bug 1770673] Re: Don't have gnome-control-center require network-manager-gnome

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

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

  * Rename ubuntu-gnome-version.patch to distro-logo.patch for proposed
upstreaming to Debian. Drop the hardcoded use of the Ubuntu font.
(LP: #1770473)
  * debian/control.in:
- Drop now unnecessary fonts-ubuntu dependency
- Don't recommend libnss-myhostname since systemd-resolved handles this
  functionality (LP: #1766575)
- Demote network-manager-gnome dependency back to recommends
  (LP: #1770673)
- Depend on system-config-printer instead of system-config-printer-common
  for the Additional Printer Settings button (LP: #1770695)
  * Add 0007-fix-open-last-page.patch:
- Proposed patch fixes the "open last opened page" feature for Devices and
  Details pages (LP: #1770699)

 -- Jeremy Bicha   Fri, 11 May 2018 12:59:17 -0400

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

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

Title:
  Don't have gnome-control-center require network-manager-gnome

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

Bug description:
  Impact
  --
  Some people want to run a GNOME system without network-manager. Although I 
believe that's not really officially supported by Canonical/Ubuntu, we don't 
need to make things more difficult than needed for people that want to try that.

  Therefore, we're dropping the Depends to a Recommends which aligns us
  better with Debian since the major bug requiring it to be a Depends
  seems to be fixed now.

  Test Case
  --
  Install the updates
  Uninstall network-manager-gnome.
  Ensure that ubuntu-desktop and gnome-control-center are still installed.

  Regression Potential
  
  The Wi-Fi and Network panels probably will not work if NetworkManager is not 
installed and running.

  Original Bug Report
  ---
  The version of gnome-control-center in Ubuntu 18.04 now has a hard dependency 
on network-manager-gnome.

  This didn't used to be the case (in Ubuntu 16.04), and isn't the case
  for the Debian version of basically the same package (gnome-control-
  center_3.28.1-1_*.deb) - https://packages.debian.org/buster/gnome-
  control-center

  As there are many cases where network manager does more harm than good
  to a Linux PC, not being able to change any Gnome settings if you
  remove network manager seems a bit unfair.

  Is there a good reason why this is a hard dependency in the Ubuntu
  18.04 version of this package?

  Required information:
  1) The release of Ubuntu you are using:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  2) The version of the package you are using:
  gnome-control-center_3.28.1-0ubuntu1_amd64.deb

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

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

[Desktop-packages] [Bug 1770695] Re: Additional Printer Settings button requires system-config-printer

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

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

  * Rename ubuntu-gnome-version.patch to distro-logo.patch for proposed
upstreaming to Debian. Drop the hardcoded use of the Ubuntu font.
(LP: #1770473)
  * debian/control.in:
- Drop now unnecessary fonts-ubuntu dependency
- Don't recommend libnss-myhostname since systemd-resolved handles this
  functionality (LP: #1766575)
- Demote network-manager-gnome dependency back to recommends
  (LP: #1770673)
- Depend on system-config-printer instead of system-config-printer-common
  for the Additional Printer Settings button (LP: #1770695)
  * Add 0007-fix-open-last-page.patch:
- Proposed patch fixes the "open last opened page" feature for Devices and
  Details pages (LP: #1770699)

 -- Jeremy Bicha   Fri, 11 May 2018 12:59:17 -0400

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

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

Title:
  Additional Printer Settings button requires system-config-printer

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

Bug description:
  Impact
  --
  system-config-printer is only a Recommends. If it is uninstalled, then the 
Additional Printer Settings button in GNOME Settings > Printers doesn't work.

  Test Case
  -
  Install the updates.
  It should now no longer be possible to uninstall system-config-printer 
without uninstalling gnome-control-center.

  Regression Potential
  
  This doesn't really change the status quo for most people since 
system-config-printer was already part of the default install.

  Other Info
  --
  Eventually the Ubuntu Desktop team wants to remove the Additional Printer 
Settings we patch in, but there are still a few features that GNOME Settings 
doesn't have yet, like printer sharing.

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

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

[Desktop-packages] [Bug 1766575] Re: Drop libnss-myhostname recommends

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

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

  * Rename ubuntu-gnome-version.patch to distro-logo.patch for proposed
upstreaming to Debian. Drop the hardcoded use of the Ubuntu font.
(LP: #1770473)
  * debian/control.in:
- Drop now unnecessary fonts-ubuntu dependency
- Don't recommend libnss-myhostname since systemd-resolved handles this
  functionality (LP: #1766575)
- Demote network-manager-gnome dependency back to recommends
  (LP: #1770673)
- Depend on system-config-printer instead of system-config-printer-common
  for the Additional Printer Settings button (LP: #1770695)
  * Add 0007-fix-open-last-page.patch:
- Proposed patch fixes the "open last opened page" feature for Devices and
  Details pages (LP: #1770699)

 -- Jeremy Bicha   Fri, 11 May 2018 12:59:17 -0400

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

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

Title:
  Drop libnss-myhostname recommends

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

Bug description:
  Impact
  ==
  gnome-control-center added a Recommends: libnss-myhostname years ago so that 
it was possible to easily change the hostname in the Details panel. That 
dependency no longer appears to be needed since we switched to systemd-resolved.

  Test Case
  =
  sudo apt uninstall libnss-myhostname
  Restart
  Open the GNOME Settings app (gnome-control-center)
  In the left sidebar, click Devices
  Enter a different Device name in the block (let's say new-hostname)
  Open a terminal and verify that the hostname has been changed.
  Then run ping new-hostname and verify that that command works in the terminal.

  Other Info
  ==
  There are concerns about having libnss-myhostname in the default install. See 
comment 5 at LP: #1741277.

  See also LP: #1162475
  Note that /etc/hosts isn't updated regardless of whether libnss-myhostname is 
installed (I guess my bug description there was wrong but there was some kind 
of bug there.)

  Regression Potential
  
  To quote from the manpage:

  https://manpages.debian.org/unstable/nss-resolve

  "Note that systemd-resolved will synthesize DNS resource records in a
  few cases, for example for "localhost" and the current hostname, see
  systemd-resolved(8) for the full list. This duplicates the
  functionality of nss-myhostname(8), but it is still recommended (see
  examples below) to keep nss-myhostname configured in
  /etc/nsswitch.conf, to keep those names resolveable if systemd-
  resolved is not running."

  Ubuntu uses systemd-resolved by default and it's expected that users
  who don't want to use that will need to configure some things
  manually.

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

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

[Desktop-packages] [Bug 1770699] Re: Last opened page feature doesn't work if last page was a subpage

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

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

  * Rename ubuntu-gnome-version.patch to distro-logo.patch for proposed
upstreaming to Debian. Drop the hardcoded use of the Ubuntu font.
(LP: #1770473)
  * debian/control.in:
- Drop now unnecessary fonts-ubuntu dependency
- Don't recommend libnss-myhostname since systemd-resolved handles this
  functionality (LP: #1766575)
- Demote network-manager-gnome dependency back to recommends
  (LP: #1770673)
- Depend on system-config-printer instead of system-config-printer-common
  for the Additional Printer Settings button (LP: #1770695)
  * Add 0007-fix-open-last-page.patch:
- Proposed patch fixes the "open last opened page" feature for Devices and
  Details pages (LP: #1770699)

 -- Jeremy Bicha   Fri, 11 May 2018 12:59:17 -0400

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

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

Title:
  Last opened page feature doesn't work if last page was a subpage

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

Bug description:
  Impact
  ---
  GNOME 3.28 added a new feature that shows the last opened page when opening 
GNOME Settings (gnome-control-center). Due to a leftover from the previous 
design (before GNOME 3.26), this feature did not work correctly in all cases.

  It would work if run from the command line.

  It would not work if the last opened page was a subpage in the Details
  or Devices section and GNOME Settings was opened from the GUI (since
  that uses the .desktop).

  Test Case
  -
  1. Open Settings to the Details > Users panel.
  2. Close Settings
  3. From the Activities Overview, open Settings

  Settings should open to the Users panel.

  Regression Potential
  
  None. This is a simple bug fix to get the intended behavior in all situations

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

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

[Desktop-packages] [Bug 1210793] Re: Nautilus - Horizontal Bookmarks Toolbar (like firefox has)

Filed upstream at https://gitlab.gnome.org/GNOME/nautilus/issues/420

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

Title:
  Nautilus - Horizontal Bookmarks Toolbar (like firefox has)

Status in nautilus package in Ubuntu:
  New

Bug description:
  There needs to be a "View > Toolbars" menu in Nautilus.

  It would be nice if nautilus had a "Bookmarks Toolbar" (like seen in
  firefox and chromium), that would allow me to bookmark commonly
  frequented paths horizontally. If these features are popular enough to
  be available in the default installations of both Firefox and
  Chromium, that are also sure to be praised when provided in Nautilus.

  I realize you can bookmark in the left pane, but that pane is already
  cluttered with too  many default items (vertically), and I'd
  appreciate being able to bookmark local paths along a horizontal
  toolbar (one exclusively dedicated to my own custom-path-bookmarks).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Sat Aug 10 08:54:51 2013
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'800x550+267+250'"
  InstallationDate: Installed on 2013-08-03 (7 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1210800] Re: No Preference for "Show UP button"

Filed upstream: https://gitlab.gnome.org/GNOME/nautilus/issues/421

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

Title:
  No Preference for "Show UP button"

Status in nautilus package in Ubuntu:
  New

Bug description:
  I appreciate elegance, but I despise  not having an Up button in
  Ubuntu's current version of Nautilus.

  A file system is a hierarchy, and some times I just want an UP-button
  that I can repeat-click to climb that hierarchy all the way back  to
  root.

  Currently, Nautilus provides a fancy dancy button-representation of
  the hierarchy, where you can click the 2nd-to-right-most button to go
  UP a directory. But these buttons require more observation and mouse-
  movement versus repeat-clicking a good old UP button.

  Also, Nautilus currently offers a BACK button, but "back" doesn't
  always mean UP.

  Even if the developers have no intention of putting an UP button in
  the default Nautilus, I wished they'd at least provide people like me
  a custom preference to "Show UP button".

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Sat Aug 10 09:06:22 2013
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'800x550+267+250'"
  InstallationDate: Installed on 2013-08-03 (7 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1210792] Re: No Preference to "Show Text Location instead of Buttons"

Filed upstream at https://gitlab.gnome.org/GNOME/nautilus/issues/419

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

Title:
  No Preference to "Show Text Location instead of Buttons"

Status in nautilus package in Ubuntu:
  New

Bug description:
  I'm one who doesn't like the trend where file explorers are using buttons 
(exclusively) to represent the current hierarchical location you're at in the 
file system. Instead, I like to see the text representation of the path like 
this:
  /home/user/

  Unfortunately, there is no way (I've found) to set my preference in
  Nautilus.

  To see what I'd prefer, you can go here in the menu:
  Files > Enter Location

  But there is no way to set this view as default.

  I do see certain advantages to the button-hierarchy method, in that
  you can click any button to go to a particular place in the hierarchy.
  But often I despise the fact that these buttons do not have enough
  room to display the complete path back to root.

  There needs to be a "View > Toolbars" (similar to options you'd see
  the Firefox). This could potentially allow you to see both
  representations of the path at the same time.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Sat Aug 10 08:32:13 2013
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'800x550+267+250'"
  InstallationDate: Installed on 2013-08-03 (7 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1770725] Re: You can not see the image of the movie

2018-05-11 Thread Cristian Aravena Romero

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

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

Title:
  You can not see the image of the movie

Status in Gstreamer1.0:
  Unknown
Status in gstreamer1.0 package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  Hello,

  You can not see the image of the movie.

  Regards,
  --
  Cristian Aravena Romero (caravena)

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

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

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

[Desktop-packages] [Bug 1452084] Re: Segmentation fault whilst opening Rubbish Bin/ trash://

As far as I understand, Fix Committed is the wrong status for the Ubuntu
task since the fix is not committed into Ubuntu.

I'm waiting for someone to rebuild the Files Nightly Flatpak (the last
build was 2018-03-18 08:53:15 +) since I don't really want to build
master by hand.

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

** No longer affects: nautilus

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

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

Title:
  Segmentation fault whilst opening Rubbish Bin/ trash://

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Package version 1:3.14.2-0ubuntu9 from http://gb.archive.ubuntu.com/ubuntu/ 
vivid/main amd64 Packages
  Ubuntu 15.04 amd64 on an i5-4670K CPU

  Hi, I'm currently getting a consistent SIGSEGV from Nautilus when
  attempting to open the rubbish bin. This happens whether I click the
  bookmark on the left or instantaneously if I run `nautilus trash://`.
  The crash occurs before the icons have fully loaded, but a second
  after the rubbish bin is selected.

  I installed the debug symbols for nautilus and ran with gdb and got
  the following output:

  (gdb) run
  Starting program: /usr/bin/nautilus 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

  (nautilus:21736): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen:
  assertion 'GDK_IS_SCREEN (screen)' failed

  (nautilus:21736): GLib-GObject-WARNING **: invalid (NULL) pointer
  instance

  (nautilus:21736): GLib-GObject-CRITICAL **: g_signal_connect_object: 
assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
  [Thread 0x77f8ba00 (LWP 21736) exited]
  [Inferior 1 (process 21736) exited normally]
  (gdb) run
  Starting program: /usr/bin/nautilus 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  nautilus-wipe-Message: Initializing
  [New Thread 0x7fffe9017700 (LWP 22649)]
  [Thread 0x7fffe9017700 (LWP 22649) exited]
  [New Thread 0x7fffc1347700 (LWP 22680)]
  [New Thread 0x7fffe35f1700 (LWP 22651)]
  [New Thread 0x7fffe3fff700 (LWP 22650)]
  [New Thread 0x7fffe9818700 (LWP 22648)]

  Program received signal SIGSEGV, Segmentation fault.
  0x7372332e in __GI__IO_default_xsputn (f=0x7f7ff5f0, 
data=0x50e080, n=6) at genops.c:447
  447   genops.c: No such file or directory.

  I can provide more info if needed as I can easily reproduce the bug. I
  know a little about using gdb as well, but may need a bit of guidance
  as I'm no hardened C programmer. Thanks!

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

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

[Desktop-packages] [Bug 1770725] [NEW] You can not see the image of the movie

2018-05-11 Thread Cristian Aravena Romero

Public bug reported:

Hello,

You can not see the image of the movie.

Regards,
--
Cristian Aravena Romero (caravena)

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

** Affects: gstreamer1.0
 Importance: Unknown
 Status: Unknown

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


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

** Summary changed:

- [Wayland] You can not see the image of the movie
+ You can not see the image of the movie

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

** Also affects: gstreamer1.0 via
   https://bugzilla.gnome.org/show_bug.cgi?id=796033
   Importance: Unknown
   Status: Unknown

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

Title:
  You can not see the image of the movie

Status in Gstreamer1.0:
  Unknown
Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Hello,

  You can not see the image of the movie.

  Regards,
  --
  Cristian Aravena Romero (caravena)

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

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

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

[Desktop-packages] [Bug 1767027] Re: Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu 18.04)

2018-05-11 Thread Treviño

What version of nautilus are you using?

That was a bug before 1:3.26.3-0ubuntu2, but it was fixed in that
revision

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

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

Title:
  Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu
  18.04)

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to Ubuntu 18.04 prerelease from Ubuntu 17.10 and am finding
  that Nautilus searches all subfolders when I start typing, not just
  the present folder, even though I have the "search only current
  folder" option selected in its preferences, and "Only searching the
  current folder" does appear in the GUI as I am searching. Nonetheless
  results appear from subfolders (which I wouldn't mind, but which I
  turn off due to its poor performance compared to current-folder-only).

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

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

[Desktop-packages] [Bug 1770600] Re: Firefox v60: does not work after updating, many "DENIED" log entries.

2018-05-11 Thread Simon Déziel

@Lonnie, it is already released, see the security announcement:
https://usn.ubuntu.com/3645-1/

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

Title:
  Firefox v60: does not work after updating, many "DENIED" log entries.

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Hello.

  Today, Firefox has been updated to v60. After first start there was so
  many problems: with new tab (errors), Sandbox option (one new option
  with 'false' value). There were so many issues. No website was
  working, I can not click on anything, there was no menu bar and so on.
  Firefox main windows has been resized etc.

  Anyway, there was also a lot of "DENIED" entries in a log files. Here
  are the AppArmor rules, that helped and now Firefox works okay. Maybe
  it will help someone too?

  # apparmor="DENIED" operation="capable" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" comm="firefox"capability=21 
  # capname="sys_admin" 
  #
  capability sys_admin,

  # apparmor="DENIED" operation="capable" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" comm="firefox" 
  # capability=19 capname="sys_ptrace" 
  #
  capability sys_ptrace, 

  # apparmor="DENIED" operation="capable" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" comm="Gecko_IOThread" 
  # capability=18  capname="sys_chroot" 
  #
  capability sys_chroot, 

  # NOTE: what about an "owner" prefix?
  #
  # apparmor="DENIED" operation="open" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/proc/4137/uid_map" 
  # comm="Gecko_IOThread" requested_mask="w" denied_mask="w" 
  # fsuid=1000 ouid=1000 
  #
  @{PROC}/@{pid}/uid_map w,

  # NOTE: what about an "owner" prefix?
  #
  # apparmor="DENIED" operation="open" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/proc/4282/gid_map" 
  # comm="Gecko_IOThread" requested_mask="w" denied_mask="w" 
  # fsuid=1000 ouid=1000 
  #
  @{PROC}/@{pid}/gid_map w,

  # NOTE: what about an "owner" prefix?
  #
  # apparmor="DENIED" operation="open" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/pro /4282/setgroups" 
  # comm="Gecko_IOThread" requested_mask="w" denied_mask="w" 
  # fsuid=1000 ouid=1000 
  #
  @{PROC}/@{pid}/setgroups w,

  # NOTE: what about an "owner" prefix?
  #
  # apparmor="DENIED" operation="dbus_bind"  bus="session" 
  # name="org.mozilla.firefox.WAJxENJayq__" mask="bind" 
  # label="/usr/lib/firefox/firefox{,*[^s][^h]}" 
  #
  dbus bind bus=session name=org.mozilla.firefox.*,

  # NOTE: this rule can be found, for example, in "abstractions/X" file. 
  # However, there is "r" in 'requested{,denied}_mask" - for '/tmp/.X11-unix/' 
  # - in log entries, so I added "r" - and now it's "rw".
  # 
  # apparmor="DENIED" operation="connect" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" 
  # name="/tmp/.X11-unix/X0" comm="firefox" requested_mask="r" denied_mask="r" 
  # fsuid=1000 ouid=0
  #
  /tmp/.X11-unix/* rw,
  unix (connect, receive, send)
type=stream
peer=(addr="@/tmp/.X11-unix/X[0-9]*"),

  Can someone check if these rules are okay? With above rules, Firefox
  v60 is working okay again: web browsing, new tabs etc. There are also
  some "segfaults" error in log files - together with "DENIED" rules.
  Here are some of them (there is a bug report on Launchpad about
  "libxul"):

  ✗ [ 3051.788218] Gecko_IOThread[4770]: segfault at 0 ip aef1b0de sp aeb1a550 
error 6 in libxul.so[aebed000+66fd000]
  ✗ Gecko_IOThread[4795]: segfault at 0 ip aef1b0de sp aeb1a550 error 6 in 
libxul.so[aebed000+66fd000]

  I hope, that above rules will help other users who will have an issues
  with a new Firefox release. Here are some technical informations:

  ● Firefox: v60.0 (32-bit)
  ● Linux kernel: 4.4.0-125-generic
  ● Release: 16.04 LTS 

  Thanks, best regards.

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

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

[Desktop-packages] [Bug 1164976] Re: support for showing cursors in nautilus

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

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

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

Title:
  support for showing cursors in nautilus

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Please add support for showing cusors in nautilus, e.g. folder
  /usr/share/icons/Adwaita/cursors/.

  Related to bug #245691.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu13
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic i686
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: i386
  Date: Fri Apr  5 12:01:34 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+223+56'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'228'
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-02-14 (49 days ago)

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

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

[Desktop-packages] [Bug 1164976] Re: support for showing cursors in nautilus

Affects Files 3.26.3-0ubuntu4 on Ubuntu 18.04 and the Files 3.28.0 Nightly 
Flatpak.
Filed upstream at https://gitlab.gnome.org/GNOME/nautilus/issues/418

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

Title:
  support for showing cursors in nautilus

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Please add support for showing cusors in nautilus, e.g. folder
  /usr/share/icons/Adwaita/cursors/.

  Related to bug #245691.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu13
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic i686
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: i386
  Date: Fri Apr  5 12:01:34 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+223+56'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'228'
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-02-14 (49 days ago)

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

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

[Desktop-packages] [Bug 1481049] Re: list view defines .iso as unknown types

I think Ubuntu should stick with upstream here really, so I'd suggest
attaching that patch on the upstream bug (and then I'll re-open the bug)
if you think the behaviour should be changed, but given they gave the
Expected Behaviour tag to my closed bug I think the matter is closed.

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

Title:
  list view defines .iso as unknown types

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  the file manager does not have iin order "type" the .iso file, as
  shown in the picture you see that I enclose, the files with the
  extension .iso not respect the line and are scattered around the
  window

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

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

[Desktop-packages] [Bug 1770721] Re: Installed the discord snap and gnome shell crashed

2018-05-11 Thread Will Cooke

** Attachment added: "syslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1770721/+attachment/5137980/+files/syslog.txt

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

Title:
  Installed the discord snap and gnome shell crashed

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I did a snap install discord, and as snapd was setting things up
  gnome-shell crashed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 11 19:12:57 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2017-08-01 (282 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (14 days ago)

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

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

[Desktop-packages] [Bug 1770721] Re: Installed the discord snap and gnome shell crashed

2018-05-11 Thread Will Cooke

And it crashed again when I uninstalled it.

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

Title:
  Installed the discord snap and gnome shell crashed

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I did a snap install discord, and as snapd was setting things up
  gnome-shell crashed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 11 19:12:57 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2017-08-01 (282 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (14 days ago)

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

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

[Desktop-packages] [Bug 1770721] [NEW] Installed the discord snap and gnome shell crashed

2018-05-11 Thread Will Cooke

Public bug reported:

I did a snap install discord, and as snapd was setting things up gnome-
shell crashed.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri May 11 19:12:57 2018
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'command-history' redacted by apport
 b'org.gnome.shell' b'app-picker-view' b'uint32 1'
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'clock-show-date' b'true'
InstallationDate: Installed on 2017-08-01 (282 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to bionic on 2018-04-27 (14 days ago)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Installed the discord snap and gnome shell crashed

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I did a snap install discord, and as snapd was setting things up
  gnome-shell crashed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 11 19:12:57 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2017-08-01 (282 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (14 days ago)

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

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

[Desktop-packages] [Bug 1770600] Re: Firefox v60: does not work after updating, many "DENIED" log entries.

2018-05-11 Thread Lonnie Lee Best

When will version 60 be released into Ubuntu 16.04.4?

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

Title:
  Firefox v60: does not work after updating, many "DENIED" log entries.

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Hello.

  Today, Firefox has been updated to v60. After first start there was so
  many problems: with new tab (errors), Sandbox option (one new option
  with 'false' value). There were so many issues. No website was
  working, I can not click on anything, there was no menu bar and so on.
  Firefox main windows has been resized etc.

  Anyway, there was also a lot of "DENIED" entries in a log files. Here
  are the AppArmor rules, that helped and now Firefox works okay. Maybe
  it will help someone too?

  # apparmor="DENIED" operation="capable" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" comm="firefox"capability=21 
  # capname="sys_admin" 
  #
  capability sys_admin,

  # apparmor="DENIED" operation="capable" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" comm="firefox" 
  # capability=19 capname="sys_ptrace" 
  #
  capability sys_ptrace, 

  # apparmor="DENIED" operation="capable" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" comm="Gecko_IOThread" 
  # capability=18  capname="sys_chroot" 
  #
  capability sys_chroot, 

  # NOTE: what about an "owner" prefix?
  #
  # apparmor="DENIED" operation="open" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/proc/4137/uid_map" 
  # comm="Gecko_IOThread" requested_mask="w" denied_mask="w" 
  # fsuid=1000 ouid=1000 
  #
  @{PROC}/@{pid}/uid_map w,

  # NOTE: what about an "owner" prefix?
  #
  # apparmor="DENIED" operation="open" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/proc/4282/gid_map" 
  # comm="Gecko_IOThread" requested_mask="w" denied_mask="w" 
  # fsuid=1000 ouid=1000 
  #
  @{PROC}/@{pid}/gid_map w,

  # NOTE: what about an "owner" prefix?
  #
  # apparmor="DENIED" operation="open" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/pro /4282/setgroups" 
  # comm="Gecko_IOThread" requested_mask="w" denied_mask="w" 
  # fsuid=1000 ouid=1000 
  #
  @{PROC}/@{pid}/setgroups w,

  # NOTE: what about an "owner" prefix?
  #
  # apparmor="DENIED" operation="dbus_bind"  bus="session" 
  # name="org.mozilla.firefox.WAJxENJayq__" mask="bind" 
  # label="/usr/lib/firefox/firefox{,*[^s][^h]}" 
  #
  dbus bind bus=session name=org.mozilla.firefox.*,

  # NOTE: this rule can be found, for example, in "abstractions/X" file. 
  # However, there is "r" in 'requested{,denied}_mask" - for '/tmp/.X11-unix/' 
  # - in log entries, so I added "r" - and now it's "rw".
  # 
  # apparmor="DENIED" operation="connect" 
  # profile="/usr/lib/firefox/firefox{,*[^s][^h]}" 
  # name="/tmp/.X11-unix/X0" comm="firefox" requested_mask="r" denied_mask="r" 
  # fsuid=1000 ouid=0
  #
  /tmp/.X11-unix/* rw,
  unix (connect, receive, send)
type=stream
peer=(addr="@/tmp/.X11-unix/X[0-9]*"),

  Can someone check if these rules are okay? With above rules, Firefox
  v60 is working okay again: web browsing, new tabs etc. There are also
  some "segfaults" error in log files - together with "DENIED" rules.
  Here are some of them (there is a bug report on Launchpad about
  "libxul"):

  ✗ [ 3051.788218] Gecko_IOThread[4770]: segfault at 0 ip aef1b0de sp aeb1a550 
error 6 in libxul.so[aebed000+66fd000]
  ✗ Gecko_IOThread[4795]: segfault at 0 ip aef1b0de sp aeb1a550 error 6 in 
libxul.so[aebed000+66fd000]

  I hope, that above rules will help other users who will have an issues
  with a new Firefox release. Here are some technical informations:

  ● Firefox: v60.0 (32-bit)
  ● Linux kernel: 4.4.0-125-generic
  ● Release: 16.04 LTS 

  Thanks, best regards.

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

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

[Desktop-packages] [Bug 1770720] [NEW] network-manager-openvpn is not working on ubuntu 18.04

2018-05-11 Thread Yannick WEBER

Public bug reported:

I'm using Ubuntu 18.04.

I installed network-manager-openvpn and as a dependency openvpn and
network-manager-openvpn-gnome.

I restarted NetworkManager with systemctl restart NetworkManager

I'm able to add new openvpn connexion trough .ovpn files but when I
click to ON to my openvpn server network-manager is doing nothing, its
not trying to connect to the openvpn server.

I think there is a bug there.

I'm open to any further questions or informations devs will need

Regards

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

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

Title:
network-manager-openvpn is not working on ubuntu 18.04

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

Bug description:
I'm using Ubuntu 18.04.

I installed network-manager-openvpn and as a dependency openvpn and
network-manager-openvpn-gnome.

I restarted NetworkManager with systemctl restart NetworkManager

I'm able to add new openvpn connexion trough .ovpn files but when I
click to ON to my openvpn server network-manager is doing nothing, its
not trying to connect to the openvpn server.

I think there is a bug there.

I'm open to any further questions or informations devs will need

Regards

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

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

[Desktop-packages] [Bug 662636] Re: File Properties in Trash to provide more information

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

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

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

Title:
  File Properties in Trash to provide more information

Status in One Hundred Papercuts:
  Invalid
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  When you select a items file properties in nautilus trash folder, it
  show provide more information like Original Folder, Trashed on:,

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

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

[Desktop-packages] [Bug 662636] Re: File Properties in Trash to provide more information

Filed upstream at https://gitlab.gnome.org/GNOME/nautilus/issues/417

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

Title:
  File Properties in Trash to provide more information

Status in One Hundred Papercuts:
  Invalid
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  When you select a items file properties in nautilus trash folder, it
  show provide more information like Original Folder, Trashed on:,

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

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

[Desktop-packages] [Bug 1767030] Re: Nautilus does not focus search bar upon typing if search bar already is visible

Filed upstream at https://gitlab.gnome.org/GNOME/nautilus/issues/416

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

Title:
  Nautilus does not focus search bar upon typing if search bar already
  is visible

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  (Nautilus 3.26.3 on Ubuntu 18.04, but bug has been present as long as
  the new search box has existed to my knowledge)

  If you start typing in nautilus, so long as no text field anywhere is
  focused, the search box will appear and get focus, so you end up
  typing into it. However, if the search box is already visible but does
  not have focus (for example, by tapping ctrl-f and then clicking
  outside the search box), then typing does not re-focus the search box.

  This is jarring since you can be looking at a normal view of a folder
  (not at search results), and out of habit expect that you can start
  typing to search. Even if you tap ctrl-f, this makes an empty search
  box *vanish*, so you have to tap ctrl-f *twice* to get it focused (or
  click on it of course)

  Solutions include:

  * Make an empty search box always vanish upon losing focus
  * Make an empty search box, if still visible, gain focus again if the user 
starts typing.

  The first solution is probably cleanest since there is no use case I
  can think of for leaving an empty search box visible if the user is
  not about to type into it.

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

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

[Desktop-packages] [Bug 1767030] Re: Nautilus does not focus search bar upon typing if search bar already is visible

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

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

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

Title:
  Nautilus does not focus search bar upon typing if search bar already
  is visible

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  (Nautilus 3.26.3 on Ubuntu 18.04, but bug has been present as long as
  the new search box has existed to my knowledge)

  If you start typing in nautilus, so long as no text field anywhere is
  focused, the search box will appear and get focus, so you end up
  typing into it. However, if the search box is already visible but does
  not have focus (for example, by tapping ctrl-f and then clicking
  outside the search box), then typing does not re-focus the search box.

  This is jarring since you can be looking at a normal view of a folder
  (not at search results), and out of habit expect that you can start
  typing to search. Even if you tap ctrl-f, this makes an empty search
  box *vanish*, so you have to tap ctrl-f *twice* to get it focused (or
  click on it of course)

  Solutions include:

  * Make an empty search box always vanish upon losing focus
  * Make an empty search box, if still visible, gain focus again if the user 
starts typing.

  The first solution is probably cleanest since there is no use case I
  can think of for leaving an empty search box visible if the user is
  not about to type into it.

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

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

[Desktop-packages] [Bug 1316873] Re: Left mouse button stops working

2018-05-11 Thread Robert Marsanyi

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

Me, too.  16.04LTS, fine for years until suddenly: left-buttons, right-
buttons (trackpad) not working consistently.

Easiest way to reproduce for me:
- while buttons work, open Thunderbird.  Auth dialog for sync'ing address book 
comes up.
- mouse pointer does not change shape.  Click on close button no longer works.  
Click on desktop Settings button, however, does.
- once I've clicked on the settings button, mouse pointer changes shape, I can 
click on close button for auth dialog.

CTRL-ALT-F1 + CTRL-ALT-F7 works to restore normal function.

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

Title:
  Left mouse button stops working

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  This  problem has plagued me for a few years across different laptops
  and Ubuntu versions. Current I am experiencing this on a Dell Inspiron
  15z running Ubuntu 14.04 LTS.

  It typically starts after I have used the chat or call feature in
  gmail, by clicking on the phone icon in the left chat margin. I am a
  Firefox user and have not tested this with chrome etc. It has not
  happened if i dont install google-talkplugin so it is quite possible
  that the plugin is to blame.

  Symptom
  ===
  The left mouse button on all attached mice - USB , Trackpad and touch - will 
not do anything  however the right mouse button continues to work.  This 
happens to all applications and also to the desktop. The keyboard continues to 
function as normal.

  When this occurs , my solution is to Alt-F4 close all windows and log
  out of the X session. When I re-login the left mouse button works as
  normal.

  
  This is an irritant and work disruptor as I have to save all browser and 
desktop applications to  safe state before I logout to reset the mouse. I will 
appreciate any soltion or workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May  6 21:41:29 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:058f]
  InstallationDate: Installed on 2014-04-17 (19 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 5523
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=f5004b03-b37f-4733-88a8-51c6f3bd0a4d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0GKGJG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/18/2013:svnDellInc.:pnInspiron5523:pvrNotSpecified:rvnDellInc.:rn0GKGJG:rvrA05:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5523
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue May  6 21:20:40 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5558 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2

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

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

[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

2018-05-11 Thread Brian Murray

** Tags added: triggers-looping

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned

Status in OEM Priority Project:
  Confirmed
Status in gnome-menus package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 13 9360 (CID 201606-22338)
  pre-installed (oem) image Xenial

  [Description]

  When I tried to perform 16.04 --> 18.04 update, the update process
  failed. The process guide me to file this bug report.

  [Steps to reproduce]
  1. Update the system to the latest stack by "sudo apt-get update; sudo 
apt-get dist-upgrade -y"
  2. Reboot
  3. Make sure /etc/update-manager/release-upgrades is able to update (The 
configuration value of "Prompt" should be "lts", namely "Prompt=lts", not 
"Prompt=never").
  4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade 
-d"
  5. During the update process, it prompts for "Configuring gdm3". There are 
two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the 
attachment for the prompt details as well.

  We should use "-d" because bionic beaver has not been officially
  released yet.

  [Expected Result]

  The release update completed and I could start using Bionic instead of
  Xenial.

  [Actual Result]

  The update process failed. It shows the error message[1] and
  automatically asking for filing this bug report.

  [1]

  Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-1ubuntu1) ...
  Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-2ubuntu6) ...
  (Reading database ... 253705 files and directories currently installed.)
  Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ...
  Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ...
  Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ...
  Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
    bamfdaemon -> gnome-menus
   packages' pending triggers which are or may be unresolvable:
    gnome-menus: /usr/share/applications
    bamfdaemon: /usr/share/applications
    libglib2.0-0:amd64: /usr/share/glib-2.0/schemas
    desktop-file-utils: /usr/share/applications
    mime-support: /usr/share/applications
  dpkg: error processing package gnome-menus (--remove):
   triggers looping, abandoned
  Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
  Processing triggers for mime-support (3.59ubuntu1) ...
  Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ...
  Errors were encountered while processing:
   gnome-menus
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/gnome-menus.0.crash'
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
    S: Send report (376.4 KB)
    V: View report
    K: Keep report file for sending later or copying to somewhere else
    I: Cancel and ignore future crashes of this program version
    C: Cancel
  Please choose (S/V/K/I/C):

  .. (a lot of them)

   qml-module-qtquick-controls2:amd64
   qml-module-org-kde-kconfig:amd64
   libunity-control-center1
   libqt5quickcontrols2-5:amd64
   libglib2.0-bin
   libkf5plasma5:amd64
   locales
   qml-module-qtqml-models2:amd64
   libkf5coreaddons5:amd64
   gir1.2-goa-1.0:amd64
   libwebkit2gtk-4.0-37:amd64
  Processing was halted because there were too many errors.

  Upgrade complete

  The upgrade has completed but there were errors during the upgrade
  process.

  To continue please press [ENTER]

  ubuntu@201606-22338:~$

  ==

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed Apr 25 22:00:01 2018
  Dependencies:

  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-04-25 (0 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  RelatedPackageVersions:
   dpkg

[Desktop-packages] [Bug 1769954] Re: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2018-05-11 Thread Brian Murray

** Tags added: triggers-unprocessed

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

Title:
  package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in desktop-file-utils package in Ubuntu:
  Confirmed

Bug description:
  run `sudo do-release-upgrade` on a relativity new 16.04 EC2 instance.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: desktop-file-utils 0.23-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Tue May  8 16:59:12 2018
  Ec2AMI: ami-70873908
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2a
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ErrorMessage: dependency problems - leaving triggers unprocessed
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: desktop-file-utils
  Title: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: 
dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-08 (0 days ago)

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

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

[Desktop-packages] [Bug 1767027] Re: Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu 18.04)

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

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

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

Title:
  Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu
  18.04)

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  I upgraded to Ubuntu 18.04 prerelease from Ubuntu 17.10 and am finding
  that Nautilus searches all subfolders when I start typing, not just
  the present folder, even though I have the "search only current
  folder" option selected in its preferences, and "Only searching the
  current folder" does appear in the GUI as I am searching. Nonetheless
  results appear from subfolders (which I wouldn't mind, but which I
  turn off due to its poor performance compared to current-folder-only).

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

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

[Desktop-packages] [Bug 1766100] Re: Desktop keeps showing files that are no longer there

I'm not able to reproduce this bug on Files 3.26.3-0ubuntu4 on Ubuntu
18.04 (at least, when downloading an image from Facebook to Desktop from
Chromium 65.0.3325.181 (277) [snap]) so I'm assuming this is Fix
Released, if you can reproduce this bug on Ubuntu 18.04 then please
change this to New.

It's not GNOME's responsibility to keep old versions of Files working on
older (but supported) versions of Ubuntu, that is Ubuntu's
responsibility, so this bug does not reflect on the alleged poor
maintenance of Files. However if you think that the default file manager
should not be GNOME Files then start a topic at
https://community.ubuntu.com/c/desktop , other appropriate places would
be #ubuntu-desktop on Freenode or the Ubuntu Desktop mailing list. You
would need to give detailed reasoning why it should be abandoned though
and clear evidence that it's not being well maintained, I've been
forwarding bugs to the Files devs and they've actually been rather
responsive (if I'm patient enough) so I think you would be hard-pressed
to show that it's actually unmaintained despite all appearances! ;)

A Bug Control member should nominate this bug for Xenial if they think
that it should be fixed by Ubuntu in that.

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

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

Title:
  Desktop keeps showing files that are no longer there

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Hours after downloading a few pdf files with  Chrome into the Desktop and 
being done with them, I went to delete them.
  I was surprised to find a file called something.pdf.chdownload. These are the 
temporary files that Chrome creates while downloading the files, then it 
renames them to their final filename without the .chrdownload suffix when they 
are complete. All of the files had been downloaded completely and succesfully 
(I had actually opened all of them) so this file shouldn't exist.

  And indeed, when I went to download it, I got an error "Cannot move 
 to trash. Delete it permanently?" (this is actually stupid in the 
first place: the reason why I'm getting this error, it turns out, is that the 
file does not exist, so it makes no sense to give me the option to permanently 
delete it, which will fail for the exact same reason).
  So I chose "delete", and got an error again, that the file could not be 
deleted. I retried several times and finally looked at "details" and found out 
that the source of the error was "no such file or directory".

  So, the file was not there.

  So why the fuck was it being shown on the desktop if it was no longer
  there? I can assume it might happen some rare times (it's a bug
  anyway) that you for some reason "miss" when a file ceases existing,
  and hence it is still falsely visible on the desktop. But there should
  come a point where Nautilus "realises" the file no longer exists and
  stops showing it. In other words, the contents of the desktop should
  be "refreshed" from time to time or on certain events. And trying to
  delete a file, triggering an error that says that the file doesn't
  fucking exist, should be such a case where you refresh the information
  and stop showing a file that doesn't exist.

  It's pathetic that you keep showing it forever until I kill and
  restart nautilus or fucking reboot.

  
  I'm sick of reporting such idiotic bugs on Nautilus. Ubuntu, for fuck's sake, 
switch to some better, decently maintained file manager. Nautilus is CRAP.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 22 18:04:34 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1369x817+258+98'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-11 (1653 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1766331] Re: nautilus preference is not remembered

Scott please could you make a screencast of your problem as per these
instructions and attach a video? https://help.gnome.org/users/gnome-
help/stable/screen-shot-record.html.en

If you can produce a screencast showing your issue then you can also
file an issue upstream and attach it to that:
https://gitlab.gnome.org/GNOME/nautilus/issues Link to your issue in
this bug when you're done :)

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

Title:
  nautilus preference is not remembered

Status in nautilus package in Ubuntu:
  New

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

  
  apt-cache policy  nautilus 
  nautilus:
Installed: 1:3.26.3-0ubuntu4
Candidate: 1:3.26.3-0ubuntu4
Version table:
   *** 1:3.26.3-0ubuntu4 500
  500 http://mirror.math.princeton.edu/pub/ubuntu bionic/main amd64 
Packages
  100 /var/lib/dpkg/status

  
  nautilus -> Files -> Preferences -> Behaviour

   changes I make here fail to be remembered for example

  by default value of  ->  Behaviour -> Open Action -> is "Double click
  to open items"

   however when I choose   "Single click to open items"

  then close nautilus and re-open nautilus that Preference change did not take
  This is also true for other Preference changes ... nautilus fails to retain 
Preference changes

  Importantly when I make same change using tool dconf-editor on a
  virgin box it correctly make the setting changes

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 23 14:51:39 2018
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-02-23 (58 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: dropbox 2015.10.28

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

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

[Desktop-packages] [Bug 1726919] Re: Ubuntu 17.10 desktops corrupted

2018-05-11 Thread peterzay

As per comment #9, I can no longer test this issue.

If you can reproduce this bug report by changing login options and then
"fix" by changing those options back, then please close this case.

Otherwise, wait for others to trip over this "bug" and enlist their
help.

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

Title:
  Ubuntu 17.10 desktops corrupted

Status in nautilus package in Ubuntu:
  New

Bug description:
  The following users were installed:

  admin from DVD install (login with X option)
  user id 1001 (login with default Ubuntu option)
  user id 1002 (login with default Ubuntu option)
  user id 1003 (login with default Ubuntu option)

  Desktops for admin and user 1001 are ok.

  Desktops for users 1002 and 1003 are corrupted.

  See attached screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 11:41:36 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus-desktop
  InstallationDate: Installed on 2017-10-21 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1765261] Re: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt

2018-05-11 Thread David Oxland

Confirmed by me on 2018-05-11
18.04 Fresh install on 2018-05-05
INTEL NUC BOX7I7BNH
Symptoms the same; re signin.
After a couple of restarts and tries I out-waited it and home screen appeared.
Took 15 min.
Looks normal now

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

Title:
  [regression] Ubuntu 18.04 login screen rejects a valid password on
  first attempt. Usually works on the second attempt

Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Bionic:
  Confirmed
Status in gnome-shell package in Fedora:
  Fix Released

Bug description:
  Upstream:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/240

  Ubuntu 18.04 login screen rejects a valid password on first attempt.
  Always works on the second attempt..

  This seems to be a new problem, just started today.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Thu Apr 19 11:16:17 2018
  InstallationDate: Installed on 2017-12-12 (127 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1765261] Re: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt

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

** Changed in: gnome-shell (Ubuntu Bionic)
   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/1765261

Title:
  [regression] Ubuntu 18.04 login screen rejects a valid password on
  first attempt. Usually works on the second attempt

Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Bionic:
  Confirmed
Status in gnome-shell package in Fedora:
  Fix Released

Bug description:
  Upstream:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/240

  Ubuntu 18.04 login screen rejects a valid password on first attempt.
  Always works on the second attempt..

  This seems to be a new problem, just started today.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Thu Apr 19 11:16:17 2018
  InstallationDate: Installed on 2017-12-12 (127 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1770707] [NEW] Screen resolution is degraded when switching between multiple users

2018-05-11 Thread Roland65

Public bug reported:

In Xubuntu bionic (18.04) with nvidia-390 driver, when switching to
another user, the screen resolution is degraded.

This also happens when locking the screen with light-locker (not with
xscreensaver).


This does not happen with the nouveau driver. So I think there is a connexion 
with bug #1757202.

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

** Description changed:

  In Xubuntu bionic (18.04) with nvidia-390 driver, when switching to
  another user, the screen resolution is degraded.
  
- This does not happen with the nouveau driver. So I think there is a
- connexion with bug #1757202.
+ This also happens when locking the screen with light-locker (not with
+ xscreensaver).
+ 
+ 
+ This does not happen with the nouveau driver. So I think there is a connexion 
with bug #1757202.

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

Title:
  Screen resolution is degraded when switching between multiple users

Status in lightdm package in Ubuntu:
  New

Bug description:
  In Xubuntu bionic (18.04) with nvidia-390 driver, when switching to
  another user, the screen resolution is degraded.

  This also happens when locking the screen with light-locker (not with
  xscreensaver).

  
  This does not happen with the nouveau driver. So I think there is a connexion 
with bug #1757202.

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

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

[Desktop-packages] [Bug 1770494] Re: Does not display VT-100 control codes correctly/consistently

2018-05-11 Thread Scott

** Description changed:

-   I'm writing a shell script that draws in color to any VT-100 terminal.
+ I'm writing a shell script that draws in color to any VT-100 terminal.
  The terminal in Ubuntu consistently and randomly drops out of graphics
  mode producing huge glitches.  This does not occur in Xterm or Gnome
- terminal on CentOS.
+ Terminal on CentOS.
  
  Appearance:
-   The image from the file below should look like a color filled square, what 
you see is a "glitch" which looks like the second half of an escape command 
followed by a lot of "a"'s where the graphical checkerboard character should be 
rendered (in Ubuntu Gnome terminal it is rendered as a cursor that is the color 
of a 50% blend between the background and foreground color, making it the best 
appearing terminal I've used)
+   The image from the file below should look like a color filled square, what 
you see is a "glitch" which looks like the second half of an escape command 
followed by a lot of "a"'s where the graphical checkerboard character should be 
rendered (in Ubuntu Gnome terminal it is rendered as a cursor that is the color 
of a 50% blend between the background and foreground color, making it the best 
appearing terminal I've used)
  
  Reproducibility:
  It is 100% reproducible with the instructions below.
  
  To reproduce:
-   Save the text below to file.txt (or all the text in this window) 
+   Using the attached screen-capture.txt file:
  
-   In Gnome-Terminal try "cat file.txt" over and over to see the error.
+   In Gnome-Terminal try "cat screen-capture.txt" over and over to see
+ the error.
  
-   In Gnome-Terminal try "less -r file.txt" and scale the terminal window
- to see variation
+   In Gnome-Terminal try "less -r screen-capture.txt" and scale the
+ terminal window to see variation
  
  Comments:
-I don't know if there is a problem where characters are dropped from 
stdin, or if the pipe is getting reset, or if the emulator can't keep up with 
the commands, or if there is a(n inconsisent) limit to the number of command 
codes that can be sent to the terminal. Or if it is being interrupted, or if it 
randomly resets...
- 
- file.txt (tried to attach as "screen-capture.txt"):
- [48;5;252m[38;5;235m[1;1f File [48;5;252m[38;5;235m[1;7f Rendering 
[48;5;252m[38;5;235m[1;18f Lighting [48;5;252m[38;5;235m[1;28f 
[48;5;0m[38;5;15mc[?25l[38;5;215m(0)0[3;22f[48;5;46m [48;5;46m 
[48;5;46m 
[48;5;40m[38;5;82ma[48;5;40m[38;5;82ma[48;5;40m[38;5;82ma[48;5;40m[38;5;112ma[48;5;40m[38;5;112ma[48;5;70m[38;5;76ma[48;5;70m[38;5;76ma[48;5;70m[38;5;76ma[48;5;70m[38;5;106ma[48;5;70m[38;5;106ma[48;5;70m[38;5;106ma[48;5;28m[38;5;214ma[48;5;28m[38;5;214ma[48;5;100m
 [48;5;100m [48;5;100m 
[48;5;88m[38;5;154ma[48;5;88m[38;5;154ma[48;5;94m[38;5;136ma[48;5;130m[38;5;136ma[48;5;130m[38;5;136ma[48;5;130m[38;5;166ma[48;5;130m[38;5;166ma[48;5;130m[38;5;166ma[48;5;160m[38;5;172ma[48;5;160m[38;5;172ma[48;5;160m[38;5;202ma[48;5;160m[38;5;202ma[48;5;160m[38;5;202ma[48;5;196m
 [48;5;196m [48;5;196m [4;22f[48;5;46m 
[48;5;40m[38;5;46ma[48;5;40m[38;5;46ma[48;5;40m[38;5;82ma[48;5;40m[38;5;76ma[48;5;40m[38;5;76ma[48;5;34m[38;5;112ma[48;5;34m[38;5;112ma[48;5;70m[38;5;76ma[48;5;70m
 [48;5;70m 
[48;5;70m[38;5;106ma[48;5;64m[38;5;106ma[48;5;64m[38;5;106ma[48;5;28m[38;5;208ma[48;5;28m[38;5;208ma[48;5;100m
 
[48;5;88m[38;5;118ma[48;5;88m[38;5;118ma[48;5;88m[38;5;154ma[48;5;94m[38;5;136ma[48;5;94m[38;5;136ma[48;5;130m
 [48;5;130m 
[48;5;130m[38;5;166ma[48;5;124m[38;5;172ma[48;5;124m[38;5;172ma[48;5;160m[38;5;166ma[48;5;160m[38;5;166ma[48;5;160m[38;5;202ma[48;5;160m[38;5;196ma[48;5;160m[38;5;196ma[48;5;196m

[Desktop-packages] [Bug 1770473] Re: Don't hardcode Ubuntu font name in Settings > Details

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

** Changed in: gnome-control-center (Ubuntu Bionic)
Importance: Undecided => Low

** Changed in: gnome-control-center (Ubuntu Bionic)
Status: New => Triaged

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

Title:
Don't hardcode Ubuntu font name in Settings > Details

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

Bug description:
Impact
--
On the About screen found in Settings > Details, the distro name and version
(Ubuntu 18.04 LTS) is hard-coded to use the Ubuntu font.

While the rest of the distro-logo.patch (or ubuntu-gnome-
version.patch) has a reasonable chance of being applied upstream, that
tweak would need to be a permanent Ubuntu patch.

The Ubuntu patch causes an issue for derivatives that are not Ubuntu
like System76's Pop!_OS. They could remove or modify the Ubuntu patch,
but it might be nicer to derivatives if they didn't need to do that.

Test Case
-
1. From Ubuntu 18.04 LTS, open the Activities Overview.
2. Enter About and open the Settings > About screen.

Does the Ubuntu version number look ok?

3. Install GNOME Tweaks
4. Open GNOME Tweaks. Switch to the Fonts page and change the interface font
to a recognizable font.
5. Look at the Settings > About window. Does the Ubuntu version number use
that font?

Regression Potential

Users that use custom fonts won't have the Ubuntu font represent the Ubuntu
version number.

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

[Desktop-packages] [Bug 1766575] Re: Drop libnss-myhostname recommends

** Description changed:

- gnome-control-center added a Recommends: libnss-myhostname years ago so
- that it was possible to easily change the hostname in the Details panel.
- That dependency no longer appears to be needed since we switched to
- systemd-resolved.
+ Impact
+ ==
+ gnome-control-center added a Recommends: libnss-myhostname years ago so that 
it was possible to easily change the hostname in the Details panel. That 
dependency no longer appears to be needed since we switched to systemd-resolved.
  
- Testing Done
- 
- In both Debian Testing and Ubuntu 18.04 (Debian doesn't use systemd-resolved 
so seemed useful to try there too).
+ Test Case
+ =
  sudo apt uninstall libnss-myhostname
  Restart
  Open the GNOME Settings app (gnome-control-center)
  In the left sidebar, click Devices
- Enter a different Device name in the block
+ Enter a different Device name in the block (let's say new-hostname)
  Open a terminal and verify that the hostname has been changed.
- 
- In Debian, running `ping new-hostname` fails, but it works fine in
- Ubuntu.
+ Then run ping new-hostname and verify that that command works in the terminal.
  
  Other Info
  ==
  There are concerns about having libnss-myhostname in the default install. See 
comment 5 at LP: #1741277.
  
  See also LP: #1162475
  Note that /etc/hosts isn't updated regardless of whether libnss-myhostname is 
installed (I guess my bug description there was wrong but there was some kind 
of bug there.)
  
  Regression Potential
  
  To quote from the manpage:
  
  https://manpages.debian.org/unstable/nss-resolve
  
  "Note that systemd-resolved will synthesize DNS resource records in a
  few cases, for example for "localhost" and the current hostname, see
  systemd-resolved(8) for the full list. This duplicates the functionality
  of nss-myhostname(8), but it is still recommended (see examples below)
  to keep nss-myhostname configured in /etc/nsswitch.conf, to keep those
  names resolveable if systemd-resolved is not running."
  
  Ubuntu uses systemd-resolved by default and it's expected that users who
  don't want to use that will need to configure some things manually.

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

Title:
  Drop libnss-myhostname recommends

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

Bug description:
  Impact
  ==
  gnome-control-center added a Recommends: libnss-myhostname years ago so that 
it was possible to easily change the hostname in the Details panel. That 
dependency no longer appears to be needed since we switched to systemd-resolved.

  Test Case
  =
  sudo apt uninstall libnss-myhostname
  Restart
  Open the GNOME Settings app (gnome-control-center)
  In the left sidebar, click Devices
  Enter a different Device name in the block (let's say new-hostname)
  Open a terminal and verify that the hostname has been changed.
  Then run ping new-hostname and verify that that command works in the terminal.

  Other Info
  ==
  There are concerns about having libnss-myhostname in the default install. See 
comment 5 at LP: #1741277.

  See also LP: #1162475
  Note that /etc/hosts isn't updated regardless of whether libnss-myhostname is 
installed (I guess my bug description there was wrong but there was some kind 
of bug there.)

  Regression Potential
  
  To quote from the manpage:

  https://manpages.debian.org/unstable/nss-resolve

  "Note that systemd-resolved will synthesize DNS resource records in a
  few cases, for example for "localhost" and the current hostname, see
  systemd-resolved(8) for the full list. This duplicates the
  functionality of nss-myhostname(8), but it is still recommended (see
  examples below) to keep nss-myhostname configured in
  /etc/nsswitch.conf, to keep those names resolveable if systemd-
  resolved is not running."

  Ubuntu uses systemd-resolved by default and it's expected that users
  who don't want to use that will need to configure some things
  manually.

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

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

[Desktop-packages] [Bug 1770673] Re: Don't have gnome-control-center require network-manager-gnome