from:"WinEunuchs2Unix"

[Desktop-packages] [Bug 1444880] Re: xrandr report inverted gamma values

2019-11-30 Thread WinEunuchs2Unix

A bug report was filed in 2010, supposedly fixed in 2018 and patched in
2019 in `xrandr` version `1.5.1`. I tried compiling `1.5.1` in Ubuntu
but it didn't seem to have been fixed yet. Documented in this Ask Ubuntu
Q: [When will xrandr version 1.5.1 be available in
Ubuntu?](https://askubuntu.com/questions/1192154/when-will-xrandr-
version-1-5-1-be-available-in-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/1444880

Title:
  xrandr report inverted gamma values

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  $ xrandr --output VGA1  --gamma 1:1:1.7
  $ xrandr --verbose | grep -iE '(gamma|bright)'
  Gamma:  1.0:1.0:1.7
  Brightness: 1.0
  Gamma:  1.0:1.0:0.59
  Brightness: 1.0
  $ xrandr --output VGA1  --gamma 1:1:.6
  $ xrandr --verbose | grep -iE '(gamma|bright)'
  Gamma:  1.0:1.0:1.7
  Brightness: 1.0
  Gamma:  1.0:1.0:1.7
  Brightness: 1.0

  As you can see in output of commands above, "Gamma" values printed by
  xrandr --verbose are exactly the invert of the values set: 1/... Appart for value 1.0 which is correct.

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

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

[Desktop-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

2019-10-25 Thread WinEunuchs2Unix

Bug still exists on Ubuntu 16.04.6 LTS, Kernel 4.14.140. Found when
looking for what was causing xrandr to reset screens to full brightness
and gamma. Even if `colord` isn't culprit, life is easier with less spam
in journalctl.

Ignore extra `s` in `fails` below (line wrap off) for bug report:

$ journalctl | grep "failed to get session \[pid"
Aug 24 08:43:54 alien colord[1366]: (colord:1366): Cd-WARNING **: fails
Aug 24 08:43:54 alien colord[1366]: (colord:1366): Cd-WARNING **: fails
Aug 25 07:41:51 alien colord[1366]: (colord:1366): Cd-WARNING **: fails
Aug 25 07:41:51 alien colord[1366]: (colord:1366): Cd-WARNING **: fails

.. (SNIP) ..

Oct 22 04:33:50 alien colord[1215]: (colord:1215): Cd-WARNING **: fails
Oct 22 04:33:50 alien colord[1215]: (colord:1215): Cd-WARNING **: fails
Oct 23 04:34:53 alien colord[1215]: (colord:1215): Cd-WARNING **: fails
Oct 23 04:34:53 alien colord[1215]: (colord:1215): Cd-WARNING **: fails
Oct 24 04:36:20 alien colord[1215]: (colord:1215): Cd-WARNING **: fails
Oct 24 04:36:20 alien colord[1215]: (colord:1215): Cd-WARNING **: fails
Oct 25 04:36:56 alien colord[1215]: (colord:1215): Cd-WARNING **: fails
Oct 25 04:36:56 alien colord[1215]: (colord:1215): Cd-WARNING **: fails

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

Title:
  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged into journalctl

  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:57:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   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-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  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

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

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

[Desktop-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation

2019-08-04 Thread WinEunuchs2Unix

I have three screens:

1) nVidia GTX 970M HDMI port of laptop.  1920x1080
2) USB-C, Thunderbolt III HDMI dongle.   3840x2160
3) Laptop eDP1 (i7 6700HQ, HD 530 iGPU). 1920x1080

Upon resume the 3840x2160 screen's wallpaper is **OK**.

The two 1920x1080 screens wallpaper is all white.

Ubuntu 16.04.6 LTS upgrade direct to 19.04 w/kernel 5.0.0-23 yesterday.

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

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend or
  hibernation

Status in GNOME Shell:
  Unknown
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Bionic:
  Confirmed
Status in mutter source package in Disco:
  Confirmed
Status in mutter source package in Eoan:
  In Progress

Bug description:
  https://trello.com/c/i5hENxSO

  Every other wake from sleep presents a corrupted screen with no unlock
  app.  There's a dock and system menu on a black background with pixel
  garbage.  Some personal information in the dock's large window
  thumbnails.  Bitmap garbage flashes on the screen when interacting
  with anything.  Only workaround is doing another sleep-wake cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:4b:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 20 22:19:29 2018
  DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-11-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-12-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162]
  InstallationDate: Installed on 2018-10-28 (54 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F24
  dmi.board.asset.tag: Default string
  dmi.board.name: X99P-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

-- 
Mailing list:

[Desktop-packages] [Bug 1753884] Re: session logout after suspend

2019-06-14 Thread WinEunuchs2Unix

This happens to me periodically with Ubuntu 16.04.6 LTS, Kernel
4.14.114.

External HDMI 1080p TV nVidia GTX 970M driven
External HDMI 4K TV i915 Thunderbolt3 USB-C driven
Internal Dell 1080p LCD i915 driven

Method:

1) close laptop lid with power & systemd set to "do nothing"
2) external monitors will disconnect (no signal) and have to move mouse to 
reconnect.
3) select GUI suspend from external monitor
4) power off external screens after system suspends
5) power on external screens
6) open laptop lid to resume
7) about 20% of time login screen appears and all work is lost

If fixed in 17.10 would be nice to see backported to 16.04 as current
plans for upgrade aren't until 20.04.

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

