[Desktop-packages] [Bug 1969709] Re: libreoffice font selection unusably slow

[Harry W. Haines, III]

Okay so we know we have a bug.  Is this just going to sit here forever
without further investigation and resolution?  Ubuntu took Debian's
testing fontconfig package and patched it without any change log.

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

Title:
  libreoffice font selection unusably slow

Status in fontconfig package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Trying to scroll through the font list in the menu bar, I experience
  an unacceptable degree of lagging. Just popping up the dropdown list
  takes 7-10 seconds and the system takes the same amount of time to
  respond to perform individidual scrolling gestures. The CPU jumps to
  100% and the whole system becomes unresponsive.

  I have tried deb, snap and even the packages offered on the site of
  the LibreOffice project. They all manifest the same behaviour. The
  only thing that works is disabling font previews. I have downgraded to
  7.2 for now, which appears to be unaffected.

  I have contacted the LibreOffice team and they tell me that this
  should be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is
  shipping 2.13...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice-core 1:7.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 21 05:01:24 2022
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2022-03-27 (24 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1969709/+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 1969709] Re: libreoffice font selection unusably slow

[Harry W. Haines, III]

There is something else going on with fontconfig.  When you go to the
fonts viewer "Fonts", some of the DejaVu font families are not shown
correctly.  Some are duplicated and others are not shown.  The issue is
solid repeatable.  Install fonts-dejavu-extra and then launch "Fonts".
I'm not sure this is a libreoffice issue.  What patches did Ubuntu make
to it?

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

Title:
  libreoffice font selection unusably slow

Status in fontconfig package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Trying to scroll through the font list in the menu bar, I experience
  an unacceptable degree of lagging. Just popping up the dropdown list
  takes 7-10 seconds and the system takes the same amount of time to
  respond to perform individidual scrolling gestures. The CPU jumps to
  100% and the whole system becomes unresponsive.

  I have tried deb, snap and even the packages offered on the site of
  the LibreOffice project. They all manifest the same behaviour. The
  only thing that works is disabling font previews. I have downgraded to
  7.2 for now, which appears to be unaffected.

  I have contacted the LibreOffice team and they tell me that this
  should be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is
  shipping 2.13...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice-core 1:7.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 21 05:01:24 2022
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2022-03-27 (24 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1969709/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[harry]

Hi all.

Please excuse my  novice approach guys but I hope that I am making some
kind of contribution!

I to have a Lenovo Legion 5 and I am running Opensuse Tumbleweed with Kernel 
5.9.11-1 with Gnome 3.38.
With some help from the Opensuse forum I have the following error;

input: MSFT0001:00 04F3:3186 Touchpad as
/devices/platform/AMDI0010:03/i2c-0/i2c-
MSFT0001:00/0018:04F3:3186.0001/input/input7

This as you may gather stops my trackpad from working and they have suggested I 
visit here and ask for
any help!

All the best - Harry

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO

[Desktop-packages] [Bug 1885235] [NEW] python 3.8 bugs in hplip / focal upgrade

[Harry Coin]

Public bug reported:

/usr/share/hplip/base/utils.py:2063: SyntaxWarning: "is" with a literal. Did 
you mean "=="?
  if weburl is "" or weburl is None:
/usr/share/hplip/check-plugin.py:116: SyntaxWarning: "is" with a literal. Did 
you mean "=="?
  if log_level is 'debug':
/usr/share/hplip/check.py:685: SyntaxWarning: "is not" with a literal. Did you 
mean "!="?
  if 'getfacl' not in g and '' is not g and 'file' not in g:
/usr/share/hplip/installer/core_install.py:2037: SyntaxWarning: "is" with a 
literal. Did you mean "=="?
  if home_dir is "":
/usr/share/hplip/ui5/devmgr_ext.py:15: SyntaxWarning: "is not" with a literal. 
Did you mean "!="?
  if self.latest_available_version is not "":
/usr/share/hplip/ui5/devmgr_ext.py:37: SyntaxWarning: "is not" with a literal. 
Did you mean "!="?
  if self.latest_available_version is not "":

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

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

Title:
  python 3.8 bugs in hplip / focal upgrade

Status in hplip package in Ubuntu:
  New

Bug description:
  /usr/share/hplip/base/utils.py:2063: SyntaxWarning: "is" with a literal. Did 
you mean "=="?
if weburl is "" or weburl is None:
  /usr/share/hplip/check-plugin.py:116: SyntaxWarning: "is" with a literal. Did 
you mean "=="?
if log_level is 'debug':
  /usr/share/hplip/check.py:685: SyntaxWarning: "is not" with a literal. Did 
you mean "!="?
if 'getfacl' not in g and '' is not g and 'file' not in g:
  /usr/share/hplip/installer/core_install.py:2037: SyntaxWarning: "is" with a 
literal. Did you mean "=="?
if home_dir is "":
  /usr/share/hplip/ui5/devmgr_ext.py:15: SyntaxWarning: "is not" with a 
literal. Did you mean "!="?
if self.latest_available_version is not "":
  /usr/share/hplip/ui5/devmgr_ext.py:37: SyntaxWarning: "is not" with a 
literal. Did you mean "!="?
if self.latest_available_version is not "":

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1885235/+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 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]

[Harry Wright]

I've been getting exactly the same issue as described here, always when
I log in and find an "Authentication Required" dialog window in the top
left of the screen. I've attached a screen shot, the details of my
environment are below:

OS: PopOS (Ubuntu 20.04 LTS x86_64)
Kernel: 5.4.0-7626-generic
DE: Gnome
Window manager: Mutter

I also have a Yubikey that I'm using in challenge-response mode and have
the following line inserted in the following PAM modules:

`auth   sufficient  pam_yubico.so mode=challenge-response
chalresp_path=/var/yubico`

** Attachment added: "Screenshot of the authentication prompt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824874/+attachment/5366258/+files/Screenshot%20from%202020-05-04%2015-45-51.png

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

Title:
  undismissable, unclickable authentication dialog left on screen (top-
  left corner) after policykit authentication [pushModal: invocation of
  begin_modal failed]

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  In disco, when policykit prompted me for a password in order for
  update-manager to dispatch instructions to aptdaemon to perform
  package updates, the password dialog remained on the screen after I
  clicked 'authenticate'.

  The window is not clickable, it appears not to even be a window -
  mouse presses are received by the window underneath.  The exception is
  that the 'cancel' button is active and receives mouse events - but
  clicking it does nothing.

  This may be a gnome-shell issue rather than policykit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: policykit-1 0.105-25
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 13:14:33 2019
  InstallationDate: Installed on 2010-09-24 (3125 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824874/+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 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!

[Harry W. Haines, III]

I can confirm that rolling back to linux-firmware=1.173.12 solves the
issue with Kernel: 5.3.0-40-generic x86_64.

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

Title:
  [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to
  reset the VCPU!!!

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  when trying > DRI_PRIME=1 glxgears , the result in dmesg is as
  following

  [  +0.91] radeon :01:00.0: WB enabled
  [  +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x8ac2d26f
  [  +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0xa848de20
  [  +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x1e4494a9
  [  +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x98a9748e
  [  +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0xb6ff734d
  [  +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0x6b4da526
  [  +0.100566] radeon :01:00.0: failed VCE resume (-110).
  [  +0.179115] [drm] ring test on 0 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 1 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 2 succeeded in 1 usecs
  [  +0.06] [drm] ring test on 3 succeeded in 3 usecs
  [  +0.04] [drm] ring test on 4 succeeded in 3 usecs
  [  +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
giving up!!!
  [  +0.40] radeon :01:00.0: failed initializing UVD (-1).
  [  +0.60] [drm] ib test on ring 0 succeeded in 0 usecs
  [  +0.51] [drm] ib test on ring 1 succeeded in 0 usecs
  [  +0.32] [drm] ib test on ring 2 succeeded in 0 usecs
  [  +0.52] [drm] ib test on ring 3 succeeded in 0 usecs
  [  +0.29] [drm] ib test on ring 4 succeeded in 0 usecs

  Also it affects the boot time.

  the used OpenGL renderer is:
  "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Feb 28 11:50:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3801]
     Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:3801]
  InstallationDate: Installed on 2019-09-17 (163 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 20238
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=385a4174-5cfe-49c9-b4c3-9e64a251d432 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79CN46WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO

[Desktop-packages] [Bug 1828313] Re: wifi cannot connect to openwrt hidden ssid after upgrade from 18.10 to 19.04.

[harry lau]

sudo /usr/lib/NetworkManager/debug-helper.py --nm debug
Traceback (most recent call last):
  File "/usr/lib/NetworkManager/debug-helper.py", line 10, in 
mm_bus = bus.get_object('org.freedesktop.ModemManager', 
'/org/freedesktop/ModemManager')
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 241, in get_object
follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 248, in __init__
self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 180, in 
activate_name_owner
self.start_service_by_name(bus_name)
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 278, in 
start_service_by_name
'su', (bus_name, flags)))
  File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in 
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The 
name org.freedesktop.ModemManager was not provided by any .service files

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

Title:
  wifi cannot connect to openwrt hidden ssid after upgrade from 18.10 to
  19.04.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  pls see my post here

  https://answers.launchpad.net/ubuntu/+question/680506

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1828313/+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 1828313] Re: wifi cannot connect to openwrt hidden ssid after upgrade from 18.10 to 19.04.

[harry lau]

sudo /usr/lib/NetworkManager/debug-helper.py --mm debug
Traceback (most recent call last):
  File "/usr/lib/NetworkManager/debug-helper.py", line 10, in 
mm_bus = bus.get_object('org.freedesktop.ModemManager', 
'/org/freedesktop/ModemManager')
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 241, in get_object
follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 248, in __init__
self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 180, in 
activate_name_owner
self.start_service_by_name(bus_name)
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 278, in 
start_service_by_name
'su', (bus_name, flags)))
  File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in 
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The 
name org.freedesktop.ModemManager was not provided by any .service files



sudo /usr/lib/NetworkManager/debug-helper.py --wpa msgdump
Traceback (most recent call last):
  File "/usr/lib/NetworkManager/debug-helper.py", line 10, in 
mm_bus = bus.get_object('org.freedesktop.ModemManager', 
'/org/freedesktop/ModemManager')
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 241, in get_object
follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 248, in __init__
self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 180, in 
activate_name_owner
self.start_service_by_name(bus_name)
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 278, in 
start_service_by_name
'su', (bus_name, flags)))
  File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in 
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The 
name org.freedesktop.ModemManager was not provided by any .service files

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

Title:
  wifi cannot connect to openwrt hidden ssid after upgrade from 18.10 to
  19.04.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  pls see my post here

  https://answers.launchpad.net/ubuntu/+question/680506

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1828313/+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 1828313] Re: wifi cannot connect to openwrt hidden ssid after upgrade from 18.10 to 19.04.

[harry lau]

I can't found python script debug-helper.py  in /usr/lib/NetworkManager/

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

Title:
  wifi cannot connect to openwrt hidden ssid after upgrade from 18.10 to
  19.04.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  pls see my post here

  https://answers.launchpad.net/ubuntu/+question/680506

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1828313/+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 1512111] Re: "Ubuntu Light" font has heavier weight than "Ubuntu"

[Harry W. Haines, III]

Any further progress on this?  Why have a bug reporter if bugs are going
to sit out here forever unresolved.  This is a definite issue with the
metadata in the fonts.  Easily fixable.

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

Title:
  "Ubuntu Light" font has heavier weight than "Ubuntu"

Status in One Hundred Papercuts:
  In Progress
Status in Ubuntu Font Family:
  In Progress
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in fonts-ubuntu package in Ubuntu:
  In Progress

Bug description:
  After upgrading from Vivid to Wily, pages using the "Ubuntu light" font 
actually renders with a weight heavier than the regular one in web pages.
  This happens with Chrome/Chromium and also the Ubuntu browser.

  After manually reinstalling the 0.80-0ubuntu6 version from Vivid (in
  place of 0.83-0ubuntu1), the issue is fixed.

  See the attached screenshot showing the result seen browing
  https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: ttf-ubuntu-font-family 0.83-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov  1 17:55:19 2015
  Dependencies:

  InstallationDate: Installed on 2014-10-14 (382 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  PackageArchitecture: all
  SourcePackage: ubuntu-font-family-sources
  UpgradeStatus: Upgraded to wily on 2015-10-31 (0 days ago)

  IMPACT: Ubuntu Light font renders incorrectly for all 15.10 users
  which impacts the usability and visual design.

  The new version of font package (0.831) corrects the relationship
  between Light and Medium weight to follow the commonly used naming
  standards:

  Ubuntu Light  Light   Light Italic
  UbuntuRegular Italic  BoldBold Italic
  Ubuntu Medium Medium  Medium Italic   
  Ubuntu Condensed  Regular 
  Ubuntu Mono   Regular Italic  BoldBold Italic

  TEST CASE: in 15.10, go to
  https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu

  If the Light weight renders heavier than Normal weight, the bug is in
  place

  REGRESSION POTENTIAL

  0.831 was tested by manually running in 15.10 and no regression was
  noticed, while the bug was fixed. The potential for regression is
  small.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1512111/+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 1789022] Re: libcaca0 still depends on old libncursesw5 and libtinfo5

[Harry]

The bug was fixed with the 0.99.beta19-2ubuntu2 update.

** Changed in: libcaca (Ubuntu)
   Status: New => Fix Committed

-- 
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:
  Fix Committed

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 1789022] Re: libcaca0 still depends on old libncursesw5 and libtinfo5

[Harry]

The version 0.99.beta19-2ubuntu1 does not take this into account.

-- 
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 1799293] Re: Locking the screen once leaves screen contents visible but not interactive. Locking the screen a second time works.

[Harry P]

@Tarmo, have you tried pressing super+L after resume, maybe twice? that
brings backa login prompt for me.

ps I don't work for ubuntu or canonical or anything, but I can't help
saying -- please don't nag open source teams about fixing bugs, it
doesn't help. if you need to recommendation ubuntu to "normal" users,
the lts doesn't have this problem. if you really need a fix you can
always fix it yourself, or pay someone else to.

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

Title:
  Locking the screen once leaves screen contents visible but not
  interactive. Locking the screen a second time works.

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Bionic:
  Confirmed
Status in gnome-shell-extension-dashtodock source package in Bionic:
  Confirmed
Status in gnome-shell source package in Cosmic:
  Confirmed
Status in gnome-shell-extension-dashtodock source package in Cosmic:
  Confirmed
Status in gnome-shell source package in Disco:
  Confirmed
Status in gnome-shell-extension-dashtodock source package in Disco:
  Confirmed

Bug description:
  1) Ubuntu 18.10 (new install)
  2) gdm3 3.30.1-1ubuntu5

  Preconditions
  The session's user has auto-login enabled (i.e. the system starts and the 
user is not prompted for a password but directly presented with the desktop)

  3) What should happen:
  Unlocked desktop is showing. Lock screen is invoked (via WIN+L or via top 
right corner menu) and the lock screen is engaged (that is, lock screen clock 
shade drops down and screen fades to dark). Pressing ENTER brings back the lock 
screen and the password is prompted.

  4) What happens:
  First Win + L lets the system in a half locked state in which the contents of 
the desktop are seen although no interaction is possible. A second Win + L 
correctly invokes the lock screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799293/+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 1811159] Re: temporary freeze under opengl, not xrender, 18.10 & kernel 4.20

[Harry Coin]

And... spoke too soon.  It happens under xrender as well.  Shorter
freezes, frequency is the same.

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

Title:
  temporary freeze under opengl, not xrender, 18.10 &  kernel 4.20

Status in xorg package in Ubuntu:
  New

Bug description:
  Several times an hour, usually when switching focus from one window to
  another, all but the mouse will stop changing for a few seconds to a
  minute or so.  If a video is playing the sound will proceed as if
  normal but the screen will not change.  The shape of the mouse will
  not change.

  This is with stock ubuntu 18.10 under opengl with nouveau and i915
  drivers active (xrandr).  I tried using the latest possible ubuntu-
  compiled kernel, 4.20 with exactly the same results.  This did not
  happen before sometime after the cosmic native initial install.  When
  I change kde to 'xrender' -- the problem disappears.

  The oft reported dmesg content is:

  [83492.038575] WARNING: CPU: 2 PID: 2114 at 
drivers/gpu/drm/nouveau/nvif/vmm.c:71 nvif_vmm_put+0x6d/0x80 [nouveau]
  [83492.038576] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd 
grace fscache rfcomm ebtable_filter ebtables ip6table_filter ip6_tables devlink 
iptable_filter bpfilter cmac bnep bridge stp llc snd_hda_codec_realtek 
snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
i915 kvm_intel kvmgt vfio_mdev crct10dif_pclmul crc32_pclmul nouveau mdev 
vfio_iommu_type1 ghash_clmulni_intel vfio aesni_intel kvm aes_x86_64 
crypto_simd snd_hda_codec_hdmi cryptd uvcvideo ttm glue_helper 
videobuf2_vmalloc snd_hda_intel irqbypass videobuf2_memops btusb intel_cstate 
drm_kms_helper snd_hda_codec snd_usb_audio videobuf2_v4l2 btrtl dell_wmi 
videobuf2_common dell_smbios btbcm snd_seq_dummy intel_rapl_perf btintel 
sparse_keymap drm dcdbas videodev dell_wmi_descriptor snd_seq_oss 
snd_usbmidi_lib snd_hda_core mxm_wmi media joydev input_leds 8250_dw wmi_bmof 
snd_seq_midi snd_hwdep snd_seq_midi_event bluetooth snd_pcm snd_rawmidi mei_me 
idma64 snd_seq snd_seq_device i2c_algo_bit
  [83492.038598]  mei fb_sys_fops syscopyarea sysfillrect mac_hid virt_dma 
ecdh_generic sysimgblt snd_timer snd soundcore acpi_pad sch_fq_codel parport_pc 
ppdev lp sunrpc parport ip_tables x_tables autofs4 btrfs xor zstd_compress 
raid6_pq libcrc32c hid_generic usbhid uas hid usb_storage alx i2c_i801 ahci 
mdio intel_lpss_pci libahci intel_lpss wmi pinctrl_sunrisepoint video 
pinctrl_intel
  [83492.038611] CPU: 2 PID: 2114 Comm: Xorg Not tainted 4.20.0-042000-generic 
#201812232030
  [83492.038611] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.1.7 07/17/2018
  [83492.038625] RIP: 0010:nvif_vmm_put+0x6d/0x80 [nouveau]
  [83492.038626] Code: 00 00 48 8d 55 e0 be 02 00 00 00 48 c7 45 e0 00 00 00 00 
