date:20180317

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

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

** Changed in: i3-wm (Ubuntu)
   Status: New => Confirmed

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

Title:
  desktop contents briefly visible on resume from suspend before lock
  dialog

Status in Compiz:
  New
Status in unity-2d:
  Confirmed
Status in gnome-screensaver package in Ubuntu:
  Incomplete
Status in i3-wm package in Ubuntu:
  Confirmed
Status in unity-2d package in Ubuntu:
  Confirmed

Bug description:
  This seems like a recent regression on Oneiric (or perhaps I haven't
  noticed it before):

  On resume from suspend, the contents of the desktop are often briefly
  visible before being hidden behind the lock screen.  This is a
  security problem if there happens to be sensitive information on the
  screen.


  =Analysis from mdeslaur=
  This is likely what happens:

  1- Something grabs mouse: ie: virtual machine window, or GTK menu in an 
application or an indicator
  2- Screensaver attempts to start, but cannot get exclusive lock on mouse
  3- DPMS turns monitor black
  4- User moves mouse, which turns the screen back on
  5- Mouse movement causes mouse to get ungrabbed by vm window or gtk menu
  6- Screensaver can now grab mouse, and starts

  This is all related to the fact that X does not have an API that will
  let the screensaver tell an application to release mouse and keyboard
  grabs.

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

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

[Desktop-packages] [Bug 1540110] Re: gnome-disk-utility (shown as "Disks") shows SMART option grayed for USB connect disks despite being available.

2018-03-17 Thread Rüdiger Kupper

I have several disks connected via USB. Most of them work with gnome-
disks' SMART interface. But for one of them, I get "operation not
permitted". smartctl in the terminal works fine for that disk.


** Also affects: gnome-disk-utility via
   https://bugzilla.gnome.org/show_bug.cgi?id=757784
   Importance: Unknown
   Status: Unknown

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

Title:
  gnome-disk-utility (shown as "Disks") shows SMART option grayed for
  USB connect disks despite being available.

Status in GNOME Disks:
  Unknown
Status in gnome-disk-utility package in Ubuntu:
  Confirmed

Bug description:
  gnome-disk-utility (show as "Disks" on the desktop environment running
  Unity) systematically does not acknowledge that disks have SMART
  capabilities when connected through a USB port; SMART capabilities are
  grayed. However, 'sudo smartctl -a /dev/' works fine confirming
  that there is no problem reading SMART data through a USB link. gnome-
  disk-utility acknowledge SMART capabilities if the same disk is
  connected through a SATA port.

  Confirmed for Ubuntu 14.04 LTS Trusty Tahr on 2016-01-26, gnome-disk-
  utility 3.10.0, udisks 2.1.3 (built against 2.1.3) by Hans Deragon.

  This bug is the same as bug #1092900 which was reported against Ubuntu
  10.04 LTS Lucid Lynx.  Following user dino99 suggestion, I opened this
  new bug report to follow the same problem on Ubuntu 14.04 LTS Trusty
  Tahr.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-disk-utility 3.10.0-1ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-76.120-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-76-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan 31 11:30:03 2016
  InstallationDate: Installed on 2014-11-01 (456 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2018-03-17 Thread Andrey Arapov

The same issue :-/

Ubuntu 16.04.4 LTS

network-manager-openvpn 1.1.93-1ubuntu1.1
network-manager-openvpn-gnome 1.1.93-1ubuntu1.1

I am usually setting:
VPN connection settings -> IPv4 Settings -> Routes... -> [x] Use this
connection only for resources on its network.

So that my default GW is not changed as I need only the VPN routes.
Except that with this bug, the VPN routes are not really applied on my system.

When running openvpn on its own, everything is working.

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

Title:
NetworkManager ignores pushed openvpn routes

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

Bug description:
Relevant information that may or may not have been included by ubuntu-
bug:

Ubuntu release 16.04
Package network-manager 1.2.0-0ubuntu0.16.04.2
Package network-manager-openvpn 1.1.93-1ubuntu1

NetworkManager ignores pushed openvpn routes when "Use this connection
only for resources on its network" is checked. This is a behavior
change since 14.04.

To repeat:

1) Use an OpenVpn server that pushes routes. I suggest using a server
that pushes several routes since this makes their absence obvious.
Set up a NetworkManager VPN of type OpenVpn to this server. Select
"Use this connection only for resources on its network" in the
"Routes" section of the IPV4 options.

2) Set up a raw OpenVpn connection to the same server.

3) Connect to the server using the raw OpenVpn connection. The pushed
routes are all there.

4) Connect to the server using NetworkManager. The only route added
is a n interface level route to the tunnel device network.

Using the same setup on 14.04, all pushed routes are added.

The missing routes are also "Resources on the VPN network", and should be
added in the absence of further direction. Ignoring pushed routes should be
controlled by the "Ignore automatically obtained routes" checkbox.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager-openvpn 1.1.93-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Fri Jul 15 23:12:55 2016
InstallationDate: Installed on 2016-05-04 (72 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: network-manager-openvpn
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1753776] Re: Graphics corruption just before login animation to Xorg sessions (Intel gen9 GPUs only)

Doing some testing:

- first modifying options into /etc/gdm3/custom.conf 
   set [daemon] WaylandEnable=false to force xorg login :
 my feeling is that should be the default now as ubuntu as made that choice for 
the release (and wayland / apps still does not well together in many cases)

- then rebboting

And now the problem existing with my hardware and reported here is gone: no 
distorted screen.
That system is using the 'proposed' archive and is fully updated.
What is also different now: the login options (gear button) have dropped the 
wayland ones.

So my conclusion are:
- /etc/gdm3/custom.conf  should use xorg, not wayland
- the issue reported gere seems have been introduced by the wayland (1.14.0-2) 
changes (patch)

