date:20180308

Also:

3. Please run 'lspci -k' and attach the output.

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

Title:
  18.04 3.27 Gnome-shell Near-Fatalities

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

Bug description:
  If I close the lid, it seems that the computer flat-out doesn't wake
  up. HOWEVER, if I wait patiently more than 20 seconds, and press (not
  hold) the power button, SOMETIMES, the computer will "snap out of it"
  and come back to my desktop. Although RAM is 25% used, and CPU usage
  is around 25-50% or less (depending on apps), mouse will regularly
  freeze up for some seconds every 10 seconds or so. Wifi will claim to
  be "on", but there aren't any networks in the "select network"
  dialogue. Turning wifi off and then on does not fix this problem. So
  I'll be in this terrifying state of non-responsive every few seconds
  computer, with no ability to reconnect to networks and report bug.

  I force restart. The first restart, upon login, will hang indefinitely
  on a purple screen with the cursor in the middle. I will have to force
  restart again. Upon 2nd restart, it will boot "normally".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 12:38:24 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-02 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1754425] Re: 18.04 3.27 Gnome-shell Near-Fatalities

Thanks Tom. More questions:

1. How are you trying to wake up the machine initially? Do you mean you're 
_opening_ the lid and expecting it to wake up (which is correct)?
("If I close the lid, it seems that the computer flat-out doesn't wake up.")

2. Can you please attach output from 'dmesg' ASAP after the problem has
started? I can see some hints of kernel/hardware issues in your
JournalErrors.txt but maybe 'dmesg' would be more useful.

** Description changed:

- It's impossible to make a normal bug report, so here's the best I can
- describe:
- 
- EVERY login to gnome, there is a moment after I enter my password and
- press return, where whole screen goes small-resolution (cursor small,
- all text and boxes get smaller), and best way to describe it is
- "colorful static" pattern replaces the purple/black. After this hiccup,
- a moment of black, then taken to the gnome desktop. Things work fine.
- 
  If I close the lid, it seems that the computer flat-out doesn't wake up.
  HOWEVER, if I wait patiently more than 20 seconds, and press (not hold)
  the power button, SOMETIMES, the computer will "snap out of it" and come
  back to my desktop. Although RAM is 25% used, and CPU usage is around
  25-50% or less (depending on apps), mouse will regularly freeze up for
  some seconds every 10 seconds or so. Wifi will claim to be "on", but
  there aren't any networks in the "select network" dialogue. Turning wifi
  off and then on does not fix this problem. So I'll be in this terrifying
  state of non-responsive every few seconds computer, with no ability to
  reconnect to networks and report bug.
  
  I force restart. The first restart, upon login, will hang indefinitely
  on a purple screen with the cursor in the middle. I will have to force
  restart again. Upon 2nd restart, it will boot "normally", in that after
  I login, I get the "familiar" "colorful static" splash screen before
  being taken to normal functional gnome desktop experience.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 12:38:24 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-02 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  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-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  If I close the lid, it seems that the computer flat-out doesn't wake up.
  HOWEVER, if I wait patiently more than 20 seconds, and press (not hold)
  the power button, SOMETIMES, the computer will "snap out of it" and come
  back to my desktop. Although RAM is 25% used, and CPU usage is around
  25-50% or less (depending on apps), mouse will regularly freeze up for
  some seconds every 10 seconds or so. Wifi will claim to be "on", but
  there aren't any networks in the "select network" dialogue. Turning wifi
  off and then on does not fix this problem. So I'll be in this terrifying
  state of non-responsive every few seconds computer, with no ability to
  reconnect to networks and report bug.
  
  I force restart. The first restart, upon login, will hang indefinitely
  on a purple screen with the cursor in the middle. I will have to force
- restart again. Upon 2nd restart, it will boot "normally", in that after
- I login, I get the "familiar" "colorful static" splash screen before
- being taken to normal functional gnome desktop experience.
+ restart again. Upon 2nd restart, it will boot "normally".
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 12:38:24 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-02 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

Title:
  18.04 3.27 Gnome-shell Near-Fatalities

Status in gnome-shell package in

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

2018-03-08 Thread geez

This bug appears to be crashing nautilus every time I try to open a file
(by double clicking). As such, it is quite critical for me, as it
effectively rendered the machine with 18.04 beta impossible to work on.
Is anyone else experiencing this?

-- 
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
  Gigacage::::operator()

Status in WebKit:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed
Status in deja-dup source package in Bionic:
  Confirmed
Status in webkit2gtk source package in Bionic:
  Confirmed

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/webkit-open-source/+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 1620688] Re: Evince crashed when a page of the pdf disapear

2018-03-08 Thread Thom Wiggers

** Also affects: evince (Arch Linux)
   Importance: Undecided
   Status: New

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

Title:
  Evince crashed when a page of the pdf disapear

Status in evince package in Ubuntu:
  Expired
Status in evince package in Arch Linux:
  New

Bug description:
  The issue appeared when I was working on a LaTeX document:
  * the pdf generated by LaTeX (which contains 3 pages) is displayed in a 
Evince Window, at the page, say, 3.
  * At the next LaTeX compilation, my document contains only 2 pages.
  * Since my pdf has changed on the disk, Evince try to reload it but fail 
because the cursor is on the 3rd page which doesn't exist anymore. It make 
Evince crashed with a : "Segmentation fault (core dumped)".

  Possible desired behavior when this scenario occurs: go to the last
  reachable page (in my case the second one).

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

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

Re: [Desktop-packages] [Bug 1754425] Re: 18.04 3.27 Gnome-shell Near-Fatalities

Remove references to colorful static. The problem was these issues may or
may not be related, and both are not reportable in the usual way. I was
just mentioning all the serious symptoms of problems together, rather than
assuming they were all the result of a single discrete bug.

On Mar 8, 2018 21:51, "Daniel van Vugt" 
wrote:

> Tom, please try to report one issue per bug.
>
> We can either:
>
>  * make this a duplicate of bug 1753776 and you log a new bug for the
> other problem; or
>  * remove references to the first "static" problem from this bug.
>
> So please let us know how you'd like to proceed.
>
> ** Changed in: gnome-shell (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1754425
>
> Title:
>   18.04 3.27 Gnome-shell Near-Fatalities
>
> Status in gnome-shell package in Ubuntu:
>   Incomplete
>
> Bug description:
>   It's impossible to make a normal bug report, so here's the best I can
>   describe:
>
>   EVERY login to gnome, there is a moment after I enter my password and
>   press return, where whole screen goes small-resolution (cursor small,
>   all text and boxes get smaller), and best way to describe it is
>   "colorful static" pattern replaces the purple/black. After this
>   hiccup, a moment of black, then taken to the gnome desktop. Things
>   work fine.
>
>   If I close the lid, it seems that the computer flat-out doesn't wake
>   up. HOWEVER, if I wait patiently more than 20 seconds, and press (not
>   hold) the power button, SOMETIMES, the computer will "snap out of it"
>   and come back to my desktop. Although RAM is 25% used, and CPU usage
>   is around 25-50% or less (depending on apps), mouse will regularly
>   freeze up for some seconds every 10 seconds or so. Wifi will claim to
>   be "on", but there aren't any networks in the "select network"
>   dialogue. Turning wifi off and then on does not fix this problem. So
>   I'll be in this terrifying state of non-responsive every few seconds
>   computer, with no ability to reconnect to networks and report bug.
>
>   I force restart. The first restart, upon login, will hang indefinitely
>   on a purple screen with the cursor in the middle. I will have to force
>   restart again. Upon 2nd restart, it will boot "normally", in that
>   after I login, I get the "familiar" "colorful static" splash screen
>   before being taken to normal functional gnome desktop experience.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-shell 3.27.92-0ubuntu1
>   ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
>   Uname: Linux 4.15.0-10-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu Mar  8 12:38:24 2018
>   DisplayManager: gdm3
>   InstallationDate: Installed on 2018-03-02 (5 days ago)
>   InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64
> (20180228)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gnome-shell
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+
> bug/1754425/+subscriptions
>

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

Title:
  18.04 3.27 Gnome-shell Near-Fatalities

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  It's impossible to make a normal bug report, so here's the best I can
  describe:

  EVERY login to gnome, there is a moment after I enter my password and
  press return, where whole screen goes small-resolution (cursor small,
  all text and boxes get smaller), and best way to describe it is
  "colorful static" pattern replaces the purple/black. After this
  hiccup, a moment of black, then taken to the gnome desktop. Things
  work fine.

  If I close the lid, it seems that the computer flat-out doesn't wake
  up. HOWEVER, if I wait patiently more than 20 seconds, and press (not
  hold) the power button, SOMETIMES, the computer will "snap out of it"
  and come back to my desktop. Although RAM is 25% used, and CPU usage
  is around 25-50% or less (depending on apps), mouse will regularly
  freeze up for some seconds every 10 seconds or so. Wifi will claim to
  be "on", but there aren't any networks in the "select network"
  dialogue. Turning wifi off and then on does not fix this problem. So
  I'll be in this terrifying state of non-responsive every few seconds
  computer, with no ability to reconnect to networks and report bug.

  I force restart. The first restart, upon login, will hang indefinitely
  on a purple screen with the cursor in the middle. I will have to force

[Desktop-packages] [Bug 239669] Re: Inkscape saves imported images from openclipart to /tmp

2018-03-08 Thread Kuntal Majumder

Cannot reproduce with trunk.


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

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

Title:
  Inkscape saves imported images from openclipart to /tmp

Status in Inkscape:
  Fix Released
Status in inkscape package in Ubuntu:
  Triaged
Status in inkscape package in Debian:
  Confirmed

Bug description:
  Hello to all!!!

  I have created a design and I have imported a clipart from openclipart.
  I have done some work and the next day I have reopened it.

  But in the place of all the openclipart, there's a "Linked image not
  found"

  I have inspectioned more this and the problem is that inkscape save the 
imported images
  by default in /tmp (i'm on ubuntu linux)
  and the path to this images point to /tmp also
  and when the system is restarted, on linux /tmp is cleared.

  And when I click search, for each click is imported and created an
  image in /tmp

  see for example the attached image, i have clicked on horse cuissard, horse 
and man, horse (lego)
  and then restarted with horse cuissard and on the left is my /tmp folder

  I think that import from openclipart should ask where to put all imported 
clipart
  (maybe in ~/.inkscape/clipart/myclipart or better in the same folder as .svg 
file)
  or incorporate the image in the .svg file
  (in this manner if I need to send the file to another person he/she don't 
lost all
  the imported clipart.

  Thanks for your work!!

  Nicola Lunghi

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

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

[Desktop-packages] [Bug 1754458] Re: applet symbol not displayed on mate (18.04)

2018-03-08 Thread Michael

** Also affects: mate-desktop (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  applet symbol not displayed on mate (18.04)

Status in mate-desktop package in Ubuntu:
  New
Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 18.04, the network manager applet symbol
  isn't displayed any longer. The other functionality (asking for
  credentials) is working. I also see other symbols.

  
  aptitude show network-manager-gnome
  Paket: network-manager-gnome
  Version: 1.8.10-2ubuntu1
  Neu: ja
  Zustand: Installiert

  
  stdout/stderr:
  Gtk-Message: 21:28:14.411: Failed to load module "appmenu-gtk-module"
  Gtk-Message: 21:28:14.431: Failed to load module "topmenu-gtk-module"
  Gtk-Message: 21:28:14.431: Failed to load module "appmenu-gtk-module"
  Gtk-Message: 21:28:14.432: Failed to load module "topmenu-gtk-module"

  ** (nm-applet:29524): WARNING **: 21:28:14.668: Couldn't register with
  accessibility bus: Did not receive a reply. Possible causes include:
  the remote application did not send a reply, the message bus security
  policy blocked the reply, the reply timeout expired, or the network
  connection was broken.

  (nm-applet:29524): nm-applet-WARNING **: 21:28:15.987: Cannot grab
  information for modem at /org/freedesktop/ModemManager1/Modem/6: No
  ModemManager support

  (nm-applet:29524): nm-applet-WARNING **: 21:28:16.124: ModemManager is
  not available for modem at /org/freedesktop/ModemManager1/Modem/6

  (nm-applet:29524): Gtk-WARNING **: 21:28:16.127: Can't set a parent on
  widget which has a parent

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-WARNING **: 21:28:16.171: Can't set a parent on
  widget which has a parent

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-WARNING **: 21:28:21.570: Can't set a parent on
  widget which has a parent

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-WARNING **: 21:28:24.655: Can't set a parent on
  widget which has a parent

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-gnome 1.8.10-2ubuntu1
  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: MATE
  Date: Thu Mar  8 21:27:56 2018
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  WpaSupplicantLog:
   
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-desktop/+bug/1754458/+subscriptions

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

[Desktop-packages] [Bug 1754564] [NEW] nautilus crash on double click on a file

2018-03-08 Thread cubells

Public bug reported:

On double click on a file like as test.txt, nautilus is closed suddenly
and file is not open.


$ G_DEBUG="all" NAUTILUS_DEBUG="All" nautilus
Gdk-Message: 06:47:01.176: Error 71 (Error de protocol) dispatching to Wayland 
display.


$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04
Codename:   bionic

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

** Package changed: evince (Ubuntu) => nautilus (Ubuntu)

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

Title:
  nautilus crash on double click on a file

Status in nautilus package in Ubuntu:
  New

Bug description:
  On double click on a file like as test.txt, nautilus is closed
  suddenly and file is not open.

  
  $ G_DEBUG="all" NAUTILUS_DEBUG="All" nautilus
  Gdk-Message: 06:47:01.176: Error 71 (Error de protocol) dispatching to 
Wayland display.


  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  Codename: bionic

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

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

[Desktop-packages] [Bug 1754485] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

2018-03-08 Thread dino99

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

** This bug has been marked a duplicate of bug 1725928
   package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with 
differing files  '/lib/udev/hwdb.d/20-sane.hwdb'

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I just updated my video drivers (nvidia 340), when i rebooted i got
  this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sat Mar  3 11:41:01 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-9SXQB5/51-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-02-26 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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::<lambda()>::operator()

2018-03-08 Thread vasilisc

[Ubuntu release]
Release:18.04
Codename:   bionic

[uname]
Linux vasilisc 4.15.0-12-generic #13-Ubuntu SMP Thu Mar 8 06:24:47 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

[Kernel command line]
BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=UUID=6d8ea6da-b2d9-406c-a812-2b21a2925731 ro rootflags=subvol=@ 
elevator=cfq


deja-dup:
  Installed: 37.1-1fakesync1
  Candidate: 37.1-1fakesync1
  Version table:
 *** 37.1-1fakesync1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

-- 
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
  Gigacage::::operator()

Status in WebKit:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed
Status in deja-dup source package in Bionic:
  Confirmed
Status in webkit2gtk source package in Bionic:
  Confirmed

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/webkit-open-source/+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: deja-dup-monitor crashed with SIGSEGV in Gigacage::<lambda()>::operator()

Also tracking in:
https://errors.ubuntu.com/problem/27441b78823246dd5392ee29ac30546f6464289e

** Description changed:

- not sure. upgraded to 18.10.
+ 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
+  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)!
+  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
+  ?? () 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

** Summary changed:

- deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()
+ [regression] deja-dup-monitor crashed with SIGSEGV in 
Gigacage::::operator()

** Tags added: regression-update

-- 
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
  Gigacage::::operator()

Status in WebKit:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed
Status in deja-dup source package in Bionic:
  Confirmed
Status in webkit2gtk source package in Bionic:
  Confirmed

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

[Desktop-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!

2018-03-08 Thread BETLOG

Yep, mine reverts to 1024x760 76Hz and has no options whatsoever.
It's a bit of a showstopper.

dmesg:
nvidia: version magic '3.13.0-143-generic SMP mod_unload modversions ' should 
be '3.13.0-143-generic SMP mod_unload modversions retpoline '

works:
Linux betlogbrick 3.13.0-142-generic #191-Ubuntu SMP Fri Feb 2 12:13:35 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

fails:
*3.13.0-143*

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04) by an insufficient compiler!

Status in gcc:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Desktop-packages] [Bug 1754557] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1748450, so it 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. Feel free to continue to report any other bugs you may
find.


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

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  this is an automated bug report.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Mar  9 02:43:53 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2015-08-05 (946 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  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/1754557/+subscriptions

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

[Desktop-packages] [Bug 1754557] [NEW] gnome-shell crashed with signal 5 in g_log_default_handler()

2018-03-08 Thread Karma Dorje

Public bug reported:

this is an automated bug report.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.27.92-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Fri Mar  9 02:43:53 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 
InstallationDate: Installed on 2015-08-05 (946 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/false
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with signal 5 in g_log_default_handler()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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


** Tags: amd64 apport-crash bionic need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  this is an automated bug report.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Mar  9 02:43:53 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2015-08-05 (946 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  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/1754557/+subscriptions

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

[Desktop-packages] [Bug 1709806] Re: autopkgtest fails on ppc64el

The autopkgtests look pretty reliable since mid-December

http://autopkgtest.ubuntu.com/packages/u/udisks2/bionic/ppc64el

There is still a hint for udisks2/2.6.5-2ubuntu2/ppc64el
Maybe that's useful a bit longer for artful SRUs?

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

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

Title:
  autopkgtest fails on ppc64el

Status in udisks2 package in Ubuntu:
  Fix Released

Bug description:
  Ever since version 2.6.5-2ubuntu1, the autopkgtest for udisks2 has
  been very flaky (failing ~80% of the time) on ppc64el:
  http://autopkgtest.ubuntu.com/packages/u/udisks2/artful/ppc64el

  We attempted to debug a little and managed to reproduce in a VM but we
  got confused trying to debug:

  [00:09:15]  Summary:
  [00:09:17]  - directly calling asubtest fails (call_lock_sync), you 
need to run all Luks tests as they depend on each other
  [00:09:18]$ sudo src/tests/integration-test Luks
  [00:09:19]There it mostly fails at one of (always a different) 
test
  [00:09:21]  - Once the bug was triggered by any of the tests in 
Luks it can be ran into with a subtest alone like
  [00:09:23]$ sudo src/tests/integration-test 
Luks.test_ascii_keyfile_newline
  [00:09:24]  - at some point after the issue further tests block at 
being unable to remove scsi_debug (needs reboot)
  [00:09:26]  - nothing obvious in dmesg, or journal neither on usidk 
nor scsi_debug
  [00:09:27]  - I've run a small dbus checker and it lists 
org.freedesktop.UDisks2 still as active
  [00:09:28]  With udisk giving neither a crash nor any sort of 
message and the test only reporting a lost connection on the Dbus service I 
leave it to you to continue tmrw
  [00:09:31]  mwhudson ^^

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

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

[Desktop-packages] [Bug 1753203] Re: unable to access audio disc in nautilus

2018-03-08 Thread Greg Trent

Received an update on March 7 and now I can play audio CD's.

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

Title:
  unable to access audio disc in nautilus

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Recently upgraded from Ubuntu 17.10 to Ubuntu 18.04 Bionic Beaver(development 
branch).
  Message recipient disconnected from message bus without replying. I can open 
the audio cd in VLC but when I try in Rhythmbox, I get the same message as 
Nautilus

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.2-0ubuntu3.1
  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: Sat Mar  3 23:37:36 2018
  InstallationDate: Installed on 2017-04-20 (318 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to bionic on 2018-03-02 (1 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1753203] Bug 1753203

2018-03-08 Thread Greg Trent

Received an update on March 7 and now I can play an audio cd.

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

Title:
  unable to access audio disc in nautilus

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Recently upgraded from Ubuntu 17.10 to Ubuntu 18.04 Bionic Beaver(development 
branch).
  Message recipient disconnected from message bus without replying. I can open 
the audio cd in VLC but when I try in Rhythmbox, I get the same message as 
Nautilus

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.2-0ubuntu3.1
  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: Sat Mar  3 23:37:36 2018
  InstallationDate: Installed on 2017-04-20 (318 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to bionic on 2018-03-02 (1 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1736603] Re: Port ibus-chewing to gtk3

2018-03-08 Thread Bug Watch Updater

** Changed in: ibus-chewing
   Status: Unknown => New

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

Title:
  Port ibus-chewing to gtk3

Status in ibus-chewing:
  New
Status in ibus-chewing package in Ubuntu:
  New

Bug description:
  gtk3 was declared stable in September 2016 with the gtk 3.22 release.
  ibus-chewing should switch to gtk3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus-chewing/+bug/1736603/+subscriptions

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

[Desktop-packages] [Bug 1736603] Re: Port ibus-chewing to gtk3

** Bug watch added: github.com/definite/ibus-chewing/issues #125
   https://github.com/definite/ibus-chewing/issues/125

** Also affects: ibus-chewing via
   https://github.com/definite/ibus-chewing/issues/125
   Importance: Unknown
   Status: Unknown

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

Title:
  Port ibus-chewing to gtk3

Status in ibus-chewing:
  Unknown
Status in ibus-chewing package in Ubuntu:
  New

Bug description:
  gtk3 was declared stable in September 2016 with the gtk 3.22 release.
  ibus-chewing should switch to gtk3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus-chewing/+bug/1736603/+subscriptions

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

[Desktop-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card

2018-03-08 Thread Kai-Heng Feng

Please see if this issue can be solved after remove xserver-xorg-video-
intel.

Also, 945GME is quite different to the one used by original bug
reporter...

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

Title:
  External monitor connecting problem on Intel graphics card

Status in linux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Desktop-packages] [Bug 1754401] Re: Fatal server error: (EE) xf86OpenConsole: Cannot open virtual console 1 (Permission denied)

** Also affects: xorg-server (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/1754401

Title:
  Fatal server error: (EE) xf86OpenConsole: Cannot open virtual console
  1 (Permission denied)

Status in gdm3 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I don't what changed but today, my Artful laptop refuses to start a
  graphical session. The last update seems entirely unrelated:

  # /var/log/apt/history.log
  Start-Date: 2018-03-06  15:50:35
  Commandline: apt-get dist-upgrade
  Requested-By: simon (1000)
  Upgrade: libpq5:amd64 (9.6.7-0ubuntu0.17.10, 9.6.8-0ubuntu0.17.10)
  End-Date: 2018-03-06  15:50:39

  I tried linux-image-4.13.0-32-generic and linux-
  image-4.13.0-36-generic to no avail. I removed the "quiet splash" args
  from /etc/default/grub but it didn't help. Using "nomodeset" makes the
  graphical session almost work but the brightness of the screen is so
  low that I cannot use it and can't make it brighter either.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.26.1-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Thu Mar  8 11:08:35 2018
  InstallationDate: Installed on 2017-10-21 (137 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1754425] Re: 18.04 3.27 Gnome-shell Near-Fatalities

Tom, please try to report one issue per bug.

We can either:

 * make this a duplicate of bug 1753776 and you log a new bug for the other 
problem; or
 * remove references to the first "static" problem from this bug.

So please let us know how you'd like to proceed.

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

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

Title:
  18.04 3.27 Gnome-shell Near-Fatalities

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  It's impossible to make a normal bug report, so here's the best I can
  describe:

  EVERY login to gnome, there is a moment after I enter my password and
  press return, where whole screen goes small-resolution (cursor small,
  all text and boxes get smaller), and best way to describe it is
  "colorful static" pattern replaces the purple/black. After this
  hiccup, a moment of black, then taken to the gnome desktop. Things
  work fine.

  If I close the lid, it seems that the computer flat-out doesn't wake
  up. HOWEVER, if I wait patiently more than 20 seconds, and press (not
  hold) the power button, SOMETIMES, the computer will "snap out of it"
  and come back to my desktop. Although RAM is 25% used, and CPU usage
  is around 25-50% or less (depending on apps), mouse will regularly
  freeze up for some seconds every 10 seconds or so. Wifi will claim to
  be "on", but there aren't any networks in the "select network"
  dialogue. Turning wifi off and then on does not fix this problem. So
  I'll be in this terrifying state of non-responsive every few seconds
  computer, with no ability to reconnect to networks and report bug.

  I force restart. The first restart, upon login, will hang indefinitely
  on a purple screen with the cursor in the middle. I will have to force
  restart again. Upon 2nd restart, it will boot "normally", in that
  after I login, I get the "familiar" "colorful static" splash screen
  before being taken to normal functional gnome desktop experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 12:38:24 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-02 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1727690] Re: package liblouis-data 2.6.4-2ubuntu0.1 failed to install/upgrade: package liblouis-data is not ready for configuration cannot configure (current status 'half-insta

2018-03-08 Thread Launchpad Bug Tracker

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

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

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

Title:
  package liblouis-data 2.6.4-2ubuntu0.1 failed to install/upgrade:
  package liblouis-data is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in liblouis package in Ubuntu:
  Confirmed

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: liblouis-data 2.6.4-2ubuntu0.1
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Oct 26 15:59:15 2017
  Dependencies:
   
  DuplicateSignature:
   package:liblouis-data:2.6.4-2ubuntu0.1
   Processing triggers for libc-bin (2.23-0ubuntu9) ...
   dpkg: error processing package liblouis-data (--configure):
package liblouis-data is not ready for configuration
  ErrorMessage: package liblouis-data is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-10-26 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: liblouis
  Title: package liblouis-data 2.6.4-2ubuntu0.1 failed to install/upgrade: 
package liblouis-data is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1754077] Re: (gnome-shell:26479): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion 'handler_id > 0' failed

Thanks. I can't seem to find any other reports of this crash yet,
although that's also partly due to errors.ubuntu.com not responding
today...

Please help us to gather a .crash file next time this problem occurs by:
1. Apply the workaround from bug 994921 now.
2. Next time the crash occurs, look in /var/crash for new files and then run:
   ubuntu-bug /var/crash/YOURFILE.crash
3. Let us know here the ID of the new bug the above command created.

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

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

Title:
  (gnome-shell:26479): GLib-GObject-CRITICAL **:
  g_signal_handler_disconnect: assertion 'handler_id > 0' failed

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Some times gnomeshell just gets stuck and crashes. I keep sending the bug 
reports automatically with the tool, and updating the system, but the issue is 
still there.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 16.04
  GsettingsChanges:
   org.gnome.shell enabled-extensions ['nohotcor...@azuri.free.fr', 
'topic...@phocean.net']
   org.gnome.shell command-history ['gconf-editor', 'dconf-editor', 'r', 
'xrandr', 'r', 'right_mouse.sh', 'r', 'R', 'r', 'terminal', 'term', 'r', 
'gnome-desktop-item-edit --create-new ~/Desktop', 'r']
   org.gnome.shell favorite-apps ['firefox.desktop', 'evolution.desktop', 
'libreoffice-writer.desktop', 'org.gnome.Nautilus.desktop', 
'chromium-browser.desktop', 'yelp.desktop', 'Mattermost.desktop', 
'skypeforlinux.desktop', 'google-chrome.desktop']
   org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
  InstallationDate: Installed on 2017-06-14 (267 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  Package: gnome-shell 3.18.5-0ubuntu0.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Tags: third-party-packages xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1753078] Re: gnome-shell crashed with SIGABRT in dump_gjs_stack_on_signal_handler() from __GI_raise() from __GI_abort() from glibtop_error_io_vr() from glibtop_error_io_r() fro

Thanks. I think I've found the related packages now. See above.

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

** Changed in: libgtop2 (Ubuntu)
   Importance: Undecided => Medium

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

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

** Changed in: gnome-shell-extension-system-monitor (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  gnome-shell crashed with SIGABRT in dump_gjs_stack_on_signal_handler()
  from __GI_raise() from __GI_abort() from glibtop_error_io_vr() from
  glibtop_error_io_r() from file_to_buffer() from glibtop_get_cpu_s()

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-system-monitor package in Ubuntu:
  New
Status in libgtop2 package in Ubuntu:
  New

Bug description:
  This error showed up after waking up the computer from sleep.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-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
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Mar  3 03:18:44 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2015-09-28 (886 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_PH:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgtop-2.0.so.11
   () at /usr/lib/x86_64-linux-gnu/libgtop-2.0.so.11
   () at /usr/lib/x86_64-linux-gnu/libgtop-2.0.so.11
   () at /usr/lib/x86_64-linux-gnu/libgtop-2.0.so.11
   glibtop_get_cpu_l () at /usr/lib/x86_64-linux-gnu/libgtop-2.0.so.11
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker fuse kismet libvirt libvirtd lp lpadmin lxd 
mail mythtv netdev plugdev sambashare sbuild scanner sudo video

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

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

[Desktop-packages] [Bug 1735499] Re: [MIR] libblockdev

Here are a list of libblockdev's binary packages that depend on universe
packages that I think we don't need in main now.

libblockdev-plugins-all
libblockdev-btrfs2
libblockdev-btrfs-dev
libblockdev-crypto2
libblockdev-crypto-dev
libblockdev-kbd2
libblockdev-kbd-dev
libblockdev-lvm2
libblockdev-lvm-dev
libblockdev-mdraid2
libblockdev-mdraid-dev

crypto requires volume-key (LP: #1754422)
mdraid requires thin-provisioning-tools
btrfs, kbd, and mdraid requires libbytesize

I updated the supported seed so that these won't try to be automatically
pulled in.

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

Title:
  [MIR] libblockdev

Status in libblockdev package in Ubuntu:
  New
Status in udisks2 package in Ubuntu:
  New

Bug description:
  Availability
  
  Built for all supported architectures. In sync with Debian.

  Rationale
  =
  udisks2 2.7 uses the "libblockdev library for all low level storage 
management tasks instead of calling command line tools." libblockdev appears to 
have the same maintainers ("storaged project") as udisks2.

  It would be nice to have the new version to support GNOME Disks 3.26's new 
Resize and Repair features.
  http://pothos.blogsport.eu/2017/08/22/last-project-phase-and-3-26-features/

  There is some interest in dropping Gparted from the Ubuntu live ISO
  since it does not support Wayland and it still uses gtk2.

  Security
  
  No known security issues

  https://security-tracker.debian.org/tracker/source-package/libblockdev
  https://launchpad.net/ubuntu/+source/libblockdev/+cve

  Quality assurance
  =
  - Ubuntu Desktop bugs is the subscriber (although the Desktop Team thinks 
that Foundations should be responsible for udisks and friends)

  https://bugs.launchpad.net/ubuntu/+source/libblockdev
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libblockdev
  https://github.com/storaged-project/libblockdev/issues

  dh_auto_test is run but I guess it's not actually running the upstream test 
suite yet. (I think the upstream test suite needs to be run as autopkgtests)
  See http://storaged.org/libblockdev/ch03.html

  No autopkgtests

  Dependencies
  
  Debian's udisks2 recommends libblockdev-crypto2 which depends on the universe 
libvolume-key1 (source: volume-key)

  It might be ok to temporarily not recommend that plugin until the MIR for 
volume-key is approved. (LP: #1754422). (This was done in
  https://launchpad.net/ubuntu/+source/udisks2/2.7.6-2 )

  Some of the other plugins depend on libbytesize, but we don't need
  those plugins in main yet.

  Standards compliance
  
  4.1.1, debhelper compat 10, simple dh7 style rules

  Maintenance
  ===
  Maintained in Debian by the Debian Utopia team, which is a small team focused 
on cross-desktop freedesktop.org stuff.

  upstream:
  https://github.com/storaged-project/libblockdev

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

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

[Desktop-packages] [Bug 1754445] Re: gnome-shell crashed with SIGSEGV in cogl_object_unref() from iter_remove_or_steal() from g_hash_table_iter_remove() from st_texture_cache_evict_icons() from on_ico

Dropped importance to Low, because the stack trace suggests this crash
could only happen when changing the icon theme(?)

** Summary changed:

- gnome-shell crashed with SIGSEGV in cogl_object_unref()
+ gnome-shell crashed with SIGSEGV in cogl_object_unref() from 
iter_remove_or_steal() from g_hash_table_iter_remove() from 
st_texture_cache_evict_icons() from on_icon_theme_changed()

** Information type changed from Private to Public

** Changed in: gnome-shell (Ubuntu)
   Importance: Medium => Low

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

Title:
  gnome-shell crashed with SIGSEGV in cogl_object_unref() from
  iter_remove_or_steal() from g_hash_table_iter_remove() from
  st_texture_cache_evict_icons() from on_icon_theme_changed()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  i don´t know

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Mar  8 20:18:43 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f921c91b510 :mov
(%rdi),%rax
   PC (0x7f921c91b510) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   cogl_object_unref () from 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-2.so
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in cogl_object_unref()
  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/1754445/+subscriptions

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

[Desktop-packages] [Bug 1754537] [NEW] Scilab 5.5.2 cannot create Java Main Class on Ubuntu 14.04.

2018-03-08 Thread fabcap77

Public bug reported:

On March 5, after months of working regularly, Scilab 5.5.2 stopped
working altogether if launched from GUI.

Trying to launch from terminal, it still did not work but at least
informed me that it could not create a Java Main Class, and some more
details:

Exception in thread "main" java.lang.NullPointerException
at org.scilab.modules.gui.utils.ConfigManager.checkVersion(Unknown 
Source)
at org.scilab.modules.gui.utils.ConfigManager.createUserCopy(Unknown 
Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

Packages:
   OpenGL version string: 3.0 Mesa 10.1.3
   Scilab;  5.5.0-2
   libjogl2-ini;  2.1.5-1ubuntu3
   libjogl1-java;  2.1.5-1ubuntu3

Ubuntu 14.04.5 LTS Release: 14.04

A related bug is: https://bugs.launchpad.net/mesa/+bug/1742894, which
has been resolved for Ubuntu Xenial with a new version of libjogl2-java.
No such fix seems to be available for Trusty, however.

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

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

Title:
  Scilab 5.5.2 cannot create Java Main Class on Ubuntu 14.04.

Status in mesa package in Ubuntu:
  New

Bug description:
  On March 5, after months of working regularly, Scilab 5.5.2 stopped
  working altogether if launched from GUI.

  Trying to launch from terminal, it still did not work but at least
  informed me that it could not create a Java Main Class, and some more
  details:

  Exception in thread "main" java.lang.NullPointerException
at org.scilab.modules.gui.utils.ConfigManager.checkVersion(Unknown 
Source)
at org.scilab.modules.gui.utils.ConfigManager.createUserCopy(Unknown 
Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Packages:
 OpenGL version string: 3.0 Mesa 10.1.3
 Scilab;  5.5.0-2
 libjogl2-ini;  2.1.5-1ubuntu3
 libjogl1-java;  2.1.5-1ubuntu3

  Ubuntu 14.04.5 LTS Release: 14.04

  A related bug is: https://bugs.launchpad.net/mesa/+bug/1742894, which
  has been resolved for Ubuntu Xenial with a new version of
  libjogl2-java. No such fix seems to be available for Trusty, however.

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

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

[Desktop-packages] [Bug 1753884] Re: session logout after suspend

2018-03-08 Thread Christopher M. Penalver

Simon:

1) Regarding the crash files, it is best if one reports the crash files
as documented at https://help.ubuntu.com/community/ReportingBugs (not
attach them).

2) Regarding the crash files, could you please advise to their file
name(s)?

3) Regarding upgrading, if you do so and the problem is fixed, then that
is the best outcome, and doesn't cause anything negative to happen.


** Description changed:

- When I close the lid of my laptop, my session gets logged out, where I
- would expect the lock screen simply to come up.
+ Only when I have a second monitor plugged in, if I close the lid of my
+ laptop, my session gets logged out. What I'm expecting is the lock
+ screen comes up.
+ 
+ Sometimes (but not always) the second monitor will flash the "logged
+ out" screen for a second or two before going dim.
+ 
+ I have "Suspend even if external monitor is plugged in" enabled in Tweak
+ Tools.
+ 
+ WORKAROUND: Suspend via the GUI with the lid open.
+ 
+ WORKAROUND: Unplug the second monitor before closing the lid.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Mar  6 18:07:50 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2018-02-15 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 20AQ009HUS
  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.13.0-36-generic 
root=UUID=6f20d80f-81f4-40c1-aafd-95b2c5de55ed ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET78WW (2.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ009HUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET78WW(2.28):bd07/29/2014:svnLENOVO:pn20AQ009HUS:pvrThinkPadT440s:rvnLENOVO:rn20AQ009HUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20AQ009HUS
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

Title:
   session logout after suspend

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Only when I have a second monitor plugged in, if I close the lid of my
  laptop, my session gets logged out. What I'm expecting is the lock
  screen comes up.

  Sometimes (but not always) the second monitor will flash the "logged
  out" screen for a second or two before going dim.

  I have "Suspend even if external monitor is plugged in" enabled in
  Tweak Tools.

  WORKAROUND: Suspend via the GUI with the lid open.

  WORKAROUND: Unplug the second monitor before closing the lid.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Mar  6 18:07:50 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics

[Desktop-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!

2018-03-08 Thread Juan José Alca Machaca

I had the same problem however I don't have a Nvidia driver (Intel HD
Graphics instead)

I got this message before enter a loop:

video: version magic '3.13.0-143-generic SMP mod_unload modversions ' should be 
'3.13.0-143-generic SMP mod_unload modversions retpoline '
drm: version magic '3.13.0-143-generic SMP mod_unload modversions ' should be 
'3.13.0-143-generic SMP mod_unload modversions retpoline '

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04) by an insufficient compiler!

Status in gcc:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Desktop-packages] [Bug 1754477] Re: totem crashed with SIGSEGV in memcpy() from gen8_render_init() from i965_Init() from __vaDriverInit_1_0()

** Summary changed:

- totem crashed with SIGSEGV in memcpy()
+ totem crashed with SIGSEGV in memcpy() from gen8_render_init() from 
i965_Init() from __vaDriverInit_1_0()

** Information type changed from Private to Public

** Also affects: intel-vaapi-driver (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel-vaapi-driver (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  totem crashed with SIGSEGV in memcpy() from gen8_render_init() from
  i965_Init() from __vaDriverInit_1_0()

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  Just after starting up the ubuntu session.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu5
  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-communitheme:ubuntu:GNOME
  Date: Sun Mar  4 11:24:46 2018
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-02-23 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcCmdline: totem
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fe15ef8e696 <__memmove_sse2_unaligned_erms+374>:
movaps %xmm0,(%rdi)
   PC (0x7fe15ef8e696) ok
   source "%xmm0" ok
   destination "(%rdi)" (0x0010) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   __vaDriverInit_1_0 () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   ?? () from /usr/lib/x86_64-linux-gnu/libva.so.2
   vaInitialize () from /usr/lib/x86_64-linux-gnu/libva.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
  Title: totem crashed with SIGSEGV in __vaDriverInit_1_0()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XorgLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/Xorg.0.log'

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

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

[Desktop-packages] [Bug 1754491] Re: "Ubuntu on Wayland" string not translated anymore on Ubuntu 18.04

** Changed in: gdm3 (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  "Ubuntu on Wayland" string not translated anymore on Ubuntu 18.04

Status in gdm3 package in Ubuntu:
  New
Status in gnome-session package in Ubuntu:
  New

Bug description:
  It looks like that the "Ubuntu on Wayland" translation disappeared
  after some recent Ubuntu 18.04 update, although the string is fully
  translated on Launchpad.

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

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

[Desktop-packages] [Bug 1735499] Re: [MIR] libblockdev

** Description changed:

  Availability
  
  Built for all supported architectures. In sync with Debian.
  
  Rationale
  =
  udisks2 2.7 uses the "libblockdev library for all low level storage 
management tasks instead of calling command line tools." libblockdev appears to 
have the same maintainers ("storaged project") as udisks2.
  
  It would be nice to have the new version to support GNOME Disks 3.26's new 
Resize and Repair features.
  http://pothos.blogsport.eu/2017/08/22/last-project-phase-and-3-26-features/
  
  There is some interest in dropping Gparted from the Ubuntu live ISO
  since it does not support Wayland and it still uses gtk2.
  
  Security
  
  No known security issues
  
  https://security-tracker.debian.org/tracker/source-package/libblockdev
  https://launchpad.net/ubuntu/+source/libblockdev/+cve
  
  Quality assurance
  =
  - Ubuntu Desktop bugs is the subscriber (although the Desktop Team thinks 
that Foundations should be responsible for udisks and friends)
  
  https://bugs.launchpad.net/ubuntu/+source/libblockdev
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libblockdev
  https://github.com/storaged-project/libblockdev/issues
  
  dh_auto_test is run but I guess it's not actually running the upstream test 
suite yet. (I think the upstream test suite needs to be run as autopkgtests)
  See http://storaged.org/libblockdev/ch03.html
  
  No autopkgtests
  
  Dependencies
  
  Debian's udisks2 recommends libblockdev-crypto2 which depends on the universe 
libvolume-key1 (source: volume-key)
  
- It might be ok to temporarily not recommend that plugin until the MIR
- for volume-key is approved. (LP: #1754422)
+ It might be ok to temporarily not recommend that plugin until the MIR for 
volume-key is approved. (LP: #1754422). (This was done in
+ https://launchpad.net/ubuntu/+source/udisks2/2.7.6-2 )
  
  Some of the other plugins depend on libbytesize, but we don't need those
  plugins in main yet.
  
  Standards compliance
  
  4.1.1, debhelper compat 10, simple dh7 style rules
  
  Maintenance
  ===
  Maintained in Debian by the Debian Utopia team, which is a small team focused 
on cross-desktop freedesktop.org stuff.
  
  upstream:
  https://github.com/storaged-project/libblockdev

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

Title:
  [MIR] libblockdev

Status in libblockdev package in Ubuntu:
  New
Status in udisks2 package in Ubuntu:
  New

Bug description:
  Availability
  
  Built for all supported architectures. In sync with Debian.

  Rationale
  =
  udisks2 2.7 uses the "libblockdev library for all low level storage 
management tasks instead of calling command line tools." libblockdev appears to 
have the same maintainers ("storaged project") as udisks2.

  It would be nice to have the new version to support GNOME Disks 3.26's new 
Resize and Repair features.
  http://pothos.blogsport.eu/2017/08/22/last-project-phase-and-3-26-features/

  There is some interest in dropping Gparted from the Ubuntu live ISO
  since it does not support Wayland and it still uses gtk2.

  Security
  
  No known security issues

  https://security-tracker.debian.org/tracker/source-package/libblockdev
  https://launchpad.net/ubuntu/+source/libblockdev/+cve

  Quality assurance
  =
  - Ubuntu Desktop bugs is the subscriber (although the Desktop Team thinks 
that Foundations should be responsible for udisks and friends)

  https://bugs.launchpad.net/ubuntu/+source/libblockdev
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libblockdev
  https://github.com/storaged-project/libblockdev/issues

  dh_auto_test is run but I guess it's not actually running the upstream test 
suite yet. (I think the upstream test suite needs to be run as autopkgtests)
  See http://storaged.org/libblockdev/ch03.html

  No autopkgtests

  Dependencies
  
  Debian's udisks2 recommends libblockdev-crypto2 which depends on the universe 
libvolume-key1 (source: volume-key)

  It might be ok to temporarily not recommend that plugin until the MIR for 
volume-key is approved. (LP: #1754422). (This was done in
  https://launchpad.net/ubuntu/+source/udisks2/2.7.6-2 )

  Some of the other plugins depend on libbytesize, but we don't need
  those plugins in main yet.

  Standards compliance
  
  4.1.1, debhelper compat 10, simple dh7 style rules

  Maintenance
  ===
  Maintained in Debian by the Debian Utopia team, which is a small team focused 
on cross-desktop freedesktop.org stuff.

  upstream:
  https://github.com/storaged-project/libblockdev

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

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

[Desktop-packages] [Bug 1681513] Re: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue)

Ubuntu 17.04 reached End of Life in January 2018. Please upgrade to
Ubuntu 17.10 which is not affected by this bug.

Ubuntu releases and their End of Life dates can be found at
https://wiki.ubuntu.com/Releases

** Changed in: network-manager (Ubuntu Zesty)
   Status: Triaged => Won't Fix

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

Title:
  Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi
  adapters from working (MAC Address Randomization issue)

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Zesty:
  Won't Fix

Bug description:
  According to 
  
https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/
  there is a new privacy feature in the new version of NetworkManager.
  This privacy feature can cause some USB WiFi adapters to stop working
  while they used to work with older versions of NetworkManager (Ubuntu 16.10 
or older).

  The purpose of this privacy feature is to get your computer to report a new 
random MAC address whenever you connect to a WiFi network.
  This privacy feature is especially useful when you connect to public WiFi 
networks, so that the operators cannot identify you when you connect multiple 
times.

  The downside of this privacy feature is that some USB WiFi adapters misbehave 
when NetworkManager tries to change their MAC address repeatedly. 
  The result is that those USB WiFi adapters cannot connect anymore to the WiFi 
 network.

  Original report follows:

  My Panda USB wi-fi adapter works just fine on 16.10, but when I try to
  connect to my wi-fi router in 17.04, GNOME network manager reports
  "Connection failed." I did some tinkering, and noticed that my MAC
  address for my wifi adapter, according to GNOME, is DIFFERENT every
  time I make it forget my wifi settings and try to reconnect. Weird,
  right? Any leads on a possible fix or work-around?

  I'm running the latest beta of Ubuntu GNOME 17.04, kernel
  4.10.0-19-generic, GNOME 3.24.0.

  https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-
  networkmanager-1-4-0/

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

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

[Desktop-packages] [Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

2018-03-08 Thread herrtimson

Which is the bug id for the mentioned skia bug?

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

Bug description:
  Firefox always crashes when launched after the 55.0.1 update on an
  Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi),
  even in safe mode.

  I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for
  ARM single-board computer) on a similar board (Orange Pi Plus 2e),
  installed Firefox and experienced the same problem--it won't load
  without crashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 55.0.1+build2-0ubuntu0.16.04.2
  Uname: Linux 3.4.113-sun8i armv7l
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: armhf
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jim1138 F pulseaudio
   /dev/snd/controlC0:  jim1138 F pulseaudio
  BuildID: 20170814194718
  Card0.Amixer.info:
   Card hw:0 'audiocodec'/'audiocodec'
 Mixer name : ''
 Components : ''
 Controls  : 12
 Simple ctrls  : 12
  Card1.Amixer.info:
   Card hw:1 'sndhdmi'/'sndhdmi'
 Mixer name : ''
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'hdmi audio format Function',0
 Capabilities: enum
 Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' 
'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO'
 Item0: 'pcm'
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Thu Aug 17 05:37:00 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.10.1 dev eth0 
   default via 192.168.10.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.10.0/24 dev eth0  proto kernel  scope link  src 192.168.10.107 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.108  
metric 600
  Locales: extensions.sqlite corrupt or missing
  PciMultimedia:
   
  PciNetwork:
   
  Profiles: Profile0 (Default) - LastVersion=55.0.1/20170814194718
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1754523] Re: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow() Backups randomly crashes always

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

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 #1751460, 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/1754523/+attachment/5073830/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::<lambda()>::operator()

** 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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1754523

Title:
  deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  Backups randomly crashes always

Status in deja-dup package in Ubuntu:
  New

Bug description:
  The backups app randomly crashes

  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
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 18:07:52 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2018-03-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f547f36b0b8:movl   $0x0,(%rax)
   PC (0x7f547f36b0b8) 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=0x7f547f5d202c, 
init_routine=0x7f547664a490 <__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<bmalloc::PerHeapKind >::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: 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/deja-dup/+bug/1754523/+subscriptions

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

[Desktop-packages] [Bug 1754510] Re: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

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

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 #1751460, 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/1754510/+attachment/5073763/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

** 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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1754510

Title:
  deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

Status in deja-dup package in Ubuntu:
  New

Bug description:
  This error always occurs when you start the system.

  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: ubuntu:GNOME
  Date: Thu Mar  8 20:09:13 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-11-12 (116 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171109)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  SegvAnalysis:
   Segfault happened at: 0x7f1d135c20b8:movl   $0x0,(%rax)
   PC (0x7f1d135c20b8) 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=0x7f1d1382902c, 
init_routine=0x7f1d0a8a1490 <__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: 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/deja-dup/+bug/1754510/+subscriptions

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

[Desktop-packages] [Bug 1720685] Re: nautilus crashed with SIGSEGV in gtk_stack_set_visible_child_name()

2018-03-08 Thread Matt Zilmer

Similar to earlier-reported.  The server went down while this client was
using it, which may be a different circumstance.

z

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

Title:
  nautilus crashed with SIGSEGV in gtk_stack_set_visible_child_name()

Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Was simply trying to attach to a remote server over SSH using the UI
  when nautilus crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  1 16:41:40 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2016-07-06 (452 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f9f5bf562c7 :   
mov0x30(%rdi,%rax,1),%edx
   PC (0x7f9f5bf562c7) ok
   source "0x30(%rdi,%rax,1)" (0xfe80) not located in a known VMA 
region (needed readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   gtk_stack_set_visible_child_name () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic_va () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in gtk_stack_set_visible_child_name()
  UpgradeStatus: Upgraded to artful on 2017-10-01 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~desktop-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: deja-dup-monitor crashed with SIGSEGV in Gigacage::<lambda()>::operator()

2018-03-08 Thread Brian Murray

** Tags removed: bugpattern-needed

** Tags added: bugpattern-written

-- 
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:
  deja-dup-monitor crashed with SIGSEGV in
  Gigacage::::operator()

Status in WebKit:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed
Status in deja-dup source package in Bionic:
  Confirmed
Status in webkit2gtk source package in Bionic:
  Confirmed

Bug description:
  not sure. upgraded to 18.10.

  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/webkit-open-source/+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 1754520] Re: gnome-control-center crashed while changing dock icons size

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

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 #1723249, 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/1754520/+attachment/5073815/+files/CoreDump.gz

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

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

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

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

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

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

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

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

Title:
  gnome-control-center crashed while changing dock icons size

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

Bug description:
  dragging slider to the right for smaller icons resulted in crash

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.26.2-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 17:55:55 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-03-07 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  ProcCmdline: gnome-control-center -s power
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x55b6ffacdf85:cmpb   $0x0,(%rbx)
   PC (0x55b6ffacdf85) ok
   source "$0x0" ok
   destination "(%rbx)" (0x4002) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev postgres sambashare sudo vboxusers

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

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

[Desktop-packages] [Bug 1754506] [NEW] AutoFS does not automatically umount SMB shares

2018-03-08 Thread Alexander Lochmann

Public bug reported:

Description:Ubuntu 17.10
Release:17.10

autofs:
  Installed: 5.1.2-1ubuntu1
  Candidate: 5.1.2-1ubuntu1
  Version table:
 *** 5.1.2-1ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status

Kernel: self-built 4.15.6

What I expect:
I expect AutoFS to automatically unmount my samba share after the timeout. 
However, it does not. The share is still mounted.
I've turned the autofs debug output in the kernel module. As far as I can tell, 
the kernel thinks the cifs mount is still busy.

I'm using the smb automount script provided by the package: /etc/auto.smb. I've 
just added an additional cifs parameter(vers=2.0).
My auto.master looks as follows:
/media/smb/  program:/etc/auto.smb

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

** Attachment added: "autofs.conf"
   
https://bugs.launchpad.net/bugs/1754506/+attachment/5073761/+files/autofs.conf

** Description changed:

  Description:Ubuntu 17.10
  Release:17.10
  
  autofs:
-   Installed: 5.1.2-1ubuntu1
-   Candidate: 5.1.2-1ubuntu1
-   Version table:
-  *** 5.1.2-1ubuntu1 500
- 500 http://de.archive.ubuntu.com/ubuntu artful/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 5.1.2-1ubuntu1
+   Candidate: 5.1.2-1ubuntu1
+   Version table:
+  *** 5.1.2-1ubuntu1 500
+ 500 http://de.archive.ubuntu.com/ubuntu artful/main amd64 Packages
+ 100 /var/lib/dpkg/status
+ 
+ Kernel: self-built 4.15.6
  
  What I expect:
- I expect AutoFS to automatically unmount my samba share after the timeout. 
However, it does not.
- The share is still mounted.
+ I expect AutoFS to automatically unmount my samba share after the timeout. 
However, it does not. The share is still mounted.
+ I've turned the autofs debug output in the kernel module. As far as I can 
tell, the kernel thinks the cifs mount is still busy.
  
  I'm using the smb automount script provided by the package: /etc/auto.smb. 
I've just added an additional cifs parameter(vers=2.0).
  My auto.master looks as follows:
  /media/smb/  program:/etc/auto.smb

** Package changed: libreoffice (Ubuntu) => autofs (Ubuntu)

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

Title:
  AutoFS does not automatically umount SMB shares

Status in autofs package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 17.10
  Release:17.10

  autofs:
    Installed: 5.1.2-1ubuntu1
    Candidate: 5.1.2-1ubuntu1
    Version table:
   *** 5.1.2-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  Kernel: self-built 4.15.6

  What I expect:
  I expect AutoFS to automatically unmount my samba share after the timeout. 
However, it does not. The share is still mounted.
  I've turned the autofs debug output in the kernel module. As far as I can 
tell, the kernel thinks the cifs mount is still busy.

  I'm using the smb automount script provided by the package: /etc/auto.smb. 
I've just added an additional cifs parameter(vers=2.0).
  My auto.master looks as follows:
  /media/smb/  program:/etc/auto.smb

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

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

[Desktop-packages] [Bug 1754491] [NEW] "Ubuntu on Wayland" string not translated anymore on Ubuntu 18.04

2018-03-08 Thread AsciiWolf

Public bug reported:

It looks like that the "Ubuntu on Wayland" translation disappeared after
some recent Ubuntu 18.04 update, although the string is fully translated
on Launchpad.

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

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


** Tags: bionic l10n

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

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

Title:
  "Ubuntu on Wayland" string not translated anymore on Ubuntu 18.04

Status in gdm3 package in Ubuntu:
  New
Status in gnome-session package in Ubuntu:
  New

Bug description:
  It looks like that the "Ubuntu on Wayland" translation disappeared
  after some recent Ubuntu 18.04 update, although the string is fully
  translated on Launchpad.

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

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

[Desktop-packages] [Bug 1754485] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

** Tags removed: need-duplicate-check

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I just updated my video drivers (nvidia 340), when i rebooted i got
  this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sat Mar  3 11:41:01 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-9SXQB5/51-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-02-26 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1754485] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o

2018-03-08 Thread Greg Munker

Public bug reported:

I just updated my video drivers (nvidia 340), when i rebooted i got this
error.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Sat Mar  3 11:41:01 2018
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-9SXQB5/51-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2018-02-26 (10 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful package-conflict

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I just updated my video drivers (nvidia 340), when i rebooted i got
  this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sat Mar  3 11:41:01 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-9SXQB5/51-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-02-26 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1752299] Re: [RFE] Show snaps in "Recent Releases"

2018-03-08 Thread AsciiWolf

Upstream bug report: https://gitlab.gnome.org/GNOME/gnome-
software/issues/314

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

Title:
  [RFE] Show snaps in "Recent Releases"

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Currently, there are no snap packages shown in the "Recent Releases"
  section in GNOME Software. Consider fixing this.

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

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

[Desktop-packages] [Bug 1754483] Re: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

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

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 #1751460, 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/1754483/+attachment/5073676/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::<lambda()>::operator()

** 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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1754483

Title:
  deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

Status in deja-dup package in Ubuntu:
  New

Bug description:
  deja-dup-monitor crashes a few minutes after booting from Live USB.
  Crashes reliably after each boot.

  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
  CasperVersion: 1.389
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 21:59:20 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f9c632d5588:movl   $0x0,(%rax)
   PC (0x7f9c632d5588) 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=0x7f9c6353d02c, 
init_routine=0x7f9c5a392490 <__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<bmalloc::PerHeapKind >::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: 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/deja-dup/+bug/1754483/+subscriptions

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

[Desktop-packages] [Bug 1754482] Re: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

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

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 #1751460, 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/1754482/+attachment/5073666/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

** 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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1754482

Title:
  deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

Status in deja-dup package in Ubuntu:
  New

Bug description:
  U18.04

  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
  CurrentDesktop: XFCE
  Date: Thu Mar  8 22:47:36 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2018-02-08 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180207)
  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: 0x7fac16ba50b8:movl   $0x0,(%rax)
   PC (0x7fac16ba50b8) 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=0x7fac16e0c02c, 
init_routine=0x7fac0dc49490 <__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: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev 
sambashare scanner sudo tape video

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

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

[Desktop-packages] [Bug 1754156] Re: Screen unlocking without password

2018-03-08 Thread pumpkinbeer

** Information type changed from Private Security to Public Security

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

Title:
  Screen unlocking without password

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  My screen is unlocking without a password after being locked for an
  unknown time period, like a lunch break or overnight.  It is not
  hibernating or suspending, just locked.  If I lock it and immediately
  unlock it forces me to use password as it should, otherwise about 40%
  of the time it just unlocks to my full session as I left it before
  locking.  I lock by physically clicking the lock icon in the top right
  of the screen.  I've not tested by just walking away and waiting.

  I originally posted here
  https://askubuntu.com/questions/1012420/ubuntu-17-10-major-security-
  issue-at-login?noredirect=1#comment1641885_1012420 if that helps.

  Let me know other info you need to help find a fix.  This is a major
  security issue for me at my location.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-screensaver 3.6.1-7ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  7 15:16:15 2018
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 300
  InstallationDate: Installed on 2018-03-01 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1754169] Re: [Bionic] [wayland] Nautilus crashes when a file is opened with gedit

2018-03-08 Thread amano

It just happens in the Ubuntu-Wayland session. It doesn't happen in the
default Ubuntu session. Added the wayland tag.

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

Title:
  [Bionic] [wayland] Nautilus crashes when a file is opened with gedit

Status in gedit package in Ubuntu:
  Invalid
Status in nautilus package in Ubuntu:
  New

Bug description:
  See title.

  ==Steps to reproduce==
  0) From the log in screen, click your name, then click the gear button and 
select Ubuntu on Wayland. Log in.
  1) Open nautilus (currently 3.26.2 in bionic)
  2) Browse to a location with a textfile (eg. /home/user/.thunderbird )
  3) Right click a textfile (eg. profiles.ini)
  4) Choose gedit from the list (probably default), click ok.
  5) Nautilus crashes, gedit doesn't come up

  ==Expected result==
  Nautilus doesn't crash, gedit comes up and lets you edit the file

  ==Why (probably) a gedit regression==
  When choosing LibreOffice Nautilus doesn't crash and LibreOffice opens the 
file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gedit 3.27.92-1ubuntu1
  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-communitheme:ubuntu:GNOME
  Date: Wed Mar  7 22:13:00 2018
  InstallationDate: Installed on 2018-02-23 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1754458] [NEW] applet symbol not displayed on mate (18.04)

2018-03-08 Thread Michael

Public bug reported:

After upgrading to Ubuntu 18.04, the network manager applet symbol isn't
displayed any longer. The other functionality (asking for credentials)
is working. I also see other symbols.


aptitude show network-manager-gnome
Paket: network-manager-gnome
Version: 1.8.10-2ubuntu1
Neu: ja
Zustand: Installiert


stdout/stderr:
Gtk-Message: 21:28:14.411: Failed to load module "appmenu-gtk-module"
Gtk-Message: 21:28:14.431: Failed to load module "topmenu-gtk-module"
Gtk-Message: 21:28:14.431: Failed to load module "appmenu-gtk-module"
Gtk-Message: 21:28:14.432: Failed to load module "topmenu-gtk-module"

** (nm-applet:29524): WARNING **: 21:28:14.668: Couldn't register with
accessibility bus: Did not receive a reply. Possible causes include: the
remote application did not send a reply, the message bus security policy
blocked the reply, the reply timeout expired, or the network connection
was broken.

(nm-applet:29524): nm-applet-WARNING **: 21:28:15.987: Cannot grab
information for modem at /org/freedesktop/ModemManager1/Modem/6: No
ModemManager support

(nm-applet:29524): nm-applet-WARNING **: 21:28:16.124: ModemManager is
not available for modem at /org/freedesktop/ModemManager1/Modem/6

(nm-applet:29524): Gtk-WARNING **: 21:28:16.127: Can't set a parent on
widget which has a parent

(nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy:
assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy:
assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:29524): Gtk-WARNING **: 21:28:16.171: Can't set a parent on
widget which has a parent

(nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy:
assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy:
assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:29524): Gtk-WARNING **: 21:28:21.570: Can't set a parent on
widget which has a parent

(nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy:
assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy:
assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:29524): Gtk-WARNING **: 21:28:24.655: Can't set a parent on
widget which has a parent

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager-gnome 1.8.10-2ubuntu1
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: MATE
Date: Thu Mar  8 21:27:56 2018
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
WpaSupplicantLog:
 
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.10.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager-applet (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 network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1754458

Title:
  applet symbol not displayed on mate (18.04)

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

Bug description:
  After upgrading to Ubuntu 18.04, the network manager applet symbol
  isn't displayed any longer. The other functionality (asking for
  credentials) is working. I also see other symbols.

  
  aptitude show network-manager-gnome
  Paket: network-manager-gnome
  Version: 1.8.10-2ubuntu1
  Neu: ja
  Zustand: Installiert

  
  stdout/stderr:
  Gtk-Message: 21:28:14.411: Failed to load module "appmenu-gtk-module"
  Gtk-Message: 21:28:14.431: Failed to load module "topmenu-gtk-module"
  Gtk-Message: 21:28:14.431: Failed to load module "appmenu-gtk-module"
  Gtk-Message: 21:28:14.432: Failed to load module "topmenu-gtk-module"

  ** (nm-applet:29524): WARNING **: 21:28:14.668: Couldn't register with
  accessibility bus: Did not receive a reply. Possible causes include:
  the remote application did not send a reply, the message bus security
  policy blocked the reply, the reply timeout expired, or the network
  connection was broken.

  (nm-applet:29524): nm-applet-WARNING **: 21:28:15.987: Cannot grab
  information for modem at /org/freedesktop/ModemManager1/Modem/6: No
  ModemManager support

  (nm-applet:29524): nm-applet-WARNING **: 21:28:16.124: ModemManager is
  not available for modem at /org/freedesktop/ModemManager1/Modem/6

  (nm-applet:29524): Gtk-WARNING **: 21:28:16.127: Can't set a parent on
  widget which has a parent

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-CRITICAL **:

[Desktop-packages] [Bug 1754436] Re: evolution-addressbook-factory-subprocess crashed with SIGABRT in std::terminate()

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

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 #1724277, 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/1754436/+attachment/5073332/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1754436

Title:
  evolution-addressbook-factory-subprocess crashed with SIGABRT in
  std::terminate()

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: evolution-data-server 3.27.90-1ubuntu1
  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: Thu Mar  8 19:33:23 2018
  ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory-subprocess
  InstallationDate: Installed on 2017-07-14 (237 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory-subprocess 
--factory google --bus-name 
org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx1921x3 --own-path 
/org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/1921/3
  ProcEnviron:
   LANG=da_DK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: evolution-data-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   operator new(unsigned long) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: evolution-addressbook-factory-subprocess crashed with SIGABRT in 
std::terminate()
  UpgradeStatus: Upgraded to bionic on 2018-03-08 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1754437] 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/1754437/+attachment/5073342/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1754437/+attachment/5073351/+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/1754437

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  gui interface remains working only see the error on the gui popup

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  Uname: Linux 4.15.7-041507-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Mar  8 11:06:30 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-06 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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
   _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () 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/1754437/+subscriptions

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

[Desktop-packages] [Bug 1754425] Re: 18.04 3.27 Gnome-shell Near-Fatalities

** This bug is no longer a duplicate of bug 1753776
   Graphics corruption in login animation to Xorg sessions

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

Title:
  18.04 3.27 Gnome-shell Near-Fatalities

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  It's impossible to make a normal bug report, so here's the best I can
  describe:

  EVERY login to gnome, there is a moment after I enter my password and
  press return, where whole screen goes small-resolution (cursor small,
  all text and boxes get smaller), and best way to describe it is
  "colorful static" pattern replaces the purple/black. After this
  hiccup, a moment of black, then taken to the gnome desktop. Things
  work fine.

  If I close the lid, it seems that the computer flat-out doesn't wake
  up. HOWEVER, if I wait patiently more than 20 seconds, and press (not
  hold) the power button, SOMETIMES, the computer will "snap out of it"
  and come back to my desktop. Although RAM is 25% used, and CPU usage
  is around 25-50% or less (depending on apps), mouse will regularly
  freeze up for some seconds every 10 seconds or so. Wifi will claim to
  be "on", but there aren't any networks in the "select network"
  dialogue. Turning wifi off and then on does not fix this problem. So
  I'll be in this terrifying state of non-responsive every few seconds
  computer, with no ability to reconnect to networks and report bug.

  I force restart. The first restart, upon login, will hang indefinitely
  on a purple screen with the cursor in the middle. I will have to force
  restart again. Upon 2nd restart, it will boot "normally", in that
  after I login, I get the "familiar" "colorful static" splash screen
  before being taken to normal functional gnome desktop experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 12:38:24 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-02 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1245666] Re: Pidgin is creating zombies