48 89 45 e8 e8 a1 e5 ff ff 85 c0 75 0a 48 c7 43 08 00 00 00 00 eb b7 <0f> 0b eb 
f2 e8 ba c3 7e cc 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44
  [83492.038627] RSP: 0018:ba4a0308fbc0 EFLAGS: 00010282
  [83492.038628] RAX: fffe RBX: ba4a0308fbf0 RCX: 

  [83492.038629] RDX: 0010 RSI: ba4a0308fb30 RDI: 
ba4a0308fbd0
  [83492.038629] RBP: ba4a0308fbe0 R08: c0d05b90 R09: 

  [83492.038630] R10: 91cc290bd310 R11: 0030 R12: 
ba4a0308fc28
  [83492.038630] R13: 91cc2bec60b0 R14:  R15: 
91cc290ba800
  [83492.038631] FS:  7f5a5f2f0a80() GS:91cc2ea8() 
knlGS:
  [83492.038632] CS:  0010 DS:  ES:  CR0: 80050033
  [83492.038633] CR2: 7f5a5800c000 CR3: 00043f42e003 CR4: 
003606e0
  [83492.038633] DR0:  DR1:  DR2: 

  [83492.038634] DR3:  DR6: fffe0ff0 DR7: 
0400
  [83492.038634] Call Trace:
  [83492.038659]  nouveau_vma_del+0x75/0xc0 [nouveau]
  [83492.038682]  nouveau_gem_object_close+0x1e0/0x1f0 [nouveau]
  [83492.038692]  drm_gem_object_release_handle+0x34/0xa0 [drm]
  [83492.038698]  drm_gem_handle_delete+0x61/0x90 [drm]
  [83492.038703]  ? drm_gem_handle_create+0x40/0x40 [drm]
  [83492.038709]  drm_gem_close_ioctl+0x25/0x30 [drm]
  [83492.038715]  drm_ioctl_kernel+0xad/0xf0 [drm]
  [83492.038720]  drm_ioctl+0x237/0x420 [drm]
  [83492.038726]  ? drm_gem_handle_create+0x40/0x40 [drm]
  [83492.038728]  ? do_iter_write+0xdd/0x190
  [83492.038750]  nouveau_drm_ioctl+0x73/0xc0 [nouveau]
  [83492.038752]  do_vfs_ioctl+0xa9/0x640
  [83492.038754]  ? __sys_recvmsg+0x88/0xa0
  [83492.038755]  ksys_ioctl+0x67/0x90
  [83492.038756]  __x64_sys_ioctl+0x1a/0x20
  [83492.038758]  do_syscall_64+0x5a/0x110
  [83492.038759]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [83492.038760] RIP: 0033:0x7f5a606273c7
  [83492.038761] Code: 00 00 90 48 8b 05 c9 3a 0d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff c3 

[Desktop-packages] [Bug 1811159] [NEW] temporary freeze under opengl, not xrender, 18.10 & kernel 4.20

[Harry Coin]

Public bug reported:

Several times an hour, usually when switching focus from one window to
another, all but the mouse will stop changing for a few seconds to a
minute or so.  If a video is playing the sound will proceed as if normal
but the screen will not change.  The shape of the mouse will not change.

This is with stock ubuntu 18.10 under opengl with nouveau and i915
drivers active (xrandr).  I tried using the latest possible ubuntu-
compiled kernel, 4.20 with exactly the same results.  This did not
happen before sometime after the cosmic native initial install.  When I
change kde to 'xrender' -- the problem disappears.

The oft reported dmesg content is:

[83492.038575] WARNING: CPU: 2 PID: 2114 at 
drivers/gpu/drm/nouveau/nvif/vmm.c:71 nvif_vmm_put+0x6d/0x80 [nouveau]
[83492.038576] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd 
grace fscache rfcomm ebtable_filter ebtables ip6table_filter ip6_tables devlink 
iptable_filter bpfilter cmac bnep bridge stp llc snd_hda_codec_realtek 
snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
i915 kvm_intel kvmgt vfio_mdev crct10dif_pclmul crc32_pclmul nouveau mdev 
vfio_iommu_type1 ghash_clmulni_intel vfio aesni_intel kvm aes_x86_64 
crypto_simd snd_hda_codec_hdmi cryptd uvcvideo ttm glue_helper 
videobuf2_vmalloc snd_hda_intel irqbypass videobuf2_memops btusb intel_cstate 
drm_kms_helper snd_hda_codec snd_usb_audio videobuf2_v4l2 btrtl dell_wmi 
videobuf2_common dell_smbios btbcm snd_seq_dummy intel_rapl_perf btintel 
sparse_keymap drm dcdbas videodev dell_wmi_descriptor snd_seq_oss 
snd_usbmidi_lib snd_hda_core mxm_wmi media joydev input_leds 8250_dw wmi_bmof 
snd_seq_midi snd_hwdep snd_seq_midi_event bluetooth snd_pcm snd_rawmidi mei_me 
idma64 snd_seq snd_seq_device i2c_algo_bit
[83492.038598]  mei fb_sys_fops syscopyarea sysfillrect mac_hid virt_dma 
ecdh_generic sysimgblt snd_timer snd soundcore acpi_pad sch_fq_codel parport_pc 
ppdev lp sunrpc parport ip_tables x_tables autofs4 btrfs xor zstd_compress 
raid6_pq libcrc32c hid_generic usbhid uas hid usb_storage alx i2c_i801 ahci 
mdio intel_lpss_pci libahci intel_lpss wmi pinctrl_sunrisepoint video 
pinctrl_intel
[83492.038611] CPU: 2 PID: 2114 Comm: Xorg Not tainted 4.20.0-042000-generic 
#201812232030
[83492.038611] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.1.7 07/17/2018
[83492.038625] RIP: 0010:nvif_vmm_put+0x6d/0x80 [nouveau]
[83492.038626] Code: 00 00 48 8d 55 e0 be 02 00 00 00 48 c7 45 e0 00 00 00 00 
48 89 45 e8 e8 a1 e5 ff ff 85 c0 75 0a 48 c7 43 08 00 00 00 00 eb b7 <0f> 0b eb 
f2 e8 ba c3 7e cc 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44
[83492.038627] RSP: 0018:ba4a0308fbc0 EFLAGS: 00010282
[83492.038628] RAX: fffe RBX: ba4a0308fbf0 RCX: 
[83492.038629] RDX: 0010 RSI: ba4a0308fb30 RDI: ba4a0308fbd0
[83492.038629] RBP: ba4a0308fbe0 R08: c0d05b90 R09: 
[83492.038630] R10: 91cc290bd310 R11: 0030 R12: ba4a0308fc28
[83492.038630] R13: 91cc2bec60b0 R14:  R15: 91cc290ba800
[83492.038631] FS:  7f5a5f2f0a80() GS:91cc2ea8() 
knlGS:
[83492.038632] CS:  0010 DS:  ES:  CR0: 80050033
[83492.038633] CR2: 7f5a5800c000 CR3: 00043f42e003 CR4: 003606e0
[83492.038633] DR0:  DR1:  DR2: 
[83492.038634] DR3:  DR6: fffe0ff0 DR7: 0400
[83492.038634] Call Trace:
[83492.038659]  nouveau_vma_del+0x75/0xc0 [nouveau]
[83492.038682]  nouveau_gem_object_close+0x1e0/0x1f0 [nouveau]
[83492.038692]  drm_gem_object_release_handle+0x34/0xa0 [drm]
[83492.038698]  drm_gem_handle_delete+0x61/0x90 [drm]
[83492.038703]  ? drm_gem_handle_create+0x40/0x40 [drm]
[83492.038709]  drm_gem_close_ioctl+0x25/0x30 [drm]
[83492.038715]  drm_ioctl_kernel+0xad/0xf0 [drm]
[83492.038720]  drm_ioctl+0x237/0x420 [drm]
[83492.038726]  ? drm_gem_handle_create+0x40/0x40 [drm]
[83492.038728]  ? do_iter_write+0xdd/0x190
[83492.038750]  nouveau_drm_ioctl+0x73/0xc0 [nouveau]
[83492.038752]  do_vfs_ioctl+0xa9/0x640
[83492.038754]  ? __sys_recvmsg+0x88/0xa0
[83492.038755]  ksys_ioctl+0x67/0x90
[83492.038756]  __x64_sys_ioctl+0x1a/0x20
[83492.038758]  do_syscall_64+0x5a/0x110
[83492.038759]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[83492.038760] RIP: 0033:0x7f5a606273c7
[83492.038761] Code: 00 00 90 48 8b 05 c9 3a 0d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 99 3a 0d 00 f7 d8 64 89 01 48
[83492.038762] RSP: 002b:7ffd2a2c6438 EFLAGS: 3246 ORIG_RAX: 
0010
[83492.038763] RAX: ffda RBX: 555e65a090c0 RCX: 7f5a606273c7
[83492.038763] RDX: 7ffd2a2c6470 RSI: 40086409 RDI: 0012
[83492.038764] RBP: 7ffd2a2c6470 R08: 555e64a01d78 R09: 0001
[83492.038764] R10: 

[Desktop-packages] [Bug 220263]

[harry]

Yeah pretty weird this is still an issue, should be pretty easy to fix. In the 
mean time. Meanwhile, this fixed my problem:
https://github.com/lightradius/firefox-dark-theme-fix

(backup your profile, then place the userContent.css file in your
~/.mozille/firefox/.default/chrome directory - create it if it
doesn't exist)

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

Title:
  Bad Firefox integration with dark themes

Status in Mozilla Firefox:
  Fix Released
Status in XULRunner:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme.
  Now I see all the input boxes and buttons filled with grey colour.
  This happened even with Firefox 2, but I solved that problem with a
  quick guide under the comment "firefox fix" by Proton at the bottom of
  this page: http://www.gnome-
  look.org/content/show.php/Grey+Neu?content=60824

  In Firefox 3 I can't correct this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/220263/+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 1789022] Re: libcaca0 still depends on old libncursesw5 and libtinfo5

[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 1800352] Re: screen lock leaves desktop and current applications displayed unless activated twice

[Harry P]

hi there, i've been trying to find the time to do a little video, but in
the meantime i have some more details:

- related bug: pressing lock (super+l) does effectively "lock" the
machine in that it prevents input/interaction, but does not hide the
desktop.  pressing it a second time displays the lock screen

- further detail:  bug where desktop is displayed only happens to me
when I close the laptop lid, rather than locking it manually, presumably
because when I lock I hit super+l twice because of the above.

- to resume from "broken-lock" i need to press the lock key to display
the password input screen.

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

Title:
  screen lock leaves desktop and current applications displayed unless
  activated twice

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  after upgrade to ubuntu 18.10, when resuming from lock (eg re-opening
  laptop lid), before typing password (or indeed anything), the whole
  desktop including running apps is displayed. although they are not
  interactable/responsive, sensitive info is displayed.

  possibly related, super+l seems to put the desktop into a similar
  state - apps visible, but not interactable.  pressing it a second time
  produces a more normal lock reaction.

  gnome-shell:  Installed: 3.30.1-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800352/+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 1800352] Re: screen lock leaves desktop and current applications displayed unless activated twice

[Harry P]

** Summary changed:

- desktop and current applications displayed when resuming from lock
+ screen lock leaves desktop and current applications displayed unless 
activated twice

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

Title:
  screen lock leaves desktop and current applications displayed unless
  activated twice

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  after upgrade to ubuntu 18.10, when resuming from lock (eg re-opening
  laptop lid), before typing password (or indeed anything), the whole
  desktop including running apps is displayed. although they are not
  interactable/responsive, sensitive info is displayed.

  possibly related, super+l seems to put the desktop into a similar
  state - apps visible, but not interactable.  pressing it a second time
  produces a more normal lock reaction.

  gnome-shell:  Installed: 3.30.1-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800352/+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 1800352] Re: desktop and current applications displayed when resuming from lock

[Harry P]

thanks for prompot, friendly and encouraging reply!  unfortunately i
can't run apport-collect, i seem to also be suffering from this bug:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1150335

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

Title:
  desktop and current applications displayed when resuming from lock

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  after upgrade to ubuntu 18.10, when resuming from lock (eg re-opening
  laptop lid), before typing password (or indeed anything), the whole
  desktop including running apps is displayed. although they are not
  interactable/responsive, sensitive info is displayed.

  possibly related, super+l seems to put the desktop into a similar
  state - apps visible, but not interactable.  pressing it a second time
  produces a more normal lock reaction.

  gnome-shell:  Installed: 3.30.1-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800352/+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 1800352] Re: desktop and current applications displayed when resuming from lock

[Harry P]

thanks for prompot, friendly and encouraging reply!  unfortunately i
can't run apport-collect, i seem to also be suffering from this bug:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1150335

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

Title:
  desktop and current applications displayed when resuming from lock

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  after upgrade to ubuntu 18.10, when resuming from lock (eg re-opening
  laptop lid), before typing password (or indeed anything), the whole
  desktop including running apps is displayed. although they are not
  interactable/responsive, sensitive info is displayed.

  possibly related, super+l seems to put the desktop into a similar
  state - apps visible, but not interactable.  pressing it a second time
  produces a more normal lock reaction.

  gnome-shell:  Installed: 3.30.1-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800352/+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 1800352] Re: desktop and current applications displayed when resuming from lock

[Harry P]

possibly related bugs from previous versions:

https://bugs.launchpad.net/debian/+source/gnome-shell/+bug/1532508
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1768786

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

Title:
  desktop and current applications displayed when resuming from lock

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  after upgrade to ubuntu 18.10, when resuming from lock (eg re-opening
  laptop lid), before typing password (or indeed anything), the whole
  desktop including running apps is displayed. although they are not
  interactable/responsive, sensitive info is displayed.

  possibly related, super+l seems to put the desktop into a similar
  state - apps visible, but not interactable.  pressing it a second time
  produces a more normal lock reaction.

  gnome-shell:  Installed: 3.30.1-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800352/+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 1800352] [NEW] desktop and current applications displayed when resuming from lock

[Harry P]

Public bug reported:

after upgrade to ubuntu 18.10, when resuming from lock (eg re-opening
laptop lid), before typing password (or indeed anything), the whole
desktop including running apps is displayed. although they are not
interactable/responsive, sensitive info is displayed.

possibly related, super+l seems to put the desktop into a similar state
- apps visible, but not interactable.  pressing it a second time
produces a more normal lock reaction.

gnome-shell:  Installed: 3.30.1-2ubuntu1

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

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

Title:
  desktop and current applications displayed when resuming from lock

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  after upgrade to ubuntu 18.10, when resuming from lock (eg re-opening
  laptop lid), before typing password (or indeed anything), the whole
  desktop including running apps is displayed. although they are not
  interactable/responsive, sensitive info is displayed.

  possibly related, super+l seems to put the desktop into a similar
  state - apps visible, but not interactable.  pressing it a second time
  produces a more normal lock reaction.

  gnome-shell:  Installed: 3.30.1-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800352/+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 1796865] [NEW] package libwoff1 1.0.2-1build0.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

[Harry Stuart Curtis]

Public bug reported:

lsb_release -rd

Description:Ubuntu 18.04.1 LTS
Release:18.04

What I expected to happen:

I expected Ubuntu to start without any errors.

What happened instead:

I received an error after logging in saying that a system app had a
problem.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libwoff1 1.0.2-1build0.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
AptOrdering:
 libbrotli1:amd64: Install
 libwoff1:amd64: Install
 libwebkit2gtk-4.0-37:amd64: Install
 libjavascriptcoregtk-4.0-18:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Oct  8 11:18:45 2018
Dependencies:
 gcc-8-base 8.2.0-1ubuntu2~18.04
 libbrotli1 1.0.3-1ubuntu1.2
 libc6 2.27-3ubuntu1
 libgcc1 1:8.2.0-1ubuntu2~18.04
 libstdc++6 8.2.0-1ubuntu2~18.04
DuplicateSignature:
 package:libwoff1:1.0.2-1build0.1
 Unpacking libwoff1:amd64 (1.0.2-1build0.1) ...
 dpkg-deb: error: failed to read archive 
'/var/cache/apt/archives/libwoff1_1.0.2-1build0.1_amd64.deb': No such file or 
directory
 dpkg: error processing archive 
/var/cache/apt/archives/libwoff1_1.0.2-1build0.1_amd64.deb (--unpack):
  dpkg-deb --fsys-tarfile subprocess returned error exit status 2
ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
InstallationDate: Installed on 2018-03-29 (193 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
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.3ubuntu0.1
SourcePackage: woff2
Title: package libwoff1 1.0.2-1build0.1 failed to install/upgrade: dpkg-deb 
--fsys-tarfile subprocess returned error exit status 2
UpgradeStatus: Upgraded to bionic on 2018-05-08 (153 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package libwoff1 1.0.2-1build0.1 failed to install/upgrade: dpkg-deb
  --fsys-tarfile subprocess returned error exit status 2

Status in woff2 package in Ubuntu:
  New

Bug description:
  lsb_release -rd

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  What I expected to happen:

  I expected Ubuntu to start without any errors.

  What happened instead:

  I received an error after logging in saying that a system app had a
  problem.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libwoff1 1.0.2-1build0.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
  AptOrdering:
   libbrotli1:amd64: Install
   libwoff1:amd64: Install
   libwebkit2gtk-4.0-37:amd64: Install
   libjavascriptcoregtk-4.0-18:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Oct  8 11:18:45 2018
  Dependencies:
   gcc-8-base 8.2.0-1ubuntu2~18.04
   libbrotli1 1.0.3-1ubuntu1.2
   libc6 2.27-3ubuntu1
   libgcc1 1:8.2.0-1ubuntu2~18.04
   libstdc++6 8.2.0-1ubuntu2~18.04
  DuplicateSignature:
   package:libwoff1:1.0.2-1build0.1
   Unpacking libwoff1:amd64 (1.0.2-1build0.1) ...
   dpkg-deb: error: failed to read archive 
'/var/cache/apt/archives/libwoff1_1.0.2-1build0.1_amd64.deb': No such file or 
directory
   dpkg: error processing archive 
/var/cache/apt/archives/libwoff1_1.0.2-1build0.1_amd64.deb (--unpack):
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  InstallationDate: Installed on 2018-03-29 (193 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  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.3ubuntu0.1
  SourcePackage: woff2
  Title: package libwoff1 1.0.2-1build0.1 failed to install/upgrade: dpkg-deb 
--fsys-tarfile subprocess returned error exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-05-08 (153 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/woff2/+bug/1796865/+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 1791991] Re: Nautilus in Gnome3 Staging PPA does not create thumbnails (tiff)

[Harry]

One more thing about the bubblewrap.
Now that gnome-desktop3 (libgnome-desktop-3-17_3.30.1-1ubuntu1) is build 
against bubblewrap and depends on it, thumbnailer is working correctly on my 
system.

The new gnome-desktop3 has been changed:
"debian/patches/disable-bubblewrap.patch, debian/control*: Drop changes to 
disable bubblewrap, now that it is approved to go into main."

I did test this with the official nautilus-3.26.4-0ubuntu4 and
tracker_2.1.4-1 (in proposed).

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

Title:
  Nautilus in Gnome3 Staging PPA does not create thumbnails (tiff)

Status in nautilus package in Ubuntu:
  New

Bug description:
  Nautilus version 3.30.0-0ubuntu1~cosmic1 in Gnome3 Staging PPA will not start.
  I am using Gnome-shell environment.
  And I also installed the new tracker version 2.1.3-1~cosmic1 from Gnome3 
Staging PPA.

  This is the error message when trying to start Nautilus from terminal:

  Tracker-ERROR **: 20:33:14.659: Unable to find default domain ontology
  rule /usr/share/tracker/domain-ontologies/default.rule

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1791991/+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 1768637] Re: /etc/modprobe.d is not a file

[Harry Coin]

FWIW I started seeing it after I installed a USB displaylink video
adapter using kernel module evdi.ko in
/lib/modules/4.15.0-34-generic/updates/dkms/

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

Title:
  /etc/modprobe.d is not a file

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Hello, I noticed the following entries in my journal after upgrading
  to 18.04 LTS from 16.04 LTS:

  May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file
  May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file
  May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file
  May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file
  May 02 12:06:31 hunt gpu-manager[1112]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
  May 02 12:06:31 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:31 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1170]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
  May 02 12:06:32 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:32 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1254]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
  May 02 12:06:32 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:32 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1316]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
  May 02 12:06:33 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:33 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:33 hunt systemd[1]: gpu-manager.service: Start request repeated 
