[Desktop-packages] [Bug 1771316] Re: Dialog renders at the center of combined monitor space with a multi-monitor setup

2019-01-18 Thread Rey Leonard Amorato
Hi, upon my limited testing, the following actions seem to exhibit the
same thing as the above:

On the desktop, with the right click context menu on a file;
-Open With Other Application
-Move to...
-Copy to...
-Compress...
-Properties

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

Title:
  Dialog renders at the center of combined monitor space with a multi-
  monitor setup

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 18.04, with the "Show Icons" and "Thrash" enabled, trying to
  empty the trash results in the dialog being rendered at the center of
  the combined desktop space.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
  Uname: Linux 4.15.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Tue May 15 17:44:05 2018
  InstallationDate: Installed on 2018-04-27 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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


[Desktop-packages] [Bug 1812469] [NEW] Xorg freeze (fail to get in the desktop during boot with black screen blocking)

2019-01-18 Thread Benjamin Li
Public bug reported:

I have this issue since quite a long time ago. But none of the system
upgrades had my problem solved! And I can only use Ubuntu under the
recovery mode, which is so inconvenient!

So, my problem is just as the title stated. I can't get in the system
unless I use recovery mode!

And I have tried the latest kernel or the normal kernel before I install
Ubuntu 18.04, which I think is my device's hardware incompatibility with
the desktop, the Gnome desktop.

And I guess it's because there's lack of certain drive for my device,
which is so uncommon, a 2-in-1 model.

Please help, I use Ubuntu so much that I don't just switch it! And
Ubuntu is so useful when I am learning Computer science stuff!

Thanks in advance!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
Uname: Linux 4.20.0-042000-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 19 13:59:30 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation HD Graphics 5300 [8086:161e] (rev 08) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:15fd]
InstallationDate: Installed on 2018-04-04 (290 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
MachineType: ASUSTeK COMPUTER INC. T300FA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000-generic 
root=UUID=63fcbd04-ec8b-462c-ba66-4f45c229353c ro recovery nomodeset
Renderer: Software
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/01/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: T300FA.214
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: T300FA
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.:bvrT300FA.214:bd09/01/2015:svnASUSTeKCOMPUTERINC.:pnT300FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: T
dmi.product.name: T300FA
dmi.product.sku: ASUS-TabletSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER 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.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sat Jan 19 21:49:40 2019
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4.2

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


** Tags: amd64 apport-bug bionic freeze 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/1812469

Title:
  Xorg freeze (fail to get in the desktop during boot with black screen
  blocking)

Status in xorg package in Ubuntu:
  New

Bug description:
  I have this issue since quite a long time ago. But none of the system
  upgrades had my problem solved! And I can only use Ubuntu under the
  recovery mode, which is so inconvenient!

  So, my problem is just as the title stated. I can't get in the system
  unless I use recovery mode!

  And I have tried the latest kernel or the normal kernel before I
  install Ubuntu 18.04, which I think is my device's hardware
  incompatibility with the desktop, the Gnome desktop.

  And I guess it's because there's lack of certain drive for my device,
  which is so uncommon, a 2-in-1 model.

  Please help, I use Ubuntu so much that I don't just switch it! And
  Ubuntu is so useful when I am learning Computer science stuff!

  Thanks in advance!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 4.20.0-042000-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd6

[Desktop-packages] [Bug 1805444] Re: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend

2019-01-18 Thread Doug McMahon
Additionally what about the newer 10XX mobile devices?
(- I've none to try.

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

Title:
  [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice
  backend

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Wayland sessions don't work with the Nvidia driver in 18.04, even
  after enabling them via the kernel command line 'nvidia-
  drm.modeset=1'.

  [Original description]
  Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend due 
to following missing changes in mutter 3.28.3-2~ubuntu18.04.2

  commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84
  Author: Miguel A. Vico 
  Date:   Thu Jun 7 16:29:44 2018 -0700

  renderer/native: Choose first EGL config for non-GBM backends

  Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only
  choose EGL configs that match the GBM_FORMAT_XRGB pixel format.
  However, there won't be any EGL config satisfying such criteria for
  non-GBM backends, such as EGLDevice.

  This change will let us choose the first EGL config for the EGLDevice
  backend, while still forcing GBM_FORMAT_XRGB configs for the GBM
  one.

  Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2

  commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b
  Author: Jonas Ådahl 
  Date:   Tue Nov 14 16:08:52 2017 +0800

  renderer/native: Also wrap flip closures for EGLStreams

  When using the EGLStream backend, the MetaRendererNative passed a
  GClosure to KMS when using EGLStreams, but KMS flip callback event
  handler in meta-gpu-kms.c expected a closure wrapped in a closure
  container, meaning it'd instead crash when using EGLStreams. Make the
  flip handler get what it expects also when using EGLStreams by wrapping
  the flip closure in the container before handing it over to EGL.

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

  apt-cache policy mutter
  mutter:
  Installed: 3.28.3-2~ubuntu18.04.2
  Candidate: 3.28.3-2~ubuntu18.04.2
  Version table:
  *** 3.28.3-2~ubuntu18.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages
  100 /var/lib/dpkg/status
  3.28.1-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages

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

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


[Desktop-packages] [Bug 1805444] Re: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend

2019-01-18 Thread Doug McMahon
In regard to caveats above:
There is no mention of specific Nvidia series, is it presumed that XXXm devices 
should work now in 18.10 & 19.04? 
(- I've never seem any Nvidia m series work in wayland..

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

Title:
  [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice
  backend

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Wayland sessions don't work with the Nvidia driver in 18.04, even
  after enabling them via the kernel command line 'nvidia-
  drm.modeset=1'.

  [Original description]
  Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend due 
to following missing changes in mutter 3.28.3-2~ubuntu18.04.2

  commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84
  Author: Miguel A. Vico 
  Date:   Thu Jun 7 16:29:44 2018 -0700

  renderer/native: Choose first EGL config for non-GBM backends

  Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only
  choose EGL configs that match the GBM_FORMAT_XRGB pixel format.
  However, there won't be any EGL config satisfying such criteria for
  non-GBM backends, such as EGLDevice.

  This change will let us choose the first EGL config for the EGLDevice
  backend, while still forcing GBM_FORMAT_XRGB configs for the GBM
  one.

  Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2

  commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b
  Author: Jonas Ådahl 
  Date:   Tue Nov 14 16:08:52 2017 +0800

  renderer/native: Also wrap flip closures for EGLStreams

  When using the EGLStream backend, the MetaRendererNative passed a
  GClosure to KMS when using EGLStreams, but KMS flip callback event
  handler in meta-gpu-kms.c expected a closure wrapped in a closure
  container, meaning it'd instead crash when using EGLStreams. Make the
  flip handler get what it expects also when using EGLStreams by wrapping
  the flip closure in the container before handing it over to EGL.

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

  apt-cache policy mutter
  mutter:
  Installed: 3.28.3-2~ubuntu18.04.2
  Candidate: 3.28.3-2~ubuntu18.04.2
  Version table:
  *** 3.28.3-2~ubuntu18.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages
  100 /var/lib/dpkg/status
  3.28.1-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages

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

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


[Desktop-packages] [Bug 1812359] Re: Login screen not appearing in bionic

2019-01-18 Thread d a i s y
I've changed #WaylandEnable=false to WaylandEnable=false and reboot the system,
after splash there is nothing so I entered into VT with Ctrl+Alt+F2,
it shows a message, 'a start job is running for hold until boot process 
finishes up.'

I reviewed this bug
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476 and
installed haveged but does not solve the issue

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

Title:
  Login screen not appearing in bionic

Status in mutter package in Ubuntu:
  New

Bug description:
  I've tried the solution mentioned here
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/comments/72
  but it did not solve my issue.

  $ dpkg -s mutter
  Package: mutter
  Status: install ok installed
  Priority: optional
  Section: x11
  Installed-Size: 101
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Version: 3.28.3-2~ubuntu18.04.2
  Provides: x-window-manager
  Depends: libc6 (>= 2.4), libglib2.0-0 (>= 2.53.2), libmutter-2-0 (>= 3.28.2), 
libx11-6, libxcomposite1 (>= 1:0.3-1), mutter-common (>= 
3.28.3-2~ubuntu18.04.2), gnome-settings-daemon, gsettings-desktop-schemas (>= 
3.21.4), zenity
  Suggests: gnome-control-center (>= 1:3.25.2), xdg-user-dirs
  Description: lightweight GTK+ window manager
   Mutter is a small window manager, using GTK+ and Clutter to do
   everything.
   .
   Mutter is the clutter-based evolution of Metacity, which, as the
   author says, is a "Boring window manager for the adult in you. Many
   window managers are like Marshmallow Froot Loops; Metacity is like
   Cheerios."
   .
   This package contains the core binaries.
  Original-Maintainer: Debian GNOME Maintainers 


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.3-2~ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 18 15:02:22 2019
  InstallationDate: Installed on 2019-01-18 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2019-01-18 Thread Launchpad Bug Tracker
[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/1799907

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

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  Unable to remove chromium browser.
  Ubuntu 18.04.1 LTS
  69.0.3497.81-0ubuntu0.18.04.1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 69.0.3497.81-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  AptOrdering:
   chromium-browser-l10n:amd64: Remove
   chromium-browser:amd64: Remove
   chromium-codecs-ffmpeg-extra:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBMLRoNVkxaWhAaAQOAMBt4KlKVpVZUnSUOUFS/74BxT4HAgQCBgJUAqcCzAAEBAjqAGHE4LUBYLEUA3QwRAAAe/QAySx5REQAKICAgICAg/ABTMjJGMzUwCiAgICAg/wBINFpINDExNzA5CiAgAf8CAxGxRpAEHxMSA2UDDAAQAAEdALxS0B4guChVQN0MEQAAHowK0JAgQDEgDEBVAN0MEQAAGIwK0Iog4C0QED6WAN0MEQAAGAAAUA==
   modes: 1920x1080 1920x1080 1920x1080 1680x1050 1600x900 1280x1024 1280x1024 
1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 
1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480 720x480 
640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Thu Oct 25 10:46:48 2018
  Desktop-Session:
   'None'
   'None'
   'None'
  DpkgTerminalLog:
   Removing chromium-browser-l10n (70.0.3538.67-0ubuntu0.18.04.1) ...
   dpkg: error processing package chromium-browser (--remove):
package is in a very bad inconsistent state; you should
reinstall it before attempting a removal
  DuplicateSignature:
   package:chromium-browser:69.0.3497.81-0ubuntu0.18.04.1
   Removing chromium-browser-l10n (70.0.3538.67-0ubuntu0.18.04.1) ...
   dpkg: error processing package chromium-browser (--remove):
package is in a very bad inconsistent state; you should
  Env:
   'None'
   'None'
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  InstallationDate: Installed on 2018-10-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InstalledPlugins:
   /usr/lib/mozilla/plugins:
 => libgnome-shell-browser-plugin.so
   (size: 18856 bytes, mtime: Fri Aug  3 08:18:24 2018)
  Load-Avg-1min: 5.92
  Load-Processes-Running-Percent:   0.3%
  Lsusb:
   Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=98ec02f9-f4a2-4059-b2db-89f6add91501 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  SourcePackage: chromium-browser
  Title: package chromium-browser 69.0.3497.81-0ubuntu0.18.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-MX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0402:bd08/19/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H61-MX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  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:

[Desktop-packages] [Bug 1799100] Re: package python3-uno 1:6.0.6-0ubuntu0.18.04.1 failed to install/upgrade: installed python3-uno package post-installation script subprocess returned error exit statu

2019-01-18 Thread Launchpad Bug Tracker
[Expired for libreoffice (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  package python3-uno 1:6.0.6-0ubuntu0.18.04.1 failed to
  install/upgrade: installed python3-uno package post-installation
  script subprocess returned error exit status 139

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  Other issue is also visible.If the laptop goes to sleep, on next
  session, the keyboard driver is not getting loaded. Keyboard does not
  work.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3-uno 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Sun Oct 21 18:24:19 2018
  DuplicateSignature:
   package:python3-uno:1:6.0.6-0ubuntu0.18.04.1
   Setting up python3-uno (1:6.0.6-0ubuntu0.18.04.1) ...
   Segmentation fault (core dumped)
   dpkg: error processing package python3-uno (--configure):
installed python3-uno package post-installation script subprocess returned 
error exit status 139
  ErrorMessage: installed python3-uno package post-installation script 
subprocess returned error exit status 139
  InstallationDate: Installed on 2016-10-22 (729 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  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.3ubuntu0.1
  SourcePackage: libreoffice
  Title: package python3-uno 1:6.0.6-0ubuntu0.18.04.1 failed to 
install/upgrade: installed python3-uno package post-installation script 
subprocess returned error exit status 139
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1740757] Re: package libreoffice-style-tango 1:5.4.2-0ubuntu0.17.10.1 failed to install/upgrade: problemas de dependencias - se deja sin configurar

2019-01-18 Thread Launchpad Bug Tracker
[Expired for libreoffice (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  package libreoffice-style-tango 1:5.4.2-0ubuntu0.17.10.1 failed to
  install/upgrade: problemas de dependencias - se deja sin configurar

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  no se que paso

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-style-tango 1:5.4.2-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-lowlatency 4.13.13
  Uname: Linux 4.13.0-19-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  Date: Mon Jan  1 12:45:04 2018
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2017-12-12 (20 days ago)
  InstallationMedia: Ubuntu-Studio 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  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 libreoffice-style-tango 1:5.4.2-0ubuntu0.17.10.1 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1799222] Re: libreoffice crashes reliably on startup (and the recovery window comes up)

2019-01-18 Thread Launchpad Bug Tracker
[Expired for libreoffice (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  libreoffice crashes reliably on startup (and the recovery window comes
  up)

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  My ubuntu is pretty stock. I recently upgraded to nautilus 3.30 from
  the GNOME3 Staging PPA and installed the Dektop Icons extension but
  that seems rather unprobable to be related.

  A few days ago (maybe two weeks) LibreOffice worked as expected. But
  that could have been version 6.1.1, I don't know for sure if 6.1.2
  ever worked for me.

  To get the crash errors below I had to set the --norestore flag,
  otherwise an endless chain of file recovery windows are shown

  Purging all libreoffice debs and re-installing the libreoffice
  metapackage wasn't successful, the crash remained.

  amano@amano-desktop:~$ libreoffice --norestore
  Application Error

  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3cfb3)[0x7f0a82c03fb3]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3d1c3)[0x7f0a82c041c3]
  /lib/x86_64-linux-gnu/libc.so.6(+0x41100)[0x7f0a829fe100]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f0a829fe077]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f0a829df535]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x11ee372)[0x7f0a83e12372]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0x90)[0x7f0a85a5cfe0]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1efdc57)[0x7f0a84b21c57]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2e3e59b)[0x7f0a85a6259b]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x17202)[0x7f0a82bde202]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3d08f)[0x7f0a82c0408f]
  /lib/x86_64-linux-gnu/libc.so.6(+0x41100)[0x7f0a829fe100]
  /lib/x86_64-linux-gnu/libc.so.6(+0xad116)[0x7f0a82a6a116]
  
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7f0a817c55a4]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2eb899f)[0x7f0a85adc99f]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9996)[0x7f0a817ba996]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9ba8)[0x7f0a817baba8]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8f203)[0x7f0a81780203]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8fad6)[0x7f0a81780ad6]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc1812)[0x7f0a817b2812]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8f203)[0x7f0a81780203]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8f239)[0x7f0a81780239]
  
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x158)[0x7f0a815cdae8]
  /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4ded8)[0x7f0a815cded8]
  
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f0a815cdf6c]
  /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x89973)[0x7f0a769a8973]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7f0a85a5d4be]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7f0a85a5ec35]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1f035b6)[0x7f0a84b275b6]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2e3fd26)[0x7f0a85a63d26]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7f0a85a63e20]
  /usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x91)[0x7f0a84b43c61]
  /usr/lib/libreoffice/program/soffice.bin(+0x107b)[0x55a4c0b8e07b]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7f0a829e109b]
  /usr/lib/libreoffice/program/soffice.bin(+0x10ba)[0x55a4c0b8e0ba]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice 1:6.1.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 15:18:05 2018
  InstallationDate: Installed on 2018-02-23 (240 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to cosmic on 2018-09-02 (49 days ago)

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

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


[Desktop-packages] [Bug 1797796] Re: embedding OLE objects in Writer leads to blurred print

2019-01-18 Thread Launchpad Bug Tracker
[Expired for libreoffice (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  embedding OLE objects in Writer leads to blurred print

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  Steps to create:

  Open blank Writer document
  Insert OLE object -> Libreoffice Calc
  enter some numbers
  leave OLE object

  -> The object is rendered blurred.

  Enter OLE object (double click)
  -> the content is rendered correctly

  Print document
  -> the content of the OLE object is printed in lower quality than rest of 
document

  Combined documents with text and calculations cannot be printed in unified 
quality.
  -> This type of document is not up to office standards.

  Only on Ubuntu (on Mac this cannot be observed)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 20:29:01 2018
  InstallationDate: Installed on 2018-04-30 (167 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1803821] Re: trackpoint scrolling not working after update to Ubuntu 18.10

2019-01-18 Thread Launchpad Bug Tracker
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  trackpoint scrolling not working after update to Ubuntu 18.10

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Scrolling by pressing the middle button + moving the trackpoint no
  longer works on my Lenovo E560 after recently updating to Ubuntu
  18.10. Other functions of the middle button besides scrolling work
  fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Sat Nov 17 12:40:30 2018
  DistUpgraded: 2018-11-06 01:04:28,107 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:5049]
 Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:5049]
  InstallationDate: Installed on 2016-05-12 (918 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b541 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20EVCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=fb8caa1e-e7e1-4c22-9a7e-fd410dd71da0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2018-11-06 (11 days ago)
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R00ET42W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR00ET42W(1.17):bd04/20/2016:svnLENOVO:pn20EVCTO1WW:pvrThinkPadE560:rvnLENOVO:rn20EVCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E560
  dmi.product.name: 20EVCTO1WW
  dmi.product.sku: LENOVO_MT_20EV_BU_Think_FM_ThinkPad E560
  dmi.product.version: ThinkPad E560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  xserver.bootTime: Thu Nov 15 15:55:41 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.1-3ubuntu2.1
  xserver.video_driver: modeset

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

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


[Desktop-packages] [Bug 1761773] Re: Touch Screen stop working on 18.04 beta1

2019-01-18 Thread Launchpad Bug Tracker
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Touch Screen stop working on 18.04 beta1

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  The touch screen on a HP TouchSmart works fine on other releases.
  On the beta of 18.04 it stopped to work.

  Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen

  On 16.04 it is recognized as TOUCHSCREEN by X.org.  
  On 18.04 beta 1, it is recognized as mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 11:39:07 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Pegatron G98M [GeForce 9300M GS] [1b0a:9010]
  InstallationDate: Installed on 2018-04-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: HP-Pavilion FQ429AA-AC4 IQ510br
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=0c40330f-866b-42e4-a61d-3ca0daf9ee6f ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.06
  dmi.board.name: EVE
  dmi.board.vendor: PEGATRON CORPORATION.
  dmi.board.version: 1.04
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.06:bd07/10/2008:svnHP-Pavilion:pnFQ429AA-AC4IQ510br:pvr:rvnPEGATRONCORPORATION.:rnEVE:rvr1.04:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.family: 103C_53316J
  dmi.product.name: FQ429AA-AC4 IQ510br
  dmi.sys.vendor: HP-Pavilion
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


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

2019-01-18 Thread Launchpad Bug Tracker
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Xorg freeze

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  I recently reported but now im having this issue on wayland as well

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 20 04:41:56 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3670] 
[1002:9593] (prog-if 00 [VGA controller])
 Subsystem: Dell RV635/M86 [Mobility Radeon HD 3670] [1028:0272]
  InstallationDate: Installed on 2018-10-23 (27 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Studio XPS 1640
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=493c5373-ab6c-4136-a868-f324e0358b9c ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0U785D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A15
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A15
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd04/09/2011:svnDellInc.:pnStudioXPS1640:pvrA153:rvnDellInc.:rn0U785D:rvrA15:cvnDellInc.:ct8:cvrA15:
  dmi.product.name: Studio XPS 1640
  dmi.product.version: A153
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1136644] Re: gedit search function is not practical anymore

2019-01-18 Thread delki8
THIS IS REALLY ANNOYING!

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

Title:
  gedit search function is not practical anymore

Status in gedit package in Ubuntu:
  Invalid

Bug description:
  i use gedit a lot, and i find it comfortable in general.

  the new small search window is extremely impractical. FOCUS PROBLEM:
  CTRL+F > type a search (search of longer strings FAR TOO SLOW) > find 
  and now, typing ESC brings one back to the former place!
  when trying to use CTRL-F again, the search string is replaced by new text.
   
  if one wants to stay in the found passage, one must use the mouse/touchpad to 
click into the text.

  this is an extremely annoying feature/behavior.

  i simply would like to have the old search window + its behavior back. 
  i am working very quickly and mostly using shortcuts. 
  gedit now completely interrupts my way of working. 

  additionally, where are the other search functions such as case-
  sensitive search?

  additionally, i do not want the search function to slow down so much.
  for me it is ok to start the search after i have finished typing my
  search string :-) this new energy-consuming ZEITGEIST-etc-fashion is
  not good for quick workers with serious amounts of data.

  best wishes, vollmanr

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

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


