date:20180513

[Desktop-packages] [Bug 1770509] Re: gui crashes on login

2018-05-13 Thread Kai-Heng Feng

** Also 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/1770509

Title:
  gui crashes on login

Status in gdm3 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in gdm3 source package in Bionic:
  New
Status in linux source package in Bionic:
  Confirmed

Bug description:
  I have installed Ubuntu 18.04 LTS on my laptop which is a Lenovo Ideapad 300 
with 8GB of RAM, an Intel® Core™ i7-6500U CPU @ 2.50GHz × 4 processor and 
Intel® HD Graphics 520 (Skylake GT2). I have GNOME 3.28.1  which logically is 
latest version of GNOME coming with Ubuntu 18.04 LTS. Everything works 
perfectly but I found a bug which happens when logging in. When I boot my 
laptop (which is not dual boot, it only has Ubuntu 18.04 LTS installed), I 
press Enter to select the only available user (my user) and then I am prompted 
to enter my password. If I type my password wrong by a character more
  (I haven't tried a smaller or a bigger length) and then give the right 
password the GUI crashes. What I mean by crashing is that I get a static purple 
screen where I can only move my mouse pointer and nothing else. I get no 
desktop, no icons, no nothing. I don't know if it is a hardware incompatibility 
or a bug but it happens every time I follow the steps I mentioned above and 
then I have to hard shutdown the laptop.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  george 1599 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=10e7b298-4d9e-47e3-a810-d58d8cf6c6ca
  InstallationDate: Installed on 2018-04-28 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 174f:14e9 Syntek 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80Q7
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=38e55cbd-3efc-41fb-a339-2c5795929cf1 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/03/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: D5CN31WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Paris 5A8
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 300-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrD5CN31WW:bd12/03/2015:svnLENOVO:pn80Q7:pvrLenovoideapad300-15ISK:rvnLENOVO:rnParis5A8:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad300-15ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80Q7
  dmi.product.version: Lenovo ideapad 300-15ISK
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)

2018-05-13 Thread Chris Billington

Lubomir, what changes were required on top of the arch patch to work
with 3.26.3? I'm using the Arch patch as-is on Ubuntu 18.04 and there
don't appear to be any problems that I've noticed so far. But assuming
your changes are necessary, could you publish them somewhere? It would
be great to maybe have a public git repo that people could contribute to
to maintain patches for the latest few versions of Nautilus that are in
common use.

Ubuntu devs - now that there is a working patch again (and seemingly the
will to maintain it by the arch community and others), might Ubuntu be
able to ship a patched nautilus once more restoring this behaviour?

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

Title:
Restore interactive_search.patch (type-ahead search)

Status in nautilus package in Ubuntu:
Won't Fix

Bug description:
Nautilus dropped the popular type-ahead search feature years ago.
Ubuntu has been carrying a patch to revert that change. See bug
1164016 for the original LP bug and patch proposal.