2018-03-08 Thread LocutusOfBorg

Hello, thanks! I removed the patch and uploaded the package!

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

Title:
  Pidgin is creating zombies

Status in Pidgin:
  Unknown
Status in pidgin package in Ubuntu:
  Confirmed
Status in pidgin package in Fedora:
  Won't Fix

Bug description:
  After upgrading to Kubuntu 13.10 pidgin is constantly creating new
  zombies.

  E.g. after an uptime of roughly 4 hours:
  $ ps aux | grep Z
  USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
  cm2589  0.0  0.0  0 0 ?Z17:46   0:00 [pidgin] 

  cm3045  0.0  0.0  0 0 ?Z17:47   0:00 [pidgin] 

  cm3106  0.0  0.0  0 0 ?Z17:48   0:00 [pidgin] 

  cm3236  0.0  0.0  0 0 ?Z17:50   0:00 [pidgin] 

  cm5760  0.0  0.0  0 0 ?Z17:54   0:00 [pidgin] 

  cm5788  0.0  0.0  0 0 ?Z18:02   0:00 [pidgin] 

  cm6405  0.0  0.0  0 0 ?Z18:12   0:00 [pidgin] 

  cm6501  0.0  0.0  0 0 ?Z18:22   0:00 [pidgin] 

  cm6519  0.0  0.0  0 0 ?Z18:32   0:00 [pidgin] 

  cm6543  0.0  0.0  0 0 ?Z18:42   0:00 [pidgin] 

  cm6580  0.0  0.0  0 0 ?Z18:52   0:00 [pidgin] 

  cm6619  0.0  0.0  0 0 ?Z19:02   0:00 [pidgin] 

  cm6645  0.0  0.0  0 0 ?Z19:12   0:00 [pidgin] 

  cm6672  0.0  0.0  0 0 ?Z19:22   0:00 [pidgin] 

  cm6691  0.0  0.0  0 0 ?Z19:32   0:00 [pidgin] 

  cm6757  0.0  0.0  0 0 ?Z19:42   0:00 [pidgin] 

  cm6846  0.0  0.0  0 0 ?Z19:52   0:00 [pidgin] 

  cm6869  0.0  0.0  0 0 ?Z20:01   0:00 [pidgin] 

  cm6889  0.0  0.0  0 0 ?Z20:11   0:00 [pidgin] 

  cm6914  0.0  0.0  0 0 ?Z20:21   0:00 [pidgin] 

  cm6931  0.0  0.0  0 0 ?Z20:31   0:00 [pidgin] 

  cm6948  0.0  0.0  0 0 ?Z20:41   0:00 [pidgin] 

  cm6972  0.0  0.0  0 0 ?Z20:51   0:00 [pidgin] 

  cm6992  0.0  0.0  0 0 ?Z21:01   0:00 [pidgin] 

  cm7015  0.0  0.0  0 0 ?Z21:11   0:00 [pidgin] 

  cm7036  0.0  0.0  0 0 ?Z21:20   0:00 [pidgin] 

  cm7121  0.0  0.0  0 0 ?Z21:30   0:00 [pidgin] 

  cm7223  0.0  0.0  10984   940 pts/0S+   21:38   0:00 grep 
