date:20180501

The BadAccess from ShmAttach is coming from the Xorg process somewhere
in here:

static int
ProcShmAttach(ClientPtr client)
{
SHMSTAT_TYPE buf;
ShmDescPtr shmdesc;

REQUEST(xShmAttachReq);

REQUEST_SIZE_MATCH(xShmAttachReq);
LEGAL_NEW_RESOURCE(stuff->shmseg, client);
if ((stuff->readOnly != xTrue) && (stuff->readOnly != xFalse)) {
client->errorValue = stuff->readOnly;
return BadValue;
}
for (shmdesc = Shmsegs; shmdesc; shmdesc = shmdesc->next) {
if (!SHMDESC_IS_FD(shmdesc) && shmdesc->shmid == stuff->shmid)
break;
}
if (shmdesc) {
if (!stuff->readOnly && !shmdesc->writable)
return BadAccess;
shmdesc->refcnt++;
}
else {
shmdesc = malloc(sizeof(ShmDescRec));
if (!shmdesc)
return BadAlloc;
#ifdef SHM_FD_PASSING
shmdesc->is_fd = FALSE;
#endif
shmdesc->addr = shmat(stuff->shmid, 0,
  stuff->readOnly ? SHM_RDONLY : 0);
if ((shmdesc->addr == ((char *) -1)) || SHMSTAT(stuff->shmid, )) {
free(shmdesc);
return BadAccess;
}

/* The attach was performed with root privs. We must
 * do manual checking of access rights for the credentials
 * of the client */

if (shm_access(client, &(SHM_PERM(buf)), stuff->readOnly) == -1) {
shmdt(shmdesc->addr);
free(shmdesc);
return BadAccess;
}

shmdesc->shmid = stuff->shmid;
shmdesc->refcnt = 1;
shmdesc->writable = !stuff->readOnly;
shmdesc->size = SHM_SEGSZ(buf);
shmdesc->next = Shmsegs;
Shmsegs = shmdesc;
}
if (!AddResource(stuff->shmseg, ShmSegType, (void *) shmdesc))
return BadAlloc;
return Success;
}

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in OEM Priority Project:
  Triaged
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Incomplete
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet

[Desktop-packages] [Bug 1767784] Re: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9

Another instance of this issue has been reported in bug 1768411.

** Description changed:

  Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is
  not showing anymore my soundcard.
+ 
+ https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.9
  
  The command "pacmd list-sinks" only shows a dummy output
  
  When running on a fresh install of ubuntu 16.04, the sound is ok.
  When updating the install with locking the following files to version 
1:8.0-0ubuntu3 the sound keeps working:
  libpulse0:amd64
  libpulse-mainloop-glib0:amd64
  libpulse-dev:amd64
  pulseaudio-module-x11:amd64
  pulseaudio-module-bluetooth:amd64
  pulseaudio-utils:amd64
  
  When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output".
  
  I tried running the following versions of Ubuntu (live usb), and get the same 
issue (no need to update to get the problem)
  17.04
  17.10
  18.04
  
  I attached the result of command "pactl list"
  I have also generated logs during the boot but I don't know how to attach 
multiple files

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

Title:
  [regression] output device not recognized anymore since update
  1:8.0-0ubuntu3.9

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is
  not showing anymore my soundcard.

  https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.9

  The command "pacmd list-sinks" only shows a dummy output

  When running on a fresh install of ubuntu 16.04, the sound is ok.
  When updating the install with locking the following files to version 
1:8.0-0ubuntu3 the sound keeps working:
  libpulse0:amd64
  libpulse-mainloop-glib0:amd64
  libpulse-dev:amd64
  pulseaudio-module-x11:amd64
  pulseaudio-module-bluetooth:amd64
  pulseaudio-utils:amd64

  When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output".

  I tried running the following versions of Ubuntu (live usb), and get the same 
issue (no need to update to get the problem)
  17.04
  17.10
  18.04

  I attached the result of command "pactl list"
  I have also generated logs during the boot but I don't know how to attach 
multiple files

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

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

[Desktop-packages] [Bug 1768411] Re: pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default

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

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


** This bug has been marked a duplicate of bug 1767784
   [regression] output device not recognized anymore since update 
1:8.0-0ubuntu3.9

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

Title:
  pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware,  the
  dummy output profile is selected by default

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I help manage a few hundred computers and since the last pulseaudio
  update a few weeks ago ( xenial-updates )  from
  pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb to
  pulseaudio_1%3a8.0-0ubuntu3.9_amd64.deb ( and libpulse0 )  certain
  hardware including dell models 755, 390, and 3050 lost sound.  They
  were working fine for years but now the dummy output profile is
  selected by default. What happened?

  
  This can be worked around by explicitly setting:
  set-card-profile 0 output:analog-stereo
  set-sink-port 1  analog-output-headphones

  
  or by reverting back to pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb ( along with 
libpulse0 ) .

  
  When I try to use apport it gets to the end and says "apport cannot connect 
to crash database" but I have included example system details in the attachment 
after the output of pacmd list sinks and default.pa.   ( You can only attach 
one file ?!?)

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

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

[Desktop-packages] [Bug 1767784] Re: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9

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

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

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

Title:
  [regression] output device not recognized anymore since update
  1:8.0-0ubuntu3.9

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is
  not showing anymore my soundcard.

  https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.9

  The command "pacmd list-sinks" only shows a dummy output

  When running on a fresh install of ubuntu 16.04, the sound is ok.
  When updating the install with locking the following files to version 
1:8.0-0ubuntu3 the sound keeps working:
  libpulse0:amd64
  libpulse-mainloop-glib0:amd64
  libpulse-dev:amd64
  pulseaudio-module-x11:amd64
  pulseaudio-module-bluetooth:amd64
  pulseaudio-utils:amd64

  When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output".

  I tried running the following versions of Ubuntu (live usb), and get the same 
issue (no need to update to get the problem)
  17.04
  17.10
  18.04

  I attached the result of command "pactl list"
  I have also generated logs during the boot but I don't know how to attach 
multiple files

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

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

[Desktop-packages] [Bug 1768416] [NEW] ath9k_htc Reason: 3=DEAUTH_LEAVING

2018-05-01 Thread sles

Public bug reported:

After upgrade from 16.04 to 18.04 I can't use wifi.
It is ath9k_htc usb.

I got error Reason: 3=DEAUTH_LEAVING

I used workaround from

https://unix.stackexchange.com/questions/386925/aborting-authentication-
by-local-choice-reason-3-deauth-leaving-when-trying

ln -s /dev/null /etc/systemd/network/99-default.link

And got it working, but, I think , this should be fixed.

Thank you!

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

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

Title:
  ath9k_htc Reason: 3=DEAUTH_LEAVING

Status in network-manager package in Ubuntu:
  New

Bug description:
  After upgrade from 16.04 to 18.04 I can't use wifi.
  It is ath9k_htc usb.

  I got error Reason: 3=DEAUTH_LEAVING

  I used workaround from

  https://unix.stackexchange.com/questions/386925/aborting-
  authentication-by-local-choice-reason-3-deauth-leaving-when-trying

  ln -s /dev/null /etc/systemd/network/99-default.link

  And got it working, but, I think , this should be fixed.

  Thank you!

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

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

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

2018-05-01 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 tex-common in Ubuntu.
https://bugs.launchpad.net/bugs/1768414

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

Status in tex-common package in Ubuntu:
  New