too quickly.
  May 02 12:06:33 hunt systemd[1]: gpu-manager.service: Failed with result 
'start-limit-hit'.

  
  The referenced dkms path does not exist:

  sarnold@hunt:~$ ls -l /lib/modules/4.15.0-20-generic/updates/dkms
  ls: cannot access '/lib/modules/4.15.0-20-generic/updates/dkms': No such file 
or directory
  sarnold@hunt:~$ ls -l /lib/modules/4.15.0-20-generic/updates/
  ls: cannot access '/lib/modules/4.15.0-20-generic/updates/': No such file or 
directory
  sarnold@hunt:~$ ls -l /lib/modules/4.15.0-20-generic/
  total 5292
  lrwxrwxrwx  1 root root  40 Apr 23 21:56 build -> 
/usr/src/linux-headers-4.15.0-20-generic
  drwxr-xr-x  2 root root4096 Apr 23 21:56 initrd
  drwxr-xr-x 15 root root4096 May  1 18:23 kernel
  -rw-r--r--  1 root root 1253762 May  1 18:36 modules.alias
  -rw-r--r--  1 root root 1235639 May  1 18:36 modules.alias.bin
  -rw-r--r--  1 root root7594 Apr 23 21:56 modules.builtin
  -rw-r--r--  1 root root9600 May  1 18:36 modules.builtin.bin
  -rw-r--r--  1 root root  552117 May  1 18:36 modules.dep
  -rw-r--r--  1 root root  780401 May  1 18:36 modules.dep.bin
  -rw-r--r--  1 root root 317 May  1 18:36 modules.devname
  -rw-r--r--  1 root 

[Desktop-packages] [Bug 1768637] Re: /etc/modprobe.d is not a file

[Harry Coin]

This has been broken for years, and not understood or even looked at yet.  
Here's the start of it:
Bug #1369216 reported by dino99 on 2014-09-14

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

Title:
  /etc/modprobe.d is not a file

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Hello, I noticed the following entries in my journal after upgrading
  to 18.04 LTS from 16.04 LTS:

  May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file
  May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file
  May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file
  May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file
  May 02 12:06:31 hunt gpu-manager[1112]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
  May 02 12:06:31 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:31 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1170]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
  May 02 12:06:32 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:32 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1254]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
  May 02 12:06:32 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:32 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1316]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
  May 02 12:06:33 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:33 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:33 hunt systemd[1]: gpu-manager.service: Start request repeated 
too quickly.
  May 02 12:06:33 hunt systemd[1]: gpu-manager.service: Failed with result 
'start-limit-hit'.

  
  The referenced dkms path does not exist:

  sarnold@hunt:~$ ls -l /lib/modules/4.15.0-20-generic/updates/dkms
  ls: cannot access '/lib/modules/4.15.0-20-generic/updates/dkms': No such file 
or directory
  sarnold@hunt:~$ ls -l /lib/modules/4.15.0-20-generic/updates/
  ls: cannot access '/lib/modules/4.15.0-20-generic/updates/': No such file or 
directory
  sarnold@hunt:~$ ls -l /lib/modules/4.15.0-20-generic/
  total 5292
  lrwxrwxrwx  1 root root  40 Apr 23 21:56 build -> 
/usr/src/linux-headers-4.15.0-20-generic
  drwxr-xr-x  2 root root4096 Apr 23 21:56 initrd
  drwxr-xr-x 15 root root4096 May  1 18:23 kernel
  -rw-r--r--  1 root root 1253762 May  1 18:36 modules.alias
  -rw-r--r--  1 root root 1235639 May  1 18:36 modules.alias.bin
  -rw-r--r--  1 root root7594 Apr 23 21:56 modules.builtin
  -rw-r--r--  1 root root9600 May  1 18:36 modules.builtin.bin
  -rw-r--r--  1 root root  552117 May  1 18:36 modules.dep
  -rw-r--r--  1 root root  780401 May  1 18:36 modules.dep.bin
  -rw-r--r--  1 root root 317 May  1 18:36 modules.devname
  -rw-r--r--  1 root root 

[Desktop-packages] [Bug 1684123] Re: bus: MMIO read of 00000000 FAULT at 3e6684 [ IBUS ]

[Harry Coin]

nouveau :01:00.0: bus: MMIO read of  FAULT at 10ac08 [ IBUS ]
nouveau :01:00.0: bus: MMIO read of  FAULT at 3e6684 [ IBUS ]

4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64
x86_64 x86_64 GNU/Linux

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

Title:
  bus: MMIO read of  FAULT at 3e6684 [ IBUS ]

Status in Nouveau Xorg driver:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  This is the error i get when running xdiagnose:

  nouveau :06:00.0: bus: MMIO read of  FAULT at 3e6684 [
  IBUS ]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-0.3-generic 4.11.0-rc6
  Uname: Linux 4.11.0-0-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Apr 19 15:21:16 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.18, 4.10.0-19-generic, x86_64: installed
   virtualbox, 5.1.18, 4.11.0-0-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GM107 [GeForce GTX 750] [1458:362e]
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-0-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Wed Apr 19 10:21:15 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Laser Mouse MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "fbdev" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "fbdev" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/nouveau/+bug/1684123/+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 1792707] Re: Thunderbird version 60.0 language packs do not work - Ubuntu Mozilla Security Team PPA

[Harry]

This issue is fixed with the new thunderbird update
(1:60.0+build4-0ubuntu0.18.04.4) in Ubuntu Mozilla Security Team PPA.

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

Title:
  Thunderbird version 60.0 language packs do not work - Ubuntu Mozilla
  Security Team PPA

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  Hi install Thundebird 60 in Ubuntu 16.04 sudo apt-get install
  thunderbird-locale-pt-br and app show in en-US set manual in config
  editor general.useragent.locale pt-BR not work

  
  Actual results:

  Thundebird 60 show in en-US

  
  Expected results:

  Thundebird 60 show in pt-BR

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1792707/+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 1792707] Re: Thunderbird version 60.0 language packs do not work - Ubuntu Mozilla Security Team PPA

[Harry]

** Summary changed:

- Thunderbird 60 Locate not work
+ Thunderbird version 60.0 language packs do not work - Ubuntu Mozilla Security 
Team PPA

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

Title:
  Thunderbird version 60.0 language packs do not work - Ubuntu Mozilla
  Security Team PPA

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  Hi install Thundebird 60 in Ubuntu 16.04 sudo apt-get install
  thunderbird-locale-pt-br and app show in en-US set manual in config
  editor general.useragent.locale pt-BR not work

  
  Actual results:

  Thundebird 60 show in en-US

  
  Expected results:

  Thundebird 60 show in pt-BR

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1792707/+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 1792707] Re: Thunderbird 60 Locate not work

[Harry]

I have the same issue with the Finnish language pack, non of it works.

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

Title:
  Thunderbird 60 Locate not work

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  Hi install Thundebird 60 in Ubuntu 16.04 sudo apt-get install
  thunderbird-locale-pt-br and app show in en-US set manual in config
  editor general.useragent.locale pt-BR not work

  
  Actual results:

  Thundebird 60 show in en-US

  
  Expected results:

  Thundebird 60 show in pt-BR

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1792707/+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 1792403] [NEW] Nautilus 3.30 in Gnome Staging PP does not start without tracker package

[Harry]

Public bug reported:

Nautilus 3.30.0-0ubuntu1~cosmic1 in Gnome Staging PP does not start without 
tracker package.
However the tracker package is now in the universe.
The official nautilus version 3.26.4-0ubuntu3 works fine without tracker which 
is a suggested package anyway.

Trying to start nautilus from the terminal I get this error message:
Tracker-ERROR **: 20:33:14.659: Unable to find default domain ontology rule 
/usr/share/tracker/domain-ontologies/default.rule

So the nautilus 3.30 seems to need the default.rule file.

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


** Tags: cosmic

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

Title:
  Nautilus 3.30 in Gnome Staging PP does not start without tracker
  package

Status in nautilus package in Ubuntu:
  New

Bug description:
  Nautilus 3.30.0-0ubuntu1~cosmic1 in Gnome Staging PP does not start without 
tracker package.
  However the tracker package is now in the universe.
  The official nautilus version 3.26.4-0ubuntu3 works fine without tracker 
which is a suggested package anyway.

  Trying to start nautilus from the terminal I get this error message:
  Tracker-ERROR **: 20:33:14.659: Unable to find default domain ontology rule 
/usr/share/tracker/domain-ontologies/default.rule

  So the nautilus 3.30 seems to need the default.rule file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792403/+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 1791991] Re: Nautilus in Gnome3 Staging PPA does not create thumbnails (tiff)

[Harry]

OK, I looked at the file default.rule file.
And I found out that it belongs to the package tracker.
However, that package is in universe now.
I did not have it installed.

Anyway, after installing the package tracker, nautilus did start.
But the thumbnailer still did not work.
It did show of course the thumbnails that were created by the official nautilus 
version,
but it did not create any new ones (tiff).

So I deleted this experimental nautilus and tracker and returned back to
the official ones.


** Summary changed:

- Nautilus in Gnome3 Staging PPA will not start
+ Nautilus in Gnome3 Staging PPA does not create thumbnails (tiff)

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

Title:
  Nautilus in Gnome3 Staging PPA does not create thumbnails (tiff)

Status in nautilus package in Ubuntu:
  New

Bug description:
  Nautilus version 3.30.0-0ubuntu1~cosmic1 in Gnome3 Staging PPA will not start.
  I am using Gnome-shell environment.
  And I also installed the new tracker version 2.1.3-1~cosmic1 from Gnome3 
Staging PPA.

  This is the error message when trying to start Nautilus from terminal:

  Tracker-ERROR **: 20:33:14.659: Unable to find default domain ontology
  rule /usr/share/tracker/domain-ontologies/default.rule

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1791991/+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 1791991] Re: Nautilus in Gnome3 Staging PPA will not start

[Harry]

I did get the default.rule error (starting from terminal) when I had installed 
both the nautilus_3.30.0-0ubuntu1~cosmic1 and the tracker_2.1.3-1~cosmic1 
packeges.
As I mentioned, at that time nautilus did not start, the small wheel on the 
screen just kept on turning.

Then, after downgrading tracker_2.1.3-1~cosmic1 back to the official 
tracker_2.0.3-3, I did get nautilus_3.30.0-0ubuntu1~cosmic1 running.
However, the thumbnailer did not work then.

Sorry, I am not familiar with the backtrace system.

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

Title:
  Nautilus in Gnome3 Staging PPA will not start

Status in nautilus package in Ubuntu:
  New

Bug description:
  Nautilus version 3.30.0-0ubuntu1~cosmic1 in Gnome3 Staging PPA will not start.
  I am using Gnome-shell environment.
  And I also installed the new tracker version 2.1.3-1~cosmic1 from Gnome3 
Staging PPA.

  This is the error message when trying to start Nautilus from terminal:

  Tracker-ERROR **: 20:33:14.659: Unable to find default domain ontology
  rule /usr/share/tracker/domain-ontologies/default.rule

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1791991/+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 1791991] Re: Nautilus in Gnome3 Staging PPA will not start

[Harry]

After trying with the official cosmic tracker version 2.0.3-3, I found out that 
Nautilus will start.
However the bubblewrap won't work and I get no thumbnails (tiff, jpg).

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

Title:
  Nautilus in Gnome3 Staging PPA will not start

Status in nautilus package in Ubuntu:
  New

Bug description:
  Nautilus version 3.30.0-0ubuntu1~cosmic1 in Gnome3 Staging PPA will not start.
  I am using Gnome-shell environment.
  And I also installed the new tracker version 2.1.3-1~cosmic1 from Gnome3 
Staging PPA.

  This is the error message when trying to start Nautilus from terminal:

  Tracker-ERROR **: 20:33:14.659: Unable to find default domain ontology
  rule /usr/share/tracker/domain-ontologies/default.rule

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1791991/+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 1791991] [NEW] Nautilus in Gnome3 Staging PPA will not start

[Harry]

Public bug reported:

Nautilus version 3.30.0-0ubuntu1~cosmic1 in Gnome3 Staging PPA will not start.
I am using Gnome-shell environment.
And I also installed the new tracker version 2.1.3-1~cosmic1 from Gnome3 
Staging PPA.

This is the error message when trying to start Nautilus from terminal:

Tracker-ERROR **: 20:33:14.659: Unable to find default domain ontology
rule /usr/share/tracker/domain-ontologies/default.rule

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


** Tags: cosmic

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

Title:
  Nautilus in Gnome3 Staging PPA will not start

Status in nautilus package in Ubuntu:
  New

Bug description:
  Nautilus version 3.30.0-0ubuntu1~cosmic1 in Gnome3 Staging PPA will not start.
  I am using Gnome-shell environment.
  And I also installed the new tracker version 2.1.3-1~cosmic1 from Gnome3 
Staging PPA.

  This is the error message when trying to start Nautilus from terminal:

  Tracker-ERROR **: 20:33:14.659: Unable to find default domain ontology
  rule /usr/share/tracker/domain-ontologies/default.rule

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1791991/+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 1789022] [NEW] libcaca0 still depends on old libncursesw5 and libtinfo5

[Harry]

Public bug reported:

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.

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


** Tags: cosmic

-- 
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 1783363] Re: Use of activities in GNOME Shell 3.28.3 prohibits applications from being displayed

[Harry]

Same bug here too.

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

Title:
  Use of activities in GNOME Shell 3.28.3 prohibits applications from
  being displayed

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I noticed this problem immediately after updating GNOME Shell to
  3.28.3 this afternoon.

  If I log in the super key works as normal as does "Show Applications".
  If I then start an application and then use the super key I cannot
  again use any open application. I have to close applications from the
  launcher. At this point I can't use "Show Applications" as the icons
  simply don't appear on the screen. I'm also unable to search for
  applications.

  Logging out and back in again is necessary to restore proper
  functionality until of course I again user the super key etc.

  At first I thought this was only affecting my main user but I also
  have two other users set up. Their profiles have not been customised.
  I see the same behaviour with both users. Any display of Activities or
  Show Applications prohibits any further use of opened programs.

  I've disabled all extensions and of course rebooted but the problem
  remains.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.28.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.10-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 24 17:02:31 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-07-12 (12 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   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/1783363/+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 1369216] Re: gpu-manager: /etc/modprobe.d is not a file

[Harry Coin]

Bionic LTS:  dmesg
[0.00] Linux version 4.15.0-20-generic (buildd@lgw01-amd64-039) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 
2018 (Ubuntu 4.15.0-20.21-generic 4.15.17)
[0.00] Command line: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1b414f6c-af2f-4116-a11c-01762878cf09 ro rootflags=subvol=@ nomodeset 
acpi_enforce_resources=lax pcie_aspm=off enable_mtrr_cleanup 
mtrr_spare_reg_nr=3 mtrr_gran_size=128M mtrr_chunk_size=256M
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Centaur CentaurHauls
[0.00] x86/fpu: x87 FPU will use FXSAVE
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009dbff] usable
[0.00] BIOS-e820: [mem 0x0009f800-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000f-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xbfed] usable
[0.00] BIOS-e820: [mem 0xbfee-0xbfee2fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xbfee3000-0xbfee] ACPI data
[0.00] BIOS-e820: [mem 0xbfef-0xbfef] reserved
[0.00] BIOS-e820: [mem 0xe000-0xe3ff] reserved
[0.00] BIOS-e820: [mem 0xfec0-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00023fff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] random: fast init done
[0.00] SMBIOS 2.4 present.
[0.00] DMI: Gigabyte Technology Co., Ltd. P35-DQ6/P35-DQ6, BIOS F9 
06/22/2009

...

Apr 28 15:46:26 syslog1db3 kernel: [3.025842] nouveau :01:00.0: fifo: 
read fault at 198000 engine 05 [BAR2] client 07 [HOST_CPU] reason 02 [PTE] 
on channel -1 [003fe36000 unknown]
Apr 28 15:46:26 syslog1db3 kernel: [3.026291] nouveau :01:00.0: DRM: 
allocated 1600x900 fb: 0x6, bo 4f60934e
Apr 28 15:46:26 syslog1db3 kernel: [3.028035] fbcon: nouveaufb (fb0) is 
primary device
Apr 28 15:46:26 syslog1db3 kernel: [3.028095] Console: switching to colour 
frame buffer device 128x48
Apr 28 15:46:26 syslog1db3 kernel: [3.028119] nouveau :01:00.0: fb0: 
nouveaufb frame buffer device
Apr 28 15:46:26 syslog1db3 kernel: [3.060003] [drm] Initialized nouveau 
1.3.1 20120801 for :01:00.0 on minor 0
Apr 28 15:46:26 syslog1db3 kernel: [3.060037] nouveau :02:00.0: 
enabling device ( -> 0003)
Apr 28 15:46:26 syslog1db3 kernel: [3.060212] nouveau :02:00.0: NVIDIA 
GK208B (b06070b1)
Apr 28 15:46:26 syslog1db3 kernel: [3.123977] clocksource: Switched to 
clocksource tsc
Apr 28 15:46:26 syslog1db3 kernel: [3.192698] nouveau :02:00.0: bios: 
version 80.28.78.00.06
Apr 28 15:46:26 syslog1db3 kernel: [3.194153] nouveau :02:00.0: fb: 
1024 MiB DDR3

