date:20180516

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

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

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

Title:
  driverless printing generates wrong language/encoding PPD

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  The printing option dialog (see attached PNG file) is broken with Bionic 
Japanese environment.
  This issue seems to be coming from the generated PPD file with wrong 
language/encoding.

  I tried with Epson EP-879AW.

  Steps to reproduce:

  1) generate a print queue by driverless feature with ja-JP locale:

  $ LANG-ja_JP.UTF-8 lpadmin -p driverlesstest-ja -E -v `driverless` -m
  everywhere

  2) check the generated PPD (attached driverlesstest-ja.ppd)

  $ sudo less /etc/cups/ppd/driverlesstest-ja.ppd

  Expected: PPD have same language/encoding with content (if the content
  have Japanese, language/encoding should be Japanese/UTF-8)

  Actual: PPD has Japanese strings, but language/encoding is
  English/ISOLatin1

  
  
  Attached files:
   
  EPSON_EP_879A_Series_007.png: screenshot of printing option dialog of 
EP-879AW driverless print queue
  driverless-ja.ppd: PPD generated with ja_JP.UTF-8 locale
  driverless-en.ppd: PPD generated with C locale
  ipptool.txt: output of ipptool, by following command:

  $ ipptool -tv `driverless` get-printer-attributes.test > ipptool.txt

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

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

[Desktop-packages] [Bug 1771716] Re: Resuming resets my session

2018-05-16 Thread Nicolas_Raoul

Thanks Daniel!
1. Done, commented out the line in /etc/apport/crashdb.conf
2. It was already set to enabled=1
3. Done, commented out the line in /etc/gdm3/custom.conf
4. Doing it after posting this
5. OK, I will continue next time the bug happens, it might take a week or so :-)

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

Title:
  Resuming resets my session

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I installed 18.04 from scratch a day after it got released.

  Twice per day I close the lid of my laptop and open it again after.
  Usually it immediately asks me for the password and brings me back to
  what I was doing.

  But 3 times so far, it took a minute before showing me a login screen
  (like if I had not yet a session) asking me to choose my user (there
  is only one user), then enter my password. It then starts to load...
  and asks me for my password AGAIN. Then it shows my desktop, but
  everything I was doing before is gone, no more open windows. When I
  start Firefox it asks me whether I want to restore my tabs. When I
  open Byobu it shows my tabs as I left them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 17 11:27:19 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo HD Graphics 5500 [17aa:2223]
  InstallationDate: Installed on 2018-04-29 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20CKCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET34W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CKCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET34W(1.10):bd08/20/2015:svnLENOVO:pn20CKCTO1WW:pvrThinkPadT550:rvnLENOVO:rn20CKCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CKCTO1WW
  dmi.product.version: ThinkPad T550
  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-server/+bug/1771716/+subscriptions

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

[Desktop-packages] [Bug 1771716] Re: Resuming resets my session

2018-05-16 Thread Nicolas_Raoul

** Description changed:

  I installed 18.04 from scratch a day after it got released.
  
  Twice per day I close the lid of my laptop and open it again after.
  Usually it immediately asks me for the password and brings me back to
  what I was doing.
  
- But 3 times so far, it took a minute before showing me a logging screen
+ But 3 times so far, it took a minute before showing me a login screen
  (like if I had not yet a session) asking me to choose my user (there is
  only one user), then enter my password. It then starts to load... and
  asks me for my password AGAIN. Then it shows my desktop, but everything
  I was doing before is gone, no more open windows. When I start Firefox
  it asks me whether I want to restore my tabs. When I open Byobu it shows
  my tabs as I left them.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 17 11:27:19 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
-Subsystem: Lenovo HD Graphics 5500 [17aa:2223]
+  Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
+    Subsystem: Lenovo HD Graphics 5500 [17aa:2223]
  InstallationDate: Installed on 2018-04-29 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20CKCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET34W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CKCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET34W(1.10):bd08/20/2015:svnLENOVO:pn20CKCTO1WW:pvrThinkPadT550:rvnLENOVO:rn20CKCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CKCTO1WW
  dmi.product.version: ThinkPad T550
  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

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

Title:
  Resuming resets my session

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I installed 18.04 from scratch a day after it got released.

  Twice per day I close the lid of my laptop and open it again after.
  Usually it immediately asks me for the password and brings me back to
  what I was doing.

  But 3 times so far, it took a minute before showing me a login screen
  (like if I had not yet a session) asking me to choose my user (there
  is only one user), then enter my password. It then starts to load...
  and asks me for my password AGAIN. Then it shows my desktop, but
  everything I was doing before is gone, no more open windows. When I
  start Firefox it asks me whether I want to restore my tabs. When I
  open Byobu it shows my tabs as I left them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 17 11:27:19 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA

[Desktop-packages] [Bug 1771716] Re: Resuming resets my session

Actually asking for the password twice in "then enter my password. It
then starts to load..." might also be another shell/session crash.
Regardless, please follow the above instructions.

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

Title:
  Resuming resets my session

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I installed 18.04 from scratch a day after it got released.

  Twice per day I close the lid of my laptop and open it again after.
  Usually it immediately asks me for the password and brings me back to
  what I was doing.

  But 3 times so far, it took a minute before showing me a login screen
  (like if I had not yet a session) asking me to choose my user (there
  is only one user), then enter my password. It then starts to load...
  and asks me for my password AGAIN. Then it shows my desktop, but
  everything I was doing before is gone, no more open windows. When I
  start Firefox it asks me whether I want to restore my tabs. When I
  open Byobu it shows my tabs as I left them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 17 11:27:19 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo HD Graphics 5500 [17aa:2223]
  InstallationDate: Installed on 2018-04-29 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20CKCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET34W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CKCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET34W(1.10):bd08/20/2015:svnLENOVO:pn20CKCTO1WW:pvrThinkPadT550:rvnLENOVO:rn20CKCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CKCTO1WW
  dmi.product.version: ThinkPad T550
  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-server/+bug/1771716/+subscriptions

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

[Desktop-packages] [Bug 1771716] Re: Resuming resets my session

Sounds like you have two bugs.

Asking for the password twice is bug 1765261.

But it sounds like you also have a crash causing your lost session so...

-

Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your bug report is missing crash details. In
order to debug a crash we will need a crash report. To create one,
please follow these steps:

1. If you are not running a future development release of Ubuntu then apply the 
workaround from bug 994921.
2. If you are running the Ubuntu Stable Release you might need to enable apport 
in /etc/default/apport.
3. If the crash is in Xorg then uncomment this option from 
/etc/gdm3/custom.conf:
   # Additionally lets the X server dump core if it crashes
   #Enable=true
4. Reboot.
5. Reproduce the crash.
6. Look in /var/crash for crash files and when found, run:
   ubuntu-bug /var/crash/YOURFILE.crash
7. Add a comment here telling us the ID of the new bug that was created in step 
6.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments, and doing so is also a
security risk for yourself.

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  Resuming resets my session

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I installed 18.04 from scratch a day after it got released.

  Twice per day I close the lid of my laptop and open it again after.
  Usually it immediately asks me for the password and brings me back to
  what I was doing.

  But 3 times so far, it took a minute before showing me a login screen
  (like if I had not yet a session) asking me to choose my user (there
  is only one user), then enter my password. It then starts to load...
  and asks me for my password AGAIN. Then it shows my desktop, but
  everything I was doing before is gone, no more open windows. When I
  start Firefox it asks me whether I want to restore my tabs. When I
  open Byobu it shows my tabs as I left them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 17 11:27:19 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo HD Graphics 5500 [17aa:2223]
  InstallationDate: Installed on 2018-04-29 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20CKCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET34W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CKCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET34W(1.10):bd08/20/2015:svnLENOVO:pn20CKCTO1WW:pvrThinkPadT550:rvnLENOVO:rn20CKCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CKCTO1WW
  dmi.product.version: ThinkPad T550
  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-server/+bug/1771716/+subscriptions

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

[Desktop-packages] [Bug 1755326] Re: Periodic glitch in sound with Firewire and snd-dice

2018-05-16 Thread Takashi Sakamoto

Please refer to my report in upstream:
http://mailman.alsa-project.org/pipermail/alsa-devel/2016-May/107715.html

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

Title:
Periodic glitch in sound with Firewire and snd-dice

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

Bug description:
I have a fresh installation of Ubuntu 17.10 with almost nothing extra
installed yet besides Bitwig Studio, Cadence and a few other things
from the KX Studio repositories.

But I also tried the bug after a fresh install with nothing else than
Bitwig Studio installed, it's the same.

Not sure if this information can be added afterwards: but I installed
the 3.19.8 low latency kernel, and the problem disappeared. On 17.1 I
can't use the current low latency kernel because the system becomes
very unresponsive to the point of being hard to even log in. So I'm
not sure if this is just a matter of difference between the low
latency and regular kernels.

I have a TC Electronics Impact Twin Firewire audio interface.
It is connected to a Iocrest SY-PEX30016 PCI-E card, which has a Texas
Instruments XIO2213BZAY chipset.

The ALSA snd-dice drivers work, but with glitches.

There is a periodic, glitch in the sound that sounds like a part of the
stream is missing, or something. It is steady in timing, nothing seems to have
an effect on it.
Recording seems to work. All outputs and inputs, also the ADAT outputs seem
to work, altough I could not test if the ADAT outputs feature the glitch too.

Seemingly randomly there might be a short maybe around 0.3 second
total break in the sound.

I'm not getting xruns at all.

I tried also Ubuntu Studio live USB, it has the exact same glitch. I
also tried a Native Instruments Audio2DJ USB interface, with that
there is no problem with the sound on my computer.

I tried also with Carla and ZynAddSubFx, and also with the live USB of
Linux Mint (current version), and the same glitch is present.

I tried also another Firewire controller card with a XIO2200A Texas
Instruments chip, it features the same glitch, but running a different
speed.

I had a KX Studio 14.x installation a few years ago, where the
interface was working without a hitch. But then I was running with
FFADO.

So to me it seems that the kernel integration of snd-dice has some
problem with timing with a TC Electronics interface?

I could not get FFADO to run with Jack now so I can't say if the FFADO
implementation would work.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3.1
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC4D0c: kim3563 F...m jackdbus
/dev/snd/pcmC4D0p: kim3563 F...m jackdbus
/dev/snd/controlC4: kim3563 F jackdbus
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 13 02:11:51 2018
InstallationDate: Installed on 2018-03-12 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/12/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2603
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 EVO R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd02/12/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.
---
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp',
'/dev/snd/hwC3D0', '/dev/snd/midiC3D0', '/dev/snd/pcmC3D0c',
'/dev/snd/pcmC3D0p', '/dev/snd/controlC3', '/dev/snd/by-path',
'/dev/snd/by-id', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0',
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/midiC2D0',
'/dev/snd/controlC2', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice:

[Desktop-packages] [Bug 1770238] Re: [nvidia] Logging in results in a black screen for many minutes after which the login screen reappears and I am able to login fine.

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

Thanks for pointing that out. The error you mention is actually right
before bug 1543192 happens to you:

May 9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE) 
Screen(s) found, but none have a usable configuration.
May 9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE)
May 9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: Fatal server 
error:
May 9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE) no 
screens found(EE)

So still bug 1543192. Maybe worth commenting on that one about the
above.

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

Title:
  [nvidia] Logging in results in a black screen for many minutes after
  which the login screen reappears and I am able to login fine.

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  ** Ubuntu Bionic; Nvidia GTX 1050 w/`nvidia-390` drivers

  ** Problem: Logging in results in a black screen for many minutes after which 
the login screen reappears and I am able to login fine. The below log seems to 
be the earliest error when this occurs.
  Note: This happened twice today so far, presumably each time I reboot.

  
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE) 
NVIDIA(GPU-0): Failed to acquire modesetting permission.
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE) 
NVIDIA(0): Failing initialization of X screen 0
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (II) 
UnloadModule: "nvidia"
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (II) 
UnloadSubModule: "wfb"
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (II) 
UnloadSubModule: "fb"
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE) 
Screen(s) found, but none have a usable configuration.
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE)
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: Fatal 
server error:
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE) no 
screens found(EE)
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE)

  ** A systemd-logind watchdog seems to be responsible for the login
  screen reappearing

  May  9 11:20:02 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Watchdog 
timeout (limit 3min)!
  May  9 11:20:02 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Killing 
process 1697 (systemd-logind) with signal SIGABRT.
  May  9 11:20:03 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Main 
process exited, code=dumped, status=6/ABRT
  May  9 11:20:03 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Failed 
with result 'watchdog'.

  ** The Xorg.0.log doesn't seem to have any problem finding the screens
  just before the above error.

  29406:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(II) NVIDIA(0): NVIDIA GPU GeForce GTX 1050 (GP107-A) at PCI:23:0:0 (GPU-0)
  29407:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(--) NVIDIA(0): Memory: 2097152 kBytes
  29408:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(--) NVIDIA(0): VideoBIOS: 86.07.2f.00.68
  29409:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(II) NVIDIA(0): Detected PCI Express Link width: 16X
  29412:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(--) NVIDIA(GPU-0): Acer AL1917 (DFP-0): connected
  29413:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(--) NVIDIA(GPU-0): Acer AL1917 (DFP-0): Internal TMDS
  29414:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(--) NVIDIA(GPU-0): Acer AL1917 (DFP-0): 330.0 MHz maximum pixel clock
  29415:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(--) NVIDIA(GPU-0):

  
  ** Note that I also saw the watchdog kick in while I was logged in and 
working when I was suddenly sent back to the login screen.  I believe that 
lines up with the syslog timestamp below:

  
  May  9 10:31:24 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Watchdog 
timeout (limit 3min)!
  May  9 10:31:24 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Killing 
process 1691 (systemd-logind) with signal SIGABRT.
  May  9 10:31:25 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Main 
process exited, code=dumped, status=6/ABRT
  May  9 10:31:25 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Failed 
with result 'watchdog'.
  May  9 10:31:25 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2607]: (EE)
  May  9 10:31:25 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2607]: Fatal 
server

[Desktop-packages] [Bug 1631859] Re: brightness, contrast, quality for Canon LIDE 60 ill defined

** Tags added: bionic

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

Title:
  brightness, contrast, quality for Canon LIDE 60 ill defined

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  I'm using a Canon Lide 60 scanner in combination with Simple Scan 3.20.0 on 
Xubuntu 16.04 .
  Appearently someone mixed up the direction of the sliders, i.e. if you want 
to scan darker you now have to move the slider towards "brighter". Same with 
"contrast".
  For "quality" the best setting is the center position. Moving the slider 
either left or right reduces quality.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: simple-scan 3.20.0-0ubuntu1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic 
root=UUID=7676a384-03c7-40eb-a188-e11cae60a27c ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.30
  dmi.board.name: Q1900-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd07/07/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnQ1900-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1755326] Re: Periodic glitch in sound with Firewire and snd-dice

2018-05-16 Thread Takashi Sakamoto

Please refer to my report in upstream:
http://mailman.alsa-project.org/pipermail/alsa-devel/2016-May/107715.html

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

Title:
Periodic glitch in sound with Firewire and snd-dice

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

Bug description:
I have a fresh installation of Ubuntu 17.10 with almost nothing extra
installed yet besides Bitwig Studio, Cadence and a few other things
from the KX Studio repositories.

But I also tried the bug after a fresh install with nothing else than
Bitwig Studio installed, it's the same.

I have a TC Electronics Impact Twin Firewire audio interface.
It is connected to a Iocrest SY-PEX30016 PCI-E card, which has a Texas
Instruments XIO2213BZAY chipset.

The ALSA snd-dice drivers work, but with glitches.

Seemingly randomly there might be a short maybe around 0.3 second
total break in the sound.

I'm not getting xruns at all.

I tried also Ubuntu Studio live USB, it has the exact same glitch. I
also tried a Native Instruments Audio2DJ USB interface, with that
there is no problem with the sound on my computer.

I tried also with Carla and ZynAddSubFx, and also with the live USB of
Linux Mint (current version), and the same glitch is present.

I tried also another Firewire controller card with a XIO2200A Texas
Instruments chip, it features the same glitch, but running a different
speed.

I had a KX Studio 14.x installation a few years ago, where the
interface was working without a hitch. But then I was running with
FFADO.

So to me it seems that the kernel integration of snd-dice has some
problem with timing with a TC Electronics interface?

I could not get FFADO to run with Jack now so I can't say if the FFADO
implementation would work.

[Desktop-packages] [Bug 1771716] [NEW] Resuming resets my session

2018-05-16 Thread Nicolas_Raoul

Public bug reported:

I installed 18.04 from scratch a day after it got released.

Twice per day I close the lid of my laptop and open it again after.
Usually it immediately asks me for the password and brings me back to
what I was doing.

