[Desktop-packages] [Bug 1697229] Re: GNOME extensions deactivated after lock unlock

2017-06-10 Thread Francewhoa
After I created that ticket #1697229 I realized that this launchpad seems to be 
for Ubuntu. Since gnome-session is primarily maintain by bugs.debian.org it 
seems more appropriate to create this ticket with bugs.debian.org?
I created a ticket at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864592

Feel really free to use either ticket or both

** Bug watch added: Debian Bug tracker #864592
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864592

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

Title:
  GNOME extensions deactivated after lock unlock

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Summary:
  Lock then unlock GNOME session result in all GNOME extensions to be 
deactivated. Intermittent bug.

  Steps to reproduce:
  1. Install fresh Debian 8.8 Jessie

  2. Using https://extensions.gnome.org install and activate all the following 
extensions:
  • https://extensions.gnome.org/extension/310/alt-tab-workspace/
  alt-tab-worksp...@kwalo.net (version 10.0)

  • https://extensions.gnome.org/extension/484/workspace-grid/
  workspace-g...@mathematical.coffee.gmail.com (version 18.0)

  • https://extensions.gnome.org/extension/495/topicons/
  topIcons@adel.gadl...@gmail.com (version 29.0)

  • https://extensions.gnome.org/extension/672/disable-screen-shield/
  disable-screenshi...@lgpasquale.com (version 7.0)

  • https://extensions.gnome.org/extension/425/project-hamster-extension/
  hams...@projecthamster.wordpress.com (version 26.0)

  • https://extensions.gnome.org/extension/1082/cpufreq/
  cpufreq@konkor (version 12.0)

  3. Lock GNOME session

  4. Unlock GNOME session. Notice that all extensions are now
  deactivated :( Expected result is that they should remaining activated
  per their configuration.

  5. Using "Tweak Tool"/"gnome-tweak-tool" re-activate all those
  extensions. Restart GNOME by pressing "ALT-F2" keys, type "r", press
  "Enter" key. The extensions are now working.

  6. Lock GNOME session again

  7. Unlock GNOME session again. Issue is reproduced again. All extensions are 
deactivated. This bug is intermittent though. It depends on various factors, 
including but not limited:
  • Which extensions are activated
  • Your personal configuration with "gnome-tweak-tool" and "gnome-session" 
packages

  8. This issue can also be reproduce with rebooting, instead of lock
  and unlock the session. Same steps to reproduce as above. But simply
  reboot.

  Using
  • Base system: Debian 8.8 Jessie, 64-bit
  • Gnome: 3.14.1
  • gnome-tweak-tool: 3.14.2-2
  • gnome-session: 3.14.0-2
  • gnome-session-bin: 3.14.0-2
  • gnome-session-common: 3.14.0-2
  • Kernel: 4.9.0-0.bpo.3-amd64 #1 SMP Debian 4.9.25-1~bpo8+1 (2017-05-19) 
x86_64 GNU/Linux

  Notes:
  This bug was fixed in the package gnome-session - 3.9.90-0ubuntu16.1 with 
that ticket comment #15 at 
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1385572/comments/15
  So that ticket #1385572 is closed. But somehow this bug is back and reported 
by others in tickets #1236749 and #1385572. Maybe a regression? Maybe a 
zombie-bug, LOL ;) Anyhow I'm reopening this bug with this new ticket #1697229.

  I would be happy to contribute testing

  Here is another related ticket which includes some temporary fixes, such as:
  # 12 at 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1236749/comments/12
  # 57 at 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1236749/comments/57

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

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