--color=auto Z

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

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

[Desktop-packages] [Bug 1754425] Re: 18.04 3.27 Gnome-shell Near-Fatalities

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

Thanks Jeremy. That bug definitely describes the normal login behavior I
see. However, the main part of this bug is strange behavior after
closing the lid, and the failed first restart freezing on purple screen.

So, while part of this bug report is duplicate, part of it is not (so
far as I know).

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

Title:
  18.04 3.27 Gnome-shell Near-Fatalities

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  It's impossible to make a normal bug report, so here's the best I can
  describe:

  EVERY login to gnome, there is a moment after I enter my password and
  press return, where whole screen goes small-resolution (cursor small,
  all text and boxes get smaller), and best way to describe it is
  "colorful static" pattern replaces the purple/black. After this
  hiccup, a moment of black, then taken to the gnome desktop. Things
  work fine.

  If I close the lid, it seems that the computer flat-out doesn't wake
  up. HOWEVER, if I wait patiently more than 20 seconds, and press (not
  hold) the power button, SOMETIMES, the computer will "snap out of it"
  and come back to my desktop. Although RAM is 25% used, and CPU usage
  is around 25-50% or less (depending on apps), mouse will regularly
  freeze up for some seconds every 10 seconds or so. Wifi will claim to
  be "on", but there aren't any networks in the "select network"
  dialogue. Turning wifi off and then on does not fix this problem. So
  I'll be in this terrifying state of non-responsive every few seconds
  computer, with no ability to reconnect to networks and report bug.

  I force restart. The first restart, upon login, will hang indefinitely
  on a purple screen with the cursor in the middle. I will have to force
  restart again. Upon 2nd restart, it will boot "normally", in that
  after I login, I get the "familiar" "colorful static" splash screen
  before being taken to normal functional gnome desktop experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 12:38:24 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-02 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1754425] Re: 18.04 3.27 Gnome-shell Near-Fatalities

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