Title:
   session logout after suspend

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  Only when I have a second monitor plugged in, if I close the lid of my
  laptop, my session gets logged out. What I'm expecting is the lock
  screen comes up.

  Sometimes (but not always) the second monitor will flash the "logged
  out" screen for a second or two before going dim.

  I have "Suspend even if external monitor is plugged in" enabled in
  Tweak Tools.

  WORKAROUND: Suspend via the GUI with the lid open.

  WORKAROUND: Unplug the second monitor before closing the lid.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Mar  6 18:07:50 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2018-02-15 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 20AQ009HUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=6f20d80f-81f4-40c1-aafd-95b2c5de55ed ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET78WW (2.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ009HUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET78WW(2.28):bd07/29/2014:svnLENOVO:pn20AQ009HUS:pvrThinkPadT440s:rvnLENOVO:rn20AQ009HUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20AQ009HUS
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'

2018-09-12 Thread WinEunuchs2Unix

Dell AW17R3, Skylake i7-6700HQ, nVidia GTX 970M, Thunderbolt USB-C,
Ubuntu 16.04.5 LTS, Kernel 4.13-0-36-generic. Error appears with
`journalctl --follow` whilst monitoring for unrelated error message
tonight.

Complete log below:

$ journalctl --follow
-- Logs begin at Sat 2018-08-04 14:57:01 MDT. --
Sep 12 19:54:46 alien sudo[11861]: root : TTY=unknown ; PWD=/root ; 
USER=root ; COMMAND=/usr/bin/tee /sys/class/backlight/intel_backlight/brightness
Sep 12 19:54:46 alien sudo[11861]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
Sep 12 19:54:46 alien sudo[11861]: pam_unix(sudo:session): session closed for 
user root
Sep 12 19:54:46 alien sudo[11858]: pam_unix(sudo:session): session closed for 
user root
Sep 12 19:55:46 alien sudo[15339]: root : TTY=unknown ; PWD=/root ; 
USER=root ; COMMAND=/bin/sh -c echo 654 | sudo tee 
/sys/class/backlight/intel_backlight/brightness
Sep 12 19:55:46 alien sudo[15339]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
Sep 12 19:55:46 alien sudo[15342]: root : TTY=unknown ; PWD=/root ; 
USER=root ; COMMAND=/usr/bin/tee /sys/class/backlight/intel_backlight/brightness
Sep 12 19:55:46 alien sudo[15342]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
Sep 12 19:55:46 alien sudo[15342]: pam_unix(sudo:session): session closed for 
user root
Sep 12 19:55:46 alien sudo[15339]: pam_unix(sudo:session): session closed for 
user root
Sep 12 19:56:46 alien sudo[18777]: root : TTY=unknown ; PWD=/root ; 
USER=root ; COMMAND=/bin/sh -c echo 650 | sudo tee 
/sys/class/backlight/intel_backlight/brightness
Sep 12 19:56:46 alien sudo[18777]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
Sep 12 19:56:46 alien sudo[18780]: root : TTY=unknown ; PWD=/root ; 
USER=root ; COMMAND=/usr/bin/tee /sys/class/backlight/intel_backlight/brightness
Sep 12 19:56:46 alien sudo[18780]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
Sep 12 19:56:46 alien sudo[18780]: pam_unix(sudo:session): session closed for 
user root
Sep 12 19:56:46 alien sudo[18777]: pam_unix(sudo:session): session closed for 
user root
Sep 12 19:59:00 alien wpa_supplicant[1399]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: 
(org.freedesktop.DBus.Error.Failed) failed to parse RSN IE
Sep 12 19:59:00 alien wpa_supplicant[1399]: dbus: Failed to construct signal
Sep 12 20:00:01 alien CRON[30005]: pam_unix(cron:session): session opened for 
user root by (uid=0)
Sep 12 20:00:01 alien CRON[30006]: pam_unix(cron:session): session opened for 
user root by (uid=0)
Sep 12 20:00:01 alien CRON[30007]: (root) CMD (/sbin/fstrim /)
Sep 12 20:00:01 alien CRON[30008]: (root) CMD (/usr/bin/updatedb)
Sep 12 20:00:06 alien CRON[30006]: pam_unix(cron:session): session closed for 
user root
Sep 12 20:00:06 alien CRON[30005]: pam_unix(cron:session): session closed for 
user root
Sep 12 20:01:58 alien upowerd[1945]: (upowerd:1945): UPower-Linux-WARNING **: 
treating change event as add on 
/sys/devices/pci:00/:00:14.0/usb1/1-9/1-9:1.2/0003:046D:C52B.0005/0003:046D:2010.0009/power_supply/hidpp_battery_3
Sep 12 20:05:00 alien wpa_supplicant[1399]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: 
(org.freedesktop.DBus.Error.Failed) failed to parse RSN IE
Sep 12 20:05:00 alien wpa_supplicant[1399]: dbus: Failed to construct signal
Sep 12 20:15:01 alien CRON[18052]: pam_unix(cron:session): session opened for 
user root by (uid=0)
Sep 12 20:15:01 alien CRON[18053]: (root) CMD (/usr/bin/updatedb)
Sep 12 20:15:06 alien CRON[18052]: pam_unix(cron:session): session closed for 
user root
Sep 12 20:17:00 alien wpa_supplicant[1399]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: 
(org.freedesktop.DBus.Error.Failed) failed to parse RSN IE
Sep 12 20:17:00 alien wpa_supplicant[1399]: dbus: Failed to construct signal
Sep 12 20:17:01 alien CRON[24974]: pam_unix(cron:session): session opened for 
user root by (uid=0)
Sep 12 20:17:01 alien CRON[24975]: (root) CMD (   cd / && run-parts --report 
/etc/cron.hourly)
Sep 12 20:17:01 alien CRON[24974]: pam_unix(cron:session): session closed for 
user root
Sep 12 20:23:00 alien wpa_supplicant[1399]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: 
(org.freedesktop.DBus.Error.Failed) failed to parse RSN IE
Sep 12 20:23:00 alien wpa_supplicant[1399]: dbus: Failed to construct signal
Sep 12 20:28:33 alien upowerd[1945]: (upowerd:1945): UPower-Linux-WARNING **: 
treating change event as add on 
/sys/devices/pci:00/:00:14.0/usb1/1-9/1-9:1.2/0003:046D:C52B.0005/0003:046D:2010.0009/power_supply/hidpp_battery_3
Sep 12 20:30:01 alien CRON[6024]: pam_unix(cron:session): session opened for 
user root by (uid=0)
Sep 12 20:30:01 alien CRON[6025]: (root) CMD (/usr/bin/updatedb)
Sep 12 20:30:06 alien CRON[6024]: pam_unix(cron:session): session closed for 
user root

-- 
You received this bug notification because you are a member of

[Desktop-packages] [Bug 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop

2018-06-24 Thread WinEunuchs2Unix

My 2 cents worth is this is a common hardware problem where newer
Laptops have GPU HDMI sound turned off as a default. I think a grub
kernel boot parameter could be set to force `setpci` to be run at
appropriate memory location.

Therefore the Linux Kernel team could be responsible for the bug fix.
However, the nVidia folks might be responsible for submitting the fix to
the Linux Kernel Team.

As a side note, I've stopped using the nVidia card in Linux for the last
six months. Since I'm only using the Intel iGPU Skylake GT 530 graphics,
I'm happy the nVidia GTX 970M HDMI sound is turned off and not
generating heat.

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

Title:
  HDMI sound output not detected / NVIDIA optimus laptop

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  not sure if this is an alsa or nvidia/nouveau bug.
  HDMI audio output doesn't appear in sound settings output panel.
  Audio works well on internal speakers, but it seems there is no way to make 
it output to hdmi...

  The laptop has optimus NVIDIA+Intel.
  The behaviour is the same with nouveau or nvidia proprietary driver.

  Please let me know if further testing is required

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sam2295 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Sun Oct  5 17:05:35 2014
  InstallationDate: Installed on 2014-04-21 (166 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  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/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VZ.215
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VZ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.215:bd11/02/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N56VZ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1377653/+subscriptions

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

[Desktop-packages] [Bug 1587154] Re: --working-directory does not work anymore

2018-05-20 Thread WinEunuchs2Unix

This bug has been fixed for Ubuntu 16.04.3 LTS running under Kernel
4.14.34-generic:

$ gnome-terminal --working-directory=/tmp

Opens a new terminal window with `/tmp` the current directory as expect.

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

Title:
  --working-directory does not work anymore

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  
  After upgrading from ubuntu 14.04 to 16.04 one of my script the uses 
--working-directory option stopped working.

  Simply running:

  gnome-terminal --working-directory=/tmp

  Starts the terminal in my home directory. Changing the command to
  gnome-terminal.real does not solve my problem either.

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

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

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

2018-04-29 Thread WinEunuchs2Unix

Reply to #8, problem seems to have gone away on it's own today. Had
tried multiple DE's that didn't work and went into Unity. A message that
"Updates are available" appeared. Clicking on it installed nothing but
probably ran `sudo apt update`, `sudo apt upgrade` in the background.
Rebooted into 16.04. Later rebooted into 18.04 test environment and
`Ctrl`+`Alt`+`T` and media keys are working.

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

Title:
  Keyboard shortcuts not operational on 18.04

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

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

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

  Some examples are:

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

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

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

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

  Any other info needed?

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

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

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

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

2018-04-28 Thread WinEunuchs2Unix

Like #3 I also have the Logitech K800 wireless keyboard.

- Ctrl+Alt+T doesn't open terminal must use Dash and select gnome-terminal
- Alt+PrintScreen doesn't open screen-shot must use Dash and select Screenshot
- Media keys don't work

Resorting to laptop's keyboard (Alienware 17 R3) Ctrl+Alt+T doesn't work
either.

Ubuntu 16.04 upgraded to Ubuntu 18.04 (luckily in test environment).
Answered Y to half a dozen prompts to convert login.d, sane, network and
others to new configuration format. Only declined not to update
/etc/default/grub to new configuration format.

Signed in with Unity under Xorg.

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

Title:
  Keyboard shortcuts not operational on 18.04

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

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

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

  Some examples are:

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

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

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

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

  Any other info needed?

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

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

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

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

2018-02-08 Thread WinEunuchs2Unix

Ubuntu 16.04, Kernel 4.14.18, nVidia GTX 970M, AW17R3 with i7 6700-HQ,
Using Intel HD 530 graphics on built-in display and external HDMI via
Thunderbolt 3 USB C adapter.

Message:

bus: MMIO read of  FAULT at 022554 [ IBUS ]

-- 
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 1568560] Re: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed

2017-12-13 Thread WinEunuchs2Unix

Not sure I agree with #13 because message comes AFTER network is up:

Dec 13 05:52:20 alien NetworkManager[902]:   [1513169540.4985] 
platform-linux: kernel support for IFLA_INET6_ADDR_GEN_MODE failed to detect; 
assume no support
Dec 13 05:52:20 alien NetworkManager[902]:   [1513169540.4991] manager: 
(enp59s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/0)
Dec 13 05:52:20 alien NetworkManager[902]:   [1513169540.4998] keyfile: 
add connection in-memory (f1d049d0-ad20-3201-ac70-5cb8cc06a6e5,"Wired 
connection 1")
Dec 13 05:52:20 alien NetworkManager[902]:   [1513169540.5001] settings: 
(enp59s0): created default wired connection 'Wired connection 1'
Dec 13 05:52:20 alien NetworkManager[902]:   [1513169540.5007] device 
(enp59s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Dec 13 05:52:20 alien NetworkManager[902]:   [1513169540.5025] device 
(enp59s0): link connected
Dec 13 05:52:20 alien kernel: alx :3b:00.0 enp59s0: NIC Up: 1 Gbps Full
Dec 13 05:52:20 alien NetworkManager[902]: nm_device_get_device_type: assertion 
'NM_IS_DEVICE (self)' failed
D

Ubuntu 16.04.3, Kernel 4.14.4, Skylake laptop. IPv6 disabled with kernel
command line in grub just because it life seems simpler that way. Only a
couple of minor network interruptions requiring reboot over the last
month.

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

Title:
  nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed

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

Bug description:
  Hello,
  On Ubuntu 15.10 4.2.0-35, with network-manager 1.0.4-0ubuntu5.3
  My WiFi connection is very unstable and I have to  often restart 
NetworkManager service (~ a dozen times every day...):

  sudo systemctl -l status NetworkManager
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: active (running) since dim. 2016-04-10 18:17:07 CEST; 2min 58s ago
   Main PID: 27832 (NetworkManager)
 Memory: 13.8M
CPU: 1.729s
 CGroup: /system.slice/NetworkManager.service
 ├─ 2703 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground 
--no-hosts --bind-interfaces 
--pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid 
--listen-address=127.0.1.1 --conf-file=/var/run/NetworkManager/dnsmasq.conf 
--cache-size=0 --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d
 ├─27832 /usr/sbin/NetworkManager --no-daemon
 └─30448 /sbin/dhclient -d -q -sf 
/usr/lib/NetworkManager/nm-dhcp-helper -pf 
/run/sendsigs.omit.d/network-manager.dhclient-wlan0.pid -lf 
/var/lib/NetworkManager/dhclient-7ec429cb-9dde-4ea4-8eda-f259b66e38a7-wlan0.lease
 -cf /var/lib/NetworkManager/dhclient-wlan0.conf wlan0

  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   keyfile: add 
connection in-memory (068de9b1-513a-46f0-b4be-93462d19f68b,"lxcbr0")
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 
20 41]
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
device state change: unavailable -> disconnected (reason 'connection-assumed') 
[20 30 41]
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
Activation: starting connection 'lxcbr0' (068de9b1-513a-46f0-b4be-93462d19f68b)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1-nic): 
new Tun device (carrier: OFF, driver: 'tun', ifindex: 34)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1): 
bridge port virbr1-nic was attached
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1-nic): 
enslaved to virbr1
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr0): new 
Bridge device (carrier: OFF, driver: 'bridge', ifindex: 29)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: 
nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   failed to 
enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: 
The name org.ofono was not provided by any .service files

  Also, each time I restart my desktop, NetworkManager generates a crash 
