[Desktop-packages] [Bug 2007742] Re: Can't update stage views actor (regarding MetaWindowGroup, MetaWindowActorX11, MetaSurfaceActorX11)

2024-04-29 Thread jean-christophe manciot
Same issue on Ubuntu 24.04 noble LTS:

- gnome-shell: 46.0-0ubuntu5
- linux 6.8.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 14 14:56:46 UTC 
2024 x86_64
- DisplayManager: lightdm 1.30.0-0ubuntu14

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

Title:
  Can't update stage views actor  (regarding MetaWindowGroup,
  MetaWindowActorX11, MetaSurfaceActorX11)

Status in GNOME Shell:
  New
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  These messages repeat:

  [  105.711276] ingenika gnome-shell[2919]: Can't update stage views actor 
[:0x55bba91da500] is on because it needs an 
allocation.
  [  105.711772] ingenika gnome-shell[2919]: Can't update stage views actor 
[:0x55bbac95c330] is on because it needs an 
allocation.
  [  105.711903] ingenika gnome-shell[2919]: Can't update stage views actor 
[:0x55bbae726860] is on because it needs an 
allocation.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  Uname: Linux 6.1.11-060111-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 17 21:54:39 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-08-22 (179 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2023-02-08 (9 days ago)

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


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


[Desktop-packages] [Bug 550856] Re: page size setting is broken, use it as default crop or fix it by other means

2023-09-16 Thread Christophe
(and by the way I found the same issue happens with xsane; my guess is
there is the same bug there)

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

Title:
  page size setting is broken, use it as default crop or fix it by other
  means

Status in Simple Scan:
  Fix Released
Status in Simple Scan 3.10 series:
  Fix Released
Status in Simple Scan 3.11 series:
  Fix Released
Status in simple-scan package in Ubuntu:
  Fix Released
Status in simple-scan source package in Saucy:
  Fix Released
Status in simple-scan source package in Trusty:
  Fix Released

Bug description:
  For some SANE drivers simple scan always scans the largest scan area
  ignoring the "Page Size" setting in the preferences.

  To reproduce:
  1. Open Simple Scan
  2. Set page size in Document > Prefrences > Page Size, e.g. to "4x6"
  3. Scan a document
  Expected result:
  The document is scanned at the requested size
  Observed result:
  The document is scanned at the maximum size

  Regression potential:
  Low. The fix was to set the page size using an alternative method for drivers 
that do not support the page-width, page-height options. There is a small 
chance that these settings might change behaviour / expose bugs on drivers that 
were previously working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/550856/+subscriptions


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


[Desktop-packages] [Bug 550856] Re: page size setting is broken, use it as default crop or fix it by other means

2023-09-16 Thread Christophe
I believe the issue is with ADF only

My option are set as A4 scanning, ADF.

Running de debug mode, i can see the requests for options :

[+135,61s] DEBUG: scanner.vala:795: Option 6: name='tl-x' title='Top-left x' 
type=fixed size=4 unit=mm min=0,00, max=215,84, quant=0 
cap=soft-select,soft-detect
[+135,61s] DEBUG: scanner.vala:798:   Description: Top-left x position of scan 
area.
[+135,61s] DEBUG: scanner.vala:1002: sane_get_option_descriptor (7)
[+135,61s] DEBUG: scanner.vala:795: Option 7: name='tl-y' title='Top-left y' 
type=fixed size=4 unit=mm min=0,00, max=355,51, quant=0 
cap=soft-select,soft-detect
[+135,61s] DEBUG: scanner.vala:798:   Description: Top-left y position of scan 
area.
[+135,61s] DEBUG: scanner.vala:1002: sane_get_option_descriptor (8)
[+135,61s] DEBUG: scanner.vala:795: Option 8: name='br-x' title='Bottom-right 
x' type=fixed size=4 unit=mm min=0,00, max=215,84, quant=0 
cap=soft-select,soft-detect
[+135,61s] DEBUG: scanner.vala:798:   Description: Bottom-right x position of 
scan area.

Then it seems it issues a call for action :

[+135,61s] DEBUG: scanner.vala:602: sane_control_option (4, 
SANE_ACTION_SET_VALUE, source="ADF Duplex") -> (SANE_STATUS_GOOD, "ADF Duplex")
[+135,61s] DEBUG: scanner.vala:602: sane_control_option (3, 
SANE_ACTION_SET_VALUE, mode="Gray") -> (SANE_STATUS_GOOD, "Gray")
[+135,61s] DEBUG: scanner.vala:514: sane_control_option (2, 
SANE_ACTION_SET_VALUE, resolution=200) -> (SANE_STATUS_GOOD, 200)
[+135,61s] DEBUG: scanner.vala:554: sane_control_option (8, 
SANE_ACTION_SET_VALUE, br-x=210,00) -> (SANE_STATUS_GOOD, 210,00)
[+135,61s] DEBUG: scanner.vala:554: sane_control_option (9, 
SANE_ACTION_SET_VALUE, br-y=297,00) -> (SANE_STATUS_GOOD, 297,00)

This will work for flatbed, as the paper, whether A4 of Letter size, is
left-aligned (it tl-x=0, which i guess is the default); however with
ADF, Letter is centered while  A4 paper is centered in he scanning area
which is 21.6cm wide; hence there should be a margin of 0.3 cm on each
side of the scanning aread

that for a flatbed, the offset for top left X should be 0 while for ADF,
the A4 page is centered in the scanner area total width, ie, the top
left X should be 6/2 = 3mm

Am I wrong, or, what is missing here, is a call to set "top left x" ie ,tl-x=3
to offset where the scan range should actually start when scanning A4 with ADF.

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

Title:
  page size setting is broken, use it as default crop or fix it by other
  means

Status in Simple Scan:
  Fix Released
Status in Simple Scan 3.10 series:
  Fix Released
Status in Simple Scan 3.11 series:
  Fix Released
Status in simple-scan package in Ubuntu:
  Fix Released
Status in simple-scan source package in Saucy:
  Fix Released
Status in simple-scan source package in Trusty:
  Fix Released

Bug description:
  For some SANE drivers simple scan always scans the largest scan area
  ignoring the "Page Size" setting in the preferences.

  To reproduce:
  1. Open Simple Scan
  2. Set page size in Document > Prefrences > Page Size, e.g. to "4x6"
  3. Scan a document
  Expected result:
  The document is scanned at the requested size
  Observed result:
  The document is scanned at the maximum size

  Regression potential:
  Low. The fix was to set the page size using an alternative method for drivers 
that do not support the page-width, page-height options. There is a small 
chance that these settings might change behaviour / expose bugs on drivers that 
were previously working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/550856/+subscriptions


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


[Desktop-packages] [Bug 550856] Re: page size setting is broken, use it as default crop or fix it by other means

2023-09-16 Thread Christophe
I am finding the same with a brother adf scanner. Whaterever i do, xsane
or simple-scan will scan with letter witdh (and a bit longer than letter
length), though I tried to set this up do A4 instead.

Any chance to have this fixed ? It sounds unbelievable it has been
around for such a long time

Thanks

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

Title:
  page size setting is broken, use it as default crop or fix it by other
  means

Status in Simple Scan:
  Fix Released
Status in Simple Scan 3.10 series:
  Fix Released
Status in Simple Scan 3.11 series:
  Fix Released
Status in simple-scan package in Ubuntu:
  Fix Released
Status in simple-scan source package in Saucy:
  Fix Released
Status in simple-scan source package in Trusty:
  Fix Released

Bug description:
  For some SANE drivers simple scan always scans the largest scan area
  ignoring the "Page Size" setting in the preferences.

  To reproduce:
  1. Open Simple Scan
  2. Set page size in Document > Prefrences > Page Size, e.g. to "4x6"
  3. Scan a document
  Expected result:
  The document is scanned at the requested size
  Observed result:
  The document is scanned at the maximum size

  Regression potential:
  Low. The fix was to set the page size using an alternative method for drivers 
that do not support the page-width, page-height options. There is a small 
chance that these settings might change behaviour / expose bugs on drivers that 
were previously working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/550856/+subscriptions


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


[Desktop-packages] [Bug 1999084] [NEW] package libgtk2.0-cil 2.12.40-3ubuntu1 failed to install/upgrade: installed libgtk2.0-cil package post-removal script subprocess returned error exit status 1

2022-12-07 Thread Cajazzo Christophe
Public bug reported:

I should uninstall pinta on my ubuntu 22.04 with:
sudo apt remove --purge cli-common ca- certicates-mono mono*
sudo apt autoremove --purge

But after i do:
sudo apt remove mono-runtime pinta
to remove pinta.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libgtk2.0-cil 2.12.40-3ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
Uname: Linux 5.15.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Dec  7 15:16:23 2022
ErrorMessage: installed libgtk2.0-cil package post-removal script subprocess 
returned error exit status 1
InstallationDate: Installed on 2022-10-23 (44 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
SourcePackage: gtk-sharp2
Title: package libgtk2.0-cil 2.12.40-3ubuntu1 failed to install/upgrade: 
installed libgtk2.0-cil package post-removal script subprocess returned error 
exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk-sharp2 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy

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

Title:
  package libgtk2.0-cil 2.12.40-3ubuntu1 failed to install/upgrade:
  installed libgtk2.0-cil package post-removal script subprocess
  returned error exit status 1

Status in gtk-sharp2 package in Ubuntu:
  New

Bug description:
  I should uninstall pinta on my ubuntu 22.04 with:
  sudo apt remove --purge cli-common ca- certicates-mono mono*
  sudo apt autoremove --purge

  But after i do:
  sudo apt remove mono-runtime pinta
  to remove pinta.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libgtk2.0-cil 2.12.40-3ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Dec  7 15:16:23 2022
  ErrorMessage: installed libgtk2.0-cil package post-removal script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2022-10-23 (44 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: gtk-sharp2
  Title: package libgtk2.0-cil 2.12.40-3ubuntu1 failed to install/upgrade: 
installed libgtk2.0-cil package post-removal script subprocess returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual

2022-10-26 Thread Christophe Bourez
Incomprehensible, a new reboot solved my issue

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

Title:
  pcscd 1.9.5-3 do not start automatically, only manual

Status in pcsc-lite package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 22.04 with the latest updates.
  Problem is present with internal smart-card reader and also external usb 
smart-card reader.

  eid-viewer sees no card reader,but When i do:

  sudo pcscd -f

  it is working, also following the tips of Ludovic:
  
https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html

  sudo systemctl stop pcscd.socket
  sudo systemctl start pcscd.socket

  It is working until next restart.

  libacsccid1  version: 1.1.8-1
  libccid version: 1.5.0-2
  pcscd version: 1.9.5-3
  eid-archive version: 2022.3
  eid-mw version: 5.0.28v5.0.28-0u2204-1
  eid-viewer version: 5.0.28v5.0.28-0u2204-1

  In Firefox, my eid card is then also recognized, but only in the ESR
  version, but this is a know Mozilla bug.

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


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


[Desktop-packages] [Bug 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual

2022-10-26 Thread Christophe Bourez
Hello,

I am facing a very similar issue
I managed to make it work on fresh install but it stopped working after a reboot
The two commands above do not resolve on my laptop


$ sudo service pcscd status
○ pcscd.service - PC/SC Smart Card Daemon
 Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor 
preset: enabled)
 Active: inactive (dead) since Wed 2022-10-26 13:52:17 CEST; 6min ago
TriggeredBy: ● pcscd.socket
   Docs: man:pcscd(8)
   Main PID: 88997 (code=exited, status=0/SUCCESS)
CPU: 13ms

oct 26 13:50:59 dadbert systemd[1]: Started PC/SC Smart Card Daemon.
oct 26 13:51:06 dadbert pcscd[88997]:  ccid_usb.c:886:WriteUSB() write 
failed (3/3): LIBUSB_ERROR_TIMEOUT
oct 26 13:51:11 dadbert pcscd[88997]: 05000646 ccid_usb.c:886:WriteUSB() write 
failed (3/3): LIBUSB_ERROR_TIMEOUT
oct 26 13:51:16 dadbert pcscd[88997]: 05000454 ccid_usb.c:886:WriteUSB() write 
failed (3/3): LIBUSB_ERROR_TIMEOUT
oct 26 13:51:16 dadbert pcscd[88997]: 0036 
ifdhandler.c:202:CreateChannelByNameOrChannel() failed
oct 26 13:51:16 dadbert pcscd[88997]: 0277 
readerfactory.c:1138:RFInitializeReader() Open Port 0x20 Failed 
(usb:0a5c/5842:libudev:1:/dev/bus/usb/003/003)
oct 26 13:51:16 dadbert pcscd[88997]: 0017 
readerfactory.c:380:RFAddReader() Broadcom Corp 58200 [Contacted SmartCard] 
(0123456789ABCD) init failed.
oct 26 13:51:16 dadbert pcscd[88997]: 0112 
hotplug_libudev.c:538:HPAddDevice() Failed adding USB device: Broadcom Corp 
58200
oct 26 13:52:17 dadbert systemd[1]: pcscd.service: Deactivated successfully.


$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0a5c:5842 Broadcom Corp. 58200
...

$ pcscd --version
pcsc-lite version 1.9.5.
Copyright (C) 1999-2002 by David Corcoran .
Copyright (C) 2001-2018 by Ludovic Rousseau .
Copyright (C) 2003-2004 by Damien Sauveron .
...


OS: Ubuntu 22.04
Dell Precision 7670

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

Title:
  pcscd 1.9.5-3 do not start automatically, only manual

Status in pcsc-lite package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 22.04 with the latest updates.
  Problem is present with internal smart-card reader and also external usb 
smart-card reader.

  eid-viewer sees no card reader,but When i do:

  sudo pcscd -f

  it is working, also following the tips of Ludovic:
  
https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html

  sudo systemctl stop pcscd.socket
  sudo systemctl start pcscd.socket

  It is working until next restart.

  libacsccid1  version: 1.1.8-1
  libccid version: 1.5.0-2
  pcscd version: 1.9.5-3
  eid-archive version: 2022.3
  eid-mw version: 5.0.28v5.0.28-0u2204-1
  eid-viewer version: 5.0.28v5.0.28-0u2204-1

  In Firefox, my eid card is then also recognized, but only in the ESR
  version, but this is a know Mozilla bug.

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


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


[Desktop-packages] [Bug 1968522] Re: Remmina can't connect to windows 2008 R2

2022-09-22 Thread Jean Christophe André
*** This bug is a duplicate of bug 1954970 ***
https://bugs.launchpad.net/bugs/1954970

I just hit this bug and found out that a temporary working workaround is
to edit your RDP connection in Remmina, go to the advanced settings tab,
then in the negociated security protocol chose RDP security protocol.

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

Title:
  Remmina can't connect to windows 2008 R2

Status in remmina package in Ubuntu:
  Confirmed

Bug description:
  Remmina on Ubuntu 22.04 can't connect to windows server 2008 R2

  error:

  Could not connect to the RDP server "***" via TLS. See the DEBUG
  traces for more information.

  Remmina Version: 1.4.25 (git n/a)

  i think remmina on ubuntu 22.04 doesn't support TLS 1.0

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


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


[Desktop-packages] [Bug 1662244] Re: lightdm causes all greeters to fail to start

2020-12-05 Thread Christophe Chisogne
Upgrading to (K)Ubuntu 18.04.5 LTS basically broke the system as X was
not restarting correctly (black screen instead of lightdm display or
even infinite loop of X crashes based on BIOS/EFI config).

This is critical for non-savvy users as my parents.

The issue is the same as can be seen in
/var/log/lightdm/seat0-greeter.log with repeated messages like

**MEMORY-ERROR***: unity-greeter[1647]: GSlice: failed to allocate 2040 bytes 
(alignment: 2048)...
**MEMORY-ERROR***: unity-greeter[1647]: GSlice: failed to allocate 2040 bytes 
(alignment: 2048)...
**MEMORY-ERROR***: unity-greeter[1647]: GSlice: failed to allocate 2040 bytes 
(alignment: 2048)...

The workaround is indded updating the memlock limits as described above
(adding the 2 lines of the above comment to /etc/security/limits.con).

Thanks for the workaround :)

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

Title:
  lightdm causes all greeters to fail to start

Status in Light Display Manager:
  Invalid
Status in LightDM GTK+ Greeter:
  Invalid
Status in lightdm package in Ubuntu:
  Invalid
Status in unity-greeter package in Ubuntu:
  Invalid

Bug description:
  lightdm is failing to start. Best guess is because of unity-session-
  manager. This is from .xsession-errors.

  dbus-update-activation-environment: setting 
_=/usr/bin/dbus-update-activation-environment
  upstart: click-user-hooks main process (4028) terminated with status 1
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon respawning too fast, stopped
  upstart: indicator-application main process ended, respawning
  upstart: indicator-application main process ended, respawning
  upstart: indicator-application respawning too fast, stopped
  xbrlapi: window 0x03a00084 changed to NULL name
  xbrlapi: window 0x03a00084 changed to NULL name
  xbrlapi: window 0x03c00084 changed to NULL name
  xbrlapi: window 0x03c00084 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  upstart: dbus main process (4023) killed by TERM signal

  
  I've tried to move aside $HOME/.config/dconf/user and that didn't work. I've 
reverted kernel versions and that didn't work. I've moved aside $HOME/.cache 
and that didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Mon Feb  6 10:21:29 2017
  InstallationDate: Installed on 2015-07-20 (566 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to yakkety on 2016-12-14 (53 days ago)

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

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


[Desktop-packages] [Bug 1887891] Re: dav/davs behind proxy doesn't work

2020-07-17 Thread Jean-Christophe
It's done :

https://gitlab.gnome.org/GNOME/gvfs/-/issues/495

** Bug watch added: gitlab.gnome.org/GNOME/gvfs/-/issues #495
   https://gitlab.gnome.org/GNOME/gvfs/-/issues/495

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

Title:
  dav/davs behind proxy doesn't work

Status in gvfs package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 20.04 behind manual proxy.
  When I want to connect on a server with webdav, I have a message : "Erreur 
HTTP : Erreur de résolution de cloud.rochodc.com : Nom ou service inconnu" -> 
DNS Error Name ou service not known

  I can connect to a webdav server on my private network.

  I can connect to cloud.rochodc.com with Firefox and the proxy I use for the 
system.
  I can connect to cloud.rochodc.com with Ubuntu 18.04 with the same proxy and 
nautilus.

  Online account with parameters doesen't work at all.

  JC

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Fri Jul 17 08:22:05 2020
  InstallationDate: Installed on 2020-07-09 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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


[Desktop-packages] [Bug 1887891] [NEW] dav/davs behind proxy doesn't work

2020-07-17 Thread Jean-Christophe
Public bug reported:

I'm using Ubuntu 20.04 behind manual proxy.
When I want to connect on a server with webdav, I have a message : "Erreur HTTP 
: Erreur de résolution de cloud.rochodc.com : Nom ou service inconnu" -> DNS 
Error Name ou service not known

I can connect to a webdav server on my private network.

I can connect to cloud.rochodc.com with Firefox and the proxy I use for the 
system.
I can connect to cloud.rochodc.com with Ubuntu 18.04 with the same proxy and 
nautilus.

Online account with parameters doesen't work at all.

JC

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Fri Jul 17 08:22:05 2020
InstallationDate: Installed on 2020-07-09 (8 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug focal

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

Title:
  dav/davs behind proxy doesn't work

Status in nautilus package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 20.04 behind manual proxy.
  When I want to connect on a server with webdav, I have a message : "Erreur 
HTTP : Erreur de résolution de cloud.rochodc.com : Nom ou service inconnu" -> 
DNS Error Name ou service not known

  I can connect to a webdav server on my private network.

  I can connect to cloud.rochodc.com with Firefox and the proxy I use for the 
system.
  I can connect to cloud.rochodc.com with Ubuntu 18.04 with the same proxy and 
nautilus.

  Online account with parameters doesen't work at all.

  JC

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Fri Jul 17 08:22:05 2020
  InstallationDate: Installed on 2020-07-09 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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


[Desktop-packages] [Bug 1811724] Re: libbd_mdraid.so.2: cannot open shared object file

2020-03-05 Thread jean-christophe manciot
Ubuntu focal
linux 5.4.0-17-generic x86_64
udisks2 2.8.4-1ubuntu1
libblockdev-crypto2 2.23-2ubuntu3

Same issue:
udisksd[1920]: Failed to load the 'mdraid' libblockdev plugin

Installing libblockdev-mdraid2 pulls in mdadm which is not a solution on
systems which don't implement RAID.

On such systems, udisksd should not try to load the 'mdraid' libblockdev
plugin.

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

Title:
  libbd_mdraid.so.2: cannot open shared object file

Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  Had some (probably unrelated?) trouble typing input into login console, and 
went looking through /var/log/syslog : 
  found

  Jan 14 21:10:21 vps39184 udisksd[611]: udisks daemon version 2.8.1 starting
  Jan 14 21:10:22 vps39184 udisksd[611]: failed to load module mdraid: 
libbd_mdraid.so.2: cannot open shared object file: No such file or directory
  Jan 14 21:10:22 vps39184 udisksd[611]: Failed to load the 'mdraid' 
libblockdev plugin

  Seems to give this warning every time I boot.

  udisks2:
Installed: 2.8.1-3
Candidate: 2.8.1-3

  ubuntu: 19.04 disco

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: udisks2 2.8.1-3
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu18
  Architecture: amd64
  CustomUdevRuleFiles: 80-net-setup-link.rules
  Date: Mon Jan 14 21:31:52 2019
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Red Hat KVM
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=/dev/vda1 ro vga16fb.modeset=0 quiet splash
  SourcePackage: udisks2
  UpgradeStatus: Upgraded to disco on 2018-11-23 (52 days ago)
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Seabios
  dmi.bios.version: 0.5.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: Red Hat
  dmi.modalias: 
dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.6.0PC:cvnRedHat:ct1:cvr:
  dmi.product.family: Red Hat Enterprise Linux
  dmi.product.name: KVM
  dmi.product.version: RHEL 6.6.0 PC
  dmi.sys.vendor: Red Hat

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

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


[Desktop-packages] [Bug 1851144] Re: Switching from unity-greeter to lightdm-gtk-greeter prevents lightdm.service from starting

2019-11-05 Thread jean-christophe manciot
No such issue with eaon.

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

Title:
  Switching from unity-greeter to lightdm-gtk-greeter prevents
  lightdm.service from starting

Status in lightdm package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04
  lightdm 1.30.0-0ubuntu2
  lightdm-gtk-greeter 2.0.6-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
  Uname: Linux 5.3.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  Date: Sun Nov  3 16:15:54 2019
  InstallationDate: Installed on 2015-04-28 (1650 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to focal on 2019-11-03 (0 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-30T10:37:29

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

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


[Desktop-packages] [Bug 1851144] [NEW] Switching from unity-greeter to lightdm-gtk-greeter prevents lightdm.service from starting

2019-11-03 Thread jean-christophe manciot
Public bug reported:

Ubuntu 20.04
lightdm 1.30.0-0ubuntu2
lightdm-gtk-greeter 2.0.6-0ubuntu1

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lightdm 1.30.0-0ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
Uname: Linux 5.3.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
Date: Sun Nov  3 16:15:54 2019
InstallationDate: Installed on 2015-04-28 (1650 days ago)
InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: lightdm
UpgradeStatus: Upgraded to focal on 2019-11-03 (0 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2018-10-30T10:37:29

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


** Tags: amd64 apport-bug focal

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

Title:
  Switching from unity-greeter to lightdm-gtk-greeter prevents
  lightdm.service from starting

Status in lightdm package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04
  lightdm 1.30.0-0ubuntu2
  lightdm-gtk-greeter 2.0.6-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
  Uname: Linux 5.3.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  Date: Sun Nov  3 16:15:54 2019
  InstallationDate: Installed on 2015-04-28 (1650 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to focal on 2019-11-03 (0 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-30T10:37:29

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

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


[Desktop-packages] [Bug 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles

2019-10-21 Thread Jean-Christophe Baptiste
It has been fixed in Fedora and Arch, where is the fix for Ubuntu?

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

Title:
  Mutter 3.34.1 broke Night Light, screen color profiles

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen
  color profile switching.  The commit at fault is
  104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict state changes
  when processing update” (which was intended to fix LP bug 1847044).

  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851

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

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


[Desktop-packages] [Bug 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles

2019-10-19 Thread Jean-Christophe Baptiste
Is there a testing package including the fix that we could test please?

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

Title:
  Mutter 3.34.1 broke Night Light, screen color profiles

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen
  color profile switching.  The commit at fault is
  104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict state changes
  when processing update” (which was intended to fix LP bug 1847044).

  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851

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

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


[Desktop-packages] [Bug 1792085] Re: MTP not working/very slow on Bionic

2019-09-29 Thread Christophe Lyon
Like others reported here, I observe the same problem (slowness) with my
Samsung Galaxy A5 and ubuntu-18.04.

I tried Android File Transfer as suggested in comment #10, and it's indeed way 
faster. That being said, I had to switch my phone to using the "Image transfer 
protocol" (MTP (or PTP?), not sure what's the actual name in english), and it 
seems this also sped up access via Thunar.
Switching back to "File transfer protocol", the access is again very slow under 
Thunar.

As other complained, this was reported 1 year ago, and apparently no
progress? (No even a "OK I could reproduce the problem...)

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

Title:
  MTP not working/very slow on Bionic

Status in libmtp:
  New
Status in gvfs package in Ubuntu:
  Incomplete

Bug description:
  Hi, unfortunately (for me) MTP android devices no more work on Ubuntu
  18.04.

  I have used MTP on 16.04 without problems, but on 18.04 it does not
  work. When I connect my Android devices (Samsung A5 and Samsung J3)
  and I try to list directories with many files (e.g. /DCIM/Camera) the
  window hangs until I disconnect the device. Same issue if I try to
  post the command "ls /var/run/1000/gvfs/".

  I have installed Ubuntu 18.04 on two different machines - an older HP
  laptop and a recent DELL laptop - and the issue is present on the all
  of them.

  I suspect a defect on the "libmtp". I tried many alternative solutions
  suggested by the net (e.g. jmtpfs and so on) but anyone worked.

  That's all!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-fuse 1.36.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 06:20:07 2018
  LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1798091] Re: thumbnailer cannot create tempfiles (with apparmor denials)

2019-09-06 Thread Christophe Boschmans
not fixed with ubuntu 19.04 pop os evince 3.32.0-1ubuntu0.1

** Tags removed: cosmic
** Tags added: verification-failed-dingo

** Tags removed: verification-failed-dingo
** Tags added: verification-failed-disco

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

Title:
  thumbnailer cannot create tempfiles (with apparmor denials)

Status in evince package in Ubuntu:
  Fix Released
Status in evince source package in Cosmic:
  Fix Released
Status in evince source package in Disco:
  Fix Released
Status in evince package in Debian:
  Fix Released

Bug description:
  * Impact

  Nautilus fails to generate previews for pdf files

  * Test case

  Download/copy a pdf, open the directory in nautilus, a preview image
  should be displayed

  * Regression potential

  Check that there are no other apparmor denials and the thumbnailer
  works

  
  -

  While trying to create thumbnails in a directory from within nautilus,
  I got:

  [781429.784125] audit: type=1400 audit(1539694722.247:989): apparmor="DENIED" 
operation="mknod" profile="/usr/bin/evince-thumbnailer" 
name="/tmp/gnome-desktop-thumbnailer.png" pid=30937 comm="evince-thumbnai" 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
  [781429.940592] audit: type=1400 audit(1539694722.403:990): apparmor="DENIED" 
operation="mknod" profile="/usr/bin/evince-thumbnailer" 
name="/tmp/gnome-desktop-thumbnailer.png" pid=30941 comm="evince-thumbnai" 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
  [781430.314591] audit: type=1400 audit(1539694722.779:991): apparmor="DENIED" 
operation="mknod" profile="/usr/bin/evince-thumbnailer" 
name="/tmp/gnome-desktop-thumbnailer.png" pid=30945 comm="evince-thumbnai" 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
  [781431.283522] audit: type=1400 audit(1539694723.747:992): apparmor="DENIED" 
operation="mknod" profile="/usr/bin/evince-thumbnailer" 
name="/tmp/gnome-desktop-thumbnailer.png" pid=30949 comm="evince-thumbnai" 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
  [781431.518566] audit: type=1400 audit(1539694723.983:993): apparmor="DENIED" 
operation="mknod" profile="/usr/bin/evince-thumbnailer" 
name="/tmp/gnome-desktop-thumbnailer.png" pid=30953 comm="evince-thumbnai" 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evince 3.30.1-1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 16 14:59:00 2018
  InstallationDate: Installed on 2014-06-19 (1580 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to cosmic on 2018-10-07 (9 days ago)

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

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


[Desktop-packages] [Bug 1724921] Re: VLANs get incorrectly listed under Bluetooth

2019-08-26 Thread Christophe CArré
*** This bug is a duplicate of bug 1785311 ***
https://bugs.launchpad.net/bugs/1785311

Ubuntu 18.04 still affected (up to date August 26, 2019)

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

Title:
  VLANs get incorrectly listed under Bluetooth

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  I expected them to show up under Wired because the VLANs' associated
  adapter is wired.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-gnome 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 11:25:17 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.50.253 dev vlan757 proto static metric 400 
   169.254.0.0/16 dev vlan757 scope link metric 1000 
   192.168.50.0/24 dev vlan757 proto kernel scope link src 192.168.50.222 
metric 400
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH SLAVE 
   VLAN Camera 1a430a37-b4b3-461c-87bd-d60b547dd369  vlan
1508437383  Thu 19 Oct 2017 11:23:03 AM PDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/4  yes vlan757  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8  --
   Wired connection 1  23ca82a4-d9c5-3d59-ac84-56db17873201  802-3-ethernet  
1508433170  Thu 19 Oct 2017 10:12:50 AM PDT  no   4294966297
no/org/freedesktop/NetworkManager/Settings/1  no  --   --   
  --  --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Desktop-packages] [Bug 1232872] Re: NFS / lock problem with LibreOffice wth 13.04

2019-08-21 Thread Christophe Lyon
I had traced this down to a problem with LibreOffice apparently not
releasing the locks.

I added comments to
https://bugs.documentfoundation.org/show_bug.cgi?id=75488

So, the problem is still here, but no one seems to care upstream.


** Bug watch added: Document Foundation Bugzilla #75488
   https://bugs.documentfoundation.org/show_bug.cgi?id=75488

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

Title:
  NFS / lock problem with LibreOffice wth 13.04

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Hi all,

  I have a problem very similar to what is exposed in question #234375.

  Since I upgraded to Ubuntu 13.04 (host x86_64), I have trouble accessing 
documents via NFS with LibreOffice.
  The slash screen display for about 30s, then there is a popup warning saying 
that another user has opened the file, and offering to open a copy, open as 
readonly or cancel.

  The point is, no other user has opened that file (being the only user
  on my personal PC, but storing my documents on NAS).

  So I tried the suggestion about adding "noauto" in /etc/fstab and
  changing /etc/rc.local, with no luck.

  But the modification of /usr/lib/libreoffice/program/soffice:
  ##

  # 
  STAR_PROFILE_LOCKING_DISABLED=1
  export STAR_PROFILE_LOCKING_DISABLED
  #

  # file locking now enabled by default
  #SAL_ENABLE_FILE_LOCKING=1 # <<- if set to 0 ; same trouble ...
  #export SAL_ENABLE_FILE_LOCKING
  ###

  (That is, uncomment the first 2 lines, and commenting the other 2)
  This works OK.

  If this is the official way of fixing things, then I guess LibreOffice
  deserves an update on Ubuntu at least.

  Thanks.

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

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


[Desktop-packages] [Bug 1838199] Re: Firefox ESR in esr/stable channel is never updated by Ubuntu

2019-08-03 Thread Christophe Chausset
OK. Next time I will then report directly to Mozilla in case of update
issues with Firefox ESR.

Thanks for your time and support !

Kind regards

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

Title:
  Firefox ESR in esr/stable channel is never updated by Ubuntu

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Hi,

  I am encountering a severe issue on several Ubuntu 18.04.2 machines
  where I have replaced Firefox by Firefox ESR through "Ubuntu Software
  Center" by selecting esr/stable channel as described in
  https://ubuntu.com/blog/firefox-esr-60-on-ubuntu

  After being installed, Firefox ESR is working as expected but it is
  never updated.

  I mean Firefox ESR is detecting that a new version is available when starting.
  Even "Ubuntu Software Center" shows a newer version exists.

  But when I run either 
  sudo apt-get update
  sudo apt-get upgrade

  or "Software Updater",

  Ubuntu is never updating the Firefox ESR.
  I have reproduced this on 3 different machines running Ubuntu 18.04.2.

  I am not sure if it is the right place to submit this problem report.
  Are you aware of this issue ?

  Thanks

  Kind regards

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

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


[Desktop-packages] [Bug 1838199] Re: Firefox ESR in esr/stable channel is never updated by Ubuntu

2019-08-02 Thread Christophe Chausset
Hi Paul,

Thank you for your kind answer and the information provided.

I confirm that finally Firefox ESR was updated to version 60.8.0esr-1 by itself.
I am just wondering why it took so long time to update.

Next time, I will try to force the update with the command provided
(sudo snap refresh firefox).

Kind regards

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

Title:
  Firefox ESR in esr/stable channel is never updated by Ubuntu

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I am encountering a severe issue on several Ubuntu 18.04.2 machines
  where I have replaced Firefox by Firefox ESR through "Ubuntu Software
  Center" by selecting esr/stable channel as described in
  https://ubuntu.com/blog/firefox-esr-60-on-ubuntu

  After being installed, Firefox ESR is working as expected but it is
  never updated.

  I mean Firefox ESR is detecting that a new version is available when starting.
  Even "Ubuntu Software Center" shows a newer version exists.

  But when I run either 
  sudo apt-get update
  sudo apt-get upgrade

  or "Software Updater",

  Ubuntu is never updating the Firefox ESR.
  I have reproduced this on 3 different machines running Ubuntu 18.04.2.

  I am not sure if it is the right place to submit this problem report.
  Are you aware of this issue ?

  Thanks

  Kind regards

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

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


[Desktop-packages] [Bug 1838199] [NEW] Firefox ESR in esr/stable channel is never updated by Ubuntu

2019-07-28 Thread Christophe Chausset
Public bug reported:

Hi,

I am encountering a severe issue on several Ubuntu 18.04.2 machines
where I have replaced Firefox by Firefox ESR through "Ubuntu Software
Center" by selecting esr/stable channel as described in
https://ubuntu.com/blog/firefox-esr-60-on-ubuntu

After being installed, Firefox ESR is working as expected but it is
never updated.

I mean Firefox ESR is detecting that a new version is available when starting.
Even "Ubuntu Software Center" shows a newer version exists.

But when I run either 
sudo apt-get update
sudo apt-get upgrade

or "Software Updater",

Ubuntu is never updating the Firefox ESR.
I have reproduced this on 3 different machines running Ubuntu 18.04.2.

I am not sure if it is the right place to submit this problem report.
Are you aware of this issue ?

Thanks

Kind regards

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

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

Title:
  Firefox ESR in esr/stable channel is never updated by Ubuntu

Status in firefox package in Ubuntu:
  New

Bug description:
  Hi,

  I am encountering a severe issue on several Ubuntu 18.04.2 machines
  where I have replaced Firefox by Firefox ESR through "Ubuntu Software
  Center" by selecting esr/stable channel as described in
  https://ubuntu.com/blog/firefox-esr-60-on-ubuntu

  After being installed, Firefox ESR is working as expected but it is
  never updated.

  I mean Firefox ESR is detecting that a new version is available when starting.
  Even "Ubuntu Software Center" shows a newer version exists.

  But when I run either 
  sudo apt-get update
  sudo apt-get upgrade

  or "Software Updater",

  Ubuntu is never updating the Firefox ESR.
  I have reproduced this on 3 different machines running Ubuntu 18.04.2.

  I am not sure if it is the right place to submit this problem report.
  Are you aware of this issue ?

  Thanks

  Kind regards

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

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


[Desktop-packages] [Bug 1831384] Re: .desktop files not working in Ubuntu 19.04 Gnome

2019-06-04 Thread Jean-Christophe Baptiste
In gnome-shell itself, in overview mode and either as favorite or not.

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

Title:
  .desktop files not working in Ubuntu 19.04 Gnome

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I use several instances of Firefox, that I usually launch from various
  launchers.

  For example, I have a `firefox-test.desktop` file in
  `~/.local/share/applications`, that contains:

  ```
  [Desktop Entry]
  Version=1.0
  Name=Firefox-Test
  StartupWMClass=firetest
  Exec=firefox --new-instance --no-remote -P Test --class firetest %u
  Icon=firefox-developer-icon
  Terminal=false
  Type=Application
  
MimeType=text/html;text/xml;application/xhtml+xml;application/vnd.mozilla.xul+xml;text/mml;x-scheme-handler/http;x-scheme-handler/https;
  StartupNotify=true
  Categories=Network;WebBrowser;
  Keywords=web;browser;internet;pentest;
  Actions=new-window;new-private-window;
  ```

  It worked for ages, in many DE, including GNOME in 18.04.

  But, in 19.04, clicking on my launchers does nothing.

  On the other hand, the commands works from the terminal:

  ```
  firefox --new-instance --no-remote -P Test --class firetest
  ```

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

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


[Desktop-packages] [Bug 1831384] Re: .desktop files not working in Ubuntu 19.04 Gnome

2019-06-04 Thread Jean-Christophe Baptiste
Log in journalctl:

gnome-shell[610]: g_environ_setenv: assertion 'value != NULL' failed

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

Title:
  .desktop files not working in Ubuntu 19.04 Gnome

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I use several instances of Firefox, that I usually launch from various
  launchers.

  For example, I have a `firefox-test.desktop` file in
  `~/.local/share/applications`, that contains:

  ```
  [Desktop Entry]
  Version=1.0
  Name=Firefox-Test
  StartupWMClass=firetest
  Exec=firefox --new-instance --no-remote -P Test --class firetest %u
  Icon=firefox-developer-icon
  Terminal=false
  Type=Application
  
MimeType=text/html;text/xml;application/xhtml+xml;application/vnd.mozilla.xul+xml;text/mml;x-scheme-handler/http;x-scheme-handler/https;
  StartupNotify=true
  Categories=Network;WebBrowser;
  Keywords=web;browser;internet;pentest;
  Actions=new-window;new-private-window;
  ```

  It worked for ages, in many DE, including GNOME in 18.04.

  But, in 19.04, clicking on my launchers does nothing.

  On the other hand, the commands works from the terminal:

  ```
  firefox --new-instance --no-remote -P Test --class firetest
  ```

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

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


[Desktop-packages] [Bug 1831384] Re: .desktop files not working in Ubuntu 19.04 Gnome

2019-06-04 Thread Jean-Christophe Baptiste
** Package changed: ubuntu => gnome-shell (Ubuntu)

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

Title:
  .desktop files not working in Ubuntu 19.04 Gnome

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I use several instances of Firefox, that I usually launch from various
  launchers.

  For example, I have a `firefox-test.desktop` file in
  `~/.local/share/applications`, that contains:

  ```
  [Desktop Entry]
  Version=1.0
  Name=Firefox-Test
  StartupWMClass=firetest
  Exec=firefox --new-instance --no-remote -P Test --class firetest %u
  Icon=firefox-developer-icon
  Terminal=false
  Type=Application
  
MimeType=text/html;text/xml;application/xhtml+xml;application/vnd.mozilla.xul+xml;text/mml;x-scheme-handler/http;x-scheme-handler/https;
  StartupNotify=true
  Categories=Network;WebBrowser;
  Keywords=web;browser;internet;pentest;
  Actions=new-window;new-private-window;
  ```

  It worked for ages, in many DE, including GNOME in 18.04.

  But, in 19.04, clicking on my launchers does nothing.

  On the other hand, the commands works from the terminal:

  ```
  firefox --new-instance --no-remote -P Test --class firetest
  ```

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

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


[Desktop-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px

2019-05-27 Thread Jean-Christophe Baptiste
upstream bug report confirms that this is a bug in Ubuntu:

https://gitlab.gnome.org/GNOME/gnome-terminal/issues/132

** Bug watch added: gitlab.gnome.org/GNOME/gnome-terminal/issues #132
   https://gitlab.gnome.org/GNOME/gnome-terminal/issues/132

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

Title:
  Scrollbars escape the bottom and right side of the Terminal window by
  1px

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu's orange overlay scrollbars escape the bottom of the window
  during resizing.

  To reproduce try gnome-shell on artful using the Ambiance theme. Open
  a Terminal window and resize it vertically, quickly. Notice the bottom
  of the overlay scrollbar overruns the bottom of the window.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  Date: Thu May 18 15:28:33 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1827235] [NEW] Ordinateur ne s'éteint pas sous ubuntu 18-04 LTS

2019-05-01 Thread PINCHON Christophe
Public bug reported:

Lors de la déonnection de l'ordinteur, l'ordinateur ne s'éteint pas et
reste figé sur les points sous le logo Ubuntu

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
Uname: Linux 4.15.0-48-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: i386
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed May  1 17:30:47 2019
DistUpgraded: 2019-05-01 13:16:39,149 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 710] 
[1462:8c93]
InstallationDate: Installed on 2019-04-30 (1 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
MachineType: Gigabyte Technology Co., Ltd. M720-US3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=9631566a-db77-4321-8f5e-f7dcd5218802 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2019-05-01 (0 days ago)
dmi.bios.date: 09/16/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F6
dmi.board.name: M720-US3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd09/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnM720-US3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM720-US3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: M720-US3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed May  1 17:26:15 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.2
xserver.video_driver: nouveau

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


** Tags: apport-bug bionic compiz-0.9 i386 ubuntu

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

Title:
  Ordinateur ne s'éteint pas sous ubuntu 18-04 LTS

Status in xorg package in Ubuntu:
  New

Bug description:
  Lors de la déonnection de l'ordinteur, l'ordinateur ne s'éteint pas et
  reste figé sur les points sous le logo Ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed May  1 17:30:47 2019
  DistUpgraded: 2019-05-01 13:16:39,149 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 
710] [1462:8c93]
  InstallationDate: Installed on 2019-04-30 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. M720-US3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=9631566a-db77-4321-8f5e-f7dcd5218802 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-05-01 (0 days ago)
  dmi.bios.date: 09/16/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: M720-US3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd09/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnM720-US3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM720-US3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: M720-US3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 

[Desktop-packages] [Bug 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

2019-02-12 Thread jean-christophe manciot
I have just found the following message in syslog:
Feb 12 13:25:56 samsung5-ubuntu colord-sane: message repeated 2 times: [ [bjnp] 
create_broadcast_socket: ERROR - bind socket to local address failed - Cannot 
assign requested address]
that matches:
● colord.service - Manage, Install and Generate Color Profiles
   Loaded: loaded (/lib/systemd/system/colord.service; static; vendor preset: 
enabled)
   Active: active (running) since Tue 2019-02-12 02:30:41 CET; 11h ago
 Main PID: 2098 (colord)
Tasks: 3 (limit: 4915)
   Memory: 14.9M
   CGroup: /system.slice/colord.service
   └─2098 /usr/lib/colord/colord

Feb 12 02:30:41 samsung5-ubuntu systemd[1]: Starting Manage, Install and 
Generate Color Profiles...
Feb 12 02:30:41 samsung5-ubuntu systemd[1]: Started Manage, Install and 
Generate Color Profiles.
Feb 12 02:30:42 samsung5-ubuntu colord[2098]: failed to get session [pid 2118]: 
No data available
Feb 12 02:30:42 samsung5-ubuntu colord-sane[2240]: [bjnp] 
create_broadcast_socket: ERROR - bind socket to local address failed - Cannot 
assign requested address

This lead me to investigate the SANE scanner and more specifically 
/etc/sane.d/dll.conf which seems to list image scanner hardware drivers, 
including canon ones. 
However, commenting out 'net' or all canon-related lines does not change 
anything:
# systemctl restart colord
# systemctl status colord
● colord.service - Manage, Install and Generate Color Profiles
   Loaded: loaded (/lib/systemd/system/colord.service; static; vendor preset: 
enabled)
   Active: active (running) since Tue 2019-02-12 14:21:12 CET; 4s ago
 Main PID: 31838 (colord)
Tasks: 4 (limit: 4915)
   Memory: 8.0M
   CGroup: /system.slice/colord.service
   └─31838 /usr/lib/colord/colord

Feb 12 14:21:12 samsung5-ubuntu systemd[1]: Starting Manage, Install and 
Generate Color Profiles...
Feb 12 14:21:12 samsung5-ubuntu systemd[1]: Started Manage, Install and 
Generate Color Profiles.
Feb 12 14:21:13 samsung5-ubuntu colord-sane[31859]: [bjnp] 
create_broadcast_socket: ERROR - bind socket to local address failed - Cannot 
assign requested address

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

Title:
  CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  It appears that the cups-browsed service as of Xenial (version
  1.8.3-2ubuntu3.1) sends an excessive amount of UDP multicast requests
  for ports 8610 (Canon MFNP) and 8612 (Canon BJNP) under unexpected
  conditions and regardless of a presence or lack of Canon printer
  devices on the network.

  This is manifested by enabling UFW, and observing multicast requests being 
blocked that are sent from the host machine's network IPv4 or IPv6 address to 
the multicast address, e.g.
  [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC= 
DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 
FLOWLBL=96642 PROTO=UDP SPT=8612 DPT=8612 LEN=24

  IN= OUT=wlan0 SRC=192.168.90.45 DST=192.168.91.255 LEN=44 TOS=0x00
  PREC=0x00 TTL=64 ID=7742 DF PROTO=UDP SPT=8612 DPT=8610 LEN=24

  Users have observed that the requests can be reproduced when any USB device 
is plugged/unplugged into the computer, regardless of whether the device has 
anything to do with printing:
  https://twitter.com/gertvdijk/status/621790755758178304
  https://bugs.kali.org/view.php?id=3094

  Just Googling "udp 8612", shows are a large number of results on different 
websites of people who have observed this behaviour in firewall and traffic 
logs, and have noticed that it may contribute to network slowdown and latency:
  https://askubuntu.com/questions/867739/what-is-this-traffic/867786
  
https://serverfault.com/questions/667376/watchguard-blocking-internal-udp-packets

  https://jehurst.wordpress.com/2016/01/22/small-victories/ recommends 
disabling the cups-browsed service to stop these requests:
  systemctl stop cups-browsed.service
  systemctl disable cups-browsed.service

  There are probably two things to address here:
  1. Connecting any USB device should not cause these requests unless the 
device is actually a printer or directly related to printing.
  2. Requests independent of connecting USB devices should be rate limited to a 
degree and/or should be dependent on the actual presence of a Canon printer 
configured on the network.

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

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


[Desktop-packages] [Bug 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

2019-02-12 Thread jean-christophe manciot
I ha

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

Title:
  CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  It appears that the cups-browsed service as of Xenial (version
  1.8.3-2ubuntu3.1) sends an excessive amount of UDP multicast requests
  for ports 8610 (Canon MFNP) and 8612 (Canon BJNP) under unexpected
  conditions and regardless of a presence or lack of Canon printer
  devices on the network.

  This is manifested by enabling UFW, and observing multicast requests being 
blocked that are sent from the host machine's network IPv4 or IPv6 address to 
the multicast address, e.g.
  [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC= 
DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 
FLOWLBL=96642 PROTO=UDP SPT=8612 DPT=8612 LEN=24

  IN= OUT=wlan0 SRC=192.168.90.45 DST=192.168.91.255 LEN=44 TOS=0x00
  PREC=0x00 TTL=64 ID=7742 DF PROTO=UDP SPT=8612 DPT=8610 LEN=24

  Users have observed that the requests can be reproduced when any USB device 
is plugged/unplugged into the computer, regardless of whether the device has 
anything to do with printing:
  https://twitter.com/gertvdijk/status/621790755758178304
  https://bugs.kali.org/view.php?id=3094

  Just Googling "udp 8612", shows are a large number of results on different 
websites of people who have observed this behaviour in firewall and traffic 
logs, and have noticed that it may contribute to network slowdown and latency:
  https://askubuntu.com/questions/867739/what-is-this-traffic/867786
  
https://serverfault.com/questions/667376/watchguard-blocking-internal-udp-packets

  https://jehurst.wordpress.com/2016/01/22/small-victories/ recommends 
disabling the cups-browsed service to stop these requests:
  systemctl stop cups-browsed.service
  systemctl disable cups-browsed.service

  There are probably two things to address here:
  1. Connecting any USB device should not cause these requests unless the 
device is actually a printer or directly related to printing.
  2. Requests independent of connecting USB devices should be rate limited to a 
degree and/or should be dependent on the actual presence of a Canon printer 
configured on the network.

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

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


[Desktop-packages] [Bug 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

2019-02-06 Thread jean-christophe manciot
If anyone knows a way to pinpoint some process which sends some specific
packets, I'd be glad to investigate further.

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

Title:
  CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  It appears that the cups-browsed service as of Xenial (version
  1.8.3-2ubuntu3.1) sends an excessive amount of UDP multicast requests
  for ports 8610 (Canon MFNP) and 8612 (Canon BJNP) under unexpected
  conditions and regardless of a presence or lack of Canon printer
  devices on the network.

  This is manifested by enabling UFW, and observing multicast requests being 
blocked that are sent from the host machine's network IPv4 or IPv6 address to 
the multicast address, e.g.
  [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC= 
DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 
FLOWLBL=96642 PROTO=UDP SPT=8612 DPT=8612 LEN=24

  IN= OUT=wlan0 SRC=192.168.90.45 DST=192.168.91.255 LEN=44 TOS=0x00
  PREC=0x00 TTL=64 ID=7742 DF PROTO=UDP SPT=8612 DPT=8610 LEN=24

  Users have observed that the requests can be reproduced when any USB device 
is plugged/unplugged into the computer, regardless of whether the device has 
anything to do with printing:
  https://twitter.com/gertvdijk/status/621790755758178304
  https://bugs.kali.org/view.php?id=3094

  Just Googling "udp 8612", shows are a large number of results on different 
websites of people who have observed this behaviour in firewall and traffic 
logs, and have noticed that it may contribute to network slowdown and latency:
  https://askubuntu.com/questions/867739/what-is-this-traffic/867786
  
https://serverfault.com/questions/667376/watchguard-blocking-internal-udp-packets

  https://jehurst.wordpress.com/2016/01/22/small-victories/ recommends 
disabling the cups-browsed service to stop these requests:
  systemctl stop cups-browsed.service
  systemctl disable cups-browsed.service

  There are probably two things to address here:
  1. Connecting any USB device should not cause these requests unless the 
device is actually a printer or directly related to printing.
  2. Requests independent of connecting USB devices should be rate limited to a 
degree and/or should be dependent on the actual presence of a Canon printer 
configured on the network.

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

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


[Desktop-packages] [Bug 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

2019-02-06 Thread jean-christophe manciot
I experience the same symptoms on Ubuntu 19.04 disco, but there is no
cups* packages installed:

# apt-cache policy cups*| grep Installed | grep -v none
# 

The issue is definitely unrelated to CUPS.

Some other process sends many strange IPv6/UDP packets to all IPv6 local nodes 
with 2 different types; the wireshark trace shows 2 types of "Discover scanner 
commands":
1. source port 8612 (canon-bjnp2) --> dest port 8610 (canon-mfnp)
2. source port 8612 (canon-bjnp2) --> dest port 8612 (canon-bjnp2)

I have no canon device on the network nor on the server and no USB device 
connected on the server.
There is no canon related package/kernel module installed.

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

Title:
  CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  It appears that the cups-browsed service as of Xenial (version
  1.8.3-2ubuntu3.1) sends an excessive amount of UDP multicast requests
  for ports 8610 (Canon MFNP) and 8612 (Canon BJNP) under unexpected
  conditions and regardless of a presence or lack of Canon printer
  devices on the network.

  This is manifested by enabling UFW, and observing multicast requests being 
blocked that are sent from the host machine's network IPv4 or IPv6 address to 
the multicast address, e.g.
  [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC= 
DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 
FLOWLBL=96642 PROTO=UDP SPT=8612 DPT=8612 LEN=24

  IN= OUT=wlan0 SRC=192.168.90.45 DST=192.168.91.255 LEN=44 TOS=0x00
  PREC=0x00 TTL=64 ID=7742 DF PROTO=UDP SPT=8612 DPT=8610 LEN=24

  Users have observed that the requests can be reproduced when any USB device 
is plugged/unplugged into the computer, regardless of whether the device has 
anything to do with printing:
  https://twitter.com/gertvdijk/status/621790755758178304
  https://bugs.kali.org/view.php?id=3094

  Just Googling "udp 8612", shows are a large number of results on different 
websites of people who have observed this behaviour in firewall and traffic 
logs, and have noticed that it may contribute to network slowdown and latency:
  https://askubuntu.com/questions/867739/what-is-this-traffic/867786
  
https://serverfault.com/questions/667376/watchguard-blocking-internal-udp-packets

  https://jehurst.wordpress.com/2016/01/22/small-victories/ recommends 
disabling the cups-browsed service to stop these requests:
  systemctl stop cups-browsed.service
  systemctl disable cups-browsed.service

  There are probably two things to address here:
  1. Connecting any USB device should not cause these requests unless the 
device is actually a printer or directly related to printing.
  2. Requests independent of connecting USB devices should be rate limited to a 
degree and/or should be dependent on the actual presence of a Canon printer 
configured on the network.

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

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


[Desktop-packages] [Bug 1769409] Re: Support for global menu

2019-01-31 Thread Christophe Boschmans
https://extensions.gnome.org/extension/1250/gnome-global-application-
menu/extension not available working on 18.10 gnome 3.30, even not
supported  any more in future versions of gnome

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

Title:
  Support for global menu

Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  The move to Gnome from Unity was ok except for two major features that
  got lost and those are global menus and pixel saving when maximized.

  Are there any chances of official support in future releases?

  Gnome extension for global menus exists https://github.com/lestcape
  /Gnome-Global-AppMenu and that may be used as a starting point. The
  Ubuntu team already did similar move by including the plugin dash-to-
  dock.

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

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


[Desktop-packages] [Bug 1782618] [NEW] package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2018-07-19 Thread Christophe HAGMANN
Public bug reported:

trying desperately to install ubuntu on a new Kingston SSD drive...

allways a bug bitchin' around :-\

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompositorRunning: None
Date: Thu Jul 19 19:37:30 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] N210 [Geforce 210] PCIe 
graphics adapter [1462:8094]
InstallationDate: Installed on 2018-07-19 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=9f0de313-6b29-4eab-9c70-eba1602a7ede ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Aucun fichier ou dossier de ce type: "/root/Error: command 
['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 
'python'] failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: mesa
Title: package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/03/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: N68C-S UCC
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/03/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-SUCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-package bionic ubuntu

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

Title:
  package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade:
  dpkg-deb --fsys-tarfile subprocess returned error exit status 2

Status in mesa package in Ubuntu:
  New

Bug description:
  trying desperately to install ubuntu on a new Kingston SSD drive...

  allways a bug bitchin' around :-\

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Jul 19 19:37:30 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] N210 [Geforce 210] 
PCIe graphics adapter [1462:8094]
  InstallationDate: Installed on 2018-07-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 046d:c52b Logitech, Inc. Unifying 

[Desktop-packages] [Bug 1699637] Re: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

2018-03-28 Thread Christophe Lyon
Hi,
I've just upgraded my x86_64 laptop to Ubuntu 17.10, and I believe I'm hitting 
the same problem.

In short, I can't login from the lightdm greeter: it accepts my
password, the login process starts and immediately stops and comes back
to the lightdm greeter. It worked well before I upgraded

I had warnings about pam-kwallet.so, which I "solved" by installing
libpam-kwallet and libpam-kwallet5 packages, and manually created
/lib/security symlink pointing to /lib/x86_64-linux-gnu/security. This
fixed the warnings, but not the login problem :(

The next thing I noticed is the error message mentioned in this bug report.
My /var/log/lightdm/lightdm.log file contains:

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.01s] DEBUG: Starting Light Display Manager 1.24.0, UID=0 PID=1208
[+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
[+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf
[+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
[+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
[+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
[+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-unity-greeter.conf
[+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
[+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/60-lightdm-gtk-greeter.conf
[+0.01s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
[+0.01s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.01s] DEBUG: Loading configuration from 
/etc/lightdm/lightdm.conf.d/10-xubuntu.conf
[+0.01s] DEBUG:   [SeatDefaults] is now called [Seat:*], please update this 
configuration
[+0.01s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.01s] DEBUG:   [SeatDefaults] is now called [Seat:*], please update this 
configuration
[+0.01s] DEBUG: Registered seat module local
[+0.01s] DEBUG: Registered seat module xremote
[+0.01s] DEBUG: Registered seat module unity
[+0.01s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.20s] DEBUG: Monitoring logind for seats
[+0.20s] DEBUG: New seat added from logind: seat0
[+0.20s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.20s] DEBUG: Seat seat0: Starting
[+0.20s] DEBUG: Seat seat0: Creating greeter session
[+0.20s] DEBUG: Seat seat0: Creating display server of type x
[+0.20s] DEBUG: Seat seat0: Plymouth is running on VT 1, but this is less than 
the configured minimum of 7 so not replacing it
[+0.20s] DEBUG: Quitting Plymouth
[+0.34s] DEBUG: Using VT 7
[+0.34s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.34s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.34s] DEBUG: XServer 0: Writing X server authority to 
/var/run/lightdm/root/:0
[+0.34s] DEBUG: XServer 0: Launching X Server
[+0.34s] DEBUG: Launching process 1296: /usr/bin/X -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.34s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.34s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.34s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
[+0.35s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.35s] DEBUG: User /org/freedesktop/Accounts/User1001 added
[+0.36s] DEBUG: User /org/freedesktop/Accounts/User1027 added
[+1.32s] DEBUG: Got signal 10 from process 1296
[+1.32s] DEBUG: XServer 0: Got signal from X server :0
[+1.32s] DEBUG: XServer 0: Connecting to XServer :0
[+2.21s] CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
[+2.21s] DEBUG: Seat seat0: Display server ready, starting session 
authentication
[+2.21s] DEBUG: Session pid=1362: Started with service 'lightdm-greeter', 
username 'lightdm'
[+2.23s] DEBUG: Session pid=1362: Authentication complete with return value 0: 
Success
[+2.23s] DEBUG: Seat seat0: Session authenticated, running command
[+2.23s] DEBUG: Session pid=1362: Running command 
/usr/lib/lightdm/lightdm-greeter-session /usr/sbin/lightdm-gtk-greeter
[+2.23s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+2.23s] DEBUG: Session pid=1362: Logging to /var/log/lightdm/seat0-greeter.log
[+2.29s] DEBUG: Activating VT 7
[+2.29s] DEBUG: Activating login1 session c1
[+2.29s] DEBUG: Seat seat0 changes active session to c1
[+2.29s] DEBUG: Session c1 is already active
[+2.49s] DEBUG: Greeter connected version=1.24.0 api=1 resettable=false
[+2.83s] DEBUG: Greeter start authentication for lyon
[+2.83s] DEBUG: Session pid=1422: Started with service 'lightdm', username 
'lyon'
[+2.84s] DEBUG: Session pid=1422: Got 1 message(s) from PAM
[+2.84s] DEBUG: Prompt greeter with 1 message(s)
[+11.59s] DEBUG: Continue authentication

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

2018-01-04 Thread Christophe Roset
Public bug reported:

Package installation fail

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Uname: Linux 4.4.0-104-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
Date: Thu Jan  4 07:50:47 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2011-11-01 (2255 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: tex-common
Title: package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: tex-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

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

Status in tex-common package in Ubuntu:
  New

Bug description:
  Package installation fail

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Thu Jan  4 07:50:47 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2011-11-01 (2255 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather

2017-12-08 Thread Christophe C
In fact the problem is simple : libgweather-common.deb had not package
the traductions (!!).

In debian sid, libgweather-common.deb (3.26.0-1) include (a part of) the trad 
files in /usr/share/locale. For example :
/usr/share/locale/et/LC_MESSAGES/libgweather-3.0.mo
/usr/share/locale/et/LC_MESSAGES/libgweather-locations.mo
/usr/share/locale/eu/LC_MESSAGES/libgweather-3.0.mo
/usr/share/locale/eu/LC_MESSAGES/libgweather-locations.mo
/usr/share/locale/fr/LC_MESSAGES/libgweather-3.0.mo
/usr/share/locale/fr/LC_MESSAGES/libgweather-locations.mo
...

See here the complet list of "normals" files :
https://packages.debian.org/sid/all/libgweather-common/filelist.

In Ubuntu 17.10 and 18.04, libgweather-common.deb has NOT these files.
/usr/share/locale is not include.

I picked the 2 files which interess me in libgweather-common.deb from sid :
/usr/share/locale/fr/LC_MESSAGES/libgweather-3.0.mo
/usr/share/locale/fr/LC_MESSAGES/libgweather-locations.mo
and i copied them (in root) in the same directory on my disk. And GNOME-WEATHER 
just Work. In french.

So please, rebuild libgweather-common.deb with /usr/share/locale/. Or
directly use the sid version

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

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Confirmed
Status in Ubuntu Translations:
  New
Status in gnome-weather package in Ubuntu:
  In Progress
Status in libgweather package in Ubuntu:
  Confirmed

Bug description:
  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

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

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


[Desktop-packages] [Bug 1704870]

2017-11-30 Thread Christophe
(In reply to Matěj Cepl from comment #29)
> I wonder whether it is the same bug, but I don’t have ANY keys inside of the
> VM machine when virt-manager runs under Xsession. Is it?

Could it be https://bugzilla.redhat.com/show_bug.cgi?id=1479682 ?

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

Title:
  Keys can't be grabbed under Wayland

Status in remmina:
  New
Status in wayland:
  Confirmed
Status in remmina package in Ubuntu:
  Confirmed
Status in wayland package in Fedora:
  Confirmed

Bug description:
  Special keys are not working under Remmina.

  Seems to be a Wayland specification and implementation of that
  specification.

  This bug could embrace all apps that need this behavior (VirtualBox,
  vncviewer, etc)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: remmina 1.1.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jul 17 15:36:36 2017
  InstallationDate: Installed on 2017-07-04 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170626)
  SourcePackage: remmina
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1731428] Re: gnome-session-binary: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop

2017-11-10 Thread jean-christophe manciot
There is no TryExec in gnome-settings-daemon.desktop:

[Desktop Entry]
Type=Application
Name=GNOME Settings Daemon
Exec=/usr/lib/gnome-settings-daemon/gnome-settings-daemon-localeexec
OnlyShowIn=GNOME;
NoDisplay=false
X-GNOME-Autostart-Phase=Initialization
X-GNOME-Autostart-Notify=true
X-GNOME-AutoRestart=true
X-Ubuntu-Gettext-Domain=gnome-settings-daemon

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

Title:
  gnome-session-binary: Unrecoverable failure in required component
  org.gnome.SettingsDaemon.Color.desktop

Status in gnome-session package in Ubuntu:
  New

Bug description:
  On Ubuntu 17.10 artful
  gnome-session 3.26.1-0ubuntu6
  gnome-settings-daemon 3.26.1-0ubuntu5

  Nov 10 09:18:44 samsung-ubuntu gnome-session[6947]: 
gnome-session-binary[6947]: WARNING: Application 
'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
  Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: WARNING: 
Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before 
timeout
  Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: Unrecoverable 
failure in required component org.gnome.SettingsDaemon.Color.desktop
  Nov 10 09:18:44 samsung-ubuntu gnome-session[6947]: 
gnome-session-binary[6947]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
  Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: CRITICAL: We 
failed, but the fail whale is dead. Sorry

  There is no other mention of org.gnome.SettingsDaemon.Color.desktop
  before in syslog and kern.log, which is odd.

  However, I found the following lines earlier in syslog regarding 
gnome-settings-daemon:
  Nov 10 09:17:12 samsung-ubuntu gnome-session[6947]: 
gnome-session-binary[6947]: WARNING: Could not parse desktop file 
gnome-settings-daemon.desktop or it references a not found TryExec binary
  Nov 10 09:17:12 samsung-ubuntu gnome-session-binary[6947]: WARNING: Could not 
parse desktop file gnome-settings-daemon.desktop or it references a not found 
TryExec binary

  I'll try to reinstall gnome-settings-daemon.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-settings-daemon 3.26.1-0ubuntu5
  Uname: Linux 4.13.0-16-generic x86_64
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov 10 09:18:44 2017

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

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


[Desktop-packages] [Bug 1731428] [NEW] gnome-session-binary: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop

2017-11-10 Thread jean-christophe manciot
Public bug reported:

On Ubuntu 17.10 artful
gnome-session 3.26.1-0ubuntu6
gnome-settings-daemon 3.26.1-0ubuntu5

Nov 10 09:18:44 samsung-ubuntu gnome-session[6947]: gnome-session-binary[6947]: 
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to 
register before timeout
Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: WARNING: Application 
'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: Unrecoverable 
failure in required component org.gnome.SettingsDaemon.Color.desktop
Nov 10 09:18:44 samsung-ubuntu gnome-session[6947]: gnome-session-binary[6947]: 
CRITICAL: We failed, but the fail whale is dead. Sorry
Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: CRITICAL: We failed, 
but the fail whale is dead. Sorry

There is no other mention of org.gnome.SettingsDaemon.Color.desktop
before in syslog and kern.log, which is odd.

However, I found the following lines earlier in syslog regarding 
gnome-settings-daemon:
Nov 10 09:17:12 samsung-ubuntu gnome-session[6947]: gnome-session-binary[6947]: 
WARNING: Could not parse desktop file gnome-settings-daemon.desktop or it 
references a not found TryExec binary
Nov 10 09:17:12 samsung-ubuntu gnome-session-binary[6947]: WARNING: Could not 
parse desktop file gnome-settings-daemon.desktop or it references a not found 
TryExec binary

I'll try to reinstall gnome-settings-daemon.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-settings-daemon 3.26.1-0ubuntu5
Uname: Linux 4.13.0-16-generic x86_64
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Nov 10 09:18:44 2017

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

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

Title:
  gnome-session-binary: Unrecoverable failure in required component
  org.gnome.SettingsDaemon.Color.desktop

Status in gnome-session package in Ubuntu:
  New

Bug description:
  On Ubuntu 17.10 artful
  gnome-session 3.26.1-0ubuntu6
  gnome-settings-daemon 3.26.1-0ubuntu5

  Nov 10 09:18:44 samsung-ubuntu gnome-session[6947]: 
gnome-session-binary[6947]: WARNING: Application 
'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
  Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: WARNING: 
Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before 
timeout
  Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: Unrecoverable 
failure in required component org.gnome.SettingsDaemon.Color.desktop
  Nov 10 09:18:44 samsung-ubuntu gnome-session[6947]: 
gnome-session-binary[6947]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
  Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: CRITICAL: We 
failed, but the fail whale is dead. Sorry

  There is no other mention of org.gnome.SettingsDaemon.Color.desktop
  before in syslog and kern.log, which is odd.

  However, I found the following lines earlier in syslog regarding 
gnome-settings-daemon:
  Nov 10 09:17:12 samsung-ubuntu gnome-session[6947]: 
gnome-session-binary[6947]: WARNING: Could not parse desktop file 
gnome-settings-daemon.desktop or it references a not found TryExec binary
  Nov 10 09:17:12 samsung-ubuntu gnome-session-binary[6947]: WARNING: Could not 
parse desktop file gnome-settings-daemon.desktop or it references a not found 
TryExec binary

  I'll try to reinstall gnome-settings-daemon.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-settings-daemon 3.26.1-0ubuntu5
  Uname: Linux 4.13.0-16-generic x86_64
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov 10 09:18:44 2017

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

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


[Desktop-packages] [Bug 1730753] [NEW] Cannot connect to Canon Pixma MG5150 printer after upgrade to Ubuntu 17.10

2017-11-07 Thread Christophe Lyon
Public bug reported:

Hello,

After I upgraded my computer (amd64) from Ubuntu 17.04 to 17.10, I can
no longer use my Canon Pixma MG5150 printer.

The existing printer still appears as the default printer, but the
documents do not get printed, despite it is active etc...

I tried to create another printer, choosing USB as connection method,
and I'm offered with a prompt to open Ubuntu "Software" to install the
relevant driver, but then I get to a page saying the needed driver was
not found.

At this stage the printer does not work, and I noticed this in the logs:
[ 135.171773] usblp0: removed
[ 135.192165] usblp 2-2:1.1: usblp0: USB Bidirectional printer dev 2 if 1 alt 0 
proto 2 vid 0x04A9 pid 0x1748

lsusb says:
 Bus 002 Device 002: ID 04a9:1748 Canon, Inc. Pixma MG5150

As a workaround, I installed Canon's drivers manually from
http://fr.software.canon-europe.com/index.asp (cnijfilter-common, 
cnijfilter-mg5100series, scangearmp-common and scangearmp-mg5100series). I also 
had install the old libtiff4 from Ubuntu precise (only libtiff5 is now normally 
installed).

Is my printer now unsupported by gutenprint or is it a bug/regression?

Thanks

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

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

Title:
  Cannot connect to Canon Pixma MG5150 printer after upgrade to Ubuntu
  17.10

Status in gutenprint package in Ubuntu:
  New

Bug description:
  Hello,

  After I upgraded my computer (amd64) from Ubuntu 17.04 to 17.10, I can
  no longer use my Canon Pixma MG5150 printer.

  The existing printer still appears as the default printer, but the
  documents do not get printed, despite it is active etc...

  I tried to create another printer, choosing USB as connection method,
  and I'm offered with a prompt to open Ubuntu "Software" to install the
  relevant driver, but then I get to a page saying the needed driver was
  not found.

  At this stage the printer does not work, and I noticed this in the logs:
  [ 135.171773] usblp0: removed
  [ 135.192165] usblp 2-2:1.1: usblp0: USB Bidirectional printer dev 2 if 1 alt 
0 proto 2 vid 0x04A9 pid 0x1748

  lsusb says:
   Bus 002 Device 002: ID 04a9:1748 Canon, Inc. Pixma MG5150

  As a workaround, I installed Canon's drivers manually from
  http://fr.software.canon-europe.com/index.asp (cnijfilter-common, 
cnijfilter-mg5100series, scangearmp-common and scangearmp-mg5100series). I also 
had install the old libtiff4 from Ubuntu precise (only libtiff5 is now normally 
installed).

  Is my printer now unsupported by gutenprint or is it a bug/regression?

  Thanks

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

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


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

2017-10-26 Thread Christophe APPERRY
Public bug reported:

I was trying to install MS Office 2013 with CrossOver

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
Date: Fri Oct 27 00:53:05 2017
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 2017-10-18 (8 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu1 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: Upgraded to artful on 2017-10-24 (2 days ago)

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


** Tags: amd64 apport-package artful

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu1 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:
  I was trying to install MS Office 2013 with CrossOver

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 00:53:05 2017
  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 2017-10-18 (8 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu1 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: Upgraded to artful on 2017-10-24 (2 days ago)

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

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


[Desktop-packages] [Bug 1726494] Re: nautilus crashed with SIGSEGV in stop_cache_selection_list()

2017-10-26 Thread Christophe Meron
Hi,

I described how it happened for me on my duplicate #1727446 but i can't
reproduce it doing the same steps

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

Title:
  nautilus crashed with SIGSEGV in stop_cache_selection_list()

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  hey

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 22:24:14 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-10-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_IN:en
   LANG=en_IN
  SegvAnalysis:
   Segfault happened at: 0x557557069bf0:mov0x38(%r13),%rdi
   PC (0x557557069bf0) ok
   source "0x38(%r13)" (0x0038) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in g_closure_invoke()
  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/nautilus/+bug/1726494/+subscriptions

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


[Desktop-packages] [Bug 1722811] Re: gnome-shell crashed with SIGSEGV in meta_workspace_get_work_area_for_monitor()

2017-10-11 Thread Christophe Meron
Got a very similar issue here, except:
- i was using Xorg
- i didnt used the UI, but used a script which does a 'dconf write 
/org/gnome/desktop/interface/text-scaling-factor 1.5'

Same caller:

#0  0x7f665c6c3877 in meta_workspace_get_work_area_for_monitor () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
#1  0x7f66580d3e18 in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
#2  0x7f66580d387a in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6

Here is the full apport crash log attached if it may help

** Attachment added: "gnome-shell.123.crash.gz"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722811/+attachment/4968072/+files/gnome-shell.123.crash.gz

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

Title:
  gnome-shell crashed with SIGSEGV in
  meta_workspace_get_work_area_for_monitor()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When I set the Scale of the Built-in display at gnome-control-center >
  Devices > Displays from 200% to 100% and click "Apply", the gnome-
  shell session crashed and brought me back to the login screen.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 09:37:07 2017
  DisplayManager: lightdm
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 
'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 
'ubuntu-amazon-default.desktop', 'gnome-control-center.desktop', 
'hexchat.desktop', 'chromium-browser.desktop', 'chromium_chromium.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-03-14 (211 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170228)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fc7a0cfa877 
:  movdqu 0x8(%rax),%xmm0
   PC (0x7fc7a0cfa877) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%xmm0" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_workspace_get_work_area_for_monitor () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in 
meta_workspace_get_work_area_for_monitor()
  UpgradeStatus: Upgraded to artful on 2017-10-11 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1705157] Re: On fresh install or fresh boot greeter always show "ubuntu" though selected session may be ubuntu-wayland

2017-08-27 Thread Christophe C
1. On fresh install 1st. login, says "ubuntu" but session is xorg
2. i quit the session and login under "Ubuntu" => xorg
3. I leave the session and login under Ubuntu Xorg => xorg
4. I deconnect the session  and login under "Ubuntu" => Wayland

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

Title:
  On fresh install or fresh boot greeter always show "ubuntu" though
  selected session may be ubuntu-wayland

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

Bug description:
  Test case:
  Do a fresh install of current image (july 19 here
  Boot up, check selected session at the greeter - it will say "ubuntu"
  Log in, ck. env., it will actually be ubuntu-wayland

  Ex.
  $ env | grep -i wayland
  DESKTOP_SESSION=ubuntu-wayland
  WAYLAND_DISPLAY=wayland-0
  XDG_SESSION_TYPE=wayland
  XDG_SESSION_DESKTOP=ubuntu-wayland
  GDMSESSION=ubuntu-wayland

  Test 2:
  From above log out, switch session in greeter to wayland on ubuntu,, switch 
back to ubuntu, login.
  Now you'll be in an ubuntu session

  Test 3:
  log out from above ubuntu session, log into ubuntu-wayland session, reboot.
  At greeter notice it says "ubuntu" selected.
  Login, ck. session. You'll actually be in an ubuntu-wayland session

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-session 3.24.1-0ubuntu15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 21:48:10 2017
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170718)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1711801] JournalErrors.txt

2017-08-21 Thread Christophe C
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1711801/+attachment/4936441/+files/JournalErrors.txt

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

Title:
  Packages in both Snap and .deb form show twice (e.g. GIMP)

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Gimp appears twice in gnome-software in french : one description is in
  english, the other on in french. Ubuntu 17.04.

  Probably a problem in appstream description (?)

  See image.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-12 (160 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: gnome-software 3.22.7-0ubuntu3.17.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags: zesty package-from-proposed third-party-packages
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-12 (162 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: gnome-software 3.22.7-0ubuntu3.17.04.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags: zesty package-from-proposed third-party-packages
  Uname: Linux 4.10.0-33-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/gnome-software/+bug/1711801/+subscriptions

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


[Desktop-packages] [Bug 1711801] Re: Packages in both Snap and .deb form show twice (e.g. GIMP)

2017-08-21 Thread Christophe C
Apport done.

I understand the 2 lines : one snap and one deb.

But today it's absolutly confusing. It's important to insist about a
clear presentation of what you install.

I'm nearly sure that 90% of ubunteros don't know what is a snap package.

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

Title:
  Packages in both Snap and .deb form show twice (e.g. GIMP)

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Gimp appears twice in gnome-software in french : one description is in
  english, the other on in french. Ubuntu 17.04.

  Probably a problem in appstream description (?)

  See image.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-12 (160 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: gnome-software 3.22.7-0ubuntu3.17.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags: zesty package-from-proposed third-party-packages
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-12 (162 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: gnome-software 3.22.7-0ubuntu3.17.04.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags: zesty package-from-proposed third-party-packages
  Uname: Linux 4.10.0-33-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/gnome-software/+bug/1711801/+subscriptions

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


[Desktop-packages] [Bug 1711801] ProcEnviron.txt

2017-08-21 Thread Christophe C
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1711801/+attachment/4936443/+files/ProcEnviron.txt

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

Title:
  Packages in both Snap and .deb form show twice (e.g. GIMP)

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Gimp appears twice in gnome-software in french : one description is in
  english, the other on in french. Ubuntu 17.04.

  Probably a problem in appstream description (?)

  See image.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-12 (160 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: gnome-software 3.22.7-0ubuntu3.17.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags: zesty package-from-proposed third-party-packages
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-12 (162 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: gnome-software 3.22.7-0ubuntu3.17.04.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags: zesty package-from-proposed third-party-packages
  Uname: Linux 4.10.0-33-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/gnome-software/+bug/1711801/+subscriptions

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


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

2017-08-21 Thread Christophe C
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1711801/+attachment/4936442/+files/ProcCpuinfoMinimal.txt

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

Title:
  Packages in both Snap and .deb form show twice (e.g. GIMP)

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Gimp appears twice in gnome-software in french : one description is in
  english, the other on in french. Ubuntu 17.04.

  Probably a problem in appstream description (?)

  See image.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-12 (160 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: gnome-software 3.22.7-0ubuntu3.17.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags: zesty package-from-proposed third-party-packages
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-12 (162 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: gnome-software 3.22.7-0ubuntu3.17.04.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags: zesty package-from-proposed third-party-packages
  Uname: Linux 4.10.0-33-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/gnome-software/+bug/1711801/+subscriptions

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


[Desktop-packages] [Bug 1711801] Re: Packages in both Snap and .deb form show twice (e.g. GIMP)

2017-08-21 Thread Christophe C
apport information

** Description changed:

  Gimp appears twice in gnome-software in french : one description is in
  english, the other on in french. Ubuntu 17.04.
  
  Probably a problem in appstream description (?)
  
  See image.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-12 (160 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: gnome-software 3.22.7-0ubuntu3.17.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags: zesty package-from-proposed third-party-packages
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
+ --- 
+ ApportVersion: 2.20.4-0ubuntu4.5
+ Architecture: amd64
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 17.04
+ InstallationDate: Installed on 2017-03-12 (162 days ago)
+ InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
+ Package: gnome-software 3.22.7-0ubuntu3.17.04.6
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
+ Tags: zesty package-from-proposed third-party-packages
+ Uname: Linux 4.10.0-33-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1711801/+attachment/4936440/+files/Dependencies.txt

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

Title:
  Packages in both Snap and .deb form show twice (e.g. GIMP)

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Gimp appears twice in gnome-software in french : one description is in
  english, the other on in french. Ubuntu 17.04.

  Probably a problem in appstream description (?)

  See image.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-12 (160 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: gnome-software 3.22.7-0ubuntu3.17.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags: zesty package-from-proposed third-party-packages
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-12 (162 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: gnome-software 3.22.7-0ubuntu3.17.04.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags: zesty package-from-proposed third-party-packages
  Uname: Linux 4.10.0-33-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/gnome-software/+bug/1711801/+subscriptions

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


Re: [Desktop-packages] [Bug 1711801] Re: Gimp appears twice in gnome-software in french

2017-08-19 Thread Christophe C
Le 19/08/2017 à 10:20, Amr Ibrahim a écrit :
> apport-collect 1711801

done

-- 
-> http://batraciens.net/ - "BATRACIENS" : Articles et photos sur 
l'élevage et la maintenance des batraciens, aquatiques ou terrestres. 
Petites annonces.
-> http://css-astuces.batraciens.net/ - "CSS-ASTUCES" : Trucs et astuces 
de codage CSS pour enrichir vos pages Web.

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

Title:
  Gimp appears twice in gnome-software in french

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Gimp appears twice in gnome-software in french : one description is in
  english, the other on in french. Ubuntu 17.04.

  Probably a problem in appstream description (?)

  See image.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-12 (160 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: gnome-software 3.22.7-0ubuntu3.17.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags: zesty package-from-proposed third-party-packages
  Uname: Linux 4.10.0-33-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/gnome-software/+bug/1711801/+subscriptions

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


[Desktop-packages] [Bug 1711801] JournalErrors.txt

2017-08-19 Thread Christophe C
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1711801/+attachment/4935212/+files/JournalErrors.txt

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

Title:
  Gimp appears twice in gnome-software in french

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Gimp appears twice in gnome-software in french : one description is in
  english, the other on in french. Ubuntu 17.04.

  Probably a problem in appstream description (?)

  See image.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-12 (160 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: gnome-software 3.22.7-0ubuntu3.17.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags: zesty package-from-proposed third-party-packages
  Uname: Linux 4.10.0-33-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/gnome-software/+bug/1711801/+subscriptions

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


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

2017-08-19 Thread Christophe C
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1711801/+attachment/4935213/+files/ProcCpuinfoMinimal.txt

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

Title:
  Gimp appears twice in gnome-software in french

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Gimp appears twice in gnome-software in french : one description is in
  english, the other on in french. Ubuntu 17.04.

  Probably a problem in appstream description (?)

  See image.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-12 (160 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: gnome-software 3.22.7-0ubuntu3.17.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags: zesty package-from-proposed third-party-packages
  Uname: Linux 4.10.0-33-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/gnome-software/+bug/1711801/+subscriptions

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


[Desktop-packages] [Bug 1711801] Re: Gimp appears twice in gnome-software in french

2017-08-19 Thread Christophe C
apport information

** Tags added: apport-collected package-from-proposed third-party-
packages zesty

** Description changed:

  Gimp appears twice in gnome-software in french : one description is in
  english, the other on in french. Ubuntu 17.04.
  
  Probably a problem in appstream description (?)
  
  See image.
+ --- 
+ ApportVersion: 2.20.4-0ubuntu4.5
+ Architecture: amd64
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 17.04
+ InstallationDate: Installed on 2017-03-12 (160 days ago)
+ InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
+ Package: gnome-software 3.22.7-0ubuntu3.17.04.6
+ PackageArchitecture: amd64
+ ProcEnviron:
+  LANGUAGE=fr_FR
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
+ Tags: zesty package-from-proposed third-party-packages
+ Uname: Linux 4.10.0-33-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1711801/+attachment/4935211/+files/Dependencies.txt

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

Title:
  Gimp appears twice in gnome-software in french

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Gimp appears twice in gnome-software in french : one description is in
  english, the other on in french. Ubuntu 17.04.

  Probably a problem in appstream description (?)

  See image.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-12 (160 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: gnome-software 3.22.7-0ubuntu3.17.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags: zesty package-from-proposed third-party-packages
  Uname: Linux 4.10.0-33-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/gnome-software/+bug/1711801/+subscriptions

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


Re: [Desktop-packages] [Bug 1711801] Re: Gimp appears twice in gnome-software in french

2017-08-19 Thread Christophe C
Le 19/08/2017 à 10:18, Amr Ibrahim a écrit :
> Thanks for filing a bug to help improve Ubuntu.
> 
> In the future, please use 'ubuntu-bug package-name' to report Ubuntu bugs.
> https://help.ubuntu.com/community/ReportingBugs
> 
> ** Package changed: plank (Ubuntu) => gnome-software (Ubuntu)
> 


Excuse me, but Jeremy Bicha (jbicha) ask me 
(https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1711728) 
to DON'T creat the bug in gnome-software, but in the specific package of 
the application.

Christophe.


Please file individual bugs against those apps and add the tag
'appstream'. If you can find the upstream bug tracker for a specific
app, it would probably be useful to file a bug there too.

I'm closing this bug because it's not specific enough to be fixed.

** Changed in: gnome-software (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1711728

Title:
  many applications are missing

Status in gnome-software package in Ubuntu:
  Invalid

Bug description:
  Many applications, even populars, are missing : conky, plank ...
  They are in the default repository.

  Probably because of missing appstream descriptions (?)

  People who don't use command lines are unable to access to thses
  applications.

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

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

Title:
  Gimp appears twice in gnome-software in french

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Gimp appears twice in gnome-software in french : one description is in
  english, the other on in french. Ubuntu 17.04.

  Probably a problem in appstream description (?)

  See image.

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

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


[Desktop-packages] [Bug 1711728] [NEW] many applications are missing

2017-08-18 Thread Christophe C
Public bug reported:

Many applications, even populars, are missing : conky, plank ...
They are in the default repository.

Probably because of missing appstream descriptions (?)

People who don't use command lines are unable to access to thses
applications.

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

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

Title:
  many applications are missing

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Many applications, even populars, are missing : conky, plank ...
  They are in the default repository.

  Probably because of missing appstream descriptions (?)

  People who don't use command lines are unable to access to thses
  applications.

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

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


[Desktop-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather

2017-08-18 Thread Christophe C
2017-08-18 - Ubuntu Gnome 17.04 - meteo mix franche and english. Exemple
: "Broken clouds, puis Drizzle, suivi par Overcast plus tard.
Température ressentie : 22,0°C"

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

Title:
  French language locale missing : Gnome-Weather

Status in Ubuntu Translations:
  New
Status in gnome-weather package in Ubuntu:
  In Progress
Status in libgweather package in Ubuntu:
  Confirmed

Bug description:
  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

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

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


[Desktop-packages] [Bug 1622306] Re: Scanning from CanoScan Lide 120 results in black pages only

2017-05-11 Thread Christophe Olivé
Hello, all.

 Scanner CanoScan Lide 120 is detected but doesn't work with Simplescan
or Xsane. Ubuntu 16.04 LTS.

May be because The sane-genesys library implements a SANE (Scanner
Access Now Easy) backend that provides access to USB flatbed scanners
based on the Genesys GL646, GL841, GL843, GL847 and GL124 chips.

the canoscan Lide 120 is based on a GL848+ !

not supported !!!

thanks to see that.

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

Title:
  Scanning from CanoScan Lide 120 results in black pages only

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Scanning from simple-scan using a CanoScan LIDE 120 has very different
  results:

  Ubuntu 14 originally comes with a sane-driver that does not support
  this scanner.

  Ubuntu 15 & 16 with original sane-package produces only black empty
  pages.

  Ubuntu 16 LTS with self-built sane version 1.25 or 1.26 (daily GIT
  snapshot) produces only black and empty pages.

  WORKAROUND: Ubuntu 14 with additional sane-package out of apt-
  repository from ppa:rolfbensch/sane-git works without problems.

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

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


[Desktop-packages] [Bug 1670630] UdevDb.txt

2017-03-07 Thread Christophe Ségui
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1670630/+attachment/4832960/+files/UdevDb.txt

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

Title:
  Multiple impression renders n^2 copies

Status in cups package in Ubuntu:
  New

Bug description:
  When trying to print with any application using gnome print backend 
(libreoffice,evince, ) and selecting multiple copies and collate assembly, 
the print actually prints n^2 copies (where n is the asked number).
  The problem exist with gnome shipped with Ubuntu 16.04. Does not happen with 
ubuntu 16.10 nor 14.

  this is not happening on kde environement on the same machine (or when
  using kde apps such as okular in gnome environment)

  lsb release :
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy ubuntu-gnome-desktop:
  ubuntu-gnome-desktop:
    Installé : 0.58.2
    Candidat : 0.58.2
   Table de version :
   *** 0.58.2 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.58 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-05-27 (283 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  KernLog: [945465.755265] audit: type=1400 audit(1488896787.907:33): 
apparmor="ALLOWED" operation="open" profile="/usr/sbin/sssd" 
name="/run/systemd/users/1396" pid=9279 comm="krb5_child" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  MachineType: Hewlett-Packard HP Compaq Pro 6300 MT
  Package: cups 2.1.3-4
  PackageArchitecture: amd64
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Tags:  xenial
  Uname: Linux 4.4.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.05
  dmi.board.asset.tag: CZC242D8L4
  dmi.board.name: 339A
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC242D8L4
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.05:bd05/07/2012:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq Pro 6300 MT
  dmi.sys.vendor: Hewlett-Packard

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

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


[Desktop-packages] [Bug 1670630] PpdFiles.txt

2017-03-07 Thread Christophe Ségui
apport information

** Attachment added: "PpdFiles.txt"
   
https://bugs.launchpad.net/bugs/1670630/+attachment/4832955/+files/PpdFiles.txt

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

Title:
  Multiple impression renders n^2 copies

Status in cups package in Ubuntu:
  New

Bug description:
  When trying to print with any application using gnome print backend 
(libreoffice,evince, ) and selecting multiple copies and collate assembly, 
the print actually prints n^2 copies (where n is the asked number).
  The problem exist with gnome shipped with Ubuntu 16.04. Does not happen with 
ubuntu 16.10 nor 14.

  this is not happening on kde environement on the same machine (or when
  using kde apps such as okular in gnome environment)

  lsb release :
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy ubuntu-gnome-desktop:
  ubuntu-gnome-desktop:
    Installé : 0.58.2
    Candidat : 0.58.2
   Table de version :
   *** 0.58.2 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.58 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-05-27 (283 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  KernLog: [945465.755265] audit: type=1400 audit(1488896787.907:33): 
apparmor="ALLOWED" operation="open" profile="/usr/sbin/sssd" 
name="/run/systemd/users/1396" pid=9279 comm="krb5_child" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  MachineType: Hewlett-Packard HP Compaq Pro 6300 MT
  Package: cups 2.1.3-4
  PackageArchitecture: amd64
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Tags:  xenial
  Uname: Linux 4.4.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.05
  dmi.board.asset.tag: CZC242D8L4
  dmi.board.name: 339A
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC242D8L4
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.05:bd05/07/2012:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq Pro 6300 MT
  dmi.sys.vendor: Hewlett-Packard

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

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


[Desktop-packages] [Bug 1670630] ProcModules.txt

2017-03-07 Thread Christophe Ségui
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1670630/+attachment/4832959/+files/ProcModules.txt

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

Title:
  Multiple impression renders n^2 copies

Status in cups package in Ubuntu:
  New

Bug description:
  When trying to print with any application using gnome print backend 
(libreoffice,evince, ) and selecting multiple copies and collate assembly, 
the print actually prints n^2 copies (where n is the asked number).
  The problem exist with gnome shipped with Ubuntu 16.04. Does not happen with 
ubuntu 16.10 nor 14.

  this is not happening on kde environement on the same machine (or when
  using kde apps such as okular in gnome environment)

  lsb release :
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy ubuntu-gnome-desktop:
  ubuntu-gnome-desktop:
    Installé : 0.58.2
    Candidat : 0.58.2
   Table de version :
   *** 0.58.2 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.58 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-05-27 (283 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  KernLog: [945465.755265] audit: type=1400 audit(1488896787.907:33): 
apparmor="ALLOWED" operation="open" profile="/usr/sbin/sssd" 
name="/run/systemd/users/1396" pid=9279 comm="krb5_child" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  MachineType: Hewlett-Packard HP Compaq Pro 6300 MT
  Package: cups 2.1.3-4
  PackageArchitecture: amd64
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Tags:  xenial
  Uname: Linux 4.4.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.05
  dmi.board.asset.tag: CZC242D8L4
  dmi.board.name: 339A
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC242D8L4
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.05:bd05/07/2012:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq Pro 6300 MT
  dmi.sys.vendor: Hewlett-Packard

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

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


[Desktop-packages] [Bug 1670630] ProcInterrupts.txt

2017-03-07 Thread Christophe Ségui
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1670630/+attachment/4832958/+files/ProcInterrupts.txt

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

Title:
  Multiple impression renders n^2 copies

Status in cups package in Ubuntu:
  New

Bug description:
  When trying to print with any application using gnome print backend 
(libreoffice,evince, ) and selecting multiple copies and collate assembly, 
the print actually prints n^2 copies (where n is the asked number).
  The problem exist with gnome shipped with Ubuntu 16.04. Does not happen with 
ubuntu 16.10 nor 14.

  this is not happening on kde environement on the same machine (or when
  using kde apps such as okular in gnome environment)

  lsb release :
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy ubuntu-gnome-desktop:
  ubuntu-gnome-desktop:
    Installé : 0.58.2
    Candidat : 0.58.2
   Table de version :
   *** 0.58.2 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.58 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-05-27 (283 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  KernLog: [945465.755265] audit: type=1400 audit(1488896787.907:33): 
apparmor="ALLOWED" operation="open" profile="/usr/sbin/sssd" 
name="/run/systemd/users/1396" pid=9279 comm="krb5_child" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  MachineType: Hewlett-Packard HP Compaq Pro 6300 MT
  Package: cups 2.1.3-4
  PackageArchitecture: amd64
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Tags:  xenial
  Uname: Linux 4.4.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.05
  dmi.board.asset.tag: CZC242D8L4
  dmi.board.name: 339A
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC242D8L4
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.05:bd05/07/2012:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq Pro 6300 MT
  dmi.sys.vendor: Hewlett-Packard

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

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


[Desktop-packages] [Bug 1670630] ProcCpuinfo.txt

2017-03-07 Thread Christophe Ségui
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1670630/+attachment/4832957/+files/ProcCpuinfo.txt

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

Title:
  Multiple impression renders n^2 copies

Status in cups package in Ubuntu:
  New

Bug description:
  When trying to print with any application using gnome print backend 
(libreoffice,evince, ) and selecting multiple copies and collate assembly, 
the print actually prints n^2 copies (where n is the asked number).
  The problem exist with gnome shipped with Ubuntu 16.04. Does not happen with 
ubuntu 16.10 nor 14.

  this is not happening on kde environement on the same machine (or when
  using kde apps such as okular in gnome environment)

  lsb release :
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy ubuntu-gnome-desktop:
  ubuntu-gnome-desktop:
    Installé : 0.58.2
    Candidat : 0.58.2
   Table de version :
   *** 0.58.2 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.58 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-05-27 (283 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  KernLog: [945465.755265] audit: type=1400 audit(1488896787.907:33): 
apparmor="ALLOWED" operation="open" profile="/usr/sbin/sssd" 
name="/run/systemd/users/1396" pid=9279 comm="krb5_child" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  MachineType: Hewlett-Packard HP Compaq Pro 6300 MT
  Package: cups 2.1.3-4
  PackageArchitecture: amd64
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Tags:  xenial
  Uname: Linux 4.4.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.05
  dmi.board.asset.tag: CZC242D8L4
  dmi.board.name: 339A
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC242D8L4
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.05:bd05/07/2012:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq Pro 6300 MT
  dmi.sys.vendor: Hewlett-Packard

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

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


[Desktop-packages] [Bug 1670630] Lpstat.txt

2017-03-07 Thread Christophe Ségui
apport information

** Attachment added: "Lpstat.txt"
   https://bugs.launchpad.net/bugs/1670630/+attachment/4832952/+files/Lpstat.txt

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

Title:
  Multiple impression renders n^2 copies

Status in cups package in Ubuntu:
  New

Bug description:
  When trying to print with any application using gnome print backend 
(libreoffice,evince, ) and selecting multiple copies and collate assembly, 
the print actually prints n^2 copies (where n is the asked number).
  The problem exist with gnome shipped with Ubuntu 16.04. Does not happen with 
ubuntu 16.10 nor 14.

  this is not happening on kde environement on the same machine (or when
  using kde apps such as okular in gnome environment)

  lsb release :
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy ubuntu-gnome-desktop:
  ubuntu-gnome-desktop:
    Installé : 0.58.2
    Candidat : 0.58.2
   Table de version :
   *** 0.58.2 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.58 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-05-27 (283 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  KernLog: [945465.755265] audit: type=1400 audit(1488896787.907:33): 
apparmor="ALLOWED" operation="open" profile="/usr/sbin/sssd" 
name="/run/systemd/users/1396" pid=9279 comm="krb5_child" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  MachineType: Hewlett-Packard HP Compaq Pro 6300 MT
  Package: cups 2.1.3-4
  PackageArchitecture: amd64
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Tags:  xenial
  Uname: Linux 4.4.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.05
  dmi.board.asset.tag: CZC242D8L4
  dmi.board.name: 339A
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC242D8L4
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.05:bd05/07/2012:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq Pro 6300 MT
  dmi.sys.vendor: Hewlett-Packard

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

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


[Desktop-packages] [Bug 1670630] Lspci.txt

2017-03-07 Thread Christophe Ségui
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1670630/+attachment/4832953/+files/Lspci.txt

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

Title:
  Multiple impression renders n^2 copies

Status in cups package in Ubuntu:
  New

Bug description:
  When trying to print with any application using gnome print backend 
(libreoffice,evince, ) and selecting multiple copies and collate assembly, 
the print actually prints n^2 copies (where n is the asked number).
  The problem exist with gnome shipped with Ubuntu 16.04. Does not happen with 
ubuntu 16.10 nor 14.

  this is not happening on kde environement on the same machine (or when
  using kde apps such as okular in gnome environment)

  lsb release :
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy ubuntu-gnome-desktop:
  ubuntu-gnome-desktop:
    Installé : 0.58.2
    Candidat : 0.58.2
   Table de version :
   *** 0.58.2 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.58 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-05-27 (283 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  KernLog: [945465.755265] audit: type=1400 audit(1488896787.907:33): 
apparmor="ALLOWED" operation="open" profile="/usr/sbin/sssd" 
name="/run/systemd/users/1396" pid=9279 comm="krb5_child" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  MachineType: Hewlett-Packard HP Compaq Pro 6300 MT
  Package: cups 2.1.3-4
  PackageArchitecture: amd64
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Tags:  xenial
  Uname: Linux 4.4.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.05
  dmi.board.asset.tag: CZC242D8L4
  dmi.board.name: 339A
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC242D8L4
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.05:bd05/07/2012:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq Pro 6300 MT
  dmi.sys.vendor: Hewlett-Packard

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

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


[Desktop-packages] [Bug 1670630] PrintingPackages.txt

2017-03-07 Thread Christophe Ségui
apport information

** Attachment added: "PrintingPackages.txt"
   
https://bugs.launchpad.net/bugs/1670630/+attachment/4832956/+files/PrintingPackages.txt

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

Title:
  Multiple impression renders n^2 copies

Status in cups package in Ubuntu:
  New

Bug description:
  When trying to print with any application using gnome print backend 
(libreoffice,evince, ) and selecting multiple copies and collate assembly, 
the print actually prints n^2 copies (where n is the asked number).
  The problem exist with gnome shipped with Ubuntu 16.04. Does not happen with 
ubuntu 16.10 nor 14.

  this is not happening on kde environement on the same machine (or when
  using kde apps such as okular in gnome environment)

  lsb release :
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy ubuntu-gnome-desktop:
  ubuntu-gnome-desktop:
    Installé : 0.58.2
    Candidat : 0.58.2
   Table de version :
   *** 0.58.2 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.58 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-05-27 (283 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  KernLog: [945465.755265] audit: type=1400 audit(1488896787.907:33): 
apparmor="ALLOWED" operation="open" profile="/usr/sbin/sssd" 
name="/run/systemd/users/1396" pid=9279 comm="krb5_child" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  MachineType: Hewlett-Packard HP Compaq Pro 6300 MT
  Package: cups 2.1.3-4
  PackageArchitecture: amd64
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Tags:  xenial
  Uname: Linux 4.4.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.05
  dmi.board.asset.tag: CZC242D8L4
  dmi.board.name: 339A
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC242D8L4
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.05:bd05/07/2012:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq Pro 6300 MT
  dmi.sys.vendor: Hewlett-Packard

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

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


[Desktop-packages] [Bug 1670630] Lsusb.txt

2017-03-07 Thread Christophe Ségui
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1670630/+attachment/4832954/+files/Lsusb.txt

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

Title:
  Multiple impression renders n^2 copies

Status in cups package in Ubuntu:
  New

Bug description:
  When trying to print with any application using gnome print backend 
(libreoffice,evince, ) and selecting multiple copies and collate assembly, 
the print actually prints n^2 copies (where n is the asked number).
  The problem exist with gnome shipped with Ubuntu 16.04. Does not happen with 
ubuntu 16.10 nor 14.

  this is not happening on kde environement on the same machine (or when
  using kde apps such as okular in gnome environment)

  lsb release :
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy ubuntu-gnome-desktop:
  ubuntu-gnome-desktop:
    Installé : 0.58.2
    Candidat : 0.58.2
   Table de version :
   *** 0.58.2 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.58 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-05-27 (283 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  KernLog: [945465.755265] audit: type=1400 audit(1488896787.907:33): 
apparmor="ALLOWED" operation="open" profile="/usr/sbin/sssd" 
name="/run/systemd/users/1396" pid=9279 comm="krb5_child" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  MachineType: Hewlett-Packard HP Compaq Pro 6300 MT
  Package: cups 2.1.3-4
  PackageArchitecture: amd64
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Tags:  xenial
  Uname: Linux 4.4.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.05
  dmi.board.asset.tag: CZC242D8L4
  dmi.board.name: 339A
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC242D8L4
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.05:bd05/07/2012:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq Pro 6300 MT
  dmi.sys.vendor: Hewlett-Packard

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

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


[Desktop-packages] [Bug 1670630] Locale.txt

2017-03-07 Thread Christophe Ségui
apport information

** Attachment added: "Locale.txt"
   https://bugs.launchpad.net/bugs/1670630/+attachment/4832951/+files/Locale.txt

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

Title:
  Multiple impression renders n^2 copies

Status in cups package in Ubuntu:
  New

Bug description:
  When trying to print with any application using gnome print backend 
(libreoffice,evince, ) and selecting multiple copies and collate assembly, 
the print actually prints n^2 copies (where n is the asked number).
  The problem exist with gnome shipped with Ubuntu 16.04. Does not happen with 
ubuntu 16.10 nor 14.

  this is not happening on kde environement on the same machine (or when
  using kde apps such as okular in gnome environment)

  lsb release :
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy ubuntu-gnome-desktop:
  ubuntu-gnome-desktop:
    Installé : 0.58.2
    Candidat : 0.58.2
   Table de version :
   *** 0.58.2 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.58 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-05-27 (283 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  KernLog: [945465.755265] audit: type=1400 audit(1488896787.907:33): 
apparmor="ALLOWED" operation="open" profile="/usr/sbin/sssd" 
name="/run/systemd/users/1396" pid=9279 comm="krb5_child" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  MachineType: Hewlett-Packard HP Compaq Pro 6300 MT
  Package: cups 2.1.3-4
  PackageArchitecture: amd64
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Tags:  xenial
  Uname: Linux 4.4.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.05
  dmi.board.asset.tag: CZC242D8L4
  dmi.board.name: 339A
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC242D8L4
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.05:bd05/07/2012:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq Pro 6300 MT
  dmi.sys.vendor: Hewlett-Packard

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

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


[Desktop-packages] [Bug 1670630] JournalErrors.txt

2017-03-07 Thread Christophe Ségui
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1670630/+attachment/4832950/+files/JournalErrors.txt

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

Title:
  Multiple impression renders n^2 copies

Status in cups package in Ubuntu:
  New

Bug description:
  When trying to print with any application using gnome print backend 
(libreoffice,evince, ) and selecting multiple copies and collate assembly, 
the print actually prints n^2 copies (where n is the asked number).
  The problem exist with gnome shipped with Ubuntu 16.04. Does not happen with 
ubuntu 16.10 nor 14.

  this is not happening on kde environement on the same machine (or when
  using kde apps such as okular in gnome environment)

  lsb release :
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy ubuntu-gnome-desktop:
  ubuntu-gnome-desktop:
    Installé : 0.58.2
    Candidat : 0.58.2
   Table de version :
   *** 0.58.2 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.58 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-05-27 (283 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  KernLog: [945465.755265] audit: type=1400 audit(1488896787.907:33): 
apparmor="ALLOWED" operation="open" profile="/usr/sbin/sssd" 
name="/run/systemd/users/1396" pid=9279 comm="krb5_child" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  MachineType: Hewlett-Packard HP Compaq Pro 6300 MT
  Package: cups 2.1.3-4
  PackageArchitecture: amd64
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Tags:  xenial
  Uname: Linux 4.4.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.05
  dmi.board.asset.tag: CZC242D8L4
  dmi.board.name: 339A
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC242D8L4
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.05:bd05/07/2012:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq Pro 6300 MT
  dmi.sys.vendor: Hewlett-Packard

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

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


[Desktop-packages] [Bug 1670630] Re: Multiple impression renders n^2 copies

2017-03-07 Thread Christophe Ségui
apport information

** Tags added: apport-collected

** Description changed:

  When trying to print with any application using gnome print backend 
(libreoffice,evince, ) and selecting multiple copies and collate assembly, 
the print actually prints n^2 copies (where n is the asked number).
  The problem exist with gnome shipped with Ubuntu 16.04. Does not happen with 
ubuntu 16.10 nor 14.
  
  this is not happening on kde environement on the same machine (or when
  using kde apps such as okular in gnome environment)
  
  lsb release :
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  
  apt-cache policy ubuntu-gnome-desktop:
  ubuntu-gnome-desktop:
    Installé : 0.58.2
    Candidat : 0.58.2
   Table de version :
   *** 0.58.2 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.58 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.5
+ Architecture: amd64
+ DistroRelease: Ubuntu 16.04
+ InstallationDate: Installed on 2016-05-27 (283 days ago)
+ InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
+ KernLog: [945465.755265] audit: type=1400 audit(1488896787.907:33): 
apparmor="ALLOWED" operation="open" profile="/usr/sbin/sssd" 
name="/run/systemd/users/1396" pid=9279 comm="krb5_child" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
+ MachineType: Hewlett-Packard HP Compaq Pro 6300 MT
+ Package: cups 2.1.3-4
+ PackageArchitecture: amd64
+ Papersize: a4
+ ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
+ Tags:  xenial
+ Uname: Linux 4.4.0-63-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 05/07/2012
+ dmi.bios.vendor: Hewlett-Packard
+ dmi.bios.version: K01 v02.05
+ dmi.board.asset.tag: CZC242D8L4
+ dmi.board.name: 339A
+ dmi.board.vendor: Hewlett-Packard
+ dmi.chassis.asset.tag: CZC242D8L4
+ dmi.chassis.type: 6
+ dmi.chassis.vendor: Hewlett-Packard
+ dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.05:bd05/07/2012:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
+ dmi.product.name: HP Compaq Pro 6300 MT
+ dmi.sys.vendor: Hewlett-Packard

** Attachment added: "CupsErrorLog.txt"
   
https://bugs.launchpad.net/bugs/1670630/+attachment/4832947/+files/CupsErrorLog.txt

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

Title:
  Multiple impression renders n^2 copies

Status in cups package in Ubuntu:
  New

Bug description:
  When trying to print with any application using gnome print backend 
(libreoffice,evince, ) and selecting multiple copies and collate assembly, 
the print actually prints n^2 copies (where n is the asked number).
  The problem exist with gnome shipped with Ubuntu 16.04. Does not happen with 
ubuntu 16.10 nor 14.

  this is not happening on kde environement on the same machine (or when
  using kde apps such as okular in gnome environment)

  lsb release :
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy ubuntu-gnome-desktop:
  ubuntu-gnome-desktop:
    Installé : 0.58.2
    Candidat : 0.58.2
   Table de version :
   *** 0.58.2 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.58 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-05-27 (283 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  KernLog: [945465.755265] audit: type=1400 audit(1488896787.907:33): 
apparmor="ALLOWED" operation="open" profile="/usr/sbin/sssd" 
name="/run/systemd/users/1396" pid=9279 comm="krb5_child" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  MachineType: Hewlett-Packard HP Compaq Pro 6300 MT
  Package: cups 2.1.3-4
  PackageArchitecture: amd64
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet 

[Desktop-packages] [Bug 1670630] CurrentDmesg.txt

2017-03-07 Thread Christophe Ségui
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1670630/+attachment/4832948/+files/CurrentDmesg.txt

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

Title:
  Multiple impression renders n^2 copies

Status in cups package in Ubuntu:
  New

Bug description:
  When trying to print with any application using gnome print backend 
(libreoffice,evince, ) and selecting multiple copies and collate assembly, 
the print actually prints n^2 copies (where n is the asked number).
  The problem exist with gnome shipped with Ubuntu 16.04. Does not happen with 
ubuntu 16.10 nor 14.

  this is not happening on kde environement on the same machine (or when
  using kde apps such as okular in gnome environment)

  lsb release :
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy ubuntu-gnome-desktop:
  ubuntu-gnome-desktop:
    Installé : 0.58.2
    Candidat : 0.58.2
   Table de version :
   *** 0.58.2 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.58 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-05-27 (283 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  KernLog: [945465.755265] audit: type=1400 audit(1488896787.907:33): 
apparmor="ALLOWED" operation="open" profile="/usr/sbin/sssd" 
name="/run/systemd/users/1396" pid=9279 comm="krb5_child" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  MachineType: Hewlett-Packard HP Compaq Pro 6300 MT
  Package: cups 2.1.3-4
  PackageArchitecture: amd64
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Tags:  xenial
  Uname: Linux 4.4.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.05
  dmi.board.asset.tag: CZC242D8L4
  dmi.board.name: 339A
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC242D8L4
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.05:bd05/07/2012:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq Pro 6300 MT
  dmi.sys.vendor: Hewlett-Packard

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

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


[Desktop-packages] [Bug 1670630] Dependencies.txt

2017-03-07 Thread Christophe Ségui
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1670630/+attachment/4832949/+files/Dependencies.txt

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

Title:
  Multiple impression renders n^2 copies

Status in cups package in Ubuntu:
  New

Bug description:
  When trying to print with any application using gnome print backend 
(libreoffice,evince, ) and selecting multiple copies and collate assembly, 
the print actually prints n^2 copies (where n is the asked number).
  The problem exist with gnome shipped with Ubuntu 16.04. Does not happen with 
ubuntu 16.10 nor 14.

  this is not happening on kde environement on the same machine (or when
  using kde apps such as okular in gnome environment)

  lsb release :
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy ubuntu-gnome-desktop:
  ubuntu-gnome-desktop:
    Installé : 0.58.2
    Candidat : 0.58.2
   Table de version :
   *** 0.58.2 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.58 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-05-27 (283 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  KernLog: [945465.755265] audit: type=1400 audit(1488896787.907:33): 
apparmor="ALLOWED" operation="open" profile="/usr/sbin/sssd" 
name="/run/systemd/users/1396" pid=9279 comm="krb5_child" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  MachineType: Hewlett-Packard HP Compaq Pro 6300 MT
  Package: cups 2.1.3-4
  PackageArchitecture: amd64
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=4c62a0aa-d21a-4531-8662-487158bf7463 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Tags:  xenial
  Uname: Linux 4.4.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.05
  dmi.board.asset.tag: CZC242D8L4
  dmi.board.name: 339A
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC242D8L4
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.05:bd05/07/2012:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq Pro 6300 MT
  dmi.sys.vendor: Hewlett-Packard

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

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


[Desktop-packages] [Bug 1670630] Re: Multiple impression renders n^2 copies

2017-03-07 Thread Christophe Ségui
** Also affects: cups (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Multiple impression renders n^2 copies

Status in cups package in Ubuntu:
  New

Bug description:
  When trying to print with any application using gnome print backend 
(libreoffice,evince, ) and selecting multiple copies and collate assembly, 
the print actually prints n^2 copies (where n is the asked number).
  The problem exist with gnome shipped with Ubuntu 16.04. Does not happen with 
ubuntu 16.10 nor 14.

  this is not happening on kde environement on the same machine (or when
  using kde apps such as okular in gnome environment)

  lsb release :
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy ubuntu-gnome-desktop:
  ubuntu-gnome-desktop:
    Installé : 0.58.2
    Candidat : 0.58.2
   Table de version :
   *** 0.58.2 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.58 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

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

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


[Desktop-packages] [Bug 1670630] Re: Multiple impression renders n^2 copies

2017-03-07 Thread Christophe Ségui
** Description changed:

- When trying to print with any application using gnome print backend 
(libreoffice,evince, ) and selecting multiple copies and collate assembly, 
the print actually prints n^2 copies (where n is the asked number). 
+ When trying to print with any application using gnome print backend 
(libreoffice,evince, ) and selecting multiple copies and collate assembly, 
the print actually prints n^2 copies (where n is the asked number).
  The problem exist with gnome shipped with Ubuntu 16.04. Does not happen with 
ubuntu 16.10 nor 14.
  
  this is not happening on kde environement on the same machine (or when
- using kde apps such as okular in gnome environment
+ using kde apps such as okular in gnome environment)
  
  lsb release :
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  
  apt-cache policy ubuntu-gnome-desktop:
  ubuntu-gnome-desktop:
-   Installé : 0.58.2
-   Candidat : 0.58.2
-  Table de version :
-  *** 0.58.2 500
- 500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
- 100 /var/lib/dpkg/status
-  0.58 500
- 500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
+   Installé : 0.58.2
+   Candidat : 0.58.2
+  Table de version :
+  *** 0.58.2 500
+ 500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
+ 100 /var/lib/dpkg/status
+  0.58 500
+ 500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

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

Title:
  Multiple impression renders n^2 copies

Status in cups package in Ubuntu:
  New

Bug description:
  When trying to print with any application using gnome print backend 
(libreoffice,evince, ) and selecting multiple copies and collate assembly, 
the print actually prints n^2 copies (where n is the asked number).
  The problem exist with gnome shipped with Ubuntu 16.04. Does not happen with 
ubuntu 16.10 nor 14.

  this is not happening on kde environement on the same machine (or when
  using kde apps such as okular in gnome environment)

  lsb release :
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy ubuntu-gnome-desktop:
  ubuntu-gnome-desktop:
    Installé : 0.58.2
    Candidat : 0.58.2
   Table de version :
   *** 0.58.2 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.58 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

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

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


[Desktop-packages] [Bug 1240336] Re: After release upgrade, the user looses permissions for several basic actions in the system

2017-03-03 Thread Christophe Gras
Got same issue after an upgrade from Ubuntu 14.04 to 16.04 and the
following actions solved the problem :

sudo pam-auth-update --force
sudo vi/etc/pam.d/lightdm

=> add following lines at the end : 
session required pam_loginuid.so
session required pam_systemd.so

sudo reboot

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

Title:
  After release upgrade, the user looses permissions for several basic
  actions in the system

Status in gdm package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged
Status in lxdm package in Ubuntu:
  Triaged
Status in policykit-desktop-privileges package in Ubuntu:
  Triaged

Bug description:
  HOW TO REPRODUCE:
  - Upgrade Ubuntu to the next release.

  RESULT:
  - The user looses permissions for several basic actions in the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: policykit-desktop-privileges 0.16
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:20:55 2013
  InstallationDate: Installed on 2013-10-09 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-desktop-privileges
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132

2016-12-02 Thread Jean Christophe André
Well… Switching to another window manager doesn't solve the “any 3D/GLX
app would crash” issue…

In my case I would have preferred to use the nouveau driver from the
beginning, except that for ancient cards like the 6150SE it makes the
whole system freeze after only a few minutes…

Finally, I was so p*ssed off about this bug and the fact that I have to
tune this or that after some security update, that I looked back into
this nouveau driver bug for 2 days and finally found a way to use it
without patching/installing anything or totally disabling all graphic
accelerations. (options nouveau config="PMPEG=0" => works for me/my
card)

So now that I have returned to The open and happy world and am not
concerned with this bug anymore. Goodluck everybody else! :-P

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Confirmed

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

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

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


[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132

2016-11-29 Thread Jean Christophe André
FYI, after a kernel upgrade the NVIDIA driver was unusable again. This
time was because of the DKMS mechanism which, for whatever reason I
didn't investigate yet (could it be because of the apt-pinning??),
didn't success to build and install the nvidia_304.ko module for the new
kernel.

If that happens to you, the solution is to run these commands:
 dpkg-reconfigure nvidia-304
 service lightdm restart (no need to reboot)

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Confirmed

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

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

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


[Desktop-packages] [Bug 1448179] Re: veth devices still appear in the applet

2016-11-16 Thread Christophe Meron
*** This bug is a duplicate of bug 1458322 ***
https://bugs.launchpad.net/bugs/1458322

** This bug has been marked a duplicate of bug 1458322
   NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

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

Title:
  veth devices still appear in the applet

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  vethXYZ devices as created by LXC shouldn't be managed or even
  displayed by Network Manager.

  They currently don't appear to be managed (good), but running a few
  hundred containers, having each of them take two lines in the network
  menu makes NM almost unusable.

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

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


[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132

2016-11-06 Thread Jean Christophe André
Sorry for the typos and long-lines… Can't find a way to edit back my
posts… :-/

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Confirmed

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

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

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


[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132

2016-11-06 Thread Jean Christophe André
In my case I have a GeForce 6150SE so I really need this 304.131 and
can't higher version like 340.xx.


For people needing to downgrade, this is one (among others) correct way to do 
so with Ubuntu 16.04:

- first create a file named /etc/apt/preferences.d/local-nvidia-quirks
with the following content:

Explanation: block this specifique update because of OpenGL problem with 304.132
Package: nvidia-304
Pin: version 304.132-0ubuntu0.16.04.2
Pin-Priority: -10

Explanation: block this specifique update because of OpenGL problem with 304.132
Package: nvidia-opencl-icd-304
Pin: version 304.132-0ubuntu0.16.04.2
Pin-Priority: -10

- then reinstall the working old packages (they are still available in
the repository):

sudo apt install nvidia-304=304.131-0ubuntu3 nvidia-opencl-
icd-304=304.131-0ubuntu3

- finally, reboot your computer (because it also affects the initrd boot
image)


The previous way only blocks the currently known not working version, without 
blocking future updates.

If you want a way to stay at the known working version without further
updates, here is the content you should use for your
/etc/apt/preferences.d/local-nvidia-quirks:

Explanation: do not use any other version than this one, ever (priority 1001 
will ensure that)
Package: nvidia-304
Pin: version 304.131-0ubuntu3
Pin-Priority: 1001

Explanation: do not use any other version than this one, ever (priority 1001 
will ensure that)
Package: nvidia-opencl-icd-304
Pin: version 304.131-0ubuntu3
Pin-Priority: 1001

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Confirmed

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

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

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


[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132

2016-11-05 Thread Jean Christophe André
Since this problem greatly affects usability (no graphic login anymore),
may be it's worth (in the users' point of view) creating a “fake
version” security-upgrade like "304.132-0ubuntu0.16.04.2+really304.131"
to fill the gap while waiting for Nvidia to provide a fix for 304.132,
IMHO.

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Unknown

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

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

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


[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132

2016-11-05 Thread Jean Christophe André
** Bug watch added: Debian Bug tracker #840342
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840342

** Also affects: nvidia-graphics-drivers-legacy-304xx (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840342
   Importance: Unknown
   Status: Unknown

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Unknown

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

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

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


[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132

2016-11-05 Thread Jean Christophe André
A debdiff between the packages shows the difference is mainly a version
upgrade from 304.131 to 304.132.

And it seems a lot of people are experiencing problems with version
304.132, cf
https://devtalk.nvidia.com/search/more/sitecommentsearch/304.132/

A specific thread retained my attention:
https://devtalk.nvidia.com/default/topic/968892/linux/geforce-7300le-
with-304-132-glxinfo-fails-now-with-quot-x-error-of-failed-request-
badvalue-quot-/

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

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

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


[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132

2016-11-05 Thread Jean Christophe André
FYI, downgrade “solved” the problem for me too.

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

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

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


[Desktop-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

2016-10-31 Thread Christophe Sauthier
Philippe, I am not really sure what you want to do with those
commands...

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [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)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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


[Desktop-packages] [Bug 1447345] Re: Support the unprivileged namespace sandbox

2016-09-20 Thread Jean Christophe André
Same here with Evince not being able to lauch the browser when you clic
on a link inside a PDF:

apparmor="DENIED" operation="capable"
profile="/usr/bin/evince//sanitized_helper" pid=16137 comm="chromium-
browse" capability=21  capname="sys_admin"

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

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

Title:
  Support the unprivileged namespace sandbox

Status in Oxide:
  Triaged
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in evince package in Ubuntu:
  New

Bug description:
  Chromium has a new layer 1 sandbox which replaces the suid sandbox on
  systems with CLONE_NEWUSER. However, it's currently incompatible with
  application confinement.

  To summarize, the sandbox mechanism does something like this:

  1) Browser launches zygote process:
- clones with CLONE_NEWUSER | CLONE_NEWPID | CLONE_NEWNET and then exec()

  2) Zygote initializes sandbox:
- unshare(CLONE_NEWUSER)
- clones a new process with CLONE_FS and then does waitpid(). The child 
chroots to /proc/self/fdinfo
- Enables CAP_SYS_ADMIN (see below)

  3) Zygote forks
- Parent becomes init
- Child continues as zygote

  4) Zygote waits for requests from the browser to create render
  processes

  5) On each request:
- Zygote clones a new process with CLONE_NEWPID (this is why it needs 
CAP_SYS_ADMIN)
- New process drops all privileges and becomes a renderer

  This produces the following denial on the device:

  type=1400 audit(1429733985.487:153): apparmor="DENIED"
  operation="capable"
  profile="com.zeptolab.cuttherope.full_cuttherope_0.5.2" pid=7195
  comm="qmlscene" capability=21 capname="sys_admin"

  The oxide_helper profile already allows sys_admin, but this is coming
  from the browser process, just here:

  7229  clone(child_stack=0, flags=CLONE_NEWUSER|SIGCHLD) = 7246 <-- Test that 
the new sandbox can be used
  7246  exit_group(0) = ?
  7229  wait4(7246,  
  7246  +++ exited with 0 +++
  7229  <... wait4 resumed> [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 
7246
  7229  --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=7246, 
si_status=0, si_utime=0, si_stime=0} ---
  7229  write(13, "\0", 1)= 1
  7229  rt_sigreturn()= 7246
  7229  access("/proc/self/ns/user", F_OK) = 0
  7229  access("/proc/self/ns/user", F_OK) = 0
  7229  access("/proc/self/ns/pid", F_OK) = 0
  7229  access("/proc/self/ns/user", F_OK) = 0
  7229  access("/proc/self/ns/net", F_OK) = 0
  7229  getuid32()= 32011
  7229  getgid32()= 32011
  7229  access("/proc/self/setgroups", F_OK) = -1 ENOENT (No such file or 
directory)
  7229  rt_sigprocmask(SIG_SETMASK, ~[RTMIN RT_1], [], 8) = 0
  7229  clone(child_stack=0xbe8518d4, 
flags=CLONE_NEWUSER|CLONE_NEWPID|CLONE_NEWNET|SIGCHLD) = -1 EPERM (Operation 
not permitted)

  It fails in step 1) above, because it needs CAP_SYS_ADMIN before it's
  able to transition to the oxide_helper profile (which allows it)

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

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


[Desktop-packages] [Bug 1611079] [NEW] package libatspi2.0-0:amd64 2.18.3-4ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting co

2016-08-08 Thread Christophe BRETON
Public bug reported:

no detail...

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libatspi2.0-0:amd64 2.18.3-4ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36
Uname: Linux 3.13.0-85-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Mon Aug  8 19:50:07 2016
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: at-spi2-core
Title: package libatspi2.0-0:amd64 2.18.3-4ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: at-spi2-core (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 at-spi2-core in Ubuntu.
https://bugs.launchpad.net/bugs/1611079

Title:
  package libatspi2.0-0:amd64 2.18.3-4ubuntu1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in at-spi2-core package in Ubuntu:
  New

Bug description:
  no detail...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libatspi2.0-0:amd64 2.18.3-4ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36
  Uname: Linux 3.13.0-85-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Aug  8 19:50:07 2016
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: at-spi2-core
  Title: package libatspi2.0-0:amd64 2.18.3-4ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1611079/+subscriptions

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


[Desktop-packages] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity

2016-07-18 Thread Christophe
Another thing I just noticed : with or without the patch, the only thing
that works with two screen is the extended mode. When I try to go from
two screen extended to two screen clone mode, both screens switch off
and cannot be switched back on.

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

Title:
  screen cannot be turned back on after being switched off after some
  time of inactivity

Status in xserver-xorg-video-ati package in Ubuntu:
  Triaged

Bug description:
  I did a fresh install of ubuntu 16.04 on my old dell computer in which
  there is an ati radeon X1300 graphics card.

   Whenever the screen turns off due to inactivity, it cannot be woken
  up by moving the mouse or by hitting a key.

  When I kill the Xorg process via ssh with another computer, the screen
  then comes to life again and I can log back in.

  When I remove the graphic card from the computer and use the built in
  graphic card instead, the bug doesn't occur. So I guess it is related
  to the radeon driver.

  Oddly enough, there is no problem waking the screen when I type "xset 
-display :0.0 dpms force off" in a terminal. Moreover typing 
gnome-screensaver-command -a in a terminal turns my screen off and after typing 
this line, the screen can be woken up by moving the mouse or by hitting a key. 
I'm confused.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7183] (prog-if 00 [VGA controller])
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] [1028:0302]
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] (Secondary) [1028:0303]
  InstallationDate: Installed on 2016-04-23 (71 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Dell DM061
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=d8d495da-2071-481b-8e28-497d8eca9aff ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0WG864
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd05/24/2007:svnDellInc.:pnDellDM061:pvr:rvnDellInc.:rn0WG864:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: Dell DM061
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions

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


[Desktop-packages] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity

2016-07-18 Thread Christophe
In the next comment, you will findthe output of xrandr --verbose, when both 
monitors are enabled, with the original (non patched) drivers.
I must say that the patch you posted in comment #47 works perfectly when it 
comes to wake the monitor after some time of sleep. Only the problem of black 
screens when switching from one to two screens enabled remains.

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

Title:
  screen cannot be turned back on after being switched off after some
  time of inactivity

Status in xserver-xorg-video-ati package in Ubuntu:
  Triaged

Bug description:
  I did a fresh install of ubuntu 16.04 on my old dell computer in which
  there is an ati radeon X1300 graphics card.

   Whenever the screen turns off due to inactivity, it cannot be woken
  up by moving the mouse or by hitting a key.

  When I kill the Xorg process via ssh with another computer, the screen
  then comes to life again and I can log back in.

  When I remove the graphic card from the computer and use the built in
  graphic card instead, the bug doesn't occur. So I guess it is related
  to the radeon driver.

  Oddly enough, there is no problem waking the screen when I type "xset 
-display :0.0 dpms force off" in a terminal. Moreover typing 
gnome-screensaver-command -a in a terminal turns my screen off and after typing 
this line, the screen can be woken up by moving the mouse or by hitting a key. 
I'm confused.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7183] (prog-if 00 [VGA controller])
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] [1028:0302]
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] (Secondary) [1028:0303]
  InstallationDate: Installed on 2016-04-23 (71 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Dell DM061
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=d8d495da-2071-481b-8e28-497d8eca9aff ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0WG864
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd05/24/2007:svnDellInc.:pnDellDM061:pvr:rvnDellInc.:rn0WG864:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: Dell DM061
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions

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


[Desktop-packages] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity

2016-07-18 Thread Christophe
** Attachment added: "Xrandr output"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+attachment/4702793/+files/xrandr

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

Title:
  screen cannot be turned back on after being switched off after some
  time of inactivity

Status in xserver-xorg-video-ati package in Ubuntu:
  Triaged

Bug description:
  I did a fresh install of ubuntu 16.04 on my old dell computer in which
  there is an ati radeon X1300 graphics card.

   Whenever the screen turns off due to inactivity, it cannot be woken
  up by moving the mouse or by hitting a key.

  When I kill the Xorg process via ssh with another computer, the screen
  then comes to life again and I can log back in.

  When I remove the graphic card from the computer and use the built in
  graphic card instead, the bug doesn't occur. So I guess it is related
  to the radeon driver.

  Oddly enough, there is no problem waking the screen when I type "xset 
-display :0.0 dpms force off" in a terminal. Moreover typing 
gnome-screensaver-command -a in a terminal turns my screen off and after typing 
this line, the screen can be woken up by moving the mouse or by hitting a key. 
I'm confused.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7183] (prog-if 00 [VGA controller])
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] [1028:0302]
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] (Secondary) [1028:0303]
  InstallationDate: Installed on 2016-04-23 (71 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Dell DM061
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=d8d495da-2071-481b-8e28-497d8eca9aff ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0WG864
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd05/24/2007:svnDellInc.:pnDellDM061:pvr:rvnDellInc.:rn0WG864:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: Dell DM061
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions

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


[Desktop-packages] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity

2016-07-06 Thread Christophe
Same problem with this patch. Well in fact, it's even worse as I got a
kernel panic when trying to switch from 2 screens to only one (see
picture attached).

I attached the output of xrandr before and after the black screen (but
before the complete crash).

The black screen when changing between one and two monitors also appears
without the patch.

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

Title:
  screen cannot be turned back on after being switched off after some
  time of inactivity

Status in xserver-xorg-video-ati package in Ubuntu:
  Triaged

Bug description:
  I did a fresh install of ubuntu 16.04 on my old dell computer in which
  there is an ati radeon X1300 graphics card.

   Whenever the screen turns off due to inactivity, it cannot be woken
  up by moving the mouse or by hitting a key.

  When I kill the Xorg process via ssh with another computer, the screen
  then comes to life again and I can log back in.

  When I remove the graphic card from the computer and use the built in
  graphic card instead, the bug doesn't occur. So I guess it is related
  to the radeon driver.

  Oddly enough, there is no problem waking the screen when I type "xset 
-display :0.0 dpms force off" in a terminal. Moreover typing 
gnome-screensaver-command -a in a terminal turns my screen off and after typing 
this line, the screen can be woken up by moving the mouse or by hitting a key. 
I'm confused.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7183] (prog-if 00 [VGA controller])
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] [1028:0302]
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] (Secondary) [1028:0303]
  InstallationDate: Installed on 2016-04-23 (71 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Dell DM061
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=d8d495da-2071-481b-8e28-497d8eca9aff ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0WG864
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd05/24/2007:svnDellInc.:pnDellDM061:pvr:rvnDellInc.:rn0WG864:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: Dell DM061
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions

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


[Desktop-packages] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity

2016-07-06 Thread Christophe
** Attachment added: "black_screen.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+attachment/4696354/+files/black_screen.txt

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

Title:
  screen cannot be turned back on after being switched off after some
  time of inactivity

Status in xserver-xorg-video-ati package in Ubuntu:
  Triaged

Bug description:
  I did a fresh install of ubuntu 16.04 on my old dell computer in which
  there is an ati radeon X1300 graphics card.

   Whenever the screen turns off due to inactivity, it cannot be woken
  up by moving the mouse or by hitting a key.

  When I kill the Xorg process via ssh with another computer, the screen
  then comes to life again and I can log back in.

  When I remove the graphic card from the computer and use the built in
  graphic card instead, the bug doesn't occur. So I guess it is related
  to the radeon driver.

  Oddly enough, there is no problem waking the screen when I type "xset 
-display :0.0 dpms force off" in a terminal. Moreover typing 
gnome-screensaver-command -a in a terminal turns my screen off and after typing 
this line, the screen can be woken up by moving the mouse or by hitting a key. 
I'm confused.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7183] (prog-if 00 [VGA controller])
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] [1028:0302]
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] (Secondary) [1028:0303]
  InstallationDate: Installed on 2016-04-23 (71 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Dell DM061
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=d8d495da-2071-481b-8e28-497d8eca9aff ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0WG864
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd05/24/2007:svnDellInc.:pnDellDM061:pvr:rvnDellInc.:rn0WG864:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: Dell DM061
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions

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


[Desktop-packages] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity

2016-07-06 Thread Christophe
I must add that without the patch, after the black screen and the ctrl-alt-F1 
then ctrl-alt-F7, I had a dialog box saying : "Impossible de restaurer la 
configuration de l'affichage
could not set the configuration for CRTC 80".

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

Title:
  screen cannot be turned back on after being switched off after some
  time of inactivity

Status in xserver-xorg-video-ati package in Ubuntu:
  Triaged

Bug description:
  I did a fresh install of ubuntu 16.04 on my old dell computer in which
  there is an ati radeon X1300 graphics card.

   Whenever the screen turns off due to inactivity, it cannot be woken
  up by moving the mouse or by hitting a key.

  When I kill the Xorg process via ssh with another computer, the screen
  then comes to life again and I can log back in.

  When I remove the graphic card from the computer and use the built in
  graphic card instead, the bug doesn't occur. So I guess it is related
  to the radeon driver.

  Oddly enough, there is no problem waking the screen when I type "xset 
-display :0.0 dpms force off" in a terminal. Moreover typing 
gnome-screensaver-command -a in a terminal turns my screen off and after typing 
this line, the screen can be woken up by moving the mouse or by hitting a key. 
I'm confused.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7183] (prog-if 00 [VGA controller])
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] [1028:0302]
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] (Secondary) [1028:0303]
  InstallationDate: Installed on 2016-04-23 (71 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Dell DM061
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=d8d495da-2071-481b-8e28-497d8eca9aff ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0WG864
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd05/24/2007:svnDellInc.:pnDellDM061:pvr:rvnDellInc.:rn0WG864:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: Dell DM061
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions

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


[Desktop-packages] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity

2016-07-06 Thread Christophe
** Attachment added: "20160706_120743.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+attachment/4696357/+files/20160706_120743.jpg

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

Title:
  screen cannot be turned back on after being switched off after some
  time of inactivity

Status in xserver-xorg-video-ati package in Ubuntu:
  Triaged

Bug description:
  I did a fresh install of ubuntu 16.04 on my old dell computer in which
  there is an ati radeon X1300 graphics card.

   Whenever the screen turns off due to inactivity, it cannot be woken
  up by moving the mouse or by hitting a key.

  When I kill the Xorg process via ssh with another computer, the screen
  then comes to life again and I can log back in.

  When I remove the graphic card from the computer and use the built in
  graphic card instead, the bug doesn't occur. So I guess it is related
  to the radeon driver.

  Oddly enough, there is no problem waking the screen when I type "xset 
-display :0.0 dpms force off" in a terminal. Moreover typing 
gnome-screensaver-command -a in a terminal turns my screen off and after typing 
this line, the screen can be woken up by moving the mouse or by hitting a key. 
I'm confused.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7183] (prog-if 00 [VGA controller])
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] [1028:0302]
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] (Secondary) [1028:0303]
  InstallationDate: Installed on 2016-04-23 (71 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Dell DM061
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=d8d495da-2071-481b-8e28-497d8eca9aff ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0WG864
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd05/24/2007:svnDellInc.:pnDellDM061:pvr:rvnDellInc.:rn0WG864:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: Dell DM061
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions

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


[Desktop-packages] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity

2016-07-06 Thread Christophe
** Attachment added: "before_black_screen.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+attachment/4696355/+files/before_black_screen.txt

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

Title:
  screen cannot be turned back on after being switched off after some
  time of inactivity

Status in xserver-xorg-video-ati package in Ubuntu:
  Triaged

Bug description:
  I did a fresh install of ubuntu 16.04 on my old dell computer in which
  there is an ati radeon X1300 graphics card.

   Whenever the screen turns off due to inactivity, it cannot be woken
  up by moving the mouse or by hitting a key.

  When I kill the Xorg process via ssh with another computer, the screen
  then comes to life again and I can log back in.

  When I remove the graphic card from the computer and use the built in
  graphic card instead, the bug doesn't occur. So I guess it is related
  to the radeon driver.

  Oddly enough, there is no problem waking the screen when I type "xset 
-display :0.0 dpms force off" in a terminal. Moreover typing 
gnome-screensaver-command -a in a terminal turns my screen off and after typing 
this line, the screen can be woken up by moving the mouse or by hitting a key. 
I'm confused.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7183] (prog-if 00 [VGA controller])
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] [1028:0302]
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] (Secondary) [1028:0303]
  InstallationDate: Installed on 2016-04-23 (71 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Dell DM061
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=d8d495da-2071-481b-8e28-497d8eca9aff ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0WG864
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd05/24/2007:svnDellInc.:pnDellDM061:pvr:rvnDellInc.:rn0WG864:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: Dell DM061
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+subscriptions

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


[Desktop-packages] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity

2016-07-05 Thread Christophe
Michel, this patch seems to work quite well, but still showing some strange 
behaviour. To sum up, with the new patch :
- with one or two screens used, when the screens goes off after some time of 
inactivity, they can be woken up by moving the mouse.
- when two screens are used, from time to time, the screen connected via the 
VGA port of the graphics card does not goes off. (Its light dims, the screen 
goes black and then shows the login page again, the dvi-connected screen 
staying off until I move the mouse). With only one screen used (the dvi one), 
this behaviour does not appear until now.
- Using the ubuntu screen selector, from time to time, when I change from two 
screens to one screen, the screen goes black only showing the mouse arrow. I 
have to go to tty1 then press ctrl alt f7 to see the normal screen again. Once, 
doing this, even the keyboard and the mouse stopped responding.
- During the make process of the driver (with the patch), I still get the same 
warning : 
radeon_drm_queue.c: In function ‘radeon_drm_queue_alloc’:
radeon_drm_queue.c:95:9: warning: return makes integer from pointer without a 
cast [-Wint-conversion]
  return NULL;

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

Title:
  screen cannot be turned back on after being switched off after some
  time of inactivity

Status in xserver-xorg-video-ati package in Ubuntu:
  Triaged

Bug description:
  I did a fresh install of ubuntu 16.04 on my old dell computer in which
  there is an ati radeon X1300 graphics card.

   Whenever the screen turns off due to inactivity, it cannot be woken
  up by moving the mouse or by hitting a key.

  When I kill the Xorg process via ssh with another computer, the screen
  then comes to life again and I can log back in.

  When I remove the graphic card from the computer and use the built in
  graphic card instead, the bug doesn't occur. So I guess it is related
  to the radeon driver.

  Oddly enough, there is no problem waking the screen when I type "xset 
-display :0.0 dpms force off" in a terminal. Moreover typing 
gnome-screensaver-command -a in a terminal turns my screen off and after typing 
this line, the screen can be woken up by moving the mouse or by hitting a key. 
I'm confused.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7183] (prog-if 00 [VGA controller])
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] [1028:0302]
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] (Secondary) [1028:0303]
  InstallationDate: Installed on 2016-04-23 (71 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Dell DM061
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=d8d495da-2071-481b-8e28-497d8eca9aff ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0WG864
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd05/24/2007:svnDellInc.:pnDellDM061:pvr:rvnDellInc.:rn0WG864:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: Dell DM061
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: 

[Desktop-packages] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity

2016-07-04 Thread Christophe
It's a DELL Dimension E520. Is that the full computer model ?

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

Title:
  screen cannot be turned back on after being switched off after some
  time of inactivity

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I did a fresh install of ubuntu 16.04 on my old dell computer in which
  there is an ati radeon X1300 graphics card.

   Whenever the screen turns off due to inactivity, it cannot be woken
  up by moving the mouse or by hitting a key.

  When I kill the Xorg process via ssh with another computer, the screen
  then comes to life again and I can log back in.

  When I remove the graphic card from the computer and use the built in
  graphic card instead, the bug doesn't occur. So I guess it is related
  to the radeon driver.

  Oddly enough, there is no problem waking the screen when I type "xset 
-display :0.0 dpms force off" in a terminal. Moreover typing 
gnome-screensaver-command -a in a terminal turns my screen off and after typing 
this line, the screen can be woken up by moving the mouse or by hitting a key. 
I'm confused.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7183] (prog-if 00 [VGA controller])
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] [1028:0302]
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] (Secondary) [1028:0303]
  InstallationDate: Installed on 2016-04-23 (71 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Dell DM061
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=d8d495da-2071-481b-8e28-497d8eca9aff ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0WG864
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd05/24/2007:svnDellInc.:pnDellDM061:pvr:rvnDellInc.:rn0WG864:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: Dell DM061
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


[Desktop-packages] [Bug 1577170] CurrentDmesg.txt

2016-07-04 Thread Christophe
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1577170/+attachment/4695144/+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/1577170

Title:
  screen cannot be turned back on after being switched off after some
  time of inactivity

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I did a fresh install of ubuntu 16.04 on my old dell computer in which
  there is an ati radeon X1300 graphics card.

   Whenever the screen turns off due to inactivity, it cannot be woken
  up by moving the mouse or by hitting a key.

  When I kill the Xorg process via ssh with another computer, the screen
  then comes to life again and I can log back in.

  When I remove the graphic card from the computer and use the built in
  graphic card instead, the bug doesn't occur. So I guess it is related
  to the radeon driver.

  Oddly enough, there is no problem waking the screen when I type "xset 
-display :0.0 dpms force off" in a terminal. Moreover typing 
gnome-screensaver-command -a in a terminal turns my screen off and after typing 
this line, the screen can be woken up by moving the mouse or by hitting a key. 
I'm confused.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7183] (prog-if 00 [VGA controller])
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] [1028:0302]
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] (Secondary) [1028:0303]
  InstallationDate: Installed on 2016-04-23 (71 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Dell DM061
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=d8d495da-2071-481b-8e28-497d8eca9aff ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0WG864
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd05/24/2007:svnDellInc.:pnDellDM061:pvr:rvnDellInc.:rn0WG864:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: Dell DM061
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


[Desktop-packages] [Bug 1577170] UnitySupportTest.txt

2016-07-04 Thread Christophe
apport information

** Attachment added: "UnitySupportTest.txt"
   
https://bugs.launchpad.net/bugs/1577170/+attachment/4695157/+files/UnitySupportTest.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/1577170

Title:
  screen cannot be turned back on after being switched off after some
  time of inactivity

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I did a fresh install of ubuntu 16.04 on my old dell computer in which
  there is an ati radeon X1300 graphics card.

   Whenever the screen turns off due to inactivity, it cannot be woken
  up by moving the mouse or by hitting a key.

  When I kill the Xorg process via ssh with another computer, the screen
  then comes to life again and I can log back in.

  When I remove the graphic card from the computer and use the built in
  graphic card instead, the bug doesn't occur. So I guess it is related
  to the radeon driver.

  Oddly enough, there is no problem waking the screen when I type "xset 
-display :0.0 dpms force off" in a terminal. Moreover typing 
gnome-screensaver-command -a in a terminal turns my screen off and after typing 
this line, the screen can be woken up by moving the mouse or by hitting a key. 
I'm confused.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7183] (prog-if 00 [VGA controller])
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] [1028:0302]
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] (Secondary) [1028:0303]
  InstallationDate: Installed on 2016-04-23 (71 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Dell DM061
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=d8d495da-2071-481b-8e28-497d8eca9aff ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0WG864
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd05/24/2007:svnDellInc.:pnDellDM061:pvr:rvnDellInc.:rn0WG864:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: Dell DM061
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


[Desktop-packages] [Bug 1577170] UdevDb.txt

2016-07-04 Thread Christophe
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1577170/+attachment/4695156/+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/1577170

Title:
  screen cannot be turned back on after being switched off after some
  time of inactivity

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I did a fresh install of ubuntu 16.04 on my old dell computer in which
  there is an ati radeon X1300 graphics card.

   Whenever the screen turns off due to inactivity, it cannot be woken
  up by moving the mouse or by hitting a key.

  When I kill the Xorg process via ssh with another computer, the screen
  then comes to life again and I can log back in.

  When I remove the graphic card from the computer and use the built in
  graphic card instead, the bug doesn't occur. So I guess it is related
  to the radeon driver.

  Oddly enough, there is no problem waking the screen when I type "xset 
-display :0.0 dpms force off" in a terminal. Moreover typing 
gnome-screensaver-command -a in a terminal turns my screen off and after typing 
this line, the screen can be woken up by moving the mouse or by hitting a key. 
I'm confused.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7183] (prog-if 00 [VGA controller])
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] [1028:0302]
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] (Secondary) [1028:0303]
  InstallationDate: Installed on 2016-04-23 (71 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Dell DM061
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=d8d495da-2071-481b-8e28-497d8eca9aff ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0WG864
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd05/24/2007:svnDellInc.:pnDellDM061:pvr:rvnDellInc.:rn0WG864:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: Dell DM061
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


  1   2   3   >