[Desktop-packages] [Bug 66566]

2018-12-22 Thread Joshua Bell
This change made me a little sad. I used the old hotkeys about a quarter
or a third of every time I used the URL bar.

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

Title:
  Inconsistent shortcuts for new tab

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Won't Fix
Status in firefox-3.0 package in Ubuntu:
  Won't Fix
Status in firefox-3.5 package in Ubuntu:
  Won't Fix

Bug description:
  There are currently too many shortcuts when opening a link in a new
  tab:

   - location bar:  + 
   - GO button:  + click
   - search bar:  + 
   - SEARCH button  + click
   - links:  + click
   - menu bar:  + click
   - BACKWARD/FORWARD button:  + click

  This is one of the reasons I'm keeping with Opera. There it is always
  the shift key and I have to remember only one key.

  Thanks for reading!

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

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


[Desktop-packages] [Bug 66566]

2018-12-22 Thread Gijskruitbosch+bugs
(In reply to Abhro from comment #152)
> I do have history turned off, but visit previously visited sites that I do
> know that TLD for and do not need to search for, thus pressing
> [Ctrl+]Shift+Enter for .net / .org directly. I see the usefulness in being
> able to open new windows from the awesome bar, but the .net / .org is still
> widely enough used TLDs

IME, less so across the globe - that is, if I'm in (say) France, I'd
probably prefer `.fr`, in South Africa, .za, etc.

The .net/.org shortcut was always hardcoded, and as noted before, no
other browser has shortcuts for any other domains.

> that such autocomplete is desired behavior for some.
> Any advice on reverting the behavior, or making a toggle between 'TLD
> autocomplete' and 'open address in new window' possible?

You can control the suffix of `.com` and change it to something else
using the `browser.fixup.alternate.suffix` pref in about:config , if you
like. You could also use bookmarks for the sites you use regularly
enough that you know the TLD, so that you don't need a modifier key at
all and can probably hit enter sooner (TBH, I suspect this is likely to
be an improvement for your usecase). As I already said in comment #150,
I don't think we'll bring back (an option to use) separate modifier keys
for .net/.org. Marco, can you confirm?

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

Title:
  Inconsistent shortcuts for new tab

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Won't Fix
Status in firefox-3.0 package in Ubuntu:
  Won't Fix
Status in firefox-3.5 package in Ubuntu:
  Won't Fix

Bug description:
  There are currently too many shortcuts when opening a link in a new
  tab:

   - location bar:  + 
   - GO button:  + click
   - search bar:  + 
   - SEARCH button  + click
   - links:  + click
   - menu bar:  + click
   - BACKWARD/FORWARD button:  + click

  This is one of the reasons I'm keeping with Opera. There it is always
  the shift key and I have to remember only one key.

  Thanks for reading!

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

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


[Desktop-packages] [Bug 66566]

2018-12-22 Thread Mak77
(In reply to :Gijs (he/him) from comment #153)
> As I already said in comment #150, I don't think we'll bring
> back (an option to use) separate modifier keys for .net/.org. Marco, can you
> confirm?

No plain in sight.
You can star a page and use autofill for it though, if you access it often 
enough.

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

Title:
  Inconsistent shortcuts for new tab

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Won't Fix
Status in firefox-3.0 package in Ubuntu:
  Won't Fix
Status in firefox-3.5 package in Ubuntu:
  Won't Fix

Bug description:
  There are currently too many shortcuts when opening a link in a new
  tab:

   - location bar:  + 
   - GO button:  + click
   - search bar:  + 
   - SEARCH button  + click
   - links:  + click
   - menu bar:  + click
   - BACKWARD/FORWARD button:  + click

  This is one of the reasons I'm keeping with Opera. There it is always
  the shift key and I have to remember only one key.

  Thanks for reading!

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

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


[Desktop-packages] [Bug 66566]

2018-12-22 Thread Abhro-r-dev
(In reply to :Gijs (he/him) from comment #151)
> (In reply to smmalis37 from comment #150)
> > > What happened so shift+enter and ctrl+shift+enter?
> > > Up to know shift+enter did .net and ctrl+shift+enter did .org.. now it 
> > > does
> > > open a new window or simply use .com.
> > 
> > I've been a Firefox user for years now. I use these keyboard shortcuts
> > daily. net and org are still extremely common TLDs, even with others
> > becoming more common. This change is annoying enough for me to seriously
> > consider downgrading to 63. I ask the Firefox team to please consider
> > reverting this change until there is a way for this functionality to be
> > supported by an extension.
> 
> I don't see this happening. Consistency both with other browsers and other
> shortcuts trumps the need for alternative domain autocompleting (and really,
> without the other browsers it would probably have trumped .com autocomplete,
> too).
> 
> I'm also really quite confused by the .net / .org case - do you turn off
> autocomplete and/or history (in the location bar), or something? Why can't
> you just hit "normal" enter when the domain you want gets autocompleted? Do
> you just visit new .net/.org domains (where you somehow do know the exact
> TLD you want, so you don't use a search engine, but you have never visited
> before) every day? That seems like a very niche usecase...
> 
> In terms of add-ons, it'd be pretty trivial to write an add-on that just
> provided you a toolbar button that, when clicked (or activated via a new
> shortcut of the add-on's choosing), provided an alternative input, where you
> could type anything and it'd just suffix '.net' or '.org' and navigate the
> current URL to it. I accept that's quite kludgy, but if you really can't use
> autocomplete / history for this and are annoyed at typing '.net' or '.org'
> after URLs, I think that might currently be your best option.

I do have history turned off, but visit previously visited sites that I
do know that TLD for and do not need to search for, thus pressing
[Ctrl+]Shift+Enter for .net / .org directly. I see the usefulness in
being able to open new windows from the awesome bar, but the .net / .org
is still widely enough used TLDs that such autocomplete is desired
behavior for some. Any advice on reverting the behavior, or making a
toggle between 'TLD autocomplete' and 'open address in new window'
possible?

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

Title:
  Inconsistent shortcuts for new tab

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Won't Fix
Status in firefox-3.0 package in Ubuntu:
  Won't Fix
Status in firefox-3.5 package in Ubuntu:
  Won't Fix

Bug description:
  There are currently too many shortcuts when opening a link in a new
  tab:

   - location bar:  + 
   - GO button:  + click
   - search bar:  + 
   - SEARCH button  + click
   - links:  + click
   - menu bar:  + click
   - BACKWARD/FORWARD button:  + click

  This is one of the reasons I'm keeping with Opera. There it is always
  the shift key and I have to remember only one key.

  Thanks for reading!

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

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


[Desktop-packages] [Bug 1809572] [NEW] The photo viewer - shotwell-is running slowly

2018-12-22 Thread SYN-2009
Public bug reported:

Hi! The photo viewer - shotwell-is running slowly. Work on cutting
photos almost does not work, very slow. In OS Ubuntu 16.04 worked well.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: shotwell 0.28.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 23 13:16:42 2018
InstallationDate: Installed on 2018-05-06 (231 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: shotwell
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  The photo viewer - shotwell-is running slowly

Status in shotwell package in Ubuntu:
  New

Bug description:
  Hi! The photo viewer - shotwell-is running slowly. Work on cutting
  photos almost does not work, very slow. In OS Ubuntu 16.04 worked
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: shotwell 0.28.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 23 13:16:42 2018
  InstallationDate: Installed on 2018-05-06 (231 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: shotwell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1809571] [NEW] Does not turn off the PC

2018-12-22 Thread Александр
Public bug reported:

1. I try to turn off the computer in the standard way or "shutdown now" 
2. Expect that the PC turns off 
3. In fact, the result is one. The Ubuntu logo appears without moving. ! Before 
the system update from 16.04 this problem was not. Changed the update mirror is 
standard on http://mirror.corbina.net/ubuntu as with the previous mirror the 
distribution upgrade did not happen, the system saw no updates.

---
1. Пытаюсь выключить компьютер стандартным способом или "shutdown now" 
2. Ожидаю что ПК выключится 
3. На деле результат один. Появляется логотип Ubuntu без движения. ! До 
обновления системы с 16.04 этой проблемы небыло. Сменил зеркало обновлений со 
стандартного на http://mirror.corbina.net/ubuntu так как с прежним зеркалом 
обновление дистрибутива не происходило, система не видела обновлений.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: evince 3.28.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic i686
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: i386
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 23 10:08:32 2018
InstallationDate: Installed on 2018-05-06 (230 days ago)
InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 
(20140807)
SourcePackage: evince
UpgradeStatus: Upgraded to bionic on 2018-12-21 (1 days ago)

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


** Tags: apport-bug bionic i386

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

Title:
  Does not turn off the PC

Status in evince package in Ubuntu:
  New

Bug description:
  1. I try to turn off the computer in the standard way or "shutdown now" 
  2. Expect that the PC turns off 
  3. In fact, the result is one. The Ubuntu logo appears without moving. ! 
Before the system update from 16.04 this problem was not. Changed the update 
mirror is standard on http://mirror.corbina.net/ubuntu as with the previous 
mirror the distribution upgrade did not happen, the system saw no updates.

  ---
  1. Пытаюсь выключить компьютер стандартным способом или "shutdown now" 
  2. Ожидаю что ПК выключится 
  3. На деле результат один. Появляется логотип Ubuntu без движения. ! До 
обновления системы с 16.04 этой проблемы небыло. Сменил зеркало обновлений со 
стандартного на http://mirror.corbina.net/ubuntu так как с прежним зеркалом 
обновление дистрибутива не происходило, система не видела обновлений.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic i686
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 23 10:08:32 2018
  InstallationDate: Installed on 2018-05-06 (230 days ago)
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 
(20140807)
  SourcePackage: evince
  UpgradeStatus: Upgraded to bionic on 2018-12-21 (1 days ago)

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

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


[Desktop-packages] [Bug 1794997] Re: virNetlinkEventCallback:700 : nl_recv returned with error: No buffer space available

2018-12-22 Thread Launchpad Bug Tracker
[Expired for libvirt (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  virNetlinkEventCallback:700 : nl_recv returned with error: No buffer
  space available

Status in libnl3 package in Ubuntu:
  Expired
Status in libvirt package in Ubuntu:
  Expired

Bug description:
  We are observing the following error while creating VMs

  Sep 27 14:25:47 xpl-dvt-41 libvirtd[4927]: 2018-09-27
  21:25:47.387+: 4927: error : virNetlinkEventCallback:700 : nl_recv
  returned with error: No buffer space available

  This message is observed with latest Bionic libvirt packages.

  lab@xpl-dvt-35:~$ dpkg -l | grep libvirt
  ii  gir1.2-libvirt-glib-1.0:amd64 1.0.0-1 
amd64GObject introspection files for the libvirt-glib library
  ii  libsys-virt-perl  4.0.0-1 
amd64Perl module providing an extension for the libvirt library
  ii  libvirt-bin   4.0.0-1ubuntu8.5
amd64programs for the libvirt library
  ii  libvirt-clients   4.0.0-1ubuntu8.5
amd64Programs for the libvirt library
  ii  libvirt-daemon4.0.0-1ubuntu8.5
amd64Virtualization daemon
  ii  libvirt-daemon-system 4.0.0-1ubuntu8.5
amd64Libvirt daemon configuration files
  ii  libvirt-glib-1.0-0:amd64  1.0.0-1 
amd64libvirt GLib and GObject mapping library
  ii  libvirt0:amd644.0.0-1ubuntu8.5
amd64library for interfacing with different virtualization systems
  ii  python-libvirt4.0.0-1 
amd64libvirt Python bindings

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

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


[Desktop-packages] [Bug 1650536] Re: wrong behaviour of interface - audio specific

2018-12-22 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  wrong behaviour of interface - audio specific

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  report
  1 no audio on audio jack
  2 in trying to fix after testing sound with the audio test Right and Left i 
changed the stereo to 5-1 surround option available in the test windows
  3 this caused to remove from the audio setting windows all output devices ( 
now is empty) 
  Audio stopped working completely and the volume in the top bar had the x and 
I cannot activate.
  is gray

  4 I just update the system with regular updates and the sound now work
  on the browser but the volume still have an x and is greyed but the
  Audio is  active!! I can hear sound on video on  youtube and and play
  music but I cannot adjust volume.

  5 try to activate pavucontrol but get message " establishing
  connection with pulseaudio please wait " but no responce

  system information:
  Linux jaki-XPS-13-9350 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux
   suppose to be one of the certified laptop

  Regarding the jack still do not work and when inserted the jack the
  audio from internal speaker stop but there is no output. Dell changed
  the motherboard but the problem persisted, tried windows 10 on a live
  usb memory and sound worked out of the jack.

  willing to let someone to log on the system and check remotely

  jaki@jaki-XPS-13-9350:~$ xprop WM_CLASS
  WM_CLASS(STRING) = "unity-control-center", "Unity-control-center"

  unity-control-center:
Installato: 15.04.0+16.04.20160705-0ubuntu1
Candidato:  15.04.0+16.04.20160705-0ubuntu1
Tabella versione:
   *** 15.04.0+16.04.20160705-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   15.04.0+16.04.20160413-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  jaki@jaki-XPS-13-9350:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Dec 16 13:29:44 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  InstallationDate: Installed on 2016-06-25 (174 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  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: Upgraded to xenial on 2016-09-07 (99 days ago)
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.4
  dmi.board.name: 0H67KH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0H67KH:rvrA03:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1794997] Re: virNetlinkEventCallback:700 : nl_recv returned with error: No buffer space available

2018-12-22 Thread Launchpad Bug Tracker
[Expired for libnl3 (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  virNetlinkEventCallback:700 : nl_recv returned with error: No buffer
  space available

Status in libnl3 package in Ubuntu:
  Expired
Status in libvirt package in Ubuntu:
  Expired

Bug description:
  We are observing the following error while creating VMs

  Sep 27 14:25:47 xpl-dvt-41 libvirtd[4927]: 2018-09-27
  21:25:47.387+: 4927: error : virNetlinkEventCallback:700 : nl_recv
  returned with error: No buffer space available

  This message is observed with latest Bionic libvirt packages.

  lab@xpl-dvt-35:~$ dpkg -l | grep libvirt
  ii  gir1.2-libvirt-glib-1.0:amd64 1.0.0-1 
amd64GObject introspection files for the libvirt-glib library
  ii  libsys-virt-perl  4.0.0-1 
amd64Perl module providing an extension for the libvirt library
  ii  libvirt-bin   4.0.0-1ubuntu8.5
amd64programs for the libvirt library
  ii  libvirt-clients   4.0.0-1ubuntu8.5
amd64Programs for the libvirt library
  ii  libvirt-daemon4.0.0-1ubuntu8.5
amd64Virtualization daemon
  ii  libvirt-daemon-system 4.0.0-1ubuntu8.5
amd64Libvirt daemon configuration files
  ii  libvirt-glib-1.0-0:amd64  1.0.0-1 
amd64libvirt GLib and GObject mapping library
  ii  libvirt0:amd644.0.0-1ubuntu8.5
amd64library for interfacing with different virtualization systems
  ii  python-libvirt4.0.0-1 
amd64libvirt Python bindings

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

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


[Desktop-packages] [Bug 1798556] Re: gnome-shell lockup when using MySQL Workbench for Ubuntu 18.04

2018-12-22 Thread Launchpad Bug Tracker
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  gnome-shell lockup when using MySQL Workbench for Ubuntu 18.04

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Ubuntu 18.04
  GNOME Shell 3.28.3
  Intel iGPU HD 620

  Oct 18 05:16:17 user gnome-shell[1634]: g_array_unref: assertion 'array' 
failed
  Oct 18 05:16:17 user gnome-shell[1634]: message repeated 8 times: [ 
g_array_unref: assertion 'array' failed]

  Happens by chance when you right click a table after resuming from
  sleep mode in the table list of MySQL Workbench.

  The desktop freezes to input, mysql-workbench freezes, the rightclick
  menu renders an outline but inner contents are not shown, but a
  terminal for example or video will still play, wont freeze. You just
  wont be able to move or click any windows or switch virtual
  workstations.

  The only remedy is switch to another tty and kill mysql-workbench
  process. Or kill gnome-shell :(.

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

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


[Desktop-packages] [Bug 1799114] Re: "More..." buttons do not work.

2018-12-22 Thread Launchpad Bug Tracker
[Expired for gnome-software (Ubuntu) because there has been no activity
for 60 days.]

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

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

Title:
  "More..." buttons do not work.

Status in gnome-software package in Ubuntu:
  Expired

Bug description:
  Neither of the "More..." buttons work limiting my choices to only 27
  apps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-software 3.30.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Oct 22 00:25:19 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-10-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.30.2-0ubuntu7
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_US
   LANG=en_US.UTF-8
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1799131] Re: takes too much time for apps to load, also many apps freeze all the time

2018-12-22 Thread Launchpad Bug Tracker
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  takes too much time for apps to load, also many apps freeze all the
  time

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  takes too much time for apps to load, also many apps freeze all the
  time

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 11:43:37 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   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-07-26 (87 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  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/1799131/+subscriptions

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


[Desktop-packages] [Bug 1798712] Re: [System76 Oryx Pro] No sound for the first 10 minutes (18.10 Cosmic)

2018-12-22 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  [System76 Oryx Pro] No sound for the first 10 minutes (18.10 Cosmic)

Status in pulseaudio package in Ubuntu:
  Expired
Status in rtkit package in Ubuntu:
  Expired

Bug description:
  Installed: 1:12.2-0ubuntu4

  I'm getting no sound on boot after upgrade.

  I tried killing the currently running pulseaudio daemon, then starting it 
with `-`, here's what happens:
  `~$ pulseaudio -
  I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation 
not permitted
  I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation 
not permitted
  D: [pulseaudio] core-rtclock.c: Timer slack is set to 50 us.`
  Although this appears in the terminal, there's still no sound in the settings 
menu, or in pavucontrol.

  alsamixer runs just fine, showing that alsa is working.

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

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


[Desktop-packages] [Bug 1798712] Re: [System76 Oryx Pro] No sound for the first 10 minutes (18.10 Cosmic)

2018-12-22 Thread Launchpad Bug Tracker
[Expired for rtkit (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [System76 Oryx Pro] No sound for the first 10 minutes (18.10 Cosmic)

Status in pulseaudio package in Ubuntu:
  Expired
Status in rtkit package in Ubuntu:
  Expired

Bug description:
  Installed: 1:12.2-0ubuntu4

  I'm getting no sound on boot after upgrade.

  I tried killing the currently running pulseaudio daemon, then starting it 
with `-`, here's what happens:
  `~$ pulseaudio -
  I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation 
not permitted
  I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation 
not permitted
  D: [pulseaudio] core-rtclock.c: Timer slack is set to 50 us.`
  Although this appears in the terminal, there's still no sound in the settings 
menu, or in pavucontrol.

  alsamixer runs just fine, showing that alsa is working.

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

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


[Desktop-packages] [Bug 1799353] Re: [Realtek ALC892, Green Line Out, Rear] No sound

2018-12-22 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  [Realtek ALC892, Green Line Out, Rear] No sound

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Pulseaudio does not detect the card too. Configuration tab says that
  there are no cards available for configuration. In the settings, the
  only output device listed is Unix FIFO Sink (points to a chrome remote
  desktop extension's file). No other output devices are listed in the
  settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 23 11:37:32 2018
  InstallationDate: Installed on 2017-01-19 (642 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA ATI SB
  Symptom_Jack: Green Line Out, Rear
  Title: [To be filled by O.E.M., Realtek ALC892, Green Line Out, Rear] 
Pulseaudio fails to detect card
  UpgradeStatus: Upgraded to bionic on 2018-09-24 (28 days ago)
  dmi.bios.date: 08/15/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0803
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX 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.:bvr0803:bd08/15/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.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.

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

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


[Desktop-packages] [Bug 1799617] Re: Main user account fails gdm3 - upgrade to Beaver 18.04

2018-12-22 Thread Launchpad Bug Tracker
[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Main user account fails gdm3 - upgrade to Beaver 18.04

Status in gdm3 package in Ubuntu:
  Expired

Bug description:
  Just upgraded 16.04.1 LTS to Bionic Beaver 18.04.1 LTS
  Upgraded from a non-admin user login using 'sudo', now that user fails GDM 
login.
  All other users, some admin - some not, work fine.
  On failing user mouse cursor locks at last position after clicking on 'login'.
  Computer Hard-Locks...

  All other users, pointer jumps to lower right quad of screen and login 
proceeds.
  Same lockup when switching to that failing user via User-Switch menu.

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

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


[Desktop-packages] [Bug 1809564] [NEW] Unfocused tilix window transparency

2018-12-22 Thread Joseph Maillardet
Public bug reported:

With Yaru theme the background transparency of unfocused Tilix Windows
is removed. I mean, when a Tilix terminal is focused, the transparency
settings is correctly applied to the background. But, if the windows
loose the focus, the background became opaque.

With other gtk theme like adwaita or arc ... we don't have this problem.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: yaru-theme-gtk 18.10.6
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Dec 23 01:24:28 2018
EcryptfsInUse: Yes
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: yaru-theme
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2015-11-27T14:42:56.796345

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


** Tags: amd64 apport-bug cosmic

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

Title:
  Unfocused tilix window transparency

Status in yaru-theme package in Ubuntu:
  New

Bug description:
  With Yaru theme the background transparency of unfocused Tilix Windows
  is removed. I mean, when a Tilix terminal is focused, the transparency
  settings is correctly applied to the background. But, if the windows
  loose the focus, the background became opaque.

  With other gtk theme like adwaita or arc ... we don't have this
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: yaru-theme-gtk 18.10.6
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec 23 01:24:28 2018
  EcryptfsInUse: Yes
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: yaru-theme
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2015-11-27T14:42:56.796345

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

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


[Desktop-packages] [Bug 1809558] Re: libreoffice calc cannot parse csv

2018-12-22 Thread peterzay
Input test.csv file is attached.


** Attachment added: "input test.csv file"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1809558/+attachment/5224394/+files/test.csv

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

Title:
  libreoffice calc cannot parse csv

Status in libreoffice package in Ubuntu:
  New

Bug description:
  On Fri, Dec 21 2018 04:30:23 AM, calc properly parsed a csv file on
  this pc.

  It can no longer do this (see screenshot).

  Input test.csv file is attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial4
  ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Dec 22 16:48:38 2018
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2018-11-14 (37 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1809558] [NEW] libreoffice calc cannot parse csv

2018-12-22 Thread peterzay
Public bug reported:

On Fri, Dec 21 2018 04:30:23 AM, calc properly parsed a csv file on this
pc.

It can no longer do this (see screenshot).

Input test.csv file is attached.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial4
ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Dec 22 16:48:38 2018
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationDate: Installed on 2018-11-14 (37 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
ProcEnviron:
 PATH=(custom, 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 xenial

** Attachment added: "screenshot of calc opening csv file"
   
https://bugs.launchpad.net/bugs/1809558/+attachment/5224389/+files/Screenshot%20from%202018-12-22%2016-47-58.png

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

Title:
  libreoffice calc cannot parse csv

Status in libreoffice package in Ubuntu:
  New

Bug description:
  On Fri, Dec 21 2018 04:30:23 AM, calc properly parsed a csv file on
  this pc.

  It can no longer do this (see screenshot).

  Input test.csv file is attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial4
  ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Dec 22 16:48:38 2018
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2018-11-14 (37 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1025388] Re: Internal mic stops working when plugging in headphones

2018-12-22 Thread Roman
Confirming x1 5th gen. Any updates?

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

Title:
  Internal mic stops working when plugging in headphones

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I am currently running Quantal and when I plug headphones into my
  headphone socket (which has an icon of a headset next to it, so I
  presume it can take some kind of headset), the internal mic on my
  laptop stops working. If I unplug the headphones the internal mic
  works as normal.

  I tried this with two different sets of headphones (one of which has a
  mic, and the other I think has a mic too).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: pulseaudio 1:2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
  Uname: Linux 3.5.0-4-generic i686
  ApportVersion: 2.3-0ubuntu4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jono   1860 F pulseaudio
   /dev/snd/pcmC0D0c:   jono   1860 F...m pulseaudio
  Date: Mon Jul 16 11:01:32 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET56WW (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4239CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4239CTO
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO

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

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


[Desktop-packages] [Bug 1809552] Re: Ubuntu sees duplicate display for each graphics card on Macbook Pro

2018-12-22 Thread Anish Moorthy
I should specify, the specific model of Macbook Pro which I am using is
the mid-2012 15" version (version 10,1)

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

Title:
  Ubuntu sees duplicate display for each graphics card on Macbook Pro

Status in xorg package in Ubuntu:
  New

Bug description:
  After booting Ubuntu in BIOS mode on my machine for years, I just
  switched over to EFI boot. The reason for which I switched is that, on
  this machine, Ubuntu cannot detect the integrated GPU under BIOS boot.

  Ubuntu now recognizes both integrated and discrete GPU on my machine,
  but it also seems to think I have two monitors.

  Expected Behavior: Ubuntu properly recognizes that both graphics cards
  are in fact controlling the same display

  Actual Behavior: Ubuntu thinks I have two displays (each being
  controlled by a separate card?). If I navigate to the "Devices >
  Displays" section of the settings app, then Ubuntu lists two "Built in
  Displays," and offers options to "Join Displays," mirror them, etc.

  I have created a question on AskUbuntu
  (https://askubuntu.com/questions/1103696/ubuntu-duplicates-display-
  for-each-graphics-card-fresh-install) detailing this issue; it
  presents much of the same information in this bug report, along with
  several images.

  I have also discovered a similar thread from three years ago
  (https://askubuntu.com/questions/582574/my-macbook-has-two-built-in-
  displays) suggesting that I am not the only Macbook user to suffer
  from this issue. The user in said thread worked around this issue by
  powering off his iGPU. I would like to set up graphics switching in
  the future, so this is not an option for me. In any case, I have
  tested his "solution" and it DOES NOT work on my machine (I also don't
  have a /sys/kernel/debug/vgaswitcheroo folder like he apparently does)

  SYSTEM INFORMATION
  

  OS Version: Ubuntu (64-bit) 18.04.1
  Kernel: 4.15.0-43-generic

  GRAPHICS CARD INFORMATION
  ==
  $ lshw -c video
  *-display 
 description: VGA compatible controller
 product: GK107M [GeForce GT 650M Mac Edition]
 vendor: NVIDIA Corporation
 physical id: 0
 bus info: pci@:01:00.0
 version: a1
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
 configuration: driver=nouveau latency=0
 resources: irq:45 memory:c000-c0ff memory:9000-9fff 
memory:a000-a1ff ioport:2000(size=128) memory:c100-c107

  *-display
 description: VGA compatible controller
 product: 3rd Gen Core processor Graphics Controller
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list
 configuration: driver=i915 latency=0
 resources: irq:47 memory:c140-c17f memory:b000-bfff 
ioport:3000(size=64)

  MORE GRAPHICS CARD INFORMATION
  ==
  $ lspci | grep VGA
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 650M 
Mac Edition] (rev a1)

  
  DISPLAY CONFIGURATION INFO (1)
  ==
  NOTE: In this diagnostic, I have chosen the "Single Display" option via the 
System Settings app. Only one of the two "built-in displays" is actually 
usable, selecting the other just gives me a black screen until my changes are 
auto-reverted

  $ xrandr - q
  Screen 0: minimum 320 x 200, current 1440 x 900, maximum 16384 x 16384
  LVDS-1 connected primary 1440x900+0+0 (normal left inverted right x axis y 
axis) 331mm x 207mm
1440x900  59.90*+
1152x864  59.97  
1024x768  59.95  
800x600   59.96  
640x480   59.94  
720x400   59.97  
640x400   59.96  
640x350   59.84  
  DP-1 disconnected (normal left inverted right x axis y axis)
  DP-2 disconnected (normal left inverted right x axis y axis)
  DP-3 disconnected (normal left inverted right x axis y axis)
  LVDS-1-2 connected (normal left inverted right x axis y axis)
1440x900  59.90 +  59.89  
1400x900  59.9659.88  
1440x810  60.0059.97  
1368x768  59.8859.85  
1360x768  59.8059.96  
1280x800  59.9959.9759.8159.91  
1152x864  60.00  
1280x720  60.0059.9959.8659.74  
1024x768  60.0460.00  
960x720   60.00  
928x696   60.05  
896x672   60.01  
1024x576  59.9559.9659.9059.82  
960x600   59.9360.00  
960x540   59.9659.9959.6359.82  
800x600   60.0060.32

[Desktop-packages] [Bug 1809552] [NEW] Ubuntu sees duplicate display for each graphics card on Macbook Pro

2018-12-22 Thread Anish Moorthy
Public bug reported:

After booting Ubuntu in BIOS mode on my machine for years, I just
switched over to EFI boot. The reason for which I switched is that, on
this machine, Ubuntu cannot detect the integrated GPU under BIOS boot.

Ubuntu now recognizes both integrated and discrete GPU on my machine,
but it also seems to think I have two monitors.

Expected Behavior: Ubuntu properly recognizes that both graphics cards
are in fact controlling the same display

Actual Behavior: Ubuntu thinks I have two displays (each being
controlled by a separate card?). If I navigate to the "Devices >
Displays" section of the settings app, then Ubuntu lists two "Built in
Displays," and offers options to "Join Displays," mirror them, etc.

I have created a question on AskUbuntu
(https://askubuntu.com/questions/1103696/ubuntu-duplicates-display-for-
each-graphics-card-fresh-install) detailing this issue; it presents much
of the same information in this bug report, along with several images.

I have also discovered a similar thread from three years ago
(https://askubuntu.com/questions/582574/my-macbook-has-two-built-in-
displays) suggesting that I am not the only Macbook user to suffer from
this issue. The user in said thread worked around this issue by powering
off his iGPU. I would like to set up graphics switching in the future,
so this is not an option for me. In any case, I have tested his
"solution" and it DOES NOT work on my machine (I also don't have a
/sys/kernel/debug/vgaswitcheroo folder like he apparently does)

SYSTEM INFORMATION


OS Version: Ubuntu (64-bit) 18.04.1
Kernel: 4.15.0-43-generic

GRAPHICS CARD INFORMATION
==
$ lshw -c video
*-display 
   description: VGA compatible controller
   product: GK107M [GeForce GT 650M Mac Edition]
   vendor: NVIDIA Corporation
   physical id: 0
   bus info: pci@:01:00.0
   version: a1
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
   configuration: driver=nouveau latency=0
   resources: irq:45 memory:c000-c0ff memory:9000-9fff 
memory:a000-a1ff ioport:2000(size=128) memory:c100-c107

*-display
   description: VGA compatible controller
   product: 3rd Gen Core processor Graphics Controller
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 09
   width: 64 bits
   clock: 33MHz
   capabilities: msi pm vga_controller bus_master cap_list
   configuration: driver=i915 latency=0
   resources: irq:47 memory:c140-c17f memory:b000-bfff 
ioport:3000(size=64)

MORE GRAPHICS CARD INFORMATION
==
$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 650M 
Mac Edition] (rev a1)


DISPLAY CONFIGURATION INFO (1)
==
NOTE: In this diagnostic, I have chosen the "Single Display" option via the 
System Settings app. Only one of the two "built-in displays" is actually 
usable, selecting the other just gives me a black screen until my changes are 
auto-reverted

$ xrandr - q
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 16384 x 16384
LVDS-1 connected primary 1440x900+0+0 (normal left inverted right x axis y 
axis) 331mm x 207mm
  1440x900  59.90*+
  1152x864  59.97  
  1024x768  59.95  
  800x600   59.96  
  640x480   59.94  
  720x400   59.97  
  640x400   59.96  
  640x350   59.84  
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
LVDS-1-2 connected (normal left inverted right x axis y axis)
  1440x900  59.90 +  59.89  
  1400x900  59.9659.88  
  1440x810  60.0059.97  
  1368x768  59.8859.85  
  1360x768  59.8059.96  
  1280x800  59.9959.9759.8159.91  
  1152x864  60.00  
  1280x720  60.0059.9959.8659.74  
  1024x768  60.0460.00  
  960x720   60.00  
  928x696   60.05  
  896x672   60.01  
  1024x576  59.9559.9659.9059.82  
  960x600   59.9360.00  
  960x540   59.9659.9959.6359.82  
  800x600   60.0060.3256.25  
  840x525   60.0159.88  
  864x486   59.9259.57  
  800x512   60.17  
  700x525   59.98  
  800x450   59.9559.82  
  640x512   60.02  
  720x450   59.89  
  700x450   59.9659.88  
  640x480   60.0059.94  
  720x405   59.5158.99  
  684x384   59.8859.85  
  680x384   59.8059.96  
  640x400   59.8859.98  
  576x432   60.06  
  640x360   59.8659.8359.8459.32  
  512x384   60.00  
  512x288   60.0059.92  
  480x270   59.6359.82  
  400x300   

[Desktop-packages] [Bug 1807983] Re: Update gnome-desktop3 to 3.30.2

2018-12-22 Thread Jeremy Bicha
I installed gnome-desktop3 3.30.2-0ubuntu1 on Ubuntu 18.10 and verified
that the GNOME version in the Settings app is now 3.30.2.

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

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

Title:
  Update gnome-desktop3 to 3.30.2

Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in gnome-desktop3 source package in Cosmic:
  Fix Committed

Bug description:
  Impact
  ==
  This updates the GNOME version number reported in Settings > Details > About 
to 3.30.2

  This is the final scheduled point release for GNOME 3.30.

  I'm also cherry-picking a potential crash bug fix from the gnome-3-30
  branch since there might not be another 3.30 release tarball.

  This also includes the fix for LP: #1807127

  Test Case
  =
  From Ubuntu 18.10, open the Settings app.
  Navigate to Details > About
  The GNOME version number should say 3.30.2

  Regression Potential
  
  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

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

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


[Desktop-packages] [Bug 1808075] Re: Backport Unicode/Emoji 11 updates

2018-12-22 Thread Jeremy Bicha
I installed pango1.0 1.42.4-3ubuntu1 on Ubuntu 18.10 and verified that
the red-haired man now displays correctly in gedit.

I also opened the GNOME Characters app (.deb and snap versions) and
verified that emoji there still displayed ok.

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

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

Title:
  Backport Unicode/Emoji 11 updates

Status in pango1.0 package in Ubuntu:
  Fix Released
Status in pango1.0 source package in Cosmic:
  Fix Committed

Bug description:
  Impact
  ==
  Once a year, there is a new Unicode and Emoji release. 2018's release is 
Unicode 11.

  Ubuntu 18.04 LTS and 18.10 already include Google's color emoji font
  for Unicode 11 (LP: #1788256) but neither Ubuntu 18.10 nor 18.04 LTS
  are able to display the new combinations introduced in Unicode 11 such
  as red-haired people.

  Test Case
  =
  Copy and paste the red-hair man ‍聆 into gedit. It should show as a single 
character.

  Regression Potential
  
  Although the code was written several weeks ago, it was only released in 
pango 1.43 (a development release) today so it's not seen many users yet.

  On the other hand, pango does have a test suite run during the build
  and as autopkgtest and those tests still pass. I haven't seen any
  issues yet and we'll work to fix any issues that do develop.

  A significant portion of the change set comes from the Unicode data
  sets and from the Chromium Unicode/Emoji parser. Both of those parts
  have received wider testing and use over several months.

  Other Info
  ==
  This issue is easy to fix with Ubuntu 18.10 but it may not be practical to 
try to update Ubuntu 18.04 LTS for this feature.

  GTK's "Insert Emoji" feature will need to be updated to offer these
  new emoji.

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

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


[Desktop-packages] [Bug 1798400]

2018-12-22 Thread Sergio Callegari
Still present in 6.2.0 RC 1

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

Title:
  Regression: cannot use impress remote over bluetooth with ubuntu
  bionic

Status in LibreOffice:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in libreoffice package in Fedora:
  Unknown

Bug description:
  Trying to use the impress remote
  (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth
  with libreoffice over ubuntu bionic fails.

  The handset errors out that it cannot connect with Libreoffice on the
  computer even if the bluetooth adapter on the handset and on the
  computer are correctly paired.

  This does not seem to be an issue in the Libreoffice or in the impress
  remote code:

  - I have tested also past LibO versions
  - The Impress remote codebase has not changed recently

  This used to work on the same hardware (headset and laptop) with
  ubuntu 16.04.

  Hence the issue seems to be in a regression in the ubuntu bluetooth
  stack.

  To replicate:

  1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo
  or with the deb packages from the document fundation)

  2) Assure that your computer has bluetooth

  3) Install impress remote on an android handset (either from the play
  store of via fdroid)

  4) Assure that "remote control" is enabled in impress
  Tools>Options>Impress>General

  5) Pair the bluetooth adapters in the laptop and in the computer

  6) Open a presentation on the laptop

  7) Open the remote on the handset, got to the bluetooth pane see the
  computer there, touch it

  8) See the impress remote erroring out

  Most likely you will also get a bluetooth error on dmesg

  RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind:
  Address already in use (98)

  Same issue was reported for fedora

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct 17 16:57:29 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1769 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Notebook W740SU
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W740SU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:C2:C6:1A:28:71  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN 
RX bytes:245088 acl:15156 sco:0 events:1266 errors:0
TX bytes:15571 acl:402 sco:1 commands:131 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions

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


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

2018-12-22 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: trying
  to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in
  package nvidia-kernel-common-390 390.87-0ubuntu1

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

Bug description:
  Ubuntu 18.10

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Sat Dec 22 15:34:24 2018
  DuplicateSignature:
   package:nvidia-340:(not installed)
   Unpacking nvidia-340 (340.107-0ubuntu2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/nvidia-340_340.107-0ubuntu2_amd64.deb (--unpack):
trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in 
package nvidia-kernel-common-390 390.87-0ubuntu1
  ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which 
is also in package nvidia-kernel-common-390 390.87-0ubuntu1
  InstallationDate: Installed on 2018-10-06 (77 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.0
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package 
nvidia-kernel-common-390 390.87-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2018-12-22 Thread dezi
Public bug reported:

Ubuntu 18.10

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: nvidia-340 (not installed)
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Sat Dec 22 15:34:24 2018
DuplicateSignature:
 package:nvidia-340:(not installed)
 Unpacking nvidia-340 (340.107-0ubuntu2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/nvidia-340_340.107-0ubuntu2_amd64.deb (--unpack):
  trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in 
package nvidia-kernel-common-390 390.87-0ubuntu1
ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is 
also in package nvidia-kernel-common-390 390.87-0ubuntu1
InstallationDate: Installed on 2018-10-06 (77 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt  1.7.0
SourcePackage: nvidia-graphics-drivers-340
Title: package nvidia-340 (not installed) failed to install/upgrade: trying to 
overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package 
nvidia-kernel-common-390 390.87-0ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package cosmic package-conflict

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: trying
  to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in
  package nvidia-kernel-common-390 390.87-0ubuntu1

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

Bug description:
  Ubuntu 18.10

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Sat Dec 22 15:34:24 2018
  DuplicateSignature:
   package:nvidia-340:(not installed)
   Unpacking nvidia-340 (340.107-0ubuntu2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/nvidia-340_340.107-0ubuntu2_amd64.deb (--unpack):
trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in 
package nvidia-kernel-common-390 390.87-0ubuntu1
  ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which 
is also in package nvidia-kernel-common-390 390.87-0ubuntu1
  InstallationDate: Installed on 2018-10-06 (77 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.0
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package 
nvidia-kernel-common-390 390.87-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1783202] Re: Build Firefox with gpsd location provider support (--enable-gpsd)

2018-12-22 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Build Firefox with gpsd location provider support (--enable-gpsd)

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Firefox 50+ has support for gpsd, see 
https://bugzilla.mozilla.org/show_bug.cgi?id=1250922
  That would allow users with a GPS device to use the provided GPS data for the 
Geolocation API within the browser - not by default (in stable release builds), 
but only after explicitly setting 'geo.location.use_gpsd' to 'true' in 
about:config. Which is a good thing, as no defaults change.

  However that support has to be enabled with the build flag --enable-gpsd.
  As you can see in toolkit/moz.configure the only thing that is needed to 
build Firefox with gpsd support is libgps-dev installed on the build system:
  
https://hg.mozilla.org/mozilla-central/file/ccfd7b716a91/toolkit/moz.configure#l550

  If you want to dig deeper here are the three changes that brought gpsd 
support:
  https://hg.mozilla.org/mozilla-central/rev/76b04196acce
  https://hg.mozilla.org/mozilla-central/rev/a1a42e8d66e9
  https://hg.mozilla.org/mozilla-central/rev/457be633b6cc

  There is not much magic here: When users switch on the flag
  'geo.location.use_gpsd', Firefox tries to get the position from gpsd,
  if no location information is received from GPS within a few seconds,
  as fallback Mozilla Location Service provides a position instead. The
  position however will be updated once GPS is ready. If GPS fails, MLS
  will take over again until GPS has been restored.

  The only thing you might want to be aware of is that on non-release
  builds, the gpsd location provider is enabled by default, meaning
  'geo.location.use_gpsd' is 'true' (see revision a1a42e8d66e9) because
  Firefox devs want to give it some testing. However that shouldn't be
  an issue, because as described, MLS acts as fallback after a few
  seconds anyway.

  What do you think?

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

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


[Desktop-packages] [Bug 1809542] [NEW] Search result are often blank.

2018-12-22 Thread 賴家亨
Public bug reported:

The Search results are not shown, unless I move my cursor on the button of 
Ubuntu Software.
I have uploaded an attachment which includes the screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubuntu-software 3.30.2-0ubuntu8
Uname: Linux 4.19.11-041911-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec 22 21:46:56 2018
InstallationDate: Installed on 2018-12-10 (12 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
InstalledPlugins:
 gnome-software-plugin-flatpak 3.30.2-0ubuntu8
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.30.2-0ubuntu8
PackageArchitecture: all
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "The screenshot."
   
https://bugs.launchpad.net/bugs/1809542/+attachment/5224312/+files/2018-12-22%2021-46-28%20%E7%9A%84%E8%9E%A2%E5%B9%95%E6%93%B7%E5%9C%96.png

** Description changed:

- The Search results are not shown, unless I move my cursor on the button
- of Ubuntu Software.
+ The Search results are not shown, unless I move my cursor on the button of 
Ubuntu Software.
+ I have uploaded an attachment which includes the screenshot.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubuntu-software 3.30.2-0ubuntu8
  Uname: Linux 4.19.11-041911-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 22 21:46:56 2018
  InstallationDate: Installed on 2018-12-10 (12 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  InstalledPlugins:
-  gnome-software-plugin-flatpak 3.30.2-0ubuntu8
-  gnome-software-plugin-limba   N/A
-  gnome-software-plugin-snap3.30.2-0ubuntu8
+  gnome-software-plugin-flatpak 3.30.2-0ubuntu8
+  gnome-software-plugin-limba   N/A
+  gnome-software-plugin-snap3.30.2-0ubuntu8
  PackageArchitecture: all
  SourcePackage: gnome-software
  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-software in Ubuntu.
https://bugs.launchpad.net/bugs/1809542

Title:
  Search result are often blank.

Status in gnome-software package in Ubuntu:
  New

Bug description:
  The Search results are not shown, unless I move my cursor on the button of 
Ubuntu Software.
  I have uploaded an attachment which includes the screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubuntu-software 3.30.2-0ubuntu8
  Uname: Linux 4.19.11-041911-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 22 21:46:56 2018
  InstallationDate: Installed on 2018-12-10 (12 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.30.2-0ubuntu8
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.30.2-0ubuntu8
  PackageArchitecture: all
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1804685] Re: Icon View Captions display in the wrong positions

2018-12-22 Thread Amr Ibrahim
Steps to verify in Bionic:
1. sudo apt install nautilus/bionic-proposed nautilus-data/bionic-proposed
2. In a terminal: nautilus -q
3. Check the order of icon view captions are correct now
I verify the bug is fixed in Bionic.

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

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

Title:
  Icon View Captions display in the wrong positions

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Bionic:
  Fix Committed
Status in nautilus source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  The nautilus view doesn't display the informations with the selected layout

  * Test case
  1. Change to 100% zoom
  2. Go to Preferences > Icon View Captions
  3. There are three captions: First, Second & Third

  When selecting details for those they should reflect in the right
  order

  * Regression potential
  The code change is only the order of the widget in the preference, check that 
the preferency/views tab is not buggy

  ---

  
  In the Preferences for Nautilus, under the Views tab, the user has the option 
to select information to appear in the "First", "Second", and "Third" position 
beneath icons.  However, in icon view,  whatever the user selects to appear in 
the "First" position will appear in the second location beneath the icon.  
Whatever the user selects to appear in the "Second" position will appear in the 
third, or bottom, position.  Whatever the user selects to appear in the "Third" 
position will appear in the first, or top, position.

  I'm on

  Ubuntu 18.04.1 LTS
  Nautilus 3.26.4-0~ubuntu18.04.2

  Thanks!

  Upstream bugs:
  https://gitlab.gnome.org/GNOME/nautilus/issues/343
  https://gitlab.gnome.org/GNOME/nautilus/issues/766

  Upstream Fix:
  
https://gitlab.gnome.org/GNOME/nautilus/commit/86080e646a81679761e09aee4071abf68a2dac3b

  Steps to reproduce:
  1. Change to 100% zoom
  2. Go to Preferences > Icon View Captions
  3. There are three captions: First, Second & Third
  I expect to see that the 1st caption is displayed just below the file/folder 
name, 2nd is below 1st and 3rd is below 2nd.

  Current behaviour:
  The order of the captions is mixed up.
  The current order is this:
  - File/Folder Name
  - Third caption
  - First caption
  - Second caption

  Expected behaviour:
  - File/Folder Name
  - First caption
  - Second caption
  - Third caption

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

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


[Desktop-packages] [Bug 972826] Re: nautilus crashed with SIGSEGV in find_subtree_recurse()

2018-12-22 Thread ghislaingeffroy
Hi Paul,

I no longer have this phone and I use Ubuntu 18.10 now.

With news versions of Ubuntu I no longer have this issue.
I think this ticket can be closed.

Thanks and good luck cleaning-up this huge pile of tickets.

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

Title:
  nautilus crashed with SIGSEGV in find_subtree_recurse()

Status in nautilus package in Ubuntu:
  Incomplete
Status in nautilus package in Fedora:
  Won't Fix

Bug description:
  Nautilus crash (no more desktop icons or nautilus window) after
  connecting my Android Phone (Sony Xperia S), not always reproduced

  * Ubuntu 12.04
  * Nautilus 1:3.4.0-0ubuntu1

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
  Uname: Linux 3.2.0-21-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Tue Apr  3 22:30:08 2012
  ExecutablePath: /usr/bin/nautilus
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110904)
  ProcCmdline: nautilus -n
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  Title: nautilus crashed with SIGSEGV in 
dbus_connection_unregister_object_path()
  UpgradeStatus: Upgraded to precise on 2012-02-03 (59 days ago)
  UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare

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

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


[Desktop-packages] [Bug 1809536] [NEW] Empty desktop background after screen unlock - only dock with app icons and top panel, cannot see any app

2018-12-22 Thread Alek Kowalczyk
Public bug reported:

Steps to reproduce (intermittently, ~1 per 10 times):

1. Leave the computer until the screen is blank - two monitors, no multimonitor 
plugin
2. Move the mouse to unblank the screen
3. Drag lock screen to top + enter password

Actual results
- Ubuntu dock is visible (with app icons)
- Top panel is visible, but with limited options (e.g. no "Sleep" button, no 
app indicators)
- Empty desktop background
- Clicking the app icon does nothing - there is some animation effect, but it 
looks like the application would be 'behind' the background
- Clicking "Applications" menu animates but then disappear as well

Partial workaround:
1. Ctrl-Alt-F1
2. Choose the same user and enter password
3. You'll come back to the "empty desktop". But in a few seconds applications 
appear with a few limitations:
a) Top panel features are still limited (no sleep/power off buttons in menu, no 
app indicators)
b) Ubuntu dock shows different set of apps on each 1st and 2nd monitor


Might be related to one of the stack traces in journalctl -first is probably 
when the screen was locked, second when unclodked

gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: == Stack trace for 
context 0x55b45f34c210 ==
gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #0   7ffd0163ba40 
b   resource:///org/gnome/gjs/modules/overrides/GObject.js:468 (7f054eccc040 @ 
25)
gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #1   7ffd0163bae0 
b   /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:416 
(7f051f315790 @ 20)
gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #2   7ffd0163bbd0 
b   self-hosted:261 (7f054ecc1dc0 @ 223)
gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #3   7ffd0163bc90 
b   /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:415 
(7f051f315700 @ 172)
gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #4   7ffd0163c910 
b   resource:///org/gnome/gjs/modules/_legacy.js:82 (7f054ecb0b80 @ 71)
gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #5   55b46572a1c0 
i   /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:424 
(7f051f315820 @ 17)
gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #6   7ffd0163d880 
b   resource:///org/gnome/gjs/modules/_legacy.js:82 (7f054ecb0b80 @ 71)
gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #7   55b46572a140 
i   /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:89 
(7f051f310ee0 @ 42)
gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #8   7ffd0163e7f0 
b   resource:///org/gnome/gjs/modules/_legacy.js:82 (7f054ecb0b80 @ 71)
gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #9   55b46572a0b8 
i   /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:456 
(7f05237fbd30 @ 82)
gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #10   7ffd0163f760 
b   resource:///org/gnome/gjs/modules/_legacy.js:82 (7f054ecb0b80 @ 71)
gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #11   55b46572a020 
i   /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1784 
(7f051f30c160 @ 116)
gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #12   7ffd016406d0 
b   resource:///org/gnome/gjs/modules/_legacy.js:82 (7f054ecb0b80 @ 71)
gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #13   55b4647f2360 
i   /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1903 
(7f051f30c550 @ 37)
gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #14   7ffd01641640 
b   resource:///org/gnome/gjs/modules/_legacy.js:82 (7f054ecb0b80 @ 71)
gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #15   55b4647f22e0 
i   /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/extension.js:31 
(7f05237fb4c0 @ 12)
gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #16   55b4647f2220 
i   resource:///org/gnome/shell/ui/extensionSystem.js:83 (7f054e85a040 @ 436)
gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #17   55b4647f21a0 
i   resource:///org/gnome/shell/ui/extensionSystem.js:354 (7f054e85ab80 @ 13)
gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #18   7ffd016427b0 
b   self-hosted:261 (7f054ecc1dc0 @ 223)
gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #19   55b4647f2120 
i   resource:///org/gnome/shell/ui/extensionSystem.js:353 (7f054e85aaf0 @ 64)
gru 22 10:23:59 alex-notebook gnome-shell[4475]: 
../../../../gobject/gsignal.c:2641: instance '0x55b465d2fb20' has no handler 
with id '2417542'
gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #20   55b4647f20a0 
i   resource:///org/gnome/shell/ui/extensionSystem.js:371 (7f054e85ac10 @ 87)
gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #21   7ffd016438f0 
b   resource:///org/gnome/gjs/modules/signals.js:128 (7f054ecc18b0 @ 386)
gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #22   7ffd01644510 
b   

[Desktop-packages] [Bug 1789022] Re: libcaca0 still depends on old libncursesw5 and libtinfo5

2018-12-22 Thread Harry
This forgotten issue still exists, also in Disco.

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

Title:
  libcaca0 still depends on old libncursesw5 and libtinfo5

Status in libcaca package in Ubuntu:
  New

Bug description:
  Ubuntu Cosmic switched some time ago from ncurses5 to ncurses6.
  However, the package libcaca0 still depends on old libncursesw5 and libtinfo5 
instead of libncursesw6 and libtinfo6.

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

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


[Desktop-packages] [Bug 1732450] Re: Lock screen doesn't respect gnome shell theme choice

2018-12-22 Thread Amit Keret
I can confirm the same behaviour persists on Ubuntu 18.10:

$ gsettings get org.gnome.desktop.interface gtk-theme
'Adapta'

$ sudo -u gdm env XDG_CURRENT_DESKTOP=GNOME-Greeter HOME=/var/lib/gdm3 
gsettings get org.gnome.desktop.interface gtk-theme
'Yaru'

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

Title:
  Lock screen doesn't respect gnome shell theme choice

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  The lockscreen theme doesn't follow the selected gnome shell theme, as
  it used to do, but instead it always uses gnome-shell.css if logged in
  as Gnome session or ubuntu.css if logged as Ubuntu session.

  The currently selected gdm theme is ubuntu.css, but after login it's
  not respected either.

  ```
  There are 3 choices for the alternative gdm3.css (providing 
/usr/share/gnome-shell/theme/gdm3.css).

    SelectionPath  Priority   Status
  
    0/usr/share/gnome-shell/theme/pop.css   20auto 
mode
    1/usr/share/gnome-shell/theme/gnome-shell.css   5 
manual mode
    2/usr/share/gnome-shell/theme/pop.css   20
manual mode
  * 3/usr/share/gnome-shell/theme/ubuntu.css10
manual mode
  ```

  The selected shell theme is Arc-Darker, from the Ubuntu repositories.

  This happens both in the Wayland and Xorg sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Nov 15 15:31:14 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-21 (85 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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