Bug description:
  This tex-common file upgrade problem happens every time I run the
  updater.  I hate to post another bug report, but the report bug window
  keeps popping up until I do.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Tue May  1 19:59:27 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2012-05-04 (2189 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-07 (632 days ago)

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

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

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

2018-05-01 Thread Steve Edlefsen

Public bug reported:

This tex-common file upgrade problem happens every time I run the
updater.  I hate to post another bug report, but the report bug window
keeps popping up until I do.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
Uname: Linux 4.4.0-121-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Tue May  1 19:59:27 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2012-05-04 (2189 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: tex-common
Title: package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-08-07 (632 days ago)

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

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

Status in tex-common package in Ubuntu:
  New

Bug description:
  This tex-common file upgrade problem happens every time I run the
  updater.  I hate to post another bug report, but the report bug window
  keeps popping up until I do.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Tue May  1 19:59:27 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2012-05-04 (2189 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-07 (632 days ago)

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

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

[Desktop-packages] [Bug 1768411] Re: pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default

here is the text from running:
apport-cli -f -p pulseaudio --save bug.apport


** Attachment added: "bug.apport"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+attachment/5131795/+files/bug.apport

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

Title:
  pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware,  the
  dummy output profile is selected by default

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I help manage a few hundred computers and since the last pulseaudio
  update a few weeks ago ( xenial-updates )  from
  pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb to
  pulseaudio_1%3a8.0-0ubuntu3.9_amd64.deb ( and libpulse0 )  certain
  hardware including dell models 755, 390, and 3050 lost sound.  They
  were working fine for years but now the dummy output profile is
  selected by default. What happened?

  
  This can be worked around by explicitly setting:
  set-card-profile 0 output:analog-stereo
  set-sink-port 1  analog-output-headphones

  
  or by reverting back to pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb ( along with 
libpulse0 ) .

  
  When I try to use apport it gets to the end and says "apport cannot connect 
to crash database" but I have included example system details in the attachment 
after the output of pacmd list sinks and default.pa.   ( You can only attach 
one file ?!?)

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

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

[Desktop-packages] [Bug 1768411] Re: pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default

here is the default.pa

** Attachment added: "default.pa"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+attachment/5131794/+files/default.pa

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

Title:
  pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware,  the
  dummy output profile is selected by default

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I help manage a few hundred computers and since the last pulseaudio
  update a few weeks ago ( xenial-updates )  from
  pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb to
  pulseaudio_1%3a8.0-0ubuntu3.9_amd64.deb ( and libpulse0 )  certain
  hardware including dell models 755, 390, and 3050 lost sound.  They
  were working fine for years but now the dummy output profile is
  selected by default. What happened?

  
  This can be worked around by explicitly setting:
  set-card-profile 0 output:analog-stereo
  set-sink-port 1  analog-output-headphones

  
  or by reverting back to pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb ( along with 
libpulse0 ) .

  
  When I try to use apport it gets to the end and says "apport cannot connect 
to crash database" but I have included example system details in the attachment 
after the output of pacmd list sinks and default.pa.   ( You can only attach 
one file ?!?)

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

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

[Desktop-packages] [Bug 1768411] Re: pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default

I see now there is an option for additional attachments (one per
comment) so I'm going to attache the files separately, here is the
output of pacmd list sinks

** Attachment added: "pacmd-list.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+attachment/5131793/+files/pacmd-list.log

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

Title:
  pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware,  the
  dummy output profile is selected by default

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I help manage a few hundred computers and since the last pulseaudio
  update a few weeks ago ( xenial-updates )  from
  pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb to
  pulseaudio_1%3a8.0-0ubuntu3.9_amd64.deb ( and libpulse0 )  certain
  hardware including dell models 755, 390, and 3050 lost sound.  They
  were working fine for years but now the dummy output profile is
  selected by default. What happened?

  
  This can be worked around by explicitly setting:
  set-card-profile 0 output:analog-stereo
  set-sink-port 1  analog-output-headphones

  
  or by reverting back to pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb ( along with 
libpulse0 ) .

  
  When I try to use apport it gets to the end and says "apport cannot connect 
to crash database" but I have included example system details in the attachment 
after the output of pacmd list sinks and default.pa.   ( You can only attach 
one file ?!?)

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

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

[Desktop-packages] [Bug 1768411] [NEW] pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default

Public bug reported:

I help manage a few hundred computers and since the last pulseaudio
update a few weeks ago ( xenial-updates )  from
pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb to
pulseaudio_1%3a8.0-0ubuntu3.9_amd64.deb ( and libpulse0 )  certain
hardware including dell models 755, 390, and 3050 lost sound.  They were
working fine for years but now the dummy output profile is selected by
default. What happened?


This can be worked around by explicitly setting:
set-card-profile 0 output:analog-stereo
set-sink-port 1  analog-output-headphones


or by reverting back to pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb ( along with 
libpulse0 ) .


When I try to use apport it gets to the end and says "apport cannot connect to 
crash database" but I have included example system details in the attachment 
after the output of pacmd list sinks and default.pa.   ( You can only attach 
one file ?!?)

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

** Attachment added: "pacmd list sinks and default.pa and  apport bug text 
contents"
   
https://bugs.launchpad.net/bugs/1768411/+attachment/5131792/+files/pacmd-list-and-default-pa-and-apport-bug.txt

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

Title:
  pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware,  the
  dummy output profile is selected by default

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I help manage a few hundred computers and since the last pulseaudio
  update a few weeks ago ( xenial-updates )  from
  pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb to
  pulseaudio_1%3a8.0-0ubuntu3.9_amd64.deb ( and libpulse0 )  certain
  hardware including dell models 755, 390, and 3050 lost sound.  They
  were working fine for years but now the dummy output profile is
  selected by default. What happened?

  
  This can be worked around by explicitly setting:
  set-card-profile 0 output:analog-stereo
  set-sink-port 1  analog-output-headphones

  
  or by reverting back to pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb ( along with 
libpulse0 ) .

  
  When I try to use apport it gets to the end and says "apport cannot connect 
to crash database" but I have included example system details in the attachment 
after the output of pacmd list sinks and default.pa.   ( You can only attach 
one file ?!?)

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

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

[Desktop-packages] [Bug 1597314] Re: Support snap interface plug/slots

** Summary changed:

- Support for apps which do not automatically connect to slots
+ Support snap interface plug/slots

** Summary changed:

- Support snap interface plug/slots
+ Support snap interface plugs and slots

** Description changed:

- With the addition of new interfaces there are some plugs which do not
- automatically connect and require action from the user in order to be
- connecte.
+ [Impact]
+ Snaps have a concept of "interfaces" which allows access to various system 
resources to be "connected" to snaps. While the majority of interfaces for 
desktop apps are connected, there are some that are not. There is no graphical 
method to connect these in the Ubuntu desktop (they can be connected from the 
command line).
  
- As an example, VLC doesn't not automatically connect to the camera
- interface, but users may want to enable this, or maybe they dont.
+ [Test Case]
+ 1. Open GNOME Software
+ 2. Select the GNOME Characters snap (installed by default)
  
- Some design considerations:
+ Expected result:
+ Information is shown about interfaces this snap uses and there is a method to 
control this. In the implementation this is done with a "Permissions" button 
(beside "Launch") and a dialog with switches to control this.
  
-  * Do we want to ask users to toggle on/off connections they do/do not
- want.  i.e. a list of toggle buttons (what effect would this have on the
- application, would it fail gracefully or just not work (in which case
- the user could be made aware that it won't work without the
- permissions).
+ Observed result:
+ No interface information is shown, so the home interface cannot be 
disconnected.
  
- vs
- 
-  * Do we want just a single Yes/No question where it's all the
- connections or none.
+ [Regression Potential]
+ The change is quite large and had to be restructured from the version that is 
shipped in Bionic. With such a large amount of code there is the potential for 
new bugs.

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

Title:
  Support snap interface plugs and slots

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Artful:
  Won't Fix
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Snaps have a concept of "interfaces" which allows access to various system 
resources to be "connected" to snaps. While the majority of interfaces for 
desktop apps are connected, there are some that are not. There is no graphical 
method to connect these in the Ubuntu desktop (they can be connected from the 
command line).

  [Test Case]
  1. Open GNOME Software
  2. Select the GNOME Characters snap (installed by default)

  Expected result:
  Information is shown about interfaces this snap uses and there is a method to 
control this. In the implementation this is done with a "Permissions" button 
(beside "Launch") and a dialog with switches to control this.

  Observed result:
  No interface information is shown, so the home interface cannot be 
disconnected.

  [Regression Potential]
  The change is quite large and had to be restructured from the version that is 
shipped in Bionic. With such a large amount of code there is the potential for 
new bugs.

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

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

[Desktop-packages] [Bug 1682695] Re: System stops recognizing correct screen resolution

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  System stops recognizing correct screen resolution

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Up to last night, I was using my system just fine, with my 1280x1024
  monitor.  Today, the system boots up with all the text and icons much
  larger, and Settings -> Displays now informs me that my monitor is
  only 1024x768 and won't permit me to change it back to the correct
  setting.  I haven't changed anything, hardware or software.  How do I
  make it work correctly again?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr 13 19:07:58 2017
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. G98 [GeForce 8400 GS Rev. 2] [1043:8321]
  InstallationDate: Installed on 2017-03-26 (18 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: MSI MS-7865
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: AM1I (MS-7865)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.0:bd02/21/2014:svnMSI:pnMS-7865:pvr2.0:rvnMSI:rnAM1I(MS-7865):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7865
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Thu Apr 13 19:04:54 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 04f3:0103KEYBOARD, id 8
   inputHID 04f3:0103KEYBOARD, id 9
   inputUSB Optical MouseMOUSE, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output DVI-I-1   
VGA-1
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1698407] Re: Checkboxes not showing on some sites

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Checkboxes not showing on some sites

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Firefox updated to 54 today, checkboxes are not showing on my private
  helpdesk application (old version of Kayako) but I have also just
  noticed on Reddit, specifically the subreddit search box. I also note
  there are no buttons showing on Gandi.net's login page which is
  probably related - this occurred in 52 but not 53.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 54.0+build3-0ubuntu0.16.10.1
  ProcVersionSignature: Ubuntu 4.8.0-54.57-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  simong 2591 F pulseaudio
  BuildID: 20170612122018
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Fri Jun 16 16:48:19 2017
  EcryptfsInUse: Yes
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-07-22 (328 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.1.1 dev wlp1s0  proto static  metric 600 
   169.254.0.0/16 dev virbr0  scope link  metric 1000 linkdown 
   192.168.1.0/24 dev wlp1s0  proto kernel  scope link  src 192.168.1.45  
metric 600 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
linkdown
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-26c3f5ab-4dd8-4ac4-8d6d-4edaa1170613
  Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=54.0/20170612122018 (In use)
  RelatedPackageVersions: adobe-flashplugin 1:20170613.2-0ubuntu0.16.10.1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to yakkety on 2016-11-02 (225 days ago)
  dmi.bios.date: 04/12/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N350DW
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd04/12/2016:svnPCSpecialistLimited:pnN350DW:pvrNotApplicable:rvnCLEVO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: N350DW
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

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

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

[Desktop-packages] [Bug 1706286] Re: Gnome System Monitor freezes when wi-fi is reconnecting

[Expired for gnome-system-monitor (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: gnome-system-monitor (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Gnome System Monitor freezes when wi-fi is reconnecting

Status in gnome-system-monitor package in Ubuntu:
  Expired

Bug description:
  To replicate:
  1. Use network manager to connect to a poor quality Wi-Fi router (signal 
strength is irrelevant: the router itself must be low quality).
  2. After a short period of time: the connection will stall and require manual 
reconnection. Use the network manager gnome applet to select the "connected" 
Wi-Fi again.

  Observed results:
  Gnome System Monitor becomes unresponsive until the Wi-Fi is connected again.

  Expected results:
  Apart from the network usage graph: Gnome System Monitor should not be 
affected by changing network connections.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-system-monitor 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-27-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jul 25 20:34:11 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-system-monitor
  InstallationDate: Installed on 2017-07-22 (2 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: gnome-system-monitor
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768408] [NEW] Desktop content

2018-05-01 Thread Davi Mizael

Public bug reported:

By dragging a desktop content into a folder on the system, the desktop
gets stuck and only comes back with the system reboot

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed May  2 01:10:35 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:225a]
InstallationDate: Installed on 2018-04-27 (4 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Hewlett-Packard HP EliteBook 820 G2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1d729abd-93bc-472e-89ed-243524756bc7 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/13/2017
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M71 Ver. 01.21
dmi.board.name: 225A
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 96.5B
dmi.chassis.asset.tag: 5CG6257W70
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM71Ver.01.21:bd07/13/2017:svnHewlett-Packard:pnHPEliteBook820G2:pvrA3009D510303:rvnHewlett-Packard:rn225A:rvrKBCVersion96.5B:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP EliteBook 820 G2
dmi.product.version: A3009D510303
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Desktop content

Status in xorg package in Ubuntu:
  New

Bug description:
  By dragging a desktop content into a folder on the system, the desktop
  gets stuck and only comes back with the system reboot

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 01:10:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:225a]
  InstallationDate: Installed on 2018-04-27 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP EliteBook 820 G2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1d729abd-93bc-472e-89ed-243524756bc7 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2017
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M71 Ver. 01.21
  dmi.board.name: 225A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 96.5B
  dmi.chassis.asset.tag: 5CG6257W70
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM71Ver.01.21:bd07/13/2017:svnHewlett-Packard:pnHPEliteBook820G2:pvrA3009D510303:rvnHewlett-Packard:rn225A:rvrKBCVersion96.5B:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 820 G2
  dmi.product.version: A3009D510303
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1

[Desktop-packages] [Bug 1763736] Re: communitheme snap not present in gnome software on bionic, but it is on 16.04

** Description changed:

- In ubuntu 18.04, communitheme is not present in the logitheque. We can't find 
it in the available applications.
- snap search can find it
+ [Impact]
+ Snaps that do not provide icons do not show in GNOME Software. They do show 
on the snapcraft.io website using a default icon.
  
- on the other side, we can notice its presence in the logitheque of
- ubuntu 16.04
+ [Test Case]
+ 1. Open GNOME Software
+ 2. Search for "communitheme"
+ 
+ Expected result:
+ Community Theme snap shows, using an appropriate icon.
+ 
+ Observed result (2 May 2018):
+ Community Theme snap does not show. Note that if the snap is updated in the 
store this behaviour will change - so will have to check another snap.
+ 
+ [Regression Potential]
+ The fix adds the default icon to snaps that do not have one. This will cause 
more snaps to show, which could expose new bugs.

** Summary changed:

- communitheme snap not present in gnome software on bionic, but it is on 16.04
+ Snaps without icons not showing

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

Title:
  Snaps without icons not showing

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Artful:
  Won't Fix
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Snaps that do not provide icons do not show in GNOME Software. They do show 
on the snapcraft.io website using a default icon.

  [Test Case]
  1. Open GNOME Software
  2. Search for "communitheme"

  Expected result:
  Community Theme snap shows, using an appropriate icon.

  Observed result (2 May 2018):
  Community Theme snap does not show. Note that if the snap is updated in the 
store this behaviour will change - so will have to check another snap.

  [Regression Potential]
  The fix adds the default icon to snaps that do not have one. This will cause 
more snaps to show, which could expose new bugs.

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

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

[Desktop-packages] [Bug 1661590] Re: GNOME Software only supports running one application from a snap

I also tried this in a VM which didn't have libreoffice installed - it
launched the welcome window, not libreoffice base. I suspect Simos
hadn't restarted GNOME Software (which is confusing, but the way is
works). Marking as verified.

** Tags removed: verification-failed-xenial

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

Title:
  GNOME Software only supports running one application from a snap

Status in GNOME Software:
  Fix Released
Status in Snappy:
  In Progress
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Artful:
  Won't Fix
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  HOW TO REPRODUCE:

  1. Install LibreOffice snap ('nonfree' tag) from Ubuntu Software.
  2. Click on the 'Launch' button once you have it installed.

  WHAT IS EXPECTED: 
  It should launch the LibreOffice wizard instead of any of Writer, Calc, etc.

  WHAT ACTUALLY HAPPENS: 
  It launches LibreOffice Database.

  
  WHY THIS HAPPENS?

  Ubuntu Software probably picks the first listed command
  (libreoffice.base), as shown in

  $ snap info libreoffice
  name:  libreoffice
  summary:   "LibreOffice is a powerful office suite including word processing 
and creation of spreadsheets, slideshows and databases"
  publisher: canonical
  description: |
LibreOffice is a powerful office suite – its clean interface and
feature-rich tools help you unleash your creativity and enhance your
productivity. LibreOffice includes several applications that make it the 
most
powerful Free and Open Source office suite on the market: Writer (word
processing), Calc (spreadsheets), Impress (presentations), Draw (vector
graphics and flowcharts), Base (databases), and Math (formula editing).
  commands:
- libreoffice.base
- libreoffice.calc
- libreoffice.draw
- libreoffice.impress
- libreoffice
- libreoffice.math
- libreoffice.writer
  tracking:stable
  installed:   5.3.0.3 (17) 374MB -
  refreshed:   2017-02-01 20:51:51 +0200 EET
  channels: 
stable:5.3.0.3 (17) 374MB -
candidate: 5.3.0.3 (17) 374MB -
beta:  5.3.0.3 (17) 374MB -
edge:  5.3.0.3 (17) 374MB -

  
  The order in snapcraft.yaml is different, so probably Snapcraft is changing 
the order (it might assume that 'libreoffice' is 'libreoffice.libreoffice', so 
it puts it further down.

  Here is snapcraft.yaml: https://git.launchpad.net/~bjoern-michaelsen
  /df-libreoffice/+git/libreoffice-snap-
  playground/tree/snapcraft.yaml?h=xenial

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

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

[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

Thanks @pjsingh5000. Your attachment shows the python stack ends at:

# There's still work to do (postinstall).  Let's keep the user
# entertained.
self.start_slideshow()
Gtk.main()

Which agrees with what I see on screen when the bug occurs. It's the
slideshow that never starts (or does, as a blank black/white image).

After that there is no debug info from comment #22. Although my
attachment from comment #15 probably fills in the blanks:
https://launchpadlibrarian.net/368099559/dbg.txt

So it looks like the bug here is entirely in the C code.

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in OEM Priority Project:
  Triaged
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Incomplete
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1751252/+subscriptions

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

[Desktop-packages] [Bug 1665126] Re: Snaps do not show in categories

On a fully updated Xenial VM with -proposed enabled I can see pin-town
in the games section.

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  Snaps do not show in categories

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Artful:
  Won't Fix
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Snaps are not shown in categories.

  [Test Case]
  1. Open GNOME Software
  2. Select "Games" category at the bottom of the page.
  3. Select "All"
  4. Look for pin-town (a snap game)

  Expected result:
  Game is shown

  Observed result:
  Game is not shown.

  [Regression Potential]
  Loading snap information in category screens could trigger new bugs.

  1- I uploaded a snap on myapps.developer.ubuntu.com
  2- I choose Category: Games (note that I cannot choose a sub-category (Kids))
  3- Default type: ? (I choose application, but not sure what it does exactly)
  4- Opening Ubuntu Software on Ubuntu 16.04 I can find and install it when 
using the search bar
  5- BUT my application is not listed in any categories, not even in Games - All
  6- After installing the application, I can see it listed in Games - Kids 
(because the .desktop file have this entry Categories=Game;KidsGame?)

  Looks like only .deb are listed in categories within Ubuntu Software?

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

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

[Desktop-packages] [Bug 1750030] Re: Report fwupd version in user agent

Spoke with fwupd upstream and they have seen requests for this version.

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  Report fwupd version in user agent

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Some firmware updates fail require a recent version of fwupd to work. 
Upstream has requested we update the user agent sent in HTTP requests so that 
they can stop sending firmware to clients that may not work.

  [Test Case]
  Check with the fwupd server that the correct user agent is being sent.

  [Regression Potential]
  Low. The fix is simply to add to the user-agent string used in HTTP requests.

  There are some situations that LVFS shouldn't be offering firmware to certain 
machines.
  Upstream is going to use the user agent for filtering these firmware 
offerings and it would be good if gnome-software can report the user agent.

  The following has been added to the gnome 3.20 tree:
  
https://gitlab.gnome.org/GNOME/gnome-software/commit/9bf4ecef4daa2d31827810d672458768c3c2a2b3

  Can this please be backported to xenial?

  Bionic can already report this as part of 3.26 gnome-software.

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

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

[Desktop-packages] [Bug 1754655] Re: Installing snap from command line confuses GNOME Software

On a fully updated Xenial VM with -proposed enabled moon-buggy shows as
installed in GNOME Software if installed from the command line.

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  Installing snap from command line confuses GNOME Software

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Artful:
  Won't Fix
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Installing snaps from the command line (or any other client) causes the state 
in GNOME Software to wrongly represented.

  [Test Case]
  1. Ensure you don't have moon-buggy installed
  $ sudo snap remove moon-buggy
  2. Start GNOME Software
  3. Install moon-buggy from the command line:
  $ sudo snap install moon-buggy
  4. Search for "moon" in GNOME Software

  Expected result:
  Moon Buggy shows in search results as installed

  Observed result:
  Moon Buggy not returned in search results.

  [Regression Potential]
  Low, we fix a bug where were reading invalid metadata and a check that makes 
stops unexpected (but valid) state notification from the snap plugin.

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

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

[Desktop-packages] [Bug 1750288] Re: Support snap channels

On a fully updated Xenial VM with -proposed enabled I can see channel
information for VLC.

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  Support snap channels

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Artful:
  Won't Fix
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  [Test Case]
  1. Open GNOME Software
  2. Select the VLC snap

  Observed result:
  No channel information is shown.

  Expected result:
  The snap is shown with four (at the time of writing) channels available - 
stable/candidate/beta/edge. You are able to choose a channel at the time of 
install and this installs the appropriate version (can be confirmed with 'snap 
info vlc' on the command line). Once installed the channel can be changed and 
the snap updated (requires clicking install again).

  [Regression Potential]
  Patch is quite large and could cause new bugs.

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

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

[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

This one also started in version 18.04.11:
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15

But this one started in 18.04.3:
https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in OEM Priority Project:
  Triaged
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Incomplete
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1751252/+subscriptions

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

[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

According to this page, the problem possibly started in ubiquity version 
18.04.11:
https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

** Description changed:

  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.
  
  ---
  
  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
+ https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  
  ---
  
  WORKAROUND:
  
  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
  
  ---
  
  Crashed in a VM in the middle of installation. The host is Bionic up to
  date.
  
  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

** Description changed:

  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.
  
  ---
  
  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
+ https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  
  ---
  
  WORKAROUND:
  
  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
  
  ---
  
  Crashed in a VM in the middle of installation. The host is Bionic up to
  date.
  
  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File

[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

2018-05-01 Thread Yuan-Chen Cheng

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Status: New => Triaged

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in OEM Priority Project:
  Triaged
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Incomplete
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1751252/+subscriptions

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

[Desktop-packages] [Bug 1597314] Re: Support for apps which do not automatically connect to slots

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-xenial

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

Title:
  Support for apps which do not automatically connect to slots

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Artful:
  Won't Fix
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  With the addition of new interfaces there are some plugs which do not
  automatically connect and require action from the user in order to be
  connecte.

  As an example, VLC doesn't not automatically connect to the camera
  interface, but users may want to enable this, or maybe they dont.

  Some design considerations:

   * Do we want to ask users to toggle on/off connections they do/do not
  want.  i.e. a list of toggle buttons (what effect would this have on
  the application, would it fail gracefully or just not work (in which
  case the user could be made aware that it won't work without the
  permissions).

  vs

   * Do we want just a single Yes/No question where it's all the
  connections or none.

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

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

[Desktop-packages] [Bug 1763736] Re: communitheme snap not present in gnome software on bionic, but it is on 16.04

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-xenial

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

Title:
  communitheme snap not present in gnome software on bionic, but it is
  on 16.04

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Artful:
  Won't Fix
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  In ubuntu 18.04, communitheme is not present in the logitheque. We can't find 
it in the available applications.
  snap search can find it

  on the other side, we can notice its presence in the logitheque of
  ubuntu 16.04

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

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

[Desktop-packages] [Bug 1763736] Re: communitheme snap not present in gnome software on bionic, but it is on 16.04

** Changed in: gnome-software (Ubuntu Xenial)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  communitheme snap not present in gnome software on bionic, but it is
  on 16.04

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Artful:
  Won't Fix
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  In ubuntu 18.04, communitheme is not present in the logitheque. We can't find 
it in the available applications.
  snap search can find it

  on the other side, we can notice its presence in the logitheque of
  ubuntu 16.04

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

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

[Desktop-packages] [Bug 1597314] Re: Support for apps which do not automatically connect to slots

** Changed in: gnome-software (Ubuntu Artful)
   Status: Triaged => Won't Fix

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

** Changed in: gnome-software (Ubuntu Xenial)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Support for apps which do not automatically connect to slots

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Artful:
  Won't Fix
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  With the addition of new interfaces there are some plugs which do not
  automatically connect and require action from the user in order to be
  connecte.

  As an example, VLC doesn't not automatically connect to the camera
  interface, but users may want to enable this, or maybe they dont.

  Some design considerations:

   * Do we want to ask users to toggle on/off connections they do/do not
  want.  i.e. a list of toggle buttons (what effect would this have on
  the application, would it fail gracefully or just not work (in which
  case the user could be made aware that it won't work without the
  permissions).

  vs

   * Do we want just a single Yes/No question where it's all the
  connections or none.

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

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

[Desktop-packages] [Bug 1768388] [NEW] "Open Tilix Here" still in context menu after uninstalling Tilix

2018-05-01 Thread Kyle Piira

Public bug reported:

On Ubuntu Budgie there is an option in the context menu in GNOME Files
to "Open Tilix Here" which will open that directory in the Tilix
terminal emulator. However, after uninstalling Tilix the option still
appears but now does nothing (since its trying to open a program that
doesn't exist on the system anymore). There should be a check somewhere
to verify that Tilix is actually installed before showing the option.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-terminal 3.28.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Tue May  1 22:07:57 2018
ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
InstallationDate: Installed on 2018-05-01 (0 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: budgie-desktop (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

** Package changed: gnome-terminal (Ubuntu) => budgie-desktop (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/1768388

Title:
  "Open Tilix Here" still in context menu after uninstalling Tilix

Status in budgie-desktop package in Ubuntu:
  New

Bug description:
  On Ubuntu Budgie there is an option in the context menu in GNOME Files
  to "Open Tilix Here" which will open that directory in the Tilix
  terminal emulator. However, after uninstalling Tilix the option still
  appears but now does nothing (since its trying to open a program that
  doesn't exist on the system anymore). There should be a check
  somewhere to verify that Tilix is actually installed before showing
  the option.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue May  1 22:07:57 2018
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767157] Re: Duplicate Folders

2018-05-01 Thread Diogo Filho de Morais

I don't now. But this get create in a fill times.

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

Title:
  Duplicate Folders

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I use Ubuntu in Brazilian Portuguese and nautillus usually creates
  folders with English names. I delete the folders and they are re-
  created some time later.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 26 13:38:00 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'201'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x548+666+205'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
  InstallationDate: Installed on 2018-04-20 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1768364] Re: Combo boxes close immediately after opening

Here's an example of it happening randomly in gnome-control-center.

** Attachment added: "combo box in gnome-control-center"
   
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1768364/+attachment/5131731/+files/Screencast%20from%2005-01-2018%2007%3A07%3A24%20PM.webm

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

Title:
  Combo boxes close immediately after opening

Status in gtk+3.0 package in Ubuntu:
  New
Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Sometimes when a select box is clicked, it opens and then closes
  almost immediately.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 14:39:28 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-27 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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/gtk+3.0/+bug/1768364/+subscriptions

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

[Desktop-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland

Bug 1767918 indicates this bug is not fixed, and still occurring in
18.04.


** Tags added: fall-through

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

Title:
  Input falls through to gdm3 and terminates the session on Ctrl+C after
  udevadm trigger is executed under wayland

Status in Snappy:
  Won't Fix
Status in console-setup package in Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in console-setup source package in Trusty:
  New
Status in gdm3 source package in Trusty:
  New
Status in gnome-shell source package in Trusty:
  New
Status in mutter source package in Trusty:
  New
Status in systemd source package in Trusty:
  New
Status in console-setup source package in Xenial:
  New
Status in gdm3 source package in Xenial:
  New
Status in gnome-shell source package in Xenial:
  New
Status in mutter source package in Xenial:
  New
Status in systemd source package in Xenial:
  New

Bug description:
  = Test Cases =

  Test Case 1:
  - Login under Wayland (session Ubuntu)
  - Open a terminal
  - snap install gimp
  - Wait until installation finishes successfully
  - In the terminal window press CTRL+C

  Result:
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  Test Case 2:
  - Login under Wayland (session Ubuntu)
  - Open a terminal and type the following command:
    $ sudo udevadm trigger
  - In the terminal window press CTRL+C

  Result
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  = Original Description =

  Multiple times a day I find myself without a session after hitting
  Ctrl+C in a terminal, it seems the input falls through the
  Ubuntu/GNOME session and to gdm, which itself decides to terminate.

  Even worse, when this happens, you can briefly see your login password
  in plaintext in the virtual terminal. You can see the password however
  long you want if you stop the gdm service when this happens.

  I don't have a good way to reproduce, but it seems locking the session
  with a keyboard shortcut, subsequently unlocking it, maybe suspending,
  at some point brings this behaviour into the picture, until the
  session dies with a Ctrl+C.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug 14 15:54:34 2017
  InstallationDate: Installed on 2016-05-06 (464 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago)

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

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

[Desktop-packages] [Bug 1759300] Re: Gnome Shell: Touchpad right click (bottom right) area does not work

I think we should improve this in 18.10 by moving the setting from
gnome-tweaks into gnome-control-center. That way most users will
actually find it, and be able to resolve the issue themselves.

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

Title:
  Gnome Shell: Touchpad right click (bottom right) area does not work

Status in gsettings-desktop-schemas package in Ubuntu:
  Invalid

Bug description:
  The right (second) touchpad click does not work.
  It ceased to work about three months ago.
  ubuntu 18,04 aser ex2519

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

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

[Desktop-packages] [Bug 1768343] Re: Not detect secondary button of notebook touchpad

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

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


** Package changed: libinput (Ubuntu) => gsettings-desktop-schemas
(Ubuntu)

** This bug has been marked a duplicate of bug 1759300
   Gnome Shell: Touchpad right click (bottom right) area does not work

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

Title:
  Not detect secondary button of notebook touchpad

Status in gsettings-desktop-schemas package in Ubuntu:
  New

Bug description:
  When I press the secondary touchpad button, Ubuntu takes it as the primary 
one. This error does not happen with a usb mouse.
  Acer Aspire 3 7100U

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 17:02:59 2018
  ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-mouse
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768259] Re: gnome-shell segfault when locking/unlocking screen

Yeah, please don't attach it here. Instead please:

1. Apply the workaround from bug 994921 first.

2. Run: ubuntu-bug YOURFILE.crash

3. Tell us here the new bug ID that is created.

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

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

Title:
  gnome-shell segfault when locking/unlocking screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  i have a fresh setup with threadripper and rxvega64. 
  Installed 17.10 and latest amd-gpu driver. 

  
  Journalctl trace : 

  
  everything runs fine except when i lock the screen, 90% of the time the 
session crash and is restarted. 
  mai 01 14:39:32 macronetmonk gnome-control-c[97659]: Language en_US.UTF-8 not 
installed, trying to install it
  mai 01 14:39:32 macronetmonk dbus[746]: [system] Successfully activated 
service 'org.freedesktop.locale1'
  mai 01 14:39:32 macronetmonk systemd[1]: Started Locale Service.
  mai 01 14:39:33 macronetmonk dbus[746]: [system] Activating service 
name='com.ubuntu.WhoopsiePreferences' (using servicehelper)
  mai 01 14:39:34 macronetmonk dbus[746]: [system] Successfully activated 
service 'com.ubuntu.WhoopsiePreferences'
  mai 01 14:39:34 macronetmonk com.ubuntu.WhoopsiePreferences[746]: Acquired 
the name: com.ubuntu.WhoopsiePreferences
  mai 01 14:39:34 macronetmonk dbus[746]: [system] Activating via systemd: 
service name='org.freedesktop.GeoClue2' unit='geoclue.service'
  mai 01 14:39:34 macronetmonk systemd[1]: Starting Location Lookup Service...
  mai 01 14:39:34 macronetmonk gnome-control-c[97659]: Failed fetch permissions 
from flatpak permission store: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.impl.portal.PermissionStore was not provided by any .service 
files
  mai 01 14:39:34 macronetmonk dbus[746]: [system] Successfully activated 
service 'org.freedesktop.GeoClue2'
  mai 01 14:39:34 macronetmonk systemd[1]: Started Location Lookup Service.
  mai 01 14:40:03 macronetmonk gnome-control-c[97659]: No devices in the tree, 
so cannot set the active output
  mai 01 14:40:13 macronetmonk dbus[746]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service'
  mai 01 14:40:13 macronetmonk systemd[1]: Starting Hostname Service...
  mai 01 14:40:13 macronetmonk dbus[746]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
  mai 01 14:40:13 macronetmonk systemd[1]: Started Hostname Service.
  mai 01 14:40:13 macronetmonk gsd-power[1624]: 
gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed
  mai 01 14:40:56 macronetmonk eog[97831]: Failed to open file 
'/home/plonky/.cache/thumbnails/normal/ee570bc7eac14baac4afd859d2a40e72.png': 
No such file or directory
  mai 01 14:41:08 macronetmonk eog[97843]: Failed to open file 
'/home/plonky/.cache/thumbnails/normal/e19a612870f16d4d6ce18ccc20d0f7b3.png': 
No such file or directory
  mai 01 14:41:20 macronetmonk nautilus[88671]: Called "net usershare info" but 
it failed: Failed to execute child process “net” (No such file or directory)
  mai 01 14:41:23 macronetmonk eog[97899]: Failed to open file 
'/home/plonky/.cache/thumbnails/normal/65711fd8ad02ac5c2aa10fea7987c2d9.png': 
No such file or directory
  mai 01 14:41:26 macronetmonk eog[97899]: Failed to open file 
'/home/plonky/.cache/thumbnails/normal/50f1c553ce3970b3fc10c1336081856a.png': 
No such file or directory
  mai 01 14:41:28 macronetmonk eog[97899]: Failed to open file 
'/home/plonky/.cache/thumbnails/normal/145ada7cc03103493699e996d1ed6056.png': 
No such file or directory
  mai 01 14:41:29 macronetmonk eog[97899]: Failed to open file 
'/home/plonky/.cache/thumbnails/normal/1bf667bc21becf85d01b6a2dc7149007.png': 
No such file or directory
  mai 01 14:41:30 macronetmonk eog[97899]: Failed to open file 
'/home/plonky/.cache/thumbnails/normal/6064c8b11c71dbb99690bc88421605fb.png': 
No such file or directory
  mai 01 14:41:32 macronetmonk eog[97899]: Failed to open file 
'/home/plonky/.cache/thumbnails/normal/fb2a5eefbc24963549272f04232270cf.png': 
No such file or directory
  mai 01 14:41:33 macronetmonk eog[97899]: Failed to open file 
'/home/plonky/.cache/thumbnails/normal/7da37c8312315e8fcfff8f18efdc45f1.png': 
No such file or directory
  mai 01 14:41:35 macronetmonk eog[97899]: Failed to open file 
'/home/plonky/.cache/thumbnails/normal/dbe454b76d4d6152831e48ee8e722895.png': 
No such file or directory
  mai 01 14:41:36 macronetmonk eog[97899]: Failed to open file 
'/home/plonky/.cache/thumbnails/normal/797a3609ddcb6e2965bfd5dedd46289f.png': 
No such file or directory
  mai 01 14:41:37 macronetmonk eog[97899]: Failed to open file 
'/home/plonky/.cache/thumbnails/normal/6c2c8973e707a2bbadf9d5d31f2c33c8.png': 
No such file or directory
  mai 01 14:42:42 macronetmonk

[Desktop-packages] [Bug 1768364] Re: Combo boxes close immediately after opening

@Daniel, this is not just Rhythmbox. It's across many interfaces. It
just happened to be on Rhythmbox now when it occurred multiple times.

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

Title:
  Combo boxes close immediately after opening

Status in gtk+3.0 package in Ubuntu:
  New
Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Sometimes when a select box is clicked, it opens and then closes
  almost immediately.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 14:39:28 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-27 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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/gtk+3.0/+bug/1768364/+subscriptions

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

[Desktop-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland

** Information type changed from Public to Public Security

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

Title:
  Input falls through to gdm3 and terminates the session on Ctrl+C after
  udevadm trigger is executed under wayland

Status in Snappy:
  Won't Fix
Status in console-setup package in Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in console-setup source package in Trusty:
  New
Status in gdm3 source package in Trusty:
  New
Status in gnome-shell source package in Trusty:
  New
Status in mutter source package in Trusty:
  New
Status in systemd source package in Trusty:
  New
Status in console-setup source package in Xenial:
  New
Status in gdm3 source package in Xenial:
  New
Status in gnome-shell source package in Xenial:
  New
Status in mutter source package in Xenial:
  New
Status in systemd source package in Xenial:
  New

Bug description:
  = Test Cases =

  Test Case 1:
  - Login under Wayland (session Ubuntu)
  - Open a terminal
  - snap install gimp
  - Wait until installation finishes successfully
  - In the terminal window press CTRL+C

  Result:
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  Test Case 2:
  - Login under Wayland (session Ubuntu)
  - Open a terminal and type the following command:
    $ sudo udevadm trigger
  - In the terminal window press CTRL+C

  Result
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  = Original Description =

  Multiple times a day I find myself without a session after hitting
  Ctrl+C in a terminal, it seems the input falls through the
  Ubuntu/GNOME session and to gdm, which itself decides to terminate.

  Even worse, when this happens, you can briefly see your login password
  in plaintext in the virtual terminal. You can see the password however
  long you want if you stop the gdm service when this happens.

  I don't have a good way to reproduce, but it seems locking the session
  with a keyboard shortcut, subsequently unlocking it, maybe suspending,
  at some point brings this behaviour into the picture, until the
  session dies with a Ctrl+C.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug 14 15:54:34 2017
  InstallationDate: Installed on 2016-05-06 (464 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago)

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

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

[Desktop-packages] [Bug 1768364] Re: Combo boxes close immediately after opening

** Summary changed:

- Select boxes close immediately after opening
+ Combo boxes close immediately after opening

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

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Combo boxes close immediately after opening

Status in gtk+3.0 package in Ubuntu:
  New
Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Sometimes when a select box is clicked, it opens and then closes
  almost immediately.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 14:39:28 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-27 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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/gtk+3.0/+bug/1768364/+subscriptions

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

[Desktop-packages] [Bug 1768343] [NEW] Not detect secondary button of notebook touchpad

You have been subscribed to a public bug:

When I press the secondary touchpad button, Ubuntu takes it as the primary one. 
This error does not happen with a usb mouse.
Acer Aspire 3 7100U

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-settings-daemon 3.28.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue May  1 17:02:59 2018
ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-mouse
InstallationDate: Installed on 2018-05-01 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gsettings-desktop-schemas (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic
-- 
Not detect secondary button of notebook touchpad
https://bugs.launchpad.net/bugs/1768343
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gsettings-desktop-schemas 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 1768387] [NEW] Can't locate File/Find.pm in @INC

2018-05-01 Thread Seth Arnold

Public bug reported:

I saw this error message during the 16.04 LTS -> 18.04 LTS upgrade:

Found memtest86+ image: /boot/memtest86+.bin
done
Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Can't locate File/Find.pm in @INC (you may need to install the File::Find 
module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.1 
/usr/local/share/perl/5.26.1 /usr/lib/x86_64-linux-gnu/perl5/5.26 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at -e line 2.
BEGIN failed--compilation aborted at -e line 2.
Processing triggers for libc-bin (2.27-3ubuntu1) ...


Thanks

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bamfdaemon 0.5.3+18.04.20180207.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
Uname: Linux 4.4.0-119-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity
Date: Tue May  1 18:42:48 2018
InstallationDate: Installed on 2012-10-18 (2021 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
SourcePackage: bamf
UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Can't locate File/Find.pm in @INC

Status in bamf package in Ubuntu:
  New

Bug description:
  I saw this error message during the 16.04 LTS -> 18.04 LTS upgrade:

  Found memtest86+ image: /boot/memtest86+.bin
  done
  Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Can't locate File/Find.pm in @INC (you may need to install the File::Find 
module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.1 
/usr/local/share/perl/5.26.1 /usr/lib/x86_64-linux-gnu/perl5/5.26 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at -e line 2.
  BEGIN failed--compilation aborted at -e line 2.
  Processing triggers for libc-bin (2.27-3ubuntu1) ...

  
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bamfdaemon 0.5.3+18.04.20180207.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May  1 18:42:48 2018
  InstallationDate: Installed on 2012-10-18 (2021 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  SourcePackage: bamf
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

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

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

[Desktop-packages] [Bug 1735986] Re: Unable to set different scale correctly on different monitors

** Description changed:

+ Upstream: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/17
+ 
  I have a system that was upgraded from 16.04 -> 16.10 -> 17.04 -> 17.10. So 
now running on 17.10.
  I upgraded to 17.10 because I hoped for better HiDPI scaling support.
  
  My laptop is Dell Precision 5520 with 4k 3840x2160 15" screen, with
  Intel graphics (it has nvidia too, but disabled).
  
  Additionally, I have an external Dell U3011 2560x1600 30" display
  connected to it.
  
- 
- When I logged into graphical session (selected the default Ubuntu session), I 
confirmed wayland is running by checking loginctl:
+ When I logged into graphical session (selected the default Ubuntu
+ session), I confirmed wayland is running by checking loginctl:
  
  loginctl show-session 2 -p Type
  Type=wayland
  
  With external display connected, display settings show that the high DPI
  laptop screen got scaling set automatically to 200%, and the external
  low DPI display got scaling set to 100%. So far, looks good - automatic
  detection of hi dpi screens did the right thing.
  
  The built-in Ubuntu applications like terminal, file browser or setting
  window work fine. When I start e.g. the terminal, it appears first on
  the laptop screen - it is scaled properly, then I drag it to the
  external screen and once I release the mouse button, the window shrinks
  to 2x smaller, so it adapts to lower DPI of that screen. Everything is
  sharp and crispy and the sizes are ok.
- 
  
  Problems:
  
  * Firefox, Chrome, Chromium, Intellij IDEA all do not scale correctly on
  the external screen. Everything is twice too big. When started, they
  appear first on the built-in hiDPI screen with the correct size, but
  after dragging to the external screen, they remain scaled by 200%.
  
  * When I enabled dock to be displayed on all screens, the dock icons are
  twice too big on the external screen. So, 200% scaling seems to be
  applied to the dock on both screens.
  
  * Sometimes the mouse pointer is twice as large. Sometimes it is twice
  too small. I didn't figure out yet when it happens. Sometimes it is only
  twice too large when over the desktop background, but ok when over an
  application window. This is a very minor issue, but looks funny.
  
  -
  What I tried so far:
- 
  
  Resetting dconf to factory settings with:
  dconf reset -f /org/gnome/
  did not help.
  
  Then I tried enabling experimental fractional scaling, with 200% / 100%
  scales set (I do not really need fractional scaling, but I hoped it
  changes how things are rendered and where scaling is applied). This
  actually helped for both scaling issues - including the dock scaling
  problem. Windows get even properly scaled in the *middle of dragging*
  between displays. Everything is the right size with this setting on.
  Really cool.
  
  Unfortunately now the image on the builtin display for the non-native
  applications like Firefox, Chrome or Idea is severely blurred. And it is
  blurred even if I disconnect the external display. It looks as if it
  rendered these apps at half the resolution (I noticed xrandr shows
  1920x1080 for that screen, but ubuntu display settings window shows
  3840x2160) and then upscaled twice the bitmap to reach higher 4k real
  screen resolution. The blur does not happen for native Ubuntu apps like
  terminal.
  
  Unfortunately the blurring effect is much stronger than if I just
  manually force the builtin screen to 1920x1080. In this case everything
  is a bit lower resolution, but still sharp enough.
  
  Therefore so far, Ubuntu 17.10 and Wayland did not improve hi dpi support for 
me at all, despite some rumours it should have. I still have to switch to lower 
resolution on the builtin display to get everything crisp and the right size.
- --- 
+ ---
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
-  # This is a distribution channel descriptor
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-somerville-xenial-amd64-20160624-2
+  # This is a distribution channel descriptor
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-xenial-amd64-20160624-2
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-04-12 (234 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Package: gnome-control-center 1:3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=pl_PL.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=pl_PL.UTF-8
+  SHELL=/bin/bash
  Tags:  artful wayland-session
  Uname: Linux 4.14.3-041403-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev

[Desktop-packages] [Bug 1741045] Re: Change the default resample-method to speex-float-10 in daemon.conf

That seems to show speex-float-1 performing quite well:
https://imgur.com/a/jtIEj


** Summary changed:

- Change the default resample-method to speex-float-10 in daemon.conf
+ Change the default resample-method to speex-float-N (N > 1) in daemon.conf

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

Title:
  Change the default resample-method to speex-float-N (N > 1) in
  daemon.conf

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I suggest changing the default resample-method to speex-float-10,
  instead of speex-float-1, which is the current default now, in
  /etc/pulse/daemon.conf.

  It would look like this in daemon.conf:
  resample-method = speex-float-10

  I have always done that since at least 12.04 LTS. I was not satisfied
  with the sound quality in Ubuntu compared to Windows, so I changed the
  resample-method.

  In my day-to-day usage, it gives better sound quality without
  sacrificing CPU power.

  I have not tried other resample methods. Maybe there are better
  options I don't know about.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amr1696 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  3 14:37:25 2018
  InstallationDate: Installed on 2017-10-02 (92 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-10-05T12:39:48.718018

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

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

[Desktop-packages] [Bug 890867] Re: pulseaudio crashed with SIGABRT in pa_memimport_free()

Taras: Please report your crash in a new bug.

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

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

Title:
  pulseaudio crashed with SIGABRT in pa_memimport_free()

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Sound crashed after changing the volume, but seems random, hasn't done
  it again. Might be related to instalation of pulseaudio-equalizer,
  even if I do notice the sound widget/icon (gnome-shell) restarting at
  times.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: pulseaudio 1:1.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dramalho   5025 F pulseaudio
   /dev/snd/controlC0:  dramalho   5025 F pulseaudio
   /dev/snd/pcmC0D0p:   dramalho   5025 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd742 irq 47'
 Mixer name : 'IDT 92HD75B3X5'
 Components : 'HDA:111d7603,103c172b,00100202 
HDA:11c11040,103c3066,00100200'
 Controls  : 15
 Simple ctrls  : 10
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xd300 irq 16'
 Mixer name : 'Nvidia GPU 0b HDMI/DP'
 Components : 'HDA:10de000b,10de0101,00100100'
 Controls  : 16
 Simple ctrls  : 4
  Date: Tue Nov 15 18:23:52 2011
  ExecutablePath: /usr/bin/pulseaudio
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libpulsecommon-1.0.so
   pa_memimport_free () from /usr/lib/x86_64-linux-gnu/libpulsecommon-1.0.so
   pa_pstream_unlink () from /usr/lib/x86_64-linux-gnu/libpulsecommon-1.0.so
   ?? () from /usr/lib/pulse-1.0/modules/libprotocol-native.so
   ?? () from /usr/lib/pulse-1.0/modules/libprotocol-native.so
  Title: pulseaudio crashed with SIGABRT in pa_memimport_free()
  UpgradeStatus: Upgraded to oneiric on 2011-09-01 (74 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare sudo
  XsessionErrors:
   (gnome-shell:2192): Clutter-WARNING **: Attempting to add actor of type 
'ShellGenericContainer' to a container of type 'StBoxLayout', but the actor has 
already a parent of type 'StBoxLayout'.
   (dropbox:2299): Gdk-CRITICAL **: 
IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion 
`private->update_and_descendants_freeze_count > 0' failed
   (process:4796): Gtk-WARNING **: Locale not supported by C library.
  dmi.bios.date: 03/09/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CCU Ver. F.12
  dmi.board.name: 172B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 30.31
  dmi.chassis.asset.tag: CZC0126G5J
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CCUVer.F.12:bd03/09/2011:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172B:rvrKBCVersion30.31:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8440p
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-01 Thread Bernadette Addison

I agree! This issue is definitely NOT FIXED!

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-01 Thread Bernadette Addison

I agree! This issue is definitely NOT FIXED!

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Desktop-packages] [Bug 1768178] Re: color scheme Solarized Dark is incorrect

2018-05-01 Thread popstas

Are you mean new abstraction, third place, preset for background,
palette and other? I think it will more intuitive if all settings will
be hidden to "Advanced settings" section.

Jetbrains implemented something like this in their IDE's -
https://i.imgur.com/ig89M4G.png

More simple way: add link to documentation describing complex scheme
details.

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

Title:
  color scheme Solarized Dark is incorrect

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Original Solarized Dark looks different. Thereis the pull request on
  Github that fixes that - https://github.com/GNOME/gnome-
  terminal/pull/6

  I'm not author of patch and don't checked it, but there is project
  that change color scheme to correct, it described here -
  https://github.com/Anthony25/gnome-terminal-colors-
  solarized/tree/master/colors/dark

  Here is built-in palette collected with gsettings get:
  ['#2E3436', 
  '#CC', 
  '#4E9A06', 
  '#C4A000', 
  '#3465A4', 
  '#75507B', 
  '#06989A', 
  '#D3D7CF', 
  '#555753', 
  '#EF2929', 
  '#8AE234', 
  '#FCE94F', 
  '#729FCF', 
  '#AD7FA8', 
  '#34E2E2', 
  '#EC']

  Here is correct palette:
  ['#070736364242', 
  '#DCDC32322F2F', 
  '#8585', 
  '#B5B58989', 
  '#26268B8BD2D2', 
  '#D3D336368282', 
  '#2A2AA1A19898', 
  '#E8E8D5D5', 
  '#2B2B3636', 
  '#CBCB4B4B1616', 
  '#58586E6E7575', 
  '#65657B7B8383', 
  '#838394949696', 
  '#6C6C7171C4C4', 
  '#9393A1A1A1A1', 
  '#FDFDF6F6E3E3']

  I asked the question about long codes - https://github.com/Anthony25
  /gnome-terminal-colors-solarized/issues/76, but anyway it matches
  original scheme perfectly.

  I created bug at launchpad because Gnome restricted creating bugs for
  non-gnome developers in their guide
  https://wiki.gnome.org/Apps/Terminal/ReportingBugs and point to
  distribution bug tracker.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 07:49:18 2018
  InstallationDate: Installed on 2018-04-29 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

2018-05-01 Thread PJSingh5000

Here is the backtrace (bt f) with debug symbols.

I still have gdb open, if anyone needs me to do anything else?

** Attachment added: "gdb backtrace (bt f) with debug symbols"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1751252/+attachment/5131712/+files/gdb_output_with_debug_symbols.txt

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in glib2.0 package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Incomplete
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1767544] Re: While running the Orca screen reader, system hangs while gnome-control-center is open

2018-05-01 Thread Jeremy Lincicome

Here is an audio demo of what happens.

** Attachment added: "Audio demo of what happens in gnome-control-center while 
using Orca in Ubuntu-18.04"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1767544/+attachment/5131695/+files/Gnome-control-center.ogg

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

Title:
  While running the Orca screen reader, system hangs while gnome-
  control-center is open

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

Bug description:
  When gnome-control-center loads, my computer becomes inaccessible. To get 
Orca working again, I have to force close the app with Alt+f4. There are parts 
of the control center that I can use, such as the sound and VPN settings, only 
if I invoke them from the dash. If I invoke Wi-Fi from the dash or top bar, it 
is inaccessible.
  Steps to reproduce:
  1. Launch Orca by pressing Alt+Super+s.
  2. Press the super key, and type "settings" into the search box.
  3. After the settings screen loads, try to move around using Tab and 
Shift+Tab. Also try to move using Orca's flat review feature.
  The commands for using flat review can be found at:
  https://help.gnome.org/users/orca/stable/commands_flat_review.html.en
  On a desktop, the Orca modifier is the insert key. On a laptop, the Orca 
modifier is the Caps lock key, if laptop layout is set in Orca's preferences.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 15:44:35 2018
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1748611] Re: Desktop symbols disappear after changing symbol size in nautilus

2018-05-01 Thread Simon P.

This bug is still present in 18.04...

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

Title:
  Desktop symbols disappear after changing symbol size in nautilus

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Problem: When changing the size of folder symbols in the nautilus file
  browser, the symbol size for desktop symbols is also changed. That
  might result in the (temporary) disappearing of desktop symbols.

  How to reproduce the bug: Place some symbols on the right edge of the
  desktop. Open nautilus, increase the size of symbols. The symbol size
  for the desktop and the symbol grid size are also affected by that
  change, symbols placed at the edge will disappear.

  What I expect to happen: Changing the symbol size in nautilus should
  not affect the desktop symbol size/symbol grid size.

  What actually happens: Changing the symbol size in nautilus will
  change the desktop symbol size/ grid size, symbols on the desktop
  might disappear.

  Ubuntu version: 17.10
  ubuntu-session version: 3.26.1-0ubuntu6

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

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

[Desktop-packages] [Bug 1753120] Re: package libgtkmm-2.4-doc (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README', which is also in package

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

** Changed in: gtkmm2.4 (Ubuntu)
   Status: New => Confirmed

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

Title:
  package libgtkmm-2.4-doc (not installed) failed to install/upgrade:
  trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README',
  which is also in package libgtkmm-2.4-dev:amd64 1:2.24.5-2

Status in gtkmm2.4 package in Ubuntu:
  Confirmed

Bug description:
  E: /var/cache/apt/archives/libgtkmm-2.4-doc_1%3a2.24.5-2_all.deb:
  trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README',
  which is also in package libgtkmm-2.4-dev:amd64 1:2.24.5-2

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgtkmm-2.4-doc (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-10.11-lowlatency 4.15.3
  Uname: Linux 4.15.0-10-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sat Mar  3 10:59:55 2018
  DuplicateSignature:
   package:libgtkmm-2.4-doc:(not installed)
   Unpacking libgtkmm-2.4-doc (1:2.24.5-2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-ebi0hY/58-libgtkmm-2.4-doc_1%3a2.24.5-2_all.deb 
(--unpack):
trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README', 
which is also in package libgtkmm-2.4-dev:amd64 1:2.24.5-2
  ErrorMessage: trying to overwrite 
'/usr/share/doc/libgtkmm-2.4-dev/examples/README', which is also in package 
libgtkmm-2.4-dev:amd64 1:2.24.5-2
  InstallationDate: Installed on 2018-03-02 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302)
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu2
  SourcePackage: gtkmm2.4
  Title: package libgtkmm-2.4-doc (not installed) failed to install/upgrade: 
trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README', which is 
also in package libgtkmm-2.4-dev:amd64 1:2.24.5-2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtkmm2.4/+bug/1753120/+subscriptions

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

[Desktop-packages] [Bug 1767542] Re: Turning off WiFi enables Airplane mode

Also, isn't importance "low" a little understated for such a grave
issue? This does not look like production ready quality.

** Changed in: gnome-control-center
 Remote watch: GNOME Bug Tracker #748476 => GNOME Bug Tracker #59

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

Title:
  Turning off WiFi enables Airplane mode

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

Bug description:
  Turning off the WiFi from the top right control enables Airplane mode
  (see screenshots). Also after turning off airplane mode, the Wi-Fi is
  not turned back on, rather the Bluetooth is.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 17:46:34 2018
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767542] Re: Turning off WiFi enables Airplane mode

Yes, this looks more like it. The bug is 13 months old though and still
in "new" status. That's sad.

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

Title:
  Turning off WiFi enables Airplane mode

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

Bug description:
  Turning off the WiFi from the top right control enables Airplane mode
  (see screenshots). Also after turning off airplane mode, the Wi-Fi is
  not turned back on, rather the Bluetooth is.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 17:46:34 2018
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768364] [NEW] Select boxes close immediately after opening

Public bug reported:

Sometimes when a select box is clicked, it opens and then closes almost
immediately.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue May  1 14:39:28 2018
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'app-picker-view' b'uint32 1'
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2018-04-27 (4 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "screencast of the problem"
   
https://bugs.launchpad.net/bugs/1768364/+attachment/5131685/+files/Screencast%20from%2005-01-2018%2002%3A37%3A17%20PM.webm

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

Title:
  Select boxes close immediately after opening

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Sometimes when a select box is clicked, it opens and then closes
  almost immediately.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 14:39:28 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-27 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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/1768364/+subscriptions

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

[Desktop-packages] [Bug 1767536] Re: Accessing the WIFI section of the "Settings" window causes massive freezes

well, if you can't install the dbg packages it's less useful but still
better than nothing

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

Title:
  Accessing the WIFI section of the "Settings" window causes massive
  freezes

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

Bug description:
  Accessing the Wi-Fi section of the "Settings" window causes huge, 5-20
  seconds freezes of the window. Nothing else seems to freeze. One
  core's utilization goes up during the freeze.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 17:23:34 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768343] Re: Not detect secondary button of notebook touchpad

** Package changed: gnome-settings-daemon (Ubuntu) => libinput (Ubuntu)

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

Title:
  Not detect secondary button of notebook touchpad

Status in libinput package in Ubuntu:
  New

Bug description:
  When I press the secondary touchpad button, Ubuntu takes it as the primary 
one. This error does not happen with a usb mouse.
  Acer Aspire 3 7100U

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 17:02:59 2018
  ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-mouse
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767542] Re: Turning off WiFi enables Airplane mode

https://bugzilla.gnome.org/show_bug.cgi?id=59 then

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Triaged

** Bug watch added: GNOME Bug Tracker #59
   https://bugzilla.gnome.org/show_bug.cgi?id=59

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

Title:
  Turning off WiFi enables Airplane mode

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

Bug description:
  Turning off the WiFi from the top right control enables Airplane mode
  (see screenshots). Also after turning off airplane mode, the Wi-Fi is
  not turned back on, rather the Bluetooth is.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 17:46:34 2018
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767544] Re: While running the Orca screen reader, system hangs while gnome-control-center is open

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

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Triaged

** Changed in: gnome-control-center (Ubuntu)
   Status: Triaged => New

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

Title:
  While running the Orca screen reader, system hangs while gnome-
  control-center is open

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

Bug description:
  When gnome-control-center loads, my computer becomes inaccessible. To get 
Orca working again, I have to force close the app with Alt+f4. There are parts 
of the control center that I can use, such as the sound and VPN settings, only 
if I invoke them from the dash. If I invoke Wi-Fi from the dash or top bar, it 
is inaccessible.
  Steps to reproduce:
  1. Launch Orca by pressing Alt+Super+s.
  2. Press the super key, and type "settings" into the search box.
  3. After the settings screen loads, try to move around using Tab and 
Shift+Tab. Also try to move using Orca's flat review feature.
  The commands for using flat review can be found at:
  https://help.gnome.org/users/orca/stable/commands_flat_review.html.en
  On a desktop, the Orca modifier is the insert key. On a laptop, the Orca 
modifier is the Caps lock key, if laptop layout is set in Orca's preferences.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 15:44:35 2018
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768332] Re: crash & doesen t start

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

** Changed in: rhythmbox (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  crash & doesen t start

Status in rhythmbox package in Ubuntu:
  Invalid

Bug description:
  The program does not open unless it is set as the default device for
  opening the mp3 tracks, but it does not play any music, and the Ubuntu
  error message wizard logs on

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

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

[Desktop-packages] [Bug 1768176] Re: Unable to suspend computer

2018-05-01 Thread Eduardo Aguilar

Hi Tom-lorinthe... I'm not so sure what is your suggestion. I should add 
"acpi_rev_override=1" after GRUB_CMDLINE_LINUX_DEFAULT="splash 
acpi_rev_override=1 nouveau.runpm=0"??
In my case, when I run that command that line is commented as 
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash". I am running Ubuntu 18.04, fresh 
install from April 26th on a Lenovo e11.
Everything works fine but the suspend feature; not with all windows closed, not 
at all, period.
Some guidance would be grateful.
Cheers.

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

Title:
  Unable to suspend computer

Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04 fails to suspend if a window is open - it merely goes to
  the lock screen with a message that 1 process could not be stopped.
  [Side note - this behaviour disregards that I have the lock  screen
  disabled in Privacy settings.]

  I closed Chrome and a terminal window to reveal the second behaviour:
  When suspend is selected (through power icon) the computer power
  momentarily stops (under a second) then the computer returns to the
  lock screen after a pause.

  Suspend worked very consistently on this hardware on 16.04 LTS in all
  situations. No changes have been made to the hardware since (long
  before) upgrade to 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screensaver 3.6.1-8ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 22:55:45 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1761606] Re: Two Wi-Fi network applets appear after logging back into live-usb Lubuntu 18.04 session.

2018-05-01 Thread aaronfranke

Occurs for me on live session and installed versions of release Xubuntu
18.04 Bionic Beaver. Two network icons are displayed, both functional.

System specs: TL-WDN4800 Wi-Fi card, i5-6600k, 16 GB RAM, GTX 770.

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

Title:
  Two Wi-Fi network applets appear after logging back into live-usb
  Lubuntu 18.04 session.

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

Bug description:
  Lubuntu 18.04 ISO version: 20180404
  network-manager-applet version: 1.8.10-2ubuntu1
  After logging into my Wi-Fi network then logging out then logging back into 
the Live-USB session Two Wi-Fi network applets appeared where One would be the 
expected outcome.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-gnome 1.8.10-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.392
  CurrentDesktop: LXDE
  Date: Thu Apr  5 21:06:24 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.166 metric 
600
  LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Zero-Daya2f10fa9-551c-4a4f-93ba-5fe6c22c4134  wifi  
1522962221  Thu Apr  5 21:03:41 2018  yes  0 no 
   /org/freedesktop/NetworkManager/Settings/2  yes wlp3s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/2  --
   Wired connection 1  472b45a7-c95b-3638-b452-3f6720688df8  ethernet  
1522961321  Thu Apr  5 20:48:41 2018  yes  4294966297no 
   /org/freedesktop/NetworkManager/Settings/1  no  --  -- --
  --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Zero-Daya2f10fa9-551c-4a4f-93ba-5fe6c22c4134  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1767536] Re: Accessing the WIFI section of the "Settings" window causes massive freezes

As for the backtrace, will not do it on a production system, as it seems
to require quite a few dbg packages.

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

Title:
  Accessing the WIFI section of the "Settings" window causes massive
  freezes

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

Bug description:
  Accessing the Wi-Fi section of the "Settings" window causes huge, 5-20
  seconds freezes of the window. Nothing else seems to freeze. One
  core's utilization goes up during the freeze.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 17:23:34 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

I performed another upgrade with the apt-clone file from this bug and
editing sources.list from xenial to bionic but this time I first
installed the version of libc6.

Start-Date: 2018-05-01  12:29:37
Commandline: apt-get install libc6
Requested-By: bdmurray (1000)
Upgrade: libc6-dbg:amd64 (2.23-0ubuntu10, 2.27-3ubuntu1), libc6-dev:amd64 
(2.23-0ubuntu10, 2.27-3ubuntu1), libc6:amd64 (2.23-0ubuntu10, 2.27-3ubuntu1), 
locales:amd64 (2.23-0ubuntu10, 2.27-3ubuntu1), libc-bin:amd64 (2.23-0ubuntu10, 
2.27-3ubuntu1), libc6-i386:amd64 (2.23-0ubuntu10, 2.27-3ubuntu1), 
libc-dev-bin:amd64 (2.23-0ubuntu10, 2.27-3ubuntu1)
End-Date: 2018-05-01  12:29:56

Again I did not encounter the bug when upgrading via this method.

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned

Status in OEM Priority Project:
  Confirmed
Status in gnome-menus package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 13 9360 (CID 201606-22338)
  pre-installed (oem) image Xenial

  [Description]

  When I tried to perform 16.04 --> 18.04 update, the update process
  failed. The process guide me to file this bug report.

  [Steps to reproduce]
  1. Update the system to the latest stack by "sudo apt-get update; sudo 
apt-get dist-upgrade -y"
  2. Reboot
  3. Make sure /etc/update-manager/release-upgrades is able to update (The 
configuration value of "Prompt" should be "lts", namely "Prompt=lts", not 
"Prompt=never").
  4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade 
-d"
  5. During the update process, it prompts for "Configuring gdm3". There are 
two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the 
attachment for the prompt details as well.

  We should use "-d" because bionic beaver has not been officially
  released yet.

  [Expected Result]

  The release update completed and I could start using Bionic instead of
  Xenial.

  [Actual Result]

  The update process failed. It shows the error message[1] and
  automatically asking for filing this bug report.

  [1]

  Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-1ubuntu1) ...
  Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-2ubuntu6) ...
  (Reading database ... 253705 files and directories currently installed.)
  Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ...
  Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ...
  Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ...
  Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
    bamfdaemon -> gnome-menus
   packages' pending triggers which are or may be unresolvable:
    gnome-menus: /usr/share/applications
    bamfdaemon: /usr/share/applications
    libglib2.0-0:amd64: /usr/share/glib-2.0/schemas
    desktop-file-utils: /usr/share/applications
    mime-support: /usr/share/applications
  dpkg: error processing package gnome-menus (--remove):
   triggers looping, abandoned
  Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
  Processing triggers for mime-support (3.59ubuntu1) ...
  Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ...
  Errors were encountered while processing:
   gnome-menus
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/gnome-menus.0.crash'
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
    S: Send report (376.4 KB)
    V: View report
    K: Keep report file for sending later or copying to somewhere else
    I: Cancel and ignore future crashes of this program version
    C: Cancel
  Please choose (S/V/K/I/C):

  .. (a lot of them)

   qml-module-qtquick-controls2:amd64
   qml-module-org-kde-kconfig:amd64
   libunity-control-center1
   libqt5quickcontrols2-5:amd64
   libglib2.0-bin
   libkf5plasma5:amd64
   locales
   qml-module-qtqml-models2:amd64
   libkf5coreaddons5:amd64
   gir1.2-goa-1.0:amd64
   libwebkit2gtk-4.0-37:amd64
  Processing was halted because there were too many errors.

  Upgrade complete

  The upgrade has completed but there were errors during the upgrade
  process.

  To continue please press [ENTER]

  ubuntu@201606-22338:~$

  ==

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package:

[Desktop-packages] [Bug 1768343] [NEW] Not detect secondary button of notebook touchpad

2018-05-01 Thread Javier

Public bug reported:

When I press the secondary touchpad button, Ubuntu takes it as the primary one. 
This error does not happen with a usb mouse.
Acer Aspire 3 7100U

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-settings-daemon 3.28.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue May  1 17:02:59 2018
ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-mouse
InstallationDate: Installed on 2018-05-01 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Not detect secondary button of notebook touchpad

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

Bug description:
  When I press the secondary touchpad button, Ubuntu takes it as the primary 
one. This error does not happen with a usb mouse.
  Acer Aspire 3 7100U

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 17:02:59 2018
  ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-mouse
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767536] Re: Accessing the WIFI section of the "Settings" window causes massive freezes

As expected, it's gnome-control-center that is eating up the CPU. Note
that 25% equals precisely 100% of one core on my four core processor.

** Attachment added: "gnome-control-center in monitor"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1767536/+attachment/5131647/+files/Screenshot%20from%202018-05-01%2012-54-23.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/1767536

Title:
  Accessing the WIFI section of the "Settings" window causes massive
  freezes

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

Bug description:
  Accessing the Wi-Fi section of the "Settings" window causes huge, 5-20
  seconds freezes of the window. Nothing else seems to freeze. One
  core's utilization goes up during the freeze.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 17:23:34 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767981] Re: Incorrect permissions on polkit-agent-helper-1

** Summary changed:

- Incorrect permissions on upgrade found for login
+ Incorrect permissions on polkit-agent-helper-1

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

Title:
  Incorrect permissions on polkit-agent-helper-1

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  I upgraded from 17.10 to 18.04, I ran 
  czajkowski@penny:~$ sudo do-release-upgrade
  czajkowski@penny:~$ sudo apt update && sudo apt dist-upgrade
  czajkowski@penny:~$ sudo apt install update-manager-core

  
  Upgrade then started and about 4 mins the Error 1 image appeared, Incorrect 
permissions on /usr/lib/policykit-1/polkit-agent-helper-1(needs to be setuid 
root)

  a few mins later the login appeared for me to enter my password,  it
  would not recognise my password Error 2.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 10:21:49 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-20 (1226 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to bionic on 2018-04-29 (0 days ago)

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

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

[Desktop-packages] [Bug 1767981] Re: Incorrect permissions on upgrade found for login

I don't believe this has anything to do with the release upgrader, it
just happened to be the process which caused you to notice that the
permissions were incorrect.

** Package changed: ubuntu-release-upgrader (Ubuntu) => policykit-1
(Ubuntu)

** Changed in: policykit-1 (Ubuntu)
   Status: Incomplete => New

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

Title:
  Incorrect permissions on upgrade found for login

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  I upgraded from 17.10 to 18.04, I ran 
  czajkowski@penny:~$ sudo do-release-upgrade
  czajkowski@penny:~$ sudo apt update && sudo apt dist-upgrade
  czajkowski@penny:~$ sudo apt install update-manager-core

  
  Upgrade then started and about 4 mins the Error 1 image appeared, Incorrect 
permissions on /usr/lib/policykit-1/polkit-agent-helper-1(needs to be setuid 
root)

  a few mins later the login appeared for me to enter my password,  it
  would not recognise my password Error 2.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 10:21:49 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-20 (1226 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to bionic on 2018-04-29 (0 days ago)

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

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

[Desktop-packages] [Bug 1767542] Re: Turning off WiFi enables Airplane mode

I accidentally changed the status back to new and it won't allow me to
set it back to "triaged".

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

Title:
  Turning off WiFi enables Airplane mode

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

Bug description:
  Turning off the WiFi from the top right control enables Airplane mode
  (see screenshots). Also after turning off airplane mode, the Wi-Fi is
  not turned back on, rather the Bluetooth is.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 17:46:34 2018
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767542] Re: Turning off WiFi enables Airplane mode

@Sebastien, I do not think this issue is reflected anywhere in the issue
you linked upstream.

** Changed in: gnome-control-center (Ubuntu)
   Status: Triaged => New

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

Title:
  Turning off WiFi enables Airplane mode

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

Bug description:
  Turning off the WiFi from the top right control enables Airplane mode
  (see screenshots). Also after turning off airplane mode, the Wi-Fi is
  not turned back on, rather the Bluetooth is.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 17:46:34 2018
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768336] [NEW] After installing vino-server "Remote Desktop" never appears for LXSession and vino-preferences command not present

2018-05-01 Thread Wayne

Public bug reported:

In Lubuntu 16.04, after installing Vino, an option appears in the
Autostart section of "Default applications for LXSession" program. In
addition, the command vino-preferences opens the configuration screen.

Vino does not install similarly in version 18.04 and entering the
command vino-preferences does not work.

Lubuntu bug marked invalid and told to make a report here.

https://bugs.launchpad.net/lubuntu-artwork/+bug/1768260

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

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

Title:
  After installing vino-server "Remote Desktop" never appears for
  LXSession and vino-preferences command not present

Status in vino package in Ubuntu:
  New

Bug description:
  In Lubuntu 16.04, after installing Vino, an option appears in the
  Autostart section of "Default applications for LXSession" program. In
  addition, the command vino-preferences opens the configuration screen.

  Vino does not install similarly in version 18.04 and entering the
  command vino-preferences does not work.

  Lubuntu bug marked invalid and told to make a report here.

  https://bugs.launchpad.net/lubuntu-artwork/+bug/1768260

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

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

[Desktop-packages] [Bug 1767981] [NEW] Incorrect permissions on upgrade found for login

You have been subscribed to a public bug:

I upgraded from 17.10 to 18.04, I ran 
czajkowski@penny:~$ sudo do-release-upgrade
czajkowski@penny:~$ sudo apt update && sudo apt dist-upgrade
czajkowski@penny:~$ sudo apt install update-manager-core


Upgrade then started and about 4 mins the Error 1 image appeared, Incorrect 
permissions on /usr/lib/policykit-1/polkit-agent-helper-1(needs to be setuid 
root)

a few mins later the login appeared for me to enter my password,  it
would not recognise my password Error 2.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.17
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 30 10:21:49 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-12-20 (1226 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to bionic on 2018-04-29 (0 days ago)

** Affects: policykit-1 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful2bionic bionic dist-upgrade
-- 
Incorrect permissions on upgrade found for login
https://bugs.launchpad.net/bugs/1767981
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to policykit-1 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 1767544] Re: While running the Orca screen reader, system hangs while gnome-control-center is open

2018-05-01 Thread Jeremy Lincicome

>From an accessibility prospective, the system appears to hang. Orca
doesn't read anything until I force close the gnome-control-center
window. I'm blind, so cannot tell if anything happens if I move the
mouse, or press Alt+Tab.

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

Title:
While running the Orca screen reader, system hangs while gnome-
control-center is open

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

Bug description:
When gnome-control-center loads, my computer becomes inaccessible. To get
Orca working again, I have to force close the app with Alt+f4. There are parts
of the control center that I can use, such as the sound and VPN settings, only
if I invoke them from the dash. If I invoke Wi-Fi from the dash or top bar, it
is inaccessible.
Steps to reproduce:
1. Launch Orca by pressing Alt+Super+s.
2. Press the super key, and type "settings" into the search box.
3. After the settings screen loads, try to move around using Tab and
Shift+Tab. Also try to move using Orca's flat review feature.
The commands for using flat review can be found at:
https://help.gnome.org/users/orca/stable/commands_flat_review.html.en
On a desktop, the Orca modifier is the insert key. On a laptop, the Orca
modifier is the Caps lock key, if laptop layout is set in Orca's preferences.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 27 15:44:35 2018
InstallationDate: Installed on 2018-04-27 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180425.1)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768178] Re: color scheme Solarized Dark is incorrect

2018-05-01 Thread Egmont Koblinger

> I missed that background color scheme and palette scheme are dedicated
and selected only first scheme, but not palette scheme (was selected
Tango).

This is indeed misleading and we're thinking about changing the
behavior. Ideally you'd just select "Solarized dark" at one place, and
this would set the fg/bg and palette colors, and even disable the
aforementioned "show bold in bright". It's unclear though for us how
this could be done in a way that doesn't at the same time introduce a
usability regression for those who prefer traditional (non-solarized)
color schemes: they'd still want to select fg/bg and palette
independently from each other according to their personal preferences.

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

Title:
  color scheme Solarized Dark is incorrect

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Original Solarized Dark looks different. Thereis the pull request on
  Github that fixes that - https://github.com/GNOME/gnome-
  terminal/pull/6

  I'm not author of patch and don't checked it, but there is project
  that change color scheme to correct, it described here -
  https://github.com/Anthony25/gnome-terminal-colors-
  solarized/tree/master/colors/dark

  Here is built-in palette collected with gsettings get:
  ['#2E3436', 
  '#CC', 
  '#4E9A06', 
  '#C4A000', 
  '#3465A4', 
  '#75507B', 
  '#06989A', 
  '#D3D7CF', 
  '#555753', 
  '#EF2929', 
  '#8AE234', 
  '#FCE94F', 
  '#729FCF', 
  '#AD7FA8', 
  '#34E2E2', 
  '#EC']

  Here is correct palette:
  ['#070736364242', 
  '#DCDC32322F2F', 
  '#8585', 
  '#B5B58989', 
  '#26268B8BD2D2', 
  '#D3D336368282', 
  '#2A2AA1A19898', 
  '#E8E8D5D5', 
  '#2B2B3636', 
  '#CBCB4B4B1616', 
  '#58586E6E7575', 
  '#65657B7B8383', 
  '#838394949696', 
  '#6C6C7171C4C4', 
  '#9393A1A1A1A1', 
  '#FDFDF6F6E3E3']

  I asked the question about long codes - https://github.com/Anthony25
  /gnome-terminal-colors-solarized/issues/76, but anyway it matches
  original scheme perfectly.

  I created bug at launchpad because Gnome restricted creating bugs for
  non-gnome developers in their guide
  https://wiki.gnome.org/Apps/Terminal/ReportingBugs and point to
  distribution bug tracker.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 07:49:18 2018
  InstallationDate: Installed on 2018-04-29 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767629] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-commo

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

** This bug has been marked a duplicate of bug 1767116
   package nvidia-340 (not installed) failed to install/upgrade: trying to 
overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package 
nvidia-kernel-common-390 390.48-0ubuntu3

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: trying
  to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in
  package nvidia-kernel-common-390 390.48-0ubuntu3+gpu18.04.2,
  overheating problem with nvidia 710M, can`t find to fix that.

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  Overheating problem with nvidia 710M, can`t find to fix that. On ubuntu 16.04 
works, that
  sudo apt install nvidia-361 nvidia-prime

  sudo prime-select intel
  and was temperature 45 grade Celsius. 

  with 18.04 it`s > 57

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sat Apr 28 13:31:20 2018
  ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which 
is also in package nvidia-kernel-common-390 390.48-0ubuntu3+gpu18.04.2
  InstallationDate: Installed on 2018-04-27 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package 
nvidia-kernel-common-390 390.48-0ubuntu3+gpu18.04.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1767629/+subscriptions

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

[Desktop-packages] [Bug 1765832] Re: Two finger scrolling not working after suspend

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

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

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

Title:
  Two finger scrolling not working after suspend

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When waking up my laptop, two finger scrolling is not working anymore.

  Running:

  $ modprobe -r psmouse
  $ modprobe psmouse

  restores the functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr 20 08:23:33 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.10, 4.15.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:2227]
  InstallationDate: Installed on 2018-04-10 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  MachineType: LENOVO 20BTS09800
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET26W (1.04 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTS09800
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET26W(1.04):bd01/23/2015:svnLENOVO:pn20BTS09800:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS09800:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 3rd
  dmi.product.name: 20BTS09800
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1768182] Re: The "Search" input field of "New Tab" of the Firefox browser can not be used depending on the theme.

2018-05-01 Thread Seth Arnold

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  The "Search" input field of "New Tab" of the Firefox browser can not
  be used depending on the theme.

Status in firefox package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 LTS (Japanese environment)

  kernel: 4.15.0-20-generic
  GNOME Tweaks 3.28.1
  GTK+ 3.22.30
  Firefox Quantum 59.0.2(64 bit)

  In "Adwaita-dark" theme, "Search" input field of "New Tab" of Firefox
  browser can not be used.

  1. Install Ubuntu 18.04 LTS in Japanese, with minimum configuration.
  2. Install the "GNOME Tweaks" application.
  3. Launch the "GNOME Tweaks" application and specify the "Appearance" tab -> 
Application: "Adwaita - dark".
  4. Start Firefox and open "New Tab".
  5. The above "URL address input field" is black, but since the input 
character is white, it is possible to judge the input character.
  6. The "Search the web" entry below it is also black. The character I entered 
is black. So, I can not use it because I can not see the characters.

  [Workaround](?)
  Click the "gear" icon on the right side of the "Web search" input field, open 
the "New tab setting" screen and uncheck "Search".
  The "Web search" input field disappears.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 59.0.2+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BuildID: 20180406121424
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 12:28:13 2018
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-04-29 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=59.0.2/20180406121424 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2014
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd10/03/2014:svnGOOGLE:pnPanther:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Panther
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

I was also able to recreate this by editing sources.list from xenial to
bionic after restoring the apt-clone file.

I did NOT encounter this bug, after restoring the clone file, and then
editing sources.list from xenial to bionic and first installing the new
version of apt which also pulled in libc among other things.

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned

Status in OEM Priority Project:
  Confirmed
Status in gnome-menus package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 13 9360 (CID 201606-22338)
  pre-installed (oem) image Xenial

  [Description]

  When I tried to perform 16.04 --> 18.04 update, the update process
  failed. The process guide me to file this bug report.

  [Steps to reproduce]
  1. Update the system to the latest stack by "sudo apt-get update; sudo 
apt-get dist-upgrade -y"
  2. Reboot
  3. Make sure /etc/update-manager/release-upgrades is able to update (The 
configuration value of "Prompt" should be "lts", namely "Prompt=lts", not 
"Prompt=never").
  4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade 
-d"
  5. During the update process, it prompts for "Configuring gdm3". There are 
two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the 
attachment for the prompt details as well.

  We should use "-d" because bionic beaver has not been officially
  released yet.

  [Expected Result]

  The release update completed and I could start using Bionic instead of
  Xenial.

  [Actual Result]

  The update process failed. It shows the error message[1] and
  automatically asking for filing this bug report.

  [1]

  Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-1ubuntu1) ...
  Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-2ubuntu6) ...
  (Reading database ... 253705 files and directories currently installed.)
  Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ...
  Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ...
  Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ...
  Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
    bamfdaemon -> gnome-menus
   packages' pending triggers which are or may be unresolvable:
    gnome-menus: /usr/share/applications
    bamfdaemon: /usr/share/applications
    libglib2.0-0:amd64: /usr/share/glib-2.0/schemas
    desktop-file-utils: /usr/share/applications
    mime-support: /usr/share/applications
  dpkg: error processing package gnome-menus (--remove):
   triggers looping, abandoned
  Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
  Processing triggers for mime-support (3.59ubuntu1) ...
  Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ...
  Errors were encountered while processing:
   gnome-menus
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/gnome-menus.0.crash'
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
    S: Send report (376.4 KB)
    V: View report
    K: Keep report file for sending later or copying to somewhere else
    I: Cancel and ignore future crashes of this program version
    C: Cancel
  Please choose (S/V/K/I/C):

  .. (a lot of them)

   qml-module-qtquick-controls2:amd64
   qml-module-org-kde-kconfig:amd64
   libunity-control-center1
   libqt5quickcontrols2-5:amd64
   libglib2.0-bin
   libkf5plasma5:amd64
   locales
   qml-module-qtqml-models2:amd64
   libkf5coreaddons5:amd64
   gir1.2-goa-1.0:amd64
   libwebkit2gtk-4.0-37:amd64
  Processing was halted because there were too many errors.

  Upgrade complete

  The upgrade has completed but there were errors during the upgrade
  process.

  To continue please press [ENTER]

  ubuntu@201606-22338:~$

  ==

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed Apr 25 22:00:01 2018
  Dependencies:

  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see

[Desktop-packages] [Bug 1768178] Re: color scheme Solarized Dark is incorrect

2018-05-01 Thread popstas

Oh, sorry, of course, I missed that background color scheme and palette
scheme are dedicated and selected only first scheme, but not palette
scheme (was selected Tango).

Confirm that built-in scheme is correct.

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

Title:
  color scheme Solarized Dark is incorrect

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Original Solarized Dark looks different. Thereis the pull request on
  Github that fixes that - https://github.com/GNOME/gnome-
  terminal/pull/6

  I'm not author of patch and don't checked it, but there is project
  that change color scheme to correct, it described here -
  https://github.com/Anthony25/gnome-terminal-colors-
  solarized/tree/master/colors/dark

  Here is built-in palette collected with gsettings get:
  ['#2E3436', 
  '#CC', 
  '#4E9A06', 
  '#C4A000', 
  '#3465A4', 
  '#75507B', 
  '#06989A', 
  '#D3D7CF', 
  '#555753', 
  '#EF2929', 
  '#8AE234', 
  '#FCE94F', 
  '#729FCF', 
  '#AD7FA8', 
  '#34E2E2', 
  '#EC']

  Here is correct palette:
  ['#070736364242', 
  '#DCDC32322F2F', 
  '#8585', 
  '#B5B58989', 
  '#26268B8BD2D2', 
  '#D3D336368282', 
  '#2A2AA1A19898', 
  '#E8E8D5D5', 
  '#2B2B3636', 
  '#CBCB4B4B1616', 
  '#58586E6E7575', 
  '#65657B7B8383', 
  '#838394949696', 
  '#6C6C7171C4C4', 
  '#9393A1A1A1A1', 
  '#FDFDF6F6E3E3']

  I asked the question about long codes - https://github.com/Anthony25
  /gnome-terminal-colors-solarized/issues/76, but anyway it matches
  original scheme perfectly.

  I created bug at launchpad because Gnome restricted creating bugs for
  non-gnome developers in their guide
  https://wiki.gnome.org/Apps/Terminal/ReportingBugs and point to
  distribution bug tracker.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 07:49:18 2018
  InstallationDate: Installed on 2018-04-29 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

2018-05-01 Thread Peter

Confirm this for

Samsung SCX-3200
ID 04e8:3441

Ubuntu 18.04 Server
connected via USB (worked flawlessly in 16.04)

Printer works (splix)

Scanner is detected, but when starting to scan: I/O Error
didn't install any third party drivers

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768332] [NEW] crash & doesen t start

2018-05-01 Thread Patrick

Public bug reported:

The program does not open unless it is set as the default device for
opening the mp3 tracks, but it does not play any music, and the Ubuntu
error message wizard logs on

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

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

Title:
  crash & doesen t start

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  The program does not open unless it is set as the default device for
  opening the mp3 tracks, but it does not play any music, and the Ubuntu
  error message wizard logs on

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

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

[Desktop-packages] [Bug 1768331] [NEW] Desktop is not displayed on screen with "Gnome Classic"

2018-05-01 Thread Ulf Samuelsson

Public bug reported:

After installing Ubuntu Desktop 18.04, I install "gnome".
After rebooting, I select "Gnome Classic" when I log in.
When right clicking on the desktop, I do not get the usual popdown list,
allowing me to create folder in the Desktop etc.
Only a very limited popdown list.

If I log out, and log in using Ubuntu instead of "Gnome Classic", I get
the expected popdown list.

ulf@Gondolin:~$ lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04

ulf@Gondolin:~$ apt-cache policy nautilus
nautilus:
  Installerad: 1:3.26.3-0ubuntu4
  Kandidat:1:3.26.3-0ubuntu4
  Versionstabell:
 *** 1:3.26.3-0ubuntu4 500
500 http://se.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue May  1 20:46:41 2018
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'start-with-sidebar' b'false'
 b'org.gnome.nautilus.window-state' b'geometry' b"'1583x907+55+505'"
InstallationDate: Installed on 2018-05-01 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug bionic

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

Title:
  Desktop is not displayed on screen with "Gnome Classic"

Status in nautilus package in Ubuntu:
  New

Bug description:
  After installing Ubuntu Desktop 18.04, I install "gnome".
  After rebooting, I select "Gnome Classic" when I log in.
  When right clicking on the desktop, I do not get the usual popdown list,
  allowing me to create folder in the Desktop etc.
  Only a very limited popdown list.

  If I log out, and log in using Ubuntu instead of "Gnome Classic", I
  get the expected popdown list.

  ulf@Gondolin:~$ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  ulf@Gondolin:~$ apt-cache policy nautilus
  nautilus:
Installerad: 1:3.26.3-0ubuntu4
Kandidat:1:3.26.3-0ubuntu4
Versionstabell:
   *** 1:3.26.3-0ubuntu4 500
  500 http://se.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 20:46:41 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'start-with-sidebar' b'false'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1583x907+55+505'"
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1744775] Re: "Operation was cancelled" when trying to use Transparency Unit in Canon 9000F Mark II

2018-05-01 Thread Florian Haftmann

The use of the transparency unit in Canon 9000F Mark II requires to take
the regular white background away from the covering lid, beneath with
the actual backlight of the transparency unit resides.

Any scanning attempt with the transparency unit as source while the
backlight is hidden by the white background yields the error described
above – which is, sadly, not very descriptly.

After taking way the background the transparency unit works like a
charm.

@Jelle you might try whether this works for you.

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

Title:
  "Operation was cancelled" when trying to use Transparency Unit in
  Canon 9000F Mark II

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to scan foto negatives using this command (that used to
  work in previous Ubuntu versions):

  scanimage --device-name pixma:04A9190D --source "Transparency
  Unit" --resolution "2400" --format "tiff" --mode Color -l 76 -x 66  >
  test.tiff

  But I get this error:

  scanimage: sane_read: Operation was cancelled

  Note: scanning regular images (using the Flatbed source) works fine.

  My current ubuntu verison is Ubuntu 17.10

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

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

[Desktop-packages] [Bug 1761834] Re: Right-click doesn't work

2018-05-01 Thread FM33

Hello,

I have this too : Physical button from the touchpad is handled as a left click.
I can use 2-fingers as a workaround, but "area" mode is not working though.

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

Title:
  Right-click doesn't work

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I decided to try out the beta for 18.04 from 17.10.  Upon upgrading, I
  discovered that right-clicking no longer works on my trackpad, and
  right-clicks are handled as left-clicks would be.  Two-finger right
  click does not work either.  If I plug in a mouse with a physical
  right button, right clicking does work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr  6 11:26:00 2018
  DistUpgraded: 2018-04-06 11:14:08,949 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.14.15-041415-generic, x86_64: installed
   bbswitch, 0.8, 4.15.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2017-05-04 (337 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic 
root=UUID=62d6bfc3-82e2-4ca2-9255-8dae5ad9b117 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-04-06 (0 days ago)
  dmi.bios.date: 08/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd08/21/2017:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1761834] Re: Right-click doesn't work

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

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

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

Title:
  Right-click doesn't work

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I decided to try out the beta for 18.04 from 17.10.  Upon upgrading, I
  discovered that right-clicking no longer works on my trackpad, and
  right-clicks are handled as left-clicks would be.  Two-finger right
  click does not work either.  If I plug in a mouse with a physical
  right button, right clicking does work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr  6 11:26:00 2018
  DistUpgraded: 2018-04-06 11:14:08,949 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.14.15-041415-generic, x86_64: installed
   bbswitch, 0.8, 4.15.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2017-05-04 (337 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic 
root=UUID=62d6bfc3-82e2-4ca2-9255-8dae5ad9b117 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-04-06 (0 days ago)
  dmi.bios.date: 08/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd08/21/2017:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1001842] Re: No Audio from HDMI After Switching Monitor Off / On

2018-05-01 Thread Victor

Same problem in ubuntu 18.04lts, 
After the monitor enters in sleep mode or is turned off, the audio is missing.

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

Title:
  No Audio from HDMI After Switching Monitor Off / On

Status in fglrx-installer package in Ubuntu:
  Confirmed

Bug description:
  After the 12.04 Update my HDMI audio stops working anytime I turn off or on,  
my 2nd monitor(plasma TV)
  System Settings>Sound - Output
  HDMI audio disappears from the list when monitor is turned off or on and does 
not reappear.

  see http://askubuntu.com/questions/133575/hdmi-audio-stops-after-tv-
  turned-off/139265#139265

  I'm guessing it has something to do with sink detection and ATI video

  The only info I've found is after running pactl list
  Partial copy

  Sink #0
  State: SUSPENDED
  Name: alsa_output.pci-_01_00.1.hdmi-stereo
  Description: Turks HDMI Audio [Radeon HD 6000 Series] Digital Stereo 
(HDMI)
  Driver: module-alsa-card.c
  Sample Specification: s16le 2ch 44100Hz
  Channel Map: front-left,front-right
  Owner Module: 4
  Mute: no
  Volume: 0: 100% 1: 100%
  0: 0.00 dB 1: 0.00 dB
  balance 0.00
  Base Volume: 100%
   0.00 dB
  Monitor Source: alsa_output.pci-_01_00.1.hdmi-stereo.monitor
  Latency: 0 usec, configured 0 usec
  Flags: HARDWARE DECIBEL_VOLUME LATENCY SET_FORMATS 
  Properties:
  alsa.resolution_bits = "16"
  device.api = "alsa"
  device.class = "sound"
  alsa.class = "generic"
  alsa.subclass = "generic-mix"
  alsa.name = "HDMI 0"
  alsa.id = "HDMI 0"
  alsa.subdevice = "0"
  alsa.subdevice_name = "subdevice #0"
  alsa.device = "3"
  alsa.card = "1"
  alsa.card_name = "HD-Audio Generic"
  alsa.long_card_name = "HD-Audio Generic at 0xfddfc000 irq 48"
  alsa.driver_name = "snd_hda_intel"
  device.bus_path = "pci-:01:00.1"
  sysfs.path = 
"/devices/pci:00/:00:02.0/:01:00.1/sound/card1"
  device.bus = "pci"
  device.vendor.id = "1002"
  device.vendor.name = "Advanced Micro Devices [AMD] nee ATI"
  device.product.name = "Turks HDMI Audio [Radeon HD 6000 Series]"
  device.string = "hdmi:1"
  device.buffering.buffer_size = "65536"
  device.buffering.fragment_size = "32768"
  device.access_mode = "mmap+timer"
  device.profile.name = "hdmi-stereo"
  device.profile.description = "Digital Stereo (HDMI)"
  device.description = "Turks HDMI Audio [Radeon HD 6000 Series] 
Digital Stereo (HDMI)"
  alsa.mixer_name = "ATI R6xx HDMI"
  alsa.components = "HDA:1002aa01,00aa0100,00100200"
  module-udev-detect.discovered = "1"
  device.icon_name = "audio-card-pci"
  Ports:
  hdmi-output-0: HDMI / DisplayPort (priority: 5900, not available)
  Active Port: hdmi-output-0
  Formats:
  pcm

  
  I checked before and after. The only difference is
  hdmi-output-0: HDMI / DisplayPort (priority: 5900, not available)

  Where "not available" is the only change I found.
  Removing cable from HDMI socket and plugging in again, restores audio.
  Logging in and out again restores audio.

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

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

[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

2018-05-01 Thread Wayne Carr

I see the same thing as #17 (Andrew).  I type in the password correctly
each time.  I login to a user (successfully, no errors) and then log
out.  After that, I login as a different user and I get the purple
screen without the desktop showing.  I typed the correct password.  If I
switch users leaving the first user still running (instead of logging
that user out) the error does not happen.  This happens on 3 different
PCs that I've updated to 18.04.

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

Status in gdm:
  New
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  WORKAROUND: After typing an incorrect password, click Cancel, then
  click your name, then enter your password again.

  ---

  Trying to log into my session (Gnome, Xorg), if I enter the wrong
  password before entering it correctly, the session doesn't load and I
  get a purple screen, a mouse cursor, and an invisible but clickable
  menu in the top right. If I enter it correctly the first time, there
  is no problem.

  I've replicated this from a fresh boot, after logging out and after
  'sudo service gdm restart' from the Ctrl-Alt-F4 console.

  This is a fresh install, and didn't occur when I was using a previous
  install of 18.04 (until Friday).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 22 20:31:13 2018
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2018-05-01 Thread Apport retracing service

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

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 #1589052, 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/1768307/+attachment/5131560/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

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

Bug description:
  Note that two are two NetworkManager entries:

  -rw--- 1 root root 295 May  1 11:29 DHCP
  -rw--- 1 root root 330 May  1 13:10 LAN

  LAN needed to have dns-search set by editing the file because Gnome UI
  tool doesn't offer that setting. (Why?)

  "Wired Connection" was turned off in an attempt to have NetworkManager
  pick up the manual change. It didn't. So "service NetworkManager" was
  run instead.

  Some two minutes after that notification that gnome-control-center
  failure was provided. Note that the segfault was logged in
  /var/log/syslog:

  May  1 13:11:51 pxei3 kernel: [ 6205.992942] gnome-control-c[3992]:
  segfault at 14a3e80 ip 7f0d0fc5ed12 sp 7ffc0b28e510 error
  4 in libgobject-2.0.so.0.5600.1[7f0d0fc29000+52000]

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 13:11:51 2018
  ExecutablePath: /usr/bin/gnome-control-center
  ExecutableTimestamp: 1523929577
  InstallationDate: Installed on 2018-04-30 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcCmdline: gnome-control-center --overview
  ProcCwd: /home/install
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f0d0fc5ed12 :
mov(%rdi),%rbp
   PC (0x7f0d0fc5ed12) ok
   source "(%rdi)" (0x14a3e80) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in 
g_type_check_instance_cast()
  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/1768307/+subscriptions

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

[Desktop-packages] [Bug 1635310] Re: privacy settings not saved

2018-05-01 Thread Jeremy Bicha

This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  privacy settings not saved

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

Bug description:
  steps to reproduce;

  1) open gnome-control-center
  2) click on privacy
  3) screen lock
  4) click on 'on' (to turn off)

  error message in the console:

  (gnome-control-center:25678): dconf-WARNING **: failed to commit
  changes to dconf:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to
  execute program ca.desrt.dconf: No such file or directory

  switch bounces back to 'on'

  You can change 'Lock screen after blank for' (screen turns off)
  ...but it seems to have no effect, and if you exit back to main control 
centre menu and go back to privacy it's re set to (screen turns off).

  similarly
  Show Notifications bounces back to default 'on' once clicked, 
  as does 'recently used' 
  and dropdowns 'retain history' in usage &  history also go back to default 
'forever' once you go back to them.

  tl;dr privacy settings don't actually do anything

  This did not seem to be the case in Ubuntu xenial ( 16.04 ), but has
  been so since upgrade to ubuntu yakkety ( 16.10 ).

  
  gnome-control-center: 1:3.20.1-2ubuntu3
  dconf-service: 0.26.0-2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-control-center 1:3.20.1-2ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 20 11:02:11 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-09 (833 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (3 days ago)

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

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

[Desktop-packages] [Bug 1768306] Re: LibreOffice crash

2018-05-01 Thread fossfreedom

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

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

Title:
  LibreOffice crash

Status in Ubuntu Budgie:
  New
Status in libreoffice package in Ubuntu:
  New

Bug description:
  Whenever LibreOffice Writer is launched, it does not load and a crash report 
appears.
  And if it is launched via the command line, it doesn't even show any info or 
error message.

  The LibreOffice base and Calc opens OK though.

  System info:

  OS: Ubuntu Budgie 18.04 32-bit
  PC: Sony Vaio VGN-FE21H

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

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

[Desktop-packages] [Bug 1768304] Re: package shared-mime-info 1.9-2 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess was killed by signal (Terminated)

2018-05-01 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 shared-mime-info in Ubuntu.
https://bugs.launchpad.net/bugs/1768304

Title:
  package shared-mime-info 1.9-2 failed to install/upgrade: installed
  shared-mime-info package post-installation script subprocess was
  killed by signal (Terminated)

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  I was trying to install projectlibre_1.7.0-1.deb when the error
  occurred.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: shared-mime-info 1.9-2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May  2 00:59:17 2018
  DuplicateSignature:
   package:shared-mime-info:1.9-2
   Setting up shared-mime-info (1.9-2) ...
   dpkg: error processing package shared-mime-info (--configure):
installed shared-mime-info package post-installation script subprocess was 
killed by signal (Terminated)
  ErrorMessage: installed shared-mime-info package post-installation script 
subprocess was killed by signal (Terminated)
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.9-2 failed to install/upgrade: installed 
shared-mime-info package post-installation script subprocess was killed by 
signal (Terminated)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1768304/+subscriptions

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

[Desktop-packages] [Bug 1768304] [NEW] package shared-mime-info 1.9-2 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess was killed by signal (Terminated

2018-05-01 Thread neversaynever

Public bug reported:

I was trying to install projectlibre_1.7.0-1.deb when the error
occurred.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: shared-mime-info 1.9-2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May  2 00:59:17 2018
DuplicateSignature:
 package:shared-mime-info:1.9-2
 Setting up shared-mime-info (1.9-2) ...
 dpkg: error processing package shared-mime-info (--configure):
  installed shared-mime-info package post-installation script subprocess was 
killed by signal (Terminated)
ErrorMessage: installed shared-mime-info package post-installation script 
subprocess was killed by signal (Terminated)
InstallationDate: Installed on 2018-05-01 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.9-2 failed to install/upgrade: installed 
shared-mime-info package post-installation script subprocess was killed by 
signal (Terminated)
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: shared-mime-info (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package shared-mime-info 1.9-2 failed to install/upgrade: installed
  shared-mime-info package post-installation script subprocess was
  killed by signal (Terminated)

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  I was trying to install projectlibre_1.7.0-1.deb when the error
  occurred.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: shared-mime-info 1.9-2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May  2 00:59:17 2018
  DuplicateSignature:
   package:shared-mime-info:1.9-2
   Setting up shared-mime-info (1.9-2) ...
   dpkg: error processing package shared-mime-info (--configure):
installed shared-mime-info package post-installation script subprocess was 
killed by signal (Terminated)
  ErrorMessage: installed shared-mime-info package post-installation script 
subprocess was killed by signal (Terminated)
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.9-2 failed to install/upgrade: installed 
shared-mime-info package post-installation script subprocess was killed by 
signal (Terminated)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1768304/+subscriptions

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

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

2018-05-01 Thread Paul Williams

I agree, I can't replicate it either

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

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

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

Bug description:
  When I run gnome-control-center I get the following error message:

  (gnome-control-center:18823): GLib-CRITICAL **: g_strsplit: assertion 'string 
!= NULL' failed
  Segmentation fault (core dumped)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 09:33:23 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: gnome-control-center user-accounts
  SegvAnalysis:
   Segfault happened at: 0x7fbb994a3b59:mov(%rsi),%rsi
   PC (0x7fbb994a3b59) ok
   source "(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_renderer_connect () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in cogl_renderer_connect()
  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/1725347/+subscriptions

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-01 Thread Kyle Weber

At the top of this page it says "Fix Released". Does anyone know to to
get them to change the status to an open bug and re-evaluate it? It's
clearly not fixed.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Desktop-packages] [Bug 890867] Re: pulseaudio crashed with SIGABRT in pa_memimport_free()

2018-05-01 Thread Taras Prokopenko

** Changed in: pulseaudio (Ubuntu)
   Status: Expired => New

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

Title:
  pulseaudio crashed with SIGABRT in pa_memimport_free()

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Sound crashed after changing the volume, but seems random, hasn't done
  it again. Might be related to instalation of pulseaudio-equalizer,
  even if I do notice the sound widget/icon (gnome-shell) restarting at
  times.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: pulseaudio 1:1.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dramalho   5025 F pulseaudio
   /dev/snd/controlC0:  dramalho   5025 F pulseaudio
   /dev/snd/pcmC0D0p:   dramalho   5025 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd742 irq 47'
 Mixer name : 'IDT 92HD75B3X5'
 Components : 'HDA:111d7603,103c172b,00100202 
HDA:11c11040,103c3066,00100200'
 Controls  : 15
 Simple ctrls  : 10
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xd300 irq 16'
 Mixer name : 'Nvidia GPU 0b HDMI/DP'
 Components : 'HDA:10de000b,10de0101,00100100'
 Controls  : 16
 Simple ctrls  : 4
  Date: Tue Nov 15 18:23:52 2011
  ExecutablePath: /usr/bin/pulseaudio
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libpulsecommon-1.0.so
   pa_memimport_free () from /usr/lib/x86_64-linux-gnu/libpulsecommon-1.0.so
   pa_pstream_unlink () from /usr/lib/x86_64-linux-gnu/libpulsecommon-1.0.so
   ?? () from /usr/lib/pulse-1.0/modules/libprotocol-native.so
   ?? () from /usr/lib/pulse-1.0/modules/libprotocol-native.so
  Title: pulseaudio crashed with SIGABRT in pa_memimport_free()
  UpgradeStatus: Upgraded to oneiric on 2011-09-01 (74 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare sudo
  XsessionErrors:
   (gnome-shell:2192): Clutter-WARNING **: Attempting to add actor of type 
'ShellGenericContainer' to a container of type 'StBoxLayout', but the actor has 
already a parent of type 'StBoxLayout'.
   (dropbox:2299): Gdk-CRITICAL **: 
IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion 
`private->update_and_descendants_freeze_count > 0' failed
   (process:4796): Gtk-WARNING **: Locale not supported by C library.
  dmi.bios.date: 03/09/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CCU Ver. F.12
  dmi.board.name: 172B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 30.31
  dmi.chassis.asset.tag: CZC0126G5J
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CCUVer.F.12:bd03/09/2011:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172B:rvrKBCVersion30.31:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8440p
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1768291] [NEW] lirc is flooding the syslog with two lines each second

2018-05-01 Thread Gert Brinkmann

Public bug reported:

Hello,

in the syslog every second two lines are written:

May  1 18:05:19 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:19 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:20 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:20 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:21 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:21 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:22 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:22 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:23 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:23 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:24 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:24 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:25 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:25 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:26 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:26 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:27 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:27 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:28 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:28 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*

This is not only annoying as it makes it difficult to use the syslog for
checking the system, but also it writes too much data into the log (18MB
each day). Also it keeps the hard disc awaken what is bad for standby.

Kubuntu 18.04
ii  liblirc-client0:amd64 0.10.0-2 amd64infra-red remote control 
support - client library
ii  liblirc0:amd640.10.0-2 amd64Infra-red remote control 
support - Run-time libraries
ii  lirc  0.10.0-2 amd64Infra-red remote control 
support - daemons and utils

I do not have infrared remote control hardware. But I cannot purge the
packages as other packages I want to keep would be removed as well.
Deactivating the services in systemd does not help (or I am doing
something wrong?)

Greetings
Gert

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

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

Title:
  lirc is flooding the syslog with two lines each second

Status in lirc package in Ubuntu:
  New

Bug description:
  Hello,

  in the syslog every second two lines are written:

  May  1 18:05:19 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:19 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:20 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:20 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:21 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:21 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:22 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:22 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:23 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:23 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:24 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:24 flupp lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:25 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob 
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:25

[Desktop-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

2018-05-01 Thread Camilo

Doesn't work on my Lenovo Y700-17ISK

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1731341] Re: Fujifilm X-T10 regression on 17.10: "Unable to fetch previews from the camera: Unspecified error (-1)"