..
Apr 28 15:46:26 syslog1db3 gpu-manager[530]: /etc/modprobe.d is not a file
Apr 28 15:46:26 syslog1db3 gpu-manager[530]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
Apr 28 15:46:26 syslog1db3 gpu-manager[530]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
Apr 28 15:46:26 syslog1db3 systemd[1]: Started Detect the available GPUs and 
deal with any system changes.

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

Title:
  gpu-manager: /etc/modprobe.d is not a file

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Get these lines logged into gpu-manager.log, on that fresh stock
  installation

  /etc/modprobe.d is not a file
  update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Sep 14 08:42:45 2014
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.default.whoopsie: [modified]
  modified.conffile..etc.gdm.Init.Default: [modified]
  mtime.conffile..etc.default.whoopsie: 2014-08-29T19:12:47.435075
  mtime.conffile..etc.gdm.Init.Default: 2014-09-07T17:01:23.246055

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1731651] Re: gpu-manager[630]: Error: can't open /lib/modules/4.13.0-16-generic/updates/dkms

[Harry Coin]

That error is now baaack

 dmesg
[0.00] Linux version 4.15.0-20-generic (buildd@lgw01-amd64-039) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 
2018 (Ubuntu 4.15.0-20.21-generic 4.15.17)
[0.00] Command line: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1b414f6c-af2f-4116-a11c-01762878cf09 ro rootflags=subvol=@ nomodeset 
acpi_enforce_resources=lax pcie_aspm=off enable_mtrr_cleanup 
mtrr_spare_reg_nr=3 mtrr_gran_size=128M mtrr_chunk_size=256M
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Centaur CentaurHauls
[0.00] x86/fpu: x87 FPU will use FXSAVE
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009dbff] usable
[0.00] BIOS-e820: [mem 0x0009f800-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000f-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xbfed] usable
[0.00] BIOS-e820: [mem 0xbfee-0xbfee2fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xbfee3000-0xbfee] ACPI data
[0.00] BIOS-e820: [mem 0xbfef-0xbfef] reserved
[0.00] BIOS-e820: [mem 0xe000-0xe3ff] reserved
[0.00] BIOS-e820: [mem 0xfec0-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00023fff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] random: fast init done
[0.00] SMBIOS 2.4 present.
[0.00] DMI: Gigabyte Technology Co., Ltd. P35-DQ6/P35-DQ6, BIOS F9 
06/22/2009

...


Apr 29 06:47:38 syslog1db3 gpu-manager[555]: /etc/modprobe.d is not a file
Apr 29 06:47:38 syslog1db3 gpu-manager[555]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
Apr 29 06:47:38 syslog1db3 gpu-manager[555]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
Apr 29 06:47:38 syslog1db3 systemd[1]: Started Detect the available GPUs and 
deal with any system changes.

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

Title:
  gpu-manager[630]: Error: can't open
  /lib/modules/4.13.0-16-generic/updates/dkms

Status in ubuntu-drivers-common package in Ubuntu:
  Invalid

Bug description:
  That fresh install does not have dkms package installed. But
  'journalctl | grep modules' list that non expected subdir & file
  'updates/dkms'

  The kernel has been purged then reinstalled to get rid of this zomby
  path, but the output is still the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-drivers-common 1:0.4.24
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Nov 11 17:15:54 2017
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.gpu-manager.conf: 2017-11-11T16:32:50.891638

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1731651/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Richard Harry]

comment #39 fixed it for me

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1740662] [NEW] eog shows irritating warning with tiff files

[Harry]

Public bug reported:

The eog shows each time I open a tiff file (tagged image file format)
this "warning" or "information" message:

"This image contains multiple pages. Image Viewer displays only the
first page. Do you want to open the image with the Document Viewer to
see all pages."

The reason to this is that Nikon creates a tiff file which contains two images, 
the main image is the full image itself and the second is a thumbnail if it.
There are no pages here, and this is not a document, it is an image file.
So the warning file is erraneous.

This is actually intentional act and not a bug. But it doesn't make the issue 
go away.
I cannot simply make this ugly blue information bar silent, not to appear again.

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

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

Title:
  eog shows irritating warning with tiff files

Status in eog package in Ubuntu:
  New

Bug description:
  The eog shows each time I open a tiff file (tagged image file format)
  this "warning" or "information" message:

  "This image contains multiple pages. Image Viewer displays only the
  first page. Do you want to open the image with the Document Viewer to
  see all pages."

  The reason to this is that Nikon creates a tiff file which contains two 
images, the main image is the full image itself and the second is a thumbnail 
if it.
  There are no pages here, and this is not a document, it is an image file.
  So the warning file is erraneous.

  This is actually intentional act and not a bug. But it doesn't make the issue 
go away.
  I cannot simply make this ugly blue information bar silent, not to appear 
again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1740662/+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 1718526] [NEW] Artful-proposed: gdk-pixbuf breaks tiff file visibility

[Harry]

Public bug reported:

After upgrading the package gdk-pixbuf to 2.36.10-1 (artful-proposed) the tiff 
files cannot be opened any more.
For example Eye of Gnome claims the file type tiff is unknown.
Downgrading to the artful release version 2.36.5-3ubuntu1 solves the issue and 
tiff's are OK.

** Affects: gdk-pixbuf (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful-proposed

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

Title:
  Artful-proposed: gdk-pixbuf breaks tiff file visibility

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  After upgrading the package gdk-pixbuf to 2.36.10-1 (artful-proposed) the 
tiff files cannot be opened any more.
  For example Eye of Gnome claims the file type tiff is unknown.
  Downgrading to the artful release version 2.36.5-3ubuntu1 solves the issue 
and tiff's are OK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1718526/+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 1654918] Re: No Internet access with default of Automatic (DHCP)

[harry brijs]

i installed from iso file
internet is avail upon goodwill of the system 
or whatever.
It comes but most of the time it does not stay.
I did not yet correlate this behaviour
2

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

Title:
  No Internet access with default of  Automatic (DHCP)

Status in Linux:
  New
Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Fresh 17.04 install, wireless router connects without any issue but there is 
no internet connection/access.
  This continues thru disconnecting, reconnecting, rebooting ect, Nothing..

  If I edit the connection > IPv4 Settings to Automatic (DCHP) addresses only & 
manually add Google DNS nameservers: then internet is enabled. screen attached
  Note this also affects ethernet, not just wireless
  Hardware is:
  description: Wireless interface
     product: Wireless 7260
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:08:00.0
     logical name: wlp8s0
     version: 73
     serial: 
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.9.0-11-generic firmware=17.352738.0 ip=192.168.1.4 latency=0 
link=ye s multicast=yes wireless=IEEE 802.11
     resources: irq:32 memory:c240-c2401fff

  To note: this hardware works perfectly in 14.04 > 16.04
  Add. note; issue doesn't arise with 4.11.x kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.2-2ubuntu4
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan  8 22:08:26 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-09 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170108)
  IpRoute:
   default via 192.168.1.1 dev wlp8s0  proto static  metric 600
   169.254.0.0/16 dev wlp8s0  scope link  metric 1000
   192.168.1.0/24 dev wlp8s0  proto kernel  scope link  src 192.168.1.4  metric 
600
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile

   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   wlp8s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2  
06F21A  fb815a75-4091-455e-b73d-2c1f2d97220f  
/org/freedesktop/NetworkManager/ActiveConnection/0
   enp7s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1654918/+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 1682322] [NEW] PCI/internal sound card not detected dummy drive only

[harry soiland]

Public bug reported:

only the dummy drive is showing in my sound preferences

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', 
'/dev/dsp1', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer'] 
failed with exit code 1:
CurrentDesktop: Unity
Date: Thu Apr 13 12:53:46 2017
InstallationDate: Installed on 2017-04-05 (7 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/30/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.9
dmi.board.name: 01W6F7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.9:bd11/30/2016:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.name: Inspiron 5567
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  PCI/internal sound card not detected dummy drive only

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  only the dummy drive is showing in my sound preferences

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', 
'/dev/dsp1', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Thu Apr 13 12:53:46 2017
  InstallationDate: Installed on 2017-04-05 (7 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.9
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.9:bd11/30/2016:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 5567
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1682322/+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 1665602] Re: nautilus no thumbnails for .jpg and .png

[Harry]

This may not be a nautilus bug.
It seems the bug persists even if I upgrade nautilus from the Gnome Staging PPA 
to either newer one:
3.22.2
3.23.90

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

Title:
  nautilus no thumbnails for .jpg and .png

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  thumbnail for .tif is ok
  corrado@corrado-z2:~$ inxi
  CPU~Dual core Intel Core i3-4130 (-HT-MCP-) speed/max~3366/3400 MHz 
Kernel~4.10.0-8-generic x86_64 Up~1:03 Mem~983.2/7861.2MB HDD~1000.2GB(16.0% 
used) Procs~231 Client~Shell inxi~2.3.8  
  corrado@corrado-z2:~$ uname -a
  Linux corrado-z2 4.10.0-8-generic #10-Ubuntu SMP Mon Feb 13 14:04:59 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  corrado@corrado-z2:~$ 
  display was ok with kernel 4.9.0-15
  corrado@corrado-z2:~$ apt-cache policy nautilus
  nautilus:
Installed: 1:3.20.3-1ubuntu4
Candidate: 1:3.20.3-1ubuntu4
Version table:
   *** 1:3.20.3-1ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-z2:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: nautilus 1:3.20.3-1ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Fri Feb 17 11:22:50 2017
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'search-view' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'1329x774+49+24'"
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'larger'"
  InstallationDate: Installed on 2017-01-23 (24 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170123)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1665602/+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 1665602] Re: nautilus no thumbnails for .jpg and .png

[Harry]

I can confirm this bug. Tiff is OK for me too.

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

Title:
  nautilus no thumbnails for .jpg and .png

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  thumbnail for .tif is ok
  corrado@corrado-z2:~$ inxi
  CPU~Dual core Intel Core i3-4130 (-HT-MCP-) speed/max~3366/3400 MHz 
Kernel~4.10.0-8-generic x86_64 Up~1:03 Mem~983.2/7861.2MB HDD~1000.2GB(16.0% 
used) Procs~231 Client~Shell inxi~2.3.8  
  corrado@corrado-z2:~$ uname -a
  Linux corrado-z2 4.10.0-8-generic #10-Ubuntu SMP Mon Feb 13 14:04:59 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  corrado@corrado-z2:~$ 
  display was ok with kernel 4.9.0-15
  corrado@corrado-z2:~$ apt-cache policy nautilus
  nautilus:
Installed: 1:3.20.3-1ubuntu4
Candidate: 1:3.20.3-1ubuntu4
Version table:
   *** 1:3.20.3-1ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-z2:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: nautilus 1:3.20.3-1ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Fri Feb 17 11:22:50 2017
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'search-view' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'1329x774+49+24'"
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'larger'"
  InstallationDate: Installed on 2017-01-23 (24 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170123)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1665602/+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 721386] Re: [Upstream] Impress PPT export does not preserve hyperlinks

[Harry Wood]

Upgraded to LibreOffice 5.2.4.2 . Still an issue

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

Title:
  [Upstream] Impress PPT export does not preserve hyperlinks

Status in LibreOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: libreoffice

  1)
  Natty:
  lsb_release -rd
  Description:Ubuntu Natty (development branch)
  Release:11.04

  Maverick:
  lsb_release -rd
  Description:  Ubuntu 10.10
  Release:  10.10

  Lucid:
  lsb_release -rd
  Description:  Ubuntu 10.04.2 LTS
  Release:  10.04

  2)
  Natty:
  apt-cache policy libreoffice-impress
  libreoffice-impress:
Installed: 1:3.3.1-1ubuntu5
Candidate: 1:3.3.1-1ubuntu5
Version table:
   *** 1:3.3.1-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 100
  /var/lib/dpkg/status

  Maverick:
  apt-cache policy libreoffice-impress
  libreoffice-impress:
    Installed: 1:3.3.1-1ubuntu3~maverick1
    Candidate: 1:3.3.1-1ubuntu3~maverick1
    Version table:
   *** 1:3.3.1-1ubuntu3~maverick1 0
  500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ maverick/main 
i386 Packages
  100 /var/lib/dpkg/status

  Lucid:
  apt-cache policy libreoffice
  libreoffice:
    Installed: 1:3.3.0-1lucid1
    Candidate: 1:3.3.0-1lucid1
    Version table:
   *** 1:3.3.0-1lucid1 0
  500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ lucid/main 
Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when performs via the Terminal:

  loimpress -nologo

  Create button -> in Slide 1 click "Click to add text" and type example
  -> highlight text -> click Insert -> Hyperlink -> in Target combo box
  type www.launchpad.net -> click Apply button -> click Close button ->
  File -> Save As -> File name: example -> File type: Microsoft
  PowerPoint 97/2000/XP (.ppt) -> Save button -> Keep Current Format
  button -> File -> Exit -> open via the Terminal:

  loimpress -nologo example.ppt

  The hyperlink is preserved.

  4) Notice the hyperlink is gone with only the text remaining.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/721386/+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 721386] Re: [Upstream] Impress PPT export does not preserve hyperlinks

[Harry Wood]

Does not work for me. Still an issue in LibreOffice 5.0.2.2

hyperlinks are gone when opening from a PPT file or also a PPTX file.

Three different types of hyperlink all get stripped (a URL detected and
automatically created as a hyperlink. An inserted hyperlink with target
set to an external URL, and a hyperlink to another slide)

These hyperlinks all remain as expected when saving and reloading from
an .odp file (issue with powerpoint import)

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

Title:
  [Upstream] Impress PPT export does not preserve hyperlinks

Status in LibreOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: libreoffice

  1)
  Natty:
  lsb_release -rd
  Description:Ubuntu Natty (development branch)
  Release:11.04

  Maverick:
  lsb_release -rd
  Description:  Ubuntu 10.10
  Release:  10.10

  Lucid:
  lsb_release -rd
  Description:  Ubuntu 10.04.2 LTS
  Release:  10.04

  2)
  Natty:
  apt-cache policy libreoffice-impress
  libreoffice-impress:
Installed: 1:3.3.1-1ubuntu5
Candidate: 1:3.3.1-1ubuntu5
Version table:
   *** 1:3.3.1-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 100
  /var/lib/dpkg/status

  Maverick:
  apt-cache policy libreoffice-impress
  libreoffice-impress:
    Installed: 1:3.3.1-1ubuntu3~maverick1
    Candidate: 1:3.3.1-1ubuntu3~maverick1
    Version table:
   *** 1:3.3.1-1ubuntu3~maverick1 0
  500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ maverick/main 
i386 Packages
  100 /var/lib/dpkg/status

  Lucid:
  apt-cache policy libreoffice
  libreoffice:
    Installed: 1:3.3.0-1lucid1
    Candidate: 1:3.3.0-1lucid1
    Version table:
   *** 1:3.3.0-1lucid1 0
  500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ lucid/main 
Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when performs via the Terminal:

  loimpress -nologo

  Create button -> in Slide 1 click "Click to add text" and type example
  -> highlight text -> click Insert -> Hyperlink -> in Target combo box
  type www.launchpad.net -> click Apply button -> click Close button ->
  File -> Save As -> File name: example -> File type: Microsoft
  PowerPoint 97/2000/XP (.ppt) -> Save button -> Keep Current Format
  button -> File -> Exit -> open via the Terminal:

  loimpress -nologo example.ppt

  The hyperlink is preserved.

  4) Notice the hyperlink is gone with only the text remaining.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/721386/+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 1647133] Re: dns=dnsmasq does not work any more

[Harry]

This bug is now solved with the latest network-manager v. 1.4.2-3ubuntu2 in 
Zesty.
Here: 
https://launchpad.net/ubuntu/+source/network-manager/1.4.2-3ubuntu2


** Changed in: network-manager (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  dns=dnsmasq does not work any more

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Network-manager will make my network connection immediately lost after 
updating to the newest version 1.4.2-2ubuntu4.
  However, downgrading to the previous version 1.4.2-2ubuntu3 the network 
connection is back again and fine. If, with this version, I remove the file 
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as 
network-manager creates a new resolv.conf file.

  The newest version 1.4.2-2ubuntu4 also creates the very same kind of
  file, but no network.

  I have the latest (Gnome-shell DE) updates installed and of course all 
packages that network-manager depends on. But not the ones it only recommends 
or suggests.
  Should I have resolvconf installed? I think not, as isc-dhcp-client only 
suggests it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+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 1647133] Re: dns=dnsmasq does not work any more

[Harry]

I can also confirm, though there is no need to, that the newest version of NM 
1.4.2-3ubuntu1 does not work better either.
So this bug still remains unsolved.

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

Title:
  dns=dnsmasq does not work any more

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Network-manager will make my network connection immediately lost after 
updating to the newest version 1.4.2-2ubuntu4.
  However, downgrading to the previous version 1.4.2-2ubuntu3 the network 
connection is back again and fine. If, with this version, I remove the file 
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as 
network-manager creates a new resolv.conf file.

  The newest version 1.4.2-2ubuntu4 also creates the very same kind of
  file, but no network.

  I have the latest (Gnome-shell DE) updates installed and of course all 
packages that network-manager depends on. But not the ones it only recommends 
or suggests.
  Should I have resolvconf installed? I think not, as isc-dhcp-client only 
suggests it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+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 1647133] Re: dns=dnsmasq does not work any more

[Harry]

First of all,
If NM 1.4.2-2ubuntu4 needs the package resolvconf in order to function 
properly, it should depend on it.

Secondly,
NM 1.4.2-2ubuntu3 works perfectly, like all earlier versions, without the 
package resolvconf.

Thirdly,
after installing resolvconf with NM 1.4.2-2ubuntu4, NM still does not work 
properly. It is not OK.

And here are some test results.

With NM 1.4.2-2ubuntu3: "systemd-resolve --status"
Global
 DNS Servers: 127.0.1.1
  DNS Domain: dhcp.inet.fi
  DNSSEC NTA: 10.in-addr.arpa
  home
  internal
  intranet
  lan
  local
  private
  test
Link 2 (eth0)
  Current Scopes: LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: allow-downgrade
DNSSEC supported: yes

With NM 1.4.2-2ubuntu4: "systemd-resolve --status"
Global
  DNSSEC NTA: 10.in-addr.arpa
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan
  local
  private
  test