Thank you for taking the time to report this bug. This bug has already
been reported as #1753776 so I am marking it a duplicate.

** This bug has been marked a duplicate of bug 1753776
   Graphics corruption in login animation to Xorg sessions

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

Title:
  18.04 3.27 Gnome-shell Near-Fatalities

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  It's impossible to make a normal bug report, so here's the best I can
  describe:

  EVERY login to gnome, there is a moment after I enter my password and
  press return, where whole screen goes small-resolution (cursor small,
  all text and boxes get smaller), and best way to describe it is
  "colorful static" pattern replaces the purple/black. After this
  hiccup, a moment of black, then taken to the gnome desktop. Things
  work fine.

  If I close the lid, it seems that the computer flat-out doesn't wake
  up. HOWEVER, if I wait patiently more than 20 seconds, and press (not
  hold) the power button, SOMETIMES, the computer will "snap out of it"
  and come back to my desktop. Although RAM is 25% used, and CPU usage
  is around 25-50% or less (depending on apps), mouse will regularly
  freeze up for some seconds every 10 seconds or so. Wifi will claim to
  be "on", but there aren't any networks in the "select network"
  dialogue. Turning wifi off and then on does not fix this problem. So
  I'll be in this terrifying state of non-responsive every few seconds
  computer, with no ability to reconnect to networks and report bug.

  I force restart. The first restart, upon login, will hang indefinitely
  on a purple screen with the cursor in the middle. I will have to force
  restart again. Upon 2nd restart, it will boot "normally", in that
  after I login, I get the "familiar" "colorful static" splash screen
  before being taken to normal functional gnome desktop experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 12:38:24 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-02 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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 in login animation to Xorg sessions

** Tags added: rls-bb-incoming

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

Title:
  Graphics corruption in login animation to Xorg sessions

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

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
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2018-03-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
   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.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=9a36b498-59f5-4a36-81db-3046ff6bdeaa ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  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.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2: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.90-1

[Desktop-packages] [Bug 1735499] Re: [MIR] libblockdev

** Description changed:

  Availability
  
  Built for all supported architectures. In sync with Debian.
  
  Rationale
  =
  udisks2 2.7 uses the "libblockdev library for all low level storage 
management tasks instead of calling command line tools." libblockdev appears to 
have the same maintainers ("storaged project") as udisks2.
  
  It would be nice to have the new version to support GNOME Disks 3.26's new 
Resize and Repair features.
  http://pothos.blogsport.eu/2017/08/22/last-project-phase-and-3-26-features/
  
  There is some interest in dropping Gparted from the Ubuntu live ISO
  since it does not support Wayland and it still uses gtk2.
  
  Security
  
  No known security issues
  
  https://security-tracker.debian.org/tracker/source-package/libblockdev
  https://launchpad.net/ubuntu/+source/libblockdev/+cve
  
  Quality assurance
  =
  - Ubuntu Desktop bugs is the subscriber (although the Desktop Team thinks 
that Foundations should be responsible for udisks and friends)
  
  https://bugs.launchpad.net/ubuntu/+source/libblockdev
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libblockdev
  https://github.com/storaged-project/libblockdev/issues
  
  dh_auto_test is run but I guess it's not actually running the upstream test 
suite yet. (I think the upstream test suite needs to be run as autopkgtests)
  See http://storaged.org/libblockdev/ch03.html
  
  No autopkgtests
  
  Dependencies
  
  Debian's udisks2 recommends libblockdev-crypto2 which depends on the universe 
libvolume-key1 (source: volume-key)
  
- It might be ok to temporarily not recommend that plugin until a MIR for
- volume-key is filed and approved.
+ It might be ok to temporarily not recommend that plugin until the MIR
+ for volume-key is approved. (LP: #1754422)
  
  Standards compliance
  
  4.1.1, debhelper compat 10, simple dh7 style rules
  
  Maintenance
  ===
  Maintained in Debian by the Debian Utopia team, which is a small team focused 
on cross-desktop freedesktop.org stuff.
  
  upstream:
  https://github.com/storaged-project/libblockdev

** Description changed:

  Availability
  
  Built for all supported architectures. In sync with Debian.
  
  Rationale
  =
  udisks2 2.7 uses the "libblockdev library for all low level storage 
management tasks instead of calling command line tools." libblockdev appears to 
have the same maintainers ("storaged project") as udisks2.
  
  It would be nice to have the new version to support GNOME Disks 3.26's new 
Resize and Repair features.
  http://pothos.blogsport.eu/2017/08/22/last-project-phase-and-3-26-features/
  
  There is some interest in dropping Gparted from the Ubuntu live ISO
  since it does not support Wayland and it still uses gtk2.
  
  Security
  
  No known security issues
  
  https://security-tracker.debian.org/tracker/source-package/libblockdev
  https://launchpad.net/ubuntu/+source/libblockdev/+cve
  
  Quality assurance
  =
  - Ubuntu Desktop bugs is the subscriber (although the Desktop Team thinks 
that Foundations should be responsible for udisks and friends)
  
  https://bugs.launchpad.net/ubuntu/+source/libblockdev
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libblockdev
  https://github.com/storaged-project/libblockdev/issues
  
  dh_auto_test is run but I guess it's not actually running the upstream test 
suite yet. (I think the upstream test suite needs to be run as autopkgtests)
  See http://storaged.org/libblockdev/ch03.html
  
  No autopkgtests
  
  Dependencies
  
  Debian's udisks2 recommends libblockdev-crypto2 which depends on the universe 
libvolume-key1 (source: volume-key)
  
  It might be ok to temporarily not recommend that plugin until the MIR
  for volume-key is approved. (LP: #1754422)
  
+ Some of the other plugins depend on libbytesize, but we don't need those
+ plugins in main yet.
+ 
  Standards compliance
  
  4.1.1, debhelper compat 10, simple dh7 style rules
  
  Maintenance
  ===
  Maintained in Debian by the Debian Utopia team, which is a small team focused 
on cross-desktop freedesktop.org stuff.
  
  upstream:
  https://github.com/storaged-project/libblockdev

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

Title:
  [MIR] libblockdev

Status in libblockdev package in Ubuntu:
  New
Status in udisks2 package in Ubuntu:
  New

Bug description:
  Availability
  
  Built for all supported architectures. In sync with Debian.

  Rationale
  =
  udisks2 2.7 uses the "libblockdev library for all low level storage 
management tasks instead of calling command line tools." libblockdev appears to 
have the same maintainers ("storaged project") as udisks2.

  It would be nice to have the new version to support GNOME Disks 3.26's

[Desktop-packages] [Bug 1754425] Re: 18.04 3.27 Gnome-shell Near-Fatalities

The colorful static looks like this, but colorful:
https://i.stack.imgur.com/GQQxy.jpg

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

Title:
  18.04 3.27 Gnome-shell Near-Fatalities

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  It's impossible to make a normal bug report, so here's the best I can
  describe:

  EVERY login to gnome, there is a moment after I enter my password and
  press return, where whole screen goes small-resolution (cursor small,
  all text and boxes get smaller), and best way to describe it is
  "colorful static" pattern replaces the purple/black. After this
  hiccup, a moment of black, then taken to the gnome desktop. Things
  work fine.

  If I close the lid, it seems that the computer flat-out doesn't wake
  up. HOWEVER, if I wait patiently more than 20 seconds, and press (not
  hold) the power button, SOMETIMES, the computer will "snap out of it"
  and come back to my desktop. Although RAM is 25% used, and CPU usage
  is around 25-50% or less (depending on apps), mouse will regularly
  freeze up for some seconds every 10 seconds or so. Wifi will claim to
  be "on", but there aren't any networks in the "select network"
  dialogue. Turning wifi off and then on does not fix this problem. So
  I'll be in this terrifying state of non-responsive every few seconds
  computer, with no ability to reconnect to networks and report bug.

  I force restart. The first restart, upon login, will hang indefinitely
  on a purple screen with the cursor in the middle. I will have to force
  restart again. Upon 2nd restart, it will boot "normally", in that
  after I login, I get the "familiar" "colorful static" splash screen
  before being taken to normal functional gnome desktop experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 12:38:24 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-02 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1754425] [NEW] 18.04 3.27 Gnome-shell Near-Fatalities

Public bug reported:

It's impossible to make a normal bug report, so here's the best I can
describe:

EVERY login to gnome, there is a moment after I enter my password and
press return, where whole screen goes small-resolution (cursor small,
all text and boxes get smaller), and best way to describe it is
"colorful static" pattern replaces the purple/black. After this hiccup,
a moment of black, then taken to the gnome desktop. Things work fine.

If I close the lid, it seems that the computer flat-out doesn't wake up.
HOWEVER, if I wait patiently more than 20 seconds, and press (not hold)
the power button, SOMETIMES, the computer will "snap out of it" and come
back to my desktop. Although RAM is 25% used, and CPU usage is around
25-50% or less (depending on apps), mouse will regularly freeze up for
some seconds every 10 seconds or so. Wifi will claim to be "on", but
there aren't any networks in the "select network" dialogue. Turning wifi
off and then on does not fix this problem. So I'll be in this terrifying
state of non-responsive every few seconds computer, with no ability to
reconnect to networks and report bug.

I force restart. The first restart, upon login, will hang indefinitely
on a purple screen with the cursor in the middle. I will have to force
restart again. Upon 2nd restart, it will boot "normally", in that after
I login, I get the "familiar" "colorful static" splash screen before
being taken to normal functional gnome desktop experience.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.27.92-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar  8 12:38:24 2018
DisplayManager: gdm3
InstallationDate: Installed on 2018-03-02 (5 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  18.04 3.27 Gnome-shell Near-Fatalities

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  It's impossible to make a normal bug report, so here's the best I can
  describe:

  EVERY login to gnome, there is a moment after I enter my password and
  press return, where whole screen goes small-resolution (cursor small,
  all text and boxes get smaller), and best way to describe it is
  "colorful static" pattern replaces the purple/black. After this
  hiccup, a moment of black, then taken to the gnome desktop. Things
  work fine.

  If I close the lid, it seems that the computer flat-out doesn't wake
  up. HOWEVER, if I wait patiently more than 20 seconds, and press (not
  hold) the power button, SOMETIMES, the computer will "snap out of it"
  and come back to my desktop. Although RAM is 25% used, and CPU usage
  is around 25-50% or less (depending on apps), mouse will regularly
  freeze up for some seconds every 10 seconds or so. Wifi will claim to
  be "on", but there aren't any networks in the "select network"
  dialogue. Turning wifi off and then on does not fix this problem. So
  I'll be in this terrifying state of non-responsive every few seconds
  computer, with no ability to reconnect to networks and report bug.

  I force restart. The first restart, upon login, will hang indefinitely
  on a purple screen with the cursor in the middle. I will have to force
  restart again. Upon 2nd restart, it will boot "normally", in that
  after I login, I get the "familiar" "colorful static" splash screen
  before being taken to normal functional gnome desktop experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 12:38:24 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-02 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1754346] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-03-08 Thread Paul White

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

** This bug has been marked a duplicate of bug 1514474
   package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  It doesnot go on updating :keepson "waiting"endlessly

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic i686
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: i386
  Date: Thu Mar  8 08:03:27 2018
  DpkgHistoryLog:
   Start-Date: 2018-03-08  08:03:14
   Commandline: apt-get autoremove
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-09-01 (918 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1754346/+subscriptions

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

[Desktop-packages] [Bug 716280] Re: gvfsd-metadata process pegs CPU while nautilus waits

This is a really old bug and the versions of Ubuntu it references are
out of support now. Can you verify whether this is still a problem on
Xenial (16.04) or Artful (17.10) and reset the bug to "confirmed" if you
can recreate the issue.

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

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

Title:
  gvfsd-metadata process pegs CPU while nautilus waits

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: nautilus

  I have been getting delays of 30-60 seconds when nautilus copies data
  on an NTFS filesystem in a 1.5 TB My Book external USB disk from
  Western Digital. I was able to see the process that has 100% of the
  CPU and causes spinners in my Nautilus Windows until it finishes. It
  is gvfsd-metadata, for which I have no man page.

  Today, I closed an earlier bug thinking that the problem had resolved
  itself as I had nominal functionality with nautilus then. I noticed
  that the problem returned and looked at running processes with top (1)
  to see what process appeared and what it was using when it ran.

  I don't know what gvfsd-metadata does or how important it is, but it
  seems to be the hog process. As soon as it exits I get the FM back. It
  appears whenever I move (drag) files from one dir to another. Another
  bug where I had long delays moving a 1.0 GB dir from the boot drive to
  this external drive, may be the same problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: nautilus 1:2.32.0-0ubuntu1.3
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  Uname: Linux 2.6.35-25-generic i686
  Architecture: i386
  Date: Wed Feb  9 23:09:42 2011
  ExecutablePath: /usr/bin/nautilus
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: nautilus

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

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

[Desktop-packages] [Bug 826283] Re: size of internal HDDs differs/wrong

This is a really old bug and the versions of Ubuntu it references are
out of support now. Can you verify whether this is still a problem on
Xenial (16.04) or Artful (17.10) and reset the bug to "confirmed" if you
can recreate the issue.

I've marked "Ubuntu Translations" as invalid because I do not believe it
is related to the text translations.

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

** Changed in: ubuntu-translations
   Status: New => Invalid

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

Title:
  size of internal HDDs differs/wrong

Status in Ubuntu Translations:
  Invalid
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I have a dual boot scenario. On sda1 is windows 7 hosted and i partitioned 
with an Ubuntu Lucid Live-CD the size to 48,0 GB.
  After the installation i got this informations:
  - If the partition is mounted it shows on the desktop an size of 52 GB (52 GB 
Dateisystem)
  - If i want to see the proporties with an right-click, it shows me an size of 
48 GB (Name: 52 GB Dateisystem, Gesamte Kapazität 48 GB)
  - In the system monitor is also the size given with 48,0 GB

  So the automatic name is wrong and should the same as the proporties
  show!

  
  Ubuntu Lucid 10.04.3
  Linux bloedbommel3 2.6.32-33-generic #72-Ubuntu SMP Fri Jul 29 21:07:13 UTC 
2011 x86_64 GNU/Linux

  Package: gnome
  Versions: 
  1:2.28+1ubuntu3 
(/var/lib/apt/lists/de.archive.ubuntu.com_ubuntu_dists_lucid_universe_binary-amd64_Packages)
   Description Language: de

  Package: nautilus
  Versions: 
  1:2.30.1-0ubuntu1.2 
(/var/lib/apt/lists/de.archive.ubuntu.com_ubuntu_dists_lucid-updates_main_binary-amd64_Packages)
 (/var/lib/dpkg/status)
   Description Language:
  --- 
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 11.10
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  NonfreeKernelModules: fglrx
  Package: nautilus 1:3.2.1-0ubuntu3.1
  PackageArchitecture: amd64
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Tags:  oneiric
  Uname: Linux 3.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  usr_lib_nautilus:
   evince   3.2.1-0ubuntu2
   file-roller  3.2.1-0ubuntu1
   nautilus-dropbox 0.7.1

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

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

[Desktop-packages] [Bug 823168] Re: gvfs webdav to common name

This is a really old bug and things may be different now. Can you verify
whether this is still a problem on Xenial (16.04) or Artful (17.10) and
reset the bug to "confirmed" if you can recreate the issue?

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

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

Title:
  gvfs webdav to common name

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  If I connect 2 webdav site on the same server but different directories, only 
one is accessable from applications (/ and /). Cause: 
for mounting a to common name is used in nautulis "Webdav as  on " 
so the /home//.gvfs/ provides only the last mounted webdav (names are 
equal)
  Please use a less common name like SMB mounts:  on . --> For 
webdav: webdav(s): on . Don' t forget escape signs.

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

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

[Desktop-packages] [Bug 874471] Re: Pendrive/USB drive cannot be open in folder

This is a really old bug and the versions of Ubuntu it references are
out of support now. Can you verify whether this is still a problem on
Xenial (16.04) or Artful (17.10) and reset the bug to "confirmed" if you
can recreate the issue.

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

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

Title:
  Pendrive/USB drive cannot be open in folder

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  When I plug in my pendrive/USB drive, my Ubuntu cannot open the
  pendrive/USB drive in a folder, however it keep open the pendrive/USB
  drive with the software centre application. Now I can't do anything...

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: software-center 5.0.1.4
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Sat Oct 15 01:45:32 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  PackageArchitecture: all
  SourcePackage: software-center
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago)

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

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