report: cf. attached screenshots.
  I have tried an Ubuntu VM with the same packages related to networking and 
the exact same releases (same repositories), the crash never happens; the 
difference appears to be only the type of network connection: WiFi for the 
desktop vs Ethernet for the VM.

  Any suggestion?

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

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

[Desktop-packages] [Bug 1309535] Re: Running without pam-kwallet installed issues a warning in auth.log

2017-12-13 Thread WinEunuchs2Unix

#19 works for me except there are two extra lines and another identical
file to change:

#authoptionalpam_kwallet.so
#authoptionalpam_kwallet5.so
#session optionalpam_kwallet.so auto_start
#session optionalpam_kwallet5.so auto_start

...are the four lines to comment out.

/etc/pam.d/lightdm
/etc/pam.d/lightdm-greeter

...are the two files to modify.

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

Title:
  Running without pam-kwallet installed issues a warning in auth.log

Status in lightdm package in Ubuntu:
  Won't Fix
Status in pam package in Ubuntu:
  Won't Fix

Bug description:
  After upgrading to lightdm 1.10.0-0ubuntu2 I started to see this error
  in auth.log:

  Apr 10 14:34:54 simon-laptop lightdm: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  Apr 10 14:34:54 simon-laptop lightdm: PAM adding faulty module: pam_kwallet.so

  This seems like a regression because with lightdm 1.10.0-0ubuntu1 or
  before I didn't have this error showing. FYI, I don't have the pam-
  kwallet package installed.

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

  $ apt-cache policy lightdm pam-kwallet
  lightdm:
Installed: 1.10.0-0ubuntu3
Candidate: 1.10.0-0ubuntu3
Version table:
   *** 1.10.0-0ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 18 09:12:37 2014
  InstallationDate: Installed on 2014-01-26 (81 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1409166] Re: Popup dialog "could not set the configuration for CRTC 65" steals keyboard, hinders login in 3-monitor configuration

2017-12-13 Thread WinEunuchs2Unix

Have a three screen setup now:

1) Laptop screen primary gets User ID password on boot. After boot chrome 
windows which were on screen 2 are restored here along with this screens chrome 
windows.
2) HDMI nVvidia hardwired TV, steals focus on resume to password.
3) Thunderbolt 3 USB-C HDMI TV which occasionally doesn't get signal when 
rebooted and has to be powered off and on.

Other notes when booting all three monitors turn on and off a few times.
There is one patch applied during boot to enable nVidia HDMI sound:

setpci -vD -s 01:00.0 0x488.l=0x:0x
sh -c 'echo 1 > /sys/bus/pci/devices/:01:00.0/remove'
sh -c 'echo 1 > /sys/bus/pci/devices/:00:01.0/rescan'
systemctl restart lightdm.service

Ubuntu 16.04.3, Kernel 4.14.4, Skylake 6700HQ, nVidia GTX 970M, Samsung
Pro 960 NVMe SSD.

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