Link 2 (eth0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: allow-downgrade
DNSSEC supported: yes
 DNS Servers: 193.210.18.18
  193.210.19.19
  DNS Domain: dhcp.inet.fi

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

Title:
  dns=dnsmasq does not work any more

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Network-manager will make my network connection immediately lost after 
updating to the newest version 1.4.2-2ubuntu4.
  However, downgrading to the previous version 1.4.2-2ubuntu3 the network 
connection is back again and fine. If, with this version, I remove the file 
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as 
network-manager creates a new resolv.conf file.

  The newest version 1.4.2-2ubuntu4 also creates the very same kind of
  file, but no network.

  I have the latest (Gnome-shell DE) updates installed and of course all 
packages that network-manager depends on. But not the ones it only recommends 
or suggests.
  Should I have resolvconf installed? I think not, as isc-dhcp-client only 
suggests it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+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 1647133] Re: dns=dnsmasq does not work any more

[Harry]

One possible issue is the contents of the /etc/resolv.conf (or actually
/run/resolvconf/resolv.conf).

With NM 1.4.2-2ubuntu4 the /etc/resolv.conf is:

nameserver 127.0.0.53


But with NM 1.4.2-2ubuntu3 it is:

search dhcp.inet.fi
nameserver 127.0.1.1


So where did the line "search dhcp.inet.fi" go?
I think this needs to be there in order to a fully working network.

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

Title:
  dns=dnsmasq does not work any more

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Network-manager will make my network connection immediately lost after 
updating to the newest version 1.4.2-2ubuntu4.
  However, downgrading to the previous version 1.4.2-2ubuntu3 the network 
connection is back again and fine. If, with this version, I remove the file 
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as 
network-manager creates a new resolv.conf file.

  The newest version 1.4.2-2ubuntu4 also creates the very same kind of
  file, but no network.

  I have the latest (Gnome-shell DE) updates installed and of course all 
packages that network-manager depends on. But not the ones it only recommends 
or suggests.
  Should I have resolvconf installed? I think not, as isc-dhcp-client only 
suggests it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+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 1647133] Re: dns=dnsmasq does not work any more

[Harry]

And a little more info:

"/etc/NetworkManager/NetworkManager.conf"

[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false


"/etc/resolv.conf"

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.53

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

Title:
  dns=dnsmasq does not work any more

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Network-manager will make my network connection immediately lost after 
updating to the newest version 1.4.2-2ubuntu4.
  However, downgrading to the previous version 1.4.2-2ubuntu3 the network 
connection is back again and fine. If, with this version, I remove the file 
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as 
network-manager creates a new resolv.conf file.

  The newest version 1.4.2-2ubuntu4 also creates the very same kind of
  file, but no network.

  I have the latest (Gnome-shell DE) updates installed and of course all 
packages that network-manager depends on. But not the ones it only recommends 
or suggests.
  Should I have resolvconf installed? I think not, as isc-dhcp-client only 
suggests it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+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 1647133] Re: dns=dnsmasq does not work any more

[Harry]

Martin,

I installed the package resolvconf.
Now the command gives this:
"systemctl status resolvconf"

● resolvconf.service - Nameserver information manager
   Loaded: loaded (/lib/systemd/system/resolvconf.service; enabled; vendor 
preset: enabled)
   Active: active (exited) since Wed 2016-12-07 19:23:29 EET; 6min ago
 Docs: man:resolvconf(8)
 Main PID: 322 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
   CGroup: /system.slice/resolvconf.service

However, there is still something wrong with my network.
Certain web pages (mainly in Finland) do not work at all.

Now the link /etc/resolv.conf points to ../run/resolvconf/resolv.conf

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

Title:
  dns=dnsmasq does not work any more

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Network-manager will make my network connection immediately lost after 
updating to the newest version 1.4.2-2ubuntu4.
  However, downgrading to the previous version 1.4.2-2ubuntu3 the network 
connection is back again and fine. If, with this version, I remove the file 
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as 
network-manager creates a new resolv.conf file.

  The newest version 1.4.2-2ubuntu4 also creates the very same kind of
  file, but no network.

  I have the latest (Gnome-shell DE) updates installed and of course all 
packages that network-manager depends on. But not the ones it only recommends 
or suggests.
  Should I have resolvconf installed? I think not, as isc-dhcp-client only 
suggests it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+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 1647133] Re: dns=dnsmasq does not work any more

[Harry]

That is simply:

"Unit resolvconf.service could not be found"

I believe there is some package(s) that I do not have installed, but I
should have?

NM 1.4.2-2ubuntu4 needs something to be installed, that NM
1.4.2-2ubuntu3 did not need.

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

Title:
  dns=dnsmasq does not work any more

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Network-manager will make my network connection immediately lost after 
updating to the newest version 1.4.2-2ubuntu4.
  However, downgrading to the previous version 1.4.2-2ubuntu3 the network 
connection is back again and fine. If, with this version, I remove the file 
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as 
network-manager creates a new resolv.conf file.

  The newest version 1.4.2-2ubuntu4 also creates the very same kind of
  file, but no network.

  I have the latest (Gnome-shell DE) updates installed and of course all 
packages that network-manager depends on. But not the ones it only recommends 
or suggests.
  Should I have resolvconf installed? I think not, as isc-dhcp-client only 
suggests it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+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 1647133] Re: dns=dnsmasq does not work any more

[Harry]

Martin,

The /etc/resolv.conf in my set up is really a link.
The target is (where folder "var/run" is a link to the folder "run"):
/var/run/NetworkManager/resolv.conf

However, I upgraded NM to the version 1.4.2-2ubuuntu4 and run the following 4 
commands:
  sudo systemctl stop NetworkManager
  sudo rm /etc/resolv.conf
  sudo ln -s ../run/resolvconf/resolv.conf /etc/resolv.conf
  sudo systemctl start NetworkManager

That did not bring the network back, though. I had to downgrade again to
NM 1.4.2-2ubuntu3.

But I noticed that I do not have a folder /run/resolvconf/ in my setup,
at all.

I do have a fully updated setup, with systemd (232-7).

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

Title:
  dns=dnsmasq does not work any more

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Network-manager will make my network connection immediately lost after 
updating to the newest version 1.4.2-2ubuntu4.
  However, downgrading to the previous version 1.4.2-2ubuntu3 the network 
connection is back again and fine. If, with this version, I remove the file 
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as 
network-manager creates a new resolv.conf file.

  The newest version 1.4.2-2ubuntu4 also creates the very same kind of
  file, but no network.

  I have the latest (Gnome-shell DE) updates installed and of course all 
packages that network-manager depends on. But not the ones it only recommends 
or suggests.
  Should I have resolvconf installed? I think not, as isc-dhcp-client only 
suggests it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+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 1647133] Re: dns=dnsmasq does not work any more

[Harry]

Martin,

OK, here goes:


cat /etc/resolv.conf

# Generated by NetworkManager
search dhcp.inet.fi
nameserver 127.0.1.1


cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false


journalctl -u NetworkManager.service -u systemd-resolved.service -b > 
/tmp/nm.log

The tmp file (nm2.log) is attached.
There is one error in the log:
"Error: failed to open /run/network/ifstate"

** Attachment added: "nm2.log"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+attachment/4788208/+files/nm2.log

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

Title:
  dns=dnsmasq does not work any more

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Network-manager will make my network connection immediately lost after 
updating to the newest version 1.4.2-2ubuntu4.
  However, downgrading to the previous version 1.4.2-2ubuntu3 the network 
connection is back again and fine. If, with this version, I remove the file 
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as 
network-manager creates a new resolv.conf file.

  The newest version 1.4.2-2ubuntu4 also creates the very same kind of
  file, but no network.

  I have the latest (Gnome-shell DE) updates installed and of course all 
packages that network-manager depends on. But not the ones it only recommends 
or suggests.
  Should I have resolvconf installed? I think not, as isc-dhcp-client only 
suggests it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+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 1647133] Re: dns=dnsmasq does not work any more

[Harry]

Martin,

I removed the line "dns=dnsmasq"
from the conf file.
Then upgraded to NM 1.4.2-2ubuntu4
Rebooted and checked that dns=dnsmasq was absent from the conf file. It was.
However, the result was still the same = no network.

Downgraded back to NM 1.4.2-2ubuntu3, got the network back and fine.
Noticed, that NM had created the line "dns=dnsmasq" back.

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

Title:
  dns=dnsmasq does not work any more

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Network-manager will make my network connection immediately lost after 
updating to the newest version 1.4.2-2ubuntu4.
  However, downgrading to the previous version 1.4.2-2ubuntu3 the network 
connection is back again and fine. If, with this version, I remove the file 
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as 
network-manager creates a new resolv.conf file.

  The newest version 1.4.2-2ubuntu4 also creates the very same kind of
  file, but no network.

  I have the latest (Gnome-shell DE) updates installed and of course all 
packages that network-manager depends on. But not the ones it only recommends 
or suggests.
  Should I have resolvconf installed? I think not, as isc-dhcp-client only 
suggests it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+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 1647133] Re: Network-manager 1.4.2-2ubuntu4 brakes network connection (Zesty)

[Harry]

Martin,
here is the failed state output of
   cat /etc/resolv.conf

# Generated by NetworkManager
search dhcp.inet.fi
nameserver 127.0.1.1


So, nothing changed. And NM still generates the file /etc/resolv.conf.

I also run
  journalctl -u NetworkManager.service -u systemd-resolved.service -b > 
/tmp/nm.log

The file nm.log is attached.

** Attachment added: "NM.log"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+attachment/4787689/+files/nm.log

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

Title:
  Network-manager 1.4.2-2ubuntu4 brakes network connection (Zesty)

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Network-manager will make my network connection immediately lost after 
updating to the newest version 1.4.2-2ubuntu4.
  However, downgrading to the previous version 1.4.2-2ubuntu3 the network 
connection is back again and fine. If, with this version, I remove the file 
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as 
network-manager creates a new resolv.conf file.

  The newest version 1.4.2-2ubuntu4 also creates the very same kind of
  file, but no network.

  I have the latest (Gnome-shell DE) updates installed and of course all 
packages that network-manager depends on. But not the ones it only recommends 
or suggests.
  Should I have resolvconf installed? I think not, as isc-dhcp-client only 
suggests it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+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 1647133] Re: Network-manager 1.4.2-2ubuntu4 brakes network connection (Zesty)

[Harry]

Sebastien,
could you please give me instructions on how to install systemd-resolved?
I do have a fully working Gnome-shell DE with systemd as pid1 and no upstart 
packages installed.
The network is working fine if I use network-manager (1.4.2-2ubuntu3), but not 
anymore if I upgrade to the version 1.4.2-2ubuntu4.
So something did happen there.

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

Title:
  Network-manager 1.4.2-2ubuntu4 brakes network connection (Zesty)

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Network-manager will make my network connection immediately lost after 
updating to the newest version 1.4.2-2ubuntu4.
  However, downgrading to the previous version 1.4.2-2ubuntu3 the network 
connection is back again and fine. If, with this version, I remove the file 
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as 
network-manager creates a new resolv.conf file.

  The newest version 1.4.2-2ubuntu4 also creates the very same kind of
  file, but no network.

  I have the latest (Gnome-shell DE) updates installed and of course all 
packages that network-manager depends on. But not the ones it only recommends 
or suggests.
  Should I have resolvconf installed? I think not, as isc-dhcp-client only 
suggests it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+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 1647133] Re: Network-manager 1.4.2-2ubuntu4 brakes network connection (Zesty)

[Harry]

Martin, here is the contents of /etc/NetworkManager/NetworkManager.conf
(with the version 1.4.2-2ubuntu3) installed:

[main]
plugins=ifupdown,keyfile
dns=dnsmasq

[ifupdown]
managed=false


And here is the output of
  cat /etc/resolv.conf

# Generated by NetworkManager
search dhcp.inet.fi
nameserver 127.0.1.1


I do next the same with the version 1.4.2-2ubuntu4 (failed state).

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

Title:
  Network-manager 1.4.2-2ubuntu4 brakes network connection (Zesty)

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Network-manager will make my network connection immediately lost after 
updating to the newest version 1.4.2-2ubuntu4.
  However, downgrading to the previous version 1.4.2-2ubuntu3 the network 
connection is back again and fine. If, with this version, I remove the file 
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as 
network-manager creates a new resolv.conf file.

  The newest version 1.4.2-2ubuntu4 also creates the very same kind of
  file, but no network.

  I have the latest (Gnome-shell DE) updates installed and of course all 
packages that network-manager depends on. But not the ones it only recommends 
or suggests.
  Should I have resolvconf installed? I think not, as isc-dhcp-client only 
suggests it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+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 1647133] [NEW] Network-manager 1.4.2-2ubuntu4 brakes network connection (Zesty)

[Harry]

Public bug reported:

Network-manager will make my network connection immediately lost after updating 
to the newest version 1.4.2-2ubuntu4.
However, downgrading to the previous version 1.4.2-2ubuntu3 the network 
connection is back again and fine. If, with this version, I remove the file 
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as 
network-manager creates a new resolv.conf file.

The newest version 1.4.2-2ubuntu4 also creates the very same kind of
file, but no network.

I have the latest (Gnome-shell DE) updates installed and of course all packages 
that network-manager depends on. But not the ones it only recommends or 
suggests.
Should I have resolvconf installed? I think not, as isc-dhcp-client only 
suggests it.

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

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

Title:
  Network-manager 1.4.2-2ubuntu4 brakes network connection (Zesty)

Status in network-manager package in Ubuntu:
  New

Bug description:
  Network-manager will make my network connection immediately lost after 
updating to the newest version 1.4.2-2ubuntu4.
  However, downgrading to the previous version 1.4.2-2ubuntu3 the network 
connection is back again and fine. If, with this version, I remove the file 
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as 
network-manager creates a new resolv.conf file.

  The newest version 1.4.2-2ubuntu4 also creates the very same kind of
  file, but no network.

  I have the latest (Gnome-shell DE) updates installed and of course all 
packages that network-manager depends on. But not the ones it only recommends 
or suggests.
  Should I have resolvconf installed? I think not, as isc-dhcp-client only 
suggests it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+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 1638836] Re: resolv.conf for resolved stub server should have a comment how to see the actual servers

[Harry]

Martin,

Please note, that in my setup, the network is lost immediately after
rebooting with the new network-manager (1.4.2-2ubuntu4). Then,
downgrading back to version 1.4.2.-2ubuntu3, and rebooting, I get
network back.

In both of these versions, the network-manager creates the same kind of
file /etc/resol.vconf.

I only use a cable network. I do not have the package resolvconf
installed, as no other package depends on it (isc-dhcp-client merely
suggests it).

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

Title:
  resolv.conf for resolved stub server should have a comment how to see
  the actual servers

Status in network-manager package in Ubuntu:
  Fix Released
Status in resolvconf package in Ubuntu:
  Fix Released

Bug description:
  resolv.conf currently just has

nameserver 127.0.0.53

  with resolved (its local stub resolver). We should have an extra
  comment on top of that that says

# systemd-resolved stub resolver; run "systemd-resolve --status" to
  see the actual name servers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638836/+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 1509711] Re: Screen temporarily not locked when coming out of suspend

[Harry P]

Since the upgrade to Xenial, I haven't seen this bug.   Unless it
affects any other LTS editions, I guess it's ok to close?

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

Title:
  Screen temporarily not locked when coming out of suspend

Status in gnome-screensaver package in Ubuntu:
  Triaged

Bug description:
  When I resume my notebook after suspend, the desktop with all open
  applications is displayed for about 1-2 seconds until the password
  prompt finally is shown. This happens every time when resuming in
  Ubuntu 15.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct 24 22:19:07 2015
  InstallationDate: Installed on 2015-04-27 (180 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen not locked when coming out of suspend/hibernate
  UpgradeStatus: Upgraded to wily on 2015-10-11 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1509711/+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 1566182] Re: Nautilus_3.19.90 crashes when using USB memory card

[Harry]

** Summary changed:

- Nautilus crashes when using USB memory card
+ Nautilus_3.19.90 crashes when using USB memory card

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

Title:
  Nautilus_3.19.90 crashes when using USB memory card

Status in nautilus package in Ubuntu:
  New

Bug description:
  Gnome 3.20
  Gnome3 Staging PPA
  Xenial development release

  Nautilus (3.19.90) crashes immediately when I click the memory card address 
(connected via USB) on the left panel (main window).
  The only case where Nautilus will not crash is if I use an empty and newly 
formatted memory card (SDHC or micro-SDHC).

  This happens also if I have an official Xenial setup with all the
  latest updates and only the PPA version of Nautilus_3.19.90 +
  GTK+3.0_3.20.2 is installed.

  What is odd, is that also the stable official Nautilus_3.18.4is3.14.3
  crashes if only the PPA version of gnome-shell_3.20.0 + mutter_3.20.0
  + gnome-session_3.20.0 + GTK+3.0_3.20.2 are installed on the otherwise
  official Xenial setup.

  However, if any other, or all other packages from the PPA (except
  Nautilus and gnome-shell - mutter) are installed on the otherwise
  offial Xenial setup, the official Nautilus works just fine.

  And of course with only the official Xenial setup, the official
  Nautilus is OK.

  So, it seems something is wrong with both nautilus_3.19.90 and gnome-
  shell_3.20.0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1566182/+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 1566182] [NEW] Nautilus_3.19.90 crashes when using USB memory card

[Harry]

Public bug reported:

Gnome 3.20
Gnome3 Staging PPA
Xenial development release

Nautilus (3.19.90) crashes immediately when I click the memory card address 
(connected via USB) on the left panel (main window).
The only case where Nautilus will not crash is if I use an empty and newly 
formatted memory card (SDHC or micro-SDHC).

This happens also if I have an official Xenial setup with all the latest
updates and only the PPA version of Nautilus_3.19.90 + GTK+3.0_3.20.2 is
installed.

What is odd, is that also the stable official Nautilus_3.18.4is3.14.3
crashes if only the PPA version of gnome-shell_3.20.0 + mutter_3.20.0 +
gnome-session_3.20.0 + GTK+3.0_3.20.2 are installed on the otherwise
official Xenial setup.

However, if any other, or all other packages from the PPA (except
Nautilus and gnome-shell - mutter) are installed on the otherwise offial
Xenial setup, the official Nautilus works just fine.

And of course with only the official Xenial setup, the official Nautilus
is OK.

So, it seems something is wrong with both nautilus_3.19.90 and gnome-
shell_3.20.0.

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


** Tags: gnome3 ppa staging

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

Title:
  Nautilus_3.19.90 crashes when using USB memory card

Status in nautilus package in Ubuntu:
  New

Bug description:
  Gnome 3.20
  Gnome3 Staging PPA
  Xenial development release

  Nautilus (3.19.90) crashes immediately when I click the memory card address 