But 3 times so far, it took a minute before showing me a logging screen
(like if I had not yet a session) asking me to choose my user (there is
only one user), then enter my password. It then starts to load... and
asks me for my password AGAIN. Then it shows my desktop, but everything
I was doing before is gone, no more open windows. When I start Firefox
it asks me whether I want to restore my tabs. When I open Byobu it shows
my tabs as I left them.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xserver-xorg-core 2:1.19.6-1ubuntu4
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
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu May 17 11:27:19 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 5500 [17aa:2223]
InstallationDate: Installed on 2018-04-29 (17 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20CKCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/20/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: N11ET34W (1.10 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20CKCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET34W(1.10):bd08/20/2015:svnLENOVO:pn20CKCTO1WW:pvrThinkPadT550:rvnLENOVO:rn20CKCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T550
dmi.product.name: 20CKCTO1WW
dmi.product.version: ThinkPad T550
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

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

Title:
  Resuming resets my session

Status in xorg-server package in Ubuntu:
  New

Bug description:
  I installed 18.04 from scratch a day after it got released.

  Twice per day I close the lid of my laptop and open it again after.
  Usually it immediately asks me for the password and brings me back to
  what I was doing.

  But 3 times so far, it took a minute before showing me a logging
  screen (like if I had not yet a session) asking me to choose my user
  (there is only one user), then enter my password. It then starts to
  load... and asks me for my password AGAIN. Then it shows my desktop,
  but everything I was doing before is gone, no more open windows. When
  I start Firefox it asks me whether I want to restore my tabs. When I
  open Byobu it shows my tabs as I left them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 17 11:27:19 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:2223]
  InstallationDate: Installed on 2018-04-29 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO

[Desktop-packages] [Bug 1771713] [NEW] Network Manager doesn't lits created connection in 18.04.

2018-05-16 Thread Jo

Public bug reported:

Tried Ubuntu, Xubuntu, Ubuntu Budgie? Ubuntu Mate, Lubuntu. 
But doesn't affect Kubuntu.
I tired to create DSL/pppoe connection.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.6-2ubuntu1
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: XFCE
Date: Thu May 17 05:59:14 2018
InstallationDate: Installed on 2018-05-16 (0 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IpRoute:
 default dev ppp0 scope link 
 10.94.255.190 dev ppp0 proto kernel scope link src 46.0.29.255
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=false
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME  UUID  TYPE   TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH 
  ACTIVE  DEVICE  STATE  ACTIVE-PATH  SLAVE 
 DSL connection 1  fdbddcec-2e10-40c1-b6f7-ce93c7dc605a  pppoe  1526515179  Чт 
17 мая 2018 03:59:39  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  no  --  -- --   
--
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
 wlp6s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/4  --   
   ----   
 enp7s0  ethernet  unmanaged/org/freedesktop/NetworkManager/Devices/2  --   
   ----   
 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  --   
   ----   
 ppp0ppp   unmanaged/org/freedesktop/NetworkManager/Devices/3  --   
   ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
WWAN-HW  WWAN
 running  1.10.6   connected  started  unknown   enabled enabled  
disabled  enabled  enabled

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


** Tags: amd64 apport-bug bionic

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

Title:
  Network Manager doesn't lits created connection in 18.04.

Status in network-manager package in Ubuntu:
  New

Bug description:
  Tried Ubuntu, Xubuntu, Ubuntu Budgie? Ubuntu Mate, Lubuntu. 
  But doesn't affect Kubuntu.
  I tired to create DSL/pppoe connection.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  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: XFCE
  Date: Thu May 17 05:59:14 2018
  InstallationDate: Installed on 2018-05-16 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default dev ppp0 scope link 
   10.94.255.190 dev ppp0 proto kernel scope link src 46.0.29.255
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID  TYPE   TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH 
  ACTIVE  DEVICE  STATE  ACTIVE-PATH  SLAVE 
   DSL connection 1  fdbddcec-2e10-40c1-b6f7-ce93c7dc605a  pppoe  1526515179  
Чт 17 мая 2018 03:59:39  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  no  --  -- --   
--
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
   wlp6s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/4  -- 
 ----   
   enp7s0  ethernet  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
   ppp0ppp   unmanaged/org/freedesktop/NetworkManager/Devices/3  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  unknown   enabled enabled  
disabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1771661] Re: After updating to 18.04 only Wayland works. Cannot get Xorg to work on Gnome

It sounds like you might have two different bugs, if the purple screen
is bug 1766137.

Please:

1. Run this command to attach more information: apport-collect 1771661

2. Run 'lspci -k' and attach its output here.

3. Copy /proc/cmdline and attach it here.


** Tags added: bionic nvidia

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

** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Incomplete

** Summary changed:

-  After updating to 18.04 only Wayland works. Cannot get Xorg to work on Gnome
+ [nvidia] After updating to 18.04 only Wayland works. Cannot get Xorg to work 
on Gnome

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

Title:
  [nvidia] After updating to 18.04 only Wayland works. Cannot get Xorg
  to work on Gnome

Status in gdm3 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  I recently updated to Ubuntu 18.04. After updating I can only log into
  Gnome if I select Gnome or Ubuntu with Wayland at my login screen.
  Nothing I can do will allow me tuse Xorg. I tried reinstalling Xorg
  and reinstalling my video driver (nvidia-390) . If I select Ubuntu
  with Xorg at login I get a purple screen and frozen mouse. If I set
  etting |WaylandEnable=false| in |/etc/gdm/custom.conf| I cannot get to
  the login screen. The system freezes.

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

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

[Desktop-packages] [Bug 1771273] Re: Gnome-shell crashes when wake up after updated to 3.28.1-0ubuntu2

If you are using Wayland then ignore step 3 :)

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

Title:
  Gnome-shell crashes when wake up after updated to 3.28.1-0ubuntu2

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  After having updated gnome-shell from 3.28.1-0ubuntu1 to 3.28.1-0ubuntu2, 
I've experienced the gnome-shell crash after every time I wake it up. It seems 
that it has killed my session.
  When I wakes my computer up, it shows the very first message usually only 
appear when starting the computer, like starting the snappy daemon, starting 
mysql server, etc.

  I'm using Ubuntu 18.04 LTS, Gnome-shell, Wayland.

  Please tell me what information I need to provide to confirm this bug.
  Thanks.

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

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

[Desktop-packages] [Bug 1771466] Re: Super+D wrongly leaves windows minimized if a new window appears while in "hiding" state

** Description changed:

+ https://gitlab.gnome.org/GNOME/gnome-shell/issues/282
+ 
+ ---
+ 
  Toggling Super+D hides or un-hides all windows so you can access icons
  on the desktop.
  
  But this breaks if a new window appears while the windows are hidden:
  They become PERMANENTLY hidden, i.e. Super+D does not restore them.
  They seem to be "minimized" -- you have to individually un-minimize each
  window to get your session back.
  
  This is very annoying, and is common: The only reason for using Super+D
  is to see something on the desktop; probably you then need to do
  something with it, i.e. click it.  If that action opens a new window,
  which is almost certain, you're hosed.
  
  STEPS TO REPRODUCE:
  
  1. Open a bunch of windows and artfully arrange them.
  2. Type Super+D (they all become hidden)
  3. Double-click the "Trash" desktop icon and wait for a file browser to open.
  
  RESULTS: Once the file-viewer opens, Super+D will not restore the
  previously-hidden windows.  Instead, it seems to forget about them and
  instead hide the new window (and un-hide it if pressed a second time
  --before yet another window is opened, of course).
  
- EXPECTED RESULTS: 
-The state should be well-defined: Either normal or windows-hidden.  
-Once in the windows-hidden state, Super-D should un-hide the hidden 
windows e
-ven if new windows have been created in the interim.
+ EXPECTED RESULTS:
+    The state should be well-defined: Either normal or windows-hidden.
+    Once in the windows-hidden state, Super-D should un-hide the hidden 
windows e
+    ven if new windows have been created in the interim.
  
  SUGGESTED FIX:
  1. (preferred): On the first Super+D, hide all windows and remember their 
IDs.  On the next Super+D, un-hide just those windows, if they still exist, and 
do nothing at all with any other windows which might be present (i.e. new 
ones).   Then return to the initial state, where Super+D hides all visible 
windows.
  
  2. (if the above is too hard to implement): If a new window appears
  while in the "hiding" state, make the new window immediately become
  hidden also; only on the second Super+D would the new window become
  visible along with the old ones.
  
  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 15 16:40:22 2018
  DisplayManager: gdm3
  GsettingsChanges:
-  b'org.gnome.shell' b'enabled-extensions' b"['keepaw...@jepfa.de', 
'rece...@leonardo.bartoli.gmail.com', 
'drive-m...@gnome-shell-extensions.gcampax.github.com', 
'sound-output-device-choo...@kgshank.net', 'suspend-button@laserb', 
'systemmoni...@gnome-shell-extensions.gcampax.github.com', 
'workspaces-to-d...@passingthru67.gmail.com']"
-  b'org.gnome.shell' b'favorite-apps' redacted by apport
-  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+  b'org.gnome.shell' b'enabled-extensions' b"['keepaw...@jepfa.de', 
'rece...@leonardo.bartoli.gmail.com', 
'drive-m...@gnome-shell-extensions.gcampax.github.com', 
'sound-output-device-choo...@kgshank.net', 'suspend-button@laserb', 
'systemmoni...@gnome-shell-extensions.gcampax.github.com', 
'workspaces-to-d...@passingthru67.gmail.com']"
+  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-05 (40 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Super+D wrongly  leaves windows minimized if a new window appears
  while in "hiding" state

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/282

  ---

  Toggling Super+D hides or un-hides all windows so you can access icons
  on the desktop.

  But this breaks if a new window appears while the windows are hidden:
  They become PERMANENTLY hidden, i.e. Super+D does not restore them.
  They seem to be "minimized" -- you have to individually un-minimize
  each window to get your session back.

  This is very annoying, and is common: The only reason for using
  Super+D is to see something on the desktop; probably you then need to
  do something with it, i.e. click it.  If that action opens a new
  window, which is almost certain, you're hosed.

  STEPS TO REPRODUCE:

  1. Open a bunch of windows and artfully arrange them.
  2. Type Super+D (they all become hidden)
  3. Double-click the "Trash" desktop icon and wait for a file browser to open.

  RESULTS: Once the

[Desktop-packages] [Bug 1365393] Re: Cropping tool does not function

Have you tried a double-click on the area selected to be cropped?

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

Title:
  Cropping tool does not function

Status in simple-scan package in Ubuntu:
  New

Bug description:
  Cropping tool allows me to select area of scanend photo on page.
  However. according to help file the outer area should be grayed out
  which it isn't.  Unable to actually execute the cropping of selection
  on a HP L:aserjet 4570c.  Pressing enter, clicking off with my mouse
  or pressing save does not work. USing Ububtu 14.04 using SANE backend
  sane-hp5590.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: simple-scan 3.12.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep  4 04:00:58 2014
  DriverPackageVersions:
   libsane 1.0.23-3ubuntu3.1
   libsane-extras 1.0.22.3ubuntu1
   hplip 3.14.3-0ubuntu3.2
   hpoj N/A
  InstallationDate: Installed on 2014-02-27 (188 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Hewlett-Packard HP Compaq dx2400 Microtower PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-35-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to trusty on 2014-05-11 (115 days ago)
  dmi.bios.date: 01/12/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.36
  dmi.board.name: 2A73h
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: 2UA9120FWC
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.36:bd01/12/2009:svnHewlett-Packard:pnHPCompaqdx2400MicrotowerPC:pvr:rvnPEGATRONCORPORATION:rn2A73h:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.name: HP Compaq dx2400 Microtower PC
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1179165] Re: Simple scan should allow "copy to clipboard" of a document (Patch included)

** Changed in: simple-scan (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Simple scan should allow "copy to clipboard" of a document (Patch
  included)

Status in Simple Scan:
  Fix Released
Status in simple-scan package in Ubuntu:
  Fix Released

Bug description:
  Simple scan should include a "copy to clipboard" option to directly copy a 
scanned page (or a portion of it) to the clipboard.
  Use case: use simple scan to get an image, copy it, and paste directly in 
Libreoffice.

  The included patch implements this new option (tested on simple scan
  3.6.1)

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

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

[Desktop-packages] [Bug 1658620] Re: Memory leak when scanning and deleting pages

In my experience in bionic, the memory isn't even freed when starting a
new document with Ctrl+N.  The memory usage simply keeps ballooning with
every additional page scanned.

** Changed in: simple-scan (Ubuntu)
   Importance: Undecided => Medium

** Changed in: simple-scan (Ubuntu)
   Status: New => Confirmed

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

Title:
  Memory leak when scanning and deleting pages

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  To reproduce:
  1. Scan a few pages
  2. Note the memory useage
  3. Delete those pages (right click delete)
  4. Note the memory useage

  You can repeat those steps and note that the more and more memory is
  being used, even after you delete those pages. The memory doesn't get
  freed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: simple-scan 3.20.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jan 23 12:10:01 2017
  InstallationDate: Installed on 2015-01-19 (734 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  MachineType: ASUSTeK COMPUTER INC. N76VB
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (177 days ago)
  dmi.bios.date: 05/24/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N76VB.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N76VB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN76VB.205:bd05/24/2013:svnASUSTeKCOMPUTERINC.:pnN76VB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN76VB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N76VB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1379531] Re: "Combine sides" should be "combine pages"?

When searching for "side" in launchpad translations it appears that the
author by "sides" means "front/back side".  Simply replacing sides by
pages does not seem to be the best wording, either, IMO.

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

Title:
  "Combine sides" should be "combine pages"?

Status in Ubuntu Translations:
  Invalid
Status in simple-scan package in Ubuntu:
  New

Bug description:
  Combine sides
  and
  Combine sides (reverse)

  look like a German speaker with poor English mistranslated 'Seiten' as
  'sides' rather than 'pages'?

   Located in ../src/ui.vala:1204 
   Located in ../src/ui.vala:1214

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

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

[Desktop-packages] [Bug 1327801] Re: Bightness and contrast settings have no effect

I cannot confirm this in bionic with a Canon LiDE 35.

If you are still affected in bionic or later, please speak up.

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

Title:
  Bightness and contrast settings have no effect

Status in simple-scan package in Ubuntu:
  Triaged

Bug description:
  Scanner: Canon, Inc. CanoScan N1240U/LiDE 30
  Ubuntu 14.04, Simple Scan version 3.12.1.

  Adjusting the settings of brightness and contrast has no effect.

  With the default for scanning in "text" mode being too bright, this makes 
"Simple Scan" in text mode unusable for me.
  Brightness and contrast settings don't work in "foto" mode, too. But the 
default of the foto mode is usable.

  Brightness setting does work in program "Skanlite".

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

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

[Desktop-packages] [Bug 1449671] Re: manpage for simple scan assumes there is an application menu

** Changed in: simple-scan (Ubuntu)
   Importance: Medium => Low

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

Title:
  manpage for simple scan assumes there is an application menu

Status in simple-scan package in Ubuntu:
  Triaged

Bug description:
  To reproduce in terminal run man simple-scan. Then read the man pages and 
notice it saysSimple  Scan has been written with GTK+ libraries, and 
after installing
 the application you can run it from the Applications menu.

  
  But lubuntu and now ubuntu with unity don't really have an applications menu 
to run it from but ubuntu-mate does. simple-scan:
Installed: 3.16.1.1-0ubuntu1
Candidate: 3.16.1.1-0ubuntu1
Version table:
   *** 3.16.1.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status
  Description:  Ubuntu 15.04
  Release:  15.04

  
  I expected the man page for simple scan to be applicable to all desktop 
environments not just like how it was in gnome 2 days years ago.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: simple-scan 3.16.1.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Tue Apr 28 10:03:55 2015
  InstallationDate: Installed on 2014-09-30 (209 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140930)
  JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] 
failed with exit code 1: No journal files were found.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic 
root=UUID=fa3d31ba-9fc4-4678-a8aa-8d59172ca54a ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf 
nomdmonisw
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to vivid on 2014-12-12 (136 days ago)
  dmi.bios.date: 04/25/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.00
  dmi.board.name: H97M Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd04/25/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

Re: [Desktop-packages] [Bug 1771394] Re: gvfsd-mtp hoovers up all memory

2018-05-16 Thread Bill Miller

Thanks, I'll give it a try, although I use adb on the host, maybe I can 
disable it, if that's what's causing the issue.

On 05/16/2018 07:57 PM, Steve Childs wrote:
> I just experienced this too. If you don't need them, remove the adb
> files from ubuntu, if you're passing the USB device onto the guest OS,
> you don't need them anyway.
>
> FYI, I followed an install guide online, so just reversed the install
> line, e.g.
>
> sudo apt-get remove android-tools-adb android-tools-fastboot
>
> Sorry if its teaching you to suck eggs, I've just included it for others
> if they stumble over the same issue.
>

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

Title:
  gvfsd-mtp hoovers up all memory

Status in gvfs package in Ubuntu:
  New

Bug description:
  When I run a Win7 Virtual Machine and attach my smartphone via USB (to
  run Samsung Smart Switch on the VM) gvfsd-mtp sucks up all of my
  16G(!) of RAM and the system becomes unresponsive.

  This same workflow worked without issue in 14.04 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-backends 1.36.1-0ubuntu1
  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: LXDE
  Date: Tue May 15 12:02:25 2018
  InstallationDate: Installed on 2018-04-27 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1769977] Re: jackd2 don't install in fresh installation of Ubuntu 18.04 LTS