Title:
  Popup dialog "could not set the configuration for CRTC 65" steals
  keyboard, hinders login in 3-monitor configuration

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  Every time I boot, while I'm trying to enter my password in the
  initial login screen (from Unity?), a dialog box pops up saying "Could
  not switch the monitor configuration  could not set the configuration
  for CRTC 65".

  The dialog box also steals the keyboard focus, which is very confusing
  if for some reason you're entering the password on an external display
  while the normally unused laptop display is not visible.  For example,
  three times in a row this morning I rebooted and tried unsuccessfully
  to log in.  Since the dialog box is only displayed on the laptop
  display, which I never use when external monitors are available, I had
  no idea why my keyboard seemed broken.

  Background:

  My Lenovo Thinkpad X230 Tablet laptop has a VGA and a DVI connector.
  I have the VGA hooked up to a Viewsonic 1920x1080 monitor, positioned
  above the laptop display.  I have a Samsung monitor to the right of
  the Viewsonic.  Since my laptop seems to only support two displays
  (which also seems true in Windows), I normally disable and totally
  ignore my laptop display, and may have papers propped up in front of
  it etc.

  Note that when I initially configured the third display I saw the
  following highly confusing behavior.  From Settings I tried to add a
  Samsung monitor to the right of the Viewsonic, via a DVI-to-HDMI
  passive connector, and got this dialog box when I hit "Apply":

     The selected configuration for displays could not be applied
     could not set the configuration for CRTC 65

  I clicked "OK" and got another dialog box:
     Failed to apply configuration: %s
     Can't add monitor: 
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gnome_2drr_2derror_2dquark.Code2:
 could not set the configuration for CRTC 65

  It works if I disable my laptop monitor, so it looks like the problem
  is with adding a third display.  I would think it would be a pretty
  common use case to use two nice external displays and disable the
  laptop display.

  Even when the hardware can't handle a third display, the error
  messages should not be so confusing, and the login process shouldn't
  result in the keyboard being mysteriously stolen by a dialog box on a
  display which may never be visible.

  This is on Trusty 64-bit, up-to-date with upgrades.

  This bug seems similar to bug 1304627, but it seemed cleanest to get
  all the right information reported via ubuntu-bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.6
  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: Fri Jan  9 15:35:57 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:2203]
  InstallationDate: Installed on 2015-01-01 (8 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-43-generic 
root=UUID=6dce26c4-3d5b-4980-880e-06f249f77c57 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2013
  dmi.bios.vendor: LENOVO

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

2017-11-26 Thread WinEunuchs2Unix

Dell Alienware 17R3 w/Sky Lake, nVidia GTX 970M and Intel HD530 with
prime-select set to nVidia. Running Ubuntu 16.04.3 LTS with a laptop
screen plus HDMI external screen plus HDMI external screen (via
Thunderbolt 3 Displayport to HDMI adapter).

>From /var/log/syslog today:

Nov 26 13:33:12 alien lightdm[1093]: /etc/modprobe.d is not a file
Nov 26 13:33:12 alien lightdm[1093]: message repeated 4 times: [ 
/etc/modprobe.d is not a file]
Nov 26 13:33:12 alien systemd[1]: lightdm.service: Main process exited, 
code=exited, status=1/FAILURE
Nov 26 13:33:12 alien systemd[1]: lightdm.service: Unit entered failed state.
Nov 26 13:33:12 alien systemd[1]: lightdm.service: Triggering OnFailure= 
dependencies.
Nov 26 13:33:12 alien systemd[1]: lightdm.service: Failed with result 
'exit-code'.
Nov 26 13:33:12 alien systemd[1]: Starting Clean up any mess left by 0dns-up...
Nov 26 13:33:12 alien systemd[1]: Started Run anacron jobs.
Nov 26 13:33:12 alien systemd[1]: Stopped target Graphical Interface.
Nov 26 13:33:12 alien mkdir[1163]: /bin/mkdir: cannot create directory 
‘/var/run/pppconfig’: File exists
Nov 26 13:33:12 alien systemd[1]: Starting Restore /etc/resolv.conf if the 
system crashed before the ppp link was shut down...
Nov 26 13:33:12 alien anacron[1164]: Anacron 2.3 started on 2017-11-26
Nov 26 13:33:12 alien anacron[1164]: Normal exit (0 jobs run)
Nov 26 13:33:12 alien systemd[1]: dns-clean.service: Control process exited, 
code=exited status=1
Nov 26 13:33:12 alien systemd[1]: Failed to start Clean up any mess left by 
0dns-up.
Nov 26 13:33:12 alien systemd[1]: dns-clean.service: Unit entered failed state.
Nov 26 13:33:12 alien systemd[1]: dns-clean.service: Failed with result 
'exit-code'.

-- 
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: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop

2017-11-11 Thread WinEunuchs2Unix

@Rudi

My BIOS doesn't have options for controlling nVidia GPU and Intel iGPU.

When I bought this laptop I thought I would be using Intel iGPU only and
was shocked to learn there was no HDMI screen until nVidia drivers were
installed. It took me about a month to figure that out. Then a couple of
days with this sound issue that you solved. Thanks again! I'm not sure
how to have nVidia take control of built-in display and Thuderbolt3
display which "I think" Intel iGPU is controlling now.

The screen flickering during boot (and the extra couple of seconds too)
is not a big deal for me. Now I'm more concerned about the 20-40 pixel
underscan nVidia GTX970M pumps out over Linux that doesn't happen in
Windows 10. Also the soft to loud fluctuating sound levels when
ThunderBolt3 HDMI sound is used to second TV (haven't checked that in
Windows 10 yet which if same means its the adapter). Then I have dozens
of bash scripts to upgrade to Windows Subsystem of Linux which requires
PowerShell instead of linux kernel commands. Also `gedit` and `nautilus`
need "tweaking" when running under xfce4, VcXsrv, WSL and Windows 10,
etc., etc.

So yeah... plate is kind of full. I've already saved 10 seconds in BIOS
POST reconfiguring so I'll live with extra 2 seconds of Ubuntu post-grub
boot screen flickering...

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

Title:
HDMI sound output not detected / NVIDIA optimus laptop

Status in alsa-driver package in Ubuntu:
Confirmed
Status in pulseaudio package in Ubuntu:
Confirmed

Bug description:
Hi,

not sure if this is an alsa or nvidia/nouveau bug.
HDMI audio output doesn't appear in sound settings output panel.
Audio works well on internal speakers, but it seems there is no way to make
it output to hdmi...

The laptop has optimus NVIDIA+Intel.
The behaviour is the same with nouveau or nvidia proprietary driver.

Please let me know if further testing is required

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sam2295 F pulseaudio
CurrentDesktop: Unity
CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission
denied
Date: Sun Oct 5 17:05:35 2014
InstallationDate: Installed on 2014-04-21 (166 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
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/02/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N56VZ.215
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N56VZ
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.215:bd11/02/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: N56VZ
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1377653/+subscriptions

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

[Desktop-packages] [Bug 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop

2017-11-11 Thread WinEunuchs2Unix

I can confirm solution in #19 works. Only caveats:

1) Rename `/root/` occurrences to `/usr/local/bin/`
2) Screens flickers on/off a couple/few times during boot.

My platform has nVidia GTX 970M hardwired to built-in HDMI hooked up to
external TV. Intel Skylake HD530 graphics controlling laptop built-in
display and USB-C Thunderbolt3 DisplayPort with HDMI adapter to 2nd
external TV.

Everything works seamlessly in Windows 10 and I'm glad the patch in #19
gets things one step closer to working in Linux/Ubuntu 16.04.

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

Title:
  HDMI sound output not detected / NVIDIA optimus laptop

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  not sure if this is an alsa or nvidia/nouveau bug.
  HDMI audio output doesn't appear in sound settings output panel.
  Audio works well on internal speakers, but it seems there is no way to make 
it output to hdmi...

  The laptop has optimus NVIDIA+Intel.
  The behaviour is the same with nouveau or nvidia proprietary driver.

  Please let me know if further testing is required

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sam2295 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Sun Oct  5 17:05:35 2014
  InstallationDate: Installed on 2014-04-21 (166 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  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/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VZ.215
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VZ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.215:bd11/02/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N56VZ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1377653/+subscriptions

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

[Desktop-packages] [Bug 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop

2017-11-10 Thread WinEunuchs2Unix

@sami I don't agree. My previous laptop Dell Insprion 17R 7720 SE has
nVidia GT650M + Intel HD4000 and works well in Linux because I simply
turned off nVidia. The new laptop Dell AW17R3 has the built-in HDMI
port hard-wired to the nVidia GTX 970M GPU which requires installing
nVidia drivers.

On the previous laptop headphone jack works perfectly. On the new one
analog and digital sound is supported and doesn't work out of the box.
On the previous laptop HDMI was full pixels with HD4000 driver. On the
new one there is about 40 pixels underscan all around.

The bigger problems (which is are technical challenges which I like) are
NVMe M.2 SSD setup, Windows Subsystem for Linux (WSL) under Windows 10
(W10) and converting Linux bash scripts on a shared NTFS parition when
dual-booting between Ubuntu and W10. Adding hybrid support to said bash
scripts with Powershell commands when running under W10. Compound the
challenges with installation of VcXsrv and Ubuntu desktops running Linux
GUI apps (like Firefox, LibreOffice) on W10.

If I didn't want technical challenges, I'd throw away my laptops and go
to the library.

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

Title:
HDMI sound output not detected / NVIDIA optimus laptop

Status in alsa-driver package in Ubuntu:
Confirmed
Status in pulseaudio package in Ubuntu:
Confirmed

Bug description:
Hi,

The laptop has optimus NVIDIA+Intel.
The behaviour is the same with nouveau or nvidia proprietary driver.

Please let me know if further testing is required

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1377653/+subscriptions

[Desktop-packages] [Bug 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop

2017-11-09 Thread WinEunuchs2Unix

Confirm this occurs with Dell AW17R3. Skylake i7 6700HQ with HM170
chipset and HD530 internal graphics controlling built in display and
external Thunderbolt 3 to display port to HDMI adapter sound works good.

Discrete GPU is GTX 970M and on built-in HDMI port is hard wired to it
(Optimus not supported). Here there is no sound and pavucontrol hangs
can't even display configuration properly. Additional problem of about
40 pixels underscanning with both Nouveau and nVidia drivers.

Windows 10 works perfectly in all departments except when resuming from
an overnight suspend nVidia HDMI might have to be hot-plugged to fix
screeching sound.

Added NVMe Samsung Pro 960 M.2 SSD card meaning in Linux kernel hot
plugging had to be deactivated due to known bug so solutions recommended
above in that area will not work.

Many thanks to previous poster for possible solution which I will
hopefully have time to try in a couple weeks.

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

Title:
HDMI sound output not detected / NVIDIA optimus laptop

Status in alsa-driver package in Ubuntu:
Confirmed
Status in pulseaudio package in Ubuntu:
Confirmed

Bug description:
Hi,

The laptop has optimus NVIDIA+Intel.
The behaviour is the same with nouveau or nvidia proprietary driver.

Please let me know if further testing is required

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1377653/+subscriptions

[Desktop-packages] [Bug 1409166] Re: Popup dialog "could not set the configuration for CRTC 65" steals keyboard, hinders login in 3-monitor configuration

2017-09-30 Thread WinEunuchs2Unix

I've been using LVDS + HDMI for a few years first under Ubuntu 14.04 and
currently under Ubuntu 16.04.

Today I setup an second external TV using the VGA port and an in-line
VGA to HDMI converter box that's worked before. The necessary xrandr
commands are given:

`xrandr --newmode "1920x1080_60.00"  173.00  1920 2048 2248 2576  1080 1083 
1088 1120 -hsync +vsync`
`xrandr --addmode VGA1 "1920x1080"`

However the CRTC 65 popup error message results.

Although I am long-term shopping for a new laptop with HDMI + one or two
DP's, it would be nice to have HDMI+VGA working now.

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

Title:
  Popup dialog "could not set the configuration for CRTC 65" steals
  keyboard, hinders login in 3-monitor configuration

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  Every time I boot, while I'm trying to enter my password in the
  initial login screen (from Unity?), a dialog box pops up saying "Could
  not switch the monitor configuration  could not set the configuration
  for CRTC 65".

  The dialog box also steals the keyboard focus, which is very confusing
  if for some reason you're entering the password on an external display
  while the normally unused laptop display is not visible.  For example,
  three times in a row this morning I rebooted and tried unsuccessfully
  to log in.  Since the dialog box is only displayed on the laptop
  display, which I never use when external monitors are available, I had
  no idea why my keyboard seemed broken.

  Background:

  My Lenovo Thinkpad X230 Tablet laptop has a VGA and a DVI connector.
  I have the VGA hooked up to a Viewsonic 1920x1080 monitor, positioned
  above the laptop display.  I have a Samsung monitor to the right of
  the Viewsonic.  Since my laptop seems to only support two displays
  (which also seems true in Windows), I normally disable and totally
  ignore my laptop display, and may have papers propped up in front of
  it etc.

  Note that when I initially configured the third display I saw the
  following highly confusing behavior.  From Settings I tried to add a
  Samsung monitor to the right of the Viewsonic, via a DVI-to-HDMI
  passive connector, and got this dialog box when I hit "Apply":

     The selected configuration for displays could not be applied
     could not set the configuration for CRTC 65

  I clicked "OK" and got another dialog box:
     Failed to apply configuration: %s
     Can't add monitor: 
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gnome_2drr_2derror_2dquark.Code2:
 could not set the configuration for CRTC 65

  It works if I disable my laptop monitor, so it looks like the problem
  is with adding a third display.  I would think it would be a pretty
  common use case to use two nice external displays and disable the
  laptop display.

  Even when the hardware can't handle a third display, the error
  messages should not be so confusing, and the login process shouldn't
  result in the keyboard being mysteriously stolen by a dialog box on a
  display which may never be visible.

  This is on Trusty 64-bit, up-to-date with upgrades.

  This bug seems similar to bug 1304627, but it seemed cleanest to get
  all the right information reported via ubuntu-bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.6
  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: Fri Jan  9 15:35:57 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:2203]
  InstallationDate: Installed on 2015-01-01 (8 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-43-generic 
root=UUID=6dce26c4-3d5b-4980-880e-06f249f77c57 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET96WW (2.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO

[Desktop-packages] [Bug 1575484] Re: "Set document metadata failed"

2017-06-12 Thread WinEunuchs2Unix

You get this error when elevating privileges to root using sudo, gksu or
pkexec. Further you can't set default tab stops, tabs to spaces, font,
it doesn't return to last save position and the entire top line menu
dissappears.

I'm curious whether creating an account called "root" will setup
configuration files for gedit to save to???

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

Title:
  "Set document metadata failed"

Status in gedit:
  Invalid
Status in gedit package in Ubuntu:
  Fix Committed

Bug description:
  Whenever I edit a document via the Terminal, I get these error
  messages:

  ** (gedit:12864): WARNING **: Set document metadata failed: Setting
  attribute metadata::gedit-spell-enabled not supported

  ** (gedit:12864): WARNING **: Set document metadata failed: Setting
  attribute metadata::gedit-encoding not supported

  ** (gedit:12864): WARNING **: Set document metadata failed: Setting
  attribute metadata::gedit-position not supported

  Info:
  OS: Ubuntu 16.04 (Xenial) x64
  App version: 3.18.3

  - Blossom

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

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

[Desktop-packages] [Bug 1582496] Re: GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup

2017-05-08 Thread WinEunuchs2Unix

Just received a similar message Ubuntu 16.04 using YAD (Yet Another
Dialog):

(yad:8401): GLib-GObject-CRITICAL **: g_object_unref: assertion
'G_IS_OBJECT (object)' failed

^^^ Appears about 20 times. I was in the process of adding new columns
of icons to existing dialog box matching mime file types. Not sure
exactly which code revisions caused the error though.

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

Title:
  GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup

Status in gnome-session:
  New
Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  I submitted this question a week but did not receive an answer or
  advice to solving them. https://answers.launchpad.net/ubuntu/+source
  /gnome-session/+question/293479

  These failures are still plaguing my syslog every time I activate
  Nautilus.

  Appreciate help to resolve these failures.

  
   Earlier question 
  After a recent updating, I notice these failures in the systemlogs. 

  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:35:01 Eliot org.gnome.zeitgeist.Engine[1400]: 
(zeitgeist-daemon:2197): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'object->ref_count > 0' failed
  May  9 16:42:54 Eliot gnome-session[1576]: (nautilus:2606): 
GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 
'G_TYPE_CHECK_INSTANCE (instance)' failed
  May  9 16:59:53 Eliot gnome-session[1576]: (nautilus:2842): 
GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 
'G_TYPE_CHECK_INSTANCE (instance)' failed
  May  9 17:00:19 Eliot gnome-session[1576]: (nautilus:2857): 
GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 
'G_TYPE_CHECK_INSTANCE (instance)' failed

  The last three failures appears whenever I activate nautilus.
  Nautilus will appear and work as usual.

  How can I resolve these failure notices?  Thanks in advance.

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

-- 
Mailing list: https://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 1506704] Re: Thin font, nautilus doesn't integrate with Unity.

2016-10-03 Thread WinEunuchs2Unix

That's good to know. I now have Startup Applications loading (which also
causes a delay) and thin fonts haven't appeared in a long time. I thought
they had fixed the bug.

Thank you for the update!

On Mon, Oct 3, 2016 at 10:17 AM, Alfred Cavigelli <
1506...@bugs.launchpad.net> wrote:

> I had a freshly installed Ubuntu 16.01.1 with same issues (thin fonts).
> The issue appeared with auto login only. Now I defined a auto-login-delay
> of 1 second and it works fine.
> To define the delay open the file "/etc/lightdm/lightdm.conf" and edit the
> line "autologin-user-timeout=1".
>
> $ sudo nano /etc/lightdm/lightdm.conf
>
> autologin-user-timeout=1
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1506704
>
> Title:
>   Thin font, nautilus doesn't integrate with Unity.
>
> Status in gnome-settings-daemon package in Ubuntu:
>   Confirmed
>
> Bug description:
>   It happens frequently (around 1/2 of the time) that when I boot the
>   computer, font lines are only one pixel thick. This concerns watch in
>   the sys-tray, all item in the menu of all applications, as well as all
>   fonts in Nautilus. When this happens. Nautilus doesn't display menu in
>   the Unity menu bar, but displays an additional button showing three
>   horizontal lines for bringing up the menu.
>
>   This problem has been with me for years, although sometimes disappears
>   for months at a time when I run sudo apt-get update. This time it re-
>   emerged after upgrading to 15.10 beta (Wily). It happens usually on
>   power-up, and disappears after system restart. (To appear again on the
>   next power-up).
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 15.10
>   Package: nautilus 1:3.14.2-0ubuntu12
>   ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
>   Uname: Linux 4.2.0-16-generic x86_64
>   ApportVersion: 2.19.1-0ubuntu2
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Fri Oct 16 04:53:31 2015
>   GsettingsChanges:
>
>   InstallationDate: Installed on 2015-10-08 (7 days ago)
>   InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
>   SourcePackage: nautilus
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
> daemon/+bug/1506704/+subscriptions
>

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

Title:
  Thin font, nautilus doesn't integrate with Unity.

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

Bug description:
  It happens frequently (around 1/2 of the time) that when I boot the
  computer, font lines are only one pixel thick. This concerns watch in
  the sys-tray, all item in the menu of all applications, as well as all
  fonts in Nautilus. When this happens. Nautilus doesn't display menu in
  the Unity menu bar, but displays an additional button showing three
  horizontal lines for bringing up the menu.

  This problem has been with me for years, although sometimes disappears
  for months at a time when I run sudo apt-get update. This time it re-
  emerged after upgrading to 15.10 beta (Wily). It happens usually on
  power-up, and disappears after system restart. (To appear again on the
  next power-up).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nautilus 1:3.14.2-0ubuntu12
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 16 04:53:31 2015
  GsettingsChanges:
   
  InstallationDate: Installed on 2015-10-08 (7 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1486450] Re: Error in loading other_hosts file

2016-09-25 Thread WinEunuchs2Unix

Same here:

Sep 25 12:06:13 dell com.ubuntu.OneConf[1161]:
WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No
such file or directory:
'/home/rick/.cache/oneconf/60404938df669372cddaa05a56db23ae/other_hosts'

I checked and the file does exist. Note the system had been suspended
and resumed 3 minutes earlier. Ubuntu 16.04 LTD, Kernel 4.7.3. Only
other anomaly (ok the major one!) is syslog shows systemd initiates
suspend and upon resume kernel starts sleep process and wakes up right
away.

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

Title:
  Error in loading other_hosts file

Status in oneconf package in Ubuntu:
  Confirmed

Bug description:
  I am seeing this error in the syslog

  Aug 19 20:38:31 M1 com.ubuntu.OneConf[25838]:
  WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No
  such file or directory: '/home/michael-
  heuberger/.cache/oneconf/813e56ef1c4f171bda95b46b5448007c/other_hosts'

  Any ideas what it could be and how to fix?

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

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

[Desktop-packages] [Bug 1506704] Re: Thin font, nautilus doesn't integrate with Unity.

2016-08-09 Thread WinEunuchs2Unix

NB This is more than a Nautilus issue because like others the Unity bar
is now clearer (before it was hard to read). Conky is now clearer.
Google chrome is noticeably clearer and scrolling is smooth when it used
to be choppy. The pixel breaks / line cracks when scrolling in Chrome
have disappeared. Should this be reclassified as a critical bug with
Linux Kernel / systemd as a whole and not just Nautilus? I had just
upgraded to Ubuntu 16.04 Kernel 4.4 then 4.6.3 when the Nautilus font
became an issue and led me to this thread. But even under Ubuntu 14.04 /
Kernel 3.13 there were problems which I'll try to recreate / eliminate
with the USB plugged in / not plugged in during boot.

As far as "3) Bluetooth Earbuds" in post #23 we must eliminate that off
the list because it's on a Y-Cable with the smartphone and only the
smartphone gets data comm + power, whereas the Earbuds are power only.

Watson the game is afoot.

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

Title:
Thin font, nautilus doesn't integrate with Unity.

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

Bug description:
It happens frequently (around 1/2 of the time) that when I boot the
computer, font lines are only one pixel thick. This concerns watch in
the sys-tray, all item in the menu of all applications, as well as all
fonts in Nautilus. When this happens. Nautilus doesn't display menu in
the Unity menu bar, but displays an additional button showing three
horizontal lines for bringing up the menu.

This problem has been with me for years, although sometimes disappears
for months at a time when I run sudo apt-get update. This time it re-
emerged after upgrading to 15.10 beta (Wily). It happens usually on
power-up, and disappears after system restart. (To appear again on the
next power-up).

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: nautilus 1:3.14.2-0ubuntu12
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Oct 16 04:53:31 2015
GsettingsChanges:

InstallationDate: Installed on 2015-10-08 (7 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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

[Desktop-packages] [Bug 1506704] Re: Thin font, nautilus doesn't integrate with Unity.

2016-08-09 Thread WinEunuchs2Unix

Can confirm now that simply unplugging the USB powered hub and rebooting
fixes the Nautilus 1 pixel font problem. Another problem where the
built-in display was black and only the TV got wallpaper was also fixed.
Plugging the USB hub in after boot did not break Nautilus fonts.

On the hub are:

1) UPS battery status monitor
2) Smartphone
3) Blue tooth ear buds
4) Laser Printer
5) Couple of spare cables

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