(connected via USB) on the left panel (main window).
  The only case where Nautilus will not crash is if I use an empty and newly 
formatted memory card (SDHC or micro-SDHC).

  This happens also if I have an official Xenial setup with all the
  latest updates and only the PPA version of Nautilus_3.19.90 +
  GTK+3.0_3.20.2 is installed.

  What is odd, is that also the stable official Nautilus_3.18.4is3.14.3
  crashes if only the PPA version of gnome-shell_3.20.0 + mutter_3.20.0
  + gnome-session_3.20.0 + GTK+3.0_3.20.2 are installed on the otherwise
  official Xenial setup.

  However, if any other, or all other packages from the PPA (except
  Nautilus and gnome-shell - mutter) are installed on the otherwise
  offial Xenial setup, the official Nautilus works just fine.

  And of course with only the official Xenial setup, the official
  Nautilus is OK.

  So, it seems something is wrong with both nautilus_3.19.90 and gnome-
  shell_3.20.0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1566182/+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 1469929] Re: error install mono-runtime:armhf on arm64

[Harry May]

the problem initially described still exists:
Installation not possible.


** Changed in: mono (Ubuntu)
   Status: Expired => New

** Changed in: mono (Ubuntu)
 Assignee: (unassigned) => Harry May (harry4516)

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

Title:
  error install mono-runtime:armhf on arm64

Status in mono package in Ubuntu:
  Confirmed

Bug description:
  sudo dpkg --add-architecture armhf
  sudo apt-get update
  sudo apt-get install mono-runtime:armhf

  
  kylin@kylin:~$ sudo apt-get install mono-runtime
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   mono-runtime:armhf : Depends: mono-runtime-sgen:armhf (= 
3.2.8+dfsg-4ubuntu2.1) but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.
  kylin@kylin:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mono/+bug/1469929/+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 1493888] Re: FGLRX incompatible with gcc 5

[Harry Plumley]

I'm seeing the exact same problem as Phillip Gemmell in post #243.

When trying to update fglrx with the wily-proposed versions I get the
message "Release 'wily-proposed' for 'flgrx-*' was not found".

This is all happening on a fresh install of 15.10.

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

Title:
  FGLRX incompatible with gcc 5

Status in Release Notes for Ubuntu:
  Fix Released
Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in fglrx-installer source package in Wily:
  Fix Released
Status in fglrx-installer-updates source package in Wily:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  The fglrx driver is not compatible with gcc 5.x. This causes the
  kernel module to crash on initialisation. As a result, users will boot
  into a black screen, as X will fail (except on Intel+AMD hybrid
  systems, where intel is used).

  [Test Case]
  1. Either install (or upgrade to) Ubuntu 15.10 and fglrx
  2. Reboot
  3. Check the display, and the output of the "dmesg | grep fglrx" command (to 
see the actual crash)

  Expected results: the system should be able to start X correctly.

  Actual results:
  The kernel module fails and X doesn't start.

  [Regression Potential]
  Low. Forcing fglrx to use gcc 4.9 is only a temporary workaround, and will be 
replaced with the proper fix once AMD makes it available.


  __

  With a R9 280 and FGLRX on ubuntu 15.10 the graphics lock up. I am
  able to SSH into the machine. I booted the older kernel
  (4.1.0-3-generic) and it works with FGLRX. After purging FGLRX and
  using xserver-xorg-video-radeon I am able to get the graphics working,
  but even it has issues with my display port (The DVI ports are working
  correctly).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: fglrx (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  Date: Wed Sep  9 09:29:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-01-07 (1705 days ago)
  InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fglrx-installer
  UpgradeStatus: Upgraded to wily on 2015-08-18 (21 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1493888/+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 1510813] Re: Update to 3.18.1

[Harry]

Tim, you wrote:
"So basically unless I am missing something, there is nothing to fix here?"

Maybe so,
I only wrote comments here because there is a clear difference between these 
two:
1) gnome desktop3_3.18.0-0ubuntu1~wily2 (Gnome3 Staging PPA)
2) gnome-desktop3_3.18.1-1ubuntu1 (xenial-proposed-new)

I cannot install nro 2 above, because that would force to remove 
libgnome-dektop-3-10.
But I have installed nro 1 above with no issues.

So, if nro 2 would be replaced with nro 1 in xenial proposed, it would be 
installable.
Then eog and mutter could be easily built against libgnome-desktop-3-12.
After this libgnome-desktop-3-10 could be removed.

To me, having nro 2 in xenial-proposed with no possibiliites to install it and 
eog + mutter with no possibiliites to build against libgnome-desktop-3-12 
(because it is not installable) is a locked-in situation.
Nothing to fix? Really?

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

Title:
  Update to 3.18.1

Status in gnome-desktop3 package in Ubuntu:
  Fix Committed

Bug description:
  Please merge 3.18.1 from debian 
  Debdiff attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1510813/+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 1509711] Re: Screen temporarily not locked when coming out of suspend

[Harry P]

I reported the dupe at https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1508148.  This bug has been around for a couple of releases
I'd say, definitely as far back as 14.04...

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

Title:
  Screen temporarily not locked when coming out of suspend

Status in gnome-screensaver package in Ubuntu:
  Triaged

Bug description:
  When I resume my notebook after suspend, the desktop with all open
  applications is displayed for about 1-2 seconds until the password
  prompt finally is shown. This happens every time when resuming in
  Ubuntu 15.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct 24 22:19:07 2015
  InstallationDate: Installed on 2015-04-27 (180 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen not locked when coming out of suspend/hibernate
  UpgradeStatus: Upgraded to wily on 2015-10-11 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1509711/+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 1510813] Re: Update to 3.18.1

[Harry]

OK
Thanks Tim.

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

Title:
  Update to 3.18.1

Status in gnome-desktop3 package in Ubuntu:
  Fix Committed

Bug description:
  Please merge 3.18.1 from debian 
  Debdiff attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1510813/+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 1510813] Re: Update to 3.18.1

[Harry]

Tim,

I suppose you have also tried to install the gnome-desktop3 
(3.18.0-0ubuntu1~wily2) from Gnome3 Staging PPA.
Those packages are installable and not in contradiction with 
libgnome-desktop-3-10.
I use that PPA and all is well with the gnome-desktop 3.12.
Also mutter has been built against libgnome-desktop-3-12 there.

To disable proposed is not a solution. I know very well what I am doing.
Plus, the gnome-desktop (3.18.1-1ubuntu1) is not in proposed yet.
It is still marked as "new" in here:
https://launchpad.net/ubuntu/+source/gnome-desktop3/3.18.1-1ubuntu1

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

Title:
  Update to 3.18.1

Status in gnome-desktop3 package in Ubuntu:
  Fix Committed

Bug description:
  Please merge 3.18.1 from debian 
  Debdiff attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1510813/+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 1510819] [NEW] Xenial: evince (3.18.1-1ubuntu1) depends on gnome-icon-theme-symbolic while gnome-shell (3.18.1-1ububtu1) depends on adwaita-icon-theme

[Harry]

Public bug reported:

In the DE gnome-shell there has been a switch from gnome-icon-theme-
symbolic to adwaita-icon-theme.

However, the new evince (3.18.1-1ubuntu1) in xenial depends now on 
gnome-icon-theme-symbolic while the new gnome-shell (3.18.1-1ububtu1) in xenial 
depends correctly on adwaita-icon-theme.
Also the evince in wily (3.16.1-0ubuntu1) depends correctly on 
adwaita-icon-theme.

So, the evince 3.18.1 should be rebuilt against adwaita-icon-theme.
This would prevent evince from pulling in gnome-icon-theme and 
humanity-icon-theme.

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


** Tags: xenial

** Summary changed:

- Xenial: Evince (3.18.1-1ubuntu1) depends on gnome-icon-theme-symbolic while 
gnome-shell (3.18.1-1ububtu1) depends on adwaita-icon-theme
+ Xenial: evince (3.18.1-1ubuntu1) depends on gnome-icon-theme-symbolic while 
gnome-shell (3.18.1-1ububtu1) depends on adwaita-icon-theme

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

Title:
  Xenial: evince (3.18.1-1ubuntu1) depends on gnome-icon-theme-symbolic
  while gnome-shell (3.18.1-1ububtu1) depends on adwaita-icon-theme

Status in evince package in Ubuntu:
  New

Bug description:
  In the DE gnome-shell there has been a switch from gnome-icon-theme-
  symbolic to adwaita-icon-theme.

  However, the new evince (3.18.1-1ubuntu1) in xenial depends now on 
gnome-icon-theme-symbolic while the new gnome-shell (3.18.1-1ububtu1) in xenial 
depends correctly on adwaita-icon-theme.
  Also the evince in wily (3.16.1-0ubuntu1) depends correctly on 
adwaita-icon-theme.

  So, the evince 3.18.1 should be rebuilt against adwaita-icon-theme.
  This would prevent evince from pulling in gnome-icon-theme and 
humanity-icon-theme.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1510819/+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 1510819] Re: Xenial: evince (3.18.1-1ubuntu1) depends on gnome-icon-theme-symbolic while gnome-shell (3.18.1-1ububtu1) depends on adwaita-icon-theme

[Harry]

This is from the gnome-shell 3.18.1-1ubuntu1:
   + drop depend on gnome-icon-theme-symbolic
   -  debian/rules: switch to adwaita-icon-theme

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

Title:
  Xenial: evince (3.18.1-1ubuntu1) depends on gnome-icon-theme-symbolic
  while gnome-shell (3.18.1-1ububtu1) depends on adwaita-icon-theme

Status in evince package in Ubuntu:
  New

Bug description:
  In the DE gnome-shell there has been a switch from gnome-icon-theme-
  symbolic to adwaita-icon-theme.

  However, the new evince (3.18.1-1ubuntu1) in xenial depends now on 
gnome-icon-theme-symbolic while the new gnome-shell (3.18.1-1ububtu1) in xenial 
depends correctly on adwaita-icon-theme.
  Also the evince in wily (3.16.1-0ubuntu1) depends correctly on 
adwaita-icon-theme.

  So, the evince 3.18.1 should be rebuilt against adwaita-icon-theme.
  This would prevent evince from pulling in gnome-icon-theme and 
humanity-icon-theme.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1510819/+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 1510813] Re: Update to 3.18.1

[Harry]

There is an issue, which must be solved.

The package libgnome-desktop-3-12 forces to remove libgnome-desktop-3-10.
This in turn causes eog and libmutter0g to be removed as these have been built 
against libgnome-desktop-3-10.

To solve this the libgnome-desktop-3-12 must be installable alongside the 
libgnome-desktop-3-10.
The eog and mutter can be rebuilt against libgnome-desktop-3-12.

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

Title:
  Update to 3.18.1

Status in gnome-desktop3 package in Ubuntu:
  Fix Committed

Bug description:
  Please merge 3.18.1 from debian 
  Debdiff attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1510813/+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 1477403] [NEW] Gegl 0.3.0-2ubuntu2 depends on libgegl-dev

[Harry]

Public bug reported:

The newest gegl (0.3.0-2ubuntu2) in wily-proposed depends on libgegl-dev, 
unlike the older version gegl 0.2.0 does.
Libgegl-dev pulls in a lot of other unnecessary packages that Gimp does not 
need.

So, as Gimp is going to be built against gegl 0.3.0, this bug needs to
be corrected.

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


** Tags: wily

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

Title:
  Gegl 0.3.0-2ubuntu2 depends on libgegl-dev

Status in gegl package in Ubuntu:
  New

Bug description:
  The newest gegl (0.3.0-2ubuntu2) in wily-proposed depends on libgegl-dev, 
unlike the older version gegl 0.2.0 does.
  Libgegl-dev pulls in a lot of other unnecessary packages that Gimp does not 
need.

  So, as Gimp is going to be built against gegl 0.3.0, this bug needs to
  be corrected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gegl/+bug/1477403/+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 1477403] Re: Gegl 0.3.0-2ubuntu2 depends on libgegl-dev

[Harry]

To be more specific, it is libgegl-0.3-0, that depends on libgegl-dev.


** Description changed:

- The newest gegl (0.3.0-2ubuntu2) in wily-proposed depends on libgegl-dev, 
unlike the older version gegl 0.2.0 does.
+ The newest gegl (libgegl-0.3-0) in wily-proposed depends on libgegl-dev, 
unlike the older version gegl 0.2.0 does.
  Libgegl-dev pulls in a lot of other unnecessary packages that Gimp does not 
need.
  
  So, as Gimp is going to be built against gegl 0.3.0, this bug needs to
  be corrected.

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

Title:
  Gegl 0.3.0-2ubuntu2 depends on libgegl-dev

Status in gegl package in Ubuntu:
  New

Bug description:
  The newest gegl (libgegl-0.3-0) in wily-proposed depends on libgegl-dev, 
unlike the older version gegl 0.2.0 does.
  Libgegl-dev pulls in a lot of other unnecessary packages that Gimp does not 
need.

  So, as Gimp is going to be built against gegl 0.3.0, this bug needs to
  be corrected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gegl/+bug/1477403/+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 445084] Re: click-to-focus window is too sensitive

[Harry Coin]

Still happening in Trusty 14.04 LTS.   Renders gnome-terminal unusable.
Click on a tab and 75% of the time you get a new window.  xubuntu nvidia
mutltimonitor setup.  Changed the 'drag detection' in the mouse settings
to be an insensitive as possible, no change.  Too bad really, I liked
the feature set otherwise.

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

Title:
  click-to-focus window is too sensitive

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnome-terminal

  in jaunty, when I click a background gnome-terminal window to bring it
  into focus, I frequently end up with text selected in that terminal.
  This clears my (selection) clipboard and severely inhibits the
  clipboard functionality.

  Prior to jaunty this was not a problem.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: nvidia
  Package: gnome-terminal 2.26.0-0ubuntu2.1
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  Uname: Linux 2.6.28-15-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/445084/+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 1387513] [NEW] nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

[harry nelsen]

Public bug reported:

I don't know anything more than the error system reported.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8
Architecture: i386
DKMSKernelVersion: 3.16.0-24-generic
Date: Thu Oct 30 00:38:14 2014
InstallationDate: Installed on 2010-05-22 (1622 days ago)
InstallationMedia: Ubuntu-Netbook 10.04 Lucid Lynx - Release i386 (20100429.4)
PackageVersion: 331.89-0ubuntu5
SourcePackage: nvidia-graphics-drivers-331
Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
UpgradeStatus: Upgraded to utopic on 2014-10-28 (1 days ago)
modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

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


** Tags: apport-package i386 utopic

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

Title:
  nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  I don't know anything more than the error system reported.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  DKMSKernelVersion: 3.16.0-24-generic
  Date: Thu Oct 30 00:38:14 2014
  InstallationDate: Installed on 2010-05-22 (1622 days ago)
  InstallationMedia: Ubuntu-Netbook 10.04 Lucid Lynx - Release i386 
(20100429.4)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
  UpgradeStatus: Upgraded to utopic on 2014-10-28 (1 days ago)
  modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1387513/+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 1360803] [NEW] [Satellite P300, Conexant CX20561 (Hermosa), Black SPDIF Out, Front, Docking station] No sound at all

[Harry Verburg]

Public bug reported:

sounds fails regulary.

And i can't seems to install Citrix Reciever correctly  on Ubuntu 14.04
LTS

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic i686
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  harry  2071 F pulseaudio
CurrentDesktop: Unity
Date: Sun Aug 24 13:05:39 2014
InstallationDate: Installed on 2014-07-11 (43 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=nl_NL
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
Symptom_Card: Intern geluid - HDA Intel
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  harry  2071 F pulseaudio
Symptom_Jack: Black SPDIF Out, Front, Docking station
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [Satellite P300, Conexant CX20561 (Hermosa), Black SPDIF Out, Front, 
Docking station] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/05/2009
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V4.20
dmi.board.name: Satellite P300
dmi.board.vendor: TOSHIBA
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnTOSHIBA:bvrV4.20:bd01/05/2009:svnTOSHIBA:pnSatelliteP300:pvrPSPC0E-008005DU:rvnTOSHIBA:rnSatelliteP300:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: Satellite P300
dmi.product.version: PSPC0E-008005DU
dmi.sys.vendor: TOSHIBA

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 trusty

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

Title:
  [Satellite P300, Conexant CX20561 (Hermosa), Black SPDIF Out, Front,
  Docking station] No sound at all

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  sounds fails regulary.

  And i can't seems to install Citrix Reciever correctly  on Ubuntu
  14.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic i686
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  harry  2071 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Aug 24 13:05:39 2014
  InstallationDate: Installed on 2014-07-11 (43 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=nl_NL
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Intern geluid - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  harry  2071 F pulseaudio
  Symptom_Jack: Black SPDIF Out, Front, Docking station
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Satellite P300, Conexant CX20561 (Hermosa), Black SPDIF Out, Front, 
Docking station] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/05/2009
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V4.20
  dmi.board.name: Satellite P300
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV4.20:bd01/05/2009:svnTOSHIBA:pnSatelliteP300:pvrPSPC0E-008005DU:rvnTOSHIBA:rnSatelliteP300:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: Satellite P300
  dmi.product.version: PSPC0E-008005DU
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1360803/+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 1343911] Re: gdm-session-worker crashed with SIGABRT in g_assertion_message()

[Harry]

Right Dino, that is fine.
BTW. The newer systemd (208-6ubuntu1) Serge built recently failed (build 
failure).

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

Title:
  gdm-session-worker crashed with SIGABRT in g_assertion_message()

Status in “gdm” package in Ubuntu:
  Confirmed

Bug description:
  The latest cgmanager installation pushed by systemd-shim has broken
  the boot process:

  https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1342586

  if the report above have solved an issue, systemd-boot is still fully
  broken: need to use back upstart

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: gdm 3.10.0.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5
  Uname: Linux 3.16.0-4-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: i386
  Date: Thu Jul 17 15:09:39 2014
  ExecutablePath: /usr/lib/gdm/gdm-session-worker
  ProcCmdline: gdm-session-worker\ [pam/gdm-launch-environment]
  Signal: 6
  SourcePackage: gdm
  StacktraceTop:
   g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libaccountsservice.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: gdm-session-worker crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1343911/+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 1343911] Re: gdm-session-worker crashed with SIGABRT in g_assertion_message()

[Harry]

This bug seems to resemble the bug LP: #1343802.

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

Title:
  gdm-session-worker crashed with SIGABRT in g_assertion_message()

Status in “gdm” package in Ubuntu:
  New

