date:20180202

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

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

Title:
  package libsane1 1.0.27-1~experimental3ubuntu1 failed to
  install/upgrade: intentando sobreescribir el compartido
  `/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias
  del paquetes libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I just update my lubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  Date: Fri Feb  2 22:49:58 2018
  ErrorMessage: intentando sobreescribir el compartido 
`/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del 
paquetes libsane1:i386
  InstallationDate: Installed on 2018-02-03 (0 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180202)
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha7ubuntu1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental3ubuntu1 failed to 
install/upgrade: intentando sobreescribir el compartido 
`/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del 
paquetes 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/1747107/+subscriptions

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

[Desktop-packages] [Bug 1747117] [NEW] package foomatic-filters 4.0.17-8 failed to install/upgrade: package foomatic-filters is not ready for configuration cannot configure (current status 'half-insta

2018-02-02 Thread shivaraj p

Public bug reported:

always shows up when any program installed

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: foomatic-filters 4.0.17-8
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Uname: Linux 4.4.0-104-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CupsErrorLog:
 
Date: Sat Feb  3 12:00:09 2018
DuplicateSignature:
 package:foomatic-filters:4.0.17-8
 Setting up libc6-dev:amd64 (2.23-0ubuntu10) ...
 dpkg: error processing package foomatic-filters (--configure):
  package foomatic-filters is not ready for configuration
ErrorMessage: package foomatic-filters is not ready for configuration  cannot 
configure (current status 'half-installed')
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
MachineType: Acer Aspire V5-572P
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=130c53b8-4124-4bd6-b2d6-9fec5721edd5 ro splash quiet
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: foomatic-filters
Title: package foomatic-filters 4.0.17-8 failed to install/upgrade: package 
foomatic-filters is not ready for configuration  cannot configure (current 
status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/08/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.01
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Dazzle_CX
dmi.board.vendor: Acer
dmi.board.version: Type2 - A01 Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.01:bd04/08/2013:svnAcer:pnAspireV5-572P:pvrV2.01:rvnAcer:rnDazzle_CX:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire V5-572P
dmi.product.version: V2.01
dmi.sys.vendor: Acer

** Affects: foomatic-filters (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package foomatic-filters 4.0.17-8 failed to install/upgrade: package
  foomatic-filters is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in foomatic-filters package in Ubuntu:
  New

Bug description:
  always shows up when any program installed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: foomatic-filters 4.0.17-8
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sat Feb  3 12:00:09 2018
  DuplicateSignature:
   package:foomatic-filters:4.0.17-8
   Setting up libc6-dev:amd64 (2.23-0ubuntu10) ...
   dpkg: error processing package foomatic-filters (--configure):
package foomatic-filters is not ready for configuration
  ErrorMessage: package foomatic-filters is not ready for configuration  cannot 
configure (current status 'half-installed')
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: Acer Aspire V5-572P
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=130c53b8-4124-4bd6-b2d6-9fec5721edd5 ro splash quiet
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: foomatic-filters
  Title: package foomatic-filters 4.0.17-8 failed to install/upgrade: package 
foomatic-filters is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.01
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Dazzle_CX
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.01:bd04/08/2013:svnAcer:pnAspireV5-572P:pvrV2.01:rvnAcer:rnDazzle_CX:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V5-572P
  dmi.product.version: V2.01
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/foomatic-filters/+bug/1747117/+subscriptions

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

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

2018-02-02 Thread Apport retracing service

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

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 #1712961, 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/1747114/+attachment/5047818/+files/CoreDump.gz

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

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

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

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

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

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

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

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

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

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

Bug description:
  running google chrome, listening to mixcloud while plain web-surfing.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.26.2-0ubuntu2
  Uname: Linux 4.15.0-041500-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  3 07:20:20 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-02-01 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171120)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fb9115f80f5 <__GI_strtoul_l_internal+53>:   
movsbq (%r14),%rax
   PC (0x7fb9115f80f5) ok
   source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   __GI_strtoul_l_internal (nptr=0x0, endptr=0x7ffeabf0aaf8, base=10, 
group=, loc=0x7fb911993800 <_nl_C_locobj>) at 
../stdlib/strtol_l.c:292
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: gnome-control-center crashed with SIGSEGV in 
__GI_strtoul_l_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1635074] Re: Nepali Keyboard symbol should have zero width joiner and non joiner

Thanks.

** Also affects: xkeyboard-config via
   https://bugs.freedesktop.org/show_bug.cgi?id=104921
   Importance: Unknown
   Status: Unknown

** Changed in: xkeyboard-config (Ubuntu)
   Status: Incomplete => New

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

Title:
  Nepali Keyboard symbol should have zero width joiner and non joiner

Status in xkeyboard-config:
  Unknown
Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  The symbols file located at '/usr/share/X11/xkb/symbols/np' doesnot
  seem to work for zero width joiner. The  'equal' key in line 22 should
  work as zero width joiner.

  'पर्=यो' is the output while it should be 'पर्‍यो' ।

  The workout seems to be replacing 'equal' in line 22 with '0x100200D'

  Also, the upper keys in numbers i.e. @,#,$,% etc are missing and
  should be available as is except for +,= where zero width joiner and
  non-joiner are used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1635074/+subscriptions

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

[Desktop-packages] [Bug 1747085] Re: NetworkManager: setting wifi.cloned-mac-address from pre-up.d fails silently for new connections

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  NetworkManager: setting wifi.cloned-mac-address from pre-up.d fails
  silently for new connections

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  network-manager 1.2.6-0ubuntu0.16.04.2

  I'm using a script in /etc/NetworkManager/dispatcher.d/pre-up.d to
  assign a pseudorandom mac address using the cloned-mac-address setting
  (via this command):

  > nmcli connection modify  wifi.cloned-mac-address
  

  (Specifically, I'm using this script:
  https://gist.github.com/paulfurley/46e0547ce5c5ea7eabeaef50dbacef3f)

  
  This works a treat for existing connections - ifconfig shows that the MAC 
address has been assigned correctly (as denoted by the leading 02):

  ```
  $ ifconfig wlp6s0
  wlp6s0Link encap:Ethernet  HWaddr 02:2a:8b:4e:ca:ef
  ```

  However if I delete that connection from Network Manager and add it
  again, the interface comes, leaking its real hardware mac address:

  ```
  $ ifconfig wlp6s0
  wlp6s0Link encap:Ethernet  HWaddr b0:35:9f:XX:XX:XX
  ```

  Theory 1: Maybe pre-up.d hooks don't run for new connections? Nope - I
  can see from the logs that the script definitely runs when I connect
  to the wifi for the first time.

  Theory 2: Maybe the Network Manager connection doesn't exist yet, so
  the script can't see it via its initial `nmcli connection show`
  command? Nope - at the top of the log is the command `nmcli connection
  modify  wifi.cloned-mac-address
  02:34:ae:08:7d:5f`

  So, in summary, setting wifi.cloned-mac-address from a pre-up.d hook
  works great for *existing* connections but appears to fail silently
  for *new* connections.

  Thanks!

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

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

[Desktop-packages] [Bug 1746004] Re: Desktop Action menus of Remmina are not translated

I figured out a hackish solution to this, which I think will work.
Building with the attached debdiff ought to give us a translation
template with the strings in the .desktop file. Then the strings can be
translated in LP, and after next update of the language packs the
strings should show up translated.

** Patch added: "remmina-translations.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1746004/+attachment/5047817/+files/remmina-translations.debdiff

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

** Changed in: remmina (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: remmina (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Tags added: patch

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

Title:
  Desktop Action menus of Remmina are not translated

Status in Ubuntu Translations:
  New
Status in remmina package in Ubuntu:
  In Progress

Bug description:
  Desktop Action menus of Remmina are not translated although they are
  fully translated in the upstream desktop file. It looks like that the
  translation is not applied for some reason. Maybe because Ubuntu is
  using gettext instead of having the translated strings directly in the
  desktop files?

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

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

[Desktop-packages] [Bug 1746638] Re: [GeForce 6150SE nForce 430] PC freezes and crashes

2018-02-02 Thread Diogo Gomes

I had a full copy of kern.log, I attached it.

(Sorry for only post last 10min in other attachment)

** Attachment added: "kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1746638/+attachment/5047802/+files/kern.log

** Attachment removed: "kern.log (10 last min before crash)"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1746638/+attachment/5047048/+files/kern%20%2810m%20before%20crash%29.log

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

Title:
  [GeForce 6150SE nForce 430] PC freezes and crashes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using the nouveau graphics driver my pc freezes and crashes.

  WORKAROUND: Use the proprietary nvidia driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-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: XFCE
  Date: Thu Feb  1 01:36:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] 
[1043:8234]
  InstallationDate: Installed on 2017-11-23 (69 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus 
CX3900/DX4000/DX4050]
   Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  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
  xserver.bootTime: Thu Feb  1 01:34:53 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 1241:1166MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1645102] Re: Allow bookmarks to launch multiple pages

2018-02-02 Thread Bug Watch Updater

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

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

Title:
  Allow bookmarks to launch multiple pages

Status in Mozilla Firefox:
  Won't Fix
Status in Ubuntu GNOME:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  I think it would be really useful if Firefox allowed you to have
  bookmarks which open multiple pages. So for instance, I have 3 news
  sites I read on a regular basis, however I don't want to have to open
  each one manually even if it's through 3 bookmarks, I also don't want
  to have them as startup pages.

  So what would be really useful for me would be just one bookmark
  titles something like "News" which upon being clicked would open 3
  separate tabs in the specified order of the pages.

  I am sure that there would be many uses for this and that others would
  also find it useful.

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

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

[Desktop-packages] [Bug 1747107] [NEW] package libsane1 1.0.27-1~experimental3ubuntu1 failed to install/upgrade: intentando sobreescribir el compartido `/lib/udev/hwdb.d/20-sane.hwdb', que es distinto

2018-02-02 Thread Don Forigua

Public bug reported:

I just update my lubuntu 18.04

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libsane1 1.0.27-1~experimental3ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
Date: Fri Feb  2 22:49:58 2018
ErrorMessage: intentando sobreescribir el compartido 
`/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del 
paquetes libsane1:i386
InstallationDate: Installed on 2018-02-03 (0 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180202)
Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.19.0.4ubuntu1
 apt  1.6~alpha7ubuntu1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental3ubuntu1 failed to 
install/upgrade: intentando sobreescribir el compartido 
`/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del 
paquetes libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package libsane1 1.0.27-1~experimental3ubuntu1 failed to
  install/upgrade: intentando sobreescribir el compartido
  `/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias
  del paquetes libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I just update my lubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  Date: Fri Feb  2 22:49:58 2018
  ErrorMessage: intentando sobreescribir el compartido 
`/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del 
paquetes libsane1:i386
  InstallationDate: Installed on 2018-02-03 (0 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180202)
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha7ubuntu1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental3ubuntu1 failed to 
install/upgrade: intentando sobreescribir el compartido 
`/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del 
paquetes 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/1747107/+subscriptions

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

[Desktop-packages] [Bug 1635074] Re: Nepali Keyboard symbol should have zero width joiner and non joiner

2018-02-02 Thread Sagar Chalise

Reported bug upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=104921

** Bug watch added: freedesktop.org Bugzilla #104921
   https://bugs.freedesktop.org/show_bug.cgi?id=104921

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

Title:
  Nepali Keyboard symbol should have zero width joiner and non joiner

Status in xkeyboard-config package in Ubuntu:
  Incomplete

Bug description:
  The symbols file located at '/usr/share/X11/xkb/symbols/np' doesnot
  seem to work for zero width joiner. The  'equal' key in line 22 should
  work as zero width joiner.

  'पर्=यो' is the output while it should be 'पर्‍यो' ।

  The workout seems to be replacing 'equal' in line 22 with '0x100200D'

  Also, the upper keys in numbers i.e. @,#,$,% etc are missing and
  should be available as is except for +,= where zero width joiner and
  non-joiner are used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1635074/+subscriptions

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

[Desktop-packages] [Bug 1746859] Re: gnome-shell wayland is spamming syslog with wl_ messages

2018-02-02 Thread Rocko

Oops, I had MUTTER_VERBOSE=1 and MUTTER_DEBUG=1. I also had
MUTTER_USE_LOGFILE=/tmp/mutterlogs, and there were mutter log messages
definitely going to /tmp, so it's surprising I was getting so much spam
in /var/log/syslog.

With those turned off, I'm not getting constant spam but I do still get
a lot of messages in syslog like so:

Feb  3 11:20:31 xps15-9560 org.gnome.Shell.desktop[2297]: #11 0x7fff4db73230 I  
 self-hosted:917 (0x7feebc3ee5e8 @ 394)
Feb  3 11:20:31 xps15-9560 org.gnome.Shell.desktop[2297]: == Stack trace for 
context 0x5654e9533000 ==
Feb  3 11:20:31 xps15-9560 org.gnome.Shell.desktop[2297]: #0 0x7fff4db71cc0 b   
resource:///org/gnome/shell/ui/tweener.js:80 (0x7feebc3ddef0 @ 82)
Feb  3 11:20:31 xps15-9560 org.gnome.Shell.desktop[2297]: #1 0x7fff4db71d60 b   
resource:///org/gnome/shell/ui/tweener.js:105 (0x7feebc3df230

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

Title:
  gnome-shell wayland is spamming syslog with wl_ messages

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Whenever I run gnome-shell under wayland now in Ubuntu 18.04, I get
  thousands of messages in syslog like this:

  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769569.758] 
wl_callb...@48.done(9760355)
  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769618.845]  -> 
wl_surface@31.attach(wl_buffer@50, 0, 0)
  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769618.888]  -> 
wl_surface@31.set_buffer_scale(2)
  wl_surface@31.set_input_region(wl_region@48)
  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769619.235]  -> 
wl_surface@31.frame(new id wl_callback@44)
  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769619.252]  -> 
wl_surface@31.commit()
  Feb  2 11:52:44 xps15-9560 org.gnome.Shell.desktop[31805]: [2769619.277] 
wl_surface@31.set_input_region(wl_region@48)
  Feb  2 11:52:44 xps15-9560 org.gnome.Shell.desktop[31805]: [2769619.286] 
wl_region@48.destroy()
  Feb  2 11:52:44 xps15-9560 org.gnome.Shell.desktop[31805]: [2769619.293]  -> 
wl_display@1.delete_id(48)
  Feb  2 11:52:44 xps15-9560 org.gnome.Shell.desktop[31805]: [2769619.342] 
wl_surface@31.frame(new id wl_display@1.delete_id(44)
  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769629.628] 
wl_display@1.delete_id(44)
  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769629.669] 
wl_keybo...@28.key(344, 9760410, 46, 1)
  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769629.727] 
wl_callb...@44.done(9760414)

  This didn't used to happen and it doesn't happen running under X.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  Uname: Linux 4.15.0-041500-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  2 11:53:30 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-16 (169 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2017-11-17 (76 days ago)

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

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

[Desktop-packages] [Bug 1745619] Re: Failed to open local calendar with "Timeout was reached"

2018-02-02 Thread Aram Agajanian

I had a similar problem on Fedora 26 which seems to have gone away after
I killed the evolution-calendar-factory process.

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

Title:
  Failed to open local calendar with "Timeout was reached"

Status in evolution package in Ubuntu:
  New

Bug description:
  After booting into a GNOME session, Evolution was started. Mail
  appeared as expected. When the Calendar section was opened, none of
  the calendars opened including the local calendar. A blue report was
  printed under the toolbar with the error that it could not open the
  local calendar as "Timeout was reached." It seems odd that there
  should be a timeout issue when accessing local data. The local
  calendar is stored on the save drive and mount point as the OS and
  Evolution.

  Closing and reopening Evolution did not resolve the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evolution 3.26.1-1
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jan 26 09:12:29 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/evolution
  InstallationDate: Installed on 2017-08-12 (166 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: evolution
  UpgradeStatus: Upgraded to artful on 2017-10-21 (96 days ago)

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

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

[Desktop-packages] [Bug 1316970] Re: g_dbus memory leak in lrmd

2018-02-02 Thread Seyeong Kim

** Patch added: "lp1316970_trusty_pacemaker_v2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1316970/+attachment/5047782/+files/lp1316970_trusty_pacemaker_v2.debdiff

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

Title:
  g_dbus memory leak in lrmd

Status in glib2.0 package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Trusty:
  New
Status in pacemaker source package in Trusty:
  In Progress

Bug description:
  [Impact]
  lrmd daemon with upstart resource has memory leak in Trusty

  affected to pacemaker 1.1.10.
  affected to glib2.0 2.40.2-0ubuntu1

  Please note that patch for pacemaker is created myself.

  [Test Case]

  1. deploy 3 trusty instance.
  2. install corosync, pacemaker, mysql.
  3. setting with below info
  3.1 corosync.conf, proper setting for 3 node
  3.2 crm configure < setup.crm ( which has upstart:mysql setting )
  3.3 monitor lrmd daemon's memory usage

  [Regression]
  Restarting daemon after upgrading this pkg will be needed. this patch added 
NULL check for several parts. prior commit[1] changed file structure. and This 
change makes user changes usage of upstart:mysql to lsb:mysql. So I added free 
function myself. This might affect to system.
  For glib2.0, commit [1] is critical, but [2],[3],[4] is needed for building 
it.

  [Others]

  Related commits.

  [1] commit a7b61e276120184c7586a3217ed3571a982f5017
  Author: Andrew Beekhof 
  Date:   Fri Aug 23 16:25:35 2013 +1000

  Refactor: attrd: Move to its own directory and create a stub for
  attrd-ng

  --
  $ git describe --contains a1a6922e43dfe80b23887a88401cbb93fe3645c0
  Pacemaker-1.1.11-rc3

  $ git describe --contains a7b61e276120184c7586a3217ed3571a982f5017
  Pacemaker-1.1.11-rc1~168

  $ rmadison pacemaker
   pacemaker | 1.1.10+git20130802-1ubuntu2   | trusty
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates

   pacemaker | 1.1.14-2ubuntu1   | xenial
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-security
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-update
   pacemaker | 1.1.16-1ubuntu1   | zesty
   pacemaker | 1.1.16-1ubuntu1   | artful
   pacemaker | 1.1.18~rc3-1ubuntu1   | bionic
  --

  For glib
  [1] 
https://github.com/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c
  [2] 
https://github.com/GNOME/glib/commit/8792609e15394967cab526838b83f90acb401663
  [3] 
https://github.com/GNOME/glib/commit/ec02a1875f29ecb8e46c0d8c1403cd00a0b3a9e4
  [4] 
https://github.com/GNOME/glib/commit/f10b6550ff2ce55d06b92d6dc3e443fc007b2f7a

  [Original Description]

  I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy
  (13.10) and have encountered a memory leak in lrmd.

  The details of the bug are covered here in this thread
  (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html)
  but to summarise, the Pacemaker developers believe the leak is caused
  by the g_dbus API, the use of which was removed in Pacemaker 1.11.

  I've also attached the Valgrind output from the run that exposed the
  issue.

  Given that this issue affects production stability (a periodic restart
  of Pacemaker is required), will a version of 1.11 be released for
  Trusty? (I'm happy to upgrade the OS to Trusty to get it).

  If not, can you advise which version of the OS will be the first to
  take 1.11 please?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+subscriptions

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

[Desktop-packages] [Bug 1316970] Re: g_dbus memory leak in lrmd

2018-02-02 Thread Seyeong Kim

Hello ddstreet

Thanks for the review.

I changed some code for pacemaker. ( char -> gchar for matching type,
with g_free)

and glib2.0 patch is needed in my test.

without it, memory leak is there. 4kB leak every 10 second at least.

Thanks.

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

Title:
  g_dbus memory leak in lrmd

Status in glib2.0 package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Trusty:
  New
Status in pacemaker source package in Trusty:
  In Progress

Bug description:
  [Impact]
  lrmd daemon with upstart resource has memory leak in Trusty

  affected to pacemaker 1.1.10.
  affected to glib2.0 2.40.2-0ubuntu1

  Please note that patch for pacemaker is created myself.

  [Test Case]

  1. deploy 3 trusty instance.
  2. install corosync, pacemaker, mysql.
  3. setting with below info
  3.1 corosync.conf, proper setting for 3 node
  3.2 crm configure < setup.crm ( which has upstart:mysql setting )
  3.3 monitor lrmd daemon's memory usage

  [Regression]
  Restarting daemon after upgrading this pkg will be needed. this patch added 
NULL check for several parts. prior commit[1] changed file structure. and This 
change makes user changes usage of upstart:mysql to lsb:mysql. So I added free 
function myself. This might affect to system.
  For glib2.0, commit [1] is critical, but [2],[3],[4] is needed for building 
it.

  [Others]

  Related commits.

  [1] commit a7b61e276120184c7586a3217ed3571a982f5017
  Author: Andrew Beekhof 
  Date:   Fri Aug 23 16:25:35 2013 +1000

  Refactor: attrd: Move to its own directory and create a stub for
  attrd-ng

  --
  $ git describe --contains a1a6922e43dfe80b23887a88401cbb93fe3645c0
  Pacemaker-1.1.11-rc3

  $ git describe --contains a7b61e276120184c7586a3217ed3571a982f5017
  Pacemaker-1.1.11-rc1~168

  $ rmadison pacemaker
   pacemaker | 1.1.10+git20130802-1ubuntu2   | trusty
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates

   pacemaker | 1.1.14-2ubuntu1   | xenial
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-security
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-update
   pacemaker | 1.1.16-1ubuntu1   | zesty
   pacemaker | 1.1.16-1ubuntu1   | artful
   pacemaker | 1.1.18~rc3-1ubuntu1   | bionic
  --

  For glib
  [1] 
https://github.com/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c
  [2] 
https://github.com/GNOME/glib/commit/8792609e15394967cab526838b83f90acb401663
  [3] 
https://github.com/GNOME/glib/commit/ec02a1875f29ecb8e46c0d8c1403cd00a0b3a9e4
  [4] 
https://github.com/GNOME/glib/commit/f10b6550ff2ce55d06b92d6dc3e443fc007b2f7a

  [Original Description]

  I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy
  (13.10) and have encountered a memory leak in lrmd.

  The details of the bug are covered here in this thread
  (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html)
  but to summarise, the Pacemaker developers believe the leak is caused
  by the g_dbus API, the use of which was removed in Pacemaker 1.11.

  I've also attached the Valgrind output from the run that exposed the
  issue.

  Given that this issue affects production stability (a periodic restart
  of Pacemaker is required), will a version of 1.11 be released for
  Trusty? (I'm happy to upgrade the OS to Trusty to get it).

  If not, can you advise which version of the OS will be the first to
  take 1.11 please?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+subscriptions

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

[Desktop-packages] [Bug 1745784] Re: package libvlc-bin:amd64 3.0.0~rc4-1ubuntu1 failed to install/upgrade: triggers looping, abandoned

2018-02-02 Thread Sebastian Ramacher

The trigger loop is detected between gnome-icon-theme and bamfdeamon. So
reassigning there.

** Package changed: vlc (Ubuntu) => gnome-icon-theme (Ubuntu)

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

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

Title:
  package libvlc-bin:amd64 3.0.0~rc4-1ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in bamf package in Ubuntu:
  New
Status in gnome-icon-theme package in Ubuntu:
  New

Bug description:
  after restart of upgrade to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libvlc-bin:amd64 3.0.0~rc4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Sun Jan 28 00:49:10 2018
  ErrorMessage: triggers looping, abandoned
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  SourcePackage: vlc
  Title: package libvlc-bin:amd64 3.0.0~rc4-1ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-01-27 (0 days ago)

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

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

[Desktop-packages] [Bug 1745784] [NEW] package libvlc-bin:amd64 3.0.0~rc4-1ubuntu1 failed to install/upgrade: triggers looping, abandoned

You have been subscribed to a public bug:

after restart of upgrade to 18.04

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libvlc-bin:amd64 3.0.0~rc4-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
Date: Sun Jan 28 00:49:10 2018
ErrorMessage: triggers looping, abandoned
Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
SourcePackage: vlc
Title: package libvlc-bin:amd64 3.0.0~rc4-1ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: Upgraded to bionic on 2018-01-27 (0 days ago)

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


** Tags: amd64 apport-package bionic third-party-packages
-- 
package libvlc-bin:amd64 3.0.0~rc4-1ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
https://bugs.launchpad.net/bugs/1745784
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-icon-theme in Ubuntu.

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

[Desktop-packages] [Bug 1747094] [NEW] alsactl --file ./config.txt store does not save Monitor of Built-in Audio Analog Stereo level

2018-02-02 Thread Eduardo

Public bug reported:

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename:   xenial

Steps to reproduce the bug:

1. Click on the volume icon on the pannel, and then on Sound Settings
2. Click on label Input, then on Monitor of Built-in Analog Stereo, under 
Choose a Device for Sound Input
3. Move the slider above (input ...) to, say, about 50%
4. Type in a console: alsactl --file ~/.config/asound.state store
5. Move the aforementioned slider to 100% or anywhere else.
6. Type in a console: alsactl --file ~/.config/asound.state restore
7. Look at the slider. It should have been restored to 50% but it hasn't been.

apt-cache policy alsa-utils:
alsa-utils:
  Installed: 1.1.0-0ubuntu5
  Candidate: 1.1.0-0ubuntu5
  Version table:
 *** 1.1.0-0ubuntu5 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   eguerras   1767 F...m pulseaudio
 /dev/snd/pcmC0D0p:   eguerras   1767 F...m pulseaudio
 /dev/snd/controlC0:  eguerras   1767 F pulseaudio
CurrentDesktop: MATE
Date: Fri Feb  2 16:44:00 2018
InstallationDate: Installed on 2018-01-28 (5 days ago)
InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
Symptom_Type: None of the above
Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/06/2012
dmi.bios.vendor: Acer
dmi.bios.version: V2.08
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Mimic
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.08
dmi.modalias: 
dmi:bvnAcer:bvrV2.08:bd11/06/2012:svnAcer:pnV5-171:pvrV2.08:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.08:
dmi.product.name: V5-171
dmi.product.version: V2.08
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug xenial

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

Title:
  alsactl --file ./config.txt store does not save Monitor of Built-in
  Audio Analog Stereo level

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  Steps to reproduce the bug:

  1. Click on the volume icon on the pannel, and then on Sound Settings
  2. Click on label Input, then on Monitor of Built-in Analog Stereo, under 
Choose a Device for Sound Input
  3. Move the slider above (input ...) to, say, about 50%
  4. Type in a console: alsactl --file ~/.config/asound.state store
  5. Move the aforementioned slider to 100% or anywhere else.
  6. Type in a console: alsactl --file ~/.config/asound.state restore
  7. Look at the slider. It should have been restored to 50% but it hasn't been.

  apt-cache policy alsa-utils:
  alsa-utils:
Installed: 1.1.0-0ubuntu5
Candidate: 1.1.0-0ubuntu5
Version table:
   *** 1.1.0-0ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   eguerras   1767 F...m pulseaudio
   /dev/snd/pcmC0D0p:   eguerras   1767 F...m pulseaudio
   /dev/snd/controlC0:  eguerras   1767 F pulseaudio
  CurrentDesktop: MATE
  Date: Fri Feb  2 16:44:00 2018
  InstallationDate: Installed on 2018-01-28 (5 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: None of the above
  Title: [HDA-Intel - HD

[Desktop-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

2018-02-02 Thread Brian Murray

You could try passing a core file to apport when there is not a
graphical shell running via a command like the following:

/usr/share/apport/apport < $my-pretend.core

With that you should get a .crash file in /var/crash. Here's an example
where 11736 was a running xeyes process and core was real crashdump
file.

 $ /usr/share/apport/apport 11736 11 0 1 < /etc/X11/core
ERROR: apport (pid 11743) Fri Feb  2 14:47:35 2018: called for pid 11736, 
signal 11, core limit 0, dump mode 1
ERROR: apport (pid 11743) Fri Feb  2 14:47:35 2018: executable: /usr/bin/xeyes 
(command line "xeyes")
ERROR: apport (pid 11743) Fri Feb  2 14:47:35 2018: debug: session gdbus call: 
(true,)

ERROR: apport (pid 11743) Fri Feb  2 14:47:49 2018: wrote report
/var/crash/_usr_bin_xeyes.1000.crash

Keep in mind that if you stop the apport service
/proc/sys/kernel/core_pattern will revert back to the default which is
just core.

 $ cat /proc/sys/kernel/core_pattern
core

So it's likely apport wasn't running on the system and is not the issue.

** Changed in: apport (Ubuntu)
   Status: Confirmed => 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/1746874

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1724250] Re: gnome-terminal graphic artifact

2018-02-02 Thread Michael Vescovo

I'm not sure how to reply to individual comments but to add to comment
#4, I am the person who reported this on askubuntu and the 4th button is
the menu button. I use Gnome Tweaks and have "Application Menu" turned
off under the "Top Bar" settings. I'm not on my work machine now so I
can't see what happens if I turn it back on or uninstall Gnome Tweaks.
I'll try it next week and report back. Having said that, I also use
Gnome Tweaks at home and don't see the issue here.

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

Title:
  gnome-terminal graphic artifact

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Opening gnome-terminal in Ubuntu 17.10 shows the terminal window with
  a graphic artifact on the right of the title bar, where the window
  buttons to minimize, maximize and close are.

  The window buttons are working so this is just a visual glitch and
  does not otherwise affect gnome-terminal functionalities.

  It does not matter whether the gnome-terminal window is maximized or
  not, the graphic artifact is always present and does not disappear
  hovering on it with the mouse.

  Other applications do not appear to be affected, only gnome-terminal.

  I'm using NVIDIA Corporation GM204M [GeForce GTX 970M] with the NVIDIA
  binary driver 384.90.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 15:37:42 2017
  InstallationDate: Installed on 2017-10-01 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1579543] Re: Firefox 46 is missing network shares in file selector

2018-02-02 Thread Paulo Villi

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

I can confirm the exact same behavior is also present on Linux Mint
Cinnamon 17.3 to 18.3 (currently at Firefox version 58.0) and it has
been like this for at least the last 1 and a half years.

The workaround described on comment #4 works perfectly but cannot be
considered proper default behavior.

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

Title:
  Firefox 46 is missing network shares in file selector

Status in Mozilla Firefox:
  In Progress
Status in GTK+:
  Confirmed
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Expected behavior:
  Firefox file selection windows show network shares mounted via Nautilus (i.e. 
gvfs SMB mounts).

  Actual behavior:
  File selection window only shows local folders.

  Steps to reproduce:
  * Go to menu File -> Open File (or start a download so that the file saving 
dialog is shown).
  * Observe the locations shortcuts offered in the left side of the selection 
window.

  Version information:
  * Vanilla Ubuntu Firefox package with Firefox 46.0.
  * Stock Ubuntu 16.04 installed on a blank machine.

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

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

[Desktop-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

2018-02-02 Thread Brian Murray

Information from 'journalctl -u apport' around the time of the core
file's creation would be useful or /var/log/apport.log if apport was
really running.

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1490738] Re: Lithuanian keyboard doesn't switch on

Thanks for your report.

This is not something I can reproduce; the Lithuanian keyboard layout
works as expected for me.

Do you still have the problem? If you have, can you please provide some
more details about the Ubuntu version and desktop environment where you
encounter the issue.

** Changed in: xkeyboard-config (Ubuntu)
   Status: New => Incomplete

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

Title:
  Lithuanian keyboard doesn't switch on

Status in xkeyboard-config package in Ubuntu:
  Incomplete

Bug description:
  Lithuanian keyboard gives no Lithuanian symbols. Using SUPER+SPACE it
  does change language indicator on the upper right corner of the
  desktop, but there's no Lt symbols where they are supposed to be.

  Lt symbols should be on the keyboard's upper number line. The symbol
  map still claims they are there. In matter of fact, when I switch to
  Lt keyboard, it still uses Finnish symbols. Finnish is my main
  keyboard at the moment.

  Before that, there were Russian symbols instead of Lt. So I
  uninstalled Rus keyboard. That caused Lt keyboard to show English
  symbols. After uninstalling Eng, now Lt keyboard is sticking with Fin.
  Adding new languages doesn't change behaviour (still Fi).

  Other languages on keyboard work fine. Uninstalling all keyboards
  except Lt, still makes no Lithuanian symbols.

  I tried uninstall Lithuanian keyboard (with reboot) and install again.
  Also tried different Lithuanian keyboards.

  Ubuntu 14.04.3 LTS 64-bit on MSI GE620DX laptop.

  (That's my first bug report, hope I'm doing it as it's supposed to be
  done.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1490738/+subscriptions

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

[Desktop-packages] [Bug 1635074] Re: Nepali Keyboard symbol should have zero width joiner and non joiner

Thanks for your report!

If you think there is a need to modify the Nepali keyboard layout, I
have to ask you to request that change upstream, more specifically here:

https://bugs.freedesktop.org/buglist.cgi?component=General&product
=xkeyboard-config&resolution=---

If you do, please post a comment here with a link to the upstream bug
report.

It's worth mentioning that if you install the ibus-m17n package, a
couple of IBus input methods for Nepali are made available. One of those
may fit your needs better.

** Changed in: xkeyboard-config (Ubuntu)
   Status: New => Incomplete

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

Title:
  Nepali Keyboard symbol should have zero width joiner and non joiner

Status in xkeyboard-config package in Ubuntu:
  Incomplete

Bug description:
  The symbols file located at '/usr/share/X11/xkb/symbols/np' doesnot
  seem to work for zero width joiner. The  'equal' key in line 22 should
  work as zero width joiner.

  'पर्=यो' is the output while it should be 'पर्‍यो' ।

  The workout seems to be replacing 'equal' in line 22 with '0x100200D'

  Also, the upper keys in numbers i.e. @,#,$,% etc are missing and
  should be available as is except for +,= where zero width joiner and
  non-joiner are used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1635074/+subscriptions

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

[Desktop-packages] [Bug 1747085] [NEW] NetworkManager: setting wifi.cloned-mac-address from pre-up.d fails silently for new connections

2018-02-02 Thread Paul M Furley

Public bug reported:

network-manager 1.2.6-0ubuntu0.16.04.2

I'm using a script in /etc/NetworkManager/dispatcher.d/pre-up.d to
assign a pseudorandom mac address using the cloned-mac-address setting
(via this command):

> nmcli connection modify  wifi.cloned-mac-address


(Specifically, I'm using this script:
https://gist.github.com/paulfurley/46e0547ce5c5ea7eabeaef50dbacef3f)


This works a treat for existing connections - ifconfig shows that the MAC 
address has been assigned correctly (as denoted by the leading 02):

```
$ ifconfig wlp6s0
wlp6s0Link encap:Ethernet  HWaddr 02:2a:8b:4e:ca:ef
```

However if I delete that connection from Network Manager and add it
again, the interface comes, leaking its real hardware mac address:

```
$ ifconfig wlp6s0
wlp6s0Link encap:Ethernet  HWaddr b0:35:9f:XX:XX:XX
```

Theory 1: Maybe pre-up.d hooks don't run for new connections? Nope - I
can see from the logs that the script definitely runs when I connect to
the wifi for the first time.

Theory 2: Maybe the Network Manager connection doesn't exist yet, so the
script can't see it via its initial `nmcli connection show` command?
Nope - at the top of the log is the command `nmcli connection modify
 wifi.cloned-mac-address 02:34:ae:08:7d:5f`

So, in summary, setting wifi.cloned-mac-address from a pre-up.d hook
works great for *existing* connections but appears to fail silently for
*new* connections.

Thanks!

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

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

Title:
  NetworkManager: setting wifi.cloned-mac-address from pre-up.d fails
  silently for new connections

Status in network-manager package in Ubuntu:
  New

Bug description:
  network-manager 1.2.6-0ubuntu0.16.04.2

  I'm using a script in /etc/NetworkManager/dispatcher.d/pre-up.d to
  assign a pseudorandom mac address using the cloned-mac-address setting
  (via this command):

  > nmcli connection modify  wifi.cloned-mac-address
  

  (Specifically, I'm using this script:
  https://gist.github.com/paulfurley/46e0547ce5c5ea7eabeaef50dbacef3f)

  
  This works a treat for existing connections - ifconfig shows that the MAC 
address has been assigned correctly (as denoted by the leading 02):

  ```
  $ ifconfig wlp6s0
  wlp6s0Link encap:Ethernet  HWaddr 02:2a:8b:4e:ca:ef
  ```

  However if I delete that connection from Network Manager and add it
  again, the interface comes, leaking its real hardware mac address:

  ```
  $ ifconfig wlp6s0
  wlp6s0Link encap:Ethernet  HWaddr b0:35:9f:XX:XX:XX
  ```

  Theory 1: Maybe pre-up.d hooks don't run for new connections? Nope - I
  can see from the logs that the script definitely runs when I connect
  to the wifi for the first time.

  Theory 2: Maybe the Network Manager connection doesn't exist yet, so
  the script can't see it via its initial `nmcli connection show`
  command? Nope - at the top of the log is the command `nmcli connection
  modify  wifi.cloned-mac-address
  02:34:ae:08:7d:5f`

  So, in summary, setting wifi.cloned-mac-address from a pre-up.d hook
  works great for *existing* connections but appears to fail silently
  for *new* connections.

  Thanks!

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

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

[Desktop-packages] [Bug 1578657] Re: spanish keyboard not accentuating vowels

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

Thanks for your report, Michael. The behavior you describe is apparently
not correct. There is a subtle issue regarding dead keys, and I mark
this bug  as a duplicate of that other bug report. You may want to study
it and try some of the workarounds mentioned.

** This bug has been marked a duplicate of bug 1573755
   Compose and dead keys stopped working with XIM after upgrade to 16.04

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

Title:
  spanish keyboard not accentuating vowels

Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  I've already added the Spanish language keyboard to unity and the keyboard 
indicator at the top indicates the Spanish keyboard and I do get Ñ and ñ
  however when I go to accentuate a vowel áéíóú it's not working

  the normal process is that I press the apostrophe key (in the us keyboard it 
would be two keys toward the right from "L") then select the vowel to be 
accentuated. 
  however you're not supposed to see anything until the vowel is selected.

  what is happening instead is that I'm getting an apostrophe right away
  when I press the tilde key.

  
  NOTE0:
  I've tested also other variants of the Spanish layout with similar success..

  NOTE1:
  I have installed cinnamon also and when I login to cinnamon it works, so I'm 
only experiencing the issue in unity.

  NOTE2:
  I'm very proficient with computers and have successfully done this many times.

  NOTE3: 
  I'm working on a fairly clean setup of Ubuntu 16.04 LTS
   I've only added Cinnamon and the Intel Drivers to the system and google 
chrome 
   system is also up to date.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1578657/+subscriptions

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

[Desktop-packages] [Bug 1660072] Re: Missing depends on xkb-data-i18n

The ubiquity source package, which is used to build the installers,
depends on xkb-data-i18n for building.

https://packages.ubuntu.com/source/bionic/ubiquity

That's apparently the reason why xkb-data-i18n exists. Closing.

** Changed in: xkeyboard-config (Ubuntu)
   Status: New => Invalid

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

Title:
  Missing depends on xkb-data-i18n

Status in xkeyboard-config package in Ubuntu:
  Invalid

Bug description:
  A reverse depends for xkb-data-i18n shows that nothing depends on it.

  Surely xkb-data should depend or recommend it's installation?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1660072/+subscriptions

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

[Desktop-packages] [Bug 854959] Re: Connect to windows share: gvfs slow, smbclient fast

still present in 16.04 64 bit as well :-(
This has been around for 7 years now. No wonder not that many people switch to 
Linux

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

Title:
  Connect to windows share: gvfs slow, smbclient fast

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  If I connect to a windows share using Places | Connect To Server |
  Windows Share (aka GVFS), a file copies from the server to my machine
  at 1 MB/sec

  If I connect to the same windows share from the same computer using a
  console "smbclient", the file copies at 15 MB/sec.

  Since smbclient can copy the same file from the same server to the
  same harddrive 15X faster than gvfs, there must be a problem with
  gvfs.

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

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

[Desktop-packages] [Bug 854959] Re: Connect to windows share: gvfs slow, smbclient fast

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

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

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

Title:
  Connect to windows share: gvfs slow, smbclient fast

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  If I connect to a windows share using Places | Connect To Server |
  Windows Share (aka GVFS), a file copies from the server to my machine
  at 1 MB/sec

  If I connect to the same windows share from the same computer using a
  console "smbclient", the file copies at 15 MB/sec.

  Since smbclient can copy the same file from the same server to the
  same harddrive 15X faster than gvfs, there must be a problem with
  gvfs.

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

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

[Desktop-packages] [Bug 854959] Re: Connect to windows share: gvfs slow, smbclient fast

Still present in 16.04 64-bit :-(

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

Title:
  Connect to windows share: gvfs slow, smbclient fast

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  If I connect to a windows share using Places | Connect To Server |
  Windows Share (aka GVFS), a file copies from the server to my machine
  at 1 MB/sec

  If I connect to the same windows share from the same computer using a
  console "smbclient", the file copies at 15 MB/sec.

  Since smbclient can copy the same file from the same server to the
  same harddrive 15X faster than gvfs, there must be a problem with
  gvfs.

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

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

[Desktop-packages] [Bug 1236619] Re: gvfs smb / cifs file copy performance is terribly slow

This problem still exists in 16.04 64-bit as well, and has been around
for about 7 years

https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/854959

This is a serious mark against switching to Linux, the mount -t cifs
option is nice for power users, but not for not so much tech-savy users.

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

Title:
  gvfs smb / cifs file copy performance is terribly slow

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Copying moderate-size files to a samba share using gvfs is
  ridiculously slow compared to doing the same via mount.cifs.  For
  example:

  $ ls -sh testfile
  1.2G testfile
  $ time cp testfile ~/mnt/share-gvfs/
  real  2m37.053s
  user  0m0.056s
  sys   0m5.120s
  $ time cp testfile ~/mnt/share/
  real  0m26.134s
  user  0m0.004s
  sys   0m1.724s

  I'm running Xubuntu 13.04 (raring) amd64, gvfs 1.16.1-0ubuntu1.1.

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

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

[Desktop-packages] [Bug 259771] Re: Browsing smb share is painfully slow

Ubuntu 16.04 still shows this behavior. :-(
Makes a very big argument against switching to Linux

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

Title:
  Browsing smb share is painfully slow

Status in gvfs:
  New
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gvfs

  I would like to open a new bug with the same issue as bug #186461,
  browsing samba shares is painfully slow.

  I don't notice this at home on my 100Mbit network with no so much
  directories but at work, over a 10Mbit leased line and hundreds of
  directories on a share, every operation takes 10-15 seconds until you
  get a bit deeper into the hierarchy inside a directory with only a
  couple of directories/files in it.

  $ lsb_release -rd
  Description:   Ubuntu 8.04.1
  Release:8.04

  $ dpkg -l | grep gvfs
  ii  gvfs   0.2.5-0ubuntu2 
userspace virtual filesystem - server

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

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

[Desktop-packages] [Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time

2018-02-02 Thread Chelmite

If I press the Ubuntu key over and over, showing the overview of all the
desktops, and then again to return to the normal view of the current
desktop, RSS for gnome-desktop increases rapidly (measurements taken at
15-second intervals.

USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
skelem   15805  9.0  1.2 4776896 820820 tty2   Sl+  10:10  12:27 
/usr/bin/gnome-shell
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
skelem   15805  9.0  1.2 4790452 831004 tty2   Rl+  10:10  12:31 
/usr/bin/gnome-shell
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
skelem   15805  9.1  1.2 4799632 849868 tty2   Sl+  10:10  12:36 
/usr/bin/gnome-shell
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
skelem   15805  9.1  1.3 4807764 859832 tty2   Sl+  10:10  12:42 
/usr/bin/gnome-shell
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
skelem   15805  9.2  1.3 4812364 865236 tty2   Sl+  10:10  12:46 
/usr/bin/gnome-shell

After kill -1 15805, I get:
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
skelem   27800 14.5  0.5 4072104 362428 tty2   Sl+  12:31   0:06 
/usr/bin/gnome-shell

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

Title:
  gnome-shell uses lots of memory, and grows over time

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
  almost 2 GiB.

  user  3039  1.8 16.1 4302340 1968476 tty2  Sl+  Mar09 120:17
  /usr/bin/gnome-shell

  strace output is voluminous; here is a representative sample:

  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\231\n\10\0\n\0 
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0 
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  open("/proc/self/stat", O_RDONLY)   = 36
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  fcntl(36, F_GETFL)  = 0x8000 (flags O_RDONLY|O_LARGEFILE)
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
  read(36, "", 3072)  = 0
  close(36)   = 0
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60

[Desktop-packages] [Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time

2018-02-02 Thread Chelmite

I'm trying to track down something that makes system performance degrade
in less than an hour. Whenever I switch desktops, move my cursor to a
place where a tooltip is displayed, open a pull-down menu, the display
freezes for 5-15 seconds before, for example, the menu or tooltip is
released.

If I kill -1 my gnome-shell, performance is restored...for a while.

I decided to take some measurements.
% ps guax | grep gnome-shell
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
skelem   15805  6.3  0.6 4037064 401804 tty2   Rl+  10:10   1:07 
/usr/bin/gnome-shell

The VSZ and RSS grow slowly, if at all, if I don't switch desktops, bring up 
menus, etc. Here are snapshots at 15 second intervals:
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
skelem   15805  8.5  1.3 4755216 862708 tty2   Sl+  10:10  10:41 
/usr/bin/gnome-shell
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
skelem   15805  8.5  1.3 4755216 862912 tty2   Sl+  10:10  10:42 
/usr/bin/gnome-shell
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
skelem   15805  8.5  1.3 4755216 862912 tty2   Sl+  10:10  10:43 
/usr/bin/gnome-shell
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
skelem   15805  8.5  1.3 4755216 863128 tty2   Sl+  10:10  10:44 
/usr/bin/gnome-shell
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
skelem   15805  8.5  1.3 4755216 863344 tty2   Sl+  10:10  10:45 
/usr/bin/gnome-shell

After 2 hours, the ps reports go from
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
skelem   15805  6.3  0.6 4037064 401804 tty2   Rl+  10:10   1:07 
/usr/bin/gnome-shell

to
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
skelem   15805  8.7  1.2 4725708 821640 tty2   Rl+  10:10  11:27 
/usr/bin/gnome-shell

VSZ increases by 688.6K, or 17%.
RSS increases by 419.8K, or 104%

I'm running GNOME Shell 3.26.2 on Ubuntu 17.10 x86-64.

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

Title:
  gnome-shell uses lots of memory, and grows over time

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
  almost 2 GiB.

  user  3039  1.8 16.1 4302340 1968476 tty2  Sl+  Mar09 120:17
  /usr/bin/gnome-shell

  strace output is voluminous; here is a representative sample:

  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\231\n\10\0\n\0 
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0 
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=

[Desktop-packages] [Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time

2018-02-02 Thread Chelmite

Regarding #32, The total shown is 16,293,840 and used is 1,781,036,
which is about 11% of the total, not more than total. (With that many
digits, commas help.)

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

Title:
  gnome-shell uses lots of memory, and grows over time

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
  almost 2 GiB.

  user  3039  1.8 16.1 4302340 1968476 tty2  Sl+  Mar09 120:17
  /usr/bin/gnome-shell

  strace output is voluminous; here is a representative sample:

  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\231\n\10\0\n\0 
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0 
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  open("/proc/self/stat", O_RDONLY)   = 36
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  fcntl(36, F_GETFL)  = 0x8000 (flags O_RDONLY|O_LARGEFILE)
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
  read(36, "", 3072)  = 0
  close(36)   = 0
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 117885) = 
1 ([{fd=4, revents=POLLIN}])
  read(4, "\1\0\0\0\0\0\0\0", 16) = 8
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, {msg_name(0)=NULL, 
msg_iov(1)=[{"[\2\327&h\0@\0i\0@\0(nu\22\n\0I\0\336\2\232\1\265\0038\2\362\2\355\1",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLL

[Desktop-packages] [Bug 1480673] Re: [ELAN 3320KD-3100] Asus T300 CHI bluetooth Touchpad is recognized incorrectly

2018-02-02 Thread Cyrus Lien

Touchpad multitouch works on 4.15-rc8 kernel but need blacklist hid-
generic.

$xinput list

⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPadid=14   [slave  pointer  (2)]
⎜   ↳ Logitech USB Receiver id=12   [slave  pointer  (2)]
⎜   ↳ Asus TouchPad id=18   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Video Bus id=7[slave  keyboard (3)]
↳ Video Bus id=8[slave  keyboard (3)]
↳ Power Button  id=9[slave  keyboard (3)]
↳ Sleep Button  id=10   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=13   [slave  keyboard (3)]
↳ Logitech USB Receiver id=11   [slave  keyboard (3)]
↳ ASUS T300CHI DOCKING  id=15   [slave  keyboard (3)]
↳ ASUS T300CHI DOCKING  id=16   [slave  keyboard (3)]
↳ ASUS T300CHI DOCKING  id=17   [slave  keyboard (3)]


$xinput list-props 18:

Device 'Asus TouchPad':
Device Enabled (143):   1
Coordinate Transformation Matrix (145): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (274): 1
Device Accel Constant Deceleration (275):   2.50
Device Accel Adaptive Deceleration (276):   1.00
Device Accel Velocity Scaling (277):12.50
Synaptics Edges (298):  105, 2535, 71, 1249
Synaptics Finger (299): 25, 30, 0
Synaptics Tap Time (300):   180
Synaptics Tap Move (301):   129
Synaptics Tap Durations (302):  180, 100, 100
Synaptics ClickPad (303):   1
Synaptics Middle Button Timeout (304):  0
Synaptics Two-Finger Pressure (305):282
Synaptics Two-Finger Width (306):   7
Synaptics Scrolling Distance (307): 59, 59
Synaptics Edge Scrolling (308): 0, 0, 0
Synaptics Two-Finger Scrolling (309):   1, 1
Synaptics Move Speed (310): 1.00, 1.75, 0.067774, 0.00
Synaptics Off (311):0
Synaptics Locked Drags (312):   0
Synaptics Locked Drags Timeout (313):   5000
Synaptics Tap Action (314): 2, 3, 0, 0, 3, 1, 0
Synaptics Click Action (315):   1, 3, 0
Synaptics Circular Scrolling (316): 0
Synaptics Circular Scrolling Distance (317):0.10
Synaptics Circular Scrolling Trigger (318): 0
Synaptics Circular Pad (319):   0
Synaptics Palm Detection (320): 0
Synaptics Palm Dimensions (321):10, 200
Synaptics Coasting Speed (322): 20.00, 50.00
Synaptics Pressure Motion (323):30, 160
Synaptics Pressure Motion Factor (324): 1.00, 1.00
Synaptics Resolution Detect (325):  1
Synaptics Grab Event Device (326):  0
Synaptics Gestures (327):   1
Synaptics Capabilities (328):   1, 0, 0, 1, 1, 0, 0
Synaptics Pad Resolution (329): 29, 31
Synaptics Area (330):   0, 0, 0, 0
Synaptics Soft Button Areas (618):  1320, 0, 1082, 0, 0, 0, 0, 0
Synaptics Noise Cancellation (331): 14, 14
Device Product ID (261):2821, 34050
Device Node (262):  "/dev/input/event14"

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

Title:
  [ELAN 3320KD-3100] Asus T300 CHI bluetooth Touchpad is recognized
  incorrectly

Status in libinput:
  Confirmed
Status in Linux:
  Unknown
Status in xinput package in Ubuntu:
  Triaged

Bug description:
  Moved the touchscreen issues to bug #1574341 "[Asus T300 CHI]
  Synaptics Touch Digitizer V04 - no multitouch".

  The Asus T300 CHI has a touchscreen and a (bluetooth) keyboard/touchpad combo.
  Both (touchscreen, touchpad) only work like a mouse (moving pointer, left and 
right click), scrolling, zooming, etc. is not working.
  the keyboard works fine.

  relevant  content of  /proc/bus/input/devices:

  [...]
  I: Bus=0003 Vendor=06cb Product=11f0 Version=0111
  N: Name="SYNAPTICS Synaptics Touch Digitizer V04"
  P: Phys=usb-:00:14.0-7/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/0003:06CB:11F0.0004/input/input9
  U: Uniq=
  H: Handlers=mouse1 event9
  B: PROP=2
  B: EV=b
  B: KEY=400 0 0 0 0 0
  B: ABS=2608003

  I: Bus=0003 Vendor=06cb Product=11f0 Version=0111
  N:

[Desktop-packages] [Bug 1480673] Re: [ELAN 3320KD-3100] Asus T300 CHI bluetooth Touchpad is recognized incorrectly

2018-02-02 Thread Cyrus Lien

Below commits should be related.

commit 73c75d395857960ea135913da7bb9537248a11e6
Author: Hans de Goede 
Date:   Fri Aug 4 15:31:04 2017 +0200

HID: asus: Add T100CHI bluetooth keyboard dock touchpad support

Put the touchpad in native (absolute coordinate mode) and export it to
userspace as a touchpad rather then as a mouse.

Note this requires HID_QUIRK_MULTI_INPUT as the T100CHI keyboard dock
has all functionality on a single HID interface and userspace expects
touchpads to be on a separate input_dev. Without MULTI_INPUT userspace
will ignore the keyboard part of the keyboard/touchpad combo.

Signed-off-by: Hans de Goede 
Signed-off-by: Jiri Kosina 

commit 5703e52cc711bc01e72cf12b86a126909c79d213
Author: Hans de Goede 
Date:   Sun Jul 2 16:34:15 2017 +0200

HID: asus: Add T100CHI bluetooth keyboard dock special keys mapping

The Asus Transformer T100CHI comes with a Bluetooth keyboard dock which
uses the same 0xff31 Asus vendor HUT page as other Asus keyboards.

This commit adds its device-id to hid-asus and fixes an issue in the
descriptor of the 0xff31 Usage, which together fixes the special keys
on this keyboard not working.

Signed-off-by: Hans de Goede 
Signed-off-by: Jiri Kosina 

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

Title:
  [ELAN 3320KD-3100] Asus T300 CHI bluetooth Touchpad is recognized
  incorrectly

Status in libinput:
  Confirmed
Status in Linux:
  Unknown
Status in xinput package in Ubuntu:
  Triaged

Bug description:
  Moved the touchscreen issues to bug #1574341 "[Asus T300 CHI]
  Synaptics Touch Digitizer V04 - no multitouch".

  The Asus T300 CHI has a touchscreen and a (bluetooth) keyboard/touchpad combo.
  Both (touchscreen, touchpad) only work like a mouse (moving pointer, left and 
right click), scrolling, zooming, etc. is not working.
  the keyboard works fine.

  relevant  content of  /proc/bus/input/devices:

  [...]
  I: Bus=0003 Vendor=06cb Product=11f0 Version=0111
  N: Name="SYNAPTICS Synaptics Touch Digitizer V04"
  P: Phys=usb-:00:14.0-7/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/0003:06CB:11F0.0004/input/input9
  U: Uniq=
  H: Handlers=mouse1 event9
  B: PROP=2
  B: EV=b
  B: KEY=400 0 0 0 0 0
  B: ABS=2608003

  I: Bus=0003 Vendor=06cb Product=11f0 Version=0111
  N: Name="SYNAPTICS Synaptics Touch Digitizer V04 Pen"
  P: Phys=usb-:00:14.0-7/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/0003:06CB:11F0.0004/input/input10
  U: Uniq=
  H: Handlers=mouse2 event10
  B: PROP=0
  B: EV=1b
  B: KEY=c03 1 0 0 0 0
  B: ABS=103
  B: MSC=10

  [...]

  I: Bus=0005 Vendor=0b05 Product=8502 Version=0001
  N: Name="ASUS T300CHI DOCKING"
  P: Phys=34:02:86:7b:3b:9d
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/bluetooth/hci0/hci0:256/0005:0B05:8502.0006/input/input18
  U: Uniq=1c:b7:2c:15:94:8b
  H: Handlers=sysrq kbd mouse3 event17
  B: PROP=0
  B: EV=12001f
  B: KEY=20 0 0 2000 40 3 10207 ff9f387ad9405fff 
febeffdfffef fffe
  B: REL=303
  B: ABS=700
  B: MSC=10
  B: LED=1f

  output of  xinput --list:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ B16_b_02 USB-PS/2 Optical Mouse id=9[slave  pointer 
 (2)]
  ⎜   ↳ HID 0566:3108   id=11   [slave  pointer 
 (2)]
  ⎜   ↳ SYNAPTICS Synaptics Touch Digitizer V04 Pen id=14   [slave  pointer 
 (2)]
  ⎜   ↳ SYNAPTICS Synaptics Touch Digitizer V04 id=15   [slave  pointer 
 (2)]
  ⎜   ↳ ASUS T300CHI DOCKINGid=18   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ HID 0566:3108   id=10   [slave  
keyboard (3)]
  ↳ C-Media Electronics Inc. USB Multimedia Audio Deviceid=12   [slave  
keyboard (3)]
  ↳ USB2.0 HD UVC WebCamid=13   [slave  
keyboard (3)]
  ↳ Asus WMI hotkeysid=16   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=17   [slave  
keyboard (3)]

  output of synclient is:
  Couldn't find synaptics properties. No synaptics driver loaded?

  but I'm unsure if the synaptics driver is the right place to look
  since basic functionality is work

[Desktop-packages] [Bug 1747045] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'aut

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

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: tentative de remplacement de «
  /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'autres instances
  du paquet libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  $ sudo apt-get install --install-recommends winehq-stable

  [...]

  Dépaquetage de libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
  dpkg: erreur de traitement de l'archive 
/tmp/apt-dpkg-install-WzFDHS/133-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack) :
   tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est 
différent d'autres instances du paquet libsane1:i386
  dpkg-deb: erreur: le sous-processus coller a été tué par le signal (Relais 
brisé (pipe))

  [...]

  Des erreurs ont été rencontrées pendant l'exécution :
   
/tmp/apt-dpkg-install-WzFDHS/133-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Feb  2 18:04:35 2018
  ErrorMessage: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », 
qui est différent d'autres instances du paquet libsane1:i386
  InstallationDate: Installed on 2018-02-01 (0 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: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb 
», qui est différent d'autres instances du paquet 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/1747045/+subscriptions

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

[Desktop-packages] [Bug 1649566] Re: [GeForce 7025 / nForce 630a] System freeze

Dieter Maurer:
>"It may take a bit of time before I can make the tests with the current Ubuntu 
>version."

If the problem is reproducible in a live environment, then testing that
would be fine.

>"And, I fear that such tests might not be reliable: after the temporary
use of the NVidia driver I could use the "nouveau" driver for some time
even without the special boot parameter "nouveau.config=NvMSI=0" - only
after some months, new freezes occurred."

Such test is reliable, in that it provides additional data points with
later versions of various related packages. This is required in order to
upstream an issue for upstream developers to address.

Despite this, if one notices different environment behavior with nouveau
after such maneuvering, the proprietary driver may be twiddling some
bits that luckily improve stability after removal. It could also be a
coincedence.

>"I have the feeling that the problem (now) arises non-deterministically
-- likely dependent on environment factors such as temperature and/or
humidity."

Evidence and data are helpful, guesses/feelings/hunches aren't. One may
monitor internal temperatures via
https://help.ubuntu.com/community/SensorInstallHowto in order to prove a
correlation.

>"While freezes are now rather rare for me, I often observe that the top
bars of my windows (usually black) are drawn in an irregular black/white
pattern (similar to the freeze pattern) when I move the mouse pointer
over the bar."

This report is scoped to freezing/crashing. If you are having graphical
issues without freezing/crashing that's a different problem for a new
report. Feel free to file a new one scoped to that and subscribe me to
it.

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

Title:
  [GeForce 7025 / nForce 630a] System freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04. From 14.04
  on, I was unable to graphically log in. A few seconds after the login
  (varying between 1 and 10 s), the screen changed to a pattern with
  dense white stripes on the violet/red background, and X froze (no
  reaction to mouse or keyboard). The latest messages in
  "/var/log/syslog" each time showed varying "nouveau E" problems, e.g.
  "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.:
  "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at
  0x00b010" (values and addresses varying).

  Usually, the freeze happens when e.g. "firefox" is started (which
  happens in my context automatically after a graphical login). In my
  case, the NVidia driver could not be started (I did not investigate
  why). Using boot parameter "nouveau.config=NvMSI=0" made the graphical
  login successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during
  the collection of the system information, the error happened again
  (despite the "nouveau.config" boot parameter).

  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Me

[Desktop-packages] [Bug 1736325] Re: ibus-sunpinyin depends on deprecated python-glade2

2018-02-02 Thread Jeremy Bicha

ibus-sunpinyin and system-config-kickstart have been demoted to
universe. I'm keeping this bug open since this package still needs to be
ported away from pygtk or it will be removed from the archives in a
future Ubuntu release.

** Tags removed: gtk2-demotion
** Tags added: gtk2-removal

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

Title:
  ibus-sunpinyin depends on deprecated python-glade2

Status in ibus-sunpinyin package in Ubuntu:
  New

Bug description:
  ibus-sunpinyin and system-config-kickstart are the only packages
  keeping pygtk2 in Ubuntu main.

  pygtk has been unmaintained upstream since around 2011. The way
  forward is to port ibus-sunpinyin to use GObject Introspection
  bindings. This also requires porting to GTK3.

  For more information on GObject Introspection see:
  https://wiki.gnome.org/Projects/GObjectIntrospection
  https://wiki.gnome.org/Projects/PyGObject

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

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

[Desktop-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started

2018-02-02 Thread Paul Smith

I'm not sure why it's being asserted that these two uses are mutually
incompatible, especially since I've been using them in a coordinated way
forever and can still do so (at the expense of junking systemd-resolve
and going back to using dnsmasq and a custom configuration, which is
obviously a big pain).  I've even, in the past, used MULTIPLE VPNs, even
at the same time, and it still just works.

If the resolver library (e.g., gethostbyname etc.) gets an unqualified
hostname, it uses the search path just as it always has including ndots
and all that stuff, to generate FQ hostnames.  No change there.

When the local resolver caching service (dnsmasq, systemd-resolv) gets a
FQ hostname it looks through the extensions provided by the VPN DHCP
information and if the hostname matches that extension it forwards the
lookup to the DNS server for that VPN.  If it doesn't match, it doesn't
forward the request.  If it doesn't match any of the VPN search paths,
it forwards the request to the default DNS servers.

I honestly don't understand why we're considering these uses
incompatible.  They seem to me to be exactly compatible and exactly what
you want to do, at least the vast majority of the time.

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

Title:
  DNS domain search paths not updated when VPN started

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

Bug description:
  I connect to work with openvpn through network-manager-openvpn.  I'm
  selecting automatic (DHCP) to get an IP address, and "Use this
  connection only for resources on its network" to support split
  tunneling.

  In the last few versions of Ubuntu I used, this all worked fine.  In
  Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both
  my VPN network and the internet, BUT I have to use FQDN for my VPN
  network hosts: the updates to the DNS search path provided by my VPN
  DHCP server are never being applied.

  Investigating the system I see that /etc/resolv.conf is pointing to
  /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not
  have any of the VPN's search path settings in it:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual 
nameservers.
nameserver 127.0.0.53

search home

  In previous versions of Ubuntu, where NetworkManager controlled the
  resolver not systemd, /etc/resolv.conf pointed to
  /run/NetworkManager/resolv.conf and there was a local dnsmasq instance
  that managed all the complexity.  In Ubuntu 17.10 when I look in
  /run/NetworkManager/resolv.conf file, I see that the search paths ARE
  properly updated there:

$ cat /run/NetworkManager/resolv.conf 
# Generated by NetworkManager
search internal.mycorp.com other.mycorp.com home
nameserver 127.0.1.1

  However this file isn't being used, and also there's no dnsmasq
  running on the system so if I switch my /etc/resolv.conf to point to
  this file instead, then all lookups fail.

  Strangely, if I look at the systemd-resolv status I see that in theory
  systemd-resolve does seem to know about the proper search paths:

$ systemd-resolve --status
   ...
Link 3 (tun0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.3.0.10
  10.8.42.2
  DNS Domain: ~internal.mycorp.com
  ~other.mycorp.com

  but for whatever reason the search domains are not getting put into
  the resolv.conf file:

$ host mydesk
;; connection timed out; no servers could be reached

$ host mydesk.internal.mycorp.com
mydesk.internal.mycorp.com has address 10.8.37.74

  (BTW, the timeout in the failed attempt above takes 10s: it is SUPER
  frustrating when all your host lookups are taking that long just to
  fail).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splas

[Desktop-packages] [Bug 1649566] Re: [GeForce 7025 / nForce 630a] System freeze

Responses to your previous questions:
1) It may take a bit of time before I can make the tests with the current 
Ubuntu version. And, I fear that such tests might not be reliable: after the 
temporary use of the NVidia driver I could use the "nouveau" driver for some 
time even without the special boot parameter "nouveau.config=NvMSI=0" - only 
after some months, new freezes occurred. I have the feeling that the problem 
(now) arises non-deterministically -- likely dependent on environment factors 
such as temperature and/or humidity.
While freezes are now rather rare for me, I often observe that the top bars of 
my windows (usually black) are drawn in an irregular black/white pattern 
(similar to the freeze pattern) when I move the mouse pointer over the bar. I 
have the feeling that this is related to the freeze problem.

2) I had no crashes in Ubuntu 12.04 - without any kernel boot
parameters. But, I am not sure that under 12.04, I was already using the
"nouveau" driver. Earlier Ubuntu versions have been using another
standard driver for NVidia cards (likely "nv") and I can no longer
remember which Ubuntu version has switched to "nouveau". I myself did
not actively switch to "nouveau".

3) I could use the NVidia driver for some time under Ubuntu 16.04. But,
its use is unstable in the sense that an Ubuntu update can render it
dysfunctional (apparently, a post installation step has problems to
properly integrate the NVidia driver) and it is very nasty to fix things
up afterwards (I must use a different driver and then reinstall the
NVidia driver via "system administration"). I therefore switched back to
"nouveau".

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

Title:
  [GeForce 7025 / nForce 630a] System freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04. From 14.04
  on, I was unable to graphically log in. A few seconds after the login
  (varying between 1 and 10 s), the screen changed to a pattern with
  dense white stripes on the violet/red background, and X froze (no
  reaction to mouse or keyboard). The latest messages in
  "/var/log/syslog" each time showed varying "nouveau E" problems, e.g.
  "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.:
  "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at
  0x00b010" (values and addresses varying).

  Usually, the freeze happens when e.g. "firefox" is started (which
  happens in my context automatically after a graphical login). In my
  case, the NVidia driver could not be started (I did not investigate
  why). Using boot parameter "nouveau.config=NvMSI=0" made the graphical
  login successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during
  the collection of the system information, the error happened again
  (despite the "nouveau.config" boot parameter).

  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a

[Desktop-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

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

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

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

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

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

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

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

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

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1735998] Re: Decouple unity related settings as unity-settings

2018-02-02 Thread Jeremy Bicha

> Is there any specific reason to carry unity specific gsettings
overrides in ubuntu-settings? Unity is not a default desktop anymore nor
it is installed in the default live iso.

Yes, by centralizing the settings, it makes it easier and faster to
change overrides for multiple flavors. It also allows for easier
comparisons between flavors.

I don't think there's a problem with review of Unity merge proposals for
ubuntu-settings taking too long. Currently, the Unity team doesn't have
any direct upload rights, right? So you'll need review anyway.

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

Title:
  Decouple unity related settings as unity-settings

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  This is an attempt to resolve "* Shared GSettings keys" issue listed
  under https://wiki.ubuntu.com/Unity/NotDefaultIssues.

  Ubuntu so far is providing session related overrides for both ubuntu &
  unity sessions in a single package, i.e. ubuntu-settings. But now that
  Unity is not the default desktop it doesn't make any sense to carry
  unity related overrides in ubuntu-settings.

  For this purpose I have created a new project: unity-settings
  (https://code.launchpad.net/~khurshid-alam/unity-settings/trunk) and
  the binary would be unity-settings in universe.

  To make this happen in under 18.04 cycle, the work-flow should be:

  1) Have unity-settings in the universe
  2) Have ubuntu-unity-desktop in the universe
  3) Let ubuntu-unity-desktop depends on unity-settings
  4) Drop unity related settings in ubuntu-settings (merge request in-progress)

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

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

[Desktop-packages] [Bug 1735998] Re: Decouple unity related settings as unity-settings

2018-02-02 Thread ventrical

@khurshid

4) The idea is to have a separate ubuntu-unity-amd64.iso. But in the
default iso, both autologin and user-session names set to "ubuntu". If
we want to change that to "unity", we could do that by shipping a
override in "/usr/share/lightdm/lightdm.conf.d/51-autologin.conf".
unity-settings seems proper place to do that. Other option is to carry
similar settings in lightdm.

Khurshid,

I like this idea and I appreciate all the help jbicha is giving you but
with our current manpower resources we may have to settle for a
flattened and leaner unity7. I don't expect you to do all of this work
by yourself. It has been my contention that we try an use any and all of
the gnome components that we can, however, I trust your direction on
this. I will try and recruit more help.

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

Title:
  Decouple unity related settings as unity-settings

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  This is an attempt to resolve "* Shared GSettings keys" issue listed
  under https://wiki.ubuntu.com/Unity/NotDefaultIssues.

  Ubuntu so far is providing session related overrides for both ubuntu &
  unity sessions in a single package, i.e. ubuntu-settings. But now that
  Unity is not the default desktop it doesn't make any sense to carry
  unity related overrides in ubuntu-settings.

  For this purpose I have created a new project: unity-settings
  (https://code.launchpad.net/~khurshid-alam/unity-settings/trunk) and
  the binary would be unity-settings in universe.

  To make this happen in under 18.04 cycle, the work-flow should be:

  1) Have unity-settings in the universe
  2) Have ubuntu-unity-desktop in the universe
  3) Let ubuntu-unity-desktop depends on unity-settings
  4) Drop unity related settings in ubuntu-settings (merge request in-progress)

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

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

[Desktop-packages] [Bug 1727765] Re: Please upgrade to 5.8

2018-02-02 Thread Hans Joachim Desserud

** Summary changed:

- Please upgrade to 5.4  (Using Ubuntu 17.10)
+ Please upgrade to 5.8

** Description changed:

- Please upgrade to 5.4
+ Please upgrade to 5.8.
  
  (Using Ubuntu 17.10)

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

Title:
  Please upgrade to 5.8

Status in mono package in Ubuntu:
  Confirmed

Bug description:
  Please upgrade to 5.8.

  (Using Ubuntu 17.10)

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

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

[Desktop-packages] [Bug 1746920] Re: Upgrade to 5.8

2018-02-02 Thread Hans Joachim Desserud

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

** This bug has been marked a duplicate of bug 1727765
   Please upgrade to 5.4  (Using Ubuntu 17.10)

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

Title:
  Upgrade to 5.8

Status in mono package in Ubuntu:
  New

Bug description:
  Upgrade Mono to 5.8
  In the old LTS too.
  4.6 is way to old.

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

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

[Desktop-packages] [Bug 1316970] Re: g_dbus memory leak in lrmd

2018-02-02 Thread Dan Streetman

Hi Seyeong,

first, I commend you for going to the trouble of fixing tests in
lp1316970_trusty_glib2.0.debdiff, but I think those are unrelated to
this actual bug and so the patch is not required for this.  I'll focus
only on the first patch.

In that patch, I did a quick review of the changes, and I'm not entirely
sure they are correct?  LP bug comments are not a great format for
reviewing patches, so please excuse formatting/line-wrapping:


> --- a/lib/services/upstart.c
> +++ b/lib/services/upstart.c
> @@ -70,6 +70,7 @@
>  if (error) {
>  crm_err("Can't connect obtain proxy to %s interface: %s", interface, 
> error->message);
>  g_error_free(error);
> +g_object_unref(proxy);

this doesn't seem right - if error is non-NULL, then proxy should be NULL, 
according to the docs:
https://developer.gnome.org/gio/stable/GDBusProxy.html#g-dbus-proxy-new-for-bus-sync

>  proxy = NULL;
>  }
>  return proxy;
> @@ -107,7 +108,9 @@
>  /*
>com.ubuntu.Upstart0_6.GetJobByName (in String name, out ObjectPath job)
>  */
> -GVariant *_ret = g_dbus_proxy_call_sync(proxy, "GetJobByName", 
> g_variant_new("(s)", arg_name),
> +GVariant *_ret = NULL;
> +
> +_ret = g_dbus_proxy_call_sync(proxy, "GetJobByName", 
> g_variant_new("(s)", arg_name),
>  G_DBUS_CALL_FLAGS_NONE, -1, 
> cancellable, error);

unless i'm missing something, there is no need for this change?

>  
>  if (_ret) {
> @@ -200,6 +203,7 @@
>  
>  g_variant_iter_free(iter);
>  g_variant_unref(_ret);
> +free(path);

this does not seem correct - per the docs, 'path' will be freed by each call in 
the while loop to g_variant_iter_loop(), and only needs to be manually freed 
after the while loop if the code breaks out of the loop manually.  That doesn't 
appear to be the case, so path should not need freeing here.
https://developer.gnome.org/glib/stable/glib-GVariant.html#g-variant-iter-loop

>  return units;
>  }
>  
> @@ -224,7 +228,7 @@
>  } else if (pass) {
>  crm_trace("Got %s", path);
>  }
> -/* free(path) */
> +free(path);

technically this should be freed only if !error - the freeing should go
into the else if (pass) block above, although free(NULL) will just do
nothing

however, i believe this should use g_free() instead of free()

>  return pass;
>  }
>  
> @@ -272,6 +276,8 @@
>  
>  g_object_unref(proxy);
>  g_variant_unref(_ret);
> +g_variant_unref(value);
> +g_variant_unref(asv);

asv is returned from g_variant_get_child_value, which does state in its docs 
that the returned value should be unref'ed, so this looks correct for 'asv'.
https://developer.gnome.org/glib/stable/glib-GVariant.html#g-variant-get-child-value

However value is returned from g_variant_lookup_value, which returns a value 
from a key-value pair in asv (as best i can tell from the docs for the 
function), and it does not indicate that the value is newly allocated or that 
it should be freed.  So it does not appear that 'value' should be unref'ed here.
https://developer.gnome.org/glib/stable/glib-GVariant.html#g-variant-lookup-value

>  return output;
>  }
>  
> @@ -299,11 +305,14 @@
>  GVariant *tmp2 = g_variant_get_child_value(tmp1, 0);
>  
>  instance = g_variant_dup_string(tmp2, NULL);
> +g_variant_unref(tmp2);
>  }
> +g_variant_unref(tmp1);

these look correct

>  }
>  
>  crm_info("Result: %s", instance);
>  g_variant_unref(_ret);
> +g_object_unref(proxy);

this looks correct

>  return instance;
>  }
>  
> @@ -338,6 +347,7 @@
>  }
>  
>  crm_info("%s is%s running", name, pass ? "" : " not");
> +free(job);

technically this is only needed in the else {} block, but as it should
still be NULL the free will do nothing

again this should be g_free() instead of free() i think

>  return pass;
>  }
>  
> @@ -400,6 +410,7 @@
>  crm_info("Call to %s passed: type '%s' %s", op->action, 
> g_variant_get_type_string(_ret),
>   path);
>  op->rc = PCMK_EXECRA_OK;
> +free(path);

looks good, but probably use g_free()

>  
>  } else {
>  crm_err("Call to %s passed but return type was '%s' not '(o)'", 
> op->action, g_variant_get_type_string(_ret));
> @@ -501,6 +512,7 @@
>  crm_info("Call to %s passed: type '%s' %s", op->action, 
> g_variant_get_type_string(_ret),
>   path);
>  op->rc = PCMK_EXECRA_OK;
> +free(path);

looks good, but probably use g_free()

>  
>  } else {
>  crm_err("Call to %s passed but return type was '%s' not '(o)'", 
> op->action, g_variant_get_type_string(_ret));

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

Title:
  g_dbus memory leak in lrmd

Status in glib2.0 package in Ubuntu:
  New
Status in pa

[Desktop-packages] [Bug 1747045] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'a

2018-02-02 Thread Véteau

Public bug reported:

$ sudo apt-get install --install-recommends winehq-stable

[...]

Dépaquetage de libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
dpkg: erreur de traitement de l'archive 
/tmp/apt-dpkg-install-WzFDHS/133-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack) :
 tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est 
différent d'autres instances du paquet libsane1:i386
dpkg-deb: erreur: le sous-processus coller a été tué par le signal (Relais 
brisé (pipe))

[...]

Des erreurs ont été rencontrées pendant l'exécution :
 
/tmp/apt-dpkg-install-WzFDHS/133-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Fri Feb  2 18:04:35 2018
ErrorMessage: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », 
qui est différent d'autres instances du paquet libsane1:i386
InstallationDate: Installed on 2018-02-01 (0 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: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb 
», qui est différent d'autres instances du paquet libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful third-party-packages

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: tentative de remplacement de «
  /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'autres instances
  du paquet libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  $ sudo apt-get install --install-recommends winehq-stable

  [...]

  Dépaquetage de libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
  dpkg: erreur de traitement de l'archive 
/tmp/apt-dpkg-install-WzFDHS/133-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack) :
   tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est 
différent d'autres instances du paquet libsane1:i386
  dpkg-deb: erreur: le sous-processus coller a été tué par le signal (Relais 
brisé (pipe))

  [...]

  Des erreurs ont été rencontrées pendant l'exécution :
   
/tmp/apt-dpkg-install-WzFDHS/133-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Feb  2 18:04:35 2018
  ErrorMessage: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », 
qui est différent d'autres instances du paquet libsane1:i386
  InstallationDate: Installed on 2018-02-01 (0 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: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb 
», qui est différent d'autres instances du paquet 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/1747045/+subscriptions

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

[Desktop-packages] [Bug 1746638] Re: [GeForce 6150SE nForce 430] PC freezes and crashes

** Summary changed:

- Nouveau graphics driver freezes and crashes
+ [GeForce 6150SE nForce 430] PC freezes and crashes

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

Title:
  [GeForce 6150SE nForce 430] PC freezes and crashes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using the nouveau graphics driver my pc freezes and crashes.

  WORKAROUND: Use the proprietary nvidia driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-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: XFCE
  Date: Thu Feb  1 01:36:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] 
[1043:8234]
  InstallationDate: Installed on 2017-11-23 (69 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus 
CX3900/DX4000/DX4050]
   Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  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
  xserver.bootTime: Thu Feb  1 01:34:53 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 1241:1166MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 879619] Re: Samsung SCX-3200 scanner isn't detected in Ubuntu 12.04 LTS

2018-02-02 Thread Vasiliy

In Lubuntu 14.04.2, kernel 4.2.0-32-generic #37~14.04.1-Ubuntu SMP
it's still problem. Yes, I have laptop with usb 3.0, and xhci_hcd driver. All 
configs is good, running from root allows scan sometimes, after 3-4 tryes with 
xsane, simple-scan don't see anything. 
Please create new thread yourself, I don't know where do it. 


Feb  2 23:21:39 acer colord: Device added: sysfs-Xerox-WorkCentre_3119_Series
Feb  2 23:22:02 acer CRON[32317]: (root) CMD (touch /media/outer/.timestamp  
>/dev/null 2>/dev/null)
Feb  2 23:22:02 acer kernel: [ 3581.748586] vgaarb: this pci device is not a 
vga device
Feb  2 23:22:03 acer kernel: [ 3582.762097] vgaarb: this pci device is not a 
vga device
^Croot@acer:~export SANE_DEBUG_XEROX_MFP=255
root@acer:~# scanimage -L  
[sanei_debug] Setting debug level of xerox_mfp to 255.
[xerox_mfp] sane_init: Xerox backend (build 13), version != null, authorize != 
null
[xerox_mfp] sane_xerox_mfp_get_devices: 0xbf9d9e5c, 0
[xerox_mfp] list_one_device: libusb:001:012
[xerox_mfp] usb_dev_open: open 0x916fef8
[xerox_mfp] :: dev_command(INQUIRY[0x12], 70)
[xerox_mfp] [70] a8 00 43 10 53 41 4d 53 55 4e 47 20 4f 52 49 4f 4e 20 20 20 20 
20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 35 3f 04 29 00 00 27 d8 00 00 36 
d8 00 01 2f 00 00 02 00 00 00 00 36 d8 00 00 36 d8 04 01 05 05 00...
[xerox_mfp] dev_inquiry: found SAMSUNG/ORION
[xerox_mfp] usb_dev_close: closing dev 0x916fef8
device `xerox_mfp:libusb:001:012' is a SAMSUNG ORION multi-function peripheral
root@acer:~# scanimage -L  
[sanei_debug] Setting debug level of xerox_mfp to 255.
[xerox_mfp] sane_init: Xerox backend (build 13), version != null, authorize != 
null
[xerox_mfp] sane_xerox_mfp_get_devices: 0xbfe0858c, 0
[xerox_mfp] list_one_device: libusb:001:012
[xerox_mfp] usb_dev_open: open 0x8817ef8
[xerox_mfp] :: dev_command(INQUIRY[0x12], 70)
[xerox_mfp] usb_dev_request: sanei_usb_read_bulk: Error during device I/O
[xerox_mfp] dev_command: dev_request: Error during device I/O
[xerox_mfp] usb_dev_close: closing dev 0x8817ef8
[xerox_mfp] list_one_device: dev_inquiry(libusb:001:012): Error during device 
I/O

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).

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