[Desktop-packages] [Bug 1697240] [NEW] package libreoffice-common (not installed) failed to install/upgrade: intentando sobreescribir `/usr/bin/soffice', que está también en el paquete openoffice-debi

2017-06-10 Thread manuel flores
Public bug reported:

antes instale openoficce

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libreoffice-common (not installed)
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Sat Jun 10 23:55:20 2017
ErrorMessage: intentando sobreescribir `/usr/bin/soffice', que está también en 
el paquete openoffice-debian-menus 4.1.3-9783
InstallationDate: Installed on 2017-05-30 (11 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: libreoffice
Title: package libreoffice-common (not installed) failed to install/upgrade: 
intentando sobreescribir `/usr/bin/soffice', que está también en el paquete 
openoffice-debian-menus 4.1.3-9783
UpgradeStatus: Upgraded to zesty on 2017-05-30 (11 days ago)

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


** Tags: amd64 apport-package zesty

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

Title:
  package libreoffice-common (not installed) failed to install/upgrade:
  intentando sobreescribir `/usr/bin/soffice', que está también en el
  paquete openoffice-debian-menus 4.1.3-9783

Status in libreoffice package in Ubuntu:
  New

Bug description:
  antes instale openoficce

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libreoffice-common (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Sat Jun 10 23:55:20 2017
  ErrorMessage: intentando sobreescribir `/usr/bin/soffice', que está también 
en el paquete openoffice-debian-menus 4.1.3-9783
  InstallationDate: Installed on 2017-05-30 (11 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: libreoffice
  Title: package libreoffice-common (not installed) failed to install/upgrade: 
intentando sobreescribir `/usr/bin/soffice', que está también en el paquete 
openoffice-debian-menus 4.1.3-9783
  UpgradeStatus: Upgraded to zesty on 2017-05-30 (11 days ago)

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

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


[Desktop-packages] [Bug 1697229] Re: GNOME extensions deactivated after lock unlock

2017-06-10 Thread Francewhoa
** Description changed:

  Summary:
  Lock then unlock GNOME session result in all GNOME extensions to be 
deactivated. Intermittent bug.
  
  Steps to reproduce:
  1. Install fresh Debian 8.8 Jessie
  
  2. Using https://extensions.gnome.org install and active all the following 
extensions:
  • https://extensions.gnome.org/extension/310/alt-tab-workspace/
  alt-tab-worksp...@kwalo.net (version 10.0)
  
  • https://extensions.gnome.org/extension/484/workspace-grid/
  workspace-g...@mathematical.coffee.gmail.com (version 18.0)
  
  • https://extensions.gnome.org/extension/495/topicons/
  topIcons@adel.gadl...@gmail.com (version 29.0)
  
  • https://extensions.gnome.org/extension/672/disable-screen-shield/
  disable-screenshi...@lgpasquale.com (version 7.0)
  
  • https://extensions.gnome.org/extension/425/project-hamster-extension/
  hams...@projecthamster.wordpress.com (version 26.0)
  
  • https://extensions.gnome.org/extension/1082/cpufreq/
  cpufreq@konkor (version 12.0)
  
  3. Lock GNOME session
  
  4. Unlock GNOME session. Notice that all extensions are now deactivated
  :( Expected result is that they should remaining activated per their
  configuration.
  
  5. Using "Tweak Tool"/"gnome-tweak-tool" re-activate all those
  extensions. Restart GNOME by pressing "ALT-F2" keys, type "r", press
  "Enter" key. The extensions are now working.
  
  6. Lock GNOME session again
  
  7. Unlock GNOME session again. Issue is reproduced again. All extensions are 
deactivated. This bug is intermittent though. It depends on various factors, 
including but not limited:
  • Which extensions are activated
  • Your personal configuration with "gnome-tweak-tool" and "gnome-session" 
packages
  
  8. This issue can also be reproduce with rebooting, instead of lock and
  unlock the session. Same steps to reproduce as above. But simply reboot.
  
  Using
  • Base system: Debian 8.8 Jessie, 64-bit
  • Gnome: 3.14.1
  • gnome-tweak-tool: 3.14.2-2
  • gnome-session: 3.14.0-2
  • gnome-session-bin: 3.14.0-2
  • gnome-session-common: 3.14.0-2
  • Kernel: 4.9.0-0.bpo.3-amd64 #1 SMP Debian 4.9.25-1~bpo8+1 (2017-05-19) 
x86_64 GNU/Linux
  
  Notes:
- This bug was fixed in the package gnome-session - 3.9.90-0ubuntu16.1 with 
that ticket at  
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1385572
- That ticket #1385572 is closed, but this bug is back. Maybe a regression? 
Anyhow I'm reopening this bug with this new ticket #1697229.
+ This bug was fixed in the package gnome-session - 3.9.90-0ubuntu16.1 with 
that ticket comment #15 at 
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1385572/comments/15
+ So that ticket #1385572 is closed. But somehow this bug is back and reported 
by others in #1236749 and #1385572. Maybe a regression? Maybe a zombie-bug, LOL 
;) Anyhow I'm reopening this bug with this new ticket #1697229.
  
  Here is another related ticket which includes some temporary fixes, such as:
  # 12 at 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1236749/comments/12
  # 57 at 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1236749/comments/57

** Description changed:

  Summary:
  Lock then unlock GNOME session result in all GNOME extensions to be 
deactivated. Intermittent bug.
  
  Steps to reproduce:
  1. Install fresh Debian 8.8 Jessie
  
- 2. Using https://extensions.gnome.org install and active all the following 
extensions:
+ 2. Using https://extensions.gnome.org install and activate all the following 
extensions:
  • https://extensions.gnome.org/extension/310/alt-tab-workspace/
  alt-tab-worksp...@kwalo.net (version 10.0)
  
  • https://extensions.gnome.org/extension/484/workspace-grid/
  workspace-g...@mathematical.coffee.gmail.com (version 18.0)
  
  • https://extensions.gnome.org/extension/495/topicons/
  topIcons@adel.gadl...@gmail.com (version 29.0)
  
  • https://extensions.gnome.org/extension/672/disable-screen-shield/
  disable-screenshi...@lgpasquale.com (version 7.0)
  
  • https://extensions.gnome.org/extension/425/project-hamster-extension/
  hams...@projecthamster.wordpress.com (version 26.0)
  
  • https://extensions.gnome.org/extension/1082/cpufreq/
  cpufreq@konkor (version 12.0)
  
  3. Lock GNOME session
  
  4. Unlock GNOME session. Notice that all extensions are now deactivated
  :( Expected result is that they should remaining activated per their
  configuration.
  
  5. Using "Tweak Tool"/"gnome-tweak-tool" re-activate all those
  extensions. Restart GNOME by pressing "ALT-F2" keys, type "r", press
  "Enter" key. The extensions are now working.
  
  6. Lock GNOME session again
  
  7. Unlock GNOME session again. Issue is reproduced again. All extensions are 
deactivated. This bug is intermittent though. It depends on various factors, 
including but not limited:
  • Which extensions are activated
  • Your personal configuration with "gnome-tweak-tool" and "gnome-session" 
packages
  
  8. This issue can also be reproduce with rebooting, 

[Desktop-packages] [Bug 1385572] Re: gnome-session not shutting down cleanly

2017-06-10 Thread Francewhoa
Done. I opened a new bug. Find new ticket at
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1697229

As you know this bug #1385572 was fixed in the package gnome-session -
3.9.90-0ubuntu16.1 per comment #15 above at
https://bugs.launchpad.net/ubuntu/+source/gnome-
session/+bug/1385572/comments/15

So this ticket #1385572 is closed. But somehow this bug is back. Maybe a
regression? Maybe a zombie-bug, LOL ;)

Steps to reproduce in that new ticket at
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1697229

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

Title:
  gnome-session not shutting down cleanly

Status in Ubuntu GNOME:
  Fix Released
Status in gnome-session package in Ubuntu:
  Fix Released
Status in gnome-session source package in Trusty:
  Fix Released
Status in gnome-session source package in Utopic:
  Fix Released
Status in gnome-session source package in Vivid:
  Fix Released

Bug description:
  [Impact]
  We have had reports going back to 13.10 that gnome-shell extensions are 
disabled after restart (LP: #1236749), this has probably been our #1 unresolved 
bug for the last few cycles. While this is the main user visible bug probably 
other bugs caused by this for example (BGO: #745707)

  The cause was tracked down to gnome-session not shutting down cleanly
  under upstart. Although the underlying issue seems to be the order in
  which upstart takes down the various components in a user session, the
  side-effects themselves appear to be caused by gnome-session
  continuing to run when it should in fact be shutdown

  The fix updates the 103_kill_the_fail_whale.patch to force shutdown of
  gnome-session. This is inline with the fix upstream for (BGO: #745707)
  also.

  [ Test Case ]
  Note: This is only reproducible under upstart init.
  1. Load gdm
  2. Login to gnome-shell using GNOME from the session list
  3. enable some extensions
  4. reboot system from user menu.
  5. login again to find extensions disabled.

  [ Regression Potential ]
  Very low, the fail whale is meant to be fatal. The upstream dialog that is 
disabled in ubuntu does in fact cause gnome-session to get shutdown.

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

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


[Desktop-packages] [Bug 1697221] Re: Wrapping for labels breaks words

2017-06-10 Thread Jeremy Bicha
*** This bug is a duplicate of bug 1696261 ***
https://bugs.launchpad.net/bugs/1696261

** This bug has been marked a duplicate of bug 1696261
   Settings app items have bad text wrapping

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

Title:
  Wrapping for labels breaks words

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

Bug description:
  
  Labels for some items in Gnome Control Center are too long to fit on a single 
line.
  As a result they must continue onto a second line.

  
  ISSUE:

  Labels do not break at work boundaries.  Instead, they break in the middle of 
words.
  (See attached screenshot).

  Examples:

  Region & Lan
  guage

  Mouse & Touch
  pad

  
  EXPECTED BEHAVIOR:

  Labels should break at work boundaries (i.e. spaces between words).

  Examples:

  Region &
  Language

  Mouse &
  Touchpad

  (If a word is too long and must break in the middle, then conventional
  word hyphenation rules should be applied, or an exception may be made
  to keep the code simple.  This may occur if new items with very long
  names are added to the control center in the future, or for
  accessibility reasons where very large fonts are used).

  
  ADDITIONAL INFO:

  The font used in the screenshots is Liberation Sans Regular 10.
  (However, the word wrapping behavior should be independent of the font and 
size used).

  $ uname -a
  Linux PS001 4.10.0-22-generic #24-Ubuntu SMP Mon May 22 17:43:20 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release --all
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.04
  Release:  17.04
  Codename: zesty

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

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


[Desktop-packages] [Bug 1697229] [NEW] GNOME extensions deactivated after lock unlock

2017-06-10 Thread Francewhoa
Public bug reported:

Summary:
Lock then unlock GNOME session result in all GNOME extensions to be 
deactivated. Intermittent bug.

Steps to reproduce:
1. Install fresh Debian 8.8 Jessie

2. Using https://extensions.gnome.org install and active all the following 
extensions:
• https://extensions.gnome.org/extension/310/alt-tab-workspace/
alt-tab-worksp...@kwalo.net (version 10.0)

• https://extensions.gnome.org/extension/484/workspace-grid/
workspace-g...@mathematical.coffee.gmail.com (version 18.0)

• https://extensions.gnome.org/extension/495/topicons/
topIcons@adel.gadl...@gmail.com (version 29.0)

• https://extensions.gnome.org/extension/672/disable-screen-shield/
disable-screenshi...@lgpasquale.com (version 7.0)

• https://extensions.gnome.org/extension/425/project-hamster-extension/
hams...@projecthamster.wordpress.com (version 26.0)

• https://extensions.gnome.org/extension/1082/cpufreq/
cpufreq@konkor (version 12.0)

3. Lock GNOME session

4. Unlock GNOME session. Notice that all extensions are now deactivated
:( Expected result is that they should remaining activated per their
configuration.

5. Using "Tweak Tool"/"gnome-tweak-tool" re-activate all those
extensions. Restart GNOME by pressing "ALT-F2" keys, type "r", press
"Enter" key. The extensions are now working.

6. Lock GNOME session again

7. Unlock GNOME session again. Issue is reproduced again. All extensions are 
deactivated. This bug is intermittent though. It depends on various factors, 
including but not limited:
• Which extensions are activated
• Your personal configuration with "gnome-tweak-tool" and "gnome-session" 
packages

8. This issue can also be reproduce with rebooting, instead of lock and
unlock the session. Same steps to reproduce as above. But simply reboot.

Using
• Base system: Debian 8.8 Jessie, 64-bit
• Gnome: 3.14.1
• gnome-tweak-tool: 3.14.2-2
• gnome-session: 3.14.0-2
• gnome-session-bin: 3.14.0-2
• gnome-session-common: 3.14.0-2
• Kernel: 4.9.0-0.bpo.3-amd64 #1 SMP Debian 4.9.25-1~bpo8+1 (2017-05-19) x86_64 
GNU/Linux

Notes:
This bug was fixed in the package gnome-session - 3.9.90-0ubuntu16.1 with that 
ticket at  https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1385572
That ticket #1385572 is closed, but this bug is back. Maybe a regression? 
Anyhow I'm reopening this bug with this new ticket #1697229.

Here is another related ticket which includes some temporary fixes, such as:
# 12 at 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1236749/comments/12
# 57 at 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1236749/comments/57

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


** Tags: amd64 gnome-session gnome-shell gnome-tweak-tool jessie

** Tags added: amd64 jessie

** Description changed:

  Summary:
  Lock then unlock GNOME session result in all GNOME extensions to be 
deactivated. Intermittent bug.
- 
  
  Steps to reproduce:
  1. Install fresh Debian 8.8 Jessie
  
  2. Using https://extensions.gnome.org install and active all the following 
extensions:
  • https://extensions.gnome.org/extension/310/alt-tab-workspace/
  alt-tab-worksp...@kwalo.net (version 10.0)
  
- • https://extensions.gnome.org/extension/484/workspace-grid/ 
+ • https://extensions.gnome.org/extension/484/workspace-grid/
  workspace-g...@mathematical.coffee.gmail.com (version 18.0)
  
  • https://extensions.gnome.org/extension/495/topicons/
  topIcons@adel.gadl...@gmail.com (version 29.0)
  
- • https://extensions.gnome.org/extension/672/disable-screen-shield/ 
+ • https://extensions.gnome.org/extension/672/disable-screen-shield/
  disable-screenshi...@lgpasquale.com (version 7.0)
  
- • https://extensions.gnome.org/extension/425/project-hamster-extension/ 
+ • https://extensions.gnome.org/extension/425/project-hamster-extension/
  hams...@projecthamster.wordpress.com (version 26.0)
  
  • https://extensions.gnome.org/extension/1082/cpufreq/
  cpufreq@konkor (version 12.0)
  
  3. Lock GNOME session
  
  4. Unlock GNOME session. Notice that all extensions are now deactivated
  :( Expected result is that they should remaining activated per their
  configuration.
  
  5. Using "Tweak Tool"/"gnome-tweak-tool" re-activate all those
  extensions. Restart GNOME by pressing "ALT-F2" keys, type "r", press
  "Enter" key. The extensions are now working.
  
  6. Lock GNOME session again
  
  7. Unlock GNOME session again. Issue is reproduced again. All extensions are 
deactivated. This bug is intermittent though. It depends on various factors, 
including but not limited:
  • Which extensions are activated
  • Your personal configuration with "gnome-tweak-tool" and "gnome-session" 
packages
  
  8. This issue can also be reproduce with rebooting, instead of lock and
  unlock the session. Same steps to reproduce as above. But simply reboot.
  
- 
  Using
  • Base system: Debian 8.8 Jessie, 64-bit
  • Gnome: 3.14.1
  • gnome-tweak-tool: 3.14.2-2
  • gnome-session: 3.14.0-2
  • 

[Desktop-packages] [Bug 1683862] Re: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial1 failed to install/upgrade: package libreoffice-common is already installed and configured

2017-06-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial1 failed to
  install/upgrade: package libreoffice-common is already installed and
  configured

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I leave the computer alone for a few minutes and when I return there
  is a crash.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial1
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Mon Apr 17 19:56:14 2017
  DuplicateSignature:
   package:libreoffice-common:1:5.1.6~rc2-0ubuntu1~xenial1
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package libnss3-nssdb (--configure):
package libnss3-nssdb is already installed and configured
  ErrorMessage: package libreoffice-common is already installed and configured
  InstallationDate: Installed on 2017-04-17 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial1 failed to 
install/upgrade: package libreoffice-common is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1697223] Re: Nil

2017-06-10 Thread Douglas L. Turnbull
If a bug is found, can it be remedied?

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

Title:
  Nil

Status in xorg package in Ubuntu:
  New

Bug description:
  Suspect virus in external hard drives.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  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
  Date: Sun Jun 11 08:52:58 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:0708]
 Subsystem: Dell GM204M [GeForce GTX 970M] [1028:0708]
  InstallationDate: Installed on 2017-02-18 (112 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Alienware Alienware 15 R2
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=b4c1ed82-d9b3-438b-8f25-73a383ef28a5 ro plymouth:debug=1=1=1=1 
plymouth:debug drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.1.5
  dmi.board.name: Alienware 15 R2
  dmi.board.vendor: Alienware
  dmi.board.version: X01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.1.5:bd09/18/2015:svnAlienware:pnAlienware15R2:pvr1.1.5:rvnAlienware:rnAlienware15R2:rvrX01:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.name: Alienware 15 R2
  dmi.product.version: 1.1.5
  dmi.sys.vendor: Alienware
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Jun 11 08:51:22 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Unknown chipset: NV124
   modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   19528 
   vendor SDC
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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


[Desktop-packages] [Bug 1697223] [NEW] Nil

2017-06-10 Thread Douglas L. Turnbull
Public bug reported:

Suspect virus in external hard drives.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.6
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
Date: Sun Jun 11 08:52:58 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 
[VGA controller])
   Subsystem: Dell Skylake Integrated Graphics [1028:0708]
   Subsystem: Dell GM204M [GeForce GTX 970M] [1028:0708]
InstallationDate: Installed on 2017-02-18 (112 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Alienware Alienware 15 R2
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=b4c1ed82-d9b3-438b-8f25-73a383ef28a5 ro plymouth:debug=1=1=1=1 
plymouth:debug drm.debug=0xe
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2015
dmi.bios.vendor: Alienware
dmi.bios.version: 1.1.5
dmi.board.name: Alienware 15 R2
dmi.board.vendor: Alienware
dmi.board.version: X01
dmi.chassis.type: 10
dmi.chassis.vendor: Alienware
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnAlienware:bvr1.1.5:bd09/18/2015:svnAlienware:pnAlienware15R2:pvr1.1.5:rvnAlienware:rnAlienware15R2:rvrX01:cvnAlienware:ct10:cvrNotSpecified:
dmi.product.name: Alienware 15 R2
dmi.product.version: 1.1.5
dmi.sys.vendor: Alienware
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun Jun 11 08:51:22 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 Unknown chipset: NV124
 modeset(G0): glamor initialization failed
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   19528 
 vendor SDC
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  Nil

Status in xorg package in Ubuntu:
  New

Bug description:
  Suspect virus in external hard drives.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  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
  Date: Sun Jun 11 08:52:58 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:0708]
 Subsystem: Dell GM204M [GeForce GTX 970M] [1028:0708]
  InstallationDate: Installed on 2017-02-18 (112 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Alienware Alienware 15 R2
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=b4c1ed82-d9b3-438b-8f25-73a383ef28a5 ro plymouth:debug=1=1=1=1 
plymouth:debug drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2015
 

[Desktop-packages] [Bug 1692528] Re: gnome-control-center assert failure: *** Error in `gnome-control-center': malloc(): memory corruption (fast): 0x0000556f8e277810 ***

2017-06-10 Thread Jason Bagavatsingham
Can confirm @AsciiWolf's comment. Clicking "Region & Language" will
cause the gnome-control-center to crash.

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

Title:
  gnome-control-center assert failure: *** Error in `gnome-control-
  center': malloc(): memory corruption (fast): 0x556f8e277810 ***

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

Bug description:
  I don't know much more than it's written into debug files, i can help
  if given instructions how to do so.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  AssertionMessage: *** Error in `gnome-control-center': malloc(): memory 
corruption (fast): 0x556f8e277810 ***
  CurrentDesktop: GNOME
  Date: Mon May 22 15:28:27 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-05-13 (8 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   LANGUAGE=pl
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fd391fd53e8 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ar_ptr=0x3, ptr=, str=0x7fd391fd57f0 
"malloc(): memory corruption (fast)", action=3) at malloc.c:5046
   _int_malloc (av=av@entry=0x7fd392208b00 , bytes=bytes@entry=6) 
at malloc.c:3421
   __GI___libc_malloc (bytes=6) at malloc.c:2925
   g_malloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center assert failure: *** Error in 
`gnome-control-center': malloc(): memory corruption (fast): 0x556f8e277810 
***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1697221] [NEW] Wrapping for labels breaks words

2017-06-10 Thread PJSingh5000
Public bug reported:


Labels for some items in Gnome Control Center are too long to fit on a single 
line.
As a result they must continue onto a second line.


ISSUE:

Labels do not break at work boundaries.  Instead, they break in the middle of 
words.
(See attached screenshot).

Examples:

Region & Lan
guage

Mouse & Touch
pad


EXPECTED BEHAVIOR:

Labels should break at work boundaries (i.e. spaces between words).

Examples:

Region &
Language

Mouse &
Touchpad

(If a word is too long and must break in the middle, then conventional
word hyphenation rules should be applied, or an exception may be made to
keep the code simple.  This may occur if new items with very long names
are added to the control center in the future, or for accessibility
reasons where very large fonts are used).


ADDITIONAL INFO:

The font used in the screenshots is Liberation Sans Regular 10.
(However, the word wrapping behavior should be independent of the font and size 
used).

$ uname -a
Linux PS001 4.10.0-22-generic #24-Ubuntu SMP Mon May 22 17:43:20 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release --all
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.04
Release:17.04
Codename:   zesty

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

** Attachment added: "Gnome Control Center showing faulty line wrapping"
   
https://bugs.launchpad.net/bugs/1697221/+attachment/4893733/+files/Screenshot%20from%202017-06-10%2018-05-53.png

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

Title:
  Wrapping for labels breaks words

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

Bug description:
  
  Labels for some items in Gnome Control Center are too long to fit on a single 
line.
  As a result they must continue onto a second line.

  
  ISSUE:

  Labels do not break at work boundaries.  Instead, they break in the middle of 
words.
  (See attached screenshot).

  Examples:

  Region & Lan
  guage

  Mouse & Touch
  pad

  
  EXPECTED BEHAVIOR:

  Labels should break at work boundaries (i.e. spaces between words).

  Examples:

  Region &
  Language

  Mouse &
  Touchpad

  (If a word is too long and must break in the middle, then conventional
  word hyphenation rules should be applied, or an exception may be made
  to keep the code simple.  This may occur if new items with very long
  names are added to the control center in the future, or for
  accessibility reasons where very large fonts are used).

  
  ADDITIONAL INFO:

  The font used in the screenshots is Liberation Sans Regular 10.
  (However, the word wrapping behavior should be independent of the font and 
size used).

  $ uname -a
  Linux PS001 4.10.0-22-generic #24-Ubuntu SMP Mon May 22 17:43:20 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release --all
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.04
  Release:  17.04
  Codename: zesty

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

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


[Desktop-packages] [Bug 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by

2017-06-10 Thread Edward Z. Yang
If you are wondering how to disable power saving, please look at
https://askubuntu.com/a/860754/35182

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

Title:
  [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945
  :03:00.0: BSM uCode verification failed at addr ...; wlan0:
  deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING),

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  From time to time, the system loses all wireles networks and kubuntu
  network manager applet goes blank - not even one network is shown. All
  wifi connections are broken. Rebooting fixes the issue, switching to
  WICD on-the-fly enables to continue browsing without rebooting, so it
  seems to be no hardware issue or iwl3945 issue.

  What to expect: stable connections and flawless network managing.
  What happens: so above.

  Further informations about the system, the network configuration, the
  package version can be found in the attachment, also parts of rsyslog
  and dmesg.

  Interesting, according to some helpers, are the following lines:
  dmesg:   wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice 
(Reason: 3=DEAUTH_LEAVING)

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic

  apt-cache policy network-manager
  network-manager:
    Installiert:   0.9.8.8-0ubuntu28
    Installationskandidat: 0.9.8.8-0ubuntu28
    Versionstabelle:
   *** 0.9.8.8-0ubuntu28 0
  500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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


[Desktop-packages] [Bug 1697122] Re: Package Firefox with MOZ_USE_XINPUT2=1 in environment

2017-06-10 Thread Adolfo Jayme
Upstream blockers:
https://bugzilla.mozilla.org/showdependencytree.cgi?id=1207700_resolved=1

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

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

Title:
  Package Firefox with MOZ_USE_XINPUT2=1 in environment

Status in firefox package in Ubuntu:
  New

Bug description:
  Ubuntu version:  Kubuntu 17.04
  Firefox version: 53.0.3+build1-0ubuntu0.17.04.2

  In Firefox, two-finger scroll gestures on a touchpad are interpreted
  as scroll wheel rotations, and the content scrolls three lines at a
  time. This is inappropriate behavior for touchpad scrolling; it should
  scroll pixel-by-pixel.

  Firefox already has the ability to do this, you just need to turn it
  on by running the program with MOZ_USE_XINPUT2=1 in the environment:
  for example, by running `MOZ_USE_XINPUT2=1 firefox`, or adding it to
  /etc/environment or something like that.

  Turning on this behavior yields a large usability improvement for
  laptop users. Therefore, I am proposing that MOZ_USE_XINPUT2=1 be
  permanently added to the packaging such that it's always present when
  Firefox runs. This is what Fedora does, and it results in a much
  improved experience for the laptop user.

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

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


[Desktop-packages] [Bug 1676131] Re: Gnome Night Light doesn't work

2017-06-10 Thread paraiko
I experience the same issue. The nightlight feature is not working
anymore.

I've used this feature for a couple of months coming from the beta's
towards the released version of ubuntu-gnome 17.04 without any issues.

this week I did a fresh install (although I left /home intact) initially
night light was working, but now it stops. The timer does work (schedule
and indicator in the top bar) but the colour temperature is not changed.

To answer the above questions:

Are you still experiencing this bug?
- yes

Was it day or night when it was not working?
- Everything about nighlight seems to work (indicator, schedule, being able to 
change from manual to sunset/sunrise schedule, switching on and off) apart from 
the actual colourtemperature change

What specifically did you try to get it to work?
- I tried to switch it on and of, change the schedule.
- I disabled the theming (paper-theme) and global dark theme
- I disabled all extensions
- I rebooted (several times)

Hope that helps in triaging. Please let me know if I can do anything to
provide more information and/or help in debuggin.

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

Title:
  Gnome Night Light doesn't work

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

Bug description:
  On the first boot of Ubuntu, the night light worked but after restart
  this option does nothing.

  I couldn't get any log from the terminal.


  Ubuntu Gnome 17.04 beta2
  gnome-control-center 1:3.24.0-0ubuntu1

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

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


[Desktop-packages] [Bug 377508] ✔new catalogue

2017-06-10 Thread bgh
Hello friend,

I found the last  catalogue of your favorite stuff, you can read it here
https://clck.ru/BGdrN

Very truly yours, Bernard GHESTIN


Sent from Mail for Windows 10

** Attachment added: "EC494C97097112BCAE9525518D4DD47C.jpg"
   
https://bugs.launchpad.net/bugs/377508/+attachment/4893699/+files/EC494C97097112BCAE9525518D4DD47C.jpg

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

Title:
  Touchpad Ko with 9.04 Xunbuntu on laptop

Status in xserver-xorg-input-synaptics package in Ubuntu:
  Expired

Bug description:
  I have the 9.04 XUbuntu version
  My touchpad dont work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/377508/+subscriptions

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


[Desktop-packages] [Bug 1697181] Re: package mesa-vulkan-drivers (not installed) failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/libvulkan_intel.so« zu überschreiben, welches auch in Pa

2017-06-10 Thread Timo Aaltonen
this is a bug in the padoka ppa package, not in ubuntu

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

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

Title:
  package mesa-vulkan-drivers (not installed) failed to install/upgrade:
  Versuch, »/usr/lib/x86_64-linux-gnu/libvulkan_intel.so« zu
  überschreiben, welches auch in Paket libgl1-mesa-glx:amd64
  1:17.1.1-1~z~padoka0 ist

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  E: /var/cache/apt/archives/mesa-vulkan-
  drivers_17.0.3-1ubuntu1_amd64.deb: Versuch, »/usr/lib/x86_64-linux-
  gnu/libvulkan_intel.so« zu überschreiben, welches auch in Paket libgl1
  -mesa-glx:amd64 1:17.1.1-1~z~padoka0 ist

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: mesa-vulkan-drivers (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22-lowlatency 4.10.8
  Uname: Linux 4.10.0-20-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering:
   libvulkan-dev:amd64: Install
   mesa-vulkan-drivers:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Jun 10 15:33:48 2017
  ErrorMessage: Versuch, »/usr/lib/x86_64-linux-gnu/libvulkan_intel.so« zu 
überschreiben, welches auch in Paket libgl1-mesa-glx:amd64 1:17.1.1-1~z~padoka0 
ist
  InstallationDate: Installed on 2016-08-23 (290 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: mesa
  Title: package mesa-vulkan-drivers (not installed) failed to install/upgrade: 
Versuch, »/usr/lib/x86_64-linux-gnu/libvulkan_intel.so« zu überschreiben, 
welches auch in Paket libgl1-mesa-glx:amd64 1:17.1.1-1~z~padoka0 ist
  UpgradeStatus: Upgraded to zesty on 2017-04-22 (48 days ago)

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

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


[Desktop-packages] [Bug 1697207] Re: gvfsd-mtp crashed with SIGSEGV

2017-06-10 Thread Apport retracing service
*** This bug is a duplicate of bug 1689770 ***
https://bugs.launchpad.net/bugs/1689770

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gvfsd-mtp crashed with SIGSEGV

Status in gvfs package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.32.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jun 10 15:53:28 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2015-04-30 (772 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/2
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7fc436532cc9:mov0x18(%rax),%rax
   PC (0x7fc436532cc9) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-mtp crashed with SIGSEGV
  UpgradeStatus: Upgraded to artful on 2017-04-14 (57 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
wireshark

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

-- 
Mailing list: https://launchpad.net/~desktop-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: Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing

2017-06-10 Thread Jeremy Bicha
** Package changed: gnome-shell (Ubuntu) => gnome-terminal (Ubuntu)

-- 
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:
  Ubuntu's orange overlay scrollbars escape the bottom of the window
  during resizing

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

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 1697205] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-06-10 Thread Apport retracing service
*** This bug is a duplicate of bug 1688721 ***
https://bugs.launchpad.net/bugs/1688721

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1688721
   Packages that trigger multiple debconf prompts fail to install

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  error of installing

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Sat Jun 10 21:18:12 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-09 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1697205] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-06-10 Thread Agung
*** This bug is a duplicate of bug 1688721 ***
https://bugs.launchpad.net/bugs/1688721

Public bug reported:

error of installing

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Sat Jun 10 21:18:12 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-06-09 (1 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  error of installing

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Sat Jun 10 21:18:12 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-09 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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: Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing

2017-06-10 Thread Adolfo Jayme
The package overlay-scrollbar hasn’t been used in GTK+ 3 applications
for a long time

** Package changed: overlay-scrollbar (Ubuntu) => gtk+3.0 (Ubuntu)

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

Title:
  Ubuntu's orange overlay scrollbars escape the bottom of the window
  during resizing

Status in gnome-shell package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New

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-shell/+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 1458220] Re: [master] system keyboard layout not honored

2017-06-10 Thread Bug Watch Updater
** Changed in: sddm (Mandriva)
   Status: In Progress => Fix Released

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

Title:
  [master] system keyboard layout not honored

Status in sddm package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in sddm package in Mandriva:
  Fix Released

Bug description:
  I'm on a fresh install of Kubuntu:
  Description:Ubuntu 15.04
  Release:15.04

  I chose German as installation language, de with nodeadkeys as
  keyboard and locale is set to de_DE.UTF-8.

  The console uses the correct keyboard, however when logging into sddm,
  the keyboard layout is set to US.

  SDDM doesn't seem to honour the keyboard configured during
  installation.

  SDDM installed is:
  ddm:
Installiert:   0.11.0-0ubuntu10
Installationskandidat: 0.11.0-0ubuntu10
Versionstabelle:
   *** 0.11.0-0ubuntu10 0
  500 http://de.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
  100 /var/lib/dpkg/status

  I believe it's a bug since the keyboard layout at login window after
  installing as described above should be the default system one, german
  in the above case.

  I have tried all sorts of ways (including some ugly hacks) to get this
  resolved on a previous installation but didn't find a way. Considering
  the many moving parts to get the login manager up and running, I'm
  aware this might be filed against the wrong package. It might even be
  an installer bug.

  
  Thanks!

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

-- 
Mailing list: https://launchpad.net/~desktop-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] [NEW] Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing

2017-06-10 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

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)

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

** Affects: gtk+3.0 (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-bug artful visual-quality
-- 
Ubuntu's orange overlay scrollbars escape the bottom of the window during 
resizing
https://bugs.launchpad.net/bugs/1691678
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gtk+3.0 in Ubuntu.

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


[Desktop-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection

2017-06-10 Thread thinow
I have the same problem under Ubuntu 17.04. Wifi connection is dropped
randomly after a couple of minutes.

Output of $ sudo lshw -class network

  *-network 
   description: Ethernet interface
   product: Killer E220x Gigabit Ethernet Controller
   vendor: Qualcomm Atheros
   physical id: 0
   bus info: pci@:04:00.0
   logical name: enp4s0
   version: 13
   serial: 44:8a:5b:6e:a0:f8
   capacity: 1Gbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm pciexpress msi msix bus_master cap_list ethernet 
physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=alx latency=0 
link=no multicast=yes port=twisted pair
   resources: irq:19 memory:f730-f733 ioport:c000(size=128)
  *-network
   description: Wireless interface
   product: Wireless 7260
   vendor: Intel Corporation
   physical id: 0
   bus info: pci@:05:00.0
   logical name: wlp5s0
   version: 6b
   serial: 7c:7a:91:9a:9e:da
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
   configuration: broadcast=yes driver=iwlwifi 
driverversion=4.10.0-22-generic firmware=17.459231.0 ip=192.168.2.106 latency=0 
link=yes multicast=yes wireless=IEEE 802.11
   resources: irq:32 memory:f720-f7201fff

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

Title:
  Internet drops every few minutes on wired and wireless connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Internet drops every 1-30 minutes when connected via wired or wireless
  (i.e., this is a problem on both wired and wireless) even though
  connection icon indicates the computer is still connected.

  Disconnecting and reconnecting via the connection icon resets internet
  temporarily until the next time.

  Dropped internet is discovered with "The site can't be reached"
  screens in Chromium, or error messages when downloading/updating in
  Terminal, or missing connection in Ubuntu Software app, or stalled
  syncing in Insync application (occurred even without Insync).

  Internet drops more frequently on wireless than on wired.

  It seems to disconnect more frequently with heavier internet use
  (e.g., downloading multiple files, opening several webpages in quick
  succession).

  This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron
  15 5567 (dual boot). It occurs when running Live CD as well though.

  Ethernet and wifi both work without randomly disconnecting in Windows
  10 on the same machine, and ethernet and wifi work on other machines
  running Ubuntu and Windows with the same router, so it is not a
  hardware or router issue.

  Output from sudo lshw -class network

  *-network
     description: Wireless interface
     product: Wireless 3165
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:02:00.0
     logical name: wlp2s0
     version: 79
     serial: 58:fb:84:55:21:52
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
     resources: irq:283 memory:df10-df101fff
    *-network
     description: Ethernet interface
     product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:03:00.0
     logical name: enp3s0
     version: 07
     serial: 18:db:f2:3c:d5:37
     size: 10Mbit/s
     capacity: 100Mbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
     resources: irq:279 ioport:d000(size=256) memory:df00-df000fff 
memory:d030-d0303fff

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 21 16:36:55 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-02-20 (1 days ago)
  InstallationMedia: Ubuntu 

[Desktop-packages] [Bug 1689680] Re: gnome-panel crashed with SIGSEGV in gtk_bin_forall()

2017-06-10 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-panel - 1:3.24.1-1ubuntu2

---
gnome-panel (1:3.24.1-1ubuntu2) artful; urgency=medium

  * Build without -Bsymbolic-functions flag (works around LP: #1689680).
  * Update suggestion: gnome-user-guide → gnome-user-docs (LP: #1691867).

 -- Dmitry Shachnev   Sat, 10 Jun 2017 19:12:29
+0300

** Changed in: gnome-panel (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  gnome-panel crashed with SIGSEGV in gtk_bin_forall()

Status in gnome-panel package in Ubuntu:
  Fix Released

Bug description:
  I'm trying to log in using Gnome Flashback but immediately gets thrown
  back out to the login screen again. I have this problem on all my
  computers that has 17.10(+edit) and Flashback(/edit) installed.

  ---
  ~$ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10
  ---
  gnome-panel:
    Installed: 1:3.24.1-1ubuntu1
    Candidate: 1:3.24.1-1ubuntu1
    Version table:
   *** 1:3.24.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status
  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-panel 1:3.24.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu6
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Tue May  9 23:02:29 2017
  ExecutablePath: /usr/bin/gnome-panel
  GsettingsChanges:
   b'org.gnome.gnome-panel.layout' b'object-id-list' b"['menu-bar-0', 
'indicators-0', 'show-desktop-0', 'window-list-0', 'workspace-switcher-0', 
'launcher-0-7', 'launcher-0', 'launcher-0-6', 'launcher-0-3', 'launcher-0-4', 
'multi-load-applet-0', 'launcher', 'launcher-1', 'launcher-4', 'launcher-3', 
'launcher-2', 'launcher-5', 'launcher-6', 'timer-applet-0']"
   b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['top-panel-0', 
'bottom-panel-0']"
  InstallationDate: Installed on 2015-01-22 (838 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: gnome-panel
  SegvAnalysis:
   Segfault happened at: 0x7f7694402464:mov(%rax),%rdi
   PC (0x7f7694402464) ok
   source "(%rax)" (0xf2d81060) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-panel
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/gnome-panel/modules/wncklet.so
   ?? () 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
  Title: gnome-panel crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to artful on 2017-05-08 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd netdev plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1691867] Re: New binary name: gnome-user-docs instead of gnome-user-guide

2017-06-10 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-panel - 1:3.24.1-1ubuntu2

---
gnome-panel (1:3.24.1-1ubuntu2) artful; urgency=medium

  * Build without -Bsymbolic-functions flag (works around LP: #1689680).
  * Update suggestion: gnome-user-guide → gnome-user-docs (LP: #1691867).

 -- Dmitry Shachnev   Sat, 10 Jun 2017 19:12:29
+0300

** Changed in: gnome-panel (Ubuntu)
   Status: New => Fix Released

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

Title:
  New binary name: gnome-user-docs instead of gnome-user-guide

Status in gnome-commander package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  New
Status in gnome-documents package in Ubuntu:
  New
Status in gnome-flashback package in Ubuntu:
  New
Status in gnome-getting-started-docs package in Ubuntu:
  Fix Released
Status in gnome-panel package in Ubuntu:
  Fix Released
Status in gnome-session package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in gnome-user-docs package in Ubuntu:
  Fix Released
Status in meta-gnome3 package in Ubuntu:
  Triaged
Status in ubuntu-docs package in Ubuntu:
  Fix Committed
Status in ubuntu-gnome-meta package in Ubuntu:
  Triaged
Status in unity-control-center package in Ubuntu:
  New
Status in vino package in Ubuntu:
  New
Status in yelp package in Ubuntu:
  New

Bug description:
  The binary package, which is currently built by the gnome-user-docs
  source package, is named gnome-user-guide. To bring it into line with
  upstream, the binary should be named gnome-user-docs.

  This affects quite a few packages, which depend/recommend/suggest
  gnome-user-guide. OTOH, the latter is turned into a transitional dummy
  package.

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

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


[Desktop-packages] [Bug 1697185] [NEW] vce init error (-22)

2017-06-10 Thread Anton Rusnanto
Public bug reported:

gaphic display

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
BootLog:
 [* ] A start job is running for Hold until boot process 
finishes up (22s / no limit)
 Starting WPA supplicant...
 [  OK  ] Started WPA supplicant.
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Jun 10 21:35:59 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c9) (prog-if 
00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Carrizo [1043:13d0]
InstallationDate: Installed on 2017-06-08 (1 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd 
 Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X555QG
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic 
root=UUID=1c098302-9a84-4d05-b001-bcb26aff0602 ro splash quiet
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/18/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X555QG.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X555QG
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555QG.304:bd10/18/2016:svnASUSTeKCOMPUTERINC.:pnX555QG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555QG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X555QG
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat Jun 10 19:37:12 2017
xserver.configfile: default
xserver.errors:
 AMDGPU(G0): amdgpu_device_initialize failed
 RADEON(G1): [drm] failed to set drm interface version.
 RADEON(G1): Kernel modesetting setup failed
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.2
xserver.video_driver: amdgpu

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  vce init error (-22)

Status in xorg package in Ubuntu:
  New

Bug description:
  gaphic display

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  BootLog:
   [* ] A start job is running for Hold until boot process 
finishes up (22s / no limit)
 Starting WPA supplicant...
   [  OK  ] Started WPA supplicant.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Jun 10 21:35:59 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c9) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Carrizo [1043:13d0]
  InstallationDate: Installed on 2017-06-08 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux 

[Desktop-packages] [Bug 1651966] Re: Ubuntu-software center can't open more than 2 seconds

2017-06-10 Thread MadhuSoodanan
https://answers.launchpad.net/ubuntu/+question/642964

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

Title:
  Ubuntu-software center can't open more than 2 seconds

Status in gnome-software package in Ubuntu:
  New

Bug description:
  When I click on the launcher icon for Ubuntu software window appears;
  but for below 2 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic i686
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Dec 22 12:45:12 2016
  InstallationDate: Installed on 2016-10-15 (67 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1697183] [NEW] Unable to select realm for Juniper SSL VPN conntworkManaer Openconnectection in Ne

2017-06-10 Thread Dave Crown
Public bug reported:

Under Ubuntu 17.04, with openconnect, I am attempting to log into a
Juniper ssl vpn. I am prompted for my credentials and realm, but I am
unable to select the realm. Any option I select is ignored, and the
first realm is selected.

# apt-cache policy network-manager-openconnect
network-manager-openconnect:
  Installed: 1.2.4-1
  Candidate: 1.2.4-1
  Version table:
 *** 1.2.4-1 500
500 http://us.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
100 /var/lib/dpkg/status

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

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

Title:
  Unable to select realm for Juniper SSL VPN conntworkManaer
  Openconnectection in Ne

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

Bug description:
  Under Ubuntu 17.04, with openconnect, I am attempting to log into a
  Juniper ssl vpn. I am prompted for my credentials and realm, but I am
  unable to select the realm. Any option I select is ignored, and the
  first realm is selected.

  # apt-cache policy network-manager-openconnect
  network-manager-openconnect:
Installed: 1.2.4-1
Candidate: 1.2.4-1
Version table:
   *** 1.2.4-1 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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


[Desktop-packages] [Bug 1697181] [NEW] package mesa-vulkan-drivers (not installed) failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/libvulkan_intel.so« zu überschreiben, welches auch in

2017-06-10 Thread Moritz Darge
Public bug reported:

E: /var/cache/apt/archives/mesa-vulkan-
drivers_17.0.3-1ubuntu1_amd64.deb: Versuch, »/usr/lib/x86_64-linux-
gnu/libvulkan_intel.so« zu überschreiben, welches auch in Paket libgl1
-mesa-glx:amd64 1:17.1.1-1~z~padoka0 ist

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: mesa-vulkan-drivers (not installed)
ProcVersionSignature: Ubuntu 4.10.0-20.22-lowlatency 4.10.8
Uname: Linux 4.10.0-20-lowlatency x86_64
ApportVersion: 2.20.4-0ubuntu4.1
AptOrdering:
 libvulkan-dev:amd64: Install
 mesa-vulkan-drivers:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Jun 10 15:33:48 2017
ErrorMessage: Versuch, »/usr/lib/x86_64-linux-gnu/libvulkan_intel.so« zu 
überschreiben, welches auch in Paket libgl1-mesa-glx:amd64 1:17.1.1-1~z~padoka0 
ist
InstallationDate: Installed on 2016-08-23 (290 days ago)
InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: mesa
Title: package mesa-vulkan-drivers (not installed) failed to install/upgrade: 
Versuch, »/usr/lib/x86_64-linux-gnu/libvulkan_intel.so« zu überschreiben, 
welches auch in Paket libgl1-mesa-glx:amd64 1:17.1.1-1~z~padoka0 ist
UpgradeStatus: Upgraded to zesty on 2017-04-22 (48 days ago)

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


** Tags: amd64 apport-package zesty

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

Title:
  package mesa-vulkan-drivers (not installed) failed to install/upgrade:
  Versuch, »/usr/lib/x86_64-linux-gnu/libvulkan_intel.so« zu
  überschreiben, welches auch in Paket libgl1-mesa-glx:amd64
  1:17.1.1-1~z~padoka0 ist

Status in mesa package in Ubuntu:
  New

Bug description:
  E: /var/cache/apt/archives/mesa-vulkan-
  drivers_17.0.3-1ubuntu1_amd64.deb: Versuch, »/usr/lib/x86_64-linux-
  gnu/libvulkan_intel.so« zu überschreiben, welches auch in Paket libgl1
  -mesa-glx:amd64 1:17.1.1-1~z~padoka0 ist

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: mesa-vulkan-drivers (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22-lowlatency 4.10.8
  Uname: Linux 4.10.0-20-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering:
   libvulkan-dev:amd64: Install
   mesa-vulkan-drivers:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Jun 10 15:33:48 2017
  ErrorMessage: Versuch, »/usr/lib/x86_64-linux-gnu/libvulkan_intel.so« zu 
überschreiben, welches auch in Paket libgl1-mesa-glx:amd64 1:17.1.1-1~z~padoka0 
ist
  InstallationDate: Installed on 2016-08-23 (290 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: mesa
  Title: package mesa-vulkan-drivers (not installed) failed to install/upgrade: 
Versuch, »/usr/lib/x86_64-linux-gnu/libvulkan_intel.so« zu überschreiben, 
welches auch in Paket libgl1-mesa-glx:amd64 1:17.1.1-1~z~padoka0 ist
  UpgradeStatus: Upgraded to zesty on 2017-04-22 (48 days ago)

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

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


[Desktop-packages] [Bug 1163886] Re: software-center crashed with signal 5 with WebKit 2.0+

2017-06-10 Thread Elias Lattash
I'm having a Software Center crash; please see:
https://github.com/awesomeWM/awesome/issues/1828#issuecomment-307533174

Should I create a new issue for it?

** Bug watch added: github.com/awesomeWM/awesome/issues #1828
   https://github.com/awesomeWM/awesome/issues/1828

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

Title:
  software-center crashed with signal 5 with WebKit 2.0+

Status in WebKit:
  Fix Released
Status in software-center package in Ubuntu:
  Triaged
Status in webkitgtk package in Ubuntu:
  Triaged

Bug description:
  software center crashes when I open it.

  === Steps to reproduce: (from xnox) ===

  1) Download Ubuntu Desktop 13.10 i386 release (disk id 20131016.1), download 
links at
  http://iso.qa.ubuntu.com/qatracker/milestones/305/builds/55929/downloads

  2) Using Virtual Machine Manager - set a VM to have little RAM, e.g.
  798 MB, boot from the above iso.

  3) Click try ubuntu

  4) Enable repositories:
  - edit /etc/apt/sources.list to add universe component
  - Enable gnome3 ppa:
  sudo add-apt-repository ppa:gnome3-team/gnome3

  4) update & dist-upgrade

  5) Click on Ubuntu Software Centre icon from the launcher

  It will appear to be loading, the UI will be fully rendered, but the
  full-width banner, which is white. The window goes gray, and
  disappears. There is a crash file generated for software-center in
  /var/crash/.

  ===

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: software-center 5.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Apr  3 14:15:24 2013
  Disassembly: => 0x7f104ac4f2c5:   Cannot access memory at address 
0x7f104ac4f2c5
  ExecutablePath: /usr/share/software-center/software-center
  InstallationDate: Installed on 2012-10-23 (161 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  InterpreterPath: /usr/bin/python2.7
  MarkForUpload: True
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/software-center
  Signal: 5
  SourcePackage: software-center
  Stacktrace:
   #0  0x7f104ac4f2c5 in ?? ()
   No symbol table info available.
   Cannot access memory at address 0x7fff92459230
  StacktraceTop: ?? ()
  ThreadStacktrace:
   .
   Thread 11 (LWP 16319):
   #0  0x7f104c563ca4 in ?? ()
   No symbol table info available.
   Cannot access memory at address 0x7f1017021e40
  Title: software-center crashed with signal 5
  UpgradeStatus: Upgraded to raring on 2013-04-01 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/webkit-open-source/+bug/1163886/+subscriptions

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


[Desktop-packages] [Bug 1684678] Re: NVIDIA Driver Crashes the System

2017-06-10 Thread Arunkarthick
I got the NVIDIA 375.66 update but still the problem persists..

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

Title:
  NVIDIA Driver Crashes the System

Status in bbswitch package in Ubuntu:
  Confirmed

Bug description:
  When I install the proprietary driver from NVIDIA the system doesn't
  log on.In return it repeatedly shows the error.

  bbswitch:No suitable _dsm call found

  
  Driver shown Additional Drivers Page:

  Using NVIDIA binary driver-version 375.29 from
  nvidia-375(proprietary,tested).

  The NVIDIA Driver was working fine in Ubuntu 16.10 in my laptop. 
  When I upgraded to Ubuntu 17.04 I got this error. So I completely removed 
that and made a clean installation of Ubuntu 17.04 but still I got the error.
   
  My Laptop Specs:

  OS:Ubuntu 17.04

  Processor:i5-5200u

  Graphics: NVIDIA 920M 2GB

  RAM: 8GB

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

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


[Desktop-packages] [Bug 1697156] [NEW] Screen locking issue - password entered for re-login is showing invalid. but the same after clicking on switch-account works

2017-06-10 Thread Saleem Ahmed Khan
Public bug reported:

1) The release of Ubuntu
Description:Ubuntu 14.04.5 LTS
Release:14.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center
No idea which package

3) What you expected to happen
After screen timeout the screen gets locked. When valid password is entered for 
unlocking the screen it should have unlocked.

4) What happened instead
Instead invalid password message is displayed even though valid password is 
entered. But the same after clicking on switch-account works that is after 
clicking on switch-accounts all the accounts are listed and selecting the 
account that was locked and password is entered the screen unlocks.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gnome-screensaver 3.6.1-0ubuntu13
Uname: Linux 3.14.1-031401-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.24
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jun 10 15:17:45 2017
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GsettingsGnomeSession:
 org.gnome.desktop.session session-name 'ubuntu'
 org.gnome.desktop.session idle-delay uint32 600
InstallationDate: Installed on 2014-09-07 (1006 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: gnome-screensaver
Symptom: security
Title: Screen locking issue
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  Screen locking issue - password entered for re-login is showing
  invalid. but the same after clicking on switch-account works

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu
  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  No idea which package

  3) What you expected to happen
  After screen timeout the screen gets locked. When valid password is entered 
for unlocking the screen it should have unlocked.

  4) What happened instead
  Instead invalid password message is displayed even though valid password is 
entered. But the same after clicking on switch-account works that is after 
clicking on switch-accounts all the accounts are listed and selecting the 
account that was locked and password is entered the screen unlocks.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-screensaver 3.6.1-0ubuntu13
  Uname: Linux 3.14.1-031401-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 10 15:17:45 2017
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 600
  InstallationDate: Installed on 2014-09-07 (1006 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1697155] [NEW] No progress dialog under Gnome Shell

2017-06-10 Thread Andreas E.
Public bug reported:

When connecting the backup drive in Gnome Shell (Ubuntu Gnome), backup
starts but does not open the progress dialog. It is hard to keep track
of when the backup process is finished and when it's save to remove the
drive.

Workaround: I have to open gnome-system-monitor and look for a process
"deja-dup" (not to confuse with deja-dup-monitor which remains running
after completion of the backup).

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: deja-dup 34.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Jun 10 11:39:49 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-11-05 (217 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: deja-dup
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: deja-dup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages zesty

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

Title:
  No progress dialog under Gnome Shell

Status in deja-dup package in Ubuntu:
  New

Bug description:
  When connecting the backup drive in Gnome Shell (Ubuntu Gnome), backup
  starts but does not open the progress dialog. It is hard to keep track
  of when the backup process is finished and when it's save to remove
  the drive.

  Workaround: I have to open gnome-system-monitor and look for a process
  "deja-dup" (not to confuse with deja-dup-monitor which remains running
  after completion of the backup).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: deja-dup 34.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jun 10 11:39:49 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-05 (217 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1681513] Re: Ubuntu 17.04: New privacy feature in NetworkManager stops some WiFi adapters from working (mac address randomization)

2017-06-10 Thread Marcos
It also does not work in 17.10. He tries three times, but without
success.

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

Title:
  Ubuntu 17.04: New privacy feature in NetworkManager stops some WiFi
  adapters from working (mac address randomization)

Status in network-manager package in Ubuntu:
  Confirmed

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

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

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

  Original report follows:

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

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

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

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

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


[Desktop-packages] [Bug 1683836] Re: WIFI stoped working when updating 16.10 -> 17.04

2017-06-10 Thread Marcos
It also does not work in 17.10. He tries three times, but without
success.

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

Title:
  WIFI stoped working when updating 16.10 -> 17.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Network manager detects 'Bus 001 Device 004: ID 148f:5370 Ralink
  Technology, Corp. RT5370 Wireless Adapter'. It detects WIFI network,
  but fails to connect. I booted with older kernel
  vmlinuz-4.8.0-46-generic: same result.  I installed ubuntu 16.10 to
  same computer and WIFI does work.  Password is OK.

  Authentication seems to fail in Ubuntu 17.04:
  Apr 18 17:13:01 k10 NetworkManager[727]: 
  [1492524781.2784] policy: auto-activating connection 'ZyXELbb3a'
  [1492524781.2798] device (wlxc83a35cde1eb): Activation: starting connection 
'ZyXELbb3a' (5362ba4d-c40e-40a3-8e17-4e3deaab48ae)
  [1492524781.2801] device (wlxc83a35cde1eb): state change: disconnected -> 
prepare (reason 'none') [30 40 0]
  [1492524781.6699] device (wlxc83a35cde1eb): set-hw-addr: set-cloned MAC 
address to C8:3A:35:CD:E1:EB (permanent)
  [1492524781.9391] device (wlxc83a35cde1eb): state change: prepare -> config 
(reason 'none') [40 50 0]
  [1492524781.9394] device (wlxc83a35cde1eb): Activation: (wifi) access point 
'ZyXELbb3a' has security, but secrets are required.
  [1492524781.9395] device (wlxc83a35cde1eb): state change: config -> need-auth 
(reason 'none') [50 60 0]
  [1492524781.9748] device (wlxc83a35cde1eb): state change: need-auth -> 
prepare (reason 'none') [60 40 0]
  [1492524781.9782] device (wlxc83a35cde1eb): state change: prepare -> config 
(reason 'none') [40 50 0]
  [1492524781.9792] device (wlxc83a35cde1eb): Activation: (wifi) connection 
'ZyXELbb3a' has security, and secrets exist.  No new secrets needed.
  [1492524781.9796] Config: added 'ssid' value 'ZyXELbb3a'
  [1492524781.9800] Config: added 'scan_ssid' value '1'
  [1492524781.9803] Config: added 'key_mgmt' value 'WPA-PSK'
  [1492524781.9806] Config: added 'auth_alg' value 'OPEN'
  [1492524781.9808] Config: added 'psk' value ''
  [1492524781.9821] sup-iface[0x55d34390d2d0,wlxc83a35cde1eb]: config: set 
interface ap_scan to 1
  [1492524782.0010] device (wlxc83a35cde1eb): supplicant interface state: 
inactive -> scanning
  [1492524783.3941] device (wlxc83a35cde1eb): supplicant interface state: 
scanning -> authenticating
  [1492524783.5787] device (wlxc83a35cde1eb): supplicant interface state: 
authenticating -> disconnected
  [1492524793.5868] device (wlxc83a35cde1eb): supplicant interface state: 
disconnected -> scanning
  [1492524794.9891] device (wlxc83a35cde1eb): supplicant interface state: 
scanning -> authenticating
  [1492524795.1145] device (wlxc83a35cde1eb): supplicant interface state: 
authenticating -> disconnected

  
  Ubuntu 16.10 is same to authentication:
  Apr 18 13:46:10 k15 NetworkManager[714]: 
  [1492512370.3874] policy: auto-activating connection 'ZyXELbb3a'
  [1492512370.3884] device (wlxc83a35cde1eb): Activation: starting connection 
'ZyXELbb3a' (fd199068-2375-4268-bb74-d60484d1fadb)
  [1492512370.3886] device (wlxc83a35cde1eb): state change: disconnected -> 
prepare (reason 'none') [30 40 0]
  [1492512370.3887] manager: NetworkManager state is now CONNECTING
  [1492512370.3895] device (wlxc83a35cde1eb): state change: prepare -> config 
(reason 'none') [40 50 0]
  [1492512370.3897] device (wlxc83a35cde1eb): Activation: (wifi) access point 
'ZyXELbb3a' has security, but secrets are required.
  [1492512370.3898] device (wlxc83a35cde1eb): state change: config -> need-auth 
(reason 'none') [50 60 0]
  [1492512370.3936] device (wlxc83a35cde1eb): state change: need-auth -> 
prepare (reason 'none') [60 40 0]
  [1492512370.3940] device (wlxc83a35cde1eb): state change: prepare -> config 
(reason 'none') [40 50 0]
  [1492512370.3943] device (wlxc83a35cde1eb): Activation: (wifi) connection 
'ZyXELbb3a' has security, and secrets exist.  No new secrets needed.
  [1492512370.3943] Config: added 'ssid' value 'ZyXELbb3a'
  [1492512370.3944] Config: added 'scan_ssid' value '1'
  [1492512370.3944] Config: added 'key_mgmt' value 'WPA-PSK'
  [1492512370.3944] Config: added 'auth_alg' value 'OPEN'
  [1492512370.3944] Config: added 'psk' value ''
  [1492512370.3949] sup-iface[0x55da7c3f2210,wlxc83a35cde1eb]: config: set 
interface ap_scan to 1
  [1492512371.8005] device (wlxc83a35cde1eb): supplicant interface state: 
inactive -> authenticating
  [1492512371.8071] device (wlxc83a35cde1eb): supplicant interface state: 
authenticating -> associating
  [1492512371.8216] device (wlxc83a35cde1eb): supplicant interface state: 
associating -> 4-way handshake
  [1492512371.8482] device (wlxc83a35cde1eb): supplicant interface state: 4-way 
handshake -> completed
  [1492512371.8482] device (wlxc83a35cde1eb): Activation: (wifi) Stage 2 of 5 
(Device Configure) successful.  Connected 

[Desktop-packages] [Bug 1684100] Re: TP-LINK TL-WN722N 150MBPS not working on Ubuntu 17.04. Worked fine on 16.10

2017-06-10 Thread Marcos
It also does not work in 17.10. He tries three times, but without
success. I have tried the solutions suggested above, but they have had
no effect.

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

Title:
  TP-LINK TL-WN722N 150MBPS not working on Ubuntu 17.04. Worked fine on
  16.10

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  TP-LINK TL-WN722N 150MBPS not working on Ubuntu 17.04. Worked fine on
  16.10

  sudo apt-get update; sudo apt-get install usbutils pciutils hwinfo grep 
rfkill; sudo lshw -C network; rfkill list; sudo iwlist scan | grep -Ei 
'chan|ssid'; cat /etc/network/interfaces; cat /etc/lsb-release; lspci -nnk | 
grep -iA2 net; lsusb; nmcli nm status; sudo lshw -short; uname -a; sudo 
updatedb; dmesg | grep -E  
'02:00|80211|acx|at76|ath|b43|bcm|brcm|CX|eth|ipw|ireless|irmware|isl|lbtf|orinoco|ndiswrapper|NPE|ound|p54|prism|rror|rtl|RTL|rt2|RT2|rt3|RT3|rt5|RT5|rt6|RT6|rt7|RT7|usb|witch|wl';sudo
 dmidecode|grep -E 'anufact|roduct|erial|elease'; iwconfig; grep -E 
'80211|acx|at76|ath|b43|bcm|brcm|CX|eth|ipw|irmware|isl|lbtf|orinoco|ndiswrapper|NPE|p54|prism|rtl|rt2|rt3|rt6|rt7|wmi|witch|wl'
 /etc/modprobe.d/*; cat /var/lib/NetworkManager/NetworkManager.state; sudo 
hwinfo --netcard ; ps -aux|grep -E 'wpa|icd|etwork'; netstat -rn ; cat 
/etc/resolv.conf; ls -lia /boot; grep tmpfs /etc/fstab; ubuntu-support-status; 
sudo update-pciids; sudo update-usbids; sudo lsmod
  Get:1 http://security.ubuntu.com/ubuntu zesty-security InRelease [89.2 kB]
  Get:2 http://gb.archive.ubuntu.com/ubuntu zesty InRelease [243 kB]
  Get:3 http://gb.archive.ubuntu.com/ubuntu zesty-updates InRelease [89.2 kB]
  Hit:4 http://gb.archive.ubuntu.com/ubuntu zesty-backports InRelease
  Fetched 421 kB in 0s (873 kB/s)   
  Reading package lists... Done
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  grep is already the newest version (2.27-2).
  pciutils is already the newest version (1:3.3.1-1.1ubuntu9).
  pciutils set to manually installed.
  rfkill is already the newest version (0.5-1ubuntu3).
  rfkill set to manually installed.
  usbutils is already the newest version (1:007-4).
  usbutils set to manually installed.
  The following additional packages will be installed:
libhd21 libx86emu1
  The following NEW packages will be installed
hwinfo libhd21 libx86emu1
  0 to upgrade, 3 to newly install, 0 to remove and 0 not to upgrade.
  Need to get 754 kB of archives.
  After this operation, 3,261 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://gb.archive.ubuntu.com/ubuntu zesty/universe amd64 libx86emu1 
amd64 1.11-2 [47.8 kB]
  Get:2 http://gb.archive.ubuntu.com/ubuntu zesty/universe amd64 libhd21 amd64 
21.38-1 [688 kB]
  Get:3 http://gb.archive.ubuntu.com/ubuntu zesty/universe amd64 hwinfo amd64 
21.38-1 [17.7 kB]
  Fetched 754 kB in 0s (2,074 kB/s) 
  Selecting previously unselected package libx86emu1:amd64.
  (Reading database ... 177811 files and directories currently installed.)
  Preparing to unpack .../libx86emu1_1.11-2_amd64.deb ...
  Unpacking libx86emu1:amd64 (1.11-2) ...
  Selecting previously unselected package libhd21:amd64.
  Preparing to unpack .../libhd21_21.38-1_amd64.deb ...
  Unpacking libhd21:amd64 (21.38-1) ...
  Selecting previously unselected package hwinfo.
  Preparing to unpack .../hwinfo_21.38-1_amd64.deb ...
  Unpacking hwinfo (21.38-1) ...
  Setting up libx86emu1:amd64 (1.11-2) ...
  Processing triggers for libc-bin (2.24-9ubuntu2) ...
  Processing triggers for man-db (2.7.6.1-2) ...
  Setting up libhd21:amd64 (21.38-1) ...
  Setting up hwinfo (21.38-1) ...
  Processing triggers for libc-bin (2.24-9ubuntu2) ...
*-network 
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:04:00.0
 logical name: enp4s0
 version: 06
 serial: f4:6d:04:90:cb:7a
 size: 10Mbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl_nic/rtl8168e-2.fw latency=0 
link=no multicast=yes port=MII speed=10Mbit/s
 resources: irq:31 ioport:c000(size=256) memory:f0004000-f0004fff 
memory:f000-f0003fff
*-network:0
 description: Wireless interface
 physical id: 3
 bus info: usb@2:1.7
 logical name: wlxf81a6721bb82
 serial: 56:3e:54:48:50:00
 capabilities: ethernet physical wireless

[Desktop-packages] [Bug 1697151] Re: package printer-driver-gutenprint (not installed) failed to install/upgrade: package printer-driver-gutenprint is not ready for configuration cannot configure (cur

2017-06-10 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package printer-driver-gutenprint (not installed) failed to
  install/upgrade: package printer-driver-gutenprint is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in gutenprint package in Ubuntu:
  New

Bug description:
  Occurred during the next update of packages.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: printer-driver-gutenprint (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sat Jun 10 09:00:06 2017
  ErrorMessage: package printer-driver-gutenprint is not ready for 
configuration  cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2016-11-14 (207 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: gutenprint
  Title: package printer-driver-gutenprint (not installed) failed to 
install/upgrade: package printer-driver-gutenprint is not ready for 
configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1697151] [NEW] package printer-driver-gutenprint (not installed) failed to install/upgrade: package printer-driver-gutenprint is not ready for configuration cannot configure (c

2017-06-10 Thread serjsb
Public bug reported:

Occurred during the next update of packages.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: printer-driver-gutenprint (not installed)
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Sat Jun 10 09:00:06 2017
ErrorMessage: package printer-driver-gutenprint is not ready for configuration  
cannot configure (current status 'half-installed')
InstallationDate: Installed on 2016-11-14 (207 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: gutenprint
Title: package printer-driver-gutenprint (not installed) failed to 
install/upgrade: package printer-driver-gutenprint is not ready for 
configuration  cannot configure (current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package printer-driver-gutenprint (not installed) failed to
  install/upgrade: package printer-driver-gutenprint is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in gutenprint package in Ubuntu:
  New

Bug description:
  Occurred during the next update of packages.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: printer-driver-gutenprint (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sat Jun 10 09:00:06 2017
  ErrorMessage: package printer-driver-gutenprint is not ready for 
configuration  cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2016-11-14 (207 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: gutenprint
  Title: package printer-driver-gutenprint (not installed) failed to 
install/upgrade: package printer-driver-gutenprint is not ready for 
configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1697153] [NEW] package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es noch

2017-06-10 Thread Manfred
Public bug reported:

linux-libc-dev:amd64 (4.4.0-79.100) wird eingerichtet ...
Fehler traten auf beim Bearbeiten von:
 libnl-genl-3-200:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
AptOrdering:
 libnl-3-200: Install
 libnl-3-200: Configure
 libnl-genl-3-200: Configure
 libnl-route-3-200: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Jun 10 10:30:10 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu7
 libgcc1 1:6.0.1-0ubuntu1
 libnl-3-200 3.2.27-1ubuntu0.16.04.1
ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
InstallationDate: Installed on 2016-04-03 (432 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: libnl3
Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to 
install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - 
Sie sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
UpgradeStatus: Upgraded to xenial on 2016-11-29 (192 days ago)

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

Title:
  package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to
  install/upgrade: Paket ist in einem sehr schlechten inkonsistenten
  Zustand - Sie sollten es  nochmal installieren, bevor Sie die
  Konfiguration versuchen.

Status in libnl3 package in Ubuntu:
  New

Bug description:
  linux-libc-dev:amd64 (4.4.0-79.100) wird eingerichtet ...
  Fehler traten auf beim Bearbeiten von:
   libnl-genl-3-200:amd64
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libnl-3-200: Install
   libnl-3-200: Configure
   libnl-genl-3-200: Configure
   libnl-route-3-200: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Jun 10 10:30:10 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
   libnl-3-200 3.2.27-1ubuntu0.16.04.1
  ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  InstallationDate: Installed on 2016-04-03 (432 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libnl3
  Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to 
install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - 
Sie sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  UpgradeStatus: Upgraded to xenial on 2016-11-29 (192 days ago)

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

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