Title:
Thin font, nautilus doesn't integrate with Unity.

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

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

[Desktop-packages] [Bug 1506704] Re: Thin font, nautilus doesn't integrate with Unity.

2016-08-09 Thread WinEunuchs2Unix

Unfortunately the solution in #21 is not permanent and you have to
repeat it after reboot. More investigation is needed.

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

Title:
Thin font, nautilus doesn't integrate with Unity.

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

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

[Desktop-packages] [Bug 1506704] Re: Thin font, nautilus doesn't integrate with Unity.

2016-08-09 Thread WinEunuchs2Unix

I had same problems with Nautilus. Something to do with MS ttf fonts.
The solution for me was to open terminal and type:

fc-cache -rv

Then log out and log back in.

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

Title:
Thin font, nautilus doesn't integrate with Unity.

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

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

Re: [Desktop-packages] [Bug 1323089] Re: wpa_supplicant writes to syslog every 2 minutes

2016-04-13 Thread WinEunuchs2Unix

It's really a design flaw. Instead of saying every two minutes "Hey I
couldn't find a new AP". It should only say "I found AP number 99 and
connected to it" if and when it does.

On Wed, Apr 13, 2016 at 3:47 PM, rustyhamsterr 
wrote:

> I'm also affected, as my house has multiple AP's #24 is not working for me.
> My wifi card :
> System information:
> Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor
> Peak] (rev 34)
> Linux rustysTP 3.16.0-38-generic #52~14.04.1-Ubuntu SMP Fri May 8 09:43:57
> UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1323089
>
> Title:
>   wpa_supplicant writes to syslog every 2 minutes
>
> Status in wpa package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Ubuntu 14.04 LTS
>   wpasupplicant 2.1-0ubuntu1
>
>   wpa_supplicant is writing to syslog every couple of minutes. Example
>   output:
>
>   May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0:
> CTRL-EVENT-SCAN-STARTED
>   May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211:
> send_and_recv->nl_recvmsgs failed: -33
>   May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0:
> CTRL-EVENT-SCAN-STARTED
>   May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211:
> send_and_recv->nl_recvmsgs failed: -33
>   May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0:
> CTRL-EVENT-SCAN-STARTED
>   May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0:
> CTRL-EVENT-SCAN-STARTED
>   May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211:
> send_and_recv->nl_recvmsgs failed: -33
>   May 25 20:03:18 ubuntu wpa_supplicant[1161]: wlan0:
> CTRL-EVENT-SCAN-STARTED
>   May 25 20:03:23 ubuntu wpa_supplicant[1161]: nl80211:
> send_and_recv->nl_recvmsgs failed: -33
>   May 25 20:05:18 ubuntu wpa_supplicant[1161]: wlan0:
> CTRL-EVENT-SCAN-STARTED
>   May 25 20:05:23 ubuntu wpa_supplicant[1161]: nl80211:
> send_and_recv->nl_recvmsgs failed: -33
>   May 25 20:05:58 ubuntu wpa_supplicant[1161]: wlan0:
> CTRL-EVENT-SCAN-STARTED
>   May 25 20:07:18 ubuntu wpa_supplicant[1161]: wlan0:
> CTRL-EVENT-SCAN-STARTED
>   May 25 20:07:23 ubuntu wpa_supplicant[1161]: nl80211:
> send_and_recv->nl_recvmsgs failed: -33
>   May 25 20:09:18 ubuntu wpa_supplicant[1161]: wlan0:
> CTRL-EVENT-SCAN-STARTED
>   May 25 20:09:23 ubuntu wpa_supplicant[1161]: nl80211:
> send_and_recv->nl_recvmsgs failed: -33
>   May 25 20:10:58 ubuntu wpa_supplicant[1161]: wlan0:
> CTRL-EVENT-SCAN-STARTED
>   May 25 20:13:18 ubuntu wpa_supplicant[1161]: message repeated 2 times: [
> wlan0: CTRL-EVENT-SCAN-STARTED ]
>   May 25 20:13:23 ubuntu wpa_supplicant[1161]: nl80211:
> send_and_recv->nl_recvmsgs failed: -33
>
>   The message seems harmless as far as the network is concerned, meaning
>   there is no problem with the wifi connection. But it's spamming the
>   syslog, making it very difficult to find any other thing there, and
>   it's generating constant writes to disk, and an unnecessarily large
>   syslog file.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1323089/+subscriptions
>

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