Bug description:
  The latest cgmanager installation pushed by systemd-shim has broken
  the boot process:

  https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1342586

  if the report above have solved an issue, systemd-boot is still fully
  broken: need to use back upstart

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: gdm 3.10.0.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5
  Uname: Linux 3.16.0-4-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: i386
  Date: Thu Jul 17 15:09:39 2014
  ExecutablePath: /usr/lib/gdm/gdm-session-worker
  ProcCmdline: gdm-session-worker\ [pam/gdm-launch-environment]
  Signal: 6
  SourcePackage: gdm
  StacktraceTop:
   g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libaccountsservice.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: gdm-session-worker crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1343911/+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 1334998] [NEW] When using Super+L keys autohide not working properly

[harry]

Public bug reported:

When using the super+l keys to lock the screen, the unity panel gets
stuck. This happens whenever the user first clicks on the super key and
then the L key.  Clicking simutaniously works as expected.

The issue was also reported on Ask Ubuntu:
http://askubuntu.com/questions/459585/launcher-auto-hide-not-working-
ubuntu-14-04/469732?noredirect=1#comment652314_469732

There is a workaround (the user has to double tap the super key)
however, this is one of those papercuts that gets rather annoying over
time.

I would expect the system to be a little more tolerant in terms of the
sequnce of keys pressed. If I first click on the super key and then the
L key, the panel will not be locked when I log back in.

===
Description:Ubuntu 14.04 LTS
Release:14.04
===
unity:
  Installed: 7.2.1+14.04.20140513-0ubuntu2
  Candidate: 7.2.1+14.04.20140513-0ubuntu2
  Version table:
 *** 7.2.1+14.04.20140513-0ubuntu2 0
500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
100 /var/lib/dpkg/status
 7.2.0+14.04.20140423-0ubuntu1.2 0
500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
 7.2.0+14.04.20140416-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

===
Screenshot: http://i.imgur.com/e3AePQ8.png

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.1+14.04.20140513-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Fri Jun 27 09:23:52 2014
InstallationDate: Installed on 2014-03-16 (103 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140313)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 lockscreen trusty unity

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

Title:
  When using Super+L keys autohide not working properly

Status in “unity” package in Ubuntu:
  New

Bug description:
  When using the super+l keys to lock the screen, the unity panel gets
  stuck. This happens whenever the user first clicks on the super key
  and then the L key.  Clicking simutaniously works as expected.

  The issue was also reported on Ask Ubuntu:
  http://askubuntu.com/questions/459585/launcher-auto-hide-not-working-
  ubuntu-14-04/469732?noredirect=1#comment652314_469732

  There is a workaround (the user has to double tap the super key)
  however, this is one of those papercuts that gets rather annoying over
  time.

  I would expect the system to be a little more tolerant in terms of the
  sequnce of keys pressed. If I first click on the super key and then
  the L key, the panel will not be locked when I log back in.

  ===
  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  ===
  unity:
Installed: 7.2.1+14.04.20140513-0ubuntu2
Candidate: 7.2.1+14.04.20140513-0ubuntu2
Version table:
   *** 7.2.1+14.04.20140513-0ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   7.2.0+14.04.20140423-0ubuntu1.2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   7.2.0+14.04.20140416-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  ===
  Screenshot: http://i.imgur.com/e3AePQ8.png

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.1+14.04.20140513-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Jun 27 09:23:52 2014
  InstallationDate: Installed on 2014-03-16 (103 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140313)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1334998/+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 1328586] Re: Synaptic is reading state information for a minute or so

[Harry]

Right, this seems to be fixed now for synaptic as well.

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

Title:
  Synaptic is reading state information for a minute or so

Status in GNOME Shell:
  Fix Released
Status in “at-spi2-core” package in Ubuntu:
  Invalid
Status in “gnome-shell” package in Ubuntu:
  Fix Released

Bug description:
  When starting synaptic I get the authentication window - OK.
  Then synaptic main window opens, but the text content stays about one minute 
unfocused and reading state information.

  This bug appeared right after upgrading gnome-shell 3.10 to the newest 
version 3.12.2-1ubuntu2 and mutter to the version 3.12.2-1ubuntu1.
  Downgrading back to the 3.10 versions solves the issue immediately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1328586/+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 1290002] Re: Volume wheel (Dell keyboard) not adjusting Ubuntu volume properly after update

[Harry P]

Is this issue ever going to be fixed?

Or no one cares anymore about older Ubuntu versions? 12.04 was supposed
to be LTS!

These issues should have not been neglected, nor allowed to happen in
the first place.

Before that specific update, which i suspect is this one: xkb-data:amd64
(2.5-1ubuntu1.3, 2.5-1ubuntu1.5),

everything on my keyboard was working flawlessly. I cannot use the
quickbuttons around the volume wheel or the volume wheel at all. This
should be an easy fix for the developers.

Please look into it as it is very annoying.

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

Title:
  Volume wheel (Dell keyboard) not adjusting Ubuntu volume properly
  after update

Status in “xkeyboard-config” package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 12.04.4 LTS
  Release:  12.04

  I run update on Ubuntu 12.04 64Bit on 2014-03-07, and after restarting
  my pc, the keyboard volume wheel doesn't adjust the volume in Ubuntu
  OS anymore.

  Keyboard is Dell X295D Multimedia USB Keyboard (Greek)

  I can confirm that the volume wheel is not malfunctioned because the
  volume wheel trigger is detectable in
  SettingsKeyboardShortcutsSound and MediaVolume Down/Volume Up, and
  it is also working in other programs (XBMC for Ubuntu).

  The packages included in the update are:
  Install: 
  linux-image-3.2.0-60-generic:amd64 (3.2.0-60.91),
  linux-headers-3.2.0-60:amd64 (3.2.0-60.91),
  linux-headers-3.2.0-60-generic:amd64 (3.2.0-60.91)
  Upgrade: 
  libmagickcore4:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), 
  gnome-settings-daemon:amd64 (3.4.2-0ubuntu0.6.4, 3.4.2-0ubuntu0.6.5), 
  icedtea-netx:amd64 (1.2.3-0ubuntu0.12.04.3, 1.2.3-0ubuntu0.12.04.4), 
  libmagickwand4:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), 
  linux-generic:amd64 (3.2.0.59.70, 3.2.0.60.71), 
  libmagickcore4-extra:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), 
  libgnutls26:amd64 (2.12.14-5ubuntu3.6, 2.12.14-5ubuntu3.7), 
  libgnutls26:i386 (2.12.14-5ubuntu3.6, 2.12.14-5ubuntu3.7), 
  xkb-data:amd64 (2.5-1ubuntu1.3, 2.5-1ubuntu1.5), 
  icedtea-netx-common:amd64 (1.2.3-0ubuntu0.12.04.3, 1.2.3-0ubuntu0.12.04.4), 
  icedtea-6-plugin:amd64 (1.2.3-0ubuntu0.12.04.3, 1.2.3-0ubuntu0.12.04.4), 
  imagemagick-common:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), 
  linux-headers-generic:amd64 (3.2.0.59.70, 3.2.0.60.71), 
  linux-image-generic:amd64 (3.2.0.59.70, 3.2.0.60.71), 
  libdvdnav4:amd64 (4.2.0-1, 4.2.0-1ubuntu0.1), 
  imagemagick:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), 
  linux-libc-dev:amd64 (3.2.0-59.90, 3.2.0-60.91), 
  perlmagick:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1290002/+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 1316873] [NEW] Left mouse button stops working

[Harry P]

Public bug reported:

This  problem has plagued me for a few years across different laptops
and Ubuntu versions. Current I am experiencing this on a Dell Inspiron
15z running Ubuntu 14.04 LTS.

It typically starts after I have used the chat or call feature in gmail,
by clicking on the phone icon in the left chat margin. I am a Firefox
user and have not tested this with chrome etc. It has not happened if i
dont install google-talkplugin so it is quite possible that the plugin
is to blame.

Symptom
===
The left mouse button on all attached mice - USB , Trackpad and touch - will 
not do anything  however the right mouse button continues to work.  This 
happens to all applications and also to the desktop. The keyboard continues to 
function as normal.

When this occurs , my solution is to Alt-F4 close all windows and log
out of the X session. When I re-login the left mouse button works as
normal.


This is an irritant and work disruptor as I have to save all browser and 
desktop applications to  safe state before I logout to reset the mouse. I will 
appreciate any soltion or workaround.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue May  6 21:41:29 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:058f]
InstallationDate: Installed on 2014-04-17 (19 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
MachineType: Dell Inc. Inspiron 5523
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=f5004b03-b37f-4733-88a8-51c6f3bd0a4d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/18/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0GKGJG
dmi.board.vendor: Dell Inc.
dmi.board.version: A05
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/18/2013:svnDellInc.:pnInspiron5523:pvrNotSpecified:rvnDellInc.:rn0GKGJG:rvrA05:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 5523
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Tue May  6 21:20:40 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5558 
 vendor CMN
xserver.version: 2:1.15.1-0ubuntu2

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


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

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

Title:
  Left mouse button stops working

Status in “xorg” package in Ubuntu:
  New

Bug description:
  This  problem has plagued me for a few years across different laptops
  and Ubuntu versions. Current I am experiencing this on a Dell Inspiron
  15z running Ubuntu 14.04 LTS.

  It typically starts after I have used the chat or call feature in
  gmail, by clicking on the phone icon in the left chat margin. I am a
  Firefox user and have not tested this with chrome etc. It has not
  happened if i dont install google-talkplugin so it is quite possible
  that the plugin is to blame.

  Symptom
  ===
  The left mouse button on all attached mice - USB , Trackpad and touch - will 
not do anything  however the right mouse button continues to work.  This 
happens to all applications and also to the desktop. The keyboard continues to 
function as normal.

  When this occurs , my solution is to Alt-F4 close all windows and log
  out of the X session. When I 

[Desktop-packages] [Bug 1261916] Re: Missing letters in spice client session with KVM guest

[Harry Coin]

This problem happens 'out of the box' using nothing more xubuntu trusty
iso installed on two systems, one running virt-manager and the other
hosting vms.  So far, so good.

To reproduce:  try a standard xubuntu amd64 install on a vm guest using
qxl as the video driver and spice as the display system.  Somewhere
during the install questions to do with disk use, every second or thid
letter randomly just disappears.   Removing firefo  a few dozen
times,.   Removing kpart redisplayed a few dozen times.  The 'Thank you
we'd love to hear about your experiences' screen has title  In ta.

Trusty / qxl / spice on vm guests is compeltely unusable.

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

Title:
  Missing letters in spice client session with KVM guest

Status in “xserver-xorg-video-qxl” package in Ubuntu:
  Incomplete
Status in “xserver-xorg-video-qxl” package in Fedora:
  Unknown

Bug description:
  Host: Xubuntu 13.04
  Guest: Xubuntu 14.04 with qxl graphics

  When connecting to a KVM guest via Spice client characters are not
  displayed (in graphical mode), to such extent that messages become
  unreadable/guest becomes unusable.

  This bug was reported and kind of resolved for Red Hat/Fedora: 
https://bugzilla.redhat.com/show_bug.cgi?id=974198
  The mentioned workaround to add kernel parameter nomodeset worked for me up 
to now.

  Proposed resolution: Upgrade Debian/Ubuntu package to an up-to-date
  upstream release.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-qxl 0.1.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Dec 17 21:42:35 2013
  InstallationDate: Installed on 2013-12-13 (4 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131213)
  SourcePackage: xserver-xorg-video-qxl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/1261916/+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 1261916] Re: Missing letters in spice client session with KVM guest

[Harry Coin]

Installation has finished.  ou can continue testing  ubuntu now,
(should be 'You' and 'Xubuntu'.The two buttons are titled 'Continue
esting' and 'Restart  ow'.The icons on the home screen have changed
to  'rash' 'ile system'  'ome' nad 'Install ubuntu 14.0'.

Looks to be a strange bug to do with highlighting letters for keyboard
shortcuts --- sort of.  There are strange little graphics artifacts here
and there as well.  There must be something else going on too since the
updated messages listing what was being installed or removed repeated
bits of earlier messages while displaying nothing of what presently was
being installed or removed.

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

Title:
  Missing letters in spice client session with KVM guest

Status in “xserver-xorg-video-qxl” package in Ubuntu:
  Incomplete
Status in “xserver-xorg-video-qxl” package in Fedora:
  Unknown

Bug description:
  Host: Xubuntu 13.04
  Guest: Xubuntu 14.04 with qxl graphics

  When connecting to a KVM guest via Spice client characters are not
  displayed (in graphical mode), to such extent that messages become
  unreadable/guest becomes unusable.

  This bug was reported and kind of resolved for Red Hat/Fedora: 
https://bugzilla.redhat.com/show_bug.cgi?id=974198
  The mentioned workaround to add kernel parameter nomodeset worked for me up 
to now.

  Proposed resolution: Upgrade Debian/Ubuntu package to an up-to-date
  upstream release.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-qxl 0.1.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Dec 17 21:42:35 2013
  InstallationDate: Installed on 2013-12-13 (4 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131213)
  SourcePackage: xserver-xorg-video-qxl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/1261916/+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 1261916] Re: Missing letters in spice client session with KVM guest

[Harry Coin]

If the graphics drivers on the system running spice viewer are relevant,
it's the nvidia 304-updates.   I mention this because the nature of the
'visual static' or 'visual artifacts' seems to change when moving from
one to another multi-head monitor.  However the missing letters remain
unchanged no matter the monitor, no matter whether ending and restarting
virt-viewer and virt-manager.

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

Title:
  Missing letters in spice client session with KVM guest

Status in “xserver-xorg-video-qxl” package in Ubuntu:
  Incomplete
Status in “xserver-xorg-video-qxl” package in Fedora:
  Unknown

Bug description:
  Host: Xubuntu 13.04
  Guest: Xubuntu 14.04 with qxl graphics

  When connecting to a KVM guest via Spice client characters are not
  displayed (in graphical mode), to such extent that messages become
  unreadable/guest becomes unusable.

  This bug was reported and kind of resolved for Red Hat/Fedora: 
https://bugzilla.redhat.com/show_bug.cgi?id=974198
  The mentioned workaround to add kernel parameter nomodeset worked for me up 
to now.

  Proposed resolution: Upgrade Debian/Ubuntu package to an up-to-date
  upstream release.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-qxl 0.1.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Dec 17 21:42:35 2013
  InstallationDate: Installed on 2013-12-13 (4 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131213)
  SourcePackage: xserver-xorg-video-qxl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/1261916/+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 1296860] Re: firefox hangs up compete laptop for no apparent reason

[Harry Stojan]

** Changed in: firefox (Ubuntu)
 Assignee: (unassigned) = Harry Stojan (softis)

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

Title:
  firefox hangs up compete laptop for no apparent reason

Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  At various occasions the firefox browser just hangs and not even the mouse 
pointer responds.
  Sometimes after some time there is a message about an irresponsive script. 
  Mostly after waiting a lot of minutes and closing firefox it works again.
  I do not have this problem on other machines or other os'es.
  Don't seem to have the problem in Chromium either.
  Seems like a firefox bug to me

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 28.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  NonfreeKernelModules: wl
  AddonCompatCheckDisabled: False
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1932 F pulseaudio
  BuildID: 20140317144912
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Mon Mar 24 18:35:37 2014
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2014-03-04 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140303)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.108  
metric 9
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=28.0/20140317144912
  RelatedPackageVersions:
   rhythmbox-mozilla 3.0.1-1ubuntu16
   totem-mozilla 3.10.1-1ubuntu3
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 92CN26WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: AIUU1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900042STD
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 11
  dmi.modalias: 
dmi:bvnLENOVO:bvr92CN26WW(V1.06):bd12/26/2013:svnLENOVO:pn20332:pvrLenovoYoga211:rvnLENOVO:rnAIUU1:rvr31900042STD:cvnLENOVO:ct10:cvrLenovoYoga211:
  dmi.product.name: 20332
  dmi.product.version: Lenovo Yoga 2 11
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1296860/+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 1296860] Re: firefox hangs up compete laptop for no apparent reason

[Harry Stojan]

** Changed in: firefox (Ubuntu)
 Assignee: Harry Stojan (softis) = (unassigned)

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

Title:
  firefox hangs up compete laptop for no apparent reason

Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  At various occasions the firefox browser just hangs and not even the mouse 
pointer responds.
  Sometimes after some time there is a message about an irresponsive script. 
  Mostly after waiting a lot of minutes and closing firefox it works again.
  I do not have this problem on other machines or other os'es.
  Don't seem to have the problem in Chromium either.
  Seems like a firefox bug to me

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 28.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  NonfreeKernelModules: wl
  AddonCompatCheckDisabled: False
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1932 F pulseaudio
  BuildID: 20140317144912
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Mon Mar 24 18:35:37 2014
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2014-03-04 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140303)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.108  
metric 9
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=28.0/20140317144912
  RelatedPackageVersions:
   rhythmbox-mozilla 3.0.1-1ubuntu16
   totem-mozilla 3.10.1-1ubuntu3
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 92CN26WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: AIUU1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900042STD
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 11
  dmi.modalias: 
dmi:bvnLENOVO:bvr92CN26WW(V1.06):bd12/26/2013:svnLENOVO:pn20332:pvrLenovoYoga211:rvnLENOVO:rnAIUU1:rvr31900042STD:cvnLENOVO:ct10:cvrLenovoYoga211:
  dmi.product.name: 20332
  dmi.product.version: Lenovo Yoga 2 11
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1296860/+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 1296860] Re: firefox hangs up compete laptop for no apparent reason

[Harry Stojan]

Me too, for four days now

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

Title:
  firefox hangs up compete laptop for no apparent reason

Status in “firefox” package in Ubuntu:
  New

Bug description:
  At various occasions the firefox browser just hangs and not even the mouse 
pointer responds.
  Sometimes after some time there is a message about an irresponsive script. 
  Mostly after waiting a lot of minutes and closing firefox it works again.
  I do not have this problem on other machines or other os'es.
  Don't seem to have the problem in Chromium either.
  Seems like a firefox bug to me

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 28.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  NonfreeKernelModules: wl
  AddonCompatCheckDisabled: False
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1932 F pulseaudio
  BuildID: 20140317144912
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Mon Mar 24 18:35:37 2014
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2014-03-04 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140303)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.108  
metric 9
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=28.0/20140317144912
  RelatedPackageVersions:
   rhythmbox-mozilla 3.0.1-1ubuntu16
   totem-mozilla 3.10.1-1ubuntu3
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 92CN26WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: AIUU1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900042STD
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 11
  dmi.modalias: 
dmi:bvnLENOVO:bvr92CN26WW(V1.06):bd12/26/2013:svnLENOVO:pn20332:pvrLenovoYoga211:rvnLENOVO:rnAIUU1:rvr31900042STD:cvnLENOVO:ct10:cvrLenovoYoga211:
  dmi.product.name: 20332
  dmi.product.version: Lenovo Yoga 2 11
  dmi.sys.vendor: LENOVO

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

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