2018-05-16 Thread Esteban

Ok.. My mistake... It's happened because isn't a fresh install.. jackd
install fail after add kxstudio repository. Where is the matter.

Thanks and sorry for the noise! :)

** Changed in: jackd2 (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  jackd2 don't install in fresh installation of Ubuntu 18.04 LTS

Status in jackd2 package in Ubuntu:
  Invalid

Bug description:
  jackd2 package don't install in Ubuntu 18.04 LTS.

  Broken dependencies, libreadline6 can't be installed anymore.

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

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

[Desktop-packages] [Bug 1771394] Re: gvfsd-mtp hoovers up all memory

2018-05-16 Thread Steve Childs

I just experienced this too. If you don't need them, remove the adb
files from ubuntu, if you're passing the USB device onto the guest OS,
you don't need them anyway.

FYI, I followed an install guide online, so just reversed the install
line, e.g.

sudo apt-get remove android-tools-adb android-tools-fastboot

Sorry if its teaching you to suck eggs, I've just included it for others
if they stumble over the same issue.

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

Title:
  gvfsd-mtp hoovers up all memory

Status in gvfs package in Ubuntu:
  New

Bug description:
  When I run a Win7 Virtual Machine and attach my smartphone via USB (to
  run Samsung Smart Switch on the VM) gvfsd-mtp sucks up all of my
  16G(!) of RAM and the system becomes unresponsive.

  This same workflow worked without issue in 14.04 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-backends 1.36.1-0ubuntu1
  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: LXDE
  Date: Tue May 15 12:02:25 2018
  InstallationDate: Installed on 2018-04-27 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

** Changed in: gdm
   Status: In Progress => Fix Released

-- 
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:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in gdm3 source package in Bionic:
  Confirmed
Status in gnome-shell source package in Bionic:
  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 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

2018-05-16 Thread Peter Bennett

Brother DCP-7065DN Network Printer & scanner. I just installed Bionic
alongside Xenial. Printer works fine on bionic with the brother drivers
but the scanner is not found. The scanner works with Xenial. For xenial,
after installing the Brother drivers, I had created links using "sudo ln
-sf /usr/lib64/sane/libsane-brother4.so* /usr/lib/sane/". I ran that on
bionic and the scanner is still not found.

-- 
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 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

2018-05-16 Thread aeronutt

FYI, I (temporarily?) switched to SDDM, so far so good (although a bit
cumbersome as delivered). It also allows Wayland sessions.

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

Status in gdm:
  In Progress
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in gdm3 source package in Bionic:
  Confirmed
Status in gnome-shell source package in Bionic:
  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 1768541] Update Released

2018-05-16 Thread Brian Murray

The verification of the Stable Release Update for gnome-keyring has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

Status in gnome-keyring package in Ubuntu:
  Fix Released
Status in gnome-keyring source package in Bionic:
  Fix Released

Bug description:
  installation of this package failed, upgrading from 17.10.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libp11-kit-gnome-keyring 3.20.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
  Date: Wed May  2 01:39:47 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DuplicateSignature:
   package:libp11-kit-gnome-keyring:3.20.1-1ubuntu1
   Unpacking gnome-keyring (3.28.0.2-1ubuntu1) over (3.20.1-1ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-PlRQuy/0830-libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1_all.deb
 (--unpack):
libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not 
co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances
  ErrorMessage: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) 
is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  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: gnome-keyring
  Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to 
install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: 
no) is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  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/gnome-keyring/+bug/1768541/+subscriptions

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