*
wayland (1.14.0-2) unstable; urgency=medium

  * debian/patches/CVE-2017-16612.patch: (Closes: #889681)
- libXcursor before 1.1.15 has various integer overflows that could lead
  to heap buffer overflows when processing malicious cursors, e.g., with
  programs like GIMP. It is also possible that an attack vector exists
  against the related code in cursor/xcursor.c in Wayland through
  1.14.0.
  * switch back to use upstream tarball
  * debian/control: bump standards version, drop priority stanzas

 -- Héctor Orón Martínez   Sun, 04 Mar 2018 11:56:31 +0100
***

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-16612

** Package changed: mutter (Ubuntu) => gdm3 (Ubuntu)

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

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

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

** Changed in: wayland (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

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

Title:
  Graphics corruption just before login animation to Xorg sessions
  (Intel gen9 GPUs only)

Status in X.Org X server:
  Confirmed
Status in gdm3 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in wayland package in Ubuntu:
  New

Bug description:
  Immediately after login (I enter the password and hit enter) the screen 
"crumbles" for few seconds, then all becomes normal and the system works fine. 
I have done apt update+upgrade many times, also with proposed enabled, I have 
also installed a new ISO (now i'm using the Alpha dated 20180305) but the 
problem remains. The problem happens with the x11 session but not with wayland. 
  Also problem does not show with different hardware. 

  corrado@corrado-p7-bb-0305:~$ inxi -Fx
  System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 
gcc: 7.3.0
 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu 
Bionic Beaver (development branch)
  Machine:   Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: 
American Megatrends v: P1.10 date: 05/11/2017
  CPU:   Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 
3072 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 
3081 MHz
  Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0
 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 
1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
 version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes
  Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 
00:1f.3
 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic
  Network:   Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 
3.2.6-k bus-ID: 00:1f.6
 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86
  Drives:HDD Total Size: 1000.2GB (1.3% used)
 ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB
  Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7
 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 38.5C mobo: N/A
 Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: 
systemd runlevel: 5 Gcc sys: N/A
 Client: Shell (bash 4.4.181) inxi: 2.3.56 
  corrado@corrado-p7-bb-0305:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  6 15:47:50 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  Distro

[Desktop-packages] [Bug 1756201] [NEW] xsane not aquiring images from Lide 30

You have been subscribed to a public bug:

Ubuntu 17.10, xsane 0.999


During the "searching for devices" phase I can hear the "usual" tick from the 
scanner.

When I try to scan the error "Failed to start scanner: Error during
device I/O" occurs.

I can dual-boot my machine into Ubuntu 14.04 LTS with xsane 0.998.
There it works perfectly (same computer, same port, same cable).

I don't see any messages on the console or in /var/log/messages.

I've tried running it as root - same problem.

Any hints?

Thanks

Mike


$ uname -a
Linux quadro 4.13.0-37-generic #42-Ubuntu SMP Wed Mar 7 14:13:23 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux


$ lsusb
...
Bus 001 Device 003: ID 04a9:220e Canon, Inc. CanoScan N1240U/LiDE 30

$ sane-find-scanner 
...
found USB scanner (vendor=0x04a9 [Canon], product=0x220e [CanoScan], 
chip=LM9830) at libusb:001:003

$ scanimage -L
device `plustek:libusb:001:003' is a Canon CanoScan N1240U/LiDE30 flatbed 
scanner

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New

-- 
xsane not aquiring images from Lide 30
https://bugs.launchpad.net/bugs/1756201
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to sane-backends in Ubuntu.

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

[Desktop-packages] [Bug 1756522] [NEW] Cannot use session '/usr/share/gdm/greeter/gnome-session/sessions/gnome-login.session': non-existing or invalid file.

Public bug reported:

Found this logged after enabling debug into/etc/gdm3/custom.conf

gnome-session-binary[1073]: DEBUG(+): Cannot use session
'/usr/share/gdm/greeter/gnome-session/sessions/gnome-login.session':
non-existing or invalid file.

oem@ubuntu:~$ ls -l /usr/share/gdm/greeter/
total 8
drwxr-xr-x 2 root root 4096 Mar  9 13:38 applications
drwxr-xr-x 2 root root 4096 Mar 10 10:45 autostart

... the required path is indeed not found; but its not the only one:

/usr/lib/gdm3/gdm-x-session[1062]: gnome-session-binary[1073]: DEBUG(+):
Cannot use session '/var/lib/gdm3/.config/gnome-session/sessions/gnome-
login.session': non-existing or invalid file.

oem@ubuntu:~$ ls -l /var/lib/gdm3/.config/gnome-session/
total 4
drwxr-xr-x 2 gdm gdm 4096 Dec  2 10:17 saved-session

... the required path is indeed not found again


ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-session-bin 3.27.91-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Mar 17 11:26:05 2018
EcryptfsInUse: Yes
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
   Cannot use session '/usr/share/gdm/greeter/gnome-session/sessions
  /gnome-login.session': non-existing or invalid file.

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Found this logged after enabling debug into/etc/gdm3/custom.conf

  gnome-session-binary[1073]: DEBUG(+): Cannot use session
  '/usr/share/gdm/greeter/gnome-session/sessions/gnome-login.session':
  non-existing or invalid file.

  oem@ubuntu:~$ ls -l /usr/share/gdm/greeter/
  total 8
  drwxr-xr-x 2 root root 4096 Mar  9 13:38 applications
  drwxr-xr-x 2 root root 4096 Mar 10 10:45 autostart

  ... the required path is indeed not found; but its not the only one:

  /usr/lib/gdm3/gdm-x-session[1062]: gnome-session-binary[1073]:
  DEBUG(+): Cannot use session '/var/lib/gdm3/.config/gnome-
  session/sessions/gnome-login.session': non-existing or invalid file.

  oem@ubuntu:~$ ls -l /var/lib/gdm3/.config/gnome-session/
  total 4
  drwxr-xr-x 2 gdm gdm 4096 Dec  2 10:17 saved-session

  ... the required path is indeed not found again


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session-bin 3.27.91-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Mar 17 11:26:05 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1756201] Re: xsane not aquiring images from Lide 30

2018-03-17 Thread mistr

I got xsane running by copying the content of /usr/lib/x86_64-linux-
gnu/sane from the old Ubuntu 14.04 (64 bit) installation to the same
location in my Ubuntu 17.10 (64 bit) install.

According to

  sane-config --version

the "old" libraries are from the release 1.0.23. (And the naming of the
files also suggests that.)

I then tried to compile sane from source according to
https://help.ubuntu.com/community/CompileSaneFromSource in the hope to
bisect the commit where this change happend:

sudo apt-get install libusb-dev build-essential libsane-dev
sudo apt-get install libavahi-client-dev libavahi-glib-dev

git clone git://git.debian.org/sane/sane-backends.git

./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu --sysconfdir=/etc 
--localstatedir=/var  --enable-avahi
make
sudo make install

After each install I rebooted the machine in order to flush any cached
libraries from memory.

This first attempt did not work. (Same error as described above).

I then tried the various newer releases and one older one (1.0.22):

git checkout RELEASE_1_0_xx

configure, make, make install, reboot, test.

However, all of those fail.

The only version that works every time is the one I've copied from
Ubuntu 14.04.

At this point I don't know how to proceed.

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

Title:
  xsane not aquiring images from Lide 30

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10, xsane 0.999

  
  During the "searching for devices" phase I can hear the "usual" tick from the 
scanner.

  When I try to scan the error "Failed to start scanner: Error during
  device I/O" occurs.

  I can dual-boot my machine into Ubuntu 14.04 LTS with xsane 0.998.
  There it works perfectly (same computer, same port, same cable).

  I don't see any messages on the console or in /var/log/messages.

  I've tried running it as root - same problem.

  Any hints?

  Thanks

  Mike

  
  $ uname -a
  Linux quadro 4.13.0-37-generic #42-Ubuntu SMP Wed Mar 7 14:13:23 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  
  $ lsusb
  ...
  Bus 001 Device 003: ID 04a9:220e Canon, Inc. CanoScan N1240U/LiDE 30

  $ sane-find-scanner 
  ...
  found USB scanner (vendor=0x04a9 [Canon], product=0x220e [CanoScan], 
chip=LM9830) at libusb:001:003

  $ scanimage -L
  device `plustek:libusb:001:003' is a Canon CanoScan N1240U/LiDE30 flatbed 
scanner

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

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

[Desktop-packages] [Bug 1756201] Re: xsane not aquiring images from Lide 30

2018-03-17 Thread mistr

see 2nd entry

** Package changed: xsane (Ubuntu) => sane-backends (Ubuntu)

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

Title:
  xsane not aquiring images from Lide 30

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10, xsane 0.999

  
  During the "searching for devices" phase I can hear the "usual" tick from the 
scanner.

  When I try to scan the error "Failed to start scanner: Error during
  device I/O" occurs.

  I can dual-boot my machine into Ubuntu 14.04 LTS with xsane 0.998.
  There it works perfectly (same computer, same port, same cable).

  I don't see any messages on the console or in /var/log/messages.

  I've tried running it as root - same problem.

  Any hints?

  Thanks

  Mike

  
  $ uname -a
  Linux quadro 4.13.0-37-generic #42-Ubuntu SMP Wed Mar 7 14:13:23 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  
  $ lsusb
  ...
  Bus 001 Device 003: ID 04a9:220e Canon, Inc. CanoScan N1240U/LiDE 30

  $ sane-find-scanner 
  ...
  found USB scanner (vendor=0x04a9 [Canon], product=0x220e [CanoScan], 
chip=LM9830) at libusb:001:003

  $ scanimage -L
  device `plustek:libusb:001:003' is a Canon CanoScan N1240U/LiDE30 flatbed 
scanner

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

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

[Desktop-packages] [Bug 1756522] Re: Cannot use session '/usr/share/gdm/greeter/gnome-session/sessions/gnome-login.session': non-existing or invalid file.

** Description changed:

  Found this logged after enabling debug into/etc/gdm3/custom.conf
  
  gnome-session-binary[1073]: DEBUG(+): Cannot use session
  '/usr/share/gdm/greeter/gnome-session/sessions/gnome-login.session':
  non-existing or invalid file.
  
  oem@ubuntu:~$ ls -l /usr/share/gdm/greeter/
  total 8
  drwxr-xr-x 2 root root 4096 Mar  9 13:38 applications
  drwxr-xr-x 2 root root 4096 Mar 10 10:45 autostart
  
- ... the required path is indeed not found
+ ... the required path is indeed not found; but its not the only one:
+ 
+ /usr/lib/gdm3/gdm-x-session[1062]: gnome-session-binary[1073]: DEBUG(+):
+ Cannot use session '/var/lib/gdm3/.config/gnome-session/sessions/gnome-
+ login.session': non-existing or invalid file.
+ 
+ oem@ubuntu:~$ ls -l /var/lib/gdm3/.config/gnome-session/
+ total 4
+ drwxr-xr-x 2 gdm gdm 4096 Dec  2 10:17 saved-session
+ 
+ ... the required path is indeed not found again
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session-bin 3.27.91-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Mar 17 11:26:05 2018
  EcryptfsInUse: Yes
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
   Cannot use session '/usr/share/gdm/greeter/gnome-session/sessions
  /gnome-login.session': non-existing or invalid file.

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Found this logged after enabling debug into/etc/gdm3/custom.conf

  gnome-session-binary[1073]: DEBUG(+): Cannot use session
  '/usr/share/gdm/greeter/gnome-session/sessions/gnome-login.session':
  non-existing or invalid file.

  oem@ubuntu:~$ ls -l /usr/share/gdm/greeter/
  total 8
  drwxr-xr-x 2 root root 4096 Mar  9 13:38 applications
  drwxr-xr-x 2 root root 4096 Mar 10 10:45 autostart

  ... the required path is indeed not found; but its not the only one:

  /usr/lib/gdm3/gdm-x-session[1062]: gnome-session-binary[1073]:
  DEBUG(+): Cannot use session '/var/lib/gdm3/.config/gnome-
  session/sessions/gnome-login.session': non-existing or invalid file.

  oem@ubuntu:~$ ls -l /var/lib/gdm3/.config/gnome-session/
  total 4
  drwxr-xr-x 2 gdm gdm 4096 Dec  2 10:17 saved-session

  ... the required path is indeed not found again


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session-bin 3.27.91-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Mar 17 11:26:05 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1756379] Re: Delay start of gnome-software service

2018-03-17 Thread Jean-Baptiste Lallement

A rotational hard drive

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

Title:
  Delay start of gnome-software service

Status in gnome-software package in Ubuntu:
  New

Bug description:
  On a default Bionic Desktop installation, gnome-software starts early and 
slows down session startup. In the bootchart attached, it overlaps with 
gnome-shell startup which is also resource intensive.
  With gnome-software delayed gnome-shell starts 2 seconds faster.

  
  gnome-software service startup should be delayed if it cannot be stop 
completely.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 17:11:41 2018
  InstallationDate: Installed on 2013-09-03 (1654 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.28.0-0ubuntu3
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu3
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago)

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

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

[Desktop-packages] [Bug 1756501] Re: Ubuntu Firefox Desktop icon is HUGE (about 5 times normal) after update to 59.0 (64-bit) Ubuntu canonical build, can't resize by any normal method.

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

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

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

Title:
  Ubuntu Firefox Desktop icon is HUGE (about 5 times normal) after
  update to 59.0 (64-bit) Ubuntu canonical build, can't resize by any
  normal method.

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Last Firefox Automatic update (I presume to v59.0) occurred.  In any
  case, the last automatic update about 3/16/18

  Firefox seems to operate correctly other than the below :

  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  firefox:
    Installed: 59.0+build5-0ubuntu0.16.04.1
    Candidate: 59.0+build5-0ubuntu0.16.04.1
    Version table:
   *** 59.0+build5-0ubuntu0.16.04.1 500
  500 http://mirror.picosecond.org/ubuntu xenial-updates/main amd64 
Packages
  500 http://mirror.picosecond.org/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   45.0.2+build1-0ubuntu1 500
  500 http://mirror.picosecond.org/ubuntu xenial/main amd64 Packages

  Icon should match size of other icons, or be adjustable by normal
  methods.

  Ubuntu Firefox Desktop icon is HUGE (about 5 times normal) after
  update to 59.0 (64-bit) Ubuntu canonical build, can't resize by any
  normal method.  See screenshot below.

  This happens in Gnome Flashback Metacity, Cinnamon, and regular Ubuntu
  desktops.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 59.0+build5-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  roger  2122 F pulseaudio
   /dev/snd/controlC1:  roger  2122 F pulseaudio
  BuildID: 20180313132747
  Channel: Unavailable
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Mar 16 21:45:26 2018
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePlugins: Shockwave Flash - 
/usr/lib/flashplugin-installer/libflashplayer.so
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-07 (1348 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 100
   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.2  metric 
100
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.
  MostRecentCrashID: bp-8429ff8e-b8cf-43ac-b316-8b5d52170318
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 - LastVersion=50.0.2/20161130094553 (Out of date)
   Profile1 - LastVersion=50.0.2/20161130094553 (Out of date)
   Profile2 (Default) - LastVersion=59.0/20180313132747 (In use)
  RelatedPackageVersions: djview-plugin 4.10.5-1
  RfKill:

  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-8429ff8e-b8cf-43ac-b316-8b5d52170318
   bp-2a006e91-1f1e-45c9-abb9-ff7082161221
   bp-29d76630-2325-4501-a14e-f72fe2161125
  UpgradeStatus: Upgraded to xenial on 2016-12-18 (454 days ago)
  dmi.bios.date: 02/08/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904
  dmi.board.name: DZ77BH-55K
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG39008-400
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:

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

[Desktop-packages] [Bug 1756525] Re: gnome-shell crashed with signal 5

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1756525/+attachment/5082095/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1756525/+attachment/5082097/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1756525/+attachment/5082100/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1756525/+attachment/5082101/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1756525/+attachment/5082102/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1756525/+attachment/5082103/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1756525/+attachment/5082104/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Fresh install of Bionic daily build, updated fully and restarted, then
  this error popped up before I did or clicked anything. I can't see any
  issues with usability, just this error.

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

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Mar 17 12:42:05 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1756526] [NEW] _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed

Public bug reported:

Gnome-shell session on xorg, with no opened apps

Getting this logged:

oem@ubuntu:~$ journalctl -b | grep XSERV
/usr/lib/gdm3/gdm-x-session[1289]: _XSERVTransSocketUNIXCreateListener: 
...SocketCreateListener() failed
/usr/lib/gdm3/gdm-x-session[1289]: _XSERVTransMakeAllCOTSServerListeners: 
server already running

per https://www.x.org/wiki/FAQErrorMessages/

i join the listening.txt output

and there is no XO-lock file on the system, which seems abnormal.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xserver-xorg-core 2:1.19.6-1ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Mar 17 12:10:02 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: r8168, 8.045.08, 4.15.0-12-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: ASRock Incorporation HD Graphics 530 [1849:1912]
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/07/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P7.00
dmi.board.name: B150M-HDV
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Feb 28 14:50:36 2018
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu2

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


** Tags: amd64 apport-bug bionic package-from-proposed reproducible ubuntu

** Attachment added: "listening.txt"
   
https://bugs.launchpad.net/bugs/1756526/+attachment/5082106/+files/listening.txt

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

Title:
  _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Gnome-shell session on xorg, with no opened apps

  Getting this logged:

  oem@ubuntu:~$ journalctl -b | grep XSERV
  /usr/lib/gdm3/gdm-x-session[1289]: _XSERVTransSocketUNIXCreateListener: 
...SocketCreateListener() failed
  /usr/lib/gdm3/gdm-x-session[1289]: _XSERVTransMakeAllCOTSServerListeners: 
server already running

  per https://www.x.org/wiki/FAQErrorMessages/

  i join the listening.txt output

  and there is no XO-lock file on the system, which seems abnormal.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Mar 17 12:10:02 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: r8168, 8.045.08, 4.15.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 530 [1849:1912]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Fou

[Desktop-packages] [Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load

2018-03-17 Thread Péter Prőhle

Today I had again a possibility to check the issue.

Tell me please, that what kind of information, what command outputs
should I attach, when I face myself to the issue in question?

Output of "dmesg | grep -i gsd" is empty.

Outout of "journalctl | grep -i gsd" has no new items in the last 4
days.

However I found interesting lines in journalctl, hence I try to add the
result of "journalctl | grep -i key | grep -i failed >
journalctl_key_failed.txt" as an attachment.

** Attachment added: "journalctl | grep -i key | grep -i failed > 
journalctl_key_failed.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1755106/+attachment/5082123/+files/journalctl_key_failed.txt

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

Title:
  /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
  fails to load

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  $ dconf dump /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
  [custom1]
  binding='BackSpace'
  command='gnome-session-quit --power-off'
  name='gnome-session-quit --power-off'

  [custom0]
  binding='g'
  command='gnome-terminal --geometry=80x99-0+0'
  name='gnome-terminal --geometry=80x99-0+0'
  $

  In spite of the above, time to time, not always, but since 18.04 much
  much more frequently this settings fails to become active just after
  booting, ... my account is logged in automatically just after boot.

  If I log out and log in again, then these key bindings work.

  If I go to the system settings, and define again, then these work
  again.

  Earlier, before 18.04 this phenomenon was rare, namely once a week at
  most.

  But since 18.04 it is almost guaranteed, not deterministic, but highly
  probable, that after an initial boot or a warm reboot these key
  bindings will not work.

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

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

[Desktop-packages] [Bug 1656071] [NEW] spacebar preview doesn't work in default Ubuntu

You have been subscribed to a public bug:

https://help.ubuntu.com/stable/ubuntu-help/files-preview.html

Supposedly, a preview should happen when you press space in nautilus
with a file highlighted.

Instead, nothing happens.

Workaround: install gnome-sushi

** Affects: gnome-user-docs
 Importance: Medium
 Status: Fix Released

** Affects: gnome-user-docs (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: 16.10 nautilus preview
-- 
spacebar preview doesn't work in default Ubuntu
https://bugs.launchpad.net/bugs/1656071
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-user-docs in Ubuntu.

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

[Desktop-packages] [Bug 1756532] Re: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1754924, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1756532/+attachment/5082176/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1756532/+attachment/5082178/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1756532/+attachment/5082181/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1756532/+attachment/5082182/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1756532/+attachment/5082183/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1756532/+attachment/5082184/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1756532/+attachment/5082185/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1754924
   gnome-control-center crashed with SIGSEGV in actualize_printers_list()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Sitting idle when crash occurred.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.27.92-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 17 06:21:51 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-03-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x55e7e3a1c5f1:mov0x90(%rbp),%rsi
   PC (0x55e7e3a1c5f1) ok
   source "0x90(%rbp)" (0x0090) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1756531] Re: gnome-control-center crashed with SIGSEGV

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1754954, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1756531/+attachment/5082166/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1756531/+attachment/5082168/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1756531/+attachment/5082171/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1756531/+attachment/5082172/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1756531/+attachment/5082173/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1756531/+attachment/5082174/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1756531/+attachment/5082175/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1754954

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-control-center crashed with SIGSEGV

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  When I am using gnome-control-center on Ubuntu 18.04, it crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.27.92-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 17 19:37:00 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-03-15 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180314)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   LANGUAGE=zh_TW:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_TW.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fa93d3e3a1d:mov0x8(%rdi),%eax
   PC (0x7fa93d3e3a1d) ok
   source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1656071] Re: spacebar preview doesn't work in default Ubuntu

2018-03-17 Thread Gunnar Hjalmarsson

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

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

Title:
  spacebar preview doesn't work in default Ubuntu

Status in Gnome Documentation:
  Fix Released
Status in gnome-user-docs package in Ubuntu:
  Confirmed

Bug description:
  https://help.ubuntu.com/stable/ubuntu-help/files-preview.html

  Supposedly, a preview should happen when you press space in nautilus
  with a file highlighted.

  Instead, nothing happens.

  Workaround: install gnome-sushi

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-user-docs/+bug/1656071/+subscriptions

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

[Desktop-packages] [Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load

2018-03-17 Thread Péter Prőhle

[continuing the previous comment]

The the output of "ps acuwx | fgrep gsd" is still empty. Should I see
any process containing the substring "gsd"?

Is it possible, that my issue has some connection with the followin
issue: https://bugs.launchpad.net/bugs/1750846

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

Title:
  /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
  fails to load

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  $ dconf dump /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
  [custom1]
  binding='BackSpace'
  command='gnome-session-quit --power-off'
  name='gnome-session-quit --power-off'

  [custom0]
  binding='g'
  command='gnome-terminal --geometry=80x99-0+0'
  name='gnome-terminal --geometry=80x99-0+0'
  $

  In spite of the above, time to time, not always, but since 18.04 much
  much more frequently this settings fails to become active just after
  booting, ... my account is logged in automatically just after boot.

  If I log out and log in again, then these key bindings work.

  If I go to the system settings, and define again, then these work
  again.

  Earlier, before 18.04 this phenomenon was rare, namely once a week at
  most.

  But since 18.04 it is almost guaranteed, not deterministic, but highly
  probable, that after an initial boot or a warm reboot these key
  bindings will not work.

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

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

[Desktop-packages] [Bug 1750846] Re: several g-s-d services are timing out when booting a live session

2018-03-17 Thread Péter Prőhle

Is it possible, that my issue https://bugs.launchpad.net/bugs/1755106
has some connection with this issue, see the journalctl | grep -i key |
grep -i failed > journalctl_key_failed.txt attachment there:

https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1755106/+attachment/5082123/+files/journalctl_key_failed.txt

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

Title:
  several g-s-d services are timing out when booting a live session

Status in gnome-settings-daemon package in Ubuntu:
  New
Status in gnome-settings-daemon source package in Bionic:
  New

Bug description:
  The following g-s-d services are timing out when booting a live
  session:

  gsd-media-keys
  gsd-color
  gsd-wacom
  gsd-power

  One impact at least is that the shortcut to launch a terminal doesn't
  work

  From the journal:
  [   82.368253] ubuntu gsd-media-keys[1865]: Failed to grab accelerators: 
Timeout was reached (24)
  [  108.828263] ubuntu gsd-color[1863]: failed to get screens: Timeout was 
reached
  [  108.836334] ubuntu gsd-wacom[1836]: Failed to construct RR screen: Timeout 
was reached
  [  108.837764] ubuntu gsd-power[1823]: Could not create GnomeRRScreen: 
Timeout was reached

  [  245.337228] ubuntu gsd-media-keys[1865]: Could not find accelerator for 
accel id 175
  ^_ this last line is displayed when Ctrl+Alt+T is pressed to open a terminal

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 21 15:20:00 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180221)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1756501] Re: Ubuntu Firefox Desktop icon is HUGE (about 5 times normal) after update to 59.0 (64-bit) Ubuntu canonical build, can't resize by any normal method.

2018-03-17 Thread Jeremy Bicha

** Description changed:

  Last Firefox Automatic update (I presume to v59.0) occurred.  In any
  case, the last automatic update about 3/16/18
  
  Firefox seems to operate correctly other than the below :
  
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04
  
  firefox:
    Installed: 59.0+build5-0ubuntu0.16.04.1
    Candidate: 59.0+build5-0ubuntu0.16.04.1
    Version table:
   *** 59.0+build5-0ubuntu0.16.04.1 500
  500 http://mirror.picosecond.org/ubuntu xenial-updates/main amd64 
Packages
  500 http://mirror.picosecond.org/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   45.0.2+build1-0ubuntu1 500
  500 http://mirror.picosecond.org/ubuntu xenial/main amd64 Packages
  
  Icon should match size of other icons, or be adjustable by normal
  methods.
  
  Ubuntu Firefox Desktop icon is HUGE (about 5 times normal) after update
  to 59.0 (64-bit) Ubuntu canonical build, can't resize by any normal
  method.  See screenshot below.
  
- This happens in Gnome Flashback Metacity, Cinnamon, and regular Ubuntu
- desktops.
+ This happens in Gnome Flashback Metacity, Cinnamon, and Unity
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 59.0+build5-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  roger  2122 F pulseaudio
   /dev/snd/controlC1:  roger  2122 F pulseaudio
  BuildID: 20180313132747
  Channel: Unavailable
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Mar 16 21:45:26 2018
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePlugins: Shockwave Flash - 
/usr/lib/flashplugin-installer/libflashplayer.so
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-07 (1348 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 100
   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.2  metric 
100
  IwConfig:
   lono wireless extensions.
  
   eth0  no wireless extensions.
  MostRecentCrashID: bp-8429ff8e-b8cf-43ac-b316-8b5d52170318
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 - LastVersion=50.0.2/20161130094553 (Out of date)
   Profile1 - LastVersion=50.0.2/20161130094553 (Out of date)
   Profile2 (Default) - LastVersion=59.0/20180313132747 (In use)
  RelatedPackageVersions: djview-plugin 4.10.5-1
  RfKill:
  
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-8429ff8e-b8cf-43ac-b316-8b5d52170318
   bp-2a006e91-1f1e-45c9-abb9-ff7082161221
   bp-29d76630-2325-4501-a14e-f72fe2161125
  UpgradeStatus: Upgraded to xenial on 2016-12-18 (454 days ago)
  dmi.bios.date: 02/08/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904
  dmi.board.name: DZ77BH-55K
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG39008-400
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:

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

Title:
  Ubuntu Firefox Desktop icon is HUGE (about 5 times normal) after
  update to 59.0 (64-bit) Ubuntu canonical build, can't resize by any
  normal method.

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Last Firefox Automatic update (I presume to v59.0) occurred.  In any
  case, the last automatic update about

[Desktop-packages] [Bug 1754833] Re: Chromium complains that it's not the default browser when it is the default according to Gnome Settings

2018-03-17 Thread Ken T

It looks highly likely (to my less-than-expert-eye anyway) that the bug
you've linked to is the same issue...

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

Title:
  Chromium complains that it's not the default browser when it is the
  default according to Gnome Settings

Status in Ubuntu Budgie:
  Confirmed
Status in xdg-utils package in Ubuntu:
  New

Bug description:
  (As seen in a daily build of Ubuntu Budgie 18.04 32bit downloaded
  earlier today)

  See attached screenshot.

  Thanks,
  Ken.
  ***

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

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

[Desktop-packages] [Bug 1754907] Re: Chromium address bar flickers and renders oddly

2018-03-17 Thread Ken T

Hi Olivier,

sorry for my slow reply - am writing from another machine at present.
Will post the results of that test in the next day or so, but in the
meantime stopped by to report the following:

The other day I spent an hour in Chromium on the laptop on which I'd
reported this issue, and for reasons I'm not sure of, the screen didn't
flicker! Will do some more testing and report back.

Ta,
K.

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

Title:
  Chromium address bar flickers and renders oddly

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  - As seen in yesterday's daily build of UB 18.04 32-bit, with updates
  applied today. Chromium Version 64.0.3282.167 (Official Build)

  See attached brief screencast, which I've tested can be viewed via
  VLC.

  Thanks,
  Ken.
  ***

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

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

[Desktop-packages] [Bug 1756526] Re: _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed

** Description changed:

  Gnome-shell session on xorg, with no opened apps
  
  Getting this logged:
  
  oem@ubuntu:~$ journalctl -b | grep XSERV
  /usr/lib/gdm3/gdm-x-session[1289]: _XSERVTransSocketUNIXCreateListener: 
...SocketCreateListener() failed
  /usr/lib/gdm3/gdm-x-session[1289]: _XSERVTransMakeAllCOTSServerListeners: 
server already running
  
  per https://www.x.org/wiki/FAQErrorMessages/
  
  i join the listening.txt output
  
  and there is no XO-lock file on the system, which seems abnormal.
+ 
+ As this missing XO-lock file should be set by system and/or app, report
+ also against gdm3 & systemd & gnome-shell (no idea which one to blame).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Mar 17 12:10:02 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: r8168, 8.045.08, 4.15.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
-Subsystem: ASRock Incorporation HD Graphics 530 [1849:1912]
+  Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
+    Subsystem: ASRock Incorporation HD Graphics 530 [1849:1912]
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 28 14:50:36 2018
  xserver.configfile: default
  xserver.devices:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  
+ 
  xserver.version: 2:1.19.6-1ubuntu2

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

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

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

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

Title:
  _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed

Status in gdm3 package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Gnome-shell session on xorg, with no opened apps

  Getting this logged:

  oem@ubuntu:~$ journalctl -b | grep XSERV
  /usr/lib/gdm3/gdm-x-session[1289]: _XSERVTransSocketUNIXCreateListener: 
...SocketCreateListener() failed
  /usr/lib/gdm3/gdm-x-session[1289]: _XSERVTransMakeAllCOTSServerListeners: 
server already running

  per https://www.x.org/wiki/FAQErrorMessages/

  i join

[Desktop-packages] [Bug 1756540] Re: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1754924, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1756540/+attachment/5082217/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1756540/+attachment/5082219/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1756540/+attachment/5082223/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1756540/+attachment/5082224/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1756540/+attachment/5082225/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1756540/+attachment/5082226/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1756540/+attachment/5082227/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1754924
   gnome-control-center crashed with SIGSEGV in actualize_printers_list()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.27.92-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 17 14:04:41 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-03-08 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x5643a46c75f1:mov0x90(%rbp),%rsi
   PC (0x5643a46c75f1) ok
   source "0x90(%rbp)" (0x0090) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

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

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

[Desktop-packages] [Bug 8949] Re: Opening a deleted 'recent document' results in a new file.

2018-03-17 Thread Luke B.

I can confirm this issue no longer affects Ubuntu 18.04, as recently
viewed items are removed upon deletion.

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

Title:
  Opening a deleted 'recent document' results in a new file.

Status in GNOME Panel:
  Invalid
Status in GTK+:
  Won't Fix
Status in One Hundred Papercuts:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  Confirmed

Bug description:
  http://bugzilla.gnome.org/show_bug.cgi?id=143385

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

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

[Desktop-packages] [Bug 1756547] [NEW] Some strings cannot be translated because of an error

2018-03-17 Thread AsciiWolf

Public bug reported:

Some strings of GNOME Shell are untranslated in the Czech translation on
Ubuntu 18.04 although they are translated upstream and when I try to
manually translate them on launchpad, I get this error: "number of
format specifications in 'msgid_plural' and 'msgstr[0]' does not match".

The bad strings are:
%d minute ago
%d minutes ago

%d hour ago
%d hours ago

%d week ago
%d weeks ago

%d month ago
%d months ago

%d year ago
%d years ago

They seem to be correct, but they are not accepted for some reason.

** Affects: ubuntu-translations
 Importance: Undecided
 Status: New

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


** Tags: bionic l10n

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

** Summary changed:

- Some strings cannot be translate because of an error
+ Some strings cannot be translated because of an error

** Description changed:

  Some strings of GNOME Shell are untranslated in the Czech translation on
  Ubuntu 18.04 although they are translated upstream and when I try to
  manually translate them on launchpad, I get this error: "number of
  format specifications in 'msgid_plural' and 'msgstr[0]' does not match".
  
  The bad strings are:
  %d minute ago
  %d minutes ago
  
  %d hour ago
  %d hours ago
  
  %d week ago
  %d weeks ago
  
  %d month ago
  %d months ago
  
  %d year ago
  %d years ago
+ 
+ They seem to be correct, but they are not accepted for some reason.

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

Title:
  Some strings cannot be translated because of an error

Status in Ubuntu Translations:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Some strings of GNOME Shell are untranslated in the Czech translation
  on Ubuntu 18.04 although they are translated upstream and when I try
  to manually translate them on launchpad, I get this error: "number of
  format specifications in 'msgid_plural' and 'msgstr[0]' does not
  match".

  The bad strings are:
  %d minute ago
  %d minutes ago

  %d hour ago
  %d hours ago

  %d week ago
  %d weeks ago

  %d month ago
  %d months ago

  %d year ago
  %d years ago

  They seem to be correct, but they are not accepted for some reason.

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

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

[Desktop-packages] [Bug 1756184] Re: Search making excessive requests for snap details and search

This bug was fixed in the package gnome-software - 3.28.0-0ubuntu4

---
gnome-software (3.28.0-0ubuntu4) bionic; urgency=medium

  * debian/patches/0001-Stop-searching-multiple-times-on-search-page.patch:
- Stop duplicate search queries (LP: #1756184)

 -- Robert Ancell   Fri, 16 Mar 2018
12:21:56 +1300

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

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

Title:
  Search making excessive requests for snap details and search

Status in gnome-software package in Ubuntu:
  Fix Released

Bug description:
  If you turn on snapd debugging and watch the log, you will see some
  excessive hits when working in Gnome Software. In particular, it
  seems:

  - Search makes the search request and then a details hit for every result
  - After clicking into a snap detail page and returning to the list, the query 
is repeated.

  Details requests should only be needed when clicking on a result, and
  returning to the search results should not repeat the query.

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

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

[Desktop-packages] [Bug 1751460] Re: [regression] deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

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

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

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

Title:
  [regression] deja-dup-monitor crashed with SIGSEGV in
  Gigacageoperator()

Status in Déjà Dup:
  New
Status in WebKit:
  Confirmed
Status in deja-dup package in Ubuntu:
  Fix Released
Status in webkit2gtk package in Ubuntu:
  Triaged
Status in deja-dup source package in Xenial:
  Triaged
Status in webkit2gtk source package in Xenial:
  Confirmed
Status in deja-dup source package in Artful:
  Triaged
Status in webkit2gtk source package in Artful:
  Confirmed
Status in deja-dup source package in Bionic:
  Fix Released
Status in webkit2gtk source package in Bionic:
  Triaged

Bug description:
  https://errors.ubuntu.com/problem/27441b78823246dd5392ee29ac30546f6464289e

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Feb 24 14:30:47 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-12-27 (59 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff1c3dda588:movl   $0x0,(%rax)
   PC (0x7ff1c3dda588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7ff1c404202c, 
init_routine=0x7ff1baec0490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess >::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  UpgradeStatus: Upgraded to bionic on 2018-02-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1751460] Re: [regression] deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

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

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

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

Title:
  [regression] deja-dup-monitor crashed with SIGSEGV in
  Gigacageoperator()

Status in Déjà Dup:
  New
Status in WebKit:
  Confirmed
Status in deja-dup package in Ubuntu:
  Fix Released
Status in webkit2gtk package in Ubuntu:
  Triaged
Status in deja-dup source package in Xenial:
  Triaged
Status in webkit2gtk source package in Xenial:
  Confirmed
Status in deja-dup source package in Artful:
  Triaged
Status in webkit2gtk source package in Artful:
  Confirmed
Status in deja-dup source package in Bionic:
  Fix Released
Status in webkit2gtk source package in Bionic:
  Triaged

Bug description:
  https://errors.ubuntu.com/problem/27441b78823246dd5392ee29ac30546f6464289e

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Feb 24 14:30:47 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-12-27 (59 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff1c3dda588:movl   $0x0,(%rax)
   PC (0x7ff1c3dda588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7ff1c404202c, 
init_routine=0x7ff1baec0490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess >::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  UpgradeStatus: Upgraded to bionic on 2018-02-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1438422] Re: Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

2018-03-17 Thread Antoine Monmayrant

Hello, I confirm I face the very same bug on my HP Spectre x360 G2 with both 
17.10 and 18.04 beta (it was OK on 17.04):
# Folding to tablet mode and back to laptop mode:
## Unknown keypress is registered:
grep Unknown /var/log/syslog
Mar 17 14:24:53 lyre kernel: [11312.248585] atkbd serio0: 
Unknown key released (translated set 2, code 0xd8 on isa0060/serio0).
## Airplane gets activated and has to be manually deactivated

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

Title:
  Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

Status in compiz package in Ubuntu:
  Invalid
Status in gnome-session package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in urfkill package in Ubuntu:
  New

Bug description:
  This bug appears to be a regression in Vivid sometime in the second
  half of March 2015.

  When the machine is tilted (e.g., onto its side), Syslog reports an
  "unknown" button being pressed. When tilted back to the normal laptop
  position, the machine's WiFi disconnects and is shown as disabled in
  the connection manager. Syslog indicates that urfkill registered a
  hardware switch cutoff for the WiFi.

  I know that the accelerometers do work in other contexts and can be
  read properly in Ubuntu. As an example, this "orient" script works for
  me: https://github.com/leszakk/orient .

  Hardware: HP Envy x360 15t -- this is a hybrid touch notebook
  OS: Ubuntu 15.04 Beta 2 -- Desktop version
  Kernel:  3.19.0-10-generic
  urfkill:
    Installed: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Candidate: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Version table:
   *** 0.6.0~20150318.103828.5539c0d.1-0ubuntu1 0
  500 http://mirrors.mit.edu/ubuntu/ vivid/universe amd64 Packages
  100 /var/lib/dpkg/status

  Below is a Syslog readout from a test event. The notebook starts in
  normal typing position, the hinge bent at a right angle. At 16:13:30,
  without moving the hinge, I tip the notebook 90 degrees to the left
  from my perspective. So the Unity launcher is now closest to the
  floor, for example. I hold it there for about 10 seconds until
  16:13:40.

  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717086] atkbd serio0: Unknown 
key pressed (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717098] atkbd serio0: Use 
'setkeycodes e058 ' to make it known.
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724168] atkbd serio0: Unknown 
key released (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724180] atkbd serio0: Use 
'setkeycodes e058 ' to make it known.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: Setting WLAN devices to blocked
  Mar 30 16:13:41 [my_hostname] URfkill[868]: set_soft: Setting WLAN to blocked
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.698934] wlan0: deauthenticating 
from [ma:ca:dd:re:ss] by local choice (Reason: 3=DEAUTH_LEAVING)
  Mar 30 16:13:41 [my_hostname] wpa_supplicant[1015]: wlan0: 
CTRL-EVENT-DISCONNECTED bssid=[ma:ca:dd:re:ss] reason=3 locally_generated=1
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.710906] cfg80211: Calling CRDA 
to update world regulatory domain
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv6 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv6 with address fe80::8286:f2ff:fe32:def8.
  Mar 30 16:13:41 [my_hostname] dhclient: receive_packet failed on wlan0: 
Network is down
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv4 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv4 with address 192.168.1.133.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for fe80::8286:f2ff:fe32:def8 on wlan0.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for 192.168.1.133 on wlan0.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: device_changed_cb: phy0
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  Connection 
disconnected (reason -3)
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  
[1427746421.849186] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  
[1427746421.849417] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 192.168.1.1/32 via 0.0.0.0 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  
[1427746421.849591] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: 
U

[Desktop-packages] [Bug 1438422] Re: Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

2018-03-17 Thread Antoine Monmayrant

Hello again,

Here is another way to look at this unexpected unknown key press and airplane 
mode activated (ie wifi killed):
acpi_listen 
# Folding to tablet mode and back to laptop mode again
button/wlan WLAN 0080  K
button/wlan WLAN 0080  K
button/wlan WLAN 0080  K

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

Title:
  Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

Status in compiz package in Ubuntu:
  Invalid
Status in gnome-session package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in urfkill package in Ubuntu:
  New

Bug description:
  This bug appears to be a regression in Vivid sometime in the second
  half of March 2015.

  When the machine is tilted (e.g., onto its side), Syslog reports an
  "unknown" button being pressed. When tilted back to the normal laptop
  position, the machine's WiFi disconnects and is shown as disabled in
  the connection manager. Syslog indicates that urfkill registered a
  hardware switch cutoff for the WiFi.

  I know that the accelerometers do work in other contexts and can be
  read properly in Ubuntu. As an example, this "orient" script works for
  me: https://github.com/leszakk/orient .

  Hardware: HP Envy x360 15t -- this is a hybrid touch notebook
  OS: Ubuntu 15.04 Beta 2 -- Desktop version
  Kernel:  3.19.0-10-generic
  urfkill:
    Installed: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Candidate: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Version table:
   *** 0.6.0~20150318.103828.5539c0d.1-0ubuntu1 0
  500 http://mirrors.mit.edu/ubuntu/ vivid/universe amd64 Packages
  100 /var/lib/dpkg/status

  Below is a Syslog readout from a test event. The notebook starts in
  normal typing position, the hinge bent at a right angle. At 16:13:30,
  without moving the hinge, I tip the notebook 90 degrees to the left
  from my perspective. So the Unity launcher is now closest to the
  floor, for example. I hold it there for about 10 seconds until
  16:13:40.

  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717086] atkbd serio0: Unknown 
key pressed (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717098] atkbd serio0: Use 
'setkeycodes e058 ' to make it known.
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724168] atkbd serio0: Unknown 
key released (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724180] atkbd serio0: Use 
'setkeycodes e058 ' to make it known.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: Setting WLAN devices to blocked
  Mar 30 16:13:41 [my_hostname] URfkill[868]: set_soft: Setting WLAN to blocked
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.698934] wlan0: deauthenticating 
from [ma:ca:dd:re:ss] by local choice (Reason: 3=DEAUTH_LEAVING)
  Mar 30 16:13:41 [my_hostname] wpa_supplicant[1015]: wlan0: 
CTRL-EVENT-DISCONNECTED bssid=[ma:ca:dd:re:ss] reason=3 locally_generated=1
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.710906] cfg80211: Calling CRDA 
to update world regulatory domain
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv6 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv6 with address fe80::8286:f2ff:fe32:def8.
  Mar 30 16:13:41 [my_hostname] dhclient: receive_packet failed on wlan0: 
Network is down
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv4 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv4 with address 192.168.1.133.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for fe80::8286:f2ff:fe32:def8 on wlan0.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for 192.168.1.133 on wlan0.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: device_changed_cb: phy0
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  Connection 
disconnected (reason -3)
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  
[1427746421.849186] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  
[1427746421.849417] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 192.168.1.1/32 via 0.0.0.0 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  
[1427746421.849591] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Joining mDNS multicast group 
on interface wlan0.IPv4 with address 1

[Desktop-packages] [Bug 1727653] Re: error: can't start new thread

2018-03-17 Thread Kenneth Loafman

Try running the command as:

DEJA_DUP_DEBUG=1 sh -c "ulimit -v 100; ulimit -n 8192; exec 
/usr/lib/x86_64-linux-gnu
/deja-dup/deja-dup-monitor"

This will create a large debug log in ~/.cache/deja-dup/.  Please add
that as an attachment to this bug report.

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

Title:
  error: can't start new thread

Status in Duplicity:
  In Progress
Status in deja-dup package in Ubuntu:
  Triaged
Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  --

  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
  manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
  fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
  fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
  return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
  'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
374, in run
  create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
420, in _attach_fork_exec
  process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
  _start_new_thread(self.__bootstrap, ())
  error: can't start new thread

  --

  Restarting deja-dup manually fixes the problem and the next few days,
  automatic backup will run correctly until (see above).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:49:45 2017
  InstallationDate: Installed on 2017-10-20 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1756472] [NEW] 17.10 CUPS remote printing issue