Re: [Desktop-packages] [Bug 1039523] Re: Mouse Scroll Wheel not working in spice vm guests

[Harry Coin]

On 04/02/2014 10:36 PM, Christopher M. Penalver wrote:
 Michal Suchanek / Harry Coin, thank you for your comment. So your hardware 
 and problem may be tracked, could you please file a new report by executing 
 the following in a terminal:
 ubuntu-bug xorg

 Please ensure you have xdiagnose installed, and that you click the Yes
 button for attaching additional debugging information.

 For more on this, please see the official Ubuntu documentation:
 Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad: 
 https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
 Ubuntu Community: 
 https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

 When opening up the new report, please feel free to subscribe me to it.

 Please note, not filing a new report will delay your problem being
 addressed as quickly as possible.

 Thank you for your understanding.

 ** Changed in: xserver-xorg-input-evdev (Ubuntu)
 Status: Confirmed = Incomplete


I tried it out with trusty beta 2 with exactly the same results as saucy 
-- no scroll wheel operation.

However, I have found a major clue.

do:

service spice-vdagent stop

and the scroll wheel works  (but cuttting and pasting and related is 
broken).

and after

service spice-vdagent start

the scroll wheel stops again, but cutting and pasting works.

There is some sort of fight between spice-vdagent and the evdev xorg
driver.

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

Title:
  Mouse Scroll Wheel not working in spice vm guests

Status in “xserver-xorg-input-evdev” package in Ubuntu:
  Incomplete

Bug description:
  Im runnning Precise in various qemu-kvm virtual machines with Spice.

  The ScrollWheel stops working in the virtual machine as soon the 
spice-vdagent gets started.
  After killing the spice-vdagent process the Scroll Wheel works again.
  Seems to be an evdev Bug, see solved Fedora Bug:

  https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=805902

  Infos:

  Description:  Ubuntu 12.04.1 LTS
  Release:  12.04

  xserver-xorg-input-evdev:
Installiert: 1:2.7.0-0ubuntu1.2
Kandidat:1:2.7.0-0ubuntu1.2
Versionstabelle:
   *** 1:2.7.0-0ubuntu1.2 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:2.7.0-0ubuntu1 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  spice-vdagent:
Installiert: (keine)
Kandidat:0.8.1-1
Versionstabelle:
   0.8.1-1 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/universe amd64 
Packages

  See also attached Xorg.0.log

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

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

Re: [Desktop-packages] [Bug 1301722] Re: Mouse Scroll Wheel not working in spice vm guests

[Harry Coin]

As I use xubuntu, (standard ubuntu is way too 'heavy' for our purpose) 
is there a version from that world you can suggest?  Whatever the 
regular ubuntu results it won't help me.


On 04/03/2014 08:50 PM, Christopher M. Penalver wrote:
 Harry Coin, could you please test for this with the latest development
 release of Ubuntu? ISO images are available from
 http://cdimage.ubuntu.com/daily-live/current/ .

 If it remains an issue, could you please just make a comment to this.

 Thank you for your understanding.

 Helpful bug reporting tips:
 https://wiki.ubuntu.com/ReportingBugs

 ** Description changed:

 -
 - https://bugs.launchpad.net/bugs/1039523
 -
 -
 -   Im runnning Precise in various qemu-kvm virtual machines with Spice.
 -
 -   The ScrollWheel stops working in the virtual machine as soon the 
 spice-vdagent gets started.
 -   After killing the spice-vdagent process the Scroll Wheel works again.
 -   Seems to be an evdev Bug, see solved Fedora Bug:
 -
 -   https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=805902
 - Michal Suchanek / Harry Coin, thank you for your comment. So your hardware 
 and problem may be tracked, could you please file a new report by executing 
 the following in a terminal:
 - ubuntu-bug xorg
 + I'm running Precise in various qemu-kvm virtual machines with Spice. The 
 ScrollWheel stops working in the virtual machine as soon the spice-vdagent 
 gets started.   After killing the spice-vdagent process the Scroll Wheel 
 works again.
 + Seems to be an evdev Bug, see solved Fedora Bug:
 + https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=805902

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xorg 1:7.7+1ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
CompizPlugins: No value set for 
 `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Apr  2 22:55:21 2014
DistUpgraded: 2013-10-21 18:32:59,232 DEBUG enabling apt cron job
DistroCodename: saucy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 -  Red Hat, Inc. Device [1b36:0100] (rev 04) (prog-if 00 [VGA controller])
 -Subsystem: Red Hat, Inc Device [1af4:1100]
 +  Red Hat, Inc. Device [1b36:0100] (rev 04) (prog-if 00 [VGA controller])
 +Subsystem: Red Hat, Inc Device [1af4:1100]
InstallationDate: Installed on 2013-05-26 (311 days ago)
InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 
 (20130423.1)
LightdmGreeterLog:
 -  ** (lightdm-gtk-greeter:25761): WARNING **: Failed to open sessions 
 directory: Error opening directory '/usr/share/lightdm/remote-sessions': No 
 such file or directory
 -
 -  ** (lightdm-gtk-greeter:25761): WARNING **: Failed to load user image: 
 Failed to open file '/home/harry/.face': No such file or directory
 +  ** (lightdm-gtk-greeter:25761): WARNING **: Failed to open sessions 
 directory: Error opening directory '/usr/share/lightdm/remote-sessions': No 
 such file or directory
 +
 +  ** (lightdm-gtk-greeter:25761): WARNING **: Failed to load user image: 
 Failed to open file '/home/harry/.face': No such file or directory
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Bochs Bochs
MarkForUpload: True
ProcEnviron:
 -  LANGUAGE=en_US
 -  TERM=xterm
 -  PATH=(custom, no user)
 -  LANG=en_US.UTF-8
 -  SHELL=/bin/bash
 +  LANGUAGE=en_US
 +  TERM=xterm
 +  PATH=(custom, no user)
 +  LANG=en_US.UTF-8
 +  SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic 
 root=UUID=adda9701-5de5-45dd-9068-ce97f8259354 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to saucy on 2013-10-21 (163 days ago)
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: 
 dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.46-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 
 1:2.7.3-0ubuntu3.1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
 2:2.99.904-0ubuntu2.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
 1:1.0.9-2ubuntu1
xserver.bootTime: Fri Mar 28 12:35:38 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.devices:
 -  input

[Desktop-packages] [Bug 1301722] Re: Mouse Scroll Wheel not working in spice vm guests

[Harry Coin]

** Bug watch added: Red Hat Bugzilla #805902
   https://bugzilla.redhat.com/show_bug.cgi?id=805902

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

Title:
  Mouse Scroll Wheel not working in spice vm guests

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  I'm running Precise in various qemu-kvm virtual machines with Spice. The 
ScrollWheel stops working in the virtual machine as soon the spice-vdagent gets 
started.   After killing the spice-vdagent process the Scroll Wheel works again.
  Seems to be an evdev Bug, see solved Fedora Bug:
  https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=805902

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Apr  2 22:55:21 2014
  DistUpgraded: 2013-10-21 18:32:59,232 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Red Hat, Inc. Device [1b36:0100] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: Red Hat, Inc Device [1af4:1100]
  InstallationDate: Installed on 2013-05-26 (311 days ago)
  InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 
(20130423.1)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:25761): WARNING **: Failed to open sessions 
directory: Error opening directory '/usr/share/lightdm/remote-sessions': No 
such file or directory

   ** (lightdm-gtk-greeter:25761): WARNING **: Failed to load user image: 
Failed to open file '/home/harry/.face': No such file or directory
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Bochs Bochs
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic 
root=UUID=adda9701-5de5-45dd-9068-ce97f8259354 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to saucy on 2013-10-21 (163 days ago)
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Bochs
  dmi.bios.version: Bochs
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
  dmi.product.name: Bochs
  dmi.sys.vendor: Bochs
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.904-0ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Fri Mar 28 12:35:38 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputAT Translated Set 2 keyboard KEYBOARD, id 7
   inputImExPS/2 Generic Explorer Mouse MOUSE, id 8
   inputspice vdagent tablet TOUCHSCREEN, id 9
  xserver.errors:
   Failed to load module evdec (module does not exist, 0)
   Failed to load module evdec (module does not exist, 0)
   No input driver matching `evdec'
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   0
   vendor QXL
  xserver.version: 2:1.14.5-1ubuntu2~saucy1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1301722/+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 1301722] [NEW] Mouse Scroll Wheel not working in spice vm guests

[Harry Coin]

Public bug reported:


https://bugs.launchpad.net/bugs/1039523


  Im runnning Precise in various qemu-kvm virtual machines with Spice.

  The ScrollWheel stops working in the virtual machine as soon the 
spice-vdagent gets started.
  After killing the spice-vdagent process the Scroll Wheel works again.
  Seems to be an evdev Bug, see solved Fedora Bug:

  https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=805902
Michal Suchanek / Harry Coin, thank you for your comment. So your hardware and 
problem may be tracked, could you please file a new report by executing the 
following in a terminal:
ubuntu-bug xorg

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xorg 1:7.7+1ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Apr  2 22:55:21 2014
DistUpgraded: 2013-10-21 18:32:59,232 DEBUG enabling apt cron job
DistroCodename: saucy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Red Hat, Inc. Device [1b36:0100] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Red Hat, Inc Device [1af4:1100]
InstallationDate: Installed on 2013-05-26 (311 days ago)
InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1)
LightdmGreeterLog:
 ** (lightdm-gtk-greeter:25761): WARNING **: Failed to open sessions directory: 
Error opening directory '/usr/share/lightdm/remote-sessions': No such file or 
directory
 
 ** (lightdm-gtk-greeter:25761): WARNING **: Failed to load user image: Failed 
to open file '/home/harry/.face': No such file or directory
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Bochs Bochs
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic 
root=UUID=adda9701-5de5-45dd-9068-ce97f8259354 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to saucy on 2013-10-21 (163 days ago)
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.46-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
xserver.bootTime: Fri Mar 28 12:35:38 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputAT Translated Set 2 keyboard KEYBOARD, id 7
 inputImExPS/2 Generic Explorer Mouse MOUSE, id 8
 inputspice vdagent tablet TOUCHSCREEN, id 9
xserver.errors:
 Failed to load module evdec (module does not exist, 0)
 Failed to load module evdec (module does not exist, 0)
 No input driver matching `evdec'
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   0 
 vendor QXL
xserver.version: 2:1.14.5-1ubuntu2~saucy1

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


** Tags: amd64 apport-bug saucy ubuntu

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

Title:
  Mouse Scroll Wheel not working in spice vm guests

Status in “xorg” package in Ubuntu:
  New

Bug description:

  https://bugs.launchpad.net/bugs/1039523

  
Im runnning Precise in various qemu-kvm virtual machines with Spice.

The ScrollWheel stops working in the virtual machine as soon the 
spice-vdagent gets started.
After killing the spice-vdagent process the Scroll Wheel works again.
Seems to be an evdev Bug, see solved Fedora Bug:

https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=805902
  Michal Suchanek / Harry Coin, thank you for your comment. So your hardware 
and problem may be tracked, could you please file a new report by executing the 
following in a terminal:
  ubuntu-bug xorg

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64

[Desktop-packages] [Bug 1039523] Re: Mouse Scroll Wheel not working in spice vm guests

[Harry Coin]

Still broken in saucy.


** Changed in: xserver-xorg-input-evdev (Ubuntu)
   Status: Expired = Confirmed

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

Title:
  Mouse Scroll Wheel not working in spice vm guests

Status in “xserver-xorg-input-evdev” package in Ubuntu:
  Confirmed

Bug description:
  Im runnning Precise in various qemu-kvm virtual machines with Spice.

  The ScrollWheel stops working in the virtual machine as soon the 
spice-vdagent gets started.
  After killing the spice-vdagent process the Scroll Wheel works again.
  Seems to be an evdev Bug, see solved Fedora Bug:

  https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=805902

  Infos:

  Description:  Ubuntu 12.04.1 LTS
  Release:  12.04

  xserver-xorg-input-evdev:
Installiert: 1:2.7.0-0ubuntu1.2
Kandidat:1:2.7.0-0ubuntu1.2
Versionstabelle:
   *** 1:2.7.0-0ubuntu1.2 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:2.7.0-0ubuntu1 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  spice-vdagent:
Installiert: (keine)
Kandidat:0.8.1-1
Versionstabelle:
   0.8.1-1 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/universe amd64 
Packages

  See also attached Xorg.0.log

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1039523/+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 1290002] [NEW] Volume wheel (Dell keyboard) not adjusting Ubuntu volume properly after update

[Harry P]

Public bug reported:

Description:Ubuntu 12.04.4 LTS
Release:12.04

I run update on Ubuntu 12.04 64Bit on 2014-03-07, and after restarting
my pc, the keyboard volume wheel doesn't adjust the volume in Ubuntu OS
anymore.

Keyboard is Dell X295D Multimedia USB Keyboard (Greek)

I can confirm that the volume wheel is not malfunctioned because the
volume wheel trigger is detectable in SettingsKeyboardShortcutsSound
and MediaVolume Down/Volume Up, and it is also working in other
programs (XBMC for Ubuntu).

The packages included in the update are:
Install: 
linux-image-3.2.0-60-generic:amd64 (3.2.0-60.91),
linux-headers-3.2.0-60:amd64 (3.2.0-60.91),
linux-headers-3.2.0-60-generic:amd64 (3.2.0-60.91)
Upgrade: 
libmagickcore4:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), 
gnome-settings-daemon:amd64 (3.4.2-0ubuntu0.6.4, 3.4.2-0ubuntu0.6.5), 
icedtea-netx:amd64 (1.2.3-0ubuntu0.12.04.3, 1.2.3-0ubuntu0.12.04.4), 
libmagickwand4:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), 
linux-generic:amd64 (3.2.0.59.70, 3.2.0.60.71), 
libmagickcore4-extra:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), 
libgnutls26:amd64 (2.12.14-5ubuntu3.6, 2.12.14-5ubuntu3.7), 
libgnutls26:i386 (2.12.14-5ubuntu3.6, 2.12.14-5ubuntu3.7), 
xkb-data:amd64 (2.5-1ubuntu1.3, 2.5-1ubuntu1.5), 
icedtea-netx-common:amd64 (1.2.3-0ubuntu0.12.04.3, 1.2.3-0ubuntu0.12.04.4), 
icedtea-6-plugin:amd64 (1.2.3-0ubuntu0.12.04.3, 1.2.3-0ubuntu0.12.04.4), 
imagemagick-common:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), 
linux-headers-generic:amd64 (3.2.0.59.70, 3.2.0.60.71), 
linux-image-generic:amd64 (3.2.0.59.70, 3.2.0.60.71), 
libdvdnav4:amd64 (4.2.0-1, 4.2.0-1ubuntu0.1), 
imagemagick:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), 
linux-libc-dev:amd64 (3.2.0-59.90, 3.2.0-60.91), 
perlmagick:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3)

** Affects: xkeyboard-config (Ubuntu)
 Importance: Undecided
 Status: New

** Summary changed:

- Volume wheel (Dell keyboard) not adjusting Ubuntu volume properly after 
update to xkb-data:amd64 (2.5-1ubuntu1.3, 2.5-1ubuntu1.5)
+ Volume wheel (Dell keyboard) not adjusting Ubuntu volume properly after update

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

Title:
  Volume wheel (Dell keyboard) not adjusting Ubuntu volume properly
  after update

Status in “xkeyboard-config” package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 12.04.4 LTS
  Release:  12.04

  I run update on Ubuntu 12.04 64Bit on 2014-03-07, and after restarting
  my pc, the keyboard volume wheel doesn't adjust the volume in Ubuntu
  OS anymore.

  Keyboard is Dell X295D Multimedia USB Keyboard (Greek)

  I can confirm that the volume wheel is not malfunctioned because the
  volume wheel trigger is detectable in
  SettingsKeyboardShortcutsSound and MediaVolume Down/Volume Up, and
  it is also working in other programs (XBMC for Ubuntu).

  The packages included in the update are:
  Install: 
  linux-image-3.2.0-60-generic:amd64 (3.2.0-60.91),
  linux-headers-3.2.0-60:amd64 (3.2.0-60.91),
  linux-headers-3.2.0-60-generic:amd64 (3.2.0-60.91)
  Upgrade: 
  libmagickcore4:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), 
  gnome-settings-daemon:amd64 (3.4.2-0ubuntu0.6.4, 3.4.2-0ubuntu0.6.5), 
  icedtea-netx:amd64 (1.2.3-0ubuntu0.12.04.3, 1.2.3-0ubuntu0.12.04.4), 
  libmagickwand4:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), 
  linux-generic:amd64 (3.2.0.59.70, 3.2.0.60.71), 
  libmagickcore4-extra:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), 
  libgnutls26:amd64 (2.12.14-5ubuntu3.6, 2.12.14-5ubuntu3.7), 
  libgnutls26:i386 (2.12.14-5ubuntu3.6, 2.12.14-5ubuntu3.7), 
  xkb-data:amd64 (2.5-1ubuntu1.3, 2.5-1ubuntu1.5), 
  icedtea-netx-common:amd64 (1.2.3-0ubuntu0.12.04.3, 1.2.3-0ubuntu0.12.04.4), 
  icedtea-6-plugin:amd64 (1.2.3-0ubuntu0.12.04.3, 1.2.3-0ubuntu0.12.04.4), 
  imagemagick-common:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), 
  linux-headers-generic:amd64 (3.2.0.59.70, 3.2.0.60.71), 
  linux-image-generic:amd64 (3.2.0.59.70, 3.2.0.60.71), 
  libdvdnav4:amd64 (4.2.0-1, 4.2.0-1ubuntu0.1), 
  imagemagick:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), 
  linux-libc-dev:amd64 (3.2.0-59.90, 3.2.0-60.91), 
  perlmagick:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1290002/+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 1267299] Re: Libreoffice reports general error when saving/opening

[Harry]

You may have not installed all the necessary packages.
For example, see that you have the package librdf0 installed.

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

Title:
  Libreoffice reports general error when saving/opening

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  The document is actually saved and can be loaded, however LibreOffice
  reports General Error accompanied by a red circle with a minus sign.

  Note ubuntu-bug said Libreoffice was not installed however synaptic
  says it is and it does run.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7
  Uname: Linux 3.13.0-1-generic x86_64
  ApportVersion: 2.12.7-0ubuntu6
  Architecture: amd64
  Date: Wed Jan  8 20:54:28 2014
  InstallationDate: Installed on 2014-01-08 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140108)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   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/1267299/+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