[Desktop-packages] [Bug 1754418] Re: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

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

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 #1751460, 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/1754418/+attachment/5073279/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

** 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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1754418

Title:
  deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Crashed and is very unhappy on Ubuntu 18.04

  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
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  9 02:30:56 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2018-03-01 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  SegvAnalysis:
   Segfault happened at: 0x7f2217d8d588:movl   $0x0,(%rax)
   PC (0x7f2217d8d588) 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=0x7f2217ff502c, 
init_routine=0x7f220ee4a490 <__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: 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/deja-dup/+bug/1754418/+subscriptions

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

[Desktop-packages] [Bug 708546] Re: USB keys freeze the computer

This is a really old bug and the versions of Ubuntu it references are
out of support now. Can you verify whether this is still a problem on
Xenial (16.04) or Artful (17.10) and reset the bug to "confirmed" if you
can recreate the issue.

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

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

Title:
  USB keys freeze the computer

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: firefox

  When I use "unity layout", I can't open any USB key.
  The icon shows on the desktop but if I click on it, this freezes the computer 
for ever.
  I have to switch off the computer and use the gnome layout to open USB key

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: firefox 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
  ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
  Uname: Linux 2.6.35-24-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Thu Jan 27 10:58:35 2011
  FirefoxPackages:
   firefox 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
   firefox-gnome-support 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
   firefox-branding 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 
(20101007)
  ProcEnviron:
   LANG=fr_FR.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

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

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

[Desktop-packages] [Bug 312722] Re: Connect to FTP with Login > Error "The file is not a directory"

This is a really old bug and the versions of Ubuntu it references are
out of support now. Can you verify whether this is still a problem on
Xenial (16.04) or Artful (17.10) and reset the bug to "confirmed" if you
can recreate the issue.

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

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

Title:
  Connect to FTP with Login > Error "The file is not a directory"

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

Bug description:
  Ubuntu 8.04 & 8.10
  Using Nautilus Connect to server, and choosing FTP (with login), entering 
(domain/IP) address, user, and hitting "Connect".

  Prompts for password, and then displays:

  "The folder contents could not be displayed"
  "Sorry, couldn't display all the contents of "/ on [host-address/IP]": The 
file is not a directory"

  To me it seems to be a problem with the directory on the server. the
  folder for the user is not the root / folder of the server it is:
  "/d:/www/edvl/domain.ch/html" when i connect with FireFTP or other
  clients.

  So Nautilus tries to connect to domain.ch/ where it has no permission!

  When connecting with the ftp> (Terminal) to "domain.ch/" there is also an 
error "ftp: domain.ch/: Unknown host
  Opening "domain.ch" leads to prompting the Username and afterwards the pw

  Perhaps Nautilus automatically adds the / at the end of the URL and
  this causes problems.

  Connecting directly to domain.ch/d:/www/edvl/domain.ch/html does not
  work neither.

  Consider:
  http://ubuntuforums.org/showthread.php?p=6468035

  BTW: This is my first Bug Report,

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

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

[Desktop-packages] [Bug 1754394] Re: Very dark chromium interface and pages when hardware acceleration is enabled

Well, I'll be absolutely damned.

I created a new user and initially started in gnome wayland. This issue
wasn't present on xwayland. I then reset the user, and logged into gnome
xorg. No problem in there either.

I reset the user and logged into Unity 7. Problem wasn't there.
Initially.

To cut a long story short, this happens on Unity 7 when the launcher has
been configured to show  on a monitor that's not the primary (eg built
in desktop display).

Steps to reproduce: 
  * Connect a second screen
  * Log into unity
  * Configure a dark theme (not totally black) - arc-dark is very good as when 
the glitch happens you can really tell the difference
  * Open chromium - looks normal and themed. 
  * Close chromium
  * Open the display tool, set the launcher placement on the secondary monitor
  * Open chromium - you'll see it looks way darker now

This is at least on my setup.

I can reproduce this as well on my main account. I'll try on a different
laptop I have at home.

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

Title:
  Very dark chromium interface and pages when hardware acceleration is
  enabled

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I switched back to FF when Quantum came out, this is why I hadn't
  realised this until today that I had to use hangouts in Chromium.

  For some reason, it's like gamma for the Chromium windows is dialled
  almost all the way down when hardware acceleration is enabled. Please
  see screenshots. The "chromium-no-hw-accel.png" screenshot shows the
  same colours as Firefox and Qupzilla.

  I've since tried on other browsers using chromium to the same effect:
* Google Chrome 65.0.3325.146
* Opera 51.0.2830.55
* Chromium 64.0.3282.167-0ubuntu0.17.10.1 (as per bug report).

  This happens on intel HD630 graphics. I have a bumblebee/bbswitch set
  up but it seems unable to boot Chromium at all with HW on.

  I haven't been able however to see the same stuff on Electron apps
  though (VS Code and Slack).

  My setup:

* XPS 9560
* Bumblebee / bbswitch set up
* i7-7700HQ / Intel HD630
* Ubuntu 17.10
* Unity 7
* Kernel 4.13.0-36-generic

  ~ cat /usr/share/X11/xorg.conf.d/20-intel.conf

  Section "Device"
 Identifier "Intel Graphics"
 Driver "intel"
 Option "AccelMethod" "sna"
 Option "TearFree" "true"
 Option "DRI" "3"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: chromium-browser 64.0.3282.167-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DRM.card0-DP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAQrG2gVVZUMB8VAQMONR546rsEoVlVnigNUFSlSwBxT4GA0cABAQEBAQEBAQEBAjqAGHE4LUBYLEUAEyshAAAe/wBOUlBQNTE3VTBUVlUK/ABERUxMIFAyNDExSAog/QA4TB5TEQAKICAgICAgABQ=
   modes: 1920x1080 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 
800x600 640x480 640x480 720x400
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBNEHYUADEaAQSlIxN4DmYap1Q0vCULS1cBAQEBAQEBAQEBAQEBAQEBTdAAoPBwPoAwIDUAWsIQAAAY/gBZMlhORIBMUTE1NkQxAAACQQMoABIAAAsBCiAgAAY=
   modes: 3840x2160
  Date: Thu Mar  8 16:08:08 2018
  Desktop-Session:
   'unity'
   
'/etc/xdg/xdg-unity:/etc/xdg/xdg-unity:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings'
   
'/home/luis/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share/:/usr/share/unity:/usr/share/unity:/home/luis/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2017-11-30 (97 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Load-Avg-1min: 0.34
  Load-Processes-Running-Percent:   0.1%
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=979f134e-10a9-41ac-86cb-67c1e8295aaf ro quiet splash 
acpi_rev_override=5 pci=nommconf vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.

[Desktop-packages] [Bug 1754419] [NEW] transmission-daemon fails

2018-03-08 Thread Ken Sharp

Public bug reported:

Updating to 2.93-1ubuntu1~16.04.1ubuntu1 from the transmissionbt PPA
causes transmission-daemon to fail.

-- Unit transmission-daemon.service has begun starting up.
Mar 08 17:01:43 homeserver systemd[3085]: transmission-daemon.service: Failed 
at step USER spawning /usr/bin/transmission-daemo
-- Subject: Process /usr/bin/transmission-daemon could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The process /usr/bin/transmission-daemon could not be executed and failed.
-- 
-- The error number returned by this process is 3.
Mar 08 17:01:43 homeserver systemd[1]: transmission-daemon.service: Main 
process exited, code=exited, status=217/USER
Mar 08 17:01:43 homeserver systemd[1]: Failed to start Transmission BitTorrent 
Daemon.
-- Subject: Unit transmission-daemon.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit transmission-daemon.service has failed.
-- 
-- The result is failed.

This first problem is resolved by changing User from transmission to
debian-transmission - the user is incorrect.

This does not get the daemon working, however:

$ sudo apt -f install
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up transmission-daemon (2.93-1ubuntu1~16.04.1ubuntu1) ...
Job for transmission-daemon.service failed because a timeout was exceeded. See 
"systemctl status transmission-daemon.service" and "journalctl -xe" for details.
invoke-rc.d: initscript transmission-daemon, action "start" failed.
● transmission-daemon.service - Transmission BitTorrent Daemon
   Loaded: loaded (/lib/systemd/system/transmission-daemon.service; enabled; 
vendor preset: enabled)
   Active: failed (Result: timeout) since Thu 2018-03-08 17:07:23 GMT; 24ms ago
  Process: 3448 ExecStart=/usr/bin/transmission-daemon -f --log-debug 
(code=exited, status=0/SUCCESS)
 Main PID: 3448 (code=exited, status=0/SUCCESS)

Mar 08 17:07:23 homeserver transmission-daemon[3448]: [2018-03-08 17:07:23.013] 
Port Forwarding Stopped (port-forwarding.c:180)
Mar 08 17:07:23 homeserver transmission-daemon[3448]: [2018-03-08 17:07:23.013] 
Port Forwarding (NAT-PMP) readnatpmpres...c:75)
Mar 08 17:07:23 homeserver transmission-daemon[3448]: [2018-03-08 17:07:23.013] 
Port Forwarding (UPnP) Stopping port fo...:270)
Mar 08 17:07:23 homeserver transmission-daemon[3448]: [2018-03-08 17:07:23.013] 
Port Forwarding State changed from "For...c:92)
Mar 08 17:07:23 homeserver transmission-daemon[3448]: [2018-03-08 17:07:23.014] 
RPC Server Stopped listening on 0.0.0.0...:874)
Mar 08 17:07:23 homeserver systemd[1]: Failed to start Transmission BitTorrent 
Daemon.
Mar 08 17:07:23 homeserver systemd[1]: transmission-daemon.service: Unit 
entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package transmission-daemon (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 transmission-daemon
E: Sub-process /usr/bin/dpkg returned an error code (1)

I have no idea what the problem is at this point.

** Affects: transmission
 Importance: Undecided
 Status: New


** Tags: artful xenial

** Package changed: transmission (Ubuntu) => transmission

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

Title:
  transmission-daemon fails

Status in Transmission:
  New

Bug description:
  Updating to 2.93-1ubuntu1~16.04.1ubuntu1 from the transmissionbt PPA
  causes transmission-daemon to fail.

  -- Unit transmission-daemon.service has begun starting up.
  Mar 08 17:01:43 homeserver systemd[3085]: transmission-daemon.service: Failed 
at step USER spawning /usr/bin/transmission-daemo
  -- Subject: Process /usr/bin/transmission-daemon could not be executed
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- The process /usr/bin/transmission-daemon could not be executed and failed.
  -- 
  -- The error number returned by this process is 3.
  Mar 08 17:01:43 homeserver systemd[1]: transmission-daemon.service: Main 
process exited, code=exited, status=217/USER
  Mar 08 17:01:43 homeserver systemd[1]: Failed to start Transmission 
BitTorrent Daemon.
  -- Subject: Unit transmission-daemon.service has failed
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- Unit transmission-daemon.service has failed.
  -- 
  -- The result is failed.

  This first problem is resolved by changing User from transmission to
  debian-transmission - the user is

[Desktop-packages] [Bug 1754415] Re: cupsd crashed with SIGSEGV in ippCopyAttribute()

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

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 #1753766, 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/1754415/+attachment/5073254/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 cups in Ubuntu.
https://bugs.launchpad.net/bugs/1754415

Title:
  cupsd crashed with SIGSEGV in ippCopyAttribute()

Status in cups package in Ubuntu:
  New

Bug description:
  Just turn my pc on and this error apeared

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: cups-daemon 2.2.6-5
  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
  Date: Thu Mar  8 07:07:13 2018
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2018-02-08 (27 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208)
  Lpstat: device for HP-M521_GTI: socket://10.2.254.103
  MachineType: Hewlett-Packard HP Compaq 6005 Pro SFF PC
  Papersize: a4
  PpdFiles:
   HP_LaserJet_Pro_MFP_M521dn_68DA1F_: LaserJet Pro MFP M521dn
   HP_LaserJet_Pro_MFP_M521dn_DC590A_: LaserJet Pro MFP M521dn
   HP-M521_GTI: HP LaserJet Pro MFP M521 Postscript (recommended)
   HP_LaserJet_Pro_MFP_M521dn_615877_: LaserJet Pro MFP M521dn
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=550af015-9954-408f-81ad-053c28803cd4 ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=550af015-9954-408f-81ad-053c28803cd4 ro quiet splash vt.handoff=1
  SegvAnalysis:
   Segfault happened at: 0x7f160a3a8db3 : addl   
$0x1,0x38(%rdx)
   PC (0x7f160a3a8db3) ok
   source "$0x1" ok
   destination "0x38(%rdx)" (0x0038) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   ippCopyAttribute () from /usr/lib/x86_64-linux-gnu/libcups.so.2
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: cupsd crashed with SIGSEGV in ippCopyAttribute()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 08/04/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G6 v01.11
  dmi.board.asset.tag: BRG112FHQ2
  dmi.board.name: 3047h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: BRG112FHQ2
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G6v01.11:bd08/04/2010:svnHewlett-Packard:pnHPCompaq6005ProSFFPC:pvr:rvnHewlett-Packard:rn3047h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq 6005 Pro SFF PC
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1735499] Re: [MIR] libblockdev

** Description changed:

  Availability
  
  Built for all supported architectures. In sync with Debian.
  
  Rationale
  =
  udisks2 2.7 uses the "libblockdev library for all low level storage 
management tasks instead of calling command line tools." libblockdev appears to 
have the same maintainers ("storaged project") as udisks2.
  
  It would be nice to have the new version to support GNOME Disks 3.26's new 
Resize and Repair features.
  http://pothos.blogsport.eu/2017/08/22/last-project-phase-and-3-26-features/
  
  There is some interest in dropping Gparted from the Ubuntu live ISO
  since it does not support Wayland and it still uses gtk2.
  
  Security
  
  No known security issues
  
  https://security-tracker.debian.org/tracker/source-package/libblockdev
  https://launchpad.net/ubuntu/+source/libblockdev/+cve
  
  Quality assurance
  =
  - Ubuntu Desktop bugs is the subscriber (although the Desktop Team thinks 
that Foundations should be responsible for udisks and friends)
  
  https://bugs.launchpad.net/ubuntu/+source/libblockdev
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libblockdev
  https://github.com/storaged-project/libblockdev/issues
  
  dh_auto_test is run but I guess it's not actually running the upstream test 
suite yet. (I think the upstream test suite needs to be run as autopkgtests)
  See http://storaged.org/libblockdev/ch03.html
  
  No autopkgtests
  
  Dependencies
  
- Debian's udisks2 recommends libblockdev-plugins-all which depends on these 
binary packages:
- - libblockdev-crypto2 which depends on the universe libvolume-key1 (source: 
volume-key)
- - libblockdev-btrfs2 which depends on the universe libbytesize1 (source: 
libbytesize)
- - libblockdev-kbd2 which depends on the universe libbytesize1 (source: 
libbytesize)
- - libblockdev-mdraid2 which depends on the universe libbytesize1 (source: 
libbytesize)
+ Debian's udisks2 recommends libblockdev-crypto2 which depends on the universe 
libvolume-key1 (source: volume-key)
  
- libbytesize is another storaged project. Neither libbytesize nor volume-
- key have any other universe binary dependencies. It might be ok to
- temporarily not recommend those udisks2 plugins until the other 2 MIRs
- are processed.
+ It might be ok to temporarily not recommend that plugin until a MIR for
+ volume-key is filed and approved.
  
  Standards compliance
  
  4.1.1, debhelper compat 10, simple dh7 style rules
  
  Maintenance
  ===
  Maintained in Debian by the Debian Utopia team, which is a small team focused 
on cross-desktop freedesktop.org stuff.
  
  upstream:
  https://github.com/storaged-project/libblockdev

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

Title:
  [MIR] libblockdev

Status in libblockdev package in Ubuntu:
  New
Status in udisks2 package in Ubuntu:
  New

Bug description:
  Availability
  
  Built for all supported architectures. In sync with Debian.

  Rationale
  =
  udisks2 2.7 uses the "libblockdev library for all low level storage 