[Desktop-packages] [Bug 1611523] Re: ibus-setup fails with local python3

2019-01-18 Thread Yusuke Doi
I'd like to add big +1 to the proposed solution. As ibus is tool
provided by the system, it SHOULD use the system python3 or anything
wrong can happen.

It's likely to have user's own python3 interpreter if you're seriously
working on machine learning field (e.g. pyenv and virtualenv), and I
strongly believe Ubuntu (or other linux distros) shall give the freedom
to the users, including installing user local python interpreter.

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

Title:
  ibus-setup fails with local python3

Status in ibus package in Ubuntu:
  Invalid

Bug description:
  If a user has installed a local python3 (e.g. Anaconda) ibus-setup may
  fail to run because of a missing library:

  Traceback (most recent call last):
File "/usr/share/ibus/setup/main.py", line 31, in 
  from gi.repository import GLib
  ImportError: No module named 'gi'

  This error can be avoided if ibus-setup explicitly executes the system
  python3 rather than the first python3 found in $PATH, by changing:

exec python3 /usr/share/ibus/setup/main.py $@

  to:

exec /usr/bin/python3 /usr/share/ibus/setup/main.py $@

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ibus 1.5.11-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Aug  9 14:17:20 2016
  InstallationDate: Installed on 2016-06-24 (45 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1338492] Re: Xorg crashed with SIGABRT in OsAbort()

2019-01-18 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Invalid

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in X.Org X server:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  At startup, my screen flashes in light green, and can't log to lightdm. 
Adding the ATI driver, it will install with a missing link... Erasing cyrillic 
path and 75 and 100 dpi path folders.
  At this time, can't find again the missing link, and  just install missings 
fonts don't fix the bug..

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-core 2:1.15.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.15.0-6-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.4-0ubuntu1
  Architecture: amd64
  BootLog:
   * Setting up X socket directories...    
[ OK ]
* Starting automatic crash report generation: apport    
[ OK ]
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  Date: Mon Jul  7 10:44:49 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 6450 1 GB 
DDR3 [174b:e164]
  InstallationDate: Installed on 2014-07-03 (3 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=UUID=68f3fab7-5c4e-4d3a-9d6d-a493c47946db ro quiet splash
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   __libc_start_main (main=0x7ffb7ec04db0, argc=11, argv=0x7fff4f6b2e88, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff4f6b2e78) at libc-start.c:287
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5401:bd11/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A55:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.10.20140606-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.54-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8
  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-1ubuntu4
  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: Mon Jul  7 10:48:37 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputEee PC WMI hotkeys   KEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputImPS/2 Logitech Wheel Mouse MOUSE, id 10
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu8
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1338492]

2019-01-18 Thread Andre Klapper
No further information provided by reporter, hence unfortunately closing
as WORKSFORME.

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in X.Org X server:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  At startup, my screen flashes in light green, and can't log to lightdm. 
Adding the ATI driver, it will install with a missing link... Erasing cyrillic 
path and 75 and 100 dpi path folders.
  At this time, can't find again the missing link, and  just install missings 
fonts don't fix the bug..

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-core 2:1.15.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.15.0-6-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.4-0ubuntu1
  Architecture: amd64
  BootLog:
   * Setting up X socket directories...    
[ OK ]
* Starting automatic crash report generation: apport    
[ OK ]
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  Date: Mon Jul  7 10:44:49 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 6450 1 GB 
DDR3 [174b:e164]
  InstallationDate: Installed on 2014-07-03 (3 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=UUID=68f3fab7-5c4e-4d3a-9d6d-a493c47946db ro quiet splash
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   __libc_start_main (main=0x7ffb7ec04db0, argc=11, argv=0x7fff4f6b2e88, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff4f6b2e78) at libc-start.c:287
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5401:bd11/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A55:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.10.20140606-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.54-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8
  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-1ubuntu4
  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: Mon Jul  7 10:48:37 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputEee PC WMI hotkeys   KEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputImPS/2 Logitech Wheel Mouse MOUSE, id 10
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu8
  xserver.video_driver: radeon

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubs

[Desktop-packages] [Bug 1812394] Re: Video playback faintly shows applications behind active browser window

2019-01-18 Thread Tom Reynolds
Setting this option in about:config and restarting Firefox fixes (or works 
around?) it for me: 
layers.acceleration.force-enabled = true

Source:
https://www.reddit.com/r/firefox/comments/a7epn7/transparent_video_player/

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

Title:
  Video playback faintly shows applications behind active browser window

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu desktop 18.10, Mozilla Firefox 64.0

  To reproduce:
  1. Open any application (such as Nautilus file manager, or the terminal 
emulator)
  2. Open Firefox above this application
  3. Begin video playback (I've found that it's easier to notice this bug when 
the video is a dark gray or black. This video worked well: < 
https://youtu.be/jYFk1O_t43A >)

  What happens:
  In the region where the video is playing, you will faintly see the 
application(s) that are behind Firefox.

  What should happen:
  The video should completely obscure any applications that are not above the 
browser window.

  I cannot reliably reproduce this bug when the player is in full screen
  - i.e. it must be in theater mode or normal player.

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

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


[Desktop-packages] [Bug 1812373] Re: Desktop is not restored correctly after screen saver

2019-01-18 Thread isparnid
same symptoms for me after these two updates (same distribution as Reuben 
Thomas):
Start-Date: 2019-01-18  12:11:53
Commandline: aptdaemon role='role-commit-packages' sender=':1.1127'
Upgrade: libcups2:amd64 (2.2.7-1ubuntu2.2, 2.2.7-1ubuntu2.3), libcups2:i386 
(2.2.7-1ubuntu2.2, 2.2.7-1ubuntu2.3), libzmq5:amd64 (4.2.5-1, 
4.2.5-1ubuntu0.1), oracle-java8-unlimited-jce-policy:amd64 (8u191-1~webupd8~1, 
8u201-1~webupd8~1), libcupsmime1:amd64 (2.2.7-1ubuntu2.2, 2.2.7-1ubuntu2.3), 
oracle-java8-set-default:amd64 (8u191-1~webupd8~1, 8u201-1~webupd8~1), 
oracle-java8-installer:amd64 (8u191-1~webupd8~1, 8u201-1~webupd8~1), 
libcupsppdc1:amd64 (2.2.7-1ubuntu2.2, 2.2.7-1ubuntu2.3), libcupsimage2:amd64 
(2.2.7-1ubuntu2.2, 2.2.7-1ubuntu2.3), libcupscgi1:amd64 (2.2.7-1ubuntu2.2, 
2.2.7-1ubuntu2.3), cups-ipp-utils:amd64 (2.2.7-1ubuntu2.2, 2.2.7-1ubuntu2.3)
End-Date: 2019-01-18  12:12:13

Start-Date: 2019-01-18  18:51:12
Commandline: /usr/sbin/synaptic
Requested-By: daniel (1000)
Upgrade: fdisk:amd64 (2.31.1-0.4ubuntu3.2, 2.31.1-0.4ubuntu3.3), 
uuid-runtime:amd64 (2.31.1-0.4ubuntu3.2, 2.31.1-0.4ubuntu3.3), libfdisk1:amd64 
(2.31.1-0.4ubuntu3.2, 2.31.1-0.4ubuntu3.3), gvfs-backends:amd64 
(1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), gvfs-bin:amd64 (1.36.1-0ubuntu1.1, 
1.36.1-0ubuntu1.2), libmount1:amd64 (2.31.1-0.4ubuntu3.2, 2.31.1-0.4ubuntu3.3), 
libmount1:i386 (2.31.1-0.4ubuntu3.2, 2.31.1-0.4ubuntu3.3), util-linux:amd64 
(2.31.1-0.4ubuntu3.2, 2.31.1-0.4ubuntu3.3), mount:amd64 (2.31.1-0.4ubuntu3.2, 
2.31.1-0.4ubuntu3.3), libblkid1:amd64 (2.31.1-0.4ubuntu3.2, 
2.31.1-0.4ubuntu3.3), libblkid1:i386 (2.31.1-0.4ubuntu3.2, 
2.31.1-0.4ubuntu3.3), gvfs-libs:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), 
gvfs-fuse:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), libuuid1:amd64 
(2.31.1-0.4ubuntu3.2, 2.31.1-0.4ubuntu3.3), libuuid1:i386 (2.31.1-0.4ubuntu3.2, 
2.31.1-0.4ubuntu3.3), libsmartcols1:amd64 (2.31.1-0.4ubuntu3.2, 
2.31.1-0.4ubuntu3.3), rfkill:amd64 (2.31.1-0.4ubuntu3.2, 2.31.1-0.4ubuntu3.3), 
bsdutils:amd64 (1:2.31.1-0.4ubuntu3.2, 1:2.31.1-0.4ubuntu3.3), gvfs:amd64 
(1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), gvfs-common:amd64 (1.36.1-0ubuntu1.1, 
1.36.1-0ubuntu1.2), gvfs-daemons:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2)
End-Date: 2019-01-18  18:51:23

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