[Desktop-packages] [Bug 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable w

This bug was fixed in the package gnome-keyring -
3.28.0.2-1ubuntu1.18.04.1

---
gnome-keyring (3.28.0.2-1ubuntu1.18.04.1) bionic; urgency=medium

  * debian/control{,.in}: Make the transitional packages be Arch any and MA
same, so upgrades work properly. (LP: #1768541)
  * Update Vcs-* for bionic.

 -- Iain Lane   Wed, 09 May 2018 20:19:29 +0100

** Changed in: gnome-keyring (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

Status in gnome-keyring package in Ubuntu:
  Fix Released
Status in gnome-keyring source package in Bionic:
  Fix Released

Bug description:
  installation of this package failed, upgrading from 17.10.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libp11-kit-gnome-keyring 3.20.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
  Date: Wed May  2 01:39:47 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DuplicateSignature:
   package:libp11-kit-gnome-keyring:3.20.1-1ubuntu1
   Unpacking gnome-keyring (3.28.0.2-1ubuntu1) over (3.20.1-1ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-PlRQuy/0830-libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1_all.deb
 (--unpack):
libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not 
co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances
  ErrorMessage: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) 
is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  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: gnome-keyring
  Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to 
install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: 
no) is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  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/gnome-keyring/+bug/1768541/+subscriptions

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

[Desktop-packages] [Bug 1624644] Update Released

2018-05-16 Thread Brian Murray

The verification of the Stable Release Update for update-manager has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Released
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades, the fix comes in an update of u-u) Run
  unattended-upgrades manually and observe the removal of the
  autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug

[Desktop-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

This bug was fixed in the package update-manager - 1:17.10.14

---
update-manager (1:17.10.14) artful; urgency=medium

  * Offer removal of unused autoremovable kernel packages
(LP: #1624644, #1675079)
  * Support package removals in install backends and really remove packages
(LP: #1624644, #1675079)
  * Keep PEP 8 checks happy
  * Place .keep files in empty directories to keep them when converting the
repo to git (LP: #1758963)

 -- Balint Reczey   Sun, 25 Mar 2018 19:57:57 +0100

** Changed in: update-manager (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Released
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades, the fix comes in an update of u-u) Run
  unattended-upgrades manually and observe the removal of the
  autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)

[Desktop-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

This bug was fixed in the package update-manager - 1:16.04.13

---
update-manager (1:16.04.13) xenial; urgency=medium

  * Offer removal of unused autoremovable kernel packages
(LP: #1624644, #1675079)
  * Support package removals in install backends and really remove packages
(LP: #1624644, #1675079)
  * Keep PEP 8 checks happy
  * Place .keep files in empty directories to keep them when converting the
repo to git (LP: #1758963)

 -- Balint Reczey   Sun, 25 Mar 2018 20:10:49 +0100

** Changed in: update-manager (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Released
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades, the fix comes in an update of u-u) Run
  unattended-upgrades manually and observe the removal of the
  autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)

[Desktop-packages] [Bug 1771702] [NEW] /usr/lib/vino/vino-server:11:gnutls_record_send:WriteExactOverTLS:WriteExact:rfbSendServerCutText:vino_server_clipboard_cb

2018-05-16 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
vino.  This problem was most recently seen with package version 
3.22.0-3ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/e241b9f33e338fd2a7cbf1ff153a3ca96195c611 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: artful bionic vivid wily xenial yakkety zesty

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

Title:
  /usr/lib/vino/vino-
  
server:11:gnutls_record_send:WriteExactOverTLS:WriteExact:rfbSendServerCutText:vino_server_clipboard_cb

Status in vino package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
vino.  This problem was most recently seen with package version 
3.22.0-3ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/e241b9f33e338fd2a7cbf1ff153a3ca96195c611 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

2018-05-16 Thread Brian Murray

Verified update-manager for artful.

** Attachment added: "bug-1624644-verification.png"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1624644/+attachment/5140527/+files/bug-1624644-verification.png

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

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Released
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades, the fix comes in an update of u-u) Run
  unattended-upgrades manually and observe the removal of the
  autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1740804] Re: Remove old vte package from Ubuntu

2018-05-16 Thread Jeremy Bicha

** No longer affects: genius (Ubuntu)

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

Title:
  Remove old vte package from Ubuntu

Status in rasmol package in Ubuntu:
  Incomplete
Status in vte package in Ubuntu:
  Incomplete

Bug description:
  NOTE
  
  Debian's debian-installer (specifically cdebconf-gtk-terminal I believe) uses 
a udeb from the old vte package. See https://bugs.debian.org/887649

  Original Bug Report
  ===
  The old vte source hasn't been maintained upstream since 2011 (when GNOME 3 
was released). vte will be dropped from Debian Testing soon. We should not ship 
it in Ubuntu 18.04 LTS. The replacement is provided by source vte2.91 (which 
requires gtk3).

  sjterm was already requested for removal in LP: #1728241

  $ reverse-depends src:vte
  Reverse-Depends
  ===
  * gnome-genius  (for libvte9)
  * pypar2(for python-vte)
  * rasmol [amd64 arm64 armhf i386 s390x]  (for libvte9)
  * stjerm(for libvte9)

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

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

[Desktop-packages] [Bug 1771682] Re: No way to logout from Snap Store.

2018-05-16 Thread Andrea Azzarone

MP here: https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/46

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

Title:
  No way to logout from Snap Store.

Status in gnome-software package in Ubuntu:
  In Progress

Bug description:
  Gnome-software has not GUI way to logout from snap store. Implement
  the proposed solution: https://github.com/CanonicalLtd/desktop-
  design/issues/62#issuecomment-385643142

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

-- 
Mailing list: https://launchpad.net/~desktop-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-16 Thread HouseSessions

Hi,

Being new around here, seen the high impact on a lot of users, is there
anyway or chance that Canonical can set prio with GNOME or deliver the
fix themselves to upstream?

thanks,
Koen.

-- 
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:
  In Progress
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in gdm3 source package in Bionic:
  Confirmed
Status in gnome-shell source package in Bionic:
  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 1771682] [NEW] No way to logout from Snap Store.

2018-05-16 Thread Andrea Azzarone

Public bug reported:

Gnome-software has not GUI way to logout from snap store. Implement the
proposed solution: https://github.com/CanonicalLtd/desktop-
design/issues/62#issuecomment-385643142

** Affects: gnome-software (Ubuntu)
 Importance: Medium
 Assignee: Andrea Azzarone (azzar1)
 Status: In Progress

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

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

** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

** Description changed:

- Gnome-software has not GUI way to logout from snap store.
+ Gnome-software has not GUI way to logout from snap store. Implement the
+ proposed solution: https://github.com/CanonicalLtd/desktop-
+ design/issues/62#issuecomment-385643142

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

Title:
  No way to logout from Snap Store.

Status in gnome-software package in Ubuntu:
  In Progress

Bug description:
  Gnome-software has not GUI way to logout from snap store. Implement
  the proposed solution: https://github.com/CanonicalLtd/desktop-
  design/issues/62#issuecomment-385643142

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

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

[Desktop-packages] [Bug 1760708] Re: Download Adobe Flash Player (apt-url). gnome-software crashed with signal 5 in g_main_context_new()

2018-05-16 Thread Marius Groenewald

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

I have downloaded the .tar.gz file from Adobe Flash Player website,
instead of using the APL option, which do not work. I extracted the file
and followed the instructions in the readme.txt file, and my Flash
Player is working!

Installation instructions
-

Installing using the plugin tar.gz:
o Download and Unpack the plugin tar.gz file. (I downloaded and extracted 
within my Downloads folder).  
o Open a terminal window and run: sudo nautilus.
o Copy the following file and folder under the extracted folder.
  + libflashplayer.so
  + /usr
o Paste the file and folder under the following location: 
/usr/lib/firefox/browser/plugins/
o Open Firefox and your Flash Player should work.

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

Title:
  Download Adobe Flash Player (apt-url). gnome-software crashed with
  signal 5 in g_main_context_new()

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I download Adobe Flash Player from https://get.adobe.com/flashplayer/
  Linux 64-bit, English, Firefox with Apt for debian/ubuntu 
  When I click to download, I selected apt-url and crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu7
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  2 22:54:12 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-03-30 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu7
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-software
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   snapd_client_find_section_sync () from 
/usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_snap.so
  Title: gnome-software crashed with signal 5 in g_main_context_new()
  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-software/+bug/1760708/+subscriptions

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

[Desktop-packages] [Bug 1750264] Re: program 'cd-paranoia' is missing from package in 1.0.0-2

2018-05-16 Thread emk2203

For anyone who wants a fix independent from Ubuntu maintainers action:

Go to the deb multimedia repo for unstable sid and download 
http://www.deb-multimedia.org/dists/unstable/main/binary-amd64/package/cd-paranoia
 and 
http://www.deb-multimedia.org/dists/unstable/main/binary-amd64/package/libcdio18.php
 .

Install with `dpkg -i`, done. Two harmless error messages are thrown
when the program runs, they can be safely ignored.


Errors to ignore:
cd-paranoia: /usr/lib/x86_64-linux-gnu/libcdio_paranoia.so.2: no version 
information available (required by cd-paranoia)
cd-paranoia: /usr/lib/x86_64-linux-gnu/libcdio_cdda.so.2: no version 
information available (required by cd-paranoia)

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

Title:
  program 'cd-paranoia' is missing from package in 1.0.0-2

Status in libcdio package in Ubuntu:
  Invalid
Status in libcdio-paranoia package in Ubuntu:
  Confirmed

Bug description:
  apt show libcdio-utils:

  Description: sample applications based on the CDIO libraries
   This package contains a collection of small libcdio-based tools:
* cd-drive  show CD-ROM drive characteristics
* cd-info   show information about a CD or CD-image
* cd-paranoia   an audio CD ripper
* cd-read   read information from a CD or CD-image
* cdda-player   a simple curses-based audio CD player
* iso-info  show information about an ISO 9660 image
* iso-read  read portions of an ISO 9660 image
* mmc-tool  issue low-level commands to a CD drive

  cd-paranoia is missing from package. This breaks abcde 'optional'
  functionality which is in fact the most common used, since the
  original cdparanoia (separate program) is abandoned since 10 years.

  Description:Ubuntu Bionic Beaver (development branch)
  Release:18.04

  libcdio-utils:
Installiert:   1.0.0-2
Installationskandidat: 1.0.0-2
Versionstabelle:
   *** 1.0.0-2 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libcdio-utils 1.0.0-2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXQt
  Date: Sun Feb 18 18:18:55 2018
  ProcEnviron:
   TERM=qterminal
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: libcdio
  UpgradeStatus: Upgraded to bionic on 2017-06-03 (260 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-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-16 Thread Sicabol

I have followed comment #96 for an Epson Perfection Photo V500 on Ubuntu
18.04 - it works perfectly.

-- 
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 1771660] [NEW] SRU: Make x11-xkb-config M-A: foreign

2018-05-16 Thread Matthias Klose

Public bug reported:

[Impact]

Installing x11-xkb-utils for a foreign architecture is not possible.
This is needed to cross build OpenJDK packages.

[Test Case]

Install build dependencies for openjdk-lts for a foreign architecture.

[Regression Potential]

None, as afar as I can see.

[Acceptance Criteria]

The package builds and is installable for foreign architectures.

** Affects: x11-xkb-utils (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  SRU: Make x11-xkb-config M-A: foreign

Status in x11-xkb-utils package in Ubuntu:
  New

Bug description:
  [Impact]

  Installing x11-xkb-utils for a foreign architecture is not possible.
  This is needed to cross build OpenJDK packages.

  [Test Case]

  Install build dependencies for openjdk-lts for a foreign architecture.

  [Regression Potential]

  None, as afar as I can see.

  [Acceptance Criteria]

  The package builds and is installable for foreign architectures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x11-xkb-utils/+bug/1771660/+subscriptions

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

[Desktop-packages] [Bug 1771661] [NEW] After updating to 18.04 only Wayland works. Cannot get Xorg to work on Gnome

2018-05-16 Thread jim ruxton

Public bug reported:

I recently updated to Ubuntu 18.04. After updating I can only log into
Gnome if I select Gnome or Ubuntu with Wayland at my login screen.
Nothing I can do will allow me tuse Xorg. I tried reinstalling Xorg and
reinstalling my video driver (nvidia-390) . If I select Ubuntu with Xorg
at login I get a purple screen and frozen mouse. If I set etting
|WaylandEnable=false| in |/etc/gdm/custom.conf| I cannot get to the
login screen. The system freezes.

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

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

Title:
   After updating to 18.04 only Wayland works. Cannot get Xorg to work
  on Gnome

Status in gdm3 package in Ubuntu:
  New

Bug description:
  I recently updated to Ubuntu 18.04. After updating I can only log into
  Gnome if I select Gnome or Ubuntu with Wayland at my login screen.
  Nothing I can do will allow me tuse Xorg. I tried reinstalling Xorg
  and reinstalling my video driver (nvidia-390) . If I select Ubuntu
  with Xorg at login I get a purple screen and frozen mouse. If I set
  etting |WaylandEnable=false| in |/etc/gdm/custom.conf| I cannot get to
  the login screen. The system freezes.

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

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

[Desktop-packages] [Bug 1764005] Re: Black-screen on boot with nvidia 390 for Budgie, MATE, Xubuntu, Kubuntu

2018-05-16 Thread Daniel Boyd

I am still having problems.  Running nvidia-prime 0.8.8.

I upgraded from 17.10 and have four monitors connected to a Dell
Precision 7510 with a Quadro M1000M.

In xorg, I get one of the four monitors.  In wayland I get the other 3!

I've attached my xorg.0.log

I unfortunately can't stick around to help troubleshoot because this is
my production work machine and I thought I'd take my lunch break to
upgrade to 18.04.  whoops.  Now I'm going to have to wipe and revert to
17.10... :/

** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1764005/+attachment/5140453/+files/Xorg.0.log

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

Title:
  Black-screen on boot with nvidia 390 for Budgie, MATE, Xubuntu,
  Kubuntu

Status in nvidia-prime package in Ubuntu:
  Fix Released

Bug description:
  Upgraded from Ubuntu Budgie 17.10 to 18.04.  After the plymouth splash
  left with a black screen.

  Purged all the nivdia-* packages and rebooted - graphical logon and
  logged in ok with nouveau.

  Tried software & updates to reinstall the nvidia 390 drivers.
  Rebooted.  Left at black screen again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-driver-390 390.48-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Sat Apr 14 21:42:04 2018
  InstallationDate: Installed on 2016-11-26 (503 days ago)
  InstallationMedia: budgie-remix 16.10 "Budgie-remix" -  amd64 (20161013)
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: Upgraded to bionic on 2018-04-14 (0 days ago)

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

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

[Desktop-packages] [Bug 1771650] [NEW] openvpn startup script isn't working in ubuntu 18.04

2018-05-16 Thread Fanar Webb

Public bug reported:

Its very simple.

1- Install ubuntu 18.04.
2- Install Openvpn using apt.
3- Put your configuration at path /etc/openvpn, for example :
/etc/openvpn/myconfig.conf.
4- start openvpn service! It won't start automatically.

Note : my config have a security weakness, but it still valid and works
perfect if I start it manually. For example : openvpn
/etc/openvpn/myconfig.conf - it works !

Thank you

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

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

Title:
openvpn startup script isn't working in ubuntu 18.04

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

Bug description:
Its very simple.

Note : my config have a security weakness, but it still valid and
works perfect if I start it manually. For example : openvpn
/etc/openvpn/myconfig.conf - it works !

Thank you

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

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

[Desktop-packages] [Bug 1771466] Re: Super+D wrongly leaves windows minimized if a new window appears while in "hiding" state

2018-05-16 Thread jimav

Upstream bug is
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/282

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

Title:
  Super+D wrongly  leaves windows minimized if a new window appears
  while in "hiding" state

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Toggling Super+D hides or un-hides all windows so you can access icons
  on the desktop.

  But this breaks if a new window appears while the windows are hidden:
  They become PERMANENTLY hidden, i.e. Super+D does not restore them.
  They seem to be "minimized" -- you have to individually un-minimize
  each window to get your session back.

  This is very annoying, and is common: The only reason for using
  Super+D is to see something on the desktop; probably you then need to
  do something with it, i.e. click it.  If that action opens a new
  window, which is almost certain, you're hosed.

  STEPS TO REPRODUCE:

  1. Open a bunch of windows and artfully arrange them.
  2. Type Super+D (they all become hidden)
  3. Double-click the "Trash" desktop icon and wait for a file browser to open.

  RESULTS: Once the file-viewer opens, Super+D will not restore the
  previously-hidden windows.  Instead, it seems to forget about them and
  instead hide the new window (and un-hide it if pressed a second time
  --before yet another window is opened, of course).

  EXPECTED RESULTS: 
 The state should be well-defined: Either normal or windows-hidden.  
 Once in the windows-hidden state, Super-D should un-hide the hidden 
windows e
 ven if new windows have been created in the interim.

  SUGGESTED FIX:
  1. (preferred): On the first Super+D, hide all windows and remember their 
IDs.  On the next Super+D, un-hide just those windows, if they still exist, and 
do nothing at all with any other windows which might be present (i.e. new 
ones).   Then return to the initial state, where Super+D hides all visible 
windows.

  2. (if the above is too hard to implement): If a new window appears
  while in the "hiding" state, make the new window immediately become
  hidden also; only on the second Super+D would the new window become
  visible along with the old ones.

  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 15 16:40:22 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['keepaw...@jepfa.de', 
'rece...@leonardo.bartoli.gmail.com', 
'drive-m...@gnome-shell-extensions.gcampax.github.com', 
'sound-output-device-choo...@kgshank.net', 'suspend-button@laserb', 
'systemmoni...@gnome-shell-extensions.gcampax.github.com', 
'workspaces-to-d...@passingthru67.gmail.com']"
   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-05 (40 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1)
  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/1771466/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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-16 Thread aeronutt

Same problem here. I can no longer log into 18.04. First password entry
fails, then on second entry, I get purple screen with working mouse
pointer. But hangs there. This has been an intermittent problem for me
over the past few weeks, but today seems to be 100%.

-- 
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:
  In Progress
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in gdm3 source package in Bionic:
  Confirmed
Status in gnome-shell source package in Bionic:
  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 1771628] [NEW] Grpahic Drivers

2018-05-16 Thread Gurjeet

Public bug reported:

Hi,

I'm getting a purple blank screen after putting my creadentials when the
computer is starting.

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
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed May 16 19:05:08 2018
DistUpgraded: 2018-05-16 16:54:13,314 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0704]
InstallationDate: Installed on 2016-11-01 (560 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0c45:670c Microdia 
 Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
 Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9350
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=247af43d-40d7-48c1-8502-e54796f36b07 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-05-16 (0 days ago)
dmi.bios.date: 06/14/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.4
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9350
dmi.sys.vendor: Dell Inc.
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 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

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


** Tags: amd64 apport-bug bionic third-party-packages 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/1771628

Title:
  Grpahic Drivers

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  I'm getting a purple blank screen after putting my creadentials when
  the computer is starting.

  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 16 19:05:08 2018
  DistUpgraded: 2018-05-16 16:54:13,314 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0704]
  InstallationDate: Installed on 2016-11-01 (560 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=247af43d-40d7-48c1-8502-e54796f36b07 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (0 days ago)
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

[Desktop-packages] [Bug 1749283] Re: configured stats_temp_directory does not get created after reboot

2018-05-16 Thread Eric Desrochers

** Changed in: resource-agents (Ubuntu)
 Assignee: (unassigned) => Eric Desrochers (slashd)

** Changed in: postgresql-common (Ubuntu)
   Status: In Progress => Won't Fix

** Changed in: postgresql-common (Ubuntu Xenial)
   Status: In Progress => Won't Fix

** Changed in: postgresql-common (Ubuntu Artful)
   Status: In Progress => Won't Fix

** Changed in: postgresql-common (Ubuntu Bionic)
   Status: In Progress => Won't Fix

** Changed in: resource-agents (Ubuntu)
   Importance: Undecided => Medium

** Changed in: resource-agents (Ubuntu)
   Status: New => In Progress

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

Title:
  configured stats_temp_directory does not get created after reboot

Status in postgresql-common package in Ubuntu:
  Won't Fix
Status in resource-agents package in Ubuntu:
  In Progress
Status in postgresql-common source package in Xenial:
  Won't Fix
Status in resource-agents source package in Xenial:
  New
Status in postgresql-common source package in Artful:
  Won't Fix
Status in resource-agents source package in Artful:
  New
Status in postgresql-common source package in Bionic:
  Won't Fix
Status in resource-agents source package in Bionic:
  New
Status in postgresql-common package in Debian:
  New

Bug description:
  Default postgres installation in Ubuntu (and Debian) configures
  stats_temp_directory inside /var/run/postgresql:

  $ grep stats_temp /etc/postgresql/10/main/postgresql.conf 
  stats_temp_directory = '/var/run/postgresql/10-main.pg_stat_tmp'

  However, this directory is not created after reboot.

  In most cases this is not a problem as systemd starts postgres via
  pg_ctlcluster, a "multiversion/cluster aware pg_ctl wrapper", and
  pg_ctlcluster will create missing directories before starting
  postgres.

  But in cases where systemd is not starting postgres this is a problem.
  Specifically, when postgres is controlled by pacemaker (using postgres 
resource agent for pacemaker) it is started using pg_ctl wrapper. pg_ctl won't 
create missing directories and therefore postgres fails to start.

  The simplest solution for this issue is to have systemd recreate
  missing directories via /usr/lib/tmpfiles.d/postgresql.conf file.

  Currently only /var/run/postgresql and /var/log/postgresql are created
  using systemd-tmpfiles.

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

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

[Desktop-packages] [Bug 1749283] Re: configured stats_temp_directory does not get created after reboot

2018-05-16 Thread Eric Desrochers

** Also affects: resource-agents (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  configured stats_temp_directory does not get created after reboot

Status in postgresql-common package in Ubuntu:
  Won't Fix
Status in resource-agents package in Ubuntu:
  In Progress
Status in postgresql-common source package in Xenial:
  Won't Fix
Status in resource-agents source package in Xenial:
  New
Status in postgresql-common source package in Artful:
  Won't Fix
Status in resource-agents source package in Artful:
  New
Status in postgresql-common source package in Bionic:
  Won't Fix
Status in resource-agents source package in Bionic:
  New
Status in postgresql-common package in Debian:
  New

Bug description:
  Default postgres installation in Ubuntu (and Debian) configures
  stats_temp_directory inside /var/run/postgresql:

  $ grep stats_temp /etc/postgresql/10/main/postgresql.conf 
  stats_temp_directory = '/var/run/postgresql/10-main.pg_stat_tmp'

  However, this directory is not created after reboot.

  In most cases this is not a problem as systemd starts postgres via
  pg_ctlcluster, a "multiversion/cluster aware pg_ctl wrapper", and
  pg_ctlcluster will create missing directories before starting
  postgres.

  But in cases where systemd is not starting postgres this is a problem.
  Specifically, when postgres is controlled by pacemaker (using postgres 
resource agent for pacemaker) it is started using pg_ctl wrapper. pg_ctl won't 
create missing directories and therefore postgres fails to start.

  The simplest solution for this issue is to have systemd recreate
  missing directories via /usr/lib/tmpfiles.d/postgresql.conf file.

  Currently only /var/run/postgresql and /var/log/postgresql are created
  using systemd-tmpfiles.

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

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

[Desktop-packages] [Bug 1771522] Re: Liferea is outdated

2018-05-16 Thread Hans Joachim Desserud

** Tags added: upgrade-software-version

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

Title:
  Liferea is outdated

Status in liferea package in Ubuntu:
  New

Bug description:
  Liferea is showing a keyring error when I try to start it hidden. I
  believe this is fixed in Liferea 1.12.3, but Liferea in the Ubuntu
  repositories is still on version 1.12.2

  See https://github.com/lwindolf/liferea/releases/tag/v1.12.3

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

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

[Desktop-packages] [Bug 1771625] Re: network-manager tray menu disappears when connecting to a wireless network

2018-05-16 Thread William Poetra Yoga

There are two general (but similar) ways to reproduce the bug:

A. Wake the laptop from suspend. There should be saved networks in range, and
the "connect automatically" setting on for at least some of those networks.
- When the laptop wakes from suspend, immediately type your password on the
lock screen, and as soon as the desktop appears, click the network-manager tray
icon to display its menu.
- The menu will be displayed, and it will show the list of wireless networks,
and also show the network that we are currently in the process of connecting.
The tray icon is also the rotating wait icon at this time.
- But as soon as we successfully connect to the network, the tray menu
disappears. This is the bug.

B. When the desktop is shown, connect to any wireless network.
- Click on the tray icon, the network-manager tray menu will appear.
- Click on any wireless network that is in range and that we have saved
previously. The menu will disappear, this might be the intended behaviour.
Also, the tray icon will flash into the network disconnected icon, and then
change to the rotating wait icon.
- While we are still in the process of connecting to the wireless network, and
the tray icon is still the rotating wait icon, click on the tray icon again to
display the menu.
- The menu will display our chosen network in bold, although we have not
successfully connected yet. This might be the intended behaviour.
- After a few seconds, at the moment that the connection is complete, and the
tray icon changes to the wireless network connected icon (with the signal
bars), the menu disappears. This is the bug.

Expected behaviour: The network-manager tray menu should not disappear
when the connection is complete.

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

Title:
network-manager tray menu disappears when connecting to a wireless
network

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

Bug description:
I'm using Linux Mint 18.3 on amd64 which is based on Ubuntu 16.04. I'm
reporting this bug here because it is related to the network-manager
tray icon, which I think is from nm-applet in the package network-
manager-gnome, which on my laptop is version 1.2.6-0ubuntu0.16.04.4,
which means that it is not modified from the Ubuntu version.

Package version: network-manager-gnome 1.2.6-0ubuntu0.16.04.4

What I expected to happen: The network-manager tray menu should update its
contents when the machine connects to a wifi network.
What happened instead: The network-manager tray menu disappears when the
machine connects to a wifi network.

Note: What I mean by the "network-manager tray menu" is the menu that
appears when the network-manager tray icon is clicked, which shows
wired and wireless connections, which connection(s) are active, and so
on. Sorry if this is not the right name for that menu.

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

[Desktop-packages] [Bug 1771625] Re: network-manager tray menu disappears when connecting to a wireless network

2018-05-16 Thread William Poetra Yoga

This is what I mean by "network-manager tray menu".

** Attachment added: "bug-report-network-manager-tray-menu.png"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1771625/+attachment/5140394/+files/bug-report-network-manager-tray-menu.png

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

Title:
  network-manager tray menu disappears when connecting to a wireless
  network

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

Bug description:
  I'm using Linux Mint 18.3 on amd64 which is based on Ubuntu 16.04. I'm
  reporting this bug here because it is related to the network-manager
  tray icon, which I think is from nm-applet in the package network-
  manager-gnome, which on my laptop is version 1.2.6-0ubuntu0.16.04.4,
  which means that it is not modified from the Ubuntu version.

  Package version: network-manager-gnome 1.2.6-0ubuntu0.16.04.4

  What I expected to happen: The network-manager tray menu should update its 
contents when the machine connects to a wifi network.
  What happened instead: The network-manager tray menu disappears when the 
machine connects to a wifi network.

  Note: What I mean by the "network-manager tray menu" is the menu that
  appears when the network-manager tray icon is clicked, which shows
  wired and wireless connections, which connection(s) are active, and so
  on. Sorry if this is not the right name for that menu.

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

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

[Desktop-packages] [Bug 1771625] [NEW] network-manager tray menu disappears when connecting to a wireless network

2018-05-16 Thread William Poetra Yoga

Public bug reported:

I'm using Linux Mint 18.3 on amd64 which is based on Ubuntu 16.04. I'm
reporting this bug here because it is related to the network-manager
tray icon, which I think is from nm-applet in the package network-
manager-gnome, which on my laptop is version 1.2.6-0ubuntu0.16.04.4,
which means that it is not modified from the Ubuntu version.

Package version: network-manager-gnome 1.2.6-0ubuntu0.16.04.4

What I expected to happen: The network-manager tray menu should update its 
contents when the machine connects to a wifi network.
What happened instead: The network-manager tray menu disappears when the 
machine connects to a wifi network.

Note: What I mean by the "network-manager tray menu" is the menu that
appears when the network-manager tray icon is clicked, which shows wired
and wireless connections, which connection(s) are active, and so on.
Sorry if this is not the right name for that menu.

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

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

Title:
  network-manager tray menu disappears when connecting to a wireless
  network

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

Bug description:
  I'm using Linux Mint 18.3 on amd64 which is based on Ubuntu 16.04. I'm
  reporting this bug here because it is related to the network-manager
  tray icon, which I think is from nm-applet in the package network-
  manager-gnome, which on my laptop is version 1.2.6-0ubuntu0.16.04.4,
  which means that it is not modified from the Ubuntu version.

  Package version: network-manager-gnome 1.2.6-0ubuntu0.16.04.4

  What I expected to happen: The network-manager tray menu should update its 
contents when the machine connects to a wifi network.
  What happened instead: The network-manager tray menu disappears when the 
machine connects to a wifi network.

  Note: What I mean by the "network-manager tray menu" is the menu that
  appears when the network-manager tray icon is clicked, which shows
  wired and wireless connections, which connection(s) are active, and so
  on. Sorry if this is not the right name for that menu.

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

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

[Desktop-packages] [Bug 1768756] Re: Libreoffice 6 does not start on Kubuntu 18.04 (clean install)

2018-05-16 Thread Tomáš Myšík

Yes. In my case, together with "libreoffice-l10n-cs" package.

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

Title:
  Libreoffice 6 does not start on Kubuntu 18.04 (clean install)

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I just did a clean install of Kubuntu 18.04 (the minimal one) and
  manually installed Libreoffice [1]. Now, when I try to start it, I get
  this:

  $ libreoffice 
  terminate called after throwing an instance of 
'com::sun::star::uno::RuntimeException'

  
  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7f8545b22568]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c316)[0x7f8545b4b316]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7f854575cf20]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f854575ce97]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f854575e801]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x8c8fb)[0x7f853d5228fb]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x92d3a)[0x7f853d528d3a]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x92d95)[0x7f853d528d95]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(__cxa_rethrow+0x4d)[0x7f853d52903d]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x10ab728)[0x7f8546e14728]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN10comphelper6detail20ConfigurationWrapper3getERKN3com3sun4star3uno9ReferenceINS5_17XComponentContextEEE+0x47)[0x7f8546e147f7]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN12OpenGLHelper18isVCLOpenGLEnabledEv+0x2e5)[0x7f8548b408c5]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN10SalDisplay10BestVisualEP9_XDisplayiR11XVisualInfo+0xfd)[0x7f852dbdbc2d]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZNK10SalDisplay10initScreenE12SalX11Screen+0x8b)[0x7f852dbe113b]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN7vcl_sal9WMAdaptorC1EP10SalDisplay+0x21d)[0x7f852dbe6e4d]
  /usr/lib/libreoffice/program/libvclplug_genlo.so(+0x4024b)[0x7f852dbe724b]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN7vcl_sal9WMAdaptor15createWMAdaptorEP10SalDisplay+0x21)[0x7f852dbe8171]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN10SalDisplay4InitEv+0x467)[0x7f852dbe2997]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN13SalX11DisplayC1EP9_XDisplay+0x24)[0x7f852dbe2b44]
  /usr/lib/libreoffice/program/libvclplug_kde4lo.so(+0x1963e)[0x7f85302d263e]
  /usr/lib/libreoffice/program/libvclplug_kde4lo.so(+0x1e636)[0x7f85302d7636]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN14X11SalInstance12AfterAppInitEv+0x12)[0x7f852dbe3282]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z7InitVCLv+0x382)[0x7f8548a53742]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cebd3d)[0x7f8548a54d3d]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7f8548a54da0]
  
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7f8547a9a215]
  /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x560c5d84978b]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f854573fb97]
  /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x560c5d8497ca]

  No matter what I try (e.g. [2]), the result is always the same.

  I also tried to remove my config dir [3] but no luck.

  Any idea what could be wrong? Thanks.

  Description:Ubuntu 18.04 LTS
  Release:18.04

  libreoffice version: 6.0.3-0ubuntu1

  [1] apt install libreoffice
  [2] libreoffice --help
  [3] ~/.config/libreoffice/

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

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