management tasks instead of calling command line tools." libblockdev appears to 
have the same maintainers ("storaged project") as udisks2.

  It would be nice to have the new version to support GNOME Disks 3.26's new 
Resize and Repair features.
  http://pothos.blogsport.eu/2017/08/22/last-project-phase-and-3-26-features/

  There is some interest in dropping Gparted from the Ubuntu live ISO
  since it does not support Wayland and it still uses gtk2.

  Security
  
  No known security issues

  https://security-tracker.debian.org/tracker/source-package/libblockdev
  https://launchpad.net/ubuntu/+source/libblockdev/+cve

  Quality assurance
  =
  - Ubuntu Desktop bugs is the subscriber (although the Desktop Team thinks 
that Foundations should be responsible for udisks and friends)

  https://bugs.launchpad.net/ubuntu/+source/libblockdev
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libblockdev
  https://github.com/storaged-project/libblockdev/issues

  dh_auto_test is run but I guess it's not actually running the upstream test 
suite yet. (I think the upstream test suite needs to be run as autopkgtests)
  See http://storaged.org/libblockdev/ch03.html

  No autopkgtests

  Dependencies
  
  Debian's udisks2 recommends libblockdev-crypto2 which depends on the universe 
libvolume-key1 (source: volume-key)

  It might be ok to temporarily not recommend that plugin until a MIR
  for volume-key is filed and approved.

  Standards compliance
  
  4.1.1, debhelper compat 10, simple dh7 style rules

  Maintenance
  ===
  Maintained in Debian by the Debian Utopia team, which is a small team focused 
on cross-desktop freedesktop.org stuff.

  upstream:

[Desktop-packages] [Bug 1754403] 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/1754403/+attachment/5073200/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1754403/+attachment/5073209/+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/1754403

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Have been using this system on a normal non-hidpi monitor (via
  displayport) for weeks, since installing 18.04 alpha from scratch.

  Just plugged it into a 4K monitor, also via displayport. The system
  was shut down while I moved it to the different desk, so it was
  switched on to the new monitor, not a live swap.

  System booted, everything came up, logged in, everything seems fine,
  including my gnome shell, which is running, but this bug report came
  up too.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Mar  8 16:12:40 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-02-20 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.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
   _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () 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/1754403/+subscriptions

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

[Desktop-packages] [Bug 1735499] Re: [MIR] libblockdev

2018-03-08 Thread Seth Arnold

I reviewed libblockdev version 2.16-2 as checked into bionic. This should
not be considered a full security audit but rather a quick gauge of
maintainability.

- libblockdev is a plugin-based library to work with block devices,
  providing an API based interface that knows how to either perform
  underlying operations directly or call the necessary command line
  applications as appropriate.

- There are no CVEs in our database

- Build-Depends: debhelper, libtool, dh-python, python3:any, libglib2.0-dev
  libgirepository1.0-dev, libcryptsetup-dev libdevmapper-dev libudev-dev
  libsystemd-dev, libdmraid-dev, libvolume-key-dev, libbytesize-dev,
  libnss3-dev libparted-dev libmount-dev libblkid-dev libpython3-dev,
  libkmod-dev gtk-doc-tools, gobject-introspection, pylint

- libblockdev does not itself daemonize
- no networking
- automatically generated pre/post inst/rm scripts
- no initscripts
- no dbus services
- no setuid files
- no executables in PATH
- no sudo fragments
- no udev rules
- There is a test suite; it is not run during the build. I suspect keeping
  this test suite disabled is the right approach.
- No cronjobs
- Noisy build logs, primarily from the documentation tools; not ideal, but
  at least not much from the code itself

- Several plugins execute helper tools; the glib helpers make the
  resulting code fairly complex, but it looks like the executions were
  carefully written
- memory management is careful; allocated memory is quickly freed when it
  is no longer used to simplify error handling
- normally 'files' being opened are block devices
- Logging functions looked careful
- No environment variable use
- Does not itself do cryptography -- drives LUKS, VeraCrypt, etc via
  helpers
- Does not do networking
- Does not use temporary files
- Does not use WebKit
- Does not use PolicyKit
- Does not use JavaScript
- Mostly clean cppcheck results; s390 code has legitimate errors:
  [src/plugins/s390.c:293]: (error) Used file that is not opened.
  [src/plugins/s390.c:293]: (error) Resource handle 'fd' freed twice.
  [src/plugins/s390.c:968]: (error) Resource leak: fd


The s390 code does not feel as mature as the rest of the code base.
I suspect a deeper inspection of the s390 sources would find more issues.
If it can be disabled without significant loss of functionality then I
recommend we disable it.

Security team ACK for promoting libblockdev to main.

Here's some notes I took while reviewing the code, in the hopes that they
are useful:

- bd_s390_dasd_online() double-closes fd, uses fd when it isn't open
- bd_s390_zfcp_offline() leaks fd in rc == EOF branch
- bd_s390_zfcp_online() calls fclose(fd) in a branch when fd is known to
  be NULL
- bd_s390_zfcp_scsi_offline() does not check fopen(hba_path, "r") for an
  error return
- bd_s390_zfcp_scsi_offline() does not check fopen(wwpn_path, "r") for an
  error return
- bd_s390_zfcp_scsi_offline() does not check fopen(lun_path, "r") for an
  error return

- bd_crypto_tc_open(), luks_format(), (and other functions) do not zero
  out secrets such as passwords. (This is difficult to do; the goal is not
  to be perfect, but to try. Simply adding memset_s() calls would be a
  step in the right direction.)

- Many routines in src/plugins/crypto.c call strlen(passwd), some other
  functions are described as taking binary data in password parameters. Is
  there a chance of one interface setting, changing, or removing a
  password, that other interfaces cannot work with?

- write_escrow_data_file() writes what looks like a secret key equivalent
  to a file but does not itself set a safe umask before doing so.


Thanks


** Changed in: libblockdev (Ubuntu)
 Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)

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

Title:
  [MIR] libblockdev

Status in libblockdev package in Ubuntu:
  New
Status in udisks2 package in Ubuntu:
  New

Bug description:
  Availability
  
  Built for all supported architectures. In sync with Debian.

  Rationale
  =
  udisks2 2.7 uses the "libblockdev library for all low level storage 
management tasks instead of calling command line tools." libblockdev appears to 
have the same maintainers ("storaged project") as udisks2.

  It would be nice to have the new version to support GNOME Disks 3.26's new 
Resize and Repair features.
  http://pothos.blogsport.eu/2017/08/22/last-project-phase-and-3-26-features/

  There is some interest in dropping Gparted from the Ubuntu live ISO
  since it does not support Wayland and it still uses gtk2.

  Security
  
  No known security issues

  https://security-tracker.debian.org/tracker/source-package/libblockdev
  https://launchpad.net/ubuntu/+source/libblockdev/+cve

  Quality assurance
  =
  - Ubuntu Desktop bugs is the subscriber (although the Desktop Team thinks 
that

[Desktop-packages] [Bug 1754395] Stacktrace.txt

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1754395/+attachment/5073197/+files/Stacktrace.txt

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

Title:
  deja-dup-monitor crashed with SIGSEGV in
  bmalloc::FreeList::initializeList()

Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  Just installed from Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  doing apt update+upgrade from terminal

  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
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 17:11:58 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2018-03-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   bmalloc::FreeList::initializeList(bmalloc::FreeCell*, unsigned long, 
unsigned int) () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   audit_list_string ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in 
bmalloc::FreeList::initializeList()
  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/deja-dup/+bug/1754395/+subscriptions

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

[Desktop-packages] [Bug 1754395] ThreadStacktrace.txt

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1754395/+attachment/5073199/+files/ThreadStacktrace.txt

** Changed in: deja-dup (Ubuntu)
   Status: New => Invalid

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

Title:
  deja-dup-monitor crashed with SIGSEGV in
  bmalloc::FreeList::initializeList()

Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  Just installed from Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  doing apt update+upgrade from terminal

  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
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 17:11:58 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2018-03-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   bmalloc::FreeList::initializeList(bmalloc::FreeCell*, unsigned long, 
unsigned int) () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   audit_list_string ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in 
bmalloc::FreeList::initializeList()
  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/deja-dup/+bug/1754395/+subscriptions

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

[Desktop-packages] [Bug 1754395] Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for perl-base
no debug symbol package found for perl-base


Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!


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

** Tags removed: need-amd64-retrace

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

Title:
  deja-dup-monitor crashed with SIGSEGV in
  bmalloc::FreeList::initializeList()

Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  Just installed from Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  doing apt update+upgrade from terminal

  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
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 17:11:58 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2018-03-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   bmalloc::FreeList::initializeList(bmalloc::FreeCell*, unsigned long, 
unsigned int) () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   audit_list_string ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in 
bmalloc::FreeList::initializeList()
  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/deja-dup/+bug/1754395/+subscriptions

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

[Desktop-packages] [Bug 1754395] StacktraceSource.txt

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1754395/+attachment/5073198/+files/StacktraceSource.txt

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

Title:
  deja-dup-monitor crashed with SIGSEGV in
  bmalloc::FreeList::initializeList()

Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  Just installed from Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  doing apt update+upgrade from terminal

  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
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 17:11:58 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2018-03-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   bmalloc::FreeList::initializeList(bmalloc::FreeCell*, unsigned long, 
unsigned int) () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   audit_list_string ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in 
bmalloc::FreeList::initializeList()
  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/deja-dup/+bug/1754395/+subscriptions

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

[Desktop-packages] [Bug 1754395] deja-dup-monitor crashed with SIGSEGV in bmalloc::FreeList::initializeList()

StacktraceTop:
 bmalloc::FreeList::initializeList (this=0x7ffd7e5abf60, head=, 
secret=140402433444016, bytes=0) at ./Source/bmalloc/bmalloc/FreeList.cpp:50
 audit_list_string ()
 ?? ()
 ?? () from 
/tmp/apport_sandbox_8LHLFd/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
 ?? () from 
/tmp/apport_sandbox_8LHLFd/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18

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

Title:
  deja-dup-monitor crashed with SIGSEGV in
  bmalloc::FreeList::initializeList()

Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  Just installed from Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  doing apt update+upgrade from terminal

  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
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 17:11:58 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2018-03-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   bmalloc::FreeList::initializeList(bmalloc::FreeCell*, unsigned long, 
unsigned int) () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   audit_list_string ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in 
bmalloc::FreeList::initializeList()
  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/deja-dup/+bug/1754395/+subscriptions

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

[Desktop-packages] [Bug 1754400] [NEW] "General input/output error" when attempting to save a document to google drive

2018-03-08 Thread Olivier Tilloy

Public bug reported:

(bug initially reported upstream, but apparently only affects ubuntu:
https://bugs.documentfoundation.org/show_bug.cgi?id=97898)

Steps to reproduce:

 - start a document in libreoffice writer
 - menu File > Save Remote…
 - use the "Add Service" button to configure an existing google account (not 
one using 2FA, that's not implemented yet)

Expected result: the document is saved on your google drive

Current result: an error dialog box that reads: "Error saving the
document Untitled 1: General input/output error."

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libreoffice 1:6.0.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar  8 17:22:50 2018
InstallationDate: Installed on 2018-02-08 (27 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  "General input/output error" when attempting to save a document to
  google drive

Status in libreoffice package in Ubuntu:
  New

Bug description:
  (bug initially reported upstream, but apparently only affects ubuntu:
  https://bugs.documentfoundation.org/show_bug.cgi?id=97898)

  Steps to reproduce:

   - start a document in libreoffice writer
   - menu File > Save Remote…
   - use the "Add Service" button to configure an existing google account (not 
one using 2FA, that's not implemented yet)

  Expected result: the document is saved on your google drive

  Current result: an error dialog box that reads: "Error saving the
  document Untitled 1: General input/output error."

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 17:22:50 2018
  InstallationDate: Installed on 2018-02-08 (27 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1164016] Re: restore type-ahead find

2018-03-08 Thread teo1978

> If that is genuinely the reason (and this bug has been marked as "Fix 
> Released" 
> since Jan 2014, so it seems correct), then is it not time to raise a new bug?

Maybe (though it seems a little stupid to raise a new bug for exactly
the same issue).

Anyway I did, like yesterday, and it got closed
(can't find it right now, I don't know what's wrong with the search engine of 
this stupid bug tracker)

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

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

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

[Desktop-packages] [Bug 1754395] [NEW] deja-dup-monitor crashed with SIGSEGV in bmalloc::FreeList::initializeList()

2018-03-08 Thread corrado venturini

Public bug reported:

Just installed from Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
doing apt update+upgrade from terminal

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
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar  8 17:11:58 2018
ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
InstallationDate: Installed on 2018-03-08 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
Signal: 11
SourcePackage: deja-dup
StacktraceTop:
 bmalloc::FreeList::initializeList(bmalloc::FreeCell*, unsigned long, unsigned 
int) () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
 audit_list_string ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
 ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
Title: deja-dup-monitor crashed with SIGSEGV in 
bmalloc::FreeList::initializeList()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash bionic need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  deja-dup-monitor crashed with SIGSEGV in
  bmalloc::FreeList::initializeList()

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Just installed from Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  doing apt update+upgrade from terminal

  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
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 17:11:58 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2018-03-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   bmalloc::FreeList::initializeList(bmalloc::FreeCell*, unsigned long, 
unsigned int) () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   audit_list_string ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in 
bmalloc::FreeList::initializeList()
  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/deja-dup/+bug/1754395/+subscriptions

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

[Desktop-packages] [Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)

2018-03-08 Thread teo1978

This is so stupid.

> One of my main interests in the last 4 releases was to improve this
> situation, whether search doesn't replace the use cases of type ahead.

Indeed, search, does NOT replace type-ahead, it's just a completely
different thing, and it won't ever be a replacement, no matter how much
you improve it, and regardless of performance.

The solution was pretty obvious: just DON'T replace type-ahead with
search.

But no, idiocy had to prevail, as it usually does in Nautilus. That's a
shame.

I wonder why Ubuntu doesn't switch to some other file manager that,
unlike Nautilus, is not maintained by complete idiots.

I guess I'll have to switch to a distro that, unlike Ubuntu, is not
maintained by idiots either.

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

Title:
Restore interactive_search.patch (type-ahead search)

Status in nautilus package in Ubuntu:
Won't Fix

Bug description:
Nautilus dropped the popular type-ahead search feature years ago.
Ubuntu has been carrying a patch to revert that change. See bug
1164016 for the original LP bug and patch proposal.

Nautilus is now under very active development. During the 3.22 cycle,
that patch needed to be rebased. I tried to do it and what I came up
with caused a crash (it didn't really crash for me, but ricotz and
some others experienced it) and the first letter typed activated type-
ahead search but the first letter was dropped. In other words, you
would need to type "ddow" to activate the Downloads folder instead of
just "dow" like in previous releases. (LP: #1635988)

I did that rebase in October 2016 and no one has stepped up then to
improve the patch.

The Nautilus maintainer csoriano has said that the slots and views
changed significantly during 3.22 and will likely be refactored more
in the future.

If there's no one available to maintain the patch, unfortunately,
we'll eventually have to drop the patch to not be stuck on an ancient
version of Nautilus.

I am proposing that we do this at the start of the 17.10 development
cycle. This gives 6 months for a developer to step up and try to fix
the patch and 12 months before 18.04 LTS.

Other Items
===
- For better performance with the built-in search, we need to reconsider
avoiding tracker in Unity (LP: #176)

- There is an option in Preferences for users to disable searching in
subfolders. I don't think we want to do that by default but maybe it
can help some people.

The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with
this patch now disabled.

https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty

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

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

[Desktop-packages] [Bug 1754356] Re: xdg-user-dirs-update does not take care of $HOME

2018-03-08 Thread Ubuntu Foundations Team Bug Bot

The attachment "xenial SRU debdiff" seems to be a debdiff.  The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

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

Title:
  xdg-user-dirs-update does not take care of $HOME

Status in xdg-user-dirs package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  When setting an user dir to a folder that is subfolder of $HOME (and
  when $HOME does not match the /etc/passwd defined home for the user),
  the ~/.config/user-dirs.dirs is wrongly generated.

  [ Test case ]

   1) env HOME=/tmp/temp-home xdg-user-dirs-update
   2) find /tmp/temp-home/
   3) should list generated XDG user directories
   4) /tmp/temp-home/.config/user-dirs.dirs should mention them

  Launching something like:
   - env HOME=/tmp/temp-home ./xdg-user-dirs-update --set DOWNLOADS 
"/tmp/temp-home/sub/folder/of/it/Downloads"

  Should modify /tmp/temp-home/.config/user-dirs.dirs so that it contains:
XDG_DOWNLOADS_DIR="$HOME/sub/folder/of/it/Downloads"

  [ Regression potential ]

  Xdg folders could be generated in wrong locations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1754356/+subscriptions

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

[Desktop-packages] [Bug 1754396] [NEW] nvidia 390 driver creates unknown screen

2018-03-08 Thread Rolf.Schmitt

Public bug reported:

ubuntu 18.04 Laptop Samsung RF711 and Sony V7
the nvidia driver creates an unknown screen and also opens it.

I do not see a login window and a desktop
I enter the password blind, I start the desktop and do not see him.
with the right mouse button and background I can change the screen.

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

** Description changed:

- 127/5000
- Meintest du: ubuntu 18.04 Laptop Samsung RF711 und Sony V7 der nvidia treiber 
erzeugt einen unbekannten bildschirm und startet auf diesem.
- ubuntu 18.04
- Laptop Samsung RF-711 and Sony V7
- the nvidia driver creates an unknown screen and launches on this.
+ ubuntu 18.04 Laptop Samsung RF711 and Sony V7
+ the nvidia driver creates an unknown screen and also opens it.
+ 
  I do not see a login window and a desktop
  I enter the password blind, I start the desktop and do not see him.
  with the right mouse button and background I can change the screen.

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

Title:
  nvidia 390 driver creates unknown screen

Status in deja-dup package in Ubuntu:
  New

Bug description:
  ubuntu 18.04 Laptop Samsung RF711 and Sony V7
  the nvidia driver creates an unknown screen and also opens it.

  I do not see a login window and a desktop
  I enter the password blind, I start the desktop and do not see him.
  with the right mouse button and background I can change the screen.

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

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

[Desktop-packages] [Bug 1754394] Re: Very dark chromium interface and pages when hardware acceleration is enabled

** Attachment added: "chromium-no-hw-accel.png"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1754394/+attachment/5073173/+files/chromium-no-hw-accel.png

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

Title:
  Very dark chromium interface and pages when hardware acceleration is
  enabled

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I switched back to FF when Quantum came out, this is why I hadn't
  realised this until today that I had to use hangouts in Chromium.

  For some reason, it's like gamma for the Chromium windows is dialled
  almost all the way down when hardware acceleration is enabled. Please
  see screenshots. The "chromium-no-hw-accel.png" screenshot shows the
  same colours as Firefox and Qupzilla.

  I've since tried on other browsers using chromium to the same effect:
* Google Chrome 65.0.3325.146
* Opera 51.0.2830.55
* Chromium 64.0.3282.167-0ubuntu0.17.10.1 (as per bug report).

  This happens on intel HD630 graphics. I have a bumblebee/bbswitch set
  up but it seems unable to boot Chromium at all with HW on.

  I haven't been able however to see the same stuff on Electron apps
  though (VS Code and Slack).

  My setup:

* XPS 9560
* Bumblebee / bbswitch set up
* i7-7700HQ / Intel HD630
* Ubuntu 17.10
* Unity 7
* Kernel 4.13.0-36-generic

  ~ cat /usr/share/X11/xorg.conf.d/20-intel.conf

  Section "Device"
 Identifier "Intel Graphics"
 Driver "intel"
 Option "AccelMethod" "sna"
 Option "TearFree" "true"
 Option "DRI" "3"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: chromium-browser 64.0.3282.167-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DRM.card0-DP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAQrG2gVVZUMB8VAQMONR546rsEoVlVnigNUFSlSwBxT4GA0cABAQEBAQEBAQEBAjqAGHE4LUBYLEUAEyshAAAe/wBOUlBQNTE3VTBUVlUK/ABERUxMIFAyNDExSAog/QA4TB5TEQAKICAgICAgABQ=
   modes: 1920x1080 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 
800x600 640x480 640x480 720x400
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBNEHYUADEaAQSlIxN4DmYap1Q0vCULS1cBAQEBAQEBAQEBAQEBAQEBTdAAoPBwPoAwIDUAWsIQAAAY/gBZMlhORIBMUTE1NkQxAAACQQMoABIAAAsBCiAgAAY=
   modes: 3840x2160
  Date: Thu Mar  8 16:08:08 2018
  Desktop-Session:
   'unity'
   
'/etc/xdg/xdg-unity:/etc/xdg/xdg-unity:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings'
   
'/home/luis/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share/:/usr/share/unity:/usr/share/unity:/home/luis/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2017-11-30 (97 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Load-Avg-1min: 0.34
  Load-Processes-Running-Percent:   0.1%
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=979f134e-10a9-41ac-86cb-67c1e8295aaf ro quiet splash 
acpi_rev_override=5 pci=nommconf vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/25/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1754394] Re: Very dark chromium interface and pages when hardware acceleration is enabled

Also I'm observing the same thing when opening photos (eg the
screenshots above) with Gnome Image Viewer 3.26.

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

Title:
  Very dark chromium interface and pages when hardware acceleration is
  enabled

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I switched back to FF when Quantum came out, this is why I hadn't
  realised this until today that I had to use hangouts in Chromium.

  For some reason, it's like gamma for the Chromium windows is dialled
  almost all the way down when hardware acceleration is enabled. Please
  see screenshots. The "chromium-no-hw-accel.png" screenshot shows the
  same colours as Firefox and Qupzilla.

  I've since tried on other browsers using chromium to the same effect:
* Google Chrome 65.0.3325.146
* Opera 51.0.2830.55
* Chromium 64.0.3282.167-0ubuntu0.17.10.1 (as per bug report).

  This happens on intel HD630 graphics. I have a bumblebee/bbswitch set
  up but it seems unable to boot Chromium at all with HW on.

  I haven't been able however to see the same stuff on Electron apps
  though (VS Code and Slack).

  My setup:

* XPS 9560
* Bumblebee / bbswitch set up
* i7-7700HQ / Intel HD630
* Ubuntu 17.10
* Unity 7
* Kernel 4.13.0-36-generic

  ~ cat /usr/share/X11/xorg.conf.d/20-intel.conf

  Section "Device"
 Identifier "Intel Graphics"
 Driver "intel"
 Option "AccelMethod" "sna"
 Option "TearFree" "true"
 Option "DRI" "3"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: chromium-browser 64.0.3282.167-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DRM.card0-DP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAQrG2gVVZUMB8VAQMONR546rsEoVlVnigNUFSlSwBxT4GA0cABAQEBAQEBAQEBAjqAGHE4LUBYLEUAEyshAAAe/wBOUlBQNTE3VTBUVlUK/ABERUxMIFAyNDExSAog/QA4TB5TEQAKICAgICAgABQ=
   modes: 1920x1080 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 
800x600 640x480 640x480 720x400
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBNEHYUADEaAQSlIxN4DmYap1Q0vCULS1cBAQEBAQEBAQEBAQEBAQEBTdAAoPBwPoAwIDUAWsIQAAAY/gBZMlhORIBMUTE1NkQxAAACQQMoABIAAAsBCiAgAAY=
   modes: 3840x2160
  Date: Thu Mar  8 16:08:08 2018
  Desktop-Session:
   'unity'
   
'/etc/xdg/xdg-unity:/etc/xdg/xdg-unity:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings'
   
'/home/luis/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share/:/usr/share/unity:/usr/share/unity:/home/luis/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2017-11-30 (97 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Load-Avg-1min: 0.34
  Load-Processes-Running-Percent:   0.1%
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=979f134e-10a9-41ac-86cb-67c1e8295aaf ro quiet splash 
acpi_rev_override=5 pci=nommconf vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/25/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1754394] Re: Very dark chromium interface and pages when hardware acceleration is enabled

** Attachment added: "chromium-yes-hw-accel.png"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1754394/+attachment/5073172/+files/chromium-yes-hw-accel.png

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

Title:
  Very dark chromium interface and pages when hardware acceleration is
  enabled

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I switched back to FF when Quantum came out, this is why I hadn't
  realised this until today that I had to use hangouts in Chromium.

  For some reason, it's like gamma for the Chromium windows is dialled
  almost all the way down when hardware acceleration is enabled. Please
  see screenshots. The "chromium-no-hw-accel.png" screenshot shows the
  same colours as Firefox and Qupzilla.

  I've since tried on other browsers using chromium to the same effect:
* Google Chrome 65.0.3325.146
* Opera 51.0.2830.55
* Chromium 64.0.3282.167-0ubuntu0.17.10.1 (as per bug report).

  This happens on intel HD630 graphics. I have a bumblebee/bbswitch set
  up but it seems unable to boot Chromium at all with HW on.

  I haven't been able however to see the same stuff on Electron apps
  though (VS Code and Slack).

  My setup:

* XPS 9560
* Bumblebee / bbswitch set up
* i7-7700HQ / Intel HD630
* Ubuntu 17.10
* Unity 7
* Kernel 4.13.0-36-generic

  ~ cat /usr/share/X11/xorg.conf.d/20-intel.conf

  Section "Device"
 Identifier "Intel Graphics"
 Driver "intel"
 Option "AccelMethod" "sna"
 Option "TearFree" "true"
 Option "DRI" "3"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: chromium-browser 64.0.3282.167-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DRM.card0-DP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAQrG2gVVZUMB8VAQMONR546rsEoVlVnigNUFSlSwBxT4GA0cABAQEBAQEBAQEBAjqAGHE4LUBYLEUAEyshAAAe/wBOUlBQNTE3VTBUVlUK/ABERUxMIFAyNDExSAog/QA4TB5TEQAKICAgICAgABQ=
   modes: 1920x1080 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 
800x600 640x480 640x480 720x400
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBNEHYUADEaAQSlIxN4DmYap1Q0vCULS1cBAQEBAQEBAQEBAQEBAQEBTdAAoPBwPoAwIDUAWsIQAAAY/gBZMlhORIBMUTE1NkQxAAACQQMoABIAAAsBCiAgAAY=
   modes: 3840x2160
  Date: Thu Mar  8 16:08:08 2018
  Desktop-Session:
   'unity'
   
'/etc/xdg/xdg-unity:/etc/xdg/xdg-unity:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings'
   
'/home/luis/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share/:/usr/share/unity:/usr/share/unity:/home/luis/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2017-11-30 (97 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Load-Avg-1min: 0.34
  Load-Processes-Running-Percent:   0.1%
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=979f134e-10a9-41ac-86cb-67c1e8295aaf ro quiet splash 
acpi_rev_override=5 pci=nommconf vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/25/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1754394] [NEW] Very dark chromium interface and pages when hardware acceleration is enabled