Title:
  Desktop is not restored correctly after screen saver

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  With the update to 3.28.3-0ubuntu0.18.04.4, on two separate machines,
  the screen saver stopped working properly.

  When the screen is locked manually (by clicking the lock screen icon),
  the screen either freezes with the desktop still showing, or shows the
  same grey background as the login screen; it does not show the normal
  lock screen image.

  When the screen saver is activated automatically, the screen turns off
  as normal, but when I press a key, the grey background as for the
  login screen is shown (in fact, it's the same as the login screen, but
  without the login widget; that is, the normal icons are shown at the
  top of the screen).

  
  Pressing Ctrl+Alt+F1 switches to the login dialog.

  I can then log in successfully, but all GNOME shell extensions are
  disabled.

  (A simple workaround is then to restart gnome-shell with the "r"
  command from the "Enter a command" dialog.)

  I am marking this bug as a security vulnerability because in the case
  that the screen simply freezes, confidential information may be
  displayed by the failure of the screen shield to activate.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jan 18 10:28:59 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-11-26 (1514 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-08-16 (155 days ago)

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

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


[Desktop-packages] [Bug 1812057] Re: Upgrade Lost Firefox ESR

2019-01-18 Thread Ubuntu User
No, of course not.  If it had, I wouldn't have upgraded.  This is
typical Ubuntu methods; no concern for the user.  I'll not make that
mistake again.

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

Title:
  Upgrade Lost Firefox ESR

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  System was upgraded from Xubuntu 14 to 16 by DVD.  It wiped out many
  things, including the installation of Firefox ESR.

  ESR was manually reinstalled, but there appears to be no integration
  with the former profiles.  While they still exist, both Firefox
  Quantum and Firefox ESR see the exact same profiles.  There appears to
  be no way to remedy the problem.

  No crash is involved.  If -profilemanager is used in Firefox, the same
  choices appear in both versions.  This was not the case prior to the
  upgrade.


  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  firefox-esr:
Installed: 52.9.0esr-1~16.04.york0
Candidate: 52.9.0esr-1~16.04.york0
Version table:
   *** 52.9.0esr-1~16.04.york0 500
  500 http://ppa.launchpad.net/jonathonf/firefox-esr-52/ubuntu 
xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  firefox:
Installed: 64.0+build3-0ubuntu0.16.04.1
Candidate: 64.0+build3-0ubuntu0.16.04.1
Version table:
   *** 64.0+build3-0ubuntu0.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   45.0.2+build1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

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

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


[Desktop-packages] [Bug 1812446] [NEW] Bluetooth mouse stops responding after 24-48 hours of connectivity

2019-01-18 Thread Juan Martinez
Public bug reported:

Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM ISO (for this model)

-Bluetooth mouse (Tested with a HP x4000b BT Laser Mouse) stops
responding after 1-2 days of being connected whereas the expectation is
that the mouse would continue working normally

-Bluetooth settings window will initially report Bluetooth is on when
opened.

-Switching away and back to the Bluetooth settings GUI will now show Bluetooth 
as disabled, and Settings GUI will lock up until system is restarted.
   o Settings window can be force closed and re-opened, but it will still 
be locked up on the Bluetooth tab

-When moving the mouse or clicking any buttons in this state, the
Bluetooth icon in the top right GNOME menu bar will briefly flash the
Bluetooth icon but there is no actual mouse activity.

-dmesg log shows an extremely large number of events “Bluetooth: hci0:
last event is not cmd complete (0x0f)”

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

Title:
  Bluetooth mouse stops responding after 24-48 hours of connectivity

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM ISO (for this model)

  -Bluetooth mouse (Tested with a HP x4000b BT Laser Mouse) stops
  responding after 1-2 days of being connected whereas the expectation
  is that the mouse would continue working normally

  -Bluetooth settings window will initially report Bluetooth is on when
  opened.

  -Switching away and back to the Bluetooth settings GUI will now show 
Bluetooth as disabled, and Settings GUI will lock up until system is restarted.
 o Settings window can be force closed and re-opened, but it will still 
be locked up on the Bluetooth tab

  -When moving the mouse or clicking any buttons in this state, the
  Bluetooth icon in the top right GNOME menu bar will briefly flash the
  Bluetooth icon but there is no actual mouse activity.

  -dmesg log shows an extremely large number of events “Bluetooth: hci0:
  last event is not cmd complete (0x0f)”

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

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


[Desktop-packages] [Bug 1812373] Re: Desktop is not restored correctly after screen saver

2019-01-18 Thread isparnid
same symptoms for me after these two updates (same distribution as Reuben 
Thomas):
Start-Date: 2019-01-18  12:11:53
Commandline: aptdaemon role='role-commit-packages' sender=':1.1127'
Upgrade: libcups2:amd64 (2.2.7-1ubuntu2.2, 2.2.7-1ubuntu2.3), libcups2:i386 
(2.2.7-1ubuntu2.2, 2.2.7-1ubuntu2.3), libzmq5:amd64 (4.2.5-1, 
4.2.5-1ubuntu0.1), oracle-java8-unlimited-jce-policy:amd64 (8u191-1~webupd8~1, 
8u201-1~webupd8~1), libcupsmime1:amd64 (2.2.7-1ubuntu2.2, 2.2.7-1ubuntu2.3), 
oracle-java8-set-default:amd64 (8u191-1~webupd8~1, 8u201-1~webupd8~1), 
oracle-java8-installer:amd64 (8u191-1~webupd8~1, 8u201-1~webupd8~1), 
libcupsppdc1:amd64 (2.2.7-1ubuntu2.2, 2.2.7-1ubuntu2.3), libcupsimage2:amd64 
(2.2.7-1ubuntu2.2, 2.2.7-1ubuntu2.3), libcupscgi1:amd64 (2.2.7-1ubuntu2.2, 
2.2.7-1ubuntu2.3), cups-ipp-utils:amd64 (2.2.7-1ubuntu2.2, 2.2.7-1ubuntu2.3)
End-Date: 2019-01-18  12:12:13

Start-Date: 2019-01-18  18:51:12
Commandline: /usr/sbin/synaptic
Requested-By: daniel (1000)
Upgrade: fdisk:amd64 (2.31.1-0.4ubuntu3.2, 2.31.1-0.4ubuntu3.3), 
uuid-runtime:amd64 (2.31.1-0.4ubuntu3.2, 2.31.1-0.4ubuntu3.3), libfdisk1:amd64 
(2.31.1-0.4ubuntu3.2, 2.31.1-0.4ubuntu3.3), gvfs-backends:amd64 
(1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), gvfs-bin:amd64 (1.36.1-0ubuntu1.1, 
1.36.1-0ubuntu1.2), libmount1:amd64 (2.31.1-0.4ubuntu3.2, 2.31.1-0.4ubuntu3.3), 
libmount1:i386 (2.31.1-0.4ubuntu3.2, 2.31.1-0.4ubuntu3.3), util-linux:amd64 
(2.31.1-0.4ubuntu3.2, 2.31.1-0.4ubuntu3.3), mount:amd64 (2.31.1-0.4ubuntu3.2, 
2.31.1-0.4ubuntu3.3), libblkid1:amd64 (2.31.1-0.4ubuntu3.2, 
2.31.1-0.4ubuntu3.3), libblkid1:i386 (2.31.1-0.4ubuntu3.2, 
2.31.1-0.4ubuntu3.3), gvfs-libs:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), 
gvfs-fuse:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), libuuid1:amd64 
(2.31.1-0.4ubuntu3.2, 2.31.1-0.4ubuntu3.3), libuuid1:i386 (2.31.1-0.4ubuntu3.2, 
2.31.1-0.4ubuntu3.3), libsmartcols1:amd64 (2.31.1-0.4ubuntu3.2, 
2.31.1-0.4ubuntu3.3), rfkill:amd64 (2.31.1-0.4ubuntu3.2, 2.31.1-0.4ubuntu3.3), 
bsdutils:amd64 (1:2.31.1-0.4ubuntu3.2, 1:2.31.1-0.4ubuntu3.3), gvfs:amd64 
(1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), gvfs-common:amd64 (1.36.1-0ubuntu1.1, 
1.36.1-0ubuntu1.2), gvfs-daemons:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2)
End-Date: 2019-01-18  18:51:23

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

Title:
  Desktop is not restored correctly after screen saver

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  With the update to 3.28.3-0ubuntu0.18.04.4, on two separate machines,
  the screen saver stopped working properly.

  When the screen is locked manually (by clicking the lock screen icon),
  the screen either freezes with the desktop still showing, or shows the
  same grey background as the login screen; it does not show the normal
  lock screen image.

  When the screen saver is activated automatically, the screen turns off
  as normal, but when I press a key, the grey background as for the
  login screen is shown (in fact, it's the same as the login screen, but
  without the login widget; that is, the normal icons are shown at the
  top of the screen).

  
  Pressing Ctrl+Alt+F1 switches to the login dialog.

  I can then log in successfully, but all GNOME shell extensions are
  disabled.

  (A simple workaround is then to restart gnome-shell with the "r"
  command from the "Enter a command" dialog.)

  I am marking this bug as a security vulnerability because in the case
  that the screen simply freezes, confidential information may be
  displayed by the failure of the screen shield to activate.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jan 18 10:28:59 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-11-26 (1514 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-08-16 (155 days ago)

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

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


[Desktop-packages] [Bug 1799614] Re: Use new media API

2019-01-18 Thread Brian Murray
The upload of snapd-glib is a new upstream version of the package yet
only this bug report is referenced in the changelog for it. Is there a
special exception for new versions of snapd-glib that I'm not aware of?

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

Title:
  Use new media API

Status in gnome-software package in Ubuntu:
  Fix Released
Status in snapd-glib package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in snapd-glib source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed
Status in snapd-glib source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  snapd now provides 'media' which replaces the old 'screenshots' data. We need 
to migrate to this as the old screenshot data will be removed in the future.

  [Test Case]
  Run gnome-software with updated snapd-glib and confirm that screenshots and 
promoted snap banners continue to work.

  [Regression Potential]
  Possibility of new errors being introduced in updated code paths.

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

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


[Desktop-packages] [Bug 1812132] Re: Does not return results with files that have hyphens in the filename

2019-01-18 Thread Alex Cabal
I *think* it's tracker because I'm using the `vanilla-gnome-desktop`
package which creates a plain Gnome Shell session, which I think uses
tracker in the Overview search (when pressing Super in Gnome Shell).

The search results I'm referring to appear within the "Files" header.

If I open a Nautilus window and try a recursive typeahead search, it is
able to find the files correctly.

$> dpkg -l | grep tracker
ii  gir1.2-tracker-2.0:amd64 2.0.3-1ubuntu4 
  amd64GObject introspection data for Tracker
ii  kerneloops   
0.12+git20140509-6ubuntu2amd64kernel oops tracker
ii  libtracker-control-2.0-0:amd64   2.0.3-1ubuntu4 
  amd64library to control/monitor tracker miners
ii  libtracker-miner-2.0-0:amd64 2.0.3-1ubuntu4 
  amd64tracker data miner library
ii  libtracker-sparql-2.0-0:amd642.0.3-1ubuntu4 
  amd64metadata database, indexer and search tool - 
library
ii  libwhoopsie-preferences0 0.19   
  amd64Ubuntu error tracker submission settings - 
shared library
ii  libwhoopsie0:amd64   0.2.62 
  amd64Ubuntu error tracker submission - shared 
library
ii  libxatracker2:amd64  
18.0.5-0ubuntu0~18.04.1  amd64X acceleration 
library -- runtime
ii  tracker  2.0.3-1ubuntu4 
  amd64metadata database, indexer and search tool
ii  tracker-extract  2.0.4-1
  amd64metadata database, indexer and search tool - 
metadata extractors
ii  tracker-miner-fs 2.0.4-1
  amd64metadata database, indexer and search tool - 
filesystem indexer
ii  whoopsie 0.2.62 
  amd64Ubuntu error tracker submission

Here's another example you can try (though I don't understand how often
tracker updates its database and sometimes it takes a few restarts for
tracker to output results at all):

$> echo "test" > ~/foobar-foobaz
$> tracker search -f "foobar-"
   Files:
$> tracker search -f "foobar"
   Files:
 file:///home/alex/foobar-foobaz

Am I looking in the right place? Anything else I can provide?

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

Title:
  Does not return results with files that have hyphens in the filename

Status in tracker package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 18.04 using the `vanilla-gnome-desktop` session (i.e. Gnome
  Shell), tracker does not return any files if there is a hyphen (-) in
  the search string.

  To recreate:

  - Create a file named `foo-bar`.

  - Press  to open Overview.

  - Type foo. Observe that the `foo-bar` file appears.

  - Type foo-. Observe that the overview says "No results."

  This is a regression as files with hyphens in the filename were
  included in search results in 16.04.

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

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


[Desktop-packages] [Bug 1812373] Re: Desktop is not restored correctly after screen saver