Title:
  wpa_supplicant writes to syslog every 2 minutes

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.04 LTS
  wpasupplicant 2.1-0ubuntu1

  wpa_supplicant is writing to syslog every couple of minutes. Example
  output:

  May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:03:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:03:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:05:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:05:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:05:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:07:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:07:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:09:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:09:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:10:58 ubuntu

Re: [Desktop-packages] [Bug 1292467] Re: Dual screen greeter can break 3D acceleration

2015-08-07 Thread WinEunuchs2Unix

Why is showing up in my google in box?




More

*1* of *635*


[image: Expand all]
[image: Print all]
[image: In new window]
[Bug 1292467] Re: Dual screen greeter can break 3D acceleration
Inbox
x
Fabiano Brites
Same problem here. So another user affected by this bug. -- You received
this...
10/16/14
Rael
Interesting. My previous version was 12.04. And I spent a huge time
wondering...
Jan 4
bigley.ling
Does anyone know when an update may be fixing this issue? Having to disable
L...
Jun 29
Mathew Hodson mathew.hod...@gmail.com via
https://support.google.com/mail/answer/1311182?hl=en canonical.com
4:31 PM (2 hours ago)
to me
** Tags added: trusty

On Fri, Aug 7, 2015 at 4:31 PM, Mathew Hodson mathew.hod...@gmail.com
wrote:

 ** Tags added: trusty

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1292467

 Title:
   Dual screen greeter can break 3D acceleration

 Status in Release Notes for Ubuntu:
   Fix Released
 Status in unity-greeter package in Ubuntu:
   Triaged

 Bug description:
   When booting with two screens (internal LVDS and VGA), lightdm comes
   up in a mode where it displays separate screen content on both
   displays (so no mirror mode). These screens seem to be arranged side-
   by-side regardless of the fact that (like in my case) the combined
   width can be greater than 2048 and that is not supported with 3D
   acceleration at least on that older i945GME graphics.

   This results in very poor graphics performance and compiz using a lot
   of cpu cycles (which are rather limited on this Atom N270 anyways).
   Even worse, this does not get resolved when changing the setup in
   system settings to either only having one screen active or arranging
   them on top of each other).

   WORKAROUND:
* Plug in external monitor after login (1)
* Boot with video=LVDS-1:d (2)

   (1) Booting with only the internal screen and then plugging in the
   external one after login seems to handle this better (although I
   probably need to remove any previous config to get into a kind of
   vanilla state again). Also it seems to be ok when I had the dual
   monitor boot and lightdm coming up side-by-side, when unplugging the
   external monitor before logging in.

   (2) This will completely disable the internal screen for that boot. It
   cannot be enabled through the settings dialogue.

 To manage notifications about this bug go to:
 https://bugs.launchpad.net/ubuntu-release-notes/+bug/1292467/+subscriptions


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

Title:
  Dual screen greeter can break 3D acceleration

Status in Release Notes for Ubuntu:
  Fix Released
Status in unity-greeter package in Ubuntu:
  Triaged

Bug description:
  When booting with two screens (internal LVDS and VGA), lightdm comes
  up in a mode where it displays separate screen content on both
  displays (so no mirror mode). These screens seem to be arranged side-
  by-side regardless of the fact that (like in my case) the combined
  width can be greater than 2048 and that is not supported with 3D
  acceleration at least on that older i945GME graphics.

  This results in very poor graphics performance and compiz using a lot
  of cpu cycles (which are rather limited on this Atom N270 anyways).
  Even worse, this does not get resolved when changing the setup in
  system settings to either only having one screen active or arranging
  them on top of each other).

  WORKAROUND:
   * Plug in external monitor after login (1)
   * Boot with video=LVDS-1:d (2)

  (1) Booting with only the internal screen and then plugging in the
  external one after login seems to handle this better (although I
  probably need to remove any previous config to get into a kind of
  vanilla state again). Also it seems to be ok when I had the dual
  monitor boot and lightdm coming up side-by-side, when unplugging the
  external monitor before logging in.

  (2) This will completely disable the internal screen for that boot. It
  cannot be enabled through the settings dialogue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1292467/+subscriptions

-- 
Mailing list: https://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 1323089] Re: wpa_supplicant writes to syslog every 2 minutes

2015-04-20 Thread WinEunuchs2Unix

I'm not Anne and I don't fully remember this bug. I believe it was about
Linux looking for new WiFi routers to connect to every 2 minutes and
issuing a message when one was not found. This given there should be an
option within Ubuntu Network Manager (or whomever) to not message every 2
minutes when a new WiFi connection is not found.