[Desktop-packages] [Bug 1768756] Re: Libreoffice 6 does not start on Kubuntu 18.04 (clean install)

So, just to confirm (and try to reproduce the issue here): "sudo apt
install libreoffice" ?

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

Title:
  Libreoffice 6 does not start on Kubuntu 18.04 (clean install)

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I just did a clean install of Kubuntu 18.04 (the minimal one) and
  manually installed Libreoffice [1]. Now, when I try to start it, I get
  this:

  $ libreoffice 
  terminate called after throwing an instance of 
'com::sun::star::uno::RuntimeException'

  
  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7f8545b22568]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c316)[0x7f8545b4b316]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7f854575cf20]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f854575ce97]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f854575e801]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x8c8fb)[0x7f853d5228fb]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x92d3a)[0x7f853d528d3a]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x92d95)[0x7f853d528d95]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(__cxa_rethrow+0x4d)[0x7f853d52903d]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x10ab728)[0x7f8546e14728]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN10comphelper6detail20ConfigurationWrapper3getERKN3com3sun4star3uno9ReferenceINS5_17XComponentContextEEE+0x47)[0x7f8546e147f7]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN12OpenGLHelper18isVCLOpenGLEnabledEv+0x2e5)[0x7f8548b408c5]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN10SalDisplay10BestVisualEP9_XDisplayiR11XVisualInfo+0xfd)[0x7f852dbdbc2d]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZNK10SalDisplay10initScreenE12SalX11Screen+0x8b)[0x7f852dbe113b]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN7vcl_sal9WMAdaptorC1EP10SalDisplay+0x21d)[0x7f852dbe6e4d]
  /usr/lib/libreoffice/program/libvclplug_genlo.so(+0x4024b)[0x7f852dbe724b]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN7vcl_sal9WMAdaptor15createWMAdaptorEP10SalDisplay+0x21)[0x7f852dbe8171]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN10SalDisplay4InitEv+0x467)[0x7f852dbe2997]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN13SalX11DisplayC1EP9_XDisplay+0x24)[0x7f852dbe2b44]
  /usr/lib/libreoffice/program/libvclplug_kde4lo.so(+0x1963e)[0x7f85302d263e]
  /usr/lib/libreoffice/program/libvclplug_kde4lo.so(+0x1e636)[0x7f85302d7636]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN14X11SalInstance12AfterAppInitEv+0x12)[0x7f852dbe3282]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z7InitVCLv+0x382)[0x7f8548a53742]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cebd3d)[0x7f8548a54d3d]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7f8548a54da0]
  
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7f8547a9a215]
  /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x560c5d84978b]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f854573fb97]
  /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x560c5d8497ca]

  No matter what I try (e.g. [2]), the result is always the same.

  I also tried to remove my config dir [3] but no luck.

  Any idea what could be wrong? Thanks.

  Description:Ubuntu 18.04 LTS
  Release:18.04

  libreoffice version: 6.0.3-0ubuntu1

  [1] apt install libreoffice
  [2] libreoffice --help
  [3] ~/.config/libreoffice/

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

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

[Desktop-packages] [Bug 1771615] [NEW] LibreOffice Apps do not appear in the panel taskbar

2018-05-16 Thread Scott Cowles Jacobs

Public bug reported:

I recently installed Lubuntu Next 18.04, which includes LibreOffice 6.

At some point, I noticed that LibreOffice Writer (unlike all my other
programs) does not appear in the panel's Taskbar (where all apps loaded
in that workspace/desktop should be).

All other apps with which I have experience, are listed in the taskbar, and can 
be minimized and un-minimized by clicking on the portion of the bar devoted to 
that app.
There is an option in the panel settings that would allow me to only have apps 
appear in the taskbar when minimized, but I never use that.

LibreOffice apps (I noticed this with Writer, but since tested it with
the other LO apps that were installed with my OS, and the same thing
happens with all) have nothing in the taskbar to show that they have
opened, and when minimized, disappear entirely.

I know that they have not quit when they disappear, in two ways:
1. If I use the OS's menu to bring up LO-W again (thus with an blank document), 
and then go to that window's menu->Window, it shows all open LO-W documents, 
which can then be brought back by clicking on them.
2.  Lubuntu Next's window manager OpenBox has a keyboard-shortcut Alt-Tab, 
which allows one to select from available app windows - and at least one LO 
document is listed, from which the others can then be accessed by #1.

I don't know what causes an app to have windows in the taskbar, but that system 
is failing with LO windows.
(I guess that I had assumed that the OS took care of managing windows in the 
taskbar - having them appear there when opened, and removing them when closed), 
but apparently I am wrong, or LO windows would not be able to hide, as they 
seem to do...)

I am assuming that this is a new bug, as this did not happen before.
I cannot think that it is a design decision, not to let the user minimize 
documents (or simultaneously open multiple documents) without apparently losing 
them altogether (at least without jumping through hoops (hoops of which they 
might well not be aware...)).



scott@scott-ASUS-M2N68-AM-PLUS:~$ uname -a
Linux scott-ASUS-M2N68-AM-PLUS 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 
06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
scott@scott-ASUS-M2N68-AM-PLUS:~$ lsb_release -dsc
Ubuntu 18.04 LTS
bionic
scott@scott-ASUS-M2N68-AM-PLUS:~$ echo $DESKTOP_SESSION
QLubuntu

scott@scott-ASUS-M2N68-AM-PLUS:~$ apt-cache policy libreoffice-core
libreoffice-core:
  Installed: 1:6.0.3-0ubuntu1
  Candidate: 1:6.0.3-0ubuntu1
  Version table:
 *** 1:6.0.3-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status



ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libreoffice-core 1:6.0.3-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: LXQt
Date: Wed May 16 11:22:53 2018
InstallationDate: Installed on 2018-04-29 (16 days ago)
InstallationMedia: Lubuntu-Next 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180421)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "Note that the only thing in the bottom panel's Taskbar is 
my (hidden) terminal app Sakura."
   
https://bugs.launchpad.net/bugs/1771615/+attachment/5140381/+files/LibreOffice_Not_In_Taskbar.jpg

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

Title:
  LibreOffice Apps do not appear in the panel taskbar

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I recently installed Lubuntu Next 18.04, which includes LibreOffice 6.

  At some point, I noticed that LibreOffice Writer (unlike all my other
  programs) does not appear in the panel's Taskbar (where all apps
  loaded in that workspace/desktop should be).

  All other apps with which I have experience, are listed in the taskbar, and 
can be minimized and un-minimized by clicking on the portion of the bar devoted 
to that app.
  There is an option in the panel settings that would allow me to only have 
apps appear in the taskbar when minimized, but I never use that.

  LibreOffice apps (I noticed this with Writer, but since tested it with
  the other LO apps that were installed with my OS, and the same thing
  happens with all) have nothing in the taskbar to show that they have
  opened, and when minimized, disappear entirely.

  I know that they have not quit when they disappear, in two ways:
  1. If I use the OS's menu to bring

[Desktop-packages] [Bug 1765799] Re: Applications menu does not get populated with recently installed apps using apt

2018-05-16 Thread fossfreedom

** Changed in: gnome-menus (Ubuntu)
   Status: In Progress => New

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

Title:
  Applications menu does not get populated with recently installed apps
  using apt

Status in gnome-menus package in Ubuntu:
  New

Bug description:
  [Impact]

   Applications menu for GNOME3 based desktop environments doesn't get
  populated with recently installed app using apt or GUI apps like
  gnome-software, budgie-welcome (Ubuntu Budgie)

  Users need to physically logout and login again before they see the
  application appear in their menu.

  This is an intermittent issue - some installs work correctly, some
  installs dont display in the menu.  After logging out and logging in,
  those installs that didnt display, now appear in the menu.

  This affects all desktop environments that use gnome-menus to
  recognise new/changed/deleted applications.  Primarily this would be
  Unity and Budgie Desktop.  Not sure about GNOME Shell or other desktop
  environments

  [Test Case]

  Install an application using apt (command line), GNOME Software or
  through budgie-welcome (Ubuntu Budgie only) - The application icon
  should appear in the menu of the desktop environment being used.

  Remove an application through apt, GNOME Software and/or budgie-
  welcome (ubuntu budgie) - The application icon should disappear from
  the menu of the desktop environment being used

  Repeat the above two test cases several times (e.g. 10x) with
  different applications

  [Regression Potential]

  Arguably the risk is that the patch introduces potential instability
  into the installation sequence that could cause crashes.  That's the
  worst case scenario.

  The mitigation here is that the patch is the exact same patch used in
  17.04 and 17.10.  It was also used in 16.04 and 16.10 - in these two
  cases the patch did not contain a one line fix introduced in 17.04
  that fixed a crashing race issue in budgie-desktop.

  [Other Info]
   
  Consultation with the uploader to 18.04 (Jeremy) is a must here to discuss 
possibly reasons why when merging with Debian, the ubuntu specific patch was 
not readded.

  
  

  Below is the original description

  Applications menu doesn't get populated with recently installed app
  using apt.

  For example, after installing Firefox using apt, its shortcut does not appear 
immediately in the applications main menu. It only appeared there after I 
rebooted (maybe logging off also does the job).
  A “refresh menu” action has to be triggered somehow after installations.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-11ubuntu1
  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
  CurrentDesktop: Budgie:GNOME
  Date: Fri Apr 20 18:39:49 2018
  Dependencies:

  InstallationDate: Installed on 2018-04-20 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180418)
  SourcePackage: gnome-menus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1771603] [NEW] Does not honour UID_MAX

2018-05-16 Thread Marc Deslauriers

Public bug reported:

accountsservice doesn't honour the UID_MAX settings in /etc/login.defs,
resulting in system users being displayed at the login screen and in the
users control panel.

See attached screenshot to see that the "libvirt-qemu" user is being
displayed when it shouldn't.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: accountsservice 0.6.45-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: ubuntu:GNOME
Date: Wed May 16 11:03:09 2018
InstallationDate: Installed on 2017-12-12 (155 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: accountsservice
UpgradeStatus: Upgraded to bionic on 2018-05-09 (7 days ago)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "screenshot of issue"
   
https://bugs.launchpad.net/bugs/1771603/+attachment/5140372/+files/Screenshot%20from%202018-05-16%2011-05-30.png

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

Title:
  Does not honour UID_MAX

Status in accountsservice package in Ubuntu:
  New

Bug description:
  accountsservice doesn't honour the UID_MAX settings in
  /etc/login.defs, resulting in system users being displayed at the
  login screen and in the users control panel.

  See attached screenshot to see that the "libvirt-qemu" user is being
  displayed when it shouldn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: accountsservice 0.6.45-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: ubuntu:GNOME
  Date: Wed May 16 11:03:09 2018
  InstallationDate: Installed on 2017-12-12 (155 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: accountsservice
  UpgradeStatus: Upgraded to bionic on 2018-05-09 (7 days ago)

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

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

[Desktop-packages] [Bug 1771308] Re: Adding the user to a new group doesn't take effect on logout and back in

2018-05-16 Thread Sebastien Bacher

Daniel, what do you mean by "running process"? The steps involve login
out and back in, so starting a new session, group changes should be
active on a new login no?

** Package changed: linux (Ubuntu) => gdm3 (Ubuntu)

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

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

Title:
  Adding the user to a new group doesn't take effect on logout and back
  in

Status in gdm3 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  Log in to a GNOME session
  Use adduser to add yourself to an existing group
  Log out and back in
  Open a terminal, run "groups" and notice that your user isn't in the new 
group.
  Reboot and log in, and you user is now in the group.

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

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

[Desktop-packages] [Bug 1674089] Re: Tamil 99 keyboard layout

2018-05-16 Thread Sivaraj D

Tamil99 keyboard is available in the package ibus-table-array30. Please
refer to  http://www.kaniyam.com/ibus/ for installation instructions.

In the long term Tamil99 should be added as the default for Tamil, or at
least as an option in default installation.

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

Title:
  Tamil 99 keyboard layout

Status in ibus-m17n package in Ubuntu:
  Confirmed

Bug description:
  Tamil 99 keyboard layout which is the default keyboard layout prescribed by 
the Indian State of Tamil Nadu is not present. Selecting Tamil layout selects 
the Tamil Inscript layout which is prescribed by the Government of India.
  However, considering that Tamil is used only in the state of Tamil Nadu and 
that most keyboards are manufactured with Tamil 99, the layout by the Tamil 
Nadu government is the only one sold currently (usually by a company called 
TVS-e). This can be verified by Googling for Tamil+English bilingual keyboards. 
The current Inscript layout is useless for actual users and the lack of Tamil 
99 layout forces people to switch to Google Input tools.

  I have observed this on Ubuntu 16.04.2 LTS

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

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

[Desktop-packages] [Bug 1771308] [NEW] Adding the user to a new group doesn't take effect on logout and back in

You have been subscribed to a public bug:

Steps to reproduce:

Log in to a GNOME session
Use adduser to add yourself to an existing group
Log out and back in
Open a terminal, run "groups" and notice that your user isn't in the new group.
Reboot and log in, and you user is now in the group.

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

-- 
Adding the user to a new group doesn't take effect on logout and back in
https://bugs.launchpad.net/bugs/1771308
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gdm3 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 1759621] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()

2018-05-16 Thread Treviño

Some gdb debugging is

#1  0x7f3abc9a1bc8 in st_label_set_text (label=0x555b3f768d10, 
text=0x555b5369d360 "...")
at ../../gnome-shell/src/st/st-label.c:331
331   ctext = CLUTTER_TEXT (priv->label);
(gdb) list
326 
327   g_return_if_fail (ST_IS_LABEL (label));
328   g_return_if_fail (text != NULL);
329 
330   priv = label->priv;
331   ctext = CLUTTER_TEXT (priv->label);
332 
333   if (clutter_text_get_editable (ctext) ||
334   g_strcmp0 (clutter_text_get_text (ctext), text) != 0)
335 {
(gdb) print label
$1 = (StLabel *) 0x555b3f768d10
(gdb) print *label
$2 = {parent_instance = {parent_instance = {parent_instance = {g_type_instance 
= {g_class = 0x555b3e5ea510}, 
ref_count = 1, qdata = 0x555b3f759800}, flags = 0, private_flags = 0, 
priv = 0x555b3f7689f0}}, 
  priv = 0x555b3f7688b0}
(gdb) print *label->priv
$3 = {label = 0x555b3f712210, text_shadow_pipeline = 0x0, shadow_width = -1, 
shadow_height = -1}
(gdb) print *label->priv->labe
There is no member named labe.
(gdb) print *label->priv->label
$4 = {parent_instance = {g_type_instance = {g_class = 0x7f3abdf80be0
 }, ref_count = 
1102656128, qdata = 0x30}, flags = 113, 
  private_flags = 0, priv = 0x68733b6572616873}

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text() from ffi_call_unix64()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/811164cadd3e9e891f9e2d439bda59925f91a62c

  ---

  trying to get vpn up and running

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 28 18:00:19 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['vpn-indica...@howdoicomputer.fastmail.com']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'org.gnome.Terminal.desktop', 
'cisco-anyconnect.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-03-23 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fd17cf23d3d :
movzbl 0x16(%rax),%edx
   PC (0x7fd17cf23d3d) ok
   source "0x16(%rax)" (0x00024562) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () at /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (4 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1768756] Re: Libreoffice 6 does not start on Kubuntu 18.04 (clean install)

2018-05-16 Thread Tomáš Myšík

In my case, it was quite soon after installation. I am using console,
apt.

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

Title:
  Libreoffice 6 does not start on Kubuntu 18.04 (clean install)

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I just did a clean install of Kubuntu 18.04 (the minimal one) and
  manually installed Libreoffice [1]. Now, when I try to start it, I get
  this:

  $ libreoffice 
  terminate called after throwing an instance of 
'com::sun::star::uno::RuntimeException'

  
  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7f8545b22568]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c316)[0x7f8545b4b316]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7f854575cf20]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f854575ce97]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f854575e801]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x8c8fb)[0x7f853d5228fb]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x92d3a)[0x7f853d528d3a]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x92d95)[0x7f853d528d95]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(__cxa_rethrow+0x4d)[0x7f853d52903d]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x10ab728)[0x7f8546e14728]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN10comphelper6detail20ConfigurationWrapper3getERKN3com3sun4star3uno9ReferenceINS5_17XComponentContextEEE+0x47)[0x7f8546e147f7]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN12OpenGLHelper18isVCLOpenGLEnabledEv+0x2e5)[0x7f8548b408c5]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN10SalDisplay10BestVisualEP9_XDisplayiR11XVisualInfo+0xfd)[0x7f852dbdbc2d]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZNK10SalDisplay10initScreenE12SalX11Screen+0x8b)[0x7f852dbe113b]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN7vcl_sal9WMAdaptorC1EP10SalDisplay+0x21d)[0x7f852dbe6e4d]
  /usr/lib/libreoffice/program/libvclplug_genlo.so(+0x4024b)[0x7f852dbe724b]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN7vcl_sal9WMAdaptor15createWMAdaptorEP10SalDisplay+0x21)[0x7f852dbe8171]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN10SalDisplay4InitEv+0x467)[0x7f852dbe2997]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN13SalX11DisplayC1EP9_XDisplay+0x24)[0x7f852dbe2b44]
  /usr/lib/libreoffice/program/libvclplug_kde4lo.so(+0x1963e)[0x7f85302d263e]
  /usr/lib/libreoffice/program/libvclplug_kde4lo.so(+0x1e636)[0x7f85302d7636]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN14X11SalInstance12AfterAppInitEv+0x12)[0x7f852dbe3282]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z7InitVCLv+0x382)[0x7f8548a53742]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cebd3d)[0x7f8548a54d3d]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7f8548a54da0]
  
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7f8547a9a215]
  /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x560c5d84978b]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f854573fb97]
  /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x560c5d8497ca]

  No matter what I try (e.g. [2]), the result is always the same.

  I also tried to remove my config dir [3] but no luck.

  Any idea what could be wrong? Thanks.

  Description:Ubuntu 18.04 LTS
  Release:18.04

  libreoffice version: 6.0.3-0ubuntu1

  [1] apt install libreoffice
  [2] libreoffice --help
  [3] ~/.config/libreoffice/

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

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