Title:
  Samsung SCX-3200 scanner isn't detected in Ubuntu 12.04 LTS

Status in sane-backends package in Ubuntu:
  Invalid
Status in Baltix:
  Confirmed

Bug description:
  After upgrading to 11.10, the scanner does not work anymore.
  I have added the configuration for SCX-3200 as shown here:
  http://3v1n0.tuxfamily.org/tumblelog/post/936/
  but nothing changed.

  Output of diagnostics:
  [21:05:47][giorgio@Desmond:~]$ sane-find-scanner
    # sane-find-scanner will now attempt to detect your scanner. If the
    # result is different from what you expected, first make sure your
    # scanner is powered up and properly connected to your computer.
    # No SCSI scanners found. If you expected something different, make sure 
that
    # you have loaded a kernel SCSI driver for your SCSI adapter.

  found USB scanner (vendor=0x04e8 [Samsung Electronics Co., Ltd.], 
product=0x3441 [SCX-3200 Series]) at libusb:001:002
    # Your USB scanner was (probably) detected. It may or may not be supported 
by
    # SANE. Try scanimage -L and read the backend's manpage.
    # Not checking for parallel port scanners.
    # Most Scanners connected to the parallel port or other proprietary ports
    # can't be detected by this program.
    # You may want to run this program as root to find all devices. Once you
    # found the scanner devices, be sure to adjust access permissions as
    # necessary.
  [21:05:52][giorgio@Desmond:~]$ scanimage -L

  No scanners were identified. If you were expecting something different,
  check that the scanner is plugged in, turned on and detected by the
  sane-find-scanner tool (if appropriate). Please read the documentation
  which came with this software (README, FAQ, manpages).

  Scaning with Samsung SCX-3400 and SCX-3405 doesn't work too, but it's
  easy to fix - just add this line into /etc/sane.d/xerox_mfp.conf file:

  usb 0x04e8 0x344f
  # Samsung SCX-3400

  See http://ubuntuforums.org/showthread.php?t=1952312 for more info

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libsane 1.0.22-2ubuntu2 [modified: lib/udev/rules.d/40-libsane.rules]
  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: Fri Oct 21 21:01:56 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash

[Desktop-packages] [Bug 1659183] Re: English (Canada) input source is missing the left backslash key

This bug was fixed in the package xkeyboard-config - 2.23.1-1ubuntu1

---
xkeyboard-config (2.23.1-1ubuntu1) bionic; urgency=medium

  * Merge with Debian (LP: #1659183, LP: #1685774, LP: #1689110,
LP: #1746544), remaining changes:
- control, rules, xkb-data-i18n.install, xkb-data.install: Split out
  xkb-data-i18n to be used by console-setup.
- xkb-data.postinst: Remove the xkb cache to make sure it gets
  regenerated.
  * Dropped patch, applied upstream:
- d/p/elfdalian-kb-layout.diff

 -- Gunnar Hjalmarsson   Fri, 02 Feb 2018 12:47:00
+0100

** Changed in: xkeyboard-config (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  English (Canada) input source is missing the left backslash key

Status in xkeyboard-config:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released

Bug description:
  In Canada, many keyboards are bilingual and have a slightly different
  layout from US keyboards. They have an additional backslash key next
  to the left shift key.

  In Text Entry, when I select English (Canada) as the input source, the
  layout is wrong. Instead of a backslash, the layout shows a less-than
  symbol, and that is what input when I press the key.

  Attached a screenshot of the incorrect layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ibus 1.5.14-2ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  Uname: Linux 4.9.0-12-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 24 22:49:41 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-01-22 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170115)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1659183/+subscriptions

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

[Desktop-packages] [Bug 1689316] Re: Desktop freeze

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  Desktop freeze

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  The desktop hangs/locks up/freezes randomly during use, the keyboard
  and cursor stop responding as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  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:Unity7
  Date: Mon May  8 19:59:24 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2017-04-14 (24 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Inspiron 3542
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=3fd29d97-25ad-421f-aed1-5261567fd0c1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0KHNVP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd05/27/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0KHNVP:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1

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

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

[Desktop-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  DNS domain search paths not updated when VPN started

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

Bug description:
  I connect to work with openvpn through network-manager-openvpn.  I'm
  selecting automatic (DHCP) to get an IP address, and "Use this
  connection only for resources on its network" to support split
  tunneling.

  In the last few versions of Ubuntu I used, this all worked fine.  In
  Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both
  my VPN network and the internet, BUT I have to use FQDN for my VPN
  network hosts: the updates to the DNS search path provided by my VPN
  DHCP server are never being applied.

  Investigating the system I see that /etc/resolv.conf is pointing to
  /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not
  have any of the VPN's search path settings in it:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual 
nameservers.
nameserver 127.0.0.53

search home

  In previous versions of Ubuntu, where NetworkManager controlled the
  resolver not systemd, /etc/resolv.conf pointed to
  /run/NetworkManager/resolv.conf and there was a local dnsmasq instance
  that managed all the complexity.  In Ubuntu 17.10 when I look in
  /run/NetworkManager/resolv.conf file, I see that the search paths ARE
  properly updated there:

$ cat /run/NetworkManager/resolv.conf 
# Generated by NetworkManager
search internal.mycorp.com other.mycorp.com home
nameserver 127.0.1.1

  However this file isn't being used, and also there's no dnsmasq
  running on the system so if I switch my /etc/resolv.conf to point to
  this file instead, then all lookups fail.

  Strangely, if I look at the systemd-resolv status I see that in theory
  systemd-resolve does seem to know about the proper search paths:

$ systemd-resolve --status
   ...
Link 3 (tun0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.3.0.10
  10.8.42.2
  DNS Domain: ~internal.mycorp.com
  ~other.mycorp.com

  but for whatever reason the search domains are not getting put into
  the resolv.conf file:

$ host mydesk
;; connection timed out; no servers could be reached

$ host mydesk.internal.mycorp.com
mydesk.internal.mycorp.com has address 10.8.37.74

  (BTW, the timeout in the failed attempt above takes 10s: it is SUPER
  frustrating when all your host lookups are taking that long just to
  fail).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  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.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System P

[Desktop-packages] [Bug 1734762] Re: Evolution crashes often

2018-02-02 Thread Stephan Saalfeld

** Also affects: evolution-indicator
   Importance: Undecided
   Status: New

** No longer affects: evolution-indicator

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

Title:
  Evolution crashes often

Status in evolution-indicator package in Ubuntu:
  Confirmed

Bug description:
  Started crashing when I upgraded to Ubuntu 17.10. See
  https://bugzilla.gnome.org/show_bug.cgi?id=790806 for more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evolution-indicator 0.2.20-0ubuntu31
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 27 15:18:08 2017
  ProcEnviron:
   LANG=en_US.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  SourcePackage: evolution-indicator
  UpgradeStatus: Upgraded to artful on 2017-11-07 (20 days ago)

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

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

[Desktop-packages] [Bug 1734762] Re: Evolution crashes often

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

** Changed in: evolution-indicator (Ubuntu)
   Status: New => Confirmed

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

Title:
  Evolution crashes often

Status in evolution-indicator package in Ubuntu:
  Confirmed

Bug description:
  Started crashing when I upgraded to Ubuntu 17.10. See
  https://bugzilla.gnome.org/show_bug.cgi?id=790806 for more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evolution-indicator 0.2.20-0ubuntu31
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 27 15:18:08 2017
  ProcEnviron:
   LANG=en_US.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  SourcePackage: evolution-indicator
  UpgradeStatus: Upgraded to artful on 2017-11-07 (20 days ago)

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

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

[Desktop-packages] [Bug 1685774] Re: Turkish keyboard issues

This bug was fixed in the package xkeyboard-config - 2.23.1-1ubuntu1

---
xkeyboard-config (2.23.1-1ubuntu1) bionic; urgency=medium

  * Merge with Debian (LP: #1659183, LP: #1685774, LP: #1689110,
LP: #1746544), remaining changes:
- control, rules, xkb-data-i18n.install, xkb-data.install: Split out
  xkb-data-i18n to be used by console-setup.
- xkb-data.postinst: Remove the xkb cache to make sure it gets
  regenerated.
  * Dropped patch, applied upstream:
- d/p/elfdalian-kb-layout.diff

 -- Gunnar Hjalmarsson   Fri, 02 Feb 2018 12:47:00
+0100

** Changed in: xkeyboard-config (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Turkish keyboard issues

Status in xkeyboard-config:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released

Bug description:
  There are still some problems with Turkish keyboard in 17.04:

  * The currency is updated as ₺ at 17.04 but there is no way to type it by 
keyboard. By the standard, it should be Alt Gr + T key to type ₺:
  
https://thumb1.shutterstock.com/display_pic_with_logo/3175712/591962180/stock-photo-word-no-meaning-hayir-in-turkish-written-on-a-keyboard-in-a-row-with-red-keys-591962180.jpg

  

  Some keys' behaviors are different from Windows, so for those, it can
  be considered as any update or not, but for any case, I am also
  reporting:

  http://wiki.laptop.org/images/thumb/6/64/TR-MP-Qv1.png/800px-TR-MP-
  Qv1.png

  * For the letter ã, Alt Gr + Ü key should be pressed then a key should be 
pressed.
  * For the letter õ, Alt Gr + Ü key should be pressed then o key should be 
pressed.
  * For the character ~, Alt Gr + Ü should be pressed then space key should be 
pressed.
  * For the letter æ, Alt Gr + A should be pressed 
  * For the letter â, Shift + 3 then a should be pressed.
  * For the letter û, Shift + 3 then u should be pressed.
  * For the letter ô, Shift + 3 then o should be pressed.
  * For the letter î, Shift + 3 then ı or i should be pressed.
  * For the letter ê, Shift + 3 then e should be pressed.
  * For the character ^, Shift + 3 then space should be presssed.
  * For the letter é, Alt Gr + ş then e should be pressed.
  * For the letter á, Alt Gr + ş then a should be pressed.
  * For the letter ú, Alt Gr + ş then u should be pressed.
  * For the letter ó, Alt Gr + ş then o should be pressed.
  * For the letter í, Alt Gr + ş then ı or i should be pressed.
  * For the character ´, Alt Gr + ş then space should be pressed.
  * For the letter ò, Alt Gr + , then o should be pressed.
  * For the letter ù, Alt Gr + , then u should be pressed.
  * For the letter à, Alt Gr + , then a should be pressed.
  * For the character `, Alt Gr + , then space should be pressed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1685774/+subscriptions

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

[Desktop-packages] [Bug 1689110] Re: There are two keyboards for the Hausa language with the same name

This bug was fixed in the package xkeyboard-config - 2.23.1-1ubuntu1

---
xkeyboard-config (2.23.1-1ubuntu1) bionic; urgency=medium

  * Merge with Debian (LP: #1659183, LP: #1685774, LP: #1689110,
LP: #1746544), remaining changes:
- control, rules, xkb-data-i18n.install, xkb-data.install: Split out
  xkb-data-i18n to be used by console-setup.
- xkb-data.postinst: Remove the xkb cache to make sure it gets
  regenerated.
  * Dropped patch, applied upstream:
- d/p/elfdalian-kb-layout.diff

 -- Gunnar Hjalmarsson   Fri, 02 Feb 2018 12:47:00
+0100

** Changed in: xkeyboard-config (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  There are two keyboards for the Hausa language with the same name

Status in xkeyboard-config:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released

Bug description:
  The keyboard selection window has two entries for the Hausa language.

  To reproduce:
  * Click "Text Entry Settings".
  * Click the +
  * Scroll down to H

  There are two entries with the identical name "Hausa". They should
  have different names so that it would be clear what is the difference
  between them.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity-control-center 15.04.0+17.04.20170402.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sun May  7 20:01:29 2017
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-02-26 (801 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1689110/+subscriptions

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

[Desktop-packages] [Bug 1746544] Re: Please merge xkeyboard-config 2.23.1-1 (main) from Debian unstable (main)

This bug was fixed in the package xkeyboard-config - 2.23.1-1ubuntu1

---
xkeyboard-config (2.23.1-1ubuntu1) bionic; urgency=medium

  * Merge with Debian (LP: #1659183, LP: #1685774, LP: #1689110,
LP: #1746544), remaining changes:
- control, rules, xkb-data-i18n.install, xkb-data.install: Split out
  xkb-data-i18n to be used by console-setup.
- xkb-data.postinst: Remove the xkb cache to make sure it gets
  regenerated.
  * Dropped patch, applied upstream:
- d/p/elfdalian-kb-layout.diff

 -- Gunnar Hjalmarsson   Fri, 02 Feb 2018 12:47:00
+0100

** Changed in: xkeyboard-config (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Please merge xkeyboard-config 2.23.1-1 (main) from Debian unstable
  (main)

Status in xkeyboard-config package in Ubuntu:
  Fix Released

Bug description:
  Version 2.23 of xkeyboard-config has been released upstream:

  https://cgit.freedesktop.org/xkeyboard-config/commit/?id=963db158

  It's highly desirable that this makes it in Ubuntu 18.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1746544/+subscriptions

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

[Desktop-packages] [Bug 561294] Re: Not a helpful or appropiate error message displayed

2018-02-02 Thread strangedata

I'm running Ubuntu 17.10 with XOrg (Wayland was impossibly laggy).

Every few seconds the window manager will stop updating. Just the mouse
keeps on moving, but videos playing will continue.

If I wait a half a minute, it will resume. If I switch to ctrl+alt+f1
and log again, it resumes too.

In the log I see:

Feb  2 14:08:17 fc993847 org.gnome.Shell.desktop[17388]: Window manager 
warning: last_user_time (332294169) is greater than comparison timestamp 
(332288825).  This most likely represents a buggy client sending inaccurate 
timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Feb  2 14:08:17 fc993847 org.gnome.Shell.desktop[17388]: Window manager 
warning: 0x445 ((39) Why A) appears to be one of the offending windows with 
a timestamp of 332294169.  Working around...
Feb  2 14:09:06 fc993847 org.gnome.Shell.desktop[17388]: Window manager 
warning: last_user_time (332347345) is greater than comparison timestamp 
(332338937).  This most likely represents a buggy client sending inaccurate 
timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Feb  2 14:09:06 fc993847 org.gnome.Shell.desktop[17388]: Window manager 
warning: 0x445 ((39) Why A) appears to be one of the offending windows with 
a timestamp of 332347345.  Working around...


The name of the offending window varies with whatever I'm focused at the time, 
doesn't matter what it is.

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

Title:
  Not a helpful or appropiate error message displayed

Status in metacity package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: metacity

  
  running compiz --replace as trying to debug an issue with lucid Beta 2 and I 
get the following output -

  Window manager warning: last_user_time (1271002643) is greater than 
comparison timestamp (799652). This most likely represents a buggy client 
sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to 
work around...
  Window manager warning: 0x4600028 (Social bro) appears to be one of the 
offending windows with a timestamp of 1271002643. Working around...
  Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x4600028 
(Social bro); these messages lack timestamps and therefore suck.

  while the error output is helpful surely a user seeing "these messages
  lack timestamps and therefore suck." is not at all helpful and should
  have a more appropriate error message displayed

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

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

[Desktop-packages] [Bug 1747034] [NEW] application startup blocks on plugin timeout

2018-02-02 Thread Jean-Baptiste Lallement

Public bug reported:

On my test machine fwupd service timeouts (due to bug 1746485) This
causes gnome-software to wait until the timeout during startup and has
an impact of 20s on startup.

16:06:43:0338 Gs  plugin no longer recently active: packagekit-history
16:07:03:0673 Gs  not GsPlugin error from plugin fwupd g-io-error-quark:24: 
Error calling StartServiceByName for org.freedesktop.fwupd: Timeout was reached
16:07:03:0673 Gs  failed to call gs_plugin_refresh on fwupd: Error calling 
StartServiceByName for org.freedesktop.fwupd: Timeout was reached
16:07:03:0674 As  run 
0x55835f044d90~GsPlugin::packagekit-refresh(gs_plugin_refresh)
16:07:03:0683 Gs  emitting global waiting

If the service is removed it starts faster bug then an error message is
displayed on the UI ('Something went wrong')

16:08:19:0509 As  run 0x561b59f85590~GsPlugin::fwupd(gs_plugin_refresh)
16:08:19:0514 Gs  not GsPlugin error from plugin fwupd FwupdError:10: The name 
org.freedesktop.fwupd was not provided by any .service files
16:08:19:0514 Gs  failed to call gs_plugin_refresh on fwupd: The name 
org.freedesktop.fwupd was not provided by any .service files
16:08:19:0514 As  run 
0x561b59f85590~GsPlugin::packagekit-refresh(gs_plugin_refresh)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.26.5-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.8-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb  2 17:09:38 2018
InstallationDate: Installed on 2013-09-03 (1612 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
InstalledPlugins:
 gnome-software-plugin-flatpak 3.26.5-1ubuntu1
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.26.5-1ubuntu1
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: Upgraded to bionic on 2018-01-26 (7 days ago)

** Affects: gnome-software (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-software in Ubuntu.
https://bugs.launchpad.net/bugs/1747034

Title:
  application startup blocks on plugin timeout

Status in gnome-software package in Ubuntu:
  New

Bug description:
  On my test machine fwupd service timeouts (due to bug 1746485) This
  causes gnome-software to wait until the timeout during startup and has
  an impact of 20s on startup.

  16:06:43:0338 Gs  plugin no longer recently active: packagekit-history
  16:07:03:0673 Gs  not GsPlugin error from plugin fwupd g-io-error-quark:24: 
Error calling StartServiceByName for org.freedesktop.fwupd: Timeout was reached
  16:07:03:0673 Gs  failed to call gs_plugin_refresh on fwupd: Error calling 
StartServiceByName for org.freedesktop.fwupd: Timeout was reached
  16:07:03:0674 As  run 
0x55835f044d90~GsPlugin::packagekit-refresh(gs_plugin_refresh)
  16:07:03:0683 Gs  emitting global waiting

  If the service is removed it starts faster bug then an error message
  is displayed on the UI ('Something went wrong')

  16:08:19:0509 As  run 0x561b59f85590~GsPlugin::fwupd(gs_plugin_refresh)
  16:08:19:0514 Gs  not GsPlugin error from plugin fwupd FwupdError:10: The 
name org.freedesktop.fwupd was not provided by any .service files
  16:08:19:0514 Gs  failed to call gs_plugin_refresh on fwupd: The name 
org.freedesktop.fwupd was not provided by any .service files
  16:08:19:0514 As  run 
0x561b59f85590~GsPlugin::packagekit-refresh(gs_plugin_refresh)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.26.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  2 17:09:38 2018
  InstallationDate: Installed on 2013-09-03 (1612 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.26.5-1ubuntu1
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.5-1ubuntu1
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (7 days ago)

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

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

[Desktop-packages] [Bug 879619] Re: Samsung SCX-3200 scanner isn't detected in Ubuntu 12.04 LTS

Vasiliy (count0-3), it will help immensely if you use the computer the problem 
is reproducible with, and provide necessary debugging logs by filing a new 
report with Ubuntu via a terminal:
ubuntu-bug sane-backends

or via https://bugs.launchpad.net/ubuntu/+source/sane-backends/+filebug
as an alternative.

Please feel free to subscribe me to it.

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

Title:
  Samsung SCX-3200 scanner isn't detected in Ubuntu 12.04 LTS

Status in sane-backends package in Ubuntu:
  Invalid
Status in Baltix:
  Confirmed

Bug description:
  After upgrading to 11.10, the scanner does not work anymore.
  I have added the configuration for SCX-3200 as shown here:
  http://3v1n0.tuxfamily.org/tumblelog/post/936/
  but nothing changed.

  Output of diagnostics:
  [21:05:47][giorgio@Desmond:~]$ sane-find-scanner
    # sane-find-scanner will now attempt to detect your scanner. If the
    # result is different from what you expected, first make sure your
    # scanner is powered up and properly connected to your computer.
    # No SCSI scanners found. If you expected something different, make sure 
that
    # you have loaded a kernel SCSI driver for your SCSI adapter.

  found USB scanner (vendor=0x04e8 [Samsung Electronics Co., Ltd.], 
product=0x3441 [SCX-3200 Series]) at libusb:001:002
    # Your USB scanner was (probably) detected. It may or may not be supported 
by
    # SANE. Try scanimage -L and read the backend's manpage.
    # Not checking for parallel port scanners.
    # Most Scanners connected to the parallel port or other proprietary ports
    # can't be detected by this program.
    # You may want to run this program as root to find all devices. Once you
    # found the scanner devices, be sure to adjust access permissions as
    # necessary.
  [21:05:52][giorgio@Desmond:~]$ scanimage -L

  No scanners were identified. If you were expecting something different,
  check that the scanner is plugged in, turned on and detected by the
  sane-find-scanner tool (if appropriate). Please read the documentation
  which came with this software (README, FAQ, manpages).

  Scaning with Samsung SCX-3400 and SCX-3405 doesn't work too, but it's
  easy to fix - just add this line into /etc/sane.d/xerox_mfp.conf file:

  usb 0x04e8 0x344f
  # Samsung SCX-3400

  See http://ubuntuforums.org/showthread.php?t=1952312 for more info

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libsane 1.0.22-2ubuntu2 [modified: lib/udev/rules.d/40-libsane.rules]
  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: Fri Oct 21 21:01:56 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.sane.d.dll.conf: 2011-10-21T20:17:22.966767
  mtime.conffile..etc.sane.d.xerox.mfp.conf: 2011-10-21T20:26:22.544361

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

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

[Desktop-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started

2018-02-02 Thread Jeroen Hoek

I hope something can be worked out before this lands in the next LTS-
release. This breaks one of the most common uses of a VPN (remote work).

Right now a workaround is using this script after connecting to a VPN-
server:

https://github.com/jonathanio/update-systemd-resolved

It calls systemd-resolved via DBus to add the proper settings after the
OpenVPN connection is established.

Of course this means abandoning NetworkManager for use with OpenVPN,
because there is also no way to specify --up and --down parameters.

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

Title:
  DNS domain search paths not updated when VPN started

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

Bug description:
  I connect to work with openvpn through network-manager-openvpn.  I'm
  selecting automatic (DHCP) to get an IP address, and "Use this
  connection only for resources on its network" to support split
  tunneling.

  In the last few versions of Ubuntu I used, this all worked fine.  In
  Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both
  my VPN network and the internet, BUT I have to use FQDN for my VPN
  network hosts: the updates to the DNS search path provided by my VPN
  DHCP server are never being applied.

  Investigating the system I see that /etc/resolv.conf is pointing to
  /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not
  have any of the VPN's search path settings in it:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual 
nameservers.
nameserver 127.0.0.53

search home

  In previous versions of Ubuntu, where NetworkManager controlled the
  resolver not systemd, /etc/resolv.conf pointed to
  /run/NetworkManager/resolv.conf and there was a local dnsmasq instance
  that managed all the complexity.  In Ubuntu 17.10 when I look in
  /run/NetworkManager/resolv.conf file, I see that the search paths ARE
  properly updated there:

$ cat /run/NetworkManager/resolv.conf 
# Generated by NetworkManager
search internal.mycorp.com other.mycorp.com home
nameserver 127.0.1.1

  However this file isn't being used, and also there's no dnsmasq
  running on the system so if I switch my /etc/resolv.conf to point to
  this file instead, then all lookups fail.

  Strangely, if I look at the systemd-resolv status I see that in theory
  systemd-resolve does seem to know about the proper search paths:

$ systemd-resolve --status
   ...
Link 3 (tun0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.3.0.10
  10.8.42.2
  DNS Domain: ~internal.mycorp.com
  ~other.mycorp.com

  but for whatever reason the search domains are not getting put into
  the resolv.conf file:

$ host mydesk
;; connection timed out; no servers could be reached

$ host mydesk.internal.mycorp.com
mydesk.internal.mycorp.com has address 10.8.37.74

  (BTW, the timeout in the failed attempt above takes 10s: it is SUPER
  frustrating when all your host lookups are taking that long just to
  fail).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.typ

[Desktop-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started

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

** Changed in: network-manager-openvpn (Ubuntu)
   Status: New => Confirmed

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

Title:
  DNS domain search paths not updated when VPN started

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

Bug description:
  I connect to work with openvpn through network-manager-openvpn.  I'm
  selecting automatic (DHCP) to get an IP address, and "Use this
  connection only for resources on its network" to support split
  tunneling.

  In the last few versions of Ubuntu I used, this all worked fine.  In
  Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both
  my VPN network and the internet, BUT I have to use FQDN for my VPN
  network hosts: the updates to the DNS search path provided by my VPN
  DHCP server are never being applied.

  Investigating the system I see that /etc/resolv.conf is pointing to
  /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not
  have any of the VPN's search path settings in it:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual 
nameservers.
nameserver 127.0.0.53

search home

  In previous versions of Ubuntu, where NetworkManager controlled the
  resolver not systemd, /etc/resolv.conf pointed to
  /run/NetworkManager/resolv.conf and there was a local dnsmasq instance
  that managed all the complexity.  In Ubuntu 17.10 when I look in
  /run/NetworkManager/resolv.conf file, I see that the search paths ARE
  properly updated there:

$ cat /run/NetworkManager/resolv.conf 
# Generated by NetworkManager
search internal.mycorp.com other.mycorp.com home
nameserver 127.0.1.1

  However this file isn't being used, and also there's no dnsmasq
  running on the system so if I switch my /etc/resolv.conf to point to
  this file instead, then all lookups fail.

  Strangely, if I look at the systemd-resolv status I see that in theory
  systemd-resolve does seem to know about the proper search paths:

$ systemd-resolve --status
   ...
Link 3 (tun0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.3.0.10
  10.8.42.2
  DNS Domain: ~internal.mycorp.com
  ~other.mycorp.com

  but for whatever reason the search domains are not getting put into
  the resolv.conf file:

$ host mydesk
;; connection timed out; no servers could be reached

$ host mydesk.internal.mycorp.com
mydesk.internal.mycorp.com has address 10.8.37.74

  (BTW, the timeout in the failed attempt above takes 10s: it is SUPER
  frustrating when all your host lookups are taking that long just to
  fail).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  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.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name:

[Desktop-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started

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

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

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

Title:
  DNS domain search paths not updated when VPN started

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

Bug description:
  I connect to work with openvpn through network-manager-openvpn.  I'm
  selecting automatic (DHCP) to get an IP address, and "Use this
  connection only for resources on its network" to support split
  tunneling.

  In the last few versions of Ubuntu I used, this all worked fine.  In
  Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both
  my VPN network and the internet, BUT I have to use FQDN for my VPN
  network hosts: the updates to the DNS search path provided by my VPN
  DHCP server are never being applied.

  Investigating the system I see that /etc/resolv.conf is pointing to
  /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not
  have any of the VPN's search path settings in it:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual 
nameservers.
nameserver 127.0.0.53

search home

  In previous versions of Ubuntu, where NetworkManager controlled the
  resolver not systemd, /etc/resolv.conf pointed to
  /run/NetworkManager/resolv.conf and there was a local dnsmasq instance
  that managed all the complexity.  In Ubuntu 17.10 when I look in
  /run/NetworkManager/resolv.conf file, I see that the search paths ARE
  properly updated there:

$ cat /run/NetworkManager/resolv.conf 
# Generated by NetworkManager
search internal.mycorp.com other.mycorp.com home
nameserver 127.0.1.1

  However this file isn't being used, and also there's no dnsmasq
  running on the system so if I switch my /etc/resolv.conf to point to
  this file instead, then all lookups fail.

  Strangely, if I look at the systemd-resolv status I see that in theory
  systemd-resolve does seem to know about the proper search paths:

$ systemd-resolve --status
   ...
Link 3 (tun0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.3.0.10
  10.8.42.2
  DNS Domain: ~internal.mycorp.com
  ~other.mycorp.com

  but for whatever reason the search domains are not getting put into
  the resolv.conf file:

$ host mydesk
;; connection timed out; no servers could be reached

$ host mydesk.internal.mycorp.com
mydesk.internal.mycorp.com has address 10.8.37.74

  (BTW, the timeout in the failed attempt above takes 10s: it is SUPER
  frustrating when all your host lookups are taking that long just to
  fail).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  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.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product N

[Desktop-packages] [Bug 1649566] Re: xserver-xorg-video-nouveau: X freeze

Dieter Maurer:

1) To see if this is already resolved in Ubuntu, could you please test 
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results? If 
still reproducible, please post results following:
https://wiki.ubuntu.com/DebuggingKernelBoot
https://wiki.ubuntu.com/DebuggingSystemCrash

2) To clarify, when you were using 12.04, you didn't have any crashing
whatsoever when using nouveau without any kernel parameters?

3) Does the nvidia driver still not work for you in 16.04?

** Description changed:

- Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS version
- in each case). From 14.04 on, I was unable to graphically log in. A few
- seconds after the login (varying between 1 and 10 s), the screen changed
- to a pattern with dense white stripes on the violet/red background, and
- X froze (no reaction to mouse or keyboard). The latest messages in
- "/var/log/syslog" each time showed varying "nouveau E" problems, e.g.
- "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.:
- "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at
- 0x00b010" (values and addresses varying).
+ Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04. From 14.04
+ on, I was unable to graphically log in. A few seconds after the login
+ (varying between 1 and 10 s), the screen changed to a pattern with dense
+ white stripes on the violet/red background, and X froze (no reaction to
+ mouse or keyboard). The latest messages in "/var/log/syslog" each time
+ showed varying "nouveau E" problems, e.g. "unrecognized interupt",
+ "PFIFO", or "PBUS" problems such as e.g.: "nouveau E[
+ PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at 0x00b010" (values
+ and addresses varying).
  
- An internet search revealed that the problem is well known. It affects
- many NVidia graphic cards with the "nouveau" driver. Usually, the freeze
- happens when e.g. "firefox" is started (which happens in my context
- automatically after a graphical login). Most reports recommend to switch
- from "nouveau" to the proprietary NVidia driver. However, there seem to
- be problems with that driver for recent Ubuntu versions. I my case, the
- NVidia driver could not be started (I did not investigate why). One
- report suggested the boot parameter "nouveau.config=NvMSI=0" which in my
- case made the graphical login successful again.
+ Usually, the freeze happens when e.g. "firefox" is started (which
+ happens in my context automatically after a graphical login). In my
+ case, the NVidia driver could not be started (I did not investigate
+ why). Using boot parameter "nouveau.config=NvMSI=0" made the graphical
+ login successful again.
  
- Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
+ Today, I wanted to report the bug with "ubuntu-bug". However, during the
+ collection of the system information, the error happened again (despite
+ the "nouveau.config" boot parameter).
+ 
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[224

[Desktop-packages] [Bug 561294] Re: Not a helpful or appropiate error message displayed

2018-02-02 Thread strangedata

uname -a
Linux fc993847 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:13:46 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Not a helpful or appropiate error message displayed

Status in metacity package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: metacity

  
  running compiz --replace as trying to debug an issue with lucid Beta 2 and I 
get the following output -

  Window manager warning: last_user_time (1271002643) is greater than 
comparison timestamp (799652). This most likely represents a buggy client 
sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to 
work around...
  Window manager warning: 0x4600028 (Social bro) appears to be one of the 
offending windows with a timestamp of 1271002643. Working around...
  Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x4600028 
(Social bro); these messages lack timestamps and therefore suck.

  while the error output is helpful surely a user seeing "these messages
  lack timestamps and therefore suck." is not at all helpful and should
  have a more appropriate error message displayed

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

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

[Desktop-packages] [Bug 561294] Re: Not a helpful or appropiate error message displayed

2018-02-02 Thread Alberts Muktupāvels

strangedata, you should report that for gnome-shell, this bug is for
metacity which is not used by gnome shell session.

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

Title:
  Not a helpful or appropiate error message displayed

Status in metacity package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: metacity

  
  running compiz --replace as trying to debug an issue with lucid Beta 2 and I 
get the following output -

  Window manager warning: last_user_time (1271002643) is greater than 
comparison timestamp (799652). This most likely represents a buggy client 
sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to 
work around...
  Window manager warning: 0x4600028 (Social bro) appears to be one of the 
offending windows with a timestamp of 1271002643. Working around...
  Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x4600028 
(Social bro); these messages lack timestamps and therefore suck.

  while the error output is helpful surely a user seeing "these messages
  lack timestamps and therefore suck." is not at all helpful and should
  have a more appropriate error message displayed

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

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

[Desktop-packages] [Bug 1687206] Re: screen goes blank

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml


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

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

Title:
  screen goes blank

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  4 try the charm!! the screen goes blank randomly. I have tried
  every variable,version,bios setting, and ubuntu version. can't even
  get through the istall without hard restart for screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Apr 29 10:38:36 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Carrizo [103c:80b0]
  InstallationDate: Installed on 2017-04-29 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=0e65c208-5506-4e3a-b42c-13d6248c23e1 ro plymouth:debug drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.41
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80B0
  dmi.board.vendor: HP
  dmi.board.version: 81.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.41:bd09/19/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B0:rvr81.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Sat Apr 29 10:37:20 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1
  xserver.video_driver: amdgpu

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

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

[Desktop-packages] [Bug 1687200] Re: [SOLVED] [X441SA, Realtek ALC3236, Speaker, Internal] Playback problem No Sound on internal Speaker, But Normal with Headphones Jack

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml


** Changed in: alsa-driver (Ubuntu)
   Status: New => Invalid

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

Title:
  [SOLVED] [X441SA, Realtek ALC3236, Speaker, Internal] Playback problem
  No Sound on internal Speaker, But Normal with Headphones Jack

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  how to Patch This https://patchwork.kernel.org/patch/9596699/ ?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1545 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Sat Apr 29 21:20:53 2017
  InstallationDate: Installed on 2017-04-23 (6 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Only some of outputs are working
  Title: [X441SA, Realtek ALC3236, Speaker, Internal] Playback problem
  UpgradeStatus: Upgraded to zesty on 2017-04-29 (0 days ago)
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X441SA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X441SA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX441SA.300:bd06/13/2016:svnASUSTeKCOMPUTERINC.:pnX441SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X441SA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-04-25T03:57:03.973122

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

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

[Desktop-packages] [Bug 1649566] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1649566/+attachment/5047625/+files/UdevDb.txt

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

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:09.0 PCI bridge: NVIDIA Corporation MC

[Desktop-packages] [Bug 1746981] Re: Kerning bug in Gentium Plus

2018-02-02 Thread Ubuntu Foundations Team Bug Bot

The attachment "Fixed version of Gentium Plus Italic" seems to be a
patch.  If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Kerning bug in Gentium Plus

Status in fonts-sil-gentium package in Ubuntu:
  New

Bug description:
  Hello,

  The the bad position of the upper anchor on lower case letter 'd' in
  all of the Gentium family fonts leads to incorrect kerning of
  diacritics placed above the said letter.

  I uploaded a fixed version of Gentium Plus Italic with correct
  position of upper anchor on letter 'd'.

  Regards,

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: fonts-sil-gentium 20081126:1.03-1
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Feb  2 13:17:45 2018
  Dependencies:
   
  InstallationDate: Installed on 2017-01-07 (390 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  PackageArchitecture: all
  SourcePackage: fonts-sil-gentium
  UpgradeStatus: Upgraded to artful on 2017-10-24 (101 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-sil-gentium/+bug/1746981/+subscriptions

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

[Desktop-packages] [Bug 1747035] [NEW] The backup is not terminated explicitly.

2018-02-02 Thread Александр

Public bug reported:

1. When you create a backup constantly prompted for the encryption password, 
the box "remember password" is set. 
2. Expect not to see this message unless necessary. 
3. Started backup "/" and the folder "/home" in the manual.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: deja-dup 34.2-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb  2 21:14:56 2018
ExecutablePath: /usr/bin/deja-dup
InstallationDate: Installed on 2018-02-01 (1 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcEnviron:
 PATH=(custom, user)
 SHELL=/bin/bash
 LANG=ru_RU.UTF-8
 LANGUAGE=ru
 XDG_RUNTIME_DIR=
SourcePackage: deja-dup
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: deja-dup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  The backup is not terminated explicitly.

Status in deja-dup package in Ubuntu:
  New

Bug description:
  1. When you create a backup constantly prompted for the encryption password, 
the box "remember password" is set. 
  2. Expect not to see this message unless necessary. 
  3. Started backup "/" and the folder "/home" in the manual.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: deja-dup 34.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb  2 21:14:56 2018
  ExecutablePath: /usr/bin/deja-dup
  InstallationDate: Installed on 2018-02-01 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1738448] Re: gnome-online-accounts should recommend dleyna-server for Media Server support

This bug was fixed in the package gnome-online-accounts - 3.26.2-2

---
gnome-online-accounts (3.26.2-2) unstable; urgency=medium

  * Update Vcs fields for migration to https://salsa.debian.org/
  * Use dh_missing --fail-missing
  * Don't enable Media Server option and drop dleyna-server recommends.
It is an experimental untested feature that was only used in GNOME
Photos and the GNOME Photos maintainer recommended we disable it.
(LP: #1738448)

 -- Jeremy Bicha   Thu, 01 Feb 2018 20:29:48 -0500

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Fix Released

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

Title:
  gnome-online-accounts should recommend dleyna-server for Media Server
  support

Status in gnome-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  Because dleyna-server is in universe, Ubuntu's gnome-online-accounts cannot 
recommend it like the Debian package does. I have pushed a hack to Debian to 
allow us to sync gnome-online-accounts and for the dependencies to be handled 
correctly.
  
https://anonscm.debian.org/git/pkg-gnome/gnome-online-accounts.git/commit/?id=e544639

  I am filing this as an informational bug since this issue will now be
  less visible than if there was a persistent diff with Debian.

  I think this will make the Media Server option in Settings > Online
  Accounts not work, but I don't have a Media Server here to test right
  now. This issue affects Ubuntu 17.10 and newer.

  Ideally, the Media Server account type should be hidden if it doesn't
  work, or modified to allow a user to easily install dleyna-server via
  PackageKit.

  Or we could try to get dleyna-server in to Ubuntu main.

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

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

[Desktop-packages] [Bug 1747009] Re: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-6.7

2018-02-02 Thread Seth Forshee

** Attachment added: "make.log"
   https://bugs.launchpad.net/bugs/1747009/+attachment/5047629/+files/make.log

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

Title:
  nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with
  linux 4.15.0-6.7

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

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-304/20180201_135601_91de8@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/n/nvidia-graphics-drivers-304/20180201_141445_91de8@/log.gz

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

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

[Desktop-packages] [Bug 1747012] [NEW] package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

2018-02-02 Thread PIYUSH CHOUDHARY

Public bug reported:

the top bar the left bar and the plank have vanished and are not
displaying

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gnome-menus 3.13.3-6ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Fri Feb  2 20:33:19 2018
Dependencies:
 
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2017-02-11 (355 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: gnome-menus
Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: Upgraded to xenial on 2018-02-02 (0 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned

Status in gnome-menus package in Ubuntu:
  New

Bug description:
  the top bar the left bar and the plank have vanished and are not
  displaying

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gnome-menus 3.13.3-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Feb  2 20:33:19 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2017-02-11 (355 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2018-02-02 (0 days ago)

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

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

[Desktop-packages] [Bug 1649566] Re: xserver-xorg-video-nouveau: X freeze

apport information

** Tags added: apport-collected ubuntu xenial

** Description changed:

  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS version
  in each case). From 14.04 on, I was unable to graphically log in. A few
  seconds after the login (varying between 1 and 10 s), the screen changed
  to a pattern with dense white stripes on the violet/red background, and
  X froze (no reaction to mouse or keyboard). The latest messages in
  "/var/log/syslog" each time showed varying "nouveau E" problems, e.g.
  "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.:
  "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at
  0x00b010" (values and addresses varying).
  
  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the freeze
  happens when e.g. "firefox" is started (which happens in my context
  automatically after a graphical login). Most reports recommend to switch
  from "nouveau" to the proprietary NVidia driver. However, there seem to
  be problems with that driver for recent Ubuntu versions. I my case, the
  NVidia driver could not be started (I did not investigate why). One
  report suggested the boot parameter "nouveau.config=NvMSI=0" which in my
  case made the graphical login successful again.
  
  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  
  At this point, I had to reset the computer.
  
  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  
  xserver-xorg-video-nouveau 1:1.0.12-1build2
  
  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:09.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2)
  00:0b.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2)
  00:0c.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2)
  00:0d.0 VGA compatible controller: NVIDIA Corporation C61 [GeForce 7025 / 
nForce 630a] (rev a2)
  00:18.0 Host bridge: Advance

[Desktop-packages] [Bug 1686690] Re: When connecting PC from suspended state distorted window borders and background image

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml


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

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

Title:
  When connecting PC from suspended state distorted window borders and
  background image

Status in gnome-terminal package in Ubuntu:
  Invalid

Bug description:
  When I turn on the computer from a suspended state, the background, the 
window border, and the Close, Minimize, and Maximize buttons are distorted.
  To tidy up the background just by changing the background image, it refreshes 
and resolves .. Already the windows I have to open the CompizConfig application 
and refresh the "Fading Windows" item it updates and resolves the distortion in 
the window.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Apr 27 08:22:41 2017
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2017-04-18 (8 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1735929] Re: security problems with incorrect permissions for ubuntu 17.10

2018-02-02 Thread Marc Deslauriers

Related bug in ubuntu-mate-welcome: bug 1745929

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

Title:
  security problems with incorrect permissions for ubuntu 17.10

Status in dconf:
  Confirmed
Status in gnome-session:
  Confirmed
Status in d-conf package in Ubuntu:
  Triaged
Status in dconf package in Ubuntu:
  Triaged
Status in gnome-session package in Ubuntu:
  Triaged
Status in session-migration package in Ubuntu:
  Fix Released

Bug description:
  The release of Ubuntu you are using (lsb_release -rd):
  Description:  Ubuntu 17.10
  Release:  17.10

  This is a fresh installation of Ubuntu 17.10 from the mini.iso.
  I select only default options + [Ubuntu Desktop] installation.

  What you expected to happen:
  My home folder contains the following folders with correct and safe 
permissions after the first login:
  drwx-- 11 user user 4096 Dec  2 17:40 .config
  drwx--  3 user user 4096 Dec  2 17:39 .local

  What happened instead:
  I received these folders after the first login:
  drwxr-xr-x 11 user user 4096 Dec  2 17:40 .config
  drwxr-xr-x  3 user user 4096 Dec  2 17:39 .local
  It is not safe. Any user can access to my .config folders and read for 
example my mail databases

  I'm trying to create a new user...:
  sudo useradd -m user2
  sudo passwd user2
  ... and login then.
  It has the same problem:
  drwxr-xr-x 10 user2 user2 4096 Dec  2 19:44 .config
  drwxr-xr-x  3 user2 user2 4096 Dec  2 19:44 .local

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

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

[Desktop-packages] [Bug 1735998] Re: Decouple unity related settings as unity-settings

2018-02-02 Thread Khurshid Alam

@Jeremy

1)

I only removed unity specific gsettings overrides from ubuntu-settings.

Is there any specific reason to carry unity specific gsettings overrides
in ubuntu-settings? Unity is not a default desktop anymore  nor it is
installed in the default live iso.

2)

We carry unity specific gsettings overrides in unity-settings and make
unity-session depends on unity-settings. That way Ubuntu and Unity
remain separate without overlapping.

3)

And as you said we also want to decouple unity-session from gnome-
session so two pieces code remains separate.

It will easier for us to maintain unity if we keep these separated from
one another.

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

Title:
  Decouple unity related settings as unity-settings

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  This is an attempt to resolve "* Shared GSettings keys" issue listed
  under https://wiki.ubuntu.com/Unity/NotDefaultIssues.

  Ubuntu so far is providing session related overrides for both ubuntu &
  unity sessions in a single package, i.e. ubuntu-settings. But now that
  Unity is not the default desktop it doesn't make any sense to carry
  unity related overrides in ubuntu-settings.

  For this purpose I have created a new project: unity-settings
  (https://code.launchpad.net/~khurshid-alam/unity-settings/trunk) and
  the binary would be unity-settings in universe.

  To make this happen in under 18.04 cycle, the work-flow should be:

  1) Have unity-settings in the universe
  2) Have ubuntu-unity-desktop in the universe
  3) Let ubuntu-unity-desktop depends on unity-settings
  4) Drop unity related settings in ubuntu-settings (merge request in-progress)

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

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

[Desktop-packages] [Bug 1687359] Re: maximising or minimising an HTML5 video sporadically wedges Firefox

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml


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

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

Title:
  maximising or minimising an HTML5 video sporadically wedges Firefox

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  When Firefox has been running for a few days, with tens of tabs loaded
  and has started to run slowly, maximising or minimising a YouTube
  video can wedge it.

  The audio keeps playing until the buffer is exhausted, but everything
  else is hung: no repainting of the window, no response to keyboard
  input. CPU usage does not fall to zero, but to around the steady state
  level it was at before the YouTube page was opened.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: firefox 53.0+build6-0ubuntu0.17.04.1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  BuildID: 20170418122848
  CurrentDesktop: GNOME
  Date: Mon May  1 13:54:57 2017
  ExecutablePath: /usr/lib/firefox/firefox
  InstallationDate: Installed on 2016-12-02 (149 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1649566] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1649566/+attachment/5047620/+files/Lspci.txt

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

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:09.0 PCI bridge: NVIDIA Corporation MCP6

[Desktop-packages] [Bug 1649566] XorgLog.txt

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1649566/+attachment/5047626/+files/XorgLog.txt

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

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:09.0 PCI bridge: NVIDIA Corporation

[Desktop-packages] [Bug 1687352] Re: Graphics Corruption on Hardware Accelerated Softwares

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml


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

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

Title:
  Graphics Corruption on Hardware Accelerated Softwares

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Applications like Blender (downloaded from blender website for linux) and 
SimCity 4 (running through Wine with Hardware Acceleration enabled) have their 
windows graphics corrupted as saw in the attachment's print screen image 
(Blender).
  Maybe this problem is OpenGL related, it's just a guess.
  It didn't occur on Ubuntu 16.10 Yakkety Yak.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Apr 30 23:43:40 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6290] [1002:9807] 
(prog-if 00 [VGA controller])
     Subsystem: Elitegroup Computer Systems Wrestler [Radeon HD 6290] 
[1019:3141]
  InstallationDate: Installed on 2017-01-14 (106 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=2db4e4b3-e99a-4d11-96af-5d10de0134c4 ro rootflags=sync splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.name: HDC-M
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd04/09/2012:svn:pnHDC-M:pvr1.0:rvn:rnHDC-M:rvr1.0:cvn:ct3:cvr1.0:
  dmi.product.name: HDC-M
  dmi.product.version: 1.0
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Sun Apr 30 23:33:33 2017
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1649566] XorgLogOld.txt

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1649566/+attachment/5047627/+files/XorgLogOld.txt

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

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:09.0 PCI bridge: NVIDIA Corpo

[Desktop-packages] [Bug 1688747] Re: frequent unabity to connect to websites, frequent connection problem.

2018-02-02 Thread worksk historya general Antonio Mainardi

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

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

Title:
  frequent unabity to connect to websites, frequent connection problem.

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
   Cabled conection to ADSL. frequently unable to connect to websites,
  restarting network manager resolves problem temporarily. Seems to be
  no problem when connected to VPN. After diconecting VPN connection,
  not able to connect to internet. Restart connection or network manager
  needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat May  6 16:53:50 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-21 (105 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 192.168.1.1 dev enp4s1 proto static metric 100 
   169.254.0.0/16 dev enp4s1 scope link metric 1000 
   192.168.1.0/24 dev enp4s1 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   lono wireless extensions.
   
   enp4s1no wireless extensions.
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (21 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enp4s1  ethernet  connected  /org/freedesktop/NetworkManager/Devices/1  
Connessione via cavo 1  e6fa8c59-3af2-3ef5-9425-38f3b0ed6c60  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1077331] ✈The world's travel search engine Skyscanner compares millions of flights to find you the cheapest deal, fast.

Whether you want to go to Tenerife or Tokyo, we'll find low cost flights to
get you there.
We also find the cheapest hotels and car hire deals.
Just dial: +1 888-369-2751.
Skyscanner is free! When you find your flights and dial (888) 369-2751, we
redirect your call through directly to the airline or travel agent.We
never charge you commission. Nor do we add hidden fees. See more ways we
put you first.
Acclaimed flight comparison Skyscanner is an award winning site recommended
by: The Independent, The Guardian, Which? Travel, BBC Radio 1 and
more!Skyscanner has been consistently found to be comprehensive, fast,
and the best way to find cheap flights.
Just dial: +1 888-369-2751.
Let’s get social! Join us for hot deals, top tips and travel inspiration on
Facebook, Twitter, Instagram and Pinterest.
Find the perfect place to stay
The Trip by Skyscanner community has reviewed tens of thousands of hotels
around the world so you can always find the perfect place to stay, based on
your tribe and your price range.
Simply select your destination, dial +1 888-369-2751, and you are
off!
And now Trip by Skyscanner searches all the top booking sites to make sure to
always find you the lowest price.
Check out some of our most popular destinations:
Chicago-New York$175.50Los Angeles-San Francisco$103.28Los Angeles-New York$175.77Chicago-Los Angeles$325.75Miami-New York$96.03Atlanta-Chicago$100.78Newark-Toronto$299.54Boston-Miami$189.12San Francisco-New York City$293.86San Francisco-Tokyo$690.02Chicago-Minneapolis$95.22Chicago-Washington DC$195.08New York City-Paris$545.81Top Deal 55% Off:
Skyscanner's Flight Deals.
Primary: +1 888-369-2751. 24/7 Support.
Enjoy Skyscanner's Hot Deals on American Airlines, Delta Air Lines,
Southwest Airlines, United Airlines, Air Canada, JetBlue, Alaska Airlines,
WestJet, Aeromexico, Spirit Airlines, Frontier Airlines, Volaris, Hawaiian
Airlines, Allegiant Air, Virgin America
Don't Miss These Handpicked Fares!

Primary +1 888-369-2751. 24/7 Support

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

Title:
fglrx-updates 2:8.982-0ubuntu0.1: fglrx-updates kernel module failed
to build

Status in fglrx-installer-updates package in Ubuntu:
Expired

Bug description:
sony vaio VPCYB1S1E

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: fglrx-updates 2:8.982-0ubuntu0.1
ProcVersionSignature: Ubuntu 3.2.0-33.52-generic 3.2.31
Uname: Linux 3.2.0-33-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu14
Architecture: amd64
DKMSKernelVersion: 3.2.0-33-generic
Date: Sat Nov 10 12:28:28 2012
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64
(20120822.4)
PackageVersion: 2:8.982-0ubuntu0.1
SourcePackage: fglrx-installer-updates
Title: fglrx-updates 2:8.982-0ubuntu0.1: fglrx-updates kernel module failed
to build
UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1077331/+subscriptions

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

[Desktop-packages] [Bug 1077335] Re: The world's travel search engine Skyscanner compares millions of flights to find you the cheapest deal, fast.

2018-02-02 Thread worksk historya general Antonio Mainardi

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

Whether you want to go to Tenerife or Tokyo, we'll find low cost flights
to get you there.
We also find the cheapest hotels and car hire deals.
Just dial: (888) 369-2751.
Skyscanner is free! When you find your flights and dial (888) 369-2751, we
redirect your call through directly to the airline or travel agent.We
never charge you commission. Nor do we add hidden fees. See more ways we
put you first.
Acclaimed flight comparison Skyscanner is an award winning site recommended
by: The Independent, The Guardian, Which? Travel, BBC Radio 1 and
more!Skyscanner has been consistently found to be comprehensive, fast,
and the best way to find cheap flights.
Just dial: (888) 369-2751.
Let’s get social! Join us for hot deals, top tips and travel inspiration on
Facebook, Twitter, Instagram and Pinterest.
Find the perfect place to stay
The Trip by Skyscanner community has reviewed tens of thousands of hotels
around the world so you can always find the perfect place to stay, based on
your tribe and your price range.
Simply select your destination, dial (888) 369-2751, and you are off!
And now Trip by Skyscanner searches all the top booking sites to make sure
to always find you the lowest price.
Check out some of our most popular destinations:
Chicago-New York$175.67Los Angeles-San Francisco$103.27Los Angeles-New York$175.59Chicago-Los Angeles$325.74Miami-New York$96.05Atlanta-Chicago$100.96Newark-Toronto$299.73San Francisco-New York City$293.65Los Angeles-Manila$654.86Chicago-Washington DC$195.82New York City-Toronto$119.58Top Deal 55% Off: Skyscanner's
Flight Deals.
Primary: (888) 369-2751. 24/7 Support.
Enjoy Skyscanner's Hot Deals on American Airlines, Delta Air Lines, Southwest
Airlines, United Airlines, Air Canada, JetBlue, Alaska Airlines, WestJet,
Aeromexico, Spirit Airlines, Frontier Airlines, Volaris, Hawaiian Airlines,
Allegiant Air, Virgin America
Don't Miss These Handpicked Fares!

Primary (888) 369-2751. 24/7 Support

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

Title:
fglrx-updates 2:8.982-0ubuntu0.1: fglrx-updates kernel module failed
to build

Status in fglrx-installer-updates package in Ubuntu:
New

Bug description:
...Installing ATI post-release drivers

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: fglrx-updates 2:8.982-0ubuntu0.1
ProcVersionSignature: Ubuntu 3.2.0-33.52-generic 3.2.31
Uname: Linux 3.2.0-33-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu15
Architecture: amd64
DKMSKernelVersion: 3.2.0-33-generic
Date: Sat Nov 10 12:50:49 2012
MarkForUpload: True
PackageVersion: 2:8.982-0ubuntu0.1
SourcePackage: fglrx-installer-updates
Title: fglrx-updates 2:8.982-0ubuntu0.1: fglrx-updates kernel module failed
to build
UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1077335/+subscriptions

[Desktop-packages] [Bug 1747023] [NEW] [P95_HR, Realtek ALC1220, Black Headphone Out, Right] No sound at all

2018-02-02 Thread Casper

Public bug reported:

External headphones don't work any more. Not sure if realted to the
internal speakers problem: https://bugs.launchpad.net/ubuntu/+source
/alsa-driver/+bug/1721074

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-31-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0:  cc16   2550 F pulseaudio
 /dev/snd/controlC1:  cc16   2550 F pulseaudio
CurrentDesktop: Unity
Date: Fri Feb  2 14:51:06 2018
InstallationDate: Installed on 2017-08-22 (164 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0:  cc16   2550 F pulseaudio
 /dev/snd/controlC1:  cc16   2550 F pulseaudio
Symptom_Jack: Black Headphone Out, Right
Symptom_Type: No sound at all
Title: [P95_HR, Realtek ALC1220, Black Headphone Out, Right] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.02
dmi.board.asset.tag: Tag 12345
dmi.board.name: P95_HR
dmi.board.vendor: CLEVO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02:bd06/29/2017:svnPCSpecialistLimited:pnP95_HR:pvrNotApplicable:rvnCLEVO:rnP95_HR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: P95_HR
dmi.product.version: Not Applicable
dmi.sys.vendor: PC Specialist Limited

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


** Tags: amd64 apport-bug xenial

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

Title:
  [P95_HR, Realtek ALC1220, Black Headphone Out, Right] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  External headphones don't work any more. Not sure if realted to the
  internal speakers problem: https://bugs.launchpad.net/ubuntu/+source
  /alsa-driver/+bug/1721074

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0:  cc16   2550 F pulseaudio
   /dev/snd/controlC1:  cc16   2550 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Feb  2 14:51:06 2018
  InstallationDate: Installed on 2017-08-22 (164 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0:  cc16   2550 F pulseaudio
   /dev/snd/controlC1:  cc16   2550 F pulseaudio
  Symptom_Jack: Black Headphone Out, Right
  Symptom_Type: No sound at all
  Title: [P95_HR, Realtek ALC1220, Black Headphone Out, Right] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P95_HR
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02:bd06/29/2017:svnPCSpecialistLimited:pnP95_HR:pvrNotApplicable:rvnCLEVO:rnP95_HR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P95_HR
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

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

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

[Desktop-packages] [Bug 1687208] Re: wont stay up long enough to post shit

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml


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

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

Title:
  wont stay up long enough to post shit

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  wont stay up long enough to post tried many times

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Apr 29 11:14:16 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Carrizo [103c:80b0]
  InstallationDate: Installed on 2017-04-29 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=0e65c208-5506-4e3a-b42c-13d6248c23e1 ro splash plymouth:debug=1 quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.41
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80B0
  dmi.board.vendor: HP
  dmi.board.version: 81.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.41:bd09/19/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B0:rvr81.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Sat Apr 29 11:12:39 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1
  xserver.video_driver: amdgpu

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

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

[Desktop-packages] [Bug 1649566] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1649566/+attachment/5047623/+files/ProcInterrupts.txt

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

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:09.0 PCI bridge: NVID

[Desktop-packages] [Bug 1687535] Re: PCI/internal sound card not detected

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml


** Changed in: alsa-driver (Ubuntu)
   Status: New => Invalid

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Problem: My audio is not working. I'm getting that "Dummy Output" in
  the sound settings. I've been scouring the web, but nothing I try is
  working. I've tried

  sudo alsa force-reload

  sudo apt-get remove --purge alsa-utils

  sudo apt-get install alsa-utils

  I've tried about every single little thing, and it's driving me crazy.

  Ubuntu dist: Saucy Salamander (13.10, running GNOME-3 Desktop) Results of 
lspci:00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM 
Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB xHCI Host Controller (rev 04)
  00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset 
Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB 
Enhanced Host Controller #2 (rev 04)
  00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High 
Definition Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI 
Express Root Port 1 (rev c4)
  00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 2 (rev c4)
  00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 3 (rev c4)
  00:1c.3 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI 
Express Root Port 4 (rev c4)
  00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB 
Enhanced Host Controller #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation 7 Series Chipset Family LPC Controller 
(rev 04)
  00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port 
SATA Controller [AHCI mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus 
Controller (rev 04)
  00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series 
Chipset Family Thermal Management Controller (rev 04)
  01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188EE 
Wireless Network Adapter (rev 01)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI 
Express Card Reader (rev 01)
  02:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12)
  (wasn't quite sure how much you guys needed) 
  For some reason, I don't have a .asoundrc file or /etc/asoundrc.conf file. I 
can't get into alsamixer either. I've uninstalled, reinstalled, uninstalled, 
and reinstalled alsa-base, alsa-utils, pulseaudio, and even Wine.
  I don't know what else to do at this point. Can you guys help me?

  EDIT: sudo alsa force-reload returns

   Unloading ALSA sound driver modules: (none loaded).
  Loading ALSA sound driver modules: (none to reload).
  Do I have to reinstall Ubuntu?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity:Unity7
  Date: Tue May  2 10:00:25 2017
  InstallationDate: Installed on 2016-10-20 (193 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to zesty on 2017-04-20 (11 days ago)
  dmi.bios.date: 07/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Gateway NE46Rs1
  dmi.board.vendor: Acer
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03:bd07/06/2015:svnAcer:pnGatewayNE46Rs1:pvrTobefilledbyO.E.M.:rvnAcer:rnGatewayNE46Rs1:rvrTobefilledbyO.E.M.:cvnAcer:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: Gateway NE46Rs1
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Acer

To manage notifications about

[Desktop-packages] [Bug 1649566] Re: xserver-xorg-video-nouveau: X freeze

In comment #6 I had reported that "apport-collect 1649566" reproduces
the freeze.

I was now able to successfully transfer the data by calling "apport-
collect" outside the X system. Because, it did not run under X, it might
not contail all information you would like. In this case, let me know
how to obtain the missing information.

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

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (re

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

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1649566/+attachment/5047622/+files/ProcCpuinfoMinimal.txt

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

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:09.0 PCI brid

[Desktop-packages] [Bug 1649566] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1649566/+attachment/5047617/+files/Dependencies.txt

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

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:09.0 PCI bridge: NVIDIA C

[Desktop-packages] [Bug 1649566] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1649566/+attachment/5047616/+files/CurrentDmesg.txt

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

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:09.0 PCI bridge: NVIDIA C

[Desktop-packages] [Bug 1649566] ProcModules.txt