On Sat, Apr 18, 2015 at 10:21 AM, Neal McBurnett n...@bcn.boulder.co.us
wrote:

 Thank you Anne for describing what looks like one way to fix this for
 all connections, rather than the easy fix in #24 which only addresses
 one SSID.

 But I worry that making wpa_supplicant more quiet will hide messages
 that are important - what else would be suppressed?

 So I suspect that the bug should be fixed somewhere else, since it seems
 clear to me that default installs with popular wifi cards should not
 spam syslog, and this does seem to be related to only some forms of
 Intel wifi cards - mostly Centrino I guess.

 So what is printing this out, which developer explained the workaround
 (sometime after 2009?), and how do we clean up our syslogs?

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1323089

 Title:
   wpa_supplicant writes to syslog every 2 minutes

 Status in wpa package in Ubuntu:
   Confirmed

 Bug description:
   Ubuntu 14.04 LTS
   wpasupplicant 2.1-0ubuntu1

   wpa_supplicant is writing to syslog every couple of minutes. Example
   output:

   May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0:
 CTRL-EVENT-SCAN-STARTED
   May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211:
 send_and_recv-nl_recvmsgs failed: -33
   May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0:
 CTRL-EVENT-SCAN-STARTED
   May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211:
 send_and_recv-nl_recvmsgs failed: -33
   May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0:
 CTRL-EVENT-SCAN-STARTED
   May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0:
 CTRL-EVENT-SCAN-STARTED
   May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211:
 send_and_recv-nl_recvmsgs failed: -33
   May 25 20:03:18 ubuntu wpa_supplicant[1161]: wlan0:
 CTRL-EVENT-SCAN-STARTED
   May 25 20:03:23 ubuntu wpa_supplicant[1161]: nl80211:
 send_and_recv-nl_recvmsgs failed: -33
   May 25 20:05:18 ubuntu wpa_supplicant[1161]: wlan0:
 CTRL-EVENT-SCAN-STARTED
   May 25 20:05:23 ubuntu wpa_supplicant[1161]: nl80211:
 send_and_recv-nl_recvmsgs failed: -33
   May 25 20:05:58 ubuntu wpa_supplicant[1161]: wlan0:
 CTRL-EVENT-SCAN-STARTED
   May 25 20:07:18 ubuntu wpa_supplicant[1161]: wlan0:
 CTRL-EVENT-SCAN-STARTED
   May 25 20:07:23 ubuntu wpa_supplicant[1161]: nl80211:
 send_and_recv-nl_recvmsgs failed: -33
   May 25 20:09:18 ubuntu wpa_supplicant[1161]: wlan0:
 CTRL-EVENT-SCAN-STARTED
   May 25 20:09:23 ubuntu wpa_supplicant[1161]: nl80211:
 send_and_recv-nl_recvmsgs failed: -33
   May 25 20:10:58 ubuntu wpa_supplicant[1161]: wlan0:
 CTRL-EVENT-SCAN-STARTED
   May 25 20:13:18 ubuntu wpa_supplicant[1161]: message repeated 2 times: [
 wlan0: CTRL-EVENT-SCAN-STARTED ]
   May 25 20:13:23 ubuntu wpa_supplicant[1161]: nl80211:
 send_and_recv-nl_recvmsgs failed: -33

   The message seems harmless as far as the network is concerned, meaning
   there is no problem with the wifi connection. But it's spamming the
   syslog, making it very difficult to find any other thing there, and
   it's generating constant writes to disk, and an unnecessarily large
   syslog file.

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


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

Title:
  wpa_supplicant writes to syslog every 2 minutes

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.04 LTS
  wpasupplicant 2.1-0ubuntu1

  wpa_supplicant is writing to syslog every couple of minutes. Example
  output:

  May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 20:03:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:03:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 20:05:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:05:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 20:05:58 ubuntu wpa_supplicant[1161]:

Re: [Desktop-packages] [Bug 1323089] Re: wpa_supplicant writes to syslog every 2 minutes

2015-04-20 Thread WinEunuchs2Unix

Indeed under this free roaming philosophy even if another WiFi node is
found it should not be connected to unless the signal strength is hire.
Then and only then when connected a message should be sent.

Sending a message on success is infinitely preferable to a message of
failure to a connection you probably weren't looking for in the first place.

On Mon, Apr 20, 2015 at 8:56 PM, Rick Lee ricklee...@gmail.com wrote:

 I'm not Anne and I don't fully remember this bug. I believe it was about
 Linux looking for new WiFi routers to connect to every 2 minutes and
 issuing a message when one was not found. This given there should be an
 option within Ubuntu Network Manager (or whomever) to not message every 2
 minutes when a new WiFi connection is not found.

 On Sat, Apr 18, 2015 at 10:21 AM, Neal McBurnett n...@bcn.boulder.co.us
 wrote:

 Thank you Anne for describing what looks like one way to fix this for
 all connections, rather than the easy fix in #24 which only addresses
 one SSID.

 But I worry that making wpa_supplicant more quiet will hide messages
 that are important - what else would be suppressed?

 So I suspect that the bug should be fixed somewhere else, since it seems
 clear to me that default installs with popular wifi cards should not
 spam syslog, and this does seem to be related to only some forms of
 Intel wifi cards - mostly Centrino I guess.

 So what is printing this out, which developer explained the workaround
 (sometime after 2009?), and how do we clean up our syslogs?

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1323089

 Title:
   wpa_supplicant writes to syslog every 2 minutes

 Status in wpa package in Ubuntu:
   Confirmed

 Bug description:
   Ubuntu 14.04 LTS
   wpasupplicant 2.1-0ubuntu1

   wpa_supplicant is writing to syslog every couple of minutes. Example
   output:

   May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0:
 CTRL-EVENT-SCAN-STARTED
   May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211:
 send_and_recv-nl_recvmsgs failed: -33
   May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0:
 CTRL-EVENT-SCAN-STARTED
   May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211:
 send_and_recv-nl_recvmsgs failed: -33
   May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0:
 CTRL-EVENT-SCAN-STARTED
   May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0:
 CTRL-EVENT-SCAN-STARTED
   May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211:
 send_and_recv-nl_recvmsgs failed: -33
   May 25 20:03:18 ubuntu wpa_supplicant[1161]: wlan0:
 CTRL-EVENT-SCAN-STARTED
   May 25 20:03:23 ubuntu wpa_supplicant[1161]: nl80211:
 send_and_recv-nl_recvmsgs failed: -33
   May 25 20:05:18 ubuntu wpa_supplicant[1161]: wlan0:
 CTRL-EVENT-SCAN-STARTED
   May 25 20:05:23 ubuntu wpa_supplicant[1161]: nl80211:
 send_and_recv-nl_recvmsgs failed: -33
   May 25 20:05:58 ubuntu wpa_supplicant[1161]: wlan0:
 CTRL-EVENT-SCAN-STARTED
   May 25 20:07:18 ubuntu wpa_supplicant[1161]: wlan0:
 CTRL-EVENT-SCAN-STARTED
   May 25 20:07:23 ubuntu wpa_supplicant[1161]: nl80211:
 send_and_recv-nl_recvmsgs failed: -33
   May 25 20:09:18 ubuntu wpa_supplicant[1161]: wlan0:
 CTRL-EVENT-SCAN-STARTED
   May 25 20:09:23 ubuntu wpa_supplicant[1161]: nl80211:
 send_and_recv-nl_recvmsgs failed: -33
   May 25 20:10:58 ubuntu wpa_supplicant[1161]: wlan0:
 CTRL-EVENT-SCAN-STARTED
   May 25 20:13:18 ubuntu wpa_supplicant[1161]: message repeated 2 times:
 [ wlan0: CTRL-EVENT-SCAN-STARTED ]
   May 25 20:13:23 ubuntu wpa_supplicant[1161]: nl80211:
 send_and_recv-nl_recvmsgs failed: -33

   The message seems harmless as far as the network is concerned, meaning
   there is no problem with the wifi connection. But it's spamming the
   syslog, making it very difficult to find any other thing there, and
   it's generating constant writes to disk, and an unnecessarily large
   syslog file.

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




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

Title:
  wpa_supplicant writes to syslog every 2 minutes

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.04 LTS
  wpasupplicant 2.1-0ubuntu1

  wpa_supplicant is writing to syslog every couple of minutes. Example
  output:

  May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211:

[Desktop-packages] [Bug 1292467] Re: Dual screen greeter can break 3D acceleration

2014-09-13 Thread WinEunuchs2Unix

Comment #8 seems out of context.  Once booted there is no problem
plugging in and unplugging monitors, changing resolution and scan
frequencies.  Additionally there is no problem suspending and resuming--
which is a good reason to never reboot unless resume fails or a boot
into windows / different distro is required.

The problem is that when booting the system compiz in my case and
lightdm is other posters cases gets confused.  I get error messages and
from then on Flash Player under Google Chrome doesn't effectively use
the GPU so burns up CPU cycles.  For other users 3D acceleration (which
also uses a GPU or discrete graphics card/chip) degrades.

Ideally users should be able to boot their machines with 2 or 3 active
monitors and not have to worry about unplugging this screen or that
screen each time.  I think with extensions users can have up to 6 or 7
screens.

Just as kernel modules have dependencies (as shown by modprobe) xrandr
needs to reveal a dependency that xorg must be up and running before it
is loaded.  The kernel scheduler (when it is written) needs to put
xrandr to sleep in 1/10th second loops until xorg is running along with
compiz and whatever else it needs.

Similar issues might exist with udev, btrfs, acpi, usb devices, etc.
etc.  Pardon my poor analysis with only 100 hours or so of Linux
education time so far.

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

Title:
  Dual screen greeter can break 3D acceleration

Status in Release Notes for Ubuntu:
  Fix Released
Status in “unity-greeter” package in Ubuntu:
  Triaged

Bug description:
  When booting with two screens (internal LVDS and VGA), lightdm comes
  up in a mode where it displays separate screen content on both
  displays (so no mirror mode). These screens seem to be arranged side-
  by-side regardless of the fact that (like in my case) the combined
  width can be greater than 2048 and that is not supported with 3D
  acceleration at least on that older i945GME graphics.

  This results in very poor graphics performance and compiz using a lot
  of cpu cycles (which are rather limited on this Atom N270 anyways).
  Even worse, this does not get resolved when changing the setup in
  system settings to either only having one screen active or arranging
  them on top of each other).

  WORKAROUND:
   * Plug in external monitor after login (1)
   * Boot with video=LVDS-1:d (2)

  (1) Booting with only the internal screen and then plugging in the
  external one after login seems to handle this better (although I
  probably need to remove any previous config to get into a kind of
  vanilla state again). Also it seems to be ok when I had the dual
  monitor boot and lightdm coming up side-by-side, when unplugging the
  external monitor before logging in.

  (2) This will completely disable the internal screen for that boot. It
  cannot be enabled through the settings dialogue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1292467/+subscriptions

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