Public bug reported:

I switched back to FF when Quantum came out, this is why I hadn't
realised this until today that I had to use hangouts in Chromium.

For some reason, it's like gamma for the Chromium windows is dialled
almost all the way down when hardware acceleration is enabled. Please
see screenshots. The "chromium-no-hw-accel.png" screenshot shows the
same colours as Firefox and Qupzilla.

I've since tried on other browsers using chromium to the same effect:
  * Google Chrome 65.0.3325.146
  * Opera 51.0.2830.55
  * Chromium 64.0.3282.167-0ubuntu0.17.10.1 (as per bug report).

This happens on intel HD630 graphics. I have a bumblebee/bbswitch set up
but it seems unable to boot Chromium at all with HW on.

I haven't been able however to see the same stuff on Electron apps
though (VS Code and Slack).

My setup:

  * XPS 9560
  * Bumblebee / bbswitch set up
  * i7-7700HQ / Intel HD630
  * Ubuntu 17.10
  * Unity 7
  * Kernel 4.13.0-36-generic

~ cat /usr/share/X11/xorg.conf.d/20-intel.conf

Section "Device"
   Identifier "Intel Graphics"
   Driver "intel"
   Option "AccelMethod" "sna"
   Option "TearFree" "true"
   Option "DRI" "3"
EndSection

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: chromium-browser 64.0.3282.167-0ubuntu0.17.10.1
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
DRM.card0-DP-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: 
AP///wAQrG2gVVZUMB8VAQMONR546rsEoVlVnigNUFSlSwBxT4GA0cABAQEBAQEBAQEBAjqAGHE4LUBYLEUAEyshAAAe/wBOUlBQNTE3VTBUVlUK/ABERUxMIFAyNDExSAog/QA4TB5TEQAKICAgICAgABQ=
 modes: 1920x1080 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 
800x600 640x480 640x480 720x400
DRM.card0-DP-2:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-HDMI-A-1:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-HDMI-A-2:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-eDP-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: 
AP///wBNEHYUADEaAQSlIxN4DmYap1Q0vCULS1cBAQEBAQEBAQEBAQEBAQEBTdAAoPBwPoAwIDUAWsIQAAAY/gBZMlhORIBMUTE1NkQxAAACQQMoABIAAAsBCiAgAAY=
 modes: 3840x2160
Date: Thu Mar  8 16:08:08 2018
Desktop-Session:
 'unity'
 
'/etc/xdg/xdg-unity:/etc/xdg/xdg-unity:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings'
 
'/home/luis/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share/:/usr/share/unity:/usr/share/unity:/home/luis/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
DetectedPlugins:
 
Env:
 'None'
 'None'
InstallationDate: Installed on 2017-11-30 (97 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Load-Avg-1min: 0.34
Load-Processes-Running-Percent:   0.1%
MachineType: Dell Inc. XPS 15 9560
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=979f134e-10a9-41ac-86cb-67c1e8295aaf ro quiet splash 
acpi_rev_override=5 pci=nommconf vt.handoff=7
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/25/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.1
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/25/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.sys.vendor: Dell Inc.
etcconfigcpepperflashpluginnonfree:
 flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
 flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed 
-e "s/,/./g"`
 CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
modified.conffile..etc.default.chromium-browser: [deleted]

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  Very dark chromium interface and pages when hardware acceleration is
  enabled

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I switched back to FF when Quantum came out, this is why I hadn't
  realised this until today that I had to use hangouts in Chromium.

  For some reason, it's like gamma for the Chromium windows is dialled
  almost all the way down when hardware acceleration is enabled. Please
  see screenshots. The "chromium-no-hw-accel.png" screenshot shows the
  same colours as Firefox and Qupzilla.

  I've since tried on other browsers using

[Desktop-packages] [Bug 1754389] Re: visual contrast of dropdown menu is very bad

2018-03-08 Thread Michael Kuster

** Attachment added: "very bad contrast.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1754389/+attachment/5073142/+files/very%20bad%20contrast.jpg

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

Title:
  visual contrast of dropdown menu is very bad

Status in libreoffice package in Ubuntu:
  New

Bug description:
  This is not a specific LibreOffice problem, I saw the problem in
  AnyDesk too, if you choose your language.

  But in LibreOffice you can see the bug in the dialog if you save a
  document and choose the fileformat from the dropdown menu. (see
  attachment)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  8 16:59:09 2018
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1754389] [NEW] visual contrast of dropdown menu is very bad

2018-03-08 Thread Michael Kuster

Public bug reported:

This is not a specific LibreOffice problem, I saw the problem in AnyDesk
too, if you choose your language.

But in LibreOffice you can see the bug in the dialog if you save a
document and choose the fileformat from the dropdown menu. (see
attachment)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial3
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Mar  8 16:59:09 2018
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "very bad contrast.jpg"
   
https://bugs.launchpad.net/bugs/1754389/+attachment/5073135/+files/very%20bad%20contrast.jpg

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

Title:
  visual contrast of dropdown menu is very bad

Status in libreoffice package in Ubuntu:
  New

Bug description:
  This is not a specific LibreOffice problem, I saw the problem in
  AnyDesk too, if you choose your language.

  But in LibreOffice you can see the bug in the dialog if you save a
  document and choose the fileformat from the dropdown menu. (see
  attachment)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  8 16:59:09 2018
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1749086] Re: 5 minute delay on booting to login screen

2018-03-08 Thread Steve Bainton

Actually I think the problem was PSU related, my old PSU was inadequate
it seems. After replacing it, no more errors.

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

Title:
  5 minute delay on booting to login screen

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  With Xubuntu or Kubuntu the screen turns off a few seconds after
  choosing Ubuntu in grub2 menu, and sometimes the login screen takes 5
  minutes to be presented. From that point on everything seems to work
  as normal.

  Booting consistently took only a minute in Kubuntu 14.04.

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  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.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3: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.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

Re: [Desktop-packages] [Bug 1754125] Re: Rhythmbox stays running in the background after quit

2018-03-08 Thread James Benton Jr

I have tried CTRL+Q. Still does not shut down. The only way is to kill the
process.

On Wed, Mar 7, 2018 at 5:30 PM, Gustavo Silva <1754...@bugs.launchpad.net>
wrote:

> How are you closing RhythmBox? The program is not actually closed if
> music is playing and you press the X on the top right corner. Usually I
> had to do CTRL+Q if I wanted to actually shut it down. Can you try this?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1754125
>
> Title:
>   Rhythmbox stays running in the background after quit
>
> Status in rhythmbox package in Ubuntu:
>   New
>
> Bug description:
>   If you do ps -alx you will see rhythmbox process still running. It
>   causes opening rhythmbox to hang when trying to open again
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: rhythmbox 3.4.2-1ubuntu1
>   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: Wed Mar  7 13:21:51 2018
>   InstallationDate: Installed on 2018-03-07 (0 days ago)
>   InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64
> (20180307)
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: rhythmbox
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   XorgLog: Error: [Errno 2] No such file or directory:
> '/var/log/Xorg.0.log'
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/
> 1754125/+subscriptions
>

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

Title:
  Rhythmbox stays running in the background after quit

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  If you do ps -alx you will see rhythmbox process still running. It
  causes opening rhythmbox to hang when trying to open again

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rhythmbox 3.4.2-1ubuntu1
  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: Wed Mar  7 13:21:51 2018
  InstallationDate: Installed on 2018-03-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

[Desktop-packages] [Bug 1754369] Re: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()