[Desktop-packages] [Bug 1759621] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()

2018-05-16 Thread Treviño

I got it finally with some proper JS stacktrace, in my case it was an
extension triggering it:

(gnome-shell:6754): Gjs-CRITICAL **: 12:22:44.730: Object St.BoxLayout 
(0x55950fcf1230), has been already deallocated - impossible to access to it. 
This might be caused by the fact that the object has been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs
== Stack trace for context 0x55950f5194c0 ==
#0 0x7fffe152eed0 I   resource:///org/gnome/shell/ui/environment.js:41 
(0x7f1e5c586d58 @ 20)
#1 0x7fffe152efc0 b   resource:///org/gnome/shell/ui/popupMenu.js:642 
(0x7f1e5c224de0 @ 61)
#2 0x7fffe152f060 I   resource:///org/gnome/gjs/modules/_legacy.js:82 
(0x7f1e5c5b5e68 @ 71)
#3 0x55950f8dd540 i   
/home/marco/.local/share/gnome-shell/extensions/clipboard-indica...@tudmotu.com/extension.js:132
 (0x7f1e0fa86808 @ 342)
#4 0x55950f8dd480 i   
/home/marco/.local/share/gnome-shell/extensions/clipboard-indica...@tudmotu.com/utils.js:121
 (0x7f1e0fab9340 @ 458)

(gnome-shell:6754): Clutter-CRITICAL **: 12:22:44.730:
clutter_layout_manager_get_child_meta: assertion
'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.730:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.730:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): Clutter-CRITICAL **: 12:22:44.730:
clutter_layout_manager_get_child_meta: assertion
'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.730:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.730:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): Gjs-CRITICAL **: 12:22:44.731: Object St.BoxLayout 
(0x55950fcf1230), has been already deallocated - impossible to access to it. 
This might be caused by the fact that the object has been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs
== Stack trace for context 0x55950f5194c0 ==
#0 0x7fffe152eed0 I   resource:///org/gnome/shell/ui/environment.js:41 
(0x7f1e5c586d58 @ 20)
#1 0x7fffe152efc0 b   resource:///org/gnome/shell/ui/popupMenu.js:642 
(0x7f1e5c224de0 @ 61)
#2 0x7fffe152f060 I   resource:///org/gnome/gjs/modules/_legacy.js:82 
(0x7f1e5c5b5e68 @ 71)
#3 0x55950f8dd540 i   
/home/marco/.local/share/gnome-shell/extensions/clipboard-indica...@tudmotu.com/extension.js:157
 (0x7f1e0fa86808 @ 585)
#4 0x55950f8dd480 i   
/home/marco/.local/share/gnome-shell/extensions/clipboard-indica...@tudmotu.com/utils.js:121
 (0x7f1e0fab9340 @ 458)

(gnome-shell:6754): Clutter-CRITICAL **: 12:22:44.731:
clutter_layout_manager_get_child_meta: assertion
'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.731:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.731:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): Clutter-CRITICAL **: 12:22:44.731:
clutter_layout_manager_get_child_meta: assertion
'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.731:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.731:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): Gjs-CRITICAL **: 12:22:44.731: Object St.BoxLayout 
(0x55950fcf1230), has been already deallocated - impossible to access to it. 
This might be caused by the fact that the object has been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs
== Stack trace for context 0x55950f5194c0 ==
#0 0x7fffe152eed0 I   resource:///org/gnome/shell/ui/environment.js:41 
(0x7f1e5c586d58 @ 20)
#1 0x7fffe152efc0 b   resource:///org/gnome/shell/ui/popupMenu.js:642 
(0x7f1e5c224de0 @ 61)
#2 0x7fffe152f060 I   resource:///org/gnome/gjs/modules/_legacy.js:82 
(0x7f1e5c5b5e68 @ 71)
#3 0x55950f8dd540 i   
/home/marco/.local/share/gnome-shell/extensions/clipboard-indica...@tudmotu.com/extension.js:171
 (0x7f1e0fa86808 @ 778)
#4 0x55950f8dd480 i   
/home/marco/.local/share/gnome-shell/extensions/clipboard-indica...@tudmotu.com/utils.js:121
 (0x7f1e0fab9340 @ 458)

(gnome-shell:6754): Clutter-CRITICAL **: 12:22:44.732:
clutter_layout_manager_get_child_meta: assertion
'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.732:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.732:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): Clutter-CRITICAL **: 12:22:44.732:
clutter_layout_manager_get_child_meta: assertion
'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.732:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754):

[Desktop-packages] [Bug 1758163] Re: Please remove xchat-gnome from Ubuntu (again)

2018-05-16 Thread Jeremy Bicha

Just installing hexchat would mean adding a "transitional" package in
the hexchat source.

One way to have a suggestion about hexchat would be having command-not-
found handle it. To get an idea of how that works, if you uninstall
hexchat and run hexchat in a terminal, you'll get this output on Ubuntu
18.04 LTS:

$ hexchat

Command 'hexchat' not found, but can be installed with:

sudo snap install hexchat
sudo apt  install hexchat

See 'snap info hexchat' for additional versions.

===
So I suggest filing a separate bug against hexchat or command-not-found for 
your suggestion.

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

Title:
  Please remove xchat-gnome from Ubuntu (again)

Status in xchat-gnome package in Ubuntu:
  Fix Released

Bug description:
  xchat-gnome is unmaintained.

  It was removed from Debian and Ubuntu 17.04. It was reintroduced to
  Ubuntu but without any real commitment to maintain the package.

  Its last upstream release was 9 years ago
  https://download.gnome.org/sources/xchat-gnome/0.26/

  The Ubuntu version is a bizarre mix up of a git snapshot and 37
  patches.

  Users would be better off switching to hexchat which is actually
  maintained.

  See also https://launchpad.net/bugs/1753169 for xchat, a somewhat
  different app with the same general problem.

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

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

[Desktop-packages] [Bug 1738164] Re: [snap] U2F doesn't work with yubikey

@Chris: can you try the following, and report whether this addresses the
issue:

snap refresh chromium --channel=candidate/raw-usb-test
snap connect chromium:raw-usb

Thanks!

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [snap] U2F doesn't work with yubikey

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  (initially reported by Daniel at https://forum.snapcraft.io/t/call-
  for-testing-chromium-62-0-3202-62/2569/50)

« U2F (Universal 2nd Factor) isn’t working when signing into my
  gmail account trying to use my yubikey. This is a USB device which
  IIRC chromium needs bidirectional communication with. »

  This requires investigation, but the yubikey I have is too old and
  doesn't support U2F.

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

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

[Desktop-packages] [Bug 1760104] Re: Xorg crashed with SIGSEGV

2018-05-16 Thread Alan Pope  濾

I've added a task for snapd, because this only happens when I'm doing
"snap install" something. Usually at the point when it connects the
opengl interface.

** Information type changed from Private to Public

** Also affects: snapd
   Importance: Undecided
   Status: New

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

Title:
  Xorg crashed with SIGSEGV

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

Bug description:
  Installed a snap, immediately after I installed it, the machine froze
  and then x crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.42  Sat Mar  3 04:10:22 
PST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-12ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Mar 30 14:15:35 2018
  Disassembly: => 0x7f6b0008:   Cannot access memory at address 
0x7f6b0008
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:13d7] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:6541]
  InstallationDate: Installed on 2018-02-13 (44 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Notebook P65_P67RGRERA
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=d6c2bf6a-9191-40b5-b3f5-ce493dcdec01 ro quiet splash vt.handoff=1
  SegvAnalysis:
   Segfault happened at: 0x7f6b0008:Cannot access memory at address 
0x7f6b0008
   PC (0x7f6b0008) not located in a known VMA region (needed executable 
region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   ()
   ()
   ()
   ()
   start_thread (arg=0x7f6b3c98b700) at pthread_create.c:463
  Title: Xorg crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_P67RGRERA
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.13:bd01/27/2016:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_P67RGRERA
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  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
  xserver.bootTime: Thu Mar 29 14:49:09 2018
  xserver.configfile: default
  xserver.errors:
   client bug: Invalid path /dev/input/event7
   systemd-logind: failed to take device

[Desktop-packages] [Bug 1770238] Re: [nvidia] Logging in results in a black screen for many minutes after which the login screen reappears and I am able to login fine.

2018-05-16 Thread Jonathan

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

I cannot view my own error reports, it just tells me I don't have
permission and am not part of the correct group. I filled out the form
to request access so we shall see.

I'm not sure if my original error is a duplicate of bug #154192. There
doesn't appear to be a crash involved. gdm-x-session just seems to shut
itself down because it couldn't find monitors.  Even though it works
after a system reload.

 May 9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE)
Screen(s) found, but none have a usable configuration.

It definitely does seem I am being hit by a miriad of bugs.  Its getting
pretty frustrating to keep using it. And its also hard to tell the
difference between them.

Issues as far as I can tell:
* First login fails due to no usable monitors, if wayland is disabled. 
(Workaround, don't disable wayland)
* gnome-calculator and possibly other snap apps lock up the computer when 
opened if wayland is disabled. (Workaround, don't disable wayland)
* System locks up and reboots. (Unknown cause, no errors appear in logs as they 
don't get flushed to disk.)
* Gnome locks up and I am returned to login screen (Unknown cause but seems to 
generate a variety of different crash reports)

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

Title:
  [nvidia] Logging in results in a black screen for many minutes after
  which the login screen reappears and I am able to login fine.

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  ** Ubuntu Bionic; Nvidia GTX 1050 w/`nvidia-390` drivers

  ** Problem: Logging in results in a black screen for many minutes after which 
the login screen reappears and I am able to login fine. The below log seems to 
be the earliest error when this occurs.
  Note: This happened twice today so far, presumably each time I reboot.

  
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE) 
NVIDIA(GPU-0): Failed to acquire modesetting permission.
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE) 
NVIDIA(0): Failing initialization of X screen 0
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (II) 
UnloadModule: "nvidia"
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (II) 
UnloadSubModule: "wfb"
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (II) 
UnloadSubModule: "fb"
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE) 
Screen(s) found, but none have a usable configuration.
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE)
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: Fatal 
server error:
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE) no 
screens found(EE)
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE)

  ** A systemd-logind watchdog seems to be responsible for the login
  screen reappearing

  May  9 11:20:02 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Watchdog 
timeout (limit 3min)!
  May  9 11:20:02 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Killing 
process 1697 (systemd-logind) with signal SIGABRT.
  May  9 11:20:03 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Main 
process exited, code=dumped, status=6/ABRT
  May  9 11:20:03 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Failed 
with result 'watchdog'.

  ** The Xorg.0.log doesn't seem to have any problem finding the screens
  just before the above error.

  29406:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(II) NVIDIA(0): NVIDIA GPU GeForce GTX 1050 (GP107-A) at PCI:23:0:0 (GPU-0)
  29407:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(--) NVIDIA(0): Memory: 2097152 kBytes
  29408:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(--) NVIDIA(0): VideoBIOS: 86.07.2f.00.68
  29409:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(II) NVIDIA(0): Detected PCI Express Link width: 16X
  29412:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(--) NVIDIA(GPU-0): Acer AL1917 (DFP-0): connected
  29413:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(--) NVIDIA(GPU-0): Acer AL1917 (DFP-0): Internal TMDS
  29414:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(--) NVIDIA(GPU-0): Acer AL1917 (DFP-0): 330.0 MHz maximum pixel clock
  29415:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(--) NVIDIA(GPU-0):

  
  ** Note that I also saw the watchdog kick in while I was logged in and 
working when I was suddenly sent back to the login screen.  I believe that 
lines up

Re: [Desktop-packages] [Bug 1771540] Re: i am not able to install the updates

2018-05-16 Thread pawan naresh chandiramani

I am getting failed to connect to a server and then it's saying check your
internet connection, but I am able to browse the net via my internet
connection

On Wed 16 May, 2018, 4:20 PM dino99, <1771...@bugs.launchpad.net> wrote:

> Reporting againg 'xorg' is unrelated to 'upgrade'; should have been
> reported against 'apt' instead.
> So all the logs joined here are useless for fixing that problem.
>
> What are the outputs of:
>
> sudo apt-get install -f
> sudo apt-get update && sudo apt-get upgrade
>
> Usually in such a case, either some package(s) are broken due to
> dependencies conflict. If you have some ppa's package(s) installed, then
> downgrade via 'ppa-purge'
>
> ** Changed in: xorg (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1771540
>
> Title:
>   i am not able to install the updates
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>i am not able to install the updates
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: xorg 1:7.7+13ubuntu3
>   ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
>   Uname: Linux 4.4.0-98-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.1-0ubuntu2.10
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   Date: Wed May 16 15:19:58 2018
>   DistUpgraded: 2017-09-01 00:53:53,943 WARNING no activity on terminal
> for 300 seconds (Installed python3-renderpm (amd64))
>   DistroCodename: xenial
>   DistroVariant: ubuntu
>   DpkgLog:
>
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07)
> (prog-if 00 [VGA controller])
>  Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
>   InstallationDate: Installed on 2017-08-01 (287 days ago)
>   InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64
> (20160803)
>   MachineType: Dell Inc. Inspiron 5559
>   ProcEnviron:
>LANGUAGE=en_IN:en
>PATH=(custom, no user)
>LANG=en_IN
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed
> root=UUID=1cde99c2-2259-44dd-a873-b302c0633c92 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: Upgraded to xenial on 2017-08-31 (257 days ago)
>   dmi.bios.date: 09/16/2015
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.0.6
>   dmi.board.name: 04D1V1
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr1.0.6:bd09/16/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn04D1V1:rvrA00:cvnDellInc.:ct9:cvr:
>   dmi.product.name: Inspiron 5559
>   dmi.sys.vendor: Dell Inc.
>   version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
>   version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.10.1-1ubuntu2
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20160325-1ubuntu1.2
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.12-1build2
>   xserver.bootTime: Wed May 16 13:57:14 2018
>   xserver.configfile: default
>   xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.outputs:
>product id1557
>vendor BOE
>   xserver.version: 2:1.18.4-0ubuntu0.7
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771540/+subscriptions
>

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