Nautilus is now under very active development. During the 3.22 cycle,
that patch needed to be rebased. I tried to do it and what I came up
with caused a crash (it didn't really crash for me, but ricotz and
some others experienced it) and the first letter typed activated type-
ahead search but the first letter was dropped. In other words, you
would need to type "ddow" to activate the Downloads folder instead of
just "dow" like in previous releases. (LP: #1635988)

I did that rebase in October 2016 and no one has stepped up then to
improve the patch.

The Nautilus maintainer csoriano has said that the slots and views
changed significantly during 3.22 and will likely be refactored more
in the future.

If there's no one available to maintain the patch, unfortunately,
we'll eventually have to drop the patch to not be stuck on an ancient
version of Nautilus.

I am proposing that we do this at the start of the 17.10 development
cycle. This gives 6 months for a developer to step up and try to fix
the patch and 12 months before 18.04 LTS.

Other Items
===
- For better performance with the built-in search, we need to reconsider
avoiding tracker in Unity (LP: #176)

- There is an option in Preferences for users to disable searching in
subfolders. I don't think we want to do that by default but maybe it
can help some people.

The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with
this patch now disabled.

https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty

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

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

[Desktop-packages] [Bug 1755900] Re: sql cookie errors from gnome-shell, or its users

2018-05-13 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/1755900

Title:
  sql cookie errors from gnome-shell, or its users

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  it seems like gnome-shell; or something that calls into gnome-shell;
  have trouble with sqlite:

  journalctl -b -e | grep -e gnome-shell -e org.gnome.Shell.desktop |
  grep sqlite

  has a lot of:

  org.gnome.Shell.desktop[24475]:
  [16281:32625:0314/201004.637228:ERROR:connection.cc(1945)] Cookie
  sqlite error 1, errno 0: cannot start a transaction within a
  transaction, sql: BEGIN TRANSACTION

  
  and similar. My current boot has 66 of them, with only 10h of uptime.

  I do suspend and resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 14 20:11:22 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['r']"
   b'org.gnome.shell' b'favorite-apps' b"['hexchat.desktop', 
'chrome-bebigdkelppomhhjaaianniiifjbgocn-Default.desktop', 
'chrome-clhhggbfdinjmjhajaheehoeibfljjno-Default.desktop', 
'google-chrome.desktop', 'firefox.desktop', 'yubioath.desktop', 
'org.gnome.Terminal.desktop', 'org.gnome.Nautilus.desktop', 
'virt-manager.desktop', 'pgadmin3.desktop', 'android-studio.desktop', 
'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2012-01-12 (2253 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318)
  ProcEnviron:
   LANG=en_US.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-01-11 (62 days ago)

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

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

[Desktop-packages] [Bug 1755202] Re: Clone Mac Address Function On Default Wifi Setting Does Not Work (Ubuntu 17.10)

2018-05-13 Thread Launchpad Bug Tracker

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

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Clone Mac Address Function On Default Wifi Setting Does Not Work
  (Ubuntu 17.10)

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  I am Just Using Ubuntu 17.10.

  My Uname -a Result -> Linux user 4.13.0-36-generic #40-Ubuntu SMP Fri
  Feb 16 20:07:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux.

  Before Using Ubuntu 17.10, I was on fedora 26. I notice that there is
  also (MAC Address Randomization issue). I can fixed it and can use
  default mac address spoofing function from wifi setting -> Network
  Profile Setting (*) -> Identity -> Cloned Address -> And Add mac
  address to spoof for particular network.

  This Default mac address spoof function is very useful for me.

  Clearly, I doesn't mean (MAC Address Randomization issue)
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513

  Now I have a trouble with this feature (default mac spoffing). I can
  connect Wifi-s with great signal easily without using cloned address
  function.

  But when I added spoof address to setting, the wifi-s cannot be
  connected. I tried two wifi-s from near me which can connect on fedora
  26. One is open type network and the other is WPA Enterprise network.

  If this function doesn't work for anyone, this must be a bug.
  If it is a bug, hope it will fix it next release.

  Please, Don't Hesitate to ask more information. I really want to help
  to fix bug.

  Hardware Info
  Lenovo Z470 - Core i5 Second Gen
  I used external wifi adapter - Card King http://a.co/gMrHzZQ  (RT3072 Chipset)

  
  #info
  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  network-manager:
    Installed: 1.8.4-1ubuntu3
    Candidate: 1.8.4-1ubuntu3
    Version table:
   *** 1.8.4-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  Update Journalctl with network-manager log
  First I Connect my wifi named "blizzart" without using spoof address. 
Connected and works fine.
  After 2 minutes later, I disconnected.
  And then add spoof address and try to connect again.
  But It is still trying to connect. You can see in the log.
  https://pastebin.com/vmFMefih

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

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

[Desktop-packages] [Bug 1715255] Re: libreoffice has uninstalled, will not launch or open documents.

2018-05-13 Thread Launchpad Bug Tracker

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

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

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

Title:
  libreoffice has uninstalled, will not launch or open documents.

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  I am using Ubuntu 17.04 and libreoffice has uninstalled making it so I
  cannot make written documents.  I am recently having trouble with
  loading new software in ubuntu 17.04 through the command line and
  through the ubuntu app store.

  ProblemType: Bug
  DistroRelease: Kali 2017.1
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue Sep  5 18:46:58 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-03-23 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  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/1715255/+subscriptions

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

[Desktop-packages] [Bug 1738971] Re: libreoffice application error

2018-05-13 Thread Launchpad Bug Tracker

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

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

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

Title:
  libreoffice application error

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  >libreoffice 
  /usr/lib/libreoffice/program/javaldx: error while loading shared libraries: 
  libreglo.so: cannot open shared object file: No such file or directory
  Warning: failed to read path from javaldx
  /usr/lib/libreoffice/program/soffice.bin: error while loading shared 
libraries: libreglo.so: cannot open shared object file: No such file or 
directory

  >locate libreglo.so
  /usr/lib/libreoffice/program/libreglo.so

  >cd /usr/lib/libreoffice/program/

  >libreoffice 
  Application Error

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice 1:5.4.2-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Dec 19 11:22:37 2017
  InstallationDate: Installed on 2009-11-30 (2940 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-08-31 (109 days ago)

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

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

[Desktop-packages] [Bug 1589215] Re: 'Unknown Application Name' menu item in Indicator Applet Appmenu when LibreOffice is running

2018-05-13 Thread G C

There is a trick suggested by mc4man to workaround this:

https://ubuntuforums.org/showthread.php?t=2391734

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

Title:
  'Unknown Application Name' menu item in Indicator Applet Appmenu when
  LibreOffice is running

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Sometimes I get the issue of a menu having the name of a different
  application and being unusable, or being an application menu for the
  focused window but being titled 'Unknown Application Name', with
  LibreOffice. I also get this with GNOME apps but was told that this is
  a separate issue to the one I reported here:
  https://bugs.launchpad.net/ubuntu/+source/gnome-
  calculator/+bug/1584720 (see comment #5).

  The issue is with using Indicator Applet Appmenu in the panel on
  gnome-flashback installed on standard Ubuntu (which I call Ubuntu
  (GNOME) Flashback).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice-writer 1:5.1.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jun  5 10:32:35 2016
  InstallationDate: Installed on 2016-04-26 (39 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160426)
  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/1589215/+subscriptions

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

[Desktop-packages] [Bug 1759462] Re: Keyboard shortcuts not operational on 18.04

2018-05-13 Thread Dustin Krysak

@arter97 - in my scenario, I have never had Compiz running (Does not
come on Ubuntu Budgie)

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

Title:
  Keyboard shortcuts not operational on 18.04

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

Bug description:
  After installing 18.04, I noticed that certain keyboard shortcuts no
  longer function.

  It appears to be related to the shortcuts that gnome-settings-daemon
  control as my shortcuts that are provided by my desktop (Budgie) still
  function.

  Some examples are:

  * Media keys for volume up/down/mute
  * ctrl-alt-t for the terminal. I tried changing the shortcut to test. Same 
behaviour.

  I double checked, and it looks like the needed daemon is still
  running,

  ```
  dustin3337  0.0  0.2 500736 22216 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-keyboard
  dustin3338  0.0  0.3 943372 25732 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-media-keys
  dustin3343  0.0  0.0 274908  5844 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-mouse
  dustin3345  0.0  0.3 519896 25144 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-power
  dustin3348  0.0  0.1 346004 10212 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-print-notifications
  dustin3351  0.0  0.0 374684  7952 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-smartcard
  dustin3355  0.0  0.1 329584  8064 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sound
  dustin3361  0.0  0.1 449708  9856 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sharing
  dustin3367  0.0  0.0 272416  4772 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
  dustin3375  0.0  0.0 420028  5804 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-rfkill
  dustin3383  0.0  0.2 507120 23244 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-wacom
  dustin3385  0.0  0.3 498040 25040 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-xsettings
  dustin3387  0.0  0.0 274900  5936 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-a11y-settings
  dustin3392  0.0  0.2 496016 22044 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-clipboard
  dustin3395  0.0  0.3 810156 25976 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-color
  dustin3396  0.0  0.2 471656 21080 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-datetime
  dustin3400  0.0  0.0 361196  7116 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-housekeeping
  dustin3433  0.0  0.1 505404 12576 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-printer
  dustin9776  0.0  0.0  18188  1032 pts/1S+   21:19   0:00 grep 
--color=auto gnome-settings-daemon
  ```

  Reboot does not seem to help. However, occasionally the shortcuts do
  seem to work - but only very occasionally.

  Any other info needed?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 27 21:12:18 2018
  InstallationDate: Installed on 2018-03-05 (22 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180304)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1759462] Re: Keyboard shortcuts not operational on 18.04

2018-05-13 Thread Dustin Krysak

I just had it come back. Just cannot nail it down (pattern).

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

Title:
  Keyboard shortcuts not operational on 18.04

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

Bug description:
  After installing 18.04, I noticed that certain keyboard shortcuts no
  longer function.

  It appears to be related to the shortcuts that gnome-settings-daemon
  control as my shortcuts that are provided by my desktop (Budgie) still
  function.

  Some examples are:

  * Media keys for volume up/down/mute
  * ctrl-alt-t for the terminal. I tried changing the shortcut to test. Same 
behaviour.

  I double checked, and it looks like the needed daemon is still
  running,

  ```
  dustin3337  0.0  0.2 500736 22216 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-keyboard
  dustin3338  0.0  0.3 943372 25732 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-media-keys
  dustin3343  0.0  0.0 274908  5844 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-mouse
  dustin3345  0.0  0.3 519896 25144 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-power
  dustin3348  0.0  0.1 346004 10212 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-print-notifications
  dustin3351  0.0  0.0 374684  7952 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-smartcard
  dustin3355  0.0  0.1 329584  8064 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sound
  dustin3361  0.0  0.1 449708  9856 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sharing
  dustin3367  0.0  0.0 272416  4772 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
  dustin3375  0.0  0.0 420028  5804 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-rfkill
  dustin3383  0.0  0.2 507120 23244 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-wacom
  dustin3385  0.0  0.3 498040 25040 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-xsettings
  dustin3387  0.0  0.0 274900  5936 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-a11y-settings
  dustin3392  0.0  0.2 496016 22044 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-clipboard
  dustin3395  0.0  0.3 810156 25976 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-color
  dustin3396  0.0  0.2 471656 21080 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-datetime
  dustin3400  0.0  0.0 361196  7116 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-housekeeping
  dustin3433  0.0  0.1 505404 12576 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-printer
  dustin9776  0.0  0.0  18188  1032 pts/1S+   21:19   0:00 grep 
--color=auto gnome-settings-daemon
  ```

  Reboot does not seem to help. However, occasionally the shortcuts do
  seem to work - but only very occasionally.

  Any other info needed?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 27 21:12:18 2018
  InstallationDate: Installed on 2018-03-05 (22 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180304)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2018-05-13 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  pulseaudio crashed with SIGABRT in pa_memimport_free()

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  just ordinary pulse crash. every day routine.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.16.0-77.99~14.04.1-generic 3.16.7-ckt27
  Uname: Linux 3.16.0-77-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  tp23619 F pulseaudio
   /dev/snd/controlC0:  tp22876 F audacity
tp23619 F pulseaudio
   /dev/snd/controlC1:  tp23619 F pulseaudio
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Mon May 14 04:33:26 2018
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2015-07-27 (1021 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: pulseaudio --start
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
   pa_memimport_free () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
   pa_pstream_unlink () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
   ?? () from /usr/lib/pulse-4.0/modules/libprotocol-native.so
   ?? () from /usr/lib/pulse-4.0/modules/libprotocol-native.so
  Title: pulseaudio crashed with SIGABRT in pa_memimport_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark
  dmi.bios.date: 07/23/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2105
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A785TD-V EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2105:bd07/23/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-VEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2018-05-14T04:23:08.098116

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

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

[Desktop-packages] [Bug 1767116] 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-05-13 Thread Michael Bloom

At their web site, Nvidia is able to detect the specific nvidia GPU
present in the current system from the web page.

It would thus seem to be reasonable for an nvidia package installation
to perfom a similar check during installation, and compare the current
GPU against a list of those supported by the software being installed.

Unless manually overridden, this could be used to prevent installation
of versions of software known to be incompatible with the current GPU
from interfering with a separate installation of compatible software.
(or to revert steps already performed it if the check could not be
performed before changes had already been made)

The use of such a check could be prophylactic against bug reports such
as this one.

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

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

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

Bug description:
  i don't know

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Uname: Linux 4.15.0-19-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu Apr 26 16:22:30 2018
  DuplicateSignature:
   package:nvidia-340:(not installed)
   Unpacking nvidia-340 (340.106-0ubuntu3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/nvidia-340_340.106-0ubuntu3_amd64.deb (--unpack):
trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in 
package nvidia-kernel-common-390 390.48-0ubuntu3
  ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which 
is also in package nvidia-kernel-common-390 390.48-0ubuntu3
  InstallationDate: Installed on 2016-05-19 (706 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package 
nvidia-kernel-common-390 390.48-0ubuntu3
  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/1767116/+subscriptions

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

[Desktop-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend

2018-05-13 Thread Alfred

>From comment 40 in upper stream bug - 
>https://bugzilla.gnome.org/show_bug.cgi?id=767317#c40
Upgrade to higher version(1.8) of NM should fix this. However xenial is stuck 
in 1.2.6... So I think 18.04 upgrade can fix this - which NM is 1.8.10.


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

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

Title:
  cannot view wifi networks after resume from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I 
have the same issue:
  After resume from suspend nm-applet doesn't show any information about 
connected/available wi-fi connections. Please see screenshot in attach.
  I can see current connection via CLI:

  nmcli dev
  DEVICE   TYPE  STATE  CONNECTION 
  docker0  bridgeconnected  docker0
  wlp58s0  wifi  connected  Turris 
  lo   loopback  unmanaged  -- 

  Now I have to run `killall nm-applet && nm-applet &` after every
  suspend. That fixes my issue

  I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1589401 but I was asked to submit separate bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  Uname: Linux 4.15.0-041500rc9-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 11 19:41:21 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-06 (493 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.1.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.1.137  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/1  
docker0 440d4ade-78be-45c3-a821-903971861d0c  
/org/freedesktop/NetworkManager/ActiveConnection/0  
   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/3  
Turris  e963-362e-4e4a-ac98-54af278d348d  
/org/freedesktop/NetworkManager/ActiveConnection/88 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1470235] Re: PolicyKit high memory usage

2018-05-13 Thread Wedge009

I have this issue on 17.10 and 18.04 but I'm not sure if it's related to
the original reporter's case because for me I suspect it's related to
amdgpu-pro. In earlier distributions the memory leak was elsewhere - I
can't remember if it was in xorg or plasmashell, though. I *think* it
also happened with fglrx, before amdgpu was released, but that was so
long ago now I can't be sure.

Regardless, the way I work around this is to restart the polkitd service
every now and then. Otherwise, after a few days the memory usage is in
the order of *gigabytes*!

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

Title:
  PolicyKit high memory usage

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  Periodically I install updates on my computer and reboot without
  logging in. When I come back to my computer and log in, polkitd is
  using a large chunk of memory. At the moment it's using > 2.3 GiB of
  memory on a machine with 8 GB RAM:

  $ ps aux | grep polkit
  root  1229  0.4 29.8 2652532 2420916 ? Sl   Jun19  67:38 
/usr/lib/policykit-1/polkitd --no-debug

  Killing the process frees the memory until I reboot again.

  
  I'm currently using the latest version of policykit-1:

  $ apt-file search /usr/lib/policykit-1/polkitd
  policykit-1: /usr/lib/policykit-1/polkitd

  $ apt-cache policy policykit-1
  policykit-1:
Installed: 0.105-4ubuntu2.14.04.1
Candidate: 0.105-4ubuntu2.14.04.1
Version table:
   *** 0.105-4ubuntu2.14.04.1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.105-4ubuntu2 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  $ sudo apt-get upgrade policykit-1
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  policykit-1 is already the newest version.

  
  Other information:

  $ lsb_release -rd
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: policykit-1 0.105-4ubuntu2.14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11
  Uname: Linux 3.16.0-41-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Date: Tue Jun 30 16:14:51 2015
  InstallationDate: Installed on 2014-08-25 (309 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

87 matches

Mail list logo