[Desktop-packages] [Bug 1323089] Re: wpa_supplicant writes to syslog every 2 minutes

2014-08-17 Thread WinEunuchs2Unix

It doesn't happen with Intel 3495 abg (wlan0) when 802.11n is turned off
but will happen if 802.11n is active for other wifi adapters.  It
happens with RTL2800 bgn (wlan1), BCM43526 ac+gn (wlan2), Intel Centrino
6235 bgn (wlan3) and now with RTL 3072 bgn (wlan4).

Very aggravating, especially since since I don't know what CTRL-EVEN-
SCAN-STARTED is and if I need on every minute instead of once a day.  I
might pick up an Atheros wifi adapter soon but I'll bet my favorite
laptop sticker it'll have the same grief with 802.11n.  And NO I'm not
turning off 802.11n because I like seeing Bit Rate:115.Mb/s on my
Conky display instead of 54 Mb/s.

Could a kernel developer or network-manager programmer not give some
advise to these many posts littering the netosphere please?

Don't even get me started ranting about 802.11ac...

PROOF:
Aug 17 17:49:15 Rick-Satellite-L300 wpa_supplicant[1491]: wlan0: 
CTRL-EVENT-SCAN-STARTED 
Aug 17 17:50:18 Rick-Satellite-L300 wpa_supplicant[1491]: wlan0: 
CTRL-EVENT-SCAN-STARTED 
Aug 17 17:50:25 Rick-Satellite-L300 wpa_supplicant[1491]: wlan4: 
CTRL-EVENT-SCAN-STARTED 
Aug 17 17:51:21 Rick-Satellite-L300 wpa_supplicant[1491]: wlan0: 
CTRL-EVENT-SCAN-STARTED 
Aug 17 17:52:24 Rick-Satellite-L300 wpa_supplicant[1491]: wlan0: 
CTRL-EVENT-SCAN-STARTED 
Aug 17 17:52:25 Rick-Satellite-L300 wpa_supplicant[1491]: wlan4: 
CTRL-EVENT-SCAN-STARTED 
Aug 17 17:53:27 Rick-Satellite-L300 wpa_supplicant[1491]: wlan0: 
CTRL-EVENT-SCAN-STARTED 
Aug 17 17:54:25 Rick-Satellite-L300 wpa_supplicant[1491]: wlan4: 
CTRL-EVENT-SCAN-STARTED 
Aug 17 17:54:30 Rick-Satellite-L300 wpa_supplicant[1491]: wlan0: 
CTRL-EVENT-SCAN-STARTED 

~$

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

Title:
  wpa_supplicant writes to syslog every 2 minutes

Status in “wpa” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.04 LTS
  wpasupplicant 2.1-0ubuntu1

  wpa_supplicant is writing to syslog every couple of minutes. Example
  output:

  May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 20:03:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:03:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 20:05:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:05:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 20:05:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:07:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:07:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 20:09:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:09:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 20:10:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:13:18 ubuntu wpa_supplicant[1161]: message repeated 2 times: [ 
wlan0: CTRL-EVENT-SCAN-STARTED ]
  May 25 20:13:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33

  The message seems harmless as far as the network is concerned, meaning
  there is no problem with the wifi connection. But it's spamming the
  syslog, making it very difficult to find any other thing there, and
  it's generating constant writes to disk, and an unnecessarily large
  syslog file.

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

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

[Desktop-packages] [Bug 1323089] Re: wpa_supplicant writes to syslog every 2 minutes

2014-08-17 Thread WinEunuchs2Unix

Oops this has been going on since 2009 and a developer did respond that
it is simply for roaming in corporate environments with multiple access
points to connect to.  If you only have one AP at home go into network
manager, select Edit Connection, highlight your AP / wlan0 and click
Edit.  Then click the down arrow next to BSSID  which is blank.  Then
select the mac address that was hidden before.

My apologies for linking this to an 802.11n problem.  Once bitten twice
shy I guess

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

Title:
  wpa_supplicant writes to syslog every 2 minutes

Status in “wpa” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.04 LTS
  wpasupplicant 2.1-0ubuntu1

  wpa_supplicant is writing to syslog every couple of minutes. Example
  output:

  May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 20:03:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:03:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 20:05:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:05:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 20:05:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:07:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:07:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 20:09:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:09:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33
  May 25 20:10:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:13:18 ubuntu wpa_supplicant[1161]: message repeated 2 times: [ 
wlan0: CTRL-EVENT-SCAN-STARTED ]
  May 25 20:13:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33

  The message seems harmless as far as the network is concerned, meaning
  there is no problem with the wifi connection. But it's spamming the
  syslog, making it very difficult to find any other thing there, and
  it's generating constant writes to disk, and an unnecessarily large
  syslog file.

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

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

[Desktop-packages] [Bug 1292467] Re: Dual screen greeter can break 3D acceleration

2014-08-08 Thread WinEunuchs2Unix

This exact bug seems to happen on a Toshiba Satellite L-300 with Intel
Centrino 2 Core Duo T5750 with GME965 GPU using i915 driver under Linux
Kernel's 3.13.xx and 3.15.xx with Ubuntu 14.04.  Work around to unplug
the external TV on every reboot is a minor inconvience.

When Henry in comment #5 made his post I was automatically e-mailed the
message along with his e-mail address.  This is an EVEN BIGGER BUG on
this website.

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

Title:
  Dual screen greeter can break 3D acceleration

Status in Release Notes for Ubuntu:
  Fix Released
Status in “unity-greeter” package in Ubuntu:
  Triaged

Bug description:
  When booting with two screens (internal LVDS and VGA), lightdm comes
  up in a mode where it displays separate screen content on both
  displays (so no mirror mode). These screens seem to be arranged side-
  by-side regardless of the fact that (like in my case) the combined
  width can be greater than 2048 and that is not supported with 3D
  acceleration at least on that older i945GME graphics.

  This results in very poor graphics performance and compiz using a lot
  of cpu cycles (which are rather limited on this Atom N270 anyways).
  Even worse, this does not get resolved when changing the setup in
  system settings to either only having one screen active or arranging
  them on top of each other).

  WORKAROUND:
   * Plug in external monitor after login (1)
   * Boot with video=LVDS-1:d (2)

  (1) Booting with only the internal screen and then plugging in the
  external one after login seems to handle this better (although I
  probably need to remove any previous config to get into a kind of
  vanilla state again). Also it seems to be ok when I had the dual
  monitor boot and lightdm coming up side-by-side, when unplugging the
  external monitor before logging in.

  (2) This will completely disable the internal screen for that boot. It
  cannot be enabled through the settings dialogue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1292467/+subscriptions

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

[Desktop-packages] [Bug 1125944] Re: (gedit:3366): IBUS-WARNING **: The owner of ~/.config/ibus/bus is not root!

2014-07-20 Thread WinEunuchs2Unix

Van Halen's Maxwell Jump song is appreciated in comment #21.

I too received this error today.  I was guilty of running two terminal
sessions a day or two ago and I am guilty of using gedit one time and
sudo gedit another time on the same file if permission is denied the
first time.

Ubuntu 14.04 LTS, Kernel 3.15.6-blah blah-generic.

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

Title:
  (gedit:3366): IBUS-WARNING **: The owner of ~/.config/ibus/bus is not
  root!

Status in “ibus” package in Ubuntu:
  Won't Fix

Bug description:
  RR i386 logged as gnome-classic (fallback)

  Seen that error for the first time while using a terminal:

  oem@oem-desktop:~$ sudo gedit /etc/default/grub

  (gedit:3366): IBUS-WARNING **: The owner of /home/oem/.config/ibus/bus
  is not root!

  That one is own by Me (screenshot joined)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: ibus 1.4.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  Date: Fri Feb 15 08:33:36 2013
  MarkForUpload: True
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1213338] Re: Displaylink slow graphic performance on Ubuntu 13

2014-07-11 Thread WinEunuchs2Unix

I have similar problems using xrandr on a laptop with a dual display LCD
32 TV under Ubuntu 14.04 with Kernel's 3.13.24, 3.13.29, 3.15.1,
3.15.2, 3.15.3, 3.15.4 and 3.15.5.  A new Kernel seems to come out each
week addressing various problems so I have held off reporting the
glitches.

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

Title:
  Displaylink slow graphic performance on Ubuntu 13

Status in “xorg-server” package in Ubuntu:
  Expired

Bug description:
  Hello,

  When I connect the diaplay link (DVI) and I activate the screen in
  xRandr, the graphic performance slow down, the mouse movement are
  jerky and the mouse cursor blink on all screen, when I move a window,
  is also not fluid.

  When I desactivate the screen in xRandr, but I keep the displaylink
  connected, everything work fine.

  I also tried to take all graphic effect and desktop in compiz setup,
  stay the same.

  I'm running Ubuntu 13.04 64 bits and the Kernel
  3.11.0-031100rc5-generic I tried also with Kernel 3.10 and 3.9.

  My Graphic card is a Intel.

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

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

37 matches

Mail list logo