Title:
  i am not able to install the updates

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
   i am not able to install the updates

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist:

[Desktop-packages] [Bug 1771278] Re: search in gnome is not working

2018-05-16 Thread Jeremy Bicha

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

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

Title:
  search in gnome is not working

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  
  1)
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  2)
  gnome-shell:
Installed: 3.28.1-0ubuntu2
Candidate: 3.28.1-0ubuntu2
Version table:
   *** 3.28.1-0ubuntu2 500
  500 http://lu.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status


  3)
  When I press Super key and start typing to search, the results of the search 
should appear.

  4)
  Instead nothing happens.

  I see this errors in syslog.

  May 15 08:44:24 Acer18 gnome-shell[2385]: JS ERROR: TypeError:
  provider.display is
  
undefined#012_clearDisplay/<@resource:///org/gnome/shell/ui/search.js:605:13#012_clearDisplay@resource:///org/gnome/shell/ui/search.js:604:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_reset@resource:///org/gnome/shell/ui/search.js:495:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012setTerms@resource:///org/gnome/shell/ui/search.js:555:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_onTextChanged@resource:///org/gnome/shell/ui/viewSelector.js:532:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012reset@resource:///org/gnome/shell/ui/viewSelector.js:464:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/viewSelector.js:284:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_animateVisible@resource:///org/gnome/shell/ui/overview.js:554:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/overview.js:540:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012toggle@resource:///org/gnome/shell/ui/overview.js:670:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_initializeUI/<@resource:///org/gnome/shell/ui/main.js:197:13

  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 15 08:49:24 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['vscode-search-provi...@jomik.org']"
   b'org.gnome.shell' b'command-history' redacted by apport
   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-05-02 (12 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/1771278/+subscriptions

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

[Desktop-packages] [Bug 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus

2018-05-16 Thread Ubuntu Foundations Team Bug Bot

The attachment "AMD64 .deb included, with .patch file" seems to be a
patch.  If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Pressing any global keyboard shortcut causes temporary loss of focus

Status in GNOME Settings Daemon:
  Confirmed
Status in compiz package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  In Progress
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-settings-daemon package in ALT Linux:
  Unknown
Status in gnome-shell package in Fedora:
  Confirmed
Status in gnome package in openSUSE:
  Unknown

Bug description:
  When pressing any global keyboard shourtcut (configurable via System
  settings -> Keyboard -> Shortcuts; i.e. for switching keyboard layout,
  volume up/down), focus temporary switches from active text input to
  something else, then restores back shortly. Maybe even active window
  loses focus, but window frame does not shows this (window header
  remains to look active).

  For example: when I press ctrl+shift here to switch keyboard layout,
  when writing this description, yellow frame disappears from text input
  box, text caret disappears too; they appear again when releasing
  ctrl+shift. The same occurs in all other programs, i.e. terminal.

  It causes serious annoyance, for example in Twitter when losing focus
  in Reply text box, reply rolls up and I have to click it again with
  mouse and set caret to correct place each time I switch keyboard
  layouts.

  Other key combinations, not only ctrl+shift, also cause this.

  It is especially annoying when using keyboard layout switch shortcut
  handled by the same subsystem (media-keys plugin):

  case SWITCH_INPUT_SOURCE_KEY:
  case SWITCH_INPUT_SOURCE_BACKWARD_KEY:
  do_switch_input_source_action (manager, type);
  break;

  (Original gnome-settings-daemon, from which unity-settings-daemon was
  forked, does not use media-keys plugin to switch keyboard layout).

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-session 3.9.90-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Thu Oct 24 11:42:19 2013
  InstallationDate: Installed on 2013-10-23 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus

2018-05-16 Thread Penn Mackintosh

I have confirmed that the above patch works by applying it and running
xev. I then pressed META+SPACE and the keyboard layout changed without
any output from xev.

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

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

Title:
  Pressing any global keyboard shortcut causes temporary loss of focus

Status in GNOME Settings Daemon:
  Confirmed
Status in compiz package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  In Progress
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-settings-daemon package in ALT Linux:
  Unknown
Status in gnome-shell package in Fedora:
  Confirmed
Status in gnome package in openSUSE:
  Unknown

Bug description:
  When pressing any global keyboard shourtcut (configurable via System
  settings -> Keyboard -> Shortcuts; i.e. for switching keyboard layout,
  volume up/down), focus temporary switches from active text input to
  something else, then restores back shortly. Maybe even active window
  loses focus, but window frame does not shows this (window header
  remains to look active).

  For example: when I press ctrl+shift here to switch keyboard layout,
  when writing this description, yellow frame disappears from text input
  box, text caret disappears too; they appear again when releasing
  ctrl+shift. The same occurs in all other programs, i.e. terminal.

  It causes serious annoyance, for example in Twitter when losing focus
  in Reply text box, reply rolls up and I have to click it again with
  mouse and set caret to correct place each time I switch keyboard
  layouts.

  Other key combinations, not only ctrl+shift, also cause this.

  It is especially annoying when using keyboard layout switch shortcut
  handled by the same subsystem (media-keys plugin):

  case SWITCH_INPUT_SOURCE_KEY:
  case SWITCH_INPUT_SOURCE_BACKWARD_KEY:
  do_switch_input_source_action (manager, type);
  break;

  (Original gnome-settings-daemon, from which unity-settings-daemon was
  forked, does not use media-keys plugin to switch keyboard layout).

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-session 3.9.90-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Thu Oct 24 11:42:19 2013
  InstallationDate: Installed on 2013-10-23 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus

2018-05-16 Thread Penn Mackintosh

I have a patch, taken from SO.

Patch is attached for package xorg-server.
After building with it, you need to install xserver-xorg-core-*.deb package 
generated.
I have attached the .deb too.

** Attachment added: "AMD64 .deb included"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1244090/+attachment/5140329/+files/patches.zip

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

Title:
  Pressing any global keyboard shortcut causes temporary loss of focus

Status in GNOME Settings Daemon:
  Confirmed
Status in compiz package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  In Progress
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-settings-daemon package in ALT Linux:
  Unknown
Status in gnome-shell package in Fedora:
  Confirmed
Status in gnome package in openSUSE:
  Unknown

Bug description:
  When pressing any global keyboard shourtcut (configurable via System
  settings -> Keyboard -> Shortcuts; i.e. for switching keyboard layout,
  volume up/down), focus temporary switches from active text input to
  something else, then restores back shortly. Maybe even active window
  loses focus, but window frame does not shows this (window header
  remains to look active).

  For example: when I press ctrl+shift here to switch keyboard layout,
  when writing this description, yellow frame disappears from text input
  box, text caret disappears too; they appear again when releasing
  ctrl+shift. The same occurs in all other programs, i.e. terminal.

  It causes serious annoyance, for example in Twitter when losing focus
  in Reply text box, reply rolls up and I have to click it again with
  mouse and set caret to correct place each time I switch keyboard
  layouts.

  Other key combinations, not only ctrl+shift, also cause this.

  It is especially annoying when using keyboard layout switch shortcut
  handled by the same subsystem (media-keys plugin):

  case SWITCH_INPUT_SOURCE_KEY:
  case SWITCH_INPUT_SOURCE_BACKWARD_KEY:
  do_switch_input_source_action (manager, type);
  break;

  (Original gnome-settings-daemon, from which unity-settings-daemon was
  forked, does not use media-keys plugin to switch keyboard layout).

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-session 3.9.90-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Thu Oct 24 11:42:19 2013
  InstallationDate: Installed on 2013-10-23 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768756] Re: Libreoffice 6 does not start on Kubuntu 18.04 (clean install)

Indeed, when doing a minimal install a normal install is performed and
then a selected list of packages is removed (casper/filesystem.manifest-
minimal-remove on the iso).

How did you initially install libreoffice after doing the minimal
install? Was it with a graphical package manager, or with apt in a
terminal?

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

Title:
  Libreoffice 6 does not start on Kubuntu 18.04 (clean install)

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I just did a clean install of Kubuntu 18.04 (the minimal one) and
  manually installed Libreoffice [1]. Now, when I try to start it, I get
  this:

  $ libreoffice 
  terminate called after throwing an instance of 
'com::sun::star::uno::RuntimeException'

  
  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7f8545b22568]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c316)[0x7f8545b4b316]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7f854575cf20]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f854575ce97]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f854575e801]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x8c8fb)[0x7f853d5228fb]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x92d3a)[0x7f853d528d3a]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x92d95)[0x7f853d528d95]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(__cxa_rethrow+0x4d)[0x7f853d52903d]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x10ab728)[0x7f8546e14728]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN10comphelper6detail20ConfigurationWrapper3getERKN3com3sun4star3uno9ReferenceINS5_17XComponentContextEEE+0x47)[0x7f8546e147f7]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN12OpenGLHelper18isVCLOpenGLEnabledEv+0x2e5)[0x7f8548b408c5]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN10SalDisplay10BestVisualEP9_XDisplayiR11XVisualInfo+0xfd)[0x7f852dbdbc2d]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZNK10SalDisplay10initScreenE12SalX11Screen+0x8b)[0x7f852dbe113b]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN7vcl_sal9WMAdaptorC1EP10SalDisplay+0x21d)[0x7f852dbe6e4d]
  /usr/lib/libreoffice/program/libvclplug_genlo.so(+0x4024b)[0x7f852dbe724b]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN7vcl_sal9WMAdaptor15createWMAdaptorEP10SalDisplay+0x21)[0x7f852dbe8171]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN10SalDisplay4InitEv+0x467)[0x7f852dbe2997]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN13SalX11DisplayC1EP9_XDisplay+0x24)[0x7f852dbe2b44]
  /usr/lib/libreoffice/program/libvclplug_kde4lo.so(+0x1963e)[0x7f85302d263e]
  /usr/lib/libreoffice/program/libvclplug_kde4lo.so(+0x1e636)[0x7f85302d7636]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN14X11SalInstance12AfterAppInitEv+0x12)[0x7f852dbe3282]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z7InitVCLv+0x382)[0x7f8548a53742]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cebd3d)[0x7f8548a54d3d]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7f8548a54da0]
  
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7f8547a9a215]
  /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x560c5d84978b]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f854573fb97]
  /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x560c5d8497ca]

  No matter what I try (e.g. [2]), the result is always the same.

  I also tried to remove my config dir [3] but no luck.

  Any idea what could be wrong? Thanks.

  Description:Ubuntu 18.04 LTS
  Release:18.04

  libreoffice version: 6.0.3-0ubuntu1

  [1] apt install libreoffice
  [2] libreoffice --help
  [3] ~/.config/libreoffice/

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

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

[Desktop-packages] [Bug 1738164] Re: [snap] U2F doesn't work with yubikey

It looks like the raw-usb interface might help here. I'll rebuild the
snap with it and will post instructions on how to test.

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

Title:
  [snap] U2F doesn't work with yubikey

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  (initially reported by Daniel at https://forum.snapcraft.io/t/call-
  for-testing-chromium-62-0-3202-62/2569/50)

« U2F (Universal 2nd Factor) isn’t working when signing into my
  gmail account trying to use my yubikey. This is a USB device which
  IIRC chromium needs bidirectional communication with. »

  This requires investigation, but the yubikey I have is too old and
  doesn't support U2F.

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

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

[Desktop-packages] [Bug 1713034] Re: gnome-shell crashed with SIGABRT in _ip_get_path_for_wd() ["assertion failed: (wd >= 0)"]

** Changed in: glib
   Status: Confirmed => Incomplete

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

Title:
  gnome-shell crashed with SIGABRT in _ip_get_path_for_wd() ["assertion
  failed: (wd >= 0)"]

Status in GLib:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  https://errors.ubuntu.com/problem/3554ed6882d41ea6b6fe921fbc9450c857b89eaa
  https://errors.ubuntu.com/problem/7d4e9fc521926903d3f796d9d01b38c242396745
  https://errors.ubuntu.com/problem/1f19262e2fd594a3cf2d89af52d8a58b42aa2c56

  ---

  ProblemType: CrashDistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Aug 25 12:05:50 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-08-13 (1107 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140810)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 6SourcePackage: gnome-shell
  StacktraceTop:
   g_assertion_message () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1687817] Re: Inkscape 0.92.1-1 always reverts display units to px

2018-05-16 Thread Alvin Penner

could you attach the svg file you are using, for testing purposes?

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

Title:
  Inkscape 0.92.1-1 always reverts display units to px

Status in Inkscape:
  New
Status in inkscape package in Ubuntu:
  New

Bug description:
  Files created in Inkscape 0.92 no longer respect user's display units.
  Inkscape 0.91 didn't have this problem.

  Expected results:

  1. Open Inkscape
  2. Set File → Document Properties → Display Units to mm
  3. Edit and save the file, then quit Inkscape
  4. Reopen the docuemnt in Inkscape, and the Display Units value in the object 
toolbar and the Document Properties should remain as mm.

  Actual results:

  
  1. Open Inkscape
  2. Set File → Document Properties → Display Units to mm
  3. Edit and save the file, then quit Inkscape
  4. Reopen the docuemnt in Inkscape, and the Display Units value in the object 