2019-01-18 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Desktop is not restored correctly after screen saver

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  With the update to 3.28.3-0ubuntu0.18.04.4, on two separate machines,
  the screen saver stopped working properly.

  When the screen is locked manually (by clicking the lock screen icon),
  the screen either freezes with the desktop still showing, or shows the
  same grey background as the login screen; it does not show the normal
  lock screen image.

  When the screen saver is activated automatically, the screen turns off
  as normal, but when I press a key, the grey background as for the
  login screen is shown (in fact, it's the same as the login screen, but
  without the login widget; that is, the normal icons are shown at the
  top of the screen).

  
  Pressing Ctrl+Alt+F1 switches to the login dialog.

  I can then log in successfully, but all GNOME shell extensions are
  disabled.

  (A simple workaround is then to restart gnome-shell with the "r"
  command from the "Enter a command" dialog.)

  I am marking this bug as a security vulnerability because in the case
  that the screen simply freezes, confidential information may be
  displayed by the failure of the screen shield to activate.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jan 18 10:28:59 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-11-26 (1514 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-08-16 (155 days ago)

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

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


[Desktop-packages] [Bug 1799614] Re: Use new media API

2019-01-18 Thread Brian Murray
Hello Robert, or anyone else affected,

Accepted gnome-software into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.30.2-0ubuntu9 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags added: verification-needed verification-needed-cosmic

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

Title:
  Use new media API

Status in gnome-software package in Ubuntu:
  Fix Released
Status in snapd-glib package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in snapd-glib source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed
Status in snapd-glib source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  snapd now provides 'media' which replaces the old 'screenshots' data. We need 
to migrate to this as the old screenshot data will be removed in the future.

  [Test Case]
  Run gnome-software with updated snapd-glib and confirm that screenshots and 
promoted snap banners continue to work.

  [Regression Potential]
  Possibility of new errors being introduced in updated code paths.

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

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


[Desktop-packages] [Bug 1807276] Re: Cannot swipe up from bottom of screen to get Onscreen Keyboard in Xorg

2019-01-18 Thread Juan Martinez
It may be worth mentioning that we are unable to reproduce the error on
some more esoteric models like rugged machines.

One theory is that Xorg/GNOME may have different thresholds than Wayland
for detecting the swipe-up gesture and this may be impacted by the
particulars of how displays report touch information

FAIL: Precision 5530
- Max "ABS_Y" value from evtest is 7743 (the highest Y-value for touch 
observed in testing)
- Note 7743 doesn't seem to have an obvious relationship with 
the screen resolution, if that is significant
- Hardware = "Wacom HID 486A Finger"


PASS: Rugged mobile (different touch hardware)
- Max Y "ABS_Y" value in evtest is 3840 - this is the same value as the 
vertical screen resolution
- Hardware = "Atmel maxTouch Digitizer"
- No issues on X or Wayland triggering the OSK

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

Title:
  Cannot swipe up from bottom of screen to get Onscreen Keyboard in Xorg

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.10 / GNOME Shell 3.30.1
  ALSO
  Ubuntu 18.04 LTS / GNOME Shell 3.28.1

  Steps to reproduce on our end:

  - Login (Xorg as default)
  - Attempt to swipe up with finger from below screen
  RESULT: It draws a thin vertical (desktop) selection box, but no OSK
  - Logout
  - Log back in, after first hitting 'gear' button to select 'Ubuntu on Wayland'
  - ps -e | grep Xwayland #shows 'Xwayland' process is running
  - Repeat swipe up with finger from below screen
  RESULT: OSK shows up as expected

  This has been verified both in 1920x1080 as well as 3840x2160
  resolutions (also with various scaling options selected)

  Issue is also logged upstream: https://gitlab.gnome.org/GNOME/gnome-
  shell/issues/839

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

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


[Desktop-packages] [Bug 1807276] Re: Cannot swipe up from bottom of screen to get Onscreen Keyboard in Xorg

2019-01-18 Thread Juan Martinez
~30 second video reproduction of issue

** Attachment added: "20190118_150138.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807276/+attachment/5230428/+files/20190118_150138.mp4

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

Title:
  Cannot swipe up from bottom of screen to get Onscreen Keyboard in Xorg

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.10 / GNOME Shell 3.30.1
  ALSO
  Ubuntu 18.04 LTS / GNOME Shell 3.28.1

  Steps to reproduce on our end:

  - Login (Xorg as default)
  - Attempt to swipe up with finger from below screen
  RESULT: It draws a thin vertical (desktop) selection box, but no OSK
  - Logout
  - Log back in, after first hitting 'gear' button to select 'Ubuntu on Wayland'
  - ps -e | grep Xwayland #shows 'Xwayland' process is running
  - Repeat swipe up with finger from below screen
  RESULT: OSK shows up as expected

  This has been verified both in 1920x1080 as well as 3840x2160
  resolutions (also with various scaling options selected)

  Issue is also logged upstream: https://gitlab.gnome.org/GNOME/gnome-
  shell/issues/839

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

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


[Desktop-packages] [Bug 1311990] Re: Switching keyboard layouts from some non-English to Japanese (Anthy, Mozc) does not work on 14.04 and 18.04

2019-01-18 Thread Atti
to reproduce:
* install Ubuntu 18.04
* go to Settings -> Language and Region: add Russian language
* run "sudo apt install ibus-mozc"
* logout-login
* go to Settings -> Language and Region: add "Japanese (Mozc)" language
* use indicator menu to switch to Russian and then to Japanese
* type anything - it'll be in Russian
* use indicator menu to switch to English and then to Japanese
* type anything - it'll be in Japanese

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

Title:
  Switching keyboard layouts from some non-English to Japanese (Anthy,
  Mozc) does not work on 14.04 and 18.04

Status in ibus-anthy package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 14.04 LTS with multiple keyboard layouts: English
  (US) – Thai – Japanese (Anthy, Mozc), as appeared in Text Entry
  settings.

  The problem is that … when I cycle through the layouts in this order
  [EN → TH → JP], I would have expected to be able to type Japanese
  properly; however, although the indicator on the top right says JP,
  the output was still in TH.

  However, if I cycle in the reverse order [TH → EN → JP], the Japanese
  input works correctly.

  In more details, whenever I switch to JP from TH (by switching to
  "next" input if TH precedes JP in the settings, or by switching to
  "previous" input if TH succeeds JP in the settings), the output is in
  TH instead of JP (but the indicator is already in JP). On the other
  hand, switching to JP from EN works fine.

  Here's what the output from apt-cache policy ibus:

  ibus:
Installed: 1.5.5-1ubuntu3
Candidate: 1.5.5-1ubuntu3
Version table:
   *** 1.5.5-1ubuntu3 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-anthy/+bug/1311990/+subscriptions

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


[Desktop-packages] [Bug 1807276] Re: Cannot swipe up from bottom of screen to get Onscreen Keyboard in Xorg

2019-01-18 Thread Juan Martinez
Adding journalctl output as requested

** Attachment added: "journalctl_output"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807276/+attachment/5230427/+files/journalctl_output

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

Title:
  Cannot swipe up from bottom of screen to get Onscreen Keyboard in Xorg

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.10 / GNOME Shell 3.30.1
  ALSO
  Ubuntu 18.04 LTS / GNOME Shell 3.28.1

  Steps to reproduce on our end:

  - Login (Xorg as default)
  - Attempt to swipe up with finger from below screen
  RESULT: It draws a thin vertical (desktop) selection box, but no OSK
  - Logout
  - Log back in, after first hitting 'gear' button to select 'Ubuntu on Wayland'
  - ps -e | grep Xwayland #shows 'Xwayland' process is running
  - Repeat swipe up with finger from below screen
  RESULT: OSK shows up as expected

  This has been verified both in 1920x1080 as well as 3840x2160
  resolutions (also with various scaling options selected)

  Issue is also logged upstream: https://gitlab.gnome.org/GNOME/gnome-
  shell/issues/839

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

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


[Desktop-packages] [Bug 1810739] Re: [SRU] libreoffice 6.1.4 for cosmic

2019-01-18 Thread Olivier Tilloy
Upgraded libreoffice to 1:6.1.4-0ubuntu0.18.10.1 from cosmic-proposed in
a clean and up-to-date cosmic amd64 VM, and successfully ran test plan
at https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice.

** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic

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

Title:
  [SRU] libreoffice 6.1.4 for cosmic

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Cosmic:
  Fix Committed
Status in libreoffice-l10n source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 6.1.4 is the fourth bugfix release of the fresh 6.1 line. 
Version 6.1.3 is currently in cosmic.
 For a list of fixed bugs compared to 6.1.3 see the list of bugs fixed in 
the two release candidates:
   https://wiki.documentfoundation.org/Releases/6.1.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.1.4/RC2#List_of_fixed_bugs
 (that's a total of 126 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 126 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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


[Desktop-packages] [Bug 1807276] Re: Cannot swipe up from bottom of screen to get Onscreen Keyboard in Xorg

2019-01-18 Thread Juan Martinez
Adding journalctl output as requested

** Attachment added: "journalctl_output"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807276/+attachment/5230426/+files/journalctl_output

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

Title:
  Cannot swipe up from bottom of screen to get Onscreen Keyboard in Xorg

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.10 / GNOME Shell 3.30.1
  ALSO
  Ubuntu 18.04 LTS / GNOME Shell 3.28.1

  Steps to reproduce on our end:

  - Login (Xorg as default)
  - Attempt to swipe up with finger from below screen
  RESULT: It draws a thin vertical (desktop) selection box, but no OSK
  - Logout
  - Log back in, after first hitting 'gear' button to select 'Ubuntu on Wayland'
  - ps -e | grep Xwayland #shows 'Xwayland' process is running
  - Repeat swipe up with finger from below screen
  RESULT: OSK shows up as expected

  This has been verified both in 1920x1080 as well as 3840x2160
  resolutions (also with various scaling options selected)

  Issue is also logged upstream: https://gitlab.gnome.org/GNOME/gnome-
  shell/issues/839

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

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


[Desktop-packages] [Bug 1793124]

2019-01-18 Thread Pnetmod
An obvious workaround is to zoom out on the sheet.  If that reduces
legibility too far, then use assorted text function to split the text
into different cells nearby, or reformat the cells using wrap etc. as
appropriate.

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

Title:
  Scrolling on Calc leaves content invisible if cell is higher than
  screen

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

Bug description:
  I sometimes receive Calc documents where the content of an individual
  cell is split on so many lines that it fills up the whole screen and
  more. I can easily see the top part of these cells but scrolling to
  the bottom does not seem to work. Whether I try dragging the scrollbar
  or moving the screen with my laptop’s touchpad, Calc seems to skip the
  bottom part of the cell and jump directly to the following cell. See
  the attached screenshots of a document which has numbers 1 to 50 so
  that numbers 4 to 40 occupy one single cell (A4). In the first
  screenshot I see the top part of that cell (4 to 23) and in the next I
  have scrolled down the screen as little as possible, and now I see
  cell A5 (number 41) on the top. Everything in between is visually
  inaccessible whatever I try.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

Installed: 1:6.0.3-0ubuntu1
Candidate: 1:6.0.3-0ubuntu1
Version table:
   *** 1:6.0.3-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-calc 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 18 11:16:17 2018
  InstallationDate: Installed on 2017-02-13 (582 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago)

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

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


[Desktop-packages] [Bug 1812057] Re: Upgrade Lost Firefox ESR

2019-01-18 Thread Olivier Tilloy
I understand this is annoying and unexpected when doing an upgrade. Yet
this is behaving as implemented. The upgrader should have warned you
that it was going to remove a number of packages, with an option to view
the list of packages to be removed. Did it not do that?

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

Title:
  Upgrade Lost Firefox ESR

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  System was upgraded from Xubuntu 14 to 16 by DVD.  It wiped out many
  things, including the installation of Firefox ESR.

  ESR was manually reinstalled, but there appears to be no integration
  with the former profiles.  While they still exist, both Firefox
  Quantum and Firefox ESR see the exact same profiles.  There appears to
  be no way to remedy the problem.

  No crash is involved.  If -profilemanager is used in Firefox, the same
  choices appear in both versions.  This was not the case prior to the
  upgrade.


  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  firefox-esr:
Installed: 52.9.0esr-1~16.04.york0
Candidate: 52.9.0esr-1~16.04.york0
Version table:
   *** 52.9.0esr-1~16.04.york0 500
  500 http://ppa.launchpad.net/jonathonf/firefox-esr-52/ubuntu 
xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  firefox:
Installed: 64.0+build3-0ubuntu0.16.04.1
Candidate: 64.0+build3-0ubuntu0.16.04.1
Version table:
   *** 64.0+build3-0ubuntu0.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   45.0.2+build1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

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

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


[Desktop-packages] [Bug 1311990] Re: Switching keyboard layouts from some non-English to Japanese (Anthy, Mozc) does not work on 14.04

2019-01-18 Thread Atti
This bug is still present in 18.04. Probably it's not related to Anthy because 
it's reproducible with ibus-mozc.
if i change layouts EN->JP, then Japanese input works correctly.
if i change layouts RU->JP, then all the letters are Russian, but all numbers 
and symbols are Japanese.

** Summary changed:

- Switching keyboard layouts from some non-English to Japanese (Anthy, Mozc) 
does not work on 14.04
+ Switching keyboard layouts from some non-English to Japanese (Anthy, Mozc) 
does not work on 14.04 and 18.04

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

Title:
  Switching keyboard layouts from some non-English to Japanese (Anthy,
  Mozc) does not work on 14.04 and 18.04

Status in ibus-anthy package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 14.04 LTS with multiple keyboard layouts: English
  (US) – Thai – Japanese (Anthy, Mozc), as appeared in Text Entry
  settings.

  The problem is that … when I cycle through the layouts in this order
  [EN → TH → JP], I would have expected to be able to type Japanese
  properly; however, although the indicator on the top right says JP,
  the output was still in TH.

  However, if I cycle in the reverse order [TH → EN → JP], the Japanese
  input works correctly.

  In more details, whenever I switch to JP from TH (by switching to
  "next" input if TH precedes JP in the settings, or by switching to
  "previous" input if TH succeeds JP in the settings), the output is in
  TH instead of JP (but the indicator is already in JP). On the other
  hand, switching to JP from EN works fine.

  Here's what the output from apt-cache policy ibus:

  ibus:
Installed: 1.5.5-1ubuntu3
Candidate: 1.5.5-1ubuntu3
Version table:
   *** 1.5.5-1ubuntu3 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-anthy/+bug/1311990/+subscriptions

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


[Desktop-packages] [Bug 1812430] [NEW] intel hd 500 - j3455 no graphic driver

2019-01-18 Thread dadanana777777
Public bug reported:

need driver please

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CompositorRunning: None
Date: Fri Jan 18 20:13:31 2019
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:8738]
InstallationDate: Installed on 2019-01-16 (2 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 045e:0750 Microsoft Corp. Wired Keyboard 600
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=sk_SK.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=427002da-8ec4-4338-927f-12021ee7cea4 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/07/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0802
dmi.board.asset.tag: Default string
dmi.board.name: J3455M-E
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.:bvr0802:bd02/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnJ3455M-E:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1~ppa1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.1~ppa1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic third-party-packages 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/1812430

Title:
  intel hd 500 - j3455 no graphic driver

Status in xorg package in Ubuntu:
  New

Bug description:
  need driver please

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Jan 18 20:13:31 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8738]
  InstallationDate: Installed on 2019-01-16 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:0750 Microsoft Corp. Wired Keyboard 600
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=sk_SK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=427002da-8ec4-4338-927f-12021ee7cea4 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0802
  dmi.board.asset.tag: Default string
  dmi.board.name: J3455M-E
  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.:bvr0802:bd02/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnJ3455M-E:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be fi

[Desktop-packages] [Bug 1808908] Re: Screen not locked when coming out of suspend/hibernate

2019-01-18 Thread Marc Deslauriers
Are you able to reproduce this issue at will?

It sounds like there is something wrong with your authentication
settings. Did you install fingerprint reader software, or are you
connected to an LDAP directory?

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

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

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

Title:
  Screen not locked when coming out of suspend/hibernate

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.04.1

  Just a few minutes ago, I typed the first character of my password,
  and the lock screen didn't change to the login screen. I typed the
  character again and nothing happened, so I pressed the spacebar to try
  to get the thing's attention.

  Then it unlocked.

  This is spooked me, so I restarted my laptop and tried logging in with
  a random string, and nothing happened. I logged in with my regular
  password and then promptly changed it.

  I tried unlocking my system with my old password, and it worked.
  However, the terminal only recognizes my new root password.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unknown
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 17 23:10:46 2018
  InstallationDate: Installed on 2018-09-15 (94 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen not locked when coming out of suspend/hibernate
  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/1808908/+subscriptions

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


[Desktop-packages] [Bug 1807514] Re: update error

2019-01-18 Thread Marc Deslauriers
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  update error

Status in xorg package in Ubuntu:
  New

Bug description:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Dec  8 17:13:53 2018
  DistUpgraded: 2018-12-08 17:07:42,953 DEBUG /openCache(), new cache size 61306
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1682:3030]
  InstallationDate: Installed on 2014-02-15 (1757 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MachineType: Dell Inc. Dell DXP051
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=e3337e9d-4116-4f99-b96f-8019182e5c07 ro
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-12-08 (0 days ago)
  dmi.bios.date: 01/08/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0YC523
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd01/08/2007:svnDellInc.:pnDellDXP051:pvr:rvnDellInc.:rn0YC523:rvr:cvnDellInc.:ct7:cvr:
  dmi.product.name: Dell DXP051
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sun Nov  4 10:33:25 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.2

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

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


[Desktop-packages] [Bug 1808861] Re: Problem crashes Unreportable - Invalid core dump: BFD: warning: apport_core is truncated

2019-01-18 Thread Mario Vukelic
I have hundreds of gigs free disk space and 16 GB or RAM of which
typically only 50% is even used

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

Title:
  Problem crashes Unreportable - Invalid core dump: BFD: warning:
  apport_core is truncated

Status in apport package in Ubuntu:
  Invalid
Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Trying to report a crash in chromium-browser, get Unreportable reason
  Invalid core dump: BFD: warning apport_core is truncated (see
  screenshot, can't copy message from apport dialog - bug # 1273752).

  UnreportableReason:
   Invalid core dump: BFD: warning: /tmp/apport_core_6yb3cl_7 is truncated: 
expected core file size >= 1245646848, found: 760283136
   warning: core file may not match specified executable file.

  
  Expected: able to report ?

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.5
  ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportLog:
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, 
signal 5, core limit 0, dump mode 1
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: 
/usr/lib/chromium-browser/chromium-browser (command line 
"/usr/lib/chromium-browser/chromium-browser\ --enable-pinch")
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
   ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report 
/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 17 15:30:28 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (96 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago)

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

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


[Desktop-packages] [Bug 1768291] Re: lirc is flooding the syslog with two lines each second

2019-01-18 Thread Chris
This problem also affects me. I am running Ubuntu 18.04 LTS with MythTV, and I 
sometimes plug in a remote control USB. When it's not plugged in, LIRC spams 
the syslog. I tried to disable startup of lircd daemon but that didn't seem to 
work. 
   sudo systemctl disable lircd.service
   sudo systemctl disable lircd.socket
and this appeared to set the links in /etc/rc2.d to be "K*lircd (kill) ) but
the glob spamming still occurred after the next reboot.

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

Title:
  lirc is flooding the syslog with two lines each second

Status in lirc package in Ubuntu:
  Triaged

Bug description:
  Hello,

  in the syslog every second two lines are written:

  May  1 18:05:19 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:19 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:20 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:20 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:21 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:21 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:22 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:22 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:23 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:23 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:24 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:24 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:25 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:25 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:26 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:26 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:27 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:27 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:28 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:28 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*

  This is not only annoying as it makes it difficult to use the syslog
  for checking the system, but also it writes too much data into the log
  (18MB each day). Also it keeps the hard disc awaken what is bad for
  standby.

  Kubuntu 18.04
  ii  liblirc-client0:amd64 0.10.0-2 amd64infra-red remote control 
support - client library
  ii  liblirc0:amd640.10.0-2 amd64Infra-red remote control 
support - Run-time libraries
  ii  lirc  0.10.0-2 amd64Infra-red remote control 
support - daemons and utils

  I do not have infrared remote control hardware. But I cannot purge the
  packages as other packages I want to keep would be removed as well.
  Deactivating the services in systemd does not help (or I am doing
  something wrong?)

  Greetings
  Gert

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

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


[Desktop-packages] [Bug 1811719] Re: sfd

2019-01-18 Thread Marc Deslauriers
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> 
About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by 
checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!


** Information type changed from Private Security to Public

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

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

Title:
  sfd

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  dfsfd

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jan 14 23:02:27 2019
  DistUpgraded: 2018-12-12 20:39:45,935 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] 
(prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Wrestler [Radeon HD 7340] [104d:90ad]
  InstallationDate: Installed on 2016-04-24 (995 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Sony Corporation SVE1112M1EW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=40da7131-b99a-4e5b-9c5e-81ba4975e74c ro nopat vesafb.invalid=1 
drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-12-12 (33 days ago)
  dmi.bios.date: 08/22/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0120D8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0120D8:bd08/22/2012:svnSonyCorporation:pnSVE1112M1EW:pvrC60B8BEP:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVE1112M1EW
  dmi.product.version: C60B8BEP
  dmi.sys.vendor: Sony Corporation
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Dec 12 18:07:04 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

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

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


[Desktop-packages] [Bug 1812089] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-commo

2019-01-18 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: trying
  to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in
  package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  See that...

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Wed Jan 16 22:02:51 2019
  DuplicateSignature:
   package:nvidia-340:(not installed)
   Unpacking nvidia-340 (340.107-0ubuntu0.18.04.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/nvidia-340_340.107-0ubuntu0.18.04.1_amd64.deb 
(--unpack):
trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in 
package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1
  ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which 
is also in package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1
  InstallationDate: Installed on 2019-01-03 (13 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package 
nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1812089/+subscriptions

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


[Desktop-packages] [Bug 1812089] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-commo

2019-01-18 Thread Marc Deslauriers
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: trying
  to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in
  package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  See that...

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Wed Jan 16 22:02:51 2019
  DuplicateSignature:
   package:nvidia-340:(not installed)
   Unpacking nvidia-340 (340.107-0ubuntu0.18.04.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/nvidia-340_340.107-0ubuntu0.18.04.1_amd64.deb 
(--unpack):
trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in 
package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1
  ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which 
is also in package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1
  InstallationDate: Installed on 2019-01-03 (13 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package 
nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1812089/+subscriptions

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


[Desktop-packages] [Bug 1448778] Re: Evince fails to display some fonts (some font thing failed)

2019-01-18 Thread Romano Giannetti
And by the way, just if somebody is still struggling to find where the
"good" error messages (instead of the surprising useful "some font thing
failed"), grep for apparmor in /var/log/kern.log

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

Title:
  Evince fails to display some fonts (some font thing failed)

Status in evince package in Ubuntu:
  Invalid

Bug description:
  Dear experts,

  Since the upgrade to Ubuntu 15.04, evince fails to display some fonts
  of most of my latex pdfs. I attached an example of the pdf rendered by
  evince, and a screenshot of what it's supposed to look like. The
  console is spammed with errors:

  'some font thing failed'

  The pdf display correctly with xpdf and  okular.

  Thanks

  Description:  Ubuntu 15.04
  Release:  15.04
  evince:
Installed: 3.14.2-0ubuntu2
Candidate: 3.14.2-0ubuntu2
Version table:
   *** 3.14.2-0ubuntu2 0
  500 http://ftp.belnet.be/ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: evince 3.14.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 26 23:15:02 2015
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1795342] Re: Higher power consumption when running gnome-shell compared to unity

2019-01-18 Thread Irfan
gjs version is 1.54.3.

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

Title:
  Higher power consumption when running gnome-shell compared to unity

Status in The Ubuntu Power Consumption Project:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hi,

  I am running Ubuntu on Thinkpad. I am facing battery back up issues on both 
18.04 and 18.10 versions. Before that I was running Ubuntu 16.04 with a normal 
back of almost 4 hours ( 2 Sony Batteries with normal back up of up to min of 6 
hours on Linux Mint 19) and when upgrading to 18.04 it reduced to 3 hours max 
on normal usage and less than 2 hours on heavy use.
  I tried installing Unity session on 18.04/10, the back up increased. I think 
it is Gnome doing the mess.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-02 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Tags:  cosmic
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1448778] Re: Evince fails to display some fonts (some font thing failed)

2019-01-18 Thread Romano Giannetti
My solution was to apply this diff:

diff --git a/./etc-apparmor.d-abstractions-fonts 
b/etc/apparmor.d/abstractions/fonts
index 45cdf9a..44c54ac 100644
--- a/./etc-apparmor.d-abstractions-fonts
+++ b/etc/apparmor.d/abstractions/fonts
@@ -51,6 +51,8 @@
 
   /usr/local/share/fonts/   r,
   /usr/local/share/fonts/** r,
+  /home/local/share/fonts/   r,
+  /home/local/share/fonts/** r,
 
   # poppler CMap tables
   /usr/share/poppler/cMap/**r,

...and the reloading the profiles (sudo service apparmor reload). So if
you have symlinked fonts directory, you simply have to add them to the
profile.

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

Title:
  Evince fails to display some fonts (some font thing failed)

Status in evince package in Ubuntu:
  Invalid

Bug description:
  Dear experts,

  Since the upgrade to Ubuntu 15.04, evince fails to display some fonts
  of most of my latex pdfs. I attached an example of the pdf rendered by
  evince, and a screenshot of what it's supposed to look like. The
  console is spammed with errors:

  'some font thing failed'

  The pdf display correctly with xpdf and  okular.

  Thanks

  Description:  Ubuntu 15.04
  Release:  15.04
  evince:
Installed: 3.14.2-0ubuntu2
Candidate: 3.14.2-0ubuntu2
Version table:
   *** 3.14.2-0ubuntu2 0
  500 http://ftp.belnet.be/ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: evince 3.14.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 26 23:15:02 2015
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1812014] Re: keyboard not responding after suspend after some time plus performance problem

2019-01-18 Thread Krzysztof
So... it happend again. The workaround doesn't work.

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

Title:
  keyboard not responding after suspend after some time plus performance
  problem

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I work on Lenovo laptop y-700. When I resume system after suspend, keyboards 
stop working, and sometimes there are performance problems visible when playing 
videos. It happens not immediately but after a few minutes or even a few hours 
of working. Restart or shutdown does not finish correctly and I need to hold 
the power button for a few seconds.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   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'"
  InstallationDate: Installed on 2018-08-06 (165 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1812057] Re: Upgrade Lost Firefox ESR

2019-01-18 Thread Ubuntu User
Obviously this has nothing to do with PPAs.  This has to do with the
system wiping out all the installed programs and forcing manual re-
installations.

In this specific case, Ubuntu also damaged the linkages between programs
and their data.  This is most bizarre because one would have thought
that the upgrade process would do no such thing and the strong promotion
to do the upgrade would imply to most people that their productivity
would be protected.

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

Title:
  Upgrade Lost Firefox ESR

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  System was upgraded from Xubuntu 14 to 16 by DVD.  It wiped out many
  things, including the installation of Firefox ESR.

  ESR was manually reinstalled, but there appears to be no integration
  with the former profiles.  While they still exist, both Firefox
  Quantum and Firefox ESR see the exact same profiles.  There appears to
  be no way to remedy the problem.

  No crash is involved.  If -profilemanager is used in Firefox, the same
  choices appear in both versions.  This was not the case prior to the
  upgrade.


  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  firefox-esr:
Installed: 52.9.0esr-1~16.04.york0
Candidate: 52.9.0esr-1~16.04.york0
Version table:
   *** 52.9.0esr-1~16.04.york0 500
  500 http://ppa.launchpad.net/jonathonf/firefox-esr-52/ubuntu 
xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  firefox:
Installed: 64.0+build3-0ubuntu0.16.04.1
Candidate: 64.0+build3-0ubuntu0.16.04.1
Version table:
   *** 64.0+build3-0ubuntu0.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   45.0.2+build1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

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

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


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

2019-01-18 Thread Krzysztof
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1812014/+attachment/5230366/+files/ProcCpuinfoMinimal.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/1812014

Title:
  keyboard not responding after suspend after some time plus performance
  problem

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I work on Lenovo laptop y-700. When I resume system after suspend, keyboards 
stop working, and sometimes there are performance problems visible when playing 
videos. It happens not immediately but after a few minutes or even a few hours 
of working. Restart or shutdown does not finish correctly and I need to hold 
the power button for a few seconds.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   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'"
  InstallationDate: Installed on 2018-08-06 (165 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1812014] Re: keyboard not responding after suspend after some time plus performance problem

2019-01-18 Thread Krzysztof
apport information

** Tags added: apport-collected cosmic

** Description changed:

- I work on Lenovo laptop y-700. When I resume system after suspend,
- keyboards stop working, and sometimes there are performance problems
- visible when playing videos. It happens not immediately but after a few
- minutes or even a few hours of working. Restart or shutdown does not
- finish correctly and I need to hold the power button for a few seconds.
+ I work on Lenovo laptop y-700. When I resume system after suspend, keyboards 
stop working, and sometimes there are performance problems visible when playing 
videos. It happens not immediately but after a few minutes or even a few hours 
of working. Restart or shutdown does not finish correctly and I need to hold 
the power button for a few seconds.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu13.1
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 18.10
+ GsettingsChanges:
+  b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
+  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'"
+ InstallationDate: Installed on 2018-08-06 (165 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: gnome-shell 3.30.1-2ubuntu1.18.10.2
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=pl_PL.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
+ Tags:  cosmic
+ Uname: Linux 4.18.0-13-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1812014/+attachment/5230365/+files/Dependencies.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/1812014

Title:
  keyboard not responding after suspend after some time plus performance
  problem

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I work on Lenovo laptop y-700. When I resume system after suspend, keyboards 
stop working, and sometimes there are performance problems visible when playing 
videos. It happens not immediately but after a few minutes or even a few hours 
of working. Restart or shutdown does not finish correctly and I need to hold 
the power button for a few seconds.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   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'"
  InstallationDate: Installed on 2018-08-06 (165 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1165573] Re: Nautilus ignores keystrokes when I don't type slowly.

2019-01-18 Thread Andrew
Yes, thanks, it's still a problem with nautilus 1:3.26.4-0~ubuntu18.04.3
on Ubuntu 18.04.1 LTS.

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

Title:
  Nautilus ignores keystrokes when I don't type slowly.

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  What I'm doing:

1) Type part of a filename.
2) Press Enter.

  What I expect to happen:

The file should open.

  What actually happens:

The file does not open.

  Workaround:

1) Type part of a filename.
2) Wait a moment.
3) Press Enter.

  I've attached a screencast of the problem happening.

  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 x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Sat Apr  6 15:39:52 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2013-04-06 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  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/1165573/+subscriptions

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


[Desktop-packages] [Bug 1808861] Re: Problem crashes Unreportable - Invalid core dump: BFD: warning: apport_core is truncated

2019-01-18 Thread Brian Murray
What happened is that gdb did not complete writing the core file
possibly due to a lack of memory or disk space on the system, then
because the core file is incomplete apport will not create a crash file
with the core dump. There isn't anything we can do here, sometimes core
file creation just fails.

** Changed in: apport (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Problem crashes Unreportable - Invalid core dump: BFD: warning:
  apport_core is truncated

Status in apport package in Ubuntu:
  Invalid
Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Trying to report a crash in chromium-browser, get Unreportable reason
  Invalid core dump: BFD: warning apport_core is truncated (see
  screenshot, can't copy message from apport dialog - bug # 1273752).

  UnreportableReason:
   Invalid core dump: BFD: warning: /tmp/apport_core_6yb3cl_7 is truncated: 
expected core file size >= 1245646848, found: 760283136
   warning: core file may not match specified executable file.

  
  Expected: able to report ?

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.5
  ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportLog:
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, 
signal 5, core limit 0, dump mode 1
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: 
/usr/lib/chromium-browser/chromium-browser (command line 
"/usr/lib/chromium-browser/chromium-browser\ --enable-pinch")
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
   ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report 
/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 17 15:30:28 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (96 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago)

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

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


[Desktop-packages] [Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)

2019-01-18 Thread lol nope
I'm experiencing this same issue as well.  Syslog grew to >100GB
overnight.

My configuration:
- Fresh install of Ubuntu 18.04.1
- HP z800 workstation with 2x Xeon X5680
- NVidia GTX 1070 Ti w/ 3 screens attached

I need to stick with LTS releases but if there is a way to install a
particular version of gnome-shell with the bug addressed I'd be happy to
give it a try.

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

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

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/602

  ---

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

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

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

[Desktop-packages] [Bug 1186647] Re: /usr/bin/nautilus:6:g_assertion_message:g_assertion_message_expr:nautilus_bookmark_connect_file:nautilus_bookmark_connect_file:g_object_newv

2019-01-18 Thread Sebastien Bacher
The error tracker shows that has been fixed in newer versions

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

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

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

Title:
  
/usr/bin/nautilus:6:g_assertion_message:g_assertion_message_expr:nautilus_bookmark_connect_file:nautilus_bookmark_connect_file:g_object_newv

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  
https://errors.ubuntu.com/bucket/?id=/usr/bin/nautilus:6:g_assertion_message:g_assertion_message_expr:nautilus_bookmark_connect_file:nautilus_bookmark_connect_file:g_object_newv

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

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


[Desktop-packages] [Bug 1075516] Re: Copy hangs in local network

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

Title:
  Copy hangs in local network

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  I copy files from one Ubuntu system to another.They are both in local
  wireless network.

  I shared entire dir on one, and tried to copy some files to another.
  It works for some time and then it just hangs at some point.

  Here is the example screenshot, it just hangs like this
  http://i.stack.imgur.com/KAaHA.png.

  After I cancel, Nautilus icon in lauchbar keeps progress bar, so I
  guess there is some problem.

  If you need any additional info, logs or whatever is required to
  reproduce and fix this bug, I can provide it.

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

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


[Desktop-packages] [Bug 776781] Re: dropbox extension slows down nautilus

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

Title:
  dropbox extension slows down nautilus

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: nautilus

  I have been using Ubuntu Natty since it was released, and nautilus was
  running just fine. Today, when I went on my computer, Nautilus is so
  slow it is unusable. This is the second time this has happened. (the
  first was while using a Natty Dev version, which prompted me to
  install the final.) If more information or data is needed, please ask.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: nautilus 1:2.32.2.1-0ubuntu13
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  Architecture: i386
  Date: Tue May  3 18:06:47 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   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/776781/+subscriptions

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


[Desktop-packages] [Bug 1096340] Re: compiz, unity crash - nvidia 310 driver

2019-01-18 Thread Sebastien Bacher
that's not a nautilus issue

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

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

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

Title:
  compiz, unity crash - nvidia 310 driver

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  nvidia 310-experimental driver

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
  Uname: Linux 3.5.0-21-generic x86_64
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: amd64
  Date: Sat Jan  5 12:48:21 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'800x550+65+24'"
  InstallationDate: Installed on 2013-01-05 (0 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.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/1096340/+subscriptions

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


[Desktop-packages] [Bug 1069123] Re: Nautilus freeze for minute when first open home folder

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

Title:
  Nautilus freeze for minute when first open home folder

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 12.10 (Latest updates installed for 2012-10-20)
  Nautilus 3.4.2

  If launch «Nautilus» after OS start or after «killall nautilus» its freeze 
for approximately a minute.
  This happens only when open «Home» folder.
  Which enabled compiz "Show repaint" plugin became visible full window redraw 
many times.

  In attachment You can find a log of executing trace command 
  «strace -ttt -o ~/Template/nautilus.strace nautilus»
  In this log a lot of command similar to

  1350668341.300860 brk(0x1b7e000)= 0x1b7e000
  1350668341.301461 brk(0x1b6e000)= 0x1b6e000
  1350668341.301585 brk(0x1b5e000)= 0x1b5e000
  1350668341.302492 brk(0x1b4e000)= 0x1b4e000
  1350668341.306849 
lstat("/usr/share/icons/Humanity/places/16/inode-directory.svg", 
{st_mode=S_IFLNK|0777, st_size=10, ...}) = 0
  1350668341.307088 
stat("/usr/share/icons/Humanity/places/16/inode-directory.svg", 
{st_mode=S_IFREG|0644, st_size=11672, ...}) = 0
  1350668341.307234 
readlink("/usr/share/icons/Humanity/places/16/inode-directory.svg", 
"folder.svg"..., 256) = 10
  1350668341.307970 
open("/usr/share/icons/Humanity/places/16/inode-directory.svg", O_RDONLY) = 21
  1350668341.308310 fstat(21, {st_mode=S_IFREG|0644, st_size=11672, ...}) = 0
  1350668341.308521 read(21, "https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1069123/+subscriptions

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


[Desktop-packages] [Bug 871385] Re: "Timeout while waiting for mount to appear" when mounting NFS

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

Title:
  "Timeout while waiting for mount to appear" when mounting NFS

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  I've got a couple NFS mounts in my /etc/fstab, set up to be user-
  mountable.  These mounts show up as network mountpoints in Nautilus's
  computer:// location, which I can click on to mount.  When I do click
  on them, nautilus successfully mounts the mountpoint -- it appears as
  a new harddisk in the same computer:// view (right next to the
  original icon I clicked).  However, Nautilus then doesn't switch my
  view to that location, and after a few seconds pops up a message,
  "Unable to mount location: Timeout waiting for mount to appear".

  After all this, I can manually click on the newly created icon and
  browse the drive.

  Further, double-clicking on the original icon while the mount is
  already there causes nautilus to pop up a message, "mount.nfs:
   is busy or already mounted".  What I expect to happen is
  that this takes me to the view of the root of the mount.

  Optimally, there shouldn't be two icons either.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: nautilus 1:3.2.0-0ubuntu5
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu2
  Architecture: amd64
  Date: Sun Oct  9 10:13:05 2011
  ExecutablePath: /usr/bin/nautilus
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20111007.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  XsessionErrors:
   (nautilus:1645): Gtk-CRITICAL **: gtk_action_set_visible: assertion 
`GTK_IS_ACTION (action)' failed
   (nautilus:1645): Gtk-CRITICAL **: gtk_action_set_visible: assertion 
`GTK_IS_ACTION (action)' failed
   (dropbox:1670): Gdk-CRITICAL **: 
IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion 
`private->update_and_descendants_freeze_count > 0' failed
   (npviewer.bin:2276): Gtk-WARNING **: Failed to load type module: 
/usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so

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

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


[Desktop-packages] [Bug 1017278] Re: High contrast theme is unusable in nautilus

2019-01-18 Thread Sebastien Bacher
The issue has been resolved in newer ubuntu versions

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

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

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

Title:
  High contrast theme is unusable in nautilus

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Set the contrast to 'high' and you get the following... oversight. See
  screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu10
  Architecture: amd64
  Date: Mon Jun 25 08:51:47 2012
  EcryptfsInUse: Yes
  GsettingsChanges:
   org.gnome.nautilus.window-state geometry '926x1021+307+88'
   org.gnome.nautilus.window-state sidebar-width 172
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to precise on 2012-04-26 (59 days ago)

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

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


[Desktop-packages] [Bug 1101162] Re: Ubuntu 12.04: Frequent System Freeze

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

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

Title:
  Ubuntu 12.04: Frequent System Freeze

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  (nautilus:2626): CRITICAL **: syncdaemon_status_info_get_online:
  assertion `SYNCDAEMON_IS_STATUS_INFO (sinfo)' failed

  
  Jan 23 17:09:48 CS-LT-0001 gnome-session[2545]: WARNING: Could not parse 
desktop file 
/home/km/.config/autostart/xfce4-settings-helper-autostart.desktop: Key file 
does not have key 'Name'
  Jan 23 17:09:48 CS-LT-0001 gnome-session[2545]: WARNING: could not read 
/home/km/.config/autostart/xfce4-settings-helper-autostart.desktop
  Jan 23 17:09:48 CS-LT-0001 gnome-session[2545]: WARNING: Could not parse 
desktop file /home/km/.config/autostart/gshared.desktop: Key file does not have 
key 'Type'
  Jan 23 17:09:48 CS-LT-0001 gnome-session[2545]: WARNING: could not read 
/home/km/.config/autostart/gshared.desktop

  I have been noticing frequent system hang for more than a month on my 
Laptop(G580). However the frequency increased to every 30-45 min recently.
  I can't generate a crash after the hang as nothing works, I have to do a hard 
reboot.
  I tried to generating a crash using  Ctrl’+'Alt’+'SysRq’+1 followed by 
Ctrl’+'Alt’+'SysRq’+t, but no use. Finally I had to do a hard reboot.

  Please help me fix this issue; Do let me know if you need any help
  from me.

  The following are the system and package information of my laptop

  System information report, generated by Sysinfo: 01/18/2013 16:45:30
  
  http://sourceforge.net/projects/gsysinfo

  SYSTEM INFORMATION
   Running Ubuntu Linux, the Ubuntu 12.04 (precise) release.
   GNOME: unknown (unknown)
   Kernel version: 3.2.0-36-generic-pae (#57-Ubuntu SMP Tue Jan 8 22:01:06 UTC 
2013)
   GCC: 4.6 (i686-linux-gnu)
   Xorg: 1.11.3 (29 August 2012  12:10:05AM) (29 August 2012  12:10:05AM)
   Hostname: CS-LT-0001
   Uptime: 0 days 0 h 38 min

  CPU INFORMATION
   GenuineIntel, Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
   Number of CPUs: 4
   CPU clock currently at 1200.000 MHz with 3072 KB cache
   Numbering: family(6) model(58) stepping(9)
   Bogomips: 4988.84
   Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm constant_tsc 
arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic 
popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb 
xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms

  MEMORY INFORMATION
   Total memory: 3750 MB
   Total swap: 3940 MB

  STORAGE INFORMATION
   SCSI device -  scsi1
    Vendor:  ATA
    Model:  ST9500325AS
   SCSI device -  scsi4
    Vendor:  PLDS
    Model:  DVD-RW DS8A8SH
   SCSI device -  scsi6
    Vendor:  Multiple
    Model:  Card  Reader

  HARDWARE INFORMATION
  MOTHERBOARD
   Host bridge
    Intel Corporation Ivy Bridge DRAM Controller (rev 09)
    Subsystem: Lenovo Device 3977
   PCI bridge(s)
    Intel Corporation Panther Point PCI Express Root Port 1 (rev c4) (prog-if 
00 [Normal decode])
    Intel Corporation Panther Point PCI Express Root Port 2 (rev c4) (prog-if 
00 [Normal decode])
    Intel Corporation Panther Point PCI Express Root Port 4 (rev c4) (prog-if 
00 [Normal decode])
    Intel Corporation Panther Point PCI Express Root Port 1 (rev c4) (prog-if 
00 [Normal decode])
    Intel Corporation Panther Point PCI Express Root Port 2 (rev c4) (prog-if 
00 [Normal decode])
    Intel Corporation Panther Point PCI Express Root Port 4 (rev c4) (prog-if 
00 [Normal decode])
   ISA bridge
    Intel Corporation Panther Point LPC Controller (rev 04)
    Subsystem: Lenovo Device 3977

  GRAPHIC CARD
   VGA controller
    Intel Corporation Ivy Bridge Graphics Controller (rev 09) (prog-if 00 [VGA 
controller])
    Subsystem: Lenovo Device 3977

  SOUND CARD
   Multimedia controller
    Intel Corporation Panther Point High Definition Audio Controller (rev 04)
    Subsystem: Lenovo Device 3977

  NETWORK
   Network controller
    Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) 
(rev 01)
    Subsystem: Lenovo Device 30a1
   Ethernet controller
    Atheros Communications Inc. AR8162 Fast Ethernet (rev 10)
    Subsystem: Lenovo Device 3978

  Package Information can be found in the attached document

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

[Desktop-packages] [Bug 952084] Re: Cannot set solid color background when background fading is disabled

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

Title:
  Cannot set solid color background when background fading is disabled

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

Bug description:
  When I try to set a solid color as desktop background with background
  fading disabled, all I get is a black background, no matter what color
  I choose in the control center/System Settings. The same works fine if
  I either enable background fading or use a  vertical or horizontal
  'color-shading-type'.

  TEST CASE:
  1. Press , type 'Appearance', and open the result.
  2. Make sure you have a background image selected.
  3. Disable background fading from the command line:

  gsettings set org.gnome.nautilus.desktop background-fade false

  4. In the 'Appearance' dialog, try to set a solid color other than
  black.

  RESULT:
  * No matter what color is set, the background will always stay black.

  To go back to the working case, run the following from the command
  line:

  gsettings set org.gnome.nautilus.desktop background-fade true

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.3.91-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  Date: Sun Mar 11 09:57:16 2012
  GsettingsChanges:
   org.gnome.nautilus.window-state geometry '927x1027+65+24'
   org.gnome.nautilus.window-state sidebar-width 183
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1165573] Re: Nautilus ignores keystrokes when I don't type slowly.

2019-01-18 Thread Sebastien Bacher
Is that still an issue for you in newer versions?

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

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

Title:
  Nautilus ignores keystrokes when I don't type slowly.

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  What I'm doing:

1) Type part of a filename.
2) Press Enter.

  What I expect to happen:

The file should open.

  What actually happens:

The file does not open.

  Workaround:

1) Type part of a filename.
2) Wait a moment.
3) Press Enter.

  I've attached a screencast of the problem happening.

  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 x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Sat Apr  6 15:39:52 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2013-04-06 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  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/1165573/+subscriptions

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


[Desktop-packages] [Bug 1172796] Re: application chooser is misleaded by filename that corresponds to application name

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

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

Title:
  application chooser is misleaded by filename that corresponds to
  application name

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  nautilus/application chooser has trouble if the software clustalw and
  clustal X is installed and a simple textfile is named "clustalw"

  On trying to open the "clustalx" textfile nautilus is trying to to
  this with the application Clustal X.

  To explain this: clustalw is the background program for Clustal X

  , so there is some logic in it that a "clustalw" file provoce a call
  of Clustal X  (the last is the graphical frontend).

  Anyway, this misbehaviour is just wrong.

  
  Steps to reproduce:
  ---

  1.Install clustalw
  2.Install clustalx
  3.call a termainal and give the follwowing line

  man clustalw > clustalw

  (you see it redirects the aoutput to a simple textfile named clustalw
  -> the textfile mentioned above)

  4.Call nautilus and switch to the directory where the textfile from the 
redirect in step3 is saved(properly your actual working directory.
  5. Try to open clustalw with simple double clicking
  6. See nothing
  7.Use right mouse click on the clustalx textfile and see in the menu that 
nautilus try to use Clustl X to open the textfile -> this could not work.

  Additional: 
  -
  Nautilus must choose also in this case the system editor for open the 
clustalw file produced in step3: By default gedit

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Thu Apr 25 18:49:52 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'796x550+65+24'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2013-01-13 (102 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-18 (6 days ago)

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

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


[Desktop-packages] [Bug 1165806] Re: rename in nautilus needs to go to next line to select last letter

2019-01-18 Thread Sebastien Bacher
The widget used to rename files has changed with deprecated this issue

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

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

Title:
  rename in nautilus needs to go to next line to select last letter

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  When I rename a file with name on several lines it does not let me place the 
cursor at the end of a line, I need to put it at the beginning of next line ; 
both should be doable.
  With this behaviour, you can't select a word in a sentence at the end of the 
line by selecting it : you need to select the beginning of the next line, and 
it's not a correct GUI behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Sun Apr  7 18:37:49 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'1260x717+1687+164'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
   b'org.gnome.nautilus.window-state' b'side-pane-view' b"'tree'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'372'
   b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true'
  InstallationDate: Installed on 2011-07-05 (641 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to quantal on 2012-10-23 (166 days ago)

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

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


[Desktop-packages] [Bug 1166508] Re: Sporadic Transfer Rates To Mounted Samba Share

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

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

Title:
  Sporadic Transfer Rates To Mounted Samba Share

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Nautilus transfers for a second or two, and then stops transferring
  for a second or two, then transfers for a second or two, then stops
  transferring for two seconds. This makes transfer rates very slow when
  dealing with a lot of large files.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu14
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Mon Apr  8 17:42:08 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'800x550+478+373'"
  InstallationDate: Installed on 2013-04-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  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/1166508/+subscriptions

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


[Desktop-packages] [Bug 1165136] Re: Nautilus-Bookmarks got lost

2019-01-18 Thread Sebastien Bacher
It wouldn't make sense now to handle that migration, closing

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

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Nautilus-Bookmarks got lost

Status in nautilus package in Ubuntu:
  Won't Fix

Bug description:
  Today I've upgraded to Raring Ringtail (13.04). After the upgrade I've
  realized that all my nautilus-bookmarks got lost.

  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 x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Fri Apr  5 20:36:28 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'683x716+684+24'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2012-11-08 (148 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-05 (0 days ago)

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

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


[Desktop-packages] [Bug 1173692] Re: launcher dragged from Dash into carpet miss executable bit

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

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

Title:
  launcher dragged from Dash into carpet miss executable bit

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Release of Ubuntu:13.04
  Package Version: 1:3.6.3-0ubuntu16
  Expected Results: it copy the launcher icon as it is
  Actual Results:it copy the launcher file without the executable bit set

  Hallo
  testcase:
  -create a carpet in Desktop
  -open Dash and drag a launcher into the created carpet
  -open the carpet and you can see a text file icon
  -double click on it and nautilus will tell that it isn't a trusted launcher.

  *workaround*
  -right click on the dragged launcher and select Properties
  -select Permission and mark Executable

  Thanks
  Fabio

  ProblemType: BugDistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sat Apr 27 19:12:15 2013
  EcryptfsInUse: Yes
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'939x715+425+24'"
  InstallationDate: Installed on 2012-10-12 (196 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20121011)MarkForUpload: TrueSourcePackage: 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/1173692/+subscriptions

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


[Desktop-packages] [Bug 1130399] Re: Nautilus CIFS Windows Share Mount Bug

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

Title:
  Nautilus CIFS Windows Share Mount Bug

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

Bug description:
  In Ubuntu 12.04 (and I believe ALL desktop versions newer than 10.10)
  are effected by this bug.

  When mounting a Windows share via Nautilus, e.g. File -> Connect to
  Server -> Type: Windows Share

  gvfs will FAIL on authentication unless BOTH the DOMAIN NAME and
  SERVER NAME are in CAPS.

  This is a major issue and will cause almost all users to fail to
  authenticate. Nautilus shows no error except verify user details.
  Nothing in logs. And will end up locking a Windows Domain user
  account.

  Also for some reason the "Add Bookmark" checkbox is missing from the
  mount process which makes no sense. This causes an additional
  usability issue as to add a bookmark the user then needs to pull up
  Nautilus, Right Click the Mount they loaded, and then Add Bookmark
  from there. This process was much more streamlined (and the bug didn't
  exist) in 10.04.

  I hope you guys can repair this soon as any mixed environment using
  Ubuntu desktops and doing a common task such as mounting a windows
  share in a corporate environment is broken in 12.04.

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

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


[Desktop-packages] [Bug 1177181] Re: Nautlis does not show the fil operation window

2019-01-18 Thread Sebastien Bacher
the UI changed since which deprecates that report

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

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

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

Title:
  Nautlis does not show the fil operation window

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  OS 12.04. If a file operation takes place you see only a small
  indicator over the personal folder in the dock. Right clicking this
  folder the option menu is open with the point "show file operation.
  Choosing this item, nothing happens.

  Version 12.04 (precise) (32-Bit)
  Kernel Linux 3.5.0-28-generic
  GNOME 3.4.2

  Hardware:
  Speicher: 2,0 GiB
  Prozessor: ntel® Pentium(R) 4 CPU 2.80GHz × 2 

  Nautilus
  Version 3.4.2

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

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


[Desktop-packages] [Bug 1176638] Re: Transparency bug when taking a screenshot of a Files window.

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

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

Title:
  Transparency bug when taking a screenshot of a Files window.

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  I took a screenshot of a nautilus ("Files"?!) window to document bug
  #1176634, and in doing so noticed that the screenshot has a weird
  transparent region on the left. I'm not sure if this is related to
  Files or to gnome-screenshot, though.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May  5 15:02:41 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'680x716+0+24'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'245'
  InstallationDate: Installed on 2012-02-28 (432 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-27 (8 days ago)

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

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


[Desktop-packages] [Bug 1174686] Re: Cannot "Open folder in new window" since change to Files in Ubuntu 13.04

2019-01-18 Thread Sebastien Bacher
That's not an option Ubuntu plans to add but feel free to report it
upstream on https://gitlab.gnome.org/GNOME/nautilus/issues/

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Cannot "Open folder in new window" since change to Files in Ubuntu
  13.04

Status in nautilus package in Ubuntu:
  Won't Fix

Bug description:
  Since Ubuntu's Nautilus changed his name to Files, it changed to
  another upstream version.

  In this version opening folders in a new window is no longer possible.
  There still is an "Open in new tab" option, but no longer an option
  for opening in a new window.

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

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


[Desktop-packages] [Bug 1152721] Re: weird graphical issue when copying files

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

Title:
  weird graphical issue when copying files

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  on my screensho you can see, that on the stop button of the copy
  window, is a werid graphical issue. i produced the issue this way :

  first : add XNBdrivers.com to a mauntpoint from nautilus by 'connect
  to server...'

  to begin :

  1. start a copy window by copying the Server's content to my desktop
  (for me : FTP://xnbrivers.com)

  2. minimize the window

  3. reopen the window from the minimized state

  4. dragging te window quickly out of the left edge of the screen and
  bringing it back to the center of the screen.

  i am able to reproduce this issue, so

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

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


[Desktop-packages] [Bug 501519] Re: ubuntuone-client-gnome prevents nautilus from refreshing after "extract here" or other modifications to the directory in view

2019-01-18 Thread Sebastien Bacher
ubuntuone got deprecated, closing this bug

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  ubuntuone-client-gnome prevents nautilus from refreshing after
  "extract here" or other modifications to the directory in view

Status in Ubuntu One Client:
  Confirmed
Status in nautilus package in Ubuntu:
  Won't Fix
Status in ubuntuone-client package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: ubuntuone-client-gnome

  I noticed that nautilus was not showing newly created files after
  extracting an archive or creating a file in the terminal.  I had to
  manually refresh the view to see the new file.

  The problem goes away if I uninstall the "ubuntuone-client-gnome"
  package, so I think the problem must be caused by the nautilus
  integration for Ubuntu One.

  Does anyone else have this problem and find that it goes away if you
  remove the Ubuntu One client?


  Linux 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC 2009
  x86_64 GNU/Linux

  ProblemType: Bug
  Architecture: amd64
  Date: Tue Dec 29 16:26:22 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/nautilus
  Package: nautilus 1:2.28.1-0ubuntu3
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
  SourcePackage: nautilus
  Uname: Linux 2.6.31-17-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntuone-client/+bug/501519/+subscriptions

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


[Desktop-packages] [Bug 697067] Re: Nautilus gives error, "Could not open location: Invalid Argument" after resume.

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

Title:
  Nautilus gives error, "Could not open location: Invalid Argument"
  after resume.

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: nautilus

  Steps to reproduce:
  Open Places -> Network
  Open Network Computer
  Open Network Share
  Close Nautilus window
  Suspend the laptop
  Resume the laptop
  Open the "Sharename on Servername" link in the Places menu
  Error appears: (Screenshot attached)
  Could not open location 'smb://servername/sharename/'
  Invalid argument

  subsequently:
  Click OK to close the error
  Open the "Sharename on Servername" link in the Places menu
  Nautilus opens enumerating the contents of the share


  Description:  Ubuntu 10.10
  Release:  10.10

  nautilus:
    Installed: 1:2.32.0-0ubuntu1.1
    Candidate: 1:2.32.0-0ubuntu1.1
    Version table:
   *** 1:2.32.0-0ubuntu1.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ maverick-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1:2.32.0-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ maverick/main i386 Packages

  smbclient:
    Installed: 2:3.5.4~dfsg-1ubuntu8.1
    Candidate: 2:3.5.4~dfsg-1ubuntu8.1
    Version table:
   *** 2:3.5.4~dfsg-1ubuntu8.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ maverick-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   2:3.5.4~dfsg-1ubuntu8 0
  500 http://us.archive.ubuntu.com/ubuntu/ maverick/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: nautilus 1:2.32.0-0ubuntu1.1
  ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
  Uname: Linux 2.6.35-24-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Mon Jan  3 22:40:37 2011
  EcryptfsInUse: Yes
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: nautilus

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

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


[Desktop-packages] [Bug 1153246] Re: Nautilus; when windows is hybernated, no option for readonly

2019-01-18 Thread Sebastien Bacher
** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Nautilus; when windows is hybernated, no option for readonly

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  in nuatulus you cannot open a drive when it is hybernated by windows,
  but there is an terminal command avaible to mount it in readonly, why
  no make an button there, with an alert that it starts in readonly and
  why, with an button "open in readonly"

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

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


[Desktop-packages] [Bug 1161344] Re: Nautilus crashes when opening several folders in own windows

2019-01-18 Thread Sebastien Bacher
** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Nautilus crashes when opening several folders in own windows

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  To reproduce:
  1. Go to Preferences>Behaviour and check "Open each folder in its own window".
  2. Select several folders and press ENTER.

  What should happen:
  For each selected folder a window with contents should open.

  What happens:
  Nautilus stops responding and crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.2-0ubuntu7
  ProcVersionSignature: Ubuntu 3.2.0-39.62-generic 3.2.39
  Uname: Linux 3.2.0-39-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  Date: Thu Mar 28 12:22:57 2013
  EcryptfsInUse: Yes
  GsettingsChanges: org.gnome.nautilus.window-state geometry '809x572+65+24'
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  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: 
2013-02-13T17:26:48.911822

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

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


[Desktop-packages] [Bug 684807] Re: There is no easy way to make a partition automatically mount on boot

2019-01-18 Thread Sebastien Bacher
That's a job for the disks utility rather than the file browser

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  There is no easy way to make a partition automatically mount on boot

Status in One Hundred Papercuts:
  Confirmed
Status in nautilus package in Ubuntu:
  Won't Fix

Bug description:
  Mounting a 2nd partition is easy -- just open it from the "Places"
  window. However, making a partition automatically mount on boot is
  much harder than it should be. The only two ways (I can find) to make
  it happen is to either manually edit /etc/fstab or by adding a mount
  command to the startup programs list. Both of these solutions are
  unintuitive and far too complicated for most users.

  Editing /etc/fstab is too difficult because it requires the user to:
  -Know what /etc/fstab is, let alone where it is and how to edit it (and it 
requires root)
  -Know the syntax for a line in /etc/fstab
  -Know the device name for the partition (/dev/sdb1? /dev/sdb2? /dev/sdc1?)

  Adding a mount command to startup programs is too difficult because it 
requires the user to:
  -Know the syntax for mount
  -Know the device name for the partition (/dev/sdb1? /dev/sdb2? /dev/sdc1?)
  -Manually create a folder in /media (which requires root) and give it the 
proper permissions (which it won't have by default)

  Making a partition boot on startup should be as simple as:
  1) Right-click on a mounted partition and click "Properties"
  2) In the properties window click on a check box somewhere that says "Mount 
on startup".

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

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


[Desktop-packages] [Bug 934288] Re: Nautilus Does not Display Menus

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

Title:
  Nautilus Does not Display Menus

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Nautilus (file manager) working fine, then not.

  What happens is the menus stop displaying.

  You select a menu item expecting a list of actions and you get about
  four pixel wide little bump where the list normally displays.

  I suspect it is there but being displayed under the menu bar where it
  is not visible on the display.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: firefox 10.0+build1-0ubuntu0.11.10.1
  ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
  Uname: Linux 3.0.0-15-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  karl   1898 F pulseaudio
   /dev/snd/controlC0:  karl   1898 F pulseaudio
  BuildID: 20120129141257
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe8f8000 irq 44'
 Mixer name : 'Realtek ALC1200'
 Components : 'HDA:10ec0888,103c2a5d,00100101'
 Controls  : 38
 Simple ctrls  : 21
  Card1.Amixer.info:
   Card hw:1 'Set'/'C-Media USB Headphone Set at usb-:00:1a.1-1.1, full 
speed'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:000c'
 Controls  : 7
 Simple ctrls  : 3
  Channel: release
  Date: Fri Feb 17 07:39:17 2012
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.6  metric 1 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.102  
metric 2
  Plugins:
   Shockwave Flash - Lib=libflashplayer.so, Location=/usr/lib/adobe-flashplugin
   DivX® Web Player - Lib=libtotem-mully-plugin.so, 
Location=/usr/lib/mozilla/plugins
   Windows Media Player Plug-in 10 (compatible; Totem) - 
Lib=libtotem-gmp-plugin.so, Location=/usr/lib/mozilla/plugins
   QuickTime Plug-in 7.6.6 - Lib=libtotem-narrowspace-plugin.so, 
Location=/usr/lib/mozilla/plugins
   VLC Multimedia Plugin (compatible Totem 3.0.1) - 
Lib=libtotem-cone-plugin.so, Location=/usr/lib/mozilla/plugins
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=10.0/20120129141257 (Running)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to oneiric on 2012-02-12 (5 days ago)
  WifiSyslog:
   
  dmi.bios.date: 10/24/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.name: Berkeley
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.04
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd10/24/2007:svnHP-Pavilion:pnGN553AA-ABAm9040n:pvr:rvnASUSTeKComputerINC.:rnBerkeley:rvr1.04:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.name: GN553AA-ABA m9040n
  dmi.sys.vendor: HP-Pavilion

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

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


[Desktop-packages] [Bug 1161427] Re: Copy from USB. "Timeout was reached"

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

Title:
  Copy from USB. "Timeout was reached"

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Every time I try to copy a video / file larger than approx. 150MB from
  USB I get this error. "Time was nått"

  If I switch to Windows so it works fine (embarrassing)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4
  Uname: Linux 3.5.0-25-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: i386
  Date: Thu Mar 28 15:25:42 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'999x773+507+227'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'186'
   b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true'
  InstallationDate: Installed on 2012-06-11 (289 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to quantal on 2013-01-05 (81 days ago)
  mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 
2013-02-02T15:29:56.340761

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

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


[Desktop-packages] [Bug 1143799] Re: gvfs and fstab mount

2019-01-18 Thread Sebastien Bacher
the place sidebar is a gtk widget nowadays

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

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

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

Title:
  gvfs and fstab mount

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  I'm using Ubuntu 12.04 LTS. I need to mount some samba share to
  different unprivilleged users in my system with different credentials.

  My fstab:

  #
  proc/proc   procnodev,noexec,nosuid 0   0
  /dev/sda1   /   ext4errors=remount-ro 0   1
  /dev/mapper/sda3_crypt /home   ext4defaults0   2
  /dev/mapper/sda2_crypt noneswapsw  0   0

  //source /home/user1/destination/ cifs 
credentials=/home/user1/.sambacr,uid=user1,gid=user1,iocharset=utf8,dir_mode=0750,file_mode=0640,nounix
  0 0
  //source /home/user2/destination/ cifs
  
credentials=/home/user2/.sambacr,uid=user2,gid=user2,iocharset=utf8,dir_mode=0750,file_mode=0640,nounix
  0 0
  etc

  
  The mount works fine, but in the menu "Places" and sidebar of Nautilus
  only one user can see mounted volume and all other didn't
  Can i do visible mounted share for each user in menu "Places" and
  sidebar of Nautilus?

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

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


[Desktop-packages] [Bug 1157621] Re: access() calls included for debugging hang nautilus on webdav fuse mount

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

Title:
  access() calls included for debugging hang nautilus on webdav fuse
  mount

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Nautilus issues access() calls with the filenames that can't possibly
  exist:

  [pid 14422] access("MARK: nautilus nautilus_directory_emit_change_signals: 
start ", F_OK) = -1 ENOENT (No such file or directory)
  [pid 14422] access("MARK: nautilus nautilus_directory_emit_files_changed: 
start ", F_OK) = -1 ENOENT (No such file or directory)
  [pid 14422] access("MARK: nautilus nautilus_directory_emit_files_changed: end 
", F_OK) = -1 ENOENT (No such file or directory)
  [pid 14422] access("MARK: nautilus nautilus_directory_emit_change_signals: 
end ", F_OK) = -1 ENOENT (No such file or directory)

  This was created in 2006,
  http://people.gnome.org/~federico/news-2006-03.html#09 to aid
  debugging, however as access() is used for testing whether the object
  exists/can be read/written by the process, these calls actually hit
  the underlying filesystem.

  While local filesystems are pretty quick to answer with ENOENT, the
  remote filesystems, such as WebDAV over FUSE (with davfs2) will need
  to check with the server for these files every time. davfs2 caches the
  results, however if the remote filesystem was modified by copying a
  file there, nautilus will hang until davfs2 finishes uploading the
  file and is able to answer that access() call in case it was issued
  with the current working dir set to a directory on davfs mount.

  I think this method to gather performance information should be
  replaced with something that does not use access() so that filesystem
  is not touched at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu9
  ProcVersionSignature: Ubuntu 3.8.0-13.22-generic 3.8.3
  Uname: Linux 3.8.0-13-generic x86_64
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: amd64
  Date: Wed Mar 20 11:15:26 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+2+83'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2013-01-04 (74 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130104)
  MarkForUpload: True
  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/1157621/+subscriptions

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


[Desktop-packages] [Bug 1113649] Re: 'Extract here' right click option leaves out some files

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

Title:
  'Extract here' right click option leaves out some files

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  I just extracted the android-ndk-r8d and android-ndk-r8b using the
  'Extract here' option on my Linux Mint 14, cinnamon DE and it left out
  from extracting a few things.

  Only when I did a tar -jxf did everything get extracted.

  $ lsb_release -rd
  Description:  Linux Mint 14 Nadia
  Release:  14

  
  A person using nautilus also has the same problem. So, I thought it was worth 
adding a bug here. Sorry, if this is the wrong place.

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

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


[Desktop-packages] [Bug 1155997] Re: Network transferts crash with SW-IOMMU space messages

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

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

Title:
  Network transferts crash with SW-IOMMU space messages

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Hi,

  when transferring around more than 1Go of data using the ethernet controller 
(04:00.0 Ethernet controller: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet 
(rev c0)) with driver atl1c , my syslog gets full of messages "DMA: out of 
SW-IOMMU space for 4096 bytes at device 04:00.0" and my ethernet connection 
stops working.
  To reproduce this problem, I simply copy a few files from my internal SSD to 
my NAS.

  The byte size of the messages varies if I then try to access internet
  with my browser or any other network oriented application (smaller
  packets?)...

  sudo lspci -s 04:00.0 -vv
  04:00.0 Ethernet controller: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet 
(rev c0)
Subsystem: ASUSTeK Computer Inc. Device 1487
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status

  Regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu9
  ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
  Uname: Linux 3.8.0-12-generic x86_64
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: amd64
  Date: Sat Mar 16 17:40:32 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'1853x404+65+24'"
  InstallationDate: Installed on 2013-02-24 (19 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130224)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  XsessionErrors:
   (nautilus:1884): GnomeDesktop-WARNING **: Unable to create loader for mime 
type video/x-matroska: Format d'image non reconnu
   (nautilus:1884): GnomeDesktop-WARNING **: Error creating thumbnail for 
file:///media/typhoe/downloads/sabnzbd/complete/Anime_Series/Gankutsuou_h264_dual_audio/Gankutsuou_09_(h264)%5Bcc293c31%5D.mkv:
 Format d'image non reconnu

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

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


[Desktop-packages] [Bug 1097711] Re: Samsung Galaxy S+ opens two (of the same drive) windows when plugged in

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

Title:
  Samsung Galaxy S+ opens two (of the same drive) windows when plugged
  in

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 12.10
  Release:  12.10

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  nautilus:
Installed: 1:3.5.90.really.3.4.2-0ubuntu4.1
Candidate: 1:3.5.90.really.3.4.2-0ubuntu4.1
Version table:
   *** 1:3.5.90.really.3.4.2-0ubuntu4.1 0
  500 http://nl.archive.ubuntu.com/ubuntu/ quantal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.5.90.really.3.4.2-0ubuntu4 0
  500 http://nl.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages

  3) What you expected to happen
  I expected two windows to pop up - both showing different drives (the two 
drives of my 

  4) What happened instead
  Two windows popped up showing the same drive.

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

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


[Desktop-packages] [Bug 1812412] Re: package gnome-user-guide 3.8.2-1ubuntu0.1 failed to install/upgrade: unable to read link `./usr/share/help/pt_BR/gnome-help/mouse-middleclick.page': Input/output e

2019-01-18 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: gnome-user-docs (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-user-docs (Ubuntu)
   Status: New => Invalid

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

Title:
  package gnome-user-guide 3.8.2-1ubuntu0.1 failed to install/upgrade:
  unable to read link `./usr/share/help/pt_BR/gnome-help/mouse-
  middleclick.page': Input/output error

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

Bug description:
  no puedo actualizar

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gnome-user-guide 3.8.2-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-141.167~14.04.1-generic 4.4.162
  Uname: Linux 4.4.0-141-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  Date: Fri Jan 18 10:01:45 2019
  DuplicateSignature: package:gnome-user-guide:3.8.2-1ubuntu0.1:unable to read 
link `./usr/share/help/pt_BR/gnome-help/mouse-middleclick.page': Input/output 
error
  ErrorMessage: unable to read link 
`./usr/share/help/pt_BR/gnome-help/mouse-middleclick.page': Input/output error
  InstallationDate: Installed on 2019-01-17 (1 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.18
  SourcePackage: gnome-user-docs
  Title: package gnome-user-guide 3.8.2-1ubuntu0.1 failed to install/upgrade: 
unable to read link `./usr/share/help/pt_BR/gnome-help/mouse-middleclick.page': 
Input/output error
  UpgradeStatus: Upgraded to trusty on 2019-01-18 (0 days ago)

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

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


[Desktop-packages] [Bug 1812412] [NEW] package gnome-user-guide 3.8.2-1ubuntu0.1 failed to install/upgrade: unable to read link `./usr/share/help/pt_BR/gnome-help/mouse-middleclick.page': Input/output

2019-01-18 Thread Moises David Martinez Bautista
Public bug reported:

no puedo actualizar

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: gnome-user-guide 3.8.2-1ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-141.167~14.04.1-generic 4.4.162
Uname: Linux 4.4.0-141-generic i686
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: i386
Date: Fri Jan 18 10:01:45 2019
DuplicateSignature: package:gnome-user-guide:3.8.2-1ubuntu0.1:unable to read 
link `./usr/share/help/pt_BR/gnome-help/mouse-middleclick.page': Input/output 
error
ErrorMessage: unable to read link 
`./usr/share/help/pt_BR/gnome-help/mouse-middleclick.page': Input/output error
InstallationDate: Installed on 2019-01-17 (1 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.8
 apt  1.0.1ubuntu2.18
SourcePackage: gnome-user-docs
Title: package gnome-user-guide 3.8.2-1ubuntu0.1 failed to install/upgrade: 
unable to read link `./usr/share/help/pt_BR/gnome-help/mouse-middleclick.page': 
Input/output error
UpgradeStatus: Upgraded to trusty on 2019-01-18 (0 days ago)

** Affects: gnome-user-docs (Ubuntu)
 Importance: Low
 Status: Invalid


** Tags: apport-package hardware-error i386 need-duplicate-check trusty

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

Title:
  package gnome-user-guide 3.8.2-1ubuntu0.1 failed to install/upgrade:
  unable to read link `./usr/share/help/pt_BR/gnome-help/mouse-
  middleclick.page': Input/output error

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

Bug description:
  no puedo actualizar

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gnome-user-guide 3.8.2-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-141.167~14.04.1-generic 4.4.162
  Uname: Linux 4.4.0-141-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  Date: Fri Jan 18 10:01:45 2019
  DuplicateSignature: package:gnome-user-guide:3.8.2-1ubuntu0.1:unable to read 
link `./usr/share/help/pt_BR/gnome-help/mouse-middleclick.page': Input/output 
error
  ErrorMessage: unable to read link 
`./usr/share/help/pt_BR/gnome-help/mouse-middleclick.page': Input/output error
  InstallationDate: Installed on 2019-01-17 (1 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.18
  SourcePackage: gnome-user-docs
  Title: package gnome-user-guide 3.8.2-1ubuntu0.1 failed to install/upgrade: 
unable to read link `./usr/share/help/pt_BR/gnome-help/mouse-middleclick.page': 
Input/output error
  UpgradeStatus: Upgraded to trusty on 2019-01-18 (0 days ago)

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

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


[Desktop-packages] [Bug 1812101] Re: libreoffice-kde5 file dialog/picker doesn't add extension automatically

2019-01-18 Thread Bug Watch Updater
** Changed in: df-libreoffice
   Status: Incomplete => New

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

Title:
  libreoffice-kde5 file dialog/picker doesn't add extension
  automatically

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

Bug description:
  Description:
  libreoffice-kde5 file dialog doesn't add automatically the file extension 
which are important for.docx .xlsx, otherwise the system recognize them as zip.

  When removing that package and letting only libreoffice-gtk, extension
  are added automatically.

  Steps to Reproduce:
  1. if isn't installed install libreoffice-kde5 package
  2. save a writer document as .docx but doesn't add manually the extension

  Actual Results:
  file are saved without .docx extension.

  Expected Results:
  file should be saved with the .docx extension

  Additional Info:
  Using lubuntu 18.10
  Version: 6.1.4.2
  Build ID: 1:6.1.4-0ubuntu1
  CPU threads: 2; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5;
  Locale: es-CL (es_CL.UTF-8); Calc: group threaded

  I filed a bug against libreoffice to because I don't know who is
  responsible for libreoffice-kde5 package
  https://bugs.documentfoundation.org/show_bug.cgi?id=122752

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

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


[Desktop-packages] [Bug 1812101]

2019-01-18 Thread Olivier Tilloy
I installed 6.2.0.2 in an up-to-date lubuntu 18.10 VM as you suggested
Xisco. I can confirm that the issue Hans is reporting is still there:
the VCL is "kde5", the save dialog doesn't have an option to add the
file extension automatically, and files are saved without an extension
if not explicitly added.

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

Title:
  libreoffice-kde5 file dialog/picker doesn't add extension
  automatically

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

Bug description:
  Description:
  libreoffice-kde5 file dialog doesn't add automatically the file extension 
which are important for.docx .xlsx, otherwise the system recognize them as zip.

  When removing that package and letting only libreoffice-gtk, extension
  are added automatically.

  Steps to Reproduce:
  1. if isn't installed install libreoffice-kde5 package
  2. save a writer document as .docx but doesn't add manually the extension

  Actual Results:
  file are saved without .docx extension.

  Expected Results:
  file should be saved with the .docx extension

  Additional Info:
  Using lubuntu 18.10
  Version: 6.1.4.2
  Build ID: 1:6.1.4-0ubuntu1
  CPU threads: 2; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5;
  Locale: es-CL (es_CL.UTF-8); Calc: group threaded

  I filed a bug against libreoffice to because I don't know who is
  responsible for libreoffice-kde5 package
  https://bugs.documentfoundation.org/show_bug.cgi?id=122752

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

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


[Desktop-packages] [Bug 1123951] Re: Wrong French translation and no way to correct it.

2019-01-18 Thread Sebastien Bacher
The string has been removed in 3.30 which fixes the issue

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

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

Title:
  Wrong French translation and no way to correct it.

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

Bug description:
  When looking at the general setings of a *.desktop file, there is no space 
between some words in French and the ":".
  In the translation in Launchpad, only the word is available not the world 
with the ":".

  see a picture attach.

  1) 
  Ubuntu 12.10 64bits

  2)
  nautilus:
Installé : 1:3.5.90.really.3.4.2-0ubuntu4.1
Candidat : 1:3.5.90.really.3.4.2-0ubuntu4.1
Table de version :
   *** 1:3.5.90.really.3.4.2-0ubuntu4.1 0
  500 http://la.archive.ubuntu.com/ubuntu/ quantal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.5.90.really.3.4.2-0ubuntu4 0
  500 http://la.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages

  3)
  Description :
  Commande :
  Commentaire :

  [Launchpad]
  Description[nbsp]:
  Commande[nbsp]:
  Commentaire[nbsp]:
  [\Launchpad]

  4)
  Description:
  Commande:
  Commentaire:

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

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


[Desktop-packages] [Bug 987274] Re: Nautilus freezes after checking properties of PEF file

2019-01-18 Thread Sebastien Bacher
The file from comment #1 doesn't seem to freeze nautilus in recent
versions, closing

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

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

Title:
  Nautilus freezes after checking properties of PEF file

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 12.04

  I was trying to change default program to open PEF files. These are RAW 
format files for Pentax camera.
  Steps to reproduce:
  1. Right click PEF file
  2. Select “Properties”
  Nautilus freezes in this moment.

  Sample file attached.

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

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


[Desktop-packages] [Bug 1016640] Re: nautilus window toolbar shows white background with grey font

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

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

Title:
  nautilus window toolbar shows white background with grey font

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  A recent update to Ubuntu 12.04 LTS (6/21/12) caused a graphical error
  in nautilus and other windows to where the top window toolbar (file,
  edit, view...) is difficult to read as the font is grayed out with a
  white background.  I'm not sure if this is a bug or what and I'm not
  sure what package was affected to cause this.

  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
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
  Date: Fri Jun 22 11:31:45 2012
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: org.gnome.nautilus.window-state geometry '800x550+253+400'
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   PATH=(custom, no 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/1016640/+subscriptions

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


[Desktop-packages] [Bug 1094841] Re: Often when copying large file over cifs mounted network share nautilus freezes after a while

2019-01-18 Thread Sebastien Bacher
Could you try if that's still an issue in recent Ubuntu versions?

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

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

Title:
  Often when copying large file over cifs mounted network share nautilus
  freezes after a while

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I have a couple of network shares mounted in my system which are
  shared with samba. When I copy to/from it to my laptop, which have the
  share mounted in the file system with cifs, nautilus freezes and gets
  unresponsive, but most of the time only after a while, not
  immediately.

  When I access the mount by navigating to smb://share/ it never freezes
  though. Perhaps it's using a different file system driver? I've had
  this issue in 12.10, 12.04, 11.10 and 11.04. Before that I never had
  this setup.

  Ubuntu 12.10 x64
  nautilus 1:3.5.90.really.3.4.2-0ubuntu4

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

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


[Desktop-packages] [Bug 1068276] Re: does not respect Emacs-style gtk-key-theme

2019-01-18 Thread Sebastien Bacher
Ubuntu is not going to work on that, it should be reported upstream if
that's still an issue/something you care about

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  does not respect Emacs-style gtk-key-theme

Status in nautilus package in Ubuntu:
  Won't Fix

Bug description:
  I have set the gtk-key-theme setting to use Emacs-style key bindings
  using the following method:

  gsettings set org.gnome.desktop.interface gtk-key-theme "Emacs"

  (The setting is also visible through dconf-editor.)

  Some applications respect the setting (eg Firefox), but others do not.
  For example, the Nautilus location text entry (opened via Ctl-L) does
  not and Nautilus file-renamer text entry (select icon, hit F2) does
  not.

  For a specific instance of the problem, open a Nautilus window, press
  Ctl-L show the location text entry, type "abc" (overwriting the
  selected contents of the text entry), then press Ctl-A. With gtk-key-
  theme=Emacs, the correct behavior would be to place the cursor at the
  start of the text entry, before the "a". The current behavior in
  Nautilus is to select the entire contents of the text entry.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Thu Oct 18 14:17:31 2012
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'800x550+65+24'"
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
  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/1068276/+subscriptions

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


[Desktop-packages] [Bug 1095321] Re: Capital JPG extension not recognized as pictures

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

Title:
  Capital JPG extension not recognized as pictures

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  When accessing my photo's stored on my home directory e.g. when I want
  to upload them to the web, or an online photoalbum files with a JPG
  (all capitals) extension are not recognized as images. When I change
  the extension to jpg (no capitals) the very same files are recognized
  as images.

  The dialog box shows 'images' and I can't select the 'all files'
  option - this could perhaps also solve the problem. I have found a
  really old bug description that seems to report the exact same
  problem.

  https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/221409

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

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


[Desktop-packages] [Bug 1107286] Re: Unexpected behavior of Nautlius in two-panel mode when open mp3-player or camera.

2019-01-18 Thread Sebastien Bacher
The split mode has been removed which deprecates this issue

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

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

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

Title:
  Unexpected behavior of Nautlius in two-panel mode when open mp3-player
  or camera.

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Plug in camera/mp3/phone.
  2. Launch Nautilus, open ~.
  3. Press F3, you'll see two panels of equal widths.
  4. Open camera/mp3/phone folder by clicking on it leftward.
  5. See how Nautilus increased one panel and decreased another.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2
  Uname: Linux 3.5.0-22-generic i686
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: i386
  Date: Mon Jan 28 01:23:02 2013
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'835x343+401+272'"
  InstallationDate: Installed on 2013-01-25 (2 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  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/1107286/+subscriptions

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


[Desktop-packages] [Bug 881880] Re: Connecting/disconnecting external monitors changes colored background to black

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

Title:
  Connecting/disconnecting external monitors changes colored background
  to black

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  When I disconnect or connect an external monitor from my laptop, and
  have my background set to a solid color, the background color of my
  desktop changes to black.

  To reproduce:

  1) Open appearance settings dialog
  2) Change from "Wallpapers" to "Colors and Gradients"
  3) Choose a color
  4) Connect or disconnect an external monitor
  5) Observe screen change to black background

  This does *not* happen with a picture as the background (i.e. when
  choosing an image from the "Wallpaper" or "Pictures" selections).

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

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


[Desktop-packages] [Bug 688190] Re: Nautilus after a while slow to open home folder

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

Title:
  Nautilus after a while slow to open home folder

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: nautilus

  I installed maverick and when it starts and click to open home folder
  i have to wait like 1.2 seconds to open that is normal because its the
  first time that nautilus is started.

  after that first time, nautilus is fast to open home, documents or
  other folder, but times to times if i dont use nautilus, if i click in
  home folder for ex. i have to wait again like it was the first time to
  open.

  in lucid this never happened...

  it was fast all the time after the first time...

  regards...

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: nautilus 1:2.32.0-0ubuntu1.1
  ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7
  Uname: Linux 2.6.35-23-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Thu Dec  9 18:52:57 2010
  ExecutablePath: /usr/bin/nautilus
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   LANGUAGE=pt:pt_BR:en
   LANG=pt_PT.utf8
   SHELL=/bin/bash
  SourcePackage: nautilus

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

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


[Desktop-packages] [Bug 1095869] Re: Folders on desktop are opened with Nautilus although my default file browser is Thunar

2019-01-18 Thread Sebastien Bacher
indeed, as the previous comment stated it that's not a bug, the desktop
is a nautilus view

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

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

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

Title:
  Folders on desktop are opened with Nautilus although my default file
  browser is Thunar

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  I use Thunar as my default file browser (folders opened from apps are
  opened with it) but when I double click on a folder on the Gnome
  desktop, it opens with Nautilus.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
  Uname: Linux 3.5.0-21-generic i686
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: i386
  Date: Fri Jan  4 00:37:41 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+0+55'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
   b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true'
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=fr_FR:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to quantal on 2012-10-25 (70 days ago)

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

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


[Desktop-packages] [Bug 1093759] Re: transfer permissions to contained folders does nothing

2019-01-18 Thread Sebastien Bacher
There has been no activity here or mention of similar issues in years
and it's likely resolved, closing but feel free to open a new report if
you still have problems in newer versions


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

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

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

Title:
  transfer permissions to contained folders does nothing

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  I ran nautilus as root (gksudo) in order to copy another user's .gconf
  folder, which then got the ownership of root. In properties of the
  .gconf folder, I corrected the permissions and clicked the button to
  transfer them to all contained files/folders. There was no indication
  that the process takes time, and the ownership of the contained
  files/folders was not changed.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
  Uname: Linux 3.5.0-21-generic i686
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: i386
  Date: Wed Dec 26 09:51:42 2012
  GsettingsChanges:
   
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.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/1093759/+subscriptions

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


  1   2   3   >