toolbar and the Document Properties are set to px.
  5. Alternatively, File → Save As… immediately changes Display units to px.

  I work with laser cut patterns made in Inkscape, and maintaining
  document size is critical. I know about the recent 90/96 px/inch
  change, and this shouldn't be affected by that

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: inkscape 0.92.1-1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue May  2 19:37:46 2017
  InstallationDate: Installed on 2015-03-08 (786 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: inkscape
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (17 days ago)

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

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

[Desktop-packages] [Bug 1771513] Re: package ibus-gtk:amd64 1.5.11-1ubuntu2 failed to install/upgrade: package ibus-gtk:amd64 is not ready for configuration cannot configure (current status 'half-inst

Can you run the following command in a terminal and share the output?

sudo apt -f install

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

Title:
  package ibus-gtk:amd64 1.5.11-1ubuntu2 failed to install/upgrade:
  package ibus-gtk:amd64 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in ibus package in Ubuntu:
  New

Bug description:
  Hello

  Notification relating ibus appears when I open my notebook.
  I don't know what is about this but everything is working nice

  Version :ubuntu 16.04 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ibus-gtk:amd64 1.5.11-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Mon May 14 18:03:21 2018
  DuplicateSignature:
   package:ibus-gtk:amd64:1.5.11-1ubuntu2
   Processing triggers for doc-base (0.10.7) ...
   Processing 2 added doc-base files...
   dpkg: error processing package ibus-gtk:amd64 (--configure):
package ibus-gtk:amd64 is not ready for configuration
  ErrorMessage: package ibus-gtk:amd64 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2018-04-03 (42 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: ibus
  Title: package ibus-gtk:amd64 1.5.11-1ubuntu2 failed to install/upgrade: 
package ibus-gtk:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1771540] Re: i am not able to install the updates

2018-05-16 Thread dino99

Reporting againg 'xorg' is unrelated to 'upgrade'; should have been reported 
against 'apt' instead.
So all the logs joined here are useless for fixing that problem.

What are the outputs of:

sudo apt-get install -f
sudo apt-get update && sudo apt-get upgrade

Usually in such a case, either some package(s) are broken due to
dependencies conflict. If you have some ppa's package(s) installed, then
downgrade via 'ppa-purge'

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

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

Title:
  i am not able to install the updates

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
   i am not able to install the updates

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed May 16 15:19:58 2018
  DistUpgraded: 2017-09-01 00:53:53,943 WARNING no activity on terminal for 300 
seconds (Installed python3-renderpm (amd64))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2017-08-01 (287 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 5559
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=1cde99c2-2259-44dd-a873-b302c0633c92 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-08-31 (257 days ago)
  dmi.bios.date: 09/16/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.6
  dmi.board.name: 04D1V1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.6:bd09/16/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn04D1V1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed May 16 13:57:14 2018
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1557 
   vendor BOE
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Desktop-packages] [Bug 1738164] Re: [snap] U2F doesn't work with yubikey

2018-05-16 Thread Chris Cowling

It appears that apparmor is blocking u2f requests :


[ 5955.568022] audit: type=1400 audit(1526465659.599:92): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/0003:045E:07B2.0001/report_descriptor"
 pid=19386 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
[ 5955.568379] audit: type=1400 audit(1526465659.599:93): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.1/0003:045E:07B2.0002/report_descriptor"
 pid=19386 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
[ 5955.568667] audit: type=1400 audit(1526465659.599:94): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.2/0003:045E:07B2.0003/report_descriptor"
 pid=19386 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
[ 5955.569840] audit: type=1400 audit(1526465659.599:95): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:1050:0407.002D/report_descriptor"
 pid=19386 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
[ 5955.570337] audit: type=1400 audit(1526465659.603:96): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.1/0003:1050:0407.002E/report_descriptor"
 pid=19386 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0

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

Title:
  [snap] U2F doesn't work with yubikey

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  (initially reported by Daniel at https://forum.snapcraft.io/t/call-
  for-testing-chromium-62-0-3202-62/2569/50)

« U2F (Universal 2nd Factor) isn’t working when signing into my
  gmail account trying to use my yubikey. This is a USB device which
  IIRC chromium needs bidirectional communication with. »

  This requires investigation, but the yubikey I have is too old and
  doesn't support U2F.

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

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

[Desktop-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

** Changed in: network-manager
   Status: Confirmed => Fix Released

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Bionic:
  Confirmed

Bug description:
  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

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

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

[Desktop-packages] [Bug 1758163] Re: Please remove xchat-gnome from Ubuntu (again)

2018-05-16 Thread Kieran Bingham

I find my way here after losing xchat-gnome on the bionic upgrade:

Ok - so I just tried out hexchat - and that seems to be pretty good
alternative / update.

Is there a way to get apt to suggest / recommend hexchat instead of
failing to install xchat-gnome?

"""
# sudo apt-get install xchat-gnome
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Package xchat-gnome is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'xchat-gnome' has no installation candidate
"""

It would be useful for that to print the alternatives - or just install
hexchat as a replacement :D

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

Title:
  Please remove xchat-gnome from Ubuntu (again)

Status in xchat-gnome package in Ubuntu:
  Fix Released

Bug description:
  xchat-gnome is unmaintained.

  It was removed from Debian and Ubuntu 17.04. It was reintroduced to
  Ubuntu but without any real commitment to maintain the package.

  Its last upstream release was 9 years ago
  https://download.gnome.org/sources/xchat-gnome/0.26/

  The Ubuntu version is a bizarre mix up of a git snapshot and 37
  patches.

  Users would be better off switching to hexchat which is actually
  maintained.

  See also https://launchpad.net/bugs/1753169 for xchat, a somewhat
  different app with the same general problem.

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

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

[Desktop-packages] [Bug 1765724] Re: Xenial -> Bionic - System fails to boot after upgrade - gnome-screensaver & gnome-shell fail to start?

2018-05-16 Thread Jean-Baptiste Lallement

I cannot reproduce this issue anymore with a fresh installation of
xenial upgraded to bionic. I'm wondering if the fontconfig fix that
delayed the boot was causing this issue (bug 1749546)

Setting to incomplete.

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

Title:
  Xenial -> Bionic - System fails to boot after upgrade - gnome-
  screensaver & gnome-shell fail to start?

Status in cryptsetup package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Test Case:
  1. Install Xenial Desktop with encrypted home
  2. Upgrade to bionic
  3. Reboot

  Actual Result
  The system appears to fail to start gnome-shell / gnome-screensaver:

  Apr 23 14:17:12 ubuntu dbus-daemon[1645]: [session uid=121 pid=1645] 
Activating service name='org.gnome.ScreenSaver' requested by ':1.3' (uid=121 
pid=1647 comm="/usr/lib/gnome-session/gnome-session-binary --auto
  Apr 23 14:17:12 ubuntu org.gnome.ScreenSaver[1645]: Unable to init server: 
Could not connect: Connection refused
  Apr 23 14:17:12 ubuntu gnome-screensav[1654]: Cannot open display:
  Apr 23 14:17:12 ubuntu dbus-daemon[1645]: [session uid=121 pid=1645] 
Activated service 'org.gnome.ScreenSaver' failed: Process org.gnome.ScreenSaver 
exited with status 1
  Apr 23 14:17:12 ubuntu gnome-session[1647]: gnome-session-binary[1647]: 
CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling 
StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.f
  Apr 23 14:17:12 ubuntu gnome-session-binary[1647]: CRITICAL: Unable to create 
a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for 
org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error
  Apr 23 14:17:12 ubuntu gnome-shell[1656]: Failed to create backend: Could not 
find a primary drm kms device
  Apr 23 14:17:12 ubuntu gnome-session[1647]: gnome-session-binary[1647]: 
WARNING: App 'org.gnome.Shell.desktop' exited with code 1
  Apr 23 14:17:12 ubuntu gnome-session-binary[1647]: WARNING: App 
'org.gnome.Shell.desktop' exited with code 1
  Apr 23 14:17:12 ubuntu gnome-session-binary[1647]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
  Apr 23 14:17:12 ubuntu gdm-launch-environment][1627]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm
  Apr 23 14:17:12 ubuntu gdm3[1187]: GdmDisplay: display lasted 0.292659 seconds
  Apr 23 14:17:12 ubuntu systemd-logind[1028]: Removed session c2.
  Apr 23 14:17:12 ubuntu spice-vdagentd[1186]: Error getting active session: No 
data available
  Apr 23 14:17:12 ubuntu spice-vdagentd[1186]: Error getting active session: No 
data available
  Apr 23 14:17:12 ubuntu gdm3[1187]: Child process -1643 was already dead.

  
  Also the system hangs on boot when it activates the encrypted swap. There are 
the following entries in the journal:
  $ journalctl -b-1 -o short-monotonic |grep crypt
  [1.535326] ubuntu kernel: Key type encrypted registered
  [  125.637205] ubuntu systemd[1]: Dependency failed for Cryptography Setup 
for cryptswap1.
  [  125.637789] ubuntu systemd[1]: Dependency failed for 
dev-mapper-cryptswap1.device.
  [  125.638311] ubuntu systemd[1]: Dependency failed for 
/dev/mapper/cryptswap1.
  [  125.639351] ubuntu systemd[1]: dev-mapper-cryptswap1.swap: Job 
dev-mapper-cryptswap1.swap/start failed with result 'dependency'.
  [  125.639478] ubuntu systemd[1]: dev-mapper-cryptswap1.device: Job 
dev-mapper-cryptswap1.device/start failed with result 'dependency'.
  [  125.639594] ubuntu systemd[1]: Dependency failed for Local Encrypted 
Volumes.
  [  125.640128] ubuntu systemd[1]: cryptsetup.target: Job 
cryptsetup.target/start failed with result 'dependency'.
  [  125.640266] ubuntu systemd[1]: systemd-cryptsetup@cryptswap1.service: Job 
systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'.
  [  383.902153] ubuntu systemd[1]: Starting Cryptography Setup for 
cryptswap1...
  [  383.913899] ubuntu systemd-cryptsetup[672]: Set cipher aes, mode 
xts-plain64, key size 256 bits for device 
/dev/disk/by-uuid/34ea85fd-854b-4892-95b9-7073dd2dbf7b.
  [  384.138596] ubuntu systemd[1]: Started Cryptography Setup for cryptswap1.
  [  384.143845] ubuntu systemd[1]: Reached target Local Encrypted Volumes.
  [  384.167475] ubuntu systemd[1]: Found device /dev/mapper/cryptswap1.
  [  384.171327] ubuntu systemd[1]: Activating swap /dev/mapper/cryptswap1...
  [  384.184639] ubuntu kernel: Adding 2093564k swap on /dev/mapper/cryptswap1. 
 Priority:-2 extents:1 across:2093564k FS
  [  384.191435] ubuntu systemd[1]: Activated swap /dev/mapper/cryptswap1.

  But eventually activates, once the device is there. Note this is not a
  hang, as timeouts are reached "instantly".

  ProblemType: Bug

[Desktop-packages] [Bug 1771540] [NEW] i am not able to install the updates

2018-05-16 Thread pawan naresh chandiramani

Public bug reported:

 i am not able to install the updates

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed May 16 15:19:58 2018
DistUpgraded: 2017-09-01 00:53:53,943 WARNING no activity on terminal for 300 
seconds (Installed python3-renderpm (amd64))
DistroCodename: xenial
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
InstallationDate: Installed on 2017-08-01 (287 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
MachineType: Dell Inc. Inspiron 5559
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=1cde99c2-2259-44dd-a873-b302c0633c92 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2017-08-31 (257 days ago)
dmi.bios.date: 09/16/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.6
dmi.board.name: 04D1V1
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.6:bd09/16/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn04D1V1:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5559
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed May 16 13:57:14 2018
xserver.configfile: default
xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1557 
 vendor BOE
xserver.version: 2:1.18.4-0ubuntu0.7

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


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

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

Title:
  i am not able to install the updates

Status in xorg package in Ubuntu:
  New

Bug description:
   i am not able to install the updates

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed May 16 15:19:58 2018
  DistUpgraded: 2017-09-01 00:53:53,943 WARNING no activity on terminal for 300 
seconds (Installed python3-renderpm (amd64))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2017-08-01 (287 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 5559
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=1cde99c2-2259-44dd-a873-b302c0633c92 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-08-31 (257 days ago)
  dmi.bios.date: 09/16/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.6
  dmi.board.name: 04D1V1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias:

[Desktop-packages] [Bug 1771278] Re: search in gnome is not working

2018-05-16 Thread Matej

Thank you Daniel.

You are right the vscode extension was the problem. After removing it
everything is back to normal.

I don't even remember installing it?!


Thank you for you fast response.

The problem is resolved.

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

Title:
  search in gnome is not working

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  
  1)
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  2)
  gnome-shell:
Installed: 3.28.1-0ubuntu2
Candidate: 3.28.1-0ubuntu2
Version table:
   *** 3.28.1-0ubuntu2 500
  500 http://lu.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status


  3)
  When I press Super key and start typing to search, the results of the search 
should appear.

  4)
  Instead nothing happens.

  I see this errors in syslog.

  May 15 08:44:24 Acer18 gnome-shell[2385]: JS ERROR: TypeError:
  provider.display is
  
undefined#012_clearDisplay/<@resource:///org/gnome/shell/ui/search.js:605:13#012_clearDisplay@resource:///org/gnome/shell/ui/search.js:604:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_reset@resource:///org/gnome/shell/ui/search.js:495:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012setTerms@resource:///org/gnome/shell/ui/search.js:555:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_onTextChanged@resource:///org/gnome/shell/ui/viewSelector.js:532:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012reset@resource:///org/gnome/shell/ui/viewSelector.js:464:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/viewSelector.js:284:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_animateVisible@resource:///org/gnome/shell/ui/overview.js:554:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/overview.js:540:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012toggle@resource:///org/gnome/shell/ui/overview.js:670:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_initializeUI/<@resource:///org/gnome/shell/ui/main.js:197:13

  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 15 08:49:24 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['vscode-search-provi...@jomik.org']"
   b'org.gnome.shell' b'command-history' redacted by apport
   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-05-02 (12 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/1771278/+subscriptions

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

[Desktop-packages] [Bug 484521] Re: Nautilus causes memory leak in Xorg?

** Changed in: xorg-server
   Status: Confirmed => Invalid

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

Title:
  Nautilus causes memory leak in Xorg?

Status in Gnome System Monitor:
  Invalid
Status in X.Org X server:
  Invalid
Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  I'm rather new here, so I hope I can give you the information you need
  for this.

  Ever since I upgraded to 9.10, I've been noticing my Xorg process will
  continue to grow in memory.  I've seen it get to ~2GB.  At that point,
  I kill the process, which then gets restarted and it will be at about
  half the size of whatever it was at before.  I'll need to do this
  every few hours while I'm at work.

  I've been googling to find a solution and there seem to be lots of
  posts that sound similar, but they all end up having a solution that
  doesn't work for me.  I'm not using compiz, so it's not related to
  that.  I'm using gnome with an nVidia video card.

  Finally, I was able to reproduce it reliably by using the nautilus
  file browser.  If I click on a folder like /usr/bin, I watch Xorg's
  memory go up by 30-60MB.  Then if I click on another folder it goes up
  again.  If I just go back and forth between those two folders, I can
  watch the memory continue to grow.  I initially thought it might be a
  cache issue, but it never goes back down.

  When I kill both nautilus and Xorg, then Xorg finally restarts with a
  reasonable ~70MB.

  I'm not sure which program is at fault, Xorg or nautilus.  Has anyone
  else noticed this problem?

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

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

[Desktop-packages] [Bug 1771539] [NEW] Xorg crash

2018-05-16 Thread Mario Costa

Public bug reported:

When I try to use ubuntu with dual desktop display it crashes
continuously, and entering into login mode.

I cannot use dual display.
To use an external monitor, I have to start the laptop with the computer closed.

It seems to be related to the graphic card, maybe dual graphic card of
the laptop.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
Uname: Linux 4.4.0-124-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME-Classic:GNOME
Date: Wed May 16 10:36:05 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
 Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Mars [Radeon HD 8730M] [103c:1990]
InstallationDate: Installed on 2017-12-13 (153 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Hewlett-Packard HP EliteBook 840 G1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=e1833df7-4a4b-41b2-8393-d88536dd0165 ro quiet splash radeon.runpm=0 
vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/26/2016
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L71 Ver. 01.39
dmi.board.name: 198F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 15.59
dmi.chassis.asset.tag: 5CG44010XD
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.39:bd09/26/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 840 G1
dmi.product.version: A3009DD10303
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Mar  8 12:39:32 2018
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug crash ubuntu xenial

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  When I try to use ubuntu with dual desktop display it crashes
  continuously, and entering into login mode.

  I cannot use dual display.
  To use an external monitor, I have to start the laptop with the computer 
closed.

  It seems to be related to the graphic card, maybe dual graphic card of
  the laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Wed May 16 10:36:05 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mars [Radeon HD 8730M] [103c:1990]
  InstallationDate: Installed on 2017-12-13 (153 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  ProcKernelCmdLine:

[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

2018-05-16 Thread Manuel

ADDENDUM to #129: Ah! Success!

I followed the advice of comment #28
(https://bugs.launchpad.net/ubuntu/+source/sane-
backends/+bug/1728012/comments/28), and it works !!!

Did the following:
$ sudo ln -sfr /usr/lib/sane/libsane-epkowa* /usr/lib/x86_64-linux-gnu/sane

Then:
1. Removed the "usb 0x04b8 0x0137" entry I had added to /etc/sane.d/epkowa.conf
2. Added a 55-epson-libsane.rules file to /etc/udev/rules.d/ with the following 
text:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE=="0666"
SUBSYSTEM=="usb_device", MODE=="0666"
ATTRS{manufacturer}=="EPSON", DRIVERS=="usb", SUBSYSTEMS=="usb", 
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="*", MODE="0666"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0137", MODE="0666", 
GROUP="scanner", ENV{libsane_matched}="yes"

Finally I unplugged / plugged my scanner and tried:
$ scanimage -L

And got this encouraging answer:
device `epkowa:interpreter:003:011' is a Epson GT-S50 flatbed scanner

Then I started iscan (Image Scan!) and it immediately detected my scanner.
I then could successfully scan a page.

The workaround is thus effective! Thanks to all contributions :-)

-- 
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 1771273] Re: Gnome-shell crashes when wake up after updated to 3.28.1-0ubuntu2

2018-05-16 Thread Zihang Ye

Hi Daniel, after read through your suggestion, I found some problem. I'm 
actually using Wayland, so that shouldn't be a Xorg crash, right?
And in the /etc/gdm3/custom.conf, I saw this:
# Uncomment the line below to force the login screen to use Xorg
# WaylandEnabled=false
So does that mean during my usage of my system, I've never activated the Xorg 
server? I don't know much about how things work.

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

Title:
  Gnome-shell crashes when wake up after updated to 3.28.1-0ubuntu2

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  After having updated gnome-shell from 3.28.1-0ubuntu1 to 3.28.1-0ubuntu2, 
I've experienced the gnome-shell crash after every time I wake it up. It seems 
that it has killed my session.
  When I wakes my computer up, it shows the very first message usually only 
appear when starting the computer, like starting the snappy daemon, starting 
mysql server, etc.

  I'm using Ubuntu 18.04 LTS, Gnome-shell, Wayland.

  Please tell me what information I need to provide to confirm this bug.
  Thanks.

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

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

[Desktop-packages] [Bug 1771273] Re: Gnome-shell crashes when wake up after updated to 3.28.1-0ubuntu2

2018-05-16 Thread Zihang Ye

Thank you for replying, Daniel. I'll try that out. However, since I
can't reproduce it, you might have to wait for a long time before my
next reply.

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

Title:
  Gnome-shell crashes when wake up after updated to 3.28.1-0ubuntu2

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  After having updated gnome-shell from 3.28.1-0ubuntu1 to 3.28.1-0ubuntu2, 
I've experienced the gnome-shell crash after every time I wake it up. It seems 
that it has killed my session.
  When I wakes my computer up, it shows the very first message usually only 
appear when starting the computer, like starting the snappy daemon, starting 
mysql server, etc.

  I'm using Ubuntu 18.04 LTS, Gnome-shell, Wayland.

  Please tell me what information I need to provide to confirm this bug.
  Thanks.

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

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

[Desktop-packages] [Bug 1771385] Re: [snap] 66.0.3359.170 in candidate channel renders fonts incorrectly

** Changed in: chromium-browser (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  [snap] 66.0.3359.170 in candidate channel renders fonts incorrectly

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Steps to reproduce:

   1) $ snap install chromium
   2) $ snap run chromium
   3) observe that fonts are correctly rendered, both in the chrome and in web 
content
   4) $ snap refresh chromium --candidate
   5) $ snap run chromium

  Expected result: fonts are still rendered correctly.

  Current result: fonts are rendered incorrectly (see attached
  screenshot).

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

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

[Desktop-packages] [Bug 1769981] Re: Temporary screen freeze when coming back from screen standby